TMO18024 - 9300 WCDMA UA06 UTRAN Description

9300 W-CDMA
UA06 UTRAN Solution

Description
TMO18024 D0 SG DENI1.0
Issue 1
STUDENT GUIDE
All Rights Reserved © Alcatel-Lucent 2009
All rights reserved © Alcatel-Lucent 2009

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

UA06 UTRAN Solution Description - Page 1
Empty page
Switch to notes view!
2 All Rights Reserved © Alcatel-Lucent 2009

9300 W-CDMA
UA06 UTRAN Solution Description
This page is left blank intentionally

Terms of Use and Legal Notices
1. Safetyto
Switch Warning
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders, including Alcatel-
Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent. All Rights Reserved © Alcatel-Lucent 2009
9300 W-CDMA
All rights reserved © Alcatel-Lucent 2009
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-
Lucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-
Lucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page

9300 W-CDMA

Course Outline
1. UTRAN
About introduction
This Course 4. Topic/Section is Positioned Here
1. UTRAN introduction
Course outline
Technical support Layer
2. UTRAN Transport 5. Topic/Section is Positioned Here
Course objectives
1. UTRAN Transport Layer
3. UTRAN Elements
1. Topic/Section is Positioned Here 6. Topic/Section is Positioned Here
Xxx 1. UTRAN Elements
Xxx
4. O&M Principles 7. Topic/Section is Positioned Here
Xxx
1. O&M Principles
5. Abbreviations
2. Topic/Section is Positioned Here
1. Abbreviations
3. Topic/Section is Positioned Here

9300 W-CDMA

Course Outline [cont.]

9300 W-CDMA

Course Objectives
Welcome to UA06 UTRAN Solution Description
Upon completion of this course, you should be able to:
functions and the architecture of a UTRAN network

UTRAN ATM transport layer
functional architecture and the configurations of the UTRAN equipment
UTRAN operation and maintenance principles.

9300 W-CDMA

Course Objectives [cont.]

9300 W-CDMA

About this Student Guide

Conventions
Switch used
to notes in this guide
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information

9300 W-CDMA
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

9300 W-CDMA

Self-assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title :
Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :
Language :
Switch to notes view! Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or

Instructional objectives globally globally Comments
yes) no)
1 To be able to XXX
2
9300 W-CDMA

Self-assessment of Objectives [cont.]
Yes (or No (or

Instructional objectives Globally globally Comments
yes) no)

9300 W-CDMA
Other comments
Thank you for your answers to this questionnaire


Do not delete this graphic elements in here:
1
Section 1
UTRAN introduction
UTRAN introduction
9300 W-CDMA
3JK11629AAAAWBZZA1
TMO18024 D0 SG DENI1.0 Edition 1
Welcome to this e-learning training about the Alcatel-Lucent UTRAN solution description.
You will find, next, the content and the objectives of this training.
At any time during the training, you can access the acronym list by clicking on the Attachments button at
the top right of the window.

3JK11629AAAAWBZZA Edition 1
Section 1 Pager 1
Objectives
Objectives:
To be able to describe the functions and the architecture of the UTRAN.
Content:
1.1 Situation
1.2 Functions
1.3 Functional Architecture
1.4 Protocols
1.5 Radio Interface Evolutions

UTRAN introduction
9300 W-CDMA UA06 UTRAN Solution Description
In this introduction, we are going to situate the UTRAN in a UMTS system. We will present the role and the
architecture of this radio access network as defined by the 3GPP standard.
Then we will go into details about the protocols used to convey information over the UTRAN interfaces
before looking at the evolutions of the radio interface.

Section 1 Pager 2
1 UTRAN Introduction
1.1 Situation

UTRAN introduction
What is the UTRAN and how is it located in a UMTS system?

Section 1 Pager 3
1.1 Situation
The Radio Access Network within Mobile Radio Systems

UTRAN introduction
In a mobile radio system such as GSM or UMTS, the objective of a radio access network is to convey
information over the air interface between a Mobile Phone and the Core Network.
The Core Network manages the communication and enables to connect to another phone of the Public
Switched Telephone Network (PSTN) via the Circuit Core Network, or to Internet via the Packet Core
Network. Access Network domain plus the Core Network domain constitute the Infrastructure domain.
The Mobile Phone is standardized as a User Equipment (UE). The UE is made up of a Mobile Equipment (ME),
and a UMTS Integrated Circuit Card (UICC) that stores the identity of the subscriber. This card contains a
UMTS SIM part to access the 3G network, but also a GSM SIM module that enables a 3G phone to access 2G
networks.
UTRAN stands for UMTS Terrestrial Radio Access Network.
As the access network of the UMTS, the UTRAN is responsible for the transfer of information over the air
interface between the Core Network and the User Equipment using terrestrial items of equipment.
All those domains have been defined precisely by the 3GPP standard in order to allow full compatibility
between manufacturers. Therefore, the UTRAN is interconnected with the Circuit-Switched domain and the
Packet-Switched domain respectively via the Iu-CS and Iu-PS interfaces.
The UTRAN is of course connected to the User Equipment via a radio interface named Uu interface. And
inside the User Equipment, the Cu interface defines the standardized interface between the Mobile
equipment and the UMTS SIM card.

Section 1 Pager 4
1.1 Situation
Role of the Core Network
Core Network Functions (Reminder)

Call establishment
Mobility Management (management of user location)
Management of subscriber databases
Providing support for services
Interconnection to external networks

UTRAN introduction
Before looking at the functions of the UTRAN, let’s remind of the functions of the Core Network.
The Core Network is independent from the access network. Indeed, the 2 separated domains (Circuit
Switched and Packet Switched), reuse the infrastructure of GSM and GPRS respectively.
Compared to the UTRAN whose main function is to convey data over the air interface between the Core
Network and the User Equipment, the Core Network can be considered as the brain of the whole system.
It is responsible for the initiation and the management of a call establishment.
It is in charge of the network mobility management by keeping in memory the location of the user in the
network as well as information about the subscriber.
The Core Network also provides support for services, manages and negotiates the Quality of Service
requested by the UE for those services.
Finally, it manages the interconnection between the local radio access of a UE and external networks.
To perform those functions, the Core Network is made up of different entities.
The Home Location Register (HLR) is the home register of the subscriber. Subscription information,
allowed services, authentication information and localization of the subscriber are at all times stored in the
HLR.
The Mobile services Switching Center (MSC) is a normal switch with extended functionalities to handle
mobile subscribers. The basic function of the MSC is to switch speech and data connections between radio
access networks such as UTRAN and external non-mobile networks.
A Visitor Location Register (VLR) is associated to each MSC. The VLR can be associated with one or several
MSCs. The VLR stores data about all customers who are roaming within the location area of that MSC.
The Gateway MSC (GMSC) has a routing function. It is the gateway between the UMTS Mobile network and
external Circuit-Switched networks such as PSTN.
The SGSN and GGSN are similar respectively to MSC/VLR and GMSC, but for the Packet-Switched domain.

Section 1 Pager 5
1.2 Functions

UTRAN introduction
Now let’s look at the functions of the UTRAN.

Section 1 Pager 6
1.2 Functions
UTRAN Telecom Main Functions
UTRAN Functions
Transfer of User Data (all classes of Traffic and Multimedia)
Overall system access control (CAC: Call Admission Control)
Radio resource management and control
Mobility management (Soft handover, Hard Handover, Cell Change Order, etc.)
Ciphering
Broadcast services management

UTRAN introduction
Focusing on the UTRAN, we could say that its basic function is the transfer of data between the Core
Network and the UE, whatever the type of data.
This means that compared to the Core, the UTRAN does not deal with applications requiring different
constraints, but rather with packets with a different Quality of service.
Therefore, the UTRAN is just a tool for the Core Network to access the UE over the air interface.
However, dealing with the radio interface is not so easy and other functions of the UTRAN obviously
appear.
The Access Control answers the question: can we accept in the cell this new user with those characteristics
of handset, for this service, using this bit rate and so on?
The Radio Resource Management (RRM) and the Radio Resource Control (RRC) answer this other issue: When
the radio conditions are getting worse, how to modify the parameters of the communication or renegotiate
the requirement in order to keep the same Quality of Service?
User radio mobility is fully controlled by the UTRAN. This mainly includes managing the handovers, the
SRNS relocation or a cell change order. Be careful to differentiate user radio mobility performed by the
UTRAN with the network mobility performed by the Core Network to update the location of a user at
network level.
Moreover, in order to protect the confidentiality of a communication over the air interface, user data
transmitted on the radio path are ciphered by the UTRAN.
Finally, the UTRAN also manages cell broadcast and multicast services such as the SMS.

Section 1 Pager 7
1.2 Functions
Example of Procedure: Call Setup CS, Mobile Originating

UTRAN introduction
Let’s see an example of a signaling procedure for a call establishment initiated by a mobile phone.
3 main entities are involved in this procedure: the User Equipment, the UTRAN and the Core Network.
As you already know, the UE discusses with the UTRAN over the Uu interface, and the UTRAN discusses with
the Core Network over the Iu interface.
First of all the UE establishes a signaling link with one Radio Network Controller (RNC) of the UTRAN. The
procedure is called RRC connection establishment.
Then the UE makes a "Request for a service". It is sent to the RNC through an RRC signaling message and the
RNC forwards the request to the MSC with a RANAP message.
At the next stage, the authentication and ciphering is performed between Core Network and UE.
At the call setup step, the UE indicates the bearer capability required for the call. The CN translates this
bearer capability into a basic service.
Upon reception of the Setup, the CN translates this bearer capability into a basic service with a RAB
allocation and Radio Bearer Allocation
Finally the "Alert" and Connect messages complete the call establishment process. The call can now start!

Section 1 Pager 8
1.2 Functions
Radio Access Bearer (RAB) – (1/2)

UTRAN introduction
We are going to see here what an RAB is.
In a system, network services (such as a voice call or an SMS) are considered as end-to-end. This means
from a User Equipment to another User Equipment.
An end-to-end service may have a certain Quality of Service (QoS) which is provided for the user, and it is
the user who decides whether or not he is satisfied with the provided QoS.
The UMTS Bearer Service has been defined to provide those UMTS QoSs.
The UMTS Bearer Service consists of two parts, the Radio Access Bearer Service and the Core Network
Bearer Service.
We are just going to focus on the Radio Access Bearer (also called RAB) as it is a service provided by the
UTRAN to the Core Network.
The Radio Access Bearer Service provides confidential transport of data between the UE and the Core
network with the QoS adequate to the negotiated UMTS Bearer Service.
This service is based on the characteristics of the radio interface and is maintained for a moving user.
An RAB is itself supported by a Radio Bearer Service over the air interface, and an Iu Bearer Service over
the Iu interface.
As an example of bearer service to support a data transfer, the characteristics of the bearer could be a bit
rate of 9.6 kilo bits per second, without acknowledgment (so in transparent mode), using turbo codes to be
able to detect and correct errors, and so on.

Section 1 Pager 9
1.2 Functions
Radio Access Bearer (RAB) – (2/2)
The RAB provides confidential transport of data between UE

and CN with the appropriate QoS.
1 10 All Rights Reserved © Alcatel-Lucent 2009

UTRAN introduction
You can imagine an RAB as a tube provided by the UTRAN that allows to connect a user to the Core
Network.
The aim of UMTS is to offer multimedia services. This implies that a UE can have at the same time a
connection with the Iu-CS domain and with the Iu-PS domain.
A UMTS bearer service is mapped on one or several RABs: each RAB can have its own QoS requirements
according to the negotiated UMTS bearer service.
Thanks to the Radio Bearer services and the Iu Bearer Services, an RAB must be flexible enough to support
different traffic types, activity levels, throughput rates, transfer delays and bit error rates. Those QoS
parameters may change during an active connection.

