TK302_Eagle R45.0 EPAP R15.0_V6.0

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

1/261

For Training Purposes Only1 I Tekelec. For Whats Next.

This document is for informational purposes only, and Tekelec reserves the right to change any aspect of the products, features

or functionality described in this document without notice. Please contact Tekelec for additional information and updates. Built on Training template 7.0.

Number Portability for GSM (G-Port)

TK302

EAGLE 5 ISS R45.0/EPAP R15.0

Version 6.0

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

2/261


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

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

3/261


Student Guide Layout

In this guide, you will find the following structure:

Large units of learning are called Modules. A Module isdivided into smaller units of learning called Lessons

Each module consists of:

Module objectives or lesson titles for each lesson

One or more lessons

Each lesson consists of:

Lesson Objectives

Lesson content presentation

Check-Your-Learning review questions

Hands-on learning activities (most lessons)

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

4/261


Course Objectives

After this course, you should be able to:

Describe G-Port and its relevance to mobile numberportability

Use the EAGLE 5 ISS commands for G-Port provisioning

Activate the G-Port feature and its options

Describe additional features associated with G-Port

Locate additional detailed information in the Tekelec User

Documentation libraries used in this course.

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

5/261




Number Portability OverviewModule 1

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

6/261


This Module contains the following lessons:

Lesson 1 GSM Network Non Portability Environment

Lesson 2 What is Portability?

Number Portability Overview

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

7/261

For Training Purposes Only11 I Tekelec. For Whats Next.This document is for informational purposes only, and Tekelec reserves the right to change any aspect of the products, featuresor functionality described in this document without notice. Please contact Tekelec for additional information and updates. Built on Training template 7.0.

GSM Network Non Portability Environment

Module 1

Lesson 1

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

8/261


Lesson Objectives

After this Lesson, you should be able to:

Identify and interpret basic GSM terminology

Identify the purpose, function and contents of Number

Plans and Nature of Address Indicator

Describe simplified call flows within a non-portability

environment

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

9/261


Basic GSM Knowledge

Basic GSM Knowledge

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

10/261


IMSI & 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 with either one or several

MSISDNs

HLR

An HLR stores IMSI numbers and their

associated MSISDN numbers

The HLR also contains subscriber profile

information and the number of the lastVLR where this subscriber was

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

11/261


Numbering Plan (NP)

The numbering plan value in the MSU is used to indicate how

a number is structured

Like GTT, the G-Port feature 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 ofthe CDPA

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

12/261


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 exchangedbetween the two SS7 nodes and the configuration of the

nodes, the appropriate NP is then selected.

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

13/261


Numbering Plan (NP) E.212 & E.164

E.212: This is the IMSINumbering Plan

E.164: This is the MSISDN

Numbering Plan

CC NDC SN

National (Significant) Number1 to 3

Maximum of 15 Digits

E.164 (International)

MCC MNC MSIN

National MSI

1 to 3



1 to 4

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

14/261


Numbering Plan (NP) E.214

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

E.212

1 to 3



E.164

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

15/261


Numbering Plan (NP) E.214 Converted Example

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

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

16/261


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-Port feature 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 theCDPA

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

17/261



In ITU, there are three types of NAI:

International National

Subscriber

Depending on the level of transaction exchanged between twoSS7 nodes and the configuration of the nodes, the appropriate

NAI is then selected

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

18/261



E.164

CC + NDC + SN (International)- 99 70 22222222222

NDC + SN (National)

- 70 22222222222

SN (Subscriber)- 22222222222

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

19/261



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

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

20/261


Call Flows

Call Flows without Portability

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

21/261


Call Related Call Flow (Simplified)

The originating network analyzes the B-number (called party) and

thus determines its subscription network

The subscription network uses SRI dialogue to route the call to the

VMSC where the subscriber is currently attached

Example: 99611111111 calling 99622222222

Originating network Subscription networkof 99622222222

ISUP IAM

SRI99611111111

Visited network99622222222

ISUP IAM

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

22/261


Call Related Call Flow (Simplified)

GMSC MSC/

VLR2

MSC/

VLR1

Mobile A Mobile B

BSSAP ISUP MAP MAP BSSAP

CALL

IAM

CALLIAM

SRI

SRI Ack

PRN

PRN Ack

END CALLREL

RELEND CALL

ISUP

HLR

Originating network Subscription network Visited network

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

23/261


Non-Call Related Call Flow (Simplified)

SMSC MSC/

VLR2

MSC/

VLR1

Mobile A Mobile B

BSSAP MAP MAP MAP BSSAP

SM

MO - FSM

SM

MT - FSM

SRI for SM

SRI for SM Ack

MAP

HLR

Originating network Subscription network Visited network

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

24/261


Learning Activities

Learning Activity

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

25/261


Check Your Learning

Answer the questions to the best of your ability.

We will review all answers as a group.

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

26/261


What is Portability?

Module 1

Lesson 2

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

27/261


Lesson Objectives

After this lesson, you should be able to: :

Describe the purpose and functions of Mobile NumberPortability (MNP)

Identify MNP environment changes

Identify different routing options for MNP

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

28/261


Mobile Number Portability

Mobile Number Portability (MNP)

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

29/261


Three Types of Number Portability

Service Provider Portability

Keep the same phone number while switching from one operator toanother

Service Portability

Keep the same number when changing one type network to another

(e.g., GSM TDMA/CDMA or VoIP TDM)

Keep the same phone number when switching from one service to

another service provided by the same carrier

Location Portability

Keep the same phone number when moving from one physical

location to another

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

30/261


Key Network Elements in an NP Domain

NPDB

NPDB

SRI

SRI

Calling

Subscriber

Originat ing

Network

Donor

Network

Called

Subscriber

Subscr ip t ion

NetworkCalled

Subscriber

STP/

G-Port

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

31/261


MNP Environment Changes

The originating switch can not determine which is the owning

subscription network just by analysing the B-number. Routing

of the signalling traffic to the subscription network needs to

be altered.

Routing changes required

Processes need to be defined to share information between

all the operators in the country so that all operators Number

Portability Database (NPDB) can be updated.

Provisioning changes required

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

32/261


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 subscriptionnetwork.

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

Partially Direct Routing

If the directory number is ported-out the originating network performs the NPDBlookup and the MSU is routed to the owner of that number range without aRouting 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 theOriginating network

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

33/261


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.

Country xxx

Operator 1 Operator 2 Operator 3

D11D22

D33

Regulator

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

34/261


Check Your Learning



8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

35/261


GSM Portability (G-Port) Architecture

Module 2

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

36/261


Objectives

After this module you should be able to:

State the purpose of the G-Port function Describe which Message Signaling Units (MSU) are affected

by G-Port

Describe MSU data extraction for the G-Port feature

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

37/261


G-Port

G-Port is a Service Provider Portability for GSM networks

G-Port is a Triggerless Application; hence, no upgrade is

required in existing HLR/MSC/VLR to support MNP

G-Port sits on GTT, so GTT is required

G-Port examines MAP messages already flowing in the

network for Number Portability lookup

If no match is found, the MAP message falls thru to GTT and is

