owb091011(slide)sgsn9810 v900r010c02 gr interface data configuration-20101105-b-v2.0

www.huawei.com

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

SGSN9810 Gr Interface Data Configuration

ISSUE2.0

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page ‹#›

References

HUAWEI SGSN9810 Serving GPRS Support Node

Operation Manual Data Configuration l (V8.60)

3GPP TS 29002 MAP Protocol


Objectives

Upon completion of this course, you will be able to:

Describe the protocol stack and main functions of the Gr interface.

Configure the data for the Gr over TDM interface.

Configure the data for the Gr over IP interface.

maxiaochuang KF27039


Contents

1. Basic Concepts

2. Data Configuration for the Gr over TDM Interface

3. Data Configuration for the Gr over IP Interface


Gr Interface

The Gr interface is a mandatory interface between the

serving GPRS support node (SGSN) and the home location

register (HLR) in a GSM or UMTS network.

On the entire network, the Gd/Gs/Ge/Gf/Lg interface is the

same as the Gr interface and based on the SS7 signaling

network.


Gr Interface Protocol Stack Gr over TDM

The protocol stack of the Gr over TDM interface consists of Message Transfer Protocol

(MTP), Signaling Connection Control Part (SCCP), Transaction Capability Application Part

(TCAP), and Mobile Application Part (MAP).

Gr over IP

The protocol stack of the Gr over IP interface consists of Internet Protocol (IP), Simple

Control Transmission Protocol (SCTP), MTP3 User Adaptation (M3UA), SCCP, TCAP,

and MAP. MAP

TCAP

SCCP

MTP3

MTP2

MTP1

MAP

TCAP

SCCP

M3UA

SCTP

IP

Gr over TDM Gr over IP


Boards Related to the Gr Interface

SS7 over E1

MAP/CAP BSSAP

+

ECU

TCAP

SCCP

MTP3

MTP2 ETI

MTP1 ETI

SS7 over IP

MAP/CAP BSSAP+ ECU

TCAP

SCCP

M3UA ECU

SCTP

IP/L2/L1 EPU/PFI


Related Processes

SPP

Based on the user international mobile subscriber identity (IMSI), the

signaling processing process (SPP) assigns the short data burst

(SDB) table and creates user contexts. The user context reserves the

authentication sets, subscription data, and access data.


Addressing Mode of the Gr Interface

According to the address numbering plan of the SS7 signaling network, there are

two addressing modes for the Gr interface:

DPC or DPC+SSN

DPC+GT

The HLR needs to be set with two different global title (GT) numbers:

HLR number: The numbering plan is ISDN. It is used to address the HLR when

the HLR message is replied.

IMSI number: The numbering plan is MSISDN. It is used for the HLR initial

addressing after the routing area is updated.


Comparison Between DPC and DCP+SSN

When the DPC+SSN addressing mode is used, the subsystem

number (SSN) in the SCCP message is the SSN that configured

in the SCCPGT.

When the DPC addressing mode is used, the SSN in the SCCP

message is the SSN that sent form the user layer to the SCCP.


MTP3 Load-sharing DPC or DPC+SSN

Two-level load-sharing

One level is route load-sharing or link set load-sharing.

The other level is link load-sharing. The signaling point link set selection mask (SLSSM) and

the signaling link selection mask (SLSM) are configured through the ADD N7DPC and ADD

N7LKS.

Implementation of load-sharing:

When receiving user messages from the upper layer, MTP3 determines route or link set and

link according to signaling link selection code (SLS) and destination signaling point code

(DPC).


SCCP Load-sharing DPC+GT

1. Configure STP1 and STP2 to active/standby

2. Configure STP1 and STP2 to load-sharing

D1

OSP DSP

STP1

STP2

D2

Link set 1Link set 1

Link set 2Link set 2


GT Structure

SCCP Address FormatSCCP address is classified as the calling and called SCCP user addresses. The

calling SCCP user address identifies the destination SCCP user and the called

SCCP user address identifies the source SCCP user. A user address is a

parameter of variable length and consists of address indicator and address. The

sequence of every unit in the address is SPC, SSN, and GT.

Su

bsy

stem

in

dica

tor

Global code indicator

Route

indica

tor

Sp

are

01234567

Sig

nalin

g p

oin

t in

dica

tor


GT Structure

SCCP Address Format

Format of global code in the SCCP address:

7 6 5 4 3 2 1 0

Translation type

Number plan Encoding scheme

Reserve Address indicator

Address signal 2 Address signal 1

…….

Pad number (if required) Address signal N


Contents

