Hld Report Ipran Iam v2

IPRAN Network High Level Design

for Maroc Telecom

Issue 1.1

Date Tuesday,July 15, 2011

IPRAN Network High Level Design for Maroc Telecom

Contents

1 Introduction..................................................................................41.1 Objectives..........................................................................................................................................................4

1.2 Scopes................................................................................................................................................................4

2 UMTS Network Structure................................................................52.1 Existing URAN Network...................................................................................................................................5

2.2 Target Network..................................................................................................................................................5

3 RAN Network Design Requirement..................................................73.1 Capacity Requirement of Target Network.........................................................................................................7

4 Principles and Information of IPRAN O&M Design............................94.1 O&M Network Topology...................................................................................................................................9

4.2 O&M Networking Principle and Design...........................................................................................................9

4.2.1 Existing O&M Network Topology...........................................................................................................9

4.2.2 Target O&M Network Topology............................................................................................................10

4.2.3 O&M IP Planning Design.......................................................................................................................11

4.2.4 NodeB OM Channel Design...................................................................................................................12

4.3 NE Time Synchronization Principle and Design.............................................................................................15

5 RAN System Clock Synchronization Design....................................165.1 RNC System Clock Source Design.................................................................................................................16

5.2 NodeB System Clock Source Design..............................................................................................................16

6 IPRAN Resource Distributed Design..............................................186.1.1 RNC Transmission Interface Boards Layout Design.............................................................................18

6.1.2 NodeB Transmission Interface Boards Layout Design..........................................................................19

6.1.3 Boards Distribution Layout....................................................................................................................19

7 RAN Transmission Interface Capability Design...............................227.1 Iub Transmission Interface Capability Design.................................................................................................22

7.1.1 Traffic Mapping on IP Strategy Design..................................................................................................22

7.1.2 Total Iub User Plane Throughput for Iub IP Transmission Estimation..................................................24

7.2 Iub Transmission Configuration Design for Typical NodeB...........................................................................25

8 IPRAN Transmission Interface Reliability Design............................268.1 Iub Transmission Interface Networking Reliability Design............................................................................26

2

http://wissal.ma/servlet/iam.servlet.accueil.ServletAccueil?tache=Accueil&refEsp=0


8.1.1 Iub Networking Topology.......................................................................................................................26

8.1.2 Iub Interface Boards Redundancy Design..............................................................................................27

8.1.3 Iub Transmission Ports Redundancy in RNC Design.............................................................................27

8.1.4 Iub Transmission Fault Detection Design..............................................................................................27

8.1.5 Iub Transmission QoS Difference Design..............................................................................................27

8.1.6 Iub Transmission Layer Address Allocation Design..............................................................................29

9 Acronyms and Abbreviations..........................................................................31

3



1 Introduction

1.1 ObjectivesBased on the customer requirement to migrate the ATM IUB interface to IPRAN network, high level design (HLD) is to reasonably design the UMTS RAN networking to establish an IP UTRAN network. The UTRAN network has the following features:

Using IP as the bearer on IUB interface for all 3G services

Being of good security, high reliability, and reasonable resource allocation

Supporting features extension

HLD focuses on Huawei RAN network elements (NEs) ,mainly NodeB and RNCs.

1.2 ScopesThis document involves HLD for the Maroc Telecom IPRAN.

According to the features of the Huawei UMTS product, HLD covers IPRAN networking migration, focusing on operation and maintenance (O&M), system clock synchronization, IPRAN resource distributed design, transmission interface capability, transmission interface networking reliability, interconnection negotiation, and common features.

4



2 UMTS Network

Structure

2.1 Existing URAN NetworkIub interface on existing UTRAN network is based on ATM over SDH networks, 19 RNCs and 1600 NodeB communicate each other through the TDM network,the RNC clock synchronizationis provided by IUCS interface, NodeBs use line clock extracted from IUB E1 links.

