Bss Gprs Database-sys102

8/8/2019 Bss Gprs Database-sys102

1/250

CHAPTER 2 CHAPTER 3 CHAPTER 4CHAPTER 1


2/250


3/250

BSS GPRS Database

Training Manual

Issue 2 Revision 0

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

SYS102


4/250


5/250

FOR TRAININGPURPOSES ONLY THISMANUAL WILL NOT BE

UPDATED

Issue 2 Revision 0

TrainingManual

BSS

GPRS

Database

Issue2

Revis

ion0

SYS102

BSS GPRS

Database

SYS102

Pos

itin

mark

for

TED

sp

ine

TrainingManual


6/250


7/250

EMOTOROLA LTD. 2001 SYS102: BSS GPRS Database

FOR TRAINING PURPOSES ONLY THIS MANUAL WILLNOT BE UPDATED

i

Issue 2 Revision 0

SYS102

BSS GPRS Database

E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999

All Rights Reserved

Printed in the U.K.


8/250

Issue 2 Revision 0

EMOTOROLA LTD. 2001SYS102: BSS GPRS Database


ii

Copyrights, notices and trademarks

Copyrights

The Motorola products described in this document may include copyrighted Motorola computerprograms 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.

RestrictionsThe 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.

AccuracyWhile 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.

Aspira, Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.

All other brands and corporate names are trademarks of their respective owners.


9/250

Issue 2 Revision 0



iii

General information 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Important notice 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cross references 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Text conventions 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

First aid in case of electric shock 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1GPRS Review i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Network Overview 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The GPRS Support Node Network (GSN) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-G 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Base Station System (BSS) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Mobile Station (MS) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Application Protocols 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Layer 2 / Layer 3 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Internet Protocol (IP) 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Tunnelling Protocol (GTP) 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User Data gram Protocol / Transmission control Protocol (UDP/TCP) 14. . . . . . . .

Subnetwork Dependent Convergence Protocol (SNDCP) 16. . . . . . . . . . . . . . . . . . .

Logical Link Control (LLC) 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Station System GPRS Protocol (BSSGP) 18. . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service (NS) 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Application Protocols 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Medium Access Control (MAC) layer 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Review 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Overview 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Coding Schemes 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Coding Scheme Rates 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Logical Channels 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Broadcast Control Channel (PBCCH) 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Common Control Channels 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS 52 Multiframe 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timeslot Configuration 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Traffic Channels 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Classes with Multislot Capability 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixed Allocation Timeslot Assignment 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Continuous Timing Advance 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2PCU Architecture i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


10/250

Issue 2 Revision 0



iv

Packet Control Unit (PCU) 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The GPRS solution 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Interface Control Processor 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU System Processor 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Resource Processor 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initial Configuration 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell INS/OOS 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier State Changes 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier Activation 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Originated Packet Access and Transfer 220. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Terminated Packet Access and Transfer 222. . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Interface 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frame Relay Functional Unit 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Functional Unit 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Router (GR) 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gateway Transmit Manager 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service Test 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Flow Control Buffer Manager (FBM) 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault Management 232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault Detection and Handling System 232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Audit Process 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Web MMI 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Management 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU Central Authority (pCA) 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3BSS/PCU Commands i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Equipage 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .BSC Site Device Equipage Hierarchy 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU Site Device Equipage Hierarchy 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PSP 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dependencies 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DPROC 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSI 310. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MMS Device 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MMS Priority 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GDS or GBL 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Data Stream (GDS) 314. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32K Trau 316. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Backhaul TS equipage 316. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Signalling Link (GSL) 318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service 320. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service 322. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Addressing 324. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NSEI/RAC Mapping 324. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL Device 326. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL Device 328. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


11/250

Issue 2 Revision 0



v

Network Service Virtual Connection (NSVC) 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Committed Information Rate (CIR) 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Committed Burst Size (Bc) 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Excess Burst Size (Be) 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSGP Virtual Circuit Identifier (BVCI) 332. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .GPRS Signalling BVCI 334. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Flow Control 336. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Flow Control Leaky Bucket 338. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSGP Virtual Circuit (BVC) Blocking and Unblocking 340. . . . . . . . . . . . . . . . . . . . . . . . . . .

BVC Reset 342. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service Block, Reset, Unblock, Test 344. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service Test 346. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LCF 348. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Carrier 350. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Reconfiguration of switchable GPRS PDCHs 352. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timeslot Management Parameters 352. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Paging Control Parameters 354. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

gprs_network_operation_mode 354. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Routing Area / GPRS Enabled 356. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Link Control (RLC) Parameters 358. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

T3168 Establishment of Uplink TBF 358. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Link Control Parameters 360. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Release of Uplink TBF 360. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N3102 362. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Link Control Parameters 364. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MAC Control Parameters 366. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Exercise Exercise1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Answers Answers1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary of Terms i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Numbers iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D xiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E xvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F xix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

G xxi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

H xxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

K xxvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


12/250

Issue 2 Revision 0



vi

L xxvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M xxix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N xxxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

O xxxv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

P xxxvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Q xl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R xli. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

S xliv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

T xlviii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U li. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V lii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

W liii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

X liv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Z lv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


13/250

Issue 2 Revision 0 General information



1

General information

Important notice

If this manual was obtained when attending a Motorola training course, it will not beupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then corrections will be supplied automatically by Motorola in the form ofGeneral Manual Revisions (GMRs).

Purpose

Motorola cellular communications manuals are intended to instruct and assist personnelin the operation, installation and maintenance of the Motorola cellular infrastructureequipment and ancillary devices. It is recommended that all personnel engaged in suchactivities be properly trained by Motorola.

Failure to comply with Motorolas operation, installation and maintenanceinstructions may, in exceptional circumstances, lead to serious injury or death.

WARNING

These manuals are not intended to replace the system and equipment training offered byMotorola, although they can be used to supplement and enhance the knowledge gainedthrough such training.


14/250

Issue 2 Revision 0General information



2

Cross references

