Ran Interfaces Protocols PDF

RNC Architecture and functionality
- RAN Interfaces & Protocols -

RAN Interfaces & Protocols
Copyright Nokia Networks Oy 2006

The information in this document is subject to change without notice and describes only
the product defined in the introduction of this documentation. This document is intended
for the use of Nokia Networks' customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be reproduced or transmitted in
any form or means without the prior written permission of Nokia Networks. The
document has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Networks welcomes
customer comments as part of the process of continuous development and improvement
of the documentation.
The information or statements given in this document concerning the suitability, capacity,
or performance of the mentioned hardware or software products cannot be considered
binding but shall be defined in the agreement made between Nokia Networks and the
customer. However, Nokia Networks has made all reasonable efforts to ensure that the
instructions contained in the document are adequate and free of material errors and
omissions. Nokia Networks will, if necessary, explain issues which may not be covered
by the document.
Nokia Networks' liability for any errors in the document is limited to the documentary
correction of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT
FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR
CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use
of this document or the information in it.
This document and the product it describes are considered protected by copyright
according to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright Nokia Networks Oy 2006. All rights reserved.

Table of Contents:
RAN Interfaces & Protocols .....................................................................................9
UTRAN Interfaces .................................................................................................10
2.1. General Protocol Model...................................................................................11
2.1.1. Control Plane and User Plane......................................................................11
2.1.2. Radio vs. Transport Network Layer..............................................................12
2.1.3. Bearer Concept............................................................................................13
2.1.4. ATM for Transport........................................................................................14
2.1.5. ATM / AAL5 .................................................................................................15
2.1.6. ATM / AAL2 .................................................................................................16
2.1.7. AAL2 Data Mapping.....................................................................................17
2.1.8. AAL5 Data Mapping.....................................................................................18
2.1.9. AAL5 vs. AAL2.............................................................................................19
2.1.10. Transport Network Control Plane ...............................................................20
2.1.11. AAL5 in User Plane ...................................................................................21
2.1.12. Convergence Protocols..............................................................................22
2.2. Exercise ..........................................................................................................23
3. Iub Interface ..........................................................................................................24
3.1. Interface Protocol Structure.............................................................................25
3.1.1. NBAP Signalling Protocol ............................................................................25
3.1.2. Common NBAP Procedures ........................................................................26
3.1.3. Dedicated NBAP Procedures.......................................................................27
3.1.4. Frame Protocol (FP) ....................................................................................28
3.1.5. User Plane Transport Channels...................................................................29
3.1.6. NBAP over AAL5 .........................................................................................30
3.2. Exercise ..........................................................................................................31
4. Iur Interface ...........................................................................................................32
4.1.1. RNSAP Signalling Protocol..........................................................................33
4.1.2. Serving RNC vs. Drift RNC ..........................................................................34
4.1.3. Interface Protocol Structure .........................................................................35
4.2. Exercise ..........................................................................................................36
5. Iu-CS/PS Interfaces...............................................................................................36
5.1.1. RANAP Signalling Protocol..........................................................................37
5.1.2. RANAP (cont.) .............................................................................................38
5.1.3. Iu-CS and Iu-PS Control Plane ....................................................................39
5.1.4. Iu-CS User Plane.........................................................................................40
5.1.5. Iu-PS User Plane .........................................................................................41
5.1.6. IP over IP.....................................................................................................42
5.1.7. GPRS Tunneling Protocol (GTP) .................................................................43
5.1.8. Convergence Protocols................................................................................44
5.1.9. 3GPP Release 4 Architecture ......................................................................45
5.2. Exercise ..........................................................................................................46
6. Iu-BC Interface ......................................................................................................47
6.1.1. Iu-BC Interface Protocol Structure ...............................................................48
6.1.2. SABP...........................................................................................................49
6.1.3. TCP .............................................................................................................50
1.
2.

6.2. SAB Service Animation ...................................................................................51

6.2.1. RNC can serve up to four CBCs ..................................................................51
6.2.2. Message broadcasting.................................................................................52
6.3. Exercise ..........................................................................................................53
7. Iu-PC Interface ......................................................................................................53
7.1 Interface Protocol Structure .................................................................................54
7.1.1. Iu-PC Interface Protocol Structure ...............................................................54
7.1.2. Positioning Calculation.................................................................................55
7.1.3. Information Exchange..................................................................................56
7.2 Exercise ..............................................................................................................57
8. Uu Interface...........................................................................................................58
8.1.1. Introduction..................................................................................................59
8.1.2. Physical Channels .......................................................................................60
8.1.3. Transport Channels .....................................................................................61
8.1.4. New Channels for HSDPA ...........................................................................62
8.1.5. Logical Channels .........................................................................................63
8.1.6. Mapping between Logical, Transport and Physical Channels ......................64
8.1.7. Mapping of User Data ..................................................................................65
8.1.8. MAC Protocol ..............................................................................................66
8.1.9. MAC Layer Logical Entities..........................................................................67
8.1.10. RLC Protocol .............................................................................................68
8.1.11. RRC Signalling Protocol ............................................................................69
8.1.12. RRC Signalling Protocol ............................................................................70
8.1.13. User Plane Transport.................................................................................71
8.1.14. User Plane Protocols: PDCP .....................................................................72
8.1.15. User Plane Protocols: BMC .......................................................................73
9. Signalling Transport...............................................................................................74
9.1. Signalling Transport at the Iub Interface..........................................................75
9.1.1. Iub Protocol Structure (1).............................................................................75
9.1.2. Iub Protocol Structure (2).............................................................................76
9.2. Broadband SS7 Protocol Structure..................................................................77
9.2.1. Iur Protocol Structure (1)..............................................................................77
9.2.4. Iu Protocol Structure ....................................................................................80
9.3. Exercise ..........................................................................................................81
10.
O&M and Supporting Interfaces.........................................................................82
10.1.
Interface Protocol Structure........................................................................83
10.2.
Exercise .....................................................................................................86
11.
RRC Connection Establishment.........................................................................86
11.1.
RRC Connection Establishment Procedure................................................87
11.1.1. RRC connection is initiated by UE .............................................................87
11.1.2. RRC Connection Request..........................................................................88
11.1.3. Admission Control......................................................................................89
11.1.4. Setting up a Dedicated Channel ................................................................90
11.1.5. Setting up a Dedicated Channel (2) ...........................................................91
11.1.6. Setting up a Dedicated Channel (3) ...........................................................92
11.1.7. RRC Connection Setup Message ..............................................................93
11.1.8. RRC Connection Setup Complete..............................................................94

11.1.9. Radio Bearer Management ........................................................................95

