974-05

34
5-1 Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003 "Confidential information -- may not be copied or disclosed without permission". Lesson 5 SCCP Layer

Upload: hungpm2013

Post on 05-Feb-2016

214 views

Category:

Documents


0 download

DESCRIPTION

974-05

TRANSCRIPT

Page 1: 974-05

5-1Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Lesson 5

SCCP Layer

Page 2: 974-05

5-2Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Objectives

Given site specific information and appropriate documentation, discuss the signaling Connection Control Part layer, including the following information:

• Signaling Connection Control Part layer

– SCCP Routing Control

– SCCP Connectionless Control

– SCCP Connection-oriented Control

– SCCP Management Control

• SCCP Addressing

• Address Manipulation

• SCCP Tables

Given site specific information and appropriate documentation, discuss the signaling Connection Control Part layer, including the following information:

• Signaling Connection Control Part layer

– SCCP Routing Control

– SCCP Connectionless Control

– SCCP Connection-oriented Control

– SCCP Management Control

• SCCP Addressing

• Address Manipulation

• SCCP Tables

Page 3: 974-05

5-3Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Signaling Connection Control Part (SCCP)

Signaling ConnectionControl Part (SCCP)

Signaling ConnectionControl Part (SCCP)

Radio Access Network

Application Part(RANAP)

Radio Access Network

Application Part(RANAP)

TransactionCapabilitiesApplicationPart (TCAP)

TransactionCapabilitiesApplicationPart (TCAP)

MobileApplication

Part(MAP)

MobileApplication

Part(MAP)

ISDNUserPart

(ISUP)

ISDNUserPart

(ISUP)

MessageTransfer

Part(MTP)

Network

Link

Physical

Base Station Subsystem

Application Part (BSSAP)

Base Station Subsystem

Application Part (BSSAP)

BSSMAPBSSMAP DTAPDTAP

Page 4: 974-05

5-4Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Topics

The information in this lesson is divided into the following sections:

• signaling Connection Control Part layer

• SCCP addressing

• Address manipulation

• SCCP tables

The information in this lesson is divided into the following sections:

• signaling Connection Control Part layer

• SCCP addressing

• Address manipulation

• SCCP tables

Page 5: 974-05

5-5Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

A logical connection is

maintained during transfer of data

A logical connection is

maintained during transfer of data

A logical connection is not maintained during

transfer of data

A logical connection is not maintained during

transfer of data

SCCP Signaling Classes

Class 0 - Basic Connectionless Class

Messages transported independently of one another, may be out of sequence.

Class 0 - Basic Connectionless Class

Messages transported independently of one another, may be out of sequence.

Connectionless Services

Connectionless Services

Connection-Oriented Services

Connection-Oriented Services

SCCP ServicesSCCP Services

Some RANAP messages use SCCP Class 0

Class 1 - Sequenced MTP Connectionless Class

MAP messages in sequence at the MTP level.

Class 1 - Sequenced MTP Connectionless Class

MAP messages in sequence at the MTP level.

Class 2 - Basic Connection-Oriented Class

A bidirectional, logical connection is maintained throughout data transfer.

Class 2 - Basic Connection-Oriented Class

A bidirectional, logical connection is maintained throughout data transfer.

Class 3 -Flow Control Connection-Oriented Class

Like Class 2, but also has flow control (expedited data transfer).

Class 3 -Flow Control Connection-Oriented Class

Like Class 2, but also has flow control (expedited data transfer).

MAP messages useSCCP Class 1

Some RANAP messages useSCCP Class 2

Page 6: 974-05

5-6Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

SCCP Message Format

F CK SIO LI FIB FSN BIB BSN F

SCCP InformationSCCP

Message

Optional PartMandatory

VariablePart

MandatoryFixed Part

CallingParty

Address

CalledParty

Address

SLS OPC DPC

Message Signal Unit 1st Bit Transmitted

- - >

MessageType

MTPRouting Label

SIF

Page 7: 974-05

5-7Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Address Indicator

8 7 6 5 4 3 2 1

Reserved for

national use

Routing indicator

Global title indicatorSSN

indicator

Point code

indicator

Page 8: 974-05

5-8Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Address

8 7 6 5 4 3 2 1

Signaling point code

Subsystem number

Global title

Page 9: 974-05

5-9Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Bits

