UM641 v03.02 Student Guide

WG Configuration and Integration
UM641 Course
"NORTEL NETWORKS AND NORTEL MATRA CELLULAR CONFIDENTIAL:

Information contained in this document is the property of Nortel Networks and Nortel Matra Cellular. Except as
specifically authorized in writing by Nortel Networks and Nortel Matra Cellular, the holder of this document
shall keep the information contained herein confidential and shall protect same in whole or in part from
disclosure and dissemination to third parties and use for evaluation, operation and maintenance purposes only".
"You may not reproduce, represent, or download through any means, the information contained herein in any
way or in any form without prior written consent of Nortel Networks and Nortel Matra Cellular".
© Nortel Matra Cellular and Nortel Networks 2000-2003
UM641 03.02 July 2003

Wireless Gateway Configuration and Integration
"Confidential information -- may not be copied or disclosed without permission".
UM641 03.02 July 2003

ii
Publication history
Version Date Comments
01.00 September 2001 UMTS 1.0

01.01 November 2001 UMTS 1.1
01.02 February 2002 UMTS 1.2
02.00 July 2002 UMTS 2.0
02.01 July 2002 Added Table of Contents, Acronyms and
Abbreviations section, and made minor
corrections
02.02 November 2002 Updated
03.01 February 2003 PC03
03.02 July 2003 Updated
UM641 03.02 July 2003

iii
UM641 03.02 July 2003

iv
Course UM641
Section Number
Introduction 1
Wireless Gateway Description 2
Cards and Software Configuration 3
Passport IP Servers (GIPS) 4
3G-SGSN Configuration 5
Wireless Media Gateway Configuration 6
Signaling Gateway and SAAL-NNI Configuration 7
Wireless Gateway ATM Configuration 8
Wireless Gateway Integration 9
Acronyms and Abbreviations 10
Appendices Number
Wireless Gateway Customer Input Questionnaire (CIQ) A
Wireless Gateway Specific Alarms B
Wireless Gateway Troubleshooting C
UM641 03.02 July 2003

v
UM641 03.02 July 2003

vi
Course Presentation
In this course the student will learn how to configure (using CLI), integrate and troubleshoot
the Wireless Gateway in the UMTS Packet Core network. The course concentrates on the
description of the Wireless Gateway CAS components and the provisioning of all the
Wireless Gateway shelves.
Course Objective:
Upon completion of this course, the student will be able to:
• Describe the Wireless Gateway Passport component architecture
• Describe the ways of switching and routing data, voice and signaling in the Wireless
Gateway
• Configure all Wireless Gateway shelves by using the Command Line Interface
• Integrate the Wireless Gateway
Prerequisite Skills:
• UMTS
• IP and ATM
• Passport Operation and Configuration
Prerequisites
Before taking this course, attendees must have attended the following applicable courses:
• UM010 UMTS SYSTEM DESCRIPTION
• UM030 WIRELESS GATEWAY DETAILED DESCRIPTION
• UM640 WIRELESS PASSPORT 7K/15K OPERATIONS
Scope
This course applies to the Packet Core 03 System Release.
UM641 03.02 July 2003

vii
UM641 03.02 July 2003

viii
Table of Contents
Publication History III
Course UM641 V
Table of Contents VII
1. INTRODUCTION 1-1
UMTS Courses 1-2

Wireless Gateway Support Engineer 1-3
GGSN Support Engineer 1-4
Preside Support Engineer 1-5
UMTS First Line Engineer 1-6
Objectives 1-7
Contents 1-8
2. WG Overview 2-1
Objectives 2-2
Contents 2-3
Wireless Gateway Overview 2-4
W IRELESS GATEWAY P ACKET S WITCHED CORE NETWORK INTERFACES 2-5
W IRELESS GATEWAY CIRCUIT SWITCHED CORE NETWORK INTERFACES 2-6
3. Cards and Software Configuration 3-1
Objectives 3-2
Contents 3-3
Wireless Gateway Shelf Definitions 3-4
Aggregation Node Software Configuration 3-5
AGGREGATION NODE SHELF 3-6
AN CARD CONFIGURATION 3-7
UM641 03.02 July 2003

ix
AN SOFTWARE CONFIGURATION 3-8

AN LOGICAL PROCESSORS CONFIGURATION 3-9
Shelf Type 1 Software Configuration : U-SGSN Function 3-11
SHELF TYPE 1 3-12
SHELF TYPE 1 CARD CONFIGURATION 3-13
SHELF TYPE 1 SOFTWARE CONFIGURATION 3-14
SHELF TYPE 1 LOGICAL PROCESSORS CONFIGURATION 3-15
Shelf Type 4 Software Configuration : WMG and SG 3-17
SHELF TYPE 4 3-18
SHELF TYPE 4E (ENHANCED) 3-19
Shelf Type 5 Software Configuration : Wireless Media Gateway 3-23
SHELF TYPE 5 3-24
SHELF TYPE 5E (ENHANCED) 3-25
Shelf Type 6 Software Configuration : Signaling Gateway 3-29
SHELF TYPE 6 3-30
Shelf Type 2 Software Configuration : USD Signaling Gateway 3-35
SHELF TYPE 2 3-36
Shelf Type 3 Software Configuration : USD Function 3-41
SHELF TYPE 3 3-42
UM641 03.02 July 2003

x
4. Passport IP Servers (GIPS) 4-1
Objectives 4-2
Contents 4-3
GIPS Configuration Principle in U-SGSN 4-4
Example: IP Servers for Gn interface 4-5
U-SGSN IP Servers for USD and USC 4-6
WG GIPS configuration: U-SGSN 4-7
5. U-SGSN Configuration (Shelf Type 1 Provisioning) 5-1
Objectives 5-2
Contents 5-3
U-SGSN Functional Description 5-5
W IRELESS GATEWAY P ACKET S WITCHED INTERFACES 5-6
WG PS FUNCTIONS: USER PLANE 5-7
PS PROTOCOL LAYERS: USER PLANE 5-8
WG PS FUNCTIONS: CONTROL PLANE 5-9
PS PROTOCOL LAYERS: CONTROL PLANE 5-10
W HICH CARDS FOR WHICH APPLICATIONS? 5-11
U-SGSN BOARDS AND APPLICATIONS 5-12
U-SGSN PROVISIONING METHODOLOGY 5-13
U-SGSN User Plane: USD Card Provisioning 5-15
PACKET SWITCHED USER PLANE: USD ON U-SGSN 5-16
USD CARD PROVISIONING METHODOLOGY (1): LU INTERFACE 5-17
STEP 1: USD CONFIGURATION : GIPS FOR LU 5-18
USD CARD PROVISIONING METHODOLOGY (2): GN INTERFACE 5-20
STEP 2: USD CONFIGURATION : GIPS FOR GN 5-21
STEP 2: USD FOR GN: ROUTING 5-23
GIPS PUBLIC AND PRIVATE SUBNETS 5-24
U-SGSN Control Plane: USC Card Provisioning 5-25
PACKET SWITCHED CONTROL PLANE: USC ON U-SGSN 5-26
USC CARD PROVISIONING METHODOLOGY (1): GIPS AND APPLICATIONS 5-27
STEP 1: USC CONFIGURATION : USC GIPS 5-28
UM641 03.02 July 2003

xi
STEP 1: USC FOR GN: ROUTING 5-30

USC CARD PROVISIONING METHODOLOGY (2): DNS AGENT AND INTERFACE TO DNS 5-31
STEP 2: DNS CONFIGURATION ON USC CARD 5-32
STEP 2. A: DNS APPLICATION CONFIGURATION 5-33
STEP 2.B: DNS INTERFACE PROVISIONING (OPTIONAL) 5-34
STEP 2.C: DNS AGENT CONFIGURATION 5-35
USGSN CONFIGURATION : TS AND DS 5-36
U-SGSN Control Plane: TCAP Applications Provisioning 5-39
GR’ INTERFACE 5-40
MAP CLIENT CONFIGURATION AND SIG COMMUNICATION 5-41
MAP CARD PROVISIONING METHODOLOGY (1): GIPS AND APPLICATIONS 5-42
STEP 1: MAP APPLICATION PROVISIONING 5-43
MAP FOR GR’ AND GE’: ROUTING 5-45
STEP 2: MAP-CLIENT TO MAP/TCAP PROVISIONING 5-46
STEP 3: SSF CLIENT TO TCAP PROVISIONING 5-47
USC CARD PROVISIONING METHODOLOGY (2): DNS AGENT AND INTERFACE TO DNS 5-48
STEP 4: MAP INTERFACE TO SIG PROVISIONING 5-49
STEP 4: IP STATIC ROUTE TO SIG PROVISIONING 5-50
HLRSim Provisioning 5-51
HLRSIM PROVISIONING METHODOLOGY 5-52
STEP 1: HLRSIM PROVISIONING: ON USC GIPS 5-53
STEP 2: HLRSIM SUBSCRIBER PROVISIONING 5-54
U-SGSN Accounting: SAS Application Provisioning 5-55
SAS APPLICATION PROVISIONING METHODOLOGY 5-56
ACCOUNTING TRAFFIC CONFIGURATION TO CGF 5-57
STEP 1: SAS APPLICATION PROVISIONING 5-58
STEP 1: SAS ROUTING 5-59
STEP 1: ACCOUNTING PARAMETERS 5-60
USC CARD PROVISIONING METHODOLOGY (2): SAS INTERFACE TO CGF 5-61
STEP 2: SAS INTERFACE PROVISIONING TO CGF 5-62
U-SGSN Lawful Intercept: LI Function Provisioning 5-63
LI FUNCTION PROVISIONING METHODOLOGY 5-64
STEP 1: LI APPLICATION PROVISIONING 5-65
UM641 03.02 July 2003

xii
ATM Interface to AN: I/O card provisioning 5-67

WG GIPS CONFIGURATION : U-SGSN 5-68
I/O CARD PROVISIONING ME THODOLOGY 5-69
PHYSICAL (OPTICAL ) PORTS PROVISIONING 5-70
IP/ATM INTERFACE TO AN 5-71
IP ROUTING 5-72
NETWORK SYNCHRONIZATION 5-73
6. Wireless Media Gateway Configuration (Shelf Type 5 Provisioning) 6-1
Objectives 6-2
Contents 6-3
Wireless Media Gateway Description 6-5
WG CS INTERFACE 6-6
WG CS USER PLANE 6-7
WG CS C ONTROL PLANE 6-8
W HICH CARDS FOR WHICH APPLICATIONS? 6-9
VOICE OVER ATM: TIMESLOT MAPPING 6-10
VOICE OVER ATM: TRUNKING USING AAL2 6-11
PVC CALL SETUP 6-12
WMG AND VSP DETAILED FUNCTIONS 6-13
CS BOARDS AND APPLICATIONS 6-14
WG ATM AND IP CONFIGURATION FOR CS 6-15
Wireless Media Gateway Provisioning 6-17
PVG PROVISIONING METHODOLOGY (1/2) 6-18
WMG PROVISIONING METHODOLOGY (2/2) 6-19
STEP 1: 32PE1TDM CARD 6-20
STEP 2: VSP2 CARD 6-21
STEP 2: TRAU FUNCTION ( VOICE) 6-22
STEP 2: MEDIA GATEWAY: SIGNALING (1) 6-24
STEP 2: MEDIA GATEWAY: SIGNALING (2) 6-26
STEP 2: MEDIA GATEWAY: VGS PROVISIONING 6-27
STEP 3: VSP2 PARAMETERS & ATTRIBUTES 6-28
PVG PROVISIONING METHODOLOGY (2) 6-30
WMG PROVISIONING 6-31
UM641 03.02 July 2003

xiii
STEP 3: 4POC3 CARD 6-32
7. Signaling Gateway Configuration (Shelf Type 6) 7-1
Objectives 7-2
Contents 7-3
Signaling Gateway Description 7-5
SG/SAAL-NNI FUNCTIONS 7-6
SIGNALING GATEWAY APPLICATION 7-7
WG POINT CODE 7-8
WG CONTROL PLANE: SIGNALING GATEWAY 7-9
SG COMMUNICATION (1 PC FOR PS AND CS) 7-10
SG COMMUNICATION (1 PC FOR PS AND 1 PC FOR CS) 7-11
WG ATM AND IP CONFIGURATION FOR SIGNALING 7-13
SG Provisioning for Packet Switched 7-15
SG GIPS PROVISIONING FOR LU INTERFACE 7-16
SIGNALING GATEWAY PROVISIONING METHODOLOGY 7-17
STEP 1: SG APPLICATION PROVISIONING FOR PS 7-18
STEP 2: SG PROVISIONING: GIPS 2 7-19
STEP 3: SS7 CONFIGURATION FOR PS 7-20
STEP 3: SS7 PROVISIONING: LINKSET TO RNC 7-21
SG Provisioning for Circuit Switched: RANAP Signaling (from RNC to MSC) 7-23
SG GIPS PROVISIONING 7-24
STEP 1: SG APPLICATION PROVISIONING 7-26
STEP 2: SG PROVISIONING: GIPS 2 7-27
STEP 3 & 4: SS7 CONFIGURATION 7-28
STEP 3 & 4: WG CS RANAP SIGNALING 7-29
STEP 3: SS7 PROVISIONING : LINKSET TO RNC 7-31
STEP 4: SS7 PROV: LINKSET TO MEDIA GATEWAY (CS) 7-32
SG Provisioning for Circuit Switched: Virtual Media Gateway Provisioning 7-33
WG CS C ONNECTION MANAGER SIGNALING 7-34
VIRTUAL MEDIA GATEWAY PROVISIONING METHODOLOGY 7-35
VMG APPLICATION PROVISIONING 7-36
UM641 03.02 July 2003

xiv
VMG PROVISIONING: LU INTERFACE 7-37

VMG PROVISIONING: INTERFACE TO WMG 7-38
SAAL-NNI/ATM Provisioning 7-41
SAAL-NNI GIPS PROVISIONING 7-42
ATM AND IP CONFIGURATION FOR CS SIGNALING 7-43
SAAL-NNI PROVISIONING METHODOLOGY 7-44
SAAL-NNI PROVISIONING: GIPS 8 7-45
ATM VCC TO AN 7-46
8. Wireless Gateway ATM Configuration 8-1
Objectives 8-2
Contents 8-3
Aggregation Node configuration overview 8-5
AGGREGATION NODE FUNCTIONS 8-6
VCC ON LU 8-7
VCC ON GN 8-8
WG INTERNAL VCC 8-9
WG IP ROUTING CONFIGURATION 8-10
WG ATM AND IP CONFIGURATION 8-11
AN interfaces provisioning (PVC) 8-13
I/O CARD PROVISIONING ME THODOLOGY (1) 8-14
PHYSICAL (OPTICAL ) PORTS PROVISIONING: AUTOMATIC PROTECTION SWITCHING (APS) 8-15
ATM INTERFACE TO AN 8-17
NRP ATM CONNECTION FOR SIGNALING VCC 8-18
STEP 3: IP/ATM PROVISIONING 8-20
STEP 3: AN VIRTUAL ROUTER PROVISIONING 8-21
STEP 3.C: IP ROUTING (1) 8-22
STEP 3.D: IP ROUTING (2) 8-23
AN interfaces provisioning (SVC) 8-25
NODAL MANAGEMENT: MASTER/SLAVE CONFIGURATION 8-26
MASTER/SLAVE CONFIGURATION : MASTER SIDE 8-27
MASTER/SLAVE CONFIGURATION SLAVE SIDE 8-28
UM641 03.02 July 2003

xv
MASTER/SLAVE CONFIGURATION : SVC CREATION BETWEEN MASTER AND SLAVE 8-29

MASTER/SLAVE CONFIGURATION : SVC CREATION THROUGH AGGREGATION NODE 8-30
SG AND USC COMMUNICATION 8-31
SG AND USC COMMUNICATION : SVC CREATION BETWEEN USC AND SG APPLICATIONS 8-32
SG AND USC COMMUNICATION : SVC CREATION THROUGH AGGREGATION NODE 8-33
USC, USD AND MAP COMMUNICATION 8-34
USD AND USC COMMUNICATION : SVC CREATION BETWEEN
USC AND USD APPLICATIONS 8-35
9. WG Integration and Troubleshooting 9-1
Objectives 9-2
Contents 9-3
Passport component state description 9-5
WG components state: example 9-6
Components state change (1) 9-7
Passport Alarm Format 9-8
Alarm Identification 9-9
Passport Alarm Index Groups 9-10
Component state change (2) 9-11
Example of SCN Generation 9-12
10. Acronyms and Abbreviations 10-1
UM641 03.02 July 2003

xvi
Introduction
Section 1
Introduction
UM641 03.02/EN 1-1 July 2003

Introduction
UMTS Courses
Duration/days
• UM30 Wireless Gateway Detailed Description 2

• UM31 GGSN Detailed Description 1
• UM100 Wireless Gateway On-Site Maintenance 4
• UM101 GGSN On-Site Maintenance 1
• UM640 Passport 7K/15K Operation and Configuration 3
• UM641 WG Configuration & Integration 5
• UM642 GGSN Operation and Configuration 3
• UM068 UMTS OAM Introduction 2
• UM650 UMTS OAM for Packet Switched Core Network 3
UM641 03.02/EN 1-2 July 2003

Introduction
Wireless Gateway Support Engineer

TL3 UM10 TL4
TCP/IP for GPRS UMTS System Overview ATM Detailed Description
UM30
WG Detailed Description
UM640
Passport 7K/15K Operation and Configuration
UM641
WG Configuration & Integration
UM641 03.02/EN 1-3 July 2003

Introduction
GGSN Support Engineer
TL3 UM10 TL4

TCP/IP for GPRS UMTS System Overview ATM Detailed Description
UM31
GGSN Detailed Description
UM642
GGSN Operation and
Configuration
UM641 03.02/EN 1-4 July 2003

Introduction
Preside Support Engineer

UM30 UM31
WG Detailed Description GGSN Detailed Description
UM640
Passport 7K/15K Operation
and Configuration
UM641 UM642
WG Configuration & GGSN Operation &
Integration Configuration
UM68
UMTS OAM Introduction
UM650
UMTS OAM for Packet Core Network Wireless Gateway Configuration and Integration
UM641 03.02/EN 1-5 July 2003

Introduction
UMTS First Line Engineer
Wireless Gateway GGSN
UM000
UMTS Introduction
optional
UM100 UM101
WG On-Site Maintenance GGSN On-Site Maintenance
UM641 03.02/EN 1-6 July 2003

Introduction
Objectives
Upon completion of this section, you will be able to:
• Describe the Wireless Gateway Passport component architecture

• Detail the ways of switching and routing data, voice and signaling
in the Wireless Gateway
• Configure all Wireless Gateway shelves by using the Command
Line Interface
• Integrate the Wireless Gateway
UM641 03.02/EN 1-7 July 2003

Introduction
Contents
Section 1 Introduction
Section 2 WG Description
Section 3 Cards and Software Configuration
Section 4 Passport IP Servers (GIPS)

Section 5 U-SGSN Configuration
Section 6 Wireless Media Gateway Configuration
Section 7 Signaling Gateway and SAAL -NNI Configuration
Section 8 Wireless Gateway ATM Configuration

Section 9 Wireless Gateway Integration and Troubleshooting
UM641 03.02/EN 1-8 July 2003

Introduction
Student notes
UM641 03.02/EN 1-9 July 2003

Introduction
Student notes
UM641 03.02/EN 1-10 July 2003

Wireless Gateway Overview
Section 2
UM641 03.02/EN 2-1 July 2003

Objectives
• Introduce the Wireless Gateway

• Describe the Wireless Gateway interfaces for Packet Switched
and Circuit Switched Core Network
UM641 03.02/EN 2-2 July 2003

Contents
Wireless Gateway Shelves Overview
Wireless Gateway Interfaces
UM641 03.02/EN 2-3 July 2003


DNS HLR
SCP Shelf
Type 1 U-SGSN
CGF
U- SGSN + Type 3
(extention
extention))
LIG-- D
LIG Shelf
SIG
Type 2 Packet
GGSN Switched
RNC AN Shelf SG
Type 6
External Circuit
SG Shelf AN
Type 4 interfaces Switched
Shelf
WMG Type 5 WMG
MSC
Wireless Gateway Wireless Gateway Overview 2-4
Wireless Gateway
A complete Wireless Gateway (for Packet Switched and Circuit Switched) is
composed of:
• 1 Aggregation Node
• the U-SGSN function (Shelf Type 1 or Type 2 or Type 3) for Packet Switched
• the Wireless Media Gateway function (Shelf Type 5 or Type 4) for Circuit
Switched
• the Signaling Gateway function (Shelf Type 6 or Type 2 or Type 4 ) for Packet
Switched and Circuit Switched
UM641 03.02/EN 2-4 July 2003

Wireless Gateway Packet Switched

Core Network Interfaces HLR
Ge SCP
Gr
DNS
Server
HP--SIG
HP
SG
U-SGSN LIG
RNC Gr’, Ge’
X1
ATM IP Backbone
CGF
Ga
Iu ATM
AN
Gn Gi
WG for PS
GGSN
Packet Switched Wireless Gateway

The Wireless Gateway for Packet Switched only is composed of:
• 1 Aggregation Node (AN)
• the U-SGSN function (Shelf Type 1)
• the Signaling Gateway function (Shelf Type 6 or Type 2 for PS)
Interfaces:
• Iu: the interface between the Access and the Core Networks. In Nortel Network’s
implementation, this is the interface between the RNC and the Wireless Gateway. The
Wireless Gateway is a common Iu interface termination point for both the Packet
Switched (PS) and the Circuit Switched (CS) domains. The transport layer of the Iu
interface is based on ATM and supports SPVCs connected to the Aggregation Node.
• Gn: the interface between the U-SGSN and the GGSN. The transport layer of the Gn
interface is based on Ip over ATM.
• Gp: the interface between the U-SGSN in one PLMN and a GGSN in a different PLMN.
The Gn and Gp interfaces share the same physical interface.
• Gr: the SS7 interface between the SS7 IP Gateway (SIG) and the Home Location
Register (HLR).
• Ge: the SS7 interface between the SIG and the Signal Connection Control Part (SCCP).
• Gr’/Ge’: the TCP/IP interface between the U-SGSN and the SIG. It is a Nortel Networks’
proprietary messaging interface: SCCP Client Interface Protocol.
• Ga: the interface between the 3G-SGSN and the Charging Gateway Function (CGF).
Legal Interception: every physical SGSN is linked by its own interface to a Delivery
Function (DF) of the Lawful Interception architecture. Consequently, interrogation as well
as invocation) independently from all other SGSNs.
The Legal Interception Common Protocol stack is used to provide both the administration
and delivery functions of the packet data legal interception network.
• X1: A set of three (X1.1 - Administration, X1-2 - intercept related information, X1-3
communication content) between a network and a Lawful Intercept Delivery Domain.
UM641 03.02/EN 2-5 July 2003

Wireless Gateway Circuit Switched

Core Network Interfaces
SG
RNC
ATM
Iu cs’
WMG mux
MSC
Iu
AN
WG for CS
Circuit Switched Wireless Gateway

A Circuit Switched Wireless Gateway is composed of:
• the Wireless Media Gateway function (Shelf Type 4 or 5)
• the Signaling Gateway function (Shelf Type 6 or 4 for CS)
CS Interfaces are:
implementation, this is the interface between the RNC and the Wireless Gateway.
The Wireless Gateway is a common Iu interface termination point for both the
Packet Switched (PS) and the Circuit Switched (CS) domains. The transport layer
of the Iu interface is based on ATM and supports SPVCs connected to the
Aggregation Node.
• Iu-cs’: the interface between the Wireless Gateway and the Mobile Switching
Center (MSC).
UM641 03.02/EN 2-6 July 2003

Student notes
UM641 03.02/EN 2-7 July 2003

Student notes
UM641 03.02/EN 2-8 July 2003

Cards and Software Configuration
Section 3
UM641 03.02/EN 3-1 July 2003

Objectives
• Configure cards and software for all Wireless Gateway shelves
Wireless Gateway Cards & Software Configuration 3-2
UM641 03.02/EN 3-2 July 2003

Contents
Aggregation Node Software Configuration

Type 1 Shelf Cards and Software Configuration
UM641 03.02/EN 3-3 July 2003

Wireless Gateway Shelf Definitions

Type 1 Type 2 Type 3 Type 4e (Enhanced)
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
4pSTM1/TDM
4pSTM1/TDM
VSP2
VSP2
USD
USD
USD
USD
USD
USC
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
SG
SG
CP
CP
CP
CP
CP
CP
SG
SG
CP
CP
8 9 10 11 12 13 14 15
8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
VSP2
VSP2
MAP
MAP
USC
USC
USD
USD
USD
USD
USD
USD
SAS
SAS
SG
SG
SG
SG
SG
SG
SG
SG
SG
SG
Type 4 Type 5 Type 6 Type 5e (Enhanced)
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
4pSTM1/TDM
4pSTM1/TDM
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
CP
CP
CP
CP
CP
CP
CP
CP
SG
SG
SG
SG
SG
SG
SG
SG
8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15 8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
SG
SG
SG
SG
SG
SG
SG
SG
SG
SG
Shelf Types
There are (6) different Wireless Gateway Passport 15000 (PP15K) shelf types
defined and pre-engineered for the the UMTS 3.0 Market Model product offerings for
the USGSN, UMGW, or UWGW. Two shelves are available in an enhanced version
that supports a 4-STM1 TDM card. A shelf type is determined by the shelf pack fill.
Any combination of two of these shelf types may be mounted in a PP15K cabinet
(NTHR96xx). The following figures indicate the (6) different she lf types with there
maximum packfill. All provisioning for the USGSN, UMGW, or UWGW must follow
these shelf types. It is not mandatory that the packfills be complete initially, but when
expanding, the packfill must follow these circuit pack patterns depending on which
shelf type you are adding packs to.
The UWGW is made up of any or all of the (6) shelf types.
For the USGSN you can use the following shelf types:
1. Shelf Type 1
2. Shelf Type 2
3. Shelf Type 3
For the UMGW you can use the following shelf types:
1. Shelf Type 4
2. Shelf Type 5
3. Shelf Type 6
An additional shelf is required for the AN function in each model.
UM641 03.02/EN 3-4 July 2003

Aggregation Node Software

Configuration
UM641 03.02/EN 3-5 July 2003

Aggregation Node Shelf

0 1 2 3 4 5 6 7
4pATM/STM1
4pATM/STM1
• CP
– 1+1 WARM redundancy
CP
CP
• I/O
– 1+1 HOT standby with APS
(Access Protection
Switching)
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
Aggregation Node (AN) Shelf

The Aggregation Node is a Passport 15K shelf that connects to every other shelf in
the Wireless Gateway. It also connects to external networks that transport Iu and Gn
traffic. The AN supports only Passport Carrier Data Networks features (no UMTS and
Wireless applications). All multi-shelf communication is routed through the AN. The
AN allows the Wireless Gateway configuration to change internally, to add capacity or
perform maintenance without affecting the transport network or re-engineering
network connectivity. This is a required shelf in the Wireless Gateway.
Given the variability of connectivity options between the AN and the network
(topology, network connectivity options, network domains, routing, etc.), the I/O
hardware to the network is not included in the Market Models but must be engineered
and added on a per site basis.
The AN provides the following benefits and services for the Wireless Gateway:
• Aggregates all I/O between the network and the Wireless Gateway cluster
maximizing utilization of I/O connections at the network edge
• Inter-shelf communication device for the Wireless Gateway shelves providing
adequate and deterministic communication characteristics such as connectivity,
routing, redundancy, and latency.
• Isolates the Wireless Gateway function from the network via a widely dispersed
Passport 15000 product increasing the successful probability of inter-operability.
• Streamlines the opportunity to introduce Passport Services along with the
wireless application by concentrating the Passport base functionality within the
Passport 15000 AN, e.g., Soft PVC.
UM641 03.02/EN 3-6 July 2003

AN card configuration
16pOC3SmIrAtm or 4pOC12SmIrAtm cards are used as ATM interfaces
Shelf
Card/0 Card/2 Card/6 Card/8

Card/1 Card/3 Card/7 Card/9
cardtype CPeE cardtype cardtype 2pGPDsk cardtype

16pOC3SmIrAtm 16pOC3SmIrAtm
or 4pOC12SmIrAtm or 4pOC12SmIrAtm
0 1 2 3 4 5 6 7
4pATM/STM1
4pATM/STM1
2pGPDsk
2pGPDsk
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
Aggregation Node cards and Software configuration methodology:

• AN card configuration: Shelf branch provisioning
• Provision the cardtype attribute under the Shelf Card/ component. Values can
be:
- CPeE for CP cards (Shelf Card/0 and Shelf Card/1 components)
- 4pOC12SmIrAtm or 16pOC3SmIrAtm for ATM cards (Shelf Card/2, Shelf
Card/3, Shelf Card/8 … Shelf Card/15 components)
• The 4-port OC-3/STM-1 ATM FP (4pOC3SmIrAtm, 4pOC3MmAtm) can
also reside in the AN
- 2pGPDsk for Ethernet Connectivity (Shelf Card/6 and Shelf Card/7
components)
• AN software configuration: Software branch provisioning
• AN Logical Processor configuration: LP branch provisioning
Ethernet Line Switchover

In UMTS03 the 2 port GPDsk card is supported on the AN to provide Ethernet
connectivity. In this case, with a spare 2pGPDsk card used (1:1 2pGPDsk cards on
the AN) two Ethernet ports can be configured : 1 active Ethernet port on one card, 1
hot standby Ethernet port on the adjacent card. When the active Ethernet port
becomes unavailable, the traffic is automatically switched over to the hot standby
Ethernet port.
UM641 03.02/EN 3-7 July 2003

AN software configuration
Sw
avlist !base_CD02S1A ip_ CD02S1A networking_ CD02S1A

atmNetworking_ CD02S1A wanDte_ CD02S1A fabric_ CD02S1A
LPT/CP LPT/ATM LPT/ETH
featurelist ! ip oamenet mvr featurelist ! ip atmcore atmmpe atmPnni featurelist ! ip atmMpe

wNapIntercept aps

• Provision the avList attribute under the Software component. Values are for the
AN:
- base_ CD02S1A ip_ CD02S1A networking_ CD02S1A
atmNetworking_ CD02S1A wanDte_ CD02S1A fabric_ CD02S1A
• Add LPT/ components under the Software component
- LPT/CP for CP cards
- LPT/ATM for ATM cards
- LPT/ETH for Ethernet cards
• Provision the featureList attribute under each Software LPT/ component. Values
are:
- ip oamenet mvr for the Software LPT/CP component
- ip atmcore atmmpe atmPnni wNapIntercept aps for the Software LPT/ATM
component
- ip atmMpe for the Software LPT/ETH
UM641 03.02/EN 3-8 July 2003

AN logical processors configuration
LP/0 LP/2 LP/3 LP/6 LP/8 LP/9
mainCard Shelf Card/0 mainCard Shelf Card/2 mainCard Shelf Card/3 mainCard Shelf Card/6 mainCard Shelf Card/8 mainCard Shelf Card/9
spareCard Shelf Card/1 spareCard ! spareCard ! spareCard Shelf Card/7 spareCard ! spareCard !
logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType
Sw Lpt/CP Sw Lpt/ATM Sw Lpt/ATM Sw Lpt/ETH Sw Lpt/ATM Sw Lpt/ATM
0 1 2 3 4 5 6 7
4pATM/STM1
4pATM/STM1
2pGPDsk
2pGPDsk
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1
4pATM/STM1


• Add one LogicalProcessor/ component per card (maincard):
- LP/0 for CP cards
- LP/2, LP/3, LP/8… LP/15 for ATM cards
- LP/6 for Ethernet cards
• Provision each LP/ component by filling its attributes:
- maincard: the value is the corresponding Shelf Card/ component
- sparecard: (if 1 + 1 redundancy) the value is the corresponding Shelf Card/
component
- logicalProcessorType: the value is the corresponding Software LPT/
component
UM641 03.02/EN 3-9 July 2003

Student notes
UM641 03.02/EN 3-10 July 2003

Shelf Type 1 Software Configuration

U-SGSN Function
UM641 03.02/EN 3-11 July 2003

Shelf Type 1
Type 1
0 1 2 3 4 5 6 7 • CP
• USD
USD
USD
USD
USD
USD
USC
CP
CP
– Load sharing across 2 shelves

• USC
8 9 10 11 12 13 14 15 • MAP
– 1+1 COLD standby
4pATM/STM1
4pATM/STM1
• SAS/LI
USC
USC
MAP
MAP
SAS
SAS
– 1+1 COLD standby

• I/O
(Access Protection Switching)
Shelf Type 1
Type 1 shelves are used in both the USGSN and the UWGW models.
The shelf contains CP, USC, USD, MAP and SAS/LI cards. ATM I/O cards are used
to connect to the AN shelf.
The CP3 card is the Control Processor (NTHW08AA) used for the NM and OAM
applications. It uses 1+1 redundancy in WARM standby mode.
The USD application uses a 4pOC3MmlrAtm (NTHR17DA) card. It uses load sharing
with a minimum of 2 cards separated across shelves.
The USC application uses a 2pGPDsk (NTHW10AA) card. It uses load sharing with a
minimum of 2 cards separated across shelves.
The MAP application uses a 2pGPDsk (NTHW10AA) card. It uses 1+1 redundancy in
COLD standby mode.
The SAS/LI applications uses a 2pGPDsk (NTHW10AA) card. It uses 1+1
redundancy in COLD standby mode.
The I/O function uses a 4pOC3SmlrAtm (NTHR21DA) card. It uses 1+1 redundancy
in HOT standby mode with APS.
The I/O function can also use the 4pOC3MM (NTHR17DA) and 16pOC3SM
(NTHW31) cards.
UM641 03.02/EN 3-12 July 2003

Shelf Type 1 card configuration

U-SGSN
Shelf
Card/1 Card/3 Card/9 Card/11 Card/13 Card/15

cardtype CPeE cardtype cardtype cardtype cardtype cardtype

4pOC3MmAtm 4pOC3SmIrAtm 2pGPDsk 2pGPDsk 2pGPDsk
Type 1
0 1 2 3 4 5 6 7
USD
USD
USD
USD
USD
USC
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
USC
USC
SAS
SAS
MAP
MAP
Shelf Type 1 cards and software configuration methodology:

• Shelf Type 1 card configuration: Shelf branch provisioning
be:
- 4pOC3MmAtm for USD cards
- 4pOC3SmIrAtm for ATM cards (ATM I/O)
• The 4pOC3MM and 16pOC3SM cards can also be used.
- 2pGpDsk for USC, MAP and SAS/LI cards
• Shelf Type 1 software configuration: Software branch provisioning
• Shelf Type 1 Logical Processor configuration: LP branch provisioning
UM641 03.02/EN 3-13 July 2003

Shelf Type 1 software configuration

U-SGSN
Sw
avlist ! base_U3001AO ip_U3001AO networking_U3001AO

