tk303 eagle r43.0 epap r14.0 v4.0 slides

This document is for training 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 V5.4

TK303

EAGLE Rel. 43.0 / EPAP Rel. 14.0

Number Portability INP, AINP, IDPR, IAR

Version 4.0

3

› 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

Course Logistics

4

In this guide, you will find the following structure:

› Large units of learning are called Modules. Modules contain:

Module objectives

Presentation and lecture

Smaller units of learning called Lessons (some modules)

› Each Lesson contains:

Lesson Objectives

Presentation and Lecture

Check-Your-Learning review questions (some lessons)

Hands-on Learning Activities (some lessons)

Student Guide Layout

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 - INP/AINPQ

Feature Manual - IDP-Related Features

6

After this Course, you should be able to:

› Describe feature need, structure, and functions for:

INP (INAP-based Number Portability)

AINP (ANSI-41 INP)

IDPR (IDP Query Relay)

IAR (Info Analyzed Relay)

› Identify call flows for each feature.

› Describe the implementation of the Service Portability (S-

Port) feature with each of the above features.

› Configure and enable all purchased features.

Course Objectives



Number Portability Review

Module 1

8

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

Module 1

9

Message Signalling Unit

Message Signalling Unit

(MSU)

SS7/CCS7 Signal Units

Signal Units

FISUFill In Signal Unit

MSUMessage Signal Unit

LSSULink Status Signal Unit

MSU

LSSU

FISU CK LIF

I

B

FSNB

I

B

BSN FLAG

CK LIF

I

B

FSNB

I

B

BSN FLAGSF

CK LIF

I

B

FSNB

I

B

BSN FLAG

Transmission Direction



16

16

16

2

2

2

6

6

6

1 1

1 1

1 1

7 7

7 7

7 7

8

8

8

8 or 16

SIF

8n, n>2

SIO

8

LSB

LSB

LSB

SS7/CCS7 Signal Unit Fields

Message Signal Unit (MSU) Structure

CRC TCAP/MAP CGPA

Length

Address Indicator

Subsystem

Point Code

(NCM NC NI)

CDPA

Length

Address

Indicator

Routing Indicator

Subsystem

Point Code

(NCM NC NI)

SLS OPC

NCM NC NI

DPC

NCM NC NI

SIO

NIC PRI SI

LI FSN BSN

Level 2 Level 4 Routing Label Level 2

CRC TCAP/MAP CGPA

Length

Address Indicator

Subsystem

Point Code

(ID Zone Area)

(NPC)

CDPA

Length

Address

Indicator

Routing Indicator

Subsystem

Point Code

(ID Zone Area)

(NPC)

SLS OPC

(ID Zone Area)

(NPC)

DPC

(ID Zone Area)

(NPC)

SIO

NIC PRI SI

LI FSN BSN

Level 2 Level 4 Routing Label Level 2

ANSI Example

ITU Example

MSU Fields Used in GTT

Message Signal Unit

(MSU)

Signalling Information Field

(SIF)

Routing

Label

Address

Indicator

Signaling Information Field - Routing Label

CK SIF SIO LI

FIB

FSN BIB BSN FLAG

TRANSMISSION DIRECTION

16 8n, n>2 8 2 6 1 7 1 7 8

Routing Label

DPC OPC

NCM-NC-NI ANSI NCM-NC-NI

0-16383 ITU-N 0–16383

MSA-SSA-SP ITU-N24 MSA-SSA-SP

Zone-Area-ID ITU-I Zone-Area-ID

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 Subsystem Number indicator - value of 0 or 1

•Bit 2 Point Code Indicator - value of 0 or 1

•Bits 3 – 6 Global Title Indicator – value of 0 to 4

•Bit 7 Routing Indicator - value of GT or SSN

•Bit 8 National/International Indicator – value of 0 or 1

8 7 6 5 4 3 2 1

NI RI GTI PC SSN

ANSI Signaling Information Field (CDPA)

CK SIF SIO LI

FIB

FSN BIB BSN FLAG

CDPA

Digits 5=MAP

6= HLR

7= VLR 8=

MSC

245=LNP

251=CLASS

253=LIDB

254=E800

GTA

Global Title

Address

TT

Translation

Type

SSN

Subsystem

Number

PC

Point

Code

AI

Address

Indicator

5=CNAM

11=LNP

251=CLASS

253=LIDB

254=E800

NCM NC NI

GTI =2(tt & digits)

RI =0 (route on gt), =1(route on pc/ssn)

NI =0 (international ntwk), =1(national ntwk)

17

CDPA Format (ANSI)

00001000 CDPA Length indicator 8

01001010 Address indicator

0- - - - - - - Reserved 0

-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

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 Point Code indicator - value of 0 or 1

•Bit 2 Subsystem Number Indicator - value of 0 or 1

•Bits 3 – 6 Global Title Indicator – value of 0 to 4

•Bit 7 Routing Indicator - value of GT or SSN

•Bit 8 National/International Indicator – value of 0 or 1

8 7 6 5 4 3 2 1

NI RI GTI SSN PC

19

ITU Signaling Information Field (CDPA)

CK SIF SIO LI

FIB

FSN BIB BSN FLAG

CDPA

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

Binary Coded Decimal

1= odd numbers

2=even numbers

5=MAP

6= HLR

7= VLR

8= MSC

GTA

Global Title

Address

NAI

Nature of Address

Indicator

TT

Translation

Type

SSN

Subsystem

Number

PC

Point

Code

NP ES

Numbering Encoding

Plan Scheme

AI

Address

Indicator

TT-0

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)

20

CDPA Format (ITU)

00001010 CDPA Length indicator 10

01010010 Address indicator

0- - - - - - - Reserved 0

-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

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.

23

Numbering Plan

Numbering Plan

(NP)

24

Numbering Plan (NP)

› 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

25

Numbering Plan (NP)

› E.212: This is the IMSI Numbering 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

26

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

E.212

1 to 3



E.164

27

Nature of Address Indicator

Nature of Address Indicator

(NAI)

28


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

29


› 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>

30


› 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

31

Number Portability

Number Portability

(NP)

32

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.

33

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 operator‟s NP solution is independent from other

operators, but it requires cooperation for implementation.

34

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

35

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

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.

Country xxx

Regulator

Operator 1 Operator 2 Operator 3

D11D22

D33

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 Signalling 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

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

Command entered at terminal #1.;


Card Loc : 1105 Status: Coherent

DN Portability Type ( 0)

861234540000 Not Known to be ported

EntIdx1 EntIdx2

H'00000006 -------

Entity Address Type PC(ANSI ) RI SSN TT NP NAI DA

25 SP 001-002-003 GT 000 000 00 000 prefix

SRFIMSI NSSN CCGT NTT NNP NNAI

no no no no no

EAGLE DB Command

Database location,

Directory Number and

Portability Type

Entity Address ID, Entity Type,

Point Code and Routing Indicator

39

Extended Usage of Database Modules: NP

…

DN 861234540000, Signalling Point (SP) 25 …DN belongs to this Service Provider

STP

Incoming MSU

with the DN

861234540000

Database

Module MSU (SP + DN) next network node

Outgoing number = 25861234540000

NP tables are down

loaded into the

memory of the

Database Modules

40

EAGLE NPDB Data Example: Ported DN


rtrv-data-rtdb:dn=861234560000

Command entered at terminal #1.;


Card Loc : 1105 Status:Coherent

DN Portability Type ( 1)

861234560000 Own Number ported out

EntIdx1 EntIdx2

H'00000029 -------

Entity Address Type PC(ANSI ) RI SSN TT NP NAI DA

30 RN 001-002-003 GT 000 000 00 000 prefix

SRFIMSI NSSN CCGT NTT NNP NNAI

no no no no no

EAGLE DB Command

Entity Address ID, Entity Type,

Point Code and Routing Indicator

Database location,

Directory Number and

Portability Type

41

Extended Usage of Database Modules: NP

…

DN 861234560000, Routing Number (RN) 30 …

Ported to Operator X

STP

Incoming MSU

with the DN

861234560000

Database

Module MSU (RN + DN) goes to Operator X

Outgoing number = 30861234560000

NP tables are down

loaded into the

memory of the

Database Modules

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 customer‟s 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.

43

Reminder: NP Data Flow Architecture

IGM

TIF

IDPR

IAR

A-Port

G-Port

S-Port

G-Flex

EIR

GTT

Provisioning System

IGM

TIF

IDPR

IAR

A-Port

G-Port

S-Port

G-Flex

EIR

GTT

Primary Write Standby Write and Read

EAGLE 5

Auto-Synch DB

SM1

SM24

EPAP-A EPAP-B

Primary Read

Redundant EPAP

Provisioning System

EAGLE 5

Auto-Synch DB

SM1

SM24

EPAP-A EPAP-B

RTDB RTDB

44

Check Your Learning: Module 1

› Answer the questions to the best of your ability.

› We will review all answers as a group.



Module 2:

INP/AINP Architecture

48

This Module contains the following lessons:

› Lesson 1 INP/AINP

› Lesson 2 INPQ/AINPQ Detailed Call Flow

› Lesson 3 INPMR Detailed Call Flow

› Lesson 4 Circular Route Prevention

› Lesson 5 INP Configuration

Module 2



Lesson 1

INP/AINP

Module 2

50

After this lesson, you should be able to:

› Identify the purpose of the INP & AINP function

› Analyze which Message Signaling Units (MSU) are affected

by INP and AINP