Throughout this manual, cross references are made to the chapter numbers and sectionnames. The section name cross references are printed bold in text.

This manual is divided into uniquely identified and numbered chapters that, in turn, aredivided into sections. Sections are not numbered, but are individually named at the top ofeach page, and are listed in the table of contents.

Text conventions

The following conventions are used in the Motorola GSM manuals to represent keyboardinput text, screen output text and special key sequences.

Input

Characters typed in at the keyboard are shown like this.

Output

Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this.

Special key sequences

Special key sequences are represented as follows:

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

ALT-f Press the Alt and f keys at the same time.

| Press the pipe symbol key.

CR or RETURN Press the Return (Enter) key. The Return key isidentified with the symbol on both the X terminal andthe SPARCstation keyboards. The SPARCstationkeyboard Return key is also identified with the wordReturn.


15/250

Issue 2 Revision 0 First aid in case of electric shock



3

First aid in case of electric shock

Warning

WARNING Do not touch the victim with your bare handsuntil theelectric circuit is broken.

Switch off.If this is not possible, protect yourselfwith dryinsulating material and pull or push the victim clear of theconductor.

Artificialrespiration

In the event of an electric shock it may be necessary to carry out artificial respiration.

Send for medical assistance immediately.

Burns treatment

If the patient is also suffering from burns, then, without hindrance to artificial respiration,carry out the following:

1. Do not attempt to remove clothing adhering to the burn.

2. If help is available, or as soon as artificial respiration is no longer required, coverthe wound with a dry dressing.

3. Do not apply oil or grease in any form.

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 tamper with 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 awritten report by fax, Swindon +44 (0)1793 430987 or China +86 1068423633 (fax).

4. Collect evidence from the equipment under the guidance of the Customer NetworkResolution Centre.

Warning labels

Personnel working with or operating Motorola equipment must comply with any warninglabels fitted to the equipment. Warning labels must not be removed, painted over orobscured in any way.


16/250

Issue 2 Revision 0First aid in case of electric shock



4

High voltage

Certain Motorola equipment operates from a dangerous high voltage of 230 V ac singlephase or 415 V ac three phase supply which is potentially lethal. Therefore, the areaswhere the ac supply power is present must not be approached until the warnings and

cautions in the text and on the equipment have been complied with.To achieve isolation of the equipment from the ac supply, the ac input isolator must beset to off and locked.

Within the United Kingdom (UK) regard must be paid to the requirements of theElectricity at Work Regulations 1989. There may also be specific country legislationwhich need to be complied with, depending on where the equipment is used.

RF radiation

High RF potentials and electromagnetic fields are present in the base station equipmentwhen in operation. Ensure that all transmitters are switched off when any antennaconnections have to be changed. Do not key transmitters connected to unterminated

cavities or feeders.

Refer to the following standards:

S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

Laser radiation

Do not look directly into fibre optic cables or optical data in/out connectors. Laserradiation can come from either the data in/out connectors or unterminated fibre optic

cables connected to data in/out connectors.

Liftingequipment

When dismantling heavy assemblies, or removing or replacing equipment, the competentresponsible person must ensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations. When equipments have to bemanhandled, reference must be made to the Manual Handling of Loads Regulations1992 (UK) or to the relevant manual handling of loads legislation for the country in whichthe equipment is used.

Do not ...... substitute parts or modify equipment.

Because of the danger of introducing additional hazards, do not install substitute parts orperform any unauthorized modification of equipment. Contact Motorola if in doubt toensure that safety features are maintained.

Lithium batteries

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithiumbatteries must not be removed or replaced. Any boards containing defective lithiumbatteries must be returned to Motorola for repair.


17/250

Issue 2 Revision 0 First aid in case of electric shock



5

Definitions

NOTE The above result applies only in the direction of maximumradiation of the antenna. Actual installations may employantennas that have defined radiation patterns and gains that

differ from the example set forth above. The distances calculatedcan vary depending on the actual antenna pattern and gain.

Observe the following cautions during operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these cautions orwith specific cautions elsewhere in the Motorola manuals may result in damage to theequipment. Motorola assumes no liability for the customers failure to comply with theserequirements.

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 orobscured in any way.

Specific cautions

Cautions particularly applicable to the equipment are positioned within the text of thismanual. These must be observed by all personnel at all times when working with theequipment, as must any other cautions given in text, on the illustrations and on theequipment.

Fibre optics

The bending radius of all fibre optic cables must not be less than 30 mm.

Static discharge

Motorola equipment contains CMOS devices that are vulnerable to static discharge.Although the damage caused by static discharge may not be immediately apparent,CMOS devices may be damaged in the long term due to static discharge caused bymishandling. Wear an approved earth strap when adjusting or handling digital boards.

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer ofinsulation that is susceptible to damage from electrostatic charge. Such a charge appliedto the leads of the device could cause irreparable damage.

These charges can be built up on nylon overalls, by friction, by pushing the hands intohigh insulation packing material or by use of unearthed soldering irons.

MOS devices are normally despatched from the manufacturers with the leads shortedtogether, for example, by metal foil eyelets, wire strapping, or by inserting the leads intoconductive plastic foam. Provided the leads are shorted it is safe to handle the device.


18/250


19/250



i

Chapter 1

GPRS Review


20/250

Issue 2 Revision 0



ii


21/250

Issue 2 Revision 0



iii

Chapter 1GPRS Review i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Network Overview 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The GPRS Support Node Network (GSN) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OMC-G 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Base Station System (BSS) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Mobile Station (MS) 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Layer 2 / Layer 3 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Internet Protocol (IP) 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Tunnelling Protocol (GTP) 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User Data gram Protocol / Transmission control Protocol (UDP/TCP) 14. . . . . . . .

Subnetwork Dependent Convergence Protocol (SNDCP) 16. . . . . . . . . . . . . . . . . . .