atmNetworking_U3001AO wanDte_U3001AO
wirelessCommon_U3001AO wanDte_U3001AO
genericUtilities _U3001AO fabric_U3001AO
wirelessSgsnCommon_U3001AO wirelessNssBss_U3001AO
wirelessGateway _U3001AO wirelessUSgsn_U3001AO
gprsHlrsim _U3001AO
LPT/CP LPT/ATM LPT/USD LPT/USC LPT/MAP LPT/SAS
featurelist ! featurelist ! ip featurelist ! featurelist ! featurelist ! ip featurelist ! ip

uSgsn ip atmPnni sgsnUsd ipServer sgsnUsc ipServer atmmpe atmmpe
oamenet mvr wNapIntercept ip atmMpe ip atmMpe mapStack ipServer
gprshlrsim atmMpe ipServer atmCore atmPnni atmCore ipServer sgsnAcct lisp
aps saalnni sgsnDnsAgent
objPoolManager

• Provision the avList attribute under the Software component. Values are for the AN:
- base_U3001AO ip_U3001AO networking_U3001AO atmNetworking_U3001AO
wanDte_U3001AO wirelessCommon_U3001AO wanDte_U3001AO
genericUtilities_U3001AO fabric_U3001AO wirelessSgsnCommon_U3001AO
wirelessNssBss_U3001AO wirelessGateway_U3001AO wirelessUSgsn_U3001AO
gprsHlrsim_U3001AO
- LPT/ATM for ATM I/O cards
- LPT/USD for USD cards
- LPT/USC for USC cards
- LPT/MAP for MAP cards
- LPT/SAS for SAS/LI cards
• Provision the featureList attribute under each Software LPT/ component. Values are:
- ip oamenet mvr uSgsn gprsHlrsim for the Software LPT/CP component
- ip atmmpe atmPnni wNapIntercept aps saalNni IpServer for the Software LPT/ATM
component
- ip atmmpe sgsnUsd IpServer atmPnni atmCore for the Software LPT/USD
component
- ip atmmpe mapStack ipServer for the Software LPT/MAP component
- ip atmmpe sgsnUsc IpServer atmPnni atmCore sgsnDnsAgent for the Software
LPT/USC component
- ip atmmpe sgsnAcct ipServer Lisp for the Software LPT/SAS component
UM641 03.02/EN 3-14 July 2003

Shelf Type 1 logical processors

configuration
LP/3 LP/9 LP/11

LP/0 LP/2 LP/8 LP/10 LP/12 LP/14
spareCard Shelf Card/1 spareCard ! spareCard ! spareCard ! spareCard Shelf Card13 spareCard Shelf Card/15
logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessor Type

Sw Lpt/CP Sw Lpt/USD Sw Lpt/ATM Sw Lpt/USC Sw Lpt/MAP Sw Lpt/SAS
Type 1
0 1 2 3 4 5 6 7
USD
USD
USD
USD
USD
USC
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
USC
USC
SAS
SAS
MAP
MAP
Shelf Type 1 cards and Software configuration methodology:

- LP/0 for CP cards
- LP/2, LP/3, … for all USD cards
- LP/8 and LP/9 for ATM I/O cards
- LP/10 and LP/11 for USC cards
- LP/12 and LP/13 for MAP cards
- LP/14 and LP/15 for SAS/LI cards
component
component
UM641 03.02/EN 3-15 July 2003

Student notes
UM641 03.02/EN 3-16 July 2003


Wireless Media Gateway and Signaling Gateway
UM641 03.02/EN 3-17 July 2003

Shelf Type 4
Type 4
0 1 2 3 4 5 6 7 • CP
32pTDM/E1
32pTDM/E1
• VSP2
VSP2
VSP2
SG
SG
CP
CP
– N+1 redundancy across 2 shelves

• 32p E1 TDM
8 9 10 11 12 13 14 15 • SG
– 1+1 HOT standby
4pATM/STM1
4pATM/STM1
• I/O
VSP2
VSP2

SG
SG
SG
SG
Shelf Type 4
Type 4 shelves are used in the USGSN and the UWGW models.
The shelf contains CP, VSP2, SG and 32p E1 TDM cards. ATM I/O cards are used
The VSP2 application uses the (NTHW87xx) card. It uses N+1 redundancy with a
The 32p E1 TDM card uses the (NTHW87xx) card. It uses N+1 redundancy with a
The SG application uses a 4pOC3MmlrAtm (NTHR17DA) card. It uses 1+1
redundancy in HOT standby mode.
(NTHW31) cards.
UM641 03.02/EN 3-18 July 2003

Shelf Type 4e (Enhanced)

Type 4e (Enhanced)
0 1 2 3 4 5 6 7
• CP
4pSTM1/TDM
4pSTM1/TDM
• VSP2
VSP2
VSP2
SG
SG
CP
CP

• 4p STM1 TDM
8 9 10 11 12 13 14 15 • SG
– 1+1 HOT standby
4pATM/STM1
4pATM/STM1
• I/O
VSP2
VSP2
SG
SG
SG
SG

Shelf Type 4 (Enhanced)

The shelf contains CP, VSP2, SG and 4p STM1 TDM cards. ATM I/O cards are used
The 4p STM1 TDM card uses the (NTHW70xx) card. It uses N+1 redundancy with a
(NTHW31) cards.
UM641 03.02/EN 3-19 July 2003


WIRELESS MEDIA GATEWAY (WMG)-SIGNALING GATEWAY (SG)
Shelf
Card/1 Card/3 Card/5 Card/7 Card/9

cardtype CPeE cardtype VSP2 cardtype 4pOC3MmAtm cardtype 32pE1Aal cardtype 4pOC3SmIrAtm
or 4pOC3ChTDM
0 1 2 3 4 5 6 7
32pTDM/E1
32pTDM/E1
VSP2
VSP2
CP
CP
SG
8 9 10 11 SG
12 13 14 15
4pATM/STM1
4pATM/STM1
VSP2
VSP2
SG
SG
SG
SG

be:
- 4pOC3MmAtm for SG (Signaling Gateway applications) cards
- VSP2 for VSP (TRAU functions) cards
- 32pE1Aal or 4pOC3ChTDM for TDM cards (E1 interface to MSC)
UM641 03.02/EN 3-20 July 2003


WIRELESS MEDIA GATEWAY (WMG)-SIGNALING GATEWAY (SG)
Sw
avlist ! base_U3001AO ip_ U3001AO networking_U3001AO

atmNetworking_U3001AO wirelessCommon_U3001AO wanDte_U3001AO
genericUtilies _ U3001AO fabric_ U3001AO wirelessNssBss_U3001AO
wirelessSgsnCommon_U3001AO wirelessUSgsn_U3001AO
wirelessGateway _U3001AO p v g_U3001AO ss7_U3001AO
LPT/CP LPT/SG LPT/ATM LPT/WGAMRVSP LPT/WGAMRCSDVSP LPT/WGTDM
featurelist ! Ip featurelist ! wgamr featurelist ! wgamrcsd

featurelist ! ip featurelist ! Sg sccp featurelist ! nsta
oamenet mvr mtp3 atmCore atmpnni atmcore
atmPnni saalnni vmg aps saalNni
atmMpe ip ipServer objPoolManager
ipServer
wNapIntercept

- base_U3001AO ip_ U3001AO networking_U3001AO
atmNetworking_U3001AO wirelessCommon_U3001AO wanDte_U3001AO
genericUtilies_ U3001AO fabric_ U3001AO wirelessNssBss_U3001AO
wirelessGateway_U3001AO pvg_U3001AO ss7_U3001AO
- LPT/SG for SG cards
- LPT/WGAMRVSP for VSP cards with AMR feature for voice only
- LPT/ WGAMRCSDVSP for VSP cards with AMR/CSD feature for voice and Circuit
Switched Data (CSD)
- LPT/WGTDM for TDM cards
- ip oamenet mvr uSgsn for the Software LPT/CP component
component
- Sg sccp mtp3 atmCore atmPnni saalnni vmg atmMpe ip ipServer for the Software
LPT/SG component
- wgamr for the Software LPT/ WGAMRVSP component
- wgamrcsd for the Software LPT/ WGAMRCSDVSP component
- nsta for the Software LPT/ WGTDM component
UM641 03.02/EN 3-21 July 2003


configuration
LP/3 LP/7 LP/9

spareCard Shelf Card/1 spareCard ! spareCard Shelf Card/5 spareCard spareCard ! spareCard !
Sw Lpt/CP Sw Lpt/WGAMRVSP Sw Lpt/SG Sw Lpt/WGTDM Sw Lpt/ATM Sw Lpt/WGAMRCSDVSP
0 1 2 3 4 5 6 7
32pTDM/E1
32pTDM/E1
VSP2
VSP2
CP
CP
SG
SG
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
VSP2
VSP2
SG
SG
SG
SG


- LP/0 for CP cards
- LP/2, LP/3, LP/10 and LP/11 for all VSP2 cards
- LP/4, LP/5, LP/12, LP/13, … for all SG cards
- LP/6 and LP/7 for TDM cards
component
component
UM641 03.02/EN 3-22 July 2003


Wireless Media Gateway
UM641 03.02/EN 3-23 July 2003

Shelf Type 5
Type 5
0 1 2 3 4 5 6 7 • CP
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
• VSP2
VSP2
VSP2
CP
CP

• 32p E1 TDM
8 9 10 11 12 13 14 15
• I/O
4pATM/STM1
4pATM/STM1

VSP2
VSP2
VSP2
VSP2
VSP2
VSP2
Shelf Type 5
The shelf contains CP, VSP2 and 32p E1 TDM cards. ATM I/O cards are used to
connect to the AN shelf.
The 32p E1 TDM card uses the (NTHW87xx) card. It uses N+1 redundancy with a
(NTHW31) cards.
UM641 03.02/EN 3-24 July 2003


Type 5e (Enhanced)
0 1 2 3 4 5 6 7
• CP
4pSTM1/TDM
4pSTM1/TDM
VSP2
VSP2
VSP2
VSP2
• VSP2
CP
CP

• 4p STM1/TDM
8 9 10 11 12 13 14 15
• I/O
4pATM/STM1
4pATM/STM1

VSP2
VSP2
VSP2
VSP2
VSP2
VSP2

Type 5e shelves can be used in the USGSN and the UWGW models.
The shelf contains CP, VSP2 and 4p STM1 TDM cards. ATM I/O cards are used to
connect to the AN shelf.
The 4p STM1 TDM card uses the (NTHW70xx) card. It uses N+1 redundancy with a
(NTHW31) cards.
UM641 03.02/EN 3-25 July 2003


WIRELESS MEDIA GATEWAY
Shelf

Card/1
cardtype VSP2 cardtype 32pE1Aal cardtype 4pOC3SmIrAtm cardtype 4pOC3SmIrAtm cardtype VSP2
cardtype CPeE
0 1 2 3 4 5 6 7
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
VSP2
VSP2
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2

be:
- VSP2 for VSP (TRAU functions) cards
- 32pE1Aal for TDM cards (E1 interface to MSC)
UM641 03.02/EN 3-26 July 2003


WIRELESS MEDIA GATEWAY
Sw
avlist !base_U3001AO ip_U3001AO networking_U3001AO

wanDte_U3001AO atmNetworking_U3001AO p v g_U3001AO
fabric_U3001AO wirelessCommon_U3001AO
genericUtilies _U3001AO wirelessNssBss _U3001AO
LPT/CP LPT/ATM LPT/WGAMRVSP LPT/WGAMRCSDVSP LPT/WGTDM
featurelist ! ip oamenet featurelist ! atmMpe ip featurelist ! wgamr featurelist ! wgamrcsd featurelist ! nsta
mvr uSgsn atmPnni wNapIntercept
IpServer objPoolManager
aps saalNni atmcore

- base_U3001AO ip_U3001AO networking_U3001AO wanDte_U3001AO
atmNetworking_U3001AO pvg_U3001AO fabric_U3001AO
wirelessCommon_U3001AO genericUtilies_U3001AO wirelessNssBss_U3001AO
- LPT/WGAMRVSP for VSP cards with AMR feature for voice only
- LPT/ WGAMRCSDVSP for VSP cards with AMR/CSD feature for voice and Circuit
Switched Data (CSD)
- LPT/WGTDM for TDM cards
component
- wgamr for the Software LPT/ WGAMRVSP component
- wgamrcsd for the Software LPT/ WGAMRCSDVSP component
- nsta for the Software LPT/ WGTDM component
UM641 03.02/EN 3-27 July 2003


configuration
mainCard Shelf Card/2 mainCard Shelf Card/7 mainCard Shelf Card/8 mainCard Shelf Card/9 mainCard Shelf Card/15
mainCard Shelf Card/0
spareCard ! spareCard spareCard ! spareCard ! spareCard !
spareCard Shelf Card/1
logicalProcessorType Sw logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType
logicalProcessorType
Lpt/WGAMRCSDVSP Sw Lpt/WGTDM Sw Lpt/ATM Sw Lpt/ATM Sw Lpt/WGAMRVSP
Sw Lpt/CP
0 1 2 3 4 5 6 7
32pTDM/E1
32pTDM/E1
32pTDM/E1
32pTDM/E1
VSP2
VSP2
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
VSP2
VSP2
VSP2
VSP2
VSP2
VSP2


- LP/0 for CP cards
- LP/2, LP/3, LP/10, LP/11, … for all VSP2 cards
- LP/6 and LP/7 for TDM cards
component
component
UM641 03.02/EN 3-28 July 2003


Signaling Gateway
UM641 03.02/EN 3-29 July 2003

Shelf Type 6
Type 6
0 1 2 3 4 5 6 7
• CP
• SG
SG
SG
SG
SG
SG
SG
CP
CP
– 1+1 HOT standby

• I/O
8 9 10 11 12 13 14 15 (Access Protection Switching)
4pATM/STM1
4pATM/STM1
SG
SG
SG
SG
SG
SG
Shelf Type 6
Type 6 shelves are used the UMGW models to increase signaling capacity.
The shelf contains CP, and SG cards. ATM I/O cards are used to connect to the AN
shelf.
UM641 03.02/EN 3-30 July 2003


Signaling Gateway
Shelf

Card/1
cardtype cardtype cardtype cardtype
4pOC3MmAtm 4pOC3MmAtm 4pOC3SmIrAtm 4pOC3SmIrAtm
cardtype CPeE
0 1 2 3 4 5 6 7
CP
CP
SG
SG
SG
SG
SG
SG
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
SG
SG
SG
SG
SG
SG

be:
UM641 03.02/EN 3-31 July 2003


Signaling Gateway
Sw
avlist ! base_U3001AO ip_U3001AO networking_U3001AO

atmNetworking_U3001AO wirelessCommon_U3001AO
wanDte_U3001AO genericUtilies _U3001AO fabric_U3001AO
ss7_U3001AO wirelessGateway _U3001AO
wirelessNssBss_U3001AO wirelessSgsnCommon_U3001AO
wirelessUSgsn_U3001AO
LPT/CP LPT/SG LPT/ATM
featurelist ! ip featurelist ! Sg sccp featurelist ! atmMpe ip

oamenet mvr uSgsn mtp3 atmCore atmPnni atmPnni wNapIntercept
saalnni vmg atmMpe ip IpServer objPoolManager
sgsnDnsAgent ipServer aps saalNni atmcore

wirelessCommon_U3001AO wanDte_U3001AO genericUtilies_U3001AO
fabric_U3001AO ss7_U3001AO wirelessGateway_U3001AO
component
LPT/SG component
UM641 03.02/EN 3-32 July 2003


configuration
LP/0 LP/2 LP/8 LP/9
mainCard Shelf Card/0 mainCard Shelf Card/2 mainCard Shelf Card/8 mainCard Shelf Card/9
spareCard Shelf Card/1 spareCard Shelf Card/3 spareCard ! spareCard !
logicalProcessorType logicalProcessorType logicalProcessorType logicalProcessorType
Sw Lpt/CP Sw Lpt/SG Sw Lpt/ATM Sw Lpt/ATM
0 1 2 3 4 5 6 7
CP
CP
SG
SG
SG
SG
SG
SG
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
SG
SG
SG
SG
SG
SG


- LP/0 for CP cards
- LP/2, LP/3, …, LP/10, LP/11, … for all SG cards (Signaling Gateway
applications)
component
component
UM641 03.02/EN 3-33 July 2003

Student notes
UM641 03.02/EN 3-34 July 2003


USD-Signaling Gateway
UM641 03.02/EN 3-35 July 2003

Shelf Type 2
Type 2
0 1 2 3 4 5 6 7
• CP
USD
USD
USD
USD
• USD
SG
SG
CP
CP

• SG
– 1+1 HOT standby
8 9 10 11 12 13 14 15
• I/O
4pATM/STM1
4pATM/STM1

SG
SG
SG
SG
SG
SG
Shelf Type 2
Type 2 shelves are used in both the USGSN and the UWGW models to increase PS
capacity.
The shelf contains CP, USD, and SG cards. ATM I/O cards are used to connect to
the AN shelf.
UM641 03.02/EN 3-36 July 2003


SIGNALING GATEWAY (SG) - USD
Shelf
Card/0 Card/2 Card/3 Card/2 Card/3 Card/8 Card/9

Card/1
cardtype cardtype cardtype cardtype cardtype cardtype
4pOC3MmAtm 4pOC3MmAtm 4pOC3MmAtm 4pOC3MmAtm 4pOC3SmIrAtm 4pOC3SmIrAtm
cardtype CPeE
0 1 2 3 4 5 6 7
USD
USD
USD
USD
CP
CP
SG
SG
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
SG
SG
SG
SG
SG
SG

be:
UM641 03.02/EN 3-37 July 2003


SIGNALING GATEWAY (SG) - USD
Sw
avList ! base_U3001AO ip_U3001AO networking_U2001K
LPT/CP LPT/ATM LPT/USD LPT/SG

featureList uSgsn featureList atmMpe ip featureList sgsnUsd featureList sg sccp
oamenet ip mvr atmPnni wNapIntercept IpServer ip atmMpe mtp3 atmCore
IpServer objPoolManager atmPnni atmCore atmPnni saalnni vmg
aps atmmpe ip ipServer


- sgsnUsd IpServer ip atmMpe atmPnni atmCore for the Software LPT/USD
component
LPT/SG component
component
UM641 03.02/EN 3-38 July 2003

Shelf Type 2 Logical Processors

Configuration
spareCard Shelf Card/1 spareCard ! spareCard ! spareCard Shelf Card/5 spareCard ! spareCard !
Sw Lpt/CP Sw Lpt/USD Sw Lpt/USD Sw Lpt/SG Sw Lpt/ATM Sw Lpt/ATM
0 1 2
USD 3 4 5 6 7
USD
USD
USD
CP
CP
SG
SG
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
SG
SG
SG
SG
SG
SG

be:
UM641 03.02/EN 3-39 July 2003

Student notes
UM641 03.02/EN 3-40 July 2003


USD Function
UM641 03.02/EN 3-41 July 2003

Shelf Type 3
Type 3
0 1 2 3 4 5 6 7 • CP
• USD
USD
USD
USD
USD
USD
USD
CP
CP

• I/O
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
USD
USD
USD
USD
USD
USD
Shelf Type 3
Type 3 shelves are used in both the USGSN and the UWGW models to further
increase PS capacity.
The shelf contains only CP, USD cards. ATM I/O cards are used to connect to the
AN shelf.
UM641 03.02/EN 3-42 July 2003


USD
Shelf

Card/1
cardtype cardtype cardtype cardtype
4pOC3MmAtm 4pOC3MmAtm 4pOC3SmIrAtm 4pOC3SmIrAtm
cardtype CPeE
0 1 2 3 4 5 6 7
USD
USD
USD
USD
USD
USD
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
USD
USD
USD
USD
USD
USD

be:
UM641 03.02/EN 3-43 July 2003


USD
Sw
avList ! base_U3001AO ip_U3001AO networking_U2001K
LPT/CP LPT/ATM LPT/USD

featureList uSgsn featureList atmMpe ip featurelist !
oamenet ip mvr atmPnni wNapIntercept sgsnUsd ipServer
IpServer objPoolManager ip atmMpe
aps atmCore atmPnni


- sgsnUsd IpServer ip atmMpe atmPnni atmCore for the Software LPT/USD
component
component
UM641 03.02/EN 3-44 July 2003

USD (type 3) Logical Processors

Configuration
LP/0 LP/2 LP/8 LP/9
mainCard Shelf Card/0 mainCard Shelf Card/2 mainCard Shelf Card/8 mainCard Shelf Card/9
spareCard Shelf Card/1 spareCard ! spareCard ! spareCard !
logicalProcessorType logicalProcessorType logicalProcessorType
logicalProcessorType
Sw Lpt/CP Sw Lpt/USD Sw Lpt/ATM Sw Lpt/ATM
0 1 2 3 4 5 6 7
USD
USD
USD
USD
USD
USD
CP
CP
8 9 10 11 12 13 14 15
4pATM/STM1
4pATM/STM1
USD
USD
USD
USD
USD
USD

be:
UM641 03.02/EN 3-45 July 2003

Student notes
UM641 03.02/EN 3-46 July 2003

Passport IP Server (GIPS)
Section 4
Passport IP Servers (GIPS)
UM641 03.02/EN 4-1 July 2003

Objectives
• Describe the GIPS process in Wireless Gateway

• Detail GIPS configuration in Wireless Gateway
Passport IP Servers 4-2
UM641 03.02/EN 4-2 July 2003

Contents
GPRS IP Servers Configuration for U-SGSN
An Example: GIPS for Gn interface
GIPS for USD and USC in U-SGSN
UM641 03.02/EN 4-3 July 2003

GIPS Configuration Principle in U-SGSN

AN
33.33.33.41
VR/3
Gn IP/ATM
C
10.60.10.222
o
r
e
Inter -shelf
IP/ATM N
10.60.10.220\30 e
t
Inter -shelf U-SGSN w
o
10.60.10.221
r
47.104.194.180
VR/3 k
10.60.11.112\30 10.60.10.128\30
GIPS 2
USD_Gn GIPS 10 USC IP/ETH
USD USC
USD card (slot 2) USC card (slot 10) Passport IP Servers 4-4
GIPS Provisioning
Principle of GIPS Provisioning is:
• create a GIPS application as an IP Server (with its IP address)
• create an IP interface on a Virtual Router to route the GIPS packets through the
IP Backbone (Core Network)
• link the GIPS to it(s) application(s) through one or many UDP/TCP Ports
This example illustrates the routing of GTP-U and GTP-C traffic from/to the Core
Network (IP Backbone) to/from the USD (GTP-U) and USC (GTP-C) applications.
UM641 03.02/EN 4-4 July 2003

Example : IP Servers for Gn interface
U-SGSN GGSN
application application application application
UDP UDP
UDP 3386 3386 UDP
PP/ IP address
Gips/ IP
IP
IP IP
PP/gips
RFC.1483 AtmMpe/ AtmMpe/ RFC.1483
ATM AtmIf/ AtmIf/

ATM
SDH/ SDH/
PHYSICAL PHYSICAL
GIPS Configuration
This slide illustrates the GIPS (GPRS IP Server) configuration i n the Passport
(for U-SGSN in this example):
• The Application (GTP-U or GTP-C) in the U-SGSN has to communicate with its
peer entity in the GGSN: they use the same UDP port.
• To configure IP routing from the application to the ATM interface on the U-SGSN,
the Passport has to be configured with a GIPS and a Virtual Router.
- The GIPS interfaces the application (through its UDP port) with the Virtual
router (VR) through an IP port and address on the GIPS.
- The Virtual router routes the IP packet containing the application from the
GIPS subnetwork to the Core Network (through Gn).
UM641 03.02/EN 4-5 July 2003

U-SGSN IP Servers for USD and USC

I/O USD USC
DNSAgent
GTP-U
99 MAP-
Client
GTP-U GTP-C
97 real99
VIRTUAL VIRTUAL GTP-C
ROUTER ROUTER real97
(VR/4) UDP UDP UDP UDP (VR/3) UDP
3386
UDP
2123
2152 3386 3386 2152
PP/GIPS2 PP/GIPS2 PP/GIPS10 UDP
_USD_IU Gips/2 Gips/18 _USD_GN _USC 53 Gips/10 UDP
IP IP IP 1234
10.60.10.114 47.104.222.203 47.104.222.201
10.60.10.113 10.61.10.113 10.60.10.121
PP/atmMpe PP/atmMpe
AtmIf/ AtmIMpe/
AtmIMpe/
Sdh/0
VCC/ VCC/

To AN
U-SGSN IP Servers
This slide illustrates the card provisioning for GIPS and Virtua l Router for one USD
card and one USC card only:
• USC card:
• one GIPS (GIPS/10) with an IP address on the same subnet than the
PP/GIPS10_USC interface of the VR/3
• 4 applications (GTP-C Real.97, GTP-C Real.99, MAP-Client, DNSAgent) reached
from the GIPS through different UDP Ports
• USD card:
• 2 GIPS:
- GIPS/2 with an IP address on the same subnet than the PP/GIPS2_USD_IU
interface of the VR/4 (for Iu interface)
- GIPS/18 with an IP address on the same subnet than the PP/
GIPS18_USD_GN interface of the VR/3
• 2 applications (GTP-U Real.97, GTP-U Real.99) reached from the 2 GIPS
through different UDP Ports
Each Virtual Router has an interface to forward/receive IP/ATM traffic to/from the
RNC (Iu interface: VR/4) or GGSN (Gn interface: VR/3)
UM641 03.02/EN 4-6 July 2003

WG GIPS configuration: U-SGSN

AN
RNC Iu 172.253.3.3 33.33.33.41
VR/4 VR/3 Gn IP/ATM
IP/ATM
10.60.10.226 10.60.10.222
VR/5
IP/ATM
10.60.10.230 (optional )
VR/6
10.60.10.234
136.147.129.19
CP
VR/0 Inter -shelf
C
Inter -shelf Inter -shelf Inter -shelf
o
10.60.10.232/30 10.60.10.228/30 10.60.10.224/30 10.60.10.220/30 r
OAM LAN e
IP/ATM IP/ATM
136.147.129.128/20 (optional ) (optional ) IP/ATM IP/ATM
N
CP Inter -shelf Inter -shelf Inter -shelf Inter -shelf U-SGSN
136.147.129.18 VR/0 e
10.60.10.233 10.60.10.225 10.60.10.221
10.60.10.229 t
47.104.194.80 w
VR/6 VR/5 VR/4 VR/3
47.104.194.180 o
r
10.60.10.161/30 10.60.222.200/30 10.60.222.200/30 10.60.11.112/30 10.60.10.128/30
k
GIPS SAS/LI GIPS MAP GIPS USD_Iu GIPS USD_Gn GIPS USC IP/ETH
SAS/LI TCAP USD USD USC

IP/ETH
SAS/LI card (slot 14) MAP card (slot 12) USD card (slot 2) USCPassport
card (slot 10)
IP Servers 4-7
WG GIPS Configuration
This illustrates an example of GIPS provisioning in a U-SGSN and Virtual Router
provisioning in Aggregation Node and U-SGSN.
GIPS provisioning: 5 GIPS in 4 cards:
• GIPS USC in a USC card
• GIPS USD_Iu in a USD card
• GIPS USD_Gn in the same USD card
• GIPS MAP in a MAP card
• GIPS SAS/LI in a SAS/LI card
Virtual Router provisioning (in AN and U-SGSN):

• VR/3 for Gn interface
• VR/4 for Iu interface
• VR/5 for Gr/Ge interface (optional, if IP/ATM routing through AN)
• VR/6 for Ga/X1 interface (optional, if IP/ATM routing through AN)
Note: VR/2 can be added also for DNS Agent routing to DNS Server.
VR/1 can also be added if SAAL-NNI application is configured on the shelf (in the
I/O ATM card)
VR/0 is used in each WG shelves for OAM traffic.
UM641 03.02/EN 4-7 July 2003

Student notes
UM641 03.02/EN 4-8 July 2003

U-SGSN Configuration
Section 5
UM641 03.02/EN 5-1 July 2003

Objectives
• Describe and draw the Passport CAS components for U-SGSN provisioning
• Configure the USD card and its applications
• Configure the USC card, its applications and its interface to the Core Network
• Configure the MAP card, its applications and its interfaces to the SIG
• Configure the HLR Simulator
• Configure the SAS (accounting) and LIAF functions and its interfaces
• Configure the U-SGSN IP/ATM interface to the Aggregation Node
U-SGSN Configuration 5-2
UM641 03.02/EN 5-2 July 2003

Contents
• U-SGSN Description
• U-SGSN User plane: USD Card Provisioning
• U-SGSN Control Plane: USC Card Provisioning
• U-SGSN Control Plane: MAP Card Provisioning
• HLRSim Provisioning
• U-SGSN Accounting: SAS Function Provisioning
• U-SGSN Lawful Interception: LIAF Function Provisioning
• Interface to AN: I/O Card Provisioning
UM641 03.02/EN 5-3 July 2003

UM641 03.02/EN 5-4 July 2003

U-SGSN Functional Description
UM641 03.02/EN 5-5 July 2003

Wireless Gateway Packet Switched

Interfaces HLR
Ge SCP
Gr
DNS
Server
HP--SIG
HP
SG
U-SGSN Gr’, Ge’ LIG

RNC X1
ATM IP Backbone
CGF
Ga
Iu ATM
AN
Gn Gi
WG for PS
GGSN U-SGSN Configuration 5-6
Wireless Gateway Packet Switched Interfaces

The WG for Packet Switched only is composed of:
• the U-SGSN function (Shelf Type 1)
• the Signaling Gateway function (Shelf Type 6 or Type 2 for PS)
Interfaces are:
implementation, this is the interface between the RNC and the Wireless Gateway. The
Wireless Gateway is a common Iu interface termination point for both the Packet
Switched (PS) and the Circuit Switched (CS) domains. The transport layer of the Iu
interface is based on ATM and supports PVCs connected to the Aggregation Node.
• Gn: the interface between the 3G-SGSN and the GGSN. The transport layer of the Gn
interface is based on Ip over ATM.
• Gp: the interface between the 3G-SGSN in one PLMN and a GGSN in a different PLMN.
In addition, it is the name of the interface between a 3G-SGSN and an SGSN in a
different PLMN, for 3G- 2G-SGSN Hand Over.
Note: Gn and Gp interfaces share the same physical interface.
• Gr: the SS7 interface between the SS7 IP Gateway (SIG) and the Home Location
Register (HLR).
• Ge: the SS7 interface between the SIG and the Signal Connection Control Part (SCCP).
• Gr’/Ge’: the TCP/IP interface between the 3G-SGSN and the SIG. It is a Nortel Networks’
proprietary messaging interface: SCCP Client Interface Protocol.
• Ga: the interface between the 3G-SGSN and the Charging Gateway Function (CGF).
Legal Interception: every physical SGSN is linked by its own interface to a Delivery
Function (DF) of the Lawful Interception architecture. Consequently, interrogation as well
as invocation) independently from all other SGSNs.
The Legal Interception Common Protocol stack is used to provide both the administration
and delivery functions of the packet data legal interception network.
• X1: A set of three (X1.1 - Administration, X1-2 - intercept related information, X1-3
communication content) between a network and a Lawful Intercept Delivery Domain.
UM641 03.02/EN 5-6 July 2003
WG PS Functions : User Plane
WG
Iu Gn
Internet
U-SGSN
GTP Tunneling
GTP Tunneling
RNC
GGSN
U-SGSN
The U-SGSN is built upon the Nortel Networks Passport product. The U-SGSN is a
part of the Wireless Gateway and performs similar functions as the MSC except that
it processes packet data instead of circuit-switched data. The main functions of the
U- SGSN include (for data traffic, User Plane) :
• to send and receive data packets between the mobile stations (through the
RNC) and the GGSN
One of the main roles of the U-SGSN is to perform data packet routing, using IP as
the network layer protocol.
The U-SGSN is able to switch the IP packet from/to an RNC (Iu interface) to/from an
GGSN (Gn interface). This switching is done through GTP-U tunnels. Iu interface
GTP-U tunnel is separated from Gn interface GTP-U tunnel.
UM641 03.02/EN 5-7 July 2003

PS Protocol Layers: User plane

Iu Gn
USD
ATM
GGSN
Application Application
RNC U-SGSN
IP IP
PDCP PDCP GTP-U GTP-U GTP-U GTP-U
UDP/TCP UDP UDP UDP
RLC RLC
IP IP IP IP
MAC MAC
ATM ATM ATM ATM
Physical Physical Physical Physical Physical Physical
User Plane
GTP-U on the Iu interface and Gn interface are the protocols used by the U-SGSN
on the user plane (for data traffic).
The SGSN software for User Plane manages the USD (UMTS Subscriber Data)
component for Iu interface and Gn interface. USD provides the GTP-U
application.
This application run on 4pOC3MM FP cards (physical ports are not used,
processors only).
The transport (IP routing and ATM switching) of the GTP-U traffic is managed by
ATM FP cards (4pOC3SM) that interface with the Aggregation Node.
UM641 03.02/EN 5-8 July 2003

WG PS Functions : Control Plane

