CP13 Motorola UMTS

CHAPTER 2
NETWORK ARCHITECTURE
CHAPTER 3
NETWORK SERVICES
CHAPTER 4
UMTS PROTOCOLS
CHAPTER 5
DATA FLOW AND
TERRESTRIAL INTERFACES
CHAPTER 1
INTRODUCTION
CHAPTER 7
THE PHYSICAL LAYER
CHAPTER 8
RRM FUNCTIONS
ANNEXE A GLOSSARY CHAPTER 6
W-CDMA THEORY
TRAINING MANUAL
CP13
UMTS OVERVIEW
FOR TRAINING PURPOSES ONLY
THIS MANUAL WILL NOT BE UPDATED
VERSION1 REV 7
T
R
A
I
N
I
N
G

M
A
N
U
A
L
CP13
FOR TRAINING
PURPOSES ONLY

THIS MANUAL
WILL NOT BE
UPDATED
V
E
R
S
I
O
N
1

R
E
V

7
U
M
T
S

O
V
E
R
V
I
E
W
EMOTOROLA LTD. 2003
CP13: UMTS Overview
i
GSM
CP13
UMTS Overview
E Motorola 2002
All Rights Reserved
Printed in the UK.
Version 1 Rev 7
EMOTOROLA LTD. 2003 CP13: UMTS Overview
ii
Copyrights, notices and trademarks
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
and MOTOROLA 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.
.
.
.
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
iii
Contents
General information 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting safety issues 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings and cautions 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General warnings 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General cautions 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Devices sensitive to static 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1
Introduction 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Services 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMT-2000 Roadmap 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMT-2000 Objectives 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Research and Proposal 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proposals 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standardisation (1998) 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Harmonisation (1999) 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CDMA-2000 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-carrier 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct-Sequence (DS) 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Permitted Carrier Combinations 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cdma2000 Evolution 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Terrestrial Radio Access (UTRA) 118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FDD Mode 118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRA TDD Mode 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
World-wide Spectrum Allocation for IMT-2000 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WARC 92 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WARC 2000 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
European Frequency Allocations 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licence Allocation in the UK 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Network Architecture 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Domains 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Architecture Release 1999 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Core Network (CN) Entities 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Access Network (AN) Entities 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Mobile Station (MS) 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Network Release 1999 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entities of the CN-CS Domain 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entities Common to the CS and PS Domains 212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of GSN3/USP1 architecture 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components of the GSN Complex 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
iv
Packet switch core network components 216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola CSGSN 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSGSN Functionality 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GGSN 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GGSN functionality 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola Charging Gateway (CGW) 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charging Gateway functionality 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Hub 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CommHub functionality 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DNS/NTP Server 226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DNS/NTP Server functionality 226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Backbone 228 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Border Gateway 230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firewall 230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Nodes 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Home Location Register (HLR) / Authentication Centre (AuC) 232 . . . . . . . . . . . . . . .
Mobile Switching Centre (MSC) / Visitor Location Register (VLR) 232 . . . . . . . . . . . .
SMS Gateway MSC (SMSGMSC) / SMS Interworking MSC (SMSIWMSC) 232
CAMEL GSM SCF / PSCP 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Identity Register (EIR) 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nodes for value added services 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lawful Intercept Administrative Node (LIAN) 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Mobile Location Centre (GMLC) 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS/UMTS Interfaces 236 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Terrestrial Radio Access Network (UTRAN) 238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRAN Functions 238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio network Controller (RNC) 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling Radio Network Controller (CRNC) 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serving Radio Network Controller (SRNC) 242 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drift Radio Network Controller (DRNC) 244 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node B 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Wideband Digital Modem (WDM) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Wideband Transceiver (WBX) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linear Power Amplifier (LPA) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Equipment (UE) 248 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to User Equipment 248 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE Architecture 250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrated Circuit (IC) Card 250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Equipment (TE) 252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile Equipment (ME) 252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MT Functionality 254 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Evolution 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product evolution 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Servers 258 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
Network Services 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
v
Introduction to Network Services 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classification of Services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multimedia services: 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supplementary services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teleservices 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bearer Services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Capabilities 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of Services 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information Transfer 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic characteristics 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information Quality 310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Bit Rates 312 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of Service 314 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QoS Attributes 316 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Security Architecture 318 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security and Privacy 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User authentication: 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network authentication: 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Confidentiality 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data integrity 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile equipment identification 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication and Key Agreement 322 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribution of authentication data from HE to SN 322 . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication and Key Agreement 322 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering Algorithms 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F8 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F9 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generation of Authentication Vectors/Tokens 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQN and RAND 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication Key Management Field 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Algorithms f1 f5 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AUTN and AV 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USIM Authentication Function 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrieval of SQN 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computation of X-MAC 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verification of SQN 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computation of CK and IK 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Authentication Response 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Link Data Integrity 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data integrity protection method 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input parameters to the integrity algorithm 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering of User/Signalling Data 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input parameters to the cipher algorithm 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
UMTS Protocols 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to UMTS Protocols 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Stratum 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Non-Access Stratum 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
vi
General Protocol Model 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horizontal Layers 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vertical Planes 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IuCS Protocol Structure 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Plane Protocol Stack 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport Network Control Plane Protocol Stack 46 . . . . . . . . . . . . . . . . . . . . . . . . . .
User Plane Protocol Stack 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IuPS Protocol Structure 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Iub Protocol Structure 410 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Iur Protocol Structure 412 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Interface Protocol Architecture 414 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Layer Functions 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping between logical and Transport channels 416 . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport format selection 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Priority handling of Data Flows 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Scheduling 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identification of UEs on Common Channels 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MUX/DEMUX of PDUs into Transport Blocks 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic Volume Monitoring 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Transport Channel Type Switching 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Service Class Selection 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RLC Protocol 420 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC Functions 422 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol Stacks 426 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Plane Protocol Stack (Dedicated Channels CS-Domain) 426 . . . . . . . . . . . . . . .
Dedicated Channel Frame Protocol (DCH FP) 428 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Plane Protocol Stack (UE-CN SIGNALLING, Dedicated Channels, CS-Domain) . . . . . . .
430
RANAP Services 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCCP 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP3-B 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAAL-NNI 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Plane Protocol Stack (UE-CN Signalling, Shared Channels, CS-Domain) 432 . . . .
RACH/FACH/ DSCH Frame Protocol 432 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Plane Protocol Stack (Dedicated Channels, PS-Domain) 434 . . . . . . . . . . . . . . . . . . . .
GPRS Tunnelling Protocol, User Plane (GTP-U) 434 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path Protocols 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Plane Protocol Stack
(UE-CN Signalling, Dedicated Channels, PS-Domain) 436 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stream Control Transmission Protocol 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M3UA 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
vii
Chapter 5
Data Flow and Terrestrial Interfaces 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terrestrial Interfaces 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Principles 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Asynchronous Transfer Mode (ATM) 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Channels and Paths 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of Virtual Channels and Paths 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Connection and Path Switching 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layers (AALs) 512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The ATM Adaptation Process 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convergence Sub-Layer (CS) 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Segmentation and Reassembly 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layer 2 (AAL2) 516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCS 516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layer 5 (AAL 5) 518 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 Architecture 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Links 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Cell to E1 Cell Mapping 522 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E Link Multiplexing 524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inverse Multiplexing for ATM (IMA) 526 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronous Digital Hierarchy (SDH) 528 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDH Drop and Insert 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Simplification 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Survivability 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Control 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bandwidth on Demand 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Principles of SDH 532 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM to STM Mapping - VC4 534 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical UMTS Transport Network 536 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6
W-CDMA Theory 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Access Schemes 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
W-CDMA Characteristics 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-Use of Frequency 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-Use of Codes 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spectral Efficiency (GSM and UMTS) 610 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct Spread (DS)-CDMA Implementation 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitter 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
viii
Spreading 614 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Orthogonal Codes 618 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channelisation Code Tree 620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
De-spreading Other Users Signals 622 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Gain 624 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise 1 - Spreading 626 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling 632 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling Codes vs Channelisaton Codes 634 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Short Codes vs Long Codes 636 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling and Summation 638 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
De-Scrambling and Data Recovery 640 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-path Radio Channels 642 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Matched Filter Operation 644 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The RAKE Receiver 646 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7
The Physical Layer 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Layer Services 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QPSK 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Locations 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channels on the Air Interface 710 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport Channels 714 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Channels 716 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Physical Channels (CPCHs) 716 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Mapping 718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical signals 718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generic Frame Structure 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Frame 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Frame 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslot 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronisation Channel (SCH) 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Primary SCH 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Secondary SCH 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modulation Symbol a 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
ix
Synchronisation (Cell Search) Procedure 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Slot synchronisation 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 2: Frame synchronisation and code-group identification 724 . . . . . . . . . . . . . . . .
Step 3: Scrambling-code identification 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronisation 725 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Pilot Channel (CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary Common Pilot Channel (P-CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Secondary Common Pilot Channel (S-CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modulation pattern for Common Pilot Channel 727 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P-CCPCH Frame Structure 728 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCH and P-CCPCH 730 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging Indicator Channel (PICH) 732 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PICH Channel Structure. 732 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discontinuous Reception (DRX) on the PICH 733 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Secondary Common Control Physical Channel (S-CCPCH) 736 . . . . . . . . . . . . . . . . . . . . . . .
Secondary CCPCH Fields 737 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pysical Random Access Channel (PRACH) 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the PRACH 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Random Access Transmission 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRACH Pre-amble 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the random-access transmission 739 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of PRACH Message Part 740 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Acquisition Indicator Channel AICH) 742 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AICH signature patterns 743 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Relationship Between PRACH and AICH 744 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Dedicated Physical Channels (DL-DPCH) 746 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DL-DPCH Structure 746 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Slot Formation in Case of Multi-Code Transmission 748 . . . . . . . . . . . . . . .
Uplink Dedicated Physical channels (UL-DPCH) 750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Random Access Procedure in Detail 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Random access parameters 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical random access procedure 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASC to Access Class Mapping 756 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH access slot sets 757 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH sub-channels 757 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH Access Slot Availability 762 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scaling Factor 768 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRACH/Access Service Class/ Sub channel/Signature Mapping 770 . . . . . . . . . . . . .
PCPCH (Physical Common Packet Channel) and Associated Physical Signals 772 . . . . . .
CPCH Status Indicator Channel (CSICH) 774 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCH transmission 776 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCH Access Preamble Acquisition Indicator Channel (APAICH) 778 . . . . . . . . . .
CPCH Collision Detection/Channel Assignment Indicator Channel (CD/CAICH) . . . . . . .
780
Physical Common Packet Channel (PCPCH) 784 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DLDPCCH for CPCH 786 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Flow Process 788 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Flow Process 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Frame Equalisation 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rate Matching 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTX 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
x
Chapter 8
Radio Resource Management Functions 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Resource Management 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE RRC States 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Idle Mode 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connected Mode 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Layer Measurements 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE Measurements 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRA Measurements 810 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compressed Mode 812 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Selection/Re-selection 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Immediate Cell Evaluation 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Re-selection 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Macro Diversity 816 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Strategy 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Causes 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Soft and Softer Handover 820 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
S-RNS Relocation 822 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Control 824 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Selection Diversity Power Control (SSDT) 824 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open Loop Power Control 826 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Power Control (Inner Loop) 828 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Power Control (Outer Loop) 830 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Cell Power Control 832 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Select Diversity Transmission 834 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Space Time Transmit Diversity (STTD) 836 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Mode Transmit diversity 838 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Admission Control 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of Service (QoS) 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Load 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Control 842 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 9
Annexe A A91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives A91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging for a UE in Idle Mode A92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging for the UE in RRC Connected Mode A94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC Connection Establishment A96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC DCH Release A98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RA Update A910 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRNC Relocation A912 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
xi
Glossary of technical terms and abbreviations G-1 . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
xii
Version 1 Rev 7 General information
EMOTOROLA LTD. 2003
CP13: UMTS Overview
1
General information
Important notice
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.
WARNING Failure to comply with Motorolas 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.
ETSI standards
The standards in the table below able are protected by copyright and are the property of
the European Telecommunications Standards Institue (ETSI).
ETSI specification number
GSM 02.60 GSM 04.10 GSM 08.08
GSM 03.60 GSM 04.11 GSM 08.16
GSM 03.64 GSM 04.12 GSM 08.18
GSM 04.01 GSM 04.13 GSM 08.51
GSM 04.02 GSM 04.60 GSM 08.52
GSM 04.03 GSM 04.64 GSM 08.54
GSM 04.04 GSM 04.65 GSM 08.56
GSM 04.05 GSM 08.01 GSM 08.58
GSM 04.06 GSM 08.02 GSM 09.18
GSM 04.07 GSM 08.04 GSM 09.60
GSM 04.08 GSM 08.06
Figures from the above cited technical specifications standards are used, in this training
manual, with the permission of ETSI. Further use, modification, or redistribution is strictly
prohibited. ETSI standards are available from http://pda.etsi.org/pda/ and
http://etsi.org/eds/
Version 1 Rev 7 General information
2
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.
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold 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.
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:
CTRLc Press the Control and c keys at the same time.
ALTf Press the Alt and f keys at the same time.
| Press the pipe symbol key.
CR or RETURN Press the Return key.
Version 1 Rev 7 Reporting safety issues
EMOTOROLA LTD. 2003
CP13: UMTS Overview
3
Reporting safety issues
Introduction
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:
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 68437733 (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.
Version 1 Rev 7 Warnings and cautions
4
Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of this Motorola manual set.
Warnings
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
WARNING 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 customers failure to comply
with these requirements.
Cautions
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
CAUTION Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.
Version 1 Rev 7 General warnings
EMOTOROLA LTD. 2003
CP13: UMTS Overview
5
General warnings
Introduction
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
S Potentially hazardous voltage
S Electric shock
S RF radiation
S Laser radiation
S Heavy equipment
S Parts substitution
S Battery supplies
S 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 customers 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.
6
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.
Potentially hazardous voltage
WARNING This equipment operates from a hazardous voltage of 230 V
ac single phase or 415 V ac three phase supply. To achieve
isolation of the equipment from the ac supply, the ac 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.
NOTE Motorola GSM equipment does not utilise high voltages.
Electric shock
WARNING 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
WARNING 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.
Relevant standards (USA and EC), to which regard should be paid when working with RF
equipment are:
S 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.
S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10 kHz to 300 GHz).
EMOTOROLA LTD. 2003
CP13: UMTS Overview
7
Laser radiation
WARNING 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
WARNING 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 equipments have 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
WARNING 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.
Battery supplies
WARNING Do not wear earth straps when working with standby battery
supplies.
Lithium batteries
WARNING 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.
Version 1 Rev 7 General cautions
8
General cautions
Introduction
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 customers 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
CAUTION Fibre optic cables must not be bent in a radius of less than
30 mm.
Static discharge
CAUTION 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.
Version 1 Rev 7 Devices sensitive to static
EMOTOROLA LTD. 2003
CP13: UMTS Overview
9
Devices sensitive to static
Introduction
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 shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted 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:
S Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
S 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.
S Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
S 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.
S All metal tools should be used and when not in use they should be placed on an
earthed surface.
S 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.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
11
Chapter 1
Introduction
Version 1 Rev 7
12
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
13
Chapter 1
Introduction 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Services 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMT-2000 Roadmap 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMT-2000 Objectives 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Research and Proposal 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proposals 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standardisation (1998) 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Harmonisation (1999) 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CDMA-2000 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-carrier 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct-Sequence (DS) 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Permitted Carrier Combinations 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cdma2000 Evolution 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Terrestrial Radio Access (UTRA) 118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FDD Mode 118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRA TDD Mode 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
World-wide Spectrum Allocation for IMT-2000 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WARC 92 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WARC 2000 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
European Frequency Allocations 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licence Allocation in the UK 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
14
Version 1 Rev 7 Objectives
EMOTOROLA LTD. 2003
CP13: UMTS Overview
11
Objectives
On completion of this chapter the student should be able to:
S State the services UMTS aims to provide.
S State the IMT-2000 objectives
S Describe the evolution of UMTS from 2G systems.
S Describe the UMTS operating modes.
S State the frequency allocations for UMTS.
Version 1 Rev 7 UMTS Services
12
UMTS Services
UMTS is expected to deliver voice, graphics, video and other broadband information
direct to the user, regardless of location, network or terminal. These fully personal
communication services will 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 (e.g. in areas with low population density), and in private/corporate markets,
ranging from home use to wireless PBXs, emergency and cordless systems.
Version 1 Rev 7 UMTS Services
EMOTOROLA LTD. 2003
CP13: UMTS Overview
13
UMTS Services
CP13_Ch1_02
Voice
Graphics
Internet
Conferencing
Video
Text
Version 1 Rev 7 IMT-2000 Roadmap

14
IMT-2000 Roadmap
The diagram opposite points out the possible routes to 3G. On one extreme we see the
route taken by 3GPP culminating in the adoption of W-CDMA. Centre stage we see the
route chosen by the UWC 136 supporters. UWC 136 will be built on TDMA technology by
enhancing its modulation techniques to meet ITUs requirements for IMT2000. Far right
we see the route chosen for 3GPP2 which has its origins in the IS95 standards known as
CDMAOne culminating in CDMA 2000.
The three different systems are:
1. UMTS W-CDMA
2. UWC-136
3. CDMA2000
Which have been designed by three separate organisations;
1. 3GPP
2. UWCC
3. 3GPP2
GSM Global Systems for Mobile Communication
ETSI European telecommunication Standard
Institute
GPRS General Packet Radio Service
EDGE Enhanced Data rates for Global Evolution
UWCC Universal Wireless Communication
Committee
TIA Telecommunication Industry Association
3GPP Third Generation Partnership Project
UWC Universal Wireless Communications
3GPP2 Third Generation Partnership Project 2
Version 1 Rev 7 IMT-2000 Roadmap
EMOTOROLA LTD. 2003
CP13: UMTS Overview
15
IMT-2000 Roadmap
GSM
TDMA
(IS 136)
IS95A
CP13_Ch1_05
GPRS
EDGE
IS95B
WCDMA
3GPP
UWC136
UWCC
cdma2000
3GPP2
CDG
TIA
UWCC
T1
GSM
Association
ETSI
3G
2.5G
2G
Version 1 Rev 7 IMT-2000 Objectives
16
IMT-2000 Objectives
The objectives of IMT-2000 are to encourage global service provision and convergence
of the many, essentially competing, wired and wireless access technologies currently in
use. IMT-2000 aims to be a global standard that provides the flexibility required by
existing operators to seamlessly evolve there networks towards the needs their
subscribers in the future. In doing IMT-2000 is expected to reduce the
telecommunications gap, by offering cost effective access to telecommunications
facilities to the billions of people who do not currently have a phone.
IMT-2000 incorporates many current radio access technologies, including both terrestrial
and satellite components. Fixed and mobile access, on both public and private networks
Will offer a much wider range of services and types of terminals than any of the
preceding radio access technologies.
Version 1 Rev 7 IMT-2000 Objectives
EMOTOROLA LTD. 2003
CP13: UMTS Overview
17
IMT-2000 Objectives
CP13_Ch1_06
Global service capabilities
Terrestrial and satellite components
Flexible/seamless service
Wider range of services/terminals
Fixed/Mobile and Public/Private
Improved operational efficiencies
Reduce the Telecommunications gap
Version 1 Rev 7 Research and Proposal

18
Research and Proposal
Having laid down the basic framework of requirements, the ITU invited research activities
to identify a suitable radio access scheme to fulfil the IMT-2000 aims and objectives.
Most of this research activity was undertaken in by standards development organisations
and industry in Europe, The United States, Japan and Korea. Many different radio
access technologies (both terrestrial and satellite), and multiple access methodologies
were considered, with the majority being based upon Code Division Multiple Access
(CDMA) and Time Division Multiple Access (TDMA).
Proposals
At the June 1998 deadline, ITU had received a total of 16-proposals, all of which would
meet or exceed the basic aims and objectives of IMT-2000. The proposals included 10
terrestrial and six satellite based radio access technologies. Of the terrestrial options,
only 2 were TDMA based, with the remainder proposing CDMA; either narrow band,
wideband or multi-carrier
The main European contender was Universal Terrestrial Radio Access (UTRA), although
now generally accepted as translating to UMTS terrestrial radio Access. UTRA
proposed a wide band, Direct Spread CDMA (DS-CDMA) and includes a combination
CDMA/TDMA mode. UTRA was designed to be backward compatible with existing GSM
Mobile Application Part (MAP) core network.
Another dominant proposal was also based on DS-CDMA, but called for the use of
multiple narrow band carriers in the down link and is hence referred to as Multi Carrier
CDMA (MC-CDMA). The MC schema make the re-use of existing IS-95 and PCS
frequencies for 3G more feasible. This, along with the fact that a ANSI-41 core was
specified, make the proposal more attractive to current IS-95 operators in the US and
Asia.
Version 1 Rev 7 Research and Proposal
EMOTOROLA LTD. 2003
CP13: UMTS Overview
19
Research and Proposal
CP13_Ch1_06a
Europe
WCDMA
WTDMA
TDMA/CDMA
OFDMA
ODMA
Japan
WCDMA
WTDMA
OFDMA
USA
WCDMAS N/A
WTDMA
MCCDMA
WIMS WCDMA
WPCDMA
Korea
WCDMA
(Asynch)
WCDMA
(Synch)
June 1998
10 Terrestrial
proposals to ITU
8 x CDMA
2 x TDMA
Version 1 Rev 7 Standardisation (1998)
110
Standardisation (1998)
At the close of the research and proposal phase in June 1998, ten suitable terrestrial
radio access technologies had been proposed. Each proposal naturally tended to favour
compatibility with the existing 2G systems in the proposing bodies region, and ITU
accepted this need for Flexible/Seamless migration. However, it became evident that
although many technical aspects of the proposals were similar, allowing each region to
independently define its own specifications would, in addition to being a waste of
resources, mean that equipment compatibility on a global basis would be very difficult to
achieve.
ITU therefore started initiatives to achieve further standardisation. From these initiatives
two forums were created, the Third Generation Partnership Project (3GPP) and 3GPP
3GPP
The standards development organisations involved in the creation of 3GPP were,
Association of Radio Industries and Businesses (ARIB) from Japan, the European
Telecommunications Standards Institute (ETSI), The Telecommunications Technology
Association (TTA) of Korea and T1P1 for the USA. The partners agreed to joint efforts
for the standardisation of W-CDMA based on the UTRA Proposal. Later during 1999,
The China Wireless Telecommunications Standards Group (CWTS) also joined 3GPP. As
well as the SDOs, manufacturers and operators also have membership of 3GPP, along
with industry interest groups such as the GSM association, UMTS forum, Global Mobile
Suppliers Association, Ipv6 Forum and the Universal Wireless Communications
Consortium (UWCC).
3GPP2
Work done by TIA and TTA was merged to form 3GPP2, focused on the development of
CDMA2000, a multi-carrier solution. This activity is running in parallel with the 3GPP
project, with participation from ARIB, TTC and CWTS as member organisations.
Version 1 Rev 7 Standardisation (1998)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
111
Standardisation
CP13_Ch1_06b
T1P1 TTA
ETSI
ARIB/
TTC
CWTS
3rd Generation
Partnership Project
(3GPP)
Standardisation for a
common WCDMA Specification
3rd Generation
Partnership Project 2
(3GPP2)
Standardisation for a common
MCCDMA Specification
TTA
TIA
Version 1 Rev 7 Harmonisation (1999)
112
Harmonisation (1999)
During the spring of 1999 several operators and manufacturers met to seek further
convergence of the CDMA based 3G solutions (UTRA W-CDMA and CDMA2000). As a
result of these meetings, the Operators Harmonisation Group (OHG) was founded and
agreed to adopt a Harmonised global 3G CDMA standard consisting of three modes:
1. A direct spread wide band CDMA, Known as UTRA Frequency Division Duplex
(FDD).
2. A wideband CDMA/TDMA option, known as UTRA Time Division Duplex (TDD).
3. A multi-carrier CDMA option, known as CDMA2000 (or 1X/3X).
The main technical impacts of the harmonisation activities were as follows:
1. The change of the UTRA FDD and TDD Chip rate from 4.096 Mcps to 3.84 Mcps.
2. The inclusion of a common pilot channel for UTRA FDD.
3. A requirement for ALL core networks to support all radio access technologies.
Version 1 Rev 7 Harmonisation (1999)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
113
Harmonisation
Manufacturers and Operators Agreed to Adopt a
Harmonised Global 3rd Generation Standard Consisting
of Three Modes:
S Multi carrier CDMA
S Direct Spread CDMA (UTRA FDD)
S Time Division Duplex (UTRA TDD)
Main Technical Impacts:
S All Core Networks To Support All Air I/F Alternatives
S Change of UTRA FDD & TDD Chip Rates from
4.096 Mcps to 3.84 Mcps
S Inclusion of a Common Pilot for UTRA FDD
CP13_Ch1_p13
Version 1 Rev 7 CDMA-2000
114
CDMA-2000
CDMA-2000, the 3G system promoted by 3GPP2, is based upon the IMT-2000 proposal
known as Multicarrier CDMA (MC-CDMA). 3GPP2 has specified an air interface system
that is backward compatible with existing IS-95 systems. This approach being necessary
because in North America, IS-95 networks already use the frequency spectrum allocated
for 3G. CDMA-2000 must therefore coexist with the older systems on the same radio
frequency bands.
For CDMA-2000, the carrier composition can be different in downlink and uplink (known
as Forward and Reverse links respectively for this system). Carrier composition is
determined by the Spreading Rate employed. Two Spreading Rates are currently
defined by 3GPP2.
S Spreading Rate 1 (SR1) - SR1 is often refered to as 1X. In this mode, both
forward and reverse links use a single, Direct-Sequence spread carrier, with a chip
rate of 1.2288 Mcps. Allowing for the required Guard Bands this requires a RF
carrier Bandwidth of 1.25 MHz.
S Spreading Rate 3 (SR3) - SR3 is often referred to as 3X. A SR3 Forward
CDMA Channel uses 3Direct-Sequence spread carriers (i.e. Multi-Carrier), each
with a chip rate of 1.2288 Mcps and a bandwidth of 1.25 Mhz. A SR3 Reverse
CDMA channel uses a single DirectSequence spread carrier with a chip rate of
3.6964 Mcps
Multi-carrier
In Multi-carrier configurations, multiple (up to 12) narrow band (1.25 MHz) carriers can be
used to provide a single composite forward radio link. Early deployments of CDMA-2000
will, as described above, utilise three such carriers and is referred to as 3X mode.
As these carriers have the same bandwidth as IS-95, they can be used in overlay mode
with IS-95. This is possible because CDMA-2000 spreading codes can be chosen to be
orthogonal with the code in IS-95, thus minimising inter-system interference. Close
timing synchronisation within and between different systems is also essential for this type
of operation.
Direct-Sequence (DS)
In the Direct-Sequence configuration, the whole available link bandwidth is allocated to
one direct spread narrow band (SR1) or wideband (SR3) carrier.
CDMA-2000 does not use time synchronisation on the uplink and therefore cannot use
codes that are orthogonal with IS-95. Thus, when using SR3, splitting the reverse link
carrier into several narrow band components, as with the forward Llnk, yields no benefits.
Permitted Carrier Combinations
S Foward Link - DS SR1. Reverse Link - DS SR1 (Currently Deployed as 1X)
S Forward Link - MC SR3. Reverse Link - DS SR1 (Future 3X Evolution Path)
S Forward Link - MC SR3. Reverse Link - DS SR3 (Future 3X Evolution Path)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
115
CDMA-2000 Modes
Direct Spread
Configuration
(SR1)
Direct Spread
Configuration
(SR3)
MultiCarrier
Configuration
(SR3)
116
cdma2000 Evolution
cdma2000 systems, based upon 3GPP2 Spreading Rate 1 standards, commonly known
as cdma200 1x are currently being deployed throughout North America and Asia.
These systems provide a packet data service, offering an average user data rate of 144
kb/s. In addition, when compared with IS-95 A/B, a 50% increase in voice capacity is
obtained. This system uses a single 1.25 Mhz bandwidth carrier pair and, is capable of
co-existing with IS-95 on the same radio spectrum.
However, cdma2000 1x alone, cannot provide the IMT-2000 objective of ISDN H12
channel equivalence, this being data services at 2.048 Mb/s. To obtain this rate, further
evolution is required. Three evolution options are available, as follows:
Spreading Rate 3 (SR3)
The original 3GPP2 specifications included standards for a SR3 service, commonly
referred to as cdma2000 3x. As previously described, this mode uses multiple narrow
(1.25 Mhz) band channels in the forward direction and, a single wideband (5 Mhz) Direct
Sequence carrier in the reverse direction, to achieve the require data bandwidth. The
requirements for large spectrum allocations and the inability to co-exist with IS-95
systems, makes this option the least attractive to operators.
cdma2000 1x Evolution - Data Only (1xEV-DO)
Technical innovations since the 3GPP2 specifications were originally drafted, have led to
a numbers of options being proposed to enhance the SR1 or cdma2000 1x system. The
first of these is known as 1xEV-DO. This system provides a standalone packet data
service, offering maximum data rates of 2450 kb/s, with a user data throughput of
600kb/s being a practical figure. A 1.25Mhz carrier pair is required to provide this
service. Concurrent voice services may be offered by the operator using IS-95 A/B or
cdma2000 1x, using separate radio spectrum allocations.
cdma2000 1x Evolution - Data and Voice (1xEV-DV)
By using sophisticated Modulation techniques, 1XEV-DV provides a method of
obtaining both voice and high speed data, including real time data services, using a
single 1.25 Mhz carrier pair. This system is 100% backward compatible with both
cdma2000 1X and IS-95 A/B systems.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
117
cdma2000 Evolution
IS95 A/B
Cdma2000 (1x)
Cdma2000 (3x)
cdma2000
(1xEVDO)
Cdma2000
(1xEVDV)
IS95 A/B
Cdma2000 (1x)
Cdma2000 (3x)
cdma2000
(1xEVDO)
Cdma2000
(1xEVDV)
CP13_Ch1_6g
Version 1 Rev 7 UMTS Terrestrial Radio Access (UTRA)
118
UMTS Terrestrial Radio Access (UTRA)
3GPP is the organisation that develops specifications for a 3G system based on the
UMTS Terrestrial Radio Access (UTRA) radio interface, which is primarily designed to
operate with an enhanced GSM core network. The UTRA system provides for two
operating modes, Frequency Division Duplex (FDD) and Time Division Duplex (TDD)
FDD Mode
In the FDD mode of operation, uplink and downlink transmissions use separate radio
carriers in different sub-bands of the IMT-2000 spectrum allocation. These paired radio
carriers must be separated by a minimum of 130 MHz. Each radio carrier is allocated a
bandwidth of 5 Mhz, in each direction.
The 5 MHz of bandwidth of each radio carrier is shared among multiple users. Individual
users are separated using Channelisation Codes, which give a unique signature to that
user. The exact code assigned to a user, determines how much of the shared bandwidth
resource that user is allocated.
The number of users that can be accommodated on a radio carrier is dependent upon
the resource requirements of those users. The higher the data rate of a user, the greater
the bandwidth required to transport that data, therefore the lower the number of users
that can be supported. The theoretical maximum number of users per carrier is 512, this
being limited by the number of available Channelisation Codes. In practice this figure will
be much lower.
Because separate uplink and downlink radio frequencies are used both network, and
user can transmit and receive simultaneously, allowing full duplex operation. However, in
addition to the transfer of user data the radio interface must support certain Layer 1
control procedures (e.g. power control). These procedures must be performed at regular
intervals, and to define these intervals a radio frame and timeslot structure is defined.
Each carrier is divided into 10 milli-second Radio Frames and each frame is further
divided into 15 timelsots.
It should be noted that unlike GSM, where Mobile Stations are allowed to transmit and
receive in set timeslots, UMTS User Equipments operating in FDD mode can transmit
and receive in every timeslot, during every radio frame.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
119
UTRA FDD Mode
CP13_Ch1_6e
10 ms
TS0 TS14
190 MHz
10 ms
TS0 TS14
10 ms
TS0 TS14
190 MHz
10 ms
TS0 TS14
120
UTRA TDD Mode
The TDD UTRA mode differs from the FDD mode in that both uplink and downlink
transmissions use the same 5 MHz bandwidth carrier, providing a service without the
requirement for paired radio carriers. Future allocations of radio spectrum to UMTS
may not permit the use of paired bands as radio spectrum becomes a more scarce
commodity. Since uplink and downlink share the same frequency, the links must be
segregated using the time domain
The physical structure of the TDD radio interface is similar to that of UTRA FDD, in that a
10 ms frame, divided into 15 timeslots is used. The 15 timeslots can be dynamically
allocated between uplink and downlink directions, thus the capacity of the links can be
different. This capability makes TDD well suited to asymmetric services.
With such a flexibility, the TDD mode can be adapted to different configurations of
uplink/downlink timeslot usage. However, in any configuration at least one timeslot has
to be allocated for the uplink and at least one time slot allocated for the uplink. In either
direction, A given user may be allocated resources within a single timeslot or multiple
timeslots.
Within each timeslot, the data part of each physical channel is defined using a unique
channelisation code. In the downlink, 16 codes are used per time slot. Multiple parallel
physical channels can be used to support higher data rates for a single user. The 16
codes in each timeslot may be also be shared by multiple users.
In the uplink direction either 1, 2, 4 8, or 16 codes may be used, with each code again
defining an individual physical channel. A User may use a maximum of two physical
channels per timeslot simultaneously. The larger the number of codes that are used, the
lower will be the data rate supported by each code.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
121
UTRA TDD Mode
10 ms
10 ms
10 ms
10 ms
OR
OR
OR
(Examples Only)
10 ms
10 ms
10 ms
10 ms
OR
OR
OR
10 ms
10 ms
10 ms
10 ms
OR
OR
OR
(Examples Only)
CP13_Ch1_6f
Version 1 Rev 7 World-wide Spectrum Allocation for IMT-2000
122
World-wide Spectrum Allocation for IMT-2000
WARC 92
The allocation of frequencies per region after the World Administration Radio Conference
(WARC 92) meeting has been varied. IMT-2000 recognised the frequencies to be
1885Mhz to 2025Mhz in the lower and 2110Mhz to 2200Mhz in the upper band. Each
band has been sub-divided into Mobile Satellite Service (MSS) and Terrestrial IMT-2000
parts.
Not all countries are able to utilise the full ITU spectrum allocation as existing services
have already been allocated frequencies in these bands. Therefore there are some
regional variations, as can bee seen from the diagram opposite.
S Europe has used part of the band for DECT - which has very low penetration. It
also has GSM 1800 at the lower edge. The band is also split in FDD and TDD
bands.
S China has left the band clear and will start IMT-2000 activities soon. This will be
split into WLL and Mobile.
S Japan has developed with Korea the DoCoMo system which is pre release 99 and
will launch Q4 2000/Q1 2001.
S In North America most of the IMT-2000 spectrum has already been allocated to
second-generation PCS networks, deployed on 5-MHz sub-bands. This makes
CDMA-2000 and EDGE the most attractive option to operators in this region, as
these systems are backward compatible with IS-95B and IS-136, and can co-exist
in the same spectrum
WARC 2000
More recently the WARC 2000 meeting, held in Istanbul, has allocated a further 519 MHz
of radio spectrum for 3G services. Again not all regions will be able to make full use of
this spectrum.
The frequency bands added are:
806 MHz - 960 MHz
1710 MHz - 1885 MHz
2500 MHz - 2690 MHz
Version 1 Rev 7 World-wide Spectrum Allocation for IMT-2000
EMOTOROLA LTD. 2003
CP13: UMTS Overview
123
World-wide Spectrum Allocation for IMT-2000
A D B F E C A D B F E C
CP13_Ch1_07
ITU Allocations
Europe
China
Japan
Korea (w/o PHS)
North
America
1850 1900 1950 2000 2050 2100 2150 2200 2250 Mhz
MSS =
Mobile Satellite
Services
MDS =
Multipoint Service/
Mobile Data Service
1850 1900 1950 2000 2050 2100 2150 2200 2250 Mhz
IMT 2000 MSS
1885 1900 1980 2010 2025
UMTS MSS
1880
IMT 2000 MSS
WLL WLL
GSM
1800
DECT
GSM
1800
IMT 2000 MSS
1893 1919
PHS
MSS
PCS
1990
IMT 2000 MSS
2110 2170 2200
UMTS MSS
IMT 2000 MSS
IMT 2000 MSS
MSS
M
D
S
Reserve
2160
Version 1 Rev 7 European Frequency Allocations
124
European Frequency Allocations
When studying the frequency allocation for Europe more closely we can see the
following.
It is split into two frequency bands:
S Lower 1900MHz - 2025MHz
S Upper 2110MHz - 2200MHz
Owing to the asymmetric nature of the frequency allocation, frequencies have been
allocated into paired and unpaired bands.
The frequency range 1920 - 1980 MHz and 2110 - 2170 MHz are available to operators
as paired bands, these support UTRA Frequency Division Duplex (FDD) and are best
suited to symmetric services such as telephony. A minimum frequency separation of
130MHz has been specified between transmit and receive frequencies.
In the lower band, 1900 - 1920 MHz and 2010 - 2025MHz are available as unpaired
bands. These can support UTRA Time Division Duplex (TDD), which is best suited to
asymmetrical services such as the Internet.
Version 1 Rev 7 European Frequency Allocations
EMOTOROLA LTD. 2003
CP13: UMTS Overview
125
European Frequency Allocations
CP13_Ch1_08
GSM
1800
DECT
T
D
D
Uplink 12 x 5 MHz
1
8
0
5
1
9
2
0
1
9
8
0
2
0
1
0
2
0
2
0
2
0
2
5
1
9
0
0
1
8
8
0
S
P
A
M
S
S
F
D
D
T
D
D
20MHz 60MHz 30MHz
M
S
S
F
D
D
2
2
0
0
2
1
1
0
2
1
7
0
Downlink 12 x 5 MHz 6 x 5 MHz
140MHz
190MHz between up
link and downlink
60MHz 30MHz
90MHz
Version 1 Rev 7 Licence Allocation in the UK
126
Licence Allocation in the UK
In the UK the spectrum was divided into five licenses. The four incumbent operators were
successful in obtaining a license each, which left one for a new entrant. License A, which
is considered as the most desirable spectral package, was set aside for this new entrant.
A - Hutchison 3G
B - Vodaphone
C - One2One
D - BT Cellnet
E - Orange
Some of the issues that should be considered in the frequency allocations are:
S Guard bands provide a reduced noise floor
S Lower frequencies travel further, I.e. less cells
S Three frequencies allows greater use of multimedia services
S Trade-offs between FDD and TDD spectrum
EMOTOROLA LTD. 2003
CP13: UMTS Overview
127
Licence Allocation in the UK
CP13_Ch1_09
D E C A
Unpaired carriers
1900 MHz 1920 MHz
1902.4 MHz
1922.8 MHz
0.4 MHz
guard band
14.6 MHz
Licence A
10.0 MHz
Licence C
14.8 MHz
Licence B
10.0 MHz
Licence E
10.0 MHz
Licence D
1980 MHz
0.3 MHz
guard band
1977.2 MHz
2110 MHz
2112.8 MHz
14.6 MHz
Licence A
10.0 MHz
Licence C
14.8 MHz
Licence B
10.0 MHz
Licence E
10.0 MHz
Licence D
2170 MHz
0.3 MHz
guard band
2167.2 MHz
0.3 MHz
guard band
128
EMOTOROLA LTD. 2003
CP13: UMTS Overview
21
Chapter 2
Network Architecture
Version 1 Rev 7
22
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
23
Chapter 2
Network Architecture 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Domains 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Architecture Release 1999 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Core Network (CN) Entities 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Access Network (AN) Entities 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Mobile Station (MS) 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Network Release 1999 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entities of the CN-CS Domain 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entities Common to the CS and PS Domains 212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of GSN3/USP1 architecture 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components of the GSN Complex 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packet switch core network components 216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola CSGSN 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSGSN Functionality 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GGSN 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GGSN functionality 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola Charging Gateway (CGW) 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charging Gateway functionality 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Hub 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CommHub functionality 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DNS/NTP Server 226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DNS/NTP Server functionality 226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Backbone 228 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Border Gateway 230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firewall 230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Nodes 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Home Location Register (HLR) / Authentication Centre (AuC) 232 . . . . . . . . . . . . . . .
Mobile Switching Centre (MSC) / Visitor Location Register (VLR) 232 . . . . . . . . . . . .
SMS Gateway MSC (SMSGMSC) / SMS Interworking MSC (SMSIWMSC) 232
CAMEL GSM SCF / PSCP 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Identity Register (EIR) 232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nodes for value added services 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lawful Intercept Administrative Node (LIAN) 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Mobile Location Centre (GMLC) 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS/UMTS Interfaces 236 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UMTS Terrestrial Radio Access Network (UTRAN) 238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRAN Functions 238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio network Controller (RNC) 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling Radio Network Controller (CRNC) 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serving Radio Network Controller (SRNC) 242 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drift Radio Network Controller (DRNC) 244 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node B 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Wideband Digital Modem (WDM) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Wideband Transceiver (WBX) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linear Power Amplifier (LPA) 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
24
User Equipment (UE) 248 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to User Equipment 248 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE Architecture 250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrated Circuit (IC) Card 250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Equipment (TE) 252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile Equipment (ME) 252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MT Functionality 254 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Evolution 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product evolution 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Servers 258 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2003
CP13: UMTS Overview
21
Objectives
S Name and state the purpose of the UMTS Domains
S Describe the architecture of a UMTS network.
S Describe the purpose of the major network components.
S Describe the options for evolution to future releases.
Version 1 Rev 7 UMTS Domains
22
UMTS Domains
Domain split
A basic architectural split is between the user equipment (terminals) and the
infrastructure. This results in two domains: the User Equipment Domain and the
Infrastructure domain. User equipment is the equipment used by the user to access
UMTS services. User equipment has a radio interface to the infrastructure. The
infrastructure consists of the physical nodes which perform the various functions required
to terminate the radio interface and to support the telecommunication services
requirements of the users. The infrastructure is a shared resource that provides services
to all authorised end users within its coverage area. The reference point between the
user equipment domain and the infrastructure domain is termed the Uu reference point
(UMTS radio interface).
User equipment Domain
This domain encompasses a variety of equipment types with different levels of
functionality. These equipment types are referred to as user equipment (terminals), and
they may also be compatible with one or more existing access (fixed or radio) interfaces
e.g. dual mode UMTS-GSM user equipment. The user equipment may include a
removable smart card that may be used in different user equipment types. The user
equipment is further sub-divided in to the Mobile Equipment Domain (ME) and the
User Services Identity Module Domain (USIM). The reference point between the ME
and the USIM is termed the Cu reference point.
Mobile equipment Domain
The Mobile Equipment performs radio transmission and contains applications. The
mobile equipment may be further sub-divided into several entities, e.g. the one which
performs the radio transmission and related functions, Mobile Termination, (MT), and
the one which contains the end-to-end application or (e.g. laptop connected to a mobile
phone), Terminal Equipment, (TE).
USIM Domain
The USIM contains data and procedures which unambiguously and securely identify
itself. These functions are typically embedded in a standalone smart card. This device is
associated to a given user, and as such allows to identify this user regardless of the ME
he uses.
Infrastructure Domain
The Infrastructure domain is further split into the Access Network Domain, which is
characterized by being in direct contact with the User Equipment and the Core Network
Domain. This split is intended to simplify/assist the process of de-coupling access
related functionality from non-access related functionality and is in line with the modular
principle adopted for the UMTS. The Access Network Domain comprises roughly the
functions specific to the access technique, while the functions in the Core network
domain may potentially be used with information flows using any access technique. This
split allows for different approaches for the Core Network Domain, each approach
specifying distinct types of Core Networks which can be connected to the Access
Network Domain, as well as different access techniques, each type of Access Network
connected to th Core Network Domain. The reference point between the access network
domain and the core network domain is termed the lu reference point.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
23
UMTS Domains
CP13_Ch2_02
Home
Network
Domain
Transit
Network
Domain
Serving
Network
Domain
Core
Network
Domain
Access
Network
Domain
Mobile
Equipment
Domain
USIM
Domain
Infrastructure
Domain
User Equipment
Domain
Iu [Yu] Uu
[Zu]
Cu
SIM
CARD
24
Access Network Domain
The Access Network Domain consists of the physical entities which manage the
resources of the access network and provides the user with a mechanism to access the
core network domain.
Core Network Domain
The Core Network Domain consists of the physical entities which provide support for the
network features and telecommunication services. The support provided includes
functionality such as the management of user location information, control of network
features and services, the transfer (switching and transmission) mechanisms for
signalling and for user generated information.
The core network domain is sub-divided into the Serving Network Domain, the Home
Network Domain and the Transit Network Domain. The reference point between the
serving network domain and the home network domain is termed the [Zu] reference
point. The reference point between the serving network domain and the transit network
domain is termed the [Yu] reference point.
Serving Network Domain
The serving network domain is the part of the core network domain to which the access
network domain that provides the users access is connected. It represents the core
network functions that are local to the users access point and thus their location changes
when the user moves. The serving network domain is responsible for routing calls and
transport user data/information form source to destination. It has the ability to interact
with the home domain to cater for user specific data/services and with the transit domain
for non-user specific data/services purposes.
Home Network Domain
The home network domain represents the core network functions that are conducted at a
permanent location regardless of the location of the users access point. The USIM is
related by subscription to the home network domain. The home network domain
therefore contains at least permanently user specific data and is responsible for
management of subscription information. It may also handle home specific services,
potentially not offered by the serving network domain.
Transit Network Domain
The transit network domain is the core network part located on the communication path
between the serving network domain and the remote party. If, for a given call, the remote
party is located inside the same network as the originating UE, then no particular
instance of the transit domain is activated.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
25
UMTS Domains
CP13_Ch2_02
Home
Network
Domain
Transit
Network
Domain
Serving
Network
Domain
Core
Network
Domain
Access
Network
Domain
Mobile
Equipment
Domain
USIM
Domain
Infrastructure
Domain
User Equipment
Domain
Iu [Yu] Uu
[Zu]
Cu
SIM
CARD
Version 1 Rev 7 UMTS Architecture Release 1999
26
UMTS Architecture Release 1999
The diagram opposite illustrates the basic configuration of a Public Land Mobile Network
(PLMN) supporting UMTS and GSM/GPRS. This architecture is as defined in Release
1999 of the 3GPP specifications (TS23.002)
The Core Network (CN) Entities
The CN is constituted of a Circuit Switched (CS) domain and a Packet Switched (PS)
domain. These two domains differ by the way they support user traffic, as explained
bellow. These two domains are overlapping, i.e. they contain some common entities. A
PLMN can implement only one domain or both domains.
CS Domain
The CS domain refers to the set of all the CN entities offering CS type of connection for
user traffic as well as all the entities supporting the related signalling. A CS type of
connection is a connection for which dedicated network resources are allocated at the
connection establishment and released at the connection release. The entities specific to
the CS domain are:
S MSC - The Mobile-services Switching Centre
S GMSC Gateway Mobile Service Switching Centre
S VLR Visitor Location Register
PS Domain
The PS domain refers to the set of all the CN entities offering PS type of connection for
user traffic as well as all the entities supporting the related signalling. A PS type of
connection transports the user information using autonomous concatenation of bits
called packets: each packet can be routed independently from the previous one. The
entities specific to the PS domain are the GPRS specific entities, i.e.
S SGSN Serving GPRS Support Node
S GGSN Gateway GPRS Support Node
Entities Common to the CS and PS domains
The following entities are common provide common functions to the CS and PS
Domains:
S HLR The Home Location Register
S AUC Authentication Centre
S EIR Equipment Identity Register
EMOTOROLA LTD. 2003
CP13: UMTS Overview
27
CP13_Ch2_11
GMSC GGSN AuC
HLR
EIR
SGSN
VLR
MSC
VLR
MSC
SIM
ME
USIM
Um
Um
CN
BSC
BTS BTS
BSC
BTS BTS
RNC
Node B Node B
RNC
Node B Node B
H
Gc
Gr
D
C
Gi
Gs
Gf F
G
E
Gp
Gn
PSTN PSTN
Abis
Gb
BSS
Abis lub lub
RNS RNS
BSS
SIMME I/f
or
MS
Cu
Uu
IuPS IuCS
IuPS
IuCS
A
Iur
28
The Access Network (AN) Entities
Two different types of access network are used by the CN: the Base Station System
(BSS) and the Radio Network System (RNS). The BSS offers a Time Division Multiple
Access (TDMA) based technology to access the Mobile Station whereas the RNS offers
a Wideband-Code Division Multiple Access (W-CDMA) based technology. The MSC
(resp. SGSN) can connect to one of these Access Network type or to both of them.
The Base Station System (BSS)
The Base Station System (BSS) is the system of base station equipments (transceivers,
controllers, etc...) which is viewed by the MSC through a single A-interface as being the
entity responsible for communicating with Mobile Stations in a certain area. Similarly, in
PLMNs supporting GPRS, the BSS is viewed by the SGSN through a single Gb
interface. The functionality for the A interface is described in GSM 08.02 and for the Gb
interface in TS 23.060. The radio equipment of a BSS may support one or more cells. A
BSS may consist of one or more base stations. Where an Abis-interface is implemented,
the BSS consists of one Base Station Controller (BSC) and one or more Base
Transceiver Station (BTS).
The Radio Network System (RNS)
The Radio Network System (RNS) is the system of base station equipments
(transceivers, controllers, etc...) which is viewed by the MSC through a single Iu-interface
as being the entity responsible for communicating with Mobile Stations in a certain area.
Similarly, in PLMNs supporting GPRS, the RNS is viewed by the SGSN through a single
Iu-PS interface. The functionality for the Iu-CS interface is described in TS 25.410 and
for the Iu-PS interface in TS 23.060. The radio equipment of a RNS may support one or
more cells. A RNS may consist of one or more base stations. The RNS consists of one
Radio Network Controller (RNC) and one or more Node B.
The Mobile Station (MS)
The mobile station consists of the physical equipment used by a PLMN subscriber; it
comprises the Mobile Equipment (ME) and the Subscriber Identity Module (SIM), called
User Services Identity Module (USIM) for Release 99 and following releases. The ME
comprises the Mobile Termination (MT) which, depending on the application and
services, may support various combinations of Terminal Adapter (TA) and Terminal
Equipment (TE) functional groups. These functional groups are described in GSM 04.02.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
29
CP13_Ch2_11
GMSC GGSN AuC
HLR
EIR
SGSN
VLR
MSC
VLR
MSC
SIM
ME
USIM
Um
Um
CN
BSC
BTS BTS
BSC
BTS BTS
RNC
Node B Node B
RNC
Node B Node B
H
Gc
Gr
D
C
Gi
Gs
Gf F
G
E
Gp
Gn
PSTN PSTN
Abis
Gb
BSS
Abis lub lub
RNS RNS BSS
SIMME I/f
or
MS
Cu
Uu
IuPS IuCS
IuPS
IuCS
A
Iur
Version 1 Rev 7 UMTS Network Release 1999
210
UMTS Network Release 1999
The diagram opposite shows a simplified schematic of a Release 1999 UMTS Network.
It illustrates only those entities associated with providing a UMTS service (i.e. excludes
any entities specifically associated with GSM/GPRS)
Entities of the CN-CS Domain
The Mobile Services Switching Centre (MSC)
The Mobile-services Switching Centre (MSC) constitutes the interface between the radio
system and the fixed networks. The MSC performs all necessary functions in order to
handle the circuit switched services to and from the mobile stations. In order to obtain
radio coverage of a given geographical area, a number of base stations are normally
required; i.e. each MSC would thus have to interface several base stations. In addition
several MSCs may be required to cover a country. The Mobile-services Switching Centre
is an exchange which performs all the switching and signalling functions for mobile
stations located in a geographical area designated as the MSC area. The main difference
between a MSC and an exchange in a fixed network is that the MSC has to take into
account the impact of the allocation of radio resources and the mobile nature of the
subscribers and has to perform procedures required for the location registration (see TS
23.012) and procedures required for handovers (see TS 23.009).
The Gateway MSC (GMSC)
If a network delivering a call to the PLMN cannot interrogate the HLR, the call is routed to
an MSC. This MSC will interrogate the appropriate HLR and then route the call to the
MSC where the mobile station is located. The MSC which performs the routing function
to the actual location of the MS is called the Gateway MSC (GMSC). The acceptance of
an interrogation to an HLR is the decision of the operator. The choice of which MSCs
can act as Gateway MSCs is for the operator to decide (i.e. all MSCs or some
designated MSCs).
The Visitor Location Register (VLR)
A mobile station roaming in an MSC area is controlled by the Visitor Location Register in
charge of this area. When a Mobile Station (MS) enters a new location area it starts a
registration procedure. The MSC in charge of that area notices this registration and
transfers to the Visitor Location Register the identity of the location area where the MS is
situated. If this MS is not yet registered, the VLR and the HLR exchange information to
allow the proper handling of calls involving the MS. A VLR may be in charge of one or
several MSC areas. The VLR contains also the information needed to handle the calls
set-up or received by the MSs registered in its database. The following elements are
included:
S The International Mobile Subscriber Identity (IMSI);
S The Mobile Station International ISDN number (MSISDN);
S The Mobile Station Roaming Number (MSRN), see TS 23.003 for allocation
principles;
S The Temporary Mobile Station Identity (TMSI), if applicable;
S The Local Mobile Station Identity (LMSI), if used;
S The location area where the mobile station has been registered;
S The last known location and the initial location of the MS.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
211
UMTS Network R99
CP13_2_3a
Node B Node B
Iub Iub
RNC
UTRAN
Node B Node B
Iub Iub
RNC
HLR
VLR
AuC
GMSC
MSC
GGSN
SGSN
CNCS
CNPS
CN Domain
IuCS IuPS
PSTN
OMCT
(Transport)
OMCU
(UTRAN)
Iur
Uu
User Equipment
RNS RNS
PDN
212
Entities Common to the CS and PS Domains
The Home Location Register (HLR)
This functional entity is a database in charge of the management of mobile subscribers.
A PLMN may contain one or several HLRs: it depends on the number of mobile
subscribers, on the capacity of the equipment and on the organisation of the network.
The following kinds of information are stored there:
S Subscription information.
S Location information enabling the charging and routing of calls towards the MSC
where the MS is registered (e.g. the MS Roaming Number, the VLR Number, the
MSC Number, the Local MS Identity).
S If GPRS is supported, location information enabling the charging and routing of
messages in the SGSN where the MS is currently registered (e.g. the SGSN
Number).
S The types of identity are attached to each mobile (e.g. International Mobile Station
Identity (IMSI), one or more Mobile Station International ISDN number(s)
(MSISDN), if GPRS is supported zero or more Packet Data Protocol (PDP)
address(es)).
The Authentication Centre (AuC)
The Authentication Centre (AuC) is an entity which stores data for each mobile
subscriber to allow the International Mobile Subscriber Identity (IMSI) to be authenticated
and to allow communication over the radio path between the mobile station and the
network to be ciphered. The AuC transmits the data needed for authentication and
ciphering via the HLR to the VLR, MSC and SGSN which need to authenticate a mobile
station. The Authentication Centre (AuC) is associated with an HLR, and stores an
identity key for each mobile subscriber registered with the associated HLR. This key is
used to generate:
S Data which are used to authenticate the International Mobile Subscriber Identity
(IMSI).
S A key used to cipher communication over the radio path between the mobile
station and the network.
The Equipment Identity Register (EIR)
The Equipment Identity Register (EIR) in the GSM system is the logical entity which is
responsible for storing in the network the International Mobile Equipment Identities
(IMEIs), used in the GSM system. The equipment is classified as white listed, grey
listed, black listed or it may be unknown as specified in TS 22.016 and TS 29.002.
This functional entity contains one or several databases which store(s) the IMEIs used in
the GSM system. An EIR shall as a minimum contain a white list (Equipment classified
as white listed). See also TS 22.016 on IMEI.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
213
UMTS Network R99
CP13_2_3a
Node B Node B
Iub Iub
RNC
UTRAN
Node B Node B
Iub Iub
RNC
HLR
VLR
AuC
GMSC
MSC
GGSN
SGSN
CNCS
CNPS
CN Domain
IuCS IuPS
PSTN
OMCT
(Transport)
OMCU
(UTRAN)
Iur
Uu
User Equipment
RNS RNS
PDN
Version 1 Rev 7 Overview of GSN3/USP1 architecture
214
Overview of GSN3/USP1 architecture
Components of the GSN Complex
The GSN Complex consists of:
S CSGSN
S GGSNs
S CommHub
S Charging Gateway (CGW)
S DNS/NTP Server
S Dynamic Load Balancer (DLB) an optional component for improved GGSN load
balancing .
Some of these network elements may not be present in a GSN Complex.
There may be one or more GSN Complexes in a PLMN.
The GSN Complex equipment also interfaces with other equipment that is needed for the
packet domain operation:
S RADIUS server (customerfurnished)
S DHCP server (customerfurnished)
S Firewall (customerfurnished)
S Border Gateway (customerfurnished)
S LIAN
S Bill System (BS) (customerfurnished).
Version 1 Rev 7 Overview of GSN3/USP1 architecture
EMOTOROLA LTD. 2003
CP13: UMTS Overview
215
Components of the GSN Complex
The GSN Complex consists of:
S CSGSN
S GGSNs
S CommHub
S DNS/NTP Server
S Dynamic Load Balancer (DLB) an optional component for
improved GGSN load balancing.
Some of these network elements may not be present in a GSN
Complex.
There may be one or more GSN Complexes in a PLMN.
The GSN Complex equipment also interfaces with other
equipment that is needed for the packet domain operation:
S RADIUS server (customerfurnished)
S DHCP server (customerfurnished)
S Firewall (customerfurnished)
S Border Gateway (customerfurnished)
S LIAN
S Bill System (BS) (customerfurnished).
CP13_Ch2_p15
Version 1 Rev 7 Packet switch core network components
216
Packet switch core network components
The Motorola GSN3/USP1 solution contains the packet switch core network elements:
CSGSN and GGSN.
A number of network elements are also needed for the packet domain operation. These
network elements are:
S DNS/NTP server
S Dynamic Load Balancer (DLB) an optional component for improved GGSN load
balancing
S IP router/CommHub
S Motorola OMCS/T server
S Cisco Management (CW4MW) Server
S Domain Manager Server (optional)
S O&M, consisting of the following applications:
CSGSN Local Manager
CGW Local Manager
Clients for the CW4MW, Motorola OMCS/T and Domain Manager.
Version 1 Rev 7 Packet switch core network components
EMOTOROLA LTD. 2003
CP13: UMTS Overview
217
Packet Switch Core Network Components
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
C-SGSN
Motorolasuppliedequipment is shown at the network element
(node) level. Multiplicity of links and nodes are shown within
the GSN Complex but no inference should be drawn regarding
the exact number of links and nodes present. Customerfur-
nished equipment, nonGSN3/USP1 equipment, communica-
tion networks and links connecting the above are only shown
at the logical level, i.e. no inference can be drawn from this
diagram about their physical implementation, multiplicity, etc.
Motorola supplied equipment for GSN3/USP1
Equipment outside the scope of GSN3/USP1 (typically
cutomerfurnished but some can be Motorola equip-
ment (e.g. RNC and PCU)
Communication network
Version 1 Rev 7 Motorola CSGSN
218
Motorola CSGSN
CSGSN Functionality
The Common SGSN supports GPRS for GSM (that is, the Gb interface is supported by
the CSGSN) and/or UMTS (that is, the Iu interface is supported by the CSGSN).
The CSGSN is the subsystem that controls the communication between the Mobile
System (MS) and a PDN host by supporting the Gb and IuPS interfaces to the
BSS/PCU and the UTRAN, respectively, on the one side, and the Gn/Gp interface to the
GGSN on the other. All bearer and control traffic from the MS and the PDN passes
through the CSGSN.
In the case of GPRS, the primary role of the CSGSN is to maintain a logical link with
each MS, providing a reliable and secure data channel as the MS moves between cells.
This link is implemented over the Logical Link Control (LLC) layer of the Gb interface. In
the UMTS case, the radio resource functions are placed within the UTRAN and the
CSGSN is not involved with the radio resource allocations.
The CSGSN mediates access to network resources on behalf of the MS and
implements the packet scheduling policy between different QoS classes. It is responsible
for establishing the Mobility Management (MM) context upon MS attachment and the
Packet Data Protocol (PDP) context with the GGSN upon activation.
The CSGSN also collects charging data for all PDP and MM contexts and SMS
sessions, generates Call Detail Records (SCDR, MCDR, SSMOCDR,
SSMTCDR), and sends those records to the CGW utilizing the Ga interface.
Version 1 Rev 7 Motorola CSGSN
EMOTOROLA LTD. 2003
CP13: UMTS Overview
219
CSGSN Functionality
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 GGSN
220
GGSN
GGSN functionality
The GGSN is the logical point of PDN interconnection to a GPRS network supporting the
Gi reference point. This interface provides access by MS subscribers to devices attached
to one or more external PDNs. The PDP used between the MS and the external PDN
hosts is currently IPv4. For a given PDP context, the MS is always anchored to one
GGSN as it moves amongst different SGSN nodes. The GGSN provides network access
to external hosts wishing to communicate with mobile subscribers. The GGSN directs
mobileterminated packets to the SGSN that is currently serving the MS, allowing the
MS to move freely within the coverage area of its home or foreign network.
The GGSN provides the following primary functions:
S Layer 3 routing.
S PDP context management (manages active MS to PDN routes).
S GTP encapsulation/decapsulation at the Gn/Gp interface.
S GPRS to PS network access via the Gi interface.
S RADIUS Proxy Client interface for end user authentication and accounting.
S DHCP Proxy Client interface for end user dynamic IP address allocation.
S APN configuration for management of mode of access to a PDN.
S PDP Context Charging data collection and subsequent forwarding to a CGW.
If configured accordingly, the GGSN can implement access restriction capability
applicable to mobile stations outside of the home PLMN (foreign mobile stations) based
on the mobiles Mobile Country Code (MCC) and Mobile Network Code (MNC).
The GGSN also collects charging data for all PDP contexts, creates GCDRs, and sends
those CDRs to the CGW over the Ga interface. The GGSN may optionally suppress
record generation based on Charging Characteristics flags.
The GGSN provides the interface to SGSNs in the home PLMN over the Gn interface
and to SGSNs in visited PLMNs over the Gp interface. When a GGSN is colocated with
the CSGSN, the physical interface is frequently configured for Fast Ethernet. An
enterprise GGSN may be connected to the CSGSN through a WAN interface (for
example, Frame Relay, ATM, and so on). The GGSN does not provide the Gc interface
in GSN3/USP1 USP1 and it relies on the CSGSN to access the HLR on its behalf and
to provide the GTP to MAP conversion.
The GPRS standards define a network identity called an Access Point Name (APN) to
identify the part of the network where a user session is established. Each GGSN is
configured with a list of APNs that it supports. The GGSN is responsible for allocating IP
addresses to MSs as part of PDP context activation. The GGSN may be configured to
access external support servers to provide services for the dynamic IP addressing of
MSs using the Dynamic Host Configuration Protocol (DHCP) and to provide security
such as authentication of users accessing a network at an APN using Remote
Authentication DialIn User Service (RADIUS) and AAA.
Version 1 Rev 7 GGSN
EMOTOROLA LTD. 2003
CP13: UMTS Overview
221
GGSN
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN
CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 Motorola Charging Gateway (CGW)
222
Motorola Charging Gateway (CGW)
Charging Gateway functionality
The Charging Gateway (CGW) provides a mechanism for transferring charging
information from the SGSNs and the GGSNs to the Network Operators chosen Billing
System (BS). The CGW concept enables a Network Operator to have just one logical
interface between the CGW and the Billing System.
The CGW collects Call Detail Records (CDR) from both the CSGSN and GGSN. CDRs
are sent from both nodes to the CGW over the Ga interface using GTP.
The CGW supports the following functions:
S CDR collection
S CDR validation
S CDR safe storage
S CDR reporting
S CDR routing (based on various criteria)
S CDR expediting (based on Charging Characteristics)
Version 1 Rev 7 Motorola Charging Gateway (CGW)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
223
Charging Gateway (CGW)
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 Communications Hub
224
Communications Hub
CommHub functionality
A platform for all IP switching, the CommHub is the central connection point for all
communication within GSN elements, and between the GSN and outside network
elements. It fulfils, among others, the functions of the backbone LAN and backbone IP
router.
The CommHub provides Ethernet connectivity, switching and IP routing capability
between the network elements in the GSN Complex (that is, CSGSN, GGSNs, CGW,
DNS server, DLBs and Firewall).
The CommHub also performs IP network security functions. For example, packet
address filtering is performed so that only those packets addressed to an MS
subnetwork are accepted. Packets directly addressed to one of the GSNs or to some
other IP subnetwork are discarded. This prevents the CommHub from being used to
directly access the GSNs, or as a relay between two external (nonGPRS) IP networks.
The IDS module provides intrusion detection by monitoring core traffic for
suspicious data signatures that would indicate a security breach. Alarm
generation and shunning of possible attack are the main functions, but is
configurable for more comprehensive features as required. It is shown on
the CommHub as an optional security enhancement.
Version 1 Rev 7 Communications Hub
EMOTOROLA LTD. 2003
CP13: UMTS Overview
225
Communications Hub
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
CommHub/IP
Router
Version 1 Rev 7 DNS/NTP Server
226
DNS/NTP Server
DNS/NTP Server functionality
The DNS/NTP Server provides the GSN system components with an internal Domain
Name Service (DNS) and Network Time Protocol (NTP).
The GSNs require accurate time information for generating accounting records, alarms
and logs. The Network Time Protocol (NTP) is used to synchronise the time of a
computer client or server to another server or high stratum reference time source. It
provides client accuracies typically within a millisecond on LANs and up to a few tens of
milliseconds on WANs, relative to a primary server synchronised to Coordinate
Universal Time (UTC) via a Global Positioning Service (GPS) receiver, for example.
Typical NTP configurations utilize multiple redundant servers and diverse network paths,
in order to achieve high accuracy and reliability.
The DNS Server provides name to IP address translation services. The two main usage
of DNS within the GPRS core network is to translate routing area codes into CSGSN IP
addresses during GPRS attach and routing area update procedures, and to translate the
Access Point Name (APN) to the IP address of a GGSN or a GGSN load balancing
device, during the PDP context activation procedure.
The content of the GSN DNS Server is names and IP addresses associated with the
GSN infrastructure equipment and its interfaces to external networks. A name can be a
piece of hardware or software. Within the GPRS network a name is most commonly any
of the following:
S GGSN.
S CSGSN.
S Module within a GGSN or CSGSN.
S Access Point Name.
S External network link.
S Other IP endpoint.
Each of these names will map to a unique IP address, which can be routed by the routing
entity in the GSN (CSGSN, Router, and so on). Hence the lookup and name resolution
service offered by the DNS ties together the entire network and maintains connectivity
between all components. A DNS is essential to the operation of all networks beyond
those of the most rudimentary size.
Version 1 Rev 7 DNS/NTP Server
EMOTOROLA LTD. 2003
CP13: UMTS Overview
227
DNS/NTP Server
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 IP Backbone
228
IP Backbone
The (intraPLMN) IP Backbone interconnects the SGSNs, the GGSNs, and other
network elements within a PLMN, which communicate via IP. It consists of all the routers,
switches, LAN, and WAN links in this IP network. The IP Backbone can be viewed as the
collection of switching/routing equipment residing in different GSN Complexes plus the
WAN links interconnecting these complexes.
The external interfaces such as the Gi and the Gp interfaces need to be secure. The
GGSN provides the option of IPSec on the Gi interface via the ISA card without
impacting performance. For the Gp interface 3GPP recommends the use of a Border
Gateway (BGW). The GSN supports this function via the use of an external router
providing the BGW functionality. If the GGSN is located remotely then this BGW may
also be used to provide security on the Gn interface. For additional security a Firewall
function may need to be implemented at the network edge (optional).
In general the router shall be capable of the following functions to be configured as an
edge router/FW/BGW.
S Address Filtering
S Antispoofing
S Intrusion Detection
S IPSec
S Routing Protocols (OSPF, RIP, and so on)
S Access Control Lists Filtering of packets based on source and/or destination IP
addresses, connection port, application, or traffic flow direction
S Audit Trail
S NAT/PAT
Version 1 Rev 7 IP Backbone
EMOTOROLA LTD. 2003
CP13: UMTS Overview
229
IP Backbone
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 Border Gateway
230
Border Gateway
The Border Gateway provides interPLMN domain routing over the Gp interface, routing
between the PLMN and PDN over the Gi interface, and potentially routing between
geographicallyseparated GSN Complexes within a PLMN over the Gn interface. The
BG requires external routing using the BGP4 external routing protocol.
The Border Gateway function also provides screening and optional firewall functions The
BG resides as a logical software function or as a dedicated appliance. The BG is used for
the GSN Complex as an edge router on the IP backbone.
The Border Gateway is customerfurnished equipment. The BG used in the reference
GSN Complex architecture is a Cisco 7206VXR with NPE400 and 512MB RAM,
equipped with one GE interface and two OC3 interfaces.
The deployed functions and features of the Border Gateway in a GPRS
Network are generally the responsibility of the Network Operator. The
Network Operator should be compatible with the GSM Association IREG
Subgroup InterPLMN roaming specification and comply with the GSM
03.60 or 3GPP 23.060 standard.
Firewall
Firewalls (FW) are designed to protect the resources of the GSN from attempted attacks
on its network resources. A firewall may be implemented as a software feature that runs
on an IP router or as a separate, standalone appliance. The FW capabilities may be
designed as a two tiered subsystem in conjunction with a BG .The BG router connecting
the outside network to the inside network provides the first layer of security. The second
layer of the FW subsystem may use routers configured with a FW feature set or with
specialized FW appliance.
Implementing a FW will always impact performance. The more options implemented
within the firewall the larger the impact. It is recommended that the BGW and FW be
implemented on dedicated hardware for larger systems where performance is critical. Not
only separate hardware alleviates the performance problems the separately implemented
FW provides a buffer between the internal and external networks. The BGW will be
aware of the addresses of the external network and the BNET/CSGSN will be aware of
the internal addresses and the FW can translate between the two without exposing one
to the other. All packets moving through the firewall are inspected based on the
established security policy and filtered accordingly.
The other traffic that needs to be routed through the FW is the DNS exchanges between
the GSN DNS server and the external DNS servers. A DNS proxy is attached to the
Firewall that is used to respond to DNS queries for interPLMN roaming.
The Firewall is customerfurnished equipment. The FW used in the reference
configuration is the Cisco PIX 535. It supports a data throughput of 1.7 Gbps maximum
in clear text with reduced throughput at 170 Mbps (estimated) when IPSec support with
3DES encryption is needed. It supports, among others, the GE interface.
Version 1 Rev 7 Border Gateway
EMOTOROLA LTD. 2003
CP13: UMTS Overview
231
Border Gateway
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 SS7 Nodes
232
SS7 Nodes
Home Location Register (HLR) / Authentication Centre (AuC)
The HLR is the central repository for subscription and subscriber location information in a
GSM/UMTS network. The HLR is used by both the CS domain and the PS domain.
The AuC stores the authentication key for GSM/UMTS subscribers and, on request,
provides authentication vectors to the MSC and the CSGSN for authentication of the
MSs and to enable encryption of traffic over the air interface. The AuC may be
colocated with the HLR.
Mobile Switching Centre (MSC) / Visitor Location Register (VLR)
The MSC provides the CS domain switching capability in a GSM/UMTS network.
If the optional Gs interface is installed between the MSC and the CSGSN, CS
procedures (e.g. IMSI attach, LA update, CS paging) can take place between the MS
and the MSC via the CSGSN.
The VLR contains subscription and MM state information for MSs served by an MSC.
The VLR is often colocated with the MSC.
SMS Gateway MSC (SMSGMSC) / SMS Interworking MSC (SMSIWMSC)
The SMSGMSC and the SMSIWMSC are special nodes for handling SMS. They
interact with the SMSC, the MSC and the CSGSN for delivery of short messages.
SMS can be delivered via the MSC, or via the CSGSN if the MS, CSGSN and the
SMSGMSC/SMSIWMSC support delivery via the PS domain (GPRS).
The SMSIWMSC processes MO short messages. The SMSGMSC processes MT
short messages.
CAMEL GSM SCF / PSCP
The CAMEL GSM SCF / PSCP is an Intelligent Network (IN) component that supports
the CAMEL Prepaid service logic for all GSM services (circuit switched voice & data,
packet switched data and SMS). It controls the behaviour of network switching nodes
(CSGSN, MSC) related to CAMEL services supported by those nodes. For GPRS, the
PSCP supports CAMEL phase 3 logic and detection points.
Equipment Identity Register (EIR)
The EIR stores the identity of the Mobile Terminal (MT) equipment and allows the MSC
and the CSGSN to verify if an MT is invalid or blacklisted.
Version 1 Rev 7 SS7 Nodes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
233
SS7 Nodes
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 Nodes for value added services
234
Nodes for value added services
Lawful Intercept Administrative Node (LIAN)
The LIAN handles the Lawful Intercept operation for the PS domain. The LIAN interacts
with one or more Law Enforcement Agency (LEA) that request LI service, and with the
SGSNs in the PLMN. The LIAN manages the list of MSs for which intercept warrants
have been issued by the LEAs and distribute this list to the SGSNs. The LIAN collects
intercept reports from the SGSNs, processes the reports and deliver them to the
interested LEAs.
Gateway Mobile Location Centre (GMLC)
A Gateway Mobile Location Centre (GMLC) is the first node an external LCS client
accesses in a PLMN (the Le reference point is supported by the GMLC). The GMLC may
request routing information from the HLR via the Lh interface to determine a subscribers
current CSGSN. The GMLC sends positioning requests to the CSGSN and receives
final location estimates via Lg interface using MAP procedures. The CSGSN determines
the subscribers current location using one of the following methods:
For subscribers in 2G mode, the current Cell ID is reported. If the current Cell ID is
unknown, then the CSGSN sends a page request to locate the target MS.
For subscribers in 3G mode, the CSGSN reports the service area or Cell ID in which
the target MS is located; The CSGSN sends a location request message to the UTRAN,
which determines the location of the target MS and sends a location report to CSGSN.
Version 1 Rev 7 Nodes for value added services
EMOTOROLA LTD. 2003
CP13: UMTS Overview
235
Value Added
IP Backbone
FE
E1 E1
GSN Complex
FE
FW BG
CommHub/IP
Router
GGSN CGW
ATM N/W
FR N/W
Foreign
PLMN
LIAN
DHCP
Server
RNC PCU
Location
Service
EIR
HLR MSC/VLR
PSCP
PDN
RADIS
Server
GSN
OMCS/T
Server
BS
DNS/
NTP
Server
DLB
CW4M
W
Server
DM
Server
SS7 N/W
SMS GMSC
SMSIWMSC
STM1
CSGSN
Version 1 Rev 7 GPRS/UMTS Interfaces
236
GPRS/UMTS Interfaces
Interface System Plane Between Protocols
Gn Both User GSNs (CSGSN to CSGSN or
CSGSN to GGSN)
GTP/UDP/IP/L2/L1
Gn Both Control GSNs GTPC/UDP/IP/L2/L1
Gb GSM User/
Control
CSGSN to BSS BSSGP/FR/E1
IuPS UMTS Control UTRAN to CSGSN RANAP/SCCP/SS7/ATM
IuPS UMTS User UTRAN to CSGSN GTPU/UDP/IP/AAL5/ATM
Gs Both Control CSGSN to MSC/VLR BSSAP+/SCCP/MTP3/
MTP2/L1
Gd Both Control CSGSN to SMSMSC MAP/TCAP/SCCP/MTP3/MTP2/L1
Gr Both Control CSGSN to HLR MAP/TCAP/SCCP/MTP3/MTP2/L1
Ga Both User/
Control
CSGSN to CGW
GGSN to CGW
GTP/UDP/IP/L2/L1
Gp Both User GSNs belonging to different
PLMNs
GTPU/UDP/IP/L2/L1
Gp Both Control GSNs belonging to different
PLMNs
GTPC/UDP/IP/L2/L1
Gi Both User/
Control
GGSN to PDN Application/TCP(UDP)/IP/
L2/L1/GRE+/PPP
Ge Both Control CSGSN to GSMSCP CAP/TCAP/SCCP/MTP3/MTP2/L1
Gf Both Control SGSN to EIR MAP/TCAP/SCCP/MTP3/MTP2/L1
CP13_Ch2_p36
Version 1 Rev 7 GPRS/UMTS Interfaces
EMOTOROLA LTD. 2003
CP13: UMTS Overview
237
GPRS/UMTS Interfaces
Gf
Uu
Um
D
Gi
Gn
Iu
C E
Gp
Gs
Signalling and Data Transfer Interface
Signalling Interface
MSC/VLR
TE MT UTRAN TE PDN
Gr
Iu
HLR
Other PLMN
SGSN
GGSN
Gd
SM-SC
SMS-GMSC
SMS-IWMSC
GGSN
SGSN
Gn
CGW
Ga
Ga
Billing
System
Gb
TE MT BSS
R
A
R
CAMEL
GSM-SCF
Ge
EIR
Version 1 Rev 7 UMTS Terrestrial Radio Access Network (UTRAN)
238
UMTS Terrestrial Radio Access Network (UTRAN)
The UTRAN consists of a set of Radio Network Subsystems (RNSs) connected to the
Core Network through the IuCS and IuPS. An RNS consists of a Radio Network
Controller (RNC) and one or more Node Bs. A Node B is connected to the RNC through
the Iub interface. A Node B can support FDD mode, TDD mode or dual-mode operation.
The RNC is responsible for the Handover decisions that require signalling to the UE. An
RNC may include a combining/splitting function to support combination/splitting of
information streams.
Inside the UTRAN, the RNCs of the Radio Network Subsystems can be interconnected
together through the Iur. Iu(s) and Iur are logical interfaces. Iur can be conveyed over
direct physical connection between RNCs or virtual networks using any suitable transport
network.
UTRAN Functions
The following is a list of the functions performed by the UTRAN sub-systems. These
functions will be discussed in further detail in later chapters.
Functions related to overall system access control
S Admission Control
S Congestion Control
S System information broadcasting
Radio channel ciphering and deciphering
Functions related to mobility
S Handover
S SRNS Relocation
Functions related to radio resource management and control
S Radio resource configuration and operation
S Radio environment survey
S combining/splitting control
S Radio bearer connection set-up and release (Radio Bearer Control)
S Allocation and deallocation of Radio Bearers
S Radio protocols function
S RF power control
S RF power setting
S Radio channel coding/decoding
S Channel coding control
S Initial (random) access detection and handling
S CN Distribution function for Non Access Stratum messages
Functions related to broadcast and multicast services
NOTE: Only Broadcast is applicable for Release 1999.
S Broadcast/Multicast Information Distribution
S Broadcast/Multicast Flow Control
S CBS Status Reporting
Version 1 Rev 7 UMTS Terrestrial Radio Access Network (UTRAN)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
239
UMTS Terrestrial Radio Access Network (UTRAN)
c
Node B Node B
Iub Iub
RNC
Node B Node B
Iub Iub
RNC
Core Network
Iu Iu
Iur
RNS RNS
Version 1 Rev 7 Radio network Controller (RNC)
240
Radio network Controller (RNC)
A Radio Network Controller (RNC) is a network component within the PLMN with the
functions to support one or more Node B, Cell and/or User Equipment.
Typically one RNC can support up to 300 Node Bs, which in turn can provide resources
for up to 6 cells. However, it should be noted that the ultimate limiting factor in planning
the number of RNCs required within a PLMN will be the traffic capacity that the RNC can
support. Typical values will start at around 1000 Erlang, rising to 10,000 Erlang as
networks mature.
A Radio Network Controller (RNC) can be considered to operate in one or more of the
following roles:
S Controlling Radio Network Controller (CRNC)
S Serving Radio Network Controller (SRNC)
S Drift Radio Network Controller (DRNC)
Controlling Radio Network Controller (CRNC)
Controlling RNC is a role an RNC can take with respect to a specific set of Node Bs.
There is only one Controlling RNC for any Node B. The Controlling RNC has the overall
control of the logical resources of its node Bs.
The main functions of a CRNC are:
S Control of the Radio Resources for the Node-B it controls.
S Provision of Services to the Node-B that it controls.
S Load and Congestion Control
S Admission Control
S Code allocation for new radio links
EMOTOROLA LTD. 2003
CP13: UMTS Overview
241
UTRAN CRNC Functions
CP13_Ch2_05
Controlling of the Radio Resources
Provision of Services to the NodeB
Load and Congestion Control
Admission Control
Code Allocation for new Radio Links
Iu
lur
Iu
CRNC CRNC
242
Serving Radio Network Controller (SRNC)
A Serving RNC is the RNC located within a Serving RNS (SRNS). SRNS is 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.
The main functions of an SRNC are:
S Termination of the Radio Resource Control Signalling between the RNC and the
UE.
S L2 Processing (PDCP, RLC, MAC)
S Radio Resource Control operations.
S Mapping of Iu Bearer Parameters onto Transport Channels Parameters.
S Hand-over decisions.
S Outer loop power control.
S Macro-Diversity combining and splitting.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
243
UTRAN SRNC Functions
CP13_Ch2_06
Termination of the Radio Resource Control Signalling
between the RNC and the UE
L2 Processing (PDCP, RLC, MAC)
Radio Resource Control Operations
Mapping of Bearer Parameters onto Transport Channel Parameters
HandOver Decisions
SRNC
Outer Loop Power Control
Macrodiversity Combining and Splitting

244
Drift Radio Network Controller (DRNC)
A Drift RNC is located within a Drift RNS. DRNS is role that an RNS can take with
respect to a specific connection between a UE and UTRAN.
A DRNS is any RNS that supports the Serving RNS by providing radio resources via the
cell(s) it controls, to provide additional radio bearer services for a specific connection
between a UE and UTRAN.
There may be zero, one or more DRNSs associated with a specific connection between
a UE and UTRAN.
The main functions of a DRNC are:
S Macro-diversity combining and splitting.
S No L2 processing, i.e. no re-transmissions, acknowledgements or negative
acknowledgements.
S Transparent routing of data on the Iub and Iur Interfaces, except when Common or
shared channels are used.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
245
UTRAN DRNC Functions
CP13_Ch2_07
Macrodiversity Combining and Splitting
No L2 Processing
Transparent Routing except for Common/Shared Channels
DRNC
SRNC
Version 1 Rev 7 Node B
246
Node B
A Node B is a logical node in the RNS that is in charge of radio transmission and
reception in one or more cells. Each Node B is Identified within the UTRAN by a unique
Node B ID. Typically a Node B will support up to six cells. Each cell is a specific radio
coverage area and is Identified by a unique Cell ID, which will be broadcast across the
entire cell area.
The diagram opposite shows the typical architecture of a Motorola Node B.
Wideband Digital Modem (WDM)
The WDM card is the heart of the Node B and performs the majority of the layer 1
(physical layer) functions. Motorola has designed the WDM card to support a high traffic
throughput and to allow trunking across multiple carriers/sectors. This gives advantages
in terms of availability and also allows the Node B to efficiently handle non-uniform traffic
distributions. Up to 6 WDMs can be installed per Node B cabinet and the WDM is fully
compliant to the June 01 standards baseline of the R99 3GPP standard.
The WDM functions include:
S Transmit and Receive chip and symbol level processing
S User plane protocol termination for the Node B/RNC interface
S Termination of intra Node B control protocol
S Physical control of the signal processing function
S Termination of the intra Node B time reference interface
The Wideband Transceiver (WBX)
The Wideband Transceiver (WBX) is the interface between the analog and digital
baseband worlds. On the forward link the WBX accepts baseband digital data from the
WDM via the baseband bus, formats this data to UMTS air interface requirements, and
produces a modulated RF signal at the required carrier frequency for further amplification
and transmission via the appropriate antenna.
On the reverse link the received signals are amplified, filtered, down-converted, sampled
and digitally processed. Digital data is then output to the WDMs via the baseband bus
for further processing. Each WBX contains two receiver line-ups, for the main and
diversity branches. The WBX also supports transmit diversity
One WRX is required per cell and typically an additional, redundant device can be fitted.
Linear Power Amplifier (LPA)
The Linear Power Amplifier (LPA) subsystem consists of either 3 or 6 hybrid matrixes
power amplifiers. 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. The trunked LPA subsystem can be configured to support omni,
three and six sector configurations, as well as allowing the site to be reconfigured to
meet new operator requirements. The input matrix accepts the composite signals for
each sector for amplification. Up to six LPA modules contribute to amplifying all signals
presented at the input ports. The output matrix ensures proper distribution of the
amplified signals to the correct sector output, whilst minimising the amount of energy
presented at the other sector outputs.
Version 1 Rev 7 Node B
EMOTOROLA LTD. 2003
CP13: UMTS Overview
247
Node B Architecture
CP13_2_7a
WBX
WDM(s)
Iub
123
123
1
2
3
To
Antenna
O/P
Matrix
I/P
Matrix
1
2
3
Trunked
linear
123
123
123
Version 1 Rev 7 User Equipment (UE)
248
User Equipment (UE)
Introduction to User Equipment
UMTS aims to offer service capabilities that enable a wide variety of services to be
implemented. Such services range from simple services like speech, to complex
multimedia services containing several simultaneous media components that place totally
different requirements on the system and on the terminal equipment. By standardising
service capabilities rather than actual services, more flexibility is available for service
providers/network operators to create unique services. The same principle also applies
for UMTS terminals, i.e. the types of terminals are not standardised and are therefore not
limited in any way. A wide range of terminal types is likely in the UMTS environment, e.g.
speech only terminals, videophones, data terminals, wideband data terminals, fax
terminals, multiband/multimode terminals and any combination of the aforementioned.
Terminal development trends for todays terminals are mainly towards higher integration
levels resulting in smaller size. The goal of four 100s has been a rule of thumb target
for handsets, i.e., 100 hour standby, 100 cc size, 100 gram weight and also 100 MIPS
performance. The size targets have already been achieved and any requirement for
smaller terminals is questionable from the usability and physical size limitations
perspective. The other target parameters have no maximum limitations. On the other
hand, we can see the following further trends for near future terminals:
S Application specific terminals (smart traffic, vending machine radio, etc.);
S Increased number of value adding features (graphics, smart messaging, PC
connectivity and compatibility, memory databases, speech recognition, messaging
features, display functions, and different source coding methods (e.g., JPEG));
S Support for higher number of source codecs (several speech codecs);
S Multiband terminals (e.g., GSM in 900MHz and DCS1800);
S Multimode terminals (e.g., UMTS/GSM dualmode terminal);
S Dynamic SW configurability;
These trends are more than likely to continue in the future. Multiband and multimode
terminals with high integration levels would be preferred by the users. Technological
development of these terminals relies on new packaging and interconnection
technologies, as well as technological steps like SWradio. The concept trends of mobile
handheld terminals is likely to diverge from simple speech terminals towards a variety of
different types, e.g., communicators, wearable phones, data terminals, etc. The dominant
role of speech terminals will be challenged in the future by these new data and
multimediaoriented terminals.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
249
User Equipment
CP13_Ch2_09
Speech Only
Videophones
Data Terminals
Wideband Data Terminals
Fax Terminals
Application Specific Terminals
Multiband/Multimode Terminals
Dynamic Software Configurability
Value Adding Features

250
UE Architecture
The UMTS UE will consists of a number of logical software and hardware modules.
Although these modules may be delivered by a single vendor as single physical and
indivisable package, it is also possible that they will be independent physical units.
The reference architecture showing the modules of the UE, along with their
corresponding network functions are illustrated opposite and described in the following
paragraphs.
Integrated Circuit (IC) Card
The IC card is the module on which are implemented the user and subscription
dependent functions of the UE. The primary component of the IC card is the User
Service Identity Module (USIM)
The mandatory requirements for IC Cards used for holding USIM application, are related
to the need to have one USIM application on the IC card, as well as to the security
issues. The following functionality is required from the IC card holding a USIM
application:
S Physical characteristics same as used for GSM SIM
S The support of one USIM application
S The support of one or more user profile on the USIM
S Possibility to update USIM specific information over the air, (e.g. such information
as service profile information, algorithms, etc.) in a secure and controlled manner.
S Security mechanisms to prevent USIM application specific information from
unauthorised access or alteration.
S User authentication.
In addition to the mandatory functions, the IC Card may support the following additional,
optional functionality
S The support for more than one simultaneous application (Multiple USIM, Ecash
and/or some other applications).
S Possibility to have shared applications/files between multiple subscriptions,
including ADNs, other user/SP controlled files and data.
S Possibility for some applications/files to be restricted to one or some of the
subscriptions, under user/SP control.
S Inclusion of a payment method (electronic money and/or prepaid and/or
subscription details)
S An interface allowing highly secure downloading and configuration of new
functionality, new algorithms and new applications into the IC card as well as
updating the existing applications, algorithms and data.
S Support for storing and possibly executing encryption related information, such as
keys and algorithms.
S In multi application cards a functionality to prevent the unauthorised access and
alteration of USIM specific information by other applications residing on the card.
S The ability to accept popular valueadding IC card applications, such as digital
signature applications, EMV credit/debit card, electronic purses such as Mondex
and Visacash, etc.
S Possibility for one UMTS SP to block multiple subscription on the card the SP has
issued.
Shared applications could include databases (e.g. telephone books), service profiles (e.g.
controlling divert information), users preferences (e.g. short dialling codes) and
SPspecific parameters inside a USIM application (e.g. call barring tables).
EMOTOROLA LTD. 2003
CP13: UMTS Overview
251
UE Architecture
CP13_Ch2_09b
MT
RT
NT
TA
IC CARD
USIM
TERMINAL
EQUIPMENT
MOBILE
EQUIPMENT
UTRAN
CORE
NETWORK
TERMINAL
EQUIPMENT
R
Tu
Iu
USER
EQUIPMENT
(UE)
USER
APPLICATION
USER
APPLICATION
252
Terminal Equipment (TE)
The TE is the part of the UE on which the users end-to-end application functions
execute, terminating the services transported via the UMTS bearers. The TE is regarded
as a service dependent component, interacting with a peer TE in the external network.
Mobile Equipment (ME)
The ME is the users subscription independent, but mobile system dependent component
of the UE. It will terminate all control plane functions and the user plane UMTS bearer.
The ME consists of the following modules:
S Terminal Adaptation Function (TAF)
S Mobile Termination (MT)
TAF
The TAF provided the interaction between the TE and MT, via the R interface/reference
point. This may include the ability of the TE to control the MT by, for example, the use of
commands sets ( e.g. Modem AT control commands).
MT
THE MT is the telecom service independent, but UMTS dependent portion of the UE
which terminates the radio transmissions to and from the network. Within the MT two
further modules are defined.
The Radio Termination (RT) which is dependent upon the the radio access network. A
single RT will provide common functions for all services using the same radio access
technology. For UMTS the RT terminates the UTRAN physical layer (Uu interface) and
also encompasses the the AccessStratum layer 2 and layer three protocols (see
chapter 4 for further details)
The RT interfaces to the Network Termination (NT), at the Tu reference points. While
the RT is RAN dependent, the NT is CN dependent, and thus terminates, at the serving
network, the Nonaccess Stratum layer 3 protocols, for functions such as mobility
management, call control, session management, etc. To fulfil many of these functions,
the NT must have access to information stored on the USIM (e.g. security information),
this is accessed via the interface at the Cu reference points.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
253
UE Architecture
CP13_Ch2_09b
MT
RT
NT
TA
IC CARD
USIM
TERMINAL
EQUIPMENT
MOBILE
EQUIPMENT
UTRAN
CORE
NETWORK
TERMINAL
EQUIPMENT
R
Tu
Iu
USER
EQUIPMENT
(UE)
USER
APPLICATION
USER
APPLICATION
254
MT Functionality
The UMTS standards do not restrict the functionality of the terminals in any way. The
standards should allow terminal specific features and functions to exist. However, a
minimum set of mandatory functions are required in order to ensure proper behaviour of
the system, and relate mainly to the interaction with the terminal and the network. Other
optional features are supported by the standard, allowing additional functionality for
UMTS terminals
Mandatory Functions
The following functions should be considered mandatory for all UMTS terminals:
S Terminal IC Card interface;
S SP and Network registration and deregistration;
S Location update;
S Originating or receiving a connection oriented or a connectionless service;
S An unalterable equipment identification;
S Basic identification of the terminal capabilities;
S Terminals capable for emergency calls should support emergency call without a
USIM;
S Support for the execution of algorithms required for authentication and encryption;
Additional Features
The Standard should support the following additional functionality for UMTS terminals:
S A mechanism to download service related information (parameters, scripts or even
software), new protocols, other functions and even new APIs into the terminal;
S An API capability to allow information transfer through a well known interface;
S Maintenance of the VHE using the same user interface and or another interface
while roaming;
S Optional insertion of several cards. An example scenario for this feature is a fax
machine with a multiple IC card slots, where several users could insert their IC
card and receive faxes.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
255
UE Functions
CP13_Ch2_09c
At least one IC Card interface
SP and Network Registration/Deregistration
Location Update
MO or MT of services
Unalterable Equipment ID
Basic ID of Equipment Capabilities
Emergency calls without USIM
Dynamic Software Configurability
Support of Authentication and Encryption
Mandatory Functions
CP13_Ch2_09c
Support for download of service related information
API capability through well known interfaces
Support of VHE
Optional insertion of multiple IC cards
Optional Functions
Version 1 Rev 7 Network Evolution
256
Network Evolution
The ultimate target of 3GPP is to drive UMTS towards an all Internet Protocol (IP)
architecture. The exact detail of this architecture is still under development and will the
subject of staged future releases of 3GPP Technical Specifications, Known as Release
4 (previously known as Release 2000) and Release 5. Motorola will track this evolution
through its core network (GSN) product, which will also evolve in a series of stages to
deliver aspects of all-IP functionality. The all IP system, shown in the diagram opposite,
complies with UMTS all-IP specifications as defined by 3GPP.
Product evolution
There are four stages in the evolution of the GSN from Release 99 to Release 4:
Using IP options on the open interfaces
Since most of the GPRS core network interfaces are already based on IP, this is a
relatively straightforward change. For the GSN, the Iu-ps interface operates using a
different protocol stack for signalling which uses SCTP protocol rather than C7 MTP3b at
the lower layer.
This can be implemented by a software upgrade for both GSN and RNC. Additionally,
GSM MAP messages can also be routed via SCTP rather than C7 MTP allowing IP to
carry all signalling traffic. This would require software upgrade within the GSN, and the
addition of a signalling gateway at the edge of the network to interwork between the C7
and IP protocol stacks.
Initially, this reduces the need for operators to maintain a separate and expensive C7
signalling network. Longer term, it also allows inter-network signalling traffic to be routed
via IP which can be secured using IPSec, both saving costs and increasing security. For
interoperability with other vendors, existing Release 99 interfaces are retained as a
configurable option.
Separation of bearer and control
Our GSN architecture follows the current GPRS standard that uses the same SGSN
node to handle both signalling and bearer traffic, although these are physically processed
on different cards.
By ensuring there are separate routes and processing cards for both types of traffic, a
higher capacity, more scalable, efficient and resilient GSN architecture can be realised.
This will be achieved by scaling a GSN separately for signalling load (based on number
of subscribers, context activations etc) and for bearer load (based on number of packets
per second, total throughput etc). A distributed GSN is also enabled at this stage, with
redundant routers providing 99.999% system availability using some 99.9% availability
components.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
257
Network Evolution
Ch2_08a.ai
IP Intranet
HSS/
SDB
Network Control Elements
Call State Control Function
Call Control + SGSN functionality
GPRS/UMTS
Intranet
RNC Servers
Node B Node B Node B
SDUs
3G RAN
IP/ATM
OMCs
OMCs
Radio
SGSN
GGSN
Transport
Management
Elements
GGSN
Gateway
PSTN
Gateway
C7
Gateway
Border
Gateway
MAP,
CAMEL,
INAP
PSTN
Voice
Other
PLMN
GSNs
Gateways
Location
Prepaid
MExE
WAP
Feature Servers
Application
Servers Iu (cs & ps)
Other RAN
Iur
PDN
Data
258
Adding Iu-CS and MSC functionality
Adding further processing cards within the GSN, supplemented by a PSTN Gateway,
extends the GPRS core network to handle voice services and voice traffic without the
need for an MSC.
The evolved SGSN is termed the Call State Control Function (CSCF) and provides the
call control aspects, and along with the GGSN, also provide the functionality to allow
calls to and from IP end points that may be an IP-enabled phone, enterprise IP-based
PBX, PC, or any other voice-enabled IP device.
The PSTN gateway provides the interworking functionality for MS to PSTN, or PSTN to
MS calls. The PSTN gateway is the interface from the IP core network to the PSTN.
Processing within the gateway holds the vocoding algorithms for converting between a
voice call encapsulated in an air interface frame and PSTN Pulse-Code Modulation
(PCM).
HLR functionality is offered by our Home Subscriber Services (HSS) node, which also
provides secure provisioning of WAP/MExE services.
Adding access independent multimedia overlay
This major new network, the IP Multimedia Sub-system (IM), will require a number of
new elements, including packet and circuit gateways and further processing. The IM
overlay uses the SIP multimedia call model, DIAMETER or RADIUS authentication and
billing, and offers the same set of services across a wide range of access technologies.
New terminals, roaming agreements and services are required to take full advantage of
this technology, which takes full advantage of widespread IP deployment and
accessibility in this timeframe.
Application Servers
In addition to providing telecommunications services (Voice and data) it is envisaged that
network operators will start to provide Network Services, such as Internet access,
e-mail facilities, etc. To provide these services, a range of applications servers will be
required.
Network services are covered in further detail in the next chapter.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
259
Network Evolution
Ch2_08a.ai
IP Intranet
HSS/
SDB
Network Control Elements
Call State Control Function
Call Control + SGSN functionality
GPRS/UMTS
Intranet
RNC Servers
Node B Node B Node B
SDUs
3G RAN
IP/ATM
OMCs
OMCs
Radio
SGSN
GGSN
Transport
Management
Elements
GGSN
Gateway
PSTN
Gateway
C7
Gateway
Border
Gateway
MAP,
CAMEL,
INAP
PSTN
Voice
Other
PLMN
GSNs
Gateways
Location
Prepaid
MExE
WAP
Feature Servers
Application
Servers Iu (cs & ps)
Other RAN
Iur
PDN
Data
260
EMOTOROLA LTD. 2003
CP13: UMTS Overview
31
Chapter 3
Network Services
Version 1 Rev 7
32
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
33
Chapter 3
Network Services 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Network Services 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Classification of Services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multimedia services: 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supplementary services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teleservices 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bearer Services 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Capabilities 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of Services 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information Transfer 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic characteristics 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information Quality 310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Bit Rates 312 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of Service 314 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QoS Attributes 316 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Security Architecture 318 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security and Privacy 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User authentication: 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network authentication: 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Confidentiality 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data integrity 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile equipment identification 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication and Key Agreement 322 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribution of authentication data from HE to SN 322 . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication and Key Agreement 322 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering Algorithms 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F8 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F9 324 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generation of Authentication Vectors/Tokens 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQN and RAND 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication Key Management Field 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Algorithms f1 f5 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AUTN and AV 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USIM Authentication Function 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrieval of SQN 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computation of X-MAC 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verification of SQN 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computation of CK and IK 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Authentication Response 328 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Link Data Integrity 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data integrity protection method 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input parameters to the integrity algorithm 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering of User/Signalling Data 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input parameters to the cipher algorithm 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
34
EMOTOROLA LTD. 2003
CP13: UMTS Overview
31
Objectives
S Describe the UMTS service objectives
S Describe the UMTS service classifications
S Describe Quality of Service Architecture
S Describe the UMTS Security Architecture
Version 1 Rev 7 Introduction to Network Services
32
Introduction to Network Services
This chapter describes the Service Principles for PLMNs specified by 3GPP.
3GPP specifications provide integrated personal communications services. The system
will support different applications ranging from narrow-band to wide-band
communications capability with integrated personal and terminal mobility to meet the user
and service requirements of the 21
st
century.
3GPP specifications allow the realisation of a new generation of mobile communications
technology for a world in which personal communications services should allow
person-to-person calling, independent of location, the terminal used, the means of
transmission (wired or wireless) and the choice of technology. Personal communication
services should be based on a combination of fixed and wireless/mobile services to form
a seamless end-to-end service for the user.
3GPP specifications outline the following objectives:
S To provide a single integrated system in which the user can access services in an
easy to use and uniform way in all environments
S To allow differentiation between service offerings of various serving networks and
home environments.
S To provide a wide range of telecommunications services, including those provided
by fixed networks and requiring user bit rates of up to 2 Mbits/s, as well as
services special to mobile communications. These services should be supported in
residential, public and office environments and in areas of diverse population
densities. These services are provided with a quality comparable with that
provided by fixed networks such as ISDN.
S To provide services via hand held, portable, vehicular mounted, movable and fixed
terminals (including those which normally operate connected to fixed networks), in
all environments (in different service environments - residential, private domestic
and different radio environments) provided that the terminal has the necessary
capabilities.
S To provide support of roaming users by enabling users to access services provided
by their home environment in the same way even when roaming.
S To provide audio, data, video and particularly multimedia services.
S To provide for the flexible introduction of telecommunication services.
S To provide within the residential environment the capability to enable a pedestrian
user to access all services normally provided by fixed networks.
S To provide within the office environment the capability to enable a pedestrian user
to access all services normally provided by PBXs and LANs
S To provide a substitute for fixed networks in areas of diverse population densities,
under conditions approved by the appropriate national or regional regulatory
authority.
S To provide support for interfaces which allow the use of terminals normally
connected to fixe networks.
Version 1 Rev 7 Introduction to Network Services
EMOTOROLA LTD. 2003
CP13: UMTS Overview
33
UMTS Service Objectives
S Single integrated system
S Differentiation between service offerings of various serving networks and
home environments.
S A wide range of telecommunications services.
S Services via hand held, portable, vehicular mounted, movable and fixed
terminals networks, in all environments
S Support of roaming users
S Audio, data, video and particularly multimedia services.
S Provide for the flexible introduction of telecommunication services.
S Within the residential environment, all services normally provided by fixed
networks.
S Within the office environment, all services normally provided by PBXs and
LANs
S Provide a substitute for fixed networks
S Support interfaces which allow the use of terminals normally connected to
fixed networks.
CP13_Ch3_p3
Version 1 Rev 7 Classification of Services
34
Classification of Services
Multimedia services:
Multimedia services combine two or more media components (e.g. voice, audio, data,
video, pictures) within one call. For some services, synchronisation between the media is
necessary (e.g. synchronised audio and video). A multimedia service may involve
multiple parties, multiple connections, and the addition or deletion of resources and users
within a single call.
Supplementary services
A supplementary service modifies or supplements a basic telecommunication service.
Consequently, it cannot be offered to a user as a stand alone service. It shall be offered
together or in association with a basic telecommunication service. The same
supplementary service may be applicable to a number of basic telecommunication
services.
Teleservices
Teleservices provide the full capabilities for communications by means of terminal
equipment, network functions and possibly functions provided by dedicated centres. The
methodology used covers both single media and multimedia services, the single media
services being a particular type of multimedia services. Multimedia services are classified
into categories with similar functional characteristics. The six categories are multimedia
conference services, multimedia conversational services, multimedia distribution
services, multimedia retrieval services, multimedia messaging services and multimedia
collection services.

Bearer Services
Bearer services provide the capability for information transfer between access points and
involve only low layer functions.
PS and CS domains provide a specific set of bearer capabilities. The Circuit bearer
services are described in 22.002. The packet services (GPRS) is described in TS 22.060.
Service Capabilities
Service capabilities are based on functionality and mechanisms/toolkits such as provided
by SAT, MExE, IN and CAMEL. These service capabilities can be made visible to the
applications through an application interface.
Version 1 Rev 7 Classification of Services
EMOTOROLA LTD. 2003
CP13: UMTS Overview
35
Classification of Services
S Multimedia Services
S Supplementary Services
S Teleservices
S Bearer Services
S Service Capabilities
CP13_Ch3_p5a
Definition of Teleservices and Bearer Services
TE
MT
PLMN
possible
transit
network
Terminating
network
Bearer services
Teleservices
UE
UE: User Equipment
MT: Mobile Termination
TE: Terminal Equipment
TAF: Teminal Adaption Function
TE TAF
Version 1 Rev 7 Description of Services
36
Description of Services
Bearer services are characterised by a set of end-to-end characteristics with
requirements on QoS. The characteristics and requirements cover major network
scenarios, i.e. the cases when the terminating network is PSTN, ISDN, GSM, IP
networks/LANs, X.25 and a PLMN.
Quality of Service is the quality of a requested service (Teleservice or Bearer Service or
any other service, e.g. customer care) as perceived by the customer. QoS is always
meant end-to-end. Network Performance of several network elements of the originating
and terminating network(s) contribute to the QoS as perceived by the customer including
terminals and terminal attachments. In order to offer the customer a certain QoS the
serving network needs to take into account network performance components of their
network, reflect the performance of the terminal and ad sufficient margin for the
terminating networks in case network performance requirements cannot be negotiated.
As far as the QoS to the subscriber is concerned network elements have to provide
sufficient performance (reflecting possible performance constraints in terminating
networks) so that the PLMN cannot be considered as a bottleneck.
This section outlines the requirements on bearer services in two main groups;
S Requirements on information transfer,
S Information quality characteristics, which describe the quality of the user
information transferred between two or more access points.
It shall be possible to negotiate / re negotiate the characteristics of a bearer service at
session / connection establishment and during an on going session / connection.
Information Transfer
Requirements on information transfer, which characterise the networks transfer
capabilities for transferring user data between two or more access points. These
characteristics include the following:
Connection oriented / connectionless services
Both Connection oriented and connectionless services shall be supported.
Traffic type.
It is required that the bearer service provides one of the following:
S guaranteed/constant bit rate,
S non-guaranteed/dynamically variable bit rate
S real time dynamically variable bit rate with a minimum guaranteed bit rate.
Real time and non real time applications shall be supported.
Real time video, audio and speech shall be supported. This implies the:
S ability to provide a real time stream of guaranteed bit rate, end to end delay and
delay variation.
S ability to provide a real time conversational service of guaranteed bit rate, end to
end delay and delay variation.
Non real time interactive and file transfer service shall be supported. This implies the:
S ability to support message transport with differentiation as regards QoS between
different users.
Multimedia applications shall be supported. This implies the:
S ability to support several user flows to/from one user having different traffic types
(e.g. real time, non real time)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
37
Information Transfer Characteristics
CP13_Ch3_18
Connection Oriented Services
Connectionless Services
Bearer Service must provide one of the following
Guaranteed/Constant Bit Rate
Nonguaranteed/Dynamically Variable Bit Rate
Real Time/Dynamically Variable Bit Rit With Minimum Guaranteed Bit Rate
Real Time Video, Audio and Speech
Non Real Time Interactive and File Transfer Services
Multimedia Applications
38
Traffic characteristics
It shall be possible for an application to specify its traffic requirements to the network by
requesting a bearer service with one of the following configurations
Point-to-Point
S Uni-Directional
S Bi-Directional
Symmetric
Asymmetric
Uni-Directional Point-to-Multipoint
S Multicast
S Broadcast
A multicast topology is one in which sink parties are specified before the connection is
established, or by subsequent operations to add or remove parties from the connection.
The source of the connection shall always be aware of all parties to which the connection
travels.
A broadcast topology is one in which the sink parties are not always known to the source.
The connection to individual sink parties is not under the control of the source, but is by
request of each sink party.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
39
Traffic Characteristics
CP13_Ch3_19
PointtoPoint
UniDirectional
BiDirectional
Symetric
Asymmetric
UniDirectional PointtoMultipoint
Multicast
Broadcast
310
Information Quality
Information quality characterises the bit integrity and delay requirements of the
applications.
Maximum transfer delay
Transfer delay is the time between the request to transfer the information at one access
point to its delivery at the other access point.
Delay variation
The delay variation of the information received information over the bearer has to be
controlled to support real-time services. The possible values for delay variation are not a
limited set, but a continuous range of values.
Bit error ratio
The ratio between incorrect and total transferred information bits. The possible values for
Bit error ratio are not a limited set, but a continuous range of values.
Data rate
The data rate is the amount of data transferred between the two access points in a given
period of time.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
311
Information Quality Characteristics
Error
tolerant
Error
intolerant
Conversational
(delay <<1 sec)
Interactive
Streaming
Background
(delay >10 sec)
Conversational
voice and video
Voice messaging
Streaming audio
and video
Fax
Email arrival
notification
FTP, still image,
paging
Ecommerce,
WWW browsing, Telnet,
interactive games
(delay approx 1 sec) (delay 10 sec)
CP13_Ch3_p11
Version 1 Rev 7 Supported Bit Rates
312
Supported Bit Rates
It shall be possible for one application to specify its traffic requirements to the network by
requesting a bearer service with any of the specified traffic type, traffic characteristics,
maximum transfer delay, delay variation, bit error ratios & data rates. The network should
satisfy these requirements without wasting resources on the radio and network interfaces
due to granularity limitations in bit rates.
It is possible for one mobile termination to have several active bearer services
simultaneously, each of which could be connection oriented or connectionless.
The only limiting factor for satisfying application requirements shall be the cumulative bit
rate per mobile termination at a given instant (i.e. when summing the bit rates of one
mobile terminations simultaneous connection oriented and connectionless traffic,
irrespective of the traffic being real time or non real time) in each radio environment:
S At least 144 kbits/s in rural outdoor radio environment.
S At least 384 kbits/s in urban/suburban outdoor radio environments.
S At least 2048 kbits/s in indoor/low range outdoor radio environment.
Version 1 Rev 7 Supported Bit Rates
EMOTOROLA LTD. 2003
CP13: UMTS Overview
313
Supported Bit Rates
CP13_Ch3_08
At Least 144 Kbps in Rural Outdoor Radio Environments
(<500km/h)
At Least 384 Kbps in Urban/Suburban Outdoor Radio Environments
(<100km/h)
At Least 2048 Kbps in Indoor/Low Range Outdoor Radio Environments
(<10km/h)
Version 1 Rev 7 Quality of Service

314
Quality of Service
Network Services are considered end-to-end, this means from a Terminal Equipment
(TE) to another TE. An End-to-End Service may have a certain Quality of Service (QoS)
which is provided for the user of a network service. It is the user that decides whether he
is satisfied with the provided QoS or not. To realise a certain network QoS a Bearer
Service with clearly defined characteristics and functionality is to be set up from the
source to the destination of a service. The diagram opposite illustrates the QoS classes
for UMTS.
The main distinguishing factor between these QoS classes is how delay sensitive the
traffic is: Conversational class is meant for traffic which is very delay sensitive while
Background class is the most delay insensitive traffic class.
Conversational and Streaming classes are mainly intended to be used to carry real-time
traffic flows. Interactive class and Background are mainly meant to be used by traditional
Internet applications like WWW, Email, Telnet, FTP and News. Due to looser delay
requirements, compared to conversational and streaming classes, both provide better
error rate by means of channel coding and retransmission.
Conversational Class
The most well known use of this scheme is telephony speech (e.g. GSM). But with
Internet and multimedia a number of new applications will require this scheme, for
example voice over IP and video conferencing tools. Real time conversation is always
performed between peers (or groups) of live (human) end-users. This is the only scheme
where the required characteristics are strictly given by human perception. (e.g. The real
time data flow is always aiming at a live (human) destination).
Interactive class
Interactive traffic is the other classical data communication scheme that on an overall
level is characterised by the request response pattern of the end-user. At the message
destination there is an entity expecting the message (response) within a certain time.
Round trip delay time is therefore one of the key attributes. Another characteristic is that
the content of the packets shall be transparently transferred (with low bit error rate).
Examples are: web browsing, data base retrieval, server access.
Streaming Class
This scheme is one of the newcomers in data communication, raising a number of new
requirements in both telecommunication and data communication systems. It is
characterised by the fact that the time relations (variation) between information entities
(i.e. samples, packets) within a flow shall be preserved, although it does not have any
requirements on low transfer delay. The delay variation of the end-to-end flow shall be
limited, to preserve the time relation (variation) between information entities of the
stream. When the user is looking at (listening to) real time video (audio) the scheme of
real time streams applies.
Background Task
Background traffic is one of the classical data communication schemes that on an overall
level is characterised by that the destination is not expecting the data within a certain
time. The scheme is thus more or less delivery time insensitive. Another characteristic is
that the content of the packets shall be transparently transferred (with low bit error rate).
Examples are background delivery of E-mail notification, SMS, download of databases
and reception of measurement records.
Version 1 Rev 7 Quality of Service
EMOTOROLA LTD. 2003
CP13: UMTS Overview
315
Quality of Services
CP13_Ch3_9a.ai
Quality of Service Classes
Conversational
Conversational Voice
Videophone, interactive Games
Streaming
Audio/Video Streaming, FTP
Interactive
Voice Mesaging
Web Browsing, ECommerce
Background
Email Arrival Notification
Fax
Maximum bitrate
Guaranteed bitrate
Delivery order
Maximum SDU size
SDU format information bits
SDU error ratio
Residual bit error ratio
Delivery of erroneous SDUs
Transfer Delay
Traffic Handling Priority
Allocation/Retention Priority
Still Image, Paging
Version 1 Rev 7 QoS Attributes
316
QoS Attributes
UMTS bearer service attributes describe the service provided by the UMTS network to
the user of the UMTS bearer service. A set of QoS attributes (QoS profile) specifies this
service.
Maximum bitrate (kbps)
Maximum number of bits delivered by UMTS and to UMTS at a SAP within a period of
time, divided by the duration of the period.
Guaranteed bitrate (kbps)
Guaranteed number of bits delivered by UMTS at a SAP within a period of time (provided
that there is data to deliver), divided by the duration of the period.
Delivery order (y/n)
Indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not.
Maximum SDU size (octets)
The maximum allowed SDU size.
SDU format information (bits)
List of possible exact sizes of SDUs
SDU error ratio
Indicates the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined
only for conforming traffic.
Indicates the undetected bit error ratio in the delivered SDUs. If no error detection is
requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs.
Delivery of erroneous SDUs (y/n/-)
Indicates whether SDUs detected as erroneous shall be delivered or discarded.
Transfer delay (ms)
Indicates maximum delay for 95th percentile of the distribution of delay for all delivered
SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the
time from a request to transfer an SDU at one SAP to its delivery at the other SAP.
Traffic handling priority
Specifies the relative importance for handling of all SDUs belonging to the UMTS bearer
compared to the SDUs of other bearers.
Allocation/Retention Priority
Specifies the relative importance compared to other UMTS bearers for allocation and
retention of the UMTS bearer. The Allocation/Retention Priority attribute is a subscription
attribute which is not negotiated from the mobile terminal.
Version 1 Rev 7 QoS Attributes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
317
UMTS Bearer QoS Attributes
CP13_Ch3_10a.ai
Traffic Class
Maximum bitrate
Delivery order
Maximum SDU size
SDU format information
SDU error ratio
Delivery of erroneous SDUs
Transfer delay
Guaranteed bit rate
Traffic handling priority
Allocation/Retention priority
Conversational
class
Streaming
class
Interactive
class
Background
class
X X X X
X X X X
X X X X
X X X X
X X X X
X X X X
X X X X
X
X X
X X
X X
Version 1 Rev 7 The Security Architecture
318
The Security Architecture
Five security feature groups are defined. Each of these feature groups meets certain
threats, accomplishes certain security objectives:
Network access security (I): the set of security features that provide users with secure
access to 3G services, and which in particular protect against attacks on the (radio)
access link.
Network domain security (II): the set of security features that enable nodes in the
provider domain to securely exchange signalling data, and protect against attacks on the
wireline network.
User domain security (III): the set of security features that secure access to mobile
stations.
Application domain security (IV): the set of security features that enable applications in
the user and in the provider domain to securely exchange messages.
Visibility and configurability of security (V): the set of features that enables the user to
inform himself whether a security features is in operation or not and whether the use and
provision of services should depend on the security feature.
Version 1 Rev 7 The Security Architecture
EMOTOROLA LTD. 2003
CP13: UMTS Overview
319
The Security Architecture
CP13_Ch3_12
Application
Stratum
Transport
Stratum
Home
Stratum/
Serving
Stratum
AN
(IV)
(I)
(III) (V)
(I) (I)
(I)
(II)
(I)
MT
TE USIM
User Application Provider Application
SN
HE
Version 1 Rev 7 Security and Privacy
320
Security and Privacy
User authentication:
The property that the serving network (SN) corroborates the identity of the user;
Network authentication:
The property that the user corroborates that he is connected to a serving network that is
authorised by the users HE to provide him services; this includes the guarantee that this
authorisation is recent.
Confidentiality
Cipher algorithm agreement: the property that the MS and the SN can securely
negotiate the algorithm that they shall use subsequently;
Cipher key agreement: the property that the MS and the SN agree on a cipher key that
they may use subsequently;
Confidentiality of user data: the property that user data cannot be overheard on the
radio access interface;
Confidentiality of signalling data: the property that signalling data cannot be
overheard on the radio access interface.
Data integrity
Integrity algorithm agreement: the property that the MS and the SN can securely
negotiate the integrity algorithm that they shall use subsequently;
Integrity key agreement: the property that the MS and the SN agree on an integrity key
that they may use subsequently;
Data integrity and origin authentication of signalling data: the property that the
receiving entity (MS or SN) is able to verify that signalling data has not been modified in
an unauthorised way since it was sent by the sending entity (SN or MS) and that the data
origin of the signalling data received is indeed the one claimed.
Mobile equipment identification
In certain cases, SN may request the MS to send it the mobile equipment identity of the
terminal. The mobile equipment identity shall only be sent after authentication of SN with
exception of emergency calls. The IMEI should be securely stored in the terminal.
However, the presentation of this identity to the network is not a security feature and the
transmission of the IMEI is not protected. Although it is not a security feature, it should
not be deleted from UMTS however, as it is useful for other purposes.
Version 1 Rev 7 Security and Privacy
EMOTOROLA LTD. 2003
CP13: UMTS Overview
321
Security and Privacy
S User Authentication
S Network Authentication
S Confidentiality
S Data integrity
S Mobile equipment identification
CP13_Ch3_p21
Version 1 Rev 7 Authentication and Key Agreement
322
Authentication and Key Agreement
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 users HE. In addition the USIM and the
HE keep track of counters SEQ
MS
and SEQ
HE
respectively to support network
authentication. The method was chosen in such a way as to achieve maximum
compatibility with the current GSM security architecture and facilitate migration from
GSM to UMTS. The method is composed of a challenge/response protocol identical to
the GSM 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 GSM 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.
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.
Version 1 Rev 7 Authentication and Key Agreement
EMOTOROLA LTD. 2003
CP13: UMTS Overview
323
CP13_Ch3_13a
MS SN/VLR HE/HLR
Authentication request
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
RES(i)
Compare RES(i) and XRES(i)
Compute CK(i) and IK(i) Select CK(i) and IK(i)
Distribution
authentication vectors
from HE to SN
Authentication Key
Generate
vectors AV (1 . . . n)
Version 1 Rev 7 Ciphering Algorithms
324
Ciphering Algorithms
The ciphering algorithms used in UMTS are shown on the slide opposite. As can be seen
a lot of different algorithms are active in the UMTS system. Algorithms f1 to f5 are of the
type that are used to compute numbers in use for authentication procedures, they will be
discussed in the UMTS Advanced courses.
Two very important algorithms, f8 and f9 are also shown, they have the following
functions.
F8
This algorithm will perform the ciphering function. The ciphering function is performed
either in the RLC sub-layer or in the MAC sub-layer according to the following rules:
S If a radio bearer is using a non-transparent RLC mode (AM or UM), ciphering is
performed in the RLC sub-layer.
S If a radio bearer is using the transparent RLC mode, ciphering is performed in the
MAC sub-layer (MAC-d entity).
Ciphering when applied is performed in the S-RNC and the ME and the context needed
for ciphering (CK, HFN, etc.) is only known in S-RNC and the ME.
F9
Most of the control signalling information elements that are sent between the MS and the
network are considered sensitive and must be integrity protected. Therefore a message
authentication function has been developed to solve this problem. The MS will still go
through the initial RRC connection establishment sequence and perform the set-up
security functions. After this however some signalling messages will be encoded using
the f9 algorithm. This will be the case for all RRC, MM, CC, GMM and SM Messages.
The MM procedure in the MS will be the process responsible for starting the integrity
protection procedure.
AK Anonymity Key
AKA Authentication and
key agreement
AUTN Authentication
Token
MAC The message
authentication code
included in AUTN,
computed using f1
XRES Expected Response
Version 1 Rev 7 Ciphering Algorithms
EMOTOROLA LTD. 2003
CP13: UMTS Overview
325
Ciphering Algorithms
CP13_Ch3_14
F1 Message authentication function used to compute MAC
F3 Key generating function used to compute CK
F2 Message authentication function used to compute RES and XRES
F1* Message authentication function used to compute MACS
F5* Key generating function used to compute AK in resynchronisation procedures
F5 Key generating function used to compute AK in normal procedures
F4 Key generating function used to compute IK
KLongterm secret key shared between the USIM and the AuC
F9 Signalling elements between the UE and RNC
F8 Data transfer between the UE and RNC
Version 1 Rev 7 Generation of Authentication Vectors/Tokens

326
Generation of Authentication Vectors/Tokens
Upon the receipt of the authentication data request from the VLR/SGSN, the HE may
have pre-computed the required number of authentication vectors and retrieve them from
the HLR database or may compute them on demand. The HE/AuC sends an
authentication response back to the VLR/SGSN that contains an ordered array of n
authentication vectors AV(1..n). The diagram opposite shows the generation of an
authentication vector AV by the HE/AuC.
SQN and RAND
The HE/AuC starts with generating a fresh sequence number SQN and an unpredictable
challenge RAND. SQNs are unique to each user (the HE/AuC keeps a counter: SQN
He

for each user) and are generated in batches, with a time stamp derived from a clock
giving universal time. RAND is a randomly generated number.
Authentication Key Management Field
An authentication and key management field AMF is used as a third input variable to the
algorithms and is also included in the authentication token of each authentication vector.
AMF may be used by the operator to switch functions in the USIM (e.g to indicate the
algorithm and key used to generate a particular authentication vector, or set the number
of entries in a Sequence list (the list size)
Algorithms f1 f5
Subsequently the following values are computed using the various algorithms (f1 f5):
<bs>A message authentication code MAC = f1
K
(SQN || RAND || AMF) where f1 is a
message authentication function.
An expected response XRES = f2
K
(RAND) where f2 is a (possibly truncated) message
authentication function.
A cipher key CK = f3
K
(RAND) where f3 is a key generating function.
An integrity key IK = f4
K
(RAND) where f4 is a key generating function.
An anonymity key AK = f5
K
(RAND) where f5 is a key generating function.<be>
AUTN and AV
Finally the authentication token (AUTN = SQN AK || AMF || MAC) and the
authentication Vector (AV:=RAND||XRES||CK||IK||MAC) are constructed from the
products of the algorithms.

Here, AK is an anonymity key used to conceal the sequence number as the latter may
expose the identity and location of the user. The concealment of the sequence number is
to protect against passive attacks only. If no concealment is needed then f5 0 (AK =
0).
Version 1 Rev 7 Generation of Authentication Vectors/Tokens
EMOTOROLA LTD. 2003
CP13: UMTS Overview
327
Generation of Authentication Vectors/Tokens
CP13_Ch3_14a
Generate SQN
Generate RAND
f1
AMF
SQN
RAND
K
AUTN := SQN AK || AMF || MAC
AV := RAND || XRES || CK || IK || AUTN
MAC XRES CK IK AK
f2 f3 f4 f5
Version 1 Rev 7 USIM Authentication Function
328
USIM Authentication Function
The VLR/SGSN invokes the procedure by selecting the next unused authentication
vector from the ordered array of authentication vectors in the VLR/SGSN database. The
VLR/SGSN sends to the USIM the random challenge RAND and an authentication token
for network authentication AUTN from the selected authentication vector.
Upon receipt the user proceeds as shown in the diagram opposite.
Retrieval of SQN
Upon receipt of RAND and AUTN the USIM first computes the anonymity key AK = f5
K
(RAND) and retrieves the sequence number SQN = (SQN AK) AK.
Computation of X-MAC
Next the USIM computes XMAC = f1
K
(SQN || RAND || AMF) and compares this with
MAC which is included in AUTN. If they are different, the user sends user authentication
reject back to the VLR/SGSN with an indication of the cause and the user abandons the
procedure. In this case, VLR/SGSN shall initiate an Authentication Failure Report
procedure towards the HLR. VLR/SGSN may also decide to initiate a new identification
and authentication procedure towards the user.
Verification of SQN
Next the USIM verifies that the received sequence number SQN is in the correct range.
If the USIM considers the sequence number to be not in the correct range, it sends
synchronisation failure back to the VLR/SGSN including an appropriate parameter, and
abandons the procedure.
If the sequence number is considered to be in the correct range however, the USIM
computes RES = f2
K
(RAND) and includes this parameter in a user authentication
response back to the VLR/SGSN.
Computation of CK and IK
Finally the USIM computes the cipher key CK = f3
K
(RAND) and the integrity key IK =
f4
K
(RAND). USIM shall store original CK, IK until the next successful execution of AKA.
User Authentication Response
Upon receipt of user authentication response the VLR/SGSN compares RES with the
expected response XRES from the selected authentication vector. If XRES equals RES
then the authentication of the user has passed. The VLR/SGSN also selects the
appropriate cipher key CK and integrity key IK from the selected authentication vector.
If XRES and RES are different, VLR/SGSN shall initiate an Authentication Failure Report
procedure towards the. VLR/SGSN may also decide to initiate a new identification and
authentication procedure towards the user.
Version 1 Rev 7 USIM Authentication Function
EMOTOROLA LTD. 2003
CP13: UMTS Overview
329
USIM Authentication Function
CP13_Ch3_15a
f1
SQN AK
RAND
K
Verify MAC = XMAC
Verify that SQN is in the correct range
XMAC RES CK IK
AK
f2 f3 f4
f5
AUTN
SQN
AMF
MAC
(USIM)
Version 1 Rev 7 Access Link Data Integrity
330
Access Link Data Integrity
Most control signalling information elements that are sent between the MS and the
network are considered sensitive and must be integrity protected. A message
authentication function shall be applied on these signalling information elements
transmitted between the ME and the RNC.
Data integrity protection method
The diagram opposite illustrates the use of the integrity algorithm f9 to authenticate the
data integrity of a signalling message. Based on the input parameters the user computes
message authentication code for data integrity MAC-I using the integrity algorithm f9. The
MAC-I is then appended to the message when sent over the radio access link. The
receiver computes XMAC-I on the message received in the same way as the sender
computed MAC-I on the message sent and verifies the data integrity of the message by
comparing it to the received MAC-I.
Input parameters to the integrity algorithm
COUNT-I
The integrity sequence number COUNT-I is 32 bits long. There is one COUNT-I value
per logical signalling channel. COUNT-I is derived from a count of the number of RRC
SDUs send/received.
IK
The integrity key IK is 128 bits long. There may be one IK for CS connections (IK
CS
) and
one IK for PS connections (IK
PS
). IK is established during UMTS AKA as the output of
the integrity key derivation function f4.
FRESH
The network-side nonce FRESH is 32 bits long. There is one FRESH parameter value
per user. The input parameter FRESH protects the network against replay of signalling
messages by the user. At connection set-up the RNC generates a random value FRESH
and sends it to the user in the (RRC) security mode command. The value FRESH is
subsequently used by both the network and the user throughout the duration of a single
connection. This mechanism assures the network that the user is not replaying any old
MAC-Is.

DIRECTION
The direction identifier DIRECTION is 1 bit long. The direction identifier is input to avoid
the use of identical set of input parameter values up-link and down-link messages. The
value of the DIRECTION is 0 for messages from UE to RNC and 1 for messages from
RNC to UE.
MESSAGE
The signalling message itself with the radio bearer identity. The latter is appended in front
of the message. Note that the radio bearer identity is not transmitted with the message
but it is needed to avoid that for different instances of message authentication codes the
same set of input parameters is used.
Version 1 Rev 7 Access Link Data Integrity
EMOTOROLA LTD. 2003
CP13: UMTS Overview
331
Access Link Data Integrity
CP13_Ch3_16a
COUNTI
MESSAGE
DIRECTION
FRESH
f9
MACI
Sender
UE or RNC
COUNTI
MESSAGE
DIRECTION
FRESH
f9
XMACI
Receiver
RNC or UE
IK
IK
Version 1 Rev 7 Ciphering of User/Signalling Data
332
Ciphering of User/Signalling Data
User data and some signalling information elements are considered sensitive and must
be confidentiality protected. To ensure identity confidentiality the temporary user identity
(P-)TMSI must be transferred in a protected mode at allocation time and at other times
when the signalling procedures permit it.
These needs for a protected mode of transmission are fulfilled by a confidentiality
function which is applied on dedicated channels between the ME and the RNC.

The diagram opposite illustrates the use of the ciphering algorithm f8 to encrypt plaintext
by applying a keystream using a bit per bit binary addition of the plaintext and the
ciphertext. The plaintext may be recovered by generating the same keystream using the
same input parameters and applying a bit per bit binary addition with the ciphertext.
Input parameters to the cipher algorithm
COUNT-C
The integrity sequence number COUNT-C is 32 bits long. There is one COUNT-C value
per logical signalling channel. COUNT-C is derived from a count of the number of
RLC/MAC SDUs send/received.
CK
The Cipher key CK is 128 bits long. There may be one CK for CS connections (CK
CS
)
and one CK for PS connections (CK
PS
). CK is established during UMTS AKA as the
output of the integrity key derivation function f3.
BEARER
The radio bearer identifier BEARER is 5 bits long.
There is one BEARER parameter per radio bearer associated with the same user and
multiplexed on a single 10ms physical layer frame. The radio bearer identifier is input to
avoid that for different keystream an identical set of input parameter values is used.
DIRECTION
The direction identifier DIRECTION is 1 bit long. The direction identifier is input to avoid
the use of identical set of input parameter values up-link and down-link messages. The
value of the DIRECTION is 0 for messages from UE to RNC and 1 for messages from
RNC to UE.
LENGTH
The length indicator LENGTH is 16 bits long. The length indicator determines the length
of the required keystream block. LENGTH shall affect only the length of the
KEYSTREAM BLOCK, not the actual bits in it.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
333
Ciphering of User/Signalling Data
CP13_Ch3_17
Sender
UE or RNC
Receiver
RNC or UE
COUNTC
BEARER
DIRECTION
LENGTH
f8 CK
COUNTC
BEARER
DIRECTION
LENGTH
f8 CK
KEYSTREAM
BLOCK
PLAINTEXT
BLOCK
KEYSTREAM
BLOCK
CYPHERTEXT
BLOCK
334
EMOTOROLA LTD. 2003
CP13: UMTS Overview
41
Chapter 4
UMTS Protocols
Version 1 Rev 7
42
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
43
Chapter 4
UMTS Protocols 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to UMTS Protocols 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Stratum 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Non-Access Stratum 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Protocol Model 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horizontal Layers 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vertical Planes 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IuCS Protocol Structure 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IuPS Protocol Structure 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Iub Protocol Structure 410 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Iur Protocol Structure 412 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Interface Protocol Architecture 414 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Layer Functions 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping between logical and Transport channels 416 . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport format selection 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Priority handling of Data Flows 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Scheduling 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identification of UEs on Common Channels 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MUX/DEMUX of PDUs into Transport Blocks 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic Volume Monitoring 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Transport Channel Type Switching 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ciphering 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Service Class Selection 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RLC Protocol 420 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC Functions 422 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol Stacks 426 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Plane Protocol Stack (Dedicated Channels CS-Domain) 426 . . . . . . . . . . . . . . .
Dedicated Channel Frame Protocol (DCH FP) 428 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Plane Protocol Stack (UE-CN SIGNALLING, Dedicated Channels, CS-Domain) . . . . . . .
430
RANAP Services 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCCP 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP3-B 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAAL-NNI 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
44
(UE-CN Signalling, Shared Channels, CS-Domain) 432 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH/FACH/ DSCH Frame Protocol 432 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Plane Protocol Stack
(Dedicated Channels, PS-Domain) 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS Tunnelling Protocol, User Plane (GTP-U) 434 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path Protocols 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(UE-CN Signalling, Dedicated Channels, PS-Domain) 436 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stream Control Transmission Protocol 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M3UA 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2003
CP13: UMTS Overview
41
Objectives
S Describe the General Protocol Model for UMTS.
S Describe the Interface specific protocol structure for the following interfaces:
lu CS
lu PS
lu b
lu r
S Describe the Radio Interface Protocol Architecture
S Describe the functions and service provided by the following Radio Interface
Protocols:
Medium Access Control (MAC)
Radio Link Control (RLC)
Packet Data Convergence Protocol (PDCP)
Broadcast Multicast (BMC)
Radio Resource Control (RRC)
S Describe selected end-to-end protocol stacks
Version 1 Rev 7 Introduction to UMTS Protocols
42
Introduction to UMTS Protocols
As has been outlined in previous chapters, one of the underlying principles in the design
and development of UMTS is to prepare a universal infrastructure able to carry both
existing and future services. All design work should be such that technological and
evolution changes in one part of the network should have no (or at least minimal impact
on other network components or services.
From a protocol perspective, this is acheived by confining , as far as is reasonably
practicable, protocol functions and services within on or several physical domains. To
this end, the 3G protocol arch itecture can be divided into two strata.
S Access Stratum
S Non-Access Stratum
Access Stratum
The Access Startum (AS) is a functional entity that encompasses radio protocols
between the UE and the UTRAN and, terrestrial interface (Iu) protocols between the
UTRAN and the Core Network (CN). These protocols all terminate within the UTRAN.
Non-Access Stratum
The Non-access Stratum (NAS) includes CN protocols that form a direct connection
between the UE and the CN itself. The NAS is transparent to the UTRAN and thus these
protocols do not terminate in the UTRAN.
The NAS protocols encompass functions such as; Mobility Management (MM), Call
Control (CC), Short Message Services (SMS) and Suplementary Services (SS)
associated with the circuit switched CN and, GPRS Mobility Management (GMM),
Session Managment (SM) and GPRS SMS assocoiated with the packet switched CN.
The NAS tries to remain independent of the underlying radio technology. Thus the NAS
protocols can remain unchanged regardless of the radio access network (RAN) that
carries them
Version 1 Rev 7 Introduction to UMTS Protocols
EMOTOROLA LTD. 2003
CP13: UMTS Overview
43
UMTS Protocol Architecture
CP13_Ch4_00
Core
Network
Protocols
Core
Network
Protocols
Radio
Protocols
Radio
Protocols
Iu
Protocols
Iu
Protocols
Access Stratum
NonAccess Stratum
UE
UTRAN
Core Network
UuInterface
IuInterface
Version 1 Rev 7 General Protocol Model
44
General Protocol Model
The Protocols in the UTRAN are designed according to a set protocol model. The
structure consists of Layers (Horizontal) and Planes (Vertical). All these entities are
independent of each other and can be changed at any time. It is also important to note
that these protocol stacks are not developed for specific entities e.g. BTS or Node-B etc,
but rather for the interfaces between these different entities. Lets have a closer look at
the Layers and Planes.
Horizontal Layers
The General protocol stack only consists of two layers, the Transport Network Layer and
the Radio Network Layer. From the bottom, the Physical layer (Part of the Transport
Network Layer) will provide the physical medium for transmission. Above the Physical
layer is the Transport layer (Part of the Transport Network Layer) which contains the
transport protocols. These protocols are not defined within the UMTS specifications. The
Transport Network Protocol proposed for UMTS is ATM. The top layer is called the Radio
Network layer, this is the layer responsible for all UTRAN related tasks. The tasks
performed on Radio Network Layer are transparent to Transport Network Layer.
Vertical Planes
Control Plane
The Control plane only exists on L3 of the Horizontal planes and is responsible for all
UMTS specific signalling. The protocols used for the control plane are the RANAP
protocol for the Iu interface, the RNSAP protocol for the Iur interface and the NBAP
protocol for the Iub interface. These are all termed Application protocols and will be used
for tasks like setting up bearers to the UE. Operation & Maintenance actions will always
set up the signalling Bearers for the Application protocol.
User Plane
This plane is being used for transfer of all kinds of information e.g. multimedia, e-mail,
speech etc. The User Plane consists of the Data Stream that will be transported on the
Data Bearer. Each Data Stream is identified and characterised by one or more frame
protocols.
Transport Network Control Plane
This plane is used for all signalling that must be transferred in the Transport Layer and
does not include any Radio Network Layer information. The protocol used for the Control
Plane is called Access Link Control Application Protocol (ALCAP). This protocol will
handle the setting up of Data Bearers for the User Plane of the Transport layer. The
introduction of the ALCAP protocol made it possible for the Application Protocols to run
with complete independence of the data bearing technology. It should be noted that we
shall not use the ALCAP protocol in the setting up of the Signalling Bearers for the
Application Protocols or for ALCAP.
Transport Network User Plane
Both the Signalling Bearer (for Applicatio Protocol) in the Control Plane and the Data
Bearer in the User Plane belong to the Transport Network Layer. The Data bearers in the
Transport Network User Plane are directly controlled by the Transport Network Control
Plane during real time operations. The control of the Signalling Bearer(s) for Application
Protocol are considerede Operations and Maintainance functions.
Version 1 Rev 7 General Protocol Model
EMOTOROLA LTD. 2003
CP13: UMTS Overview
45
General Protocol Model
CP13_Ch4_01
Radio
Network
Layer
Transport
Network
Layer
Control Plane
Application
Protocol
Signalling
Bearer(s)
Transport Network
Control Plane
ALCAP(S)
Signalling
Bearer(s)
User Plane
Data
Stream(s)
Data
Bearer(s)
Physical Layer
Transport Network
User Plane
Transport Network
User Plane
Version 1 Rev 7 IuCS Protocol Structure
46
IuCS Protocol Structure
As can be seen form the IuCS protocol stack, it resembles the UMTS Protocol Model
very closely and so it will be the case for all other Interfaces. Two different layers can be
detected, the Transport Network Layer and the Radio Network Layer. The Physical layer
in the Transport Network Layer consist of normal OSI L1 specified protocols like E1,
STM, Fibre Optic or even Microwave. On OSI L2 is the ATM protocol, one thing to note is
that the first two layers will form a common bearer for all three planes above.
The Protocol used on the radio Network Layer is called Radio Access Network
Application Part (RANAP). This protocol will run on top of Broad Band SS7 protocols.
The function of this protocol includes the following:
S SRNS relocation and Hard Handover procedures
S Radio Access Bearer (RAB) Management. (Set-up, Maintenance and Clearing)
S Reporting of unsuccessful data transfer for Charging Applications
S Common ID Management
S Paging of the UEs
S Transparent UE to CN transfers.
S Security Mode Control with integrity checking.
S Overload Management.
S Management of reset procedures.
S Location Management and Reporting.
On the Transport Network Layer the following protocols can be seen:
SCCP Signalling Connection Control Part
MTP3-b Message Transfer Part - Broadband
SAAL-NNI Signalling ATM Adaptation Layer for Network
to Network Interfaces
SSCF Service Specific Co-ordination functions
SSCOP Service Specific Connection Orientated
Protocol
AAL5 ATM Adaptation Layer 5
Transport Network Control Plane Protocol Stack
The Transport Network Protocol Stack consists of Signalling protocols for setting up of
the AAL2 Connections in the User Plane. Again broad band SS7 signalling protocols are
being used.
This is a very simple combination of protocols with the User plane being directly on top of
AAL2, which is responsible for segmenting the data to ATM cells. Note that a dedicated
AAL2 connection will be reserved for each users CS service.
Version 1 Rev 7 IuCS Protocol Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
47
IuCS Protocol Structure
CP13_Ch4_02
Radio
Network
Layer
Transport
Network
Layer
Control Plane
RANAP
Transport Network
Control Plane
AAL5
User Plane
Iu UP Protocol
Layer
Physical Layer
SCCP
MTP3b
SSCFNNI
SSCOP
ATM
AAL5
SSCFNNI
MTP3b
Q.2150.2
SSCOP
Q.2630.1
AAL2
Transport Network
User Plane
Transport Network
User Plane
Version 1 Rev 7 IuPS Protocol Structure
48
IuPS Protocol Structure
Again, two different layers can be detected, the Transport Network Layer and the Radio
Network Layer. The Physical layer in the Transport Network Layer consist of normal OSI
L1 specified protocols like E1, STM, Fibre Optic or even Microwave.
The Protocol used on the Radio Network Layer is again RANAP and the functions are
the same then for the IuCS.
The broad band SS7 part of the Transport Network will stay the same. We will however,
have additional protocols that could be used. These are the IP based signalling bearer for
packet switched information.
M3UA SS7 and MTP3b User Adaptation Layer
SCTP Stream Control Transmission Protocol (Designed for
signalling transport in the Internet)
IP Internet Protocol
This Plane is not applied to the IuPS.
Normal GPRS Tunnelling Protocol (GTP) tunnelling will be used over User Datagram
Protocol (UDP) which is a connectionless protocol. Multiple packets and flows will be
multiplexed on one or more AAL.
Version 1 Rev 7 IuPS Protocol Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
49
IuPS Protocol Stack
CP13_Ch4_03
Radio
Network
Layer
Transport
Network
Layer
Control Plane
RANAP
Transport Network
Control Plane
AAL5
User Plane
Iu UP Protocol
Layer
SSCOP
AAL5
Transport Network
User Plane
Transport Network
User Plane
Physical Layer
ATM
Physical Layer
IP
UDP
GTPU
SSCFNNI
ATM
IP
M3UA
SCCP
MTP3b
SCTP
Version 1 Rev 7 Iub Protocol Structure
410
Iub Protocol Structure
As with the Iu interface, two different layers can be detected, the Transport Network
Layer and the Radio Network Layer. The Physical layer in the Transport Network Layer
consist of normal OSI L1 specified protocols like E1, STM, Fibre Optic or even
Microwave. On OSI L2 is the ATM protocol, one thing to note is that the first two OSI
layers will form a common bearer for all three planes above.
The Protocol used on the radio Network Layer is called NBAP. This protocol is in turn
divided into the Common NBAP (C-NBAP) and Dedicated NBAP (D-NBAP). The
C-NBAP defines all common procedures carried out like Operations & Maintenance task
through channels like Random Access Channel (RACH) and PAging Channel (PCH).
The main functions of C-NBAP are:
S Setting up of the Radio Link to the UE
S Selection of the Traffic termination point
S Cell Configuration
S Fault management
S Handling of the Common Transport Channels
S Reporting and Initialization of Node-B and/or Cell specific measurements
The main functions of D-NBAP are:
S Set-up, release and reconfiguration of radio links for the UE Context
S Softer Combining Management
S Compressed Mode Control
S Dedicated and Shared channel Management
S Reporting and Initialisation of Radio link specific measurement
S Downlink Power Drifting Correction
S Radio link Fault Management
Again the usage of broad band SS7 signalling can be seen.
The User Plane Protocol Stack consists of all the Control and User frame protocols being
used in order to pass the information on to the Node-B and then finally the UE. Three
basic type of transmissions are defined. Transparent, Unacknowledged or
Acknowledged. The lower layers is a simple combination of protocols with the User plane
being directly on top of AAL2 which is responsible for segmenting the data to ATM cells.
Version 1 Rev 7 Iub Protocol Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
411
Iub Protocol Stack
CP13_Ch4_04
Radio
Network
Layer
Transport
Network
Layer
Radio Network
Control Plane
NBAP
Transport Network
Control Plane
AAL5
User Plane
Physical Layer
SSCFUNI
SSCOP
ATM
AAL5
SSCFUNI
Q.2150.2
Q.2630.1
SSCOP
AAL2
D
C
H

F
P
R
A
C
H

F
P
F
A
C
H

F
P
P
C
H

F
P
D
S
C
H

F
P
U
S
C
H

F
P
C
P
C
H

F
P
Version 1 Rev 7 Iur Protocol Structure
412
Iur Protocol Structure
The Iur was originally developed to support Soft Handovers, but has since been changed
to have 4 main distinct functions that will be discussed in this section. Again two different
layers can be detected, the Transport Network Layer and the Radio Network Layer. The
Physical layer in the Transport Network Layer consist of normal OSI L1 specified
protocols like E1, STM, Fibre Optic or even Microwave. On OSI L2 is the ATM protocol,
one thing to note is that the first two layers will form a common bearer for all three planes
above.
The Protocol used on the radio Network Layer is called RNSAP, this protocol could run
on Broad Band SS7 protocols or IP based signalling. The 4 main functions of this
protocol include the following:
S Support for basic Inter RNC Mobility
S Support for Dedicated Channel Traffic
S Support for Common Channel Traffic
S Support of Global Resource Management
The Transport Network Protocol Stack is more complex than any other interface. This is
mainly due to 4 different uses as specified above. Signalling and Data will be carried
between different Node-Bs on either broad band SS7 Interfaces or IP based Interfaces.
This is a very simple combination of protocols with the User plane being directly on top of
AAL2, which is responsible for segmenting the data to ATM cells.
Version 1 Rev 7 Iur Protocol Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
413
Iur Protocol Stack
CP13_Ch4_05
Radio
Network
Layer
Transport
Network
Layer
Control Plane
RNSAP
Transport Network
Control Plane
User Plane
DCH
FP
AAL2
Transport Network
User Plane
ATM
Physical Layer
AAL5
M3UA
SCCP
MTP3b
SSCFNNI SCTP
SSCOP IP
AAL5
Q.2150.1
M3UA MTP3b
SSCFNNI SCTP
SSCOP IP
CCH
FP
Q.2630.1
Transport Network
User Plane
Version 1 Rev 7 Radio Interface Protocol Architecture
414
Radio Interface Protocol Architecture
The radio interface is layered into three protocol layers:
S The physical layer (L1);
S The data link layer (L2);
S The network layer (L3).
Layer 1 provides the Physical layer service between the UTRAN and the UE and is
described in detail in later chapters
Layer 2 is split into following sublayers: Medium Access Control (MAC), Radio Link
Control (RLC), Packet Data Convergence Protocol (PDCP) and Broadcast/Multicast
Control (BMC).
Layer 3 and RLC are divided into Control (C-) and User (U-) planes. PDCP and BMC
exist in the U-plane only.
In the C-plane, Layer 3 is partitioned into sublayers where the lowest sublayer, denoted
as Radio Resource Control (RRC), interfaces with layer 2 and terminates in the UTRAN.
The next sublayer provides Duplication avoidance. It terminates in the CN but is part of
the Access Stratum; it provides the Access Stratum Services to higher layers. The higher
layer signalling such as Mobility Management (MM) and Call Control (CC) are assumed
to belong to the non-access stratum.
The diagram opposite shows the radio interface protocol architecture. Each block in
represents an instance of the respective protocol. Service Access Points (SAP) for
peer-to-peer communication are marked with circles at the interface. The SAP between
MAC and the physical layer provides the transport channels. The SAPs between RLC
and the MAC sublayer provide the logical channels. In the C-plane, the interface between
Duplication avoidance and higher L3 sublayers (CC, MM) is defined by the General
Control (GC), Notification (Nt) and Dedicated Control (DC) SAPs.
Also shown in the figure are connections between RRC and MAC as well as RRC and L1
providing local inter-layer control services. An equivalent control interface exists between
RRC and the RLC sublayer, between RRC and the PDCP sublayer and between RRC
and BMC sublayer. These interfaces allow the RRC to control the configuration of the
lower layers. For this purpose separate Control SAPs are defined between RRC and
each lower layer (PDCP, RLC, MAC, and L1).
Version 1 Rev 7 Radio Interface Protocol Architecture
EMOTOROLA LTD. 2003
CP13: UMTS Overview
415
Radio Interface Protocol Architecture
CP13_Ch4_06
L3
L2/PDCP
L2/BMC
L2/RLC
L2/MAC
L1 PHY
PDCP
PDCP
RLC
BMC
RRC
RLC
MAC
RLC
RLC
RLC
RLC
RLC
RLC
c
o
n
t
r
o
l
c
o
n
t
r
o
l
c
o
n
t
r
o
l
control
Logical
Channels
Transport
Channels
c
o
n
t
r
o
l
Duplication avoidance
GC Nt DC
Cplane signalling Uplane information
GC Nt DC
UuS boundary
Version 1 Rev 7 MAC Layer Functions
416
MAC Layer Functions
Mapping between logical and Transport channels
The MAC layer performs cross mapping of information between logical channels (to/from
higher level protocols) and the appropriate transport channel, according to the type of
information to be transferred. Logical and transport channel types are covered in more
detail in a later chapter.
Transport format selection
MAC will select the most appropriate Transport format (from the transport format
combination set) for each transport channel, depending upon the instantaneous source
rate.
Priority handling of Data Flows
Priority handling of data flows of a single UE using multiple Services, is achieved by
selecting the most appropriate high or low bit rate formats for the respective service.
Dynamic Scheduling
Under certain circumstances UEs may use common or shared transport channels to
receive data in the downlink. Use of these shared resources is dynamically scheduled by
the MAC-sh layer according the UEs QoS requirements.
Identification of UEs on Common Channels
When a common transport channel carries data from dedicated-type logical channels, the
MAC-sh will identify the source or destination UE by including a Radio Network
Temporary Identifier (RNTI) in the MAC header.
MUX/DEMUX of PDUs into Transport Blocks
MAC handles the service multiplexing for both common and dedicated transport
channels. However, it should be noted that MAC multiplexing of dedicated channels can
only be performed for services with the same QoS parameters, while physical layer
multiplexing makes it possible to multiplex any type of service, including those with
different QoS parameters.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
417
MAC Layer Functions
S Mapping of Logical Channels to transport Channels
S Transport Format Selection
S Priority Handling of Data Flows of one UE
S Priority Handling of Handling Between UEs by Dynamic Scheduling
S Identification of UEs on Common Channels
S MUX/DEMUX of Higher Layer PDUs Into/ Transport Blocks
S Traffic Volume Monitoring
S Dynamic Transport Channel Switching
S Ciphering (Transport RLC Mode Only)
S Access Service Class Selection
CP13_Ch4_p17
418
Traffic Volume Monitoring
MAC receives RLC PDUs together with status information on the amount of data in the
RLC buffer. MAC compares the amount of status corresponding to a transport channel
with the thresholds set by RRC. If the amount of data is too high or too low, MAC sends
a traffic volume status measurement to RRC. RRC uses these reports to trigger
reconfiguration of the Radio Bearers/Transport channels.
Dynamic Transport Channel Type Switching
Based upon a switching decision received from RRC, MAC is able to execute switching
of data flows between common and dedicated transport channels.
Ciphering
The MAC-D entity performs ciphering if a logical channel is using transparent RLC mode.
Ciphering is an XOR function where data is XORed with a ciphering mask produced by a
ciphering algorithm.
Access Service Class Selection
UEs are allocated to one of eight Access Service Classes, to provide different priorities
for service resources. MAC indicates the ASC associated with a PDU received from the
physical layer.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
419
MAC Layer Functions
S Mapping of Logical Channels to transport Channels
S Transport Format Selection
S Priority Handling of Data Flows of one UE
S Priority Handling of Handling Between UEs by Dynamic Scheduling
S Identification of UEs on Common Channels
S MUX/DEMUX of Higher Layer PDUs Into/ Transport Blocks
S Traffic Volume Monitoring
S Dynamic Transport Channel Switching
S Ciphering (Transport RLC Mode Only)
S Access Service Class Selection
CP13_Ch4_p17
Version 1 Rev 7 RLC Protocol
420
RLC Protocol
The radio link control (RLC) protocol provides segmentation and retransmission services
for both user and control data
The diagram opposite gives an overview model of the RLC layer. The figure illustrates
the different RLC peer entities. Each RLC instance is configured by RRC to operate in
one of three modes
S Transparent Mode (Tr)
S Unacknowledged Mode (UM)
S Acknowledged Mode (AM)
The mode to be used is determined by the SAP into which the higher layer deliver their
PDUs. The mode chosen indicates which services and functions are to be applied and
what (if any) response will be passed to higher level protocols regarding error detection.
For all RLC modes, CRC error detection is performed by the physical layer and the result
of the CRC check is delivered to RLC together with the actual data.
Version 1 Rev 7 RLC Protocol
EMOTOROLA LTD. 2003
CP13: UMTS Overview
421
RLC Protocol Model
CP13_Ch04_08
TrSAP UMSAP AMSAP
UMSAP
TrSAP
AMEntity
Transmit
TrEntity
Transmit
UMEntity
Receive
TrEntity
Receive
UMEntity
Transmitting Side Receiving Side
Version 1 Rev 7 RRC Functions
422
RRC Functions
The Radio Resource Control (RRC) layer handles the control plane signaling of Layer 3
between the UEs and UTRAN. The RRC performs the following functions:
Broadcast of information provided by the non-access stratum (Core
Network)
The RRC layer performs system information broadcasting from the network to all UEs.
The system information is normally repeated on a regular basis. The RRC layer performs
the scheduling, segmentation and repetition. This function supports broadcast of higher
layer (above RRC) information. This information may be cell specific or not. As an
example RRC may broadcast Core Network location service area information related to
some specific cells.
Broadcast of information related to the access stratum
The RRC layer performs system information broadcasting from the network to all UEs.
The system information is normally repeated on a regular basis. The RRC layer performs
the scheduling, segmentation and repetition. This function supports broadcast of typically
cell-specific information.
Establishment, re-establishment, maintenance and release of an
RRC connection between the UE and UTRAN
The establishment of an RRC connection is initiated by a request from higher layers at
the UE side to establish the first Signaling Connection for the UE. The establishment of
an RRC connection includes an optional cell re-selection, an admission control, and a
layer 2 signaling link establishment. The release of an RRC connection can be initiated
by a request from higher layers to release the last Signaling Connection for the UE or by
the RRC layer itself in case of RRC connection failure. In case of connection loss, the UE
requests re-establishment of the RRC connection. In case of RRC connection failure,
RRC releases resources associated with the RRC connection.
Establishment, reconfiguration and release of Radio Bearers
The RRC layer can, on request from higher layers, perform the establishment,
reconfiguration and release of Radio Bearers in the user plane. A number of Radio
Bearers can be established to an UE at the same time. At establishment and
reconfiguration, the RRC layer performs admission control and selects parameters
describing the Radio Bearer processing in layer 2 and layer 1, based on information from
higher layers.
Assignment, reconfiguration and release of radio resources for the
RRC connection
The RRC layer handles the assignment of radio resources (e.g. codes, CPCH channels)
needed for the RRC connection including needs from both the control and user plane.
The RRC layer may reconfigure radio resources during an established RRC connection.
This function includes coordination of the radio resource allocation between multiple radio
bearers related to the same RRC connection. RRC controls the radio resources in the
uplink and downlink such that UE and UTRAN can communicate using unbalanced radio
resources (asymmetric uplink and downlink). RRC signals to the UE to indicate resource
allocations for purposes of handover to GSM or other radio systems.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
423
RRC Functions
S Broadcast of information related to the non-access stratum (Core
Network)
S Broadcast of information related to the access stratum
S Establishment, maintenance and release of an RRC connection
between the UE and UTRAN
S Establishment, reconfiguration and release of Radio Bearers
S Assignment, reconfiguration and release of radio resources for the
RRC connection
S RRC connection mobility functions
S Control of requested QoS
S UE measurement reporting and control of the reporting
S Outer loop power control
S Control of ciphering
S Slow Dynamic Channel Allocation (TDD mode)
S Paging
S Initial cell selection and cell re-selection
S Arbitration of radio resources on uplink DCH
S RRC message integrity protection
S Timing advance (TDD mode)
S CBS control.
CP13_Ch4_p23
424
RRC connection mobility functions
The RRC layer performs evaluation, decision and execution related to RRC connection
mobility during an established RRC connection, such as handover, preparation of
handover to GSM or other systems, cell re-selection and cell/paging area update
procedures, based on e.g. measurements done by the UE.
Paging/notification
The RRC layer can broadcast paging information from the network to selected UEs.
Higher layers on the network side can request paging and notification. The RRC layer
can also initiate paging during an established RRC connection.
Routing of higher layer PDUs
This function performs at the UE side routing of higher layer PDUs to the correct higher
layer entity, at the UTRAN side to the correct RANAP entity.
Control of requested QoS
This function shall ensure that the QoS requested for the Radio Bearers can be met. This
includes the allocation of a sufficient number of radio resources.
UE measurement reporting and control of the reporting
The measurements performed by the UE are controlled by the RRC layer, in terms of
what to measure, when to measure and how to report, including both UMTS air interface
and other systems. The RRC layer also performs the reporting of the measurements
from the UE to the network.
Outer loop power control
The RRC layer controls setting of the target of the closed loop power control.
Control of ciphering
The RRC layer provides procedures for setting of ciphering (on/off) between the UE and
UTRAN.
Arbitration of radio resources on uplink DCH
This function controls the allocation of radio resources on uplink DCH on a fast basis,
using a broadcast channel to send control information to all involved users.
Note: This function is implemented in the CRNC.
Initial cell selection and re-selection in idle mode
Selection of the most suitable cell based on idle mode measurements and cell selection
criteria.
Integrity protection
This function adds a Message Authentication Code (MAC-I) to those RRC messages that
are considered sensitive and/or contain sensitive information.
Allocation of radio resources for CBS
This function allocates radio resources for CBS based on traffic volume requirements
indicated by BMC. The radio resource allocation set by RRC (i.e. the schedule for
mapping of CTCH onto FACH/S-CCPCH) is indicated to BMC to enable generation of
schedule messages. The resource allocation for CBS shall be broadcast as system
information.
Configuration for CBS discontinuous reception
This function configures the lower layers (L1, L2) of the UE when it shall listen to the
resources allocated for CBS based on scheduling information received from BMC.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
425
RRC Functions
S Broadcast of information related to the non-access stratum (Core
Network)
S Broadcast of information related to the access stratum
S Establishment, maintenance and release of an RRC connection
between the UE and UTRAN
S Establishment, reconfiguration and release of Radio Bearers
S Assignment, reconfiguration and release of radio resources for the
RRC connection
S RRC connection mobility functions
S Control of requested QoS
S UE measurement reporting and control of the reporting
S Outer loop power control
S Control of ciphering
S Slow Dynamic Channel Allocation (TDD mode)
S Paging
S Initial cell selection and cell re-selection;
S Arbitration of radio resources on uplink DCH
S RRC message integrity protection
S Timing advance (TDD mode)
S CBS control.
CP13_Ch4_p23
Version 1 Rev 7 Protocol Stacks
426
Protocol Stacks
The following pages construct the protocol stacks for each UMTS network entity. The
exact protocol structure is dependent upon which Core Network domain (CS or PS) is
providing the Bearer Service, and whether the information transfer is user plane or
control plane.
User Plane Protocol Stack (Dedicated Channels CS-Domain)
The diagram opposite shows the User plane protocol stack for user plane data transfer,
using dedicated channels via the CN-PS. The user CS payload will be received at the
MSC from the external network (e.g. the PSTN. The protocols used the transfer the
Payload across this interface may vary and are not described in this document. AAL,
ATM and Physical layers will be described in detail in later chapters.
Iu UP Frame Protocol
The Iu UP protocol is located in the User plane of the Radio Network layer over the Iu
interface and is used to convey user data associated to Radio Access Bearers (RABs) .
One Iu UP protocol instance is uniquely associated to each RAB. If several RABs are
established towards one given UE, then these RABs make use of several Iu UP protocol
instances. These Iu UP instances are established, relocated and released together with
the Associated RAB.
The Iu UP Protocol is defined with modes of operation, which can be activated on a RAB
basis rather than on A CN domain or service basis. This makes the protocol
independent of the CN domain and to have limited or no dependency with the Transport
Network Layer. This provides the flexibility to evolve services regardless of the CN
domain. The Iu UP mode of operation determines if and which set of features shall be
provided. Currently two mode of operation are defined:
S Transparent Mode (TrM)
S Support modes
TrM is intended for those RAB that do not require any particular feature from the Iu UP
protocol other than transfer of user data. In this mode the, The Iu UP protocol does not
perform any peer-to-peer information transfer over the Iu interface. The Iu UP protocol
layer is crossed though by PDUs being exchanged between upper layers and the
transport network layer, no Iu UP overhead is added to the payload.
The support modes are intended for those RABs that do require particular features from
the Iu UP protocol in addition to transfer of user data. When operating in support mode,
the peer Iu UP protocol instances exchange Iu UP frames, adding overhead to the
payload. The Iu UP Support mode is prepared to support variations. However, the only
support mode currently defined in 3GPP specifications; namely Support Mode for
Predefined SDU size (SMpSDU), and provides the following functions.
S Transfer of user data;
S Initialisation
S Rate Control
S Time Alignment
S Handling of Error Events
S Frame Quality Classification
EMOTOROLA LTD. 2003
CP13: UMTS Overview
427
User Plane Protocol Stack (Dedicated Channels
CS-Domain)
CP13_Ch4_15
luUP
RLC
CS
Payload
CS
Payload
Phys
AAL2
ATM
Phys
RLC
MACd
Split/
Comb
Phys
Split/
Comb
Phys
DCH
FP
AAL2
ATM
Phys
MACd
Split/
Select
DCH
FP
AAL2
ATM
Phys
luUP
AAL2
ATM
Phys Phys
UE Node B SRNC MSC PSTN
428
Dedicated Channel Frame Protocol (DCH FP)
User data is received at the SRNC, via the transport layer and Iu UP protocol and the
passed to the Radio Interface Control protocols for RLC and MAC processing as
appropriate. The resultant Transport Blocks are delivered to the DCH FP.
DCH FP transfers DCH data frames every transmission time interval from the SRNC to
the Node B fro downlink transfer and from Node B to the SRNC for uplink transfer. An
Optional error detection mechanism may be used to protect the data transfer if needed.
At the transport channel set-up it shall be specified if the error detection on the User data
is used.
In addition to the transfer of user data, DCH FP provides the following services
S Transport of outer loop power control information between SRNC and Node B.
S Support of transport channel synchronisation mechanism.
S Support of Node Synchronisation method.
S Transfer of DSCH TFI from SRNC to Node B.
S Transfer of RX timing deviation (TDD) from the Node B to the RNC.
S Transfer of radio interface parameters from the SRNC to the Node B.
The specification of Iub DCH data streams is also valid for the Iur DCH data streams.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
429
(Dedicated Channels CS-Domain)
CP13_Ch4_16
luUP
RLC
CS
Payload
CS
Payload
Phys
AAL2
ATM
Phys
RLC
MACd
Split/
Comb
Phys
Split/
Comb
Phys
DCH
FP
AAL2
ATM
Phys
MACd
Split/
Select
DCH
FP
AAL2
ATM
Phys
luUP
AAL2
ATM
Phys Phys
UE Node B SRNC MSC PSTN
Version 1 Rev 7 Control Plane Protocol Stack (UE-CN SIGNALLING, Dedicated Channels, CS-Domain)
430
Control Plane Protocol Stack (UE-CN SIGNALLING, Dedicated
Channels, CS-Domain)
The diagram opposite illustrates the protocol stack for UE to CN signalling, when the UE
is connected to the network and operating in dedicated mode.
RANAP Services
RANAP provides the signalling service between UTRAN and the CN that is required to
fulfil the RANAP functions. RANAP services are divided into three groups based on
Service access Points.
General control services
General control services are related to the whole Iu interface instance between RNC and
logical CN domain, and are accessed in CN through the General Control SAP. They
utilise connectionless signalling transport provided by the Iu signalling bearer.
Notification services
Notification services are related to specified UEs or all UEs in specified area, and are
accessed in CN through the Notification SAP. They utilise connectionless signalling
transport provided by the Iu signalling bearer.
Dedicated control services
Dedicated control services are related to one UE, and are accessed in CN through the
Dedicated Control SAP. RANAP functions that provide these services are associated with
Iu signalling connection that is maintained for the UE in question. The Iu signalling
connection is realised with connection oriented signalling transport provided by the Iu
signalling bearer.
SCCP
SCCP provides connectionless service, class 0, connection oriented service, class 2,
separation of the connections mobile by mobile basis on the connection oriented link and
establishment of a connection oriented link mobile by mobile basis.
MTP3-B
MTP3-b provides message routing, discrimination and distribution (for point-to-point link
only), signalling link management load sharing and changeover/back between link within
one link-set. The need for multiple link-sets is precluded.
SAAL-NNI
SAAL-NNI consists of the following sub-layers: - SSCF [3], - SSCOP [2] and AAL5 [6].
The SSCF maps the requirements of the layer above to the requirements of SSCOP.
Also SAAL connection management, link status and remote processor status
mechanisms are provided. SSCOP provides mechanisms for the establishment and
release of connections and the reliable exchange of signalling information between
signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM
cells.
Version 1 Rev 7 Control Plane Protocol Stack (UE-CN SIGNALLING, Dedicated Channels, CS-Domain)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
431
Control Plane Protocol Stack (UE-CN SIGNALLING,
Dedicated Channels, CS-Domain)
CP13_Ch4_17
RRC
RLC
MACd
Combining
Phys
UE
Split/
Comb
Phys
DCH
FP
AAL5
ATM
Phys
Node
RLC
MACd
Split/
Comb
DCH
FP
AAL5
ATM
Phys
SRNC
RRC
RANAP
MS
RANAP
SCCP
MTP3b
SAAL
NNI
ATM
Phys
SCCP
MTP3b
SAAL
NNI
ATM
Phys
Version 1 Rev 7 Control Plane Protocol Stack (UE-CN Signalling, Shared Channels, CS-Domain)
432
Control Plane Protocol Stack (UE-CN Signalling, Shared
The diagram opposite illustrates the protocol stack for UE to CN signalling, when the UE
is connected to the network and operating on shared or common channels. The stack
differs from that of dedicated mode, in that the CRNC is no longer transparent.
The continues to provide the majority of the Layer 2 services (RRC, RLC, MAC-d),
However, the CRNC is responsible for terminating the MAC-c/sh entity.
On the diagram, the MUX-1 box in the CRNC represents the multiplexing of the various
AAL2 connections coming from multiple SRNCs into MAC-c/sh. The MUX-2 box
represents the multiplexing of various instances of MAC-d from the same SRNC into
AAL2, for transfer to the MAC-c/sh at the CRNC.
RACH/FACH/ DSCH Frame Protocol
RACH/FACH/DSCH Frame protocols (FPs) are responsible for the transfer of Transport
Blocks between the Node B and the DRNC for common/shared channels. These FPs
will always add overhead to the payload, in the form of a header.
In addition to providing a data transfer function, the common/shared FPs provide the
following services:
S Support of transport channel synchronisation mechanism.
S Support of Node synchronisation mechanism.
S DSCH TFCI signalling.
Version 1 Rev 7 Control Plane Protocol Stack (UE-CN Signalling, Shared Channels, CS-Domain)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
433
Control Plane Protocol Stack(UE-CN Signalling, Shared
CP13_Ch4_18
MUX1
Phys
RACH/
FACH/
DSCH
FP
AAL5
ATM
Phys
MAC
c/sh
RACH/
FACH/
DSCH
FP
AAL5
ATM
Phys
AAL2
ATM
Phys
UE
Node B CRNC SRNC CN
RRC
RLC
MACd
RRC
RLC
MACd
SCCP
RANAP
MAC
c/sh
Phys
MUX2
AAL2
ATM
Phys
RANAP
SCCP
MTP3b
SAAL
NNI
ATM
Phys
MTP3b
SAAL
NNI
ATM
Phys
Version 1 Rev 7 User Plane Protocol Stack (Dedicated Channels, PS-Domain)
434
User Plane Protocol Stack (Dedicated Channels, PS-Domain)
The diagram opposite shows the user plane protocol stack for user data transfer, using
dedicated channels via the CN-PS. The user CS payload will be received at the GGSN
from the external network (e.g. the Internet). The protocols used to transfer the payload
across this interface may vary and are not described in this document.
GPRS Tunnelling Protocol, User Plane (GTP-U)
The user payload data packets, known as T-PDUs, arrive at the GGSN from the external
PDN. Typically these will be IP based and addressed to an application running on the
target UE. Alternate transport mechanisms, such as X25, may also be used. The
T-PDUs will be presented to GTP, via the appropriate NSAPI for the source protocol. For
UMTS the second version of GTP (version 1) will be used.
GTP allows multi-protocol packets to be tunnelled through the UMTS/GPRS Backbone
between GSNs and is necessary to forward packets between an external packet data
network and an MS user. In the user plane, GTP uses a tunnelling mechanism (GTP-U)
to provide a service for carrying user data packets. The GTP-U protocol is implemented
by SGSNs and GGSNs in the UMTS/GPRS Backbone and by Radio Network Controllers
(RNCs) in the UTRAN. No other systems need to be aware of GTP. UMTS/GPRS MSs
are connected to an SGSN without being aware of GTP.
A GTP tunnel in the GTP-U plane is defined for each PDP Context in the GSNs and/or
each RAB in the RNC. A GTP tunnel is identified in each node with a Tunnel Endpoint ID
(TEID), a UDP port number and an IP address. The TEID unambiguously identifies a
tunnel endpoint in the receiving GTP-U protocol entity. The TEID values are negotiated
and exchanged between tunnel endpoints using control plane procedures defined in
protocols such as GTP-C (or RANAP, over the Iu) messages during the activation of the
PDP context or RAB.
Path Protocols
UDP/IP is the only path protocol defined to transfer GTP messages in the version 1 of
GTP.
UDP
A User Datagram Protocol (UDP) compliant with STD 0006 shall be used. The UDP
destination port number for GTP-U messages is 2152.
IP
An Internet protocol compliant with STD 0005 shall be used. The IP destination address
in a GTP message shall be the IP address of the destination GSN/RNC. The source
address shall be the IP address of the originating GSN/RNC.
Version 1 Rev 7 User Plane Protocol Stack (Dedicated Channels, PS-Domain)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
435
(Dedicated Channels, PS-Domain)
CP13_Ch4_19
UE Node B SRNC SGSN PDN GGSN
AAP
Split/
Comb
DCH
FP
PDCP
RLC
GTPU GTPU GTPU
IP IP
AAP
IP
PDCP
RLC
MACd
Comb
Phys Phys
AAL2
ATM
Phys
MACd
Split
Comb
DCH
FP
AAL2
ATM
Phys
UDP
IP
AAL5
ATM
Phys
UDP
IP
AAL5
ATM
Phys
UDP
IP
L2
Phys
GTPU
UDP
IP
L2
Phys Phys
IP
Phys
Version 1 Rev 7 Control Plane Protocol Stack
436
(UE-CN Signalling, Dedicated Channels, PS-Domain)
Stream Control Transmission Protocol
The basic service offered by SCTP is the reliable transfer of user messages between
peer SCTP users. It performs this service within the context of an association between
two SCTP endpoints. SCTP is connection-oriented in nature, but the SCTP association is
a broader concept than the TCP connection. SCTP provides the means for each SCTP
endpoint to provide the other endpoint (during association startup) with a list of transport
addresses (i.e., multiple IP addresses in combination with an SCTP port) through which
that endpoint can be reached and from which it will originate SCTP packets. The
association spans transfers over all of the possible source/destination combinations,
which may be generated from each endpoints lists.
M3UA
MU3A provides adaptation between the SCCP layer and the Transmission protocols. An
RNC equipped with the M3UA stack option shall have client functionality. This enables
the RNC to report to the SGSN when it is a newly introduced entity in the network.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
437
(UE-CN Signalling,Dedicated Channels, PS-Domain)
CP13_Ch4_20
RRC
RLC
MACd
Combining
Phys
UE
Split/
Comb
Phys
DCH
FP
AAL5
ATM
Phys
Node
RLC
MACd
Split/
Comb
DCH
FP
AAL5
ATM
Phys
SRNC
RRC
CN
RANAP
SCCP
M3UA
RANAP
SCCP
M3UA
SCTP
IP
SAAL
NNI
ATM
Phys
SCTP
IP
SAAL
NNI
ATM
Phys
438
EMOTOROLA LTD. 2003
CP13: UMTS Overview
51
Chapter 5
Data Flow and Terrestrial
Interfaces
Version 1 Rev 7
52
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
53
Chapter 5
Data Flow and Terrestrial Interfaces 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terrestrial Interfaces 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Principles 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Asynchronous Transfer Mode (ATM) 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Channels and Paths 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of Virtual Channels and Paths 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Connection and Path Switching 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layers (AALs) 512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The ATM Adaptation Process 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convergence Sub-Layer (CS) 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Segmentation and Reassembly 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layer 2 (AAL2) 516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCS 516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Adaptation Layer 5 (AAL 5) 518 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 Architecture 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Links 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Cell to E1 Cell Mapping 522 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E Link Multiplexing 524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inverse Multiplexing for ATM (IMA) 526 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronous Digital Hierarchy (SDH) 528 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDH Drop and Insert 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Simplification 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Survivability 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Control 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bandwidth on Demand 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Principles of SDH 532 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM to STM Mapping - VC4 534 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical UMTS Transport Network 536 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
54
EMOTOROLA LTD. 2003
CP13: UMTS Overview
51
Objectives
S State the transport mechanisms used for the UMTS transport network.
S Describe the basic principles of ATM.
S Describe the use of PDH and SDH bearers for UMTS.
Version 1 Rev 7 Terrestrial Interfaces
52
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 the following pages a closer look will be taken at these
aspects.
It should also be mentioned that as data rates increase the use of E1/T1 systems
become more difficult. ATM is the preferred transport mechanism on the CN. Voice and
IP over ATM is conducted using ATM adaptation layers.
Version 1 Rev 7 Terrestrial Interfaces
EMOTOROLA LTD. 2003
CP13: UMTS Overview
53
Terrestrial Interfaces
CP13_Ch5_10
UE Node B RNC SGSN GGSN
CS PS
Network
CDMA
FDD
CDMA
TDD
ATM
E1
ATM
SDH
IP
IP
X25
Uu Iub Iups GN
Version 1 Rev 7 ATM Principles
54
ATM Principles
ATM is used to transfer different types of information with different rate factors over one
or more common link with a high bit rate. This 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:
S Considering data, voice, and video payload requirements, ATM was constructed.
ATM cells are of fixed size, 53 bytes each with 48 bytes for payload and 5 for ATM
header. This helps in reducing the packetization delay significantly, which is one of
the major delay parameters.
S It supports extensive QoS (Quality of Service) parameters, which allows voice
traffic to be transmitted across the network in a reliable jitter-free way.
S Various ATM Adaptation Layers (AALs) support various service classes
capabilities.
S ATM switches have always been designed with effective traffic management
capabilities, for example, call admission control, usage parameter control, traffic
shaping, etc.
S Single network for voice, data, and video.
S Interworking with PSTN is relatively straightforward.
Version 1 Rev 7 ATM Principles
EMOTOROLA LTD. 2003
CP13: UMTS Overview
55
ATM Principles
CP13_Ch5_12
Fixed Bit Stream
Variable Bit Stream
Discontinues
Bit Stream
Version 1 Rev 7 Asynchronous Transfer Mode (ATM)
56
Asynchronous Transfer Mode (ATM)
Asynchronous Transfer Mode (ATM) is a technology originally designed for LANs that
have transport, switching and network management facilities built into it. Data rates are:
S Primary User 155.2 Mb/s
S Network Interface 622.08 Mb/s
In general terms ATM is a packet switching protocol made up of fixed length packets.
The standard packet length is 53 Octets, 5 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.
ATM can provide both CBR and VBR transport.
Version 1 Rev 7 Asynchronous Transfer Mode (ATM)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
57
Asynchronous Transfer Mode (ATM)
CP13_Ch5_13
Data transferred in Cells
Fast Switching
Supports RealTime Services
Connection Orientated Virtual Circuits
Resource Allocation on Requirement Basis
Primary User Rate 155.2 Mbps
Network Interface 622.08 Mbps
No Error Correction or Flow Control
Header Payload
5 Bytes 48 Bytes
Version 1 Rev 7 Virtual Channels and Paths

58
Virtual Channels and Paths
On 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 we could have up to 256 addresses for a VP User to Network Interface (UNI) and
4096 for a VP Network to Network Interface (NNI). When VCIs are used, up to 2
16
channels per path can be addressed.
Use of Virtual Channels and Paths
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 opposite 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.
Version 1 Rev 7 Virtual Channels and Paths
EMOTOROLA LTD. 2003
CP13: UMTS Overview
59
Virtual Channels and Paths
Use of Virtual Channels and Paths
CP13_Ch5_15
ATM Path
Virtual Path (VP)
Virtual Channel (VC)
Each VP within the physical layer has a different VPI value
Each VC within a VP has a different VCI value
CP13_Ch5_16
Virtual Channel Connection Endpoints
Virtual Channel Connection
Virtual Channel Link Virtual Channel Link
Virtual Path Link Virtual Path Link
VC Switch VCI and VPI
values change
Virtual Path Connection
Virtual Path Connection Endpoints
VP Switch VC Switch
ATM
END
SYSTEM
ATM
END
SYSTEM
Version 1 Rev 7 Virtual Connection and Path Switching
510
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. Therefore we would only switch on VP level like illustrated in
the diagram. 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.
Version 1 Rev 7 Virtual Connection and Path Switching
EMOTOROLA LTD. 2003
CP13: UMTS Overview
511
Virtual Connection and Path Switching
CP13_Ch5_17
VC Switch
VP Switch
VP Switch
Endpoint
of VPC
Representation of VC and VP Switching Representation of VP Switching
Version 1 Rev 7 ATM Adaptation Layers (AALs)
512
ATM Adaptation Layers (AALs)
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).
Version 1 Rev 7 ATM Adaptation Layers (AALs)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
513
ATM Adaptation Layers
CP13_Ch5_11
Class A Class B Class C Class D
Timing Relation Required Not Required
Bit Rate
Connection Rate
Examples
Service Type
to be used
Constant Variable
Connection
Orientated
Connection
Less
Emulation
of Circuits
CPCM
Variable Bit
Rate Video
Connection
Orientated Data
Transmission
Connection
Less Data
Transmission
AAL 1 AAL 2
AAL 3/4 or
AAL 5
Version 1 Rev 7 The ATM Adaptation Process
514
The ATM Adaptation Process
The AAL consists of two sub-layers; The Convergence sub-layer (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 (CS-PDU). Finally it passes the
CS-PDUs to the SAR.
Segmentation and Reassembly
At the source end, the SAR sub-layer 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.
Version 1 Rev 7 The ATM Adaptation Process
EMOTOROLA LTD. 2003
CP13: UMTS Overview
515
Generic AAL Process
CP13_Ch5_31
User
Header Trailer User
T CSSDU H
SARSDU T H
SARPDU SARPDU H H
T CSSDU H T CSSDU H
SARSDU T H
CS
PROCESS
SAR
PROCESS
ATM
LAYER
CSPDU
SARPDU
ATM Cell
Version 1 Rev 7 ATM Adaptation Layer 2 (AAL2)
516
ATM Adaptation Layer 2 (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.
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.
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 sub-stream
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.
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.
Version 1 Rev 7 ATM Adaptation Layer 2 (AAL2)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
517
AAL 2
CP13_Ch5_32
HEADER OSF SN P Info Packets or padding
CID
8bits
LI
6bits
UUI
5bits
HEC
5bits
CPSInformation field
VARIABLE 1 64 Octets
3Octet CPS Header User Information
CPSPDU
ATM Cell (53Octets)
CPSPacket
CPSSDU Header CPSSDU
OSF
6bits
SN
1bit
P
1bit
Info packets or padding
47 Octets
Version 1 Rev 7 ATM Adaptation Layer 5 (AAL 5)
518
ATM Adaptation Layer 5 (AAL 5)
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.
CPI Common Part Indicator LI Length Indicator
PDU Protocol Data Unit AAL ATM Adaption Layer
SDU Service Data Unit CRC Cyclic Redundancy Check
CPCS Common Part Convergence
Sublayer
SAR Segmentation and
Reassembly
Version 1 Rev 7 ATM Adaptation Layer 5 (AAL 5)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
519
AAL5
CP13_Ch5_33
User Data
1 65,535 bytes
H SAR Payload
SAR Payload
CPCSPDU Payload PAD UUI CPI LI CRC
H SAR Payload
SAR Payload
H SAR Payload
SAR Payload
047 1 1 2 4
AAL 5
SDUs
ATM
CELLS
SAR
PDUs
CPCS
PDUs
Version 1 Rev 7 E1 Architecture
520
E1 Architecture
Logical Links
We have seen some of the mediums over which the data is transmitted, now let us
consider the format of the data that is carried over these means.
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.
T1
T1 is the American version of E1.
There are significant differences in the make up of the TDM frame.
T1 uses 24 time slots per frame, with 24 PCM channels per frame. The output bit rate is
1.544 Mbit/s and the signalling used in the frame is only used once every 6
th
frame,
instead of every frame in E1.
Version 1 Rev 7 E1 Architecture
EMOTOROLA LTD. 2003
CP13: UMTS Overview
521
E1 Architecture
CP13_Ch5_22
T1/DS1
E1
Frequency
Sampling Rate
Bits per Sample
Bits per Frame
PCM Channels per Frame
Output Bit Rate
Encoding Law
Signalling Capabilities
300 3400Hz
8000Hz
8
193
24
1.544 Mb/s
Law
1st bit in frame Sync
1 bit in timeslots 6 and 12
Frequency Range
Sample Rate
Bits per Sample
Time Slots per Frame
Output Bit Rate
Encoding Law
Signalling Capabilities
300 3400Hz
8000Hz
8
32
2.048 Mb/s
A LAW
TS16 Signalling
TS0 Sync
Version 1 Rev 7 ATM Cell to E1 Cell Mapping
522
ATM Cell to E1 Cell Mapping
The ATM cell is mapped into bits 9 to 128 and bits 137 to 256 (i.e. 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 the Figure opposite. 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.
Version 1 Rev 7 ATM Cell to E1 Cell Mapping
EMOTOROLA LTD. 2003
CP13: UMTS Overview
523
ATM Cell to E1 Cell Mapping
CP13_Ch5_34
TS0
Synch
TS16
Sig
ATM Mapping Field
15 Octets
ATM Mapping Field
15 Octets
125 S E1 frames - 256 bits per frame
Version 1 Rev 7 E Link Multiplexing
524
E Link Multiplexing
The standard E1 and T1 streams can be further multiplexed to put more channels over
one transmission path.
Version 1 Rev 7 E Link Multiplexing
EMOTOROLA LTD. 2003
CP13: UMTS Overview
525
E Series Hierarchies
CP13_Ch5_23
E1
2.048 Mb/s
E2
8.448 Mb/s
E3
34.368 Mb/s
E4
139.264 Mb/s
E5
564.992 Mb/s
x 4
x 4
x 4
x 4
30 TCH
120 TCH
480 TCH
1,920 TCH
7,680 TCH
Version 1 Rev 7 Inverse Multiplexing for ATM (IMA)
526
Inverse Multiplexing for ATM (IMA)
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 (e.g., DS1/E1 links) grouped to
collectively provide higher intermediate rates.
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. The figure opposite 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.
Version 1 Rev 7 Inverse Multiplexing for ATM (IMA)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
527
Inverse Multiplexing and De-multiplexing of ATM cells
CP13_Ch5_35
PHY
PHY
PHY
IMA Group IMA Group
PHY
PHY
PHY
Physical Link #0
Physical Link #1
Physical Link #2
Original ATM Cell
Stream to ATM Layer
Single ATM CellStream
from ATM Layer
Tx direction: cells distributed across links in round robin sequence
Rx direction: cells recombined into single ATM stream
IMA Frames
CP13_Ch5_36
ATM F ATM ICP2 ATM F F ATM ICP0 ATM F F ATM ICP1 F Link 0
ICP2 F ATM F F ICP0 F ATM F ATM ICP1 ATM ATM ATM ATM Link 1
ATM ICP2 ATM F F F ICP0 ATM ATM ATM F ICP1 ATM ATM ATM Link 2
IMA Frame 2 IMA Frame 1 IMA Frame 0
M1 2 3 1 0 M1 2 3 1 0 M1 2 3 1 0
ICP1 ICP Cell in Frame # 1 F Filler Cell ATM ATM Layer Cell
Time
Version 1 Rev 7 Synchronous Digital Hierarchy (SDH)
528
Synchronous Digital Hierarchy (SDH)
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 Mb/s).
SDH uses a basic transmission rate of 155.52 Mb/s (abbreviated to 155 Mb/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 125s. Any of the
PDH rates can be multiplexed into the STM-1.
The main advantages of SDH are:
S It allows direct access to tributary signals without demultiplexing the composite
signal.
S 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.
S Overhead bytes have been preserved for growth to support services and
technologies of the future.
Version 1 Rev 7 Synchronous Digital Hierarchy (SDH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
529
SDH
CP13_Ch5_19
SDH Bit Rates
Synchronous Transport
Module
Transmission
Rate
STM 1
STM 4
STM 16
STM N
155.52 Mb/s
622.08 Mb/s
2,488.32 Mb/s
N x 155.52 Mb/s
Version 1 Rev 7 SDH Drop and Insert
530
SDH Drop and Insert
SDH overcomes the limitations of plesiochronous networks, and will allow transmission
networks to evolve to meet the demands of emerging broadband services.
Network Simplification
Synchronous transmission equipment eliminates the multiplexer mountain, leading to
lower equipment and maintenance costs, and improved service provisioning. The
diagram shows how 2Mb/s channels can be dropped and inserted from a Synchronous
Transfer Module, Type 1 (STM-1) by means of remote commands at a network
management station. The flexibility of SDH transmission is attractive to carriers because
it offers the potential of generating new revenues.
Survivability
SDH includes overheads for end-to-end monitoring and maintenance of transmission
equipment; the network management station can immediately identify the failure of links
and equipment. Furthermore, as shown in the diagram, an SDH network can be
constructed with a self-healing ring architecture that automatically re-routes traffic until
the faulty segment is repaired; there will be no disruption of service to the end user,
allowing carriers to guarantee service levels.
Software Control
SDH also includes overheads for management channels; these are used for
performance monitoring, equipment configuration, resource management, network
security, inventory management, network planning and network design. Since all of
these management operations can be performed remotely, SDH offers the possibility of
centralised network management and provisioning, with associated cost savings.
Bandwidth on Demand
The flexibility of SDH allows carriers to allocate network capacity dynamically in that
users will be able to subscribe at very short notice to large bandwidth services e.g.
video-conferencing. This feature opens up the possibility of providing new services e.g.
high-speed LAN interconnection and High Definition TV.
Version 1 Rev 7 SDH Drop and Insert
EMOTOROLA LTD. 2003
CP13: UMTS Overview
531
SDH Drop and Insert
CP13_Ch5_38
SDH Mux
2Mb/s interface
1 63 2
SDH Mux
2Mb/s interface
SDH Mux
2Mb/s interface
SDH Mux
2Mb/s interface
155Mb/s alternate routing
using ring topology
Management of
2Mb/s traffic
155Mb/s
155Mb/s
155Mb/s
Version 1 Rev 7 Principles of SDH
532
Principles of SDH
Although a full description of SDH is beyond the scope of this course, this section will
cover the main principles.
The diagram 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:
S C - Container
S VC - Virtual Container
S TU - Tributary Units
S TUG - Tributary Unit Group
S AU - Administrative Unit
S AUG - Administrative Unit Group
S STM - Synchronous Transfer Module
The following table lists the container size suffices used when referring to equivalent
PDH traffic rates within SDH signals:
Container Suffix Bit rate kbps
0 64
11 1,554
12 2,048
21 6,312
22 8,448
31 34,368
32 44,736
4 139,264
Version 1 Rev 7 Principles of SDH
EMOTOROLA LTD. 2003
CP13: UMTS Overview
533
Principles of SDH
CP13_Ch5_37
STM1
AUG AU4
TU3
VC4
VC3
VC11
VC12
VC2
VC3
C11
C12
C2
C3
C4
140 Mbit/s
45 Mbit/s
34 Mbit/s
6 Mbit/s
2 Mbit/s
1.5 Mbit/s
TU11
TU12
TU2 TUG2
AU3
x1
x3
x3
TUG3
x1
x7
x7
x1
x3
x4
STM0
Version 1 Rev 7 ATM to STM Mapping - VC4
534
ATM to STM Mapping - VC4
B-ISDN maintains a transmission rate of 155.520 Mbps or 622.080 Mbps. The physical
medium can be optical with an extension capability of 0 - 800m or coaxial cable with an
extension capability of 0 - 100m.
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.520Mbps, only 149.760Mbps is filled with ATM cells
and the other 5.760Mbps is filled with STM frame overheads (SOH, POH, Pointer ).
Identifying cell boundaries is done using HEC or an SDH overhead.
Version 1 Rev 7 ATM to STM Mapping - VC4
EMOTOROLA LTD. 2003
CP13: UMTS Overview
535
ATM to STM Mapping
CP13_Ch5_20
1 octet 260 octets
SOH
SOH
AU4PTR
3
1
5
VC4
STM1
VC4 POH
ATM Cell
53 octets
9 octets 261 octets
J1
B3
C2
G1
H4
Version 1 Rev 7 Typical UMTS Transport Network
536
Typical UMTS Transport Network
The diagram opposite 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 Bs, 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 100Mbps due to the hardware limitations.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
537
ATM Transport Network
CP13_Ch5_39
Node B
SGSN
MSCu
RNC
RNC
RNC
Node B
Node B
Node B
Node B
ATM Mux
OMC
ATM Switch
ATM Switch
Ethernet
Ethernet
(Option under
investigation)
STM1
STM1
STM1
STM1
STM1
E1, IMA
E1, IMA
E1, IMA
E1, IMA
SDH Ring
(STM1/STM4/STM16)
538
EMOTOROLA LTD. 2003
CP13: UMTS Overview
61
Chapter 6
W-CDMA Theory
Version 1 Rev 7
62
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
63
Chapter 6
W-CDMA Theory 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Access Schemes 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
W-CDMA Characteristics 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-Use of Frequency 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-Use of Codes 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spectral Efficiency (GSM and UMTS) 610 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct Spread (DS)-CDMA Implementation 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitter 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver 612 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spreading 614 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Orthogonal Codes 618 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channelisation Code Tree 620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
De-spreading Other Users Signals 622 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Gain 624 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling 632 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling Codes vs Channelisaton Codes 634 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Short Codes vs Long Codes 636 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scrambling and Summation 638 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
De-Scrambling and Data Recovery 640 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-path Radio Channels 642 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Matched Filter Operation 644 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The RAKE Receiver 646 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
64
EMOTOROLA LTD. 2003
CP13: UMTS Overview
61
Objectives
S Describe various options for multiple access schemes.
S State the Characteristics of UMTS W-CDMA.
S State why W-CDMA has been chosen for the UMTS multiple access scheme.
S Describe W-CDMA spreading and depreading procedures.
S Describe the use of orthagonal codes and the channelisation code tree.
S Describe the scrambling and summation process.
S Describe the effects of multi-path radio channels and the purpose of the RAKE
receiver.
Version 1 Rev 7 Multiple Access Schemes
62
Multiple Access Schemes
There are 3 forms of multiple access schemes, frequency, time and code. The major
issue with the first two is the requirement to have guard bands.
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.
Version 1 Rev 7 Multiple Access Schemes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
63
Multiple Access Schemes
CP13_Ch6_01
CDMA
TDMA
Frequency
Power
FDMA
Frequency
Power
Time
Time
Time
Frequency
Codes
Version 1 Rev 7 W-CDMA Characteristics
64
W-CDMA Characteristics
The vital statistics for our W-CDMA UMTS system is shown opposite. Dont be confused
by the slots and frames, this is not a TDMA system, every user does share the same
band. The frames and slots are used for interleaving, power control.
The major points are:
FDD requires paired frequencies for up and down channels.
The chip rate of 3.84 Mcps 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.
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 Kbps.
Version 1 Rev 7 W-CDMA Characteristics
EMOTOROLA LTD. 2003
CP13: UMTS Overview
65
W-CDMA Characteristics
CP13_Ch6_03
Multiple Access Scheme
Duplexing Method
Chip Rate
Bandwidth
Carrier Spacing
Frame Length
Slots per Frame
Intercell Synchronization
Spreading Factor
User Data Rate
CDMA
FDD
3.84 Mcps
5 MHz
200 kHz Raster
10 ms
15
None
Variable (4512)
3384 Kbps
Version 1 Rev 7 Re-Use of Frequency
66
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.
In 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.
Version 1 Rev 7 Re-Use of Frequency
EMOTOROLA LTD. 2003
CP13: UMTS Overview
67
Re-Use of Frequency
CP13_Ch6_14
1
2
5
3
7
4
1 6
2
5
3
7
4
1 6
2
5
3
7
4
1 6
2
5
3
7
4
1
6
2
5
3
7
4
1 6
2
3
4
1
2
5
7
4
6
3
Version 1 Rev 7 Re-Use of Codes
68
Re-Use of Codes
Codes are used to uniquely identify a cell in the network. Frequency planning is more or
less a thing of the past but code planning will have to be implemented. Code planning will
be much easier then frequency planning since we have 512 Codes to play with, the code
re-use pattern will thus be 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.
Version 1 Rev 7 Re-Use of Codes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
69
Re-Use of Codes
CP13_Ch6_15
14 6
16
15
13
7
4
1 27
28
30
31
29
36 37
2
25
35
32
34
23 39
20
18
38
22
21
17 19
11
10
12
2
4
7 4
1
6
5
41
24
5
33
40
26
Version 1 Rev 7 Spectral Efficiency (GSM and UMTS)
610
Spectral Efficiency (GSM and UMTS)
The Slide opposite shows how spectrally efficient UMTS and GSM is in comparison to
each other when employed in a multi-cellular structure.
The capacity, which Shannon derived in 1947, provided a Law, which we now call
Shannons Law. This details the digital capacity of the link given the transmit power and
the bandwidth.
If we are using, FDMA, TDMA or CDMA, the capacity is still controlled by this law.
However, some gains are made by technology and coding methods.
Version 1 Rev 7 Spectral Efficiency (GSM and UMTS)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
611
Spectral Efficiency (GSM and UMTS)
CP13_Ch6_06
7 x 200 kHz = 1.4 MHz
1 Call = 25 kHz
8 Calls = 200 kHz Carrier
1 Call = 25 kHz
GSM
7 Cells, 5 MHz
1 Call = 2.8 kHz
256 Calls = 5 MHz Carrier
1 Call = 19.4 kHz
UMTS SF256
Version 1 Rev 7 Direct Spread (DS)-CDMA Implementation
612
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 2Ghz
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.
Here the input is multiplied by the de-spreading codes to produce digital speech.
Version 1 Rev 7 Direct Spread (DS)-CDMA Implementation
EMOTOROLA LTD. 2003
CP13: UMTS Overview
613
Direct Spread (DS)-CDMA Implementation
CP13_Ch6_26
Single User Channel
5 MHz
Multiple User Channel Multiple User Channel Output
0
0
Input
External Interference
Radio
Modulator
Digital
Signal
Digital
Signal
Spreading
Code
Generator
Digital
Modulator
Digital
Modulator
Radio
Modulator
C
o
m
b
i
n
e
r
S
p
l
i
t
t
e
r
Digital
Signal
Digital
Signal
Digital
Demodulator
Radio
Demodulator
Radio
Demodulator
Digital
Demodulator
t0
Rx
Radio
Carrier
Radio
Carrier
Tx
WCDMA
Modulated Carrier
Spreading
Code
Generator
5 MHz 5 MHz
Version 1 Rev 7 Spreading
614
Spreading
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 Mcs. After the spreading operation each Bit of the
data signal is represented by a number of chips.
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
EMOTOROLA LTD. 2003
CP13: UMTS Overview
615
Spreading
Data
480 kB/s
Spreading
Code
3.84 Mcs
Spread
Data
1
1
1
1
1
1

616
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.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
617
De-spreading (desired signal)
CP13_Ch6_26b
Spread
Data
Spreading
Code
Correlation
RX
Integrator
O/P
Recovered
Data
1
1
1
1
1
1
Version 1 Rev 7 Orthogonal Codes
618
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.
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.
Version 1 Rev 7 Orthogonal Codes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
619
Orthogonal Codes
CP13_Ch6_18
Channelisation codes known as OVSF codes are
used to distinguish individual physical channels
The OVSF codes limit the number of users per carrier
OVSF codes are orthogonal codes
The cross correlation between orthogonal codes is zero
1 1 1 1
1 1
1 1
1
1
1
1
1 1
1
1
Version 1 Rev 7 Channelisation Code Tree
620
Channelisation Code Tree
For separating channels from the same source, channelisation codes called Orthogonal
Variable Spreading Factors are used.
The lines in the diagram 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 above.
Each level in the code tree defines a Spreading Factor (SF) indicated in the figure. 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.
Version 1 Rev 7 Channelisation Code Tree
EMOTOROLA LTD. 2003
CP13: UMTS Overview
621
Channelisation Code Tree
CP13_Ch6_13
(1, 1, 1, 1, 1, 1, 1, 1)
Cch, 8, 7
Cch, 8, 6
(1, 1, 1, 1, 1, 1, 1, 1)
(1, 1, 1, 1, 1, 1, 1, 1)
Cch, 8, 5
Cch, 8, 4
(1, 1, 1, 1, 1, 1, 1, 1)
(1, 1, 1, 1, 1, 1, 1, 1)
Cch, 8, 3
Cch, 8, 2
(1, 1, 1, 1, 1, 1, 1, 1)
(1, 1, 1, 1, 1, 1, 1, 1)
Cch, 8, 1
Cch, 8, 0
(1, 1, 1, 1, 1, 1, 1, 1) Cch, 4, 0
Cch, 4, 1
Cch, 4, 2
Cch, 4, 3
(1, 1, 1, 1)
(1, 1, 1, 1)
(1, 1, 1, 1)
(1, 1, 1, 1)
Cch, 2, 0
Cch, 2, 1
(1, 1)
(1, 1)
Cch, 1, 0
(1)
SF = 1 SF = 2 SF = 4 SF = 8
Version 1 Rev 7 De-spreading Other Users Signals
622
De-spreading Other Users Signals
It must be remembered that 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.
The lower diagram opposite shows the effect of dispreading and correlation at a given
receiving station (e.g UE A), on an interferer signal, (e.g 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. (i.e. the output of the integration process
will be zero.) This process is only true when correctly selected Orthogonal Spreading
Codes are employed.
Version 1 Rev 7 De-spreading Other Users Signals
EMOTOROLA LTD. 2003
CP13: UMTS Overview
623
De-spreading (Interferer Signals)
CP13_CH6_13a
Data for UE B
Spreading Code
for UE B
Spread Data
for UE B
Spread Code
for UE A
1
1
1
1
1
1
1
1
1
1
Recovered Data
at UE A
Correlation R
Integrator O/P
at UE A
This example shows the correlator output when UE A tries
to despread UE Bs spread data
Version 1 Rev 7 Processing Gain
624
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 that we get from the Processing Gain is an extremely important part of CDMA.
It is in fact 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. As we know, 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 must be increased of any transmitter 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.
Version 1 Rev 7 Processing Gain
EMOTOROLA LTD. 2003
CP13: UMTS Overview
625
Processing Gain
CP13_Ch6_16
PG = 10 x log (Chip Rate/Bit Rate)
or
PG = 10 x log (SF)
Version 1 Rev 7 Exercise 1 - Spreading
626
Exercise 1 - Spreading
This Exercise demonstrates the Modulo-2 Addition, Spreading Factor usage, Code
Lengths and in general will give the student a feel for the Spreading Principle.
The Lecturer should use this exercise as an example.
NOTES
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
________________________________________________
EMOTOROLA LTD. 2003
CP13: UMTS Overview
627
CP13_Ch6_22
Spreading
Despreading
C/I = 5 dB 6 dB
= 1 dB
S/N = 5dB
Calculation Box
SF = 4
PG = 4 (ratio)
PG = 6 dB
Data
Spreading Code
Spread Data
Spreading Code
Despread Data
1
1
1
1
1
1
1
1
1
1
628
To gain some experience in Spreading the student can complete the following exercise.
The student can complete the despreading part of the exercise and then calculate the SF
and PG. See if it matches with the answers provided.
Note the irregular structure in the answer.
NOTES
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________
EMOTOROLA LTD. 2003
CP13: UMTS Overview
629
CP13_Ch6_23
C/I = 5 dB 6 dB
= 1 dB
S/N = 5dB
Calculation Box
SF = 4
PG = 4 (ratio)
PG = 6 dB
Spreading
Despreading
Data
Spreading Code
Spread Data
Spreading Code
Despread Data
Wrong
Spreading Code
Despread Data
Wrong Code
1
1
1
1
1
1
1
1
1
1
1
1
1
1
630
In this exercise the student must complete the following:
1. Determine the SF used?
2. Do the spreading part of the exercise?
3. Do the despreading part of the exercise using the right code?
4. Do the despreading part of the exercise using the wrong code?
5. Complete the calculation?
NOTES
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
____________________________________
EMOTOROLA LTD. 2003
CP13: UMTS Overview
631
P13_Ch6_24
C/I =
= 1 dB
S/N = 5db
Calculation Box
SF =
PG =
PG =
Spreading
Despreading
1
1
1
1
1
1
1
1
1
1
1
1
1
Data
Spreading Code
Spread Data
Spreading Code
Despread Data
Wrong
Spreading Code
Despread Data
Wrong Code
1
Version 1 Rev 7 Scrambling
632
Scrambling
As previously described, 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.
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.
Version 1 Rev 7 Scrambling
EMOTOROLA LTD. 2003
CP13: UMTS Overview
633
Scrambling
CP13_Ch6_35
Cch SF,x Csc,x
Cch SF,x Csc, x
Cch SF,x Csc,x
Channel x
Data
Channel y
Data
Channel z
Data
Version 1 Rev 7 Scrambling Codes vs Channelisaton Codes

634
Scrambling Codes vs Channelisaton Codes
The Slide shows the major differences between Scrambling Codes (SC) and
Channelisation Codes (CC).
Version 1 Rev 7 Scrambling Codes vs Channelisaton Codes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
635
Scrambling Codes vs Channelisation Codes
CP13_Ch6_12
CC SC
Usage Uplink
Length Uplink
Number of Codes
available
Code Family
Spreading
Separation of Data & Control Channels
(from the same UE)
Separation of channels to different UEs
Separation of UEs
Separation of Cells Usage Downlink
Length Downlink 4 512 Chips
No effect on Bandwidth
LC=10ms = Gold Code
SC = Extended S2 Family
Uplink = 2 1 = 16,777,215
LC =38400 Chips
LC 10ms=38400 Chips or
SC = 66.7us = 256 Chips
Increases Tx Bandwidth
512 Uplink and Downlink
OVSF
4 256 Chips
24
Downlink = 2 1 = 262,143
(truncated to 8,192)
18
Version 1 Rev 7 Short Codes vs Long Codes
636
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
very 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.
Version 1 Rev 7 Short Codes vs Long Codes
EMOTOROLA LTD. 2003
CP13: UMTS Overview
637
Short Codes vs Long Codes
CP13_Ch6_21
Short codes
Code sequence length <Timeslot
Code sequence repeated within every timeslot
Good auto correlation properties
Bad cross correlation properties
Planning Difficult
Code sequence length >> Timeslot
Code sequence repeated for each Radio Frame
Bad auto correlation properties (long repetition cycle)
Good cross correlation properties
Planning easy
Long codes
Version 1 Rev 7 Scrambling and Summation
638
Scrambling and Summation
The diagram opposite 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.
Version 1 Rev 7 Scrambling and Summation
EMOTOROLA LTD. 2003
CP13: UMTS Overview
639
Scrambling and Summation
CP13_Ch6_36
Spread Data
Channel X Cch 8,1
Spread Data
Channel Y Cch 8,2
Spread Data
Channel Z Cch 8,3
Scrambling
code
Channel X after
scrambling
Channel Y after
scrambling
Channel Z after
scrambling
Complex added
scrambled codes
1
1
1
1
1
1
1
1
1
1
1
1
1
1
+3
+2
+1
1
2
3
Version 1 Rev 7 De-Scrambling and Data Recovery
640
De-Scrambling and Data Recovery
The diagram opposite 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.
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.
Version 1 Rev 7 De-Scrambling and Data Recovery
EMOTOROLA LTD. 2003
CP13: UMTS Overview
641
De-Scrambling and Data Recovery
CP13_Ch6_37
Received
Scrambled
Scrambling
Code
Descrambled
Signal
Chan Code for
Chan Y (Cch8.2)
Correlation
Output
+3
+2
+1
1
2
3
1
1
+3
+2
+1
1
2
3
Version 1 Rev 7 Multi-path Radio Channels
642
Multi-path Radio Channels
Radio propagation for mobile communications suffers greatly from the effects of mulipath
reflections, diffractions and attenuation of the signal energy. These effects are causes by
objects such as buildings, hills, etc, resulting 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.26uS at 3.84 Mcs. This equates to a path length
difference of 78 m). Delays of 1 or 2 micro seconds are typical in urban areas, with 20uS
possible in hilly areas.
Signal Fade
In multi-path situations where path lengths are multiples of half a wavelength of the
received frequency (7cm at 2GHz), 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.
Version 1 Rev 7 Multi-path Radio Channels
EMOTOROLA LTD. 2003
CP13: UMTS Overview
643
Multi-path Radio Channels
CP13_6_38

Version 1 Rev 7 Matched Filter Operation
644
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.
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.
Version 1 Rev 7 Matched Filter Operation
EMOTOROLA LTD. 2003
CP13: UMTS Overview
645
Matched Filter Operation
CP13_Ch6_27
RF
Front End
Circuitry
Matched
Filter
Slot Wise
Accumulation
Version 1 Rev 7 The RAKE Receiver
646
The 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. Note 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 the figure and 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.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
647
The RAKE Receiver
CP13_Ch6_28
D0
Cch sf,k
Cch sf,k
Cch sf,k
Cch sf,k
t1
t2
t3
D1
D2
D3
648
EMOTOROLA LTD. 2003
CP13: UMTS Overview
71
Chapter 7
The Physical Layer
Version 1 Rev 7
72
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
73
Chapter 7
The Physical Layer 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Layer Services 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QPSK 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Locations 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Transmission 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channels on the Air Interface 710 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic Channels 712 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport Channels 714 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Channels 716 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Physical Channels (CPCHs) 716 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Channel Mapping 718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical signals 718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generic Frame Structure 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Frame 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Frame 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslot 720 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronisation Channel (SCH) 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Primary SCH 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Secondary SCH 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modulation Symbol a 722 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronisation (Cell Search) Procedure 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Slot synchronisation 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 2: Frame synchronisation and code-group identification 724 . . . . . . . . . . . . . . . .
Step 3: Scrambling-code identification 724 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronisation 725 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Pilot Channel (CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary Common Pilot Channel (P-CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Secondary Common Pilot Channel (S-CPICH) 726 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modulation pattern for Common Pilot Channel 727 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P-CCPCH Frame Structure 728 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCH and P-CCPCH 730 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging Indicator Channel (PICH) 732 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PICH Channel Structure. 732 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discontinuous Reception (DRX) on the PICH 733 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Secondary Common Control Physical Channel (S-CCPCH) 736 . . . . . . . . . . . . . . . . . . . . . . .
Secondary CCPCH Fields 737 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pysical Random Access Channel (PRACH) 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the PRACH 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Random Access Transmission 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRACH Pre-amble 738 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the random-access transmission 739 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of PRACH Message Part 740 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
74
Acquisition Indicator Channel AICH) 742 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AICH signature patterns 743 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Relationship Between PRACH and AICH 744 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Dedicated Physical Channels (DL-DPCH) 746 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DL-DPCH Structure 746 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Slot Formation in Case of Multi-Code Transmission 748 . . . . . . . . . . . . . . .
Uplink Dedicated Physical channels (UL-DPCH) 750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Random Access Procedure in Detail 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Random access parameters 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical random access procedure 752 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASC to Access Class Mapping 756 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH access slot sets 757 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH sub-channels 757 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACH Access Slot Availability 762 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scaling Factor 768 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRACH/Access Service Class/ Sub channel/Signature Mapping 770 . . . . . . . . . . . . .
PCPCH (Physical Common Packet Channel) and Associated Physical Signals 772 . . . . . .
CPCH Status Indicator Channel (CSICH) 774 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCH transmission 776 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPCH Access Preamble Acquisition Indicator Channel (APAICH) 778 . . . . . . . . . .
CPCH Collision Detection/Channel Assignment Indicator Channel (CD/CAICH) . . . . . . .
780
Physical Common Packet Channel (PCPCH) 784 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DLDPCCH for CPCH 786 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downlink Flow Process 788 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uplink Flow Process 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Frame Equalisation 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rate Matching 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTX 790 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2003
CP13: UMTS Overview
71
Objectives
S Describe the procedures performed by the Air Interface Physical Layer
S Describe the UMTS Channel Structure.
- Logical Channels
- Transport Channels
- Physical Channels
S Describe the Downlink and Uplink Flow Processes.
Version 1 Rev 7 Physical Layer Services
72
Physical Layer Services
The Physical Layer (L1) will be the main discussion in this section since this is where
most of the air interface tasks are performed.
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.
S Macrodiversity distribution, combining and soft handover execution.
S Error detection on transport channels and indication to higher layers.
S FEC encoding/decoding of transport channels.
S Multiplexing of transport channels and demultiplexing of coded composite transport
channels (CCTrCHs).
S Rate matching of coded transport channels to physical channels.
S Mapping of coded composite transport channels on physical channels.
S Power weighting and combining of physical channels.
S Modulation and spreading/demodulation and despreading of physical channels.
S Frequency and time (chip, bit, slot, frame) synchronisation.
S Radio characteristics measurements including FER, SIR, Interference Power, etc.,
and indication to higher layers.
S Inner - loop power control.
S 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.
Version 1 Rev 7 Physical Layer Services
EMOTOROLA LTD. 2003
CP13: UMTS Overview
73
Physical Layer Services
CP13_Ch7_02
Macrodiversity distribution, combining and soft handover execution.
Error detection on transport channels.
FEC encoding & decoding of transport channels.
Mux & Demux of transport channels and 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 demodulation and spreading of physical channels.
Frequency and time synchronisation.
Radio characteristics measurements.
Inner loop power control.
RF processing.
Version 1 Rev 7 QPSK
74
QPSK
The modulation scheme used in W-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.
Version 1 Rev 7 QPSK
EMOTOROLA LTD. 2003
CP13: UMTS Overview
75
QPSK
CP13_Ch6_09
QPSK
(0,0)
I
Q Q
2 bits per symbol
(0,1)
(1,0) (1,1)
Version 1 Rev 7 Channel Locations
76
Channel Locations
The Radio Interface is the section of the network between the UE and the Network. This
section of the network is where the biggest limitation lies at the moment, it is the most
vulnerable section and therefore very complex methods have to be invented in order to
transmit the required data at the high speeds that is demanded of todays networks. The
radio interface is composed of Layers 1, 2 and 3.
The slide opposite 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.
Version 1 Rev 7 Channel Locations
EMOTOROLA LTD. 2003
CP13: UMTS Overview
77
Channel Locations
CP13_Ch7_08
Layer 2
Layer 1
Logical Channels
Transport Channels
Physical Channels
MAC
Physical Layer
UE
Version 1 Rev 7 Structure of Transmission
78
Structure of Transmission
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 1control
information must be transmitted on the physical channel along with the transport channel
information.
As previously discussed, 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 make the transmission of Layer 1 control information continuous and
hence prevents bursty transmission, even when DTX is applied.
Version 1 Rev 7 Structure of Transmission
EMOTOROLA LTD. 2003
CP13: UMTS Overview
79
Structure of Transmission
CP13_Ch7_07
I
Q
Version 1 Rev 7 Channels on the Air Interface
710
Channels on the Air Interface
The slide opposite shows the most common channels used on the air interface. The
channels are divided horizontally into the Physical Channels (PCHs), the Transport
Channels (TCHs) and the Logical Channels (LCHs). Vertically they are divided into 2
channel types, the Dedicated Channels and the Common channels. Dedicated Channels
are dedicated to one UE only and Common Channels can be shared by multiple UEs.
Version 1 Rev 7 Channels on the Air Interface
EMOTOROLA LTD. 2003
CP13: UMTS Overview
711
Channels on the Air Interface
Version 1 Rev 7 Logical Channels
712
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:
S Control Channels (for the transfer of control plane information).
S Traffic Channels (for the transfer of user plane information).
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.
Traffic Channels
Dedicated Traffic Channel (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.
Version 1 Rev 7 Logical Channels
EMOTOROLA LTD. 2003
CP13: UMTS Overview
713
Logical Channels
CP13_Ch7_10
DCCH DTCH BCCH PCCH CCCH CTCH
Between MAC and Higher Applications
URNTI PTM
Version 1 Rev 7 Transport Channels
714
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:
S Common transport channels (where there is a need for inband identification of the
UEs when particular UEs are addressed.
S Dedicated transport channels (where the UEs are identified by the physical
channel, i.e. code and frequency for FDD and code, time slot and frequency for
TDD).
Random Access Channel (RACH)
A contention based uplink channel used for transmission of relatively small amounts of
data, e.g. for 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.
Downlink Shared Channel (DSCH)
A downlink channel shared by several UEs carrying dedicated control or traffic 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.
Version 1 Rev 7 Transport Channels
EMOTOROLA LTD. 2003
CP13: UMTS Overview
715
Transport Channels
CP13_Ch7_11
Between the Physical Layer and MAC
CCH
BCH PCH FACH
USCH
DSCH
RACH CPCH
DCH
Version 1 Rev 7 Physical Channels
716
Physical Channels
Common Physical Channels (CPCHs)
P-SCH ; S-SCH Primary Synchronisation Channel; Secondary Synchronisation
Channel
Synchronisation to the network
P-CCPCH Primary Common Control Physical Channel
Cell Information and 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
packet-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
DSCH
Carry information associated with the DCHs
P-CPICH;
S-CPICH
Primary Common Pilot Indicator Channel; Secondary Pilot
Indicator Channel
Helps with channel estimation and shows the attractiveness of the
cell
DPDCH
DPCCH
Dedicated Physical Channels
Uplink and downlink control and data information; Dedicated to a
single user
Version 1 Rev 7 Physical Channels
EMOTOROLA LTD. 2003
CP13: UMTS Overview
717
Physical Channels
Version 1 Rev 7 Channel Mapping
718
Channel Mapping
The diagram opposite summarises the mapping of logical channels onto transport
channels, and transport channels onto physical channels.
The DCHs are coded and multiplexed, as described later in this chapter, 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. Note that 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.
Version 1 Rev 7 Channel Mapping
EMOTOROLA LTD. 2003
CP13: UMTS Overview
719
Channel Mapping
CP13_Ch7_14
CTCH CCCH BCCH PCCH
DCCH
DTCH
DCCH
DTCH
CCCH
DSCH FACH BCH PCH DCH
Primary
CCPCH
Sec
CCPCH
DPDCH
DPCCH
PDSCH
DPDCH
DPCCH
PRACH
DCH CPCH RACH
Uplink Downlink
Paging
Control
Channel
Broadcast
Contro
Channel
Common
Control
Channel
Common
Traffic
Channel
Dedicated
Control Channel
Dedicated
Traffic Channel
Download
Shared
Channel
Physical
Download
Channel
PCPCH
Version 1 Rev 7 Generic Frame Structure
720
Generic Frame Structure
The diagram opposite illustrates the generic frame structure, use to delimit the transfer of
units of information on the UMTS air interface.
Radio Frame
As previously outlined 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
employed, a radio frame thus has a duration of 10 mS.
System Frame
Several physical layer procedures (e.g. Paging and Random Access) span more than a
single frame. 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 uS. 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.
Version 1 Rev 7 Generic Frame Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
721
Generic Frame Structure
CP13_Ch7_29
Time Slot = 2560 chips
TS0 TS1 TSn
Frame
0
Frame
n
TS13 TS14
Frame
4094
Frame
4095
10ms
666s
SLOT
FRAME
SYSTEM FRAME
40.96 secs
Version 1 Rev 7 Synchronisation Channel (SCH)
722
Synchronisation Channel (SCH)
The Synchronisation 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.
The diagram opposite illustrates the structure of the SCH radio frame.
The Primary SCH
The Primary SCH consists of a modulated code of length 256 chips, the Primary
Synchronisation Code (PSC) denoted c
p
in the diagram, transmitted once every slot. The
PSC is the same for every cell in the system.
The Secondary SCH
The Secondary SCH consists of repeatedly transmitting a length 15 sequence of
modulated codes of length 256 chips, the Secondary Synchronisation Codes (SSC),
transmitted in parallel with the Primary SCH. The SSC is denoted c
s
i,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 cells downlink
scrambling code belongs to.
Modulation Symbol a
The primary and secondary synchronization codes are modulated by the symbol a shown
in the diagram, which indicates the presence/ absence of STTD encoding on the
P-CCPCH and is given by the following table:
P-CCPCH STTD encoded a = +1
P-CCPCH not STTD encoded a = -1
Version 1 Rev 7 Synchronisation Channel (SCH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
723
Synchronisation
CP13_Ch7_21
acp
acsi,0
acp
acsi,1
acp
acsi,2
acp
acsi,3
acp
acsi,14
Tslot = 2560 chips
256 chips
Primary
SCH
Secondary
SCH
One 10ms SCH radio frame
Version 1 Rev 7 Synchronisation (Cell Search) Procedure
724
Synchronisation (Cell Search) Procedure
During the cell search, the UE searches for a cell and determines the downlink
scrambling code and frame synchronisation of that cell. The cell search is typically
carried out in three steps:
Step 1: Slot synchronisation
During the first step of the cell search procedure the UE uses the SCHs primary
synchronisation code to acquire slot synchronisation to a cell. This is typically done with a
single matched filter (or any similar device) matched to the primary synchronisation 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 synchronisation and code-group identification
During the second step of the cell search procedure, the UE uses the SCHs secondary
synchronisation code to find frame synchronisation 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 synchronisation 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 synchronisation 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.
Version 1 Rev 7 Synchronisation
EMOTOROLA LTD. 2003
CP13: UMTS Overview
725
Synchronisation
Scrambling
Code Group
slot number
#0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
Group 0 1 1 2 8 9 10 15 8 10 16 2 7 15 7 16
Group 1 1 1 5 16 7 3 14 16 3 10 5 12 14 12 10
Group 2 1 2 1 15 5 5 12 16 6 11 2 16 11 15 12
Group 3 1 2 3 1 8 6 5 2 5 8 4 4 6 3 7
Group 4 1 2 16 6 6 11 15 5 12 1 15 12 16 11 2
Group 5 1 3 4 7 4 1 5 5 3 6 2 8 7 6 8
Group 6 1 4 11 3 4 10 9 2 11 2 10 12 12 9 3
Group 7 1 5 6 6 14 9 10 2 13 9 2 5 14 1 13
Group 8 1 6 10 10 4 11 7 13 16 11 13 6 4 1 16
Group 9 1 6 13 2 14 2 6 5 5 13 10 9 1 14 10
Group 10 1 7 8 5 7 2 4 3 8 3 2 6 6 4 5
Group 11 1 7 10 9 16 7 9 15 1 8 16 8 15 2 2
Group 12 1 8 12 9 9 4 13 16 5 1 13 5 12 4 8
Group 13 1 8 14 10 14 1 15 15 8 5 11 4 10 5 4
Group 14 1 9 2 15 15 16 10 7 8 1 10 8 2 16 9
Group 15 1 9 15 6 16 2 13 14 10 11 7 4 5 12 3
Group 16 1 10 9 11 15 7 6 4 16 5 2 12 13 3 14
Group 17 1 11 14 4 13 2 9 10 12 16 8 5 3 15 6
Group 18 1 12 12 13 14 7 2 8 14 2 1 13 11 8 11
Group 19 1 12 15 5 4 14 3 16 7 8 6 2 10 11 13
Group 20 1 15 4 3 7 6 10 13 12 5 14 16 8 2 11
Group 21 1 16 3 12 11 9 13 5 8 2 14 7 4 10 15
Group 22 2 2 5 10 16 11 3 10 11 8 5 13 3 13 8
Group 23 2 2 12 3 15 5 8 3 5 14 12 9 8 9 14
Group 24 2 3 6 16 12 16 3 13 13 6 7 9 2 12 7
Group 25 2 3 8 2 9 15 14 3 14 9 5 5 15 8 12
Group 26 2 4 7 9 5 4 9 11 2 14 5 14 11 16 16
Group 27 2 4 13 12 12 7 15 10 5 2 15 5 13 7 4
Group 28 2 5 9 9 3 12 8 14 15 12 14 5 3 2 15
Group 29 2 5 11 7 2 11 9 4 16 7 16 9 14 14 4
Group 30 2 6 2 13 3 3 12 9 7 16 6 9 16 13 12
Group 31 2 6 9 7 7 16 13 3 12 2 13 12 9 16 6
Group 32 2 7 12 15 2 12 4 10 13 15 13 4 5 5 10
Group 33 2 7 14 16 5 9 2 9 16 11 11 5 7 4 14
Group 34 2 8 5 12 5 2 14 14 8 15 3 9 12 15 9
Group 35 2 9 13 4 2 13 8 11 6 4 6 8 15 15 11
Group 36 2 10 3 2 13 16 8 10 8 13 11 11 16 3 5
Group 37 2 11 15 3 11 6 14 10 15 10 6 7 7 14 3
Group 38 2 16 4 5 16 14 7 11 4 11 14 9 9 7 5
Group 39 3 3 4 6 11 12 13 6 12 14 4 5 13 5 14
Group 40 3 3 6 5 16 9 15 5 9 10 6 4 15 4 10
Group 41 3 4 5 14 4 6 12 13 5 13 6 11 11 12 14
Group 42 3 4 9 16 10 4 16 15 3 5 10 5 15 6 6
Group 43 3 4 16 10 5 10 4 9 9 16 15 6 3 5 15
Group 44 3 5 12 11 14 5 11 13 3 6 14 6 13 4 4
Group 45 3 6 4 10 6 5 9 15 4 15 5 16 16 9 10
Group 46 3 7 8 8 16 11 12 4 15 11 4 7 16 3 15
Group 47 3 7 16 11 4 15 3 15 11 12 12 4 7 8 16
Group 48 3 8 7 15 4 8 15 12 3 16 4 16 12 11 11
Group 49 3 8 15 4 16 4 8 7 7 15 12 11 3 16 12
Group 50 3 10 10 15 16 5 4 6 16 4 3 15 9 6 9
Group 51 3 13 11 5 4 12 4 11 6 6 5 3 14 13 12
Group 52 3 14 7 9 14 10 13 8 7 8 10 4 4 13 9
Group 53 5 5 8 14 16 13 6 14 13 7 8 15 6 15 7
Group 54 5 6 11 7 10 8 5 8 7 12 12 10 6 9 11
Group 55 5 6 13 8 13 5 7 7 6 16 14 15 8 16 15
Group 56 5 7 9 10 7 11 6 12 9 12 11 8 8 6 10
Group 57 5 9 6 8 10 9 8 12 5 11 10 11 12 7 7
Group 58 5 10 10 12 8 11 9 7 8 9 5 12 6 7 6
Group 59 5 10 12 6 5 12 8 9 7 6 7 8 11 11 9
Group 60 5 13 15 15 14 8 6 7 16 8 7 13 14 5 16
Group 61 9 10 13 10 11 15 15 9 16 12 14 13 16 14 11
Group 62 9 11 12 15 12 9 13 13 11 14 10 16 15 14 16
Group 63 9 12 10 15 13 14 9 14 15 11 11 13 12 16 10
Version 1 Rev 7 Common Pilot Channel (CPICH)
726
Common Pilot Channel (CPICH)
The CPICH is a fixed rate (30 kbps, SF=256) downlink physical channel that carries a
pre-defined bit/symbol sequence. The diagram opposite 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, see figure 14. In case of no transmit diversity, the
symbol sequence of Antenna 1 in figure 14 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.
Primary Common Pilot Channel (P-CPICH)
The Primary Common Pilot Channel (P-CPICH) has the following characteristics:
S The same channelization code is always used for the P-CPICH (SF=256,0).
S The P-CPICH is scrambled by the primary scrambling code.
S There is one and only one P-CPICH per cell.
S 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.
Version 1 Rev 7 Common Pilot Channel (CPICH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
727
CPICH Frame Structure
CP13_Ch7_25
Slot #0 Slot #1 Slot #i Slot #14
Predefined symbol sequence
Tslot = 2560 chips, 20 bits = 10 symbols
1 radio frame: Tf = 10ms
Modulation pattern for Common Pilot Channel
CP13_Ch7_25a
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 1
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#i
Frame Boundary
Frame#i+1
Version 1 Rev 7 P-CCPCH Frame Structure
728
P-CCPCH Frame Structure
The Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channels used
to carry the BCH.
The frame structure of the Primary CCPCH is illustrated opposite.
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.
Version 1 Rev 7 P-CCPCH Frame Structure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
729
P-CCPCH Frame Structure
CP13_Ch7_19
Data
18 bits
Tslot = 2560 chips, 20 bits
Tf = 10ms
(Tx OFF)
256 chips
Version 1 Rev 7 SCH and P-CCPCH
730
SCH and P-CCPCH
The diagram opposite 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 2
Physical Channels are very important to the synchronization process.
Version 1 Rev 7 SCH and P-CCPCH
EMOTOROLA LTD. 2003
CP13: UMTS Overview
731
SCH and P-CCPCH
CP13_Ch7_20
Frame 0
Data on PCCPCH
SCH
Frame 1
Data on PCCPCH Data on PCCPCH
Frame 2
Version 1 Rev 7 Paging Indicator Channel (PICH)
732
Paging Indicator Channel (PICH)
PICH Channel Structure.
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 a S-CCPCH to
which a PCH transport channel is mapped.
The diagram illustrates the frame structure of the PICH. One PICH radio frame of length
10 ms consists of 300 bits (b
0
, b
1
, , b
299
). Of these, 288 bits (b
0
, b
1
, , b
287
) 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 {PI
0
, , PI
N-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 PI
p
, 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):
] ]
]
(
)
(
)
(
) N
N
SFN
SFN SFN SFN PI p
mod
144
144 mod 512 /
64 / 8 / 18
,
_
1
]
1
+ + + + =
The mapping from {PI
0
, , PI
N-1
} to the PICH bits {b
0
, , b
287
} 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.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
733
Structure of Paging Indicator Channel (PICH)
CP13_Ch7_30
One radio frame (10 ms)
288 bits for paging indication
b0
12 bits
(transmission off)
b1 b287b288 b299
Mapping of Paging Indicators (PI) to PICH bits
CP13_Ch7_31
Number of PI per frame (N)
N=18
N=36
N=72
N=144
Plp = 1
{b16p, ...,b16p+15} = {-1,-1,...,-1}
{b8p, ...,b8p+7} = {-1,-1,...,-1}
{b4p, ...,b4p+3} = {-1,-1,...,-1}
{b2p,b2p+1} = {-1,-1}
Plp = 0
{b16p, ...,b16p+15} = {+1,+1,...,+1}
{b8p, ...,b8p+7} = {+1,+1,...,+1}
{b4p, ...,b4p+3} = {+1,+1,...,+1}
{b2p,b2p+1} = {+1,+1}
Discontinuous Reception (DRX) on the PICH
The PICH Channel is used to alert the mobile that a possible paging message will be
broadcast to it on the PCH channel. Each mobile will calculate a paging occasion, which
it listens to for such an alert. In order to save on UE battery life the time between
monitoring the paging occasions can be altered, also the number of paging indicators per
frame that carry the alerts may be configured. These settings are all broadcast in the Cell
system information messages.
The main parameters that determine the time between the UE monitoring its paging
indicator are as follows:
734
DRX Cycle length.
The DRX Cycle Length is made up of a number of system Frames (each 10msecs
duration). It is this period that determines how long the mobile is actually in DRX mode
thus conserving battery power. The cycle is repeated continuously and the UE must only
become active once during each cycle. The duration of the cycle is variable and maybe
altered to suit network conditions.
Paging Occasion.
The Paging Occasion determines the frame number the UE becomes active in, during
the DRX Cycle.
Paging Indicator.
The Paging Indicator is repeated multiple times per System Frame. The UE calculates
which Paging Indicator to listen to using networkdetermined parameters.
The mobile listens to the system information messages to obtain the parameters required
for receiving paging indicators in the selected cell. It then performs a standard calculation
using the cell parameters and its IMSI. The result of this calculation is a single paging
indicator during the DRX cycle time. In other words the mobile must power up and listen
to the calculated paging indicator (now know as its paging occasion) between a repetition
period of 80msecs to 5.12secs (DRX Cycle Period).
The diagram opposite illustrates the frame structure of the PICH.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
735
Discontinuous Reception Parameters on the PICH
Frame. 10msecs
DRX Cycle, 80msecs to 5.12seconds
Paging Indicators 18,36,72 or 144 per 10msecs PICH Frame.
Calculated Paging Occasion
UE is in DRX until this Paging Indicator
CP13_Ch7_21a
Version 1 Rev 7 Secondary Common Control Physical Channel (S-CCPCH)
736
Secondary Common Control Physical Channel (S-CCPCH)
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/2
k
. 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.
Version 1 Rev 7 Secondary Common Control Physical Channel (S-CCPCH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
737
S-CCPCH Frame Structure
CP13_Ch7_23
Data
Ndatabits
Pilot
Npilotbits
TFCI
NTFCIbits
Tslot = 2560 chips, 20*2kbits (k = 0..6)
1 radio frame: Tf = 10ms
Secondary CCPCH Fields
Slot Format
#i
Channel Bit
Rate (kbps)
Channel
Symbol Rate
(ksps)
SF Bits/ Frame Bits/
Slot
N
data
N
pilot
N
TFCI
0 30 15 256 300 20 20 0 0
1 30 15 256 300 20 12 8 0
2 30 15 256 300 20 18 0 2
3 30 15 256 300 20 10 8 2
4 60 30 128 600 40 40 0 0
5 60 30 128 600 40 32 8 0
6 60 30 128 600 40 38 0 2
7 60 30 128 600 40 30 8 2
8 120 60 64 1200 80 72 0 8*
9 120 60 64 1200 80 64 8 8*
10 240 120 32 2400 160 152 0 8*
11 240 120 32 2400 160 144 8 8*
12 480 240 16 4800 320 312 0 8*
13 480 240 16 4800 320 296 16 8*
14 960 480 8 9600 640 632 0 8*
15 960 480 8 9600 640 616 16 8*
16 1920 960 4 19200 1280 1272 0 8*
17 1920 960 4 19200 1280 1256 16 8*
* If TFCI bits are not used, then DTX shall be used in TFCI field.
Version 1 Rev 7 Pysical Random Access Channel (PRACH)
738
Pysical Random Access Channel (PRACH)
Structure of the PRACH
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 diagram opposite.
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
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.
PRACH Pre-amble
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
EMOTOROLA LTD. 2003
CP13: UMTS Overview
739
RACH access slot numbers and their spacing
CP13_Ch7_32
#0 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4 #3 #2 #1 #14
5120
chips
Access slot
radio frame: 10 ms radio frame: 10 ms
Structure of the random-access transmission
CP13_Ch7_33
Message part
10 ms (one radio frame)
Message part
20 ms (two radio frames)
Preamble Preamble Preamble
4096 chips
Preamble Preamble Preamble
4096 chips
740
Structure of PRACH Message Part
The structure of the Random-access message part is shown opposite. 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:
S Existence in uplink only
S Limited data field
S Collision risk
S Open loop power control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
741
Structure of the PRACH Message Part
CP13_Ch7_24
Data
Ndatabits
Pilot
Npilotbits
TFCI
NTFCIbits
Message part radio frame TRACH = 10ms
Data
Control
Random-access message data fields
CP13_Ch7_24a
Slot Format #i
Channel Bit
Rate (kbps)
Channel
Symbol Rate
(ksps)
SF
Bits/
Frame
Bits/Slot Ndata
0 15 15 256 10 10 150
1 30 30 128 20 20 300
2 60 60 64 40 40 600
3 120 120 32 80 80 1200
Version 1 Rev 7 Acquisition Indicator Channel AICH)
742
Acquisition Indicator Channel AICH)
The Acquisition Indicator channel (AICH) is a fixed rate (SF=256) physical channel used
to carry Acquisition Indicators (AI). Acquisition Indicator AI
s
corresponds to signature s
on the PRACH.
The diagram opposite 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 a
0
, , a
31
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 a
0
, a
1
, , a
31
are given by
=
=
15
0
j s, s j
b AI a
s
where AI
s
, taking the values +1, -1, and 0, is the acquisition indicator corresponding to
signature s and the sequence b
s,0
, , b
s,31
is given in the table opposite. The
real-valued symbols, a
j
, are spread and modulated in the same fashion as bits when
represented in { +1, -1 } form.
Version 1 Rev 7 Acquisition Indicator Channel AICH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
743
Structure of Acquisition Indicator Channel (AICH)
CP13_Ch7_34
AS # 14 AS # 0 AS # 1 AS # i AS # 14 AS # 0
20 ms
a0 a31 a30 a2 a1 Transmission Off
Al part = 4096 chips, 32 realvalued symbols 1024 chips
AICH signature patterns
s b
s,0
, b
s,1
, b
s,31
0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1
2 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1
3 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1
4 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1
5 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1
6 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1
7 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1
8 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
9 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1
10 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1
11 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1
12 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1
13 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1
14 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -1 -1
15 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1
Version 1 Rev 7 Relationship Between PRACH and AICH
744
Relationship Between PRACH and AICH
The PRACH contains two sets of access slots as shown below. Access slot set 1
contains PRACH slots 0 7 and starts
pa
chips before the downlink PCCPCH frame
for which SFN mod 2 = 0. Access slot set 2 contains PRACH slots 8 14 and starts
(
pa
2560) chips before the downlink PCCPCH frame for which SFN mod 2 = 1.
AICH access
slots
10 ms
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
pa
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
PRACH
access slots
SFN mod 2 = 0 SFN mod 2 = 1
10 ms
Access slot set 1 Access slot set 2
Version 1 Rev 7 Relationship Between PRACH and AICH
EMOTOROLA LTD. 2003
CP13: UMTS Overview
745
PRACH/AICH Relationship
AICH access
slots
10 ms
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
pa
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
PRACH
access slots
10 ms
Version 1 Rev 7 Downlink Dedicated Physical Channels (DL-DPCH)
746
Downlink Dedicated Physical Channels (DL-DPCH)
DL-DPCH Structure
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, i.e. 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.
The diagram opposite shows the frame structure of the downlink DPCH. Each frame of
length 10 ms is split into 15 slots, each of length T
slot
= 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/2
k
. The spreading factor may thus range from 512 down to 4. The exact
number of bits of the different downlink DPCH fields (N
pilot
, N
TPC
, N
TFCI
, N
data1
and
N
data2
) 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 (e.g. for several simultaneous services) and those that do not include TFCI
(e.g. 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.
TPC Bit Pattern Transmitter power
control command
N
TPC
= 2 N
TPC
= 4 N
TPC
= 8
11
00
1111
0000
1111 1111
00000000
1
0
EMOTOROLA LTD. 2003
CP13: UMTS Overview
747
Frame Structure for Downlink DPCH
CP13_Ch7_16
Data 1 TPC TFCI Data 2 Pilot
Npilot bits
DPDCH DPCCH DPDCH DPCCH
One radio frame = 10ms
Tslot = 2560 chips
748
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, i.e. 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.
TFCI Transport Formation Combination Indicator
DCH Dedicated Channel
CCTrCH Coded Composite Transport Channel
DPCH Dedicated Physical Channel
TPC Transmit Power Control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
749
Downlink Slot Format in Case of Multi-Code Transmission
CP13_Ch7_17
TPC TFCI
Pilot
DPDCH
DPDCH
One Slot (2560 chips)
Physical Channel 1
Physical Channel L
Physical Channel 2
Transmission
Power
Transmission
Power
Transmission
Power
Version 1 Rev 7 Uplink Dedicated Physical channels (UL-DPCH)
750
Uplink Dedicated Physical channels (UL-DPCH)
There are two types of uplink dedicated physical channels, the uplink Dedicated Physical
Data Channel (uplink DPDCH) and the 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 one and only one uplink DPCCH on each radio link.
The diagram opposite 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 T
slot
=
2560 chips, corresponding to one power-control period.
The parameter k in the diagram determines the number of bits per uplink DPDCH slot. It
is related to the spreading factor SF of the DPDCH as SF = 256/2
k
. The DPDCH
spreading factor may range from 256 down to 4, giving data rates between 15kbs and
960kbs The spreading factor of the uplink DPCCH is always equal to 256, i.e. 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 (e.g.
for several simultaneous services) and those that do not include TFCI (e.g. 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.
Version 1 Rev 7 Uplink Dedicated Physical channels (UL-DPCH)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
751
Frame Structure for Uplink DPDCH/DPCCH
CP13_Ch7_18
DPDCH
DPCCH
Data
Ndatabits
Pilot
Npilotbits
TFCI
NTFCIbits
FBI
NFBIbits
TPC
NTPCbits
Tf = 10ms
Version 1 Rev 7 The Random Access Procedure in Detail
752
The Random Access Procedure in Detail
Random access parameters
PRACH
Access Slot (FDD only).
Preamble scrambling code (FDD only).
Available preamble signatures (FDD only).
Spreading factor for data part.
Power control info:
UL target SIR;
primary CCPCH DL TX Power;
UL interference;
power offset (Power ramping) (FDD only).
Access Service Class Information (PRACH Partitioning):
Available signatures for each ASC (FDD only).
Available Subchannels for each ASC.
AICH transmission timing parameter (FDD only).
Physical random access procedure
The physical randomaccess procedure shall be performed as follows:
1. Derive the available uplink access slots, in the next full access slot set, for the set
of available RACH subchannels within the given ASC. Randomly select one
access slot among the ones previously determined. If there is no access slot
available in the selected set, randomly select one uplink access slot corresponding
to the set of available RACH subchannels within the given ASC from the next
access slot set. The random function shall be such that each of the allowed
selections is chosen with equal probability.
2. Randomly select a signature from the set of available signatures within the given
ASC. The random function shall be such that each of the allowed selections is
chosen with equal probability.
3. Set the Preamble Retransmission Counter to Preamble Retrans Max.
4. Set the parameter Commanded Preamble Power to Preamble_Initial_Power.
5. In the case that the Commanded Preamble Power exceeds the maximum allowed
value, set the preamble transmission power to the maximum allowed power. In the
case that the Commanded Preamble Power is below the minimum level required,
set the preamble transmission power to a value, which shall be at or above the
Commanded Preamble Power and at or below the required minimum power.
Otherwise set the preamble transmission power to the Commanded Preamble
Power. Transmit a preamble using the selected uplink access slot, signature, and
preamble transmission power.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
753
Decrement Preamble Transmission
counter M
Y
N
Indicate to higher layer
that maximum number of
preamble cycles have been
reached (TX status
unsuccessful)
Ack
(PRACH message part transmitted)
End
N
Y
M = Mmax
N
Y
NOTE: MACc/sh receives
RACH tx control parameters from
RRC with CMACCONFIGReq
primitive whenever one of the
parameters is updated
ASC selection:
End
Start
Get RACH tx control parameters
from RRC: M
max
, N
B02min
,
N
B01Max
, set of ASC parameters
Any data to be
transmitted?
M = 0
Update RACH tx control
parameters
Set Timer T
2
(10 ms)
Wait expiry
Time T
2
(10ms)
Wait expiry
Time T
2
(10ms)
Set and wait expiry
timer T
B01
(N
B01
*10ms)
(PRACH partition i, P
i
)
Draw random number 0pR
i<1
Rp
Pi
?
Send PHYACCESS=REQ
(start of L1 PRACH
transmission procedure)
Wait expiry
Time T
2
(10ms)
L1 access info?
No Ack Nack
Send PHYDATA=REQ
indicate TX status to higher
layer
754
6. If no positive or negative acquisition indicator (AI +1 nor 1) corresponding to the
selected signature is detected in the downlink access slot corresponding to the
selected uplink access slot:
i. Select the next available access slot in the set of available RACH
subchannels within the given ASC.
ii. Randomly select a new signature from the set of available signatures within
the given ASC. The random function shall be such that each of the allowed
selections is chosen with equal probability.
iii. Increase the Commanded Preamble Power by P
0
= Power Ramp Step
[dB]. If the Commanded Preamble Power exceeds the maximum allowed
power by 6dB, the UE may pass L1 status (No ack on AICH) to the higher
layers (MAC) and exit the physical random access procedure.
iv. Decrease the Preamble Retransmission Counter by one.
v. If the Preamble Retransmission Counter > 0 then repeat from step 5.
Otherwise pass L1 status (No ack on AICH) to the higher layers (MAC)
and exit the physical random access procedure.
7. If a negative acquisition indicator corresponding to the selected signature is
detected in the downlink access slot corresponding to the selected uplink access
slot, pass L1 status (Nack on AICH received) to the higher layers (MAC) and exit
the physical random access procedure.
8. Transmit the random access message three or four uplink access slots after the
uplink access slot of the last transmitted preamble depending on the AICH
transmission timing parameter. Transmission power of the control part of the
random access message should be P pm [dB] higher than the power of the last
transmitted preamble. Transmission power of the data part of the random access
message is set according to subclause 5.1.1.2.
9. Pass L1 status RACH message transmitted to the higher layers and exit the
physical random access procedure.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
755
Decrement Preamble Transmission
counter M
Y
N
Indicate to higher layer
that maximum number of
preamble cycles have been
reached (TX status
unsuccessful)
Ack
(PRACH message part transmitted)
End
N
Y
M = Mmax
N
Y
NOTE: MACc/sh receives
RACH tx control parameters from
RRC with CMACCONFIGReq
primitive whenever one of the
parameters is updated
ASC selection:
End
Start
Get RACH tx control parameters
from RRC: M
max
, N
B02min
,
N
B01Max
, set of ASC parameters
Any data to be
transmitted?
M = 0
Update RACH tx control
parameters
Set Timer T
2
(10 ms)
Wait expiry
Time T
2
(10ms)
Wait expiry
Time T
2
(10ms)
Set and wait expiry
timer T
B01
(N
B01
*10ms)
(PRACH partition i, P
i
)
Draw random number 0pR
i<1
Rp
Pi
?
Send PHYACCESS=REQ
(start of L1 PRACH
transmission procedure)
Wait expiry
Time T
2
(10ms)
L1 access info?
No Ack Nack
Send PHYDATA=REQ
indicate TX status to higher
layer
756
ASC to Access Class Mapping
All UEs are members of one out of ten randomly allocated mobile populations, defined as
Access Classes 0 to 9. The population number is stored in the SIM/USIM. In addition,
mobiles may be members of one or more out of 5 special categories (Access Classes 11
to 15), also held in the SIM/USIM. These are allocated to specific high priority users as
follows. (The enumeration is not meant as a priority sequence):
Class 15 PLMN Staff
Class 14 Emergency Services
Class 13 Public Utilities (e.g. water/gas suppliers)
Class 12 Security Services
Class 11 For PLMN Use
If the UE is a member of at least one Access Class, which corresponds to the permitted
classes as signalled over the air interface, and the Access Class is applicable in the
serving network, access attempts are allowed. Otherwise access attempts are not
allowed.
Access Classes are applicable as follows:
Class 09 Home and Visited PLMNs
Class 11 and 15 Home PLMN only
Classes 12, 13, 14 Home PLMN and visited PLMNs of
home country only.
Any number of these classes may be barred at any one time.
An additional control bit known as Access Class 10 is also signalled over the air
interface to the UE. This indicates whether or not network access for Emergency Calls is
allowed for UEs with access classes 0 to 9 or UEs without an IMSI. For UEs with access
classes 11 to 15, Emergency Calls are not allowed if both Access class 10 and the
relevant Access Class (11 to 15) are barred. Otherwise, Emergency Calls are allowed.
All Emergency Calls use ASC
0
, and all ACs being in the range from 0 to 9 are mapped to
ASC
1
.
The AC10 to AC15 are in turn mapped to ASC
i
, where i=2,,7 respectively. Mapping
function is specified by fixed assignment AC to ASC based on OMC provisioned
parameters.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
757
Access Service Class to Access Class Mapping
AC
ASC
09
1st IE
10
2nd IE
11
3rd IE
12
4th IE
13
5th IE
14
6th IE
15
7th IE
AC
ASC
09
1
10
0
11
2
12
4th IE
13
5th IE
14
6th IE
15
7th IE
AC
ASC
09
1
10
0
11
3
12
4
13
5th IE
14
6th IE
15
7th IE
Partitions not available (i.e. not configured)
CP13_Ch7_p72
RACH access slot sets
The PRACH contains two sets of access slots as shown in Figure 2. Access slot set 1
contains PRACH slots 0 7 and starts pa chips before the downlink PCCPCH frame
for which SFN mod 2 = 0. Access slot set 2 contains PRACH slots 8 14 and starts
(pa 2560) chips before the downlink PCCPCH frame for which SFN mod 2 = 1.
RACH sub-channels
A RACH subchannel defines a subset of the total set of uplink access slots. There are
a total of 12 RACH subchannels. RACH subchannel #i (i = 0, , 11) consists of the
following uplink access slots:
Uplink access slot #i leading by
pa
chips the downlink access slot #i contained within
the 10 ms interval that is time aligned with PCCPCH frames for which SFN mod 8 = 0
or SFN mod 8 = 1.
Every 12
th
access slot relative to this access slot.
The access slots of different RACH subchannels are also illustrated in the Table below.
Table 7-1 The available uplink access slots for different RACH subchannels
Sub-channel number
SFN modulo 8 of
corresponding
P-CCPCH frame
0 1 2 3 4 5 6 7 8 9 10 11
758
Sub-channel number
0 0 1 2 3 4 5 6 7
1 12 13 14 8 9 10 11
2 0 1 2 3 4 5 6 7
3 9 10 11 12 13 14 8
4 6 7 0 1 2 3 4 5
5 8 9 10 11 12 13 14
6 3 4 5 6 7 0 1 2
7 8 9 10 11 12 13 14
Each 10msecs RACH frame is associated with a set of sub channel numbers as shown
in the table above. There are 12 sub channels for each 10msec RACH frame. Each sub
channel number is either associated with a RACH access slot number or it there is no
association and the field is blank. Remember there are 15 RACH access slots
EMOTOROLA LTD. 2003
CP13: UMTS Overview
759
RACH Access Slot Availability
AICH access
slots
10 ms
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
pa
#0 #1 #2 #3 #14 #13 #12 #11 #10 #9 #8 #7 #6 #5 #4
PRACH
access slots
10 ms
RACH Sub-Channels
Sub-channel number
SFN modulo 8
of
corresponding
P-CCPCH
frame
0 1 2 3 4 5 6 7 8 9 10 11
0 0 1 2 3 4 5 6 7
1 12 13 14 8 9 10 11
2 0 1 2 3 4 5 6 7
3 9 10 11 12 13 14 8
4 6 7 0 1 2 3 4 5
5 8 9 10 11 12 13 14
6 3 4 5 6 7 0 1 2
7 8 9 10 11 12 13 14
760
The Sub Channel frames are repeated over a cycle of eight 10msecs frames (Modulo 8).
Each of the eight sub channel frames indicates different RACH access slot availability.
The UE will use the current Sub channel frame as part of the decision in selecting a
RACH access slot in which to transmit.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
761
RACH Subchannels
CP13_Ch7_24b
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 1 2 3 4
10msecs
10msecs
RACH ACCESS SLOTS
Frame 0 1 2 3 4 0 5 6 77
Frame 1
13 14 12 8 9 10 11
1 2 3 4
Frame 2
0 5 6 7
Sub Channel Number
0 1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
2 3 4 5 6 7 8 9 10 11
0 1 2 3 4 5 6 7 8 9 10 11
0 1 2 3 4 5 6 7 8 9 10 11
762
Each Access Service class is mapped to a network parameter Assigned sub channel
number. This is broadcast in System information number 5 for every cell. The parameter
is made up of 3 or 4 bits that are repeated 4 or 3 times in order to make up a 12 bit
pattern. This pattern is then logically anded to a parameter Available Sub channel
number. This is a 12 bit bitmap which represents the available sub channel numbers for
each access service class. The result of this and operation is then combined again with
the current sub channel frame. The result of this is another 12 bit bitmap where a logical
1 indicates the indicated sub channel is available for use (and consequently the RACH
Access Slot) and a 0 means it cannot be used. This is illustrated in the diagram opposite.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
763
CP13_Ch7_Rach access slot avail
The b Bitmaps are logically added to the 12 bit Bitmap using the AND function
Sub Slots Allowed 12 Bit Bitmap
Sub Slots Allowed 12 Bit Bitmap
&
=
Frame 1
The Result Of combining Sub slots allowed, b bits and Sub channels allowed is sub channels 9 and 11
Thus a mobile in an Access Service class with this set of b bits may choose partion 9 or 11 for this frame
For this frame the UE would choose from
partitions 13, 9 or 11.
&
b3, b2, b1, b0 or b2, b1, b0 are set for each Access Service Class
.
They are repeated 3 or 4 times to make a bitmap of 12 Bits
0 1 0 0 1 1 0 0 0 1 1 0
b1 b2 b0 b1 b2 b0 b1 b2 b0 b1 b2 b0
1 0 1 1 0 1 1 0 1 1 0 1
0 0 0 0 0 0 0 0 1 1 1 0
0 1 0 0 1 1 0 0 0 1 1 0
b1 b2 b0 b3 b1 b2 b0 b3 b1 b2 b0 b3
1 0 1 1 1 0 1 1 1 0 1 1
0 1 0 0 1 1 0 0 0 1 1 0
12 13 14 8 9 10 11
0 0 0 0 0 1 0 0 0 1 0 1
12 13 14 8 9 10 11
0 1 0 0 1 1 0 0 0 1 0 1
764
Persistence Value and PRACH Partitioning
Each Access Service class (ASC) is defined by an identifier I (07). This identifier is then
mapped to one of more PRACH Access Slots (max 15). The mapped slots are then
known as a PRACH Partition. One or more ASC maybe mapped to the same PRACH
Access slot therefore the subsequent partitions for each ASC may overlap each other.
Associated with each ASC is a Persistence value. This value (18) is used to influence
the probability of a PRACH Preamble being transmitted in the selected PRACH access
slot.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
765
Persitence Value and PRACH Partitioning
An ASC Is defined by an identifier, i, that defines a
certain partition of the PRACH resources and an
associated persistence value P
i
The persistence values Pi to be associated with each
ASC shall be derived from the dynamic persistence
level N = 1, ... , 8
CP13_Ch7_p63
ASC #1
P(N) P(N) P(N) P(N) P(N) P(N) P(N) 1 P
i
0 1 2 3 4 5 6 7
766
Calculating the persistence value
The Persistence value is between 1 and 8 and is determined by the network for each
ASC. The Value programmed is multiplied in the formula P(N) = 2 (N1). The values
that result are between 0 and 1. These are then compared with a Random Number
between 0 and 1, in 0.1 steps, generated by the UE. If the Persistence value is equal or
less than the random number then the Access procedure is allowed to continue. If it is
greater then the UE must wait 10msecs and try again with a new set of values.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
767
Calculating the Persistence Value
Example

if

N

=

2

the

P(N)

=

0.5
The UE chooses a random number between 0 and 1
in 0.1 steps. It then compares this with the P(N)
value and if equal or less it can then continue with
the access procedure, if not it tries again 10msecs
later
ASC #1
P(N) P(N) P(N) P(N) P(N) P(N) P(N) 1 P
i
0 1 2 3 4 5 6 7
P(N)

=

2

(N1) N

=

1

to

8
S = 0 to 1 in 0.1 steps
CP13_Ch7_p65
768
Scaling Factor
The Scaling Factor is optional and if implemented only applies to ASC 2 to 7. If
implemented the Scaling Factor has the effect of altering the probability of the access
procedure continuing onto transmission of a preamble or waiting 10msecs and
recalculating all access parameters again. The example opposite shows how the access
procedure is allowed if a scaling factor is applied but not allowed if it was not applied. The
Scaling Factor maybe dynamically controlled by the network for access control
procedures. It has a range of 0 to 1 in 0.1 steps and is multiplied with the calculated
Persistence value to produce the new result for comparison with the UE generated
Random number.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
769
Scaling Factor
Example:

with

a

persistence

value

of

0.5

and

a

random

number

of
0.4

the

access

procedure

would

not

continue.

If

a

scaling

factor

of
0.1

were

applied,

the

new

persistence

value

would

be

0.05

and

the
UE

would

be

able

to

continue

with

the

access

procedure
ASC #1
S
5
P(N) S
6
P(N) S7P(N) S
4
P(N) S
3
P(N) S
2
P(N) P(N) 1 P
i
0 1 2 3 4 5 6 7
The

Scaling

Factor

is

optional

and

if

implemented

only

applies

to
Access

service

classes

2

to

7.
The Scaling Factor value can be within the range of
0 in 0.1 increments.
If implementing the Scaling Factor has the effect of
altering the probability of access procedure
continuing by making the persistence value smaller
or larger.
CP13_Ch7_p67
770
PRACH/Access Service Class/ Sub channel/Signature Mapping
The diagram opposite shows several PRACH channels and their mapping to preamble
scrambling codes, Access Service Classes, Sub channels and available preamble
signatures. It also shows that the different ASCs are mapped to different PRACH slots.
Each preamble signature is also associated to a particular PRACH access slot (015).
In this way Partitions maybe created for the exclusive use of particular ASCs. Note
though that it is also possible for all ASCs to share the same preamble signature, sub
channel and preamble scrambling code as this is a contention based access system
and collisions are possible between UEs requesting network resources.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
771
PRACH/Access Service Class/Subchannel/Signature
Mapping
a
v
a
i
l
a
b
l
e

p
r
e
a
m
b
l
e

s
i
g
n
a
t
u
r
e
s

(
m
a
x

1
6
)
a
v
a
i
l
a
b
l
e
s
u
b
c
h
a
n
n
e
l
s
(
m
a
x

1
2
)
P
R
A
C
H

p
a
r
t
i
t
i
o
n
s
(
o
n
e

p
a
r
t
i
t
i
o
n

p
e
r

A
S
C
,
m
a
x
.

8

p
e
r

P
R
A
C
H
)
A
S
C

0
A
S
C

1
A
S
C

2
A
S
C

0
A
S
C

1
A
S
C

2
P
R
A
C
H
(
m
a
x

1
6

p
e
r

c
e
l
l
)
P
R
A
C
H

0
P
R
A
C
H

1
R
A
C
H
(
m
a
x

1
6

p
e
r

c
e
l
l
)
R
A
C
H

0
R
A
C
H

1
P
r
e
a
m
b
l
e

s
c
r
a
m
b
l
i
n
g

c
o
d
e
(
m
a
x

1
6

p
e
r

c
e
l
l
)
P
r
e
a
m
b
l
e
s
c
r
a
m
b
l
i
n
g
c
o
d
e

0
P
r
e
a
m
b
l
e
s
c
r
a
m
b
l
i
n
g
c
o
d
e

1
0
1
5
0
1
1
0
1
5
0
1
1
A
S
C

3
A
S
C

0
A
S
C

1
A
S
C

2
P
R
A
C
H

2
R
A
C
H

2
P
r
e
a
m
b
l
e
s
c
r
a
m
b
l
i
n
g
c
o
d
e

2
0
9
0
1
1
A
S
C

0
A
S
C

1
P
R
A
C
H

3
R
A
C
H

3
P
r
e
a
m
b
l
e
s
c
r
a
m
b
l
i
n
g
c
o
d
e

2
1
0
1
5
0
1
1
P
a
r
t
i
t
i
o
n

n
o
t

a
v
a
i
l
a
b
l
e
o
n

P
R
A
C
H

2
P
a
r
t
i
t
i
o
n

n
o
t

a
v
a
i
l
a
b
l
e
o
n

P
R
A
C
H

3
C
o
d
i
n
g
C
o
d
i
n
g
C
o
d
i
n
g
C
o
d
i
n
g
CP13_Ch7_p69
Version 1 Rev 7 PCPCH (Physical Common Packet Channel) and Associated Physical Signals
772
PCPCH (Physical Common Packet Channel) and Associated
Physical Signals
Physical Channels/Signals Required to support the CPCH
The Following parameters are required for the PCPCH:
PCPCH
CPCH Set ID to which this PCPCH belongs.
Parameters related to the AP preamble:
Access Preamble (AP) scrambling code;
available AP signatures/sub channels for access request;
Parameters related to the CD preamble:
CD preamble scrambling code;
available CD signatures/subchannels;
Parameters related to PCPCH message part:
PCPCH scrambling code;
PCPCH Channelisation code;
data rate (spreading factor);
N_frames_max: Maximum length of CPCH message in radio frames.
CD/CAICH
CPCH Set ID.
Scrambling code.
Channelisation code.
Tx diversity mode.
NOTE This physical channel is used in conjunction with PCPCH when
Channel Assignment is active.
CSICH
CPCH Set ID.
Scrambling code.
Channelisation code.
Tx diversity mode.
NOTE The values for the parameters need to be consistent with the
APAICH that is timemultiplexed with this CSICH.
DLDPCCH for CPCH
The downlink DPCCH for CPCH is a special case of downlink dedicated physical
channel of the slot format #0. The spreading factor for the DLDPCCH is 512
EMOTOROLA LTD. 2003
CP13: UMTS Overview
773
Channels required to support an UL Common Packet
Channel
S Pysical Common Packet Channel - PCPCH
S Access Preamble Acquisition Indicator Channel
(AP-AICH)
S Collision Detection/Channel Assignment Indicator
Channel - CD/CA-ICH
S CPCH Status Indicator Channel - CSICH
S Downlink Dedicated Physical Control Channel for
CPCH - DL-DPCCH for CPCH
CP13_Ch7_p74
774
CPCH Status Indicator Channel (CSICH)
In order to avoid unnecessary access attempts when all CPCH channels are occupied,
thus improving CPCH throughput, the UE will ascertain the current status of the CPCHs
using the CSICH.
The CSICH Broadcasts Status Indicators (SIs), which convey the following information:
S When Channel Assignment is NOT Active
In this mode, the CSICH conveys the PCPCH Channel Availability value, which is
a 1 to 16 bit value which indicates the availability of each of the 1 to 16 defined
PCPCHs in the PCPCH set. This information is known as the PCPCH Resource
Availability Value (PRA).
S When Channel Assignment is Active
in this mode, the CSICH conveys two pieces of information. Firstly the PRA value
of the 1 to 57 defined PCPCHs. Secondly the Minimum Available Spreading
Factor (MASF) value indicates the MASF that can be supported by the CCPCH
set. All spreading factors greater than the MASF are available.
The CSICH is a fixed rate (SF=256) physical channel used to carry CPCH status
information and May share the same physical channel resources as the AICH
(Channelization and scrambling codes). A CSICH is always associated with a physical
channel used for transmission of CPCH APAICH and uses the same channelization and
scrambling codes.
The figure opposite illustrates the frame structure of the CSICH. The CSICH frame
consists of 15 consecutive access slots (AS) each of length 40 bits. Each access slot
consists of two parts, a part of duration 4096 chips with no transmission that is not
formally part of the CSICH, and a Status Indicator (SI) part consisting of 8 bits
b
8i
,.b
8i+7
, where i is the access slot number. The part of the slot with no transmission is
reserved for use by AICH, APAICH or CD/CAICH. The modulation used by the CSICH
is the same as for the PICH. The phase reference for the CSICH is the Primary CPICH.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
775
Structure of CPCH Status Indicator Channel (CSICH)
AS #14 AS #0 AS #1 AS #i AS #14 AS #0
b
8i
b
8i+1
4096 chips
Transmission off
SI part
20 ms
b
8i+7
b
8i+6
CP13_Ch7_p76
776
CPCH transmission
The CPCH transmission is based on DSMACD approach with fast acquisition indication.
The UE can start transmission at the beginning of a number of welldefined
timeintervals, relative to the frame boundary of the received BCH of the current cell.
The access slot timing and structure is identical to RACH.
Having determined, by monitoring the CSICH, that CPCH resources are currently
available, the UE will, when requested by the MAC layer, commence the actual access
procedure, as follows:
Access Segment
The UE starts transmission of Access Preambles on a randomly selected PCPCH from
the set of available PCPCH Channels, using a randomly selected CPCH-AP signature
from the set of available signatures, at the initial power level (P
CPCH
) supplied by the
MAC layer.
If the UE does not detect the Positive or negative acquisition indicator (AI) corresponding
to the the selected signature in the downlink AP-AICH slot corresponding to the selected
uplink slot, the will re-check the PRA of the selected PCPCH, and if it is found to be
unavailable, the procedure will be aborted and a failure message sent to the MAC layer.
Provided the SI still shows the selected PCPCH as available, the UE will select the next
available access slot on the selected PCPCH, Increase the preamble transmission power
by the specified offset P, decrease the AP retransmission counter (if the AP
retransmission counter < 0, the UE aborts the access attempt) and repeats the AP
Transmission.
On receipt of a positive acknowledgement (the AP-AICH signature corresponds to the AP
signature), the access segment ends and the contention resolution segment
commences. If a negative acknowledgement is received (AP-AICH and AP signatures
do not match), the UE aborts the access attempt.
Contention Resolution Segment
So far the PCPCH access procedure has been identical to that of the PRACH access
procedure and thus only a very simple contention resolution procedure has been
completed. It is therefore still possible that more than one UE has Accepted the positive
acknowledgement, with the potential for data collision when their data parts are
subsequently transmitted. As each PRACH message part transmission can only last a
maximum of two radio frames, this is of little significance. However, on the PCPCH, the
UE may be expected to transmit a significant amount of data (up to 64 radio frames
duration), with data collisions severely degrading the QoS of the service. Further steps
are thus introduced to counter this problem.
In the contention resolution segment the UE randomly selects a Collision Detection (CD)
signature from the CD signature set, selects a a CD access slot sub-channel from the
CD sub-channel group supported in the cell and transmits a CD preamble at the same
power level as the last AP, then waits for the CD/CA-ICH.
Receipt of a positive CD-I (CD-I Signature matches CD signature), enable the UE to
proceed with a Power Control preamble Transmission on the selected PCPCH. If
Channel Assignment is active, the CD/CA-ICH will also carry a Channel Assignment
Indicator (CA-I), indicating on which PCPCH to transmit, this may be the UE selected
PCPCH or an alternative selected by the network.
If at anytime no acknowledgement or a negative acknowledgement is received, the UE
will abort the procedure.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
777
Structure of CPCH transmission
APAICH
APs
P0
P1 P1
0 or 8 slots
Power Control
Preamble
Information
and
Control Data
Power Control, Pilot and CPCH
control commands
Ta
pp
pcdp cdppcp
pa1 a1cdp cdpa2
DPCCH (DL)
PCPCH (UL)
[Example shown is for Tcpch=0]
CD/CA
CD/CAICH
CP13_Ch7_p78
778
CPCH Access Preamble Acquisition Indicator Channel (APAICH)
The Access Preamble Acquisition Indicator channel (APAICH) is a fixed rate (SF=256)
physical channel used to carry AP acquisition indicators (API) of CPCH. AP acquisition
indicator API
s
corresponds to AP signature s transmitted by UE.
APAICH and AICH may use the same or different channelisation codes. The phase
reference for the APAICH is the Primary CPICH. The Figure below illustrates the
structure of APAICH. The APAICH has a part of duration 4096 chips where the AP
acquisition indicator (API) is transmitted, followed by a part of duration 1024chips with no
transmission that is not formally part of the APAICH. 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 channelisation of the APAICH is 256.
1024 chips
Transmission Off
AS #14 AS #0 AS #1 AS #i AS #14 AS #0
a
1
a
2
a
0
a
31
a
30
API part =4096 chips, 32 realvalued symbols
20 ms
CP13_Ch7_p79
EMOTOROLA LTD. 2003
CP13: UMTS Overview
779
Structure of AP Acquisition Indicator Channel (AP-AICH)
1024 chips
Transmission Off
AS #14 AS #0 AS #1 AS #i AS #14 AS #0
a
1
a
2
a
0
a
31
a
30
API part =4096 chips, 32 realvalued symbols
20 ms
CP13_Ch7_p80
780
CPCH Collision Detection/Channel Assignment Indicator Channel (CD/CAICH)
The Collision Detection Channel Assignment Indicator channel (CD/CAICH) is a fixed
rate (SF=256) physical channel used to carry CD Indicator (CDI) only if the CA is not
active, or CD Indicator/CA Indicator (CDI/CAI) at the same time if the CA is active. The
structure of CD/CAICH is shown below. CD/CAICH and APAICH may use the same
or different channelisation codes.
The CD/CAICH has a part of duration of 4096chips where the CDI/CAI is transmitted,
followed by a part of duration 1024chips with no transmission that is not formally part of
the CD/CAICH. 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 channelisation of the CD/CAICH is 256.
1024 chips
Transmission Off
AS #14 AS #0 AS #1 AS #i AS #14 AS #0
a
1
a
2
a
0
a
31
a
30
CDI/CAIpart =4096 chips, 32 realvalued symbols
20 ms
CP13_Ch7_p81
EMOTOROLA LTD. 2003
CP13: UMTS Overview
781
Structure of CD/CA Indicator Channel (CD/CA-ICH)
1024 chips
Transmission Off
AS #14 AS #0 AS #1 AS #i AS #14 AS #0
a
1
a
2
a
0
a
31
a
30
CDI/CAIpart =4096 chips, 32 realvalued symbols
20 ms
CP13_Ch7_p82
782
Power Control Preamble Segment
Having passed contention resolution, the UE may optionally commence a power control
preamble segment.
The UE transmits a Power Control Preamble, starting at a specified time intervals
measured from the commencement of the CD Preamble. The initial transmission power
of the power control preamble shall be Ppm [dB] higher than the power of the CD
preamble.
A PCPCH power control preamble is a period when both the UL PCPCH control part and
the associated DL DPCCH are transmitted prior to the start of the uplink PCPCH data
part.
The length of the power control preamble is a higher layer parameter, Lpcpreamble and
can take the value 0 slots or 8 slots. The uplink PCPCH data part shall not commence
before the end of the power control preamble.
Message Part
The transmission of the message portion of the burst starts immediately after the power
control preamble. Power control in the message part is conducted using the DL DPCCH.
During the first few frames of the Data Transmission, the UE tests the value of Start of
Message Indicator received from DLDPCCH for CPCH during the first NStart_Message
frames after Power Control preamble. Start of Message Indicator is a known sequence
repeated on a frame by frame basis. The value of NStart_Message shall be provided by
the higher layers. If the UE does not detect Start of Message Indicator in the first
NStart_Message frames of DLDPCCH for CPCH after Power Control preamble, the UE
aborts the access attempt and sends a failure message to the MAC layer. Otherwise, UE
continuously transmits the packet data.
If the UE detects loss of DPCCH DL during transmission of the power control preamble
or the packet data, the UE halts CPCH UL transmission, aborts the access attempt and
sends a failure message to the MAC layer.
The UE may send empty frames after the end of the packet to indicate the end of
transmission. The number of the empty frames is set by higher layers.
NOTE If the Lpcpreamble parameter indicates a zero length preamble,
then there is no power control preamble and the message
portion of the burst starts cdppcp ms after the initiation of
the CD Preamble. In this case the initial transmission power of
the control part of the message part shall be Ppm [dB] higher
than the power of the CD preamble.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
783
Structure of CPCH transmission
APAICH
APs
P0
P1 P1
0 or 8 slots
Power Control
Preamble
Information
and
Control Data
Power Control, Pilot and CPCH
control commands
Ta
pp
pcdp cdppcp
pa1 a1cdp cdpa2
DPCCH (DL)
PCPCH (UL)
[Example shown is for Tcpch=0]
CD/CA
CD/CAICH
CP13_Ch7_p84
784
Physical Common Packet Channel (PCPCH)
The CPCH transmission is based on DSMACD approach with fast acquisition indication.
The UE can start transmission at the beginning of a number of welldefined
timeintervals, relative to the frame boundary of the received BCH of the current cell.
The access slot timing and structure is identical to RACH.
The PCPCH access transmission consists of one or several Access Preambles [AP] of
length 4096 chips, one Collision Detection Preamble (CDP) of length 4096 chips, a
DPCCH Power Control Preamble (PCP) which is either 0 slots or 8 slots in length, and
a message of variable length Nx10 ms.
Each message consists of up to N_Max_frames 10 ms frames. N_Max_frames is a
higher layer parameter. Each 10 ms frame is split into 15 slots, each of length
T
slot
= 2560 chips. Each slot consists of two parts, a data part that carries higher layer
information and a control part that carries Layer 1 control information. The data and
control parts are transmitted in parallel.
The spreading factor for the control part of the CPCH message part shall be 256.
Pilot
N
pilot
bits
TPC
N
TPC
bits
Data
N
data
bits
T
slot
= 2560 chips, 10*2
k
bits (k=0..6)
1 radio frame: T
f
= 10 ms
Data
Control
FBI
N
FBI
bits
TFCI
N
TFCI
bits
CP13_Ch7_p85
EMOTOROLA LTD. 2003
CP13: UMTS Overview
785
Frame structure for uplink Data and Control Parts
Associated with PCPCH
Pilot
N
pilot
bits
TPC
N
TPC
bits
Data
N
data
bits
T
slot
= 2560 chips, 10*2
k
bits (k=0..6)
1 radio frame: T
f
= 10 ms
Data
Control
FBI
N
FBI
bits
TFCI
N
TFCI
bits
CP13_Ch7_p86
786
DLDPCCH for CPCH
The downlink DPCCH for CPCH is a special case of downlink dedicated physical channel
of the slot format #0. The spreading factor for the DLDPCCH is 512. The figure below
shows the frame structure of DLDPCCH for CPCH.
TPC
N
TPC
bits
TFCI
N
TFCI
bits
CCC
N
CCC
bits
Pilot
Npilot bits
Slot #0 Slot #1 Slot #i
Slot #14
T
slot
= 2560 chips, 10 bits
One radio frame, T
f
= 10ms
CP13_Ch7_p87
DLDPCCH for CPCH consists of known pilot bits, TFCI, TPC commands and CPCH
Control Commands (CCC). CPCH control commands are used to support CPCH
signalling. There are two types of CPCH control commands: Layer 1 control command
such as Start of Message Indicator, and higher layer control command such as
Emergency Stop Command.
The CCC field above is used for the transmission of CPCH control command. On CPCH
control command transmission request from higher layer, a certain pattern is mapped
onto CCC field, otherwise nothing is transmitted in CCC field. There is one to one
mapping between the CPCH control command and the pattern. In case of Emergency
Stop of CPCH transmission, [1111] pattern is mapped onto CCC field. The Emergency
Stop command shall not be transmitted during the first N
Start_Message
frames of DL
DPCCH after Power Control preamble.
Start of Message Indicator shall be transmitted during the first N
Start_Message
frames of
DL DPCCH after Power Control preamble. [1010] pattern is mapped onto CCC field for
Start of Message Indicator. The value of N
Start_Message
shall be provided by higher layers.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
787
Frame structure for downlink DPCCH for CPCH
TPC
N
TPC
bits
TFCI
N
TFCI
bits
CCC
N
CCC
bits
Pilot
Npilot bits
Slot #0 Slot #1 Slot #i
Slot #14
T
slot
= 2560 chips, 10 bits
One radio frame, T
f
= 10ms
CP13_Ch7_p88
Version 1 Rev 7 Downlink Flow Process
788
Downlink Flow Process
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:
S Add CRC to each transport block
S Transport block concatenation and code block segmentation
S Channel coding
S Rate matching
S First insertion of discontinuous transmission (DTX) indication bits
S First interleaving
S Radio frame segmentation
S Multiplexing of transport channels
S Second insertion of DTX indication bits
S Physical channel segmentation
S Second interleaving
S Mapping to physical channels
It should be noted that not every step is applicable to every data type.
Version 1 Rev 7 Downlink Flow Process
EMOTOROLA LTD. 2003
CP13: UMTS Overview
789
Transport channel multiplexing structure for downlink
CP13_Ch7_36
P
h
C
H
#
2
P
h
C
H
#
1
Rate matching
TrBk concatenation /
Code block segmentation
1st insertion of DTX
indication
CRC attachment
Channel coding
Rate matching
1st interleaving
Radio frame segmentation
2nd insertion of DTX
indication
Physical channel
segmentation
2nd interleaving
Physical channel mapping
TrCH Multiplexing
CCTrCH
Version 1 Rev 7 Uplink Flow Process
790
Uplink Flow Process
The uplink flow process is largely the same as that for the downlink, and is illustrated in
the diagram opposite. 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 the 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
EMOTOROLA LTD. 2003
CP13: UMTS Overview
791
Uplink Flow Process
CP13_Ch7_44
TrBk concatenation /
Code block segmentation
1st interleaving
CRC attachment
Channel coding
Radio Frame equalisation
Radio frame segmentation
Rate matching
TrCH Multiplexing
Rate matching
P
h
C
H
#
1
P
h
C
H
#
2
Physical channel
segmentation
2nd interleaving
Physical channel mapping
CCTrCH
792
EMOTOROLA LTD. 2003
CP13: UMTS Overview
81
Chapter 8
Radio Resource Management
Functions
Version 1 Rev 7
82
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
83
Chapter 8
Radio Resource Management Functions 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Resource Management 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE RRC States 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Idle Mode 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connected Mode 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Layer Measurements 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UE Measurements 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTRA Measurements 810 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compressed Mode 812 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Selection/Re-selection 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Immediate Cell Evaluation 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Re-selection 814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Macro Diversity 816 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Strategy 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover Causes 818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Soft and Softer Handover 820 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
S-RNS Relocation 822 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Control 824 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Selection Diversity Power Control (SSDT) 824 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open Loop Power Control 826 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Power Control (Inner Loop) 828 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Power Control (Outer Loop) 830 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Cell Power Control 832 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site Select Diversity Transmission 834 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Space Time Transmit Diversity (STTD) 836 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closed Loop Mode Transmit diversity 838 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Admission Control 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of Service (QoS) 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Load 840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Control 842 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
84
EMOTOROLA LTD. 2003
CP13: UMTS Overview
81
Objectives
S Describe basic Radio Resource and Mobility Management functions.
Version 1 Rev 7 Radio Resource Management
82
Radio Resource Management (RRM) is responsible for the air Interface utilisation. RRM
guarantees that services will be provided according to the necessary quality that is
expected from the network. It is divided into 5 different sections:
S Cell Selection/Reselection
S Handover
S Power Control
S Admission Control
S Load Control
Version 1 Rev 7 Radio Resource Management
EMOTOROLA LTD. 2003
CP13: UMTS Overview
83
CP13_Ch9_01
Handovers
Power Control
Admission Control
Load Control
Cell Selection / Reselection
Version 1 Rev 7 UE RRC States
84
UE RRC States
The two basic operational modes of the UE are Idle Mode and Connected Mode. The
connected mode can be further divided into service states, which define what kind of
physical channels a UE is using. The diagram opposite shows the main RRC service
states in the connected Mode. It also shows the transitions between idle mode and
connected mode, and the possible transitions within connected mode.
Idle Mode
In idle mode, after the UE is switched on, it selects (either automatically or manually) a
PLMN to contact. The UE looks for a suitable cell of the chosen PLMN, chooses that cell
to provide available services and tunes to the control channel. This is known as
Camping on a cell. After camping on a cell in idle mode, the UE is able to receive
system information messages broadcast from the cell. The UE stays in idle mode until
such time as it transmits a request to establish a RRC connection. In Idle mode the UE is
identified by IMSI, TMSI and P-TMSI. The UTRAN has no information of its own about
individual idle mode UEs and can only address, for example, all UEs in a cell or all UEs
monitoring a paging group.-
Connected Mode
Cell DCH
In Cell DCH state a dedicated physical channel is allocated to the UE and the UE is
known by its serving RNC on a cell or active set level. The UE performs measurements
and sends measurement reports according to measurement control information received
from the RNC. The DSCH can also be used in this state, and Ues with certain
capabilities are also able to monitor the FACH channel for system information messages.
Cell FACH
In Cell FACH state no dedicated channel is allocated to the UE, but the RACH and FACH
channels can be used, both for transferring signalling messages and small amounts of
data. In this state the UE is also capable of monitoring the broadcast channel to acquire
system information. The CPCH can also be used when instructed by the UTRAN.
In this state the UE performs cell reselections, and after a reselection always sends a Cell
Update message to the RNC so the RNC knows the UE location on a cell level. For
Identification, a C-RNTI in the MAC PDU header separates UEs from each other in a
cell. When the LIE performs cell reselection it uses an U-RNTI when sending the Cell
Update message, so the UTRAN can route the message to the current serving RNC of
the UE, even if the first RNC receiving the message is not the current SRNC. The
U-RNTI is part of the RRC message, not in the MAC header.
If the new cell belongs to another RAN system, such as GPRS, the UE enters idle mode
and accesses the other system according to that systemss access procedure
EMOTOROLA LTD. 2003
CP13: UMTS Overview
85
UE RRC Connection States
CP13_Ch8_03a
Idle Mode
UTRAN Connected Mode
Cell DCH
Cell FACH
URA PCH
Cell PCH
86
Cell PCH
In the Cell PCH state the UE is still known on a cell level in the SRNC, but it can be
reached only via the paging channel. In this state the battery consumption is less than in
cell FACH, since the monitoring of the paging channel includes a discontinuous reception
(DRX) functionality. The LIE also listens to system information on the broadcast channel.
A UE supporting the CBS is also capable of receiving BMC message in this state. If the
UE performs cell reselection, it moves autonomously to the Cell FACH state to execute
the Cell Update procedure, after which it re-enters the Cell PCH state if no other activity
is triggered during the Cell Update procedure.
If the new cell belongs to another RAN system, such as GPRS, the UE enters idle mode
and accesses the other system according to that systemss access procedure
URA PCH
The URA PCH state is very similar to the Cell PCH, except that the UE does not execute
Cell Update after each reselection, but instead reads UTRA Registration Area (URA)
identities from the broadcast channel, and only if the URA changes does the UE pass its
location to the SRNC. This is achieved with the URA Update procedure (the UE enters
the Cell_FACH state to execute the procedure and then reverts to the URA PCH state).
One cell can belong to one or many URAs, and only if the UE cannot find its latest URA
identification from the list of URAs in a cell does it need to execute the URA Update
Procedure. This overlapping URA feature is needed to avoid pin-pong effects in possible
network configuration, where geographically succeeding base stations are controlled by
different RNCs.
The UE leaves the connected mode and returns to idle mode when the RRC connection
is released or at RRC connection failure.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
87
UE RRC Connection States
CP13_Ch8_03a
Idle Mode
UTRAN Connected Mode
Cell DCH
Cell FACH
URA PCH
Cell PCH
Version 1 Rev 7 Physical Layer Measurements
88
Physical Layer Measurements
The majority of radio resource management functions rely on the exchange of Layer 1
measurement reports between the UTRAN and the UE.
To initiate a specific measurement at the UE, the UTRAN transmits a measurement
control message to the UE including a measurement ID and type, a command (setup,
modify, release), the measurement objects and quantity, the reporting quantities, criteria
(periodical/event-triggered) and mode (acknowledged or unacknowledged). In idle mode
the measurement control message is broadcast in a System Information message.
When the reporting criteria is fulfilled the UE shall answer with a measurement report
message to the UTRAN including the measurement ID and the results.
UE Measurements
CPICH RSCP
Received Signal Code Power, the received power on one code measured on the Primary
CPICH.
SIR
Signal to Interference Ratio, defined as: (RSCP/ISCP)(SF/2). The SIR shall be
measured on DPCCH after RL combination.
UTRA carrier RSSI
Received Signal Strength Indicator, the wide-band received power within the relevant
channel bandwidth. Measurement shall be performed on a UTRAN downlink carrier.
GSM carrier RSSI
Received Signal Strength Indicator, the wide-band received power within the relevant
channel bandwidth. Measurement shall be performed on a GSM BCCH carrier.
CPICH Ec/No
The received energy per chip divided by the power density in the band. The Ec/No is
identical to RSCP/RSSI. Measurement shall be performed on the Primary CPICH.
Transport channel BLER
Estimation of the transport channel block error rate (BLER). The BLER estimation shall
be based on evaluating the CRC on each transport block after RL combination.
UE transmitted power
The total UE transmitted power on one carrier.
UE Rx-Tx time difference
The difference in time between the UE uplink DPCCH/DPDCH frame transmission and
the first significant path, of the downlink DPCH frame from the measured radio link.
Measurement shall be made for each cell included in the active set.
The Observed time difference to GSM
The Observed time difference to GSM cell is defined as: T
RxGSMj
- T
RxSFNi
, where:
T
RxSFNi
is the time at the beginning of the P-CCPCH frame with SFN=0 from cell i
.
T
RxGSMj
is the time at the beginning of the GSM BCCH 51-multiframe from GSM
frequency j received closest in time after the time T
RxSFNi
.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
89
UE Measurements
S CPICH RSCP
S SIR
S UTRA carrier RSSI
S GSM carrier RSSI
S CPICH Ec/No
S Transport channel BLER
S UE transmitted power
S UE Rx-Tx time difference
S The Observed time difference to GSM
810
UTRA Measurements
RSSI
Received Signal Strength Indicator, the wide-band received power within the UTRAN
uplink carrier channel bandwidth in an UTRAN access point.
SIR
Signal to Interference Ratio, is defined as: (RSCP/ISCP)SF. Measurement shall be
performed on the DPCCH after RL combination in Node B
Transmitted carrier power
Transmitted carrier power, is the ratio between the total transmitted power and the
maximum transmission power. Total transmission power is the mean power [W] on one
carrier from one UTRAN access point. Maximum transmission power is the mean power
[W] on one carrier from one UTRAN access point when transmitting at the configured
maximum power for the cell.
Transmitted code power
Transmitted code power, is the transmitted power on one channelisation code on one
given scrambling code on one given carrier. Measurement shall be possible on the
DPCCH-field of any dedicated radio link transmitted from the UTRAN access point and
shall reflect the power on the pilot bits of the DPCCH-field.
Transport channel BER
The transport channel BER is an estimation of the average bit error rate (BER) of
RL-combined DPDCH data. Transport channel BER is only required to be reported for
TrCHs that are channel coded.
Physical channel BER
The Physical channel BER is an estimation of the average bit error rate (BER) on the
DPCCH after RL combination in Node B.
Round trip time
Round trip time (RTT), is defined as
RTT = T
RX
T
TX
, where
T
TX
= The time of transmission of the beginning of a downlink DPCH frame to a UE.
T
RX
= The time of reception of the beginning (the first significant path) of the
corresponding uplink DPCCH/DPDCH frame from the UE.
PRACH Propagation delay
Propagation delay is defined as one-way propagation delay as measured during either
PRACH or PCPCH access.
Acknowledged PRACH preambles
The Acknowledged PRACH preambles measurement is defined as the total number of
acknowledged PRACH preambles per access frame per PRACH. This is equivalent to
the number of positive acquisition indicators transmitted per access frame per AICH
EMOTOROLA LTD. 2003
CP13: UMTS Overview
811
UTRA Measurements
S RSSI
S SIR
S Transmitted carrier power
S Transmitted code power
S Transport channel BER
S Physical channel BER
S Round trip time
S PRACH Propagation delay
S Acknowledged PRACH preambles
Version 1 Rev 7 Compressed Mode
812
Compressed Mode
In addtion to monitoring Node Bs on the same carrier, the UE must be able to monitor for
potential target resources on other UMTS carriers, and in the case of dual mode UEs on
alternative RAN technologies (e.g GSM/GPRS). This will involve at minimum retuning of
the UEs receiver elements to a new radio frequency. As the transfer of information
between network and UE is continuous in a CDMA system, time must be created for
the UE perform this function. This achieved by the use of Compressed Mode.
In compressed mode, time slots from N
first
to N
last
are not used for transmission of data.
Instead, the data that would normally be transmitted during those slots is compressed
into the remaining timeslots within that radio frame.
As illustrated in the figure opposite, the instantaneous transmit power is increased in the
compressed frame in order to keep the quality (BER, FER, etc.) unaffected by the
reduced processing gain. The amount of power increase depends on the transmission
time reduction method What frames are compressed, are decided by the network. When
in compressed mode, compressed frames can occur periodically, as illustrated, or
requested on demand. The rate and type of compressed frames is variable and depends
on the environment and the measurement requirements. The maximum idle length is
defined to be 7 slots per 10 ms frame (yielding 4.67 ms). Compressed mode can
There are three methods of compressing the data:
Compressed mode by puncturing
During compressed mode, rate matching (puncturing) is applied for creating
transmission gap in one frame.
Compressed mode by reducing the spreading factor by 2
During compressed mode, the spreading factor (SF) can be reduced by 2 during one
radio frame to enable the transmission of the information bits in the remaining time slots
of a compressed frame.
Compressed mode by higher layer scheduling
Compressed mode can be obtained by higher layer scheduling. Higher layers then set
restrictions so that only a subset of the allowed TFCs are used in compressed mode.
The maximum number of bits that will be delivered to the physical layer during the
compressed radio frame is then known and a transmission gap can be generated.
Version 1 Rev 7 Compressed Mode
EMOTOROLA LTD. 2003
CP13: UMTS Overview
813
Compressed Mode
CP13_Ch9_04
Transmission gap available for
interfrequency measurements
One frame
(10 ms)
Version 1 Rev 7 Cell Selection/Re-selection
814
Cell Selection/Re-selection
The goal of the cell selection procedures is to fast find a cell to camp on. To speed up
this process, at power up or when returning from out of coverage, the UE shall start
with the stored information from previous network contacts. If the UE is unable to find
any of those cells the Initial cell search will be initiated.
If it is not possible to find a cell from a valid PLMN the UE will choose a cell in a
forbidden PLMN and enter a limited service state. In this state the UE regularly attempt
to find a suitable cell on a valid PLMN. If a better cell is found the UE has to read the
system information for that cell. The cell to camp on is chosen by the UE on link quality
basis. However, the network can set cell re-selection thresholds in order to take other
criteria into account, such as, for example:
S available services;
S cell load;
S UE speed.
In CDMA, it is important to minimise the UE output power, and also to minimise the
power consumption in the UE. In order to achieve that, an Immediate Cell Evaluation
Procedure at call set up can ensure that the UE transmits with the best cell, while
keeping the power consumption low.
Immediate Cell Evaluation
It is important that the UE chooses the best cell (according to the chosen criteria) prior to
a random access on the RACH. This is the aim of the immediate cell evaluation. This
procedure shall be fast and there shall not be any hysteresis requirements between the
different cells. However, it must be possible to rank two neighbouring cells by means of
an offset. This offset is unique between two cells. This implies that this value must be a
part of the system information in the serving cell. This offset is introduced for system
tuning purposes, in order to move the cell border.
Before the access on the RACH can be initiated the UE also needs to check the relevant
parts of system information for making the access. The time it takes to perform an
immediate cell evaluation and select a new cell is dependent on the time it takes to read
the system information. This can be optimised by the scheduling of the system
information at the BCCH, the better scheduling the faster cell evaluation. In particular, at
call set up, it would be important to select the optimal cell, i.e. the one where the UE
uses the lowest output power.
Cell Re-selection
The cell reselection procedure is a procedure to check the best cell to camp on. The
evaluation of the measurements for this procedure is always active, in idle mode, after
the cell selection procedure has been completed and the first cell has been chosen. The
goal of the procedure is to always camp on a cell with good enough quality even if it is
not the optimal cell all the time.
It is also possible to have a time to trigger and hysteresis criteria in the cell reselection
to control the number of cell reselections. The parameters needed for the cell reselection
procedure (e.g., the offset value and the hysteresis) are unique on a cell to neighbour cell
relation basis. These have therefore to be distributed, together with time to trigger value,
in system information in the serving cell. This implies that the UE does not need to read
the system information in the neighbouring cells before the cell reselection procedure
finds a neighbouring cell with better quality.
Version 1 Rev 7 Cell Selection/Re-selection
EMOTOROLA LTD. 2003
CP13: UMTS Overview
815
Cell Selection/Re-selection
CP13_Ch9_15QS
Camped
normally
NAS
registration
rejected
no
suitable
cell
found
Initial
Cell Selection
Cell
Reselection
Immediate
Cell
Evaluation
Cell Selection
when leaving
connected
mode
Stored
Information
Cell Selection
Connected
Mode
1
go here whenever
a new PLMN
is selected
cell information
stored for the PLMN
no cell information
stored for the PLMN
no suitable
cell found
no suitable
cell found
suitable cell found
no suitable cell found
suitable cell found
suitable
cell selected
trigger
suitable
cell found
return to
idle mode
leave
idle mode
best
suitable
cell selected
Camped on
Any Cell
suitable
cell found
Any Cell
Reselection
Immediate
Cell
Evaluation
Cell Selection
when leaving
connected
mode
Connected
Mode
(Emergency
calls only)
1
USIM inserted
no acceptable cell found
no acceptable cell found
an acceptable cell found
acceptable
cell selected
trigger
acceptable
cell found
return to
idle mode
leave
idle mode
best
acceptable
cell selected
Any Cell
Selection
1
go here when no USIM in the UE
Version 1 Rev 7 Macro Diversity
816
Macro Diversity
Macrodiversity provides an improved error correction capability through the use of
combining/splitting at the RNC and Node B. Communications will be sent via the Iur
interface from the RNC in the D-RNS to the RNC in the S-RNS and on to the Iu to the
core network.
This function controls the duplication/ replication of information streams to receive/
transmit the same information through multiple physical channels from/ towards a single
mobile terminal.
This function also controls the combining of information streams generated by a single
source (diversity link), but conveyed via several parallel physical channels (diversity
sub-links). Macrodiversity control should interact with channel coding control in order to
reduce the bit error ratio when combining the different information streams. In some
cases, depending on physical network configuration, there may be several entities that
combine the different information streams, i.e. there may be combining/splitting at the
S-RNC, D-RNC or Node B level. This function is located in the UTRAN.
Version 1 Rev 7 Macro Diversity
EMOTOROLA LTD. 2003
CP13: UMTS Overview
817
Macro Diversity
CP13_Ch9_04
DRNS
UTRAN
lu
RNC RNC RNC
SRNS
Version 1 Rev 7 Handover
818
Handover
Handover Strategy
The handover strategy employed by the network for radio link control determines the
handover decision that will be made based on the measurement results reported by the
UE/RNC and various parameters set for each cell. Network directed handover might also
occur for reasons other than radio link control, e.g. to control traffic distribution between
cells. The network operator will determine the exact handover strategies. Possible types
of Handover are as follows:
S Handover 3G -3G;
S FDD soft/softer handover;
S FDD inter-frequency hard handover;
S FDD/TDD Handover;
S TDD/FDD Handover;
S TDD/TDD Handover;
S Handover 3G - 2G (e.g. Handover to GSM);
S Handover 2G - 3G (e.g. Handover from GSM).
Handover Causes
The following is a non-exhaustive list for causes that could be used for the initiation of a
handover process.
Uplink quality;
Uplink signal measurements;
Downlink quality;
Downlink signal measurements;
Distance;
Change of service;
Better cell;
O&M intervention;
Directed retry;
Traffic;
Pre-emption
Version 1 Rev 7 Handover
EMOTOROLA LTD. 2003
CP13: UMTS Overview
819
Handover
Handover Strategy Handover Causes
Handover 3G -3G;
FDD soft/softer handover;
Uplink quality;
Uplink signal measurements; FDD soft/softer handover;
FDD inter-frequency hard handover;
Uplink signal measurements;
Downlink quality;
FDD/TDD Handover;
TDD/FDD Handover;
Downlink signal measurements;
Distance; TDD/FDD Handover
TDD/TDD Handover;
Handover 3G 2G (e g Handover to GSM);
Distance
Change of service;
Better cell; Handover 3G - 2G (e.g. Handover to GSM);
Handover 2G - 3G (e.g. Handover from
GSM)
Better cell;
O&M intervention; ( g
GSM).
Directed retry;
Traffic; Traffic;
Pre-emption
Version 1 Rev 7 Soft and Softer Handover
820
Soft and Softer Handover
Soft Handover is a handover in which the mobile station starts communication with a new
Node-B on a same carrier frequency, or sector of the same site (softer handover),
performing at most a change of code. For this reason Soft Handover allows easily the
provision of macro-diversity transmission. This intrinsic characteristic terminology tends
to identify Soft Handover with macro-diversity even if they are two different concepts. As
a result of this definition there are areas of the UE operation in which the UE is
connected to a number of Node-Bs. With reference to Soft Handover, the Active Set is
defined as the set of Node-Bs the UE is simultaneously connected to (i.e., the UTRA
cells currently assigning a downlink DPCH to the UE constitute the active set).
The Soft Handover procedure is composed of a number of single functions:
S Measurements
S Filtering of Measurements
S Reporting of Measurement results
S The Soft Handover Algorithm
S Execution of Handover.
Based on the measurements of the set of cells monitored, the Soft Handover function
evaluates if any Node-B should be added to (Radio Link Addition), removed from (Radio
Link Removal), or replaced in (Combined Radio Link Addition and Removal) the Active
Set. This procedure is known as the Active Set Update procedure.
Version 1 Rev 7 Soft and Softer Handover
EMOTOROLA LTD. 2003
CP13: UMTS Overview
821
Soft Handover Procedure
CP13_Ch9_06
Eb/(No + lo)
Time
Tadd
Tdrop
Cell B Cell A
Add A
Drop B
Relative
Threshold
Absolute
Threshold
Version 1 Rev 7 S-RNS Relocation
822
S-RNS Relocation
This functionality allows moving the Serving RNS functionality from one RNC to another
RNC, e.g. closer to where the UE has moved during the communication. The Serving
RNS Relocation procedure may be applied when active cell management functionality
has created a suitable situation for it. Both UTRAN and CN are involved.
Version 1 Rev 7 S-RNS Relocation
EMOTOROLA LTD. 2003
CP13: UMTS Overview
823
S-RNS Relocation
CP13_Ch9_07
RNC RNC
lu lu
DRNS
SRNS
SRNS Step 1
Step 2
RNC
lur lur
Version 1 Rev 7 Power Control
824
Power Control
Power control controls the level of the transmitted power in order to minimise interference
and keep the quality of the connections.
Three types of Power Control Procedures are identified:
Open Loop Power Control
Closed Loop using the Inner Loop method
UL Inner Loop Power Control - located in both the UTRAN and the UE
DL Inner Loop Power Control - located in both the UTRAN and the UE
Closed Loop using the Outer Loop method
The main difference between Inner and Outer Loop power control is that the Frame Error
Rate can be set with Outer Loop Power Control.

UL Outer Loop Power Control - located in the S-RNC (UTRAN).
DL Outer Loop Power Control - located mainly in the UE, but some control parameters
are set by the UTRAN
Site Selection Diversity Power Control (SSDT)
A form of power control for the downlink that can be applied in the UE is in soft handover.
Version 1 Rev 7 Power Control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
825
Power Control
CP13_Ch9_08
Closed Loop Power Control (Inner Loop)
Closed Loop Power Control (Outer Loop)
Site Selection Diversity Power Control
Version 1 Rev 7 Open Loop Power Control
826
In UTRAN, open loop power control is applied only immediately prior to initiating a
transmission on the PRACH.
The UE determines an estimation of the downlink pathloss between the base station and
the UE by measuring the UTRA carrier received signal strength at the mobile. Through
the medium of the System Information messages on the P-CCPCH, the UE will also
have access to certain cell parameters, such as Cell ERP, Cell size, receiver sensitivity,
etc.
Form this information the UE will calculate the required mean output power level required
to achieve the access requirements of the cell it wishes to connect to. The UE will now
send its first RACH Pre-amble at this calculated value. If no positive or negative
acquisition indicator is detected, the UE will increase its power by the required
power-ramping factor, (cell defined parameter), and send a second RACH Pre-amble.
This process will be repeated until an acknowledgement is received, or the max retries
value is exceeded.
If a positive Ack is received, the UE will again adjust its output power, according to an
offset value notified by the cell, and transmit the RACH message part. On receipt of the
RACH Message part, the UTRAN can accurately calculate the uplink path loss and
initiate the use of closed loop power control.
Version 1 Rev 7 Open Loop Power Control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
827
CP13_Ch9_17
UE monitors Common Pilot
and Broadcast information,
and calculates DL path Loss
Only used prior to initial transmission on PRACH
Using DL path loss as
perceived UL path
loss, UE calculates TX
power O/P required
access network
Version 1 Rev 7 Closed Loop Power Control (Inner Loop)
828
The objective of Closed loop power control is to maintain the the received signal strength,
at the base station, for all UEs at the same average level. As all UEs in a cell transmit on
the same frequency, a single overpowered mobile could block a whole cell to other users.
The uplink inner-loop power control adjusts the UE transmit power in order to keep the
received uplink signal-to-interference ratio (SIR) at a given SIR target (SIR
target)
. The
serving cells (cells in the active set) should estimate signal-to-interference ratio (SIR
est)
of the uplink, using the received pilot symbols in each uplink uplink timeslot.
The serving cells should then generate TPC commands and transmit the commands
once per slot, using the TPC symbols in each time slot, according to the following rule: if
SIR
est
> SIR
target
then the TPC command to transmit is 0, while if SIR
est
< SIR
target
then the TPC command to transmit is 1. The UE uses this information to derive
TPC_cmd.
After deriving of the TPC_cmd, the UE shall adjust the transmit power of the uplink with a
step (in dB) which is given by:
D = D
TPC
TPC_cmd.
The step size
TPC
is a layer 1 parameter which is derived from the UE-specific
higher-layer parameter TPC-StepSize which is under the control of the UTRAN. If
TPC-StepSize has the value dB1, then the layer 1 parameter
TPC
shall take the
value 1 dB and if TPC-StepSize has the value dB2, then
TPC
shall take the value
2 dB.
A similar process is used in the downlink, to control the relative power weighting to be
applied to each downlink dedicated channel.
Version 1 Rev 7 Closed Loop Power Control (Inner Loop)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
829
CP13_Ch9_18
Node B Monitors UL Signal
Interference Ratio (SIR)
And compares against
Target SIR level
Inner Loop Power Control command rate is 1500 Hz
Node B sends Transmit Power Control (TPC)
information to UE, adjusting UE
transmit power output in an attempt to
acheive target SIR
Version 1 Rev 7 Closed Loop Power Control (Outer Loop)
830
While Closed loop power control (Inner Loop) is used to maintain a target SIR, Outer
loop power control adjusts the SIR target in the base station according to the needs of
the individual radio link and aims at a constant quality, usually defined as a certain target
bit error rate (BER) or frame error rate (FER). The reason for adjusting the target is to
compensate for variations in UE speed and multipath profile when actually mobile.
Outer loop power control is implemented by having the Node B tag each uplink user data
frame with a frame error indicator, such as a CRC check result to the serving RNC.
Should this indicate to the RNC that the transmission quality is decreasing, the RNC will
in turn command the Node B to increase the SIR target proportionally.
The reason for having the outer loop power control reside in the RNC is that this function
should be performed after a possible soft handover combining has been performed.
Version 1 Rev 7 Closed Loop Power Control (Outer Loop)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
831
CP13_Ch9_19
SRNC target quality
Value sent to Node B
as New Target SIR
value for Inner Loop
Power Control
Outer Loop Power Control
command rate is 10100 Hz
Node B receives UL dedicated
channel data, which is passed
serving RNC along with a Quality
estimate of the Transport Channel
SRNC
SRNC Checks FER
and adjusts target
quality value for
the UL
Version 1 Rev 7 Multi-Cell Power Control
832
Multi-Cell Power Control
As we have seen the UE has the ability to receive and process the transmitted downlink
from several Node Bs simultaneously. By the same token several Node Bs will be
sending conflicting power control commands to the one UE. In this situation the UE will
always ramp its power down unless all received power control commands require it to
power up.
Version 1 Rev 7 Multi-Cell Power Control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
833
Multi-Cell Power Control
CP13_Ch9_09
Node B
Node B
Node B
Node B
Increase
Increase
Increase
Decrease
Mobile Decreases
Tx Power
Mobile Increases
Tx Power
Version 1 Rev 7 Site Select Diversity Transmission
834
Site Select Diversity Transmission
Site Selection Diversity Transmit Power Control (SSDT) is a form of power control for the
downlink that can be applied while a UE is in soft handover (SHO). This section explains
how SSDT works, and provides some examples when SSDT should be used. In SHO, a
UE has DL connections to more than one cell. Thus, one UE contributes to the DL
interference in several cells. SSDT is a power control method that reduces the DL
interference generated while the UE is in SHO. The principle of SSDT is that the best cell
of the active set is dynamically chosen as the only transmitting site, and the other cells
involved turn down their DPDCHs. The DPCCH is transmitted as normally.
Each cell is given a temporary identification number. The UE measures the pilot power of
the PCCPCHs, and chooses the best one as its primary cell. The temporary id of this
primary cell (the primary id) is transmitted on the UL DPCCH to all Node Bs of the active
set. A cell that has been selected as primary station transmits its dedicated channels with
the power necessary to reach the desired SIR target, whereas all other cells switch off
their downlink DPDCH transmission. The primary id is updated by the UE at a frequency
of 5, 10 or 20ms. The frequency depends on the SSDT mode and is set by the UTRAN.
In order for the UE to continuously perform measurements and to maintain
synchronisation, the secondary cells continue to transmit pilot information on the
DPCCH.
The prerequisite for using SSDT during an RRC connection or during a part of an RRC
connection is that all Node-Bs involved support SSDT. SSDT is controlled by L3
procedures. The control involves assignment of temporary IDs, setting an SSDT mode
and switching SSDT on or off. The control information itself (temporary IDs) terminates in
the L1 of Node B and UE respectively.
Version 1 Rev 7 Site Select Diversity Transmission
EMOTOROLA LTD. 2003
CP13: UMTS Overview
835
Site Select Diversity Transmission
CP13_Ch9_10
Version 1 Rev 7 Space Time Transmit Diversity (STTD)
836
Space Time Transmit Diversity (STTD)
The open loop Downlink Transmit Diversity employs a space time block coding based
transmit diversity. The STTD encoding is optional in UTRAN. STTD support is thus
mandatory at the UE. A block diagram of the transmitter and a generic STTD encoder
are shown in the slide opposite. Channel coding, rate matching and interleaving is done
as in the non-diversity mode.
The bit sequence at the antennas after encoding, for an input bit sequence of b0, b1, b2,
b3 is shown below:
CP13_Ch9_21
b0 b1 b2 b3
b2 b3 b0 b1
b0 b1 b2 b3
Version 1 Rev 7 Space Time Transmit Diversity (STTD)
EMOTOROLA LTD. 2003
CP13: UMTS Overview
837
Space Time Transmit Diversity (STTD)
CP13_Ch6_31
Interleaver
Rate
Matching
Channel
Encoder
STTD
Encoder
M
U
X
M
U
X
Diversity
Pilot
Pilot
TPC
TFI
Data
Ant 1
Ant 2
Ant 1
Ant 2
Channelizaton code
and long scrambling code C,
spreading length = M
Tx
Antenna 1
Tx
Antenna 2
QPSK symbols
Version 1 Rev 7 Closed Loop Mode Transmit diversity
838
Closed Loop Mode Transmit diversity
The general transmitter structure to support closed loop mode transmit diversity for
DPCH transmission is shown opposite. Channel coding, interleaving and spreading are
done as in non-diversity mode. The spread complex valued signal is fed to both TX
antenna branches, and weighted with antenna specific weight factors w
1
and w
2
. The
weight factors are complex valued signals (i.e., w
i
= a
i
+ jb
i
), in general.
The weight factors (actually the corresponding phase adjustments in closed loop mode 1
and phase/amplitude adjustments in closed loop mode 2) are determined by the UE, and
signalled to the UTRAN access point (=cell transceiver) using the D-bits of the FBI field
of uplink DPCCH.
For the closed loop mode 1 different (orthogonal) dedicated pilot symbols in the DPCCH
are sent on the 2 different antennas. For closed loop mode 2 the same dedicated pilot
symbols in the DPCCH are sent on both antennas.
Version 1 Rev 7 Closed Loop Mode Transmit diversity
EMOTOROLA LTD. 2003
CP13: UMTS Overview
839
Closed Loop Mode Transmit diversity
CP13_Ch9_20
Determine FBI message

from Uplink DPCCH
CPICH2
x
x
Ant1
W2
x
Spread/scramble
CPICH1
W1
Tx
Ant2
Rx
Tx
Weight Generation
W2 W1
DPCCH
DPCCH
DPCCH
Rx
Version 1 Rev 7 Admission Control
840
Admission Control
In CDMA networks the soft capacity concept applies. Each new call that is established
will increase the interference level in the network, this will effect quality of all other
ongoing calls in the network. Therefore it is very important to control the access to the
network in a suitable way (Call Admission Control - CAC).
The following will serve as a criterion for admission control.
Quality of Service (QoS)
Admission Control is performed according to the Quality of Service (QoS) required by the
UE. This is an example of the services required.
Service Domain Transport
Channel
Type of Service CAC
Performed
Voice CS DCH Premium Yes
Streaming PS DCH Premium Yes
Web
Browsing
PS DSCH Assured Service Yes
E-mail PS DSCH Best Effort No
System Load
Admission Control is performed according to the current system load and the required
service. The call should be blocked if none of the suitable cells can efficiently provide the
service required by the UE at call set up (i.e., if, considering the current load of the
suitable cells, the required service is likely to increase the interference level to an
unacceptable value). This would ensure that the UE avoids wasting power affecting the
quality of other communications. In this case, the network can initiate a re-negotiation of
resources of the on-going calls in order to reduce the traffic load.
An example of Call Admission Control is given on the right side of the page.
1. CN requests SRNC for establishing a Radio Access Bearer (RAB) indicating QoS
parameters.
2. According to QoS parameters the requested service is assigned a type of service.
CAC is performed according to the type of service.
3. Resources are allocated according to the result of CAC.
4. Acknowledgement is sent back to CN according to the result of CAC. Sub-layers
are configured accordingly.
Version 1 Rev 7 Admission Control
EMOTOROLA LTD. 2003
CP13: UMTS Overview
841
Admission Control
RRM Entity
2. Mapping Qos Parameter
Type of Service
CAC
3. Resource Allocation
CP13_Ch9_11
1. RANAP
Message
4. RANAP
Message
RANAP
RRC
RLC
MAC
4. CPHYRL
SetupREQ
4. CMAC
Connection
4. CRLC Config
Version 1 Rev 7 Load Control
842
Load Control
This Management task ensures that the system will never be overloaded and remains
stable. A well planned system will seldom overload, however if such a condition does
occur there must be mechanisms in place to reduce the load quickly and efficiently.
Some of the mechanisms available to reduce the load are the following:
S Downlink fast load control (Deny power-up commands)
S Uplink fast load control (Reduction of Eb/No)
S Handover to another W-CDMA carrier
S Handover to GSM
S Reduce packet data throughput
S Decrease bit rate of real time users (AMR Algorithms)
S Drop calls in a controlled fashion
EMOTOROLA LTD. 2003
CP13: UMTS Overview
843
Load Control
CP13_Ch9_12
Downlink fast load control
Uplink fast load control
Handover to another WCDMA carrier
Handover to GSM
Reduce packet data throughput
Decrease bit rate of real time users
Drop calls in a controlled fashion
844
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A91
Chapter 9
Annexe A
Version 1 Rev 7
A92
Version 1 Rev 7
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A93
Chapter 9
Annexe A A91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives A91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging for a UE in Idle Mode A92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Paging for the UE in RRC Connected Mode A94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC Connection Establishment A96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RRC DCH Release A98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RA Update A910 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRNC Relocation A912 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version 1 Rev 7
A94
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A91
Objectives
S Describe selected UMTS Signalling Flow procedures.
Version 1 Rev 7 Paging for a UE in Idle Mode
A92
Paging for a UE in Idle Mode
This example shows how paging is performed for a UE in RRC Idle Mode. The UE may
be paged for a CS or PS service. Since the UE is in RRC Idle Mode, the location is only
known at CN level and therefore paging is distributed over a defined geographical area
(e.g. LA).
NOTE:
The example below illustrates scenario where LA spans across 2 RNCs.
1. The CN initiates the paging of a UE over a LA spanning two RNCs (i.e. RNC1 and
RNC2) via a RANAP message called the Paging message.
Parameters Sent:
CN Domain Indicator, Permanent NAS UE Identity, Temporary UE Identity, Paging
Cause.
2. Paging of UE performed by cell1 using Paging Type 1 message.
3. Paging of UE performed by cell2 using Paging Type 1 message.
The UE detects page message from RNC1 (as example) and the procedure for
NAS signalling connection establishment follows. NAS message transfer can now
be performed.
This procedure described for RRC idle mode, applies also to the RRC connected
mode in the case of CELL_PCH and URA_PCH states.
Version 1 Rev 7 Paging for a UE in Idle Mode
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A93
Paging for UE in Idle Mode
CP13_Ch10_01
UE
Node B
1.1
Node B
2.1
RNC
1
RNC
2
CN
RANAP
RANAP
RANAP
RANAP
2.PCCH: Paging Type 1
3.PCCH: Paging Type 1
1. Paging
1. Paging
Version 1 Rev 7 Paging for the UE in RRC Connected Mode
A94
Paging for the UE in RRC Connected Mode
This will occur in case the position of the UE is already known; a mobility management
session will be active at this stage. Two possible solutions exists:
S The UTRAN co-ordinates the paging request with the existing RRC connection.
S The UE co-ordinates the paging request with the existing RRC connection.
The following example shows how paging is performed for a UE in RRC Connected
Mode (CELL_DCH and CELL_FACH states) when the UTRAN co-ordinates the paging
request with the existing RRC connection using DCCH.
1. CN initiates the paging of a UE via RANAP message Paging Request Message.
Parameters used: CN Domain Indicator, Permanent NAS UE Identity, Temporary
UE Identity, Paging Cause.
2. SRNC sends RRC message Paging Type 2.
Version 1 Rev 7 Paging for the UE in RRC Connected Mode
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A95
Paging for UE in RRC Connected Mode
CP13_Ch10_02
CN
RRC
RANAP
RRC
RANAP
1. Paging
UE
Serving
RNC
2. DCCH Paging Type 2
Version 1 Rev 7 RRC Connection Establishment
A96
RRC Connection Establishment
The following example shows establishment of a RRC connection in dedicated transport
channel (DCH) state.
The following sequence are identified:
1. The UE initiates set-up of an RRC connection by sending RRC message Connection
Request on CCCH.
Parameters used: Initial UE Identity, Establishment cause, Initial UE Capability.
2. The SRNC decides to use a DCH for this RRC connection, allocates RNTI and radio
resources for the RRC connection. When a DCH is to be set-up, NBAP message Radio
Link Setup Request is sent to Node B.
Parameters used: Cell id, Transport Format Set, Transport Format Combination Set,
frequency, UL scrambling code(FDD only), Time Slots (TDD only), User Codes (TDD
only), Power control information.
3. Node B allocates resources, starts PHY reception, and responses with NBAP
message, Radio Link Setup Response. Parameters used: Signalling link termination,
Transport layer addressing information (AAL2 address, AAL2 Binding Identity) for the Iub
Data Transport Bearer.
4. SRNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This
request contains the AAL2 Binding Identity to bind the Iub Data Transport Bearer to the
DCH. The request for set-up of Iub Data Transport bearer is acknowledged by Node B.
5./6. The Node B and SRNC establish synchronism for the Iub and Iur Data Transport
Bearer by means of exchange of the appropriate DCH Frame Protocol frames Downlink
Synchronisation and Uplink Synchronisation. Then Node B starts DL transmission.
7. Message RRC Connection Setup is sent on CCCH from SRNC to UE.
Parameters: Initial UE Identity, RNTI, Capability update Requirement, Transport Format
Set, Transport Format Combination Set, frequency, DL scrambling code (FDD only),
Time Slots (TDD only), User Codes (TDD only), Power control information.
8. Message RRC Connection Setup Complete is sent on DCCH from UE to SRNC.
Parameters: Integrity information, ciphering information.
Version 1 Rev 7 RRC Connection Establishment
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A97
RRC Connection Establishment
CP13_Ch10_03
RRC
UE
Serving
RNC
Node B
Serving RNS
NBAP
DCH
RRC
NBAP
NBAP NBAP
DCH
DCH DCH
RRC
RRC
RRC
RRC
Allocate RNTI
Select L1 and L2
parameters
Start Rx
4. ALCAP Iub Data Transport Bearer Setup
Start Rx
1. CCCH: RRC Connection Request
2. Radio Link Setup Request
3. Radio Link Setup Response
5. Downlink Synchronisation
6. Uplink Synchronisation
7. CCCH: RRC Connection Setup
8. DCCH: RRC Connection Setup Complete
Version 1 Rev 7 RRC DCH Release
A98
RRC DCH Release
This example shows RRC Connection release of a dedicated channel, in the case of
macrodiversity on two Nodes-Bs; the first one connected to the Serving RNC, the second
one to the Drift RNC.
1. The CN initiates the release of a dedicated Channel by sending the message Iu
Release Command to the SRNC. Parameters used: Cause.
2. The SRNC confirms the release by sending an Iu Release Complete message to
the CN.
Parameters used: Data volume Report (if data volume reporting to PS is required).
3. The SRNC initiates release of Iu Data Transport bearer using ALCAP protocol.
4. Message RRC Connection Release from SRNC to UE to initiate the RRC
connection release.
Parameters: Cause.
5. Message RRC Connection Release Complete from UE to SRNC to confirm the
RRC connection release.
6. The SRNC initiates the release of the link by sending the Radio Link Deletion to
the Node B (SRNC).
7. The SRNC initiates the release of the link by sending the Radio Link Deletion to
the Drift RNC.
8. The Drift RNC initiates the release of the link by sending the Radio Link Deletion
to the Node B (Drift RNC).
9. The Node B (SRNC) confirms the release of the link by sending the Radio Link
Deletion Response to the SRNC.
10. The Node B (Drift RNC) confirms the release of the link by sending the Radio Link
Deletion Response to the Drift RNC.
11. The Drift RNC confirms the release of the link by sending the Radio Link Deletion
Response to the SRNC.
12. The Node B (SRNC) initiates release of Iub Data Transport bearer using ALCAP
protocol.
13. The Node B (Drift RNC) initiates release of Iub Data Transport bearer using
ALCAP protocol.
14. The Drift RNC initiates release of Iur Data Transport bearer using ALCAP protocol.
Version 1 Rev 7 RRC DCH Release
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A99
RRC DCH Release
CP13_Ch10_04
RRC
NBAP
RRC
NBAP
NBAP
NBAP
RNSAP
RRC
RRC
NBAP
NBAP
NBAP
NBAP
RANAP
Node B
Serving RNS
UE
Node B
Drift RNS
Drift
RNC
Serving
RNC
CN
RANAP RANAP
RANAP
RNSAP RNSAP
RNSAP
1. Iu Release
2. Iu Release
3. ALCAP Iu Bearer Release
4. RRC connection Release
5. RRC Connection Release Complete
6. Radio Link Deletion
7. Radio Link
Deletion
9. Radio Link Deletion Response
Response
11. Radio Link
12. ALCAP Iub Bearer Release
13. ALCAP Iub Bearer Release ALCAP Iur Bearer Release
Complete
Complete
Deletion
Response
Version 1 Rev 7 RA Update
A910
RA Update
This example shows location registration when changing Routing Area including change
of 3G SGSN when the UE is in MM idle state towards the 3G SGSN.
The illustrated transfer of MM signalling to/from the UE uses an established RRC
connection. This RRC connection can have been established beforehand due to ongoing
inter-working between UE and 3G-MSC/VLR or be established only for this location
registration procedure towards the 3G-SGSN. For each indicated MM message sent in
this case to/from UE, the CN discriminator indicates 3G-SGSN.
The following procedure will take place to perform the RA update:
1. The RRC connection is established, if not already done. The UE sends the initial
message Routing Area Update Request (old P-TMSI, old RAI, etc.) to the new
3G-SGSN. The old P-TMSI and the old RAI are assigned data in UMTS. The
SRNS transfers the message to the 3G-SGSN. The sending of this message to
3G-SGSN will also imply establishment of a signalling connection between SRNS
and 3G-SGSN for the concerned UE. The UTRAN shall add the RAC and the LAC
of the cell where the message was received before passing the message to the
SGSN.
2. The new 3G-SGSN send an SGSN Context Request (old P-TMSI, old RAI) to the
old 3G-SGSN to get the IMSI for the UE. (The old RAI received from UE is used to
derive the old 3G-SGSN identity/address.) The old 3G-SGSN responds with
SGSN Context Response (e.g. IMSI, PDP context information and Authentication
triplets).
3. Security functions may be executed.
4. The new 3G-SGSN informs the HLR of the change of 3G-SGSN by sending
Update GPRS Location (IMSI, SGSN number, SGSN address) to the HLR.
5. The HLR cancels the context in the old 3G-SGSN by sending Cancel Location
(IMSI). The old 3G-SGSN removes the context and acknowledges with Cancel
Location Ack.
6. The HLR sends Insert Subscriber Data (IMSI, subscription data) to the new
3G-SGSN. The new 3G-SGSN acknowledges with Insert Subscriber Data Ack.
7. The HLR acknowledges the Update GPRS Location by sending Update GPRS
Location Acknowledge to the new 3G-SGSN.
8. The new 3G-SGSN validates the UEs presence in the new RA. If due to regional,
national or international restrictions the UE is not allowed to attach in the RA or if
subscription checking fails, then the new 3G-SGSN rejects the Routing Area
Update Request with an appropriate cause. If all checks are successful, then the
new 3G-SGSN responds to the UE with Routing Area Update Accept (new
P-TMSI, new RAI, etc.).
9. The UE acknowledges the new P-TMSI with Routing Area Update Complete.
10. When the location registration procedure is finished, the 3G-SGSN may release
the signalling connection towards the SRNS for the concerned UE. The SRNS will
then release the RRC connection if there is no signalling connection between
3G-MSC/VLR and SRNS for the UE.
Version 1 Rev 7 RA Update
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A911
RA Update
CP13_Ch10_05
Old
3G_SGSN
UE HLR SRNS
New
3G_SGSN
1. RRC connection
establishment
1. RRC update required (old RAI, old PTMSI)
2. SGSN Context Required (old PTMSI, old RAI)
2. SGSN Context Resp. (IMSI, Auth.triplets)
3. Security Functions
4. Update GPRS Location
5. Cancel Location
6. Insert Subscriber Data
6. Insert Subscriber Data Ack
7. Update GPRS Location Ack
8. RA upd Accept (new RAI, new PTMSI
9. RA update complete
10. Release
10. RRC connection release
5. Cancel Location Ack
Version 1 Rev 7 SRNC Relocation
A912
SRNC Relocation
This example shows SRNS relocation when the source RNC and target RNC are
connected to different 3G-MSC.
The procedure is as follows:
1. The UTRAN makes the decision to perform the Serving RNC relocation procedure,
including the decision of onto which RNC (Target RNC) the Serving RNC
functionality is to be relocated. The source SRNC sends SRNC Relocation
required messages to the MSC. This message includes parameters such as target
RNC identifier and an information field that shall be passed transparently to the
target RNC.
2. Upon reception of SRNC Relocation required message the Anchor MSC prepares
itself for the switch and determines from the received information that the SRNC
relocation will (in this case) involve another MSC. The Anchor MSC will then send
a Prepare SRNC Relocation Request to the applicable non-anchor MSC, including
the information received from the Source RNC.
3. The non-anchor MSC will send a SRNC Relocation Request message to the target
RNC. This message includes information for building up the SRNC context,
transparently sent from Source RNC (UE ID, No of connected CN nodes, UE
capability information), and directives for setting up Iu user plane transport
bearers. When Iu user plane transport bearers have been established, and target
RNC has completed its preparation phase, SRNC Relocation Proceeding 1
message is sent to the non-anchor MSC.
4. The Prepare SRNC Relocation Response that is sent from non-anchor MSC to
Anchor MSC will contain the SRNC Relocation Proceeding 1 received command
from the target RNC.
5. When the SRNC Relocation Proceeding 1 command has been received in the
Anchor MSC, the user plane transport bearers has been allocated between the
target RNC and Anchor MSC and the Anchor MSC is ready for the SRNC move.
Then the Anchor MSC indicates the completion of preparation phase at the CN
side for the SRNC relocation by sending the SRNC relocation proceeding 2
message to the Source RNC.
6. When the source RNC has received the SRNC Relocation Proceeding 2
message, the source RNC sends a SRNC Relocation Commit message to the
target RNC. The target RNC executes switch for all bearers at the earliest suitable
time instance.
7. Immediately after a successful switch at RNC, the target RNC (=SRNC) sends
SRNC Relocation Complete message to the non-anchor MSC. This message is
included by the non-anchor MSC in the Complete SRNC relocation message that
is sent to the anchor MSC. Upon reception of this message, the Anchor-MSC
switches from the old Iu transport bearers to the new ones.
8. After a successful switch at the Anchor MSC, a release indication is sent towards
the Source RNC. This will imply release of all UTRAN resources that were related
to this UE.
9. When the target RNC is acting as SRNC, it will send New MM System Information
to the UE indicating e.g. relevant Routing Area and Location Area. Additional RRC
information may then also be sent to the UE, e.g. new RNTI identity.
EMOTOROLA LTD. 2003
CP13: UMTS Overview
A913
SRNC Relocation
CP13_Ch10_06
UE
Source
RNC
Target
RNC
Anchor
MSC
HLR
Nonanchor
MSC
1. SRNC Relocation Required
2. Prepare SRNC Relocation
3. SRNC Relocation Request
3. SRNC Relocation Proceeding
4. Prepare SRNC response
5. SRNC Reloc Proceed 2
6. SRNC Reloc
Commit
7. SRNC Reloc Complete
7. Complete SRNC Reloc
8. Release
9. New MM System Info
10. Routing Area Update
(a)
(b)
A914
10TH JULY 95
Manual Title Goes Here
G1
Glossary of technical terms and
abbreviations
10TH JULY 95 Manual Title Goes Here
G2
Numbers
10TH JULY 95
G3
Numbers
# Number.
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 3
rd
Generation Partnership Program.
A
G4
A
AAL ATM Adaptation Layer.
AAL2 ATM Adaptation Layer Type 2.
AAL5 ATM Adaptation Layer Type 5.
AGC Automatic Gain Control.
AICH Acquisition Indication Channel. (Physical Channel)
AMR Adaptive Multi Rate (Transcoder).
API Application Programming Interface.
ARQ Automatic repeat Request.
ATC ATM Transfer Capabilities
ATM Asynchronous Transfer Mode.
AUI Attachment Unit Interface.
B
10TH JULY 95
G5
B
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.
BER Bit Error Rate.
BLER Block Erasure Rate.
BS Billing System.
BTS Base Transmitter Station.
C
G6
C
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.
CBB Clock Bridge Board.
CBC Cell Broadcast Centre.
CBR Constant Bit Rate.
CCTrCH Coded Composite Transport Channel.
CCPCH Common Control Physical Channel. (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.
CDMA Code Division Multiple Access technique.
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 users
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(s) Call Detail Record(s).
CDVT Cell Delay Variation Tolerance.
Radio coverage area where the cell ID is broadcast. Cell
IDCell identifies the cell within UTRAN.
CGFu Charging Gateway Function, specific to UMTS.
CLP Cell Loss Priority.
CMIP Common Management Information Protocol.
CN Core Network.
Core Network Service and Transit Network Domains.
CP2/CP5/CP8 Common platform software message protocols.
CPCH Common Packet Channel. (Physical Channel)
cPCI Compact PCI.
CRC Cyclic Redundancy Check.
CRNC Controlling Radio Network Controller.
C
10TH JULY 95
G7
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.
CS-Service Domain Circuit Switched-Service Domain.
D
G8
D
DAC Digital to Analogue Converter.
dB Decibel. A unit of power ratio measurement.
DCCH Dedicated Control Channel.
DCH Dedicated Channel. (Transport Channel)
The DCH is a downlink or uplink transport channel that is
used to carry user or control information between the network
and a mobile station. The DCH is transmitted over the entire
cell or over only a part of the cell using lobe-forming
antennas.
DL Downlink.
DPC Digital Processing and Control.
DPCCH Dedicated Physical Control Channel. (Physical 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. (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).
DPDCH Dedicated Physical Data Channel. (Physical Channel)
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.
DRAC Dynamic Resource Allocation Control.
DRNC Drift Radio Network Controller.
Control-plane functions that pertain to the management of a
particular users radio access signalling and bearer
connection to the Iur interface.
DSCH Downlink Shared Channel.
The DSCH is a downlink transport channel shared by several
UEs carrying dedicated control or traffic data.
DSI De-serialising Interface.
DSP Digital Signal Processor.
DTCH Dedicated Transport Channel.
DTX Discontinuous Transmission.
E
10TH JULY 95
G9
E
E1 2 Mbit/s digital transmission link (32 x 64 kbit/s timeslots).
EEPROM Electrically Erasable Programmable ROM.
F
G10
F
FACH Forward Access Channel. (Transport 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.
FDD Frequency Division Duplex.
FMK FrameWork.
FPGA Field Programmable Gate Array.
FRAS Feature Requirement and Architecture Specification.
FRU Field Replaceable Unit.
FS Full Scale.
FTP File Transfer Protocol.
G
10TH JULY 95
G11
G
Ga interface Interface between the CGFu and the SGSNu, and the CGFu
and the GGSNu.
GCRA Generic Cell Rate Algorithm.
GGSNu Gateway GPRS Support Node, specific to UMTS.
Gi interface Interface between the GGSNu and the PS-Service Domain.
Gn interface Interface between the SGSNu and the GGSNu.
GPRS General Packet Radio System.
GPS Global Positioning System.
Gr interface Interface between the SGSNu and the HLR.
GRNC Generic Radio Network Controller.
Control-plane functions that pertain to the 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.
GSM Global System for Mobile Communications.
GSNu GPRS Support Node, specific to UMTS.
High performance broadband packet-switching node.
GUI Graphical User Interface.
H
G12
H
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.
HLR Home Location Register.
I
10TH JULY 95
G13
I
ID Identifier.
IMA Inverse Multiplexing for ATM.
IP Internet Protocol.
IPPS
ISDN Integrated Services Digital Network.
ISS Integrated Support Service.
Iu Reference points between Access and Serving Network
domains.
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.
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.
K
G14
K
L
10TH JULY 95
G15
L
LA Location Area.
LLMF Low Level Maintenance Functions.
LMT Local Maintenance Terminal.
LPA Linear Power Amplifier.
LPF Low Pass Filter.
LVDS Low Voltage Digital Signal.
M
G16
M
MAC Media Access Control.
MSCu Mobile Switching Centre, specific to UMTS.
MIB Management Information Base.
MMI Man Machine Interface.
MPROC Master Processor.
N
10TH JULY 95
G17
N
NBAP Node B Application Part.
Is used for setting up RAB in the RNL over the Iub.
NE Network Element.
NIB Network Interface Board.
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.
Node B ID identifies the Node B within UTRAN (used for
measurement reporting for instance).
NPC Network Parameter Control.
NRT Non Real Time.
O
G18
O
O&M Operations and Maintenance.
OMC-G Operations and Maintenance Centre-GPRS.
OML Interface between each RNC and the controlling OMC-U.
Also the interface between the SGSNu and the controlling
OMC-Gu.
OMC-R Operations and Maintenance Centre-Radio.
OMC-T Operations and Maintenance Centre-Transportation network.
OMC-U Operations and Maintenance Centre-UMTS.
OpenMaster Bull product for integrated systems management.
P
10TH JULY 95
G19
P
PACE Payload Active CP2 Emulator.
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.
PCI Peripheral Component Interconnect.
PCU Packet Control Unit.
PCS Physical Channel Segmentation.
PDU Protocol Data Unit.
PhCH Physical Channel.
PICH Page Indicator Channel. (Physical Channel)
PLMN Public Land Mobile Network.
PMC PCI Mezzanine Card.
PRACH Physical Random Access Channel. (Physical Channel)
The PRACH is an uplink physical channel that is used to
carry the RACH.
PS-Service Domain Package Switched-Service Domain.
PSM Power Supply Module.
PSTN Public Switched Telephone Network.
PSU Power Supply Unit.
Q
G20
Q
QoS Quality of Service.
QPSK Quadrature Phase Shift Keying.
R
10TH JULY 95
G21
R
RA Routing Area.
RAB Radio Access Bearer.
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.
RANAP Radio Access Network Application Part.
Radio network signalling over the Iu.
RAP Radio Access Procedures.
RF Radio Frequency.
RFSI RF to Serial Interface.
RLC Radio Link Control.
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).
ROM Random Access Memory.
RRC Radio Resource Control.
RRCAM RRC Acknowledge Mode.
RRCUM RRC Unacknowledge Mode.
RSSI Received Signal Strength Indicator.
RT Real Time.
Rx Receive.
S
G22
S
SAAL Signalling AAL.
SAR Segmentation and Re-assembly.
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.
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.
SCU Slim Carrier Unit (Radio).
SF Spreading Factor.
SGSNu Serving GPRS Support Node, specific to UMTS.
SNMP Simple Network Management Protocol.
SI Serialising Interface.
SIR Signal to Interference Ratio.
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.
SPROC System Processor.
Is a MPC750 processor that is responsible for executing all of
the site resident software.
SRNC Serving Radio Network Controller.
Control-plane functions that pertain to the management of a
particular users 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 users radio access
signalling and bearer connection to the Iu-PS interface.
T
10TH JULY 95
G23
T
TFCI Transport Format Combination Indicator.
TFCS Transport Format Combination Set.
TFS Transport Format Set.
TFTP Trivial File Transfer Protocol.
TGL Transmission Gap Length.
TPC Transmit Power Control.
TrCH Transport Channel.
TTI Transmission Time Interval.
tty Tele-Type.
Tx Transmit.
U
G24
U
UBR Unspecified Bit Rate.
UE User Equipment.
UMTS Universal Mobile Telecommunications System.
UNI User Network Interface.
UPC Usage Parameter Control.
URIB UMTS Radio Interface Board.
URXB UMTS Receiver Board.
USNB UMTS Synthesiser Board.
UTRAN UMTS Terrestrial Radio Access Network.
UTXB UMTS Transmitter Board.
UL Uplink.
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.
V
10TH JULY 95
G25
V
VCAT Vector Capture and Analysis Tool.
VC Virtual Channel.
VCC Virtual Channel Connection.
VP Virtual Path.
VPC Virtual Path Connection.
W
G26
W
WAN Wide Area Network.
WCDMA Wideband CDMA.
WDM Wideband Digital Modem.
X
10TH JULY 95
G27
X
Y
G28
Y
Z
10TH JULY 95
G29
Z
Z
G30

CP13 Motorola UMTS

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CP13 Motorola UMTS

Uploaded by

Copyright:

Available Formats

CHAPTER 2

Version 1 Rev 7 IMT-2000 Roadmap

Reduce the Telecommunications gap

Version 1 Rev 7 Research and Proposal

Macrodiversity Combining and Splitting

Version 1 Rev 7 Radio network Controller (RNC)

Application Specific Terminals

Dynamic Software Configurability

Value Adding Features

Version 1 Rev 7 User Equipment (UE)

Basic ID of Equipment Capabilities

Emergency calls without USIM

Dynamic Software Configurability

Support of Authentication and Encryption

Version 1 Rev 7 Quality of Service

F3 Key generating function used to compute CK

F2 Message authentication function used to compute RES and XRES

F1* Message authentication function used to compute MACS

F5* Key generating function used to compute AK in resynchronisation procedures

F5 Key generating function used to compute AK in normal procedures

F4 Key generating function used to compute IK

F9 Signalling elements between the UE and RNC

F8 Data transfer between the UE and RNC

Version 1 Rev 7 Generation of Authentication Vectors/Tokens

Version 1 Rev 7 Virtual Channels and Paths

Version 1 Rev 7 Scrambling Codes vs Channelisaton Codes

Determine FBI message

You might also like