› Analyze MSU data extraction for the INP and AINP features

Module 2: Lesson 1

51

INP and AINP

INAP Portability (INP) and ANSI-41

INP Query (AINP)

52

INP and AINP

› INP and AINP are different features that can be activated separately or together.

INP is activated when the EAGLE STP is used to check the portability information of INAP/CAP transactions.

AINP is activated when the EAGLE STP is used to check the portability information of AIN transactions.

› INP/AINP features are divided into two services:

INPQ for call-related and for ITU-N and ANSI

INPMR for non-call related and for ITU-I / ITU-N / ANSI

• The type of transaction is ISDN Supplementary Services, like CCBS or Message Waiting Indication.

53

INP and AINP Architecture

› INP/AINP are deployed along with STP.

STP/

INP/AINP

MSC

SCP 2SCP 1 SCP 3

STP/

INP/AINP

54

Which MSU are Affected by INP

› A Directory Number (DN) can be:

Non-Ported (same case as before Mobile Number Portability (MNP))

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

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

A DN cannot have more than 15 digits to be successfully processed by INP.

› Call flows can be:

Call related with INAP/CAP/AIN Protocol

• INPQ acts as a NP SCP in all cases.

• DN is extracted from the INAP/CAP layer.

Non-Call related with INAP/CAP Protocol

• INPMR acts as a Message Relay in all cases.

• DN is extracted from the CDPA layer.

55

Check Your Learning: Module 2 – Lesson 1





Lesson 2

INPQ/AINPQ Detailed Call Flow

Module 2

58


› Explore and analyze data extraction, number conditioning

and service selection steps performed for ported-out DNs.

› Identify and analyze data and communications sent to and

from the INP/AINP database node.

Module 2: Lesson 2

59

INPQ/AINPQ

INPQ/AINPQ Call Flow in the

Portability Environment when

the EAGLE STP is the NPDB

60

INPQ / AINPQ

› INAP Portability Query (INPQ) and ANSI-41 INAP Query

(AINPQ) are using the same processing inside the EAGLE;

only the content of the MSU is different.

CAP or INAP for ITU

TCAP which is AIN for ANSI

› In the EAGLE STP, the same service INPQ will process INPQ

and AINPQ if both features have been activated. Note: This

changes in EAGLE Release 41.1.

61

INPQ Example

Switch STP

Checks the portability status of 0622222222 and

answers back to the switch

IDP Message

Call the number

0622222222

Connect Message

with DRA or

Continue Message

252

62

AINPQ Example

Switch STP

Checks the portability status of 9199324000 and

answers back to the switch

TCAP NP Request

Call number

9199324000

Return Result with

Routing Digits or

Return Result without

Routing Digits

252

63



example

64

Examples Data

A country (CC=99) with three operators

Operator 1

• Own range of number: 99610000000-99619999999

• Routing Number: d11

Operator 2 (Considered the operator with INP)



Operator 3



INPQ/AINPQ Detailed Call Flow Example

SSN=252

TT=0

NP=E164

NAI=INTL

Digit 1=9

ES=BCD

Digit 2=9

Digit 3=6Digit 4=2

Digit 5=2Digit 6=2

Digit 7=2Digit 8=…

NI=0 RI=0 GTI=4 SSN=1PC=0

CGPA CDPA

SCCP Fields

… …GTT is required

SSN of STP


SwitchSTP

INP/AINP

GT=99623456789

NAI NP CdPA

CAP/INAP/AIN Fields

252

IDP/TCAP NP

Request sent by

the Switch to the

STP

CdPA=99622222222


SSN=251

TT=0

NP=E164

NAI=INTL

Digit 1=9

ES=BCD

Digit 2=9

Digit 3=6Digit 4=2

Digit 5=3Digit 6=4



CGPA CDPA

SCCP Fields

… …GTT is NOT required

Switch SSN


SwitchSTP

INP/AINP

GT=99623456789

NAI NP CdPA

CAP/INAP/AIN Fields

252

IDP/TCAP NP

Request sent by

the Switch to the

STP

CdPA=99622222222


IDP/TCAP NP

Request sent by

the Switch to the

STP

CGPA CDPA

SCCP Fields

… …


SwitchSTP

INP/AINP

GT=99623456789

NAI NP CdPA

CAP/INAP/AIN Fields

NAI=Unkn

Digit 1=0Digit 2=6

Digit 3=2Digit 4=2

Digit 5=2Digit 6=2


NP=E164

252

CdPA=99622222222

68


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

Module; and the service selector table is looked up first.

EAGLE Database Module

yes

GTT

INPQ

conditioning

and lookup into

RTDB table

Send

Response

With

Number

no

Evaluate

SPRESTYPE

Yes (RN) Generate

Response

using RNYes (SP)

Send

Response

without

Number

No

Service

Selector

Table

MSU in from IMT

MSU out to IMT

Connect

Continue

Generate

Response

69


› Fields extracted from the CDPA by the EAGLE

SSN=252

TT=0

NP=E164

NAI=INTL

Digit 1=9Digit 2=9

Digit 3=6Digit 4=2

Digit 5=2Digit 6=2



ES=BCD

Parameters

extracted from

the CDPA to find

a match in

Service

Selectors Table

Service Selectors Table contains:

…

GTIN=4:SSN=252:TT=0: NP=E164:

NAI=INTL:SERV=INPQ

…

INPQ is

triggered

70


› INPQ service has been triggered.

The DN is conditioned before RTDB lookup.


yes

GTT

INPQ

conditioning

and lookup into

RTDB table

Send

Response

With

Number

no

Evaluate

SPRESTYPE

Yes (RN) Generate

Response

using RNYes (SP)

Send

Response

without

Number

No

Service

Selector

Table

MSU in from IMT

MSU out to IMT

Connect

Continue

Generate

Response

71


NAI=Unkn

Digit 1=0Digit 2=6

Digit 3=2Digit 4=2

Digit 5=2Digit 6=2


DN or Dialed Digit

(DGTSDIAL)

extracted to

perform a RTDB

lookup

NP=E164

NAI NP DN

INAP/CAP/AIN CdPN Fields

……

› DN extraction from Application Layer

72


Conditioning is done in the following sequence:

1. Compare the extracted DN with the prefixes defined by the parameter

CDPNPFX of the table INPOPTS.

• If a match is found, the prefix is removed prior to the next step.

2. If present, remove the ST (STop) digit.

3. Compare the remaining DN with the NEC parameter of the table INPOPTS.

• If a match is found, the NEC is removed.

4. Compare the NAI of CdPN with the parameter CDPNNAI of the table

INPOPTS to know how to prepare the DN prior to RTDB lookup.

• If they match, the SNAI parameter of INPOPTS is used.

• If they do not match, the DN is considered National unless the

NAI field from the INAP/CAP/IS41 is International or Subscriber.

In this case, the DN is respectively considered International or

Subscriber

73


› In our example, we consider:

No prefix is defined

NEC=0

CDPNNAI=3 (NATL) and SNAI=NATL

The extracted DN is 0622222222

› After removing NEC, the remaining digits are 622222222.

NAI of CdPN = Unknown; does not match with CDPNNAI, the DN is considered National.

This number will be converted to international as the RTDB contains only international numbers.

• The DEFCC parameter of the STPOPTS (99 in this example)

• The DN becomes 99622222222

74


› After number conditioning, RTDB lookup is performed to

search for the international number.

RTDB Database contains:

…

DN 99622222222, RN d33

…


RTDB

This DN has been ported-

out with RN d33.

This result is used to build the

response to the switch

75


› INPQ has found a RN associated with this DN.


yes

GTT

INPQ

conditioning

and lookup into

RTDB table

Send

Response

With

Number

no

Evaluate

SPRESTYPE

Yes (RN) Generate

Response

using RNYes (SP)

Send

Response

without

Number

No

Service

Selector

Table

MSU in from IMT

MSU out to IMT

Connect

Continue

Generate

Response

76


› The response depends on two things:

The result of the RTDB lookup

The value of the parameter SPRESTYPE of the tables INPOPTS and AINPOPTS

› The response is a connect message (ITU) or Return Result with Routing Digits (ANSI) in the following cases:

The NPDB query result type is RN (in this case the SPRESTYPE does not matter)

The NPDB query result type is SP and the SPRESTYPE is specified as connect

› Otherwise, the response is a continue message (ITU) or Return Result without Routing Digits (ANSI).

77


› If the response is a connect message (as it will be in this

example) the DRA section is built according to the following

parameters:

• The DRANAI/DRANAIV parameter of the tables INPOPTS and

AINPOPTS will be used to fill the outgoing NAI of the CdPN.

• The DRANP/DRANPV parameter of the tables INPOPTS and

AINPOPTS will be used to fill the outgoing NP of the CdPN.

• The DRA parameter of the tables INPOPTS and AINPOPTS will be

used to format the CdPN.

• In addition to the use of the DRA parameter to format the CdPN, if

during the prefix deletion (if a prefix was found during conditioning

before the RTDB lookup) this found prefix is associated with the

parameter dltpfx=yes. In this case that means the prefix of the CdPN

shall be remove in the DRA message

78


› In our example, we consider:

DRANAI=NATL

DRANP=E164

DRA=RNDN

› The sections of the message built with the above parameters

are:

Destination Routing Address (DRA) for ITU

Return Results with Routing Digit for ANSI


SSN=251


SwitchSTP

INP/AINP

CGPA CDPA

SCCP Fields

… …


NAI NP DN

