GPRS Access Network Parameters User Guide: Wireless Service Provider Solutions

Wireless Service Provider Solutions
GPRS Access Network Parameters User Guide

PE/DCL/DD/0136 12.01/EN Preliminary July 2000 41190010136
< 119 >< 136 > : GPRS Access Network Parameters User Guide
Wireless Service Provider Solutions

Document number: PE/DCL/DD/0136 41190010136 Document status: Preliminary Document issue: 12.01/EN Product release: GSM/BSS V12 Date: July 2000
Copyright 19962000 Nortel Matra Cellular and Nortel Networks, All Rights Reserved Printed in France
NORTEL NETWORKS AND NORTEL MATRA CELLULAR CONFIDENTIAL: The information contained in this document is the property of Nortel Networks and/or Nortel Matra Cellular. Except as specifically authorized in writing by Nortel Networks and Nortel Matra Cellular, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation, operation and maintenance purposes only. You may not reproduce, represent, or download through any means, the information contained herein in any way or in any form without prior written consent of Nortel Networks and Nortel Matra Cellular. The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL Globemark, HOW THE WORLD SHARES IDEAS. All other brand and product names are trademarks or registred trademarks of their respective holders.
Nortel Networks Confidential
Publication History
iii
PUBLICATION HISTORY
SYSTEM RELEASE : GSM/BSS V12
July 2000 This version is based on the internal document Access Network Parameters User Guide (version 01.02) completed in July 2000.
iv
Publication History
PAGE INTENTIONALLY LEFT BLANK
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Table of contents
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix
ix ix ix ix ix ix x
1 2
2.1 2.2
Classification of parameters per object . . . . . . . . . . . . . . . . . . . . . . GPRS algorithms and mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 2.2.2 2.2.3 GPRS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 21
21 21 21 23 24 26 26 29 210 213 214 214 217 219 221 223 223 224 230 230 230
2.3
Uplink temporary block Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 2.3.2 2.3.3 2.3.4 Establishment of uplink temporary block flow . . . . . . . . . . . . . . . . . . . . . . Uplink transfer establishment during downlink transfer . . . . . . . . . . . . . . Release of uplink temporary block flow . . . . . . . . . . . . . . . . . . . . . . . . . . . Loss of communication procedures for uplink transfer . . . . . . . . . . . . . .
2.4
Downlink temporary block flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 2.4.2 2.4.3 2.4.4 Establishment of downlink temporary block flow (access without paging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink TBF establishment during uplink transfer . . . . . . . . . . . . . . . . . Release of downlink temporary block flow . . . . . . . . . . . . . . . . . . . . . . . . Loss of communication procedures for downlink transfer . . . . . . . . . . . .
2.5
RLC/MAC features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 2.5.2 Countdown Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sliding Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6
Reselection algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1 2.6.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell reselection in Ready state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Table of contents
2.7
MS power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.1 2.7.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Loop Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
232 232 232 234 236
2.8 2.9
DRXmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13
OMCR algorithms parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call establishment parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Countdown procedure parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio link failure parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell selection and reselection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRX mode parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot sharing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dualband cell parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDMA selection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sliding window parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block allocation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other access network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reserved parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31 36 37 311 313 314 319 322 323 324 326 329 331
4
4.1 4.2 4.3
PCUSN OAM algorithm parameters . . . . . . . . . . . . . . . . . . . . . . . . . .

Network service parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41 45 412
5
5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8
Appendix A: main procedures between the MS and the PCU . .

Proc_1: establishment of uplink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proc_2: establishment of uplink TBF during a downlink transfer . . . . . . . . . . . . . . . Proc_3: release of an uplink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proc_4: release of an uplink TBF with a lost of communication . . . . . . . . . . . . . . . Proc_5: establishment of a downlink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proc_6: failure of downlink TBF establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proc_7: Establishment of downlink TBF during an uplink transfer . . . . . . . . . . . . . . Proc_8: release of a downlink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
51 52 53 54 55 56 57 58
6
6.1
Abreviations and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Abreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
61 63
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
List of figures
vii
Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 210 Figure 211 Figure 212 Figure 213 Figure 214 Figure 215 Figure 216 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35
GPRS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Protocol Stack Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MM State Model of MS ( with SIM card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main procedures to transfer data from MS to PCU. . . . . . . . . . . . . . . . . . . . . . A successful uplink access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishment of an uplink TBF during a downlink TBF. . . . . . . . . . . . . . . . . . . Example of Uplink TBF Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of an Uplink TBF with lost of the communication . . . . . . . . . . . . . . . . Establishment of Downlink TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink TBF Establishment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishment of Downlink TBF during an Uplink transfer . . . . . . . . . . . . . . . . Example of Downlink Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of Sliding Window at a RLC endpoint transmitter . . . . . . . . . . . . . Description of Sliding Window at a RLC endpoint receiver . . . . . . . . . . . . . . . . The occurrence of the CCCH channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of continuous timing advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . maxRach part on the Uplink Establishment Transfer . . . . . . . . . . . . . . . . . . . . Parameters of MS Output Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic example of uplink power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic example of uplink power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Impact of AllocBitmap on TBF Establishment duration . . . . . . . . . . . . . . . . . . .
22 23 24 26 27 29 211 212 215 217 218 221 226 228 235 237 33 315 317 318 327
viii
List of figures
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
About this document
ix
ABOUT THIS DOCUMENT

This user guide describes the Nortel GPRS access network algorithms and parameters from an engineering point of view. This document contains extensive Nortel GPRS parameters setting knowhow. Information coming from experiments, studies, simulations are also related in it. This version is a complement of the Manual < 36 > BSS Parameter User Guide (Release V12).
Applicability
This document applies to Gate 2 soft release of the PCU available for the trials and is compliant with the V12.4 BSS release.
Audience
ABPUG is mainly aimed at all persons needing exhaustive descriptions of the GPRS parameters.
Prerequisite
In order for this document to be fully profitable, readers should have basic knowledges of the GPRS system functioning.
Related Documents
Applicable document PRJ/DOM/CLA/NNNN GPRS Engineering test plan Reference document [R1] [R2] [R3] [R4] PE/DCL/DD/0036 BSS Parameters User Guide PE/DCL/DD/0007 BSS Operating Principles PE/DCL/DD/0124 BSS Dictionary of Parameters PE/DCL/DD/0125 Observation Counter Dictionary
About this document
How this document is organized

The classification of the parameters by object is provided in Chapter 1. Chapter 2 describes the GPRS Nortel access network algorithms and recommends ways to use them efficiently. All the algorithms and mechanisms are compliant with the Gate 2 release. All parameters used in the algorithms are described in Chapter 3. The parameters considered in this document are managed by the OMCR or NMS. They are conveyed in the Air interface, Abis interface, Agprs interface between the MS and the PCU. For each parameter, the following essential fields are described: Class Object Default value Range Value Recommended Value Engineering rules Some engineering rules given in this document will be improved from the field tests and from the GPRS Network Dimensioning Simulator (CT9500) results. In Chapter 4, simulations results are presented as well as impact studies for some parameters. Chapter 5 gives the main exchange between the MS and the PCU. In Chapter 6, the signification of all the abbreviations used in this document and some keydefinitions are explained.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Classification of parameters per object
11
CLASSIFICATION OF PARAMETERS PER OBJECT

Bts:
V12.4 Parameter bsCvMax btsSensitivity radioAllocator gprsCellAllocation gprsPermittedAccess maxRACH panDec panInc panMax nAvgT nAvgW N3103 reserved3 (T3168) reserved4 (T3192) gprsPreemption maxDwAssign gprsPreemptionProtection minNbrGprsTs btsSensitivityInnerZone longTbfLossThroughput longTbfSizeThreshold maxBsTransmitPowerInnerZone maxDnTbfPerTs maxUpTbPerTs drxTimerMax T3172 msCapWeightActive Object bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts bts Class 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 2 X a X X X X X X X X X X X X X X b X X X X X X X X X X X X X X X X X X c 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
12
V12.4 Parameter nbrFreeTchBeforeAnticipation nbrFreeTchToEndAnticipation maxUpTbfP1P2Threshold speechOnHoppingTs maxDnTbfP1P2Threshold nAvgl Object bts bts bts bts bts bts Class 3 3 3 3 3 3 a b c
reserved parameter reserved parameter reserved parameter reserved parameter reserved parameter Not used
Bsc:
V12.4 Parameter bscGprsActivation Object bsc Class 3 a X b X c X
Transceiver:
V12.4 Parameter blockErrorRate codingScheme gprsPriority maxNbrPUDWithoutVChange (N0002Max) N3105Max upAckTime maxSize dLPwrValue maxNbrPDAAssig maxNbrRLCEmptyBlock (N0001Max) dwAckTime Object transceiver transceiver transceiver transceiver transceiver transceiver transceiver transceiver transceiver transceiver transceiver Class 3 2 2 2 2 3 3 3 2 2 3 a X X X X X X b X X X X X X c X X X X X X X reserved parameter Not used Not used Not used
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
13
Channel:
V12.4 Parameter channelType Object channel Class 2 a X b X c X
GprsNsProv:
V12.4 Parameter nsBlockTimer nsBlockRetries nsUnblockRetries nsResetTimer nsResetRetries resumeTimer resumeRetries nsTestTimer nsAliveTimer nsAliveReries Attribute GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv GprsNsProv Criticity None None None None None None None None None None a X X X X X X X X X X b X X X X X X X X X X c X X X X X X X X X X
GprsPcBssgpProv:
V12.4 Parameter bvcBlockRetries bvcUnblockRetries bvcResetReqTimer bvcResetReqRetries suspendTimer suspendRetries raCapabilityUpTimer raCapabilityUpRetries Attribute GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv Criticity None None None None None None None None a X X X X X X X X b X X X X X X X X c X X X X X X X X
14
V12.4 Parameter flowControlMaxRate tsflowCntlBucketSize (tsBmax) tsLeakRate msFlowCntlBucketSize Attribute GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv GprsPcBssgpProv Criticity None None None None a X X X X b X X X X c X X X X
FrAtmDlciSpProv:
V12.4 Parameter maximumFrameSize (n203) rateEnforcement (re) committedInformationRate (cir) committedBurstSize (bc) excessBurstSize (be) measurementInterval (t) accounting (ac) Attribute FrAtmDlciSpProv FrAtmDlciSpProv FrAtmDlciSpProv FrAtmDlciSpProv FrAtmDlciSpProv FrAtmDlciSpProv FrAtmDlciSpProv Criticity None None None None None None None a X X X X X X X b X X X X X X X c X X X X X X X
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
GPRS algorithms and mechanisms
21
GPRS ALGORITHMS AND MECHANISMS

2.1 Introduction
This chapter describes major GPRS algorithms using OMCR algorithm parameters, both on the PCU and the MS side.
2.2
GPRS overview
In order to have a better understanding of all the algorithms and the mechanisms described in this document, an GPRS overview is presented below.
2.2.1
GPRS architecture GPRS is primarily intending to support data applications, which generates bursty traffic (ON/OFF pattern), where packet switched transmission is obviously a more efficient transportation means. The application of the packet oriented transmission scheme on the airlink, results in a better utilization of the scarce radio resources for typical Internet applications. The kind of Traffic has an important impact on the parameter values and on the choice of algorithms. The improvements are gained from the provision of a packet oriented data service for GSM, which allows reduced connection setup times supports existing packet oriented protocols like IP provides and optimizes usage of radio resources. To introduce GPRS in the existing GSM infrastructure, additional network elements are added to the GSM architecture. This structure is depicted in Figure 21.
22
GSM NSS
PSTN/ISDN
BSS HLR GPRS BSS Datafill SGSN PCU
GPRS NSS GGSN
IP. X 25
Figure 21
GPRS Architecture
Since the existing GSM network provides only circuitswitched services, two new network nodes are defined to give support for packet switching: the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN). The SGSN is responsible for the communication between the mobile station (MS) and the GPRS network. It serves the mobile station (MS) and maintains the mobility context. The GGSN provides the interface to external packet data networks or the Internet, but also to GPRS networks of other operators. It routes incoming packets to the appropriate SGSN for a particular mobile station. The GSM Base Station Subsystem (BSS) is used as a shared resource of both circuitswitched and packetswitched network elements to ensure backward compatibility and keep the required investments for the introduction of GPRS at a sustainable level. In order to distinguish GSM and GPRS architecture, the following name are commonly used: Access Network: this is the GPRS BSS, made up the BTS, BSC and PCU elements. Core Network: this is the GPRS NSS, made up the SGSN and GGSN equipments.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
23
2.2.2
GPRS protocol stack
Application part Application IP SNDCP SAPI LLC LLC relay TLLI RLC TFI MAC GSM RF MS Um MAC GSM RF RLC BSSGP Network service L1 bis Gb BSSGP Network service L1 bis SGSN IP L2 L1 Gn IP L2 L1 GGSN Gi LLC UDP/TCP UDP/TCP
Figure 22

Relay IP/ X.25 GTP NSAPI SNDCP GTP TID BSS
Application
GPRS Protocol Stack Description
The SGSN may allocate TMSI for visiting mobile subscriber using GPRS, which are referred to as PacketTMSI or PTMSI. Then each active MS (READY or STANDBY) is identified by the Temporary Link Level Identity, TLLI, inside the SGSN and the access network at the LLC level. LLC shall be independent of the underlying radio interface protocols in order to allow introduction of alternative GPRS radio solutions with minimum changes to the core network. In the SNDCP layer, the NSAPI (Network Service Access Point Identifier), allocated dynamically by the MS, at the PDP Context Activation, identify a specific PDP type which precise the IP version and PDP address pair. This transmission functionality maps networklevel onto the characteristics of the underlying network. The Tunnel Identity, TID, used by the GTP, identifies a PDP context in the IP backbone (between SGSN and GGSN). TID consists of an IMSI and a NSAPI.
24
The TFI (Temporary Flow Identity) is the unique identification of a TBF, used by the MS and the BTS/PCU. Most of access network parameters and algorithms described in this document are related with RLC/MAC. This layer contains two functions: the Radio Link Control function provides a radiosolutiondependent reliable link thanks to the Sliding Window procedure. The Medium access Control function controls the access signaling (request and grant) procedures for the radio channel. It also proposes the Countdown Procedure in order to optimize the resources at the end of a TBF. 2.2.3 Mobility management
IDLE GPRS Attach (t3330) STANDBY Timer expiry READY READY Timer (t3314) expiry STANDBY GPRS Detach (t3322) Cell updates No need of paging
PDU transmission RA updates Paging
Figure 23
MM State Model of MS ( with SIM card)
Before an MS is able to send data to a corresponding host, it has to be attached to an SGSN. Thus, an attachment procedure (GPRS Attach) between the MS and the Network is carried out and a TLLI is assigned to the MS. There are three Mobility Management states related to a GPRS subscriber and each state describes the level of functionality and information allocated. In IDLE state, the MS is not yet attached to the GPRS MM. Therefore a GPRS Attach procedure shall be perform.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
25
In READY state, the MS is attached to GPRS MM and is known with accuracy of a cell. The MS may receive and transmit data for all relevant services type. If the READY Timer (MS or SGSN one) expires, the MS will move to STANDBY state. In STANDBY state, the subscriber is attached to GPRS MM and is known in accuracy of routing area (RA). Therefore the MS performs GPRS Routing Area update and GPRS cell selection and reselection locally. At this point if the subscriber wants to request an Email message or a Web page, a PDP context must be activated before. If the STANDBY Timer (MS or SGSN one) expires in this state, the MM contexts both in MS and in SGSN independently return to IDLE state and may be deleted.
26
2.3
Uplink temporary block Flow

In GPRS, access procedures are not the same in uplink as in downlink. The signaling is asymmetric. Here below are the main steps from the incoming LLC frames to the PDTCH transfer for an uplink TBF.
Sliding window RLC buffer First LLC frame incoming
Call admission
TRANSFER TO PCU
Segmentation
Figure 24
Main procedures to transfer data from MS to PCU.
2.3.1
Establishment of uplink temporary block flow This section describes the allocation for an uplink transfer (no transfer is currently in progress with this MS). Nortel implementation concerns the Fixed Allocation (Bitmap) mechanism for uplink flow establishment (as opposed to the USF mechanism). The uplink transfer establishment is performed in two.
Uplink TBF establishment first phase: on CCCH
On receipt of the first LLC frame in the buffer of the RLC/MAC layer, the MS must send a RACH (Packet Channel Request message) to the BTS. The BTS makes a first treatment to send a Channel Required message to the PCU.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
27
Thus during all this phase, the PCU and the MS communicate through the BTS. That means, that the BTS modifies the message at its level. The messages between the BTS and the PCU are using the Abis GSL interface. See the description in the Figure 25 below.
MAX_RACH filter
MS
BTS
BSC
PCU
RACH (CCCH)
Channel Required IMM. Assign. Command
IMM. Assign. (AGCH) PACKET RESOURCE REQUEST PACKET UPLINK ASSIGNMENT FIRST PDTCH
Start T3168
Allocator filter (TFI & resources limits)
Figure 25
A successful uplink access.
On reception of the Channel Required message the PCU responds according to the OMC parameter maxRach, which is the maximum RACH accepted by the PCU per second. In the Air interface, an Immediate Assignment (AGCH) or an Immediate Assignment Reject is sent. The PCU responds on the same timeslot on which it has received the RACH.
28
If the BTS can not send the Immediate Assignment message (traffic too loaded), the BTS informs the PCU by sending a Delete Indication message. Thus the procedure is discarded at this level. If the Allocator makes the choice to reject the MS request, by sending an immediate Assignment Reject message, the procedure is stopped at this level. In the other case, after this point, the mobile station use PDCH channels to talk with the PCU. Note that the Channel Required message provides the Timing Advance (Access delay field), but this value is valid only during a timer which is set to 6 seconds. Thus before the expiration of this timer, the PCU must send the Packet Uplink Assignment message. If this timer elapses, the procedure is cancelled (see Paragraph 2.9 Timming Advance).
Uplink TBF establishment second phase: on PDCH
By receiving an Immediate Assignment, RLC/MAC knows the type of TDMA (N TDMA) attributed, the frame number of the allocated block (TBFSTARTINGTIME) from which the MS is allowed to transmit the Packet Resource Request. Thus, it indicates the RLCMODE requested (RLC Acknowledged (0) or RLC unacknowledged (1)), the RLCOCTETCOUNT (used by the allocator to compute the number of blocks allocated to closeended TBF according to the BLER and the coding scheme; else indicates 0), its Multislot Class capability, etc Then the MS starts timer T3168 to control the time to wait for the Packet Uplink Assignment message. If T3168 expires, the packet access procedure is reinitiated. If the PCU does not receive the Packet Resource Request in the allocated single radio block (PACCH), the procedure is canceled in the PCU side and the packet access procedure is reinitiated after T3168 expires. On receipt of the Packet Resource Request, the allocator knows the MS capabilities and the TBF type (openended if RLCOCTETCOUNT= 0; else closeended). For a closeended TBF, the PCU knows the number of user data octets that has to be transferred and can give only what is needed. For an openended, the PCU does not know the number of user data octets that has to be transferred and the MS has to request resources in each bitmap. Therefore, the allocator can decide if it is able to allocate resources or not, by sending a Packet Uplink Assignment or a Packet Access Reject. The Packet Uplink Assignment message is sent by the PCU to the mobile station to assign uplink resources (bitmap). The TFI is provided at this level to the MS. The communication is established and the MS goes in packet transfer mode.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
29
2.3.2
Uplink transfer establishment during downlink transfer The mobile station may request the establishment of an uplink transfer during a downlink TBF. This consists in including a Channel Request Information Element (containing fields RLCMODE, RLCOCTETCOUNT and a flag to indicate that these fields are valid) in the Packet Downlink Ack/Nack message (Initiation is triggered by a request from upper layers to transfer a LLC PDU) (see Figure 26).
MS
PCU
PACKET DOWNLINK ACK/NACK DOWNLINK DATA PACKET UPLINK ASSIGNMENT(S/P=1) PACKET CONTROL ACKNOWLEDGEMENT DOWNLINK DATA DOWNLINK DATA UPLINK DATA Allocator filter (TFI & resources limits)
TBF starting time for the uplick TBF
Figure 26
Establishment of an uplink TBF during a downlink TBF.
When the MS requests an uplink TBF establishment, the PCU can be in the release procedure. Thus, there are two cases: If the PCU has already sent the data block with the FBI set to 1, in that case it is like an half duplex uplink TBF establishment: the uplink TBF establishment request is resent after the release of the Downlink TBF. It means that when the LLC frame will trigger at the MS side an Uplink request, the MS will keep the request and wont send the PACKET RESOURCE REQUEST at this present time but will wait for the end of the Downlink Transfer to send the Uplink Channel Request.
210
If the PCU has not already sent the data block with the FBI set to 1, the uplink TBF establishment request is taken into account (Full Duplex transfer). If it is needed, the sending of this block is delayed until the PACKET UPLINK ASSIGNMENT message is correctly acknowledged. On receipt of a Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message, the PCU may assign radio resources to the mobile station on one PDCH by transmitting a PACKET UPLINK ASSIGNMENT message on the PACCH, or may reject the request by sending a PACKET ACCESS REJECT message on the PACCH. The PCU sends the PACKET UPLINK ASSIGNMENT message with all information for establishing the uplink TBF. The MS acknowledges this message by sending a PACKET CONTROL ACKNOWLEDGEMENT. If the message is not acknowledged by the MS, the PCU sends again the message until it will be acknowledged or a loss of communication is detected by the downlink TBF. If the loss of communication is detected, an error message is sent to the SGSN and the procedure is canceled at this point. If the MS acknowledges the message, the TBF uplink is established. 2.3.3 Release of uplink temporary block flow There are two kinds of release: normal or abnormal. A normal release of an uplink TBF by the PCU occurs in the following cases: The PCU sends an allocation to the MS with the field FINAL_ALLOCATION set to 1. The PCU sends a Packet Access Reject to the MS to indicate it has rejected the MS request. The PCU initiates a release by sending a Packet TBF Release to the MS. A normal release of an uplink TBF by the MS occurs when it has no more RLC/MAC blocks to transfer so it initiates a countdown procedure. The MS must begin the countdown procedure in order to end it within the current allocation. An abnormal release of an uplink TBF by the PCU occurs in the following cases: Some PDCHs allocated to a TBF are no more available. This may happen when the BSC informs the PCU that some GPRS resources are no more available. The PCU has lost the communication with the MS. In the case of a normal release of an uplink TBF by the MS, the RLC/MAC initiates release of the uplink TBF by beginning the countdown process when the mobile station has sent the RLC data block with CV = 0. The MS starts the Timer T3182.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
211
If the timer T3182 expires before the reception of the Packet Uplink Ack/Nack message with Final Ack Indicator bit (FAI) set to 1, then the TBF is released. If the network has not received all RLC data blocks when it detects the end of the TBF, it will send the Packet Uplink Ack/Nack message to the mobile station. Besides, if necessary, the PCU allocates sufficient uplink resources for the mobile station to retransmit the required RLC data blocks. If a new bitmap is needed, the MAC PCU layer provides it to the MS to end the TBF. For any TBF, this bitmap is provided without request from the MS (see Figure 27). If the network has received all RLC data blocks when it detects the end of the TBF (i.e. When CV = 0 and there are no elements in the V(B) array set to the value Nacked), it will send the Packet Uplink Ack/Nack message with the Final Ack Indicator bit and the FINAL_ALLOCATION set to 1 and clears counter N3103 (OAM parameter).
Start T3182 MS PCU
PDTCH (CV=0) PACKET UPLINK Ack/Nack PDTCH PDTCH PACKET UPLINK Ack/Nack (Final Ack Indicator =1) PACKET CONTROL ACKNOWLEDGEMENT
TBF release
TBF release
Figure 27
Example of Uplink TBF Release
212
On reception of the Packet Uplink Ack/Nack message with the Final Ack Indicator bit set to 1, the MS must transmit the Packet Control Acknowledgement message and releases the TBF. If the network does not receive the Packet Control Acknowledgement message in the radio block expected, it increments counter N3103 and repeats the sending of the Packet Uplink Ack/Nack message with the Final Ack Indicator bit set to 1, including a valid RRBP field. This procedure is repeated until the message is acknowledged or the counter N3103 exceeds N3103Max. The MAC starts timer T3169 when counter N3103 exceeds its limit. The PCU may reuse the TFI resources (see Figure 28) when timer T3169 expires.
Start T3182 MS PCU
PDTCH (CV=0) PACKET Uplink Ack/Nack (Final Ack Indicator =1) .......... PACKET Uplink Ack/Nack (Final Ack Indicator =1) N3103Max
Not received by the MS
TBF release
TBF release
Start T3169
Figure 28
Release of an Uplink TBF with lost of the communication
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
213
2.3.4
2.3.4.1
Loss of communication procedures for uplink transfer

In the PCU
The loss of communication is detected by two ways: When the RLC layer detects NN0001Max consecutive erroneous blocks for a TBF, it informs the MAC layer, which activates the RRBP field in the next Packet Uplink Ack/Nack message. It means that the PCU expects for a Packet Control Acknowledgement. If this message is acknowledged, the MAC informs the RLC of the reestablishment of the communication, else the procedure is the same as for a MAC detection of the loss of communication. When the MAC sends a message with the RRBP field activated (it requests an acknowledgement with a Packet Control Acknowledgement), and there is no acknowledgement of this message. After this point if the RLC detects the loss of communication, this detection is not taken into account by the MAC layer. When the first control message is not acknowledged, the MAC starts the timer NT0001 and resends the message with a RRBP field valid. If the MAC receives an acknowledgement of one control message the procedure is stopped at this level. If one message is not acknowledged the message is resent with a RRBP field valid. If the timer NT0001 elapses the TBF is released.
2.3.4.2 In the Mobile Station
The loss of communication is detected at the MS side by the timer T3184. When the MS receives a Packet Uplink Ack/Nack from the PCU, it stops T3184 and it starts again. If T3184 elapses, i.e. a Packet Uplink Ack/Nack has not been received in time from PCU, the MS shall try to reestablish the TBF by reinitiating a random access procedure. If the procedure succeeds then the RLC/MAC layer shall retransmit the current LLC frame.
214
2.4
2.4.1
Downlink temporary block flow

Establishment of downlink temporary block flow (access without paging) This chapter describes the allocation for a downlink transfer when the MS is in the Ready state (GPRS Mobility Management) and in Packet Idle mode (there is no current TBF in progress with this MS). From the allocator point of view, the establishment of a downlink transfer with an MS in: The STANDBY state is similar to the establishment of an uplink TBF to carry the paging response, followed by the establishment of a downlink transfer towards an MS in the STANDBY state. The Ready state and Packet Transfer mode is a downlink TBF establishment during uplink transfer. As for uplink transfer establishment, the downlink transfer establishment can be seen as a two phases access.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
215
Start NT1002
MS
BTS
BSC
PCU
IMM. Assignment
IMM. Assign. Command
BSSGPDLUnitData
PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACKNOWLEDGEMENT (Over 4 bursts ) PACKET TIMING ADVANCE FIRST PDTCH
Figure 29
2.4.1.1
Establishment of Downlink TBF

First phase on CCCH (downlink TBF)
The downlink establishment procedure using CCCH is applicable when the MS is in packet idle mode and when there is no PCCCH in the cell. On receipt of a downlink DLUNITDATA coming from the SGSN, the MAC layer verifies if there is no existing transfer for this mobile and asks the Allocator for resources. If no resources are available, the PCU sends an error message to the SGSN. If resources are available for this new downlink TBF, the PCU sends an Immediate Assignment message on the Agprs GSL interface to the BTS. Then the BTS sends an Immediate Assignment message to the MS. This is the only message using CCCH in this procedure. The Allocator can allocate only one PDCH channel for downlink transfer establishment. This PDCH is used in the second phase to allocate more resources to the MS according to its multislot class capability and the radio resources available.
216
When the MAC layer sends the Immediate Assignment Command message, it starts the timer NT1002. If the BTS can not send the Immediate Assignment message (traffic too loaded), the BTS informs the PCU by a Delete Indication message. Thus the PCU resets the timer NT1002 and sends an other time the Immediate Assignment message. Compare to the uplink TBF establishment, the timing advance is not known by the PCU on the sending of the Immediate Assignment message. So, in order to provide the MS with a valid timing advance, the PCU set a polling bit in the Immediate Assignment message in order to use the four access bursts mechanism. Starting time is defined neither during the first phase nor during the second phase of the downlink TBF establishment. But for the reservation of the downlink blocks in the routing table, the allocator must take into account the transmission delay and the MS reaction time.
2.4.1.2 Second phase on PDCH (downlink TBF)
Upon receipt of the Immediate Assignment message, the MS must start to monitor the PDCH specified in the message. In the second phase, on this PDCH, the PCU sends a Packet Downlink Assignment message (when the timer NT1002 elapses), with RRBP field activated, to the MS to assign downlink resources. Upon receipt of the Packet Downlink Assignment message, the MS (RLC/MAC layer) must respond by the Packet Control Ack message on four access bursts, with the RLCMODE requested (see Figure 29). This message is used by the BTS to compute the timing advance. The TFI provided in this message may be different from the TFI given in the Immediate Assignment message because the two messages can be send on different TDMA. If the Packet Control Acknowledgement message is not received in the block expected, the MAC layer repeats the sending of the Packet Downlink Assignment message, with the RRBP field activated. The case of a failure is described in the Figure 210.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
217
MS
BTS
BSC
PCU
Start NT1002
IMM. Assignment
IMM. Assignment
PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACK. 500 ms PACKET DOWNLINK ASSIGNMENT NBMAXPDASSIGN. PACKET CONTROL ACK.
500 ms PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACK. TBF release Start NT1001
Figure 210
Downlink TBF Establishment failure
2.4.2
2.4.2.1
Downlink TBF establishment during uplink transfer

Description
The establishment of a downlink TBF is triggered by the SGSN. When the decision to establish a downlink TBF is taken there are two possible cases: The current uplink resource allocation allows the MS to establish a downlink TBF. Thus the PCU sends directly a Packet Downlink Assignment message on the PACCH to the MS to provide the downlink resources. This message is acknowledged by sending a Packet Control Acknowledgement.
218
The current uplink resource allocation, according to the MS capability, does not allow the MS to establish a downlink TBF. Thus the PCU sends a Packet Uplink Assignment message to provide a new uplink resource allocation to the MS that allows establishing a downlink TBF. Then the PCU sends a Packet downlink Assignment message to the MS to provide the downlink resources. The two messages are acknowledged by sending a Packet Control Acknowledgement (see Figure 211).
MS
PCU
PDTCH PACKET UPLINK ASSIGNMENT (bitmap i+1) PDTCH PDTCH PACKET CONTROL ACKNOWLEDGEMENT Uplink Bitmap i PDTCH PACKET DOWNLINK ASSIGNMENT PDTCH PACKET CONTROL ACKNOWLEDGEMENT PDTCH PDTCH Uplink Bitmap i+1 PDTCH PDTCH Downlink TBF start
Figure 211
Establishment of Downlink TBF during an Uplink transfer
In these two cases, before beginning the downlink TBF, the MS must finish its current uplink resource allocation (it means its current bitmap). The PCU must take into account this constraint for the TBF starting time and waits to the end of the current uplink resource allocation before to send data to the MS.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
219
When the PCU receives the TBF downlink establishment request from the SGSN, the TBF can be in the release procedure. Thus there are two cases: If the PCU has already sent the last Packet Uplink Ack/Nack message (message with the Final Ack Indicator bit and the FINAL_ALLOCATION bit set to 1) of the TBF, in that case it is like an half duplex downlink TBF establishment. If the PCU has not already sent the last Packet Uplink Ack/Nack message (message with the Final Ack Indicator bit and the FINAL_ALLOCATION bit set to 1), the TBF downlink establishment request is taken into account (Full Duplex transfer) and the sending of this message is delayed until the acknowledgement of the Packet Downlink Assignment message is received correctly.
2.4.2.2 Failure case
If the Packet Downlink Assignment message is not acknowledged, the MAC starts the timer NT0001 and the message is repeated. Each time one message is not acknowledged the message is repeated. If a message is acknowledged, then the timer NT0001 is stopped and the procedure continues normally. If the timer NT0001 elapses, the TBF uplink is released and the SGSN is informed of the failure. If the Packet Downlink Assignment message is not acknowledged, the MAC starts the timer NT0001 and the message is repeated. Each time one Packet Downlink Assignment is not acknowledged the message is repeated. If a message is acknowledged, then the timer NT0001 is stopped and the procedure continue normally. If the timer NT0001 elapses, the TBF uplink is released and the SGSN is informed of the failure. 2.4.3 Release of downlink temporary block flow There are two kinds of release: normal or abnormal. A normal release of a downlink TBF by the PCU occurs in the following case: The PCU has no more LLCPDU to be transferred. In this case, it sends a downlink RLC block with the Final Block Indicator (FBI) set to 1, with a valid RRBP to ask for a Packet Downlink Ack/Nack, then it starts the timer T3191.
220
Upon receipt of the last downlink RLC block, the MS must send a Packet Downlink Ack/Nack with FAI=1 and start timer T3192. When T3192 expires, the MS shall release the TBF. When the PCU receives a Packet Downlink Ack/Nack with FAI=1, it starts T3193. When T3193 expires, the network shall release the TBF. An abnormal release of a downlink TBF by the PCU occurs in the following cases: Some PDCHs allocated to a TBF are no more available. This may happen when the BSC informs the PCU that some GPRS resources are no more available. The PCU has lost the communication with the MS. In the case of a normal release of a downlink TBF by the PCU, the PCU initiates release of a downlink TBF by sending an RLC data block with the Final Block Indicator (FBI) set to the value 1 and with a valid RRBP field. The RLC data block sent must have the highest BSN of the downlink TBF. The PCU may retransmit the RLC data block with the FBI bit set to the value 1. Then the PCU starts Timer T3191. If T3191 expires, the TBF is released. If the mobile receives an RLC data block with the FBI bit set the value 1 and with a valid RRBP field, the mobile station will transmit a Packet Downlink Ack/Nack message in the specified uplink block. The mobile station will continue to monitor all assigned PDCHs. If the network receives a Packet Downlink Ack/Nack message, and if retransmissions are required, then the network retransmits necessary RLC data blocks. If the mobile station has received all previous RLC data blocks, the mobile station shall send the Packet Downlink Ack/Nack message with the Final Ack Indicator (FAI) bit set to 1 and shall start timer T3192. The PCU shall stop T3191 and shall start T3193. The network releases the TBF (see Figure 212) when T3193 expires. The mobile station will stop monitoring its assigned downlink PDCH when T3192 expires. If the PCU has new data to transmit to the MS when receiving a Packet Downlink Ack/Nack message with FAI=1, the PCU must be able to establish a new downlink TBF through the assigned PDCH, so the allocator must be able to allocate blocks on this PDCH until T3192 expires. Sending a Packet Downlink Assignment or a Packet Timeslot Reconfigure on PACCH (see [R8]) does this establishment.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
221
MS
PCU
Start T3191
PDTCH (FBI=1) PACKET DOWNLINK ACK/NACK (FAI=0) PDTCH (FBI=0) PDTCH (FBI=0) PDTCH (FBI=0) PACKET DOWNLINK ACK/NACK (FAI=1) Stop T3191
Start T3193 TBF release Start T3192 TBF release
Figure 212
Example of Downlink Release
2.4.4
2.4.4.1
Loss of communication procedures for downlink transfer

In the PCU
The PCU polls the mobile station by setting the S/P bit and providing a valid RRBP in RLC data blocks. After sending a valid RRBP in a downlink RLC data block, if no RLC/MAC control message is received in the specified block the counter N3105 is incremented. If a valid RLC/MAC control message is received the counter N3105 is reset. If the counter N3105 reaches N3105max, the timer T3195 is started. If the timer T3195 expires the TFI resources are released.
222
2.4.4.2
In the MS
At the MS side, timer T3190 is used in order to detect a loss of communication in downlink transfer. T3190 is started each time the MS receives downlink resources (by Packet Downlink Assign or Packet Control Acknowledgement). It is reset each time a RLC/MAC data block is received or when new downlink resources are received. When T3190 elapses, the MS shall consider that the communication is lost.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
223
2.5
2.5.1
2.5.1.1
RLC/MAC features
Countdown Procedure
Algorithms
The mobile station will send the Countdown Value (CV) in each uplink RLC data block to indicate to the network the absolute BSN (BSN) of the last RLC data block that will be sent in the uplink TBF. Consider this integer: x = round [(TBC BSN 1) / NTS] (The function round rounds upward to the nearest integer.) Then: CV = {x, if x Where: TBC = total number of RLC data blocks that will be transmitted in the TBF, BSN = absolute block sequence number of the RLC data block, with range from 0 to (TBC 1), NTS = number of timeslots assigned to the uplink TBF, with range 1 to 8, BS_CV_MAX is a parameter broadcast in the system information.
2.5.1.2 Countdown Procedure objective

BS_CV_MAX 15, otherwise}
This procedure is managed at the MS side and is only used for openended TBF. As uplink resources are allocated by allocation of bitmaps (one bitmap may contains 24 blocks), to avoid wasting resources at the end of an uplink TBF when just few blocks remain to be transmitted, a threshold is computed that permit to count down the remaining blocks. As soon as in the RLC buffer, the number of RLC blocks is below the threshold NTS*bsCvMax, RLC/MAC can start the Countdown Procedure by sending CV = x to the allocator. Therefore, the allocator can optimize its resources by calculating the number of blocks requested (it takes into account the BLER measurements in the cell) for ending the transfer. BsCvMax is the parameter, which determines when the procedure can start (see Paragraph 3.2 Coutndown procedure parameters).
224
2.5.1.3
Mechanism
Once the mobile station transmits a value other than 15, the mobile will not add any new RLC data blocks to the TBF. Any data that arrives after the beginning of the countdown procedure will be sent in a future TBF. At the beginning of each allocation of an openended TBF, the MS shall either request to continue the TBF by transmitting a Packet Resource Request, or the MS shall begin the Countdown Procedure so that it ends within the current allocation. During the Countdown Procedure in RLC acknowledged mode, if reemission of RLC blocks is needed, the MS may obtain another bitmap to end the TBF. In this case, the PCU provides a new allocation without MS request. The MAC provides this new allocation when the RLC detects this case. 2.5.2
2.5.2.1
Sliding Window
Sliding window objective
The Sliding Window procedure makes the RLC/MAC layer reliable. Thus in RLC acknowledged mode of operation, it defines the Backward Error Correction enabling the selective retransmission of unsuccessfully delivered RLC/MAC blocks. Note those three parameters: upAckTime, maxNbrPUDWithoutVChange and T3198, are related to this procedure. These parameters have important impacts on GPRS network performances and so their value should be set very carefully (see Paragraph 3.10 Sliding window parameters).
2.5.2.2 Transmitter Definitions
Firstly, here below is presented a short definition of important characteristics for the RLC endpoint transmitter in the Sliding Window procedure: V(B): is an array of 128 elements indicating the acknowledgement status of k = 64 previous RLC data blocks. V(A): contains the BSN value of the oldest RLC data block that has not been positively acknowledged. V(S): denotes the sequence number of the next RLC data block to be transmitted. BSN: is set equal to the value of the send state variable V(S) and is 7 bits in length. NN0002: is a PCU Timer. It is a counter incremented each time V(A) does not change on receipt of Packet Ack/Nack message. The counter NN0002 is reset when V(A) is changed. When the counter NN0002 reaches its maximum value maxNbrPUDWithoutVChange , the TBF is aborted.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
225
T3198: is a mobile Timer. The MS shall set an instance of T3198 for each RLC data block sent. It shall have the expiry value set to bsCvMax block periods. PENDING_ACK: as each RLC data block transmitted, the corresponding element in V(B) is set to the value PENDING_ACK before the reception of the Packet Ack/Nack message. ACK: is the value of the elements acknowledged by the Packet Ack/Nack message. NACKED: is the value of the elements not acknowledged by the Packet Ack/Nack message. INVALID: when an element in the V(B) array falls outside of the active transmit window, i.e. [V(A) 3 BSN 3 V(S)], the element will be set to the value INVALID. STALL CONDITION: the mobile station will indicate a transmit window stall condition when [V(S) = V(A) + k]. Upon detecting a transmit window stall condition, the mobile station will set the Stall indicator (SI) bit in all uplink RLC data blocks until the stall condition ceases to exist.
Description
In RLC acknowledged mode, RLC/MAC layer considered as a RLC endpoint transmitter has an associated acknowledge state array V(B) as it is described in the Figure 213.
226
State array V(B)
PDTCH (BSN = V(A))
V (S)
ACK ACK
2 State variable updating
PENDING_ACK NACKED PENDING_ACK ACK k NACKED PENDING_ACK V (A) NACKED ACK ACK ACK 1 PACKET ACK/NACK
Figure 213
Description of Sliding Window at a RLC endpoint transmitter
The values of V(B) are updated from the values received from its peer in the received block bitmap (RBB) of the Packet Ack/Nack message (see Figure 214). On receipt of the Packet Ack/Nack message, the transmitter will first send the oldest RLC data block indexed relative to V(A). Then: If [V(S) < V(A) + k] modulo 128 and RLC data blocks have a corresponding element in V(B) with the value NACKED, the oldest block with a corresponding element set to NACKED will be transmitted and the corresponding element in V(B) will be set to the value PENDING_ACK.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
227
If [V(S) < V (A) + k] modulo 128 and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with BSN indexed relative to V(S) will be transmitted and the corresponding element in V(B) will be set to the value PENDING_ACK. If [V(S) = V(A) + k] modulo 128, the sending side will transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING_ACK, then the next oldest RLC data block, etc. If all RLC data block whose corresponding element in V(B) has the value PENDING_ACK has been transmitted once, the process will be repeated beginning with the oldest RLC data block. The process of transmitting the oldest RLC data blocks whose value in V(B) has the value PENDING_ACK will continue until all RLC data blocks are acknowledged (or the counter NN0002 reaches maxNbrPUDWithoutVChange at the PCU side). If there are no further RLC data blocks available for transmission, the sending side will transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING_ACK, then the next oldest block. If all RLC data blocks whose corresponding element in V(B) has the value PENDING_ACK have been transmitted once, the process will be repeated beginning with the oldest RLC data block. The process is repeated until all RLC data blocks are acknowledged (or the counter NN0002 reaches maxNbrPUDWithoutVChange at the PCU side).
2.5.2.3 Receiver Definitions
Firstly, here below is presented a short definition of important characteristics for the RLC endpoint receiver in the Sliding Window procedure: V(N): is an array of 128 elements indicating the receive status of k= 64 previous RLC data blocks. V(R): denotes the BSN of the next RLC data block expected to be received. V(Q): denotes the sequence number of the oldest RLC data block not well received. BSN: is set equal to the value of the send state variable V(S) and is 7 bits in length. NN0002: is a PCU Timer. It is a counter incremented each time V(Q) does not change on receipt of Packet Ack/Nack. The counter NN0002 is reset when V(Q) is changed. When the counter NN0002 reaches its maximum value NN0002max, the TBF is aborted. T3198: is a mobile Timer. The MS shall set an instance of T3198 for each RLC data block sent. It shall have the expiry value set to BS_CV_MAX block periods.
228
RECEIVED: is the value of the corresponding element in V(N) when a RLC data block is received with BSN such that [V(Q) BSN V(R)] modulo 128. SSN: is assigned the value of the receive state variable V(R) at the RLC receiver. INVALID: when an element in the array V(N) falls outside of the active receive window, i.e. [V(Q) BSN V(N)], the element will be set to the value INVALID.
Description
In RLC acknowledged mode, RLC/MAC layer considered as a RLC endpoint receiver has an associated receive state array V(N) as it is described in the Figure 214.
V (R) 1 State variable updating PACKET ACK/NACK
RECEIVED 2 RECEIVED RECEIVED V (Q) RECEIVED RECEIVED RECEIVED RECEIVED RECEIVED RECEIVED 3 PDTCH
Figure 214
Description of Sliding Window at a RLC endpoint receiver
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
229
When an RLC data block is received with BSN such that [V(Q) BSN < V(R)] modulo 128, the corresponding element in V(N) is set to the value RECEIVED. The Packet Ack/Nack message sent by the RLC endpoint receiver contains a starting sequence number (SSN) and a received block bitmap (RBB). At the RLC transmitter, for each bit in the RBB whose corresponding BSN value is within transmit window, if the bit contains the value 1, the corresponding element in V(B) indexed relative to SSN will be set to the value ACKED. If the bit contains the value 0 and if at the MS side the instance of timer T3198 corresponding to BSN is expired, the element in V(B) will be set to the value NACKED. If the bit contains the value 0 (and the instance of timer T3198 is not expired at the MS side), the element in V(B) will not be modified. A bit within the RBB whose corresponding BSN is not within the transmit window, will be ignored. The RBB is assigned the k elements whose indices in the receive state array V(N) at the receiver range from [V(R) 1] modulo 128 to [V(R) k] modulo 128. For each bit in the bitmap, the bit is assigned the value 1 if the corresponding element in V(N) indexed to SSN has the value RECEIVED. The bit is assigned the value 0 if the element in V(N) has the value INVALID. When sending a Packet Ack/Nack message initiated by the RLC entity, if V(Q) has not been changed at the PCU side since the previous Packet Ack/Nack message was sent, then the counter NN0002 is incremented. If V(Q) has been changed since the previous Packet Ack/Nack message was sent the counter NN0002 is reset. When NN0002 reaches NN0002max at the PCU side, the PCU aborts the TBF.
230
2.6
Reselection algorithms
The mobility within GPRS is managed at two different levels: At network level, it is managed by the SGSN that determines the location of the mobile. At air interface level, the MS that makes the decision to move between cells.
2.6.1
Overview Unlike GSM, there is no Handover procedure defined for GPRS. The transition between cells is performed through Cell Reselection procedure. Four modes are defined in GSM specifications: NC0: Normal MS control. The MS shall perform autonomous cell reselection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network. The MS shall perform autonomous cell reselection. NC2: Network control. The MS shall send measurement reports to the network. The MS shall not perform autonomous cell reselection. RESET: the MS shall return to the broadcast parameters. Only sent on PCCCH or PACCH. The parameter values NC1 and NC2 only apply in Ready State. In Standby State, the MS shall always use normal MS control.
2.6.2
Cell reselection in Ready state Cell reselection is the same than for GSM using C2, with the same list of neighbor cells and the same radio parameters. At least every 5 seconds, the MS shall calculate the value of C1 and C2 for the serving cell and recalculate C1 and C2 values for non serving cells (if necessary). The MS shall then check whether: The path loss criterion (C1) for current serving cell falls below zero for a period of 5 seconds. This indicates that the path loss to the cell has become too high. The calculated value of C2 for a nonserving suitable cell exceeds the value of C2 for the serving cell for a period of 5 seconds, except:
In the case of the new cell being in a different location area, or for a GPRS MS
in a different routing area, or always for a GPRS MS in Ready State, the C2 value for the new cell shall exceed the C2 value of the serving cell by at least CELL_RESELECT_HYSTERESIS (dB) (defined by the BCCH data from the current serving cell) for a period of 5 seconds.
In case of a cell reselection occurring within the previous 15 seconds, the C2
value for the new cell shall exceed the C2 value of the serving cell by at least 5 dB for a period of 5 seconds.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
231
This indicates that it is a better cell. In order to minimize the impact of the introduction of the GPRS in an existing GSM network, it is recommended not to modify the current value of CellReselectHysteresis used for voice (recommended value for urban area is 6 dB). A high value would keep the link for a long time hence some communications would have a high BLER due to an important load of the cell. The throughput would then decrease because of the retransmission at RLC/MAC layer. On the other hand a low value would ease the Cell Reselection pingpong in data mode. When a reselection occurs, the MS terminates its TBF in the previous cell, executes a cell reselection, and establishes a new TBF in the new cell. Note that for the moment a cell reselection of a GSM cell for a GPRS MS is possible. So, in this case, the loss of buffered data is unavoidable, as the establishment of a new TBF in the new cell is impossible.
232
2.7
2.7.1
MS power control
Overview Power control, only done in uplink, is important for spectrum efficiency as well as for power consumption in a cellular system. For good spectrum efficiency, quality based power control is required. Power control for a packet oriented is more complicated than for a circuit switched connection, since there is no continuous connection but an ON/OFF data traffic, where ON periods can be very short. As for GSM, Power Control algorithm is implemented in the BSS with two main goals: Reduce the overall interference level. Reduce the battery consumption at the mobile side. The RF output power P to be used by the MS on each individual uplink PDCH is: P = min {0 CH * (C + 48), PMAX} Where: CH is an MS and channel specific power control parameter, sent to the MS in an RLC/MAC control message. 0 = 39 dBm for GSM900 = 36 dBm for DCS1800 is a system parameter, broadcast on PBCCH or optionally sent to MS in an RLC/MAC control message. C is the normalized received signal level at the MS. It is mean of the received signal level of the four normal bursts that compose the block. PMAX is the maximum allowed output power in the cell, represented by the following parameters: GPRS_MS_TXPWR_MAX_CCH if PBCCH exists, MS_TXPWR_MAX_CCH otherwise. The and CH parameters are provided to the PCU by the BSC in the power control parameters of the TDMA Config Request message of the Agprs OAM interface. When the MS receives new CH or values, the MS shall use the new value to update P two radio blocks after the end of the last timeslot of the message block containing the new value.
2.7.2
Open Loop Control A pure open loop is achieved by setting = 1 and keeping CH constant in the cell. We take the BTS power reduction Pb, due to power control, equal to 0 since there is no downlink power control in Gate 2.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
233
The output power will be: P = min (0 CH C 48, PMAX) The value CH is calculated by the PCU to achieve an uplink sensitivity with a fixed downlink transmit power. The computation is done as follows to give a target value for the received signal, SSb = BtsSensitivity, at the BTS. The received signal strength at the MS: C = SSm = PBTS Pb L. Where: PBTS = BTS maximum output power on PDTCHs (as BTS power control is not implemented in V12.4, PBTS = bsTxPwrMax on BCCH). L = Path Loss. Pb = 0. Due to Pb = 0, the C value (normalized signal strength) is: C = PBTS L. The MS output power is: P = 0 CH C 48 = 0 CH PBTS + L 48. The received signal strength at the BTS is: SSb = P L = 0 CH PBTS 48. So, the constant value of CH is: CH = 0 PBTS SSb 48 Which can be written: CH = 0 bsTxPowerMax BtsSensitivity 48 The CH parameter is constant on a cell basis but computed by the PCU through the BSC parameter BtsSensitivity (OAM Agprs interface) which is the minimum power needed for BTS decoding.
234
2.8
DRXmode
DRX (sleep mode) will be supported when the MS is in Packet Idle Mode. DRX is independent from MM states Ready and Standby (see [R13]). In DRX mode, during Packet Idle Mode, the MS shall only listen the paging blocks belonging to the paging group (BS_PA_MFRMS). During Transfer nonDRX mode period, the MS shall listen to all the CCCH channels (see Figure 215). Thus, the establishment of a downlink TBF duration will decrease if the downlink request is sent during the Transfer nonDRX mode period. In each cell, the network defines an upper limit for the duration of the period in nonDRX mode to be applied by the MS following the transition from the Packet Transfer Mode to the Packet Idle Mode (see [R8]). There are three cases when the MS shall enter nonDRX mode: Upon transition from the Packet Transfer Mode to the Packet Idle Mode, an MS shall enter the Transfer nonDRX mode period. The duration of this period is determined by the minimum value of the NON_DRX_TIMER parameter, requested in the GPRS attach procedure, and the drxTimerMax parameter, broadcast in the cell. When the mobile station receives a new value of the DRX_TIMER_MAX parameter, the mobile station is not required to consider the new value until the next time it enters Packet Idle Mode. An MS, operating in NC2 mode, shall enter the NC2 nonDRX mode period when it sends a NC measurement report. The duration of this period is defined by the NC_NON_DRX_PERIOD parameter. When initiating the GMM procedures for GPRS attach and routing area update procedures, the MS shall enter the GMM nonDRX mode period. This period ends when either the messages GPRS Attach Accept, GPRS Attach Reject, Routing Area Update Accept or Routing Area Update Reject is received by the mobile station. This period also ends after timeout when waiting for any of these messages. Otherwise, the MS may be in DRX mode. To sumup, MS remains in Transfer nonDRX mode period after any TBF is ended, during: min (NON_DRX_TIMER, drxTimerMax [of the serving cell] The MS in DRX mode has a DRX period, which is defined by the GSM parameters: BS_PA_MFRMS. Thus the paging group definition based on BS_PA_MFRMS shall be used.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
235
The DRX period defined by BS_PA_MFRMS has an important impact on the downlink TBF establishment. The Gate 2 release of Nortels GPRS product does not support the nonDRX mode.
DRX mode
Packet transfer mode
NonDRX mode
DRXmode
BS_PA_MFRMS BS_PA_MFRMS BS_PA_MFRMS
BS_PA_MFRMS BS_PA_MFRMS
CCCH channels belonging to the paging Group
All CCCH channels
CCCH channels belonging to the paging Group
Figure 215
The occurrence of the CCCH channels
236
2.9
Timing advance
The TAI defines the PTCCH subchannel used by the MS for the continuous timing advance. The TAI is allocated by the PCU and the timing advance is computed by the BTS. The MS sends an access burst in the assigned PTCCH (specified by the TAI). This burst is used by the BTS to compute the timing advance. The BTS updates the timing advance values in the next TAmessage following the access burst. If the TAI and Timing advance timeslot are present in the assignment message, the MS shall immediately begin operation of the Continuous Timing Advance procedure at the point in time denoted by the TBF starting time if present, otherwise after the reaction time. The TAI is coded on 4 bits, so on a Timing advance timeslot we can have a maximum of 16 MS. The following table (see Figure 216) gives an example of the continuous timing advance. Each row represents a 52multiframe. If present, the TBF_STARTING_TIME, given in the assignment message, defines the frame number from which the MS is allowed to start the continuous timing advance procedure. The four access bursts is supported, so it means that for the first phase of the downlink TBF establishment (on CCCH), the TAI is not provided by the allocator. The TAI is provided in the second phases of access in uplink and downlink.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
237
Uplink B0 B1 B2
TAI = 0 0 B4
52multiframe number n B5 B6 1 B7 B8 B9
TAI = 1 2 B10 B11 B12 3
Downlink Uplink B0 B1
TA_message 1 TAI = 2 B2 4 B4
TA_message 1 52multiframe number n+1 B5 B6 5 B7 B8 B9 TAI = 3 6 B10 B11 B12 7
Downlink
TA_message 4
TA_message 4
Figure 216
Example of continuous timing advance
238
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
OMCR algorithms parameters
31
OMCR ALGORITHMS PARAMETERS

For each of the following parameters, the name, class, description, range and default values are given. When available, recommended values as well as engineering rules are specified. Parameters class definitions are given below: Class 0: Class 0 attributes can only be set before the BSC application database is built. The system is effectively reconfigured after the BSC database is built in response to a Built BDA command. Class 1: Class 1 attributes can only be set when the related BSC object is locked. Class 2: Class 2 attributes can only be set when the object is locked and the parent BSC object is unlocked. Class 3: Class 3 attributes can only be set when the parent BSC object is unlocked. The system is immediately reconfigured and there is no impact on the system operations.
3.1
Call establishment parameters

maxDwAssign Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Type : Default value : V12
Maximum number of Immediate Assignment Downlink messages per second. Used to configure signaling block. [1 to 49] bts DP , Optimization 8
Recommended value : Simulation (8) Comments : In uplink, maxDwAssign blocks per second are reserved for Packet Control Acknowledgement messages and, in downlink, maxDwAssign blocks per second are reserved for Packet Downlink Assignment messages. V12
maxNbrPDAAssig Class 2 (gprsTranscvLockExtendedConf) Description : Range value : Object :
Maximum number of repetition of Packet Downlink Assignment message [1 to 10] transceiver
32
Type : Default value :
DP , Optimization 5
maxRach Class 3 Description :
V12 Maximum number of RACHs (Random Access Channel) accepted by the PCU per second (only considered for uplink transfer) [0 to 49] blocks bts 0
Range value : Object : Default value :
Recommended value : 15 Engineering Rules : The higher the maxRach the higher the number of Channel Request per second is accepted, with a risk of PCU overload. Besides, if maxRach is too low, the establishment time may be increased.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
33
MS
PCU
MAXRACH filter
RACH (CCCH)
IMM. ASSIGN.
P.RESOUR. REQ.
P. UL. ASSIGN.
Figure 31
maxRach part on the Uplink Establishment Transfer
Comments :
*In uplink, 16 blocks per second are reserved for Packet Resoure Request messages while, in downlink, up to maxRach blocks can be allocated for Packet Uplink Assignment messages (empty or prereserved blocks for Packet Uplink Assignment messages but unused). **Only values between 0 and 15 will be considered. If greater then 15 is taken into account. ***The load (traffic in uplink) and the radio conditions (BLER) in the cell must be evaluated in order to estimate this value. Moreover, the correlation with several parameters must be taken into account. Indeed after the expiration of many counters and timers, an abnormal release with random access is performed. Therefore, if one of these parameters is underestimated, the RACH access will often be used and maxRach must increase.
34
reserved3 (T3168) Class 3 (gprsBtsExtendedConf) Description :
V12
Wait for the reception of the uplink assignment after sending a Packet Resource Request message. This T3168 timer is used on the MS side to define when to stop waiting for Packet Uplink Assignment message after sending a packet resource request message.
Range value : Object : Type : Default value :
[0 to 7] bts DP , Optimization 5
Recommended value : See Engineering Rules Engineering Rules : The radio conditions (BLER for signalling messages) must be taken into account to set the value of the timer.
For very good radio conditions: BLER (for signalling
blocks) < 2%, T3168 = 0.5 s

For good radio conditions: 2% < BLER (for signalling
blocks) < 5%, T3168 = 1 s

For bad radio conditions: 5% < BLER (for signalling
blocks) < 10%, T3168 = 2 s Comments : It corresponds to parameters gprsTimerWaitPUAM. Values from 0 to 7 correspond to (in milliseconds):
0 = 500, 1 = 1000, 2 = 1500, 3 = 2000, 4 = 2500, 5 = 3000, 6 = 3500, 7 = 4000.
T3172 Class 3 (gprsBtsExtendedConf) Description : Range value :
V12
Value of the timer started by the mobile on reception of a Packet Access Reject message (in seconds) [1 to 255]
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
35
Object : Default value :
bts 5
Recommended value : 5 Comments : Packed Access Rejected messages are not managed yet.
36
3.2
Countdown procedure parameters

bsCvMax Class 3 Description : Range value : Object : Default value : V12 Number of packets left to transmit from which the MS counts those packets [1 to 15] bts 1
Recommended value : >10 Engineering Rules : Used by the PCU for the resources allocation management. Timer T3198 on the MS side shall have the expiry value set to bsCvMax block periods. This timer is started each time the MS transmits a RLC data block. At the expiration of it, the MS is allowed to accept negative acknowledgement for the RLC data block considered.
In one hand, the higher the value the lower the
efficiency of the Sliding Window procedure.

In the other hand, the lower the value, the higher the risk
to waste bandwidth by retransmitting blocks which do not have the time to be received by the PCU. The delay propagation between the MS and the PCU has to be evaluated to ensure that the value of the timer is greater. According an R&D estimation, the round trip delay is around 200 ms and so the delay between the BTS and the PCU is around 100 ms. The timer T3198 shall have the expiry value set to bsCvMax blocks periods. As a result, T3198 must be over 100 ms and bsCvMax over 10.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
37
3.3
Radio link failure parameters

maxNbrRLCEmptyBlock Class 2 (NN0001Max) Description : Range value : Object : Type : Default value : V12
Maximum number of consecutive RLC erroneous blocks [1 to 255] transceiver DP , Optimization 10
N3105max Class 2 (gprsTranscvLockExtendedConf Description :
V12
Maximum number of consecutive RLC data blocks sent by PCU with a valid RRBP and not having been acknowledged by the MS [1 to 64] transceiver DP , Optimization 4
Recommended value : 4 Comments : The network shall increment counter N3105 for each radio block, allocated to that mobile station with the RRBP field, for which no RLC/MAC control message is received. If N3105 = N3105max, the network shall release the downlink TBF internally and start timer T3195 (default value=5s). When T3195 expires, the network may reuse the TFI. V12 Counters used in case of block acknowledgment time out. The MSs counter N3102 is decremented by panDec each time the timer for packet uplink ack/nack expires. [0 to 7] bts 0
panDec Class 3 (pan) Description :
38
Recommended value : 1 Engineering Rules : The evolution of V(A) is directly linked to the BLER present in the Cell. Therefore, PAN values depend on the Cell load and on the Radio environment. It is better to take a high panMax just as panInc value must be bigger than panDec value in order to avoid the access on CCCH and on BCCH. The following proposition: panInc = 2*panDec can be considered. Comments : At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter panMax. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value panInc, however N3102 shall never exceed the value panMax. Each time T3182 (default value=5s) expires the mobile station shall decrement N3102 by the broadcast value panDec. When N3102 =<0 is reached, the mobile station shall perform an abnormal release with cell reselection. V12 Counters used in case of block acknowledgment time out. The MSs counter N3102 is incremented by panInc each time a packet uplink acknowledgment which allow the transmit window to go forward, has been received. [0 to 7] bts
panInc Class 3 (pan) Description :
Range value : Object :
Recommended value : 2
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
39
Engineering Rules :
The evolution of V(A) is directly linked to the BLER present in the Cell. Therefore, PAN values depend on the Cell load and on the Radio environment It is better to take a high panMax just as panInc value must be bigger than panDec value in order to avoid the access on CCCH and on BCCH. The following proposition: panInc = 2*panDec can be considered.
Comments :
At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter panMax. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value panInc, however N3102 shall never exceed the value panMax. Each time T3182 (default value=5s) expires the mobile station shall decrement N3102 by the broadcast value panDec. When N3102 =<0 is reached, the mobile station shall perform an abnormal release with cell reselection. V12
panMax Class 3 (pan) Description :
Counters used in case of block acknowledgment time out. Maximum value of the counter N3102 set by the mobile at each cell reselection. [0 to 7] bts 0
Recommended value : 7 Engineering Rules : The evolution of V(A) is directly linked to the BLER in the Cell. Therefore, PAN values depend on the Cell load and on the Radio environment.
310
It is better to take a high panMax just as panInc value must be bigger than panDec value in order to avoid the access on CCCH and on BCCH. The following proposition: panInc = 2*panDec can be considered. Comments : At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter panMax. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value panInc, however N3102 shall never exceed the value panMax. Each time T3182 (default value=5s) expires the mobile station shall decrement N3102 by the broadcast value panDec. When N3102 =<0 is reached, the mobile station shall perform an abnormal release with cell reselection.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
311
3.4
Cell selection and reselection parameters

cellReselectHysteresis Class 3C3 Description : Range value : Object : Default value : Type : Hysteresis to reselect towards cell with different Location Area [0 to 14, by steps of 2] dB bts 6 DP , Optimization
Recommended value : 4 dB (rural), 6 dB (urban) Engineering Rules : A high value prevents the MS from making frequent location updates and may also prevent an MS from performing adequate location updates, thus risking not receiving calls. The level variation of the signal is more important in an urban context, so a higher value of hysteresis should be set. To avoid frequent location updates, there is also a timer forbidding the reselection of the previous server cell. For a reselection with change of location area, the value is 15 seconds (GSM recommendation). This is a GSM parameter. V12
Comments :
gprsCellActivation Class 3 Description : Range value : Default value :
Flag used to activate the GPRS at cell level (to allow the GPRS MSs to access) [disabled / enabled] disabled
Recommended value : enabled
312
gprsPermittedAccess Class 3 Description :
V12
It defines the Routing Area Color of the cell. If the mobile station revecives different values of the RA COLOUR field from different cells, the mobile station must interpret the cell reselection information as if the two cells belonged to different routing aeras. [0 to 7] bts 0
Recommended value : Not Applicable
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
313
3.5
DRX mode parameters

drxTimerMax Class 3 Description : Range value : Object : Default value : V12 Maximum value allowed for mobile stations to request nonDRX mode after packet transfer mode [0 to 7] seconds bts 0s
Recommended value : 7 Engineering Rules : After the transfer mode, the mobile remains in non DRX mode during min (NON_DRX_TIMER, drxTimerMax). The recommended value set to 7 (maximum value) means that the value taken into account will be the mobiles one (NON_DRX_TIMER). Before V12.4c, the mobile directly switch to DRX mode after leaving the transfer mode.
Comments :
314
3.6
Power control parameters

btsSensitivity Class 3 Description : Range value : Object : Default value : V12 Minimum power needed for BTS decoding. This parameter has an influence on the power control efficiency. [0 to 255] bts 0
Recommended value : 25 (see Manual Manual < 36 > BSS Parameter User Guide) Engineering Rules : The power control algorithm used is Open Loop Control. A pure open loop is achieved by setting = 1 and keeping CH constant. The constant value of CH is: CH = 0 PBTS BtsSensitivity + 48 where PBTS is is the BTS transmit power on PDTCH. Since downlink power control is not implemented yet, PBTS is equal to bsTxPwrMax. According to the GPRS Engineering test plan, the lowest the amplitude of the signal is, the highest the BER is. The sensitivity of BTS is mainly impacted by:
Ambient noise (urban noise due to cars, other radio
systems,..)
Internal noise of the BTS, and its noise factor Modulation bandwidth of the radio signal (in GSM it is
271 kHz)
C/I environment, and Rayleighs fading
Normally, since the radio modulation and coding are the same for GSM and GPRS, the sensitivity of the BTS should not vary. Measurements have already been performed, and they all showed a sensitivity (S8000) (with particular conditions) of 110 dBm.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
315
However, they do not have any consequences on the Bts. They are used by the PCU to calculate CH. Then CH is forward to the MS and it allows the MS to calculate its output power (See Figure 32 below). Thus with CH the MS can calculate its output power. Comments : The value x set on the OMCR MMI corresponds to x dBm.
1 3 2 P CH ( BtsSensitivity, MaxBsTransmitPower) BSC BTS
BtsSensitivity MaxBsTransmitPower
MS
PCU
Figure 32
Parameters of MS Output Power.
According to a RF study, the following results can be considered:

Low CH values mean little or No Power Control Medium CH values mean Power Control at high signal High CH values mean lots of Power Control
nAvgl Class 3 (gprsAvgParam) Description :
V12
Signal strength filter used for MS output power control It specifies the interference signal strength filter constant for power control.
316
[0 to 15] bts 0 V12
nAvgT Class 3 (gprsAvgParam) Description :
Signal strength filter used for MS output power control It specifies the signal strength filter period for power control in packet transfer mode.
[0 to 25] bts 0
Recommended value : 25 Engineering Rules : The used power control algorithm is Open Loop Control. In packet idle mode, the MS measures its own paging group on PPCH. It does measurements per nAvgW multiframes and continuously updates C. Meanwhile, the BSS measures the interference of the PDCHs, which are candidates for the transfer phase. The BSS continuously updates the CH values (see Figure 33) to be used for the first transfer period of nAvgT multiframes. This is transferred to the MS in the PACKET UPLINK ASSIGNMENT. In packet transfer mode, the MS measures all RLC blocks on the PDCH carrying the PACCH and filters the obtained CBLOCK. The MS updates the C value every nAvgT multiframes. The BSS measures all RLC blocks on the used PDCH. The BSS updates the MS specific CH values and transfers them to the MS when needed (i. e. when the interference level has changed). The BSS updates the CHvalue every nAvgT multiframes if necessary (see Figure 34).
The smaller the periods the higher the flexibility for the
Power Control.
However important period smoothes the output power
from the MS. A too strong variation of power may create interference. Comments : The propose recommended value is to optimize uplink power control algorithm for Mitsubishi mobiles.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
317
Non transfer phase
Transfer phase
MS uses Pa
MS uses Pb
MS uses Pc
Ci T AVG_W
Cj T AVG_W
Ca T AVG_T
Cb T AVG_T
Cc T AVG_T
Cd
Cd
Figure 33
Traffic example of uplink power control
nAvgW Class 3 (gprsAvgParam) Description :
V12
Signal strength filter used for MS output power control It specifies the signal stength filter period for power control in packet idle mode.
[0 to 25] bts 0
Recommended value : 25 Engineering Rules : The used power control algorithm is Open Loop Control. In packet idle mode, the MS measures its own paging group on PPCH. It does measurements per nAvgW multiframes and continuously updates C. Meanwhile, the BSS measures the interference of the PDCHs, which are candidates for the transfer phase. The BSS continuously updates the CH values (see Figure 33) to be used for the first transfer period of nAvgT multiframes. This is transferred to the MS in the PACKET UPLINK ASSIGNMENT. In packet transfer mode, the MS measures all RLC blocks on the PDCH carrying the PACCH and filters the obtained Cblock. The MS updates the C value every nAvgT multiframes. The BSS measures all RLC blocks on the used PDCH. The BSS updates the MS specific CH values and transfers them to the MS when needed (i. e. when the
318
interference level has changed). The BSS updates the CHvalue every nAvgT multiframes if necessary (see Figure 34).
The smaller the periods the higher the flexibility for the
Power Control.
However important period smoothes the output power
from the MS. A too strong variation of power may create interference. Comments : The propose recommended value is to optimize uplink power control algorithm for Mitsubishi mobiles.
Non transfer phase
Transfer phase
MS uses Pa
MS uses Pb
MS uses Pc
Ci T AVG_W
Cj T AVG_W
Ca T AVG_T
Cb T AVG_T
Cc T AVG_T
Cd
Cd
Figure 34
Traffic example of uplink power control
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
319
3.7
Timeslot sharing parameters

channelType Class 2 C4 Description : Range value : Type of logical channel supported by a radio time slot [tCHFull (traffic) / sDCCH (traffic) / mainBCCH / mainBCCHCombined (with SDCCH) / bcchSdcch4CBCH / sdcch8CBCH / cCH (V12) / pDTCH (V12)] channel None DP , Optimization
Object : Default value : Type :
Recommended value : pDTCH gprsPreemption Class 3 (gprsBtsExtendedConf) Description : V12
Allows the Cell to refuse the GSM preemption if the GPRS resources are not sufficient to the minimum of Bandwidth share for each MS. [yes / no] bts DP , Optimization False
Comments :
No recommended value is specified since it this parameter depends on the resources dimensioning strategy. V12
gprsPreemptionProtection Class 3 (gprsBtsExtendedConf ) Description :
Protection timer used by the BSC in order to reduce the load in case of PCU TDMA TS status NACK message reception during a preemption procedure. This message is sent by the PCU [1 to 60] second(s) bts 10 DP , Optimization
Range value : Object : Default value : Type :
320
Recommended value : 10 gprsPriority Class 2 (gprsTranscvLockExtendedConf) Description : Range value : Object : Default value : Type : Comments : Priorities that can be affected to the TDMA [p1 / p2] transceiver p1 DP , Optimization Only 1 GPRS TDMA until drop 1.3 at least. No recommended value is specified since it this parameter depends on the resources dimensioning strategy. V12 V12
minNbrGprsTs Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value : Comments : [0 to 127] bts 0
Minimum number of TS dedicated to GPRS in your cell
It ensures a minimum of GPRS timeslots in the Cell. No recommended value is specified since it this parameter depends on the resources dimensioning strategy. V12
msCapWeightActive Class 2 Description : Range value : Object : Default value :
It specifies whether the Weight Fair Allocation algorithm is actived or not [yes / no] bts yes
Recommended value : yes radioAllocator Class 2 Description : Range value : radio allocator type used in the cell [voice + dataCircuit, voice + dataCircuit + packetData] V12
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
321
Object : Default value : Type :
bts voice + dataCircuit DP , Optimization
Recommended value : voice + dataCircuit + packetData
322
3.8
Dualband cell parameters

btsSensitivityInnerZone Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value : Type : V12
Minimum power needed for BTS decoding in the inner zone of a dualband cell [0 to 255] bts 0 DP , Optimization
Recommended value : See Engineering Rules Engineering Rules : This parameter should be set according to GSM dualband cell parameters (see Manual < 36 > BSS Parameter User Guide). The value x set on the OMCR MMI corresponds to 110+x dBm. V12
Comments :
maxBsTransmitPowerInnerZone Class 3 (gprsBtsExtendedConf ) Description : Range value : Object : Default value : Type :
Maximum level of BTS transmission power in the inner zone of a dualband cell [2 to 51] bts 10 DP , Optimization
Recommended value : See Engineering Rules Engineering Rules : This parameter should be set according to GSM dualband cell parameters (see Manual < 36 > BSS Parameter User Guide). The value x set on the OMCR MMI corresponds to 110+x dBm.
Comments :
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
323
3.9
TDMA selection parameters

codingScheme Class 2 Description : Range value : Object : Default value : V12 Channel coding scheme that the Mobile Station shall use when transmitting data on the uplink [cs1, cs2] transceiver cs1
Recommended value : cs2 Engineering Rules : It has a direct impact on the RLC/MAC throughput. In fact cs1 is better than cs2 to convey RLC blocks in a reliable way. However in a good radio conditions cs2 provide a higher throughput than cs1.
Using cs1, whatever the profile considered, BLER will
not exceed 6% on the whole region already covered with acceptable voice quality.
Using cs2, whatever profile considered, it will be very
difficult on certain cells / regions to ensure GPRS coverage with acceptable user throughput, as maximum BLER will exceed 10%. Percentage of area covered with acceptable BLER:
Using cs1, whatever profile considered, acceptable
BLER can be offered on a large part of the region (more than 92% covered with BLER better than 0.1).
Using cs2, whatever profile considered, some areas will
suffer from very high BLER and then limited throughput (typically GPRS calls at cell boundaries).
324
3.10
Sliding window parameters

dwAckTime Class3 (packetAckTime) Description : Range value : Object : Default value : V12
Time (multiple of 20 ms) defining the period for the acknowledgments for downlink transfers [1 to 64] blocks transceiver For 1+1 mobiles, one block per bitmap (every 24 blocks) is reserved for Packet downlink acknolewdgement. Two blocks per bitmap are reserved for other mobiles. DP
Type :
maxNbrPUDWithoutVchange Class 2 (NN0002Max) gprsTransvLockExtendedConf Description :
V12
Maximum number of PACKET UPLINK (resp. DOWNLINK) ACK/NACK consecutively sent (resp. received) without V(R) (resp. V(Q)) is changed. [1 to 255] transceiver DP , Optimization 10
Recommended value : 10 Comments : Recommended value comes from trials results. V12
N3103Max Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value :
Maximum number of repetition of a Packet Uplink Ack/Nack message [1 to 64] bts 0
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
325
upAckTime Class3 (packetAckTime) Description : Range value : Object : Default value : Type :
V12
Time (multiple of 20 ms) defining the period for the acknowledgments for uplink transfers [1 to 64] blocks transceiver 1 DP
Recommended value : 10 Engineering Rules : Values can be set between 2 and 23, which means uplink acknowledgements are sent at most 1 block out of 2 and at least once per bitmap.
326
3.11
Block allocation parameters

blockErrorRate Class 3 (allocBitmap) Description : V12
Block error rate in the cell used by the PCU to build allocation bitmap. This parameter is used to estimate the number of blocks to add in the bitmap allocation (for close ended TBF) due to retransmission caused by degraded radio conditions. [0 to 127] blocks [0, 100]% transceiver DP , Optimization 0
Recommended value : 24, Engineering rule (10) Engineering Rules : This parameter should be set according to the radio characteristics of the considered cell.
maxSize Class 3 (allocBitmap) Description : Range value : Object : Type : Maximum size of the allocation bitmap provided to the MS [0 to 127] blocks transceiver DP , Optimization
Recommended value : 24 Engineering Rules : In one hand, the higher the size of the bitmap the higher the connection establishment duration (a channel request has to wait at least one bitmap size before being introduced in the next bitmap).
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
327
Request TBF
Bitmap current: Bitmap i
Bitmap fixed: Bitmap i+1
Resources allocated
Bitmap in changing: Bitmap i+2
Figure 35
Impact of AllocBitmap on TBF Establishment duration
On the other hand, the smaller the bitmap size the lower the throughput (a new bitmap has to be requested more often). So a tradeoff has to be found between the connection establishment duration and the throughput. Comments : For V12.4a&b, the bitmap size is fixed and equal to 24. V12
maxDnTbfPerTs Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value :
Maximum number of downlink TBF per TDMA on a timeslot basis [1 to 8] bts 8
328
maxUpTbfPerTs Class 3 Description : Range value : Object : Default value :
V12
Maximum number of uplink TBF per TDMA on a timeslot basis [1 to 8] bts 8
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
329
3.12
Other access network parameters

bscGprsActivation Class 3 Description : Range value : Default value : Flag used to activate the GPRS at BSC level [disabled / enabled] disabled V12
Recommended value : enabled longTbfLossThroughput Class 3 (gprsBtsExtendedConf) Description : V12
Loss of throughput for long TBF in percentage of allocated bandwidth. Prioritize normal transfer over long data transfer. [1 to 100] in % bts DP , Optimization 0 V12
longTbfSizeThreshold Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Type : Default value :
Threshold for long TBF size, in Kbytes. This parameter is used in the functionality which penalize long TBF. [1 to 65535] bts DP , Optimization 100 V12
reserved4 (T3192) Class 3 (gprsBtsExtentedConf) Description :
Wait for release of the TBF after reception of the final block. This timer T3192 is used on the Mobile Station side to define when the Mobile Station has received all the RLC data blocks. When the timer expires the Mobile Station releases the resources associated with the TBF and begins to monitor its paging.
Range value :
[0 to 7]
330
Object : Type : Default value : Engineering Rules :
bts DP , Optimization 5 In one hand the higher the value set to this timer, the higher the risk of Blocking Rate due to the fact that the MS keeps its TFI and it remains on the TS allocated. On the other hand, the higher the value set to this timer, the lower the risk of the establishment using access on CCCH. Therefore it can decreases the load on CCCH and also the establishment time. The value of this timer has to take into account the kind of traffic in the cell. Therefore the typical call profiles in the cell has to be considered. Indeed it is worth to set an important value only if the downlink traffic pattern is consisting of successive ON periods with a short mean delay between two ON periods.
Comments :
This parameter corresponds to parameters gprsTimerWaitRLC. Values from 0 to 7 correspond to (in milliseconds):
0 = 500, 1 = 1000, 2 = 1500, 3 = 2000, 4 = 2500, 5 = 3000, 6 = 3500, 7 = 4000.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
331
3.13
Reserved parameters
dLPwrValue Class 3 Description : Range value : Object : Default value : Attribute reserved for future use [0 to 3] corresponding to 0 to 6 dB/8 to 14 dB/16 to 22 dB/24 to 30 dBm transceiver 0 V12 V12
maxDnTbfP1P2Threshold Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value : Attribute reserved for future use [1 to 32] bts 16
maxUpTbfP1P2Threshold Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value : Attribute reserved for future use [1 to 32] bts 16
V12
nbrFreeTchBeforeAnticipation (gprsBtsExtendedConf ) Class 3 Description : Range value : Object : Attribute reserved for future use [0] bts
V12
Comments :
It is part of gprsBtsExtendedConf. V12
nbrFreeTchToEndAnticipation Class 3 Description : Range value : Object : Attribute reserved for future use [0] bts
Comments :
It is part of gprsBtsExtendedConf.
332
speechOnHoppingTs Class 3 (gprsBtsExtendedConf) Description : Range value : Object : Default value : Attribute reserved for future use [true, false] bts false
V12
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
PCUSN OAM algorithm parameters
41
PCUSN OAM ALGORITHM PARAMETERS

In this chapter are listed the parameters related to PCUSN and, more precisely, to the Gb interface. Those parameters are managed by the PCUSN OAM. The criticity field indicates the impact of a parameter setting change on the network service. If the field criticity is equal to None, then the parameter value update is dynamic and no service interruption is undergone.
4.1
Network service parameters

nsAliveRetries (GprsNsProv) Description : V12
This attribute specifies the times the NSALIVE message can be retried if NSALIVE ACK is not received before the nsAliveTimer expires. [3 to 10] seconds 10
Range value : Default value :
Criticity :
None V12
nsAliveTimer (GprsNsProv) Description :
This attributes specifies the timer to guard the Network Service Virtual Connection (NSVC) ALIVE procedure. This the time intervall between an NSALIVE and NSALIVE ACK. [1 to 10] seconds 3
Criticity : Engineering Rules :
None The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). The default value is the one provided in the GPRS specifications.
42
nsBlockRetries (GprsNsProv) Description :
V12
This attributes specifies the number of times the NSBLOCK message can be retried if NSBLOCK ACK is not received before nsBlockTimer expires. [0 to 10] 3
Criticity :
None V12
nsBlockTimer (GprsNsProv) Description :
This attributes specifies the timer to guard the Network Service Virtual Connection (NSVC) BLOCK and UNBLOCK procedures. This the time intervall between an NSBLOCK and NSBLOCK ACK, or between an NSUNBLOCK and NSUNBLOCK ACK. [1 to 120] seconds 3
None The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). The default value is the one provided in the GPRS specifications. V12
nsResetRetries (GprsNsProv) Description :
This attribute specifies the times the NSRESET message can be retried if NSRESET ACK is not received before the nsResetTimer expires. [3 to 10] 5
Criticity :
None
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
43
nsResetTimer (GprsNsProv) Description :
V12
This attributes specifies the timer to guard the Network Service Virtual Connection (NSVC) RESET procedure. This is the time intervalle between an NSRESET and NSRESET ACK [1 to 120] seconds 3 None The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). The default value is the one provided in the GPRS specifications. V12
Range value : Default value : Criticity : Engineering Rules :
nsTestTimer (GprsNsProv) Description :
This attribute specifies the periodicity of the Network Service Virtual Connection (NSVC) TEST procedure which is the initiation of the NSALIVE Protocol Data Unit. [1 to 60] seconds 30 None The range is the value provided in the GPRS specifications. Increasing the timer value results in longer time before the test procedure is re to executed, which means the NSVC could be dead but the software might find it out late. They could be a loss of packets. V12
nsUnblockRetries (GprsNsProv) Description :
This attributes specifies the number of times the NSUNBLOCK message can be retried if NSUNBLOCK ACK is not received before nsBlockTimer expires. [3 to 15] 3 None
Range value : Default value : Criticity :
44
resumeRetries (GprsPcBssgpProv) Description :
V12
This attribute specifies the maximum number of times the Packet Control Unit (PCU) can send the RESUME PDU in case a RESUME ACK is not received before the resumeTimer expires. [0 to 6] 3
Criticity :
None V12
resumeTimer (GprsPcBssgpProv) Description :
This attribute specifies the timer to guard the RESUME procedure. The Packet Control Unit (PCU) sends a RESUME Protocol Data Unit (PDU) to the Serving GPRS Support Node (SGSN) and starts the resumeTimer. The PCU stops the timer upon reception of a RESUMEACK (NACK) PDU from the SGSN. If the timer expires, the PCU retries the RESUME procedure. [1 to 10] seconds 5
None The range is the value provided in the GPRS specification. The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU).
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
45
4.2
BSSGP parameters
bvcBlockRetries (GprsPcBssgpProv) Description : V12
This attributes specifies the maximum number of times the Packet Control Unit (PCU) can send the BVCBLOCK Protocol Data Unit (PDU) in case a BVCBLOCK ACK is not received before the bvcBlockUnblockTimer expires. [0 to 6] 3
Criticity :
None V12
bvcBlockUnblockTimer (GprsPcBssgpProv) Description :
This attribute specifies the timer to guard the blocking and unblocking procedures. The Packet Control Unit (PCU) sends a BVCBLOCK (UNBLOCK) Protocol Data Unit (PDU) to the serving GPRS Support Node (SGSN) and starts the bvcBlockUnblockTimer. The PCU stops the timer upon reception of a BVCBLOCK (UNBLOCK) ACK PDU from the SGSN. If the timer expires, the PCU retries the BVCBLOCK (UNBLOCK) procedure. [1 to 30] seconds 15
None The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). V12
bvcResetReqRetries (GprsPcBssgpProv) Description :
This attributes specifies the maximum number of times the Packet Control Unit (PCU) can send the BVCRESET Protocol Data Unit (PDU) in case a BVCRESET ACK is not received before the BvcResetReqTimer expires. [0 to 6] 3
46
Criticity : None Recommended value : 5 Engineering Rules : If BvcResetReqRetries is set to 5, the time for the distant to send to send the BVCRESET ACK will be (5+1) *10 = 60 seconds, which according to IOT tests, is enough. V12
bvcResetReqTimer (GprsPcBssgpProv) Description :
This attribute specifies the timer to guard the BVCRESET procedures. The Packet Control Unit (PCU) sends a BVCRESET Protocol Data Unit (PDU) to the serving GPRS Support Node (SGSN) and starts the bvcResetReqTimer for a BVC. The PCU stops the timer upon reception of a BVCRESET ACK PDU from the SGSN. If the timer expires, the PCU retries the BVCRESET procedure. [1 to 120] seconds 60
bvcUnblockRetries (GprsPcBssgpProv) Description :
This attributes specifies the maximum number of times the Packet Control Unit (PCU) can send the BVCUNBLOCK Protocol Data Unit (PDU) in case a BVCUNBLOCK ACK is not received before the bvcBlockUnblockTimer expires. [0 to 6] 3
Criticity :
None
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
47
flowControlMaxRate (GprsPcBssgpProv) Description :
V12
This attribute specifies the minimum interval between sending consecutive Flow Control PDU for a given BSS GPRS Virtual Connection (BVC) or for a Mobile Station (MS). [100 to 10000] milliseconds 1000
None Changing the value can affect the flow control function at the PCU level with the Logical Link Control (LLC) frames discarded due to overflow of the MS or BVC buckets. This parameter should be lower msFlowControlThTimer (see SGSN parameter). than
Comments :
msFlowCntlBucketSize (GprsPcBssgpProv) Description : Range value : Default value :
V12
This attribute specifies the Mobile Station (MS) maximum bucket size. [0 to 655355] *100 bits/s 90
Criticity : None Recommended value : 200 Engineering Rules : The default value assumes 6 Logical Link Control (LLC) frames in the bucket. The unit is 100 bit/s. A recommended value for the maximum size of the bucket would be 320, based on the waiting factor of 30 seconds and considering that if data are older than 30 seconds, they become useless. The higher the value, the more CPU load is saved.
48
raCapabilityUpRetries (GprsPcBssgpProv) Description :
V12
This attributes specifies the maximum number of times the Packet Control Unit (PCU) can send the RACAPABILITYUPDATE Protocol Data Unit (PDU) in case a RACAPABILITYUPDATE ACK is not received before the raCapabilityUpTimer expires. [0 to 6] 3 None V12
raCapabilityUpTimer (GprsPcBssgpProv) Description :
This attribute specifies the timer to guard the RACAPABILITYUPDATE procedure. When the Packet Control Unit (PCU) sends a RACAPABILITYUPDATE Protocol Data Unit (PDU) to the serving GPRS Support Node (SGSN) and starts the raCapabilityUpTimer. The PCU stops the timer upon reception of a RACAPABILITYUPDATE ACK PDU from the SGSN. If the timer expires, the PCU retries the RACAPABILITYUPDATE procedure. [1 to 30] seconds 15 None The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). V12
resumeRetries (GprsPcBssgpProv) Description :
This attribute specifies the maximum number of times the Packet Control Unit (PCU) can send the RESUME PDU in case a RESUME ACK is not received before the resumeTimer expires. [0 to 6] 3 None
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
49
resumeTimer (GprsPcBssgpProv) Description :
V12
This attribute specifies the timer to guard the RESUME procedure. The Packet Control Unit (PCU) sends a RESUME Protocol Data Unit (PDU) to the Serving GPRS Support Node (SGSN) and starts the resumeTimer. The PCU stops the timer upon reception of a RESUMEACK (NACK) PDU from the SGSN. If the timer expires, the PCU retries the RESUME procedure. [1 to 10] seconds 5
None The range is the value provided in the GPRS specification. The timer must be provisioned to a value that is greater than the maximum expected round trip delay of a Protocol Data Unit (PDU). V12
suspendRetries (GprsPcBssgpProv) Description :
This attributes specifies the maximum number of times the Packet Control Unit (PCU) can send the SUSPEND Protocol Data Unit (PDU) in case a SUSPEND ACK is not received before the suspendTimer expires. [0 to 6] 3
Criticity :
None V12
suspendTimer (GprsPcBssgpProv) Description :
This attribute specifies the timer to guard the SUSPEND procedures. The Packet Control Unit (PCU) sends a SUSPEND Protocol Data Unit (PDU) to the serving GPRS Support Node (SGSN) and starts the suspendTimer. The PCU stops the timer upon reception of a SUSPEND ACK (NACK) PDU from the SGSN. If the timer expires, the PCU retries the SUSPEND procedure. [1 to 10] seconds
Range value :
410
Default value :
tsFlowCntlBucketSize (tsBmax) (GprsPcBssgpProv) Description :
This attribute specifies the maximum bucket size (Bmax) for a BSS GPRS Virtual Connection (BVC) Flow Control procedure. The value is the BVC Max Bucket size for a BVC with 1 time slot. The PCU calculates the actual BVC Max Bucket size for the configuration by multiplying this provisioned value by the number of time slot in the cell, dinamically given by the Base Station Controller (BSC). [0 to 655355] *100 bytes 200
Criticity : None Recommended value : 1600 Engineering Rules : The default value has been estimated based on the msFlowCntlBucketSize default value, with 8 mobiles in downlink transfer. The unit is 100 bytes. From V12.4c, tsFlowCntlBucketSize should be set to msFlowCntlBucketSize * 8. Before, tsFlowCntlBucketSize = msFlowCntlBucketSize
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
411
tsLeakRate (GprsPcBssgpProv) Description :
V12
This attribute specifies the leak rate parameter for a BVC with 1 time slot. The PCU calculates the actualBVC leak rate for the configuraton, by multiplying the provisioned value by the number of time slots in the cells, dynamically given by the BSC. [0 to 655355] *100 bits/s 100
None The default value assumes a CS1 mobile station, with a throughput of 10000 bit/s, with assumption that the flow is statiscally regular in the cell. The unit is 100 bit/s.
412
4.3
Frame relay parameters