Section 1 Pager 10

UTRAN introduction
Now let’s see more in details the functional architecture with all the entities of the UTRAN.

Section 1 Pager 11
UTRAN Network Elements (NEs) and Interfaces

UTRAN introduction
The UTRAN is composed of several Radio Network Subsystems (RNSs).

Each RNS is composed of only one Radio Network Controller (RNC).
Each RNC is linked to several Nodes B attached to it through an Iub interface.
Two RNSs can be linked together through an Iur interface in order to allow the sharing of radio resources.
We will see later in which cases this interface can be used.
One RNS is linked with the Core Network using the Iu interface. The Iu-CS interface interconnects one RNS
to the Circuit Core Network. The Iu-PS interface interconnects one RNS to the Packet Core Network.

Section 1 Pager 12
RNS, RNC and Node B Functions
RNS Functions
Allocation and release of radio
resources to allow connections
between UE and UTRAN
RNC Functions
Control of radio resources in its
domain
Control of UE connections
Service Access Point (SAP) for
CN
Node B Functions
Radio transmission/reception

UTRAN introduction
What are the functions of each entity?
The UTRAN consists of several Radio Network Subsystems. Each RNS performs the allocation and release of
specific radio resources to allow connections between the Mobile Terminal and the UTRAN. For example,
those resources include the transmit power of any element, scrambling codes, frequencies, etc.
The role of the RNC is almost the same as the RNS since the RNC is like the brain of the UTRAN.
So, the RNC controls the radio resources in its domain, meaning all the attached Nodes B. This function of
the RNC refers to its Controlling RNC part.
The controlling RNC has the overall control of the logical resources of its Node B and there is only one
controlling RNC per Node B.
The RNC also controls the user equipment connections. This function of the RNC refers to its Serving RNC
part. In this case, the function of the RNC is directly related to the users. And there is only one serving RNC
per user. For one user, the serving RNC can change depending on the location of this user.
Finally, the RNC is the element of the UTRAN which collects user data for transfer up to the Core Network.
So, we can say that the RNC is like a Service Access Point for the Core Network.
Regarding the Node B, it is much less clever than the RNC. However its simple function is crucial. Indeed,
the Node B is responsible for the radio transmission/reception in its cells of signals going to the mobile
terminal or coming from the mobile terminal.
The Node B also participates in the radio resource and mobility management.
RNC and Node B are sometimes designated by the generic name: Network Element (NE).

Section 1 Pager 13
Serving RNC Definition
What Do We Call a Serving RNC?

"Serving RNC" is one of the RNC functions.
There is one Serving RNC for each UE that
has a connection to the UTRAN.
The Serving RNC is in charge of the radio
connection between a UE and the UTRAN.
The Serving RNC terminates the Iu
interface for the connected UE.

UTRAN introduction
We have just seen the RNC working as a Controlling RNC for all its attached Nodes B.
One RNC can also work as a "Serving RNC" for a mobile user when it performs the transfer of user data and
user signaling for this user.
Here, we are going to detail the function of Serving RNC.
So, as soon as a UE is connected to the UTRAN, it means that one RNC and only one is working as Serving
RNC for this user.
The serving RNC manages radio resources (such as the mapping of RAB parameters onto the air interface,
handover decision or power control) and it terminates the protocols related to this user on both sides of the
RNC.
Therefore, it terminates both the signaling protocols and transport of the Iub link for the transport of user
data between the UE and the UTRAN. It also terminates both the Iu link for the user data and the
corresponding signaling protocol (RANAP) to or from the Core Network.
So, the Serving RNC (SRNC) "serves" a connection related to one UE, compared to the Controlling RNC
(CRNC) that controls a set of Nodes B, so related to one or more Nodes B.
Of course one RNC can be at the same time a Controlling RNC for several Nodes B and a Serving RNC for
several mobile users.

Section 1 Pager 14
Case of Hard HO
One radio link at a time

UTRAN introduction
At this point we will recall different possibilities of handover in UMTS, in order to introduce the third
function of the RNC.
In this example, a mobile with one radio link is connected to the UMTS network. At the limit of the UMTS
coverage, the UE is going to hand over a GSM cell and thus it cannot keep the two links simultaneously.
If a mobile changes of frequency or of system, the network needs to allocate new resources in the target
cell and to release the UE link in the source cell: it’s a Hard Handover.

Section 1 Pager 15
Case of Softer HO
Cell A
Cell B
As all cells are working on the same frequency, you

can take advantages of the diversity paths.

UTRAN introduction
In this second example, the UE sets up a radio link on the cell A of the Node B and is then connected to the
"Serving RNC".
As the frequency used in all the Node B sectors is the same, it is easy for the mobile to add a radio link
through the cell B.
This new link must be considered as an additional diversity path, increasing the gain of your signal.
A case where the active cells belong to the same node B is called a SOFTER Handover.
It allows us to recombine both signals, directly at the physical layer within the Node B.

Section 1 Pager 16
Drift RNC Definition: Case of Soft HO
What Do We Call a Drift RNC?

"Drift RNC" is the third RNC function.
A Drift RNC offers its radio resource to a serving RNC for a given user.
Serving and Drift RNCs manage inter-RNC handovers through Iur.
Drift
RNC

UTRAN introduction
The soft HO is similar to the softer HO we have just described, but now the UE is linked to 2 different
Nodes B.
If the Node B belongs to another RNC than the serving one, then this RNC is called the Drift RNC.
This third function of the RNC allows us to provide the UE with radio resources and the communication is
still managed by the serving RNC. The Drift RNC acts as a switch relay.
We see here the utility of the Iur interface between 2 RNCs: to allow a Serving and a Drift RNC to perform
inter-RNC handovers.

Section 1 Pager 17
1.4 Protocols

UTRAN introduction
Now, let’s see how it works at protocols level.

Section 1 Pager 18
1.4 Protocols
Radio Protocols: UE – RNC Communication
Control Control
User Plane User Plane
Plane Plane
RRC RRC
RLC RLC
Logical channels Logical channels
MAC MAC
Transport channels Transport channels
Iub-FP Iub-FP
Transport Transport
Physical Physical layer layer
(WCDMA) (WCDMA)
Physical Physical
RNC

UTRAN introduction
Let’s look first at the radio protocols. Radio protocols are used to exchange signaling and traffic data between the UE and the UTRAN,
mainly the RNC.
Here is a common representation of protocols called a protocol stack.
In a protocol stack, the higher layer of protocols close to the services is represented at the top. Below this layer, other protocols are
applied to the data in order to pass through the network as well and as quickly as possible.
Each protocol has specific functions. We are going to describe each one briefly.
Let’s begin with the user plane in the higher layer of the Access stratum of the UE. No protocols are usually used at this level in order
to transmit a voice call. Regarding the transfer of data, 2 different protocols can be applied.
The Packet Data Convergence Protocol (PDCP) allows to compress the header of IP packets.
The Broadcast/Multicast Control protocol (BMC) allows to broadcast messages such as SMS to all users of a cell for example.
Then, the Radio Link Control protocol (RLC) controls the link. For example, the RLC protocol can apply a retransmission algorithm to
insure the reception of a frame, or perform segmentation of big packets.
The output of the RLC protocol down to the MAC layer is called a logical channel.
The Medium Access Control layer (MAC) has a very important role regarding the resource management. Indeed, the MAC layer
multiplexes logical channels between each other in order to optimize the size of the radio frame sent over the air interface.
The result is called a transport Channel.
Once in the Physical layer, those channels are multiplied by the codes, modulated, multiplied by the carrier frequency, etc to be sent
over the air interface and received by the Node B.
At the Node B, the physical layer filters around the carrier frequency, demodulates and re-multiplies by the codes to rebuild the
transport channels which are then, mapped on to protocols such as the Iub Frame Protocol, for the transport up to the RNC.
A new physical layer allows to map those transport frame onto the medium which can be an optical fiber for example.
Up to the RNC, transport channels are rebuilt again, then the MAC layer demultiplexes them to rebuild the logical channels.
Eventually, the RLC layer will concatenate or ask for a retransmission.
And finally, the voice can be decoded or in case of data transfer, the PDCP protocol will be used to decompress the IP header of IP
packets.
Now if we look at the transmission of a signaling message. First, the Radio Resource Control protocol (RRC) will be used.
Indeed, the RRC protocol provides information transfer upper to the Non-Access Stratum and controls the configuration of the radio
interfaces through lower layers.
Otherwise, nothing changes for the transmission of RRC messages.
RRC messages go down the different layers: RRC, MAC, Physical layer, over the air interface, mapped on ATM cells in the Node B and
then up to the RRC protocol of the RNC to be treated.
Section 1 Pager 19
1.4 Protocols
Network Protocols Based on ATM Transport

UTRAN introduction
After the radio protocols between the user and the UTRAN, network protocols are also protocols of the
access stratum managed partly by the UTRAN.
They are used to exchange signaling and traffic data between the Network Elements.
So it can be between a Node B and its RNC over the Iub interface, between 2 RNCs over an Iur Interface,
or between the RNC and a gateway of the Core Network over the Iu-CS or Iu-PS interface.
Like the Radio protocols, network protocols present a Control plane and a User plane.
The User plane includes protocols that transmit traffic data through the Network Elements and has the
transport and physical layers in common with the control plane.
Basically, the user plane uses the same protocols between the different Network Elements.
You can notice that the traffic data between Network Elements include the RRC protocol as it is radio
signaling at the level of a user and not at Network Element level.
Regarding the control plane, different protocols manage the signaling between the Network Elements.
The Node B Application Protocol (NBAP) is used to exchange specific signaling between an RNC and a
Node B.
The Radio Network Subsystem Application Protocol (RNSAP) is used to exchange specific signaling
between 2 RNCs.
And finally the Radio Access Network Application Protocol (RANAP) is used to exchange specific signaling
between an RNC and the Core Network.

Section 1 Pager 20
1.4 Protocols
Network Protocols Based on IP Transport
Possible evolution of
transport interfaces
in UA06:

UTRAN introduction
A smooth evolution from the ATM Transport Backbone to an IP Transport backbone is possible thanks to the
introduction of the Release UA06.
This evolution enables to carry high load of DATA traffic, such as an Internet call, through a cost-effective
backbone based on IP over Ethernet.
The Iub and the Iu-PS interfaces can be deployed with such a technology. We will cover this point in deeper
detail later in this training.

Section 1 Pager 21

UTRAN introduction
Let's examine how the radio interface has evolved.

Section 1 Pager 22
HSDPA: What For?
HSDPA Standardized by 3GPP R5

HSDPA is designed to:
Increase the Downlink data throughput over the air interface (theoretical peak user bit
rate = 14.4Mbps).
Provide instantaneous high data rates in the PS domain (e.g., Internet browsing, video
on demand).
HSDPA could be deployed in both FDD and TDD modes.
DL
UL

UTRAN introduction
High Speed Downlink Packet Access (HSDPA) has been standardized by 3GPP R5. It aims at increasing
significantly the downlink data throughput up to 14.4 Mega bits per second at the physical layer. It is based
on techniques such as Adaptive Modulation and Hybrid ARQ to achieve such high data throughput, and
peak rates and reduce delay.
HSDPA relies on a new type of transport channel, the HS-DSCH, which is terminated in the Node B. HS-DSCH
is applicable only on PS domain RABs.

