0% found this document useful (0 votes)

442 views113 pages

Etisalat Nigeria 3G Mobile Network: UMTS Network (UTRAN) Low Level Design Document

Description

Uploaded by

syed

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

442 views113 pages

Etisalat Nigeria 3G Mobile Network: UMTS Network (UTRAN) Low Level Design Document

Description

Uploaded by

syed

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 113

Etisalat Nigeria 3G Mobile Network

UMTS Network (UTRAN)

Low Level Design Document

February 23, 2011

Version: v0.8 Draft

EMTS 3G UTRAN LLD

Page 1 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted
without written authorization

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, electronic, mechanical, photocopying, recording or otherwise without the
prior written permission of the Alcatel-Lucent Project Managers.

This document is the property of Alcatel-Lucent, and may not be disclosed to any third party
without the consent of Alcatel-Lucent.
No person who is not the personnel of Etisalat or Alcatel-Lucent to read this document without
having first signed a Confidentiality Agreement.

Revision Control
Version

Date

Comments

Author

Draft v0.0

27 oct 2010

Initial Document

Draft v0.1

05 Nov 2010

Initial Document

Draft v0.2

09 Nov 2010

Initial Document

Draft v0.3

23 Nov 2010

Draft v0.4

13 Jan 2011

Updating the NodeB and RNC new names

Draft v0.5

25 Jan 2011

Update IuR information, , IuCS information

after first call, NodeB configuration parameters
with 2 frequencies, ALCAP info, synchro

Eric Juillot

Draft v0.6

03 Feb 2011

Resiliency, QoS requirements, traffic descriptor

Eric Juillot

Draft v0.7

18 Feb 2011

Updated after review

Nancy Fayek

Draft v0.8

24 Feb 2011

Correct inconsistency

Eric Juillot

Nancy Fayek
Eric Juillot
Nancy Fayek
Eric Juillot
Nancy Fayek
Eric Juillot

Modifying WMS server used

Nancy Fayek

Modifying IuB ATM Traffic Descriptors

Eric Juillot
Nancy Fayek
Eric Juillot

Nancy Fayek

References
N

Reference

Title

[1]

UTRAN High Level Design

EMTS Network Architecture Overview Edition 10

[2]

LGRL203 RNC CIQ

UTRAN_CIQ_ETISALAT_Nigeria_LGRL203_Ed21.xls

[3]

BNRL204 RNC CIQ

UTRAN_CIQ_ETISALAT_Nigeria_BNRL204_Ed10.xls

EMTS 3G UTRAN LLD

Page 2 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Revision Control .................................................................................................. 2

References ......................................................................................................... 2
1.

Introduction ................................................................................................... 10
1.1.

Purpose .................................................................................................. 10

1.2.

Scope of this document .............................................................................. 10

1.3.

Audiences ............................................................................................... 10

UTRAN Architecture Overview ............................................................................. 11

2.1.

IP UTRAN Solution ..................................................................................... 11

2.2.

UA07.1 with IP Introduction ......................................................................... 13

Etisalat Nigeria UTRAN Network Architecture .......................................................... 14

Etisalat Nigeria UTRAN Network Configuration ......................................................... 16

4.1.

9370 RNC ................................................................................................ 17

4.1.1

RNC Hardware Configuration ..................................................................... 17

4.1.2

RNC Software Release ............................................................................. 21

4.1.3

RNC Capacity........................................................................................ 21

4.1.4

RNC Configuration Parameters .................................................................. 22

4.1.5

Virtual Routers ..................................................................................... 24

4.1.6

Resiliency ............................................................................................ 26

4.1.7

RNC Synchronization ............................................................................... 31

4.2.

Node B ................................................................................................... 32

4.2.1

9326 DIGITAL 2U NODEB VERSION 2 ............................................................. 32

4.2.2

9341 RRH60-21 A ................................................................................... 34

4.2.3

Node B Software Release ......................................................................... 36

4.2.4

Node B Configuration Parameters ............................................................... 36

4.2.5

Node B Synchronization ........................................................................... 40

4.2.6

Node B Capacity Licenses ......................................................................... 41

4.2.7

Feature Licenses ................................................................................... 42

4.3.

IuCS ...................................................................................................... 43

4.3.1

IuCS/IP protocol stack ............................................................................. 43

4.3.2

IuCS User Plane ..................................................................................... 44

4.3.3

IuCS Control Plane ................................................................................. 49

4.3.4

IuCS Flex ............................................................................................. 53

4.3.5

IuCS IP Addressing .................................................................................. 54

4.4.

IuPS ...................................................................................................... 55

4.4.1

IuPS/IP protocol stack ............................................................................. 55

4.4.2

IuPS User Plane ..................................................................................... 56

4.4.3

IuPS Control Plane ................................................................................. 60

4.4.4

IuPS IP Addressing .................................................................................. 66

EMTS 3G UTRAN LLD

Page 3 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.5.
4.5.1

IuR/IP protocol stack .............................................................................. 67

4.5.2

IuR User Plane ...................................................................................... 68

4.5.3

IuR Control Plane ................................................................................... 72

4.5.4

IuR IP Addressing ................................................................................... 76

4.6.

IuB ........................................................................................................ 77

4.6.1

Hybrid IP IuB protocol stack ...................................................................... 78

4.6.2

Hybrid IP IuB User Plane in the RNC ............................................................ 78

4.6.3

BTS IP Flow Configuration ........................................................................ 81

4.6.4

Consolidated VR .................................................................................... 82

4.6.5

IuB IP Addressing ................................................................................... 84

4.7.

ATM IuB .................................................................................................. 85

4.7.1

The ATM IuB interface of Alcatel- Lucent ..................................................... 85

4.7.2

ATM UTRAN IuB interface Description .......................................................... 85

4.7.3

ATM UTRAN IuB Interfaces Configuration ...................................................... 90

4.8.

QoS Management ...................................................................................... 94

4.8.1

IP Backbone QoS requirement ................................................................... 94

4.8.2

Priority handling in IP backbone................................................................. 95

4.8.3

RNC QoS Management ............................................................................. 97

4.8.4

Call Admission Control ............................................................................ 98

4.9.

IuR ........................................................................................................ 67

UTRAN OAM Architecture ............................................................................ 99

4.9.1

9353 WMS .......................................................................................... 100

4.9.2

OAM-NE NETWORK CONFIGURATION .......................................................... 102

4.9.3

Wireless Quality Analyzer....................................................................... 103

4.9.4

Network Performance Optimizer .............................................................. 104

4.9.5

DCN And Peripherals ............................................................................. 104

APPENDIX .................................................................................................... 106

5.1.

UTRAN IP Planning for Etisalat Nigeria Network ............................................... 106

5.2.

TransportMap Table ................................................................................. 107

EMTS 3G UTRAN LLD

Page 4 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table of illustrations
Figure 1: Network architecture overview for IP configuration ............................................. 11
Figure 2: Hybrid IP UTRAN User Plane logical view ........................................................... 12
Figure 3: Hybrid IP UTRAN Control Plane logical view ....................................................... 12
Figure 4: Network Topology Physical Architecture (LGRL203) .............................................. 15
Figure 5: Network Topology Physical Architecture (BNRL204).......... Error! Bookmark not defined.
Figure 6: 9370 RNC Benin configuration (4 DCPS) ............................................................. 17
Figure 7: 9370 RNC hardware 4P GIGE board & SFP ........................................................ 20
Figure 8: Example of RNC Virtual Router ....................................................................... 25
Figure 9: Segmented VRs applied for all RNCs in Etisalat NIGERIA network............................ 26
Figure 10: Example of PDR configuration ...................................................................... 27
Figure 11: ICMP Heartbeat Algorithm ........................................................................... 29
Figure 12: SCTP Heartbeat Algorithm ........................................................................... 30
Figure 13: 9326 d2U v2 HW architecture ....................................................................... 32
Figure 14: xCCM-U faceplate ..................................................................................... 33
Figure 15: 9326 d2U v2 + 9341 RRH.............................................................................. 35
Figure 16: Star / daisy chain configuration .................................................................... 35
Figure 17: Needs for Synchronization ........................................................................... 40
Figure 18: Synchronization Methods for RNC .................................................................. 41
Figure 19: IuCS over IP protocol stack .......................................................................... 43
Figure 20: RNC IuCS/IP IP Components ....................................................................... 46
Figure 21: IuCS/IP IP Flow CIR/PIR .............................................................................. 47
Figure 22: IuCS User Plane VR .................................................................................... 47
Figure 23: IuCS User Plane GE connection.................................................................... 48
Figure 24: IuCS/IP CP M3UA signaling type ................................................................... 49
Figure 25: IuCS Control Plane VR ................................................................................ 52
Figure 26: IuCS Control Plane GE connection ................................................................ 52
Figure 27: IuCS IP Addressing LGRL203........................................................................ 54
Figure 28: IuPS over IP protocol stack .......................................................................... 55
Figure 29: IuPS User Plane VR .................................................................................... 58
Figure 30: IuPS User Plane GE connection .................................................................... 58
Figure 31: IuPS/IP CP M3UA signaling type ................................................................... 60
Figure 32: IuPS SCTP associations LGRL203 .................................................................. 63
Figure 33: IuPS SCTP associations BNRL204 .................................................................. 63
Figure 34: IuPS Control Plane VR................................................................................. 64
Figure 35: IuPS Control Plane GE connection ................................................................ 64
Figure 36: IuPS IP Addressing LGRL203 ........................................................................ 66
Figure 37: IuR requirement based on RF data ................................................................. 67
Figure 38: IuR over IP protocol stack ............................................................................ 68
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 5 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 39: RNC IuR/IP IP Components ......................................................................... 69

Figure 40: IuR User Plane VR ..................................................................................... 71
Figure 41: IuR User Plane GE connection ..................................................................... 71
Figure 42: IuR/IP CP M3UA signaling type .................................................................... 72
Figure 43: IuR Control Plane VR .................................................................................. 74
Figure 44: IuR Control Plane GE connection ................................................................. 75
Figure 45: IuR IP Addressing LGRL203 ......................................................................... 76
Figure 46: Hybrid IP architecture ................................................................................ 77
Figure 47: Hybrid IP IuB protocol stack ......................................................................... 78
Figure 48: RNC Hybrid IP IuB IP Components ................................................................ 79
Figure 49: RNC Hybrid IP IuB Bandwdith Pool ................................................................ 80
Figure 50: IuB Consolidated VR (CP&UP) ....................................................................... 82
Figure 51: IuB GE connection ................................................................................... 83
Figure 52: IuB IP Addressing LGRL203 ......................................................................... 84
Figure 53: E1 ports on XCCM ...................................................................................... 85
Figure 54: ATM Traffic management on BTS ................................................................... 86
Figure 55: 16pSTM-1 ports ........................................................................................ 87
Figure 56: APS mechanism ........................................................................................ 87
Figure 57: RNC STM-1 Connection with SR7750- LGRL203 ................................................... 88
Figure 58: RNC STM-1 Connection with SR7750- BNRL204 ................................................... 88
Figure 59: ATM Traffic Management on RNC ................................................................... 89
Figure 60: ATM UTRAN IuB protocol stack ...................................................................... 90
Figure 61: ATM Vc Switching ...................................................................................... 94
Figure 62: Diffserv .................................................................................................. 96
Figure 63: Router Types ........................................................................................... 96
Figure 64: Schedulers on 4ptGE .................................................................................. 98
Figure 65: CAC Algorithm.......................................................................................... 99
Figure 66: OAM Architecture for UTRAN ...................................................................... 100
Figure 67: OAM-NE network configuration ................................................................... 102
Figure 68: WQA architecture ................................................................................... 103
Figure 69: NPO Architecture .................................................................................... 104

LIST OF TABLES
Table 1: RNCs Locations ........................................................................................... 14
Table 2: NodeB BOQ ............................................................ Error! Bookmark not defined.
Table 3: 9370 RNC hardware configuration EMTS network ............................................... 17
Table 4: 9370 RNC CP4 characteristics......................................................................... 18
Table 5: IP RNC Packet Server PMC distribution ............................................................ 19
Table 6: RNC cards and connectors specifications ............................................................ 21
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 6 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table 7: RNC Software load ...................................................................................... 21

Table 8: 9370 RNC dimensioning with DCPS in UA7.1 with CP4 ............................................ 22
Table 9: RNC configuration parameters LGRL203 and BNRL204 .......................................... 24
Table 10: RNC VR assignment all RNCs ........................................................................ 25
Table 11: Node-B Quantity by Configurations ................................................................. 32
Table 12: xCEM capacity .......................................................................................... 34
Table 13: 9341 RRH60-21 A RF Characteristics ................................................................ 36
Table 14: 9341 RRH60-21 A Optical Characteristics .......................................................... 36
Table 15: Node B Software load ................................................................................. 36
Table 16: Node B parameters BTS equipment .............................................................. 37
Table 17: Node B parameters BTS Cell ....................................................................... 37
Table 18: Node B parameters FDD Cell ...................................................................... 38
Table 19: Node B parameters FDD Cell (continued) ....................................................... 38
Table 20: Site Info parameters .................................................................................. 39
Table 21: Node B synchronization methods ................................................................... 40
Table 22: RNC synchronisation parameters ................................................................... 41
Table 23 BTS synchronisation parameters ...................................................................... 41
Table 24: Node B Capacity Licensing parameters ............................................................ 42
Table 25: RNC IuCS user plane IP subnet - Lagos RNC ....................................................... 44
Table 26: RNC IuCS user plane IP subnet - Benin RNC ....................................................... 45
Table 27: MGW IuCS user plane IP subnet for all RNC ..................................................... 46
Table 28: IuCS/IP stream definition for all RNC ............................................................ 46
Table 29: RNC IuCS user plane GE configuration - Lagos RNC ............................................. 48
Table 30: RNC IuCS user plane GE configuration - Benin RNC ............................................. 49
Table 31: CS CN Network Indicator and Point code .......................................................... 49
Table 32: RNC IuCS Control plane M3UA setting all RNCs ............. Error! Bookmark not defined.
Table 33: RNC IuCS Contorl plane IP subnet LGRL203 ..................................................... 50
Table 34: RNC IuCS Contorl plane IP subnet BNRL204 ..................................................... 50
Table 35: IuCS SCTP association configuration LGRL203 .................................................. 51
Table 36: IuCS SCTP association configuration BNRL204................................................... 51
Table 37: RNC IuCS control plane GE configuration LGRL203 ............................................ 53
Table 38: RNC IuCS control plane GE configuration BNRL204 ............................................ 53
Table 39: RNC IuCS Flex configuration all RNC ............................................................. 54
Table 40: RNC IuPS user plane IP subnet - Lagos RNC ....................................................... 56
Table 41: RNC IuPS user plane IP subnet - Benin RNC ....................................................... 57
Table 42: SGSN IuPS user plane IP subnet for all RNC ..................................................... 57
Table 43: RNC IuPS user plane GE configuration LGRL203 ................................................ 59
Table 44: RNC IuPS user plane GE configuration BNRL204................................................ 59
Table 45: PS CN Network Indicator and Point code .......................................................... 60
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 7 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table 46: RNC IuPS Control plane M3UA setting all RNCs ................................................. 60
Table 47: RNC IuPS Contorl plane IP subnet LGRL203 ..................................................... 61
Table 48: RNC IuPS Control plane IP subnet BNRL204 ..................................................... 62
Table 49: IuPS SCTP association configuration LGRL203 .................................................. 63
Table 50: IuPS SCTP association configuration BNRL204 .................................................. 64
Table 51: RNC IuPS control plane GE configuration LGRL203 ............................................ 65
Table 52: RNC IuPS control plane GE configuration BNRL204 ............................................ 65
Table 53: RNC IuR user plane IP subnet LGRL203 .......................................................... 68
Table 54: Neighbour RNC IuR user plane IP subnet LGRL203 ............................................. 69
Table 55: IuR/IP stream definition LGRL203 ................................................................ 70
Table 56: IuR/IP IP Flow CIR/PIR ................................................................................ 70
Table 57: RNC IuR user plane GE configuration LGRL203 ................................................. 72
Table 58: RNC IuR Control plane M3UA setting all RNCs .................................................. 72
Table 59: RNC IuR Contorl plane IP subnet LGRL203 ...................................................... 73
Table 60: IuR SCTP association configuration LGRL203 ................................................... 74
Table 61: RNC IuR control plane GE configuration LGRL203 ............................................. 75
Table 62: RNC IuB user plane IP subnet LGRL203 .......................................................... 78
Table 63: RNC IuB user plane IP subnet BNRL204 .......................................................... 79
Table 64: Transport Map Service Table ........................................................................ 81
Table 65: Node B Hybrid Iub IP subnet - Example of NodeB adresses .................................... 82
Table 66: RNC IuB GE configuration LGRL203 ............................................................... 83
Table 67: RNC IuB GE configuration BNRL204 ............................................................... 84
Table 68: RNC Ports used for SR7750 connections ............................................................ 88
Table 69: NodeB holding priority rules ......................................................................... 91
Table 70: VCC numbering - 8 E1 ................................................................................. 91
Table 71: VCC numbering - 2 E1 ................................................................................. 92
Table 72: A2EA adress format .................................................................................... 92
Table 73: IuB Vcc Traffic descriptors from NodeB side ...................................................... 93
Table 74: IuB Vcc Traffic descriptors from RNC side ......................................................... 93
Table 75: Iub VP number on RNC versus VP NodeB number ................................................. 94
Table 76: IP Backbone QoS requirement for IuB ............................................................. 95
Table 77: IP Backbone QoS requirement for IuCS ............................................................ 95
Table 78: DSCP Marking on IuCS .................................................................................. 97
Table 79: DSCP Marking on IuPS ............................................................................... 97
Table 80: EP Mapping on RNC Ethernet link ................................................................... 98
Table 81: WMS Primary Combo Server ........................................................................ 101
Table 82: a part of WMS configuration extracted from WNMS CIQ ...................................... 101
Table 83: PC Workstation specification....................................................................... 102
Table 84: WMS Software load .................................................................................. 102
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 8 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table 85: NodeB OAM IP adressing ............................................................................ 103

Table 86: WQA Hardware Specifications ..................................................................... 103
Table 87: NPO server specification ............................................................................ 104
Table 88: DCN And Peripherals ................................................................................. 105
Table 89: UTRAN IP Planning for Etisalat Nigeria Network ................................................ 106
Table 90: Transportmap/5 Table .............................................................................. 107
Table 91: Transportmap/2 Table .............................................................................. 108

EMTS 3G UTRAN LLD

Page 9 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

1. INTRODUCTION
1.1.

Purpose

The purpose of this Low Level Design (LLD) document is to capture the detailed design supporting
UTRAN implementation for Etisalat Nigeria 3G mobile network.
The document includes the Etisalat Nigeria UTRAN configuration for 2100MHz network in UA07.1
release with full IP solution for IuCS, IuPS and IuR and Hybrid solution for Iub.
The actual data for UTRAN network will be centralized and controlled through the CIQ documents
(Customer Input Questionnaire).

1.2.

Scope of this document

This document will address the following major areas:

UTRAN Network architecture & configuration description (i.e. Node Bs, RNC, OAM and
associated interfaces)

Hardware Engineering for Node B, RNC, W-NMS

Full IP UTRAN Solution for IuCS, IuPS and Iur

Hybrid UTRAN Solution for Iub

IP Planning in UTRAN

The system load line up for this document is as follow:

1.3.

UTRAN

OAM

UA07.1.1.7

OAM07.1.1.3 EP2

Audiences

The primary intended readers are EMTS operations teams, as well as the Alcatel-Lucent
engineering community assigned to this project.

EMTS 3G UTRAN LLD

Page 10 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

2. UTRAN ARCHITECTURE OVERVIEW

The UTRAN is composed of several Radio Network Subsystems (RNS). Each RNS is composed of
several entities:

One Radio Network Controller (RNC), that manages several Node Bs.

One or more Node Bs which is the logical node for radio transmission/reception in one or
more cells to/from the UE.

Those entities are interconnected with each other and to the outside world through interfaces: Iu
(RNC <-> Core Network), IuR (RNC <-> RNC) and IuB (RNC <-> Node B)

2.1.

IP UTRAN Solution

The scope of IP Transport in UTRAN is intended to replace the ATM transport Network (AAL2/ATM
or AAL5/ATM) by an IP transport network to reduce transmission costs.
The primary benefit of this feature is to achieve OPEX savings through the use of more cost
effective IP transport on all UTRAN interfaces e.g. Iu, IuR and IuB.
Below figure presents the Hybrid IuB IP UTRAN network architecture when all nodes are connected
through IP + ATM backbone for Iub and full IP backbone for IuCS, IuPS and IuR.

Figure 1: Network architecture overview for IP configuration