CAP/INAP/AIN CdPN Fields

252

Response sent

by the STP to

the switch

GT=99623456789

CdPA=99622222222


Response sent

by the STP to

the switch

SSN=252


SwitchSTP

INP/AINP

CGPA CDPA

SCCP Fields

… …


NAI NP DN


GT=99623456789

CdPA=99622222222

81


Response sent

by the STP to

the switch

SwitchSTP

INP/AINP

CGPA CDPA

SCCP Fields

… …


252

NAI=Natl

Digit 1=dDigit 2=3

Digit 3=3Digit 4=6

Digit 5=2Digit 6=2


NP=E164


GT=99623456789

CdPA=99622222222

NAI NP DN

82

Learning Activity: Module 2 – Lesson 2

Learning Activities

84






Lesson 3

INPMR Detailed Call Flow

Module 2

88



and service selection steps performed for ported-out DNs


from the INPMR database node

Module 2: Lesson 3

89

INPMR

› INPMR service is triggered for non-call related

INAP/CAP/AIN messages to be relayed by the STP to the

next node according to portability information.

› Non-call related messages are ISDN Supplementary

Services, like CCBS or Message Waiting Indication.

› CCBS is a subscriber feature used for completing calls to a

busy subscriber by monitoring the called party„s line and

completing a call attempt when the called party is free.

90

INPMR Detailed Call Flow Example

› CCBS example

STP

Checks the portability status of 99622222222

and optionally insert information into CDPA

before relaying to the next node

CCBS

Request

Busy B-number

99622222222

252

HLRNext Node

CCBS

Request

91


SSN=6

TT=0

NP=E164

NAI=INTL

Digit 1=9

ES=BCD

Digit 2=9

Digit 3=6Digit 4=2

Digit 5=2Digit 6=2



CGPA CDPA

SCCP Fields


SSN of HLR


STP

INP

GT=99623333333252

CCBS Request

sent by the HLR to

the STP

CdPA=99622222222

HLR

92


SSN=6

TT=0

NP=E164

NAI=INTL

Digit 1=9

ES=BCD

Digit 2=9

Digit 3=6Digit 4=2

Digit 5=3Digit 6=3



CGPA CDPA

SCCP Fields


SSN of HLR


STP

INP

GT=99623333333252

CCBS Request

sent by the HLR to

the STP

CdPA=99622222222

HLR

93


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

Module and the service selector table is looked up first.


yes

GTT

Fall

thru

no

Update CDPA &

MTP3

Yes (RN)

Yes (SP)

Route

Message

No

Service

Selector

Table

MSU in from IMT

MSU out to IMT

INPMR

conditioning

and lookup into

RTDB table

94


› Fields extracted from the CDPA by EAGLE

SSN=6

TT=0

NP=E164

NAI=INTL

Digit 1=9Digit 2=9

Digit 3=6Digit 4=2

Digit 5=2Digit 6=2



ES=BCD

Parameters

extracted from

the CDPA to find

a match in

Service

Selectors Table


…


NAI=INTL:SNP=E164:SNAI=RNIDN:

SERV=INPMR

…

INPMR is

triggered

95


› INPMR service has been triggered.

The DN is conditioned, if needed, before RTDB lookup.


yes

GTT

Fall

thru

no

Update CDPA &

MTP3

Yes (RN)

Yes (SP)

Route

Message

No

MSU in from IMT

Service

Selector

Table

MSU out to IMT

INPMR

conditioning

and lookup into

RTDB table

96


› The DN (GTA) is extracted from the CDPA by INPMR.

SSN=6

TT=0

NP=E164

NAI=INTL

Digit 1=9Digit 2=9

Digit 3=6Digit 4=2

Digit 5=2Digit 6=2



ES=BCD

GTA extracted

from the CDPA

to perform a

RTDB lookup

97


› Depending on the value of the SNAI field previously found in the service selector table when INPMR has been triggered, the INPMR service knows how to process the GTA.

In this example, we choose SNAI=RNIDN.

INPMR will first try to find a match with the beginning of the GTA (or DN) and one of the RN entered in the table HOMERN.

• If a match is found, the RN is stripped off.

• If no match is found, the DN is considered to be IDN.

› The number is then converted to international, if not already, by using the information of the STPOPTS table (defcc and defndc parameters).

98


› After number conditioning, the RTDB lookup is performed to

search for the DN.


…

DN 99622222222, RN d33

…

da PREFIX, PC 3-0-0


RTDB

This DN has been

ported out and is

associated with RN d33.

This result is used to

modify the GTA into the

CDPA of the MSU before

routing or sending to the

next node.

Resulting information

is used to route the

MSU to the next

node.

How to format the

GTA into the CDPA

99


› INPMR has found a RN associated with this DN.


yes

GTT

Fall

thru

no

Update CDPA &

MTP3

Yes (RN)

Yes (SP)

Route

Message

No

MSU in from IMT

Service

Selector

Table

MSU out to IMT

INPMR

conditioning

and lookup into

RTDB table

100


› INPMR relays the MSU with the lookup results.

› Puts the PC found in the RTDB for this DN into the DPC field

(MTP3 layer)

› Formats the GTA into the CDPA according to the parameter

found in the RTDB associated with this RN for this DN

In this example, the value for da is PREFIX so RN+DN is put as

GTA into the CDPA.

101


MSU routed by

the STP to the

GMSCSSN=6

TT=0

NP=E164

NAI=INTL

Digit 1=d

ES=BCD

Digit 2=3

Digit 3=3Digit 4=9

Digit 5=9Digit 6=6



CDPA

SCCP Fields

CGPA …DPC=3-0-0 …

MTP3 Fields

……

STP

INP252

Node 3-0-0


Learning Activities

104






Circular Route Prevention

Lesson 4Module 2

108


› State the purpose and describe the function and control requirements for

of Circular Route Prevention

Module 2 – Lesson 4

Circular Routing Problem

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

feature which helps in cases of circular routing caused by incorrect

information in one or more networks‟ number portability databases.

› CRP is not associated with AINP.

HLRA

MSCA

Originating Network A Network B

EAGLE

INP

HLRB

MSCB

EAGLE

INP

110

Circular Route Prevention (CRP)

Recipient

Network

MSC

1

IAM

(RN + MSISDN)

SRI (RN+MSISDN)

Originating

Exchange

HLR

Originating

Network 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

111

Control Feature Activation

› 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-ctrl-feat:partnum=8930077001:fak=<feature access key>

chg-ctrl-feat:partnum=8930077001:status=ON



Lesson 5

INP Configuration

Module 2

114


› Configure INPQ and INPMR

Module 2: Lesson 5

115

INP Configuration

› The SS7 configuration in the EAGLE STP is assumed to be

already done:

All information used for MTP3 routing (Route, linkset, links, point

code)

› The INP feature requires the GTT/EGTT features, which must

be activated prior to INP feature activation.

We assume GTT has been configured.

› We also assume the EAGLE Database Modules have been

configured.

116

INP Configuration

› INP is a control feature activated by the commands:

ENABLE-CTRL-FEAT:partnum=893017901:fak=VCWCAP957SA66

CHG-CTRL-FEAT:partnum=893017901:status=ON

› ANSI-41 INP Query is activated separately.

ENABLE-CTRL-

FEAT:partnum=893017801:fak=NXK5WRDHNRB3B

CHG-CTRL-FEAT:partnum=893017801:status=ON

› Define the Routing Number assigned by the regulator

ENT-HOMERN:RN=d22

Up to a maximum of 100 Home RNs can be entered

117

INP Configuration

› INPQ and INPMR need to define some STP options, if it is

not already done:

CHG-STPOPTS:DEFCC=99:DEFNDC=20

Used eventually to condition

the number to an international

format before the RTDB

lookup

Used eventually to condition

the number to an international

format before the RTDB

lookup

118

INP Configuration

› INPQ needs to define some INAP Options:

CHG-INPOPTS:CDPNNAI=3:SNAI=NATL:NEC=0:

DRA=RNDN:DRANAI=NATL:DRANP=E164:

SPRESTYPE=CONNECT

Used during the conditioning

of the DN by the service INPQ

Used by

INPQ to build

the response

For the EAGLE to

send a “Connect”

Message to the GMSC

119

INP Configuration

› INPQ also needs to create and activate a local SSN of the

STP. Only one SSN can be created.

› ENT-MAP:PC=TRUESTPPC:SSN=252:RC=10 To create the local SSN

› ENT-SS-APPL:SSN=252:APPL=INP To link the local SSN to the application INP

› CHG-SS-APPL:APPL=INP:NSTAT=ONLINE To put the SSN up. The command rtrv-ss-appl can be used to check

the status of the local SSN.

120

INP Configuration

› Service Selector entry for our INPQ example

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

SSN=252:SERV=INPQ

› Service Selector entry for our INPMR example

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

SNP=E164:SNAI=RNIDN:SSN=6:SERV=INPMR

121

Data Provisioning of the Database Modules

› The Customer‟s Provisioning Database contains the most

current MNP information.

› This information must be sent to the EAGLE STP through the

MPS/EPAP platform to allow it to correctly route MNP traffic.

122

Provisioning Data Flow

EPAP A Active

EPAP BRTDB

RTDB

PDBA

PDBIPDB

Customers

Provisioning

Database

STP1

EPAP A

EPAP B ActiveRTDB

RTDB

PDBA

PDB

STP2

Active

Standby

Database

Module

Database

Module

Database

Module

RTDB

RTDB

RTDB