11.2.
Exercise .....................................................................................................96
12.
Non-Access Stratum Signalling..........................................................................97
12.1.
Example: Mobile Originated Call ................................................................98
12.1.1. RRC Connection Must Exist.......................................................................98
12.1.2. Initial NAS Message...................................................................................99
12.1.3. Further NAS Messages............................................................................100
12.1.4. Access Stratum Signalling Required ........................................................101
12.1.5. Mobile Originated Call..............................................................................102
12.2.
Example: Mobile Terminated Call.............................................................103
12.2.1. Paging .....................................................................................................103
12.2.2. RRC Connection Must Exist.....................................................................104
12.2.3. Initial NAS Message.................................................................................105
12.2.4. Mobile Terminated Call ............................................................................106
13.
Radio Access Bearer Set-up............................................................................107
13.1.
RAB Setup Procedure..............................................................................108
13.1.1. RAB Assignment Request .......................................................................108
13.1.2. Admission Control....................................................................................109
13.1.3. AAL2 Data Bearer at Iu-CS......................................................................110
13.1.4. DCH Reconfiguration (1)..........................................................................111
13.1.5. DCH Reconfiguration (2)..........................................................................112
13.1.6. AAL2 Data Bearer at Iub..........................................................................113
13.1.7. Data Bearer Synchronisation ...................................................................113
13.1.8. New Radio Link Configuration..................................................................114
13.1.9. RB Setup Message..................................................................................115
13.1.10. RB Setup Completion ............................................................................116
13.2.
Exercise ...................................................................................................116
14.
Soft Handover Signalling .................................................................................117
14.1.
Example: Branch Addition ........................................................................118
14.1.1. Measurement Report ...............................................................................118
14.1.2. Handover Control.....................................................................................118
14.1.3. Radio Link Setup Request - Iur ................................................................119
14.1.4. Admission Control....................................................................................120
14.1.5. Radio Link Setup Request - Iub ...............................................................120
14.1.6. Radio Link Setup Response - Iub.............................................................121
14.1.7. Radio Link Setup Response - Iur .............................................................122
14.1.8. AAL2 Data Bearer Setup .........................................................................122
14.1.9. Active Set Update Message.....................................................................123
14.1.10. Active Set Update Complete ..................................................................124
14.2.
Radio Bearer vs. Radio Link.....................................................................125
14.2.1. Radio Bearer vs. Radio Link ....................................................................125
14.2.2. Radio Bearer ...........................................................................................126
14.2.3. Radio Link................................................................................................127
14.2.4. Soft Handover..........................................................................................128
15.
RAN Protocol Exercise ....................................................................................129

Table of Figures:
Figure 1...........................................................................................................................9
Figure 2.........................................................................................................................10
Figure 3.........................................................................................................................11
Figure 4.........................................................................................................................12
Figure 5.........................................................................................................................13
Figure 6.........................................................................................................................14
Figure 7.........................................................................................................................15
Figure 8.........................................................................................................................16
Figure 9.........................................................................................................................17
Figure 10.......................................................................................................................18
Figure 11.......................................................................................................................19
Figure 12.......................................................................................................................20
Figure 13.......................................................................................................................21
Figure 14.......................................................................................................................22
Figure 15.......................................................................................................................23
Figure 16.......................................................................................................................24
Figure 17.......................................................................................................................25
Figure 18.......................................................................................................................26
Figure 19.......................................................................................................................27
Figure 20.......................................................................................................................28
Figure 21.......................................................................................................................29
Figure 22.......................................................................................................................30
Figure 23.......................................................................................................................31
Figure 24.......................................................................................................................32
Figure 25.......................................................................................................................33
Figure 26.......................................................................................................................34
Figure 27.......................................................................................................................35
Figure 28.......................................................................................................................36
Figure 29.......................................................................................................................37
Figure 30.......................................................................................................................37
Figure 31.......................................................................................................................38
Figure 32.......................................................................................................................39
Figure 33.......................................................................................................................40
Figure 34.......................................................................................................................41
Figure 35.......................................................................................................................42
Figure 36.......................................................................................................................43
Figure 37.......................................................................................................................44
Figure 38.......................................................................................................................45
Figure 39.......................................................................................................................46
Figure 40.......................................................................................................................47
Figure 41.......................................................................................................................48
Figure 42.......................................................................................................................49
Figure 43.......................................................................................................................50
Figure 44.......................................................................................................................51
Figure 45.......................................................................................................................52
Figure 46.......................................................................................................................53
Figure 47.......................................................................................................................54
Figure 48.......................................................................................................................54

Figure 49.......................................................................................................................55
Figure 50.......................................................................................................................56
Figure 51.......................................................................................................................57
Figure 52.......................................................................................................................60
Figure 53.......................................................................................................................61
Figure 54.......................................................................................................................62
Figure 55.......................................................................................................................63
Figure 56.......................................................................................................................64
Figure 57.......................................................................................................................65
Figure 58.......................................................................................................................66
Figure 59.......................................................................................................................67
Figure 60.......................................................................................................................68
Figure 61.......................................................................................................................69
Figure 62.......................................................................................................................70
Figure 63.......................................................................................................................71
Figure 64.......................................................................................................................72
Figure 65.......................................................................................................................73
Figure 66.......................................................................................................................74
Figure 67.......................................................................................................................75
Figure 68.......................................................................................................................76
Figure 69.......................................................................................................................77
Figure 70.......................................................................................................................78
Figure 71.......................................................................................................................79
Figure 72.......................................................................................................................80
Figure 73.......................................................................................................................81
Figure 74.......................................................................................................................82
Figure 75.......................................................................................................................83
Figure 76.......................................................................................................................84
Figure 77.......................................................................................................................84
Figure 78.......................................................................................................................85
Figure 79.......................................................................................................................86
Figure 80.......................................................................................................................86
Figure 81.......................................................................................................................87
Figure 82.......................................................................................................................88
Figure 83.......................................................................................................................89
Figure 84.......................................................................................................................90
Figure 85.......................................................................................................................91
Figure 86.......................................................................................................................92
Figure 87.......................................................................................................................93
Figure 88.......................................................................................................................94
Figure 89.......................................................................................................................95
Figure 90.......................................................................................................................96
Figure 91.......................................................................................................................97
Figure 92.......................................................................................................................98
Figure 93.......................................................................................................................99
Figure 94.....................................................................................................................100
Figure 95.....................................................................................................................101
Figure 96.....................................................................................................................102
Figure 97.....................................................................................................................103
Figure 98.....................................................................................................................104

Figure 99.....................................................................................................................105
Figure 100...................................................................................................................106
Figure 101...................................................................................................................107
Figure 102...................................................................................................................108
Figure 103...................................................................................................................109
Figure 104...................................................................................................................110
Figure 105...................................................................................................................111
Figure 106...................................................................................................................112
Figure 107...................................................................................................................113
Figure 108...................................................................................................................114
Figure 109...................................................................................................................114
Figure 110...................................................................................................................115
Figure 111...................................................................................................................116
Figure 112...................................................................................................................116
Figure 113...................................................................................................................117
Figure 114...................................................................................................................118
Figure 115...................................................................................................................118
Figure 116...................................................................................................................119
Figure 117...................................................................................................................120
Figure 118...................................................................................................................120
Figure 119...................................................................................................................121
Figure 120...................................................................................................................122
Figure 121...................................................................................................................122
Figure 122...................................................................................................................123
Figure 123...................................................................................................................124
Figure 124...................................................................................................................125
Figure 125...................................................................................................................126
Figure 126...................................................................................................................127
Figure 127...................................................................................................................128
Figure 128...................................................................................................................129

1. RAN Interfaces & Protocols

This module includes
Mandatory part (pages 2-8)
Optional part 1 (pages 9-10)
Optional part 2 (pages 11-14)
Objectives
Compare the user plane and control plane in radio network layer and transport network
layer and describe the generic use of each of these planes.
List the involved protocols building the Iub, Iur, Iu-PS, Iu-CS and Iu-BC.
Describe the role of each protocol in a single sentence.
Describe the interfaces and protocols used for the transfer of operation and
maintenance data in radio access networks.
Learning time
Mandatory part 3-4 hours
Optional parts 1-2 hours
Figure 1
The weight of this module in the assessment is 15%.

