Professional Documents
Culture Documents
Umt Irc App 007149 Iub Teg Ua6 External STD Ed7-2 STD 090629
Umt Irc App 007149 Iub Teg Ua6 External STD Ed7-2 STD 090629
Umt Irc App 007149 Iub Teg Ua6 External STD Ed7-2 STD 090629
Document number:
Document issue:
Document status:
Date:
Author:
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Philippe DELMAS
External document
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write protected; it
may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master
electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.
Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein
confidential, shall disclose the information only to its employees with a need to know, and shall protect the information
from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the
holder is granted no rights to use the information contained herein. If you have received this document in error, please
notify the sender and destroy it immediately..
PUBLICATION HISTORY
External
Edition
UMTS
Release:
Date
7-2
UA6
29/06/09
26/01/09
7-1
ReasonsForChange
3.6.2.1.3: add the qos mapping table for the 16pOC3 PQC FP
3.8.7.2+5.5.1.3: Modification: sharedForTrafficType qos3 vcc
HP=0 to HP=1.
Standard
3.6.2.2.3: upd, 16pOC3 MS3 FP ECMP.
3.6.10.5.1: upd, asym traffic with 1 bwPool.
02/12/08
26/08/08
- Preliminary Edition.
- CM: qosDiscardThreshold formula update,
26/06/08
25/09/07
6-1
06/09/07
6-0
18/07/07
7-0
6-2
5-1
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 3/263
5-0
5-0
10/07/07
22/01/07
10/01/07
42-2
4-2
42-1
4.1
4-0
10/11/06
01/11/06
FRS29840: Hsupa
FRS30782: 16pOC3 MS3 FP
FRS27083: Rnc aal2Cac enhancement,
FRSxxxxx: Introduction of the atm micro NodeB,
FRS27943: NodeB IMA HoldingPriority,
FRS32602: FallBack to DCH, if hsdpa CAC rejection
29/05/06
05/01/05
26/11/04
01/08/04
&
3
4.0
4-0
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 4/263
&
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 5/263
CONTENTS
1
INTRODUCTION............................................................................................................................9
OBJECT ....................................................................................................................................9
SCOPE OF THIS DOCUMENT .......................................................................................................9
AUDIENCE FOR THIS DOCUMENT ................................................................................................9
2
RELATED DOCUMENTS ............................................................................................................10
3
IUB TRANSPORT NETWORK LAYER, DESCRIPTION ............................................................12
3.1
TRANSMISSION .......................................................................................................................13
3.1.1
PDH:..............................................................................................................................13
3.1.2
SDH/SONET: ................................................................................................................17
3.2
ATM ......................................................................................................................................24
3.2.1
ATM interface Type .......................................................................................................24
3.2.2
VPC, VPT ......................................................................................................................25
3.2.3
OverSubscription...........................................................................................................31
3.2.4
CAC...............................................................................................................................31
3.2.5
Traffic Management ......................................................................................................33
3.2.6
QOS ..............................................................................................................................38
3.2.7
Fractional E1/T1 ............................................................................................................47
3.2.8
Addressing ....................................................................................................................52
3.2.9
PNNI..............................................................................................................................52
3.2.10
IMA ...............................................................................................................................56
3.2.11 ATM OAM......................................................................................................................61
3.3
AAL2.....................................................................................................................................69
3.3.1
Addressing ....................................................................................................................69
3.3.2
Alcap .............................................................................................................................69
3.4
IP ..........................................................................................................................................71
3.4.1
InverseARP ...................................................................................................................71
3.4.2
SiteLAN .........................................................................................................................73
3.5
IUB TOPOLOGY .......................................................................................................................73
3.5.1
ATM Backbone:.............................................................................................................75
3.5.2
Atm ring on Iub ..............................................................................................................75
3.5.3
SDH ring........................................................................................................................76
3.5.4
Hybrid UTRAN...............................................................................................................77
3.5.5
Ethernet topology ..........................................................................................................78
3.6
RNC ATM .............................................................................................................................79
3.6.1
ASIC ..............................................................................................................................79
3.6.2
FP..................................................................................................................................80
3.6.3
RNC capacity ..............................................................................................................105
3.6.4
Aal2 Components:.......................................................................................................106
3.6.5
Aal2 Paths ...................................................................................................................113
3.6.6
Aal2 QOS ....................................................................................................................114
3.6.7
aal5 connections .........................................................................................................114
3.6.8
QOS ............................................................................................................................115
3.6.9
TransportMap ..............................................................................................................117
3.6.10 Transport admission Control .......................................................................................124
3.6.11 Congestion Management bandwidth Limitation a.k.a rate Control .............................137
3.6.13 NodeB discrimination ..................................................................................................143
3.6.14 Alcap ...........................................................................................................................144
3.6.15 Utran Sharing ..............................................................................................................147
3.6.16 PNNI Hairpin removal .................................................................................................149
3.7
RNC HYBRID........................................................................................................................150
3.7.1
FP................................................................................................................................150
3.7.2
RNC capacity ..............................................................................................................156
3.7.3
IP Components............................................................................................................157
3.7.4
Virtual Router RNC composition .................................................................................163
3.7.5
LocalMedia ..................................................................................................................165
1.1
1.2
1.3
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 6/263
3.7.6
PDR.............................................................................................................................168
3.7.7
ICMP HeartBeat ..........................................................................................................172
3.7.8
QOS ............................................................................................................................174
3.7.9
TransportMap ..............................................................................................................176
3.7.10 Transport admission Control .......................................................................................179
3.7.11 CongestionManagement bandwidth Limitation a.k.a rate Control ..............................183
3.7.12 Routing: .......................................................................................................................190
3.7.13 NodeB discrimination ..................................................................................................190
3.7.14 Utran Sharing ..............................................................................................................191
3.8
NODE B (IBTS).....................................................................................................................191
3.8.1
Cards...........................................................................................................................191
3.8.2
PDH Layer:..................................................................................................................193
3.8.3
Ethernet Layer:............................................................................................................194
3.8.4
Synchronisation...........................................................................................................194
3.8.5
ATM Connections:.......................................................................................................194
3.8.6
MultiPCM.....................................................................................................................195
3.8.7
IMA ..............................................................................................................................196
3.8.8
Mix of N * E1 xPCM and p E1 IMA..............................................................................198
3.8.9
IP .................................................................................................................................199
3.8.10 QOS ............................................................................................................................200
3.8.11 Traffic Management ....................................................................................................202
3.8.12 Hspa CAC ...................................................................................................................204
3.8.13 Alcap ...........................................................................................................................204
3.9
NODEB (ONEBTS)................................................................................................................205
3.9.1
Alcap ...........................................................................................................................205
3.10
MICRO NODEB ATM (BTS 1120) ...........................................................................................205
3.10.1 Transmission: ..............................................................................................................205
3.10.2 Atm: .............................................................................................................................206
3.10.3 Aal2 .............................................................................................................................208
3.10.4 SAAL: ..........................................................................................................................208
3.10.5 IP: ................................................................................................................................209
3.10.6 UMTS traffic flows: ......................................................................................................210
3.11
PICO NODEB ATM (BTS 1010) ...............................................................................................211
3.11.1 Transmission: ..............................................................................................................211
3.11.2 Atm: .............................................................................................................................211
3.11.3 Aal2: ............................................................................................................................212
3.11.4 IP: ................................................................................................................................212
3.11.5 UMTS traffic flows: ......................................................................................................213
3.12
7670....................................................................................................................................213
3.13
UMTS PLANE DESCRIPTION ..................................................................................................214
3.13.1 HSUPA Plane..............................................................................................................214
3.13.2 HSDPA Plane..............................................................................................................216
3.13.3 OAM Plane ..................................................................................................................218
3.13.4 Control Plane...............................................................................................................225
3.13.5 User plane ...................................................................................................................226
3.13.6 ATM Backbone Requirements ....................................................................................227
4
UMTS RELEASES.....................................................................................................................228
4.1
RNC....................................................................................................................................228
4.1.1
FP................................................................................................................................228
4.1.2
RNC Types:.................................................................................................................230
4.1.3
RNC capacity: .............................................................................................................230
4.1.4
Iuxif / IubIf / aal2If:.......................................................................................................230
4.1.5
Pathid: .........................................................................................................................230
4.1.6
Aal2 Path assignment to PMC-PC ..............................................................................231
4.1.7
AAL2 Link CAC: ..........................................................................................................231
4.1.8
aal2CongestionManagement ......................................................................................232
4.1.9
Icn VCC .......................................................................................................................232
4.1.10 TMU.............................................................................................................................232
4.1.11 QOS ............................................................................................................................233
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 7/263
4.2
NODEB ................................................................................................................................233
4.2.1
CCM related: ...............................................................................................................233
4.2.2
CEM related: ...............................................................................................................233
4.2.3
MultiPCM:....................................................................................................................233
4.2.4
IMA: .............................................................................................................................234
4.2.5
n E1 xPCM + p E1 IMA: ..............................................................................................235
4.2.6
AAL1 CES ...................................................................................................................235
4.2.7
QOS ............................................................................................................................235
4.2.8
Traffic Management ....................................................................................................236
4.3
MICRO NODEB .....................................................................................................................237
4.4
PICO NODEB ........................................................................................................................237
4.5
PLANE RELATIVE ...................................................................................................................237
4.5.1
UMTS HSUPA Plane: .................................................................................................237
4.5.2
UMTS HSDPA Plane: .................................................................................................237
4.5.3
UMTS OAM Plane:......................................................................................................237
4.5.4
UMTS Control Plane: ..................................................................................................238
4.5.5
UMTS User Plane .......................................................................................................238
4.5.6
Transport Network ControlPlane:................................................................................238
5
TRANSPORT IDENTIFIERS .....................................................................................................238
5.1
ATM VCC............................................................................................................................240
5.1.1
UpGrade from UA5 to UA6 .........................................................................................240
5.1.2
NodeB interface ..........................................................................................................242
5.1.3
RNC Interface..............................................................................................................244
5.1.4
PNNI............................................................................................................................249
5.2
FP ATTRIBUTES ....................................................................................................................250
5.2.1
16pOC3/Stm1 FP Attributes........................................................................................250
5.2.2
16pOC3/Stm1 MS3 (Atm/Pos) FP ..............................................................................254
5.3
IP ........................................................................................................................................254
5.4
AAL2...................................................................................................................................254
5.4.1
IubIf / aal2If..................................................................................................................254
5.4.2
Pathid: .........................................................................................................................255
5.5
IMA .....................................................................................................................................256
5.5.1
NodeB Holding Priority................................................................................................256
5.5.2
IMA LinkGroup ID:.......................................................................................................258
5.5.3
Traffic descriptor .........................................................................................................258
5.6
TRAFFIC DESCRIPTOR ...........................................................................................................258
5.6.1
Aal2 vcc TD .................................................................................................................259
5.6.2
Aal5 vcc TD .................................................................................................................260
5.7
PARAMETERS .......................................................................................................................260
5.7.1
Traffic Descriptor Type................................................................................................260
5.7.2
Parameter Class .........................................................................................................260
6
ABBREVIATIONS......................................................................................................................262
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 8/263
1 INTRODUCTION
1.1
OBJECT
This document intends to describe the Transport layers on the Iub interface.
It also provides:
- Engineering rules inserted in a red square,
- Configuration of UMTS Node Transport interfaces,
- Traffic parameters over Iub interface.
1.2
UA 4-1
Passport Release:
OAM Release:
OAM4.2
UA 5-0
PCR6-1
UA 5-1
PCR7-2
OAM5.0
OAM5.0
PCR8-2
1.3
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 9/263
2 RELATED DOCUMENTS
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 10/263
[
[
[
[[
[[
[
[
[
[
[
[
[
[
[
[
[
[[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
1
2
3
456
798
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
]
]
]
]]
]]
]
]
]
]
]
]
]
]
]
]
]
]]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
UMT/IRC/APP/7149
UMT/IRC/APP/011674
UMT/IRC/APP/12509
Iub TEG
Iu TEG
Iur TEG
Addressing TEG
3GPP TS 25 430
3GPP TS 25 442
3GPP TS 34 108
3GPP TS 25.410
3GPP TS 25. 412
3GPP TS 25. 414
3GPP TS 29.060
3GPP TS 25 420 v3.5.0
3GPP TS 25.422 v3.6.0
3GPP TS 23.236 v5.4.0
3GPP TS 25.425 v3.6.0
3GPP TS 25.309 Rel6
G702
G703
G707
G804
G700 to 706
Q711 to Q 714
G832
G783
G841
G775
I361
I610
I363-1
I363-2
I363-5
I732
I761
I762
Q2210
Q2931
Q2630.1
Q2630.2
E191
X213
Q2941.2
Q1970 and 1990
Q.1950
Q.765.5
Q.2150.1
G711
atmf 0055.000
af-phy-0086.000
af-phy-0086.001
af-phy-0130.00
af-ra-0105.000
af-tm-0121.000
af-vtoa-0078.000
af-cs-0173.000
af-vtoa-0113.000
RFC 1541
RFC 2225
RFC 1629
RFC1293
RFC826
RFC1485
RFC1483
RFC2991
RFC 3331
RFC 3332
RFC 2960
RFC 3309
DHCP
IP & ARP over ATM
Guideline for OSI NSAP allocation in internet
InverseARP
ARP
IP over ATM
IP over AAL5
ECMP
SS7 MTP2 User Adaptation (M2UA) Layer
SS7 MTP3 User Adaptation (M3UA) Layer
SCTP, Stream Control
Transmission Protocol
ALU confidential
SCTP, Stream Control Transmission Protocol
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 11/263
[
[
[[
[
[
[
[
[
[[
[
[
[[
[[
[[
[
[[
[
[
[
[
[
[
[
[
[
[
[
[
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
]
]
]]
]
]
]
]
]
]]
]
]
]]
]
]]
]
]]
]
]
]
]
]
]
]
]
]
]
]
]
GR253
GR2878
241-5701-705
241-5701-706
241-5701-707
241-5701-708
241-5701-702
UMT/IRC/APP/007147
UMT/IRC/APP/7146
PEI NodeB
PEI RNC
UMT/DCL/DD/0020
UPUG
3GPP TS 23.002
3GPP TS 23.221
3GPP TS 23.205
3GPP TS 29.205
3GPP TS 29.232
3GPP 29.414
3GPP 29.415
3GPP 29.232
R4 Network Architecture
Architectural Requirements
BICN; Stage 2
Application of Q.1900 Series to BICN Architecture; Stage 3
MGC, MG Interface, Stage 3, Release 4
CN Nb Data Transport and Transport Signaling
CN Nb interface User Plane Protocols
TFO package
[ R 150 ]
[ R 151 ]
FRS 25647
FRS 33767
aal2LinkCac evolution
Iub over protected atm ring
[ R 160 ]
[ R 161 ]
UMT_SYS_DD_023235
UMT/Sys/DD/023092
UA6_Bandwidth_Pools_FN
Hybrid Iub FN
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 12/263
RNL
OAM
OAM appl
appl
NBAP
NBAP
FP
FP
FP
FP
Q2630.2
Q2630.2
TCP
TCP
TNL
Q2150.2
Q2150.2
IP
IP
SSCF-UNI
SSCF-UNI
LLC/SNAP
LLC/SNAP
SSCOP
SSCOP
UDP
UDP
AAL5
AAL5
AAL2
AAL2
IP
IP
ATM
ATM
OAM
umts CP
Ethernet
Ethernet
Transport CP
UP
UP
(Hspa I/B)
Iub TEG
Figure 3-1, IUB Protocol stack
3.1
TRANSMISSION
3.1.1
PDH:
Different kinds of PDH links are specified either at ITU or at ANSI.
- ITU PDH links:
- E1, 2048 kbit/s,
- E2, 8448 kbit/s, multiplex of 4 E1,
- E3, 34368 kbit/s, multiplex of 4 E2,
- E4, 139264 kbit/s, multiplex of 4 E3, or
- E5, 564992 kbit/s, multiplex of 4 E4.
- ANSI PDH links :
- T1, 1544 kbit/s,
- T2, 6312 kbit/s, multiplex of 4 T1,
- T3, 44736 kbit/s, multiplex of 7 T2,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 13/263
3.1.1.1 T1 LINK:
T1 frame is 193 bits length. The frame repetition rate is 125s.
Therefore the T1 throughput is 1,544 Mb/s = 3622 cellules per second.
The T1 frame is split in:
- 1 bit, first bit of the frame, called F bit, dedicated to synchronisation, it is set to 1 for odd frame,
and to 0 for even frame, followed by
- 24 timeSlots, 64 kb/s throughput each when configured with ATM.
Remarks:
MSA32 FP doesnt manage T1 links.
F
F
F
F
F
F
Header
Header
ATM
cell
Header
53 octets
T1302260-93
Since T1 payload is 192 bits each 125 s, throughput available for ATM is 1,536 Mb/s,
Rule: IubTEG_T1_1
T1 ATM throughput is 1,536 Mb/s = 3622 Cells/s.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 14/263
3.1.1.1.2 CRC:
On T1 is configured as an option CRC.
CRC6 is specified for T1 Signal.
A T1 multiframe is composed of 24 T1 frames.
Within the 24 F bits of a T1 multiframe, 6 bits are reserved for CRC.
3.1.1.2 T3 LINK:
T3 link is resulting from the multiplexing of seven T2 tributaries.
T3 throughput is 44 736 kbits/s = 7 * 6312 kb/s + second stage multiplexing Overhead.
There are two formats for T3, T3 signal may be either Channelized or unchannelized:
- Channelized means that T3 signal results from the two stages multiplexing:
T3 = 7 * T2 and T2 = 4 * T1.
A Channelized T3 is the result of the multiplexing of 28 DS1 links.
A Channelized T3 is composed of 7 * 4 * 24 = 672 timeSlots.
- Unchannelized means that T3 payload is filled with bulk data, either cell direct mapping or PLCP
based.
Only Channelized T3 is defined in this section, since unchannelized are not used in UMTS
network.
Throughput
# Bits
# Timeslot
7 * T2
T3
T3 overhead
44 736 kb/s
552 kb/s
56 bits
7 * 96 = timeSlots
672 timeSlots
2 timeSlots
Note:
T3 is defined as 44 736 kb/s throughput, and 4760 bits multiframe size, therefore 1,174 T3
frames are transmitted each 125 s.
Detail: 44,736*125 = 5592 bits are transmitted; 5592 bits / 4760 bits = 1,174 T3 multiframes
are transmitted.
T3 multiframe is composed of 4760 bits:
- 4704 bits payload,
- 56 bits overhead.
T3 user throughput in cells/s is calculated on following way:
[44 736 kbit/s / (53 * 8)] * 4704 / 4760 = 104 268 cells/s
Rule: IubTEG_T3_1
T3 ATM throughput is 104 268 Cells/s.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 15/263
X1
X2
P1
P2
M1
M2
M3
F1
F1
F1
F1
F1
F1
F1
C11
C21
C31
C41
C51
C61
C71
F2
F2
F2
F2
F2
F2
F2
C12
C22
C32
C42
C52
C62
C72
F3
F3
F3
F3
F3
F3
F3
C13
C23
C33
C43
C53
C63
C73
F4
F4
F4
F4
F4
F4
F4
The P-bits are calculated and may be modified at each section of a facility;
therefore, the P-bits provide SECTION performance information NOT end-to-end
performance information.
Multiframe alignment signal (M1, M2, M3) :
3.1.1.2.1 OAM:
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 16/263
Idle Signal consists in setting information bits are set to a 1100... sequence, starting with a
binary one (1) after each M-bit, F-bit, X-bit, and C-bit. The C-bits are set to binary zero
(C1 = 0, C2 = 0, C3 = 0), in the third M-subframe (C31, C32, C33); the remaining C-Bits
(three C-bits in M-subframes 1, 2, 4, 5, 6, and 7) may be individually set to one or zero,
and may vary with time. The X-bits are set to binary one (X1 = 1, X2 = 1).
3.1.2
SDH/SONET:
Reference: [R50, 51, 40, 110].
SONET is recommended by ANSI, whereas SDH is recommended by ITU.
Difference between SDH and SONET:
Frame field terminology,
Minor differences in the application of certain overhead bytes, level of detail beyond the
scope of this document.
3.1.2.1 THROUGHPUT
Two levels of SDH/SONET signals are used within UMTS network.
These levels and associated throughputs are presented in the following table:
Notation:
-
SDH Level
SONET Level
Throughput
Throughput
User in Mb/s
Throughput
User in Cells/s
STM1
ClearChannel
STS3 = OC3
Concatenated
155,52 Mb/s
149,76 Mb/s
353 207
STM4
STS12 = OC12
622,08 Mb/s
1 412 828
OC-n stands for OpticalCarrier level n: Optical specification for signal generation level.
Carries Maintenance and Status signals related to SDH MultiplexSection / SONET Line.
LowOrder Section OAM flow:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 17/263
Carries Maintenance and Status signals related to SDH lowOrder PathSection / SONET
Path.
HighOrder Section OAM flow:
Carries Maintenance and Status signals related to SDH highOrder PathSection / SONET
Path.
The mechanisms to provide OAM functions and to generate Transmission OAM flows depend on the
transport mechanism of the transmission system as well as on the supervision functions contained
within the physical layer termination functions of equipments. Three types of transmission can be
provided in ATM networks:
- SDH-based transmission systems;
-
Rule: TEG_SDH_OAM_1
On ALU nodes, the OAM Flow Type of Transmission implemented is SDH/PDH based. Not Cell based.
The following Maintenance signals may be generated on different kinds of transmission OAM levels:
- AIS (Alarm Indication Signal):
AIS signal notifies the adjacent downstream node that a failure has occurred upstream.
AIS may be generated at MultiplexSection, LowOrder and HighOrder PathSection level.
The SDH MS-AIS is renamed L-AIS in SONET.
AIS triggers: LOS, LOF condition within 125 s on the incoming link.
The MS-AIS is generated in a STM-N / OC-N that contains a valid MultiplexSection
overhead, the K2 byte indicating MS-AIS and a all-ones pattern in the payload:
K2 byte
Bits 6, 7, 8
111
MS-AIS
The HO & LO P-AIS are coded with as all one in the container and Path pointers.
-
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 18/263
Bits 6, 7, 8
110
MS-RDI
The HO and LO RDI are coded in one bit of the HO / LO container overhead.
Examples of AIS and RDI generation on UMTS interface composed of SDH nodes:
POH
MSOH
P-RDI
K1
K2
P-AIS
0 000
UMTS
UMTS
UMTS
UMTS
LOS Condition
AIS
ATM
ATM
ATM
ATM
crossConnect
Line 1
TX
TX
RX
RX
W
RX
RX
W
RX
RX
RX
RX
RX
RX
RX
RX
TX
TX
Selected Line
TX
TX
RX
RX
TX
TX
TX
TX
RX
RX
RX
RX
TX
TX
PTE
PTE
RSTE
RSTE
MSTE
MSTE
TX
TX
Regenerator
W
TX
TX
PTE
PTE
TX
TX
Line 0
MultiPlex Section 1
RX
RX
TX
TX
TX
TX
RX
RX
RX
RX
TX
TX
MultiPlex Section 2
Figure 3-3 AIS/RDI Generation
3.1.2.3 APS
Reference: [R50 & R51 & R110],
Each Iub ATM SDH line is duplicated on the RNC, referred as 1+1 port redundancy, to ensure that the
network will continue operation when a single SDH line is defective. The duplicated SDH line is either
located:
- In the same card case of MSA32E1/Oc3, it is referred as intraCard APS or
-
One line is configured as the Working line, whereas the associated line is configured as the Protected
Line. See MML Attributes:
ATTRIBUTE Aps workingLine (working)
ATTRIBUTE Aps protectionLine (protection)
Both the Working and the Protected lines carry the same payload in the transmit direction, but only the
Working line is used for received payload.
At the node startup, workingLine is selected for receiving user payload data.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 19/263
Nodes permanently monitor quality of the received signal. Based on these measurements, either node
keeps the working line selected or decides to select protectionLine for receiving user payload data; this
operation is referred as APS Switch.
The Line switching time in case of a fault (SF/SD on the line) is within 50 ms
RNC
RNC
UMTS
UMTS
Node
Node
ActiveCard
16pOC3
16pOC3
WorkingLine
Rx
Rx
Tx
Tx
STM1
STM1
Rx
Rx
Tx
Tx
Same Signal
Rx
Rx
Tx
Tx
Rx
Rx
Tx
Tx
STM1
SDH Network
RNC Traffic
Traffic generator
generator
RNC
16pOC3
16pOC3
Tx
Tx
Rx
Rx
Tx
Tx
Rx
Rx
16pOC3
16pOC3
STM1
Tx
Tx
Rx
Rx
Protected Line
Tx
Tx
Rx
Rx
16pOC3
16pOC3
Rule: TEG_SDH_APS-1
It is recommended to activate APS on all 16pOC3 FP ports.
Moreover it is recommended to configured them as
- WorkingLine, Stm1 links on the 16pOC3/Stm1 FP located on RNC-IN Slot 8,
- ProtectedLine, Stm1 links on the 16pOC3/Stm1 FP located on RNC-IN Slot 9.
Abnormal Case:
In some cases, operators may decide temporarily not to connect the second fiber on some interfaces.
In such a context:
- IuxIf constraint: If LAPS component is configured on one port supporting AAL2 Vcc, LAPS
must be configured on all RNC 16pOC3 FP ports supporting AAL2 Vcc, even if the second
fiber not connected, in order to ensure a proper behavior of the equipment.
- No constraint on other application: AtmMpe,
- Moreover to minimize outage duration, for conformity with R&D platform RNC configuration
and to facilitate introduction of future features (eg: Y-Splitter)
Its recommended to configure LAPS on each RNC 16pOC3/Stm1 FP port.
Rule: TEG_SDH_APS-3
It is recommended to configure the LAPS component between each port of the pair of
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 20/263
16pOC3/Stm1 FP even so the protected fiber is not connected to the RNC 16pOC3/Stm1
FP.
Remark:
If LAPS component is configured whereas the protected fiber is not connected, one port is in LOS
condition and then alarms appear on the Management platform for the non connected fiber; to
remove these useless alarms either lock the non populated port (lock Lp/9 Sdh/i) or activate the
"alarm filtering" (W-NMS).
Unidirectional/bidirectional mode:
Unidirectional mode: APS switching occurs only in the node which detects misbehavior,
when APS is configured in unidirectional mode. There is no APS switching in the remote
node.
Indeed on node which detects traffic disturbance, selected line is switched from the working
line to the protected line, whereas on adjacent node selected line remains the working line.
Even in unidirectional APS, K1 byte is still used to inform the remote SDH node of the local
action. Moreover, K2 byte/Bit5 is set to 0 to reflect unidirectional mode.
Bidirectional mode: APS switching occurs in the node which detect misbehavior on one
hand, and then in the remote node on the other hand, when APS is configured in
bidirectional mode. Node which detects misbehavior on a link invokes APS and informs
remote node by means of SDH MSOH K1 bytes on the protected line that this link is
experiencing a defect. K1 byte is set with the channel number, 0 or 1 in case of redundancy
1+1, and the nature of the defect which occurs on this link e.g.: SF, SD
Indeed on both adjacent nodes, selected line is switch from working line to protected line.
The K2 byte is transmitted too on the protected line.
Remark:
According to SONET recommendation, each node extremity of a SONET link has to
be configured with the same mode unidirectional or bidirectional. If nodes are
configured on different way, each node will apply unidirectional mode.
See MML Attribute: ATTRIBUTE Aps mode
Unidirectional is the default mode on RNC.
Revertive mode:
After APS switching has been invoked, APS feature allows, since misbehavior has been
corrected, to come back to the initial configuration, if Revertive option is enabled. Such
information is exchanged between SDH nodes by means of K1 bytes set with:
WaitToRestore: the protection line is active and the working line has recovered from a
Signal Fail or Signal Degrade. After the period defined by attribute waitToRestorePeriod the
working line will automatically revert to being the received active line and the request will
change to noRequest.
ReverseRequest: This request is only applicable when the provisioned mode is bidirectional.
DoNotRevert: the protection line is active, and Revertive option is not activated. the
working line has recovered from a signalFail or signalDegrade; or a forcedSwitch or
manualSwitch request has been cleared.
NoRequest: the working line is active and no other requests are in effect.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 21/263
Remark:
Bidirectional APS setting allows identifying with any doubt the working fiber.
Unidirectional APS setting is slightly more robust because it can tolerate a failure on the
working fiber transmit side and failure on the protected fiber receive side.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 22/263
LOS Condition
MSOH
K1
UMTS
UMTS
0000
K2
0000
0000
0 110
MS-RDI
UMTS
UMTS
ATM
ATM
ATM
ATM
Regenerator
Regenerator
TX
TX
RX
RX
TX
TX
Line 1
RX
RX
Selected Line
TX
TX
RX
RX
W
RX
RX
TX
TX
PTE
PTE
RX
RX
TX
TX
RSTE
RSTE
RX
RX
TX
TX
PTE
PTE
RSTE
RSTE
Selected Line
Line 0
TX
TX
P
RX
RX
RX
RX
TX
TX
RX
RX
TX
TX
TX
TX
RX
RX
TX
TX
RX
RX
MultiPlex Section
RX
RX
TX
TX
APS Invokation
POH
MSOH
K1
1101
K2
0001
0000
0000
SF HP Work
Prot
Idle
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 23/263
Remark:
APS is configured on the 16pOC3 FP, if one line is in LOS condition:
- No P-RDI is returned to the farEnd (If P-RDI would be returned the farEnd would discard the
traffic),
- The MS-RDI is returned to the farEnd.
2
POH
MSOH
MSOH
K1
0000 0000
K1
0000
K2
0000
0 110
MS-RDI
K2
0000
0000
0 111
MS-AIS
UMTS
UMTS
UMTS
UMTS
LOS Condition
AIS
ATM
ATM
ATM
ATM
Regenerator
Regenerator
TX
TX
RX
RX
TX
TX
Line 1
RX
RX
Selected Line
TX
TX
RX
RX
W
RX
RX
TX
TX
PTE
PTE
RX
RX
TX
TX
RSTE
RSTE
RX
RX
TX
TX
PTE
PTE
RSTE
RSTE
Selected Line
Line 0
TX
TX
P
RX
RX
RX
RX
TX
TX
RX
RX
TX
TX
TX
TX
RX
RX
TX
TX
RX
RX
MultiPlex Section
RX
RX
TX
TX
APS Invokation
2
MSOH
K1
1101
K2
0001
0000
0000
SF HP Work
3.2
ATM
3.2.1
NNI
POC
Network side Network side
User side
RNC-IN
User side
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 24/263
Public
UNI
NodeB
POC
UNI
User side
ATM BackBone
Network side
UNI
RNC-IN
UNI
User side
3.2.2
VPC, VPT
A VPC (Virtual Path Connection) is an ATM Connection resulting from the grouping of different Vcc. A
VPC is identified by VPi (Virtual Path Identifier).
The AtmForum defines the notion of a VP endPoint. A VP endPoint is the node which is responsible for
the grouping of Vcc within a VPC. This function is implemented in Passport nodes as a VPT component
(VirtualPathTermination).
The reason of grouping several Vcc within one VPC, by means of VPT, is to apply a common treatment
to the set of Vcc, e.g.: TrafficManagement, OAM.
3.2.2.1 VPC
The target of this section is to summarize contexts where VPCs are required.
NodeB E1/T1s can be connected directly to ASP network or connected to a POC before reaching the
ASP.
- When the NodeB is connected directly to the ASP network, without POC, in a multiPCM
configuration, it is recommended to use one VPC for each E1/T1 link that connects NodeB to
the ASP. The ASP provides the E1/T1 access port as well as the VPC across the network.
There are per nodeB as many VPC configured in the ASP as amount of E1/T1 per nodeB.
However, the OAM VCC must still be configured separately; explanation is given in
trafficShaping section.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 25/263
1 E1/T1
VC UP DS
NodeB
x
VC UP NDS
VC CP
VC CCP
VP x , rtVBR
VC OAM
VC OAM
VC UP NDS
VC CP
VC CCP
VP y, rtVBR
VC OAM
VC OAM
VC UP DS
NodeB
z
VP x1
VP y1
VP z1
VCC OAM x
VCC OAM y
VCC OAM z
1 E1/T1
VC UP NDS
VC CP
VC CCP
VP z , rtVBR
VC OAM
VC OAM
16pOC3/STM1 FP
NodeB
1 E1/T1
ATM Backbone
VC UP DS
RNC-SDH
RNC-SDH
When NodeB, IMA configuration, is connected directly to ASP network, without POC, it is
recommended to use one VPC per IMA linkGroup that connects NodeB to ASP. There are per
nodeB as many VPC configured in the ASP as amount of IMA linkGroups per nodeB.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 26/263
POC
VC OAM
NodeB
VCC OAM
VC UP DS
VC UP NDS
k=x
VC CP
RNC-SDH
VC CCPn
VPu, rtVBR
VC UP NDS
VC CP
VC CCPn
k=y
VC OAM
VCC OAM
POC
VPv, rtVBR
RNC-IN
NodeB
ATM Backbone
VPu, rtVBR
VC UP DS
VCC OAM
VCC OAM
VC UP DS
NodeB
VPv, rtVBR
VC UP NDS
VCC OAM
VC CP
VC CCPn
k=z
VC OAM
VCC OAM
Figure 3-9 VPC setting when NodeB connected to ASP through POC
Rule: IubTEG_VP_01
- If ASP and POC inserted on Iub interface, on RNC side set one VP per POC.
- If NodeB MultiPCM configuration connected to ASP without POC, on RNC side set one
VP per NodeB E1/T1 link.
- If NodeB IMA configuration connected to ASP without POC, on RNC side set one VP
per NodeB IMA linkGroup.
Remark:
If VPI of all nodeB Vcc is set to 0, the ATM network cannot treat this as VPC. VPI 0 is reserved for VCC
connections, as defined by ITU-T and ATM Forum.
VPC ServiceCategory:
It is recommended to configure Iub VPC with rtVBR serviceCategory.
Setting VP serviceCategory with rtVBR instead of CBR provides the VP ATM connection
with a longer bufferSize e.g.: Passport CBR default bufferSize is 96 cells, whereas rtVBR
default bufferSize is 480 cells.
Within ASP, CBR serviceCategory might be reserved for traffic more vulnerable to delay:
GSM, ATM CES
Rule: IubTEG_VP_02
VPC ServiceCategory is set to rtVBR
VP TrafficDescriptor parameter:
Setting of VPC TrafficDescriptor Throughput parameters (PCR, SCR), depends on Iub
configuration:
- Case of NodeBs connected directly to ASP:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 27/263
A VPC initiated in the ASP and terminated in the RNC, if no bandwidth constraint
between ASP and RNC, then
o VPC PCR could be set at NodeB(s)*E1_bandwidth, and
o SCR of PVP could be set at NodeB(s)*E1_bandwidth*E1_UsageRate.
With UsageRate = 80%
Remark:
If on RNC, trafficShaping at VP level is activated, only PCR is taken into account since
16pOC3 FP provides singleRate shaping (linearShaping).
-
E1/T1
NodeB
NodeB
E1/T1
NodeB
ATM Switch
E1/T1
ATM Switch
E1/T1
STM1/OC3
RNC
TrafficRegulation mechanisms:
When an ASP is included on the Iub interface and provides policed access, it is recommended
to group the Vcc into a single Vp and to invoke TrafficShaping at VP level either on POC and
RNC side.
Rule: IubTEG_VP_03
When an ASP is included on the Iub interface and provides policed access, it is recommended
to activate the TrafficShaping at Vp level, on the RNC side or on the POC side (if present).
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 28/263
Moreover when activating trafficShaping at VP level on one port of the 16pOC3/Stm1 FP, the size of the
assigned perVc queue need to be configured with an appropriate value see 3.2.6.1.
3.2.2.2 VPT
Within Passport two kinds of VPTs are available:
- basicVPT and
- StandardVPT.
BasicVPT is available on APC based card, e.g.: 16pOC3 FP and AQM based cards, e.g.: 4pOC3 FP,
whereas StandardVPT is available only on AQM based cards.
When configuring basicVPT on a port, activation of trafficShaping is not allowed. For activating
trafficShaping at VP level, a second port and a hairpin is required; VPT is configured on one port, traffic
is diverted to a second port where trafficShaping is activated. It is called the two port solution.
BackPlane
Rx
APC
C la s s
S c h e d u le r:
EP & M BG
C o n n e c t i o n S c h e d u le r :
W FQ O r SFQ
T r a n s m it
P e rV C & c o m m o n Q u e u e s
EP0
P er V C Q u e u e s :
VCC 1 Q ueue
W e ig h t 1
Port1
VCC 2 Q ueue
W e ig h t 2
L in k C la s s
Q ueue
fo r E P 0
V P C Q u eu e
W e ig h t 3
Tx
VPT
Co m m on Q ueues:
E P 1 to E P 7 Q u e u e s
Per VC Q ueues :
VCC 71 Q ueue
W e ig h t 1
L in k C la s s
Q ueue
fo r E P 7
VCC 72 Q ueue
W e ig h t 1
EmissionPriority/MostUrgent
E P 0 Q u eu es
C om m o n Q ueues:
EP2
CBR
EP3
rtVBR
EP4 nrtVBR
EP7
UBR
VCC 73 Q ueue
W e ig h t 1
Rx
APC
C la s s
S c h e d u le r :
EP & M BG
C o n n e c tio n S c h e d u le r :
W FQ O r SFQ
T ra n s m it
P erV C & co m m o n Q u e u e s
CBR
E P 0 Q ueues
Port2
Per VC Q ueues :
VCC 1
Q ueue
W e ig h t 1
VCC 2
Q ueue
W e ig h t 2
L i n k C la s s
Q ueue
fo r E P 0
VPC
Tx
C o m m o n Q u eu es:
Q ueue
W e ig h t 3
E P 1 to E P 7 Q u e u e s
Per V C Q ueues :
VCC 71 Q ueue
W e ig h t 1
L i n k C la s s
Q ueue
fo r E P 7
VCC 72 Q ueue
W e ig h t 1
EmissionPriority/MostUrgent
C om m o n Q u eu es:
rtVBR
nrtVBR
EP0
EP2
EP3
EP4
EP7
VCC 73 Q ueue
W e ig h t 1
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 29/263
AtmIf n1
VPT vpi
VPd
- SegmentLoopBack on, off, sameAsInterface
- EndToEndLoopBack on, off, sameAsInterface
AtmIf n2
VPC vpi
VPd
TM
TrafficShaping disabled, sameAsCa
AtmIf n1
VPT vpi
VPd
- SegmentLoopBack on, off, sameAsInterface
- EndToEndLoopBack on, off, sameAsInterface
TM
- TrafficShaping disabled, sameAsCa
- ServiceCategory,
- Tx TrafficDescriptor Type & Parameters,
- Rx TrafficDescriptor Type & Parameters,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 30/263
3.2.3
OVERSUBSCRIPTION
E1/T1
BwPoll-1
100%
All SC
3.2.3.2 NODEB:
OverSubscription feature is not available on NodeB.
3.2.4
CAC
CAC (Connection Admission Control) is a generic function which checks that connections request less
bandwidth than available.
Different algorithm may be used for CAC implementation
CAC is an algorithm invoked at AtmConnection setup. It verifies that bandwidth required for the new
atmConnection is below than bandwidth available on the physical link.
For Permanent VC, CAC is invoked in provisioning phase, whereas CAC is invoked in establishment
phase for a Switched VC.
Based on atmConnection trafficDescriptor, CAC calculates the ECR (EquivalentCellRate) associated to
this atmConnection. ECR is the bandwidth required for an atmConnection from the CAC point of view.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 31/263
AtmConnection is rejected when it requires more bandwidth than available at physical link.
Different kinds of CAC Algorithm:
- NodeB:
Equivalent cell rate is calculated as following:
- ECR = PCR for a CBR atmConnection,
- ECR = SCR for a VBR atmConnection,
- ECR = MCR for a UBR+ atmConnection,
- ECR = 0 for a UBR atmConnection,
Remark:
CDVT is not managed at NodeB level.
-
Hsdpa CAC:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 32/263
The Hsdpa CAC is invoked in RAB AssignmentRequest phase, (same as for the aal2LinkCac), it
consists in counting amount of Hsdpa calls per NodeB radio cell.
The amount of allowed Hsdpa calls per NodeB radio cell is configured through the parameter:
HsdpaCellClass/maximumNumberOfUsers
Range: [0..50], Class 0, Granularity RNC, defaultValue 20
3.2.5
TRAFFIC MANAGEMENT
At ATM level, bandwidth per ATM Connection is managed by means of TrafficDescriptor parameters.
TrafficDescriptor parameters may be involved in traffic regulation, when its activated.
Regulation of traffic on Egress side is achieved by trafficShaping whereas regulation of traffic on
Ingress side is achieved by means of Policing.
For a VBR service category, traffic is considered bursty, and then cells are sent within a burst, bursts are
sent periodically.
Such traffic is described at ATM level by means of 2 throughput parameters: PCR and SCR and size of
the burst MBS:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 33/263
Context:
TrafficSource: continuous
DualRateShaping:
PCR = linkRate
CDVT = 0
SCR = 1/8 LR
MBS = 3
=> BT = 2*(Ts-T)
1 23456
Shaped traffic
TAT
TAT
Period2
Period3
Period4
Period5
Period6
T= 1/PCR
Ts= 1/SCR
BT
Ts= 1/SCR
BT
Ts= 1/SCR
Ts= 1/SCR
BT
BT
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 34/263
RRC
PDCP
RRC
PDCP
RLC
RLC
MAC
MAC
Physical
Physical
AAL2
ATM
Physical
UE
NodeB
Uu
Iub
RNC
Context:
MBS = 4
Tm = 20 ms
=> SCR = MBS/Tm = 200 c/s
=> Ts = 5 ms
PCR = 2 * SCR
=> T = 2,5 ms
Example: RAB 64
E1:
= 220 s
STM1: = 2,8 s
R A B 6 4 , B lo c k s
1 2 3 4
1 2 3 4
t
T T I= 2 0 m s
ATM
TD
TAT
TAT
P e r io d 2
P e rio d 3
P e rio d 4
T = 1 /P C R
T s = 1 /S C R
BT
T s = 1 /S C R
BT
T s = 1 /S C R
BT
T s = 1 /S C R
BT
Tm = M BS / SCR
T T I= 2 0 m s
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 35/263
Direction
Speech /
12,2 kb/s 12,2 kb/s
DL
CS Data /
14,4 kb/s 14,4 kb/s
DL
CSD 57, 6
DL
UL
UL
TTI
BlockSize
#MaxBlocks
/TTI
Consecutive
ATM cells
Ms
Bits
Bytes
For highest TF
20
244
31
20
244
31
40
576
72
40
576
72
40
576
72
UL
40
576
72
4
Table 3-1 List of RAB for DelaySensitive traffic
UMTS
ServiceClass
RAB
Direction
64kb/s / 64 kb/s
DL
TTI
Background
Interactive /
Ms
UL
64kb/s / 128 kb/s
DL
DL
UL
BlockSize
Bits
Bytes
#MaxBlocks
/TTI
Consecutive
ATM cells
For highest TF
20
336
42
20
336
42
20
336
42
20
336
42
10
336
42
12
12
UL
20
336
42
4
Table 3-2 List of RAB for nonDelaySensitive traffic
RAB definition provides then, amount of consecutiveCellsForSingleCall sent each TTI. This value can
be considered as the MBS for a single call.
Moreover to establish MBS value, maximum amount of simultaneous calls handled by a node has to be
taken into account.
According to the chosen methodology, either simultaneous call is considered as an input for setting
MBS value, or amount of simultaneous calls is calculated based on a customer trafficModel, by means
of a dimensioning exercise.
Remark:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 36/263
3.2.5.3 TRAFFICSHAPING
Traffic shaping regulates egress traffic according to trafficDescriptor parameter values.
TrafficShaping is presented in a PowerPoint file stored on Transport web site. Here an extract from this
file.
According to line card, different kinds of trafficShaping are available: singleRate and dualRate shaping.
(SingleRate TS is also called LinearShaping; dualRate TS is also called InverseVBR TS)
On 16pOC3/STM1, only SingleRate TrafficShaping is available, whereas on 4pOC3 both kinds of
trafficShaping are available.
LinearShaping regulates egress traffic according to PCR, whereas dualRate Shaping regulates egress
traffic according to PCR, SCR and MBS. DualRate Shaping may be called VBR shaping.
For a continuous flow of traffic has to be transmitted, and dualRate Shaping is activated, MBS cells are
sent at PCR, following cells are sent at SCR:
1 23456
Shaped traffic
TAT
TAT
Period2
Period3
Period4
Period5
Period6
T= 1/PCR
Ts= 1/SCR
BT
Ts= 1/SCR
BT
Ts= 1/SCR
BT
Ts= 1/SCR
BT
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 37/263
Rule: IubTEG_ATM-TM_1
To the extent that public ATM backbone is not involved on the UMTS interface, It is
not recommended to activate TrafficShaping or Policing function, in order to avoid
cell delay and cell discard.
Rule: IubTEG_ATM-TM_2
When a policed ATM backbone is inserted on the UMTS interface, It is recommended
to activate TrafficShaping at VP level.
According to the Iub topology, the VPC results either from the grouping of all Vcc
from a NodeB with exception of the OAM VCC, or from the grouping from all Vcc
from nodeBs behind the POC, with exception of NodeB OAM Vcc.
Reason why Isolating NodeB OAM VCC from a NodeB or POC VPC:
When activating TrafficShaping at VP level on RNC, two 16pOC FP ports are
involved.
On the first port NodeB Vcc dedicated Queues are scheduled, resulting in a common
queue, VPT is configured. The common queue feeds the loop at OC3/STM1 linkRate.
On the second port, the VPC dedicated queue is fed at STM1/OC3 linkRate. The VPC
queue is scheduled at ShapingRate.
The VPC Queue ingress throughput is higher than the egress throughput.
Therefore a high volume of OAM cells may be inserted between delay sensitive cells
in the second port VPC queue, which generates delay on delay sensitive cells.
3.2.5.4 NODEB
Node-B VCC can be either shaped or not shaped (see 4 NodeB release compliancy).
When TrafficShaping applies, nodeB transmits MBS cells at PCR, and following cells are sent at SCR.
In certain configuration, when connecting NodeB to RNC across ATM backbone, a VPC may be used
on the POC / RNC interface. All Vcc on NodeB E1/T1 with exception of OAM VCC will be carried on
this VPC. As all E1 /T1 traffic is carried on VPC, this VPC is equivalent to leased line E1/T1.
VP EndPoint is not provided by NodeB.
3.2.5.5 RNC
Traffic shaping is not activated by default in RNC downlink direction.
Traffic shaping is not recommended on a per VC basis since, since it impacts delay.
Moreover, TrafficShaping is available on 16pOC3/STM1 card only with EP0.
Nevertheless in case of RNC-SDH/SONET, when crossing ATM Public network, Traffic Shaping at VP
level is recommended at remote concentrator level and at RNC nodes.
On RNC-IN, hairpins are required on 16p/OC3-STM1 card when invoking on one hand VPT (only
basic VPT available on APC) and on other hand TrafficShaping, what is called the 2portSolution.
As 16 ports STM-1 FP supports only linear shaping, the same linear traffic shaping method should be
used on remote concentrator.
3.2.6
QOS
Within ALU UMTS node, QOS is handled at ATM level, by means of:
Different parameters:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 38/263
Mechanism: Scheduling.
3.2.6.1 BUFFER
This section concerns Passport based UMTS nodes only.
A queue may be provisioned either per ATM Connection or per serviceCategory; it is referred as
perVcQueuing or Common Queuing.
APC
Class
Scheduler:
EP & M BG
Transm it
PerVC & comm on Q ueues
Connection Scheduler:
SFQ
EP0 Q ueue
Per VC Queues :
Com mon
Queues:
LinkClass
Queue
for EP0
n1 cells
n2 cells
n3 cells
AT M IP FP QOS M apping
SC
EP
(5 EP, from EP0 to EP7)
FROM
PQC
CLP, SC and CC
Cell discard
EmissionPriority/MostUrgent
Or Comm on Queue:
EP0
cells
EP1
Connection Scheduler:
W FQ
CBR
EP2
I = [2, 3, 7]
rtVBR
EP3
EP i Queue
Per VC Queues :
To Link
Egress
Com mon
Queues:
nrtVBR
ATM Connection i1 Queue
W eight 1
EP4
EP5
LinkClass
Queue
for EP i
UBR
EP7
Or Comm on Queue:
AP C M apping Table,
SC m apped to EP configurable
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 39/263
AQM
Class
Scheduler:
EP & M BG
Transm it
PerVC & comm on Q ueues
Connection Scheduler:
W FQ Or SFQ
EP0 Q ueue
Per VC Queues :
Com mon
Queues:
LinkClass
Queue
for EP0
n1 cells
n2 cells
n3 cells
AT M IP FP QOS M apping
(according to AQ M
Mapp ing Table) :
SC and CLP
EP
(EP0 to EP7)
DP
(DP0 to DP7)
FROM
PQC
E missionPriority/MostUrgent
Or Comm on Queue:
EP0
cells
EP1
CBR
EP2 (CLP1)
CBR
(CLP0)
rtVBR
EP3 (CLP1)
rtVB R
(CLP0)
I = [2, 3, 7]
EP i Queue
Per VC Queues :
To Link
Egress
Com mon
Queues:
nrtVB R
EP4 (CLP1)
nrtVBR
(CLP0)
EP5
LinkClass
Queue
for EP i
UBR
EP7 (CLP0+1
)
DP3
DiscardPriority
DP2
DP1
DP0
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 40/263
The discard thresholds are set at approximately 35, 75 and 90 percent of the scaled queue limit for
traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively.
When this attribute is set to autoConfigure, an appropriate value is selected based on the card type. It is
set to 96 for the following Passport ATM cards (DS1, E1, DS3, E3, and OC-3).
For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a
value in the Vcd Tm or Vpd Tm txQueueLimit attribute. The operational value of the maximum length of
a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vp Tm txQueueThresholds
attribute.
Default autoConfigure
ATTRIBUTE AtmIf Vcc Vcd Tm txQueueLimit (txQlim)
This attribute specifies an override to the default transmit queue limit for this connection.
A value of sameAsCa means that the default per-VC transmit queue limit, as defined by the CA service
category, is used for this connection.
Default sameAsCa
Per Card and per serviceCategory, a summary of the default buffer size values:
xpOC3 FP
serviceCategory
CBR
rtVBR
nrtVBR
UBR
BufferSize
maximum effective
96
480
10240
10240
86
432
7680
7680
ratio
90%
90%
75%
75%
MSA32 FP:
MSA32
serviceCategory
CBR
rtVBR
nrtVBR
UBR
BufferSize
maximum effective
96
288
1792
1792
86
259
1344
1344
ratio
90%
90%
75%
75%
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 41/263
3.2.6.2 CLR
CLR (Cell Loss Ratio) is defined as the number of lost cells divided by the total number of transmitted
cells per ATM Connection.
CLR is specified per ServiceCategory at PVC provisioning. It is involved in ECR calculation done by
ATM CAC.
A small CLR value (for example 10-10) configured on a serviceCategory, results in reserving more
bandwidth for ATM Connections configured with this serviceCategory, in other word results in a larger
ECR.
If CLR=0, means that no bandwidth is reserved per ATM connection.
No CLR is configured for UBR serviceCategory, since no bandwidth is reserved for UBR
atmConnections.
Suggested CLR values:
CLR values:
rtVBR
nrtVBR
-10
-9
If CSD64 mapped on UP DS
-10
-7
Remark:
CSD 64 is mapped on UP NDS VCC in release2, whereas it is recommended to map it
to UP DS VCC in release3.
3.2.6.3 SCHEDULING
At ATM level, QOS is provided by means of Scheduling mechanism. Scheduling takes into account
ATM Connection ServiceCategory Parameter.
Scheduling applies to egress traffic.
This section describes Scheduling within Passport node.
Passport provides a two stage Scheduling:
Connection Scheduling and
Class Scheduling.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 42/263
Within each EP pool of Queues, cells are extracted from each perVC queues,
and are stored in the associated linkClass Queue.
Amount of cells extracted per perVC queue depends on PerVC Weight (WFQ),
or
Class Scheduler:
Each linkClass (5 for APC, and 8 for AQM) queue is pulled according to its priority.
APC
Class
Class Scheduler
Scheduler Connection
Connection Scheduler
Scheduler
WFQ
WFQ or
or SFQ
SFQ
EP 0 linkClass Queue
1/ SC:
EP 0 perVC Queues
EP, (5 EP (O, 2, 3, 4, 7)
n1 cells
ATM Connection 01 Queue
Weight 1
n2 cells
n3 cells
From PQC
EmissionPriority/MostUrgent
P0
To Link
Egress
EP1
CBR
EP2
EP 7 perVC Queues
EP 7 linkClass Queue
rtVBR
EP3
n1 cells
ATM Connection 71 Queue
Weight 1
n2 cells
n3 cells
nrtVBR
EP4
EP5
EP6
UBR
EP7
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 43/263
Less severe
congestion state
Most severe
congestion state
The AQM perVC buffers are implemented with 3 hardcoded thresholds, called CongestionControl levels,
involved in the discard policy. The CC level thresholds are identical for each serviceCategory:
Node discards
DP2 & DP3 cells
35%
CC2
CC3
No Cell discarded
CC1
75%
Node discards
DP3 cells
CC0
Node discards
DP1 & DP2 &
DP3 cells
90%
EP1
EP2
CBR
(CLP1)
CBR
(CLP0)
EP3
rtVBR
(CLP1)
rtVBR
(CLP0)
EP4
nrtVBR
(CLP1)
nrtVBR
(CLP0)
EP5
EP6
EP7
UBR
(CLP0&1)
least Urgent
DP3
DP2
Least important
DP1
DP0
DiscardPriority
Most important
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 44/263
Then a comparison is done between discardPriority value associated to the cell and buffer load, resulting in
storage or discard of the cell:
When buffer load is below CC2 threshold, all cells candidate to transmission are accepted in the buffer.
When buffer load has reached CC1 threshold, cells with discardPriority value 3, are discarded, whereas cells
with discardPriority value 2, 1 and 0 are stored in the buffer.
When buffer load has reached CC0 threshold, cells with discardPriority value 3, 2 and 1, are discarded,
whereas cells with discardPriority value 0 are stored in the buffer.
Queues:
MappingTable :
ATM Interface :
EmissionPriority
Tagged cell
NonTagged cell
Most Urgent
EP0 Queue
CBR
EP0 (CLP1)
CBR
(CLP0)
rtVBR
EP1 (CLP1)
rtVBR
(CLP0)
CLP1
Cell2
CLP0
Cell1
VCC CBR
CC0 CC1 CC2
CC3
EP2
EP3
nrtVBR
EP4 (CLP1)
Tagged cell
nrtVBR
(CLP0)
EP4 Queue
CLP1
EP5
Cell2
NonTagged cell
CLP0
Cell1
VCC nrtVBR
EP6
CC0 CC1 CC2
CC3
UBR
EP7 (CLP0+1
)
Least Urgent
DP3
DiscardPriority
DP2
DP1
Least important
DP0
Most important
Figure 3-22 Discard Policy on AQM card, based on an example of QOS mapping table.
CBR
90%
CLP0 discard
CC0
CC1
38%
CLP1 discard
CC2
CC3
90%
rtVBR
nrtVBR
CLP0 discard
CC0
38%
CLP1 discard
CC1
CC2
CLP0 discard
CC0
CC1
75%
CLP1 Discard
CC2
CC3
32%
CC3
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 45/263
No DiscardPriority parameter on the APC based card, the cell CLP values is directly compared to the buffer
occupancy:
Queues:
MappingTable :
ATM Interface :
EmissionPriority
EP0 Queue
Tagged cell
NonTagged cell
Most Urgent
90%
38%
CBR
CLP1
Cell2
CLP0
Cell1
EP0
VCC CBR
EP1
CC0 CC1 CC2
CC3
rtVBR
EP2
EP3
EP4 Queue
Tagged cell
nrtVBR
NonTagged cell
EP4
CLP1
75%
Cell2
CLP0
Cell1
32%
EP5
VCC nrtVBR
EP6
CC0 CC1 CC2
CC3
UBR
EP7
Least Urgent
Figure 3-24 Discard Policy on APC card, based on an example of QOS mapping table.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 46/263
CDVT =< ( T
), e g : C D V T = ( T ):
TAT
P e r io d 1
P e r io d 2
TAT
P e r io d 3
TAT
P e r io d 4
TAT
t
T = 1 /P C R
CDVT
CDVT > ( T
CDVT
CDVT
), e g : C D V T = 2 *( T ):
TAT
P e r io d 1
CDVT
P e r io d 2
TAT
P e r io d 3
TAT
P e r io d 4
TAT
t
T = 1 /P C R
CDVT
CDVT
CDVT
Figure
3-25
CDVT
CDVT
representation
A consequence of setting CDVT is backToBack cell.
BackToBack cells are cells transmitted at linkRate. When setting CDVT, backToBack
cells are declared conformed.
Amount of cells transmitted backToBack declared conformed depends on CDVT
value:
N = Integer [1 + CDVT / (T )],
with:
N: amount of cells transmitted backToBack,
T = 1/PCR,
3.2.7
FRACTIONAL E1/T1
Fractional E1/T1 [R46 & R93] Transport feature is used for UMTS Drop&Insert feature.
Drop&Insert is available on single port E1/T1 (combination of Fractional Rate E1/T1 for UMTS and
AAL1 CES cross connect for GSM IBTS).
NodeB CCM card supports fractional E1/T1.
Rule: IubTEG_D&I_01
Only one link (E1/T1) may be used in a nodeB toward the RNC, if configuring Drop&Insert.
Let us called:
The droppedNode: node at the end of the chain, where fractional E1/T1 is configured.
The droppingNode: node which inserts on the link its own SDUs and SDUs received
from the dropped node.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 47/263
Dropped NodeB
Dropping NodeB
E1 n1
E1 n2
NodeB
N2
NodeB
N1
TDM
backbone
UMTS IBTS
1 Fract E1
14 TS
RNCANode
TDM
backbone
UMTS IBTS
1 Fract E1
12 TS
RNCINode
e/w MSA 32
with STM-1
Example:
NodeB N1 Iub ATM stream from 12 TS (E1 n1, TS 2-13) is sent over STM1 to RNC-IN,
E1 N2 :
STM-1:
Aggregation traffic from many IBTS including the ones from other MSA (full
or fractional E1).
Rule: IubTEG_D&I_02
D&I of 2 nodeB max,
At MSA 32E1 port level : AAL1 CES must be used to do TDM cross connect ,
Connectivities:
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 48/263
Remarks:
Maximum number of available E1 TS is 30 since TS0 and 16 are reserved [R47].
An Hairpin must be added on MSA32 card because MSA32 port can handle only 1 ATM interface :
RNC-ANode
32 Timeslots
ATM1
Not used
MSA32 card
Node-B 1
Node-B 2
CCM
CCM
ATM1
32 Timeslots
Not used
E1
ATM1
32 Timeslots
Not used ATM2 Not used
E1
32 Timeslots
ATM2
32 Timeslots
Not used ATM2 Not used
ATM / Fractional E1
Timeslot Cross Connect
Cross Connect & ATM Fract E1
Dropped NodeB
Dropping NodeB
T1 n1
T1 n2
UMTS
IBTS N2
UMTS
IBTS N1
TDM
backbone
UMTS IBTS
TST1
112
Fract
14 TS
TDM
backbone
OC-3/T1
connector
RNC
UMTS IBTS
12 TS
1 Fract T1
14 TS
Rule: IubTEG_D&I_03
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 49/263
Connectivities:
Remarks:
F4/F5 AIS dedicated to dropped NodeB Atm connections go through the dropping
nodeB.
The POC based on MSS7k is not involved in T1 D&I, since doesnt provide T1
access.
UMTS
GSM
BTS
NodeB
E1 n1
UMTS IBTS
1 Fract E1
22 TS
1 Fract E1
8 TS
GSM BTS
1 Fract E1
15 TS
TDM
backbone
E1 n2
RNC-ANode
e/w MSA 32
with STM-1
E1 n6
TDM
backbone
GSM
BTS
TDM backbone
shared between
UMTS & GSM
E1 n4
E1 n5
UMTS E1 n3
NodeB 1 Fract E1
15 TS
BSC
GSM
BTS
GSM BTS
2 Fract E1
10 + 8 TS
E1 n7
One E1 link is shared between one GSM BTS and one NodeB:
Example:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 50/263
NodeB ATM stream from 22 TS (E1 N1 TS 2-4, 12-15, 17-31) is sent over
STM-1 to RNC.
E1 N2:
- 15 GSM TS (TS 2, 17-30) are switched on E N 4 and then mapped onto
TS1-TS15 of E1 N7.
E1 N3:
- NodeB stream from 15 TS (E1 N3 TS 17-31) is switched on E1 N5 and
then sent over STM-1 to RNC.
E1 N4:
- 10 GSM TS (TS 1, 5-13) are mapped onto TS2 and TS17-TS26 of E1 N6.
-
The extraction of the GSM TS will be performed by ALU Networks MSS7K. The
limitations are the same as for UMTS-UMTS D&I except that no hairpin is required on
MSA32 card.
Connectivities:
Remarks:
GSM BTS must be the dropping node, in order to not perturb GSM traffic,
Fractional T1:
One T1 link is shared between one GSM BTS and one NodeB:
Rule: IubTEG_D&I_05
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 51/263
GSM BTS must be the dropping node, whereas the UMTS NodeB must be the dropped
node.
Maximum guaranteed configuration 2 dropped nodes: 1 GSM BTS and 1 UMTS nodeB.
The dropping node being a GSM BTS.
Connectivities:
Remarks:
3.2.8
GSM BTS must be the dropping node, in order to not perturb GSM traffic,
Fractional T1 is not available on 4 ports DS3ch IMA nor on 4 port DS3ch CES.
ADDRESSING
Since UNI signaling or PNNI is configured in network, ATM addresses are required. ATM addresses
are called AESA (ATM End System Address). AESA is structured according to NSAP format (Network
Service Access Point)
To establish sPVCs or SVCs across the network, ATM source and destination points need to be
uniquely identified with ATM addresses.
NodeB does not support neither UNI signaling nor PNNI.
3.2.9
PNNI
The PNNI recommendations encompass network Topology and Protocols notions.
Reason for PNNI, on atm interfaces, is to simplify the network configuration and to improve the network
reliability and availability.
The PNNI allows shorter outage times, and transparent recovery from network outage, by means of
dynamic rerouting mechanisms.
Therefore, a better GOS behavior is expected when configuring PNNI.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 52/263
PNNI RoutingProtocol: Distribution of Topology information within the network. Thanks to this
protocol, node routing tables are updated with information related to reachability, QOS, resource
availability
Topology information are exchanged between each node of the network by means of Hello protocol
messages. These messages are carried in the RCC (RoutingControlChannel) VCC=0/18.
PNNI Signaling Protocol: allows establishment of ATM connections. This protocol is based on BISDN [R47 & 90] with some additional functionalities: sourceRouting, crankBack
PNNI Signaling Protocol messages are carried in the SignalingChannel VCC=0/5.
PNNI SignallingProtocol PNNI RoutingProtocol
SSCF-UNI Q2130
SSCOP Q2110
SAAL UNI
CallingParty Node:
Calling vcc: 3/33
Called vcc= 2/32
CalledAddress = AESA_1
Vcc 3/33
ATM
ATM switch
switch
Or
Or
RNC
RNC
CalledParty
CalledParty
CalledParty Node:
vcc= 2/32
Address = AESA_1
ATM
ATM switch
switch
intermediate
intermediate
sPVC
ATM
ATM switch
switch
Or
Or
RNC
RNC
CalledParty
CalledParty
Vcc 2/32
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 53/263
Since the sPvc is configured in the originating node, the sPvc is automatically set in each intermediate
node until the destination node. When establishing a sPvc, an intermediate Passport node runs the ACAC
to verify that the sPvc required bandwidth is acceptable.
In the originating Passport node the GCAC is run.
On each intermediate interface, if the node which sends the Pnni Setup message has a higher nodeId than
the node which receives it, then:
- The local interface vpi.vci is selected by the node which sends the setup message; the
vpi.vci value is chosen in the range specified by the minAutoSelectedVciForVpiZero and
maxAutoSelectedVciForVpiZero attribute.
If no more available vci for VPI=0, then a vci is chosen for the next vpi value; the vci
value is then chosen in the range delimited by: minAutoSelectedVciForNonZeroVpi and
maxAutoSelectedVciForNonZeroVPI attribute.
Else, the vpi.vci value is determined by the node which receives the pnni setup message.
The NodeId attribute is configured under the attribute: atmRouting Pnni ConfiguredNode.
SAAL Failure,
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 54/263
The Hello protocol monitor the status of the SVCC used as a PNNI routing control
channel between the two LGNs to increase robustness.
Failure of the SVCC indicated from lower levels (ATM, PHY, and Signaling) is treated as
a Link down Event. Procedures to re-establish the SVCC are followed.
Expiry of timer T310 or T303
Following table provides duration for re-routing a set of sPVC connections, according to type of Passport
equipment failure (card, shelf):
Recover 10,000 Connections
13 sec
UMTS
UMTS
1/ RELEASE
2/ SETUP
PNNI
PNNI
ATM
ATM
UMTS
UMTS
1/ RELEASE
PNNI
PNNI
PNNI
PNNI
PNNI
PNNI
ATM
ATM
ATM
ATM
ATM
ATM
2/ SETUP
PNNI
PNNI
ATM
ATM
TX
TX
RX
RX
TX
TX
RX
RX
TX
TX
RX
RX
TX
TX
RX
RX
RX
RX
TX
TX
RX
RX
TX
TX
RX
RX
TX
TX
RX
RX
TX
TX
2/ SETUP
2/ SETUP
PNNI
PNNI
ATM
ATM
TX
TX
RX
RX
TX
TX
RX
RX
RX
RX
TX
TX
RX
RX
TX
TX
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 55/263
3.2.9.5.1 RNC-PCM:
The PNNI is used to participate to the Iub interface reliability between POC and RNC (RNC-PCM
configuration). More precisely, the Pnni Rerouting mechanism provides a protection against POC
OC3/Stm1 ClearChannel FP failure eg: MSA32 or 2pOC3 FP.
Rule: IubTEG_PNNI_01
PNNI is recommended for RNC-PCM configuration, on RNC-IN/MSS7k interface.
When a MSA32 card fails, both the APS Working and Protected lines from this card become unavailable,
the PNNI determines the paths terminating on the other FP and re establishes the impacted
atmConnections under condition there is enough available bandwidth on these paths.
RNC-PCM
PNNI signalling
UNI
NodeB
RNC-AN
RNC-IN
E1
STM 1
On the MSS7k / RNC interface, 3 stm1 links are configured for capacity and reliability reasons.
In normal condition, when the 3 stm1 are active, the Iub pnni atmConnections are distributed over the 3
stm1 links.
Even if 3 stm1 links are configured on the Rnc / MSS7k interface, a bandwidth equivalent to 2 stm1 is
reserved for the Iub atmConnections through the trafficDescriptors.
Then in case of failure of one stm1 due to MSA32 FP failure, the two still active stm1, are able to support
all the Iub atmConnections.
The activation of Pnni on the RNC implies the configuration of some pnni sPvc Hairpins on the RNC
16pOC3/STM1 FP card.
The amount of sPvc hairpins is determined based on the bandwidth required on the RNC Iub interface.
Since Iub VCC TrafficManagement parameter had been set in such a way two stm1 bandwidth is enough,
2 sPvc hairpins are set.
The Pnni sPvc source node may be either the RNC-IN, the MSS7k or an atmSwitch.
Rule: IubTEG_PNNI_02
It is preferred to initiate the pnni sPvc in the MSS7k or in an atmSwitch instead of in the RNCIN.
The reason for pnni sPvc source in the atmSwitch is to better managed the case of PCM failure. Indeed
if the pnni sPvc source is configured in the atmSwitch doing the interworking between Pcm interfaces
and sdh interfaces, the pnni atmConnection releasing and rerouting invocations can be synchronized
with PCM failure/restoration events.
3.2.10 IMA
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 56/263
IMA linkGroup
NodeB
NodeB
IMA linkGroup
Up to8 E1
IMA linkGroup
IMA linkGroup
NodeB
NodeB
E1
RNC
RNC
POC
POC
POC
POC
IMA linkGroup
NodeB
NodeB
E1
Stm1
3.2.10.1
SYNCHRONISATION
3.2.10.2
Rule: IubTEG_IMA_02
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 57/263
The iCCM support the two IMA versions 1.1 and 1.0, and provides the ability to fallback
from IMA version 1.1 to IMA version 1.0.
LinkGroup Identifier,
configuration,
synchronization,
status and
defect information
IMA Frame 0
ICP
Link 0
127 ICP
128 cells
ICP
IMA Frame 2
127 ICP
128 cells
127
ICP
127
128 cells
127
ICP
ATM node
ATM node
IMA Frame 1
127
Link 1
IMA
3.2.10.3
IMA LG BANDWIDTH
The process of IMA framing and control slightly reduces the capacity of individual physical
links within an IMA link group.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 58/263
The cell capacity of a physical link involved in an IMA linkGroup is calculated with the
formula:
Rule: IubTEG_IMA_03
IMA link available throughput:
IDCR = TRLCR * 127/128 * 2048/2049
Where:
- IDCR: IMA Data Cell rate, cell capacity of a physical link
- TRLCR: TimingReferenceLinkCellRate, link cell rate without IMA.
Table below provides IDCR for E1 and T1, in the last column is taken into account
MininimumBandwidthGuaranty = 2% reserved for RNC EmissionPriority7 (OAM VCC):
IDCR
(kb/s)
IDCR IDCR-MBG
(cells/s)
(cells/s)
E1
30
1920
4528
1904
4490
4400
T1
24
1536
3622
1523
3591
3519
3.2.10.4
The RNC IMA LinkGroup bandwidth Reduction mechanism is described in section: Erreur ! Source
du renvoi introuvable..
The NodeB IMA LinkGroup bandwidth Reduction mechanism is described in section: 3.8.7.2.
The IMA LinkGroup bandwidth Reduction mechanism is activated as an option in the NodeB, the RNC
or the Passport.
On one IMA interface, the IMA LinkGroup bandwidth Reduction mechanism should not be activated in
both nodes extremity of the IMA interface; the mechanism should be activated in one node at the
extremity of the IMA interface.
The node where is activated the IMA LinkGroup bandwidth Reduction mechanism, since aware about
PCM defect (s), releases one or several Vcc(s) and notifies the adjacent node thanks to atm oam signals.
A/ In case of interworking with an otherVendor atmSwitch, the operator decides to activate the IMA LG
bandwidth Reduction mechanism in:
- The ALU node (the NodeB, the Passport or the RNC) or
- The otherVendor atmSwitch.
If the IMA bandwidth Reduction mechanism is activated in the otherVendor atmSwitch and not in the
ALU NodeB, the operator should take care that the otherVendor bandwidth Reduction mechanism
behavior is compliant with the expectations of the RNC aal2 congestionManagement (3.6.7) and
aal2LinkCac. The otherVendor node must be able to notify the RNC thanks to endToEnd atm oam
signals, about the vcc which have been released, in such a way the RNC is aware about the available
bandwidth on Iub interface.
In fact, the ALU RNC expects that the otherVendor bandwidth Reduction mechanism has same
behavior as the ALU NodeB bandwidth Reduction mechanism.
Expected bandwidth Reduction mechanism behavior from the otherVendor atmSwitch:
Case of 8 PCM within the IMA LG, one PCM defect, then one Up Ds vcc is released,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 59/263
Case of less than 8 PCM within the IMA LG, one couple (Up Ds vcc, Up Nds Vcc) is released
for each PCM defect,
Notification to the atm endPoint nodes about the Vcc release.
If the otherVendor behaves differently than the ALU nodeB, then a specific interworking study will be
required.
Rule: IubTEG_IMA_04
In case of OtherVendor atmSwitch on an Iub IMA interface, the IMA defense mechanism should
be activated in the NodeB or in the otherVendor atmSwitch under condition it provides same IMA
defense behavior as the NodeB
This rule is dictated by the RNC aal2 Congestion Management mechanism.
B/ In case of an IMA interface delimited by a ALU NodeB and a Passport atmSwitch or ALU RNC:
Argument 1:
In the context of IMA LG bandwidthReduction, the RNC aal2 Congestion Management (
3.6.7) expects that:
Only one Up Ds Vcc is released when one PCM defect occurs on an IMA LG
composed of 8 PCM and configured with 8 up ds vcc and 7 up nds Vcc,
At each PCM failure within an IMA LG, one couple (up ds Vcc, up nds Vcc) is
released.
The 4 HP values assigned to the aal2 Vcc within the MSS7k (see Erreur ! Source du renvoi
introuvable.), don't allow to have such a behavior in case of more than 4 PCM within an IMA
LG.
Argument 2:
In the context of IMA LG bandwidthRestoration, the RNC or the Passport restores the vcc
according to the perVc reserved bandwidth (vcc ECR) and the IMA LG available bandwidth.
When restoring the UP aal2 vcc, the RNC or Passport doesnt take care about the aal2 qos, in
other words doesnt guarantee the restoration of as many UP ds aal2 vcc as UP nds vcc.
Beside, in the context of IMA LG bandwidthRestoration, the nodeB restores a couple of (UP
ds, UP nds) vcc each time a PCM is restored.
The NodeB IMA LG bandwidthRestoration algorithm works as expected by the RNC aal2
CongestionManagement mechanism.
Rule: IubTEG_IMA_05
On an IMA interface delimited by the ALU NodeB and either a Passport atmSwitch or the
ALU RNC, it is recommended to activate the IMA LG bandwidth Reduction mechanism
in the NodeB whatever amount of PCM in the IMA LG.
Remark:
When the IMA LinkGroup bandwidth Reduction mechanism is activated on the nodeB, when
bandwidth reduction occurs, the nodeB releases 1 or several Vcc, and returns an endToEnd
oam RDI signal for each released Vcc. On reception of the RDI in the RNC-IN, the Vcc
rdiState is changed to bad, and the aal2/x path/y (linked to the vcc) localBlockingStatus is
changed from unblocked to blocked.
3.2.10.5
The IMA Transmitter shall not introduce differential delay among the constituent links of more
than 2.5 cell times at the physical link rate. Application to E1case: 2,5*220 s = 550 s.
On the IMA Receiver, the amount of link differential delay tolerated by an IMA implementation
shall be up to at least 25 milliseconds when used over DS1/E1 links.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 60/263
In the context of the UMTS network, the IMA max differential delay is set in such a way to satisfy the
UMTS network delayBudget.
As long as the E1/T1 composing the IMA Group:
- Used same path (amount of transmission node, transmission link length),
- Used same media (e.g.: cupper line) or different media offering same delay characteristics,
Then closed delay values are expected from the different E1/T1, the IMA max differential delay can be
set with a minimal value:
Rule: IubTEG_IMA_06
The IMA Differential Delay is set to 2 ms as long as same path and same medium used for the
E1/T1 composing the IMA Group.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 61/263
The atm OAM Information is bidirectional; it is carried once the ATM connection is established.
The atm OAM PDU are directly encapsulated within and ATM cell payload, without AAL (ATM
AdaptationLayer).
3.2.11.1
3.2.11.2
The atm OAM flows are called either F4 or F5 OAM flows according they are related to Vp or Vc
Connection.
For both the F4 and F5 ATM OAM flows may be specified an EndToEnd OAM flow and a Segment
oriented OAM flow:
- EndToEnd OAM flow:
The endToEnd OAM flow is transmitted between two adjacent ATM connection EndPoint
nodes. An atm Connection endpoint node is the node where the atm-User PDU is
encapsulated within the atm cell payload.
- Segment OAM flow:
The segment OAM flow is transmitted between two nodes at extremity of an OAM
boundary. OAM boundaries are configured (see [R49]).
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 62/263
NodeB
NodeB OAM Boundary
VCC
RNC
RNC
ATM
ATM
switch
switch
VCC / VPC
ATM
ATM
switch
switch
OAM Type
Function
Type
Reserved
CRC-10
5 bytes
4 bits
4 bits
45 bytes
6 bits
10 bits
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 63/263
OAM Type
0001
Function Type
Fault Management
0000
AIS
0001
RDI
0100
ContinuityCheck
1000
LoopBack
When LoopBack is activated, loopBack information is inserted in the OAM Cell Function specific field:
LoopBack Correlation
LoopBack indication ID
indication
Tag
1 bytes
4 bytes
16 bytes
Source ID
Unused
16 bytes
8 bytes
Where:
-
3.2.11.3
LoopBack indication: The source loopBack point fills this field with value: 0000 0001.
The destination loopBack point returns the value: 0000 0000.
Correlation Tag: Identifier of the loopBack invocation checked in loopBack source point
on reception of loopBack answer.
LoopBack Location ID: Identification of the node where loopback has to occur.
Source ID: Coded as an option, identification of the loopBack source point.
AIS:
Target of AIS (AlarmIndicationSignal) is to notify downstream endPoint node with a failure
that has occurred between endPoint nodes.
The AIS is sent downstream to all affected active atmConnections from the atmConnection
connection point (ATM cross connect or switch), which detects the atmConnection failure.
F4/F5 AIS OAM Cells triggers:
- SDH/PDH condition indicating physical link failure E.g. LOS.
- Reception of SDH MS-AIS, PDH AIS,
- Loss of Continuity at ATM layer detected by LoopBack or ContinuityCheck
when activated.
- LCD,
- IMA LinkGroup failure, when RNC IMA releases vcc, ATM layer generates AIS
OAM notification in both directions. RNC vcc NEP notifies application of vcc
failure, and application takes appropriate action.
- Moreover VC-AIS may be triggered by VP-AIS.
The AIS is sent at a frequency of 1 cell/s usually. AIS cells generation stops since failure
detection is removed.
The AIS generation feature is systematically activated when configuring a static
AtmConnection (PVC or PVP).
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 64/263
The AIS generation becomes an option when configuring dynamic AtmConnection PNNI
sPVC. This option is available at the source and destination of the PNNI sPVC through
attributes:
Atmif Vcc Dst aisGeneration,
Atmif Vcc Src aisGeneration.
Rule: IubTEG_ATM-OAM
It is highly recommended to activate aisGeneration attribute on source and destination of
sPvc dedicated to UserPlane and OAM traffic.
It is not recommended to activate aisGeneration attribute on source and destination of
sPvc dedicated to Iub CP and CCP traffic, since RNC-CN doesnt manage AIS signal.
The reason for activating aisGeneration attribute on source and destination of sPVCs dedicated
to UserPlane and OAM traffic, is that if a VCC part of an IMA group goes down, IuxIf/Path
associated to this VCC is informed about VCC failure and then doesnt allow calls on this Path.
When activating aisGeneration on source and Destination of a sPVC, failure of the sPVC, is a
trigger for aisGeneration on Permanent AtmConnections, the sPVC is switched on at the
source and destination:
PVC
F5 AIS
PNNI sPVC
ATM
Switch
PNNI sPVC
PNNI
AtmIf
AtmIf
AtmIf
AtmIf
sPVC CdPyNb,
AisGeneration
activated
PVC
ATM
Switch
F5 AIS
sPVC CgPyNb,
AisGeneration
activated
Upon receiving an F4/F5 AIS OAM cell, VPC/VCC endPoint node returns a F4/F5 RDI to
alert upstream intermediate and endPoint nodes that a failure has been detected downstream.
RDI:
RDI is used to return an indication to the upstream VP/VC EndPoint node that the received end
has detected an incoming section defect or is receiving AIS.
RDI is an upstream signal, whereas AIS is a downstream signal.
F4/F5 EndToEnd RDI is generated by a VP/VC EndPoint node, whereas F4/F5 Segment RDI
is generated by the segment endPoint node or a VP/VC EndPoint node.
The F4/F5 RDI signal is sent with a periodicity of 1 second as long as the defect persists.
After 3 second without reception of a F4/F5 RDI, the atm connection is brought back into
service.
F4/F5 RDI OAM Cells triggers:
- SDH/PDH condition indicating physical link failure E.g. LOS in Segment
boundary node or VPC/VCC EndPoint node.
- Reception of SDH MS-AIS, PDH AIS in a Segment boundary node or VPC/VCC
EndPoint node.
- Reception of F4/F5 AIS EndToEnd in a VPC/VCC EndPoint node,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 65/263
RDI frequency generation is usually 1 cell/s. RDI generation stops when failure detection is
removed.
Remark:
AIS generation attribute available when configuring dynamic AtmConnection PNNI sPVC,
allows activating/deactivating both AIS and RDI signals.
LOS Condition
UMTS
UMTS
UMTS
UMTS
ATM
ATM
ATM
ATM
ATM
ATM
F4/F5-AIS
P-AIS
TX
TX
RX
RX
PTE
PTE
TX
TX
RX
RX
MSTE
MSTE
RX
RX
TX
TX
TX
TX
RX
RX
PTE
PTE
RX
RX
TX
TX
PTE
PTE
RX
RX
TX
TX
MS-RDI
Ete F4/F5-RDI
Ete F4/F5-RDI
VPC/VCC
EndPoint node
Ete F4/F5-RDI
VPC/VCC
ConnectionPoint node
VPC/VCC
EndPoint node
LOS Condition
UMTS
UMTS
UMTS
UMTS
ATM
ATM
ATM
ATM
ATM
ATM
MS-AIS
TX
TX
RX
RX
PTE
PTE
RX
RX
PTE
PTE
RX
RX
TX
TX
Ete F4/F5-RDI
VPC/VCC
EndPoint node
TX
TX
TX
TX
RX
RX
RSTE
RSTE
RX
RX
TX
TX
Ete F4/F5-RDI
PTE
PTE
RX
RX
TX
TX
Ete F4/F5-RDI
VPC/VCC
ConnectionPoint node
VPC/VCC
EndPoint node
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 66/263
LOS Condition
UMTS
UMTS
UMTS
UMTS
ATM
ATM
ATM
ATM
TX
TX
RX
RX
PTE
PTE
ATM
ATM
TX
TX
RX
RX
PTE
PTE
RX
RX
TX
TX
TX
TX
RX
RX
RSTE
RSTE
RX
RX
TX
TX
PTE
PTE
RX
RX
TX
TX
Path-RDI
Ete F4/F5-RDI
VPC/VCC
EndPoint node
Ete F4/F5-RDI
VPC/VCC
ConnectionPoint node
VPC/VCC
EndPoint node
Detect failure within an ATM Network where nodes dont handle ATM OAM
signals: AIS, RDI.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 67/263
Rule: ATM-OAM_2
On Iub interface, ascertains that F4/F5 OAM AIS/RDI Signals are activated in each
node of the ATM backbone.
If F4/F5 OAM AIS/RDI Signals is not available on otherVendor nodes within the
ATM backbone, then loopBack must be activated on some RNC Iub
atmConnections.
On 16pOC3/STM1 FP, up to 50 loopBacks may be activated simultaneously.
Remark:
When activating loopBack in the RNC, it is assumed that intermediate equipments are
transparent for this signal and the far end support loopBack (ALU NodeB and
coreNetwork nodes support loopBack).
Moreover without LocationID value inserted in the loopBack signal, it is not
guaranteed that the far end node which answers is the expected one.
Within Passport based nodes, following MML are involved in LoopBack:
ATTRIBUTE AtmIf endToEndLoopback (eeLbk)
ATTRIBUTE AtmIf segLinkSideLoopback (segLkLbk)
3.2.11.4
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 68/263
- LoopBack.
Not Supported:
- PerformanceManagement,
- FaultManagement: ContinuityCheck.
NodeB:
On the reception of F4/F5 AIS the NodeB takes appropriate actions: alarm generation, send RDI.
The NodeB does not initiate the AIS signal since nodeB is an atm endPoint node not an atmSwitch.
The NodeB transmits an ATM OAM RDI signal on reception of ATM OAM AIS.
Nevertheless the NodeB is not yet able to initiate a RDI on reception of Transmission OAM defect
signal or since aware about LOS condition.
The NodeB autonomously configures the EndToEnd F4 OAM VCC (see 4 for release compliancy).
This OAM flow terminates at the VPC endpoint. EndToEnd F4 OAM VCC is identified by VCI=4.
The NodeB autonomously configures the Segment F4 OAM VCC (see 4 for release compliancy). This
OAM flow terminates at the OAM boundary. Segment F4 OAM VCC is identified by VCI=3.
The F4 OAM Vcc is configured with UBR serviceCategory to avoid bandwidth reservation.
The endToEnd F4 OAM VCC is initiated in the nodeB, and terminates in the RNC-IN
Segment F4 OAM VCC is initiated in the nodeB and terminates within the boundary of the VPC
segment. A VPC segment is under control of Network Administration. The POC may be the boundary
of the VPC segment, therefore node where Segment F4 OAM VCC terminates.
3.3
AAL2
3.3.1
ADDRESSING
Aal2 address is called A2EA [R41].
AAL2 addresses are not used on Iub, since ALCAP is not implemented.
3.3.2
ALCAP
The RNC Iub interface and the NodeB (iBTS are enhanced with the Alcap protocol.
Beside the oneNodeB still supports the Alcap.
The implemented Alcap is conformed to Q2630-2, with the exception:
- Q2630-2 aal2 connection modification procedure not supported (since achieved at RNL layer).
- Alternative routing not supported.
The Alcap uses the services of SAAL-UNI, one SSCOP connection is dedicated to the Iub Alcap.
Beside one SSCOP connection is established for the Nbap-c and one SSCOP connection is established
per Nbap-d.
One Alcap vcc is assigned to the Alcap SSCOP connection.
On the Iub interface, the Alcap is used to establish the aal2 bearer:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 69/263
NodeB
NodeB
RNC
RNC
NBAP/RadioLink Setup Request
NBAP/RadioLink Setup Response
TLA = nodeB A2EA + Binding Id1,
TLA = nodeB A2EA + Binding Id2 +
Q2630.2 ERQ
A2EA, SUGR = Binding Id1, PathId, CID, PathType, LC
Q2630.2 ECF
synchronisation
Q2630.2 ERQ
A2EA, SUGR = Binding Id2, PathId, CID, PathType, LC
Q2630.2 ECF
synchronisation
TEG
Figure 3-36, Iub Alcap call flow
The RNC may request several aal2 connection establishments when sending the Nbap/RL Setup Request
message to the nodeB.
Within the Alcap/ERQ/LinkCharacteristics parameter the RNC specifies:
- Maximum CPS-SDU bit rate
- Average CPS-SDU bit rate
- Maximum CPS-SDU size
- Average CPS-SDU size
The nodeB does not take into consideration these values
Within the Alcap/ERQ/pathType parameter the RNC inserts the requested aal2 qos to inform the
downstream aal2 node.
In the case of calls initiated on the Iur interface, the LinkCharacteristics values inserted in the alcap ERQ
sent on the Iub interface is determined by the driftRNC whereas the LinkCharacteristics values inserted
in the alcap ERQ sent on the Iur interface is determined by the servingRNC:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 70/263
NodeB
NodeB
DRNC
DRNC
SRNC
SRNC
RNSAP/RadioLink Setup Request
TEG
Figure 3-37, Iub & Iur Alcap call flow
3.4
IP
Since only IP services are only used by UMTS OAM plane, most of IP items are described in the UMTS
OAM plane subsection.
3.4.1
INVERSEARP
Reference: ARP [R68 & 66]
ARP (AddressResolutionProtocol) is used to infer the target layer2 address (e.g.: Ethernet) from the target
Layer3 address (e.g.: IP). The ARP is implemented neither in NodeB nor in Passport.
InverseARP is used to infer the target Layer3 address (e.g.: IP) from the target Layer2 address (e.g.:
ATM). InverseARP is implemented in NodeB and Passport.
InverseARP is a protocol defined in [R83 & R84]. InverseARP provides a method for dynamically
discovering the IP address configured at the remote end of the VCC (e.g. Passport VR PP IP@).
InverseARP uses services of AAL5. On the Iub interface, InverseARP traffic is carried in the OAM Vcc:
IP
ARP
LLC/SNAP
AAL5
ATM
Layer1
An IP node sends InvARP Request to the remote IP node, and expects to receive InvARP Reply with
remote Host IP address included. Then the ARP table is updated with the mapping between VCC and
Host IP address.
Within Passport based nodes, ARP table is updated periodically, according to the setting of MML.
Remark:
In the context of IP over ATM network, ARP is not invoked, only InverseARP is invoked.
Therefore this section treats only InverseARP.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 71/263
DHCP Request
DHCP Request
Ack
NodeB IP@
InvARP
Request
InvARP Reply
NodeB IP@
InvARP
Request
InvARP Reply
NodeB IP@
NodeB
NodeB
RNC-IN
RNC-IN
VCC OAM
NodeB
NodeB ARP
ARP Table:
Table:
ATM@
ATM@
Empty
Empty ifif PVC
PVC
VpiVci
VpiVci
OAM
OAM Vpi.Vci
Vpi.Vci
IP
IP
RNC
RNC IP@
IP@
RNC-IN
RNC-IN ARP
ARP Table:
Table:
@Age
@Age
xxx
xxx
ATM@
ATM@
Empty
Emptyifif PVC
PVC
VpiVci
VpiVci
OAM
OAM Vpi.Vci
Vpi.Vci
IP
IP
NodeB
NodeB IP@
IP@
@Age
@Age
xxx
xxx
Rule: IubTEG_ARP_1
Within UMTS nodes, on IP over ATM interfaces, it is recommended to activate InverseARP with exception
of Interface terminating on otherVendor nodes not supporting InverseARP.
On nodeB by default is activated dynamic ARP.
On RNC-IN, choice of Dynamic or Static InverseARP, impacts the PassPort ATM MPE component
configuration.
When configuring an ATM MPE component, type of encapsulation must be specified:
Encapsulation type values:
- IpVcEncapsulation: is set when only IP packets are inserted in ATM cells. No InverseARP packet
may be inserted. Therefore with such an encapsulation mechanism InverseARP can not be
configured, only StaticARP applies.
- LlcEncapsulation: is set when IP packets, InverseARP packets, and other kinds of packets are
inserted in ATM cells. Then an LLC and SNAP overhead is added to the encapsulated packet.
Within SNAP overhead two bytes are filled with the EthernetType to reflect the type of inserted
packet:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 72/263
Rule: IubTEG_ARP_2
When configuring ATM MPE,
EncapsulationType must be set with value LLC Encapsulation value.
Remark:
If StaticArp is configured for all nexthop Ip@ used on the PP, EncapsulationType=
IpVcEncapsulation may be configured.
Moreover on RNC-IN, when VPT is configured, DynamicARP works correctly only if ATTRIBUTE
AtmIf faultHoldOffTime is set to 0 on port where is configured the VPT.
Rule: IubTEG_ARP_3
If VPT activated, Set ATTRIBUTE AtmIf faultHoldOffTime = 0 on RNC port where is
configured VPT.
Passport MML for dynamic InverseARP:
COMPONENT Vr Ip Arp DynHostEntry (DynHost)
ATTRIBUTE AtmMpe encapType (etype)
Passport MML for static InverseARP:
COMPONENT Vr Ip Arp HostEntry (Host)
This component defines a static host entry in the ARP table.
ATTRIBUTE Vr Ip Arp Host permanentVirtualCircuitNumber (pvcNo)
This attribute specifies the number of the PVC for the static host entry.
ATTRIBUTE Vr Ip Arp autoRefreshTimeout
This attribute defines the timeout value, in minutes, which is assigned to updated ARP entries,
or newly created ARP entries.
The range for the timeout is 1 minute to 1440 minutes (24 hours). Default 5.
ATTRIBUTE Vr Pp IpPort arpNoLearn
When this attribute is set with Disable, the ARP table is automatically updated with
InverArpResponse.
3.4.2
SITELAN
3.5
IUB TOPOLOGY
Different topologies apply to the Iub interface according to:
- The RNC type: ATM RNC or Hybrid RNC,
- Backbone transport node: atmSwitch, sdh nodes, IP Router, ethernetSwitch,
- Backbone transmission interface: cupper, optical, Wave, Satellite, DSL
Related to the ATM RNC, the following options are considered for the choice of topology:
- NodeB transmission option:
- E1/T1 or Fractional E1/T1,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 73/263
If Fractional Rate E1/T1, do we have GSM BTS in the link as well (usage of
CES for cross connecting),
- MultiPCM or IMA,
Atm backbone:
- ThirdParty atm backbone, or backbone owns by the umts operator,
- Backbone dedicated to the UMTS or shared with others Telecom traffic
sources,
- Is the policing activated,
- Vc or vp switching,
- Atm signaling or permanent connections,
Sdh backbone:
- Either clearChannel or channelized access,
DSL technology,
Related to the Hybrid RNC, the following options are considered for the choice of topology:
Same options as for the atm RNC backbone and option related to the IP / Ethernet interfaces:
- IP backbone
- Ethernet backbone
- LAN / VLAN,
- DSL technology,
-
Below are presented some examples of network topologies on the Iub interface:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 74/263
3.5.1
ATM BACKBONE:
Iub
NodeB
E1
E1
NodeB
BTS
TDM E1
BSC
BSC
NodeB
TDM E1
NodeB
IMA
N*E1
7670
7670 ESE
ESE
NodeB
7670
7670 ESE
ESE
N*E1
oc3/stm1
RNC
RNC
N*E1
NodeB
N*E1
NodeB
7670
7670 ESE
ESE
N*oc3/stm1
NodeB
NodeB
NodeB
IMA
N*E1
IMA
N*E1
7670
7670 ESE
ESE
ATM
ATM
Backbone
Backbone
N*E1
NodeB
NodeB
3.5.2
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 75/263
Src
Pnni sPvc
PVC
nodeB1
nodeB1
atmSwitch
atmSwitch
IMA
E1
Src
E1
Dst
AESA
IMA
ADM
ADM
nodeB2
nodeB2
atmSwitch
atmSwitch
Atm loop
E1
IMA
nodeB3
nodeB3
E1
IMA
Src
atmSwitch
atmSwitch
Stm1
ADM
ADM
vc12
ADM
Stm1
ADM
Vc4
Vc12
7670
7670
RSP
RSP
RNC
RNC
Stm1
Vc4
Pnni sPvc,
alternative path
3.5.3
SDH RING
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 76/263
IMA /1
nodeB
nodeB
nodeB
nodeB
nodeB
nodeB
nodeB
nodeB
nodeB
nodeB
IMA /2
N * E1
Stm1
Vc4/Vc12
Sdh
Sdh
CC
CC
Stm1
63 vc12
Stm1
Vc4/Vc12
7670
7670
ESE
ESE
ADM
ADM
Stm1/oc3
Vc4
Stm1/oc3
Vc4/Vc12
ADM
ADM
RNC
RNC
7670
7670
RSP
RSP
RNC
RNC
Stm1/oc3
Vc4
N * E1
ADM
ADM
N * E1
7670
7670
ESE
ESE
Stm1
Vc4/Vc12
3.5.4
HYBRID UTRAN
The RNC is connected to an atm backhaul and to either IP or Ethernet backhaul.
Only Hspa interactive and background traffic may be transmitted through the RNC IP interface.
On the RNC ATM interface are transmitted: Signaling, oam, R99, Hspa streaming and as an option Hspa
I/B traffic.
On the NodeB side, the ATM traffic is handling either on multiPcm or IMA.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 77/263
R99 traffic,
Signaling,
Oam
Hspa stream.
Hspa I/B (opt)
RNC
RNC
CS
CS core
core
RNC
RNC
ATM
ATM
Backbone
Backbone
OC3
OC3
ATM
ATM
Backbone
Backbone
OC3
OC3
OC3
OC3
SGSN
SGSN
OC3
OC3
NodeB
NodeB
GE
GE GE
GE
SGSN
SGSN
IP
IPBackHaul
BackHaul
ATM
ATM
Backbone
Backbone
Hspa I/B
SGSN
SGSN
SGw
SGw
TEG
GE
GE
Router
Eth
Eth
Bridge
Bridge
Eth
Eth
Bridge
Bridge
NodeB
NodeB
NodeB
NodeB
NodeB
NodeB
SGSN
SGSN
NodeB
NodeB
NodeB
NodeB
Vlan z
GE
GE
Vlan u
Vlan v
Vlan x
RNC
RNC
Vlan x
Vlan y
Vlan z
Vlan y
Vlan u
Vlan v
NodeB
NodeB
TEG
3.5.5
ETHERNET TOPOLOGY
The Ethernet backhaul may present on the Iub interface, nevertheless at least one IP router must be
present. Therefore an ethernet backhaul may be inserted between the RNC and the IP backbone and
between the IP backbone and the NodeB.
Different Ethernet topologies may apply in such a way to guarantee the robustness against link, port node
failures:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 78/263
Eth
Bridge
RNC
GigE
6
Router
RNC
GigE
Eth
Bridge
GigE
Eth
Bridge
GigE
Eth
Bridge
GigE
RNC
Eth
Bridge
GigE
Router
GigE
RNC
Eth
Bridge
GigE
Router
GigE
RNC
Eth
Bridge
GigE
Router
GigE
RNC
GigE
Eth
Bridge
Router
Eth
Bridge
Router
Eth
Bridge
Router
Router
Router
3.6
RNC ATM
This section covers the ATM RNC. A new section is dedicated to the Hybrid RNC.
The ATM RNC is populated with the 16pOC3/Stm1 FP and provides atm accesses on all the UTRAN
interfaces.
The hybrid RNC is populated with both the 16pOC3/Stm1 FP and the 4pGE FP and provides both atm
and IP accesses on the Iub interfaces, atm accesses on the IuCS and Iur interfaces, and both ATM and IP
on the IuPS interface.
Rule: IubTEG_hybridRNC
On the Iub, the IP interface when present is dedicated to Hsdpa and Hsupa interactive/Background
whereas the atm is dedicated to R99, signaling, Hspa streaming, oam and as an option Hspa
interactive/Background.
3.6.1
ASIC
The different Passport FP, are based either on APC or AQM trafficManagement ASIC. The type of ASIC
determines the FP trafficManagement behavior.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 79/263
3.6.2
FP
interCard APS:
1+1 inter-card line APS. APS configured for lines physically connected to different cards, also
called dual-FP APS.
The Line switching time in the case of a fault (SF/SD on the line) is within 50 ms.
The value standard indicates that 1+1 linear APS is used, as described in the
recommendation [R80] and [R33 7]
The value g841AnnexB indicates that optimized 1+1 bidirectional switching is used, as
described in the standard [R33 Annex B].
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 80/263
3.6.2.1.2.1
The objective of AtmIf ConnMap attributes is the reservation of Vci range for vcc. The Vci reservation is
done for vcc identified with Vpi = 0 on one hand and for vcc identified with a nonZero Vpi on other hand.
The AtmIf ConnMap attributes are set per port.
AtmIf ConnMap ov Attribute list:
- ATTRIBUTE AtmIf ConnMap Ov numVccForVpiZero (nZVcc):
Reservation of the Vci range for vcc identified with a Vpi = 0.
The Vci range = [0 (nZVcc-1)].
The value assigned to this attribute must take into account the Vci values: 0 to 31 reserved by
ITU.
The allowed values are power of 2.
The attribute range is (0 16384)
- ATTRIBUTE AtmIf ConnMap Ov numNonZeroVpisForVcc (nVpis):
Setting of the supported contiguous Vpi values for vcc.
The attribute range is [0, 255] for UNI atmInterface, and [0, 4095] for NNI atmInterface.
- ATTRIBUTE AtmIf ConnMap Ov firstNonZeroVpiForVcc (firstVpi):
Setting of the first nonZero Vpi value used for vcc.
If nVpi = 0 then this attribute is ignored.
The attribute range is [1, 255] for UNI atmInterface, and [1, 4095] for NNI atmInterface.
-
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 81/263
nZVcc
511
nVcc
255
32
1024
3
4
firstVpi
18 19 20
firstVpi+nVpi
255 UNI
VPI
4096 NNI
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 82/263
3.6.2.1.2.2
The Lp Eng Arc ov and Lp Eng Arc Apc ov attributes provide the ability to set the FP and APC capacity
in terms of amount of atmConnections.
Lp Eng Arc ov Attribute list:
- Lp Eng Arc Ov connectionPoolCapacity (connCap)
The attribute specifies the maximum number of unspared (no APS) connectionResources.
UMTS RNC context: since all 16pOC3/Stm1 FP ports are configured with Laps, unprotected
connectionResources are used only for test purpose.
-
In the UMTS RNC context, the 16pOC3/STM1 FP handles both ATM and IP traffic (IPRts>0).
In this context of application, the FP capacity is:
3.6.2.1.2.3
ATMIF CA ATTRIBUTES:
The AtmIf CA attributes provide the ability to set the port capacity in terms of amount of
atmConnections.
Moreover atmIf CA attributes are used for setting the port atmInterfaceType.
The AtmIf CA attributes are set per port.
AtmIf CA Attribute list:
- ATTRIBUTE AtmIf CA maxVcc (vcc)
Setting of the maximum amount of vc Connections that can be configured on a port.
It encompasses both independent vcc and vcc configured under a VPT.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 83/263
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 84/263
The CA Attribute values consumed FP resources. Therefore check the APC connectionResource
UsageRate:
The formula 10 is valid for basicVPT, and not valid for standardVPT (StandardVPT is not
available on 16pOC3/Stm1 FP).
Remark:
The CA attributes: minAutoSelectedVpi and maxAutoSelectedVpi are not introduced in the TEG
since not used in the RNC.
The VPC space delimited by [minAutoSelectedVpi,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 85/263
3.6.2.1.3 QOS:
-
FP Scheduler:
The 16pOC3/STM1 FP supports 5 EP: EP0, EP2, EP3, EP4 and EP7.
The 16pOC3/STM1 FP supports 4 classQueues .
The MBG is configured against the EP2, EP3, EP4 and EP7; no MBG configured against the EP0.
The 16pOC3/STM1 FP first allocates to each EP its minimum bandwidth guaranteed and then
allocates the remaining bandwidth among the different EP according to a strict priority.
The MBG has precedence over the EP0 and EP1.
This type of scheduling is referred to as Priority Guaranteed Queuing (PGQ).
DSD instance
multiService
DSCP
CSx, EF, AFxy, DE
classSelector
CSx
assuredForwarding
AFxy, CS6, DE
packetVoice
wirelessUmts
Custom
CS6, DE
Notes: x is in the range [0 to 7] for the CS DSCP, [1 to 4] for the AF DSCP, and y in the
range [1 to 3]. The CS0 is equivalent to Default DSCP then removed from the text.
UMTS
UP
CP
TrafficClass
Conversational
Signaling
Streaming
ARP
1, 2, 3
na
0
1
2
0
1
UP
Interactive
Background
2
0
1
2
0,1,2
THP
na
1
2
1
2
1
2
3
na
DSCP
trafficClass
sc4q
EP
MBG%
ipCos
SC
CS7
CS6
EF
critical
network
premium
77
cbr
platinium
18
rtVbr
nrtVbr
ubr
AF41
AF42
AF43
AF31
AF21
AF32
AF22
AF33
AF23
AF11
AF12
AF13
DE
gold
silver
gold
silver
gold
silver
bronze
bronze
bronze
Standard
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 86/263
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 87/263
3.6.2.2.2.1
QOS
MBG:
The MBG parameter configured against nonAbsolute EP is taken into consideration by the
ClassScheduler.
The MBG is set through the command: ATTRIBUTE AtmIf Ep minimumBandwidthGuarantee
(minBw).
The parameter is set with either with:
- a MBG value in the range [0, 100] or
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 88/263
The mix of priority and MBG provisioning is not supported on the 16pOC3/Stm1 Atm/Pos
FP. What is supported is either specifying the priority option for all EPs, or the explicit
configuration of the MBG value for all used EPs used on one atmInterface.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 89/263
- The default weigh assigned by the Passport to the EP for case of MBG = Priority,
The following MBG values are suggested as default values:
rtVbr
nrtVbr
Ubr
EP2
EP3
EP4
EP7
# Used
non absolute
EP
1st EP
1
2
100
99
90
77
18
2d EP
3d EP
4th EP
100
100
100
100
QOS/Discard mechanism:
Same mechanism as for the AQM based FP.
Four discardPriority thresholds are set on a connection queue, Default values:
DP0
Threshold
100%
DP1
90%
DP2
75%
DP3
35%
The discard thresholds apply to the common and the perVc queues.
The four DP thresholds are not configurable.
The mapping of (SC+CLP) to DP (DiscardPriority) is hardcoded:
Rule: IubTEG_16pOC3/Stm1 atm/Pos_9
DP
Cbr
Clp0
DP1
Clp1
DP3
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 90/263
rtVbr
DP1
DP3
nrtVbr
DP2
DP3
Ubr
DP3
DP3
WiseDiscard:
Within each 4 CC (congestionControl level), are set the EPD, PPD, and EFCI thresholds:
Rule: IubTEG_16pOC3/Stm1 atm/Pos_10
The CC, EPD, PPD and EFCI thresholds are hardcoded with the following values:
perVc Queue
Thresholds
CCO
DP
100%
PPD
99%
EPD
90%
CC1
90%
89%
80%
CC2
75%
74%
65%
CC3
35%
34%
25%
EFCI
35%
Remark:
On the AQM based card, the EPD thresholds are configured through the epdOffset attribute,
which is not supported by the GQM.
CLP:
Context of IP over atm interface:
The atm Cell CLP value is determined by the ATM service category (SC) and the Drop
Precedence of the IP packet that reached the VR that has the DSD provisioned on. The DP of
IP packets can have a value of low (1), medium (2) or high (3). In our case the IP packets
originate from the PMC-RAB, therefore the DP is set there.
Here below the CLP value according to the SC and DP:
serviceCategory
Cbr
Cbr
Cbr
rtVbr
rtVbr
rtVbr
nrtVbr
nrtVbr
nrtVbr
Ubr
Ubr
Ubr
dropPrecedence
1
2
3
1
2
3
1
2
3
1
2
3
Tx CLP
0
0
1
0
0
1
0
0
1
1
1
1
Conclusion:
- The ubr atmConnection cells are always tagged,
- The cbr and vbr atmConnection are tagged only for dropPrecedence 3.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 91/263
3.6.2.2.2.2
TRAFFICMANAGEMENT:
3.6.2.2.2.3
AAL5:
3.6.2.2.2.4
OAM:
According to I610,
PM and CC not supported,
3.6.2.2.3 IP CHARACTERISTICS:
The FP IP forwarding capacity: 2,5 Gb/s .
FP characteristics:
The FP supports:
- Static routing,
- MPE,
- inverseARP,
- LocalMedia.
- ECMP ,
The FP does not support:
- DHCP relayAgent,.
QOS:
The IPCos parameter is removed and replaced by the DSCP parameter.
As a result the DSCP is mapped directly to a SC. The removal of IpCos parameter must be
done before introducing the 16pOC3/Stm1 POS/Atm FP in the RNC.
VR/n
|--------DiffServ/I
|--------IP
|
(new)
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 92/263
ECMP:
The FP supports flow based ECMP with up to 3 nextHops.
To activate the IP route traffic loadSharing amongst several paths:
- At least 2 nextHops and up to 3 nextHops are configured under the IP route,
- The ecmpMode parameter is set to perFlowEnh.
Rule: IubTEG_16pOC3/Stm1 atm/Pos_12
ecmpMode = perFlowEnh when ECMP is required.
3.6.2.2.4 TRAFFICMEASUREMENT
All the Sonet and SDH spooled statistics from the Passport are supported,
All the Atm interface and Vpt spooled statistics from the Passport are supported.
3.6.2.2.5 HARDWARE:
-
3.6.2.3 MSA32 FP
MSA32E1 FP is a PP7k card. It is inserted in the Mss7k to provide E1/DS1 connectivity on Iub interface, and as
an option STM1 connectivity on RNC / Mss7k interface.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 93/263
3.6.2.3.3.1
The MSA32 FP ATM TrafficManagement characteristics are those from the AQM.
3.6.2.3.3.2
-
IMA CHARACTERISTICS:
Unchannelized E1 ports only may participate in IMA linkGroup.
Fractional rate E1s are not allowed.
ATM UNI, PNNI are all supported over IMA. In basic configuration ATM UNI is configured on
IMA AtmIf,
The MSA32 supports up to 28 E1 or 30 DS1 IMA ports per FP, distributed across the two
Makers (block of ports #0-15 or 16-31) as up to:
- 14 E1 ports in up to 7 IMA LG per Maker, or
- 13 E1 ports in up to 13 IMA LG per Maker.
- 15 DS1 ports in up to 7 IMA LG per Maker, or
- 13 DS1 ports in up to 13 IMA LG per Maker.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 94/263
Ports #30-31 can be used for IMA if part of an IMA LG with ports in the range 16-29.
From 1 to 8 ports per IMA LG.
All ports in an IMA link group must be in same port-block (Maker).
Do not mix services on same port-block as IMA:
When IMA is activated on a port block, other services are not supported on that port block:
Mixing of IMA with e.g. single port ATM or AAL1 CES is not recommended on the same port
block (port 0-15, 16-31).
In terms of link selection criteria, the MSA32 FP supports only the delay metric (leastDelay) and
not the bandwidth metric (maximumBandwidth).
Compliancy:
- IMA1.0 vs. IMA1.1: Technically MSA32 supports both. An MSA32 IMA port first comes
up in IMA1.1 mode then negotiates the remote end; if it is IMA1.0, then MSA32 changes to
IMA1.0 to match. Otherwise it stays in IMA1.1 mode and runs successfully. MSA32
display commands always show the port running in IMA1.0 mode.
IMA Clock Modes:
- The ports within an IMA group may use the Module, Line or a combination of the two for
the transmit clocking configuration. The clocking options in the IMA feature are:
- Common Transmit Clock mode (CTC) and
- Independent Transmit Clock mode (ITC).
- If the shelf clock is available the default for clocking source is Module.
For fully loaded UTRAN Mss7k, it is expected that number of ATM Vcc should be in range of 200 - 300 per FP,
therefore recovery time should not exceed 2 min. The establishment of SPVCs should not increase this recovery
time.
Within the Mss7k, one FP is designated as spare FP, whereas others are designated as Main FP, by means of
configuration.
Rule: IubTEG_RNC-MSA32 FP_3
The MSA FP configured for sparing function, must be one without STM1 connectivity to RNC.
The connectivity of the Mss7k is reduced since one MSA FP is reserved for acting as spare FP. The Mss7k is
then populated with up to 6 effective MSA32 FP.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 95/263
Working Line
16pOC3/Stm1
16pOC3/Stm1 FP
FP
RNC
Protected Line
16pOC3/Stm1
16pOC3/Stm1 FP
FP
STM1
1 spare FP:
66
77
88
99 10
10 11
11 12
12 13
13 14
14 15
15
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
SPARING
SPARING
55
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
44
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
33
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
6 main FP:
22
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
11
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
00
MSA32 E1/Stm1
E1/Stm1 FP
FP
MSA32
MSS7K
7 * 32 E1
SparingPanel
SparingPanel
6 * 32 E1
3.6.2.6 2 P STM1 E CH FP
(Reference [R254, R255 & R40])
The 2pStm1 e ch FP is a PP7k card.
This FP may be introduced in the Mss7k when NodeBs and RNC traffic transits through a SDH backbone.
It provides 2 STM1 ports electrical and channelized.
According to ITU, 63 E1 links are included within a STM1 Channelized. Each E1 link is encapsulated within a
VC12; 63 VC12s are encapsulated within a VC4. Within a VC4, each VC12 is identified by a triplet value
called: (k, l, m).
Therefore the 2pSTM1e Ch FP supports up to 126 E1 links.
The 2pSTM1e Ch FP doesnt handle IP.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 96/263
If RNC-AN is populated with four 2pSTM1e Ch FPs, then 8 slots are reserved.
Six slots remain available for RNC / Mss7k interface. These six slots may be populated with three
MSA32E1/STM1 FPs reserving 6 slots, indeed providing 3 STM1 links, or with three 2pOC3 FP reserving 3
slots.
Rule: IubTEG_RNC-2pStm1Ch_1
Eight Mss7k slots are reserved for the 2pSTM1e Ch FPs, in such a way to be able to provide Iub up to
4 STM1 Channelized links secured by sparingPanel.
When configuring a VC12, on one SDH link, a (k, l, m) triplet value is assigned to the VC12. This triplet value
identifies the VC12 within the VC4.
- k is in the range [1, 2, 3],
- l is in the range [1, , 7] and
- m is in the range [1, 2, 3].
From the VC12 assigned triplet value, the 2pStm1e Ch FP, computes the AQM internal port number using the
following formula:
Rule: IubTEG_RNC-2pStm1Ch_2
AQM port number for an isolated E1:
AQM InternalPort number = (k-1) * 21+ (l-1) + (m-1) * 7
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 97/263
k
1
1
1
1
1
1
1
l
1
2
3
4
5
6
7
m
1
1
1
1
1
1
1
AQM InternalPort #
0
1
2
3
4
5
6
# SDH
1
1
1
1
1
1
1
k
1
1
1
1
1
1
1
l
1
2
3
4
5
6
7
m
1
1
1
1
1
1
1
AQM InternalPort #
0
1
2
3
4
5
6
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
2
3
4
5
6
7
2
2
2
2
2
2
2
7
8
9
10
11
12
13
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
2
2
2
2
2
2
2
7
8
9
10
11
12
13
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
2
3
4
5
6
7
3
3
3
3
3
3
3
14
15
16
17
18
19
20
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
3
3
3
3
3
3
3
14
15
16
17
18
19
20
0
0
0
0
0
0
0
2
2
2
2
2
2
2
1
2
3
4
5
6
7
1
1
1
1
1
1
1
21
22
23
24
25
26
27
1
1
1
1
1
1
1
2
2
2
2
2
2
2
1
2
3
4
5
6
7
1
1
1
1
1
1
1
21
22
23
24
25
26
27
0
0
0
0
0
0
0
2
2
2
2
2
2
2
1
2
3
4
5
6
7
2
2
2
2
2
2
2
28
29
30
31
32
33
34
1
1
1
1
1
1
1
2
2
2
2
2
2
2
1
2
3
4
5
6
7
2
2
2
2
2
2
2
28
29
30
31
32
33
34
0
0
0
0
0
0
0
2
2
2
2
2
2
2
1
2
3
4
5
6
7
3
3
3
3
3
3
3
35
36
37
38
39
40
41
1
1
1
1
1
1
1
2
2
2
2
2
2
2
1
2
3
4
5
6
7
3
3
3
3
3
3
3
35
36
37
38
39
40
41
0
0
0
0
0
0
0
3
3
3
3
3
3
3
1
2
3
4
5
6
7
1
1
1
1
1
1
1
42
43
44
45
46
47
48
1
1
1
1
1
1
1
3
3
3
3
3
3
3
1
2
3
4
5
6
7
1
1
1
1
1
1
1
42
43
44
45
46
47
48
0
0
0
0
0
0
0
3
3
3
3
3
3
3
1
2
3
4
5
6
7
2
2
2
2
2
2
2
49
50
51
52
53
54
55
1
1
1
1
1
1
1
3
3
3
3
3
3
3
1
2
3
4
5
6
7
2
2
2
2
2
2
2
49
50
51
52
53
54
55
0
0
3
3
1
2
3
3
56
57
1
1
3
3
1
2
3
3
56
57
58
58
59
59
60
60
61
61
62
62
AQM 2
# SDH
0
0
0
0
0
0
0
AQM 3
AQM 1
AQM 0
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 98/263
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 99/263
Remark:
-
The AQM internalPort number [57-62] can not be assigned to an IMA LG.
Nevertheless the E1 links associated to AQM internalPort number [57-62] may be included in an
IMA LG.
The AQM internalPort assigned to the IMA LG, may be an AQM internal port associated to one E1
belonging to this IMA LG, or to another IMA LG. For simplicity, the rule above suggests to assign
to the IMA LG an AQM internalPort already associated to an E1 belonging to this IMA LG.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 100/263
The CES connections may be configured only on AQM1 and AQM3; no CES connection configured on
AQM0 and AQM2.
AAL1 CES warm standby (< 16 sec), the aal11 CES is released when sparing occurs, and
services need to be reconnected
IMA warm standby (< 32 sec), ima/atm Vcc is released when sparing occurs, and
services need to be reconnected
2pOC3 Clear FP
10
11
SparingPanel
Stm1
12
Stm1
13
14
15
16
CP2
2pOC3 Clear FP
2pSTM1 e Ch
SparingPanel
2pSTM1 e Ch
2pSTM1 e Ch
SparingPanel
2pSTM1 e Ch
2pOC3 Clear FP
PP7K:
2pStm1 Ch
SparingPanel
CP2
SparingPanel
Stm1
Stm1
3.6.2.8 2POC3 FP
The 2pOC3 FP is a PP7k card.
This FP is used as an alternative to the MSA32 Stm1 FP, for interface with the RNC-IN.
Three 2pOC3 FP may be populated on the Mss7k, in such a way to have on RNC/Mss7k interface 3 STM1 Links
APS protected.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 101/263
PDC:
Each PDC provides a management functions for that one DCPS FP card only.
Moreover the PDC is in charge of handling the SaalNNI and the Sctp.
The SaalNNI and Sctp traffic is distributed over all the PDC with exception of those running
PMC-NI.
Each PDC is configured with one external IP@ which is used as the RNC CP IP@ on the
IuPS interface.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 102/263
PMC-OMU:
The OAM functionality is implemented on 2 PMC-OMU components located on different
PSFP cards.
The PMC-OMU handles also the CBS traffic (IuBC).
The sparing scheme is 1+1. The PMC-OMU switch produces no interruption of service except
in case of double fault scenarios.
PMC-M:
The PMC-M hosts the CID management and the Alcap for Iub Iur and IuCS interfaces.
The RNC is populated with two PMC-M components, working in 1+1 redundancy scheme.
Two PMC-M components reside on different PSFP cards.
The PMC-M switch produces no interruption of existing calls except in case of double fault
scenarios. New calls cannot be initiated for approximately 5 seconds.
PMC-NI:
The MTP3b and SCCP protocols are implemented on two PMC-NI components located on
different DCPS FP cards.
Moreover the PMC-NI handles the locationServices traffic (IuPC).
The RNC is populated with two PMC-NI components, working in 1+1 redundancy scheme.
The sparing scheme is 1+1. The PMC-NI switch produces no interruption of existing calls or
service except in double fault scenarios.
The PMC-NI is PSFP cards 2 and 3.
PMC-TMU:
The PMC-TMU is in charge of processing UMTS protocols: RANAP, RNSAP, and NBAP
(Supports RRM, RRC, and aal2Link CAC).
Moreover PMC-TMU is in charge of the UMTS heartBeat.
Up to 14 PMC-TMU components in the ATM RNC, up to 12 PMC-TMU in the Hybrid RNC
are spread over all the PSFP/DCPS FP.
The sparing scheme is N+1 if 7 or fewer PSFP and otherwise N+2 spared.
If a PMC-TMU fails, the control planes for the NodeBs and cells managed by that TMU are
automatically taken over by one of the spare PMC-TMU within 30 seconds but individual
Radio Links are lost. Individual calls are managed by all the PMC-TMUs in load sharing
mode. If a PMC-TMU fails the calls on that PMC-TMU are lost.
PMC-RAB:
The UMTS user plane is handled in up to 40 PMC-RABs within an ATM RNC, in up to 32
PMC-RABs within an Hybrid RNC spread over all the PSFP in load sharing mode.
Cell common channel user plane functionality is spared so if one PMC-RAB fails its cell
common channel user plane load is taken over by up to 5 other PMC-RAB on other DCPS FP
cards with no loss of common channel service.
Individual call user planes are managed by all the PMC-RAB in load sharing mode.
If a PMC-RAB fails the calls on that PMC-RAB are lost.
Each PMC-RAB is configured with one external IP address used as the RNC IuPS UP IP@.
PMC-PC:
Up to 12 PMC-PC within an ATM RNC and up to 10 PMC-PC within an Hybrid RNC
PMC-PC sparing scheme: N+1.
RNC ATM Interface, PMC-PC function:
The PMC-PC is the aal2 Path point of termination.
The PMC-PC achieves the aal2 to UDP conversion.
The Aal2 paths and the PMC-PC functionality is spared so if one PMC-PC fails its
paths and load is spread over up to 5 other PMC-PC located on other DCPS FP cards
without interruption of cell common channels or calls in progress.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 103/263
RNC
0&1
8&9
10
11
12
13
14
15
DCPS
DCPS 66 DCPS
DCPS 77 DCPS
DCPS 88 DCPS
DCPS 99 DCPS
DCPS 10
10 DCPS
DCPS 11
11
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
Pdc
Pdc
saalNni
saalNni
RAB
RAB
RAB
RAB
OMU
OMU
OMU
OMU
RAB
RAB
RAB
RAB
TMU
TMU
TMU
TMU
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
PMC-M
PMC-M PMC-M
PMC-M
16pOC3 FP
16pOC3 FP
CP3
CP3
DCPS
DCPS 00 DCPS
DCPS 11 DCPS
DCPS 22 DCPS
DCPS 33 DCPS
DCPS 44 DCPS
DCPS 55
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
NI
NI
NI
NI
RAB
RAB
RAB
RAB
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
TEG
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 104/263
Up to 32 PMC-RAB.
RNC
0&1
8&9
DCPS
DCPS 00 DCPS
DCPS 11 DCPS
DCPS 22 DCPS
DCPS 33 DCPS
DCPS 44 DCPS
DCPS 55
10
11
12
13
14 & 15
DCPS
DCPS 66 DCPS
DCPS 77 DCPS
DCPS 88 DCPS
DCPS 99
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
Pdc
RAB
RAB
RAB
RAB
OMU
OMU
OMU
OMU
RAB
RAB
RAB
RAB
TMU
TMU
TMU
TMU
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
4pGE FP
4pGE FP
PMC-M
PMC-M PMC-M
PMC-M
16pOC3 FP
16pOC3 FP
CP3
CP3
Pdc
Pdc
0
3
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
NI
NI
NI
NI
RAB
RAB
RAB
RAB
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
PC
TEG
Rule: IubTEG_PSFP
The RNC supports up to 10 PSFP/DCPS FP since populated with two 16pOC3 FP and two 4pGE FP.
3.6.3
RNC CAPACITY
The RNC capacity depends on the type and amount of component it is populated with and parameter
setting.
Parameter:
The setting of the RncIn/hardwareCapability component determines the RNC capacity:
Rule: IubTEG_RNC-Capacity_
- Set hardwareCapability = allPktServSP2FullDim when the RNC is populated with DCPS, CP4
and 16pOC3 MS3 FP and as an option gigaEth cards.
- Set hardwareCapability = allPktServSP2 when the RNC is populated with DCPS or PSFP, CP3
and 16pOC3 MS3 FP or classical 16pOC3 FP cards.
- Set hardwareCapability = all6mPktServ when the RNC is populated with PSFP, CP3 and
16pOC3 MS3 FP or classical 16pOC3 FP cards.
Avoid:
- hardwareCapability= allPktServSP2FullDim when RNC is populated with CP3.
- hardwareCapability= allPktServSP2 or all6mPktServ when RNC is populated with
CP4.
Capacity:
- When the RNC is populated with: DCPS, CP4, and MS3 and the hardwareCapability parameter =
allPktServSP2FullDim:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 105/263
UA5-1-2
12 PSFP
4 DCPS
6 DCPS
8 DCPS
10 DCPS
12 DCPS
# nodeB
200
600
1000
1400
2000
2400
# cells
1200
612
1020
1428
2040
2448
- When the RNC is populated with: DCPS, CP3 or CP4 and the hardwareCapability parameter =
allPktServSP2:
UA6, hardwareCapability parameter allPktServSP2.
UA5-1-2
12 PSFP
4 DCPS
6 DCPS
8 DCPS
10 DCPS
12 DCPS
# nodeB
200
360
600
720
800
1200
# cells
1200
360
600
720
800
1200
- When the RNC is populated with: PSFP, CP3 and the hardwareCapability parameter = all6mPktServ:
UA6, hardwareCapability parameter all6mPktServ.
UA5-1-2
3.6.4
12 PSFP
4 PSFP
6 PSFP
8 PSFP
10 PSFP
12 PSFP
# nodeB
200
360
600
720
800
1200
# cells
1200
360
600
720
800
1200
AAL2 COMPONENTS:
3.6.4.1 AAL2IF
All the aal2 Paths configured between the RNC and an adjacent aal2 point node are configured under an
aal2If instance.
Rule: IubTEG_RNC aal2 Components_0
The ipIf component instance must be unique within the RNC.
The ipIf component instance range: [1, 5000] is reserved for the Iub interface
The adjacent aal2 Point is either a NodeB or an aal2Switch.
Remark: The RNC supports aal2Switch over the iub interface under some condition, see 3.6.14 .
Therefore an aal2If instance is assigned to each nodeB, within an aal2If instance are grouped all paths
serving the NodeB.
The bwPool is an optional component of the aal2If.
3.6.4.2 IUBIF:
Moreover an IubIf instance is assigned to each NodeB. The aal2if and the IubIf instances assigned to the
nodeB are linked together within the RNC.
Rule: IubTEG_RNC aal2 Component_1
On Iub interface, there is a one to one relation between aal2If and IubIf.
The aal2if instances linked to the IubIf instances cannot be assigned to any other aal2 interfaces: IucsIf,
IurIf or IubIf.
Up to 2400 iubIf are going to be reserved to identify up to 2400 nodeB.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 106/263
3.6.4.3 BANDWIDTHPOOL:
Furthermore the RNC introduced in the previous release the notion of bandwidthPool defined as a group
of aal2Paths amongst all the paths terminating on one specific nodeB. Then a bandwidthPool is a subset
of an aal2if.
The bwPool is optional under an aal2If component.
The bandwidthPool concept has been specified within the RNC to distinguish the nodeB aal2Paths
configured over different NodeB Transport media, e.g.:
- The NodeB paths configured over two different IMA linkGroups are grouped under two different
bwPools,
- The NodeB paths configured over different E1 (mode xPcm) are grouped under different bwPools,
- The NodeB paths configured over an IMA linkGroups and the NodeB paths configured over E1
(mix of xPcm and IMA mode) are isolated into different bwPools.
Moreover the aal2 paths configured over a nodeB IMA linkGroup may be distributed over different
bandwidthPools.
The composition of a bandwidthPool with a set of Path is done by configuration.
The bandwidthPool concept has been extended to takes into consideration:
- The nodeB ip interface, see 3.7.11. On the RNC side, the bandwidth reserved for a nodeB ip
interface and the bandwidth reserved for a nodeB atm interface are isolated into different
bandwidthPools.
- The utranSharing: The traffic from the different PLMN sharing the utran may be as an option
isolated into different bandwidthPool.
- Asymmetrical traffic.
Rule: IubTEG_RNC aal2 Component _2
- Up to 16 bandwidthPools per aal2If,
- Each bandwidthPool may be populated with up to 16 aal2 paths.
- Within an aal2If the pathIds must be unique whatever they belong to same or different bwPools.
Remark: Even if the aal2If supports up to 16 bandwidthPool, 8 bandwidthPools are enough to cover case
of NodeB configured with 8 E1 in xPcm mode.
The bandwidthPool granularity is taken into consideration by the congestionManagement mechanism for
regulating the downlink traffic.
Rule: IubTEG_RNC aal2 Component_3
Each bwPool must be associated to a congestionManagement instance.
Definition:
- TrafficType: RNC classification of the umts traffic based on the: trafficClass and the RbSetQos
information.
Different types of bandwidthPool:
- primaryForTrafficType bandwidthPool:
The primaryForTrafficType bandwidthPool is supported only on the Iub interface and may be
specified for both the atm and the ip interfaces.
A limited range of UMTS trafficTypes is assigned to such a bandwidthPool: only the Hspa I/B
traffic can be handled over a primaryForTrafficType bwPool.
Within an ATM primaryForTrafficType bwPool, up to 3 qos streams: qos1, qos2 and qos3 may
be configured. The CM/backPressure applies to each 3 qos streams.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 107/263
sharedForAllTrafficTypes bandwidthPool:
A sharedForAllTrafficTypes bandwidthPool may be specified only on the atm interfaces.
A wide range of UMTS trafficTypes selects such a bandwidthPool.
Within a sharedForAllTrafficTypes bwPool, the CM/backPressure applies to all the qos
streams with exception of the qos0 stream.
Each bwPool is linked to one transportMap, see 3.6.9. Within the transportMap is specified the bwPool
properties:
- TransportMap/Preference specifies the bwPool type either sharedForAllTrafficTypes or
primaryForTrafficType,
- Transportmap/transportServiceEntry specifies the trafficTypes assigned to the bandwidthPool.
Rule: IubTEG_RNC aal2 Component_6
Each bwPool must be associated to a transportMap instance with the appropriated
interfaceType.
Exemple of one atm sharedForAllTrafficTypes bwPool and one atm primaryForTrafficType bwPool
associated to one nodeB:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 108/263
RNCIN
RNCIN / IubIf
aal2If i
TransportMap i
interfaceType: Iub
BwPool/x
preference: sharedForAllTrafficTypes
transportServiceEntries:
[TC=conv, RbSetQos=0, ]
=> qos0
[TC=stream, RbSetQos=1+2, ]
=> qos1
[TC=interact, RbSetQos=1, ]
=> qos2
=> qos3
qos0
path
qos1
path
qos2
path
qos3
path
TransportMap j
interfaceType: Iub
BwPool/y
preference: primaryForTrafficType
transportServiceEntries:
[TC=interactive, RbSetQos=2, ] => qos3
qos3
path
TEG
Figure 3-51, NodeB with two atm bwPools
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 109/263
RNCIN
RNCIN / IubIf
aal2If i
TransportMap i
interfaceType: Iub
BwPool/x
preference: sharedForAllTrafficTypes
qos0
path
qos1
path
qos2
path
qos3
path
transportServiceEntries:
[TC=conv, RbSetQos=0, ]
=> qos0
[TC=stream, RbSetQos=1+2, ]
=> qos1
[TC=interact, RbSetQos=1, ]
=> qos2
=> qos3
ipIf i
interfaceType: Iub
preference: primaryForTrafficType
BwPool/y
transportServiceEntries:
ipFlow/i
qos 3
TEG
Figure 3-52, NodeB with one atm bwPools and one ip bwPool
Topology
bwPool/Preference
Transport
Comments
N * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Atm
1 * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Ip
1 * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Atm
1 * sharedForTrafficTypes
Atm
N*E1+IMA
Hybrid Iub
One primaryForTrafficType bwPool associated to the nodeB Ethernet link.
2 IMA
1 IMA
UtranSharing:
Per definition a PLMN Common bwPool is a bwPool shared by all the PLMN sharing the Utran
whereas a PLMN specific bwPool is a bwPool dedicated to one PLMN sharing the Utran.
A PLMN Common bwPool and a PLMN specific bwPool may be either primaryForTrafficType or
sharedForAllTrafficTypes bwPool.
On the iub interface may be configured a mix of PLMN Common bwPool and a PLMN specific
bwPool.
Per PLMN sharing the utran, may be configured one or several bwPool for atm, ip or mixed of atm and
ip interfaces.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 110/263
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
atmSwitch
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
RNC
NodeB
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
IMA 3 E1
PLMN A specific bwPool bwPool4
IP router
FE
IubIf i
aal2If i
ipIf i
TEG
Figure 3-53, bwpool in the utranSharing 2 PLMN context, exemple
Asymmetrical traffic:
To handle separately hsdpa and Hsupa flows, two different bandwidthPools must be specified linked to
two different transportMaps:
- The hsdpa is handle by a primaryForTrafficType bwPool linked to a transportMap including a
transportServiceEntry set with ulDlPreference: dlPref,
- The hsupa is handle by a SharedForTrafficTypes bwPool linked to a transportMap including a
transportServiceEntry set with ulDlPreference: ulDlPref.
Rule: IubTEG_RNC aal2 Component_8
The asymmetrical traffic handling applies:
- Only to the hspa I/B traffic,
- Only to on the Iub interface,
- On both the atm and the ip interfaces.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 111/263
RNCIN
RNCIN / IubIf
aal2If i
TransportMap i
interfaceType: Iub
BwPool/x
preference: sharedForAllTrafficTypes
qosx
path
tse:
qos3
path
TransportMap j
interfaceType: Iub
BwPool/y
preference: primaryForTrafficType
qosx
path
path
TEG
Figure 3-54 Asymmetrical bwPools case of nE1+IMA
Robustness:
The robustness mechanism applies to the asymmetrical traffic: Hsdpa or Hsupa, identified by the
received radioBearerType UMTS EI
Assuming the configuration indicated in theFigure 3-54 Asymmetrical bwPools case of nE1+IMA:
In normal condition, the admissionControl assigns the hsdpa traffic to the bwPool/y.
In case of bwPool/y bandwidth exhaustion, the admissionControl assigns the hsdpa traffic
to the bwPool/x.
On call establishment, the admissionControl identifies the different TransportMap(s) including tse
satisfying the call qos characteristics.
If several TransportMaps are identified, the ulDlPreference parameter is taken into consideration for
determing the most preferred TM:
- A tse with ulDlPreference = ulPref or dlPref is more preferred than a tse with
ulDlPreference=ulDlPref.
- A tse with ulDlPreference = ulDlPref is more preferred than a tse with
ulDlPreference=noPref.
If not enough available bandwidth in the bwPool linked to the most preferred transportMap, the
admissionControl assigns the call to the bwPool linked to the less preferred transportMap.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 112/263
3.6.5
AAL2 PATHS
The RNC supports up to 810 aal2 paths per configured PSFP or DCPS.
UA6
4 PSFP/DCPS
6 PSFP/DCPS
7 PSFP/DCPS
8 PSFP/DCPS
10 PSFP/DCPS
12 PSFP/DCPS
3240
4860
5670
6480
8100
9720
The RNC supports up to 9720 paths, identified by a pathId in the range [0, 65535].
Rule: IubTEG_RNC_aal2Path_2
The pathIds must be unique within an aal2If, even if the PathIds belongs to different
bandwidthPool
Under one aal2If component, the paths are either configured against the aal2If or against a bwPool; a
mix of path under aal2If and path bwPool is not allowed.
All aal2 Paths under a particular aal2If are assigned to one single PMC-PC, whatever the aal2
Path Qos. Indeed one PMC-PC handles all the Paths from one NodeB.
The load of a Path is estimated by means of its ECRgcac: ECRgcac = 2*SCR*PCR / (SCR+PCR).
The load of a PMC-PC is estimated by summing ECR from each Path configured on it.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 113/263
3.6.6
AAL2 QOS
The mapping between the different kinds of path (qos0, qos1, qos2 and qos3 paths) and the ITU
codePoint is configured within the RNC.
ALU suggests a mapping as an example that may be modified by the network operator.
The mapping is configured in the RNC thanks to the parameter: qosxtoQ2630QosCodePoint, with x in the
range [0,3].
Based on the ITU codePoint definition:
1 Stringent class
2 Tolerant class
128 to 255 Reserved for network specific assignment
The following ITU code points are suggested for the UA6 realease:
- WithOut hspaStreaming:
qos0toQ2630QosCodepoint = 1
qos2toQ2630QosCodepoint = 2
qos3toQ2630QosCodepoint = 2
With hspaStreaming:
qos0toQ2630QosCodepoint = 1
qos1toQ2630QosCodepoint = 1
qos2toQ2630QosCodepoint = 2
qos3toQ2630QosCodepoint = 2
3.6.7
AAL5 CONNECTIONS
The amount of aal5 connection supported by the RNC depends on the amount of PSFP/DCPS within the
RNC:
4 PSFP/DCPS
6 PSFP/DCPS
8 PSFP/DCPS
10 PSFP/DCPS
12 PSFP/DCPS
Service groups
10
12
1800
3000
4200
6000
7200
UA6
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 114/263
# active TMU
# spare TMU
# serviceGroup
serviceGroup Id
[ 0, 2 ]
[ 0, 4 ]
[ 0, 5 ]
[ 0, 6 ]
10
12
10
[ 0, 9 ]
12
14
12
[ 0, 11 ]
The nodeB distribution over the different PMC-TMU depends on the serviceGroup value configuration.
The maximum amount of nodeB per serviceGroup depends on the RNC capacity configuration (3.6.3):
all6mPktServSP
allPktServSP2
allPktServSP2FullDim
120
120
200
3.6.8
QOS
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 115/263
The ARP attribute is a subscription attribute which is not negotiated from the mobile
terminal.
In situations where resources are scarce, the relevant network elements can use the ARP to
prioritize bearers with a high ARP value over bearers with a low ARP value when
performing admission control.
ARP range value: [1, 2, 3]
- The THP (TrafficHandlingPriority):
The THP specifies the relative importance for handling of all the SDU belonging to the radio
access bearer compared to the SDU of other bearers.
The THP applies only to the interactive trafficClass umts flows.
Within the interactive trafficClass, there is a definite need to differentiate between bearer
qualities. This is handled by using the THP attribute, to allow the RAN to schedule traffic
accordingly.
THP range value: [1, 2, 3], with THP=1 being the highest priority while THP= 3 being the
lowest priority.
Moreover the ALU RNC introduces one more qos information taken into consideration in the qos
mapping table:
- RbSetQos:
Traffic class
IUB interface
RbSetQos
R99
Conv
+cSRB+dSRB
R99 Streaming
R99 I/B
Hspa I/B+Streaming
Conversational
Common
Signaling
Streaming
Interactive
Background
Streaming
Interactive
Background
Since the Transport qos information are correctly mapped between each others, the final objective is to
mapped each different UMTS flows to a specific DSCP value in such a way each umts flow received the
expected qos treatment and is correctly marked.
The UMTS qos information is mapped to the Transport Qos information through the configurable
TransportMap RNC component.
3.6.8.2 SERVICECATEGORY
The RNC supports the serviceCategories: cbr, rtVbr, nrtVbr, ubr and ubr+.
To each serviceCategory is assigned a trafficDescriptoType value which determines which
trafficDescriptor parameters must be set against the vcc:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 116/263
SC
Cbr
tdt
Tx tdp1
Rx tdp1
Tx tdp2
Rx tdp2
Tx tdp3
Rx tdp3
pcr
pcr
Vbr
pcr
pcr
scr
scr
mbs
mbs
Ubr
Ubr+
pcr
pcr
mdcr
mdcr
A MDCR (Minimum Desired Cell Rate) may be configured against an ubr vcc, in such case the ubr
serviceCategory is said ubr+.
The MDCR is the bandwidth reserved by the ACAC for the ubr+ atmConnection, ECRacac = MDCR.
Moreover the MDCR is also taken into consideration by the aal2 CAC: ECRgcac = MDCR.
Rule: IubTEG_RNC-Atm _QOS_7
When tdt=9 is associated to the ubr serviceCategory, a MDCR must be configured against the vcc.
Remark:
- The MDCR is configured through the tdp3.
- The PCR must be non-zero and must be greater than or equal to MDCR..
The cbr sc is either associated to the tdt=3 or tdt=1. In the second case no bandwidth is configured against
the cbr vcc.
The vcc trafficDescriptor may be set asymmetrical.
3.6.9
TRANSPORTMAP
The TransportMap realizes Classification for atm and ip interfaces and moreover Marking for the ip
interface:
- Classification:
- Up to 4 UMTS streams are identified called: qos0, qos1, qos2 and qos3,
- The classification is achieved based on the Umts qos information: trafficClass, RbSetQos,
ARP-PL, THP,
The congestionManagement applies per umts stream.
- Marking:
- A DSCP value is assigned per Umts stream identified by the Umts qos information:
trafficClass, RbSetQos, ARP-PL, THP.
Remark: The transportMap is the way to configure the Umts to Transport qos mapping table within the
RNC.
The transportMap tables apply to all the utran interfaces, with exception of the IuPS.
Several transportMap tables may be configured within the RNC.
Rule: IubTEG_RNC-Atm_TMap_1
The RNC may be configured with up to 64 transportMap components.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 117/263
A transportMap is linked either to an ipIf bwPool, an aal2if bwPool or an aal2If (as long as no bwPool
configured under the aal2if, case of IucsIf or IurIf). One TransportMap may be shared between several
instances of ipIf bwPool, aal2If bwPool and aal2If, may also be shared between different utran interfaces.
Remark: No transportMap linked to ipFlow, aal2Path or iuPS components.
Rule: IubTEG_RNC-Atm_TMap_2
Each BwPool (or Aal2If if no BwPool declared) must be linked to exactly one TransportMap.
A transportMap is configured with the following parameters:
RNCIN
TransportMap i
interfaceType:
Iub, Iur, IuCS, ( not iuPS)
preference:
sharedForAllTrafficTypes, or
primaryForTrafficType(only Iub case).
transportServiceEntry 1:
[TC, RbSetQos, ARP PL, Thp] => qos i
ulDlPreference.
transportServiceEntry n:
[TC, RbSetQos, ARP PL, Thp] => qos i
ulDlPreference.
TEG
Figure 3-55, transportMap parameters
- InterfaceType:
Values: [Iub, iuCs, Iur, (not iuPS)]
One transportMap may be configured with different interfaceType values, in other
words a transportMap may be allocated to different Utran interfaces.
- Preference:
Values: [sharedForAllTrafficTypes, primaryForTrafficType]
The setting of the Preference parameter determines the nature of the bwPool the
transportMap is connected to.
The Preference parameter is not taken into consideration by the admissionControl
when selecting a bwPool.
The sharedForAllTrafficTypes preference can be assigned only to an atm bwPool.
The primaryForTrafficType preference can be assigned to both atm bwPool and IP
bwPool.
Rule: IubTEG_RNC-Atm_TMap_3
The interfaceType and Preference are mandatory parameters within the transportMap.
Rule: IubTEG_RNC-Atm _ TMap _4
The primaryForTrafficType Preference value is available only on the Iub interface.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 118/263
- Transport serviceEntry:
- Inputs: TC, rbSetQos, ARP-PL, THP.
Each input may be set with a specific value or with the ignore value when the input
parameter doesnt apply to the UMTS flow.
- Output:
qos i: with i in the range [0, 1, 2, 3], one associated transport qos value
involved in both the atm and ip interfaces,
The DSCP value is not taken into consideration on the ATM interface.
INPUT values
TC
rbSetQos
ARP-PL
THP
OUTPUT Values
UlDlPreference
DSCP
Qos i
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 119/263
RNCIN
RNCIN
IubIf
TransportMap 1
aal2If i
Preference: sharedForAllTrafficTypes
qos/i Paths
qos/j, Paths
TransportMap 2
interfaceType: Iub
BwPool/y
Preference: primaryForTrafficType
Qos/k, Paths
IucsIf
Congestionmanagement i
aal2If i
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
Qos/i, path/m
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
Congestionmanagement j
IurIf
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
aal2If i
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
Qos/i, paths
Qos/j, paths
TEG
Figure 3-56, transportMap exemple
Several transportMap tables are suggested for the RNC atm interfaces for different applicationContexts:
TM/#
Description
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 120/263
Transport MAP /1
Comments:
Tse
TC
1 Common
2 signaling
R99
"
"
IuCS
R99
"
"
Iub, Iur
R99
"
Hspa
"
"
Iub, Iur
R99
"
18 interactive
19 interactive
20 interactive
"
"
"
"
"
"
Hspa
"
27 interactive
28 interactive
29 interactive
"
"
"
R99
30 interactive
31 interactive
32 interactive
33 background
Hspa
34 background
35 background
36 background
"
"
"
Iub, Iur
"
"
21 interactive
22 interactive
23 interactive
24 interactive
25 interactive
26 interactive
"
"
Iub, Iur R99
"
12 streaming
13 streaming
14 streaming
15 interactive
16 interactive
17 interactive
"
Iub, Iur
6 streaming
7 streaming
8 streaming
9 streaming
10 streaming
11 streaming
"
Iub, Iur
3 conversational
4 conversational
5 conversational
37 background
38 background
ARP
ignore
ignore
THP
ignore
ignore
ignore
ignore
ignore
ignore
ignore
2
0
1
ignore
ignore
ignore
ignore
ignore
ignore
ignore
0
rbsetQos
0
0
0
qos
0
0
0
0
1
noPreference
default
noPreference
default
noPreference
default
noPreference
default
nopreference
default
nopreference
default
default
nopreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
default
noPreference
default
default
noPreference
noPreference
default
noPreference
default
noPreference
default
default
2
1
uldlpreference
noPreference
2
0
0
DSCP
default
2
ignore
ignore
2
0
1
ignore
ignore
ignore
ignore
- TransportMap/2:
ApplicationContext:
- UA5 backward compatibility,
- InterfaceType: Iub,
- Preference: PrimaryForTrafficType,
- Transport: ip or atm with only qos3 vcc.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 121/263
Transport MAP /2
Tse
TC
ARP
THP
1 interactive
2 interactive
3 interactive
4 interactive
5 interactive
6 interactive
7 interactive
8 interactive
9 interactive
rbsetQos
qos
DSCP
uldlpreference
AF11
preferredForUlAndDl
preferredForUlAndDl
preferredForUlAndDl
preferredForUlAndDl
2
AF12
preferredForUlAndDl
preferredForUlAndDl
preferredForUlAndDl
AF13
10 background
11 background
ignore
ignore
12 background
ignore
preferredForUlAndDl
preferredForUlAndDl
preferredForUlAndDl
DE
preferredForUlAndDl
preferredForUlAndDl
- TransportMap/3:
ApplicationContext:
- InterfaceType: Iub, IuCS and Iur,
- Hspa streaming: hspa streaming supported,
- Preference: SharedForAllTrafficTypes,
- Transport: atm, enhancedQos activated.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 122/263
Transport MAP /3
Comments:
Tse
TC
1 Common
2 signaling
R99
"
"
IuCS
R99
"
"
Iub, Iur
R99
Hspa
"
"
Iub, Iur
R99
"
"
"
"
"
"
"
Hspa
"
"
"
ignore
ignore
2
0
1
ignore
ignore
ignore
12 streaming
13 streaming
14 streaming
15 interactive
ignore
ignore
ignore
0
16 interactive
17 interactive
21 interactive
22 interactive
23 interactive
24 interactive
Hspa
34 background
35 background
36 background
"
"
ignore
R99
"
"
6 streaming
7 streaming
8 streaming
9 streaming
ignore
30 interactive
31 interactive
32 interactive
33 background
"
THP
ignore
27 interactive
28 interactive
29 interactive
"
Iub, Iur
ignore
25 interactive
26 interactive
"
"
Iub, Iur R99
"
18 interactive
19 interactive
20 interactive
"
Iub, Iur
ignore
3 conversational
4 conversational
5 conversational
10 streaming
11 streaming
"
"
Iub, Iur
ARP
ignore
ignore
37 background
38 background
ignore
qos
0
0
0
default
noPreference
default
noPreference
default
nopreference
default
nopreference
default
default
nopreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
noPreference
default
default
noPreference
noPreference
2
0
1
2
ignore
0
1
noPreference
noPreference
noPreference
default
default
default
2
0
uldlpreference
noPreference
default
DSCP
default
2
1
rbsetQos
0
0
ignore
2
0
1
ignore
ignore
ignore
ignore
default
noPreference
default
default
noPreference
noPreference
default
noPreference
default
noPreference
- Transportmap/4:
ApplicationContext:
- InterfaceType: Iub,
- Preference: PrimaryForTrafficType,
- Transport: atm, four qosx vcc.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 123/263
Transport MAP /4
Tse
TC
ARP
1 interactive
2 interactive
3 interactive
4 interactive
5 interactive
6 interactive
7 interactive
8 interactive
9 interactive
THP
rbsetQos
qos
DSCP
0
1
AF11
preferredForUlAndDl
AF12
2
1
preferredForUlAndDl
2
AF13
preferredForUlAndDl
preferredForUlAndDl
ignore
preferredForUlAndDl
10 background
11 background
ignore
12 background
ignore
preferredForUlAndDl
preferredForUlAndDl
0
2
preferredForUlAndDl
preferredForUlAndDl
0
1
uldlpreference
preferredForUlAndDl
DE
preferredForUlAndDl
preferredForUlAndDl
3.6.10.1
EQUIVALENTBITRATE
For each utran aal2 interface (Iub, Iur and IuCS), per direction (ul and dl), per trafficClass and as an
option per THP are configured:
- an equivalentBitRate (EBR),
- a maximumBitRate (MBR) and
- a rbSetQos value.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 124/263
admissionControl
- Iux: iubif, iurif or iucsif
- TC: trafficClass
TransportMap
admCtrl, bwPool selection
TEG
Figure 3-57 admissionControl, EBR configuration
The configured EBR value is taken into consideration by the admissionControl during radioBearer
establishment phase when selecting a bwPool.
The configured RbSetQos is an input parameter for the transportMap table.
The equivalentBitRate is an estimation of the bandwidth consumed by a rab at RNL layer. The Transport
overhead must not be taken into consideration when configuring the equivalentBitRate values.
When executing the admissionControl, the RNC applies a transport overhead ratio to the
equivalentBitRate.
The transport overhead ratio applied by the RNC is hardcoded and depends on the transport type:
- ATM: 21% overhead is added to the EBR,
- IP: 15% overhead is added to the EBR.
Rule: Iub_RNC-Atm_AC_1
The configured equivalentBitRate must not take into account the transport overhead.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 125/263
DlRbSetConf:
cacTransportInfoList[MAX_NB_REF_AMR_BIT_RATE=8]
cacTransportInfoList(i ). iubFpEquivalentBitRate
cacTransportInfoList(i ). iubFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iurFpEquivalentBitRate
iurFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iuFpEquivalentBitRate
iuFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iubIurTransportQosId
iuTransportQosId
cacTransportInfoInstanceCharacteristic
Integer [0..3]
[0..3] step 1
enum {AMR_12_2, AMR_10_2, AMR_7_95, AMR_7_4,
AMR_6_7, AMR_5_9, AMR_5_15, AMR_4_75,
interactive THP=0, interactive THP=1,
interactive THP=2, interactive unspecifiedTHP,
backGround, SRB_ON_HS_DSCH, SRB_ON_DCH, UnSpecified }
UlRbSetConf:
cacTransportInfoList[MAX_NB_REF_AMR_BIT_RATE=8]
cacTransportInfoList(i ). iubFpEquivalentBitRate
cacTransportInfoList(i ). iubFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iurFpEquivalentBitRate
iurFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iuFpEquivalentBitRate
iuFpMaxBitRate
cacTransportInfoList(i ).
cacTransportInfoList(i ).
cacTransportInfoList(i ).
iubIurTransportQosId
iuTransportQosId
cacTransportInfoInstanceCharacteristic
Integer [0..3]
[0..3] step 1
enum {AMR_12_2, AMR_10_2, AMR_7_95, AMR_7_4,
AMR_6_7, AMR_5_9, AMR_5_15, AMR_4_75,
interactive THP=0, interactive THP=1,
interactive THP=2, interactive unspecifiedTHP,
backGround, SRB_ON_HS_DSCH, SRB_ON_DCH, UnSpecified }
FACH (Nodeb.FDDCell.SCCPCH.FACH)
cacTransportInfo.
dlCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
dlCacTransportInfo.fpMaxBitRate
cacTransportInfo.
ulCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
ulCacTransportInfo.fpMaxBitRate
PCH (Nodeb.FDDCell.SCCPCH.PCH)
cacTransportInfo.
dlCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
dlCacTransportInfo.fpMaxBitRate
cacTransportInfo.
ulCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
ulCacTransportInfo.fpMaxBitRate
RACH (Nodeb.FDDCell.RACH)
cacTransportInfo.
dlCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
dlCacTransportInfo.fpMaxBitRate
cacTransportInfo.
ulCacTransportInfo.fpEquivalentBitRate
cacTransportInfo.
ulCacTransportInfo.fpMaxBitRate
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
[0..16777216],
Rule: Iub_RNC-Atm_AC_2
Three set of EBR values can be configured for the Interactive trafficClass; one set of EBR values
per THP.
Remark:
Either are configured:
- 1 EBR for interactive THP=0,
+ 1 EBR for interactive THP=1,
+ 1 EBR for interactive THP2.
Or is configured:
- 1 EBR for interactive unspecifiedTHP,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 126/263
On both the Iub and the Iur interfaces, the equivalentBitRate for the streaming trafficClass over hsdpa, is
derived from the received Ranap GBR and from the HspaTransportEbrCorrectiveFactor parameter values
configured against the streaming trafficClass:
Hspa streaming EBR = f (GBR * HspaTransportEbrCorrectiveFactor).
RNC/radioAccessService//HspaTransportEbrCorrectiveFactor range: [0, 200%].
If HspaTransportEbrCorrectiveFactor = 0%, then EBR=0 the admissionControl doesnt apply to the
stream.
The Operator ensures the consistency of the configured EBR value based on his desired allocation
strategy.
3.6.10.2
INTERFACE BANDWIDTH
On the atm interface, the admissionControl determines the aal2path bandwidth for each direction based
on the configured UL and DL vcc trafficDescriptor and the generic CAC algorithm:
- Cbr vcc, ECRgcac = PCR c/s
- Vbr vcc, ECRgcac = 2*PCR*SCR/(PCR+SCR) c/s
- Ubr+ vcc, ECRgcac = MDCR c/s,
- Ubr vcc, ECRgcac = 0.
On the ip interface, the admissionControl determines the ipFlow bandwidth based on the configured UL
and DL ipFlow peak and committed rates and the generic CAC algorithm:
ERgcac = 2*CR*SR/(PR+SR) kb/s
The bandwidth granulary that the admissionControl takes into consideration for the regulation is
configured through the cacm parameter.
The cacm parameter is configured against an aal2if and an ipIf component, and applies to all the bwPools
under the aal2If and the ipIf components.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 127/263
aal2If i
Cacm=qos
qosnBwReservation
BwPool/x
qos 0
path
path
qos 1
path
path
qos 2
path
path
qos 3
path
path
iubIf 1
SignalingBearer
userPlane
aal2LinkToaal2if: aal2If i
ipLinkToIpif: ipIf i
congestionManagement n
transportMap m
congestionManagement x
transportMap y
BwPool/y
qos 3
path
path
TEG
Figure 3-58, admissionControl attributes
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 128/263
- Cacm = Path: The availableBandwidth taken into consideration by the admissionControl is the
bandwidth per aal2Path and per direction,
aal2Path UL availableBandwidth = vcc UL ECRgcac,
aal2Path DL availableBandwidth = vcc DL ECRgcac.
- Cacm = Qos: The availableBandwidth taken into consideration by the admissionControl is the
calculated total bandwidth per bwPool, per qos and per direction.
The cacm qos value applies to both the atm and the ip interfaces.
Furthermore when setting the qosnBwReservation with a non zero value, the admissionControl takes
into consideration an additional bandwidth portion available for all the qos within a bwPool.
The common for all qos bandwidth portion is taken into consideration by the admissionControl on qos
i call establishment when the qos i availableBandwith is exausted.
The qosnBwReservation parameter value is taken into consideration by the admissionControl on both
downLink and upLink.
Rule: IubTEG_RNC-Atm_AC_4
The qosnBwReservation is applicable only if cacm=qos.
The qosnBwReservation parameters are either configured against the bwPool component or against
the aal2If then apply to all the bwPool under the aal2If.
Case of atm interface, the availableBandwidth is the sum of the bandwidth of all the vcc for one
aal2Qos within a bwPool, assuming one bwPool under an aal2If then:
Per qos available bandwidth:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 129/263
aal2If i
bwPool x
Available bw =3200 c/s
Cacm = qos
qos0BwReservation=60%
qos1BwReservation=60%
qos2BwReservation=60%
qos3BwReservation=100%
BwPool/x
qos 0
Path, ul/dl ECRgcac=1000 c/s
qos 1
Path, ul/dl ECRgcac=1000 c/s
bwPool y
Available bw =2000 c/s
qos 2
Path, ul/dl ECRgcac=1000 c/s
qos 3
Path, ul/dl ECRgcac=200 c/s
BwPool/y
qos 3
Path, ul/dl ECRgcac=2000 c/s
Rule: IubTEG_RNC-Atm_AC_5
In such a way qos3BwReservation > 0% is effective then:
- a non nul bandwidth must be assigned to the qos3 vcc, therefore the ubr serviceCategory must
not be assigned to the qos3 vcc, preferred ubr+ (MDCR), nrtVbr...
3.6.10.3
ALGORITHM
At each radioBearer establishment, per direction, the admissionControl is invoked to determine the
preferred bwPool and to assign the resources.
The bwPool is selected by the admissionControl according to the algorithm:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 130/263
Within ipIf and aal2If, identification of all the bwPools set with:
OutPut:
selected bwPools
Bw check:
- If cacm = aal2If / ipIf, check that bwPool ul/dl AR > ul/dl EBR,
ii
- If cacm = qos, check that bwPool qosi ul/dl AR > ul/dl EBR.
- TM identification: Identification of the TM linked to the selected bwPools.
- bwPool selection: select a bwPool :
Linked to TM with TSE matching the input (TC, THP, ARP-PL, rbSetQos, rbType (optional)).
iii
iv
TEG
Figure 3-60, admissionControl, bwPool selection
When selecting the bwPool, the admissionControl takes into consideration:
The PLMN Id configured against the bwPool (utranSharing case),
The cacm option,
The ulDlPreference configured against the TSE within the transportMap (asymmetrical
traffic handling case),
The available bandwidth.
Remark: the admissionControl doesnt take into account the Preference attribute within the
transportMap.
BwPool selection ulDlPreference involvement (case of asymmetrical traffic handling):
The admissionControl takes into consideration the optional received rbType EI and the
ulDlPreference attribute within the transportMap:
If rbType = HS-Dsch:
The tse set with dlPref and ulDlPref are more preferred,
The tse set with noPref and ulPref are LessPreferred,
If rbType = E-Dch:
The tse set with ulPref and ulDlPref are more preferred,
The tse set with noPref and dlPref are LessPreferred,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 131/263
rBType = hsDpa
First choice
Second choice
rBType = hsUpa
First choice
Second choice
ulDlPreference:
Comment:
dlPref
ulDlPref
If no dlPref configured.
ulPref
ulDlPreference:
Comment:
ulPref
ulDlPref
If no ulPref configured.
dlPref
3.6.10.4
TRAFFICMEASUREMENT
NT_UL_Watermark_EBR_Aal2If
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
NT_UL_WaterMark_EBR_IpIf
- Type: cumulative,
- Granularity: qos,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 132/263
Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
NT_DL_Watermark_EBR_Aal2If
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
NT_DL_WaterMark_EBR_IpIf
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
3.6.10.5
APPLICATION CASES
The objective of this section is give some examples of traffic handling according to the setting
of the RNC admissionControl. Focus is given to the asymmetrical traffic handling.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 133/263
Atm vcc:
- 3 hsdpa qos3 vcc:
o On the RNC side, is reserved a DL bandwidth equivalent to 95%*E1 and
no UL bandwidth to each Hsdpa vcc.
o On the nodeB side, different HoldingPriority values assigned to each
Hsdpa vcc.
- 1 hsupa qos3 vcc and 1 qos2 vcc:
o On the RNC side, is reserved an UL bandwidth equivalent to 95%*E1
and no DL bandwidth to the Hsupa vcc. The Hsupa is coupled with one
qos2 vcc for which is reserved a DL bandwidth equivalent to 95%*E1
and no UL bandwidth.
o On the nodeB side, the same HoldingPriority value is assigned to both
the Hsupa vcc and the qos2 vcc.
- 1 qos0 and 1 qos2 vcc:
o On the RNC side, is reserved a UL/DL bandwidth equivalent to 95%*E1
to the set of qos0 and qos2 vcc.
o On the nodeB side, the same HoldingPriority is assigned to both the qos0
vcc and the qos2 vcc.
- And signaling and oam vcc.
RNC CAC and CM:
Cacm=qos and qos3bwReservation=100%
Test configuration values:
RNC provisioning
Vcc
#
Radio
Type
QoS
BW
ATM SC
Reserv
DCH
rtVBR
DCH
nrtVBR
HSUPA
DCH
HSDPA
100%
100%
nrtVBR
RNC ATM tx
PCR
SCR
4490
900
1499
30
2766
30
4266
4266
4266
4490 1999
1
nrtVBR
4490 4063
UBR+
4490
Backhaul
RNC ATM rx
ECR per
HP
4266
4267
4266
PCR
SCR
4490
900
1499
4490 1999
30
2766
4490 4062
40
4265
4266
4266
xDSL
SDSL
SDSL
SDSL
SDSL
1
2
Qos
UBR1
UBR
UBR+3
UBR
ADSL
UBR+3
HSDPA
100%
UBR+
4490
4266
4266
4266
ADSL
UBR+3
HSDPA
100%
UBR+
4490
4266
4266
4266
ADSL
UBR+3
ALU confidential
UMT/IRC/APP/7149
N
HP
07.02 / EN
Standard
29/06/2009
Page 134/263
TransportMap x
interfaceType: Iub,
preference: sharedForAllTrafficTypes
BwPool/x
qosxbwReserv = 0%
qos3bwReserv = 100%
qos x
path
qos 3
3 hsDpa path
1 hsUpa path
atm
atm
atm
atm
adsl
RNC
RNC
NodeB
NodeB
Stm1
IMA 5 E1
TEG
Figure 3-62 1 IMA, 1 bwPool and asymmetrical traffic
Remarks:
- As long as one single bwPool handling the qos3 traffic, it is not necessary to set the
transportMap/Tse/ulDlPref parameter.
- 95% of each nodeB E1 is reserved for the userPlane traffic. 5% of each nodeB E1 remains
available for the controlPlane.
- Hsupa serviceCategory set either with ubr+ or nrtVbr.
o Hsupa sc= ubr+ if a minimum bandwidth needs to be reserved for HSUPA traffic at
the FP atm scheduler level.
o Both ubr+ and nrtVbr allow reserving bw for the Hsupa vcc at the admissionControl
and congestionManagement level.
- The nrtvbr / TDT= 6 not accept 0 /0 /0, reason why set with 1/1/1.
Expected behaviour:
hsDpa traffic:
The hs-dsch traffic is assigned to a qos3 vcc within the sharedForAllTrafficTypes
bwPool x.
Within the bwPool x, a qos3 vcc with the most available downLink bandwidth is
selected.
The hs-dsch leg is accepted if the bwPool x available bandwidth is higher than the hsdsch overhead*iubFpEquivalentBitRate.
hsUpa traffic:
The e-dch traffic is assigned to a qos3 vcc within the sharedForAllTrafficTypes
bwPool x.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 135/263
Within the bwPool x, a qos3 vcc with the most available upLink bandwidth is
selected.
The e-dch leg is accepted if the bwPool x available bandwidth is higher than the e-dch
overhead*iubFpEquivalentBitRate.
TransportMap x
BwPool x
qos 3
4 hsDpa path
BwPool y
qos 3
1 path
qos 2
1 path
qos 1
1 path
qos 0
1 path
preference: primaryForTrafficType
tse i: I/B, rbSetQos2, , ulDlPref = dlPref => qos3
UBR+, rx&tx tdt=9, rxTD= 4490-0-4490-0, txTD= 4490-0-4490-0
TransportMap y
leasedLines
preference: sharedForAllTrafficTypes
tse: Conv, rbSetQos0, => qos0
tse: Str, rbSetQos1&2, => qos1
tse: I/B, rbSetQos1, => qos2
tse: I/B, rbSetQos2, , ulDlPref = ulDlPref => qos3
qos0, 1, 2 , 3 vcc
BwPool y
4 qos3 vcc
BwPool x
aal2If i
Stm1
IMA 4 E1
ADSL
ADSL
Eth
RNC
RNC
NodeB
NodeB
E1
1 qos3 vcc
1 qos2 vcc
1 qos1 vcc
1 qos0 vcc
qos 3 vcc
TEG
Expected behaviour:
HsDpa traffic:
The traffic hs-dsch is spead over the qos3 vcc from the primaryForTrafficType
bwPool x AND the sharedForAllTrafficTypes bwPool y, according to the available
downLink bandwidth.
The hs-dsch leg is accepted if the selected bwPool available bandwidth is higher than
the hs-dsch overhead*iubFpEquivalentBitRate.
HsUpa traffic:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 136/263
The traffic e-dch is assigned first to a qos3 vcc within the sharedForAllTrafficType
bwPool y.
The bwPool y is composed of the bw from qos1 and qos2 vcc.
In case of bandwidth exhaustion within the bwPool y, the e-dch traffic is assigned as a
second choice to the primaryForTrafficType bwPool x.
The e-dch leg is accepted if the bwPool x available bandwidth is higher than the e-dch
overhead*iubFpEquivalentBitRate.
3.6.11.1
CONGESTIONMANAGEMENT TABLE:
The congestionManagement parameters involved in the qosDiscard and backPressure thresholds setting,
are configured through the RncIn/CongestionManagement tables.
Rule: IubTEG_RNC-Atm_CM_2
Each aal2Path must be linked to an appropriated congestionManagement table either through the
aal2If or aal2If/bwPool component it belongs to.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 137/263
RNCIN
RNCIN
aal2If i
CongestionManagement i
BwPool/x
path/i
path/j
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
2
BwPool/y
CongestionManagement j
path/k
path/l
ipIf i
3
BwPool/u
CongestionManagement k
Activation: [qosDiscard only, qosDiscard+backPressure]
ipFlow/i
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
ipFlow/l
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
TEG
Figure 3-64, congestionManagement links
3.6.11.2
The congestionManagement algorithm provides two different behaviours according to the setting of the
RncIn/enhancedQos parameter:
- If enhancedQos=disable, the congestionManagement provides the UA5 equivalent behaviour:
Emulation of the UA5 behavior, with some variations:
o New formula for Txoff,
o New formulas for qosDiscard and qosBackPressure thresholds,
o The congestionFlag is inserted in the Xoff signal, always set to No.
Remarks:
o Supports up to 3 qos, No support of Hspa streaming,
o GBR and minBr not supported.
Rule: IubTEG_RNC-Atm_CM _4
The RncIn enhancedQos parameter must be set to disable, when the congestionManagement
UA5 equivalent behavior is preferred.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 138/263
THP
minBrForR99
minBrForHsdpa
Interactive
16 kb/s
16 kb/s
Interactive
8 kb/s
8 kb/s
Interactive
8 kb/s
8 kb/s
backGround
na
Rule: IubTEG_RNC-Atm_CM _5
The RncIn enhancedQos parameter must be set to enable, when the congestionManagement
UA6 behavior is preferred.
Rule: IubTEG_RNC-Atm_CM _6
The RncIn enhancedQos parameter must be set to enable when the congestionManagement has
to take into consideration the GBR for streaming and minBrForHspa and minBrForR99 for
interactive/Background
3.6.11.3
Since up to 4 qos are supported, up to four qosDiscard thresholds and 4 qosBackPressure thresholds are
set then one qosDt parameter is set per qos and one qosBP parameter is set per qos.
Rule: IubTEG_RNC-Atm_CM _7
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 139/263
3/ the remote POC is populated with a FP supporting standardVPT, the remote POC
acts as a VP switch (not VC switch) and the trafficShaping at VP level is activated in
the remote POC on the atm interfaces toward the NodeB.
For these 3 Iub configurations, apply on the RNC the congestionManagement Discard Threshold
set of values case of basicVPT trafficShaping on the Iub interface.
Context No basicVPT trafficShaping on the Iub interface:
o 1/ the trafficShaping is not activated neither in the RNC nor in the POC,
o 2/ the remote POC is populated with a FP supporting standardVPT, the remote POC
acts as a VC switch (not VP switch) and the trafficShaping at VP level is activated in
the remote POC on the atm interfaces toward the NodeB.
For these two Iub configurations, apply on the RNC the congestionManagement Discard
Threshold set of values case of No basicVPT trafficShaping on the Iub interface.
Rule: IubTEG_RNC-Atm_CM _8
3.6.11.4
qosBPt 0 0 1 0 2 95 3 95
qosBPt 0 0 1 0 2 33 3 35
COUNTERS:
Two kinds of real time counters are implemented which measure the trafficVolume per 10 ms period:
- The per qos real time counters: Q010ms, Q110ms, Q210ms and Q310ms,
- The per cumulative qos counters: Qxxx, in extenso: Q0, Q01, Q012 and Q0123.
The four per qos counters provide per qos the trafficVolume over a 10 ms period:
Qn10 ms Counters
Qos
Q010 ms
Qos0
Q110 ms
Qos1
Q210 ms
Qos2
Q310 ms
Qos3
Furthermore the RNC estimates the per qos expected trafficVolume over the next 10 ms period, based
on the per qos measured trafficVolume over the previous 10 ms periods. For that the RNC set the Qne
(estimated) counters:
Qne Counter
definition
Q0e
Q1e
Q2e
Q3e
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 140/263
The counter unit is either cell/10ms for the atm interface or bytes/10ms for the ip interface.
The four per cumulative qos counters Qxxx provide the trafficVolume over a 10 ms period for qos0,
qos0+qos1, qos0+qos1+qos2, qos0+qos1+qos2+qos3:
Qxxx Counters
definition
Q0
Q01
= Q0e + Q1
Q012
= Q01 + Q2
Q0123
= Q012 + Q3
3.6.11.5
THRESHOLDS
The qosDiscard and qosBackPressure threshold values calculated by the RNC depend on the bandwidth
configured per qos against a bwPool, the configured qosDt and qosBP parameters and the setting of the
qosnBwReservation parameters.
The qosnBwReservation parameters are involved in the Transport admissionControl.
The qosnBwReservation parameters are also involved in the congestionManagement thresholds
determination if:
- the enhancedQos = enabled,
- cacm=qos,
- qosnBwReservation > 0%.
Rule: IubTEG_RNC-Atm_CM _10
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 141/263
qosDiscardThresholds
dth0 = Th0 = bwPool vcc ECRgcac /100
= bwPool ipFlow ERgcac /100
Th0 = bwPool [qos0 vcc ECRgcac + qos1 vcc ECRgcac + qos2 vcc ECRgcac + qos3 vcc ECRgcac]
/100 for the atm interface,
Th0 = bwPool [qos0 ipFlow ERgcac + qos1 ipFlow ERgcac + qos2 ipFlow ERgcac + qos3 ipFlow
ERgcac] /100 for the ip interface,
The dthn thresholds are recalculated each 50 ms.
The Th0 threshold is updated when there is a change in transport status (bandwidth reduction,
restoration, addition),
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 142/263
Per period of 10 ms, an estimation of the per qos traffic using the Bwnavail portion is given by the
relation:
Traffic qos n shared
Trafficqosnshared = Qne bwnexclus
With:
- n = [0, 1, 2, 3],
- If TrafficQosnShared is negative, it is forced to Zero, then Trafficqosnshared 0.
The qos discard threshold definition is impacted by the qosnBwReservation through the
Trafficqosnshared and the bwnavail:
qosDiscardThresholds
dth0 = bw0avail
dth1 = bw1avail + (qosDt1/100 -1) * [ bw1avail trafficqos0shared ]
dth2 = bw2avail + (qosDt2/100 -1) * [ bw2avail ( trafficqos0shared + trafficqos1shared ) ]
dth3 = bw3avail + (qosDt3/100 -1) * [ bw3avail ( trafficqos0shared + trafficqos1shared + trafficqos2shared ) ]
The qosBP threshold formulas are not impacted by the qosnBwReservation nevertheless the qosBP
threshold values are impacted by the qosnBwReservation.
qosDiscardThresholds
bpThn = dthn * qosBPtn/100
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 143/263
RNC
ULRbSetConf
- Qaal2 Cac
DLRbSetConf
- Qaal2 Cac
NodeB
- ConnectionMode,
- saalUniParams
(common for CP, CCP and Alcap)
- IubIfID,
Linked to RNC-IN model/ Root/IubIf
- nodeBCapability,
- alcapCelValidityTimer,
- nodeBType.
CtrlPort (up to 8)
Linked to RNC-IN IubIf/Sig507)
- CtrlPort Id,
- CtrlPortType:
- 0: CP, 1: CCP, 2: SCP, 3: alcap
TEG
Figure 3-65, RNC-CN Model
Rule: IubTEG_RNC_nodeB discrimination_1
The nodeBType parameter must be set according to the type of nodeB either: iBTS,
micro/picoBTS or oneBTS.
Rule: IubTEG_RNC_ nodeB discrimination _2
The RNC/NodeB/ nodeBCapability last bit must be set to:
- 1 if Hybrid NodeB,
- 0 if atm NodeB.
3.6.14 ALCAP
Within the RNC no parameter is set for activating the Alcap.
Since the NodeB AlcapActivation parameter is set to true, no more version/edition fields included in the
NBAP message then the RNC concludes that the Alcap is the protocol used for the aal2 connection
establishment.
Rule: IubTEG_RNC_Alcap_1
Since alcap is activated on the Iub interface, one single alcap vcc must be configured per nodeB.
The Node B inserts its own A2EA in the NBAP RL Setup Response TLA sent to the RNC. The RNC aal2
address translation table must be configured with the NodeB A2EA and the associated aal2If and PathIds.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 144/263
Node B
ALCAP ERQ
- Destination address:
Node B A2EA in NSAP format
- SUGR parameter:
Binding Id (Node B context reference)
- CEID: aal2 path + CID
ALCAP ECF
TEG
Figure 3-66 Alcap protocol flow
Both the RNC-IN and the RNC-CN models are involved in the Alcap configuration.
The RNC-IN model:
Root
Aal2if i
- Cacm
IubIf i
RNC
- CidSelectMeth
Sig (07)
- Qosparameters
- saalUni
Nap/ atmConnection
- LoadBalancingMeth
- UmtsInterfaceList (up to 16)
UPlane
- linkTo aal2If
IubTransport flowCtrl
- activation
Qaal2Parameters
- orig A2EA,
- Qaal2 timers,
Qaal2 endPoints
A2EA (0):
PathId i
- atmConnection
aal2If, cost
- Qos
- pathOwner
aal2If, cost
Alcap bearer
-saalUni
Nap/ atmConnection
TEG
Figure 3-67, RNC-IN Model
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 145/263
RNC
ULRbSetConf
- Qaal2 Cac
NodeB
- ConnectionMode,
DLRbSetConf
- Qaal2 Cac
- saalUniParams
(common for CP, CCP and Alcap)
- IubIfID,
Linked to RNC-IN model/ Root/IubIf
- nodeBCapability,
- alcapCelValidityTimer,
- nodeBType.
CtrlPort (up to 8)
Linked to RNC-IN IubIf/Sig507)
- CtrlPort Id,
- CtrlPortType:
- 0: CP, 1: CCP, 2: SCP, 3: alcap
TEG
Figure 3-68, RNC-CN Model
According to the RNC-CN model, the RNC allows configuration of one single alcap
connection per nodeB. Within the RNC one Alcap connection must be assigned to each nodeB
supporting Alcap. The ctrlPortType=3 is assigned to the Alcap connection.
Rule: IubTEG_RNC_Alcap_2
Within the RNC-CN model:
- The ctrlPortType = 3 must be used for the Alcap connection,
- The ctrlPortType = 0 must be used for the CP connection,
- The ctrlPortType = 1 must be used for the CCP connection.
On the Iub interface, several SSCOP connections are established per nodeB for the different
SSCOP-Users: nbap-c, nbap-d and Alcap.
The RNC-CN model allows configuration of one single set of SaalUni parameters per nodeB.
It applies to all the nodeB SSCOP connections whatever the SSCOP-User.
Rule: IubTEG_RNC_Alcap_3
On the RNC, one set of saalUni parameters is configured and applies to all the sscop
connections (nbap and alcap sscop connections).
Aal2 Translation Table:
Within the RNC-IN model, the RNC aal2 translation table must be fill with the nodeB A2EA
and the associated aal2If component.
Rule: IubTEG_RNC_Alcap_4
The RNC aal2 translation table must be fill with the nodeB A2EA and the associated
aal2If component.
Only one aal2If instance must be assigned against one qaal2 endPoint A2EA.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 146/263
The RNC aal2 feature: prefixAddressing is not used on the Iub interface, since the RNC
allows up to one nodeB beyond the aal2Switch.
The alternative routing is not supported.
Alcap Cell Validity Timer
The RNC supports the Alcap Cell Validity Timer. It is configured per nodeB.
On Alcap SSCOP disconnection, the RNC rejects all the new aal2 connection establishment
requests and starts the Alcap Cell Validity timer.
At the expiration of the Alcap Cell Validity timer, the aal2 connections are released.
- If the RNC Alcap Cell Validity Timer is not provisioned (infinite value): the aal2
connections are maintained during the SSCOP disconnection, whatever the SSCOP
disconnection duration.
- If the RNC Alcap Cell Validity Timer is provisioned:
- The aal2 connections are maintained as long as the timer is running,
- At the expiration of the timer, the aal2 connections are released.
- If the RNC Alcap Cell Validity Timer = 0, the aal2 connections are released since the
SSCOP is disconnected.
The Alcap Cell Validity timer must be configured on only one aal2 node (endPoint or
relayPoint), either the nodeB or the RNC or the aal2Switch if present).
Assuming no aal2Switch on the Iub interface:
- When the RNC interworks with the iBTS nodeB then the Alcap Cell Validity timer
must be desactivated in the RNC. The SSCOP disconnection event is under control of
the nodeB.
- When the RNC interworks with the oneBTS nodeB, the Alcap Cell Validity timer
must be activated in the RNC since not available in the nodeB. The RNC controls the
SSCOP disconnection event.
Rule: IubTEG_RNC_Alcap_5
The RNC Alcap Cell Validity must be desactivated when Interworking with the iBTS
nodeB.
The RNC Alcap Cell Validity must be activated when Interworking with the oneBTS
nodeB.
Remark: To desactivate the RNC timer, the timer is not provisioned.
Aal2 Switch:
An aal2Switch may be inserted on the Iub interface. Nevertheless the ALU RNC doesnt allow
several NodeB beyond one aal2Switch. Indeed the alcap vcc is configured in the RNC per
nodeB (RNC/NodeB/CtrlPort/controlPortType). The ALU RNC accepts an Iub topology where
each aal2Switch is dedicated to one nodeB.
Rule: IubTEG_RNC_Alcap_6
If the aal2Switching function is required on the Iub interface, each aal2Switch node
must be dedicated to one single nodeB.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 147/263
3.6.15.1
3.6.15.2
TRANSPORT IDENTIFIERS:
The RNC equipment is composed of one logical RNC per PLMN sharing the RNC equipment.
One logical RNC is identified by its global RNC Id:
Global RNC Id = PLMN Id + RNC Id = MCC + MNC + RNC Id
One RNC Id is configured in the RNC equipment; it is common to all the logical RNC.
Rule: IubTEG_utranSharing_2
The RNC Id numbering plan of all the Plmn sharing the utran operators must be coordinated.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 148/263
The RNC is identified by one A2EA, and traffics with utran aal2 nodes (NodeB, neighbor RNC and
MGw):
Rule: IubTEG_utranSharing_4
The A2EA numbering plan must be coordinated between all the Plmn sharing the utran.
Example of utran network with utranSharing activated:
UE
UE
MGw1
MGw2
MGC1
Operator A:
CP & UP vcc
MGw10
Mc
Operator B:
UE
UE
Mc
NRI = 1
Nc
MGw1
CP & UP vcc
MGC2
NRI = 2
UE
UE
UE
UE
Iub
atm
atm
Shared
resources
RNC
RNC
UE
UE
NODE B
B
NODE
MGw10
Iu Plmn 1
Iu Plmn2
dedicated
resources
SGSN 1
NRI = 1
SGSN 2
NRI = 2
MSC
NRI = 1
MSC
NRI = 2
SGSN 1
NRI = 1
SGSN 1
NRI = 2
Iur
atm
atm
Shared RNC
RNC
Shared
Plmn2, RNC
RNC
Plmn2,
UE
UE
Plmn1, RNC
RNC
Plmn1,
ATM
ATM
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 149/263
3.7
RNC HYBRID
The hybrid RNC is populated with both the 16pOC3/Stm1 FP and the 4pGE FP and provides:
- Both atm and ip on the Iub interface,
- Only atm available on the IuCS and Iur interfaces,
- Both atm and ip on the IuPS interface.
The features related to the atm interfaces are described in the section 3.6 RNC ATM.
This section cover the hybrid RNC features related to the IP over Ethernet interfaces.
Rule: IubTEG_hybridRNC_1
On the Iub, the IP interface is dedicated to Hsdpa and Hsupa interactive/Background whereas the atm
is dedicated to R99, signaling, Hspa streaming, oam and as an option Hspa interactive/Background.
3.7.1
FP
3.7.1.1 4PGE FP
The 4 pGE FP provides 4 Ethernet accesses:
- Ethernet port throughput: 1 Gb/s
- FP throughput: 2,5 Gb/s.
3.7.1.1.1 PHYSICAL
The 4pGE FP is designed according to the MS3 architecture.
It is composed of the GQM/FQM ASIC, which determines the FP egress qos and TrafficManagement
capabilities.
It provides 4 ethernet ports each offering a transmission 1 giga bit/s in both directions on optical medium.
Each port can be independently configured as SX (1000Base-SX), or LX (1000BASE-LX):
- 1000BASE-LX interface:
The "LX" stands for Long wavelength lasers to transmit data over fiber optic cable.
- 1000BASE-SX interface:
The SX stands for Short wavelength lasers to transmit data over fiber optic cable.
Rule: IubTEG_4pGE FP_1
- The 1000BASE-LX interface supports single-mode optical fibers (SMF) or multimode optical
fibers (MMF).
- The 1000BASE-SX interface supports only multimode optical fiber.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 150/263
The configured maximum frame size value takes into consideration the ethernet frame fields: destination
and source addresses, the 4 bytes length Q-Tag if present, the protocolType, the payload and the CRC.
The Ethernet frame preamble is not taken into account.
The configured maximum ethernet frame size has been set in such a way to allow an IP packet 1500 bytes
length (default MTU value).
Rule: IubTEG_4pGE FP_2
The current configured maximum Ethernet frame size is 1518 bytes.
The current configured maximum Ethernet frame size is 1522 bytes when VLAN field inserted in
the frame.
3.7.1.1.3 AUTONEGOCIATION
The objective of the auto-Negotiation function is to provide the means to exchange information between
two devices that share a link segment and to automatically configure both devices to take maximum
advantage of their abilities.
Rule: IubTEG_4pGE FP_3
It is recommended that the link partner activates the auto-negotiation with remote fault encoding
and that auto-negotiation be enabled on the GigE port.
The auto-negotiation can be enabled or disabled for each GigE port (Lp Ethernet autoNegotiation
attribute).
3.7.1.1.4 QOS
FP Scheduler:
The 4pGE FP provides 8 classQueues per port.
The 4pGE FP scheduler applies the absolute PriorityQueuing algorithm to the two highest priority class
queues: EP0 and EP1 and applies the WFQ algorithm the the six lowest priority class queues.
Since the EP0 and EP1 class queues have been served, the scheduler shared the residual bandwidth
between the EP2 to EP7 class queues according to the weight assigned against these queues.
The scheduler terminates transmission of any IP packet from the served queue before visiting another
queue. The empty queues are skipped by the scheduler.
The 4pGE FP must be configured with:
- the mapping between each DSCP value and the classQueue,
- classQueue properties,
- The per DSCP discard policy.
DSCP mapping to classQueue:
Each DSCP value is mapped to the RNC proprietary parameter trafficClass, which determines
the priority assigned by the scheduler to the behaviourAggregate.
Several DSCP values may be mapped to one single trafficClass value.
The mapping between the DSCP value and the trafficClass value is set through the attribute: Vr
Dsd Phb trafficClass.
Range value: [critical, network, premium, platinum, gold, silver, bronze, standard].
Without customisation, the following default Qos mapping applies:
DSCP
CS7
trafficClass
Critical
CS6
Network
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 151/263
EF, CS5
Premium
CS4, AF4y
Platinum
CS3, AF3y
Gold
CS2, AF2y
CS1, AF1y
Silver
Bronze
DE
Standard
Table 3-23, trafficClass
Furthermore each trafficClass value is mapped to a schedulingClass value through the attribute
Vr Dsd Tc schedulingClass8Queues (sc8q).
This value is used to select one queue over the eight supported by the 4pGE FP port when
transmitting packets.
A higher schedulingClass value is assigned to the more delay sensitive behaviourAggregate.
The schedulingClass range value: [0, 7].
Without customisation, the following default mapping applies:
trafficClass
Critical
schedulingClass
7
Network
Premium
Platinum
6
4
Gold
Silver
Bronze
1
Standard
0
Table 3-24, schedulingClass
ClassQueues properties:
The 4pGE FP applying the WFQ algorithm to the EP2 to EP7 queues, a weight is assigned to
each EP2 to EP7 through the MBG component which determines queue serving policy of the
scheduler. A higher MBG value is assigned to the higher priority queue.
Without customisation, the following default mapping applies:
EP Queues:
EP0
MBG
Na
EP1
Na
EP2
EP3
50
25
EP4
EP5
10
7
EP6
EP7
3
Table 3-25, MBG
Taking into consideration the DSCP values specified for the current utran release and the qos mapping
done within the 4pGE FP, the following qos information mapping applies:
Rule: IubTEG_4pGE FP_4
Transport Qos information mapping:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 152/263
DSCP
CS6
AF4y
AF3y
AF2y
AF1y
DE
with y = (1, 2, 3)
trafficClass
critical
premium
network
platinium
gold
silver
bronze
Standard
schedulingClass
7
6
5
4
3
2
1
0
EP
0
1
2
3
4
5
6
7
MBG%
na
na
50
25
10
7
5
3
Queue Size
100 K
300 K
300 K
300 K
7000 K
4200 K
3000 K
2200 K
Discard policy:
A dropPrecedence value is assigned to each DSCP value through the attribute: Vr Dsd Phb
dropPrecedence.
Per classQueue, a queue congestion threshold is associated to each dropPrecedence value.
When receiving an IP packet from the backplane, according to the IP packet dropPrecedence
and the queue occupancy rate the IP packet is either enqueued or discarded:
- The IP packet is discarded if the queue occupancy rate is higher than the congestion
threshold associated to the IP packet dropPrecedence.
- The IP packet is enqueued if the queue occupancy rate is lower than the congestion
threshold associated to the IP packet dropPrecedence.
The dropPrecedence range value: [low, medium, high], while le low value indicates that the
behaviourAggregate is less candidate to discard compared to a high dropPrecedence
behaviourAggregate.
Without customisation, the following default qos mapping applies:
DSCP
CSx, AFx1, EF
dropPrecedence
Low
AFx2
Medium
AFx3, DE
High
table 3-26 Qos mapping: dropPrecedence
It is suggested to apply the RNC default dropPrecedence values:
Rule: IubTEG_4pGE FP_5
Transport dropPrecedence suggestion:
DSCP
dropPrecedence
AFx1, CS6
Low
AFx2
Medium
AFx3, DE
High
with x = (1, 2, 3, 4)
Ethernet QOS
P-Tag:
The 3 bits length P-Tag field is ignored on the reception of a valid frame and is set to 0 when
transmitting a Vlan tagged frame.
Rule: IubTEG_4pGE FP_6
The P-Tag is ignored by the RNC
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 153/263
Port mode:
Vlan mode:
EM
EM
LanApplication (La)
LanApplication (La)
Vlan
LinkToProtocolPort
LinkToProtocolPort
TEG
Figure 3-69, port mode versus Vlan mode components
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 154/263
Protocol:
The 4 bytes length Q-Tag field is inserted in any frames transmitted over a Vlan. The Q-Tag is
composed of different fields:
- Q-Tag / Tag Protocol Identifier field:
The RNC set the Q-Tag / Tag Protocol Identifier field with 0x8100 and accepts any received
frame with such a Tag Protocol Identifier value. The frame received with another Tag Protocol
Identifier values are discarded.
Rule: IubTEG_4pGE FP_10
The 4pGe FP accept any received tagged frame with Q-Tag / Tag Protocol ID = 0x8100
and discard received frame with other Tag Protocol ID value.
- VLAN Identifier field:
The 12 bits length VLAN field is set with a value in the range: [0-4095].
- Vlan ID = 0: the null-VLAN indicates that no VLAN is configured on the Ethernet
port.
- Vlan ID =1: indicates the port VLAN on the 4pGe FP. The port VLAN is
represented by the LanApplication component when the port is operating in VLAN
mode. In the Vlan mode, the received untagged or priority tagged frame are handle
by the port Vlan if present.
- Vlan ID = 4095: is discarded for IP applications
Rule: IubTEG_4pGE FP_11
As long as VLAN is configured on a RNC GE port, the 4pGe FP accepts any tagged
frame with a VLAN ID in the range [2-4094].
Any received tagged frames with an unknown VLAN or a Vlan ID = 4095 are discarded by the
RNC.
3.7.1.1.6 ARP
The 4pGE FP ARP table is dimensioned to support up to 500 entries per port and up to 1000 entries per
FP.
As an example:
- A RNC VR protocol port configured with a /30 subnet size consuming one 4pGE FP ARP
table entries,
- A RNC VR protocol port configured with a /24 subnet size consuming 252 4pGE FP
ARP table entries.
Rule: IubTEG_4pGE FP_12
The 4pGE FP ARP table supports up to 500 entries per port and up to 1000 entries per
FP.
3.7.1.1.7 SOC
IP
IP
Supported
IPv4
Not Supported
Ipv6
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 155/263
IP static routing
OSPF, RIP
ICMP
ECMP (note1)
ARP
IPSec
DHCP relayAgent
Fragmentation (note2)
DifferentiatedServices
PDR (protection Default Route)
Note1: The ECMP used as protection against a 4pGE FP failure causes a too long traffic disruption, >
1s)
Note2: Fragmentation is not actually performed on the 4pGe card since the MTU of the egress IP port
will always be greater than or equal to the incoming IP packet size.
Ethernet:
Ethernet
Supported
Auto negotiation
Not Supported
LAG
MAC Pause frame note1)
Note1: The MAC pause are not generated by the 4pGEFP, nevertheless the 4pGEFP responds to the
received MAC Pause frame by stopping the traffic on that port until that pause condition is removed.
3.7.2
RNC CAPACITY
The RNC capacity depends on the type and amount of component it is populated with and parameter
setting.
Parameter:
The setting of the RncIn/hardwareCapability component determines the RNC capacity:
Rule: IubTEG_RNC-Capacity_
- Set hardwareCapability = allPktServSP2FullDim when the RNC is populated with DCPS, CP4
and 16pOC3 MS3 FP and as an option gigaEth cards.
- Set hardwareCapability = allPktServSP2 when the RNC is populated with DCPS or PSFP, CP3
and 16pOC3 MS3 FP or classical 16pOC3 FP cards.
- Set hardwareCapability = all6mPktServ when the RNC is populated with PSFP, CP3 and
16pOC3 MS3 FP or classical 16pOC3 FP cards.
Avoid:
- hardwareCapability= allPktServSP2FullDim when RNC is populated with CP3.
- hardwareCapability= allPktServSP2 or all6mPktServ when RNC is populated with
CP4.
Capacity:
- When the RNC is populated with: DCPS, CP4, and MS3 and the hardwareCapability parameter =
allPktServSP2FullDim:
UA5-1-2
12 PSFP
4 DCPS
6 DCPS
8 DCPS
10 DCPS
12 DCPS
# nodeB
200
600
1000
1400
2000
2400
# cells
1200
612
1020
1428
2040
2448
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 156/263
- When the RNC is populated with: DCPS, CP3 or CP4 and the hardwareCapability parameter =
allPktServSP2:
UA6, hardwareCapability parameter allPktServSP2.
UA5-1-2
12 PSFP
4 DCPS
6 DCPS
8 DCPS
10 DCPS
12 DCPS
# nodeB
200
360
600
720
800
1200
# cells
1200
360
600
720
800
1200
- When the RNC is populated with: PSFP, CP3 and the hardwareCapability parameter = all6mPktServ:
UA6, hardwareCapability parameter all6mPktServ.
UA5-1-2
3.7.3
12 PSFP
4 PSFP
6 PSFP
8 PSFP
10 PSFP
12 PSFP
# nodeB
200
360
600
720
800
1200
# cells
1200
360
600
720
800
1200
IP COMPONENTS
3.7.3.1 IPIF:
The IpIf component identifies the remote UMTS node ip interface, e.g.: NodeB ip interface.
Remark: The ipIf component is supported only on the Iub interface (Not supported on the IuPS).
On the Iub interface, the IpIf is linked to the IubIf / Uplane identifying the nodeB.
The NodeB IP@ is dynamically assigned to the ipIf component.
The RNC may be connected to up to 2400 nodeB each having its own IP interface.
Rule: IubTEG_RNC IP Components_1
The ipIf component instance must be unique within the RNC.
The ipIf component instance range: [1, 5000] is reserved for the Iub interface
The cacm parameter is configured against each IpIf component and applies to all the bwPools under the
ipIf instance.
3.7.3.2 BANDWIDTHPOOL:
The bandwidthPool concept has been specified within the RNC to distinguish the nodeB aal2Paths
configured over different NodeB Transport media, e.g.:
- The NodeB paths configured over two different IMA linkGroups are grouped under two different
bwPools,
- The NodeB paths configured over different E1 (mode xPcm) are grouped under different bwPools,
- The NodeB paths configured over an IMA linkGroups and the NodeB paths configured over E1
(mix of xPcm and IMA mode) are isolated into different bwPools.
Moreover the aal2 paths configured over a nodeB IMA linkGroup may be distributed over different
bandwidthPools.
The composition of a bandwidthPool with a set of Path is done by configuration.
The bandwidthPool concept has been extended to takes into consideration:
- The nodeB ip interface: On the RNC side, the bandwidth reserved for a nodeB ip interface and the
bandwidth reserved for a nodeB atm interface are isolated into different bandwidthPools.
- The utranSharing: The traffic from the different PLMN sharing the utran may be as an option
isolated into different bandwidthPool.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 157/263
Asymmetrical traffic.
sharedForAllTrafficTypes bandwidthPool:
A sharedForAllTrafficTypes bandwidthPool may be specified only on the atm interfaces.
A wide range of UMTS trafficTypes selects such a bandwidthPool.
Within a sharedForAllTrafficTypes bwPool, the CM/backPressure applies to all the qos
streams with exception of the qos0 stream.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 158/263
Each bwPool is linked to one transportMap, see 3.6.9. Within the transportMap is specified the bwPool
properties:
- TransportMap/Preference specifies the bwPool type either sharedForAllTrafficTypes or
primaryForTrafficType,
- Transportmap/transportServiceEntry specifies the trafficTypes assigned to the bandwidthPool.
Rule: IubTEG_RNC IP Components_8
Each bwPool must be associated to a transportMap instance with the appropriated interfaceType.
Exemple of one atm sharedForAllTrafficTypes bwPool and one ip primaryForTrafficType bwPool
associated to one nodeB:
RNCIN
RNCIN / IubIf
aal2If i
TransportMap i
interfaceType: Iub
BwPool/x
preference: sharedForAllTrafficTypes
qos0
path
qos1
path
qos2
path
qos3
path
transportServiceEntries:
[TC=conv, RbSetQos=0, ]
=> qos0
[TC=stream, RbSetQos=1+2, ]
=> qos1
[TC=interact, RbSetQos=1, ]
=> qos2
=> qos3
ipIf i
interfaceType: Iub
preference: primaryForTrafficType
BwPool/y
transportServiceEntries:
ipFlow/i
qos 3
TEG
Figure 3-70, NodeB with one atm bwPools and one ip bwPool
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 159/263
Topology
N*E1+IMA
Hybrid Iub
2 IMA
1 IMA
bwPool/Preference
Transport
N * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Atm
1 * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Ip
1 * sharedForTrafficTypes
Atm
1 * primaryForTrafficType
Atm
1 * sharedForTrafficTypes
Atm
UtranSharing:
Per definition a PLMN Common bwPool is a bwPool shared by all the PLMN sharing the Utran
whereas a PLMN specific bwPool is a bwPool dedicated to one PLMN sharing the Utran.
A PLMN Common bwPool and a PLMN specific bwPool may be either primaryForTrafficType or
sharedForAllTrafficTypes bwPool.
On the iub interface may be configured a mix of PLMN Common bwPool and a PLMN specific
bwPool.
Per PLMN sharing the utran, may be configured one or several bwPool for atm, ip or mixed of atm and
ip interfaces.
Rule: IubTEG_RNC IP Components_9
For the case of PLMN specific bwPool, the bwPool component must be configured with the
corresponding PLMNId.
For the case of PLMN common bwPool, the bwPool component must be configured with the
PLMNId set to Zero.
Case of RNC configured with both PLMN common bwPool and PLMN specific bwPool for a
specific nodeB, the RNC selects first the resources from the PLMN specific bwPool, if exhausted
selects the resources from the PLMN common bwPool.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 160/263
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
atmSwitch
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
RNC
NodeB
qos0 Paths
qos1 Paths
qos2 Paths
qos3 Paths
IMA 3 E1
PLMN A specific bwPool bwPool4
IP router
FE
IubIf i
aal2If i
ipIf i
TEG
Figure 3-71, bwpool in the utranSharing 2 PLMN context, exemple
Asymmetrical traffic:
To handle separately hsdpa and Hsupa flows, two different bandwidthPools must be specified linked to
two different transportMaps:
- The hsdpa is handle by a primaryForTrafficType bwPool linked to a transportMap including a
transportServiceEntry set with ulDlPreference: dlPref,
- The hsupa is handle by a SharedForTrafficTypes bwPool linked to a transportMap including a
transportServiceEntry set with ulDlPreference: ulDlPref.
Rule: IubTEG_RNC aal2 Component
The asymmetrical traffic handling applies:
- only to the hspa I/B traffic,
- only to on the Iub interface,
- on both the atm and the ip interfaces.
Case of hybrid Iub:
- hsupa handles by the sharedForTrafficTypes bwpool over atm interface,
- hsdpa handles by the primaryForTrafficType bwpool over ip interface,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 161/263
RNCIN
RNCIN / IubIf
aal2If i
TransportMap i
interfaceType: Iub
BwPool/x
preference: sharedForAllTrafficTypes
qosx
path
tse:
tse: [TC=interactive, RbSetQos=2, ulDlPreference = ulPref ] => qos3
tse: [TC=backGround, RbSetQos=2, ulDlPreference = ulPref] => qos3
qos3
path
TransportMap j
ipIf i
interfaceType: Iub
preference: primaryForTrafficType
BwPool/y
ipFlow/i
qos x
TEG
Figure 3-72 Asymmetrical bwPools case of hybrid iub
Robustness:
The robustness mechanism applies to the asymmetrical traffic: Hsdpa or Hsupa, identified by the
received radioBearerType UMTS EI
Assuming the configuration indicated in the Figure 3-72 Asymmetrical bwPools case of hybrid iub:
In normal condition, the admissionControl assigns the hsdpa traffic to the bwPool/y.
In case of bwPool/y bandwidth exhaustion, the admissionControl assigns the hsdpa traffic
to the bwPool/x.
On call establishment, the admissionControl identifies the different TransportMap(s) including tse
satisfying the call qos characteristics.
If several TransportMaps are identified, the ulDlPreference parameter is taken into consideration for
determing the most preferred TM:
- A tse with ulDlPreference = ulPref or dlPref is more preferred than a tse with
ulDlPreference=ulDlPref.
- A tse with ulDlPreference = ulDlPref is more preferred than a tse with
ulDlPreference=noPref.
If not enough available bandwidth in the bwPool linked to the most preferred transportMap, the
admissionControl assigns the call to the bwPool linked to the less preferred transportMap.
3.7.3.3 IPFLOW:
One ipIf/bwPool is populated with one or up to 4 ipFlow component(s), each configured with different
qos.
Nevertheless, in UA6 only one qos3 stream is supported under an ipIf/bwPool, therefore one ipIf/bwPool
is populated with one single ipFlow set with either qos3.
Furthermore is configured against each ipFlow component, the expected traffic through the attributes:
- downLinkCommitedRate (kb/s)
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 162/263
- upLinkCommitedRate (kb/s)
- downLinkPeakRate (kb/s)
- upLinkPeakRate (kb/s)
The per ipFlow rates are involved in the downlink congestionManagement mechanism, and also in the
downlink and uplink transport IP admissionControl.
iubIf j
SignalingBearer
userPlane
ipLink
ipIf i
ipLinkToIpif: ipIf i
cacm
BwPool/y
transportMap
congestionmanagement
PLMN Mcc & Mnc (utranSharing)
qosnBwReservation
(with n =[0, 1, 2, 3]
IP Flow:
qos3
downLinkCommitedRate (kb/s)
upLinkCommitedRate (kb/s)
downLinkPeakRate (kb/s)
upLinkPeakRate (kb/s)
transportMap i
congestionManagement i
TEG
Figure 3-73, RNC IP components
3.7.4
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 163/263
- The consolidated VR composition consists in assigning one single VR for both Iub userPlane traffic
and IuPS traffic.
Indeed the RNC is configured with 5 VR:
- 1 VR dedicated to the OAM traffic,
- 1 VR dedicated to the IuPS userPlane, controlPlane traffic and the Iub userPlane traffic,
- 1 VR dedicated to the locationServices traffic,
- 1 VR dedicated to the cellBroadcast traffic,
- 1 VR dedicated to the RNC internal traffic.
Exemple of VR instance number:
- VR0 dedicated to the OAM traffic,
- VR1 dedicated to the IuPS userPlane, controlPlane traffic and the Iub userPlane traffic,
- VR3 dedicated to the locationServices traffic,
- VR4 dedicated to the cellBroadcast traffic,
- VR2 dedicated to the RNC internal traffic.
Note: this VR instance number example is used within the TEG to identify each virtualRouter.
Remark: For both VR compositions, the oam, the internal, the locationServices and cellBroadcast traffic
are served by their own separate VR.
Rule: IubTEG_RNC IP VR_1
One VR is dedicated to the Iub userPlane IP traffic, if Segmented VR.
One VR is shared between the Iub userPlane and the IuPS traffic, if Consolidated VR
The VR is dedicated to the Iub OAM traffic.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 164/263
RNC,
RNC, segmented
segmented VR
VR
IuPS
Hybrid Iub
OAM VR 0
PP
PP PP
PP
UP VR 5
PP
PP PP
PP
IuPS VR 1
PP
PP PP
PP
LS VR 3
CBS VR 4
int VR 2
PP
PP
PP
PP
PP
PP
4pGE
4pGE
RNC,
RNC, consolidated
consolidated VR
VR
Iub
OAM VR 0
PP
PP PP
PP
PP
PP PP
PP
4pGE
LS VR 3
CBS VR 4
int VR 2
PP
PP
PP
PP
PP
PP
4pGE
TEG
Figure 3-74, RNC VR composition
Segmented VR advantage:
3.7.5
LOCALMEDIA
Reference: [R161]
The localMedia is a RNC IP media functionality which provides a functional interface to the PMC that
are unaware of the Virtual Router. It provides IP forwarding capability to the PMC on the PSFP/DCPS
FP.
The localMedia is centrally located on the CP.
There is one instance of the localMedia within the RNC.
The localMedia supports up to 32 interfaces each identified by an instance in the range [0, 31].
A trafficType value is assigned to the LocalMedia interface which identifies the nature of the traffic
supported by the interface.
TrafficType values:
- trafficType = iubUPlane: LocalMedia interface dedicated to Iub User Plane traffic,
- trafficType = iubUPinternal: LocalMedia interface dedicated to the PMC-TMU,
application: UMTS Proprietary loopBack on Iub routes,
- trafficType = ss7CPlane: LocalMedia interface dedicated to IuPS Control Plane traffic,
- trafficType = oam: LocalMedia interface dedicated to the RNC Oam traffic.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 165/263
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 166/263
RNC
RNC
TMU0
TMU0 RAB
RAB
TMU13
TMU13 RAB
RAB
RAB
RAB
M
M 00
M
M 11
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
OMU0
OMU0
OMU1
OMU1 PC0
PC0 PC11
PC11
PP
PP
VR1
PP
nodeB (hybrid)
(hybrid)
nodeB
IP
IP
VR0
PP
PP
(V)LAN
MPE
GigE
GigE xx
GigE
GigE xx
R99 UP
R99 CP
PP
VR5
Iub
If/2
oam
tT: iubUP
If/5
If/6
tT: rnc
If/0
R99 traffic,
Signaling,
Oam
Hspa stream.
Hspa I/B (opt)
Hspa I/B.
tT: iubUPint
LM
LM
PP
MPE
16pOC3
16pOC3
16pOC3
16pOC3
ATM
ATM
RNC
RNC
Figure 3-76
Consolidated VR
TMU0
RAB
TMU0 NI
NI 00 RAB
RAB
RAB
TMU13
RAB
RAB
TMU13 NI1
NI1 over
RAB
RAB
The user traffic handle
the
RNC
IP interface is routed through the VR5 in case of the VR segmented
RAB
RAB
RAB
RAB
mode, whereas
VR1
in
case
of
the
VR
consolidated mode.
M
PDC0
M 00 PDC0
OMC
eth
OMC
eth
IP
PDC1
M
PDC1 RAB
M 11
IP
RAB
RAB
RAB
PDC2
PDC2
Assuming the VR
segmented mode, the VR5 is configured with one or more PP to the network. More
PDC3
PDC3
OMU0
OMU0
than oneOMU1
PP to the
network
may
required if Iub layer2 backhaul and the subnet size doesnt allow to
bePC9
PDC9
PC0
OMU1
PDC9
PC0
PC9
address all the connected nodeB.
localMedia
CP
localMedia
CP
tT: CBS
If/4
MPE
MPE
If/2
tT: LS
If/3
SS7
oam
If/1
tT: internal
tT: rnc
If/0
If/7
tT: ss7CP
& Iub
tT: iubUP
If/5
IuPS CP & UP
If/6
tT: iubUPint
(V)LAN
MPE
NodeB
NodeB
16pOC3
16pOC3
16pOC3
16pOC3
IP
IP
GigE
GigE xx
GigE
GigE xx
SGSN
SGSN
TEG
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 167/263
tT = iubUPinternal
PP
PP
TMU 00
TMU
TMU 11
TMU
itf = 6
VR 55
VR
TMU 11
11
TMU
4pGE
4pGE
PP
PP
tT = rnc
itf = 0
VR1
VR1
PP
PP
PP
PP
RAB
RAB
RAB
RAB
RAB
RAB
localM
localM
PC 00
PC
PC 11
PC
PC9
PC9
tT = iubUPlane
itf = 5
(V)LAN
(V)LAN
TEG
Figure 3-77 Segmented VR, traffic flows
The UMTS Proprietary heartbeat checks the continuity of the overall Iub userPlane datapath between the
RNC and the Node B.
3.7.6
PDR
Reference: [R161]
The Protected default route (PDR) is a layer3 sparing mechanism which guarantees a traffic disruption
less than one second; this time includes the failure detection and the traffic diversion.
The PDR is a protection against port and line failure.
The PDR feature is supported for IP flows over the 4pGE FP.
Rule: IubTEG_PDR_1
The PDR is available only for IP route with nextHops over the 4pGE FP.
The PDR may be used for protection as long as:
- No routing protocol running on the RNC (Vr Ip Ospf ecmpStatus = disabled),
- The ECMP is deactivated (Vr Ip Static maxEcmpNextHops = 1)
Rule: IubTEG_PDR_2
When PDR is enabled, maxEcmpNextHops must be set to 1, Vr Ip Ospf ecmpStatus must be
disabled.
Only the VR default route (IP@=0.0.0.0, 0.0.0.0) can be used for the Protected Default Route.
Rule: IubTEG_PDR_3
If PDR is used, only the static default route must be the protected route.
The VR default route acts as a protected default route since the protected attribute is set to yes (Vr Ip
Static Route protected).
Rule: IubTEG_PDR_4
For enabling the PDR, the RNC attribute Vr Ip Static Route protected must be set to yes against
the default route.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 168/263
R
R 33
Y
IP@ 3-2
IP
Static
Route = 0.0.0.0, protected=y
NextHop = IP@ 1-2 /30,
lan
RNC
RNC
Path 3
GE
VR
VR
NodeB
NodeB
PP3
metric=1
PP2
PP1
R
R 22
NodeB
NodeB
Backhaul
Backhaul
IP@ 2-2
lan
lan
lan
metric=2
Route = X.X.X.X,
NextHop = IP@ 3-2 /30
lan
GE
Path 2
GE
GE
FP1
FP1
GE
FP2
FP2
SGSN
SGSN
IP@ 1-1
R
R 11
Y
IP@ 1-2
lan
GE
Path 1
TEG
Figure 3-78 PDR with 3 routes and 3 routers
Comments:
Assuming metric=1 assigned to the RNC VR PP1 and metric=2 assigned to the RNC VR PP2,
Under normal condition:
- The RNC sends the IP packets with DA = x.x.x.x to router 3,
- The RNC sends the IP packets with DA x.x.x.x to router 1.
Under Path1 failure:
- The RNC forwards the IP packets with DA x.x.x.x to the router 2,
Under Path3 failure:
- If the RNC is aware about the path3 failure, it forwards the IP packets with DA
x.x.x.x to the router 1.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 169/263
In this case the ICMP Heartbeat is not a trigger for PDR since the ICMP heartbeat is not
supported on the more specific IP route ( 0.0.0.0).
A protected static default route should be configured with several nextHops in such a way to be able to
divert the traffic to a less preferred nextHop in case of failure of the most preferred nextHop.
Whatever amount of nextHop(s) assigned to the protected default route, only one nextHop, the most
preferred, is active for forwarding the IP traffic. On failure of the more preferred nextHop, the IP traffic is
diverted on one of the less preferred nextHop(s).
Rule: IubTEG_PDR_6
At least 2 nextHops and up to 4 nextHops are assigned to a protected default route.
Each PDR nextHop belongs to different subnets as per the VR PP definition.
To provide maximum traffic protection, the different PDR nextHops should transmit over different paths
when available:
Rule: IubTEG_PDR_7
Each PDR nextHop should be configured over different Ethernet links from different 4pGE FP
and should be connected to different adjacent IP routers.
The more specific route nextHop and the PDR nextHop should be configured over different
Ethernet links from different 4pGE FP and should be connected to different adjacent IP routers.
The duration of the failure detection and PDR IP traffic diversion from the failed nextHop to an active
nextHop is less than 1 second (with exception of the ICMP heartbeat trigger).
The following figures provide different topologies when PDR is activated on the RNC side, according to
one or several adjacent IP routers, 2 or more IP routes between the RNC and the routers:
RNC
RNC
R
R 11
Y
GE
GE
lan
IP@ 2-1
Group 1
lan
PP2
IP@ 1-1
10.32.2.253
lan
Backhaul
Backhaul
NodeB
NodeB
IP@ 1-2
NodeB
NodeB
10.32.2.128
PP1
X
IP@ 2-2
Group 2
VR
VR
lan
FP0
FP0
GE 0
GE 1
GE 2
GE 3
NodeB
NodeB
10.32.2.1
FP1
FP1
GE 0
GE 1
GE 2
NodeB
NodeB
10.32.2.127
GE 3
TEG
Figure 3-79, with 2 routes, 1 router, assuming up to 253 nodeB
Remarks: a solution with one router is less desirable since one single point of failure.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 170/263
RNC
RNC
RNC Iub VR routingTable:
VR /x
VR
VR
Group 2
PP1
IP@ 1-2
10.32.2.128
IP
Static
Route = 0.0.0.0, protected=y
NextHop = IP@ 1-2 /30
metric = 1
IP@ 2-1
NodeB
NodeB
PP2
IP@ 1-1
R
R 11
GE
lan
Path 1
lan
lan
NodeB
NodeB
Backhaul
Backhaul
10.32.2.253
Group 1
NodeB
NodeB
R
R 22
Y
10.32.2.1
FP0
FP0
GE 0
GE 1
GE 2
GE 3
IP@ 2-2
lan
GE
Path 2
NodeB
NodeB
FP1
FP1
GE 0
GE 1
GE 2
GE 3
10.32.2.127
TEG
Figure 3-80, PDR with 2 routes, 2 routers, assuming up to 253 nodeB
Group 4
NodeB
NodeB
10.32.3.128
R
R 11
NodeB
NodeB
GE
FP0
FP0
GE 0
GE 1
GE 2
NodeB
NodeB
GE 3
R
R 22
10.32.2.128
Group 1
lan
IP@ 2-2
10.32.2.253
lan
lan
lan
IP
Static
Route = 0.0.0.0, protected=y
NextHop = IP@ 1-2 /30
metric = 1
NextHop = IP@ 2-2 /30
metric = 2
NextHop = IP@ 3-2 /30
metric = 3
NextHop = IP@ 4-2 /30
metric = 4
Route = 10.32.2.0 /25
NextHop = IP@ 2-2 /30
X
IP@ 4-2
NodeB
NodeB
PP4
IP@ 4-1
Group 2
IP@ 2-1
GE
Backhaul
Backhaul
NodeB
NodeB
PP2
lan
lan
10.32.3.127
PP3
IP@ 3-1
lan
10.32.3.1
IP@ 1-1
NodeB
NodeB
PP1
IP@ 1-2
Group 3
VR
VR
X
IP@ 3-2
10.32.3.253
RNC
RNC
lan
FP1
FP1
GE 0
GE 1
GE 2
GE 3
NodeB
NodeB
GE
10.32.2.1
GE
NodeB
NodeB
10.32.2.127
TEG
Figure 3-81, PDR with 4 routes and 2 routers, assuming up to 400 nodeB
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 171/263
3.7.7
ICMP HEARTBEAT
Reference: [R161]
As long as no IP routing protocol running on the RNC, the way to detect failure on the interface consists
in activating the ICMP Heartbeat.
The ICMP heartbeat checks the continuity of the IP path between two adjacent IP nodes transparently
through the layer2 nodes.
Rule: IubTEG_ICMP_0
The RNC supports the ICMP Heartbeat on the default route (0.0.0.0) only. Not supported on more
specific route.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 172/263
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 173/263
RNC NH
IP router
ICMP EchoRequest
ICMP EchoReply
Periodicity = 1 s
ICMP EchoRequest
ICMP EchoReply
Periodicity = 1 s
ICMP EchoRequest
ICMP EchoRequest
ICMP EchoRequest
ICMP EchoRequest
deadInterval = 3 s
NH down
ICMP EchoRequest
ICMP EchoReply
NH up
TEG
The ICMP Heartbeat allows the RNC to be aware about a failure occurring on a not-directly-connectedto-RNC layer 2 interface:
RNC
RNC
Router
GE
GE
GE
GE
Eth
Eth
Bridge
Bridge
TEG
Remark: The preferred PDR nextHop is the one with up heartbeat state, the lowest metric assigned.
Miscellaneous:
- TTL: The RNC inserts the ICMP hearbeat within an IP packet set with TTL=64,
- DSCP: The RNC marks the IP packet containing the ICMP hearbeat according to the attribute
value: Vr Dsd phbGeneralSource (phbG).
3.7.8
QOS
Reference: [R160]
The differentiedServices Qos model applies into the UTRAN network.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 174/263
IUB interface
RbSetQos
R99
Conv
+cSRB+dSRB
R99 Streaming
R99 I/B
Hspa I/B+Streaming
Conversational
Common
Signaling
Streaming
Interactive
Background
Streaming
Interactive
Background
Since the Transport qos information are correctly mapped between each others, the final objective is to
mapped each different UMTS flows to a specific DSCP value in such a way each umts flow received the
expected qos treatment and is correctly marked.
The UMTS qos information are mapped to the Transport Qos information through the configurable
TransportMap RNC component.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 175/263
Rule: IubTEG_Hybrid-RNC_Qos_7
Whatever IP over atm or IP over Ethernet UTRAN interface, the differentiatedServicesDomain
must be configured at VR level.
The set of available DSCP values for the user IP packets is determined by the choice of the Vr
DifferentiatedServicesDomain (dsd) component instance:
DSD instance
multiService
DSCP
CSx, EF, AFxy, DE
classSelector
CSx
assuredForwarding
AFxy, CS6, DE
packetVoice
wirelessUmts
Custom
CS6, DE
Notes: x is in the range [0 to 7] for the CS DSCP, [1 to 4] for the AF DSCP, and y in the
range [1 to 3]. The CS0 is equivalent to Default DSCP then removed from the text.
Only one differentiatedServicesDomain instance can be enable per VR and applies to all the VR ports.
Even if the DSD component is an optional Router component, it must be set in the Umts context:
Rule: IubTEG_Hybrid-RNC_Qos_8
One DifferentiatedServicesDomain instance must be configured to allow a flexible tagging.
The suggested DSD instance: assuredForwarding.
Beside the non user IP packet tagging is specified when setting the following attributes:
- Vr Dsd phbRoutingSource (phbR): set with the DSCP value applying to the IP routing
packets. Range value: [EF, AFxy, CSx, DE).
- Vr Dsd phbGeneralSource (phbG): set with the DSCP value applying to the non user and non
routing IP packets, e.g.: applying to the ICMP echo request/reply IP packets. Range value:
[EF, AFxy, CSx, DE).
The qos treatment applying to the IP packets depends on the DSCP and how each DSCP value is mapped
to the FP Qos parameters, see3.7.1.1.4.
3.7.9
TRANSPORTMAP
The TransportMap realizes Classification for atm and ip interfaces and moreover Marking for the ip
interface:
- Classification:
- Up to 4 UMTS streams are identified called: qos0, qos1, qos2 and qos3,
- The classification is achieved based on the Umts qos information: trafficClass, RbSetQos,
ARP-PL, THP,
The congestionManagement applies per umts stream.
- Marking:
- A DSCP value is assigned per Umts stream identified by the Umts qos information:
trafficClass, RbSetQos, ARP-PL, THP.
Remark: The transportMap is the way to configure the Umts to Transport qos mapping table within the
RNC.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 176/263
The transportMap components apply to all the utran interfaces, with exception of the IuPS.
Several transportMap tables may be configured within the RNC.
Rule: IubTEG_Hybrid-RNC_TMap_1
The RNC may be configured with up to 64 transportMap components.
A transportMap is linked either to an ipIf bwPool, an aal2if bwPool or an aal2If (as long as no bwPool
configured under the aal2if, case of IucsIf or IurIf). One TransportMap may be shared between several
instances of ipIf bwPool, aal2If bwPool and aal2If, may also be shared between different utran interfaces.
Remark: No transportMap linked to ipFlow, aal2Path or iuPS components.
Rule: IubTEG_Hybrid-RNC_ TMap _2
Each bwPool or aal2If (if no declared bwPool) configured on the Iub, Iur and IuCS interfaces must
be linked to one or several transportMap (s).
A transportMap is configured with the following parameters:
RNCIN
TransportMap i
interfaceType:
Iub, Iur, IuCS, ( not iuPS)
preference:
sharedForAllTrafficTypes, or
primaryForTrafficType(only Iub case).
transportServiceEntry 1:
[TC, RbSetQos, ARP PL, Thp] => (DSCP), qos i
ulDlPreference.
transportServiceEntry n:
[TC, RbSetQos, ARP PL, Thp] => (DSCP), qos i
ulDlPreference.
TEG
Figure 3-82, transportMap parameters
- InterfaceType:
Values: [Iub, iuCs, Iur, (not iuPS)]
One transportMap may be configured with different interfaceType values, in other
words a transportMap may be allocated to different Utran interfaces.
- Preference:
Values: [sharedForAllTrafficTypes, primaryForTrafficType]
The setting of the Preference parameter determines the nature of the bwPool the
transportMap is connected to.
The Preference parameter is not taken into consideration by the admissionControl
when selecting a bwPool.
The sharedForAllTrafficTypes preference can be assigned only to an atm bwPool.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 177/263
rbSetQos
ARP-PL
THP
OUTPUT Values
UlDlPreference
DSCP
Qos i
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 178/263
RNCIN
RNCIN
IubIf
aal2If i
TransportMap 1
interfaceType: Iub/IuCS, Iur
BwPool/x
qos/i Paths
Preference: sharedForAllTrafficTypes
qos/j, Paths
TransportMap 2
interfaceType: Iub
ipIf i
Preference: primaryForTrafficType
BwPool/x
ipFlow/i
IucsIf
Congestionmanagement i
aal2If i
qos/i, path/m
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
IurIf
Congestionmanagement j
aal2If i
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
qos/i, paths
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
qos/j, paths
TEG
Figure 3-83, transportMap exemple
On the RNC IP interface, the transportMap/2 table applies per default (3.6.9)
3.7.10.1
EQUIVALENTBITRATE
See 3.6.10.1
3.7.10.2
INTERFACE BANDWIDTH
On the atm interface, the admissionControl determines the aal2path bandwidth for each direction based
on the configured UL and DL vcc trafficDescriptor and the generic CAC algorithm:
- Cbr vcc, ECRgcac = PCR c/s
- Vbr vcc, ECRgcac = 2*PCR*SCR/(PCR+SCR) c/s
- Ubr+ vcc, ECRgcac = MDCR c/s,
- Ubr vcc, ECRgcac = 0.
On the ip interface, the admissionControl determines the ipFlow bandwidth based on the configured UL
and DL ipFlow peak and committed rates and the generic CAC algorithm:
ERgcac = 2*PR*CR/(PR+CR) kb/s
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 179/263
The bandwidth granulary that the admissionControl takes into consideration for the regulation is
configured through the cacm parameter.
The cacm parameter is configured against an aal2if and an ipIf component, and applies to all the bwPools
under the aal2If and the ipIf components.
aal2If i
cacm
ipIf i
cacm
BwPool/x
BwPool/y
qosnBwReservation
qos 0
path
path
qos 1
path
path
qos 2
path
path
qos 3
path
path
iubIf 1
SignalingBearer
userPlane
aal2LinkToaal2if: aal2If i
ipLinkToIpif: ipIf i
BwPool/y
qosnBwReservation
qos 3
path
path
qosnBwReservation
IP Flow, qos3
congestionManagement i
transportMap j
congestionManagement n
transportMap m
congestionManagement x
transportMap y
TEG
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 180/263
- Cacm = ipIf: The availableBandwidth taken into consideration by the admissionControl is the
calculated total bandwidth per bwPool and per direction,
E.g.: 1 bwPools under one ipIf then:
- Cacm= path: The availableBandwidth taken into consideration by the admissionControl is the
bandwidth per aal2Path and per direction,
aal2Path UL availableBandwidth = vcc UL ECRgcac,
aal2Path DL availableBandwidth = vcc DL ECRgcac.
- Cacm= qos: The availableBandwidth taken into consideration by the admissionControl is the
calculated total bandwidth per bwPool, per qos and per direction,
The cacm qos value applies whatever atm or ip interface.
Furthermore when setting the qosnBwReservation with non zero value, the admissionControl takes
into consideration a additional bandwidth portion available for all the qos.
The common for all qos bandwidth portion is taken into consideration by the admissionControl on qos
i call establishment when the qos i availableBandwith is exausted.
The qosnBwReservation parameter value is taken into consideration by the admissionControl on both
downLink and upLink.
Rule: IubTEG_Hybrid-RNC_AC_4
The qosnBwReservation is applicable only if cacm=qos.
The qosnBwReservation parameters are either configured against the bwPool component or against
the aal2If then apply to all the bwPool under the aal2If.
Case of atm interface, the availableBandwidth is the sum of the bandwidth of all the vcc for one
aal2Qos within a bwPool, assuming one bwPool under an aal2If then:
Per qos available bandwidth:
Case of ip interface, the availableBandwidth is the sum of the bandwidth of all the ipFlow for one qos
within a bwPool, assuming one bwPool under an ipIf and one ipFlow under the bwPool then:
Per qos available bandwidth:
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 181/263
bwPool x
Available bw =3200 c/s
aal2If i
Cacm = qos
qos0BwReservation=60%
qos1BwReservation=60%
qos2BwReservation=60%
qos3BwReservation=100%
BwPool/x
qos 0 Path, ul/dl ECRgcac=1000 c/s
qos 1
qos 2
ipIf i
Cacm = qos
BwPool/y
qos3BwReservation=100%
qos 3
ipFlow, ul/dl ERgcac=10000 kb/s
TEG
bwPool y
Available bw =10000 B/s
qos 3
Rule: IubTEG_Hybrid-RNC_AC_5
In such a way qos3BwReservation > 0% is effective then:
- a non nul bandwidth must be assigned to the qos3 vcc, therefore the ubr serviceCategory must
not be assigned to the qos3 vcc,
- a non nul bandwidth must be assigned to the qos3 ipFlow.
3.7.10.3
ALGORITHM
See 3.6.10.3
3.7.10.4
TRAFFICMEASUREMENT
NT_UL_Watermark_EBR_Aal2If
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 182/263
NT_UL_WaterMark_EBR_IpIf
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
NT_DL_Watermark_EBR_Aal2If
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
NT_DL_WaterMark_EBR_IpIf
- Type: cumulative,
- Granularity: qos,
- Definition:
Watermark of allocated uplink EBR during the CAC (reported by TRM) expressed in percentage
of the total bandwidth pool capacity.
The purpose is to look for a trend. For example if the High watermark is consistently very high,
obs period after the period, it means that this one BW pool gets selected very often.
For both algorithms and per qos, the RNC measures the per qos realTime traffic and determines
thresholds which are based on the configured per qos bandwidth and configured per qos parameters:
- qosDt(n), for the qosDiscard thresholds, with n=[0, 1, 2, 3],
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 183/263
3.7.11.1
CONGESTIONMANAGEMENT TABLE:
The congestionManagement parameters involved in the qosDiscard and backPressure thresholds setting,
are configured through the RncIn/CongestionManagement tables.
Rule: IubTEG_Hybrid-RNC_CM_2
The RNC supports up to 64 congestionManagement tables.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 184/263
RNCIN
RNCIN
aal2If i
CongestionManagement i
BwPool/x
path/i
path/j
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
2
BwPool/y
CongestionManagement j
path/k
path/l
ipIf i
3
BwPool/u
CongestionManagement k
Activation: [qosDiscard only, qosDiscard+backPressure]
ipFlow/i
qosBackPressureThreshold (qosBPt) 0 0 1 x 2 y 3 z
ipFlow/l
qosDiscardThreshold, qosDt 0 0 1 x 2 y 3 z
TEG
Figure 3-86, congestionManagement links
3.7.11.2
The congestionManagement algorithm provides two different behaviours according to the setting of the
RncIn/enhancedQos parameter:
- If enhancedQos=disable, the congestionManagement provides the UA5 equivalent behaviour:
Emulation of the UA5 behavior, with some variations:
o New formula for Txoff,
o New formulas for qosDiscard and qosBackPressure thresholds,
o The congestionFlag is inserted in the Xoff signal, always set to No.
Remarks:
o Supports up to 3 qos, No support of Hspa streaming,
o GBR and minBr not supported,
Rule: IubTEG_Hybrid-RNC_CM_5
The RncIn enhancedQos parameter must be set to disable, when the congestionManagement
UA5 equivalent behavior is preferred.
-
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 185/263
THP
minBrForR99
minBrForHsdpa
Interactive
16 kb/s
16 kb/s
Interactive
8 kb/s
8 kb/s
Interactive
8 kb/s
8 kb/s
backGround
na
Rule: IubTEG_Hybrid-RNC_CM_6
The RncIn enhancedQos parameter must be set to enable, when the congestionManagement
UA6 behavior is preferred.
Rule: IubTEG_Hybrid-RNC_CM_7
The RncIn enhancedQos parameter must be set to enable when the congestionManagement has
to take into consideration the GBR for streaming and minBrForHspa and minBrForR99 for
interactive/Background
3.7.11.3
Since up to 4 qos are supported, up to four qosDiscard thresholds and 4 qosBackPressure thresholds are
set then one qosDt parameter is set per qos and one qosBP parameter is set per qos.
Rule: IubTEG_Hybrid-RNC_CM_8
qosDt(0) qosDt(1) qosDt(2) qosDt(3)
A qosBP(n)=0 means that the backPressure doesnt apply for the qos n.
For the case of no hspa streaming supported, two sets of qosDiscardThreshold values are suggested which
satisfy two different Iub contexts:
- The context basicVPT trafficShaping on the Iub interface.
It encompasses 3 Iub configurations:
o 1/ the trafficShaping at VP level is activated in the RNC 16pOC3/Stm1 FP Iub
interfaces, or
o 2/ the remote POC is populated with a FP supporting basicVPT and the trafficShaping
at VP level is activated in the remote POC on the atm interfaces toward the NodeB, or
o 3/ the remote POC is populated with a FP supporting standardVPT, the remote POC
acts as a VP switch (not VC switch) and the trafficShaping at VP level is activated in
the remote POC on the atm interfaces toward the NodeB.
For these 3 Iub configurations, apply on the RNC the congestionManagement Discard Threshold
set of values case of basicVPT trafficShaping on the Iub interface.
- Context No basicVPT trafficShaping on the Iub interface:
o 1/ the trafficShaping is not activated neither in the RNC nor in the POC,
o 2/ the remote POC is populated with a FP supporting standardVPT, the remote POC
acts as a VC switch (not VP switch) and the trafficShaping at VP level is activated in
the remote POC on the atm interfaces toward the NodeB.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 186/263
For these two Iub configurations, apply on the RNC the congestionManagement Discard
Threshold set of values case of No basicVPT trafficShaping on the Iub interface.
Rule: IubTEG_Hybrid-RNC_CM_9
Case of No basicVPT trafficShaping on the Iub interface: qosDt 0 0 1 0 2 350 3 500
Case of basicVPT trafficShaping on the Iub interface:
qosDt 0 0 1 0 2 300 3 500
Rule: IubTEG_Hybrid-RNC_CM_10
Case of No basicVPT trafficShaping on the Iub interface:
Case of basicVPT trafficShaping on the Iub interface:
3.7.11.4
qosBPt 0 0 1 0 2 95 3 95
qosBPt 0 0 1 0 2 33 3 35
COUNTERS:
Two kinds of real time counters are implemented which measure the trafficVolume per 10 ms period:
- The per qos real time counters: Q010ms, Q110ms, Q210ms and Q310ms,
- The per cumulative qos counters: Qxxx, in extenso: Q0, Q01, Q012 and Q0123.
The four per qos counters provide per qos the trafficVolume over a 10 ms period:
Qn10 ms Counters
Qos
Q010 ms
Qos0
Q110 ms
Qos1
Q210 ms
Qos2
Q310 ms
Qos3
Further the RNC estimates the per qos expected trafficVolume over the next 10 ms period, based on the
per qos measured trafficVolume over the previous 10 ms periods. For that the RNC set the Qne
(estimated) counters:
Qne Counter
definition
Q0e
Q1e
Q2e
Q3e
The four per cumulative qos counters Qxxx provide the trafficVolume over a 10 ms period for qos0,
qos0+qos1, qos0+qos1+qos2, qos0+qos1+qos2+qos3:
Qxxx Counters
definition
Q0
Q01
Q0+ Q1
Q012
Q01 + Q2
Q0123
Q012 + Q3
The counter unit is either cell/10ms for the atm interface or bytes/10ms for the ip interface.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 187/263
3.7.11.5
THRESHOLDS
The qosDiscard and qosBackPressure threshold values calculated by the RNC depend on the bandwidth
configured per qos against a bwPool, the configured qosDt and qosBP parameters and the setting of the
qosnBwReservation parameters.
The qosnBwReservation parameters are involved in the Transport admissionControl.
The qosnBwReservation parameters are also involved in the congestionManagement thresholds
determination if:
- the enhancedQos = enabled,
- cacm=qos, and
- qosnBwReservation > 0%.
Rule: IubTEG_Hybrid-RNC_CM_11
The qosnbwReservation is taken into consideration by the congestionManagement if:
- The RncIn enhancedQos = enable,
- The cacMethod = Qos under Aal2If or IpIf level
qosDiscardThresholds
dth0 = Th0 = bwPool vcc ECRgcac /100
= bwPool ipFlow ERgcac /100
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 188/263
Th0 = bwPool [qos0 vcc ECRgcac + qos1 vcc ECRgcac + qos2 vcc ECRgcac + qos3 vcc ECRgcac]
/100 for the atm interface,
Th0 = bwPool [qos0 ipFlow ERgcac + qos1 ipFlow ERgcac + qos2 ipFlow ERgcac + qos3 ipFlow
ERgcac] /100 for the ip interface,
The dthn thresholds are recalculated each 50 ms.
The Th0 threshold is updated when there is a change in transport status (bandwidth reduction,
restoration, addition).
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 189/263
Per period of 10 ms, an estimation of the per qos traffic using the Bwnavail portion is given by the
relation:
Traffic qos n shared
Trafficqosnshared = Qne bwnexclus
With:
- n = [0, 1, 2, 3],
- If TrafficQosnShared is negative, it is forced to Zero, then Trafficqosnshared 0.
The qos discard threshold definition is impacted by the qosnBwReservation through the
Trafficqosnshared and the bwnavail:
qosDiscardThresholds
dth0 = bw0avail
dth1 = bw1avail + (qosDt1/100 -1) * [ bw1avail trafficqos0shared ]
dth2 = bw2avail + (qosDt2/100 -1) * [ bw2avail ( trafficqos0shared + trafficqos1shared ) ]
dth3 = bw3avail + (qosDt3/100 -1) * [ bw3avail ( trafficqos0shared + trafficqos1shared + trafficqos2shared ) ]
The qosBP threshold formulas are not impacted by the qosnBwReservation nevertheless the qosBP
threshold values are impacted by the qosnBwReservation.
qosDiscardThresholds
bpThn = dthn * qosBPtn/100
3.7.12 ROUTING:
On the RNC, no IP routing protocol is activated, the IP routing tables are manually configured.
Rule: IubTEG_Hybrid-RNC_Routing_1
No Routing protocol is activated, Static routes are used.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 190/263
3.8
NODE B (IBTS)
The oneBTS is the ex Nortel nodeB.
3.8.1
CARDS
Two kinds of nodeB card: the CEM and the CCM impact the NodeB Transport part.
3.8.1.1 CEM:
The CEM card is the gateway between radio and Iub interface. The amount of CEM cards per nodeB,
determines the call processing capacity of the NodeB.
Different kinds of CEM:
The NodeB may be populated with four kinds of CEM card:
- alphaCEM,
- iCEM64,
- iCEM128,
- xCEM.
All kind of CEM supports Hsupa traffic with exception of the alphaCEM.
Rule: IubTEG_ NodeB-CEM_02
The alphaCEM doesnt support hsupa traffic.
BBU Component:
The different kinds of CEM are populated with different amounts BBU components (BaseBandUnit) in
charge of handling the UMTS traffic:
- The iCEM64 is composed of one BBU,
- The iCEM128 is composed of two BBU.
BBU Role:
Each BBU component within a CEM is loaded with a BBU role; the different BBU roles:
- D-BBU: The BBU dedicated to the release99 traffic (dedicatedServices).
- H-BBU: The BBU dedicated to the hsdpa traffic,
- E-BBU: The BBU dedicated to the hsupa traffic.
Rule: IubTEG_ NodeB-CEM_03
The NodeB supports up to four E-BBU roles.
Remark: It is forecasted for UA6 that the NodeB supports up to 6 CEM loaded with E-BBU role.
One BBU component loaded with E-BBU role is able to handle simultaneously up to 15 hsupa legs.
Rule: IubTEG_ NodeB-CEM_04
One E-BBU handles up to 15 Hsupa simultaneous sessions.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 191/263
Since UA5-0, an algorithm is in charge of assigning the different BBU roles to the CEM BBU
components. Therefore the kind of traffic handle by a CEM can not be predicted in configuration phase.
CCP Vcc:
Each CEM involved in release99 traffic or a mix of release99 and Hspa traffic is a point of termination of
one aal5 CCP Vcc. The CEM manages also the associated SSCOP connections.
The CEM involved only in hspa traffic dont require terminating one aal5 CCP Vcc.
Since the BBU role assignment to BBU component is devolved to an algorithm, no way to determine
which CEM requiring a ccp vcc and which CEM nor requiring ccp vcc.
As a consequence, it is recommended to configure as many ccp vcc as amount of CEM within the nodeB,
whatever the traffic handle by the CEM.
The ccp vcc configured on the CEM dedicated to hspa is set disable by the nodeB without alarm
generation.
Rule: IubTEG_ NodeB-CEM_01
One CCP Vcc is configured per CEM Card,
The CCP Vcc configured on the Iub interface is switched in the CCM to the CEM.
CEM Characteristics:
The iCEM64 is composed of one BBU component.
The iCEM64 handles one kind of traffic amongst three: Release99, hsdpa and hsupa traffics, according to
the BBU role loaded.
The iCEM64 capacity is up to 15 simultaneous hsupa legs.
The iCEM128 is composed of 2 BBU components.
- The iCEM128 handles either:
- Simultaneously two kinds of traffic amongst three: Release99, hsdpa and hsupa
traffics according to the two different BBU roles loaded, or
- One kind of UMTS traffic, if both BBU are loaded with the same BBU role:
Release99 or hsdpa.
- One iCEM128 can not be populated with two E-BBU s.
- The iCEM128 capacity is up to 15 simultaneous hsupa legs.
The xCEM supports up to 1 E-BBU, and up to 64 hsupa legs..
Rule: IubTEG_ NodeB-CEM_05
The iCEM128 may be loaded with only one E-BBU role.
Slot 1
Slot 2
D-BBU
iCEM64
H-BBU
NA
E-BBU
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 192/263
iCEM128
Slot 1
Slot 2
D-BBU
D-BBU
D-BBU
H-BBU
H-BBU
D-BBU
H-BBU
H-BBU
D-BBU
E-BBU
E-BBU
D-BBU
E-BBU
E-BBU
E-BBU
H-BBU
H-BBU
E-BBU
3.8.1.2 CCM:
For Card hardware aspects see [R100]
In NodeB, CCM is in charge of OAM management, part of call processing and internal/external data flow
switching/combining.
Inside CCM, The BRIC (BTS Router Interface Controller) provides the main processing and control for
the NodeB.
The BRIC operates internally at atm level (aal2 for UMTS traffic, aal5 for UMTS Signaling and OAM)
and supports atm aal2/aal5 backhaul to the RNC for UMTS operation.
The CCM terminates the aal5 CP Vcc and manages the associated SSCOP connections.
This CCM provides E1/T1 interfaces to the network. The CCM supports up to 8E1/T1 and one single
IMA linkGroup.
Different CCM card characteristics:
- The initial CCM does not support simultaneously IMA and xPcm.
- The CCM types: iCCM and iCCM2 supports simultaneously: IMA and xPcm.
Ethernet accesses are not supported when the nodeB is populated with the iCCM.
- The xCCM supports two IMA linkGroups and two FastEthernet accesses.
The xCCM provides a 100Mbps Ethernet port, anyway the ThroughPut is
limited to 30 Mbps in DL and 15Mbps in UL.
3.8.2
PDH LAYER:
The NodeB provides both atm and ethernet accesses.
A NodeB may be populated with up to eight E1/T1 links.
The NodeB supports the CRC4. Two modes of configuration:
- A fix configuration: the nodeB is configured with CRC4 activated or not activated, thanks to the
parameter ReceiveCRC = 0 or 1,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 193/263
3.8.3
An automatic configuration: the nodeB is configured in such a way that the CRC4 activation is
conditioned by the presence of the CRC4 in the received multiframe. For that the NodeB
E1pcmFrame parameter is set with the value: multiframeAuto, the ReceiveCRC parameter is
ignored.
ETHERNET LAYER:
The nodeB populated with xCCM supports up to 8 E1/T1 and two FastEthernet links.
The nodeB populated with xCCM supports 2 fast ethernet accesses on copper.
One FE link is used for UMTS traffic, the second is used either for siteLan or for localMaintenance.
Per definition: the FE throughput is 100 Mb/s
Ethernet frames:
The NodeB supports:
- 802.3 MAC Frame
The NodeB doesnt support:
- 802.3 Q-Tagged MAC Frame
- Ethernet version2 MAC Frame (the RNC sends only EthV2 frames)
Q-Tag: the nodeB does not support Vlan.
P-Tag: 802.1P is not supported. If received, it is ignored.
The auto-negociation is not supported.
3.8.4
SYNCHRONISATION
The nodeB is synchronized either from:
- A reference clock given by a stratum 1 clock source, or
- A connected Iub E1.
In the context of synchronization on Iub E1, and CP vcc configured over a single E1 (xPCM) then the E1
where is configured the CP vcc is considered per default as the E1 clock reference.
Else the E1 clock reference is fixed by the configuration.
In the context of IMA, the NodeB supports CTC clocking mode. ITC is not supported.
Rule: IubTEG_NodeB-IMA_Synchronisation 01
NodeB supports CTC clocking mode.
3.8.5
ATM CONNECTIONS:
AtmConnection identifier range:
Rule: IubTEG_ NodeB-atm_01
Vpi range: [ 0 to 7]:
- Up to 8 Vpi values can be configured simultaneously.
- The same vpi value may be configured simultaneously on the IMA group and
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 194/263
on multiPcm E1.
Vci range: [ 0 to 255].
3.8.6
MULTIPCM
The NodeB Iub interface is configured either with IMA linkGroup, xPcm or a mix of IMA and xPcm.
For the E1 not inserted within an IMA linkGroup, configured in xPcm mode, the vcc are distributed on
each E1 link.
The Oam vcc is configured on the pcm 1 per default (in factory).
The others vcc are distributed over the different pcm in such a way to satisfy robustness and load
balancing:
- the CP vcc is configured on a Pcm, different from those supporting oam vcc,
- the CCP vcc are distributed over the different available pcm,
- one up ds vcc and one up nds vcc are configured per pcm.
- If hspa configured over xPcm, then 1 hspa vcc is configured per pcm.
Exemple:
- 6 pcm,
- NodeB with 5 CEM,
- 1 Hspa vcc over one shared Pcm together with release99 vcc, the RNC BwPool must be
set in accordance.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 195/263
- 1 Hspa vcc over one dedicated Pcm in such a way to avoid congestion, the RNC
BwPool must be set in accordance.
The following table provides an exemple of the vcc distribution:
PCM 1
1 oam vcc
PCM 2
1 cp vcc
PCM 3
PCM 4
PCM5
1 ccp vcc
1 ccp vcc
1 ccp vcc
1 ccp vcc
1 ccp vcc
1 up ds vcc
1 up ds vcc
1 up ds vcc
1 up ds vcc
1 up ds vcc
1 up nds vcc
1 up nds vcc
1 up nds vcc
1 up nds vcc
1 up nds vcc
1 hspa vcc
3.8.7
PCM6
1 hspa vcc
IMA
The IMA linkGroup configured on the nodeB is either shared by the Release99 and Hspa traffic or
dedicated the Hspa traffic.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 196/263
Furthermore, within the RNC, the trafficDescriptor against the userPlane vcc
belonging to a set of userPlane vcc are set in such a way:
set of userPlane vcc ECRgcac = E1 bandwidth minus E1 bandwidth portion reserved for
the signaling.
The HP values are suggested in 5.5.1.
Case of IMA Group associated to a primaryForTrafficType bwPool composed of only qos3
vcc:
Rule: IubTEG_NodeB-IMA_4
As many HSPA qos3 vcc are configured as amount of E1 within the IMA group.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 197/263
Furthermore within the RNC, the rtVbr, nrtVbr or UBR+/MDCR is assigned to each
qos3 vcc, the trafficDescriptor assigned to each qos3 vcc are set in such a way qos3
vcc ECRgcac = E1 bandwidth minus E1 bandwidth portion reserved for the signaling.
Case of IMA Group associated to a primaryForTrafficType bwPool composed of qos0, qos1,
qos2 and qos3 vcc:
Up to four types of aal2 vcc (qos0, qos1, qos2 or qos3 vcc) are configured over the
IMA group. The amount of configured aal2 vcc per type depends on the amount of
E1:
- For each E1 within an IMA group, a set of userPlane vcc is configured. A set of
userPlane vcc is composed of one or several vcc with different qos.
- Within the nodeB all the vcc within a set of userPlane vcc are set with the same
holdingPriority value.
Furthermore, within the RNC, the trafficDescriptor against the userPlane vcc
belonging to a set of userPlane vcc are set in such a way:
set of userPlane vcc ECRgcac = E1 bandwidth minus E1 bandwidth portion reserved for
the signaling.
The HP values are suggested in 5.5.1.
NodeB IMA Defense Activation/desactivation:
The nodeB IMA Defence mechanism is activated as an option at the OMC-B thanks to the
parameter: IMAGroup/imaDefenseDelay present at the OMCB:
- IMAGroup/imaDefenseDelay = unset, means the defense mechanism is desactivated,
- IMAGroup/imaDefenseDelay = x, indicates the delay the nodeB introduced between the
link failure event and the invocation of the Defence mechanism. If x=0, the nodeB starts
the defense mechanism since aware about the bandwidthReduction.
Triggers:
The nodeB releases some vcc in the following context:
- PCM LOS condition observed locally,
- PCM manually locked,
- Aal2 Vcc creation,
- Reception of ICP cell with physicalDefect information (case of PCM LOS observed by
the farEnd node).
The nodeB restores some vcc in the following context:
- PCM recovery,
- PCM manually unlocked
- Aal2 Vcc deletion.
3.8.8
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 198/263
The fractional E1 feature is not compatible with the nodeB mix configuration.
The atm oam loopBack mechanism may be activated on the isolated E1 and is not available for E1
inserted in the IMA linkGroup.
Synchronisation:
- Either all the NodeB is synchronized on a reference clock given by a stratum one clock
source, or
- One Iub E1 is chosen as the clock reference. The E1 designated as the clock reference must be
the E1 transported within the backbone over the media the less impacting in terms of delay,
e.g.: preferred E1 over leased line instead of E1 over DSL.
IMA:
It is still recommended to activate the IMA Defense on the NodeB side.
Hspa vcc amount:
- If the IMA linkGroup is dedicated to the Hspa traffic, it is recommended to configure as many
hspa vcc as amount of E1 within the IMA linkGroup, in such a way to relay on the nodeB
IMA defense mechanism.
- If the IMA linkGroup is shared between Hspa and Release99 traffic, the amount of hspa vcc
results from the need of simultaneous aal2 CID. One or two hspa vcc may be required (NodeB
hspa cac constraint).
- Over an E1 in a xPcm mode, only one Hspa vcc is enough.
Application exemples:
- The Release99 userPlane vcc, the signaling vcc and the oam vcc are configured on the
independent E1, whereas the hspa vcc are configured on the IMA LG.
The distribution of the Release99 userPlane vcc and the signaling vcc over the E1 in xPcm mode is
done as for the xPcm configuration, see 3.8.6.
3.8.9
IP
IP version:
- IPv4 supported. IP v6 not supported.
IP routing:
- IP routing protocols are not supported; static routing applies.
IP@:
The NodeB is configured with two external IP@:
- 1 external IP@ for the userPlane with its associated subnetMask and one single associated
nextHop IP @,
- 1 external IP@ for the OAM.
The NodeB doesnt support DHCP then the NodeB IP@ must be manually configured (can not
automatically be set by a DHCP Server).
The NodeB-UserPlane-IP@ is exchanged, call by call, with the RNC during the NBAP Radio Link
setup procedure.
NodeB IP@ parameters:
The nodeB addressing parameters (if no DHCP):
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 199/263
- BTSipRanNodeBAddress,
- BTSipRanNodeBsubnetMask,
- IP@nextHopGateway.
3.8.10 QOS
3.8.10.1
IP QOS
Node B
NBAP RL setup/add/reconf request
- TLA IE: RNC IP @ in NSAP format
- Binding IE: RNC UDP port
- TNL QoS: DSCP
NBAP CTCH/RL setup/add response
- TLA IE: Node B IP @ in NSAP format
- Binding Id: contains Node B UDP port
TEG
The NodeB rejects the NBAP RL Setup with an unrecognized DSCP value.
3.8.10.2
ATM QOS
The QOS is configured in the nodeB through the NodeB proprietary serviceCategory parameter, which is
an extension of the AtmForum serviceCategory.
List of the NodeB proprietary serviceCategory parameter values:
- CBR, CBR1, CBR2, CBR3,
- VBRrt, VBRrt1, VBRrt2, VBRrt3
- VBRnrt0, VBRnrt, VBRnrt2, VBRnrt3,
- UBR0, UBR1, UBR, UBR3,
- UBRPlus0, UBRPlus1, UBRPlus, UBRPlus3.
The highest priority is given to the CBR vcc and the lowest priority is given to the UBR vcc.
For vcc configured with the same AtmForum serviceCategory, the highest priority is given to the xBR0
vcc and the lowest priority is given to the xBR3 vcc.
The UBR and UBRPlus NodeB proprietary serviceCategory parameter values (without a numerical
suffix) are considered priority 2.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 200/263
suggested SC
in the network
ProprietarySC parameter
configured in the NodeB
qos0 vcc
rtVbr
UBR1
qos2 vcc
nrtVBR
UBR
qos3 vcc
UBR
UBRPlus3 (MCR)
CP
rtVbr
UBR1
CCP
rtVbr
UBR1
alcap
rtVbr
UBR1
OAM
UBR
UBRPlus3 (MCR)
/2/
suggested SC
in the network
ProprietarySC parameter
configured in the NodeB
qos0 vcc
cbr
UBR0
qos1 vcc
rtVbr
UBR1
qos2 vcc
nrtVBR
UBR
qos3 vcc
UBR
UBRPlus3 (MCR)
CP
rtVbr
UBR1
CCP
rtVbr
UBR1
Alcap
rtVbr
UBR1
OAM
UBR
UBRPlus3 (MCR)
/2/
Remarks:
- The NodeB proprietary SC UBR means priority:2; the NodeB proprietary SC UBRPlus
means priority:2
- The qos3 vcc carries both hspa user traffic and hspa flowControl traffic. In such a way to
guarantee a minimum bandwidth for flowControl, a MCR value is assigned to Hsdpa Vcc.
NodeB QOS handling:
- The UBRx vcc and the UBRPlusx vcc get the same priority,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 201/263
Assuming two vcc configured with the same proprietary SC, if there are cells in both vcc
queues, the nodeB scheduler considers each queue with the same weight, indeed one cell is
extracted from first queue, then one cell from the second queue, then one cell is extracted
from first queue,
SC configured in NodeB
Proprietary SC
qos0 vcc
rtVBR
rtVbr
qos1 vcc
nrtVBR
nrtVbr
qos3 vcc
Ubr
Ubr3
CP
rtVBR
rtVbr
CCP
rtVBR
rtVbr
Alcap
rtVbr
rtVbr
OAM
UBR+
UBRPlus
3.8.11.1
MCR:
(see 4)
To avoid lowest priority vcc traffic starvation by highest priority vcc traffic, a MCR
(MinimumCellRate) value is configured on lowest priority vcc to guarantee a minimum bandwidth.
The MCR parameter is configured for UBR+ vcc.
The MCR is taken into account by CAC; UBR+ Vcc ECR = MCR.
MCR is not involved in TrafficShaping; whatever the MCR value, an UBR+ vcc may transmit at
linkRate.
Even if a lower priority vcc is configured with a MCR, a higher priority vcc is able to use the
complete link bandwidth, if available.
The MCR parameter may be configured against aal5 and aal2 vcc.
In the nodeB, the MCR value is configured against an UBR+ vcc through the vcc SCR parameter.
Indeed for a UBR+ vcc the SCR parameter is filled with the expected MCR value whereas for vcc
configured with another serviceCategory the SCR parameter is filled with the expected SCR value.
For an UBR+ vcc, the nodeB accepts only SCR filled with a nonzero value, rejects the SCR=0.
How to configure the MCR value through OMC-B, and impact on NodeB:
Rule: IubTEG_NodeB-TM_1
On OMC-B
Results on NodeB:
UBR, SCR=0
UBR, SCR=0, MCR=mcr with mcr <> 0
UBR
UBR+, MCR=scr
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 202/263
UBR+, MCR=scr
UBR+ , MCR=SCR=0
Error
3.8.11.2
TRAFFIC SHAPING
In first UMTS Releases, trafficShaping was always activated at VC level. It becomes optional in last
UMTS Releases (see 4).
Since trafficShaping becomes optional,
- Activation of trafficShaping in NodeB consists in setting serviceCategory and proprietary SC
values indicated in rule Iub_NodeB-QOS_1.
- Non activation of trafficShaping in nodeB consists in setting serviceCategory and proprietary
SC values indicated in rule Iub_NodeB-QOS_2.
Remarks:
To remove TrafficShaping on NodeB, serviceCategory are change to UBR/UBR+, nevertheless keeps
on other Iub Atm nodes Iub recommended serviceCategory values, as indicated in rule Iub_NodeBQOS_2 column SC recommended for the interface.
Moreover when removing trafficShaping in nodeB:
Rule: IubTEG_NodeB-TM_3
- For UBR VCC, set SCR=MBS=0 on nodeB,
- For UBR+ VCC, set SCR and MCR according to rule Iub_NodeB-TM_1.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 203/263
Remarks:
PCR is still used for regulating Egress traffic, then set PCR to the interface bandwidth.
Rule: IubTEG_NodeB-TM_4
A mix of shaped atmConnections and notShaped atmConnections is not allowed on nodeB.
3.8.13 ALCAP
The NodeB allows establishment of the aal2 connections either using the Nbap (UA5 behaviour) or the
Alcap protocol.
The choice of the protocol used for the aal2 connections establishment is determined by the setting of the
AlcapActivation parameter.
Rule: IubTEG_NodeB-Alcap_1
The nodeB AlcapActivation parameter must be set to true, for running Alcap protocol. Else the
aal2 callControl is achieved by NBAP.
It is mandatory to activate the Alcap protocol on the Iub interface.
Parameter: BtsEquipment / AlcapActivation (class0) values: True or false.
Since the alcap is activated on the Iub interface, one single alcap vcc must be configured per nodeB.
Alcap Cell Validity Timer:
The iBTS supports the Alcap Cell Validity Timer.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 204/263
The objective of this timer is to avoid aal2 traffic instability when SCCOP connection
bouncing.
3.9
NODEB (ONEBTS)
3.9.1
ALCAP
Alcap Cell Validity Timer:
The NodeB (oneBTS) doesnt support the Alcap Cell Validity Timer.
3.10
3.10.1 TRANSMISSION:
The NodeB atm supports the following kind of transmission links:
- Supports: E1, T1, J1,
- Up to 8 x E1/T1/J1
- Ethernet 10/100 baseT for local Maintenance tool.
Not supported:
- Fractional E1/T1/J1 links (drop&Insert),
Atm bandwidth:
Case of E1 on the Iub interface, the micro NodeB atm must be configured with the E1 reserved
bandwidth (timeslot 0 and 16) and then the E1 bandwidth available for the user.
The TimeslotUsage parameter value is a 32 bit length word, in which each bit is a
representation of the E1 frame timeslot. The bits associated to the reserved timeslots are set to
0, whereas the bits associated to the timeslots usable by user are set to 1.
According to the ITU recommendation related to atm over E1, the timeslot 0 and 16 are
reserved., therefore the parameter timeslotUsage is set as following:
Rule: IubTEG_NodeB atm- 01
Case of E1, set timeslotUsage = 7FFF 7FFF
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 205/263
CRC4:
The CRC is activated as an option through the parameter lineFraming = basicFraming /
multiFraming.
If CRC is activated in the Nodeb, take care it is also activated in the adjacent node.
Synchronization:
The synchronization is derived from one active PCM. Each PCM (0 to 7) within an IMA LG
may be selected by configuration as primary synchronization source.
When the PCM used as primary synchronization source is outOfService, the NodeB selects
another still active E1 as primary synchronization source.
If no PCM may be used as primary synchronization source, the NodeB local clock is used as
synchronization source for the radio interface.
3.10.2 ATM:
Atm characteristics supported:
- Scrambling according to ITU, activated as an option,
Command: linePayloadScrambling = According to Standard, means scrambling is
automatically activated if the received cell is scrambled.
AtmConnection and atmConnection Identifier supported:
- Pvc,
- Aal2, aal5,
- Up to 16 aal2 vcc
- Up to 2 Vpi values may be configured on the NodeB Iub interface.
- UNI Vpi range: [0-255], Vci range: [32-65535].
IMA characteristics supported:
- IMA version 1.1, does not support IMA1.0,
- Up to one IMA LG,
- From 1 to 8 E1/T1/J1 within an IMA LG,
- IMA Identifier range: [0-255],
- IMA Defense mechanism is identical to the NodeB IMA Defense.
Atm OAM characteristics:
- Activation/deactivation of F4 and F5 atm oam flows through the parameter: f4f5flow, per
default these flows are not activated.
Rule: IubTEG_NodeB atm- 02
Activate the F5 oam flows, to satisfy the RNC aal2CongestionManagement.
F4f5flow = F5 inUse.
-
Performance management:
- Collecting measurements from the different blocks within the BTS,
- Handling of PM jobs,
- Reporting of results.
Test functions:
- Monitoring status of physical link, IMA, F4/F5 etc,
- Ordering test model transmission,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 206/263
loopBack supported.
Qos:
-
UP DS
rtVbr
UP NDS
nrtVBR
CP
rtVbr
CCP
rtVbr
HSDPA
UBR+
OAM
UBR+
TrafficManagement:
The NodeB performs No policing and performs trafficShaping at Vc level.
List of the trafficManagement parameters:
- PCR:
- PCR unit is cells/s,
- The PCR is mandatory for all vcc whatever the SC,
- PCR range = [ 1, 35 000 c/s],
- The PCR value can not exceed the linkRate,
- The maximum PCR value 4528 c/s if the vcc is configured on an E1,
- The maximum PCR value X * 4490 c/s if the vcc is configured on an IMA LG
composed of X E1,
- The maximum PCR value 3622 c/s if the vcc is configured on a T1.
- SCR:
- SCR unit is cells/s,
- SCR range = [ 1, 35 000 c/s],
- The SCR must be set for the vcc serviceCategory = rtVbr and nrtVbr, unused for other SC.
- 1 SCR PCR.
- MBS:
- The MBS must be set for the vcc serviceCategory = rtVbr and nrtVbr,
- MBS 2,
- MCR:
- The MCR must be set for the vcc serviceCategory = UBR+, unused for other SC.
- MCR range = [ 1, 35 000 c/s],
- 1 MCR PCR,
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 207/263
per link, CBR Vcc PCR + VBR Vcc PCR + UBR+ Vcc PCR linkRate,
per link, CBR Vcc PCR + VBR Vcc SCR + UBR+ Vcc MCR linkRate,
CBR Vcc PCR + VBR Vcc PCR + UBR+ Vcc PCR linkRate x * linkRate,
If atm oam F4/F5 flow is activated, the linkRate taken into consideration by the CAC
is reduced by the bandwidth reserved for the F4/F5 atm oam vcc.
If IMA is configured, the linkRate taken into consideration by the CAC is reduced by
the IMA overhead. Eg: E1 bandwidth when inserted in IMA = 4490 c/s.
3.10.3 AAL2
Aal2 PathId:
The pathid is coded over 4 bytes, pathid range: [1, 7F FF FF FF]
Rule: IubTEG_ Iub_NodeB atm - 04
The RNC PathId being coded on 2 bytes whereas the NodeB atm pathid is coded on 4 bytes,
the Pathid value must be dictated by the RNC.
Aal2 CPS:
The aal2 CPS Packet payload length is configurable, choice of 45 or 64 bytes length:
Parameter
Meaning
Value
CPS-INFO
45 or 64 bytes
3.10.4 SAAL:
List of the NodeB Saal parameters:
Parameter
Default value
Range
[1 10]
MaxCC
MaxPD
25
Timer_POLL
750 milliseconds
Timer_KEEP-ALIVE
2000 milliseconds
Timer_NO-RESPONSE
7000 milliseconds
Timer_IDLE
15000 milliseconds
Timer_CC
1000 milliseconds
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 208/263
The Timer_NO-RESPONSE should be set to at least the sum of Timer_KEEP-ALIVE and the
roundTripDelay:
Timer_NO-RESPONSE > Timer_KEEP-ALIVE + roundTripDelay.
The Timer_IDLE should be set to a considerably larger value than the Timer_KEEP-ALIVE:
Timer_IDLE >> Timer_KEEP-ALIVE
3.10.5 IP:
The NodeB support IPv4.
- DHCP:
The parameter dhcpInUse is set with a Boolean value to indicate if a DHCP server assigns an IP@
to the NodeB.
- inverseARP:
The inverseARP is supported.
- IP Addresses:
Up to two IP Addresses are configured in the NodeB:
- One IP Address identifying the NodeB UMTS OAM Host point of termination of the Iub
OAM IP over atm vcc. This Ip Address is called: ipoaIpAddress.
- One IP Address identifying the NodeB Host point of termination of the
LocalManagementTerminal Ethernet interface. This Ip Address is called: ethPortIpAddress.
Parameters:
ethPortIpAddress:
Range: [0.0.0.0 255. 255. 255. 255];
Default value: 192.168.0.2.
ethPortIPSubnetMask:
Range: [255. 255. 255. 255- 0.0.0.0];
Default value: 255.255.255.0.
IpoaIpAddress:
Range: [0.0.0.0 255. 255. 255. 255];
IpoaIPSubnetMask:
Range: [255. 255. 255. 255- 0.0.0.0];
IpDefaultGateway: equivalent to the nextHop.
Range: [255. 255. 255. 255- 0.0.0.0];
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 209/263
Oam Vcc:
The Oam Vcc is per default configured with UBR+ and PCR = 150 c/s.
UP Vcc:
On the NodeB are configured as many couple of (UP DS, UP NDS) Vcc as amount of E1 in the
IMA LG.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 210/263
3.11
3.11.1 TRANSMISSION:
Fractional E1.
3.11.2 ATM:
The pico NodeB atm is compliant with R35.
AtmInterface Type:
- Supports UNI interface type.
- Doesnt support GFC (GenericFlowCtrl). The GFC field is filled with 0000.
AtmConnection Type:
- Only PVC is supported.
AtmConnection Identifiers:
- Supports one Vpi per transmission link.
- Up to 2 vpi values on one picoNodeB.
- Two vpi values are supported in case of IMA.
AtmConnection Amount:
- Up to 16 aal2 vcc (TRB, dSRB and cSRB).
- 1 or 2 aal5 vcc:
- If 1 aal5 Vcc is configured, it carries both nbap-c and nbap-d,
- If two aal5 Vcc are configured, one carries the nbap-c traffic (CP vcc), the second carries the
nbap-d traffic (CCP vcc),
- 1 aal5 vcc for UMTS OAM.
IMA:
-
OAM:
- The endToEnd F4 and F5 flows supported according to R[36].
- The endToEnd VP and VC LoopBack supported.
Upon reception of AIS, the picoNodeB returned upstream a RAI (= RDI) according to R[34].
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 211/263
Atm Qos:
- ServiceCategory:
- Cbr, rt and nrtVBR, Ubr and Ubr+ are supported,
- Each SC can be assigned to each kind of vcc,
- CAC:
No CAC implemented in the PicoNodeB,
-
OverBooking:
Not Applicable since any CAC.
TrafficManagement:
- TrafficDescriptor:
The set of trafficDescriptor parameters to configure depends on the atmConnection
serviceCategory:
- Cbr vcc: PCR,
- Vbr vcc: PCR, MBS and SCR,
- UBR vcc: PCR,
- UBR+ vcc: PCR and MCR (Minimum Celle rate)
The PCR is a mandatory parameter for all the serviceCategories.
The PCR range is [0; IMA LG bw].
- TrafficShaping/Policing:
The trafficShaping at Vc level is always activated.
ShapingRate = PCR: whatever the Vcc serviceCategory, the configured PCR, and only this
parameter, is considered as the shapingRate (=GCRA(PCR) from the atmForum121).
The SCR, MBS are not taken into consideration by the trafficShaping.
The Policing is not supported.
3.11.3 AAL2:
Aal2 Qos: Yes
Aal2 Signaling:
- Supports ALCAP according to R[46].
When interworking with ALU RNC, no Alcap protocol is running on the Iub interface, the Alcap
function is provided by an enhanced Nbap-c. See R[310].
Pathid range: the pathid is coded over 4 bytes:
Rule: IubTEG_ Iub_picoNodeB atm 01
The RNC PathId range being smaller that the picoNodeB range, the configured pathids must
satisfied the RNC range.
A2EA: the NodeB must be configured with its own A2EA if Alcap is run on the Iub interface. This is not
the case when interworking with the ALU RNC.
3.11.4 IP:
-
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 212/263
3.12
7670
The 7670 RSP provides a high capacity atm switching for large size atm backbone and all the sdh
hierarchy access rates from stm1/oc3 to stm16/oc48 either clearChannel or channelized nevertheless no
support for pdh link. The 7670 RSP has been specified to fulfil the backbone core services.
The 7670 ESE has been specified to fulfil the backbone edge services, the 7670 supports both pdh and
sdh access up to stm4/oc12, IMA E1/T1.
7670 RSP (Release 6-2)
7670 ESE
Product architecture:
Roles:
Synchronisation:
BITS E1/T1
Stratum3
internal (freerun)
Transmission:
interface card:
pdh
ethernet
APS:
4p 10/100 Mb/s
up to oc48/Stm16
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 213/263
7670 ESE
Atm:
vpi.vci range:
atmConnection:
type:
capacity:
Pvc/svc/spvc, pvp/svp/sPvp
up to 768 000 vc / node
up to 32 000 vp / node
8 serviceCategories: cbr, 2 rtVbr, 3 nrtVbr, abr, ubr/ubr+ (mdcr)
PerVc queues
WFQ
vpa (aka: vp endpoint), trafficShaping at vpa level
qos:
trafficManagement:
Signaling:
Pnni
IMA:
OAM:
F4/F5
Aal2:
encoding:
Ethernet:
Vlan:
P-Tagging
Eth over atm:
LAG:
G711
G726 and G726A/B compression & silence encodin
according to IEEE802.1Q
according to IEEE802.1P
according to rfc2684
no
IP:
version:
ThroughPut:
MTU
PPP:
VPN:
Qos:
Classification:
Marking/Remarking:
Policing/shaping
Routing:
ICMP:
ECMP:
DHCP:
MPLS:
3.13
supported
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 214/263
The Hsdpa traffic is carried over a downlink RNL channel called: HS-DSCH.
The eDCH uplink channel is always associated to a HS-DSCH downlink channel, not to a DCH, whereas
a HS-DSCH is associated to either a DCH or E-DCH.
The introduction of hsupa feature consists in NodeB and RNC software upgrade.
On the Iub interface, the UMTS hsupa traffic uses the services from the atm/aal2.
The PS Streaming, Interactive and Background trafficClass may use Hsupa services. The Conversational
trafficClass traffic remains assigned to DCH.
Any PS RAB request with Streaming, Interactive or Background trafficClass is matched to the E-DCH
Radio Bearer if the mobile is E-DCH capable and the primary cell of the active set supports E-DCH. If it
is not the case, the request is mapped on DCH as usual.
Rule: IubTEG_Hsupa_
When adding the HSPA Streaming on the Iub, The rncIn enhancedQos parameter must be set to
enable.
The dedicatedSRB associated to hsupa session is carried over the UP DS Vcc.
3.13.1.1
AAL2:
Each hsupa leg is carried over one aal2 dedicated connection identified by one CID. One different aal2
connection is seized for the associated hsdpa leg. As a consequence 2 CID are seized for one hsupa/hsdpa
user session.
One more aal2 Cid is seized on the aal2Qos0 path for the hspa dedicated SRB.
The CID from one aal2 path may be seized either by hsupa leg and hsdpa leg. The aal2 paths configured
for the hsupa and hsdpa are called Hspa Paths.
The streaming hspa paths are assigned to qos1 vcc within a sharedForAllTrafficTypes bwPool.
The Interactive/background hspa paths are either assigned to qos3 vcc within a sharedForAllTrafficTypes
bwPool or either to qos3, qos2, qos1 or qos0 vcc within a primaryForTrafficType bwPool.
CID
Path /qos0 vcc
CID
CID
CID
CID
RNC
NodeB
CID
CID
CID
CID
Path /qos3 vcc
dSRB
AMR TRB
CID
CID
CID
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 215/263
3.13.1.2
ATM:
3.13.2.1
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 216/263
The hspa traffic is handle on the Iub interface whatever IMA or multiPcm on the nodeB side.
CID
Path /qos0 vcc
CID
CID
CID
CID
RNC
NodeB
CID
CID
CID
CID
Path /qos3 vcc
dSRB
AMR TRB
CID
CID
CID
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 217/263
shareForAllTrafficType bwPool.
Whereas if the Hspa traffic is transmitted over a primaryForTrafficType bwPool and IMA, different HP
values are set against the different qosx vcc (see5).
3.13.2.2
3.13.2.3
TRAFFIC REGULATION:
Not Reviewed:
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 218/263
The Umts OAM traffic exchanged between the NodeB and the RNC is encapsulated in TCP/IP packets.
The IP packets are carried within the Umts OAM vcc.
Rule: IubTEG_OAM_01
On the Iub interface, the UMTS OAM traffic must be transmitted over the atm interface. It is not
supported over the ip interface.
3.13.3.1
ATM:
InBand OAM:
On the RNC Iub interface are configured as many Iub oam vcc as amount of connected nodeB.
Moreover may be configured as an option additional oam vcc related to backbone atmSwitches.
The OAM InBand solution consists within the RNC, in aggregating:
- the different nodeB umts OAM flows,
- the RNC own OAM flow and
- as an option the backbone atmSwitch OAM flow(s)
into one OAM vcc, configured on one atm transmission link also used by the UMTS traffic vcc.
The OAM vcc carried aggregated oam traffic destinated to the OMC. It may be switched within an
atmBackbone and as an option within umts coreNetwork nodes.
The aggregation operation is done by the RNC VR 0.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 219/263
RNC
RNC
IP@: 10.9.1.1
NodeB 11
NodeB
Subnet@: 10.9.1.0
PMC-OMU
PMC-OMU
SubnetMask: /24
CP
CP
CP
CP
PMC-OMU
PMC-OMU
Vcc 1.32
Ethernet
IP@: 10.9.0.3
LM
LM
E1
Subnet@: 10.9.0.1
PP3
IP@: 10.9.1.2
SubnetMask: /24
Vcc 1.32
E1
PP6
Subnet@: 10.9.1.0
SubnetMask: /30
MPE/1000
MPE/1001
AC3
AC3
E1
atmIf /801
STM1
MPE/1002
AC1
AC1
OAM vcc
AC1
AC1
NodeB 150
150
NodeB
Iub
Vcc 1.32
PP1
SubnetMask: /24
IP@: 10.9.1.150
SubnetMask: /24
IP@: 10.9.0.10
PP7
Subnet@: 10.9.0.8
AC1
AC1 AC2
AC2
Subnet@: 10.9.1.0
SubnetMask: /29
VR
VR 00
IP@: 10.9.1.254
ATM Switch
NodeB 22
NodeB
Subnet@: 10.9.1.0
PP2
Iu
OAM vcc
CP & UP vcc
atmIf /815
STM1
TEG
Figure 3-90 inBand OAM
Remark: The IP addresses are given as an example.
OutBand OAM:
Within the RNC, the aggregated OAM flows destinated to the OMC, are transmitted over the
ethernet links present on the RNC CP card.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 220/263
RNC
RNC
IP@: 10.9.1.1
Vcc 1.32
LM
LM
E1
PP3
IP@: 10.9.1.2
SubnetMask: /24
Vcc 1.32
E1
PP6
Subnet@: 10.9.1.0
PP7
SubnetMask: /24
MPE/1000
AC1
AC1 AC2
AC2
MPE/1001
AC1
AC1
AC3
AC3
SubnetMask: /24
NodeB 150
150
NodeB
Iub
Subnet@: 10.9.1.0
IP@: 10.9.1.150
Vcc 1.32
PP2
VR
VR 00
IP@: 10.9.1.254
ATM Switch
NodeB 22
NodeB
Subnet@: 10.9.1.0
OMC
OMC
CP
CP
CP
CP
PMC-OMU
PMC-OMU
BackBone
BackBone
PMC-OMU
PMC-OMU
SubnetMask: /24
Hub
Hub
NodeB 11
NodeB
Subnet@: 10.9.1.0
atmIf /801
STM1
TEG
Figure 3-91 outBand OAM
Remark: The IP addresses are given as an example.
TrafficManagement: the OAM vcc carrying the aggregated OAM flows should be configured with UBR
ServiceCategory.
3.13.3.2
IP:
The Iub oam vcc and the aggregated oam vcc carry IP based OAM traffic between the NodeB and RNC
and between the RNC and the OMC. The oam IP packets are routed within the RNC to the OMC.
3.13.3.2.1 MPE
The RNC may be connected to up to 2400 nodeB.
The RNC atmMpe supports up to 255 atmConnections.
Therefore to address the maximum amount of nodeB, are required:
- up to 10 atmMPE,
- 10 PP under the Iub OAM VR0 with /24 subnet size.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 221/263
OMU0
OMU0
OAM
OAM plateform
plateform
OMU1
OMU1
eth
eth
IP
IP
oam
LM
LM
If/2
CP
CP
127.255.0.0 /24
movable
PP
PP
VR0
Iub oam
PP
Iub oam
PP
Iub oam
PP
MPE 10
MPE 11
MPE 19
16pOC3
16pOC3
TEG
Figure 3-92 RNC OAM
Note: The atmMpe instance number are given in the Figure as an example.
Rule: IubTEG_OAM_03
10 atmMpe components must be configured for the Iub OAM traffic when up to 2400 nodeB
connected to the RNC.
3.13.3.2.2 ADDRESSING:
See [R80]
One dedicated to oam IP@ is assigned to the NodeB either on a static or dynamic way by means of
DHCP. This IP@ may be either a Private or a Public IP@. It is involved in the dialogue between the
NodeB and the remote OMC or a remote TIL.
Moreover, one local IP address is configured on NodeB Ethernet port, involved in local communication
between TIL and NodeB.
If public IP backbone is crossed, the NodeB-OMC IP session is managed through a VPN access.
If Static allocation applies, one oam IP@ is configured against each nodeB. On the RNC side either the
mapping between NodeB IP@ and NodeB oam vcc is configured or since the inverseARP is enable the
ARP table is automatically updated.
The Dynamic allocation implies that the DHCP is supported by the network.
The DHCP is composed of three functions:
- DHCP Client: located in the nodeB,
- DHCP Relay Agent: the DHCP routing function inserted in an UMTS node, and
- DHCP Server: located in the OMC.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 222/263
DHCP
Port 67
Port 68
UDP
Proto = 17
IP
IP
DHCP
DHCP
Server
Server
AAL5
ATM
DHCP
DHCP
OAM
OAM Server
Server
backbone
backbone
NodeB
DHCP Client
RNC
Iub
OAM Vcc
DHCP
RelayAgent
DHCP
DHCP
Server
Server
X
Iu
DHCP Servers
Atm
Ethernet
TEG
One or several DHCP Servers may be included in the network. They may be located on the OMC.
Rule: IubTEG_OAM_03
The RNC DHCP Relay Agent can forward messages to up to 3 DHCP Servers.
The DHCP which answers first to the nodeB request is selected.
The DHCP Relay Agent must be located in the UMTS node which handles the Aggregation of the nodeB
oam vcc. Indeed the inverseARP has to be executed in the node which manages 1 OAM vcc per nodeB.
Rule: IubTEG_OAM_04
The DHCP Relay Agent must be located in the RNC, since each nodeB oam vcc terminate in the
RNC.
The DHCP is invoked at the nodeB start up phase.
The DHCP dialogue between the NodeB and DHCP server in three phases:
- Broadcast IP dialogue from the NodeB to each DHCP server. One DHCP servers provide
the nodeB with an IP@. The selected DHCP is the first which answers to the nodeB
request.
- Broadcast IP dialogue from the NodeB to each DHCP; the NodeB indicates to all the
DHCP Servers the selected DHCP server. The selected DHCP returns the configuration
parameters.
- The inverse ARP protocol is invoked for configuration parameter check, it results with an
update of the RNC ARP tables (NodeB oam vcc, nodeB IP@).
- Unicast IP dialogue between the NodeB and the selected DHCP server.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 223/263
Since the IP@ ia allocated to the nodeB, the nodeB is ready to receive OAM traffic on the iub oam vcc.
When nodeB reparenting, a new IP@ is allocated to nodeB, if DHCP Servers connected to Source RNC
and target RNC are different.
As long as up to 200 nodeB per RNC, the class C IP@ are enough to identify a nodeB in the RNS.
Rule: IubTEG_OAM_05
NodeB IP@ is a Class C IP address.
Subnet mask: 255.255.255.0
As long as one class C subnet is defined, then up to 255 IP@ are allowed. Among the 255 IP
addresses, 2 are reserved:
- All host bits set to 0 for Subnet IP address,
- All host bits set to 1 for broadcast address.
Therefore 253 IP@ are available to identify the nodeB. It is suggested to assign 200 IP@ from
the class C subnet to the nodeB and keep 53 IP@ available for the case of reparenting.
Rule: IubTEG_OAM_06
Its not mandatory for OMC-B to be in the same subnet as nodeB.
NodeB IP address shall be a private IP address .
DHCP Configuration:
Rule: IubTEG_OAM_07
Range 192.168.0.0 to 192.168.255.0 is reserved for nodeB internal subnet and then shall not
be used by DHCP.
DHCP Relay Agent Configuration:
The DHCP Relay Agent is a routing function implemented in the RNC. The functionality consists in
routing IP packets which contains DHCP information to DHCP Servers.
Rule: IubTEG_OAM_08
The RNC DHCP Relay Agent is provisioned with:
- Its own DHCP Relay Agent IP@, and
- The IP@ of each connected DHCP Server
Remark: the DHCP Relay Agent IP@ and NodeB IP@ may be in different subnet.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 224/263
OAM
OAM Plateform
Plateform
DHCP Clients
Clients
DHCP
DHCP
DHCP
Server
Server
DHCP
DHCP
Server
Server
IP@
IP@
DHCP
DHCP
Server
Server
IP@
Ethernet
Option
Iub
POC
POC
RNC
RNC
PP
atm
atm
AC
Ethernet
OAM vcc
AtmMPE
AC
AtmIf
AC
AtmIf
AC
PP
AtmIf
NodeB 3
E1
AC
PP
AtmMPE
AtmIf
VR
PP
AtmMPE
VCC 0 / 32
atmSwitch
atmSwitch
++ IP
IP Router
Router
VR 0
AtmIf
AtmIf
IP flow
AtmIf
VCC 0 / 32
CP
CP
PP
AtmIf
NodeB 2
IP flow
AtmIf
NodeB 1
VCC 0 / 32
Iu
DHCP
RelayAgent
IP flow
Ethernet
Stm1
Stm1
TEG
Figure 3-94 DHCP Dialogue synoptique
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 225/263
3.13.5.1
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 226/263
Remark: the NAS Signaling carried over the dedicatedSRB is initiated by the UE, goes through
nodeB transparently up to the RNC within Iub qos0 vcc. Within the RNC, the PMC-TMU is in
charge of handling this traffic.
3.13.5.2
IP BASED USERPLANE
Only the UMTS hspa I/B userPlane is allowed to use the services from ip.
The transport bearer is identified by the UDP port numbers and the IP addresses (source UDP port
number, destination UDP port number, source IP address, destination IP address).
The bearer identifiers (UDP port numbers and IP addresses) are exchanged over ATM between RNC and
Node B at each Radio Link Setup via NBAP signaling messages.
3.13.6.1
TRAFFICMANAGEMENT
The third party ATM backbone may provide policed accesses which are characterized by pcr, cdvt, scr
and mbs.
Then to avoid cell discard by the atm backbone, the UMTS Nodes should shape the atmConnection to the
atm backbone, in such a way the traffic received in the ATM Backbone is conformed to the expected
traffic (SLA).
The service offers by the atm backbone is either vc or vp Switching.
An atm backbone providing vp switching services is preferred to an atm backbone providing vc switching
services. Indeed when activating Atm trafficRegulation mechanisms, the shaping rate must be determined
based on expected / forecast traffic.
Each vcc traffic source is considered to be erratic; the vp traffic, resulting from different vcc sources, is
expected to be more constant (multiplexing Gain). More vcc are included in the vpc, more constant is
expected to be the vp traffic.
Applying atm traffic Regulation at vp level, is then more economical (Improvement of bandwidth usage),
the shaping rate is determined more easily (expected traffic more constant), moreover the vp atm traffic
regulation has less impact (cell delay and discard) on the traffic than the vc atm traffic regulation.
If the atm backbone provides VP switching services, and policed accesses:
Rule: IubTEG_BB_01
When crossing a policed ATM backbone which provides vp switching services, the vpc are initiated in
the RNC (VPT feature) and trafficShaping is activated at vp level.
The Iub OAM vcc must not be inserted in the vp formation, to avoid QOS disturbance by the OAM
flow.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 227/263
3.13.6.2
OAM FLOW
The OAM vcc is configured with the lowest priority, UBR ServiceCategory.
To avoid traffic starvation, a minimum cell rate is reserved for OAM Vcc within UMTS passport based
Nodes by means of MBG. On NodeB, the parameter MCR is assigned to lowest priority Vcc for
guarantying them a minimum bandwidth (see nodeB/MCR availability in 4) .
In such a way to avoid traffic starvation within the ATM backbone, it is recommended to configure OAM
vcc within the ATM backbone with a minimum bandwidth.
Rule: IubTEG_BB_02
The OAM vcc must be configured with a MCR (MinimumCellRate) within the ATM
backbone.
4 UMTS RELEASES
4.1
RNC
4.1.1
FP
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 228/263
OUTPUT:
N/U
Iub
Icn
Hairpin
removed sPvc
Iub
Hairpin
PVC
Iub
Hairpin
sPvc
APC 3
Iu/Iur
Iu/Iur
Iu/Iur
Hairpin Hairpin N/U or
Hairpin
sPvc or PVC or
Iu/Iur
PVC Iub
Iub
Iu/Iur Shaped
Shaped
Shaped Shaped
VPC
VPT
VPC
VPT
APC 2
Iub
PNNI
Iu/Iur
Iub PNNI Iub PNNI Hairpin
sPvc
APC 1
APC 0
Iub
Hairpin
PVC
N/U
Iu/IuR
PNNI
SDH14
SDH0
SDH1
SDH2
SDH3
SDH4
SDH5
SDH6
SDH7
SDH8
SDH9
SDH10
SDH11
SDH12
SDH13
12
12
12
12
AtmIf CA maxVccs
2402
2402
2402
536
4802
536
536
64
2175
2175
2175
2175
536
AtmIf CA maxVpcs
200
22
AtmIf CA maxVpts
200
22
4095
4095
4095
255
255
255
255
255
255
255
255
255
255
255
4095
4095
AtmIf maxVpiBits
AtmIf CA minAutoSelectedVpi
AtmIf CA maxAutoSelectedVpi
4095
4095
4095
255
255
255
255
255
255
255
255
255
255
255
AtmIf CA minAutoSelectedVciForVpiZero
13981
13981
13981
1023
1023
1023
1023
1023
4095
8191
8191
8191
8191
1023
487
AtmIf CA maxAutoSelectedVciForVpiZero
16383
16383
16383
1023
1023
1023
1023
1023
4095
8191
8191
8191
8191
1023
1023
511
AtmIf Ca minAutoSelectedVciForNonZeroVpi
63
63
63
63
63
63
511
63
63
63
63
63
63
63
AtmIf Ca maxAutoSelectedVciForNonZeroVpi
63
63
63
63
63
63
511
63
63
63
63
63
63
63
511
16384
16384
16384
1024
1024
1024
1024
1024
4096
8192
8192
8192
8192
1024
1024
200
22
22
64
64
64
64
64
64
512
64
64
64
64
64
64
64
512
16384
16384
16384
1024
13824
1024
12288
1024
4096
8192
8192
8192
8192
1024
12288
2403
2403
2403
537
5203
737
581
87
2176
2176
2176
2176
537
Checks:
Arc
Lp Eng Arc Ov ConnectionPoolCapacity
1000
28440
>
24900
8000
>
7746
7000
>
6608
6600
>
6529
3300
>
3251
Apc/0
Lp Eng Arc Apc Ov connectionPoolCapacity
Apc/1
Lp Eng Arc Apc Ov connectionPoolCapacity
Apc/2
Lp Eng Arc Apc Ov connectionPoolCapacity
Apc/3
Lp Eng Arc Apc Ov connectionPoolCapacity
UA5-0:
- SS MSA32 is available.
Since UMTS UA4-1 / PCR5-2:
- SparingPanel available,
The MSA32 supports up to 28 E1 or 30 DS1 IMA ports per FP, distributed across the two
Makers (block of ports #0-15 or 16-31) as up to:
- 14 E1 ports in up to 7 IMA groups per Maker, or
- 13 E1 ports in up to 13 IMA groups per Maker.
- 15 DS1 ports in up to 7 IMA groups per Maker, or
- 13 DS1 ports in up to 13 IMA groups per Maker.
Before UA 4-1:
The MSA32 supported up to 22 E1 or 24 DS1 IMA ports per FP, distributed across the
two Makers (block of ports #0-15 or 16-31) as up to:
- 11 E1 ports in up to 5 IMA groups per Maker, or
- 10 E1 ports in up to 10 IMA groups per Maker.
- 12 DS1 ports in up to 6 IMA groups per Maker, or
- 10 DS1 ports in up to 10 IMA groups per Maker.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 229/263
2pStm1 Electrical Channelized FP is available on RNC-AN for the Passport release PCR52.
UMTS UA 4-0 & 3:
Not available.
UMTS UA4-1:
UMTS UA4-1:
4.1.2
RNC TYPES:
UMTS UA4-1:
RNC 1500 is available.
4.1.3
RNC CAPACITY:
-
4.1.4
UMTS UA 4-2:
Up to 400 nodeBs per RNC, TBC
UMTS UA 4-1 and previous:
Up to 200 nodeBs per RNC,
UA4 -2:
The Iuxif component is removed and replaced by two components: IubIf and aal2If.
4.1.5
PATHID:
-
UA 6:
The RNC supports up to 9720 aal2 Paths.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 230/263
UA 5-0 & 4:
The RNC supports up to 2100 aal2 Paths.
4.1.6
4.1.7
Release 4-2:
All Paths from one NodeB are assigned to one single PMC-PC. This modification is linked
the Hsdpa introduction.
The loadBalancing parameter is removed. This parameter was set to weighted on the Iub
interface and determined the way the Iub paths were assigned to the PMC-PC.
UA 5-0:
Enhancement of the AAL2 link CAC in such a way the bandwidth taken into consideration
(ACR) is either
1/ the NodeB per Path bandwidth,
2/ the NodeB per aal2Qos bandwidth:
3/ the total NodeB aal2 bandwidth, per Iubif (Sum of Vcc ECRgcac).
UA4 -1:
Enhancement of the AAL2 link CAC in such a way the bandwidth taken into consideration
(ACR) is either
1/ The NodeB per aal2Qos bandwidth,
2/ The IuxIf bandwidth.
UA4 -0:
The RNC aal2Link CAC consider the per aal2 interface bandwidth when regulating.
The total NodeB aal2 bandwidth = per Iuxif (Sum of Vcc ECRgcac).
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 231/263
Bandwidth reserved by the aal2 Link CAC for an already established call, is updated when
bandwidth update occurred due to always on UMTS feature (see FRS 25647).
The reconfiguration of a user toward another RB occurs when the following mechanisms are
invoked:
- Always On downsizing
- Always On upsizing
- iRM Scheduling downgrading
- iRM Scheduling upgrading
- Downgrading because of iRM pre-emption
4.1.8
AAL2CONGESTIONMANAGEMENT
UA5-1
-
UA 4-2, 5-0:
-
4.1.9
ICN VCC
UA4-1
4.1.10 TMU
-
UA 4 & 3:
One TMU manages up to 160 CP/CCP vcc.
Remark: TMU Redundancy is N+1, if less than 9 TMU, else TMU redundancy is N+2.
RNC available configuration:
# TMU
11
12
14
# nodeB
80
120
140
140
200
200
200
480
800
960
980
1400
1400
1400
Note:
#TMU in the table indicates the sum of active and Spare TMU.
This corresponds to the maximum NodeB configuration equipped with 6 CEM, which
requires 1 CP + 6 CCP vcc per NodeB.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 232/263
4.1.11 QOS
-
UA6
The qos mapping table is achieved through thr TransportMap
UA5-1:
The RNC is configured with one Qos information mapping table, which applies to all the Iub and
Iur interface:
TrafficClass
Aal2Qos
RNC serviceCategory
Conversational
0
rtVbr
Streaming
0
rtVbr
Interactive
1
nrtVbr
Background
1
nrtVbr
Hspa
2
- ubr, if hspa path within a shared bandwidthPool,
- nrtVbr, if hspa path within a hspa dedicated bandwidthPool.
4.2
NODEB
4.2.1
CCM RELATED:
UA5-1:
- The NodeB supports the the CCM type: xCCM, iCCM2 and iCCM.
- When populated with xCCM, the nodeB supports up to 2 IMA linkGroups,
- When populated with iCCM or iCCM2, the nodeB supports simultaneously IMA and
multiPcm.
UA 5-0:
The nodeB is populated with the iCCM.
IMA simultaneously with xPcm is not supported.
4.2.2
CEM RELATED:
An algorithm is in charge of assigning the different BBU roles to the CEM BBU
components. Therefore the kind of traffic handle by a CEM can not be predicted in
configuration phase.
UA 4-2:
Each BBU component is configured with one BBU role.
4.2.3
MULTIPCM:
UA5-1:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 233/263
The xPcm mode is supported. Either all the nodeB E1 are in xPcm mode, or the nodeB is
configured with a mix of n*E1 IMA and p*E1 in xPcm.
Hspa over xPcm is supported.
UA 4-2, UA5-0:
The nodeB multiPCM configuration is no more supported.
4.2.4
IMA:
UA5-1:
Either all the nodeB E1 are inserted within an IMA linkGroup, or the nodeB is configured
with a mix of n*E1 IMA and p*E1 in xPcm.
UA 4-2, UA5-0:
The vcc PCR can be set with a value higher than 4490 cells/s, up to the IMA linkGroup
bandwidth, this value is taken into consideration by the NodeB without correction.
UA 4-0 & 3:
-
The vcc PCR must be set with a value lower than 4490 cells/s.
If a higher PCR value is set, nodeB automatically reduces PCR value to 4490 cell/s.
The CCM card allows configuring only one IMA linkGroup per nodeB.
All the PCM links declared from OMC-B have to be part of the IMA group (to avoid
managing mix configuration: IMA and not IMA).
UA 4-2:
The Previous IMA LG Bw reduction/Restoration is replaced by a new one. The NodeB
Call processing is no more involved in traffic reduction/restoration, beside atm Vcc are
deactivated/activated.
Reason for change: satisfies the RNC aal2 Congestion Management mechanism
introduced for Hsdpa traffic.
The parameters: IMA DefenseActivation and IMA WeightingFc are removed.
UA 4-1:
NodeB IMA bandwidthReduction defense mechanism is activated by setting the
parameter: IMA DefenseDelay.
The parameter IMA DefenseActivated is no more present.
IMA DefenseDelay parameter is optional.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 234/263
4.2.5
N E1 XPCM + P E1 IMA:
UA 5-1:
The nodeB supports simultaneously n*E1 in xPCM mode and p*E1 in IMA mode.
Hspa vcc can be configured over single E1 (Hspa over xPcm)
4.2.6
AAL1 CES
4.2.7
UA 5-0:
AAL1 CES SDT NOT available.
QOS
NodeB set of priorityLevel values, case of trafficShaping Not activated:
UA 4-2:
Raison for Modification:
- Introduction of CES,
- Introduction of Hsdpa Vcc,
- MCR taken into account by NodeB.
See 3
SC recommended
for the interface
SC configured in
NodeB
UP DS
rtVBR
UBR
UP NDS
nrtVBR
UBR
CP
rtVBR
UBR
CCP
rtVBR
UBR
OAM
UBR
UBR+/MCR
PriorityLevel
- As long as the MCR is not taken into account in NodeB, the CP and CCP serviceCategory is
changed from UBR+ to UBR, in parallel the UP DS PriorityLevel is changed from 0 to 1 (same
as CP and CCP PL).
- The MCR configured against the OAM Vcc is taken into account by the scheduling.
UA3:
Note: It was assumed that the MCR is taken into account by the NodeB)
VCC
UP DS
SC recommended
for the interface
rtVBR
SC configured in
NodeB
UBR
PriorityLevel
0
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 235/263
4.2.8
UP NDS
nrtVBR
UBR
CP
rtVBR
UBR+ / MCR
CCP
rtVBR
UBR+ / MCR
OAM
UBR
UBR+/MCR
TRAFFIC MANAGEMENT
UA 4-1 > 3:
MCR configured for UBR+ VCC, is not taken into consideration by NodeB when
trafficShaping is not activated.
AAL2 Vcc can not be configured with UBR+ serviceCategory. Only AAL5 VCC may be
configured with UBR+.
Minimum throughput for full E1 is: 1, 92 kbits/s / 20 = 96 kbits/s for both full
E1 and IMA linkGroup composed of up to 8 E1s. NodeB OAM converts
kbits/s into bits/s using ratio 1000. Therefore minimum throughput is
227cells/s.
Case of E1 Drop&Insert 15/15, the minimal cell rate is 227/2 = 114 cells/s.
Case of T1:
UA 4-1 & 3:
The OAM Vcc is still provided by factory, configured with UBR+/MCR.
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 236/263
When trafficShaping is not activated, case of IMA, the NodeB accepts and dont correct a
PCR value higher than E1 bandwidth. The maximum PCR value is #PCM*(PCM
bandwidth-IMA overhead). The nodeB cut the egress traffic at this PCR.
UA3:
TrafficShaping at VC level becomes optional.
When trafficShaping is not activated, case of IMA, the NodeB automatically reduces the
configured PCR value to [PCM LinkRate-IMA overhead] and cut the egress traffic at this
PCR.
Policing:
Policing is not activated.
UA 4:
Ingress traffic is cut at 16 Mb/s (equivalent to 8 E1).
UA 2:
Ingress traffic is cut at 8 Mb/s (equivalent to 4 E1).
4.3
MICRO NODEB
UA4-2:
The microNodeB atm is available.
4.4
PICO NODEB
UA4-2-5:
The picoNodeB atm is available.
4.5
PLANE RELATIVE
4.5.1
UA5-0:
The UMTS HSUPA traffic flow is added.
The Hsdpa and Hsupa are carried over different dedicated vcc.
4.5.2
UA4-2:
The UMTS HSDPA traffic flow is added.
Hsdpa is handled on Iub interface, not on Iur interface.
4.5.3
UA4:
On nodeB side, OAM traffic is carried VCC=0/32, set in factory. Change of this VCC
value requires a NodeB reset.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 237/263
4.5.4
4.5.5
CommonSRB:
UA4:
4 commonSRB are set per UMTS Radio Cell. One more commonSRB is added per UMTS
cell, dedicated to a second FACH, it is called cellFach.
RAB mapping:
UA4:
CSD64 is mapped to UP DS VCC.
4.5.6
UA4:
ALCAP is not implemented. NBAP protocol is enhanced in such a way to assume
ALCAP functions. Therefore NBAP is proprietary.
5 TRANSPORT IDENTIFIERS
Within the TEG, the transport identifiers are provided for the UMTS nodes: NodeB and RNC.
One decision tree is set per kind of bandwidthPool to make easier selection of table within this section:
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 238/263
SharedForAllTrafficTypes
SharedForAllTrafficTypes
Without
Without hspa
hspa Streaming
Streaming
SharedForAllTrafficTypes
SharedForAllTrafficTypes
With
With hspa
hspa Streaming
Streaming
NodeB
NodeB vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-3
5-3
NodeB
NodeB vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-4
5-4
RNC vpi/vci/sc
RNC vpi/vci/sc
Tables:
iubIf
Tables:
iubIf
5-8
[1-200]
5-14
[1-200]
5-9
[201-400]
5-15
[201-400]
5-10
[401-600]
5-16
[401-600]
5-11
[601-800]
5-17
[601-800]
5-12
[801-1200]
5-18
[801-1200]
5-13
[1201-2400]
5-19
[1201-2400]
Iub
Iub pathId:
pathId:
Table
Table 5-27
5-27
Iub
Iub pathId:
pathId:
Table
Table 5-28
5-28
IMA
IMA HP:
HP:
Table
Table 5-34
5-34
IMA
IMA HP:
HP:
Table
Table 5-34
5-34
primaryForTrafficType
primaryForTrafficType
One Qos
Up to 4 qos
?#Qos?
xPcm
?IMA/xPcm?
IMA
NodeB
NodeB vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-5
5-5
NodeB
NodeB vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-6
5-6
NodeB
NodeB vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-7
5-7
RNC
RNC vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-20
5-20
RNC
RNC vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-21
5-21
RNC
RNC vpi/vci/sc:
vpi/vci/sc:
Table
Table 5-22
5-22
Iub
Iub pathId
pathId
Table
Table 5-29
5-29
Iub
Iub pathId
pathId
Table
Table 5-30
5-30
Iub
Iub pathId
pathId
Table
Table 5-30
5-30
IMA
IMA HP:
HP:
Table
Table 5-32
5-32
IMA
IMA HP:
HP:
Table
Table 5-33
5-33
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 239/263
5.1
ATM VCC
On the Iub interface are configured user plane vcc for different qos according to the kind of UMTS traffic
they are assigned to.
The following vcc naming rule applies:
After migration from UA5 to UA6, and in UA6 as long as the hspa streaming is not enabled:
Vcc name
serviceCategory
UMTS flows
qos0 vcc
rtVbr
qos2 vcc
nrtVbr
qos3 vcc
ubr
Hspa I/B
Since the hspa streaming traffic is enabled one more kind of vcc is created:
5.1.1
Vcc name
serviceCategory
UMTS flows
qos0 vcc
cbr
qos1 vcc
rtVbr
qos2 vcc
nrtVbr
R99 I/B
qos3 vcc
ubr or ubr+
Hspa I/B
Yes
No
Add the alcap vcc for up to 200 nodeB:
Alcap vcc, RNC ECRacac = 0
5.1.1.2 UPGRADE
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 240/263
=> sharedForAllTrafficTypes
=> n qos0 rtVbr vcc, TDDS
=> n qos2 nrtVbr vcc, TDNDS
=> 1 or 2 qos3 ubr vcc
=> preferredForTrafficType
=> p qos3 nrtvbr vcc
TransportMap:
- Iub sharedForAllTrafficType bwPool linked to transportMap/1
- Iub preferredForTrafficType bwPool linked to transportMap/2
- IuCS and Iur aal2If linked to transportMap/1
admissionControl:
- qos2bwReservation
- qos1bwReservation
=> qos3bwReservation
=> qos2bwReservation
congestionManagement:
- qosDt 0 0 1 xx 2 yy 3 0 => qosDt 0 0 1 0 2 xx 3 yy
- qosBp 0 0 1 xx 2 yy 3 0 => qosBp 0 0 1 0 2 xx 3 yy
Note:
- Within a preferedForTrafficType bwPool, p qos3 vcc are configured, since the associated NodeB
IMA group is composed of p E1.
Overbooking factor:
Since more vcc configured on the Iub stm1 then more bandwidth reserved through the
trafficDescriptors, the overbooking factor must be re-calculated (atmIf/ ca bwpool 1 x 2 0 3 0 4
0 5 0), e.g.: x=700.
Pnni:
The pnni sPvc configured for the nodeB iubif [1, 200] in the previous release are not impacted
by the UA5 to UA6 migration procedure. After migration, these connections are still switched
on the pnni sPvc hairpins.
Only the pnni sPvc connections created for nodeB IubIf > 200 after migration terminate on the
application without being switched on the pnni sPvc hairpins.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 241/263
UA6
Add Hspa Streaming
qos1 vcc:
Previously existing DS vcc.
sharedForAllTrafficTypes:
- n qos0 rtVbr vcc, TDDS:
- qos0 vcc [vci range 4 bottom values] => qos1 rtVbr vcc tdt=6, TDDS
- qos0 vcc [vci range 3 top values]
=> qos0 cbr vcc tdt=1, TD=0
- n qos2 nrtVbr vcc, TDNDS
- 1 or 2 qos3 ubr/ubr+ vcc
qos0 vcc:
Qos0 vcc is created with
cbr and TD=0.
preferredForTrafficType:
- p qos3 nrtVbr vcc
=> p qos3 vbr/ubr/ubr+ vcc
5.1.2
NODEB INTERFACE
The table below summarizes the maximum number of vcc supported by the NodeB:
Atm User
Oam
Cp
Aal
Aal5
Aal5
Max # vcc
1
1
Ccp
Aal5
Alcap
Aal5
User traffic
Aal2
16
Remarks:
-
The nodeB oam vcc is pre-provisioned in factory with default vpi.vci 0.32.
The nodeB oam vpi.vci, like other I&C parameters, can be modified using WICL or
remote TIL (for nodeB).
Since the nodeB is populated with up to 6 CEM then up to 6 CCP vcc may be configured.
The TEG provides several NodeB vpi.vci tables according to the Iub context:
- The vcc belongs to a RNC SharedForTrafficTypes BwPool or primaryForTrafficType
bwPool.
- Within a sharedForAllTrafficTypes BwPool, the hspa streaming is or is not supported on
the Iub.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 242/263
Within a sharedForAllTrafficTypes bwPool, the Hspa Streaming traffic is supported on the Iub as an
option. If supported then a dedicated to streaming traffic vcc is created. The streaming vcc carries both
hspa and R99 streaming traffic.
Since the hspa streaming traffic is optional then two nodeB vpi.vci addressing plans are suggested:
- one without streaming vcc and
- one with streaming vcc.
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
Qos
0
2
3
na
VPI
1
1
1
1
1
1
0
41
49
48
35
VCI
to
to
+
34
to
33
32
47
55
56
40
nodeB SC
ubr1
ubr2
ubr+3
ubr1
ubr1
ubr1
ubr+3
POC SC
rtVbr
nrtVbr
ubr
rtVbr
rtVbr
rtVbr
ubr
#
7
7
2
1
6
1
1
16
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
Qos
0
1
2
3
na
VPI
1
1
1
1
1
1
1
0
VCI
45 to
41 to
49 to
48 +
34
35 to
33
32
47
44
55
56
40
nodeB SC
ubr0
ubr1
ubr2
ubr+3
ubr1
ubr1
ubr1
ubr+3
POC SC
cbr
rtVbr
nrtVbr
ubr
rtVbr
rtVbr
rtVbr
ubr
#
3
4
7
2
1
6
1
1
16
Remarks:
-
The vci 41 to 56 are reserved for the aal2 vcc. These vci values are shared between the
release99 and the hspa vcc. Per default two vci (vci=48, 56) are allocated to the hspa I/B
vcc. If more hspa I/B vcc are required either in the sharedForAllTrafficTypes or the
primaryForTrafficType BwPool then the highest vci from the qos2, qos1 or qos0 vci range
are going to be assigned to the hspa I/B vcc.
The Alcap vcc introduced in UA6 is identified with the vci not used in the previous
release.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 243/263
AAL
aal2
Qos
3
VPI
1
VCI
41 to 56
nodeB SC
ubr3
POC SC #
ubr
16
AAL
Qos
VPI
aal2
aal2
aal2
1
2
3
1
1
1
VCI
42 to
43 to
44 to
nodeB SC
42
43
44
POC SC
ubr x
ubr x
ubr3
#
1
1
1
3
5.1.3
RNC INTERFACE
The vpi on the RNC-POC interface are fixed to 0 in such a way to optimize the RNC 16pOC3/Stm1
resources.
The vci on the RNC-POC interface are indexed by IubIf parameter value; each nodeB being identified
from the RNC side by means of an IubIf value called k in the following tables.
This section doesnt consider the vpi.vci to configure on the pnni Hairpin interface.
Rule description:
- On the classical 16pOC3 FP up to 1200 nodeB may be configured whereas on the 16pOC3
MS3 FP up to 2400 nodeB may be configured.
- On the classical 16pOC3 FP, the specified vpi.vci space allows to configure up to 800 nodeB
if 3 stm1/oc3 allocated to the Iub interface. A fourth stm1/oc3 must be allocated to the Iub
interface if more than 800 nodeB configured. Refer to default RNC port assignment on
5.2.1.2 .
- For the nodeB identified by IubIf [1, 200]: the associated vpi.vci naming rule applies on the
three stm1: 800, 801 and 802. This rule provides backward compatibility with the UA5
vpi.vci naming rule.
- For the nodeB identified by IubIf [201, 400]: the associated vpi.vci naming rule applies only
on the stm1 800,
- For the nodeB identified by IubIf [401, 600]: the associated vpi.vci naming rule applies only
on the stm1 801,
- For the nodeB identified by IubIf [601, 800]: the associated vpi.vci naming rule applies only
on the stm1 802,
- For the nodeB identified by IubIf [801, 1200]: a fourth stm1 from the classical 16pOC3 FP,
is going to be allocated to the Iub (e.g.: port 808), the associated vpi.vci naming rule applies
only on this stm1. The fourth stm1 is going to be assigned to the iub interface, since as soon
as the pnni hairpins are removed and the classical 16pOC3FP attributes set accordingly, see
3.6.16..
- For the nodeB identified by IubIf [1201, 2400]: the RNC must be populated with a 16pOC3
MS3 FP to support so many nodeB. The associated vpi.vci naming rule applies to all the
stm1 involved on the Iub.
- One additional vcc is reserved for POC oam. This vcc is used as an option.
- The TEG provides several suggestions for the RNC vpi.vci values according to the contexts:
- SharedForAllTrafficTypes or primaryForTrafficType preference,
- Hspa Streaming traffic supported or not within the SharedForAllTrafficTypes
bwPool.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 244/263
The nodeB spreading on the different RNC Iub stm1/oc3 is realized by assigning to the nodeB an IubIf
value from the different IubIf ranges: [0,200], [201, 400], [401, 600], [601, 800], [800, 1200].
For the nodeB k = [1201, 2400] configured on the RNC populated with the 16pOC3 MS3 FP, the vcc can
be configured on all the Iub port.
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
aal5
Port
800
&
801
&
802
VPI
k = 1 to 200
VCI
34
42
41
50
51
33
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
to
to
+
40 + 24*(k-1)
48 + 24*(k-1)
49 + 24*(k-1)
to
56 + 24*(k-1)
32
5033 - k
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
ubr
rtVbr
#
7
7
2
1
6
1
1
1
Table 5-8, RNC vpi.vci, sharedForTrafficTypes, No hspa streaming, IubIf in the range [1, 200]
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
800
VPI
5034
5042
5041
5050
5051
5033
5057
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
k = 201 to 400
to
to
+
VCI
5040 + 25*(k-201)
5048 + 25*(k-201)
5049 + 25*(k-201)
to
5056 + 25*(k-201)
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
7
7
2
1
6
1
1
Table 5-9, RNC vpi.vci, sharedForTrafficTypes, No hspa streaming, IubIf in the range [201, 400]
RNC Iub interface, preference sharedForAllTrafficTypes,
VCC type:
qos0
qos2
qos3
CP
CCP
NodeB oam
Alcap
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
801
VPI
5034
5042
5041
5050
5051
5033
5057
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
k = 401 to 600
to
to
+
VCI
5040 + 25*(k-401)
5048 + 25*(k-401)
5049 + 25*(k-401)
to
5056 + 25*(k-401)
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
7
7
2
1
6
1
1
Table 5-10, RNC vpi.vci, sharedForTrafficTypes, no hspa streaming, IubIf in the range [401,
600]
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 245/263
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
802
VPI
5034
5042
5041
5050
5051
5033
5057
+ 25*(k-601)
+ 25*(k-601)
+ 25*(k-601)
+ 25*(k-601)
+ 25*(k-601)
+ 25*(k-601)
+ 25*(k-601)
k = 601 to 800
to
to
+
VCI
5040 + 25*(k-601)
5048 + 25*(k-601)
5049 + 25*(k-601)
to
5056 + 25*(k-601)
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
7
7
2
1
6
1
1
Table 5-11, RNC vpi.vci, sharedForTrafficTypes, no hspa streaming, IubIf in the range [601,
800]
RNC Iub interface, preference sharedForAllTrafficTypes,
VCC type:
qos0
qos2
qos3
CP
CCP
NodeB oam
Alcap
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
Port
808
VPI
k = 801 to 1200
VCI
34
42
41
50
51
33
57
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
to
to
+
40 + 25*(k-801)
48 + 25*(k-801)
49 + 25*(k-801)
to
56 + 25*(k-801)
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
7
7
2
1
6
1
1
Table 5-12, RNC vpi.vci, sharedForTrafficTypes, no hspa streaming, IubIf in the range [801,
1200]
RNC Iub interface, preference sharedForAllTrafficTypes,
VCC type:
qos0
qos2
qos3
CP
CCP
NodeB oam
Alcap
AAL
aal2
aal2
aal2
aal5
aal5
aal5
aal5
Port
800
&
801
&
802
VPI
16383
16391
16390
16399
16400
16382
16406
k = 1201 to 2400
VCI
+ 25*(k-1201) to 16389 + 25*(k-1201)
+ 25*(k-1201) to 16397 + 25*(k-1201)
+ 25*(k-1201) + 16398 + 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201) to 16405 + 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
SC
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
7
7
2
1
6
1
1
Table 5-13, RNC vpi.vci, sharedForTrafficTypes, no hspa streaming, IubIf in the range [1201,
2400]
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
aal5
port
800
&
801
&
802
VPI
38
34
42
41
50
51
33
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
VCI
to
to
to
+
40
37
48
49
to
56 + 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
+ 24*(k-1)
32
5033 - k
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
1
25
Table 5-14, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [1, 200]
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 246/263
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
800
VPI
5038
5034
5042
5041
5050
5051
5033
5057
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
VCI
to
to
to
+
5040
5037
5048
5049
to
5056 + 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
+ 25*(k-201)
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
25
Table 5-15, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [201, 400]
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
801
VPI
5038
5034
5042
5041
5050
5051
5033
5057
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
VCI
to
to
to
+
5040
5037
5048
5049
to
5056 + 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
+ 25*(k-401)
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
25
Table 5-16, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [401, 600]
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
802
VPI
5038
5034
5042
5041
5050
5051
5033
5057
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
VCI
to
to
to
+
5040
5037
5048
5049
to
5056 +25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
+25*(k-601)
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
25
Table 5-17, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [601, 800]
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
808
VPI
38
34
42
41
50
51
33
57
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
VCI
to
to
to
+
40
37
48
49
to
56 + 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
+ 25*(k-801)
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
25
Table 5-18, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [801, 1200]
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 247/263
AAL
aal2
aal2
aal2
aal2
aal5
aal5
aal5
aal5
port
800
&
801
&
802
VPI
16387
16383
16391
16390
16399
16400
16382
16406
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
VCI
to
to
to
+
16389
16386
16397
16398
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
+ 25*(k-1201)
to 16405 + 25*(k-1201)
SC
cbr
rtVbr
nrtVbr
ubr+ / ubr
rtVbr
rtVbr
ubr
rtVbr
#
3
4
7
2
1
6
1
1
25
Table 5-19, RNC vpi.vci, SharedForTrafficTypes, hspa streaming, IubIf in the range [1201,
2400]
Remarks:
-
Per default, within the SharedForTrafficTypes bwPool, up to two vci are allocated to the
hspa I/B vcc. If more hspa I/B vcc are required either in the sharedForAllTrafficTypes or
the primaryForTrafficType BwPool then the highest vci from the qos2, qos1 or qos0 vci
range are going to be assigned to the hspa I/B vcc.
In such a way to provide backward compatibility with the UA5 release, for each nodeB
identified by IubIf=[1, 200], the Alcap vci and the other nodeB vcc are not contiguous.
When Pnni is configured on the RNC/POC interface, then the RNC/POC atm interface is
NNI, the vpi field is coded on 12 bits; therefore the range of vpi values is: [0, 4095]. The
vpi/vci values are automatically chosen by Passport in a pre-configured range at Pnni sPvc
setup.
SC
#
ubr/ubr+ 16
Remark: One available vci amongst the pool of vci reserved per nodeB.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 248/263
AAL
port
VPI
VCI
aal2
aal2
aal2
SC
rtVbr
nrtVbr
ubr/ubr+
1
1
1
3
AAL
port
VPI
VCI
aal2
aal2
aal2
SC
rtVbr
nrtVbr
ubr/ubr+
4
4
5
13
5.1.4
PNNI
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 249/263
In UA6, the Iub pnni sPvc hairpin is still involved in the pnni iub traffic from the nodeB configured in
the previous release (up to 200 nodeB).
The pnni sPvc from the additional NodeB configured in UA6 dont terminate on the RNC pnni hairpins,
on the contrary the additional pnni sPvc originates (or terminates) on the application (atmMpe, aal2If,
iubIf).
Related to the nodeB already configured in UA5 and using the pnni, userPlane, CP, CCP and oam pnni
sPvc terminate on the pnni hairpins.
5.2
FP ATTRIBUTES
5.2.1
16POC3/STM1 FP ATTRIBUTES
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 250/263
RNC
RNC
16pOC3/Stm1
16pOC3/Stm1 FP
FP
Em
Rec 7
15 Em
Rec
Em 6
Rec
14 Em
Rec
Iur/Iu UNI/NNI
APC 11
APC
Em 5
Rec
13 Em
Rec
N/U
Em 3
Rec
11 Em
Rec
UNI / Pnni
Em 2
Rec
10 Em
Rec
UNI / Pnni
Em 1
Rec
UNI / Pnni
Em 0
Rec
N/U
Iub
POC
POC
APC 22
APC
12 Em
Rec
APC 00
APC
Em 4
Rec
9 Em
Rec
User side
UNI
Iub sPVC Hairpins
Network side
8 Em
Rec
TEG
Figure 5-4 16pOC3 connectivity scheme, without Pnni on the Iu/Iur interface
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 251/263
RNC
RNC
16pOC3/Stm1
16pOC3/Stm1 FP
FP
N/U
User side
User side
Em 6
Rec
14 Em
Rec
Em 5
Rec
APC 33
APC
Network side
15 Em
Rec
APC 11
APC
Em
Rec 7
13 Em
Rec
Em 4
Rec
12 Em
Rec
Em 3
Rec
11 Em
Rec
UNI / Pnni
Em 2
Rec
10 Em
Rec
UNI / Pnni
Em 1
Rec
Iur/Iu Pnni
N/U
User side
Iub
Network side
APC 22
APC
APC 00
APC
POC
POC
UNI / Pnni
Em 0
Rec
9 Em
Rec
UNI
Network side
User side
UNI
Iub sPVC Hairpins
Network side
8 Em
Rec
TEG
Figure 5-5 16pOC3 connectivity scheme, with Pnni on the Iu/Iur interface
Per default three stm1/oc3 are assigned to the Iub interface, in combination with the vpi.vci specified in
5.1, this allows to configure up to 800 nodeB. The configuration of up to 1200 nodeB requires the
allocation of a fourth stm1/oc3 to the Iub.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 252/263
Iub
Iu/Iur
Iu/Iur/Iub
- Iub VPT
Iu/Iur/Iub
Iub VPC
Iu/Iur/Iub
Iu/Iur VPT
sPvc
or
Pvc
sPvc
or
Pvc
sPvc
or
Pvc
- Iu/Iur
sPvc H
- Iu/Iur
sPvc H
- Iu/Iur
sPvc H
- Iu/Iur
sPvc H
(network)
(user)
(network)
(user)
Iu/Iur
Iu/IurVPC
Not
Used
Iub
sPvc
Hairpin
(network)
Iub
Iub
sPvc
sPvc
Hairpin Hairpin
(user) (network)
APC 3
Iub
APC 2
Iub
APC 1
APC 0
Iub
sPvc
Hairpin
(user)
Not
Used
Iu/Iur
Iu/Iur
sPvc
or
Pvc
sPvc
or
Pvc
SDH15
SDH0
SDH1
SDH2
SDH3
SDH4
SDH5
SDH6
SDH7
SDH8
SDH9
SDH10
SDH11
SDH12
SDH13
SDH14
12
12
12
12
12
12
16384
16384
16384
1024
1024
1024
1024
1024
8192
8192
8192
8192
1024
1024
200
22
64
64
64
64
64
64
64
64
64
64
8192
8192
8192
8192
64
512
512
AtmIf CA maxVccs
3401
3401
3401
536
4802
536
536
64
2500
2500
2500
2500
500
500
AtmIf CA maxVpcs
200
22
AtmIf CA maxVpts
200
22
AtmIf CA minAutoSelectedVciForVpiZero
12982
12982
12982
1023
1023
1023
1023
1023
5691
5691
5691
5691
523
523
AtmIf CA maxAutoSelectedVciForVpiZero
16383
16383
16383
1023
1023
1023
1023
1023
8191
8191
8191
8191
1023
1023
AtmIf CA minAutoSelectedVpi
4095
4095
4095
255
255
255
255
255
255
4095
4095
AtmIf CA maxAutoSelectedVpi
4095
4095
4095
255
255
255
255
255
255
4095
4095
AtmIf Ca minAutoSelectedVciForNonZeroVpi
63
63
63
63
63
63
63
63
32
8191
8191
8191
8191
63
511
511
AtmIf Ca maxAutoSelectedVciForNonZeroVpi
63
63
63
63
63
63
63
63
32
8191
8191
8191
8191
63
511
511
3402
3402
3402
537
5203
737
581
87
2501
2501
2501
2501
501
501
AtmIf CA maxVpiBits
AtmIf ConnMap Ov numVccsForVpiZero
[maxVccs+maxVpcs+2*maxVpts+1
Lp Eng Arc Apc Ov connectionPoolCapacity
10743
6608
7504
3504
1081
28359
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 253/263
5.2.2
5.3
IP
Within the RNC, each nodeB interface is identified by an ipIf instance.
Suggested ipIf values for up to 2400 nodeB:
ipIf
Interface:
Iub
IuPS
Values
to
2400
na
#
2400
5.4
AAL2
5.4.1
IUBIF / AAL2IF
Between the RNC and the NodeB are configured the aal2 paths.
In the RNC, all the paths terminating in one nodeB are grouped within an aal2If component instance. The
aal2If instance is assigned to one IubIf instance. There is a one to one relationship between an aal2If
instance and an IubIf instance.
IubIf and aal2if instance value range:
iubIf
Interface:
Iub
Iub extension
1
300
Values
to
299
to
2400
#
299
2101
2400
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 254/263
1
600
300
375
350
1225
Values
to
299
to
2700
to
349
to
564
to
374
to
1235
#
299
2101
50
190
25
11
5.4.2
PATHID:
The TEG provides the pathId tables for the contexts:
- sharedForAllTrafficTypes bwPool:
- without hspa Streaming supported on the Iub,
- with hspa Streaming supported on the Iub,
- primaryForTrafficType bwPool.
Remark:
The pathId table for case of sharedForAllTrafficTypes bwPool without hspa streaming may be
also used during the migration between UA5 and UA6 with hspa streaming.
The table below indicates the suggested Pathid values to configure per nodeB according to iubIf value
assigned to NodeB. (The iubIf is noted k in the table).
1/ Case of sharedForAllTrafficTypes bwPool, without hspa streaming supported:
Iub
Path
qos0
qos2
qos3
QOS
PATHID
0
(16*k)
to ((16*k) - 6)
2
((16*k) - 8) to ((16*k) - 14)
3
((16*k) - 15) + ((16*k) - 7)
#
7
7
2
Range
1
43200
Iub
Path
qos0
qos1
qos2
qos3
QOS
PATHID
0
(16*k)
to ((16*k)-2)
1
((16*k) - 3) to ((16*k)-6)
2
((16*k) - 14) to ((16*k) - 8)
3
((16*k) - 15) + ((16*k) - 7)
#
3
4
7
2
Range
1
43194
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 255/263
1 qos
Iub
Path
QOS
Pathid
qos3
16
4/ Case of primaryForTrafficType bwPool, case of qos1, qos2 and qos3 vcc configured:
3 qos
Path
Iub
QOS
Pathid
1
2
3
4
4
5
qos1
qos2
qos3
Table 5-30, PathIds for primaryForTrafficType, case of three kinds of qos vcc
5.5
IMA
5.5.1
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 256/263
E1_ 1
E1_ 2
E1_ 3
E1_ 4
E1_ 5
E1_ 6
E1_ 7
E1_ 8
Vcc
qos3
qos3
qos3
qos3
qos3
qos3
qos3
qos3
HP
1
2
3
4
5
6
7
8
qos1
qos2
qos3
E1_ 3
E1_ 4
qos1
qos2
qos3
E1_ 5
E1_ 6
E1_ 7
E1_ 8
qos1
qos2
qos3
qos3
qos1
qos2
qos3
HP
1
2
3
4
5
6
7
8
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 257/263
NodeB Vcc
CP
CCP
Alcap
OAM
rank
1
1 to 6
1
1
HP
qos0
qos2
qos3
1
1
1
1
1
1
1 E1
qos0
qos2
2
2
2
2
2 E1
qos0
qos2
qos0
qos2
qos2
qos2
qos2
3
3
4
4
5
6
7
3
3
4
5
6
7
8
3 E1
1 E1
2 E1
3 E1
4 E1
5 E1
6 E1
7 E1
8 E1
4 E1
5 E1
6 E1
7 E1
8 E1
12 aal2 vcc
NodeB Vcc
CP
CCP
Alcap
OAM
qos0
qos1
qos2
qos3
qos0
qos1
qos2
qos0
qos1
qos2
qos1
qos2
qos2
qos2
qos2
rank
1
1 to 6
1
1
1
1
1
1
2
2
2
3
3
3
4
4
5
6
7
HP
0
1
1
1
1
2
2
2
3
3
3
4
5
6
7
8
15 aal2 vcc
5.5.2
5.5.3
TRAFFIC DESCRIPTOR
5.6
TRAFFIC DESCRIPTOR
for
all
VCCs.
The determination of TrafficDescriptor values should be the result of an UMTS Dimensioning study as
long as they are involved in the atm traffic regulation mechanismes.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 258/263
5.6.1
AAL2 VCC TD
Within the RNC the vcc TD are taken into consideration by the atm Cac, the link Cac and the
congestionManagement. It is not recommended to activate the trafficShaping at vc level.
Within the RNC, as an option the VPC trafficShaping is activated, then the vpc TD is configured.
The atmConnection TD values satisfy the atm Cac condition as long as the RNC port overbooking factor
is correctly set:
xPcm
IMA:
1
2
3
4
5
6
7
8
E1
E1
E1
E1
E1
E1
E1
E1
1
2
3
4
4
4
4
4
1
2
3
3
4
5
6
7
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1
2
3
3
3
3
3
3
1
2
3
4
4
4
4
4
1
2
3
3
4
5
6
7
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
1 or 2
Rule: Iub_TD_
As long as the nodeB IMA is populated with 3 E1, as many qosx vcc are configured as # E1.
With x=[0 and 2] if no hspa streaming supported, x=[0, 1 and 2] if hspa streaming supported.
When a fourth E1 is added, configure one more qos0 vcc if no hspa streaming supported or one more qos1
vcc if hspa streaming supported.
When the fifth, the sixth, the seventh or the eighth E1 is added, configure one more qos2 vcc per added E1.
Vcc trafficDescriptor:
- As long as the nodeB IMA is populated with up to 3 E1 included, the nodeB is configured
with as many qosx vcc as amount of E1 on the nodeB side.
Per definition a set of vcc is composed of (1 qos0 vcc, 1 qos2 vcc) when no hspa streaming or
(1 qos0 vcc, 1 qos1 vcc, 1 qos2 vcc) when hspa streaming.
On the RNC side, the TD for a set of vcc are set in such a way
bandwidth minus bandwidth portion reserved for the signaling.
- When adding the fourth E1, one more qos0 vcc is configured if no hspa streaming supported
or one more qos1 vcc is configured if hspa streaming supported.
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 259/263
The TD configured against the added vcc is set in such a way vcc ECRgcac = E1 bandwidth
minus bandwidth portion reserved for the signaling.
- When adding the fifth, the sixth, the seventh or the eighth E1, one more qos2 vcc is
configured per added E1.
The TD configured against the added qos2 vcc is set in such a way qos2vcc ECRgcac = E1
bandwidth minus bandwidth portion reserved for the signaling.
5.6.2
AAL5 VCC TD
On the RNC IMA interface, the Alcap, CP and CCP vcc trafficDescriptors are set in such a way ECR=0.
The ECR=0 is obtained when setting PCR=SCR=MBS=0.
The RNC doesnt allow to configure PCR=SCR=MBS=0 when the TDT = 6 (TrafficDescriptorType).
Therefore:
Rule: Iub_IMA_12
The TDT=1 is set against the Alcap, CP and CCP vcc. Beside the rtVbr serviceCategory is assigned to
the Alcap, CP and CCP vcc.
5.7
PARAMETERS
The aim of this section is to provide a complement of information on some Transport parameters.
5.7.1
tdt
Tx tdp1
Rx tdt1
Tx tdp2
Rx tdt2
Tx tdp3
Rx tdt3
pcr
pcr
Vbr
pcr
pcr
scr
scr
mbs
mbs
Ubr
Ubr+
pcr
pcr
mdcr
mdcr
Cbr
5.7.2
PARAMETER CLASS
Parameters are described in NTP and UPUG documents. Target of this section is to bring some
additional information on some parameters.
Class of parameter:
Class 0: the NE must be restarted to take into account a new parameter value.
Class 2: the parameter can be changed on-line provided that the object (or its parent
object) is locked.
Class 3: the parameter can be changed on-line without impact on the service. The new
value is taken into account either immediately or for new calls only.
Operator : the parameter is configurable from the OMC and seen by the operator
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 260/263
Manufacturer : the parameter is configurable from the OMC and only seen by ALU
engineering teams
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 261/263
6 ABBREVIATIONS
AAL: ATM Adaptation Layer
ACAC: Actual CAC
AESA: ATM End Station Address
A2EA: AAL2 End Address
ALCAP:
Access Link Control Application Part
APS: Automatic Protection Switching
ASP: ATM Service Provider
AU-4: Administrative Unit 4 (149,74 Mb/s), from SDH STM1 [R40]
BER: Bit Error Rate
CAC: Connection Admission Control
CC:
Call Control
CDV: Cell Delay Variation
CDVT: Cell Delay Variation Tolerance
CES: Circuit Emulation Service
CLR : Cell Loss Ratio
CP:
Control Port
CPCH: Common Packet Channel
CCP: Communication Control Port
CID:
Channel IDentifier (aal2)
CRB: CommonRadioBearer
CRC: Cyclic Redundancy Code
DCH: Dedicated CHannel
DchFP: Dedicated Channel Frame Protocol
DS:
Delay Sensitive
DSCH: Downlink Shared Channel
ECR: Equivalent Cell Rate
E-DCH:
Extended Dedicated Channel
EP:
Emission Priority
FACH: Forward Access Channel
FEBE: Far End Block Errors,
FP:
Functional Processor (Passport definition)
GCAC: Generic CAC
GMM: GPRS Mobility Management
GQM: GenericQueueManager
HSDPA:
High Speed Downlink Packet Access.
HSUPA:
High Speed Uplink Packet Access
LCD: Loss of Cell Delineation
LLC: LogicalLinkControl
MBS: Maximum Burst Size
MPE: MultiProtocolEncapsulation
MSTE : MultiplexSection Terminating Equipment
MUX: Multiplexer
NBAP: NodeB Application Part
NBAP-c:
NBAP common
NBAP-d:
NBAP dedicated
NDS: Non Delay Sensitive
NSAP: Network Service Access Point
NNI: Network to Network Interface
OAM: Operation Administration Maintenance
OEM: Other Equipment Manufacturer
PCH: Paging Channel
PCM: Pulse Code Modulation
PCR: Peak Cell Rate
PDH: Plesiochrone Digital Hierarchy
PLCP: Physical layer Convergence Protocol
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 262/263
END OF DOCUMENT
ALU confidential
UMT/IRC/APP/7149
07.02 / EN
Standard
29/06/2009
Page 263/263