EMTS 3G UTRAN LLD

Page 11 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

In User plane, the radio network layer remains unchanged when compared to ATM transport (UP:
Iu, IuR and IuB Frame Protocols)

Figure 2: Hybrid IP UTRAN User Plane logical view

In Control Plane, the radio network layer remains unchanged (CP: NBAP, RNSAP and RANAP),
except that the transport layer information provided in CP is expanded in flexibility to also support
IP-based information used for IP-based UP flows. ALCAP is still required in the transport network
control plane since ATM-based transport is still used.

Figure 3: Hybrid IP UTRAN Control Plane logical view

EMTS 3G UTRAN LLD

Page 12 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

2.2.

UA07.1 with IP Introduction

The Alcatel-Lucent UA07.1 release will provide the possibility to use only the IP transport
network on all the interfaces with the following features:

Hybrid IuB Support

Hybrid IuB means support of ATM and IP transport on the IuB interface, for the Control
Plane, User Plane and NodeB OAM flows. In this case ATM carries the Control Plane, part of
the user plane, while HSDPA is carried on IP transport.

RNC Support for IuCS over IP

IP transport on IuCS: between the RNC and the MSC server for Radio Network Layer control
plane, and between the RNC and the Media GateWay (MGW) for user plane in the Bearer
Independent CS Core Network (BICN) architecture

RNC Support for IuPS over IP

IP transport on IuPS: between the RNC and the SGSN for control plane and user plane
traffic.

RNC Support for IuR over IP

IP transport on IuR: between two RNCs.

Pure IP transport on Itf-R and Itf-B

The OMC can be connected only to the IP backbone

The UTRAN IP backbone and the CN IP backbone are supposed to be a level 3 or level 2 network
with IPv4 addressing, IP (or IP/MPLS) routing and DiffServ forwarding.
It is supposed to be secured and transparent: IP packets shall be conveyed without any
modification of the UDP/IP headers because IP addresses and UDP ports are used as bearer
identifiers.
To address a level 2 network, with Ethernet or VPLS, L3/L2 gateways are needed between the
UTRAN Network Elements (NEs) and the layer 2 backbone.

-> The UA07.1 release with full IP for IuCS, IuPS and Iur will be implemented in Etisalat
Nigeria 3G mobile network.
Iub will use a combination of ATM and IP transport (hybrid Iub)

EMTS 3G UTRAN LLD

Page 13 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

3. ETISALAT NIGERIA UTRAN NETWORK ARCHITECTURE OVERVIEW

Etisalat has engaged Alcatel-Lucent to deploy a WCDMA (2100 MHz) HSPA network to provide
coverage in Lagos and Benin areas.
This first deployment phase in scope of UTRAN includes:

142 x Node B sites in Lagos area

20 x NodeB sites in Benin area

1 RNC in Lagos area

1 RNC in Lagos area (additional shelf)

1 RNC in Benin area

1 WNMS in Lagos area

The Core network compositions are

1 Huawei MGW in Ikosi IKMG01
1 Huawei MGW in Lagos LGMG01
1 Huawei MGW in Benin BNMG01
3 Huawei MSCs in Lagos
1 Huawei MSC in Abuja
1 Huawei SGSN in Lagos LGSG01
The Alcatel Lucent RNCs will be connected to Huawei MGW/MSC on IuCS, and on Huawei SGSN on
IuPS
According to the distribution of the cities to be covered, Alcatel-Lucent proposes to consider 3
main sites for the deployment of the UMTS equipment in Nigeria :
Locations are as follows
Site
Lagos RNC

Site ID
B3130

latitude
6.608642

longitude
3.379605

Benin RNC and Benin MGW

B4210

6.293426

5.63143

Lagos MGW & SGSN

B3012

6.44883

3.47849

Table 1: RNCs Locations

In the proposed network, a service router is used to connect the RNC to Node Bs through an
Ethernet/IP backbone network. For redundancy reason, a pair of 7750 SR is used as the service
router at each RNC site.

EMTS 3G UTRAN LLD

Page 14 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Lagos RNC connect to the remote core network through SDH network

Figure 4: Network Topology Physical Architecture (LGRL203)

Benin RNC will be connected to Benin MGW and Lagos SGSN for the first call

EMTS 3G UTRAN LLD

Page 15 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4. ETISALAT NIGERIA UTRAN NETWORK CONFIGURATION

For Etisalat Nigeria network, Proposed Items in this scope are as follows:

Radio Network Controller (RNC) with Dual Core Packet Server

1x
1x
1x
1x

9370-RNC-single-10DCPS-CP4-Hybrid IuB - Lagos

9370-RNC-single-10DCPS-CP4-Hybrid IuB - Lagos (additional shelf)
9370-RNC-single-10DCPS-CP4-Hybrid IuB Benin
9370-RNC-single-4DCPS-CP4-IP Testbed

Node Bs

162x 9326 digital 2U Node B (1x XCCM-U with IP interface, 1x XCEM-U)

162 x
o
o
o
o

3 sectors Remote Radio Head RRH60W-2100MHz distributed as follows:

106x NodeB (Lagos)
36x NodeB (Ibadan)
14x NodeB (Benin)
6x NodeB (Warri)

1x NodeB-DistInd-3,2(16D+16H+16E)-IP-3 RRH60-21a-MM - Testbed

Point of Concentration (POC)

2x 7750 SR7 (2IOM, 2MDA 10PT GE, 2MDA 4PT OC3) - Lagos
2x 7750 SR7 (2IOM, 2MDA 10PT GE, 2MDA 4PT OC3) - Benin
1x 7750 SR7 (1IOM, 1MDA 10PT GE, 1MDA 4PT OC3) - Testbed

Wireless Management System (WMS)

9353 WMS based on T54400 MED

9351 WQA

5x WMS clients

1x RAMSES with 1 x 48port switch and 2 x 24ports switches

1x Firewall ( Brick) for VPN

Software Release:

UTRAN Base Software UA07.1

Synchronisation

Synchronisation of NodeB will be done through E1 (ATM) connecting to the RNC

EMTS 3G UTRAN LLD

Page 16 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

9370 RNC

4.1.

Alcatel-Lucent RNC portfolio provides: 9370 RNC

The 9370 RNC supports IP, ATM, Frame Relay and voice services. For Etisalat NIGERIA, IP interfaces
are provided on IuCS, IuPS, Iur with two 4-port Gigabit Ethernet (4p GE) cards.
Iub interfaces use a combination of IP interfaces and ATM using the 16 ports STM1 card.

4.1.1 RNC Hardware Configuration

The 9370 RNC hardware configuration rules in hybrid Iub (position of cards in the slots) are
provided in Figure 7. This figure illustrates the configuration used in Etisalat Nigeria RNCs with 10
DCPS cards.
The RNC layout is:
o

CP4 cards must be inserted in slots 0 and 1

DCPS cards must be deployed using the slot sequence 2 to 7, then from slot 10 to slot
13 (if necessary)

16ports STM1 cards must be deployed in slot 8 and 9

Two 4 port GIGE port cards must be deployed in slot 14 to 15

The non used slots have filler inserted (when < 10 DCPS)

Figure 5: 9370 RNC Hardware configuration rules

For Etisalat Nigeria network, all the RNCs host 10 DCPS cards.
RNC Name
LGRL203
BNRL204

HW Configuration
9370 RNC with 10 DCPS
9370 RNC with 10 DCPS

Total Node B
142
20

Max NodeB
2000
2000

Table 2: 9370 RNC hardware configuration EMTS network

EMTS 3G UTRAN LLD

Page 17 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.1.1.1

Hardware Modules

CP:
The Control Process (CP) board is responsible for the system control of the RNC. Two types of CP
boards exist: CP3 or CP4.
For Etisalat NIGERIA RNC(s), the control process board used is CP4.
In RNC context, there are always 2 CP boards per RNC and the CP operates into 1+1 redundant.

Table 3: 9370 RNC CP4 characteristics

CP also has an external access (Ethernet 100BASE-T on RJ45 Connector) from/to OAM to be used
in case of outband O&M configuration.

Packet Server:
The Packet Server Functional Processor (FP) has no external interfaces and provides the RNC with
power processing for UMTS specific Layers and Transport Network Layer management. Two types of
Packet Server boards exist: PSFP and DCPS
For Etisalat NIGERIA RNC(s), the Packet Server board used is DCPS (Dual Core Packet Server).
Each Packet Server board includes 6 PMC processors. Their function is related to the slot of the
Packet Server board. So, if we interchange 2 Packet Server boards, each PMC is reconfigured
according to the new slot position of the board.

EMTS 3G UTRAN LLD

Page 18 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table 4: IP RNC Packet Server PMC distribution

PMC Roles brief description

PMC-Master: 2 per RNC

Manage other processors
1:1 spared

Protocol Converter (PC) max 12 per RNC

Segmentation and Reassembly, handle IuCS/Iur/Iub Uplane UDP/IP
N+1 Load share

Radio Access Bearer (RAB) max 40 per RNC

Bearer Processing, Radio Protocol Handling (MAC, RLC,..), Interface bearer, Macro Diversity
Handover, GTP-U Processor
N+1 Load share

Network Interface (NI) 2 per RNC

MTP3b/M3UA and SCCP layers of the SS7 stack
1:1 spared

Traffic Management Unit (TMU) max 14 per RNC

Terminates Radio network interface protocols (RANAP, RNSAP, NBAP etc..)
Support RRM (RRC, Always-On, QoS management, Call Admission, iRM scheduling)
N+P spared (P=2 for more than 7 DCPS)

OAM Management Unit (OMU) 2 per RNC

Manages Control plane functions, Configuration and Fault management
1:1 spared

EMTS 3G UTRAN LLD

Page 19 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

In addition, there is a PDC (Processor Daughter Card) on the Packet Server card. The PDC will be
used as a SCTP termination for control plane of IuCS/IP, IuPS/IP, IuR/IP. All Packet Server cards
except those supporting the PMC-NI (slot 4 &5) are able to support SCTP associations.
4P GIGE Boards:
The 4-port Gigabit Ethernet boards are needed in case where direct IP
interfaces are used for the RNC.
As indicated by its name, this board provides 4 full-duplex ports for Gigabit
Ethernet access, and support of Small form-factor pluggable (SFP) optics, SX
(with 500 meter reach), LX (with 10 KM reach)
For Etisalat NIGERIA RNC(s), the SFP used is LX.

Note that only IPV4 is supported with 4pGIGE

boards.

Full Gigabit Ethernet throughput (1 Gbps)

supported on each port, but the total
aggregated throughput is limited to 2.5 Gbps
for the 4 ports.

Support Ethernet II, 802.3 LLC SNAP

encapsulation, 802.3z Gigabit MAC, IEEE VLAN
support (802.1Q)
Figure 6: 9370 RNC hardware 4P GIGE board & SFP

The Alcatel-Lucent RNC provides several external/internal interfaces listed below.

RS232 (CP4 card) as console connection for on-site maintenance purposes

Ethernet (CP4 card) as IP connection for OAM purpose

STM-1 clear channel (16pOC3/STM1) as logical interface (IuB, IuR, Iu)

Gigabit Ethernet (4p GE) as logical interface (IuB, IuR, Iu)

Each version of optical module uses a specific wavelength laser to transmit and receive data over a
fibre optic cable. The wavelengths are matched to the type of fibre cable it accommodates and to
the strength of the laser, namely short reach (SR), intermediate reach (IR), or long reach (LR).

In Single Mode the types available are IR or LR; in Multi-Mode the type available is SR.

It is important to note that Optical Fibres commonly used within RNC are SINGLE mode ones (as
opposed to Multi-mode).

The different boards used in RNC have fixed connectivity types: either IR or LR. Therefore on a
port basis for these boards, Single Mode OR Multi-mode, as well as the strength of the laser Short,
Intermediate OR Long Reach could be used. In the context of RNC the Single Mode Intermediate
Reach is usually used. Long Reach (Single Mode) or Short Reach (Multi-Mode) could be also chosen
depending on the need. When an in-service SFP fails or the inserted SFP does not match what the
socket is configured for in software, alarm 70115480 is generated.

EMTS 3G UTRAN LLD

Page 20 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

The table below presents the different connectivity characteristics of the different optical boards.
(Important Reminder: RNC RoHS version relies on 16pOC3/STM1 with LC connectors)

In Etisalat Nigeria network, the following cards and connectors have been deployed.

Board

PEC code

Connector
Type

16pOC3/STM1
MS3 POS ATM

NTHW48AG

Single
Mode IR

4pGiGE

NTHW49AG

Single
Mode IR

Distance

Mean
Transmission
Power

Mean
Peception
Power

From
-15
to -8 dBm

From
-28
to -8 dBm

Up to 10 km with a
nominal wavelength of
1310 nm

Table 5: RNC cards and connectors specifications

4.1.2 RNC Software Release

The following licensed software will be operating on the RNC in Etisalat Nigeria network
Software Item

Software Version

RNC Load

UA07.1.1.7 TAP3
Table 6: RNC Software load

4.1.3 RNC Capacity

The RNC capacity is defined in three dimensions:

Traffic

Coverage

connectivity

These dimensions are independent, thus the RNC capacity is determined by the most constraining
limit.
In addition, RNC capacity depends on Software release and the type & number of HW cards
installed in the RNC.
Alcatel-Lucent 9370 RNC in UA07.1 will support 5 Market Models i.e. 4, 6, 8, 10 and 12 DCPSs.
Alcatel-Lucent proposed the implementation of 10 DCPS models in Etisalat Nigeria network as
mentioned previously i.e. Benin and LagosRNC: 9370 RNC with10 DCPS + CP4

RNC Capacity - Traffic Dimension

12 DCPS

Call profile
Speech (Erlangs)
Mobile Office Premium
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

12000
Page 21 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Iu Application Mbps
IuB Application Mbps
HSPA+Uni-Service
Iu Application Mbps
IuB Application Mbps
R99 Service-Mix
Erlangs
Iu Application Mbps
IuB Application Mbps
HSPA Service-Mix
Erlangs
Iu Application Mbps
IuB Application Mbps

655
935
655
1022
5523
126
152
3231
261
314

Table 7: Summary of 9370 RNC traffic with DCPS (UA07.1)

In Etisalat Nigeria network: there will be a mixture of services i.e. R99, HSDPA and HSUPA, so HSPA
service-mix Traffic view is recommended for reference of RNC Capacity.
See appendix for call profile assumption parameters.

RNC Capacity Coverage Dimension

10 DCPS
Node Bs
2000
Cells
2000
Table 8: 9370 RNC dimensioning with DCPS in UA7.1 with CP4

Number of Node B: This is the number of Node Bs that can be under a single serving RNC.
Number of Cells: This is the number of cells that one serving RNC can support. A cell is defined
as one carrier in one sector

RNC Capacity Connectivity Dimension

IP RNC is used in Etisalat Nigeria network, so the RNC connectivity view is based both on
Number of Ethernet ports: This is the number of Ethernet Ports that the RNC can
terminate.
o

2 GiGE cards are installed per RNC and should work in active & standby mode,
thanks to PDR mechanism.

Each card has 4 Gigabit Ethernet ports

1 Gbps supported on each port, but the total aggregated throughput is limited to
2.5 Gbps for the 4 ports

o
Number of STM1 ports: This is the number of STM1 Ports that the RNC can terminate.
o

2 STM1 cards are installed per RNC and should work in active & standby mode,
thanks to APS mechanism.

Each card has 16 STM1 ports @ 155 Mbps

4.1.4 RNC Configuration Parameters

Following tables are the main RNC parameters to be configured during the RNC Integration. These
data are extracted from RNC CIQ files

EMTS 3G UTRAN LLD

Page 22 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

RNC

RNC1 (Lagos/Ibadan)

RNC2 (Warri/Benin)

RNC Name

LGRL203

BNRL204

RNC Id

203

204

Version

07_01_00

INodeName

LGRL203_IN

BNRL204_IN

RNC Frequency Band(s)

umtsBand

GsmBandIndicator

dcs1800

dlFrequency

10662/10687

ulFrequency

9712/9737

testFrequency

10662

mobileCountryCode

621

mobileNetworkCode

PSPF Model Type

DCPS

RNC Market Model

10 PS Cards

RNC NSAP Address

45000000000032031F0000000000 45000000000032041F0000000000
000000000000
000000000000

Clock Synchronization

LP8 SDH/0 LP9 SDH/0

SS7 originatingPointCode

203

204

ciphering

cipheringActivated

relocationCiphering

cipheringDisableIgnored

securityControl

integrityActivated

Out_band_OAM

Out_band OAM

GIGE port

GIGE 1 port 1/ GIGE 2 port 1

mobileCountryCode

621

mobileNetworkCode

Network indicator

3 - NationalSpare

SS7 destination Point Code PS

1514

GIGE port

GIGE 1 port 2/ GIGE 2 port 2

mobileCountryCode

621

mobileNetworkCode

Network indicator

3 - NationalSpare

SS7 destination Point Code CS

1550

1557

OAM
In_band / Out_band OAM
IP PS domain

IuPS Control Plane

IP CS domain

IuCS Control Plane

IUB Hybrid
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 23 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

GIGE 1 port 0/ GIGE 2 port 0

16pOC3/4pGigE board number

Port number

0,1,2,3,4

1+1 APS used

1+1

APS mode

bidirectionnal

revertive

Revertive

revertive

Protected Line

PNNI on interface

N/A

GIGE port

GIGE 1 port 3/ GIGE 2 port 3

N/A

mobileCountryCode

621

N/A

mobileNetworkCode

N/A

GIGE port
IUB ATM

IP Iur domain

IuCS Control Plane

Network indicator

N/A
3 - NationalSpare

SS7 destination Point Code CS

N/A
N/A

Table 9: RNC configuration parameters LGRL203 and BNRL204

4.1.5 Virtual Routers

In the RNC, IP routing is provided by IP Virtual Routers:

A VR is a software element acting as a logical instance of a physical router

A VR is dedicated to an IP routing domain. Each VR has its own Routing and Forwarding
database : this allows a secure separation of traffic

A VR is configured with Protocol Ports (PP)

Each PP is identified by an IP@ and a subnet

Each PP is linked to a physical interface : an internal interface to the Local Media

or an external Ethernet port of the 4pGE card

Several PPs can be linked to the same ethernet port with the use of VLANs

EMTS 3G UTRAN LLD

Page 24 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 7: Example of RNC Virtual Router

4.1.5.1

VR Configuration:

Three primary configurations of VR are possible:

1. One Consolidated VR: a single Subnet and a single Ethernet port (optionally a single VLAN)
is used for all interfaces
2. Segmented VRs per interface: one Subnet and one Ethernet port (optionally one VLAN) is
used per interface
3. Segmented VRs per interface and per CPlane/UPlane:
- One Subnet and one VLAN-Ethernet is used per interface and per CPlane/UPlane.
- The use of VLANs is mandatory on some interfaces. 2PP -> 1 Ethernet port

4.1.5.2

VR Limitation:

In UA07, the RNC supports:

400 VLANs

12 VRs with PDR

4 next hops per PDR

60 protocol ports per VR

1 Subnet per protocol port and the same Subnet cannot be configured to different VRs

For PDR description, please refer to section 4.1.6.1

4.1.5.3

VR Implementation for Etisalat NIGERIA network

For Etisalat NIGERIA network, the chosen VR configuration is Segmented VRs per interface and
per CPlane/UPlane. And the VR assignment for each RNC is as follows:
VR

Traffic Type

VR/0

OAM Traffic

VR/1

IuPS User Plane

VR/2

RNC Internal Traffic

VR/3

Reserved for Location Service

VR/4

Reserved for Cell Broadcast Service

VR/5

IuB User Plane

VR/6

Unused

VR/7

IuPS Control Plane

VR/8

IuCS User Plane

VR/9

IuCS Control Plane

VR/10

IuR User Plane

VR/11

IuR Control Plane

Table 10: RNC VR assignment all RNCs

EMTS 3G UTRAN LLD

Page 25 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 8: Segmented VRs applied for all RNCs in Etisalat NIGERIA network

From above figure:

IuPS traffic from VR/1 and VR/7 is linked to GiGE port 14.1 (active) and 15.1 (standby)

IuCS traffic from VR/8 and VR/9 is linked to GiGE port 14.2 (active) and 15.2 (standby)

IuR traffic from VR/10 and VR/11 is linked to GiGE port 14.3 (active) and 15.3 (standby)

IuB traffic from VR/5 is linked to GiGE port 14.0 (active) and 15.0 (standby)

GiGE port active/standby is configured by means of PDR mechanism, see following section

4.1.6 Resiliency
The defense strategy in the RNC is based on two mechanisms:

PDR (Protected Default Route)

Heartbeat Monitoring Mechanism