M d
Man obility pai
age Pre IN) SCP
men (
HLR t
Ge
Gr
s
Gr’, Ge’ ord
g rec CGF
tin
oun
HP SIG Acc
Ga
Mobility and Session Contexts

U-SGSN
Gn
GTP Tunneling (GTP-C)

s (Start, Stop, Modify)
ord
ce rec
Tra GGSN
R
Re out
so ing
lut
ion DNS
LIG
Control Plane
The main functions of the U-SGSN for Control Plane include:
• to detect new UMTS mobile stations in its service area (Mobility Management)
and to record the location of mobile stations inside its service area (MAP)
• to get the IP address of the GGSN by sending the APN to the DNS server
• to activate a PDP Context to the GGSN (Session Management) by creating a
GTP tunnel (GTP-C) after negotiation of the Quality of Service (RANAP)
• to create accounting records (CDR) and to forward it to the CGF (Charging
Gateway Function)
• to create and send trace records to the LIG server
• to interface to the SCP server for Prepaid services
UM641 03.02/EN 5-9 July 2003

U-SGSN USC
PS Protocol Layers: Control Plane ATM
Iu Gn
Towards the
DNS server
Towards
MAP to the SIG
Towards the
WG GGSN
RNC
SM SM
DNS MAP-
Client GTP-C
GMM GMM Agent
RRC RRC RANAP RANAP TCP/UDP

SCCP SCCP
RLC RLC IP
MTP3-B MTP3-B
MAC SAAL-NNI SAAL-NNI ATM
MAC
ATM ATM Ethernet
Physical Physical Physical Physical
Physical
UMTS Subscriber Control

The UMTS Subscriber Control (USC) consists of those protocols associated with
the subscriber path. The USC communicates signaling information for:
• the Iu interface using SM and MM to the MS,
• the Gn interface using GTP-C,
• the MAP card using MAP-Client and SSF-Client. Then the MAP card creates
the MAP/TCAP and SSF/TCAP messages to the HLR and SCP through the
SIG.
• the DNS using DNS request
Ga and X1 interfaces are used to transfer accounting records to the CGF and trace
records to the LIG.
GMM (GPRS Mobility Management): for the management of MS state,

attach/detach, authentication, Routing Area update, Location Area update, …
SM (Session Management): for the activation of PDP Context (QoS parameters for
example)
GTP-C: to start, stop or modify a PDP Context
MAP-Client: for the Mobility Management (Attach/Detach, subscriber data) to the
HLR through the MAP card and the HP SIG
SSF: for the Prepaid Services to the SCP through the MAP card and the HP SIG
DNS Agent: to get the IP address of the GGSN where is stored the APN of the
subscriber.
UM641 03.02/EN 5-10 July 2003

Which cards for which applications?

AN
Gn, Iu and inter-shelf ATM interface
Subscriber’s Data USD
Subscriber’s signaling USC

U-SGSN
MAP and Gr, Ge interfaces
Charging Gateway Billing SAS

Lawful Intercept (LI)
Applications
The UMTS Subscriber Layer Data (USD) card contains the USD function. This
function consists of the protocols involved in the data path: GTP-U, UDP and IP for
Iu interface and Gn interface. No physical interface is provided by this functions, by
the USD card.
The UMTS Subscriber Control (USC) card contains the USC function. This
function consists of those protocols associated with the subscriber path. The USC
communicates signaling information over the Core Network (GTP-C for Gn interface,
MAP-Client and SSF-Client to the MAP card) and over Iu interface (SM and MM to
the MS through the RNC). USC sends accounting and trace information to the
SAS/LI cards. Ethernet port can be optionally used to interface the DNS.
The MAP card contains the MAP/TCAP and SSF/TCAP applications. MAP card gets
MAP-Client and SSF messages from the USC card and creates the MAP/TCAP
messages through the Gr interface and SSF/TCAP messages through the Ge
interface. Ethernet port can be optionally used to interface the HP-SIG.
The SAS card manages the SAS function and the LI function. SAS function creates
accounting CDR (Call Detail Records) and forwards it to the CGF. LI function
creates trace records and forwards it to the LI server. Ethernet port can be optionally
used to interface the CGF and LI servers.
The ATM card (4pOC3SM) interfaces the Aggregation Node for Iu and Gn
interfaces, and optionally for the DNS interface, HP-SIG interface, CGF interface
and LI server interface.
UM641 03.02/EN 5-11 July 2003

U-SGSN Cards and Applications

RNC
GGSN
CP USD
HLR
SIM GTP-U
I/O USC MAP SAS/LI

GMM/ GTP-C HP-SIG
SM SAS IP Backbone
MAP- TCAP
DNS Client,
Agent SSF LIAF
Data traffic CGF

Signaling traffic
File transfer LIG
DNS Server
U-SGSN Cards and Applications

This slide illustrates the way of data traffic and signaling traffic from/to MS to/from
Core Network elements through U-SGSN cards.
This example illustrates a shelf containing one card per type and represents the
applications in each cards.
UM641 03.02/EN 5-12 July 2003

U-SGSN Provisioning Methodology

A. USD Card Provisioning D. HLRSim Provisioning
a. USD application for Iu interface a. HLRSim application
b. USD application for Gn interface b. Subscriber provisioning
E. SAS Application Provisioning
B. USC Card Provisioning
a. SAS application
a. USC application b. IP/Ethernet to CGF interface
b. DNS Agent Configuration and IP
interface F. LIAF Application Provisioning
C. TCAP Applications Provisioning a. LIAF application
b. IP/Ethernet to LIG interface
a. MAP/TCAP applications
b. MAP-Client G. ATM interface Provisioning
c. SSF Client a. LAPS
d. DNS Agent Configuration and IP b. IP/ATM interface
interface c. IP routing (OSPF)
d. Network Synchronization
U-SGSN Provisioning Methodology

For U-SGSN Provisioning methodology, we can identify 7 steps:
1. USD card provisioning
2. USC card provisioning
3. TCAP Applications provisioning
4. HLRSim provisioning
5. SAS function provisioning
6. LI function provisioning
7. ATM interface provisioning
UM641 03.02/EN 5-13 July 2003

Student notes
UM641 03.02/EN 5-14 July 2003

U-SGSN User Plane :

USD Card Provisioning
UM641 03.02/EN 5-15 July 2003

Packet Switched User Plane :

USD on U-SGSN
U-SGSN
USD
GTP-U GTP-U
(slot 2)
UDP GIPS2 UDP
Iu IP GIPS18 IP Gn
AAL5 AAL5 GTP-U
99
ATM ATM
GTP-U
97
USD Card: UMTS Subscriber Data
USD OC3 Card VR/4 UDP UDP UDP UDP VR/3

2152 3386 3386 2152
(VR for Iu) (VR for Gn)
I/O OC3 Card Gips/2 Gips/18
IP IP
10.60.10.114 47.104.222.203
PP/GIPS2_USD_IU PP/GIPS2_USD_GN
10.60.10.113 10.61.10.113
USD Card Provisioning

USD card provisioning consists of:
• USD Iu interface provisioning:
• Create the Virtual Router for Iu interface (VR/4 in this example)
• One Protocol Port (PP/) on the Virtual Router for Iu interface
• One GIPS for Iu GTP-U traffic (GIPS/2 in this example). The GIPS IP address
belongs to the same subnet than the Virtual Router Protocol Port.
• 2 GTP-U applications: GTP-U Real.99 and GTP-U Real.97
• 2 UDP Ports connecting the GIPS and the GTP-U applications (UDP 2152 and
3386)
• USD Gn interface provisioning:

• Create the Virtual Router for Iu interface (VR/3 in this example)
• One Protocol Port (PP/) on the Virtual Router for Gn interface. This is a private IP
address.
• One GIPS for Iu GTP-U traffic (GIPS/18 in this example). The GIPS IP address is
public and does not belong to the same subnet than the Virtual Router Protocol
Port.
• 2 GTP-U applications: GTP-U Real.99 and GTP-U Real.97 (same than for Iu
interface)
• 2 UDP Ports connecting the GIPS and the GTP-U applications (UDP 2152 and
3386)
UM641 03.02/EN 5-16 July 2003

USD Card Provisioning Methodology (1):

Iu Interface
1. USD Card GIPS and Applications Configuration for Iu

a. Create a Protocol Port on the Virtual Router (IP @ on a private subnet)
b. Provision the GIPS (IP @ on the private subnet) for USD applications
c. Provision the UDP Ports under the GIPS
d. Provision USD: declare the GTPU applications and link them to UDP Ports
2. USD Card GIPS and Applications Configuration for Gn
UM641 03.02/EN 5-17 July 2003

Step 1: USD Configuration: GIPS for Iu

VR/4
UDP 3386
PP/GIPS2_USD_IU U
Gips/2 GTP-U S
IpAddress/
10.60.10.113 10.60.10.114 D
UDP 2152
vr/4 Gips/2 Lp/2 Usd/2
linkToLogicalProcessor lp/2 linkToLogicalProcessor lp/2

linkToProtocolPort maxActiveSessions 15000
PP/GIPS2_USD_IU v r/4 pp/GIPS2_USD_IU
GtpU
IpAddress/
10.60.10.114 utranPortLink
ipPort Gips/2 IP/10.60.10.114 UDP Port/3386,
Gips/2 IP/ 10.60.10.114 UDP Port/2152
Udp
IpLogicalInterface /
10.60.10.113
Port/3386 Port/2152
NetMask 255.255.255.252
linkToApplication linkToApplication
BroadcastAddress 10.60.10.115
Usd/2 gtpU Usd/2 gtpU
Step 1: Iu interface USD Provisioning

For GIPS provisioned in U-SGSN, 3 CIT (Component Instance Tree) have to be provisioned:
• The Virtual Router CIT (VR/4 in this example):
the IP address of the Virtual Router is the first application that is going to use the IP
Server. GIPS needs to have an IP address that is on the same sub-network than the
address of the virtual port of the virtual router (VR/ component). Components to provision
are:
- a virtual port (ProtocolPort/ component), a virtual IP Port (ipPort component)
- its IP address under the IPLogicalInterface/ component with its netmask and
broadcastAddress attributes.
• The GPRS IP Server (GIPS/) CIT (GIPS/2 in this example):
GIPS/ component is a top-level component that represents the host UDP/IP server on
the USD card. GIPS/ component is linked to its IP interface on the virtual router by the
LinkToProtocolPort attribute. Sub-components to provision are:
- The GIPS IP address: IPAddress/ component under the GIPS/ component. This
component represents the Internet Protocol (IP) functionality supported by the
GPRS for a particular address. The IpAddress provides best-effort delivery, inter
network-wide addressing, fragmentation and reassembly, time-to-live control of
datagrams and checksum verification of header contents. Each IpAddress should
be unique among GprsIpServer Instances. In addition, the IP address should not be
the virtual router protocol port logical interface address, the subnet address, or the
subnet broadcast address.
UM641 03.02/EN 5-18 July 2003

Step 1: Iu interface USD Provisioning (continued)

- UDP Port/ components to connect to USD GTP-U applications through the
linkToApplication attribute. (Port/ instances are fixed: 3386 and 2152)
This IP Server must be linked to the Logical Processor (LP/ component) of the
USD card (LP/2 in this example).
• The UMTS Subscriber Data Path Component Instance Tree (CIT):
Top-level component USD/ (USD/2 in this example) represents the data path
layers of the UMTS Subscriber GPRS Support Node (USGSN).
USD/ attributes:
- LinkToLogicalProcessor: This attribute specifies the Logical Processor that
the UmtsSubscriberDataPath (Usd) and its subcomponents are provisioned
on.
- MaxActiveSessions attribute specifies the maximum number of active
session contexts allowed for this instance of USD/. The current number of
active sessions allowed is indicated by the attribute currentActiveSessions
operational attribute.
The sub-component USD/ GTP represents the data traffic part of the GTP
protocol layer.
USD/ GTP attributes:
- utranPortLink attribute specifies the IP Address and the UDP port numbers
that the GPRS Tunneling Protocol User Plane (GTP-U) version 0 and version
1 respectively use to communicate with the UTRAN. The IP Address and
UDP Port are specified by setting this attribute to link to the correct Gips/n
Ip/<ipaddress> Port Udp/<n> component. The standards recommend the
value of the first member of this list (used by GTP Version 0) to be set to
Gips/n Ip/<ipaddress> Port Udp/3386. The standards recommend the
value of the second member of this list (used by GTP Version 1) to be set to
Gips/n Ip/<ipaddress> Port Udp/2152. Changing this value causes the
outstanding transactions to be affected. If this attribute is empty, the IP
address and port specified by the networkPortLink attribute (see later) will be
used for communication with the UTRAN.
- networkPortLink (see later)
To know more about USGSN USD Component Instance Tree, please refer to UMTS
Wireless Gateway Components Reference Manual (NTP 411-8111-060).
UM641 03.02/EN 5-19 July 2003

USD Card Provisioning Methodology (2):

Gn Interface
OK
1. USD Card GIPS and Applications Configuration for Iu
2. USD Card GIPS and Applications Configuration for Gn

b. Provision the GIPS (IP @ on a public GIPS subnet) for USD applications
d. Provision USD: declare the GTPU application and link them to the UDP Ports
e. Create a static route to map the GIPS public IP @ to a private IP @
f. Route the GIPS packets from the public GIPS subnet to the private VR subnet
UM641 03.02/EN 5-20 July 2003

Step 2: USD Configuration: GIPS for Gn

VR/3
UDP 3386
PP/GIPS18_USD_GN Gips/18
U
IpAddress/ GTP-U S
10.61.10.113 47.104.222.203 D
UDP 2152
vr/3 Gips/18 Lp/2 Usd/2
linkToLogicalProcessor lp/2 linkToLogicalProcessor lp/2

linkToProtocolPort maxActiveSessions 15000
PP/GIPS18_USD_GN v r/3 pp/GIPS18_USD_GN
GtpU
IpAddress/
47.104.222.203 networkPortLink
ipPort Gips/18 IP/47.104.222.203 UDP Port/3386,
Gips/18 IP/47.104.222.203 UDP Port/2152
Udp
10.61.10.113
Port/3386 Port/2152
NetMask 255.255.255.252
linkToApplication linkToApplication
Usd/2 gtpU Usd/2 gtpU
Step 2: Gn interface USD Provisioning

For GIPS provisioned in U-SGSN, 3 CIT (Component Instance Tree) have to be
provisioned:
• The Virtual Router Component Instance Tree (CIT) (VR/3 in this example):
This Virtual Router is used for Gn interface only and has to be different from the
Virtual Router used for Iu interface. The IP address of the Virtual Router is the
first application that is going to use the IP Server. Components to provision are:
- a virtual port (ProtocolPort/ component), a virtual IP Port (ipPort
component)
- its IP address under the IPLogicalInterface/ component with its netmask
and broadcastAddress attributes.
• The GPRS IP Server (GIPS/) Component Instance Tree (CIT) (GIPS/18 in this
example):
GIPS/ component is a top-level component that represents the host UDP/IP
server on the USD card. GIPS/ component is linked to its IP interface on the
virtual router by the LinkToProtocolPort attribute. Sub -components to provision
are:
- The GIPS IP address: IPAddress/ component under the GIPS/ component.
This IP address must be a public one.
- UDP Port/ components to connect to USD GTP-U applications through the
linkToApplication attribute. (Port/ instances are fixed: 3386 and 2152)
USD card (LP/2 in this example).
UM641 03.02/EN 5-21 July 2003

Step 2: Gn interface USD Provisioning (continued)

• The UMTS Subscriber Data Path Component Instance Tree (CIT):
USD/ GTP component (see description p.5-19)
USD/ GTP new attributes:
- networkPortLink specifies the IP Address and the UDP port numbers that the
GPRS Tunneling Protocol User Plane (GTP-U) version 0 and version 1
respectively use to communicate with the Gateway GPRS Support Node
(GGSN). The IP Address and UDP Port are specified by setting this attribute to
link to the correct Gips/n Ip/<ipaddress> Udp Port/<n> component. The
standards recommend the value of the first member of this list (used by GTP
Version 0) to be set to Gips/n Ip/<ipaddress> Udp Port/3386. The standards
recommend the value of the second member of this list (used by GTP Version 1)
to be set to Gips /n Ip/<ipaddress> Udp Port/2152. Changing this value causes
the outstanding transactions to be affected. If the utranPortLink attribute is set,
the IP address and port specified by this attribute are only used for GGSN traffic.
Traffic to the UTRAN is routed using the IP address and port specified by
utranPortLink. If the utranPortLink attribute is empty, the IP address and port
specified by this attribute are used to route all GTP-U traffic whether from the
UTRAN or the GGSN.
To know more about USGSN USD Component Instance Tree, please refer to UMTS
UM641 03.02/EN 5-22 July 2003

Step 2: USD for Gn: Routing Public

subnet
VR/3
IpAddress/
PP/GIPS18_USD_GN 47.104.222.203
10.61.10.112/30 Gips/18
10.61.10.113 Private subnet
static route to GIPS public IP @ (47.104.222.203)
go through 10.61.10.114 (Next Hop)
vr/3 Gips/18
linkToProtocolPort
v r/3 pp/GIPS18_USD_GN
PP/GIPS18_USD_GN ip
IpAddress/
47.104.222.203
ipPort static OSPF
asBdrRtrStatus TRUE
IpLogicalInterface / Route/47.104.222.203,255.255.255.255,0 Export/1

10.61.10.113
protocol staticremote
NetMask 255.255.255.252
BroadcastAddress 10.61.10.115 NextHop/10.61.10.114 NetworkList/1
ipAddress 47.104.222.200
ipMask 255.255.255.240 U-SGSN Configuration 5-23
Routing
Core Network GIPS are configured with public IP addresses. In consequence, the
Protocol Port IP address on the Virtual Router needs also to have a public IP
address, because it has to be in the same subnet.
To reduce the number of public IP addresses, it is possible to declare the Protocol
Port IP address on the Virtual Router as a private one. It means that the Protocol Port
IP address on the Virtual Router and the GIPS IP address are in 2 separated
networks.
2 things have to be provisioned to provide this feature:
1. Static route provisioning from GIPS public IP subnet to Protocol Port IP subnet
on the Virtual Router: static routes are required to route packets from the new
public address to the new private IP addresses/subnets.
2. An appropriate export policy must be defined to route the GIPS packets to the
Core Network (i.e. the GGSN). The GIPS network address is the network
address of your public GIPS subnet. OSPF is assumed to be the export policy of
choice and the following provisioning allows the GIPS addresses to be routable.
To know more about Passport IP routing, please refer to Passport Carrier IP (3406)
course (4 days).
UM641 03.02/EN 5-23 July 2003

GIPS public and private subnets

USD USD USD USD USC USC MAP SAS
slot 2 slot 3 slot 4 slot 5 slot 10 slot 11 slot 12 slot 14
Gips/2 Gips/3 Gips/4 Gips/5

10.60.10.114 10.60.10.118 10.60.10.122 10.60.10.126
Gips/18 Gips/19 Gips/20 Gips/21 Gips/10 Gips/11 Gips/12 Gips/14

47.104.222.203 47.104.222.204 47.104.222.205 47.104.222.206 47.104.222.201 47.104.222.202 47.104.222.254 47.104.222.253
public subnet: 47.104.222.200/255

10.60.10.120/30
10.60.10.116/30 10.61.10.120/30 10.60.10.128/30 10.60.222.200/30 10.60.10.160/30

10.61.10.124/30
10.61.10.116/30
10.60.10.112/30 10.60.10.124/30 10.60.10.132/30
10.61.10.112/30
10.60.10.117 10.61.10.12110.61.10.125
10.60.10.161
10.60.10.121 10.61.10.117 10.60.10.129 10.60.222.201
10.60.10.113
10.60.10.125 10.61.10.113 10.60.10.133
VR/3 VR/5 VR/6

VR/4 optional (VR for Gn) (VR for Gr’ and Ge’) (VR for Ga)
(VR for Iu)
to Ethernet Ports to AN to AN (to SIG) to AN (to CGF)
to AN (to RNCs)
(USC card) (to GGSNs) or Ethernet port or Ethernet port
(MAP card) (SAS card)
GIPS public and private subnets

This slides is an example that illustrates a U-SGSN configuration with:
• 4 USD cards (slots 2 to 5; 2 GIPS per card for Iu and Gn interface)
• 2 USC cards (Slots 10 and 11)
• 1 MAP card (slot 12)
• 1 SAS/LI card (slot 14)
UM641 03.02/EN 5-24 July 2003

U-SGSN Control Plane:

USC Card Provisioning
UM641 03.02/EN 5-25 July 2003

Packet Switched Control Plane:

USC on U-SGSN
U-SGSN USC
SM GMM MAP DNS GTP + HlrSim DNSAgent
RANAP Client Agent -C

MAP-
Client
SCCP UDP GIPS10
SG MTP3-B GTP-C
IP
real99
SAAL-NNI Gn
Iu Ethernet AAL5 GTP-C
AAL5 real97
ATM PHYSICAL ATM
UDP UDP
to DNS UDP 3386 2123
VR/3 53
UDP
USC : UMTS Subscriber Control Gips/10 1234
IP
47.104.222.201
10.60.10.121
USC GSP Card
I/O OC-3 Card
USC Card Provisioning

USC card provisioning consists of:
• Create the Virtual Router for signaling to the Core Network (VR/3 in this example)
• One Protocol Port (PP/) on the Virtual Router for Core Network: the address is a
private one (private network)
• One GIPS for USC functions traffic (GIPS/10 in this example). The GIPS IP
address is a public one and does not belong to the same subnet than the Virtual
Router Protocol Port.
• USC functions:
- 2 GTP-C applications: GTP-C Real.99 and GTP-C Real.97
- MAP-Client application to talk with MAP card
- DNS-Agent application to talk with MAP Ethernet or ATM interface
• 4 UDP Ports connecting the GIPS and the applications:
- GTP-C: UDP 2152 and 3386
- MAP-Client: UDP 1234
- DNS-Agent: UDP 53
UM641 03.02/EN 5-26 July 2003

USC card provisioning methodology (1):

GIPS and Applications
1. USC Card GIPS and Applications Configuration
b. Provision the GIPS (IP @ on a public GIPS subnet) for USC applications
d. Provision USC: declare GMM, SM, MAP-Client, HLR Cache and GTP-C
applications and link them to their respective UDP port
e. Create a static route to map the public IP @ to a private IP @
f. Route the GIPS packets from the public GIPS subnet to the private subnet
2. DNS Agent Configuration on USC Card and IP interface to DNS
UM641 03.02/EN 5-27 July 2003

Step 1: USC Provisioning : USC GIPS

MAP-
U Client UDP 1234 VR/3
S UDP 2123
C GTP-C Gips/10 PP/GIPS10_USC
IpAddress/
10.60.10.129
UDP 3386 47.104.222.201
USC/10 Lp/10 GIPS/10 vr/3
linkToLogicalProcessor LP/10 linkToProtocolPort VR/3 PP/GIPS10_USC

linkToLogicalProcessor LP/10
PP/GIPS10_USC
IPAddress/
MapClient GtpC SSF HlrC Ranap 47.104.222.201
maxTransactions 100 ipPort

maxGtpPaths 10 GMM SM UDP
Port/3386 Port/2123 Port/1234 10.60.10.129
linkToApplication linkToApplication linkToApplication NetMask 255.255.255.252
USC/10 GtpC USC/10 GtpC USC/10 MC BroadcastAddress 10.60.10.131
Step 1: USC Provisioning

For GIPS provisioned in U-SGSN, 3 CIT (Component Instance Tree) have to be provisioned:
• The Virtual Router Component Instance Tree (CIT) (VR/3 in this example):
This Virtual Router is used to route signaling traffic to the Core Network. The IP address
of the Virtual Router is the first application that is going to use the IP Server.
Components to provision are:
broadcastAddress attributes. This IP address is a private one (private subnet).
• The GPRS IP Server (GIPS/) Component Instance Tree (CIT) (GIPS/10 in this
example):
GIPS/ component is a top-level component that represents the host UDP/IP server on
the USD card. GIPS/ component is linked to its IP interface on the virtual router by the
- The GIPS IP address: IPAddress/ component under the GIPS/ component. This IP
address must be a public one.
- UDP Port/ components to connect to USC applications through the
linkToApplication attribute. (Port/ instances are fixed: 3386 and 2152 for GTP-U;
1234 for MAP-Client; 53 for DNS-Agent)
This IP Server must be linked to the Logical Processor (LP/ component) of the USC card
(LP/10 in this example).
UM641 03.02/EN 5-28 July 2003

Step 1: USC Provisioning (continued)

• The UMTS Subscriber Control Path CIT:
Top-level component USC/ represents the subscriber control entities such as the GPRS
Mobility Management (GMM), the Session Management (SM), the control part of the
GPRS Tunneling.
USC/ attributes are:
- linkToLogicalProcessor: This attribute specifies the Logical Processor that the
UmtsSubscriberControl (Usc) and its subcomponents are provisioned on.
- sgsnNumber (see later)
- maxAttachedSubscriber: This attribute specifies the maximum attached subscribers
for this instance of UMTS Subscriber Control (Usc). The current attached
subscribers can be obtained from the attribute currentlyAttached defined in the
GprsMobilityManagement (Gmm) component. Changing the value of this attribute
causes all the subscribers using this Usc to be disconnected.
- maxActiveSession: This attribute specifies the maximum simultaneous active
sessions supported in this UMTS Subscriber Control (USC). Changing the value of
this attribute causes all the subscribers using this Usc to be disconnected. Default
value: 1500.
- linkToDnsAgent (see later)
- linkToLisp (see later)
- localPointCode (see later)
USC/ sub-component are:
- USC/ SM: This component represents the Session Management (SM) protocol layer
of the USGSN.
- USC/ GMM: This component represents the GPRS Mobility Management (GMM)
protocol layer of the UMTS Serving GPRS Support Node (USGSN).
- USC/ GTPC: represents the control plane (signalling traffic) of the GPRS Tunnelling
Protocol (GTP) layer used over the Gn and Gp interfaces.
- USC/ MAP -Client: This component represents the MapClient functionality of the
UmtsSubscriberControl (Usc). The MapClient component provides the Mobile
Application Part (MAP) over SS7 to interact with the Home Location Register (HLR)
via the SS7-IP Gateway.
- USC/ SSF: This component represents the Service Switching Function (SSF)
functionality of the USGSN (3G). The Service Switching Function is responsible for
handling communication between the SGSN (2G and 3G) and one or more Service
Control Points (SCP). An SCP is an external entity present in a wireless network
supporting CAMEL (Customized Application for Mobile Network Enhanced Logic). It
provides prepaid services. The SSF maintains the state of the CAMEL dialogues
between the SGSN and the external SCPs with which it communicates.
- USC/ HlrCache: This component represents the Home Location Register (HLR)
Cache functionality. It stores subscription data retrieved from the HLR.
To know more about USGSN USC Component Instance Tree, please refer to UMTS
UM641 03.02/EN 5-29 July 2003

Step 1: USC for Gn: Routing Public

subnet
VR/3
IpAddress/
PP/GIPS10_USC 47.104.222.201
10.60.10.128/30 Gips/10
vr/3 Gips/10
linkToProtocolPort
v r/3 pp/GIPS10_USC
PP/GIPS10_USC ip
IpAddress/
47.104.222.201
ipPort static OSPF
asBdrRtrStatus TRUE

10.60.10.129
NetMask 255.255.255.252
ipAddress 47.104.222.200
ipMask 255.255.255.240
Routing
networks.
1. Static route provisioning from GIPS public IP subnet to Protocol Port IP
subnet on the Virtual Router: static routes are required to route packets from
the new public address to the new private IP addresses/subnets.
address of your public GIPS subnet. OSPF is assumed to be the export policy
of choice and the following provisioning allows the GIPS addresses to be
routable.
To know more about Passport IP routing, please refer to Passport Carrier IP (3406)
course (4 days).
UM641 03.02/EN 5-30 July 2003


DNS Agent and interface to DNS
1. USC Card GIPS and Applications Configuration OK
2. DNS Agent Configuration on USC Card and IP interface to DNS

a. Declare the DNS Agent and link it to the USC card and to its UDP port (53)
on the USC GIPS
b. DNS interface provisioning: provision the Ethernet Port on USC card and
a Protocol Port on the Virtual Router for DNS traffic to the server (optional)
c. Provision the DNS Agent
UM641 03.02/EN 5-31 July 2003

Step 2: DNS Configuration on USC card

Step 2.a: DNS Application to USC GIPS
USC
Step 2.b: DNS Interface to Core Network
USC Step 2.a:
Step 2.c: DNS Agent Provisioning
DNS DNS Application Provisioning
Client
DNS Step 2.c:

Agent
DNS Agent Provisioning
VR/3 UDP 53
PP/gips10_USC
Gips/10
10.60.10.129 IpAddress/
47.104.222.201
PP/DNSIF 47.104.194.80
Step 2.b: (OPTIONAL)

LanApplication/10 DNS Interface Provisioning
Eth100/0
to DNS (PS Core Network)
STEP 2: DNS Configuration

DNS provisioning consists of:
• STEP 2.a: DNS Application Provisioning
• Create DNSAgent application and link it to its UDP Port under the GIPS used for
USC card (GIPS/10 in this example). The UDP Port is 53.
• STEP 2.b: DNS Interface Provisioning

• One Protocol Port (PP/) on the Virtual Router used for Core Network: the address
must be in the same subnet than the HP-SIG or has to be statically routed to the
HP-SIG subnet
• One LanApplication component for Ethernet framing
• One physical Ethernet port
• STEP 2.c: DNS Agent Provisioning

• Create a static route to the GGSN (without asking the DNS)
UM641 03.02/EN 5-32 July 2003

Step 2.a: DNS Application Configuration

VR/3
PP/gips10_USC UDP 53 DNS DNS
U
10.60.10.129 Gips/10 S
Agent Client
IpAddress/ C
47.104.222.201
vr/3 Gips/10 Lp/10 DnsAgent/3,10 Usc/10

linkToLogicalProcessor lp/10 linkToLogicalProcessor lp/10 linkToLogical
linkToProtocolPort v r/3 pp/gips10_USC linkToPort gips/10 Processor lp/10
IpAddress/47.104.222.201
PP/GIPS10_USC Udp Port/53
IpAddress/
47.104.222.201 linkToDnsClient usc/10
serverAddresses 47.104.194.81
ipPort
Udp
MapClient GMM SM
10.60.10.129 Port/53
IP address of the DNS server
NetMask 255.255.255.252
IP Server (GIPS) for DNS : UDP Port 53

STEP 2.a: DNS application provisioning:

• Create the DnsAgent/ component (DNsAgent/3,10 in this example). This
component represents a Domain Name System (DNS) Agent for a particular
Virtual Router (VR). Component instance means:
- first instance: instance of the Virtual Router
- second instance: instance of the USC card
• DnsAgent/ attributes:
the DnsAgent and its subcomponents are provisioned on.
- LinkToPort: This attribute specifies the IP Address and the UDP port number
that the DnsAgent associates with. Changing this value causes the
outstanding transactions to be affected.
- LinkToDnsClient: This attribute specifies the IP Address and the UDP port
number that the DnsAgent associates with. Changing this value causes the
outstanding transactions to be affected.
- serverAddresses: This attribute specifies the IP addresses of the Domain
NameSystem (DNS) Name Server, which this Server queries as necessary. If
this attribute is empty then only static entries are used. The list size is limited
to 4 values (4 IP addresses).
To know more about USGSN DNSAgent Component Instance Tree, please refer to
UMTS Wireless Gateway Components Reference Manual (NTP 411-8111-060).
UM641 03.02/EN 5-33 July 2003

Step 2.b: DNS Interface Provisioning

(OPTIONAL)
LAN
Virtual router application Physical port
(VR)
(Ethernet frames)
Ethernet port
Root (CAS)
VR/3 Lan/10 LP/10
linkToProtocolPort VR/3
ProtocolPort/DNSIF ProtocolPort/DNSIF
Eth100/0
ipPort framer
interfaceName LP/10 Eth100/0
ipLogicalInterface /
47.104.194.80
netmask 255.255.255.128
broadcast 47.104.194.127
STEP 2.b: DNS interface provisioning:

For each Ethernet port (e.g. on a 2pGPDSk card), we need to configure :
• a physical port, that is defined under the LP/ component associated to the
Ethernet card:
- Eth100/ for the 10/100BaseT port of the Ethernet card
• a LAN application that will manage Ethernet frames using an Ethernet port. The
Framer component builds the Ethernet frames,
• an entity that will handle IP packets. That’s the Virtual Router component.
The virtual router has logical ports that are called Protocol Ports. One protocol port
needs to be detailed toward the LAN application.
The Passport can now act as a router. In that case, its role is very simple: it just
receives and forwards IP packets. Then, we need to provision :
- the IP address of the logical port on the virtual router,
- the netmask of the local network and eventually a fixed route toward a LAN
router if any.
Note that we can provision up to 8 IP addresses per Protocol Port but two different
Protocol Ports must have IP addresses that are on two different subnets. Thus, while
provisioning an Ethernet card, be careful about the netmask. One Protocol Port can
be linked to only one LAN application and one Physical Port.
Note: this configuration is optional and can be replaced by an IP/ATM interface

provisioning to the DNS through the Aggregation Node.
UM641 03.02/EN 5-34 July 2003

Step 2.c: DNS Agent Configuration

STATIC ROUTE EXTERNAL DNS server
to GGSN communication
Usgsn DnsAgent/3,10
serverAddresses 47.104.194.81
dnsagent OR
MCC/208
tRetry 5
tRefresh 10080
nRetry 2 ê CacheEntry/static.www.nortel.com
MNC/77
Static/3,10
A CacheEntry component appears
logicalName static.www. nortel.com with the APN + operator Id name
ipAddress 136.147.129.32
LAC/000A
logicalName = APN
RAC/00
ipAddress = GGSN
rncIds 1
STEP 2.c: DNS Agent provisioning:

Static Route to GGSN can be provisioned by creating a Usgsn dnsAgent Static/
component.
USGSN DNSAgent component: This component represents a Logical Name-IP
Address mapping entry for the Serving GPRS Support Node (SGSN) in GPRS. An
instance of this component is provisioned if a static Domain Name System (DNS)
mapping is required.
USGSN DNSAgent attributes:
• logicalName: value must be the APN used by the MS
• ipAddress: value must be the one of the GGSN where the APN is configured.
This attribute specifies the IP addresses corresponding to a given Logical Name.
One Logical Name can have up to ten IP addresses mapped to it. The order of
the addresses is not important; successive queries of the Logical Name return the
IP addresses in a round robin fashion.
UM641 03.02/EN 5-35 July 2003

USGSN Configuration:
Tiered Subscription and Differentiated Services
Usgsn
TieredSubscription DifferentiatedService (DS)

signalingDscpMark de
defaultRoamer 3
AllocationRetention/1 AR/2 AR/3
TrafficClass/conversational TC/streaming TC/interactive TC/background

dataDscpMark de dataDscpMark de dataDscpMark de dataDscpMark de
USGSN Tiered Subscription (TS) component:

This component represents the differentiated tiers of service on the USGSN on a per Packet
Data Protocol (PDP) context basis for downlink traffic. The maximum average bandwidth
associated with each tier is not guaranteed at all times but indicates the upper bound on the
average data rate for the service. If this component is not provisioned, the data rate for every
context will be best effort.
USGSN Tiered Subscription (TS) attributes:
• roamerTier attribute specifies the peak bit rate (tier) that can be assigned to a PDP
context for mobiles that are not in their Home PLMN. Tier 0 through Tier 9 map to peak
throughput classes 0 through 9. Peak throughput class 0 represents the subscribed peak
throughput class for a PDP context. Peak throughput classes 1 through 9 represent peak
bit rates of 8 kbit/s, 16 kbit/s, 32 kbit/s, 64 kbit/s, 128 kbit/s, 256 kbit/s, 512 kbit/s, 1024
kbit/s and 2048 kbit/s respectively. The Tiered Subscription service uses this information
during a PDP context activation for a roamer to determine the maximum average
throughput for the context. If the roamerTier is provisioned as 0, then the peak
throughput for the context is the lower of the peak throughput class of the mobile
requested QoS and the mobile’s subscribed QoS. If the roamerTier is a value between 1
and 9, then the peak throughput class for the context is the peak throughput associated
with that tier.
• averagingWindow (avgWin) attribute specifies the size of the averaging window used to
compute the average bandwidth used by a PDP context. User traffic is policed per
context using the peak throughput rate. In order to police the average peak data rate per
context in the down link direction, Tiered Subscription (TS) monitors the amount of data
passed over a specified period of time, which is defined by the averagingWindow. In
other words, the user data rate is throttled in terms of how many bytes are passed over
the averaging Window time frame. Tiered Subscription (TS) limits the data transfer to the
data rate (bits/s) multiplied by the averagingWindow (s). The larger the
averagingWindow, the more burst size is accommodated.
UM641 03.02/EN 5-36 July 2003

USGSN Differentiated Services (DS) component:

This component represents the differentiated service (QOS) on USGSN that governs the
behavior of packets and contexts that pass through this node. If this component is not
provisioned, the data rate for every context will be best effort.
USGSN Differentiated Services (DS) attributes:
• signalingDscpMark attribute specifies the Differentiated Service (DS) Code Point
(DSCP) value for signalling traffic. It is used for all signaling traffic. The Expedited
Forwarding (EF) Per Hop Behaviors (PHB) can be used to build an assured bandwidth
end-to-end service through DS domains with low loss, low latency and low jitter. Assured
Forwarding (AF) PHB group allows a DS domain to offer different levels of forwarding
assurances for IP packets received. Four AF classes and three drop Precedences are
defined. A DEfault (DE) PHB defined in [DS Field] is the common, best-effort forwarding
behavior available in existing routers as standardized in [RFC1812]. The Class Selector
(CS) PHB and associated code points are used to support legacy (non-DS-compliant)
routers and switches in a DiffServ-compliant network.
• defaultRoamerAr attribute specifies the allocation and retention priority assigned to a
mobile that is a roamer. The actual allocation and retention priority of a roamer will be
limited to the value of this attribute. The roamer's subscribed QOS value will be used if it
does not exceed the value of this attribute; otherwise the attribute value will be used.
USGSN DS AllocationRetention/<allocation retention priority> (AR) component:
This component represents the allocation and retention priority on the USGSN. This
allocation and retention levels are the relative importance compared to other Radio access
bearers for allocation and retention of the Radio access bearer. The most important level has
the value of 1. The allocation is larger and retention is longer for buffers under the most
important level.Values of instance: 1, 2 or 3.
USGSN DS/ AR/ TrafficClass/<trafficclass> component:
This component represents the traffic class on the USGSN. The Traffic Class distinguishes
the delay sensitivity, error rate. The instance value of this component can be one of the
following: Conversational, Background, Interactive, Streaming. Conversational class is
meant for traffic which is very delay sensitive while Background class is the most delay
insensitive traffic class. Interactive class and Background class provide better error rate.
The main difference between Interactive and Background class is that Interactive class is
mainly used by interactive applications while Background class is meant for background
traffic. Background applications use transmission resources only when interactive
applications do not need them. This component provides a mapping from "allocation and
retention priority" and "traffic class" to a DS codepoint.
USGSN DS/ AR/ TrafficClass/ attribute:
dataDscpMark attribute specifies the Differentiated Service Code Point (DSCP) mark for the
data traffic of the corresponding service level (allocation, retention, and traffic class
combination). Values are: de (default value), cs0, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, af11,
af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43.
UM641 03.02/EN 5-37 July 2003

Student notes
UM641 03.02/EN 5-38 July 2003

U-SGSN Control Plane:

TCAP Applications Provisioning
(MAP card and USC card)
UM641 03.02/EN 5-39 July 2003

Gr’ interface
Gr’ Gr
U-SGSN SIG HLR
HLR SIM MAP-C MAP MAP

Relay
HLRC
TCAP TCAP
SCIP SCIP SCCP SCCP
TCP TCP
MTP3 MTP3
IP IP
Ethernet Ethernet MTP2 MTP2
L1 L1 L1 L1
USC card MAP card
Communication to HLR
Communication to HLR can be done by 2 ways:
• to a real external HLR: MAP-Client send its requests to the MAP card which
create the MAP and TCAP message to the HLR through the SIG
• to the HLR Simulator: MAP-Client send directly its messages to the HLR
Simulator
UM641 03.02/EN 5-40 July 2003

MAP Client Configuration and SIG

communication
USC MAP
USC TCAP
MAP-
Client MAP
Step 1:
SS7IPIF
Step 2 and 3: MAP Application
MAP-Client and SSF- Provisioning
Client to TCAP link
UDP 1234 VR/3 TCP 4444
VR/5
PP/GIPS12_MAP
IpAddress/ IpAddress/
Gips/10 10.60.222.201
47.104.222.254
Gips/12
47.104.222.201
PP/GIPS10_USC
10.60.10.129 PP/MAPIF
47.104.194.180
Step 4:
Ethernet
LanApplication/12 Interface
Provisioning
Eth100/0 to SIG
to SIG (PS
Core Network)
MAP Card Provisioning

MAP card provisioning consists of:
• STEP 1: MAP application provisioning:
• Create the Virtual Router for Gr’ and Ge’ interfaces (VR/5 in this example)
• One Protocol Port (PP/) on the Virtual Router used for Core Network for the GIPS
interface: the address is a private one (private network)
• MAP (TCAP) application
• 1 TCP Port connecting the GIPS and the applications:
- TCAP: TCP 4444
• STEP 2: Link MAP-Client to MAP/TCAP application
• STEP 3: Link SSF to MAP/TCAP application
• STEP 4: MAP interface provisioning to the SIG:

must be in the same subnet than the HP-SIG or has to be statically routed to the
HP-SIG subnet
UM641 03.02/EN 5-41 July 2003
MAP card provisioning methodology (1):

GIPS and Applications
1. MAP Card GIPS and MAP/TCAP Applications Configuration
b. Provision the GIPS (IP @ on a public GIPS subnet) for MAP applications
c. Provision the TCP Ports under the GIPS
d. Provision MAP/TCAP: declare TCAP and MAP applications and link them to their
TCP port (4444)
2. Link MAP-Client application (USC card) to MAP/TCAP application (MAP card)
3. Link SSF Client application (USC card) to TCAP application (MAP card)
4. TCP/IP/Ethernet Interface to SIG (optional)
UM641 03.02/EN 5-42 July 2003

Step 1: MAP Application Provisioning

(1.a, b, c, d)
VR/5
PP/GIPS12_MAP TCP 4444 M
Gips/12 MAP A
47.104..222.254
10.60.222.201 IpAddress/ P
vr/5 Gips/12 Lp/12 TCAP/12

linkToLogicalProcessor lp/12 linkToLogical Processor lp/12
linkToProtocolPort v r/5 PP/GIPS12_MAP
PP/GIPS12_MAP
IpAddress/
47.104.222.254
Ss7IpIf MAP
ipPort
linkToPort GIPS/12 IP/47.104.222.201
TCP TCP Port/4444
ss7ipGatewayIpAddress
IpLogicalInterface / 47.104.105.45
10.60.222.201 Port/4444 ss7ipGatewayTcpPort 11005
NetMask 255.255.255.252
IP address of the HP SIG
TCP port on the HP SIG
IP Server (GIPS) for MAP: TCP Port 4444

Step 1: MAP application Provisioning

For GIPS provisioned in U-SGSN, 3 CIT have to be provisioned:
• The Virtual Router CIT (VR/5 in this example):
This Virtual Router is used for Gr’ and Ge’ interfaces only. The IP address of the
Virtual Router is the first application that is going to use the IP Server.
Components to provision are:
component)
broadcastAddress attributes. This IP address is a private one (private
subnet).
• The GPRS IP Server (GIPS/) CIT (GIPS/12 in this example):
server on the MAP card. GIPS/ component is linked to its IP interface on the
are:
- TCP Port/ components to connect to TCAP applications through the
linkToApplication attribute. (Port/ instances is 4444 in this example)
MAP card (LP/12 in this example).
UM641 03.02/EN 5-43 July 2003

