TK310 PDF

TK310
EAGLE 5 ISS Release 40 / EPAP 12
IS41 GSM Migrations (IGM)
TK310v.1.5
TEKELEC Confidential For Training Purposes Only
Table of Contents
Module 1 Number Portability Review.. 7
Module 2 IGM Feature Defined.47
Module 3 IGM Functions ... 65
Module 4 IGM Feature Activation..
81
Module 5 Additional Features..105

Appendix A: ANSI-41 & GSM Operation Codes137
TK310v.1.5
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
TK310v.1.5
Training Strategies and Materials

Participant-Centered Training
Based on learning objectives
Lecture and discussion
Question and answer
Daily performance reviews
Student Training Guide

Classroom
Tekelec Product Documentation

Feature Manual - Migration
Copies of the listed EAGLE STP user manuals will be available for use during classroom and
laboratory activities. The instructor will direct students to the appropriate manual.
At the end of each day, you will complete a Daily Progress Review form. This form will give
you an opportunity to evaluate your learning progress and request additional information on
topics covered during that day of training.
TK310v.1.5
Course Objectives
After this Course, you should be able to:
Describe IS41 - GSM Migration (IGM) and its
relevance to mobile number portability
Know the EAGLE 5 ISS commands for IGM
provisioning
Activate the IGM feature
Describe additional features associated with IGM
TK310v.1.5
Student Notes
TK310v.1.5
Module 1
Number Portability Review
TK310v.1.5
Module 1
After this module of instruction, you should be
able to:
Identify and define fields within the Message Signal Unit
(MSU)
Identify components of the Numbering Plan (NP) and the
Nature of Address Indicator (NAI)
Define the purpose and functions of Number Portability (NP)
Identify NP environment changes
Identify different routing options for NP
TK310v.1.5
Message Signalling Unit
Message Signalling Unit

(MSU)
TK310v.1.5
10
SS7/CCS7 Signal Units
Signal Units
FISU
LSSU
MSU
Fill In Signal Unit
Link Status Signal Unit
Message Signal Unit
The SS7 protocol uses signal units to provide transmission of data in the SS7
network. There are three different types of signal units providing three different
levels of service. These signal units vary in length and consist of octets of 8 bit
segments.
Fill In Signal Unit (FISU) - used for error control if there are no MSU
being transmitted, and are transmitted along with MSUs to keep signaling
links full of some type of signal units . It is the lowest level signal unit.
Link Status Signal Unit (LSSU) transports level two status information
about the Signaling Link over which it is transmitted. LSSUs are present
only when there is some type of problem with the signaling link. When
signaling links are aligned, and performing correctly, there are no LSSUs
being transmitted across a signaling link.
Message Signal Unit (MSU) transports the message payload over the
Signaling Network. This payload includes ISUP, SCCP, & Network
Management messages.
TK310v.1.5
10
11
SS7/CCS7 Signal Unit Fields

Transmission Direction
FISU
CK
LI
16
F
B
I FSN I BSN
B
B
7
7
1
1
FLAG
LSB
8
LSSU
CK
F
B
I FSN I BSN
B
B
6 1
7
1
7
LI
SF
8 or 16 2
16
FLAG
LSB
8
MSU
CK
SIF
SIO
16
8n, n>2
F
B
I FSN I BSN
B
B
7
7
6 1
1
LI
2
FLAG
LSB
8
Fill-In-Signal Unit (FISU)

Sent when no traffic is being sent and the network is idle
Provides continuous error checking on signaling links
Allows the SS7 network to maintain its reliability
Lowest level signal unit
Carries basic level 2 information only (i.e., acknowledgment of signal unit
receipt by a remote signaling point)
Link Status Signal Unit (LSSU)
Carries one or two octets (8-bit bytes) of link status information
Used to control link alignment
Indicates the status of a signaling point (e.g., local processor outage) to
the remote signaling point
Message Signal Unit (MSU)
Call control
Database query and response
Network management
Network maintenance
Has a routing label which consists of an originating and a destination point
code
TK310v.1.5
11
12
Message Signal Unit (MSU) Structure

ANSI Example
Level 2
CRC
Level 4
TCAP/MAP
CGPA
Length
Address Indicator
Subsystem
Point Code
(NCM NC NI)
Routing Label
CDPA
Length
Address
Indicator
Routing Indicator
Subsystem
Point Code
(NCM NC NI)
SLS
OPC
NCM NC NI
DPC
NCM NC NI
Level 2
SIO
NIC PRI SI
LI FSN BSN
ITU Example
Level 2
CRC
TK310v.1.5
Level 4
TCAP/MAP
CGPA
Length
Address Indicator
Subsystem
Point Code
(ID Zone Area)
(NPC)
Routing Label
CDPA
Length
Address
Indicator
Routing Indicator
Subsystem
Point Code
(ID Zone Area)
(NPC)
SLS
OPC
(ID Zone Area)
(NPC)
DPC
(ID Zone Area)
(NPC)
Level 2
SIO
NIC PRI SI
LI FSN BSN
12
13
MSU Fields used in GTT
Message Signal Unit

(MSU)
Signaling Information Field
(SIF)
Address
Indicator
Routing
Label
An MSU is distinguished from other Signaling Unit (SU) types by two fields, the Signaling Information
Field (SIF) and Service Information Octet (SIO).
The SIF is made up of two components used in GTT:
Address Indicator containing calling party address information (CGPA) and called party
information (CDPA)
Routing Label containing originating and destination point codes
The CDPA field has the digits, translation type (tt), point code (pc), and routing indicator (ri)
used during the Migration process.
TK310v.1.5
13
14
Signaling Information Field - Routing Label

TRANSMISSION DIRECTION
16
8n, n>2
CK
SIF
SIO
L F FSN BIB
I I
B
BSN
FLAG
Routing Label
DPC
NCM-NC-NI
0-16383
OPC
ANSI
NCM-NC-NI
ITU-N
016383
MSA-SSA-SP
ITU-N24
MSA-SSA-SP
Zone-Area-ID
ITU-I
Zone-Area-ID
The Signaling Information Field (SIF) is used by both level three and level four. It is divided into multiple parts:
Routing label - includes SLS (Signaling Link Selection), OPC and DPC and is used by level three for
message routing.
The point codes of the routing label change values as the SCCP message moves from signaling
point to signaling point if the MSU is manipulated.
TK310v.1.5
14
15
ANSI SIF Address Indicator

The first octet of the CGPA and the CDPA is the
Address Indicator.
Address Indicator is coded as follows:
Bit 1
Bit 2
Bits 3 6
Bit 7
Bit 8
8
NI
RI
Subsystem Number indicator - value of 0 or 1

Point Code Indicator - value of 0 or 1
Global Title Indicator value of 0 to 4
Routing Indicator - value of GT or SSN
National/International Indicator value of 0 or 1
6
GTI
PC SSN
The SCCP portion contains these fields used in the EAGLE Global Title Translation database administration
commands.
The address indicator octet in the CGPA/CDPA is divided into five Modules:
Bit one indicates if a SSN is included:
0 - subsystem number is not included.
1 - subsystem number is included.
Bit two indicates if a PC is included.
0 - point code is not included.
1 - point code is included.
Bits three thru six are the global title indicator(GTI) with one of the 5 values:
0 - no global title included.
1- global title includes nature of address indicator only.
2 - global title includes translation type and digits.
3 - global title includes translation type, numbering plan and encoding scheme.
4 - global title includes translation type, numbering plan, nature of address indicator, and digits.
Bit seven indicates if subsequent GT translations are required (RI).
GT indicates that a subsequent translation must be performed (protocol uses a value of 0 to indicate
this).
SSN indicates that no further translations are required (protocol uses a value of 1 to indicate this).
Bit eight is the international/national network indicator:
0 - indicates a message from an international network.
1 - indicates a message from a national network.
TK310v.1.5
15
16
ANSI Signaling Information Field (CDPA)

CK
SIF
L F FSN BIB
I I
B
SIO
BSN FLAG
CDPA
GTA
TT
Global Title Translation

Type
Address
Digits
PC
SSN
AI
Point
Code
Subsystem
Number
Address
Indicator
5=CNAM
11=LNP
251=CLASS
253=LIDB
254=E800
NCM NC NI
TK310v.1.5
5=MAP
6= HLR
7= VLR
8= MSC
245=LNP
251=CLASS
253=LIDB
254=E800
GTI =2(tt & digits)

RI =0 (route on gt), =1(route on pc/ssn)
NI =0 (international ntwk), =1(national ntwk)
16
17
CDPA Format (ANSI)
TK310v.1.5
00001000
CDPA Length indicator
01001010
Address indicator
0- - - - - - -
Reserved
-1- - - - - -
Routing Indicator
1 - route on DPC + SSN
- -0010- -
Global Title indicator
2 - Global title includes tt, digits
------0-
Point Code indicator
0 - address does not contain a point code
- - - - - - -1
SSN indicator
1- the address contains a SSN
11111110
Subsystem number
254 - E800
11111110
Translation type
254
--------
Global title address information
8004618345
17
18
ITU SIF Address Indicator

The first octet of the CGPA and the CDPA is the
Address Indicator.
Address Indicator is coded as follows:
Bit 1
Bit 2
Bits 3 6
Bit 7
Bit 8
8
NI
RI
Point Code indicator - value of 0 or 1