10
2. UTRAN Interfaces
Figure 2
In the UMTS Terrestrial Radio Access Network (UTRAN), there are two internal
interfaces:
Iub interface between the RNC and the base transceiver station
Iur interface between two RNC nodes involved in an inter-RNC soft handover or
inter-RNC relocation.
Between the radio access network and the core network, there are two interfaces:
Iu-CS interface between RNC and MGW
Iu-PS interface between RNC and SGSN
In addition, there are two interfaces to servicespecific platforms:
Iu-BC interface between RNC and CBC
Iu-PC interface between RNC and SAS
Between the radio access network and the user equipment, there is the Uu interface.

11
2.1. General Protocol Model

2.1.1. Control Plane and User Plane
Figure 3
UTRAN terrestrial interfaces are vertically divided into a control plane and a user plane.
In the control plane, signalling messages are carried over the interface using a specific
application protocol.
In the user plane, different kinds of user data is carried over the interface for instance
encoded speech, IP traffic, or various kinds of multimedia information.
Also, higher layer signalling traffic for instance RRC messages between the RNC and
user equipment are carried in the user plane.

12
2.1.2. Radio vs. Transport Network Layer
Figure 4
UTRAN interfaces are horizontally divided into a radio network layer and a transport
network layer.
The radio network layer contains the application protocols in the control plane and data
streams carrying user data in the user plane.
The transport network layer offers various signalling bearers and data bearers for
reliable transport of the radio network layer information.

13
2.1.3. Bearer Concept
Figure 5
In 3G terms, a bearer is a transport entity with specified capacity and Quality of Service
(QoS) attributes.
As you can see from the figure on the right, many kinds of bearers have been specified,
such as radio access bearers and radio bearers - note that these are two different types
of bearers.
The UTRAN transport network layer is concerned with bearer management at the lowest
level.

14
2.1.4. ATM for Transport
Figure 6
Asynchronous Transfer Mode (ATM) forms the basis of the transport network layer and
is used for all transport - both user data and signalling - over all UTRAN terrestrial
interfaces.

15
2.1.5. ATM / AAL5
Figure 7
Signalling messages are carried over ATM using ATM Adaptation Layer 5 (AAL5), which
in practice means chopping up a message and carrying it within successive ATM cells.

16
2.1.6. ATM / AAL2
Figure 8
Information in the user plane is also carried over ATM, but employing ATM Adaptation
Layer 2 (AAL2).
AAL2 offers multiplexing of bytes of data from different sources (or to different
destinations) within a single ATM
cell.In this way the available transport network resources - in other words ATM links - are
more efficiently utilized (in the case of small packets such as voice packets), than when
using AAL5 transport. At the same time, AAL2 guarantees low delay, which is important
for real-time services.

17
2.1.7. AAL2 Data Mapping
Figure 9
AAL2 offers the possibility of packing variable-sized AAL2 protocol data units from different data
sources into a single ATM cell, as shown in the figure.
Following the ATM header, the one-byte start field indicates where the next AAL2 PDU starts.
This is necessary, since an AAL2 PDU may occupy two successive ATM cells. The start of the
next AAL2 PDU can be calculated from the PDU length information contained in the header of the
previous PDU. If there is no more AAL2 data, the ATM cell is filled up with padding bytes.

18
2.1.8. AAL5 Data Mapping
Figure 10
In the case of AAL5, the user data is packed into ATM cells as shown in the figure.
First, an 8-byte trailer is appended to the user data in the AAL5 protocol data unit, which
can have a length of up to 65535 bytes. Then the PDU is split into 48-byte segments and
packed into ATM cells. The last ATM cell contains the AAL5 trailer and is filled up with
padding bytes. The next ATM cell contains the first segment of the next AAL5 PDU, and
so forth.

2.1.9. AAL5 vs. AAL2
Figure 11
In summary, the ATM adaptation protocols AAL5 and AAL2 are compared in the figure
on the right.
19

20
2.1.10. Transport Network Control Plane
Figure 12
The transport layer network contains its own control plane, which carries an application
protocol denoted Q.2630.1. The main task of this protocol - more generally referred to as
the Access Link Control Application Part (ALCAP) - is the dynamic management of the
data bearers, in other words dynamic management of the AAL2 connections carrying the
data streams in the user plane. By contrast, the signalling bearers in the control plane,
as well as in the transport network control plane, are always set up by Operation &
Maintenance (O&M) actions.

21
2.1.11. AAL5 in User Plane
Figure 13
In the Iu-PS interface, data bearers are based on AAL5 transport.

The reason for selecting AAL5 instead of AAL2 is that AAL5 is more efficient than AAL2
when carrying data traffic consisting of long data packets.
The AAL5 bearers in the user plane are always set up by O&M actions, in the same way
as the signalling bearers based on AAL5. Consequently, the transport network control
plane is not needed in this case.

22
2.1.12. Convergence Protocols
Figure 14
Finally, convergence protocols adapt the application protocols in the control plane and
ALCAP in the transport network control plane to the lower protocol layers, AAL5 and
ATM.
Convergence protocols are described in more detail in the topic Signalling Transport".
At the Iur and Iu interfaces, the application protocols in the control plane are carried over
SS7 protocols over convergence protocols over ATM.

2.2. Exercise
Figure 15
23

24
3. Iub Interface
Figure 16
The logical interface between an RNC and a base transceiver station, which is Node B in
3G terminology, is called Iub.
The control plane is concerned with Node B Application Part (NBAP) signalling between
the RNC and base transceiver station.
In the user plane, information carried in the various transport channels is packed into the
payload of Frame Protocol (FP) frames.
Both the user plane data and the signalling is carried over ATM connections..

25
3.1. Interface Protocol Structure

3.1.1. NBAP Signalling Protocol
Figure 17
The application protocol Node B Application Part in the control plane is used for
signalling between the RNC and the base transceiver station. This protocol can be
divided into common NBAP procedures and dedicated NBAP procedures.
Common NBAP procedures include various functions that are in general not related to a
specific mobile user.
In contrast, dedicated NBAP procedures are concerned with the signalling related to a
specific mobile user.

26
3.1.2. Common NBAP Procedures
Figure 18
Common NBAP procedures include cell configuration, traffic management of common

transport channels, initialization and reporting of cell or base station specific
measurements, fault management, and setting up the first radio link for a specific UE. A
traffic termination point must first be assigned at the base station for this user before
further user-related signalling using dedicated NBAP procedures is possible.
For handling common NBAP procedures, only one signalling connection per BTS is
needed at the Iub interface.

27
3.1.3. Dedicated NBAP Procedures
Figure 19
After the first radio link to a certain user has been set up, all subsequent NBAP signalling
related to this user takes place using NBAP dedicated procedures.
Such signalling includes the addition, release and reconfiguration of radio links for this
user, the handling of dedicated transport channels, initialisation and reporting of radio
link specific measurements, and radio link fault management.

28
3.1.4. Frame Protocol (FP)
Figure 20
FP is employed for the transfer of the data streams on top of AAL2.

The FP header contains control information for transport channel synchronisation and
outer loop power control.
Furthermore, in the uplink direction, signal quality information for macrodiversity
combining is sent together with the signal replicas received via the various radio
channels. Based on this information, the best signal can be selected by the Serving RNC
for further transmission towards the core network.