Section 1 Pager 23
HSDPA: How Does It Work?
How is HSDPA able to provide higher spectral efficiency with the same radio resources
(5MHz BW, power, frequency, codes)?

UTRAN introduction
One can wonder how with the same frequency bandwidth, transmitters power and OVSFs, HSDPA is able
to achieve such high performance.
HSDPA is using a "smarter Radio Management" with both QPSK and 16 QAM modulation techniques.
The Transmission Time Interval (TTI) is shortened to 2ms to achieve short round trip delay between the
Node B and the terminal, compared to 10, 20 or 40-ms TTI defined in release ’99.
Users are code & time multiplexed. One user can get various number of codes depending on the
scheduling strategy implemented.
As stated previously, the maximum data rate is 14.4Mbps. This maximum theoretical throughput can be
allocated either to one user having 15 codes allocated or it can be divided between several users. If
QPSK is used, the maximum theoretical throughput cannot be achieved. If one user gets all the 15 codes,
then only one modulation (either QPSK or 16-QAM) is used on all the codes.
Fast scheduling is an important part of Radio Resource Management. The choice of the Fast Packet
Scheduling strategy has an influence on achievable cell throughput.
For example, a fair scheduler will provide fairness regarding user throughput, but will decrease the
overall cell throughput. A scheduler based on channel quality will maximize the cell throughput, favor
the UE close to the Node B despite of other users at the edge of the cell.

Section 1 Pager 24
HSDPA: Better Use of Resources
With DCH With HS-DSCH
A shared channel is much more efficient

than a dedicated channel to carry bursty packet traffic.

UTRAN introduction
HSDPA is using a shared transport channels, the High-Speed Downlink Shared CHannels (HS-DSCHs). It is
easy to understand that shared channels are more cost efficient than Dedicated CHannels (DCHs). But there
are other advantages. Dedicated CHannels have been designed predominantly for circuit-switched
services, that is to say for a conversational Quality of Service class: constant bit rate and stringent real-
time requirements. DCHs are not cost-efficient for packet-switched services and are difficult to optimize.
Shared channels have been introduced to fit with packet-switched services that are downlink oriented
with a “bursty” nature and that are less sensitive to delay than circuit-switched services.

Section 1 Pager 25
HSDPA: New Functionalities of the Node B
MAC-hs
With HSDPA, a new MAC layer is implemented in
the Node B (MAC-hs):
To save transmission time as most of the
retransmission can be done from the Node B. Ok, at the next TTI, I will allocate the
radio resources as follows:
To schedule rapidly users with the radio UE 3:
resources (every 2ms). 6 codes (SF=16)
16-QAM modulation
Coding rate of 3/4
UE 12:
4 codes (SF=16)
QPSK modulation
Coding rate of 1/2
UE 4: nothing
UE 6: nothing

UTRAN introduction
A new MAC layer called Medium Access Control high speed (MAC-hs) is implemented in the Node B. The
choice to implement this protocol stack in the Node B rather than the RNC as for the MAC-d, MAC-c, MAC-sh
and MAC-b is to reduce packet transmission time. Hence most packet retransmission can be done from the
Node B. User scheduling is efficient as the TTI duration is reduced for MAC-hs to 2 milliseconds.

Section 1 Pager 26
HSUPA: What For?
HSUPA Standardized by 3GPP R6

HSUPA is designed to increase the uplink data throughput over the air interface theoretical
peak user bit rate (5,7 Mbps).
Uplink
HSUPA
High
Throughputs 3GPP Release 6
Dedicated
Channels
Throughput
&
Capacity

UTRAN introduction
High-Speed Uplink Packet Access (HSUPA) is introduced by 3GPP in release 6 with the aim to improve the
Uplink (UL) data rate.
HSUPA is characterized by a high data rate for PS calls over the UL air interface.

Section 1 Pager 27
HSUPA: How Does It Work?
How is HSUPA able to provide higher spectral efficiency with the same radio resources
(5MHz BW, power, frequency, codes)?
E-DCH Uplink Function in

(an enhanced Dedicated
channel) the Node B
(RRM and Noise Rise)
HSUPA
Technology
Fast retransmission Fast Scheduling

(every 10ms mandatory; 2ms
mechanism
optional at the NodeB)
(Hybrid-ARQ)
QPSK Modulation
(2 BPSK)

UTRAN introduction
The 3GPP objectives are to improve the performance of uplink dedicated transport channels by scheduling
the Uplink UE data rates depending on the interference and on the Node B processing resources, while
increasing the radio interface robustness with the HARQ protocol associated with TTI of 2ms and 10ms.
HSUPA is not only an HSDPA for the reverse link.
Of course, some of the mechanisms are inspired by the HSDPA solution (HARQ process, Incremental
Redundancy, Scheduling) but more generally HSUPA is an enhancement of classical dedicated channels.
Such new UL channels will be called in the following slide, E-DCH channels.

Section 1 Pager 28
HSUPA: Increase of UL Capacity
New UL High Bit Rate Transport Channel: E-DCH
Logical DCCH DTCH DTCH
Signaling Traffic Traffic

SRB TRB TRB
Mobile i Mobile b Mobile i
Transport DCH HS-DSCH E-DCH

UL DL DL UL
Physical DPCCH DPCCH HS-PDSCH E-DPDCH
HS-SCCH HS-DPCCH E-HICH E-DPCCH
E-AGCH E-RGCH
E-DCH coupled with HSDPA
enhances the spectral
efficiency.

UTRAN introduction
The introduction of new UL channels allows high bit rate and global quick resources sharing is useful to map
as a first step the best effort UL traffic (i.e., Interactive/Background traffic on E-DCH) keeping for DCH the
UL Conversational/Streaming traffic class.
A specific E-DCH transport channel is defined. As the classical DCH transport channel, it allows to offer
transport services to higher layers.
E-DCH network introduction while being coupled with HSDPA (for which the same basic segmentation has
been done – DL Conversational/Streaming on DCH and DL Interactive/Background on HSDPA) enhances the
spectral efficiency of UMTS technology versus live uneven traffic.
Indeed, E-DCH/HSDPA maximizes the number of high data rate users from an air interface standpoint while
minimizing the UL/DL service delay.
By principle, E-DCH with HSDPA dynamically adapts and maximizes the peak data rate of each subscriber
according to cell load and UTRAN resource availability.

Section 1 Pager 29
HSUPA: New Functionalities of the Node B
MAC-e
Radio Resource Management and Noise Rise Management are handled in the Node B.
HSUPA impacts the MAC layer implemented in the Node B (MAC-e):
To save transmission time as most of the retransmission can be done from the Node B.
To schedule rapidly users with the radio resources (every 10 or 2ms).
Ok, at the next TTI,

I will allocate
the radio resources.
RNC
E-DCH over E-DPDCHs
Node B

UTRAN introduction
The Node B supports several HSUPA functions which are fast scheduling at Node B level, fast retransmission
of data, QPSK modulation (2 BPSK), Uplink Noise Rise Management in the Node B and Uplink resource
management in the Node B.
To perform those functions, a new MAC layer called MAC-e is introduced in the Node B.

Section 1 Pager 30
Quiz maker

UTRAN introduction

Section 1 Pager 31
End of Module
UTRAN introduction

UTRAN introduction

Section 1 Pager 32
2
Section 2
UTRAN Transport Layer
9300 W-CDMA
3JK11630AAAAWBZZA1
Edition 1

Section 2 Pager 1
Objectives
Objectives:
To be able to describe the UTRAN ATM transport layer.
Content:
2.1 ATM Notions
2.2 AAL Used in the UTRAN
2.3 ATM Cells on Physical Links
2.4 VP/VC Connections and IMA Feature
2.5 Evolution to All IP

In this chapter, we are going to see what the benefits of ATM are, the role and the implementation of the
ATM Adaptation Layer (AAL) in the UTRAN, how ATM cells are mapped on physical links, how an ATM cell is
routed as well as the use of the IMA feature in the UTRAN. Finally we will see how the UTRAN transport
backbone will evolve to an "All IP" transport network.

Section 2 Pager 2
2 UTRAN Transport Layer
2.1 ATM Notions

What does ATM mean and why is it used in the UTRAN?

Section 2 Pager 3
2.1 ATM Notions
Principles of ATM

At the moment, 2 types of techniques are used to convey information: Circuit switching and Packet switching.
The Circuit switching works on the principle of fixed phones for which you establish a “circuit”, dedicated to the
communication between the users.
The advantages are a bit rate and a delay guaranteed as the dedicated link cannot be used by anyone else.
The disadvantage is the fixed rate which implies a loss of resources during silence and the incapacity to adapt the
rate to the service.
The Packet switching works on the principle of IP packets like on Internet.
The information is divided into packets that can take different ways to join the destination point.
The advantage is in the flexibility of the rate since you can adapt the rate to the service and so optimize the
resources by multiplexing different users with different traffic profiles.
The disadvantage is the incapacity to insure neither a constant rate nor a delay.
ATM is a standard mixed transport technology that combines the advantages of the circuit-switched mode and of the
packet-switched mode. ATM stands for Asynchronous Transfer Mode.
The asynchronous transfer mode is based on the transmission of small packets called cells. The number of cells
generated will be proportional to the rate of information sent by the source.
So ATM benefits, in terms of Quality of Service, from the connection-oriented mode as an ATM call can be made only
over a dedicated connection. ATM also benefits, in terms of flexibility, from the rate since information is
transported in cell form as a small packet. Therefore, it is possible to share a connection among users with different
data rates but requiring the same QoS.
Guaranteed connection means that there is a path between two points in the network, that Quality of Service is
linked to the information transmitted. A connection can be either point-to-point and bidirectional or point-to-
multipoint and unidirectional.
Cell switching means that the information is transported in cell form. A cell is a small packet of fixed size and
contains the information needed to route it through the network.
ATM is a standard mixed transport technology that combines the advantages of both circuit- and packet-switched
modes. The circuit-switched mode provides guaranteed rate and delay as ATM is connection-oriented whereas the
packet-switched mode provides flexibility in bit rates and statistic gains due to multiplexing of different users with
different traffic profiles as ATM is cell switching.
Section 2 Pager 4
2.1 ATM Notions
ATM Cell Definition

What does an ATM cell look like?

Like an IP address of an IP packet, an ATM cell has a header that allows to route the cell in the network.
Compared to IP packets, this header is fixed to 5 bytes and the payload is fixed to 48 bytes.
So an ATM cell has a fixed size. Consequently, there is no need to control its payload.
Inside the header, the information for the routing of the cell is given by the identifier of the Virtual Path
(VPI) and inside this Virtual Path, the Virtual Circuit is given by another identifier (VCI).
An ATM cell is built with simplicity and the switching cell concept provides flexibility.

Section 2 Pager 5
2.1 ATM Notions
ATM Is Connection-Oriented

In order to understand the routing of an ATM cell through the network, let’s see on this example of LAN
game, how User 1 can send information to other users.
As seen previously, we don’t have any identification for the destination but we have identifiers for the
connection used to reach it.
So when User 1 wants to send information to user 2, he knows that he has to send the cells on the Virtual
circuit number 4 of the Virtual Path zero.
Inside the first ATM switch, a static routing table automatically routes the couple “VP zero VC 4” on the
“VP 7 VC 5” up to the second ATM switch.
This switch reads in its static routing table that the incoming VC 5 of the VP 7 has to be routed on the VC 8
inside the VP zero up to User 2.
So you see that an ATM connection relies on the information written on the static routing tables of the ATM
backbone.
In the same way, if User 1 sends ATM cells to User 3, he knows, thanks to the static routing tables, sending
them on the VC 2 of the VP 0, that ATM cells will go through the ATM backbone and will be received by User
3 on VC 1 of the VP zero.