Step 1: MAP application Provisioning (continued)
• The TCAP CIT:
Top-level component TCAP/ (TCAP/12 in this example) represents Transaction
Capability Application Part (TCAP) Stack functionality. The TCAP Stack provides
transaction services to applications such as Mobile Application Part (MAP) to the
HLR and Camel Application Part (CAP) to the IN-SCP on the UMTS and GPRS
Serving GPRS Support Node by the LinkToPort attribute to the GIPS/ sub-
components Port/4444.
TCAP/ attributes:
- LinkToLogicalProcessor: This attribute specifies the Logical Processor on
which the Tcap component process will be created.
- maxTransactionsPerSubsystem (maxTransPerSs): This attribute specifies
the maximum number of concurrent TCAP Transactions that are supported
by the TCAP stack for each subsystem receiving service.
- maxInvokesPerSubsystem (maxInvokePerSs): This attribute specifies the
maximum number of concurrent TCAP invokes that are supported by the
TCAP Stack for each subsystem receiving service.
- linkToTcapStackUsers (users): This attribute specifies components that
utilize the services of thisTcapStack component.
TCAP/ SS7IpInterface sub-component: This component represents an interface
to the HP or USP SS7-IP Gateway (SIG). The HP SIG and Universal Signaling
Point (USP) SIG are referred to generically as the SIG. The SIG is a “stateless”
message routing gateway used by many wireless components to communicate
with other SS7 nodes in the wireless network such as the Home Location
Register (HLR) and Visitor Location Register (VLR). A single ins tance of the
Ss7IpIf provides connectivity to the SIG, but an additional instance can be added
for redundancy.
TCAP/ SS7IpInterface attributes:
- linkToPort (lToPort): This attribute specifies a link to a Gips/n Ip/address
Tcp Port/n component. This determines the IP Address and port used by this
component for communication with the SIG.
- ss7IpGatewayAddress (sigIpAddr): This attribute specifies the SS7-IP
Gateway (SIG) IP address. The value must match the IP address specified
on the SIG and must not be set to 0.0.0.0. Changing this value causes the
Ss7IpIf to redirect data using the new IP address. Current transactions being
processed using this interface may be affected.
- ss7IpGatewayTcpPort (sigTcpPort): This attribute specifies the SS7-IP
Gateway (SIG) TCP port number. The value must match the TCP port
number specified on the SIG. Changing this value causes the Ss7IpIf to
redirect data using the new TCP Port number. Current transactions being
processed using this interface may be affected.
To know more about TCAP Component Instance Tree, please refer to UMTS
UM641 03.02/EN 5-44 July 2003

MAP for Gr’ and Ge’: Routing

(1.e and 1.f) Public
subnet
VR/5 IpAddress/
PP/GIPS12_MAP 47.104.222.254
10.60.222.200/30 Gips/12
vr/5 Gips/12
linkToProtocolPort
v r/5 PP/GIPS12_MAP
PP/GIPS12_MAP ip
IpAddress/
47.104.222.254
ipPort static OSPF
asBdrRtrStatus TRUE

10.60.222.201
NetMask 255.255.255.252
ipAddress 47.104.222.200
Routing
networks.
routable.
UM641 03.02/EN 5-45 July 2003

Step 2:
MAP-Client to MAP/TCAP Provisioning
VR/3 VR/5
U UDP TCP M
S MAP- 1234 Gips/10 Gips/12 4444 MAP A
Client
C P
USC/10
Usgsn TCAP/12
localPointCode
maxAccessCode Timers
sgsnNumber e.555555555555 TransactionsType
USC maxAttachedSubscribers 500
maxActiveSessions 1500
mcTimer 15 (sec)
uglRetries 1 MAP Ss7IpIf
saiRetries 1 HlrCache MapClient
AfrRetries 1 Timers Timers
MapFallbackResetTimer 30 (days)
maxRecord 5000 linkToMapStack tcap/12 Map
maxPdpContexts 1500 maxTransactions 30
GMM mapStackInstanceId 12
mscEmulationMode on
simultaneousTransientContext 10 (%) sccpMapCGPARoutInd gt
mapSgsnSubsystemNumber 149
sccpServiceRequestTimer 10 Provisioned only if
HLR SIM is used
sccpVariant itu
hrlSimIpAddress X.X.X.X
hlrSimPort XXXX
Step 2: MAP-Client application and MAP application association

The TCAP CIT (TCAP/12 component in this example) has another sub-component:
the MAP component. It represents the Mobile Application Part (MAP) Stack
functionality. Mobile Application Part (MAP) Stack provides MAP Protocol services for
the MAP client on the USGSN. Its attributes are mostly timers.
MAP component is linked to the USC/ MapClient component Port/4444 by the
LinkToMapStack attribute under the MapClient component.
MAPClient component important attributes:
• sccpMapCGPARoutInd:values can be: gt (globalTitle) or pc (PointCode).
- If gt is selected, the routing to the HLR through the HP-SIG is made by the
Global Title that is provisioned under the USC/ component by the
sgsnNumber attribute.
- If pc is selected, the routing to the HLR through the HP-SIG is made :
• by the Point Code that is provisioned under the USC/ component by the
localPointCode attribute and
• By the SSN that is provisioned under the USC/ MAPClient component
by the mapSgsnSubsystemNumber attribute .
• mapSgsnSubsystemNumber:149 is the value corresponding to the MAP SSN
UM641 03.02/EN 5-46 July 2003

Step 3: SSF Client to TCAP Provisioning

CAMEL PROVISIONING
VR/5
U TCP M
S Gips/12 4444 TCAP A
SSF
C P
Usgsn USC/10 TCAP/12
USC
SSF
tssfTimer 3 (sec)
ssfChargingGuardTimer 3 (sec) linkToTcapStack tcap/12
ssfTcapStackRegistartionTimer 10 (sec)
ssfChargingGuardRetryAttempt 0 maxCamelDialogues 20000
ssfCgpaRoutingIndicator Globaltitle
ssfCapSsn 146
ssfRoamerService enabled
ssfSupportedCamelPhase notsupported
Step 3: SSF application and TCAP application association

USC/10 SSF component is linked to the TCAP/ component through by the
linkToTcapStack attribute. This attribute is a pointer to the TCAP/ component.
Usgsn USC component important attributes for SSF traffic:
• ssfCGPARoutInd:values can be: gt (globalTitle) or pc (PointCode).
- If gt is selected, the routing to the IN SCP through the HP-SIG is made by the
Global Title that is provisioned under the USC/ component by the
sgsnNumber attribute.
- If pc is selected, the routing to the IN SCP through the HP-SIG is made :
• by the Point Code that is provisioned under the USC/ component by the
localPointCode attribute and
• By the SSN that is provisioned under the Usgsn USC component by the
mapSgsnSubsystemNumber attribute .
• ssfCapSgsnSubsystemNumber:146 is the value corresponding to the CAP SSN
UM641 03.02/EN 5-47 July 2003


DNS Agent and interface to DNS
1. MAP Card GIPS and MAP/TCAP Applications Configuration OK
2. Link MAP-Client application (USC card) to MAP/TCAP application OK

(MAP card)
3. Link SSF Client application (USC card) to TCAP application (MAP card) OK
4. TCP/IP/Ethernet Interface to SIG (optional)

a. provision the Ethernet Port on MAP card
b. provision a Protocol Port on the Virtual Router for MAP traffic through the
SIG
c. Provision a static route to the SIG
UM641 03.02/EN 5-48 July 2003

Step 4: MAP Interface to SIG Provisioning

(4.a. and 4.b.)
LAN
Virtual router application Physical port
(VR)
(Ethernet frames)
Ethernet port
Root (CAS)
VR/5 Lan/12 LP/12
linkToProtocolPort VR/5 ProtocolPort/MAPIF

ProtocolPort/MAPIF
Eth100/0
ipPort framer
47.104.194.180
netmask 255.255.255.0
broadcast 47.104.194.255
STEP 4: MAP card Interface to SIG provisioning:

Ethernet card:
router if any.
UM641 03.02/EN 5-49 July 2003

Step 4: IP Static route to SIG provisioning

(4.c.) SIG
VIRTUAL ROUTER NextHop
(default gateway) HLR
(VR/5)
47.0.0.0\8
47.104.194.129
PP/MAPIF 47.104.105.45 SS7 network
47.104.194.180
Core Network
IP backbone
47.104.194.128\25
Vr/5
pp/MAPIF ip
ipPort static
ipLogicalinterface /47.104.194.180 Route/47.0.0.0,255.0.0.0,0
NetMask 255.255.255.128
BroadcastAddress 47.104.194.255 NextHop/47.104194.129
Static Route Definition

Static route definition allows the definition of explicit routes to remote IP networks or
hosts. The definition includes a destination address, address mask, and one or more
next hop addresses (gateways). Multiple static routes may be defined and can be used
in a load sharing mode.
Passport static provisioning also provides a mechanism to statically define routes that
will not receive packets through IP. Static route provisioning allows the operator to
specify that packets addressed to a specified host or route be discarded.
UM641 03.02/EN 5-50 July 2003

HLRSim Provisioning
UM641 03.02/EN 5-51 July 2003

HLRSIM provisioning methodology:
1. Provision HLRSIM
a. Link HLRSIM to USC GIPS
b. Provision HLRSIM in USC MAP-Client application
2. HLRSIM subscriber provisioning

a. Provision authentication
b. Provision PDP Context
UM641 03.02/EN 5-52 July 2003

Step 1:
HLRSIM Provisioning : on USC GIPS
VR/2
PP/GIPS10_USC MAP-C U
Gips/10 S
IpAddress/ Hlrsim GTP-C C
vr/3 Gips/10 Lp/10 hlrsim Usc/10

hlrSimNumber e.12341111
linkToLogicalProcessor lp/10
linkToPort gips/10
linkToProtocolPort v r/3 pp/GIPS10_USC IpAddress/47.104.222.201
PP/GIPS10_USC Udp port/5000 MapClient
hlrsimIpAddress 47.104.222.201
IpAddress/
47.104.222.201 hlrSimPort 5000
ipPort
Udp
10.60.10.129
NetMask 255.255.255.252 Port/1234 Port/5000
HLRSIM communicates with MapClient through UDP Port 5000

HLR Simulator
The HLR Simulator (HLRSIM) is a software tool designed to simulate a GSM HLR on the
SGSN platform. It has a small subscriber database that supports up to 1000 mobile
subscribers and provides the necessary HLR functions that are required for the GPP03
release of the Nortel Networks GPRS platform. The HLRSIM software resides on the Control
Processor card and allows the SGSN to be tested without being connected to a ‘live’ HLR.
When the HLRSIM is active and the SGSN MAP Client (MC) is provisioned with the HLRSIM
IP address and port number, all MAP-Intent messages initiated by the MC are routed through
an internal interface to the HLRSIM instead of sending them to the SIG. The HLRSIM tool
acts like a real HLR and responds to the SGSN MAP service request as described in the
GSM 09.02 specification. The HLRSIM tool uses the GSM MAP defined services to
automatically propagate to the SGSN any GPRS subscription changes of an active
subscriber.
HLRSIM and MAP-C need to communicate through the internal virtual router. We have
already linked MAP-C to an IP Server. We can link the HLRSIM to the same IP Server
because it is possible to link an application which is not on the same FP card than the IP
Server.
Except the GIPS/ branch, we need to provision 2 other branches:
• The Hlrsim top-level component represents the signaling traffic to the HLRSIM (that is
put on the CP card) on the SGSN. It is linked to the Port/ component that is a sub-
component of GIPS/. This port that has the number 5000 allows the access of UDP/IP
packets to the HLRSIM.
• The Virtual Router branch: The IP address of the IP Server is the first application that is
going to use the IP Server. GIPS needs to have an IP address that is on the same sub-
network as the address of the virtual port of the virtual router (VR/ component). For a
virtual port (ProtocolPort/ component), we need to provision the IP address under
IPLogicalInterface / component (sub-component of the VirtualRouter/ component).
GIPS/ component is linked to its IP interface by the LinkToProtocolPort attribute.
UM641 03.02/EN 5-53 July 2003
Step 2: HLRSIM Subscriber Provisioning
hlrsim
hlrsimNumber e.12341234
maxSubscribers 100
subscriber/2087700000000090
MsIsdn e.33699…
ImsiStatus activated
AuthQuint/1 PdpContext/1
ck pdpTypeNumber ipv4
ik pdpAddress 0.0.0.0
rand apnNetworkIdentifier test
autn qosPrecedence normalPriority
xres qosDelayClass 4
qosReliabilityClass 3
qosPeakThroughput 16k
qosMeanThroughput 10k
vplmnAllowed no
….
Attributes and Default Values

All attributes and default values of the HlrSim Subs/ PdpC/ component are detailed:
pdpTypeNumber = ipv4
pdpAddress = 0.0.0.0
apnNetworkIdentifier = apn
qosPrecedence = normalPriority
qosDelayClass =4
qosReliabilityClass = 3
qosPeakThroughput = 16k
qosMeanThroughput = 10k
vplmnAllowed = yes
pdpChargingCharacts = normal
extQosDeliveryOrder = withoutDeliveryOrder
extQosDelivOfErrorSDU = noDetect
extTrafficClass = conversational
extQosMaxSduSize = 500
extQosMaxBitrateUp = 8000
extQosMaxBitrateDown = 8000
extQosResidualBER = 9
extQosSduErrorRatio = 7
extQosTraffHandlPriority = 1
extQosTransferDelay = 4000
extQosGuaranteedBitrateUp = 8000
extQosGuaranteedBitrateDown = 8000
extAllocRetentionPriority = 1
UM641 03.02/EN 5-54 July 2003

U-SGSN Accounting:
SAS Application Provisioning
UM641 03.02/EN 5-55 July 2003

SAS application provisioning

methodology
1. SAS GIPS and SAS Application Configuration
b. Provision the GIPS (IP @ on a public GIPS subnet) for MAP applications
d. Provision SAS: declare SAS application and link it to its UDP port (3386)
g. Provision SAS Parameters
2. UDP/IP Interface to CGF (accounting server)
UM641 03.02/EN 5-56 July 2003

Accounting Traffic Configuration

to CGF SAS
SAS
SAS
Step 1:
VR/6 UDP 3386

PP/GIPS14
IpAddress/ Gips/14
PP/CGFIF
Step 2:
CGF Interface Provisioning
LanApplication/14
Eth100/0
to CGF (PS Core Network)

SAS application provisioning consists of:
• STEP 1: SAS application provisioning:
• Create the Virtual Router for Ga interface (VR/6 in this example)
• One Protocol Port (PP/) on the Virtual Router used for Core Network for the GIPS
interface: the address is a private one (private network)
• SAS application
• 1 UDP Port connecting the GIPS and the application:
- SAS: UDP 3386
• STEP 2: SAS interface provisioning to the CGF:

must be in the same subnet than the CGF or has to be statically routed to the
CGF subnet
UM641 03.02/EN 5-57 July 2003

Step 1: SAS Application Provisioning

VR/6
PP/GIPS14 UDP 3386 S
Gips/14 SAS A
IpAddress/ S
vr/6 Gips/14 Lp/14 SAS/1

linkToLogicalProcessor lp/14 linkToLogical
Processor lp/14
linkToProtocolPort v r/6 pp/gips14
linkToPort GIPS/14
PP/GIPS14 IP/47.104.222.253 UDP
IpAddress/ Port/3386
47.104.222.253
ipport
UDP
10.60.10.161 Port/3386
netMask 255.255.255.252
IP Server (GIPS) for Accounting : UDP Port 3386
Step 1: SAS application Provisioning

For GIPS provisioned in U-SGSN, 3 branches have to be provisioned:
• The Virtual Router branch (VR/6 in this example):
This Virtual Router is used for Ga interface only. The IP address of the Virtual Router is
the first application that is going to use the IP Server. Components to provision are:
broadcastAddress attributes. This IP address is a private one (private subnet).
• The GPRS IP Server (GIPS/) branch (GIPS/14 in this example):
GIPS/ component is a top-level component that represents the host UDP/IP server on the
MAP card. GIPS/ component is linked to its IP interface on the virtual router by the
- The GIPS IP address: IPAddress/ component under the GIPS/ component. This IP
address must be a public one.
- UDP Port/ components to connect to SAS applications through the
This IP Server must be linked to the Logical Processor (LP/ component) of the SAS card
(LP/14 in this example).
• The SAS branch:
Top-level component SAS/ top-level component (SAS/14 in this example) represents the
SAS traffic on U-SGSN to the CGF. It is linked:
- by the LinkToPort attribute to the GIPS/ sub-components Port/3386.
UM641 03.02/EN 5-58 July 2003

Step 1: SAS Routing

(1.e and 1.f) Public
subnet
VR/6 IpAddress/
PP/GIPS14 47.104.222.253
10.60.10.160/30 Gips/14
vr/6 Gips/14
linkToProtocolPort
v r/6 PP/GIPS14
PP/GIPS14 ip
IpAddress/
47.104.222.253
ipPort static OSPF
asBdrRtrStatus TRUE

10.60.10.161
NetMask 255.255.255.252
ipAddress 47.104.222.200
Routing
networks.
routable.
UM641 03.02/EN 5-59 July 2003

Step 1.g: Accounting parameters

Root (CAS)
Usgsn
Accounting
cdrCapture sgsn mobility
locationBasedBilling disabled
transferInterval 30 (min)
updateInterval 60 (min)
scdrPartialRecordInterval noPartialRecords
mcdrPartialRecordInterval noPartialRecords
mcdrMaxContainers 5
echoRequestInterval 5
primaryCgfIpAddress 47.162.77.132
secundaryCgfIpAddress 0.0.0.0
cdrTransferTime 5
cdrRetries 1
primaryCgfAsn1Encoding ber
secundaryCgfAsn1Encoding ber
timeOffset 0
genAuditFiles disabled
auditFileLife 5
roamerCapture all U-SGSN Configuration 5-60
USGSN Accounting CIT

To know more about USGSN Accounting Component Instance Tree, please refer to
UMTS Wireless Gateway Components Reference Manual (NTP 411-8111-060).
UM641 03.02/EN 5-60 July 2003


SAS interface to CGF
1. SAS GIPS and SAS Application Configuration OK
2. UDP/IP Interface to CGF (accounting server)

a. provision the Ethernet Port on SAS card
b. provision a Protocol Port on the Virtual Router for SAS traffic to the CGF
c. Provision a static route to the CGF
UM641 03.02/EN 5-61 July 2003

Step 2: SAS Interface Provisioning to CGF

LAN
Virtual router
(VR) application Physical port
(Ethernet frames)
Ethernet port
Root (CAS)
VR/6 Lan/14 LP/14
linkToProtocolPort VR/6
ProtocolPort/CGFIF ProtocolPort/CGFIF
Eth100/0
ipPort framer
47.162.77.121
netmask 255.255.255.0
broadcast 47.162.77.255
STEP 2: SAS interface provisioning to the CGF:

Ethernet card:
router if any.
UM641 03.02/EN 5-62 July 2003

U-SGSN Lawful Intercept:

LIAF Application Provisioning
UM641 03.02/EN 5-63 July 2003

LI Function provisioning methodology
1. LIAF Application Configuration

a. Provision LIAF: declare LIAF application
b. Link the LIAF to the GIPS of the SAS card
c. link the LIAF to the USC LI Client
2. TCP/IP Interface to LIG
UM641 03.02/EN 5-64 July 2003

Step 1: LI Application Provisioning

VR/6
PP/GIPS14 TCP 3333 S U
Gips/14 S LI
SAS A Client
IpAddress/ S C
vr/6 Gips/14 Lp/14 LIAF/1 USC/10

Processor lp/14
linkToProtocolPort v r/6 pp/gips14
linkToPort GIPS/14
PP/GIPS14 IP/47.104.222.253 TCP
IpAddress/ Port/3333
47.104.222.253
linkToLiClient USC/10
ipPort admfAddress 10.60.10.190

admfPort 11060
TCP
10.60.10.161 Port/3333 LIAF : Lawful Intercept Access Function
netMask 255.255.255.252
(SGSN)
ADMF : Admin Function
Step 1: LI application Provisioning

For GIPS provisioned in U-SGSN, 3 branches have to be provisioned:
• The Virtual Router branch (VR/6 in this example):
This Virtual Router is used for Ga interface only. The IP address of the Virtual
Router is the first application that is going to use the IP Server. Components to
provision are:
component)
broadcastAddress attributes. This IP address is a private one (private
subnet).
• The GPRS IP Server (GIPS/) branch (GIPS/14 in this example):
server on the MAP card. GIPS/ component is linked to its IP interface on the
are:
- TCP Port/ components to connect to LI application through the
This IP Server must be linked to the Logical Processor (LP/ component) of the LI
card (LP/14 in this example).
UM641 03.02/EN 5-65 July 2003

Step 1: LIAF application Provisioning (continued)

• The LIAF CIT:
Top-level component LIAF/ (LIAF/1 in this example):
This component represents the Lawful Intercept Access function. Legal
Intercept is used by law enforcement agencies to monitor the activities of a
subscriber on the network based on the IMSI or the MSISDN.
LIAF/ attributes:
the LawfulInterceptAccessFunction (Liaf) is provisioned on.
- LinkToPort This attribute specifies the IP address and the TCP port number
of the Legal Intercept Access Function. In this example, it is linked to the
GIPS/ sub-components Port/3333. The IP Address and TCP Port are
specified by setting this attribute to link to the correct Gips IpAddress Port
Tcp component. A minimum of two IP addresses must be assigned.
Changing this value causes the outstanding transactions to be affected. Gips
component must be provisioned on the same card. LinkToLiClient This
attribute specifies links to the UMTS/GPRS subscriber control entities that
are handled by this Legal Intercept Access Function. This attribute must be
set to Usc/ instance, based on whether it is used in UMTS or GPRS.
Changing this value causes the outstanding transactions to be affected.
- AdmfAddress : This attribute specifies the IP address of the 3rd part Lawful
Intercept Access Function (LIAF) Gateway Administrative Function (ADMF).
The ADMF provides a list of target subscribers to be monitored to the Legal
Intercept Access function. Changing this value causes the outsta nding
transactions to be affected.
- AdmfPort: This attribute specifies the IP port number of the Lawful Intercept
Access Function (LIAF) Gateway Administrative Function (ADMF). The
ADMF provides a list of target subscribers to be monitored to the Legal
Intercept Access function.
UM641 03.02/EN 5-66 July 2003

ATM Interface to AN: I/O card provisioning
UM641 03.02/EN 5-67 July 2003

WG GIPS configuration: U-SGSN

AN
RNC Iu 172.253.3.3 33.33.33.41
VR/4 VR/3 Gn IP/ATM
IP/ATM
10.60.10.226 10.60.10.222
VR/5
IP/ATM
10.60.10.230 (optional )
VR/6
10.60.10.234
136.147.129.19
CP
VR/0 Inter -shelf
C
Inter -shelf Inter -shelf Inter -shelf
o
10.60.10.232/30 10.60.10.228/30 10.60.10.224/30 10.60.10.220/30 r
OAM LAN e
IP/ATM IP/ATM
136.147.129.128/20 (optional ) (optional ) IP/ATM IP/ATM
N
CP Inter -shelf Inter -shelf Inter -shelf Inter -shelf U-SGSN
136.147.129.18 VR/0 e
10.60.10.233 10.60.10.225 10.60.10.221
10.60.10.229 t
47.104.194.80 w
VR/6 VR/5 VR/4 VR/3
47.104.194.180 o
r
10.60.10.161/30 10.60.222.200/30 10.60.222.200/30 10.60.11.112/30 10.60.10.128/30
k
GIPS SAS/LI GIPS MAP GIPS USD_Iu GIPS USD_Gn GIPS USC IP/ETH
SAS/LI TCAP USD USD USC

IP/ETH
SAS/LI card (slot 14) MAP card (slot 12) USD card (slot 2) USC card
U-SGSN (slot 10)
Configuration 5-68
GIPS Provisioning
This illustrates an example of GIPS provisioning in a U-SGSN and Virtual Router
provisioning in Aggregation Node and U-SGSN.
GIPS provisioning: 5 GIPS in 4 cards:
• GIPS USC in a USC card
• GIPS USD_Iu in a USD card
• GIPS USD_Gn in the same USD card
• GIPS MAP in a MAP card
• GIPS SAS/LI in a SAS/LI card
Virtual Router provisioning (in AN and U-SGSN):

• VR/3 for Gn interface
• VR/4 for Iu interface
• VR/5 for Gr/Ge interface (optional, if IP/ATM routing through AN)
• VR/6 for Ga/X1 interface (optional, if IP/ATM routing through AN)
Note: VR/2 can be added also for DNS Agent routing to DNS Server.
VR/1 can also be added if SAAL-NNI application is configured on the shelf (in the
I/O ATM card)
VR/0 is used in each WG shelves for OAM traffic.
UM641 03.02/EN 5-68 July 2003

I/O card provisioning methodology

1. Optical Ports and APS Provisioning
a. Create SDH/ Optical Ports under each I/O card Logical Processor
b. Create a LAPS/ and link it to its working and its protected optical ports
2. ATM Interface and VCC Provisioning

a. Create an ATMIF/ for each working optical port
b. Create the VCC/ to AN under the ATMIF/
c. Activate PNNI and declare the ATM prefix and ESI addresses (NSAP addresses)
3. IP/ATM Provisioning
a. Create an PP/ and its IP address for each Ip interface on the Virtual router (VR)
b. Create an ATMMPE/ (RFC 1483) and link it to its PP/ (IP) and its VCC (ATM)
c. Activate OSPF on all IP interfaces and on the Virtual Router (VR) also
I/O Card Provisioning

Provisioning of I/O card consists of provisioning components for 3 protocol layers:
1. Optical Ports and APS
2. ATM Interface and VCC
3. IP Provisioning
UM641 03.02/EN 5-69 July 2003

Physical (Optical) Ports Provisioning:

Automatic Protection Switching (APS)
I/O (slot 8) I/O (slot 9)
SDH/0 SDH/0
SDH/1 SDH/1
SDH/2 SDH/2
SDH/3 SDH/3
LP/8 LAPS/80 LP/9 AtmIf/80
clockingSource module workingLine LP/8 Sdh/0 clockingSource module

protectionLine LP/9 Sdh/0
Sdh/0 Sdh/0
LineAutomaticProtectionSwitching LAPS/80 LineAutomaticProtectionSwitching LAPS/80
Vc4/0
Vc4/0 applicationFramerName ATMIF/80 Vc4/0
Optical Ports and APS Configuration

Configuration of Optical Ports consists of:
• declaration of physical ports under the LP/ of the card: SDH/ component
• declaration of a VC4 optical frame under the SDH/ component: VC4/ component
Configuration of APS (Automatic Protection Switching) consists of:

• declaration of physical ports under the LP/ of 2 optical cards
• declaration of the LAPS/ component which is linked to 2 SDH/ components
under 2 different LP/
• The link between the Layer 1 and Layer 2 is mad by the
applicationFramerName attribute under the LAPS/ VC4/ component.
UM641 03.02/EN 5-70 July 2003

IP/ATM interface to AN:

example of VR/3 interface
Layer 3 Layer 2 Layer 1

AtmMultiProtocol
Encapsulation
Virtual router ATM Physical port
(RFC 1483)
(IP packets) (Virtual Channels)
Sdh port
VR/3 AtmMpe /802 AtmIf/80 LAPS/80
interfaceName LAPS/8 Vc4/0 workingLine LP/8 Sdh/0

linkToProtocolPort
ProtocolPort/ATMMPE802 VR/2 PP/ATMMPE802 protectionLine LP/9 Sdh/0
Vcc/0.40
ipPort AtmConnection/82 Vc4/0
atmConnection
Nep
ipLogicalInterface /10.60.10.221 AtmIf /80 Vcc/0.40 Nep
netMask 255.255.255.252
broadcastAddress 10.60.10.223
IP/ATM Interface Provisioning