M2000 maintain RNCs by direct connection based on PPP over E1,all NodeB communicate with M2000 through RNCs, in other word the OM link of NodeB is carried over IUB.

Fig: Existing UTRAN Network Architecture

2.2 Target NetworkIn the targeted IPRAN network, Maroc Telecom requires to migrate from ATM to IP all de services carried on IUB interface.

The TDM E1s are maintained only for Clock synchronization in the first phase ,later on, SyncE and/or PTP synchronization will replace E1 .

IUCS,IUPS,IUR interfaces will not be changed.

5



Fig: Target UTRAN Network Architecture

6



3 RAN Network

Design Requirement

3.1 Capacity Requirement of Target Network

Target Network Scale

The entire target Maroc Telecom will include 19 RNCs and around 1600 NodeBs which are distributed as below

Distribution of NodeBs On 11/05/2011

NE NameTotal NodeB

RNC_TangerMsallah 97RNC-AinSbaa 136RNC-CasaAnwal 149RNC-CasaGare 106RNC-CasaNU 148RNC-CasaOualfa 26RNC-CasaSidiOtmane 30RNC-FesAdarissa 44RNC-FesNarjis 74RNC-HayNahda 129RNCJedida 94RNC-Kenitra 80RNC-Meknes 163RNC-RabatCentre 1RNC-Settat 63RNC-TangerIbnTaymia 1RNC-TangerPrincipal 114RNC-Tetouan 83RNC-TetouanMyHassan 67Total 1605

Interface Connection Requirement

Each RNC connect to IPRAN through 2 Different access points (CEX)

7



The NodeBs connect to IPRAN using one GE optical port

All Connections are 1 GE optical fibers

Fig: RNC and NodeB interconnection with the IPRAN

Product Version Information

Version Information

RNC BSC6810 V200R011, BSC6900 V200R011

Node B BTS3900 V200R011, BTS3812 V200R011

Requirements for Transmission QoS

Requirements for Iub transmission QoS:

　Time delay（ms）

Delay variation（ms） Packet lost

　IUBMax suggest Max suggested Max suggested40 10 15 2 1.00E-03 1.00E-04

8



4 Principles and

Information of IPRAN O&M Design

4.1 O&M Network TopologyM2000 manage and maintain NodeB directly through IP network without passing by RNC.

Fig: Topology of Target O&M network

4.2 O&M Networking Principle and Design

4.2.1 Existing O&M Network Topology

The RNC BAMs are connected to the local router using FE ,each RNC uses a.b.c.d/29 subnet.The RNC router is then connecter to Central OMC router in Sokarno using E1.Static routes are defined in RNC ,M2000 and on Both Local and central routers.

The NodeB communicate with M2000 through RNCs, which define internal routes between Iub interface and M2000.

9



Fig: Topology of Existing O&M network

Existing OM Network IP design:Used IP Remarks2.X.Y.Z/8

PPP between RNC router and M2000 router

3.X.Y.Z/8...20.X.Y.Z/8172.121.139.0/24

RNC BAM Segment172.121.138.0/24192.168.8.0/24 M2000 Segment

4.2.2 Target O&M Network Topology

In order to enable the M2000 to access NodeB directly through IPRAN, The M2000 will connect to IP:MPLS backbone, The OM channel reliability and security can be enhanced by connecting both active and standby OSS system to IP backbone.

10



Fig: NodeBs OM/IPRAN configuration

Hay nahda and Sokarno M2000 local routers configure VRRP to assure geographical redundancy.The M2000 LAN segment will not be changed 192.168.8.0/24Here below the actual addressing for M2000 servers and routers:

M2000 IP address Router IP addressSokarno 192.168.8.22/24 192.168.8.88/24

Hay Nahda 192.168.8.24/24 192.168.8.89/24

4.2.3 O&M IP Planning DesignThe RNC OM Link will not be changed,

The NodeB is maintained by the M2000 or the maintenance terminal (including LMT) through the remote OM channel.