29
3.1.5. User Plane Transport Channels
Figure 21
The user data carried in various transport channels is packed into the payload of Frame
Protocol frames and carried over AAL2 connections in the user plane.

30
3.1.6. NBAP over AAL5
Figure 22
In the control plane, the Node B Application Part signalling protocol is carried on top of
the Signalling ATM Adaptation Layer (SAAL) protocol stack which consist of ATM
Adaptation Layer 5 (AAL5), the Service Specific Connection Oriented Protocol (SSCOP),
and the Service Specific Coordination Function for the User-Network Interface (SSCFUNI).

3.2. Exercise
Figure 23
31

32
4. Iur Interface
Figure 24
The logical interface between two RNC nodes is called Iur. This interface is needed
during inter-RNC soft handover.
In the control plane, the application protocol Radio Network Subsystem Application Part
(RNSAP) carries signalling information between the RNC nodes.
The protocol structure in the user plane is similar to the user plane protocol structure of
the Iub interface.

33

4.1.1. RNSAP Signalling Protocol
Figure 25
The application protocol at the Iur interface, the Radio Network Subsystem Application
Part (RNSAP), takes care of setting up and releasing transport connections between
RNC nodes.
This is necessary for implementing inter-RNC soft handovers, in other words handovers
involving base transceiver stations that are connected to different RNC nodes.

34
4.1.2. Serving RNC vs. Drift RNC
Figure 26
The Serving RNC (SRNC) manages the radio connections between the radio access
network and the user equipment. The SRNC also handles the macrodiversity combining
in the case of a soft handover.
The connection to the core network over the Iu interface is always via the SRNC.
The Drift RNC (DRNC) does not process Frame Protocol frames in any way, but instead
relays the frames transparently to the destination - the SRNC or the user equipment.

35
4.1.3. Interface Protocol Structure
Figure 27
The protocol structure of the Iur interface is practically the same as that of the Iub
interface. See the topic Iub Interface".
However, contrary to the Iub interface, the Iur interface is based on SS7 protocols. There
are also some differences in the convergence protocols. See the topic"Signalling
Transport".

4.2. Exercise
Figure 28
5. Iu-CS/PS Interfaces
36

37
Figure 29
The interface between the RNC and circuit-switched core network is called Iu-CS. The
interface between the RNC and packed-switched core network is called Iu-PS.
In the control plane, the application protocol RANAP (Radio Access Network Application
Part) carries signalling information over the Iu-CS and Iu-PS interfaces.
The Iu-CS user plane is based on AAL2 connections, whereas the Iu-PS user plane is
based on IP-over-ATM (IPoA) and AAL5 transport.

5.1.1. RANAP Signalling Protocol
Figure 30
The main task of RANAP is to set up and release dedicated connections, with defined
capacity and QoS performance, between the user equipment and the core network.
Such a dedicated connection is called Radio Access Bearer (RAB).
RANAP signalling is also required during an intersystem or intrasystem handover if the
RNS Relocation procedure is involved in this handover. RNS Relocation means that a
different RNC becomes the Serving RNC.

38
5.1.2. RANAP (cont.)
Figure 31
RANAP also carries the signalling between the core network and RNC needed for
implementing location services, for downloading security keys to the radio access
network, and for paging mobile users.
Finally, like the signalling protocol RRC between UE and RNC, RANAP carries higherlayer - or Non Access Stratum (NAS) - signalling information for various Call Control
(CC), Mobility Management (MM) and Session Management (SM) tasks. This signalling
information is carried transparently via the RNC and thus has no significance for the
RNC.

39
5.1.3. Iu-CS and Iu-PS Control Plane
Figure 32
The protocol structure of the control plane is similar to the control plane protocol
structure of the Iur interface.
The signalling bearers are based on the Signalling ATM Adaptation Layer (SAAL) which
uses AAL5 transport.

40
5.1.4. Iu-CS User Plane
Figure 33
Like the Iub and Iur user planes, the Iu-CS user plane is based on AAL2 connections
that are set up by means of the ALCAP protocol.
On top of AAL2, the user data is carried within Iu User Plane Protocol (Iu-UP) frames.
In Support Mode, the Iu-UP frame size can change during the connection. This feature is
useful for transport of AMR encoded speech.
In Transparent Mode, Iu-UP does not offer any services.

5.1.5. Iu-PS User Plane
Figure 34
All user plane traffic at the Iu-PS interface is multiplexed on to one or several AAL5
permanent virtual circuits.
The permanent AAL5 connections are set up by Operation & Maintenance actions; so
the transport network control plane is not required here.
Transport in the transport network layer is based on IP-over-ATM.
The user data - usually in form of IP packets - is carried in the GTP-U payload without
using any Iu-UP services.
41

5.1.6. IP over IP
Figure 35
It should be noted that the Internet Protocol (IP) is located in two different layers in the
Iu-PS user plane protocol stack.
The Iu-PS user data typically consists of IP packets that are packed into the GTP-U
payload.
In addition, the transport network layer uses IP-over-ATM technology for carrying the
GTP-U protocol data units over the Iu-PS interface.
42

43
5.1.7. GPRS Tunneling Protocol (GTP)
Figure 36
At the Iu-PS interface, a connection-oriented data bearer is obtained by forming a

"tunnel" between the RNC and SGSN. This tunnel is, in fact, an extension of a similar
tunnel in the packet-switched core network between SGSN and GGSN.
The tunnel identifier required for setting up a GTP-U tunnel is provided in a RANAP
message during Radio Access Bearer (RAB) establishment.
In order to fulfill certain QoS requirements, separate GTP-U tunnels are established for
non-real-time (NRT) and real-time (RT) traffic.

44
5.1.8. Convergence Protocols
Figure 37
The convergence protocols at the Iu-PS interface are the same as those used at the Iur
interface.
The convergence protocols at the Iu-CS interface are also the same.
Convergence protocols are explained in more detail in the topic "Signalling Transport".

5.1.9. 3GPP Release 4 Architecture
Figure 38
In 3GPP Release 4, as far as the circuit-switched core network is concerned, Mobile
Switching Center (MSC) network elements are replaced with Media Gateway (MGW)
and MSC Server nodes.
The user plane data originates or terminates in the MGW.
However, the RANAP signalling in the control plane traverses the MGW and originates
or terminates in the MSC Server.
On the other hand, ALCAP signalling originates or terminates in the MGW.
45

5.2. Exercise
Figure 39
46

47
6. Iu-BC Interface
Figure 40
The interface between the RNC and a Cell Broadcast Center (CBC) is called Iu-BC. This
interface is required for implementing the Service Area Broadcast (SAB) service.
This service corresponds to the SMS Cell Broadcast Service (CBS) defined for GSM.
SAB is a service that enables a provider of information to submit short messages for
broadcasting within a specified area of the mobile network. These messages could be
used for notification of, for example, PLMN news, emergencies, traffic reports, road
accidents, delayed trains, weather reports, theatre programmes, telephone numbers or
tariffs.


6.1.1. Iu-BC Interface Protocol Structure
Figure 41
The protocol stack at the Iu-BC interface is shown in the figure on the right.
The Service Area Broadcast Protocol (SABP) carries both the user data and the
associated signalling over the Iu-BC interface.
Consequently, there is no clear separation between control plane and user plane.
48