8 7 6 5 4 3 2 10 0 0 0 0 0 0 0 SSN not known/not used0 0 0 0 0 0 0 1 SCCP management0 0 0 0 0 0 1 0 reserved for ITU-T allocation0 0 0 0 0 0 1 1 ISDN user part0 0 0 0 0 1 0 0 operation, maintenance and administration part (OMAP)0 0 0 0 0 1 0 1 mobile application part (MAP)0 0 0 0 0 1 1 0 home location register (HLR)0 0 0 0 0 1 1 1 visitor location register (VLR)0 0 0 0 1 0 0 0 mobile switching centre (MSC)0 0 0 0 1 0 0 1 equipment identifier centre (EIC)0 0 0 0 1 0 1 0 authentication centre (AUC)0 0 0 0 1 0 1 1 ISDN supplementary services0 0 0 0 1 1 0 0 reserved for international use0 0 0 0 1 1 0 1 broadband ISDN edge-to-edge applications0 0 0 0 1 1 1 0 TC test responder0 0 0 0 1 1 1 1

to0 0 0 1 1 1 1 1

reserved for international use

0 0 1 0 0 0 0 0to

1 1 1 1 1 1 1 0reserved for national networks

1 1 1 1 1 1 1 1 reserved for expansion of national and international SSN

Subsystem Number

Page 10: 974-05

5-10Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Bits

8 7 6 5

0 0 0 0 unknown

0 0 0 1 ISDN/telephony numbering plan (ITU-T E.163 and E.164)

0 0 1 0 generic numbering plan

0 0 1 1 data numbering plan (ITU-T X.121)

0 1 0 0 telex numbering plan (ITU-T F.69)

0 1 0 1 maritime mobile numbering plan (ITU-T E.210, E.211)

0 1 1 0 land mobile numbering plan (ITU-T E.212)

0 1 1 1 ISDN/mobile numbering plan (ITU-T E.214)

1 0 0 0

to spare

1 1 0 1

1 1 1 0 private network or network-specific numbering plan

1 1 1 1 reserved

Numbering Plan (NP)

The numbering plan (NP) is encoded as follows:

Page 11: 974-05

5-11Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Deriving a CdPA (Update Location Example)

New VLR HLR Old VLR

UL

ISD

ISD Ack

UL Ack

CL

CL Ack

CdPA derived from:

Received CdPA (IMSI as a GT)

Received CgPA

Received CdPA(VLR number as GT)

Received CgPA

Received CgPA

Received CgPA

Page 12: 974-05

5-12Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Inter-PLMN Address Manipulation—GTT

A = Country A international gatewayB = Country B international gateway

Country ANetwork

Country BNetwork

InternationalCCS7

Network

INTLRS HLRRS

C7INTLRSUpdate Location

ISC B

ISC A

DMS-STP

DMSHLR

(SCP)

DMSVLR

Page 13: 974-05

5-13Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Global Title Translations (GTT)

MAP-VLRPC = 1SSN = 7GT = 123

CdPA:RI = GTGT = 456DPC = 2CgPA:RI = GTGT=123

International GatewayPC = 2

International GatewayPC = 4

MAP-HLRPC = 5SSN = 6GT = 456

CdPA:RI = GTGT = 456DPC = 4CgPA:RI = GTGT=123

CdPA:RI = GTGT = 456

CgPA:RI = GTGT=123

STPPC = 3

CdPA:RI = GTGT = 456DPC = 4CgPA:RI = GTGT=123

MAP

TCAP

SCCP

MTP

MAP

TCAP

SCCP

MTP

SCCP

MTP

SCCP

MTP

SCCP

MTP

DPC = 5

Page 14: 974-05

5-14Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

SCCP Tables

C7GTTYPEC7GTTYPE

C7GTTC7GTT

C7NETSSNC7NETSSN

C7LOCSSNC7LOCSSN

GGTTHEADGGTTHEAD

GGTTCODEGGTTCODE

PLMNRTEPLMNRTE

SCCPTMRSCCPTMR

C7SERVERC7SERVER

This table is a default table set by Nortel Networks.

Page 15: 974-05

5-15Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table PLMNRTE Example

Table PLMNRTE:

• defines the calling party address which is a GT or PC+SSN.

If IMSI:

refer to table OFCVAR tuple MCC & MNC

If MSISDN:

refer to table OFCVAR tuple GSMMSC –NUMBER GSMVLR – NUMBER

• Rules

– The calling party will be PC+SSN if match found in office table or in table PLMNRTE.

– The calling party will be a global title if not match found.

Table PLMNRTE:

• defines the calling party address which is a GT or PC+SSN.

If IMSI:

refer to table OFCVAR tuple MCC & MNC

If MSISDN:

refer to table OFCVAR tuple GSMMSC –NUMBER GSMVLR – NUMBER

• Rules

– The calling party will be PC+SSN if match found in office table or in table PLMNRTE.

– The calling party will be a global title if not match found.

Page 16: 974-05

5-16Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

To set up the SCCP layer in a GSM CCS7 network, datafill the following tables:

• Table PLMNRTE

• Table SCCPTMR

• Table C7NETSSN

• Table C7LOCSSN

• Table C7SERVER

• Table GGTTHEAD

• Table GGTTCODE

• Table C7GTTYPE

• Table C7GTT

To set up the SCCP layer in a GSM CCS7 network, datafill the following tables:

• Table PLMNRTE

• Table SCCPTMR

• Table C7NETSSN

• Table C7LOCSSN

• Table C7SERVER

• Table GGTTHEAD

• Table GGTTCODE

• Table C7GTTYPE

• Table C7GTT

SCCP Tables

Page 17: 974-05

5-17Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table PLMNRTE: Multiple CC/MCC Example

Country A

Country B

Country C

CC=60NDC=41 43

PLMN

CC=62NDC=48 520-525

CC=63NDC=41-45 48000-48155

The Application provides:CC=71NDC=41SN=01000000NA=International

Table OFCVAR

PARMNAME PARMVALUE------------------------------------------------------------GSMMSC_NUMBER 60 41 80100000GSMVLR_NUMBER 60 41 80100000

Table OFCVAR

PARMNAME PARMVALUE------------------------------------------------------------GSMMSC_NUMBER 60 41 80100000GSMVLR_NUMBER 60 41 80100000

Table PLMNRTE

PLMNKEY------------------------------------------------------------MSISDN_INTL 62 48 62 48MSISDN_INTL 62 520 62 525MSISDN_INTL 63 41 63 45MSISDN_INTL 63 48 000 63 48 155MSISDN_NATL 41 41MSISDN_NATL 43 43

Table PLMNRTE

PLMNKEY------------------------------------------------------------MSISDN_INTL 62 48 62 48MSISDN_INTL 62 520 62 525MSISDN_INTL 63 41 63 45MSISDN_INTL 63 48 000 63 48 155MSISDN_NATL 41 41MSISDN_NATL 43 43

Page 18: 974-05

5-18Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table PLMNRTE: Multiple NDC/MNC Example

Country Code=60

NDC=214 218

PLMN

The Application provides:CC=60NDC=21SN=41000000NA=National

Table OFCVAR

PARMNAME PARMVALUE------------------------------------------------------------GSMMSC_NUMBER 60 41 80100000GSMVLR_NUMBER 60 41 80100000

Table OFCVAR

PARMNAME PARMVALUE------------------------------------------------------------GSMMSC_NUMBER 60 41 80100000GSMVLR_NUMBER 60 41 80100000

Table PLMNRTE

PLMNKEY------------------------------------------------------------MSISDN_NATL 21 4 21 4MSISDN_NATL 21 8 21 8

Table PLMNRTE

PLMNKEY------------------------------------------------------------MSISDN_NATL 21 4 21 4MSISDN_NATL 21 8 21 8

Page 19: 974-05

5-19Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table SCCPTMR Example

>TABLE: SCCPTMR

TOP

INDEX TCONNEST TCONNREL TINTERVL TIASEND TIARCV

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

0 60 10 60 300 300

BOTTOM

>TABLE: SCCPTMR

TOP

INDEX TCONNEST TCONNREL TINTERVL TIASEND TIARCV

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

0 60 10 60 300 300

BOTTOM

Page 20: 974-05

5-20Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Example of Global Title Configuration

MAP-HLR : SSN=6E164 @ : 301 22 1111MSISDN : E164 CC = 301 NDC = 22 IMSI : MCC = 200 MNC = 20

VLR

HLR A ISC A

E164 @ : 301 22 3333

E164 @ : 301 22 2222MAP-MSC = SSN=8MAP-VLR : SSN=7

ISC B

HLR B

MSC B

VLR

E164 @ : 902 41 2222

E164 @ : 902 41 3333

E164 @ : 902 41 1111MSISDN : E164 CC = 902 NDC = 41 IMSI : MCC = 300 MNC = 30MAP-HLR : SSN =6

MSC A

NET1

NET2

RNC

HLRARS

BSCARS

ISCARS

PLMN1 PLMN2