The recommended remote NodeB maintenance channel is over the IP link. IP data streams are terminated on the Iub interface board. Through IP routing, O&M packages are routed to the main control board of the NodeB for processing.

11



Fig: NodeB ETHIP & OMIP

the OM IP addresses are numbered in ascending order on the same network segment according to NodeB numbers.

For each RNC ,NodeB group are /24 network segment, maximum reserved IP per RNC is 254 ,the proposed planning is as below:

RNC Name Target Node B OM NodeBRNC-CasaGare 250 10.146.0.0/24RNC-AinSbaa 250 10.146.1.0/24RNC-CasaAnwal 250 10.146.2.0/24RNC-CasaNU 250 10.146.3.0/24RNC-CasaOualfa 250 10.146.4.0/24RNC-CasaSidiOtmane 250 10.146.5.0/24RNC-FesAdarissa 250 10.146.8.0/24RNC-FesNarjis 250 10.146.9.0/24RNC-Meknes 250 10.146.10.0/24RNC-Kenitra 250 10.146.12.0/24RNCHayNahda 250 10.146.13.0/24RNC-RabatCentre 250 10.146.14.0/24RNCJedida 250 10.146.16.0/24RNC-Settat 250 10.146.17.0/24RNC-TangerIbnTaymia 250 10.146.20.0/24RNC-TangerPrincipal 250 10.146.21.0/24RNC-Tetouan 250 10.146.22.0/24RNC-TetouanMyHassan 250 10.146.23.0/24RNC_TangerMsallah 250 10.146.24.0/24

NodeB OM IP planning

12



4.2.4 NodeB OM Channel Design

OMCH Policy

It is recommended that the NodeB is directly routed to the M2000 for maintenance without passing the RNC. This can separate service channels from maintenance channels, thus enhancing network security.

The OM packet are carried over the same VLAN 200,OM and other services on IPRAN are differentiated using QoS priority .

DSCP Design

The Differentiated Service is a method of providing different services with different transmission priorities.

All the IUB services are carried over a single VLAN, the priority policy are assured by layer 3 and layer 2 tagging:

3GPP Traffic TypePHB (Per Hop

Behavior) DSCPIEEE802.1 Ppriority

Signal Plane Common Channel,SRB CS6 48 6

User Plane

AMR Voice EF 46 5Visio EF 46 5

R99 Streaming AF41 34 4R99 Interactive AF31 26 3

R99 Background AF31 26 3SHSPA Streaming AF41 34 4

HSPA Interactive, HSPA Background AF21 18 2

OAM O&M AF41 34 4

The recommended OM DSCP is 34, at IEEE802.1p level the OM is tagged with priority 4,

OMCH Configuration

Route 1: On the NodeB side, configure a route to the M2000. The next hop is the interface IP address of the access Router to IPRAN.

Route 2: On the M2000, configure a route to the NodeB OMIP. The next hop is the interface IP address of the PE Router.

In addition, the routes of transmission equipment need to be configured.

OSPF is configured between OSS router and IP backbone

13



Figure 4-1 Configuring an OMCH

(1) Router A and B , Two PE use OSPF VPN, A---PE haynahda use sub interface to connect ,also Router B---PE sokarno

(2) switch E and F interface use the trunk to permit the VLAN pass.

(3) Router A -----M2000 haynahda do not use sub interface also M2000 sokarno------Router B.

(4) Router A and B configure VRRP in the interface which connected Switch C and D. the heard packets path like A--C---D---B.

14



OSS Node IP PE Node IP

M2000 Huawei Rabat Sokarno

192.168.111.1/30 PE_NE80E_RABAT_SOEKARNO_03 192.168.111.2/30

M2000 Huawei Rabat Hay Nahda

192.168.111.5/30 PE_NE80E_RABAT_HAY_NAHDA_02 192.168.111.6 /30

Tab: Proposal of IP Planning for M2000 interconnection with MPLS backbone

4.3 NE Time Synchronization Principle and Design