4.1.6.1

PDR

RNC support static route only, no other dynamic routing protocol supported. Thus routing between
RNC and adjacent routers is static route.
For resiliency, RNC uses Alcatel-Lucent proprietary Protected Default Route (PDR) to provide IP
route failure protection at Layer 3, thus the recommended and implemented configuration in EMTS.
Note that PDR is used in egress/downstream of RNC to adjacent routers.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 26 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

PDR provide protection against:

4ptGiGE card and port failure
Adjacent Routers Failure (in case of collate routers)
GiGE link failure
PDR protecting a default route entry (i.e. 0.0.0.0) has following criteria:
Minimum 2 NextHop entries and maximum 4 NextHop entries.
Revertive
Supported on maximum 12 VRs in UA07 release.
Each NextHop within a VR is assigned different metric/cost values. The advantage of specifying
different costs for the NextHop is the predictability of the path being used when all path are
available.
The drawback is the short disruption resulting from reversion, when the failed path comes back
into service. However, this is short enough to avoid CP impacts, and will have minimal UP impacts
since PDR reroute traffic over alternate path in less than 1 second in the event of GigE card failure
or link failure and less than 5 seconds for next hop failures.
Protected Default Route (PDR) is a defense mechanism is used to provide IP route failure detection
and protection between RNC and its next hop router.

Example of PDR Configurations:

Each next hop uses a unique IP subnet, e.g. 11.11.11.0/32 and 22.22.22.0/32.

At least 2 default route 0.0.0.0 entries in the Routing Table

One default route entry in the Forwarding Table

Use of metric to select preferred default route

Figure 9: Example of PDR configuration

EMTS 3G UTRAN LLD

Page 27 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

For PDR configuration in Etisalat NIGERIA network, please refer to IuCS, IuPS, IuR, IuB chapters,
section GE connection.

4.1.6.2

Heartbeat Monitoring Mechanism with Next Hop Router

ICMP echo requests are used to detect adjacent router failures. This mechanism verifies the L3
connectivity of next hops routers of the PDR for IuCs and IuPS.
This is because with IP static routing, no routing protocol running between adjacent routers to
detect L3 failure on adjacent router that is not caused by a port or link failure.
In order to detect loss of L3 connectivity of the adjacent next-hop router, this feature uses a L3
heartbeat monitoring with ICMP Pings. After obtaining ARP data, an ICMP Echo request is sent to
each next hop router of all PDR routes every second. If no ICMP Echo response is received within
the last pre-configured seconds (minimum is 4 seconds), the heartbeat status of this next hop
router will be considered down.

Heartbeat Configuration:
If the heartbeat monitoring is enabled for the PDR, the route selection will always favor those next
hops with heartbeatState = up , regardless of their metric values. The metric value is only taken
into consideration for the route among those heartbeat-status-up next hops. Also heartbeat only
applies to protected default routes.
Under Vr/ IP/ Static/ Route/0.0.0.0, 0.0.0.0,0 attribute heartbeat is set to enabled to activate
the heartbeat mechanism.
Attribute heartbeatDeadInterval is set to 4 seconds, if no heartbeat response received in the 4s
interval it means that the heartbeat status of the nexthop router is down. Heartbeat polling
requests are sent 1 per second.

EMTS 3G UTRAN LLD

Page 28 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 10: ICMP Heartbeat Algorithm

4.1.6.3

Heartbeat Monitoring Mechanism for hybrid Iub (proprietary)

Whereas the PDR heartbeat mechanism is used to detect any card/port failure or external
facing router failure, this proprietary heartbeat is an E2E mechanism from RNC to BTS in order
to detect any IP Network failure or BTS Failure.
This mechanism will only be started as soon as the RNC receives the IP @ address of the
corresponding BTS, that is to say after the first successful RadioLink Establishment over IP.
Set of values should be the same on both sides (RNC and BTS) in order to avoid any long failure
misdetections. For instance, UDP port used for this heartbeat must be configured to the same
value on both side RNC and BTS (65535)
Other parameters to be checked: IubheartBeatPingTimeInterval ; IubheartBeatNumAttempts.
Be aware that the following relation has to be verified:

Parameter

4.1.6.4

Value

RNC /IubheartBeatUDPPortNumber

65535

BTS/IPRAN/ heartBeatUDPPortNumber

65535

RNC /IubheartBeatNumAttempts

RNC /IubheartBeatPingTimeInterval

1 .8 sec

Heartbeat Monitoring Mechanism For SCTP

For the Control Plane, SCTP protocol provides a resiliency mechanism on Iu
Several SCTP associations are established between RNC and its peer M3UA node
(SGSN / SG) to provide redundancy in case of path failure.
When a path becomes unreachable and the peer CN entity is multi-homed, then a
secondary path is selected. When a path becomes unreachable and the peer CN
entity is not multi-homed or there is no remaining secondary path, then an indication
is sent to the upper layer, i.e. M3UA.
It is recommended that each DPC be assigned at least two SCTP associations. The
two associations that lead to the same DPC must be assigned to two different PSFP
cards. This provides protection for the associations against PSFP card failures.

To detect the failure of one path

An SCTP instance monitors all transmission paths to the peer instance

of an association. To this end, HEARTBEAT chunks are sent over all
paths which are currently not used for the transmission of data chunks.
Each HEARTBEAT chunk has to be acknowledged by a HEARTBEATACK chunk.

Each path is assigned a state: it is either active or inactive. A path is

active if it has been used in the recent past to transmit an (arbitrary)
SCTP datagram which has been acknowledged by the peer. If
transmissions on a certain path seem to fail repeatedly, the path is
regarded as inactive.
EMTS 3G UTRAN LLD

Page 29 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

The number of events where heartbeats were not acknowledged within

a certain time, or retransmission events occurred is counted on a per
association basis, and if a certain limit is exceeded (the value of which
may be configurable), the peer endpoint is considered unreachable, and
the association will be terminated.

Figure 11: SCTP Heartbeat Algorithm

The RNC SCTP heartbeat is configured with:
the heartBeatInterval
the MaxPathRtx parameters
RetransmissionTimeOut (RTO)
Without activity of the SCTP association, on heartBeatInterval expiry, the RNC sends the heartbeat
signal to the SCTP EndPoint, without answer from the peer SCTP endPoint, the heartBeat is
repeated maxPathRtx times

Ensure symmetry between the RNC and SGSN configuration at the M3UA and SCTP layers.

M3UA

ack timer: 2 seconds; range [1..60]

recovery timer: 2 seconds; range [0..5]
sequence control timer: 800 msec; range [500..1200]
heart beat timer: 30 seconds; range disabled=0, [30..90]

RTO initial: 3000 msec; range [1000..30000]

RTO minimum: 500 msec; range [100..5000]
RTO maximum: 10000 msec; range [1000..60000]
RTO Alpha: 1/8 (not configurable)
RTO Beta: 1/4 (not configurable)
maximum initial retransmit: 8; range [1..32]
sctp ack delay: 200 ms; range [50..500]
heartbeat interval: 3000 msec; range [1500..60000]
maximum path retransmit: 3 [1..8]
path mtu: 1500 bytes [512..9180]

SCTP

EMTS 3G UTRAN LLD

Page 30 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.1.7 RNC Synchronization

RNC does not require any external synchronization reference thanks to its internal clock offering a
Stratum 3 ( +/- 4.6 10-6 s) accuracy
Nevertheless NodeB for the Uu Radio interface needs a Stratum 1 ( +/- 10-11 s) accuracy, which can
come from the RNC but RNC then needs to itself retrieve it from another source than its internal
clock
In case of full IP configuration for IuB interface, NodeB require an external synchronization
method (External clock, GPS or PTP/1588).
In Etisalat NIGERIA network, the Iub uses an hybrid configuration, the NodeB synchronization
method will be through E1

EMTS 3G UTRAN LLD

Page 31 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.2.

Node B

For Etisalat NIGERIA network, Node Bs are remotely distributed across the network and they are
co-located with existing 2G BTS equipment. The antenna system for 2G and 3G are separate; new
2100MHz antenna will be used on every site.
The product offered is Alcatel-Lucent 9326 digital 2U Node B. Both Indoor and Outdoor 9326 D2U
V2 are offered, in 2-carrier configuration and in 3-sectored distributed architecture with 9341 RRH
60-A 2100 Remote Radio Heads.
The following table shows the quantity of Node B per configuration:

Item

Quantity

Indoor 9326 D2U V2 with

3x 9341 RRH 60-A 2100
1x xCEM,
1x xCCM

Outdoor 9326 D2U V2 with

3x 9341 RRH 60-A 2100
1x xCEM,
1x xCCM

143

TOTAL

162
Table 11: Node-B Quantity by Configurations

4.2.1 9326 DIGITAL 2U NODEB VERSION 2

The 9326 d2U version 2 is an evolution, taking benefit of experience acquired with d2U V1.
This is in fact a complete new product with a new architecture (new rack + new modules).
Within version 2, there is 2 phases of introduction:
- 9326 d2U v2 phase 1: with modules iCCM/U and xCEM-U
- 9326 d2U v2 phase 2: with modules xCCM-U and xCEM-U -> used in Etisalat NIGERIA
Network

Figure 12: 9326 d2U v2 HW architecture

EMTS 3G UTRAN LLD

Page 32 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

This d2U Node B V2 is composed of:

Up to 3 xCEM-U modules, these modules are in charge of part of call processing, base band
transmit/receive digital signal processing.

One xCCM-U Module (or iCCM-U) with adaptor board at the introduction of the product.

a 2U Mechanical shelf

an associated backplane RBP 2U V2 (user Rack Back Plane), which is in charge of supporting
all internal links between modules.

2 boards: RUC front 2U V2, and RUC back 2U V2 (Rack User Commissioning), which are in
charge of supporting all commissioning non volatile memories, and fan alarms. RUC front
2U V2 also supports the interface with a 16 external alarms kit. RUC back 2U V2 also routed
the power supply tracks to the RBP 2U V2

4.2.1.1

xCCM-U

The xCCM-U module is installed in the BTS D2U V2 in order to support the IP features.
Characteristics
The xCCM-U is an enhanced version of the iCCM-U. It provides increased processing capabilities to
adapt the Node B to the evolution of the last mile connectivity using state of the art hardware and
software components.
It is composed of the following part:

CBB (Control & Baseband Board): this is the "mother board" of the xCCM supporting 4 PCM
connections for Iub link on faceplate.

External interfaces (motherboard) on front panel

1 x RJ45 for GPS synchronisation connector. It is used for providing clock synchronization
and communication with TMU.

6 Optical SFP cages (3 CPRI + 3 CPRI/HSSL) with built-in LEDs for RRH, TRDUs or MC-TRX

1-Wire interface connector (RJ45) for Alarm connectivity

2 Fast Ethernet (RJ45) ports, 10/100 BaseT:

This link Port1 (Debug) on front-panel (10/100bT type) is used for debug purpose.

The link Port2 (SiteLAN) on front-panel (10/100bT type) allows the management of
OEM devices (such as tilt antenna or microwave device) co-located to the BTS. This
100Mbps fast ethernet (FE) port can also be used for native Iub. It is sufficient
to connect the iBTS to the Ethernet backhaul. FE is of since the throughput is
limited to 30 Mbps in DL and 15Mbps in UL. This port is the one used for Hybrid
IuB connectivity

Embedded
4 E1/T1
ports

xCCM-U (used in d2U NodeB) front

RJ-45 Ethernet Port 2 will be used for IP Connectivity

Figure 13: xCCM-U faceplate

EMTS 3G UTRAN LLD

Page 33 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

SFP1 connector (optical or electrical transceiver)

SFP2 connector (electrical transceiver)

1 RJ45 (electrical) for 10/100/1000 Base-T

Supports Ethernet protocols : IEEE 802.3 compliant; IEEE 802.1q VLAN tag; IEEE 802.1p bits

Maximum iBTS capacity: 30Mbps DL + 15 Mbps UL

4.2.1.2

xCEM-U

CEM (Channel Element Modules) is in charge of part of call processing, base band transmit/receive
digital signal processing. CEM performs the base-band Layer1 and a sub-set of the Layer2 MAC
functionality for the UMTS FDD standard.
The xCEM/xCEM-U is the third generation of CEM, following CEM and iCEM modules.
xCEM-U is an essential building block of the capacity increase path of the dNodeB 2U.
xCEM-U provides the operators with means to double the maximum capacity of the dNodeB 2U sites
(in terms of speech Channel Elements) without any additional rack

Capacity:

Table 12: xCEM capacity

Throughputs:
- HSDPA: 28.8 Mbps shared throughput per xCEM board
- HSUPA: 10 Mbps (in UA7.1) shared throughput per xCEM board
Each xCEM board can manage up to 6 cells belonging to 2 Local Cell Groups.
Note: Local Cell Group (LCG): Group of NODE B Cells for which Softer Handover is possible. Up to 3
cells per LCG

4.2.2 9341 RRH60-21 A

9341 RRH60-21 A is a product offered for Etisalat NIGERIA network in order to provide the RF
interface while connecting to 9326 d2U v2 via optical fibers.

EMTS 3G UTRAN LLD

Page 34 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 14: 9326 d2U v2 + 9341 RRH

OPTICAL TRANSMISSION
RRH is the master for the optical transmission with the NodeB. The NodeB is the slave and only
transmits if it receives a signal from the master.
In case of optical link failure, the RRH restarts and periodically try to resend. Meanwhile the NodeB
has lost the reception signal, it cuts the laser transmission.
The laser used in the optical transceiver is in Class 1 Laser product per FDA/CDRH and IEC-60825
standards. A class 1 laser is safe under all conditions of normal use. This means the maximum
permissible exposure (MPE) cannot be exceeded.
In UA07.1, it can be possible to connect up to 6 RRH per NodeB in star and/or daisy chain
configuration

Figure 15: Star / daisy chain configuration

2 kinds of Node B cells exist:

- Local cells that are managed by RF modules inside the Node B (TRM/PA/DDM or TRDU). The RF
interface of local cells is at Node B bulkhead level.
- Remote cells that are managed by RRH. The RF interface of remote cells is at RRH bulkhead level

EMTS 3G UTRAN LLD

Page 35 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

9341 RRH60-21 A Configuration

Table 13: 9341 RRH60-21 A RF Characteristics

Table 14: 9341 RRH60-21 A Optical Characteristics

4.2.3 Node B Software Release

The following licensed software will be operating on the Node B in Etisalat Nigeria network
Software Item
Node B Load

Software Version
UA07.1.1.7 EP3

Table 15: Node B Software load

4.2.4 Node B Configuration Parameters

Following tables are examples of the main Node B parameters to be configured during the Node B
Integration.
For more details, please refer to the sheets related to NodeB/BTS in RNC CIQ files.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 36 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

The BTS equipment is configured with 2 carriers, hence RRH2 configuration

The BTS equipment information is provided in the BTS Equipment sheet, as shown in following table
Second
Local
RRH
RRH
ne
hsdpaHardware iRMLCGRep
tmaAccessT Altitud Longitu Latitud
RNC
BTSEquipment
Version
Configur Configur
Cluster
Id
Allocation
ortMode
ype
e
de
e
ation
ation
Configur
ation
LGRL
07_01_0 No
U3000_GOVONOR'S OFFICE_OD
203
0
te
None
RRH2 xcemPreference SharedPool no_RRH
noTMA
45
3.36594 6.6111

RfCarrier
instance

dlFrequencyN frequency ulFrequencyN

umber
Band
umber

0/1

10662 / 10687

2100

9712 / 9737

Table 16: Node B parameters BTS equipment

Note that neId is corresponding to the BTS serial number which the actual value will be retrieved from Node B commissioning. The neId in CIQ is a dummy
value till getting the update from commissioning.

The BTS Cell information is provided in the NodeB BTSCell sheet, as shown in following table. BTSCell 0 to 2 correspond to F1, BTS cell 3 to 5 to F2.
HSPA service is configured only on 2nd frequency hence hspaResourceActivation and eDchresourceActivation=false for F1 and true for F2
RNC

BTSEquipment

BTSCell localCellId cellSize

edchResource

hsdpaResource

Activation

paRatio dualCell ctivation

hsdpaHardware
Allocation

LGRL203 U3000_GOVONOR'S OFFICE_OD

30001

from5to10

FALSE

xcemPreference

LGRL203 U3000_GOVONOR'S OFFICE_OD

30002

from5to10

FALSE

xcemPreference

LGRL203 U3000_GOVONOR'S OFFICE_OD

30003

from5to10

FALSE

xcemPreference

LGRL203 U3000_GOVONOR'S OFFICE_OD

30005

from5to10

yes

FALSE

xcemPreference

LGRL203 U3000_GOVONOR'S OFFICE_OD

30006

from5to10

yes

FALSE

xcemPreference

LGRL203 U3000_GOVONOR'S OFFICE_OD

30007

from5to10

yes

FALSE

xcemPreference

Table 17: Node B parameters BTS Cell

The NodeB Fdd Cell information is provided in the NodeB_FddCell sheet, as shown in following table
The following conventions are used:

For cell name = BTSname + _A for 1st cell, _B for 2nd cell, _C for 3rd cell. For 2nd frequency, _E,_F,_G are used

EMTS 3G UTRAN LLD

Page 37 of 113

Version draft 0.7

Twin cell ID is the cell of the same sector on the other frequency: hence cell A is twin of Cell E (and reciprocial), B F, CG

CellID=localCellID=ServiceAreaCode

RNC

NODEBID

FDDCell

LGRL203

3000

U30001_GOVONOR'S OFFICE_OD_A

Local CellId Cellid

30001

Scrambling Code locationArea Code routingArea Code serviceAreaCode IMCTA Mode twin Cell ID
132

32031

30001

All

30005

LGRL203

3000

U30002_GOVONOR'S OFFICE_OD_B

30002

32031

30002

All

30006

LGRL203

3000

U30003_GOVONOR'S OFFICE_OD_C

30003

133

32031

30003

All

30007

LGRL203

3000

U30005_GOVONOR'S OFFICE_OD_E

30005

132

32031

30005

All

30001

LGRL203

3000

U30006_GOVONOR'S OFFICE_OD_F

30006

32031

30006

All

30002

LGRL203

3000

U30007_GOVONOR'S OFFICE_OD_G

30007

133

32031

30007

All

30003

Table 18: Node B parameters FDD Cell

The rest of the table is shown below.

ulFrequency

dlFrequency

Number

U30001_GOVONOR'S OFFICE_OD_A

9712

10662

6.6111

North

3.36594

TBD

3000

U30002_GOVONOR'S OFFICE_OD_B

9712

10662

6.6111

North

3.36594

TBD

LGRL203

3000

U30003_GOVONOR'S OFFICE_OD_C

9712

10662

6.6111

North

3.36594

TBD

LGRL203

3000

U30005_GOVONOR'S OFFICE_OD_E

9737

10687

6.6111

North

3.36594

TBD

LGRL203

3000

U30006_GOVONOR'S OFFICE_OD_F

9737

10687

6.6111

North

3.36594

TBD

LGRL203

3000

U30007_GOVONOR'S OFFICE_OD_G

9737

10687

6.6111

North

3.36594

TBD

RNC

NODEBID

FDDCell

LGRL203

3000

LGRL203

latitude

latitudeSign longitude maxTxPower pcpichPower

Table 19: Node B parameters FDD Cell (continued)

EMTS 3G UTRAN LLD

Page 38 of 113

Version draft 0.7

The description of the site is given in the sheet Site Info

These are mainly RF planning parameters related to the antenna characteristics (height, azimuth, radiation pattern, mechanical and electrical down tilt)

RNC

NodeB

NODEBID

Sector Id

LGRL203

U3000_GOVONOR'S OFFICE_OD

3000

Sector/0

LGRL203

U3000_GOVONOR'S OFFICE_OD

3000

Sector/1

LGRL203

U3000_GOVONOR'S OFFICE_OD

3000

Sector/2

Azimuth

Height

270

330

Antenna Type

ANT*1710-2170_65_18_V010T_Xpol_RET
ANT*1710-2170_65_18_V010T_Xpol_RET
ANT*1710-2170_65_18_V010T_Xpol_RET

Table 20: Site Info parameters

EMTS 3G UTRAN LLD

Page 39 of 113

Version draft 0.7

Downtilt

Electrical downtilt

4.2.5 Node B Synchronization

Synchronization is a key feature in mobile packet transport. As illustrated in below, the need for
synchronization is motivated by:

Radio framing accuracy (1)

Handoff control (no dropped call handovers) (2)

Backhaul transport (no data slips) (3)

Figure 16: Needs for Synchronization

Different type of Node B synchronization methods:

IEEE 1588 v2 The Precision Time Protocol (referred also as PTP)

Local GPS Using a local GPS receiver for synchronization.