Logical Link Control (LLC) 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Station System GPRS Protocol (BSSGP) 18. . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service (NS) 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Medium Access Control (MAC) layer 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Review 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Overview 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Coding Schemes 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Logical Channels 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Broadcast Control Channel (PBCCH) 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Common Control Channels 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS 52 Multiframe 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timeslot Configuration 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Traffic Channels 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Classes with Multislot Capability 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixed Allocation Timeslot Assignment 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Continuous Timing Advance 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


22/250

Issue 2 Revision 0



iv


23/250

Issue 2 Revision 0 Objectives



11

Objectives

On completion of this chapter the student will be able to:

S Explain the air interface structure for GPRS.

S Describe the protocol layers of the BSS and MS for GPRS.

S Describe GPRS mobile operation.


24/250

Issue 2 Revision 0GPRS Network Overview



12

GPRS Network OverviewThe diagram opposite shows a simplified General Packet Radio Service (GPRS)network. Each network component is illustrated once, however, many of the componentswill occur several times throughout a network.

The principal network component groups are:

The GPRSSupport NodeNetwork (GSN)

The GPRS Support Node Network (GSN) is the main element in the GPRSinfrastructure. It is a high performance, broadband packet switching node that providesconnection and interworking with various data networks, mobility management anddelivery of data packets to mobile stations. The GSN Network is made of the followingcomponent groups.

S CommHub The GSN CommHub is the central connection point for the

components in a GPRS system. It provides LAN connectivity between GPRScomponents through Ethernet and WAN connectivity to data networks outside theGPRS system.

S ISS The Integrated Support Services provides GPRS system components withthe current time, domain name translation and network information.

S GGSN The Gateway GPRS Support Node provides network access to externalhosts so they can communicate with MSs. It also decapsulates and forwardsexternal data networks packets to the appropriate data network.

S SGSN The Serving GPRS Support Node detects and tracks GPRS MSs in itsservice area and provides a reliable, secure data channel as the MS movesbetween cells.

OMC-GThe OMC-G enables operators to use an NT graphical user interface (GUI) whenmanaging the GPRS components. System operators use the OMC-G to configure andmonitor system components and view performance data.

The Base StationSystem (BSS)

The Base Station System provides the radio frequency link between the GPRS networkinfrastructure and mobile subscribers throughout the operational area. A BSS consists ofthree components:

S Base Station Controller (BSC).

S Base Station Transceiver (BTS).

S Packet Control Unit (PCU) The Packet Control Unit (PCU) performs radiofunctions and GPRS network functions. It has interfaces to the OMC-R, BSC andthe SGSN.

The MobileStation (MS)

The MSs can belong to three classes A, B or C the class determines whether GPRS andCircuit Switched services can be carried out at the same time or not. The mobiles arealso divided in to multi slot classes that determine the mobile capability of sending andreceiving over multiple slots in a TDMA frame.


25/250

Issue 2 Revision 0 GPRS Network Overview



13

GPRS Network Overview

Internet

Gi

Frame Relay

RXCDR MSC

PCU

BSC

BTS

SGSN

GGSNISS

Router

Comm

Hu

b

BSS101_Mod1_Ch1_01

OMCG


26/250

Issue 2 Revision 0GPRS Application Protocols



14

GPRS Application Protocols

Layer 2 / Layer 3

The purpose of GPRS is to act as a bearer service to transport packets of data from anexternal network to a mobile subscriber. The contents of user data packets travellingacross the GPRS network are in fact transparent, and thus the protocols of GPRS areconsidered to be layer 2 protocols. Protocols running from the external network to themobile subscriber can actually be considered to be running at the IP layer, layer 3.Layers above this are concerned with the application or function that the mobilesubscriber/external network is carrying out, and thus is of no interest to the GPRSnetwork.

Internet Protocol(IP)

The Internet protocol appears twice in the GPRS protocol stack. It is both used withinthe Internet to transport data to and from the GPRS network, and also within the GPRSnetwork itself, to route user data and control signalling between the GSN elements.

GPRS TunnellingProtocol (GTP)

GPRS Tunnelling Protocol (GTP) allows multi-protocol packets to be tunnelled throughthe GPRS backbone, between GSN elements. These GTP tunnels carry user data andcontrol signaling. GTP usesTransmission Control Protocol/Internet Protocol (TCP/IP) andUser Data gram Protocol/Internet Protocol (UDP/IP) protocols to communicate betweenSGSN and GGSN. GTP simultaneously supports two operation modes for information

transfer between the GGSN and the SGSN: acknowledged and unacknowledged.

User Data gramProtocol /Transmissioncontrol Protocol(UDP/TCP)

User Data gram Protocol (UDP) carries GTP PDUs for protocols that do not need areliable data link. UDP also provides protection against corrupted GTP PDUs.

Transmission Control Protocol (TCP) carries GTP PDUs for protocols requiring a reliable

data link. TCP also provides flow control and protection against lost and corrupted GTP

PDUs.


27/250

Issue 2 Revision 0 GPRS Application Protocols



15


SYS102_1_2

IP

SNDCP

LLC

RLC/MAC

GSM RF

RLC/MAC

GSM RF

BSSGP

NetworkService

L1 Bis

IP

GTP

TCP/UDP

IP

L1

L2

GTP

TCP/UDP

IP

LLC

BSSGP

NetworkService

L1 Bis L1

L2

SNDCP

MS BSS SGSN GGSN


28/250




16

SubnetworkDependentConvergenceProtocol

(SNDCP)Network Layer protocols are intended to be capable of operating over services derivedfrom a wide variety of subnetworks and data links. GPRS supports several network layerprotocols providing protocol transparency for the users of the service. Introduction of newnetwork layer protocols to be transferred over GPRS shall be possible without anychanges to GPRS. Therefore, all functions related to the transfer of Network layerProtocol Data Units (N-PDUs) shall be carried out in a transparent way by GPRS networkentities using Subnetwork Dependent Convergence Protocol (SNDCP). Another functionof SNDCP is to improve channel efficiency fulfilled by protocol compression and datacompression.

Logical LinkControl (LLC)

The LLC provides a highly reliable logical connection between the SGSN and the MS andas such spans the Gb and Um interfaces. In addition the LLC has been designed to beindependent of the underlying radio interface protocols. The LLC includes functions for:

S Provision of one or more logical link connections discriminated between by meansof the Service Access Point Identifier (SAPI).

S Sequence Control.

S Error detection and Recovery.

S Flow Control.

S Ciphering.


29/250




17


SYS102_1_2

IP

SNDCP

LLC

RLC/MAC

GSM RF

RLC/MAC

GSM RF

BSSGP

Network

Service

L1 Bis

IP

GTP

TCP/UDP

IP

L1

L2

GTP

TCP/UDP

IP

LLC

BSSGP

Network

Service

L1 Bis L1

L2

SNDCP

MS BSS SGSN GGSN

sys102_1_2a

Packet DataProtocol

Packet DataProtocol

Packet DataProtocol

NPDU

SNPDU

LLC

SNDCP

NSAPI

SAPI


30/250




18

Base StationSystem GPRSProtocol(BSSGP)

BSSGP is situated on top of the Network Services layer within the GPRS protocol stack.This protocol is specific to GPRS, providing services between the SGSN and the BSS.To that end it is completely invisible to the mobile subscriber, despite the fact that thesubscriber avails it of the services it has to offer. BSSGP uses the underlying FrameRelay Network to create virtual circuits between the SGSN and the BSS, which carrycontrol and signalling data. In addition, it forms an interface for user data between theRLC layers and the LCC layer at the respective ends. (this is shown on the diagramopposite)

The functions of the BSSGP protocol are to:

S Provide a connectionless link between the SGSN and the BSS.

S Transfer data unconfirmed between the SGSN and the BSS.

S Provide tools for the bi-directional control of the flow of data between the SGSNand the BSS.

S Handle paging requests from the SGSN to the BSS.

S Give support for the flushing of old messages from the BSS, for example when anMS changes BSSs.

S Support multiple layer 2 links between the SGSN and the BSS.

Network Service(NS)

The Network Service (NS) utilizes Frame Relay protocol to transports the BSSGP PDUs.In addition it controls the link in terms of reset, blocking/unblocking and periodic testing.The Network Service Control entity is responsible for the following functions:

S NS SDU transmission: The NS SDUs shall be transmitted on the NSVCs. TheNSSDUs are encapsulated into Network Service Control PDUs, which in turn areencapsulated into SubNetwork Service PDUs.

S Load sharing: The load sharing function distributes the NS SDU traffic amongst theavailable (i.e. unblocked) NSVCs of a group.

S NSVC management: A blocking procedure is used by an NS entity to inform anNS peer entity when an NSVC becomes unavailable for NS user traffic. Anunblocking procedure is used for the reverse operation. A reset procedure is used

between peer NS entities in order to set an NSVC to a determined state, afterevents resulting in possibly inconsistent states of the NSVC at both sides of theGb interface. A test procedure is used to check that an NSVC is operatingproperly between peer NS entities.


31/250




19

Base Station System GPRS Protocol (BSSGP)

SYS102_1_3

IP

SNDCP

LLC

RLC/MAC

GSM RF

RLC/MAC

GSM RF

BSSGP

NetworkService

L1 Bis

IP

GTP

TCP/UDP

IP

L1

L2

GTP

TCP/UDP

IP

LLC

BSSGP

NetworkService

L1 Bis L1

L2

SNDCP

MS BSS SGSN GGSN

CPO7_4_8

Relay GMM NM NMGMMLLC

BSSGP GMM NM

BSSGP

Network ServiceNetwork Service

RL GMM NMRL

BSSGPRLC/MAC

Service Model in a BSS Service Model in a SGSN


32/250




110


Radio Link Control (RLC)

The Radio Link Control (RLC) function is responsible for:

S Interface allowing transfer of UL PDUs between the Logical Link Control (LLC)layer and the Media Access Control (MAC) function.

S Segmentation of LLC PDUs into RLC data blocks and the re-assembly of RLCdata blocks into LLC PDUs.

S Backwards Error Correction (BEC) Procedures, enabling selective retransmissionof RLC data blocks.

An RLC connection comprises two peer entities. Each RLC endpoint has a receiver thatreceives RLC data blocks. Each RLC endpoint has a transmitter that transmits RLC datablocks.

Each RLC data block may be encoded using any of the available channel codingschemes, CS1, CS2, CS3 and CS4. The chosen scheme will effect the degree ofsegmentation and subsequent reassembly. The structure of the RLC Data Blocks isdependent upon the transmission direction, i.e. Uplink or Downlink.

Medium AccessControl (MAC)layer

The main function of the MAC layer is the control of multiple MSs sharing a commonresource on the GPRS air interface. This is of particular importance in the uplinkdirection, where we can use fixed or dynamic allocation to allow MS to transfer data.


33/250




111

Radio Link Control/Medium Access Control

NormalBurst

sys102_1_13

LLC

RLC/MAC

PhysicalLayer

NormalBurst

NormalBurst

NormalBurst

BH BH BHBCS BCS BCSInfo Field Info Field Info Field

Information FieldFH FCS

LLC

RLC

MAC

Physical

Layer

LLC

RLC

MAC

PhysicalLayer

MS BSS SGSN


34/250

Issue 2 Revision 0GPRS Review



112

GPRS Review

System

OverviewGPRS is a set of new GSM Bearer and Teleservices providing Packet modeTransmission with the PLMN and external networks. It allows the MSs to send andreceive data in an end to end packet transfer without using resources reserved for circuitswitch.

GPRS will be able to provide both Point to Point (PTP) and Point to Multipoint (PTM).

The GSM radio is broken down for efficient use by data users.

S Multiple MSs may use a single timeslot

S Multiple MSs may share multiple timeslots

S A single MS may use multiple timeslots (up to eight)

S Different MSs may use uplink or downlink radio resource

S Each radio may use one of four channel coding schemes to get up to 21.4kbps ofdata per timeslot

The channel coder firmware will support CS1 to CS4 for GPRS at GSN1.1


35/250