An IP/ATM interface provisioning consists of provisioning:
• IP layer (layer 3): one ProtocolPort/ component and its IP address
(IpLogicalInterfacecomponent/)
• ATMMPE layer (layer 2.5): one ATMMPE/ component that will be able to
encapsulate the IP packet. Its subcomponent (ATmConnection/) permits to put
the IP packet into one or many Vcc (atmConnection attribute that is pointer to a
VCC/ Nep component).
• ATM layer (layer 2): one VCC/ component terminated by a NEP
ATMMPE component: it represents a logical interface between the virtual router and
an ATM media (ATMif). Multiprotocol encapsulation as specified in RFC 1483 is used
to transfer higher-layer protocol data across virtual channels in an ATM network. The
AtmMpe component provides a means to associate multiple ATM virtual channel
connections with a single ProtocolPort through a linkage attribute abd with virtuak
channel connections through a linkage attribute in each AtmConnection
subcomponent.
Encap Type: this attribute specifies the RFC 1483 encapsulation type to be used for
the AtmConnection component under this AtmMpe component. Specifying llcEncap
allows multiplexing of multiple protocols over the VCCs. The protocol of the carried
PDU will be identified by an IEEE 802.2 LLC heade. If bridging or inverrsse ARP is to
be carried over a VCC, llcEncap must be used. Specifying ipVcEncap or ipxVcEncap
indicates that all the VCCs (that is, AtmConnection components) under an AtmMpe
component use VC-based multiplexing and carry IP PDUs only.
UM641 03.02/EN 5-71 July 2003

IP routing
OSPF for Gn (VR/3)
VR/3
IP
ProtocolPort/ATMMPE802
OSPF
ipPort
Area/1.1.1.1 Export/1 ipLogicalInterface /10.60.10.221
OSPFInterface
areaId 1.1.1.1
Create an OSPFInterface component

under every OSPF IP interface
OSPF Routing
OSPF routing is declared by:
• provisioning an OSPF component under the VR/ IP component
• provisioning an OSPFIF component under each Virtual Router Protocol Port
interface
UM641 03.02/EN 5-72 July 2003

Network synchronization
LP/8 NS (Network Synchronization) LP/9

primaryReference lp/8 SDH/0
secundaryReference lp/9 SDH/3
SDH/0 SDH/3
tertiaryReference
clockingSource module clockingSource module
UM641 03.02/EN 5-73 July 2003

Student notes
UM641 03.02/EN 5-74 July 2003

Wireless Media Gateway Configuration
Section 6
UM641 03.02/EN 6-1 July, 2003

Objectives
• Describe the WG Circuit Switched functions and applications

• Draw the ways of communication in WG for Circuit Switched
• Describe and draw the WMG CAS components
• Configure a Shelf Type 4 or Shelf Type 5 for WMG
Wireless Media Gateway Configuration 6-2
UM641 03.02/EN 6-2 July, 2003

Contents
Wireless Media Gateway Description
Wireless Media Gateway Provisioning
UM641 03.02/EN 6-3 July, 2003

Student notes
UM641 03.02/EN 6-4 July, 2003

Wireless Media Gateway Description
UM641 03.02/EN 6-5 July, 2003

WG CS Interfaces
SG
Shelf Type 2, 4 or 6
RNC
ATM
Iu cs’
WMG mux
Shelf Type 4 or 5
MSC
Iu
AN
WG for CS
Wireless Media Gateway

WMGs are an optional component of the WG and is required only if the Circuit
Domain is being supported.
A WMG is a collection of Media Gateways (MGs) which can be spread across at least
2 shelves (Shelf Type 4 or Type 5).
The main functions of the WMG :
• for User Plane:
• it provides Transcoding and Rate Adaptation Units (TRAU) for the Core
Network Circuit Domain to each Signaling Gateway function: since each SG
supports a single RNC, each WMG is associated with an RNC. WMG translates
TDM packet (Iu cs’) to ATM (Iu).
• it provides Echo Cancellation functionality for the Core Network Circuit Domain.
• it provides Circuit Data Services.
• for Control Plane:
• forward RANAP signaling into MTP2 in TDM DS0 to the MSC.
• control the AAL-2 circuit establishment for CS UP traffic, allocate (through
ASPEN) the CS UP resource on TDM and map the AAL-2 resource to the TDM
resource.
UM641 03.02/EN 6-6 July, 2003

WG CS User Plane
WMG
AMR A-law PCM
AAL2
Iu Iu cs’
ATM E1/DS0
Physical
4pOC3SM VSP
(WMG & AN) 32pE1TDM
Circuit Switched User Plane

Circuit Switched User Plane in Wireless Gateway consists of:
• the TRAU (Transcoder and Rate Adapter Unit) function:
• transcoding and adapting the rate of voice form/to A-law PCM (over TDM E1
DsO) to/from AMR rates (range from 4.75 kbps to 12.2 kbps over ATM AAL-2)
• adapt Circuit Switched Data from/to TDM E1 DsO to/from ATM AAL-2 at 14.4
kbps or 64 kbps.
VSP card provides this TRAU function, but is also able to provide:
• Echo Cancellation
• Tandem Free Operation
• Voice Quality Enhancement features
• Iu User Plane (IuUP) protocol Termination
UM641 03.02/EN 6-7 July, 2003

WG CS Control Plane
RANAP
ALCAP
RANAP-CS Q.2630.1 RANAP-CS
SCCP Q.2150.1 SCCP

ASPEN
MTP3-B
MTP3
SAAL-NNI
Iu Iu cs’
AAL5 ASPEN MTP2
ATM E1/DS0
SG OC3 card
VSP WMG
SG
(Shelf I/O OC3 Card (Shelf
32pE1TDM
Type 6) (SG & AN) Type 5)
Circuit Switched Control Plane

Circuit Switched Control Plane in Wireless Gateway consists of:
• forward RANAP to/from RNC from/to MSC: in this case the WG will just relay
RANAP between RNC and MSC. RANAP is received/sent from/to the RNC over
a MTP-3b linkset over an AAL-5 Vcc and is forwarded to/from the MSC into an
MTP3 linkset over MPT2 over MTP1. The role of the WMG is just to
receive/sent the MTP-2 information from/to the Signaling Gateway in order to
sent/receive it to/from the MSC in an signaling Ds0 channel.
• receive ALCAP from the RNC, control the AAL-2 circuit establishment for CS
UP traffic, allocate (through ASPEN) the CS UP resource on TDM and map the
AAL-2 resource to the TDM resource. The role of WMG in this case
corresponds to the tasks of ASPEN.
UM641 03.02/EN 6-8 July, 2003

Which cards for which applications?
SG
Signaling Gateway SG
AN Iu and inter-shelf ATM interface
Voice Service Processor VSP

WMG
Iu cs’ TDM interface to MSC
Wireless Gateway and Wireless Media Gateway

Wireless Gateway for Circuit Switched is managed by 2 main functions:
• Signaling Gateway (see section 7) for the control plane only
• Wireless Media Gateway for the user plane and a part of the control plane (for
Iu cs’ interface)
Wireless Media Gateway resides in Shelves Type 4 or Type 5 and is composed of:
• ATM cards for ATM interface to the Aggregation Node
• VSP cards for the TRAU function
• TDM cards for the TDM interface to the MSC
UM641 03.02/EN 6-9 July, 2003

voice over ATM: Timeslot mapping
DS3/E1
ATM TDM P
network S
T
N
AAL2 VCC
RNC WMG
DS1/E1 timeslots
Timeslot mapping by means of
channels within an AAL2 VCC
CID 8 CID 9 CID 31
AAL2 packets
Timeslot Mapping
WMG dynamically creates media (voice and voiceband data) connections between
the ATM network and the TDM network. The mapping between ATM VCCs/CIDs
and TDM timeslots is not static. The incoming calls (into an ATM VCC/CID on Iu
interface) are effectively switched to an appropriate TDM outgoing.
As shown in the slide, all bearer traffic travels over the ATM network in AAL2
VCCs. ATM trunks can be implemented using ATM PVCs for the moment, or SVCs,
endpoint-provisioned SVCs, or SPVCs in the future release. Whenever a bearer
traffic connection is to be made in the WG, the Signaling Gatewa y sends a “create
connection” ASPEN message with the appropriate parameters to the WMG. In the
WMG, the VSP FP acts upon instructions from its Signaling Gatewa y application
(the one that manages the RNC) to make or break narrowband connections
between TDM trunks and AAL2 trunks.
Control traffic travels over an IP network. Each VSP on the WMG interconnects
with the IP network to the Signaling Gateway using a single AAL5 VCC. This VCC
carries IP datagrams using RFC 1483 encapsulation and terminates on the
Signaling Gateway.
UM641 03.02/EN 6-10 July, 2003

voice over ATM: Trunking using AAL2
AAL2 CID
ATM
ts
ts 11 ts
ts 22 ts
ts 33 Ts
Ts 30
30 Ts
Ts 31
31 AAL2 CID VCC
E1 stream (voice)
AAL2 CID
ATM
Signaling MTP2 TS is VCC
transported by another VCC (signaling)
Trunking using AAL2

In the Wireless Gateway, narrowband signaling is not terminated; instead it is
“snooped” and transported transparently. Each service interface timeslot is statically
mapped to a particular CID within a particular ATM VCC. When there is no call
present in a timeslot, the corresponding VCC/CID will not be used by another
narrowband call using another timeslot.
Within this mode of operation, narrowband services are transported over AAL2 and
AAL5 PVCs. AAL2 PVCs carry voice traffic and inband signaling information. AAL5
PVCs carry out-of-band signaling information.
MTP2 signaling at TDM interface (Iu cs ‘) transports the RANAP signaling coming
from the RNC (AAL-5 Vcc).
UM641 03.02/EN 6-11 July, 2003

PVC call setup
• RNC and VSP need to know the following information:

– identity of remote peer (in format of NSAP address)
– VCCI for each individual VCC
– CID for each individual AAL2 channel
– voice profile
PVC Call Setup

Each PVC between the RNC and a VSP is labeled with an identifier, which is
identical at both ends of the connection. This identifier is referred to as the VCCI and
is used in the process of establishing calls. So that the terminating VSP can connect
its TDM endpoint to the CID in the VCC chosen by the RNC for the call initiated by
the mobile, communication between the RNC and the VSP is required. The RNC
and the VSP need to know the following information:
• the identity of its remote peer (formatted as an NSAP address)
• the VCCI for each individual VCC connecting the RNC with the VSP
• the CID for each of the individual AAL2 channels
• the voice profile
The way in which this communication between the RNC and the VSP is achieved is
through the exchange of session descriptors. When a call is to be set up, the RNC
produces a session descriptor with its ATM NSAP address specified, but with the
VCCI and CID left blank. It also sets the voice profile to a list of the profiles that it
supports. This session descriptor is delivered through the controller to the
terminating VSP. The terminating VSP selects an available VCCI a nd CID and an
appropriate voice profile, includes its own ATM NSAP address, and returns the
session descriptor via the Signaling Gateway. At this point, an AAL2 VCC is
established between the RNC and the VSP.
UM641 03.02/EN 6-12 July, 2003

WMG and VSP Detailed Functions

MTP3 ASPEN MTP2
UDP 12004 UDP 12001 64 Kbit/s
I/O VSP 32pE1AAL

SPM
VxWorks kernel IP stack
RFC
1483
driver
ASPEN MTP2
AtmIf/
ATM
signaling
VCC/ NAP T E1/DS0
D
Voice ATM M
VCC/
NAP PCM frame
VPM
Dispatch
TRAU
DSP
AMR compressed voice on AAL -2 A-law

AMR is converted to TDM 64 Kb/s A-law voice 64 Kbit/s
WMG and VSP

WMG is able to manage the CS UP and CP.
The CS User plane:
• TDM interface: PCM A-law voice (64 kbps) is carried in E1 links
• VSP card: TRAU function: VPM (Voice Processing Module) processors are able
to transcode PCM voice in AMR and to adapt the rate to a range between 4.75
kbps to 12.2 kbps. One VSP card can manage up to 480 Ds0 to/from one MSC
from/to several RNC.
• ATM card: AMR voice is carried to/from the AN through ATM AAL-5 Vcc.
The CS Control Plane:
• TDM interface: RANAP signaling is carried over MTP2/MTP1 in an E1 link
• VSP card: SPM (Signaling Processing Module) processors :
- are able to extract the MTP2 signaling from the E1 and to forward it to the
Atm card.
- Manage ASPEN messages with the Signaling Gateway for call setup
establishment
- Dispatch Ds0 carrying voice in the different VPM
• ATM card: MTP2 signaling and ASPEN signaling are carried to/from the AN
through ATM AAL-5 Vcc (different from UP Vcc).
UM641 03.02/EN 6-13 July, 2003

CS Cards and Applications

CP SG I/O SG
MTP3
VMG
Voice/Data traffic
SAAL-
NNI
Signaling traffic
MTP3 -B
(RANAP)
RNC
Signaling traffic
CP I/O I/O AN (ALCAP/ASPEN)
CP I/O VSP 32pE1
SPM
VPM MSC
WMG
CS Cards and Applications

The Signaling Gateway function passes the Control Plane messages from the RNC to
the U-SGSN for RANAP-PS (PS CP) and/or to the Wireless Media Gateway for
RANAP-CS (CS CP) for processing. It supports on the Iu interface the MTP3b,
SCCP, RANAP protocols.
On the Iu cs’ interface, to communicate with the MSC, the Signaling Gateway (and
Virtual Media Gateways) use the protocols (MTP2 and ASPEN) implemented on the
Wireless Media Gateway (VSP card) that forward the RANAP-CS message to the
MSC.
For Packet Switched, the RANAP-PS message terminates at the Signaling Gateway:
GMM and SM are forwarded to the USC on the U-SGSN.
UM641 03.02/EN 6-14 July, 2003

WG ATM and IP configuration for CS

AtmIf/20
AN
Vcc/0.46 (CS CP)
RNC
Vcc/0.105 (CS UP)
Vcc Vcc
(voice) VR/1 (CS CP)
10.60.11.14
Vcc/3.120 10.0.180.1
AtmIf/80 (CS UP)
Vcc/2.160 AtmIf/41 AtmIf/41

(CS CP: MTP2
+ ASPEN) Vcc/1.400 Vcc/1.200 (CS CP:
VSP (CS CP: MTP2 ALCAP + RANAP)
10.0.180.240 + ASPEN)
AtmIf/80
10.60.11.13
WMG VR/1
10.60.11.32/30
GIPS 2 GIPS 8
SG SAAL-NNI SG
ATM Switching and IP Routing

This example of ATM and IP configuration illustrates the ATM switching and IP
routing between shelves in WG for Circuit Switched.
• for Circuit Switched Control Plane:
• ATM switching: RNC communicates to SG (Shelf Type 6) through the AN
(VCC/1.200 for CS CP between AN and SG in this example)
• IP routing: SG (Shelf Type 6) communicates to WMG (Shelf Type 5) through
AN and VR/1 (VCC/1.400 between SG and AN; VCC/2.160 between AN and
WMG)
• for Circuit Switched User Plane:
• ATM switching: RNC communicates to WMG (Shelf Type 5) through the AN
(VCC/0.105 between AN and RNC in this example; VCC/3.120 between WMG
and AN)
UM641 03.02/EN 6-15 July, 2003

Student notes
UM641 03.02/EN 6-16 July, 2003

Wireless Media Gateway Provisioning
UM641 03.02/EN 6-17 July, 2003

PVG provisioning methodology (1/2)
1. TDM interface to Narrowband switch (32pE1TDM card)

- Physical E1 ports and channels
2. Media Gateway (VSP card)

a. Processing Module (PM) declaration: VPM and SPM
b. TRAU function: AmrBrag or CsdBrag (E1 to VPM association for voice traffic)
c. MTP2 Signaling: association to UDP ports
d. ASPEN Signaling: association to UDP ports
3. Voice Parameters
4. ATM interface (ATM card)
PVG Provisioning
We can identify 4 steps:
1. TDM interface
2. Media Gateway
3. Voice Parameters
4. ATM interfaces
UM641 03.02/EN 6-18 July, 2003

WMG provisioning methodology (2/2)

NSTA
E1/0
E1/1 Mux
P1
SPM E1/2
SDH/0
E1/3
SDH/1
VPM
SDH/2
MSC
SDH/3
ATM VSP2 32pE1

UM641 03.02/EN 6-19 July, 2003

Step 1: 32pE1TDM card

E1 ports & channels
E1/0
LP/7
E1/1 Mux
P1
E1/2
E1/1 E1/2
E1/3
lineType ccs
clockingSource module
lineType ccs
clockingSource module =
MSC
chan/0 chan/0
ts 1 2 3 4 5 6 7 8 ….. ts 1 2 3 4 5 6 7 8 …..
32pE1
TDM components
LP/x E1/x
The lineType attribute defines the framing of the E1 line. The lineType attribute
beneath an E1 component must be set to ccs for 32pE1Atm.
The clockingSource attribute defines the source of the transmit for the E1 line.
• local means the crystal on the port generates the clocking for the line.
• module means the port’s clock synchronizes to the clock provided by the
oscillator on the active CP.
LP/x E1/x Channel/0
Only component Channel/0 is used. This component corresponds to the E1 Time
Slots (Ds0).
The timeSlots attribute corresponds to the time slots used for this specific E1 link.
UM641 03.02/EN 6-20 July, 2003

Step 2: VSP2 card

2.a. PM declaration
SPM = Signaling Processing Module
NSTA VPM = Voice Processing Module
Lp/15
VSP
SPM
=
VPM PM/1 PM/3 …. PM/12
moduleType spm moduleType spm moduleType vpm
2 SPM modules 10 VPM modules

(signaling) (voice processing)
VSP2
Vsp component
When a Vsp component is added to a logical processor the system with a card type
of Vsp2, 12 PModule components are automatically provisioned beneath the added
Vsp component.
Passport WMG dynamically creates one PBlock component for each PModule
component set to spm. Passport WMG creates two PBlock components for each
PModule component set to vpm.
Passport 15000 – Vsp2
The system sets the moduleType attribute for component PModule /1 and PModule/3
to spm.
The system sets the moduleType attribute for components PModule /2 and
PModule/4 through PModule/12 to vpm.
UM641 03.02/EN 6-21 July, 2003

Step 2: TRAU Function (voice)

2.b AmrBRAG provisioning
SPM or VPM allocation to
NSTA PCMLink is dynamic !
AAL1
NSTA/15 LP/7
Lp/15
E1/0 linkToServer LP/15 Vsp
VPM E1/1 VSP

P1 VGS E1/1
E1/2
TRAU
E1/3 PM/1 …. PM/12 AmrBRAG /1 chan /0
applicationFramerName
Nsta/15 Vgs AmrBrag/1
DS0/1
AAL1 connection
VGS between VSP and TDM
AmrBRAG Transcoded TDM Circuit
CsdBRAG Circuit Switched Data E1 traffic

Dynamic component representing
VSP2 E1 DS0/n Timeslot for the BRAG
AmrBRAG Provisioning
Essentially, the NSTA feature provides WMG with multiplexing/trunking between a TDM
voice network and an ATM network. It enables Passport PVG to carry VBR traffic across the
ATM network to a DS3/E1 TDM interface using standardized ATM AAL2 adaptation. This
allows bandwidth saving services, such as silence suppression and rate compression, to be
applied.
TDM ingress data streams are handled by a 32pE1Aal FP. These FPs demultiplex either
the DS3 and associated DS1 bit streams or the E1 bit stream into standard 64-kbps
channels for separate treatment. The 64-kbps channels are switched to a VSP2 FP for
encoding prior to being sent out over the ATM network.
An ATM FP handles the interface to the ATM network.
Nsta/n (NarrowbandServicesTrunkOverATM/n)
The Nsta component contains all narrowband connections for a single VSP2 FP. As such,
there is one Nsta per VSP2 FP.
Nsta/n attributes:
Attribute linkToServer contains a hardware link to a Vsp component.
Attribute idlePattern defines the pattern that is transmitted onto the TDM interface to
maintain bit integrity when data is unavailable from the ATM network. (Value: Hex 00–FF;
Default: 7F)
Nsta/n Vgs (Voice Gateway Service)
The Vgs component provides an operational and maintenance interface for switched voice
features. A Vgs subcomponent must be provisioned for the Nsta component to provide
switched trunking. If it is not provisioned the Nsta component will only support non-switched
trunking.
Nsta/x Vgs attributes (continued on next page)
UM641 03.02/EN 6-22 July, 2003

Nsta/n Vgs AmrBrag/n

This component defines a basic rate group, which represents a number of TDM connections
from the Voice Services Processor (VSP) to the TDM network. The TDM connections are all
associated with the same TDM interface. A particular AmrBrag is associated with a single
E1/ channel/ component. Connections on this channel are used to transport AMR-encoded
speech. This component defines default processing for all TDM connections on this
channel. For each connection, this default processing may be overridden by the controller.
Nsta/n Vgs AmrBrag/n attributes:
- interfaceName contains a link to a E1/ Channel/ component.
- other attributes (see later)
Nsta/x Vgs CsdBrag/n

This component represents a number of TDM connections from the Voice Services
Processor (VSP) to the TDM network. The TDM connections are all associated with the
same TDM interface.
A particular CsdBrag/ is associated with a single E1/ channel/ component. Connections on
this channel are used to transport CSD. This component defines default processing for all
TDM connections on this channel. For each connection, this default processing may be
overridden by the controller.
Nsta/x Vgs CsdBrag/n attributes:
- interfaceName contains a link to a E1/ Channel/ component.
- other attributes (see later)
UM641 03.02/EN 6-23 July, 2003

Step 2: Media Gateway: signaling (1)

2.c. MTP2
NSTA MTP2 à UDP port 12004
NSTA/15
E1/0
SPM E1/1 VGS
Port/0
E1/2
to ATM NEP
MTP2 E1/3
CTRL/mediagateway AmrBRAG /1
UDP/12004
IpAddress 10.0.180.240
MTP2/16
UDP/12001 UDP/12004
VPM
UdpPortConnection Nsta/15
Vgs Ctrl/mediaGateway
UdpPort/12004
layer3IpAddress 10.60.11.34
to SG MTP3 to SG GIPS/2 layer3Port 12004

VSP2 E3 (through AN) (through AN)
MTP2 Provisioning
The signaling between Passport WMG and the controller occurs over an ATM VCC.
Nsta/x Vgs ControlConnection/(mediaGateway, signalingGateway)
The mediagateway instance of the ControlConnection component defines a
communication path between the voice gateway (Vgs) and a Controller (Signaling
Gateway) for SPM/3;
The signalingGateway instance of the ControlConnection component defines a
communication path between the voice gateway (Vgs) and a Controller (Signaling
Gateway) for SPM/1;
Nsta/x Vgs ControlConnection/n attributes:
• ipAddress specifies the IP address of this media gateway. Control messages
from the controller are sent to this IP address to manage connections within this
media gateway.
• dnsServers specifies the IP addresses of the DNS servers available to this
media gateway. A DNS server translates between names and IP addresses.
Each DNS server has one IP address associated with it. A maximum of two
DNS servers is allowed.
Nsta/x Vgs Control/mg UdpPort/n
This component is used to link a UDP port, within a control connection, to an
application that sends and receives packets using the port.
Attribute linkToApplication indicates the application that sends and receives packets
using the UDP port. This attribute is set, for example, by provisioning the Nsta/n
Vgs AmrBrag/n MTP2/n UdpPortConnection attribute. If it is properly configured,
this attribute will show a value such as Nsta/n Vgs AmrBrag/n MTP2/n .
UM641 03.02/EN 6-24 July, 2003

Nsta/x Vgs AmrBrag/n MTP2/16

This component represents the MTP2 transport layer between the Call Server and
the Signaling Gateway. The instance of the component represents the signaling
timeslot on the TDM connection. This signaling timeslot contains RANAP messages
to/from the MSC. The component is reached by the VSP card throug h the UDP Port
provisioned under the Nsta/n Vgs Control/n UdpPort/n.
No more than six Mtp2/ components may be provisioned under a given Nsta/ Vgs
hierarchy.
Nsta/n Vgs AmrBrag/n MTP2/16 attributes
- udpPortConnection (udpConn): This attribute specifies the link to the Nsta/ Vgs
CtrlConn/ UdpPort/ component that defines the UDP port access to the IP
network for connection to the layer 3 user. It should match the UDP port
provisioned in the corresponding Mtp3/ Linkset/ Link/ component specified by
its remoteUdpPort attribute (Signaling Gateway side). A port must be specified
for Check Prov to succeed. Within a single Nsta/ Vgs hierarchy, at most three
Mtp2/ components can link to UdpPort/ components under the Ctrl/mg
component, and at most three Mtp2 components can link to UdpPort/
components under the Ctrl/sg component. Changing this attribute will cause the
link to be restarted.
- layer3IpAddress (l3IpAddr): This attribute specifies the remote IP address of the
layer 3 entity that owns this link. This address must match the IP address
provisioned in the corresponding Mtp3/ component specified by its linkToPort
attribute. Changing this attribute will cause the link to be restarted.
- layer3Port (l3Port): This attribute specifies the remote UDP port of the layer 3
entity that owns this link. This port must match the UDP port provisioned in the
corresponding Mtp3/ component specified by its linkToPort attribute. Changing
this attribute will cause the link to be restarted.
UM641 03.02/EN 6-25 July, 2003

Step 2: Media Gateway: signaling (2)

2.d ASPEN (VGCP)
NSTA VGCP (ASPEN) à UDP port 12001
NSTA/15
E1/0
SPM E1/1
UDP/12004 Port/0 VGS
MTP2
E1/2
to ATM NEP E1/3
VGCP
UDP/12001
CTRL/mediaGateway VGCP BRAG/1
IpAddress 10.0.180.240 UdpPortConnection

DnsServers Nsta/15 Vgs
Ctrl/mediaGateway
VPM UdpPort/12001
UDP/ 12004 UDP/ 12001 MgIfController /1 MgIfController /2
One MgIfController per VMG

to SG VMG
VSP2 32pE1 (through AN)
(one VMG per RNC):
that’s VSP PARTITIONING !!!
Nsta/n Vgs Vgcp

This component provides an interface to a controller using the ASPEN protocol.
Nsta/n Vgs Vgcp attributes:
• udpPortConnection specifies the link to the Nsta/n Vgs Control/mg UdpPort/n
component that defines the UDP port access to the IP network for the ASPEN
protocol. (Default: none)
• differentiatedServiceField specifies the differentiated service field in transmitted
ASPEN IP packets. Diffserv is used in IP networks to control quality of service.
Refer to RFC 791 for service field types. (Values: 0–63; Default: none)
VSP Partitioning feature:

This feature consists of using a VSP card for many RNC. VSP Ds0 resources will be
partitioned to several RNC.
Nsta/x Vgs Vgcp MgControllerIf/x
This component represents a Media Gateway (MG) Controller. This component
represents the interface to one specific Virtual Media Gateway (VMG) that runs on
the Signaling Gateway. It is only used for signaling (Circuit Switched Control Plane).
For each VSP card, one MgControllerIf/ has to be configured for the
communication one RNC (one VMG in Signaling Gateway).
UM641 03.02/EN 6-26 July, 2003

Step 2: Media Gateway: VGS Provisioning

NSTA
NSTA/15
E1/0
SPM E1/1 VGS
Port/0
E1/2 gatewayAtmAddress 47123456789012345678901234567890
hostName pvghost1
VPM
VSP2 32pE1
Nsta/n Vgs
The Vgs component provides an operational and maintenance interface for switched
voice features. The Vgs component has the following possible subcomponent types:
AmrBrag, CsdBrag, AtmTConn, Control and Vgcp.
Nsta/n Vgs attributes:
• gatewayAtmAddress specifies the ATM address of this Vgs component. This
address is used for identifying this gateway to the RNC. A change in the value
of this attribute causes all current calls to be dropped. If the nodePrefix attribute
of the ModuleData component has been provisioned, a default value for
gatewayAtmAddress will be generated by the system; otherwise, the
gatewayAtmAddress will default to an empty string.
• hostname specifies the host name of this gateway. It is required to identify this
gateway. The value provisioned in this attribute must match the value
provisioned in its associated Signaling Gateway. The hostname must be unique
within the group of gateways controlled by the controller. A change in the value
of this attribute causes all current calls to be dropped. (Value: ASCII string with
a non-zero length <=255; Default: none)
• defaultPacketLogLaw specifies whether the digitizing stream is m- law or A-law.
This attribute can be overridden by the packetLogLawattribute of the individual
AtmTConn components at call setup or by the per call values signaled by the
media gateway controller. (Default: A-law)
• defaultToneset specifies the default tone set for all Brag components. This
value can be overwritten by toneset attribute in Brag component. (Default:
canadaUsa)
UM641 03.02/EN 6-27 July, 2003

Step 3: VSP2 parameters & attributes

defaultRate 12.2 (kb/s)
tdmLogLaw autoConfigure NSTA/15
bufferSize 80 (ms)
packetDelayVariationTolerance 35 (ms)
lossIntegrationPeriod 5 (seconds) VGS
uplinkGain 0 (dB)
downlinkGain 0 (dB) defaultPacketLogLaw aLaw
echoCancellation enabled
defaultToneset CanadaUsa
minimumEchoReturnLoss 6 (dB)
echoCancelComfortNoiseGeneration enabled
echoCancellationTailLength 64 (ms)
backgroundNoiseConditioning disabled AmrBRAG /1
downlinkAutomaticControlGain disabled CsdBrag/1
downlinkAgctargetLevel –20 (dBm0)
downlinkAgcMaximumLoss –10 (dB) localAddress 1..44, AESANsapAddress
downlinkAgcMaximumGain 10 dB DS0/1 defaultMode transparent
uplinkAutomaticGainControl disabled
uplinkAgcTargetLevel –20 dBm0 defaultRate 64 kbit/s
uplinkAgcMaximumLoss –10 dB bufferSize 200 (ms)
uplinkAgcMaximumGain 10 dB packetDelayVariationTolerance 80 (ms)
disContinuousTransmission disabled lossIntegrationPeriod 5 (seconds)
backgroundReduction disabled
mobileEchoControl disabled MTP2/16
echoCancellationFixedDelay0 DS0/1
mobileEchoControlFixedDelay 220 (ms) aligmentReadyTimer 45 (seconds)
tandemFreeOperation disabled notAlignedTimer 60 (seconds)
downlinkAutomaticGainControl sameAsNormalMode alignedTimer 1500 (ms)
uplinkAutomaticGainControlTfo sameAsNormalMode
MobileEchoControlTfo sameAsNormalMode
normalProvingTimer 8500 (ms) DS0/n: dynamic
emergencyProvingTimer 1500 (ms)
iuTimeAlignment disabled component representing
echoCancelHybridDetector enabled sendSIBTimer 100 (ms)
remoteCongestionTimer 4500 (ms) Timeslot for the BRAG
If TDM is 4pOC3Ch TDM ackTimer 1250 (ms)
localAddress 1..44, AESANsapAddress
backgroundNoiseConditioningTfo sameAsNormalMode
dejitterBuffAdaptWindow 1.50 (s)
dejitterBuffAdaptMargin 1.0 (ms) Wireless Media Gateway Configuration 6-28
Nsta/x Vgs AmrBrag/ x

Attribute defaultRate specifies the AMR encoding rate for voice calls when no specific rate is given at
time of call setup time. (Value: 4.75 kbps, 5.15 kbps, 5.90 kbps, 6.70 kbps, 7.40 kbps, 7.95 kbps, 10.2
kbps, 12.2 kbps; Default: 12.2 kbps)
Attribute tdmLogLaw specifies the G.711 companding law to use on the TDM side of the NSTA trunk.
(Value: mu-law, a-law EBI, a-law ABI, autoconfigured; Default: autoconfigured)
Attribute bufferSize specifies the capacity of the PDV buffer. (Value: 5–100 ms; Default: 80 ms)
Attribute packetDelayVariationTolerance defines the maximum packet arrival jitter in milliseconds that
the AAL2 SSCS reassembly process will tolerate in the packet stream without producing errors on the
TDM interface. This attribute, together with the bufferSize attribute, can be configured to optimize the
jitter versus absolute delay trade-off in various network configurations. (Value: 5–50 ms; Default: 35
ms)
Attribute lossIntegrationPeriod specifies the interval of time in seconds for which a loss of packets
condition must persist before the packet loss status is set.
(Value: 1–60 s; Default: 5 s)
Attribute uplinkGain specifies the gain applied on the TDM ingress side to balance the network loss
plan. (Value: -15 to +15 dB; Default: 0 dB)
Attribute downlinkGain specifies the gain applied on the TDM egress side to balance the network loss
plan. (Value: -15 to +15 dB; Default: 0 dB)
Attribute echoCancellation enables or disables the echo cancellation feature. It can be enabled in
G.164 or G.165 tone disabler mode or left always on. (Value: g165Mode, disabled, alwaysOn,
g164Mode; Default: g165Mode)
Attribute minEchoReturnLoss specifies the minimum echo return loss expected on the line in dB.
(Value: Decimal 3; 6; Default: 3 db)
Attribute echoCancelComfortNoiseGeneration enables or disables comfort noise generation for the
echo cancellation feature. (Value: enabled, disabled; Default: enabled)
Attribute echoCancellationTailLength specifies the echo cancellation tail length applied to all
timeslots. This attribute has no effect if the echoCancellation attribute is set to disabled. (Value:
Decimal 64; Default: 64 ms)
UM641 03.02/EN 6-28 July, 2003