Section 2 Pager 6
2.1 ATM Notions
ATM Reference Model

Let’s zoom on the ATM reference model.

The ATM model is organized in three layers: the Physical layer, the ATM layer and the ATM Adaptation Layer
(AAL).
The physical layer contains the transmission-related functions, so the adaptation to the physical medium
(that can be a PCM or an optical fiber), and applies some transmission processings such as Rate adaptation
or error control.
The ATM layer handles the routing of information with the addition or extraction of the cell header, and
the multiplexing/switching of ATM cells.
The ATM adaptation layer adapts information from the higher layers to create payload adapted to ATM
cells. In the other way, it adapts the payload of ATM cells to the nature of the frames in higher layers (such
as voice, video or data). That’s why it exists several ATM aAdaptation Layers with different characteristics.
In the following slides, we will describe the 2 types of ATM Adaptation Layer implemented in the UTRAN:
AAL5 and AAL2.

Section 2 Pager 7
2.1 ATM Notions
ATM Adaptation Layer 5: AAL5

AAL5 has been designed to adapt non real time, connectionless-oriented data at variable bit rate to ATM.
Typically, applications with those criteria can be web browsing or e-mails for example.
So, AAL5 deals with big packets, and/or packets with non delay requirements.
Big packets probably need to be cut to fill several small ATM cells with their 48-byte payload.
AAL5 has been designed in this way since it is just able to apply segmentation on packets of higher layers.
In the connection, in order to inform about the end of the packet, a trailer is added at the last segment of
data. So, each part perfectly fits the 48-byte payload of the ATM cell.
The ATM layer then encapsulates the payload in an ATM cell and generates identifiers for the virtual path
and the virtual circuit.

Section 2 Pager 8
2.1 ATM Notions
ATM Adaptation Layer 2: AAL2

Regarding the other ATM adaptation layer used in the UTRAN, AAL2 has been designed to adapt real time,
connection oriented data at variable bit rate.
Typically, an application with those criteria can be a voice call for example.
So, AAL2 deals with small packets, and/or packets with high delay requirements.
In order to fill one ATM cell with a 48-byte payload, small packets need to be concatenated.
AAL2 has been designed in this way since it concatenates several small packets in a 48-byte payload.
In the connection, in order to inform about the destination of the data block inside the ATM cell, a
Connection IDentifier (CID) is added to each data block.
The ATM layer then encapsulates those data units and their User identifiers in an ATM cell and generates
identifiers for the virtual path and the virtual circuit.

Section 2 Pager 9

Let’s see where AAL2 and AAL5 are used in the UTRAN.

Section 2 Pager 10
UTRAN Interfaces Based on ATM (User Plane)

All information sent and received by the user, such as the coded voice in a voice call, or the packets in an
Internet connection, is transported via the user plane.
On the radio interface, small packets are transferred through the ATM model as they result from the
RLC/MAC layers. Those packets have a size independent from the type of service. That’s why AAL2 is used
over the Iub and Iur interfaces.
On the Iu interface, we find service-specific packets such as IP packets on the Iu-PS interface.
So, AAL2 is used efficiently on Iu-CS for speech because it makes use of silence suppression and idle
channel suppression.
AAL5 is more suitable for the Iu-PS domain because it is more efficient for the bigger IP packets.

Section 2 Pager 11
UTRAN Interfaces Based on ATM (Control Plane)
Iub
RNC
CSCN
Nodes B Iu-CS
Iur
Iub Iu-PS
PSCN
RNC
Node B

In the control plane, AAL5 is used everywhere for all specific control signaling, since the packets of higher
layers can be bigger than the RLC/MAC radio blocks.

Section 2 Pager 12

ATM cells can be conveyed over E1 links or over STM-1 links.

But, how are ATM cells mapped on those physical links?

Section 2 Pager 13
ATM on PCM Link (E1) at 2Mbps
Characteristics of an E1 Frame
125 µs
32 bytes
0.58 ATM cell

Let’s see first how it works on a PCM link like E1 links at 2 mega bits per second.
An E1 frame lasts 125 micro seconds. At 2 mega bits per second, it represents 32 bytes of data, that is a
little bit more than half an ATM cell.
Therefore, a 53-byte ATM cell is mapped over several PCM frames.

Section 2 Pager 14
ATM on SDH Link (E1) at 155Mbps
Characteristics of an STM-1 Frame

125 µs
2430 bytes
44 ATM cells

Let’s see now how it works on an SDH link like STM-1 links at 155 mega bits per second.
An STM-1 frame also lasts 125 micro seconds. But at 155 mega bits per second, it represents now 2,430
bytes of data, that is 44 ATM cells.
Therefore, 44 ATM cells can be mapped over one single STM-1 frame.

Section 2 Pager 15

Well, let’s now talk about the VP/VC connections as implemented in the UTRAN.

Section 2 Pager 16
VP/VC Connections Characteristics
1 connection = 1 (VP/VC) = 1 Quality of Service

VP/VC connections are established on terrestrial interfaces based on ATM.

Each connection has its own characteristics in terms of bandwidth, delay constraints, error rate, ATM
adaptation layer used, etc.
You know that one connection corresponds to one VP/VC couple.
So it is easy to remark that to one VP/VC is attributed one Quality of Service.

Section 2 Pager 17
IMA Principles and Benefits
Principle
Inverse Multiplexing for ATM (IMA) enables the transport of one ATM VP over several
physical links such as E1 links.
Without IMA With IMA
Interest
With HSDPA introduction, the radio interface overcomes the throughput manageable on
VPs of the current Iub. IMA overcomes this BW limitation.

IMA stands for Inverse Multiplexing for ATM. It enables the transport of one ATM VP over several physical
links such as E1 cables.
In fact, with HSDPA introduction, it is likely that operators will need VP bandwidth higher than 2Mbps,
which is the physical limitation of E1. It is possible to transport these large VPs over STM-1 but this is
certainly overdimensioned at the time of HSDPA introduction. Hence, IMA technology is the appropriate
solution to overcome this issue. It enables the transport of one ATM VP over several physical links such as
E1 links, and it allows then the configuration of VPs with capacities higher than 2 mega bits per second over
the Iub interface.
Thus the IMA feature allows first to overcome the bandwidth limitation of a single physical link and
handling ATM connections over a bundle of physical links, called an "IMA virtual link".
The IMA enables to simplify the configuration of the ATM transmission on Iub. In fact, the operator will
have the possibility to configure one VP instead of several VPs, or worse, individual VCs. The bandwidth
associated to this VP connection may be higher than what would be offered by a single physical link. For
instance, without IMA, 4 VPs of maximum 1920 Kilo bits per second each are defined for a Node B
connected to an RNC with 4 E1 links.
With IMA, it becomes possible to define a single VP of 7616 Kilo bits per second bandwidth. Of course the
configuration of several VPs on the Iub interface will still be possible.
Finally, IMA allows redundancy in case of failure of one or several E1 links. Indeed, the VP will still carry
traffic even if its capacity is degraded.

Section 2 Pager 18
UTRAN Configurations with IMA
Iub with IMA terminated

in the ATM Backbone
Iub with IMA terminated

in the RNC transport node

IMA is provided on Node B side on E1 links and managed by Operation and maintenance. It is terminated
in the first ATM equipment connected to the Node B. Therefore there are two possible cases as
illustrated here.
In case there is an intermediate ATM switch between RNC and Node B, IMA is terminated in the first ATM
switch between Node B and RNC. This switch needs to support IMA.
In case Node B and RNC are directly interconnected at ATM layer, the Transport Node terminates IMA as
peer entity to Node B.

Section 2 Pager 19
2.5 Smooth Evolution to All IP

Well, let’s now talk about the evolution from an ATM to an "All IP" transport backbone.

Section 2 Pager 20
Transport Backbone in UA05.1
Characteristics
HSPA Offload over DSL
Support Split Iub
supports 2 IMA groups
IMA = pE1
R99 over ATM
E1 Leased Lines
HSPA over low

IMA = nE1 Cost Backhaul
DSL DSL

Alcatel-Lucent’s UTRAN offers the possibility to split the HSPA traffic from the R99 traffic at the Node B
level into two streams. The R99 stream can be carried over one IMA, and the HSPA stream can be carried
over another IMA.
Split R99 & HSDPA traffic with 2 IMA groups are supported on the Node B interface board.
The support of two IMA groups allows to separate HSPA (HSDPA + HSUPA) traffic from R99 traffic on Iub
interface. On the one hand, the HSPA traffic is exclusively carried over a group of E1 links inside a first IMA
group. On the other hand, a second group of E1 links inside a second IMA group is used for R99 User Plane,
Control Plane and OAM traffic. This group may also carry HSPA traffic.

Section 2 Pager 21
Transport Backbone in UA06
Characteristics
Optimized HSPA Offload
Hybrid Iub
IMA = nE1
R99 over ATM

E1 Leased Lines
Node B HSPA over IP

Low Cost
Ethernet Backhaul
7705 7705

As you can see, HYBRID IUB introduces a hybrid transport (ATM & IP) on the Iub interface on the RNC &
Node B. This functionality enables the operator to split delay sensitive traffic from non delay sensitive
traffic. R99 traffic is carried over E1 to secure voice transportation as well as all delay sensitive traffic,
whereas non-delay sensitive traffic is carried over IP, over a private IP network.
In the hybrid Iub interface, the R99, signaling and OAM traffic remains on the ATM/PCM and the HSPA
(HSDPA and E-DCH) is supported on IP/Ethernet. Hybrid Iub requires a 100Base-T Ethernet port in the Node
B and a Gigabit Ethernet board on the RNC side.

Section 2 Pager 22
Transport Backbone in UA07
Characteristics
Native IP over Ethernet
Ethernet
Node B
Network with
SGW
Ethernet Sync.

Alcatel-Lucent will support native IP Iub with Node B. This product supports IP over Ethernet directly. A
Giga bit Ethernet module is integrated directly into the RNC to support the IP connectivity.
The RNC is connected to a public IP backbone through a Security Gateway (SGW) which protects the RNC
against malicious attacks using Virtual Private Network tunnelling. The SGW is also used to terminate IPSec
tunnels with Node B.
This requires software features to enable native IP on the Node B. No hardware upgrade is required.
Indeed, it is a simple matter of changing the connection.

Section 2 Pager 23
UTRAN Interfaces Based on IP (User Plane)
IP Evolution in UA06
Iub
RNC
CSCN
Nodes B Iu-CS
Iur
Iub Iu-PS
PSCN
RNC
Node B

The evolution of the Tranport network towards IP is applicable on 2 interfaces in UA06. The first possible IP
evolution is the introduction of the Hybrid Iub Interface, combining both traffic such as voice over ATM and
traffic such as data on IP over Ethernet. The second possible IP evolution consists in the Iu-PS interface
towards the SGSN. This interface will carry the Internet packet on a IP backbone over Ethernet instead of
AAL5 over ATM.

Section 2 Pager 24
UTRAN Interfaces Based on IP (Control Plane)
IP Evolution in UA06
Iub
RNC
CSCN
Nodes B Iu-CS
Iur
Iub Iu-PS
PSCN
RNC
Node B

