10 Rn30038en06gln0 Ru10 Overview

1 © Nokia Siemens Networks DRAFT <dnxxxxxxx> Issue <y-y>Confidental

Module 9 – RU10 Overview

Confidental2 © Nokia Siemens Networks

Agenda

• Objective is to give an overview on the transport related features coming in RU10

– UBR+ For Control Plane And Iu/Iur User Plane– RNC Ethernet Physical Interface– IP Based Iub for Flexi WCDMA BTS– Dual Iub for Flexi WCDMA BTS– IP based Iu-PS, Iu-CS and Iur– OSPF for Redundancy– Timing over Packet– Iub Transport QoS– QoS Aware HSPA Scheduling– Streaming QoS for HSPA


Nokia Siemens Networks WCDMA RAN System, Rel. RU10, Pre-release Documentation

RAN1192 UBR+ For Control Plane And Iu/Iur User PlaneFeature Introduction


Introduction

• This feature belongs to operating software.• Feature Description:

– The feature supports the operator to use the UBR+ ATM service category for control plane.

– However the feature allows in general the application of UBR+ in all the interfaces and for any application as depicted in the table below.

XNAxxManagement Plane (Note 1)

Note 2NAxxUser plane

xxxxControl Plane

IubIu-BCIurIu-cs / Iu-ps

Note 1: Management Plane does not belong to the 3GPP interfaces even associated here in this context.

Note 2: Supported by the RAS06 feature RAN1095 UBR+ for Iub user planeNA: Not applicable


Benefits for the operator

• Control Plane: – UBR+ instead of CBR with same bandwidth reservation reduces the

call set-up time if there is left-over transmission bandwidth capacity.

• Management Plane:– UBR+ instead of UBR allows to reserve bandwidth and such to

achieve some throughput guarantee for network management traffic.

• Iu User Plane:– UBR+ together with CBR allows to differentiate traffic from different

UMTS classes, e.g.:▪ CBR: conversational, streaming▪ UBR+: interactive, background

• Easier network planning


Functional description

• UBR+ ATM Service category:– Provides a minimum guarantee based on the MDCR configuration parameter. – May use all the available capacity of the bandwidth depending on the traffic

load conditions while CBR is limited to PCR.

VP capacity

VCC1 CBR (user plane); PCR

VCC2 CBR (control plane), PCR

VCC3 UBR+ (user plane), MDCR

bandwidth reservation forExample: RAS06 solution in Iub

VP capacity

VCC1 CBR (user plane); PCR

VCC2 UBR+ (control plane), MDCRVCC3 UBR+ (user plane), MDCR

RU10 solution in Iub

reduced transmission time -> faster signaling

actual traffic in VCC1 actual traffic in VCC2 actual traffic in VCC3



RAN77: RNC Ethernet Physical InterfaceFeature Introduction


Introduction

• RNC Ethernet Physical Interface – NP2GE, a new RNC interface unit– Provides two interfaces for Ethernet (based upon IEEE 803.2) support

• Each interface provides two different connectors to allow connectivity for either copper or optical networks

– 1 RJ45 - connector for twisted pair cable– 1 SFP connector (to be used for an optical SFP module) with an LC-Type

connector• The interfaces are designed to operate as gigabit Ethernet only

– They will operate in full duplex mode• Automatic MDI/MDIX detection to ease commissioning

– Misconfiguration of TX and RX directions if e.g. no cross-over cables are used and swapping of RX/TX directions are supported

• The Ethernet MTU is configurable– Defaults to 1500 octets to fit standard Ethernet networks– For more sophisticated networks Jumbo frames up to 4000 octets are

supported.


Interdependencies between features

• HW requirements– RNC must be equipped either with SF10E or SF20 to support NP2GE

units▪ Upgrade needed to SFU

• Dependencies/effects/connections to other features– This feature is needed for

▪ RAN 75: IP Based Iu-CS ▪ RAN 750: IP Based Iu-PS ▪ RAN 76: IP Based Iur▪ RAN 74: IP Based Iub for Flexi WCDMA BTS ▪ RAN 1449: Dual Iub for Flexi WCDMA BTS



RAN74 IP Based Iub for Flexi WCDMA BTSFeature Training



• This feature enables use of IP and Ethernet transport according to 3GPP Rel-5 and Rel-6 at the Iub interface for the Flexi WCDMA BTS and the RNC

• Enables OPEX and CAPEX savings for the operator due to lower cost access IP / Ethernet transport

BTS

E1

ATM

IP based Iub(Ethernet)