The RNC keep the same configuration of the time synchronization, it recover Time data from SNTP server set in M2000.

The NodeB can be set to the SNTP client only. The NodeB time synchronization server recommended by Huawei is the M2000:

NodeB time synchronization parameters:

Time Synchronization Parameter Recommended Value

Time synchronization server M2000

Address of the time clock synchronization server IP address of the M2000 server

Time synchronization period 6 hours

Number of the port used by the time synchronization server

123

Fig: Logical line of NodeB time synchronization

15



5 RAN System Clock

Synchronization Design

This chapter describes the system clock source design of the RNC and NodeB and flow directions of relevant system clocks.

5.1 RNC System Clock Source Design The RNC clock synchronization is provided by the STM1 link connecting the MGW to RNC.the RNC synchronization mode will not be changed after migration to IPRAN.

Fig: System clock stream of the RNC

5.2 NodeB System Clock Source DesignTow scenarios are supported by NodeB for clock synchronization:

16



The Iub interface uses currently the TDM transport: all NodeB are connected to RNC using E1, Therefore, it is recommended to set the NodeB to extract clock signals from the existing E1, or from any other transmission equipment able to provide 2Mhz input for the NodeB.

The NodeB supports also the IP clock synchronization, in this scenario; both SyncE and 1588v2 are supported by the BTS

E1 Clock Synchronization

Fig: E1 Clock synchronization

• Keep TDM transmission for NodeB synchronization (Synchronization Over E1)

• Smooth migration to IP

IP Clock Synchronization

17



Fig: IP Clock synchronization

• All service are based on metro IP network, no need for the E1 network for the clock

• The NodeB extract The clock using GE interface, the clock can be SyncE or 1588v2

• Clock source based on IP should be provided by IPRAN network

6 IPRAN Resource

Distributed Design

This chapter describes optimization design for RNC capabilities, involving board configuration, the port controller, NodeB allocation.

6.1.1 RNC Transmission Interface Boards Layout Design

The GOUa interface is the main GE interface of RNC,it s recommended to use 2 GOUa Board in load share mode to connect each RNC to IPRAN.The GOUa board performs the following functions:

Provides two channels over GE optical ports, which are used for IP transmission

Provides the Automatic Protection Switching (APS) function between the active and standby boards

Provides the routing-based backup and load sharing

18



Fig: Panel of the GOUa board

6.1.2 NodeB Transmission Interface Boards Layout Design

BTS 3900 will be provided with UTRP board, each UTRP board can be added in slot 4 or 5 in the BBU base band module.The UTRP support 2 GE optical ports.

Fig: Panel of the UTRP (with 2 GE port)

For BTS3812 / DBS a hardware upgrade is mandatory to support GE optical, for those sites an extra module will be provided to allow GE inter connection with IPRAN

19



6.1.3 Boards Distribution LayoutThe figure below shows an example of GOUa board configuration of the RNC according to the preceding design rules for board configuration.

Fig:Board configuration for the RNC

The design of GE ports per RNC is detailed in the following table

RNC 1st GE 2nd GE

RNC_TangerMsallahSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-AinSbaaSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-CasaAnwalSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-CasaGareSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-CasaNUSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-CasaOualfaSub 0 Slot 18 TX0

Sub 0 Slot 18 RX0

Sub 0 Slot 19 TX0

Sub 0 Slot 19 RX0

RNC-FesAdarissaSub 0 Slot 24 TX0

Sub 0 Slot 24 RX0

Sub 0 Slot 25 TX0

Sub 0 Slot 25 RX0

RNC-FesNarjisSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-HayNahda Sub 1 slot 18 Sub 1 slot 18 Sub 1 slot 19 Sub 1 slot 19

20



TX0 RX0 TX0 RX0

RNC-JedidaSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-KenitraSub 1 slot 26 TX0

Sub 1 slot 26 RX0

Sub 1 slot 27 TX0

Sub 1 slot 27 RX0