Attribute backgroundNoiseConditioning specifies the enabling or disabling of the background noise
conditioning and low-pass filtering. (Value: enabled, disabled, enabledLowPass; Default: disabled)
Attribute downlinkAutomaticControlGain specifies the enabling or disabling of the Automatic Gain
Control (AGC) in the downlink direction. (Value: enabled, disabled; Default: Disabled)
Attribute downlinkAgctargetLevel specifies the target signal power level of the Automatic Gain Control
(AGC) functionality in the downlink direction. AGC attempts to maintain a consistent call volume at
the specified target level. AGC is performed on the signal using this target value before downlinkGain
attribute is applied. (Value: Signed -30..-9; Default: -19 dBm0)
Attribute downlinkAgcMaximumLoss specifies the maximum loss that can be applied to any downlink
frame by the Automatic Gain Control (AGC) functionality. By specifying the maximum loss that AGC
can apply to any given frame, this value affects how quickly variations in call volume can be adjusted
toward the dnAgcTargLev attribute when a signal power loss is required for the adjustment. (Value:
Signed -14..-1; Default: -10 db)
Attribute downlinkAgcMaximumGain specifies the maximum gain that can be applied to any downlink
frame by the Automatic Gain Control (AGC) functionality. By specifying the maximum gain that AGC
can apply to any given frame, this value affects how quickly variations in call volume can be adjusted
toward the dnAgcTargLev attribute when a signal power gain is required for the adjustment. (Value:
Decimal 1..14; Default: 10 db)
Attribute uplinkAutomaticControlGain specifies the enabling or disabling of the Automatic Gain
Control (AGC) in the uplink direction. (Value: enabled, disabled; Default: disabled)
Attribute uplinkAgctargetLevel specifies the target signal power level of the Automatic Gain Control
(AGC) functionality in the uplink direction. AGC attempts to maintain a consistent call volume at the
specified target level. AGC is performed on the signal using this target value before uplinkGain
attribute is applied. (Value: Signed -30..-9; Default: -19 dBm0)
Attribute uplinkAgcMaximumLoss specifies the maximum loss that can be applied to any uplink frame
by the Automatic Gain Control (AGC) functionality. By specifying the maximum loss that AGC can
apply to any given frame, this value affects how quickly variations in call volume can be adjusted
toward the upAgcTargLev attribute when a signal power loss is required for the adjustment. (Value:
Signed -14..-1; Default: -10 db)
Attribute uplinkAgcMaximumGain specifies the maximum gain that can be applied to any uplink frame
by the Automatic Gain Control (AGC) functionality. By specifying the maximum gain that AGC can
apply to any given frame, this value affects how quickly variations in call volume can be adjusted
toward the upAgcTargLev attribute when a signal power gain is required for the adjustment. (Value:
Decimal 1..14; Default: 10 db)
Attribute disContinuousTransmission specifies the enabling or disabling of the Discontinuous
Transmission (DTX) functionality of the Adaptive Multi-Rate (AMR) speech encoder in the downlink
direction. In the uplink direction, the AMR speech decoder is capable of handling DTX Service
Identifier (SID) and no data frames. (Value: disabled, enabledSilent, enabledIuNoData; Default:
disabled)
Attribute BackgrroundReduction specifies the enabling or disabling of the background noise
reduction. (Value: enabled, disabled; Default: disabled)
Attribute mobileEchoControl specifies the enabling or disabling of the mobile echo control. (Value:
enabled, disabled; Default: disabled)
Attribute echoCancellationFixedDelay specifies the fixed delay offset for the echo cancellation tail
length applied to all timeslots. This attribute has no effect if the value of the echoCancellation attribute
is set to disabled. (Value: Decimal 0..16; Default: 0 ms)
Attribute mobileEchoControlFixedDelay specifies the fixed delay offset for the mobile echo control tail
length applied to all timeslots. The value specified must be a multiple of 20 msec. This attribute has
no effect if the value of the mobileEchoControl attribute is set to disabled. (Value: Decimal
100,120,140,160,180,200,220,240,260,280,300,320; Default 220 ms)
Attribute tandemFreeOperation specifies the enabling or disabling of the Tandem Free Operation
(TFO) functionality of the Transcoding and Rate Adaptation Unit (TRAU). (Value: enabled, disabled;
Default: disabled)
Attribute downlinkAutomaticGainControl specifies the enabling or disabling of the Automatic Gain
Control (AGC) in the downlink direction for Tandem Free Operation (TFO) mode. AGC in the
downlink may be turned off for TFO mode and it may still be on for the normal operations. (Value:
enabled, disabled, sameAsNormalMode; Default: sameAsNormalMode)
UM641 03.02/EN 6-29 July, 2003

Attribute uplinkAutomaticGainControlTfo specifies the enabling or disabling of the Automatic Gain
Control (AGC) in the uplink direction for Tandem Free Operation (TFO) mode. AGC in the uplink may
be turned off for TFO mode and it may still be on for the normal operations. (Value: enabled, disabled,
sameAsNormalMode; Default: sameAsNormalMode)
Attribute mobileEchoControlTfo specifies the enabling or disabling of the mobile echo control in
Tandem Free Operation (TFO) mode. Mobile Echo Control uplink may be turned off for TFO mode
and it may still be on for the normal operations. (Value: enabled, disabled, sameAsNormalMode;
Default: sameAsNormalMode)
Attribute luTimeAlignment specifies the enabling or disabling of the time alignment algorithm for the
Iu-User Plane (Iu-UP) functionality of the Transcoding and Rate Adaptation Unit (TRAU). (Value:
enabled, disabled; Default: disabled)
Attribute echoCancelHybridDetector specifies the enabling or disabling of the hybrid detector for the
echo cancellation functionality. The hybrid detector will temporarily disable the echo canceller when a
digital call is detected. (Value: enabled, disabled; Default: enabled)
The following attributes apply to the 4pOC3Ch TDM:

Attribute localAddress specifies the AmrBragS component Asynchronous Transfer Mode (ATM)
address. (Value: String 1..44, AESANsapAddress; Default: no default)
Attribute backgroundNoiseConditioningTfo specifies the enabling or disabling of the background noise
conditioning and low-pass filtering for Tandem Free Operation (TFO) mode. (Value: disabled,
enabled, enabledLowPass, sameAsNormalMode; Default: sameAsNormalMode)
Attribute dejitterBufferAdaptWindow specifies the window size over which the Universal Terrestrial
Radio Access Network (UTRAN) jitter is estimated for de-jitter buffer level adaptation. (Value:
Decimal disabled=0.00,0.25..30.00; Default: 1.5s)
Attribute dejitterBufferAdaptMargin specifies the margin for the dynamic de-jitter buffer level target.
The de-jitter buffer level is adjusted whenever it exceeds the target level by the specified margin. The
value of this attribute is rounded to the nearest multiple of 0.5 ms. (Value: Decimal 0.5..25.0; Default:
1.0 ms)
Nsta/x Vgs CsdBrag/ x

Attribute defaultRate specifies the AMR encoding rate for data calls when no specific rate is given at
time of call setup time. (Value: 14.4 kbps or 64.0 kbps; Default: 64.0 kbps)
Attribute defaultMode specifies the operational mode of a call within the TRAU. (Value: transparent,
nontransparent; Default: transparent)
Attribute bufferSize specifies the capacity of the PDV buffer. (Value: 5–100 ms; Default: 80 ms)
Attribute packetDelayVariationTolerance defines the maximum packet arrival jitter in milliseconds that
the AAL2 SSCS reassembly process will tolerate in the packet stream without producing errors on the
TDM interface. This attribute, together with the bufferSize attribute, can be configured to optimize the
jitter versus absolute delay trade-off in various network configurations. (Value: 5–50 ms; Default: 50
ms)
Attribute lossIntegrationPeriod specifies the interval of time in seconds for which a loss of packets
condition must persist before the packet loss status is set.
(Value: 1–60 s; Default: 5 s)
UM641 03.02/EN 6-30 July, 2003

PVG provisioning methodology (2)
1. TDM interface to Narrowband switch (32pE1TDM card) OK
2. Media Gateway (VSP card) OK
3. Voice Parameters OK
4. ATM interface (ATM card)

a. Transcoded voice encapsulation in ATM AAL-2 VCC (PVC)
b. ASPEN Signaling in ATM AAL-5 VCC (to Signaling Gateway)
UM641 03.02/EN 6-31 July, 2003

WMG Provisioning
PCM to VCC
SG
WMG
ASPEN
Control Plane Connection MTP2
VCC manager Signaling TS
UDP UDP
RNC AN 12004
12001 MSC
TRAU
AtmIf/ AtmIf/
User Plane VCC TDM trunk (Brag )
(AMR/AAL -2) (PCM: voice + MTP2)
WMG Provisioning
At least 2 separate Vcc has to be configured for the communication to one RNC:
• Vcc for CS UP to the RNC through the AN
• Vcc for CS CP to the SG through the AN
UM641 03.02/EN 6-32 July, 2003

Step 3: 4pOC3 card VSP

4.a. AAL-2 VCC for Voice VPM
TRAU
voice AtmIf/80 NEP (nailed -up NAP (nailed BRAG
Vcc/3.120 end point) adaptation point)
SDH/0
NSTA/15
LAPS/80 AtmIf/80
SDH/0
VGS
SDH/1
gatewayAtmAddress 471234… (20 bytes)
SDH/2
SDH/3 AtmTConn/1 AmrBRAG/1

Vc4/0 vcc/3.120
remoteAddress 471111… (20 bytes)
vcci 8
AtmIf /80
maxNumberAal2Trunks 124
packetLogLaw aLaw
holdOverTime 2.000
NEP
NAP MTP2/16
ATM atmConnection AtmIf/80
Gateway ATM address = VSP ATM @ Vcc/3.120 Nep
Remote address = RNC ATM @ (also on SG/ RNCIF in SG) Wireless Media Gateway Configuration 6-33
AAL-2 VCC
To link bearer channels to an ATM PVC interface, you must associate the NSTA services to the VCCs on
the ATM ports. To do this, associate a Nap subcomponent of an AtmTConn component to the Nep
subcomponent of an ATM interface VCC component. To connect the NSTA connections to the TDM
interface, link the interface name of the AmrBrag component to the TDM channel.
Nsta/x Vgs AtmTConn/x
The narrowband services trunking connection AtmTConn is the main application component defined for the
AAL2 trunk services.
Attribute remoteAddress specifies the ATM NSAP address of the node that can be reached via this trunk.
This address may not be the same as the value of the gatewayAtmAddress attribute of the Nsta Vgs
component. (Value: NSAP ATM address; Default: none)
Attribute vcci specifies the vcci for this trunk. It must be set to a value to uniquely identify an ATM trunk
between two nodes; consequently, all ATM trunks between any two nodes must have distinct vcci attribute
values. The connection on the remote node must be configured with the same vcci attribute value. ATM
trunks terminating on different remote nodes can share the same vcci attribute value. (Value: 0–32767;
Default: none)
Attribute maxNumberOfAal2Trunks specifies the maximum number of AAL2 trunks that can be allocated on
this ATM trunk. The local node can allocate no more than this number of trunks. (Value: 1–247; Default:
240)
Attribute packetLogLaw specifies whether the digitizing stream is m-law or A-law. This attribute defines the
default that is used by individual AtmTConn components at call setup, unless an alternative value is
provided by the controller. The remote end of this connection must be provisioned with the same
packetLogLaw attribute value.
Attribute holdOverTime specifies the maximum period of time before a partially filled AAL2 packet is
scheduled for transmission. (Value: 0.500–15.875 ms; Default: 2.000 ms)
Nsta/x Vgs AtmTConn/x Nap
This component is a nailed-up adaptation point, linking an AtmTConn component to an ATM interface.
Attribute atmConnection specifies a link to an Atmif Vcc/vpi. vci Nep component, which provides transport to
the ATM network.
UM641 03.02/EN 6-33 July, 2003

VSP
Step 3: 4pOC3 card UDP
SPM
4.b. AAL-5 VCC for Signaling 12004 MTP2
signaling
VGCP
AtmIf/80 NEP (nailed -up NAP (nailed UDP
Vcc/2.160 BRAG
end point) adaptation point) 12001
SDH/0
NSTA/15
LAPS/80 AtmIf/80
SDH/0
VGS
SDH/1 to MTP3 & VMG
(through AN)
SDH/2 CTRL/mediagateway
SDH/3 Vc4/0 vcc/2.160
IpAddress 10.0.180.240
AtmIf /80
UDP/ UDP/
NEP NAP 12004 12001
atmConnection AtmIf/80
Vcc/2.160 Nep Link to VGCS
ATM
Link to MTP2
Nsta/x Vgs Control/mg Nap

This component specifies the ATM trunk over which the Control component
communicates with the controller.
Attribute atmConnection specifies a link to an Atmif Vcc/vpi.vci Nep component,
which provides transport to the ATM network.
UM641 03.02/EN 6-34 July, 2003

Student notes
UM641 03.02/EN 6-35 July, 2003

Student notes
UM641 03.02/EN 6-36 July, 2003

Signaling Gateway Configuration
Section 7
UM641 03.02/EN 7-1 July, 2003

Objectives
• Configure the Signaling Gateway application for Packet Switched

• Configure the Signaling Gateway application for Circuit Switched
• Configure the Virtual Media Gateway application
• Configure the SAAL -NNI application
Signaling Gateway Configuration 7-2
UM641 03.02/EN 7-2 July, 2003

Contents
• SG Overview
• SG Provisioning for Packet Switched
• SG Provisioning for Circuit Switched
• VMG provisioning
• SAAL-NNI/ATM Provisioning
UM641 03.02/EN 7-3 July, 2003

Student notes
UM641 03.02/EN 7-4 July, 2003

Signaling Gateway Description
UM641 03.02/EN 7-5 July, 2003

SG/SAAL-NNI Functions
1 SG application for PS per RNC Packet Switched
U-SGSN
1 SG application for CS per RNC
USC VMG: Virtual Media
SM/GMM Gateway maps
ALCAP to ASPEN
RNC
RANAP-P S
AN SG PS
Iu links RANAP-PS
SS7 SAAL- NNI
SAAL- SG CS
RANAP-CS SAAL-- NNI
SAAL VMG
/SS7
ALCAP SAAL-- NNI
SAAL
SG
ASPEN
RANAP-CS
/SS7
ASPEN MTP2 ASPEN and RANAP are

1 SAAL-NNI application per ATM VCC
transferred over UDP/IP
between SG and WMG
VSP
WMG Circuit Switched Signaling Gateway Configuration 7-6
SG/SAAL-NNI Functions
The Signaling Gateway function passes the Control Plane messages from the RNC to
the U-SGSN for RANAP-PS (PS CP) and/or to the Wireless Media Gateway for
RANAP-CS (CS CP) for processing. It supports on the Iu interface the MTP3b,
SCCP, RANAP protocols.
On the Iu cs’ interface, to communicate with the MSC, the Signaling Gateway (and
Virtual Media Gateways) use the MTP2 protocol implemented on the Wireless Media
Gateway (VSP card) that forward the RANAP-CS message to the MSC.
ASPEN is terminated by the VSP card.
For Packet Switched, the RANAP-PS message terminates at the Signaling Gateway:
GMM and SM are forwarded to the USC on the U-SGSN.
UM641 03.02/EN 7-6 July, 2003

Signaling Gateway application

1 SG CS only card supports up to 2 RNCs U-SGSN
1 SG for 1 WMG
1 SG PS only card supports up to 2 RNCs (1 WMG = at least 1 VSP card)
USC USC
1 SG PS + CS card supports up to 2 RNCs
WMG A
SG FP
SG 1 PS WMG 2
A 0 1 2 3 44 5 6 7
WMG 1
ATM FP
ATM FP
SG 1 CS
SG - RNC
SG - RNC
CP3
CP3
ATM FP
ATM FP
CP Expansion
SG - RNC
SG - RNC
RNC 1 SG 2
(PS + CS) B 8 9 10 11 12 13 14 15
AN 1 MSC for 1 WG
SAAL -NNI
4p OC3/STM1
CP Expansion
SAAL -NNI
4p OC3/STM1
MSC
WMG B
I/O FP
RNC 2
(CS only) In this example, WMG 1
RNC1 is used for CS and PS
RNC2 for CS only WMG 2
Signaling Gateway Application

Up to 2 RNCs can be supported by one SG ATM FP.
Up to 2 SG applications can be configured on one SG FP.
One RNC needs 1 or 2 SG applications:
• 1 for PS or CS (example of RNC2)
• 2 for PS and CS (example of RNC1)
Note: Nortel Networks recommends to have only one RNC per SG PS + CS card to
avoid impacting RNC capacity.
UM641 03.02/EN 7-7 July, 2003

WG Point Code
PC USC
1 linkset for PS (for PS) linksets for CS
SG PS (through WMG)
PC RNC
SG
SG CS PC MSC
1 linkset for CS PC MSC PC RNC
(for CS) MSC
iRNC
WG
1 or 2 Linkset to the same RNC

⇔
1 or 2 SS7 Point Code per SG to the same RNC
1 linkset for CS + PS linksets for CS

(through WMG)
PC RNC PC MSC SG PC MSC
(for CS + PS)
PC RNC
iRNC MSC
WG
WG Point Code
The Core Network directs messages to the RNC using the SS7 Point Code of the
RNC: the SG application of this RNC is provisioned with the RNC’s Point Code.
• RNC may direct messages to the Core Network using a single Point Code for
the CS domain and the PS domain: the RNC’s SG is provisioned with the Point
Code of the MSC (CS domain’s Point Code) and the SG application supports the
RNC’s Control Plane for CS and PC domains, the SG looks into each RANAP
message to identify the correct domain to forward the message.
• But the RNC may also direct messages to the Core Network using two different
Point Codes for the CS and PS domains: therefore the RNC will be support by
two SG functions, one provisioned with the MSC’s Point Code, another
provisioned with a private Point Code (isolated from the SS7 network) common to
all the SG functions of the WG only dedicated to PS domain.
To sum up, one SG FP card can have between two Signaling Gateway applications
for two RNCs.
UM641 03.02/EN 7-8 July, 2003

WG Control Plane : Signaling Gateway

to U-SGSN (USC card)
SG OC3MM card
SG
I/O OC3SM card
PS CS VMG
RANAP Q.2630.1 RANAP-CS
SCCP Q.2150.1 ASPEN SCCP
MTP3-B GIPS2 MTP3
SAAL-NNI GIPS8
Iu
AAL5
ATM
to WMG (MTP2)
Q.2630.1 : ALCAP
Q.2150.1 : SCF to WMG (ASPEN)
Signaling Gateway Control Plane

Signaling Gateway Control Plane can be divided in 3 main parts:
• RANAP Packet Switched Signaling: it concerns the SG for :
• Iu ps interface only: the content of the RANAP message received/sent from/to the
RNC is forwarded to/from the U-SGSN (USC card). This RANAP message is
routed by a linkset (MTP3) over AAL-5 Vcc (SAAL-NNI ATM protocol is able to
able signaling from MTP3 level to ATM VCC)
• RANAP Circuit Switched Signaling: it concerns the SG for :
• Iu cs interface: the content of the RANAP message received/sent by/from the
RNC is forwarded to/from the MSC through the Iu cs’ interface. This RANAP
message is routed by a linkset (MTP3) over AAL-5 Vcc (SAAL-NNI ATM protocol
is able to able signaling from MTP3 level to ATM VCC)
• Iu cs’ interface: the RANAP message is forwarded to/from the MSC and routed
by a linkset (MTP3) over AAL-5 Vcc to the WMG and then over MTP2/MTP1
between the WMG and the MSC (TDM interface)
• ALCAP/ASPEN Packet Switched Signaling (Virtual Media Gateway)
• Iu cs interface: the content of the ALCAP message received from the RNC is
forwarded is analyzed by the Virtual Media Gateway (sub-entity of the Signaling
Gateway). This ALCAP message is routed by a linkset (MTP3) over AAL-5 Vcc
(SAAL-NNI ATM protocol is able to able signaling from MTP3 level to ATM VCC)
• Between SG and WMG: The content of the ALCAP message is forwarded by
ASPEN to the WMG (destination: VSP card). The VSP will be able to allocate the
AAL-2 and TDM resource for the incoming voice call.
UM641 03.02/EN 7-9 July, 2003

SG communication (1 PC for PS and CS)

I/O SG
to U-SGSN
(USC card)
RANAP
SAAL -NNI
MTP3 MTP3
(RNC) (CS)
UDP
12003 UDP UDP
12002 12004
VMG
Gips/2
VR/1 to MTP2
Gips/8 (WMG) UDP
12001
IP IP
PP/gips8 PP/gips2
to Connection
Manager
AtmIf/
(WMG)
AtmIMpe/
Sdh/0
Signaling Inter -shelves

VCC/ VCC/
to AN
(to RNC or WMG) Signaling Gateway Configuration 7-10

Signaling Gateway application (1 per RNC, maximum 2 per cards) for PS+CS
If the RNC is connected to its SG through one linkset (the same one used for PS and CS),
only 2 MTP3 Point Codes (PC) have to be provisioned on the Signaling Gateway application:
• 1 PC for Iu interface: this is configured in the MTP3 application (for RNC interface) in the
Signaling Gateway application used for Circuit Switched signaling and also Packet
Switched signaling. This application has to talk:
- with the SAAL-NNI application configured on the ATM card.
- with its SCCP application that reads into the RANAP message to send the content
of the RANAP to:
• The SCCP application used by the second MTP3 application for Iu cs’ interface
• With the USC application configured in the U-SGSN for Packet Switched.
• 1 PC for Iu cs’ interface: this is configured in another MTP3 application (for MSC
interface: CS) in the same Signaling Gateway application. This application has to talk:
- with the MTP2 application configured in the VSP card on the WMG for Circuit
Switched
- with the VMG application (Virtual Media Gateway) used for ALCAP/ASPEN
signaling. VMG is reachable through another UDP port and the same GIPS and has
to talk to the VGS application configured in the VSP card on the WMG.
These 2 MTP3 applications are reached through specific UDP Ports and a GIPS configured
in the SG FP (1 GIPS only for several SG applications).
SAAL-NNI application (1 per AAL5 Vcc, maximum 32 per ATM cards)
These SAAL-NNI applications are reached through specific UDP Ports and a GIPS in the
ATM FP (1 GIPS only for several SG applications).
UM641 03.02/EN 7-10 July, 2003

SG communication (1 PC for PS and 1 PC for CS)

I/O SG to U-SGSN
(USC card)
RANAP
SAAL -NNI
MTP3 MTP3 MTP3
(RNC PS) (CS)
(RNC CS)
UDP UDP
12003 UDP 12006 UDP
12002 12004
VMG
Gips/2
VR/1 to MTP2
Gips/8 (WMG) UDP
12001
IP IP
PP/gips8 PP/gips2
to Connection
Manager
AtmIf/
(WMG)
AtmIMpe/
Sdh/0
Signaling Inter -shelves

VCC/ VCC/
to AN
(to RNC or VSP-WMG) Signaling Gateway Configuration 7-11

Signaling Gateway application (1 per RNC, maximum 4 per cards) for PS+CS
If the RNC is connected to its SG through 2 separete linkset for PS and CS, 3 MTP3
Point Codes (PC) have to be provisioned on 2 different Signaling Gateway
applications:
• SG application for Circuit Switched:
• 1 MTP3 application for Iu interface: this configures the Point Code for the RNC
linkset. This application has to talk:
- with the SAAL-NNI application configured on the ATM card.
- with its SCCP application that talks with the SCCP application used by the
second MTP3 application for Iu cs’ interface
• 1 MTP3 application for Iu cs’ interface (same Signaling Gateway application): this
configures the Point Code for MSC linset. This application has to talk:
- with the MTP2 application configured in the VSP card on the WMG for Circuit
Switched
- with the VMG application (Virtual Media Gateway) used for ALCAP/ASPEN
signaling. VMG is reachable through another UDP port and the same GIPS
and has to talk to the VGS application configured in the VSP card on the
WMG.
These 2 MTP3 applications are reached through specific UDP Ports and a GIPS
configured in the SG FP (1 GIPS only for several SG applications).
UM641 03.02/EN 7-11 July, 2003

• SG application for Packet Switched:

• 1 PC for Iu interface: this is configured in the MTP3 application (for RNC
interface) in the Signaling Gateway application used for Packet Switched
signaling only. This application has to talk with the SAAL-NNI application
configured on the ATM card.
This MTP3 application is reached through specific UDP Ports and a GIPS configured
in the SG FP (1 GIPS only for several SG applications).
SAAL-NNI application (1 per AAL5 Vcc, maximum 32 per ATM cards)

These SAAL-NNI applications are reached through specific UDP Ports and a GIPS in
the ATM FP (1 GIPS only for several SG applications).
UM641 03.02/EN 7-12 July, 2003

WG ATM and IP configuration for Signaling

SG independant (Shelf Type 6)
Vcc/0.46 (control) AtmIf/20 Vcc (CS CP) AN
RNC
10.0.180.1
VR/1
10.60.11.14
AtmIf/80
Vcc/2.160 AtmIf/41 AtmIf/41
(CS CP: MTP2)
VSP 10.0.180.240 Vcc/1.400 Vcc/1.200
(CS CP: MTP2) (CS CP RNC)
SG AtmIf/80
10.60.11.13
WMG VR/1
10.60.11.32\30 10.60.11.128\30
GIPS 2 GIPS 8
SAAL-
SG
NNI Signaling Gateway Configuration 7-13
ATM and IP Configuration

routing between shelves in WG for Circuit Switched Control Plane.
• IP routing: SG (Shelf Type 6) communicates to WMG (Shelf Type 5) through
AN and VR/1 (VCC/1.400 between SG and AN; VCC/2.160 between AN and
WMG)
UM641 03.02/EN 7-13 July, 2003

Student notes
UM641 03.02/EN 7-14 July, 2003

SG Provisioning for Packet Switched
UM641 03.02/EN 7-15 July, 2003

SG GIPS provisioning for Iu interface

SG
SG
to USC
CS PS
RANAP
MTP3 SCCP
(RNC)
UDP MTP3-B GIPS2
12006
VR/1
SAAL-NNI
Gips/2 Iu
IP
AAL5
PP/gips2
ATM
to AN
SG OC3 card
I/O OC3 card (A)
SG GIPS Provisioning
Packet Switched Signaling Gateway application is limited to the Iu ps interface:
• MTP3-b protocol
• SCCP protocol
• RANAP protocol
UM641 03.02/EN 7-16 July, 2003

Signaling Gateway Provisioning

Methodology:
1. SG Provisioning
a. Provision RNC interface (RNC Id and NSAP @)
b. Provision Packet Switched interface (to U-SGSN)
2. SG GIPS and MTP3-b Application Provisioning

b. Provision the GIPS (on the same private subnet) for PS MTP3-b application
c. Provision the UDP Ports under the GIPS and link it to MTP-3b application
3. SS7 Provisioning for Iu PS

a. Provision MTP-3 linkset to RNC (Point Codes and interface to SAAL-NNI)
b. Provision SCCP interface
c. Provision RANAP interface

Methodology in 3 steps:
1. Signaling Gateway application provisioning (for PS only)
2. SG GIPS and MTP-3 applications provisioning
3. SS7 provisioning:
• MTP3 linkset
• SCCP
• RANAP
UM641 03.02/EN 7-17 July, 2003

Step 1: SG application Provisioning for PS
Lp/2 SG/3
linkToLP LP/2
RncInterface PsDomain
rncId 0
rncAtmAddress 47111…. RNC ATM Address = ATM @ of RNC
(20 bytes long)
SCCPConn
To SCCP
(RNC)
Step 1: Signaling Gateway application provisioning (for PS only)

2 domains to to configure:
• RNC interface domain: this is represented by the RncInterface component. This
component identifies the RNC connected to this SG application. It has to be
identified by:
- its ID: rncId attribute. It has to match the ID provisioned on the RNC
- its ATM NSAP address: rncAtmAddress attribute. It has to match the ATM
NSAP address provisioned on the RNC
• PS domain: this is represented by the PsDomain component. It will be able to
talk with the USC application when SVC will be setup between the SG and the U-
SGSN USC applications (trough the AN).
UM641 03.02/EN 7-18 July, 2003

Step 2: SG Provisioning : GIPS 2

VR/1 SG
PP/gips2
10.60.11.33 Gips/2 UDP 12006 MTP3
10.60.11.34
(RNC PS)
IpAddress/
vr/1 Gips/2 Lp/2 MTP3/23

Processor lp/2
pp/gips2 linkToProtocolPort v r/1 pp/gips2
linkToPort gips/2
Ipaddress/10.60.11.34
IpAddress/ Udp Port/12006
ipport
10.60.11.34
10.60.11.33
Udp
NetMask 255.255.255.252
MTP3/23 is used for the

Port/12006 linkset to the RNC for
Packet Switchedonly
Step 2: GIPS and MTP3 application provisioning

As the GIPS provisioned in U-SGSN, 3 branches have to be provisioned:
• The GIPS CIT:
GIPS/x (GPRS IP Server) is a top-level component that represents the host
UDP/IP server on the SG card. This IP Server must be linked to the Logical
Processor of the SG FP (LP/2 in this example).
• The MTP3 CIT:
MTP3/x top-level component represents the MTP3 signaling traffic on SG. This
component is linked to the sub-component Port/x of the GIPS/ component. This
port allows access of SAAL-NNI cells to MTP3 layer.
• The Virtual Router CIT:
The IP address of the IP Server is the first application that is going to use the IP
Server. GIPS needs to have an IP address that is on the same sub-network than
the address of the virtual port of the virtual router (VR/ component). For a virtual
port (ProtocolPort/x component, sub-component of the VirtualRouter/x
component), we need to provision the IP address under the IPLogicalInterface/x
component. GIPS/x component is linked on the virtual router to its IP interface by
the LinkToProtocolPort attribute.
UM641 03.02/EN 7-19 July, 2003

Step 3: SS7 Configuration for PS

WG
PC = Point Code
Point Code used for SG on Iu interface SG • originated Point Code (OPC)
is the one of the WG for Packet U-SGSN • destination Point Code (DPC)
Switched signaling management
• adjacent Point Code (same as DPC)
PC 0.0.6 SG (PS) Linkset = 1 to 16 Links
Linkset to RNC
AN
PC 0.0.3 SS7
RNC
Step 3: SS7 applications provisioning

Packet Switched Signaling Gateway provisioning consists of:
• MTP3 application provisioning: Point Codes (OPC, DPC, APC), linkset and links
to the RNC
• SCCP and RANAP applications provisioning: link to MTP3 and to the RNC
interface
UM641 03.02/EN 7-20 July, 2003

Step 3: SS7 Provisioning : linkset to RNC

Iu interface for PS
RANAP(RNC)/SCCP/MTP3B
Gips/2 MTP3/23 SCCP/23 SG/3

linkToLogicalProcessor lp/2 linkToLogicalProcessor lp/2 linkToLogicalProcessor lp/2
linkToProtocolPort linkToPort gips/2 RncInterface
v r/1 pp/gips2 Ipaddress/10.60.11.34
Udp Port/12006
originatedPointCode 0.0.6 Mtp3Conn LocalS/142
IpAddress/ mtpType mtp3b linkToSccpConnection
10.60.11.34 Sg/2 RncIf
subsystemNumber ranap
Udp ServInd/3
LinkSet/0
adjPointCode 0.0.3 linkToMtp3Conn
Sccp/23 Mtp3Conn
Port/12006 RemoteSubsystem/142
Link/0 subsystemNumber ranap
remoteIpAddress 10.60.11.130
To SaalNNi
remoteUdpPort 12003
OPC = 0.0.6 (PS SG) SSN 142 identifies RANAP
APC = 0.0.3 (RNC) Sub System Number
SAAL -NNI UDP Port: 12003

Packet Switched Signaling Gateway provisioning consists of:
• MTP3 application provisioning:
• Point Codes:
- OPC: is configured by setting the PC value to the originatedPointCode attribute. The value must
be the PC of the MSC.
- DPC: is configured by setting the PC value to the adjacentPointCode attribute under the
LinkSet/0 component. Since there are no STP between RNC and SG, the Adjacent Point Code
(APC) is equivalent to the Destination Point Code (DPC). The value must be the PC of the RNC.
• linkset to the RNC: is represented by the LinkSet/0 component, sub-component of MTP3/x
application. The Adjacent Point Code (APC) is configured under this component by filling the
adjacentPointCode attribute.
• links to the RNC: is represented by the Link/x component, sub-component of LinkSet/0 component.
This linkset needs to be mapped to an AAL5 Vcc to the RNC. To encapsulate MTP3-b in AAL-5, this
link has to talk with the SAAL-NNI application used by its Vcc. This communication is made by
provisioning 2 attributes that identify the SAAL-NNI application:
- The SAAL-NNI GIPS IP address: remoteIpAddress attribute
- The SAAL-NNI GIPS UDP Port: remoteUdpPort attribute
MTP3-b type is provisioned by filling the mtp3type attribute and setting the mtp3b value.
• SCCP and RANAP applications provisioning: link to MTP3 and to the RNC interface:
• SCCP: provisioned by the SCCP/x component. SCCP application is linked to the MTP3 sub-layer
through one of its sub-component: MTP3Connection component.
• RANAP: 2 components representing:
- The RANAP local (WG) sub-system: LocalSubSystem/142 component and its
subSystemNumber attribute (142 is RANAP’s SSN). This component is linked to the SG through
its linkToSccpConnection attribute to the SG/x RNCInterface component.
- The RANAP remote (RNC) sub-system: RemoteSubSystem/142 component and its
subSystemNumber attribute (142 is RANAP’s SSN)
UM641 03.02/EN 7-21 July, 2003

Student notes
UM641 03.02/EN 7-22 July, 2003

SG Provisioning for Circuit Switched:

RANAP Signaling (from RNC to MSC)
UM641 03.02/EN 7-23 July, 2003

SG GIPS provisioning
SG
SG
VMG
PS CS VMG
MTP3
(CS : VMG) RANAP Q.2630.1 RANAP-CS
MTP3 SCCP Q.2150.1 ASPEN SCCP
(RNC)
UDP UDP MTP3-B GIPS2 MTP3
12002 12004
UDP VR/1
12001 SAAL-NNI
Gips/2 Iu
IP
AAL5
PP/gips2
ATM
SG OC3 card
I/O OC3 card (A)
Circuit Switched Signaling Gateway Application

Circuit Switched Signaling Gateway application corresponds to:
• the Iu interface (to RNC):
• MTP3-b protocol
• SCCP protocol
• RANAP protocol
• the Iu cs’ interface (to MSC):
• MTP3 protocol
• SCCP protocol
• RANAP protocol
• the VMG:
• MTP3 protocol
• ALCAP protocol
• ASPEN protocol
UM641 03.02/EN 7-24 July, 2003


Methodology:
1. SG Provisioning
a. Provision RNC interface (RNC Id and NSAP @)
b. Provision Circuit Switched interface to RNC (Iu cs)
c. Provision Circuit Switched interface to MSC (Iu cs’)
2. SG GIPS and MTP3-b and MTP3 Applications Provisioning

b. Provision the GIPS (on the same private subnet) for PS MTP3-b application
c. Provision the UDP Ports under the GIPS and link it to MTP-3b application
3. SS7 Provisioning for Iu cs (RNC interface)
4. SS7 Provisioning for Iu cs’ (MSC interface)


Signaling Gateway provisioning methodology in 4 steps (VMG not detailed):
1. Signaling Gateway application provisioning (for PS only)
2. SG GIPS and MTP-3 applications provisioning
3. SS7 provisioning for Iu cs:
• MTP3 linkset to RNC
• SCCP
• RANAP
4. SS7 provisioning for Iu cs’:
• MTP3 linkset to MSC
• SCCP
• RANAP
UM641 03.02/EN 7-25 July, 2003

Step 1: SG application Provisioning

RNC ATM Address = ATM @ of RNC (20 bytes long)
This address should match the remote address

provisioned under NSTA/ VGS ATMTConn/ on VSP card
Lp/2 If 1 PC is used
VMG/20 SG/2
for CS and PS
linkToLP LP/2 linkToLP LP/2
VMG for ALCAP

(see next part) CsDomain RncInterface PsDomain
linkToVmg Vmg/20 rncId 0
rncAtmAddress 47111….
SCCPConn SCCPConn
To SCCP To SCCP
(MSC) (RNC)
Step 1: Signaling Gateway application provisioning (for CS only)

2 domains to to configure:
• RNC interface domain: this is represented by the RncInterface component. This
component identifies the RNC connected to this SG application. It has to be
identified by:
- its ID: rncId attribute. It has to match the ID provisioned on the RNC
- its ATM NSAP address: rncAtmAddress attribute. It has to match the ATM
NSAP address provisioned on the RNC. This RNC ATM NSAP address is
also provisioned under the NSTA/x VGS AtmTConn/x component
• CS domain: this is represented by the CsDomain component. It will be able to
talk with:
- the SCCP application for the Iu cs’ interface
- the VMG application to send ASPEN to the WMG
Note: PsDomain sub-component is provisioned only if the Signaling Gateway

application (SG/x component) is used for PS and CS (it means if only one PC is used
for PS + Cs on Iu interface)
UM641 03.02/EN 7-26 July, 2003