The Iu-PS interface is an open interface between the RNC and the SGSN for the packet domain.
ATM and IP stacks for Iu-PS are supported.
On this interface, the SCCP supports transport of RANAP messages used by the Control Plane.
The ATM stack is like the Iu-CS interface.
The AAL5/ATM stack is used to transport IP packets across the Iu interface towards the packet-switched
domain.
The IP stack uses the MTP-3 User Adaptation Layer (or M3UA) and the Stream Control Transmission Protocol
(SCTP) to transport signaling over the IP network.
UDP/IP is used for the User Plane.
Dynamic management of GTP tunnel is ensured by the user plane towards the PS domain.
The physical layer is supported by OC-3/STM-1 and IP over Gigabit Ethernet.
The Transport Network Control plane is not necessary on the Iu-PS interface.

Section 2 Pager 25
Quiz maker


Section 2 Pager 26
End of Module


Section 2 Pager 27
3
Section 3
UTRAN Elements
UTRAN Elements
9300 W-CDMA
3JK11631AAAAWBZZA1
Edition 1

Section 3 Pager 1
Objectives
Objectives:
To be able to describe the functional architecture and the configurations
of the UTRAN elements (RNC, Node B portfolio).
Content:
3.1 RNC Description
3.2 Node B Description

UTRAN Elements
In this chapter, we will focus on each element of the UTRAN. So you will be able to describe the
functional architecture and the configurations of the RNC 9370, and the Node B portfolio.

Section 3 Pager 2
3 UTRAN Elements
3.1 RNC Description

UTRAN Elements
Let’s start with the description of the Standard RNC.

Section 3 Pager 3
3.1 RNC Description
Role of the RNC
RNC Functions
Concentration step between Node B and core network
Control of a set of Nodes B
Radio Resource Control
Diversity Handover
Power control (outer closed loop)

UTRAN Elements
The Radio Network Controller broadly supports the same functions as the BSC in a GSM system.
The RNC exchanges information with the core network and Node B while controlling call origination, call
termination, call clearing, diversity handover, and other call processings. Those are examples of the
radio resource control.
The RNC is also connected to an adjacent RNC via an Iur interface which enables to perform soft
handovers and so to increase the capacity as well as the coverage of the cells.
Another key function of the RNC is to perform a fast and accurate power control which is possible with
the Closed loop power control. This allows to save the key radio resource of the UTRAN.

Section 3 Pager 4
3.1 RNC Description
Situation of the RNC in Full ATM Configuration
In the Alcatel-Lucent solution, the RNC is made up of a Control Node, an Interface Node
and an optional network element called the PoC (can be used for PCM to STM-1
conversion).
RNC functionalities
Iub/
STM-1 STM-1 MSC
Iu-CS
9370 RNC
Iub/E1 Iu-PS
ATM ATM SGSN
backbone C-Node backbone
BTS I-Node Iur
RNC
STM-1
PoC
(Point of OAM
Concentration) link
BTS Conversion for
BTS E1 transmission
OMC

UTRAN Elements
In the Alcatel-Lucent UTRAN architecture, two different types of RNC configurations can be
implemented in the network according to the physical links used by the operator. The first type is the
RNC in full ATM Configuration. The RNC with ATM Optical interfaces (SDH/SONET technology) allows
the operator to directly connect the RNC to the Nodes B through the Iub interface based on an OC-
3/STM-1 optical link up to the ATM backbone. In this case, the electrical link for E1/T1 frames covers the
second part of the Iub interface, from the ATM backbone down to the Nodes B.
A Point of Concentration (PoC) associated to the RNC can offer direct PCM connectivity (E1/T1) along the
Iub interface. However, this solution requires an additional equipment which is the A7670 platform. This
equipment supports electrical links for 120Ω and 75Ω E1 frames.
In both cases, the Iu (toward Core Network) and Iur (toward a neighboring RNC) interfaces are based on
an OC-3/STM-1 optical link.
OAM connection to the Wireless Management System (WMS) can be managed with an Ethernet link to a
LAN or In-band through the ATM backbone.

Section 3 Pager 5
3.1 RNC Description
Alcatel-Lucent RNC Evolution to IP
Iub/
STM-1 STM-1
Iu-CS MSC
Alcatel-Lucent
RNC
Iub/E1
Iur
ATM ATM Other
backbone backbone RNC
BTS
9370 RNC
Itf-R
Itf-B
Fast-Ethernet IP
backbone IP
backbone
OMC
Giga-Eth
Giga-Eth SGSN
Iu-PS

UTRAN Elements
The second type of RNC Configuration supports IP transport on the Iub and Iu-PS interface.
A native IP Iub interface is introduced through a software upgrade and the addition of two 4-ports Gigabit
Ethernet boards on the RNC connected to the IP backbone. In this case, Fast Ethernet frames covers the
second part of the Iub interface, from the IP backbone down to the Nodes B.
IP over Ethernet interface is used to carry HSDPA/HSUPA best effort traffic type (Interactive and
Background). No forklift is required and the existing STM-1 boards can be used for any interfaces that
remain on ATM transport: R99 services and Streaming on HSDPA, newly introduced in release UA06, is
transported over the Iub ATM based interface.
IP over Ethernet is also used to convoy the packet data over the Iu-PS interface toward the SGSN by using
the 4-ports Gigabit Ethernet boards on the RNC. The voice and video calls remain on the Iu-CS ATM based
interfaces.

Section 3 Pager 6
3.1 RNC Description
9370 RNC Hardware Overview
Power Carrier Grade Platform 9370 RNC

SDH configuration (MSS15K):
C-Node / I-Node
single cabinet
on MSS 15K
16 STM-1 connectivity
IP configuration:
Hybrid Iub and Iu-PS
4 Giga - Ethernet connectivity Option with PoC or a
2nd 9370 RNC
Scalability: 5 models available
Capacity
Up to 2400 Node B, 2400 cells,
8000 Erlangs per RNC
• Low-level telecom
• User plane processing
• Interface termination (STM-1 and Giga-Eth)
• Call processing
• Shelf/platform management

UTRAN Elements
The Alcatel-Lucent RNC is called the RNC 9370. The 9370 RNC is implemented on an MSS 15000 (15K)
platform that provide both I-Node and C-Node functions in a single shelf.
The I-Node or Interface Node, with its 16 STM-1 connectivity and 4 Giga Ethernet connectivity, allows to
connect up to 2400 Nodes B and 2400 cells.
The C-Node or Control Node offers the processing capabilities of 8000 Erlangs.
Optionally a Point of Concentration or a 2nd 9370 RNC can be put in the upper shelf.

Section 3 Pager 7
3.1 RNC Description
RNC Architecture
Control Processor
Packet Server • Switch supervision
• ATM segmentation and re-assembly • Network management
• High level radio bearer processing • Configuration control
• Radio protocol termination (RLC, MAC, etc.) • Routing tables and topology mgt
Packet Server CP
Packet Server CP
Dual Core Packet Server

(DCPS) Packet Server 16p OC-3STM-1
Up to 12 * DCPS per RNC
4p Giga-Eth
16p OC-3STM-1 ATM Transmission
provides 16 STM-1 ports
for connectivity
Packet Server 4p Giga-Eth
IP Transmission
provides 4 Gbps Ethernet
Internal connection ports for connectivity

UTRAN Elements
The 9370 RNC platform includes 4 main types of boards. First Control Processors (CP4) are used for the
overall RNC OAM tasks and IP routing functions. Then Dual Core Packet Server Processors (DCPSs) manage
the call processing and the radio protocols. Next the 16 ports OC-3/STM-1 Functional Processors (16p OC-
3/STM-1 FPs) and 4 ports Giga bit Ethernet Functional Processors (4p Giga-Eth FPs) provide optical
interface ports that connect network communication facilities and switches. And finally, fabric cards
allow fast internal bus communication between the processing boards.

Section 3 Pager 8
3.1 RNC Description
Transport Node / PoC: A7670
OSS
5620 NM OAM WMS OAM
Fault Performance Configuration

Transport Nodes (Co-located with RNC)
8p OC3/STM1o Ch High Density

8p STM1e Ch 16P
VC12/IMA
16p OC3/STM1c OC3STM1c
16p OC3/STM1c
Node B 4p Gig-E
7670 RSP
1 : N RNC
High Density
T1E1 IMA,
32p T1/E1 Low density
Core 1p OC3STM1o Ch VC12IMA 4P Gip-E
Network 1p STM1e Ch 4p OC3/STM1c
1p OC3/STM1c 7670 ESE
1 : 1 RNC
ATM/IMA termination, VP shaping, ATM switching, …

UTRAN Elements
Alcatel-Lucent takes advantage of Transport Node(s) (often referred to as Point of Concentration nodes) to
provide different interface variants and functionality. This allows connectivity to be decoupled from RNC
capacity providing a more efficient transport solution.
Alcatel-Lucent UTRAN introduces two new models of ATM Transport Node(s), namely the 7670 RSP and the
7670 ESE.
7670 RSP is primarily used in Large-to-Medium size RNC location (multiple RNC(s)) to provide high density
OC-3/STM-1 ATM/IMA termination (SDH mux).
The 7670 ESE is used in Small-to-Medium size RNC location (single RNC) to provide high density T1/E1
ATM/IMA termination.
This switch is based on a 14-slot shelf, 2 slots (X and Y) being reserved for Control Complex cards, and 12
slots (1 to 12) for Interface cards that is E1 card with 32 E1 ports, STM-1 links are provided by one ECC card
and additional STM-1 cards.

Section 3 Pager 9
UTRAN Elements

Section 3 Pager 10
3 UTRAN Elements

UTRAN Elements
What about the Alcatel-Lucent Node B?

Section 3 Pager 11
Role of the Node B
Node B Functions
Radio transmission/reception
Mapping between transport channels and physical channels (Uu)
Transport of radio channel over the Iub
Power control (inner closed loop)

UTRAN Elements
The main role of the Node B is to convey transport channels between the User terminals and the RNC.
To do that, transport channels are mapped on physical channels on the radio interface (over the Uu
interface), and are mapped on ATM cells or Ethernet frame between the Node B and the RNC (over the
Iub interface).
Moreover, the Node B is involved in the fast closed loop power control, very efficient compared to the
open loop power control in GSM. More particularly, the Node B performs a part called the inner loop
power.

Section 3 Pager 12
Node B Functional Description
45W – 60W amplifier CDMA baseband signal processing Common/Control functions,
3-carrier capable Dynamically shared 6 carriers OAM management, switching, routing
Node B
RF Block Digital Block
TMA DDM MCPA

(option)
xCEM
Iub
TMA DDM MCPA RNC

(option) xCCM
TMA DDM MCPA

(option) xTRM
RF interconnection panel Modulation/Demodulation, Power control/detection

3x15MHz Transmit Chains, 6x10MHz Receive Chains

UTRAN Elements
The generic Node B architecture is made up of several types of module, each performing specific
functions.
The xCCM provides the Node B with control and data routing functions related to the Iub interface,
call processing, data switching and routing, OAM management.
The xCEM achieves digital signal processing for both Tx and Rx paths. The xCEM is able to manage 256
Channel Elements (CEs).
The xTRM achieves modulation/demodulation, power control and clock synchronization. The xTRM
supports up to 2 carriers in 1 module.
The Multi Carrier Power Amplifier (MCPA) boosts the RF signal delivered by the TRM. 2 TRMs can be
connected to a single PA for redundancy issues.
The Dual Duplexer Module (DDM) consists in a double duplexer-LNA chain: one for the main path and
the other for the diversity path. This module provides two functions: isolation among the transmit signals
and receive signals and also filtering of the transmit and received signals thus reducing the interfering
signals.