6.1.2. SABP
Figure 42
The protocol SABP performs the following tasks:

Distribution of messages to the correct service areas and stopping the
broadcasting of specific messages if requested
Sending of the load status of the service area(s) to the CBC when requested
Ending the broadcasting in one or more service areas, as ordered by the CBC
Reporting of errors to the CBC.
49

50
6.1.3. TCP
Figure 43
At the Iu-BC interface, the Transmission Control Protocol (TCP) is employed instead of
the User Datagram Protocol (UDP) used at the Iu-PS interface.
TCP is a connection-oriented protocol that offers flow control - which means temporarily
suspending transmission in case of congestion - and error control, which in this case is
retransmission of erroneous packets.

6.2. SAB Service Animation

6.2.1. RNC can serve up to four CBCs
Figure 44
The RNC can be connected to a maximum of four cell broadcast centers, for example
situated in the four core networks of four different operators.
51

52
6.2.2. Message broadcasting
Figure 45
The broadcast message is sent from the CBC over the Iu-BC interface to the RNC using
the SABP protocol.
In the RNC, the message is delivered to the correct Broadcast/Multicast Control Protocol
(BMC) entity, where it is stored.
This BMC entity corresponds to a specific service area in which the message will be
broadcast.
The message is broadcast within the service area using the BMC protocol.

6.3. Exercise
Figure 46
7. Iu-PC Interface
53

54
Figure 47
In the 3GPP specifications, the interface between the RNC and the standalone SMLC
(known as the SAS) is called Iu-PC. The SAS is a separate "calculator" for location
estimates and determining the assistance data for GPS. It is needed for other methods,
even if the RNC integrated SMLC is used for the Cell ID and RTT based positioning.
The Iu-PC interface is used to send the position requests to the SAS and to send
responses back to the RNC. The response may include the calculated position of the UE
(if network based A-GPS is used) or assistance data for UE, which is sent UE to
enhance UEs GPS performance.
The ADIF is a proprietary interface supported by the RNC for the same purpose as the
Iu-PC.
7.1 Interface Protocol Structure

7.1.1. Iu-PC Interface Protocol Structure
Figure 48

55
The Positioning Calculation Application Part (PCAP) is used between the Radio Network
Controller (RNC) and the Stand-alone (A-GPS) SMLC (SAS). The PCAP defines the IuPC interface and related signalling procedures.
Alternatively, the RNC may interact with the proprietary A-GPS data server via a vendorspecific binary protocol over the TCP/IP interface.
These two interfaces and protocols differ in the message structure but signalling
procedures are very similar.
7.1.2. Positioning Calculation
Figure 49
In the network based A-GPS positioing, the RNC first collects assistance data from SAS
and sends it to UE to enhance GPS performance. The UE sends measurement data to
the RNC, which forwards the data to the SAS. The SAS converts this measurement data
into position estimate.
The RNC sends the "position calculation request" to the SAS. When the SAS receives
this message, it calculates the UE position based on the provided measurement data.
If the SAS is able to calculate the position estimate, it responds with a "position
calculation response" message.

56
7.1.3. Information Exchange
Figure 50
The network may also retrieve the A-GPS assistance data from the SAS, for instance to
allow the UE to calculate the position.
The procedure is initiated with an "information exchange initiation request" message sent
from the RNC to the SAS.
The SAS then collects the requested information according to the parameters given in
the request and sends the "information exchange initiation response" back to the RNC.

7.2 Exercise
Figure 51
57

58
8. Uu Interface
Figure 52
The logical interface between the base station and the user equipment - in other words
the air interface or radio interface - is called Uu in the 3GPP specifications.
The physical protocol layer of this interface is based on WCDMA technology and
physical channels that are multiplexed in the so-called code division domain.
Let us next examine the different types of channels and protocols that are used over the
Uu interface.

59

8.1.1. Introduction
Figure 53
Transport of user data and signalling traffic over the Uu interface is based on three kinds
of channels: physical, transport, and logical channels.
The Medium Access Control protocol plays a central role in WCDMA, since it takes care
of the mapping between logical and transport channels. Note the location of the MAC
protocol in the radio access network protocol stack figure.
Let us briefly examine the WCDMA channels before moving on to the various protocols
used over the Uu interface.

60
8.1.2. Physical Channels
Figure 52
Physical channels carry information over the WCDMA air interface between the user
equipment and the base station.
Only the physical channels shown on the right are relevant from the RNC point of view,
since they carry or support transport channels which in turn carry higher-layer user and
control data.
Some additional physical channels not shown are used for transporting
synchronization signals, pilot signals, paging indicators, acknowledgements, and so
forth, over the air interface.

61
8.1.3. Transport Channels
Figure 53
The concept of transport channels is central to WCDMA. A transport channel defines

how the higher-layer data is carried over the air interface. For instance, the higher-layer
data can be split up into several bit streams that are carried in parallel over the transport
channel.
As shown on the right, there are five kinds of transport channels available for carrying
user and control data between the user equipment and the RNC or base station.

8.1.4. New Channels for HSDPA
Figure 54
The introduction of High-Speed Downlink Packet Access (HSDPA) requires three new
physical channels and one additional transport channel.
The High-Speed Downlink Shared Channel carries the user data between the base
station and the user equipment.
62

63
8.1.5. Logical Channels
Figure 55
Logical channels carry information over the Uu interface between the Serving RNC and
one or more user terminals (depending on the type of channel).
Logical channels are divided into control channels that carry various kinds of control
information, and traffic channels that carry higher-layer user data, such as voice or IP
traffic.

8.1.6. Mapping between Logical, Transport and Physical Channels
Figure 56
The figure on the right shows the mapping of logical channels into transport channels,
and the mapping of transport channels into physical channels, both in the uplink and
downlink directions.
64

8.1.7. Mapping of User Data
Figure 57
Transport of higher-layer user data over the Uu interface is based on the following
channels:
DTCH - DCH - DPDCH (uplink and downlink)
DTCH - RACH - PRACH (uplink, small amounts of data)
DTCH or CTCH FACH SCCPCH (downlink, small amounts of data)
DTCH - HS-DSCH - HS-PDSCH (high speed downlink packet data).
65

8.1.8. MAC Protocol
Figure 58
The main task of the Medium Access Control (MAC) protocol is to handle the mapping
between logical channels and transport channels, and for selecting an appropriate
transport format for each transport channel.
Note the location of the MAC protocol: it runs both in the Serving RNC and in the base
station.
66

67
8.1.9. MAC Layer Logical Entities
Figure 59
The MAC layer consists of four logical entities:

The MAC-b entity handles the Broadcast Channel (BCH). The MAC-c/sh entity handles
the Paging Channel (PCH), Forward Access Channel (FACH), and Random Access
Channel (RACH). The MAC-d entity is responsible for handling dedicated channels
(DCH) allocated to specific mobile terminals. Finally, the MAC-hs entity handles the
High-Speed Downlink Shared Channel (HS-DSCH), used in the case of HSDPA.

68
8.1.10. RLC Protocol
Figure 60
The Radio Link Control (RLC) protocol provides segmentation, concatenation, and
retransmission services for higher-layer user and control traffic
.The RLC protocol operates in one of three modes: transparent mode, where no
protocol overhead is added to the higher-layer data, unacknowledged mode, which
offers segmentation, concatenation and in-sequence delivery of higher-layer data, and
acknowledged mode, which takes care of error correction by retransmitting erroneous
frames over the Uu interface..