processed as before MNP

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

38/261


G-Port Architecture

G-Port is deployed along with STP

STP/

G-Port

MSC

HLR 2HLR 1 HLR 3

STP/

G-Port

STP/

G-Port

MSC

HLR 2HLR 1 HLR 3

STP/

G-Port

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

39/261


Which MSU are affected by G-Port?

A Directory Number (DN) can be: Non-Ported (own DN still subscriber of the operator)

Ported-Out (an exported DN lost by an operator)

Ported-In (an imported DN gained by an operator)

Foreign DN ported to foreign operator (Only on Direct routing)

Call flows can be: Call related with MAP Protocol

- G-Port acts as a Message Relay for Ported-Inand Non-PortedDN

- G-Port acts as a NP HLR for Ported-OutDN and Foreign DN

Non-Call related with MAP Protocol

- G-Port acts as a Message Relay in al l c ases

G-Port can work by extracting the DN from the SCCPlayer or MAP layer (But only for call related scenario)

G f O

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

40/261


G-Port for Ported-Out DNs

G-Port for Ported-Out DNs with

information extracted from SCCP

E l D t

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

41/261


Example Data

A country (CC=99) with 3 operators

Operator 1

- Own range of number: 99610000000-99619999999

- Routing Number: d11

Operator 2- Own range of number: 99620000000-99629999999


Operator 3- Own range of number: 99630000000-99639999999


G P t P t d O t C ll Fl E l

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

42/261


G-Port Ported-Out Call Flow Example

Originating networkOperator 1

Donor networkOperator 2

Subscription network

Operator 3

NPDB

NPDBSRI

99622222222

Direct Routing

Call FlowExample

3-0-0

STP/

G-Port

SRI9962000000

9962200000

G P t P t d O t C ll Fl SRI Q

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

43/261


G-Port Ported-Out Call Flow : SRI Query

G-PORT

Eagle STP

RTDB

GTT

CGPA CDPA

SCCP Fields

MAP Parameters

MAP Fields

Address Indicator

GTI =4

RI =0

NI =0

SSN=1

PC=0

SSN=6

NP=E164

NAI=INTL

Digits=9962222

MSU TRANSMISSION DIRECTION

GMSC

SRI sent by the GMSC to the STP

GTT is required

An HLR is requested

Operation Code = 22

.

SRI MAP

Message

G P t P t d O t C ll Fl S i S l t T bl

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

44/261


G-Port Ported-Out Call Flow: Service Selector Table

When GTT is requested, the MSU is sent to the Database

Module and the service selector table is looked up first.

EAGLE Service Module

Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

Selector

Table

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G P t P t d O t C ll Fl S i S l t T bl

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

45/261


Address Indicator

GTI =4

RI =0 (GTT

required)

NI =0

SSN=1

PC=0

SSN=6 (SSN of

HLR)

TT=0

NP=E164

NAI=INTL

Digits=99622228

G-Port Ported-Out Call Flow : Service Selector Table

Fields extracted from the CDPA by the EAGLE.

Parameters

extracted

from the

CDPA to finda match in

Service

Selectors

Table.

CGPA CDPA

SCCP Fields

EAGLE Service Selectors Table contains:GTIN=4:SSN=6:TT=0: NP=E164: NAI=INTL:SNP=E164:

SNAI=CCRNDN: SERV=GPORT

(G-PORT Service is tr igg ered)

If CDPA parameters match the Service Selector

Table, the MSU is sent to the provisioned service.

G P t P t d O t C ll Fl N C diti i & L k

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

46/261


G-Port Ported-Out Call Flow: No. Conditioning & Lookup

G-Port service has been triggered

The DN is conditioned if needed before RTDB lookup


Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

SelectorTable

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G P t P t d O t C ll Fl N C diti i & L k

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

47/261


G-Port Ported-Out Call Flow : No. Conditioning & Lookup

GTA extracted from the CdPA is used to

perform the RTDB lookup

The RTDB stores international MSISDNs

only. When G-Port is required and the

number is not international, number

conditioning is triggered.

Number Conditioning

For a National (Significant) Number, the

received CdPA/MAP MSISDN digits areprepended with the default country code

For a Subscriber Number, the CdPA/MAP

MSISDN digits are prepended with the default

country code and the default network code.

Address Indicator

GTI =4

RI =0 (GTT

required)

NI =0

SSN=1PC=0

SSN=12 (SSN of

STP)

TT=0

NP=E164

NAI=INTL

Digits=99622228

CGPA CDPA

SCCP Fields

G P t P t d O t C ll Fl GTA P i

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

48/261


G-Port Ported-Out Call Flow: GTA Processing

Depending on the value of the SNP and SNAI fields previously

found in the service selector table when G-Port has beentriggered, the G-Port service knows how to process the GTA

As SNP=E164 and SNAI=CCRNDN, G-Port first tries to identify the

CC by finding a match with the value of the parameter DEFCC from

the table STPOPTS.

- In this example DEFCC=99

Then G-Port tries to locate the RN after the CC by finding a match

with the parameter RN in the table HOMERN

- In this example RN=d22 and G-Port doesnt find a match with the RN

configured, so G-Port processes the DN as CC+DN

G Port Ported Out Call Flow: MSISDN Extraction

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

49/261


G-Port Ported-Out Call Flow: MSISDN Extraction

When the DN has to be extracted from the MSISDN portion

of MAP layer (SRIDN=TCAP in the GSMOPTS table), the

SNAI parameter defined in the service selector table is not

used,

The treatment of the number is depended on the NAI of the

MSISDN portion (SUB, NATL, INTL)

The conditioning of the DN prior to the RTDB lookup is the

same as with SCCP; remove the RN if necessary and

convert to international if needed:

If NAI=INTL, G-Port process the DN as CC+RN+DN

Otherwise, G-Port considers it is RN+DN

G Port Ported Out Call Flow: RTDB Lookup

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

50/261


G-Port Ported-Out Call Flow: RTDB Lookup

After number conditioning, the RTDB lookup is performed to

try to find the CCDN number

RTDB Database

DN 99622222222, RN d33

EAGLE Database Module This DN hasbeen ported-out

with RN d33.

This result is

used to build the

MSRN into the

MSU before to

route it to the

next node

G-PORT

Eagle

STP

RTDB

GTT

G Port Ported Out Call Flow: SRI ACK Response

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

51/261


G-Port Ported-Out Call Flow: SRI ACK Response

G-Port has found a RN associated to this DN


Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

SelectorTable

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G Port Ported Out Call Flow: SRI ACK Response

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

52/261


G-Port Ported-Out Call Flow: SRI ACK Response

G-Port builds the SRI-ACK message with the lookup

results Invert OPC and DPC fields

Build the SCCP layer

- Copy the incoming CGPA into CDPA

- Put in CGPA the EAGLE STP E.164 number, NP and NAI as configured inthe GSMOPTS table

Build the MAP layer (Only in call related scenario)

- G-Port builds the Roaming Number with

The RN found in the RTDB for this DN (d33)

The parameters MSRNDIG, MSRNNP, and MSRNNAI from the GSMOPTS tableinto the EAGLE STP