Section 3 Pager 13
Node B Functional Description with TRDU
TRDU = Modulation/Demodulation + Amplifier + RF Antennae interconnection
Node B
RF Block Digital Block
TMA TRDU
(option)
xCEM
Iub
TMA TRDU RNC

(option) xCCM
TMA TRDU
(option)

UTRAN Elements
The evolution of the Node B architecture reduces the number of modules, by integrating several
functions into one module. The Transmit Receive Digital Unit (TRDU) integrates the function of the
xTRM (that is modulation/demodulation, Digital to Analogic conversion), the Amplification function of
the MCPA and the function of the DDM (RF connection) into a single module.

Section 3 Pager 14
Alcatel-Lucent 9300 W-CDMA Node B Product Family
Standard Node B Solutions Distributed Node B Solutions
Macro
Indoor & Outdoor
d2U
RRH 40W
Street
Compact
RRH 60W
Multi-Standard
BTS (2G/3G)

UTRAN Elements
In the Alcatel-Lucent Portfolio, a large range of Node B product exists. There is always a Node B solution
whatever the coverage or the capacity issue the operator is facing.
The Macro BTS solution allows to provide high capacity and large coverage with indoor and outdoor
solutions. The compact Node B solution also exists when the operator is facing space issue on site.
The Distributed Node B solutions allow to optimize power and capacity at the antenna when facing
coverage issue such as high feeder length or provide hot spot for indoor location solutions.

Section 3 Pager 15
9311 Macro Node B Portfolio
High capacity and coverage

9311 Macro Node B for suburban, rural, 9311 Macro Node B
(Outdoor) highways & rooftop areas (Indoor)
Characteristics
High capacity: Large coverage
3 sectors x 4 carriers 640 CEs (future 1536)
6 sectors x 2 carriers
High power (Up to 6 x 45W
– 60 W)
Rx and Tx Diversity

UTRAN Elements
The 9311 Macro Node B family supplies an indoor solution with the 9311 Macro Node B (Indoor) and an
outdoor solution with the 9311 Macro Node B (Outdoor). Both provide high capacity, large coverage,
support of high power solution (up to 60W) and full UMTS frequencies range (2100 or 900).

Section 3 Pager 16
Outdoor Compact Node B Portfolio
DAMPER
3U User space (incl. ext Alarms & PCM LP) C USER ICO
TRDU
DIGITAL MODULES (4 xCEM-U + 1 xCCM-U) (up to 3)
FANS & HEATER

with damper
Power supply unit
FREE SPACE for battery

mangt and airflow
Outdoor Compact
Node B
(9312 Compact) BATTERY SPACE
Interfaces BATTERY SPACE
Installation plinth

UTRAN Elements
For locations with limited space, where installation of standard macro equipment is difficult, the 9312
Compact Node B is preferred, while providing similar high capacity and large coverage. This Node B is also
called 9312 Compact.
The digital block is composed of xCEM and xCCM in a compact design, called xCEM-U and xCCM-U.
The radio block is composed of TRDU modules which provide the necessary Antennae connections for
typical tri-sectors configuration.

Section 3 Pager 17
Smart Compact Node B
TRDU Subrack (11U)

including 1U Air inlet
1..6 TRDU
1..2 Interconnection unit
FAN Unit
Airflow (1U)
PCM Protection (1U Optional)
d2U Subrack (2U) 1..3 xCEM-u

1 xCCM-u
External Alarms (1U Optional)

UTRAN Elements
The 9312 Compact Indoor is built around two main subracks: the digital shelf (9326 d2U) and a Radio
Frequency subrack (TRDU Subrack).

Section 3 Pager 18
Distributed Node B Solution
Interest
The Remote Radio Head provides operators with a flexible solution to address:
specific coverage issues (high feeder length),
specific space issues (Node B located far from the antenna),
specific capacity issues (by placing the radio heads close to where the traffic is).
RRH

UTRAN Elements
The radio coverage of specific environments such as dense urban areas or high buildings can cause real
difficulties at several levels.
Cells coverage can be drastically degraded because of the power loss due to the length of the feeders
since the Node B is generally located far from the antennas (the Node B is in the basement and the
antennas are on the roof of the buildings).
You can guess, that this power loss can also have a significant impact on the cells capacity since a part of
downlink traffic power is lost before reaching antennas.
To address these issues, Alcatel-Lucent offers the possibility to use the Remote Radio Head.
The RRH is located close to the antenna (implying no feeder losses) and is connected to a Digital Node B
through optical fiber, which hosts the Base Band boards and the transmission interfaces (to allow high
traffic capacity). Several remote parts can be connected to one Digital Node B.

Section 3 Pager 19
Distributed Node B Portfolio for all Environments
9341 RRH40-21 9341 RRH40-08 (850 MHz) 9326 Digital 2U Node B

(2100 MHz and AWS)
(9326 d2U)
RRH40-19 (1900 MHz)
High power compact High power compact

RRH: 40W/60W, RRH: 40W/60W,
3 carriers 2 carriers
230W power 34 litres – 22 kg
consumption
24 litres – 19 kg

UTRAN Elements
For locations with limited space such as urban rooftops, at top mast near the antenna or water tower sites,
installation of a Distributed Node B is the solution.
In the Alcatel-Lucent Distributed Node B portfolio, you can use a 9326 Digital 2U Node B (9326 d2U), which
is a rackable solution that can be integrated into existing cabinets for easy and quick deployments and used
in combination 9341 RRH modules.
9341 Remote Radio Head (9341 RRH) enables remote placement of the radio modules and filter functions
used near the radiating antenna, the rooftop or at ground level, connected with any digital unit via optical
fibers.

Section 3 Pager 20
9326 Digital 2U Node B (d2U)
A high capacity and density unit that can Characteristics

Indoor environments
be used in combination with RRH units, Compact design (2U height)
the Node B and multi-standard cabinets in and a min weight (<8 Kg)
dense areas with site space limitations Supports up to 6 RRHs in
star via optical fiber
Up to 6 fibers, i.e. 6 sectors
x 2 carriers or 3 sectors x 4
carriers
Up to 3 xCEM-U (768 CEs)
GSM Modules
In a GSM Cabinet
Iub
9326 d2U
9341 RRH 9326 d2U

UTRAN Elements
The d2U is a digital Node B taking 2 User Space slots; Easy to install with its compact design, the d2U can be
linked up to 6 RRHs via optical fibers. The d2U provide high capacity with its xCCM board allowing high
traffic (up to 8 E1/T1 and 1 Fast Ethernet port) combined with up to 3 xCEM boards allowing a maximum
capacity of 768 CEs.
There is no need for an additional base station as installation is possible within existing space or inserted in
a standard 19-inch rack (such as Macro in GSM sites).
The integration into a GSM cabinet is a very easy way to migrate a GSM site to a site with 2G and 3G
capability. This Multi-standard Distributed BTS solution just requires a set of RRHs connected to a d2U
module inserted in the 2G cabinet.

Section 3 Pager 21
Multi-Standard BTS Indoor & Outdoor
Description
Capacity:
Up to 12 TRX with Twin TRX
Up to 4 carriers 3 sectors
Up to 768 CE, more than 80 Mbps of HSPA
traffic
VALUE
2G modules Investment protection:
Capitalize on existing assets
No need for new site acquisition
Same KPIs and features as Macro Node B
UMTS RF
Modules
(TRDU)
Reuse GSM sites, cabinets

Reuse feeders/antennas (900 MHz)
d2U

UTRAN Elements
When re-use of GSM site and feeders is possible, we will prefer to implement the Multistandard BTS
solution without additional RRHs.
In such a case the RRHs modules are replaced by up to 6 TRDU modules, providing a full Macro Node B
capacity within an existing GSM cabinet (Indoor or Outdoor).

Section 3 Pager 22
Quiz maker

UTRAN Elements

Section 3 Pager 23
End of Module
UTRAN Elements

UTRAN Elements

Section 3 Pager 24
4
Section 4
O&M Principles
O&M Principles
9300 W-CDMA
3JK11632AAAAWBZZA1
Edition 1

Section 4 Pager 1
Objectives
Objectives:
To be able to describe the UTRAN operation and maintenance principles.
Content:
4.1 O&M Functions
4.2 O&M Architecture
4.3 O&M Software
4.4 O&M Menus

O&M Principles
In this last chapter, we are going to see the functions of the operation and maintenance managed by the
Wireless Management System. Then, we'll discover the functional and hardware architecture of the
operation and maintenance center. We'll also have a look at the software interfaces for operation and
maintenance. And finally we will briefly turn towards the menus of the WMS.

Section 4 Pager 2
4 O&M Principles
4.1 O&M Functions

O&M Principles
What are the functions and the domains of application of the operation and maintenance?

Section 4 Pager 3
4.1 O&M Functions
High-Level Functional Architecture
Wireless Management System (WMS)
Interfaces
Administration
Faults & Events
Configuration
Performance
Security
Hardware & Framework