RNC-MeknesSub 1 slot 22 TX0

Sub 1 slot 22 RX0

Sub 1 slot 23 TX0

Sub 1 slot 23 RX0

RNC-SettatSub 2 Slot 24 TX0

Sub 2 Slot 24 RX0

Sub 2 Slot 25 TX0

Sub 2 Slot 25 RX0

RNC-SidiOtmaneSub 1 slot 20 TX0

Sub 1 slot 20 RX0

Sub 1 slot 21 TX0

Sub 1 slot 21 RX0

RNC-TangerPrincipalSub 1 slot 18 TX0

Sub 1 slot 18 RX0

Sub 1 slot 19 TX0

Sub 1 slot 19 RX0

RNC-TetouanSub 0 slot 16 TX0

Sub 0 slot 16 RX0

Sub 0 slot 17 TX0

Sub 0 slot 17 RX0

RNC-TetouanMyHassanSub 0 slot 26 TX0

Sub 0 slot 26 RX0

Sub 0 slot 27 TX0

Sub 0 slot 27 RX0

RNC-RabatCentreSub 1 slot 20 TX0

Sub 1 slot 20 RX0

Sub 1 slot 21 TX0

Sub 1 slot 21 RX0

RNC-TangerIbnTaymiaSub 0 slot 18 TX0

Sub 0 slot 18 RX0

Sub 0 slot 19 TX0

Sub 0 slot 19 RX0

RNC Ports allocation design

From NodeB side ,the UTRP board is configured in slot 4 or 5 as described here below:

Fig: usage of the UTRP interface boards in BTS/DBS 3900.

21



7 RAN Transmission

Interface Capability Design

This chapter provides recommended transmission configurations on the control plane and user plane of each IUB over IP interface .

7.1 Iub Transmission Interface Capability DesignThis section describes how different services on IUB are mapped over IP transmission resources.

7.1.1 Traffic Mapping on IP Strategy DesignIP transport networking of the Iub interface indicates that the protocol (IP) stack networking is used between the RNC and the NodeB.

With the development of data services, especially the introduction of the HSDPA/HSUPA, the Iub interface has larger and larger requirements for transmission bandwidth. Introducing the IP transmission technology can save the cost.

22



IP transport Networking

IP transport can transmit the services of different QoS in different ways. Real time services have higher priority than HSPA services. the figure here below shows the IP transport networking.

Fig: IP transport networking

The Maroc Telecom RNC is configured with the IP interface board (GOUa). The IP interface board is connected to the IP transmission network through the GE port.

The NodeB is connected to the IP transmission networks through the corresponding IP interface boards.

Design for the Transmission Resource Mapping Table

The transmission resource mapping table (TRMMAP) shown in following table is designed according to Maroc Telecoms requirement and the transmission resource allocation.

Service TypeIAM Request

Common channel EFIMS SRB EFSRB EFAMR voice EFR99 CS conversational AF41R99 CS streaming AF41R99 PS conversational AF41R99 PS streaming AF41R99 PS high PRI interactive AF31R99 PS middle PRI interactive AF31R99 PS low PRI interactive AF31R99 PS background AF31HSDPA Signal EFHSDPA IMS Signal EFHSDPA Voice AF41

23



HSDPA conversational AF41HSDPA streaming AF41HSDPA high PRI interactive AF21HSDPA middle PRI interactive AF21HSDPA low PRI interactive AF21HSDPA background AF21HSUPA Signal EFHSUPA IMS Signal EFHSUPA Voice AF41HSUPA conversational AF41HSUPA streaming AF41HSUPA high PRI interactive AF21HSUPA middle PRI interactive AF21HSUPA low PRI interactive AF21HSUPA background AF21

TRMMAP of the Iub interface in IP transport

7.1.2 Total Iub User Plane Throughput for Iub IP Transmission Estimation

Existing IUB Throughput

Based on the current IUCS, IUPS throughput per RNC and the number of NodeB attached to each RNC , an average of IUB throughput is calculated :