accounting (ac) (FrAtmDlciSpProv) Description : V12
This attribute allows the operator to control accounting for this DLCI. To enable accounting data collection and record generation, the value of this attribute must be onand at least one of the accountCollection reasons in the FrAtm Ca component must be set. [on / off] off
Criticity :
None V12
committedBurstSize (bc) (FrAtmDlciSpProv) Description :
This attribute specifies the committed burst size (Bc). It represents the amount of data that a network agrees to transfer under normal conditions over a measurement interval when rate enforcement is in effect. Data marked DE=1 is not accounted for in the committed burst size. When rate enforcement is not in effect, this attribute is ignored. [0 to 50000000] bit 64000
None The committedInformationRate must have a value of 0 when rate enforcement is in effect and committedBurstSize has a value of 0.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
413
committedInformationRate (cir) (FrAtmDlciSpProv) Description :
V12
This attribute specifies the committed information rate (CIR). It represents the rate at which the network agrees to transfer information under normal conditions when rate enforcement is in effect. When rate enforcement is not in effect, this attribute is ignored. Determination of the actual CIR is based on committedInformationRate, committedBurstSize and a measurement interval. The measurement interval is determined internally when committedInformationRate has a non to zero value. Otherwise, it is based on measurementInterval which must be explicitly provisioned. [0 to 50000000] bits/s 64000
None The committedBurstSize must have a value of 0 when rate enforcement is in effect and committedInformationRate has a value of 0. V12
excessBurstSize (be) (FrAtmDlciSpProv) Description :
This attribute specifies the excess burst size (Be). It represents the amount of uncommitted data that the network will attempt to deliver over a measurement interval when rate enforcement is in effect. Data marked DE=1 by the user or by the network is accounted for here. committedInformationRate, committedBurstSize, and excessBurstSize cannot all be zero when rate enforcement is in effect. [0 to 50000000] bit 64000
None The default value assumes 6 Logical Link Control (LLC) frames in the bucket. The unit is 100 bit/s. Decreasing the value may lower the throughput on the Gb interface. The higher the value, the more CPU load is saved.
414
maximumFrameSize (n203) (FrAtmDlciSpProv) Description :
V12
This attribute specifies the maximum number of octets which may be included in the information field. The Frame Relay header and CRC octets are not included in this definition. This attribute corresponds to the dN1 parameter described in the Vendor Forum Specification. [1 to 8187] octets 2100
Criticity :
None V12
measurementInterval (t) (FrAtmDlciSpProv) Description :
This attribute specifies the time interval over which rates and burst sizes are measured when rate enforcement is in effect. When rate enforcement is in effect and both committedInformationRate and committedBurstSize have values of zero, this attribute must have a non to zero value. When rate enforcement is not in effect or when committedInformationRate and committedBurstSize have nonzero values, this attribute is ignored.
[0 to 25500] milliseconds 0
Criticity : Comments :
None When committedInformationRate and committedBurstSize have non to zero values, the time interval is internally calculated. In this situation, measurementInterval is ignored, and it does not represent the time interval.
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
415
rateEnforcement (re) (FrAtmDlciSpProv) Description :
V12
This attribute specifies whether rate enforcement is in effect for this user data link connection. When rateEnforcement is on, the CIR and De=1 traffic will be measured and enforced. When rateEnforcement is off, all frames from the user are accepted and no modifications to the frame with respect to the De bit will be made. [on / off] on
Criticity :
None
416
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Appendix A: main procedures between the MS and the PCU
51
APPENDIX A: MAIN PROCEDURES BETWEEN THE MS AND THE PCU