O&M Principles
O&M standard domains are divided into several functions: faults, configuration, performance, security
and administration.
The Faults functions allow you to detect and visualize in real time a problem in order to react quickly, to
filter and sort the active alarms according to criteria (e.g. alarm severity), with the ability to navigate in
the equipment view.
The Configuration functions provide upload of the network configuration (snapshot), facilities to manage
a large amount of data (through templates for examples. Note that 1200 Node Bs and 10 RNCs represent
over 1 Million parameters. The Configuration functions also allow you to download a new configuration
and offer facilities to import/export a configuration through 3GPP interfaces.
With the Performance functions, you can get counters from the network (granularity period), create
indicators and receive QoS warning on threshold violation. You can also create reports graphs and tables
and store the counters and indicators in a database for long time in order to perform QoS statistics
evaluation.
Security functions avoid intrusion.
And finally the Administration functions define rights to each user for the network access and functional
access domains.

Section 4 Pager 4
4 O&M Principles

O&M Principles
Now, let’s have a look at the functional and hardware architecture of the operation and maintenance
center.

Section 4 Pager 5
O&M Architecture
WMS

O&M Principles
The functionality of the WMS solution is distributed between two servers: the main server and the NPO
server. These two servers share the objective of FCAPS: Fault, Configuration, Accounting, Performance
and Security management.

Section 4 Pager 6
Main Server Functions
Access Control
Backup
& Restore Data
Performance
Management
Configuration
Management
WMS Client
Fault Main Server

Software
Management Management

O&M Principles
The main server is designed to handle Fault Management, Configuration Management, Performance
Management, Software Management, Access Control as well as Back-up & Restore data (for Configuration
/ Fault data).

Section 4 Pager 7
Main Server Hardware
Small-scale/pilot network Medium-scale network

Mid-range server
Sun® Netra 240

Sun StorEdge 3120
2 CPUs/1500Mhz Sun Fire V890
8GB RAM 4 CPUs/1500Mhz
2x146GB 15kprm disks (RAID1) 16GB RAM
12x146GB 10krpm disks (RAID1)
Large-scale network
High-end server
PC clients
CPU Pentium IV 2.8GHz
1GB RAM
Sun Ultra45 clients

1600Mhz, 2G RAM, 250GB disk
Sun Fire E4900
8/12 1800Mhz CPUs
32/48GB RAM
16/32 x 146GB 4Gbps Fiber Channel disks,
15Krpm

O&M Principles
In order to scale to various network sizes, 3 WMS hardware configurations have been defined.
In the first configuration, the Sun Netra 240 server (1 Main Server) is intended for the management of small
packet/voice core networks or UMTS trials, up to 1800 3G cells.
In the second configuration, Sun Fire 890 servers (1 or 2 Main Servers) are intended for the management of
UTRAN and core network, up to 4200 3G cells.
In the third configuration, Sun Fire E4900 servers (1 or 2 Main Servers) are intended for the management of
large networks, up to 18000 3G cells.
WMS servers are using Solaris 10 as Operating System.

Section 4 Pager 8
NPO Functions
Performance Data
Reporting Mediation
Data
Collection
WMS Client
NPO Server

O&M Principles
Wireless Network Performance Optimizer (the NPO for WCDMA) is the next generation performance
reporting product of Alcatel-Lucent. It is based on the field-proven RNO product, which has been
recognized as one of the most efficient performance reporting product for wireless access products. For
the quality of service analysis, and for back-office activities like network optimization and network
planning, periodical measurements on radio traffic, radio resource usage, transmission and handover
behavior are collected from the network elements through WMS.
The network-wide QoS analysis relies on the regular collection of the same performance counters on all
managed Network Elements. Based on the counters, indicators are calculated and stored by NPO for up
to 1 year.
The optimizer can select and launch predefined or user-defined QoS report based on those indicators.

Section 4 Pager 9
Extended Interface for Integration into MS-Portal
Multi-Standard Portal
MS Portal
Interface
with MS-Portal
MS-SUP MS-NPO
OMC-R WMS
GSM Access UMTS Access

O&M Principles
Customer must have a common application to supervise 2G & 3G access OMC-R. This application is called
MS-Portal and is interfaced to WMS and 2G OMC-R.
MS-Portal allows you to use a common interface (called MS-SUP) for 2G and 3G network supervision.
This application also allows you to use a common interface ( which is called MS-NPO) to optimize and
analyze the Quality of Service of 2G and 3G network.

Section 4 Pager 10
4 O&M Principles
4.3 O&M Software

O&M Principles
Now, let’s have a look at the software interfaces for operation and maintenance.

Section 4 Pager 11
4.3 O&M Software
WMS Tool Set for Managing the RAN
Characteristics
Carrier grade scalable solution, field
hardened solution with large deployed
base
Powerful visualization tools and
monitoring capabilities allow rapid fault
detection and isolation
Optimized configuration workflows
enable fast roll-out and easy re-
configuration (e.g. plug and play, NodeB
reparenting)
E2E highly flexible & pre-defined KPIs &
reporting features with alarm on
threshold capabilities
Secure the infrastructure
(Authentication, Encryption, Audit logs)

O&M Principles
In front and back offices, the network administrators can use WMS to evaluate and to solve faults. WMS
with its specialized applications offers the network administrators the ability to configure, monitor and
troubleshoot efficiently the network.

Section 4 Pager 12
4.3 O&M Software
Configuration Manager
Various Ways of Configuring UTRAN

Off-line configuration: Bulk & complex configuration and planning operations.
On-line configuration: Minor and "on the fly" configuration changes.
Off-line Configuration On-line Configuration Multiple / Flexible
interfaces
3GPP bulkCM
Manager &
associated
CM OSS WPS (Option) On-line editor WICL productized tools
to match
all your operational
3GPP XML Object WICL needs
BulkCM IRP interface Editor MMI scripting

O&M Principles
For the UMTS Access Network, WMS provides several configuration interfaces adapted to different types
of operations. CM XML is the Alcatel-Lucent proprietary main interface for configuration.
The operator can provision a file of configuration called WorkOrder with an offline tool WPS (Wireless
Provisioning System). The WorkOrder (WO) can be imported on the WMS Main server through an XML
interface, in order to be activated on the live network thanks to the Session Manager.
The operator can also perform on-line modifcation by using the on-line editor GUI or via script with the
WICL interface (WIreless Command Line)
A snapshot of the live network with the up to date modifications can be then retrofit back into the
offline tool (WPS) through the XML interface again.

Section 4 Pager 13
4.3 O&M Software
WPS
Planning
Provisioning activities Activation activities
activities WPS is an option.
WPS colocated
on W-NMS clients
Cell Planning
XML XML Work-orders High performance

consolidation Flexible usage
Easy integration
Transmission Flexible architecture
Planning Standalone WPS Publish
XML / Retrieve
Data
XML
Main Server
Repository function for XML with Workspace
OSS
multi-user repository
XML collaboration Publish Configuration
/ Retrieve activation
Data

O&M Principles
The WPS for Access Network tool, or WPS Access, is the Alcatel-Lucent UMTS Access Network
configuration tool. Based on the WPS platform, this optional product is an external offline application of
the Alcatel-Lucent Access OAM software. Besides the basic WPS capabilities, WPS for Access Network
delivers added-value access-specific configuration capabilities, based on Alcatel-Lucent expertise in
UTRAN configuration.
WPS Access covers the Node, the RNC, the cell neighboring and the Iu interfaces configuration.

Section 4 Pager 14
4.3 O&M Software
Performance Monitoring Products
BASE PRODUCT OPTIONAL PRODUCTS
Network Performance
Optimizer (NPO)
UTRAN
Counters
Counters CallTraces
Wireless Management
System (WMS)
Radio Frequency
Optimizer (RFO)
CallTraces
Wireless Quality
Analyzer (WQA)
CallTraces
O&M Principles
Alcatel-Lucent allows to analyze and optimize the network Quality of Service, thanks to a large set of
powerful post-processing tools.
In this performance reporting cahin, WMS collects and stores the data. Then NPO allows to display QoS
reports. Next RFO analyzes user call trace to better troubleshoot call failure, when WQA optimizes the
cell neighboring (by adding missing neighbors or removing unused links for example) based on
geographical call traces.

Section 4 Pager 15
4 O&M Principles
4.4 O&M Menus

O&M Principles
Let me now briefly introduce you to the operation and maintenance possibilities with a few screenshots
of the WMS and NPO menu.

Section 4 Pager 16
4.4 O&M Menus
Launch NSP

O&M Principles
The Network Services Platform (NSP) is a network management platform that enables you to manage your
network from within a single user interface.
A WMS client can be installed on any PC, thanks to the easy to implement NSP interface. NSP can be
installed and launch from a simple web browser.

Section 4 Pager 17
4.4 O&M Menus
Main Window

O&M Principles
In the main Window, a menu bar provides standardized functional grouping of menus and dialogs boxes.
This consistent user environment increases efficiency, driving down operational costs.
The Resource Browser provides a layered, map-based representation of the network.
The Navigator provides an hierarchical view of the network organized in a Windows ExplorerTM style tree,
based on NE groups. The Navigator also provides a summary count of alarms at each level in the network
hierarchy.
The Network Banner provides an "always-on" summary of active alarms in the network.
This main window also provides System Administration tools.

Section 4 Pager 18
4.4 O&M Menus
Fault & Event Management
Ease of Operation and Integration Enhanced Alarm Management Efficient Troubleshooting

Layouts Alarm severity change On-line help
Groups & sub-groups Inhibition In-context launch
easy navigation Delay Find capabilities
sort capabilities Actions on alarm Pass through
In-context CM launch Forward to e-mail/SMS
3GPP interface Maintenance mode
Toggling alarms
Alarm Correlation
Powerful UTRAN First Alert,

Troubleshooting and Alarm
Statistics.
Alarm Correlation
Topological View
Matrix View
NE Shelf level Display Service View

Grid View
O&M Principles
The Fault Management can be performed at network level through a Grid view (each NE is represented by a
small icon), a Matrix view (sorting by RNC), or a Topological view (map view). The icon color indicates the
highest severity alarm reached on the NE.
The operator can go further into investigation through the Alarm Manager (to get the list of alarms) and the
NE shelf-level display (for equipment monitoring purposes).

Section 4 Pager 19
4.4 O&M Menus
WMS On-Line Editor
Attributes
Selection
Objects
Selection
Commands
buttons
Attributes
Modification

O&M Principles
Object editors are available from the WMS NSP GUI and are designed to support operations personnel
making real-time adjustments to NE configuration, for either tuning or troubleshooting activities.
These default editors allow you to display multiple objects of any network element type (Node B, RNC C-
Node and I-node). They provide the user with information regarding the parameter setting operation
(constraints, status, and so on). If the parameter modification implies an impact on the network, a
special caution message is displayed to warn the user.

Section 4 Pager 20
4.4 O&M Menus
Configuration Management - WPS
Highly Flexible for Easy Integration Enable Fast Network Fulfilment Significant OPEX Savings
XML interfaces & Reconfiguration Checks with auto fix
Work orders Ease of use Dataset
Import/export capabilities Bulk provisioning Task-oriented assistants
Tabular editor Hyperlink navigation
Templates Automated
Copy/paste synchronization
Flexible, powerful and Object list
reliable configuration
solution Filtering 1600 Node Bs and 10
Network Reconfiguration RNCs represent over
Procedures (e.g. Scrambling 3.5 Million parameters.
Code Plan Update)
Intuitive Wizards Flexible toolset Fast and Secure configuration

O&M Principles
In order to configure the thousands of NEs in a typical UMTS access network, WPS provides high-level task-
oriented configuration wizards that simplify the provisioning task by relying on extensive use of templates
and embedded engineering rules. 60 to 90% of parameters are automatically filled.
Wizards are implemented in a task-oriented approach, allowing de-correlated tasks to be completed
independently. The task breakdown reflects a typical operator’s organization and allows several
departments to work on different aspects on the same nodes.

Section 4 Pager 21
4.4 O&M Menus
NPO Overview
Properties
& Functions
Network resources
management
Cartography, Diagnosis,
Tuning Session
& Reports Browser
Views Browser

O&M Principles
The performance management user interface of NPO is very intuitive. Most of the operations can be done
through the drag-and-drop mechanism or with the help of menu bars and toolbars.
The main NPO user interface (analysis desktop) is composed of four main areas.
In the Network Resources Management area, Topologies of the radio resources (cells), as well as the
physical resources (such as the BTS, Node B, BSC and RNC) are displayed in tree gadgets and can be
selected from there.
In the Properties and Function area, the browser allows the operator to select QoS indicators, QoS
counters, logical / design parameters, or views / reports (grouped into families).
The View Browser is the target place to drag and drop network resources and functions. This browser
displays values of logical / design parameters, indicators, and counters in tabular and graphical mode.
The Report Browser is the target place to drag and drop network resources and QoS report. A report is
composed of several views, each displaying a set of defined indicators or parameters for a user defined
report period.

Section 4 Pager 22
4.4 O&M Menus
NPO Facilities
Click
Drag and Drop
Drag and Drop

O&M Principles
Many operations inside the Analysis Desktop can be done using drag and drop.
Let's suppose an operator wants to compare the call failure that occurred in multiple cells the day
before. The operator then selects a set of cells, selects a QoS report relative to the selected cell (Call
Drop report) and drags and drops the selection into the Report Browser.
The Call Drop Indicators listed in the report are displayed in a graphical mode. The report can then be
saved into an Excel spreadsheet format.
In a similar operation, parameters, counters and indicators selection can be dragged and dropped in the
View Browser part to be displayed.

Section 4 Pager 23
Quiz maker

O&M Principles

Section 4 Pager 24
End of Module
O&M Principles

O&M Principles

Section 4 Pager 25
UTRAN Solution Description -
Abbreviations
3JK11633AAAAWBZZA1
All Rights Reserved © 2007, Alcatel-Lucent
3JK11633AAAAWBZZA1
Page 1
Blank Page
2

3JK11633AAAAWBZZA1
Page 2
Abbreviations and Acronyms
3
Ω ohm
µs Switch to notes view!
microsecond
2G second Generation
3G third Generation
3GPP third Generation Partnership Project
A
AAL ATM Adaptation Layer
AAL2 ATM Adaptation Layer 2
AAL5 ATM Adaptation Layer 5
AMR Adaptative Multi Rate
API Application Program Interface
ARQ Automatic Repeat Request
ATM Asynchronous Transfer Mode
B
BB Building Block
BMC Broadcast/Multicast Control
BPSK Binary Phase Shift Keying
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
BW BandWidth
C
CAC Call Admission Control
CAPEX CAPital EXPenditure
CCM Core Control Module
CE Channel Element All Rights Reserved © Alcatel-Lucent 2007
CEM Channel Element Module

CID Connection Identifier
CN Core Network
CORBA Common Object Request Broker Architecture
CP Control Processor
CRNC Controlling RNC
CS Circuit Switching
CSCN Circuit-Switched Core Network
CT Call Trace
D
DA Device Adapter
DCCH Dedicated Control Channel
DCH Dedicated Channel
DCPS Dual Core Packet Server
DDM Dual Duplexer Module
DPCCH Dedicated Physical Control Channel
DSP Digital Signal Processor
DTCH Dedicated Traffic Channel
E
E Erlang
E-AGCH E-DCH Access Grant Channel
E2E End-to-End
ECC Error Correction Coding
E-DCH Enhanced Dedicated Channel
E-DPCCH E-DCH Dedicated Physical Control Channel
E-DPDCH E-DCH Dedicated Physical Data Channel
E-HICH E-DCH Hybrid ARQ Indicator Channel
EQL Extensible Query Layer
E-RGCH E-DCH Relative Grant Channel
ESE Edge Service Extender
3JK11633AAAAWBZZA1
Page 3
Abbreviations and Acronyms [cont.]
4
F

FCAPS
SwitchFault,
to notes view!
Configuration, Accounting, Performance and Security
FDD Frequency Division Duplex
FMBB Fault Management Building Block
FP Functional Processor
FRU Field Replaceable Unit
G
GGSN Gateway GPRS Support Node
GigE Giga Ethernet
GMSC Gateway MSC
GPRS General Packet Radio Service
GSM Global System for Mobile communications
GTP GPRS Tuneling Protocol
GUI Graphical User Interface
H
HARQ Hybrid ARQ
HEC Head Error Control
HLR Home Location Register
HO Handover
HSDPA High-Speed Downlink Packet Access
HS-DPCCH High-Speed Dedicated Physical Control Channel
HS-DSCH High Speed Downlink Shared Channel
HSPA High-Speed Packet Access
HS-PDSCH High-Speed Dedicated Physical Data Channel
HS-SCCH High-Speed Single-Cell Control Channel
HSUPA High-Speed Uplink Packet Access
I
IMA Inverse Multiplexing for ATM
IP Internet Protocol
IPSec IP Security
ITU International Telecommunications Unit
Iu-FR Iu Frame Protocol
Iub interface between Node B and RNC
Iub-FP Iub Frame Protocol
Iu-CS interface between RNC and MSC
Iu-FP Iu Frame Protocol
Iu-PS interface between RNC and SGSN
Iur interface between RNC and RNC
Iur-FP Iur Frame Protocol
J
J2EE JAVA 2 Enterprise Edition
K
kbps kilobits per second
KPI Key Performance Indicator
L
LAC Location Area Code
LAN Local Area Network
LNA Low Noise Amplifier
3JK11633AAAAWBZZA1
Page 4
5
M

M A AT SwitchMto
U SEnotes
A nalysisview!
Ap plication T ie r
MAC M e dium A ccess Control layer
M A C -b M A C b roadcast
M A C -c M A C con trol
M A C -d M A C d ed icated
M A C -e M A C e ntity
M A C -hs M A C h igh sp eed
M A C -sh M A C shared
M 3U A M T P-3 U ser Ad ap tation Laye r
M b ps M e gab its pe r second
MBS M u lti-stan dard Base Station
MCPA M u lti C arrier P ow er Am plifier
ME M ob ile Equipm en t
MHz M e ga H ertz
MMI M an -M ach in e In terface
ms m illise con d
M SC M ob ile services Sw itchin g C e nter
M SS M u ltiService Sw itch platform
MTP M e ssage T ran sfe r Part
N
N BAP N ode B Ap plication P rotocol
NDS N etscap e D ire ctory Service
NE N etw ork Elem en t
N PA N etw ork Perform ance An alyze r
N PO N etw ork Perform ance O p tim ize r
N SP N etw ork Se rvices Platform
O All Rights Reserved © Alcatel-Lucent 2007
O&M O pe ration and M ainte nance

O AM O pe ration, Adm inistration and M aintenan ce
O C -3 O ptical Carrie r-3
O IM O ptical In te rface M od ule
OMC O pe ration and M ainte nance C e nter
O M C -R O pe ration and M ainte nance C e nter – R adio
O PEX O Pe rational EXp en ditu res
O SS O pe ration Supp ort System
O V SF O rthogonal V ariab le Spre ad ing Factor
P
PA P ow er Am plifier
PC P ersonal C om pu te r
PC M P ulse C ode M odulation
PD C P P acket D ata C onvergen ce Protocol
PM P hysical M e diu m
PoC P oint of C oncen tration
PO H P ath O verH ead
PS P acket Sw itch in g
PSC N P acket-Sw itche d C ore N etw ork
PSFP P acket Se rver Fun ctional P rocessor
PST N P ublic Sw itche d Te leph one N e tw ork
Q
Q AM Q uad rature Am p litud e M odu lation
Q oS Q uality of Service
Q PSK Q uad rature Ph ase Shift Keying
3JK11633AAAAWBZZA1
Page 5
6
R
RAB SwitchRadio
to notes view!
Access Bearer
RANAP Radio Access Network Application Protocol
RF Radio Frequency
RFO Radio Frequency Optimizer
RLC Radio Link Control
RNC Radio Network Controller
RNO Radio Network Optimizer
RNP Radio Network Planning
RNSAP Radio Network Subsystem Application Protocol
RRC Radio Resource Control
RRH Remote Radio Head
RRM Radio Resource Management
RSP Routing Switch Platform
Rx Reception
S
SAP Service Access Point
SAR Segmentation and Reassembly
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SF Spreading Factor
SGSN Serving GPRS Support Node
SGW Security Gateway
SIM Subscriber Identity Module
SMS Short Message Service
SOH Section OverHead
SQL Structured Query Language All Rights Reserved © Alcatel-Lucent 2007
SRB Signaling Radio Bearer
SRNC Serving RNC
SRNS Serving Radio Network Subsystem
STM-1 Synchronous Transport Module level 1
SW SoftWare
T
TC TransCoder
TDD Time Division Duplex
TE Terminal Equipment
TMN Telecommunications Management Network
TRB Traffic Radio Bearer
TRDU Transmit Receive Digital Unit
TRM Transmit/Receive Module
TTI Transmission Time Interval
Tx Transmission
U
UDP User Datagram Protocol
UE User Equipment
UICC UMTS Integrated Circuit Card
UL UpLink
UMTS Universal Mobile Telecommunications System
USIM UMTS Subscriber Identity Module
UTRAN UMTS Terrestrial Radio Access Network
Uu interface between UTRAN and UE
V
VC Virtual Circuit
VCI Virtual Circuit Identifier
VLR Visitor Location Register
VP Virtual Path
VPI Virtual Path Identifier
3JK11633AAAAWBZZA1
Page 6
7
W
W SwitchWatt
to notes view!
WCDMA Wideband Code Multiple Division Access
WICL Wireless Internet Common Language
WiMAX Worldwide interoperability for Microwave Access
WMS Wireless Management System
WPS Wireless Provisioning System
WQA Wireless Quality Analyzer
X
XML eXtended Markup Language
3JK11633AAAAWBZZA1
Page 7
8
End of Module
3JK11633AAAAWBZZA1
Page 8
Last But One Page
1 All Rights Reserved © Alcatel-Lucent @@YEAR

@@PRODUCT
@@COURSENAME
All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1
All rights reserved © Alcatel-Lucent @@YEAR
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved © Alcatel-Lucent @@YEAR
@@COURSENAME - Page 2

TMO18024 - 9300 WCDMA UA06 UTRAN Description

Uploaded by

Copyright:

Available Formats

You might also like

TMO18024 - 9300 WCDMA UA06 UTRAN Description

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TMO18024 - 9300 WCDMA UA06 UTRAN Description

Uploaded by

Copyright:

Available Formats

9300 W-CDMA

UA06 UTRAN Solution

All Rights Reserved © Alcatel-Lucent 2009

All rights reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

2 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All rights reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

4 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

3. Topic/Section is Positioned Here

5 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

6 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

Welcome to UA06 UTRAN Solution Description

Upon completion of this course, you should be able to:

functions and the architecture of a UTRAN network

7 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

8 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

9 All Rights Reserved © Alcatel-Lucent 2009

Where you can get further information

If you want further information you can refer to the following:

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

10 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Did you meet the following objectives ?

Yes (or No (or

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

Yes (or No (or

12 All Rights Reserved © Alcatel-Lucent 2009

Thank you for your answers to this questionnaire

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

12 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

13 All Rights Reserved © Alcatel-Lucent 2009

What is the UTRAN and how is it located in a UMTS system?

All Rights Reserved © Alcatel-Lucent 2009

14 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Core Network Functions (Reminder)

15 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

16 All Rights Reserved © Alcatel-Lucent 2009

Now let’s look at the functions of the UTRAN.

All Rights Reserved © Alcatel-Lucent 2009

12 All Rights Reserved © Alcatel-Lucent 2009

13 All Rights Reserved © Alcatel-Lucent 2009

14 All Rights Reserved © Alcatel-Lucent 2009

15 All Rights Reserved © Alcatel-Lucent 2009

16 All Rights Reserved © Alcatel-Lucent 2009

17 All Rights Reserved © Alcatel-Lucent 2009

18 All Rights Reserved © Alcatel-Lucent 2009

19 All Rights Reserved © Alcatel-Lucent 2009

1 10 All Rights Reserved © Alcatel-Lucent 2009

1 11 All Rights Reserved © Alcatel-Lucent 2009

1 12 All Rights Reserved © Alcatel-Lucent 2009

1 13 All Rights Reserved © Alcatel-Lucent 2009

1 14 All Rights Reserved © Alcatel-Lucent 2009

1 15 All Rights Reserved © Alcatel-Lucent 2009

1 16 All Rights Reserved © Alcatel-Lucent 2009

1 17 All Rights Reserved © Alcatel-Lucent 2009

1 18 All Rights Reserved © Alcatel-Lucent 2009

1 19 All Rights Reserved © Alcatel-Lucent 2009

1 20 All Rights Reserved © Alcatel-Lucent 2009

1 21 All Rights Reserved © Alcatel-Lucent 2009

1 22 All Rights Reserved © Alcatel-Lucent 2009

1 23 All Rights Reserved © Alcatel-Lucent 2009

1 24 All Rights Reserved © Alcatel-Lucent 2009

1 25 All Rights Reserved © Alcatel-Lucent 2009

1 26 All Rights Reserved © Alcatel-Lucent 2009

1 27 All Rights Reserved © Alcatel-Lucent 2009

1 28 All Rights Reserved © Alcatel-Lucent 2009

1 29 All Rights Reserved © Alcatel-Lucent 2009

1 30 All Rights Reserved © Alcatel-Lucent 2009