G Port Ported Out Call Flow: SRI ACK Response Contents

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

53/261


Address Indicator

GTI =4

RI =0 (GTTrequired)

NI =0

SSN=1

PC=0

SSN=8

TT=0

NP=E164

NAI=INTL

Digits=9962000

G-PORT

Eagle STP

RTDB

GTT

CDPA CGPA

SCCP Fields Roaming Number

MAP Fields

G-Port Ported-Out Call Flow: SRI-ACK Response Contents


GMSC

SRI-Ack Response from STP to GMSC

GMSC is requested

Operator 2 GMSC

E.164 No.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

54/261


Address Indicator

GTI =4

RI =0 (GTTrequired)

NI =0

SSN=1

PC=0

SSN=8

TT=0

NP=E164

NAI=INTL

Digits=9962000

ATINP

Eagle

STP

RTDB

GTT

CDPA CGPA

SCCP Fields MAP Parameters

MAP Fields

Address Indicator

GTI=4

RI =0

NI =0

SSN=1

PC=0

SSN=6

NP=164

NAI=INTL

Digits=9962200

..



GMSC

SRI-Ack Response from STP to GMSC

From an HLR

From SRFADDR parameter

From SRFNP parameter

From SRFNAI parameter


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

55/261


Address Indicator

GTI =4

RI =0NI =0

SSN=1

PC=0

SSN=8

TT=0

NP=E164

NAI=INTL

Digits=9962000

ATINP

Eagle

STP

RTDB

GTT

CDPA CGPA

SCCP Fields MAP Parameters

MAP Fields

Address Indicator

GTI=4

RI =0NI =0

SSN=1

PC=0

SSN=6

NP=164

NAI=INTL

Digits=9962200

..



GMSC

SRI-ACK Response from STP to GMSC

NAI= INTL

NP=E164

Roaming NO = 99d3362

Number formatted

according the

MSRNDIG

parameter: CCRNDN

Come from the

parameter

MSRNNAI if filled

Come from the

parameter

MSRNNP if filled

Optional SRI ACK Functions

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

56/261


Optional SRI ACK Functions

CUG Parameter in SRI Ack Messages

Option to SuppressNumberPortabilityStatusIndicator in SRI Ack


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

57/261



The Include Optional CUG Parameter in SRI Ack Messagesfunctionality

allows an existing Closed User Group-CheckInfo (CUG-CheckInfo)parameter in an incoming SRI message to be included in the outgoingSRI Ack message.

controlled by the encodecug option of the chg-gsmopts command offand on parameters.

off/on parameter can be changed only if the G-Port or IGM feature is

enabled.

The CUG-CheckInfo parameter in an incoming SRI message iscopied in the original sequence to the outgoing SRI Ack messagewhen these conditions are met:

The encodecug option of the chg-gsmopts command is set to on. The CUG-CheckInfo parameter is present in an incoming SRI

message.

The CUG-CheckInfo parameter in an incoming SRI message isencoded in definite length format that is less than or equal to 30 bytes.

Suppress NumberPortabilityStatusIndicator in SRI ADK

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

58/261


Suppress NumberPortabilityStatusIndicator in SRI ADK

Option to Suppress NumberPortabilityStatusIndicator

in SRI Ack functionality allows the Number PortabilityStatus Indicator (NPSI) to be omitted from all SRI Ack

messages.

This functionality is controlled by the encodenps option ofthe chg-gsmopts command off and on parameters.

The encodenps off/on parameter can be changed only if the G-Port

or IGM feature is enabled. The default setting is on.

The NumberPortabilityStatusIndicator parameter is not encoded in

any SRI Ack message if the encodenps option of the chg-gsmoptscommand is set to off.

G-Port Call Flow for Ported-In DNs

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

59/261


G-Port Call Flow for Ported-In DNs

G-Port Call Flow

Direct Routing for Ported-In DNs withdata extracted from SCCP layer

G-Port Ported-In Call Flow

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

60/261


G-Port Ported-In Call Flow

Originating network

Operator 1


Operator 2

ISUP IAM

Donor network

Operator 3

NPDB

NPDB

SRI

Call Related

example

99633333333

STP/

G-Port

G-Port Ported-In Call Flow: IAM

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

61/261


G-Port Ported-In Call Flow: IAM

Directory Number: 99633333333

IAM sent by

Operator 1

A-Num B-NumISUP Fields

TRANSMISSION DIRECTION

GMSC

99d22633333333

Operator 1 looks up NPDB as the number belongs to

its range and sees that this DN has been ported to

Operator 2 -> sends MSU to Operator 2 with RN


Operator 2

STP/

G-Port

G-Port Ported-In Call Flow: SRI Query

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

62/261


G Port Ported In Call Flow: SRI Query

G-PORT

Eagle STP

RTDB

GTT

CGPA CDPA

SCCP Fields

Address Indicator

GTI =4

RI =0

NI =0

SSN=1

PC=0

SSN=6

NP=E164

NAI=INTL

Digits=99d2263


GMSC

SRI sent by the GMSC to the STP

GTT is required

An HLR is requested

G-Port Ported-In Call Flow: Service Selector Table

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

63/261


G Port Ported In Call Flow: Service Selector Table


Module and the service selector table is looked up first.


Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

SelectorTable

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G-Port Ported-In Call Flow: Service Selector Table

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

64/261


Address Indicator

GTI =4

RI =0 (GTT

required)

NI =0SSN=1

PC=0

SSN=6 (SSN of

HLR)

TT=0

NP=E164

NAI=INTL

Digits=99d2263

G Port Ported In Call Flow: Service Selector Table


Parameters

extracted

from the


Service

Selectors

Table.

CGPA CDPA

SCCP Fields

EAGLE Service Selectors Table contains:

GTIN=4:SSN=6:TT=0: NP=E164: NAI=INTL:SNP=E164:


(G-PORT Service is tr igg ered)



G-Port Ported-In Call Flow: No. Conditioning & Lookup

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

65/261


G Port Ported In Call Flow: No. Conditioning & Lookup

G-Port service has been triggered

The DN is conditioned if needed before RTDB lookup


Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

SelectorTable

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G-Port Ported-In Call Flow: No. Conditioning & Lookup

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

66/261


G Port Ported In Call Flow: No. Conditioning & Lookup

As the parameter SRIDN from the GSMOPTStable is set to SCCP, the DN (GTA) isextracted from the CDPA by G-Port

GTA extracted from the CdPA is used toperform the RTDB lookup

The RTDB stores international MSISDNs only.When G-Port is required and the number isnot international, number conditioning istriggered.

Number Conditioning

For a National (Significant) Number, the receivedCdPA/MAP MSISDN digits are prepended with thedefault country code

For a Subscriber Number, the CdPA/MAPMSISDN digits are prepended with the defaultcountry code and the default network code.

Address Indicator

GTI =4

RI =0 (GTT

required)

NI =0

SSN=1

PC=0

SSN=12 (SSN of

STP)

TT=0

NP=E164

NAI=INTL

Digits=99622228

CGPA CDPA

SCCP Fields