5.1 Proc_1: establishment of uplink TBF
MAX_RACH filter
MS
BTS
BSC
PCU
RACH (CCCH)
IMM. Assign. (AGCH) PACKET RESOURCE REQUEST PACKET UPLINK ASSIGNMENT FIRST PDTCH
Start T3168
Allocator filter (TFI & resources limits)
52
5.2
Proc_2: establishment of uplink TBF during a downlink transfer
MS
PCU
PACKET DOWNLINK ACK/NACK DOWNLINK DATA PACKET UPLINK ASSIGNMENT(S/P=1) PACKET CONTROL ACKNOWLEDGEMENT DOWNLINK DATA DOWNLINK DATA UPLINK DATA Allocator filter (TFI & resources limits)
TBF starting time for the uplick TBF
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
53
5.3
Proc_3: release of an uplink TBF
Start T3182 MS PCU
PDTCH (CV=0) PACKET UPLINK Ack/Nack PDTCH PDTCH PACKET UPLINK Ack/Nack (Final Ack Indicator =1) PACKET CONTROL ACKNOWLEDGEMENT
TBF release
TBF release
54
5.4
Proc_4: release of an uplink TBF with a lost of communication
Start T3182 MS PCU
PDTCH (CV=0) PACKET Uplink Ack/Nack (Final Ack Indicator =1) .......... PACKET Uplink Ack/Nack (Final Ack Indicator =1) N3103Max
Not received by the MS
TBF release
TBF release
Start T3169
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
55
5.5
Proc_5: establishment of a downlink TBF
Start NT1002
MS
BTS
BSC
PCU
IMM. Assignment
BSSGPDLUnitData
PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACKNOWLEDGEMENT (Over 4 bursts ) PACKET TIMING ADVANCE FIRST PDTCH
56
5.6
Proc_6: failure of downlink TBF establishment
MS
BTS
BSC
PCU
Start NT1002
IMM. Assignment
IMM. Assign. Command BSSGPDLUnitData
PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACK. 500 ms PACKET DOWNLINK ASSIGNMENT NBMAXPDASSIGN. PACKET CONTROL ACK.
500 ms PACKET DOWNLINK ASSIGNMENT PACKET CONTROL ACK. TBF release Start NT1001
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
57
5.7
Proc_7: Establishment of downlink TBF during an uplink transfer
MS
PCU
PDTCH PACKET UPLINK ASSIGNMENT (bitmap i+1) PDTCH PDTCH PACKET CONTROL ACKNOWLEDGEMENT Uplink Bitmap i PDTCH PACKET DOWNLINK ASSIGNMENT PDTCH PACKET CONTROL ACKNOWLEDGEMENT PDTCH PDTCH Uplink Bitmap i+1 PDTCH PDTCH Downlink TBF start
58
5.8
Proc_8: release of a downlink TBF
MS
PCU
Start T3191
PDTCH (FBI=1) PACKET DOWNLINK ACK/NACK (FAI=0) PDTCH (FBI=0) PDTCH (FBI=0) PDTCH (FBI=0) PACKET DOWNLINK ACK/NACK (FAI=1) Stop T3191
Start T3193 TBF release Start T3192 TBF release
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Abreviations and definitions
61
ABREVIATIONS AND DEFINITIONS