1. Basic Concepts




SS7 Links Configuration Guidelines

At least two SS7 links are required between the SGSN and

a neighboring signaling point.

To ensure the security, you must configure all the links in an

office evenly among the ECUs in different subracks of an

SGSN.

maxiaochuang KF27039


GT Configuration Guidelines

Addressing mode:

Scheme 1: Use the DPC addressing mode to transmit MAP and CAP

messages for signaling points inside a province. Use the GT addressing

mode to transmit MAP and CAP messages for signaling points outside a

province.

Using the DPC addressing mode, the STP load is light but the data configuration for the

SGSN is high.

Scheme 2: Use the GT addressing mode to transmit messages for signaling

points inside or outside a province.

Using the GT addressing mode, the STP load is heavy but the data configuration for the

SGSN is low.


Configuration Restrictions for the SGSN

For all links destined for the same DPC, up to 16 links can take effect. If

more than 16 links are configured, the remaining ones are idle.

The SLSSM in the ADD N7RT command and SLSM in the ADD N7DPC

command cannot have the same bit value as 1.

For example, when SLSSM is B0001, the maximum value of SLSM is B1110.

If multiple STPs are used for forwarding messages and multiple links are

configured to share loads destined for each STP, you can use the following

mitigation methods:

For SLSSMs destined for different signaling points, set different bit values to 1.

For example, set SLSSM of DPC=0x9fe10 to B0001 and that of DPC=0x9fe11 to

B0010.

Use the 2 Mbit/s link to provide broader bandwidth.


Networking Example

ETI

ETI

ECU

ECU

0

Sub2

Slot

0

Sub4

Slot

SGSNSGSN

HLR1HLR1link5link5


Networking Data

Item Value Item ValueSGSN SPC CC0001 HLR SPC EE0000SGSN GT 8613900757 HLR GT 8613900756

MCC 460 MNC 07CC 86 NDC 139

IMSI Number Segment in HLR 46007755Translation Type DPC

Item Frame No. Slot

No.

Port No. Link

Rate

Timeslot

ID

SLC

1 0 2 2 64 Kbit/s 16 1


Step Operation Command

Configure the hardware.1 Set the operation mode for ETI. SET ETICFG2 Set the E1 port. SET ET1PORT

Set the attributes for the signaling network.

3Set the signaling network attributes

for the local SGSN. SET SIGATTR

Set the MTP3.

4Add MTP originating signaling point

code (OPC). ADD N7OPC

5 Add the MTP DPC. ADD N7DPC6 Add the MTP link set. ADD N7LKS

7 Add the MTP route. ADD N7RT

8 Add the MTP link. ADD N7LNK

Procedure for Data Configuration



Configure SCCP.

9 Add SCCP OPC. ADD SCCPOPC10 Add SCCP DPC. ADD SCCPDPC11 Add SCCP subsystem to the SGSN. ADD SCCPSSN

12 Add SCCP subsystem to the HLR. ADD SCCPSSN

Configure the GT translation table.

13Configure the conversion between

IMSI and GT. ADD IMSIGT

14Configure the SCCP GT for the local

SGSN. ADD SCCPGT

15Configure the SCCP GT for the

destination HLR. ADD SCCPGT

Procedure for Data Configuration


Step 1: Set the operation mode for ETI.

SET ETICFG

This command is used to configure:

ETI operation mode

Example:

SET ETICFG: SRN=0, SN=2, CFGTDMTYPE=E1,

E1IMPED=E1_75ohm, CFGAPPMODE=FR;


Step 2: Set the E1 port.

SET ET1PORT

This command is used to set the port position of the E1 link.

Certain parameters need to be negotiated with the peer

device.

Example:

SET ET1PORT: SRN=0, SN=2, STRPORTID=1,

ENDPORTID=31, CFGTDMTYPE=E1, CFGE1FRM=DF,

CFGE1ENC=HDB3, TRANSMODE=SHORTLINE;


Step 3: Configure the local office information.

ADD HPLMN

This command is used to configure the first public land mobile

network (PLMN) number for the SGSN.

ADD HPLMN: MCC="460", MNC="07", CC="86";

SET SIGATTR

This command is used to set the attributes of the signaling

network.

SET SIGATTR: IF=INVALID, IRF=INVALID, NF=LABEL24,

NRF=LABEL14, MAPNI=INT, CAPNI=INT, SS7T=ITUT_SS7;


Step 4: Add an MTP OPC.

ADD N7OPC

This command is used to add an MTP OPC.

ADD N7OPC: OPX=1, NI=NAT, OPC="CC0001";