MAP-VLR : SSN=7MAP-MSC : SSN =8

Page 21: 974-05

5-21Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Defining Remote SubsystemUsing Table C7NETSSN

Table C7NETSSN defines the adjacent applications

>TABLE: C7NETSSN

TOP

PCNAME XUDTIND CGT1 CGT2 SSNAMES

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

UTRAN1_RS Y 0 0 (RANAP 142) $

UTRAN2_RS Y 0 0 (RANAP 142) $

UTRAN3_RS Y 31 31 (RANAP 142) $

HLR5_RS Y 31 31 (RMAPHLR 6) $

MSC5MSC2_RS Y 0 0 (RMAPMSC 8) (RMAPVLR 7) $

DEMO_RS Y 0 0 (RANAP 142) $

BSC1RTS Y (BSSAP 254) $

BOTTOM

>TABLE: C7NETSSN

TOP

PCNAME XUDTIND CGT1 CGT2 SSNAMES

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

UTRAN1_RS Y 0 0 (RANAP 142) $

UTRAN2_RS Y 0 0 (RANAP 142) $

UTRAN3_RS Y 31 31 (RANAP 142) $

HLR5_RS Y 31 31 (RMAPHLR 6) $

MSC5MSC2_RS Y 0 0 (RMAPMSC 8) (RMAPVLR 7) $

DEMO_RS Y 0 0 (RANAP 142) $

BSC1RTS Y (BSSAP 254) $

BOTTOM

Page 22: 974-05

5-22Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Defining Local SubsystemsUsing Table C7LOCSSN

Table C7LOCSSN defines the DMS-MSC applications

>TABLE: C7LOCSSN

TOP

SSNAME SSNUMBER MININST REPLINFO TFMI PCNAMES

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

MAPMSC 8 1 N N (HLR5_RS) (MSC5MSC2_RS) $

RANAP 142 1 N N (UTRAN1_RS) (UTRAN2_RS) (UTRAN3_RS) (DEMO_RS) $

MAPVLR 7 1 N N (HLR5_RS) $

GSMINAP 200 1 N N $

BSSAP 254 4 N N $

BOTTOM

>TABLE: C7LOCSSN

TOP

SSNAME SSNUMBER MININST REPLINFO TFMI PCNAMES

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

MAPMSC 8 1 N N (HLR5_RS) (MSC5MSC2_RS) $

RANAP 142 1 N N (UTRAN1_RS) (UTRAN2_RS) (UTRAN3_RS) (DEMO_RS) $

MAPVLR 7 1 N N (HLR5_RS) $

GSMINAP 200 1 N N $

BSSAP 254 4 N N $

BOTTOM

Page 23: 974-05

5-23Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Datafilling Table C7SERVER if Using MMU

Table C7SERVER is used with MMU or C7SERVER

To datafill table C7SERVER:

1. Datafill tables LIUINV

2. Datafill C7LOCSSN.

>TABLE: C7SERVER

TOP

SVR7ID SVR7NAME SVR7INFO

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

1 SVR7 0 APPLICATION (MMU) $

2 SVR7 1 APPLICATION (MMU) $

3 SVR7 2 APPLICATION (MMU) $

4 SVR7 3 APPLICATION (MMU) $

5 SVR7 4 APPLICATION (MMU) $

6 SVR7 5 APPLICATION (MMU) $

7 SVR7 6 APPLICATION (MMU) $

8 SVR7 7 APPLICATION (MMU) $

9 SVR7 8 APPLICATION (MMU) $

10 SVR7 9 APPLICATION (MMU) $

11 SVR7 10 APPLICATION (MMU) $

12 SVR7 11 APPLICATION (MMU) $

13 SVR7 12 APPLICATION (MMU) $

14 SVR7 13 APPLICATION (MMU) $

BOTTOM

>TABLE: C7SERVER

TOP

SVR7ID SVR7NAME SVR7INFO

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

1 SVR7 0 APPLICATION (MMU) $

2 SVR7 1 APPLICATION (MMU) $

3 SVR7 2 APPLICATION (MMU) $

4 SVR7 3 APPLICATION (MMU) $

5 SVR7 4 APPLICATION (MMU) $

6 SVR7 5 APPLICATION (MMU) $

7 SVR7 6 APPLICATION (MMU) $

8 SVR7 7 APPLICATION (MMU) $

9 SVR7 8 APPLICATION (MMU) $

10 SVR7 9 APPLICATION (MMU) $