Total Iub Thruput Kbps

0

50000

100000

150000

200000

250000

300000

350000

24



The trend above shows the throutput of RNC Ainsebaa ( Iub interface including 144 NodeB),the peak required bandwidth for Iub is 300 Mbps, then the average of used Iub bandwidth per NodeB is 2 Mbps ,

Target IUB Throughput

Taking in consideration the expansion of the network and the introduction of new enhanced features, requirements in term of bandwidth are increased, therefore a model design of Iub is performed in order to respond to the future bandwidth demand.We admit the following assumption:

1) NodeB and RNC are both RAN112) HSPA+ 21 Mbps is activated (increase the traffic around 16% ) 3) Current bandwith is the the Physical Iub Bandwidth (7 Mbps)4) S222 is implemented in all hard ware (double the current traffic)5) No limitation in term of Hardware processing

Current Max bandwidhth :7 MbpsS222 Max Bandwidth ( x2): 14 Mbps

Hspa+ (+ 16%) = 16.24 Mbps

PS: the Model above is a theatrical one based on some assumption, an accurate model should take in account the Number of user per RNC and traffic model.

7.2 Iub Transmission Configuration Design for Typical NodeB

It s recommended to use 4 IPPATH in user plan to differentiate each service priority, for control plan NCP and CCP are assigned DSCP 48.

The Qos is assured according to layer 2 and layer 3 mapping (DSCP,VLAN priority)

Tx(kbps) Rx(kbps) DSCP Vlan Priority

Signal Plane

NCP 48 6CCP 48 6

User Plane

EF Physical Link BW Physical Link BW 46 5AF41 Physical Link BW Physical Link BW 34 4AF31 Physical Link BW Physical Link BW 26 3AF21 Physical Link BW Physical Link BW 18 2

OAM AF41 34 4

25



8 IPRAN

Transmission Interface Reliability Design

This chapter describes the reliability design of transmission interfaces, including the network topology of the Iub, redundancy of interface boards and ports, failure detection, QoS, transmission security design, and address allocation. This can ensure reliable and secure transmission, detect failures in time, and differentiate priorities to guarantee high-priority services.

8.1 Iub Transmission Interface Networking Reliability Design

8.1.1 Iub Networking Topology

Fig: Iub networking

The Iub interface uses the IP transmission and supports IP protocol stacks. Active and standby GOUa boards provide GE port to connect two CEX Routers ,the GOUa corresponding ports are configured in load share. Therefore The RNC provide 2 interface IP and one logical IP for communication. In NodeB side, one GE port is used to support connection.

The load sharing is assured by configuring 2 routes for each NodeB with different priority (high & low),

26



One of them pass through the active GOU the second one pass through standby one. the NodeBs are balanced in both GOU, in other Word 50% of NodeB High priority Routes is over active GOU, and the rest NodeB high priority routes are over standby GOU.

8.1.2 Iub Interface Boards Redundancy Design

Board Redundancy Principle

In the case of board backup, one board is active and the other is standby. When the active board is faulty, switchover occurs and the standby board serves as active board.

The processing capability of one pair of active and standby boards is equivalent to the processing capability of one active board.

Board backup can improve network reliability. Services can run normally so long as one of the active and standby boards works properly. In the case of non-redundancy, the failure of a board may interrupt network services.

Recommended Board Redundancy Mode

It is recommended that GOUa work in boards backup mode for the Iub interface.

8.1.3 Iub Transmission Ports Redundancy in RNC Design

GOUa Port Redundancy Principle

When a pair of GOUa boards work in the backup mode, the corresponding ports of the active and standby GOUa boards can be also in the backup mode, for example, port 0 of active board and port 0 of standby board. Board backup and port backup are independent,Thus GE ports can be both active while the related board are in active standby mode.

Recommended port Redundancy Mode

It is recommended that the 2 port are work in active in order to assure load sharing over Iub interface.