IP based Iub(Ethernet

ATM based Iub(SDH/PDH)

ATM based Iub(SDH/PDH

BTS

E1

BTS

Eth

BTS

Eth

IP

RNC

STM1


Functional Description

• Main building blocks for Dual Iub– 3GPP Rel-5/ Rel-6 compliant protocol stack

▪ It also supports Release 7 version of the NBAP messages– Dual transport protocol stack

▪ The RNC supports ATM and IP stacks in Iub▪ BTSs transport can be based either on ATM or on IP Iub

– Quality of Service– IPv4 support– BFD for connectivity supervision– Virtual LANs– Performance counters


Functional description: Quality of Service

• IP protocol is a connectionless protocol and packets are routed in the network without static reservations

• However, in the RAN certain QoS needs to be guaranteed for the RAB services and RAN functionalities

• QoS provision can be performed by applying DiffServ and IP CAC against the specified guaranteed bit rate

• There is no provision on a per call basis, but for traffic aggregates• Packets are marked according to the selected QoS, and based on this

information, the RNC, BTS and the routers will handle the packets• Qos is based on three main functions in RNC and BTS

- Traffic Classification- Scheduling and Shaping- Connection Admission Control


InteractiveDSCP

DSCP

DSCP

DSCP

DSCP

DSCP

6 Default PHBscorresponding to the IP egressscheduling queues

IP transport

EF

AF4

AF3

AF2

AF1

BE

DSCP

Operator configurablemapping

RNC (Application)IP Based Iub basic DSCP mapping

If EthernetVLAN in use:- VLAN tag / userpriority (0-7)

RNC / BTSDSCP to PHB mappingVLAN priority bit markingHS-

DSCH

E-DCHnRT HSPA

DSCP

HS-DSCH FP

E-DCH FP E-DCH FP DSCP

HS-DSCH FP DSCP

Background

Functional description: Traffic Classification

RT HSPA DSCP*

Conversational

Streaming

* RAN1004 Streaming QoS for HSPA licence needed

Interactive

Background

Conversational

Streaming

Common channels

RT DCH DSCP

PCH, FACH, RACH

SRB

R99 DCH CS

domain

R99 DCH PS

domain

CS AMR Speech

CS-T dataCS-NT data

nRT DCH DSCP

When packet is traversing in Diffserv network, DSCP is used to define PHB


Functional description: Traffic Classification cont’d• DSCP is forwarded by the RNC to the BTS during transport bearer setup by NBAP

RL Setup and RL Reconfiguration procedures– Parameter is carried in TNL QoS IE, DS parameter (requires Release 7 message

format)• All other IP traffic is also mapped to a DSCP:

▪ Control plane (NBAP)▪ ICMP▪ OSPF (RNC only)▪ BFD▪ O&M

• DSCPs are further mapped to PHBs (configurable)– 6 PHBs available in RNC and BTS: EF, AF4, AF3, AF2, AF1, BE(Note: for AF PHB, the drop precedence is not used)

• IP packets are marked according to the DSCP into ToS (Type of Service) field.• If VLANs are enabled, a PHB to VLAN priority bits mapping is defined.

– VLAN priority bits are marked according to the previous mapping– IP ToS marking with the DCSP is still performed

• Full range of DSCPs is supported with the optional RAN1253 Iub transport QoS feature.


Functional description: BTS Scheduling

• Each PHB is mapped to a queue• EF is served as Strict Priority• Other PHBs are served as WFQ• Highest priority queue is rate limited• Lowest priority queues are controlled by a WFQ scheduler (weights:

w1-w5)• Aggregate (interface) traffic is shaped to the specified transport

service capacity.


Functional description: RNC Scheduling

•There is a logical SP+WFQ scheduler per IP Based route (BTS)•The interface scheduler is also SP+WFQ, which aggregates traffic from each traffic class in each IP Based Route•Aggregate (interface) traffic is shaped to the specified transport service capacity.

Subject to possible change


Functional description: IP Connection Admission Control• IP Connection Admission Control (CAC) functionality is

implemented to confirm reasonable traffic load towards BTSs• The CAC is performed against the specified BTS guaranteed

capacity (usually the Iub bottleneck)• It is performed by the RNC in DL and by the BTS in UL• CAC applies to

– RT DCH– nRT DCH– Common Transport Channels– HSPA streaming (with RAN1004 Streaming QoS for HSPA)– HSPA interactive (with RAN1004)– HSPA background (with RAN1004)


Functional description: CAC Traffic Descriptors

• Set of 4 traffic descriptors for each bearer, one for UL and one for DL

– Maximum bit rate in IP layer– Average bit rate in IP layer– Maximum size of one IP packet– Average size of one IP packet

• Parameters include IP overhead, but do not include Ethernet overhead

• Traffic descriptors are defined in the RNC, and forwarded to the BTS by using a private NBAP message


Functional description: CAC Algorithms

• “Connection” bit rate:Bit rate of IP connection = MAX_Bitrate x 0.2 + AVE_Bitrate x 0.8

• IP based route CAC (RNC) /Interface CAC (BTS)IP Based Route Committed Bit Rate >= Σ Bit rate of IP connection

+ IP Based Route Signalling Committed Bit Rate+ IP Based Route DCN Committed Bit Rate

• Configurable parameters– IP Based Route Committed Bit Rate (RNC)– IP interface committed bit rate (BTS)– IP Based Route Signalling Committed Bit Rate– IP Based Route DCN Committed Bit Rate


RNC

Network dimensioning:capacity ≥IPRouteBw1 capacity ≥IPRouteBw2

BTS 1

IP CAC ensures thatguaranteed bitrate traffickeeps withinIPRouteComBitRate

CAC guaranteed traffic

Non-guaranteedtraffic

Rnc

Ethe

rnet

Bw

CAC guaranteedtraffic


CAC guaranteed traffic goes throughNon-guaranteed traffic could be dropped

IPR

oute

Bw

1

CAC guaranteed traffic


IPRouteComBitrate

IPR

oute

Bw

2

Network dimensioning:Σ IPRouteComBitRate < capacity < Σ IPRouteBw

IP route bandwidthis shaped to IPRouteBw

Transport network does not drop CAC guaranteed traffic- This is achieved with the queuing algorithm and following the network dimensioning rules- all CAC guaranteed traffic has to be mapped to (highest) priority PHB/VLAN classes which have high enough weight in transport

BTS 2

CAC guaranteedtraffic


Functional description: CAC vs. Scheduling

IPRouteComBitrate


Functional description: IPv4

• IPv4– Only IPv4 is supported– UDP protocol is used to carry Frame Protocol (FP) frames

• IP fragmentation/reassembly– In Iub a maximum MTU of 1500 bytes is supported. However the

packets could exceed that size, which requires fragmentation:▪ Uplink user plane: IP fragmentation is applied in the BTS. RNC performs

reassembly▪ Downlink user plane: FP fragmentation is applied in the RNC. BTS

handles the fragments without need for reassembly▪ Control plane: SCTP performs message fragmentation in DL. No need for

IP fragmentation


Functional description: BFD

• BFD (Bidirectional forwarding detection) is used to monitor user plane availability (similar solution as for RAS06 Hybrid feature)

BTS RNC

Actual transmission interval (jitter: -12.5%)

TX

Control packets

Negotiated Transmission Interval (TI) = Max [Local DesiredMinTxInterval, Remote Required Min RX Interval]

RX

Detection Time = DetectMult x Remote TI(at least one packet has to be received)

Same in the other direction


Functional description: VLANs

• Virtual LANs are supported for two different applications:– Radio Network split (broadcast domain): Traffic from a number of BTSs is

limited to a broadcast domain▪ A host is broadcasting some packets, e.g. when sending ARP requests ▪ => increased security and less overhead

– Layer 2 prioritization: Ethernet packets can be tagged with a priority for prioritization in the L2 network. Priority is defined based on the PHB


Functional description: Addressing

To N

etA

ct

• RNC:– Address pool for User Plane (10 per port)– Address pool for Control Plane

• BTS:– One address for User Plane and for Control Plane– Two addresses for O&M (FTM and BTS)


Implementation in RAN

• New Ethernet physical interface HW and new SW are necessary in the RNC

• A license is needed for this feature• Ethernet physical interface HW and new SW are necessary in the Flexi

WCDMA BTS– Requires FlexiTransport Ethernet + E1/J1/T1 if HW module in the

FlexiWCDMA BTS.▪ FTIA, a hybrid PDH/Ethernet transport sub module, provides 4xE1/T1/JT1

(symmetrical, 120 Ohm), 2x10/100Base-TX and 1x optional optical Gigabit Ethernet interfaces.

▪ FTJA, another hybrid PDH/Ethernet transport sub module, provides 4xE1 (coaxial, 75 Ohm), 2x10/100Base-TX and 1x optional optical Gigabit Ethernet interfaces.

– In RNC this feature requires NP2GE Gigabit Ethernet interface unit. That will be available for RNC2600 (RAN1197). For RNC196 and RNC450 HW upgrade is needed (see RAN1225)

• Synchronization is by the feature RAN1254 Timing over Packet



RAN1449 Dual Iub for Flexi WCDMA BTSFeature Training


Introduction

• This feature enables the utilization of ATM Iub protocol stack for delay critical traffic and IP Iub protocol stack for more delay tolerant traffic

– There is no need for PW emulation

• Dual Iub allows using Ethernet for HSPA, e.g. via Carrier Ethernet or DSL, with significant cost savings compared to leased E1/J1/T1s


Functional description: General

• Flexi WCDMA BTS and RNC are connected simultaneously by both IP based link and ATM based link.

BTS

E1

ATM




BTS

E1

BTS

Eth

IP

RNC

STM1

E1

Dual Iub




Functional description: Traffic Mapping

• Rel99 RT, NRT, Control plane and O&M is carried over ATM Iub over E1s / STM1s

• HSPA is carried over IP Iub over Ethernet

BTSTransmission RNC

Ethernet Network

TDM Networkn x E1 STM1RT

Control Plane& O&M

CBR VCC’s

CBR VCC’s

RTUBR+ VCC’s NRTNRT

ATMSwitch

TunnelHSPAHSPA

Control Plane& O&M

VPC VPC


Functional description: Building Blocks

• Main building blocks for Dual Iub – 3GPP Rel-5/ Rel-6 compliant protocol stack

▪ It also supports Release 7 version of the NBAP messages– Dual transport protocol stack

▪ The RNC supports ATM and IP stacks in Iub. Node Bs transport can be based either on ATM or on Dual Iub

– Quality of Service– IPv4 support– BFD for connectivity supervision– Virtual LANs– Performance counters

• Same functionality for the IP path as in the Iub over IP– Scheduling, Quality of Service and Traffic Classification


InteractiveDSCP

DSCP

DSCP

DSCP

DSCP

DSCP


IP transport

EF

AF4

AF3

AF2

AF1

BE

DSCP


RNC (Application)Dual Iub basic DSCP mapping

If EthernetVLAN in use:- VLAN tag / userpriority (0-7)

RNC / BTSDSCP to PHB mappingVLAN priority bit marking

HS-DSCH

E-DCHnRT HSPA

DSCP

HS-DSCH FP

E-DCH FP E-DCH FP DSCP

HS-DSCH FP DSCP

Background

Functional description: Traffic Classification

RT HSPA DSCP*

Conversational

Streaming

* RAN1004 Streaming QoS for HSPA licence needed



implemented to confirm reasonable traffic load towards BTSs• The CAC is performed against the specified BTS guaranteed

capacity (usually the Iub bottleneck)• It is available ONLY if RAN1004 Streaming QoS for HSDPA

traffic is also available– Implementation is the same as for IP over Iub

• It is performed by the RNC in DL and by the Node B in UL• CAC applies to

▪ HSPA streaming (with RAN1004 introducing GBR)▪ HSPA interactive (with RAN1004 introducing NBR)▪ HSPA background (with RAN1004 introducing NBR)



•Dependencies/effects/connections to other features– This feature requires the Ethernet physical interface both in the Flexi

WCDMA BTS and in the RNC▪ Requires FlexiTransport Ethernet + E1/J1/T1 if HW module in the

FlexiWCDMA BTS• FTIA, a hybrid PDH/Ethernet transport sub module, provides 4xE1/T1/JT1

(symmetrical, 120 Ohm), 2x10/100Base-TX and 1x optional optical Gigabit Ethernet interfaces

• FTJA, another hybrid PDH/Ethernet transport sub module, provides 4xE1 (coaxial, 75 Ohm), 2x10/100Base-TX and 1x optional optical Gigabit Ethernet interfaces

– In RNC this feature requires NP2GE Gigabit Ethernet interface unit. That will be available for RNC2600 (RAN1197). For RNC196 and RNC450 HW upgrade is needed (see RAN1225)

– The end-user will have the same service experience with this feature as with the default ATM transport option

– This feature does not replace any older features


Nokia Siemens Networks WCDMA RAN System, Rel. RU10, Pre-release DocumentationRAN750 IP Based Iu-PSRAN75 IP Based Iu-CSRAN76 IP Based IurFeature Training


Introduction

• These features enable the use of IP and Ethernet transport according to 3GPP Rel-5 and Rel-6 at the Iu-PS, Iu-CS and Iur interface for the RNC

• Benefits of this feature– OPEX and CAPEX savings in transport between RNC and Core

Networks nodes– Allows more cost efficient transport network for Iu-PS, Iu-CS and Iur

traffic



• Main building blocks for IP Based Iu-PS are – 3GPP Rel-5/ Rel-6 compliant protocol stack– Dual stack (ATM Iu-PS and IP Iu-PS simultaneously) in the RNC

▪ A connection towards one single SGSN can be either ATM or IP based– Quality of Service– IPv4 support– IP IU-PS error handling– Performance counters

• Main building blocks for IP Based Iu-CS are – 3GPP Rel-5/ Rel-6 compliant protocol stack– Dual stack (ATM Iu-CS and IP Iu-CS simultaneously) in the RNC

▪ A connection towards one single MGW can be either ATM or IP based– Quality of Service– IPv4 support– RTP/RTCP– Performance counters

• Main building blocks for IP Based Iur are – 3GPP Rel-5/ Rel-6 compliant protocol stack– Dual stack (ATM Iur and IP Iur simultaneously) in the RNC

▪ A connection towards a neighbor RNC can be either ATM or IP based– Quality of Service– IPv4 support– BFD for connectivity supervision possible since connection between two NSN network elements– Performance counters


Functional description: Quality of Service

• IP protocol is a connectionless protocol and packets are routed in the network without static reservations

• However, in the RAN certain QoS needs to be guaranteed for the RAB services and RAN functionalities

• QoS provision can be performed by applying DiffServ and IP CAC against the specified guaranteed bit rate

• There is no provision on a per call basis, but for traffic aggregates• Packets are marked according to the selected QoS, and based on this

information, the RNC and the routers will handle the packets• Qos is based on three main functions in RNC

▪ Traffic Classification▪ Scheduling and Shaping▪ Connection Admission Control


DSCP

DSCP

DSCP

DSCP

DSCP

DSCP


IP transport

EF

AF4

AF3

AF2

AF1

BE

DSCP


IPA platformDSCP to PHB mapping

Functional description: Traffic Classification (Iu-CS and PS)

Conversational

Streaming

ApplicationIPQM object

Interactive THP1

Background

Interactive THP2

Interactive THP3


DSCP

DSCP

DSCP

DSCP

DSCP

DSCP


IP transport

EF

AF4

AF3

AF2

AF1

BE

DSCP


Application IPA PlatformDSCP to PHB mapping

Functional description: Traffic Classification in Iur

Interactive

Background

Conversational

Streaming

RT DCH DSCP

R99 DCH CS

domain

R99 DCH PS

domain

CS AMR Speech

CS-T dataCS-NT data

nRT DCH DSCP

Note: No HSPA over Iur


Functional description: Traffic Classification cont’d• All other IP traffic is also mapped to a DSCP

▪ Control Plane (RANAP in Iu-PS and Iu-CS and RNSAP in Iur)▪ ICMP▪ BFD (Iur, like in Iub)▪ OSPF

• DSCPs are further mapped to PHBs (configurable)▪ 6 PHBs available in RNC and BTS: EF, AF4, AF3, AF2, AF1, BE▪ (Note: for AF PHB, the drop precedence is not used)

• IP packets are marked according to the DSCP into ToS field


Functional description: RNC Scheduling

• Each PHB is mapped to a queue• EF is served as Strict Priority• Other PHBs are served as WFQ• Highest priority queue is rate limited• Lowest priority queues are controlled by a WFQ scheduler (weights: w1-w5)• Aggregate (interface) traffic is shaped to the specified transport service capacity• WRED is also supported to avoid TCP global synchronization.



implemented to confirm reasonable traffic load towards the SGSN

• The CAC is performed against the specified IP interface guaranteed capacity

• It is performed in DL and in UL• CAC applies to

– PS conversational– PS streaming– CS conversational– CS streaming– RT DCH– nRT DCH

Iu-PS

Iu-CS

Iur


Functional description: CAC Traffic Descriptors

• Set of 4 traffic descriptors for each bearer, one for UL and one for DL

– Maximum bit rate in IP layer– Average bit rate in IP layer– Maximum size of one IP packet– Average size of one IP packet

• Parameters include IP overhead, but do not include Ethernet overhead


Functional description: CAC Algorithms

• “Connection” bit rate:Bit rate of IP “connection” = MAX_Bitrate x 0.2 + AVE_Bitrate x 0.8

• IP based route CACIP Based Route Committed Bit Rate >= Σ Bit rate of IP connection

• Configurable parameters▪ IP Based Route Committed Bit Rate



• IPv4– Only IPv4 is supported– UDP protocol is used to carry

▪ GTP-U frames (Iu-PS)▪ RTP (real-time transport protocol) and RTCP (real-time transport control

protocol) frames (Iu-CS)▪ FP frames (Iur)

• Physical interface options for RNC– IP over Ethernet for the user plane and the control plane– IP over ATM for the user and control plane– IP over ATM for the user plane (legacy ATM transport option) and for

the control plane


Functional description: BFD

• BFD control packets are encapsulated on the top of UDP• A BFD session is established between the RNC and each

neighbour RNC• Detection time depends rate of the control packets and the

number of packets needed to detect the failureDetection time =

DetectMult (received from the peer) x MAX[RequiredMinRxInterval, DesiredMinTXInterval (received from the peer)]


Functional description: Addressing

• Address pool for User Plane (10 per port)• Address pool for Control Plane

RNC

IP termination(address pool)

ICSU

IP I/F # 1IP Address A

IP I/F # 2IP Address B

DMPG

DMPG

UP + CPCP

UP

Port 0

IP termination(address pool)DMPG

Port 1

UP



• New physical interface HW and new SW are necessary in the RNC

– HW requirements▪ NP2GE Gigabit Ethernet interface unit

• Will be available for RNC2600 (RAN1197). ▪ For RNC196 and RNC450 HW upgrade is needed (see RAN1225)

• A license is needed for this feature



• Dependencies/effects/connections to other features– This feature requires the RNC Ethernet Physical Interface feature– This feature needs to be activated in order to use RAN1510 ”OSPF for

redundancy”– The end-user will have the same service experience with this feature

as with the default ATM transport option– This feature does not replace any older features



RAN1510 OSPF for RedundancyFeature Training


Introduction

• This feature provides a redundancy solution for all RNC IP/Ethernet interfaces with Open Shortest Path First (OSPF) protocol

• As OSPF is unaware of the underlying protocol layers, it is well suited for different network environments and usable as a generic solution

• OSPF provides dynamic redundancy with two alternative routes allowing a quick recovery from failures without need of immediate human intervention

• Operator will benefit from enhanced network protection and better experience of network availability


Functional Description

• This feature can be used in any logical interface supporting IP• Two routes are provided for the each IP termination point by means of

virtual addressing• OSPF Hello protocol is used to monitor the route availability between

network elements• OSPF detects topology changes based on interface status (e.g. interface

will go down by failure on the Ethernet link) or the failure to receive a Hello packet response within specified time

• After a route failure is detected, the RNC starts re-routing the IP packets via an alternate route.

– As two interfaces on the same unit are used, this feature gives also interface protection

• OSPF advertises the change in the route by sending an LSA (Link-State Advertisement)

• OSPF is supported by most routers, MGWs and SGSNs


Addressing

• Virtual addressing– OSPF redundancy in the RNC is used together with virtual IP

addressing– The RNC has a virtual network interface card and a virtual IP address

has an interface to a virtual internal IP network, which contains the RNC virtual address as the one and only host

– The virtual address can be reached through any of the two physical interfaces

• Although two routes are always possible, one of them is given much lower cost than the other


Normal Operation

Configuration before route failure

RNCOther

network elementsIF0

IF1

IP subnetVirtual interface

IP subnet

IP subnet

VirtualIP address Interface address

Interface address

Working path

Virtual network


Route Failure

RNCOther

network elementsIF0

IF1

IP subnetVirtual interface

IP subnet

IP subnet

VirtualIP address Interface address

Interface address

Virtual network

Configuration after route failure

Working path

Faulty path



• New SW is necessary in the RNC• Licenses are needed for this feature and for the features in

the dependency list• HW requirements

▪ In RNC this feature requires NP2GE Gigabit Ethernet interface unit. That will be available for RNC2600 (RAN1197). For RNC196 and RNC450 HW upgrade is needed (see RAN1225)



• Dependencies/effects/connections to other features– This feature requires the RNC Ethernet Physical Interface feature– This feature requires the activation of

▪ RAN75 IP Based Iu-CS, ▪ RAN750 IP Based Iu-PS, ▪ RAN76 IP Based Iur, ▪ RAN1449 Dual Iub for Flexi WCDMA BTS or ▪ RAN74 IP Based Iub for Flexi WCDMA BTS

– This feature does not replace any older features


Nokia Siemens Networks WCDMA RAN System, Rel. RU10

RAN1254: Timing over PacketFeature Training


Introduction

• Timing over Packet (ToP) provides means for providing synchronization reference for base stations in Ethernet/packet transport networks

• It consists of a Master Clock at the RNC site, Slave Clocks integrated into base stations and related software

• Timing over Packet solution allows the operator to take full advantage of Ethernet/packet transport in BTS backbone

• Feature provides CAPEX/OPEX savings– No need for separate TDM links for providing synchronization

reference for base stations– No need for expensive GPS based synchronization sources at base

station sites


BTS

BTS


• Timing over Packet solution is based on the use of IEEE 1588 v2 protocol• Master Clock at the RNC site

– The Master Clock has a timing reference traceable to Primary Reference Clock (PRC)• Every base station has a Slave Clock• The Master and Slave Clocks communicate by using IEEE 1588 v2 protocol

– Unicast is used as the communication mode.• The Master Clock sends Sync messages to the Slave Clocks• The Slave Clocks recovers the synchronization reference by using the Sync

messages received from the Master Clock

S

SM Master Clock

S Slave Clock

Timingserver

PRC

RNCPSN

M


IEEE 1588 v2 in RU10 ToP solution

• Only a subset of IEEE 1588 v2 features and functions is supported

• Support of unicast option of IEEE 1588 v2 is essential part of the solution

– Unicast discovery (pre-configuration of slave clocks with the address of the master clock) and unicast negotiation are supported

• Sync messages and signaling messages are supported– Sync messages are time stamped event messages– Signaling messages are used for unicast negotiation

▪ signaling messages are not time stamped


Unicast messaging between the Master and Slave ClocksAll slaves are preconfigured with the address of the master.

Signaling messageREQUEST_UNICAST_TRANSMISSION TLVmessageType: Sync, logInterMessagePeriod: 1/16 s, durationField: 300 s

GRANT_UNICAST_TRANSMISSION TLVmessageType: Sync, logInterMessagePeriod: 1/16 s, durationField: 300 s, R flag (Renewal Invited): TRUE

Master Slave

Sync messages (16 packets per second for 300 s)

RequestGrantSync messages

RequestGrant



• The Master Clock is implemented as a dedicated network element at the RNC site

– RNC site: Requires external timing server for the master clock functionality

• Slave Clocks are integrated in Ethernet interface units of base stations

– Flexi BTS requires Transport module FTIB, containing additional hardware supporting Timing over Packet

– Ultrasite BTS requires IFUH interface unit, with an additional Timing over Packet plug-on unit called TOPA


Activation and operation

• This feature is controlled by a long-term ON/OFF license– License key in Flexi WCDMA BTS and AXC is required

• Configuration of Slave Clocks– unicast_master_table (the address of the Master Clock)– desired Sync message rate

• How to verify/monitor?– Out of lock indication of the slave clock

• This feature is needed for– RAN74: IP based Iub for Flexi WCDMA BTS, in case external

synchronization signal is not available– RAS06 Hybrid BTS Backhaul in Full Pseudo-Wire Emulation (Full

PWE) mode, in case external synchronization signal is not available



RAN1253 Iub Transport QoSFeature Introduction


Overview

• Traffic differentiation capabilities are enhanced with ATM Iub and IP Iub

– With ATM Iub AAL2 priorities are implemented in the downlink direction

– In the case of FlexiWCDMA BTS, for the uplink direction as well– In case of ATM Iub also the VCC differentiation possibilities for HSPA

transmission is extended– With IP Iub, IP layer priorities are supported in the scheduling

• RAB priorities between and within traffic classes and the guaranteed bit rate requirement are taken into account at ATM and IP transport resource reservations on Iub


Functionality - ATM Iub

• AAL2 layer traffic separation is extended with four AAL2 priorities per VCC– HSPA traffic can be mapped into the four AAL2 queues in downlink direction

based on the Scheduling Priority Indicator (SPI)– SPI is derived from the RAB QoS parameters and used for the service

differentiation in the radio interface as well– Mapping between SPI and AAL2 priority queues is operator configurable

• With Flexi WCDMA BTS four uplink AAL2 priority queues are supported. – The priority information for the AAL2 level differentiation in uplink is conveyed

from the RNC to the BTS via ALCAP signaling• This feature can be used together with path selection, which supports

traffic differentiation into ATM VCs• VCC separation to RT DCH, NRT DCH and HSPA VCCs is extended

by further separating HSPA traffic into up to three VCC types: HSPA Stringent, HSPA Stringent-bi-level and HSPA Tolerant

• ATM VCCs provide the differentiated treatment with CBR and UBR+ services

• With hybrid BTS backhaul, AAL2 priorities in the ATM Iub are carried within the VCCs, which are then emulated over the packet network.


Functionality - IP Iub

• This feature introduces additional IP Layer PHB queuing / scheduling, with maximum 6 differentiated PHB queues

• The queue corresponding to the PHB is selected based on the DSCP given for the transport bearer of the RAB

• DSCP is further based on the SPI of the RAB• Mapping between SPIs, DSCPs and PHB queues is operator

configurable.


Functional descriptionRAN1253 Iub Transport QoS mapping scheme

HS-DSCH

Conversational ARP1-3Streaming

InteractiveTHP1

InteractiveTHP2

InteractiveTHP3

Background

ARP1-3

ARP1-3

ARP1-3

ARP1-3

ARP1-3

Conversational ARP1-3Streaming

InteractiveTHP1

InteractiveTHP2

InteractiveTHP3

Background

ARP1-3

ARP1-3

ARP1-3

ARP1-3

ARP1-3

E-DCH

R99 DCH PS domain

PCH, FACH, RACH

QoSPri15

QoSPri14

QoSPri13

QoSPri12

QoSPri11

QoSPri10

QoSPri9

QoSPri8

QoSPri7

QoSPri6

QoSPri5

QoSPri4

QoSPri3

QoSPri2

QoSPri1

QoSPri0

AAL2.Q1

Common channels

DSCP

DSCP

DSCP

DSCP

DSCP

DSCP

6 Default PHBscorresponding to the IP egress scheduling queues

IP transport

EF

AF4

AF3

AF2

AF1

BE

DSCP

AAL2.Q2

AAL2.Q3

AAL2.Q4


AAL2PT Stringent

AAL2PT Str-bi-level

AAL2PT Tolerant

Radio Network layer Transport Network layer

- ALCAP ERQ: Standard AAL2 PT- AAL2 VCC selection

- AAL2 queue selection

If Ethernet VLAN in use:- VLAN tag / user priority (0-7)

ATM transport

R99 DCH CSDomain

CS AMR SpeechCS-T dataCS-NT data

SRB

ARP - Allocation/Retention Priority affects to power division between NRT DCH and NRT HSPAScheduling Priority Indicator (SPI) is derived from the RAB QoS parameters



• RNC and BTS (Flexi BTS) implement the AAL2 scheduling with four queues and with configurable scheduling weights

• The BTS and RNC support the ATM VCC level traffic differentiation (Flexi BTS, Ultra Site BTS (AXU-B, AXU Compact))

• The NBAP signaling is used to deliver the selected AAL2 priority or DSCP to the BTS for UL traffic prioritization

• RNC RNW object model contains a new TQM object where the transport bearer priority is retrieved at call setup based on the air interface channel type and packet scheduling prioritization

– TQM object provides one central place for adjusting the transport layer priorities under the RNC.

• NetAct offers an interface to activate and deactivate the feature and handle other parameters related to this feature



• This feature is controlled by RNC level long-term capacity license. Measure for capacity is the number of BTSs.

• Radio network layer packet scheduling– PS scheduling prioritization configuration at RNC is done according to

RAN1262 QoS Aware HSPA Scheduling and RAN1004 Streaming QoS for HSPA

• Iub configuration BTS– AAL2 VCC configuration

• Iub configuration RNC– AAL2 VCC configuration for controlling the VCC level traffic separation

▪ AAL2UPUsage and the allowed AAL2 Path types configured for each AAL2 VCC• RNW logical configuration at RNC

– Transport bearer prioritization scheme configured to TQM object– TQM object needs to be assigned to the planned WBTS objects to enable the

QoS mapping for the BTS. One TQM QoS mapping profile can be utilized for one, several or all BTSs within the RNC. Several TQM objects can be created to enable different prioritization schemes under the RNC.



• Verification and monitoring– The AAL2 layer performance can be followed with the AAL2 layer

counters▪ ”AAL2 layer scheduling performance measurement in RNC” M553▪ ”AAL2 layer scheduling performance measurement in BTS" M5004

– The IP layer performance can be followed with the IP layer counters

• Feature deactivation– The TQM object relation is removed from the WBTS in the RNC RNW

configuration▪ ATM transport

• The system prioritizes the traffic with system defaults. ▪ IP Transport

• The RT/NRT traffic differentiation is provided with IP transport features basic DSCP configuration.


AAL2 User plane Usage

Following explains RAS06 Path selection AAL2 VCC combinations inRU10 “format”

TolerantHSUPAHSUPATolerantHSPAHSPA

TolerantHSDPAHSDPA

Stringent, Stringent bi-level, Tolerant

DCH + HSDPASharedStringent bi-levelDCHNRT DCHStringentDCHRT DCH Stringent, Stringent bi-levelDCHDCH

AAL2PT combinations (RU10/RN4.0)

AAL2UPUsage (RU10 / RN4.0)

RAS06 AAL2UPUsage



VCCs for RT/NRT DCH + RT HSPA:• ATM Service Category: CBR• AAL2UPUsage: DCH + HSPA• AAL2 PTs: Stringent + Stringent bi-level

VCCs for NRT HSPA (high peak rate):• ATM Service Category: UBR+• AAL2UPUsage: HSPA• AAL2 PTs: Tolerant

BTSAAL2 VCCs, example 1

Basic RT/NRT HSPA ATM layer differentiation (Flexi BTS, Ultra Site BTS)



VCCs for RT/NRT DCH:• ATM Service Category: CBR• AAL2UPUsage: DCH• AAL2 PTs: Stringent + Stringent bi-level

VCCs for RT/NRT HSPA:• ATM Service Category: UBR+• AAL2UPUsage: HSPA• AAL2 PTs: Stringent + Stringent bi-level + Tolerant


Basic DCH / HSPA separation



VCCs for RT DCH:• ATM Service Category: CBR• AAL2UPUsage: DCH • AAL2 PTs: Stringent

VCCs for DCH NRT + RT HSPA:• ATM Service Category: UBR+• AAL2UPUsage: DCH + HSPA• AAL2 PTs: Stringent bi-level

VCCs for NRT HSPA (high peak rate):• ATM Service Category: UBR+• AAL2UPUsage: HSPA• AAL2 PTs: Tolerant


Stringent, Stringent bi-level and Tolerant VCCs


Activation and operation: DCH+HSPA VCC: UTRAN RAB Characteristics mapping to AAL2 Path type and AAL2 queue

QoS Pri 3

QoS Pri 4

QoS Pri 7

QoS Pri 8

QoS Pri 9

QoS Pri 10

QoS Pri 11

QoS Pri 14

QoS Pri 15

QoS Pri 6

QoS Pri 12

QoS Pri 13

QoS Pri 5

QoS Pri 2

QoS Pri 0

QoS Pri 1

RRM QoS Pri

Stringent Q2

Stringent Q1

Stringent bi-level Q3


R99 DCH AAL2 Path Type / AAL2 queue

Interactive THP3 ARP3

Background ARP1

Background ARP2






Streaming ARP3

Streaming ARP2

Conversational ARP2

Conversational ARP1


Streaming ARP1

Conversational ARP3



Background ARP3

UMTS TC, THP, ARP

2

1

4

3

DCH+HSPA Stringent, Stringent bi-level, Tolerant

Radio Resource Management

Stringent Q2

Stringent Q1



Tolerant Q4

Tolerant Q3

HSPA AAL2 Path Type / AAL2 queue

VCC configurationOne shared VCC,four queues

TQOS mapping

Only part of the mapping values represented (all queue values possible)

Operator can freely choose the mapping to queues towards the VCC


Activation and operation: DCH+HSPA VCCs: UTRAN RAB Characteristics mapping to AAL2 Path type and AAL2 queue

Stringent Q2

Stringent Q1



Tolerant Q4

Tolerant Q3



Background ARP1

Background ARP2






Streaming ARP3

Streaming ARP2

Conversational ARP2

Conversational ARP1


Streaming ARP1

Conversational ARP3



Background ARP3

UMTS TC, THP, ARP

2

1

4

3

Stringent, Stringent bi-level VCC


Stringent Q2

Stringent Q1



Tolerant Q4

Tolerant Q3


VCC configurationOne VCC for Stringent and Stringent bi-level priorities (RT/NRT DCH + RT HSPA)

TQOS mapping


4

1 / 2 / 3

Tolerant VCC(high peak rate

QoS Pri 3

QoS Pri 4

QoS Pri 7

QoS Pri 8

QoS Pri 9

QoS Pri 10

QoS Pri 11

QoS Pri 14

QoS Pri 15

QoS Pri 6

QoS Pri 12

QoS Pri 13

QoS Pri 5

QoS Pri 2

QoS Pri 0

QoS Pri 1

RRM QoS Pri

One VCC for Tolerant (NRT HSPA traffic)


Activation and operation: DCH+HSPA VCCs: UTRAN RAB Characteristics mapping to AAL2 Path type and AAL2 queue

Stringent Q2

Stringent Q1



Tolerant Q4

Tolerant Q3



Background ARP1

Background ARP2






Streaming ARP3

Streaming ARP2

Conversational ARP2

Conversational ARP1


Streaming ARP1

Conversational ARP3



Background ARP3

UMTS TC, THP, ARP

2 / 3 / 4

1

Stringent VCC


Stringent Q2

Stringent Q1



Tolerant Q4

Tolerant Q3


VCC configurationThree VCCs, transport priority and VCC defined in the Call setup (using AAL2 path type and AAL2 queue)

TQOS mapping


4

1 / 2 / 3

Tolerant VCC

3 / 4

1 / 2

Stringent bi-level VCC

QoS Pri 3

QoS Pri 4

QoS Pri 7

QoS Pri 8

QoS Pri 9

QoS Pri 10

QoS Pri 11

QoS Pri 14

QoS Pri 15

QoS Pri 6

QoS Pri 12

QoS Pri 13

QoS Pri 5

QoS Pri 2

QoS Pri 0

QoS Pri 1

RRM QoS Pri


Limitations and Interdependencies between features• Limited to AXUB and AXC Compact (cannot be used for AXUA)• RAN1262 QoS Aware HSPA Scheduling

– Configurable Transport Layer QoS differentiation based on the packet scheduling prioritization

• RAN1004 Streaming QoS for HSPA – Configurable Transport Layer QoS differentiation based on the packet

scheduling prioritization• RAN754 Path Selection

– Path selection license is mandatory for RAN1253 Iub Transport QoS– Path selection contains the basic AAL2 VCC level traffic differentiation. The

AAL2 VCC differentiation mechanism is enhanced with Iub Transport QoS feature

• RAN74 IP Iub– Enhanced DSCP mapping for Transport Layer QoS differentiation

• RAN1449 Dual Iub– Enhanced DSCP mapping for Transport Layer QoS differentiation


Management data, RNC RNW Object model

RNC

WBTS

WCEL COCO(ATM)

TQM(ATM/IP)

Iub/Iur ATM/IP transport

1n

1n

1

0-1

1

n

IPQM(IP)

Iu-CS

Iu-PS

Iur

Iu-CS, Iu-PS IP transport

0-1n

n

n

0-1

TQM Object introduced as a new object type containing Iub Transport QoS mapping Information (IP + ATM mapping)

IPNBC-NBAPD-NBAP (+SCTP)

(IP)

0-1

New RN4.0, IP Based Iub New RN4.0

1



1262: QoS Aware HSPA SchedulingFeature Introduction


Introduction

• This feature allows service and subscriber differentiation and supports different tariffing plans for NRT traffic classes, e.g. premium services and subscribers will have higher priority over low tariff broadband HSPA data traffic.

• Prioritization is defined in RNC level by mapping Traffic Class (TC), Traffic Handling Priority (THP) and Allocation/Retention Priority (ARP) combinations received from RANAP to priority value (0…11)

– New prioritization is used always with DCH transport channels (TC+THP+ARP based prioritization for DCHs is generic functionality)

– New prioritization is used in case of HSPA transport channels just if this new feature is activated in cell in question

• Priorities are used in RNC (DCH) and in BTS (HSPA) in scheduling


Priorities for Interactive and Background Traffic • Operator is able to define priority for each

Radio Access Bearer (RAB) specific Traffic Class, Traffic Handling Priority and Allocation/Retention Priority combination(only interactive and background TCs can be used with this feature)

• Prioritization of real time RABs is not changed, they have still the highest priority

• Priority is used inside RNC to prioritize use of resources used by Radio Bearers

• In case of HSPA transport channels priority is also sent to the BTS as Scheduling Priority Indication (SPI) value that is used by the scheduler in BTS Y12

Y11Y10Y9Y8Y7Y6Y5Y4Y3Y2Y1

Priority (0…11)

Background ARP3Background ARP2Background ARP1

Interactive THP3 ARP3Interactive THP3 ARP2Interactive THP3 ARP1Interactive THP2 ARP3Interactive THP2 ARP2Interactive THP2 ARP1Interactive THP1 ARP3Interactive THP1 ARP2Interactive THP1 ARP1

TC+THP+ARP

• New prioritization is used to prioritize capacity requests in capacity request queuein RNC packet scheduler

• Replaces old prioritization defined by management parameters CrHandlingPolicyUL and CrHandlingPolicyDL


Prioritization for DCH• Operator defined prioritization is used always to prioritize resources

used by PS NRT RABs mapped to DCH transport channels• DCH part of this feature is generic functionality

• Prioritization is used in the following cases:1. Overload control, Enhanced overload control

– Replaces use of management parameters CrHandlingPolicyUL/DL

2. Priority based scheduling– Replaces the fixed order used by the system

3. RT-over-NRT functionality– Replaces the fixed order used by the system

• The operator has also possibility to define Allocation/Retention Priority (ARP) specific weights that affects to power division between NRT DCH and NRT HSPA

• Affects to system variables PtxTargetPS and PrxTargetPS that areused when feature HSDPA dynamic resource allocation is in use


Prioritization for HSPA used for Scheduling in BTS

• Operator defined prioritization is used in the cell for the HSPA if QoS prioritization is activated to the cell with the management parameter HSPAQoSEnabled

• If the feature is not activated, then the lowest priority (SPI=0) is used for all TC+THP+ARP combinations for RBs mapped to HSPA transportchannels

• In case of HSPA priority defined with the RNP parameter QoSPriorityMapping is also used as SPI value

• SPI value is sent to the BTS, where it is used in scheduling• SPI value is also given to the user plane where it is used in HSUPA

congestion control• HSUPA Iub congestion control do congestion control in priority order

based on SPI, that is, in average the lower priority NRT bearers suffers more probably congestion than higher priority NRT bearers


HSUPA and HSDPA Packet Scheduling

• HSUPA and HSDPA packet schedulers in the BTS take Scheduling Priority Indicator (SPI) into account.

• HSUPA and HSDPA packet schedulers weight different priority queues based on their SPI values. Additionally, there is a operator controllable weight value per SPI value in the BTS, which sets the magnitude how often queues of different SPI classes get scheduled in relation to other SPI classes.

• Proportional Fair Required Activity Detection with Delay Sensitivity (PF-RAD-DS) scheduler is used for HSDPA.

• In addition to SPI and weight parameters, also the radio conditions, UE capabilities and the data amount in the users buffers affect to the scheduling decision.

• With RAN1004 (Streaming QoS with HSPA) the Guaranteed Bit Rate and Discard Timer are included in the scheduling decision.



• The feature is controlled with the long-term capacity license that specifies in how many BTSs this feature can be used

• RNC sets the used priority• BTS schedules HSPA traffic according priority set in RNC• NetAct offers an interface to activate and deactivate the

feature and handle other parameters related to this feature• BTS Site Manager offers an interface to control the

scheduling weight parameters in BTS.


Interdependencies Between Features

• Optional part of this feature requires feature RAN312 HSDPA Dynamic Resource Allocation

• Optional part of this feature can be used with or without HSUPA

• This feature forms a base for feature RAN1004 Streaming QoS for HSPA(streaming feature can not be used without this scheduling feature)

• HSUPA Congestion Control (RAN992) can be configured per SPI class



RAN1004: Streaming QoS for HSPAFeature Introduction


Overview

• This feature enables Guaranteed bit rate (GBR) for streaming traffic class in HSPA

• Admission of a new user can be denied if the guaranteed bit rate cannot be provided to the user, or if the guaranteed QoS of existing users would be affected

– However, a new streaming user can take resources from HSPA NRT or from DCH NRT users (RT-over-NRT).

• The guaranteed bit rate is taken into account in the BTS scheduler– On HS-DSCH the PF-RAD-DS scheduler first fulfills the GBR requirements of

real time users in the order of SPI• Uplink direction of streaming class RAB using GBR and mapped to E-

DCH is not congestion controlled in Iub, i.e. HSUPA Congestion Control feature is not applied to NRT users on E-DCH

• Operator can also select whether the downlink streaming class bearers are HSDPA Congestion Controlled or not on the Iub

• This feature makes it also possible to have Nominal Bit Rate (NBR) for NRT traffic classes


Prioritization 1/2

• Operator is able to define priority for each Radio Access Bearer specific Traffic Class, Traffic Handling Priority and Allocation/Retention Priority combination(combinations for streaming are added)

• Priority is used inside RNC to prioritize use of resources used by Radio Bearers

– For example for overload control or for RT-over-NRT

• In case of HSPA transport channels priority is also sent to the BTS as Scheduling Priority Indication (SPI) value that is used by the scheduler in BTS

X1Streaming ARP1X2Streaming ARP2X3Streaming ARP3Y0Interactive signaling

Y12Y11Y10Y9Y8Y7Y6Y5Y4Y3Y2Y1

Priority (0…15)

Background ARP3Background ARP2Background ARP1

Interactive THP3 ARP3Interactive THP3 ARP2Interactive THP3 ARP1Interactive THP2 ARP3Interactive THP2 ARP2Interactive THP2 ARP1Interactive THP1 ARP3Interactive THP1 ARP2Interactive THP1 ARP1

TC+THP+ARP


Prioritization 2/2

• PS RAB with Signaling Indication IE is prioritized with own priority (Y0)• Rules for setting the priorities

– Streaming traffic class has always higher priority values than NRT classes– Interactive signaling has always higher priority than other NRT classes– SPI values with Nominal Bit Rate (NBR) set for uplink or downlink must

form continuous block of SPI values starting from the highest priority value used for NRT traffic classes▪ See separate slides for Nominal Bit Rates

– Otherwise priorities can be used freely• Priority is used always with DCH transport channels and also with HS

transport channels if HSPA streaming is activated cell in question (HS-DSCH serving cell) with the RNP parameter HSPAQoSEnabled


Prioritization, recommended mappings

Background ARP3Background ARP3Background ARP1-30

Not usedNot usedNot usedNot usedInteractive THP3 ARP1-3Not usedNot usedInteractive THP2 ARP1-3Not usedNot used

Interactive THP1 ARP1-3Interactive signalingStreaming ARP1-3Not usedNot used

Default

Interactive THP3 ARP3Background ARP21

Interactive THP1 ARP1Interactive THP1 ARP111

Streaming ARP1Streaming ARP115

Interactive THP2 ARP3Interactive THP1 APR3Background ARP2Interactive THP3 ARP2Interactive THP2 ARP2Interactive THP1 ARP2Background ARP1Interactive THP3 ARP1Interactive THP2 ARP1

Interactive signalingStreaming ARP3Streaming ARP2

ARP based

Background ARP1Interactive THP3 APR3Interactive THP3 ARP2Interactive THP3 ARP1Interactive THP2 APR3Interactive THP2 ARP2Interactive THP2 ARP1Interactive THP1 APR3Interactive THP1 ARP2

Interactive signalingStreaming ARP3Streaming ARP2

TC based

2345678910

121314

Priority


Supported Transport Channel Combinations for PS Services• All PS RABs of one UE are mapped just one of the following transport

channel combinations:– UL DCH and DL DCH– UL DCH and DL HS-DSCH– UL E-DCH and DL HS-DSCH

• However one or more RABs of one UE can always be mapped also to DCH 0/0 (Radio Bearer without resources, released Radio Bearer)

• Any other combinations are not allowed• Not succeed establishment of new PS RB or resource reservation for

PS RB mapped to DCH 0/0 does not trigger channel type switch between DCH and HS transport channels, but RAB is rejected or RBstays in DCH 0/0

– Only exception is situation where used transport channel type can not be used because of used configuration▪ For example if HSPA streaming is not activated, then establishment of

streaming can cause DCH switch for the existing NRT services


Nominal Bit Rate (NBR) 1/2

• Nominal Bit Rate (NBR) is bit rate that can be configured in RNC level for each SPI value used for Interactive or Background traffic classes separately for uplink and downlink

– Structured RNP parameter HSPANBRValues• Nominal Bit Rate is only used in case of E-DCH and HS-DSCH transport

channels• Nominal Bit Rate is used same way as Guaranteed Bit Rate (GBR) for

scheduling– In principle scheduler does not know is received GBR NBR or real GBR– Only difference is that RBs with NBR has always lower SPI value– NBR (and GBR) is always tried to be offered for the user and this does not

depend on used SPI valueSPIs with NBR has higher priority than SPIs without NBR and for this reason

SPIs without NBR must have lower SPI values than SPIs with NBR


Nominal Bit Rate (NBR) 2/2

N12M120

N0M012

N11N10N9N8N7N6N5N4N3N2N1

DL NBR

M11M10M9M8M7M6M5M4M3M2M1

UL NBR

123456789

1011

SPI

In BTS there are SPI specific weights to divide extra capacity after MAC-d flows with GBR and NBR are scheduled

Value 0 is used as default value for all NBRs


DL RB, Transport, Physical Channel and RLC Configuration• HSPA streaming brings the following changes to parameterization:

– MAC-d flow id (each PS RAB has its own MAC-d flow)– Scheduling Priority Indication (SPI) is taken into use to differentiate priorities– GBR is taken into use

▪ In case of streaming RAB value is received from RANAP▪ In case of NRT RAB value can be set in RNC (NBR)

– MAC-d PDU size (just size 336 is used in case of streaming RB)– Discard Timer (DT) is taken into use for streaming

▪ Value is got by multiplying value of the Transfer Delay IE (from RANAP) with the RNP parameter TDMultForHSDPAStreaming

• RLC mode AM is used for streaming• There are own RLC retransmission parameters for streaming

– Defined with the structured RNP parameter AMRLCOnHSDSCHOfStrPS


Functional description, Iub Transport

• This feature brings basic RT/NRT differentiation to Iub transport• Iub transport differentiates streaming class traffic from Interactive and

Background class bearers.• More control over the Iub Transport (both ATM/IP Transport and their

CAC) QoS differentiation is provided with RAN1253 Iub Transport Qosfeature.



• The affected NEs are BTS, RNC and NetAct• RNC does admission and resource allocation • RNC sets the used priority and signals it to BTS with DL GBR• RNC schedules HSUPA RT traffic according UL GBR and

signals the scheduled bit rate to UE and BTS• BTS schedules HSDPA RT traffic according priority and DL

GBR• NetAct offers an interface to activate and deactivate the

feature and handle other parameters related to this feature• BTS Site Manager offers an interface to control the

scheduling weight parameters in BTS.



• This feature is controlled by RNC level long-term capacity license. Measure for capacity is the number of BTSs. License condition is checked only when the feature is activated to the cell.

• If license allows, operator can use the RNP parameter HSPAQoSEnabled to activate and deactivate HSPA with Streaming Support feature. This is done in cell level.

• If the HSPA with Streaming QoS Support feature is not activated to the cell, then RABs with streaming traffic class isnot mapped to HS transport channel (DCH is used).

• Priorities used by PS services are defined with the RNP parameter QoSPriorityMapping

– These priorities are also used for HSPA, if HSPA QoS features are activated

– SPI specific scheduling weights in BTS must be checked and updated according of selected mapping


Interdependencies between features 1/2

• RAN1262 QoS Aware HSPA Scheduling and RAN312 HSDPA Dynamic Resource Allocation features are needed for this feature.

• This feature can be used with or without HSUPA.• RAN750 IP Based Iu-PS brings traffic class (TC) and traffic

handling priority (THP) based mapping to DSCP (differentiated services). This feature can be used to bring RT/NRT differentiation to Iu-PS.

• Alternatively RAN717 Iu-PS IP Quality of Service Support feature brings RT/NRT differentiation in Iu-PS interface.

• RAN1253 Iub transport Qos feature introduces the Transport Network Layer (TNL) QoS differentiation based on the Radio Network Layer (RNL) traffic prioritization strategy.


Interdependencies between features 2/2

• RAN1276 HSDPA Inter-frequency Handover introduces compressed mode when HS-DSCH is mapped to the streaming RB.

• RAN285 HSPA Multi NRT RAB makes it possible to have 3 simultaneous PS NRT RBs mapped to HS-DSCH when also PS streaming RB mapped to HS-DSCH exists.

10 Rn30038en06gln0 Ru10 Overview

Documents

Transcript of 10 Rn30038en06gln0 Ru10 Overview