G-Port Ported-In Call Flow: GTA Processing

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

67/261


G Port Ported In Call Flow: GTA Processing

Depending on the value of the SNP and SNAI fields previously

found in the service selector table when G-Port has been

triggered, the G-Port service knows how to process the GTA

As SNP=E164 and SNAI=CCRNDN, G-Port first tries to identify the

CC by finding a match with the value of the parameter DEFCC from

the table STPOPTS.

- In this example DEFCC=99

Then G-Port tries to locate the RN after the CC by finding a match

with the parameter RN in the table HOMERN

- In this example RN=d22 and G-Port doesnt find a match with the RN

configured, so G-Port processes the DN as CC+DN

G-Port Ported-In Call Flow: RTDB Lookup

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

68/261


G Port Ported In Call Flow: RTDB Lookup

After number conditioning, the RTDB lookup is performed to

try to find the CCDN number

G-PORT

Eagle

STP

RTDB

GTT

RTDB Database contains:

DN 99633333333, SP A01

PC 2000da prefix

This DN is ported-inand its related data

can be found in the

HLR with the id A01.

RTDB also contains

the PC of this HLR

which will be used

as DPC into the

MSU.

How to format the

GTA into the CDPA

G-Port Ported-In Call Flow: Route Message

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

69/261


G Port Ported In Call Flow: Route Message

G-Port has found an SP associated to this DN.

Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

Selector

Table

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G-Port Ported-In Call Flow: SRI Query Contents

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

70/261


.

OPC= STP

DPC = 2000

Address Indicator

GTI =4

RI =1

NI =0

SSN=1

PC=0

SSN=6

TT=0

NP=E164

NAI=INTL

Digits=A019963

CDPA CGPA

SCCP Fields.

Routing Label

MTP3 Fields

G o t o ted Ca o S Que y Co te ts


SRI Routed by the STP to the HLR

Remove RN and prefix

with SP ID into the CDPA

HLRG-PORTEagle

STP

RTDB

GTT

.

G-Port Ported-In Call Flow: SRI-Ack Contents

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

71/261


.

OPC= HLR

DPC = GMSC

Address Indicator

GTI =4

RI =0

NI =0

SSN=1

PC=0

SSN=8

TT=0

NP=E164

NAI=INTL

Digits=9962000

CDPA CGPA

SCCP Fields.

Routing Label

MTP3 Fields


SRI-ACK Routed by the HLR to the STP

MSC is requested

HLRG-PORT

Eagle

STP

RTDB

GTT

.

GTT is required

G-Port Ported-In Call Flow: SRI-Ack Routing

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

72/261


g


Module and the service selector table is looked up first


Yes

G-PORT

conditioning

and RTDB

lookup

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

SelectorTable

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G-Port Ported-In Call Flow: SRI-Ack Routing

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

73/261


Address Indicator

GTI =4

RI =0 (GTT

required)

NI =0SSN=1

PC=0

SSN=8

TT=0

NP=E164NAI=INTL

Digits=9962000

g


Parameters

extracted

from the


Service

Selectors

Table.

CGPA CDPA

SCCP Fields

EAGLE Service Selectors Table contains:

GTIN=4:SSN=6:TT=0: NP=E164: NAI=INTL:SNP=E164:


.

No match found with theextracted parameters



G-Port Ported-In Call Flow: GTT Routing

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

74/261


g

MSU fall thru GTT

EAGLE Service ModuleG-Port

conditioning

and lookup into

RTDB table

Yes

No

Generate

ACK Using

RN

Yes (RN)

Yes (SP)

Send Ack

No

Service

Selector

Table

MSU out to IMT

Update

CDPA &

MTP3

GTT

Route

Message

MSU in from IMT

G-Port Non-Call Related Examples

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

75/261


p

Non-Call related

Examples with an SMSC sends aSRI for SM

G-Port Non-Call Related

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

76/261


Everything works in the same way as the call related call flow,

except that the STP/G-Port node will never send a MAP SRI-

ACK message instead of the HLR to the GMSC.

The message will always be relayed to an HLR or another network

with the RN (MNP-SRF behavior).

The DN is always extracted from the CDPA (=GTA).

G-Port does the discrimination between call related and non-

call related MAP messages with the Operation Code

information. SRI = Call Related

Non-SRI = Non-Call Related

G-Port Non-Call Related: Ported-Out SCCP

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

77/261


SRI for SM3-0-0

Originating network

Operator 1 Donor networkOperator 2

SRI for SM


Operator 3

STP/

G-Port

NPDB

NPDB

99622222222Non-CallRelated

example

MSC/VLR

SMSC

SRI for SM Ack

SRI for SM

MT-FSM

G-Port Non-Call Related: Ported-In SCCP Message

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

78/261


g

Originating network

Operator 1Subscription network

Operator 2

SRI for SM

Donor network

Operator 3

NPDB

NPDB

SRI for SM

Non-CallRelated

example

99633333333

STP/G-Port

SMSC

SRI for SM Ack

MT-FSM

G-Port Measurements

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

79/261


G-Port Measurements

EAGLE Measurements

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

80/261


EAGLE measurements provide support for:

STP performance management

SS7 traffic monitoring and engineering

Specific feature performance analysis

Measurements can by collected and reported with thefollowing collection methods:

OAM Based Measurements

Measurements Platform

E5-OAM Integrated Measurements

Primary Functions of Measurements

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

81/261


The primary functions of Measurements are as follows:

Collection

- Measurements are collected in 5-minute, 30-minute, and 60-minute

intervals. An option exists for

- the default 30-minute measurements to be collected every 15 minutes.

Many 30-minute

- measurements intervals are accumulated into daily intervals. Storage

- Measurements are stored in dedicated RAM tables and/or disks after

collection. Most are retained

- for 24 hours. Measurements for some features (LNP, INP, G-Port, MAP

Screening, EIR, and VFLEX)

- are retained for 7 days.

Primary Functions of Measurements (continue)

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

82/261


The primary functions of Measurements are as follows:

Retrieval

- Measurements data is retrieved from the RAM storage area and/or disk.

ACTIVE measurement

- data is retrieved and reported from the application cards except for SCP

SMCs. Registers collected from SCP SMCs are not supported for ACTIVE

measurements and will be reported as zero in an

- ACTIVE measurement report. An ACTIVE linkset report requires all links

in the linkset to be available in order to provide the report.

Reporting

- Measurement reports are available on-demand/scheduled

Measurement Categories and Report Types

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

83/261


Traffic Engineering Reports STP Systems Totals (SYSTOT)

Component Measurements (COMP) Network Management (NM)

Error Tracking/Troubleshooting Reports Daily Availability (AVLD)

Day-to-Hour Availability (AVLDTH)

Availability (AVL) Daily Maintenance Reports

Hourly Maintenance Measurements (MTCH)

Daily Maintenance Measurements (MTCD)

Day-to-Hour Maintenance Measurements (MTCDTH)

Network Usage Reports Gateway (GTWY)

Record Base (RBASE)

Maintenance Status Reports Maintenance Status Indicators (MTCS)

Measurement Report Characteristics

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

84/261