Issue 2 Revision 0 GPRS Review



113

System Overview

SYS102_1_4

Multiple MSs may use a single TS

Multiple MSs may share multiple TS

A single MS may use multiple TS (up to 8)

Different MSs may use one of four channel coding schemes

Each radio may use one of four channel coding schemes


36/250




114

GPRS CodingSchemes

In a GPRS network, there are several channelcoding schemes defined to operate overthe air interface and provide varying data rates to the enduser. In general, as the

mobile experiences better RF conditions, the coding scheme in use can be changedautomatically by the PCU to afford higher throughput. Essentially the differencesbetween coding schemes determine the amount of protection provided to the data. Thechannel coding schemes in GPRS are referred to as CS1, CS2, CS3, and CS4.

Due to the degree to which the data is coded as the coding scheme changes, the radioproperties experienced by the mobile station will dictate how efficient a given codingscheme is. When there is not much coding on the data (i.e. CS3 and CS4), a givenblock will generally not be received correctly in poor RF environments. It is the PCUsresponsibility to calculate which coding scheme should be used. This decision is basedupon:

Downlink signal and interference level information provided by the MSduring channel quality reports, sent with the downlink packet ack/nack.

Uplink Rx signal level sampled by the BTS

Uplink Interference level on idle blocks sampled by the BTS

When the coding scheme is calculated for uplink data transfers, the information providedto the PCU by the channel coders within the BTS, are combined to define the C/I (Carrierto Interference) ratio for the given mobile station.

The data rates for the GPRS coding schemes are as follows:

Coding SchemeRates

Channel Coding Scheme Throughput

(Per TS)

ConvolutionalCoding Rate

CS1 9.05 Kbps 1/2

CS2 13.5 Kbps 2/3

CS3 15.6 Kbps 3/4

CS4 21.4 Kbps 1


37/250




115

GPRS Coding Schemes

Sys102_1_14

CS4

CS1

CS2

CS3

Coding SchemeRates

Channel Coding Scheme Throughput

(Per TS)

Convolutional Coding Rate

CS1 9.05 Kbps 1/2

CS2 13.5 Kbps 2/3

CS3 15.6 Kbps 3/4

CS4 21.4 Kbps 1


38/250




116

Logical Channels

GPRS uses one or more timeslots per cell known as Packet Data Channel (PDCH).

PDCHs are physical channels, which consist of various logical channels.

Packet BroadcastControl Channel(PBCCH)

The PBCCH broadcasts packet data system information and follows the same rules asthe BCCH. The existence of the PBCCH is indicated on the BCCH. If the PBCCH is notallocated then the packet system information will be broadcasted on the BCCH.

Packet CommonControl Channels

The PCCH comprises logical channels for common control signalling of packet data. ThePCCH is similar in format to the CCCH and when not allocated in a cell, packet transfercan be initiated by the CCCH.

Packet Random Access Control Channel (PRACH) UL only

Uplink only. Used by an MS to initiate uplink transfer for sending data or signallinginformation. PRACH is also used to obtain timing advance information. For a cell with noPCCH, the MS can initiate a uplink transfer using the RACH.

Packet Paging Channel (PPCH) DL only

Downlink only. PPCH is used to page an MS prior to a downlink transfer. The PPCH uses

the same predefined rules as the PCH. For a cell with no PCCH, the MS can be pagedusing the PCH. Further to this, an MS engaged in uplink packet switched transfer can bepaged on a Packet Associated Control Channel (PACCH).

Packet Access Grant Channel (PAGCH) DL only

Downlink only. PAGCH is used in the packet transfer establishment phase to sendresource assignment to an MS prior to packet transfer.

Note: Resource assignment for a downlink assignment can be sent on the PACCH if theMS is currently involved in a Packet transfer.

Packet Notification Channel (PNCH) DL only

Downlink only to send a Point to Multipoint Multicast (PTM-M) notification to a group ofMSs prior to a PTM-M packet transfer taking place. This notification is in the form of aresource assignment message.


39/250




117

Logical Channels

CCH

CCCH BCCH

RACH PCH/AGCH

PCCH

PBCCH

PCCCH

PRACH PAGCH PNCHPPCH

Sys102_1_6

CBCH


40/250




118

GPRS 52Multiframe

The 52 frame structure shown opposite is a new frame. Its structure is totally differentfrom the existing 51 and 26 frame structures.

The 52 Multiframe does not have a rigid structure. Essentially the different channels areidentified by message type. The Multiframe can carry control channels or data channels.

CONTROL CHANNELS TRAFFIC CHANNELS

PBCCH PDTCH

PPCH PACCH

PAGCH

PNCH

The structure for a 52 frame multiframe consists of 12 blocks of four frames called radioblocks and four idle frames. Each radio block may be used to carry any channel of traffic

or control independently of the other radio blocks. Further, each radio block can provide acommunication path to a mobile as such theoretically twelve MS can send/receive in any52 frame multiframe. It has a duration of 240 ms, the equivilant of two 26 framemultiframes.

Mobiles operating on a 52 Multiframe still require the capability to monitor a 51Multiframe. For example when performing neighbour cell measurements, the mobile mustextract the BSIC from the synchronization channel on the BCCH.

GPRS mobiles perform BSIC extraction during the 2nd and 4th idle frames. Theseframes occur exactly where an idle frame for a 26 Multiframe occurs. GPRS mobiles willtherefore read a different control channel on the BCCH of a neighbour cell. Each time amobile returns to monitor the neighbour cell BCCH.


41/250




119

52 Multiframe structure

sys102_1_5

0 1 2 3 4 5 6 7 0 1 072 3 4 5 6 1 072 3 4 5 6

B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11I I I I

NBNBNBNB

1 072 3 4 5 6

Radio Block

TDMA frame

240ms


42/250




120

TimeslotConfiguration

The BSS will support one GPRS carrier per cell. This carrier can be either the BCCH orNon-BCCH.

GPRS timeslots are divided into Reserved and Switchable timeslots.

Reserved GPRS Timeslot