Subsystem Number Indicator - value of 0 or 1
Global Title Indicator value of 0 to 4
Routing Indicator - value of GT or SSN
National/International Indicator value of 0 or 1
6
GTI
SSN
PC
The SCCP portion contains these fields used in the EAGLE Global Title Translation database administration commands.
The address indicator octet in the CGPA/CDPA is divided into five Modules:
Bit one indicates if a PC is included.
0 - point code is not included.
1 - point code is included.
Bit two indicates if a SSN is included:
0 - subsystem number is not included.
1 - subsystem number is included.
Bits three thru six are the global title indicator(GTI) with one of the 5 values:
0 - no global title included.
1- global title includes nature of address indicator only.
2 - global title includes translation type and digits.
3 - global title includes translation type, numbering plan and encoding scheme.
4 - global title includes translation type, numbering plan, nature of address indicator, and digits.
Bit seven indicates if subsequent GT translations are required (RI).
GT indicates that a subsequent translation must be performed (protocol uses a value of 0 to indicate this).
SSN indicates that no further translations are required (protocol uses a value of 1 to indicate this).
Bit eight is the international/national network indicator:
0 - indicates a message from an international network.
1 - indicates a message from a national network.
TK310v.1.5
18
19
ITU Signaling Information Field (CDPA)

CK
SIF
SIO
L F FSN BIB
I I
B
BSN FLAG
CDPA
GTA
NAI
NP
ES
TT
SSN
PC
AI
Global Title
Address
Nature of Address
Indicator
Numbering
Plan
Encoding
Scheme
Translation
Type
Subsystem
Number
Point
Code
Address
Indicator
Dialed
Digits /
Directory
Number
1= Subscriber Number
2= Reserved
3= National
4= International
5=127 - Spare
1= E164 ISDN
6= E212 Land Mobile
7= E214 ISDN Mobile
TT-0
5=MAP
6= HLR
7= VLR
8= MSC
Binary Coded Decimal

1= odd numbers
2=even numbers
Zone Area ID
NPC
MSA SSA SP
GTI =2(tt & digits), =4(tt, nai, np & digits)
RI =0 (route on gt), =1(route on pc/ssn)
NI =0 (international ntwk), =1(national ntwk)
TK310v.1.5
19
20
CDPA Format (ITU)

00001010
CDPA Length indicator
10
01010010
Address indicator
0- - - - - - -
Reserved
-1- - - - - -
Routing indicator
1 - route on DPC + SSN
- -0100- -
Global title indicator
4 - Global title includes tt, np, nai, digits
- - - - - -1-
SSN indicator
1- the address contains a SSN
- - - - - - -0
Point code indicator
0 address does not contain a point code
10010010
Subsystem number
146 - CAMEL
00000000
Translation type
0 - unknown
0001- - - -
Numbering plan
1- ISDN numbering plan E.164
- - - -0010
Encoding scheme
2 BCD, even number of digits
- 0000100
Nature of address indicator
4 - international number
--------
Global title address information
553199339484
An example of protocol analysis of this SCCP message
TK310v.1.5
20
21
MAP Layer
Following the TCAP (Transaction Capability Application Part)
layer is the Map (Mobile Application Part) layer.
Within the MAP Layer there are a variety of parameters but
the parameters that are most important to the Migration
feature are the Operation Codes (Op Codes).
See Appendix A for lists of ANSI and ITU Op Codes.
TK310v.1.5
21
22
Numbering Plan
Numbering Plan
(NP)
TK310v.1.5
22
Numbering Plan (NP)
23
The numbering plan value in the MSU is used to

indicate how a directory number is structured.
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
Numbering Plan is then selected
TK310v.1.5
23
24
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 Mobile 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
This is the Numbering Plan for IGM
TK310v.1.5
24
25
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
TK310v.1.5
25
26
Nature of Address Indicator

(NAI)
TK310v.1.5
26
27
The Nature of Address Indicator value in the MSU is

used to indicate how a number is formatted.
In ITU, there are four types of NAI:
International
National
Subscriber
Unknown
Depending on the type of transaction exchanged

between two SS7 nodes and the configuration of
the nodes, the appropriate NAI is then selected.
TK310v.1.5
27
28
E.164
CC + NDC + SN (International)
- 99 70 22222222222
NDC + SN (National)
- 70 22222222222
SN (Subscriber)
- 22222222222
Unknown National
- 0 70 22222222222
- 0 at the beginning is called National Escape Code <NEC>
Unknown International
- 00 99 70 22222222222
- 00 at the beginning is called International Escape Code <IEC>
TK310v.1.5
28
29
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
TK310v.1.5
29
30
Number Portability
Number Portability
(NP)
TK310v.1.5
30
31
Number Portability (NP) Definitions

Number Portability is the ability of customers to
change from one Network Operator to another (in
the same country) while retaining the same
Directory Number (DN).
A Directory Number is the telephone number
entered when making a voice call or sending an
SMS to a customer.
TK310v.1.5
31
32
NP Definitions
The Network that the customer is leaving is called
the Donor network.
The Network that the customer is moving to is
called the Recipient or Subscription network
Only the Directory Number (DN) is portable.
Each operators NP solution is independent from
other operators, but it requires cooperation for
implementation.
TK310v.1.5
32
33
NP Environment Changes
When an MSU is sent in a Portability Environment
the originating switch can not determine which is
the owning subscription network just by analysing
the B-number. Routing of the signaling traffic to the
subscription network needs to be altered.
Routing changes are required.
In a Portability Environment, processes need to be

defined to share information between all the
operators in the country so that all operators
Number Portability DataBases (NPDB) can be
updated.
Provisioning changes are required.
TK310v.1.5
33
34
Routing Options
Indirect Routing
The network that originally owned the DN is responsible for
determining whether the called party has been ported and then
routing the call to the new subscription network.
Routing based on number ranges
NP database query for all terminating calls to own number ranges
NPDB contains all ported-in and ported-out numbers
Direct Routing
Direct routing from originating network to subscription network
NP database query for all Terminating calls to directory numbers in
that country
NPDB contains all ported numbers
TK310v.1.5
34
35
Routing Options
Partially Direct Routing
If the directory number is ported-out the originating
network performs the NPDB lookup and the MSU is routed
to the owner of that number range without a Routing
Number. The DN owner will then process the MSU using
Indirect Routing
If the DN is a ported-in number, the call setup process will
stay within the Originating network
NPDB will contain all ported-in and ported-out numbers
Reduces tromboning
The choice of which method will be used is normally

made by the regulator in each country.
TK310v.1.5
35
36
Regulator
The regulator in a country defines the routing
method that all the operators have to implement.
The regulator in a country also assigns a Routing
Number to each operator within the country.
Regulator
D11
Operator 1
D22
D33
Operator 2
Operator 3
Country xxx
TK310v.1.5
36
37
Number Portability Basic Message Call Flow

When an incoming MSU queries the Number
Portability Database there can be two basic
outcomes:
If the incoming DN is a Ported-In or a Non-Ported
number, a Signaling Point (SP) identification can be
added to the DN (SP+DN) and route to the next node.
If the incoming DN is a Ported-Out number, a Routing
Number identifying the DN owner can be added to the DN
(RN+DN). The MSU is then routed using the RN.
If no match, MSU can fall though and be routed by
regular GTT
TK310v.1.5
37
38
EAGLE NPDB Data Example: Not Ported DN

hubdtx0100w 08-11-04 16:30:01 EDT EAGLE5 39.2.0-61.32.0
rtrv-data-rtdb:dn=861234540000
EAGLE DB Command
Command entered at terminal #1.;
Card Loc : 1105
DN
861234540000
EntIdx1
H'00000006
Status: Coherent
Portability Type ( 0)
Not Known to be ported
EntIdx2
-------
Entity Address Type

25
SP
SRFIMSI
TK310v.1.5
Database location,
Directory Number and
Portability Type
Entity Address ID, Entity Type,

Point Code and Routing Indicator
PC(ANSI ) RI SSN TT NP NAI DA
001-002-003 GT 000 000 00 000 prefix
NSSN CCGT NTT NNP NNAI

no
no
no no
no
38
Extended Usage of Database Modules: NP
DN 861234540000, Signaling Point (SP) 25

DN belongs to this Service Provider
Database
Incoming MSU
Module
with the DN
861234540000
39
NP tables are down

loaded into the
memory of the
Database Modules
MSU (SP + DN) next network node

Outgoing number = 25861234540000
STP
TK310v.1.5
39
40
EAGLE NPDB Data Example: Ported DN

rtrv-data-rtdb:dn=861234560000
EAGLE DB Command
Command entered at terminal #1.;
Card Loc : 1105
DN
861234560000
EntIdx1
H'00000029
Status:Coherent
Portability Type ( 1)
Own Number ported out
EntIdx2
-------
Entity Address Type

30
RN
SRFIMSI
TK310v.1.5
Database location,
Directory Number and
Portability Type
Entity Address ID, Entity Type,

Point Code and Routing Indicator
PC(ANSI ) RI SSN TT NP NAI DA
001-002-003 GT 000 000 00 000 prefix
NSSN CCGT NTT NNP NNAI

no
no
no no
no
40
Extended Usage of Database Modules: NP
DN 861234560000, Routing Number (RN) 30

Ported to Operator X
Database
Incoming MSU
Module
with the DN
861234560000
41
NP tables are down

loaded into the
memory of the
Database Modules
MSU (RN + DN) goes to Operator X

Outgoing number = 30861234560000
STP
TK310v.1.5
41
42
Reminder: NP Data Flow Architecture

The NP data for the EAGLE Features resides within
the Real Time Database (RTDB) on the Service
Module Cards, such as the Database Service
Module (DSM) and the EAGLE 5 Service Module 4
GB (E5-SM4G) cards.
The Real Time Databases are provisioned by the
customers provisioning system via the EAGLE
Provisioning Application Processor (EPAP).
The data that resides within the RTDB is used for
incoming digit manipulation and message routing.
TK310v.1.5
42
43
Reminder: NP Data Flow Architecture

