Umts Overview

System Information: UMTS Overview
© 2002 -2004 Motorola, Inc. 68P02905W21-B

All Rights Reserved 02-Jun-2004
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to
copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in
accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of
the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language,
in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions
in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve
reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to
notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein;
neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
02-Jun-2004
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Resolution of service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Feature references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Failure to comply with warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Caution labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Ordering manuals and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR amendment record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1: Introduction to this manual and Motorola documentation

Overview of the contents of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contents of 68P02905W21: UMTS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Chapter 2: Overview of UMTS

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Topics in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
68P02905W21-B i
02-Jun-2004
Contents
What is UMTS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

UMTS services for the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
UMTS technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Overview of the UMTS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Typical UMTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
UMTS network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
UTRAN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
UTRAN components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Radio Network Controller (RNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
User Equipment (UE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Operations and Maintenance Centre-UTRAN (OMC-U) . . . . . . . . . . . . . . . . . . . . . . . 2-9
Core Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Core Network (CN) components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Gateway GPRS Support Node (GGSNu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Serving GPRS Support Node (SGSNu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Mobile services Switching Centre (MSCu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Location Registers (LR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Operations and Maintenance Centre - Transportation network (OMC-S/T) . . . . . . . . . . . . . . 2-12
Network Management Centre (NMC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Core Network subsystems (non-network elements) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Interworking Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Echo Canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Billing Centre. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Cell Broadcast Centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
UMTS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Introduction to this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Overview of UMTS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
UMTS functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Core Network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
NMC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Location Register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
UTRAN network protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
OSI/protocol relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
ITU-TSS signalling system 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
E1/STM-1 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
STM-1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Wideband Code Division Multiple Access (W-CDMA) . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Introduction to W-CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Cocktail party analogy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
W-CDMA techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Advantages of W-CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
W-CDMA features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
UMTS frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Worldwide spectrum allocation for IMT-2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
European frequency allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
ii 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Contents
Mobile services Switching Centre for UMTS (MSCu) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
MSCu functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Gateway MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
MSCu flexible design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
MSCu interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Iu-CS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Layered signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Location Register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Call control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Emergency calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Short Message Service (SMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Security procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Local registration and call handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Inter-MSC handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Equipment Identity Register (EIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Home Location Register (HLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Authentication Centre (AUC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Authentication and Key Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Distribution of authentication data from HE to SN . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Authentication and Key Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Visited Location Register (VLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Controlling LAIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Controlling MSRNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Allocating handover numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Allocating TMSI numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Call handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Network Management Centre (NMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
National management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Monitoring equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Monitoring routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Managing traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Simulating the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Introduction to QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
QoS operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
QoS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Migration from GSM/GPRS to UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Introduction to UMTS migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Migration process GSM to UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Chapter 3: Functional description of UTRAN components

Introduction to this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Overview of this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
UMTS Terrestrial Radio Access Network (UTRAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Introduction to the UTRAN components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Radio Access Network (RAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Introduction to RAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
RAN links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
68P02905W21-B iii
02-Jun-2004
Contents
Typical RNS layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
RNS functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Non-imperative handover rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Congestion relief handover retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Incoming handover requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Handover retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Multiband mobile station redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
RNC description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
RNC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
RNS site configuration and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
RNS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Node B cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
RNC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
RNS with more than one Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
RNC subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
RNC user features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Overview of RNC user features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Short Message Service (SMS) point to point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Radio Resource Management (RRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
User Equipment (UE) capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Overload control (RNC and Node B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Node B description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Node B functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Logical flows through a Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
RF coverage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Antenna system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
User Equipment (UE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
UE phone call procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Mobile station components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Hand portable viability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Equipment identity number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Subscriber identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Operations and Maintenance Centre - UTRAN (OMC-U) . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Introduction to an OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
OMCs in UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Role of the OMC-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Role of the OMC-S/T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Chapter 4: Data flow and terrestrial interfaces for UMTS

Overview of terrestrial interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
iv 68P02905W21-B
02-Jun-2004
Introduction to terrestrial interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Diagram of terrestrial interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Introduction to Asynchronous Transfer Mode (ATM) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Principles of ATM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Asynchronous Transfer Mode (ATM) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
ATM data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
ATM adaption layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
ATM adaption process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Generic AAL process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
ATM Adaption Layer2 (AAL2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
ATM Adaption Layer5 (AAL5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
ATM virtual channels and paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
E1 architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
E1 specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
ATM cell to E1 cell mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
E link multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Inverse Multiplexing for ATM (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Multiplexing technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Plesiochronous Digital Hierarchy (PDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Overview of PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Synchronous Digital Hierarchy (SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Principles of SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
ATM to STM Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Typical UMTS ATM Transport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Chapter 5: Air Interface Physical Layer

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Topics covered in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Overview of the Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Physical Layer Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
QPSK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Channel locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Structure of transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Downlink transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Uplink transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Channels on the Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Overview of Air Interface channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Logical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Transport channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Channel mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Physical signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Generic frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Radio frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
System frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
68P02905W21-B v
02-Jun-2004
Contents
Timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Synchronization Channel (SCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Primary SCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Secondary SCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Modulation a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Synchronization (Cell Search) procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Common Pilot Channel (CPICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Primary Common Pilot Channel (P-CPICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Secondary Common Pilot Channel (S-CPICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
P-CCPCH frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
SCH and P-CCPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Paging Indicator Channel (PICH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Secondary Common Control Physical Channel (S-CCPCH) . . . . . . . . . . . . . . . . . . . . . . . 5-26
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Random Access Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Structure of Random Access Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
PRACH Preamble. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Acquisition Indicator Channel (AICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Structure of PRACH Message Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Downlink dedicated physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Downlink slot formation in case of Multi-Code Transmission . . . . . . . . . . . . . . . . . . . . 5-34
Uplink dedicated physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Downlink flow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Convolution Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Turbo Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Rate matching and insertion of DTX indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Rate matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Insertion of DTX indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Transport channel multiplexing and Physical Layer segmentation . . . . . . . . . . . . . . . . . . . . . 5-44
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
2nd Insertion of DTX Indication segmentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Physical Layer segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
2nd Interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Downlink spreading and channel combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Channel combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Uplink flow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Radio frame equalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Rate matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Uplink spreading and channel combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
vi 68P02905W21-B
02-Jun-2004
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
PRACH Message Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Chapter 6: W-CDMA theory

Introduction to Wideband Code Division Multiple Access (W-CDMA) . . . . . . . . . . . . . . . . . . 6-3
Introduction to W-CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Cocktail party analogy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
W-CDMA techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Multiple access schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Frequency Division Multiple Access (FDMA). . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Time Division Multiple Access (TDMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Code Division Multiple Access (CDMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
W-CDMA characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Major features of W-CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Re-use of frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Re-use of codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Spectral efficiency (GSM and UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Direct Spread (DS)-CDMA implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Spreading and despreading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Spreading operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
De-spreading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Orthogonal Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Channelisation Code Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
De-spreading other users signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Processing Gain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Scrambling and summation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Scrambling Codes vs Channelisaton Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Short codes vs long codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Scrambling and Summation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
De-Scrambling and Data Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Multi-path radio channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Inter-symbol interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Signal fade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Matched Filter Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
RAKE receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Chapter 7: Transmission systems

Introduction to this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Overview of UMTS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Diagram of UMTS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Outline of UMTS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Iub interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Introduction to the Iub interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Iub radio application signalling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
68P02905W21-B vii
02-Jun-2004
Contents
Iub DCH data stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Iub interface logical O&M procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Iub interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Iub interface network layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Iub interface Transport Network Layer (TNL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Introduction to the Iub TNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Iub TNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Iub TNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Iub TNL transport network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Iub interface Radio Network Layer (RNL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Introduction to the Iub RNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Iub RNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Iub RNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Iub control and user plane protocol stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Introduction to Iub control plane protocol stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Iub radio network control plane protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Iub transport network control plane protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Iub user plane protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Iub interface procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Introduction to Iub procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Categories of Iub procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Iub user plane procedures for common transport channel data streams . . . . . . . . . . . . . . . . . . . 7-16
Introduction to Iub user plane procedures for common transport channel data streams . . . . . . . . . 7-16
Iub common transport channel data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Iub common transport channel node synchronisation. . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Iub common channel downlink transport channels synchronisation . . . . . . . . . . . . . . . . . . 7-16
Iub user plane procedures for dedicated transport channel data streams . . . . . . . . . . . . . . . . . . 7-17
Introduction to Iub user plane procedures for dedicated transport channel data streams . . . . . . . . . 7-17
Iub dedicated transport channel data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Iub dedicated transport channel timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Iub dedicated transport channel synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Iub dedicated transport channel outer loop power control information transfer (FDD) . . . . . . . . . 7-18
Iub dedicated transport channel node synchronisation . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Iub dedicated transport channel radio interference parameter update (FDD) . . . . . . . . . . . . . . 7-18
NBAP common procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Introduction to NBAP common procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
NBAP common transport channel management . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
NBAP configuration alignment (common) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
NBAP common resources measurements (common) . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
NBAP cell configuration management (common) . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
NBAP resource event management (common). . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
NBAP system information management (common) . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
NBAP radio link management (common) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
NBAP dedicated procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Introduction to NBAP dedicated procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
NBAP radio link management (dedicated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
NBAP downlink power drifting correction (FDD) (dedicated) . . . . . . . . . . . . . . . . . . . . 7-24
NBAP measurements on dedicated resources (dedicated). . . . . . . . . . . . . . . . . . . . . . . 7-25
NBAP radio link supervision (dedicated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
NBAP compressed mode control (FDD) (dedicated) . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Error handling procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Introduction to error handling procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Reporting of general error conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Iur interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Introduction to the Iur interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
viii 68P02905W21-B
02-Jun-2004
Iur interface network layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Iur interface radio application signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Iur interface radio network signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Iur interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Introduction to Iur interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Iur interface data frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Iur interface user data streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Iur interface quality estimates for uplink transport channels . . . . . . . . . . . . . . . . . . . . . 7-30
Iur interface node synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Iur interface frame synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Iur interface MAC-d/ MAC-c(sh) flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Iur interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Introduction to Iur interface protocol structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Iur interface layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Iur interface Transport Network Layer (TNL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Introduction to the Iur TNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Iur TNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Iur TNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Iur TNL transport network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Iur interface Radio Network Layer (RNL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Introduction to the Iur RNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Iur RNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Iur RNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
RNSAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Introduction to RNSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
RNSAP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
RNSAP message flow diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
RNL user plane channel procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Introduction to RNL user plane channel procedures . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
RNL user plane procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
RNL user plane common channel procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Introduction to RNL user plane common channel procedures . . . . . . . . . . . . . . . . . . . . . 7-40
RACH/CPCH data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
FACH data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
FACH flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
RNL user plane dedicated channel procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Introduction to RNL user plane dedicated channel procedures . . . . . . . . . . . . . . . . . . . . 7-43
Data transfer - uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Data transfer - downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
RNL user plane dedicated channel control frame procedures . . . . . . . . . . . . . . . . . . . . . . . 7-45
Introduction to RNL dedicated channel control frame procedures . . . . . . . . . . . . . . . . . . . 7-45
Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Outer loop power control (PC) information transfer . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Node synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Radio interface parameter update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Common transport channel frame structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Introduction to common transport channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Data frame structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
Dedicated channel frame structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
Introduction to dedicated channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
Uplink data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
Downlink data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56
Control frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Iu-CS and Iu-PS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58
68P02905W21-B ix
02-Jun-2004
Contents
Introduction to Iu-CS and Iu-PS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58

Iu-CS and Iu-PS interface Radio Access Bearer (RAB) signalling . . . . . . . . . . . . . . . . . . 7-58
Iu-CS and Iu-PS interface data information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58
Iu-CS and Iu-PS interface in-band user plane frame protocol signalling . . . . . . . . . . . . . . . . 7-59
Iu-CS and Iu-PS interface protocol structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Introduction to Iur interface protocol structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Iu-CS and Iu-PS interface network layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Iu-CS and Iu-PS interface Transport Network Layer (TNL). . . . . . . . . . . . . . . . . . . . . . . . 7-62
Introduction to the Iu TNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Iu TNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Iu TNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Iu TNL transport network control plane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Iu-CS and Iu-PS user plane protocol modes of operation . . . . . . . . . . . . . . . . . . . . . . . 7-63
Iu-CS and Iu-PS interface Radio Network Layer (RNL) . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Introduction to the Iu RNL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Iu RNL radio network control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Iu RNL radio network user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Uu interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Uu interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Uu interface signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Uu interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Uu interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Uu interface layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Uu interface layer 1 - physical layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Uu interface layer 2 - Medium Access (MAC) layer . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Uu interface layer 2 - Radio Link Control (RLC) layer . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Uu interface layer 2 - Packet Data Convergence Protocol (PDCP) layer . . . . . . . . . . . . . . . . 7-71
Uu interface layer 2 - Broadcast/ Multicast Control (BMC) layer . . . . . . . . . . . . . . . . . . . 7-72
Uu interface layer 3 - Radio Resource Control (RRC) layer . . . . . . . . . . . . . . . . . . . . . 7-72
Uu interface Non-Access Stratum (NAS) layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
RRC connection procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
RRC connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
RRC connection release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
RRC connection re-establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Transmission of UE Capability Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
UE Capability Enquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
RRC management procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Broadcast of system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Initial direct transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Downlink direct transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Uplink direct transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
UE dedicated paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Security mode control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Signalling Connection Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Signalling Connection Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Counter check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Inter RAT handover information transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Chapter 8: Cabinet description

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Node B cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
x 68P02905W21-B
02-Jun-2004
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Node B cabinet for indoor and outdoor use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Node B configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
External views of the Node B cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
External view of stacked cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Node B outdoor enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Overview of outdoor enclosure for Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Node B outdoor ancillary enclosure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Ancillary enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
RNC5000 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Introduction to the RNC5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
RNC architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
RNC modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Chapter 9: UTRAN features in USR 1.0

USR1.0 Initial Base Load features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Overview of USR1.0 Initial Base Load features . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Node B configuration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Signalling and terrestrial interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
UMTS air interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Radio connection, admission and resource management functions: . . . . . . . . . . . . . . . . . . 9-6
Node B configuration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Receive spatial diversity (23033) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Support for 3rd party mast head amplifiers (23039) . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
IMA (Inverse Multiplxing for ATM) (23041) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Signalling and terrestrial interfaces features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Overview of signalling and terrestrial interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Signalling and terrestrial interface feature categories. . . . . . . . . . . . . . . . . . . . . . . . . 9-13
ATM backbone support features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Benefits of the ATM backbone support features . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
ATM backbone available (leasing of VP/VC) (23014) . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Line Leasing: star configurations (23015). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
ATM transport (23047) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Support of all Defined QoS Classes (23048) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Traffic shaping (23049) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
CBR and VBR (23155/23156) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
AAL2 switching (23158) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Cross-connect and routing (23159) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
ATM protection switching (23160) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
RNC Shared Physical Interface features for Iu, Iur, Iub . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Benefits of RNC Shared Physical Interface features for Iu, Iur, Iub . . . . . . . . . . . . . . . . . . 9-19
Iu open interface (23050) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Iu-CS at least 64 kbit/s (23051) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
68P02905W21-B xi
02-Jun-2004
Contents
Iu-CS signalling by SS7 (23054) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

Iu-PS at least 384 kbit/s (23052) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Iu-PS signalling by SS7 (23053) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Iub interface (23056) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Iur open interface (23058) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Iur signalling by SS7 (23059) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
UMTS air interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Support of FDD mode air interface to 3GPP (23061) . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Support of all FDD transport channels except CPCH (23062). . . . . . . . . . . . . . . . . . . . . 9-22
Air interface coding, multiplexing and interleaving supported (23063) . . . . . . . . . . . . . . . . 9-23
Turbo coding (23064) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Convolutional Coding (23065) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
System Information Broadcasting (23077) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Radio connection, admission and resource management functions features . . . . . . . . . . . . . . . . 9-27
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Radio connection, admission and RM functions feature categories . . . . . . . . . . . . . . . . . . 9-28
General support of RRM functions features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Radio resource allocation and management (23067) . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Radio Admission Control (23068) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
UE capability handling (23071) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
Radio Channel Ciphering and Deciphering (23075) . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
Air interface signalling integrity protection (23076) . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
System Information Broadcasting (23077) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
RAB Admission Control (23080). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
CS RAB supported (23082) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
PS RAB supported (23083) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Transport Channel and RRC State Selection and Switching (23084) . . . . . . . . . . . . . . . . . 9-32
Code Management (23085) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Active UE register (23086) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Cell Update (23078). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Paging (23088) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Compressed Mode (23089) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Traffic Volume Measurement (23090) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
RAB Establishment, Reconfiguration, and Release (23091) . . . . . . . . . . . . . . . . . . . . . 9-34
RAB Mapping (23092) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Radio Interface Scheduling (23093) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Radio Interface Synchronisation (23094) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
Time Alignment (23095) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
Frame Synchronisation (23097) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
RNC Based Radio Load Control (23120) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Power Control features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Benefits of the power control features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Closed loop power control (23072) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Outer loop power control (23073) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Open loop power control (23074) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Handover features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
Description of UMTS to UMTS handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
Benefits of Motorola’s Handover solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41
xii 68P02905W21-B
02-Jun-2004
RNC Soft handovers (23099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42

RNC Softer Handovers (23101) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42
RNC hard Handovers (23102) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
Intra Sector Hard Handovers (23103) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
SRNS Relocation (23107) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-44
USR1.0 optional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Overview of USR1.0 optional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Optional features and categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
Node B hardware support features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
Six Sectors Support (23023) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
Downlink transmit diversity: Open Loop (22953) . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49
Node B Trunked Power Amplifier Support (23038) . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Radio resource management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
Simultaneous Multiple Radio Access Bearers Support (1CS + 1PS) (23081). . . . . . . . . . . . . . 9-52
AMR Speech Codec Rate Control (23162) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Dynamic Channel Configuration Control (DCCC) (23163) . . . . . . . . . . . . . . . . . . . . . . 9-54
Direct Retry (23164) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
Tracing functions (23165) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Load Optimisation (23166) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
PDCP (Packet Data Convergence Protocol) Header Compression (23167) . . . . . . . . . . . . . . . 9-56
Inter RAT Handover features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Inter System Active Handover (UMTS-GSM) (23110) . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Inter System Handover with Dual Receiver Handset (23111) . . . . . . . . . . . . . . . . . . . . . 9-60
Inter System Handover - Compressed Mode Handover (23112). . . . . . . . . . . . . . . . . . . . 9-60
Inter System Change via Cell Reselection (UMTS-GSM/GPRS) (23121) . . . . . . . . . . . . . . . 9-60
Short Message Service (SMS) Point to Point (23066) . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Location Based Services (LBS) - Cell ID (23113) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Call Trace (23115). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Overload Control features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Node B Overload Control (23116) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
RNC Overload Control (23117) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-67
Chapter 10: OMC-U and its USR 1.0 features

68P02905W21-B xiii
02-Jun-2004
Contents

Operations and Maintainance Centre for UMTS (OMC-U) . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
UMTS network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Overview of OMC-U features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Initial Baseload OMC-U features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Optional OMC-U features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
OMC platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Overview of OMC platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
NT Server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
UNIX Server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
OMC-U platform features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
OMC-U Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Alarm Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Audible indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Subscription and filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Fault Management information synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Fault Management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
OMC-U Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Configuration Management Information Synchronization . . . . . . . . . . . . . . . . . . . . . . 10-16
Data interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Offline provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
OMC-U Configuration Management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
OMC-U Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
OMC-U Load Management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
OMC-U Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Background statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Performance data presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
On-Demand Statistics View (OMC-S/T only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
OMC-U Performance Management features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Interfaces from OMC-U to higher level management. . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Fault Management IRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Interface to Network Performance Management (Metrica) . . . . . . . . . . . . . . . . . . . . . . 10-23
OMC-U interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
OMC-U Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Security performed by the network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
User authentication and control of user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Logged operator actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
OMC-U Security Management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
OMC-U general application functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
OMC Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Customer-definable network regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
OMC Help facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
OMC-U general application features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Optional OMC-U features in USR1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Support for 3GPP IRP FM Northbound Interface to NMC (23197) . . . . . . . . . . . . . . . . . . 10-29
Web Access Server (22044) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
xiv 68P02905W21-B
02-Jun-2004
Contents
Chapter 11: Glossary of abbreviations

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-37
H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
J. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-49
K. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-50
L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-51
M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-54
N. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-59
O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-63
P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-65
Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-73
R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-74
S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-79
T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-87
U. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-92
V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-94
W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-96
X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-97
68P02905W21-B xv
02-Jun-2004
Contents
This page intentionally left blank.
xvi 68P02905W21-B
02-Jun-2004
List
of
Figures
List of Figures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 2-1: UMTS network elements and physical UMTS interfaces . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-2: UMTS components and logical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Figure 2-3: UMTS functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-4: OSI layers - main protocol relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Figure 2-5: Radio network CN protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Figure 2-6: Worldwide spectrum allocation for IMT-2000 . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Figure 2-7: European frequency allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Figure 2-8: Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Figure 2-9: Database list summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Figure 2-10: HLR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Figure 2-11: Authentification centre configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Figure 2-12: Authentication and Key Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Figure 2-13: Visited location register configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Figure 2-14: MM logical entities and their relationships . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Figure 2-15: MS to PSTN subscriber call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Figure 2-16: PSTN subscriber to MS call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Figure 2-17: MS to MS call (same PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Figure 2-18: MS to MS call (different PLMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Figure 2-19: MS to MS call (different PLMN/different country) . . . . . . . . . . . . . . . . . . . . . 2-49
Figure 2-20: GSM/GPRS to UMTS migration path . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Figure 2-21: Deployment of UMTS in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
Figure 3-1: Dual RNS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Figure 3-2: RNC in the UTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Figure 3-3: RNC in UTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Figure 3-4: Multiple Node B sites per RNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-5: RNC5000 cabinet layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Figure 3-6: RNC5000 functional modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Figure 3-7: Logical view of Node B architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Figure 3-8: O & M platforms and network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Figure 4-1: Terrestrial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Figure 4-2: ATM basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Figure 4-3: ATM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-4: ATM Adaption Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Figure 4-5: Generic AAL Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-6: AAL2 format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-7: AAL5 format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Figure 4-8: Virtual channels and paths and their use . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Figure 4-9: Virtual Connection and Path Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-10: ATM cell to E1 mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Figure 4-11: E1 Series hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Figure 4-12: Inverse Multiplexing and De-multiplexing of ATM cells . . . . . . . . . . . . . . . . . . . 4-20
Figure 4-13: IMA Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
68P02905W21-B xvii
02-Jun-2004
List of Figures
Figure 4-14: PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Figure 4-15: SDH Multiplex Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Figure 4-16: ATM to STM Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-17: Typical ATM transport network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Figure 5-1: QPSK modulation scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Figure 5-2: Layers 1, 2 and 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Figure 5-3: Air Interface channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Figure 5-4: Logical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Figure 5-5: Transport channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Figure 5-6: Physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Figure 5-7: Channel mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Figure 5-8: Generic frame structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Figure 5-9: Primary and Secondary synchronization codes modulated by the symbol a . . . . . . . . . . . 5-19
Figure 5-10: CPICH Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Figure 5-11: Modulation pattern for the Common Pilot Channel . . . . . . . . . . . . . . . . . . . . . 5-22
Figure 5-12: P-CCPCH frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Figure 5-13: SCH and P-CCPCH structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Figure 5-14: Structure of the Paging Indicator Channel (PICH) . . . . . . . . . . . . . . . . . . . . . . 5-25
Figure 5-15: S-CCPCH structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Figure 5-16: RACH access slot numbers and their spacing . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Figure 5-17: Structure of the random-access transmission . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Figure 5-18: Acquisition Indicator Channel (AICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Figure 5-19: Structure of the PRACH Message Part . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Figure 5-20: Structure of the Downlink DPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Figure 5-21: Downlink slot format of multi-code transmission . . . . . . . . . . . . . . . . . . . . . . 5-35
Figure 5-22: Structure for the Uplink DPDCH/DPCCH . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Figure 5-23: Transport Channel Multiplexing Structure for the Downlink . . . . . . . . . . . . . . . . . 5-39
Figure 5-24: Fixed and Flexible Bit positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Figure 5-25: Transport Channel multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Figure 5-26: Spreading for all downlink physical channels except SCH . . . . . . . . . . . . . . . . . . 5-46
Figure 5-27: Channel combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Figure 5-28: Uplink flow process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Figure 5-29: DPCCH/DPDCH spreading and combination . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Figure 5-30: PRACH spreading and combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Figure 6-1: Multiple access schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Figure 6-2: Spectral efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Figure 6-3: Direct Spread CDMA implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Figure 6-4: Spreading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Figure 6-5: De-spreading (desired signal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Figure 6-6: Orthogonal codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Figure 6-7: Channelisation code tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Figure 6-8: De-spreading (Interferer Signals) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Figure 6-9: Scrambling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Figure 6-10: Scrambling and Summation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Figure 6-11: De-Scrambling and Data Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Figure 6-12: Multi-path radio channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Figure 6-13: Matched filter operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Figure 6-14: RAKE receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Figure 7-1: UMTS interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Figure 7-2: Iub interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Figure 7-3: Iub radio network control plane protocol stack . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Figure 7-4: Iub transport network control plane protocol stack . . . . . . . . . . . . . . . . . . . . . . 7-14
Figure 7-5: Iub user plane protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Figure 7-6: Iur interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Figure 7-7: RACH/CPCH data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
xviii 68P02905W21-B
02-Jun-2004
List of Figures
Figure 7-8: FACH data transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41

Figure 7-9: FACH flow control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Figure 7-10: Uplink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Figure 7-11: Downlink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Figure 7-12: Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Figure 7-13: DCH synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Figure 7-14: Outer loop PC information transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Figure 7-15: Node synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Figure 7-16: Radio interface parameter update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Figure 7-17: Common transport channel frame structure . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Figure 7-18: Example common transport channel frame structure . . . . . . . . . . . . . . . . . . . . . 7-50
Figure 7-19: RACH data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
Figure 7-20: FACH data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Figure 7-21: Dedicated channel frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
Figure 7-22: Uplink DCH data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
Figure 7-23: Downlink DCH data frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56
Figure 7-24: General structure of the control frame . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Figure 7-25: Iu-CS and Iu-PS interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . 7-61
Figure 7-26: Uu interface protocol structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Figure 7-27: PDCP layer architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
Figure 7-28: Uu interface RRC layer architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Figure 7-29: RRC connection establishment, network accepts RRC connection . . . . . . . . . . . . . . 7-75
Figure 7-30: RRC connection establishment, network rejects RRC connection . . . . . . . . . . . . . . . 7-76
Figure 8-1: Closed cabinet with hood and closed cabinet with stacking bracket . . . . . . . . . . . . . . 8-5
Figure 8-2: View of stacked Node B indoor cabinets, showing stacking bracket, front cover and hood. . . . 8-6
Figure 8-3: External view of the Node B outdoor enclosure . . . . . . . . . . . . . . . . . . . . . . . 8-8
Figure 8-4: External view of the ancillary enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Figure 8-5: External view of the RNC5000 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Figure 8-6: RNC5000 functional modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
68P02905W21-B xix
02-Jun-2004
List of Figures
xx 68P02905W21-B
02-Jun-2004
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Table 2-1: W-CDMA features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Table 2-2: QoS classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Table 4-1: Physical Layer Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Table 4-2: E1 specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Table 4-3: SDH Bit Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Table 4-4: SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Table 5-1: Common Physical Channels (CPCHs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Table 5-2: Modulation a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Table 5-3: Dedicated downlink physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Table 5-4: Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Table 5-5: Usage of channel coding scheme and coding rate . . . . . . . . . . . . . . . . . . . . . . . 5-40
Table 6-1: W-CDMA characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Table 6-2: Scrambling codes vs Channelisation codes . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Table 6-3: Short codes vs long codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Table 10-1: NT Server - Dell PowerEdge™ 6400/6450 specifications . . . . . . . . . . . . . . . . . . . 10-9
Table 10-2: Unix Server - Sun SunFire 4800 specifications . . . . . . . . . . . . . . . . . . . . . . . . 10-9
68P02905W21-B xxi
02-Jun-2004
List of Tables
xxii 68P02905W21-B
02-Jun-2004
About
This
Manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 1
02-Jun-2004
Issue status of this manual
Issue status of this manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1 Manual version history
Manual
Date of issue Remarks
issue
A 30 Sep 2003 Original issue - Software release GSR5/GSN1/USR1
B 02 Jun 2004 Issue B- Software release
Resolution of service requests
The following Service Requests are now resolved in this manual:
Table 2 Service requests resolved in this manual
Service GMR
Remarks
Request Number
N/A N/A Original issue - Volume Deployment
2 68P02905W21-B
02-Jun-2004
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage,
loss or reduction in system performance arising directly or indirectly out of the failure
of the customer, or anyone acting on the customers behalf, to abide by the instructions,
system parameters or recommendations made in this manual
• If this manual was obtained when attending a Motorola training course, it will not be updated
or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied
under normal operational circumstances, to support a major software release, then corrections
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,
installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is
recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorola’s operation, installation and maintenance

instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features
released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In
these manuals, new and amended features are tagged to help users to assess the impact on installed
networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and
Development Prioritization (RDP) numbers. The tags include index references which are listed in the
manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP
numbers for the released features, with page references and hot links in electronic copy.
68P02905W21-B 3
02-Jun-2004
General information
The tags have the format: {nnnn} or {nnnnn}

Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
New and amended feature information Tag position in text

New sentence/s or new or amended text. Immediately before the affected text.
Complete new blocks of text as follows: Immediately after the headings as follows:
• Full sections under a main heading • Main heading
• Full paragraphs under subheadings • Subheading

New or amended complete Figures and Tables After the Figure or Table number and before
the title text.
Warning, Caution and Note boxes. Immediately before the affected text in the box.
General command syntax, operator input or On a separate line immediately above the
displays (in special fonts). affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this
software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to
the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and
section names. The references to external publications are shown in italics, chapter and
section name cross references are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and
GPRS network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels as individually standardised, or may not be present
at all in some parts of the network in which it is normally implemented. The manual set, of which
this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual
countries, limitations on the encryption included in the particular software being delivered, are covered
in the Release Notes that accompany the individual software release.
4 68P02905W21-B
02-Jun-2004
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent
keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
¦ Press the pipe symbol key.
CR or RETURN Press the Return key.
68P02905W21-B 5
02-Jun-2004
Reporting safety issues
Reporting safety issues

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure
that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1 Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written
report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
6 68P02905W21-B
02-Jun-2004
Warnings and cautions

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this manual and in
all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use of
adhesives and solvents, as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Failure to comply with warnings
Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specific
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Cautions
A definition and example follow below:
68P02905W21-B 7
02-Jun-2004
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.
8 68P02905W21-B
02-Jun-2004
General warnings
General warnings
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
• Potentially hazardous voltage.
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working
with or operating Motorola equipment must comply with any warning labels fitted to the equipment.
Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must
any other warnings given in text, in the illustrations and on the equipment.
68P02905W21-B 9
02-Jun-2004
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment
from the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material
and pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even
death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart,
to stop. It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS
send for trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool,
until trained first aid or medical assistance arrives.
RF radiation
High RF potentials and electromagnetic fields are present in this equipment

when in operation. Ensure that all transmitters are switched off when
any antenna connections have to be changed. Do not key transmitters
connected to unterminated cavities or feeders.
10 68P02905W21-B
02-Jun-2004
General warnings
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields

High Frequency (10 kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

competent responsible person must ensure that adequate lifting facilities are
available. Where provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames
must be used for these operations. When equipment has to be manhandled, reference must be
made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling
of loads legislation for the country in which the equipment is used.
Parts substitution
Do not install substitute parts or perform any unauthorized modification of

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
68P02905W21-B 11
02-Jun-2004
General warnings
Battery supplies
Do not wear earth straps when working with stand-by battery

supplies. Use only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

lithium batteries must not be removed or replaced. Any boards containing
defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
12 68P02905W21-B
02-Jun-2004
General cautions
General cautions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specific cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to
the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual.
These must be observed by all personnel at all times when working with the equipment, as must
any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the section
Devices sensitive to static in the preface of this manual for further information.
68P02905W21-B 13
02-Jun-2004
Devices sensitive to static
Devices sensitive to static

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to
the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together,
for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic
foam. Provided the leads are short circuited it is safe to handle the device.
Special handling techniques
In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
• Always wear an earth strap which must be connected to the electrostatic

point (ESP) on the equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material.
A cotton overall is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices.

These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges and
not by their tracks and pins, they should be transferred directly from their packing to the equipment
(or the other way around) and never left exposed on the workbench.
14 68P02905W21-B
02-Jun-2004
Motorola manual set
Motorola manual set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
• Electronic, as fully navigable PDF files on:

◦ The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
◦ CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software
release, together with current versions of appropriate hardware manuals, and has additional
navigation facilities. A snapshot copy of on-line documentation is also included, though it
will not be updated in line with subsequent point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist
products such as MARS or COP.
Ordering manuals and CD-ROMs
Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
68P02905W21-B 15
02-Jun-2004
GMR amendment
GMR amendment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Changes to a manual that occur after the printing date are incorporated into the manual using
General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when
required. A GMR has the same identity as the target manual. Each GMR is identified by a
number in a sequence that starts at 01 for each manual at each issue.
GMR availability
GMRs are published as follows:
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
◦ Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
• Motorola service web - Updated at the same time as hard copies.
• CD-ROM - Updated periodically as required.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it in
a suitable place in this manual for future reference.
16 68P02905W21-B
02-Jun-2004
GMR amendment
GMR amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number Incorporated by (signature) Date

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
68P02905W21-B 17
02-Jun-2004
GMR amendment
18 68P02905W21-B
02-Jun-2004
Chapter
1
Introduction to this manual and Motorola
documentation
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter provides an overview of the contents of this manual and a listing of Motorola
UMTS manuals supplied to customers. The chapter also includes a description of the Motorola
documentation system and includes a brief summary of the contents of each manual. Other
documents available to Motorola customers are also listed.
The following topics are included in this chapter:
• "Overview of the contents of this manual" on page 1-2.
68P02905W21-B 1-1
02-Jun-2004
Overview of the contents of this manual Chapter 1: Introduction to this manual and Motorola documentation
Overview of the contents of this manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Contents of 68P02905W21: UMTS Overview
The follow sections describe the chapters in this manual. An Index is also provided at the end of the manual.
Chapter 1 Introduction to this manual and Motorola documentation

This chapter contains an overview of this manual and a description of the Motorola manual
set, which includes GSM, GPRS and UMTS manuals.
Chapter 2 Overview of UMTS

This chapter provides an overview of Universal Mobile Telecommunications System (UMTS),
including UMTS network elements, subsystems, W-CDMA, interfaces, links, protocols, and UTRAN.
For readers requiring more detail, some topics have their own chapters.
Chapter 3 Functional description of UTRAN components

This chapter provides a functional description of the UTRAN components; RAN (Node B
and RNC5000), User Equipment (UE), and OMC-U.
Chapter 4 Data flow and terrestrial interfaces for UMTS

This chapter describes the transport mechanisms for the UMTS transport network, especially ATM,
which is the preferred transport mechanism on the Core Network.
Chapter 5 Air Interface Physical Layer

This chapter describes the UMTS Air Interface Physical Layer, such as UMTS channel
structure and Downlink and Uplink flow processes.
Chapter 6 W-CDMA theory

This chapter provides an introduction to W-CDMA theory, such as multiple access schemes, W-CDMA
characteristics, spreading and despreading procedures, the scrambling and summation process.
Chapter 7 Transmissions systems

This chapter details the interfaces and protocols that allow UMTS network entities to communicate
with each other and with external systems. Transmissions systems described include Iub, Iur, Iu-CS,
Iu-PS, Iu-BC, Iu-O&M, and the Uu interface. GSNu interfaces are also described.
Chapter 8 Cabinet descriptions

This chapter describes the hardware components in the UTRAN, that is, Node B cabinet, Node
B Outdoor Enclosure, Node B Ancillary Enclosure, and the RNC5000.
1-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of the contents of this manual
Chapter 9 UTRAN features in USR1.0

This chapter lists and describes the base load and optional features in UMTS release USR1.0.
Chapter 10 OMC-U and its USR1.0 features

This chapter describes the OMC-U and the base load and optional features included in USR1.0.
Chapter 11 Glossary of abbreviations and terms

This chapter provides a list and explanation of UMTS abbreviations and terms.
68P02905W21-B 1-3
02-Jun-2004
Overview of the contents of this manual Chapter 1: Introduction to this manual and Motorola documentation
1-4 68P02905W21-B
02-Jun-2004
Chapter
2
Overview of UMTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 2-1
02-Jun-2004
Chapter overview Chapter 2: Overview of UMTS
Chapter overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This chapter provides an overview of the Universal Mobile Telecommunications System (UMTS).
It provides overview information for the key areas of UMTS. For readers who need more detail,
some topics have their own chapter later in the manual.
Topics in this chapter
The following topics are covered in this chapter:
"What is UMTS?" on page 2-4

This section lists the services UMTS is expected to deliver to subscribers and the
technology that is used to provide these services.
"Overview of the UMTS network" on page 2-5

This section provides an illustration of a typical UMTS network.
"UTRAN network" on page 2-8

This section describes the components of the UTRAN network.
"Core Network" on page 2-10

This section describes the components of the Core Network (CN).
"Core Network subsystems (non-network elements)" on page 2-13

This section describes the subsystem elements of a Core Network.
"UMTS interfaces" on page 2-15

This section provides an introduction to the interfaces used in a UMTS network.
"Core Network interfaces" on page 2-18

This section provides an introduction to the interfaces used in a Core Network network
"UTRAN network protocols" on page 2-19

This section describes the protocols used in a UTRAN network.
2-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Chapter overview
"E1/STM-1 links" on page 2-23

This section describes the physical link elements of a UMTS network.
"Wideband Code Division Multiple Access (W-CDMA)" on page 2-24

This section provides an introduction to the W-CDMA techniques employed in UMTS.
"UMTS frequencies" on page 2-27

This section describes the the frequency allocation for UMTS.
"Mobile services Switching Centre for UMTS (MSCu)" on page 2-30

This section describes the MSCu; a component of the Core Network.
"Authentication and Key Agreement" on page 2-39

This section describes the Authentication and Key Agreement (AKA).
"Network Management Centre (NMC)" on page 2-50

This section describes the NMC; a component of the Core Network.
"Quality of Service (QoS)" on page 2-52

This section describes the Quality of Service (QoS) offered by a UMTS network.
"Migration from GSM/GPRS to UMTS" on page 2-56

This section describes the migration from an existing GSM/GPRS network to UMTS.
68P02905W21-B 2-3
02-Jun-2004
What is UMTS? Chapter 2: Overview of UMTS
What is UMTS?
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
UMTS services for the user
The Universal Mobile Telecommunications System (UMTS) will deliver voice, graphics, video and other
broadband information direct to the user, regardless of location, network or terminal.
These fully personal communication services provide terminal and service mobility on fixed and mobile
networks, taking advantage of the convergence of existing and future fixed and mobile networks
and the potential synergies that can be derived from such convergence.
The key benefits that UMTS promises include improvements in quality and security, incorporating broadband
and networked multimedia services, flexibility in service creation and ubiquitous service portability.
Networked multimedia includes services such as, pay-TV, video and audio on-demand,
interactive entertainment, educational and information services, and communication services
such as video-telephony and fast, large file transfer.
UMTS services are also likely to be used by other sectors, including systems with limited mobility
(for example, in areas with low population density), and in private/corporate markets, ranging
from home use to wireless PBXs, emergency and cordless systems.
UMTS technology
UMTS is a new generation GSM which utilises the spread-spectrum, Wideband Code Division
Multiple Access Technique (W-CDMA) for its radio interface.
W-CDMA receivers separate communication channels by means of a pseudo-random modulation
that is applied and removed in the digital domain (with modulation codes), not on the basis of
frequency. Multiple users occupy the same frequency band.
W-CDMA optimises the use of spectrum efficiency, and efficiently supports variable bit rate
services, reduces peak and average transmitted power, permits average interference among
all users, and removes the necessity for frequency planning.
2-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of the UMTS network
Overview of the UMTS network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Typical UMTS system
Figure 2-1 shows a typical UMTS network, including the physical UMTS interfaces.
68P02905W21-B 2-5
02-Jun-2004
Overview of the UMTS network Chapter 2: Overview of UMTS
Figure 2-1 UMTS network elements and physical UMTS interfaces
CORE NETWORK
CS-SERVICE BC PS-SERVICE
DOMAIN DOMAIN DOMAIN
Gi
GSN
GGSN
OML OMC-S/T
Gn
MSCu C-SGSN
Iu-CS Iu-BC Iu-PS
ATM
Iu Iu
Iu-REFERENCE POINT
OMC-U
RAN RAN
OML RNC Iur RNC
ATM ATM
Iub Iub Iub Iub
NODE B NODE B NODE B NODE B
Uu
MOBILE USER EQUIPMENT

(UE)
UTRAN
2-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of the UMTS network
UMTS network components
A UMTS system comprises two networks:

• UMTS Terrestrial Radio Access Network (UTRAN)
• Core Network (CN).
68P02905W21-B 2-7
02-Jun-2004
UTRAN network Chapter 2: Overview of UMTS
UTRAN network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
UTRAN components
The UTRAN includes the following subsystems:

• Radio Network Subsystem (RNS).
Responsible for the resources and transmission/reception in a set of cells. Each
RNS has an Iu-CS interface to the Circuit Switched Service Domain, and an Iu-PS
interface to the Packet Switched Service Domain.
The RNS consists of:
◦ Radio Network Controller (RNC)
◦ Node B
• User Equipment (UE) - the mobile station (MS).
• Operations and Maintenance Centre-UTRAN (OMC-U).
Radio Network Controller (RNC)
The RNC is the network element that performs higher level controlling functions for the Radio
Network System (RNS). It terminates the Iub interface towards the Node B, the Iu interface towards
the Core Network, and the Iur interface towards another RNC.
Node B
The Node B is a logical node, responsible for radio transmission/reception in one or more cells to or from the
User Equipment (UE). This is the network element within the Radio Network System (RNS). It terminates the
Iub interface (interface between the RNC and the Node B) towards the Radio Network Controller (RNC).
User Equipment (UE)
The Mobile Station (MS) together with the UMTS Subscriber Identity Module (USIM) are
defined as the radio equipment and Man-Machine Interface (MMI) that a subscriber needs to
access the Public Land Mobile Network (PLMN) services. Typically, this is a mobile telephone
though it may also be a mobile data communications unit.
2-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UTRAN network
Operations and Maintenance Centre-UTRAN (OMC-U)
The OMC-U is responsible for the static management of the UTRAN. This includes allocation
of resources which can be used dynamically by the RNC.
At system initialisation, the OMC-U is responsible for object verification, code load and initialisation
of Node B and the RNC to a default state before they are brought into operation.
OMC-U provides UTRAN management functionality in the following areas:
• Fault Management.
• Configuration Management.
• Load & Database Management.
• Performance Management.
• Security Management.
• On-line Help.
• Northbound interface to Operations Support Systems/Business Support Systems (OSS/BSS).
The OMC-U is connected to each RNC, and through the controlling RNC (CRNC) to each Node B.
The OMC-U receives:
• Control and network information only (not speech or data traffic).
• Alarm reports from Node B, thus enabling Node B degradation to be

handled by the UTRAN network.
For example, if Node B capability is degraded then the static configuration of the system may
be changed to reduce the overall effect on the system.
The OMC-U comprises Window clients and a UNIX server.
For further details, see Chapter 10 - OMC-U and its features.
68P02905W21-B 2-9
02-Jun-2004
Core Network Chapter 2: Overview of UMTS
Core Network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Core Network (CN) components
The UMTS CN includes the following subsystems:

• Gateway GPRS Serving Node (GGSNu).
• Serving GPRS Support Node (SGSNu).
• Mobile Switching Centre (MSCu).
• Location Registers (LR).
• Operations and Maintenance Centre - Transportation network (OMC-S/T).
• Network Management Centre (NMC).
Gateway GPRS Support Node (GGSNu)
The Location Register (LR) function in the GGSNu stores subsriber data received from the HLR and the
SGSNu. There are two types of subsriber data needed to handle originating and terminating packet data transfer:
• Subscriber information:
◦ International Mobile Subscriber Identity (IMSI).
◦ Zero or more Packet Data Protocal (PDP) addresses.
• Location information:
◦ SGSN address for the SGSN where the MS is registered.
2-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Core Network
Serving GPRS Support Node (SGSNu)
The location register function in the SGSNu stores two types of subscriber data needed to
handle originating and terminating packet data transfer:
• Subscriber infprmation:
◦ IMSI.
◦ Zero or more PDP addresses.
• Location information:
◦ Depending on the operating mode of the MS, the cell or the routeing
area where the MS is registered.
◦ Visitor Location Register (VLR) number of the associated VLR (if the
Gs interface is implemented).
◦ GGSNu address of each GGSNu for which an active PDP context exists.
Mobile services Switching Centre (MSCu)
The Mobile services Switching Centre (MSCu) is a telephone switching office for handling calls to and
from the MSs within a defined geographical area. The MSC also provides the interface between the
cellular network and the ordinary land-based Public Switched Telephone Network (PSTN), allowing the
UMTS system to function as an extension of the PSTN. It also allows the UMTS network to interface to
other PLMNs. There can be a number of MSCs within the region controlled by an OMC-U.
Location Registers (LR)
Three Location Register (LR) network elements may be collocated with the MSC. These
are database-oriented processing nodes that manage subscriber data and keep track of the
location of an MS as it roams around the network.
The following are the LRs in the UMTS Network:
Equipment Identity Register (EIR)

The EIR is the database used for validating the International Mobile station Equip-
ment Identity (IMEI) of each MS.
Home Location Register (HLR)

The HLR is the master database of the subscribers to a PLMN. It incorporates an Authentication
Centre (AUC) which is used to authenticate users of the network.
68P02905W21-B 2-11
02-Jun-2004
Core Network Chapter 2: Overview of UMTS
Visitor Location Register (VLR)

The VLR is the database that contains information on subscribers while they are in
the area controlled by the VLR.
Operations and Maintenance Centre - Transportation network

(OMC-S/T)
The Operations and Maintenance Centre (OMC-S/T) provides GSN management

functionality in the following areas:
• On-line Help.
The OMC-S/T provides a Graphical User Interface (GUI) to enable a user to carry
out CN management functions.
The OMC-S/T monitors and receives alarm reports from SGSNu, GGSNu, ISS and
CommHub CN elements. All maintenance, CN reconfiguration, troubleshooting, and CN
administration, is carried out from the OMC-S/T.
Network Management Centre (NMC)
The Network Management Centre (NMC) administers the entire cellular network to provide
operations and maintenance at the network level.
2-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Core Network subsystems (non-network elements)
Core Network subsystems (non-network elements)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The UMTS network also includes the following additional subsystems, which are not
formally recognised as network elements.
Interworking Function
The Interworking Function (IWF) performs the data rate adaptation between the PLMN and networks such as
the PSTN, the Integrated Services Digital Network (ISDN), and packet networks. Other functions of the
IWF include provisions for mobile subscribers to communicate with a PSTN-based modem, or to connect
directly to customer provided equipment, such as X.25 Packet Assembly/Disassembly facilities (PADs).
Echo Canceller
The Echo Canceller (EC) eliminates echo from voice circuits. The voice signal from the PLMN
has to be transformed from the 4-wire PLMN circuit to the 2-wire circuit on the land network. If
it were not cancelled, the total round-trip delay introduced by the UMTS system (typically 180
ms) would become audible to the PLMN subscriber as an echo.
Billing Centre
The billing centre is a system provided by the PLMN administration which collects the billing
data from the UMTS network elements and applies the billing data to subscribers’ accounts.
The details of the billing centre’s operation are not addressed by UMTS, and the billing centre
is not considered to be a network element of the PLMN.
68P02905W21-B 2-13
02-Jun-2004
Core Network subsystems (non-network elements) Chapter 2: Overview of UMTS
There are two types of billing data:

• Call records
Call records are produced by the MSC, which may provide facilities for storing the completed
call records, as well as forwarding them to the billing centre. The records are stored in a disk
file as they are being generated. In this case, the file has a fixed size and when the file becomes
full, it is automatically closed and a new one opened. The completed file is then automatically
transferred to the billing centre using X.25 communication links and the File Transfer, Access,
and Management (FTAM) file transfer protocol. A backup copy of the completed billing
files can be manually copied to magnetic tape. These same storage and communication
facilities can also be provided at HLRs and VLRs for the handling of event records.
• Event records
These are produced by the HLRs and VLRs. An event records the location updates
for the MS and the forwarding of MS terminated calls.
Cell Broadcast Centre
The Cell Broadcast Centre (CBC) is the call processing centre for Cell Broadcast Short
Message Service (CBSMS) messages, which are unacknowledged short messages (128 bytes
maximum) that are broadcast to all MSs in a particular cell.
2-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS interfaces
UMTS interfaces
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to this section
This section provides a brief introduction to the interfaces used in a UMTS network..
Overview of UMTS interfaces
Figure 2-2 shows the logical interfaces within the UMTS. They are:
• Iub interface - provides a service for the exchange of information between
each Node B and its controlling RNC.
• Iur interface - provides the service to enable an RNC to address any other
RNC within the UTRAN.
• Iu interfaces - provide the service of exchange of information between the RNC

and the core network (CN). The Iu interfaces as follows:
◦ Iu-CS interface - provides the interface between the RNC and the MSCu,
for the circuit-switched domain.
◦ Iu-PS interface - provides the interface between the RNC and the SGSNu,
for the packet-switched domain.
◦ Iu-O&M interface - provides the interface between the RNC and the Operations
and Maintenance Centre - UMTS (OMC-U), for the RAN.
• Uu interface - the radio interface between the UTRAN (RNC/Node B) and the UE.
The use of these standardized interfaces throughout the mobile network allows compatibility
between network elements from different manufacturers.
68P02905W21-B 2-15
02-Jun-2004
UMTS interfaces Chapter 2: Overview of UMTS
Figure 2-2 UMTS components and logical interfaces
PSTN PACKET DATA NETWORK

(PDN)
Gs
GMSCu MSCu SGSNu GGSNu
Iu-CS Iu-PS
Iu-PS Iu-CS
RNC Iur RNC
Iub Iub Iub Iub Iub Iub Iub Iub
NODE NODE NODE NODE NODE NODE NODE NODE

B B B B B B B B
Uu
UMTS functional layering
The layering of UMTS functions is partially based on the seven layer model for open systems interconnection
suggested by the ISO. Each layer performs a specific set of functions that are isolated and enhances those
performed by the lower layers. This philosophy facilitates a modular approach to implementation. The
functions occurring at one layer have only limited interaction with those at another. This provides a
degree of flexibility for future improvements without redesigning the entire system.
Layer 1 - Physical
Layer 1 comprises the physical channel layer and is concerned with transmitting and receiving
coded information symbols over the radio link.
Layer 2 - Transport
Layer 2 features include the multiplexing and demultiplexing of logical channels.
2-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS interfaces
Layer 3 - Management
Layer 3 provides for the three major management functions:
• Radio resource control (paging, cipher mode set, frequency redefinition, assignments,
handover, measurement reports, and so on).
• Mobility management (authorization, location updating, IMSI attach/detach,

periodic registration, ID confidentiality and so on).
• Call management (control, supplementary services, Dual Tone Multi-Frequency

(DTMF), Short Message Service and so on).
Figure 2-3 shows the UMTS functional layering.
Figure 2-3 UMTS functional layering
Management Layer
Radio Resource Mobility Call

Management Management Management
For example: For example: For example:
Paging Authentication Control
Layer 3 Cipher mode set Location updating Supplementary services
Frequency redefinition IMSI attach DTMF
Assignments IMSI detach Short Message Service
Handover Periodic registration
Measurements ID confidentiality
Reports
Transport Layer
Layer 2 Multiplexes and demultiplexes logical channels:
Traffic Signalling Synchronization
Control
Layer 1 Physical Channel Layer

Transmits and receives coded information symbols over the radio link
68P02905W21-B 2-17
02-Jun-2004
Core Network interfaces Chapter 2: Overview of UMTS
Core Network interfaces

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
A major portion of UMTS recommendations deals with standards for interfaces between network elements.
Connection between the RNC and the CN (MSCu, SGSNu) is through STM-1s.
These links support the following major interfaces defined by UMTS:
• B Interface: MSCu-to-VLR.
• C Interface: MSCu-to-HLR/AUC.
• D Interface: VLR-to-HLR.
• E Interface: MSCu-to-MSC.
• F Interface: MSCu-to-EIR.
• G Interface: VLR-to-VLR.
• H Interface: HLR-to-AUC.
The use of these standardized interfaces throughout the mobile network allows compatibility
between network elements from different manufacturers.
NMC interface
The interface between the NMC and OMC is defined by UMTS to use a Q3 protocol on a 64 kbit/s digital link.
Location Register interfaces
For the interfaces between the MSCu, VLR, HLR, and EIR, the lower level communication functions
also follow ITU-TSS recommendations for C7. At the application level, the messages used on these
interfaces are specified by UMTS as the Mobile Application Part (MAP).
Using standardized interfaces throughout the UMTS digital cellular system ensures compatibility
of network elements from different manufacturers.
2-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UTRAN network protocols
UTRAN network protocols

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
UMTS utilises a set of radio network protocols (one per logical channel) which are responsible
between the UTRAN components and the interfaces to the CN.
Protocols
The network protocols are:
Node B Application Part (NBAP)

The NBAP protocol is utilised between the RNC and Node B enabling the CRNC to
manage the radio resources of a given Node B.
Radio Network System Application Part (RNSAP)

The RNSAP protocol is utilised between RNCs when a UE requires multiple RNCs during macro-diversity.
Radio Access Network Application Part (RANAP)

The RANAP protocol enables the RNCs, and thereby the UTRAN, to communicate with the CN.
OSI/protocol relationship
Figure 2-4 shows the relationship between the OSI layers and the main protocols. In Figure 2-4, the
individual C7 protocols are shown, but not the interfaces on which these protocols are used.
68P02905W21-B 2-19
02-Jun-2004
UTRAN network protocols Chapter 2: Overview of UMTS
Figure 2-4 OSI layers - main protocol relationships
OSI Layers C7 Levels C7 X25 Others

Application 7
MAP
BSSAP
Presentation 6 (DTAP+BSSAP)
4 TUP ISUP
X25
Session 5 TCAP Applications
Transport 4 SCCP
Network 3 3 MTPb Level 3 Abis

X25
2 MTP Level 2 LAPD
Link 2
1 MTP Level 1
Physical 1 G.732
Network protocols
Figure 2-5 shows the UTRAN logical interfaces with the corresponding CN signalling protocols.
2-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UTRAN network protocols
Figure 2-5 Radio network CN protocols
NBAP
NODE B
Iub
RANAP
NODE B Iub RNC
Iu
Iub
NODE B
Iur
CN
RANAP
NODE B
Iub
Iu
NODE B Iub RNC
RANAP
Iub
NODE B
NBAP
ITU-TSS signalling system 7
The ITU-TSS signalling system 7 (C7) protocol is composed of several parts: the Message
Transfer Part (MTP), the Signalling Connection Control Part (SCCP), the X.25 link, the
LAPDm protocol, and various signalling link protocols.
Message Transfer Part broadband (MTPb)

MTPb is part of the C7 protocol that is used throughout the network. MTPb provides layers 1, 2 and 3 of the
seven layer model. MTPb is the transport system for reliable transfer of messages between users.
68P02905W21-B 2-21
02-Jun-2004
UTRAN network protocols Chapter 2: Overview of UMTS
The three functions involved in MTPb are:

• MTPb1 - Signalling data link functions.
Physical, electrical and mechanical specifications for the interface.
• MTPb2 - Signalling link functions.

Defines the functions and procedures for controlling the transfer of signalling
messages over a signalling link.
• MTPb3 - Signalling network functions.

Defines the methods for message handling and routing on a signalling link.
MTPb uses three types of Signalling Units (SU) to transmit information:

• MSU - Message Signalling Unit.
• LSSU - Link Status Signalling Unit.
• FISU - Fill-In Signalling Unit.
Signalling Connection Control Part (SCCP)

The SCCP is a layer 3 protocol and provides network connectivity as required.
The SCCP forms part of the Signalling Information Field (SIF) in the MTPb signalling unit.
The SCCP can operate in four modes. Two of these modes are used for GSM. Protocol class
numbers carried in the mandatory fixed field of the SCCP message indicate which mode
is being used. The two modes used for GSM are:
• Connectionless. Protocol Class 0 - Single messages are sent to other SCCP users. The
Unit Data (UDT) is the only type of message sent in connectionless mode.
• Connection-oriented. Protocol Class 2 - A signalling connection is established before messages

are sent. The following SCCP message types must be passed to establish this connection:
◦ CR - Connection Request.
◦ CC - Connection Confirm.
◦ CREF - Connection Refused.
◦ DT1 - Data form 1.
◦ IT - Inactivity Test.
Once the communication is complete the link must be released. The following
SCCP message types are used to release the connection:
• RLSD - Released.
• RLC - Release Complete.
2-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview E1/STM-1 links
E1/STM-1 links
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
UMTS uses two types of operating links:

• E1
• STM-1
These provide the physical links on the network. Communication between the PSTN, MSCu and BSS
equipment is over E1 links. X.25 and C7 information are sent using the physical protocols on these links.
E1 link
The E1 link has a signalling rate of 2.048 Mbit/s and provides thirty-two 64 kbit/s
timeslots, of which 30 are generally available:
• Timeslot 0 is always reserved for synchronization purposes.
• Although the remaining 31 are available for PCM or data channels, one
is normally reserved for control.
The E1 link is sometimes referred to as a 2 Mbit/s link or bearer.
STM-1 link
The frame has a repetitive structure with a period of 125 microseconds – the same as for pulse code modulation
(PCM) – and consists of nine equal-length segments. At the gross transport rate of 155.52 Mbps for the base
synchronous transport module (STM-1), there is a burst of nine overhead bytes at the start of each segment.
68P02905W21-B 2-23
02-Jun-2004
Wideband Code Division Multiple Access (W-CDMA) Chapter 2: Overview of UMTS
Wideband Code Division Multiple Access (W-CDMA)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to W-CDMA
UMTS employs Wideband Code Division Multiple Access (W-CDMA) as the means
of allocating radio spectrum.
W-CDMA is a form of spread spectrum technique. It has many advantages over other multiple access
techniques such as Frequency Division Multiple Access (FDMA) and Time Division Multiple Access
(TDMA), including greater spectral efficieny and greater immunity to interference and noise.
Cocktail party analogy
The concept of W-CDMA can be explained by the cocktail party analogy.

Groups of people in a room, speaking different languages, can communicate simultaneously despite
the surrounding noise. The language each group are using allows them to talk to each other, whilst
filtering out the noise of the other conversations in different languages.
However if the noise is recorded, someone who knows the various languages, could playback
the tape several times, and extract the different conversations. If there are several listeners to
the tape, all the conversations could be extracted simultaneously.
W-CDMA techniques
Unlike FDMA and TDMA, the carrier is not split into frequency bands or shared on a time basis. Instead
the signal is spread over a wider spectrum and allocated an individual code.
The user data signal to be transmitted, is multiplied by a pre-defined bit pattern called a spreading
code. The symbols of the spreading code are referred to as chips, and following the spreading
operation, the user data signal is represented by a number of chips. The chip rate for UMTS
is 3.84 Mchip/s, which enables a bandwidth of 5 MHz.
As the user data signal is spread over the bandwidth, the amplitude is reduced to that of noise level.
The degree to which the original data signal is widened to fill the available spectrum is called the
spreading factor; the higher the data rate, the lower the spreading factor.
Multiple access users have different spreading codes but occupy the same frequency band. The
W-CDMA receiver removes the spreading code to extract the original signal.
In UMTS, the uplink and downlink paths are separated by Frequency Division Duplex (FDD). Paired
frequencies are used for the uplink and downlink spaced at 190 MHz.
2-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Wideband Code Division Multiple Access (W-CDMA)
Advantages of W-CDMA
W-CDMA has many advantages over FDMA and TDMA systems:

• Wide bandwidth
In UMTS, the whole of the 5 MHz bandwidth is available for each users, unlike FDMA
where it is shared on a frequency basis, or TDMA where it split into timeslots.
• Greater spectral efficiency
• Immunity to interference and noise

The use of W-CDMA permits to average interference among all users, thus avoiding to
dimension a network for the worst case. It thus permits to optimise the use of spectrum
efficiency. It also efficiently supports variable bit rate services.
• Frequency reuse factor of 1

W-CDMA allows a reuse factor of 1, the same frequency being used in adjacent cells. The
need for frequency planning is removed, code planning is required instead. However, this
is less difficult than frequency planning, as the code reuse pattern is much larger than
the frequency reuse pattern commonly employed in FDMA systems.
• Reduced transmitter power

Average and peak transmitter power is reduced, thus power amplifier power consumption
is also reduced and battery efficiency is increased.
Power control
Referring again to the cocktail party analogy, if somebody starts talking louder, they will disturb the other
conversations. To be still able to understand each other, the other groups will also start talking louder. If too
many people are present (or if too many people talk too loudly), it becomes impossible to understand anything.
For this reason, W-CDMA requires complex and very accurate power control, which is a
key factor for the system capacity and proper operation.
The power control problem implies the need to sometimes control the user equipment from more
than one place. This is known as macrodiversity or soft handover.
68P02905W21-B 2-25
02-Jun-2004
Wideband Code Division Multiple Access (W-CDMA) Chapter 2: Overview of UMTS
W-CDMA features
Wideband W-CDMA (W-CDMA) is the variant of CDMA used in UMTS.

Table 2-1 summarizes some of the features of W-CDMA.
Table 2-1 W-CDMA features
Duplexing method Frequency Division Duplex (FDD)

Chip rate 3.84 Mchip/s
Bandwidth 5 MHz
Carrier spacing 200 kHz
Frame length 10 ms
Spreading factor Variable (4-512)
User data rate 3-384 kbit/s
Further information
For further information about W-CDMA theory, see Chapter 10.
2-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS frequencies
UMTS frequencies
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Worldwide spectrum allocation for IMT-2000
After the World Administration Radio Conference (WARC 92), the allocation of frequencies per region has
been varied. International Mobile Telephone-2000 (IMT-2000) recognized the frequencies to be 1885 MHz to
2025 Mhz in the lower band and 2110 Mhz to 2200 Mhz in the upper band. Each band was split into satellite
(MSS) and terrestrial IMT-200 parts. Not all countries could utilize exactly this range of frequencies because
they already have other systems operating in these bands. Therefore they vary as can bee seen in Figure 2-6.
Europe
Europe has used part of the band for DECT, which has very low penetration. It also has GSM
at the lower edge. The band is also split in FDD and TDD bands.
China
China has left the band clear and will start IMT-200 activities soon. This will split into WLL and Mobile.
Japan
Japan has developed with Korea the DoCoMo system which is pre-release.
PCS
UTRA FDD for Region 2 - Re-farming A, B, C, D, E, F Bands currently used for PCS. EDGE will
be developed on the PCS frequencies and some TV frequencies in 2006.
68P02905W21-B 2-27
02-Jun-2004
UMTS frequencies Chapter 2: Overview of UMTS
Figure 2-6 Worldwide spectrum allocation for IMT-2000
1850 1900 1950 2000 2050 2100 2150 2200 2250 Mhz
1885 1900 1980 20102025 2110 2170 2200

ITU Allocations IMT 2000 MSS IMT 2000 MSS
1880
Europe GSM
DECT UMTS MSS UMTS MSS
1800
WLL WLL
China GSM IMT 2000 MSS IMT 2000 MSS
1800
1893 1919
Japan MSS =
PHS IMT 2000 MSS IMT 2000 MSS
Korea (w/o PHS) Mobile Satellite
Services
1990 2160
M
MDS =
North PCS Multipoint Service/
MSS D
Reserve MSS
America A DB E F C A D B E F C S Mobile Data Service
1850 1900 1950 2000 2050 2100 2150 2200 2250 Mhz
CP13_Ch1_07
European frequency allocation
The frequency allocation for Europe is split into two frequency bands:
• Lower: 900 MHz to 2025 MHz
• Upper: 2110 MHz to 2200 MHz
Owing to the asymmetric nature of the frequency allocation, frequencies have been additionally allocated
into paired and unpaired bands. The frequency range 1920 to 1980 MHz and 2110 to 2170 MHz are
available to operators as paired bands. These support FDD that is best suited to symmetric services
such as telephony. The frequency Uplink (UL) and Downlink (DL) separation is 190 MHz. The lower
band 1900 to 1920 MHz and 2010 to 2025 MHz are available as unpaired bands. These can support
TDD, which is best suited to asymmetrical services such as the Internet.
Figure 2-7 illustrates the European frequency allocation, showing Frequency Division
duplexing (FDD), and Time Division duplexing (TDD).
2-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS frequencies
Figure 2-7 European frequency allocation
1805
1880
1900
1920
1980
2010
2020
2025
Uplink 12 x 5 MHz
MSS
TDD
TDD
FDD
SPA
GSM
DECT
1800
20MHz 60MHz 30MHz
140MHz
2110
2170
2200
Downlink 12 x 5 MHz 6 x 5 MHz
MSS
FDD
190MHz between up-

link and down-link
60MHz 30MHz
90MHz
CP13_Ch1_08
68P02905W21-B 2-29
02-Jun-2004
Mobile services Switching Centre for UMTS (MSCu) Chapter 2: Overview of UMTS
Mobile services Switching Centre for UMTS (MSCu)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Mobile services Switching Centre for UMTS (MSCu) coordinates the setting up of calls to and from UMTS
users. It is the telephone switching office for MS originated or terminated traffic and provides the appropriate
bearer services, teleservices and supplementary services. It controls a number of Node Bs within a specified
geographical coverage area and gives the radio subsystem access to the subscriber and equipment databases.
The MSCu controls the call set up and routeing procedures in a similar way to a land network end office
controlling land line calls. On the land network side, the MSCu performs call signalling functions using the
ITU-TSS C7 communications protocol. The forms of the protocol used are Telephone User Parts (TUPs)
on the interface to the PSTN and ISDN User Part (ISUP) on the interface to the ISDN.
MSCu functions
The MSCu acts as an exchange for all types of mobile calls: local, national, and international. The
following are mobile-specific call processing functions in the MSCu:
• Provision of access to the VLR and HLR.
• Provision of access to the EIR.
• Processing of telecommunication services and supplementary services.

(For example, Short Message Service).
• Mobility management, for example:

◦ Interrogation of MS.
◦ Paging.
◦ Handover.
◦ Call re-establishment.
◦ Location updating: interrogation and updating of VLR and HLR.
• Interworking between the signalling systems of fixed networks and the

signalling system of the RNS.
• Resource handling:
◦ Queuing.
◦ Off-air call set up.
• Mobile subscriber charging.
2-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Mobile services Switching Centre for UMTS (MSCu)
• Inter-administrative revenue accounting.
• Security functions.
• Simultaneous and alternate use of services.
• Interworking for dual tone multifrequency signals.
• User information language.

(For example, recorded announcements).
Gateway MSC
When the MSC provides the interface between the fixed and mobile networks, it is known as the Gateway
MSC (GMSC), since it gives the mobile network access to the land lines of the PSTN, ISDN and data
networks. It may also provide specific InterWorking Functions (IWFs) to other networks.
MSCu flexible design
The UMTS recommendations define the functions of the MSCu, but allow flexibility in its design.
• The most common solution is to combine the functions of the MSC, VLR, HLR, AUC and
EIR into one functional node. This has the advantage that the dynamic load, caused for
example by interworking through C7 signalling links, is kept to a minimum.
• Another approach is to separate all functional elements into separate network nodes.
• A third solution consists of combining functional elements in accordance with

the requirements of the operating company. For example, the MSC and VLR
can be combined, as can the HLR and AUC.
In practice, due to the transmission capacity of C7, the MSC should not be separated
from the VLR, nor the HLR from the AUC.
68P02905W21-B 2-31
02-Jun-2004
MSCu interfaces
The MSCu has interfaces to the following:

• OMC-U.
• Other MSCs within the same PLMN.
• UTRANs.
• Location registers: HLR, VLR and EIR.
• Emergency Service Centre.
• Service Centre (SC) - Used for Short Message Service.
• Other networks, including the PSTN/ISDN, PDN and other PLMNs.
Iu-CS interface
This interface between the MSCu and the RNS is defined as the Iu interface. The interface is based on the
use of STM-1 digital links. The channels on these links can be used for traffic or signalling.
The Iu interface provides facilities to the traffic channels and signalling links for the following functions:
• Terrestrial management: allocation and blocking of the terrestrial traffic channels.
• Radio channel management: RNS management - radio channel allocations/control.
• Mobility management: location update - transparency between the MS and MSCu.
• Call control: set up for mobile originating/terminating calls.
• Supplementary services: transparency through the RNS.
Layered signalling
The signalling is layered, similar to that in the OSI reference model. However, the layers
referred to are not identical but are specified by ITU-TSS C7.
Location Register interfaces
The lower level communication functions for the interfaces between the MSC, VLR, HLR, and EIR
follow ITU-TSS recommendations for C7. At the application level, the messages used on these
interfaces are specified by UMTS as the Mobile Application Part, or MAP.
2-32 68P02905W21-B
02-Jun-2004
Call control
The MSCu performs call control functions such as number translations and routeing, matrix path control,
and allocation of outgoing trunks. It maintains PLMN synchronization and provides synchronization to
its RNSs. The MSCu also collects traffic statistics for performance management purposes.
Emergency calls
An international emergency number allows UMTS subscribers to make emergency calls wherever they are.
The MSCu receives the emergency call set up message, and routes the call to the appropriate emergency centre.
Short Message Service (SMS)
The Service Centre (SC) sends point-to-point short messages destined for an MS to the GMSC.
• The GMSC checks for errors, interrogates the HLR to determine the location of the MS and
transfers the message to the appropriate MSC. (The GMSC and the MSC may be the same
equipment.) The MSC uses call set up parameters from the VLR to establish the call, and
reports the outcome back to the GMSC which in turn reports to the MSC.
• If the message is unsuccessful, the GMSC requests the HLR to store the SC address as a
Message Waiting Data for the MSISDN. The HLR determines when the MS is next ready
to receive a message, and informs the MSC that has the interworking interface with the SC.
(The interworking MSC and the MSC may be the same equipment.) The interworking MSC
in turn informs the SC so that a further attempt to send the message can be made.
• MSCs also handle short messages sent from an MS. The MSC local to the MS checks
the message for errors and transfers it to the appropriate interworking MSC. The
interworking MSC transfers the message to the destination SC, receives the outcome
and reports it back to the MSC, which reports it to the MS.
MSCs only handle point-to-point short messages. Short messages broadcast to all MSs in
a cell may be handled by the OMC and the UTRAN.
68P02905W21-B 2-33
02-Jun-2004
Security procedures
Other functions performed by the MSCu are unique to the mobile environment. The MSCu supports the
security procedures used to control access to the radio channels. These procedures include:
• Passing keys to the RNS which are used to validate the identity of the
mobile equipment and the subscriber.
• Encrypting the data sent on the traffic channel and control channels.
Local registration and call handover
In addition to the call set up procedures, the Mobile Switching Centre/Visitor Location Register
(MSC/VLR) also controls location registration and some handover procedures. Location registration
(and location update) allows Mobile Stations/User Equipment (MSs/UEs) to report changes in their
locations, enabling automatic completion of MS/UEs terminated calls. The handover procedure preserves
call connections as MSs/UEs move from one radio coverage area to another during an established
call. Handovers within cells controlled by a single BTS/RNC are controlled by that BTS/RNC.
When handovers are between cells controlled by different BTS/RNC, the primary control is at the
MSCu/VLR. Figure 2-8 shows how the two types of handover are achieved.
2-34 68P02905W21-B
02-Jun-2004
Figure 2-8 Handover control
MSC/VLR
BSC
BSC
BTS BTS
BSC
UMTS MS
BTS BSC MSC/VLR GMSC/VLR
PSTN
HLR
UMTS MS
/ UMTS
UE
PSDN
INTERNET
NODE B RNC SGSN GGSN
MS MOBILE STATION
UE USER EQUIPMENT
RNC
UMTS UE
NODE B NODE B
68P02905W21-B 2-35
02-Jun-2004
Inter-MSC handovers
Handovers between MSCs/VLRs can also be performed between RNSs connected to two different
MSCs/VLRs. In these handovers, the MSC/VLR where the call originates functions as the
primary MSC/VLR, and retains ultimate control of the call through out its duration, even though
the call processing tasks are handed over to another MSC/VLR.
The Equipment Identity Register (EIR) option, is a centralized database for validating the
international mobile station equipment identity, the IMEI.
The database contains three lists:
• The white list contains the IMEIs of valid MSs.
• The grey list contains IMEIs of equipment to be monitored and observed

for location and correct function.
• The black list contains IMEIs of MSs which have been reported stolen or are to be denied service.
Figure 2-9 summarises the three database lists.

The EIR database is remotely accessed by the MSCs in the network. The EIR can also be accessed
by an MSC in a different PLMN. A given PLMN may contain more than one EIR, in which case
each EIR controls certain blocks of IMEI numbers. The MSC contains a translation facility, which,
when given an IMEI, returns the address of the proper EIR to access.
Figure 2-9 Database list summary
WHITE LIST GREY LIST BLACK LIST
ALL VALID SERVICE ALLOWED SERVICE

ASSIGNED IDs BUT NOTED DENIED
MOBILE 1 MOBILE 5 MOBILE 9

MOBILE 2 MOBILE 6
MOBILE 10
MOBILE n MOBILE n
MOBILE n
Home Location Register (HLR)
Figure 2-10 shows the Home Location Register (HLR), which is a database of subscriber information used in
setting up calls. Various identification numbers and addresses are stored as well as authentication parameters,
services subscribed, special routeing information. The current status of the subscriber is maintained.
2-36 68P02905W21-B
02-Jun-2004
Figure 2-10 HLR configuration
MSC MSISDN HLR

(HOME LOCATION
REGISTER)
MSISDN
or IMSI MSISDN
EXTERNAL For Example: VLR
PLMN BASIC SERVICE LIST
SUPPLEMENTARY
SERVICE LIST
CURRENT VLR
IMSI CALL FORWARD
NUMBER IMSI
MSC
VLR
HLR master database

The HLR contains the master database of the subscribers to a PLMN. This data is remotely accessed
by the MSCs and VLRs in the network. A PLMN may include more than one HLR, in which case
each HLR contains a portion of the total subscriber database. The subscriber data may be accessed by
either the IMSI or the mobile subscriber ISDN number. The data can also be accessed by an MSC
or a VLR in a different PLMN to allow inter-system and inter-country roaming.
HLR data
The data stored in the HLR indicates which basic and supplementary services a given subscriber is
allowed to use. This data is changed only when new subscribers are added or deleted, or the specific
services they subscribe to are changed. The HLR data also includes temporary information related
to supplementary services such as the current call forwarding number.
A subscriber’s HLR entry also includes the address of his current VLR. This information, in connection
with the VLR data explained below, allows completion of calls to the mobile subscriber.
Authentication Centre (AUC)
The HLR function may also include the Authentication Centre (AUC) as shown in Figure 2-11.
The AUC generates and stores the parameters necessary to authenticate a subscriber’s
identity so as to guard against fraudulent system use.
68P02905W21-B 2-37
02-Jun-2004
Figure 2-11 Authentification centre configuration
AUTHENTICATION
CENTRE
AUTHENTICATION
KEY
ONE PER
REQUEST FOR SUBSCRIBER SIGNED
AUTHENTICATION RESPONSE
ALGORITHM To VLR
PROCESS
RANDOM
NUMBER RANDOM
GENERATOR NUMBER
To MS
2-38 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Authentication and Key Agreement
Authentication and Key Agreement

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Authentication and Key Agreement (AKA) achieves mutual authentication by the user and the network
showing knowledge of a secret key K which is shared between and available only to the USIM and
the AuC in the user’s HE. In addition the USIM and the HE keep track of counters SEQMS and SEQHE
respectively to support network authentication. The method was chosen in such a way as to achieve
maximum compatibility with the current UMTS security architecture and facilitate migration from UMTS
to UMTS. The method is composed of a challenge/response protocol identical to the UMTS subscriber
authentication and key establishment protocol combined with a sequence number-based one-pass
protocol for network authentication derived from the ISO standard ISO/IEC 9798-4
Distribution of authentication data from HE to SN
Upon receipt of a request from the VLR/SGSN, the HE/AuC sends an ordered array of n authentication
vectors (the equivalent of a UMTS “triplet") to the VLR/SGSN. Each authentication vector consists
of the following components: a random number RAND, an expected response XRES, a cipher key
CK, an integrity key IK and an authentication token AUTN. Each authentication vector is good for
one authentication and key agreement between the VLR/SGSN and the USIM.
Authentication and Key Agreement
When the VLR/SGSN initiates an authentication and key agreement, it selects the next authentication
vector from the array and sends the parameters RAND and AUTN to the user. The USIM
checks whether AUTN can be accepted and, if so, produces a response RES which is sent back
to the VLR/SGSN. The USIM also computes CK and IK.
The VLR/SGSN compares the received RES with XRES. If they match the VLR/SGSN
considers the authentication and key agreement exchange to be successfully completed. The
established keys CK and IK will then be transferred by the USIM and the VLR/SGSN to the
entities which perform ciphering and integrity functions.
This is illustrated in Figure 2-12.
68P02905W21-B 2-39
02-Jun-2004
Authentication and Key Agreement Chapter 2: Overview of UMTS
Figure 2-12 Authentication and Key Agreement
MS SN/VLR HE/HLR
Authentication request
Distribution Generate
authentication vectors vectors AV (1 . . . n)
from HE to SN Authentication data response
AV (1 . . . n)
Store authentication vectors
Select authentication vectors

User authentication request
RAND(i) || AUTN(i)
Verify AUTN(i)
compute User authentication Authentication Key
RES(i)
Compare RES(i) and XRES(i)
Compute CK(i) and IK(i) Select CK(i) and IK(i)
CP13_Ch3_13a
Visited Location Register (VLR)
Figure 2-13 shows the Visited Location Register (VLR), which is a local subscriber database, holding
details on those subscribers who enter the area of the network that it covers. The details are held in
the VLR until the subscriber moves into the area serviced by another VLR. The data includes most of
the information stored at the HLR, as well as more precise location and status information. The VLR
provides the system elements local to the subscriber, with basic information on that subscriber, thus
removing the need to access the HLR every time subscriber information is required.
2-40 68P02905W21-B
02-Jun-2004
Figure 2-13 Visited location register configuration
VLR
(VISITED LOCATION
REGISTER)
MSRN
(MOBILE STATION
VLR Database ROAMING MSRN
NUMBER)
GENERATOR
COPY OF SELECTED
IMSI DATA FROM HLR HANDOVER
INTERROGATION TMSI DATABASE FOR ALL HANDOVER NUMBER
ACCESS MODES SUBSCRIBERS NUMBER
MSRN CURRENTLY IN AREA GENERATOR
SERVICED BY THIS
VLR
TMSI
(TEMPORARY MOBILE NEW TMSI
SUBSCRIBER IDENTITY)
GENERATOR
Controlling LAIs
Circuit Switched only

Cells in the PLMN are grouped into geographic areas and each is assigned a Location Area Identification
(LAI). Each VLR controls a certain set of LAIs. When a mobile subscriber roams from one LAI to another,
the current location is updated in his VLR entry using the location validate procedure. If the old and new LAIs
are under control of two different VLRs, the entry on the old VLR is deleted and a new entry is created at the
new VLR by copying the basic data from the HLR entry. The subscriber’s current VLR address, stored at the
HLR, is also updated. This provides the information necessary to complete calls to the mobile subscriber.
68P02905W21-B 2-41
02-Jun-2004
Location structures and their identities

In addition to addressing and identitying the subscribers and their terminals, the Mobility Management
(MM) needs to define the network in a logical structure. The structure is defined as parts of
the access network, consequently these structures act as a map for MM procedures and their
parmeterization. UMTS has four level of logical definitions, they are:
• Location Area (LA)
• Routeing Area (RA)
• UTRAN Registration Area (URA)
• Cell
Within the Core Network (CN) Circuit Switched (CS) domain, the UE can move within the LA without
performing an update procedure. The LA is composed of cells, the minimum being one, whilst the maximum
being all the cells under one VLR. Within the LA the UE is updated in the VLR since the UE may terminate a
call. In turn the VLR pages the required UE from the LA from which it has carried out the last update.
Every LA has a unique Location Area Identity (LAI). The LAI is subdivided into the following parts:
LAI = MCC + MNC + LA code
Mobile Country Code (MCC) and Mobile Network Code (MNC) are the same format as the
International Mobile Subscriber Identity (IMSI) code. The LA code is a number identifying the LA.
The LAI is a unique number and within the same network should not be repeated. One VLR is unable to
handle duplicate LA codes. The transport channel BCH provides the LAI(s) from which the UEs listen
to. The content of this transport channel is cell-specific and contains only RNC information.
The Packet Switched (PS) domain has its own location registration based on the Routeing Area. Like the LA,
the RA is an area where the UE may move without performing an RA update. However, the RA is a subset of the
LA, one LA can have several RSs within it but not vice versa, also, one RA cannot belong to two location areas.
Figure 2-14 illustrates the logical entities and their relationships.
2-42 68P02905W21-B
02-Jun-2004
Figure 2-14 MM logical entities and their relationships
LA
RA
URA URA
URA URA
KEY
LA = LOCATION AREA
RA = ROUTEING AREA
URA = UTRAN ROUTEING AREA
= CELL
The VLR and SGSN have an optional connecting interface Gs through which nodes may communicate. The
UMTS has to interrogate with UMTS, the UMTS CN supports also features available in UMTS. One of these
features is a combined location/RA update, here the UMTS terminal performs updated requests to the
SGSN first. Should the Gs interface be available, the SGSN also requests the VLR (through its interface),
to update the location area registration. However in the plain UMTS network, the combined location/RA
area update is not available and a UE registers its location to both CN domains independently.
68P02905W21-B 2-43
02-Jun-2004
Within UMTS the network the MM is completely handled between the terminal and NSS, while in UMTS
the UTRAN is partially involved in MM. Due to this the UTRAN contains local mobility registration, as a
consequence the 3G SGSN contains both 2G SGSN and 3G SGSN functionality. The difference between the
two is that in 3G UMTS, the SGSN carries tunnelled IP traffic to/from a UE according to the URA identity,
whilst in 2G the SGSN terminates the tunnelled IP traffic and relays it over the 2G-specific Gb link.
As the URA has a similar logical definition (as opposed to LA and RA), in principle, it does not
have any limitations in respect of network elements. In practice, the URA and Radio Network
Subsystem (RSN) have more or less fixed relationships. However the URA is not a logical
definition which combines traffic routeing and radio resource control.
In routeing the URA, the addressing entity is pointing towards the access domain and in the radio resource
control the terminal has states indicating the location accuracy and traffic reception ability.
The smallest unit used for the preceding MM logical entities is a cell. The CN does not need to be aware
of cells directly, but sets of cells, or areas. The cell in the access domain is the smallest entity having its
own publicity visible identity call (Cell ID (CI)). Similar to the LA code, the CI is also just a number, which
should be unique withn the network. In order to globally separate cells from each other, the identity must be
expanded and in this case is called Cell Global Identity (CGI). The CGI has the following format:
CGI = MNC + MCC + LA code + C
The CGI value will cover the country of the network (MCC), the network within a country (MNC), the
location area within the network and finally the cell number within the network. This information is
sent to the UE through the UTRAN functionally for system information broadcasting.
Controlling MSRNs
The VLR also controls the assignment of Mobile Station Roaming Numbers (MSRNs). When an MS
receives an incoming call, the HLR requests the correct VLR for a MSRN, the VLR selects an MSRN
from its pool of numbers and returns it to the MSC that initially handled the call. The call is then
forwarded using the MSRN as the called address. The MSRN causes the call to be routed to the MSC
which controls the base stations in the area where the MS is currently located.
Allocating handover numbers
The VLR also allocates handover numbers for use in inter-MSC handovers. These handovers require the call to
be re-routed from the source MSC to the target MSC. The handover number functions similarly to an MSRN,
in that it allows the required trunk connection to be set up by routeing the call through the land network.
Allocating TMSI numbers
The VLR also controls allocation of new Temporary Mobile Subscriber Identity (TMSI) numbers.
A subscribers TMSI can be periodically changed to secure the subscriber’s identity. The system
configuration database controls when the TMSIs are changed. Options include changing the TMSI
during each location update procedure or changing it within each call set up procedure.
The database in the VLR can be accessed by IMSI, TMSI, or MSRN. Typically, there will be
one VLR per MSC, but other configurations are possible.
2-44 68P02905W21-B
02-Jun-2004
Call handling
The following sections illustrate the functions of the MSC in handling mobile-originated or -terminated traffic.
MS to PSTN subscriber
Figure 2-15 shows a call from an MS to a subscriber in the land network (that is, the PSTN). The MSC acts as
an outgoing exchange. If the call is directed to another country, the MSC routes it to the International Switching
Centre. If the call is to a subscriber on the national network, the call is routed to the PSTN, which sets up the
connection to the PSTN subscriber. The MSC performs the same function for a call directed to the ISDN.
Figure 2-15 MS to PSTN subscriber call
PLMN
VLR
MSC
RAN
MS
PSTN/
ISDN
PSTN subscriber to MS
Figure 2-16 shows a call from a subscriber in the land network (that is, the PSTN) to an MS. The
assumption is that the PSTN cannot interrogate the HLR, so the call has to be directed to the Gateway
MSC which performs the interrogation. The MSRN is then used to route the call to MSC-B which
pages MS-B and sets up the call to it. The connection between the Gateway MSC and MSC-B may
be routed through one or more transit exchanges of the national ISDN/PSTN.
68P02905W21-B 2-45
02-Jun-2004
Figure 2-16 PSTN subscriber to MS call
PSTN/ISDN
PLMN
MSC-B GMSC
RAN
VLR HLR
MS-B
MS to MS calls
The scenarios covered include:
• A call between MSs in the same PLMN.
• A call between MSs in different PLMNs in the same country.
• A call between MSs in different PLMNs in different countries.
MS to MS (same PLMN)
Figure 2-17 shows a call between a calling MS (MS-A) and a called MS (MS-B) in the same
PLMN. MSC-A analyses the called number for MS-B, via the VLR. It interrogates the HLR
to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts as an incoming
exchange and establishes the call to MS-B. The connection between the two MSCs may be routed
through one or more transit exchanges of the national ISDN/PSTN.
2-46 68P02905W21-B
02-Jun-2004
Figure 2-17 MS to MS call (same PLMN)
PLMN
HLR VLR
MSRN of MS-B
RETRIEVED
MSC-A
RAN
MS-A
VLR
PSTN/ISDN
MSC-B
RAN
MS-B
MS to MS (different PLMN/same country)

Figure 2-18 shows a call between a calling MS (MS-A) in one PLMN and a called MS (MS-B)
in another PLMN. MSC-A analyses the called number for MS-B. It interrogates the HLR of
the other PLMN to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts
as an incoming exchange and establishes the call to MS-B.
68P02905W21-B 2-47
02-Jun-2004
Figure 2-18 MS to MS call (different PLMN)
PLMN
VLR
MSC-A
RAN
MS-A
PSTN/
ISDN
PLMN
HLR VLR
MSC-B
RAN
MS-B
MS to MS (different PLMN/different country)

Figure 2-19 shows a call from an MS (MS-A) in one PLMN to an MS (MS-B) in a PLMN in another
country. MSC-A determines from the international prefix that the call is directed to another country but
cannot determine the location of the called MS. The call is therefore routed to the Gateway MSC in the
other country which interrogates the HLR to discover the MSC area where MS-B is currently located.
The HLR returns the MSRN and the call is routed to MSC-B. MSC-B acts as an incoming exchange
and establishes the call to MS-B. The connection between the GMSC and whichever MSC area MS-B
roams to, may be routed through one or more exchanges of the national ISDN/PSTN.
2-48 68P02905W21-B
02-Jun-2004
Figure 2-19 MS to MS call (different PLMN/different country)
PLMN 1
VLR
MSC-A
RAN
MS-A
PSTN/ISDN
PSTN/ISDN
PLMN 2 GMSC
MSC-B
RAN
VLR HLR
MS-B
68P02905W21-B 2-49
02-Jun-2004
Network Management Centre (NMC) Chapter 2: Overview of UMTS
Network Management Centre (NMC)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Network Management Centre (NMC) is an element defined by the UMTS recommendations
for managing an entire UMTS cellular network.
Functions
It performs the following functions:

• Monitors trunk routes between nodes on the network.
• Monitors high level alarms.
• Monitors OMC regions and provides assistance to OMC staff.
• Passes information from one OMC region to another to improve problem solving strategies.
• Enables long-term planning for the entire network.
National management
The NMC performs overall management of the PLMN, being responsible for operations and maintenance at
the network level and managing traffic on the network. It is a single control point in systems with multiple
MSCs, with the ability to co-ordinate interconnects to networks such as alternative PSTNs.
Monitoring equipment
The OMC-U system provide the NMC with information about the network equipment. The NMC monitors
this information for high level alarms, such as a failed or overloaded network node, and also monitors the
status of automatic controls applied at the network equipment in response to conditions such as overload.
NMC operators monitor the network status, and in the event of a problem are able to give guidance to staff
at the appropriate OMC, according to the ability of other regions to handle traffic flow increases.
2-50 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Network Management Centre (NMC)
Monitoring routes
The NMC monitors the signalling and trunk routes between nodes to prevent an overload condition
propagating through the network. Routes between the PLMN and the PSTN are also monitored to avoid
propagation of overload conditions between networks. NMC staff are able to co-ordinate network
management controls with the NMC facilities supporting the other networks.
Managing traffic
The NMC also manages traffic on UTRAN network equipment. In extreme circumstances NMC
operators are able to invoke controls such as priority access, as described in UMTS recommendation
2.11. The control of traffic on the signalling and traffic routes between the MSC and UTRAN can
be used to isolate overloading problems within a region. The NMC provides its operators with the
ability to reconfigure cell parameters as needed and to force handovers.
Simulating the OMC
The NMC may be able to take regional responsibility when an OMC is not manned, with the
OMC acting as transit point between the NMC and the network equipment. In this instance, the
NMC can provide operators with functions equivalent to those available at the OMC. The NMC
also supports planned changes to, or expansion of the network.
Interface
The interface between the NMC and OMC is defined by UMTS to use Q3 protocol on a 64 kbit/s digital link.
68P02905W21-B 2-51
02-Jun-2004
Quality of Service (QoS) Chapter 2: Overview of UMTS
Quality of Service (QoS)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to QoS
From a user viewpoint, Quality of Service (QoS) is the collective effect of service performances
which determine the degree of satisfaction which the user has of a service. It is characterised by the
combined aspects of performance factors applicable to all services, such as:
• Service operability performance.
• Service accessibility performance.
• Service retainability performance.
• Service integrity performance.
• Other factors specific to each service.
The QoS features also allow an operator to maximise revenue opportunity by providing a range of
services which fill available traffic capacity whilst offering premium rates for those users who require
low-delay higher capacity links. For example, a background service can be used to download e-mail
overnight while an interactive service can be used for more demanding applications. Requirements can
therefore be matched to the user expectations (based on tariff) of service delivery.
To implement the QoS features, UMTS terminals and UTRAN, which support QoS must be
deployed. In the GPRS core network, these capabilities are available as a feature in the standard
GSN and are provided by a software upgrade to the GSN components.
The QoS feature places an additional processing load on the hardware (mostly the SGSNu)
especially for conversation, streaming and real-time services. In conditions where a substantial
percentage of the traffic is conversational (more than 10%) additional hardware would be
required in the SGSNu to ensure maximum capacity.
From an operator viewpoint, the benefits of implementing the QoS features are as follows:
• The ability to maximise premium revenue from high quality packet data services.
• The ability to utilise all available capacity with appropriate data traffic.
• The flexibility to offer a wide range of services based on a common infrastructure.
2-52 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Quality of Service (QoS)
QoS operation
When a terminal initiates a GPRS session (referred to as a PDP context), additional parameters are
specified which request the bandwidth and QoS for the individual session.
This results in the following:
• The request is made to the SGSNu which acts as the main admission controller for the system.
The SGSNu then authorises the bandwidth and QoS resources for the whole system.
• The SGSNu negotiates with the RNC and GGSNu to set up an appropriate radio bearer
and sets the quality and bandwidth limits to be maintained.
During the session:

• The RNC and GGSNu check that the traffic load is within agreed limits.
• Internally the RNC, GGSNu and SGSNu implement a series of algorithms to queue,
prioritise each data packet in order to optimise system performance and maximise
efficiency (especially over the Uu air interface).
The RRM feature within the RNC optimises the Uu air interface resources
and in so doing, maximises the number of users while maintaining the
individual QoS requirements for each user.
68P02905W21-B 2-53
02-Jun-2004
Quality of Service (QoS) Chapter 2: Overview of UMTS
QoS classes
The QoS standards for UMTS specify four classes or grades of QoS. These are:
• Conversational.
• Streaming.
• Interactive.
• Background.
The factor which differentiates between the classes is how sensitive to delay the traffic is.
Therefore Conversational class of service applies to traffic which is most delay sensitive
whereas Background class is the least delay sensitive.
Table 2-2 shows a typical logical mapping of the classes of service.
Table 2-2 QoS classes
Application Service Requirements Class of Service

VoiceVoice over Low delayLow delay Conversational
IPVideo/Multimedia call variationSymmetric traffic
Real Audio/Video webcast Low delay variationAsymmetric Streaming
traffic
Web browsingE-commerce Request response patternPreserve Interactive
payload contentAsymmetric
traffic
Non-critical dataBackground Best effortAsymmetric traffic Background
download of E-mails
Conversational
Conversational class is intended to be used to carry real-time traffic flows. Conversational
real time services like video telephony are the most delay-sensitive and those data streams
should be carried only in Conversational class.
Streaming
The main divider between Conversational and Streaming class relates to how sen-
sitive to delay the traffic flow is.
2-54 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Quality of Service (QoS)
Interactive
Interactive class (similarly with Background class) is intended mainly for use by traditional internet
applications such as WWW, Email, Telnet FTP and News. Because of the less stringent delay
requirements compared with Conversational and Streaming classes, both Interactive and Background
provide better error rates using channel coding and retransmission.
Note that the main difference between the Background and Interactive classes is that Interactive
is, as its name suggests, used mainly for interactive applications such as web browsing
whereas Background class is used for background traffic.
Responsiveness of the Interactive applications is achieved by separating these from Background applications.
Traffic in the Interactive class has a higher scheduling priority than that of Background traffic.
Background
Background class is intended for background traffic such as, background download
of Emails or background file download.
Background applications use resources only when they are not required by Interactive
class. This is very important in a wireless environment where the bandwidth is
low compared to that of fixed networks.
68P02905W21-B 2-55
02-Jun-2004
Migration from GSM/GPRS to UMTS Chapter 2: Overview of UMTS
Migration from GSM/GPRS to UMTS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to UMTS migration
UMTS is a natural evolution path for GSM and GPRS operators. Most of the CN elements
of both GSM and GPRS are used in a UMTS network.
The GSM CN was originally developed as a cellular telephony system supporting voice and circuit-switched
data transfer. The GPRS system was later introduced and built upon existing GSM technology to
provide packet switching services to mobile users. GPRS introduced the concept of gateway system
units GGSN and SGSN in order to provide access to packet switched domains.
As GSM provides only the circuit system for the UMTS, the GPRS packet system must
be added to the GSM CN before migration to UMTS.
UMTS provides high-speed data access and transmission utilising the GGSN and SGSN concept but with the
addition of two new system units; RNC and Node B, these two units together comprise the RAN.
UMTS also introduces a new air interface providing high data transmission rates with real time QoS,
allowing both voice and data services to be handled concurrently on the same UE.
Figure 2-20 shows the migration path from GSM to UMTS.
Figure 2-20 GSM/GPRS to UMTS migration path
GSM
(VOICE AND CIRCUIT-SWITCHED SERVICES)
GPRS
(PACKET-SWITCHED SERVICES)
UMTS
(PACKET AND CIRCUIT SWITCHED SERVICES)
2-56 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Migration from GSM/GPRS to UMTS
Migration process GSM to UMTS
Achieving GSM to GPRS

To achieve the full evolution from GSM to UMTS, GPRS components must be deployed in
the GSM system. This procedure includes the following:
• Deployment of GPRS components - SGSN, GGSN, ISS and PCU.
• Upgrading the Home Location Register (HLR).
• Deployment of the Network Management System (OMC-G).
Achieving GPRS to UMTS

The procedure for evolution from GPRS to UMTS is as follows:
• Deployment of UTRAN - Node Bs and RNCs.
• Upgrade of the Gateway GPRS Serving Node (GGSN) to GGSNu.
• Upgrade of the Serving GPRS Serving Node (SGSN) to SGSNu.
• Upgrade of the Mobile Switching Centre (MSC) to MSCu.
• Upgrade the OMC to OMC-U.
• Add new protocol stacks for UMTS-specific signalling and data flow.
• Add ATM transport capabilities.
• Update of the Home Location Register (HLR) and service/features databases

for new services and subscribers.
• Deployment of multiple network management systems for both the UTRAN and CN elements.
Figure 2-21 shows a UMTS deployed in a GSM system.
68P02905W21-B 2-57
02-Jun-2004
Migration from GSM/GPRS to UMTS Chapter 2: Overview of UMTS
Figure 2-21 Deployment of UMTS in a GSM network
PSTN
BSS MSC GSM

MS
BTS BSC MSC GMSC

(GSM) CS-SERVICE
DOMAIN
CGF HLR
Gb MSCu UMTS
SS7
Gs
UTRAN CAMEL EIR
Uu
UE Iu-CS
Iub Iu-PS SGSNu Gn GGSNu PS-SERVICE

Node B RNC
DOMAIN
Uu
UE Iub Gn Gn
Node B PDN/
Iur SGSNu INTERNET
Uu Iu-PS
UE
Iub
Node B RNC
Uu
UE Iub
Node B
2-58 68P02905W21-B
02-Jun-2004
Chapter
3
Functional description of UTRAN
components
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 3-1
02-Jun-2004
Introduction to this chapter Chapter 3: Functional description of UTRAN components
Introduction to this chapter

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of this chapter
This chapter describes the Universal Terrestrial Radio Access Network (UTRAN) components,
which process signalling data and route traffic data between the User Equipment (EU)
and the Mobile Switching Centre (MSCu).
The chapter contains the following information about the UTRAN components:
• "UMTS Terrestrial Radio Access Network (UTRAN)" on page 3-3.
• "Radio Access Network (RAN)" on page 3-4.
• "RNS functionality" on page 3-8.
• "RNC description" on page 3-10.
• "RNS site configuration and capacity" on page 3-12.
• "RNC subsystems" on page 3-15.
• "RNC user features" on page 3-19.
• "Node B description" on page 3-22.
• "User Equipment (UE)" on page 3-25.
• "Operations and Maintenance Centre - UTRAN (OMC-U)" on page 3-29.
3-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS Terrestrial Radio Access Network (UTRAN)
UMTS Terrestrial Radio Access Network (UTRAN)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the UTRAN components
In UMTS, the UTRAN is divided into:

• Radio Access Network (RAN):
◦ Radio Network Controller (RNC).
◦ Node B.
An RNC and a several Node Bs are known collectively as an Radio
Network System (RNS).
• User Equipment.
• OMC-U.
Each RAN is responsible for managing the resources of its own set of cells. However, unlike GSM
the RAN is fully responsible for mobility management (handover detection and control) and radio
resource management including connection set up, release and transfer of packets.
The RNC is roughly equivalent to the BSC in UMTS terminology. Each RNC controls one or
more Node B elements. A RNC is then connected to both the MSCu and SGSNu via the Iu
interface and is connected to other RNCs via the Iur interface.
Node B is equivalent to a BTS in UMTS terminology in that it provides the air interface element via CDMA
connected to the RNC via the Iub interface. Each Node B can support one or more cells.
68P02905W21-B 3-3
02-Jun-2004
Radio Access Network (RAN) Chapter 3: Functional description of UTRAN components
Radio Access Network (RAN)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RAN
The Radio Access Network (RAN) is the interface between the User Equipment (UE) and the
Core Network (CN) elements of the UMTS system. The RAN processes signalling data and
routes traffic data between the UE and the Core Network.
The following comprise the functions provided by the RAN:
• Radio coverage areas and control functions for one or more cells.
• Radio coverage areas and control functions for the UE in the cells.
• Signalling data processing and routeing of the traffic data exchanged between
the UE and the Core Network.
• Digital signal interfaces to the land circuits linking the RAN and the Core Network.
RAN links
The RAN has links to the Core Network and the UE. The following comprise the links:
Interface links
Land circuits link the Radio Network Controller (RNC) to the Core Network (CN). Each interface link
contains a multiplexed E1/T1 serial data stream. The BSS places UE originated, or UE terminated
subscriber (signalling or traffic) data in a channel on a serial data stream.
Air Interface link

The communication link, or Uu interface, between the Node B and the UE uses digital radio techniques.
RNC to Core Network link

The RNC to Core Network interface uses ATM (AAL2, AAL5) and STM-1 links.
Typical RNS layout
Figure 3-1 shows the layout of a typical system with two RSNs. Each RNS contains several components
to make the link between the UE and the Core Network (CN). Also note that the system enables macro
diversity within Nodes within the RNSs. Software handover can also now occur between Node Bs of
different RNSs. The RNS components are described in more detail in the following sections.
3-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Radio Access Network (RAN)
Figure 3-1 Dual RNS system
RNS #1 RNS #2
UE
NODE
B
SITE
UE UE
NODE
Iub B
UE SITE
NODE NODE
B B
Iub SITE
SITE Iub
RNC NODE
Iub B NODE
SITE UE
B
Iub
SITE
Iub
Iub
NODE RNC
B
SITE Iur
Iu
CORE
Iu
NETWORK
LEGEND
Uu Interface
Iu Iu Interface PSTN/ISDN/PUBLIC DATA NETWORK
Iur Iur Interface NOTE

DASHED LINES ENCLOSE NETWORK COMPONENTS OF
Iub Iub Interface A PARTICULAR RADIO NETWOR SUBSYSTEM (RNS)
SERVICE AREA.
68P02905W21-B 3-5
02-Jun-2004
Radio Access Network (RAN) Chapter 3: Functional description of UTRAN components
Node B
Node B embodies the base station transceiver functionality, has soft combining capabilities and
supports a mixture of voice and data services with data rates of up to 2Mbit/s. Each Node B can have
only one Controlling RNC (CRNC) to which it is connected via the Iub interface. The Node B is a
logical node responsible for radio transmission and reception, in one or more cells, to and from the
UE and the RNC controls the use and the integrity of the radio resources.
Thus a phone call sets up a link through the Node B between the RNC and UE. The Node
B is connected to the RNC via the Iub interface.
RNC
The RNC is connected to the CN via the Iu-CS and Iu-PS interfaces corresponding to the circuit switched
and packet switched domains, respectively, and can be compared functionally with the UMTS Base Station
Controller (BSC). The Iu-BC (not used in USR1.0) is shown in Figure 3-2 and Figure 3-3for completeness.
Each RNC can control a number of Node Bs, each connected to its controlling RNC via an Iub interface.
The RNC manages the use and integrity of the radio resources. It performs the following functions:
• Control of the Node Bs.
• Performs call processing, operations and maintenance.
The RNC receives signalling and traffic data from the Core Network. The RNCs then provide the
opportunity for remote switching, distributed control, and traffic concentration.
Figure 3-2 shows the relationship between the RNC and the UTRAN and CN.
3-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Radio Access Network (RAN)
Figure 3-2 RNC in the UTRAN
CS PS BC
Iu-BC
Iu-BC
Iu-CS Iu-PS Iu-PS
Iu-CS
RNC Iur RNC
Iub Iub Iub Iub
NODE NODE NODE NODE

B B B B
Uu
68P02905W21-B 3-7
02-Jun-2004
RNS functionality Chapter 3: Functional description of UTRAN components
RNS functionality
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
The RNS supports the following functionality:

• Non-imperative handover rejection
• Congestion relief handover retry
• Incoming handover requests
• Handover retry
• Multiband mobile station redirection
Non-imperative handover rejection
The RNS rejects an incoming non-imperative handover if it will cause congestion relief procedures to be
triggered. The RNS does not allow an incoming handover if the reason for that handover is congestion relief
and the handover itself will lead to the invocation of congestion relief procedures. Should such a handover be
allowed, then the net result would simply be the movement of a congestion problem from one cell to another.
Congestion relief handover retry
The source cell will not attempt a congestion relief handover, for a period of time, to a target cell which had
rejected a previous handover attempt, both imperative and congestion relief. A new timer element is used to
control this period of time. It does not, however, affect any imperative handover retries. These handovers are
allowed to take place regardless of such timers, as they are needed in order to keep the call active.
Incoming handover requests
If a RNS target cell rejects an incoming handover, because that handover would trigger congestion relief
procedures, the target cell attempts to inform the source cell of its future, intra-RNS only, accessibility
status. If the target cell is configured to optionally invoke congestion relief procedures after rejecting
the handover request, then it may be capable of handling the necessary handovers.
If a RNS target cell accepts an incoming handover due to congestion relief, and this handover itself
triggers the target cell congestion relief procedures, the target cell does not trigger any handover attempts
back to the source cell which triggered the congestion relief to begin with.
3-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNS functionality
Handover retry
The source cell optionally retries an imperative, intra-RNS only, handover to target cells which
rejected the initial handover request and initiated a congestion relief procedure.
Multiband mobile station redirection
The RNS does not allow an incoming band preference handover should the servicing of that handover
cause this percentage to be exceeded. If such a handover is allowed to be serviced, the net result would
simply be the movement of a Multiband congestion problem from one cell to another.
68P02905W21-B 3-9
02-Jun-2004
RNC description Chapter 3: Functional description of UTRAN components
RNC description
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
The RNC network element provides the control for the RNS. It controls and manages the associated
Node Bs, and interfaces with the Operations and Maintenance Centre-UTRAN (OMC-U).
RNC functions
The RNC is connected to the CN via the Iu-CS and Iu-PS interfaces corresponding to the
circuit switched and packet switched domains, respectively, and can be compared functionally
with the UMTS Base Station Controller (BSC). Each RNC can control a number of Node Bs,
each connected to its controlling RNC via an Iub interface.
Each RNC can serve multiple Node Bs. The RNC is a complex UMTS component which
provides the following major functionalities:
• Local mobility (hard handover, soft handover).
• Advanced dynamic radio resource management.
• QoS maintenance.
• Admission control.
• Bearer control.
• Channelisation code management.
• Diversity combining.
• Call control.
Figure 3-3 shows the relationship between the RNC and the UTRAN and Core Network (CN).
3-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC description
Figure 3-3 RNC in UTRAN
CS PS BC
Iu-BC
Iu-BC
Iu-CS Iu-PS Iu-PS
Iu-CS
RNC Iur RNC
Iub Iub Iub Iub
NODE NODE NODE NODE

B B B B
Uu
RNCs are connected to each other via logical lur interfaces. This enables soft handover (macro
diversity) procedures to be undertaken when multiple RNCs are used by one user simultaneously.
In such cases, one of the RNCs involved takes the serving role (SRNC) and the others act as drift
(DRNCs). Synchronised data flow from the various DRNCs reach the SRNC through the associated
lur interface and are combined (using best selection process) to the SRNC.
RNCs are connected to the Core Network (CN) circuit-switched (CS-service) domain through
the logical interface lu-CS to a serving MSCu and to the packet-switched (PS-service)
domain via the lu-PS logical interface to SGSNu.
The MSCu and SGSNu are upgraded versions of the conventional MSC and SGSN. The MSCu
and SGSNu are modified and configured to UMTS signalling and ATM information flows.
Also that each RNC is controlled by only one MSCu and SGSNu, however, each
MSCu or SGSNu is capable of controlling multiple RNCs.
68P02905W21-B 3-11
02-Jun-2004
RNS site configuration and capacity Chapter 3: Functional description of UTRAN components
RNS site configuration and capacity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
The Motorola RNS uses a variety of RNCs and Node Bs site configurations to meet
a wide range of requirements.
The following items must be considered when meeting requirements for cell site configuration:
• The number of RF carriers.
• The distribution of the RF carriers at a site.
• The type of transmit channel combining.
• The antenna configuration.
• The number of E1/STM-1 links for traffic/signalling channels.
• The equipment redundancy provided for the site(s).
• Congestion relief.
RNS configurations
The RNS is set up to perform a variety of functions. In order to perform those functions,
the following equipment is required:
• An RNC cabinet.
• Up to 300 Node B sites.
Flexibility
Motorola RNS equipment uses a flexible architecture that expands easily. The RNC, Node B can
start small and expand incrementally. The size of the Motorola RNC provides significant switching
capability to handle a variety of different Node B sites and network configurations.
3-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNS site configuration and capacity
Node B cabinet
The Node B cabinet contains the radio transceivers and associated Air Interface modules that
make up the Node B function. The Node B cabinet can contain equipment for up to 6 RF carriers
and support up to three different RF coverage areas and six sectors.
The Node B cabinet is configured to provide the BTS functions only.
RNC cabinet
A single Radio Network Controller (RNC) cabinet can provide the RNC function.
The equipment configuration in the cabinet determines the function(s).
RNS with more than one Node B
Figure 3-4 shows examples of two RNSs, designated RNS #1 and RNS #2, with more than one Node B site.
A separate RNC site operates the Node B sites of RNS #1 remotely.
A separate RNC operates the Node sites of RNS #2 remotely. Transcoding for this
RNS is located remotely at the CN site.
Also note that the system enables macro diversity within Nodes within the RNSs. Soft handover
can also now occur between Node Bs of different RNSs.
68P02905W21-B 3-13
02-Jun-2004
RNS site configuration and capacity Chapter 3: Functional description of UTRAN components
Figure 3-4 Multiple Node B sites per RNS
RNS #1 RNS #2
UE
NODE
B
SITE
UE UE
NODE
Iub B
UE SITE
NODE NODE
B B
Iub SITE
SITE Iub
RNC NODE
Iub B NODE
SITE UE
B
Iub
SITE
Iub
Iub
NODE RNC
B
SITE Iur
Iu
CORE
Iu
NETWORK
LEGEND
Uu Interface
Iu Iu Interface PSTN/ISDN/PUBLIC DATA NETWORK
Iur Iur Interface NOTE

DASHED LINES ENCLOSE NETWORK COMPONENTS OF
Iub Iub Interface A PARTICULAR RADIO NETWOR SUBSYSTEM (RNS)
SERVICE AREA.
3-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC subsystems
RNC subsystems
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
The RNC5000 is one of the network elements of the UMTS Radio Access Network (UTRAN). The RNC
is responsible for controlling the use and integrity of the radio resources present at the Node Bs under the
RNC control. Each RNC and its corresponding Node Bs, form the Radio Network Subsystem (RNS).
The RNC5000 has a modular architecture designed for flexibility and scalability. Capacity of the RNC
can easily be increased by adding additional modules without system outage, thus making the system
very network friendly. This also allows the operator to grow the network in line with the UMTS market
development allowing for efficient management of capital investment. As can be seen in Figure 3-5, the
RNC5000 consists of the following functional modules: System Unit, Switch Unit, and OA&M Unit.
68P02905W21-B 3-15
02-Jun-2004
RNC subsystems Chapter 3: Functional description of UTRAN components
Figure 3-5 RNC5000 cabinet layout
SYSTEM UNIT
SWITCH UNIT
OA&M UNIT
ti-UMTS-EP-00145-v01-ai-sw
The UMTS RNC consists of three main subsystems illustrated in Figure 3-6.
System Unit
All the internal and external switching for the RNC is done at the System Unit. The user plane on Iu-PS
is also terminated on the System Unit. It provides high speed STM-1 (VC4) optical interfaces for Iu-PS,
Iu-CS, and Iur. It can also optionally terminate high speed STM-1 (VC4) Iub interface. Additionally
it supports STM-4 interfaces for Iu-CS and Iu-PS. The System Unit also provides the interfaces for
interconnections to all other Units within the RNC as well as for the system clock.
3-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC subsystems
Switch Unit
The Switch Unit performs layer 2 processing, call control functions, handover, frame processing and Radio
Resource Management within the RNC. It performs processing for the following control plane protocols
— RANAP, RNSAP, NBAP, ALCAP, and RRC. It also performs user plane processing which includes
RLC, MAC, and PDCP. It also performs macro diversity selection and combining.
The Switch Unit supports high speed STM-1 (VC12) and E1/T1 interfaces for Iub. The E1/T1
interfaces can be used to optionally support Iu-PS, Iu-CS, and Iur. There can be up to 16 System
Units per RNC. Each Switch Unit provides a maximum voice capacity of 2,500 Erlangs and a
maximum data capacity of 40 Mbit/s in both Uplink (UL) and Downlink (DL) paths. The Switch
Unit capacity can be dynamically allocated between voice and data.
OA&M Unit
There is one OA&M Unit per RNC which performs the following functions:
• Fault management.
• Load management.
• Performance management.
• Configuration management.
• Security management.
• Status monitoring.
68P02905W21-B 3-17
02-Jun-2004
RNC subsystems Chapter 3: Functional description of UTRAN components
It consists of a:
• Primary and back-up Administration Server.
• Primary and back-up LAN switches, which provide connection to the:

◦ Operations and Maintenance Centre - UMTS (OMC-U).
◦ Local Maintenance Terminal (LMT).
◦ Alarm Terminal.
Figure 3-6 RNC5000 functional modules
RNC
Iu-PS
Iu-CS System OA&M LMT/OMC-U
Iur Unit Unit
Iub
Iu-PS
Iu-CS Switch
Iur Unit
Iub
PHYSICAL INTERFACES:
STANDARD OPTIONAL
3-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC user features
RNC user features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of RNC user features
The main user features available via the RNC are:

• Short Message Service (SMS) point to point.
• Radio Resource Management (RRM).
• Queuing.
• User Equipment (UE) compatibility.
• Overload Control (RNC and Node B).
Short Message Service (SMS) point to point
SMS allows subscribers to send/receive data in an end-to-end mode. The traffic is particularly bursty
where blocks of data are sent during intervals of non-activity (non real-time).
UMTS provides, at the minimum, the same level of service as that offered by UMTS. Inter-operability
with UMTS is possible with the availability of multi-standard mobile stations.
68P02905W21-B 3-19
02-Jun-2004
RNC user features Chapter 3: Functional description of UTRAN components
Radio Resource Management (RRM)
RRM optimises the air interface resources and in so doing, maximises the number of users
while maintaining the individual QoS requirements for each user.
The RNC manages all radio resources for each cell that it controls. The RRM algorithm within the
RNC attempts to match the radio resource usage of different cells and the users.
Selection of the appropriate radio transport channel and management of interference are key factors in
delivering the required QoS to the user as is maximising the throughput of the air interface.
Elements of the algorithm include:
• Power control.
• Selection of radio bearer channel type.
• Radio admission and load control.
• Scheduling of non real-time user data.
Queuing
Queuing of system allocation requests for radio resources needed to support user
services enables higher call completion.
In the event that radio resources (for example, air interface bandwidth required for a voice call) to
support a user’s requested service is not available the call queuing feature provides a mechanism
whereby the system waits for resources to become available.
Queuing effects co-ordination between the RNC and core network at the time the core network
requests a Radio Access Bearer from the RNC. If the RNC cannot immediately handle the request,
an indication is given to the core network that the request has been queued.
3-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC user features
User Equipment (UE) capability
In UMTS, UE capabilities signalled to the RNC allow the RNC to assign appropriate radio
resources and manage intra-system handovers.
Examples of the UE capabilities signalled to the RNC include:
• Support of the IP header compression.
• Data buffer capacity.
• Physical radio parameters supported (for example, turbo coding, spreading factor).
• UE power class.
• Support of UMTS multi-carrier and UMTS (including if compressed mode

is required to scan other carriers).
The RNC uses the capability information for RRM (for example, selection of the best type of radio transport
channel) including if necessary, handover of the user to a different type of system (UMTS for example).
Overload control (RNC and Node B)
The RNC and Node B automatically react to overload conditions relating to resources under their in
addition to the signals to signals from the core network or adjacent RNC.
The RNC manages radio overload as part of its responsibility for RRM. The reaction to overload includes
denying admission of new calls as well as the throttling of data traffic for non real-time services.
The RNC and Node B manage internal processing resources and interface capacity. The
RNC takes action to reduce traffic towards the Iu interface (lu-CS and lu-PS) after receiving
a signal from the CN that an overload condition exists.
68P02905W21-B 3-21
02-Jun-2004
Node B description Chapter 3: Functional description of UTRAN components
Node B description
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
The Node B element consists of the hardware components, such as radios, interface modules and antenna
systems that provide the Air Interface between the RNC and the Core Network.
Node B functions
The Node B provides radio channels (RF carriers) for a specific RF coverage area. The radio channel is
the communication link between the UE within an RF coverage area and the RAN. A single Node B site
contains all the network components that provide RF channels for the same geographic area.
Logical flows through a Node B
The Node B is a logical node responsible for radio transmission and reception, in
one or more cells, to and from the UE.
There are two logical flows through the node B:
• Control flow - All control functions emanate from a single point - the Site Control.
The Site Control terminates all RNC signalling channels also.
• User data flow - In the transmit direction, user data flow first passes through the Network
block. The Network block terminates the physical channel and switches the data to Baseband
Signal Processing and control flows are switched to the Site Controller.
Figure 3-7 shows a logical view of Node B.

In the transmit direction, the user data flow first passes through the Network block. The
network block terminates the physical link and switches the data to Baseband Signal Processing
and control flows are switched to the Site controller.
The Baseband Signal Processing performs symbol and chip level processing dependent on
the physical radio channel allocated to that user.
The output of the Baseband Signal Processing (BSP) is passed to the Radio Unit
where it is converted to an RF signal.
The Tx Distribution function defines the antenna to which the Radio Unit is connected and routes
the signal to the appropriate Linear Power Amplifier (LPA).
Within the Combiner function, combining of upto two carriers takes place at the input to the
Fourier Transform Matrices,this enables the LPAs to be truncated.
3-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B description
The Duplexor allows for sharing antenna for transmit and receive signals. The
receive user path is a reciprocal flow.
Figure 3-7 Logical view of Node B architecture
Tx
COMBINER LPA DIST.
RADIO NET-
UNIT BSP WORK
Rx
LNA DIST.
TO/FROM TO/FROM
ANTENNAE NETWORK
DUPLEXOR
USB INTEGRATED
KEY: SITE RS232
CONTROL CELLSITE
V11 EQUIPMENT
USER DATA FLOW
CONTROL DATA FLOW

TO
MAINTENANCE
TERMINAL
RF coverage areas
The term cell defines a single RF coverage area which may be either a multidirectional and
sectorized area, or an omnidirectional single area.
A Node B site can provide either of the following:
• An omnidirectional RF coverage area, singular and undivided.
• Multidirectional RF coverage area divided into sectors.
The antenna system at the Node B site determines the type of RF coverage area.
68P02905W21-B 3-23
02-Jun-2004
Node B description Chapter 3: Functional description of UTRAN components
Antenna system
Node B RF hardware can be configured for operation with the following types of
antenna systems for RF coverage areas:
• 1 omnidirectional sector.
• 3 directional sectors (120° or alternate 60°).
• 6 directional sectors (60°).
3-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview User Equipment (UE)
User Equipment (UE)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The UMTS User Equipment (UE) enables consumers and commercial enterprises
to gain quick and easy information access.
UMTS enables personal networking by providing traditional and innovative telecommunications
solutions to users who can utilise high speed data connections and transfer rates.
UMTS UEs incorporate new and evolving technologies supporting both voice and data capability enabled.
The UEs currently available utilise CDMA technology and include terminals with the following capabilities:
• Advanced voice and data phones.
• Data Cards for integration into PCs or laptops to allow the user to be wirelessly
networked without the need for an additional wireless device.
• PDA devices with large colour displays. The features available with these devices include
handwriting recognition software, voice recognition and a QWERTY compliant keyboard.
• Smart phone with browser facilities.
• Video phone with video capture and streaming facilities.
UEs connect to the Node B via the Uu air interface.

Each UE contains a smart card known as the UMTS Subscriber Identity Module (USIM),
This card provides personal access to subscriber services.
UE phone call procedure
To handle a phone call, the UE synchronises itself to the Node B downlink (transmit) timeslot and frame timing.
When synchronised, the UE gathers the information required to contact over the Broadcast Channel (BCH).
Phone calls can be one of two types, mobile initiated or mobile terminated. If a mobile terminated
call is to be set up, the UE must be paged over the Paging Channel (PCH) by the Node B. The UE
responds to set up the call using the same procedures as for initiating the call.
The UE contacts Node B using the Random Access Channel (RACH). If a Dedicated Channel (DCH) is
required, the DCH is passed to the UE over the Forward Access Channel (FACH). Uplink and downlink
DCHs are then set up to support the call. The DCH can be reconfigured during a phone call using the
control channel information. This could for example, be to support the required QoS.
Signal power control is essential in a CDMA system to reduce cross channel interference. This is
achieved using signal power measurements and control channel information.
68P02905W21-B 3-25
02-Jun-2004
User Equipment (UE) Chapter 3: Functional description of UTRAN components
Mobile Station (MS)
The subscriber uses the Mobile Station (MS) to access the services provided by the PLMN.
MSs can be installed in vehicles or can be portable or hand held stations. The MS can include
provisions for data communication as well as voice communication.
Different types of MSs can provide different types of data interfaces. To provide a common
model for describing these different MS configurations, UMTS defines reference configurations
for MSs similar to those defined for ISDN land stations.
Mobile station components
The Mobile Station consists of the Mobile Equipment (ME) and the UMTS Subscriber Identity Module (USIM).
Mobile Equipment
The Mobile Equipment is the hardware used by the subscriber to access the network. There are three types:
• Vehicle mounted, with the antenna physically mounted on the outside of the vehicle.
• Portable mobile unit, which can be hand held, but the antenna is not on the handset.
• Hand portable unit, which consists of a small handset with the antenna attached to the handset.
USIM
The USIM is a removable card that plugs into the ME. It identifies the mobile subscriber and
provides information about the service that the subscriber should receive.
Hand portable viability
The UMTS specifications for hand portable MSs aim to minimise power consump-
tion by design features such as:
• Discontinuous transmission (DTx). This ensures that the hand portable transmitter
is energised only when there is speech or data traffic to transmit.
• Discontinuous reception (DRx). This is a group paging technique that allows the hand
portable to cycle to a low drain standby mode as much as 98% of the time.
• Active power control. As the hand portable gets closer to the BTS, it uses less
power to transmit. This saves on battery life.
UMTS hand portables also incorporate digital signal processing.
3-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview User Equipment (UE)
Equipment identity number
International Mobile station Equipment Identity (IMEI)

Each MS is identified by an International Mobile station Equipment Identity (IMEI) number which is
permanently stored in the Mobile Equipment. On request, the MS sends this number over the signalling
channel to the MSC. The IMEI can be used to identify MSs that are reported stolen or operating incorrectly.

A listing of the allowed IMEIs is maintained by the PLMN in the Equipment Identity
Register (EIR) to validate the mobile equipment.
68P02905W21-B 3-27
02-Jun-2004
User Equipment (UE) Chapter 3: Functional description of UTRAN components
Subscriber identification
International Mobile Subscriber Identity (IMSI)

Just as the IMEI identifies the mobile equipment, other numbers are used to identify the mobile
subscriber. Different subscriber identities are used in different phases of call set up. The
International Mobile Subscriber Identity (IMSI) is the primary identity of the subscriber within
the mobile network and is permanently assigned to that subscriber.
Temporary Mobile Subscriber Identity (TMSI)

The UMTS system can also assign a Temporary Mobile Subscriber Identity (TMSI). After the
subscriber’s IMSI has been initialized on the system, the TMSI can be used for sending backwards
and forwards across the network to identify the subscriber. The system automatically changes
the TMSI at regular intervals, thus protecting the subscriber from being identified by someone
attempting to monitor the radio channels. The TMSI is a local number and is always transmitted
with the Location Area Identification (LAI) to avoid ambiguities.
Mobile Subscriber ISDN (MSISDN)

The Mobile Subscriber ISDN (MSISDN) number is the telephone number of the MS. This is the number a
calling party dials to reach the subscriber. It is used by the land network to route calls toward the MSC.
Home Location Register (HLR) and Visited Location Register (VLR)

The PLMN holds subscriber data in a series of registers: the Home Location Register
(HLR) and the Visited Location Register (VLR).
Subscriber Information Module (SIM)

By making a distinction between the subscriber identity and the mobile equipment identity, a UMTS
PLMN can route calls and perform billing based on the identity of the subscriber rather than the
mobile equipment being used. This can be done using a removable Subscriber Information Module
(SIM). A smart card is one possible implementation of a SIM module.
The following information is stored in the SIM:
• IMSI. This is transmitted at initialization of the mobile equipment.
• TMSI. This is updated periodically by the PLMN.
• MSISDN. This is made up of a country code, a national code and a subscriber number.
• Local Area Identity (LAI). This identifies the current location of the subscriber.
• Subscriber Authentication Key (Ki). This is used to authenticate the SIM.
When the SIM is inserted in the mobile equipment, a location update procedure registers the
subscriber’s new location, allowing the correct routeing of incoming calls.
3-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Operations and Maintenance Centre - UTRAN (OMC-U)
Operations and Maintenance Centre - UTRAN

(OMC-U)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to an OMC
The UMTS recommendations identify an element that controls and monitors the other network
elements within a region. In the Motorola network, the Operations and Maintenance Centre (OMC)
performs this function. The OMC also monitors the quality of service being provided by the network.
The OMC is connected to the other network elements via an X.25 packet network, and sends and
receives control and network information only, not speech or data traffic.
OMCs in UMTS
The Operations and Management (O & M) Network for the UMTS comprises two Operations
and Maintenance platforms. These are as follows:
• OMC-U for the UTRAN - The OMC-U is a new hardware platform that has the
same architecture as the OMC-G in the GPRS system.
• OMC-S/T for the CN - The OMC-S/T is a derivative of the OMC-G (the

OMC-G can be upgraded to OMC-S/T).
The OMCs are controlled at an operator level using Graphic User Interfaces (GUIs). Each OMC
has an associated Unix server which provides persistent data storage and communications, together
with an NT server providing an application and data server.
Figure 3-8 shows OMC-U and OMC-S/T platforms and network.
68P02905W21-B 3-29
02-Jun-2004
Operations and Maintenance Centre - UTRAN (OMC-U) Chapter 3: Functional description of UTRAN components
Figure 3-8 O & M platforms and network
OMC-U GUI OMC-S/T GUI
APPLICATION APPLICATION
SERVER SERVER
OMC-U OMC-S/T
IP SUPPORT
RNC RNC COMM HUB SUBSYSTEM
(ISS)
PACKET DATA
NODE B NODE B SGSNu GGSNu NETWORK
(PDN)
UE
UTRAN CORE NETWORK
3-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Operations and Maintenance Centre - UTRAN (OMC-U)
Role of the OMC-U
The OMC-U is responsible for the static management of the UTRAN. This includes allocation
of resources which can be used dynamically by the RNC.
At system initialisation, the OMC-U is responsible for object verification, code load and initialisation
of Node B and the RNC to a default state before they are brought into operation.
OMC-U provides UTRAN management functionality in the following areas:
• On-line Help.
• Northbound interface to Operations Support Systems/Business Support Systems (OSS/BSS).
The OMC-U is connected to each RNC, and through the controlling RNC (CRNC) to each Node B.
The OMC-U receives control and network information only (not speech or data traffic).
The OMC-U receives alarm reports from Node B, thus enabling Node B degradation to be handled
by the UTRAN network. For example, if Node B capability is degraded then the static configuration
of the system may be changed to reduce the overall effect on the system.
Role of the OMC-S/T
Similarly to the OMC-G in the GPRS, the OMC-S/T provides GSN management
functionality in the following areas:
• On-line Help.
The OMC-S/T provides a Graphics User Interface (GUI) to enable a user to carry out CN management functions.
The OMC-U monitors and receives alarm reports from C-SGSN, GGSN, ISS and CommHub CN elements.
All maintenance, CN reconfiguration, troubleshooting, and CN administration, is
carried out from the OMC-S/T.
68P02905W21-B 3-31
02-Jun-2004
Operations and Maintenance Centre - UTRAN (OMC-U) Chapter 3: Functional description of UTRAN components
3-32 68P02905W21-B
02-Jun-2004
Chapter
4
Data flow and terrestrial interfaces for
UMTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 4-1
02-Jun-2004
Introduction to this chapter Chapter 4: Data flow and terrestrial interfaces for UMTS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter describes the transport mechanisms for the UMTS transport network.
The topics included in this chapter are:

• "Overview of terrestrial interfaces" on page 4-3.
• "Introduction to Asynchronous Transfer Mode (ATM)" on page 4-5.
• "ATM virtual channels and paths" on page 4-13.
• "E1 architecture" on page 4-16.
• "Inverse Multiplexing for ATM (IMA)" on page 4-19.
• "Plesiochronous Digital Hierarchy (PDH)" on page 4-22.
• "Synchronous Digital Hierarchy (SDH)" on page 4-23.
• "Typical UMTS ATM Transport Network" on page 4-27.
4-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of terrestrial interfaces
Overview of terrestrial interfaces

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to terrestrial interfaces
One very important aspect that is sometimes overlooked is the transport medium required between the
different entities. In the case of UMTS the Network Operator will run into problems if the wrong links are
utilised. Speed of transfer and cost will be two of the major determining factors when planning the UMTS
network. Other issues that need to be addressed are the types of converting equipment used between the
different types of Terrestrial Interfaces. In this chapter a closer look is taken at these aspects.
It should also be mentioned that as data rates increase the use of E1/T1 systems become more
difficult. Asynchronous Transfer Mode (ATM) is the preferred transport mechanism on the CN.
Voice and IP over ATM is conducted using ATM adaptation layers.
Diagram of terrestrial interfaces
Figure 4-1illustrates the terrestrial interfaces used by the Core Network.
68P02905W21-B 4-3
02-Jun-2004
Overview of terrestrial interfaces Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-1 Terrestrial Interfaces
CS PS
Network
Uu Iub Iups GN
Node B RNC SGSN GGSN

UE
CDMA ATM ATM IP IP

- FDD E1 SDH X25
CDMA
- TDD
4-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Introduction to Asynchronous Transfer Mode (ATM)
Introduction to Asynchronous Transfer Mode (ATM)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Principles of ATM
ATM is used to transfer different types of information with different rate factors over one or
more common links with a high bit rate. These properties makes ATM an extremely useful
system when it comes to wideband or broadband data transfer.
With the standards in place it is now possible for packet switching techniques like Frame
Relay or ATM to deliver high quality speech. Some of the intrinsic advantages ATM has
over other network technologies are listed below:
• ATM was constructed, after considering data, voice, and video payload requirements. ATM cells
are of fixed size, 53 bytes each with 48 bytes for payload and five for ATM header. This helps
in reducing the packetization delay significantly, which is one of the major delay parameters.
• It supports extensive QoS (Quality of Service) parameters, which allows voice traffic
to be transmitted across the network in a reliable jitter-free way.
• Various ATM Adaptation Layers (AALs) support various service classes capabilities.
• ATM switches have always been designed with effective traffic management capabilities,
for example, call admission control, usage parameter control, traffic shaping.
• Single network for voice, data, and video.
• Interworking with PSTN is relatively straightforward.
68P02905W21-B 4-5
02-Jun-2004
Introduction to Asynchronous Transfer Mode (ATM) Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-2 ATM basics
FIXED BIT
STREAM
VARIABLE BIT STREAM
DISCONTINUES BIT STREAM
FIXED BIT STREAM
Asynchronous Transfer Mode (ATM) protocol
Asynchronous Transfer Mode (ATM) is a technology originally designed for LANs that has transport,
switching and network management facilities built into it. Data rates are:
• Primary User 155.2 Mbit/s
• Network Interface 622.08 Mbit/s
In general terms ATM is a packet switching protocol made up of fixed length packets. The standard packet
length is 53 Octets, five being header information and the remaining 48 user data, called the payload.
The fixed length cell gives some key advantages over variable length structures. The first is that short cells can
be switched quickly and economically. Secondly the queuing caused by long, variable length frames can be
reduced to the wait time for a single 53 Octet frame, allowing time dependent voice and video to be transported.
4-6 68P02905W21-B
02-Jun-2004
ATM can provide both CBR and VBR transport. It has the following features:
• Data transferred in Cells
• Fast Switching
• Supports Real-Time Services
• Connection Oriented - Virtual Circuits
• Resource Allocation on Requirement Basis
• Primary User Rate - 155.2 Mbit/s
• Network Interface - 622.08 Mbit/s
• No Error Correction or Flow Control
Figure 4-3 ATM features
HEADER PAYLOAD
5 BYTES 48 BYTES
CP13_Ch5_13
ATM data rates
The real data rate are not always the stated ATM data rate, this is mainly because of the overheads like packet
headers. When ATM is multiplexed onto different types of links some of the information rate is also lost.
Table 4-1 Physical Layer Parameter Values
lower bit-rate (Mbits/s) higher bit-rate (Mbit/s)

gross physical-layer bit-rate 155.520 622.080
max bit-rate available for ATM 149.760 599.040
cells
max bit-rate available for cell 135.631 542.526
payload
68P02905W21-B 4-7
02-Jun-2004
ATM adaption layers
The ATM Adaptation Layer (AAL) is the protocol used between the ATM layer itself and higher
layers. The main functionality is to adapt the information coming in from the higher layers so they
can be transferred onto ATM. This is what gives ATM its powerful property of transferring many
traffic types, and ensures appropriate service characteristics are provided.
The AALs are divided into 5 different categories, where AAL1 has the lowest delay and AAL5 the
highest. This means that services like speech will tend to go towards a lower AAL number.
Horizontally the AAL protocol is divided into the Convergence Sublayer (CS) and the
Segmentation and Reassemble Sublayer (SAR).
Figure 4-4 ATM Adaption Layers
Class A Class B Class C Class D
TIMING NOT REQUIRED

REQUIRED
RELATION
BIT RATE CONSTANT VARIABLE
CONNECTION CONNECTION CONNECTION

RATE ORIENTED LESS
EXAMPLES EMULATION VARIABLE CONNECTION CONNECTION

OF ORIENTATED LESS DATA
CIRCUITS BIT RATE DATA
VIDEO TRANSMISSION TRANSMISSION
CPCM
SERVICE TYPE AAL 3/4
AAL 1 AAL 2 OR
TO BE USED
AAL 5
ATM adaption process
The ATM Adaption Layer (AAL) consists of two sub-layers; The Convergence Sublayer (CS)
and the Segmentation And Reassembly sub-layer (SAR).
Convergence Sub-Layer (CS)

The function of the CS is to divide very long packets into fixed-length packets called CS-service
data units (CS-SDUs). It may add header and/or trailer information to the CS-SDU to generate a
CS-protocol data unit (-PDU). Finally it passes the CS-PDUs to the SAR.
4-8 68P02905W21-B
02-Jun-2004
Segmentation And Reassembly (SAR)

At the source end, the SAR sublayer is responsible for segmenting each CS-PDU received
from the CS sub-layer into fixed-length SAR-SDUs according to the application traffic type.
The SAR then appends a header and/or trailer to each SAR-SDU to generate an SAR-PDU
that it sends to the ATM layer, to be built into the cell.
At the destination end, the SAR is responsible for reassembling all SAR-PDUs belonging to the
same CS-PDU and presenting the reassembled CS-PDU to the CS.
Generic AAL process
Figure 4-5 illustrates the Generic AAL Process.
Figure 4-5 Generic AAL Process
USER
HEADER USER TRAILER
CS
PROCESS
H CS-SDU T H CS-SDU T H CS-SDU T
CS-PDU
H SAR-SDU T H SAR-SDU T
SAR
PROCESS SAR-PDL
ATM
LAYER H SAR-SDU H SAR-SDU ATM CELL
ATM Adaption Layer2 (AAL2)
AAL 2 is designed for applications with a variable bit rate but requiring real time delivery. It supports
mechanisms, which can identify and multiplex multiple users over a common ATM layer connection.
68P02905W21-B 4-9
02-Jun-2004
AAL2 is a lot more efficient at transporting voice as there is a more efficient use of bandwidth
due to silence detection and suppression as well as idle channel deletion.
In this type of AAL, the convergence sub-layer further divided into two parts. Common Part Convergence
Sub-layer (CPCS), over which may operate zero or more Service Specific Convergence Sub-layer (SSCS).
In UMTS the Higher level protocols used, do not require the support of an SSCS.
Figure 4-6 illustrates AAL2 format.
Figure 4-6 AAL2 format
3-OCTET CPS HEADER USER INFORMATION
CID LI UUI HEC CPS-INFORMATION FIELD

8 BITS 6 BITS 5 BITS 5 BITS
CPS - PACKET
OSF SN P INFO PACKETS OR PADDING

6 BITS 1BIT 1BIT 47 OCTETS
CPS - PDU
HEADER OSF SN P INFO PACKETS OR PADDING
ATM CELL (53-OCTETS)
CPCS
User information, from multiple users is received at the CPCS sub-layer and placed into, containing
a variable length CPS-Information Field (1-64 Octets) and a three octet CPS Header. The header
contains; The Channel ID (CID) which identifies the substream within the AAL2 connection. The
Length indication (LI) indicates the length of the CPS-INFO payload. The User-to-User Indication
(UUI) carries information between the SSCSs/Applications running above the CPS. The Header
Error Control (HEC) can be used to report errors within the header.
4-10 68P02905W21-B
02-Jun-2004
Dependent upon size multiple CPS Packets, from different sources, can be multiplexed to form 47 Octet
CPS-SDUs, (If necessary, padding can be added to give 47-Octets). A further header is added to the
SDU to yield a 48 Octet CPS-PDU. The CPS-PDU header contains an Offset Field (OSF) which is a
pointer to the first octet of the next CPS-Packet in the CPS-SDU. The 1 bit sequence number is an
alternating logic-1, logic-0, logic-1, etc sequence. A single parity bit is also included.
The Complete CPS-PDU is now 48-octets, and is now passed unchanged to the ATM
layer, to be built directly into an ATM cell.
ATM Adaption Layer5 (AAL5)
The most recent of the adaptation layers, AAL 5 is also becoming the most popular and has largely
superseded AAL3/4. Often referred to as the Simple And Efficient Adaptation Layer (SEAL), it supports
a wide variety of applications. It is the adaptation layer of choice for the ATM signalling protocol
on VCI 5. MPEG video and Frame Relay also use AAL 5. Unlike AAL2 (or AAL 3/4) AAL5 does
not support multiplexing of data from multiple higher layer applications
AAL 5 takes any user data, normally as a frame, adds some padding and an 8-byte trailer so that the
whole of the resulting CPCS PDU is N x 48-bytes long. The PDUs are then sent for segmentation
by SAR and forwarded 48-bytes at a time to the ATM layer. When the last cell from the PDU is
given to the ATM layer, the ATM layer is informed that it is the last cell. The ATM layer then sets
the End of User Data bit in the ATM header to inform the receiving end.
In the receiver, the ATM layer passes the payloads up to the SAR sublayer. When the last cell arrives, it is
recognised by the ATM layer. The ATM layer informs the SAR layer that the payload is the last for that
frame. The SAR presents the assembled PDU to the CS. The CS performs a CRC on the PDU and compares
this with the last 4 bytes in the trailer. If the CRCs match, the CS then checks the 2-byte Length Indicator
(LI). The LI field indicates the amount of user data in the PDU so that the CS can remove the padding and
recover the user data. Should the CRC not match, then the whole PDU is discarded. AAL 5 relies on the
application to recover from lost frames. For video applications, the last correct frame received would be
repeated. For LAN data, the transport protocol would arrange for re-transmission of the missing frame.
Figure 4-7 illustrates AAL5 format.
68P02905W21-B 4-11
02-Jun-2004
Figure 4-7 AAL5 format
User Data
1 - 65,535 BYTES 0 - 47 1 1 2 4
CPCS
CPCS-PDU PAYLOAD PAD CPS-UU CPI LI CRC
PDUs
SAR SAR SAR SAR

PAYLOAD PAYLOAD PAYLOAD PDUs
SAR SAR SAR ATM

H H PAYLOAD H
PAYLOAD PAYLOAD CELLS
AAL ATM ADAPTION LAYER LI LENGTH INDICATOR
CRC CYCLIC REDUNDANCY CHECK PDU PROTOCOL DATA UNT
CPCS SERVICE DATA UNIT SDU SERVICE DATA UNIT
CPI COMMON PART INDICATOR
SAR SEGMENTATION AND REASSEMLY
4-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview ATM virtual channels and paths
ATM virtual channels and paths

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
On a physical level, ATM connects via the specification of Virtual Paths (VPs) and Virtual Channels (VCs).
A Virtual Channel will be located inside a Virtual Path. A Virtual Channel Identifier (VCI) will identify
the Virtual Channel and the Virtual Path Identifier (VPI) will identify the Virtual Path (VP).
In total , up to 256 addresses for a VP User to Network Interface (UNI) and 4096 for a VP Network to
Network Interface (NNI) can be used. When VCIs are used, up to 216 channels per path can be addressed.
A virtual channel provides an end-to-end connection, referred to as a Virtual Channel Connection.
This connection in turn may consist of a number of VC and VP components. These components
are illustrated in Figure 4-8 and are defined as follows:
• Virtual Channel Link
A virtual channel link is a unidirectional facility transporting ATM cells between two
consecutive ATM entities where a VCI value is assigned, remapped or removed. For example,
between an ATM endpoint and a VC Switch, or between two VC switches.
• Virtual Channel Connection

A virtual channel connection is a concatenation of virtual channel connections.
• Virtual Path Link

A virtual path link is a unidirectional facility transporting ATM cells between two consecutive
ATM entities where a VPI value is assigned, remapped or removed. For example, between
an ATM endpoint and a VC Switch, or between two VC switches.
• Virtual Path Connection

A virtual path connection is a concatenation of virtual path connections.
Figure 4-8 illustrates virtual channels and paths and their use.
68P02905W21-B 4-13
02-Jun-2004
ATM virtual channels and paths Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-8 Virtual channels and paths and their use
VIRTUAL PATH (VP)
AMT PATH
VIRTUAL CHANNEL (VC)
EACH VP WITHIN THE PHYSICAL LAYER HAS A DIFFERENT VPI VALUE

EACH VC WITHIN A VP HAS A DIFFERENT VCI VALUE
USE OF VIRTUAL CHANNELS AND PATHS
VIRTUAL CHANNEL CONNECTION ENDPOINTS
VIRTUAL CHANNEL CONNECTION
VIRTUAL CHANNEL LINK VIRTUAL CHANNEL LINK
ATM ATM
END VP SWITCH VC SWITCH END
SYSTEM SYSTEM
VC SWITCH
VIRTUAL CHANNEL LINK VIRTUAL PATH LINK VCI AND VPI
VALUES CHANGE
VIRTUAL PATH CONECTION
VIRTUAL PATH CONNECTION ENDPOINTS
4-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview ATM virtual channels and paths
Virtual connection and path switching

When addressing is carried out on VP level only, a VP address would be needed since all the
VCs are inside the VP. Figure 4-9 shows the switch on VP level. If however VCs need to be
switched, a VP Switch combined with a VC Switch would be needed.
The switching in ATM could get complicated at times therefore special tools have
been developed to help with this aspect.
Figure 4-9 Virtual Connection and Path Switching
VC SWITCH
VP SWITCH VP SWITCH
REPRESENTATION OF REPRESENTATION OF
VC AND VP SWITCHING VP SWITCHING
68P02905W21-B 4-15
02-Jun-2004
E1 architecture Chapter 4: Data flow and terrestrial interfaces for UMTS
E1 architecture
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
This section describes the format in which of the data is carried.
Logical Links
In GSM all the data is in digital form, and the path that the data takes is called a Logical Link. The format of
the data is dependent on where in the system the data is and what sort of data needs to be transferred.
E1
In the European GSM system the basic building block of data that gets carried around the
network is based around the multiplexed 2.048 Mbit/s frame.
This frame contains 32 channels of 64 Kbit/s. 30 are used for user information. Channel 0 is reserved
for timing and synchronisation and channel 16 is used for signalling.
E1 also specifies the sampling rate, frequency bandwidth, bits per sample, time slots per frame, output
bit rate, encoding law and the dedicated signalling and synchronisation channels.
E1 specifications
Table 4-2 provide the parameters for the T1/DS1 and E1 specifications.
Table 4-2 E1 specifications
Parameters Valid
Frequency Range 300 - 3400Hz
Sampling Rate 8000Hz
Bits per Sample 8
Bits per Frame 32
Output Bit Rate 2.048 Mbit/s
Encoding Law A Law
Signalling Capabilities TSO SyncTS16 Signalling
4-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview E1 architecture
ATM cell to E1 cell mapping
The ATM cell is mapped into bits 9 to 128 and bits 137 to 256 (that is to say, time slots 1 to 15 and time
slots 17 to 31) of the 2048 kbit/s frame as specified in ITU-T Recommendation G.704[2] and as shown in
Figure 4-10. The ATM cell octet structure shall be aligned with the octet structure of the frame.
There shall be no relationship between the beginning of an ATM cell and the beginning of an 2048
kbit/s transmission frame. Since the frame payload capacity (30 octets) is not an integer multiple
of cell length (53 octets), ATM cells will cross the E1 frame boundary.
Figure 4-10 illustrates ATM cell to E1 cell mapping.
Figure 4-10 ATM cell to E1 mapping
TS0 ATM MAPPING FIELD TS16 ATM MAPPING FIELD

SYNCH 15 OCTETS SIG 15 OCTETES
125 mS E1 frames - 256 BITS PER FRAME
68P02905W21-B 4-17
02-Jun-2004
E1 architecture Chapter 4: Data flow and terrestrial interfaces for UMTS
E link multiplexing
The standard E1 stream can be further multiplexed to put more channels over one
transmission path as shown in Figure 4-11.
Figure 4-11 E1 Series hierarchies
E1 E2 E3 E4 E5
2.048 Mbit/s 8.448 Mbit/s 34.368 139.264 564.992
Mbit/s Mbit/s Mbit/s
30
TCH
x 4 120
TCH
x4 480
TCH
x 4 1,920
TCH 7,680
TCH
x4
4-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Inverse Multiplexing for ATM (IMA)
Inverse Multiplexing for ATM (IMA)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Inverse Multiplexing for ATM (IMA) is a methodology which provides a modular bandwidth for user
access to ATM networks and for connection between ATM network elements, at rates between the
traditional order multiplex level. An example is to achieve rates between the DS1/E1 and DS3/E3
levels in the asynchronous digital hierarchies. DS2/E2 physical links are not necessarily readily
available throughout a given network. Therefore the introduction of ATM Inverse Multiplexers
provides an effective method of combining the transport bandwidths of multiple links (that is to say,
DS1/E1 links) grouped to collectively provide higher intermediate rates.
Multiplexing technique
The ATM Inverse Multiplexing technique involves inverse multiplexing and de-multiplexing of ATM cells in
a cyclical fashion among links grouped to form a higher bandwidth logical link whose rate is approximately
the sum of the link rates. This is referred to as an IMA group. provides a simple illustration of the ATM
Inverse Multiplexing technique in one direction. The same technique applies in the opposite direction.
IMA groups terminate at each end of the IMA virtual link. In the transmit direction, the ATM cell stream
received from the ATM layer is distributed on a cell by cell basis, across the multiple links within the IMA
group. At the far end, the receiving IMA unit recombines the cells from each link, on a cell by cell basis,
recreating the original ATM cell stream. The aggregate cell stream is then passed to the ATM layer.
The IMA interface periodically transmits special cells that contain information that permit reconstruction of
the ATM cell stream at the receiving end of the IMA virtual link. The receiver end reconstructs the ATM
cell stream after accounting for the link differential delays, smoothing CDV introduced by the control cells,
etc. These cells, defined as IMA Control Protocol (ICP) cells, provide the definition of an IMA frame. The
transmitter must align the transmission of IMA frames on all links. This allows the receiver to adjust for
differential link delays among the constituent physical links. Based on this required behavior, the receiver
can detect the differential delays by measuring the arrival times of the IMA frames on each link.
At the transmitting end, the cells are transmitted continuously. If there are no ATM layer cells to be
sent between ICP cells within an IMA frame, then the IMA transmitter sends filler cells to maintain a
continuous stream of cells at the physical layer. The insertion of Filler cells provides cell rate decoupling
at the IMA sublayer. The Filler cells should be discarded by the IMA receiver.
68P02905W21-B 4-19
02-Jun-2004
Inverse Multiplexing for ATM (IMA) Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-12 Inverse Multiplexing and De-multiplexing of ATM cells
IMA IMA
PHYSICAL
GROUP LINK #0 GROUP
PHY PHY
PHYSICAL
PHY LINK #1 PHY
SINGLE ATM ORIGINAL ATM CELL

CELLSTREAM FROM STREAM TO ATM
ATM LAYER LAYER
PHY PHY
PHYSICAL
LINK #2
TX DIRECTION: CELLS DISTRIBUTED ACROSS LINKS IN ROUND SEQUENCE

RX DIRECTION: CELLS RECOMMENDED INTO SINGLE ATM STREAM
4-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Inverse Multiplexing for ATM (IMA)
Figure 4-13 IMA Frames
IMA FRAME 2 IMA FRAME 1 IMA FRAME 0
A A A I I I
A A A A A
T T T F C F T T F C T T T F C LINK 0
M M M P P P
M M
2 1 M M M
0
M -1 3 2 1 0 M -1 3 2 1 0 M -1 3 2 1 0
I I I
C A A A A A LINK 1
C A C A
F P T F F T P T T T T P T F F
2 M M M M M
1 M 0 M
F A A I A
I A A I
T T C
A C T T A C A LINK 2
F T F T F T P T
M M P M
P M M
2 M 1 M 0 M
TIME
I A
C IPC CELL IN FILLER T ATM LAYER
P FRAME #1 F CELL
CELL M
1
68P02905W21-B 4-21
02-Jun-2004
Plesiochronous Digital Hierarchy (PDH) Chapter 4: Data flow and terrestrial interfaces for UMTS
Plesiochronous Digital Hierarchy (PDH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of PDH
When already multiplexed streams are added together, a problem with timing arises. Because the timing
sources of each stream are derived from separate clocks, there maybe slight differences in them.
To overcome this synchronisation problem, the output bit rate from the higher order multiplexer is
increased to allow for extra justification bits to be inserted. These justification bits allow the combined
bit streams to sync correctly before retransmission at the higher bit rate.
If, for example, four E1 links are multiplexed together, they will be transmitted over an
8.448 Mbit/s stream, not 8.192 Mbit/s. The channel multiplexing is unaffected, the 30 E1
information channels become 120 in the new stream.
This higher form of multiplexing is called Plesiochronous, which translates to nearly
synchronous. The resulting higher order multiplexing rates are known as Plesiochronous
Digital Heirarchys (PDH). This is illustrated in Figure 4-14.
Figure 4-14 PDH
Nearly Synchronous
140 Mb/s
LTE
140 Mb/s 140 140 140 Mb/s

LTE 34 34 LTE
34 34
8 8
8 8
2 2
Customer
Site
CP13_Ch5_21
4-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Synchronous Digital Hierarchy (SDH)
Synchronous Digital Hierarchy (SDH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
With the advent of fully digital and synchronous networks, the CCITT defined a new multiplexing hierarchy
called Synchronous Digital Hierarchy (SDH). In the USA is called Synchronous Optical Network (SONET)
with the two major differences being terminology and the basic line rates used (SONET - 51.84 Mbit/s).
SDH uses a basic transmission rate of 155.52 Mbit/s (abbreviated to 155 Mbit/s) and multiples of 4n.
This basic rate is known as a Synchronous Transport Module level 1 (STM-1), higher
rates are STM-4 and STM-16.
As with PDH, the signal is repetitive frames with a repeat period of 125 µs. Any of the
PDH rates can be multiplexed into the STM-1.
The main advantages of SDH are:
• It allows direct access to tributary signals without demultiplexing the composite signal.
• It supports advance operations, administration and maintenance by dedicating

channels for this purpose. The network can therefore be reconfigured under
software control from remote terminals.
• Overhead bytes have been preserved for growth to support services and
technologies of the future.
Table 4-3 SDH Bit Rates
Synchronous Transport
Transmission Rate
Module
STM-1 155.52 Mbit/s
STM-4 622.08 Mbit/s
STM-16 2,488.32 Mbit/s
STM-N N x 155.52 Mbit/s
68P02905W21-B 4-23
02-Jun-2004
Synchronous Digital Hierarchy (SDH) Chapter 4: Data flow and terrestrial interfaces for UMTS
Principles of SDH
Figure 4-15 shows the SDH multiplex structure, indicating how an STM is formed from various PDH
traffic rates. The following terms are used in the diagram, and further explained below:
• C — Container
• VC — Virtual Container
• TU — Tributary Units
• TUG — Tributary Unit Group
• AU — Administrative Unit
• AUG — Administrative Unit Group
Table 4-4 lists the suffices used when referring to PDH traffic rates within SDH signals.
Table 4-4 SDH
n Suffix Bit rate kbit/s

0 64
11 1,554
12 2,048
21 6,312
22 8,448
31 34,368
32 44,736
4 139,264
4-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Synchronous Digital Hierarchy (SDH)
Figure 4-15 SDH Multiplex Structure
X1
140
STM-4 AUG AU-4 VC-4 C-4 MBIT/S
X3
X1
TUG-3 TU-3 VC-3
X3
X7 45
MBIT/S
AU-4 VC-3 C-3
35
MBIT/S
X7
X1
6
TUG-2 TU-2 VC-2 C-2 MBIT/S
X3
TU-12 VC-12 C-12 2

MBIT/S
X4
1.5
TU-11 VC-11 C-11 MBIT/S
ATM to STM Mapping
B-ISDN maintains a transmission rate of 155.520 Mbit/s or 622.080 Mbit/s. The physical medium can be
optical with an extension capability of 0 - 800 m or coaxial cable with an extension capability of 0 - 100 m.
The SDH-based signal is formed by filling the VC-4 payload space of an STM frame with ATM cells and
the OAM ( Operations, Administration & Maintenance ) signals are transported via STMs SOH or POH
( Section overhead, Path overhead ). Since, in case of the transmission speed being 155.520 Mbit/s, only
149.760 Mbit/s is filled with ATM cells and the other 5.760 Mbit/s is filled with STM frame overheads
(SOH, POH, Pointer ). Identifying cell boundaries is done using HEC or an SDH overhead.
68P02905W21-B 4-25
02-Jun-2004
Synchronous Digital Hierarchy (SDH) Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-16 ATM to STM Mapping
9 OCTETS 261 OCTETS

STM-1
3
SOH
1 OCTECT 260 OCTETS
VC-4
1
AU4-PTR J1
B3
C2
5 SCH
G1
H4
ATM CELL
53 OCTETS
VC-4 POH
4-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Typical UMTS ATM Transport Network
Typical UMTS ATM Transport Network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 4-17 shows a typical implementation of an ATM transport network to support the UMTS interfaces.
The UMTS nodes as shown are connected to a single SDH ring, whereas there may actually be several rings
involved depending on the network providers configuration and may include PDH interfaces as well.
Node Bs use E1 physical interfaces and in the case where multiple E1s are used IMA is utilised by the
Node B. The ATM Mux shown in the figure is expected to provide E1 (VC-12) to STM-1 (VC-4) mapping
and vice versa in addition to providing IMA and reverse IMA capability. For a large number of Node
B’s, the transport network will have to provide a significant number of E1 interfaces.
The ATM switch will be utilised for VP and VC switching and will be expected to provide aggregation of
logical interfaces to physical interfaces via VP and VC switching. The ATM network is also expected to be
configurable to limit the throughput of a given physical interface. For example, the RNC STM-1 physical
interfaces need to be limited to a bandwidth of 100 Mbit/s due to the hardware limitations.
68P02905W21-B 4-27
02-Jun-2004
Typical UMTS ATM Transport Network Chapter 4: Data flow and terrestrial interfaces for UMTS
Figure 4-17 Typical ATM transport network
ETHERNET
(OPTION UNDER
INVESTIGATION) STM-1 RNC
OMC-R
STM-1 ATM SWITCH

ETHERNET
MSCU
RNC
SDH RING STM-1
(STM-1/STM-4/STM-16)
NODE B ATM SWITCH
ATM MUX
E1, IMA STM-1 SGSN
E1, IMA STM-1
E1, IMA
NODE B
NODE B RNC
NODE B
4-28 68P02905W21-B
02-Jun-2004
Chapter
5
Air Interface Physical Layer
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 5-1
02-Jun-2004
Introduction to this chapter Chapter 5: Air Interface Physical Layer

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Chapter overview
This chapter describes the UMTS Air Interface Physical Layer.
Topics covered in this chapter
This chapter describes the following:

• "Overview of the Physical Layer" on page 5-4.
• "Structure of transmission" on page 5-7.
• "Channels on the Air Interface" on page 5-8.
• "Channel mapping" on page 5-15.
• "Generic frame structure" on page 5-17.
• "Synchronization Channel (SCH)" on page 5-19.
• "Common Pilot Channel (CPICH)" on page 5-21.
• "P-CCPCH frame structure" on page 5-23.
• "Paging Indicator Channel (PICH)" on page 5-25.
• "Secondary Common Control Physical Channel (S-CCPCH)" on page 5-26.
• "Acquisition Indicator Channel (AICH)" on page 5-30.
• "Structure of PRACH Message Part" on page 5-31.
• "Downlink dedicated physical channels" on page 5-33.
• "Uplink dedicated physical channels" on page 5-36.
• "Downlink flow process" on page 5-38.
• "Channel coding" on page 5-40.
• "Rate matching and insertion of DTX indication" on page 5-42.
• "Transport channel multiplexing and Physical Layer segmentation" on page 5-44.
• "Downlink spreading and channel combination" on page 5-46.
• "Uplink flow process" on page 5-48.
5-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Introduction to this chapter
• "Uplink spreading and channel combination" on page 5-50.
68P02905W21-B 5-3
02-Jun-2004
Overview of the Physical Layer Chapter 5: Air Interface Physical Layer
Overview of the Physical Layer

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Physical Layer Services
Most of the air interface tasks are performed in the Physical Layer (L1).
The physical layer offers data transport services to higher layers. The access to these services is
through the use of transport channels via the MAC sub-layer. The physical layer is expected to
perform the following functions in order to provide the data transport service.
• Macrodiversity distribution, combining and soft handover execution.
• Error detection on transport channels and indication to higher layers.
• FEC encoding/decoding of transport channels.
• Multiplexing of transport channels and demultiplexing of coded composite

transport channels (CCTrCHs).
• Rate matching of coded transport channels to physical channels.
• Mapping of coded composite transport channels on physical channels.
• Power weighting and combining of physical channels.
• Modulation and spreading/demodulation and despreading of physical channels.
• Frequency and time (chip, bit, slot, frame) synchronisation.
• Radio characteristics measurements including, for example; FER, SIR, Interference

Power, and indication to higher layers.
• Inner - loop power control.
• RF processing.
When network elements (UEs and network) provide compatible service bearers (for example
support a speech bearer) they should be assured of successful interworking. Moreover, different
implementation options of the same (optional) feature would lead to incompatibility between
UE and network. Therefore, this shall be avoided.
QPSK
The modulation scheme used in CDMA is quadrature phase shift keying (PSK) which allows
2 bits to be sent per symbol (I and Q). The reason for using QPSK is that it is fairly resilient
to amplitude variations. The major problem with CDMA is that all users are on the same
frequency and thus interfering with each other. See Figure 5-1.
5-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of the Physical Layer
Figure 5-1 QPSK modulation scheme
(0, 1) (0, 0)
(1, 1) (1, 0)
2 BITS PER SYMBOL
Channel locations
The Radio Interface is the section of the network between the UE and the Network. This is where the
biggest limitation lies at the moment, therefore very complex methods have to be invented in order to
transmit the required data at the high speeds that is demanded of today’s networks.
The radio interface is composed of Layers 1, 2 and 3. Figure 5-2 shows the UTRA radio interface protocol
architecture around the physical layer (Layer 1). The physical layer interfaces with the Medium Access
Control (MAC) sub-layer of Layer 2 and the Radio Resource Control (RRC) Layer of Layer 3.
The physical layer offers different Transport channels to MAC. A transport channel is characterized
by how the information is transferred over the radio interface.
MAC offers different Logical channels to the Radio Link Control (RLC) sub-layer of Layer 2.
The type of information transferred characterizes a logical channel.
Physical channels are defined in the physical layer. In FDD mode, physical channels are defined by a
specific carrier frequency, scrambling code, channelization code (optional), time start and stop (giving
duration) and, on the uplink, relative phase (0 or π/2). In the TDD mode the physical channels is
also characterized by the timeslot. The physical layer is controlled by RRC.
68P02905W21-B 5-5
02-Jun-2004
Overview of the Physical Layer Chapter 5: Air Interface Physical Layer
Figure 5-2 Layers 1, 2 and 3
LOGICAL CHANNELS
LAYER 2
MAC
TRANSPORT CHANNELS
LAYER 1
PHYSICAL LAYER
PHYSICAL CHANNELS
UE
5-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Structure of transmission
Structure of transmission
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Physical Layer receives information, on a transport channel, as Transport Blocks (or Transport
Block sets) from Layer 2. This information will consist of User Plane or Control Plane streams. In
addition the physical layer will generate Layer 1 control information, used to maintain the radio
bearer between the UE and the UTRAN. This Layer 1 control information must be transmitted on
the physical channel along with the transport channel information.
Even when FDD mode is in use, a Radio Frame/Time Slot structure is observed. (A 10 mS
radio frame is divided into 15 timeslots). Though it is important to note that any given radio
bearer is able to use all timeslots in every radio frame.
Downlink transmission
On the downlink each timeslot will contain transport channel information and Layer 1 control
information in time-multiplex. Each timeslot will contain fields supporting transport block information,
interspersed with Layer 1 control fields. The exact structure of the fields is dependent upon the type
of physical channel in use, and is described in detail later in this section.
Uplink transmission
On the Uplink a time-multiplex structure is not practical as Discontinuous Transmission (DTX) is

frequently employed. The combination of DTX and Time-multiplex would result in a Bursty transmission,
which would generate audio band noise perceptible to the other party in a voice call.
To overcome this problem, the transport channel information and Layer 1 control information are I/Q code
multiplexed within each timeslot, allowing them to be transmitted in parallel. This makes the transmission of
Layer 1 control information continuous and hence prevents bursty transmission, even when DTX is applied.
68P02905W21-B 5-7
02-Jun-2004
Channels on the Air Interface Chapter 5: Air Interface Physical Layer
Channels on the Air Interface

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of Air Interface channels
Figure 5-3 illustrates the Air Interface channels.
Figure 5-3 Air Interface channels
DCCH DTCH BCCH PCCH CCCH CTCH

LOGICAL
CHANNELS
PTM
CCH
TRANSPORT
DCH CHANNELS
BCH PCH FACH USCH RACH CPCH

DSCH
PDCH PCCH
P-CCPCH S-CCPCH PICH PRACH SCH CPICH AICH PCPCH PDSCH
PHYSICAL
CHANNELS
* *
DPCCH DPDCH P-SCH S-SCH PRIMARY SECONDARY
5-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Channels on the Air Interface
Logical channels
The MAC layer provides data transfer services on logical channels. A set of logical channel
types is defined for different kinds of data transfer services as offered by MAC. Each logical
channel type is defined by what type of information is transferred.
A general classification of logical channels is into two groups:
• Control Channels (for the transfer of control plane information).
• Traffic Channels (for the transfer of user plane information).
Figure 5-4 illustrates the logical channels.
Control channels
• Broadcast Control Channel (BCCH)
A downlink channel for broadcasting system control information.
• Paging Control Channel (PCCH)

A downlink channel that transfers paging information. This channel is used when
the network does not know the location cell of the UE, or, the UE is in the cell
connected state (utilising UE sleep mode procedures).
• Common Control Channel (CCCH)

Bi-directional channel for transmitting control information between network and UEs. This
channel is commonly used by the UEs having no RRC connection with the network and by the
UEs using common transport channels when accessing a new cell after cell reselection.
• Dedicated Control Channel (DCCH)

A point-to-point bi-directional channel that transmits dedicated control information between a
UE and the network. This channel is established through RRC connection setup procedure.
68P02905W21-B 5-9
02-Jun-2004
Traffic channels
For the following, refer to Figure 5-4.
• Dedicated Traffic Channels (DTCH)
A Dedicated Traffic Channel (DTCH) is a point-to-point channel, dedicated to one UE, for
the transfer of user information. A DTCH can exist in both uplink and downlink.
• Common Traffic Channel (CTCH)

A point-to-multipoint unidirectional channel for transfer of dedicated user
information for all or a group of specified UEs.
Figure 5-4 Logical channels
BETWEEN MAC AND HIGHER APPLICATIONS
DCCH DTCH BCCH PCCH CCCH CTCH
U-RNTI PTM
5-10 68P02905W21-B
02-Jun-2004
Transport channels
The physical layer offers information transfer services to MAC and higher layers. The physical layer transport
services are described by how and with what characteristics data is transferred over the radio interface. An
adequate term for this is Transport Channel. A general classification of transport channels is into two groups:
• Common transport channels (where there is a need for inband identification of
the UEs when particular UEs are addressed.
• Dedicated transport channels (where the UEs are identified by the physical channel, that is
the code and frequency for FDD and code and time slot and frequency for TDD).
Figure 5-5 illustrates the Transport channels.
Random Access Channel (RACH)

A contention based uplink channel used for transmission of relatively small amounts of data, for
example; initial access or non-real-time dedicated control or traffic data.
Common Packet Channel (CPCH)

A contention based channel used for transmission of bursty data traffic. This channel only exists in
FDD mode and only in the uplink direction. The common packet channel is shared by the UEs in
a cell and therefore, it is a common resource. The CPCH is fast power controlled.
Forward Access Channel (FACH)

Common downlink channel without closed-loop power control used for transmission
of relatively small amount of data.
Uplink Shared Channel (USCH)

An uplink channel shared by several UEs carrying dedicated control or traffic data, used in TDD mode only.
Broadcast Channel (BCH)

A downlink channel used for broadcast of system information into an entire cell.
Paging Channel (PCH)

A downlink channel used for broadcast of control information into an entire cell allowing efficient
UE sleep mode procedures. Currently identified information types are paging and notification.
Another use could be UTRAN notification of change of BCCH information.
Dedicated Channel (DCH)

A channel dedicated to one UE used in uplink or downlink.
68P02905W21-B 5-11
02-Jun-2004
Figure 5-5 Transport channels
BETWEEN THE PHYSICAL LAYER AND MAC
CCH
DCH
BCH PCH FACH RACH CPCH
USCH
DSCH
5-12 68P02905W21-B
02-Jun-2004
Physical channels
The Common Physical Channels (CPCHs) are shown in Table 5-1. Figure 5-6 illustrates the Physical channels.
Table 5-1 Common Physical Channels (CPCHs)
Channel Acrynom description

P-SCH Primary Synchronisation Channel
S-SCH Secondary Synchronisation Channel
Synchronisation to the network
P-CCPCH Primary Common Control Physical Channel
Cell Information
Frequency info
S-CCPCH Secondary Common Control Physical Channel
Paging Information and Transfer of small amounts of user data.
Downlink only.
PRACH Physical Random Access Channel
Initial message when UE wants to gain access to the network
Transfer of small amounts of data
Uplink only
PCPCH Physical Common Packet Channel
Extension of the PRACH Channel that is intended to carry
packer-based user data in the uplink direction.
PICH Paging Indicator Channel
Provides UEs with efficient sleep mode operation
AICH Acquisition Indicator Channel
Acknowledges an effective request for access after preamble has been
send up
Carry information associated with the DCHs
P-CPICH Primary Common Pilot Indicator Channel
S-CPICH Secondary Pilot Indicator Channel
Helps with channel estimation and shows the attractiveness of the cell
DPDCH Dedicated Physical Channels
DPCCH
Uplink and downlink control and data information
Dedicated to a single user
68P02905W21-B 5-13
02-Jun-2004
Figure 5-6 Physical channels
BETWEEN THE PHYSICAL LAYER AND THE UE
PDCH PCCH
P-CCPCH S-CCPCH PICH PRACH SCH CPICH AICH PCPCH PDSCH
PHYSICAL
CHANNELS
* *
DPCCH DPDCH P-SCH S-SCH PRIMARY SECONDARY
CP13_Ch7_13
5-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Channel mapping
Channel mapping
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 5-7 summarises the mapping of logical channels onto transport channels, and
transport channels onto physical channels.
The DCHs are coded and multiplexed, and the resulting data stream is mapped sequentially
(first-in-first-mapped) directly to the physical channel(s).
The mapping of BCH and FACH/PCH is equally straightforward, where the data stream after coding and
interleaving is mapped sequentially to the Primary and Secondary CCPCH respectively.
The BCCH logical channel can be mapped to both BCH and FACH, so as to be available to idle
mode and connected mode UEs respectively. Also for the RACH, the coded and interleaved bits
are sequentially mapped to the physical channel, in this case the message part of the PRACH.
Physical signals
Physical signals are entities with the same basic on-air attributes as physical channels but do not
have transport channels or indicators mapped to them. Physical signals may be associated with
physical channels in order to support the function of physical channels. SCH, CPICH, and AICH
are classified as physical signals and hence are not shown on the map opposite.
68P02905W21-B 5-15
02-Jun-2004
Channel mapping Chapter 5: Air Interface Physical Layer
Figure 5-7 Channel mapping
UPLINK
DCCH
CCCH
DTCH
RACH CPCH DCH
PRACH PCPCH DOCCH

PPDCH
DOWNLINK
DCCH
PCCH BCCH CCCH CTCH
DTCH
PAGING BROADCAST COMMON COMMON DEDICATED

CONTROL CONTROL CONTROL TRAFFIC CONTROL CHANNEL
CHANNEL CHANNEL CHANNEL CHANNEL DEDICATED
TRAFFIC CHANNEL
PCH BCH FACH DSCH DCH
DOWNLOAD
SHARED
CHANNEL
PRIMARY
CCPCH
DPDCH
PDSCH DPCCH
SEC
PHYSICAL
CCPCH DOWNLOAD
CHANNEL
5-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Generic frame structure
Generic frame structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 5-8 illustrates the generic frame structure, use to delimit the transfer of units
of information on the UMTS air interface.
Figure 5-8 Generic frame structure
SLOT
TSLOT =SLOT
2560 CHIPS
FRAME
TS0 TS1 TSn FRAME TS13 TS14

TS0
666ms TS1 TSn
SYSTEM FRAME
666ms
FRAME FRAME FRAME FRAME
1 n SYSTEM FRAME
4096 4096
10ms Frame Frame

1 40.96 secs n
Radio frame
The basic unit of the air interface is the radio frame. A radio frame is defined as “A processing duration
which consists of 15 timeslots. The length of a radio frame corresponds to 38,400 chips." With a system
chip rate of 3.84 McpS being employe, a radio frame thus has a duration of 10 mS.
68P02905W21-B 5-17
02-Jun-2004
Generic frame structure Chapter 5: Air Interface Physical Layer
System frame
Several physical layer procedures (for example, Paging and random access) span more than a
single frame, being the. To accommodate these procedures, a system frame is defined. The frame
within the system frame structure is identified by a System Frame Number (SFN), which is a 12
bit binary number, thus a System Frame can consist of 4096 frames.
Timeslot
Each radio frame consists of 15 timeslots. “A slot duration consists of fields containing bits.
The length of the slot always corresponds to 2560 chips." The time duration of a timeslot is
approximately 666 microseconds. The number of fields within each timeslot is dependent upon the
physical channel in use. Similarly the number of bits which can be accommodate by a timeslot is
dependent upon the spreading factor in use for that physical channel.
5-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Synchronization Channel (SCH)
Synchronization Channel (SCH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Synchronization Channel (SCH) is a downlink signal used for cell search. The SCH consists of two sub
channels, the Primary and Secondary SCH. The 10 ms radio frames of the Primary and Secondary SCH are
divided into 15 slots, each of length 2560 chips. Figure 5-9 illustrates the structure of the SCH radio frame.
Figure 5-9 Primary and Secondary synchronization codes modulated by the symbol a
TSLOT = 2560 CHIPS
256 CHIPS
PRIMARY
SCH
acp acp acp acp acp
SECONDARY
SCH
acsi, 0 acsi, 1 acsi, 2 acsi, 3 acsi, 4
ONE 10MS SCH RADIO FRAME
Primary SCH
The Primary SCH consists of a modulated code of length 256 chips, the Primary Synchronization Code (PSC)
denoted cp in the diagram, transmitted once every slot. The PSC is the same for every cell in the system.
Secondary SCH
The Secondary SCH consists of repeatedly transmitting a length 15 sequence of modulated codes of length 256
chips, the Secondary Synchronization Codes (SSC), transmitted in parallel with the Primary SCH. The SSC is
denoted csi,k in the diagram, where i = 0, 1, …, 63 is the number of the scrambling code group, and k = 0, 1,
…, 14 is the slot number. Each SSC is chosen from a set of 16 different codes of length 256. This sequence on
the Secondary SCH indicates which of the code groups the cell’s downlink scrambling code belongs to.
68P02905W21-B 5-19
02-Jun-2004
Synchronization Channel (SCH) Chapter 5: Air Interface Physical Layer
Modulation a
The primary and secondary synchronization codes are modulated by the symbol a shown in
the Figure 5-9, which indicates the presence/ absence of STTD encoding on the P-CCPCH
and is given by the following Table 5-2.
Table 5-2 Modulation a
P-CCPCH STTD encoded a=+1

P-CCPCH not STTD encoded a=-1
Synchronization (Cell Search) procedure
During the cell search, the UE searches for a cell and determines the downlink scrambling code and
frame synchronization of that cell. The cell search is typically carried out in three steps.
Step 1: Slot synchronization

During the first step of the cell search procedure the UE uses the SCHs primary synchronization code
to acquire slot synchronization to a cell. This is typically done with a single matched filter (or any
similar device) matched to the primary synchronization code which is common to all cells. The slot
timing of the cell can be obtained by detecting peaks in the matched filter output.
Step 2: Frame synchronization and code-group identification

During the second step of the cell search procedure, the UE uses the SCHs secondary synchronization
code to find frame synchronization and identify the code group of the cell found in the first step.
This is done by correlating the received signal with all possible secondary synchronization code
sequences, and identifying the maximum correlation value. Since the cyclic shifts of the sequences
are unique the code group as well as the frame synchronization is determined.
Step 3: Scrambling-code identification

During the third and last step of the cell search procedure, the UE determines the exact primary
scrambling code used by the found cell. The primary scrambling code is typically identified through
symbol-by-symbol correlation over the CPICH with all codes within the code group identified in
the second step. After the primary scrambling code has been identified, the Primary CCPCH can be
detected and the system- and cell specific BCH information can be read.
If the UE has received information about which scrambling codes to search for, steps
2 and 3 above can be simplified.
5-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Common Pilot Channel (CPICH)
Common Pilot Channel (CPICH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The CPICH is a fixed rate (30 kbit/s, SF=256) downlink physical channel that carries a pre-defined
bit/symbol sequence. Figure 5-10 shows the frame structure of the CPICH.
In case transmit diversity (open or closed loop) is used on any downlink channel in the cell, the
CPICH shall be transmitted from both antennas using the same channelization and scrambling code.
In this case, the pre-defined symbol sequence of the CPICH is different for Antenna 1 and Antenna
2. In case of no transmit diversity, the symbol sequence of Antenna 1 is used.
There are two types of Common pilot channels, the Primary and Secondary CPICH. They differ
in their use and the limitations placed on their physical features.
Figure 5-11 illustrates the modulation pattern for the Common Pilot Channel.
Primary Common Pilot Channel (P-CPICH)
The Primary Common Pilot Channel (P-CPICH) has the following characteristics:
• The same channelization code is always used for the P-CPICH (SF=256,0).
• The P-CPICH is scrambled by the primary scrambling code.
• There is one and only one P-CPICH per cell.
• The P-CPICH is broadcast over the entire cell.
The Primary CPICH is the phase reference for the following downlink channels: SCH, Primary CCPCH,
AICH, PICH. The Primary CPICH is also the default phase reference for all other downlink physical channels.
Secondary Common Pilot Channel (S-CPICH)
A Secondary Common Pilot Channel (S-CPICH) has the following characteristics:

An arbitrary channelization code of SF=256 is used for the S-CPICH.
A S-CPICH is scrambled by either the primary or a secondary scrambling code.
There may be zero, one, or several S-CPICH per cell.
A S-CPICH may be transmitted over the entire cell or only over a part of the cell.
A Secondary CPICH may be the reference for the Secondary CCPCH and the downlink DPCH. If
this is the case, the UE is informed about this by higher-layer signalling.
68P02905W21-B 5-21
02-Jun-2004
Common Pilot Channel (CPICH) Chapter 5: Air Interface Physical Layer
Figure 5-10 CPICH Frame Structure
PRE-DEFINED SYMBOL SEQUENCE
Tslot = 2560 CHIPS, 20 BITS = 10 SYMBOLS
SLOT #0 SLOT #1 SLOT #i SLOT #14
1 RADIO FRAME: Tf = 10ms
Figure 5-11 Modulation pattern for the Common Pilot Channel
ANTENNA 1 A A A A A A A A A A A A A A A A A A A A A A A A
ANTENNA 2 -A -A A A -A -A A A -A A -A -A A A -A -A A A -A -A A A -A -A
SLOT #14 SLOT #0 SLOT #1
FRAME#1 FRAME#i+1
FRAME BOUNDARY
5-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview P-CCPCH frame structure
P-CCPCH frame structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Primary CCPCH is a fixed rate (30 kbit/s, SF=256) downlink physical channels used to carry the BCH.
Figure 5-12 illustrates the frame structure of the Primary CCPCH.
The frame structure differs from the downlink DPCH in that no TPC commands, no TFCI and no pilot
bits are transmitted The Primary CCPCH is not transmitted during the first 256 chips of each slot.
Instead, Primary SCH and Secondary SCH are transmitted during this period.
Figure 5-12 P-CCPCH frame structure
256 CHIPS
(Tx OFF) DATA 18 BITS
Tslot = 2560 CHIPS, 20 BITS
Tf = 10ms
FRAME #0 FRAME #1 FRAME #i FRAME #71
Tsuper = 720 ms
SCH and P-CCPCH
Figure 5-13 shows the construction of the SCH and the P-CCPCH. It is thus clear that different
channels can be multiplexed onto one link. The structure of these two Physical Channels
are very important to the synchronization process.
68P02905W21-B 5-23
02-Jun-2004
P-CCPCH frame structure Chapter 5: Air Interface Physical Layer
Figure 5-13 SCH and P-CCPCH structure
SCH
FRAME 0 FRAME 1 FRAME 2

DATA ON P-CCPCH DATA ON P-CCPCH DATA ON P-CCPCH
5-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Paging Indicator Channel (PICH)
Paging Indicator Channel (PICH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Paging Indicator Channel (PICH) is a fixed rate (SF=256) physical channel used to carry the Paging
Indicators (PI). The PICH is always associated with an S-CCPCH to which a PCH transport channel is mapped.
Figure 5-14 illustrates the frame structure of the PICH. One PICH radio frame of length 10 ms
consists of 300 bits (b0, b1, …, b299). Of these, 288 bits (b0, b1, …, b287) are used to carry Paging
Indicators. The remaining 12 bits are not formally part of the PICH and shall not be transmitted. The
part of the frame with no transmission is reserved for possible future use.
N Paging Indicators {PI0, …, PIN-1} are transmitted in each PICH frame, where N=18, 36, 72, or 144.
The PI calculated by higher layers for use for a certain UE, is mapped to the paging indicator PIp, where p is
computed as a function of the PI computed by higher layers, the SFN of the P-CCPCH radio frame during
which the start of the PICH radio frame occurs, and the number of paging indicators per frame (N), as in :.
P = {PI + [((18 x (SFN + [SFN/8] + [SFN/64] +[SFN/512]))mod 144) x (N/144)]) mod N
The mapping from {PI0, …, PIN-1} to the PICH bits {b0, …, b287} are according to table 22.
If a Paging Indicator in a certain frame is set to "1" it is an indication that UEs associated with this Paging
Indicator should read the corresponding frame of the associated S-CCPCH as shown in Figure 5-14.
Figure 5-14 Structure of the Paging Indicator Channel (PICH)
12 BITS
288 BITS FOR PAGING INDICATION (TRANSMISSION OFF)
b0 b1 b287 b288 b289
ONE RADIO FRAME (10 ms)
68P02905W21-B 5-25
02-Jun-2004
Secondary Common Control Physical Channel (S-CCPCH) Chapter 5: Air Interface Physical Layer
Secondary Common Control Physical Channel

(S-CCPCH)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Secondary CCPCH is used to carry the FACH and PCH. There are two types of Secondary
CCPCH; those that include TFCI and those that do not include TFCI. It is the UTRAN that
determines if a TFCI should be transmitted, hence making it mandatory for all UEs to support the
use of TFCI. The set of possible rates for the Secondary CCPCH is the same as for the downlink
DPCH. The frame structure of the Secondary CCPCH is shown opposite.
The parameter k in the diagram determines the total number of bits per downlink Secondary CCPCH slot.
It is related to the spreading factor SF of the physical channel as SF = 256/2k. The spreading factor range
is from 256 down to 4. The values for the number of bits per field are given in the table opposite. The
channel bit and symbol rates given in the table are the rates immediately before spreading.
The FACH and PCH can be mapped to the same or to separate Secondary CCPCHs. If FACH and PCH
are mapped to the same Secondary CCPCH, they can be mapped to the same frame.
The main difference between a CCPCH and a downlink dedicated physical channel is that
a CCPCH is not inner-loop power controlled.
The main difference between the Primary and Secondary CCPCH is that the transport channel mapped to the
Primary CCPCH (BCH) can only have a fixed predefined transport format combination, while the Secondary
CCPCH support multiple transport format combinations using TFCI. Furthermore, a Primary CCPCH is
transmitted over the entire cell while a Secondary CCPCH may be transmitted in a narrow lobe in the same
way as a dedicated physical channel (only valid for a Secondary CCPCH carrying the FACH).
For slot formats using TFCI, the TFCI value in each radio frame corresponds to a certain
transport format combination of the FACHs and/or PCHs currently in use. This correspondence
is (re-)negotiated at each FACH/PCH addition/removal.
Figure 5-15 illustrates the S-CCPCH structure.
5-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Secondary Common Control Physical Channel (S-CCPCH)
Figure 5-15 S-CCPCH structure
TFCI DATA Pilot

NTFCIBITS DdataBITS NpilotBITS
Tslot = 2560 CHIPS, 20*2kBITS (K = 0..6)
1 RADIO FRAME, Tf = 10ms
68P02905W21-B 5-27
02-Jun-2004
Random Access Transmission Chapter 5: Air Interface Physical Layer
Random Access Transmission

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The random-access transmission is based on a Slotted ALOHA approach with fast acquisition indication.
The UE can start the random-access transmission at the beginning of a number of well-defined time
intervals, denoted access slots. There are 15 access slots per two frames and they are spaced 5120 chips
apart, see Figure 5-16. Information on what access slots are available for random-access transmission
is given by higher layers and is based upon the Access Service Class (ASC) of the UE
Figure 5-16 RACH access slot numbers and their spacing
RADIO FRAME: 10ms RADIO FRAME: 10ms
5120
CHIP
S
ACCESS
SLOT #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
RANDOM ACCESS TRANSMISSION
Structure of Random Access Transmission
The structure of the random-access transmission is also shown opposite. The random-access transmission
consists of one or several preambles of length 4096 chips and a message of length 10 ms or 20 ms.
Figure 5-17 illustrates the structure of the random-access transmission.
5-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Random Access Transmission
Figure 5-17 Structure of the random-access transmission
PREAMBLE PREAMBLE PREAMBLE MESSAGE PART
4096 CHIPS 10 ms (ONE RADIO FRAME)
PREAMBLE PREAMBLE PREAMBLE MESSAGE PART
4096 CHIPS 20 ms (TWO RADIO FRAME)
PRACH Preamble
Each preamble is of length 4096 chips and consists of 256 repetitions of a signature of length
16 chips. There are a maximum of 16 available signatures.
68P02905W21-B 5-29
02-Jun-2004
Acquisition Indicator Channel (AICH) Chapter 5: Air Interface Physical Layer
Acquisition Indicator Channel (AICH)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Acquisition Indicator channel (AICH) is a fixed rate (SF=256) physical channel used to carry Acquisition
Indicators (AI). Acquisition Indicator AIs corresponds to signature s on the PRACH.
Figure 5-18 illustrates the structure of the AICH.
The AICH consists of a repeated sequence of 15 consecutive access slots (AS), each of length
5120 chips. Each access slot consists of two parts, an Acquisition-Indicator (AI) part consisting
of 32 real-valued symbols a0, …, a31 and a part of duration 1024 chips with no transmission that is
not formally part of the AICH. The part of the slot with no transmission is reserved for possible
use by CSICH or possible future use by other physical channels.
The spreading factor (SF) used for channelization of the AICH is 256.
The phase reference for the AICH is the Primary CPICH.
The real-valued symbols a0, a1, …, a31 are given by:
where AIs, taking the values +1, -1, and 0, is the acquisition indicator corresponding to signature s
and the sequence bs,0, …, bs,31 is given in the table opposite. The real-valued symbols, aj, are spread
and modulated in the same fashion as bits when represented in { +1, -1 } form. .
Figure 5-18 Acquisition Indicator Channel (AICH)
AI PART = 4096 CHIPS, 32 REAL-VALUED SYMBOLS 1024 CHIPS
a0 a1 a2 a30 a31 TRANSMISSION OFF
AS # 14 AS # 0 AS # 1 AS # i AS # 14 AS # 0
20 ms
5-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Structure of PRACH Message Part
Structure of PRACH Message Part

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The structure of the Random-access message part is shown in Figure 5-19. The 10 ms message
is split into 15 slots, each of length Tslot = 2560 chips. Each slot consists of two parts, a data
part that carries Layer 2 information and a control part that carries Layer 1 control information.
The data and control parts are transmitted in parallel.
The data part consists of 10*2k bits, where k=0,1,2,3. This corresponds to a spreading factor
of 256, 128, 64, and 32 respectively for the message data part. The value for the number
of bits in the data field are given in the table opposite.
The control part consists of 8 known pilot bits to support channel estimation for coherent detection
and 2 TFCI bits. This corresponds to a spreading factor of 256 for the message control part. The
total number of TFCI bits in the random-access message is 15*2 = 30. The TFCI value corresponds
to a certain transport format of the current Random-access message.
The Random Access Channel(s) (RACH) is characterised by:
• Existence in uplink only
• Limited data field
• Collision risk
• Open loop power control
68P02905W21-B 5-31
02-Jun-2004
Structure of PRACH Message Part Chapter 5: Air Interface Physical Layer
Figure 5-19 Structure of the PRACH Message Part
DATA
DATA NdataBITS
CONTROL DATA TFCI

NpilotBITS NTFCI BITS
Tslot = 2560 CHIPS, 10*2kBITS (k = 0..3)
MESSAGE PART RADIO FRAME TRACH = 10ms
5-32 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Downlink dedicated physical channels
Downlink dedicated physical channels

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
There is only one type of downlink dedicated physical channel, the Downlink Dedicated
Physical Channel (downlink DPCH).
Within one downlink DPCH, dedicated data generated at Layer 2 and above, that is to say, the dedicated
transport channel (DCH), is transmitted in time-multiplex with control information generated at Layer 1
(known pilot bits, TPC commands, and an optional TFCI). The downlink DPCH can thus be seen as a
time multiplex of a downlink DPDCH and a downlink DPCCH, compare subclause.
Figure 5-20 shows the frame structure of the downlink DPCH. Each frame of length 10 ms is split into 15
slots, each of length Tslot = 2560 chips, corresponding to one power-control period. The parameter k in the
diagram determines the total number of bits per downlink DPCH slot. It is related to the spreading factor SF
of the physical channel as SF = 512/2k. The spreading factor may thus range from 512 down to 4. The exact
number of bits of the different downlink DPCH fields (Npilot, NTPC, NTFCI, Ndata1 and Ndata2) is dependent upon
the SF. What slot format to use is configured by higher layers and can also be reconfigured by higher layers.
There are basically two types of downlink Dedicated Physical Channels; those that include TFCI
(that is to say, for several simultaneous services) and those that do not include TFCI (that is to say,
for fixed-rate services). It is the UTRAN that determines if a TFCI should be transmitted and it is
mandatory for all UEs to support the use of TFCI in the downlink.
The Pilot bits are provided to permit frame synchronisation and channel estimation at the receiving node.
TPC symbol will indicate a step increase or decrease of transmitter power by the receiving node. See Table 5-3.
Table 5-3 Dedicated downlink physical channels
Tranmitter power
TPC Bit Pattern
control command
NTPC = 2 NTPC = 4 NTPC = 8
11 1111 11111111 1
00 0000 00000000 0
68P02905W21-B 5-33
02-Jun-2004
Downlink dedicated physical channels Chapter 5: Air Interface Physical Layer
Figure 5-20 Structure of the Downlink DPCH
DPDCH DPCCH DPDCH DPCCH
PILOT
DATA 1 TPC TFCI DATA 2
Npilot Bits
Tslot = 2560 chips
ONE RADIO FRAME = 10ms
Downlink slot formation in case of Multi-Code Transmission
For slot formats using TFCI, the TFCI value in each radio frame corresponds to a certain combination of bit
rates of the DCHs currently in use. This correspondence is re-negotiated at each DCH addition/removal.
When the total bit rate to be transmitted on one downlink CCTrCH exceeds the maximum bit rate for
a downlink physical channel, multicode transmission is employed, that is; several parallel downlink
DPCHs are transmitted for one CCTrCH using the same spreading factor. In this case, the Layer 1 control
information is put on only the first downlink DPCH. The additional downlink DPCHs belonging to the
CCTrCH do not transmit any data during the corresponding time period. See Table 5-4.
Table 5-4 Acronyms
TFCI Transport Formation Combination Indicator

DCH Dedicated Channel
CCTrCH Coded Composite Transport Channel
DPCH Dedicated Physical Channel
TPC Transmit Power Control
Figure 5-21 illustrates the downlink slot format of Multi-Code Transmission.
5-34 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Downlink dedicated physical channels
Figure 5-21 Downlink slot format of multi-code transmission
DPDCH DPDCH
TPC TFCI PILOT
TRANSMISSION PHYSICAL CHANNEL

POWER

POWER

POWER
ONE SLOT (2560 CHIPS)
68P02905W21-B 5-35
02-Jun-2004
Uplink dedicated physical channels Chapter 5: Air Interface Physical Layer
Uplink dedicated physical channels

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
There are two types of uplink dedicated physical channels:

• Uplink Dedicated Physical Data Channel (uplink DPDCH)
• Uplink Dedicated Physical Control Channel (uplink DPCCH).
The DPDCH and the DPCCH are I/Q code multiplexed within each radio frame.
The uplink DPDCH is used to carry the DCH transport channel. There may be zero, one,
or several uplink DPDCHs on each radio link.
The uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information
consists of known pilot bits to support channel estimation for coherent detection, transmit power-control (TPC)
commands, feedback information (FBI), and an optional transport-format combination indicator (TFCI).
The transport-format combination indicator informs the receiver about the instantaneous transport format
combination of the transport channels mapped to the simultaneously transmitted uplink DPDCH radio frame.
There is only one uplink DPCCH on each radio link.
Frame structure
Figure 5-22 shows the frame structure of the uplink dedicated physical channels. Each radio frame of length
10 ms is split into 15 slots, each of length Tslot = 2560 chips, corresponding to one power-control period.
The parameter k in Figure 5-22 determines the number of bits per uplink DPDCH slot. It is related to
the spreading factor SF of the DPDCH as SF = 256/2k. The DPDCH spreading factor may range from
256 down to 4, giving data rates between 15 kit/s and 960 kit/s The spreading factor of the uplink
DPCCH is always equal to 256, (that is, there are 10 bits per uplink DPCCH slot). What slot format
to use is configured by higher layers and can also be reconfigured by higher layers.
The FBI bits are used to support techniques requiring feedback from the UE to the UTRAN Access Point,
including closed loop mode transmit diversity and site selection diversity transmission (SSDT).
There are two types of uplink dedicated physical channels; those that include TFCI (for
example; for several simultaneous services) and those that do not include TFCI (for example;
for fixed-rate services). It is the UTRAN that determines if a TFCI should be transmitted and it
is mandatory for all UEs to support the use of TFCI in the uplink.
Multi-code operation is possible for the uplink dedicated physical channels. When multi-code
transmission is used, several parallel DPDCH are transmitted using different channelization
codes. However, there is only one DPCCH per radio link.
5-36 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Uplink dedicated physical channels
Figure 5-22 Structure for the Uplink DPDCH/DPCCH
DATA
DPDCH Npilot BITS
NdataBITS
PILOT TFCI FBI TPC

DPCCH NTFCIBITS NTFBI BITS NTPC BITS
Npilot BITS
Tslot = 2560 CHIPS, 10*2kBITS (k = 0..6)
Tf = 10ms
FRAME #0 FRAME #1 FRAME #i FRAME #71
Tsuper = 720 ms
68P02905W21-B 5-37
02-Jun-2004
Downlink flow process Chapter 5: Air Interface Physical Layer
Downlink flow process

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The downlink flow process consists of the following physical layer functions.
Data arrives to the coding/multiplexing unit in the form of transport block sets once every transmission time
interval. The transmission time interval is transport-channel specific from the set {10 ms, 20 ms, 40 ms, 80 ms}.
The following coding/multiplexing steps can be identified for downlink:
• Add CRC to each transport block
• Transport block concatenation and code block segmentation
• Channel coding
• Rate matching
• First insertion of discontinuous transmission (DTX) indication bits
• First interleaving
• Radio frame segmentation
• Multiplexing of transport channels
• Second insertion of DTX indication bits
• Physical channel segmentation
• Second interleaving
• Mapping to physical channels
It should be noted that not every step is applicable to every data type.
Figure 5-23 illustrates the transport multiplexing structure for the downlink.
5-38 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Downlink flow process
Figure 5-23 Transport Channel Multiplexing Structure for the Downlink
CRC ATTACHMENT
TrBk CONCATENTATION
CODE BLOCK SEGMENTATION
CHANNEL CODING
RATE MATCHING RATE MATCHING
1st INSERTION OF DTX

INDICATION
1st INTERLEAVING
RADIO FRAME SEGMENTATION
TrCH MULTIPLEXING
2nd INSERTION OF DTX

INDICATION
CCTrCH
PHYSICAL CHANNEL
SEGMENTATION
2nd INTERLEAVING
PHYSICAL CHANNEL MAPPING
PhCH#1
PhCH#2
68P02905W21-B 5-39
02-Jun-2004
Channel coding Chapter 5: Air Interface Physical Layer
Channel coding
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Code blocks are delivered to the channel coding block where one of the following channel
coding schemes can be applied to TrCHs:
• Convolutional coding
• Turbo coding
• No coding
Usage of coding scheme and coding rate for the different types of TrCH is shown in Table 5-5. Channel
coding adds redundant bits to the Code blocks, which will be used to detect and, within limits, correct
errors within the code blocks introduced during transfer across the Uu interface.
Table 5-5 Usage of channel coding scheme and coding rate
Type of TrCH Coding scheme Coding rate

BCH
PCH 1/2
RACH Convolution coding
CPCH, DCH, 1/3, 1/2
FACH Turbo coding 1/3
No coding
Convolution Coding
Convolutional codes with constraint length 9 and coding rates 1/2 and 1/3 are defined. A rate ½
coder will generate one redundant bit for every bit in the code block, thus doubling the input bit
rate at the output of the coder. Similarly rate 1/3 coding will treble the input bit rate. Simplified
diagrams of convolutional coders for each rate are illustrated opposite.
Output from the rate 1/3 convolutional coder shall be done in the order output0, output1, output2,
output0, output1, output 2, output 0,…,output2. Output from the rate 1/2 convolutional coder shall
be done in the order output 0, output 1, output 0, output 1, output 0, …, output 1.
8 tail bits with binary value 0 shall be added to the end of the code block before encoding.
The initial value of the shift register of the coder shall be all 0 when starting to encode the input bits.
5-40 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Channel coding
Turbo Coding
The scheme of Turbo coder is a Parallel Concatenated Convolutional Code (PCCC) with two
8-state constituent encoders and one Turbo code internal interleaver. The coding rate of Turbo
coder is 1/3. The structure of Turbo coder is illustrated opposite.
The initial value of the shift registers of the 8-state constituent encoders shall be all zeros when
starting to encode the input bits. Output from the Turbo coder is
x1, z1, z’1, x2, z2, z’2, …, xK, zK, z’K,
where x1, x2, …, xK are the bits input to the Turbo coder i.e. both first 8-state constituent encoder and
Turbo code internal interleaver, and K is the number of bits, and z1, z2, …, zK and z’1, z’2, …, z’K are
the bits output from first and second 8-state constituent encoders, respectively.
The bits output from Turbo code internal interleaver are denoted by x’1, x’2, …, x’K, and these
bits are to be input to the second 8-state constituent encoder.
68P02905W21-B 5-41
02-Jun-2004
Rate matching and insertion of DTX indication Chapter 5: Air Interface Physical Layer
Rate matching and insertion of DTX indication

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Rate matching
Rate matching is used to match the number of bits to be transmitted to the number of bits available
on a single radio frame (on either a single or multiple physical channels). This achieved either by
puncturing or repetition. Higher layers assign the rate-matching attribute for each transport channel.
This attribute is semi-static and can only be changed through higher level signalling.
For the downlink, rate matching to the bit rate of the closest available physical channel format will
be performed. If multiple services are to multiplexed onto the same physical channels(s), only the
repetition/puncturing pattern for the highest rate service is calculated. This same pattern will be applied to
the remaining, lower rate services. If the number of bits present for these services is still less than the
minimum, transmission is interrupted (that is; discontinuous transmission will be applied)
Insertion of DTX indication
In the downlink, DTX is used to fill up the radio frame with bits when there is no TrCH
information to be transmitted. DTX indication bits only indicate when the transmission
should be turned off, they are not transmitted.
The insertion point of DTX indication bits depends on whether fixed or flexible positions of the TrCHs in the
radio frame are used. It is up to the UTRAN to decide for each CCTrCH whether fixed or flexible positions
are used during the connection. The concept of fixed versus flexible positions is illustrated opposite.
The use of fixed positions means that for a given transport channel, the same symbols are within each
timeslot are always used. If the transmission rate for that channel is below maximum, then DTX indication
bits are used for those symbols. Since the different channels do not have a dynamic impact on each other,
DTX indication bits can be inserted at the first insertion point, before TrCH multiplexing.
With flexible positions the situation is different since now the channel bits unused by one service may be utilised
by another service. It will therefore not be clear until after TrCH multiplexing, which bit positions will finally
be unused, thus the 2nd insertion point, following Radio Frame Segmentation and TrCH Multiplexing is used.
Figure 5-24 illustrates Fixed and Flexible Bit Positions.
5-42 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Rate matching and insertion of DTX indication
Figure 5-24 Fixed and Flexible Bit positions
FIXED POSITION
TPC TFCI PILOT

TrCH A BITS TrCH B
BITS BITS
TPC TFCI PILOT

TrCH A DTX TrCH B
BITS BITS BITS
FLEXIBLE POSITION
TPC TFCI PILOT

TrCH A BITS TrCH B
BITS BITS
TPC TFCI PILOT

TrCH A TrCH A TrCH B BITS
BITS BITS
68P02905W21-B 5-43
02-Jun-2004
Transport channel multiplexing and Physical Layer segmentation Chapter 5: Air Interface Physical Layer
Transport channel multiplexing and Physical Layer

segmentation
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Every 10 ms, one radio frame segment from each TrCH is delivered to TrCH multiplexing. These
radio frame are serially multiplexed into a Coded Composite Transport Channel (CCTrCH). Figure 5-25
illustrates the process of TrCH multiplexing of a 12.2 kbit/s AMR speech channel (which uses
three separate TrCHs) and a 3.4 kbit/s Background data channel.
Figure 5-25 Transport Channel multiplexing
12.2 kbit/s data 12.2 kbit/s data 3.4 kbit/s data
# 1a # 2a # 1b # 2b # 1c # 2c # 1a # 1b # 2a # 2b # 3a # 3b #1 #2 # 3 #4
TrCH
MULTIPLEXING
#1a #1b #1c #1 #2a #2b #2c #2 #1a #1b #1c #3 #2a #2b #2c #4
RADIO FRAME 1 RADIO FRAME 2 RADIO FRAME 3 RADIO FRAME 4
2nd Insertion of DTX Indication segmentation
After TrCH multiplexing has been completed, insertion of DTX indication bits into unused bit positions can
now be performed, to indicate a requirement to turn off transmission. This insertion point is only used when
flexible positioning of TrCHs with the radio frame structure is used. The DTX function will insert the bits,
so that they are evenly distributed over all timeslots within the radio frame, after 2nd interleaving.
Physical Layer segmentation
When more than one PhCh is used, physical channel segmentation divides the bits contained
within the CCTrCH among the different PhCHs.
5-44 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Transport channel multiplexing and Physical Layer segmentation
2nd Interleaving
For each PhCN in use for the connection, a 2nd interleaving (or Intra-frame interleaving) process is
performed. As with first interleaving, a block interleaver, with inter-column permutations is used, with the
rectangular matrix having a fixed width of 30 columns. This process distributes the bits, non-contiguously
across the time slots of the radio frame, to minimise the effect of bursty errors.
The resultant bit sequence is mapped to the appropriate physical channel and passed
on to the chip level processing functions.
68P02905W21-B 5-45
02-Jun-2004
Downlink spreading and channel combination Chapter 5: Air Interface Physical Layer
Downlink spreading and channel combination

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 5-26 illustrates the spreading operation for all downlink physical channels except SCH, that is to
say, for P-CCPCH, S-CCPCH, CPICH, AICH, PICH, PDSCH, and downlink DPCH. The non-spread
physical channel consists of a sequence of real-valued symbols. For all channels except AICH, the
symbols can take the three values +1, -1, and 0, where 0 indicates DTX. For AICH, the symbol values
depend on the exact combination of acquisition indicators to be transmitted.
Each pair of two consecutive symbols is first serial-to-parallel converted and mapped to an I and Q
branch. The mapping is such that even and odd numbered symbols are mapped to the I and Q branch
respectively. For all channels except AICH, symbol number zero is defined as the first symbol in each
frame. For AICH, symbol number zero is defined as the first symbol in each access slot.
The I and Q branches are then spread to the chip rate by the same real-valued channelization code
Cch,SF,m. The sequences of real-valued chips on the I and Q branch are then treated as a single
complex-valued sequence of chips. This sequence of chips is scrambled (complex chip-wise
multiplication) by a complex-valued scrambling code Sdl,n.
In case of P-CCPCH, the scrambling code is applied aligned with the P-CCPCH frame boundary, (that
is; the first complex chip of the spread P-CCPCH frame is multiplied with chip number zero of the
scrambling code). In case of other downlink channels, the scrambling code is applied aligned with
the scrambling code applied to the P-CCPCH. In this case, the scrambling code is thus not necessarily
applied aligned with the frame boundary of the physical channel to be scrambled.
Figure 5-26 Spreading for all downlink physical channels except SCH
I
x Sdl,n
ANY DOWNLINK
PHYSICAL CHANNEL SERIAL I + jQ S
EXCEPT SCH TO C ch, SF + x
PARALLEL
x x
Q
5-46 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Downlink spreading and channel combination
Channel combining
Figure 5-27 illustrates how different downlink channels are combined. Each complex-valued spread
channel, (corresponding to point S in the upper diagram), is separately weighted by a weight factor
Gi. The complex-valued P-SCH and S-SCH, are separately weighted by weight factors Gp and Gs.
All downlink physical channels are then combined using complex addition.
Figure 5-27 Channel combining
DIFFERENT DOWNLINK
x
PHYSICAL CHANNELS
(POINT S IN FIGURE
ABOVE) G1
x
Σ
G2
P-SCH x
Σ
GP
S-SCH x
GS
68P02905W21-B 5-47
02-Jun-2004
Uplink flow process Chapter 5: Air Interface Physical Layer
Uplink flow process

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The uplink flow process is largely the same as that for the downlink, and is illustrated in Figure 5-28.
The differences in the individual process steps are as follows.
Radio frame equalisation
Radio frame size equalisation is padding the input bit sequence in order to ensure that the output can
be segmented in data segments of equal size. Radio frame size equalisation is only performed in the UL
(DL rate matching output block length is always an integer multiple of the frame length).
Rate matching
The rate matching operation in the uplink, is a much more dynamic process that may vary on a
frame-by-frame basis. The rate matching operation needs to take into account the the number of bits
coming from all transport channels. When tha data rate of one service, the dynamic rate matching adjusts
the rates of the remaining service as well so that all symbols in the radio frame will be used.
For example if with two transport channels, one has a momentary zero rate, rate matching used repetition to
increase the symbol rate for the other service sufficiently so that all uplink channel symbols are used.
DTX
Because Uplink rate matching ensures that all unused transport channel bits are filled, there is no
requirement for DTX indication bits to be inserted in the uplink flow.
5-48 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Uplink flow process
Figure 5-28 Uplink flow process
CRC ATTACHMENT
TrBk CONCATENTATION
CODE BLOCK SEGMENTATION
CHANNEL CODING
RADIO FRAME EQUALIZATION
1st INTERLEAVING
RADIO FRAME SEGMENTATION
RATE MATCHING RATE MATCHING
TrCH MULTIPLEXING
CCTrCH
PHYSICAL CHANNEL
SEGMENTATION
2nd INTERLEAVING
PHYSICAL CHANNEL MAPPING
PhCH#2
PhCH#1
68P02905W21-B 5-49
02-Jun-2004
Uplink spreading and channel combination Chapter 5: Air Interface Physical Layer
Uplink spreading and channel combination

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 5-29 illustrates the principle of the uplink spreading of DPCCH and DPDCHs. The binary
DPCCH and DPDCHs to be spread are represented by real-valued sequences, that is, the binary
value "0" is mapped to the real value +1, while the binary value "1" is mapped to the real value
–1. The DPCCH is spread to the chip rate by the channelization code cc, while the n:th DPDCH
called DPDCHn is spread to the chip rate by the channelization code cd,n. One DPCCH and up to six
parallel DPDCHs can be transmitted simultaneously, that is, 1 ≤ n ≤ 6.
After channelization, the real-valued spread signals are weighted by gain factors, βc for DPCCH and βd for all
DPDCHs. The weighting process is performed to equalise all power levels in the combination set.
After the weighting, the stream of real-valued chips on the I- and Q-branches are then summed
and treated as a complex-valued stream of chips. This complex-valued signal is then scrambled
by the complex-valued scrambling code Sdpch,n. The scrambling code is applied aligned with the
radio frames, that is, the first scrambling chip corresponds to the beginning of a radio frame.
The resultant complex coded signal is forwarded to the modulator.
PRACH Message Part
Figure 5-30 illustrates the principle of the spreading and scrambling of the PRACH message part,
consisting of data and control parts. The binary control and data parts to be spread are represented by
real-valued sequences, that is, the binary value "0" is mapped to the real value +1, while the binary value
"1" is mapped to the real value –1. The control part is spread to the chip rate by the channelization code
cc, while the data part is spread to the chip rate by the channelization code cd.
After channelization, the real-valued spread signals are weighted by gain factors, βc for the control part and
βd for the data part. At every instant in time, at least one of the values βc and βd has the amplitude.
After the weighting, the stream of real-valued chips on the I- and Q-branches are treated as a complex-valued
stream of chips. This complex-valued signal is then scrambled by the complex-valued scrambling code
Sr-msg,n. The 10 ms scrambling code is applied aligned with the 10 ms message part radio frames, that
is, the first scrambling chip corresponds to the beginning of a message part radio frame.
5-50 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Uplink spreading and channel combination
Figure 5-29 DPCCH/DPDCH spreading and combination
Cd,n Bd
DPDCH1
Cd,n Bd
DPDCH3
Cd,n Bd
DPDCH5
SCdpch,n
Cd,n Bd I+jQ
DPDCH2
Cd,n Bd
DPDCH4 +j
Cd,n Bd
DPDCH6
CC Bd
DPCCH1
Figure 5-30 PRACH spreading and combination
Cd Bd
PRACH message
data part Sr-msg,n
I+jQ
S
PRACH message
control part
Cc Bc j
CP13_Ch7_06a
68P02905W21-B 5-51
02-Jun-2004
Uplink spreading and channel combination Chapter 5: Air Interface Physical Layer
5-52 68P02905W21-B
02-Jun-2004
Chapter
6
W-CDMA theory
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 6-1
02-Jun-2004
Introduction to this chapter Chapter 6: W-CDMA theory

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter provides an introduction to W-CDMA theory.

• "Introduction to Wideband Code Division Multiple Access (W-CDMA)" on page 6-3.
• "Multiple access schemes" on page 6-4.
• "W-CDMA characteristics" on page 6-6.
• "Spreading and despreading" on page 6-10.
• "Orthogonal Codes" on page 6-11.
• "Channelisation Code Tree" on page 6-12
• "Scrambling and summation" on page 6-16.
• "Multi-path radio channels" on page 6-20.
• "RAKE receiver " on page 6-23.
6-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Introduction to Wideband Code Division Multiple Access (W-CDMA)
Introduction to Wideband Code Division Multiple

Access (W-CDMA)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to W-CDMA
UMTS employs Wideband Code Division Multiple Access (W-CDMA) as the means
of allocating radio spectrum.
W-CDMA is a form of spread spectrum technique. It has many advantages over other multiple access
techniques such as Frequency Division Multiple Access (FDMA) and Time Division Multiple Access
(TDMA), including greater spectral efficieny and greater immunity to interference and noise.
Cocktail party analogy
The concept of W-CDMA can be explained by the cocktail party analogy.

Groups of people in a room, speaking different languages, can communicate simultaneously despite
the surrounding noise. The language each group are using allows them to talk to each other, whilst
filtering out the noise of the other conversations in different languages.
However if the noise is recorded, someone who knows the various languages, could playback
the tape several times, and extract the different conversations. If there are several listeners to
the tape, all the conversations could be extracted simultaneously.
W-CDMA techniques
Unlike FDMA and TDMA, the carrier is not split into frequency bands or shared on a time basis. Instead
the signal is spread over a wider spectrum and allocated an individual code.
The user data signal to be transmitted is multiplied by a pre-defined bit pattern called a spreading
code. The symbols of the spreading code are referred to as chips, and following the spreading
operation, the user data signal is represented by a number of chips. The chip rate for UMTS
is 3.84 Mchip/s, which enables a bandwidth of 5 MHz.
As the user data signal is spread over the bandwidth, the amplitude is reduced to that of noise level.
The degree to which the original data signal is widened to fill the available spectrum is called the
spreading factor; the higher the data rate, the lower the spreading factor.
Multiple access users have different spreading codes but occupy the same frequency band. The
W-CDMA receiver removes the spreading code to extract the original signal.
In UMTS, the uplink and downlink paths are separated by Frequency Division Duplex (FDD). Paired
frequencies are used for the uplink and downlink spaced at 190 MHz.
68P02905W21-B 6-3
02-Jun-2004
Multiple access schemes Chapter 6: W-CDMA theory
Multiple access schemes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
There are three forms of multiple access schemes, frequency, time and code. These are shown in Figure 6-1.
Figure 6-1 Multiple access schemes
Power Time
FDMA
Power Frequency
Time
TDMA
Frequency
Codes Time
CDMA
Frequency
CP13_Ch6_01
6-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Multiple access schemes
Frequency Division Multiple Access (FDMA)
FDMA divides radio channels into a range of radio frequencies and is used in the traditional analogue
system. With FDMA, only one subscriber is assigned to a channel at one time. Other subscribers cannot
access this channel until the original call is terminated or handed off to a different channel.
Time Division Multiple Access (TDMA)
TDMA is a common multiple access technique employed in digital cellular systems. It divides
radio channels into time slots to obtain higher capacity. As with FDMA, no other conversations
can access an occupied channel until that channel is vacated.
Code Division Multiple Access (CDMA)
CDMA assigns each subscriber a unique code to put multiple users on the same channel
at the same time. CDMA users can share the same frequency channel because their
conversations are distinguished only by digital code.
68P02905W21-B 6-5
02-Jun-2004
W-CDMA characteristics Chapter 6: W-CDMA theory
W-CDMA characteristics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The characteristics of W-CDMA UMTS system are listed in Table 6-1.
This is not a TDMA system. Every user shares the same band. The frames and
slots are used for interleaving, power control.
Table 6-1 W-CDMA characteristics
Multiple access scheme: CDMA

Duplexing method: FDD
Chip rate: 3.84 Mchip/s
Bandwidth: 5 MHz
Carrier spacing: 200 kHz raster
Frame length: 10 ms
Slots per frame: 15
Intercell synchronisation: None
Spreading factor: Variable (4 - 512)
User data rate: 3 - 384 Kbit/s
Major features of W-CDMA
The major points are:

• FDD requires paired frequencies for up and down channels.
• The chip rate of 3.84 Mchip/s provides a bandwidth of 5 MHz. A chip

is a pseudo random code bit.
• The carrier spacing of 200 kHz is used to allow re-farming of GSM frequencies
which have been set at 200 kHz spacing.
• The frame length is set at 10 ms. Each frame is split into 15 timeslots each timeslot
contains user data, power control and signaling data.
6-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview W-CDMA characteristics
• The UMTS system does not require synchronisation due to the framing structure
and use of matched filters for the framing alignment.
• The spreading factor is the ratio between the user data and the chip rate. As the
user data increases this factor will vary between 4 and 512. The spreading factor is
a rough indication of the number of users in the system.
• The user data rates available in the FDD system is up to 384 Kbhip/s.
Re-use of frequency
Mobile telephones and cell broadcast networks use cellular radio; a technique developed in recent
years to enable the use of mobile telephones. It would be impossible to provide each phone with
an individual radio frequency, so the idea of cellular radio evolved.
A region is divided into geographical areas called cells, varying in size depending on the number of
users in the area. In cities cells are small whereas in rural areas cells are much larger.
GSM cells use a set of frequencies that are different from any neighbouring cell, but can be
the same as another cell as long as it is far enough away.
For UMTS, a frequency re-use of one, may be employed. This means that all cells within a given
geographical area, or even an entire network may use the same carrier frequency.
An alternate method of discriminating between neighbouring cells must therefore be found.
Re-use of codes
Codes are used to uniquely identify a cell in the network. Frequency planning is more or less redundant in
UMTS but instead code planning has to be implemented. Code planning is much easier than frequency
planning because there are 512 codes for use, so the code re-use pattern is extremely large.
Codes can be reused when the separation between cells containing the same channel set is far enough
apart so that co-channel interference can be kept below acceptable levels. The number of cells in a
cluster is 512, which provides greater separation between co-channel cells than GSM.
Spectral efficiency (GSM and UMTS)
Figure 6-2 shows how spectrally efficient UMTS and GSM are in comparison to each
other when employed in a multi-cellular structure.
The capacity, which Shannon derived in 1947, provided a Law (called Shannons Law). This details
the digital capacity of the link given the transmit power and the bandwidth.
When using, FDMA, TDMA or CDMA, the capacity is still controlled by this law. However,
some gains are made by technology and coding methods.
68P02905W21-B 6-7
02-Jun-2004
W-CDMA characteristics Chapter 6: W-CDMA theory
Figure 6-2 Spectral efficiency
GSM UMTS - SF256
8 Calls = 200 kHz Carrier 256 Calls = 5 MHz Carrier

1 Call = 25 kHz 1 Call = 19.4 kHz
7 x 200 kHz = 1.4 MHz 7 Cells, 5 MHz

1 Call = 25 kHz 1 Call = 19.4 kHz
CP13_Ch6_06
Direct Spread (DS)-CDMA implementation
Transmitter
The digital modulator will take digital speech/data and multiply it with the spreading code.
The radio modulator moves the baseline signal from the digital modulator onto a 2 GHz
carrier to produce the W-CDMA output.
Receiver
The modulated carrier is moved by the radio demodulator to the digital demodulator which can
be very complicated due to the large number of users. See Figure 6-3
Here the input is multiplied by the de-spreading codes to produce digital speech.
6-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview W-CDMA characteristics
Figure 6-3 Direct Spread CDMA implementation
Single User Channel Multiple User Channel Multiple User Channel Output
5 MHz 5 MHz 5 MHz 0

W-CDMA
Digital Digital Modulated Carrier Digital
Radio
Signal Modulator Modulator C S Radio Digital
o p Demodulator Demodulator Signal
m l
b i
Tx Spreading
Code
Radio
Carrier
i t Radio
t Carrier
Spreading
Code Rx
Generator n Generator
e e
r r
Digital Digital Radio Radio Digital Digital
Signal Demodulator Demodulator Signal
Modulator Modulator
Input External Interference
0 t0
CP13_Ch6_26
68P02905W21-B 6-9
02-Jun-2004
Spreading and despreading Chapter 6: W-CDMA theory
Spreading and despreading

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Spreading operation
The spreading operation is the multiplication of each user data bit with a “Spreading Code" , which is a
pre-defined bit pattern. To discriminate between User data “bits" and spreading code “bits", the symbols in
the spreading code are referred to as “Chips". The chip rate for UMTS is fixed at 3.84 Mchips. After the
spreading operation each “Bit" of the data signal is represented by a number of “chips". See Figure 6-4.
The number of chips representing each bit is referred to as the “Spreading Factor" (SF) and is given
by dividing the chip rate by the source signal bit rate; in this example:
3.84 Mcs / 480 kBs = (SF=8)
The spreading operation has resulted in an increase of the “signalling rate of the user data, in this case
by a factor of 8, and corresponds to a widening of the “spectrum" occupied by the user data signal. Due
to this, CDMA systems are more generically referred to as “Spread Spectrum" systems.
The SF is also referred to as the Processing Gain (PG), which is expressed as a Decibel ratio and describes
the gain or amplitude increase that will be applied to the signal at the receiving station as a result of
the despreading operation. This concept is described in more detail later in this chapter.
Figure 6-4 Spreading
Data 1
480 kB/s -1
Spreading
Code 1
3.84 Mcs -1
Spread 1
Data -1
6-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Spreading and despreading
De-spreading
De-spreading is performed at the receiving station (UE or Node B) by multiplying the chip rate,
spread user data signal by a chip rate spreading code. By using the same spreading code as
used at the transmitting station for the spreading operation, the multiplication of the two chip
rate signals will reproduce the original bit rate user data signal.
To aid accurate recovery of the user data, a Correlation Receiver is employed in most CDMA
systems. The correlation receiver integrates the product of the de-spreading process on a chip-by-chip
basis. In the upper diagram opposite, the example shown illustrated that for a perfectly received
de-spread signal, the correlation receiver output has effectively “Lifted" the amplitude of the
received signal by a factor of 8, a function of the processing gain.
De-spreading is shown in Figure 6-5.
Figure 6-5 De-spreading (desired signal)
Spread 1
Data -1
Spreading 1
Code -1
Correlation
RX
Integrator
O/P
Recovered 1
Data -1
CP13_Ch6_26b
Orthogonal Codes
Transmissons from a single source are separated by channelisation codes. The channelisation codes of UTRA
are based upon the Orthogonal Variable Spreading Factor (OVSF) technique (see Figure 6-6).
There are a finite number of OVSF codes available, and some restrictions in their use.
OVSF codes are, as their name implies, orthogonal codes. Orthogonal codes possess good cross
correlation properties allowing easy discrimination between signals produced using correctly
selected codes. For OVSF the cross correlation between codes is zero, meaning interferer signals
between different codes is effectively zero after correlation.
68P02905W21-B 6-11
02-Jun-2004
Figure 6-6 Orthogonal codes
1 1 1 1
1 1
-1 -1
1 1
-1 -1
1 1
-1 -1
CP13_Ch6_18
Channelisation Code Tree
For separating channels from the same source, channelisation codes called Orthogonal
Variable Spreading Factors are used.
The lines in Figure 6-7 represent codes, these are Orthogonal Variable Spreading Factor (OVSF) codes,
allowing to mix in the same timeslot channels with different spreading factors while preserving the
orthogonality. The OVSF codes can be defined using the code tree shown in Figure 6-7.
Each level in the code tree defines a Spreading Factor (SF) indicated in Figure 6-7. All codes within
the code tree cannot be used simultaneously in a given timeslot. A code can be used in a timeslot if
and only if no other code on the path from the specific code to the root of the tree or in the sub-tree
below the specific code is used in this timeslot. This means that the number of available codes in a
slot is not fixed but depends on the rate and spreading factor of each physical channel.
The spreading codes can be used to identify individual channels, but a mobile usually has to identify the
base station that it is currently parented on. A long code (PN) is usually used for that.
6-12 68P02905W21-B
02-Jun-2004
Figure 6-7 Channelisation code tree
Cch, 8, 0
Cch, 4, 0 (1, 1, 1, 1, 1, 1, 1, 1)
(1, 1, 1, 1) Cch, 8, 1
Cch, 2, 0 (1, 1, 1, 1, -1, -1, -1, -1)
(1, 1) Cch, 8, 2
Cch, 4, 1 (1, 1, -1, -1, 1, 1, -1, -1)
(1, 1, -1, -1) Cch, 8, 3
Cch, 1, 0
(1, 1, -1, -1,- 1, -1, 1, 1)
(1) Cch, 8, 4
Cch, 4, 2 (1, -1, 1,- 1, 1, -1, 1, -1)
Cch, 8, 5
(1, -1, 1, -1)
Cch, 2, 1 (1, -1, 1, -1, -1, 1, -1, 1)
(1, -1) Cch, 8, 6
Cch, 4, 3 (1, -1, -1, 1, 1, -1, -1, 1)
(1, -1, -1, 1) Cch, 8, 7
(1, -1, -1, 1, -1, 1, 1, -1)
SF = 1 SF = 2 SF = 4 SF = 8
CP13_Ch6_13
De-spreading other users signals
In a CDMA system, all users are potentially transmitting on the same frequency. This means that at
any given receiver station, in addition to the desired signal, multiple Interferer signals will also be
received. It is the task of the correlation receiver to reject these interferer signals.
Figure 6-8 shows the effect of dispreading and correlation at a given receiving station (UE A),
on an interferer signal, (for example, a signal transmitted on the same carrier for reception by
UE B). The de-spreading/correlation of the interferer signal will result in a crosscorrelation of
zero (that is, the output of the integration process will be zero). This process is only true when
correctly selected Orthogonal Spreading Codes are employed.
68P02905W21-B 6-13
02-Jun-2004
Figure 6-8 De-spreading (Interferer Signals)
Spread 1
-1
Code -1
Spreading 1
Data -1
Recovered 1
Correlation
Integrator
CP13_Ch6_26b
O/P
RX
Data
6-14 68P02905W21-B
02-Jun-2004
Processing Gain
Processing Gain can be defined as the Chip Rate divided by the bit rate. This gives a ratio that
can be converted to decibels by using the following formula:
PG = 10 x log SF
The gain resulting from the Processing Gain is an extremely important part of CDMA. It is because of
this relationship that CDMA is so effective and is used even in space transmissions. Processing gain will
determine how much the received signal can be lifted out of the noise floor. There is one simple rule to follow,
the higher the SF the higher the processing gain will be, the lower the SF the lower the processing gain.
The SF is also inversely proportional to the speed of the transmission. This means that the higher the speed
of transmission the lower the processing gain will be. Due to this relationship the power output of any
transmitter must be increased if the transmission rate is increased due to the loss in Processing Gain.
This will also mean that if the Frame Error Rate (FER) is increased on the receiver side the power must be
increased or the transmission rate must drop on the transmitter side to meet the FER requirement.
68P02905W21-B 6-15
02-Jun-2004
Scrambling and summation Chapter 6: W-CDMA theory
Scrambling and summation

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
OVSF spreading codes can be used to separate individual users on a common RFcarrier freq. However,
because of the need to maintain orthogonality of codes, the number of codes available is very limited
(512 Downlink, 256 Uplink). These 512 code must be reused in every cell, as such they do not
become unique to a cell and users located at the boundaries of cells, would receive transmissions
using the same OVSF code, from more than one cell. For UMTS therefore, OVSF codes are used
only as Channelisation Codes, used identify individual Physical Channels. A further coding, process,
known as a Scrambling is performed, in order to discriminate between the transmissions between
different cells on the downlink and different UEs on the uplink. See Figure 6-9.
Each physical channel is first individually spread to chip rate using a channelisation code (Cch sf,k) taken
from the OVSF code tree, resulting in an increase in bandwidth of the signal form Bit Rate to Chip Rate.
The sequence of chips produced by the channelisation process is then Scrambled, using a
chip-to-chip multiplication with a complex-valued scrambling code (Csc). The code chosen
is used to identify the source of the signal. As scrambling is performed on top of spreading,
it has no further effect on the bandwidth of the signal.
Although the primary purpose of using a scrambling code is to identify all channels from a single source,
that single source may use more than scrambling code. For example, in the downlink, a cell may transmit
using one of 16 possible scrambling codes. After scrambling, all physical channels are then combined,
using complex addition, before being forwarded to the RF Modulator for transmission.
Figure 6-9 Scrambling
Channel x
Data
Cch SF,x Csc,x
Channel y
Data
Cch SF,x Csc, x
Σ
Channel z
Data
Cch SF,x Csc,x
CP13_Ch6_35
6-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Scrambling and summation
Scrambling Codes vs Channelisaton Codes
Table 6-2 shows the major differences between Scrambling Codes (SC) and Channelisation Codes (CC).
Table 6-2 Scrambling codes vs Channelisation codes
CC SC
Usage uplink Separation of Data Control Separation of UEs

Channels (from the same UE)
Usage downlink Separation of channels to different Separation of Cells
UEs
Length uplink 4 - 256 Chips LC - 10ms=38400 Chips
or
SC = 66.7us = 256 Chips
length downlink 4 - 512 Chips LC = 38400 Chips
Number of codes available 512 Uplink and Downlink Uplink = 224 - 1 =
16,777,215Downlink = 218 -
1 = 262, 143(truncated to 8,192)
Code family OVSF LC = 10ms = Gold CodeSC =
Extended S2 family
Spreading Increases Tx Bandwidth No effect on bandwidth
Short codes vs long codes
Short codes and long codes are both used in the UMTS system. The main advantage of short codes is that
they have good Auto Correlation properties. This means that they are easy to synchronise to.
The main advantage of long codes is that they have excellent cross correlation properties. This means
that they are very resistant to interference from other codes in the network.
Table 6-3 compares the properties of short and long codes.
Table 6-3 Short codes vs long codes
Feature Short Codes Long codes

Code sequence length <timeslot >>timeslot
Code sequence repeated within every timeslot for each Radio Frame
Auto correlation properties Good Bad (long repetition cycle)
Cross correlation properties Bad Good
Planning Difficult Easy
68P02905W21-B 6-17
02-Jun-2004
Scrambling and summation Chapter 6: W-CDMA theory
Scrambling and Summation
Figure 6-10 illustrates the process of scrambling and summation of multiple channels, prior to modulation
onto the RF carrier and transmission over the UMTS air interface (Uu).
For the purposes of this example, three separate data streams (Channels X, Y and Z), each
carrying a user bit sequence of “0,1,1,0", have been spread using channelisation codes
of Cch 8,1 , Cch 8,2 and Cch 8,3 respectively.
The spread signals are then independently scrambled using a single scrambling code. The resultant
chip sequences are then combined using complex addition, to produce the multi level digital
baseband signal, that will be used to modulate the RF carrier.
Figure 6-10 Scrambling and Summation
Spread Data 1
Channel X Cch 8,1 -1
Spread Data 1
Channel Y Cch 8,2 -1
Spread Data 1
Channel Z Cch 8,3 -1
Scrambling 1
code -1
Channel X after 1
scrambling -1
Channel Y after 1
scrambling -1
Channel Z after 1
scrambling -1
+3
Complex added +2
scrambled codes +1
-1
-2
-3
CP13_Ch6_36
De-Scrambling and Data Recovery
Figure 6-11 illustrates the processes of de-scrambling of a complex scrambled signal and
the recovery of user data from one channel.
The input signal (derived from the example on the preceding page) is first de-scrambled by
multiplication with the specified scrambling code. The result is a combined version of all
received channels, represented by a complex chip sequence.
6-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Scrambling and summation
The dispreading process must now be performed to recover the user data. The example illustrates the recovery
of the data for Channel “X" from the preceding page. By performing a direct multiplication of the complex
signal with the appropriate channelisation code, the illustrated correlation receiver output will be obtained. As
can be seen, the integrated output indicates “Bit Values" of “0,1,1,0", the expected result for this example.
Figure 6-11 De-Scrambling and Data Recovery
+3
+2
Received +1
Scrambled -1
-2
-3
Scrambling 1
Code -1
+3
+2
De-scrambled +1
Signal -1
-2
-3
Chan Code for
Chan X (Cch8,2)
Correlation
Output
CP13_Ch6_37
68P02905W21-B 6-19
02-Jun-2004
Multi-path radio channels Chapter 6: W-CDMA theory
Multi-path radio channels

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Radio propagation for mobile communications suffers greatly from the effects of mulipath
reflections, diffractions and attenuation of the signal energy (as illustrated in Figure 6-12).
These effects are causes by objects such as buildings, hills, and so on, resulting in Multipath
Propagation, which has two main effects upon the signal.
Inter-symbol interference
Inter-symbol interference occurs when the signal energy from more than one radio path, pertaining to a single
symbol (or chip in the case of W-CDMA), such that the energy from the various paths overlaps. This results
in the smearing of the signal, such that is hard to define where one chip starts and one chip ends and the
true value of the chips may be distorted. This problem can be resolved, providing the delay between the two
paths is greater than one chip period (0.26 uS at 3.84 Mchips. This equates to a path length difference of 78
m). Delays of 1 or 2 micro seconds are typical in urban areas, with 20 uS possible in hilly areas.
Signal fade
In multi-path situations where path lengths are multiples of half a wavelength of the received frequency
(7 cm at 2 GHz), the signals on two (or more) paths will arrive in anti-phase to each other. This results
in cancellation of the signals, causing fast or Rayleigh fading. Such fading can result in signal level
drops in the order of 20 to 30 dB, making the reception of error free data bits very difficult.
6-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Multi-path radio channels
Figure 6-12 Multi-path radio channels
CP13_6_38
Matched Filter Operation
The main task of the matched filter is to determine the timing reference of the information
as it arrives at the receiver, as shown in Figure 6-13.
The filter will perform a chip-by-chip comparison of the received signal against a known Pilot
reference, to identify multiple copies of the same chip pattern.
After several iterations of the multiple paths have been accumulated, the time dispersion between the
two paths can be calculated and tracked, allowing the paths to be separated.
68P02905W21-B 6-21
02-Jun-2004
Multi-path radio channels Chapter 6: W-CDMA theory
Figure 6-13 Matched filter operation
RF Matched
Front End Slot Wise
Circuitry Filter Accumulation
CP13_Ch6_27
6-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RAKE receiver
RAKE receiver
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The RAKE receiver performs a similar (but not identical) function to the equaliser in GSM. Instead of training
bits, the pilot signals (all zeros) are used as a basis for the search for the best path. The rake receiver then
constructs its fingers to track the other multi-path rays by stepping through delays one chip at a time until it finds
another, lower level pilot. It can then use the weightings to bring the rays into phase and constructive addition.
That the different rays are uncorrelated if the delay difference is greater than one chip.
The effect of the propagation environment on spread spectrum modulated signals is to produce
a series of signal components that have traversed differing paths. This is known as multipath
interference and, depending on whether or not there is a significant specula multipath component,
the envelope of the multipath signal may be Rician or Rayleigh distributed.
Multipath results in two signal perturbations, known as Inter-Symbol Interference (ISI) and fading.
Both introduce severe degradation in the system performance. ISI creates signal components that are
delayed into the next signal period, making these signals overlap and therefore interfere with one
another. Fading is caused by signals of opposite phase cancelling in the receiver. To combat this,
a RAKE receiver may be used. This is the type of receiver shown in Figure 6-14and contains many
signal paths, each with an individual delay. These delays are changed so as the total delay from the
transmitter for all paths is the same and thus when combined they are in-phase.
Figure 6-14 RAKE receiver
∆0
Cch sf,k
τ1
∆1
Cch sf,k
τ2 ∆2
Cch sf,k
∆3
τ3
Cch sf,k
CP13_Ch6_28
68P02905W21-B 6-23
02-Jun-2004
RAKE receiver Chapter 6: W-CDMA theory
6-24 68P02905W21-B
02-Jun-2004
Chapter
7
Transmission systems
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 7-1
02-Jun-2004
Chapter overview Chapter 7: Transmission systems
Chapter overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter details the interfaces and protocols that allow UMTS network entities to
communicate with each other and with external systems.
Topics covered in this chapter are:

• "Iub interface" on page 7-6.
• "Iur interface" on page 7-27.
• "Iu-CS and Iu-PS interfaces" on page 7-58.
• "Iu-CS and Iu-PS interface protocol structure" on page 7-60.
• "Uu interface" on page 7-66.
7-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of UMTS interfaces
Overview of UMTS interfaces

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This section includes a:

• Diagram of UMTS interfaces.
• Overview of UMTS interfaces.
Diagram of UMTS interfaces
Figure 7-1 shows the interfaces between UMTS network entities and between ex-
ternal entities in outside networks.
68P02905W21-B 7-3
02-Jun-2004
Overview of UMTS interfaces Chapter 7: Transmission systems
Figure 7-1 UMTS interfaces
CORE NETWORK
BS-SERVICE CS-SERVICE PS-SERVICE

Gi
MSCu
GSNu
GGSNu
Ga
OMC-S/T
Gn CGWu
OML
Ga
Iu-BS Iu-CS SGSNu
Gr
HLR Iu-PS
Billing
System
OMC-U
Iu-O&M
ATM
Iu Iu
Iu REFERENCE POINT
UTRAN
RNS RNS
RNC Iur RNC
Iub Iub Iub Iub
NODE B NODE B NODE B NODE B
Uu
MOBILE USER EQUIPMENT

(UE)
7-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of UMTS interfaces
Outline of UMTS interfaces
Iub interface
A single Iub interface provides a service for the exchange of information between
each Node B and its controlling RNC.
Iur interface
The Iur interface provides the service to enable an RNC to address any other RNC within the UTRAN.
Iu interfaces
The Iu interfaces provide the service of exchange of information between the RNC and the
core network (CN). The Iu interfaces as follows:
• Iu-CS provides the interface between the RNC and the MSCu, for the circuit-switched domain.
• Iu-PS provides the interface between the RNC and the SGSNu, for the packet-switched domain.
• Iu-O&M provides the interface between the RNC and the Operations and
Maintenance Centre - UMTS (OMC-U), for the RAN.
Uu interface
The Uu interface is the radio interface between the UTRAN (RNC/Node B) and the UE.
68P02905W21-B 7-5
02-Jun-2004
Iub interface Chapter 7: Transmission systems
Iub interface
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iub interface
The Iub interface is the network interface that provides the service of information exchange
between the Node B and RNC network elements.
Each Node B has a single Iub interface to its controlling RNC.
The information exchange is for the purpose of passing signalling and data information between
the NEs and supporting logical O&M procedures as follows:
• Radio application signalling.
• Iub DCH data stream.
• Iub RACH data stream.
Iub radio application signalling
The Iub interface provides signalling to support the applications as follows:

• Resource allocation for supporting dedicated channels.
• Resource allocation for common channels.
• Control of broadcast channels.
• Data to be transported on the broadcast channels.
7-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub interface
Iub DCH data stream
The Iub interface supports data transmission as follows:

• Dedicated Channel (DCH) data.
• Random Access Channel (RACH) data.
• Forward Access Channel (FACH) data.
• Paging Channel (PCH) data.
Iub interface logical O&M procedures
The Iub interface supports procedures to enable O&M functions as follows:

• Cell configuration.
• Common transport channel configuration.
• Change of cell availability.
• Change of carrier availability.
• Change of traffic handling capability.
• Configuration and collection of measurement report information.
68P02905W21-B 7-7
02-Jun-2004
Iub interface protocol structure Chapter 7: Transmission systems
Iub interface protocol structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Iub interface network layers
Figure 7-2 shows the Iub interface protocol structure.
Figure 7-2 Iub interface protocol structure
RADIO NETWORK RADIO NETWORK

CONTROL PLANE USER PLANE
DCH CCH
RADIO
NETWORK NODE B DCH FP
LAYER APPLICATION RACH FP
PROTOCOL PCH FP
(NBAP) FACH FP
DSCH FP
TRANSPORT
NETWORK
CONTROL PLANE
ALCAP
TRANSPORT
SIGNALLING
DCH/CCH
TRANSPORT
NETWORK
LAYER SIGNALLING
BEARER AAL TYPE 2
SIGNALLING
BEARER
DCH/CCH
ATM
PHYSICAL LAYER
7-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub interface protocol structure
Figure 7-2 shows two main functional (horizontal) layers as follows:

• "Iub interface Transport Network Layer (TNL)" on page 7-10.
• "Iub interface Radio Network Layer (RNL)" on page 7-12.
In addition to the two main functional layers, protocols are shown in vertical planes as follows:
• Transport network control plane.
• Radio network control plane.
• Radio network user plane.
These functional layers and vertical planes are described in the following sections.
68P02905W21-B 7-9
02-Jun-2004
Iub interface Transport Network Layer (TNL) Chapter 7: Transmission systems
Iub interface Transport Network Layer (TNL)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iub TNL
The Iub interface TNL is the lowest end-to-end layer and is responsible for establishing
physical connections between the RNC and Node B.
The transport layer is sub-divided into three planes, as follows:
The Iub TNL is sub-divided into three planes; radio network control plane, radio network
user plane and transport network user plane.
Iub TNL radio network control plane
The Iub TNL radio network control plane is responsible for carrying messages related to Node B
Application Protocol (NBAP) common and dedicated signalling procedures, as follows:
• NBAP common procedures (for example; common channel management, radio
resource management, system information update). These are procedures not
related to a specific UE. They also include the procedures that request initiation
of a UE context in Node B for a specific UE.
• NBAP dedicated procedures (for example; radio link addition, radio link deletion, downlink
power control). These are procedures related to a specific UE context in Node B.
The TNL radio network control plane ensures the reliable transfer of control plane signalling messages,
that is, the radio network layer messages between the RNC and the Node B.
7-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub interface Transport Network Layer (TNL)
Iub TNL radio network user plane
The Iub TNL radio network user plane manages the data transfer to and from the application programmes.
AAL2 is used for all types of data, both CS and PS on Iub interface user plane.
One DCH transport channel is mapped on one and only one AAL2 channel. It is
possible for several co-ordinated DCHs on the same AAL2 connection, but an AAL2
connection can be used for one and only one user.
AAL2 channel mapping is as follows:
• A single RACH transport channel is mapped on one and only one AAL2 channel.
• A single FACH transport channel is mapped on one and only one AAL2 channel.
• One PCH transport channel is mapped on one and only one AAL2 channel.
For common transport channels, AAL2 channels are used in one direction only, although they are bi-directional.
A separate AAL2 connection is made for RACH and FACH.
A Virtual Circuit Connection (VCC) is not dedicated to one transport channel. A VCC may carry
a number of AAL2 channels corresponding to several types of transport channels
The maximum number of AAL2 VCCs available for the user plane is limited by Node B capacity.
The number of AAL2 channels multiplexed in one VCC is not infinite and several ATM VCCs
may be required as each VCC is limited to 248 AAL2 channels.
Iub TNL transport network control plane
The Iub TNL transport network control plane facilitates the setting up of the data bearers for the user plane
through the use of ALCAP (Access Link Control Application Protocol) protocol. It is also responsible for
transporting the ALCAP messages associated with the setting up of these bearers between RNC and Node B.
68P02905W21-B 7-11
02-Jun-2004
Iub interface Radio Network Layer (RNL) Chapter 7: Transmission systems
Iub interface Radio Network Layer (RNL)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iub RNL
The Iub interface RNL is the highest layer and is responsible for all procedures involving
interactions between the RNC and Node B.
The Iub RNL is sub-divided into two planes; radio network control plane and radio network user plane.
Iub RNL radio network control plane
The Iub RNL supports the Node B Application Protocol (NBAP) for the support of common and
dedicated signalling procedures between the RNC and the Node B, as follows:
• NBAP common procedures are procedures that are not related to a specific UE or
procedures that request initiation of a UE context for a specific UE. Examples of common
procedures that are not related to a specific UE are common channel management, cell
configuration management and system information update. Example of a common
procedure that requests initiation of a UE context is Radio Link Setup.
• NBAP dedicated procedures are procedures related to specific UE context in Node B.

Examples of dedicated procedures are radio link addition and radio link deletion.
Iub RNL radio network user plane
The SRNC provides the Node B with the complete configuration of the transport channels
to be provided by the Node B for a given communication. These transport channels are
multiplexed on the downlink by the Node B on radio physical channels, and de-multiplexed
on the uplink from radio physical channels to transport channels.
The user plane protocols support channel specific protocols related to the data streams
between the UTRAN and the UE.
The following Frame Protocols (FP) exist in the user plane:
• Dedicated Channel Frame Protocol (DCH FP).
• Random Access Frame Protocol (RACH FP).
• Forward Access Frame Protocol (FACH FP).
• Paging Channel Frame Protocol (PCH FP).
7-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub control and user plane protocol stacks
Iub control and user plane protocol stacks

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iub control plane protocol stacks
This section provides digrams of the following protocol stacks:

• Iub radio network control plane protocol stack.
• Iub transport network control plane protocol stack.
• Iub user plane protocol stack.
Iub radio network control plane protocol stack
Figure 7-3 shows the generic protocol stack over the Iub interface for the radio network
control plane in both transport and radio network layers.
Figure 7-3 Iub radio network control plane protocol stack
Node B RNC
NBAP NBAP
SAAL-UNI SAAL-UNI
ATM ATM
Iub
Iub transport network control plane protocol stack
Figure 7-4 shows the generic protocol stack over the Iub interface for the transport network
control plane in both transport and radio network layers.
68P02905W21-B 7-13
02-Jun-2004
Iub control and user plane protocol stacks Chapter 7: Transmission systems
Figure 7-4 Iub transport network control plane protocol stack
Node B RNC
Q.AAL2 Q.AAL2
SAAL-UNI SAAL-UNI
ATM ATM
Iub
Iub user plane protocol stack
Figure 7-5 shows the generic protocol stack over the Iub interface that applies to all (FP) in
the user plane for both transport and radio network layers.
Figure 7-5 Iub user plane protocol stack
Node B RNC
Frame Protocol Frame Protocol
AAL2 AAL2
ATM ATM
Iub
7-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub interface procedures
Iub interface procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iub procedures
Iub interface procedures enable data and control message signals to be transmitted over the Iub interface.
Categories of Iub procedures
Iub procedures can be categorised as user plane procedures and NBAP (control plane) procedures, as follows:
• "Iub user plane procedures for common transport channel data streams" on page 7-16.
• "Iub user plane procedures for dedicated transport channel data streams" on page 7-17.
• "NBAP common procedures" on page 7-19.
• "NBAP dedicated procedures" on page 7-24.
• "Error handling procedure" on page 7-26.
68P02905W21-B 7-15
02-Jun-2004
Iub user plane procedures for common transport channel data streams Chapter 7: Transmission systems
Iub user plane procedures for common transport

channel data streams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iub user plane procedures for common transport

The following Iub user plane procedures are defined for common transport channel data streams.
Iub common transport channel data transfer
The Iub common channel data transfer procedure is used to transfer RACH, FACH,
PCH or DSCH data across the Iub interface.
Iub common transport channel node synchronisation
The Iub common channel node synchronisation procedure provides a method for the CRNC to
estimate the frame timing difference between the CRNC and the Node B.
The RNC and the Node B support the node synchronisation procedure on RACH, FACH,
PCH and DSCH common transport channels.
Iub common channel downlink transport channels

synchronisation
The Iub transport downlink channels synchronisation procedure provides a method to estimate
the appropriate time to deliver downlink frames to the Node B.
The RNC and the Node B support the downlink transport channels synchronisation procedure
on RACH, FACH, PCH and DSCH common transport channels.
7-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iub user plane procedures for dedicated transport channel data streams
Iub user plane procedures for dedicated transport

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iub user plane procedures for dedicated transport

The following Iub user plane procedures are defined for dedicated transport channel data streams:
Iub dedicated transport channel data transfer
The Iub dedicated transport channel data transfer procedure is used to transfer user or
signalling data across the Iub interface between the SRNC and Node B for downlink transfer
and between Node B and SRNC for uplink transfer.
For uplink transmission transmission two modes can be used:
• normal mode.
• silent mode.
The mode is selected by the SRNC when transport connection is setup and signalled to the
Node B with the relevant control plane procedure.
Iub dedicated transport channel timing adjustment
The Iub dedicated transport channel timing adjustment procedure is used by the Node B to notify
the SRNC that downlink frames are being received too late or too early.
Iub dedicated transport channel synchronisation
The Iub dedicated transport channel synchronisation procedure defines the synchronisation of the
frame transport between the RNC and Node B. This procedure enables the SRNC to estimate
the appropriate time to deliver downlink frames to the Node B.
68P02905W21-B 7-17
02-Jun-2004
Iub user plane procedures for dedicated transport channel data streams Chapter 7: Transmission systems
Iub dedicated transport channel outer loop power control

information transfer (FDD)
The Iub dedicated transport channel outer loop power control information transfer procedure is used to provide
the uplink inner loop power control with a new Signal to Interference Ratio (SIR) target for the uplink quality.
Iub dedicated transport channel node synchronisation
The Iub dedicated transport channel node synchronisation procedure enables the SRNC to
estimate the timing difference among UTRAN nodes. Two types of node synchronisation
exist; RNC-Node B and inter Node B synchronisation.
Iub dedicated transport channel radio interference parameter

update (FDD)
The Iub dedicated transport channel radio interference parameter update procedure enables the update
the radio interface parameters that are applicable to all radio links for the corresponding UE.
The RNC and the Node B support both synchronised and unsynchronised parameter updates procedures.
7-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview NBAP common procedures
NBAP common procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to NBAP common procedures
NBAP common procedures are procedures that request initiation of a UE context for a specific
UE in a Node B or are not related to a specific UE.
The NBAP common procedures are grouped as follows:
NBAP common transport channel management
The NBAP common transport channel management group of procedures provide the capability to activate,
delete and reconfigure common channel resources such as random access and cell broadcast channels.
The common transport channel management procedures are:
• Common transport channel setup.
• Common transport channel reconfiguration.
• Common transport channel deletion.
NBAP configuration alignment (common)
The NBAP configuration alignment procedures provide the CRNC and the Node B with ability to each
verify that both nodes have the same information for the configuration of the radio resources.
The NBAP configuration alignment procedures are:
• Audit required.
• Audit.
68P02905W21-B 7-19
02-Jun-2004
NBAP common procedures Chapter 7: Transmission systems
NBAP common resources measurements (common)
The NBAP common resources measurements group of procedures enable the RNC to request measurements
from the Node B and to terminate previously requested measurements. The Node B uses procedures
in this group to report or terminate previously requested measurements.
The NBAP common resources measurements group of procedures are:
• Common measurement initiation.
• Common measurement reporting.
• Common measurement termination.
• Common measurement failure indication.
7-20 68P02905W21-B
02-Jun-2004
NBAP cell configuration management (common)
The NBAP cell configuration management group of procedures enable the RNC to configure parameters
of the Node B such as RF parameters, system information parameters and channel configuration. These
procedures are also used by the Node B to report such parameters to the RNC.
The NBAP cell configuration management group of procedures are:
• Cell setup.
• Cell reconfiguration.
• Cell deletion.
NBAP resource event management (common)
The NBAP resource event management group of procedures provides the Node B with the ability
to inform the CRNC about the status of Node B resources.
The NBAP resource event management group of procedures are:
• Block resource.
• Unblock resource.
• Resource status indication.
68P02905W21-B 7-21
02-Jun-2004
NBAP common procedures Chapter 7: Transmission systems
NBAP system information management (common)
The NBAP system information management comprises a single procedure which provides the CRNC
the ability to manage the scheduling of system information to be broadcast in a cell.
The NBAP system information management procedure is System information update.
7-22 68P02905W21-B
02-Jun-2004
NBAP radio link management (common)
The NBAP radio link management comprises a single procedure which provides the CRNC the
ability to manage the radio links using dedicated resources in a Node B. The NBAP radio link
management function has both common and dedicated procedures.
The only common procedure associated with the NBAP radio link management function is the Radio link setup.
68P02905W21-B 7-23
02-Jun-2004
NBAP dedicated procedures Chapter 7: Transmission systems
NBAP dedicated procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to NBAP dedicated procedures
NBAP dedicated procedures are procedures that are related to a specific UE context in the Node B.
The NBAP dedicated procedures are grouped as follows:
NBAP radio link management (dedicated)
The NBAP radio link management group of procedures provides the CRNC the ability to manage
the radio links using dedicated resources in a Node B. The NBAP radio link management
function has both common and dedicated procedures.
The dedicated procedures associated with the NBAP radio link management function are:
• Radio link addition.
• Radio link deletion.
• Unsynchronised radio link reconfiguration.
• Synchronised radio link reconfiguration preparation.
• Synchronised radio link reconfiguration commit.
• Synchronised radio link reconfiguration cancellation.
NBAP downlink power drifting correction (FDD) (dedicated)
The NBAP downlink power drifting correction (FDD) is a single procedure which enables
the CRNC to adjust the downlink power level of one or more radio links in order to avoid
downlink power drifting between the radio links.
The NBAP downlink power drifting correction (FDD) procedure is:
• Downlink power control.
7-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview NBAP dedicated procedures
NBAP measurements on dedicated resources (dedicated)
The NBAP measurements on dedicated resources group of procedures enables the CRNC to initiate
measurements in the Node B. These procedures also enable the Node B to report the result of the measurements.
The NBAP measurements on dedicated resources group of procedures are:
• Dedicated measurement initiation.
• Dedicated measurement reporting.
• Dedicated measurement termination.
• Dedicated measurement failure.
NBAP radio link supervision (dedicated)
The NBAP radio link supervision procedures provide notification to the CRNC of
change in radio link status (failure/restoration).
The NBAP radio link supervision procedures are:
• Radio link failure
• Radio link restoration.
NBAP compressed mode control (FDD) (dedicated)
The NBAP compressed mode control is a single procedure which enables the CRNC to
control the usage of compressed mode in a Node B.
The NBAP compressed mode control (FDD) procedure is Compressed mode command.
68P02905W21-B 7-25
02-Jun-2004
Error handling procedure Chapter 7: Transmission systems
Error handling procedure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to error handling procedure
The error handling procedure enables general error situations, for which function specific
error messages are not provided, to be reported.
Reporting of general error conditions
The single error handling procedure for reporting of error conditions is Error indication.
7-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iur interface
Iur interface
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iur interface
The Iur interface is the logical connection that enables an RNC to address any other RNC within the UTRAN
to establish a signalling bearer and user data bearers for Iur data streams. These RNCs can be Serving RNC
(SRNC) and Drift RNC (DRNC), or SRNC and Controlling RNC (CRNC), or two RNCs with no specificity.
The Iur interface is a logical point-to-point interface that is feasible even in the absence of a direct link and
supports the exchange of signalling information between any two RNCs (handovers, synchronisation and radio
resources management) and the transmission of data streams (common and dedicated transport channels).
Iur interface network layers
The Iur interface is composed of two network layers:
Transport Network Layer (TNL)

The TNL is concerned with the transport of the Radio Network Layer (RNL) protocols across the
Iur interface between two RNCs. This includes transport of the RNL control plane protocols, for
example RNL signalling information, and transport of RNL user plane protocols, for example
RNL user data. The TNL also provides the control for the establishment of the AAL2 circuits
used to transport the RNL user plane protocols belonging to this TNL.
Radio Network Layer (RNL)

The RNL is concerned with the radio specific functionality and the procedures related to
the interaction of two RNCs, for example, RL setup and deletion, UE mobility (handover
support), synchronisation, power control information.
68P02905W21-B 7-27
02-Jun-2004
Iur interface Chapter 7: Transmission systems
Iur interface radio application signalling
The Iur interface supports the radio application signalling as follows:

• Support of radio interface mobility, between RNSs, of UEs having a Radio
Resource Control (RRC) connection with UTRAN. This includes support for
Handover, RRM and synchronisation between RNSs.
• Paging in a UTRAN Registration Area (URA) or in a cell, in a DRNC.
• Soft Handover signalling, Hard Handover and SRNC Relocation signalling.
• Signalling related to radio resource handling between RNCs.
• Measurement reporting.
Iur interface radio network signalling
The Iur interface supports radio network signalling applications as follows:

• RL set-up, RL addition (addition of cells in the DRNS which may lead to
the addition of a new Iur data stream).
• RL deletion (removal of cells in the DRNS).
• Modification of RL characteristics.
• Reconfiguring DL code.
• Participating in SRNS relocation procedures.
• Transfer of UE-UTRAN signalling to be processed by the serving RNC (uplink

signalling transfer/downlink signalling transfer).
• Participating in the paging in the URA or in a cell in a DRNC.
• Releasing Controlling Radio Network Temporary Identity (C-RNTI) context in the old RNC.
• Reporting measurements (for example; RL failures, overload) from CRNC to SRNC.
7-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iur interface data
Iur interface data

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iur interface data
The Iur interface supports information exchange and includes one or more Iur data
streams, comprising the following:
• User data streams.
• Commonly agreed quality estimates.
• Synchronisation information.
• Flow control information for downlink common channels.
Iur interface data frames
The Iur interface supports the transport of uplink and downlink Iub/Iur data frames that carry user
and control data between SRNC and the Node B in the DRNS, via the DRNC.
Iur interface user data streams
The Iur interface supports user data flows for data retrieve (during relocation/handover). These are
defined logically over the Iur interface but are carried physically by the Iu interface.
Iur DCH data stream

The Iur interface provides a means for transporting uplink and downlink DCH Iur frames between the SRNC
and the DRNC. The DCH data frames are the same for the Iub and Iur interfaces. All the co-ordinated DCHs
that constitute a RAB are carried over one single transport bearer, that is, over one AAL2 connection.
Iur RACH data stream

The Iur interface transports uplink RACH transport data from the CRNC to the SRNC.
Each Iur RACH data stream between a SRNC and a CRNC is carried over one single
transport bearer, that is, over one AAL2 connection.
Iur FACH data stream

The Iur interface transports downlink FACH transport data from the SRNC to the CRNC. Each Iur FACH
data stream is carried over one single transport bearer, that is, over one AAL2 connection.
68P02905W21-B 7-29
02-Jun-2004
Iur interface data Chapter 7: Transmission systems
Iur interface quality estimates for uplink transport channels
On the radio, each transport block is associated with a Cyclic Redundancy Check (CRC) that is controlled by
the physical layer when received by the Node B. The result of this control is transferred with the transport block.
Each transport block set is associated with a Quality Estimate Indicator, calculated by the Node B.
These principles apply to both DCH and RACH transport channels.
Iur interface node synchronisation
Iur interface node synchronisation is only required between Node Bs belonging to the same RNC.
Therefore node synchronisation information is not carried over the Iur interface.
Iur interface frame synchronisation
Iur interface frame synchronisation is achieved via information held in the DCH data frames.
Maintenance of SRNC/Node B frame synchronisation via the use of DCH Control Frames when no data is
to be transmitted is achieved by sending DL synchronisation control frames to the Node B.
Iur interface MAC-d/ MAC-c(sh) flow control
The Iur provides a means of transporting uplink and downlink Medium Access Control entity handling
common channels (RACH, FACH)/(MAC-c(sh)) Service Data Units (SDU)s. The Iur interface also provides
a means to the SRNC for queue reporting and a means for the DRNC to allocate capacity to the SRNC.
Medium Access Control (MAC) entity handling dedicated channels (DCH) (MAC-d), MAC-c
and MAC-c(sh), at CRNC, operate scheduling between user flows coming from different SRNCs
according to a number of factors, such as their priority. Therefore, congestion may occur at CRNC
and a flow control mechanism is implemented to avoid this occurring.
The main principles of the flow control scheme are:
• Flow control is carried out per UE and priority class.
• The number of priority classes needed for FACH data stream over Iur is to be defined.
7-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iur interface protocol structure
Iur interface protocol structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iur interface protocol structure
This section describes the protocol structure and control and user planes within the
TNL and the RNL of the Iur interface.
Iur interface layers
Figure 7-6 shows a diagrammatic representation of the Iur interface protocol structure, which
shows two main functional (horizontal) layers as follows:
• "Iur interface Transport Network Layer (TNL)" on page 7-33.
• "Iur interface Radio Network Layer (RNL)" on page 7-35.
In addition to these two main functional layers, the Iur interface diagram also shows
protocols in vertical planes as follows:
68P02905W21-B 7-31
02-Jun-2004
Iur interface protocol structure Chapter 7: Transmission systems
Figure 7-6 Iur interface protocol structure

RADIO DCH FP
RNSAP RACH FP
NETWORK
LAYER FACH FP
DSCH FP
TRANSPORT NETWORK TRANSPORT NETWORK TRANSPORT NETWORK

USER PLANE CONTROL PLANE USER PLANE
ALCAP
SCCP STC
MTP3-B M3UA MTP3-B M3UA

TRANSPORT
NETWORK SSCF-NNI SCTP SSCF-NNI SCTP
LAYER
SSCOP IP SSCOP IP
AAL5 AAL5 AAL2
ATM
PHYSICAL LAYER
7-32 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iur interface Transport Network Layer (TNL)
Iur interface Transport Network Layer (TNL)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iur TNL
The Iur interface TNL is the lowest end-to-end layer and corresponds to the transport bearers used to provide
services to the RNL to transmit and receive RNL information, such as RNL PDUs, from the SRNC to the
DRNC. There are no specific RNL aspects within TNL as the TNL is independent of the RNL.
The TNL is sub-divided into three planes:
• radio network control plane.
• radio network user plane.
• transport network control plane.
Iur TNL radio network control plane
The TNL radio network control plane is responsible for carrying messages relating to
RNSAP procedures. These may be related to either a specific UE (connection-oriented
mode) or non-specific UE (connection-less mode).
The TNL radio network control plane is responsible for the following functions:
• Reliable transfer of control plane signalling messages in both connectionless
and connection-oriented modes.
• Independent connections for message transfers corresponding to individual UEs.
• Connection status information reporting for individual UEs.
• Networking and routing functions.
• Redundancy in the signalling network.
• Load sharing.
68P02905W21-B 7-33
02-Jun-2004
Iur interface Transport Network Layer (TNL) Chapter 7: Transmission systems
Iur TNL radio network user plane
The Iur ATM connections are Permanent Virtual Connections (PVCs), however, AAL2 connections are
established via Q.AAL2 (Q.2630.1) signalling protocol within these VCCs as follows:
• For DCH transport channels, AAL2 connections are established synchronously with
RAB. When a list of signal bearer sub-flows is requested one single AAL2 connection
is set-up for the set of RAB sub-flows. This makes the assumption that the error-rate on
the AAL2 connection is far lower than that occurring on the Uu interface.
• For common channels FACH and RACH, one AAL2 connection for each transport
channel between SRNC and CRNC is made, that is, one AAL2 connection for
each FACH (per physical channel), one for each RACH.
Iur TNL transport network control plane
The TNL transport network control plane facilitates the setting up of the data bearers for the user plane
through the use of Access Link Control Application Protocol (ALCAP). It is also responsible for transporting
the ALCAP messages associated with the setting up of these bearers between the RNC and Node B.
7-34 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iur interface Radio Network Layer (RNL)
Iur interface Radio Network Layer (RNL)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iur RNL
The Iu interface RNL provides the UTRAN related services and defines the procedures related to the
interface between two RNSs within a UTRAN. These procedures are as follows:
• Mobility management.
• Traffic management of Common Traffic Channels (CTC), this includes preparation

of common transport channel resources and paging.
• Traffic management of dedicated transport channels, this includes RL

setup/addition/deletion and management reporting.
• Traffic management of downlink shared transport channels, this includes RL

setup/addition/deletion and capacity allocation.
The Iur RNL is sub-divided into two planes; radio network control plane and radio network user plane.
Iur RNL radio network control plane
The Iur RNL radio network control plane incorporates the Radio Network Subsystem Application Part
(RNSAP) procedures and the signalling bearer for transporting the RNSAP messages.
The RNSAP functions and procedures are described in "RNSAP" on page 7-37.
68P02905W21-B 7-35
02-Jun-2004
Iur interface Radio Network Layer (RNL) Chapter 7: Transmission systems
Iur RNL radio network user plane
The Iur RNL radio network user plane is responsible for conveying actual user information such as speech,
video and data across the DRNC to/from the SRNC together with some radio control information, such
as measurement reports, power control information, synchronisation information and flow control. The
frame protocols in the user plane are transported over user specific AAL2 connections.
The CRNC provides uplink and downlink signalling to the SRNC for a given communication. The
RACH/FACH Iur data streams correspond to the data stream of one specific UE.
The user plane protocols support channel specific protocols related to the data streams
between the UTRAN and the UE.
The following frame protocols exist in the radio network user plane:
• Dedicated Channel Frame Protocol (DCH FP).
• Random Access Frame Protocol (RACH FP).
• Forward Access Frame Protocol (FACH FP).
The radio network layer user plane data are transported in common or dedicated channels, the
frame structures for these channels are described as follows:
• "Common transport channel frame structures" on page 7-50.
• "Dedicated channel frame structures" on page 7-54.
7-36 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNSAP
RNSAP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RNSAP
RNSAP is the radio network protocol used as the radio network layer signalling
protocol between RNCs over the Iur interface.
RNSAP is responsible for signalling procedures over a connection-oriented transport for addition/removal
of cells to the active set in the DRNS, for modification of RAB characteristics and power control.
RNSAP functions
RNSAP functions provide for mobility management and transparent transfer of signalling between CN and
UE. Connection-less procedures are also provided for, such as paging and common channel management.
The RNSAP protocol has the following functions:
• RL management.
• Physical channel reconfiguration.
• RL supervision.
• Compressed mode control.
• Measurements on dedicated resources.
• Downlink power drifting correction.
• Common Control Channel (CCCH) signalling transfer.
• Paging.
• Common control channel resources management.
• Relocation execution.
• Reporting of general error situations.
68P02905W21-B 7-37
02-Jun-2004
RNSAP Chapter 7: Transmission systems
RNSAP message flow diagrams
The Iur interface RNSAP protocol procedures are described within procedure categories as follows:
RNSAP basic mobility procedures

The RNSAP basic mobility procedures are related to the basic mobility handling of the UE within the UTRAN.
RNSAP Dedicated Channel (DCH) procedures

The RNSAP DCH procedures are specific to the support of a particular user.
RNSAP Dedicated Channel (DCH) measurement procedures

The RNSAP measurement procedures are a subset of the RNSAP DCH procedures, and are used to enable
the SRNC to request and obtain specific network measurements through the DRNC.
RNSAP Control Channel (CCH) procedures

The RNSAP CCH procedures are used to control common transport channel data streams over the Iur interface.
RNSAP global procedures

The RNSAP global procedures are the procedures not related to a specific UE.
7-38 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNL user plane channel procedures
RNL user plane channel procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RNL user plane channel procedures
RNL user plane services allow the transmission of user data from the UE to the CN, providing continuation
of the Iub data transport. Also some control information, such as power control, measurement reports and
synchronisation is exchanged between the SRNC and the DRNC, and SRNC and Node B. These data
are transported in data frames or control frames and over common or dedicated channels.
RNL user plane procedures
RNL user plane channel procedures are described under the following headings:
• "RNL user plane common channel procedures" on page 7-40.
• "RNL user plane dedicated channel procedures" on page 7-43.
• "RNL user plane dedicated channel control frame procedures" on page 7-45.
68P02905W21-B 7-39
02-Jun-2004
RNL user plane common channel procedures Chapter 7: Transmission systems
RNL user plane common channel procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RNL user plane common channel procedures
The SRNC and DRNC support the transmission of data and control frames over common channels
(RACH/FACH) to provide the continuation of the Iub data transport over the Iur interface.
RNL user plane common channel procedures are as follows:
• RACH/CPCH data transfer.
• FACH data transfer.
• FACH flow control.
RACH/CPCH data transfer
RACH/CPCH data transfer objective

The RACH/CPCH data transfer procedure provides transport of MAC-c/sh SDUs from the
DRNC to the SRNC for RACH/CPCH common transport channels.
RACH/CPCH data transfer description

The DRNC transmits the data received on the RACH/CPCH transport channel to the SRNC using
RACH/CPCH data frames. The DRNC protects the data transmitted with a mandatory payload CRC
and maps all RACH for a given UE to the same Iur transport bearer.
RACH/CPCH data transfer procedure

The DRNC initiates the RACH/CPCH data transfer procedure by sending the RACH/CPCH
data frame to the SRNC. See Figure 7-7.
Figure 7-7 RACH/CPCH data transfer
SRNC DRNC
RACH/CPCH DATA FRAME
7-40 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNL user plane common channel procedures
Abnormal conditions
A Frame Protocol with an unknown or invalid IE will be ignored.
FACH data transfer
FACH data transfer objective

The FACH data transfer procedure provides transport of MAC-c SDUs from the SRNC to the DRNC.
FACH data transfer description

The SRNC transmits the data on the FACH transport channel to the DRNC using FACH data frames.
The SRNC maps all FACH for a given UE to the same Iur transport bearer.
FACH data transfer procedure

The SRNC initiates the FACH data transfer procedure by sending the FACH data
frame to the DRNC. See Figure 7-8.
Figure 7-8 FACH data transfer
SRNC DRNC
FACH DATA FRAME
Abnormal conditions
A Frame Protocol with an unknown or invalid IE will be ignored.
FACH flow control
FACH flow control objective

The FACH flow control procedure enables flow control between MAC-d and MAC-c.
FACH flow control description

The DRNC sends FACH flow control frames to the SRNC to provide flow control between MAC-d and MAC-c.
68P02905W21-B 7-41
02-Jun-2004
RNL user plane common channel procedures Chapter 7: Transmission systems
FACH flow control procedure

The DRNC initiates the FACH flow control procedure by sending the FACH flow
control frames to the SRNC. See Figure 7-9.
Figure 7-9 FACH flow control
SRNC DRNC
FACH FLOW CONTROL
Abnormal conditions
A frame protocol with an unknown or invalid IE will be ignored.
7-42 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNL user plane dedicated channel procedures
RNL user plane dedicated channel procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RNL user plane dedicated channel procedures
The SRNC and the DRNC, through the Iur interface, supports the transmission of data and control frames
over dedicated channels (DCH) to provide the continuation of the Iub data transport over the Iur interface.
RNL user plane dedicated channel procedures are as follows:
• Date transfer - uplink.
• Data transfer - downlink.
Data transfer - uplink
Data transfer - uplink objective

The data transfer - uplink procedure is used to provide transmission of user data from the UE to
the SRNC through the Node B and DRNC over the Iur interface.
Data transfer - uplink message flow

The DCH data frame is sent from the UE, through the Node B and the DRNC to the SRNC. See Figure 7-10
Figure 7-10 Uplink data transfer
NODE B DRNC SRNC
DATA FRAME
Abnormal conditions
There are no abnormal conditions associated with this procedure.
68P02905W21-B 7-43
02-Jun-2004
RNL user plane dedicated channel procedures Chapter 7: Transmission systems
Data transfer - downlink
Data transfer - downlink objective

The data transfer - downlink procedure is used to provide transmission of user data from the SRNC to
the UE through the DRNC and Node B over the Iur interface. See Figure 7-11.
Figure 7-11 Downlink data transfer
NODE B DRNC SRNC
DATA FRAME
The DCH data frame is sent from the SRNC, through the DRNC and the Node B to the UE.
Abnormal conditions
There are no abnormal conditions associated with this procedure.
7-44 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNL user plane dedicated channel control frame procedures
RNL user plane dedicated channel control frame

procedures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to RNL dedicated channel control frame procedures
Control frames are used to transport control information between SRNC and Node B
through the DRNC over the Iur interface.
Control frame procedures are as follows:
• Timing adjustment.
• Synchronisation.
• Outer loop PC information transfer.
• Node synchronisation.
• Radio interface parameter update.
Timing adjustment
Timing adjustment objective

The timing adjustment procedure is controlled by the SRNC to ensure that downlink data frames
sent to the Node B arrive in time to be transmitted on the specified CFN.
Timing adjustment message flow

The timing adjustment signal is sent from the Node B through the DRNC to the SRNC.
The SRNC includes the CFN in all downlink DCH frame protocol frames to maintain the
synchronisation of a DCH data stream.. See .Figure 7-12.
Figure 7-12 Timing adjustment
NODE B DRNC SRNC
TIMING ADJUSTMENT
68P02905W21-B 7-45
02-Jun-2004
RNL user plane dedicated channel control frame procedures Chapter 7: Transmission systems
Abnormal conditions
A frame protocol frame with illegal or incomprehensible parameter values will be ignored.
Synchronisation
Synchronisation objective
The synchronisation procedure is used to establish an arrangement between the SRNC and
Node B about the CFN and ToA parameters and to supervise whether or not data frames
are received in the configured receive time window.
Synchronisation message flow

1. The SRNC invokes the synchronisation procedure by sending a downlink
synchronisation control frame to Node B through the DRNC, this message
indicates the target CFN. See Figure 7-13.
2. On receipt of the downlink synchronisation control frame from the SRNC,

the Node B responds with an uplink synchronisation control frame indicating
the ToA for the downlink synchronisation frame and the CFN indicated in the
received downlink synchronisation control frame.
The uplink synchronisation control frame is always sent to the SRNC, even if the downlink
synchronisation control frame is received by the Node B within the arrival time window.
Figure 7-13 DCH synchronisation
NODE B DRNC SRNC
DOWNLINK SYNCHRONISATION
UPLINK SYNCHRONISATION
Abnormal conditions
7-46 68P02905W21-B
02-Jun-2004
Outer loop power control (PC) information transfer
Outer loop PC information transfer objective

The outer loop PC information transfer procedure is used by the SRNC to provide the Node B
with a new quality target value for the uplink quality.
Outer loop PC information transfer flow

The SRNC uses a single transport bearer, with low transfer delay (high prority) to send the uplink outer loop
power control frames through the DRNC to the Node B. Based, for example, on the Cyclic Redundancy
Check Indicator (CRCI) values and on the quality estimate in the uplink frames, the SRNC modifies the
Signal-to-Interference Ratio (SIR) target in one control frame sent to the Node Bs. See Figure 7-14.
Figure 7-14 Outer loop PC information transfer
NODE B DRNC SRNC
OUTER LOOP PC
Abnormal conditions
Node synchronisation
Node synchronisation objective

The node synchronisation procedure is used for the estimation and compensation of timing differences
between SRNC and Node B in order to achieve a common timing reference.
Node synchronisation message flow

1. The SRNC invokes the node synchronisation procedure by sending a downlink
node synchronisation control frame to Node B through the DRNC, this message
contains the parameter T1. See Figure 7-15.
68P02905W21-B 7-47
02-Jun-2004
RNL user plane dedicated channel control frame procedures Chapter 7: Transmission systems
2. On receipt of the downlink node synchronisation control frame from the SRNC, the Node B
responds with an uplink node synchronisation control frame indicating T2 and T3, as well as
T1 which was indicated in the received downlink node synchronisation control frame.
Figure 7-15 Node synchronisation
NODE B DRNC SRNC
DOWNLINK SYNCHRONISATION
UPLINK SYNCHRONISATION
Abnormal conditions
Radio interface parameter update
Radio interface parameter update objective

The radio interface parameter update procedure is used to update radio interface
parameters which are applicable to all RLs for the concerned UE. Both synchronised and
unsynchronised parameter updates are supported.
Radio interface parameter update message flow

1. The SRNC sends the update parameters in a radio interface parameter update control
frame through the DRNC to the Node B. See Figure 7-16.
2. If the radio interface parameter update control frame contains a Transmit Power Control Power
Offset (TPC PO) value, the Node B will apply the newly provided TPC PO value as soon
as possible in case there is no CFN included or no CFN indication is given.
Figure 7-16 Radio interface parameter update
NODE B DRNC SRNC
RADIO INTERFACE PARAMETER UPDATE
7-48 68P02905W21-B
02-Jun-2004
Abnormal conditions
68P02905W21-B 7-49
02-Jun-2004
Common transport channel frame structures Chapter 7: Transmission systems
Common transport channel frame structures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to common transport channel
The general structure of a common transport channel frame consists of a header and a payload. The
payload section may consist of user or control data. Figure 7-17 shows this structure.
Figure 7-17 Common transport channel frame structure
HEADER PAYLOAD: DATA OR CONTROL INFORMATION
The header contains the frame type field and information related to the frame type.
There are two types of frames, as follows:
• Data frame for transmission of data.
• Control frame for signalling between RNCs, no user data is transmitted in a control frame.
Figure 7-18 shows an example common transport channel frame structure.
Figure 7-18 Example common transport channel frame structure
7 6 5 4 3 2 1 0
FIELD 1 FIELD 2 BYTE 1
FIELD 3 BYTE 2
FIELD 3 (CONT) FIELD 4 BYTE 3
BYTE 4
Unless otherwise indicated, fields which consist of multiple bits within a byte have the more significant bit
located at the higher bit position (indicated above frame in Figure 7-18). In addition, if a field spans several
bytes, more significant bits will be located in lower numbered bytes (right of frame in Figure 7-18).
For the Iur interface, the frame is transmitted starting from the lowest numbered byte. Within each
byte, the bits are sent according to decreasing bit position (bit position 7 first).
7-50 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Common transport channel frame structures
The parameters are specified giving the value range and the step (if not 1). The
coding is normally carried out as follows:
• Lower value (in the range) coded as a sequence of 0s.
• Higher value in the range coded as a sequence of 1s.
Data frame structure
RACH channels
RACH Iur data stream corresponds to the data stream of one specific UE. The used transport
bearer for the transport of FACH/RACH is bi-directional.
The RACH/FACH FP does not allow multiplexing of data streams from different UEs onto the
same data frame, but does allow multiple UEs to share the same transport bearer.
Figure 7-19 shows the RACH data frame structure.
68P02905W21-B 7-51
02-Jun-2004
Common transport channel frame structures Chapter 7: Transmission systems
Figure 7-19 RACH data frame structure
7 0
HEADER CRC FT
SRNTI
SRNTI HEADER
PROPAGATION DELAY
DATA FRAME LENGTH
MAC-c SDU
PAYLOAD
MAC-c SDU (cont) PAD
PAYLOAD CRC
PAYLOAD CRC (cont)
FT = Frame Type
PAD = Propagation Delay
FACH channels
FACH Iur data stream corresponds to the data stream of one specific UE. The used transport
bearer for the transport of FACH/RACH is bi-directional.
Figure 7-20 shows the FACH data frame structure.
7-52 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Common transport channel frame structures
Figure 7-20 FACH data frame structure
7 0
HEADER CRC FT
DRNTI
DRNTI
FI CmCH PRIORITY INDICATOR PAD HEADER
FRAME SEQUENCE NUMBER
USER BUFFER SIZE
DATA FRAME LENGTH
MAC-s SDU
PAYLOAD
MAC-c SDU (cont) PAD
PAYLOAD CRC
PAYLOAD CRC (cont)
FT = Frame Type
FI = Frame Indicator
PAD = Propagation Delay
68P02905W21-B 7-53
02-Jun-2004
Dedicated channel frame structures Chapter 7: Transmission systems
Dedicated channel frame structures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to dedicated channel
The general structure of a dedicated channel frame consists of a header, payload and tail. The payload
section may consist of user or control data. Figure 7-21 shows this structure.
Figure 7-21 Dedicated channel frame structure
HEADER PAYLOAD: DATA OR CONTROL INFORMATION
The header contains the frame type field and information related to the frame type.
There are two types of frames, as follows:
• Data frame for transmission of data.
• Control frame for signalling between RNCs, no user data is transmitted in a control frame.
The uplink and downlink dedicated data channel frame and the general control frame
structures are described as follows.
Uplink data frame structure
See Figure 7-22.
7-54 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Dedicated channel frame structures
Figure 7-22 Uplink DCH data frame structure
7 0
HEADER CRC FT
CONNECTION FRAME NUMBER (CFN)
TRANSPORT FORMAT INDICATOR (TFI) OF FIRST DCH HEADER
TFI OF LAST DCH
QUALITY ESTIMATE (QE) OF PHYSICAL CHANNEL
FIRST TRANSPORT BLOCK (TB) OF FIRST DCH
FIRST TB OF FIRST DCH (cont.) PAD
LAST TB OF FIRST DCH
LAST TB OF FIRST DCH (cont.) PAD
FIRST TB OF LAST DCH
PAYLOAD
FIRST TB OF LAST DCH (cont.) PAD
LAST TB OF LAST DCH
LAST TB OF LAST DCH (cont.) PAD
2 PAD
PAYLOAD CHECKSUM
OPTIONAL
PAYLOAD CHECKSUM (cont.)
1 = CRCI OF FIRST TB OF FIRST DCH

2 = CRCI OF LAST TB OF LAST DCH
68P02905W21-B 7-55
02-Jun-2004
Dedicated channel frame structures Chapter 7: Transmission systems
Downlink data frame structure
See Figure 7-23
Figure 7-23 Downlink DCH data frame structure
7 0
HEADER CRC FT
CFN
TFI OF FIRST DCH HEADER
TFI OF LAST DCH
FIRST TB OF FIRST DCH
FIRST TB OF FIRST DCH (cont.) PAD
FIRST TB OF LAST DCH
LAST TB OF LAST DCH PAYLOAD
LAST TB OF LAST DCH
LAST TB OF LAST DCH (cont.) PAD
PAYLOAD CHECKSUM
OPTIONAL
PAYLOAD CHECKSUM (cont.)
7-56 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Dedicated channel frame structures
Control frame structure
Figure 7-24 shows the general control frame structure.
Figure 7-24 General structure of the control frame
7 0
FRAME CRC FT
HEADER
CONTROL FRAME TYPE (2 BYTES)
CONTROL INFORMATION
PAYLOAD
(VARIABLE
LENGTH)
CONTROL INFORMATION (cont.)
68P02905W21-B 7-57
02-Jun-2004
Iu-CS and Iu-PS interfaces Chapter 7: Transmission systems
Iu-CS and Iu-PS interfaces

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iu-CS and Iu-PS interface
The Iu interfaces (comprising Iu-CS and Iu-PC interfaces) is a single ATM based connection between the
UMTS Terrestrial Radio Access Network (UTRAN) and the UMTS Core Network (CN). Separate logical links
and protocol stacks are used to exchange signalling and user data between the Radio Network Controller (RNC)
and MSCu for circuit-switched service domains using ATM Adaptation Layer Type 2 (AAL2), and between
the RNC and SGSNu for packet-switched service domains using ATM Adaptation Layer Type 5 (AAL5).
The Iu interface performs a similar function to the Gb interface between GSM BSS and GPRS Core Network.
Each individual RNC within the UTRAN has one Iu-CS and one Iu-PS interface.
The Iu interfaces (Iu-CS and Iu-PS) are used for signalling and information exchange as follows:
• Radio Access Bearer (RAB) signalling.
• Data information.
• In-band user plane frame protocol signalling.
Iu-CS and Iu-PS interface Radio Access Bearer (RAB) signalling
The Iu interfaces support RAB set-up, modification and release signalling as follows:
• Transparent non-access signalling between UE and CN.
• Paging in a Location Area (LA) or a Routing Area (RA).
• Hard handover and serving RNC (SRNC) relocation signalling.
• Signalling related to radio resource handling between RNCs.
• Common procedures such as global reset.
Iu-CS and Iu-PS interface data information
The Iu interfaces support the transfer of user data streams as two logically separate signalling flows between
the combined or separate circuit-switched or packet-switched core networks and the RNC.
7-58 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iu-CS and Iu-PS interfaces
Iu-CS and Iu-PS interface in-band user plane frame protocol

signalling
The Iu interfaces support in-band user plane frame protocol signalling as follows:
• Frame handler function signalling.
• Signalling for procedure control functions.
• Signalling for non access stratum specific functions.
There are separate signalling and data connections to the two CN domains,
this applies to both transport and radio network layers.
At the CN the Iu-CS is connected to a serving MSCu and the Iu-PS is connected to a
SGSNu. Each RNC is controlled by one MSCu and one SGSNu. However, each MSCu
or SGSNu is capable of controlling multiple RNCs.
68P02905W21-B 7-59
02-Jun-2004
Iu-CS and Iu-PS interface protocol structure Chapter 7: Transmission systems
Iu-CS and Iu-PS interface protocol structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to Iur interface protocol structure
This section describes the protocol structure and control and user planes within the
TNL and the RNL of the Iu interface.
Iu-CS and Iu-PS interface network layers
Figure 7-25 shows the Iu-CS and Iu-PS interface protocol strcuture, with the following
two main functional (horizontal) layers:
• "Iu-CS and Iu-PS interface Transport Network Layer (TNL)" on page 7-62.
• "Iu-CS and Iu-PS interface Radio Network Layer (RNL)" on page 7-65.
In addition to these two main functional layers, the Iu interface protocol structure diagram
also shows protocols in vertical planes as follows:
7-60 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iu-CS and Iu-PS interface protocol structure
Figure 7-25 Iu-CS and Iu-PS interface protocol structure

Iu-CS OR Iu-PS USER

PLANE (UP) DATA
RADIO RANAP STREAM FRAME
NETWORK PROTOCOL(S)
LAYER
TRANSPORT NETWORK TRANSPORT TRANSPORT NETWORK

USER PLANE NETWORK USER PLANE
CONTROL PLANE
TRANSPORT
SIGNALLING
(ALCAP(S))
TRANSPORT
NETWORK
LAYER RADIO NETWORK TRANSPORT
SIGNALLING SIGNALLING NETWORK CS OR PS
BEARER(S) BEARER(S) DATA BEARER(S)
ATM
PHYSICAL LAYER
68P02905W21-B 7-61
02-Jun-2004
Iu-CS and Iu-PS interface Transport Network Layer (TNL) Chapter 7: Transmission systems
Iu-CS and Iu-PS interface Transport Network Layer

(TNL)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iu TNL
The Iu-CS and Iu-PS interface TNL is the lowest end-to-end layer and is responsible for establishing physical
connections of the transport network signalling bearers used to carry the radio network related information.
The Iu TNL is sub-divided into three planes; radio network control plane, radio network
user plane and transport network user plane.
Iu TNL radio network control plane
The Iu TNL radio network control plane is responsible for carrying messages related to
RANAP procedures. These may be related to a specific UE (connection-oriented mode) or to
a common, non-UE specific procedure (connection-less mode).
For both CS and PS domains the TNL radio network control plane is responsible for the following functions:
• Reliable transfer of control plane signalling messages in both connectionless
and connection-oriented modes.
• Independent connections for message transfers corresponding to individual UEs.
• Connection status information reporting for individual UEs.
• Networking and routing functions.
• Redundancy in the signalling network.
• Load sharing.
Iu TNL radio network user plane
The Radio Network User Plane is responsible for conveying actual user information (not
user radio equipment information but client user data like speech, video, data) across the Iu
Interface and the protocols include facilities for transfer of that data as well as user plane
control (different than control or signalling in control plane).
7-62 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iu-CS and Iu-PS interface Transport Network Layer (TNL)
Iu TNL transport network control plane
The Iu TNL transport network control plane facilitates the setting up of the data bearers for the user plane
through the use of the Access Link Control Application Protocol (ALCAP). It is also responsible for
transporting the ALCAP messages associated with the setting up of these bearers between the RNC and Node B.
Iu-CS and Iu-PS user plane protocol modes of operation
There are two modes of operation as follows:

• Transparent Mode (TM).
• Support Mode for predefined SDU size (SMpSDU).
68P02905W21-B 7-63
02-Jun-2004
Iu-CS and Iu-PS interface Transport Network Layer (TNL) Chapter 7: Transmission systems
Transparent Mode (TM)

Transparent mode is intended for those RABs that do not require any particular feature from
the Iu UP protocol other than the transfer of user data.
In this mode, the Iu UP protocol instance does not perform any Iu UP protocol information exchange with
its peer over the Iu interface: no frame is sent. The Iu UP protocol layer is crossed through by Protocol
Data Units (PDUs) being exchanged between upper layers and transport network layer.
For instance, the transfer of GPRS Tunnelling Protocol (GTP-U) PDUs or nontransparent CS
data could utilise the transparent mode of the Iu UP protocol.
Support Mode for predefined SDU size (SMpSDU)

The support modes are intended for those RABs that do not require particular features from the Iu UP
protocol in addition to transfer of user data. When operating in a support mode, the peer Iu UP protocol
instances exchange Iu UP frames whereas in transparent mode, no Iu UP frames are generated.
7-64 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Iu-CS and Iu-PS interface Radio Network Layer (RNL)
Iu-CS and Iu-PS interface Radio Network Layer (RNL)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Iu RNL
The Iu-CS and Iu-PS interface RNL provides the UTRAN related services and defines
procedures related to the operation of the RNC.
The Iu RNL is sub-divided into two planes; radio network control plane and radio network user plane.
Iu RNL radio network control plane
The Iu RNL control plane is responsible for handling RANAP procedures to enable the setting
up and management of the RABs. RANAP procedures also manage individual UEs, mobility
management, RNC configuration and handling of abnormal conditions.
For both CS and PS domains RANAP provides the following services:
• Provides a set of general UTRAN procedures from CN such as paging, reset, overload,
CN information broadcast, or from UTRAN such as reset, overload.
• Separates each UE on the protocol level for mobile specific signalling management.
• Enables transfer of transparent non-access stratum signalling.
• Request and management of various types of UTRAN RABs.
Iu RNL radio network user plane
The Iu RNL radio network user layer is responsible for handling the Iu interface user plane protocols.
68P02905W21-B 7-65
02-Jun-2004
Uu interface Chapter 7: Transmission systems
Uu interface
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Uu interface overview
The Uu interface is the radio interface between the UTRAN and the User Equipment (UE).
The Uu interface provides the means of exchange of information between the network and the UE.
Uu interface signalling
The Uu interface supports signalling to provide applications as follows:

• Resource allocation for supporting dedicated channels.
• Resource allocation for common channels.
• Broadcast channel control.
• Broadcast channel data.
• Paging.
• Broadcast/Multicast services.
Uu interface data
The Uu interface supports data transmission as follows:

• Dedicated Channel (DCH) data.
• Random Access Channel (RACH) data.
• Forward Access Channel (FACH) data.
• Paging Channel (PCH) data.
• Broadcast Channel (BCH) data.
7-66 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Uu interface protocol structure
Uu interface protocol structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Uu interface layers
Figure 7-26 shows the Uu interface protocol structure.
Figure 7-26 Uu interface protocol structure
C-PLANE SIGNALLING U-PLANE INFORMATION
GC Nt DC
DUPLICATION AVOIDANCE
GC Nt DC
UuS BOUNDARY
L3
CONTROL
RRC
CONTROL
CONTROL
CONTROL
CONTROL
PDCP L2/PDCP
PDCP
BMC L2/BMC
RLC
RLC RLC
RLC RLC L2/RLC
RLC RLC
RLC RLC
LOGICAL
CHANNELS
MAC L2/MAC
TRANSPORT
CHANNELS
PHYSICAL LAYER L1
68P02905W21-B 7-67
02-Jun-2004
Uu interface protocol structure Chapter 7: Transmission systems
The Uu interface consists of four functional layers as follows:

• Layer 1 - physical layer between the Node B and the UE.
• Layer 2 - (MAC/RLC/PDCP) between the RNC and the UE.
• Layer 3 - (RRC) between the RNC and the UE.
• The Non Access Stratum (NAS) layers (MM/CC) between the CN and the UE.
Uu interface layer 1 - physical layer
The Uu interface physical layer (layer 1) is mainly located between the Node B and the UE (except
for the soft-handover splitting/selection function located in the RNC).
The physical layer is based on W-CDMA technology and 3GPP TS25.2xx series
describes the physical layer specification.
The physical layer interfaces with Medium Access Control (MAC) sublayer of Layer 2 and with Radio
Resource Control (RRC) Layer of Layer 3. The physical layer offers different transport channels to the
MAC. A transport channel is characterized by how the information is transferred over the radio interface.
Physical channels are defined in the physical layer. There are two duplex modes:
• Frequency Division Duplex (FDD).
• Time Division Duplex (TDD) specified in the 3GPP standards.
Only FDD is supported in USR1.0.

The physical layer is controlled by the RRC.
The physical layer offers data transport services to the higher layers. This is achieved through the use of
transport channels via the MAC. The characteristics of a transport channel are defined by its transport format (or
transport format set), specifying the physical layer processing to be applied to the transport channel in question,
such as convolutional channel coding and interleaving, and any service-specific rate matching as needed.
The following physical layer functions are supported by Node B:
• Error detection on transport channels through the use of CRC.
• Transport block concatenation and code block segmentation
• Convolutional encoding/decoding of the following transport channels: BCH,

PCH, RACH, FACH, DCH.
• Turbo encoding/decoding of the following transport channels: FACH, DCH,
• Rate matching of transport channels
• Discontinuous transmission (DTX) through the use of DTX indication bits

for downlink transport channels
• Inter-frame interleaving/de-interleaving on a per transport channel basis
• Radio frame segmentation
7-68 68P02905W21-B
02-Jun-2004
• Multiplexing of different transport channels into a coded composite transport

channels in the downlink
• De-multiplexing of a coded composite transport channels into different

transport channels in the uplink
• Mapping of a coded composite transport channel onto multiple physical channels in the downlink
• Mapping of multiple physical channels onto a coded composite transport channel in the uplink
• Physical channel segmentation when multiple physical channels are used
• Intra-frame interleaving/de-interleaving on a per radio frame basis
• Compressed mode implementation
• Transport format signalling through the use of TFCI based transport format detection
• Transport format signalling through the use of blind transport format detection
• Spreading of downlink physical channels
• Modulation of downlink physical channels
• Despreading of uplink physical channels
• Demodulation of uplink physical channels
• Frequency and time (chip, bit, slot, frame) synchronisation
• Space time block coding based transmit antenna diversity (STTD) of the following downlink
physical channels: P-CCPCH, S-CCPCH, PICH, DPCH, and PDSCH
• Time switched transmit diversity (TSTD) of the following downlink physical channel: SCH
• Uplink inner loop power control
• Downlink inner loop power control
• Soft handover
• Inter-system hard handover
• Inter-frequency hard handover
• Softer handover (combining/splitting)
• Physical layer measurements
• Error indication by means of CRC failure detection, Transport Channel

BER and Physical Channel BER
68P02905W21-B 7-69
02-Jun-2004
Uu interface layer 2 - Medium Access (MAC) layer
The Uu interface MAC layer provides the procedures needed to control access to physical radio resources.
The MAC specific functions are:
• Mapping between logical channels and transport channels.
• Transport format selection depending on instantaneous source rate.
• Priority handling between data flows of one UE.
• Priority handling between UE by means of dynamic scheduling.
• Identification of UE on common transport channels.
• Multiplexing/demultiplexing of higher layer Protocol Data Units (PDUs) into/from Transport

Block (TB) delivered to/from physical layer on common or dedicated transport channels.
• Dynamic transport channel switching.
• Ciphering for transparent RLC on DCH.
• Control of RACH transmission.
• Traffic volume monitoring.
• Flow control towards the MAC-c (MAC on the common channel).
• Routing of higher layer signalling.
• Access service class selection for RACH transmission.
Uu interface layer 2 - Radio Link Control (RLC) layer
The Uu interface RLC layer provides the procedures needed for transferring data between the
UTRAN and the UE with three different protection modes as follows:
• Transparent Mode (TM).
• Unacknowledged Mode (UM).
• Acknowledged Mode (AM).
Any one RLC entity must be assigned one of the above protection modes.
7-70 68P02905W21-B
02-Jun-2004
Transparent Mode (TM)

Functions for the transparent mode are as follows:
• Segmentation and reassembly.
• Transfer of user data.
Unacknowledged Mode (UM)

Functions for the unacknowledged mode are as follows:
• Concatenation.
• Padding (when concatenation is not applicable).
• Ciphering.
• Sequence number check.
Acknowledged Mode (AM)

Functions for the acknowledged mode are as follows:
• Concatenation.
• Padding (when concatenation is not applicable).
• Error correction.
• Ciphering.
• In sequence delivery of higher layer PDUs.
• Duplicate detection.
• Protocol error detection and recovery.
• Flow control.
• Header compression.
Uu interface layer 2 - Packet Data Convergence Protocol (PDCP)

layer
Figure 7-27 shows the Uu interface PDCP layer architecture.
68P02905W21-B 7-71
02-Jun-2004
Figure 7-27 PDCP layer architecture
C-SAP
PDCP-
sublayer
PDCP PDCP PDCP PDCP PDCP
RLC-SDU
UM-SAP AM-SAP Tr-SAP RLC
The Uu interface PDCP layer provides the functions required for header compression
within UTRAN when using IP services.
The PDCP specific functions are:
• Compression of redundant protocol control information (that is, TCP/IP and RTP/UDP/IP
headers) at the transmitting entity and decompression at the receiving entity. The header
compression method is specific to the particular network layer, transport layer or upper
layer protocol combinations, that is, TCP/IP and RTP/UDP/IP.
• Transfer of user data. Transmission of user data means that PDCP receives
PDCP-SDU from the NAS layer and forwards it to the appropriate radio bearer
provided by the RLC layer and vice versa.
• Buffering of transmitted PDCP SDUs and associated PDCP SDU sequence numbers to the
transmitted and received PDCP SDUs to guarantee lossless SRNS relocation.
• Multiplexing of different Radio Bearers (RBs) onto the same RLC entity.
Uu interface layer 2 - Broadcast/ Multicast Control (BMC) layer
The Uu interface BMC layer provides the procedures needed for supporting broadcast
and multicast services in UTRAN.
Uu interface layer 3 - Radio Resource Control (RRC) layer
Figure 7-28 shows the Uu interface RRC layer architecture.
7-72 68P02905W21-B
02-Jun-2004
Figure 7-28 Uu interface RRC layer architecture
ACCESS STRATUM
RFE RFE RFE
RRC
RRC
SAPs
BCFE
PDCP PNFE PNFE
DCFE PNFE
SCFE
TME
Tr-SAP UM-SAP AM-SAP

RLC
ctrl
RLC
MAC
ctrl
MAC
L1
ctrl
L1
The Uu interface RRC layer handles the control plane signalling of layer 3 between the UTRAN and UEs.
68P02905W21-B 7-73
02-Jun-2004
The RRC specific functions are:

• Broadcast of information provided by the CN.
• Broadcast of information related to the access stratum.
• Establishment, maintenance and release of an RRC connection between the UE and UTRAN.
• Establishment, reconfiguration and release of RABs.
• Assignment, reconfiguration and release of radio resources for the RRC connection.
• RRC connection mobility functions.
• Paging/notification.
• Routing of higher layer PDUs.
• UE measurement reporting and control of the reporting.
• Outer loop power control.
• Control of ciphering.
• Arbitration of radio resources on uplink DCH.
Uu interface Non-Access Stratum (NAS) layer
The Uu interface NAS layer consists of Mobility Management and Call Control layers,
which are located between the CN and the UE.
7-74 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RRC connection procedures
RRC connection procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
RRC connection establishment
RRC connection establishment objective

When the RNC receives a request to establish a Radio Resource Control (RRC) connection, the
Radio Network Connection Control function handles the RRC connection establishment process.
There can only be one RRC connection per UE. A UE in idle mode requests the establishment
of an RRC connection using the RRC connection request message either when directed to do
so by its upper layers or in response to a page from the network.
RRC connection establishment procedure

See Figure 7-29.
Figure 7-29 RRC connection establishment, network accepts RRC connection
UE UTRAN
RRC CONNECTION REQUEST
RRC CONNECTION SETUP

TIMER TRRC_EST
STARTED
RRC CONNECTION SETUP COMPLETE
TIMER TRRC_EST
STOPPED
TIMER
Twait_for_initial_direct_transfer
STARTED
1. On receiving the RRC connection request message the RNC invokes the RRC connection
request procedure, sends the RRC connection setup message and starts timer TRRC_EST.
2. The RNC stops timer TRRC_EST on receipt of the RRC connection setup complete
message from the UE and considers the UE context established.
68P02905W21-B 7-75
02-Jun-2004
RRC connection procedures Chapter 7: Transmission systems
3. The RNC starts timer Twait_for_initial_direct_transfer on receipt of the RRC connection setup complete
message to wait for a RRC initial direct transfer message to be received. See Figure 7-30.
Figure 7-30 RRC connection establishment, network rejects RRC connection
UE UTRAN
RRC CONNECTION REQUEST
RRC CONNECTION REJECT
RRC connection release
The purpose of this procedure is to release all established signaling connections between the UE and
UTRAN due to a RRC connection. These include all signaling links and radio bearers.
If the RRC CONNECTION RELEASE message is in response to a CELL UPDATE message or
URA UPDATE message, then the SRNC should use the CCCH logical channel for the transmission
of this message. In all other cases the DCCH logical channel should be used.
RRC connection re-establishment
The purpose of RRC Connection Re-establishment procedure is for an UE to re-establish lost RRC connection.
This procedure is replaced by the Cell Update procuedure with cause RL Failure.
Transmission of UE Capability Information
The UE Capability Information procedure is initiated by the UE to convey the UE capability

to the UTRAN. The procedure may be initiated in response to the UE Capability Enquiry
procedure, or due to any capability update in the UE.
The capability information received from UE including: radio capability, security capability, and handover
capability, will be saved by the SRNC to 5 facilitate various functions and algorithm such as:handover to
different system, physical and transport channel re-configuration, chosen of security algorithm.
7-76 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RRC connection procedures
UE Capability Enquiry
The UE Capability Enquiry procedure is initiated by the UTRAN to request for the UTRAN capability
information (for example; radio capability, security algorithm, inter RAT handoff capability) from a UE. The
UE capabilities information may be first sent to the UTRAN upon the establishment of RRC connection.
After that, UTRAN may initiate this procedure anytime if the information is absent after RRC connection
is established (for example; during inter-RAT handoff to UMTS, or lack of security information).
68P02905W21-B 7-77
02-Jun-2004
RRC management procedures Chapter 7: Transmission systems
RRC management procedures

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Broadcast of system information
This procedure is used by the UTRAN to broadcast system information to the UE using system information
blocks (SIB). A system information block is used to group together system information elements of the
same nature. The system information is organized as a tree with the Master system information block as
the base. The master information block gives references and scheduling information to a number of system
information blocks in a cell. The system information blocks contain the actual system information.
Paging
The Paging procedure is to page an UE in the RRC Idle mode, CELL_PCH or URA_PCH state with
PAGING TYPE 1 message using the paging control channel (PCCH).
The paging procedure is not only limited to page UE at the request of the Core Network, but also
to be used by the RNC to page an UE for the following scenarios:
• To establish a signalling connection.
• To trigger UE to perform cell update procedure.
• To trigger UE to read updated system information.
For an UE that is in the CELL_DCH or CELL_FACH state, the CRNC will page it using UE
Dedicated Paging procedure by sending the PAGING TYPE 2 message to UE. The state of the
UE is determined by searching of UE Active Register in the RNC.
Initial direct transfer
The RRC INITIAL DIRECT TRANSFER message is sent by an UE on AM DCCH to establish

a signalling connection and to transport an initial higher layer (NAS) message. The UE uses this
procedure to request new services at a core network (CN). The UE wraps a NAS message inside the
RRC INITIAL DIRECT TRANSFER message with an indication of the CN domain this service is
connected to. If the UE is in the idle mode, it will perform the RRC Connection Establishment procedure
before sending the RRC Initial Direct Transfer message. If the UE is in CELL_PCH or URA_PCH
state, it will perform the Cell Update procedure before sending the message.
7-78 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RRC management procedures
Downlink direct transfer
The Downlink Direct Transfer procedure is used by a SRNC to forward higher layer (NAS)
messages from a CN to an UE. This procedure is initiated by the SRNC when it receives a RANAP
DIRECT TRANSFER message from the CN. The SRNC extracts the NAS message and send it
to the UE in a RRC DOWNLINK DIRECT TRANSFER message.
Uplink direct transfer
The RRC UPLINK DIRECT TRANSFER message is used by an UE to send subsequent higher layer (NAS)
messages to the CN via the SRNC when the RRC signalling connection has been established.
UE dedicated paging
The UE Dedicated Paging procedure is triggered by the CN to page a UE in the CELL_DCH or CELL_FACH
state. The RNC sends the PAGING TYPE 2 message to page UE. For the UE that is in the idle, CELL_PCH
or URA_PCH state, the UTRAN will page the UE using PAGING TYPE 1 message as specified in the Paging
procedure (not covered in this section). The state of the UE is determined after searching of UE Active Register.
Security mode control
The Security Mode Control procedure is used for two purposes:

1. To start, re-start, or stop ciphering for signalling link or radio bearers.
2. To start or modify integrity protection configuration for a signalling link.
Both procedures can be operated independently but supported by one same procedure.
The Security Mode Control procedure is triggered by the reception of RANAP Security
Mode Command received from the Core Network. After accepting the request, the RNC
initiates this procedure per Core Network request.
Signalling Connection Release
The Signalling Connection Release procedure is used to notify the UE that one of its signalling connections has
been released. This procedure is triggered when the SRNC receives an Iu RELEASE COMMAND message
with the IE Cause of "No remaining RAB" from a CN domain and the UE remains engaged in a signalling
connection to another CN domain. Thus this procedure does not initiate the release of RRC connection.
68P02905W21-B 7-79
02-Jun-2004
RRC management procedures Chapter 7: Transmission systems
Signalling Connection Release Request
The UE uses the Signalling Connection Release Request procedure to request the SRNC to release
one of its signalling connections. Upon receiving the request, the SRNC will send an Iu RELEASE
REQUEST to the CN domain with the IE Cause of "Release due to UE generated signalling
connection release". It is up to the CN domain to take the appropriate action. If the CN domain
decides to release the Iu signalling connection, it will initiate an Iu RELEASE COMMAND to the
RNC to release the Iu connection and the associated UTRAN resources.
Counter check
The Counter Check procedure is to check if the amount of transmitted and received data is identical between
UTRAN and UE. The procedure is intended for the un-ciphered radio bearers only. It’s only applicable to
AM or UM RLC in Release 99. The procedure is initiated by the RNC when the the elapsed Count-C
exceeds a check point since last checking. The data is compared with internal record. If the discrepancy
exceeds an acceptable level, the RNC will initiate the release of RRC connection.
Inter RAT handover information transfer
The inter RAT handover information transfer procedure is used by the UE to convey RRC
information needed for inter RAT handover to UTRAN.
7-80 68P02905W21-B
02-Jun-2004
Chapter
8
Cabinet description
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 8-1
02-Jun-2004
Chapter overview Chapter 8: Cabinet description
Chapter overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This chapter describes the hardware components in the UTRAN.
The topics included in this chapter are:

• "Node B cabinet" on page 8-3.
• "Node B outdoor enclosure" on page 8-7.
• "Node B outdoor ancillary enclosure" on page 8-9.
• "RNC5000 cabinet" on page 8-11.
8-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B cabinet
Node B cabinet
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This section gives an overview of the Node B cabinet. For further information refer to: 68P02905W29 Service
Manual: Motorola Node B and 68P02905W51 Installation and Configuration: Motorola Node B.
Node B cabinet for indoor and outdoor use
The Node B cabinet is suitable for indoor and outdoor use.

When used outdoors, the Node B cabinet needs to be placed inside an Node B outdoor enclosure.
This configuration is then referred to as a Node B Outdoor. Optionally, an ancillary enclosure
can also be used with a Node B Outdoor for additional batteries.
68P02905W21-B 8-3
02-Jun-2004
Node B cabinet Chapter 8: Cabinet description
Node B configurations
The Node B can be a standalone BTS or co-located with existing systems for use as expansion frames.
A single cabinet UMTS Node B supports the following standard configurations:
• Omni sector, 1 to 2 carrier, Rx diversity and no Tx diversity.
• Omni sector, 1 to 2 carrier, Rx diversity and Tx diversity.
• 2-sector, 1 to 2 carrier, Rx diversity and no Tx diversity.
• 2-sector, 1 to 2 carrier, Rx diversity and Tx diversity.
• 3-sector, 1 to 2 carrier, Rx diversity and no Tx diversity.
• 3-sector, 1 to 2 carrier, Rx diversity and Tx diversity.
• 4-sector, 1 carrier, no Tx diversity.
External views of the Node B cabinet
Figure 8-1 shows two examples of the Node B cabinet. The first is a cabinet fitted with a hood, and
the second a cabinet fitted with a stacking bracket and Rx filter basket.
8-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B cabinet
Figure 8-1 Closed cabinet with hood and closed cabinet with stacking bracket
Closed Cabinet with

Stacking Bracket
Closed Cabinet with Hood
External view of stacked cabinets
Figure 8-2 shows a view of stacked Node B indoor cabinets with front covers attached
to the stacking bracket and hood on top cabinet.
68P02905W21-B 8-5
02-Jun-2004
Node B cabinet Chapter 8: Cabinet description
Figure 8-2 View of stacked Node B indoor cabinets, showing stacking bracket, front cover and
hood.
8-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B outdoor enclosure
Node B outdoor enclosure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This section gives an overview of Node B Outdoor equipment (that is, Node B indoor
cabinet and Node B outdoor enclosure).
For further information refer to: 68P02905W35 Service Manual: Motorola Node B Outdoor and
68P02905W53 Installation and Configuration: Motorola Node B Outdoor Enclosure.
Overview of outdoor enclosure for Node B
The outdoor enclosure, Figure 8-3, operates from a nominal 200 V to 240 V, single phase
or three phase ac supply. Temperature control within the enclosure is provided by a Heat
Management System (HMS), located at the rear of the enclosure.
68P02905W21-B 8-7
02-Jun-2004
Node B outdoor enclosure Chapter 8: Cabinet description
Figure 8-3 External view of the Node B outdoor enclosure
8-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B outdoor ancillary enclosure
Node B outdoor ancillary enclosure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This section gives an overview of the optional Node B outdoor ancillary enclosure.
For further information refer to: 68P02905W35 Service Manual: Motorola Node B Outdoor and
68P02905W55 Installation and Configuration: Motorola Node B Outdoor Ancillary Enclosure.
Ancillary enclosure
The ancillary enclosure, Figure 8-4, is a customer option which is specifically intended to extend the
battery backup capability of the Node B outdoor enclosure (the main enclosure).
The ancillary enclosure can accommodate up to eight battery strings, with two strings per shelf.
68P02905W21-B 8-9
02-Jun-2004
Node B outdoor ancillary enclosure Chapter 8: Cabinet description
Based on typical load and temperature conditions, battery backup times that can be expected are:
• Thirty minutes per string for internal batteries.
• One hour per two string set for external batteries.
Figure 8-4 External view of the ancillary enclosure
8-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC5000 cabinet
RNC5000 cabinet
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the RNC5000
This section gives an overview of the RNC5000 cabinet. For further information refer to:
68P02905W09 Service Manual: Motorola RNC5000.
RNC architecture overview
The RNC5000, Figure 8-5, has a modular architecture designed for flexibility and scalability. Capacity
of the RNC can easily be increased by adding additional modules without system outage, thus making
the system very network friendly. This also allows the operator to grow the network in line with the
UMTS market development allowing for efficient management of capital investment.
68P02905W21-B 8-11
02-Jun-2004
RNC5000 cabinet Chapter 8: Cabinet description
Figure 8-5 External view of the RNC5000 cabinet
RNC modules
The UMTS RNC consists of three main subsystems illustrated in Figure 8-6.
Switch Unit
All the internal and external switching for the RNC is done at the Switch Unit. The user plane on Iu-PS is
also terminated on the Switch Unit. It provides high speed STM-1 (VC4) optical interfaces for Iu-PS,
Iu-CS, and Iur. It can also optionally terminate high speed STM-1 (VC4) Iub interface. Additionally
it supports STM-4 interfaces for Iu-CS and Iu-PS. The Switch Unit also provides the interfaces for
WINTerconnections to all other Units within the RNC as well as for the system clock.
System Unit
The System Unit performs layer 2 processing, call control functions, handover, frame processing and
Radio Resource Management within the RNC. It performs processing for the following control plane
protocols — RANAP, RNSAP, NBAP, ALCAP, and RRC. It also performs user plane processing which
includes RLC, MAC, and PDCP. It also performs macro diversity selection and combining. The System
Unit supports high speed STM-1 (VC12) and E1/T1 interfaces for Iub. The E1/T1 interfaces can be
8-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC5000 cabinet
used to optionally support Iu-PS, Iu-CS, and Iur. There can be up to 16 Systems Units per RNC. Each
System Unit provides a maximum voice capacity of 2,500 Erlangs and a maximum data capacity of 40
Mbit/s. The System Unit capacity can be dynamically allocated between voice and data.
OA&M Unit
There is one OA&M Unit per RNC which performs the following functions:
• Fault management.
• Load management.
• Performance management.
• Configuration management.
• Security management.
• Status monitoring.
68P02905W21-B 8-13
02-Jun-2004
RNC5000 cabinet Chapter 8: Cabinet description
It consists of a:
• Primary and back-up Back Administration Server (BAM).
• Primary and back-up LAN switches, which provide connection to the:

◦ Operations and Maintenance Centre - UMTS (OMC-U).
◦ Local Manager (LM).
◦ Alarm Terminal.
Figure 8-6 RNC5000 functional modules
RNC
Iu-PS
Iu-CS Switch OA&M LM/OMC-U
Iur Unit Unit
Iub
Iu-PS
Iu-CS System
Iur Unit
Iub
PHYSICAL interfaces:
STANDARD OPTIONAL
ti-UMTS-EP-00xxx-v01-ildoc-sw
8-14 68P02905W21-B
02-Jun-2004
Chapter
9
UTRAN features in USR 1.0
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 9-1
02-Jun-2004
Chapter overview Chapter 9: UTRAN features in USR 1.0
Chapter overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter lists and describes the features in UMTS release USR1.0.

• "USR1.0 Initial Base Load features" on page 9-3.
• "Node B configuration features" on page 9-9.
• "Signalling and terrestrial interfaces features" on page 9-12.
• "ATM backbone support features" on page 9-14.
• "RNC Shared Physical Interface features for Iu, Iur, Iub" on page 9-18.
• "UMTS air interface features" on page 9-21.
• "Radio connection, admission and resource management functions features" on page 9-27.
• "General support of RRM functions features" on page 9-29.
• "Power Control features" on page 9-37.
• "Handover features" on page 9-40.
• "USR1.0 optional features" on page 9-46.
• "Node B hardware support features" on page 9-48.
• "Radio resource management features" on page 9-52.
• "Inter RAT Handover features" on page 9-58.
• "Short Message Service (SMS) Point to Point (23066)" on page 9-61.
• "Location Based Services (LBS) - Cell ID (23113)" on page 9-63.
• "Call Trace (23115)" on page 9-65.
• "Overload Control features" on page 9-66.
9-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview USR1.0 Initial Base Load features
USR1.0 Initial Base Load features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of USR1.0 Initial Base Load features
The focus for all USR1.0 software is revenue generation through the provision of a solution that
enables an expanded data services portfolio for the operator. The USR1.0 initial program load (IPL)
is the UTRAN solution operating system. The majority of the base load content in the first release is
focussed on the system functionality to create an operational UTRAN. Motorola’s software, utilising
proven CDMA features, means Motorola can commit to delivering a stable commercial UMTS
network capable of generating new service revenues from delivery of USR1.0.
Motorola’s CDMA expertise strongly contributes to the functionality of the USR1.0 base load. In particular
the optimisation of intra-system handover and power control algorithms ensure the smooth operation and
efficient use of the installed network system. Motorola’s fine tuning of power control and handover in
CDMA networks strongly contributed to the achievement by June 1998 of CDMA networks achieving 99%
call completion rate. This type of learning curve carried over to our UMTS Network deployments will
ensure quality of service levels from day one that match existing GSM / GPRS based services.
The base load functionality also includes capacity enhancing features such as Receive Diversity. CDMA
based performance figures demonstrate Receive Diversity can increase cell erlang capacity x 3 compared to a
system without this capability. Also in the USR1.0 base load are important network service enablers such
as multiple QoS service support that ensure the network can differentiate the various service types.
The CDMA-based power control and intra system handover efficiency incorporated into the USR1.0 base
load ensures that maximum resource is obtained from the network infrastructure installed. This provides
two cost of ownership benefits; firstly the amount of infrastructure required to meet a required level of
coverage/capacity for early UMTS network areas is reduced thus saving on capex; secondly the efficient
utilisation of the network resource increases the level of operator revenue generated per $ of network
investment, reducing the associated cost of ownership of the infrastructure footprint.
Stable UMTS commercial systems protects Operators service reputation and brand value. The power control
and intra system handover functionality also ensure subscriber access to UMTS services is maximised
and that the service requested is successfully delivered to the user. Both key drivers of QOS.
68P02905W21-B 9-3
02-Jun-2004
USR1.0 Initial Base Load features Chapter 9: UTRAN features in USR 1.0
Node B configuration features
The features for Node B configuration are:

• Receive spatial diversity (23033)
• Support for 3rd party Mast Head Amplifiers (23039)
• Inverse Multiplxing for ATM (IMA) (23041)
9-4 68P02905W21-B
02-Jun-2004
Signalling and terrestrial interface features
The features for signalling and terrestrial interfaces are:

• For ATM backbone support:
◦ ATM backbone available (leasing of VP/VC) (23014)
◦ Line leasing: star configurations (23015)
◦ ATM transport (23047)
◦ Support of all defined QoS Classes (23048)
◦ Traffic shaping - (23049)
◦ CBR and VBR (23155/23156)
◦ AAL2 switching (23158)
◦ Cross-connect and routing (23159)
◦ ATM protection switching (23160)
• For RNC shared phsical interface for lu, lur, lub:

◦ Iu open interface (23050)
◦ Iu-CS at least 64 kbit/s (23051)
◦ lu-CS signalling by SS7 (23054)
◦ Iu-PS at least 384 kbit/s (23052)
◦ Iu-PS signalling by SS7 (23053)
◦ Iub interface (23056)
◦ Iur open interface (23058)
◦ Iur signalling by SS7 (23059)
68P02905W21-B 9-5
02-Jun-2004
UMTS air interface features
The features for the UMTS air interface are:

• Support of FDD mode air interface to 3GPP (23061)
• Support of all FDD transport channels except CPCH (23062)
• Air interface coding, multiplexing and inleaving supported (23063)
• Turbo Coding (23064)
• Convoltional coding (23065)
Radio connection, admission and resource management

functions:
The features for radio connection, admission and resource management are:
9-6 68P02905W21-B
02-Jun-2004
• For general support of RRM functions:

◦ Radio resource allocation and management (23067)
◦ Radio admission control (23068)
◦ UE capability handling (23071)
◦ Radio channel ciphering and deciphering (23075)
◦ Air interface signalling integrity protection (23076)
◦ System information broadcasting (23077)
◦ RAB admission controll (23080)
◦ CS RAB supported (23082)
◦ PS RAB supported (23083)
◦ Transport channel and RRC state selection and switching (23084)
◦ Code management (23085)
◦ Active UE register (23086)
◦ Cell update (23087)
◦ Paging (23088)
◦ Compressed mode (23089)
◦ Traffic volume management (23090)
◦ RAB establishment, reconfiguration and release (23091)
◦ RAB mapping (23092)
◦ Radio Interface Scheduling (23093)
◦ Radio Interface Synchronisation (23094)
◦ Time Alignment (23095)
◦ Frame Synchronisation (23097)
◦ RNC Based Radio Load Control (23120)
• For Power Control:

◦ Closed loop power control (23072)
◦ Outer loop power control (23073)
◦ Open loop power control (23074)
68P02905W21-B 9-7
02-Jun-2004
• For UMTS handovers:

◦ RNC soft handovers (23099)
◦ RNC softer handovers (23101)
◦ RNC hard handovers (23102)
◦ Intra sector hard handovers (23103)
◦ SRNS relocation (23107)
9-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B configuration features
Node B configuration features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Receive spatial diversity (23033)
Summary
Receive Diversity is a currently used, simple method of improving signal reception at
basestations with minimal impact. With this feature the benefits, improved performance and
lower interference, can be utilise with the UMTS system.
Standards
Compliant with 3GPP R99 standards.
Description
Receive spatial diversity allows a single signal transmitted by a mobile to be received simultaneously by a
main and diversity antenna at the Node B. This allows the main and diversity signals received on separate
antenna’s to be combined into a single signal at the receiver, which greatly improves performance.
Benefits
• Improves receiver performance.
• Increases channel capacity by lowering channel interference.
• RF expansion allows half as many antennas to be used at a multi-cabinet site.
Support for 3rd party mast head amplifiers (23039)
Summary
A Mast Head Amplifier (MHA), or Tower Top Amplifier (TTA), enables the Base Station to receive mobile
signals more clearly in a wider coverage area that they could otherwise achieve. A MHA is a low noise
amplifier that is mounted on the antenna. The MHA is used to improve the system noise figure and thus the
sensitivity of the Node B receiver by reducing the effect of feeder loss between the Node B and the antenna.
Standards
Fully compliant to 3GPP R99 specifications.
68P02905W21-B 9-9
02-Jun-2004
Node B configuration features Chapter 9: UTRAN features in USR 1.0
Description
Mast Head Amplifier move the first stage of active gain in the Node B receive chain to the top of
the antenna mast. This gives system performance gains by eliminating the Node B feeder loss,
with the system Noise Factor (NF) now being governed by that of the MHA (typically < 2 dB).
Depending on the characteristics and length of feeder the reverse link budget may be improved
by more than 3 dB. This link budget improvement can be equated directly into increased range,
assuming an uplink limitation, and hence fewer sites to cover a given area.
In USR1 Motorola support the use of third party MHAs with their own current injectors and power
supply/ alarm units. In future release it is proposed that a range of fully integrated solutions will
be offered, to meet different co-siting requirements, with current injectors and power supplies
integrated in to the Node B. Fully integrated alarming will also be proposed.
Benefits
There are two options for increasing profitability of an operation, firstly is of course increasing the revenue,
secondly is minimizing expenditure. Mast Head Amplifiers are able to address both of these, simultaneously.
• Cost of infrastructure - MHAs and co-siting are powerful options used to reduce the
cost of network infrastructure. Compensating for feeder loss between the base station
and the antenna allows normally lost power resource to be utilized to potentially
increase network coverage by increasing the size of the cell. As a result MHAs at a
base station can reduce the required number of base station sites.
• Time to market - In a world where it is getting increasingly difficult to get permission to build
new sites, an obvious ambition is to get the most out of existing sites through co-siting.
In addition to the extended range and capacity achieved with MHAs, MHAs can give a
reduction in the number of required sites, as well as much greater flexibility in locating
sites. A reduction in the number of base stations potentially shortens the time to launch,
enables a cost-effective network and therefore a competitive pricing strategy.
• Revenue - In UMTS, power is the shared resource; noise is the ’unwanted user’ on the
system. By reducing noise, it is possible to increase the amount of power that can be
used for chargeable services. Typically, the improved performance will initially be used
to maximize coverage area and as the traffic increases in the maturing system, the major
benefit from MHAs will be increased capacity. This improvement in capacity can be
traded for either an improved data transmission rate for existing users in a cell, or adding
more users in the cell. Both alternatives will lead to increased revenues. Coverage
enhancements and signal quality improvements have the combined effect of increasing
traffic volume and user satisfaction, hence increasing network revenue.
The network operator can deploy the system at an earlier date and at a reduced infrastructure
cost, allowing for a market leading position. This may lead to an increase in market share. The
time to break even for the network operator will be shortened.
9-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B configuration features
IMA (Inverse Multiplxing for ATM) (23041)
Summary
This feature provides an economic way of utilising n * E1 links in the UTRAN transmission network. IMA
provides for cell sequence integrity and resilience to link failure through graceful degradation.
Standards
This feature complies with the ATM Forum specification on Inverse Multiplexing for
ATM Version 1.1 af-phy-0086.001.
Description
IMA is used to describe the technique for round-robin scheduling and justifying ATM cells into n* E1
links. Reverse IMA refers to the process of extracting ATM cell from n* E1 links and restoring cell
sequence integrity. IMA enables a number of PDH links to be used in parallel. IMA is performed in
the Node Bs and reverse IMA is done higher in the network.Initially the number of E1s supported per
Node B will be 8 the IMA group will be limited to a maximum of eight E1s.
Benefits
The benefit of this technique is to provide higher capacities using highly available PDH links in an economic
way. IMA also provides a redundancy mechanism against E1 link failure by reallocating the bandwidth
according to the remaining links, thus, offering a graceful method of bandwidth degradation.
68P02905W21-B 9-11
02-Jun-2004
Signalling and terrestrial interfaces features Chapter 9: UTRAN features in USR 1.0
Signalling and terrestrial interfaces features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of signalling and terrestrial interfaces
There are several key differences between the GSM and UMTS radio subsystems related to the
cell site to switching centre transmission links. These impact both the design of the cell site
transmission system and its integration with any existing GSM deployment:
• High Capacity - much more capacity per cellsite is required than for GSM for several reasons:
◦ The higher capacity building blocks in UMTS (each radio carrier supports over
40 full rate voice calls compared with 8 in GSM). A typical cellsite will have 3
radio carriers supporting approximately 120 simultaneous voice calls.
◦ WCDMA soft-handover sends the same user data in parallel to several cellsites.
Soft handover figures in live deployments are notoriously difficult to predict,
but average factor of 1.4 is considered reasonable. Higher factors benefit the
spectrum efficiency (and thus reduce the number of cellsites required), but
trade-off the additional backhaul transmission capacity.
◦ The overheads of the UMTS user-plane frame protocols, ATM protocol stack, and
signalling all contribute to increasing the bandwidth on the access links.
• Non-deterministic - the capacity of WCDMA systems varies depending on a range of factors,

from the underlying service being used (voice, data, multimedia, and so on) to nearby cell
utilisation. Therefore, unlike GSM where the backhaul transmission capacity is directly
proportional to the number of radio carriers, backhaul usage is more difficult to predict.
• Packet Based - the inherent packet data format of the backhaul link provides flexibility to
adapt easily to any type of traffic (voice, data, video) and can be shared between carriers
and cellsites. Initial R99 deployments provide logical ATM point-to-point transport
between the cellsite and RNC; a later enhancement can migrate to IP.
• Multi-technology sites - it is likely that many UMTS licensees will also be GSM operators, and
will be reusing the same cellsites for both technologies. Since UMTS backhaul requirements
far exceed those for typical GSM cellsite backhaul, consideration must be given to sharing
links whilst protecting the integrity and performance of both systems.
An underlying SDH/PDH transmission infrastructure transports the logical ATM connections between the RNC
and cellsite. Standard Add-Drop Multiplexors (ADM) are used, so that bandwidth can be coarsely provisioned
over different physical layer with the benefit of protection switching and clock dissemination. This allows a
flexible migration approach to IP technologies on a practical evolution basis, as the standard interface matures.
9-12 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Signalling and terrestrial interfaces features
Signalling and terrestrial interface feature categories
Signalling and terrestrial interface features are divided into the following sections:
• ATM backbone support
• RNC shared phsical interface for lu, lur, lub.
These are described and listed in the following sections.
68P02905W21-B 9-13
02-Jun-2004
ATM backbone support features Chapter 9: UTRAN features in USR 1.0
ATM backbone support features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
There are several key differences between the GSM and UMTS radio subsystems related to the cellsite to
switching centre transmission links due to the amount of traffic that is to be carried by the backhaul. This
difference requires the implementation of an ATM link between network nodes. There are four different
ways of encoding data traffic into the standard ATM packets, called adaptation layers. The RNC supports
ATM adaptation layers AAL2 and AAL5 as defined by the 3GPP specifications with capability to switch
AAL2. In addition, the RNC can route an O&M traffic between the OMC and the Node B.
Standards
These features comply with 3GPP specifications.
Description
There are four different ways of encoding data traffic into the standard ATM packets, called adaptation layers,
and they are: AAL1, AAL2, AAL3/4 and AAL5. ATM networks typically use both AAL1 to carry circuit
switched traffic (such as voice) and AAL5 to carry data traffic (such as IP). The deployment of AAL2 scheme is
new and is extensively used in UMTS, and is capable of handling the characteristics of both voice/multimedia
traffic (such as simple voice calls) as well as data/multimedia traffic (such as WAP and Internet sessions). All
bearer traffic is sent from the Node B using AAL2, with signalling control and O&M traffic sent over AAL5.
The RNC can connect to an ATM backbone with VC/VP structure provided or to physical interfaces
(VC4/STM1) with an SDH transmission network compliant with ITU-T specification I.432.2,
‘Optical Interfaces for Equipment and Systems Relating to the SDH’. The RNC supports AAL2
and AAL5 as defined by the 3GPP specifications with capability to switch AAL2. In addition, the
RNC can route an O&M traffic between the OMC and the Node B.
The RNC architecture is designed to provide smooth and seamless migration to support the evolution of future
technologies. Motorola RNC is ready for IP transport as part of our end-to-end solution. To minimise
disruption to the network during the transition from ATM to IP backhaul, Motorola’s RNC provides
simultaneous support of both IP and ATM signalling interfaces. This will enable the operator to migrate
Node B across to IP in a controlled manner without introducing significant network downtime.
Operators have a number of options to increase the link availability to each Node B, and thus achieve
higher overall system availability. Microwave equipment can provide space diversity, redundant equipment
and error coding schemes. The use of microwave and optical SDH transmission allows the use of its
built-in ATM Protection System (G.783) that provides alternative routing when a link error is detected.
This feature must be enabled on each individual element within the ring itself.
9-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview ATM backbone support features
Benefits of the ATM backbone support features
These features reduce the overall cost, size, and management of the RNC, and improves
transmission backhaul for the following reasons:
• Using packet technologies enables resource sharing between connections.
• Provides both facility and line card protection.
• Provides a new level of ATM reliability, where downtime is significantly reduced, and
enables customization of the protection given to specific services or customers.
• Leasing reduces the operation expenditure for maintaining and setting up

the transmission equipment.
• Initial UMTS network rollout cost is minimised.
• Provides basic ATM functionality for support of Iu interfaces.
ATM backbone available (leasing of VP/VC) (23014)
ATM backbone leasing feature is available for interconnection between the UMTS Network
elements. This also provides the ability for the operator to lease VPs and VCs for connections
between the RNC and Core Network and also the RNC and Node Bs.
Line Leasing: star configurations (23015)
USR1.0 provides the capability for line leasing, star and hub configuration for connectivity to the following:
• Core Network and RNC .
• Between RNCs.
• Between RNCs and Node Bs.
68P02905W21-B 9-15
02-Jun-2004
ATM backbone support features Chapter 9: UTRAN features in USR 1.0
ATM transport (23047)
This feature provides basic ATM functionality, for example:

• VC/VP connection support.
• UNI/NNI interface support.
• AAL support (AAL2, AAL5, SAAL-UNI, SAAL-NNI).
Support of all Defined QoS Classes (23048)
Summary
This feature gives the capabilities of the UTRAN to administer and manage the QoS mechanism for all the
four QoS classes. These are conversational, streaming audio and video, interactive and background (also
called Best Effort). The importance of QoS management by the RAN and the Core network elements is to
ensure that the specified QoS class is maintained throughout the duration of the call/ information exchange
for the whole network. Supplying a reliable mechanism for delivering this capability provides quality of
service benefits to subscribers and new revenue streams for current GSM / GPRS operators.
Standards
Compliant to applicable 3GPP Release 99 standards.
Description
The users’ service requirements can be addressed through a single concept; End-to-End Quality of Service
(QoS). QoS essentially ensures that each user’s experience is satisfactory. To achieve this goal requires
multiple network elements (core network and radio access network) to provide sufficient performance
so that the QoS is maintained throughout the duration of the information exchange.
Whilst all services (applications) involve the transfer of information, the specifics of how the information
is exchanged vary from service to service. A quality of service profile is associated with each packet data
protocol (PDP) context, and is considered to be a single parameter with multiple data transfer attributes.
These attributes include delay, reliability, and peak throughput and guaranteed throughput. For example,
a conversational voice service requires stringent delay requirement whilst, at the same time, being able to
tolerate a relatively high information loss rate. In contrast a server access e-mail service places a much lower
One-way delay constraint, has no delay variation requirement but demands no information loss.
Fundamentally the support of a wide variety of services, with different characteristics, requires different
delivery mechanisms. This feature will enable the UTRAN to admit a call with different QoS requirement,
to ensure that available resources are not over committed, and policing and scheduling mechanisms are
used to enforce and optimise the volume of user data traffic handled by the system.
9-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview ATM backbone support features
Benefits
The benefits of the Support of all Defined QoS Classes feature are:
• The network operators will be able to offer a wider range of service with different QoS
requirements. In future releases network operators can maximise their investment returns
by charging premium rates for higher grades of service, i.e. increase ARPU. This feature
will enhance the end user experience and hence less susceptible to churn.
• Efficient bandwidth utilisation.
• When the QoS classes are reliably delivered to end users, perceptions of network service quality
will be high, encouraging increased use and less susceptibility to churn in the UMTS network.
Traffic shaping (23049)
This feature shapes outgoing ATM traffic to be conformant, so that it is not susceptible to policing by
the receiver of the ATM traffic. They allow increase in the admissible loads (input side) and to reduce
the jitters of outgoing flows. Traffic shaping to be performed at VPC and/or VCC.
CBR and VBR (23155/23156)
This feature sprovided support of Constraint Bit Rate (CBR) data and Varible Bit Rate (VBR).
AAL2 switching (23158)
The AAL2 switching feature is required (without processing the content data) for some channels
routed from Iub to Iur, and can be planned for optimising Iur routing.
Cross-connect and routing (23159)
This feature supports routing (without processing) of the Iur traffic through one RNC to another
RNC or Core Network. It will deal with cross-connect functions of ATM VP. The RNC will support
routing and concentration of the O&M links between OMC and Node B.
ATM protection switching (23160)
This feature (also called 1+1 Protection Switching) provides customisable, duplicate line
card protection where a service interruption can occur on either a port or an entire line card.
This is supported in accordance with SDH standard.
68P02905W21-B 9-17
02-Jun-2004
RNC Shared Physical Interface features for Iu, Iur, Iub Chapter 9: UTRAN features in USR 1.0
RNC Shared Physical Interface features for Iu, Iur,

Iub
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
Motorola’s RNC provides open Iu (Iu-CS, Iu-PS), Iur and Iub interfaces as specified in the 3GPP
specifications. The RNC is connected to the network using one or more 155 Mbit/s STM-1
connections with a maximum of 10 STM-1s per RNCS shelf. The same physical 155 Mbit/s
connection shares transmission to cellsites, other RNCs, the MSCu and GSN.
Standards
This feature complies with 3GPP Release 99 June 01.
Description
The support of logical interfaces on a single interface is achieved by mapping the VPs associated to the
different logical connections on a single physical interface. Motorola’s interface features are outlined below:
9-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview RNC Shared Physical Interface features for Iu, Iur, Iub
Benefits of RNC Shared Physical Interface features for Iu, Iur, Iub
The benefits of the RNC Shared Physical Interface features for Iu, Iur, Iub are:
• Allows easy installation and integration, reducing OPEX Motorola’s UTRAN
due to 3GPP compliant interfaces.
• Saves OPEX when interfacing the UTRAN with existing Core networks or
alternate UTRAN in multivendor environments.
• There are orders of magnitude fewer cables into the RNC for large installation.
• Greater system reliability because there are fewer connectors and cables.
• Increased availability if multiple physical interfaces are used to carry the logical interfaces.
Iu open interface (23050)
This feature supports the open Iu interface between the RNS and the Core Network allowing the
RNS to interface to differing Core Networks. Operators implementing UMTS networks can use
Motorola RNS to interface to their existing UMTS core networks.
Iu-CS at least 64 kbit/s (23051)
This feature supports data rates of at least 64 kbit/s over circuit switched Iu connections.
Iu-CS signalling by SS7 (23054)
This feature supports SS7 signalling over ATM, for control signalling across the Iu-CS interface.
Iu-PS at least 384 kbit/s (23052)
This fetaure supports data rates of at least 384 kbit/s on the Iu packet switched interface.
Reference documents include: TS 23.107 and the TS 25.41x series.
Iu-PS signalling by SS7 (23053)
This fetaure supports SS7 signalling over ATM, for control signalling across the Iu-PS interface.
68P02905W21-B 9-19
02-Jun-2004
RNC Shared Physical Interface features for Iu, Iur, Iub Chapter 9: UTRAN features in USR 1.0
Iub interface (23056)
This fetaure supports the Iub interface between the Node B and the RNC.
Iur open interface (23058)
This fetaure supports the Iur interface between one RNC and another RNC.
Iur signalling by SS7 (23059)
This feature allows the Iur to be used in support of SS7 signalling over ATM being used for Iu-CS.
9-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview UMTS air interface features
UMTS air interface features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Support of FDD mode air interface to 3GPP (23061)
Summary
The UMTS system allows simultaneous two-way communication (Full Duplex) between mobile user’s
equipment and base station (Node B) by providing two simultaneous but separate radio channels,
this feature compiles with 3GPP standards to allow this functionality
Standards
3GPP TS 25.211: Physical channels and mapping of transport channels onto physical
channels (FDD). Release 99.
3GPP TS 25.212: Multiplexing and channel coding (FDD). Release 99.
3GPP TS 25.213: Spreading and modulation (FDD). Release 99.
3GPP TS 25.214: Physical layer procedures (FDD). Release 99.
3GPP TS 25.215: Physical layer - Measurements (FDD). Release 99.
channels (TDD). Release 99.
3GPP TR 25.944: Channel coding and multiplexing examples. Release 99.
3GPP TS 25.301: Radio Interface Protocol Architecture. Release 99.
3GPP TS 25.302: Services provided by the physical layer. Release 99.
3GPP TS 25.101: UE Radio transmission and reception (FDD). Release 99.
3GPP TS 25.104: BTS Radio transmission and reception (FDD). Release 99.
Description
The UMTS system allows simultaneous two-way communication (Full Duplex) between mobile user’s
equipment and base station (Node B) by providing two simultaneous but separate radio channels.
The channel used to convey traffic from Node B to user’s equipment is called the downlink and
channel used to carry traffic from user’s equipment to a Node B is called the uplink. In Frequency
Division Duplex (FDD) the distinction between a pair of one-way, downlink and uplink communication
channels is carried out by fixed and known frequency separation.
Downlink frequency band: 2110 MHz - 2170 MHz.
Uplink frequency band: 1920 MHz - 1980 MHz.
68P02905W21-B 9-21
02-Jun-2004
UMTS air interface features Chapter 9: UTRAN features in USR 1.0
Benefits
The benefits of the Support of FDD mode air interface to 3GPP feature are:
• Higher robustness to system synchronization and timing inaccuracies than
Time Division Duplex (TDD) systems.
• Higher than TDD, system reliability especially for large coverage distance communication.
• Lower average production costs of radio network infrastructure and

user’s equipment using FDD.
• UMTS FDD operation mode characterize in average with higher transmission

quality and higher system capacity.
Support of all FDD transport channels except CPCH (23062)
Summary
In Support of the UMTS system simultaneous two-way communication (Full Duplex) between mobile user’s
equipment and base station, Transport channels are services offered by physical layer to the higher layers.
Standards
3GPP TS 25.201: Physical layer - general description, Release 99.
channels (FDD), Release 99.
3GPP TS 25.212: Multiplexing and channel coding (FDD), Release 99.
3GPP TS 25.213: Spreading and modulation (FDD), Release 99.
3GPP TS 25.214: Physical layer procedures (FDD), Release 99.
3GPP TS 25.222: Multiplexing and channel coding (TDD), Release 99.
3GPP TS 25.215: Physical layer - Measurements (FDD), Release 99.
3GPP TS 25.301: Radio Interface Protocol Architecture, Release 99.
3GPP TS 25.302: Services Provided by the Physical Layer, Release 99.
3GPP TS 25.401: UTRAN Overall Description, Release 99.
3GPP TS 25.133: Requirements for Support of Radio Resource Management (FDD), Release 99.
9-22 68P02905W21-B
02-Jun-2004
Description
A transport channel is defined by how and with what characteristics data is transferred over the air
interface. A general classification of transport channels is into two groups:
• Dedicated channels, using inherent addressing of user’s equipment (UE):
◦ DCH (Dedicated Channel), Uplink & Downlink.
• Common channels:
◦ BCH (Broadcast Channel), Downlink
◦ PCH (Paging Channel), Downlink
◦ FACH (Forward Access Channel), Downlink
◦ RACH (Random Access Channel), Uplink.
Benefits
Support of these Transport Channels is indispensable for system operation.
Air interface coding, multiplexing and interleaving supported

(23063)
Summary
Channel coding refers to the class of signal transformations, design to improve communication performance
by enabling the transmitted signals to increase robustness against effects of various radio communication
channel impairments, such as noise and/or fading. Usually, the goal of channel coding is to reduce
the probability of bit error at the cost of expending useful signal bandwidth.
Standards
Compliant to applicable 3GPP Release 99 standards:
3GPP TS 25.212: Multiplexing and channel coding (FDD), Release 99.
channels (FDD), Release 99.
3GPP TS 25.213: Spreading and modulation (FDD), Release 99.
3GPP TS 25.214: Physical layer procedures (FDD), Release 99.
3GPP TS 25.215: Physical layer - Measurements (FDD), Release 99.
3GPP TS 25.302: Services Provided by the Physical Layer, Release 99.
3GPP TS 25.402: Synchronisation in UTRAN, Stage 2, Release 99.
68P02905W21-B 9-23
02-Jun-2004
Description
The channel coding process introduces additional, redundant bits to the information stream increasing
correlation among consecutive bits in the coding data stream. Complementary process of channel decoding
takes advantage of that redundant information for the detection and correction of errors.
Interleaving the coded data stream before transmission and deinterleaving after reception
causes that burst of channel errors are spread out in the time and thus may be handled by
the channel decoder as if they were random errors.
The radio communication channel characterizes with mutually dependant signal transmission impairments
like slowly, comparing to one symbol duration time, varying fades, multipath transmission and others. All
these time-correlated effects result in statistical dependence among successive symbol transmissions. These
disturbances tend to cause errors that occur in bursts, instead of isolated events. Channel coding and decoding
procedures are vulnerable to burst errors result in degradation of error detection or correction performance.
Interleaving process separates data the codeword symbols in time by shuffling symbols of different codewords.
Multiplexing process maps onto and splits data between transport and physical channels.
Benefits
Support of that functionality is indispensable for system operation.
Turbo coding (23064)
Summary
Compliance with 3GPP over the air Turbo coding schemes, providing very high performance of error correction.
Standards
Description
Since 3G systems provides a multitude of services like two-way transmission of high quality audio, data,
video, fast Internet access, teleconferencing, the flexible data rate and service quality is mandatory.
The Turbo Code are applied for transmission error protection coding (channel coding) of services
characterized by data rate above 32 kbit/s and high quality of Bit Error Rate down to 10^-9.
This type of channel coding scheme provides very high performance of error correction capabilities due to
complex interactive decoding algorithm, much more efficient than traditional convolutional decoder.
Benefits
3GPP Standards require Convolutional Coding scheme for error-controlling coding.
9-24 68P02905W21-B
02-Jun-2004
Convolutional Coding (23065)
Summary
Compliance with 3GPP over the air convolutional coding schemes.
Standards
Description
Convolutional codes are utilised for error correction purposes.
In UMTS the convolutional codes are used to provide a cost-effective facility for error control
coding of the transmitting information over the radio channel from one end of the system at a data
rate up to 32 kbit/s, and at quality acceptable to the user at the other end.
The encoder for a convolutional code operates on the incoming message bit sequence, using the sliding
window method to generate a continuous stream of output bits with higher rate.
Benefits
3GPP Standards require Convolutional Coding scheme for error‘-controlling coding.
68P02905W21-B 9-25
02-Jun-2004
System Information Broadcasting (23077)
Summary
The UMTS system information is broadcasted over the air to inform the UE in a cell about the current system
configurations and facilitates the UE to access the system. Information Broadcast contains:
Standards
Description
• CN domain and UTRAN information
• Cell selection
• Common and shared physical channel configuration
• Measurement control
• UE positioning, and so on.

For USR1.0 release, the following SIP types are broadcast on the BCH: 1, 2, 3, 5, 7, 11, 12, and 18.
9-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Radio connection, admission and resource management functions features
Radio connection, admission and resource

management functions features
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
The deployment of UMTS systems requires significant investment from Network Operators. The
performance and capacity of such systems will be limited primarily by interference and code
availability within the WCDMA air interface. The Network Operator can achieve a significant
cost saving by maximising the potential of this interface and reducing the number of Node B sites
required. Once operational the Network Operator shall be equipped to demonstrate leadership in the
delivery of mobile data services, reducing churn and increasing revenue.
The complex interaction of a large number of functions is required to achieve optimal performance of
the radio environment. Motorola has significant expertise in delivering both GSM and CDMA access
networks and is ideally positioned to deliver this competitive advantage in UMTS.
Motorola supports the full range QoS classes, Radio Bearers and AMR voice rates defined within 3GPP. In
conjunction with Motorola’s intelligent algorithms, which address uplink and downlink radio environments
independently, this comprehensive feature set enables Motorola’s UTRAN to inter-operate with a all 3GPP
compliant terminals and Core Networks to provide a flexible and highly efficient radio solution.
Standards
This feature complies with 3GPP specifications.
Description
Radio Connection, Admission and Resource Management (RM) functions within the RNC are responsible for
managing the resource allocation to all calls connected to the RNS. Efficient management of this resource will
ensure that as many users as possible can be provided with the QoS required for the particular applications in
use at a given time. This section provides a summary of the key functions that contribute to this task.
68P02905W21-B 9-27
02-Jun-2004
Radio connection, admission and resource management functions features Chapter 9: UTRAN features in USR 1.0
Radio connection, admission and RM functions feature categories
The radio connection, admission and resource management functions features are
divided into the following categories:
• General support of RRM functions
• Power control
• Handovers
These are described in the following sections.
9-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview General support of RRM functions features
General support of RRM functions features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Radio resource allocation and management (23067)
This feature handles allocation of Channelisation codes and temporary UE identifiers based on input
from radio admission control function, radio access bearer establishment, reconfiguration and release
function, and radio network connection control function. For DCH transport channel, Channelisation
code is allocated. For common transport channels (RACH/FACH), an UE identifier is allocated, and the
Channelisation code of the relevant common transport channel is assigned. Scheduling users on the common
transport channels is the responsibility of NRT services scheduling, multiplexing, and retransmission
function. The radio resource allocation and management function also manages the scrambling codes
if necessary. Radio resource allocation and management function is located in the CRNC.
Radio Admission Control (23068)
The radio admission control feature is responsible for managing access to radio resources on a per
call basis. Note that a call is always associated with a single RAB.
The radio admission function is divided into two categories:
• Replying to requests from the SRNC RAB establish/reconf.
• A change of transport channel for Non Real Time (NRT) services.
Upon request from SRNC, the radio admission control function performs the following actions:
• Check that there is no overload alarm in the cell due to radio overload.
• Check if admission is possible with the requested parameters, according to the type
of service and to the type of transport channel requested. Radio admission control is
performed in both directions, and the request is established only if an acceptable level
of interference can be maintained within the network in both directions.
• Check if the required channel codes are available.
68P02905W21-B 9-29
02-Jun-2004
General support of RRM functions features Chapter 9: UTRAN features in USR 1.0
UE capability handling (23071)
In UMTS, UE capabilities signalled to the RNC allow the RNC to assign appropriate radio resources,
manage intra-system and inter-system handovers, security and other functions.
Examples of UE capabilities signalled to the RNC include:
• Support of IP header compression
• Data buffer capacity
• Physical radio parameters supported (for example, turbo coding, spreading factor)
• Support of UMTS multi-carrier and GSM (including if compressed mode

is required to scan other carriers).
The RNC uses this information for Radio Resource Management (for example, selection of best type of radio
transport channel) including if necessary handover of the user to a different system (for example, GSM).
Radio Channel Ciphering and Deciphering (23075)
The radio ciphering/deciphering provides the confidentiality of user data and signaling such that it cannot
be overheard on the radio access interface. The ciphering and deciphering process requires usage of
pre-negotiated algorithm and pre-agreeable ciphering key from UE and infrastructure.
Air interface signalling integrity protection (23076)
Integrity protection provides UE and UTRAN a capability to verify the radio signals transmitted over
the radio interface has not been modified in an unauthorised way since it was sent by the sending entity
and that the data origin of the signalling data received is indeed the one claimed. The integrity protection
process uses a pre-negotiated algorithm and key between UE and the serving network.
9-30 68P02905W21-B
02-Jun-2004
System Information Broadcasting (23077)
• CN domain and UTRAN information
• Cell selection
• Common and shared physical channel configuration
• Measurement control
• UE positioning, and so on.
For release USR1.0, the following SIB types are broadcast on the BCH: 1, 2, 3, 5, 7, 11, 12, 18.
RAB Admission Control (23080)
The RAB admission control manages the call admission process at each call setup to maintain the QoS
that network guaranty to deliver, and to prevent the performance of network from degrading.
The Call Admission applied to the call setup includes:
• At each new RAB request from CN
• At each RAB reconfiguration request from CN
• At each handover.
Prior to admitting the RAB request, the RAB Admission Control selects the type of logical and transport
channel to be used, request the RAB to RB mapping, check the congestion and overload condition, request
radio resources and terrestrial resources, etc. If all are accepted, the call can be admitted to the UTRAN.
CS RAB supported (23082)
The CS RAB support the following service:

• AMR speech service at 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s,
5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.
• Transparent data services at 28.8 kbit/s, 32 kbit/s, and 64 kbit/s.
• Non-transparent data services at 14.4 kbit/s, 28.8 kbit/s, 57.6 kbit/s.
UTRAN supports at least two RABs per UE.
68P02905W21-B 9-31
02-Jun-2004
PS RAB supported (23083)
The PS RAB supports the PS services with bit rates up to 384 kbit/s. The UTRAN
supports at least 2 RABs per UE.
Transport Channel and RRC State Selection and Switching

(23084)
Transport channel and RRC state selection and switching feature is to select and switch transport channels
and switch UE states based on UE activity to maximally optimise the radio resource usage.
The transport channel selection function is responsible for selecting transport channels for radio access
bearers between dedicated and common/shared transport channels based on the radio access bearer
attribute values, particularly the traffic class information received by the SRNC from the core network
for the radio access bearer under consideration and taking into account of UE capability.
Transport channel switching function is charged with switching transport channels for reconfigured radio access
bearers, if necessary, per the new radio access bearer attribute values. It can also trigger a change of transport
channel for a given radio access bearer which is not being reconfigured, based on measurement reports from
the traffic volume measurement function. The transport channel switching function is located in the SRNC.
The RRC State Switching Function resides in the SRNC. It is in charge of switching an UE from one state to
another due to low activity except for the transition between CELL_DCH and CELL_FACH.
Code Management (23085)
The Channelisation codes are used to distinguish the UEs within one cell. This feature is responsible
for allocating Channelisation codes for downlink DCH transport channels and providing the
spreading factors for uplink DCHs to be used by UE and Node B to calculate the exact uplink
Channelisation codes. If codes are available, allocations are made.
Active UE register (23086)
Active UE register is maintained by the UTRAN for a UE in the connected mode to store the UE context.
The information may be use to facilitate the paging procedure. The register may contain UE information
such as UE identification, current state, cell ID or URA ID where UE registered, and so on.
9-32 68P02905W21-B
02-Jun-2004
Cell Update (23078)
The Cell Update function allows the UE to notify the UTRAN of its current cell and the
status when one of the following conditions occurs:
• Uplink data transmission
• Paging response
• Re-entering service area
• Radio link failure
• RLC unrecoverable error
• Cell reselection
• Periodic cell update.
Paging (23088)
The Paging procedure allows both Core Network(s) and UTRAN to page and UE which is roaming
in the UTRAN. The CN originates paging procedure for a terminated call. The UTRAN originates
paging for various reasons, for example, to notify UE of updated system information, to inform
UE to perform cell update, or to deliver downlink packet data, and so on.
Compressed Mode (23089)
Compressed mode consists of providing a gap in transmission on downlink to allow a dual mode
Mobile with single receiver capability to scan other carrier frequencies for inter Radio Access
Technology (between UMTS and GSM/GPRS) hard handover purposes.
To support monitoring by UE of cells on other FDD frequencies, and other radio access technologies, the
Serving RNC performs the following functions prior to commanding the UE to enter the compressed mode:
• Check UE capability.
• Provide UE and the Node B with compressed mode configuration.
• Command UE and the Node B to take the measurement of radio environment.
• Command UE and the Node B to enter compressed mode.
Handover from UMTS to GSM will be of particular useful in the early phases of UMTS deployment. UMTS
to GSM handovers allows for calls to continue as mobiles move out of the UMTS coverage.
It is possible that some governments may mandate that new entrants to the UMTS market have a right to roam
on the GSM network of existing operators. Clearly here inter-mode roaming will be very desirable.
68P02905W21-B 9-33
02-Jun-2004
Traffic Volume Measurement (23090)
The traffic volume measurement is to measure the traffic load on the common transport
channel as well as on a UE basis.
Measurement on the common transport channel allows UTRAN to control the call admitted
to the common channel based on the current load.
Measurement on UE basis allows UTRAN to select an appropriate type of transport channel for a requested
services, or to switch bearers between transport channels to optimize the usage of radio resources.
UE basis measurement is instructed by the UTRAN via a request to UE or broadcasting.
RAB Establishment, Reconfiguration, and Release (23091)
The RAB Establishment, Reconfiguration, and Release feature is to set up the radio bearers in response to a
request for a radio access bearer received from the Core Network via Iu interface. The setup includes
deriving RLC, MAC, transport channel, and physical channel parameters, and communicating to the
core network and the network node within UTRAN (DRNC/CRNC, and Node B).
RAB Mapping (23092)
The RAB Mapping feature is to map a requested Radio Access Bearer (RAB) service
attributes to the Radio Bearer (RB) service parameters.
There are four QoS classes: conversational, streaming, interactive and background. Full range
of radio bearer configurations and AMR voice rates defined by 3GPP are supported. Based on
the RAB profile: for example; data rate, delay sensitivity, regularity of data transfer, the RAB
Mapping function will configure the most appropriate Radio Bearer.
Radio Interface Scheduling (23093)
Description
This feature enables the network operator to reconfigure the bearer every 10 ms and offers an efficient
way to support bursty non-realtime traffic over a range of rates. Scheduling and multiplexing functions
are located in the CRNC. The scheduling functions are divided into two categories:
• Dynamic scheduling on downlink, either on FACH or on DCH.
• Dynamic scheduling on uplink, either on RACH or on DCH.
Scheduling permits tight power management, priority and QoS handling, and statistical
multiplexing onto the radio pipe.
9-34 68P02905W21-B
02-Jun-2004
Benefits
The benefits of this feature are:
• Radio resources are utilised efficiently by reconfiguring it every 10ms to those
users who need the resources most.
• Enhanced end user experience.
• Higher peak rate: more 384 kbit/s channels can be allocated.
• Packet call completed more quickly.
• Very high mean data rate is possible if loading is low.
• Higher call admission rate - more new calls can be admitted.
• Enhanced Priority Handling can be offered.
• Differentiated QoS treatment to high priority calls.
Radio Interface Synchronisation (23094)
Radio interface synchronisation involves the management of the Td offset parameter associated with each
radio link for diversity reception at the UE to ensure the reception signal at the UE with high quality. The
feature is to ensures that radio frames from diverse links arrive at the UE at approximately the same time.
The UTRAN only selects a Td offset at the time of establishment of the first radio link. For radio
links that are added later (or possibly coincident with the initial radio link establishment) for the
purpose of soft handover, the Td value is effectively determined by the UE.
Time Alignment (23095)
Time alignment procedure feature is used to manage the transmission delay of userplane data between
Node B and RNC and reduce delay between RNC and core network. It includes two parts:
• Time alignment between RNC and Node B
• Time alignment between RNC and Core Network
The purpose of time alignment between RNC and Node B is to manage the transmission delay of userplane
data through the UTRAN, maintain the continuity of data flow, and observe buffering constraints at Node B.
Time alignment between RNC and CN is to reduce delay by synchronising the transport of data
frames across Iu with the timing related to DCH in the UTRAN. For non-real-time services, a
time alignment procedure with the Core Network is not required.
68P02905W21-B 9-35
02-Jun-2004
Frame Synchronisation (23097)
The frame synchronisation feature (also called Transport Channel Synchronisation in 3GPP
TS 25.402) is used to achieve high quality macro-diversity for dedicated transport channel
reception and support the requirements related to ciphering by using CFN (connection frame
number) as the common reference between the UE and UTRAN.
The feature ensures that the contents of the radio frames that arrive together at the UE
contain the same encoded user data delivering.
RNC Based Radio Load Control (23120)
Description
The radio load control functionality maintains quality of service in occurrence of the radio network
overloaded conditions. The feature protects radio network from introducing excessive RF interferences
in UL and DL direction in case of high traffic intensity in the system.
Two main effects may indeed occur in such events:
• In uplink, mobiles may increase their transmitter power to overcome the increase of interference,
thus increasing overall level of interference, which results in degradation of services quality.
• On downlink the maximum DL transmitter power available in the Node B may be

reached, so that radio quality cannot be maintained for some mobiles or NodeB
power amplifiers my be overdriven result in cell outages.
Benefits
• Selection of the appropriate radio transport channel and management of interference are key
factors in delivering the requisite QoS to the user as well as maximising the throughput
of the air interface. With Motorola’s intelligent algorithms this process is optimised
resulting in increased capacity and improved call performance.
• Better utilization of radio resources and service continuity (handover to other carriers
or systems, for eample, GSM) help to reduce OPEX and CAPEX.
• Improve receiving signal quality, availability and capacity for UE.
• To support frame synchronization and time alignment features to gain high quality
macro-diversity reception and reduce transmission delay.
• Motorola’s solution will inter-work with all 3GPP compliant terminals and core networks
and shall enable the network operator to introduce new services with ease.
9-36 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Power Control features
Power Control features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
Power control is extremely important for the efficient resource utilisation of an UMTS (W-CDMA)
network. This is because of the direct relationship between the power outputs from each
mobile and the level of interference generated in the radio access network. The higher the
interference level, caused by unnecessarily high transmit power from mobiles, the smaller the
subscriber coverage and capacity of the UMTS network will be.
Previous experience in CDMA is critical for effective power control which balances two opposing goals
when controlling the transmit power of the mobile to the network. These are maximising call quality
(Goal 1), put simply the higher the mobile transmit power the better the call quality, while minimising
the interference level (Goal 2) which is increased by mobiles transmitting at higher power.
Motorola has carried out extensive research in the area of power control. The main focus has been on
Outer Loop Power Control. This is the element of power control that manages the output level of all the
mobiles and is a critical consideration when setting power control parameters. Due to the impact this has
on the available capacity of the network (as discussed above) Motorola CDMA expertise can provide a
considerable network loading advantage to an operator by optimising power control algorithms.
Standards
Compliant with 3GPP R99 standards.
Description
Closed loop power control consists of two loops. The inner power control loop, or fast power control
loop, simply tries to maintain the received Eb/Io ratio (signal to total interference ratio) at a given
level, or target. The target is set by the outer power control loop. Different target Eb/Io ratios are
appropriate for different bearer services and even for the same bearer service as a function of propagation
conditions. The outer loop is quality driven and seeks to set the Eb/Io ratio at the minimum value
possible to achieve the desired QoS associated with a given connection.
The combination of inner and outer loop power control together try to set the Eb/Io for each radio bearer at the
minimum level to achieve the desired QoS, usually defined in terms of FER. In WCDMA this power control
is essential to overcome the so-called near-far problem. If power control were not used then mobiles in close
proximity to the Node B would swamp mobiles located further from the base site. Power control ensures
that, irrespective of physical distance from the base site, each mobile just transmits enough power to meet its
requirements. This minimises both intra and inter cell interference and hence maximises capacity in the system.
68P02905W21-B 9-37
02-Jun-2004
Power Control features Chapter 9: UTRAN features in USR 1.0
Different radio bearers have quite different Eb/Io characteristics and even for a given bearer performance
can vary significantly as a function of propagation environment, for example multipath profile and
mobile speed. The outer loop seeks to autonomously set the minimum Eb/Io for each connection
in response to the prevailing propagation conditions, the details of the outer loop algorithm are not
specified by 3GPP and each vendor must design their own outer loop.
Benefits of the power control features
The benefits of the power control features are as follows:

• Motorola has carried out extensive research in the area of power control, in particular with
reference to outer loop power control where there is considerable room for differentiation
between vendors in terms of the ability to set the appropriate outer loop target as a function
of propagation conditions. Motorola has developed efficient solutions for all classes of
bearers, which in turn maximize radio resource utilization for the operator.
• Motorola can enhance the effectiveness of outer loop power control algorithms through
our capability to identify the most favourable parameters, as a function of propagation
conditions, during planning and optimisation of UMTS type networks.
• The improved service access and call performance provided by Motorola’s power control
efficiency will have a very positive impact on early UMTS subscriber QOS perceptions. QOS
is a key driver for maximising service utilisation and minimising subscriber churn.
• Motorola’s fine tuning of power control and handover in our CDMA networks
strongly contributed to our achievement by June 1998 of CDMA networks achieving
99% call completion rate. Our UMTS algorithm optimisation model is validated
by in field CDMA testing started in 1994.
Closed loop power control (23072)
Closed loop power control reduces interference in the system by maintaining the quality of UE-UTRAN
communication (trhat is, a radio link) as close as possible to the minimum quality required for the type of
service requested by the user. Closed loop power control is used for physical layer channels that support
dedicated transport channels (DCH). The power control loop is closed since the receiver of the radio
signal communicates commands back to the sender to adjust the transmitted power.
Closed loop power control consists of two parts; an inner loop and an outer loop in both the
uplink and the downlink (see Outer loop power control (23073)).
The inner loop is sometimes referred to as fast power control and is an essential part of a CDMA-based
system. This is especially true in the uplink since a single overpowered mobile could block an entire
cell. The inner loop responds to fast variations in propagation characteristics of the radio link (for
example, fast fading at slow or medium speeds) as well as rapidly changing interference conditions
and is where the decision is made to issue the commands to power up or down. The inner loop
is fast because it operates on a power-control-command per slot basis. This results in a 1500 Hz
command rate. The commands are passed at the physical layer (layer 1).
9-38 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Power Control features
Outer loop power control (23073)
There are two types of outer loop power control; downlink outer loop power control
and uplink outer loop power control.
The downlink outer loop power control adjusts the SIR target the UE uses for comparison to the estimated
SIR to determine the power control command to issue to the Node B. The downlink outer loop resides in the
UE and is totally under the control of the UE. The UTRAN, however, provides a block error rate (BLER)
target on a transport channel basis that the UE will use to determine the correct target SIR.
The uplink outer loop power control algorithm is performed at the SRNC and passes down
an updated SIR_target to each serving Node B at integral multiple of (10 ms) radio frame
periods. The UL outer loop threshold SIR_target will be calculated by SRNC based on UL
frame quality information (CRCI) and BER metrics measured on serving Node Bs. CRCI=0
indicates good block received; CRCI=1 indicates a block erasure.
Open loop power control (23074)
Open loop power control is to allow the UE to intelligently set the proper power level it uses to transmit
information on the packet random access channel (PRACH) under the assistance of UTRAN.
Although the procedure is principally the responsibility of the UE, the requirement on the UTRAN is to provide
assistance information to help the UE determine what power level to use. The mobile measures the received
power for the primary CPICH and creates a path loss estimate. The UE then determines the requisite power
level to transmit in order for the Node B to receive the signal level equal to the constant plus interference. The
algorithm in the UE is defined so that if the UE does not succeed in accessing the system using the initial power
level estimate, it will retry at an increased power level. Only open loop power control is used for the PRACH.
68P02905W21-B 9-39
02-Jun-2004
Handover features Chapter 9: UTRAN features in USR 1.0
Handover features
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
Intra-system handover is critical in any wireless network as efficient handover ensures calls are
successfully maintained and completed as subscribers move around during the duration of the call.
This contributes to revenue generation and quality of service performance.
As UMTS is a W-CDMA technology, lessons from other CDMA technologies can be applied. For Example,
in CDMA effective management of handover timing is critical to maximising network capacity and coverage
resources from infrastructure. Through our CDMA network deployments Motorola has identified issues
such as handover times and pilot dominance and we can apply this experience and knowledge to optimise
these handover parameters reduce unnecessary handover operations, within UMTS.
UMTS systems will require a variety of intra and inter mode handovers. This section aims to summarise
and describe the main types of handover Motorola offers within USR1.
Standards
Description of UMTS to UMTS handovers
CDMA is commonly explained by the cocktail party image, where groups of people of different languages
can communicate simultaneously, despite the surrounding noise. For a group of people speaking the same
language, the rest of the people in the room are perceived as noise. Knowing the language they are talking
allows them to filter out this noise and understand each other. If someone records the noise, and knows
different languages, he/she will be able, by playing the tape several times, to extract the various conversations
taking place in the various languages. With sufficient processing capacity (for example, in the cocktail party
image, with several listeners to the tape), all conversations can be extracted simultaneously.
However, CDMA requires in particular a complex and very accurate power control, which is a key factor
for the system capacity and proper operation. The cocktail party image again can help understanding the
problem: if somebody starts talking louder, he/she will disturb the other conversations. To be still able to
understand each other, the other groups will also start talking louder. If too many people are present (or if too
many people talk too loudly), it becomes impossible to understand anything. The power control problem
implies the need to sometimes control the radio path between a mobile station and the fixed network from
more than one place, as will be explained below. This feature corresponds to the soft handover concept.
In a CDMA cellular system, a key feature is the reuse factor of 1, that is the reuse of the same
frequency in all cells. This means that when an active Mobile located in a cell, say cell 1 enters
another cell, say cell 2, it interferes more and more with the mobiles in cell 2. Entering cell 2 also
means leaving cell 1. This implies that the Node B serving cell 1 will tend to increase the power of
the Mobile to a level more and more disturbing for the traffic of cell 2. Therefore, it is necessary to
9-40 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Handover features
control the Mobile power from both cells. The Mobile will receive power control information from
Node B serving cell 1 and from Node B serving cell 2, and always choose the lowest one, which
corresponds to the power needed in at least one of the cells to be received properly.
Soft handover
This then leads to the concept of soft and softer handovers. A soft handover is where the RNC performs
splitting of downlink user data and signalling and selection of uplink user data and signalling. In
other words in a soft handover, the mobile is linked to several cells supported by different Node Bs.
Soft handover algorithm is unique to CDMA technology and critical to achieve commercial quality
performance. In soft handover the mobile starts communication with a new Node B on a same frequency,
or sector of the same site (softer handover). For this reason soft handover allows easily the provision
of macro-diversity transmission. Motorola has performed extensive system simulations in lab as well
as field testing to confirm predicted handover performance and system benefits.
A softer handover is where the Node B performs splitting of downlink user data and signalling and combining
of uplink user data and signalling. In other words, two or more cells of the same Node B are serving the mobile.
Based on IS-95 data, the amount of soft handover to be expected is quite significant; about 30% to
40% of mobiles are reported to be in a soft handover situation at any one time.
Hard handover
There is a third and final category of W-CDMA handover, the hard handover. This is a category of
handover procedures where all the old radio links in the mobile are abandoned before the new radio
links are activated, for example in the case of handovers between frequencies.
Benefits of Motorola’s Handover solutions
• The concept of soft and softer handovers in W-CDMA networks allows power control
algorithms to minimise uplink and downlink transmit power. This reduces system interference,
thereby increasing system capacity (and also increasing mobile battery life).
• Efficient handover ensures operators do not lose revenue by subscribers suffering dropped
calls. Irritated users may decide not to continue the call once it has been dropped, particularly if
this occurs several times in quick succession. Alternatively if near to a fixed line phone the user
may continue the call on this service. Either way the mobile operator loses valuable revenue.
• In a UMTS (W-CDMA) network there is a strong link between initiating Handovers

at the optimum time and obtaining maximum utilisation of coverage and capacity
resources. This refers again to the impact in UMTS of mobiles transmitting at
unnecessarily high power levels, increasing interference and therefore reducing
the coverage and capacity capability of the network.
• In particular Motorola expertise in CDMA based soft and softer handover will ensure
that mobiles are communicating with the optimum Node B radio in its contact range in
terms of a stable call being maintained without the mobile having to use high levels
of power to do so, thus minimising overall interference.
68P02905W21-B 9-41
02-Jun-2004
• In W-CDMA all mobiles transmit on the same frequency therefore a mobile can be in contact
with several Node Bs simultaneously. Motorola can optimise handover to ensure that
when a mobile is in simultaneous contact with several Node Bs, that the transmit link is
disconnected to any Node B in its contact range, that requires the mobile to use excessive
power levels. This approach also avoids assigning considerable BTS resources to just one
mobile to ensure BTS resource is spread over an effective number of subscribers.
• Efficient handover ensures calls are maintained and completed successfully, a

major contributor to subscriber customer satisfaction.
• Motorola’s fine tuning of power control and handover in our CDMA networks
strongly contributed to our achievement by June 1998 of CDMA networks achieving
99% call completion rate. Our UMTS algorithm optimisation model is validated
by in field CDMA testing started in 1994.
RNC Soft handovers (23099)
Description
The soft handover is the feature that allows to a given UE to be connected at the same time to more than one
Node B in order to improve the radio link conditions due to the macro diversity combining of the several
radio links that the UE may have established. It is also the process that needs to be followed to change
the radio connection that a given UE may have with a Node B to another Node B, in such a way that the
connection is never broken during the movement of the UE. To do so, the RNC shall perform splitting of
downlink user and signalling data and transmit it to different Node Bs connected to it or over the Iur interface
if the Node B is connected to a neighbour RNC. In addition, the RNC shall perform combining/selection
of uplink user data and signalling received from radio links received at different Node Bs connected to
that specific RNC or over Iur interface if the Node Bs are connected to a neighbour RNC.
Benefits
The benefits of this fetaure are:
• Allows the maintenance of the Quality of Service requested by the Core Network by
performing a connection to a different Node B when the radio conditions are not optimal.
• Increases significantly the performance of the Air Interface through the combining process
from the different radio links received at the antenna (macro diversity gain).
RNC Softer Handovers (23101)
Description
The UMTS softer handover is the feature that allows to a given UE to be connected at the same time to more
than one sector within the same Node B in order to improve the radio link conditions due to the macrodiversity
combining of the several radio links that the UE may have established. It is also the process that needs to be
followed to change the radio connection that a given UE may have with a sector to another sector of the
same Node B in such a way that the connection is never broken during the movement of the UE.
9-42 68P02905W21-B
02-Jun-2004
To do so, the Node B shall perform local splitting of downlink user and signalling data and local combining of
uplink user data and signalling transmitted to/received from radio links from different sectors of the same site.
Benefits
The benefits of this fetaure are:
• Allows the movement of the UE within the vicinity of a given site without transmission gaps.
• Allows the maintenance of the Quality of Service requested by the Core Network by
performing a connection to a different Node B when the radio conditions are not optimal.
• Increases significantly the performance of the Air Interface through the combining process
from the different radio links received at the antenna (macrodiversity gain).
RNC hard Handovers (23102)
Description
The hard handover is the feature that allows to a given UE to change the carrier of the radio link connection.
To do so, the RNC shall trigger for a given UE a handover from one carrier to a different one, both used
within its set of Node Bs if the handover is performed within the RNC (intra-RNC). If the hard handover
is performed inter RNC, the Node B to connect to, belonging to the adjacent RNC, works at a different
working frequency. This means a change in the frequency at which the UE is communicating, with a
transmission gap interval to allow for the equipment to change the working frequency. This handover type
is triggered when there are no more sites with the same frequency to connect to, or when the radio link
conditions would significantly improve, based on the inter-frequency measurements. These inter-frequency
measurements are obtained during the transmission gaps of the Compressed Mode.
Benefits
• Maintains the connection for a given UE when the radio link conditions for a given
frequency are not optimal based on interfrequency measurements.
• Increase of system capacity due to the implementation of two or more frequency layers
in the deployment area, ensuring as well a complete coverage.
Intra Sector Hard Handovers (23103)
Description
The intra sector hard handover is the feature that allows to a given UE to change the carrier of the radio link
correction within the same Node B sector. Accordingly, the Node B needs to support several carriers. The
RNC shall trigger for a given UE a handover from one carrier to a different one both used in a given sector
of a Node B connected to it. This means a change in the frequency at which the UE is communicating,
with a transmission gap interval to allow for the equipment to change the working frequency. This
68P02905W21-B 9-43
02-Jun-2004
handover type is triggered when there are no more sites with the same frequency to connect to, or when the
radio link conditions would significantly improve, based on the inter-frequency measurements. These
inter-frequency measurements are obtained during the transmission gaps of the Compressed Mode.
Benefits
• Maintains the connection for a given UE when the radio conditions for a given frequency
are not optimal based on interfrequency measurements.
• Increase of system capacity due to the implementation of two or more

frequency layers in the deployment area.
SRNS Relocation (23107)
Summary
There is one Serving RNS for each mobile that has a connection to UTRAN. The serving RNS is in
charge of the radio connection between a mobile and the UTRAN and terminates the Iu for this mobile.
This features enables the moving of the serving RNS functionality from one RNC to another RNC. The
process is triggered by cell update, or timers and is initiated by the source RNC. This functionality
involves the core network and the UTRAN. The procedure is unique to UMTS. The key benefit of the
feature is that it eliminates inefficient routing of user data stream over the Iur interface (between RNC
and RNC) and this allows more efficient use of network resources by operators.
Standards
Description
The SRNS (Serving Radio Network Subsystem) refers to the RNS where the RNC that is performing the
frame protocol termination is located. This means that this is the RNC that is providing service to the UE.
Any other RNC (Drift RNC) the UE may be connected to will route the data streams to the Serving RNC.
The SRNS relocation procedure consists of changing the Serving RNC of a given UE that has a connection
with a Drift RNC. This procedure transfers all the UE context (RAB parameters, etc) from the SRNC to the
DRNC (Drift), changing the latter its role, becoming the Serving RNC for that UE. This procedure involves
both the Core Network and the UTRAN. Seen from the CN, it consists in changing the Iu interface.
The SRNS Relocation procedure does not modify the radio resources already involved in the call,
the same radio resources should be used before and after the procedure.
This procedure is always decided and initiated by the source SRNC and implies signalling
over the Iur interface between SRNC and DRNC.
9-44 68P02905W21-B
02-Jun-2004
Benefits
• This feature optimises the use of the UTRAN, by optimising inefficient routing of
user data streams in the UTRAN. The traffic between SRNC and DRNC that is sent
over the Iur is avoided by performing a SRNS relocation.
• The performance of the UTRAN is also improved, since after a SRNS relocation performance
indicators like the processing delay (after the procedure the traffic only needs to go through
one RNC) and therefore the average transfer delay are significantly improved.
• The capacity of the network is also increased. The RNC does not have to route user
traffic to be combined at another RNC (or route traffic to its Radio Network Subsystem
coming from another RNC) and the processing load of the RNC decreases as well.
This provides more capacity for the same capital expenditure.
68P02905W21-B 9-45
02-Jun-2004
USR1.0 optional features Chapter 9: UTRAN features in USR 1.0
USR1.0 optional features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of USR1.0 optional features
USR1.0 allows a faster time to an operational, revenue generating network. Motorola’s CDMA heritage
enables us to achieve commercially operational networks in optimum time, with 100% parameters optimised
at launch - 90% pre optimised before deployment, final 10% in the field with tools and planning services.
Motorola’s efficient 3G - 2G Handover features ensure service is maintained in a suitable format on user
exit of an UMTS area and with Motorola’s GSM GSR 6 GSM/UMTS interworking features, ensures
UMTS services are offered when a user enters an UMTS area. The Pooled Resource feature enables
increased network capacity in hotspots to ensure subscriber access to services maintained even in busy
traffic periods. These coverage features and with the support of R99 QoS and multiple RABs means that
initial operation networks maintain and enhance operators services to their consumers.
Motorola’s USR1.0 software not only allows the faster time to revenue, but does it with features aimed at
minimising operators cost of ownership. The Pooled Resource feature such Trunked Linear power amplifiers
and pooled Wide band Digital modems provides an inherent soft fail capability with no need to purchase
additional redundant hardware. For example In a non trunked LPA configuration all cell coverage would be
lost in the event of an LPA failure. This Pooled resource also provides flexible coverage / capacity meaning
operators do not have to design each cell for highest traffic load. This in conjunction with the ability to install
six sector base stations can improve coverage and capacity significantly. Implementing the Transmit Diversity
feature can also increase the capacity of the downlink by up to 50% or coverage by up to 30%.
Standard interfaces between O&M systems including the industry leading Corba interface from the OMC-U to
the NMC simplifies the network management process and associated Opex costs. OMC offline provisioning
means new software and subscriber service uploads are right first time on the live network. Both these OMC
feature positively impacts Opex reductions as less engineering and management spent on correcting errors.
Maintaining the standard of service

UMTS Service launch will not have the same period of grace that early GSM service providers experienced.
Subscriber expectations have now been set and from launch UMTS service areas must offer the same
standards of service quality in terms of network availability and successful completion of voice and data calls.
Motorola’s UTRAN hardware and software contributes some unique capabilities to ensure good QoS achieved.
Standards compliance
USR 1.0 Standards Compliance: Currently June 01, however ongoing 3GPP Standard R99
standards reviews are done to ensure compatibility with future standards driven by mobile
specification and Network Operators. Longevity - 3GPP R4 Ready.
9-46 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview USR1.0 optional features
Optional features and categories
The USR1.0 optional features are divided into the following categories:
• Node"Node B hardware support features" on page 9-48.:
◦ Six Sectors Support (23023)
◦ Downlink Transmit Diversity: Open Loop (22953)
◦ Node B Trunked Power Amplifier Support (23038)
• "Radio resource management features" on page 9-52.:

◦ Simultaneous Multiple Radio Access Bearers Support (1CS + 1PS) (23081)
◦ AMR Speech Codec Rate Control (23162)
◦ Dynamic Channel Configuration Control (DCCC) (23163)
◦ Direct Retry (23164)
◦ Tracing Functions (23165)
◦ Load Optimisation (23166)
◦ PDCP (Packet Data Convergence Protocol) Header Compression (23167)
• "Inter RAT Handover features" on page 9-58.:

◦ Inter System Active Handover (UMTS <-> GSM) (23110)
◦ Inter System Handover with Dual Receiver Handset (23111)
◦ Inter System Handover - Compressed Mode Handover (23112)
◦ Inter System Change via Cell Reselection (UMTS <-> GSM/GPRS) (23121)
• "Short Message Service (SMS) Point to Point (23066)" on page 9-61.
• "Location Based Services (LBS) - Cell ID (23113)" on page 9-63.
• "Call Trace (23115)" on page 9-65.
• "Overload Control features" on page 9-66.:

◦ Node B Overload Control (23116)
◦ RNC Overload Control (23117)
68P02905W21-B 9-47
02-Jun-2004
Node B hardware support features Chapter 9: UTRAN features in USR 1.0
Node B hardware support features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Six Sectors Support (23023)
Summary
Six sector cell sites in UMTS (W-CDMA) are a very efficient investment since they provide not only excellent
coverage but also increased capacity over tri sector configurations. Also Motorola’s unique pooled resource
capability can be used across all six sectors to provide additional capacity and reliability benefits. Motorola
has successfully implemented our six sector capability in our CDMA networks since 1998. This technology is
therefore fully tested in-field and the network capacity and coverage benefits commercially proven.
Standards
Compliant to 3GPP Release 99 standards.
Description
This configuration is optimised to provide maximum capacity. For this configuration
transmit diversity is not supported.
Six sector requires an LPA per sector.
Benefits
A six sector site is a very cost-effective way of improving coverage. The reduction in the number
of UMTS cell sites required overall (for example; site acquisition, backhaul), far outweighs the cost
of the additional infrastructure required for each individual six sector site.
Coverage increase of 220%+ vs. omni cell and 48% vs. tri sector sites.
Six sector offers up to a 30% reduction in the number of cell sites required to deploy UMTS coverage,
compared to tri-sectored sites. This is particularly beneficial for operators to reduce the initial
capex of a UMTS rollout but can also be leveraged over the long-term.
While achieving the same level of coverage with less sites required, using six sector enables the coverage
plan to offer more capacity. Simulations have proven that coverage provided by 30 six sector sites is equal
to 45 tri-sector sites, which is equal to 100 omni sites. It also showed that six sector provided 12% more
capacity than the tri-sector and 25% more capacity than the omni sites in the above scenario.
9-48 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B hardware support features
Downlink transmit diversity: Open Loop (22953)
Summary
In 2nd generation systems receive antenna diversity is normally used at the base station to enhance the uplink
sensitivity. However antenna diversity in the handset was not deployed widely due primarily to cost and size
constraints. In UMTS it is envisaged that (in at least the short to medium term) the traffic load on the up and
downlink will be highly asymmetric with the downlink being much more heavily loaded than the uplink due
to the widespread uptake of data services. In view of the symmetric duplex spectrum allocation there is a
requirement to raise the spectral efficiency (kbit/s/MHz/cell) of the downlink to support both symmetric and
asymmetric traffic demands. This can be achieved by transmitting from multiple base station antennas on the
downlink. This technique is known as downlink transmit diversity. The basic principle is to create more path
diversity, which combats fading and gives increased performance from the mobile’s rake receiver.
Standards
Fully compliant to 3GPP Release 99 standards, all standardised schemes supported. Open loop schemes:
Space Time Transmit Diversity (STTD) and Time Switched Transmit Diversity (TSTD).
Description
Transmit diversity is used to increase the spectral efficiency of the downlink. Two classes of
transmit diversity scheme have been adopted, the first class uses open loop techniques and the
second uses closed loop feedback (USR3) from the mobile to adjust the transmission phase
(or phase and amplitude) from each of the transmit antennas.
Open loop schemes

Open loop schemes can be applied to both common and dedicated channels since they simply combat fading
without explicit per-UE knowledge (such as the characteristics of the channel paths between the transmitter
and receiver). Maximum gains are achieved under conditions where a mobile is moving at a low speed, where
there is limited path diversity and the fading from the transmit antennas is uncorrelated. Since Transmit
diversity operates by increasing diversity in the system, the gains achievable diminish if the system already
exhibits significant diversity. Thus the achievable gain drops when there is significant inherent path diversity
(for example; due to the environment in which a base station is situated), when mobile speed is sufficiently
high, or when the fading observed (at the receiver) from the different transmission antennas is correlated. Open
loop schemes do give smaller relative gains as speed increases; however they are suitable for all conditions.
A simulation was run for a representative dense urban environment with a mix of packet and circuit
users. No radio resource management was employed since the aim was to assess the capacity limits
of the air interface. If STTD is not used then the downlink capacity, based on 95 % of connections
achieving target QoS, is around 60 % of the uplink capacity (defined by the same criterion). However
with STTD enabled the downlink capacity is around 130 % of the uplink.
The difference in uplink noise rise at high loads, as a function of downlink transmit diversity being
enabled or not, is due to the difference in pilot coverage achieved in these scenarios.
Benefits
Benefits to the operator from transmit diversity are an increased spectral efficiency on the downlink and
increased range due to the increase in sensitivity. For the mobile support of all the transmit diversity
schemes is mandatory. It is up to the operator to select the appropriate transmit diversity variant for a
particular connection/Node B deployment, as a function of the propagation environment. Motorola has
68P02905W21-B 9-49
02-Jun-2004
Node B hardware support features Chapter 9: UTRAN features in USR 1.0
been, and continues to be, particularly active in the area of transmit diversity standardisation and as such
is well positioned to advise an operator of the relative benefits of each of the schemes in terms of absolute
performance gain and applicability to a particular cell site deployment scenario.
Node B Trunked Power Amplifier Support (23038)
Summary
Motorola’s advanced multi-carrier Linear Power Amplifier (LPA) architecture and trunked PA technology
are already deployed and extensively proven in existing 2G CDMA networks. The techniques have
been enhanced to offer significant benefits to the operator in WCDMA. A trunked Linear Power
Amplifier (LPA) is used to provide power amplifier trunking efficiency. In this arrangement, a group
of amplifier modules operate as a single trunked resource pool of RF power that can be allocated
as required between multiple sectors at a cell site. This facilitates efficient support of asymmetric
traffic and avoids RF overload conditions. The method dispenses with the need to over-design the
individual power amplifiers for the worst-case output power in each sector.
Average transmit power

Standard Power output (irrespective of configuration +43dBm
or load)
Power out put using power sharing across sectors +46dBm
(dependant on configuration and load)
Standards
Compliant to 3GPP Release 99 standards.
Description
The trunked LPA subsystem consists of either three or six LPAs arranged in a matrixed fashion. Each amplifier
should be thought of as part of an overall power amplification resource which can be distributed between
sectors and carriers to provide power amplifier trunking efficiency. Each LPA module is multicarrier and
linear over a 20 MHz bandwidth, meeting all operator requirements for multicarrier WCDMA deployments.
The three or six LPA trunked sets support all possible site configurations and allow the site
to be upgraded easily. One LPA is required for each Carrier.
The input (splitter) matrix accepts the composite, potentially multi-carrier, signal from each sector to
be amplified by the trunked set. One input signal is present for each sector (being of bandwidth 5 or
10 MHz). Each LPA module contributes simultaneously to amplification of all signals presented at
the input ports and the resulting amplified signals are summed in the output (combiner) matrix. The
input and output matrices can be thought of as a transform pair being designed such that the amplitude
and phase relationships ensure proper distribution of the amplified signals to the correct sector/antenna
output; whilst minimising the amount of energy present at the other sector outputs.
9-50 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Node B hardware support features
Benefits
This amplifier architecture has two major advantages:
• Trunked PA - Each amplifier is part of a trunked resource and as such the BTS power may
be allocated arbitrarily between multiple sectors at the cell site. This is especially useful for
handling non-uniform traffic distribution at a site without needing to over design the power
amplifier for the worst-case output power in all sectors. Power is simply directed to the sector
where it is needed most. The sectors that are not requiring the same level of power are
effectively donating their spare power to the sector that needs it. A traditional LPA architecture
would require the LPA to be dimensioned to ensure the maximum power needed in non-uniform
distributions was available for each sector resulting in a less efficient implementation.
• Soft Fail - a second advantage is the soft fail nature of the architecture. Since all power
amplifier modules are sharing in the amplification of all signals, the failure of any one
amplifier module results in only a slight degradation in available power for all sectors.
This further reduces the system cost of the power amplifier system by not requiring a fully
redundant amplifier in each sector to achieve high availability of the BTS power subsystem
under failure conditions. An amplifier failure simply causes more cross-talk between sectors.
Since WCDMA uses single frequency reuse this simply alters the softer handover regions.
68P02905W21-B 9-51
02-Jun-2004
Radio resource management features Chapter 9: UTRAN features in USR 1.0
Radio resource management features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Simultaneous Multiple Radio Access Bearers Support (1CS +

1PS) (23081)
Summary
UMTS delivers rich multimedia content and services to mobile users. It provides a flexible framework
designed to facilitate the creation of new value-added services that enhance the user experience over and
above that which today’s second-generation networks can provide. In particular, UMTS is capable of
supporting the simultaneous provisioning of data streams with different characteristics, which may be
bundled at the application layer to create exciting new services. The constituent data streams may vary
in terms of bandwidth, tolerance to information loss and sensitivity to delay (amongst other attributes).
Since nobody can say which services will become popular, flexibility to be configured to efficiently
support a wide range of service bundles is a key requirement. Motorola’s UTRAN supports multiple
simultaneous Radio Access Bearers (RAB) per mobile with a maximum of one RAB per mobile with
subflows. This allows a wide range of differentiating services and applications to be provided.
Standards
This feature is compliant with 3GPP Release 99 specification.
Description
UMTS offers the simultaneous support of multiple data streams with different characteristics. At a
basic level this allows simultaneous service capability but by bundling a number of these data streams,
at the application layer, news services can be generated which will allow an operator to differentiate
themselves from their competitors and generate new revenue streams. A simple example is video
streaming at the same time as a basic AMR voice call, or a video conferencing service.
To support a single data transfer UMTS defines a number of different transport channels that in turn are
mapped onto a specific type of physical channel. The type of transport channel a particular data transfer
is mapped onto depends on its characteristics, which are defined by its RAB parameters.
Given a specific set of RAB parameters the UTRAN maps the data transfer to the most efficient choice of
transport channel. Either the core network or a mobile may initiate a call consisting of multiple simultaneous
data transfers, each with its own set of RAB parameters. Motorola’s UTRAN is capable of supporting up
to two simultaneous RABs per mobile. The Radio Access Bearer Establishment, Reconfiguration and
Release function in the RNC maps each of the RABs onto the appropriate transport channel taking the
capabilities of the mobile and core network into consideration. For example one RAB may be mapped
to a Dedicated Channel (DCH) carried on a Dedicated Physical Channel (DPCH).
Initially Motorola’s UTRAN supports two simultaneous Radio Access Bearers (RAB) per mobile.
(one for data and one for voice). This decision has been made partly because most UMTS mobiles
will initially support only two simultaneous RABs. As four RAB handsets become available Motorola
will initiate infrastructure support. At present this is planned for USR2.0.
9-52 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Radio resource management features
However even with the initial two multiple RABs this is still new capability over GSM and
this allows a wide range of differentiated and targeted multimedia services to be provided by
the operator with the resulting impact on new revenue flows.
Benefits
The first benefit of multiple RAB’s to network operators is that it creates the platform to launch a totally
new segment of multimedia applications and services that are not currently available on GSM. This enables
Operators to target new revenue streams as UMTS is rolled out and provides a key marketing pull tool for
consumer interest in applications that are new and differentiated from existing services and call capability.
The second benefit provided by multiple RABs is more flexibility in the way subscribers can access
different services. ARPU per user will increase if the user is utilising the ability to access two services
simultaneously, that is the subscriber effectively pays more for the duration of their service session.
AMR Speech Codec Rate Control (23162)
Summary
AMR Speech Codec rate control allows the dynamic allocation of the full range of AMR source rates to
ensure subscribers receives the best rate for the service being used and network resource available.
Standards
Description
Motorola offers the full range of AMR source rates from 4.75 to 12.2 kbit/s. In our UMTS network these can be
dynamically allocated so that subscribers are always offered the best AMR rate for high voice quality within the
confines of the network resource available. The rate can be adapted for each individual during an active call.
Examples of when dynamic rate change could be initiated on the downlink include; when traffic on
the air interface exceeds the acceptable load, or when the connection based Frame Erasure Rate value
indicates a bad quality connection. In the uplink the corresponding change could be initiated when
there is a need to extend the uplink coverage area for speech by using several AMR modes or when
the measured load on the air interface is reported to exceed the acceptable load level.
Motorola’s AMR codec feature also has an error concealment mechanism to combat
the effects of transmission errors.
Benefits
This feature provides enhanced end user experience by maintaining stable voice
quality for the duration of the subscriber call.
The error concealment feature also assists in the provision of stable, quality service
when AMR capability is initiated.
68P02905W21-B 9-53
02-Jun-2004
Dynamic Channel Configuration Control (DCCC) (23163)
Summary
DCCC reduces requirements for valuable channel code resources, and in addition the associated
reduction in mobile transmit power increases subscriber access to the network.
Standards
Description
As the source rate of Background (Best Effort) QoS service varies considerably due to the range of applications
that come under this heading, DCCC feature provides channel coding efficiencies by configuring the channel
bandwidth according to the source rate. When the source rate is lower, Motorola configure a smaller channel
bandwidth for the service, while we configure larger channel bandwidth when the source rate is higher.
One of the key benefits of the DCCC feature offering flexible configuration is related to channel code
limitations on the downlink. Configuring smaller bandwidth for Best Effort service with lower source
rate saves valuable capacity in channel code source. In addition this reduction in code transmission
means the transmitted power from the mobile can also be reduced and this enables increased subscriber
access in the cell due to transmit power / capacity relationship in UMTS networks.
However to ensure an effective balance between channel bandwidth utilised and number of
subscribers able to obtain network access in a cell, Motorola also consider the current radio link
quality when configuring the best effort service channel bandwidth. If the radio link quality
suddenly becomes very poor configuring larger bandwidth is prohibited.
Benefits
Having flexible configuration of smaller channels when lower source rates are required and
its associated effect on reducing mobile transmit power enables operators to carry higher
volumes of subscriber traffic. If the configuration of channels is managed by a fixed parameter
approach then this additional capacity opportunity is lost.
Direct Retry (23164)
Summary
Directed Retry allows balancing call load over available UTRAN resources for increased user access
with associated quality of service improvements and revenue increase.
Standards
9-54 68P02905W21-B
02-Jun-2004
Description
This feature helps to balance network call load over available UTRAN cell resource. Direct Retry enables the
RNC to allocate radio resources from another Node B cell under its control in a situation where a mobile
cannot gain access to the network from its current cell location due to insufficient radio resource.
It can also be used when a subscriber on an active call is moving into a new cell and needs
to complete successful handover to maintain the call.
The RNC initiates this process by sending a command to the mobile to access another
cell through messaging on the Uu interface.
Benefits
Key benefits of this feature are increased subscriber access rate to available UMTS services and
more efficient radio resource allocation across Node B cells.
This feature has a very positive impact on the subscriber’s quality of service percep-
tions from increase service access.
Tracing functions (23165)
Standards
Load Optimisation (23166)
Summary
Load Optimisation is part of Motorola’s set of RNC algorithms that support operators in efficient
management of radio network resources. This is very important if operators are to make really effective
use of the network coverage and capacity provided by their UMTS infrastructure.
Standards
68P02905W21-B 9-55
02-Jun-2004
Description
Motorola offers operators unique focus on the management of radio resource due to its impact on revenue
generation and quality of service through increased subscriber access at all times. Motorola features provide:
• Increased capacity across the whole radio network due to performance efficiency.
• Increased stabilization of radio network and RNC.
• Increased call access rate when network hot spots occur.
• Reduced dropped call rate.
To specifically assist with load balancing in the UTRAN network, Motorola offers Inter-Frequency Load
Balance, Intra-Frequency Load Balance (that is, Cell Breathing), and PUC (Potential User Control).
The Inter-Frequency Load Balance algorithm balances the load level between cells that have the
same coverage area but utilise different frequencies. It achieves this by transferring some mobiles,
via hard handover, from the high loaded cell to the cell with low traffic load.
The cell breathing algorithm moves required mobiles from one adjacent cell to another one by adjusting
the soft handover area to achieve a more even load balance across the cells concerned.
The PUC algorithm controls the potential cell load by adjusting the parameters of
cell selection and cell reselection.
Benefits
Increased call access rate when network hot spots occur and overall reduced dropped call rate will provide
significant input to positive subscriber experience and perceptions of quality service provision.
PDCP (Packet Data Convergence Protocol) Header Compression

(23167)
Summary
This feature compresses the IP header code. With supporting mobile functionality this feature will enable
compressed packet data messages from the mobile, through to the RAN, into the Core Network and vica versa.
Standards
Implemented according to the PDCP Protocol specified in 3GPP TS 25.323 V3.5.0. This standard
covers several methods of header compression but for initial UMTS release Motorola is supporting
the IP header compression method that is the RFC2507 protocol.
Description
This Motorola features enables you to run IP more efficiently over ATM, in particular saving on header
resource across the air interface and accelerating transmission of Packet Data services.
This will provide an improved compression method for IP header over today’s techniques
and enables IP to run more efficiently over ATM.
9-56 68P02905W21-B
02-Jun-2004
In the first phase of UMTS it is expected that the key IP messaging being sent over the air interface
and ATM layer in the RAN will be O&M messaging. As IP evolves to be the protocol for all data
packet transfer in the network the benefit of this feature will further improve operator service levels.
It will enable faster transmission of subscriber data services, increased air interface capacity and
therefore the ability for operators to accommodate more users on the network.
Benefits
When this feature is utilised for all data packet transfer it is expected that UMTS services will be
under heavy demand. Subscribers will benefit from faster data service transmission and increased
user access to network services, both targeting QoS performance.
68P02905W21-B 9-57
02-Jun-2004
Inter RAT Handover features Chapter 9: UTRAN features in USR 1.0
Inter RAT Handover features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
3G-2G Handover compressed mode/dual receiver are associated with inter system or inter frequency
hard handover functionality. This category of handover occurs when a mobile is transferring from one
set of radio frequencies to a completely new set, for example handover from UMTS to GPRS/GSM
services or vice versa. The 3G-2G handover features are only concerned with handover from UMTS
to GSM/GPRS systems. When the network is making handover decisions it uses radio environment
measurements that are sent by the mobile to the RNC. UMTS standards have planned for two methods
by which a mobile can collect these radio environment measurements.
Standards
Description
Radio environment measurement reported by the mobiles are used in handover decisions. There are two
types of dual mode/dual band mobiles in the market to support the inter-mode hard handovers:
• Compressed Mode
Compressed Mode is where a single receiver mobile performs measurements on the
GSM/GPRS network under compressed mode. The mobile starts monitoring upon
receiving the command from the RNC. In compressed mode, idle periods are created
within a radio frame so that the mobile can perform measurements during these periods.
The idle period is created by compressing, in time, the information normally sent in a
10ms radio frame. Longer synchronisation time (more than two seconds to synchronise
with one GSM cell) will be required for this operation. Additional interference may be
generated within the cell when the information is compressed and transmitted at higher
power and this may induce the associated interference/ capacity impacts previously
mentioned under the power control feature seen in USR1 baseload.
• Dual Receiver
A dual receiver mobile performs measurements simultaneously on GSM/GPRS network
while the subscriber is in active mode using UMTS services. This means the mobile is
able to synchronise with the GSM network very quickly, typically less than two seconds,
and hence facilitate faster handover operation when required.
Handovers from GSM/GPRS to UMTS require additional software, included in GSR6, support in the GSM
BSS network. In areas served by both 2G and 3G networks, to perform cell reselection from the 2G
to 3G system in idle mode and to handover from the 3G to 2G system in circuit switched active mode
9-58 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Inter RAT Handover features
(during a call) through a system initiated handover. This functionality only applies to Circuit Switched
calls. For active mode GPRS Packet calls, mobile controlled cell reselection between the 2G and 3G
systems uses the same algorithm as that used for cell reselection in idle mode.
Handovers involving active GPRS data calls will require the GSN software release
GSN3 or 2G/3G compatibility core network.
Benefits
It is possible that some governments may mandate that new entrants to the UMTS market may have a right to
roam on the GSM network of existing operators. Clearly here intermode roaming will very desirable.
It is critical that Operators provide continuity of service when they are transferring from 3G to 2G
areas to be seamlessly maintained to ensure good customer satisfaction levels.
Motorola’s proven expertise in CDMA handover management has been utilised in USR1.0 software
to ensure an efficient handover process is consistently delivered. High quality of service perceptions
when using new UMTS services will be a key competitive differentiator for network operators
in maintaining existing customers and attracting new subscribers.
Maintaining call connections for voice and data services will ensure revenue streams are
optimised. Also important for generating early 3G revenues will be cell reselection from 2G
systems to 3G systems when a subscriber enters a UMTS service.
It is also possible that greenfield UMTS operators will be given rights to offer services to the public by
national roaming on existing operators GSM/GPRS networks. Orderly and effective handover algorithms
will be paramount for existing operators to manage this extra subscriber traffic.
Inter System Active Handover (UMTS-GSM) (23110)
The Inter System Active Handover UMTS-GSM is the procedure that needs to be followed
to perform a handover from a UMTS cell to a GSM cell.
The term Active makes reference to the dedicated (or connected) GSM mode, to which
this handover is performed, as opposed to the UMTS-GSM inter-RAT handover via cell
reselection that is performed to idle GSM mode.
According to this statement, this handover is performed while the UE is transmitting, and the
procedure needs to establish an active connection with the GSM network.
Like all the inter system handovers, this is a hard handover, since both systems have different working
frequencies, a transmission gap to update the working frequency at the handset will be neccessary.
This handover type is triggered when there are no suitable UMTS sites to move to, or when the
radio link conditions would significantly improve, based on the inter system measurements. These
inter system measurements are obtained during the transmission gaps of the Compressed Mode
in which the UE should enter before performing this procedure.
Since GSM only supports Circuit Switched traffic, if the handset has a Packet Switched connection established
when performing the inter system change to GSM, an inter system change UMTS-GPRS shall be triggered.
68P02905W21-B 9-59
02-Jun-2004
Inter RAT Handover features Chapter 9: UTRAN features in USR 1.0
Inter System Handover with Dual Receiver Handset (23111)
The Inter System Handover with dual receiver handset is a inter system handover type that is based on the UE
capability of receiving information at the same time from both systems it performs the handover between.
frequencies, a transmission gap to update the transmitting frequency at the handset will be necessary.
This handover type is triggered when there are no suitable UMTS sites to move to, or when the
radio link conditions would significantly improve, based on the inter system measurements. Unlike
other inter system handover types, it is not necessary for the UE to enter in Compressed Mode to
perform the interfrequency measurements, since based on its dual receiving capability, it is possible
to perform these measurements while its working in a normal way.
Inter System Handover - Compressed Mode Handover (23112)
The Inter System Handover - Compressed Mode handover is the inter system handover type that is based
on the UE capability of performing the inter frequency measurements during the Compressed Mode
transmission gaps, as opposed to the UMTS - Intersystem handover with Dual receiver handset.
Like all the inter system handovers, this is a hard handover, since both systems have different
working frequencies, a transmission gap to update the working frequency (Transmission
and Reception) at the handset will be necessary.
This handover type is triggered when there are no suitable UMTS sites to move to, or when the radio link
conditions would significantly improve, based on the inter system measurements.
Inter System Change via Cell Reselection (UMTS-GSM/GPRS)

(23121)
The inter system change via cell reselection is the procedure that needs to be followed to
perform a handover from a UMTS cell to a GSM cell.
frequencies, a transmission gap to update the working frequency at the handset will be necessary.
This handover type is triggered when there are no suitable UMTS sites to connect to, or when
the radio link conditions would significantly improve, based on the inter system measurements.
These measurements are performed during the Compressed Mode Transmission Gaps if it is a
Compressed Mode handover. If it is an Inter System Handover with Dual Receiver Handset there
is no need to perform these measurements in compressed mode.
The hard handover can be also triggered by the network, based as well on the measurements taken by the UE.
Since GSM only supports Circuit Switched traffic, if the handset has a Packet Switched connection established
when performing the inter system change to GSM, an inter system change UMTS-GPRS shall be triggered.
9-60 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Short Message Service (SMS) Point to Point (23066)
Short Message Service (SMS) Point to Point (23066)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
This is a key subscriber application for GSM, which is also be available in UMTS. SMS
availability on UMTS will allow service continuity for users with multimode handsets as they
move between UMTS coverage areas. It also has continued revenue stream generation capabilities
for operators as SMS is taken into new application areas.
Standards
Description
This feature enables subscribers to send and receive data in an end-to-end mode. The traffic is
particularly bursty where blocks of traffic are sent at intervals of idle periods and non-real time. At
the minimum, UMTS will provide the same level of service as that offered in GSM. Interoperability
with GSM is possible with the availability of multistandards mobile stations.
The Short Message Service (SMS) provides a means of sending messages of limited size to and from
GSM/UMTS mobiles (user equipment - UE). The provision of SMS makes use of a Service Centre
(SC), which acts as a store and forward centre for short messages. Thus a GSM/UMTS PLMN needs
to support the transfer of short messages between Service Centres and UEs.
Mobile originated messages shall be transported from an MS to a Service Centre. These may be
destined for other mobile users, or for subscribers on a fixed network. Mobile terminated messages
shall be transported from a Service Centre to an user equipment (UE).
The text messages to be transferred by means of the Short Message Mobile Terminated or the
Short Message Mobile Originated contain up to 140 octets.
68P02905W21-B 9-61
02-Jun-2004
Short Message Service (SMS) Point to Point (23066) Chapter 9: UTRAN features in USR 1.0
Benefits

• Provides an efficient method for delivering short message services to subscribers,
leading to potential increase in revenue generating capabilities through higher
traffic usage and attractive value added services.
• Service continuity and consistency as subscribers move between different coverage areas
for UMTS enhancing the end users experience and hence reduce churn.
• Enhances the potential of SMS including, for example, gaming and information
services are being further developed utilising this capability. Thus, SMS still
has considerable scope to deliver further value added services to subscribers
and therefore revenue generating deliverables.
9-62 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Location Based Services (LBS) - Cell ID (23113)
Location Based Services (LBS) - Cell ID (23113)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
The Cell ID-based location service is a coarse user’s terminal positioning method provided in UMTS
mobile network. A particular UE location is estimated by indication of cell identifier (Cell ID), which
may be mapped directly to Node B serving cell geographical coordinates or Service Area Identity (SAI).
The Cell ID positioning uncertainty is limited by cell site radio coverage area.
The location identification is provided to identify the likely location of specific user’s
terminals. This is meant to be used for charging, location-based services, lawful interception,
emergency calls, as well as the positioning services.
Standards

USA FCC Wireless E911 Rules, with respect to E911 location technology by the
Third Report and Order (FCC 99-245).
Description
In the cell ID-based (that is, cell coverage) method, the position of an UE (User Equipment) is estimated
with the knowledge of its serving Node B. The information about the serving Node B and cell may be
obtained by paging, locating area update, cell update, URA update, or routing area update.
The cell coverage based positioning information can be indicated as the Cell Identity of the used cell, the
Service Area Identity or as the geographical coordinates of a position related to the serving cell. The position
information shall include a QoS (Quality of Service) estimate (for example, regarding achieved accuracy).
When geographical coordinates are used as the position information, the estimated position of the UE can
be a fixed geographical position within the serving cell (for example, position of the serving Node B), the
geographical centre of the serving cell coverage area, or some other fixed position within the cell coverage area.
Identify and report in a standard format (for example, geographical coordinates) the current location of the
user’s terminal and to make the information available to the user, network operator, service provider, value
added service providers and for PLMN (Public Land Mobile Network) internal operations.
Benefits
Location Services may be considered as a network-provided enabling technology consisting of standardised
service capabilities, which enables the provision of location applications.
68P02905W21-B 9-63
02-Jun-2004
Location Based Services (LBS) - Cell ID (23113) Chapter 9: UTRAN features in USR 1.0
LBS will be a major element of UMTS service revenues, Ovum forecast that overall market demand for LBS
will be expected to grow from $2.1B in 2001 to $10.1B in 2005. LBS services developed today and in the early
phases of 3G can be an effective hook for building consumer and business users interest in new data services.
9-64 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Call Trace (23115)
Call Trace (23115)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
Call Trace is the ability to trace a call through the cellular network, and assist improve operators to
optimise network by ’following’ calls to monitor factors such as quality and handover successes. This
allows operators to improve the quality of the network and address any coverage issues.
Standards
Description
Call Trace requires the Network Elements in the Core Network and Radio Network Infrastructure and
their corresponding managers to interact in order to collect the call specific information.
The call trace functionality embraces:
• Subscriber trace is used to trace the calls of a particular subscriber or User Equipment
(UE) device (UE testing, Subscriber’s call surveillance).
• Infrastructure trace is used to trace any calls involving any terminal device on a specified
set of network equipment (Node B, Radio Network Controller).
Benefits
Call trace is useful for the following purposes:

• Network optimisation.
• UE and Network Infrastructure testing.
• Subscriber’s call surveillance.
68P02905W21-B 9-65
02-Jun-2004
Overload Control features Chapter 9: UTRAN features in USR 1.0
Overload Control features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Summary
The RNC and Node B automatically react to overload conditions pertaining to the resources under
their control as well as signals sent from the core network or adjacent RNC. This improves the quality
of the network as it enhances system reliability under extreme processing loads.
Standards
Description
The reaction to radio overload includes denying admission of new calls as well as throttling of data traffic for
non-real-time services. The RNC and Node B also manage internal processing resources and interface capacity.
Benefits
• Increasing overall UTRAN reliability and availability.
• Decreasing system outages due to exceeding of limited RNC processing capabilities.
• Decreasing system outages due to exceeding of limited Node B processing capabilities.
• This feature maintains system stability and QoS for existing connections.
Node B Overload Control (23116)
Node B overload control refers to processing overload management of its limited resources and capabilities.
Node B limits traffic processing base on its instantly monitored processing power utilization.
9-66 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overload Control features
RNC Overload Control (23117)
The RNC overload control refers traffic processing overload management. The Radio Network Controller
(RNC) rejects establishing of new calls and tries to preserve existing calls as a first course of action until
overload condition disappear. Moreover if RNC receives an overload indication from a remote node, the
overload management procedure at the RNC acts to decrease the load it creates in that remote node.
68P02905W21-B 9-67
02-Jun-2004
Overload Control features Chapter 9: UTRAN features in USR 1.0
9-68 68P02905W21-B
02-Jun-2004
Chapter
10
OMC-U and its USR 1.0 features
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 10-1
02-Jun-2004
Chapter overview Chapter 10: OMC-U and its USR 1.0 features
Chapter overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter describes the OMC-U and the features included in UMTS release USR1.0.
The topics covered in this chapter are:

• "Operations and Maintainance Centre for UMTS (OMC-U)" on page 10-3.
• "Overview of OMC-U features" on page 10-4.
• "OMC platforms" on page 10-8.
• "OMC-U Fault Management" on page 10-11.
• "OMC-U Configuration Management" on page 10-16.
• "OMC-U Load Management" on page 10-20.
• "OMC-U Performance Management" on page 10-21.
• "Interfaces from OMC-U to higher level management" on page 10-23.
• "OMC-U Security Management" on page 10-24.
• "OMC-U general application functions" on page 10-26.
• "Optional OMC-U features in USR1.0" on page 10-29.
10-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Operations and Maintainance Centre for UMTS (OMC-U)
Operations and Maintainance Centre for UMTS

(OMC-U)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Motorola’s OMC-U is the intelligent solution for UMTS network management. The focus is on features that
provide real benefit to operators in terms of reduced operator workload, reduced administration, reduced
training, increased flexibility, increased operability, and increased system intelligence and automation.
The OMC is built on a stable third party platform and utilises a scaleable architecture that
ensures only one OMC is needed to provide integrated management functionality for all UMTS
Network Elements. The high reliability of this architecture will be further enhanced in future
releases with the introduction of a fully redundant clustered solution.
Intelligent features built into the system and the benefits they provide include:
• Offline provisioning tool - the right first time approach to network
provisioning reducing operator error.
• Standards-based northbound interface and pre-integrated OSS gateways - allows

networkwide monitoring and management reducing training load.
• Multi-stage alarm filtering - reduction in alarms seen by operator.
The reliable architecture is matched by the use of a reliable messaging flow between the OMC and
the network elements. This ensures complete reliability of O&M communications, increases security
and removes the need for operator invoked audits and resynchronisations.
UMTS network management architecture
In the UTRAN, a 3GPP standards compliant Iub Interface (including Resource Management) has been
implemented between the Node B and RNC. This allows network elements in the UTRAN to route interface
traffic to other network elements. Network elements can then be physically connected in two different ways:
• The OMC communicates with the Node Bs via the RNC (indirect Node B connection).
• The OMC has direct connection to the Node Bs and RNC.
In the core, the Comm Hub facilitates connection between the OMC and all NEs using IP over Ethernet.
For remote NEs, the WAN connectivity options on the Comm Hub can be utilised.
68P02905W21-B 10-3
02-Jun-2004
Overview of OMC-U features Chapter 10: OMC-U and its USR 1.0 features
Overview of OMC-U features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Initial Baseload OMC-U features
In USR1.0 the initial baseload features for the OMC-U are listed in this section. Each features
is described in the application section later in this chapter.
Platform Management features

The USR1.0 features relating to Platorm Management are:
• Backup and Restore (23212)
• Web-based Access to OMC (23353)
• NT Client Install (23175)
• Unix Server Install (23176)
• System Administration Features for USR1.0 Commercial Delivery (23365)
• Solaris-based OMC-U (21906)
• SunFire Platform (23352)
• Centralised Date/Time Management (23351)
Fault Management (FM) features

The USR1.0 features relating to Fault Management are:
• Real-time Alarm Window (23168)
• Alarm Filtering (23170)
• Event Filtering - Phase 1 (23169)
• Alarm Comment (23347)
• Alarm Notification (Audible Indicator) (23171)
• Real-time Event Window (23348)
• Event Logging Database (23172)
• Scheduled Historical Event Reports (23446)
• Alarm Logging Database (23173)
• Scheduled Historical Alarm Reports (23448)
10-4 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of OMC-U features
• Alarm Consolidation/Reduction (23207)
• State Management - Phase 1 (23174)
• Alarm and Event Customisation for USR1.0 (23335)
• Fault Management Information Synchronisation (heartbeat polling) on UTRAN (23196)
Configuration Management (CM) features

The USR1.0 features relating to Configuration Management are:
• Integration of RNC LMT Functionality (23356)
• Configuration Change History Report (23357)
• NE Configuration Report (23358)
• Bulk Provisioning (Off-line) (23359)
• Bulk Provisioning Impact Report (23188)
• Distribute NE Configuration (23189)
• Distribute NE Sofware (4524)
• Managed Objects Form Interface (Parameter Views) (23204)
• Configuration Import/Export via FCL - Phase 1 (23199)
• Distribution Monitor (23192)
• Manual Distribution Control (23191)
• Distribution to Management Platform (23209)
• Configuration Management Customisation for USR1.0 (23364)
• Management of Node B Outdoor (23193)
• OMC Manage LBS (Cell Id) (23194)
• RNC Capacity License File Management (23200)
• Multiple NE Version Support for UTRAN - 2 Version Support (23363)
• Configuration Management Synchronisation for Node B (23195)
68P02905W21-B 10-5
02-Jun-2004
Overview of OMC-U features Chapter 10: OMC-U and its USR 1.0 features
Load Management features

The USR1.0 features relating to Load Management are:
• Software Upgrade - Quick Reboot - Phase 1 (23177)
• Software Upgrade - Quick Reboot: Multiple Upgrades - Phase 1 (23178)
• Manage Software Updates (23190)
Performance Management (PM) features

The USR1.0 features relating to Performance Management are:
• 3rd Party Application Support for Statistics (23211)
◦ User Customisable Performance Management Reporting - 23202
◦ Scheduled PM Reports (23349)
◦ PM Statistics Customisation for USR1.0 (23198)
◦ Performance Management Synchronisation for UTRAN (23350)
Interfaces from OMC to higher level management applications features

The USR1.0 features relating to interfaces are:
• Support for 3GPP IRP FM Northbound Interface to NMC (23197)
• Support for 3GPP PM File Format (XML file format) (23206)
Security Management features

The USR1.0 features relating to Security Management are:
• User Account and Access Control Management (User Profile Editor) (23179)
10-6 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Overview of OMC-U features
General Application features

The USR1.0 features relating to general application functions are:
• Operation Context Editor (23180)
• Domain Editor (Region Editor) (23182)
• Map Editor (23184)
• Workspace (23181)
• UTRAN Map (23183)
• Discriminator Contruct Editor (3554)
• Entity Browser (Navigator) (23187)
• Online Help - Contextual Help for Alarms and Events (23201)
• Help Customisation for USR1.0 (23367)
• Call Trace (Display) (23186)
Optional OMC-U features
In USR1.0 the optional features for the OMC-U are:

• Support for 3GPP IRP FM Northbound Interface to NMC (23197).
• Web Access Server (22044).
68P02905W21-B 10-7
02-Jun-2004
OMC platforms Chapter 10: OMC-U and its USR 1.0 features
OMC platforms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of OMC platforms
In line with Motorola’s strategy to provide a single OMC to manage a Motorola UMTS network, the
OMC-U (managing the UTRAN) and OMC-S/T (managing the UMTS Core Network), can share the
same platform. This approach reduces the cost of ownership of the network management system both
in terms of hardware and number of network management personnel required.
The hardware platform uses the Sun™ SunFire V880 Server and takes advantage of the
familiar environment of Windows through the use of a Dell PowerEdge™ Server. The
user interface is implemented on Windows Clients.
A plug and play concept is used for the OMC software allowing the operator to select the
building blocks with which to manage their Motorola network.
A single load pack of software provides both OMC-U and OMC-S/T functionality. OMC-U functionality is
then enabled depending on the licenses purchased. The Server software provides the basic functionality that
is shared by all OMCs; whether they are managing the UTRAN or Core Networks. In addition to this, the
specific U and/or T modules are then enabled. The capacity of the OMC can be expanded through expansion
modules specific to the managed network. A similar model can be seen with the client software.
This solution offers a UNIX server providing persistent data storage and network communications,
together with a combined Windows Server providing an application and data server. In this way the
benefits of flexible GUI design are maintained and combined with the resilience and scalability of
UNIX. Due to the fast moving nature of the computer industry Motorola expects that these models
will be superseded during the course of the UMTS lifecycle. Motorola will adopt successor platforms
and provide backwards support for current platforms whenever possible.
NT Server hardware
The Dell PowerEdge™ 6400/6450 is the Windows server. It delivers best-in-class high availability
and performance features for the mission critical operation of the today’s networks. The PowerEdge™
6400/6450 provides a robust and highly available platform for the OMC-U. Features such as redundant
cooling fans, hot-pluggable redundant power supplies and hot-plug drives, allows the replacement of
failed components without having to shut down the server first. Load balancing network cards also
incorporate redundancy, eliminating a further single point of failure. Customers have a choice of tower
(6400) or rack mountable (6450) configurations. Table 10-1 lists the specifications.
10-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC platforms
Table 10-1 NT Server - Dell PowerEdge™ 6400/6450 specifications
Processors Intel Quad Pentimum III Xeon Processors 700MHz

RAM 1 GB
HDD 4 x 18 GB SCSI hot swappable
Channel controller PERC2, 4 channel RAID controller
Backup Tape
Redundancy Redundant PSUs
UNIX Server hardware
Perfect for remote offices, departmental environments, and as a complementary system for data
centre environments, the SunFire 4800 server excels in supporting an extensive array of applications,
including Internet and database, e-commerce, and ERP software. This rack-mountable, deskside unit
combines an advanced set of reliability, availability, and serviceability (RAS) features and supports
two to eight processors, an integrated Fibre Channel disk subsystem, and a maximum of 32 GB of
main memory for exceptional performance. The SunFire 4800 server is binary-compatible with the
entire line of Sun desktop and server systems, as well as their applications.
Table 10-2 Unix Server - Sun SunFire 4800 specifications
Processors 2 x 1.2 GHz CPU

RAM 4 GB
Disks 6 x 36GB mirrored
DAT drive (optional interface)
Graphics card and head
68P02905W21-B 10-9
02-Jun-2004
OMC platforms Chapter 10: OMC-U and its USR 1.0 features
OMC-U platform features
Backup and Restore (23212)

This feature provides the ability to backup and restore the Manager software and NE data.
Web-based access to OMC (23353)

This feature provides a web enabled OMC display for remote OMC access.
NT Client Install (23175)

This feature provides installation of the NT client.
Unix Server Install (23176)

This feature provides installation of the Unix Server.
System Administration features for USR1.0 Commercial Delivery (23365)

Provision of the full commercial standard set of System Administration documentation
for USR1.0 Commercial release delivery.
Solaris-based OMC-U (21906)

Port of the OMC-U onto a Solaris8-based platform. (Internal feature only for development use).
SunFire platform (23352)

This feature delivers the OMC on a Solaris8-based SUN platform - SF4800.
Centralised Date/Time Management (23351)

The OMC-U (UMTS Manager) is the NTP (network time protocol) for the UTRAN network
elements. The OMC-S/T is the NTP for the Core Network elements.
10-10 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U Fault Management
OMC-U Fault Management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Initial high level monitoring of the UMTS Network is carried out using the map and navigator applications.
From these, the operator can get an overview of the current status of the network, with all the information
filtered to meet their requirements. They can then drill down into the problem by using filtered and
unfiltered alarm and event windows, and the historical alarm and event log.
Presentation
The map provides the operator with a graphical overview of the location, connectivity and status of the network
elements in any given region. The map consists of an operator configurable background and a series of nodes.
The background may be divided into several layers each of which may be turned on or off independently. The
background may be either geographic or topological. Topological maps contain a series of nodes and a user
defined background image. The layout of the map components is arranged for ease of viewing. The OMC
has an associated Map Editor, which is used to create, modify, and delete maps within the OMC.
The Navigator contains a representation of the UMTS RAN network containment hierarchy for that
portion of the network under the control of the OMC. Each region, network element, network element
subcomponent, and hardware device or software function is represented by an icon on the navigation tree.
These icons also provide a visual indication of the alarm state of the devices shown on the tree.
In order to view the details associated with fault conditions, the operator should use the alarm
window. Alarms are displayed based on the operator’s subscription criteria and can be sorted on
any labelled column and formatted to suit the operator’s preferences. The alarm window provides
the user with a detailed view of alarms occurring in the system, and provides the user with alarm
handling and fault management capabilities. As information associated with the alarms changes, the
alarm window is automatically updated in real time to reflect the changes.
In addition the OMC is equipped with an Event Viewer. This allows the operator to monitor events from
the network elements as they occur via a scrolling window. Events are displayed based on the operator’s
subscription criteria and can be sorted on any labelled column and formatted to suit the operator’s preferences.
Alarm Database
To view historical information associated with alarms, the operator can use the alarm and event history
reporting application. This provides a simple mechanism for the operator to generate historical alarm and
event history reports. The alarm and event history reporting mechanism will allow operators to produce a
number of different types of reports. The reporting system allows ad-hoc report generation similar to that
offered by SQL query based reporting packages In addition to the Report Viewer, there is a Report Editor
which allows the operator the flexibility to define report conditions (queries) and the layout for the report.
68P02905W21-B 10-11
02-Jun-2004
OMC-U Fault Management Chapter 10: OMC-U and its USR 1.0 features
Audible indicator
The audible alarm indication feature provides visual and audible notification to the operator on the
occurrence of new alarms conforming to their subscription criteria.
Subscription and filtering
Multi-stage filtering and subscription are available on the OMC to ensure that both the operator, and the
internal processes of the OMC are not overloaded with alarm information from the network elements.
Filters can be set up at various stages of the alarm process in the OMC:
• At the reception level: events are filtered before being posted to the event manager;
this reduces the volume of alarms to be processed.
• At the fault management level: filtering is applied before alarm reports are stored in
the data-store; this reduces the volume of alarms stored.
• At the GUI level: allows the operator to quickly focus on specific information displayed
(the filter criteria stays local to the current operator session).
The user interface allows the filters to be set up quickly and efficiently using drag and
drop actions to define the necessary characteristics.
Subscriptions are effectively the reverse of filters, allowing an operator to define which alarms they are
interested in (rather than those they are not). These can be set up to allow the map or alarm and event windows
to display only information from certain regions in the network, certain types of network element, certain
alarm types etc. Again, the user interface allows the subscriptions to be set-up using drag and drop actions.
Fault Management information synchronisation
To ensure the OMC accurately reflects network element alarm information, the OMC implements an
automatic synchronisation process. The OMC will automatically detect a loss of synchronisation of fault
management information due to problems such as NE resets or link outages, and will resynchronise the
information when the connection is re-established. All of this is done without operator intervention.
10-12 68P02905W21-B
02-Jun-2004
Fault Management features
Real-time Alarm Window (23168)

This feature allows the operator to view and handle alarms associated with a network element.
A detailed view of alarms occurring in the system is presented which provides the user with
alarm handling and fault management capabilities.
The following alarm types are supported:
• Communications alarm
• Environmental alarm
• Equipment alarm
• Processing Error alarm
• Quality of Service alarm
Alarm Filtering (23170)

This feature allows alarm filters to be set up and managed. Filtering can be applied at the following levels:
• Reception level - events are filtered before being posted to the event manager. This reduces the
volume of alarms to be processed. The Discriminator Construct Editor is used in part for this.
• Fault management level - filtering is applied before alarm reports are stored
in the datastore. This reduces the volume of alarms stored. The Discriminator
Construct Editor is used in part for this.
• GUI level - allows the operator to quickly focus on specific information displayed
(the filter criteria stays local to the current operator session).
The Discriminator Construct (DC) is a filter for OSI alarms and OSI events that the operator
builds by defining an arrangement of subfilters to obtain the required selectivity. The DC Editor
provides a mechanism to define a DC filter via a graphical interface.
Event Filtering - Phase1 (23169)

This feature allows event filters to be set up and managed. Event Filtering is carried out at two
levels; a low level and a high level. Low level filtering is the functionality that filters events at
source using the discriminator construct. Low level filtering can be used to prevent events reaching
the Operator that are generated as a result of another, perhaps more serious problem, but may not be
the cause of the problem. Five types of low level filter can be defined:
• Corrective Filter
• Tap Filter
• Transient Filter
• Threshold Filter
• Heap Filter
68P02905W21-B 10-13
02-Jun-2004
OMC-U Fault Management Chapter 10: OMC-U and its USR 1.0 features
• Toggling Filter
High level filtering takes place at the level of the Log entities. High level filtering presents the Operator with a
particular view of network activity; it collects events and passes only those that match this view.
Alarm Comment (23347)

This feature allows the operator to add comments to individual alarm instances.
Alarm Notification (Audible Indicator) (23171)

This feature allows the operator to specify whether an audible indicator sounds and presents a
confirmation dialogue detailing the contents of the alarm. A new dialogue is presented for each alarm
that meets the filter criteria. This can be configured using any Alarm field.
Real-time Event Window (23348)

This feature allows the operator to view real-time events, handle state changes and events.
This feature includes the following main functionalities:
• Create top filter to filter event according to managed object, managed object
type, event type, time, and details.
• Set entity list to filter event.
• Sort events.
• Find, copy, save, and print events.
• Modify the column layout of event display.
• Open Management View according to the selected event.
• Open Real-time Event View in Map View and Alarm Handling.
The following Event Types are supported:

• Object Creation
• Object Deletion
• Attribute Value Change
• State Change
• Relationship Change.
Event Logging Database (23172)

The event logging database records all details of events that occur within the network (for example,
configuration events, security events). Event records can be viewed from the Event Record View.
10-14 68P02905W21-B
02-Jun-2004
Scheduled Historical Event Reports (23446)

The manager has the facility to schedule historical event reports. This capability
is provided by Business Objects.
Alarm Logging Database (23173)

This alarm logging database records all alarms generated within the network.
Scheduled Historical Alarm Reports (23448)

The manager has the facility to schedule historical alarm reports. This capability
is provided by Business Objects.
Alarm Consolidation/Reduction (23207)

Alarm Consolidation is designed to reduce the amount of network element alarms seen by
the operator at the Manager. This allows the operator to focus on the most critical, service
affecting alarms, thus improving service levels to customers.
This feature provides the ability to hide similar alarms from the alarm view (presentation layer). It
can be accessed via Similar Alarms menu. Alarm Reduction is configured on a per operation context
basis. It can be set through the Operation Context Management View.
State Management Phase 1 (23174)

This feature supports the ability to view the state of devices in the network and initiate state
management actions such as lock, unlock, graceful lock, reset, pre-cut and cutover of devices.
These commands can be invoked from management views.
The RNC supports lock/unlock only.
Alarm and Event Customisation for USR1.0 (23355)

Support for Node B R1 and RNC R1 generated alarms and events. This feature provides the alarm
and event stream to all the alarm related features and state mangement features.
Fault Management information synchronisation (heartbeat polling) on UTRAN (23196)

This feature automatically detects and generates an alarm when there is a loss of synchronization of Fault
Management information due to NE resets, link outages, and so on, and resynchonises the FM information
with the UTRAN Network Elements without the need for operator intervention.
68P02905W21-B 10-15
02-Jun-2004
OMC-U Configuration Management Chapter 10: OMC-U and its USR 1.0 features
OMC-U Configuration Management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The OMC Configuration Management user interface consists of the OMC Navigator and the offline
provisioning system which are accessed through the OMC Workspace. Configuration of all UMTS
network elements and links between them is supported from the OMC.
The Navigator window is a Windows explorer style interface that allows the operator to navigate through
the UMTS network hierarchy. Each region, network component, hardware device, or software function is
represented by an icon in a tree structure in the Navigator window. For large networks, a search facility is
provided to assist in finding devices and parameters of objects represented in the navigator.
From the Navigator the operator can create and delete objects that have been pre-equipped in the network.
Once network elements or their components have been created, it is possible to drill down to
detailed information on individual parameter settings.
Configuration Management Information Synchronization
Configuration synchronisation provides automatic detection of loss of synchronization and update of the
configuration data between the NE and the OMC. This removes the need for operator-invoked audits.
Data interface
Motorola will support an export mechanism to export the configuration of the Node B to an XML file.
10-16 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U Configuration Management
Offline provisioning
The OMC supports an offline provisioning application to ensure rapid, accurate network provisioning.
The provisioning application performs bulk provisioning of multiple network elements and the
links between those network elements using one of two methods:
• Bulk - changes the whole network element database.
• Individual - changes a single or a few parameters across the whole network by

generating, and running, an FCL file with all the changes in it.
There are limitations to using wildcards in FCL. For example; do

not expect to be able to change the value of attribute x to 1 across
100 Node Bs from the OMC-U client.
A Distribution Monitor allows the network operator to view and control the distribution of software and
configuration data to the network elements. The Distribution Monitor allows the operator to view:
• A list of pending NEs.
• Mode of distribution for each NE.
Prior to the new configuration information being deployed, the OMC validates the
range and rules of the information.
OMC-U Configuration Management features
Integration of RNC LMT functionality (23356)

This feature provides integration (launch with context) of RNC Local Manager man-
agement software into the OMC GUI.
Configuration Change History Report - Phase 1 (23357)

This feature provides the operator with the ability to generate a report of historical configuration
changes. The report can include the following information:
• Operator or trigger of each change.
• Date and time the change was made.
• Change operation.
• Managed object instance that was changed.
68P02905W21-B 10-17
02-Jun-2004
OMC-U Configuration Management Chapter 10: OMC-U and its USR 1.0 features
• Managed object instance attribute values that were changed, old and new.
NE Configuration Report (23358)

This feature provides the operator with the export facility to an XML file on actual
NE configuration in the network.
Bulk Provisioning (Offline) Phase 1 (23359)

This feature provides the operator with the ability to make large sets of configuration changes to
a draft system configuration. Once the set of changes are determined to be correct and complete
they can be distributed into the network as a coordinated unit of work. Multiple operators
can work together in creating the set of configuration changes.
Bulk Provisioning Impact Report (23188)

This provides the operator with a Bulk Provisioning summary report listing all the NEs changed as part of
the current Bulk Provisioning activity. As network operators make changes to a system version, the Impact
Service fans out and tracks the distribution mode of those changes in order to produce an impact report. The
impact report allows the operators to understand the set of network elements that will be distributed and the
mode of distribution that will be used if the system version is selected as the current system version.
Distribute NE Configuration (23189)

The distribution service is capable of downloading the configuration changes identified by the impact
service in a format that is understood by the class of NE being managed.
Distribute NE Software (4524)

This feature allows the operator to load and activate a new software load on a supported NE.
Managed Objects Form Interface (Parameter Views) - Phase 1 (23204)

This feature provides the operator with the ability to make provisioning changes via a forms interface.
Configuration Import/Export via FCL - Phase 1 (23199)

This feature provides the operator with the ability to import and export configuration
data to/from the system via FCL.
Distribution Monitor (23192)

This feature allows the network operator to view and control the distribution of software and
configuration data to the NEs being managed by the Manager.
Manual Distribution Control - Phase 1 (23191)

This feature allows the operator to manually control the distribution of NE changes (software
or configuration data) to one or more NEs.
10-18 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U Configuration Management
Distribution to Management Platform - Phase 1 (23209)

This feature provides the ability to update the management platform with the new
configuration changes/system version.
Configuration Management Customisation for USR1.0 (23364)

This feature provides support for Node B R1 configuration information such as new objects.
Management of Node B Outdoor (23193)

This feature provides management of the Node B Outdoor from the OMC-U GUI.
OMC Manage LBS (Cell ID) (23194)

This feature provides a provisionable parameter in the RNC, for each cell served by the RNC,
consisting of the latitude and longitude of the cell. It also provides a provisionable parameter in the
RNC, for each cell served by the RNC, consisting of the uncertainty code used to indicate the radius
of uncertainty of the point estimate of the latitude/longitude of that cell.
This provisioning is done via the LMT, as the OMC-U does not hold these
parameters for the RNC5000.
RNC Capacity License File Management (23200)

This feature provides the ability to download the RNC Capacity License file to the RNC from
the OMC. This includes file management such as error handling and logging of last download
time and status. All License handling is performed at the RNC.
Multiple NE Version Support For UTRAN - 2 version support - Phase 1 (23363)

The Manager supports two software versions of the Node B to allow a smooth rollout
of a new software version to the network.
Configuration Management Synchronisation for Node B (23195)

This feature automatically maintains synchronization of Configuration Management
data with the Node B network elements.
68P02905W21-B 10-19
02-Jun-2004
OMC-U Load Management Chapter 10: OMC-U and its USR 1.0 features
OMC-U Load Management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The OMC Load Management applications are available as options on the Load Management Provisioning
menu on the Navigator and Map. The following functionality is provided:
• Obtain a report listing the software versions of each NE in the system.
• Installation of software load onto OMC (from distribution media).
• Deletion of software load from OMC.
• Installation of database to OMC - this can be from distribution media or

from the offline provisioning system.
• Download of software load/database to NEs.
• Upgrade NE via quick reboot.
• Progress display of software load/database download.
OMC-U Load Management features
Software Upgrade - Quick Reboot - Phase 1 (23177)

This feature provides an upgrade with quick reboot, and is intended for minor software upgrades (such
as software point releases). Rolling Upgrade strategy is to upgrade the NE with minimal capacity
or service loss. This feature is supported on the UTRAN NEs only.
Software Upgrade - Quick Reboot: Multiple Upgrades - Phase 1 (23178)

It is expected that upgrade with quick reboot will be used for minor software upgrades (such as software point
releases). Rolling Upgrade strategy is to upgrade the NE with minimal capacity or service loss. This feature
supports upgrade to multiple NEs at one time. This feature is supported on the UTRAN NEs only.
Manage Software Updates (23190)

This feature allows the user to download and deploy patch releases via the RNC
10-20 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U Performance Management
OMC-U Performance Management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Performance management provides functions to evaluate and report upon the behaviour and
effectiveness of network equipment and interfaces. To achieve these goals, performance
management provides tools to perform the following subtasks:
• Performance Monitoring - gather the appropriate data for determining network performance.
• Performance Control - control the performance mechanism used to retrieve

performance-monitoring data.
• Performance Analysis - provide an intuitive interface to operators to allow real

time and off line analysis of network performance.
The OMC Performance Management application provides the user with the ability to
create/view background (historical) statistics.
Background statistics
Network element statistics files are created every 30 minutes. These files are transferred to the OMC and
parsed into the relational database. From there they can be interpreted by the PM application or extracted via
SQL to a network performance reporting package. The storage capacity of the OMC extends to 14 days of
statistics, for a longer storage duration, the information can be transferred to external media.
Performance data presentation
A third party reporting tool is included with the OMC to form the core of the performance management
application, and to ensure that operators can set up and run reports from performance data stored in the database.
On-Demand Statistics View (OMC-S/T only)
In addition to the historical statistics reporting, the GSN statistics attributes can be viewed on a
polled basis. This means that the user can create a real-time display of a statistic for a specific GSN.
The statistic is displayed in a graphical form and is updated periodically according to a polling
interval. The user can change the polling interval. The polled statistic graph can be launched from
the Display menu on any of the main OMC applications, that is, Navigator, Map, Tabular View,
Alarm Window, Event Window, SGSNu & GGSNu Parameter Views.
68P02905W21-B 10-21
02-Jun-2004
OMC-U Performance Management Chapter 10: OMC-U and its USR 1.0 features
OMC-U Performance Management features
3rd Party Application Support for Statistics (23211)

For Performance Management, this feature provides an SQL Northbound Interface interface to allow
relevant data to be read directly from the PM database. A Network Performance Reporting application (for
example, Metrica) can use SQL scripts to read directly from the PM database. To ensure operators obtain
full functionality from this feature, Motorola shall publish the portion of the PM database schema that
is relevant to OSS. Note that this northbound interface is separate and distinct from the 3GPP defined
PM IRP. This feature applies to both OMC-U and Domain Manager PM database.
This northbound interface is separate and distinct from the 3GPP-defined PM IRP. This
feature applies to both OMC-U and Domain Manager PM database.
User Customisable Performance Management Reporting (23202)

This feature provides an application to enable the operator to view statistics in a tabular or graphical
format and provide reports which can be made available outside the operations staff work area. The
PM application is a third party product called Business Objects. This application allows the operator
to set up and run reports from performance data stored in the database.
Scheduled PM Reports (23349)

This feature provides the facility to schedule performance management reports. This
capability is provided by Business Objects.
PM Statistics Customisation for USR1.0 (23198)

This feature provides the mechanism for the collection of Node B R1 and RNC R1 provided statistics
and the parsing of the network provided statistics into the database. In addition, the statistics are stored
for up to 14 days in the database. The statistics themselves are created in accordance with the relevant
specifications and are based on a collection interval in the network element of 30 minutes. Customisation
also covers the work required to publish the PM schema for 3rd Party Statistics support.
Performance Management Synchronisation for UTRAN (23350)

This feature automatically retrieves Performance Management data from the UTRAN Network Elements
that it may have missed due to, for example; link outages, Manager upgrades.
10-22 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Interfaces from OMC-U to higher level management
Interfaces from OMC-U to higher level management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Motorola has implemented interfaces on the OMC to allow integration of the OMC with
the Network Operator’s existing OSS packages.
Fault Management IRP
Motorola has implemented a standards-based Northbound Interface for the OMC. In the first
commercial release, this provides full support for alarm information. In future releases this
will migrate to become a full two-way fault and configuration management API. The standards
specify a number of technologies that can be used to enable the interface, Motorola has chosen
to implement a CORBA based IRP in line with industry trends.
Interface to Network Performance Management (Metrica)
For Performance Management, an interface is available directly linking Metrica NPR

Performance Alarm Server and the OMC. This allows historical data to be passed to Metrica
so that network wide analysis can be performed.
OMC-U interface features
3GPP PM file format (XML file format) (23206)

This feature provides support of the 3GPP Standard Performance Management (PM)
file format as defined in 3GPP release 5.
Support for 3GPP IRP FM Northbound Interface to NMC (23197)

See "Optional OMC-U features in USR1.0" on page 10-29 for details.
68P02905W21-B 10-23
02-Jun-2004
OMC-U Security Management Chapter 10: OMC-U and its USR 1.0 features
OMC-U Security Management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
As modern telecommunication networks evolve into more open architectures, especially IP based networks,
the various NEs must implement some level of protection against unauthorized access.
Motorola UMTS network security is provided at the edge of the NE. Once a management request arrives and
is accepted by the NE, it is routed within the platform in an unsecured manner. Only if the message exits
the NE is it re-secured. If a security violation is found, an alarm is raised to the element manager.
Security performed by the network elements
The network elements preform the following security:

• Encrypt all outgoing traffic over all external (to the NE) interfaces.
• Provide the ability to set the encryption algorithm for all outgoing traffic
over the external (to the NE) interfaces.
• Authenticate incoming traffic on a per packet basis for all external (to the NE) interfaces.
• Secure access to all physical resources/systems.
• Upon detection of a security violation, send an alarm notification to the manager.
• Log all security violations (including type of violation and the time/date
when the violation occurred).
• Upon request from the manager, supply a list of all security violations.
User authentication and control of user access
Security management involves both user authentication and control of user access.
User authentication is achieved by checking the validity of the username/password combination
entered by the user when they attempt to log on to the system.
Access control is administrated by the security administrator, and is on a per operation basis. For example,
operator 1 may not be allowed to perform Configuration Management operations.
Access control is also avaialble on a per region basis. For example, operator 1 may have no
access, read-only access, or read/write access to a region. If the user has read-only access to a
region, their access privileges are redundant. If the user has read/write access to a region, their
access privileges are those defined by their user access privileges.
10-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U Security Management
Logged operator actions
All operator actions are recorded in logs, which can be searched.

The OMC logs the following:
• Failed account acccess:
◦ A user account is locked for a period of 30 minutes following three successive failed
login attempts. The Administrator account is exempt from lockout.
◦ A user account is disabled after five failed login attempts. Re-enabling the
account requires action by the Administrator. The Administrator account is not
disabled as a result of any number of failed login attempts.
• Account access:
◦ All successful logins are logged.
◦ All unsuccessful logins are logged.
◦ All new account creations are logged.
◦ All account modifications are logged.
OMC-U Security Management features
User account and access control management (User Profile Editor) (23179)
This feature allows the management of user accounts and the specification of user account access
rights. Access Control is a set of mechanisms that prevent a given user from accessing part
of the management information when running an application.
Access Control can be applied to either or both of the following:
• A network entity instance and its associated attributes.
• A command and its associated parameters. For example, an operator could be restricted
to the Alarm Handling function, with a single Operation Context (managed object)
active, and be denied access to the commands Create and Delete.
Access control is also used to control access to system versions for CPA for OMC-U.
68P02905W21-B 10-25
02-Jun-2004
OMC-U general application functions Chapter 10: OMC-U and its USR 1.0 features
OMC-U general application functions

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
OMC Workspace
The OMC Workspace acts as a container within which the OMC applications run. From the Workspace
the operator can open the applications, such as Navigator, Table, and Map.
A useful facility to the OMC operator is the ability to save their current Workspace layout
including the applications that are currently running, this allows an operator to restart their
workspace with their familiar customised desktop without the need to restart all the applications
which the operator would normally have running.
Some customisation of the applications launched from the Tools Menu of the operator workspace is
possible. Operators are able to add and remove programs and tools, such as, Notepad.
Customer-definable network regions
Network regionalisation allows the OMC administrator to subdivide the network into regions
to support the division of responsibilities between members of the customer operations
staff and the field maintenance organisation.
A region is a defined subset of the network elements, which are within the scope of control
of the OMC. The region editor provides a graphical mechanism to create and maintain one or
more regions for network monitoring and maintenance purposes.
OMC Help facility
Motorola have chosen to use the Microsoft[Symbol_registersans] HTML Help, which is the
standard help system for the Windows platform. This information delivery system has enabled
Motorola to develop a user-friendly context sensitive help for the OMC. Context sensitive help
can be picked up from the alarm and map windows, providing all the relevant information
allowing an operator to quickly ascertain the cause of the fault.
In the HTML Help system, one window lets the operator view a directory tree of help topics, an
index of all topics, or a search tool. Another window displays the topic they choose. As the operator
moves from topic to topic, the directory tree always keeps track of where they are in the hierarchy,
stopping the operator from getting lost in the layers of help screens.
The Help facility provides the following functionality:
• A full text search, which makes searches faster and more efficient.
• A Favourites tab, which enables operators to save a list of topics they use most often.
10-26 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview OMC-U general application functions
• Context-sensitive help is available from all applications for:

◦ Menu commands.
◦ Dialog boxes.
◦ Toolbar buttons.
• The Parameters view can provide help on attributes displayed within the view. Information
provided includes the type of attribute (integer, string, and so on), valid range of the attribute
and the effect of changing the attribute on other equipment within the network.
• The Alarm view provides help on alarms appearing within the view. Information
provided by the Help include the likely cause of the alarm, typical subscriber
impacts and possible solutions to the problem.
• All topics within the OMC Help system are displayed in a hierarchical format for
easy navigation and quick location of information required.
• Topics are indexed on keywords providing an alternative to the table of content’s view.
OMC-U general application features
Operation Context Setup (Editor) (23180)

This feature allows the operator to define a particular view of alarm activity in a management domain (or
domain tree). By assigning appropriate values to the available arguments when an operation context is created,
the user defines how the alarm handling feature is to behave to fulfil some aspect of problem management.
Domain Editor (Region Editor) (23182)

Entities in the network can be grouped into subsets based on any criteria, such as, geographic, functional,
and technical. The Domain Editor allows the creation of these groupings (referred to as domains).
There are two types of domains:
• Visualisation domains - associated with the Map application.
• Collection domains - relate to the Alarm window.
Map Editor (23184)

This feature provides a simple mechanism to define and maintain regional geographical and topological maps.
The Map Editor enables users to represent network elements on maps (via symbols), create
relationships between symbols, and build comprehensive map hierarchies for the purposes
of monitoring and/or browsing network equipment.
Automatic generation of maps is possible using the update_maps directive. When this directive
is run, the configuration of the Node Bs and RNCs on the system is determined and the maps
are automatically updated to reflect this configuration.
68P02905W21-B 10-27
02-Jun-2004
OMC-U general application functions Chapter 10: OMC-U and its USR 1.0 features
Workspace (23181)
The purpose of the Workspace is to provide a focal point for the entire routine operations and maintenance
application. All user interface components are launched from the Manager Workspace, and are contained
within the borders of the window. The user can save their Workspace layout.
UTRAN Map (23183)

This feature provides a graphical overview of the location, connectivity and status of network
components and their associated links in any given region.
Maps are used to display a network structure based on criteria defined by the user (that is, maps
can be based on buildings, equipment, or geography). They can be used for Browsing part (or
all) of a network, or for monitoring alarm and state information.
Entity Browser (Navigator) (23187)

This fetaure allows the operator to use the Navigator window to navigate the network hierarchy. All
entities managed by the OMC-U are displayed on the Entity Browser (Navigator window).
Online Help - Contextual for Alarms and Events (23201)

This feature provides contextual help for alarms and events. This provides hooks from alarms
and events into the help contents for the selected items.
Help Customisation for USR1 (23367)

This feature provides help to support Alarms and Events for contextual help provided on the OMC-U.
Call Trace (Display) (23186)

The Call Trace feature allows the operator to identify signalling path and bearer route (NEs and
interconnects) taken for a given subscriber. It is also possible to utilize streaming statistics from NEs.
It is possible to limit the number of active simultaneous subscriber traces.
10-28 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Optional OMC-U features in USR1.0
Optional OMC-U features in USR1.0

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The optional features in USR1.0 are:

• Support for 3GPP IRP FM Northbound Interface to NMC (23197)
• Web Access Server (22044)
Support for 3GPP IRP FM Northbound Interface to NMC (23197)
Summary
Motorola has implemented a standards based Fault Management (FM) Integration Reference Point (IRP)
for the OMC-U. This provides support for alarm information to be sent from the OMC-U to the OSS,
and for the OSS to acknowledge alarms and resynchronise with the OMC-U. The standards specify a
number of technologies that can be used to enable the interface, Motorola has chosen to implement
a CORBA based IRP in line with industry trends. Efficiency gains from using standardised systems
will provide operability advantages and Opex benefits in a number of areas.
Standards
Description
Support the 3GPP IRP standard northbound interface. This provides full support for access to
alarms information as outlined in the current release of the 3GPP standards.
To run the Northbound Interface (Corba FM IRP), additional hardware will be required in the form
of a Netra 20 server (or similar), running Solaris 2.8 or newer. This additional hardware is required
to ensure that the main server does not suffer any performance impact when dealing with a large
volume of alarms to be forwarded to the OSS. The additional software runs on this new hardware
and enables communication between the OMC and the OSS using CORBA.
68P02905W21-B 10-29
02-Jun-2004
Optional OMC-U features in USR1.0 Chapter 10: OMC-U and its USR 1.0 features
Benefits
• Operating and analysing a network from a single or reduced number of O&M systems can
improve network operability. Efficiency gains are achieved through the required operator
knowledge of only a single package, reduced data transfer (and hence errors) between
systems, and management simplicity when using single interface package.
• Significant cost of ownership reductions can be achieved through operating and analysing
a network from a reduced number of O&M systems. Gains are achieved through reduced
training costs, reduced system management costs, and reduced number of operational staff.
Web Access Server (22044)
Summary
The Web Access Server is designed to offer OMC functionality to users who are either remote
from the management centre, or are only occasional users of the information. Through a standard
browser window, the operator has the ability to connect to one or more Motorola OMCu and
access the full functionality (dependant on their security permissions).
Standards
This Web Access Server complies with relevant IETF recommendations.
Description
The Web Access Server is designed to offer OMC functionality to users who are either remote
from the management centre, or are only occasional users of the information. Through a standard
browser window, the operator has the ability to connect to one or more Motorola OMC-Us and
access the full functionality (dependant on their security permissions).
Motorola recommends that the web access server be used to enable access across a corporate
intranet or other secure link, such as VPN. By configuring the system in this way, three levels of
security ensure that only operators with the correct permissions access the OMC. The first level of
security will be access to corporate intranet or VPN, the second level of security is a log-in to the
web server itself, and the third level is the operators existing OMC log-in.
The standard OMC-U screens are all preserved by the web access server, as are all of the standard
operations such as popup menus, mouse button actions and multiple screens (within the browser). This
ensures that operators are already familiar with the procedures needed to manage the network, and they
understand the information being given to them and the way in which it is presented.
By supporting browser based access to the OMC, Motorola is allowing operators to achieve
flexibility in their workstation architecture. The browsers supported can be run on a Unix or
Windows workstation depending upon operator requirements. An additional benefit of this approach
is the ability for an operator to multitask using the same terminal.
10-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Optional OMC-U features in USR1.0
Benefits
For network operators with OMCs spread across a wide geographic area, this feature provides
an opportunity to reduce OpEx: through the consolidation of OMC operators to a single location
without the need for a full network management centre or alternatively by allowing OMC
operators to manage multiple OMCs from wherever they are, thus maximising their efficiency and
reducing travel expenditure. This will become more important to a wider number of operators as
consolidation and network sharing agreements become more widespread.
The use of web browser access allows operators to achieve flexibility in their operator terminal architecture.
Operators will no longer be restricted to terminals that are dedicated to OMC functionality, they will be
able to carry out multiple taks from a single workstation. This will only be made more relevant with the
social shifts in working practices towards remote working and working from home.
The web access interface exactly replicates the standard OMC screen down to the functions of individual
mouse buttons. This replication ensures that the full OMC functionality is preserved, and that operators
do not have to learn a new interface or procedures thus reducing training costs.
68P02905W21-B 10-31
02-Jun-2004
Optional OMC-U features in USR1.0 Chapter 10: OMC-U and its USR 1.0 features
10-32 68P02905W21-B
02-Jun-2004
Chapter
11
Glossary of abbreviations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02905W21-B 11-1
02-Jun-2004
Numbers Chapter 11: Glossary of abbreviations
Numbers
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
# Number.
10/100BASE-T An Ethernet implementation in which the physical
medium is an unshielded twisted pair of wires
capable of carrying data at either 10 or 100 Mbps on
the same port.
1G mobile network First generation mobile network. The initial
category of mobile wireless networks which uses
analog technology only.
2G mobile network Second generation mobile network. Generic term
referring to the category of mobile wireless networks
that first implemented digital technology. GSM is an
example of a 2G mobile network standard.
2G+ mobile network Second generation plus mobile network. Generic
term referring to the category of mobile wireless
technology that supports data rates higher than 2G.
GPRS is an example of a 2G+ mobile network
standard.
3G mobile network Third generation mobile network. Generic term
referring to the category of next-generation mobile
networks. UMTS is an example of a 3G mobile
network standard.
2 Mbit/s link 4-wire As used in this manual set, the term applies to the
European E1 digital line or link which can carry 30
A-law PCM channels or 120 16 kbit/s channels.
3GPP 3rd Generation Partnership Program.
3PNEM 3rd Party Network Element Manager.
11-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview A
A
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
A Interface Interface between MSC and BSS. The interface is

based on the use of one or more E1/T1 digital links.
The channels on these links can be used for traffic or
signalling.
AA Anonymous Access.
AAA Authentication, Authorization, and Accounting
Server.
AAL ATM Adaption Layer.
AAL2 ATM Adaption Layer of type 2.
AAL5 ATM Adaption Layer of type 5.
AA-TID Anonymous Access-Tunnel IDentifier.
AB Access Burst. Used by the MS to access the BTS
and start a call.
Abis interface Interface between a remote BSC and BTS.
ABR Available Bit Rate.
ac-dc PSM AC-DC Power Supply module.
ac/AC Alternating Current. In electricity, AC occurs when
charge carriers in a conductor or semiconductor
periodically reverse their direction of movement.
Household utility current in most countries is AC
with a frequency of either 50 or 60 hertz (complete
cycles per second). The RF current in antennas
and transmission lines is another example of AC.
An AC waveform can be sinusoidal, square, or
sawtooth-shaped. Some AC waveforms are irregular
or complicated. Square or sawtooth waves are
produced by certain types of electronic oscillators,
and by a low-end UPS when it is operating from
its battery.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control. A method by which
congested switches automatically communicate their
congestion level to other switches.
Access Burst The Access Burst is used by the MS to access the
BTS. It carries RACH uplink from the MS to the
BTS to start a call.
ACCH Associated Control CHannel. Control information
associated with TCH or DCCH.
ACIR Adjacent Channel Interference Ratio.
68P02905W21-B 11-3
02-Jun-2004
A Chapter 11: Glossary of abbreviations
ACK ACKnowledgement.
ACLR Adjacent Channel Leakage Power Ratio.
ACM Accumulated Call meter. The ACM is a function
contained within the SIM. It accumulates the total
units (in the home currency) for both the current
call and all preceding calls. For security reasons,
the SIM only allows the value of the ACM to be
incremented, not decremented. Resetting of the
ACM is only possible after entering PIN2.
ACM Address Complete Message.
ACPIM AC Power Interface Module. Used in M-Cell6
indoor ac BTS equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS
equipment.
ACS Adjacent Channel Selectivity.
ACSE Associated Control Service Element. One of 3
Application Service Elements that reside in the
application layer of the OSI protocol stack and act
as an interface to the lower layer protocols.
Active mode The state of a User Equipment when processing a
call.
Active Set Set of radio links simultaneously involved in a
specific communication service between an User
Equipment and a UTRAN access point.
ACU Antenna Combining Unit.
Adaptive Terminal Terminal equipment with the capability of adapting
to more than one type or variation of network.
ADC ADministration Centre.
ADC Analogue to Digital Converter. A device that
converts a signal that is a function of a continuous
variable into a representative number sequence
carrying equivalent information.
ADCCP ADvanced Communications Control Protocol. A
data link protocol used to provide point-to-point and
point-to-multipoint transmission of data frames that
contain error control information. ADCCP is similar
to HDLC.
ADM Add and Drop Multiplexer.
ADMF ADMinistration Function. An LI function that
interfaces with the LEAs and GSNs, and keeps
concurrent interception activities separate.
ADN Abbreviated Dialling Number. A telephone service
feature that enables a user to access a network by
dialling less numbers than standard.
11-4 68P02905W21-B
02-Jun-2004
ADPCM Adaptive Differential Pulse Code Modulation. A

form of PCM that produces a digital signal with a
lower bit rate than standard PCM.
AE Application Entity.
AEC Acoustic Echo Control. In a system, the reduction
of the power level of an echo, or the elimination of
an echo.
AEF Additional Elementary Functions.
AESA ATM End System Address.
AET Active Events Table. Alarms and events are sent
to the Events Log in the GUI. Different operators
will have different subscription lists. All alarms and
events are sent to the AET before they are re-routed
to different subscription lists.
AFC Automatic Frequency Control. A device or circuit
that maintains the frequency of an oscillator within
the specified limits with respect to a reference
frequency.
AFN Absolute Frame Number.
AGC Automatic Gain Control. A process or means by
which gain is automatically adjusted in a specified
manner as a function of a specified parameter such
as received
AGCH Access Grant CHannel. A GSM common control
channel used to assign MS to a SDCCH or a TCH.
agent In the client-server model, the part of the system that
performs information preparation and exchange on
behalf of a client or server application.
AH Authentication Header.
Ai Action indicator.
AI Artificial Intelligence. A branch of computer
science whose goal is to develop electronic devices
that can operate with some of the characteristics
of human intelligence. Among these properties
are logical deduction and inference, creativity, the
ability to make decisions based on past experience
or insufficient or conflicting information, and the
ability to understand natural language.
AI Acquisition Indicator.
AIB Alarm Interface Board.
AICH Acquisition Indication Channel. (Physical Channel)
AIN Advanced Intelligent Network.
Air interface The radio link between the BTS and the MS.
Alarm Notification that a rising or falling threshold has
been crossed.
68P02905W21-B 11-5
02-Jun-2004
ALCAP Access Link Control Application Parameter.

Generic name for the transport signalling protocols
used to setup and tear-down transport bearers.
ALG Application Level Gateway.
AM Acknowledged Mode (of RLC).
AM Amplitude Modulation. Modulation in which the
amplitude of a carrier wave is varied in accordance
with some characteristic of the modulating signal.
AMA Automatic Message Accounting (processor). A
service feature that automatically records data
regarding user-dialled calls.
AMR Adaptive Multi Rate (Transcoder).
AMRC Adaptive Multi Rate Control
AN Access Network.
ANSI American National Standards Institute. Voluntary
organization that acts as a facilitator for developing
US and international business standards.
Antenna A transmitter/receiver which converts electrical
currents into RF and vice versa. In GSM systems,
transmits and receives RF signals between the BTS
and MS.
AoC Advice of Charge.
AoCC Advice of Charge Charging supplementary service.
AoCI Advice of Charge Information supplementary
service.
AOC Automatic Output Control.
AOI Advance Operational Impact.
AP Access Preamble.
API Application Programming Interface. Means of
communication between two programs to give one
program transparent access to the other.
APN Access Point Name. Identifies the PDN to which an
MS wishes to connect. The internal DNS function
translates the APN into the IP address of the GGSN.
Application Layer The highest of 7 protocol layers in the OSI model. It
performs application services and issues requests to
the Presentation Layer.
Applied Load The GPRS application data such as email that is
carried on GPRS carrier timeslots from all of the
MSs in a cell.
Architecture Overall design and structure of a network or
communications system. The architecture influences
the capabilities and limitations of the system.
11-6 68P02905W21-B
02-Jun-2004
ARFCN Absolute Radio Frequency Channel Number. An

integer which defines the absolute RF channel
number.
ARP Address Resolution Protocol. A protocol that
resolves a Network Layer IP address to a Data Link
Layer address when IP is used over Ethernet.
ARQ Automatic repeat Request.
AS Access Stratum.
ASC Access Service Class.
ASCE Association Control Service Element. An ASE
which provides an AP with the means to establish
and control an association with another AP in a
remote network entity. Maps directly onto the
Presentation layer.
ASCII American Standard Code for Information
Interchange. An ANSI standard where each
alphabetic, numeric or special character is
represented by a 8-bit (7 bits plus parity) binary
number.
ASE Application Service Element. A coherent set of
integrated functions used to communicate with an
application entity.
ASE Application Specific Entity (TCAP).
ASIC Application Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One. A formal
notation used for describing data transmitted by
telecommunications protocols.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio. The percentage of calls that
are completed successfully.
ATC ATM Transfer Capability.
ATB All Trunks Busy. An equipment condition in which
all trunks (paths) in a given trunk group are busy.
ATI Antenna Transceiver Interface.
ATM Asynchronous Transfer Mode.
ATT (flag) ATTach.
ATTS Automatic Trunk Testing Subsystem. Ensures the
quality of telephone lines by means of a series of
tests. ATTS can be initiated by either an operator
command or by a command file, which can be
activated at a predetermined time.
AUG Administrative Unit Group.
68P02905W21-B 11-7
02-Jun-2004
AuC Authentication Centre. A GSM network entity

which provides the functionality for verifying the
identity of an MS when requested by the system.
Often a part of the HLR.
AU-n Administrative Unit n with n being xxx.
AUI Attachment Unit Interface.
Authentication and authorization A method of verifying the identity of a user,
validating a service request, and authorizing the
user’s use of the service.
Autonomous system A collection of networks under a common
administration sharing a common routing strategy.
An autonomous system is assigned a unique 16-bit
number by the IANA.
AWGN Additive White Gaussian Noise.
AYA Are You Alive. A heartbeat request.
11-8 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview B
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
B channel Bearer channel. Used in ISDN services to carry

64kbit/s of data, when used at full capacity.
B Interface Interface between MSC and VLR.
BA BCCH Allocation. The radio frequency channels
allocated in a cell for BCCH transmission.
Backbone A LAN or WAN that interconnects bridges, switches
and routers.
Backplane The main data bus within a device.
BAIC Barring of All Incoming Calls supplementary
service.
BAM Back Administration Module.
Bandwidth A measure of the range of frequencies occupied by
a signal.
BAOC Barring of All Outgoing Calls supplementary
service.
Baud The unit in which the information carrying capacity
or signalling rate of a communication channel is
measured. One baud is one symbol (state transition
or level-transition) per second. This coincides with
bits per second only for two-level modulation with
no framing or stop bits
BBBX Battery Backup Board.
BBH Base Band Hopping. Method of frequency hopping
in which each transceiver at the base station is tuned
to a different frequency, and the signal is switched to
a different transceiver for each burst.
Bc Committed Burst size. The maximum amount of
data (in bits) that the network agrees to transfer,
under normal conditions, during a time interval Tc.
BCC Base station Colour Code. The BCC and the NCC
are part of the BSIC. The BCC comprises three bits
in the range 000 to 111. See also NCC and BSIC.
BCD Binary Coded Decimal. The representation of a
decimal digit by a unique arrangement of no fewer
than four binary digits.
BCCH Broadcast Control Channel (logical channel)
BCF Base station Control Function. The GSM term for
the digital control circuitry which controls the BTS.
In Motorola cell sites this is a normally a BCU
which includes DRI modules and is located in the
BTS cabinet.
68P02905W21-B 11-9
02-Jun-2004
B Chapter 11: Glossary of abbreviations
BCFE Broadcast Control Functional Entity.

BCH Broadcast Channel (transport channel)
The BCH is a downlink transport channel that is used
to broadcast system and cell specific information.
The BCH is always transmitted over the entire cell.
BCIE Bearer Capability Information Element. Specific
GSM parameters in the Setup message are mapped
into a BCIE for signalling to the network and within
the PLMN. The BCIE is used to request a bearer
service (BS) from the network.
BCUP Base Controller Unit Power.
Be Beryllium.
Be Burst Excess size. The maximum amount of
uncommitted data (in bits) in excess of Bc that a
Frame Relay network can attempt to deliver during
a specified interval. The network delivers this data
with a lower probability of success than the Bc size.
BECN Backward Explicit Congestion Notification. Bit
set by a Frame Relay network in frames that are
travelling in the opposite direction opposite to
frames passing through a congested path.
BER Bit Error Rate. A measure of signal quality in the
GSM system.
BES Business Exchange Services.
Best effort A service model providing minimum performance
guarantees, allowing an unspecified variance in the
measured performance criteria.
BFL, BRDFAIL Board Failure.
BG Border Gateway. Router that communicates with
routers in other autonomous systems.
BGW Border Gateway.
BGP Border Gateway Protocol. An Internet protocol
that enables groups of routers to share routeing
information so that efficient, loop-free routes can
be established. BGP is commonly used within and
between ISPs.
BH Busy Hour. In a communications system, the sliding
60-minute period that carries the maximum total
traffic load in a 24-hour period.
BHCA Busy Hour Call Attempt.
BI Barring of all Incoming call supplementary service.
BIC-Roam Barring of all Incoming Calls when Roaming outside
the Home PLMN Country supplementary service.
BID Binding Identity.
11-10 68P02905W21-B
02-Jun-2004
BIM Balanced-line Interconnect Module.

Bin From BINary. An area in a data array used to store
information. Also, a name for a directory that
contain files stored in binary format.
bit Binary digit. A character used to represent one of the
two states or digits (0 or 1) in the binary numbering
system.
bit/s Bits per second. A measure of data transmission
speed - the number of bits transmitted in one second.
BITS Building Integrated Timing Supply.
BER Bit Error Rate.
BL Boot Load. Also known as download.
BLER Block Error Rate.
block A group of bits (binary digits) transmitted as a unit,
over which a parity check procedure is applied for
error control purposes.
Bm Full rate traffic channel.
BN Bit Number. Number which identifies the position
of a particular bit period within a timeslot.
BNET Broadband Network.
BPF Bandpass Filter. A filter that ideally passes all
frequencies between two non-zero finite limits and
bars all frequencies not within the limits.
BPSK Binary Phase Shift Keying.
BPSM µBCU Power Supply Module.
Bottleneck Traffic slowdown resulting from too many network
nodes trying to access a server node at the same time.
Br Burst rate.
BRI Basic Rate Interface. The basic ISDN configuration
which consists of two B-channels that can carry
voice or data at the rate of 64 Kbps, and one
D-channel, which carries call-control information.
Bridge A device that interconnects local or remote networks
forming a single logical network. Bridges operate
at the physical and link layers of the OSI reference
model.
Bridge/router A device that can provide the functions of a bridge
or router, or both concurrently. A bridge/router can
route one or more protocols and bridge all other
traffic.
BS Base Station.
BS Billing System.
BS Basic Service (group).
68P02905W21-B 11-11
02-Jun-2004
B Chapter 11: Glossary of abbreviations
BS Bearer Service. A type of telecommunication service

that provides the capability for the transmission
of signals between user-network interfaces. The
PLMN connection type used to support a bearer
service may be identical to that used to support other
types of telecommunication service.
BSC Base Station Controller. A network component
in the GSM PLMN which has the digital control
function of controlling all BTSs. The BSC can be
located within a single BTS cabinet (forming a BSS)
but is more often located remotely and controls
several BTSs (see BCF, BCU, and BSU).
BSFREQ Billing System Frequency.
BSG Basic Service Group.
BSIC Base Transceiver Station Identity Code. Each cell
has a BSIC. It is a local colour code that allows
a mobile station to distinguish between different
neighbouring base stations. The BSIC is an octet,
consisting of three bits for the Network Colour Code
(NCC) and three bits for the Base station Colour
Code (BCC). The remaining two bits are unused.
See also NCC and BCC.
BSN Backward Sequence Number. A field in a signal
unit (SU) that contains the forward sequence
number (FSN) of a correctly received signal unit
being acknowledged in the signal unit that is being
returned to the sender. See also FSN and SU.
BSP Base Site control Processor (at BSC).
BSS Base Station System. The system of base station
equipment (Transceivers, controllers and so on)
which is viewed by the MSC through a single
interface as defined by the GSM 08 series of
recommendations, as being the entity responsible for
communicating with MSs in a certain area. The radio
equipment of a BSS may cover one or more cells. A
BSS may consist of one or more base stations. If
an internal interface is implemented according to
the GSM 08.5x series of recommendations, then the
BSS consists of one BSC and several BTSs.
BSSAP BSS Application Part. Protocol for LAPD or LAPB
signalling links on the A-interface.
BSSAP+ BSS Application Part Plus. Enhanced version of
BSSAP for signalling across the Gs interface.
BSSC Base Station System Control cabinet. The cabinet
which houses one or two BSU shelves at a BSC
or one or two RXU shelves at a remote transcoder
(RXCDR).
11-12 68P02905W21-B
02-Jun-2004
BSSGP BSS GPRS Protocol. Provides radio-related

information and performs node management
functions between the SGSN and the BSS.
BSSMAP Base Station System Management Application Part.
Call processing protocol for A-interface messages
exchanged between the MSC and BSS.
BSTUN Block Serial Tunnelling.
BSU Base Station Unit shelf. The shelf which houses the
digital control modules for the BTS (part of BTS
cabinet) or BSC (part of BSSC cabinet).
BT British Telecom.
BT Bus Terminator. In order to avoid signal reflections
on the bus, each bus segment has to be terminated
at its physical beginning and at its end with the
characteristic impedance.
BTC Bus Terminator Card.
BTF Base Transceiver Function.
BTP Base Transceiver Processor (at BTS). One of the six
basic task groups within the GPROC.
BTS Base Transceiver Station. A network component
in the GSM PLMN which serves one cell, and is
controlled by a BSC. The BTS contains one or more
Transceivers (TRXs).
Buffer Area in a device for temporary storage of data in
transit. A buffer can accommodate differences in
processing speeds between devices by storing data
blocks until they are ready to be processed.
Burst A period of modulated carrier less than one timeslot.
The physical content of a timeslot.
Bursty traffic An uneven pattern of data transmission.
Bus The physical pathway used to communicate between
the CPU, memory and various input and output
devices.
BVC BSSGP Virtual Connection. A data and signalling
communication path across the Gb interface between
remote BSSGP entities.
BVCI BSSGP Virtual Connection Identifier.
Byte A sequence of adjacent binary digits (usually 8)
operated upon as a unit. A byte is the smallest
addressable unit of information in a data store or
memory.
68P02905W21-B 11-13
02-Jun-2004
C Chapter 11: Glossary of abbreviations
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
C Control.
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 ITU-TSS signalling system number 7, also
sometimes known as SS7, not to be confused with
ANSI SS7. See SS7.
CA Cell Allocation. The radio frequency channels
allocated to a particular cell.
CA Central Authority.
CA Capacity Allocation.
CAA Capacity Allocation Acknowledgement.
CAB Cabinet.
Cabinet Upright frame in which standard equipment can be
installed.
CAC Connection Admission Control.
To decide whether a new ATM or AAL2 connection
can be accepted, meeting its QoS requirements and
still maintaining the QoS of already established
connections and if so what resources should be
allocated.
CADM Country ADMinistration. The Motorola procedure
used within DataGen to create new country and
network files in the DataGen database.
CAI Charge Advice Information.
CALEA Communication Assistance for Law Enforcement
Act (USA).
CAMEL Customized Applications for Mobile Network
Enhanced Logic.
Camped on a cell The UE is in idle mode and has completed the cell
selection/reselection process and has chosen a cell.
The UE monitors system information and (in most
cases) paging information. Note that the services
may be limited, and that the PLMN may not be
aware of the existence of the UE within the chosen
cell.
CAP CAMEL Application Part.
Card A printed circuit assembly.
11-14 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview C
CAT Cell Analysis Tool. The CAT is part of the Motorola

Cell Optimization product. It is intended for
engineering staff and OMC administrators. CAT
provides information about GSM network cell
performance.
CB Cell Balancer. Process that balances the cells
configured for GPRS across PRPs. In the event of a
PRP outage, the process sends messages indicating
that GPRS service is unavailable to the appropriate
Cell Resource Machines for the cells that could not
be moved to an IN Service PRP.
CB Cell Broadcast. See CBSMS.
CBA Cell Broadcast Agent.
CBB Clock Bridge Board.
CBC Cell Broadcast Centre.
CBCH Cell Broadcast CHannel. The channel used to
broadcast messages to all MSs in a specific cell.
CBF Combining Bandpass Filter.
CBL Cell Broadcast Link. A bi-directional data link
which allows communications between the BSS and
the CBC.
CBM Circuit Breaker Module.
CBMI Cell Broadcast Message Identifier.
CBR Constant Bit Rate.
CBS Cell Broadcast Service. See CBSMS.
CBSMS Cell Broadcast Short Message Service. CBSMS
allows a number of unacknowledged general
messages to be broadcast to all MSs within
a particular region. The content may include
information such as local traffic conditions, the
weather, the phone number of the local taxi
company, etc. The messages are sent from a CBC
via a BSC to a BTS and from there on a special
cell broadcast channel to the MSs. The CBC is
considered as a node outside the PLMN and can be
connected to several BSCs. However, a BSC is only
connected to one CBC.
CBUS Clock Bus.
CC Connection Confirm. Part of SCCP network
connectivity.
CC Country Code. A one to three digit number which
specifically identifies a country of the world that an
international call is being routed to (for example, 1
= North America, 44 = United Kingdom).
68P02905W21-B 11-15
02-Jun-2004
CC Call Control. CC functions, such as number

translations and routing, matrix path control, and
allocation of outgoing trunks are performed by the
MSC.
CCB Cavity Combining Block, a three way RF combiner.
There are two types of CCB, CCB (Output) and
CCB (Extension). These, with up to two CCB
Control cards, may comprise the TATI. The second
card may be used for redundancy.
CCBS Completion of Calls to Busy Subscriber
supplementary service.
CCCH Common Control CHannel(s). A class of GSM
control channels used to control paging and grant
access. Includes AGCH, PCH, and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Cluster Configuration Database.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding.
CCH Control Channel. Channels that carry system
management messages.
CCH Council for Communications Harmonization
(referred to in GSM Recommendations).
CCITT Comité Consultatif International Télégraphique
et Téléphonique. This term has been superseded
by ITU-TSS (International Telecommunications -
Telecommunications Sector).
CCM Current Call Meter.
CCP Common Communications Port.
CCPCH Common Control Physical Channel.
The channel used to carry the BCCH. A primary
CCPCH is continuously transmitted over the entire
cell. Primary CCPCH is a fixed rate (32 kbit/s)
downlink physical
The Secondary CCPCH is a constant rate (which
may differ for different cells, depending on the
capacity needed) downlink physical channel used
to carry the FACH and PCH. The FACH and PCH
are mapped to separate secondary CCPCHs. A
secondary CCPCH is only transmitted when there is
data available, and may be transmitted in a narrow
lobe (FACH only) in the same way as a DPCH.
CCPE Control Channel Protocol Entity.
11-16 68P02905W21-B
02-Jun-2004
CCS Hundred call-seconds. A single call lasting one

hundred seconds is one CCS. Also, a measure of
traffic load obtained by multiplying the number of
calls per hour by the average holding time per call
expressed in seconds, and dividing by 100. Often
used in practice to mean hundred call seconds per
hour with “per hour" implied; as such, it is a measure
of traffic intensity. See also erlang.
Cct Circuit.
CCTrCH Coded Composite Transport Channel.
CCU Channel Coder-decoder (Coding) Unit. Performs
channel coding and radio channel measurement
functions.
CD Compact Disk.
CD Capacity Deallocation.
CD Collision Detection.
CDA Capacity Deallocation Acknowledgement.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN
software (crontab - cron job file).
CDMA Code Division Multiple Access.
Consists in allocating a specific code to each
user. It does not break up the signal into time
slots or frequency bands. The signals are decoded
by using knowledge of the user’s code. CDMA
is a form of spread-spectrum, a family of digital
communication techniques. The basic principle
of spread-spectrum is the use of noise-like carrier
waves, and bandwidths much wider than that
required for simple point-to-point communication at
the same data rate.
CDR Call Detail Record. Record written to a database for
use in post-processing activities, primarily billing
and network analysis.
CD-ROM Compact Disk-Read Only Memory.
CDUR Chargeable DURation.
CDVT Cell Delay Variation Tolerance.
Radio coverage area where the cell ID is broadcast.
Cell IDCell identifies the cell within UTRAN.
CEB Control Equalizer Board (BTS).
68P02905W21-B 11-17
02-Jun-2004
CED Called station identifier.

Cell An RF coverage area. At an omni-site, cell is
synonymous with site; at a sectored site, cell is
synonymous with sector. This differs from analog
systems where cell is taken to mean the same thing
as site.
In UMTS: A cell is a geographical area that can
be identified by a User Equipment from a (cell)
identification that is broadcast from one UTRAN
Access Point
CEND End of charge point. The time at which the calling,

or called, party stops charging by the termination of
the call or by an equivalent procedure invoked by
the network or by failure of the radio path.
CENELEC European Committee for Electrotechnical
Standardization.
CEPT Conférence des administrations Européennes des

Postes et Telecommunications, CCITT G.703/704
based European digital transmission facility (2.048
Mbit/s).
CERM Circuit Error Rate Monitor. Identifies discontinuity
in a circuit.
CES Circuit Emulation Service.

CF Conversion Facility.
CF Call Forwarding. A feature available to the mobile
telephone user whereby, after initiation of the feature
by an authorised subscriber, calls dialled to the
mobile telephone of an authorised subscriber will
automatically be routed to the desired number. See
also CFC and CFU.
CF Controlling Function.
CFN Connection Frame Number.
CGF Charging Gateway Function.
CG Charging Gateway. Collects and stores subscriber
accounting data for collection by a Billing System.
CGFu Charging Gateway Function, specific to UMTS.
CGI Cell Global Identity.
CGN CDR Generating Node.
CGW Charging Gateway.
Channel A means of one-way transmission. A defined
sequence of periods (for example, timeslots) in a
TDMA system; a defined frequency band in an
FDMA system; a defined sequence of periods and
frequency bands in a frequency hopped system.
11-18 68P02905W21-B
02-Jun-2004
Chassis An equipment shelf with slots that accept modules

and cards.
China-specific SS7 A variation of ITU SS7 for the People’s Republic
of China.
C/I Carrier-to-Interference ratio.
CI Cell Identity. A block of code which identifies a cell
within a location area.
CIC Circuit Identity Code. A unique identifier for the
terrestrial portion of a circuit path.
C-ID Charging Identification.
CID Channel Identifier.
CIDR Classless Inter-Domain Routing. An newer IP
addressing scheme that replaces the system based on
Classes A, B, and C with one that allows a single IP
address to designate many unique IP addresses.
CIE Cell ID Export. A method of tracing the locations of
MSs attached to an SGSN.
CIM Coaxial Interconnect Module (also called T43).
Ciphertext Unintelligible data produced using encryption.
CIR Committed Information Rate. A specified amount
of guaranteed bandwidth (measured in bit/s) on a
Frame Relay service.
Circuit A communications channel between two or more
points.
CK Cipher Key.
CKSN Ciphering Key Sequence Number. The CKSN is a
number which is associated with the ciphering key,
Kc. It is used to ensure authentication consistency
between the MS and the VLR.
CLASS Custom Local-Area Signalling Services.
Class A Voice only class of MS access.
Class B Voice and data class of MS access.
Class C Data only class of MS access.
CLI Command Line Interface. Software interface in
which commands are entered on the keyboard as
opposed to selecting items from a menu.
CLIP Calling Line Identification Presentation. A
supplementary service that enables a called party to
identify the caller.
CLIR Calling Line Identification Restriction. A
supplementary service that allows a caller to
withhold their identity from the called party.
CLK Clock.
68P02905W21-B 11-19
02-Jun-2004
CLKX Clock Extender half size board. The fibre optic link
that distributes GCLK to boards in system (part of
the BSS, etc).
CLM Connection-Less Manager. Coordinates global
control over the BSS by handling all connection-less
messages including global resets, load limiting and
circuit blocking.
CLNS Connection-Less Network Service. Packet-switched
network in which each packet of data is independent
and contains complete address and control
information. This minimizes the effect of individual
line failure and distributes the load more efficiently
across the network. CLNS does not require a circuit
to be established before data is transmitted.
CLP Cell Loss Priority.
Cluster node The Sun Netra t 1125 component of the ISS Cluster.
CM Compressed Mode.
CM Configuration Management.
CM Call Management (in CM Service).
CMD CoMmanD.
CMIP Common Management Information Protocol. An
OSI standard protocol used with CMIS.
CMIS Common Management Information Service. An OSI
network management service interface that monitors
and controls heterogeneous networks.
CMISE Common Management Information Service
Element.
CMM Channel Mode Modify. Message sent to an MS to
request a channel mode change.
CMOS Complementary Metal-Oxide Semiconductor.
High-speed integrated circuit used in processors.
CMOS uses little power and therefore generates
little heat.
CMP Common Management Platform.
CmCH Common Transport Channel.
CN Core Network.
C-n Container-n (n=1-4).
CNEOMI Common Network Element Operations Management
Interface.
CNR Cisco Network Registrar. A Cisco product that
provides DNS server capabilities to the GSN.
CNRC Customer Network Resolution Centre.
CO2 Carbon Dioxide.
11-20 68P02905W21-B
02-Jun-2004
CODEC COder-DECoder. A speech coding unit that converts

speech into a digital format for radio broadcast, and
vice versa.
CODEX Manufacturer’s name for a type of multiplexer and
packet switch commonly installed at the Motorola
OMC-R.
Coincident Cell A cell whose cell boundary follows the boundary of
a co-located neighbour cell. The coincident cell has
a different frequency type, but the same BSIC, as
that of the neighbour cell.
CoL Change of Location.
Collocated Placed together; two or more items together in the
same place.
Colour Code An 8-bit code assigned to a BTS to distinguish
interfering signals from another cell.
COMB Combiner. The purpose of a combiner in the BSS is
to combine transmitter outputs from the RCUs onto
an antenna.
COMM, Comms COMMunications.
CommHub Communications Hub. Provides Ethernet switching
and IP routeing for the GSN complex local
networking and GSN complex E1 interfaces to the
public data network.
CommsLink Communications Link.
Communications cabinet A cabinet holding the CommHub and ISS Cluster
equipment.
Compact PCI See cPCI.
A service that allows transfer of information among
service users without end-to-end call establishment
procedures.
Congestion Situation occurring when an element cannot receive
all the service it is requesting.
CONP Connection-Oriented Network Protocol.
CONNACK CONNect ACKnowledgement. Part of the
synchronization process. After a connection has
been established, the CONNACK message indicates
that traffic channels are available.
CONS Connection-Oriented Network Service. An OSI
protocol for packet-switched networks that exchange
information over a virtual circuit.
Control channel A logical channel that carries system control
information.
68P02905W21-B 11-21
02-Jun-2004
Controlling RNC A role an RNC can take with respect to a specific

set of UTRAN access points. There is only one
Controlling RNC for any UTRAN access point .
The Controlling RNC has the overall control of the
logical resources of its UTRAN access points.
COSHH Control of Substances Hazardous to Health. 1999
health regulations.
CORBA Common Object Request Broker Architecture
(Object Management Group).
Core Network Service and Transit Network Domains.
COTS Commercial Off-The-Shelf.
CP2/CP5/CP8 Common platform software message protocols.
Coverage area The area over which a UMTS service is provided
with the service probability above a certain
threshold.
CP Call Processing. Process in the BTS that controls the
MS-to-BSS-to-MS signalling link, MS originated
and terminated calls, and inter-BSS and inter-BTS
handovers.
CPCH Common Packet Channel.
cPCI Compact PCI.
CPCS Common Part Convergence Sublayer.
CPE Customer Provided Equipment.
CPGM CCCH Paging Manager. Processes the paging
messages sent from the SGSN to the BSC/BTS.
CPICH Common Pilot Channel.
CPS Common Part Sublayer.
CPU Central Processing Unit.
CPX8216 SGSN chassis hardware model.
CR Connection Request. An SCCP Connection Request
message is sent form the BSS to the MSC to
establish a connection.
CR Change Request.
CRC Cyclic Redundancy Check. An error-detection
scheme that (a) uses parity bits generated by
polynomial encoding of digital signals, (b) appends
those parity bits to the digital signal, and (c) uses
decoding algorithms that detect errors in the received
digital signal.
CRE Call RE-establishment procedure. Procedure for
re-establishing a call in the event of a radio link
failure.
CRNC Controlling Radio Network Controller.
11-22 68P02905W21-B
02-Jun-2004
CRM Cell Resource Manager. The CRM allocates and

activates timeslots and subchannels on the available
carriers.
CRO Controlled Roll Out. A customer site implementation
of a new product, software release, or combination
of products/releases.
CRS Cyclic Redundancy Check.
CRCI CRC Indicator.
CRNC Controlling RNC.
Control-plane and user-plane functions that pertain
to the management of the radio resources for a
particular Node B or cell/sector within the Node B.
c-RNTI RNTI allocated by CRNC.
C-SGSN Common Serving GPRS Support Node.
CS-Service Domain Circuit Switched-Service Domain.
CS Circuit Switched. A method of providing a physical
path dedicated to a single connection between two
end-points in a network, for the duration of the
connection.
CS Coding Scheme.
CS-1 Coding Scheme-1 (9.05 kbit/s per TCH).
CSD Circuit Switched Domain.
CSE CAMEL Service Environment.
CSFP Code Storage Facility Processor (at BSC and BTS).
A GPROC device that facilitates the propagation of
new software with reduced system downtime.
CSI CAMEL Subscription Information
CSP Central Statistics Process. The statistics process in
the BSC.
CSPDN Circuit Switched Public Data Network. A publicly
available communications network using circuit
switched digital data circuits.
CTCH Common Traffic Channel.
CTDMA Code Time Division Multiple Access.
CTL Control.
68P02905W21-B 11-23
02-Jun-2004
CTP Call Trace Product (Tool). The CTP is designed

to help operators of GSM900 and DCS1800
communication networks tune and optimize their
systems. CTP allows Call Trace data to be analysed
and decoded.
CTP Control Terminal Port.
CTS Clear to Send. A handshake signal used with
communication links, especially RS232 or CCITT
Rec. V.24, to indicate (to a transmitter from a
receiver) that transmission may proceed.
CTU Compact Transceiver Unit (M-Cellhorizon radio).
CUG Closed User Group. A supplementary service
used to create a unique group whose members are
authorized to receive or place calls over a specific
interface.
Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service. A subscriber
feature which allows an individual mobile telephone
user currently engaged in a call to be alerted that
another caller is trying to reach him. The user has a
predetermined period of time in which to terminate
the existing conversation and respond to the second
call.
CW Continuous Wave (unmodulated signal).
CW4MW Cisco Works for Mobile Wireless.
11-24 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview D
D
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
D channel Data channel. Used in ISDN to perform call

signalling and connection setup functions. In some
circumstances, the channel can also be used to carry
user data.
D Interface Interface between VLR and HLR.
DAC Digital to Analogue Converter.
DACS Digital Access Cross-connect System.
DAK Downlink Acknowledgement
DAN Digital ANnouncer (for recorded announcements
on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape. A storage device that records
digital information on magnetic tape.
DataGen Sysgen Builder System. A Motorola offline BSS
binary object configuration tool.
Datagram Logical block of data sent as a network layer
unit over a transmission medium without first
establishing a virtual circuit. IP datagrams are the
primary information units in the Internet.
Data Link Layer The second layer in the OSI protocol stack model. It
responds to service requests from the Network Layer
and issues service requests to the Physical Layer.
dB Decibel. A unit of power ratio measurement.
DB Database.
DB Dummy Burst. A period of carrier less than one
timeslot whose modulation is a defined sequence
that carries no useful information. A dummy
burst fills a timeslot with an RF signal when no
information is to be delivered to a channel.
DBA DataBase Administration/Database Administrator.
DBB Data Bus Ready.
dBm A dB referenced to 1 milliwatt; 0 dBm equals one
milliwatt.
DBMS DataBase Management System. A collection of
programs that enable a user to store, modify and
extract information from a database.
DC, dc Direct Current.
DC Dedicated Control (SAP).
DCA Dynamic Channel Allocation.
68P02905W21-B 11-25
02-Jun-2004
D Chapter 11: Glossary of abbreviations
DC PSM DC Power Supply Module.

DCB Diversity Control Board (part of DRCU).
DCCH Dedicated Control Channel.
DCD Data Carrier Detect signal. Hardware signal defined
by the RS-232-C specification that indicates that a
device such as a modem is on-line and ready for
transmission.
DCE Data Circuit terminating Equipment or Data
Communication Equipment. A device that
communicates with a DTE device in RS-232C
communications.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in
Horizonmacro).
DCH Dedicated Channel.
DCN Data Communications Network. A DCN connects
Network Elements with internal mediation functions
or mediation devices to the Operations Systems.
DCS1800 Digital Cellular System at 1800 MHz. A cellular
phone network using digital techniques similar to
those used in GSM 900, but operating on frequencies
of 1710 - 1785 MHz (receive) and 1805 - 1880 MHz
(transmit).
DDN Digital Data Network.
DDS DataGen Data Store. Store area for DataGen input
and output files.
DE Discard Eligibility.
Decryption Applying an encryption algorithm in reverse to
restore data to its original form.
Dedicated line A transmission circuit installed between two sites in
a private network and open, or available, at all times.
Default route Entry in a routing table that redirects any frames for
which the table has no listing for the next hop.
Deployment scenario A description of assumed user density and traffic
to be served by a system in simulations. In the
radio transmission technology selection process, the
deployment scenario serves as a representation of
the ultimate UMTS deployment.
DEQB Diversity Equalizer Board.
DES Data Encryption Standard.
DET DETach.
DF Delivery Function.
DF2 Delivery Function handling IRI data.
11-26 68P02905W21-B
02-Jun-2004
DF3 Delivery Function handling IDP data.

DFE Decision Feedback Equalizer. A receiver
component/function that results in a sharp BER
threshold by using error feedback.
DGT Data Gathering Tool. Collects data relevant to
a specific problem and copies it to tape or file,
together with a problem description. The data is
then sent to Motorola for analysis.
DHCP Dynamic Host Configuration Protocol. A protocol
for assigning dynamic IP addresses to devices on
a network. Dynamic addressing enables a device
to have a different IP address each time it connects
to the network.
DHO Diversity Handover.
Digital signals Discrete high- and low-voltage signals that represent
1s and 0s. Analog signals can be converted to digital
signals using a CODEC.
DISC DISConnect.
Discon Discontinuous.
DIQ Diversity In phase and Quadrature phase.
DIR Device Interface Routine. Software routine used in
the BSS.
DL Data Link (layer). The second lowest layer in the
OSI reference model.
DL Downlink.
DLC Data Link Connection.
DLCI Data Link Connection Identifier. In Frame Relay
transmission, the 13-bit field that defines the
destination address of a packet.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLS DownLink Segmenter. The DLS segments LLC
frames into RLC data blocks to be transmitted over
the air interface.
DLSP Data Link Service Process. Handles messages for a
Operation and Maintenance Processor and a shelf
GPROC.
DLSP Digital Link Signalling Processor.
Dm Control channel. ISDN terminology applied to
mobile service.
DMA Deferred Maintenance Alarm. An alarm report level;
an immediate or deferred response is required).
68P02905W21-B 11-27
02-Jun-2004
DMA Direct Memory Access. Transfer of data from a

peripheral device, such as a hard disk drive, into
memory without that data passing through the
microprocessor. DMA transfers data into memory at
high speeds with no processor overhead.
DMR Digital Mobile Radio.
DMTF Distributed Management Task Force.
DMX Distributed Electronic Mobile Exchange (Motorola’s
networked EMX family).
DN Directory Number.
DNIC Data Network Identifier Code. A CCITT code
where the first 4 digits indicate the international data
number, the next 3 digits are the country code, and
the final digit is the network code.
DNS Domain Name Service. A service that translates
from logical domain or equipment names to IP
addresses.
Downlink A unidirectional radio link for the transmission
of signals from a UTRAN access point to a User
Equipment.
DP Detection Point.
DPC Digital Processing and Control.
DPCCH Dedicated Physical Control Channel.
The DPCCH is an uplink physical channel that is
used to carry control information of known pilot
bits to support channel estimation for coherent
detection, transmit power control (TPC) commands,
and an optional transport format indicator (TFI). The
TFI informs the receiver about the instantaneous
parameters of the different transport channels
multiplexed on the uplink
There is only one uplink DPCCH on each
connection.
DPCH Dedicated Physical Channel.
The DPCH is the only downlink physical channel
and is used to carry dedicated data for the DCH,
with control information (known pilot bits, TPC
commands and an optional TFCI).
DPCM Pulse-code modulation (PCM) in which an analog
signal is sampled and the difference between the
actual value of each sample and its predicted value,
derived from the previous sample or samples, is
quantified and converted, by encoding, to a digital
signal. Note: There are several variations of
differential pulse-code modulation.
DPDCH Dedicated Physical Data Channel.
11-28 68P02905W21-B
02-Jun-2004
The DPDCH is an uplink physical channel that is

used to carry dedicated data generated for the DCH.
There may be zero, one or several uplink DPDCHs
on each connection.
DPNSS Digital Private Network Signalling System (BT
standard for PABX interface).
DPP Dual Path Preselector. BTS module.
DPR, DPRAM Dual Port Random Access Memory.
DPROC Data PROCessor board (in PCU).
DPSM Digital Power Supply Module.
DRAC Dynamic Resource Allocation Control.
DRAM Dynamic RAM. A memory technology characterized
by high density and low power.
DRC Data Rate Converter board. Provides data and
protocol conversion between PLMN and destination
network for 8 circuits (p/o IWF).
DRI Digital Radio Interface. Part of the BSS. Provides
encoding/decoding and encryption/decryption for
radio channels.
Drift RNS The role an RNS can take with respect to a specific
connection between a User Equipment and UTRAN.
An RNS that supports the Serving RNS with
radio resources when the connection between the
UTRAN and the User Equipment need to use cell(s)
controlled by this RNS is referred to as Drift RNS.
DRIM Digital Radio Interface Module. A DRI with extra
memory.
DRNC Drift RNC.
Control-plane functions that pertain to the
management of a particular user’s radio access
signalling and bearer connection to the Iur interface.
DRNS Drift RNS.
DRT Data Record Transfer in GPRS Charging.
DRX Discontinuous Reception. A means of saving battery
power by periodically and automatically switching
the MS receiver on and off.
DS Differentiated Services.
DS0 Digital Service Zero (0). A single 64 kbit/s timeslot
on a T1digital interface.
DS-1 Digital transmission System 1 (or Digital Signal
level 1). Term used to refer to the 1.44 Mbit/s (U.S.)
or 2.108 Mbit/s (Europe) digital signal carried on a
T1 facility.
DS-2 German term for 2 Mbit/s line (PCM interface).
68P02905W21-B 11-29
02-Jun-2004
DS-CDMA Direct-Sequence CDMA.

DSCH Downlink Shared Channel.
The DSCH is a downlink transport channel shared
by several UEs carrying dedicated control or traffic
data.
DSCP DiffServ Code Point (IP header DS byte)
DSE Data Switching Exchange.
DSI De-serialising Interface.
DSP Digital Signal Processor. A specialized,
programmable computer processing unit that can
perform high-speed mathematical processing.
DSS Digital Subscriber Signalling. An ISDN user
network interface method of signalling.
DTAP Direct Transfer Application Part.
DTCH Dedicated Traffic Channel.
DTE Data Terminal Equipment. An end instrument
that converts user information into signals for
transmission, or reconverts the received signals into
user information.
DTF Digital Trunk Frame. A frame or electronic rack of
digital trunk interface equipment.
DTI Digital Trunk Interface.
DTMF Dual Tone Multi-Frequency
DTR Data Transfer Rate.
DTX Discontinuous Transmission. A method of saving
battery power and reducing interference by
automatically switching the transmitter off when no
data or speech is being sent.
Dummy burst A period of carrier less than one timeslot whose
modulation is a defined sequence that carries no
useful information. A dummy burst fills a timeslot
with an RF signal when no information is to be
delivered to a channel.
DVD Digital Video Decoder.
Dynamic routeing Routeing that adjusts automatically to changes in
network topology or traffic.
DYNET DYnamic NETwork. Used to specify BTSs sharing
dynamic resources.
11-30 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview E
E
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
E See Erlang.
E1 2 Mbit/s digital transmission link (32 x 64 kbit/s
timeslots).
E2E End-to-End.
E Interface Interface between MSC and MSC.
EA External Alarm. See EAS. Typical external alarms
are: Door open, High humidity, Low humidity, Fire,
Intruder.
EAS External Alarm System. The EAS is responsible
for the monitoring of all customer-defined
environmental alarms at a site. The customer defines
the alarm string and the severity of the alarms
based on the individual requirements of the site.
Indications are provided when the alarms are set or
cleared.
Eb/No Energy per Bit/Noise floor, where Eb is the signal
energy per bit and No is the noise energy per hertz
of noise bandwidth.
EB E-business
EBCG Elementary Basic Service Group.
EC Echo Canceller. Performs echo suppression for all
voice circuits. If cancellation does not take place,
the PLMN subscriber hears the voice signal as an
echo, due to the total round-trip delay introduced by
the GSM system (typically 180 ms).
ECC Error Correction Code.
ECID The Motorola European Cellular Infrastructure
Division.
ECM Error Correction Mode. A facsimile mode, in which
the sending machine will attempt to send a partial
page up to four times.
Ec/No Ratio of energy per modulating bit to the noise
spectral density.
ECT Explicit Call Transfer.
EDGE Enhanced Data rates for Global Evolution. An
extension to the GSM standard that provides higher
speed access.
EDP Event Detection Point. A Prepaid Service event,
which is reported in the context of an existing
relationship between the GSN and the P-SCP, for
a specific PDP context.
68P02905W21-B 11-31
02-Jun-2004
E Chapter 11: Glossary of abbreviations
EDP-R EDP Request.

EDP-N EDP Notification.
EE Equipment Engineering.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable ROM.
Read-Only Memory. EPROM that can be erased
using electrical signals applied to specific pins. See
also EPROM.
EFCI Explicit Forward Congestion Indicator.
Effective Load This is the true load carried by a cell from all of the
mobiles after the Applied Load has been wrapped by
the GPRS protocols and weighted by the expected
BLER, V.42 bis data compression, and TCP/IP
header compression.
EFR Enhanced Full Rate. A voice coding algorithm.
EGP Exterior Gateway Protocol. Internet routing protocol
by which gateways exchange information about
which systems they can reach.
EGPRS Enhanced GPRS.
EGSM900 Extended GSM900. EGSM900 provides the BSS
with a further range of frequencies for MS and
BSS transmit. EGSM MSs can use the extended
frequency band as well as the primary band, while
non-EGSM MSs cannot use the extended frequency
band. A GSM900 cell can contain both GSM900
and EGSM900 carrier hardware. EGSM operates on
the frequency range, 880 - 915 MHz (receive) and
925 - 960 MHz (transmit).
EIDE Enhanced Integrated Design (Disk) Electronics.
EIR Equipment Identity Register. Contains a centralized
database for validating the IMEI.
EIRP Equivalent Isotropic Radiated Power.
EL Echo Loss.
EM Event Management. An OMC-R application.
It provides a centralised facility for reporting
network-wide generated events and alarms, and for
monitoring the status of the Network.
EMC Electromagnetic Compatibility.
EMF Electro Motive Force. The rate at which energy
is drawn from a source that produces a flow of
electricity in a circuit; expressed in volts.
EMI Electromagnetic interference
Encapsulation Wrapping a data unit with a protocol header
containing address and control information.
11-32 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview E
Encryption Applying a specific algorithm to data in order to

alter the appearance of the data and prevent other
devices from reading the information.
EPROM Erasable Programmable Read-Only Memory.
Nonvolatile memory chips that are programmed
after manufacture and can be erased and
reprogrammed. See Also EEPROM.
EPSM Enhanced Power Supply Module. Used in +27 V
positive earth cabinets.
Equalization The process by which attenuation and/or phase
shift is rendered essentially constant over a band of
frequencies, even though the transmission medium
or the equipment has losses that vary with frequency.
Equalizer An electrical network in which attenuation (or gain)
and/or phase shift varies as a function of frequency.
Used to provide equalization.
Erlang International (dimensionless) unit of traffic intensity
defined as the ratio of time a facility is occupied to
the time it is available for occupancy. One erlang is
equal to 36 CCS. In the US this is also known as
a traffic unit (TU).
ERP Ear Reference Point. Facility for assessing handset
and headset acoustic responses.
ERP Effective Radiated Power. The power supplied to an
antenna multiplied by the antenna gain in a given
direction.
ERR ERRor.
ES Encoding Scheme.
ESD Electrostatic Discharge.
ESP Encapsulating Security Payload.
ESP Electro-static Point. Connection point on the
equipment for an anti-static wrist strap.
ESQL Embedded SQL (Structured Query Language). An
RDBMS programming interface language.
Ethernet A LAN standard network protocol that uses radio
frequency signals carried by coaxial cables.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETS Expanded Trunking System.
ETSI European Telecommunication Standard Institute.
ETX End of Transmission.
EXEC Executive Process.
Expansion cabinet A cabinet holding the GSN equipment, including the
GGSN chassis and SGSN chassis.
68P02905W21-B 11-33
02-Jun-2004
F Chapter 11: Glossary of abbreviations
F
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
F Interface Interface between MSC and EIR.

FA Fax Adaptor. Device which complements Group
3 facsimile apparatus in order to be able to
communicate over a GSM PLMN.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACH Forward Access Channel.
The FACH is a downlink transport channel that is
used to carry control information to a mobile station
when the system knows the location cell of the UE.
The FACH may also carry short user packets. The
FACH is transmitted over the entire cell or over only
a part of the cell using lobe-forming antennas.
FAUSCH Fast Uplink Signalling Channel.
FBI Feed Back Indicator.
FBM Flow control Buffer Management. A functional unit
that resides on the PRP and controls buffer capacity
for each cell and mobile. This allows the incoming
data from the SGSN to match the air throughput.
FCC Federal Communications Commission. US
government agency that controls electronic
transmission standards.
FCCH Frequency Correction CHannel. A GSM broadcast
control channel that carries information for MS
frequency correction.
FCAPS Fault, Configuration, Accounting, Performance and
Security.
FCS Frame Check Sum. The extra characters added to a
frame for error detection and correction.
FDD Frequency Division Duplex.
FDDI Fibre Distributed Data Interface. LAN technology
that permits data transfer on fibre-optic cable at up
to 100 Mbps.
FDM Frequency Division Multiplex. A multiplexing
technique that uses different frequencies to combine
multiple streams of data for transmission over a
communications medium. FDM assigns a discrete
carrier frequency to each data stream and then
combines many modulated carrier frequencies for
transmission.
11-34 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview F
FDMA Frequency Division Multiple Access. Each physical

channel occupies one carrier frequency and requires
a separate transmitter.
FEC Forward Error Correction.
FECN Forward Explicit Congestion Notification. The bit
that informs the DTE receiving the frame that there
was congestion in the path followed by the frame.
FEP Front End Processor. An OMC driver that stores data
about all the sites in the system in its own database.
FER Frame Erasure Rate.
FET Field Effect Transistor.
FFS For Further Study.
FH Frequency Hopping. The repeated switching of
frequencies during radio transmission, according to
a specified algorithm.
FHI Frequency Hopping Index.
Firewall A security system that enforces an access control
policy between a network and the Internet.
Flash A special type of EEPROM that provides
non-volatile storage and can be electrically erased
and reprogrammed.
Flow control Method for ensuring that a transmitting device does
not overwhelm a receiving device with data.
FM Fault Management.
FM Frequency Modulation.
FMIC Fault Management Initiated Clear.
FMK FrameWork.
FN Frame Number.
FP Frame Protocol.
FPGA Field Programmable Gate Array.
FPLMTS Future Public Land Mobile Telecommunications
System.
FQDN Fully Qualified Domain Name.
Period of RF carrier less than one timeslot whose
modulation bit stream allows frequency correction
to be performed easily within an MS burst.
FR Frame Relay. A packet-switching protocol for
connecting devices on a WAN at high speeds.
Frame Set of bits that form an elementary block of data to
be sent over a communications channel. A frame
usually contains its own control information.
68P02905W21-B 11-35
02-Jun-2004
F Chapter 11: Glossary of abbreviations
Frame Alignment The state in which the frame of the receiving

equipment is synchronized with respect to that of
the received signal to accomplish accurate data
extraction.
Frequency Correction Period of RF carrier less than one timeslot whose
modulation bit stream allows frequency correction
to be performed easily within an MS burst.
Frequency Hopping The repeated switching of frequencies during radio
transmission according to a specified algorithm.
Frequency hopping improves capacity and quality
in a highly loaded GSM network. Multipath fading
immunity can be increased by using different
frequencies and interference coming from neighbour
cells transmitting the same or adjacent frequencies
can be reduced.
FRF Frame Relay Forum.
FrPvc Frame relay Permanent virtual circuit.
FRU Field Replaceable Unit.
FS Full Scale.
FS Frequency Synchronization. All BSS frequencies
and timing signals are synchronized to a high
stability reference oscillator in the BSS. This
oscillator can free run or be synchronized to the
recovered clock signal from a selected E1/T1
serial link. MSs lock to a reference contained in a
synchronization burst transmitted from the BTS site.
FSL Free Space Loss. The decrease in the strength of a
radio signal as it travels between a transmitter and
receiver. The FSL is a function of the frequency of
the radio signal and the distance the radio signal has
travelled from the point source.
FSN Forward Sequence Number.
FTAM File Transfer Access and Management.
FTD File Transit Delay.
FTP File Transfer Protocol.
FU Functional Unit.
Full Rate Refers to the current capacity of a data channel on
the GSM air interface, that is, 8 simultaneous calls
per carrier. See also HR - Half Rate.
FW Firewall.
11-36 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview G
G
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
G Interface Interface between VLR and VLR.

Ga interface Interface between the CGFu and the SGSNu, and
the CGFu and the GGSNu.
Gateway Device that performs protocol-conversion to
interconnect networks that have different,
incompatible communications protocols.
Gateway MSC An MSC that provides an entry point into the GSM
PLMN from another network or service. A gateway
MSC is also an interrogating node for incoming
PLMN calls.
GB, Gbyte Gigabyte.
Gb Interface Interface between SGSN and Bxx.
Gb card Card that performs the SGSN communication
protocol functions for a single Gb interface. Also
called LTF module.
Gb link The cable that carries GPRS user data and signalling
information between the PCU and SGSN using
Frame Relay over E1.
GBIC Gigabit Interface Converter Converter for
connection to the Gigabit Ethernet.
GBM Gb Manager.
Gbps Gigabits per second (equivalent to 1000 Mbps).
G-CDR GGSN-Call Detail Record.
GC General Control (SAP).
GCI GDS Channel Identifier (16kbit/s resource used for
data).
GCLK Generic Clock board. System clock source, one per
site (part of BSS, BTS, BSC, IWF, RXCDR).
Gc Interface Interface between the CommHub and HLR.
GCMD Generator CoMmanD (CoMmanD Generator).
GCRA Generic Cell Rate Algorithm.
Gd Interface between SGSN and SMS-GMSC/SMS-
IWMSC.
GDL GPRS Data Link.
GDP Generic DSP Processor board. Interchangeable with
the XCDR board.
GDS GPRS Data Stream.
68P02905W21-B 11-37
02-Jun-2004
G Chapter 11: Glossary of abbreviations
GDS LAPD (GSL) The GSLs are provisioned over one or two E1s
between the BSC and PCU. Each GDS LAPD
channel uses 64 kbit/s of bandwidth on an E1. This
LAPD link carries out-of-band GPRS signalling
information, PCU statistics, and other PCU O&M
information such as software code loads.
GDS TRAU The GDS TRAU is provisioned by the network
operator over one to ten E1s between the BSC and
PCU. These E1s carry GPRS user data.
Ge Interface Interface between SGSN and P-SCP.
GEA GPRS Encryption Algorithm.
GEM GPRS Encryption Module.
Gg GSN CommHub firewall screening.
gg GGSN-CONTROL, GGSN-GiPROC,
GGSN-GNPROC integrated functions
GGSN Gateway GPRS Serving Node.
GGSN-CONTROL GGSN-CONTROL function.
GGSN-GiPROC GGSN Gi Processor.
GGSN-GNPROC GGSN Gn Processor.
GGSNu Gateway GPRS Support Node, specific to UMTS.
GHz Giga-Hertz (10).
Gi interface Interface between the GGSNu and the PS-Service
Domain.
Gi-e Gi external.
Gi-i Gi internal.
GID Group ID. A unique number used by the system to
identify a user’s primary group.
GLIC GPRS LI Correlation.
GMLC Gateway Mobile Location Center.
GMSK Gaussian Minimum Shift Keying.
GMR General Manual Revision.
GMM GPRS Mobility Management. A function that
performs procedures for packet data mobility
management by interacting with the Network
Elements.
GMSC Gateway Mobile-services Switching Centre.
GMT Greenwich Mean Time.
GMSC Gateway Mobile Switching Centre.
Gn interface Interface between the SGSNu and the GGSNu.
11-38 68P02905W21-B
02-Jun-2004
Gn card Card that performs the SGSN communication

protocol functions for a single Gn interface. Also
called UTF module.
GND GrouND.
GNO GPRS Network Operators
GOS Grade Of Service. A traffic statistic defined as the
percentage of calls that have a probability of Busy
or Queueing Delay.
G-PDU GTP-Packet Data Unit. A GTP packet that contains
a T-PDU encapsulated by a GTP header. G-PDUs
are transmitted between GSNs in a GTP tunnel.
GP Guard Period.
Gp Interface Interface between two GSNs in different PLMNs.
GPA GSM PLMN Area.
GPROC Generic Processor board.
GPRS General Packet Radio System.
GPRS-Attach GPRS-Attach is performed when the MS indicates
its presence to the PLMN for the purpose of using
the GPRS PTP service.
GPRS-Detach GPRS-Detach is performed when the MS indicates
to the PLMN that the MS is no longer using the
GPRS services.
GPS Global Positioning System. A system for
determining position on the surface of the Earth by
comparing radio signals from several satellites.
GR Gb Router.
Gr interface Interface between the SGSNu and the HLR.
Gr link The cable that carries information between the
SGSN and HLR.
GRE Generic Route Encapsulation.
GRNC Generic Radio Network Controller.
applications that are not specific to any particular
call (user connection) or any particular Node B.
Represents the RNC functions that are not covered
by any of the other three types (See, CRNC, DRNC
and SRNC). This also relates to global functions
such as transit or ATM functions.
GRR GPRS Radio Resource sublayer (RLC/MAC).
GRX GPRS Roaming Exchange.
Gs Interface Interface between an SGSN and an MSC/VLR.
68P02905W21-B 11-39
02-Jun-2004
G Chapter 11: Glossary of abbreviations
GSA GSM Service Area. The area in which an MS

can be reached by a fixed subscriber, without the
subscriber’s knowledge of the location of the MS. A
GSA may include the areas served by several GSM
PLMNs.
GSA GSM System Area. The group of GSM PLMN areas
accessible by GSM MSs.
GSL GPRS Signalling Link.
GSM Global System for Mobile communications.
GSM Groupe Spécial Mobile (the committee).
GSM900 See PGSM.
GSMRF GSM Radio Frequency.
GSN GPRS Support Node. The combined functions
provided by the SGSN and GGSN.
GSN Complex GSNs and an ISS Cluster connected to a single
CommHub.
GSNu GPRS Support Node, specific to UMTS. High
performance broadband packet-switching node.
GSR GSM System Release.
GT Global Title.
GTAI Global Title Address Information.
GTI Global Title Indication.
GTM Gb Transmit Manager or Gateway Transmit
Manager.
GTP GPRS Tunnelling Protocol. Protocol that handles
the flow of packet data and signalling information
between the SGSN and GGSN.
GTP’ GTP Prime.
GTP tunnel A tunnel, referenced by a TID and defined by 2
associated PDP contexts, used to communicate
between an external PDN and an MS. A GTP tunnel
is created each time an SGSN sends a Create PDP
Context Request.
GTT Global Title Translation.
Guard period Period at the beginning and end of timeslot during
which MS transmission is attenuated.
GUI Graphical User Interface. The graphics-based user
interface that an application provides that allows
users to pull down menus, point and click, or
otherwise choose commands or actions.
GUI client A computer used to display a GUI from an OMC
GUI application which is being run on a GUI server.
11-40 68P02905W21-B
02-Jun-2004
GUI server A computer used to serve the OMC GUI application

process running locally (on its processor) to other
computers (GUI clients or other MMI processors).
GW Gateway.
GWM GateWay Manager.
GWY GateWaY (MSC/LR) interface to PSTN.
68P02905W21-B 11-41
02-Jun-2004
H Chapter 11: Glossary of abbreviations
H
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
H Interface Interface between HLR and AUC.

HA High Availability.
HA NFS High Availability Network File System.
HA Disk Array High Availability Disk Array. A Sun Netra D1000
that provides reliable, long-term storage for network
configuration, software loads, charging data
information and network statistics.
HADA High Availability Disk Array. This term is now
superseded. See HA Disk Array.
Half Rate Refers to a type of data channel that will double
the current GSM air interface capacity to 16
simultaneous calls per carrier (see also FR - Full
Rate).
HANDO, Handover HANDOver. The action of switching a call in
progress from one radio channel to another radio
channel (can be the same or different cell).
Hard Handover A category of handover procedures where all the old
radio links in the UE are abandoned before the new
radio links are activated.
HCS Hierarchical Cell Structure.
HDLC High level Data Link Control. ITU-TSS link layer
protocol standard for point-to-point and multi-point
communications.
HDSL High bit-rate Digital Subscriber Line. A data
transmission mechanism that supports duplex high
speed digital communication (at E1 rates) on one or
more unshielded twisted pair lines.
HEC Header Error Control.
HGGSN Home GGSN.
HHLR Home HLR.
HHO Hard Handover.
HLC High Layer Compatibility. The HLC can carry
information defining the higher layer characteristics
of a teleservice active on the terminal.
HLR Home Location Register. The register where the
current location and all subscriber parameters of an
MS are permanently stored.
HLRS Home Location Register Service.
Hot-swappable Able to replace a card in a hardware device without
turning it off or losing functionality.
11-42 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview H
HPLMN Home PLMN. The home network a mobile

subscriber belongs to.
HO HandOver. See HANDO.
Home PLMN The PLMN where the Mobile Country Code (MCC)
and Mobile Network Code (MNC) of the PLMN
identity are the same as the MCC and MNC of the
IMSI.
Hot Spot Capacity Number of users who may be instantaneously
supported per isolated cell (or satellite spot beam)
per unit spectrum. This must be specified at a stated
spectrum allocation, quality and grade of service.
HR See Half Rate.
HSC Hot Swap Controller.
HSCSD High Speed Circuit Switched Data
HSGSN Home SGSN.
HSM HLR Subscriber Management.
HSRP HA Standby Router Protocol.
HSSI High-Speed Serial Interface. A de facto standard for
high-speed serial communications over WAN links.
HW Hardware.
Hyperframe 2048 superframes. The longest recurrent time period
of the frame structure.
HTML Hypertext Markup Language.
68P02905W21-B 11-43
02-Jun-2004
I Chapter 11: Glossary of abbreviations
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
IA Incoming Access. A supplementary service that

allows a member of a CUG to receive calls from
outside the CUG.
IA Intercept Area (jurisdiction).
IAM Initial Address Message. A message sent in the
forward direction that contains information about
addresses, signalling, service-class, user and
network facilities, and call-originator or call-receiver
identity.
IANA Internet Assigned Numbers Authority.
IAP Intercept Access Point.
IC Integrated Circuit. An electronic circuit that
consists of many individual circuit elements, such as
transistors, diodes, resistors, capacitors, inductors,
and other active and passive semiconductor devices,
formed on a single chip of semiconducting material
and mounted on a single piece of substrate material.
ICANN Internet Corporation for Assigned Names and
Numbers.
ICB Incoming Calls Barred. An access restriction that
prevents a CUG member from receiving calls from
other members of that group.
ICMP Internet Control Message Protocol. In TCP/IP, the
collection of messages exchanged by IP modules in
both hosts and gateways to report errors, problems
and operating information.
ICD Interface Control Document.
ID Identifier.
IDE Integrated Drive Electronics.
Idle mode State of a User Equipment switched on but not
actively processing a call.
IDP Intercept Data Product. All user data sent or received
by a Lawful Intercept target.
IDP Implementation-dependent protocol.
IDPS MS IDP—Surveilled MS.
IDN Integrated Digital Network. A network that uses
both digital transmission and digital switching.
IE Information Element.
IEC International Electrotechnical Commission.
11-44 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview I
IEC297 International Electrotechnical Commission 297.

IEE Institution of Electrical Engineers.
IEEE Institute of Electrical and Electronic Engineers.
Committees that develop and propose computer
standards that define the physical and data link
protocols of communication networks.
I-ETS Interim European Telecommunication Standard.
IETF Internet Engineering Task Force.
iGMLC interim Gateway Mobile Location Centre
IHOS Internet Hosted Octet Stream.
IKE Internet Key Exchange protocol.
IMA Inverse Multiplexing for ATM.
IMEI International Mobile Equipment Identity. Electronic
serial number that uniquely identifies the MS as a
piece or assembly of equipment. The IMEI is sent
by the MS along with request for service.
IMEISV IMEI Software Version.
IMS Interception Management System. The software
function that manages a LIAN.
IMSI International Mobile Subscriber Identity. A unique
identifier stored in the SIM of an MS.
IMT-2000 International Mobile Telecommunication 2000.
IN Intelligent Network.
INAP Intelligent Network Application Protocol.
INI Inter Network Interface.
INS IN Service.
INSS Intelligent Network Support System.
Inter-cell handover Handover between different cells. An inter-cell
handover requires network connections to be altered.
Interface The common boundary between two associated
systems.
Intermittent Intermittent alarms are transient and not usually
associated with a serious fault condition. After
the intermittent alarms are displayed in the Alarm
window, the operator must handle and clear the
alarm. The system will report every occurrence of
an intermittent alarm unless it is throttled.
Internet A world-wide TCP/IP network made up of several
large backbone networks connecting to countless
regional and local networks.
Internet address The 32-bit address assigned to hosts using TCP/IP.
68P02905W21-B 11-45
02-Jun-2004
Interworking The general term used to describe the inter-operation

of networks, services, and supplementary services.
Interval A recording period of time in which a statistic is
pegged.
Intra-cell handover Handover within one sector or between different
sectors of the same cell. An intra-cell handover does
not require network connections to be altered.
IOS Internetworking Operating System.
IOT Inter-operability Testing.
I/O Input/Output.
IP Initialization Process. Process responsible for
bringing up the site from a reset.
IP Internet Protocol. Standard protocol designed for
use in interconnected systems of packet-switched
computer communications networks. IP deals only
with packets.
IPC Inter-Process Communication. Exchange of data
between one process and another, either within the
same computer or over a network.
IP-M Internet Protocol Multicase.
IPSec IP Security. A framework of open standards
that provides data confidentiality, integrity, and
authentication between participating peers.
IRDY Indicator Ready.
IREG International Roaming Experts Group.
IRI Intercept Related Information. Collection of
GPRS signalling information associated with
telecommunications services involving an LI target.
For example, GPRS Attach Request, Modify PDP
Context Request, or Cell Update Request.
Iridium A communications system comprising a
constellation of 66 low-earth-orbiting (LEO)
satellites forming a mobile wireless system allowing
subscribers to place and receive calls from any
location in the world. The satellite constellation is
connected to existing terrestrial telephone systems
through a number of gateway ground-stations.
IRIS MS IRI-Surveilled MS.
ISA Industry Standard Architecture. A 16-bit bus design
used for Intel-based personal computers.
ISC International Switching Centre. The ISC routes calls
to/from other countries.
ISCP Interference Signal Code Power.
11-46 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview I
ISDN Integrated Services Digital Network. A standard for

providing digital connections between user-network
interfaces over public telephone networks.
Island coverage A characteristic of a geographical zone in which
UMTS service is provided in a number of separate
isolated areas (reffered to as islands).
ISM Integrated Systems Management.
iSLMC interim Service Mobile Location Centre.
ISO International Organisation for Standardization. A
world-wide federation of national standards bodies.
ISP Internet Service Provider. Commercial organization
that provides Internet access to individuals and
organizations.
ISS Integrated Support Service.
ISS Cluster The ISS Cluster comprises the ISS plus the HA Disk
Array and Terminal Concentrator.
ISO International Organization for Standards.
ISUP ISDN User Part. An upper-layer application
supported by SS7 for connection setup and
teardown.
ITC Information Transfer Capability. A GSM Bearer
Capability Element that supports terminal adaptation
function to Interworking control procedures.
ITU International Telecommunication Union. An
organization established by the United Nations to
set international telecommunications standards and
allocate frequencies for specific uses.
ITU-T ITU - Telecommunications standardization sector.
The standardization functions of this body were
previously performed by CCITT, a group within the
ITU.
Iu Reference point between Access and Serving
Network domains. Interconnection point between an
RNS and a Core Network.
Iub Interface between Node B and RNC network
elements.
The information exchange is for the purpose
of passing signalling and data information, and
supporting logical O&M procedures.
Iu-BC Interface between the SRNC and the CBC for the
Broadcast Domain of the Core Network.
Iu-CS Interface between the SRNC and the MSCu for
the Circuit Switched-Service Domain of the Core
Network.
68P02905W21-B 11-47
02-Jun-2004
Iu-PS Interface between the SRNC and the SGSNu for

the Packet Switched-Service Domain of the Core
Network.
Iur The logical interface between two RNC network
elements.
These RNCs can be SRNC and DRNC, or SRNC
and CRNC, or two GRNCs that have no specific
function.
IWF InterWorking Function. A network functional entity
which provides network interworking, service
interworking, supplementary service interworking
or signalling interworking. It may be a part of one or
more logical or physical entities in a GSM PLMN.
IWMSC InterWorking MSC. An MSSC used to deliver data
to or from an SGSN.
IWU InterWorking Unit. Unit where the digital-to-analog
and analog-to-digital conversion takes place within
a GSM network.
11-48 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview J
J
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
JD Joint Detection.
JP Joint Predistortion.
68P02905W21-B 11-49
02-Jun-2004
K Chapter 11: Glossary of abbreviations
K
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
k kilo (103).
kbit kilobit. 1 kbit is1,024 bits for technical purposes;
1,000 bits for general purposes.
kbit/s kilobits per second. A transmission rate expressed
in thousands of bits per second.
kbps kilobits per second.
kbyte kilobyte. A transmission rate expressed in thousands
of bytes per second.
Kc Ciphering key. A sequence of symbols that controls
enciphering and deciphering.
kg kilogram.
kHz kilo-Hertz (10-3).
Ki Individual subscriber authentication Key. Part of the
authentication process of the AUC.
kph Kilometres per hour.
ksps kilo-symbols per second.
kW kilo-Watt.
11-50 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview L
L
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
L1 Layer 1 (of a communications protocol).

L2 Layer 2. The second layer of the OSI model. See
Data Link layer.
L3 Layer 3. Third layer of the OSI model. See Network
layer.
L3MM Layer 3 Mobility Management.
L4 Layer 4. The fourth layer of the OSI model. See
Transport layer.
L5 Layer 5. The fifth layer of the OSI model. See
Session layer.
L6 Layer 6. The sixth layer of the OSI model. See
Presentation layer.
L7 Layer 7. The seventh layer of the OSI model. See
Application layer.
LA Location Area.
LAC Location Area Code. Part of the LAI. The
operator-defined code that identifies the location
area.
LAC Link Access Control.
LAI Location Area Identity. The information indicating
the location area in which a cell is located. The LAI
data on the SIM is continuously updated to reflect
the current location of the MS.
LAN Local Area Network.
LAPB Link Access Protocol Balanced. The balanced-mode,
enhanced version of HDLC.
LAPD Link Access Protocol D-channel (Data). A protocol
that operates at layer 2 of the OSI architecture.
Used to convey information between layer 3 entities
across the FR network. The D-channel carries
signalling information for circuit switching.
LAP-G Link Access Protocol-GPRS.
LAU Location Area Update.
Layer A level of the OSI reference model. Each layer
performs certain tasks to move the information.
Protocols within the layers define the tasks for
networks, but not how the software accomplishes
the tasks.
68P02905W21-B 11-51
02-Jun-2004
L Chapter 11: Glossary of abbreviations
LCD Liquid Crystal Display. An alphanumeric display

on computers and other devices using liquid crystal
sealed between two pieces of glass.
LCD Low Constrained Delay.
LEA Law Enforcement Agency. A body authorized by
law to intercept transmissions on a GPRS PLMN.
LEA clients Computer nodes located at LEA sites and containing
secure tunnelling software for providing a secure
communication link for IRI and IDP data transfer
from the LIAN.
Leased line A transmission line reserved by a communications
carrier for the private use of a customer.
LED Light-Emitting Diode. A semiconductor device
that emits light when connected in a circuit. LEDs
are frequently used to indicate hardware equipment
status.
LF Line Feed. A code that moves the cursor on a display
screen down one line. In the ASCII character set, a
line feed has a decimal value of 10. On printers, a
line feed advances the paper one line.
LI Lawful Intercept. A function that provides the
ability to track and monitor signalling information
and user data for a particular MS.
LIAN Lawful Intercept Administration Node. The node
from which LI is managed. The LIAN consists
of the administrative function (ADMF) and two
delivery functions (IRI and IDP).
Link A physical or logical connection between two points.
LIRF Lawful Intercept Relay Function.
LL Lower layers.
LLC Logical Link Control. The upper part of layer 2
(data link layer) in the OSI reference model.
LLGMM Logical Link GPRS Mobility Management.
LLMF Low Level Maintenance Functions.
LLSMS Logical Link Short Message Service.
LM Load Management.
LMI Local Management Interface. A Frame Relay
specification that defines a method of exchanging
status information between devices such as routers.
LMT Local Maintenance Terminal.
Load balancing A method of spreading server traffic over multiple
links to relieve congestion.
11-52 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview L
Location area An area in which a mobile station may move freely

without updating the location register. A location
area may comprise one or several base station areas.
Location Registration The UE registers its presence in a registration
area, for instance regularly or when entering a new
registration area.
Logical Channel An information stream dedicated to the transfer of a
specific type of information over the radio interface.
LORP List of Required Parts.
LPA Linear Power Amplifier.
LPF Low Pass Filter.
LR Location Register. The functional unit where MS
location information is stored. The HLR and VLR
are location registers.
LRSN Local Record Sequence Number.
LSA Localized Service Area.
LSSU Link Stations Signalling Unit (Part of MTP transport
system).
LTF Lower Transmission Function. Gb interface
communication protocol functions.
LU Location Update. An event initiated by the MS when
it detects that it has entered a new location area.
LVDS Low Voltage Digital Signal.
68P02905W21-B 11-53
02-Jun-2004
M Chapter 11: Glossary of abbreviations
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
M Mandatory.
M Mega - 106.
M-Cell Motorola Cell.
MA Multiple Access.
MAC Media/Medium Access Control. MAC includes the
functions related to the management of the common
transmission resources, including packet data
physical channels and their radio link connections.
MACN Mobile Allocation Channel Number.
Macro cell Outdoor cells with a large cell radius, typically a few
tens of km. However, the range can be extended by
the use of directional antennas or repeaters.
Macro diversity An operation state in which a User Equipment
simultaneously has radio links with two or more
UTRAN access points for the sole aim of improving
quality of the radio connection or providing seamless
handover.
MAP Mobile Application Part (of SS7). The
inter-networking signalling between MSCs and LRs
and EIRs.
MAPP Mobile Application Part Processor.
Maximum Path Loss (dB) The maximum loss that permits minimum SRTT
performance at the cell boundary.
Maximum Range (km) Rmax, is given by the range associated with the
maximum path loss.
Maximum Total Transmitter Power (dBm The aggregate maximum transmit power of all
channels.
Maximum Transmitter Power Per Traffic Channel The maximum power at the transmitter output for
(dBm) a single traffic channel.
Mb, Mbit Megabit. One million binary bits.
MB, Mbyte Megabyte. One million binary bytes.
Mbps, Mbit/s Megabits per second. A bit rate expressed in
millions of binary bits per second.
MCC Mobile Country Code. The first three digits of the
IMSI, used to identify the country.
MCCF M-CDR Collection Function.
MCDF Motorola Customer Data Format used by DataGen
for simple data entry and retrieval.
M-CDR Mobility management-Call Detail Record.
11-54 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview M
MCG Motorola Computer Group.

MCP Main Control Processor.
Mcps Mega-chips per second.
MCTF M-CDR Transfer Function.
MD Mediation Device. A device that allows the OSI
processor to communicate between the NMC and
the OMCs (OMC-G and OMC-R) for network
configuration, events and alarms.
MDS Multimedia Distribution Service.
ME Mobile Equipment. Equipment intended to
access a set of GSM PLMN and/or DCS
telecommunications services, but which does not
contain subscriber-related information.
Mega cells/satellite cells Outdoor cells served by a satellite. The individual
sectors of a satellite cell may have radii of 500 to 1
500 km.
MEHO Mobile Evaluated Handover.
MER Message Error Rate.
Metadevice A group of physical slices that the system sees as a
single, logical device. Metadevices increase storage
capacity and data availability.
MF MultiFrame. In PCM systems, a set of consecutive
frames in which the position of each frame can be
identified by reference to a multiframe alignment
signal.
MHz Mega-Hertz (106).
MGMT, mgmt Management.
MGR Manager.
MIB Management Information Base.
Micro cell A cell in which the base station antenna is
generally mounted below rooftop level. Radio wave
propagation is by diffraction and scattering around
buildings, the main propagation is within street
canyons.
min minute(s).
µs micro-second (10-6).
MIT Management Information Tree. A file on the
Motorola OMC. The MIT file effectively monitors
data on every device and every parameter of each
device that is in the current versions of software on
the OMC. The data is stored as a text file on the
OMC. The MIT file also contains the hierarchical
relationships between the network devices.
68P02905W21-B 11-55
02-Jun-2004
MLS MultiLayer Switching. Scales Layer 3 performance

to high performance link speeds by extending the
MLS concept, introduced in Cisco IOS software, to
LAN switching hardware.
MM Mobility Management. Functions that track the
current location of an MS including authorization,
location updating, IMSI attach/detach, periodic
registration, ID confidentiality, paging and handover.
MMI Man Machine Interface.
MML Man Machine Language.
MMS Multiple Serial Interface Link (one of two T1 links)
on the MSI board.
MNC Mobile Network Code. The fourth, fifth and
optionally sixth digits of the IMSI, used to identify
the network.
MNRG Mobile station Not Reachable for GPRS (flag).
MNRR Mobile station Not Reachable Reason.
MO Mobile Originated.
Mobile evaluated handover Mobile evaluated handover (MEHO) is a type of
handover triggered by an evaluation made in the
mobile. The mobile evaluates the necessity of
handover based on the measured radio environment
and based on criteria defined by the network.
When the evaluation meets the hand-off criteria
the necessary information is sent from the mobile
to the network. The network then decides on the
necessity of the handover based on the reported
evaluation result and other conditions, eg. uplink
radio environment and/or availability of network
resources, the network may then execute the
handover.
MOHO Mobile Originated Handover.
MOS Metal Oxide Semiconductor.
Mobis Motorola Abis Interface.
Module A self-contained, separable assembly of electronic
parts and software such as the three-card set that
makes up the SGSN.
MoU Memorandum of Understanding. A document that
sets out the broad parameters of an understanding as
well as the general responsibilities and obligations
of each party in the proposed venture.
MPROC Master Processor.
MTBF Mean Time Between Failures.
MTTR Mean Time To Repair.
11-56 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview M
MS Mobile Station. The GSM/GPRS subscriber unit

used to access network services. GPRS supports
three classes of MS - Class A, Class B and Class C.
MSC Mobile Switching Centre.
MSCu Mobile Switching Centre, specific to UMTS.
msec millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface
to two 2 Mbit/s digital links.
MSID Mobile Station Identifier.
MSIN Mobile Station Identification Number. The part
of the IMSI identifying the MS within its home
network.
MSISDN Mobile Station International ISDN number.
Published mobile number that uniquely defines the
MS as an ISDN terminal. It consists of 3 parts: The
Country Code, the National Destination Code, and
the Subscriber Number.
MSRN Mobile Station Roaming Number. A number
assigned by the MSC to service and track a visiting
subscriber.
MSU Message Signal Unit. Part of the MTP transport
system. A signal unit containing a service
information octet and a signalling information field
which is retransmitted by the signalling link control,
if it is received in error.
MT Mobile Terminal. A subscriber unit in a mobile
system. See the entry for MS - the MT specific to
GPRS.
MT Mobile Terminated. Describes a call or short
message destined for an MS.
MTBF Mean Time Between Failures. An indicator of
expected system reliability calculated on a statistical
basis from the known failure rates of various system
components. MTBF is usually expressed in hours.
MTL Message Transfer Link. The 64 kbit/s PCM timeslot
used to convey the SS7 signalling information on
the A interface.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part. The part of the SS7 protocol
that transfers signalling messages and performs
associated functions such as error control and
signalling link security. MTP consists of three layers
- MTP1, MTP2 and MTP3.
MTP1 Message Transfer Part One. SS7 physical layer
that defines the physical, electrical, and functional
characteristics of the digital signalling link.
68P02905W21-B 11-57
02-Jun-2004
MTP2 Message Transfer Part Two. SS7 data link layer that
exercises flow control, message sequence validation,
error checking, and retransmission.
MTP3 Message Transfer Part Three. SS7 network level
that provides messages between signalling points in
the network, helping control traffic when congestion
or failures occur.
MT/PP Mobile Terminated Point-to-Point messages.
Transmission of a short message from a message
handling system to an MS.
MUI Mobile User Identifier.
Multicast A method of broadcasting where copies of a
packet are delivered only to a subset of all possible
destinations.
Multiframe Two types of multiframe are defined in the system:
a 26-frame multiframe with a period of 120 ms and
a 51-frame multiframe with a period of 3060/13 ms.
MUX Multiplexer. A device that combines multiple inputs
into an aggregate signal to be transported via a
single transmission channel.
MWD Messages Waiting Data.
MWI Messages—Waiting—Indication.
11-58 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview N
N
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
N/W Network.
NACK, Nack No Acknowledgement.
NAI Nature of Address Identification.
NAK Negative Acknowledgment.
NAS Network Access Server/Stratum.
NAT Network Address Translation.
NB Normal Burst. A period of modulated carrier less
than a timeslot.
NBAP Node B Application Part.
Is used for setting up RAB in the RNL over the Iub.
NC0 Network Cell reselection mode 0.
NC1 Network Control Option 1.
NC2 Network Control Option 2.
NCH Notification CHannel. Part of the downlink element
of the CCCH reserved for voice group and/or voice
broadcast calls and notification messages.
NCO Network Control Option.
NCP Node B Control Port.
NDC National Destination Code. Part of the MSISDN.
NE Network Element.
NEBS Network Equipment Building System.
NEHO Network Evaluated Handover.
NET Norme Européennes de Telecommunications.
NetPlan An RF planning tool, NetPlan can import data from
the OMC and use it to carry out a network frequency
replan.
68P02905W21-B 11-59
02-Jun-2004
N Chapter 11: Glossary of abbreviations
Network evaluated handover Network evaluated handover (NEHO) is a type

of handover triggered by an evaluation made in
the network. There are three cases. The first
case is that the mobile measures and reports the
measurement to the network upon request from the
network either periodically or on demand, and the
network then evaluates the necessity of handover.
The second case is that the network measures and
evaluates the necessity of handover. In the third case
measurements are made in both the mobile and in
the network. In all cases, the network decides the
necessity of handover based on the measurements
and other conditions; for example. availability of
network resources. The network always executes
any handover.
Network layer A protocol layer that responds to service requests
from the Transport Layer and issues service request
to the Data Link Layer. This layer provides network
routing, flow control, segmentation/desegmentation,
and error control functions.
NFFC NetFlow Feature Card.
NFS Network File System. A file system distributed over
a computer network. Also, a file system, on a single
computer, that contains the low-level networking
files for an entire network.
NFS server The NFS server provides reliable long-term storage
for network configuration, software storage,
charging data information, and network statistics.
NHA Network Health Analyst. The NHA is an optional
feature. It detects problems by monitoring network
statistics and events via the OMC-R. The NHA
analyses the event history, statistics and network
configuration data to try to determine the cause of
the detected problems.
NI Network Indicator.
NIB Network Interface Board.
NIC Network Interface Card. A circuit board that enables
a computer to be attached to a network.
NIS Network Information Service. A function that allows
centralised control of network information. For
example hostnames, IP addresses and passwords.
NGAF Non-GPRS Alert Flag.
NM Network Management. All activities that control,
monitor, and record the use and performance of
resources in a telecommunications network.
Nm Newton metres.
NMASE Network Management Application Service Element.
11-60 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview N
NMC Network Management Centre. The highest-level

management node in a network, linked to
subordinate OMC nodes.
NMI Non-Maskable Interrupt.
NMSI National Mobile Station Identification number. The
MNC and MSIN combined.
NNI Network-Network Interface.
Node B Logical node in the RNS, responsible for radio
transmission/reception in one or more cells to/from
the UE. Terminates the Iub interface towards the
RNC.
Node A point of connectivity.
Node B ID identifies the Node B within UTRAN
(used for measurement reporting for instance).
Normal burst A period of modulated carrier less than a timeslot.
NP Numbering Plan.
NPC Network Parameter Control.
N-PDU Network layer PDU.
NRT Non Real Time.
NS Network Service.
NS-VC Network Service-Virtual Circuit
NS-VCI NS-VC Identifier.
NS-VL Network Service-Virtual Link.
NS-VLI NS-VL Identifier.
NSAP Network Service Access Point. A registration
specifying the desired listening criteria of an
application. The registration is limited to a particular
CPU and port number. Criteria can include DNICs,
national numbers, subaddress ranges, protocol IDs
and extended addresses.
NSAPI NSAP Identifier.
NSEI Network Service Entity Identifier. Identifier of an
NS entity.
NSS Network SubSystem.
NSVC Network Service Virtual Circuit. A logical circuit
that connects the NSE peers between the SGSN and
the PCU. The NSVC has significance across the
network and is therefore configured identically at
both the SGSN and PCU.
NSVCI NSVC Identifier. Uniquely identifies one NSVC.
There is a one-to-one mapping between the NSVCI
and DLCI.
Nt Notification (SAP).
68P02905W21-B 11-61
02-Jun-2004
N Chapter 11: Glossary of abbreviations
NTF Name and Time Function.

NTP Network Time Protocol. A protocol that
synchronizes the time of GSN components with
reference to radio, atomic or other clocks located
on the Internet.
NVRAM Non-Volatile Random Access Memory. Static
random access memory converted into non-volatile
storage either by using a permanently-connected
battery or by saving its contents to EEPROM before
powering off and reloading when power is restored.
NVRAMRC NVRAM Run Control.
nW Nano-Watt (10-9).
11-62 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview O
O
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
O&M Operations and Maintenance.

O Optional.
OAMP Operation, Administration, Maintenance and
Provisioning.
OA&M Operation, Administration & Monitoring.
OCB Outgoing Calls Barred within the CUG
supplementary service. An access restriction that
prevents a CUG member from placing calls to other
members of that group.
OCCCH ODMA Common Control Channel.
ODCCH ODMA Dedicated Control Channel.
ODCH ODMA Dedicated Channel.
ODMA Opportunity Driven Multiple Access.
ODTCH ODMA Dedicated Traffice Channel.
OIC Operator Initiated Clear.
OID Object Identifier.
OIR Online Insertion and Removal.
OLM Off_Line MIB. A Motorola DataGen database, used
to modify and carry out Radio Frequency planning
on multiple BSS binary files.
OMAP Operations and Maintenance Application Part of
SS7 (previously OAMP).
OMC Operations and Maintenance Centre. The OMC
provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area
controlled by the specific OMC.
OMC-G Operations and Maintenance Centre - GPRS. The
OMC-G provides an interface for managing the
GSN functions of a GPRS network.
OMC-R Operations and Maintenance Centre - Radio. For
GPRS, the OMC-R provides an interface for
managing the PCU. It also manages all GSM
functions.
OMC-S/T Operations and Maintenance Centre-Transportation
network.
OMC-U Operations and Maintenance Centre-UMTS.
OML Interface between each RNC and the controlling
OMC-U. Also the interface between the SGSNu and
the controlling OMC-Gu.
68P02905W21-B 11-63
02-Jun-2004
O Chapter 11: Glossary of abbreviations
OPC Originating Point Code. A part of the label in a

signalling message that uniquely identifies, in a
signalling network, the (signalling) origination point
of the message.
OOS Out Of Service.
OpenMaster Bull product for integrated systems management.
ORACH ODMA Random Access Channel.
OS Operating System.
OSI Open Systems Interconnection. A seven-layer
reference model for defining communication
between points in a telecommunications network.
OSPF Open Shortest Path First. Interior Gateway protocol
for TCP/IP. Uses an algorithm that calculates routes
for packets based on a number of factors including
least number of hops, speed of transmission lines,
and congestion delays.
OVSF Orthogonal Variable Spreading Factor.
11-64 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview P
P
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PA Power Amplifier.
PABX Private Automatic Branch eXchange. A private
automatic telephone exchange that allows calls
within the exchange and also calls to and from the
public telephone network.
PACCH Packet Associated Control CHannel.
PACE Payload Active CP2 Emulator.
Packet A sequence of bits, including data and control
signals, transmitted as a single logical block over a
packet-switched network.
Packet-switched network A network in which data is transmitted in packets.
The packets are sent individually over the best
available network connection and then reassembled
at the destination to form a complete message.
Packet switching The process of routeing and transferring data using
addressed packets so a channel is occupied only
during transmission and is then available to other
traffic.
PAD Packet Assembler/Disassembler. A hardware device
that allows a data terminal not set up for packet
switching to use a packet switching network. The
PAD assembles data into packets for transmission
and disassembles the packets on arrival.
PAGCH Packet Access Grant CHannel.
Paging The procedure by which a PLMN fixed infrastructure
attempts to reach an MS/UE within its location area,
before any other network-initiated procedure can
take place.
Paging area The geographical region in which a User
Equipment will be paged as a part of incoming call
establishment. A paging area may comprise one or
more cells or sectors.
Parser A computer program that determines the syntactic
structure of a sentence or string of symbols in a
computer language.
PAT Port Address Translation.
PATH CEPT 2 Mbit/s route through the BSS network.
PBB PCU processor Bridge Board. Allows an MPROC
to be linked to a separate bus.
PBCCH Packet Broadcast Control CHannel.
68P02905W21-B 11-65
02-Jun-2004
P Chapter 11: Glossary of abbreviations
PBX Private Branch eXchange. In the general use of the

term, PBX is a synonym for PABX. However, a
PBX operates with only a manual switchboard; a
private automatic exchange (PAX) does not have a
switchboard, a private automatic branch exchange
(PABX) may or may not have a switchboard.
PC Personal Computer. A general-purpose
microcomputer designed to be operated by one
person at a time.
PC Power Control.
PC Point Code.
PCA PCU Control Authority. A PCU software process
that maintains a list containing the status of each
device and software process at the site.
PCA Parallel Channel Adapter.
PCB Printed Circuit Board.
PCCC Parallel Concatenated Convolutional Code.
PCCCH Packet Common Control CHannel.
PCCH Paging Control Channel (Logical Channel).
PCCPCH Primary Common Control Physical Channel.
The PCCPCH is a downlink physical channel that
carries the BCH.
PCH Paging Channel (Transport Channel).
The PCH is a downlink transport channel that is used
to carry control information to a mobile station when
the system does not know the location cell of the UE.
The PCH is always transmitted over the entire cell.
PCHN Physical Channel. The medium over which
information is carried such as the air interface or
Ethernet.
PCI Peripheral Component Interconnect. A
high-performance internal interconnect bus used for
data transfer to peripheral controller components.
PCI Packet Control Interface.
pCM PCU Configuration Management. A process that
distributes database changes performed at the BSC
to the PCU boards.
PCM Pulse Code Modulation. Technique for converting
an analog signal with an infinite number of possible
values into discrete binary digital words that have a
finite number of values.
11-66 68P02905W21-B
02-Jun-2004
PCMCIA Personal Computer Memory Card International

Association. The organization that developed the
standard for a card that can be plugged into a
specially-designed bus and be operational without
further system modification.
PCN Personal Communications Network. Any network
supporting PCS, but in particular DCS1800.
PCPCH Physical Common Packet Channel.
PCR Preventative Cyclic Retransmission. A form of
error correction suitable for use on links with long
transmission delays, such as satellite links.
PCS1900 A cellular phone network using the higher frequency
range allocated in countries such as the USA. It
operates on the frequency range, 1850 - 1910 MHz
(receive) and 1930 - 1990 MHz (transmit).
PCS Physical Channel Segmentation.
PCS Personal Communications Service/System. The
FCC term used to describe a set of digital cellular
technologies being deployed in the US. PCS works
over GSM, CDMA and North American TDMA
air interfaces.
PCU Packet Control Unit. A BSS component that
provides GPRS with packet scheduling over the air
interface with the MS, and packet segmentization
and packetization across the Frame Relay link with
the SGSN.
PCU chassis Empty equipment chassis in which the PCU
hardware modules will be housed.
PCU unit PCU chassis complete with PCU modules.
PD Protocol Discriminator. The first octet of the packet
header that identifies the protocol used to transport
the frame.
PDA Personal Digital Assistant.
PDCH Packet Data Channel. PDCH carries a combination
of PBCCH and PDTCH logical channels.
PDH Plesiochronous Digital Hierarchy.
PDN Public Data Network. Packet-switched network that
provides customers with wide area network services,
usually for a fee.
PDP Packet Data Protocol. Network protocol used
by external PDNs to communicate with a GPRS
network.
PDP context A set of information used by MSs and GSNs to
identify the wireless session.
PDSCH Physical Downlink Shared Channel.
68P02905W21-B 11-67
02-Jun-2004
PDTCH Packet Data Traffic CHannel.

PDU Protocol Data Unit. OSI terminology for packet.
A PDU is a data object exchanged by protocol
machines within a given layer of the OSI protocol
model. It contains both protocol control information
and user data.
Peg A single incremental action modifying the value of a
statistic.
Pegging Modifying a statistical value.
Perf Performance.
pFCP PCU Fault Collection Process.
pFTP PCU Fault Transaction/Translation Process. Process
to which all PCU alarms are reported.
PG Processing Gain.
PGSM Primary GSM. PGSM operates on the standard
GSM frequency range, 890 - 915 MHz (receive) and
935 - 960 MHz (transmit).
PH Packet Handler. Process that assembles and
disassembles packets.
PhCH Physical Channel.
PHI Packet Handler Interface.
PHS Personal Handyphone System.
PHY Physical layer.
PhyCH Physical Channel.
Physical Channel In FDD mode, a physical channel is defined by code,
frequency and, in the uplink, relative phase (I/Q). In
TDD mode, a physical channel is defined by code,
frequency, and time-slot.
Physical channel data stream In the uplink, a data stream that is transmitted on
one physical channel. In the downlink, a data stream
that is transmitted on one physical channel in each
cell of the active set.
Physical layer The OSI protocol layer that performs services
requested by the Data Link Layer including
establishing and terminating connections.
PI Page Indicator.
PICH Page Indicator Channel. (Physical Channel)
PICMG PCI Industrial Computers Manufacturing Group.
Pico cell A cell site where the base station antenna is mounted
within a building, with a radius typically less than
50 metres.
11-68 68P02905W21-B
02-Jun-2004
PICP Packet Interface Control Processor. A PCU

hardware component used for interfacing with the
SGSN and BSC.
PID Packet Identification.
PIM PMC Interface Module.
PIN Personal Identification Number. A password,
typically four digits entered through a telephone
keypad.
Ping Packet Internet Groper. A utility that sends a packet
to a specific IP address to see if the component
is alive. Primarily used to troubleshoot Internet
connections.
PLL Phase Lock Loop. A mechanism whereby timing
information is transferred within a data stream and
the receiver derives the signal element timing by
locking its local clock source to the received timing
information.
PLMN Public Land Mobile Network. The mobile
communications network that uses earth-based
stations (as opposed to satellites).
PM Performance Management. An OMC application.
PM enables the user to produce reports specific to
the performance of the network.
PMC PCI Mezzanine Card.
PMD Physical Media Dependent.
PM/E1 Plugin Memory/E1.
PM/T1 Plugin Memory/T1.
PN Pseudo Noise.
PNCH Packet Notification CHannel.
POI Point of Interconnection (with PSTN).
Polling Method of controlling the transmission sequence by
requiring each device on a multipoint line to wait
until the polling processor requests it to transmit.
POP3 Post Office Protocol version 3.
POTS Plain Old Telephone Service. The existing
conventional analog telephone service.
PP Point-to-Point.
PPB PCI (Peripheral Component Interconnect) to PCI
Bridge. A board that allows an MPROC to be linked
to a separate bus.
ppb Parts per billion.
PPC Power PC.
PPCH Packet Paging CHannel.
68P02905W21-B 11-69
02-Jun-2004
PPF Paging Proceed Flag.

ppm Parts per million (x 10-6).
pps Packets per second.
PPP Point-to-Point Protocol. Protocol that provides
router-to-router and host-to-network connections
over both synchronous and asynchronous circuits.
PR Problem Report.
PRACH Physical Random Access Channel. (Physical
Channel)
The PRACH is an uplink physical channel that is
used to carry the RACH.
Prepaid Service A service that allows network operators to charge
subscribers in advance for service. The network
equipment debits the customer account as service
is used, and the network may deny service when
account funds are exhausted.
Presentation layer The protocol layer that responds to service requests
from the Application Layer and issues service
requests to the Session Layer. It relieves the
Application Layer of concern regarding syntactical
differences in data representation within end-user
systems.
PRI Primary Rate Interface. In North America, PRI is
split into 23B channels and one 64Kbps D channel
and delivered over the same physical link as a T1.
In Europe, PRI is split into 30 B channels and one
64Kbps D channel, and delivered over a single E1
link.
Primary Cell A cell which is already optimized in the network
and has a collocated neighbour whose cell boundary
follows the boundary of the said cell. The primary
cell has a preferred band equal to the frequency type
of the coincident cell.
PRM Packet Resource Manager. A process that performs
all RLC/MAC functions and realises UL/DL power
control and timing advance.
PROM Programmable Read-Only Memory. A storage
device that, after being written once, becomes a
read-only memory.
Protocol A formal set of procedures for transmitting data
between functions within the same layer of a
hierarchy of functions.
Protocol stack Related layers of protocol software that function
together to implement a particular communications
architecture.
11-70 68P02905W21-B
02-Jun-2004
PRP Packet Resource Process(or). A PCU hardware

component that provides radio-related processing
and manages the packet resources at the PCU.
PS-Service Domain Package Switched-Service Domain.
PS Packet Switched. A method in which network nodes
are interconnected by circuits that allow routing of
packets over several different routes.
PSA Periodic Supervision of Accessibility. A fault
management function that sends messages to
Network Elements requesting information on their
current state.
PSA Prepaid Service Agent.
pSAP PCU System Audit Process. A PCU process that
periodically monitors the soft devices to maintain
the reliability of the system.
PSAP Presentation Services Access Point.
PSC Primary Synchronisation Code.
PSCCCH Physical Shared Channel Control Channel.
PSCH Physical Shared Channel.
P-SCP Prepaid Service Control Point. An Intelligent
Network (IN) component that supports the CAMEL
Prepaid Service logic for all GSM services (circuit
switched voice and data, packet switched data and
SMS).
PSDN Packet Switched Data Network.
PSF Power Supply and Fan unit.
pSM PCU Switch Manager.
PSM Power Supply Module.
PSM Platform Shelf Management.
PSP PCU System Processor.
PSPDN Packet Switched Public Data Network. Public data
communications network. x.25 links required for
NE to OMC communications will probably be
carried by PSPDN.
PS-Service Domain Package Switched-Service Domain.
PSTN Public Switched Telephone Network.
PSU Power Supply Unit.
PTCH Packet Traffic CHannel.
PTM Point-To-Multipoint.
PTM-G Point-To-Multipoint Group.
PTM-M Point-To-Multipoint Multicast.
P-TMSI Packet-TMSI.
68P02905W21-B 11-71
02-Jun-2004
PTO Public Telecommunications Operator.

PTP Point-To-Point.
PTP-M Point-To-Point-Multicast.
PTP-CLNS PTP-ConnectionLess Network Service.
PU Payload Unit.
PVC Permanent Virtual Circuit. A permanently
established virtual circuit. A PVC saves the time
associated with establishing and taking down a
circuit.
PW Pass Word.
PWR Power.
11-72 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Q
Q
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
QA Q (Interface) - Adapter. TMN interface adapter used

to communicate with non-TMN compatible devices
and objects. Used to connect MEs and SEs to TMN
(GSM Rec. 12.00).
Q3 Interface between NMC and GSM network.
QFE card Quad FastEthernet card. Provides network
connections on Cluster nodes.
QoS Quality of Service.
QPSK Quadrature Phase Shift Keying.
Queue An ordered list of packets waiting to be forwarded
over a routing interface.
Quiescent mode IDS intermediate state before shutdown.
68P02905W21-B 11-73
02-Jun-2004
R Chapter 11: Glossary of abbreviations
R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
R Value of reduction of the MS transmitted RF power

relative to the maximum allowed output power of
the highest power class of MS (A).
RA Routing Area.
RAB Radio Access Bearer.
RAC Routing Area Code.
RACCH Random Access Control CHannel. A common
control channel used to originate a call or respond
to a page.
RACE Reset And Clock Extender.
RACH Random Access Channel. (Transport Channel)
The RACH is an uplink transport channel that is used
to carry control information from a mobile station.
The RACH may also carry short user packets. The
RACH is always received from the entire cell.
Radio Access Bearer The service that the access stratum provides to the
non-access stratum for transfer of user data between
User Equipment and CN.
Radio Access Network Application Part Radio Network Signalling over the Iu.
Radio connection A logical association between one or more User
Equipments and one or more UTRAN access points
to establish point-to-point, point-to-multipoint,
broadcasting communications or even macro
diversity. A radio connection comprises one or more
radio links.
Radio frame A numbered time interval of 10 ms duration used for
data transmission on the radio physical channel. A
radio frame is divided into 15 time slots of 0.625 ms
duration. The unit of data that is mapped to a radio
frame (10 ms time interval) may also be referred to
as radio frame.
Radio Frequency A term applied to the transmission of
electromagnetically radiated information
from one point to another, usually using air
or vacuum as the transmission medium. An
electromagnetic wave frequency intermediate
between audio frequencies and infrared frequencies
used in radio and television transmission.
Radio interface The tetherless interface between a User Equipment
and a UTRAN access point. This term encompasses
all the functionality required to maintain such
interfaces.
11-74 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview R
Radio link A logical association between a single User

Equipment and a single UTRAN access point. Its
physical realization comprises one or more radio
bearer transmissions.
Radio link addition The procedure where a new radio link is added to
the active set.
Radio link removal The procedure where a radio link is removed from
the active set.
Radio Network Controller This equipment in the RNS is in charge of controlling
the use and the integrity of the radio resources.
(SMG2 ARC)
Radio Network Subsystem Either a full network or only the access part of
a UMTS network offering the allocation and the
release of specific radio resources to establish means
of connection in between an UE and the UTRAN.
A Radio Network Subsystem is responsible for the
resources and transmission/reception in a set of
cells. (SMG2 ARC)
Radio Network Subsystem Application Part Radio Network Signalling over the Iur.
Radio Network Temporary Identifier (RNTI) A Radio Network Temporary Identifier is an
identifier for a UE when an RRC connection exists.
For example, it is used by the MAC protocol on
common Transport Channels (RACH, FACH, PCH).
Radio resource unit A single controllable resource employable for
unidirectional information transfer over the radio
interface. Typical examples for radio bearers are a
time and frequency slot in a TDMA transmission
scheme with frequency hopping, or the portion of
radio resources characterized by a code sequence in
a CDMA transmission scheme.
RADIUS Remote Access Dial-In User Service.
RAI Routeing Area Identity.
RAID Redundant Array of Independent Disks. A method
of storing the same data in different places on
multiple hard drives to improve performance and
fault-tolerance.
RAM Random Access Memory. The temporary memory
that a computer uses to hold the current instructions
and data. All data in RAM is lost when the computer
is turned off.
RAN Radio Access Network.
RANAP Radio Access Network Application Part.
Radio network signalling over the Iu.
RAND RANDom number (used for authentication).
RAP Radio Access Procedures.
RAT Radio Access Technology
68P02905W21-B 11-75
02-Jun-2004
RAU Routeing Area Update.

RCU Radio Channel Unit. Part of the BSS. Contains
transceiver, digital control circuits, and power
supply.
RDB Requirements DataBase.
RDBMS Relational DataBase Management System
(INFORMIX). The database management system
for the OMC-R database.
RDPU Relay layer PDU.
REC, Rec RECommendation.
Receiver Antenna Gain (dBi) The maximum gain of the receiver antenna in the
horizontal plane (specified as dB relative to an
isotropic radiator).
Reciprocal neighbour Used to describe adjacent cells; each being
designated as a neighbour of the other. Also known
as bi-directional and two-way neighbour.
Redundant Spare. A redundant device becomes active if the
primary unit fails.
REJ REJect(ion).
REL RELease.
resync Resynchronize/resynchronization.
REQ REQuest.
Revgen A Motorola DataGen utility for producing an MMI
script from a binary object database.
RF Radio Frequency.
RF Requesting Function.
RFC Request for Comments. Documents used for
communicating standards, specifications, and other
information about the Internet.
RFSI RF to Serial Interface.
RJ-45 Registered Jack-45. An eight-wire connector
commonly used to connect computers on an Ethernet
LAN.
RL Remote login. RL is a means by which the
operator performs configuration management, fault
management, and some performance management
procedures at the NEs. The RL software manages
the X.25 connection for remote login. The circuit is
made by the OMC calling the NE.
RL Radio Link.
RLC Radio Link Control. Air interface transmission layer
which processes the transfer of PDUs from the LLC
layer.
11-76 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview R
RLCP Radio Link Control Protocol.

RLP Radio Link Protocol. An ARQ protocol used to
transfer user data between an MT and IWF. See
GSM 04.22.
RMON Remote Monitoring. A subset of SNMP MIB II
that exchanges network monitoring data between
network monitors and console systems.
RNC Radio Network Controller.
Is in charge of controlling the use and integrity of
the radio resources.
RNL Radio Network Layer.
RNS Radio Network System.
The RNS is responsible for the resources and
transmission/reception in a set of cells. The RNS is
further broken down into RNC and Node B network
elements.
RNSAP Radio Network Subsystem Application Part.
Radio network signalling over the Iur between the
SRNC and DRNC.
RNTI Radio Network Temporary Identity.
There are two types of RNTI:
Controlling RNC RNTI (c-RNTI)
Serving RNC RNTI (s-RNTI).
Roaming Situation where mobile station operates in a cellular
system other than the one from which service is
subscribed.
ROM Random Access Memory.
Router A protocol-dependent device that connects
subnetworks. Routers can break down very
large networks into manageable subnetworks but
introduce longer delays and have slower throughput
rates than bridges.
Routeing bridge A MAC-layer bridge that uses network layer
methods to determine the topology of a network.
Routeing table Table that keeps track of routes to specific network
destinations.
RRC Radio Resource Control.
RRC Connection A point-to-point bi-directional connection between
RRC peer entities on the UE and the UTRAN sides,
respectively. An UE has either zero or one RRC
connection.
RRCAM RRC Acknowledge Mode.
RRCUM RRC Unacknowledge Mode.
RRM Radio Resource Management.
68P02905W21-B 11-77
02-Jun-2004
RS-232 Recommended Standard-232C. A standard interface

for connecting serial devices.
RSCP Received Signal Code Power.
RSL Radio Signalling Link. Interface used for signalling
between the BSC and BTSs.
RSLP Radio System Link Processor.
RSM Route Switch Module.
RSSI Received Signal Strength Indicator.
RST Reset.
RT Real Time.
RTC Remote Tuned Combiner. Channel combiner used
to fine-tune the cavities to the correct frequency.
RTD RLC-block-equivalent Transit Delay.
RTF Receive Transmit Function.
RTS Request To Send. A handshaking signal used with
some communication links to indicate that data is
ready for transmission.
RU Resource Unit.
Rx Receive (uplink).
RXCDR Remote transcoder. Transcoder used at sites located
away from the BSC.
RXLEV Received signal level. An indication of received
signal level based on the RSSI. RXLEV is one of
the two criteria for evaluating the reception quality
(the basis for handover and power control). See
also RXQUAL. The MS reports RXLEV values
related to the apparent received RF signal strength.
It is necessary for these levels to attain sufficient
accuracy for the correct functioning of the system.
RXQUAL Received signal quality. An indication of the
received signal quality based on the BER. RXQUAL
is one of the two criteria for evaluating the reception
quality (the basis for handover and power control).
See also RXLEV. The MS measures the received
signal quality, which is specified in terms of BER
before channel decoding averaged over the reporting
period of length of one SACCH multiframe.
11-78 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview S
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
S7 See SS7.
S/W (or SW) SoftWare.
SAAL Signalling ATM Adaptation Layer.
SABM Set Asynchronous Balanced Mode
SACCH Slow Associated Control CHannel. A GSM control
channel used by the MS for reporting RSSI and
signal quality measurements.
SAP Service Access Point. In the reference model for
OSI, SAPs of a layer are defined as gates through
which services are offered to an adjacent higher
layer.
SAPI Service Access Point Indicator (identifier). The OSI
term for the component of a network address that
identifies the individual application on a host that is
sending or receiving a packet.
SAR Segmentation and Reassembly.
SB Synchronization Burst (see Synchronization burst).
S-CDR SGSN-Call Detail Record.
SC Service Centre.
Scaleable Capable of being scaled to accommodate increased
traffic.
SCCF S-CDR Collection Function.
SCCH Synchronisation Control Channel.
SCCP Signalling Connection Control Part. An SS7
protocol level that provides connectionless
and connection-oriented network services, and
addressing services.
SCCPCH Secondary Common Control Physical Channel.
The SCCPCH is a downlink physical channel that
carries the FACH and PCH to support a mobile
phone call.
SCH Synchronisation Channel. (Physical Channel)
The SCH is a downlink signal used for cell search
and consists of two sub channels.
The Primary SCH consists of an unmodulated
orthogonal code (of length 256 chips) transmitted
once every slot and is the same for every Node B
in the system.
68P02905W21-B 11-79
02-Jun-2004
S Chapter 11: Glossary of abbreviations
The Secondary SCH consists of repeatedly

transmitting a sequence of 16 unmodulated
orthogonal codes (of length 256 chips) in parallel
with the primary SCH. The sequence on the
secondary SCH indicates to which of the 32 different
code groups the Node B downlink scrambling
code belongs. 32 sequences are used to encode
the 32 different code groups, each containing 16
scrambling codes to uniquely determine both the
long code group and the frame timing.
SCP Service Control Point.
SCSI Small Computer System Interface. A parallel
interface standard for attaching peripheral devices
to computers.
SCTF S-CDR Transfer Function.
SCU Slim Carrier Unit (Radio).
SDCCH Stand-alone Dedicated Control CHannel. A GSM
control channel where the majority of call setup
occurs. Used for MS to BTS communications before
the MS is assigned to TCH.
SDH Synchronous Digital Hierarchy.
SDL Simple Data Link.
SDS Solstice DiskSuite. Sun Microsystems software that
provides the HA NFS function in the ISS Cluster.
SDU Service Data Unit. An amount of information that
has its identity preserved when transferred between
peer layers and which is not interpreted by the
supporting layers.
SE Supervisor Engine.
Seamless handover A handover without perceptible interruption of the
radio connection.
Sector A sub-area of a cell. All sectors within one cell
are served by the same base station. A radio link
within a sector can be identified by a single logical
identification belonging to that sector.
SEP Signalling End Point.
Service provider An organization through which a subscriber obtains
GSM/GPRS telecommunications services.
Serving RNS A role an RNS can take with respect to a specific
connection between an UE and UTRAN. There is
one Serving RNS for each UE that has a connection
to UTRAN. The Serving RNS is in charge of the
radio connection between a UE and the UTRAN.
The Serving RNS terminates the Iu for this UE.
(SMG2 ARC).
11-80 68P02905W21-B
02-Jun-2004
Session layer The layer of the OSI reference model that

coordinates communication between systems,
maintains sessions, and performs security, logging
and administrative functions.
SF Spreading Factor.
SFN Spreading Factor Number.
SGSN Serving GPRS Support Node.
SGSN chassis Empty CPX8216 equipment chassis in which the
SGSN hardware module and cards will be housed.
SGSN-CF SGSN-Control Function (card).
SGSN-CONTROL SGSN-CONTROL function.
SGSN-GBPROC SGSN-Gb Processor.
SGSN-GNPROC SGSN-Gn Processor.
SGSN module A 3-card set of equipment contained within an SGSN
chassis. The set contains one Control Function card,
one Gn card, and one Gb card.
SGSN-OAMP SGSN-Operations And Maintenance Processor.
SGSN-TF SGSN-Transmission Function (card).
SGSNu Serving GPRS Support Node, specific to UMTS.
SGSN unit SGSN chassis complete with one SF module, one
to three SGSN modules, and two system processor
cards.
SGW Signalling Gateway.
Shelf Manager The Shelf Manager module is composed of a system
processor card and a HSC bridge card. The Shelf
Manager performs the bus control functions in the
SGSN chassis, enabling the communication between
non-system slot cards over the cPCI bus. It also
performs the shelf level O&M functions including
relaying shelf alarms to the OMC-G and software
load management (BOOTP). Each SGSN chassis
contains two Shelf Manager modules (4 cards in
total).
SI Serialising Interface.
Signalling connection An acknowledged-mode link between the user
equipment and the core network to transfer higher
layer information between the entities in the
non-access stratum.
Signalling link Provides an acknowledged-mode link layer to
transfer the MS-UTRAN signalling messages as
well as MS - Core Network signalling messages
(using the signalling connection).
SIM Subscriber Identity Module. A removable module
within an MS that contains all information for that
subscriber.
68P02905W21-B 11-81
02-Jun-2004
SIR Signal to Interference Ratio.

SITE BSC, BTS or collocated BSC-BTS site.
SLC Signalling Link Code.
SLS Signalling Link Set.
SM Session Management. Facilitates the transfer of
PDP contexts.
SM Short Message.
SM—AL Short Message Application Layer.
SM—CP Short Message Control Protocol.
SM—RL Short Message Relay Layer.
SM—TL Short Message Transport Layer.
SMC Short Message Control (entity).
SMC Short Message Centre.
SMG Special Mobile Group. The group responsible for
developing mobile networking technologies such
as GSM and GPRS.
SMI Short Message Identifier.
SMI Structure of Management Information. Rules in
RFC 1155that specify how managed objects in the
MIB are defined.
SMLC Serving Mobile Location Center.
SMO message Short Message Service Mobile Originated message.
SMR Short Message Relay (entity).
SMS Short Message Service. A globally-accepted
wireless service that enables the transmission of
alphanumeric messages between mobile subscribers
and external systems such as e-mail, paging, and
voice-mail systems.
SMS-C Short Message Service-Centre.
SMSCB Short Message Service Cell Broadcast. SMSCB is a
service in which short messages may be broadcast
from a PLMN to MSs. SMSCB messages come
from different sources (for example, traffic reports,
weather reports). Messages are not acknowledged
by the MS. Reception of SMSCB messages by the
MS is only possible in idle mode. The geographical
area over which each message is transmitted is
selected by the PLMN operator, by agreement with
the provider of the information.
SMS-CDR Short Message Service-CDR.
SMS-GMSC SMS-Gateway Mobile Switching Centre.
SMS-IWMSC SMS-InterWorking Mobile Switching Centre.
11-82 68P02905W21-B
02-Jun-2004
SMT Station Management. An ANSI FDDI specification

that defines how ring stations are managed.
SMT message Short Message Service Mobile Terminated message.
SN-PDU SubNetwork-Protocol Data Unit.
SN Subscriber Number.
SND SeND.
SNDR SeNDeR.
SNDCP SubNetwork Dependent Convergence Protocol.
SNMP Simple Network Management Protocol.
Soft Handover Is a category of handover procedures where the radio
links are added and abandoned in such a manner that
the UE always keeps at least one radio link to the
UTRAN. This typically involves multiple Node Bs.
Softer Handover Is a type of handover that involves one or more cells
of the same Node B.
Software Instance A complete set of software and firmware objects
including the database object.
SP Signalling Point.
SP Switching Point.
SPAN Switched Port Analyzer. Monitors traffic on any port
for analysis by a network analyzer or RMON probe.
Spare A module The Spare A module (card) is a field replacement
module (card) for CF, Gb or C7 modules. It consists
of a non-system slot card and two dual E1 PMCs.
Spare B module The Spare B module (card) is a field replacement
module (card) for the Gn module. It consists of
a non-system slot card and one PMC encryption
module.
SPC Signalling Point Code.
Spectrum efficiency A comparative measure characterizing the extent to
which a radio interface is able to support a given
number of users of a given UMTS service. Spectrum
efficiency can be measured in ETE per cell per MHz
or ETE per square kilometre per MHz.
SPOF Single Point Of Failure.
SPROC System Processor.
Is a MPC750 processor that is responsible for
executing all of the site resident software.
SQL Structured Query Language.
SR Service Request.
SRAM Static RAM.
68P02905W21-B 11-83
02-Jun-2004
SRES Signed RESponse. An authentication and ciphering

response.
SRNC Serving Radio Network Controller.
management of a particular user’s radio access
signalling and bearer connection to the Iu-CS
interface.
User-plane functions that pertain to the management
of the bearer data stream for a particular user’s radio
access signalling and bearer connection to the Iu-PS
interface.
SRNS Serving RNS.
SRNS relocation The change of Iu instance. It should be noted
that SRNS Relocation was previously known as
Streamlining.
SS Supplementary Service. A modification of, or a
supplement to, a basic telecommunications service.
SS7 Signalling System No. 7.
SS7 card A card that provides the logical interface to the
HLR, MSC/VLR, and SM-SC.
S-SMO-CDR SGSN-delivered Short message Mobile Originated -
Call Detail Record.
S-SMT-CDR SGSN-delivered Short message Mobile Terminated
- Call Detail Record.
SSC Secondary Synchronisation Code.
SSCF Service Specific Co-ordination Function.
SSCF-NNI Service Specific Co-ordination Function - Network
Node Interface.
SSCOP Service Specific Connection Oriented Protocol.
SSCS Service Specific Convergence Sublayer.
SSDT Service Specific Diversity Transmission.
SSN Subsystem Number.
SSP System Slot Processor. A card that acts as an
Ethernet switch and passes data between all system
cards and to any other switches connected to the
system.
SSP Service Switching Point. An element of SS7 that
performs call origination, termination or tandem
switching.
SSSAR Service Specific Segmentation and Reassembly
sublayer.
ST Subscriber Trace.
11-84 68P02905W21-B
02-Jun-2004
Standard A set of detailed technical guidelines used as a

means of establishing uniformity in an area of
hardware or software development.
STAT STATistics.
stats Statistics.
STC Signalling Transport Converter.
STM-1 Synchronous Transfer Mode-1.
STM-4 Synchronous Transfer Mode-4.
STP Signalling Transfer Point. Packet switch that
routes SS7 messages based on routeing information
obtained by a service switching point.
Stratum Hierarchical clock reference in the PSTN network,
where 1 represents the highest possible quality of
clocking.
Streamlining Process which changes the role of an RNS (serving
and drift) when one or multiple drift RNSs are
involved in a connection.
STTD Space Time Transmit Diversity.
STUN Serial Tunnelling.
Sun Cluster Sun Microsystems components located in the ISS
Cluster.
SunOS Sun Microsystem’s UNIX Operating System.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period
6.12s).
Super user User account that can access all files, regardless of
protection settings, and control all user accounts.
SVC Switched Virtual Circuit. A virtual circuit or
connection that is established dynamically in
response to a signalling request message.
SW Software.
Switching Process of taking incoming traffic from one interface
and delivering it through another.
sync synchronize/synchronization.
System processor Card that manages the CF, TF (Gn and Gb), and SF
modules in the SGSN chassis.
Synchronization burst Period of RF carrier less than one timeslot whose
modulation bit stream carries information for the
MS to synchronize its frame to that of the received
signal.
Synthesizer hopping Synthesizer hopping is a method of frequency
hopping in which the RCUs are re-tuned in real-time,
from frequency to frequency.
68P02905W21-B 11-85
02-Jun-2004
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for
loading a configuration database into a BTS.
11-86 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview T
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
T Timer.
T1 North American point-to-point communications
circuit for voice and data transmissions. Also see E1.
TA Terminal Adaptor. A physical entity in the MS
providing terminal adaptation functions (see GSM
04.02).
TAC Technical Assistance Centre.
TACS Total Access Communication System. European
analogue cellular system.
TAP Transferred Accounts Procedure.
TBD To Be Determined.
TBF Temporary Block Flow.
Tc Committed rate measurement interval. The time
interval during which a user can send Bc and Be
amounts of data. In general, Tc is computed as
Tc=Bc/CIR. Tc is not a periodic time interval but
used only to measure incoming data.
TC Terminal Concentrator.
TC Transmission Convergence.
TCAP Transaction Capabilities Application Part (SS7).
TCH Traffic CHannel. GSM logical channels that carry
either encoded speech or user data.
TCI Transceiver Control Interface.
TCL Tool Command Language.
TCP Transmission Control Protocol. One of the main
protocols in a TCP/IP network. TCP enables two
hosts to establish a connection and exchange streams
of data. TCP guarantees delivery of data and that
packets will be delivered in the same order in which
they were sent.
TCP/IP TCP over Internet Protocol. A suite of
communications protocols used to connect hosts on
the Internet.
TDD Time Division Duplex.
TDM Time Division Multiplexing. A type of multiplexing
that combines data streams by assigning each stream
a different time slot in a set.
TDMA Time Division Multiple Access.
68P02905W21-B 11-87
02-Jun-2004
T Chapter 11: Glossary of abbreviations
TDP Trigger Detection Point. An initial Prepaid Service

event, which triggers the establishment of a
relationship between the GSN and the P-SCP.
TDP-R TDP Request.
TDV Traffic Data Volume.
TE Terminal Equipment. Equipment that provides the
functions necessary for the operation of the access
protocols by the user.
TEI Temporary Equipment Identifier.
Telnet Standard terminal emulation protocol used for
remote terminal connections, enabling users to log
in to remote systems and use resources as if they
were connected to a local system.
TEMP TEMPorary.
Terminal Concentrator Terminal equipment that provides console access
to the ISS.
TF Transmission Function.
TF Transport Format.
TFC Transport Format Combination.
TFCI Transport Format Combination Indicator.
TFCS Transport Format Combination Set.
TFI Transport Format Indicator.
TFO Tandem Free Operation.
TFS Transport Format Set.
TFTP Trivial File Transfer Protocol. A simplified version
of the TCP/IP file transfer protocol that allows the
transfer of files from one computer to another over
a network.
TGL Transmission Gap Length.
Threshold A trigger point that, when crossed, causes an alarm
or event report to be sent to the OMC-G or OMC-R.
Throughput The amount of data transferred over a connection
during a specific time period, usually measured as
characters per second.
TID Tunnel IDentifier. Identifier for a GTP tunnel. The
TID contains an MM Context ID and a NAPI.
Timeslot The multiplex subdivision in which voice and
signalling bits are sent over the air. Each RF carrier
is divided into 8 timeslots.
Timing advance A signal sent by the BTS to the MS. It enables the
MS to advance the timing of its transmission to the
BTS so as to compensate for propagation delay.
TLLI Temporary Logical Link Identity.
11-88 68P02905W21-B
02-Jun-2004
TM Transition Module.
TMN Telecommunications Management Network. The
physical entities required to implement the Network
Management functionality for the PLMN.
Also, TMN was originated formally in 1988 under
the ITU-TS as a strategic goal to create or identify
standard interfaces that would allow a network
to be managed consistently across all network
element suppliers. The concept has led to a series of
interrelated efforts at developing standard ways to
define and address network elements. TMN uses the
OSI Management Standards as its framework. TMN
applies to wireless communications and cable TV as
well as to private and public wired networks.
TMSI Temporary Mobile Subscriber Identity. A temporary
code used to identify an MS. The TMSI is assigned
using encryption after the HLR has identified the
MS.
TN Termination Node.
TOC Table of Contents.
TOM Tunnelling of Messages.
Topology A logical characterization of how the devices on a
network are connected.
TPC Transmit Power Control.
T-PDU Tunnelling Protocol Data Unit. A packet originating
from an MS or network node in an external PDN.
The T-PDU is encapsulated with a GTP header
(making it a G-PDU) so it can be transmitted in a
GTP tunnel.
TPDU Transfer layer PDU.
TPDU Transfer layer PDU.
Traffic channel A logical channel which carries user speech or data.
Training sequence Sequence of modulating bits employed to facilitate
timing recovery and channel equalization in the
receiver.
Transmission Time interval Defined as the inter-arrival time of Transport Block
Sets, that is, the time it should take to transmit a
Transport Block Set. It is always a multiple of 10 ms
(the length of one Radio Frame).
Transport Block Defined as the basic unit passed down to L1 from
MAC, for L1 processing. An equivalent term for
Transport Block is MAC PDU.
Transport Block set Defined as a set of Transport Blocks which is passed
to L1 from MAC at the same time instance using
the same transport channel. An equivalent term for
Transport Block Set is MAC PDU Set.
68P02905W21-B 11-89
02-Jun-2004
T Chapter 11: Glossary of abbreviations
Transport Block set size Defined as the number of bits in a Transport Block
Set.
Transport Block size Defined as the size (number of bits) of a Transport
Block.
Transport channel The channels offered by the physical layer to Layer
2 for data transport between peer L1 entities are
denoted as Transport Channels. Different types of
transport channels are defined by how and with
which characteristics data is transferred on the
physical layer; for example, whether using dedicated
or common physical channels are employed.
Transport Format Defined as a format offered by L1 to MAC for
the delivery of a Transport Block Set during a
Transmission Time Interval on a Transport Channel.
The Transport Format constitutes of two parts —
one dynamic part and one semi-static part.
Transport Format Combination Defined as the combination of currently valid
Transport Formats on all Transport Channels of an
MS, that is, containing one Transport Format from
each Transport Channel.
Transport Format Combination Set Defined as a set of Transport Format Combinations
to be used by an MS.
Transport Format Combination Indicator (TFCI) A representation of the current Transport Format
Combination.
Transport Format Identification (TFI) A label for a specific Transport Format within a
Transport Format Set.
Transport Format Set A set of Transport Formats. For example, a variable
rate DCH has a Transport Format Set (one Transport
Format for each rate), whereas a fixed rate DCH has
a single Transport Format.
Transport layer The protocol layer that responds to service requests
from the Session Layer and issues service requests to
the Network Layer. It provides transparent transfer
of data between end users, relieving the upper
layers from any concern with providing reliable and
cost-effective data transfer.
TRAU Transcoder Rate Adapter Unit.
TrCH Transport Channel.
TRS Timeslot Resource Shifter.
TRX Transceiver(s). A network component which can
serve full duplex communication on 8 full-rate
traffic channels according to specification GSM
05.02. If Slow Frequency Hopping (SFH) is not
used, then the TRX serves the communication on
one RF carrier.
TS Time Service. A server maintaining and distributing
the correct time and date over a computer network.
11-90 68P02905W21-B
02-Jun-2004
TS TimeSlot.
TSC Training Sequence Code. A training sequence is sent
at the centre of a burst to help the receiver identify
and synchronize to the burst. The training sequence
is a set sequence of bits which is known by both the
transmitter and receiver. There are eight different
TSCs numbered 0 to 7. Nearby cells operating with
the same RF carrier frequency use different TSCs to
allow the receiver to identify the correct signal.
TSN Trau SynchronizatioN process at PCU.
TSTD Time Switched Transmit Diversity.
TTI Transmission Timing Interval.
TTL Time To Live. Field in an IP header that indicates
how long a packet is considered valid.
TTY/tty TeleTYpe (refers to any terminal).
Tunnelling The encapsulation of one protocol within another to
transport it across a backbone that does not support
the original protocol.
Two-way neighbour See Reciprocal neighbour.
Tx Transmit/Transmitter (downlink).
68P02905W21-B 11-91
02-Jun-2004
U Chapter 11: Glossary of abbreviations
U
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
UA Unnumbered Acknowledgment. A message sent

from the MS to the BSS to acknowledge release of
radio resources when a call is being cleared.
UARFCN UTRA Absolute Radio Frequency Channel Number.
UARFN UTRA Absolute Radio Frequency Number.
UBR Unspecified Bit Rate.
UDD Unconstrained Delay Data.
UDP User Datagram Protocol. A TCP/IP protocol that
allows an application on one machine to send a
datagram to an application on another machine.
UDP/TCP User Datagram Protocol/Transmission Control
Protocol.
UE User Equipment.
UER User Equipment with ODMA relay operation
enabled.
UFS UNIX File System.
UHF Ultra High Frequency. The UHF range of the radio
spectrum is the band extending from 300 MHz to 3
GHz.
UID User ID. Unique number used by the system to
identify the user.
UL UpLink. (Reverse Link)
ULC UpLink Concatenator.
Um Air interface between a BTS and MS.
UMTS Universal Mobile Telecommunications System.
A 3G wireless telecommunications system with
standards developed by the Third Generation
Partnership Project (3GPP).
UMTS Terrestrial Radio Access Network UTRAN is a conceptual term identifying that part
of the network which consists of RNCs and Node
Bs between Iu an Uu. The concept of UTRAN
instantiations is currently undefined. (SMG2 ARC).
UNI User to Network Interface.
UNIX Open platform, multi-user, multi-tasking operating
system.
UP User Plane.
UPC Usage Parameter Control.
11-92 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview U
Uplink A unidirectional radio link for the transmission of

signals from a Mobile Station to a base station, from
a Mobile Station to a mobile base station or from a
mobile base station to a base station.
UPS Uninterruptible Power Supply. Power system
designed to protect mission-critical networks against
power-outages, brownouts, power surges and spikes.
URA UTRAN Registration Area.
URA updating A family of procedures that updates the UTRAN
registration area of a UE when a RRC connection
exists and the position of the UE is known on URA
level in the UTRAN.
URIB UMTS Radio Interface Board.
URXB UMTS Receiver Board.
USB Universal Serial Bus. A serial bus standard that
delivers power to peripherals on the bus and
eliminates separate power cords.
USCH Uplink Shared Channel.
User Equipment A Mobile Equipment with one or several User
Services Identity Modules(s).
USIM UMTS Subscriber Identity Module.
USNB UMTS Synthesiser Board.
USSD Unstructured Supplementary Services Data.
UTC Universal Time Coordinated.
UTF Upper Transmission Function. Gn interface
communication protocol functions.
UTRA UMTS Terrestrial Radio Access (ETSI); Universal
Terrestrial Radio Access (3GPP).
UTRAN UMTS Terrestrial Radio Access Network.
UTRAN access point A conceptual point within the UTRAN performing
radio transmission and reception. A UTRAN access
point is associated with one specific cell, that is,
there exists one UTRAN access point for each cell.
It is the UTRAN-side end point of a radio link.
UTRAN Registration Area (URA) An area covered by a number of cells. The URA is
only internally known in the UTRAN.
UTXB UMTS Transmitter Board.
Uu Radio (Air) interface between the Node B network
element and UE.
The information exchange is for the purpose of
passing signalling and data information.
68P02905W21-B 11-93
02-Jun-2004
V Chapter 11: Glossary of abbreviations
V
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
V.42 An ITU-T protocol for error correction.

V.42bis A standard that provides data compression as an
extension of the V.42 protocol.
V Value only.
VA Voice Activity factor.
VBR Variable Bit Rate.
VCAT Vector Capture and Analysis Tool.
VC Virtual Circuit/Channel. Service enabling two end
points to communicate as though connected by a
physical circuit.
VCC Virtual Channel Connection. Logical circuit that
carries data between two end points. Sometimes
called a Virtual Circuit Connection.
VDU Visual Display Unit. A device used for the real-time
temporary display of computer output data. Monitor.
VGGSN Visited GGSN.
VHLR Visited HLR.
VIP2 Versatile Interface Processor 2. A T1/E1 serial
module.
Virtual Circuit A connection between two devices, that functions
as though it is a direct connection, even though it
may physically be circuitous. The term is used most
frequently to describe connections between two
hosts in a packet-switching network.
VLAN Virtual Local Area Network. Group of devices on
different LAN segments that are logically configured
to communicate as if they are attached to the same
wire.
VLR Visitor Location Register.
VMPS VLAN Membership Policy Server.
VP Virtual Path.
VPC Virtual Path Connection.
VPLMN Visited PLMN. A PLMN to which an MS has
roamed from its HPLMN.
VPN Virtual Private Network. Connection that has
the appearance and many of the advantages of a
dedicated link but occurs over a shared network.
VSGSN Visited SGSN.
11-94 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview V
VSWR Voltage Standing Wave Ratio. In a transmission

line, the ratio of maximum to minimum voltage
in a standing wave pattern. Note: The VSWR is
a measure of impedance mismatch between the
transmission line and its load. The higher the
VSWR, the greater the mismatch. That is, the
minimum VSWR which corresponds to a perfect
impedance match, is unity.
VT Virtual Template. A logical interface configured
with generic information for a purpose or
configuration common to specific users, plus
router-dependent information.
VTP VLAN Trunking Protocol. Protocol used for
connecting two or more Cisco switches and
providing load-sharing. It maintains VLAN
configuration consistency throughout the network.
68P02905W21-B 11-95
02-Jun-2004
W Chapter 11: Glossary of abbreviations
W
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
W Watt. Measurement of the rate of energy flow.

WAN Wide Area Network. A physical or logical network
that provides data communications to a larger
number of independent users than are usually
served by a LAN and is usually spread over a larger
geographic area than that of a LAN. WANs may
include physical networks, such as ISDN networks,
X.25 networks, and T1 networks.
WAP Wireless Application Protocol.
WCDMA Wideband CDMA.
WDM Wideband Digital Modem.
WFMR WCDMA RNC radio frame processing board.
WHPU WCDMA RNC High speed packet processing board.
WLPU WCDMA RNC Line Processing board.
WMPU WCDMA RNC Switch Module Main Processing
board.
WMUX WCDMA RNC System Multiplexing board.
WNET WCDMA RNC Network Switch board.
WOSE WCDMA RNC Single Mode Optical Interface board
of E1/T1.
WOME WCDMA RNC Multi-mode Optical interface board
of E1/T1.
WRBS WCDMA RNC Business Subrack.
WRSS WCDMA RNC Switch Subrack.
WS Work Station.
WSPU WCDMA RNC Signalling Processing board.
WWW World Wide Web. An Internet-based hypertext
system.
WXIE WCDMA RNC general(X)E1/T1 Interface board.
11-96 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview X
X
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25 X.25, adopted as a standard by the CCITT, is a

commonly used protocol for public packet-switched
networks (PSPDNS). The X.25 protocol allows
computers on different public networks to
communicate through an intermediary computer at
the network layer level. The protocol corresponds
closely to the data-link and physical-layer protocols
defined in the OSI communication model.
X.25 link A communications link which conforms to X.25
specifications and uses X.25 protocol (NE to OMC
links).
XCDR Full-rate Transcoder. The XCDR is the digital
signal processing equipment required to perform
GSM-defined speech encoding and decoding. In
terms of data transmission, the speech transcoder
interfaces the 64 kbit/s PCM in the land network
to the 13 kbit/s vocoder format used on the Air
Interface. See also RXCDR.
XID Exchange Identifier. An identifier that allows two
nodes to recognize each other and to establish link
and node characteristics for communicating.
XML Extensible Markup Language.
X-Term X terminal window.
68P02905W21-B 11-97
02-Jun-2004
X Chapter 11: Glossary of abbreviations
11-98 68P02905W21-B
02-Jun-2004
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
2 Mbit/s link . . . . . . . . . . . . . . . . . . 2-23
A
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Abbreviations ATM
Numbers . . . . . . . . . . . . . . . . . . 11-2 introduction . . . . . . . . . . . . . . . . . 4-5
AICH . . . . . . . . . . . . . . . . . . . . . 5-30 inverse multiplexing . . . . . . . . . . . . . 4-19
Air Interface . . . . . . . . . . . . . . . . . . 3-4 typical transport network . . . . . . . . . . . 4-27
channels . . . . . . . . . . . . . . . . . . . 5-8 virtual channels and paths . . . . . . . . . . 4-13
overview . . . . . . . . . . . . . . . . . . 5-4 AUC . . . . . . . . . . . . . . . . . . . . . 2-37
allocating handover numbers Authentication and Key Agreement . . . . . . . 2-39
overview . . . . . . . . . . . . . . . . . . 2-44 AUthentication Centre
allocating TMSI numbers Authentication centre. . . . . . . . . . . . . 2-37
overview . . . . . . . . . . . . . . . . . . 2-44
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
billing centre . . . . . . . . . . . . . . . . . . 2-13
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
C7. . . . . . . . . . . . . . . . . . . . 2-21, 2-32 CDMA (contd.)

call control functions theory . . . . . . . . . . . . . . . . . . . . 6-2
overview . . . . . . . . . . . . . . . . . . 2-33 Cell Broadcast Centre (CBC) . . . . . . . . . . 2-14
call handling Channel Code Tree . . . . . . . . . . . . . . . 6-12
overview . . . . . . . . . . . . . . . . . . 2-45 Channel coding . . . . . . . . . . . . . . . . 5-40
call management communication link . . . . . . . . . . . . . . 3-4
functional layering . . . . . . . . . . . . . . 2-17 controlling LAIs
CBC. . . . . . . . . . . . . . . . . . . . . . 2-14 overview . . . . . . . . . . . . . . . . . . 2-41
CDMA controlling MSRNs
characteristics . . . . . . . . . . . . . . . . 6-6 overview . . . . . . . . . . . . . . . . . . 2-44
direct spread . . . . . . . . . . . . . . . . . 6-8 Core Network . . . . . . . . . . . . . . . . . 2-10
introduction . . . . . . . . . . . . . . . . . 6-3 interfaces . . . . . . . . . . . . . . . . . . 2-18
multi-path radio channels . . . . . . . . . . . 6-20 overview . . . . . . . . . . . . . . . . . . 2-10
scrambling and summation . . . . . . . . . . 6-16 subsystems . . . . . . . . . . . . . . . . . 2-13
spreading and despreading . . . . . . . . . . 6-10 CPICH . . . . . . . . . . . . . . . . . . . . 5-21
68P02905W21-B IX-1
02-Jun-2004
Index
D
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Downlink dedicated physical channels . . . . . . 5-33 Downlink spreading (contd.)

Downlink flow process . . . . . . . . . . . . . 5-38 and channel combining . . . . . . . . . . . . 5-46
Downlink spreading DPCH . . . . . . . . . . . . . . . . . . . . . 5-33
E
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
E1 equipment identity
architecture . . . . . . . . . . . . . . . . . 4-16 mobile
definition . . . . . . . . . . . . . . . . . . 2-23 international. . . . . . . . . . . . . . . . 3-27
Echo Canceller . . . . . . . . . . . . . . . . . 2-13 Equipment Identity Register (EIR). . . . . . . . 3-27
EIR . . . . . . . . . . . . . . . . . . . 2-11, 3-27 overview . . . . . . . . . . . . . . . . . . 2-36
emergency calls Error handling procedure . . . . . . . . . . . . 7-26
overview . . . . . . . . . . . . . . . . . . 2-33
F
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
FDMA. . . . . . . . . . . . . . . . . . . . . 6-5 functional layering . . . . . . . . . . . . . . . 2-16
G
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GGSNu . . . . . . . . . . . . . . . . . . . . 2-10 Glossary of technical terms (contd.)

Glossary of technical terms N. . . . . . . . . . . . . . . . . . . . . 11-59
A. . . . . . . . . . . . . . . . . . . . . . 11-3 Numbers . . . . . . . . . . . . . . . . . . 11-2
B. . . . . . . . . . . . . . . . . . . . . . 11-9 O. . . . . . . . . . . . . . . . . . . . . 11-63
C. . . . . . . . . . . . . . . . . . . . . 11-14 P . . . . . . . . . . . . . . . . . . . . . 11-65
D. . . . . . . . . . . . . . . . . . . . . 11-25 Q. . . . . . . . . . . . . . . . . . . . . 11-73
E . . . . . . . . . . . . . . . . . . . . . 11-31 R. . . . . . . . . . . . . . . . . . . . . 11-74
F . . . . . . . . . . . . . . . . . . . . . 11-34 S . . . . . . . . . . . . . . . . . . . . . 11-79
G. . . . . . . . . . . . . . . . . . . . . 11-37 T . . . . . . . . . . . . . . . . . . . . . 11-87
H. . . . . . . . . . . . . . . . . . . . . 11-42 U. . . . . . . . . . . . . . . . . . . . . 11-92
I . . . . . . . . . . . . . . . . . . . . . 11-44 V. . . . . . . . . . . . . . . . . . . . . 11-94
J . . . . . . . . . . . . . . . . . . . . . 11-49 W. . . . . . . . . . . . . . . . . . . . . 11-96
K. . . . . . . . . . . . . . . . . . . . . 11-50 X. . . . . . . . . . . . . . . . . . . . . 11-97
L . . . . . . . . . . . . . . . . . . . . . 11-51 GSNu
M. . . . . . . . . . . . . . . . . . . . . 11-54 interfaces . . . . . . . . . . . . . . . . . . 7-2
H
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
HLR. . . . . . . . . . . . . . . . 2-11, 2-36, 3-28 Home Location Register (HLR)

data . . . . . . . . . . . . . . . . . . . . . 2-37 overview . . . . . . . . . . . . . . . . . . 2-36
master database . . . . . . . . . . . . . . . 2-37
IX-2 68P02905W21-B
02-Jun-2004
System Information: UMTS Overview Index
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
IMEI . . . . . . . . . . . . . . . . . . . . . 3-27 Iub interface (contd.)

IMSI . . . . . . . . . . . . . . . . . . . . . 3-28 procedures. . . . . . . . . . . . . . . . . . 7-15
Insertion of DTX indication . . . . . . . . . . . 5-42 protocol structure . . . . . . . . . . . . . . 7-8
inter<<#0106>MSC handovers . . . . . . . . . 2-36 Radio network layer . . . . . . . . . . . . . 7-12
Interfaces Radio network control plane . . . . . . . . 7-12
description of . . . . . . . . . . . . . . . . 7-2 User plane . . . . . . . . . . . . . . . . 7-12
UMTS . . . . . . . . . . . . . . . . . . . 2-15 transport network layer . . . . . . . . . . . . 7-10
International Mobile station Equipment Identity Iur interface . . . . . . . . . . . . . . . . . . 7-27
(IMEI). . . . . . . . . . . . . . . . . . . . . 3-27 AAL2 . . . . . . . . . . . . . . . . . . . . 7-33
International Mobile Subscriber Identity common transport channel frame structures . . 7-50
(IMSI) . . . . . . . . . . . . . . . . . . . . . 3-28 Data exchange . . . . . . . . . . . . . . . . 7-29
Interworking Function . . . . . . . . . . . . . 2-13 data frames . . . . . . . . . . . . . . . . . 7-29
Iu interface dedicated channel frame structures . . . . . . 7-54
AAL2 . . . . . . . . . . . . . . . . . . . . 7-58 MAC flow control . . . . . . . . . . . . . . 7-30
AAL5 . . . . . . . . . . . . . . . . . . . . 7-58 Network layers. . . . . . . . . . . . . . . . 7-27
Protcol modes of operation Radio Network Layer . . . . . . . . . . . 7-27
Support Mode for predefined SDU size . . . 7-64 Transport Network Layer. . . . . . . . . . 7-27
Transparent Mode (TM) . . . . . . . . . . 7-64 protocol structure . . . . . . . . . . . . . . 7-31
RAB signalling . . . . . . . . . . . . . . . 7-58 Protocol structure . . . . . . . . . . . . . . 7-31
Radio network control plane . . . . . . . . . 7-60 Quality Estimate Indicator . . . . . . . . . . 7-30
Radio network layer . . . . . . . . . . . . . 7-60 Radio network layer . . . . . . . . . . . . . 7-35
Radio network control plane . . . . . . . . 7-65 Radio network control plane . . . . . . . . 7-35
User plane . . . . . . . . . . . . . . . . 7-65 User plane . . . . . . . . . . . . . . . . 7-35
Transport layer. . . . . . . . . . . . . . . . 7-60 Radio network signalling . . . . . . . . . . . 7-28
Radio network control plane . . . . . . . . 7-62 Signalling . . . . . . . . . . . . . . . . . . 7-28
Transport network control plane . . . . . . 7-62 Transport layer. . . . . . . . . . . . . . . . 7-33
User plane . . . . . . . . . . . . . . . . 7-62 Radio network control plane . . . . . . . . 7-33
Transport network control plane. . . . . . . . 7-60 Transport network control plane . . . . . . 7-33
User plane . . . . . . . . . . . . . . . . . . 7-60 User plane . . . . . . . . . . . . . . . . 7-33
Iu-CS interface . . . . . . . . . . . . . . 2-32, 7-58 User data streams
protocol structure . . . . . . . . . . . . . . 7-60 DCH . . . . . . . . . . . . . . . . . . . 7-29
Iu-PS interface . . . . . . . . . . . . . . . . . 7-58 DSCH . . . . . . . . . . . . . . . . . . 7-29
protocol structure . . . . . . . . . . . . . . 7-60 FACH. . . . . . . . . . . . . . . . . . . 7-29
Iub interface . . . . . . . . . . . . . . . . . . 7-6 RACH . . . . . . . . . . . . . . . . . . 7-29
control plane and protocol stacks . . . . . . . 7-13 IWF . . . . . . . . . . . . . . . . . . . . . . 2-13
L
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
local registration and call handover Location Register (contd.)

overview . . . . . . . . . . . . . . . . . . 2-34 interfaces . . . . . . . . . . . . . . . 2-18, 2-32
Location Register Location Registers (LR) . . . . . . . . . . . . 2-11
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Management Layer . . . . . . . . . . . . . . . 2-17 Mobile Application Part (MAP) . . . . . . 2-18, 2-32

MAP . . . . . . . . . . . . . . . . . . 2-18, 2-32 Mobile services Switching Centre (MSC)
migration overview . . . . . . . . . . . . . . . . . . 2-11
from GSM/GPRS to UMTS. . . . . . . . . . 2-56
68P02905W21-B IX-3
02-Jun-2004
Index
Mobile services Switching Centre for UMTS MS to MS calls (contd.)

(MSCu) . . . . . . . . . . . . . . . . . . . . 2-30 MS to MS (contd.)
Mobile Subscriber ISDN (MSISDN) number . . . 3-28 same PLMN. . . . . . . . . . . . . . . . 2-46
mobility management overview . . . . . . . . . . . . . . . . . . 2-46
functional layering . . . . . . . . . . . . . . 2-17 MS to PSTN subscriber
module overview . . . . . . . . . . . . . . . . . . 2-45
information MSC
subscriber . . . . . . . . . . . . . . . . . 3-28 interfaces . . . . . . . . . . . . . . . . . . 2-32
MS to MS calls MSCu . . . . . . . . . . . . . . . . . . 2-11, 2-30
MS to MS MSISDN . . . . . . . . . . . . . . . . . . . 3-28
different PLMN different country . . . . . . 2-48 MTP . . . . . . . . . . . . . . . . . . . . . 2-21
different PLMN same country . . . . . . . 2-47 Multiple access schemes . . . . . . . . . . . . 6-4
N
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NBAP . . . . . . . . . . . . . . . . . . . . . 2-19 NMC . . . . . . . . . . . . . . . . . . 2-12, 2-50

NBAP common procedures . . . . . . . . . . . 7-19 interface . . . . . . . . . . . . . . . . . . . 2-18
NBAP dedicated procedures. . . . . . . . . . . 7-24 Node B . . . . . . . . . . . . . . . . . . 2-8, 3-6
network elements cabinets . . . . . . . . . . . . . . . . . . . 3-13
Location Registers configurations . . . . . . . . . . . . . . . . 8-4
overview . . . . . . . . . . . . . . . . . 2-11 description. . . . . . . . . . . . . . . . . . 3-22
Node B functions . . . . . . . . . . . . . . . . . . 3-22
overview . . . . . . . . . . . . . . . . . 2-8 overview and types. . . . . . . . . . . . . . 8-3
OMC-U . . . . . . . . . . . . . . . . . . . 2-9 Node B cabinet
RNC external view . . . . . . . . . . . . . . . . 8-4
overview . . . . . . . . . . . . . . . . . 2-8 indoor and outdoor use . . . . . . . . . . . . 8-3
UE Node B Outdoor
overview . . . . . . . . . . . . . . . . . 2-8 overview . . . . . . . . . . . . . . . . . . 8-7
Network Management Centre (NMC) . . . . . . 2-50 Node B Outdoor Ancillary enclosure
overview . . . . . . . . . . . . . . . . . . 2-12 overview . . . . . . . . . . . . . . . . . . 8-9
Node B outdoor enclosure
overview . . . . . . . . . . . . . . . . . . 8-7
O
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
O&M . . . . . . . . . . . . . . . . . . . . . 3-29 OMC-U (contd.)

OMC NT server hardware . . . . . . . . . . . . . 10-8
platforms . . . . . . . . . . . . . . . . . . 10-8 optional features in USR1.0. . . . . . . . . 10-29
OMC-S/T overview . . . . . . . . . . . . 2-9, 10-3, 10-10
overview . . . . . . . . . . . . . . . . . . 2-12 Performance management . . . . . . . . . 10-21
role . . . . . . . . . . . . . . . . . . . . . 3-31 role . . . . . . . . . . . . . . . . . . . . . 3-31
OMC-U . . . . . . . . . . . . . . . . . . . . 10-2 Security Management . . . . . . . . . . . 10-24
Configuration Management . . . . . . . . . 10-16 UNIX server hardware . . . . . . . . . . . . 10-9
Fault Management . . . . . . . . . . . . . 10-11 Orthogonal codes. . . . . . . . . . . . . . . . 6-11
features in USR1.0 . . . . . . . . . . . . . . 10-4 OSI . . . . . . . . . . . . . . . . . . . . . . 2-19
general application functions . . . . . . . . 10-26 overview
interfaces . . . . . . . . . . . . . . . . . 10-23 of this manual . . . . . . . . . . . . . . . . 1-2
Load and Database Management . . . . . . 10-20
IX-4 68P02905W21-B
02-Jun-2004
P
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
P-CCPCH Physical Layer (contd.)

frame structure. . . . . . . . . . . . . . . . 5-23 generic frame structure . . . . . . . . . . . . 5-17
part overview . . . . . . . . . . . . . . . . . . 5-4
application segmentation . . . . . . . . . . . . . . . . 5-44
mobile . . . . . . . . . . . . . . . . . . 2-32 structure of transmission . . . . . . . . . . . 5-7
PDH. . . . . . . . . . . . . . . . . . . . . . 4-22 PICH . . . . . . . . . . . . . . . . . . . . . 5-25
physical channels PRACH Message Part
downlink dedicated . . . . . . . . . . . . . 5-33 structure . . . . . . . . . . . . . . . . . . . 5-31
uplink dedicated . . . . . . . . . . . . . . . 5-36 Processing gain . . . . . . . . . . . . . . . . 6-15
Physical Layer protocols
channel mapping . . . . . . . . . . . . . . . 5-15 network . . . . . . . . . . . . . . . . . . . 2-19
channels . . . . . . . . . . . . . . . . . . . 5-8 PSTN subscriber to MS
description of . . . . . . . . . . . . . . . . 5-2 overview . . . . . . . . . . . . . . . . . . 2-45
functional layering . . . . . . . . . . . . . . 2-16
Q
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
QoS . . . . . . . . . . . . . . . . . . . . . . 2-52 Quality of Service . . . . . . . . . . . . . . . 2-52
R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Radio Access Network (RAN). . . . . . . . . . 3-4 RNC (contd.)

Radio Network Controller. . . . . . . . . . . . 2-8 functions . . . . . . . . . . . . . . . . . . 3-10
Radio Resource Management (RRM) . . . . . . 3-20 subsystems . . . . . . . . . . . . . . . . . 3-15
functional layering . . . . . . . . . . . . . . 2-17 user features . . . . . . . . . . . . . . . . . 3-19
RAKE receiver . . . . . . . . . . . . . . . . . 6-23 RNC5000
RAN . . . . . . . . . . . . . . . . . . . . . 3-4 overview . . . . . . . . . . . . . . . . . . 8-11
layout . . . . . . . . . . . . . . . . . . . . 3-4 RNL. . . . . . . . . . . . . . . . . . . . . . 7-12
RANAP . . . . . . . . . . . . . . . . . . . . 2-19 user plane channel procedures. . . . . . . . . 7-39
Random Access Transmission . . . . . . . . . . 5-28 RNS
Rate match. . . . . . . . . . . . . . . . . . . 5-42 functionality . . . . . . . . . . . . . . . . . 3-8
RNC . . . . . . . . . . . . . . . . . . . . . 3-6 RNSAP . . . . . . . . . . . . . . . . . 2-19, 7-37
cabinet . . . . . . . . . . . . . . . . . . . 3-13 RRC
configuration and capacity . . . . . . . . . . 3-12 connection procedures . . . . . . . . . . . . 7-75
description. . . . . . . . . . . . . . . . . . 3-10 RRM . . . . . . . . . . . . . . . . . . . . . 3-20
68P02905W21-B IX-5
02-Jun-2004
Index
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
S-CCPCH . . . . . . . . . . . . . . . . . . . 5-26 SIM . . . . . . . . . . . . . . . . . . . . . . 3-28

SCCP . . . . . . . . . . . . . . . . . . . . . 2-22 smart card . . . . . . . . . . . . . . . . . . . 3-28
SCH . . . . . . . . . . . . . . . . . . . . . . 5-19 SMS. . . . . . . . . . . . . . . . . . . . . . 2-33
SDH. . . . . . . . . . . . . . . . . . . . . . 4-23 point-to-point . . . . . . . . . . . . . . . . 3-19
security procedures subscriber identity
overview . . . . . . . . . . . . . . . . . . 2-34 mobile
SGSNu . . . . . . . . . . . . . . . . . . . . 2-11 international. . . . . . . . . . . . . . . . 3-28
Short Message Service (SMS) ISDN . . . . . . . . . . . . . . . . . . . 3-28
overview . . . . . . . . . . . . . . . . . . 2-33 temporary . . . . . . . . . . . . . . . . . 3-28
signalling system 7 . . . . . . . . . . . . 2-21, 2-32 Subscriber Information Module (SIM) . . . . . . 3-28
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
T1 link TMSI . . . . . . . . . . . . . . . . . . . . . 3-28

definition . . . . . . . . . . . . . . . . . . 2-23 TNL . . . . . . . . . . . . . . . . . . . . . . 7-10
TDMA . . . . . . . . . . . . . . . . . . . . 6-5 Transport channel
Temporary Mobile Subscriber Identity (TMSI) . . 3-28 multiplexing . . . . . . . . . . . . . . . . . 5-44
terrestrial interfaces Transport Layer
overview . . . . . . . . . . . . . . . . . . 4-3 functional layering . . . . . . . . . . . . . . 2-16
U
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
UMTS USR1.0 (contd.)

frequencies . . . . . . . . . . . . . . . . . 2-27 Node B hardware support features. . . . . . . 9-48
glossary . . . . . . . . . . . . . . . . . . . 11-2 OMC-U features . . . . . . . . . . . . . . . 10-4
handovers . . . . . . . . . . . . . . . . . . 9-40 CM features . . . . . . . . . . . . . . . 10-17
interfaces . . . . . . . . . . . . . . . . . . 7-2 FM features . . . . . . . . . . . . . . . 10-13
network overview . . . . . . . . . . . . . . 2-5 general application features. . . . . . . . 10-27
OMCs. . . . . . . . . . . . . . . . . . . . 3-29 interface features . . . . . . . . . . . . 10-23
system overview . . . . . . . . . . . . . . . 2-5 Load Management features . . . . . . . . 10-20
Uplink optional features . . . . . . . . . . . . . 10-29
flow process . . . . . . . . . . . . . . . . . 5-48 platform features . . . . . . . . . . . . 10-10
Uplink dedicated physical channels . . . . . . . 5-36 PM features . . . . . . . . . . . . . . . 10-22
Uplink spreading Security Management features . . . . . . 10-25
and channel combination . . . . . . . . . . . 5-50 optional features . . . . . . . . . . . . . . . 9-46
User Equipment . . . . . . . . . . . . . . 2-8, 3-25 overload control features . . . . . . . . . . . 9-66
capability . . . . . . . . . . . . . . . . . . 3-21 power control features . . . . . . . . . . . . 9-37
USR1.0 radio connection, admission and RM function
ATM backbone support features. . . . . . . . 9-14 features . . . . . . . . . . . . . . . . . . . 9-27
call trace feature . . . . . . . . . . . . . . . 9-65 Radio Resource Management features . . . . . 9-52
features . . . . . . . . . . . . . . . . . . . 9-2 signalling and terrestrial interface features . . . 9-12
general support of RRM functions features. . . 9-29 SMS point to point feature . . . . . . . . . . 9-61
handover features . . . . . . . . . . . . . . 9-40 UMTS Air Interface features . . . . . . . . . 9-21
initial base load features . . . . . . . . . . . 9-3 UTRAN . . . . . . . . . . . . . . . . . . 2-8, 3-3
Inter-RAT handover features . . . . . . . . . 9-58 hardware components . . . . . . . . . . . . 8-2
Iu, Iur and Iub interface features. . . . . . . . 9-18 network protocols . . . . . . . . . . . . . . 2-19
LBS feature . . . . . . . . . . . . . . . . . 9-63 overview . . . . . . . . . . . . . . . . . . 2-8
Node B configuration features . . . . . . . . 9-9
IX-6 68P02905W21-B
02-Jun-2004
Uu interface . . . . . . . . . . . . . . . . . . 7-66 Uu interface (contd.)

BMC layer . . . . . . . . . . . . . . . . . 7-72 RLC layer
MAC layer . . . . . . . . . . . . . . . . . 7-70 Acknowledged Mode (AM) . . . . . . . . 7-70
NAS layer . . . . . . . . . . . . . . . . . . 7-74 Transparent Mode (TM) . . . . . . . . . . 7-70
PDCP layer . . . . . . . . . . . . . . . . . 7-71 Unacknowledged Mode (UM) . . . . . . . 7-70
Functions . . . . . . . . . . . . . . . . . 7-71 RRC layer . . . . . . . . . . . . . . . . . . 7-72
protocol structure . . . . . . . . . . . . . . 7-67 Functions . . . . . . . . . . . . . . . . . 7-72
Protocol structure . . . . . . . . . . . . . . 7-67
V
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Visited Location Register (VLR) VLR. . . . . . . . . . . . . . . . 2-12, 2-40, 3-28

overview . . . . . . . . . . . . . . . . . . 2-40
W
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
W-CDMA
overview . . . . . . . . . . . . . . . . . . 2-24
X
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25. . . . . . . . . . . . . . . . . . . . . . 3-29
68P02905W21-B IX-7
02-Jun-2004

Umts Overview

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Umts Overview

Diunggah oleh

Hak Cipta:

Format Tersedia

System Information: UMTS Overview

© 2002 -2004 Motorola, Inc. 68P02905W21-B

System Information: UMTS Overview

Chapter 1: Introduction to this manual and Motorola documentation

Chapter 2: Overview of UMTS

What is UMTS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Mobile services Switching Centre for UMTS (MSCu) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Chapter 3: Functional description of UTRAN components

Typical RNS layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Chapter 4: Data flow and terrestrial interfaces for UMTS

Introduction to terrestrial interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Chapter 5: Air Interface Physical Layer

Chapter 6: W-CDMA theory

Chapter 7: Transmission systems

Iub DCH data stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Iur interface network layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Introduction to Iu-CS and Iu-PS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58

Chapter 8: Cabinet description

Chapter 9: UTRAN features in USR 1.0

Iu-CS signalling by SS7 (23054) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

RNC Soft handovers (23099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42

Chapter 10: OMC-U and its USR 1.0 features

Topics covered in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Chapter 11: Glossary of abbreviations

This page intentionally left blank.

Figure 4-14: PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Figure 7-8: FACH data transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41

This page intentionally left blank.

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

This page intentionally left blank.

System Information: UMTS Overview

Issue status of this manual

Table 1 Manual version history

Resolution of service requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

Failure to comply with Motorola’s operation, installation and maintenance

The tags have the format: {nnnn} or {nnnnn}

The tags are positioned in text as follows:

New and amended feature information Tag position in text

• Full sections under a main heading • Main heading

• Full paragraphs under subheadings • Subheading

Special key sequences

CTRL-c Press the Control and c keys at the same time.

Reporting safety issues

Whenever a safety issue arises:

Procedure 1 Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

Warnings and cautions

A definition and example follow below:

Example and format

Failure to comply with warnings

A definition and example follow below:

Example and format

• Potentially hazardous voltage.

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.

High RF potentials and electromagnetic fields are present in this equipment

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields

When dismantling heavy assemblies, or removing or replacing equipment, a

Do not install substitute parts or perform any unauthorized modification of

Do not wear earth straps when working with stand-by battery

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

Motorola equipment contains CMOS devices. These metal oxide semiconductor