– OPX

– NI (network indication)


Step 5: Add an MTP DPC.

ADD N7DPC

This command is used to add an HLR DPC.

ADD N7DPC: DPX=3, OPX=1, DPC="EE0000", SLSSM=B0000,

ADJF=TRUE, DPN="HLR1";

– Only one route: SLSSM=B0000

– Direct route: adjacent node


Step 6: Add an MTP link set.

ADD N7LKS

This command is used to add an MTP link set.

ADD N7LKS: LSX=2, DPX=3, SLSM=B0000, LSN="HLR1";

– Only one link set: SLSM=B0000


Step 7: Add an MTP route.

ADD N7RT

This command is used to add an MTP route.

ADD N7RT: RTX=3, DPX=3, LSX=2, PRI=0, RTN="HLR1";

SGSN HLR1Link set 2


Step 8: Add an MTP link.

ADD N7LNK

This command is used to add an MTP link.

ADD N7LNK: SRN=0, SN=2, LNK=2, RATET=LINK_E1_64K,

TS=80, LSX=2, SLC=1, SLCS=1;

SGSN HLR1Link set 2

Link 1


Step 9: Add an SCCP OPC.

ADD SCCPOPC

This command is used to add an SCCP OPC.

Example:

ADD SCCPOPC: OPX=1, NI=NAT, OPC="CC0001",

SPN=COREONLY, SGSNN=" 8613900757";


Step 10: Add an SCCP DPC.

ADD SCCPDPC

This command is used to add an SCCP DPC.

ADD SCCPDPC: DPX=3, OPX=1, DPC="EE0000",

DPN="HLR1";


Step 11: Configure SSNs.

SSN OPC DPC

SGSN SGSN's SPC SGSN's SPC

SCMG (SGSN) SGSN's SPC SGSN's SPC

HLR SGSN's SPC HLR's SPC

SCMG (HLR) SGSN's SPC HLR's SPC


Step 12: Configure SCCP subsystems. ADD SCCPSSN

ADD SCCPSSN: SSNX=0, SSN=SCMG, NI=NAT,

DPC="CC0001", OPC="CC0001",

SSNNAME="SGSN";

ADD SCCPSSN: SSNX=1, SSN=SGSN, NI=NAT,

DPC="CC0001", OPC="CC0001",

SSNNAME="SGSN";


Step 13: Configure the SCCP Subsystem of the HLR.

ADD SCCPSSN

ADD SCCPSSN: SSNX=4, SSN=SCMG, NI=NAT,

DPC="EE0000", OPC="CC0001", SSNNAME="HLR1";

ADD SCCPSSN: SSNX=5, SSN=HLR, NI=NAT,

DPC="EE0000", OPC="CC0001", SSNNAME="HLR1";


Step 14: Configure the IMSTGT table.

ADD IMSIGT

Configure the IMSI GT translation table.

ADD IMSIGT: IMSI="46007", GT="86139";

Attach request (IMSI)

SGSN HLR

IMSI=46007 7551237567

GT =86139 7551237567

SCCPGT=DPC (HLR/STP)

DPC (HLR/STP)

MTP LINK


Step 15: Configure the SCCP GT translation table. ADD SCCPGT

Configure the SCCP GT translation table for the local SGSN.

For the SGSN, you need to configure the SCCP GT

according to the SGSN No.; otherwise, transmission of

SCCP layer messages will fail.

ADD SCCPGT: GTX=0, NI=NAT, RT=DPC, NP=ISDNP,

ADDR="8613900757", DPC="CC0001", NAME="SGSN";


Step 16: Configure the SCCP GT translation table of HLR.

ADD SCCPGT

Configure the SCCP GT translation table of the IMSI number

segment:

ADD SCCPGT: GTX=1, NI=NAT, RT=DPCSSN, NP=ISDNMS,

ADDR="86139755", DPC="EE0000", SSN=HLR,

NAME="HLR1";

Configure the GT translation table of the HLR number:

ADD SCCPGT: GTX=2, NI=NAT, RT=DPCSSN, NP=ISDNP,

ADDR="8613900756", DPC="EE0000", SSN=HLR,

NAME="HLR1";


GT Configuration Specification

In SCCP GT translation table, the GT translation of the

following number/number segments are required:

Domestic/International IMSI number segment

Number of local SGSN

Domestic/International HLR number segment


GT Configuration Specification

Number Type Numbering Plan

Translation Type

Destination Number Segment to Be Configured

IMSI number E.214, ISDN/mobile numbering planNP=ISDNMS