tekelecstp 11-02-23 18:36:15 EST Rel XX.X

TYPE OF REPORT: NETWORK MANAGEMENT MEASUREMENTS ON LNKSET

REPORT PERIOD: LAST

REPORT INTERVAL: 11-02-23, 18:30:00 THROUGH 18:34:59

LNKSET-NM MEASUREMENTS: lsn XXXX

These measurements are from 11-02-23, 18:30:00 through 18:34:59.

OCTRAN = 974080 OCTRECVD = 954624

MSUTRAN = 15220 MSURECVD = 14916

System

Information

Report

Type

Report

Interval

Collected

Data

Measurement Documentation Layout

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

85/261


Event Name Description Unit

CRSYSAL Number of Critical System Alarms - The total peg count

number of critical system alarms

GTTPERFD GTTs Performed - The total number of MSUs peg count

that successfully completed global title

translation (GTT)

LNKAVALT Link Available Time - The total time the link was seconds

available to MTP level 3

TRMSUOCT Terminated MSU Octets - The total number of octets octets

associated with incoming MSUs carrying the STP

point code in the DPC. Includes octets removed in

the MTP level 2 processing.

NOTE: Units can be listed as peg counts, seconds, mil l iseconds, or octets.

Measurement Information & Procedures

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

86/261


Detailed information and procedures on measurements can befound in:

EAGLE 5 ISS Measurements Manual- information about measurement systems and reporting.

EAGLE 5 ISS Commands Manual

- descriptions of commands used to generate, schedule, and transfer

measurements reports.

Database Administration Manual

- System Management for provisioning information and procedures for thefollowing measurement systems:

OAM-based Measurements - G-Port measurements are available using the FileTransfer Area (FTA)feature and not directly by EAGLE 5 ISS terminals.

Measurements Platform

E5-OAM Integrated Measurements

G-Port Measurements: NP MTCD Report

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

87/261


NP MTCD Report

The daily GPORT measurements specify the entity type NP

(enttype=np) which generates two separate reports per period.

These reports for OAM based measurements are generated toCSV files in the FTA.

The command example will generate the following dailyreports:

- Daily System Wide Measurements

- Daily Measurements Per SSP

Command Examples

OAM- rept-meas:type=mtcd:enttype=np:period=specific:day=xxx

MP and E5-OAM

- rept-ftp-meas:type=mtcd:enttype=np[:period=specific:day=xxx]

G-Port Measurements: NP MTCH Report

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

88/261


NP MTCH Report

The hourly GPORT measurements specify the entity type NP

(enttype=np) which generates two separate reports per period.

The command example will generate the following hourly reports:

- Hourly System Wide Measurements

- Hourly Measurements Per SSP

Command Examples

OAM

- rept-meas:type=mtch:enttype=np:period=specific:day=xxx

MP and E5-OAM

- rept-ftp-meas:type=mtch:enttype=np[:period=specific:day=xxx]

G-Port Measurements: Per System and Per SSP

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

89/261


Event Name Description Type Unit

GPSRACK Number of call-related SRI ack messages. Peg count counts

for register GPSRACKPP are not included in this register.

Point Code Peg

countGPSRNACK Number of call-related SRI negative ack messages in

successful G-Port service

Point Code Peg

count

GPSRRLY Number of call-related SRI messages relayed Point Code Pegcount

GPNOCL Number of non-call-related messages relayed byG-Port System,Point Code

Peg

count

GPNOCLGT Number of non-call-related messages that fell through toGTT

System,

Point Code

Peg

count

GPSRSMREP Number of SRI_SM messages that result in SRI_SM_ACKor SRI_SM_NACK responses

System,

Point Code

Peg

count

GPSRSMERR Number of SRI_SM messages that result in error System,Point Code

Peg

count

GPSRSMRCV Number of SRI_SM messages received System,Point Code

Peg

count

MNPCRD Number of times Circular Route is detected System,Point Code

Peg

count

G-Port Measurements: Per System and Per SSP

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

90/261



GPSRRCV Number of call-related SRI messages received. Peg counts for registerGPSRRCVPP are not included in this register.

System Peg

count

GPSRGTT Number of call-related SRI messages that fellthrough to GTT. Peg counts for register

GPSRGTTPP are not included in this register.

System Peg

count

GPSRREP Number of call-related SRI messages that received G-Port service. Pegcounts for register

GPSRREPPP are not included in this register.

System Peg

count

GPSRERR Number of call-related messages that cause SRI negative ackmessages because of G-Port service failure. Peg counts for registerGPSRERRPP are not included in this register

System Peg

count

GPNOCL Number of non-call-related messages relayed byG-Port System,Point Code

Peg

count

GPNOCLGT Number of non-call-related messages that fell through to GTT System,Point Code

Peg

count

GPSRSMREP Number of SRI_SM messages that result in SRI_SM_ACK orSRI_SM_NACK responses System,Point Code Pegcount

GPSRSMERR Number of SRI_SM messages that result in error System,Point Code

Peg

count

GPSRSMRCV Number of SRI_SM messages received System,Point Code

Peg

count

MNPCRD Number of times Circular Route is detected System,

Point Code

Peg

count

G-Port SRI Query for Prepaid Measurements

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

91/261



GPSRACKPP Number of call-related SRI ack messages for G-Port

SRI Query for Prepaid feature. Peg counts for registerGPSRACK are not included in this register.

Point Code Peg

count

GPSRGTTPP Number of call-related SRI messages that fell throughto GTT for G-Port SRI Query for Prepaid GPSRGTTPP

feature. Peg counts for register GPSRGTT are not

included in this register.

System Peg

count

GPSRRCVPP Number of call-related SRI messages received for G-

Port SRI Query for Prepaid feature. Peg counts forregister GPSRRCV are not included in this register.

System Peg

count

GPSRERRPP Number of call-related messages that cause SRInegative ack messages for G-Port SRI Query for

Prepaid feature. Peg counts for register GPSRERR are

not included in this register.

System Peg

count

GPSRREPPPNumber of call-related SRI messages that received G-

Port service for G-Port SRI Query for Prepaid feature.

Peg counts for register GPSRREP are not included in

this register.

System Peg

count

G-Port Measurements: MTCD & MTCDTH

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

92/261


The following measurement events are included on the STP

Daily Maintenance (MTCD) and STP Day-to-Hour (MTCDTH)

measurement reports and include peg counts for G-PortMSUs.

MSSCCPFL - MSUs discarded due to SCCP routing failure.

GTTUN0NS - GTT unable to perform; no such type

GTTUN1NT - GTT unable to perform: no translation on this address

GTTPERFD - Total number of GTT performed

Learning Activity

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

93/261


Learning Activities

Check Your Learning

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

94/261




8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

95/261




G-Port Configuration

Module 3


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

96/261


After this Module, you should be able to:

Provision and validate the G-Port service on the EAGLE STP Identify the PDBI commands needed to provision MNP data

into EAGLE Database Modules

G-Port Configuration Prerequisites

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

97/261


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-Port feature sits on GTT/EGTT features, those have

to be activated prior to G-Port feature activation.

We presume GTT is already configured