8.1.4 Iub Transmission Fault Detection DesignBFD detection can be used to detect gateway of RNC GE port connectivity according to RNC license.

8.1.5 Iub Transmission QoS Difference DesignIn terms of wireless network layers, the transmission network layers of the RNC and NodeB first map service priorities into the DiffServ PHB at the IP layer, mark the service priorities with different DSCPs, and then map the service priorities into the VLAN priority domain through the PHB. In addition, operators can flexibly configure the mapping between subscriber service priorities and IP QoS and the mapping between IP QoS and VLAN priorities according to the requirement.

Therefore, the QoS-related design covers the following three parts:

Transmission Resource mapping table for Iub, that is, the mapping between services and transmission resources (paths). It may use the default map for Iub IP.

DSCP values design for the user plane IPPATH, signaling plane SCTPLNK, and the OM in IP transmission.

27



Mapping between the DSCP and the VLAN priority in IP transmission.

QoS Requirements for IP over Ethernet Transmission

All the service are mapped on one VLAN. The DSCP and VLAN priority design agreed with the customer engineering and planning department is summarized in the table below:

3GPP Traffic TypePHB (Per Hop Behavior) DSCP IEEE802.1 Ppriority

Common Channel,SRB CS6 48 6Synchronisation (IEEE 1588) CS6 48 6AMR Voice EF 46 5Visio EF 46 5R99 Streaming AF41 34 4R99 Interactive AF31 26 3R99 Background AF31 26 3SHSPA Streaming AF41 34 4HSPA Interactive,HSPA Background AF21 18 2O&M AF41 34 4

QoS Requirements for IP over ATM Transmission

For few NodeB (around 10) the IUB transmission is expected to be based on IP over ATM, using PTN equipment, The related QOS design is as follow:

ATM service type ATM Service class PVC PW IP QOS

Signal PlaneNCP CBR 1/40

PW1 CS6CCP CBR 1/41ALCAP CBR 1/42

User Plane

AMR voiceR99 CS/PS conversational/streamingHSPA voice/conversational/streaming

RT-VBR 1/50

PW2 EFAMR voiceR99 CS/PS conversational/streamingHSPA voice/conversational/streaming

RT-VBR 1/51

AMR voiceR99 CS/PS conversational/streamingHSPA voice/conversational/streaming

RT-VBR 1/52

R99 PS interactive/background NRT-VBR 1/53PW3 AF21HSPA interactive/background UBR 1/54

OAM IPOA UBR+ 1/33

28



8.1.6 Iub Transmission Layer Address Allocation Design

RNC IP Address Planning

In IP L3 (FE/GE) networking, it is recommended to use Ethernet IP address for each FE/GE port to connect to the transmission equipment, another device IP should be defined as logical IP for communication with NodeB.

RNC IPRAN

Fig: IP requirements of RNC

IP1_IP2/IP3_IP4 are used for interconnection with CEX Device

IP5_IP6 are logical IP used for communication with NodeB (Service and OM)

IP1/IP3/IP5 can not be in the same subnet

The segment 1 and 2 are provided according to IPRAN planning design

The segment 3 is designed by UTRAN, in addition, another 3 segment per RNC are reserved by

UTRAN for future migration to dynamic routing.

RNC Name Target Node B OM & Service RNC & NE40RNC-CasaGare 250 192.168.1.0/28RNC-AinSbaa 250 192.168.1.16/28RNC-CasaAnwal 250 192.168.1.32/28RNC-CasaNU 250 192.168.1.48/28RNC-CasaOualfa 250 192.168.1.64/28RNC-CasaSidiOtmane 250 192.168.1.80/28RNC-FesAdarissa 250 192.168.1.96/28RNC-FesNarjis 250 192.168.1.112/28RNC-Meknes 250 192.168.1.128/28RNC-Kenitra 250 192.168.1.144/28RNCHayNahda 250 192.168.1.160/28RNC-RabatCentre 250 192.168.1.176/28RNCJedida 250 192.168.1.192/28RNC-Settat 250 192.168.1.208/28RNC-TangerIbnTaymia 250 192.168.1.224/28RNC-TangerPrincipal 250 192.168.1.240/28RNC-Tetouan 250 192.168.2.0/28RNC-TetouanMyHassan 250 192.168.2.16/28RNC_TangerMsallah 250 192.168.2.32/28