DPCGT (DPC+GT)

HSTP 1, 2, 3, 4, 5, 6, 7, 8, 9

Local SGSN number

E.164, ISDN/telephone numbering planNP=ISDNP

DPC SGSN SGSN number

HLR number E.164, ISDN/telephone numbering planNP=ISDNP

DPCGT (DPC+GT)

HSTP 1, 2, 3, 4, 5, 6, 7, 8, 9


MTP Layer Test

Check SS7 link status:

DSP N7LNK

Check link route status:

DSP N7RT

Check DPC status:

DSP N7DPC


SCCP Layer Test

Check SCCP DPC status:

DSP SCCPDPC

Check SCCP subsystem status:

DSP SCCPSSN

Check GT translation:

TST SCCPGT


SCCP Layer Test

In SCCP message tracing, how to check whether the Gr interface

is normal?

The SCCP status can be displayed by running DSP SCCPDPC

and DSP SCCPSSN. When SCCP status is normal, if an upper

layer message is not delivered on the SCCP layer, the reason is

the incorrect configuration of the GT code. Find a MAP message

in Gr interface tracing, for example, the location update request.

Then, find whether there is a corresponding message in SCCP

tracing. If yes, the SCCP layer is normal. If no, check the GT code

configuration.


Contents

1. Basic Concepts




SIGTRAN Definition

The Signaling Transport (SIGTRAN) protocol stack has two

layers: Transfer protocol layer (SCTP) and adaptation

protocol layer (M3UA and IUA).

The SGSN9810 implements only M3UA.


Basic Concepts The M3UA refers to the SS7 MTP3 user adaptation protocol. It is used

together with the Stream Control Transmission Protocol (SCTP) to

transmit SS7 MTP3 user signaling messages, namely, the SCCP

messages, through the IP network. The protocol elements allow MTP3

peer users to carry out seamless operations in the SS7 and IP

domains.

SCTP is the reliable datagram transmission protocol based on

unreliable transmission service protocols, such as IP. The upper layer

of SCTP is SCTP user application layer and the lower layer of SCTP is

packet network layer. SCTP provides highly efficient and reliable

services for M2UA, M3UA, IUA, and H.248 signaling.


SIGTRAN-based SGSN-HLR Networking

M3UA link

IP connection

HLR SGSN

SCCP

IP

SCTP

M3UA

IP

SCTP

M3UA

SCCP

IP


SIGTRAN-based SGSN-HLR Networking

HLR SG SGSN

MTP1

MTP2

MTP3

SCCP

MTP1

MTP2

MTP3

IP

SCTP

M3UA

IP

SCTP

M3UA

SCCP

No.7 IP

M3UA link

IP connectionTDM connection

MTP link


Networking Between the SGSN and the HLR

Two networking modes exist between the SGSN and the

HLR:

SGSN directly connecting with the local HLR

SGSN connecting with the local HLR through the SG

SGSN connecting with the HLR of users roaming in the local network

SGSN connecting with the HLR of users roaming in external networks

SGSNHLR n

SG1

SG2

HLR1

IP


Configuration Procedure


Add related boards.

1Set the operating mode for the IP

interface.MOD PORT

2 Configure the interface IP address. ADD IFIP

3Configure the IP address for the

EPU.ADD BRDIP

Configure signaling network attributes.

4Configure the signaling network

attributes for the SGSN. SET SIGATTR




Configure the M3UA layer data.

5 Add the M3UA local entity. ADD M3LE

6Add the M3UA destination

entity. ADD M3DE

7Add the M3UA signaling link

set. ADD M3LKS

8 Add the M3UA signaling route. ADD M3RT

9 Add the M3UA signaling link. ADD M3LNK

10Configure the IP route destined

for the destination entity.ADD IPRT




Configure the SCCP layer data.

11 Configure the SCCP DPC. ADD SCCPDPC

12Configure the SCCP

subsystem.ADD SCCPSSN

Configure the GT translation data.

13Configure the IMSI-GT

conversion.ADD IMSIGT

14Configure the GT translation

data.ADD SCCPGT

Note: The data configuration from Step 11 to Step 14 is the same as that of Gr over TDM. Thus, the configuration steps are not described in this part.


Networking Example

8 9

11 13

SS

SGSNSGSN

PF

I

PF

I

RR

EP

U

EP

U

11

EC

U

4

EC

U

5E

PU

HLR

Logical IP

Physical port

DATA SIGTRAN

IP

address

HLR IP

address

EP

U

13

10.40.40.1

220.0.0.1/2


Networking Data