E1/T1 line timing The NodeB can continue to use the E1/T1 line timing as a clock
reference in native IP mode, but the E1/T1 line will be used only for synchronization and
will not carry any data traffic.

Synchronous Ethernet This will be supported only on an xCCM/xCCM-U equipped with a

Gigabit Ethernet MDA. This method will be available in UA07.1.2

Table 21: Node B synchronization methods

EMTS 3G UTRAN LLD

Page 40 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

The different possibilities are illustrated with the picture below

In Etisalat NIGERIA UTRAN, the chosen synchronization method is Option 3 Line synchronization
through STM1 and E1s since we still have an ATM connection to the RNC via Iub.

Figure 17: Synchronization Methods for RNC

In Etisalat Nigeria network, the synchronization is done via the Iub, with a primary Clock (card in
slot 8 / port 0 = card 16pOC3 / port 0 being the port for Iub card 8 is the active card by default)
RNC-IN Primary Reference Clock

Lp8/Sdh 0

For synchronisation from Iub

RNC-IN Secondary Reference Clock

Lp9/Sdh 0

For synchronisation from Iub

Table 22: RNC synchronisation parameters

BTSEquipment/U3130

synchronizationMethodList

dedicatedE1T1

Table 23 BTS synchronisation parameters

4.2.6 Node B Capacity Licenses

The Node B Capacity Licensing feature allows reduced initial costs by tailoring the BTS capacities
and providing the possibility to Pay as you Grow. The principle is to limit the capacity of the
Node Bs by a license and to update the license when the traffic grows.
In UA07.1, there are 11 parameters concerning to Node B Capacity Licensing feature.
For Etisalat NIGERIA Network, a generic package with temporary license with no limitation of
capacity to be provided.
Afterwards, the parameters to be updated with the finite permanent values see below table.

EMTS 3G UTRAN LLD

Page 41 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Table 24: Node B Capacity Licensing parameters

The customer has a permanent and infinite capacity licensing.

4.2.7 Feature Licenses

The Feature Licensing is introduced in UA07 release. The features involved in the licensing
management are:

Adaptive Multi-Rate Low Rate package

iMCRA

HSDPA -64 QAM

Video Telephony FallBack To Speech

End User Mobility Improvement

Advanced Location Services

MBMS Multimedia Broadcast

Native IP IuB

RNC IP IuCS

RNC IP Iur

Advanced Receiver

Multi Operator Core Network

Automatic Carrier Switch Off

New Services Enabler Thru Rab Modifications

For Etisalat NIGERIA Network, all these features are offered except for Native IP IuB instead Hybrid
Iub is provided, so the associated feature licensing parameters are set to infinite values.

EMTS 3G UTRAN LLD

Page 42 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.3.

IuCS

IuCS interface provides a connection between RNC and CS core network (MSC and MGW)
IuCS is supported either on ATM or on IP. However, IuCS Control Plane and User Plane must be on
the same transport layer (either both on IP or both on ATM).
For Etisalat NIGERIA network, the chosen configuration is IuCS traffic carried over an IP transport
network.
With a CS R4 CN, Alcatel RNC sends the Control Plane part to the MSC and the User plane part to
the MGW.

In this IuCS over IP solution, RNC must be connected to an IP backbone through a layer 3 access
router (two routers are needed in case of the IP redundancy) providing IP routing, DiffServ
forwarding and L3 Carrier Grade.
o

In Lagos: 1 RNC has IuCS over IP connection through a pair of 7750 SR-7

In Benin: 1 RNC has IuCS over IP connection through a pair of 7750 SR-7

4.3.1 IuCS/IP protocol stack

Here is on overview of the protocol stack on the IuCS over IP.

Figure 18: IuCS over IP protocol stack

EMTS 3G UTRAN LLD

Page 43 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.3.2 IuCS User Plane

4.3.2.1

IuCS/IP UP in the RNC:

The IuCS user plane connection terminates on the RNC within the PMC-PC assigned to the specific
RTP session. The IuCS user plane traffic from a given MGW is distributed across all the PMC-PC
configured on the RNC.
The number of PMC-PC per RNC depends on the number of DCPS cards installed. One DCPS contains
one PMC-PC. Maximum 12 DCPS (i.e. also 12 PMC-PC) is possible in a RNC.
A /28 IP subnet (max 14 host id) is required for addressing all PMC-PC as for IuCS/IP user plane
termination.
Following tables present the RNC IuCS user plane IP subnet defined for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuCS sheet)
RNC: Lagos RNC

Subnet (16 IPs)

Network @
Range
Broadcast
VR IuCS_UPLANE LocalMedia
Subnet Mask
VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/
IU CS PC1 @
IU CS PC2 @
IU CS PC3 @
..

RNC IuCSUP-IP
PC @
10.1.0.112/28
10.1.0.112
10.1.0.113-10.1.0.126
10.1.0.127
10.1.0.126
255.255.255.240/28
VR/8
PP/IUCS_UPLANE
If/11
iucs
uplane
1500
PP/GIGE1
PP/GIGE2
10.1.0.113
10.1.0.114
10.1.0.115

Table 25: RNC IuCS user plane IP subnet - Lagos RNC

RNC: Benin RNC

Subnet (16 IPs)

Network @
Range
Copyright Alcatel-Lucent

RNC IuCSUP-IP
PC @
10.1.2.112/28
10.1.2.112
10.1.2.113-10.1.2.126
EMTS 3G UTRAN LLD

Page 44 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Broadcast
VR IuCS_UPLANE LocalMedia
Subnet Mask
VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/

10.1.2.127
10.1.10.126
255.255.255.240/28
VR/8
PP/IUCS_UPLANE
If/11
iucs
uplane
1500
PP/GIGE1
PP/GIGE2
10.1.2.113
10.1.2.114
10.1.2.115

IU CS PC1 @
IU CS PC2 @
IU CS PC3 @
..

Table 26: RNC IuCS user plane IP subnet - Benin RNC

UDP Ports in the RNC:

One PMC-PC supports 16,000 UDP ports in the range [49152,.., 65535]
The number of PMC-PC depends on the number of DCPS board installed in the RNC i.e. 1 PMC-PC
per DCPS
On the IuCS, two source and four destination UDP ports from the RNC UDP port range are assigned
per UE connection (in case IuFlex not activated)
-

One pair of UDP port for RTP and

One pair of UDP port for RTCP (even if not used)

So,
LGRL203 (10 DCPS): total UDP ports = 16,000 port * 10 PMC-PC = 160,000 ports -> then 80,000 ports
for RTP and remaining 80,000 ports reserved for RTCP
BNRL204 (10 DCPS): total UDP ports = 16,000 port * 10 PMC-PC = 160,000 ports -> then 80,000 ports
for RTP and remaining 80,000 ports reserved for RTCP

4.3.2.2

IuCS/IP UP in the CS Core network:

In case the CS core network is Bearer Independent Core Network (BICN) architecture, within BICN,
the MGC (or Huawei MSC) is in charge of handling UMTS call Control RANAP protocol, whereas the
MGW is in charge of handling the bearer user plane. The BICN is composed of one MGC and one or
several MGW(s).
The IuCS/IP user plane connection (RTP session) are terminated on the CS CN side at MGW(s).
Table below present the remote (MGW) IuCS user plane IP subnet defined for Etisalat NIGERIA
network. These data are extracted from RNC CIQ files (IP IuCS sheet)

EMTS 3G UTRAN LLD

Page 45 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Remote User Plane Subnet

(MGW)
10.67.85.0, 10.67.85.128
10.67.65.0, 10.67.65.128
10.67.109.0, 10.67.109.128

Subnet Mask
255.255.255.128
255.255.255.128
255.255.255.128

MGW
BNMG01
LGMG01
IKMG01

Table 27: MGW IuCS user plane IP subnet for all RNC

4.3.2.3

IP Components for IuCS/IP in RNC

A CS core network (e.g. one BICN) is identified in the RNC by an IuCSIf instance.

Figure 19: RNC IuCS/IP IP Components

Under the IuCSIf component, one single ipIf instance identified the CS core network user plane
over IP.
The Bandwidth Pool (BwPool) is always present under an IuCS ipIf. One Single Bwpool is configured
under ipIf component. The IuCS BwPool must be linked to a transport Map table.
TransportMap (Tm) provides the IuCS UMTS to DSCP QoS mapping. Tm/5 is recommended for IuCS
over IP. Refer to Appendix 5.2 for Tm/5 table.
The IP Flow (corresponding to one stream) is a subcomponent of the BwPool. A BwPool can be
configured with up to 4 IpFlow called qos0, qos1, qos2 and qos3.
For IuCS BW pool, it has a single IP flow to manage CS traffic (QoS 0).
IuCS/IP stream definition for Etisalat NIGERIA network is shown below. These data are extracted
from RNC CIQ files (IP IuCS sheet)

Stream
1

Bwpool
1

Plmn
621-60

TransportMap
Tm/5

QoS
0

IpFlow Id
1

Table 28: IuCS/IP stream definition for all RNC

4.3.2.4

Bandwidth Pools CAC for IuCS/IP in RNC

IuCS BW pool has a single IP flow to manage CS traffic (QoS 0)

flow is configured with Committed Information Rate (CIR) and Peak Information Rate (PIR)
corresponding to IuCS User plane BW between RNC and CN, CIR and PIR must be set accordingly
with the IuCS user plane BW = 2*PIR*CIR/(CIR+PIR): default is 100 Mbps
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 46 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

IP
Figure 20: IuCS/IP IP Flow CIR/PIR
Call Admission Control (CAC) works the following way on the bandwidth pool for IuCS:
At each new call, IP Equivalent Bit Rate (EBR) is calculated based on RAB type. EBR is provisioned
for each RAB type regardless of ATM or IP (no change from ATM) in cacTransportInfoList objects.
Then IP overhead is added.
If this EBR can be accommodated within the bandwidth pool capacity 2*PIR*CIR/(CIR+PIR), the call
is accepted. Otherwise the RAB is rejected.

4.3.2.5

VR Configuration

Separate Virtual Router for IuCS Control Plane and User Plane is chosen for Etisalat NIGERIA
network.
VR/8 is assigned for IuCS User Plane same for all RNCs:

Figure 21: IuCS User Plane VR

EMTS 3G UTRAN LLD

Page 47 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.3.2.6

GE Configuration

To transmit/receive IuCS UP traffic to CS core network, each RNC will have 2 GE connections on
port 14.2 & 15.2 to two different adjacent routers see below the generic GE connection.

Figure 22: IuCS User Plane GE connection

For outgoing IuCS UP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 2 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 2 provides the standby path as higher metric (=10) defined.

Note: lower metric identifies the preferred path.

For incoming IuCS UP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuCS user plane GE configuration for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuCS sheet)
Lagos RNC

Table 29: RNC IuCS user plane GE configuration - Lagos RNC

EMTS 3G UTRAN LLD

Page 48 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

RNC: Benin RNC

Table 30: RNC IuCS user plane GE configuration - Benin RNC

4.3.3 IuCS Control Plane

4.3.3.1

SIGTRAN Configuration

For the IuCS control plane over IP, the protocol stack includes SCCP, M3UA and SCTP, a reliable
transmission protocol defined by the IETF. Refer to section 4.3.1

M3UA: M3UA is used in Application Server Process (ASP) mode (not officially supported by
Alcatel Lucent) to interconnect with Huawei CS CN
Indeed Huawei CS Core network uses the MGW as a Signaling Gateway Point (SGP) towards
MSC that shall end the M3UA connection
The Huawei MGW provide the IuFlex function and selects the destination Core network
(MSC) that will handle the call.

ASP
MSC

SGP
IP
Network

IP
Network

MGW

RNC

Figure 23: IuCS/IP CP M3UA signaling type

In Alcatel-Lucent RNC solution, PMC-NI serves as M3UA endpoint
Below present the RNC IuCS Control plane M3UA setting for Lagos RNC network.

Network indicator

3 - NationalSpare

SS7 destination Point Code CS

1550

M3UA signalling type

M3UA traffic mode

ASP
M3UA_LOADSHARE_MOD

Table 31: CS CN Network Indicator and Point code

M3UA Routing Context and Network Appearance

EMTS 3G UTRAN LLD

Page 49 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

SIGTRAN message exchange contains two optional parameters, Routing context & Network
appearance. These parameters are not supported in the RNC.
Likewise, these parameters must also be disabled at WCS.

SCTP:
According to 3GPP specifications, SCTP (Stream Control Transmission Protocol) is used as control
plane transport layer for UTRAN IP interfaces.
SCTP endpoint:
In Alcatel-Lucent RNC solution, PDC serves as SCTP endpoint, with one IP@ per PDC. The
corresponding peer SCTP endpoint terminated at WCS.
Maximum number of PDC per RNC is 10, so one /28 IP subnet is required for addressing PDC SCTP
endpoints.
Following tables present the RNC IuCS CP IP subnet defined for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (IP IuCS sheet)

RNC: Lagos RNC LGRL203

Table 32: RNC IuCS Contorl plane IP subnet LGRL203

RNC: Benin RNC BNRL204

Table 33: RNC IuCS Contorl plane IP subnet BNRL204

For Etisalat NIGERIA network:
Two PDCs on DCPS slot 6 & 7 are configured as two source SCTP endpoints in the RNC for IuCS.
1 PMP on each WCS is configured with 2 ip addresses as two peer SCTP endpoints for the RNC IuCS,
except for Aabuja WCS which is configured with 2 PMPs each with 2 IP addresses as 4 peer SCTP
end points.

EMTS 3G UTRAN LLD

Page 50 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

SCTP associations:
SCTP association is a logical connection between two SCTP endpoints. An association is defined by
pair: source IP@ + port number, destination IP@ + port number.
The port number 20050 is reserved in RNC PDC to carry M3UA over SCTP.
The port number 20050 also used in MSC this information is given by CS Core Network team.
For Etisalat NIGERIA network: as 2 source SCTP endpoints in the RNC and total 8 peer SCTP
endpoints in 4 WCSs (2 endpoints per WCS), so total 16 SCTP associations are configured for each
RNC. This configuration can provide load sharing & redundancy among the SCTP associations.

SCTP Multi-homing:
The feature multihoming enables SCTP endpoints to support multiple IP addresses.
Multihoming is supported and required on the WCS side.
Multihoming is not supported in RNC but RNC supports multihoming for the far end point, which
means that we can have 2 IP address per peer endpoint. This is called asymmetric multihoming
Following Figures and Tables show the IuCS SCTP configuration for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (IP IuCS sheet).
RNC: LGRL203
CS Core Network

PSFP slot
(SCTP Id)

Source
SCTP IP@

Source
SCTP port

Peer SCTP
IP@

Peer
SCTP port

Peer
WCS

CsCoreNetworkAccess/0

10.1.0.97

20050

10.67.108.2

20050

IKMG01 1550

CsCoreNetworkAccess/0

10.1.0.97

20050

10.67.108.130

20050

IKMG01 1550

CsCoreNetworkAccess/0

10.1.0.98

20050

10.67.108.2

20050

IKMG01 1550

CsCoreNetworkAccess/0

10.1.0.98

20050

10.67.108.130

20050

IKMG01 1550

DPC

Table 34: IuCS SCTP association configuration LGRL203

RNC: BNRL204

CS Core Network

PSFP slot
(SCTP Id)

Source
SCTP IP@

Source
SCTP port

Peer SCTP
IP@

Peer SCTP
port

Peer
WCS

CsCoreNetworkAccess/0

10.1.2.97

2095

10.67.84.2

2095

BNMG01 1557

CsCoreNetworkAccess/0

10.1.2.97

2095

10.67.84.130

2095

BNMG01 1557

CsCoreNetworkAccess/0

10.1.2.98

2095

10.67.84.2

2095

BNMG01 1557

CsCoreNetworkAccess/0

10.1.2.98

2095

10.67.84.130

2095

BNMG01 1557

Table 35: IuCS SCTP association configuration BNRL204

4.3.3.2

VR Configuration

Separate Virtual Router for IuCS Control Plane and User Plane is chosen for Etisalat NIGERIA
network.
VR/9 is assigned for IuCS Control Plane same for all RNCs:

EMTS 3G UTRAN LLD

Page 51 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

DPC

Figure 24: IuCS Control Plane VR

4.3.3.3

GE Configuration

To transmit/receive IuCS CP traffic to CS core network, each RNC will have 2 GE connections on
port 14.2 & 15.2 to two different adjacent routers see below the generic GE connection.

Figure 25: IuCS Control Plane GE connection

For outgoing IuCS CP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 2 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 2 provides the standby path as higher metric (=10) defined.

Note: lower metric identifies the preferred path.

For incoming IuCS CP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuCS Control plane GE configuration for Etisalat NIGERIAnetwork.
These data are extracted from RNC CIQ files (IP IuCS sheet)
RNC: Lagos
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 52 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC IuCSCP-IP
4pGIGE1 IF @ (Card 14)
10.1.0.208/30
10.1.0.208
10.1.0.209-10.1.0.210
10.1.0.211
255.255.255.252/30
912

RNC IuCSCP-IP
4pGIGE2 IF @ (Card 15)
10.1.0.212/30
10.1.0.212
10.1.0.213-10.1.0.214
10.1.0.215
255.255.255.252/30
916

10.1.0.209
10.1.0.210
5

10.1.0.213
10.1.0.214
10

Table 36: RNC IuCS control plane GE configuration LGRL203

RNC: Benin RNC

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC IuCSCP-IP
4pGIGE1 IF @ (Card 14)
10.1.2.208/30
10.1.2.208
10.1.2.209-10.1.2.210
10.1.2.211
255.255.255.252/30
962

RNC IuCSCP-IP
4pGIGE2 IF @ (Card 15)
10.1.2.212/30
10.1.2.212
10.1.2.213-10.1.2.214
10.1.2.215
255.255.255.252/30
966

10.1.2.209
10.1.2.210
5

10.1.2.213
10.1.2.214
10

Table 37: RNC IuCS control plane GE configuration BNRL204

4.3.4 IuCS Flex

IMPORTANT NOTE: In case of a pool of several MSC, the CS Core Network Node Selection Function
(NNSF) (.i.e. decision of which MSC will handle the call) can either be performed

by the UTRAN network, this is called IuFlex.

Or it can be performed by the CS Core Network (MGW providing the IuFlex) , this is the
current solution supported by Huawei CS CN

But both NNSF functions can not be activated at the same time on UTRAN and CN: the selection of
the CS core can only be performed by a single entity.
To be confirmed whether NNSF by Core CS can be deactivated! If not, IuFlex will probably not be
used, and the datafill of table x will not be valid, and the rest of this section will NOT APPLY.

In Etisalat NIGERIA network, there are 4 WCS and 2 Media gateways. They are geographically
distributed throughout 3 sites. For MSC we have 3 MSCs in Lagos and 1 MSC in Abuja, for MGWs, we
have 1 MGW in Lagos and 1 MGW in Benin. With Iu-flex, the core network elements are configured
to serve in the same resource pool with the same Iu-Flex domain.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 53 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Following tables present the RNC IuCS Flex configuration for Etisalat NIGERIA network. These data
are extracted from RNC CIQ files (IP IuCS sheet)
The traffic is equally distributed across the 4 MSC

Table 38: RNC IuCS Flex configuration all RNC

IuCS flex will not be deployed in EMTS Nigeria anymore.

4.3.5 IuCS IP Addressing

Figure 26: IuCS IP Addressing LGRL203

EMTS 3G UTRAN LLD

Page 54 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.4.

IuPS

IuPS interface provides a connection between RNC and PS core network (SGSN)
IuPS is supported either on ATM or on IP. However, IuPS Control Plane and User Plane must be on
the same transport layer (either both on IP or both on ATM).
For Etisalat NIGERIA network, the chosen configuration is IuPS traffic carried over an IP transport
network
In this IuPS over IP solution, RNC must be connected to an IP backbone through a layer 3 access
router (two routers are needed in case of the IP redundancy) providing IP routing, DiffServ
forwarding and L3 Carrier Grade.
o

In Lagos : 1 RNCs have IuPS over IP connection through a pair of 7750 SR-7

In Benin: 1 RNC has IuPS over IP connection through a pair of 7750 SR-7

4.4.1 IuPS/IP protocol stack

Here is on overview of the protocol stack on the IuPS over IP.

Figure 27: IuPS over IP protocol stack

EMTS 3G UTRAN LLD

Page 55 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.4.2 IuPS User Plane

4.4.2.1

IuPS/IP UP in the RNC:

The User IP packet is sent between RNC and SGSN on a GTP-U tunnel which is carried over an IP
backbone. The tunnel is identified by GTP-U TEID (source and destination) and IP address (source
and destination). There may be one or several IP addresses in the RNC and in the CN.
The IP addresses and GTP TEID are exchanged between RNC and SGSN by using RANAP protocol.
The Transport Layer Address IE contains the IP address and the Iu Transport Association IE contains
the GTP TEID.
In RNC, GTP-U is terminated on PMC-RAB (dynamically allocated, per call). Each PMC-RAB has its
own IP address and manages several GTP endpoints (GTP Tunnel End Point Identifier (TEID)).

The number of PMC-RAB per RNC depends on the number of DCPS cards installed. Maximum 40
PMC-RAB is for a RNC with maximum 12 DCPS cards.
A /26 IP subnet (max 62 host id) is required for addressing all PMC-RAB as for IuPS/IP user plane
termination.
Following tables present the RNC IuPS user plane IP subnet defined for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuPS sheet)
RNC: Lagos

Subnet (40 IPs)

Network @
Range
Broadcast
VR IuPS_UPLANE LocalMedia
Subnet Mask
VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/

RNC IuPsUP-IP
RAB/GTP @
10.1.0.0/26
10.1.0.0
10.1.0.1-10.1.0.62
10.1.0.63
10.1.0.62
255.255.255.192/26
VR/1
PP/UPLANEIUPS
If/3
iups
uplane
1500
PP/GIGE1
PP/GIGE2

Table 39: RNC IuPS user plane IP subnet - Lagos RNC

RNC: Benin

Subnet (40 IPs)

Network @
Range
Copyright Alcatel-Lucent

RNC IuPsUP-IP
RAB/GTP @
10.1.2.0/26
10.1.2.0
10.1.2.1-10.1.2.62
EMTS 3G UTRAN LLD

Page 56 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

10.1.2.63
10.1.2.62
255.255.255.192/26

Broadcast
VR IuPS_UPLANE LocalMedia
Subnet Mask
VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/

VR/1
PP/UPLANEIUPS
If/3
iups
uplane
1500
PP/GIGE1
PP/GIGE2

Table 40: RNC IuPS user plane IP subnet - Benin RNC

4.4.2.2

IuPS/IP UP in the PS Core network:

The IuPS/IP user plane connection (GTP-U tunnel) is terminated on the PS CN side at SGSN.
In Etisalat NIGERIA network, there is only one SGSN. Every RNC is connected to this SGSN through
an IP network.
We will define a default route to this SGSN:
Table below present the remote (SGSN) IuPS user plane IP subnet defined for Etisalat NIGERIA
network. The IP addresses are dynamically assigned by the SGSN for each call.

SGSN Subnet Addresses

SGSN subnet adresses mask

10.88.0.10/28
10.88.0.11/28
10.88.0.12/28

10.88.0.0/28
10.88.0.0/28
10.88.0.0/28

Table 41: SGSN IuPS user plane IP subnet for all RNC
For the User Plane, the mechanism to check the path availability between RNC and SGSN (GGSN in
case of direct tunnel) is based on sending GTP Echo Request messages periodically
This mechanism is currently activated on Huawei SGSN.
It shall therefore be activated on RNC under object RNC/IN/EM/IuPS/1
Parameter

Value

gtpEchoEnabled
gtpEchoReqAttempts
gtpEchoReqInterval
gtpEchoRspTime

EMTS 3G UTRAN LLD

true
5
1
2

Page 57 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.4.2.3

IP Components for IuPS/IP in RNC

A PS core network (e.g. one SGSN) is identified in the RNC by an IuPSIf instance.
Unlike IuCS, ipIf component is not supported on IuPS.
Since no ipIf component on IuPS, all ipIf subcomponents (BwPool and Ipflow) are also not available
for IuPS.
TransportMap (Tm) is not required for IuPS, because the IuPS UMTS to DSCP QoS mapping is
configured in the MIB.

4.4.2.4

VR Configuration

Separate Virtual Router for IuPS Control Plane and User Plane is chosen for Etisalat NIGERIA
network.
VR/1 is assigned for IuPS User Plane same for all RNCs:

Figure 28: IuPS User Plane VR

4.4.2.5

GE Configuration

To transmit/receive IuPS UP traffic to PS core network, each RNC will have 2 GE connections on
port 14.1 & 15.1 to two different adjacent routers see below the generic GE connection.

Figure 29: IuPS User Plane GE connection

EMTS 3G UTRAN LLD

Page 58 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

For outgoing IuPS UP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 1 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 1 provides the standby path as higher metric (=10) defined.

Note: lower metric identifies the preferred path.

For incoming IuPS UP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuPS user plane GE configuration for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuPS sheet)

RNC: Lagos LGRL203

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC IuPsUP-IP
4pGIGE1 IF @ (Card 14)
10.1.0.184/30
10.1.0.184
10.1.0.185-10.1.0.186
10.1.0.187
255.255.255.252/30
901

RNC IuPsUP-IP
4pGIGE2 IF @ (Card 15)
10.1.0.188/30
10.1.0.188
10.1.0.189-10.1.0.190
10.1.0.191
255.255.255.252/30
905

10.1.0.185
10.1.0.186
5

10.1.0.189
10.1.0.190
10

Table 42: RNC IuPS user plane GE configuration LGRL203

RNC: Benin BNRL204

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC IuPsUP-IP
4pGIGE1 IF @ (Card 14)
10.1.2.184/30
10.1.2.184
10.1.2.185-10.1.2.186
10.1.2.187
255.255.255.252/30
951

RNC IuPsUP-IP
4pGIGE2 IF @ (Card 15)
10.1.2.188/30
10.1.2.188
10.1.2.189-10.1.2.190
10.1.2.191
255.255.255.252/30
955

10.1.2.185
10.1.2.186
5

10.1.2.189
10.1.2.190
10

Table 43: RNC IuPS user plane GE configuration BNRL204

EMTS 3G UTRAN LLD

Page 59 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.4.3 IuPS Control Plane

4.4.3.1

SIGTRAN Configuration

For the IuPS control plane over IP, the protocol stack includes SCCP, M3UA and SCTP, a reliable
transmission protocol defined by the IETF. Refer to section 4.4.1

M3UA: the connection is via IPSP (IP server Process) since both RNC and PS CN support SS7 over IP
transport, and can communicate directly (contrary to IuCS)

IPSP

IPSP
IP
Network

CNE

RNC

Figure 30: IuPS/IP CP M3UA signaling type

In Alcatel-Lucent RNC solution, PMC-NI serves as M3UA endpoint

Below present the RNC IuPS Control plane M3UA setting for Etisalat NIGERIA network. These data
are extracted from RNC CIQ files (RNC sheet)

Table 44: PS CN Network Indicator and Point code

In RNC CIQ files (IP IuPS sheet)
M3UA signalling type
M3UA traffic mode

IPSP
M3UA_LOADSHARE_MOD

Table 45: RNC IuPS Control plane M3UA setting all RNCs

M3UA Routing Context and Network Appearance

SCTP:
According to 3GPP specifications, SCTP (Stream Control Transmission Protocol) is used as control
plane transport layer for UTRAN IP interfaces.

SCTP endpoint:
In Alcatel-Lucent RNC solution, PDC serves as SCTP endpoint, with one IP@ per PDC. The
corresponding peer SCTP endpoint terminated at SGSN.
Maximum number of PDC per RNC is 10, so one /28 IP subnet is required for addressing PDC SCTP
endpoints.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 60 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Following tables present the RNC IuPS CP IP subnet defined for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (IP IuPS sheet)

RNC: Lagos LGRL203

RNC1
RNC IuPsCP-IP
PDC/STCP @
10.1.0.80/28
10.1.0.80
10.1.0.81-10.1.0.94
10.1.0.95

Subnet (16 IPs)

Network @
Range
Broadcast
VR IuPS_CPLANE
LocalMedia
Subnet Mask

10.1.0.94
255.255.255.240/28

VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface
Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/

VR/7
PP/IUPS_CPLANE
If/7

M3UA signalling type

M3UA traffic mode

IPSP
M3UA_LOADSHARE_MOD

iups
ss7Cplane
9180
PP/GIGE1
PP/GIGE2

10.1.0.81
10.1.0.82

PDC1/STCP @
PDC2/STCP @
STCP port @

2905

SCTP/2 PMP/0 assoc/0

STCP/3 PMP/1 assoc/0

SCTP/2 (10.1.0.81)
SCTP/3 (10.10.82)

10.87.0.1
10.87.0.1

Table 46: RNC IuPS Contorl plane IP subnet LGRL203

RNC: Benin BNRL204

Subnet (16 IPs)

Network @
Range
Broadcast
VR IuPS_CPLANE
LocalMedia
Subnet Mask
Copyright Alcatel-Lucent

RNC IuPsCP-IP
PDC/STCP @
10.1.2.80/28
10.1.2.80
10.1.2.81-10.1.2.94
10.1.2.95
10.1.2.94
255.255.255.240/28
EMTS 3G UTRAN LLD

Page 61 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

VR/7
PP/IUPS_CPLANE
If/7

VR
@ PP/
@ PP/LocalMedia If/
@ PP/LocalMedia interface
Type
@ PP/LocalMedia Traffic Type
@ PP/LocalMedia MTU
@ PP/
@ PP/

iups
ss7Cplane
9180
PP/GIGE1
PP/GIGE2

M3UA signalling type

M3UA traffic mode

IPSP
M3UA_LOADSHARE_MOD
10.1.2.81
10.1.2.82

PDC1/STCP @
PDC2/STCP @
STCP port @

2905

SCTP/2 PMP/0 assoc/0

STCP/3 PMP/1 assoc/0

SCTP/2 (10.1.2.81)
SCTP/3 (10.1.2.82)

10.87.0.1
10.87.0.1

Table 47: RNC IuPS Control plane IP subnet BNRL204

For Etisalat NIGERIA network:
Two PDCs on DCPS slot 2 & 3 are configured as two source SCTP endpoints in the RNC for IuPS.
One station on the SGSN is configured as one peer SCTP endpoint for the RNC IuPS.

SCTP associations:
SCTP association is a logical connection between two SCTP endpoints. An association is defined by
pair: source IP@ + port number, destination IP@ + port number
The port number 2905 is reserved in RNC PDC to carry M3UA over SCTP.
The port number 2905 also used in SGSN this information is given by PS Core Network team.
For Etisalat NIGERIA network: as 2 source SCTP endpoints in the RNC and 1 peer SCTP endpoints in
the SGSN, so total 2 SCTP associations are configured for each RNC. This configuration provides
load sharing & redundancy among the SCTP associations from RNC side but not from SGSN side. ALU
recommends to add another station from SGSN side.

SCTP Multi-homing:
The feature multihoming enables SCTP endpoints to support multiple IP addresses
Multihoming is supported on the SGSN side
Multihoming is not supported in RNC but RNC supports multihoming for the far end point, which
means that we can have 2 IP address per peer endpoint. This is called asymmetric multihoming.
In Etisalat NIGERIA network, we apply single homing on both RNC and SGSN sides.

EMTS 3G UTRAN LLD

Page 62 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Following Figures and Tables show the IuPS SCTP configuration for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (IP IuPS sheet).

RNC: Lagos LGRL203

Figure 31: IuPS SCTP associations LGRL203

SCTP
Associations
1
2

PSFP slot
(SCTP Id)
2
3

Source
SCTP IP@
10.1.0.81
10.1.0.82

Source
SCTP port
2905
2905

Peer SCTP
IP@
10.87.0.1
10.87.0.1

Peer
SCTP
port
2905
2905

Peer
SGSN
SGSN
SGSN

PC
1514
1514

Table 48: IuPS SCTP association configuration LGRL203

RNC: Benin BNRL204

Figure 32: IuPS SCTP associations BNRL204

EMTS 3G UTRAN LLD

Page 63 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

SCTP
Associations
1
2

PSFP slot
(SCTP Id)
2
3

Src SCTP
IP@
10.1.2.81
10.1.2.82

Src
SCTP
port
2905
2905

Peer SCTP
IP@
10.87.0.1
10.87.0.1

Peer SCTP
port
2905
2905

Peer
SGSN
SGSN
SGSN

PC
1514
1514

Table 49: IuPS SCTP association configuration BNRL204

4.4.3.2

VR Configuration

Separate Virtual Router for IuPS Control Plane and User Plane is chosen for Etisalat NIGERIA
network.
VR/7 is assigned for IuPS Control Plane same for all RNCs:

Figure 33: IuPS Control Plane VR

4.4.3.3

GE Configuration

To transmit/receive IuPS CP traffic to PS core network, each RNC will have 2 GE connections on
port 14.1 & 15.1 to two different adjacent routers see below the generic GE connection.

Figure 34: IuPS Control Plane GE connection

For outgoing IuPS CP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 64 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

GE Card slot 14 port 1 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 1 provides the standby path as higher metric (=10) defined.

Note: lower metric identifies the preferred path.

For incoming IuPS CP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuPS Control plane GE configuration for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuPS sheet)
RNC: Lagos LGRL203
RNC IuPsCP-IP

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

4pGIGE1 IF @ (Card 14)

10.1.0.192/30
10.1.0.192
10.1.0.193-10.1.0.194
10.1.0.195
255.255.255.252/30
911

RNC IuPsCP-IP
4pGIGE2 IF @ (Card
15)
10.1.0.196/30
10.1.0.196
10.1.0.197-10.1.0.198
10.1.0.199
255.255.255.252/30
915

10.1.0.193
10.1.0.194
5

10.1.0.197
10.1.0.198
10

Table 50: RNC IuPS control plane GE configuration LGRL203

RNC: Benin BNRL204
RNC IuPsCP-IP

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

4pGIGE1 IF @ (Card 14)

10.1.2.192/30
10.1.2.192
10.1.2.193-10.1.2.194
10.1.2.195
255.255.255.252/30
961

RNC IuPsCP-IP
4pGIGE2 IF @ (Card
15)
10.1.2.196/30
10.1.2.196
10.1.2.197-10.1.2.198
10.1.2.199
255.255.255.252/30
965

10.1.2.193
10.1.2.194
5

10.1.2.197
10.1.2.198
10

Table 51: RNC IuPS control plane GE configuration BNRL204

EMTS 3G UTRAN LLD

Page 65 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.4.4 IuPS IP Addressing

Figure 35: IuPS IP Addressing LGRL203

EMTS 3G UTRAN LLD

Page 66 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.5.

IuR

IuR interface provides a connection between two RNCs.

IuR is supported either on ATM or on IP. However, IuR Control Plane and User Plane must be on the
same transport layer (either both on IP or both on ATM).
The RNC supports up to 36 neighbour RNCs whatever the transport solution.
For Etisalat NIGERIA network, the chosen configuration is IuR traffic carried over an IP transport
network
In this IuR over IP solution, RNC must be connected to an IP backbone through a layer 3 access
router (two routers are needed in case of the IP redundancy) providing IP routing, DiffServ
forwarding and L3 Carrier Grade.
o

In Lagos : 1 RNC connected to a pair of 7750SR-7

In Etisalat NIGERIA network, the IuR definitions are as follows:

LGRL203: 1 IuR connection to Huawei RNC LGRH201

LGRL203: 1 IuR connection to Huawei RNC LGRH202

BNRL204: no IUR connection

The figure below shows the position of the Huawei NodeB sites in red and Alcatel Lucent NodeB
sites in blue, for the city of Lagos.

Figure 36: IuR requirement based on RF data

4.5.1 IuR/IP protocol stack

Here is on overview of the protocol stack on the IuR over IP.

EMTS 3G UTRAN LLD

Page 67 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 37: IuR over IP protocol stack

4.5.2 IuR User Plane

4.5.2.1

IuR/IP UP in the RNC:

In RNC, IuR over IP User Plane is terminated on PMC-PC (dynamically allocated). Each PC has its
own IP address.
The number of PMC-PC per RNC depends on the number of DCPS cards installed. One DCPS contains
one PMC-PC. Maximum 12 DCSP (i.e. also 12 PMC-PC) is possible in a RNC.
A /28 IP subnet (max 14 host id) is required for addressing all PMC-PC as for IuR/IP user plane
termination.
Following tables present the RNC IuR user plane IP subnet defined for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuR sheet)
RNC: Lagos RNC

Subnet (16 IPs)

Network @
Range
VR IuR_UPLANE LocalMedia
Broadcast
Subnet Mask

RNC IuRUP-IP
PC @
10.1.0.160/28
10.1.0.160
10.1.0.161-10.1.0.174
10.1.0.174
10.1.0.175
255.255.255.240/28

Table 52: RNC IuR user plane IP subnet LGRL203

EMTS 3G UTRAN LLD

Page 68 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

UDP Ports in the RNC:

One PMC-PC supports 16,000 UDP ports in the range [49152,.., 65535]
The number of PMC-PC depends on the number of DCPS board installed in the RNC i.e. 1 PMC-PC
per DCPS
On the IuR, one source and one destination UDP ports from the RNC UDP port range are assigned
per UE connection.
So,
LGRL203 (6 DCPS): total UDP ports = 16,000 port * 10 PMC-PC = 160,000 ports

4.5.2.2

IuR/IP UP in the Neighbour RNC(s):

Table below present the remote (Neighbour RNCs) IuR user plane IP subnet defined for Etisalat
NIGERIA network. These data are extracted from RNC CIQ files (IP IuR sheet)
Remote User Plane Subnet
(Neighbor RNC) / mask

Neighbour RNC

10.32.14.221/30

LGRH201

10.32.15.45/30

LGRH202
Table 53: Neighbour RNC IuR user plane IP subnet LGRL203

4.5.2.3

IP Components for IuR/IP in RNC

Each neighbour RNC is identified in the ALU local RNC by an IurIf instance.

Figure 38: RNC IuR/IP IP Components

Under the IurIf component, one single ipIf instance identified the peer RNC user plane over IP.
The Bandwidth Pool (BwPool) is always present under an IuR ipIf. One Single Bwpool under ipIf
component is an engineering recommendation. The IuR BwPool must be linked to a transportMap
table.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 69 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

TransportMap (Tm) provides the IuR UMTS to DSCP QoS mapping. Tm/5 is also recommended for
IuR over IP (same as for IuCS over IP). Refer to Appendix for Tm/5 table.
The IP Flow (corresponding to one stream) is a subcomponent of the BwPool. A BwPool can be
configured with up to 4 IpFlow called qos0, qos1, qos2 and qos3.
For IuR BW pool: when hspa streaming is enable on the IuR, it has to be 4 IP flows (QoS 0, QoS 1,
QoS 2 and QoS3).
IuR/IP stream definition for Etisalat NIGERIA network is shown below. These data are extracted
from RNC CIQ files (IP IuR sheet)

RNC: Lagos LGRL203

Bwpool

IpFlow
Id

Stream

Plmn

Transp
ortMap

QoS

Neighbour
RNC

621-60

Tm/5

LGRH201

621-60

Tm/5

LGRH201

621-60

Tm/5

LGRH201

621-60

Tm/5

LGRH201

621-60

Tm/5

LGRH202

621-60

Tm/5

LGRH202

621-60

Tm/5

LGRH202

621-60

Tm/5

LGRH202

Table 54: IuR/IP stream definition LGRL203

4.5.2.4

Bandwidth Pools CAC for IuR/IP in RNC

The recommended configuration chosen for Etisalat is to have a single Bandwidth Pool with type
SharedForAllTrafficTypes:
4 Qos Ipflows (QoS 0, QoS 1, QoS 2 and QoS3) are configured by default for Voice, Streaming, DCH
I/B and HSPA I/B with the CIR/PIR adapted to the IuR Bandwidth.
CIR/PIR must be compliant with CAC Equivalent Rate computation: 2*PIR*CIR/(CIR+PIR)
Here are the recommended CIR/PIR values for IuR to be updated
Downlink

Downlink

CIR

PIR

IpFlow

Version

Model

qos

07_01_00

INode

07_01_00

INode

07_01_00

INode

07_01_00

INode

Uplink

CIR

PIR

Table 55: IuR/IP IP Flow CIR/PIR

EMTS 3G UTRAN LLD

Page 70 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.5.2.5

VR Configuration

Separate Virtual Router for IuR Control Plane and User Plane is chosen for Etisalat NIGERIA network.
VR/10 is assigned for IuR User Plane same for all RNCs:

Figure 39: IuR User Plane VR

4.5.2.6

GE Configuration

To transmit/receive IuR UP traffic to Neighbor RNC, each RNC will have 2 GE connections on port
14.3 & 15.3 to two different adjacent routers see below the generic GE connection.

Figure 40: IuR User Plane GE connection

For outgoing IuR UP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 3 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 3 provides the standby path as higher metric (=10) defined.

Note1: lower metric identifies the preferred path.

For incoming IuR UP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

EMTS 3G UTRAN LLD

Page 71 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuR user plane GE configuration for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuR sheet)
RNC: Lagos LGRL203
RNC IuRUP-IP

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id