6.1 Abreviations
A Abis Agprs ARQ BCCH BLER BSC BSS BTS BSSGP CCCH CSx CV DL FBI Gb GGSN Gi Gn GPRS GSL GTP IP LA LAC LAI ETSI generic name for BSSNSS interface ETSI generic name for BSCBTS interface NORTEL specific name for BSCPCU interface Automatic ReQuest for retransmission Broadcast Control CHannel Block Error Rate Base Station Controller Base SubSystem Base Transceiver Station Base Station System GPRS Protocol. Common Control Channel Coding Scheme x Countdown Value DownLink Final Block Indicator ETSI generic name for PCUSGSN interface Gateway GPRS Support Node ETSI generic name for GGSNPDN interface ETSI generic name for SGSNGGSN interface General packet radio service Gprs Signalling Link Gprs Tunneling Protocol Internet Protocol Location Area Location Area Code Location Area Identity
62
LAPD LLC MAC MM MS NS NSAPI NSS O&M OAM OML PACCH PBCCH PCCCH PCM PCU PDCH PDN PDP PDU PDTCH PLMN PSI (15) QoS RA RAC RAI RACH RLC
Link Access Protocol on D channel Logical Link Control Medium Access Control Mobility Management Mobile Station Network Service Network Service Access Point Identifier Network and Switching Subsystem Operation and Maintenance Operation Administration Maintenance OAM Link Packet Associated Control Channel Packet Broadcast Control Channel Packet Common Control Channel Pulse Coded Modulation Packet Control Unit Packet Data Channel Packet Data Network Packet Data Protocol Packet Data Unit Packet Data Traffic Channel Public Land Mobile Network Packet System Information Type 1 to 5 Quality of Service Routing Area Routing Area Code Routing Area Identity Random Access Channel Radio Link Control
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
63
RR RRM RSL SAPI SI SGSN SNDCP TA TAI TBF TCP TDMA TFI TID TLLI TRX TS UL USF WAP
Radio Resources Radio Resources Management Radio Signaling Link Service Access Point Identifier Stall Indicator Serving GPRS Support Node SubNetwork Dependent Convergence Protocol Timing Advance Timing Advance Index Temporary Block Flow Transmission Control Protocol Time Division Multiple Access Temporary Flow Identity Tunnel IDentity Temporary Link Level Identity BTS Transceiver entity Time Slot UpLink Uplink State Flag Wireless Application Protocol
6.1.1
Definitions
Block period: CV (Countdown Value): Multislot Class: ON period: is the sequence of four timeslots on a PDCH used to convey one radio block. indicates in which state the countdown procedure is. indicates the UL and DL capabilities of the Mobile Station. one ON period corresponds to the transfer of information (web page, email, etc) at the GPRS application layer (above IP/X25). one OFF period corresponds to the time between two ON periods.
OFF period:
64
PBCCH:
used to broadcast System Information. If there are GPRS common channels in the cell, then PBCCH is present. Alternatively, the BCCH can be used. The basic idea of PBCCH is to broadcast for GPRS MS all the information needed, that is information related to packet as well as general GSM information. However, the MS needs to monitor BCCH for synchronisation, identification of the cell. is a physical channel dedicated to packet data traffic. In packet idle mode, the mobile station is not allocated any radio resource on a PDCH. It listens to the BCCH and the CCCH. In packet transfer mode, the mobile station is prepared to transfer LLC PDUs on packet data physical. The mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. indicates the RLC Nonacknowledged). Mode (Acknowledged or
PDCH: Packet idle mode:
Packet transfer mode:
RLCMODE: RLCOCTETCOUNT:
indicates the type of TBF (openended or closeended) and eventually the number of bytes to transmit. is a physical connection established between a MS and the network to support the upper layers exchange of information flows. An RR connection is maintained and released by the two peer entities. indicates if the window is stalled.
RR connection:
SI (Stalled Indication):
TBF (Temporary Block Flow): the radio resources allocations are called TBF in GPRS. One TBF is allocated to a GPRS subscriber during the GPRS transfer duration. A TBF corresponds to a set of radio TS (belonging to the same TDMA) allocated to that subscriber and for each TS (in uplink), a bitmap describing the way the subscriber is allowed to transmit its data on that TS, in the time. TBFSTARTINGTIME: TBF abort: indicates when the Bitmap is usable. The term abort as applied to TBF is used when the TBF is abruptly stopped without using the Release of TBF procedures. The term release as applied to TBF is used when the TBF is stopped using one of the Release of TBF procedures. the number that identifies the TBF. delay used to compensate propagation time between the MS and the BTS. is all the duration of one connection for one service.
TBF release:
TFI: Timing Advance: Transaction:
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Index of parameters
A
accounting (ac), 412
B
blockErrorRate, 326 bscGprsActivation, 329 bsCvMax, 36 btsSensitivity, 314 btsSensitivityInnerZone, bts, 322 bvcBlockRetries, 45 bvcBlockUnblockTimer, 45 bvcResetReqRetries, 45 bvcResetReqTimer, 46 bvcUnblockRetries, 46
C
cellReselectHysteresis, 311 channelType, 319 codingScheme, 323 committedBurstSize (bc), 412 committedInformationRate (cir), 413
D
dLPwrValue, 331 drxTimerMax, 313 dwAckTime, 324
E
excessBurstSize (be), 413
F
flowControlMaxRate, 47
G
gprsCellActivation, 311 gprsPermittedAccess, 311 gprsPreemption, 319 gprsPreemptionProtection, 319 gprsPriority, 320
ii
Index of parameters
L
longTbfSizeThreshold, 329
M
maxBsTransmitPowerInnerZone, bts, 322 maxDnTbfP1P2Threshold, 331 maxDnTbfPerTs, 327 maxDwAssign, 31 maximumFrameSize (n203), 414 maxNbrPDAAssig, 31 maxNbrRLCEmptyBlock, 37 maxNbrWithoutVchange, 324 maxRach, 32 maxSize, 326 maxUpTbfP1P2Threshold, 331 maxUpTbfPerTs, 327 measurementInterval (t), 414 minNbrGprsTs, 320 msCapWeightActive, 320 msFlowCntlBucketSize, 47
N
N3103Max, 324 N3105max, 37 nAvgl, 315 nAvgT, 316 nAvgW, 317 nbrFreeTchBeforeAnticipation, 331 nbrFreeTchToEndAnticipation, 331 nsAliveRetries, 41 nsAliveTimer, 41 nsBlockRetries, 42 NsBlockTimer, 42 nsBlockTimer, 42 nsResetRetries, 42 nsResetTimer, 43 nsTestTimer, 43 nsUnblockRetries, 43
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Index of parameters
iii
P
panDec, 37 panInc, 38 panMax, 39
R
raCapabilityUpRetries, 48 raCapabilityUpTimer, 48 radioAllocator, 320 rateEnforcement (re), 415 reserved3, bts, 34 reserved4, bts, 329 resumeRetries, 44, 48 resumeTimer, 44, 49
S
speechOnHoppingTs, 332 suspendRetries, 49 suspendTimer, 49
T
T3172, 34 tsFlowCntlBucketSize (tsBmax), 410 tsLeakRate, 411
U
upAckTime, 325
iv
Index of parameters
PE/DCL/DD/0136 41190010136
Preliminary
12.01/EN
July 2000
GSM/BSS V12
Nortel Networks Wireless Solutions GPRS ACCESS NETWORK PARAMETERS USER GUIDE
Copyright 19962000 Nortel Matra Cellular and Nortel Networks, All Rights Reserved NORTEL NETWORKS AND NORTEL MATRA CELLULAR CONFIDENTIAL: The information contained in this document is the property of Nortel Networks and/or Nortel Matra Cellular. Except as specifically authorized in writing by Nortel Networks and Nortel Matra Cellular, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation, operation and maintenance purposes only. You may not reproduce, represent, or download through any means, the information contained herein in any way or in any form without prior written consent of Nortel Networks and Nortel Matra Cellular. The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL Globemark, HOW THE WORLD SHARES IDEAS. All other brand and product names are trademarks or registred trademarks of their respective holders. Publication Reference PE/DCL/DD/0136 41190010136 12.01/EN July 2000 Printed in France
For more information, please contact: For all countries, except USA: Documentation Department 1, Place des Frres Montgolfier GUYANCOURT 78928 YVELINES CEDEX 9 FRANCE Email : gsmntp@nortelnetworks.com Fax : (33) (1) 39445029 In the USA: 2221 Lakeside Boulevard Richardson TX 75082 USA Tel: 18004 NORTEL 18004667838 or (972) 6845935
Internet Address: http://www.nortelnetworks.com

GPRS Access Network Parameters User Guide: Wireless Service Provider Solutions

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GPRS Access Network Parameters User Guide: Wireless Service Provider Solutions

Uploaded by

Copyright:

Available Formats

Wireless Service Provider Solutions

GPRS Access Network Parameters User Guide

Wireless Service Provider Solutions

GPRS Access Network Parameters User Guide

Nortel Networks Confidential

GPRS Access Network Parameters User Guide

Nortel Networks Confidential

PAGE INTENTIONALLY LEFT BLANK

Nortel Networks Confidential

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Classification of parameters per object . . . . . . . . . . . . . . . . . . . . . . GPRS algorithms and mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS Access Network Parameters User Guide

Nortel Networks Confidential

232 232 232 234 236

DRXmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMCR algorithms parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCUSN OAM algorithm parameters . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A: main procedures between the MS and the PCU . .

Abreviations and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Nortel Networks Confidential

GPRS Access Network Parameters User Guide

Nortel Networks Confidential

PAGE INTENTIONALLY LEFT BLANK

Nortel Networks Confidential

About this document

ABOUT THIS DOCUMENT

GPRS Access Network Parameters User Guide

About this document

Nortel Networks Confidential

How this document is organized

Nortel Networks Confidential

Classification of parameters per object

CLASSIFICATION OF PARAMETERS PER OBJECT

GPRS Access Network Parameters User Guide

Classification of parameters per object

Nortel Networks Confidential

Nortel Networks Confidential

Classification of parameters per object

GPRS Access Network Parameters User Guide

Classification of parameters per object

Nortel Networks Confidential

Nortel Networks Confidential

GPRS algorithms and mechanisms

GPRS ALGORITHMS AND MECHANISMS

GPRS Access Network Parameters User Guide

GPRS algorithms and mechanisms

Nortel Networks Confidential

BSS HLR GPRS BSS Datafill SGSN PCU

GPRS NSS GGSN

Nortel Networks Confidential

GPRS algorithms and mechanisms

GPRS protocol stack

GPRS Protocol Stack Description

GPRS Access Network Parameters User Guide

GPRS algorithms and mechanisms

Nortel Networks Confidential

PDU transmission RA updates Paging

MM State Model of MS ( with SIM card)

Nortel Networks Confidential

GPRS algorithms and mechanisms

GPRS Access Network Parameters User Guide

GPRS algorithms and mechanisms