A reserved GPRS timeslot is a timeslot that is used only for GPRS services.

Switchable GPRS Timeslot

A switchable timeslot is a timeslot that can be switched from GPRS service to circuitswitched service and vice versa.

GPRS vs CS

For switchable GPRS timeslots, circuit switched services always have priority. So, if thenumber of idle TCHs falls to zero and the BSS needs to set up a circuit switched callthen the BSS will reconfigure a switchable GPRS TS to a circuit switched timeslot.

Timeslot Configuration

Reserved GPRS timeslots are placed above Switchable GPRS timeslots which areplaced above circuit switched.


43/250




121

Timeslot configuration

Sys102_1_7

TCH

TCH

TCH

SW

SW

RES

RES

RES

TS0

TS1

TS2

TS3

TS4

TS5

TS6

TS7

TCH = Circuit Switched TS

SW = GPRS Switchable TS

RES = GPRS Reserved TS


44/250




122

Packet TrafficChannels

One Packet Data Traffic Channel (PDTCH) is mapped to one physical channel. Up to 8PDTCH on different TS but some frequency parameters can be allocated to one MS at

the same time.

Packet Associated Control Channel (PACCH)

One Packet Associated Control Channel (PACCH) is mapped on to one physicalchannel. PACCH is dynamically allocated on a block basis. It provides signallinginformation including acknowledgements, power control and timing advance information.The PACCH can also be used for resource allocation messages, whilst the MS is alreadycarrying out packet transfer.

If a single PDTCH is assigned to an MS then the PACCH will be assigned on the samephysical channel. If multiple PDTCHs are assigned to a mobile then the PACCH isalways allocated on one of the Packet Data Channels (PDCHs) on which the PDTCHsare allocated.

PACCH is bi-directional in nature. In other words whilst the assignment might be uplinkor downlink, if PDTCHs are assigned on the uplink then one corresponding downlinktimeslot must be monitored for the possible occurrences of the PACCH. At the sametime, the MS can use the uplink assignment to send a PACCH at any time.

UL PDTCH Fixed Allocation

Fixed Allocation uses the Packet Uplink Assignment to communicate a detailed fixeduplink resource allocation to the MS. This fixed allocation consists of a start frame, slotassignment and block assignment bitmap to represent the assigned blocks per timeslot.

PACCH, the MS will transmit a UL PACCH at any time. To gain a DL PACCH the fixedallocation will purposely have gaps to allow the MS to monitor all PDCH for a PACCHaddressed to it. To this purpose the network will leave sets of 3 timeslot gaps in theuplink fixed allocation for the purpose of transmission of the DL PACCH.

During transfer of RLC/MAC blocks a mobile station may request to continue theTemporary Block Flow (TBF) by transmitting a Packet Resource Request on the ULPACCH. The network then responds with a Packet Resource Reassignment on the DLPACCH.


45/250




123

UL PDTCH Fixed Allocation

Sys102_1_8



TS0 TS1 TS2 TS3 TS0 TS5 TS6 TS7

= MS assigned blocks + timeslots


46/250




124

PDTCHs Dynamic Allocation

Dynamic Allocation allows multiple MSs to use the same uplink resource. This isaccomplished by using the Uplink State Flag (USF), a 3 bit flag that can be used to allowup to 7 mobiles to access the same resource.

If, for example, a mobile is allocated in the assignment command timeslot 0, 2 and 3 thenthe mobile will monitor the downlink PDCH timeslots 0, 2 and 3 for its assigned USFvalue.

If the mobile receives the USF on a downlink block then on the next uplink block themobile will transmit and also on the next 3 blocks if USF granularity is set to 1.

The appearance of USF for the mobile on a TS will also affect its other assigned PDCHs.For example, a USF on TS2 with an assignment of TS 0, 2, 3 would mean to transmit onthe uplink on the next block on TS2 and 3.


47/250




125

PDTCHs Dynamic Allocation

sys102_1_8a

5 5 5 4 5 5 4 4

5 5 5 4 4455

3 3 2 2 3 3 2 2

3 3 2 2 3 3 2 2

I I

II

I I

I

I

I I

I

II

I

II

DL

DL

UL

UL

TS6

TS7

FCS

BH Information BCS BH Information BCS BH Information BCS

Information FieldFH

NB NB NB NB


48/250




126

MS Classes withMultislotCapability

Phase 2+ Mobiles have the capability to use multiple slots in one TDMA frame in both

uplink and downlink. They are split into classes 1 through 29.

The mobiles are split into two types:

S Type 1 MS are not required to transmit and receive at the same time

S Type 2 MS are required to transmit and receive at the same time

Tt = Time to transmit

Tr = Time to receive

a = A measurement is made

b = No measurement made

a)=1 with frequency hopping

= 0 without frequency hopping

b)=1 with frequency hopping or change from Rx to Tx

=0 without frequency hopping or no change from Rx to Tx

c)=1 with frequency hopping or change from Tx to Rx

=0 without frequency hopping and no change from Tx to Rx

Type 1 MS are not required to transmit and receive at the same time.

Type 2 MS are required to be able to transmit and receive at the same time.


49/250




127

MS Classes with Multislot capabilities

Multislot Maximum number of slots Minimum number of slots Type

Rx Tx Sum Tta Ttb Tra TrbDefault

1 1 1 2 3 2 4 2 1

2 2 1 3 3 2 3 1 1

3 2 2 3 3 2 3 1 1

4 3 1 4 3 1 3 1 1

5 2 2 4 3 1 3 1 1

6 3 2 4 3 1 3 1 1

7 3 3 4 3 1 3 1 1

8 4 1 5 3 1 2 1 1

9 3 2 5 3 1 2 1 1

10 4 2 5 3 1 2 1 111 4 3 5 3 1 2 1 1

12 4 4 5 2 1 2 1 1

13 3 3 NA NA a) 3 a) 2

14 4 4 NA NA a) 3 a) 2

15 5 5 NA NA a) 3 a) 2

16 6 6 NA NA a) 2 a) 2