4pGIGE1 IF @ (Card 14)

10.1.0.216/30
10.1.0.216
10.1.0.217-10.1.0.218
10.1.0.219
255.255.255.252/30
922

RNC IuRUP-IP
4pGIGE2 IF @ (Card
15)
10.1.0.220/30
10.1.0.220
10.1.0.221-10.1.0.222
10.1.0.223
255.255.255.252/30
926

10.1.0.217
10.1.0.218
5

10.1.0.221
10.1.0.222
10

@ PP/GIGE
@ Adjacent Router
PDR / METRIC

Table 56: RNC IuR user plane GE configuration LGRL203

4.5.3 IuR Control Plane

4.5.3.1

SIGTRAN Configuration

For the IuR control plane over IP, the protocol stack includes SCCP, M3UA and SCTP, a reliable
transmission protocol defined by the IETF. Refer to section 4.5.1

M3UA: the connection is via IPSP (IP server Process) since two RNCs support SS7 over IP transport
(SIGTRAN).

Figure 41: IuR/IP CP M3UA signaling type

In Alcatel-Lucent RNC solution, PMC-NI serves as M3UA endpoint
Below present the RNC IuR Control plane M3UA setting for Etisalat NIGERIA network. These data
are extracted from RNC CIQ files (IP IuR sheet)
M3UA signalling type
M3UA traffic mode

IPSP
M3UA_LOADSHARE_MOD

Table 57: RNC IuR Control plane M3UA setting all RNCs

M3UA Routing Context and Network Appearance

SIGTRAN message exchange contains two optional parameters, Routing context & Network
appearance. These parameters are not supported in the RNC.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 72 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

SCTP:
According to 3GPP specifications, SCTP (Stream Control Transmission Protocol) is used as control
plane transport layer for UTRAN IP interfaces.
SCTP is used to transport signaling in the same way it is performed with IuCS, IuPS control plane.

SCTP endpoint:
In Alcatel-Lucent RNC solution, PDC serves as SCTP endpoint, with one IP@ per PDC. The
corresponding peer SCTP endpoint terminated at neighbour RNC.
Maximum number of PDC per RNC is 10, so one /28 IP subnet is required for addressing PDC SCTP
endpoints.
Following tables present the RNC IuR CP IP subnet defined for Etisalat NIGERIA network. These data
are extracted from RNC CIQ files (IP IuR sheet)

RNC: Lagos LGRL203

Subnet (16 IPs)

Network @
Range
VR IuR_CPLANE LocalMedia
Broadcast
Subnet Mask

RNC IuRCP-IP
PDC/SCTP @
10.1.0.144/28
10.1.0.144
10.1.0.145-10.1.0.158
10.1.0.158
10.1.0.159
255.255.255.240/28

Table 58: RNC IuR Contorl plane IP subnet LGRL203

For Etisalat NIGERIA network:
Two PDCs on DCPS slot 6 & 7 are configured as two source SCTP endpoints in the Alcatel Lucent
RNC for IuR. They are the same PDCs used for IuCS SCTP endpoints.
Also, two PDCs on DCPS slot 6 & 7 on each Alcatel Lucent RNC are configured as two peer SCTP
endpoints for the RNC IuR.

SCTP associations:
SCTP association is a logical connection between two SCTP endpoints. An association is defined by
pair: source IP@ + port number, destination IP@ + port number
The port number 2905 is reserved in RNC PDC to carry M3UA over SCTP.
For Etisalat NIGERIA network: as 2 source SCTP endpoints in the RNC and 2 peer SCTP endpoints in
each neighbour RNC, so total 4 SCTP associations are configured between two RNCs. This
configuration can provide load sharing & redundancy among the SCTP associations.

SCTP Multi-homing:
The feature multihoming enables SCTP endpoints to support multiple IP addresses.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 73 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Multihoming is not supported in RNC

Following Figures and Tables show the IuR SCTP configuration for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (IP IuR sheet).

Neighbouring RNC
NeighbouringRNC/1
NeighbouringRNC/1
NeighbouringRNC/2
NeighbouringRNC/2

PSFP slot
(SCTP Id)
6
7
6
7

Source
SCTP IP@
10.1.0.145
10.1.0.146
10.1.0.145
10.1.0.146

Source
SCTP
port
1085
1085
1085
1085

Peer SCTP
IP@
10.32.6.33
10.32.6.33
10.32.6.45
10.32.6.45

Peer
SCTP
port
1085
1085
1085
1085

Peer RNC
LGRH201
LGRH201
LGRH202
LGRH202

PC
201
201
202
202

Table 59: IuR SCTP association configuration LGRL203

4.5.3.2

VR Configuration

Separate Virtual Router for IuR Control Plane and User Plane is chosen for Etisalat NIGERIA network.
VR/11 is assigned for IuR Control Plane same for all RNCs:

Figure 42: IuR Control Plane VR

4.5.3.3

GE Configuration

To transmit/receive IuR CP traffic to neighbour RNC, each RNC will have 2 GE connections on port
14.3 & 15.3 to two different adjacent routers see below the generic GE connection.

EMTS 3G UTRAN LLD

Page 74 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 43: IuR Control Plane GE connection

For outgoing IuR CP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 3 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 3 provides the standby path as higher metric (=10) defined.

Note1: lower metric identifies the preferred path.

For incoming IuR CP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuR Control plane GE configuration for Etisalat NIGERIA network.
These data are extracted from RNC CIQ files (IP IuR sheet)
RNC: Lagos LGRL203
RNC IuRCP-IP

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

4pGIGE1 IF @ (Card 14)

10.1.0.224/30
10.1.0.224
10.1.0.225-10.1.0.226
10.1.0.227
255.255.255.252/30
932

RNC IuRCP-IP
4pGIGE2 IF @ (Card
15)
10.1.0.228/30
10.1.0.228
10.1.0.229-10.1.0.230
10.1.0.231
255.255.255.252/30
936

10.1.0.225
10.1.0.226
5

10.1.0.229
10.1.0.230
10

Table 60: RNC IuR control plane GE configuration LGRL203

EMTS 3G UTRAN LLD

Page 75 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.5.4 IuR IP Addressing

Broadcast@:
10.1.0.219/30

LGRL203 RNC(10DCPS) IuR IP Addressing Plan

Itf / Traffic Type
iur / UPlane

10.1.0.161

10.1.0.217
PP/GIGE1

IuR UP VR

PMC-PC

10.1.0.174

10.1.0.162

If/x

PP/IuRUplane

PMC-PC
Broadcast@:
10.1.0.175 /28

10.1.0.163

10.1.0.170
PMC-PC

Local Media

PMC-PC

Vlan/922

10.1.0.221

LP/14
GE 0
GE 1
GE 2
La /143 GE 3

Vlan/932

Broadcast@:
10.1.0.227/30

10.1.0.226
Port

Vla n/926

VR/Iur UPlane

Broadcast@:
10.1.0.159/28

LP/15
GE 0

10.1.0.225

If/x

GE 1
GE 2
GE 3

Vlan/932

PP/IuRCplane

10.1.0.158

10.1.0.146

IuR CP VR

10.1.0.145

10.1.0.229

Vlan/926

La /153

Vlan/936
Itf / Traffic Type iur
/ SS7CPlane

Port
10.1.0.222

IP Router
Card 2

PP/GIGE2

PDC

RNC

Port
10.1.0.218

IP Router
Card 1

PP/GIGE2

PP/GIGE1

PDC

Vlan/922

Vlan/936

VR/Iur CPlane

10.1.0.230
Port

Broadcast@:
10.1.0.223 /30

Broadcast@:
10.1.0.231/30

Figure 44: IuR IP Addressing LGRL203

EMTS 3G UTRAN LLD

Page 76 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.6.

IuB

IuB interface provides a connection between RNC and Node B

In ALU UA07 release, UTRAN supports IuB with three UTRAN transport options:
-

Iub over ATM: both CP and UP use the services from ATM

Hybrid IuB: consisting in using the services from IP for HSPA I/B traffic whereas all other
UMTS UP and CP uses services from ATM

Native IP IuB: both CP and UP use the services from IP

For Etisalat NIGERIA Network, the chosen configuration is Hybrid IP IuB.

Figure 45: Hybrid IP architecture

In this Hybrid IP IuB solution, RNC must be connected to an IP backbone through a layer 3 access
router (two routers are needed in case of the IP redundancy) providing IP routing, DiffServ
forwarding and L3 Carrier Grade.
o

In Lagos: 1 RNCs has hybrid IuB over IP connection through a pair of 7750 SR-7

In Benin: 1 RNCs has hybrid IuB over IP connection through a pair of 7750 SR-7

And RNC must be also connected to an ATM Network (ATM backbone) to transfer the ATM traffic.

EMTS 3G UTRAN LLD

Page 77 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

4.6.1 Hybrid IP IuB protocol stack

Here is on overview of the protocol stack on the Hybrid IP IuB.

Figure 46: Hybrid IP IuB protocol stack

4.6.2 Hybrid IP IuB User Plane in the RNC

The IuB user plane connection terminates on the RNC within the PMC-PC.
The number of PMC-PC per RNC depends on the number of DCPS cards installed. One DCPS contains
one PMC-PC. Maximum 12 DCSP (i.e. also 12 PMC-PC) is possible in a RNC.
A /28 IP subnet (max 14 host id) is required for addressing all PMC-PC as for Hybrid IuB user plane
termination.
Following tables present the RNC IuB user plane IP subnet defined for Etisalat NIGERIA Network.
These data are extracted from RNC CIQ files (Hybrid IuB sheet)
RNC: Lagos LGRL203

Table 61: RNC IuB user plane IP subnet LGRL203

EMTS 3G UTRAN LLD

Page 78 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

RNC: BNRL204

Table 62: RNC IuB user plane IP subnet BNRL204

UDP Ports in the RNC:

One PMC-PC supports 16,000 UDP ports in the range [49152,.., 65535]
The number of PMC-PC depends on the number of DCPS board installed in the RNC i.e. 1 PMC-PC
per DCPS, so
LGRL203 (10 DCPS): total UDP ports = 16,000 port * 10 PMC-PC = 160,000 ports
BNRL204 (10 DCPS): total UDP ports = 16,000 port * 10 PMC-PC = 160,000 ports
On the IuB:
-

4.6.2.1

User Plane: one source and one destination UDP ports are assigned per UE
connection from the RNC UDP Port range.

IP Components for Hybrid IP IuB in RNC

Each Node B is identified on the RNC side by an IubIf instance.

Figure 47: RNC Hybrid IP IuB IP Components

EMTS 3G UTRAN LLD

Page 79 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Under the IubIf component, one single ipIf instance identified the Node B user plane over IP.

The Bandwidth Pool (BwPool) is always present under an Iub ipIf.

With hybrid Iub, there are two Bandwidth Pools:
1. One primary Bandwidth Pool, used for IP transport, handling Interactive/Background on
HSPA
2. One shared Bandwidth Pool, used for ATM transport, handling other traffic types
(Conversational, Streaming, Interactive/Background on R99), and also possibly handling
Interactive/Background on HSPA, when CAC refuses to establish them on the primary
Bandwidth Pool (e.g. in case of bandwidth shortage on the primary Bandwidth Pool or in
case of IP link failure).

Figure 48: RNC Hybrid IP IuB Bandwdith Pool

The IuB BwPool is linked to a transportMap instance and a congestionManagement instance for
regulating the downlink traffic.

TransportMap (Tm) Each bandwidth Pool will be linked to a Transport Map instance where a
set of transport input values will have to be defined correctly (tse = transportServiceEntry). At
this stage, the interface Type (iub), the name of the BP and the preference shall be set
Tm/2 is used for Hybrid IP IuB.
The IP Flow (corresponding to one stream) is a subcomponent of the BwPool. A BwPool can be
configured with up to 4 IpFlow called qos0, qos1, qos2 and qos3. In case of Hybrid Iub, its
configured with just 1 ipflow called qos3 for I/B, since the rest of the traffic and signaling is
carried on ATM.

EMTS 3G UTRAN LLD

Page 80 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Example:

Table 63: Transport Map Service Table

4.6.2.2

Bandwidth Pools CAC for Hybrid IuB in RNC

The CAC Method will apply per Bandwidth Pool where the bandwidth is equal to the SUM of all
paths inside the BP. The IP Bandwidth Pool initial bandwidth is equal to the sum of configured
tx/rx bandwidth set for IP BP => Equivalent Rate (UL/DL) = 2*CR*PR/(CR+PR); where CR =
committed Rate and PR = Peak Rate.

The new CAC Algorithm will retry Call Admission process in the shared BP in case of failure in
the Primary BP (resiliency).

4.6.3 BTS IP Flow Configuration

On each BTS, the following IP information must be defined:
-

A single BTS OAM IP @

A subnet mask for it /24
An aggregation point
a single IP RAN address (different from the OAM IP @),
a subnet mask /24 and
an IP Gateway address (IP @ of the 7750 facing the BTS)

Also an alcap A2EA address must be defined for ATM connectivity

Routing Table on NodeB
The routing Table of the BTS will be updated at the first hybrid call requested by the RNC by
using the following information:

EMTS 3G UTRAN LLD

Page 81 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

The RNC will pass on the IP@ of the PMC-PC (board situated in the RNC in the Iub PU
LocalMedia) to the BTS via the RadioLinkSetup/Addition/Reconf messages (transport
Layer Address field)
The IP Gateway address configured in the BTSEquipment object (OAM)

Following tables present the Hybrid Node B IP subnet defined for Etisalat NIGERIA network. These
data are extracted from RNC CIQ files (NodeB_Iub_Parenting_Hybrid sheet)
Note that for details of IP address assigned for each Node B, please refer to the Node B CIQ file
(NodeB_Iub_Parenting_Hybrid tab)

Table 64: Node B Hybrid Iub IP subnet - Example of NodeB adresses

4.6.4 Consolidated VR
Consolidated Virtual Router for IuB User Plane is chosen for Etisalat NIGERIA network.
VR/5 is assigned for User plane for IuB same for all RNCs:

Figure 49: IuB Consolidated VR (CP&UP)

4.6.4.1

GE Configuration

To transmit/receive IuB CP traffic to Node Bs, each RNC will have 2 GE connections on port 14.0 &
15.0 to two different adjacent routers see below the generic GE connection.

EMTS 3G UTRAN LLD

Page 82 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

Figure 50: IuB GE connection

For outgoing IuB CP&UP traffic, the 2 GE connections shall be working in active & standby mode,
thanks to PDR mechanism implemented in the RNC.
-

GE Card slot 14 port 0 provides the active path as lower metric (=5) defined.

GE Card slot 15 port 0 provides the standby path as higher metric (=10) defined.

Note: lower metric identifies the preferred path.

For incoming IuB UP traffic, RNC can receive the traffic from both GE links.
Each PP/GiGE requires:
-

One Subnet /30 for RNC point to point connection to adjacent routers

One VLAN ID to separate other traffic flows which share the same GE port.

Following tables present the RNC IuB GE configuration for Etisalat NIGERIA network. These data are
extracted from RNC CIQ files (Hybrid IuB sheet)
RNC: Lagos LGRL203

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC Iub-IP
4pGIGE1 IF @ (Card 14)
10.1.0.176/30
10.1.0.176
10.1.0.177- 10.1.0.178
10.1.0.179
255.255.255.252/30
903

RNC Iub-IP
4pGIGE2 IF @ (Card 15)
10.1.0.180/30
10.1.0.180
10.1.0.181-10.1.0.182
10.1.0.183
255.255.255.252/30
907

10.1.0.177
10.1.0.178
5

10.1.0.181
10.1.0.182
10

Table 65: RNC IuB GE configuration LGRL203

EMTS 3G UTRAN LLD

Page 83 of 113

Version draft 0.7

All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without
written authorization

RNC: Benin BNRL204

Subnet (4 IPs)
Network @
Range
Broadcast
Subnet Mask
VLAN Id
@ PP/GIGE
@ Adjacent Router
PDR / METRIC

RNC Iub-IP
4pGIGE1 IF @ (Card 14)
10.1.2.176/30
10.1.2.176
10.1.2.177- 10.1.2.178
10.1.2.179
255.255.255.252/30
953

RNC Iub-IP
4pGIGE2 IF @ (Card 15)
10.1.2.180/30
10.1.2.180
10.1.2.181-10.1.2.182
10.1.2.183
255.255.255.252/30
957

10.1.2.177
10.1.2.178
5

10.1.2.181
10.1.2.182
10

Table 66: RNC IuB GE configuration BNRL204

4.6.5 IuB IP Addressing

Figure 51: IuB IP Addressing LGRL203

EMTS 3G UTRAN LLD

Page 84 of 113

Version draft 0.7

ATM IuB

4.7.

4.7.1 The ATM IuB interface of Alcatel- Lucent

The 3GPP Iub stack Iub in UA7.1 is fully implemented
On the Iub physical interface, 2 parts have to be considered :

STM1-Vc4 on the RNC side

E1 or IMA on the NodeB side

The RNC and Node B are managing Vcc resources regarding the Iub point of view.

4.7.2 ATM UTRAN IuB interface Description

4.7.2.1

ATM IuB physical Interface Description

The IuB interface is split into 3 different equipments: RNC, SR 7750 and NodeB.

1. Node B side:

On the node B side, the physical layer is supported by E1s. The maximum number of E1 links per
NodeB equals 8 (product specification). In Etisalat Nigeria Network 2 E1s will be used per NodeB

8 ports E1
IMA mandatory from 2 E1

8
7
6
5

X
X
X
X

4
3
2
1

X
X
X
X

XCCM

Figure 52: E1 ports on XCCM

IMA Inverse Multiplexing ATM - is configured for all NodeBs. The purpose of this document isnt to
describe the IMA functionality but from a dimensioning aspect, the defence mechanism has to be
noticed:
When a link is lost within an IMA group, the defence mechanism triggered by the NodeB is to
shutdown one couple of [DS, NDS/HSDPA] VCCs. The number of VCC configured by NodeB is
described in the transport ATM section. The physical redundancy level on NodeB side is linked to the
number of E1, the loss of 1 link triggers a capacity reduction but has no functional impact on the site.
Note: IMA is always configured even if only one E1 is available; this strategy will guaranty easier
operation in case of extra connectivity addition
Any PCM within the IMA group could be used to synchronize the NodeB in order to guarantee that
the impact of a link failure is restricted to an Iub capacity reduction.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 85 of 113

Version draft 0.7

The ATM traffic is managed as followed in the BTS:

BTS
iCCM2
CCM
or iCCM-U

iCEM2
XCEM
or iCEM-U

1 to 16 AAL2
(User plane)
AAL5
(NBAP-c)
AAL5
(OAM)

AAL5
(NBAP-d)

AAL5
AAL5
(NBAP-d pour iCEM 1)
(NBAP-d for xCEM 1)

Internal Link
(HSSL)

iCEM2
XCEM
or iCEM-U

AAL5
(NBAP-d)

AAL5
AAL5
(NBAP-d pour iCEM n)
(NBAP-d for xCEM n)

AAL5
(OAM)
AAL5
(NBAP-c)
1 to 16 AAL2
(User plane)

AAL5 alcap
Figure 53: ATM Traffic management on BTS
Note: For the phase 1 deployment, each BTS has only one xCEM.(Extra XCEM card could be added
later on for more capacity).

Within the digital module, the master board: CCM manages the communication with external
interfaces (Iub) and other NodeB modules management/messages switching.
The xCEM is mainly involved in radio interface layer 1 and 2 functions and supports a part of call
processing.
2. RNC side (between the RNC and the SR7750):
The interface card on the RNC is the 16port STM1 card

EMTS 3G UTRAN LLD

Page 86 of 113

Version draft 0.7

Figure 54: 16pSTM-1 ports

We usually have STM-1 ports reserved for IuCS, IuPS and IuR but since in Etisalat Nigeria, IuCS, IuPS
and IuR are all over IP, so we have available up to 16 ports STM-1 for IuB. We will be deploying 5
STM-1 for RNC Lagos and 1 STM-1 for RNC Benin.

Two pair (active + redundant) of optical links are available between the RNC and the SR 7750. APS
functionalities ensure a full protection against link or board failure. The optical connexion is done with
single mode fiber with MT-RJ connectors.

Figure 55: APS mechanism

EMTS 3G UTRAN LLD

Page 87 of 113

Version draft 0.7

The RNC ports used for SR7750 connections are:

RNC1500
16pOC3

16pOC3

Slot 8 SDH/0-7

Slot 9 SDH/0-7

Table 67: RNC Ports used for SR7750 connections

For RNC Lagos LGRL203: 5 STM-1 VC-4 will be deployed

Figure 56: RNC STM-1 Connection with SR7750- LGRL203