We also presume the EAGLE Database Modules have already

been configured.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

98/261


G-Port is a control feature activated by the commands:

ENABLE-CTRL-FEAT:

- PARTNUM=893017201:

- FAK=XXXXX

CHG-CTRL-FEAT:

- PARTNUM=893017201:

- STATUS=ON

Define the Routing Number assigned by the regulator

ENT-HOMERN:RN=d22

Up to 100 Home RNs can be entered


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

99/261


In cases where a DN is ported-out, G-Port needs to define some GSMparameters to customize MSU fields when the EAGLE STP builds the

SRI-ACK.

CHG-GSMOPTS: MSRNDIG=CCRNDN:DEFMAPVR=2:

SRFADDR=996299999:SRFNAI=4:SRFNP=1:SRIDN=SCCP

Parameters put into the CGPAwhen G-Port builds the SRI-

Ack. Only the numeric value is

accepted for NAI and NP.

MSRNDIG defines how the MSISDN is

formatted in the SRI-ACK. DEFMAP is the

Default Map Version. This is useful to avoid

extraction errors when the MAP layer is

chosen.

Parameters to specify wherethe number has to be

extracted: SCCP or TCAP


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

100/261


G-Port needs also to define some STP Options.

CHG-STPOPTS:DEFCC=99:DSMAUD=CCC

Used to identify the CC of the

number and/or to condition the

number to an international

format before the RTDB

lookup

It is useful to set this

parameter to CCC. In this

case when a record into the

RTDB is corrupted on a

DSM/E5-SM card, this record

can be corrected by loading

the correct data from a mate

card.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

101/261


Service Selector entry for International MAP in E.164

ENT-SRVSEL:GTIN=4:SSN=6:TT=0:NP=E164:NAI=INTL

:SNP=E164:SNAI=CCRNDN:SERV=GPORT

Service Selector entry for National MAP in E.164

ENT-SRVSEL:GTIN=4:SSN=6:TT=0:NP=E164:NAI=NATL:SNP=E164:SNAI=RNDN:SERV=GPORT

Parameters

of the MSU

that trigger G-

PortService triggered if all

the previous parametersmatches the MSU

To specify how the G-Port

service has to processthe number


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

102/261


To load the VSCCP CARD with the RTDB, OAM, GPL, and GTT

data, once the G-Port feature is turned on, always boot the

DSM cards with the following command: INIT-CARD:LOC=

To display IS-NR status of VSCCP card input:

REPT-STAT-CARD


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

103/261


To set the G-Port service to be online use:

CHG-SCCP-SERV:SERV=GPORT:STATE=ONLINE

Confirm success of activation with the following commands:

REPT-STAT-SCCP

REPT-STAT-MPS

REPT-STAT-DB:DISPLAY=ALL

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.

Data Provisioning of the Database Modules

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

104/261


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 MNP traffic

A ti

Provisioning Data Flow

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

105/261

For Training Purposes Only117 I Tekelec. For Whats Next.EPAP B Active

PDBA

PDBIRTDB PDB

RTDB

EPAP A Standby

EPAP B Standby

PDBA

PDBIRTDB PDB

RTDB

EPAP A Active

Active

Standby

STP 2

Service

Module

Service

Module

Service

Module

STP 1

Service

Module

Service

Module

Service

Module

Customers

Provisioning

Database

Provisioning Configuration

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

106/261


Provisioning commands are sent to the Active PDBA through

the PDBI port

First the RN has to be entered