Board/Slot IP Address Operating Mode

EPU0/11 220.0.0.1 Active

0/13 220.0.0.2 Active

PFI0/11

10.40.40.1Active

0/13 Standby

IP address

of the router10.40.40.2

IP Address of the Local End of the

M3UA LinkPort HLR IP Address Port

M3UA link220.0.0.1 2000 230.0.0.1 2000

220.0.0.2 2001 230.0.0.1 2001

OPC DPC

CC0001 EE0001


Step 1: Set the Operating Mode for the IP Interface

MOD PORT Example:

n MOD PORT: SRN=0, SN=11, PORTTYPE=EETH_PFI,

PORTNAME=Card1/Lan0, PEERSN=13, PEERPNAME=Card1/Lan0;


Step 2: Set the IP address for the Interface

ADD IFIP

p ADD IFIP: SRN=0, SN=11, PN=0, IP="10.40.40.1",

MSK="255.255.255.0";


Step 3: Set the IP address for the EPU

ADD BRDIP

Example:

ADD BRDIP: SRN=0, SN=11, MSTYPE=PRIMARY, IPT=IPV4,

IPV4="220.0.0.1";

ADD BRDIP: SRN=0, SN=13, MSTYPE=PRIMARY, IPT=IPV4,

IPV4="220.0.0.2";


Step 4: Set Signaling Network Attributes

SET SIGATTR

This command is used to set signaling network attributes.

SET SIGATTR: IF=INVALID, IRF=INVALID, NF=LABEL24,

NRF=LABEL14, MAPNI=INT, CAPNI=INT, SS7T=ITUT_SS7;


M3UA Entity Type

M3UA link

IPSPIPSP

SGSN HLR

M3UA link

SGPASP

SGSN HLRSGMTP3 link

SP

ASP Application Server Process

SGP Signaling Gateway Process

IPSP IP Server Process


Step 5: Configure the Local Entity

ADD M3LE

This command is used to add local entities.

Example:

ADD M3LE: LEX=1, NI=NAT, OPC="CC0001", LET=IPSP;


Step 6: Configure the Destination Entity

ADD M3DE

This command is used to add the destination entity.

Example:

ADD M3DE: DEX=1, LEX=1, DPC="EE0001", SLSSM=B0000,

DET=IPSP, ADJF=TRUE, RC=2, PVER=RFC3332, DEN="HLR";


Step 7: Configure the M3UA Link Set

ADD M3LKS

This command is used to add the M3UA link set. Only one

link set can be configured between two adjacent M3UA

entities.

Example:

ADD M3LKS: LSX=1, ADX=1, SLSM=B0001, WM=IPSP,

TM=LOADSHARE, LSN="TO HLR";


Traffic Mode

OVERRIDE (active and standby): 1+N backup in this mode, there is only one

link is in active status while all others are standing by. When the active link is

faulty, one of the standby links are activated and start transmitting.

LOADSHARE (load-sharing): In this mode, all the links in the link set are active

and share the traffic load.

1+N backup mode

Active

Standby

Load-sharing mode


Step 8: Configure the Route

ADD M3RT

This command is used to configure the M3UA route destined for the

HLR.

Example:

ADD M3RT: RTX=1, DEX=1, LSX=1;


Step 9: Configure the M3UA Link

ADD M3LNK

ADD M3LNK: SRN=0, SN=14, LNK=1, IPT=IPv4,

LOCIPV41="220.0.0.1", LOCPORT=2000, PEERIPV41="230.0.0.1",

PEERPORT=2000, CS=S, LSX=1;

ADD M3LNK: SRN=0, SN=15, LNK=1, IPT=IPv4,

LOCIPV41="220.0.0.2", LOCPORT=2001, PEERIPV41="230.0.0.1",

PEERPORT=2001, CS=S, LSX=1;


Step 10: Configure the IP Route

ADD IPRT

This command is used to add the IP route to forward the IP packets to

the HLR.

Example:

ADD IPRT: IP="230.0.0.1", MSK="255.255.0.0",

GATE="10.40.40.2";


Transmission Test

Step Operation Note

1 Run PING to check whether the M3UA

link between the source IP address and

the destination IP address is normal.

If the result shows that the link is

disconnected, check whether the route

configuration is correct.


Checking M3UA Interface Status

Check the signaling link status:

DSP M3LNK

Check the signaling route status:

DSP M3RT

Check the destination entity status:

DSP M3DE

www.huawei.com

Thank you

owb091011(slide)sgsn9810 v900r010c02 gr interface data configuration-20101105-b-v2.0

Documents