17 7 7 NA NA a) 1 0 2

18 8 8 NA NA 0 0 0 2

19 6 2 NA 3 b) 2 c) 1

20 6 3 NA 3 b) 2 c) 1

21 6 4 NA 3 b) 2 c) 1

22 6 4 NA 2 b) 2 c) 1

23 6 6 NA 2 b) 2 c) 1

24 8 2 NA 3 b) 2 c) 1

25 8 3 NA 3 b) 2 c) 1

26 8 4 NA 3 b) 2 c) 1

27 8 4 NA 2 b) 2 c) 1

28 8 6 NA 2 b) 2 c) 1

29 8 8 NA 2 b) 2 c) 1

a) = 1 with frequency hopping0 without frequency hopping

b) = 1 with frequency hopping or change from Rx to Tx= 0 without frequency hopping or no change from Rx to Tx

c) = 1 with frequency hopping or change from Tx to Rx= 0 without frequency hopping and no change from Tx to Rx

Type 1 MS are not required to transmit and receive at the same time.Type 2 MS are required to be able to transmit and receive at the same time.


50/250




128

Fixed AllocationTimeslotAssignment

Fixed allocation presents particular restrictions to the allocation of Packet Data Channels

(PDCHs) to multislot mobiles. In particular, the assignment must not conflict with therules for Packet Associated Control Channel (PACCH) monitoring or transmission andmeasurements of neighbour cells.

If for instance a multislot mobile station Class 4 is assigned a 3 timeslot Temporary BlockFlow (TBF) downlink and no uplink TBF. In this example the Packet DownlinkAssignment does not assign Measurement Mapping Parameters to the mobile so the MSmust make neighbour cell power measurement in 24 out of every 26 TDMA frames.

For multislot Class 4 mobiles the time needed for the MS to make a neighbour cell signalmeasurement and then get ready to transmit is 3 timeslots. Therefore the mobile canmake a measurement in every TDMA frame.

If the mobile is polled on timeslot 1, with a Relative Reserved Block Period (RRBP) of

zero (to send PACCH from next RLC/MAC Block on timeslot 1), then the mobile willtransmit a PACCH on timeslot 1. This transmission obeys the time needed for the mobileto transmit for multislot Class 4 which is 1 TS. It also conforms to the time needed tocarry out neighbour cell measurements.


51/250




129

Fixed Allocation Timeslot Assignment

Sys102_1_10

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

RLC/MAC Block

poll

Downlink

Uplink

Ttb= 1 Tra= 3