Step 2: SG Provisioning : GIPS 2

VMG
UDP 12001
VR/1 SG
PP/gips2
Gips/2 UDP 12004 MTP3/21
10.60.11.33
10.60.11.34 (CS)
IpAddress/
MTP3/20
UDP 12002 (RNC)
vr/1 Gips/2 Lp/2 MTP3/21 VMG/20

linkToLogicalProcessor lp/2 linkToLogical linkToPort gips/2
Processor lp/2 Ipaddress/ 10.60.11.34
pp/gips2 linkToProtocolPort v r/1 pp/gips2 Udp Port/12001
linkToPort gips/2
IpAddress/ Udp Port/12004
ipport VMG for ALCAP
10.60.11.34 MTP3/20 (see next part)
IpLogicalInterface / linkToLogicalProcessor lp/2

10.60.11.33 linkToPort gips/2
Udp Ipaddress/10.60.11.34
NetMask 255.255.255.252 Udp Port/12002
Port/12001 Port/12002 Port/12004
Step 2: GIPS and MTP3 application provisioning

As the GIPS provisioned in U-SGSN or for SG Packet Switched, 3 branches have to
be provisioned:
• The GIPS branch:
GIPS/x (GPRS IP Server) is a top-level component that represents the host
UDP/IP server on the SG card. This IP Server must be linked to the Logical
Processor of the SG FP (LP/2 in this example).
• The MTP3 branch:
MTP3/x top-level component represents the MTP3 signaling traffic on SG. This
component is linked to the sub-component Port/x of the GIPS/ component. This
port allows access of SAAL-NNI cells to MTP3 layer.
• The Virtual Router branch:
The IP address of the IP Server is the first application that is going to use the IP
Server. GIPS needs to have an IP address that is on the same sub-network than
the address of the virtual port of the virtual router (VR/ component). For a virtual
port (ProtocolPort/x component, sub-component of the VirtualRouter/x
component), we need to provision the IP address under the IPLogicalInterface/x
component. GIPS/x component is linked on the virtual router to its IP interface by
the LinkToProtocolPort attribute.
UM641 03.02/EN 7-27 July, 2003

Step 3 & 4: SS7 Configuration

WG
PC = Point Code
SG • originated Point Code (OPC)
• destination Point Code (DPC)
U-SGSN
• adjacent Point Code (same as DPC)
PC 0.0.3
PC 0.45.6
SG Linkset = 1 to 16 Links
Linkset to RNC
( Iu cs interface) Linkset to MSC
( Iu cs’ interface)
AN
PC 0.45.6
PC 0.0.3
SS7
RNC
MSC

Circuit Switched Signaling Gateway provisioning consists of:
• Iu cs interface provisioning (RNC interface):
• MTP3 application (MTP3-b) provisioning: Point Codes (OPC, DPC, APC), linkset
and links to the RNC
• SCCP and RANAP applications provisioning: link to MTP3 and to the RNC
interface
• Iu cs’ interface provisioning (MSC interface):
• MTP3 application provisioning: Point Codes (OPC, DPC, APC), linkset and links
to the MSC
• SCCP and RANAP applications provisioning: link to MTP3 and to the MSC
interface
UM641 03.02/EN 7-28 July, 2003

Step 3 & 4: WG CS RANAP Signaling
Shelf Type 6 Signaling Gateway Shelf Type 5
RANAP- CS
SCCP SCCP
MTP3-B MTP3
SAAL-NNI MTP2
UDP UDP
UDP UDP
AAL5 VR/1 12002 12004 VR/1 12004
12003
GIPS/8 GIPS/2 IP (VSP) PCM
PP/gips8 PP/gips2 PP/gips2 PP/AN
ATM
to RNC to MSC

1. Signaling Gateway application provisioning (for PS only) à OK
2. SG GIPS and MTP-3 applications provisioning à OK
• SCCP
• RANAP
• SCCP
• RANAP
UM641 03.02/EN 7-29 July, 2003


Methodology:
1. SG Provisioning OK
2. SG GIPS and MTP3 Application Provisioning OK
3. SS7 Provisioning for Iu cs (RNC interface)

a. Provision MTP3-b linkset to RNC (Point Codes and interface to SAAL-NNI)
4. SS7 Provisioning for Iu cs’ (MSC interface)

a. Provision MTP3 linkset to MSC (Point Codes and interface to MG for MTP2)

1. Signaling Gateway application provisioning (for PS only) à OK
2. SG GIPS and MTP-3 applications provisioning à OK
• SCCP
• RANAP
• SCCP
• RANAP
UM641 03.02/EN 7-30 July, 2003

Step 3: SS7 Provisioning : linkset to RNC

Iu INTERFACE RANAP(RNC)/SCCP/MTP3B
Gips/2 MTP3/20 SCCP/20 SG/2

linkToProtocolPort linkToPort gips/2 RncInterface
Udp Port/12002
originatedPointCode 0.45.6 Mtp3Conn LocalS/142 SCCPConn
IpAddress/ mtpType mtp3b linkToSccpConnection
10.60.11.34 Sg/2 RncIf SccpConn
Udp LinkSet/0 ServInd/3

linkToMtp3Conn
adjPointCode 0.0.3 Sccp/20 Mtp3Conn
Port/12002 RemoteSubsystem/142
Link/0 subsystemNumber ranap
To SaalNNi
remoteUdpPort 12003
OPC = 0.45.6 (MSC) SSN 142 identifies RANAP
MTP3/SAAL -NNI UDP Port : 12003 APC = 0.0.3 (RNC) Sub System Number

Circuit Switched Signaling Gateway provisioning for Iu cs interface consists of:
• Point Codes:
- OPC: is configured by setting the PC value to the originatedPointCode attribute. The value must be
the PC of the MSC.
- DPC: is configured by setting the PC value to the adjacentPointCode attribute under the LinkSet/0
component. Because there are no STP between RNC and SG, the Adjacent Point Code (APC) is
equivalent to the Destination Point Code (DPC). The value must be the PC of the RNC.
• linkset to the RNC: is represented by the LinkSet/0 component, sub-component of MTP3/x application.
The Adjacent Point Code (APC) is configured under this component by filling the adjacentPointCode
attribute.
• links to the RNC: is represented by the Link/x component, sub-component of LinkSet/0 component.
This linkset needs to be mapped to an AAL5 Vcc to the RNC. To encapsulate MTP3-b in AAL-5, this link
has to talk with the SAAL-NNI application used by its Vcc. This communication is made by provisioning 2
attributes that identify the SAAL-NNI application:
- The SAAL-NNI GIPS IP address: remoteIpAddress attribute
- The SAAL-NNI GIPS UDP Port: remoteUdpPort attribute
MTP3-b type is provisioned by filling the mtp3type attribute and setting the mtp3b value.
• SCCP and RANAP applications provisioning: link to MTP3 and to the RNC interface:
- The RANAP local (WG) sub-system: LocalSubSystem/142 component and its subSystemNumber
attribute (142 is RANAP’s SSN). This component is linked to the SG through its
linkToSccpConnection attribute to the SG/x RNCInterface component.
- The RANAP remote (RNC) sub-system: RemoteSubSystem/142 component and its
UM641 03.02/EN 7-31 July, 2003

Step 4: SS7 Prov : linkset to Media Gateway (CS)

Iu cs’ INTERFACE RANAP(CS)/SCCP/MTP3
Gips/2 MTP3/21 LP/2 SCCP/21 SG/2

linkToPort gips/2 CsDomain
linkToProtocolPort
Udp Port/12004
originatedPointCode 0.0.3 Mtp3Conn LocalS/142 SCCPConn
IpAddress/ mtpType mtp3 linkToSccpConnection
10.60.11.34 Sg/2 CsDomain SccpConn
Udp ServInd/3
LinkSet/0
linkToMtp3Conn
adjPointCode 0.45.6 Sccp/21 Mtp3Conn
Port/12004
Link/0 RemoteSubsystem/142
remoteIpAddress 10.0.180.240 subsystemNumber ranap
to VSP/MTP2
(WMG) remoteUdpPort 12004
OPC = 0.0.3 (RNC)
APC = 0.45.6 (MSC)
MTP3/MTP2 UDP Port : 12004

Circuit Switched Signaling Gateway provisioning for Iu cs’ interface consists of:
• Point Codes:
- OPC: is configured by setting the PC value to the originatedPointCode attribute. The value must be
the PC of the RNC.
- DPC: is configured by setting the PC value to the adjacentPointCode attribute under the LinkSet/0
component. Because there are no STP between RNC and SG, the Adjacent Point Code (APC) is
equivalent to the Destination Point Code (DPC). The value must be the PC of the MSC.
• linkset to the MSC: is represented by the LinkSet/0 component, sub-component of MTP3/x application.
The Adjacent Point Code (APC) is configured under this component by filling the adjacentPointCode
attribute.
• links to the MSC: is represented by the Link/x component, sub-component of LinkSet/0 component.
This linkset needs to reach the VSP card (SPM) for MTP3/MTP2 IP routing. This communication is made
by provisioning 2 attributes that identify the VSP FP:
- The VSP IP address: remoteIpAddress attribute
- The VSP UDP Port (UDP Port for MTP2 application): remoteUdpPort attribute
MTP3 type is provisioned by filling the mtp3type attribute and setting the mtp3 value.
• SCCP and RANAP applications provisioning: link to MTP3 and to the MSC interface:
- The RANAP local (WG) sub-system: LocalSubSystem/142 component and its subSystemNumber
attribute (142 is RANAP’s SSN). This component is linked to the SG through its
linkToSccpConnection attribute to the SG/x CsDomain component.
- The RANAP remote (MSC) sub-system: RemoteSubSystem/142 component and its
UM641 03.02/EN 7-32 July, 2003

SG Provisioning for Circuit Switched:

Virtual Media Gateway Provisioning
UM641 03.02/EN 7-33 July, 2003

WG CS Connection Manager Signaling

Shelf Type 6 Shelf Type 5
(SG) (WMG)
Virtual Media Gateway (VMG)
ALCAP
SCF ASPEN
MTP3-B
Connection
SAAL-NNI Manager (ASPEN)
UDP UDP
UDP UDP 12001
AAL5 12003 VR/1 12002 12001 VR/1
GIPS/8 GIPS/2 IP (VSP)

PP/gips8 PP/gips2 PP/gips2 PP/AN
ATM
to RNC
UM641 03.02/EN 7-34 July, 2003

Virtual Media Gateway Provisioning

Methodology:
1. VMG Provisioning
a. Link VMG to CS Domain (MG interface for ASPEN)
b. Link VMG to a UDP Port under the SG GIPS
2. VMG Provisioning for ALCAP (Iu cs to RNC)

a. Link VMG to CS MTP3-b application
3. VMG Provisioning for ASPEN (Interface to MG)

a. Link VMG to Media Gateway (VSP card) and TDM Ports
UM641 03.02/EN 7-35 July, 2003

One VMG for
STEP 1: VMG application Provisioning one RNC
VMG
UDP 12001
SG
Gips/2 UDP 12004 MTP3
(CS)
IpAddress/
MTP3
UDP 12002 (RNC)
Gips/2 Lp/2 VMG/20 SG/2

linkToLogicalProcessor lp/2 linkToLP LP/2 linkToLP LP/2
linkToProtocolPort v r/1 pp/gips2 linkToPort gips/2
Udp Port/12001
IpAddress/
10.60.11.34 CsDomain RncInterface
linkToVmg rncId 0
MgIf/0 MTP3Conn Vmg/20 rncAtmAddress 47111….
Udp
SCCPConn SCCPConn
Port/12001 Port/12002 Port/12004 Interface to WMG To MTP3 (RNC)

to SCCP to SCCP
(see 2nd next slide) (see next slide) (MSC) (RNC)
Step 1: VMG applications provisioning

VMG/ (VirtualMediaGateway) component:
The Virtual Media Gateway component represents a pool of Media Gateway
resources managed by a Signaling Gateway.
VMG/ attributes:
- linkToLogicalProcessor (lp): This attribute specifies the Logical Processor that
this component and its subcomponents are associated with.
- Vmg linkToPort (lToPort): This attribute specifies a link to a Gips IpAddress
Udp Port component. This determines the IP Address and UDP port that the
Media Gateways use to address this Virtual Media Gateway. The linkToPort
attribute must be set. Changing this value will cause all the Media Gateway
interfaces associated with this component to be restarted.
UM641 03.02/EN 7-36 July, 2003

STEP 2: VMG Provisioning:

Iu INTERFACE
VMG SG MTP3/20
(RNC)
VMG/20 SG/2 MTP3/20
linkToLogicalProcessor LP/2 origPointCode 0.45.6

linkToPort gips/2 mtpType mtp3b
IP/10.60.11.34 Udp Cs RncIf Ps
Port/12001
linkToCsDomain Sg/2 Cs
ServInd/12 LS/0 ServInd/3

Mtp3Conn
adjPointCode 0.0.3
linkToServiceIndicator
Mtp3/20 ServInd/12
Link/0
To SAAL-NNI GIPS/8 remoteUdpPort 12003
for RNC ATM signaling
MTP3/SAAL -NNI UDP Port : 12003 Signaling Gateway Configuration 7-37
Step 2: VMG Iu interface provisioning

VMG/ MTP3Connection component:
This component represents a connection to an MTP3 layer.
VMG/ MTP3Connection attribute:
• linkToServiceIndicator (lToSI): This attribute specifies a link to an Mtp3/n
ServiceIndicator/n component for MTP 3 services. Changing this attribute will
cause the application using the MTP3 layer’s services to be restarted.
UM641 03.02/EN 7-37 July, 2003

STEP 3: VMG Provisioning: RNC ATM Address = ATM @ of RNC

INTERFACE TO WMG Media Gateway name: Name of VSP (Shelf Type 5)
UDP MG ATM Address = ATM @ of VSP (Shelf Type 5)
VGCP 12001 MG IP Address = IP @ of VSP (Shelf Type 5) for signaling

VMG
(WMG)
Lp/2
VMG/20 SG/2
linkToLP LP/2 linkToLP LP/2
Mtp3Conn MgIf/0 CsDomain
mediaGatewayName mg1 linkToVmg Vmg/20
mgAtmAddress 47123….
to MTP3 to VSP for ASPEN
(RNC) mgIpAddress 10.0.180.240
mgUdpPort 12001
SCCPConn
AtmRsrc/6 Tdm /0 Tdm /1

bearerType speech bearerType data to SCCP
When bearerType is “speech ”, speech is tdmLpNumber 7 tdmLpNumber 7 (MSC)
supported at the following rates: 4.75 kbit/s; tdmPortNumber 1 tdmPortNumber 2
5.15 kbit/s; 5.9 kbit/s; 6.7 kbit/s; 7.4 kbit/s; timeSlots 1…….30 timeSlots 8 9 10 11 12 13 14
7.95 kbit/s; 10.2 kbit/s; 12.2 kbit/s; startingCic 1 startingCic 1
When bearerType is “data”, data is supported
at the following rates: 16 kbit/s; 64 kbit Signaling Gateway Configuration 7-38
Step 3: VMG WMG interface provisioning

VMG/ MgIf/ (MediaGatewayInterface) component:
This component represents an interface to a single Media Gateway controlled by
the VirtualMediaGateway/n component. The Media Gateway Interface manages
resources associated with the Media Gateway and initiates connection requests
and releases.
VMG/ MgIf/ attributes:
- mgAtmAddress (mgAtmAddr): This attribute specifies the ATM Address of the
Media Gateway associated with this component.
- mgIPAddr (ip): This attribute specifies the IP Address of the Media Gateway
associated with this component. This value must match the IP Address
specified by the attribute ipAddress provisioned in the Nsta Vgs Control
component. Changing the value of this attribute will cause outstanding
- mgUdpPort (port): This attribute specifies the UDP port of the Media Gateway
associated with this component. This value must match the UDP port specified
by the instance value of the Nsta Vgs Control UdpPort component associated
with the Media Gateway. Changing this value will cause outstanding
- mediaGatewayName (mgName): This attribute specifies the name of the
Media Gateway associated with this component. This value must be the same
as the value of the hostname attribute of the Nsta/n Vgs component
associated with the corresponding Media Gateway.
UM641 03.02/EN 7-38 July, 2003

Step 3: VMG WMG interface provisioning (continued)
VMG/ MgIf/ TDMResource/ component:
This component represents a TDM resource used by a Media Gateway, such as, an E1 span.
VMG/ MgIf/ TDMResource/ attributes:
- startingCic: this attribute provides a unique logical identifier for a particular E1 resource. The SS7
CICs associated with the DS0s managed by this resource are numbered beginning with the
startingCic value and ending with startingCic + 30, inclusive. The startingCic value for an E1
resource must not fall between the startingCic and startingCic+30 of any other E1 resource under
the same Virtual Media Gatway. If a CCS channel exists on the E1 resource, the DS0 for that
channel will be assigned a CIC, however this CIC will never be allocated for use by the Call
Server.
- tdmLpNumber (tdmLpNum): This attribute specifies the instance number of the Logical
Processor corresponding to the E1 card on the Media Gateway shelf, which communicates with
the Call Server. The combination of tdmLpNumber and tdmPortNumber must be unique across
all TdmResource subcomponents of an MgIf component.
- tdmPortNumber (tdmPortNum): This attribute specifies the E1 port number on the Logical
Processor specified by the attribute tdmLpNumber, corresponding to the E1 card on the Media
Gateway shelf, which communicates with the Call Server. The combination of tdmLpNumber and
tdmPortNumber must be unique across all TdmResource subcomponents of an MgIf component.
- bearerType: This attribute specifies the bearer type supported by this TdmResource component.
The value specified by the bearerRate attribute must correspond to a rate supported by the
bearer type specified.
- speech (Default value) - speech is supported at the following rates: 4.75 kbit/s, 5.15 kbit/s,
5.9 kbit/s, 6.7 kbit/s, 7.4 kbit/s, 7.95 kbit/s, 10.2 kbit/s, and 12.2 kbit/s
- data - data is supported at the following rates: 14.4 kbit/s and 64 kbit/s
- timeslots (ts): This attribute specifies the block of timeslots controlled by this TdmResource
component. There are 31 timeslots within an E1 span that can be controlled. One timeslot may
be reserved for signaling. More than one MgIf component can be created to utilize a single E1
span specified by the tdmLpNumber and tdmPortNumber attributes of a TdmResource
subcomponent. The timeslots attribute allows the operator to divide up the timeslots of a given
E1 span among multiple MgIf components. Two MgIf components cannot control the same
timeslot; so, the operator must ensure that no two MgIf components using the same VSP
resource specify any of the same values for this attribute. If more than one TdmResource
component specifies the same timeslots, an alarm is generated when the components are
activated, and only one of the TdmResource components is enabled. By default, this attribute
specifies 30 timeslots omitting timeslot 31 for signalling. If a VSP is controlled by two different
MgIf components, this attribute must be set to specify only the timeslots that this MgIf controls.
There may be no more than one timeslot omitted from the sequence of timeslots specified by this
attribute. The timeslot blocks (1,2,3,4) and (1,2,3,5) are valid, but the timeslot block (1,2,4,6) is
not valid because two timeslots are omitted from the sequence. The omitted timeslot must be
used for signalling and cannot be specified by the timeslots attribute of another TdmResource
component using this span. The Brag associated with this VSP resource must have an Mtp2
subcomponent with an instance value equal to the number of the omitted timeslot. Not every E1
span uses a timeslot for signalling. If the Brag component associated with the span represented
by this TdmResource does not have an Mtp2 subcomponent, there is no need to omit a timeslot
on any of the TdmResource components that divide up this span.
UM641 03.02/EN 7-39 July, 2003

Student notes
UM641 03.02/EN 7-40 July, 2003

SAAL-NNI/ATM Provisioning
UM641 03.02/EN 7-41 July, 2003

SAAL-NNI GIPS provisioning

I/O
SG
SAAL -NNI
NAP PS CS VMG
To SG
(GIPS 2) RANAP Q.2630.1 RANAP-CS
UDP
12003 SCCP Q.2150.1 ASPEN SCCP
VR/1
Gips/8 MTP3-B MTP3
IP
SAAL-NNI GIPS 8
Iu
AtmIf/ AAL5
NEP NEP
AtmMpe/ ATM
Sdh/0
SG OC3 card
CS Signaling Signaling
VCC/ VCC/ I/O OC3 card (A)
to AN
UM641 03.02/EN 7-42 July, 2003

ATM and IP configuration for CS signaling

RNC Iu AtmIf/20 AN SAAL-NNI
Vcc/0.46 (control) Vcc/
(control) UDP
AAL5
12003 VR/1
VR/1
10.60.11.14 GIPS/8
10.0.180.1
AtmIf/80 ATM
AtmIf/41 AtmIf/41
Vcc/3.120
(CS CP: MTP2) Vcc/1.200
VSP Vcc/1.400
10.0.180.240 (CS CP: MTP2) (CS CP RNC)
SAAL-NNI
AtmIf/80 NAP
SG UDP 12003
VR/1
10.60.11.13 Gips/8
WMG IP
VR/1
CS & PS control
10.60.11.32/30 10.60.11.128/30 VCC/1.200
A
NEP t
GIPS 2 GIPS 8 m
NEP I AtmMpe/
SG SAAL- CS control f
NNI VCC/1.400 Signaling Gateway Configuration 7-43
UM641 03.02/EN 7-43 July, 2003

SAAL-NNI Provisioning Methodology:

1. SAAL-NNI Application Provisioning
b. Provision the GIPS (IP @ on the private subnet) for SAAL-NNI application
d. Provision SAAL-NNI: link it to UDP Ports and route to SG (MTP3) application
e. Provision SAAL-NNI: Link to VCC to AN
2. IP/ATM VCC to AN Provisioning (ATMMPE)

c. Create an PP/ and its IP address for each Ip interface on the Virtual router
(VR)
d. Create an ATMMPE/ (RFC 1483) and link it to its PP/ (IP) and its VCC (ATM)
UM641 03.02/EN 7-44 July, 2003

SAAL-NNI Provisioning : GIPS 8

VR/1 SAAL-NNI AtmIf/80
PP/gips8 UDP 12003 Signaling
Gips/8 VCC/1.200
Saal-Nni NAP NEP
IpAddress/
To AN
vr/1 Gips/8 Lp/8 SaalNni/80 AtmIf/80
linkToLogicalProcessor lp/8 linkToLogical Processor lp/8

linkToProtocolPort v r/1 pp/gips8 linkToPort gips/8
IpAddress/10.60.11.130
pp/gips8 udp port/12003
IpAddress/ layer3IpAddress 10.60.11.34
Vcc/1.200
10.60.11.130
layer3Port 12002
ipport
Udp
Nap Nep
IpLogicalInterface / atmConnection Atm/80 Vcc/1.200 Nep

10.60.11.129 Port/12003
NetMask 255.255.255.252 ATM connection to
ATM VCC Nailed -Up-End-Point
BroadcastAddress 10.60.11.131 for Control Plane
To SG GIPS/2 for
RNC MTP3 signaling
(UDP 12002) SAAL-NNI/ATM
UM641 03.02/EN 7-45 July, 2003

ATM VCC to AN Saal-Nni NAP
A NEP
t to AN VCC 1.200
m
VR/1 I (Control Plane)
f
/ NEP
8 Sdh port
0
to AN VCC 1.400
(CS Control Plane)
Root (CAS)
VR/1 AtmMpe /80 AtmIf/80 LAPS/8

interfaceName LAPS/8 Vc4/0
linkToProtocolPort
ProtocolPort/AN VR/1 PP/AN
ipPort AtmConnection/1 Vcc/1.400 Vc4/0

Vcc/1.200
atmConnection AtmIf/80
ipLogicalInterface / Vcc/0.30 Nep
10.60.11.13 Nep Nep ATM connection to

ATM SAAL-NNI
Nailedup -Adaptation-
Point for Control Plane
UM641 03.02/EN 7-46 July, 2003

Student notes
UM641 03.02/EN 7-47 July, 2003

Student notes
UM641 03.02/EN 7-48 July, 2003

Aggregation Node Configuration
Section 8
Wireless Gateway ATM configuration
UM641 03.02/EN 8-1 July, 2003

Objectives
• Describe IP routing in Wireless Gateway

• Describe ATM switching in Wireless Gateway
• Configure the Wireless Gateway external interfaces (Iu and Gn)
• Configure the Wireless Gateway inter-shelf communication
• Configure Wireless Gateway internal and external routing
Aggregation Node Configuration 8-2
UM641 03.02/EN 8-2 July, 2003

Contents
• Aggregation Node Configuration Overview
• AN external interfaces Provisioning (PVC)
• AN inter-shelves interfaces Provisioning (PVC and SVC)
UM641 03.02/EN 8-3 July, 2003

Student notes
UM641 03.02/EN 8-4 July, 2003

Aggregation Node
configuration overview
UM641 03.02/EN 8-5 July, 2003

Aggregation Node Functions

A-law/E1
3G SGSN WMG MSC

SS7/E1
IP (GTP-C)/ATM Voice (AMR)/ATM
IP (GTP-U)/ATM RANAP/SS7/IP/ATM
Voice (AMR)/ATM IP (GTP-U)/ATM

IP (GTP-U)/ATM
RNC Aggregation GGSN
Node (AN)
IP (GTP-C)/ATM
RANAP/SS7/ATM
IP/ATM CS UP
(to/from SGSN RANAP/SS7/SAAL -NNIATM
and WMG) (to/from RNC) CS CP
PS UP
PS CP
SG
Aggregation Node Functions

This slide represents the ways used by signaling and data or voice traffic through the
Wireless Gateway.
As an exercise, you can draw by yourself the ways used for:
- Circuit Switched User Plane (voice or data) traffic
- Circuit Switched Control Plane (RANAP or ALCAP/ASPEN) traffic
- Packet Switched User Plane (subscriber IP PDU) traffic
- Packet Switched Control Plane (RANAP or Core Network signaling protocols) traffic
UM641 03.02/EN 8-6 July, 2003

VCC on Iu
PS CP (MTP3) VCC: 2 to 16 VCC (rtVBR)
CS CP (MTP3) VCC: 2 to 16 VCC (rtVBR)
RNC: WG:
PS UP (GTP-U) VCC: 4 VCC: IP CoS 3 (VCC CBR)
Interface Aggregation
IP CoS 1 (VCC CBR/rtVBR)
Node (IN) Node (AN)
IP CoS 1 (VCC nrtVBR)
IP CoS 0 (VCC UBR)
CS UP (AMR Voice) VCC: 4 to 248 VCC (CBR AAL2)
Packet Switched Control Plane

Circuit Switched Control Plane
Packet Switched User Plane
Circuit Switched User Plane
VCC on lu
Between 1 WG and 1 GGSN, VCCs are:
• signaling VCCs:
• For Packet Switched:
- AAL5 VCCs carrying RANAP/SCCP (up to 16, RNC limitation): QoS VBR
• For Circuit Switched:
- AAL5 VCCs carrying RANAP/SCCP (up to 16, RNC limitation ): QoS VBR
The sum of VCC signaling is limited to 16 (TMU cards limtation in the RNC)
• voice/data VCCs:
- AAL5 VCCs carrying subscriber IP PDU (CoS 3): QoS CBR
- AAL5 VCCs carrying subscriber IP PDU (CoS 1): QoS VBR
- AAL5 VCCs carrying subscriber IP PDU (CoS 0): QoS UBR
- AAL2 VCCs carrying AMR voice (from 4 up to 248): QoS rtVBR
The minimum of AAL2 VCC for voice/data is 4 (2 per VSP card, 2 VSP cards
minimum for 1 RNC)
UM641 03.02/EN 8-7 July, 2003

VCC on Gn
PS CP (GTP-C) VCC: 1 VCC: IP CoS 3 (CBR)
WG: PS UP (GTP-U) VCC: 4 VCC: IP CoS 3 (VCC CBR)

Aggregation GGSN
IP CoS 1 (VCC CBR/rtVBR)
Node (AN)
IP CoS 1 (VCC nrtVBR)
IP CoS 0 (VCC UBR)
Packet Switched Control Plane

Packet Switched User Plane
VCC on Gn
Between 1 RNC and its WG, VCCs are:
• signaling VCCs:
- AAL5 VCCs carrying GTP-C (CoS 3): QoS CBR or VBR
• data VCCs:
- AAL5 VCCs carrying subscriber IP PDU (CoS 2): QoS CBR or VBR
UM641 03.02/EN 8-8 July, 2003

WG internal VCC
U-SGSN 1 WMG 1
PS CP VCC
2 CS UP VCC 1 CS CP VCC
4 VCC for PS UP per VSP per VSP
16 CS CP VCC
per SG
Aggregation Node (AN) SG
Iu
16 PS CP VCC
per SG
4 VCC for PS UP 2 CS UP VCC 1 CS CP VCC

per VSP per VSP
PS CP VCC
U-SGSN 2 WMG 2 Gn
WG Internal VCC
Internal WG VCCs are:
• signaling VCCs (to/from SG):
- AAL5 VCCs carrying RANAP/SCCP (up to 16, RNC limitation ): QoS VBR
The sum of VCC signaling is limited to 16 (TMU cards limitation in the RNC)
• voice/data VCCs:
• For Packet Switched (to/from U-SGSN):
• For Circuit Switched (to/from WMG):
- AAL2 VCCs carrying AMR voice (from 4 up to 248): QoS rtVBR
The minimum of AAL2 VCC for voice/data is 4 (2 per VSP card, 2 VSP cards
minimum for 1 RNC)
UM641 03.02/EN 8-9 July, 2003

WG IP Routing configuration
AN
RNC 172.253.3.3 33.33.33.41 GGSN
Iu
VR/4 VR/3 Gn
IP/ATM IP/ATM
1 10.60.10.226 10.60.10.222
0
. 10.60.11.14
6
SG 10.60.11.13 0
. VR/1
1
1 C
VR/1 . 10.0.180.1 o
1
2
10.60.11.32/30 10.60.11.128/30 \ r
3
0 Inter -shelf Inter -shelf e
GIPS SG GIPS IO 10.60.10.224/30 10.60.10.220/30
SAAL- N
SG
NNI IP/ATM IP/ATM e
SG card (slot 2) I/O card (slot 8) t
Inter -shelf Inter -shelf U-SGSN w
10.60.10.225 10.60.10.221 o
10.0.180.0\24
47.104.194.80 r
VR/4 VR/3 k
WMG
10.60.222.200/30 10.60.11.112/30 10.60.10.128/30
GIPS GIPS
VSP USD_Iu USD_Gn GIPS USC IP/ETH
10.0.180.240 USD USD USC

USD card (slot 2) USC card (slot 10)
WG IP Routing Configuration
This example of IP routing configuration illustrates the communication between Virtual
Routers in WG.
In this example,
• VR/1 is used in AN and SG (Shelf Type 6) to route CS signaling (ASPEN and
MTP2)
• VR/3 is used in AN and U-SGSN (Shelf Type 1) to route GTP-U and GTP-C
traffic to/from one GGSN
• VR/4 is used in AN and U-SGSN (Shelf Type 1) to route GTP-U traffic to/from
one RNC
UM641 03.02/EN 8-10 July, 2003

WG ATM and IP configuration

PS UP Vcc/0.100 (UBR) AtmIf/20
RNC AN Vcc/1.32
PS UP Vcc/0.101 (nrt-VBR)
172.253.3.3 33.33.33.41 Vcc/1.33
Iu PS CP Vcc/0.32 (rt-VBR)
VR/4 VR/3 AtmIf/22
Vcc/1.34
CS CP Vcc/0.46 (rt-VBR) Vcc/1.35
10.60.10.226 10.60.10.222
CS UP Vcc/0.105 (rt-VBR) Gn GGSN
10.0.180.1
VR/1
Vcc/3.120 10.60.11.14
(rt-VBR)
AtmIf/80
WMG
Vcc/2.160
(rt-VBR) AtmIf/41 AtmIf/40
VSP Vcc/1.40 (nrt-VBR) Vcc/1.32 (UBR)
10.0.180.240 CS CP CS CP Vcc/1.33 (nrt-VBR)
Vcc/1.400 Vcc/1.39 (UBR)
Vcc/1.200 Vcc/1.34 (rt-VBR)
(rt-VBR) (rt-VBR)
Vcc/1.35 (rt-VBR)
AtmIf/80 U-SGSN
AtmIf/80 10.60.10.225 10.60.10.221
SG 10.60.11.13
PS CP 47.104.194.80
VR/1 Vcc/1.205 VR/4 VR/3
(rt-VBR)
10.60.11.32/30 10.60.11.128/30 10.60.222.200/30 10.60.11.112/30 10.60.10.128/30
GIPS SG GIPS GIPS

GIPS IO GIPS USC IP/ETH
USD_Iu USD_Gn
SG SAAL- USD USC
NNI USD
SG card (slot 2) I/O card (slot 8) Aggregation Node Configuration
USC card (slot 10) 8-11
USD card (slot 2)
ATM and IP Configuration

routing between shelves in WG.
• for Circuit Switched Control Plane:
• IP routing: SG (Shelf Type 6) communicates to WMG (Shelf Type 5) through AN
and VR/1 (VCC/1.400 between SG and AN; VCC/2.160 between AN and WMG)
• for Packet Switched Control Plane:
(VCC/1.205 for PS CP in this example)
• ATM switching: SG communicates to U-SGSN (Shelf Type 1) through the AN
by SVC (not shown in this picture)
• for Circuit Switched User Plane:
• ATM switching: RNC communicates to WMG (Shelf Type 5) through the AN
(VCC/0.105 between AN and RNC in this example; VCC/3.120 between WMG
and AN)
• for Packet Switched User Plane:
• IP switching: RNC communicates to U-SGSN (Shelf Type 1) through the AN
and VR/4 (VCC/0.100 and VCC/0.101 for PS CP in this example)
• IP switching: U-SGSN (Shelf Type 1) communicates GGSN through the AN and
VR/3 (VCC/1.32, VCC/1.33, VCC/1.34, VCC/1.35 for PS CP in this e xample)
UM641 03.02/EN 8-11 July, 2003

Student notes
UM641 03.02/EN 8-12 July, 2003

AN interfaces provisioning (PVC)
UM641 03.02/EN 8-13 July, 2003

I/O card provisioning methodology (1)

a. Create SDH/ Optical Ports under each I/O card Logical Processor
b. Create a LAPS/ and link it to its working and its protected optical ports
3. IP Provisioning

3. IP Provisioning
UM641 03.02/EN 8-14 July, 2003

Physical (Optical) Ports Provisioning:

Automatic Protection Switching (APS)
I/O (slot 8) I/O (slot 9)
SDH/0 SDH/0
SDH/1 SDH/1
SDH/2 SDH/2
SDH/3 SDH/3
LP/8 LAPS/80 LP/9 AtmIf/80
clockingSource module workingLine LP/8 Sdh/0 clockingSource module

Sdh/0 Sdh/0
LineAutomaticProtectionSwitching LAPS/80 LineAutomaticProtectionSwitching LAPS/80
Vc4/0
Vc4/0 applicationFramerName ATMIF/80 Vc4/0
STEP 1: Physical Ports Provisioning