Provisioning System
Primary Write
Primary Read
Standby Write and Read
Redundant EPAP
Provisioning System
EPAPEPAP-A
RTDB
IGM
TIF
IDPR
A-Port
G-Port
G-Flex
EIR
GTT
EPAPEPAP-B
Auto-Synch DB
S
M
1
S
M
24
EAGLE 5
EPAPEPAP-A
RTDB
IGM
TIF
IDPR
A-Port
G-Port
G-Flex
EIR
GTT
EPAPEPAP-B
Auto-Synch DB
S
M
1
S
M
24
EAGLE 5
With its RTDB database architecture, the Eagle is able to support features such as;
IGM, TIF, IDPR, A-Port, G-Port, INP, G-Flex, EIR, and GTT.
It supports full replication of the NPDB in each DSM card and EPAP server. And for
routing options, the Eagle supports All Call Query, Query on Release, and Onward
Routing/Call Forwarding.
TK310v.1.5
43
44
Check Your Learning: Module 1

Answer the questions to the best of your ability.
We will review all answers as a group.
TK310v.1.5
44
1. The Global Title Address (GTA) contains what type of data?

a) Subsystem Number
b) Directory Number
c) Point Code
d) Dialed Digits
e) b and d only
f) All of the above
g) None of the above
2. List some of the different types of Nature of Address Indicators within the ITU Network.
3. List some of the different types of Numbering Plans within the ITU Network.
4. In Number Portability, the _______________________________ is the data used to

perform database queries.
5. If the incoming DN is a Ported-In or a Non-Ported number, the

_________________________ identification number can be added to the DN.
6. If the incoming DN is a Ported-Out number, a ___________________________

identifying the DN owner can be added to the DN.
TK310v.1.5
45
Student Notes
TK310v.1.5
46
Module 2
IGM Feature Defined
TK310v.1.5
47
48
Module 2
After this module of instruction, you should
be able to:
Define IS4 to GSM Migration (IGM) and its key benefits
List the general considerations for implementing IGM
Define migrated and non-migrated subscribers
Differentiate between call related and Short Message
Service (SMS) message handling
TK310v.1.5
48
49
IGM Defined
HLR
HLR
EAGLE
IS-41 Network
GSM Network
IGM
Database
MSC
MSC
The IGM feature provides the mobile wireless service provider a way to migrate
subscribers from IS-41 to GSM and GSM to IS-41. This is referred to as
Portability Type = 5 (PT=5).
It provides the ability for subscribers to change service providers while retaining
their Mobile Dialed Number (MDN).
IGM uses the EAGLE Provisioning Application Processor (EPAP) database (also
used by G-Port, INP, EIR, G-Flex, and the A-Port features) to maintain subscriber
portability/migration information.
Subscriber information in the EPAP database is keyed by Mobile Dialed Numbers
(MDN) for ANSI-41 subscribers and Mobile Station International ISDN Number
(MSISDNs) for GSM subscribers.
Based on the EAGLE 5 ISS platform, it is deployed in a node that is also performing
the STP function.
Once the subscriber is marked as migrated, the GSM handset is fully functional,
and the migrated subscriber has the option whether to continue to receive calls on
the IS-41 or GSM handset.
TK310v.1.5
49
50
Call Originated at GSM MSC for GSM Subscriber
GSM
HLR
2. SRI
EAGLE
IGM
Database
1. SRI
GSM
MSC
TK310v.1.5
50
51
Originated at TDMA MSC for GSM Subscriber

TDMA
HLR
GSM
HLR
5. SRI
(MSISDN))
EAGLE
2. LocReq
Return Response
(Prefix+MDN)
IGM
Database
1. LocReq
TDMA
MSC
TK310v.1.5
3. ISUP IAM
(Prefix+DN)
4. SRI
(Prefix+MSISDN))
GSM
MSC
51
Key Benefits of IGM
52
Support the migration without mandating changes

of subscribers phone numbers.
Allows the two different networks to interoperate
without tedious IS-41 to GSM MAP protocol
conversion
Support IntraCarrier Number Portability between
CDMA and GSM
TK310v.1.5
52
53
Requirements for IGM

EAGLE 5 ISS platform
IGM is deployed along with STP
MPS subsystem
EPAP database
HLR 1 HLR 2
Service Module cards
STP/
IGM
HLR 3
STP/
IGM
MSC
The MPS (Multi-Purpose Server) is a subsystem of the EAGLE 5 ISS. The MPS is composed of
hardware and software components that interact to create a secure and reliable platform. The
MPS provides the means of interfacing the customer provisioning application with the EAGLE. It
connects the customer with the EAGLE and accepts the customer migration data, while
accommodating numbers of varying lengths.
The EAGLE Provisioning Application Processor (EPAP) is software that runs on the MPS
hardware platform. It collects and organizes customer provisioning data and forwards it to the
EAGLE Service Module cards.
On the Eagle, a user can provision from 1 to 25 Service Module cards with the IGM feature. IGM
requires that all Service Module cards contain 4GB of memory. (Service Module Card refers to
either a DSM card or an E5-SM4G).
TK310v.1.5
53
54
Special Note: Service Module Features

1100 TPS Service Module Card Feature
26,400 transactions per second
(24 + 1 cards times 1100 = 26,400)
Service Module rates of 1100 TPS each
The MNP feature is enabled
E5-SM4G Throughput Capacity Feature
75,000 transactions per second
The GTT feature must be turned on
1100 TPS Service Module Cared Feature

Feature provides up to 26,400 transactions per second when the maximum
number of Service Module cards (25) are installed in the EAGLE and one or
more of the EPAP features, like IGM, is enabled and turned on.
The feature can only be enabled for Service Module cards that are rated at
1100 transactions per second.
The part number for this feature is 893018001
CAUTION: The increase of the Service Module card capacity, 1100 TPS per
Service Module card, assumes incoming traffic consists of at least 30% of
GTT routed traffic that does not require EPAP based lookup. If more than
70% of incoming traffic requires EPAP based lookup, the Group Ticket
Voucher (TVG) may shutdown and overall TVG capacity of 1100 TPS for the
card may not be met.
E5-SM4G Throughput Capacity Feature
This feature provides up to 75,000 transactions per second when the
maximum number of Service Module cards (25) are installed in the EAGLE
and an EPAP-related feature such as IGM is enabled and turned on.
The part number for this feature is 893019101
TK310v.1.5
54
55
IGM Considerations
GTT must be on before the IGM feature can be enabled.
IGM cannot be enabled if any TSM cards running the SCCP
application are in the system.
IGM is turned on, but not turned off, via the feature access key.
IGM, A-Port, G-Port, G-Flex features can run concurrently on an
EAGLE.
When IGM and G-Flex are on the same node, interactions between
the two features must be addressed.
IGM and North American Local Number Portability (LNP) are mutually
exclusive on an EAGLE.
TK310v.1.5
55
Subscriber Entries
56
Two types of subscriber entries, migrated and

non-migrated subscribers are supported.
Migrated:
- Migrated IS-41 subscribers who retain their IS-41 phone
number; or
- New GSM subscribers assigned with IS-41 numbers
Non-Migrated:
- Existing IS-41 subscribers who have not been migrated
NOTE: IGM treats only those DN entries assigned with the following as Migrated
subscribers:
SP and PT= 5
No NE and PT=5
RN and PT= 0
Any other types of NE/PT assignments are not considered as migrated or
ported subscribers.
Migration also supports DN block entries.
NE = Network Element
SP = Service Provider
RN = Routing Number
PT = Portability Type
TK310v.1.5
56
57
Signaling Relay Function (SRF)

IGM supports only the SRF-based solution for MNP.
Intercepts the existing MAP messages to check for
ported numbers. IGM acts as a NPHLR where the
number has been exported, by responding to the switch.
Call related message handling

For call related messages, IGM responds to the switch
with a SRI or LOCREQ ack messages.
Short Message handling

For SMS related messages, IGM responds to the switch
with SRI-SM or SMSREQ ack messages.
Non-Migrated calls
IGM performs message relay as per GTT results.
The European Technical Standards Institute (ETSI) standards are defined so that
GSM carriers can choose to implement either Signaling Relay Function (SRF)based (using MAP protocol) MNP or IN-based (using INAP protocol) MNP. IGM
supports only the SRF-based solution for MNP. (INAP-based MNP processing is
similar to wireline networks; this function is supported by the INP feature.)
SRF-based MNP processing involves the intercepting of existing MAP messages
to check for ported numbers.
For call-related messages, IGM acts as a NPHLR in the case where the number
has been exported, by responding to the switch with a SRI, SRI-SM, LOCREQ, and
SMSREQ ack messages. For non-migrated calls, IGM performs message relay.
SRI = Send Routing Information (GSM)
SIR-SM = SRI Short Message (GSM)
LOCREQ = Location Request Message (IS-41)
SMSREQ = SMS Request Message (IS-41)
MAP = Mobile Application Part
GTT = Global Title Translation
Ack = Data Acknowledgement
TK310v.1.5
57
Call Related Message Handling
58
Call Related Messages refer to MAP SRI or IS-41

LOCREQ message.
TK310v.1.5
Call-related messages
received from
Called party marked as
Actions taken by Eagle
GSM (MAP SRI)
Served by GSM
Relay call to its serving GSM HLR
GSM (MAP SRI)
Served by CDMA/TDMA
Reroute call to a IS-41 MSC
IS41 (IS-41 LOCREQ)
Served by GSM
Reroute call to a GSM MSC
IS41 (IS-41 LOCREQ)
Served by CDMA/TDMA
Relay call to its serving IS-41 HLR
58
59
Short Message Handling