For RNC Benin BNRL204: 1 STM-1 VC-4 will be deployed

Figure 57: RNC STM-1 Connection with SR7750- BNRL204

The ATM traffic is managed as followed in the RNC via 16p STM 1 card:

EMTS 3G UTRAN LLD

Page 88 of 113

Version draft 0.7

(*)

Figure 58: ATM Traffic Management on RNC

On each PSFP/DCPS there is a set of daughter card. Each daughter card (PMC card) has a
dedicated role (PC, RAB, NI, TMU, OMU). The control plane and the user plane are managed by
these PMCs has shown the picture. The ATM/IP interface is managed by the 16p STM 1 card.

EMTS 3G UTRAN LLD

Page 89 of 113

Version draft 0.7

4.7.3 ATM UTRAN IuB Interfaces Configuration

4.7.3.1

ATM UTRAN IuB Transport Configuration

The different protocol stacks involved on the Iub are described in following picture. The protocol
termination and the equipment involved in their management are also identified by this
representation.

ALCAP

Figure 59: ATM UTRAN IuB protocol stack

For RNC Lagos LGRL203: 71 NodesB will be configured per STM-1 on the RNC IuB ports (we will
deploy 2 STM-1s)

For RNC Benin BNRL204: 20 NodesB will be configured on the single STM-1 available

4.7.3.2

ATM Configuration

In the RNC and at the NodeB level, the ATM connections are configured and managed at VC level.

In the NodeB, for all ATM VCCs QOS and Emission Priority level has to be defined.

Common Control Port AAL5 VCCs:

As many VCCs as amount of xCEM (Nbap-dedicated), up to 2 xCEMs,

In case of Etisalat Nigeria only 1 xCEM and therefore 1 CCP VCC.

Up to 2 CCP VCC

Control Port AAL5 VCC:

1 VCC carrying Nbap-common signalling,

UserPlane AAL2 VCC:

1 Vcc DS per E1 within the IMA Link Group. (Delay Sensitive Trafic & Signaling, hence CS
trafic)

EMTS 3G UTRAN LLD

Page 90 of 113

Version draft 0.7

1 Vcc NDS per E1 within the IMA Link Group. (Non Delay Sensitive Trafic hence PS R99)

1 Vcc Hspa

UMTS OAM AAL5 VCC: (IPoverATM),

1 Vcc OAM

ALCAP VCC:

1 Vcc ALCAP

The IMA link Group is shared by the R99 and HSPA traffic. So, the rules for the Vccs grouped under
one IMA are the following :

Node B holding priority rules:

The lower holding priority level (0) is the highest priority. It is the last Vcc disabled in case of E1
failure.

Vpi,Vci

Node B priority
level

serviceCategory
(ATMProfile/x)
in node B

OAM

1.32

UBRPlus3

ALCAP

1.33

UBR1

1.34

UBR1

CCP

1.35-1.36

UBR1

UP DS

1.41-1.47

1-7

UBR1

UP NDS

1.49-1.55

1-7

UBR

HSDPA

1.56

UBRPlus3

Table 68: NodeB holding priority rules

The SR7750 equipment is configured to perform VC switching. This backbone architecture has been
decided to provide granularity on VCC level for QOS management.
The following table details the range of VCi reserved for the max configuration of NodeB with 7 E1

Each E1 will be carried on a dedicated VCC for AAL2 User Plane DS, and NDS hence a
range of 7 consecutive VCi are reserved for those 2 flows (for a maximum of 7 E1)

A single VC will carry HSDPA traffic with Vpi 56

RNC

IMA

connection

Vpi.Vci

Vci

PVP

x.32- x.36

UBR+

AAL5 OAM, CP + CCP

NBAP C and D data

PVP

x.41-x.47

CBR

AAL2 User Plane DS data

PVP

x.49-x.55

UBR+

AAL2 User plane NDS data

PVP

x.56

UBR

AAL2 HSDPA

IMA
(Node
B id)

Cos

Usage

Table 69: VCC numbering - 8 E1

EMTS 3G UTRAN LLD

Page 91 of 113

Version draft 0.7

Where x is the number of each nodeB = 1 for first nodeB , =2 for second nodeB and so on.

In case of Etisalat Nigeria configuration with 2 E1s the below tables will be deployed
2 VC are used respectively for DS traffic (VCi 41 and 42) and NDS traffic with VCi (Vci 49 and 50)

RNC

IMA

connection

Vpi.Vci

Vci

PVP

x.32- x.36

UBR+

AAL5 OAM, CP + CCP

NBAP C and D data

PVP

x.41-x.42

CBR

AAL2 User Plane DS data

PVP

x.49-x.50

UBR+

AAL2 User plane NDS data

PVP

x.56

UBR

AAL2 HSDPA

IMA
(Node
B id)

idxx

Cos

Usage

Table 70: VCC numbering - 2 E1

4.7.3.3

ALCAP

Hybrid Iub requires ALCAP VCC for the allocation of transport network layer (TNL) resources over
ATM.
Each BTS is identified by an A2EA (AAL2 End point Adress)
The format of the address is the following 4500000000+rss+xxxx+F0000000000000000000000
where rss= rnc id, xxxx= nodeb id
as shown in the table below
RNC

NodeB

A2EA Address

LGRL203

U3000_GOVONOR'S OFFICE_OD

45000000002003361F0000000000000000000000

Table 71: A2EA adress format

4.7.3.4

ATM Traffic Description

NodeB traffic descriptor:

On node B side, as no shaping is activated, the PCR could be set by default to the available IuB
bandwidth (PCR = n x4490 cell/s for nE1)
This VCC TD strategy, without shaping allows high flexibility and maximum of potential multiplexing
gain.

Configuration 2 E1s from RNC CIQ ( IuB_NodeB_Vcc sheet):

Name

VPI.VCI

serv.category

PCR (c/s)

SCR (c/s)

OAM

1.32

UBR+

8980

Alcap

1.33

UBR1

8980

1.34

UBR1

8980

CCP

1.35

UBR1

8980

1.41

UBR1

8980

1.42

UBR1

8980

EMTS 3G UTRAN LLD

Page 92 of 113

Version draft 0.7

NDS

1.49

NDS
HSxPA

UBR

8980

1.50

UBR

8980

1.56

UBRplus3

8980

227

Table 72: IuB Vcc Traffic descriptors from NodeB side

Backbone traffic descriptor:

for BTS 2 E1s: the following table provide the ATM traffic descriptor used on RNC (Peak Cell
Rate ,Sustained Cell Rate in cells/sec, Max Burst Size in cells) and the corresponding ATM traffic
descriptor on SR7750 router (PIR,SIR in Kbit/sec, and MBS in kbits). They are converted from ATM
cells to Kbits with 53bytes per ATM cell.
Equivalent Cell rate (ECR)
ECR=2*PCR*SCR/(PCR+SCR)

computed

per

VCC

according

GCAC

formula

The sum of ECR VCC is equal to 95% of the IMA link group bandwidth (2*4940cells), the 5%
remaining are for AAL5 VCCs to ensure minimum bandwidth for signalling.

RNC ATM traffic descriptor

SR7750 ATM traffic descriptor

Node B
VPI/VCI Flow

Service
category PCR
SCR
MBS
RNC
(cells/s) (cells/s) (cells)

1/32

OAM

UBR

4490

1904

1/33

ALCAP

rtVbr

4490

1904

1/34

rtVbr

4490

1904

1/35

CCP

rtVbr

4490

1904

1/41

rtVBR

4490

2417

3142

1904

1025

1332

1/42

rtVBR

4490

2417

3142

1904

1025

1332

1/49

NDS

nrtVBR

4490

642

1123

1904

272

476

1/50

NDS

nrtVBR

4490

642

1123

1904

272

476

1/56

HSDPA UBR

1904

ECR
PIR
SIR
MBS
ECR
(cells/sec) (Kbits/s) (kbits/s) (Kbits) (Kbits/sec)

Table 73: IuB Vcc Traffic descriptors from RNC side

4.7.3.5

ATM Backbone switching

The selected option for ATM backbone is VC switching.

For a VPm.VCa in the node B IMA group, there is a corresponding VPn.VCa on the RNC side.

EMTS 3G UTRAN LLD

Page 93 of 113

Version draft 0.7

Figure 60: ATM Vc Switching

The correspondence between the VP number on NodeB side (m always=1) and the VP at RNC side
(n=NodeB.IubIf=INVccGroup) is given by the sheet NodeB_Iub_Parenting_ATM in the CIQ.
Here is an example for 2 different NodeB

RNC

NodeB

LGRL203
LGRL203

U3000_GOVONOR'S
OFFICE_OD
U3130_IKOSI_KETU_OD

NbPCM

INVccGroup
(NodeB.IubIf)

VCC on
NodeB side

VCC On RNC
side

ATM Interface
(RNC)

1.33- 1.56

35.32-35.56

800

1.33- 1.56

1.32-1.56

800

Table 74: Iub VP number on RNC versus VP NodeB number

QoS Management

4.8.

4.8.1 IP Backbone QoS requirement

4.8.1.1

IuB & IuR QoS requirement

QoS handling in the backbone follows an SLA between UTRAN operator and backbone provider. The
SLA specifies:

Delay, jitter, packet loss level for a given CIR/PIR for a given QoS class

Service availability (e.g maximum outage time)

The QOS requirement on the IuB interface, or SLA (Service Level Agreement) that need to be
provided by the IP backbone is the following:

EMTS 3G UTRAN LLD

Page 94 of 113

Version draft 0.7

QoS requirements
-

The target end-to-end Iub QoS requirements are detailed in table below.

UTRAN ALU Iub QoS requirements per Traffic Class

Conversational
R99 I/B
Iub
delay + jitter
Impact on MOS
Iub
rate of packet loss

0 to 50 ms

HSDPA I/B

HSUPA I/B

< 50 ms

1 E-03

1 E-04

- 0 to - 0.3
1 E-03

Note: Packet loss requirement refers to Frame Protocol packets, in order to remain independent of the
underlying transport (ATM or IP).
Note: optimal throughput performance when increasing delay on IuB requires TCP tuning.

Table 75: IP Backbone QoS requirement for IuB

IuR should require the same QoS level as for IuB.

4.8.1.2

IuCS QoS requirement

The general guidelines for IuCS over IP SLA:

Backbone provider may not provide as many QoS level as the number of differentiated
flows in RNC.

IuCS Uplane (RNC QoS 0) should be mapped on the backbone QoS level with highest
priority and throughput guarantees (CIR/PIR).

IuCS Cplane SCTP (RNC QoS 3) should be mapped on lower backbone QoS, but should
not be mapped on lowest. A minimum throughput guarantee should also be available
for signaling.

Recommended SLA in the transmission backbone for IuCS over IP :

CIR/PIR for IuCS UP should be dimensioned with CIR=PIR=RNC value and according to
target call blocking.

Additional SLA parameters can be provided such as re-convergence time in case of

backbone node failure.

Table 76: IP Backbone QoS requirement for IuCS

4.8.2 Priority handling in IP backbone

4.8.2.1

Diffserv

IP Differentiated Services (DiffServ) shall be supported by the IP network.

EMTS 3G UTRAN LLD

Page 95 of 113

Version draft 0.7

In the IP header, the Type of Service (ToS) field is superseded by the Differentiated Services (DS)
field as defined in IETF RFC 2474.
DiffServ provides 8 QoS Classes:

CS7 & CS6 (IP Network Control )

EF (Expedited Forwarding)

AF4 & AF3 & AF2 & AF1 (Assured Forwarding)

Each AF Class has 3 levels of drop precedence: AF11, AF12, AF13

DF (Default Forwarding) same as BE (Best Effort)

Figure 61: Diffserv

The Diffserv mechanism allows the router to classify the IP packets depending on their priority and
to apply a required treatment.
A value, the DSCP, in the IP header indicates the priority level
There are 2 types of routers:

The Edge Router at the border of the IP transport network.

It has to classify and mark the IP packets with the DSCP value

The Router inside the IP transport network

It has to queue and schedule packets depending on the DSCP value

Figure 62: Router Types

4.8.2.2

DSCP Marking

DSCP marking is ensured by RNC and Node B

On Iub (downlink), Iur and Iu-CS the DSCP value is set by the RNC according to the service.
For a given service, the DSCP value can be different for each interface.

EMTS 3G UTRAN LLD

Page 96 of 113

Version draft 0.7

On Iub (uplink) the DSCP value is set by the Node B IP Differentiated Services (DiffServ)
shall be supported by the IP network.

DSCP values are configurable by O&M

In User plane:
Traffic categories are defined in the RNC by the 3-tuple (Traffic Class, ARP, THP).
Each DL IP packet will be marked by a DSCP value depending of the instance of this 3-tuple.
For UL IP packet, the Node B will use the DSCP value indicated by the RNC in NBAP
messages
For other flows (Control Plane, O&M, PTP):
The DSCP values are configurable in RNC and/or in Node B.

DSCP Marking on IuCS

Traffic Class
ARP THP DSCP
1,2,3 NA
EF
Conversational
AF41
RANAP Signaling NA
1
EF
CS Streaming
2
EF
3
EF
Table 77: DSCP Marking on IuCS
Traffic Class
ARP THP
RANAP Signaling NA NA
1,2,3 NA
Conversational
1
NA
PS Streaming
2
3
1
1
Interactive
2
3
1
2
2
3
1
3
2
3
1,2,3 NA
Background

DSCP
AF41
EF
AF41
AF42
AF43
AF31
AF21
AF11
AF32
AF22
AF12
AF33
AF23
AF13
DE

Table 78: DSCP Marking on IuPS

4.8.3 RNC QoS Management

4.8.3.1

Scheduler

Priority handling in RNC 4pGE is really needed when a given GE port may be overloaded

Scheduling
o

one scheduler on each of the 4 ethernet links

EMTS 3G UTRAN LLD

Page 97 of 113

Version draft 0.7

Each link class scheduler has 8 Emission Priorities (EPs) : 2 absolute priorities (EP0
and EP1) and 6 lower EPs (EP 2 to EP7) sharing the residual bandwidth left over
by EP0 and EP1 using a Weighted Fair Queuing according to Minimum Bandwidth
Guarantee (MBG) configured to each EP

o
Figure 63: Schedulers on 4ptGE

Buffering: Each EP has a configurable Queue Size

Congestion control: 3 Discard Priorities (DPs) : High, Medium, Low

Traffic classification: Mapping of traffic types on EPs and DPs is configurable per DSCP QoS
Class

4.8.3.2

Emission Priority (EP) Mapping

Table 79: EP Mapping on RNC Ethernet link

4.8.4 Call Admission Control

The bandwidth efficiency depends on the way the available bandwidth on a given Iub is shared
among the different QoS
If no checking is made about the available transport resources during the service establishment,
the IP transport network will be congested.
Congestion does not allow providing the required QoS to the end user.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 98 of 113

Version draft 0.7

So a Call Admission Control (CAC) is used for IP

Bandwidth Pool (BP)

If the sum of established bearer is above the BP, the bearer establishment is rejected

Bandwidth Pool (BP) definition:

BPs partition the Iub Interface into groups (or pools) of bandwidth resources

BP resources/bandwidth are not shared with other BPs

BPs can be Dedicated BPs (HSPA BPs, R99 BPs) or Shared BPs (HSPA + R99)

In Etisalat NIGERIA network, Shared BP configuration is chosen to ensure efficient usage of

resources

Figure 64: CAC Algorithm

1. QoS, TC, THP, ARP is used to select DSCP in dedicated BP (if applicable), otherwise in shared BP
2. This DSCP corresponds to an IP path which is in a QoS.
3. CAC checks if there is sufficient bandwidth in the BP (excluding any BW reserved for a specific
QoS)
if EBR < Available Rate (AR), the call is accepted and AR = AR EBR,
if EBR > Available Rate, the call admission may check shared BP (if applicable), otherwise
call is rejected.
4. If CAC failed in the dedicated BP, the DSCP selection is played in the shared BP.

4.9.

UTRAN OAM Architecture

The figure below shows the OAM architecture for the various parts of the UTRAN network, which
includes

WMS 9353 Wireless Management System servers

NPO 9359 Network Performance Optimizer servers

EMTS 3G UTRAN LLD

Page 99 of 113

Version draft 0.7

WQA 9351 Wireless Quality Analyzer servers

It also presents local and remote ROC (Regional Operation Centre) client stations

Remote access supported with a Brick for the Internet.

The OAM network can be divided into IP sub networks to separate different types of traffic.
Different parts of the network can be isolated as much as possible, to prevent them from talking to
each other. The interconnection between the sub networks is done at the router level
(OmniSwitch)

Figure 65: OAM Architecture for UTRAN

4.9.1 9353 WMS

The 9353 WMS (Wireless Management System server) is delivered on a simple, scalable hardware
platform strategy designed to grow effectively with the rollout of Wireless services. The primary
Network Management functions are hosted by a pair of Sun Servers:
The WMS Main Server for the Network Management platform, Fault Management and
Configuration Management functions
The WMS Performance Server for the Performance Management functions.
The client workstations supported for management of the Wireless network include Sun
Workstations and PCs.
The 9353 WMS is based on Sun platforms: three types of Sun servers are available to manage small,
medium and large 3G/HSPA access networks. The system has been designed to minimize downtime
during upgrade, data back-up, data restore or when unexpected outages occur.
The Equipments in the Etisalat Nigeria network are:

EMTS 3G UTRAN LLD

Page 100 of 113

Version draft 0.7

The Alcatel-Lucent Wireless Network Management System (WMS) will use the MED configuration
based on Sun SPARC Enterprise T5440. This will be single server architecture with 1 Primary Combo
Server (PCS).

The hardware configuration for the T5440 is as follows. It allows to support up to 7 RNC, 700 NodeB
or 4200 cells
SUN server

T5440

nb of CPU

CPU type

US T2 plus 8 core processors 1.4 Ghz

RAM (GB)

internal disk (GB)

12*300 SAS

external tape drive

DAT 72
Table 80: WMS Primary Combo Server

Below table shows a part of WMS configuration for Etisalat NIGERIA network. For complete
information, please refer to WNMS CIQ file (Main Server tab)
Description

Parameter

Number of servers in the architecture

Comment

One ROC allows up to 2 Main Servers

Number of Main Servers

Hostname of the machine (also Hostname 0

below)
IP address of the machine (also IPAddress0
below)
Netmask of the machine (also Netmask 0
below)
time_zone

eg. Hardy0

Value

Solaris Installation
Hostname of the server
IP Address of the server
Netmask of the server
Timezone where the machine is located

omc3glagos

eg. 172.72.34.2

10.7.1.1

eg. 255.255.255.162
Attention: Please read important note in
engineering guide (Time Synchronisation
section) on the restriction on Time Zones and
the fact that the clients and servers need to
be in the same zone.
NOTE: The definition of the time zones for
the Solaris servers needs to be done
according to the definitions in
/usr/share/lib/zoneinfo

255.255.255.0

Africa/Freetown

Alcatel-Lucent Equipment Installation

Default Router IP Address
Model of server

router_address (DefaultRouterAdd)
Platform

eg. 172.72.34.1
SFV8x0/SF4x00/SFV250/Netra 240

10.7.1.254
Netra T5440

Table 81: a part of WMS configuration extracted from WNMS CIQ

4.9.1.1

WMS Clients

The PC workstation has a minimum recommended specification as detailed

Attribute

Value

CPU Processor

1 CPU Intel Core 2 Duo or Core 2 Quad or higher

RAM Memory

2GB RAM or higher

Hard Disk Memory

80 GB disk or higher

Media drives

Internal DVD drive

Ethernet board

100/1000 Mb/sec Ethernet boards

Operating System

Windows XP professional service pack 2 or 3 ,

Windows 2000 Professional sp4
Windows Vista Business/Enterprise Service Pack 1

EMTS 3G UTRAN LLD

Page 101 of 113

Version draft 0.7

(With Windows Vista it is highly recommended to add

1 GB of RAM to the above requirements)
Table 82: PC Workstation specification
5x Clients are provided to granted access with certain level of management capabilities.

4.9.1.2

WMS Software

The following licensed software will be the initial load operating on the WMS.
Software Item
WMS Load

Qty
N/a

Type
OAM 7.1.1.3

Table 83: WMS Software load

4.9.2 OAM-NE NETWORK CONFIGURATION

The OAM-NE (Network Element) interconnections overview is as follow:

Figure 66: OAM-NE network configuration

NODEB OAM flows are aggregated by the RNC through an Aggregation Point. A range of IP
address (subnet /24) is dedicated to establish connection between RNC and NODEB.
At RNC level a Virtual Router (Management VR) enable connections from the W-NMS servers
towards NODEB. RNC CP4 port connection belonging to the OAM-NE subnet carries W-NMS
servers flows
An example of the IP configuration for OAM is given in the CIQ NodeB_Iub_Parenting_ATM