8.1.11. RRC Signalling Protocol
Figure 61
Let us next examine the protocols located on top of the RLC protocol.
In the control plane, the signalling protocol Radio Resource Control or RRC carries
signalling information between the user equipment and the Serving RNC.
Note that RRC signalling messages are carried transparently via the base station and
the Drift RNC. Transport via the Drift RNC naturally takes place only in the case of an
inter-RNC soft handover.
69

70
8.1.12. RRC Signalling Protocol
Figure 62
The Radio Resource Control protocol basically offers two functions:

1) RRC participates in various radio bearer management tasks in coordination with the
NBAP protocol operating over the Iub interface.
2) RRC also carries higher-layer signalling information for various call control, mobility
management and session management tasks. This so-called Non Access Stratum (NAS)
signalling information is carried transparently between the user equipment and the core
network using the RRC and RANAP protocols.

8.1.13. User Plane Transport
Figure 63
In the user plane, the user data for instance coded speech or IP traffic is carried
within a transport channel which could be a bidirectional Dedicated Channel, a
downlink Forward Access Channel, or an uplink Random Access Channel.
The Forward Access Channel and Random Access Channel can be used for carrying
small amounts of data in the downlink and uplink directions, respectively. In this case,
soft handover cannot be used.
71

72
8.1.14. User Plane Protocols: PDCP
Figure 64
The Packet Data Convergence Protocol removes the redundant overhead in IP data
streams in order to make IP transport over the air interface more efficient. In this way the
capacity over the air interface can be increased.
PDCP supports various algorithms for compressing TCP, RTP, UDP and IP header
information at the transmitting entity, and decompresses the information at the receiving
entity.

73
8.1.15. User Plane Protocols: BMC
Figure 65
The Broadcast and Multicast Control protocol takes care of the storage of Cell Broadcast
messages in the RNC, as well as the scheduling, transport and delivery of the messages
to mobile users.

74
9. Signalling Transport
Figure 66
Signalling in the PSTN and the CS core of mobile networks is based on a highperformance and reliable common channel signalling system called SS7.
The SS7 protocol stack consists of MTP that offers reliable signalling transport between
exchanges in circuit switched networks, SCCP that also offers signalling connections to
network nodes other than exchanges, and the application protocol that contains the
actual signalling messages.
It is also possible to use IP-based transport protocols instead of MTP - or use them
together with MTP.

75
9.1. Signalling Transport at the Iub Interface

9.1.1. Iub Protocol Structure (1)
Figure 67
The control plane protocol stack at the Iub interface does not contain any SS7-related
parts. Let us still look at the protocols between the ATM layer and the signalling
protocols NBAP and ALCAP, since these protocols are also partly used at the other RAN
interfaces:
The Service Specific Connection Oriented Protocol (SSCOP) guarantees error-free and
in-sequence delivery of signalling messages.
AAL5 alone is not capable of offering error-free and in-sequence message delivery.

76
9.1.2. Iub Protocol Structure (2)
Figure 68
At the User-Network Interface (UNI), the Service Specific Coordination Function (SSCF)
has very little functionality.
In the transport network control plane, ALCAP is used for managing AAL2 connections
in the user plane.
Q.2150.2 signalling transport converter (STC) is needed to carry ALCAP on SSCOP.
The main task of the protocol Q.2150.2 is to re-establish a connection if SSCOP has
released the connection.

9.2. Broadband SS7 Protocol Structure

9.2.1. Iur Protocol Structure (1)
Figure 69
Like the Iub interface, the control plane of the Iur interface is based on AAL5 and
SSCOP. However, unlike the Iub interface, the Iur interface makes use of the SS7
protocol SCCP. For this reason, the signalling protocol structure is referred to as
broadband SS7 - broadband since ATM is used at the lower layers.
The SCCP protocol offers direct signalling connections for each active UE. In other
words, SCCP connections are used for differentiating the signalling transactions
intended for different subscribers.
77

78
Figure 70
The Service Specific Coordination Function (SSCF) at the Network Node Interface (NNI)
allows an ATM link to be seamlessly incorporated into an existing SS7 stack, employing
MTP3b as its network layer. The broadband version of Message Transfer Part Layer 3
(MTP3b) is used for transporting the SCCP packets over several parallel signalling links.
If one of the signalling links fails, the MTP3b protocol directs the traffic to the remaining
links.
Q.2150.1 AAL2 signalling transport converter (STC) is needed to carry ALCAP on
MTP3b. Q.2150.1 offers a similar functionality to the protocol Q.2150.2 which is used at
the Iub interface.

79
Figure 71
It is possible to replace the conventional convergence protocol stack between AAL5 and
SCCP with a similar protocol stack based on IP over ATM transport.
SCTP is a new alternative to the unreliable UDP and the reliable but slow TCP protocol.
SCTP is described in IETF RFC 3286. M3UA supports the transport of SCCP messages
over IP using the services of SCTP. M3UA is described in RFC 3332.

80
9.2.4. Iu Protocol Structure
Figure 72
The convergence protocol structure at the Iu-CS interface is exactly the same as that of
the Iur interface.
At the Iu-PS interface, the convergence protocol structure is also the same. However,
remember that the transport network control plane is not used. Naturally, the IP-based
transport alternative is available at this packet-oriented interface.

9.3. Exercise
Figure 73
81

82
10. O&M and Supporting Interfaces
Figure 74
The NWI3 network management interface connects Nokia NetAct (network and service
management system) to an RNC and, via a mediator implemented in the RNC, to a BTS.
The ATM Cross-Connect (AXC) at the BTS is managed directly from Nokia NetAct.
Instead of the network management interface, the telecom related radio network
connection and performance management for a base station is handled with the Iub
NBAP interface, which is not a network management interface.

83
Figure 75
NWI3 is a Nokia Proprietary interface that connects Network Management Systems with
mediators - such as NEMU in RNC or network elements with integrated mediation
function - such as ATM Cross Connects.
The network management interface for network elements in WCDMA RAN contain
functionality for performance, configuration, fault, hardware, and software management.
Configuration management includes management of configurable parameters and
network topology.

84
Figure 76
The NWI3 network management interface between the RNC and Nokia NetAct is based
on TCP/IP communication protocols.
The RNC provides a LAN interface (Ethernet) or IP-over-ATM (IPoA) connection to
Nokia NetAct. The application level communication mechanism is based on Common
Object Request Broker Architecture - or CORBA.
Figure 77

85
CORBA is an architecture and specification for creating, distributing, and managing

distributed program objects in a network.
The essential concept in CORBA is the Object Request Broker - or ORB - that allows the
usage of distributed objects using the General Inter-ORB Protocol (GIOP) and, for the
Internet, its Internet Inter-ORB Protocol (IIOP).
Figure 78
The CORBA based NetAct interface is mediated in the RNC to the BTS O&M protocol.
The network management interface for the BTS is a TCP/IP connection. The O&M
messages to the BTS are passed via the IP router in the AXC.
NetAct offers a means for the BTS software handling, fault management, reset from the
GUI, BTS connection establishment indication and BTS hardware handling.

10.2. Exercise
Figure 79
11. RRC Connection Establishment
Figure 80
86