Fig:RNC IP Planning proposal for OM/services and NE40(dynamic routing)

29



NodeB Address Planning

In IP L3 (FE/GE) networking, the address of a NodeB (ETHIP) must not be on the same network segment as the RNC interface board’s ETHIP and DEVIP.

Each NodeB needs one ETHIP and one OMIP.

NodeB IPRAN

Fig: IP requirements of NodeB

IP1_IP2 is used for interconnection and traffic/signaling, the planning is provided by IPRAN IP3 is used for O&MNetwork 10.22.1.X is reserved and can not be usedThe IP planning proposal for NodeB OM is described in : 4.2.3 O&M IP Planning Design

30



9 Acronyms and

Abbreviations

AAL2 ATM Adaptation Layer type 2ALCAP Access Link Control Application PartAMR Adaptive Multi RateARP Address Resolution ProtocolATM Asynchronous Transfer ModeBAM Back Administration ModuleBITS Building Integrated Timing Supply System BPS Board Protect SwitchCCP Communication Control PortCN Core NetworkCRNC Controlling RNCCS Circuit Switched DHCP Dynamic Host Configuration ProtocolDRNS Drift RNSDSCP DiffServ Code PointEMS Element Management System ESN Electronic Serial NumberFE Fast EthernetFP Frame ProtocolGE Gigabit EthernetGPS Global positioning system GTP-U GPRS Tunneling Protocol User PlaneHDB3 High Density Bipolar 3HSDPA High Speed Downlink Packet AccessHS-DSCH High Speed Downlink Shared ChannelHSUPA High Speed Uplink Packet AccessIP Internet Protocol IPDV IP Packet Delay VariationIPLR IP Packet Loss RateIPTD IP Packet Time DelayIUUP Iu Interface User PlaneLMT Local Maintenance TerminalM2000 iManager M2000MAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServiceMDC Macro Diversity ConvergenceMGW Media GatewayMSC Mobile services Switching CanterMSP Multiplex Section ProtectionMTP3 Message Transfer Part Level 3 MTU Maximum Transfer Unit NBAP NodeB Application ProtocolNCP NodeB Control PortNodeB WCDMA base stationNRI Network Resource Identifier

31



NRNC Neighboring Radio Network ControllerNRT Non-Real-Time OMC Operation and Maintenance CenterOMIP IP Address of Operation and Maintenance PDCP Packet Data Convergence ProtocolPPP Point-to-Point ProtocolPPS Port Protect SwitchPS Packet Switched PVC Permanent Virtual ChannelQoS Quality of Service RAN Radio access networkRANAP Radio Access Network Application Part RBS RNC Business Subrack RLC Radio Link ControlRNC Radio Network ControllerRSS RNC Switch Subrack RTP Real-Time Transport Protocol RT-VBR Real Time Variable Bit Rate SAAL Signaling ATM Adaptation LayerSCTP Stream Control Transmission Protocol SDH Synchronous Digital Hierarchy SGSN Serving GPRS Support NodeSHO Soft HandOverSNTP Simple Network Time Protocol SRNC Serving RNCSTM-1 SDH Transport Module-1UBR Unspecified Bit Rate UDP User Datagram Protocol UE User EquipmentUMTS Universal Mobile Telecommunications SystemUNI User-Network Interface UTRAN UMTS Terrestrial Radio Access NetworkVCI Virtual Channel IdentifierVLAN Virtual Local Area Network VPI Virtual Path IdentifierVRRP Virtual Route Redundancy Protocol

32


Documents

Hld Report Ipran Iam v2