Configuration of Optical Ports consists of:
• declaration of physical ports under the LP/ of the card: SDH/ component
• declaration of a VC4 optical frame under the SDH/ component: VC4/ component
Configuration of APS (Automatic Protection Switching) consists of:

• declaration of physical ports under the LP/ of 2 optical cards
• declaration of the LAPS/ component which is linked to 2 SDH/ components
under 2 different LP/
• The link between the Layer 1 and Layer 2 is mad by the
applicationFramerName attribute under the LAPS/ VC4/ component.
UM641 03.02/EN 8-15 July, 2003


OK

c. Declare the VCC as a NEP (Nailed-up End Point) or NRP (Nailed-up Relay Point)
d. Activate PNNI and declare the ATM prefix and ESI addresses (NSAP addresses)

3. IP Provisioning
UM641 03.02/EN 8-16 July, 2003

ATM interface to AN
Layer 1 Layer 2
Physical port ATM

(Virtual Channels)
Sdh port
LAPS/80 AtmIf/80
workingLine LP/8 Sdh/0 interfaceName LAPS/8 Vc4/0

Vcc/0.40 Vcc/1.200
Vc4/0
NRP OR NEP RP EP
OR
Nailed-up Nailed-up Relay Point End Point
Relay Point End Point
STEP 2: ATM interface and VCC Provisioning

The ATMIF/ component refers to an ATM physical interface (one ATMIF/ component
per optical port on the card).
The Vcc (ATM Virtual Channel Connection) can be provisioned (PVC or static Vcc) or
can appear dynamically (SVC or dynamic Vcc).
Static Vcc must be configured (VCC/ component) at each ATM interface (end point
or relay point) of the physical link. VCC/ are configured under the ATMIF/ component.
Dynamic Vcc appear dynamically and don’t have to be provisioned.
At the ATMIF /, the VCC is terminated by an End Point, or relayed to another interface
(another ATMIF/ by a Relay Point). The end point can be:
• Nailed-Up End Point for PVC
• Nailed-Up Relay Point for PVC
• End Point for SVC
• Relay Point for SVC
UM641 03.02/EN 8-17 July, 2003

NRP ATM connection for Signaling VCC:

Example of Relay between SG and RNC
Layer 1 Layer 2 Layer 1
ATM
2 (Virtual Channels) 4
to RNC to SG
Sdh/0 Vcc/0.46 Vcc/1.200 Sdh/1
NRP NRP
LAPS/20 AtmIf/20 AtmIf/41 LAPS/41

workingLine LP/8 Sdh/0 interfaceName interfaceName
protectionLine LP/9 Sdh/0 LAPS/20 Vc4/0 LAPS/41 Vc4/0
Vcc/0.46 Vcc/1.200
Vc4/0 Vc4/0
Nrp Nrp
nextHop nextHop
AtmIf /41 vcc /1.200 Nrp AtmIf /20 vcc /0.46 Nrp
Relay between SG and RNC

In case of static relay from one Passport interface to another one (PVC to PVC), the
nextHop attribute has to be provisioned under the NRP component of every VCC/.
This nextHop attribute is a pointer to another component and its value refers to the
NRP component of the relayed Vcc.
UM641 03.02/EN 8-18 July, 2003


OK
OK
a. Create an PP/ and its IP address for each Ip interface on the Virtual router (VR)
b. Create an ATMMPE/ (RFC 1483) and link it to its PP/ (IP) and its VCC (ATM)
c. IP routing (1): Activate OSPF on all IP interfaces and on the Virtual Router (VR)
d. IP routing (2): Create eventually static routes

3. IP Provisioning
UM641 03.02/EN 8-19 July, 2003

Step 3: IP/ATM Provisioning:

Example for Iu interface: ARP
VR/4 ATMMPE/20 AtmIf/20
linkToProtocolPort VR/4 PP/IUUP interfaceName LP/2 Sdh/0 Vc4/0
IP PP/IUUP
To SDH/
Vcc/0.100
ARP ipPort
AtmConnection/41 Nep
atmConnection AtmIf/20 Vcc/0.100 Nep

Host/172.253.3.2
physAddress 00-00- 00-00-0 0-00 172.253.3.1
PVCNumber 41
netmask 255.255.255.252
broadcastAddress 172.253.3.3
STEP 3: IP over ATM Provisioning

An IP/ATM interface provisioning consists of provisioning:
• IP layer (layer 3): one ProtocolPort/ component and its IP address
(IpLogicalInterfacecomponent/)
• ATMMPE layer (layer 2.5): one ATMMPE/ component that will be able to
encapsulate the IP packet. Its subcomponent (ATmConnection/) permits to put
the IP packet into one or many Vcc (atmConnection attribute that is pointer to a
VCC/ Nep component).
• ATM layer (layer 2): one VCC/ component terminated by a NEP
ATMMPE component:
it represents a logical interface between the virtual router and an ATM media (ATMif).
Multiprotocol encapsulation as specified in RFC 1483 is used to transfer higher-layer
protocol data across virtual channels in an ATM network. The AtmMpe component
provides a means to associate multiple ATM virtual channel connections with a single
ProtocolPort through a linkage attribute abd with virtuak channel connections through
a linkage attribute in each AtmConnection subcomponent.
Encap Type: this attribute specifies the RFC 1483 encapsulation type to be used for
the AtmConnection component under this AtmMpe component. Specifying llcEncap
allows multiplexing of multiple protocols over the VCCs. The protocol of the carried
PDU will be identified by an IEEE 802.2 LLC heade. If bridging or inverse ARP is to
be carried over a VCC, llcEncap must be used. Specifying ipVcEncap or ipxVcEncap
indicates that all the VCCs (that is, AtmConnection components) under an AtmMpe
component use VC-based multiplexing and carry IP PDUs only.
UM641 03.02/EN 8-20 July, 2003

Step 3: AN Virtual Router Provisioning:

Example of VR/3 (Gn interface)
ATMMPE/40
d ATMMPE/42 VR/3 ATMMPE/22
to AtmIf/22
to AtmIf/40 to LP/2 Sdh/2
PP/SHELF2 PP/SHELF1 PP/GGSN
to LP/4 Sdh/0 to GGSN
linkToMedia atmMpe/42 linkToMedia atmMpe/40 linkToMedia atmMpe/22
to U-SGSN1
to AtmIf/42 ipPort ipPort ipPort

to LP/4 Sdh/2
to U-SGSN2
ipLogicalInterface / ipLogicalInterface / ipLogicalInterface /
10.60.13.222 10.60.10.222 33.33.33.41
netmask 255.255.255.252 netmask 255.255.255.252 netmask 255.255.255.252

broadcastAddress 10.60.13.223 broadcastAddress 10.60.10.223 broadcastAddress 33.33.33.43
OSPFIF OSPFIF OSPFIF

Virtual Routing
Virtual Routing has the same features than classic routing: each Virtual Router (VR/
component) has many interfaces (ProtocolPort/ component) than are identified by
an IP address (IpLogicalInterface/ component).
This is an example that illustrates the IP routing between one GGSN (PP/GGSN
component) and 2 U-SGSN shelves (PP/SHELF1 and PP/SHELF2).
UM641 03.02/EN 8-21 July, 2003

Step 3.c: IP routing (1)

OSPF (Gn Virtual Router)
VR/3
IP
ProtocolPort/GGSN
OSPF
ipPort
Area/1.1.1.1 Export/1 ipLogicalInterface /33.33.33.41

OSPFInterface
areaId 1.1.1.1
Create an OSPFInterface component

under every OSPF IP interface
OSPF Routing
OSPF routing is declared by:
• provisioning an OSPF component under the VR/ IP component
• provisioning an OSPFIF component under each Virtual Router Protocol Port
interface
UM641 03.02/EN 8-22 July, 2003

Step 3.d: IP routing (2)

IP Static route (from AN to SG GIPS for VR/1)
AN SG
VR/1 (AN) VR/1 (SG) GIPS SG SG
PP/ PP/AN 10.60.11.128/30
VSP1 PP/SHELF_SG 10.60.11.13
10.60.11.14 10.60.11.32/30
GIPS IO
SAAL-
NNI
Vr/1
PP/SHELF_SG ip
SG GIPS
ipPort static subnets
ipLogicalinterface /10.60.11.14 Route/10.60.11.128,255.255.255.252,0
NetMask 255.255.255.252
BroadcastAddress 10.60.11.15 NextHop/10.60.11.13
inter-shelf
interface on SG Aggregation Node Configuration 8-23
IP Static Routing
Static route definition allows the definition of explicit routes to remote IP networks or
hosts. The definition includes a destination address, address mask, and one or more
next hop addresses (gateways). Multiple static routes may be defined and can be used
in a load sharing mode.
Passport static provisioning also provides a mechanism to statically define routes that
will not receive packets through IP. Static route provisioning allows the operator to
specify that packets addressed to a specified host or route be discarded.
This example illustrates the IP routing between a VSP card (WMG) and its SG
application. On the AN, a static route has to be provisioned to reach the SG GIPS
(where runs the SG application).
UM641 03.02/EN 8-23 July, 2003

Student notes
UM641 03.02/EN 8-24 July, 2003

AN interfaces provisioning (SVC)
UM641 03.02/EN 8-25 July, 2003

Nodal Management:
Master/Slave configuration
MASTER SLAVE 1
ATM EP
USGSN1 Connection
(End Point) USGSN2
Slave/1 AtmIf/80
AtmIf/80
Connection
Slave/3 Connection
Master
Connection
Slave/2
AtmIf/20 AtmIf/22
nodePrefix: 4500003490170118 0F00000000
nodePrefix: 4500003490170118 1F00000000
atmLocalEsi : 00003110000000 atmLocalEsi : 00003111000000
ATM RP
(Relay Point)
WMG- AtmIf/80 WMG-

AtmIf/80 AtmIf/21 AN AtmIf/23
SG 1 SG 2
Connection Connection
Master Master
ATM EP
(End Point)
nodePrefix: 4500003490170118 2F00000000 nodePrefix: 4500003490170118 3F00000000

atmLocalEsi : 00003112000000 SLAVE 2 SLAVE 3 atmLocalEsi : 00003113000000
Nodal Management
The nodal manager feature is used to facilitate the communication of various applications
within the 3G-SGSN. These applications include among others:
• the signaling gateway
• the UMTS subscriber control-plane
• the UMTS subscriber data layer
• the domain name server agent
The nodal manager feature (NMF) allows the applications to register themselves by
indication their location within the multishelf SGSN system.
The NMF maintains information about the status and location of each application and
facilitates inter-application communication by helping applications determine the location of
other applications with which they must communicate.
The nodal manager feature consists of two parts, the nodal manager: residing on the CP
and the nodal manager agent residing on the functional processor cards.
One nodal manager is created for each shelf. One of the nodal managers will act as a
"master" and the nodal managers on other shelves will be "slaves".
The master nodal manager maintains information about the applications running on its shelf,
and receives messages from slave nodal managers about the applications running on their
shelves. The master nodal manager sends messages to all slave nodal managers to inform
them of applications running on other shelves. The nodal manager agent provides multishelf
functionality by setting up and maintaining SVC connections between applications that are
interested in one another.
The intershelf communication between the following applications is done through SVCs:
• SG and USC
• USC and USD
UM641 03.02/EN 8-26 July, 2003

Master/Slave configuration:
MASTER side
Usgsn
ModuleData
nodeName USGSN1
nodeId 301
nodePrefix 45000034901701180F00000000 Shelf
atmLocalEsi 00003110000000
Node Prefix + ATM Local ESI = ATM @ (master shelf: U-SGSN1)
ConnectionToSlave /1 ConnectionToSlave /2
slaveAddress 45000034901701181F0000000000003111000000 slaveAddress 45000034901701182F0000000000003112000000
Node Prefix ATM local ESI Node Prefix ATM local ESI
Slave Addresses = ATM @ (other shelves: U-SGSN, SG, WMG)
Master/ Side
The dynamic SVC creation needs at first to provision the Nodal Management
feature:
• at master side, all the slaves have to be known by the master. Slaves and
Master are identified by their ATM NSAP address.
An ATM NSAP address is the sum of the node prefix (identifier of the node or the
shelf itself) and the ATM local ESI (identifier of a specific ATM interface for this
node).
PNNI has to be configured under each ATMIF/ component and under the ARTG
component in order to create dynamically the ATM SVC.
To set up PNNI, please refer to another Passport course:

Course Number: 3288
Course Title: Passport Carrier ATM (4 days)
UM641 03.02/EN 8-27 July, 2003

SLAVE side
ModuleData Usgsn
nodeName USGSN2
nodeId 302
nodePrefix 45000034901701181F00000000 Shelf
atmLocalEsi 00003111000000
Node Prefix + ATM Local ESI = ATM @ (slave shelf: U-SGSN2)
ConnectionToMaster
masterAddress 45000034901701180F0000000000003110000000
Node Prefix ATM local ESI
Slave Addresses = ATM @ (other shelves: U-SGSN, SG, WMG)

Slave Side
At slave side, the slave shelf has to know who is its master: this provisioned under
the Usgsn Shelf ConnectionToMaster component.
The masterAddress attribute refers to the Master ATM NSAP address.
PNNI has to be configured under each ATMIF/ component and under the ARTG
component in order to create dynamically the ATM SVC.
UM641 03.02/EN 8-28 July, 2003

SVC Creation between Master and Slave
MASTER SLAVE
Usgsn AtmIf/80 Usgsn

AtmIf/80
Shelf Shelf
Vcc/0.600 Vcc/0.678
atmLocalEsi 00003110000000 atmLocalEsi 00003111000000
ConnectionToSlave /1 Ep Ep ConnectionToMaster
slaveAddress 45000034901701181… nextHop Usgsn nextHop Usgsn masterAddress 45000034901701180…
Shelf ConSlave/1 Shelf ConMaster
AtmConnection AtmConnection
SVC Creation between Master and Slave

When SVC is established between the master shelf and its slaves, shelves can
know the running applications of each other.
In terms of CAS components,
At Master side,
• an AtmConnection component appears dynamically under the USGSN SHELF
CONNECTIONTOSLAVE/ component.
• a VCC/ EP components will appear dynamically under one ATMIF/ supporting
PNNI. AtmConnection and VCC/ EP are linked by the nextHop attribute under
VCC/ EP component and by the AtmConnection attribute under the
AtmConnection component.
At Slave side,
• an AtmConnection component appears dynamically under the USGSN SHELF
CONNECTIONTOMASTER component.
UM641 03.02/EN 8-29 July, 2003

SVC Creation through Aggregation Node
Vcc/0.600 Vcc/0.678
EP RP RP EP
MASTER AN SLAVE
AtmIf/80 AtmIf/20 AtmIf/22 AtmIf/80
Vcc/0.600 Vcc/0.600 Vcc/0.678 Vcc/0.678
Ep Rp Rp Ep
nextHop Usgsn nextHop AtmIf/22 nextHop AtmIf/20 nextHop Usgsn
Shelf ConSlave/1 vcc/0.678 Rp vcc/0.600 Rp Shelf ConMaster

SVC between master and Slaves shelves are established through the Aggregation
Node.
This one has to create dynamically the VCC/ and the RelayPoint components to
switch the traffic between the master and the slave shelves.
UM641 03.02/EN 8-30 July, 2003

SG and USC communication

MASTER ATM EP SLAVE 1
(End Point)
USGSN1 USGSN2
USC,0,10 AtmIf/80 USC,1,10
AtmIf/80
USD,0,2 USD,1,2
MAP,0,12 MAP,1,12
AtmIf/20 AtmIf/22
ATM RP ATM RP
(Relay Point) (Relay Point)
WMG- AtmIf/21 AN AtmIf/23

WMG-
SG 1 SG 2
SG,2,3
SG,3,3
AtmIf/80
AtmIf/80
ATM EP
(End Point)
SLAVE 2 SLAVE 3
SG and USC Communication

Master and Slaves communicate their application through the Nodal Management
SVC.
Now they can create some new SVC to in order that their application can talk
together.
In this example, USC application needs to talk to 2 SG applications in 2 other

shelves.
UM641 03.02/EN 8-31 July, 2003

SG and USC communication:

SVC Creation between USC and SG Applications
USGSN SG
USC/10 AtmIf/80 SG/3

AtmIf/80
PS
Vcc/0.682 Vcc/0.605
RaConn/SG,2,3 Ep Ep RaConn/USC,0,10
nextHop USC/10 nextHop SG/3 PS
RaConn/SG,2,3 RaConn/USC,0,10
RaConn = Remote Application Connection
CAS Components
In terms of CAS components,
• an RemoteApplicationConnection/ AtmConnection component appears
dynamically under the local application (USC/10 at the USGSN side and SG/3
at the SG side in this example). The instances of the
RemoteApplicationConnection component corresponds to:
- Name of the remote application
- Shelf Id (O for the Master, 1 for Slave/1, etc.)
- Remote application instance number
UM641 03.02/EN 8-32 July, 2003

SG and USC communication:

Vcc/0.600 Vcc/0.605
EP RP RP EP
MASTER AN SLAVE
AtmIf/80 AtmIf/20 AtmIf/22 AtmIf/80
Vcc/0.682 Vcc/0.682 Vcc/0.605 Vcc/0.605
Ep Rp Rp Ep
nextHop USC/10 nextHop AtmIf/22 nextHop AtmIf/20 nextHop SG/3 PS
RqConn/SG,2,3 vcc/0.605 Rp vcc/0.682 Rp RaConn/USC,0,10
SVC between Inter-Shelves

SVC between inter-shelves applications are established through the Aggregation
Node.
switch the traffic between the shelves.
UM641 03.02/EN 8-33 July, 2003

USC, USD and MAP communication

MASTER ATM EP SLAVE 1
(End Point)
USGSN1 USGSN2
USC,0,10 AtmIf/80 USC,1,10
AtmIf/80
USD,0,2 USD,1,2
MAP,0,12 MAP,1,12
AtmIf/20 AtmIf/22
ATM RP ATM RP
(Relay Point) (Relay Point)
WMG- AtmIf/21 AN AtmIf/23

WMG-
SG 1 SG 2
SG,2,3
SG,3,3
AtmIf/80
AtmIf/80
ATM EP
(End Point)
SLAVE 3
SLAVE 2
USC Card
USC card is also able to talk with:
• USC application in another U-SGSN shelf
• USD application in another U-SGSN shelf
• MAP application in another U-SGSN shelf
• SAS application in another U-SGSN shelf
• LI application in another U-SGSN shelf
In this example, USC application needs to talk to USC, USD and MAP applications
in an other shelf.
UM641 03.02/EN 8-34 July, 2003

USD and USC communication:

SVC Creation between USC and USD Applications
USGSN1 USGSN2
USC/10 AtmIf/80 USD/2

AtmIf/80
Vcc/0.352 Vcc/0.76
RaConn/USD,1,2 Ep Ep RaConn/USC,0,10
nextHop USC/10 nextHop USD/2
RaConn/USD,1,2 RaConn/USC,0,10
RaConn = Remote Application Connection
SVC between Inter-Shelves

SVC between inter-shelves applications are established through the Aggregation
Node.
switch the traffic between the shelves.
UM641 03.02/EN 8-35 July, 2003

Student notes
UM641 03.02/EN 8-36 July, 2003

WG Integration and Troubleshooting
Section 9
UM641 03.02/EN 9-1 July, 2003

Objectives
• Integrate a Wireless Gateway

• Describe the origin of Wireless Gateway alarms
• Interpret some Wireless Gateway alarms
WG Integration and Troubleshooting 9-2
UM641 03.02/EN 9-2 July, 2003

Content
Passport OSI States/Status
Passport Alarms/SCNs
Wireless Gateway Troubleshooting Methodology
UM641 03.02/EN 9-3 July, 2003

Student notes
UM641 03.02/EN 9-4 July, 2003

Passport components state

description
Attributes Values
Operational state enabled, disabled
OSI State Usage state idle, active, busy
Administrative state unlocked, locked, shutting down

empty, under repair, critical, major, minor, alarm,
Alarm status
outstanding
empty, initialization required, not initialized,
Procedural status
initializing, reporting, terminating
empty, in text, failed, power off, off line, off duty,
Availability status
dependency, degraded, not installed, log full
OSI Status
empty, subject to test, part of services locked,
Control status
reserved for test, suspended.
not set, hot standby, cold standby, providing
Standby status
Service
Unknown status true or false
Open Systems Interconnection States

Displaying the Open Systems Interconnection (OSI) states of components can be a
start to determining the cause of the problem. Combination of state values indicate
certain conditions. Understanding the meaning of a particular state combination can
be very helpful when troubleshooting.
Refer to the following NTPs in order state combination tables for base system
components :
• NTP, 241-5701-605, Passport 7400, 8700, 15000 Operation and Maintenance
Guide, (Appendix OSI states)
• NTP, 241-7401-610, Passport 7400, 15000 FP Configuration and Testing
Guide,
UM641 03.02/EN 9-5 July, 2003

WG components state : example

Root (CAS)
IP Layer VR/2
AdminState Unlocked
OperationalState Enable
usageState busy
ProtocolPort/IUUP
AdminState Unlocked
usageState busy
ipPort
AdminState Unlocked
usageState busy
10.6.20.130
OSI states and status on a component relating to a

protocol layer provides information about the state
of the interface on a specific protocol layer WG Integration and Troubleshooting 9-6
Verifying Operational OSI States and Status

Verifying the operational OSI states and Status of some components provides many
information about the behavior of the node. For example :
• Logical Processors and physical ports
• Logical interfaces
• Hardware devices : File System, bus cards, …
UM641 03.02/EN 9-6 July, 2003

Component state change (1)

Root (CAS)
1 ATMMPE/41 VR/2
2 usageState active à idle
AtmConnection/41 ProtocolPort/IUUP
ipPort
AtmMpe/41; 2001- 10-15 18:29:38.24
SET critical operator operationalCondition 00001000
ADMIN: locked OPER: enabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: STBY: notSet UNKNW: false ipLogicalInterface /
Id: 29 Rel : Lp/0
10.6.20.130
Com: The component is locked
Int: 0/0/2/21648; osiState.cc; 668; ms.51
UM641 03.02/EN 9-7 July, 2003

Passport Alarm Format

Involved
Component Severity
OSI States Alarm Index
AtmMpe/41; 2001-10-15 18:29:38.24

Alarm SET critical operator operationalCondition 00001000
Type
ADMIN: locked OPER: enabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 29 Rel: Lp/0
Com: The component is locked OSI Status
Int: 0/0/2/21648; osiState.cc; 668; ms.51
What happen?
Alarm Format as displayed by CLI
Passport Alarm Format

The alarm fields in the Active Alarms window (full format) which are displayed in a
slightly different manner compared to a terminal interface, are described in the
following format :
Field Name - Mandatory/Optional - Example - Description
Severity - M - Warning
Indicates the severity of the alarm. It may have the following values (for further
details, refer to ITU-T X.733):
• Indeterminate: the system cannot determine the level of severity.
• Critical: requires you to react immediately to the failure. Usually it implies that the
resource is completely disabled and that service is affected.
• major: requires that you take immediate corrective measures. The resource is
severely disabled and service is affected.
• Minor: corrective action should be taken to prevent a more serious fault. The
resource is partially disabled but service is not affected.
• Warning: action should be taken to diagnose and correct a problem. Some
problem has been detected but the resource is not disabled and service is not
affected.
• Cleared: all previous alarms on this component are cleared. Alarms that have a
status of clear always have a severity of cleared.
Date and Time - M - 1995-11-23 20:39:52
The date and time the alarm was issued.
UM641 03.02/EN 9-8 July, 2003

Passport Alarm Format (Continued)

Component ID - M - EM/NODEY2C5 LP/2 X21/1
The full name of the component needing repair, or detecting the fault. The component
name can be used for hierarchically clearing alarms for its subcomponents (since the
subcomponent name is derived from the component name).
ID - M - 02000001
The system automatically inserts the notification Identifier. Notification identifiers are
unique within each Passport.
Type - M - Processing
This is a general explanation of why the alarm was generated. Possible values are:
• communications alarm indicates a problem related to communication (for
example protocol errors)
• qualityOfService alarm indicates a problem related to quality of service (ex:
crossing thresholds)
• processing alarm indicates a problem related to processing data (ex: memory
problem)
• equipment alarm indicates a problem with the physical equipment (ex:processor
failure)
• security alarm indicates a problem related to security (ex: an unauthorized
access)
• operator alarm indicates that some event was caused by operator error (ex: lock)
• debug alarm indicates that the event was for debugging purposes
• unknown alarm indicates that reason for the event is not known
Cause - M - configurationError
This provides another level of detail of why the alarm was generated. This information
is given in addition to the general explanation given in the Type field.
CO - O - Termination switch setting does not match …
Comment data is additional data in ASCII format. It provides the operator with extra
information in the form of a comment.The text appearing in this field is self-
explanatory.
OP - O - 596F7572206E616...
Operator data is hexadecimal format data that an operator can use for additional
information.
Raw - M - oos
Possible values for RAW are: insv (in service), oos (out of service), trb (troubled), unk
(unknown), nex (non-existent).
ADMIN, OPER, USAGE - M - unlocked, disabled, idle
These fields describe the possible OSI states. Passport uses component state
definitions according to the OSI standards. Components that do not provide any
behavior do not require any component state variables defined. A component has
three high-level state variables: an operational state, a usage state, and an
administrative state. These states are the primary factors affecting the management
state of a component.
UM641 03.02/EN 9-9 July, 2003

Alarm Identification
Alarm Number/Index – 8 digits
XXXX XXXX
Index Group – 4 digits SubIndex (NTP Index) – 4 digits

Logical grouping of alarms Identification within a group
Example
0999 0001
NMS Generated Alarms

UM641 03.02/EN 9-10 July, 2003

Passport Alarm Index Groups

IndexGroup Group
0000 Common alarms

0999 NMS-generated alarms
7000 Component administration system
7001 Virtual circuit
7002 Bus control system
7003 Data collection system
7004 Module interconnection link
7005 Module interconnection transport
7006 Network management interface system
7007 Frame relay service
7008 File system
… …
UM641 03.02/EN 9-11 July, 2003

Component state change (2)

Root (CAS)
1 ATMMPE/41 VR/2
2 usageState active à idle

3
5
AtmConnection/41 ProtocolPort/IUUP
4 operationalState enabled à disabled
7
SCN AtmMpe/41 Ac/41; 2001-10-15 18:29:37.72 6
ADMIN: unlocked OPER: disabled USAGE: active
AVAIL: PROC: CNTRL: ipPort
SCN Vr/2 Pp/IUUP; 2001-10-15 18:29:37.72

8
ADMIN: unlocked OPER: disabled USAGE: idle
AVAIL: PROC: CNTRL: ipLogicalInterface /
10.6.20.130
SCN Vr/2 Pp/IUUP IpPort; 2001-10-15 18:32:14.59

ADMIN: unlocked OPER: disabled USAGE: idle
AVAIL: PROC: CNTRL:
ALARM: alrmOutstdng STBY: notSet UNKNW: false WG Integration and Troubleshooting 9-12
UM641 03.02/EN 9-12 July, 2003

Example of SCN Generation
Example of SCN Generation

In this example, we unlock one physical port on the Gb interface : the LP/9 E1/0
component (1).
This component before unlocking had the following OSI states : locked, disabled,
idle. The components linked to this LP/9 E1/0 component had the following OSI
states : unlocked, disabled, idle .
The action of unlocking generates an CLEAR alarm on on the LP/9 e1/0 component
(2) which will become unlocked and enabled. Its usageState becomes busy : there
is traffic on the link.
As a consequence, other components (FrAtm/2040, Framer) will become enabled
(the OperationalState is thus changed). For these components, the system will only
generate SCNs and no alarm is directly generated.
UM641 03.02/EN 9-13 July, 2003

Student notes
UM641 03.02/EN 9-14 July, 2003

Acronyms and Abbreviations

2pGPDsk 2-port General Processor with Disk FP
3GPP 3rd Generation Partnership Project
AGC Automatic Gain Control
AMR Adaptive Multi Rate vocoder
AN Aggregation Node
APN Access Point Name
APS Automatic Protection Switching
AQM ATM queue manager
A/R Allocation/Retention
ASIC Application-specific integrated circuit
ASPEN Automatic System for Performance Evaluation of
the Network
ATM Asynchronous Transfer Mode
ATMMPE ATM MultiProtocol Encapsulation
BIM Breaker Interface Module
BIP Breaker Interface Panel
BITS Building-Integrated Timing Supply
BNC Background Noise Conditioning
BNR Background Noise Reduction
CAMEL Customized Application for Mobile network
enhanced Logic
CAP Camel Application Part
CDR Call Data Records
CGF Charging Gateway Function
CN Core Network
CP Control Processor
CP Control Plane
CPAC Cross-point access controller
CPE Costumer Premises Equipment
CPU Central Processing Unit
CS Circuit Switched
CSD Circuit Switched Data
DCE Data circuit-terminating equipment
DL Down Link
DNS Domain Name Server
DP Discard Priority
UM641 03.02 July 2003

10-1
DSCP DiffServ Code Point

DSP Digital Signal Processor
EC Echo Cancellation
EIDE Enhanced Integrated drive Electronics
EMI Electro-Magnetic Interference
EP Emission Priority
ERL Echo Return Loss
ERLE Echo Return Loss Enhancement
FP Function Processor
GA General Availability
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile Telecommunication
GSP General Service Processor
GTP’ Enhanced GPRS Tunneling Protocol
GTP-C GPRS Tunneling Protocol Control Plane
GTP-U GPRS Tunneling Protocol User Plane
HLR Home Location Register
HSCX High-level serial communication controller
extended
I/O Input/Output
IP Internet Protocol
IP Cos IP Class of Service
IPv4 Internet Protocol version 4
ISP Internet Service Provider
IWF InterWorking Function
Kbps Kilobits per second
LED Light-Emitting Diode
LI Lawful Interception
MAD Multiport Aggregate Device
MAP Mobile Application Part
M-CDR Mobility Management CDR
MEC Mobile Echo Control
MG Media Gateway
MGCP Media Gateway Control Protocol
MM Mobility Management
MM Multi Mode
MS Mobile Station
MSC Mobile services Switching Center
MTBF Mean Time Between Failure
MTP3b Message Transfer Part layer 3 for broadband
networks
UM641 03.02 July 2003

10-2
NEBS Network Equipment Building System

O&M Operation and Maintenance
OA&M Operation, Administration and Maintenance
OC-3 Optical Carrier level 3
PBX Private Branch eXchange
PC Point Code
PCM Pulse Code Modulation
PDN Packet Data Network
PDP Packet Data Protocol
PEC Product Engineering Code
PIM Power Interface Module
PLMN Public Land Mobile Network
PNNI Private Network-network Interface
PP15K Passport 15000
PQC Passport Queue Controller
PS Packet Switched
PSTN Public Switched Telephone Network
PUPS Point-of-use power supply
PVG Passport Voice Gateway
QoS Quality of Service
RAB Radio Access Bearer
RAM Random-access Memory
RANAP Radio Access Network Application Part
RA Routing Area
RAU Routing Area Update
RNC Radio Network Controller
SAAL-NNI Signaling AAL - Network Node Interface
SAS SGSN Accounting Server
SC Subscriber connector
SCCP Signaling Connection Control Part (CCITT N°7)
S-CDR Serving GPRS Support Node CDR
SCIP SCCP Client Interface Protocol
SCP Service Control Point
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SG Signaling Gateway
SGAF Second Generation ATM function Processor
SGSN Serving GPRS Support Node
SIG SS7 to IP Gateway
SIM Subscriber-Identity Module
SM Session Management
SM Single Mode
UM641 03.02 July 2003

10-3
SONET Synchronous Optical NETwork

SPM Signal Processing Module
SS7 Common Channel Signaling number 7
SSCOP Service Specific Connection Oriented Protocol
SSCF-NNI Service Specific Coordination Function - Network
Node Interface
SSF Service Switching Function
S-SMO-CDR SGSN delivered Short message Mobile Originated
CDR
S-SMT-CDR SGSN delivered Short message Mobile
Terminated CDR
STM-1 Synchronous Transfer Mode level 1 (SDH)
TCAP Transaction Capabilities Application Part
TCP Transmission Control Protocol
TDM Time Division Multiplexing
TFO Tandem Free Operation
TRAU Transcoder and Rate Adaptation Unit
UDI Unrestricted Digital Information
UDP User Datagram Protocol
UL Up Link
UMGW UMTS Media GateWay
UMTS Universal Mobile Telecommunication System
U-Plane User Plane
USC UMTS Subscriber Control
USD UMTS Subscriber Datapath
USGSN UMTS Serving GPRS Support Node
USP Universal Signaling Point
UTRAN UMTS Terrestrial Radio Access Network
UWGW UMTS Wireless GateWay
VCC Virtual Channel Connection
VMG Virtual Media Gateway
VPM Voice Processing Module
UM641 03.02 July 2003

10-4

UM641 v03.02 Student Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UM641 v03.02 Student Guide

Uploaded by

Copyright:

Available Formats

WG Configuration and Integration

"NORTEL NETWORKS AND NORTEL MATRA CELLULAR CONFIDENTIAL:

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

Version Date Comments

01.00 September 2001 UMTS 1.0

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

Table of Contents VII

UMTS Courses 1-2

3. Cards and Software Configuration 3-1

UM641 03.02 July 2003

AN SOFTWARE CONFIGURATION 3-8

UM641 03.02 July 2003

4. Passport IP Servers (GIPS) 4-1

5. U-SGSN Configuration (Shelf Type 1 Provisioning) 5-1

UM641 03.02 July 2003

STEP 1: USC FOR GN: ROUTING 5-30

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

ATM Interface to AN: I/O card provisioning 5-67

6. Wireless Media Gateway Configuration (Shelf Type 5 Provisioning) 6-1

UM641 03.02 July 2003

STEP 3: 4POC3 CARD 6-32

7. Signaling Gateway Configuration (Shelf Type 6) 7-1

UM641 03.02 July 2003

VMG PROVISIONING: LU INTERFACE 7-37

8. Wireless Gateway ATM Configuration 8-1

UM641 03.02 July 2003

MASTER/SLAVE CONFIGURATION : SVC CREATION BETWEEN MASTER AND SLAVE 8-29

9. WG Integration and Troubleshooting 9-1

10. Acronyms and Abbreviations 10-1

"Confidential information -- may not be copied or disclosed without permission".

UM641 03.02 July 2003

UM641 03.02/EN 1-1 July 2003

• UM30 Wireless Gateway Detailed Description 2

UM641 03.02/EN 1-2 July 2003

Wireless Gateway Support Engineer

UM641 03.02/EN 1-3 July 2003

GGSN Support Engineer

TL3 UM10 TL4

Wireless Gateway Configuration and Integration

UM641 03.02/EN 1-4 July 2003

Preside Support Engineer

UM641 03.02/EN 1-5 July 2003

UMTS First Line Engineer

Wireless Gateway GGSN

Wireless Gateway Configuration and Integration

UM641 03.02/EN 1-6 July 2003

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

• Describe the Wireless Gateway Passport component architecture

Wireless Gateway Configuration and Integration

UM641 03.02/EN 1-7 July 2003