87
The purpose of the RRC connection establishment procedure is to set up an RRC

connection for various kinds of signalling between the RNC and a specific UE.
Not more than one RRC connection at a time can be established between the UE and
the RNC.
An RRC connection is always initiated by the UE, and the release of the connection is
always initiated from the network side.
An important task during RRC connection establishment is to create a dedicated control
channel (DCCH) over which the subsequent signalling can be transported.
11.1. RRC Connection Establishment Procedure

11.1.1. RRC connection is initiated by UE
Figure 81
The establishment of an RRC connection is always initiated by the UE.

This is obviously true for mobile originated transactions.
This is also true for mobile terminated transactions - for instance an incoming call. In this
case the network informs the UE about the incoming call by means of paging - via a
common paging channel - after which the UE initiates the RRC connection establishment
procedure as described in the following paragraphs.

11.1.2. RRC Connection Request
Figure 82
The UE leaves the idle mode and initiates establishment of an RRC connection by
sending the "RRC Connection Request" message over RACH to the RNC.
Random access signalling takes place in the lower protocol layers before the "RRC
Connection Request" message is received at the base station.
The "RRC Connection Request" message contains the initial UE identifier, the
establishment cause, and the initial UE capability.
88

89
11.1.3. Admission Control
Figure 83
After receiving the "RRC Connection Request" message, the RNC performs admission
control.
If the cell is not in an overload condition, the request to establish the RRC connection is
accepted. During admission control, the RNC allocates a Radio Network Temporary
Identity as well as radio resources for this connection.

11.1.4. Setting up a Dedicated Channel
Figure 84
If the "RRC Connection Request" message indicates that the RNC should allocate a
dedicated control channel (DCCH) to the UE, the NBAP message "Radio Link Setup
Request" is sent to the base transceiver station. This message includes important
information required for setting up the dedicated control channel.
90

91
11.1.5. Setting up a Dedicated Channel (2)
Figure 85
After the BTS has allocated the required radio resources, it can receive information over
the air interface related to this dedicated channel.
The BTS returns the NBAP message "Radio Link Setup Response", which includes
transport layer addressing information.

11.1.6. Setting up a Dedicated Channel (3)
Figure 86
Using the AAL2 binding identity provided by the BTS, the RNC establishes the AAL2
data bearer over the Iub interface using the ALCAP protocol.
After some additional signalling between the BTS and RNC in order to achieve perfect
synchronisation, the dedicated control channel is ready for use, which means that the
BTS is ready to transmit and receive information over the air interface.
92

93
11.1.7. RRC Connection Setup Message
Figure 87
After the dedicated control channel has been set up in the radio access network, an
"RRC Connection Setup" message is sent to the UE over the FACH. This message
includes among others, the following information: The initial UE identifier, the Radio
Network Temporary Identity, and the various parameters related to the dedicated control
channel that has been set up.
Now the UE is also ready to transmit and receive information over the dedicated control
channel.

94
11.1.8. RRC Connection Setup Complete
Figure 88
The BTS achieves uplink synchronisation and notifies the RNC with an NBAP "Radio
Link Restore Indication" message.
The user equipment acknowledges successful setup of the RRC connection by sending
an "RRC Connection Setup Complete" message over the recently established dedicated
control channel to the RNC.

95
11.1.9. Radio Bearer Management
Figure 89
The RRC connection establishment procedure automatically creates three optionally

four signalling radio bearers between the UE and the RNC. These bearers can later be
reconfigured or deleted.
RRC signalling is also used for creating and releasing radio bearers for the transport of
user data between the UE and the RNC.

11.2. Exercise
Figure 90
96

12. Non-Access Stratum Signalling
Figure 91
A Non Access Stratum (NAS) signalling connection could be requested by the user
terminal by itself - for example to initiate a certain service - or could be the result of
paging from the core network.
Both cases are described in the examples below.
97

98
12.1. Example: Mobile Originated Call

12.1.1. RRC Connection Must Exist
Figure 92
In this example, a mobile user wishes to call in other words set up a circuit switched
connection to another user located, for example, in another radio access network.
If the UE is in idle mode, an RRC connection must first be established. This is explained
in the topic "RRC Connection Establishment".

99
12.1.2. Initial NAS Message
Figure 93
The UE sends an RRC "Initial Direct Transfer" message to the RNC over the Dedicated
Control Channel (DCCH) established during RRC connection setup.
This RRC message carries the initial NAS message, in this case "Classmark Service
Request" indicating to the destination - the MSC - that the user wishes to place a call.
The initial NAS message is then carried without modification from the RNC to the MSC in
the RANAP "Initial UE Message".

100
12.1.3. Further NAS Messages
Figure 94
All subsequent Non Access Stratum messages are then carried between the MSC and
the UE, packed within RANAP and RRC "Direct Transfer" messages.

101
12.1.4. Access Stratum Signalling Required
Figure 95
However, during the setup of a mobile call, there are two signalling functions that involve
Access Stratum signalling.
One is related to ciphering control. Ciphering is employed between the UE and the RNC,
not between the UE and the MSC.
The other signalling transaction in which the radio access network is involved is the
establishment of the radio access bearer carrying the speech. This is described in the
topic "Radio Access Bearer Setup".

102
12.1.5. Mobile Originated Call
Figure 96
In summary, setting up a mobile call typically involves the signalling - at the originating
end - as shown in the figure.
The labelled boxes represent radio access network specific signalling functions.
If a mobile user answers an incoming call, the situation is slightly different. This is shown
in the second signalling example.

12.2. Example: Mobile Terminated Call

12.2.1. Paging
Figure 97
In the case of a mobile terminated call, the called user must be notified about the
incoming call. For this purpose, the MSC initiates the paging procedure.
The RNC broadcasts the RRC "Paging" message over the paging channel (PCH).
103

104
12.2.2. RRC Connection Must Exist
Figure 98
Before the UE can respond to the paging, an RRC connection must exist between the
UE and the RNC.
If the UE is in idle mode, the RRC connection must first be established. This is explained
in the topic "RRC Connection Establishment".

105
12.2.3. Initial NAS Message
Figure 99
The UE sends an RRC "Initial Direct Transfer" message to the RNC over the Dedicated
Control Channel (DCCH) established during RRC connection setup.
This RRC message carries the initial NAS message, in this case "Paging Response"
indicating to the destination - the MSC - that the user is responding to the paging
message.
The initial NAS message is then carried without modification from the RNC to the MSC in
the RANAP "Initial UE Message".

106
12.2.4. Mobile Terminated Call
Figure 100
The subsequent signalling is quite similar to that of a mobile-originated call.

In summary, setting up a mobile call typically involves the signalling - at the terminating
end - as shown in the figure.

107
13. Radio Access Bearer Set-up
Figure 101
The Radio Access Bearer (RAB) defines the transmission characteristics for the user
plane data. The RAB parameters describe the traffic class, symmetry properties and
transmission characteristics such as capacity and permissible delay. For circuit-switched
data, the RAB is usually established over a dedicated channel as in the "RAB Setup
Procedure" example below.
The RAB establishment is initiated by the core network. The RNC, after checking the
availability of air interface resources, maps the RAB parameters into the appropriate
transport format and physical channel characteristics.

108
13.1. RAB Setup Procedure