11 SVR7 10 APPLICATION (MMU) $

12 SVR7 11 APPLICATION (MMU) $

13 SVR7 12 APPLICATION (MMU) $

14 SVR7 13 APPLICATION (MMU) $

BOTTOM

Page 24: 974-05

5-24Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Defining Originating Point CodeUsing Table GGTTHEAD

Table GGTTHEAD defines the originated point code.

To datafill table GGTTHEAD:

1. Datafill table C7NETWRK.

>TABLE: GGTTHEAD

TOP

XLANAME DFLT

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

IMSI UIS_NATLSP

MSISDN UIS_NATLSP

BOTTOM

>TABLE: GGTTHEAD

TOP

XLANAME DFLT

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

IMSI UIS_NATLSP

MSISDN UIS_NATLSP

BOTTOM

Page 25: 974-05

5-25Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Discriminate the Originated Point CodeUsing Table GGTTCODE

If different networks are defined in the node, this table becomes mandatory.

>TABLE: GGTTCODE

TOP

XLAKEY XLADATA

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

IMSI 208 208 NET1

MSISDN 33 33 NET1

BOTTOM

>TABLE: GGTTCODE

TOP

XLAKEY XLADATA

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

IMSI 208 208 NET1

MSISDN 33 33 NET1

BOTTOM

Page 26: 974-05

5-26Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Define the Different Type of GTUsing Table C7GTTYPE

An hardcoded/hidden table, defined in the DMS-MSC, allows you to datafill those tables. This hard coded table is also known as the Address Manipulation table.

In UMTS or GSM we will generally have the need to route messages based on one of the following numbers (or global title)

• Subscriber IMSI (example: Update location request at VLR)

• Subscriber MSISDN (example: SRI request at MSC)

• Subsystem global title (example: VLR number for PRN request at HLR)

• Hybrid number (example: update location request at VLR in case of roaming)

Page 27: 974-05

5-27Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Address Manipulation Table

The following information is hardcoded in the DMS.

To datafill table C7GTTYPE , use GTTID.

ASE SSN Digits Numbering Plan GTTID

SRI (INTL number) HLR MSISDN E.164/INTL MAPISDNINTL

MAIISDN (ANSI)

ISD VLR Hybrid format E.214/INTL MAPHLRGT

UL HLR IMSI E.212/INTL MAPISDNMOBILEMAISDNM (ANSI)

Page 28: 974-05

5-28Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table C7GTTYPE Example

>TABLE: C7GTTYPE

TOP

GTTNAME GTTYPE GTTID

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

IMSI_GT CCITT7 0 INTL E212 (MAPISDNMOBILE) $

MSISDN_NAGT CCITT7 0 NATL E164 (MAPISDN) $

MSISDN_INGT CCITT7 0 INTL E164 (MAPISDNINTL) $

E214_GT CCITT7 0 INTL E214 (MAPHLRGT) $

GSMINAP_GT CCITT7 5 INTL E164 (GSMINAPGT) $

BOTTOM

>TABLE: C7GTTYPE

TOP

GTTNAME GTTYPE GTTID

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

IMSI_GT CCITT7 0 INTL E212 (MAPISDNMOBILE) $

MSISDN_NAGT CCITT7 0 NATL E164 (MAPISDN) $

MSISDN_INGT CCITT7 0 INTL E164 (MAPISDNINTL) $

E214_GT CCITT7 0 INTL E214 (MAPHLRGT) $

GSMINAP_GT CCITT7 5 INTL E164 (GSMINAPGT) $

BOTTOM

Page 29: 974-05

5-29Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Defining Where and How to Route the GTUsing Table C7GTT

The routing information in the message must include:

• Destination Point Code either STP or final destination