Short Messages refer to IS41 SMSREQ or MAP SRI for
SM Message
Short Messages
Received from
Called Party Marked as
Actions Taken by
EAGLE 5
GSM SMSC (MAP

SRI_for SM)
Served by GSM
Relay call to its serving GSM HLR
GSM SMSC (MAP

SRI_for SM)
Served by CDMA/TDMA
Return NAK to GSM SMSC
IS41 SMSC (IS-41

SMSRequest)
IS41 SMSC (IS-41
SMSRequest)
Served by GSM
Return NAK to IS-41 SMSC
Served by CDMA/TDMA
Relay call to its serving IS-41 HLR
SMSC = Short Message Service Center

NAK = Negative Acknowledgement
TK310v.1.5
59
60
Number Lengths
Variance of number lengths
Between countries
Within a country
Maximum number length

15 digits
TK310v.1.5
Number lengths vary between countries and may even vary within a country. As
a result, the IGM Database structure supports numbers of varying length in a
flexible way without necessitating software modifications. A maximum number
length of 15 digits for ported numbers is supported.
60
61
IS412GSM Migration Changes

For systems that are upgraded to the IGM feature, the
upgrade process sets an SCCP option to on if the G-Port
feature is turned on and the IS412GSM prefix is defined. If
the G-Port feature is turned on and the IS412GSM prefix is
not defined, the upgrade process sets the SCCP option to
off. The default setting for new systems is off (disabled).
The EAGLE 5 ISS populates a new GSM2IS41 prefix
following the same mechanism that is used for the existing
IS412GSM prefix. The EAGLE 5 ISS returns a GSM2IS41
prefix in the SRI_ACK message if a received SRI message
is destined for a non-migrated IS41 or GSM migrated IS41
subscriber (a data entry is found with RN and PT=0).
TK310v.1.5
61
62
Check Your Learning Module 2

TK310v.1.5
62

1. One of the key benefits of IBM is support of Intra-carrier Number Portability
between _________ and GSM networks.
2. IGM utilizes the _________ database to derive the portability status of the
subscriber?
3. Subscriber information in the database is keyed by Mobile Dialed Numbers
(MDN). True or False
4. IGM and North American Local Number Portability (LNP) are mutually exclusive
on an EAGLE 5 ISS. True or False
5. Migrated subscribers can be defined as:
a. Migrated IS-41 subscribers who retain there is-41 phone number
b. New GSM subscribers assigned with IS-41 numbers
c. Both of the above
d. Neither of the above
6. For Short Message (SMS) messages, IGM responds to the switch with
_________ or ___________ ack messages.
TK310v.1.5
63
Student Notes
TK310v.1.5
64
Module 3
IGM Functions
TK310v.1.5
65
66
Module 3
able to:
Describe the main functions of IGM, including:
Message discrimination
Op-Code discrimination
Number Conditioning
RTDB lookup
Customer message processing
DigitAction Applications
TK310v.1.5
66
67
Message Discrimination
Eagle Service Module
IGM Conditioning
and Lookup in
RTDB table
yes
Service Selector
Table
SERV=MNP
no
GTT
no
MSU out to IMT
MSU in from IMT
Because IGM provides translation of migrated and non-migrated numbers, it

provides a method to identify which messages need migration handling versus GTT.
This task of identification is provided via a service selector table where the user
defines the service for a combination of selectors.
RTDB = Real Time Database
NOTE: The MNP service includes the IGM service.
TK310v.1.5
67
68
Op-Code Discrimination
IGM handles ANSI Loc_Req, SMSREQ, GSMSRI, and
SRI_SM differently than other ANSI/GSM operation codes.
The Portability type field is only considered for these
operation codes. Message relay is performed for all other
operation codes based on IGM Translation data.
TK310v.1.5
68
69
Number Conditioning
The RTDB stores International MSISDN only.
IGM provides the capability to condition incoming
numbers to be international MSISDN (Insert CC
or/and NDC) for the database look up.
IGM removes the GSM prefix from GSMSRI
messages and then conditions the non-international
numbers to international numbers, if needed, before
performing any database lookup.
TK310v.1.5
69
70
IS412GSM Prefix
IGM generates a Loc_Req Return Result
Response, when the MDN in the Loc_Req is a
"Migrated with one handset" subscriber.
When formulating a Loc_Req response, IGM uses
the IS412GSM prefix in GSMOPTS to build the
Routing Digits.
If the IS412GSM prefix is not provisioned, IGM
issues UIM 1130 LOCREQ rcvd - IS412GSM not
provisioned and falls through to GTT.
TK310v.1.5
70
71
GSM2IS41 Prefix
The GSM2IS41 prefix is used in the SRI-ack if
the message received is SRI and DN lookup has
RN and PT = 0 assigned.
If MIGRPFX = MULTPLE then the RN from the
RTDB is used as the prefix in the SRI-ack
message.
If MIGRPFX = SINGLE and GSM2IS41 prefix is
NONE, then the SRI-ack message issues UIM
1341 "SRI rcvd GSM2IS41 prefix not
provisioned" and the message falls through to
GTT.
TK310v.1.5
71
72
RTDB Lookup Using International MSISDN

The individual number database is searched first:
If the number is not found, the number range database is searched.
If a match is not found in the individual and range-based database,
the GTT is performed on the message.
In the event of the MSISDN numbers in the RTDB

database being odd and CdPAGTI of the incoming
message being 2, and the last digit of the number
is 'zero':
IGM first performs database lookup one time using the even number.
If no match is found, IGM again performs the database lookup, using
the odd number (without last digit).
Note that database lookup results in the following:

1. Applying normal routing or
2. Relaying the message to the destination as noted in the database or
3. Returning an acknowledge message to the originating switch.
TK310v.1.5
72
Student Notes
TK310v.1.5
73
74
Customer Message Processing

Since a DN may be the target of the A-Port, G-Port,
or IGM message processing in a hybrid network
(where an operator owns both GSM and IS41
network), message processing call disposition is
based on what applications are in service.
Call disposition for IGM Customer Processing is
seen on notes section of the next page.
Call disposition for the other configurations are seen
in tables located in the Database Lookup section of
the IGM Feature Description documentation.
Legend for next page:

PT = Portability Type for the DN
Values:
0 = not known to be ported
1 = own number ported out
2 = foreign number ported to foreign network
3 = prepaid 1 (used by PPSMS)
4 = prepaid 2 (used by PPSMS)
5 = migrated with one handset
RN = Routing Number
SP = Signaling Point
NE = Network Entity
TK310v.1.5
74
IGM Customer Message Processing