13.1.1. RAB Assignment Request
Figure 102
It is always the core network that initiates the establishment of a radio access bearer.
For this purpose, the MSC - or the SGSN in the case of a packet connection - sends a
RANAP "RAB Assignment Request" message to the RNC.
This message includes various radio access bearer parameters and transport layer
addressing information for establishing the Iu-CS data bearer.

109
Figure 103
After receiving the "RAB Assignment Request" message, the RNC performs admission
control to determine whether the request can be fulfilled or not.

110
13.1.3. AAL2 Data Bearer at Iu-CS
Figure 104
Using the AAL2 address provided by the MSC in the "RAB Assignment Request"
message, the RNC establishes the AAL2 data bearer over the Iu-CS interface using the
ALCAP protocol.
This step is not, of course, required if a packet-based radio access bearer is established
between the user equipment and the packet switched domain of the core network.

13.1.4. DCH Reconfiguration (1)
Figure 105
The RNC requests the base transceiver station to prepare reconfiguration of the
dedicated channel (DCH) that will carry the radio access bearer by sending an NBAP
"Radio Link Reconfiguration Prepare" message to the BTS.
This message contains important information for the BTS, so that it can allocate the
required transport resources over the air interface.
111

112
13.1.5. DCH Reconfiguration (2)
Figure 106
The base transceiver station allocates the transport resources and notifies the RNC that the
preparation is ready by sending an NBAP "Radio Link Reconfiguration Ready" message.
This message contains the selected downlink channelisation code and transport layer addressing
information.

113
13.1.6. AAL2 Data Bearer at Iub
Figure 107
Using the AAL2 address provided by the BTS in the "Radio Link Reconfiguration Ready"
message, the RNC establishes the AAL2 data bearer over the Iub interface using the
ALCAP protocol.
13.1.7. Data Bearer Synchronisation

114
Figure 108
In the case of a soft handover, after all the AAL2 data bearers between the base
transceiver stations and the serving RNC have been established as previously
explained, the base transceiver stations and the serving RNC must establish
synchronism for the downlink and uplink data bearers, respectively, by means of the
exchange of appropriate Frame Protocol frames.
13.1.8. New Radio Link Configuration
Figure 109
Returning to the case of one radio link in the active set - for the sake of simple illustration
- the RNC sends an NBAP "Radio Link Reconfiguration Commit" message to the BTS to
order it to switch to the new configuration for the radio link.

115
13.1.9. RB Setup Message
Figure 110
The RNC sends the RRC message "Radio Bearer Setup" to the user equipment over an
existing dedicated control channel (DCCH).
This message contains parameters related to the dedicated channel that has been set
up for carrying the radio access bearer.

116
13.1.10. RB Setup Completion
Figure 111
The user equipment returns the RRC message "Radio Bearer Setup Complete" to the
RNC over the dedicated control channel (DCCH).Finally, the RNC sends the RANAP
message "RAB Assignment Response" indicating to the MSC that radio access bearer
establishment was successful.
13.2. Exercise
Figure 112

117
14. Soft Handover Signalling
Figure 113
A basic WCDMA function is macro diversity. This means that a terminal can be
connected to the network through several radio links, also called "branches", during a
so-called soft handover.
In practice, the RNCs and base stations that are involved in the soft handover need to
be controlled in a centralised manner. The central control point is the "Serving RNC"
(SRNC). If other RNCs are involved in the soft handover, they are called "Drift RNCs"
(DRNC).
The number of radio links involved in a soft handover at any point in time is called
"Active Set". Radio links can be added or deleted depending on their signal quality.

118
14.1. Example: Branch Addition

14.1.1. Measurement Report
Figure 114
The user equipment continuously measures the downlink quality of signals received from
base transceiver stations located nearby.
When certain reporting criteria set by the RNC are met, the user equipment sends an
RRC "Measurement Report" message to the Serving RNC over the Dedicated Control
Channel.
14.1.2. Handover Control
Figure 115

119
The Handover Control entity in the Serving RNC analyses the measurement report and
decides to add a new radio link to the Active Set.
14.1.3. Radio Link Setup Request - Iur
Figure 116
The Serving RNC requests radio resources from the Drift RNC by sending an RNSAP
"Radio Link Setup Request" message.
The parameters of this message should be quite familiar after having studied the topics
"RRC Connection Establishment" and "Radio Access Bearer Setup".
If this is the first radio link via the Drift RNC for this UE, a new Iur signalling connection
must be established. This new Iur connection will be used for all further RNSAP
signalling related to this UE.

120
Figure 117
The Drift RNC performs admission control to determine whether or not the request can
be fulfilled.
14.1.5. Radio Link Setup Request - Iub
Figure 118

121
If the requested radio resources are available, the Drift RNC sends an NBAP "Radio Link
Setup Request" message to the base transceiver station.
The parameters of this message are shown in the figure.
14.1.6. Radio Link Setup Response - Iub
Figure 119
After the BTS has allocated the required radio resources, it can receive information over
the air interface related to this radio link.
The BTS returns the NBAP message "Radio Link Setup Response" - which also contains
transport layer addressing information - to the Drift RNC.

122
14.1.7. Radio Link Setup Response - Iur
Figure 120
The Drift RNC returns the RNSAP "Radio Link Setup Response" message to the Serving
RNC.
14.1.8. AAL2 Data Bearer Setup
Figure 121

123
Using the AAL2 address provided by the BTS and the Drift RNC, respectively, the Drift
RNC and Serving RNC establish the AAL2 data bearers over the Iub and Iur interfaces
using the ALCAP protocol.
After some additional signalling between the base transceiver station and the Serving
RNC in order to achieve synchronisation with respect to the other existing radio links, the
base transceiver station is ready to transmit information over the air interface.
14.1.9. Active Set Update Message
Figure 122
The Serving RNC has all the necessary information for sending the RRC "Active Set
Update" message to the user equipment over the existing Dedicated Control Channel.
Now the user equipment is also ready to receive information over the new radio link.

124
14.1.10. Active Set Update Complete
Figure 123
The user equipment acknowledges receipt of the information with the RRC "Active Set
Update Complete" message over the Dedicated Control Channel.

14.2. Radio Bearer vs. Radio Link

14.2.1. Radio Bearer vs. Radio Link
Figure 124
Radio bearers and radio links are not the same thing. Let us look at the difference
between a radio bearer and a radio link.
125

126
14.2.2. Radio Bearer
Figure 125
Radio bearers carry signalling or user data between the user equipment and the Serving
RNC.
A radio bearer is controlled by the Serving RNC responsible for managing the radio
access bearer with which the radio bearer is associated. Several radio bearers can be
established at the same time towards a certain user equipment.
There are two types of radio bearers: signalling radio bearers and radio bearers for
transport of user data.

14.2.3. Radio Link
Figure 126
Each radio bearer utilises one or several radio links for physical transport over the air
interface. In fact, there are also situations where a radio link can carry several radio
bearers. If several radio links are used, this is called macro diversity or soft handover.
127

128
14.2.4. Soft Handover
Figure 127
Soft handover means that at least two radio links are involved in the handover.
The radio links can exist via one base station, via several base stations belonging to the
same RNC, or via several base stations belonging to different RNCs - resulting in the
Serving RNC / Drift RNC concept.

15. RAN Protocol Exercise
Figure 128
129

Ran Interfaces Protocols PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ran Interfaces Protocols PDF

Hochgeladen von

Copyright:

Verfügbare Formate

RNC Architecture and functionality