• Global title (IMSI, MSISDN or MSC/HLR/VLR/EIR/SMSC/SCP(IN) number

The different ways to route the message are:

• GTONLY Routing

• PCSSN Routing

• SSN Routing

• New GT Routing

Page 30: 974-05

5-30Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Table C7GTT Example

>TABLE: C7GTT

GTTKEY GTTRSLT

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

IMSI_GT 2081140000000 2081140000000 PCONLY (HLR5_RS 0) $ GT

MSISDN_NAGT 336104000 336104000 PCONLY (HLR5_RS 0) $ GT

MSISDN_NAGT 610599991 610599991 SSNONLY (MAPMSC) $

MSISDN_NAGT 610599992 610599992 SSNONLY (MAPVLR) $

MSISDN_NAGT 610599995 610599995 PCSSN (MSC5MSC2_RS RMAPMSC 0) $ GT

MSISDN_NAGT 610599996 610599996 PCSSN (MSC5MSC2_RS RMAPVLR 0) $ GT

MSISDN_INGT 33610599991 33610599991 SSNONLY (MAPMSC) $

MSISDN_INGT 33610599992 33610599992 SSNONLY (MAPVLR) $

MSISDN_INGT 33610599993 33610599993 PCONLY (HLR5_RS 0) $ GT

IMSI_GT 20813 20813 NEWGT GTI_40 E214 INTL REPLACE_DIGS 1 5 33660 NEWGT_PCONLY (STP1RTS 0) (STP2RTS 0) $ GT

>TABLE: C7GTT

GTTKEY GTTRSLT

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

IMSI_GT 2081140000000 2081140000000 PCONLY (HLR5_RS 0) $ GT

MSISDN_NAGT 336104000 336104000 PCONLY (HLR5_RS 0) $ GT

MSISDN_NAGT 610599991 610599991 SSNONLY (MAPMSC) $

MSISDN_NAGT 610599992 610599992 SSNONLY (MAPVLR) $

MSISDN_NAGT 610599995 610599995 PCSSN (MSC5MSC2_RS RMAPMSC 0) $ GT

MSISDN_NAGT 610599996 610599996 PCSSN (MSC5MSC2_RS RMAPVLR 0) $ GT

MSISDN_INGT 33610599991 33610599991 SSNONLY (MAPMSC) $

MSISDN_INGT 33610599992 33610599992 SSNONLY (MAPVLR) $

MSISDN_INGT 33610599993 33610599993 PCONLY (HLR5_RS 0) $ GT

IMSI_GT 20813 20813 NEWGT GTI_40 E214 INTL REPLACE_DIGS 1 5 33660 NEWGT_PCONLY (STP1RTS 0) (STP2RTS 0) $ GT

Page 31: 974-05

5-31Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Page 32: 974-05

5-32Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

CgPA/CdPA Address Indicator Bits (CCITT)

APC indicator

1 = PC included)BSSN indicator

1 = SSN included)C-FGT indicator

0000 = GT not included0001 = GT includes nature of address0010 = GT includes translation type0011 = GT includes translation type, numbering plan,

and encoding scheme0100 = GT includes translation type, numbering plan,

encoding scheme and nature of address)GRouting Indicator

0 = route on GT1 = route on PC + SSN

HReserved for national use

0

APC indicator

1 = PC included)BSSN indicator

1 = SSN included)C-FGT indicator

0000 = GT not included0001 = GT includes nature of address0010 = GT includes translation type0011 = GT includes translation type, numbering plan,

and encoding scheme0100 = GT includes translation type, numbering plan,

encoding scheme and nature of address)GRouting Indicator

0 = route on GT1 = route on PC + SSN

HReserved for national use

0

ABCDEFGH

Global Title

Point Code

1

2

3

4

5

N

Subsystem Number

Page 33: 974-05

5-33Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

CgPA/CdPA Address Indicator Bits (ANSI)

A

SSN indicator

1 = SSN included

B

PC indicator

1 = PC included

C-F

GT indicator

0000 = GT not included

0001 = GT includes translation type, numbering plan and encoding scheme

0010 = GT includes translation type

G

Routing Indicator

0 = route on GT

1 = route on PC + SSN

H

Network indicator

0 = international

1 = national

A

SSN indicator

1 = SSN included

B

PC indicator

1 = PC included

C-F

GT indicator

0000 = GT not included

0001 = GT includes translation type, numbering plan and encoding scheme

0010 = GT includes translation type

G

Routing Indicator

0 = route on GT

1 = route on PC + SSN

H

Network indicator

0 = international

1 = national

ABCDEFGH

Global Title

1

2

3

4

5

N

Subsystem Number

Point Code

Page 34: 974-05

5-34Lesson 5. SCCP Layer PE/TRD/CN/UM974 16.02/EN January, 2003

"C

onfi

den

tial

info

rmat

ion

--

may

not

be

copi

ed o

r di

sclo

sed

wit

hou

t per

mis

sion

".

Subsystems and SSNs

= Subsystem

DMS-HLRDMS-MSC

RNC

MAP-MSC8

RANAP142

VLR

MAP-VLR7

MAP-HLR6

BSSAP254

BSC

GSMCAP146

GSMINAP15

BSSAP254

MSC-BSSAP-LE251