Database

Module

Database

Module

Database

Module

RTDB

RTDB

RTDB

PDBI

123

Provisioning Configuration

› Provisioning commands are sent to the Active PDBA through

the PDBI port.

› First, the RN must 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

used for Non-Call

related only

(INPMR))

RN value

Command

to add a

new SP or

a RN

Type of this

entity is a

Routing Number

Intermediate

GTT

Insert RN

into the

number

124


› Then the HLR must be entered, if it is not already present.

ent_entity(id A01, type SP, ri SSN, 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 a

Signaling

Point

Final GTT

to this

HLR

125


› To enter a new Ported In number

ent_sub(dn 99633333333, sp A01)

› 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

126


Learning Activities



Module 3

Prepaid IDP Query Relay (IDPR)

with Number Plan Processor (NPP)

130

This module contains the following lessons:

› Lesson 1 Prepaid IDPR

› Lesson 2 IDPR Detailed Call Flow

› Lesson 3 IDPR Configuration

Module 3



Lesson 1

Prepaid IDPR

Module 3

132


› Describe a call flow in a portability environment

› Describe the behavior and advantage of IDPR

› Identify which messages are affected by IDPR

Module 3: Lesson 1

133

Call Flow with Portability

Call Flow with Portability

134

Prepaid SCP with Portability

› The Prepaid SCP has to query the MNP Platform in order to

get the status of the B-Number and know how to charge the

call.

› Two sorts of queries can be sent by the Prepaid SCP:

MAP SRI message to the MNP Platform

MAP ATI message to the MNP Platform

135

(6) Gives the portability

status of the B-Number

Portability Call Flow : SRI Message

MSCPrepaid

SCPSTP(2) IDP Message (2) IDP Message

(4) SRI Message

(3) Doesn‟t have any

information yet if the B-

Number is ported or not

and so doesn‟t know how

to charge this operation

(8) SRI Ack Message

(1) Prepaid mobile = A-Number

MNP

Platform

(5) SRI Message(7) SRI Ack Message

(9) Connect Message

(9) Connect Message

136

Portability Call Flow : ATI Message

MSCPrepaid

SCPSTP(2) IDP Message (2) IDP Message

(4) ATI Message

(3) The message doesn‟t

have any information yet

if the B-Number is ported

or not and so doesn‟t

know how to charge this

operation

(8) ATI Resp Message


MNP

Platform

(5) ATI Message(7) ATI Resp Message

(6) Gives the portability

status of the B-Number

(9) Connect Message

(9) Connect Message

137

IDPR Architecture

IDPR Architecture

138

IDPR Architecture

› The IDP Relay Query for Prepaid (IDPR) control feature is

used when the EAGLE STP is also used as the MNP

Platform.

STP/MNP

IDPR

MSC1

PP SCP 2PP SCP 1 PP SCP 3

STP/MNP

IDPR

MSC2

139

Prepaid IDPR

› The IDPR control feature is used to intercept the IDP

messages and put into the message the information about

the portability status of the B-Number.

› The message is then relayed to the Prepaid SCP per GTT.

› The Prepaid SCP can use the information inserted by IDPR

to know how to charge the call.

› The IDPR optimizes the call flows to the Prepaid SCP

because the IDP message is intercepted, and the portability

information about the B-Number is inserted into the IDP

query before relaying the message to the Prepaid SCP.

140

Prepaid IDPR

MSCPrepaid

SCP

STP/

MNP

(3) Triggers IDPR and adds portability

information (RN or SP) into the CdPN of the

INAP/CAP layer of the message

(4) Fall thru GTT to route the

message to the Prepaid SCP

platform (using GTA of CdPN,

99111111 in this example)

(2) IDP Message (5) IDP Message

GTA= 99111111


(6) Connect Message(6) Connect Message

141

Which MSU are Affected by IDPR

› Only IDP messages to a Prepaid SCP with the correct service key will be affected by the IDPR insertion of information.

› IDPR extracts CdPN from the INAP/CAP layer. In this portion, the Dialed Number (DN) can be:

Non-Ported (Same case as before MNP)

Ported out (An exported DN “lost” by an operator)

Ported-In (An imported DN “gained” by an operator)

› IDP message call flows are processed as follows:

IDP MSUs related with INAP/CAP Protocol

• IDPR inserts SP for Ported-In and Non-Ported DN (if filled into RTDB)

• IDPR inserts RN for Ported-Out DN

Fall thru GTT to route the IDP message to the Prepaid SCP

142






Lesson 2

IDPR Query Detailed Call Flow Ported Out Example

Module 3

146



and service selection steps performed for ported-out DNs


from the IDPR database node

Module 3: Lesson 2

147

Examples Data

›A country (CC=99) with three operators

Operator 1



Operator 2



Operator 3



148

IDPR – Call Flow Example

› Call flow into Operator 1 for a local call

The B-Number has been ported from Operator 1 to Operator 3.

The NAI of the CdPN is international, whereas the DN of CdPN is the

subscriber mobile number (SN).

The DN stored in the RTDB has the format CC+AC+SN.

The CdPN format expected by the Prepaid SCP is RN+CC+AC+SN.

A-Number is a subscriber of Operator 1.

MSCPrepaid

SCP

STP/

MNP

IDP Message IDP Message

GTA= 99111111

Prepaid mobile A-Number=611111112

B-number

CdPN = 111111

149

IDPR – Content of the IDP Message

Dialed Number: 111111

CgPN CdPN

INAP/CAP Fields

… …

NAI=International

NP=E.164

DN=111111

Call flow inside operator 1

MSU sent by

the MSC to the

STP

MSCSTP

MNP

611111112

LAI

LAC=002f

SK BCSM

=210

=2

150

IDPR – Content of the IDP Message

MSU sent by

the MSC to the

STP

SSN=146

TT=0

NP=E164

NAI=INTL

Digit 1=9

ES=BCD

Digit 2=9

Digit 3=1Digit 4=1

Digit 5=1Digit 6=1

Digit 7=1Digit 8=1


CGPA CDPA

SCCP Fields


CAMEL is requested

MSCSTP

MNP

151

IDPR – Service Selector Table

› As GTT is requested, this MSU arrives to the DSM/E5-SM.

The service selector table is looked up first.

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no

Conditioning, Actions

Execution and Formatting

Service

Selector

Table

MSU in from IMT MSU out to IMT

yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no

152

IDPR – Service Selector Table

› Fields extracted from the CDPA by the EAGLE

SSN=146

TT=0

NP=E164

NAI=INTL

Digit 1=9Digit 2=9

Digit 3=1Digit 4=1

Digit 5=1Digit 6=1

Digit 7=1Digit 8=1


ES=BCD

Parameters

extracted from

the CDPA to find

a match in

Service

Selectors Table


…


NAI=INTL:SERV=IDPR

…

IDPR is

triggered

153

IDPR – CSL Checks

› If IDPR service has been triggered, then the type of message

is checked (INAP or CAP); as well as the operation code

which must be IDP.

If the checks fail, the IDPR process is stopped and the MSU

falls thru GTT.

If the checks succeed, the MSU has to pass some screening

tests (CSL checks) to determine if this MSU is destined to IDPR.

• If the MSU fails at any list it will fall thru GTT

154

IDPR – CSL Checks

› CSL is a table with different lists used by different features.

IDPR uses two lists at this stage in the CSL table.

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no

Conditioning, Service and

Formatting Actions

Execution

Service

Selector

Table


yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no

155

IDPR – CSL GTA List

› The list GT is the first list checked. The list GTA contains all

the GTs of the Prepaid SCP Platform in Operator 1.

SSN=146

TT=0

NP=E164

NAI=INTL

Digit 1=9Digit 2=9

Digit 3=1Digit 4=1

Digit 5=1Digit 6=1

Digit 7=1Digit 8=1


ES=BCDGTA extracted from

the CdPN must

match an element of

the GT list if the

MSU is for a Prepaid

SCP Platform.

156

IDPR – CSL SKBCSM List

› The second list is the SKBCSM list which contains a

concatenation of the CAP/INAP field SK and BCSM destined

to IDPR.

SK and BCSM represent a type of service.

CAP/INAP part contains in

decimal

Service Key=210

Event Type BCSM=2

Decimal values

converted to hex,

then concatenated

must match an

element of the list.

210=D2h

2=02h

SKBCSM=D202

157

IDPR – NPP IDPRCDPN

› If the MSU passes through both lists with success, the NPP

IDPRCDPN is performed.

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no


Formatting Actions

Execution

Service

Selector

Table


yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no

158


› This process is called Numbering Plan Processor (NPP) and

is common to different features.

› IDPR uses NPP to provide more flexibility in the treatment of

the number. It is separated in the following steps:

When IDPR has been triggered from SRVSEL, automatically a link is

made with the NPP services called IDPRCDPN

IDPRCDPN is associated with different Action Sets (AS). According to

the incoming parameters, one is chosen which will contain a set of

actions to apply to the MSU.

• The number is conditioned, the service actions of the set are processed

and the number is formatted

Optionally IDPRCGPN is done and finally the MSU fall thru GTT.

159


› When the NPP service IDPRCDPN and the incoming CdPN

NAI match, we next decide which AS to choose.

› This choice is made according to the parameters extracted

from CdPN. (Incoming CdPN parameters are: NAI=INTL,

NP=E164 and DN=111111)

› Three parameters are part of the AS filtering:

The Filter NAI (FNAI=INTL in this example)

The Filter Prefix (FPFX=* in this example)

The Filter Digit Length (FDL=6 in this example)

› When a match is found with the incoming CdPN, then the

associated action set (AS) is applied on this MSU.

160


› An AS has been selected, then the associated actions of this

set will be performed.

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no

Service

Selector

Table


yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no


Formatting Actions

Execution

161


› An Action Set consists of three subsets of actions done in this order:

Conditioning Actions (CA)

Service Actions (SA)

Formatting Actions (FA)

› Each Action Set contains one outgoing FNAI that will be used to set the outgoing NAI of CdPN before the next step(s) (IDPRCGPN and/or GTT).

› In an Action Set, we can define many Service Actions that we are going to apply to our CdPN. In this example, we are going to:

Check if the call terminates to a subscriber in the country of the operator (1st SA)

Perform the RTDB lookup (2nd SA)

163

Conditioning Action

Conditioning Action

164

IDPR – NPP IDPRCDPN : CA

› The first step is to perform the CA to condition our SN to be

ready for both SAs that we want to apply.

› According to our example, we are going to do the following:

Add the CC from the STPOPTS table (99 in our

example)

Add the AC from the extracted LAC of INAP/CAP layer

(002f in our example)

›The conditioning result will be 99002f111111.

165

Service Actions

Service Actions

166

IDPR – NPP IDPRCDPN : SA1

› The first SA is to determine if a call terminates to a subscriber

in the country.

Prior to release 39.x (and so NPP), we used the CSL

list named CCNC to check that. This CCNC list still

exists, and it is looked up at this stage by the Service

Action named CCNCCHECK.

› If a match is found, the process continues. Otherwise, falls

thru GTT.

If the CCNC list contains 99 for example, a match is found with

our previous conditioned DN (best match algorithm).

167


› The second SA is to perform the RTDB lookup.

In our example, the DN in the RTDB is in the format

CC+AC+SN.

› The CA performed in the previous step is done to match the

format contained in the RTDB.

The conditioning result was 99002f111111.

168


› RTDB lookup (At this stage, the international format of the

DN is only used for the RTDB lookup; no change in the msu.)


…

DN 99002f111111, RN d33

…

DSM / E5-SM4G Card

RTDB

This DN has been ported

out to operator3 with RN

d33

This RN will be used to build

the outgoing DN

169


› A match is found and the result of the RTDB lookup is an RN. We use the Triggerless TCAP Relay Options (TTROPTS) table of the EAGLE (chg-ttropts) to determine how to interpret this result.

For example we can consider the lookup is successful only if we find an RN or an SP.

By default, the result is considered successful if we find an RN or an SP. (RNSP) => In our example, we are going to use this default value.

› Other parameters can be set in the table TTROPTS:

To define when the lookup on the CgPN is considered successful

To set the incoming NAI of CdPN/CgPN

To define delimiters for formatting the outgoing DN

To define if the CGPA Check has to be perform (to check if the IPDR should be applied (call inside the country to national number) or not (call outside the country to national number)).

171

Formatting Action

Formatting Action

172

IDPR – NPP IDPRCDPN : FA

› In the third step after the evaluation of the result, the DN will be modified by the FA.

› The CdPN format expected by the Prepaid SCP is RN+CC+AC+SN; thus, we are going to use the Formatting Actions (FA) to build the outgoing DN by:

Adding the RN stored after the RTDB lookup

Adding the CC previously stored when added during the conditioning

Adding the AC previously stored when added during the conditioning

Adding the SN previously stored when added during the conditioning

› The result in our example is d3399002f111111.

› Moreover, the outgoing NAI of CdPN is set regarding the value defined for this action set.

173

IDPR – ENCODING MSU

› Once the CdPN has been formatted, we check if the NPP

service IDPRCGPN is configured or not.

If IDPRCGPN is configured, the whole NPP process starts again by:

• Selecting an action set (according to the incoming CgPN values)

• Conditioning, executing the actions and Formatting of the CgPN

› In our example, IDPRCGPN is not configured; so the CdPN

is encoded.

174

IDPR – ENCODING MSU

› Encoding of CdPN

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no


Formatting Actions

Execution

Service

Selector

Table


yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no

175

IDPR – GTT

› Then, the MSU falls thru GTT by using CDPA parameters

against the gttsel table as a basic GTT process.

DSM / E5-SM4G Card

yesGTT

IDPRCDPN

filter+ Choice of

Action Set using

incoming values

no


Formatting Actions

Execution

Service

Selector

Table


yes

CSL checks

yes

no

yes

noEncoding MSU

IDPRCGPN

no

176


Learning Activities



Lesson 3

IDPR Configuration

Module 3

180


› Configure IDPR

Module 3: Lesson 3

181

IDPR Configuration

› The SS7 configuration into the EAGLE STP is presumed to be already done:

Point codes of the PrePaid SCPs

Links, linksets and routes to those PrePaid SCPs

The information will be used for MTP3 routing.

› As the IDPR feature sits on GTT/EGTT features, those have to be activated prior to IDPR feature activation.

We presume GTT is already configured.

› We also presume the DSM / E5-SM4G cards have already been configured.

182

IDPR Configuration

› IDPR is a control feature activated by the commands ENABLE-CTRL-FEAT:PARTNUM=893016001:FAK=VNK3TR54BVKHX

CHG-CTRL-FEAT:PARTNUM=893016001:STATUS=ON

› Define the Routing Number assigned by the regulator ENT-HOMERN:RN=d11

› Up to a maximum of 100 Home RNs can be entered.

183

IDPR Configuration

› IDPR needs to define some STP Options

CHG-STPOPTS:DEFCC=99:DSMAUD=CCC

Used to condition the number

to an international format

before the RTDB lookup (used

by a CA=CCDEF). Also used

by CgPNCCCHK if set

It is useful to set this

parameter to CCC. In this

case when a record into the

RTDB is corrupted on a

DSM/E5-SM4G card, this

record can be corrected by

loading the correct data from a

mate card

184

IDPR Configuration

› Service Selector entry for National CAP/INAP in E.164

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

:SERV=IPDR

› Service Selector entry for International CAP/INAP in E.164

ENT-SRVSEL:GTII=4:SSN=146:TT=0:NP=E164:NAI=INTL

:SERV=IPDR

Parameters of the CdPN

trigger IPDR

Service triggered if all

the previous parameters

matches the MSU

185

IDPR Configuration

› CSL entries:

ENT-CSL:PN=893016001:LIST=GT:DS=99111111

ENT-CSL:PN=893016001:LIST=SKBCSM:DS=D202

ENT-CSL:PN=893016001:LIST=CCNC:DS=99

• This is the CCNC list used by NPP SA=CCNCCHK

186

IDPR Configuration

› The TTROPTS table contains options used to support IDPR

› The below values are already set as they are the default

values; the purpose here is to show an example of utilization.

› CHG-TTROPTS:NPTYPE=RNSP:CGPACCCK=NONINTL

The result of the RTDB

lookup is considered

successful when we find a

RN or a SP

Do the CgPNCCCK only

when the NAI of CdPN is

not international

187

IDPR Configuration

› The IDPR Feature uses NPP for message processing.

› The NPP process is configured by the use of EAGLE

commands.

› Before starting the NPP configuration, it is useful to have a

look at the predefined configuration of the NPP services with

the command RTRV-NPP-SERV

The displayed result shows for each service configurable with

NPP, the NAI value supported, the SA available with their

predefined precedence number

188

IDPR Configuration

› The first step is to create the Action Set.

› ENT-NPP-AS:ASN=LOCALCALL:

CA1=CCDEF:CA2=ACLAC:CA3=SNX:

SA1=CCNCCHK:SA2=CDPNNP:

FA1=RN:FA2=CC:FA3=AC:FA4=SN:

OFNAI=INTL

Second CA add the LAC from LAI and put

the value in the variable AC

Third CA stores the SN in the variable SN

Trigger the

CCNC check by

using the CSL

list : CCNC

Name of the AS

First CA to

add the CC

and put the

value to the

variable CC This SA perform the

RTDB lookup on the

CdPN

Format the outgoing DN by

concatenation of the values

stored in the different variablesFormat the

Outgoing CdPN

189

IDPR Configuration: Conditioning Action

› ACLAC – Area Code/Location Area Code

Get AC from LAC

If Area Code is not included in the incoming DN, the ACLAC

should be obtained from LAI.

IF AC is present in LAI, ACLAC will be used in the CA and also

appended to the incoming digit string (SN).

190

IDPR Configuration: Service Actions

ASDLKUP Additional Subscriber Data (ASD) Lookup

CCNCCHK Country Code/Network Code Check

CDPNNP CdPN Number Portability

CGPNASDRQD CgPN ASD required

CGPNGRNRQD CgPN Generic Routing Number (GRN)

Required

CGPNNPRQD CgPN Number Portability Required

GRNLKUP GRN Lookup

LACCK Location Area Code Check

INPRTG INP Routing

SKGTARTG Service Key GTA Routing

IDPRCDPN(X) Service Actions Parameters

191

IDPR Configuration: Service Action

ASDLKUP Additional Subscriber Data (ASD) Lookup

CGPNNP CgPN Number Portability

GRNLKUP GRN Lookup

INPRTG INP Routing

IDPRCGPN Service Action Parameters

192

IDPR Configuration: Formatting Actions

FA Parameter Description

sn Subscriber number

dn Dialed number (AC+SN)

zn Internationally formatted dialed no.

(CC+AC+SN)

ac Area code

rn Routing number

sp Service provider

cc Country code

fpfx Filter prefix

pfxa - pfxf Prefix A through F

dlma -dlmp Delimiter A thru P

asd Additional subscriber data

orig Incoming digit string

grn Generic routing number

vmid Voice mail identifier

193

IDPR Configuration

› In the processing order, the selection of the AS (called SRS)

according to the incoming values of CdPN is done before

executing the actions of the AS.

› In the provisioning order, the SRS creation is done after the

AS creation because the ASN must exist before we can point

to it. (same logic as with GTTSET and GTTSEL)

› ENT-NPP-SRS:SRVN=IDPRCDPN:

FNAI=INTL:FPFX=*:FDL=6:ASN=LOCALCALL

Incoming selectors:

INTL CdPN, all prefixes,

length of SN=6

ASN used if the incoming

selectors match with the

incoming CdPN

Name of the NPP service created with the command chg-npp-serv

194

IDPR Configuration: Filters and Action/Service Name

› :asn= (mandatory)

Action set name. This parameter specifies the name of the AS.

› :fdl= (mandatory)

Filter digit length. This parameter specifies the number of digits on the incoming digit string that is filtered by the NPP. Range: 1-32 , *

› :fnai= (mandatory)

Filter nature of address indicator. This parameter specifies the filter Nature of Address Indicator (NAI) class. Range: intl, natl, nai1, nai2, nai3, unkn

› :fpfx= (mandatory)

Filter prefix. This parameter specifies the prefix used to filter incoming digit strings. Range: 1-16 digits , * , ?

› :srvn= (mandatory)

Service name. This parameter specifies the name of the NPP service. Range: nppt , idprcdpn , idprcgpn , tif , tif2 , tif3

195

IDPR Configuration: Activation

› Activation of the IDPRCDPN service:

› CHG-NPP-SERV:SRVN=IDPRCDPN:STATUS=ON

197

Multiple IDP Relay Instances


198


› Need:

The customer needs the Eagle STP to allow processing of IDP

message to be tailored based on the Service Key parameter,

CdPN, and CgPN.

• An example is when a single Eagle database catering to multiple

domains such as mobile NP for country X, mobile NP for country Y,

IN Service NP for country X etc, where the IDP messages from the

different domains may be differentiated by one or more of Service

Key parameter, CdPN, and CgPN.

› Each type of IDP message processing flow is referred to as

an IDP Relay instance.

199


› The Multiple IDP Relay Instances feature allows the existing

Prepaid IDP Query Relay feature to support up to 4

IDPRCDPN NPP services (IDPRCDPN, IDPRCDPN2,

IDPRCDPN3, and IDPRCDPN4 ) for Called Party

modifications.

› Each service can be configured separately to process an

incoming IDP message in a different way.

› The filters and Action Sets in the NPP Service Rules that are

provisioned for IDP Relay services are used to determine

what NPP processing is required.

200


chg-npp-srs:

srvn=idprcdpn4:fpfx=98:fnai=intl:asn=cdset2:fdl=9

rtrv-npp-srs

tekelecstp 10-10-28 16:41:44 EST EAGLE 43.0.0

Command entered at terminal #4.

SRVN FPFX FDL FNAI ASN

-------------------------------------------------------------------------------------------------------------

idprcdpn 91 12 Intl cdset1

idprcdpn2 91 10 natl cdset2

idprcdpn3 * * intl cdset3

idprcdpn4 98 9 intl cdset2

201

TTR Test Tool

Triggerless TCAP Relay Test Tool

202

TTR Test Tool

› The Test Tool can be used to send provisioned TTR (INAP

and CAP) messages to test the number conditioning and

formatting for the IDPRCDPN, IDPRCDPN2, IDPRCDPN3,

IDPRCDPN4, and IDPRCGPN services.

› The test message is never sent out to the network.

203

TTR Test Tool

The Test Tool provides the following capabilities:

› Define up to 10 TTR test messages in the TSTMSG table.

› Invoke IDP Relay and NPP to process the a test message.

› Generate a report of the actions taken and the results of the

test.

204

TTR Test Tool Commands

› chg-ttr-msg

chg-ttrmsg: msgn=1:tcaptype=INAP:cdpnnai=4

:cdpadgts=12457896abcd:cgpnnai=4

› tst-msg

tst-msg:loc=1103:prot=ttr:feat=ttr:msgn=1:mode=debug

› rtrv-ttr-msg

rtrv-ttr-msg:msgn=1

Note: Refer to the IDP Related Feature Manual and the Commands Manual for

a detailed list of test message parameters that can be used with the TTR Test

Tool.

205






Module 4

IDP A-Party Blacklist & IDP A-Party Routing

208

After this Module, you should be able to:

› State the purpose and describe the function of the IDP A-

Party Blacklist and IDP A-Party Routing features

› Differentiate between IDP A-Party Routing and IDP SK

Routing

› List measurements for these features

› Identify commands for configuration of these features

Module 4

IDP A-Party Blacklist

IDP A-Party Blacklist

210

A-Party Blacklist Need

› When a subscriber is blacklisted for some reason like not

paying the phone bill, an operator would like to forward the

call to a predetermined number like a customer care number

when any call origination is attempted.

A trigger detection point is put in for all post paid subscriber profile to

generate an IDP query.

The IDP query is received by EAGLE with an EPAP based subscriber

database.

The subscribers that are to be flagged as blacklist are entered with a

flag along with any Routing Number necessary to re-route the call.

211

BLKLSTQRY / BLKLSTRLY Service Actions

› BLKLSTQRY (Query – Response)

Inclusion of the BLKLSTQRY NPP Service Action in a ruleset

indicates that the query response mode handling is desired for

selected incoming IDP Query messages.

The BLKLSTQRY SAH determines if a CONNECT or a

CONTINUE message should be sent to the originating SSP.

› BLKLSTRLY (Relay)

Inclusion of the BLKLSTRLY NPP Service Action in a ruleset

indicates that the relay mode handling is desired for selected

incoming IDP Query messages.

The BLKLSTRLY SAH determines if a CONNECT message

should be sent to the originating SSP.

212

A-Party Blacklist Query-Response Scenarios

EAGLE /

EPAP

RTDB

Switch

Connect:

BLKLSTQRY Service

provisioned for CgPN.

CgPN is marked as Blacklist

Subscriber in EPAP/RTDB

and GRN is present.

IDP

Connect Response

EAGLE /

EPAP

RTDB

Switch

Continue:

BLKLSTQRY Service

provisioned for CgPN.

CgPN is not marked as

Blacklist Subscriber in

EPAP/RTDB OR GRN is not

present OR CgPN is not

found in RTDB lookup.

IDP

Continue Response

213

Post-NPP Processing

› The IDP Relay feature post-NPP processing function handles IDP A-Party

Blacklist post-NPP processing.

Based on the IDP Relay feature status and the possible BLKLSTQRY Service Action

Handler execution results, post-processing encodes the Connect or Continue response.

On completion of feature specific handling, a generic translation can be applied to map

success/failure results into required measurements pegs and rept-stat-sccp statistics.

› In the post-processing handler for IDP A-Party Blacklist Query, network

conversion is not allowed while sending the response.

If the resulting PC is of a different network domain, or the Connect or Continue results in

any encoding or decoding failures, then the IDP A-Party Blacklist Query processing is

considered to be a failure.

Based on the “return-on-error” flag in the incoming IDP message, either the UDTS will

be sent back to the originator or the message is discarded. In case of any failures in

message processing, feature specific post-processing will also set unique execution

error codes that can be used to identify the processing applied to the IDP message.

214

IDP A-Party Blacklist Relay

EAGLE /

EPAP

RTDB

SwitchIDP

Prepaid

SCP

Blacklist conditions not met.

Execute other applicable for

this message IDPR services

OR in absence of those, Fall

Thru to GTT Routing

Prepaid / GTT

translated SCP

2

1

CgPN Subscriber Blacklisted

& GRN present – Connect

Response

215

A-Party Blacklist Service Actions Summary

Service Action Description Function Precedence

BLKLSTQRY Blacklist Query Provides query

response mode

handling for selected

incoming IDP Query

messages.

90

BLKLSTRLY Blacklist Relay Provides relay mode

handling for selected

incoming IDP Query

messages.

90

CgPNSvcRqd Calling Number

Lookup

Sets a flag to cause

the IDPRCgPN

service to be invoked

for the message.

60-

• IDP A-Party Blacklist provides Service Action Handlers for the NPP Service

Actions that are specific to the feature. IDP A-Party Blacklist and NPP perform the

following functions:

• RTDB lookup

• Interpretation of results from RTDB lookups

• NPP processing of Service Actions that are used for IDP A-Party Blacklist

216

A-Party Blacklist Measurements

› The following measurement registers are defined for the IDP

A-Party Blacklist feature. All registers added in this feature

are reported in the STP system Total (SYSTOT-STP) report.

IDPBKLCONN: Total number of IDP messages received that matched

the blacklist criteria and a CONNECT response was generated.

IDPBKLCONT: Total number of IDP messages received that did not

match the blacklist criteria and a CONTINUE response was generated.

IDP A-Party Routing

IDP A-Party Routing

218

IDP A-Party Routing Components

› The IDP A-Party Routing feature has two components:

IDP A-Party Routing uses the A-Party (CgPN) parameter of an

IDP or IDPSMS message

IDP Service Key Routing uses the Service Key and EventType

BCSM parameters in the incoming IDP or IDPSMS message.

Prepaid

SCP

EAGLE /

EPAP

RTDB

MSC

Prepaid

SCPSCP

IDP/IDPSMS

CGPNRTG Service Provisioning for CgPN

IDP Routing, CgPN,

Valid Prepaid Type

CgPN has one of the valid

Prepaid Types in EPAP and

PPSOPTS table has all the required

Data for RoutingFailure

UDTS or discard

IDP Routing,

Valid Prepaid Type

Load-Sharing Up to

32 servers using

MNR/MAPSET

1

3

Not a Prepaid Subscriber OR

PPSOPTS table does not have required

data for routing to Prepaid Server.

Fall-Thru to other Routing

2

IDP A-Party Routing

Prepaid Server 1

Prepaid Server 32

GTT Routed SCP

Destination

IDP Service Key Routing

Prepaid

SCP

EAGLE /

EPAP

RTDB

MSC

Prepaid

SCPSCP

IDP/IDPSMS

SK Routing feature is enabled and turned on.

IDP/IDPSMS Routing

Valid Prepaid Type in

skbcsm CSL list and

PPSOPTS table has all

data for routing. Failure

UDTS or discard

Load-Sharing Up to

32 servers using

MNR/MAPSET

1

3

2

Prepaid Server 1

Prepaid Server 32

GTT Routed SCP

Destination

No Prepaid Type in SKBCSM

list OR PPSOPTS table does

not have requirad data for

routing to Prepaid Server.

Fall-Thru to Other Routing.

IDP/IDPSMS Routing

A-Party Routing & SK Routing Interaction

A-Party Routing

turned ON

CGPNRTG SA

Provisioned

SK Routing

turned ON

TTRPOPTS:

CGPNSKRTG

Routing Decisions

No N/A No N/A Fall –Thru to GTT

Yes N/A SK Routing

Yes No No N/A Fall –Thru to GTT

Yes N/A SK Routing

Yes Yes Insufficient

Data

No N/A Fall –Thru to GTT

Yes Off Fall –Thru to GTT

On Fall – Thru to SK

Routing

Sufficient

Data

N/A N/A A-Party Routing

A-Party Routing Service Actions

› IDP A-Party Routing provides Service Action Handlers for the NPP Service

Actions that are specific to IDP A-Party Routing. IDP A-Party Routing and NPP

perform the following functions:

RTDB lookup

Interpretation of results from RTDB lookups

NPP processing of Service Actions that are used for IDP A-Party Routing

Service Action Description Function Precedence

CGPNRTG CgPN A-Party or

Service Key

Routing

Determines whether CgPN

routing and/or SK routing

should be attempted during

post-NPP processing.

80

CGPNSVCRQD Calling Number

Lookup

Sets a flag to cause the

IDPRCGPN service to be

invoked for the message.

60

223

A-Party Routing Measurements

› IDPAPTYRTD: Total number of IDP/IDPSSM messages that were selected for A-Party

Routing service, and were successfully routed based on A-Party PPSOPTS routing data

(routing data associated with the RTDB Prepaid Type assigned to the A-Party digits).

› IDPAPTYGTT : Total number of IDP/IDPSSM messages that were selected for A-Party

Routing service, but fell through to GTT (with or without having attempted Service Key

Routing first).

› IDPAPTYSKR : Total number of IDP/IDPSSM messages that were selected for A-Party

Routing service, but fell through to Service Key (SK) Routing, and were successfully routed

based on SK/BCSM PPSOPTS data (routing data associated with the RTDB Prepaid Type

assigned to the SK/BCSM entry).

• IDPSKGTT: Total number of IDP/IDPSSM messages that were selected for Service Key

Routing (without having first gone to A-Party Routing), but fell through to GTT.

• IDPSKRTD: Total number of IDP/IDPSSM messages that were selected for Service Key

Routing (without having first gone to A-Party Routing), and were successfully routed based

on SK/BCSM PPSOPTS data.

224






Module 5

Info Analysis Relay with NPP

228

After this Module, you should be able to:

›State the purpose and describe the function of the

IAR feature

›Describe NPP for this feature

›Describe control requirements for this feature

Module 5

Introduction to IAR

Introduction to IAR

230

IAR Operation Overview

IAR Base

IAR NP IAR ASD IAR GRN

The IAR Base feature

intercepts and processes

Info Analyzed Relay

(a.k.a. Analyzed

Information) messages

that are sent from an

MSC to a prepaid SCP.

The IAR Base feature

forms a base upon which

the IAR NP, IAR ASD,

and IAR GRN features

are built.

Number

Portability

Additional

Subscriber Data

Generic

Routing Number

IAR and IDP Equivalents

IDP INAP Layer Parameter Analyze Information IS41 Layer Equivalent

Parameter Name Acronym Parameter Name Acronym

Called Party Number CdPN Destination Digits DESTDGTS

Calling Party Number CgPN Calling Party Number Digits CGPNDGTS

Service Key SK Trigger Type TRIGTYPE

IDP & Analyzed Information Parameter Equivalents

TTROPTS (Triggerless TCAP Relay) & TATROPTS (Triggerless ANSI TCAP Relay)

Existing TTROPTS Equivalent TATROPTS

cgnptype cgnptype

cgpaccck cgpaccck

cgsnai N/A

dfltrn dfltrn

nptype cdnptype

snai N/A

sporttype sporttype

IAR Call Flows (Own vs. Out Subscriber)

Prepaid

SCPEAGLE

RTDB

MSC

ANLYZD Message

CdPN=DN

ANLYZD Response

DGTSDIAL

ANLYZD Message

Unmodified CdPN

ANLYZD Response

DGTSDIAL

“Own” Subscriber Relay

Prepaid

SCPEAGLE

RTDB

MSC

ANLYZD Message

CdPN=DN

ANLYZD Response

DGTSDIAL

ANLYZD Message

CdPN=RN+DN

ANLYZD Response

DGTSDIAL

“Out” Subscriber Relay

233

EAGLE Interactions

› EPAP. EPAP is used to manage subscriber information. The

IAR NP, IAR ASD, IAR GRN, and S-Port features all relate to

the query and interpretation of subscriber data.

› Gateway Screening (GWS). GWS can be used to select

incoming traffic on a LIM card for Service Module card

processing.

› GTT. The GTT feature must be used to send route-on-GT

messages toward their proper destination.

› NPP. The IAR Base feature uses two NPP services to

manipulate message parameters and interpret subscriber

data.

234

EAGLE Interactions

EAGLE

IAR Base Feature

LIM Card Service Module Card

PC- and GT- routed messages via specific linksets

GT-routed message

Gateway Screening Feature

235

IAR Base Message Processing

EAGLE Service Module Card

TTRService Selector

IARPre-Processing

IARNPP Processing

IARPost -Processing

ModificationsIAR AppliesIAR Selected

Message Routed Via LIM Card

Message From LIM Card

Number Processing Plan for IAR

Number Processing Plan for IAR

TTR Service Selector IAR (ANSI) and IDPR (ITU)

ANSI

TCAP

Detected

IAR

Base

Feature

“ON”

IAR Pre-

Processing

ITU

TCAP

Detected

IDPR

Feature

“ON”

IDPRTT

R S

erv

ice

Se

lec

tor

IAR Pre-Processing

CdPA

Screening

TCAP

Decoding

CgPA

DefCC

Check

Trigger

Type

Screening

NPP Service

Processing

IAR Pre-

Processing

Numbering Plan Processor

IARCDPN

Service

“ON”

NPP Service

ProcessingApply IARCDPN

IARCGPN

Invoked

IARCGPN

Service

“ON”

Apply IARCGPN

IARCDPN

Service

FAE

IAR Post-

Processing

NPP Service Actions

Service Action Feature Precedence IARCDPN IARCGPN

ASDLKUP IAR ASD 50 YES YES

CCNCCHK IAR Base 100 YES no

CDIAL IAR Base 10 YES YES

CDPNNP IAR NP 80 YES no

CGPNASDRQD IAR ASD 50 YES no

CGPNGRNRQD IAR GRN 50 YES no

CGPNNP IAR NP 80 no YES

CGPNSRVRQD IAR Base 60 YES no

GRNLKUP IAR GRN 50 YES YES

Number Portability (Success Criteria)

NPTYPE Option Success Criteria

RN When an RTDB match is found with an RN entity.

SP When an RTDB match is found with an SP entity.

RNSPWhen an RTDB match is found with an RN or SP entity.

RNSPDN

ALWAYS Always

ANYMATCH When an RTDB match is found.

NP functionality is applied by both the CDPNNP and CGPNNP Sas.

The success criteria above are used when NP functionality is applied. If the

success criteria are not met then the CDPNNP and CGPNNP SA handlers will

request that FAE be skipped.

NPTYPE RN and SP Population

NPTYPE RTDB Has RN Entity SP Entity and DFLTRN SP Entity No DFLTRN

RN RN FA set to RTDB RN.

SP FA is not changed.

(failure) (failure)

SP (failure)

RN FA set to DFLTRN.


RN FA is not changed.

SP FA set to RTDB SP.

RNSP

RN FA set to RTDB RN.


RNSPDN

ALWAYS

ANYMATCH

The FA population described below only occurs when the success criteria are

met. Note that the purpose of the TATROPTS:DFLTRN option is to override

an SP entity when one is provisioned in the RTDB.

When the RTDB does not contain an RN or SP entity, but the NPTYPE

success criteria are still met (i.e. ALWAYS or ANYMATCH), then neither the

RN nor the SP FA are not changed.

245

Notes on Service Portability (S-Port)

› The Service Portability feature will be discussed in more

detail in the next Module. The S-Port functionality is only

applied by the CDPNNP and is only applied to “own” network

subscribers.

› S-Port is applied based on the value of the

TATROPTS:SPORTTYPE option.

› If the S-Port feature is ON then the CDPNNP SA will prefer S-

Port functionality over NP functionality.

IAR Post-Processing Tasks

NPP

Success

Message

should be

modified?

Route

Message

IAR Post-

Processing

Encode message

with modified

parameter(s)

No

Yes

IAR

Po

st P

roce

ssin

g

Route Message

GTT

Required?Route Message

Pass the

message on for

MTP routing

Pass the

Message to GTT

Done

No

Yes

IAR-Related Features Provisioning

IAR-Related Features Provisioning

250

IAR Features Provisioning

› IAR provisioning is similar to IDP and other control features

utilizing NPP. Standard EAGLE commands are used,

including:

enable/chg/rtrv-ctrl-feat

ent/chg/dlt/rtrv-csl

ent/chg/dle/rtrv-srvsel

chg/rtrv-stpopts

chg/rtrv-tatropts

ent/chg/rtrvdlt/rtrv-npp-as, nppsrs, npp-serv

chg/rtrv-tatr-msg, tst-msg

rept-stat-sccp

› Detailed provisioning steps and commands are found in your

“Feature Manual – IDP and IRA”

251

Learning Activity: Module 5

Learning Activities



Module 6

Service Portability

256

After this module of instruction, you should be able to:

› State the purpose and describe the function of the Service

Portability feature

› Describe control requirements for this feature

Module 6

257

Service Portability Defined

› Service Portability is a term used to describe a special type

of number portability:

It allows a subscriber to keep their phone number when

switching from one type of network/service technology to

another within the same operator’s network

• CDMA (IS41)<> GSM

• Fixed <> Mobile

• Fixed <> VoIP

• Mobile <> VoIP

258

Other Terminology

› Own-network CDMA subscriber: A subscriber belonging to the carrier‟s

own IS41 network, with RTDB entry containing NE=RN and PT=0

› Own-network GSM subscriber: A subscriber belonging to the carrier‟s

own GSM network, with RTDB entry containing NE=SP (generally these

subscribers will also be provisioned with PT=5, but the code only looks at

SP for decisions).

› “Circles”: Same as service area, calling region, or local area, etc. A

geographic area serviced by an operator within which Number Portability

applies.

› Note that Service Portability only deals with own-network subscribers.

Service Portability Digits

Operator XXX

CDMA

Network

Operator XXX

GSM

Network

LSA (Circle)

Own-network subscriber

can port to different

technology in same LSA

Prefixes provide knowledge

of network technology +

circle information for own-

network subscriber to apply

correct routing & billing

Allows the operator to

use a different set of

digits when formatting the

called party in responses

and relayed messages

Service portability digits:

cLRN = CDMA subscriber

gLRN = GSM subscriber

EAGLE uses RTDB GRN

field for provisioning the

c/gLRN digits

260

IS41 GSM Migration vs. Service Portability

› Migration

Prefixes to help handle

migrated customers

• IS412GSM

• GSM2IS41

Provides information on only

one leg of the call

Prefix provided only to

migrated subscriber

Impacts message flows

› Service Portability

Provides own-network

network technology & “circle”

using the per subscriber

GRN variable in EPAP RTDB

database

Specifies which subscriber

technology type requires use

of this routing data for

prefixing

Operator can provision a

unique GRN for each of its

own-network subscribers as

the routing prefix

Does not modify message

flow

261

Supported Number Portability Features

› INAP-based Number Portability (INP)

› ANSI-41 INP Query (AINPQ)

› IDP Query Relay (IDPR)

› Info Analyzed Relay (IAR)

› G-Port SRI Query for Prepaid

› ATINP Query

› TIF Number Portability (TIF NP, Release and Relay)

› MO-based IS41 & GSM SMS NP

› To enable Service Portability for a given feature requires both:

The Service Portability Feature Access Key (FAK)

The corresponding FAK for any one of the above NP features.

262

Baseline Limitations

› Mutually exclusive features:

TIF NP if GRN service action is used

IDPR if GRN service action is used

V-Flex

IDP A-Party blacklist

› For features that offer called and calling party functionality

(e.g. TIF NP, IDPR), Service Portability applies only to the

called party.

INPOPTS / AINPOPTS / TTROPTS Parameter(SPORTTYPE)

SPORTTYPE specifies whether Service Portability will apply to INP, AINP. & IDPR

Query for own-network subscribers (RN/0 and SP). If Service Portability is

applicable, GRN digits shall be used in place of RN digits.

Parameter Value Action in the STP

SP

OR

TT

YP

E

(In

itia

l valu

e i

s N

ON

E)

NONE

GSM

CDMA

ALL

Existing behavior. Service Portability not indicated.

Service Portability indicated for messages to own-network GSM

subs (EPAP entity type SP); Service Portability not indicated for

own-network CDMA subs.

Service Portability indicated for messages to own-network CDMA

subs (EPAP entity type RN/0); Service Portability not indicated for

own-network GSM subs.

Service Portability indicated for messages to own-network GSM

and CDMA subs (entity type RN/0 and SP).

264

INPOPTS / AINPOPTS /TTROPTS Parameter (DFLTRN)

The DFLTRN (Default RN) parameter specifies which digits should be used in the

case of non-Service Portability scenarios in the query flow when an RTDB match

is found for an own-network subscriber (RN/0 or SP).

Parameter Value Action in the STP

DF

LT

RN

(In

itia

l valu

e i

s N

ON

E)

NONE Existing behavior (use RN or SP associated with

RN/0 or SP subscriber)

1-15 hex

digits String of hexadecimal digits, 1-15 digits long

INP / AINP Without and With Service Portability

EAGLE

INAP IDP (or TCAP Query)

(CdPN = DN)

Connect

(DRA = 1234+DN)

RTDB

Without

Service

Portability

EAGLE

INAP IDP (or TCAP Query)

(CdPN = DN)

Connect

(DRA = 8888+DN)

RTDB

With

Service

Portability

MSC

MSC

RN

GRN

IDPR Without and With Service Portability

Prepaid

SCPEAGLE

RTDB

MSC

IDP Message

CdPN = DNIDP Message

RN or SP + DN

Connect

Message

Connect

Message

Without

Service

Portability

Prepaid

SCPEAGLE

RTDB

MSC

IDP Message

CdPN = DNIDP Message

GRN + DN With

Service

PortabilityConnect

Message

Connect

Message

IAR Without and With Service Portability

Prepaid

SCPEAGLE

RTDB

MSC

ANLYZDMessage

CdPN = DNANLYZD Message

GdPN=GRN + DN With

Service

Portability

Prepaid

SCPEAGLE

RTDB

MSC

ANLYZD Message

CdPN=DN

ANLYZD Response

DGTSDIAL

ANLYZD Message

CdPN=RN+DN

ANLYZD Response

DGTSDIAL

ANLYZD Response

DGTSDIAL

ANLYZD Response

DGTSDIAL

Without

Service

Portability

268

Control Feature Activation

› Before Service Portability feature can be enabled, the INP, AINP Query,

or IDPR feature must be enabled and turned on.

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

› Features can be turned on and off. Turning off only disables the message

processing – configuration parameters will remain in opts table.

enable-ctrl-feat:partnum=893034301:fak=<Feature Access Key>

chg-inpopts:sporttype=(none, gsm, cdma, or all)

(-or ainpopts)

(-or ttropts)

chg-inpopts:dfltrn=(none or 1-15 hex digits)

(-or ainpopts)

(-or ttropts)


RTRV-INPOPTS (or AINPOPTS, TTROPTS) Example

tekelecstp 09-04-28 15:43:00 EST EAGLE 41.1.0

INP (or AINP or IDPR)OPTIONS

-----------------------

DEFMCC = NONE

DEFMCC = NONE

SRFADDR = NONE

MSRNDIG = RN

DEFMAPVR = 1

SRIDN = TCAP

IS412GSM = NONE

MSISDNTRUNC = 0

SPORTTYPE = ALL

DFLTRN = 12345

Optional S-Port Feature

S-Port Subscriber Differentiation

Feature

272


› S-Port Subscriber Differentiation is an optional feature that

can be used with Service Portability to allow use of

provisioned ASD digits in place of GRN digits as an

alternative Routing Number for own-network subscribers.

For example, the ASD can be used as the subscriber‟s private

routing number (for message relay features) and the GRN as

the subscriber‟s public routing number (for query/response

features).

273


› When the Service Portability feature and the S-Port

Subscriber Differentiation feature is on and provisioned , and

Service Portability is applicable, then provisioned ASD digits

are used in place of GRN digits.

› Subscribers without ASD provisioned will follow standard

Service Portability processing and will always use GRN

274

S-Port Subscriber Differentiation Provisioning

› The S-Port Subscriber Differentiation feature must be

enabled and turned on using the feature part number

893037901 and a feature access key

enable-ctrl-feat:partnum=893037901:fak=<Feature Access

Key>


› Provision the SCCPOPTS SUBDFRN option to specify

whether the S-Port Subscriber Differentiation is on or off.

chg-sccpopts:subdfrn=on

275




277

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!

tk303 eagle r43.0 epap r14.0 v4.0 slides

Documents