NE/PT
RN & PT = 0
SRI
MIGRPFX=
single: ACK
(use
GSM2IS41
prefix)
SRI_SM
Other
GSM
LOCREQ
SMSREQ
Other
IS41
SRI_SM_ACK
with Return
Error
Component
Relay
Relay
Relay
Relay
MIGRPFX=
multiple: ACK
(RN from
EPAP)
RN & PT 0
GTT
GTT
GTT
GTT
GTT
GTT
SP & PT = 5
Relay
Relay
Relay
ACK
(IS412GSM
prefix)
smsreq (SMS
Access Denied
Reason = 5)
Relay
GTT (if
smsreqbypass
=true
SP & PT 5
Relay
Relay
Relay
Relay
Relay
Relay
No NE & PT
=0
ACK (no NE)
GTT
GTT
GTT
GTT
GTT
No NE & PT
= 1, 2, or No
PT
GTT
GTT
GTT
GTT
GTT
GTT
No NE & PT
=5
GTT
GTT
GTT
ACK
(IS412GSM
prefix)
smsreq (SMS
Access Denied
Reason = 5)
GTT
GTT (if
smsreqbypass
=true
No DN entry
found
GTT
GTT
GTT
GTT
GTT
GTT
See previous page for legend.
TK310v.1.5
75
76
Message Relay - DigitAction Field

The rules for formatting the SCCP CdPA GTA field
are based on the value specified in the DigitAction
field.
When a received IS41 message is relayed, the
EAGLE formulates the SCCP CdPA GTA field of the
outgoing message according to the following.
If DigitAction = none
the EAGLE does not manipulate the SCCP CdPA GTA
If DigitAction = any other value

the EAGLE formats the SCCP CdPA GTA to the value
TK310v.1.5
76
77
DigitAction Applications
DigitAction
Value in Incoming
CdPA GTA
Value in Outgoing
CdPA GTA
Meaning
none
886944000213
886944000213
No change to the
CdPA GTA (default)
prefix
886944000213
1404886944000213
Prefix CdPA GTA

with the entity id
replace
886944000213
1404
Replace CdPA GTA

with the entity id
insert
886944000213
8861404944000213
Insert entity id after

country code (cc +
entity id + ndc + sn)
delccprefix
886944000213
1404944000213
Delete country code

and add prefix
delcc
886944000213
944000213
Delete country code
This table identifies the required DigitAction options as well as examples of how the SCCP CdPA
GTA of an outgoing message is formatted for each of the options.
The example assumes the RN/SP ID is 1404 and default country code is 886.
See Returning Acknowledge (encoding rules) on next page.
TK310v.1.5
77
The following encoding rules are followed when a LOCREQ ack is returned:
When a ACK/Response is returned, the EAGLE5ISS follows the LOCREQ
encoding rules along with the following enhancements for added flexibility
Allow users to specify which TCAP locreq parameter (a.k.a., the TCAP Outgoing
Called Party parameter) shall encode the RN (and/or DN) information
Allow users to specify the DigitType value to encode the TCAP Outgoing Called
Party parameter
Allow users to specify the value to encode the Nature of Number field of the
TCAP Outgoing Called Party parameter
Allow users to specify the value to encode the Numbering Plan field of the TCAP
Outgoing Called Party parameter
Allow users to specify the digit encoding format of the locreq TCAP Outgoing
Called Party parameter
Allow users to specify the MSCID values to be encoded in the locreq message
Allow users to specify the ESN values to be encoded in the locreq message
Allow users to specify how the digits of the locreq MIN parameter shall be
encoded.
:
The following encoding rules are followed when a SIR ack is returned:
When a SRI ack is returned, the EAGLE5ISS follows the SRI ack encoding rules
along with the following enhancements for added flexibility:
Allow users to specify which SRI parameter (the TCAPMSRN parameter)

encodes the RN (and/or DN) information
3Allow users to specify the value to encode the Nature of Address field of the
TCAPMSRN parameter
Allow users to specify the value to encode the Numbering Plan field of the
TCAPMSRN parameter.
TK310v.1.5
78
79

TK310v.1.5
79

1. The _________________________ table on the Service Module card identifies
which messages need migration handling versus GTT.
2. The RTDB stores only international MSISDN for IGM. True or False
3. The _____________________ prefix is used in the SRI-ack if the message
received is SRI and DN lookup has RN and PT = 0 assigned.
4. Portability Type (PT 5 for the DN indicates:
a. Not know to be ported
b. Foreign number ported to foreign network
c. Own number ported out
d. Migrated with one handset
5. IGM conditions incoming numbers to be MSISDN by inserting _____________
for the database look up.
a. Country Code
b. Translation Type
c. Subsystem Number
d. GTii
6. If the IS412GSM prefix is not provisioned, a specific UIM (1130) is issued and
the message falls through to GTT. True for False
TK310v.1.5
80
Module 4
IGM Feature Activation
TK310v.1.5
81
82
Module 4
able to:
Know the cautions and prerequisites of enabling the IGM
feature
List and describe steps for activating the IGM feature
Use available Eagle equipment and documentation to
configure the IGM feature
TK310v.1.5
82
83
CAUTION!
Do not attempt IGM activation in an in-service

environment. Call the Customer Care Center:
After the feature is turned on, it cannot be turned off.

Because features may overwrite other features or create changes in the database, ensure that you
have a license and full technical support before turning on this feature.
TK310v.1.5
83
84
In-Service Systems Considerations

Add during a maintenance window
Reboot Service Module cards one at a time
Verification of the cards in the IS-NR state
For in-service systems, schedule the Service Module replacement of TSMs in a maintenance window
that allows the reboot of Service module cards one at a time.
init-card: Loc=<service module card location>
Verify the cards return to the IS-NR state before initializing another Service Module card. This
precaution keeps cards in service and prevents an interruption of SCCP services.
SCCP traffic redundancy will be lost if inhibiting two TSM cards running the SCCP application at
a time with only one Service Module card available in their place. Redundancy will be reestablished after the two TSM cards running the SCCP application are replaced with a second
Service Module.
TK310v.1.5
84
Configuration Prerequisites
85
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
As the IGM feature sits on GTT feature, GTT must

be activated prior to IGM feature activation.
We presume GTT is already configured
We also presume the EAGLE Service Modules

running the VSCCP application have already been
installed and configured.
CAUTION: For an in-service environment, contact the Customer Care Center

before activating the IGM feature.
The IGM feature cannot be turned on if any of the Service Module cards have less
than 4 GB of memory installed.
CAUTION: After a feature has been turned on with the enable-ctrl-feat command,
the feature cannot be turned off. Because features may overwrite other features or
create changes in the database, confirm that you have a license and full technical
support from Tekelec before turning on this or any feature.
The IGM feature requires a Service Module card running the VSCCP application.
Systems with TSM cards running the SCCP application must be upgraded to 4 GB
Service Module cards prior to turning on the IGM feature.
TK310v.1.5
85
86
IGM Provisioning Commands

enable-ctrl-feat
chg-ctrl-feat
chg-stpopts
chg-gsmopts
chg-is41opts
ent-homern:rn=
ent-servsel
init-card
rept-stat-card
used to enable the IGM feature.

used to change values of one or more STP node
level processing option indicators.
used to change GSM- and IS41-specific options
and update associated tables.
used to enter any Home RNs that are prefixed to
DNs for incoming INPMR messages.
used to assign applicable service selectors.
used to reload a Service Module card and show
that service is restored.
chg-sccp-serv:
used to specify the name and state of the service.
rept-stat-sccp
rept-stat-mps
rept-stat-db
used to confirm IGM feature activation.
Each of the above commands for provisioning the IGM feature will be discussed in
this Module.
For more information, see the Migration Feature Manual and the Eagle Commands
Manual.
TK310v.1.5
86
Enable IGM Feature
87
As with all control features, IGM is activated by the

commands to enable and turn on the feature:
ENABLE-CTRL-FEAT:
PARTNUM=893017301:
FAK=<Feature Access Key>
CHG-CTRL-FEAT:
PARTNUM=893017301:
STATUS=ON
Use this command to enable a controlled feature that the customer has purchased.
In this case IGM.
NOTE : The IGM feature cannot be turned on until TSM cards running the SCCP
application are removed from the system.
Remember, contact Customer Care Center for assistance in conducting the IGM
activation procedure. Do not proceed without consulting with
Technical Services.
TK310v.1.5
87
Example: chg-stpopts
88
chg-stpopts:
defcc=
defndc=
dsmaud=
dpcfmti=
(Default country code)

(Default network destination code)
(Default DSM audit running state)
(ITU national point code identifier)
Use this command to change the values of one or more of the STP node level
processing option indicators maintained in the STPs options table. All values are
assigned initially to system defaults at STP installation time, and they may be
updated subsequently using this command.
Enter the default country code (CC) and default network destination code (NDC) to
convert the nature of address indicator (NAI) of MDNs to the international format
(nai=intl) with the chg-stpopts command.
Note the ITU National Point Code Format Identifier identifies how the ITU-N point
code is entered into the database and how it is displayed in all EAGLE 5 ISS
outputs. The code is a 14-bit integer.
TK310v.1.5
88
89
Example: rtrv-stpopts Output

rlghncxa03w 08-02-17 16:02:05 EST EAGLE 38.0.0
STP OPTIONS
--------------------------MTPT31CTL
1
MTPLTI
yes
MTPLTCTDPCQ
3
MTPLTST
10000
MTPDPCQ
2000
DEFCC
1
DEFNDC
38
DESAUD
on
TFATFRPR
1000
MTPLPRST
yes
MTPT10ALT
30000
UIMRD
yes
SLSCNV
perls
CRITALMINH
yes
DISPACTALMS
no
NPCFMTI
2-9-2-1
RPTLNPMRSS
yes
Verify the new country code and network destination code using the rtrv-stpopts
command.
NOTE: The options that appear in the actual output vary, depending on the features
that are enabled or turned on.
TK310v.1.5
89
Example: chg-gsmopts
90
chg-gsmopts:
srfnai
srfaddr
srfnp
is412gsm
gsm2is41
msrsndig
defmapvr
(defines NAI value of MNP_SRF)

(defines entity address of MNP_SRF node)
(defines NP value of the MNP_SRF)
(defines IS-41 to GSM migration prefix)
(defines GSM to IS-41 migration prefix)
(defines RN used or concatenated with the MDN)
(defines the default MAP version)
The chg-gsmopts command changes IGM-specific options in the database. This

command updates the GSMOPTS table. The default parameter values are always
overwritten when specified. Refer to the Commands Manual for details of this
command.
ccrndn Country code, routing number, and national directory number
TK310v.1.5
90
91
Example: rtrv-gsmopts Output

tekelecstp 08-05-05 14:05:45 EST EAGLE 39.0.0
GSM OPTIONS
----------------------SRFADDR = 23448
SRFNAI = 7
SRFNP = 15
DEFMAPVR = 2
MSRNDIG = RN
SRIDN = TCAP
IS412GSM = 34
MULTCC = 2
MULTCC = 4
MULTCC = 5
MULTCC = 20
MSRSNDIG = CCRNDN
MSISDNTRUNC = 0
MIGRPFX = SINGLE
GSM2IS41 = 34
The rtrv-gsmopts command displays the GSM option indicators maintained in the
GSMOPTS table
TK310v.1.5
91
Example: chg-is41opts
92
chg-is41opts:
rspcgpanai=7:
(defines new NAI value to override the NAI value

specified in the SCCPCdPA of a received
LOCREQ/SMSREQ if the message is to be relayed
after database lookup)
rspcgpanp=15:
(defines NP value of the MNP_SRF)
rspdig=ccrndn
(specifies digit encoding format of the LOCREQTCAP

Outgoing Called Party parameter on a per EAGLE
node basis)
The chg-is41opts command changes IS41-specific options in the database. This

command updates the IS41OPTS table. The default parameter values are always
overwritten when specified. Refer to the Commands Manual for details of this
command.
TK310v.1.5
92
93
Example: rtrv-is41opts Output

tekelecstp 08-04-15 12:49:20 EST EAGLE 39.0.0
IS41 OPTIONS
----------------------SMSREQBYPASS
= NO
LOCREQDN
= TCAP
RSPCDPAPCP
= OFF
RSPCGPANAI
=7
RSPCGPANP
= 15
RSPCGPATT
=0
MTPLOCREQNAI
= SUB
RSPPARM
= DDIGT
RSPDIG
= CCRNDN
RSPNON
=0
RSPNP
=0
ESNMFG
=0
ESNSN
=0
RSPDIGTYPE
=0
LOCREQRMHRN
= NO
TCAPSNAI
= SUB
MTPLOCREQLEN
= 15
The rtrv-is41opts command displays the IS41 option indicators maintained in the
IS41OPTS table.
TK310v.1.5
93
Example: ent-homern & rtrv-homern

ent-homern:rn=
94
(rn = the home number prefix)
rtrv-homern
rlghncxa03w 03-03-28 08:50:12 EST EAGLE 31.3.0
RN
--------------216780909087654
76345098
abc
abc1234
c10234567
cabade
HOMERN table is (6 of 100) 6% full
NOTE: The INP feature or the G-Port feature must be turned on, or the TINP
feature must be enabled before this command can be entered.
TK310v.1.5
94
Student Notes
TK310v.1.5
95
Example: ent-srvsel
96
ent-srvsel:
gtii=1:4
tt=1
snp=e164
snai=intl
serv=mnp
nai=intl
np=e164
ssn=9
(specifies GTT indicator)

(specifies translation type)
(defines service numbering plan)
(specifies intl. Service Nature of Address)
(specifies the service feature)
(specifies the nature of address indicator)
(specifies numbering plan)
(defines subsystem number
Use this command to assign the applicable service selectors required to specify a
service entry for DSM services.
TK310v.1.5
96
97
Example: rtrv-srvsel Output

rtrv-srvsel:gtii=2
rtrv-srvsel:gtii=4
rlghncxa03w 01-03-28 00:29:31 GMT EAGLE 36.0.0
GTII TT NP NAI NPV NAIV SNP SNAI SERV
2
0 e164 intl ----- e164 intl gport
2
1 e164 intl ----- e164 intl gport
rlghncxa03w 01-03-28 00:29:31 GMT EAGLE 36.0.0
GTII TT NP NAI NPV NAIV SNP SNAI SERV
4
0 e164 intl --- --e164 intl mnp
4
1 e164 intl --- --e164 intl gport
Use this command to display a list of administered service selector combinations.

NOTE: The rtrv-srvsel operation may be lengthy because the service selector
table can contain over 1,000 entries.
The list can be filtered using various parameter combinations as seen above.
TK310v.1.5
97
98
Example: init-card
You would now need to reload a Service Module card using
this command.
init-card:loc=
Use the following to show that service is successfully restored.
rept-stat-card:loc=
The output should show DSM VSCCP IS-NR.
You would now need to repeat for each Service Module card.
CAUTION: When you have an in-service environment and you are replacing TSM
cards with Service Module cards, initialize one Service Module card at a time. Verify
its return to IS-NR state before initializing another Service Module card. This
precaution keeps cards in service and precludes an interruption of SCCP services.
GTT, EGTT, and VGTT traffic are routed based on the global titles in the OAM
database while G-Flex, IGM, and INP traffic is routed based on the global title in the
RTDB. Rebooting a Service Module card running the VSCCP application causes
both the OAM and RTDB databases on the Service Module card to reload.
TK310v.1.5
98
99
Example: chg-sccp-serv
chg-sccp-serv:
serv=mnp
state=online
TK310v.1.5
(specifies the name of the service)

(specifies the state of the service, offline or
online. Note that re-routing is performed
when the service state is offline.)
99
100
Confirming IGM Feature Activation

Use rept-stat-sccp to verify all your Service Module cards
are loaded and are IS-NR (in-service normal) status.
Use rept-stat-mps to verify all your Service Module cards
and the EPAP are connected and operational.
Use rept-stat-db:display=all to verify database levels are
identical for the EPAPPDB and RTDB and the RTDBs on the
Service Module cards.
The IGM feature should now be installed, activated, and
ready for operations.
TK310v.1.5
100
101
Learning Activity: Module 4
Learning Activities
Learning Activity: IGM Activation

Purpose
To provide practical application on the steps and commands needed to provision and validate the
IGM 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 IGM service; to recognize the step and commands needed to
provision the IGM service on the EAGLE STP; and to use EAGLE commands to validate the
successful completion of IGM service activation.
Materials, Equipment, and References

EAGLE STP connected to the MPS/EPAP
EAGLE Commands Manuals:
Commands Manual
Feature Migration Manual
Instruction (s):
Follow directions for Student Assignments A and B.
Stop after each assignment, and let the instructor review your work.
TK310v.1.5
101
Learning Activity: Module 4

Student Assignment A:
Using the parameter input values below, write out the EAGLE commands needed to active the
IGM Feature.
When completed, STOP and allow the instructor to verify your work.
PARAMETERS
INPUT VALUES
Feature(s) Part Number(s)
See Instructor
Feature(s) Access Key(s)
See Instructor
Routing Number
34
Routing number to be used as is or to be

concatenated with the MDM
Country code, routing number and national

directory number
Default MAP Version
SRF Address
23448
SRF Nature Address Indicator
SRF Number Plan
15
Default Network Destination Code
38
ITU National Point Code Format
2-9-21
Digit encoding format of the LOCREQTCAP outgoing

called party parameter
NAI to override the NAI value specified in the

SCCPDdPA of a received LOCREQ/SMSREQ
Default Country Code
DSM Audit running state
ON
Global Title Indicator
ITU
Translation Type
Subsystem Number
Number Plan
e164
International
Service Numbering Plan
e164
Service Nature of Address Indicator
Land Mobile Numbering Plan
Service
MNP
TK310v.1.5
102
Student Assignment B:
Where applicable, use the data from Assignment A and provision an EAGLE STP
for IGM activation.
When completed, STOP and allow the instructor to verify your work.
TK310v.1.5
103
Student Notes
TK310v.1.5
104
Module 5
Additional Features
TK310v.1.5
105
106
Module 5
able to:
Describe the function and steps for activating these
additional features:
TK310v.1.5
Circular Route Prevention

MNP SCCP Service Re-Route Capability
MTP Msgs for SCCP Apps
MO-Based IS41-to-GSM Migration
106
107
TK310v.1.5
107
108
MNP Circular Route Prevention

Originating Network A
Network B
HLRA
HLRB
EAGLE
MNP
EAGLE
MNP
MSCA
MSCB
MNPCRP is an extension of IGM
This feature helps in cases of circular routing caused by incorrect information in one or more of
the network number portability databases. It is enabled and turned on using the Feature Access
Key commands.
Subscriber ports from Network A to Network B.
Network A has the correct routing information, indicating that the subscriber now belongs to
Network B.
Network B has incorrect routing information, indicating that the subscriber still belongs to
Network A.
Network A routes the call to Network B, but Network B routes the call back to Network A.
This results in a circular route.
The MNPCRP feature provides logic to prevent this scenario.
TK310v.1.5
108
109
Enable Circular Route Prevention

Note that this is a control feature and is
activated using the following:
ENABLE-CTRL-FEAT:
PARTNUM=8930077001:
CHG-CTRL-FEAT:
PARTNUM=8930077001:
STATUS=ON
TK310v.1.5
109
110
SCCP Service Re-Route Capability
MNP SCCP Service Re-Route

Capability
TK310v.1.5
110
111
SCCP Service Re-Route Capability

Need
If the MNP database is incoherent with MPS data and the
GTT data is valid, the EAGLE MNP node needs to be
able to handle and control re-routing of IGM traffic from
an affected node to alternate nodes within an operators
network.
Solution
The SCCP Service Re-Route feature provides the
capability to re-route traffic from the EAGLE to other MNP
database nodes and inform the originating nodes to reroute the service related traffic to other MNP service
nodes.
TK310v.1.5
111
112
SCCP Service Re-Route Capability Functions

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

The use of MNP capability point code aids in notifying adjacent nodes
about MNP service outages.
TK310v.1.5
112
113
Re-Route Capability Provisioning

chg-sccp-serv:
serv=mnp:
pci1=1-1-1:
rc1=10:
pci2=2-2-2:
rc2=10:
pci3=3-3-3:
rc3=10:
pci4=4-4-4:
rc4=10
(specifies service)
(adds PCs to existing service group)
(changes relative cost of existing PC group)
Once provisioned, the MNP service can be changed to OFFLINE.

chg-sccp-serv:serv=mnp:state=offline
Define alternate point codes to re-route MNP traffic. Up to 7 alternate MNP nodes
can be provisioned to re-route all the incoming MNP traffic.
TK310v.1.5
113
114
MNP Capability Point Codes

Capability Point Codes are supported for MNP
Allows the adjacent nodes to know about MNP
outages
MNP supports the following PC types:
-
ANSI
ITU-I
ITUN14
ITUN spare
ITU-I spare
ITUN24
When MNP is taken offline through administrative commands, all traffic destined to that MNP
node will result in a Transfer Prohibited (TFP) message being sent to the adjacent node about
the MNP CPC.
The TFP message to the adjacent node causes the traffic originating nodes to stop sending MNP
traffic to the node.
All MNP traffic coming into this node is sent to the alternate MNP nodes.
Adjacent nodes will initiate route-set-test procedures after receipt of the TFP response.
TK310v.1.5
114
115
MTP-Routed SCCP Traffic for IGM
MTP Msgs for SCCP Apps

Feature
TK310v.1.5
115
116
MTP-Routed SCCP Traffic for IGM

MTP Msgs for SCCP Apps Feature
IGM supports MTP-routed SCCP & LOCREQ messages.
This feature can not be turned on unless IGM is on.
This feature adversely affects the message capacity as all of these
messages are counted under SCCP capacity.
MTP Routing
If the MTP-routed messages have CdPA = 0 and IGM is turned on, message
is sent for IGM processing. If MNP service is offline, MTP routing is
performed.
If the MTP routed messages have CDPAGTI 0, then SRVSEL lookup is
performed using the SCCP CDPA information. If the result of the lookup is
MNP service, the message is sent to MNP handling. If a service selector is
not defined or does not match, or if the service is OFFLINE, then MTP
routing is performed on the messages. The MNP SCCP Service re-route is
not performed on MTP routed messages.
After this feature is turned on, all SCCP messages are routed to the TSM cards running the SCCP
application. The TSM card running the SCCP application then performs SCCP
decode/verification. If the MTP routed messages have CDPAGTI = 0 and IGM is turned on, then
the message is sent for IGM processing. If MNP service is OFFLINE, then MTP routing is
performed on the messages.
If the MTP routed messages have CDPAGTI 0, then SRVSEL lookup is performed using the SCCP
CDPA information. If the result of the lookup is MNP service, the message is sent to MNP
handling. If a service selector is not defined or does not match, or if the service is OFFLINE, then
MTP routing is performed on the messages.
The MNP SCCP Service re-route is not performed on MTP routed messages.
MNP checks to see if the TCAP portion of the message is ITU or ANSI. If the message has ITUTCAP
then normal routing (or G-Flex if provisioned) is performed on the message. If the message has
ANSITCAP then, IGM general TCAP/MAP verification is performed if A-Port or IGM is turned on.
SMS Address conversion is not affected by the MTP Msgs for SCCP Apps feature; SMS conversion
handles only Registration Notification and SMS Notification messages.
A feature access key (FAK) for part number 893017401 is required to enable the MTP Msgs for
SCCP Apps feature.
TK310v.1.5
116
Student Notes
TK310v.1.5
117
118
Message Flow MTP Msgs for SCCP Apps Feature
1. The EAGLE receives the MSU.

2. The MSU is sent to the SCCP function.
3. The DSM card examines the MSU for a LOCREQ message.
4. The digits are encoded from TCAP or SCCP layer
5. IGM is applied to the digits to determine if the subscriber is migrated. If so, a LOCREQ Return
result is generated to the OPC. If not, the LOCREQ is routed.
6. If the message is not a LOCREQ, ANSI SMS Address Conversion is applied. SMS Address
conversion feature does not have any impact on this feature because SMS conversion handles
only Registration Notification and SMS Notification messages.
7. The MSU is routed. MTP and SCCP conversion are performed if crossing a network boundary.
TK310v.1.5
118
MTP Routed Handling Example:

IGM is ON, A-Port, G-Port, and G-Flex are OFF. SERV=MNP or GTI=0
NE/PT
SRI
SRI_SM
Other
GSM
LOCREQ
SMSREQ
Other
IS41
RN & PT = 0
MTP
routing
MTP
routing
MTP
routing
Relay
MTP
routing
MTP
routing
RN & PT 0
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
SP & PT = 5
MTP
routing
MTP
routing
MTP
routing
ACK
(IS412GSM
prefix)
MTP
routing
MTP
routing
SP & PT 5
MTP
routing
MTP
routing
MTP
routing
Relay
MTP
routing
MTP
routing
No NE & PT
=0
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
No NE & PT
= 1, 2, or No
PT
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
No NE & PT
=5
MTP
routing
MTP
routing
MTP
routing
ACK
(IS412GSM
prefix)
MTP
routing
MTP
routing
No DN entry
found
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
MTP
routing
Note that additional examples are included in the Migration Feature Manual
TK310v.1.5
119
120
Enable MTP MSGS for SCCP Apps Feature

Note that this is a control feature and is
activated using the following:
ENABLE-CTRL-FEAT:
PARTNUM=893017401:
CHG-CTRL-FEAT:
PARTNUM=893017401:
STATUS=ON
TK310v.1.5
120
121
MO SMS IS41-to-GSM Migration
MO SMS = Mobile Originated Short Message Service
TK310v.1.5
121
122
Introduction to MO SMS
The Mobile Originated Short Message Service (MO SMS) features
address the number portability requirements of wireless network
operators for delivery of Mobile Originated SMS messages in a number
portability environment for GSM and IS41 and in the IS41-to-GSM
Migration environment
The EAGLE 5 ISS MO SMS features apply number portability database
lookup to SMS messages for IS41 and GSM networks:
Mobile Originated Based GSM SMS Number Portability Mobile
Originated Based IS41 SMS Number Portability
Mobile Originated SMS IS41-to-GSM Migration
The MO SMS features are all based on the EAGLE 5 ISS platform with
EPAP.
TK310v.1.5
122
123

This feature provides network information to the Short
Message Service Center (SMSC) for subscribers using the
IS41 network.
The information allows the SMSC to select a protocol to
deliver Short Message Service Delivery Point-to Point
(SMDPP) messages to the called party.
The SMSC uses the DN porting information to determine
whether to forward the message to other operators or to
process the message for an in-network subscriber.
This feature applies to ANSI TCAP/MAP and ANSI or ITU
transport (MTP and SCCP) messages.
For more information see the following manual from the EAGLE documentation
DVD, Feature MO SMS.
TK310v.1.5
123
124
How it works
TK310v.1.5
Intercepts
Intercepts SMS messages before they reach the

Home Short Message Service Center (SMSC)
Decodes
Decodes the TCAP/MAP message destination

address and performs lookup in the Real-time
Database (RTDB)
Modifies
Modifies the destination address in the TCAP

message with DN (dialed number) porting
information or the IS412GSM Migration Prefix
Relays
Relays the SMS message to its original

destination
124
125
Feature Control
This feature has the following control requirements:
TK310v.1.5
A FAK for part number 893-0262-01

The feature cannot be enabled if the LNP feature is enabled.
A temporary FAK cannot be used to enable the feature.
The feature cannot be turned off after if has been turned on.
125
126
Feature Activation
enable-ctrl-feat
ent-srvsel
chg-stpopts
chg-is41smsopts
chg-ctrl-feat
TK310v.1.5
Command to enable the MO SMS IS41-to-GSM Migration
feature.
Command to assign the service selector with service
feature serv=smsmr.
Command to enter default country code (CC) and default network
destination code (NDC) if handling non-international numbers.
Command to change the values of one or more of the feature
option indicators maintained in the SMS Options table.
Commands to turn on this feature
126
127
enable-ctrl-feat
enable-ctrl-feat
ent-srvsel
To enable the MO SMS IS41-to-GSM feature
enable-ctrl-feat:partnum=893019501:fak=xxxxxxxxxxxx
chg-stpopts
Part Number for

the this Feature
chg-is41smsopts
Feature Access
Key for this
Feature
chg-ctrl-feat
The command, rtrv-ctrl-feat, can be used to verify that the feature is enabled.
TK310v.1.5
127
128
ent-srvsel
enable-ctrl-feat
ent-srvsel
This command assigns applicable

service selectors required to specify
the service entry for Service Module
services.
chg-stpopts
Example:
chg-is41smsopts
chg-ctrl-feat
Parameters of the
MSU trigger
entsrvsel
:gtia=2:tt=0:nai=intl:np=e164:ssn=255
:snp=e164:snai=intl:serv=smsmr
To specify how the service
has to process the number
Service triggered if all

the previous parameters
matches the MSU
Use this command to enter the MO SMS IS41-to-GSM feature service selectors by network type. This
command assigns applicable service selectors required to specify the service entry for Service Module
services.
Service Selector Parameters:

:gtia - Specifies the global title translation indicator (2 = ANSI, ITU; 4 = ITU)
:tt - Specifies the translation type.
:snp - Defines the service numbering plan (e164, e212, or e214).
:snai - Specifies the international Service Nature of Address Indicator.
:serv - Specifies the service feature. This must be set to smsmr for this feature
:nai - Specifies the nature of address indicator.
:np - Specifies the numbering plan.
:ssn - Defines the subsystem number.
For details on all parameters, refer to the Commands Manual.
chg-srvsel: - Use this command to specify the applicable A-Port selectors required to change an existing A-Port
selector entry.
dlt-srvsel: - Use this command to delete an A-Port service selector.
TK310v.1.5
128
129
chg-stpopts
To provision STP default System Options
enable-ctrl-feat
chg-stpopts:defcc=49:defndc=177
ent-srvsel
Used to identify the CC and the NDC of

the number and/or to condition the
number to an international format before
the RTDB lookup
chg-stpopts
chg-is41smsopts
chg-ctrl-feat
:defcc= (optional) Default country code.

Range: 1-3 digits , none
Valid digits are 0-9, A-F, a-f.
noneDeletes the current value.
defndc= (optional) Default network destination code.
Range: 1-5 digits , none
Valid digits are 0-9, A-F, a-f.
noneDeletes the current value.
Default: Current value
TK310v.1.5
129
130
chg-is41smsopts
enable-ctrl-feat
ent-srvsel
chg-stpopts
This command is used to change

the IS41 SMS options in the
database for this feature.
Specifies that the MO
Example:
Specifies the format
of a dialed number.
SMS IS41-to-GSM
Migration prefix
chg-is41smsopts
chg-is41opts:mosmsdnfmt=rndn:moigmpfx=is412gsm
:mosmsnai=nat:modaparam=da
chg-ctrl-feat
Indicates how the called party

number will be conditioned
before lookup in the database.
Specifies whether the

SMS DA or ODA from the
IS41 SMDPP message is
used for conditioning,
lookup, and modification
The systems options (IS41smsopts) commands are used to change and report on the values of one or more of the STP
node level processing option indicators maintained in the IS41 SMS option tables.
All values are assigned initially to system defaults at STP installation time.
The chg-is41smsopts command changes IS41 SMS specific options in the database and updates the IS41 SMS opts
table.
DA = Destination Address
ODA = Original Destination Address
Refer to the Commands Manual for details of all parameter.
TK310v.1.5
130
131
System Options for MO SMS IS41-to-GSM Migration Feature

IS41SMSOPTS
Parameter
Range
Description
mosmsnai
intl, nai, nat, unknown
MO-Based SMS nature of

address indicator
mosmsdnfmt
rn, rndn, ccrndn
MO-Based SMS directory

number format
moigmpfx
ne, is412gsm
Migration feature uses

NE associated with B
number or is412gsm as a
prefix to modify the
destination address in the
outgoing SMDPP
modaparam
da, oda
Specifies which address

(DA or ODA) is used for
conditioning, lookup, &
modification
chg-is41smsopts command is used to update the is41smsopts table.

The default parameters are always overwritten when specified.
TK310v.1.5
131
132
Retrieve MO-Based IS41 SMS NP Options
rtrv-is41smsopts
tekelecstp 09-01-16 10:33:44 EST EAGLE 40.0.0.
IS41 SMS OPTIONS
----------------------MOSMSNAI = NAT
MOSMSDIGMAT = EXACT
MOSMSDNFMT = RDDN
MOIGMPFX = IS412GSM
MOSMSDNNAI = NONE
MODAPARAM = da
This is the output from the EAGLE when you retrieve the options
with the feature enabled
Use the command, rtrv-is41smsopts, to obtain the existing values of the is41smsopts table.
TK310v.1.5
132
133
chg-ctrl-feat
enable-ctrl-feat
To enable the MO SMS IS41-to-GSM Migration
ent-srvsel
chg-stpopts
chg-ctrl-feat:partnum=893019501:status=on
chg-is41opts
The operational status
of the feature (on or off)
chg-sccp-serv
chg-ctrl-feat
This command is used to turn on the MO SMS IS41-to-GSM Migration Feature

After the feature is on, it cannot be turned off.
The command, rtrv-ctrl-feat, can be used to verify that the feature is enabled
and turned on.
TK310v.1.5
133
134

TK310v.1.5
134

1. List the basic commands and parameters to enable a control feature.
2. With the SCCP Service Re-Rout Capability, if alternate point codes are not
provisioned or none are available, then messages destined for MNP will:
a. fall through to GTT
b. be re-routed to an alternate PC
c.
be re-routed to a CPC
d. be re-routed to a different HLR

3. Once provisioned, the MNP service can be changed to OFFLINE using what
command?
4. The SCCP Service re-rout is not performed on ________ routed messages.
5. The MO SMS IS41-to-GSM Migration feature provides network information to
the Short Message Center for subscribers using the IS41 network. True or
False
6. The MO SMS IS41-to-GSM Migration feature can not be enabled if the _______
feature is enabled.
TK310v.1.5
135
136
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!
TK310v.1.5
136
Appendix A
ANSI-41 and GSM Operation

Codes (Op Codes)
TK310v.1.5
137
ANSI-41 MAP Operations

Bit Value
Decimal Value
00000001
01
Handoff Measurement Request
00000010
02
Facilities Directive
00000011
03
Mobile On Channel
00000100
04
Handoff Back
00000101
05
Facilities Release
00000110
06
Qualification Request
00000111
07
Qualification Directive
00001000
08
Blocking
00001001
09
Unblocking
00001010
10
Reset Circuit
00001011
11
Trunk Test
00001100
12
Trunk Test Disconnect
00001101
13
Registration Notification
00001110
14
Registration Cancellation
00001111
15
Location Request
00010000
16
Routing Request
00010001
17
Feature Request
00010100
20
Unreliable Roamer Data Directive
00010110
22
MS Inactive
00010111
23
Transfer To Number Request
00011000
24
Redirection Request
00011001
25
Handoff To Third
00011010
26
Flash Request
00011011
27
Authentication Directive
00011100
28
Authentication Request
TK310v.1.5
Description
138
ANSI-41 MAP Operations

Bit Value
Decimal Value
Description
00011101
29
Base Station Challenge
00011110
30
Authentication Failure Report
00011111
31
Count Request
00100000
32
Inter System Page
00100001
33
Unsolicited Response
00100010
34
Bulk Deregistration
00100011
35
Handoff Measurement Request 2
00100100
36
Facilities Directive 2
00100101
37
Handoff Back 2
00100110
38
Handoff To Third 2
00100111
39
Authentication Directive Forward
00101000
40
Authentication Status Report
00101010
42
Information Directive
00101011
43
Information Forward
00101100
44
Inter System Answer
00101101
45
Inter System Page2
00101110
46
Inter System Setup
00101111
47
Origination Request
00110000
48
Random Variable Request
00110001
49
Redirection Directive
00110010
50
Remote User Interaction Directive
00110011
51
SMS Delivery Backward
00110100
52
SMS Delivery Forward
00110101
53
SMS Delivery Point To Point
00110110
54
SMS Notification
00110111
55
SMS Request
TK310v.1.5
139
GSM Operation Codes

Bit Value
Decimal Value
Description
00000010
Update Location
00000011
Cancel Location
00000100
Provide Roaming Number
00000110
Resume Call Handling
00000111
Insert Subscriber Data
00001000
Delete Subscriber Data
00001001
Send Parameters
00001010
10
Register SS
00001011
11
Erase SS
00001100
12
Activate SS
00001101
13
Deactivate SS
00001110
14
Interrogate SS
00010001
17
Register Password
00010010
18
Get Password
00010011
19
Process Unstructured SS Data
00010110
22
Send Routing Information
00010111
23
Update GPRS Location
00011000
24
Send Routing Information for GPRS
00011001
25
Failure Report
00011010
26
Note Ms Present for GPRS
00011100
28
Perform Handover
00011101
29
Send End Signal
00011110
30
Perform Subsequent Handover
00011111
31
Provide SIWFS Number
00100000
32
SIWFS Signaling Modify
00100001
33
Process Access Signaling
00100010
34
Forward Access Signaling
00100011
35
Note Internal Handover
00100101
37
Reset
00100110
38
Forward Check SS-Indication
00100111
39
Prepare Group Call
00101000
40
Send Group Call End Signal
TK310v.1.5
140
GSM Operation Codes

Bit Value
Decimal Value
00101001
41
00101010
42
00101011
43
00101100
44
00101101
45
00101110
46
00101111
47
00110000
48
00110001
49
00110010
50
00110011
51
00110100
52
00110110
54
00110111
55
00111000
56
00111001
57
00111010
58
00111011
59
00111100
60
00111101
61
00111111
63
01000000
64
01000010
66
01000011
67
01000100
68
01000101
69
01000110
70
01000111
71
01001000
72
01001001
73
01001010
74
01001011
75
01001100
76
01001101
77
TK310v.1.5
Description
Process Group Call Signaling
Forward Group Call Signaling
Check IMEI
MT Forward
Send Routing Information for SM
Forward SM
Report SM-Delivery Status
Note Subscriber Present
Alert SC Without Result
Activate Trace Mode
Deactivate Trace Mode
Trace Subscriber Activity
Begin Subscriber Activity
Send Identification
Send Authentication Information
Restore Data
Send IMSI
Process Unstructured SS Request
Unstructured SS-Request
Unstructured SS-Notify
Inform Service Centre
Alert Service Centre
Ready for SM
Purge SM
Prepare Handover
Prepare Subsequent Handover
Provide Subscriber Information
Any Time Interrogation
SS Invocation Notification
Set Reporting State
Status Report
Remote User Free
Register CC-Entry
Erase CC-Entry
141

TK310 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TK310 PDF

Uploaded by

Copyright:

Available Formats

TK310

EAGLE 5 ISS Release 40 / EPAP 12

IS41 GSM Migrations (IGM)

TEKELEC Confidential For Training Purposes Only

Module 5 Additional Features..105

TEKELEC Confidential For Training Purposes Only

Class Time and Breaks

TEKELEC Confidential For Training Purposes Only

Training Strategies and Materials

Student Training Guide

Tekelec Product Documentation

TEKELEC Confidential For Training Purposes Only

TEKELEC Confidential For Training Purposes Only

TEKELEC Confidential For Training Purposes Only

Number Portability Review

TEKELEC Confidential For Training Purposes Only

TEKELEC Confidential For Training Purposes Only

Message Signalling Unit

Message Signalling Unit

TEKELEC Confidential For Training Purposes Only

SS7/CCS7 Signal Units

Fill In Signal Unit

Link Status Signal Unit

Message Signal Unit

TEKELEC Confidential For Training Purposes Only

SS7/CCS7 Signal Unit Fields

Fill-In-Signal Unit (FISU)

TEKELEC Confidential For Training Purposes Only

Message Signal Unit (MSU) Structure

TEKELEC Confidential For Training Purposes Only

MSU Fields used in GTT

Message Signal Unit

TEKELEC Confidential For Training Purposes Only

Signaling Information Field - Routing Label

TEKELEC Confidential For Training Purposes Only

ANSI SIF Address Indicator

Subsystem Number indicator - value of 0 or 1

TEKELEC Confidential For Training Purposes Only

ANSI Signaling Information Field (CDPA)

Global Title Translation

GTI =2(tt & digits)

TEKELEC Confidential For Training Purposes Only

CDPA Format (ANSI)

CDPA Length indicator

1 - route on DPC + SSN

Global Title indicator

2 - Global title includes tt, digits

Point Code indicator

0 - address does not contain a point code

1- the address contains a SSN

Global title address information

TEKELEC Confidential For Training Purposes Only

ITU SIF Address Indicator

Point Code indicator - value of 0 or 1

TEKELEC Confidential For Training Purposes Only

ITU Signaling Information Field (CDPA)

Binary Coded Decimal

TEKELEC Confidential For Training Purposes Only

CDPA Format (ITU)

CDPA Length indicator

1 - route on DPC + SSN

Global title indicator