EMTS 3G UTRAN LLD

Page 102 of 113

Version draft 0.7

RNC

NodeB

NodeB IP @

nodeB IP mask

NodeB aggregation
point IP@

LGRL203

U3000_GOVONOR'S_OFFICE_OD

10.1.1.1

255.255.255.0

10.1.1.254

Table 84: NodeB OAM IP adressing

4.9.3 Wireless Quality Analyzer

The Alcatel Lucent 9351 Wireless Quality Analyzer (based on dedicated PC server and PC clients)
provides capability to allow UTRAN network optimization based on the UTRAN traces generated by
the RNC.
It analyses the performance of the mobility within 3G network and allows to have updated
neighbouring lists (intra/inter Frequency and Inter System) that are crucial for good end user QoS.

W-NMS

measurement
gathering

Activation

Data mediation

Analysis presentation
3 ,00%
2 ,50%
2 ,00%

Data collection,

1 ,50%
1 ,00%
0 ,50%
0 ,00%
-11

storage

C e ll 1

C e ll 2

C e ll 3

M (1 ,2 )

M (1 ,3 )

...

M (1 ,N )

M (2 ,3 )

...

M (2 ,N )

...

M (3 ,N )

C e ll 2

M (2 ,1 )

C e ll 3

M (3 ,1 )

M (3 ,2 )

...

(Cell 1 - Cell 2)

...

percentage total
interference

-5

-3

-1

100,00%

M ( P3,00%
,1 )

M (P ,2 )

M ( P ,3 )

...

90,00%
80,00%

2,50%

70,00%
60,00%

2,00%

50,00%
1,50%

40,00%
30,00%

1,00%

20,00%
0,50%

10,00%

0,00%
-35

-7

...

3,50%

C e ll P

and analysis

-9

C e ll N

cumu lative distributio n

I n t e rf e re r
S e r vi n g

0,00%
-25

-15

-5

C/I (dB)

WQA Server

WQA Client

Figure 67: WQA architecture

WQA follows a J2EE based architecture, working on a Microsoft Windows server with the following
specifications
Attribute

Value

CPU Processor

2xPentium IV 2.8GHz or higher

RAM Memory

8 GB RAM or higher

Hard Disk Memory

600GB disk or higher*

Media drives

Internal DVD drive

Ethernet board

100/1000 Mb/sec Ethernet boards

Operating System

Microsoft Windows Server 2003 Enterprise Edition 32 bits

Service Pack 2
Table 85: WQA Hardware Specifications

EMTS 3G UTRAN LLD

Page 103 of 113

Version draft 0.7

4.9.4 Network Performance Optimizer

The Alcatel-Lucent 9359 Network Performance Optimizer for W-CDMA later referred as NPO
allows to produce performance reports based on counters produced by the UMTS NE (BTS, RNC)
The NPO server retrieves the counters files available in the W-NMS Performance server (which is
coresident with the main server since UA6.0) and produces Key Performances Indicator accordingly.
The network configuration is uploaded from the W-NMS main server.
The NPO architecture is described in the following figure:

Figure 68: NPO Architecture

The NPO deployed has the below specifications. It allows to support up to 3000 NodeB or 9000 cells.

Sun Sparc M4000-2 CPU MED, 2 * 2.5GHz quad core

SPARC 64 VII
Processors, 32GB RAM, disk 2x300 GB
WMS External Tape Drive LTO4
Table 86: NPO server specification

4.9.5 DCN And Peripherals

The Severs and Ethernet switches are to be mounted in a single rack mounting. It comes with
peripherals for DCN network connectivity and RAMSES access.
Copyright Alcatel-Lucent

EMTS 3G UTRAN LLD

Page 104 of 113

Version draft 0.7

The following items are included:

Items

Qty

WMS rack 1242 EAC w PDS

WMS VPN Brick

WMS RAMSES PC

WMS Eth Routing Switch AC 24p

WMS Eth Routing Switch AC 48p

Table 87: DCN And Peripherals

EMTS 3G UTRAN LLD

Page 105 of 113

Version draft 0.7

5. APPENDIX
5.1.

UTRAN IP Planning for Etisalat Nigeria Network

Following tables are the summary of UTRAN IP Planning for Etisalat Nigeria Network. For more details, please refer to UTRAN IP planning file.

Table 88: UTRAN IP Planning for Etisalat Nigeria Network

EMTS 3G UTRAN LLD

Page 106 of 113

Version draft 0.7

5.2.

TransportMap Table

Tm/5:
Application Context:
-

Interface Types: IuR, IuCS

Preference: SharedForAllTrafficTypes

Transport: IP

Table 89: Transportmap/5 Table

EMTS 3G UTRAN LLD

Page 107 of 113

Version draft 0.7

Tm/2:
Application Context:
-

Interface Types: IuB (Hybrid)

Preference: PrimaryForTrafficTypes

Transport: IP

Table 90: Transportmap/2 Table

EMTS 3G UTRAN LLD

Page 108 of 113

Version draft 0.7

5.3.

Call Profile Assumptions

Alcatel-Lucent RNC capacity commitments are based on a set of call profile assumptions per
service
3 types of Call profiles depending on services

Uni-service Call Profile

R99 service-mix Call Profile

HSPA service-mix Call Profile

Each call profiles are described by 2 sets of parameters

Traffic parameters

Signaling parameters

5.3.1 Traffic parameter Uni service Call Profile

In Uni-service profile, each service assumes that 100% of the traffic is generated using only this
service. Note that in reality, there will be a mixture of services.

BHCA per attached Subscriber is 1 for speech. In the Uni-service profiles, data services are run in
isolation. Therefore, BHCA for each data service has been set to 0.3 in order to make each all
data scenario significant and comparable

EMTS 3G UTRAN LLD

Page 109 of 113

Version draft 0.7

5.3.2 Traffic parameter R99 service mix Call Profile

This table refers to R99 service-mix profile which contains only R99 RABs without HSPA

In Uni-service

Session Duration is the time from the first to last user packet transmission
Iu connection duration time is the time from first user packet transmission until the application is
closed. PS I/B calls are assumed to end due to user-initiated action

Compressed mode represents the % of 3G calls per busy hour that terminate with a Hard Handover
to 2G.
Number of pauses per session and the average pause duration simulates long intra session
periods of inactivity in data applications. These pauses may result in a change to/from the
downsized/nominal state

EMTS 3G UTRAN LLD

Page 110 of 113

Version draft 0.7

5.3.3 Traffic parameter HSPA service mix Call Profile

HSPA service-mix profile: R99 & HSDPA & EDCH RABs

EMTS 3G UTRAN LLD

Page 111 of 113

Version draft 0.7

5.3.4 Signaling parameters

Call Profile assumptions Signalling parameters
Values for
Uni-Service
Profiles

Values for
R99 SMP
Profile

Values for
HSPA SMP
Profile

0.17 (CS)

0.14 (CS)

0.12 (CS)

0.27 (PS)

0.17 (PS

0.27 (PS

0.14 (CS)

0.12 (CS)

0.08 (PS)

0.17 (PS

0.27 (PS

Per attached subscriber during busy hour

This includes UE and network initiated

Location Area Update

1.25 (CS)

1.28 (CS)

Per attached subscriber during busy hour

Routing Area Update

0.65 (PS)

Per attached subscriber during busy hour

70% (CS)

80% (CS)

80% (PS)

Percentage of
reference
attached to the network

1.3

1.5

Average Sector per User in Cell DCH state

0.1

0.12

Active Set Update rate in Hertz. E.g. 0.1

means 1 radio link addition OR deletion
every 10 seconds.

40%

34%

Percentage of handovers that are softer

handovers

15%

Percentage of handovers that are between

2 RNCs.

0.1

0.12

MR/sec per subscriber in cell-DCH state

using full event triggered measurement
reports.

1.5

1.1

CN paging request repetition factor

1.3

UTRAN Paging repetition factor

10%

Due to Block Error Rate

Cell Update Rate

0.03

0.036

NBAP MR rate

Compressed Mode Cells

per RRC MR

6+6

N/A

UMTS+GSM

Cells per URA

N/A

600

# of cells per UTRAN Registration Area

Cells per LA

1200

# Cells per Location Area

Cells per RNC

1200

# Cells per RNC

Parameter
IMSI attach

IMSI detach

% attached subscribers

Macro
only)

Diversity

Softer Handover
(R99 only)

Comments
Per attached subscriber during busy hour

subscribers

(R99

ratio

Inter RNC SHO Ratio (R99

only)

RRC Measurements

UMTS Cells per RRC Measurement Report

Paging Repetition

RLC Retransmission

Per second in CellFACH, CellPCH states

Dedicated MR per iRM upgrade

The assumptions proposed in these tables are realistic assumptions based on Alcatel-Lucents
extensive field experience in live GSM, CDMA and IP networks. All traffic and signaling values are
for attached subscribers

EMTS 3G UTRAN LLD

Page 112 of 113

Version draft 0.7

END OF DOCUMENT

EMTS 3G UTRAN LLD

Page 113 of 113

Version draft 0.7

Tawuniya Insurance Hospitals
41% (17)
Tawuniya Insurance Hospitals
64 pages
Uma Coisa Nova-Partitura e Partes
No ratings yet
Uma Coisa Nova-Partitura e Partes
65 pages
Radio Access Network and Operations 1 Technology PDF
No ratings yet
Radio Access Network and Operations 1 Technology PDF
128 pages
Core Network
100% (1)
Core Network
16 pages
LTE Basics
No ratings yet
LTE Basics
10 pages
UTRAN Interfaces and Protocol Structure
No ratings yet
UTRAN Interfaces and Protocol Structure
10 pages
RAN Engineer PDF
No ratings yet
RAN Engineer PDF
4 pages
Radio Quality Measurements in LTE
No ratings yet
Radio Quality Measurements in LTE
3 pages
Unit-Iii Umts:: Universal Universal Mobile Telecommunication System
No ratings yet
Unit-Iii Umts:: Universal Universal Mobile Telecommunication System
22 pages
694 Cellular Network
No ratings yet
694 Cellular Network
64 pages
LTE Fundamentals
No ratings yet
LTE Fundamentals
16 pages
3GPP - ETSI - Study On New Radio Access Technologeis 5G Rel 14 2017 - pp78
No ratings yet
3GPP - ETSI - Study On New Radio Access Technologeis 5G Rel 14 2017 - pp78
78 pages
Trend Victoria SDH Sonet PDH
100% (1)
Trend Victoria SDH Sonet PDH
7 pages
Huawei RAN TX Counters
No ratings yet
Huawei RAN TX Counters
8 pages
WCDMA Radio Network Mobility Counters and KPIs
No ratings yet
WCDMA Radio Network Mobility Counters and KPIs
68 pages
3g To 4g Migration - Article
No ratings yet
3g To 4g Migration - Article
3 pages
Chapter 11 Development of Network Planning Technology .................................................... 11-1
0% (1)
Chapter 11 Development of Network Planning Technology .................................................... 11-1
47 pages
EE5406 Network Architectures
100% (1)
EE5406 Network Architectures
50 pages
GRP F
No ratings yet
GRP F
9 pages
SDH Vs PDH
100% (1)
SDH Vs PDH
5 pages
Solution Architect - RAN
No ratings yet
Solution Architect - RAN
2 pages
UMTS Networks Standardization
No ratings yet
UMTS Networks Standardization
10 pages
Tn9400 p25 Trunking Core Network
100% (1)
Tn9400 p25 Trunking Core Network
4 pages
Register 5 - Radio Resource Control Protocol RRC
No ratings yet
Register 5 - Radio Resource Control Protocol RRC
72 pages
WCDMA RAN Synchronization
No ratings yet
WCDMA RAN Synchronization
71 pages
SIGTRAN (SS7 Over IP) : Notes: There Are Two Other IETF Standards Which Define Transport of PSTN Signaling (Non
No ratings yet
SIGTRAN (SS7 Over IP) : Notes: There Are Two Other IETF Standards Which Define Transport of PSTN Signaling (Non
9 pages
Study Case CoreNetworkPlanning
100% (1)
Study Case CoreNetworkPlanning
34 pages
HARPY Core Network India PVT
No ratings yet
HARPY Core Network India PVT
3 pages
Flyer Mobile Core Network
0% (1)
Flyer Mobile Core Network
2 pages
Sralxd: Installation & Commissioning Basic MW System Overview
100% (1)
Sralxd: Installation & Commissioning Basic MW System Overview
33 pages
3g Networks Technologies.
No ratings yet
3g Networks Technologies.
153 pages
Multiple Operator Core Network
100% (1)
Multiple Operator Core Network
6 pages
Evolution From Fixed-Line Technology To GSM, Umts, Lte and Beyond
No ratings yet
Evolution From Fixed-Line Technology To GSM, Umts, Lte and Beyond
27 pages
Anritsu MP1552B SDH PDH ATM Analyzer Data Sheet
100% (1)
Anritsu MP1552B SDH PDH ATM Analyzer Data Sheet
11 pages
SDH Basics
100% (1)
SDH Basics
72 pages
LTT Core
100% (1)
LTT Core
16 pages
En DC Secondary Node Addition Core Network Details
100% (1)
En DC Secondary Node Addition Core Network Details
6 pages
TCP/IP Protocol and IP Addressing
No ratings yet
TCP/IP Protocol and IP Addressing
30 pages
Latency in HSPA Network
No ratings yet
Latency in HSPA Network
18 pages
Bss Function
No ratings yet
Bss Function
12 pages
SDH
100% (1)
SDH
76 pages
GSM Network Architecture
No ratings yet
GSM Network Architecture
5 pages
OSS-RC 11.2 Description
100% (4)
OSS-RC 11.2 Description
46 pages
Network Registration: Chin Gang Wu, Application Engineer October 26, 2016 Confidential
No ratings yet
Network Registration: Chin Gang Wu, Application Engineer October 26, 2016 Confidential
12 pages
17.mobile Intelligent Network
No ratings yet
17.mobile Intelligent Network
14 pages
Reinventing Ericsson
No ratings yet
Reinventing Ericsson
17 pages
CCDP Question 1
0% (1)
CCDP Question 1
30 pages
1.1 5 - Zero Touch Provisioning
No ratings yet
1.1 5 - Zero Touch Provisioning
10 pages
IP Core Planning
100% (1)
IP Core Planning
1 page
Belair Networks
No ratings yet
Belair Networks
54 pages
ResIP White Paper The Mobile Packet Backbone Network A Compelling Multiservice IP Backbone Usecase PDF
No ratings yet
ResIP White Paper The Mobile Packet Backbone Network A Compelling Multiservice IP Backbone Usecase PDF
8 pages
Synce and Ieee 1588
No ratings yet
Synce and Ieee 1588
16 pages
I. UMTS Architecture
No ratings yet
I. UMTS Architecture
54 pages
Analysis of KT S 5G Network Architecture PDF
No ratings yet
Analysis of KT S 5G Network Architecture PDF
7 pages
08.1 Presentation of Nera Networks
No ratings yet
08.1 Presentation of Nera Networks
25 pages
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
Connectivity Prediction in Mobile Ad Hoc Networks for Real-Time Control
From Everand
Connectivity Prediction in Mobile Ad Hoc Networks for Real-Time Control
Sebastian Thelen
5/5 (1)
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
UMTS RNC Product Description v1 07 July 2010
No ratings yet
UMTS RNC Product Description v1 07 July 2010
84 pages
Nokia - LTE - RL40 - Features Description
No ratings yet
Nokia - LTE - RL40 - Features Description
72 pages
E-UTRAN System Timers & Constants - Ver1
No ratings yet
E-UTRAN System Timers & Constants - Ver1
12 pages
06wk48 - CSSR Improvement Fach Power Trial Phase II - VDF UK
No ratings yet
06wk48 - CSSR Improvement Fach Power Trial Phase II - VDF UK
19 pages
RRC Signaling Trend - Trial - Change Access Parameter - Wadi & Majmaah - r2
No ratings yet
RRC Signaling Trend - Trial - Change Access Parameter - Wadi & Majmaah - r2
7 pages
3g 4g InterworkingSupport
100% (1)
3g 4g InterworkingSupport
34 pages
PS Call Management
No ratings yet
PS Call Management
84 pages
3g Handover Issues
No ratings yet
3g Handover Issues
37 pages
Trial Report: Huawei Optimization Team Eastern Region 29-May-2013
No ratings yet
Trial Report: Huawei Optimization Team Eastern Region 29-May-2013
53 pages
Call Trace Troubleshooting Examples - Several Releases
No ratings yet
Call Trace Troubleshooting Examples - Several Releases
79 pages
R99NPO TrainingCounters UA6
No ratings yet
R99NPO TrainingCounters UA6
368 pages
3G Cluster Packet Service Optimization Report
No ratings yet
3G Cluster Packet Service Optimization Report
72 pages
PM89563 - Enhanced Layer 2 For Uplink - Feature Assessment ORF FOA - May 2014 - V1
No ratings yet
PM89563 - Enhanced Layer 2 For Uplink - Feature Assessment ORF FOA - May 2014 - V1
44 pages
WCDMA Power Calculation Guide
79% (14)
WCDMA Power Calculation Guide
14 pages
HSDPCCH Trial To Increase - Hsupa TH (T
No ratings yet
HSDPCCH Trial To Increase - Hsupa TH (T
17 pages
3g Handover Issues
No ratings yet
3g Handover Issues
37 pages
Module 4A Receive RF Amp
No ratings yet
Module 4A Receive RF Amp
1 page
Baroque Classical Dance Forms PDF
100% (1)
Baroque Classical Dance Forms PDF
4 pages
GG2 - SB 60 63
No ratings yet
GG2 - SB 60 63
4 pages
Amada ITS Technical Manual 45899
No ratings yet
Amada ITS Technical Manual 45899
104 pages
7-Las D5-Music-W1-Q1
No ratings yet
7-Las D5-Music-W1-Q1
6 pages
Popular Science Australia September 2017
100% (1)
Popular Science Australia September 2017
85 pages
Radio Advertising: Presented By:-Ankita Bohra Kalgi Pandya Nikita Porwal Ritu Malik
No ratings yet
Radio Advertising: Presented By:-Ankita Bohra Kalgi Pandya Nikita Porwal Ritu Malik
12 pages
Google
100% (1)
Google
64 pages
SEC-OGC Opinion No. 21-18
No ratings yet
SEC-OGC Opinion No. 21-18
6 pages
All My Single Ladies Sponsorship Proposal
No ratings yet
All My Single Ladies Sponsorship Proposal
15 pages
Timbre - 05
No ratings yet
Timbre - 05
7 pages
Short Story
No ratings yet
Short Story
12 pages
Z 40 Manual
No ratings yet
Z 40 Manual
8 pages
Dominant Seventh Sharp Ninth Chord - Wikipedia
No ratings yet
Dominant Seventh Sharp Ninth Chord - Wikipedia
7 pages
The NTA Phenomenon
No ratings yet
The NTA Phenomenon
4 pages
Manual Instalacion Pm810
No ratings yet
Manual Instalacion Pm810
166 pages
Quiz Unit 4
50% (2)
Quiz Unit 4
5 pages
Interworking of IP Telephony With Legacy Networks
No ratings yet
Interworking of IP Telephony With Legacy Networks
12 pages
UMTS Basic Refresher
No ratings yet
UMTS Basic Refresher
26 pages
Xmas List
100% (1)
Xmas List
4 pages
BardwoodGrove Rulebook
No ratings yet
BardwoodGrove Rulebook
24 pages
KWWL Chart
No ratings yet
KWWL Chart
1 page
PHIL ART DEV - LADIA, Apple - BSECE 2-1P
No ratings yet
PHIL ART DEV - LADIA, Apple - BSECE 2-1P
2 pages
Chapter 10 - Wave Propagation in Satellite Communication
No ratings yet
Chapter 10 - Wave Propagation in Satellite Communication
28 pages
Designing A Class A Power Amplifier Using The Load-Pull Method
No ratings yet
Designing A Class A Power Amplifier Using The Load-Pull Method
15 pages
Self Install Kit Manual Eng PDF
No ratings yet
Self Install Kit Manual Eng PDF
22 pages
T8 B17 FAA Trips 3 of 3 FDR - Checklist For Accidents - 9-11 Personnel - Emails Re Documents 170
No ratings yet
T8 B17 FAA Trips 3 of 3 FDR - Checklist For Accidents - 9-11 Personnel - Emails Re Documents 170
18 pages
'Musical Instruments of Latin America
No ratings yet
'Musical Instruments of Latin America
12 pages
The World of Hindusthani Ragas
No ratings yet
The World of Hindusthani Ragas
19 pages