ent_entity(id d33, type RN, ri GT, da INSERT, pctype INTL, pc 3-0-0

Point Code of the

next node and its

format (Those

information are usedfor Non-Call related

only)

RN value

Command to

add a new

SP or a RN

Type of this

entity is a

Routing

Number

IntermediateGTT

Insert RN

into the

number

(CDPA only)


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

107/261


Then the HLR has to be entered, if it is not already present

ent_entity(id A01, type SP, ri SSN, da INSERT, pctype NATL, pc 2000)

Point Code of the HLR

and its format

ID of this

HLR

Command

to add a

new SP or

a RN

Type of this

entity is aSignaling

Point

Final GTT

to thisHLR

Insert SP ID

into the

number

(CDPA only)


T t P t d I b

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

108/261


To enter a new Ported-In number

ent_sub(dn 99633333333, spA01)

To enter a new Ported-Out number

ent_sub(dn 99622222222, rn d33)

DN to provisionCommand to

associate a new

DN to a HLR

ID of the HLR to

link to that DN

DN number to

provision

RN associated to

that DN

EAGLE RTDB: Retrieve DN data

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

109/261


The RTRV-DATA-RTDB command is used to retrieve EPAP

Provision data from the RTDB within the EAGLE Service

Module cards.

rtrv-data-rtdb:dn= 99622222222 :loc=1107

tekelecstp 08-08-26 14:03:15 EST EAGLE5 39.1.0

Card Loc : 1107 Status: Coherent

DN Portability Type ( 1) Entity Index

99622222222 Own Number ported out H'0000513d

Entity Address Type PCI (INTL ) RI SSN TT NP NAI DA

d33 RN 3-0-0 GT 000 000 00 000 none

SRFIMSI NSSN CCGT NTT NNP NNAI

no no no no no

ASD Address: 1234567890

Learning Activity

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

110/261


Learning Activities

Check Your Learning

Answer the questions to the best of your ability

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

111/261




8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

112/261

For Training Purposes Only127 I Tekelec. For Whats Next.This document is for informational purposes only, and Tekelec reserves the right to change any aspect of the products, features


G-Port Optional Extensions

Module 4


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

113/261


After this module, you should be able to:

State the purpose and describe the function of the following optional

features:

G-Port Circular Route Prevention

G-Port SRI Query for Prepaid

G-Port SCCP Service Re-Route Capability

GSM MAP SRI Redirect to Serving HLR

Digit Actions

Describe control requirements for each of these features.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

114/261



Circular Routing problem

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

115/261


The MNP Circular Route Prevention (CRP) feature is an extension of the

G-Port feature which helps in cases of circular routing caused by

incorrect information in one or more networks number portability

databases

HLRA

MSCA

Originating Network A Network B

EAGLE

MNP

HLRB

MSCB

EAGLE

MNP

Circular Route Prevention (CRP)

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

116/261


RecipientNetwork

MSC

1

IAM(RN + MSISDN)

SRI (RN+MSISDN)

Originating

Exchange

HLR

OriginatingNetwork A

2

NPDB

RN= Own Network ?

Yes, then NPDB lookup

should result in own

network result.

If other network result, then

a loop is detected

Generate SCCP UDTS

Log condition

SCCP UDTS3

Control Feature Activation

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

117/261


The G-Port feature must be enabled before the Circular Route Prevention

feature can be turned ON.

Feature can be enabled with a Temporary Feature Access key (FAK).

Temporary enabling of the feature shall follow existing controlled feature

requirements, such as :

30 day temporary enabled period.

Major alarm to indicate temporary key expiring 7 days prior to expiration. Critical alarm to indicate temporary key has expired.

The ENABLE-CTRL-FEAT Command can also be used to support the

permanent enabling of MNP Circular Route Prevention Feature.

enable-ctr l- feat:partnum=8930077001:fak=

chg-ctr l- feat:partnum=8930077001:status=ON


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

118/261



A need for G-Port SRI Query for Prepaid

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

119/261


Need

Correct charging for prepaid calls in most mobile networks requires

the Prepaid SCP database to not only have accurate informationabout the calling subscriber (A party), but also accurate information

about the called subscriber (B party). This is because the prepaid

database may set different call tariffs based not only on the status of

the calling subscriber, but also based on the status or receiving

network of the called subscriber.

Solution

G-Port SRI Query for Prepaid allows any SS7 node to directly query

the EAGLEs MNP database with an SRI message; EAGLE bypassesstandard SRF behavior, and will always respond to the originator with

SRI Ack with routing information.

SRI Query for Prepaid Function

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

120/261


EAGLE

SRI

TT=optional special value

SRI-ack

MSRN contains RN or HLR

value from EAGLEs RTDB

RTDB

EAGLE determines this is a special SRI from:

Special TT value included by SCP, or

SCCP CgPA or MTP OPC

Prepaid

SCP

Control Feature Activation

B f SRI Q f P id f t b bl d th G P t

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

121/261


Before SRI Query for Prepaid feature can be enabled, the G-Portfeature must be enabled and turned on.

Feature cannot be enabled with a Temporary Feature Access key(FAK).

Feature cannot be turned off after the feature is turned on.

enable-ctr l-feat:partnum=893017701:fak=

ent-gserv-data command to provision the translation type,originating point code, or global title address data in the GSERVtable.

These values are used to determine whether a SRI requestreceives G-Port SRI Query for Prepaid service or normal G-Portservice.

chg-ctr l- feat:partnum=893017701:status=ON

Optional Routing

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

122/261


p

G-Port SCCP Service Re-Routing

GSM MAP SRI Redirect to Serving HLR

Route SRI_SM and

ReportSMSDeliveryStatus for Non-local

or Ported-out Subscribers using GTT

G-Port SCCP Service Re-Route

Th G P t SCCP S i R R t f t

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

123/261


The G-Port SCCP Service Re-Route feature

Used when the G-Port subscriber database is incoherent with

MPS data and the GTT data is valid. designed to handle and control re-routing of G-Port traffic

- re-routes traffic from the EAGLE to other G-Port subscriberdatabase nodes within an operators network.

- inform the originating nodes to re-route the G-Port service related

traffic to other G-Port service nodes.

This feature and does not affect the normal G-Portfunctionality.

This feature also provides the option to mark G-Portoffline to perform a controlled re-routing during thisstate.

GSM MAP SRI Redirect to Serving HLR Feature

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

124/261


The GSM MAP SRI Redirect to Serving HLR feature provides

the capability to resolve network problems introduced by

maintaining equipment from multiple manufacturers withvendor-specific proprietary implementations.

This feature allows the operator to route SRI messages

based on the type of equipment at the source MSC anddestination HLR.

Vendor Type, Vendor Number, and Vendor Prefix are used to

identify the source and destination equipment.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

125/261


If the originating Mobile Switching Center (MSC) of the Send

Route Information (SRI) message and the destination Home

Location Register (HLR) are the same vendor type, the message is relayed to the HLR associated in the RTDB to the

service provider.

If the originating MSC of the SRI message and thedestination HLR are not the same vendor type,

G-Port checks whether the vendor type is deployed in more than

one network; each network has its own vendor/network

prefixes.MSC SRI message Home Location Register (HLR)


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

126/261


If the vendor types of the originating MSC and destination

HLR are different and the destination HLR vendor type is

deployed in more than one network, the vendor/network prefix that points to the network where the

hosting HLR resides is appended.

If the vendor types of the originating MSC and destinationHLR are different and the vendor type of destination HLR is

deployed in only one network,

the vendor/network prefix that is assigned to the network is

appended.


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

127/261


The GSM MAP SRI Redirect to Serving HLR feature is

provisioned

Vendor Prefix List

- contains the Vendor Number and associated Vendor Prefix (maximum of

six digits).

- up to three vendor prefix entries

Vendor ID List- contains the Vendor ID, Vendor Type, and Vendor (network) Number.

- All Vendor IDs must be the same length which is provisionable for 1 to 15

digits using the ent-vendid command.

- A Vendor ID cannot be entered into the database until the associated

Vendor Prefix is defined.

- vendor ID list can have up to 200 entries.

GSM MAP SRI Redirect to Serving HLR Call Flows

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

128/261


Route SRI_SM and ReportSMSDeliveryStatus forNon-local or Ported-out Subscribers using GTT

Th R t SRI SM d R tSMSD li St t f N

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

129/261


The Route SRI_SM and ReportSMSDeliveryStatus for Non-

local or Ported-out Subscribers using GTT functionality:

modifies SRI_SM and ReportSMSDeliveryStatus messages to allowrouting of the message to an alternate network using Global Title

Translation (GTT).

This process occurs when the Directory Number (DN) in the database is associated with both the

Service Point (SP) and Generic Routing Number (GRN) network

elements and the GRN is not present in the EAGLE HomeRN table,

or when the subscriber is ported out and associated with the

Routing Number (RN).

Route SRI_SM and ReportSMSDeliveryStatus for Non-local or Ported-out Subscribers using GTT

F thi f t th CDPA i lt d d ll GTT t

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

130/261


For this feature the CDPA is altered and allows GTT to

redirect the query to an alternate network. The CdPA is

change to one the following formats: CC + GRN + DN

CC + RN + DN.

If a Country Code (CC) is not located in the DN, then theSCCP CdPA is converted to:

GRN + DN or RN +DN

This functionality is controlled by the SRISMGTTRTG optionof the CHG-GSMOPTS command off and on parameters.

chg-gsmopts:srismgttrtg={on/off}

Optional Digit Action Features

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

131/261


Digit Action Expansion

Digit Action DELCCPREFIX

Multiple Country CodeMSISDN Truncation Support

Digit Action Expansion

Th Di itA ti E i f t

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

132/261


The DigitAction Expansion feature

provides more flexibility to formulate the SCCP Called Party

Address - Global Title Address (GTA) field of the MAP messagesrelayed by G-Port.

Without DigitAction Expansion,

G-Port supports only four options (none, insert, prefix, andreplace) to overwrite the SCCP CdPA GTA field.

With DigitAction Expansion,

four additional options (delcc, delccprefix, spare1, and spare2)are included to overwrite the SCCP CdPA GTA field.

Digit Action DELCCPREFIX

DELCCPREFIX DigitAction Feature

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

133/261


DELCCPREFIX DigitAction Feature

Supports the deletion of the Called Party Global Title Address (CdPA

GTA) country code and the GTA is prefixed with the Entity Id Applies to the CdPA GTA in either National format or International

format.

The DELCCPREFIX option in the SCCPOPTS table specifies how

the DELCCPREFIX digit action is applied to a Called Party GlobalTitle Address (CdPA GTA).

CHG-SCCPOPTS:DELCCPREFIX={PFXWCC or PFX4ALL}

- pfxwcc Apply the DELCCPREFIX digit action to the CdPA GTA only whenthe address has a International format. If this option is selected, then theCountry Code is deleted and the GTA is prefixed with the Entity Id.

- pfx4all Apply the DELCCPREFIX digit action to the CdPA GTA in all cases.If this option is selected, then for an International format, the Country Code isdeleted and the GTA is prefixed with the Entity Id. For a National format, theGTA is prefixed with the Entity ID.

Multiple Country Code

The Multiple Country Code (MULTCC) feature;

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

134/261


The Multiple Country Code (MULTCC) feature;

supports up to 10 MULTCCs for customers having one MNP node

servicing several countries, or areas with differing country codes. is used to construct Mobile Station Roaming Number (MSRN)

parameter for the Send Routing Information acknowledgement (SRIAck) message from G-Port, and in certain cases for the formulation ofthe SCCP CdPA.

The CHG-GSMOPTS command along with the MULTCC andNMULTCC parameters are used to provision Multiple CountryCode list entries.

The MULTCC list is optional.

If no values are provisioned, G-Port uses the DEFCC to processmessages.

If values are provisioned, G-Port automatically uses both the DEFCCand the MULTCC to process messages.

MSISDN Truncation Support for G-Port

Some carriers require MSISDN digits to be truncated when

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

135/261


Some carriers require MSISDN digits to be truncated when

formulating the MSRN parameter of SRI Ack message in G-Port to

maintain a maximum length of 15 digits. The International MSISDN is 12 digits long, and the RN is 5 digits long.

So when the RN is added to form the MSRN parameter, it will exceed

15 digits in length.

The MSISDN Truncation Support for G-Port feature

allows an operator to specify a certain number of digits to be deletedfrom the beginning of the National MSISDN (MSISDN without Country

Code) prior to formulating the MSRN parameter of the SRI Ack

message.

This feature only changes the behavior of the encoding of the MAP

MSRN parameter in an SRI Ack message formulated by the EAGLE.

The chg-gsmopts command along with the MISDNTRUNC

parameter is used to set-up the MSISDN Truncation Support

feature.

Check Your Learning


8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

136/261




8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

137/261



GSM SMS/MMS NP

Module 5



8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

138/261



Lesson 1 Mobile Terminated (MT)-Based GSM SMS/MMS NP

Lesson 2 Mobile Originated (MO)-Based GSM SMS NP

Lesson 3 MO SMS GSM NP Numbering Plan Processor (NPP)

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

139/261



Mobile Terminated (MT)-Based GSM SMS/MMS NP

Module 5

Lesson 1

Lesson Objectives

After this Lesson you should be able to:

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

140/261


After this Lesson, you should be able to:

State the purpose and describe the function of the for the

Mobile Terminated (MT) Based GSM SMS/MMS NP Feature:

Describe control requirements for this feature

NP support for SMS

Need

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

141/261


eed

With number portability, the SMSC/MMSC can no longer use the

called party number to determine whether the called subscriber is itsown subscriber or belongs to another operator.

Effect

If the SMSC cannot determine this, then the SMSC does not know

when to use IS41 or GSM protocol and when to use the SMPPprotocol to deliver the SMS message.

Solution

The MT-based GSM SMS feature allows the SMSC/MMSC to retrievethe called subscribers network information, so that the SMSC/MMSCcan use the correct protocol and deliver the SMS to the called party.

MT-Based GSM SMS Number Portability

The Mobile-Terminated (MT) Based GSM SMS NP feature

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

142/261


The Mobile Terminated (MT) Based GSM SMS NP feature

allows wireless operators to route short message service

(SMS) messages destined to mobile subscribers within anumber portability (NP) environment.

MT-Based GSM MMS NP

The MT-Based GSM MMS NP feature allows wireless operators

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

143/261


The MT Based GSM MMS NP feature allows wireless operators

to route Multimedia Message Service (MMS) messages

destined to mobile subscriber within a number portability (NP)environment.

The MT Based GSM MMS NP feature allows number portability

(NP) database lookup to be performed on MMS messages thatare routed from a Multimedia Message Service Center

(MMSC).

MT-Based GSM MMS NP

The MT-Based GSM MMS NP feature intercepts SRI SM

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

144/261


p _messages and sends response messages with routing

information for out-of-network destination subscribersusing the following process:

1. An SRI_SM message is intercepted by the EAGLE 5 ISS before it reachesthe home location register (HLR).

2. Extracts the message destination address (SCCP Called Party GTA),

conditions the digits, and performs a lookup in the Real-TimeDatabase (RTDB).

3. If the destination address/subscribers belongs to a foreign network,then a reply message is sent to the MMSC with routing information. Ifthe destination address/subscribers belongs to a local network, thenthe SRI_SM message is relayed to the HLR or according to the

options set for normal G-Port routing.

MT-Based GSM SMS/MMS NP In-network Subscriber

TCAP Calling Party: wireless GSM subscriber

TCAP C ll d P t t d / t d i i l b ib

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

145/261


GSM MSC

EAGLE

5 ISS

Originating Wireless Network Visited Wireless Network

4. SRI_SM Ack

(VLR)

1. SRI_SM (B)

5.MT

3. SRI_SM Ack

(VLR)

2. SRI_SM (B)

MMSC/SMSC

NPDB

TCAP Called Party: non-ported / ported-in wireless subscriber

belonging to the same carrier

Type of call: MMS/SMS

Change relative to the current call processing: MMSC/SMSC

has to be reconfigured to generate SRI_SM to the HLR,

regardless of called subscriber number being in or out of its own

numbering range

Observations:

- in case called subscriber is ported-in, it has to be provisionedindividually

- in case called subscriber is TDMA, EAGLE Migration (IGM)

feature ensures that the message gets delivered in the TDMA

network

MT-Based GSM SMS/MMS NP Other Network Subscriber

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

146/261


TCAP Calling Party: wireless GSM subscriber

TCAP Called Party: ported-out wireless subscriber

Type of call: MMS/SMS

Change relative to the current call processing:

MMSC/SMSC has to be reconfigured to associate the RNs

to their respective carriers

Observations:- called subscriber has to be provisionedindividually

MMSC/SMSC SMSC

EAGLE 5

ISS

Originating Wireless Network Recipient Wireless Network

2. SRI_SM Ack

(RN)1. SRI_SM (B)

3.Deliver_SMor

Submit_SMSMPP

NPDB

Feature Control Requirements

The MT-Based GSM SMS NP feature has the following

8/13/2019 TK302_Eagle R45.0 EPAP R15.0_V6.0

147/261


The MT Based GSM SMS NP feature has the following

control requirements:

The defcc and defmcc parameters in the chg-stpopts command must be setto a value other than none before the feature can be turned on.

FAK for part number 893-0200-01

The G-Port feature must be enabled and turned on before the MT-Based

GSM SMS NP feature can be enabled and turn

Date post:	04-Jun-2018
Category:	Documents
Upload:	fredspb
View:	221 times
Download:	1 times

TK302_Eagle R45.0 EPAP R15.0_V6.0

Documents