Multislot class 4 (Rx= 3, Tx= 1, Sum= 4, 3 timeslot downlink TBF, with a poll

on timeslot 1 (the natural timeslot)


52/250




130

Timing Advance

Within GSM, the mobile subscriber is allocated space on a radio channel for only a shortperiod of time, 577s of a 4.615ms TDMA frame. Information on the air interface is sentusing a normal burst whose duration is 546s. It is therefore vital that timing between

the MS and the BSS is maintained, if the information is to be received back at the BSS,within the allotted timeslot of the TDMA frame. Failure to achieve this would result in theinformation in one timeslot corrupting the information in another timeslot, which could bein use by another subscriber.

In a GSM system, the Network can easily calculate the timing advance required to beused by the MS. As the MS continually transmits normal bursts uplink when indedicated mode; regardless of the passage of data, the position of the TSC within thereceived timeslot can be measured. Once the network has calculated the timingadvance for the MS, the value is transmitted downlink to the MS on a SACCH. It takes480ms to transfer the complete timing advance message to the MS.

Within GPRS, the data flow between the MS and the network tends to be of a burstynature, even more so if the MS has been allocated few uplink resources. As the data

flow is not continuous the MS may have moved a considerable distance before it againtransmits uplink. This unknown distance could seriously affect the timing of receiveddata at the BSS if it were not corrected.

To overcome the timing advance problems of GPRS, an alternative method is usedcalled, Continuous Timing Advance.


53/250




131

Timing advance

SYS02_Ch1_02

0 1 2 3 4 5 6 7

Frame 2

0 1 2 3 4 6

Frame 1

5 7

TimingAdvance

3 TS offset

Downlink

BSS MS

Uplink

MSBSS


54/250




132

ContinuousTiming Advance

The initial timing advance is based on the single access burst carrying the PacketChannel Request. The estimated timing advance value is passed to the MS via the

Packet Immediate Assignment. This value is used by the MS until continuous timingadvance update provides a new value.

In continuous timing advance the mobile sends in a special access burst in an idle slot forthe network to derive the timing advance. In the downlink the network sends a timingadvance value via the Packet Associated Control Channel (PACCH) which is transmittedduring the idle timeslots of the 52 multiframe.

Timing Advance Index gives the MS the position to send the access burst. For example,TAI = 1 refers to idle frame 2. The network will then update the MS timing advance in thenext Timing Advance Message and also the next 3 TA messages. The mobile only hasto read the message once.


55/250




133

Continuous timing advance GPRS

sys102_1_12

52multiframe number n:

TA=1TA=0Uplink

Downlink TA message 1 TA message 1

52multiframe number n + 1:

Uplink TA=2 TA=3

B0 B1 B2 0 B3 B4 B5 1 B6 B7 B8 2 B9 B10 B11 3

B0 B1 B2 4 B3 B4 B5 5 B6 B7 B8 6 B9 B10 B11 7

B0 B1 B2 12 B3 B4 B5 13 B6 B7 B8 14 B9 B10 B11 15

B0 B1 B2 16 B3 B4 B5 17 B6 B7 B8 18 B9 B10 B11 19

B0 B1 B2 20 B3 B4 B5 21 B6 B7 B8 22 B9 B10 B11 23

B0 B1 B2 24 B3 B4 B5 25 B6 B7 B8 26 B9 B10 B11 27

B0 B1 B2 8 B3 B4 B5 9 B6 B7 B8 10 B9 B10 B11 11

B0 B1 B2 28 B3 B4 B5 29 B6 B7 B8 30 B9 B10 B11 31



Uplink TA=4 TA=5

Downlink TA message 2 TA=message 2


Uplink TA=6 TA=7



Uplink TA=8 TA=9



Uplink TA=10 TA=11



Uplink TA=12 TA=13



Uplink TA=14 TA=15


B0 B11=Radio blocks idle bursts are numbered from 0 to 31


56/250




134


57/250



i

Chapter 2

PCU Architecture


58/250

Issue 2 Revision 0



ii


59/250

Issue 2 Revision 0



iii

Chapter 2PCU Architecture i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Control Unit (PCU) 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The GPRS solution 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Packet Interface Control Processor 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU System Processor 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet Resource Processor 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initial Configuration 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell INS/OOS 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier State Changes 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier Activation 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Originated Packet Access and Transfer 220. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Terminated Packet Access and Transfer 222. . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Interface 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frame Relay Functional Unit 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gb Functional Unit 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Gb Router (GR) 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Gateway Transmit Manager 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Service Test 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Flow Control Buffer Manager (FBM) 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault Management 232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault Detection and Handling System 232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Audit Process 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Web MMI 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Management 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU Central Authority (pCA) 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


60/250

Issue 2 Revision 0



iv


61/250

Issue 2 Revision 0 Objectives



21

Objectives

On completion of this section the student will be able to:

S Describe the hardware, software and communication protocols used in the BSS

(GPRS) network.

S Describe the main software entities of the PCU and their interaction with the BSSsoftware entities.

S Describe the download and initialisation process.


62/250

Issue 2 Revision 0Packet Control Unit (PCU)



22

Packet Control Unit (PCU)

The new BSS functionality for GPRS mainly resides at the Packet Controller Unit (PCU).The PCU includes the handling of Frame Relay, Network Services Signalling, BSSGPsignalling, routing of signalling messages, Radio Link Control (RLC) and Media Access

Control (MAC) preload and transferring of user data.

User data is routed to the PCU via the CCU uplink from the BTS to the BSC and thenover E1 to the PCU. At the PCU the RLC Blocks are reformulated in Logical Link Control(LLC) frames and forwarded to the SGSN.

BSSGP signalling and NS signalling occur between the PCU and the SGSN using framerelay protocol. There is also signalling between existing functional process at the BSCsuch as the BSP and the PCU via the E1 Span, as well as between the PCU andChannel Coders.


63/250


64/250




24

The GPRSsolution

The GPRS solution is a compact PCI based solution. The CPCIPCU cabinet isconnected to the BSC using E1 spans and the SGSN by E1 using Frame Relay as the

network service.

The Packet Control Unit (PCU) comprises 3 different boards which are defined below:

MPROC

The MPROC is the system slot processor which is responsible for bus arbitration andCPCI clock generation. It contains interface and BSSGP protocol functions and is calledthe PCU System Processor. Only one PCU System Processor (PSP) may be equippedat a PCU at this present time.

DPROC

The DPROC boards are nonsystem slot boards which have two PMC sockets and canhost two different functions. The DPROC can be configured as either a Packet InterfaceControl Processor (PICP) or as a Packet Resource Processor (PRP).

If configured as the PICP the DPROC shall contain up to 2 PMC modules to provide theE1 interfaces. The E1 interface can support the Gb interface or the GPRS Data Stream(GDS) interface, the GPRS Signalling Link (GSL).

If configured as a PRP, the DPROC performs Air Interface scheduling. A singleprocessor can support a pool of 120 radio timeslots of which 30 radio timeslots can beactive at any one time. A PRP may also support a GDS interface. Only one PMC can befitted if the DPROC is configured as a PRP.

Bridge

The Bridge known as the PCI to PCI Bridge (PPB) allows an MPROC to be linked to aseparate bus. The PPB and MPROC are paired boards.


65/250

Issue 2 Revision 0 Packet Control Unit (PCU)



25

PCU Cage

SYS102_Ch2_22

CPCI CHASSIS

ALARM MODULE

DIGITALMODULES

(MPROC andDPROC)

FAN/POWER SUPPLYSLEDS

POWERDISTRIBUTION

MODULE(not visible)

DIGITALMODULES

(transition moduleand HSC bridge)

SYS102_2_2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

P

SP

P

PB

P

SP

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

PRP

orPICP

P

PB


66/250




26

Packet InterfaceControlProcessor

The Packet Interface Control Processor (PICP) is a function residing on a DPROC. A

PICP is made up of the functional units:

A Gb functional unit to terminate the Gb links, to determine whether a Logical LinkControl (LLC) frame is user data, SGSN MS signalling or BSSGP signalling. The LLCframe is then routed to the appropriate board based on LLC frame type.

S Route signalling for paging messages to appropriate cell

S Routing of flushing of queued SDU at appropriate cell

S Routing flow control of downlink traffic

S Queuing MS Packets based on priority queues

GPRS Signalling Link (GSL) LAPD functional unit for synchronization of LAPD link over

GSL between the PCU and the BSC.A TRAU functional unit created for the synchronization and handling of Packet ControlUnit (PCU) frames between the PCU and the BSC.

A PICP Status functional unit for debugging mechanisms, statistics and alarms.

Finally an I/O functional unit is created for routing messages between the functional unitson the PICP and the functional units on the PCU System Processor (PSP).


67/250

Issue 2 Revision 0 Packet Control Unit (PCU)



27

Packet Interface Control Processor

Sys102_2_3

GSL/TRAU

FrameRelay

I/O

PICP

status

(alarms, stats,

debugging)

PICP


68/250




28

PCU SystemProcessor

The PCU System Processor (PSP) resides on the MPROC. As well as control of busarbitration the PSP has the following functional units:

GB Manager

GB manager handling blocking/unblocking and reset.

Gateway Manager (GWM)

The Gateway Manager handles the following function:

1. Code loading of objects during initialisation and reset

2. Board initialisation and startup for software processes

3. Handling database information and changing affected functional units

4. Fault management functions (i.e. fault detection, fau

Documents

Bss Gprs Database-sys102