ALU GPRS Radio Resource Management

d o c u m e n t, u s e a n d c o m m u n ic a tio n o f its c o n te n ts
n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.
A ll r ig h ts r e s e r v e d . P a s s in g o n a n d c o p yin g o f th is
Site
VELIZY
MOBILE COMMUNICATION DIVISION

GPRS Radio Interface
RRM sub-layer
Originator(s)
SYT
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
Alcatel 900/BSS
PRODUCT DEFINITION
SYS-TLA
SYSTEM FUNCTIONAL BLOCKS
Internal :
External :
PREDISTRIBUTION:
MCD/TD Vlizy:
L. Cruchant
JY Amaudrut
S.Bourdeaut
E. Desorbay
R. Forni
PJ Pietri
M. Wu
P. Dupuy
S. Baudet
J. Guinand
T. Donzel (CNS)
M. Freynet (CNS)
G. Linden (CNS)
R. Bialobroda (BTS)
M. Delprat (BTS)
JP Humeau (BTS)
B. De Jaeger
P. Godin
MCD/TD Kontich:
G. Van Dijck
JL Carpentier
Y. Vereecke
MCD/TD Kaisemer:
MCD/TD Zuffenhausen:
R. Goedecker
PREDISTRIBUTION: DOC. CENTRES

MCD VELIZY
B. Marliac
MCD STUTTGART
I. Lentzsch
MCD ANTWERP
L. Van Eyck
ABSTRACT
This document describes the RRM protocol between the MFS and the MS, for GPRS B6.2.
Name
D.Berthoumieux
M. Bialobroda
AM
CNS
App.
Name
App.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
REVIEW
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Not applicable
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
HISTORY
Ed.01
In Preparation 01
Ed.01
In Preparation 02
Ed.01
In Preparation 03
15/04/98
Document creation
28/05/98
Working meeting minutes : see TD/SAS/bla/80775.98
29/07/98
Ed.01
Proposal 01
24/08/98
Ed.01
Proposal 02
21/09/98
Ed. 01
Proposal 03
Ed. 02
Proposal 01
Ed. 02
Proposal 02
Ed. 02
Proposal 03
Ed. 02
Proposal 04
09/10/98
Radio Resource algorithm, PCC & PAG & PRH FSM, Gb

congestion control are specified.
Working meeting minutes : see TD/ST/bla/80949.98
Remarks of last working group meeting are taken into account.
PRH FSM, System Information PDUs, NTM Ater circuits
management are not described.
Some Pilot features are also not yet covered.
MCD/TD/SYT/bla/81054.98
Remarks of last review meeting are taken into account.
Simplification on QoS
Introduction of PRH FSM.
Some Pilot features are also not yet covered.
MCD/TD/SYT/bla/81087.98
Remarks of last review meeting are taken into account.
21/10/98
Document updated for GPRS pilot & step 1.
xx/11/98
Document updated after review, see minutes in

TD/SYT/JPJ/81113.98
Document updated after review, see minutes in TD/SYT/JPJ/81195
Ed. 02
Proposal 04
Ed.02
Released
Ed.03
Proposal 01
31/05/99

TD/SYT/JPJ/81250. Aligned on BSCGP specification, ed.2
proposal 03.
22/06/99
25/06/99
Ed.03
Proposal 02
09/07/99
Ed.03 Released
19/04/15
Ed 04 Proposal
01
01/12/99
Document updated for B6.2 SMG29 BSS :

- Support of the Master PDCH feature
- Uplink congestion control
- Bandwidth capacity reduction
- SMG#29 impacts
- Document updated after review, see minutes in
TD/SYT/BLA/90414,
- Inclusion of extracts of technical note 99611 (Marc Freynet) and
extracts of technical note 90418_1 (Stanislas Bourdeaut), about
PSI3 and PSI3bis coding
TD/SYT/SBO/90460
The following CRs are taken into account:
- 057386
- 057672
- 057929
- 058457
- 059220
- 059616
- 061866
- 062827
- 062852
- 064475
- 065474
- 066001
ED
MCD
11/12/98
15/01/99
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
INTERNAL REFERENCED DOCUMENTS

[i1]
[i2]
[i3]
3BK 10204 0438 DTZZA

3BK 10204 0433 DTZZA
3BK 10204 0467 DTZZA
TFD: General Packet Radio Service

TFD: Multi-BSS Fast packet Server
GPRS BSS technical feature list
FOR INTERNAL USE ONLY

By derogation to the QS recommendation (see document 8BL 14106 0000 BGZZA - TD
documentation layout) more than three levels used in the table of contents with agreement of the
PQE.
END OF DOCUMENT
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS
HISTORY............................................................................................................................................... 8
REFERENCED DOCUMENTS............................................................................................................. 8
RELATED DOCUMENTS..................................................................................................................... 9
PREFACE........................................................................................................................................... 10
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1. OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER......................................
1.2 Overview description of layer services.....................................................................................

1.2.1 Services provided by (RRM) layer..........................................................................................
1.2.2 Services required from (RLC) layer........................................................................................
1.2.3 Services required from (BSCGP) layer...................................................................................
1.2.4 Services required from (BSSGP) layer...................................................................................
1.1 Layer location..............................................................................................................................
1.3 Overview description of layer protocol.....................................................................................

1.3.1 Layer procedures....................................................................................................................
1.3.2 GPRS multiplexing principles.................................................................................................
1.3.2.1 Temporary Block Flow....................................................................................................
1.3.2.2 Temporary Flow Identity..................................................................................................
1.3.2.3 Medium access modes...................................................................................................
1.3.3 Master PDCH..........................................................................................................................
1.3.4 GPRS MS behaviour...............................................................................................................
1.3.4.1 MS class mode of operation...........................................................................................
1.3.4.2 Network modes of operation...........................................................................................
1.3.4.3 System information reading............................................................................................
1.3.4.4 Cell reselection...............................................................................................................
1.3.4.5 MS Radio Resource state...............................................................................................
1.3.4.6 Channels listened by the MS..........................................................................................
1.3.4.7 GPRS traffic interruption, in a cell..................................................................................
1.3.4.8 GPRS access in the cell and Overload control...............................................................
1.3.5 Quality of Service Management..............................................................................................
1.3.5.1 QoS parameters.............................................................................................................
1.3.5.2 BSS behaviour related to QoS in B6.2...........................................................................
2. PROTOCOL LAYER STRUCTURE...........................................................................

2.1 Overview of layer functional model...........................................................................................
2.2 Overview of layer interfaces.......................................................................................................
3. SERVICE PRIMITIVES DEFINITION.........................................................................

3.1 Primitives provided to Layer Management Plane.....................................................................
3.2 List of service primitives used by the layer..............................................................................
3.2.1 Service primitives used from (RLC) layer...............................................................................
3.2.2 Service Primitives used from (BSSGP) layer.........................................................................
3.2.3 Service Primitives used from (BSCGP) layer.........................................................................
3.3 Detailed description of service primitives provided by the layer...........................................
3.3.1 Service primitives provided to Layer Management entity.......................................................
3.3.1.1 LM-BSS-CREATE-req....................................................................................................
3.3.1.2 LM-BSS-CREATE-cnf.....................................................................................................
3.3.1.3 LM-BSS-DELETE-req.....................................................................................................
3.3.1.4 LM-BSS-DELETE-cnf.....................................................................................................
3.3.1.5 LM-BSS-GET-req...........................................................................................................
3.3.1.6 LM-BSS-GET-cnf............................................................................................................
3.3.1.7 LM-BSS-STATE-CHANGE-ind.......................................................................................
3.3.1.8 LM-BSS-SET-req............................................................................................................
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.9 LM-BSS-SET-cnf............................................................................................................
3.3.1.10 LM-CELL-CREATE-req.................................................................................................
3.3.1.11 LM-CELL-CREATE-cnf.................................................................................................
3.3.1.12 LM-CELL-DELETE-req.................................................................................................
3.3.1.13 LM-CELL-DELETE-cnf.................................................................................................
3.3.1.14 LM-CELL-SET-req........................................................................................................
3.3.1.15 LM-CELL-SET-cnf........................................................................................................
3.3.1.16 LM-CELL-GET-req........................................................................................................
3.3.1.17 LM-CELL-GET-cnf........................................................................................................
3.3.1.18 LM-CELL-State-Change-ind.........................................................................................
3.3.1.19 LM-GIC-Group-CREATE-req........................................................................................
3.3.1.20 LM-GIC-Group-CREATE-cnf........................................................................................
3.3.1.21 LM-GIC-Group-DELETE-req........................................................................................
3.3.1.22 LM-GIC-Group-DELETE-cnf.........................................................................................
3.3.1.23 LM-GIC-Group-GET-req...............................................................................................
3.3.1.24 LM-GIC-Group-GET-cnf...............................................................................................
3.3.1.25 LM-GIC-Group-State-Change-ind.................................................................................
4. DEFINITION OF LAYER PROTOCOL.......................................................................

4.1 Peer to peer protocol description..............................................................................................
4.1.1 Protocol definition...................................................................................................................
4.1.2 Packet connection control.......................................................................................................
4.1.2.1 One phase access UL TBF establishment initiated by MS in packet idle mode on
PCCCH.......................................................................................................................................
CCCH.........................................................................................................................................
4.1.2.3 Two phase access UL TBF establishment initiated by MS in packet idle on PCCCH.....
4.1.2.4 Two phase access UL TBF establishment initiated by MS in packet idle on CCCH.......
4.1.2.5 UL TBF establishment initiated by MS in packet transfer mode.....................................
4.1.2.6 UL TBF resources modification initiated by MS..............................................................
4.1.2.7 DL TBF establishment initiated by network for MS in packet idle mode on PCCCH......
4.1.2.8 DL TBF establishment initiated by network for MS in packet idle mode on CCCH........
4.1.2.9 DL TBF establishment initiated by network for MS in packet transfer mode..................
4.1.3 Paging.....................................................................................................................................
4.1.3.1 PS or CS Paging procedure for MS in packet idle mode when there is a MPDCH........
4.1.3.2 PS or CS Paging procedure for MS in packet idle mode when there is no MPDCH......
4.1.3.3 CS Paging procedure for MS in packet transfer mode...................................................
4.1.4 Packet radio resource handling...............................................................................................
4.1.4.1 Packet PDCH Release...................................................................................................
4.1.4.2 Packet System Information provisioning (B6.2 SMG29)................................................
4.2 PDU definition..............................................................................................................................
4.2.1 PDU description......................................................................................................................
4.2.2 Information Element description.............................................................................................
4.3 Protocol error handling...............................................................................................................
5. LAYER DYNAMIC MODEL........................................................................................

5.1 Inter-entities communication.....................................................................................................
5.1.1 Packet connection control.......................................................................................................
5.1.1.1 One phase access UL TBF establishment on CCCH......................................................
5.1.1.2 One phase access UL TBF establishment on PCCCH or PACCH..................................
5.1.1.3 2 phase access UL TBF establishment on CCCH..........................................................
5.1.1.4 2 phase access UL TBF establishment on PCCCH.......................................................
5.1.1.5 DL TBF establishment on CCCH....................................................................................
5.1.1.6 DL TBF establishment on PCCCH/PACCH.....................................................................
5.1.1.7 One phase access contention resolution........................................................................
5.1.1.8 Coding scheme adaptation notification...........................................................................
5.1.1.9 DL TBF Release initiated by (RRM) PRH.......................................................................
5.1.1.10 UL TBF Release initiated by (RRM) PRH.....................................................................
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.11 DL TBF Release initiated by (RLC)...............................................................................

5.1.1.12 UL TBF Release initiated by (RLC)...............................................................................
5.1.2 Packet radio resource handling...............................................................................................
5.1.2.1 PDCH dynamic allocation...............................................................................................
5.1.2.2 PDCH dynamic deallocation...........................................................................................
5.1.2.3 MPDCH dynamic allocation (B6.2 SMG29)....................................................................
5.1.2.4 MPDCH dynamic deallocation (B6.2 SMG29)................................................................
5.1.2.5 PDCH establishment......................................................................................................
5.1.2.6 PDCH release.................................................................................................................
5.1.3 Data transfer...........................................................................................................................
5.1.3.1 DL LLC PDU transfer......................................................................................................
5.1.3.2 Receipt of an invalid DL LLC PDU.................................................................................
5.1.3.3 DL LLC PDU deletion......................................................................................................
5.1.3.4 DL TBF flow control with RLC.........................................................................................
5.1.3.5 DL TBF termination notification......................................................................................
5.1.3.6 DL LLC transfer with RLC mode modification................................................................
5.1.3.7 UL LLC PDU transfer......................................................................................................
5.1.3.8 Flush procedure..............................................................................................................
5.1.3.9 MS Flow Control procedure (not in Pilot)........................................................................
5.1.3.10 BVC Flow Control procedure........................................................................................
5.1.4 CS or PS Paging.....................................................................................................................
5.1.5 Network Management.............................................................................................................
5.1.5.1 BSS creation...................................................................................................................
5.1.5.2 BSS lock.........................................................................................................................
5.1.5.3 BVC-SIG failure/recovery...............................................................................................
5.1.5.4 Cell creation....................................................................................................................
5.1.5.5 Cell unlock......................................................................................................................
5.1.5.6 Cell lock..........................................................................................................................
5.1.5.7 Gb failure/recovery.........................................................................................................
5.1.5.8 Unavailability notification from BSC...............................................................................
5.1.5.9 LAC/CI modification........................................................................................................
5.1.5.10 BSS reset......................................................................................................................
5.1.5.11 Cell RESET...................................................................................................................
5.1.5.12 No response from the BSC...........................................................................................
5.2 PAG Entity detailed description.................................................................................................
5.2.1 CS Paging...............................................................................................................................
5.2.2 PS Paging...............................................................................................................................
5.2.3 Activation / Deactivation of the MPDCH.................................................................................
5.3 PCC Entity detailed description.................................................................................................
5.3.1 Packet connection establishment............................................................................................
5.3.1.1 UL packet connection establishment..............................................................................
Request type...............................................................................................................................
RLC mode..................................................................................................................................
5.3.1.2 DL packet connection establishment..............................................................................
5.3.1.3 Activation / Deactivation of the MPDCH.........................................................................
5.3.2 Packet connection modification..............................................................................................
5.3.2.1 MS requested modification of UL TBF............................................................................
5.3.2.2 Network decided coding scheme adaptation..................................................................
5.3.2.3 TLLI notification by RLC.................................................................................................
5.3.2.4 TLLI modification by SGSN............................................................................................
5.3.2.5 DL TBF modification.......................................................................................................
5.3.3 Packet connection release......................................................................................................
5.3.4 SDL diagrams..........................................................................................................................
5.3.4.1 Downlink.........................................................................................................................
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.4 TRN Entity detailed description.................................................................................................

5.4.1 DL LLC PDU transfer..............................................................................................................
5.4.1.1 DL Packet connection control.........................................................................................
5.4.1.2 DL PDU storage..............................................................................................................
5.4.1.3 DL LLC PDU lifetime expiry............................................................................................
5.4.1.4 DL LLC PDU Flush.........................................................................................................
5.4.1.5 DL congestion control.....................................................................................................
5.4.2 UL LLC PDU transfer..............................................................................................................
5.3.4.2 Uplink..............................................................................................................................
5.5 PRH Entity detailed description.................................................................................................

5.5.1 Packet System Information management (B6.2 SMG29).......................................................
5.5.1.1 Broadcast of GPRS System Information on BCCH........................................................
5.5.1.2 Broadcast of Packet System Information on PBCCH.....................................................
5.5.1.3 Broadcast of Packet System Information on PACCH.....................................................
5.5.2 Packet radio resources management......................................................................................
5.5.2.1 Packet radio resources allocation...................................................................................
5.5.3 PDCH resource control..........................................................................................................
5.5.3.1 Inputs of reservation algorithm......................................................................................
5.5.3.2 Initial PDCH allocation...................................................................................................
5.5.3.3 Reservation of 1 UL block.............................................................................................
5.5.3.4 Reservation of multiple blocks with dynamic PDCH allocation.....................................
5.5.3.5 Examples of reservation of multiple blocks...................................................................
5.5.3.6 Allocation request procedure..........................................................................................
5.5.3.7 Dynamic deallocation.....................................................................................................
5.5.3.8 Multi requests handling (B6.2 SMG29)..........................................................................
5.5.3.9 Allocation / Deallocation of the MPDCH.........................................................................
5.5.4 UL congestion control..............................................................................................................
5.5.5 NSE capacity bandwidth adaptation........................................................................................
5.6 NTM Entity detailed description.................................................................................................
5.6.1 Functions description..............................................................................................................
5.6.1.1 Managed entities............................................................................................................
5.6.1.2 Performance Monitoring.................................................................................................
6. SYSTEM PARAMETERS...........................................................................................
6.1 System dimensioning parameters.............................................................................................
6.2 Timers...........................................................................................................................................
6.3 Other parameters.........................................................................................................................
7. ANNEX 1....................................................................................................................
8. GLOSSARY................................................................................................................
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
TABLE OF FIGURES
FIGURE 1 : RRM LAYER LOCATION.....................................................................................................
FIGURE 2 : QUALITY OF SERVICE LEVELS........................................................................................
FIGURE 3 RRM INTERFACES...............................................................................................................
FIGURE 4 : 1 PHASE ACCESS UL TBF ESTABLISHMENT BY MS IN PACKET IDLE MODE ON
PCCCH............................................................................................................................................
CCCH...............................................................................................................................................
PCCCH............................................................................................................................................
CCCH...............................................................................................................................................
FIGURE 8 : UL TBF ESTABLISHMENT BY MS IN PACKET TRANSFER MODE..................................
FIGURE 9 : UL TBF RESOURCES MODIFICATION BY MS..................................................................
FIGURE 10 : DL TBF ESTABLISHMENT FOR MS IN PACKET IDLE MODE ON PCCCH....................
FIGURE 11 : DL TBF ESTABLISHMENT FOR MS IN PACKET IDLE MODE ON CCCH.......................
FIGURE 12 : DL TBF ESTABLISHMENT FOR MS IN PACKET TRANSFER MODE.............................
FIGURE 13 : PS OR CS PAGING FOR MS IN PACKET IDLE MODE IN CELL WITH MPDCH............
FIGURE 14 : PS OR CS PAGING FOR MS IN PACKET IDLE MODE IN CELL WITHOUT MPDCH.....
FIGURE 15 : CS PAGING FOR MS IN PACKET TRANSFER MODE....................................................
FIGURE 16 : PACKET PDCH RELEASE PROCEDURE........................................................................
FIGURE 17 : PACKET SYSTEM INFORMATION BROADCAST PROCEDURE....................................
FIGURE 18 : ONE PHASE ACCESS UL TBF ESTABLISHMENT ON CCCH - NOMINAL SCENARIO.
FIGURE 19 : ONE PHASE ACCESS UL TBF ESTABLISHMENT ON CCCH - ERROR SCENARIO.....
FIGURE 20 : ONE PHASE ACCESS UL TBF ESTABLISHMENT ON PCCCH/PACCH - NOMINAL
SCENARIO......................................................................................................................................
FIGURE 21 : ONE PHASE ACCESS UL TBF ESTABLISHMENT ON PCCCH/PACCH - ERROR
SCENARIO......................................................................................................................................
FIGURE 22 : 2 PHASE ACCESS UL TBF ESTABLISHMENT ON CCCH NOMINAL SCENARIO......
FIGURE 23 : 2 PHASE ACCESS UL TBF ESTABLISHMENT ON PCCCH NOMINAL SCENARIO....
FIGURE 24 : DL TBF ESTABLISHMENT ON CCCH NOMINAL SCENARIO......................................
FIGURE 25 : DL TBF ESTABLISHMENT ON PCCCH/PACCH NOMINAL SCENARIO.......................
FIGURE 26 : ONE PHASE ACCESS CONTENTION RESOLUTION SCENARIO.................................
FIGURE 27 : CODING SCHEME ADAPTATION NOTIFICATION..........................................................
FIGURE 28 : DL TBF RELEASE SCENARIO INITIATED BY (RRM) PRH.............................................
FIGURE 29 : UL TBF RELEASE SCENARIO INITIATED BY (RRM) PRH.............................................
FIGURE 30 : DL TBF RELEASE SCENARIO INITIATED BY (RLC).......................................................
FIGURE 31 : UL TBF RELEASE SCENARIO INITIATED BY (RLC).......................................................
FIGURE 32 : PDCH DYNAMIC ALLOCATION SCENARIO, SUCCESSFUL CASE...............................
FIGURE 33: PDCH DYNAMIC ALLOCATION SCENARIO, UNSUCCESSFUL CASE...........................
FIGURE 34 : PDCH DYNAMIC DEALLOCATION SCENARIO, SUCCESSFUL CASE..........................
FIGURE 35: PDCH DYNAMIC DEALLOCATION SCENARIO, UNSUCCESSFUL CASE......................
FIGURE 36 : MPDCH DYNAMIC ALLOCATION SCENARIO.................................................................
FIGURE 37 : MPDCH DYNAMIC DEALLOCATION SCENARIO............................................................
FIGURE 38 : PDCH ESTABLISHMENT SCENARIO..............................................................................
FIGURE 39 : PDCH RELEASE SCENARIO...........................................................................................
FIGURE 40 : DL LLC PDU TRANSFER SCENARIO..............................................................................
FIGURE 41 : RECEIPT OF AN INVALID DL LLC PDU SCENARIO.......................................................
FIGURE 42 : DL LLC PDU DELETION SCENARIO...............................................................................
FIGURE 43 : DL TBF FLOW CONTROL WITH RLC SCENARIO..........................................................
FIGURE 44 : DL TBF TERMINATION SCENARIO.................................................................................
FIGURE 45 RLC MODE MODIFICATION (CURRENT MODE IS UNACKNOWLEDGED MODE).........
FIGURE 46 RLC MODE MODIFICATION (CURRENT MODE IS ACKNOWLEDGED MODE)..............
FIGURE 47 : UL LLC PDU TRANSFER SCENARIO..............................................................................
FIGURE 48 : FLUSH SCENARIO...........................................................................................................
FIGURE 49 : MS FLOW CONTROL SCENARIO...................................................................................
FIGURE 50 : BVC FLOW CONTROL SCENARIO.................................................................................
FIGURE 51 : CS OR PS PAGING SCENARIO.......................................................................................
FIGURE 52 BSS CREATION SCENARIO (ADMINISTRATIVE STATE = LOCKED)..............................
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
ED
MCD
53 BSS LOCK SCENARIO.......................................................................................................

54 CELL CREATION SCENARIO (ADMINISTRATIVE STATE = LOCKED)............................
55 CELL UNLOCK SCENARIO (MPDCH SUPPORTED)........................................................
56 CELL UNLOCK SCENARIO (MPDCH NOT SUPPORTED)................................................
57 CELL LOCK SCENARIO (MPDCH SUPPORTED)..............................................................
58 CELL LOCK SCENARIO (MPDCH NOT SUPPORTED).....................................................
59 GB FAILURE/RECOVERY SCENARIO...............................................................................
60 BSC UNAVAILABILITY NOTIFICATION SCENARIO (WITH MPDCH)...............................
61 BSC UNAVAILABILITY NOTIFICATION SCENARIO (WITHOUT MPDCH)........................
62 LAC/CI MODIFICATION SCENARIO (WITH MPDCH).......................................................
63LAC/CI MODIFICATION SCENARIO (WITHOUT MPDCH).................................................
64 BSS RESET SCENARIO.....................................................................................................
65 CELL RESET SCENARIO...................................................................................................
66 BSC NO-RESPONSE SCENARIO......................................................................................
67 : GB CONGESTION CONTROL AT SGSN (1/2).................................................................
68 : GB CONGESTION CONTROL AT SGSN (2/2).................................................................
69 FREQUENCY OF SENDING BVC_FLOW_CONTROL PDU..............................................
70 FREQUENCY OF SENDING MS_FLOW_CONTROL PDU................................................
71 NEIGHBOUR CELL PARAMETERS STRUCTURE.............................................................
72 PSI HANDLING INTERFACE (WITH MPDCH)...................................................................
74 ACC_CONTR_CLASS (PSI1) AND CELL_BAR_ACCESS2 (PSI3) PROCESSING...........
75 MPDCH ACTIVATION (AT CELL ACTIVATION, BSCGP SUPPORTED).............................
76 MPDCH ACTIVATION (AT NMO MODIFICATION)..............................................................
77 MPDCH DEACTIVATION (AT CELL DEACTIVATION)........................................................
78 MPDCH DEACTIVATION (AT NMO MODIFICATION)........................................................
79 PSI HANDLING INTERFACE (WITHOUT A MPDCH)........................................................
80 SI13/PSI13 SYNCHRONISATION.......................................................................................
81 SI13/PSI13 SYNCHRONISATION (MS IN PACKET TRANSFER MODE)..........................
82: EXAMPLE OF ALLOCATED PDCHS.................................................................................
83: EXAMPLE OF INITIAL PDCH ALLOCATION.....................................................................
84: PARAMETERS CALCULATED FOR DYNAMIC ALLOCATION.........................................
85: QUEUING OF DOWNLINK REQUEST..............................................................................
86: MFS DECISION PROCESS FOR GPRS ASSIGNMENT..................................................
87 DYNAMIC DEALLOCATION................................................................................................
88: EXAMPLE OF "SOFT" PRE-EMPTION DECISION...........................................................
89 ENTITY RELATIONSHIP DIAGRAM...................................................................................
90 BSS/CELL STATE RELATIONSHIP.....................................................................................
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
HISTORY
Ed. 01 Document creation for GPRS Demonstrator

Ed. 02 Document updated for GPRS Pilot and BSS SMG28 BSS
Ed. 03 Document updated for BSS SMG29 BSS
REFERENCED DOCUMENTS
Alcatel references
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]
[16]
[17]
[18]
19
3BK 11202 0256 DSZZA

3BK 11202 0257 DSZZA
3BK 11202 0260 DSZZA
3BK 11202 0264 DSZZA
3BK 11202 0263 DSZZA
3BK 11202 0262 DSZZA
3BK 11202 0258 DSZZA
3BK 11202 0259 DSZZA
3BK 11202 0266 DSZZA
3DC 25176 0001 FLZZA
3DC 25176 0001 FLZZA
3BK 11202 0199 DSZZA
3BK 11202 0267 DSZZA
3BK 11203 0055 DSZZA
3BK 10204 0467 DTZZA
3BK 10202 0279 DSZZA
3BK 10202 0222 DSZZA
3BK 10202 0271 DSZZA
3BK 10204 02228 DSZZA
FBS GPRS telecom presentation

FBS GPRS Gb interface BSSGP Layer
FBS GPRS MFS-BSC interface BSCGP Layer
FBS GPRS Radio Interface RLC SUBLAYER
FBS GPRS Radio Interface MAC SUBLAYER
FBS GPRS MFS-BTS interface GCH stack
FBS GPRS Gb interface Network Service Control Sublayer
FBS GPRS Gb interface Sub-Network Service Sublayer
FBS GPRS Radio Interface Physical link layer
GPRS marketing requirements
TBF BSS GPRS feature list
System information management
BSS telecom parameters
GPRS traffic model and performances
GPRS BSS Feature List
Application document 04.60
Application document 04.08
Resource Allocation and Management
GPRS counter catalogue
GSM references
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
[A]
GSM 02.60
[B]
GSM 03.60
[C]
GSM 03.64
[D]
GSM 04.60
[E]
GSM 04.08
[F]
GSM 08.18
[G]
GSM 05.02
[H]
GSM 05.08
[I]
GSM 05.10
Digital cellular telecommunications system (Phase2+)

General Packet Radio Services (GPRS)
Service description
Stage 1
Service description
Stage 2
Overall description of the GPRS radio interface
Stage 2
Mobile Station (MS) Base Station System (BSS) interface
Radio Link Control / Medium Access Control (RLC/MAC)
protocol
Mobile radio interface layer 3 specification
Base Station System (BSS) - Serving GPRS Support Node
(SGSN) interface; BSS GPRS Protocol (BSSGP)
Digital cellular telecommunications system
GSM Radio Access Phase 3
Multiplexing and multiple access on the radio path
Radio subsystem link control
Radio subsystem synchronisation
The applicable versions of ETSI Technical Specifications are defined in [15].
RELATED DOCUMENTS
[R1]
ED
MCD
AA-CRC/RD/Na/GSM/JBr
/1088/98 version 2.0
GPRS Radio Resource Allocation Part III : Comparison of

several Reservation / Polling strategies for GPRS (errorless
channel)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
PREFACE
The aim of this document is to give a system description of the RRM layer within the MFS, for B6.2.
This document describes the different functions of RRM layer.
It also describes the primitives used on the interface with LM entity. The primitives used on the
interface with RLC, BSCGP and BSSGP are not described, they are respectively described in 4, 3
and 2.
As this document is a system document, implementation is not constrained by the architecture and
primitives described in this document.
The edition 3 of the document is applicable to GPRS Pilot BSS, SMG28 BSS and SMG29 BSS, with
the exception that the coding of the radio interface PDUs is SMG#29 compliant. Refer to the edition
2 for the SMG#28 compliant coding.
Restrictions are indicated when a feature is not part of GPRS Pilot or SMG28 BSS. They are also
explicitly described in 15.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.
OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER
1.1
Layer location
Layer Management Plane
MS
User & control Plane

LLC
BSC
relay
SGSN
relay
RRM
RRM
RRM
MFS
BSSGP
RLC
Radio
interface
RLC
BSCGP
NS
MAC
Physical
Layer
MAC
L2-GSL
L1-GSL
L2-GCH
L1-GCH
Gb
L1-Gb
Figure 1 : RRM layer location
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.2
Overview description of layer services
1.2.1 Services provided by (RRM) layer
Packet connections establishment or modification

transfer of LLC PDU from SGSN to MS or from MS to SGSN
PS or CS paging of mobile stations
1.2.2 Services required from (RLC) layer
Establishment, maintenance and release of TBF contexts

LLC PDU segmentation/reassembly and transfer in acknowledged or unacknowledged
mode
Signalling transfer towards (MAC) layer for :
packet connection establishment or packet connection resource modification over PCCCH or
PACCH
PS and CS Paging transfer over PCCCH or PACCH
reservation of PDCH resources to packet connection
broadcast of system information over PBCCH
1.2.3 Services required from (BSCGP) layer
signalling transfer over CCCH for packet connection establishment

PS and CS Paging transfer over CCCH
allocation / deallocation of PDCH
allocation / deallocation of MPDCH
GPRS radio resource management
1.2.4 Services required from (BSSGP) layer
ED
MCD
LLC PDU transfer towards SGSN

flow control per mobile or per cell
notification to SGSN of discarded or invalid PDU
notification to SGSN of MS communication failures
BVC control procedures (reset, block/unblock)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3
Overview description of layer protocol
1.3.1 Layer procedures

The following procedures are defined between mobiles and the MFS at (RRM) protocol level :
packet connection establishment, packet contention resolution and packet connection
resources modification (that procedure may be invoked by the MS but the BSS does not
change the QoS previously granted to a TBF)
provisioning of GPRS system parameters
PS and CS paging
Notification of PDCH release to MS
Additionally at network side, the (RRM) layer defines procedures related to :
packet connection control :
packet connection release
radio resource management
allocation / deallocation of radio resources to packet connections
monitoring of GPRS traffic needs and dynamic allocation of PDCH
data transfer :
transfer of LLC PDU
DL flow control to enslave SGSN with cell or mobile actual radio throughput
UL congestion control procedure to recover a Gb congestion
DL flow control procedure with RLC layer
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.2 GPRS multiplexing principles

A PDCH can be shared by several MSs.
A TBF can be allocated on several PDCHs.
1.3.2.1 Temporary Block Flow
A Temporary Block Flow (TBF) is a physical connection used by two (RRM) entities to support the
unidirectional transfer of LLC PDU on packet data physical channels. The TBF is allocated radio
resource on one or more PDCH and comprises a number of RLC/MAC data or control blocks
carrying one or more LLC PDU. A TBF is temporary and is maintained only for the duration of the
data transfer.
Only one TBF may be established per MS, per direction and per PDCH group (i.e. per cell in B6.2); a
MS may be assigned two concurrent TBF (1 TBF per direction).
1.3.2.2 Temporary Flow Identity
Each TBF is assigned a Temporary Flow Identifier (TFI) by the network. The TFI is unique in the
PDCH group (i.e. the cell, in B6.2) among concurrent TBF in each direction (uplink or downlink). The
same TFI value may be used concurrently for TBF in opposite directions.
1.3.2.3 Medium access modes
Three medium access modes are supported by the radio protocol :
-
dynamic allocation, characterised by USF allocation for UL TBF

extended dynamic allocation, where the MS may be assigned several UL radio blocks when
detecting its USF on one DL radio block
fixed allocation, where MS is assigned bitmap indicating the number of radio blocks assigned to
it
MS shall support dynamic allocation and fixed allocation methods. Extended dynamic allocation is
an optional feature for MS.
Network shall support either dynamic allocation or fixed allocation methods. Extended dynamic
allocation is an optional feature for network. The dynamic allocation method has been chosen for
B6.2 product.
Refer to 5 for dynamic allocation detailed description.
1.3.3 Master PDCH

A specific additional signalling channel designated as MPDCH (Master Packet Data Channel) has
been defined in the standard to allow high GPRS traffic.
The MPDCH supports both the PBCCH (Packet Broadcast Control Channel) and PCCCH (Packet
Common Control Channel) on a dedicated radio timeslot. The interest of PBCCH is to introduce
specific GPRS dedicated cell reselection mechanisms. The interest of PCCCH is to allow high GPRS
signalling traffic that cannot be handled by GSM CCCH. In addition, the use of PCCCH reduces the
BSC and GSL loads in the Alcatel architecture.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The presence or not of a MPDCH in a cell is indicated through the system information broadcast on
the BCCH channel. When present, any GPRS MS (whatever its class mode of operation) shall listen
to it and is no longer required to listen to the BCCH. As the GPRS MS may also invoke circuit
switched services, few circuit switched service parameters are broadcast on the PBCCH. The
PCCCH channel is then used to establish a TBF or to convey paging messages for GPRS MS in idle
mode.
In the current release, the following restrictions are defined :
Only 1 PCCCH may be activated per cell.
The MPDCH allocation is decided by O&M, i.e. there is no dynamic MPDCH allocation
based on signalling load assumptions. The operator configures on-line the Network Mode of
Operation of the BSS (NMO I, II or III) and the presence or absence of a MPDCH.
If NMO is set to I or III AND MIN_MPDCH = 1, RRM shall dynamically allocate a MPDCH
channel.
Otherwise (NMO is II OR MIN_MPDCH = 0), RRH shall dynamically deallocate the MPDCH
if any.
There is no optimization of the cell reselection procedure duration, i.e. the information
broadcasted by the serving cell only contain static information related to the neighbour
cells: one MS entering the reselection procedure has to listen the target cell BCCH before
decoding the target cell PBCCH. Moreover the PACKET PSI STATUS procedure defined in
[D] is not supported.
The GPRS adjacencies are set equal to the GSM adjacencies, i.e. the BA(PBCCH) is equal
to the BA(BCCH). It is expected that the GPRS service is available in all cells of the
operator network.
There is no PRACH dynamic load control, i.e. the persistence level broadcast in the cell
does only take into account the static operator configuration.
There is no queuing of the packet uplink accesses on the PRACH.
Only the normal page mode is supported on the MPDCH, i.e. there is no paging
reorganisation.
The same downlink power level is used on the BCCH, PBCCH and all PDCHs.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4 GPRS MS behaviour

1.3.4.1 MS class mode of operation
Three MS class modes of operation are defined within ETSI Technical Specifications :
- class A:
supports simultaneously GPRS and circuit switched services
- class B:
supports simultaneous attach, but not simultaneous traffic
- class C:
supports only non-simultaneous attach
1.3.4.2 Network modes of operation
The network may provide coordination for paging CS and PS.
Paging coordination means that the network sends paging CS messages on the same channel as
used for PS paging messages (i.e. on the GPRS paging channel or the GPRS traffic channel).
Three network operation modes are defined:
- network operation mode I
The network sends a CS paging message for a GPRS-attached MS, either on the same channel as
the GPRS paging channel (i.e. the packet paging channel or the CCCH paging channel), or on a
GPRS traffic channel.
This means that the MS needs only to monitor one paging channel and that it receives CS paging
messages on the PDCH when it has been assigned a PDCH.
- network operation mode II
The network sends a CS paging message for a GPRS-attached MS, on the CCCH paging channel,
and this channel is also used for GPRS paging.
This means that the MS needs only to monitor the PCH, but that CS paging continues on the PCH
even if the MS has been assigned a PDCH.
- network operation mode III
The network sends a CS paging message for a GPRS-attached MS, on the CCCH paging channel,
and sends a GPRS paging message on either the packet paging channel (if allocated in the cell) or
on the CCCH paging channel.
That means that a MS that wants to receive pages for both CS and PS shall monitor PCH and PPCH
(if there is a MPDCH)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The following table gives the characteristics of the 3 modes:

Mode
Circuit Paging Channel
GPRS Paging Channel
PCCCH
PCCCH
CCCH
CCCH
II
Packet data channel

CCCH
(not applicable)
CCCH
III
CCCH
PCCCH
CCCH
CCCH
Characteristics
- Gs interface
- MPDCH
- Gs interface
- no MPDCH
- Gs interface
- no MPDCH
- no Gs interface
- MPDCH
- no Gs interface
- no MPDCH
- no Gs interface
The network operation mode is notified to the MS either in PSI1 or in SI13.

The mode operation is the same for one BSS.
(this information is linked to the BSC, because it depends whether there is a Gs interface or not)
1.3.4.3 System information reading
BCCH information of the serving cell indicates whether the GPRS service is supported in the cell or
not. This is done through the emission of the SI13 message.
The MS shall monitor the System Information broadcast in the cell.
If PBCCH is present in the serving cell, the MS shall receive the PSI messages broadcast on
PBCCH.
The MS shall refresh every 30s the system information of the serving cell:
- When camping on a cell where PBCCH is present, the MS shall attempt to receive the
PSI1 message at least every 30s.
- When camping on a cell where PBCCH is not present, the MS shall attempt to receive SI13
or the PSI13 message at least every 30s.
These messages contain a parameter (PBCCH_CHANGE_MARK or BCCH_CHANGE_MARK)
indicating the level of the system information.
In case the MS detects a change of that parameter, its reads the modified system information
messages (indicated in the message)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.4 Cell reselection

Three mode of cell reselection has been defined within ETSI Technical specification for GPRS MS,
known as the NC0, NC1 and NC2 network control mode, as shortly described below :
NC0 : the GPRS MS performs autonomous cell reselection without sending measurement
reports to the network.
NC1 : the GPRS MS performs autonomous cell reselection. Additionally it sends
measurement reports to the network.
NC2 : the GPRS MS shall not perform autonomous cell reselection. It sends measurement
reports to the network. The network controls the cell reselection.
The network shall support at least one of these NC modes. The GPRS MS shall support all of them.
The NC1 and NC2 modes only apply when the GPRS MS is in GMM Ready state. In GMM Standby
state, the MS shall behave according to NC0 mode.
In the current release, the NC0 mode is implemented.
As a consequence, cell reselection is exclusively done upon radio criteria (the service support in the
cell is not considered).
When the MS reselects a cell, the support of GPRS in the target cell is indicated in SI sent on BCCH.
This may also be indicated on the PBCCH of the serving cell when the Master PDCH is allocated :
this facility is however not implemented in the current release.
When a cell reselection is determined, the MS may continue its operation in the old serving cell,
while acquiring certain SI for the target cell.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.5 MS Radio Resource state
1.3.4.5.1
Packet idle mode
In packet idle mode, no TBF exists and the MS is also not trying to establish an UL TBF. The MS is
monitoring the common channels (CCCH or PCCCH), either in DRX or non DRX mode
The MS shall enter non-DRX mode in any of the following cases :
-
Upon transition from the packet transfer mode to the packet idle mode, a mobile station shall
enter the Transfer non-DRX 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 DRX_TIMER_MAX parameter, broadcast in the cell.
The DRX_TIMER_MAX value is set to 0 by the Alcatel BSS. The mobile station enters the
DRX mode immediately after the release of an on-going TBF.
A mobile station operating in NC2 mode shall enter the NC2 non-DRX mode period when it
sends an NC measurement report. The duration of this period is defined by the
NC_NON_DRX_PERIOD parameter.
The Alcatel BSS does not support the NC2 mode. The mobile station does not enter the NC2
non-DRX mode.
When initiating the MM procedures for GPRS attach and routeing area update, the mobile
station shall enter the MM non- DRX mode period. This period ends when the corresponding
MM procedures terminate.
Otherwise, the MS shall be in DRX mode. The parameter SPLIT_PG_CYCLE, provided by the
mobile station in the GPRS attach procedure, controls the occurrence of paging blocks on PCCCH
belonging to the mobile station in DRX mode (the Alcatel BSS does not support the split-pg-cycle
option on CCCH).
1.3.4.5.2
Packet transfer mode
In packet transfer mode, a TBF has been assigned to the MS or the MS is currently trying to get a
packet channel for UL transfer.The mobile station is in non-DRX mode (even when the assigned
resources are not usable immediately, i.e. the network used the tbf_starting_time option when
allocationg radio resources to the mobile station)
The MS is either listening to common channels (in case it is trying to establish an UL TBF or in case
it has to wait before using assigned resources) or assigned PDCHs when it is allowed to use them.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.5.3
MS Radio Resource substates
Following MS radio resource substates are defined to define the MS state and expected behaviour.
RR_states
Packet Idle Mode
Idle_substate
RR_substates
Packet Transfer Mode

UL_transfer_substate
DL_transfer_substate
Idle_substate :
- DRX_mode
: MS listens common channels according to its paging group(s) only (the
paging group on PCH is defined by the IMSI, the paging groups on PPCH are defined by the
IMSI and the SPLIT_PG_CYCLE value of the mobile station).
- non_DRX mode
: MS listens common channels continuously. Except during the uplink packet
access procedure, the mobile station may ignore some radio blocks on PCCCH while reading
system informations (case where the cell supports several PCCCH channels and the PCCCH
group of the mobile station is not supported by the channel carrying the PBCCH). The mobile
station will in all circumstances listen to the paging blocks.
UL_transfer_substate and DL_transfer_substate :
- idle
: no traffic need for either UL or DL path
- establishing
: on-going UL TBF establishment, no TFI nor radio resources are assigned
- waiting
: TFI is assigned but radio resources are either not yet assigned or not usable
yet by the MS
- transferring
: TFI is assigned and radio resources are usable for transfer
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.6 Channels listened by the MS

The following table indicates the channels to be listened by MS according to its RR_state and
RR_substates.
RR_state
RR_substates
DRX_mode
Packet_Idle_mode
Packet_Transfer_mode
Non_DRX_mode
UL idle
UL establishing
DL waiting
DL transferring
DL idle
DL waiting
DL transferring
DL idle
UL waiting
UL transferring
DL waiting
DL transferring
DL idle
DL waiting
DL transferring
Listened channels
(P)CCCH blocks
defined by paging
group(s)
Full (P)CCCH (note 1)
Full (P)CCCH (note 1)
Assigned DL PDCH(s)
Full (P)CCCH
Full (P) CCCH
Assigned DL PDCH(s)
- PDCH on which
Packet Resource
request was sent (case
of MS waiting for
second uplink
assignment in 2 phase
access)
Or
- full (P)CCCH if MS is
waiting
for
using
allocated resources
Full (P)CCCH
Assigned DL PDCH(s)
Assigned UL PDCH(s)
Assigned UL PDCH(s)
Assigned DL & UL
PDCH(s)
Note 1 : in case of a cell configured with multiple PCCCH channels :

- the mobile station performing an uplink access listens to the full PCCCH channel (it does not
read system informations during the packet access procedure)
- otherwise the mobile station may loose some blocks to read system informations ; the paging
blocks are not ignored by the mobile station.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.7 GPRS traffic interruption, in a cell

Below are indicated the different steps of this procedure, in the different cases.
1.3.4.7.1
With a MPDCH
1) MS in packet transfer mode

- The MS receives a Packet PDCH Release on its PACCH with the indication that all its
PDCHs have been released.
- Then the MS performs
- either an abnormal release with random access , if the MS had an UL transfer in
progress
- or an abnormal release with return to PCCCH, if the MS had no UL transfer in progress
- The MFS indicates through PSI1 that the MPDCH will be released shortly (BS_PCC_REL
set). The aim of this indication is to force the MS to return on BCCH to read SI13 and thus to
perform a complete acquisition of BCCH messages.
The MS will, then be informed that this cell doesnt support GPRS any more
(Otherwise if PSI broadcast would have been stopped abruptly, the MS would wait for 60s,
before undertaking a cell reselection). The timer T_MPDCH_Deact shall at least cover the
time needed to update the BCCH information, plus 2 times the PSI1_REPEAT_PERIOD
duration to allow the MS to receive at least 2 PSI1 after the BCCH has been updated.
2) MS in idle mode
- When receiving the BS_PCC_REL indication on PSI1, the MS will return on BCCH.
1.3.4.7.2
Without MPDCH
1) MS in packet transfer mode

- The MS receives a Packet PDCH Release on its PACCH with the indication that all its
PDCHs have been released.
- Then the MS performs
- either an abnormal release with random access , if the MS had an UL transfer in
progress
- or an abnormal release with return to CCCH, if the MS had no UL transfer in progress
- The MS will be notified, through SI messages, that the cell doesnt support any more
GPRS.
2) MS in idle mode
- The MS will be notified, through SI messages, that the cell doesnt support any more
GPRS.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.4.8 GPRS access in the cell and Overload control

Access can either be done on CCCH or PCCCH.
1.3.4.8.1
Access class barring/unbarring
In order to provide certain MS users (e.g. police, fire brigade,...) priorities in case of overload
situations, the concept of access classes is used.
- low priority access classes 0..9
- high priority access classes 11..15
- emergency call access 10 (not a class as such, but an authorisation for normal MS to
establish emergency calls)
An information ACC_CONTR_CLASS defining the state of each access class (barred/unbarred) is
broadcast to the MS.
The value of this information depends on:
- dynamic conditions (e.g. overload detection)
- and O&M indications
1.3.4.8.2
Cell barring
The cell reselection procedure is only started by an MS when a cell is barred and not when the
access class of the MS is barred.
Therefore barring a cell will force the MS to try to camp on other cells, from where they can
undertake calls.
A cell can be barred
- either by an O&M command
- or when the last MS access class has been barred, if the O&M AUT_BAR is set.
The status for cell reselection is indicated to the MS, through the CELL_BAR_ACCESS2 parameter
(broadcast on PSI3), which values are defined in the table below according CB and CBQ
(Cell_Barr_Qualify)
CB = 0
Normal
Normal
CBQ = 0
CBQ = 1
- Normal:
- Barred:
CB = 1
Barred
Normal
a MS can access to the cell

a MS cannot access to the cell
CBQ depends on an O&M parameter and is also set when barring is due to access class barring.
(for more details, see 5.5.1.2.2.3)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.5 Quality of Service Management

1.3.5.1 QoS parameters
M
S
Um
BSS
Gb
SGSN
Gn
GGSN
Gi
PDN
T
E
Radio
QoS
GPRS QoS
User QoS
User
opinion
Figure 2 : Quality of service levels
Different levels of QoS shall be distinguished :
user QoS profile : end-to-end QoS granted to a user application.
GPRS QoS profile :

QoS granted in the GPRS network between the MS (R or S reference points) and the PDN (Gi
reference point).
defined in A and B in term of service precedence, transfer delay, mean and peak throughputs
and reliability.
managed by SGSN according to application time scale.
Radio QoS profile :
QoS granted on the radio interface to transfer one or few PDU.
Throughput : this is the useful throughput expected on radio interface. The throughput actually
allocated on radio interface may be higher to take into account control information overhead required
by the radio protocol stack and data retransmissions for error recovery.
service precedence : defines the priority for maintaining service under congested situation ; it is
specified explicitly on DL path and is equal to the radio priority on UL path.
RLC reliability mode : RLC acknowledged or not acknowledged protocol
A BSS transfer delay requirement is provided for DL LLC PDU through the PDU lifetime which
indicates the latest time at which the PDU shall be completely transmitted. PDU lifetime is expected
to be configured by SGSN according to GPRS transfer delay class of associated PDP context.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1.3.5.2 BSS behaviour related to QoS in B6.2

- service precedence
The service precedence (i.e. the service precedence value in DL LLC PDU or the radio priority level
of UL TBF) is not managed, except that the operator can configure in case of GPRS cell configured
with a Master PDCH - the persistence level of each radio priority level and therefore control the
uplink TBF establishment delay.
There is no preemption of on-going TBF to establish a new one with higher service precedence level.
- Throughput
There is no quantitative commitment made to the user in term of granted throughput.
The information requested throughput of DL LLC PDU or UL TBF is not taken into account by the
BSS. The allocation strategy consists in trying to allocate to the MS as many PDCHs as supported by
its multislot class if such information is known. The operator may limit the maximum number of
PDCHs allocated to a TBF through O&M configuration (from GPRS Pilot). The PDCH available
throughput is equally shared between all MS allocated on it.
(RRM) layer accepts any UL or DL packet connection request up to the maximum possible number of
packet connections. PDCH may be allocated even above 100% of their capabilities in case of
insufficient available radio resources, e.g. when DL data flow is greater than the cell radio capacity.
The radio block allocation performed in (MAC) layer does not take into account PDU lifetime nor
service precedence in B6.2
The maximum throughput that may be served to a MS is limited to n x 12 kbits/s in case of good
radio conditions (no retransmissions), n being limited by upper multislot class supported by the
network (n=5). The Peak throughput classes 1 to 3, and Mean throughput classes 1 to 18 defined in
B are therefore supported.
- RLC mode
The RLC mode is not changeable during on-going TBF (compliant to ETSI standard). In case PDUs
received from SGSN and addressed to the same MS own different RLC mode, there are 2 cases:
- current RLC mode is acknowledged
If a LLC-PDU is received with unacknowledged RLC mode, the LLC-PDU is sent in
acknowledged RLC mode.
- current RLC mode is unacknowledged
If a LLC-PDU is received with acknowledged RLC mode, the LLC-PDU is queued and when
the previous LLC-PDU have been sent, a new TBF is established, in RLC acknowledged
mode.
- PDU lifetime
DL LLC PDUs are deleted in case their PDU lifetime expires.
In case of unavailability of either traffic resources (TFI, TAI, throughput) or PDCH resources, DL TBF
establishments requests are queued and served according to the PDU lifetime.
PDU lifetime is not further taken into account by the MFS (the radio block allocation at MAC level is
not influenced by the PDU lifetime).
- Signalling
The LLC PDU type is not handled by the MFS.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- Transfer delay
Best effort is supported.
DL LLC PDU transfer delay depends on the allocated throughput and potentially PDU lifetime.
UL LLC PDU transfer delay depends on radio priority (assumed to be defined by the SGSN
according to PDP context transfer delay and service precedence) and allocated throughput.
For the first PDU sent on TBF :
BSS Transfer delay = (paging delay) + radio access delay + transmission delay over radio
interface
For subsequent PDUs sent on established TBF :
BSS Transfer delay = BSS queuing delay + transmission delay over radio interface
-
On UL path :
Radio access delay is function of :

The radio priority assigned by the SGSN to the MS during the PDP context activation. Service
precedence and transfer delay class are likely to be the basic inputs used by SGSN to compute the
MS radio priority.
The presence or not of a Master PDCH
The persistence level of each radio priority configured by the operator and sent within Packet
System Information
Transmission delay is function of allocated throughput, PDCH load and radio propagation
conditions with the MS.
BSS queuing delay at Gb interface may be considered in case of NS congestion.
-
On DL path :
Paging delay may be applicable in case cell location procedure is needed.
Radio access delay covers :
the time to get radio resources for the DL packet connection : it is instantaneous in case there is a
DL TFI and a TAI available in the cell. Otherwise requests are served as soon as resources are
released, starting with PDU with the shortest PDU lifetime.
The time to send a Packet Downlink Assignment to the MS : it depends on the channel type on
which it is sent (CCCH / PCCCH), on the MS DRX parameter, on the channel configurations (e.g.
split-pg-cycle) and load.
Transmission delay is function of allocated throughput, PDCH load and radio propagation
conditions with the MS.
BSS queuing delay represents the time needed to send previous DL LLC PDU to that MS. It
depends on the transmission delay of previous PDU.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- QoS multiplexing over the radio interface

Data may be simultaneously sent between the same MS and SGSN for different PDP contexts with
different QoS. These are multiplexed on the same TBF on radio interface.
BSS may consequently receive DL PDU to be sent to the same MS with different QoS.
In case a DL LLC PDU is received with a different RLC mode than the RLC mode of
already established TBF, the BSS keeps the LLC-PDU emission order and each time the
RLC mode is changed the current TBF is released and another TBF is established.
Service precedence modification during on-going TBF is not supported
throughput change during on-going TBF is not supported
(Service precedence and throughput parameters are not handled in B6.2 )
- Gb priority field
not managed
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2.
PROTOCOL LAYER STRUCTURE
2.1
Overview of layer functional model
RRM
PRH
PAG
TBF
Resources
Allocation
CS Paging
PDCH
resource
control
PS Paging
Packet
System
Informations
NTM
PCC
TRN
Entity
state
management
Packet
connection
establishment
DL data
transfer
Performance
monitoring
Packet
connection
modification
UL data
transfer
Packet
connection
release
Management
Figure 4 : RRM layer functional model

PRH entity
The (RRM) Packet Radio Resource Handling entity supports the following functions :
TBF resources allocation to allocate radio resources to packet transfer
PDCH resource control to monitor the radio resource usage and potentially dynamically
allocate PDCH.
Packet System information broadcast on PBCCH (B6.2 SMG29 only)
PAG entity
The (RRM) Packet Paging entity supports the following functions :
CS and PS Paging of MS on the relevant radio channel according to MS Packet mode
(Packet idle or transfer mode) and MPDCH configuration
NTM entity
The (RRM) Network Management entity supports the following functions :
Entity state management
Performance monitoring
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
PCC entity
The (RRM) Packet Connection Control entity is in charge of establishing or releasing Packet
connections. Besides it takes into account modification of packet connection attributes (e.g. TLLI,
coding scheme).
TRN entity
The (RRM) Transport entity supports the following functions :
DL LLC PDU transfer from BSSGP to RLC layer
UL LLC PDU transfer from RLC to BSSGP layer
DSP memory congestion handling
DL flow control with RLC layer
UL congestion control
Bandwidth capacity adaptation in case of failure on Gb interface or NS-VC lock
2.2
Overview of layer interfaces
LME
BSCGP
RRM
BSSGP
RLC
Figure 3 RRM interfaces
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.
SERVICE PRIMITIVES DEFINITION
3.1
Primitives provided to Layer Management Plane
R I R C
E N E N
Q D S F
LM-BSS-CREATE
x
x
LM-BSS-DELETE
x
x
LM-BSS-SET
x
x
LM-BSS-GET
x
x
LM-BSS-STATE-CHANGE
x
LM-CELL-CREATE
x
x
LM-CELL-SET
x
x
LM-CELL-DELETE
x
x
LM-CELL-GET
x
x
LM-CELL-STATE-CHANGE
x
LM-GIC-Group-CREATE
x
x
LM-GIC-Group-DELETE
x
x
LM-GIC-Group-GET
x
x
LM-GIC-Group-STATE-CHANGE
x
Primitive Name
ED
MCD
Semantic
Creation of a BSS
Deletion of a BSS
to modify a BSS parameter
to get operational state
state change notification
Creation of a cell
Modification of cell parameters
Deletion of a cell
To read cell attributes or counters
state change notification
Creation of a GIC group
Deletion of a GIC group
To read GIC group attributes
Notification of GIC Group state
change
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.2
List of service primitives used by the layer
3.2.1 Service primitives used from (RLC) layer

The primitives used from (RLC) layers are described in 4 or 5:
Type
Primitive name
Semantic
re
q
ind res cnf
PRH-SYS-DEFINE
PRH-BLOCK-RESERVE
PRH-PDCH-ESTABLISH
PRH-PDCH-RELEASE
PRH-PDTCH-ASSIGN
PRH-PDTCH-DEASSIGN
x
x
PAG-PAGE-MS
PCC-DL-CONTROL
PCC-UL-CONTROL
PCC-DL-ASSIGN
PCC-UL-REJECT
PCC-RLC-ESTABLISH
PCC-RLC-ACTIVATE
PCC-RLC-RELEASE
PCC-RLC-MODIFY
x
x
x
x
x
x
x
PCC-TLLI-NOTIFY
TRN-DL-FLOW-CTRL
TRN-DL-UNITDATA
TRN-UL-UNITDATA
TRN-DL-FLOW-END
ED
MCD
x
x
x
x
x
x
x
x
x
x
x
x
to provide MAC with MPDCH logical

configuration and sysinfo. MAC is in
charge of broadcasting provided sysinfo
msg.
to request allocation of a block on a
given PDCH for 2 phase access
to declare a new PDCH in MAC layer,
and to activate it for GPRS in BTS
to release a PDCH in MAC layer ;
indication that a PDCH has been
released (e.g. L2GCH desynchronisation)
to reserve resources for a new TBF
to free resources reserved for an existing
TBF
to send a CS or PS paging request on
PPCH
To send RRM signalling PDU to a MS .
To receive RRM signalling PDU from a
MS
To perform a DL assignment on PCCCH.
To receive notification when the Packet
Downlink Assignment is not sent by
MAC.
to reject access request on PCCCH
to establish a TBF context in (RLC)
to start allocation of radio blocks
to free a TBF context
Used by RLC to notify a coding scheme
adaptation
UL contention resolution information
DL flow control with RLC for 1 TBF
to send DL PDU to (RLC)
received UL PDU
RLC(TRN) notifies RRM(TRN) that DL
TBF is being released (last RLC data
blocks are sent). New DL LLC PDU can
not be sent on that TBF.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The following table identifies the RLC primitive and the RRM PDU mnemonic used in dynamic
scenarios and finite state machines in the remaining of the document, for each RRM PDU sent to or
received from MS.
RRM PDUs sent to MS
PACKET DOWNLINK
ASSIGNMENT
PACKET UPLINK
ASSIGNMENT
RLC primitive used RLC primitive used PDU

name
in
when PDU is sent on when PDU is sent on subsequent scenarios
Master PDCH
other PDCH
and
finite
state
machines
PCC-DL-ASSIGN-req
PCC-DL-CONTROLPCC-DL-ASSIGN-req
req
PCC-DL-CONTROL-req
PCC-UL-ASSIGN-req
PACKET ACCESS
REJECT
PCC-UL-REJECT-req
PACKET PAGING
REQUEST
PACKET PDCH
RELEASE
PACKET POWER /
TIMING ADVANCE
UPDATE
PACKET SYSTEM
INFORMATION
PACKET CHANNEL
REQUEST
UL access request
during DL transfer
PACKET RESOURCE
REQUEST
PACKET CONTROL
ACKNOWLEDGEMENT
PAG-PAG-MS-req
PAG-PAGE-MS-req
PCC-DL-CONTROL-req
PRH-PDCH-RELEASEMS-req
PCC-TA-UPDATE-req
ED
MCD
PCC-DL-CONTROLreq
PCC-DL-CONTROLreq
PCC-DL-CONTROL-req
PCC-UL-REJECT-req
PRH-SYS-DEFINE
Not applicable
PRH-SYS-DEFINE-req
PCC-UL-CONTROLind
Not applicable
Not applicable
PCC-UL-CHN-REQ-ind
PCC-UL-CONTROLind
PCC-UL-CONTROL-ind
PCC-UL-CHN2-REQ-ind
PCC-UL-CONTROL-ind
PCC-CTRL-ACK-ind
PCC-UL-RES-REQ-ind
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.2.2 Service Primitives used from (BSSGP) layer

Type
Semantic
Primitive name
re
q
RL-DL-UNITDATA
RL-UL-UNITDATA
RL-UL-START
RL-UL-STOP
GMM-PAGING-PS
GMM-PAGING-CS
GMM-RADIO-STATUS
ind res cnf
x
x
x
x
x
x
x
NM-FLUSH-LL
NM-LLC-DISCARDED
NM-FLOW-CONTROL-BVC
NM-FLOW-CONTROL-MS
NM-STATUS
x
x
x
NM-BVC-PTP-CREATE
NM-BVC-PTP-DELETE
NM-BVC-SIG-CREATE
NM-BVC-SIG-DELETE
x
x
NM-BVC-PTP-T-STATUS
NM-BVC-SIG-T-STATUS
NM-NSE-CONGESTION
ED
MCD
NM-NSE-CAPACITY
NM-BVC-PTP-START
NM-BVC-PTP-STOP
NM-BVC-SIG-START
NM-BVC-SIG-STOP
NM-CELL-RESET
x
x
x
send a DL-UNITDATA to BSS

send a UL-UNITDATA to SGSN
throughput reservation request
(RRM) informs (BSSGP) of end of
transfer
page an MS within group of cells
page an MS within group of cells
report that an exception condition
occurred in the operation of the radio
interface for an MS.
request to re-route or delete queued LLCSDU(s)
indicates that a number of buffered LLCSDUs in a cell for an MS have been
deleted inside the BSS
BVC flow control is notified to SGSN
MS flow control is notified to SGSN
indicates a PDU exception condition
occurred.
BVC-PTP creation requested to BSSGP
layer
BVC-PTP deletion requested to BSSGP
layer
BVC-SIG creation requested to BSSGP
layer
BVC-SIG deletion requested to BSSGP
layer
BVC-PTP transmission status change
notified by (BSSGP) layer
BVC-SIG transmission status change
notified by (BSSGP) layer
NSE congestion notified by (BSSGP)
layer
NSE available bandwidth notification
RRM asks to BSSGP to unblock a PTPBVC
RRM asks to BSSGP to block a PTPBVC
RRM asks to BSSGP to start a SIG-BVC
RRM asks to BSSGP to stop a SIG-BVC
BVC-PTP RESET has been received
from SGSN
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.2.3 Service Primitives used from (BSCGP) layer

Primitive Name
NTM-BSC-RESET
NTM-BSC-STATE
NTM-BSC-TRAFFICCONTROL
NTM-CELL-DETACH
NTM-CELL-START
NTM-CELL-STATE
NTM-CELL-STOP
NTM-CELL-RESET
NTM-CELL-TRAFFICCONTROL
NTM-GICGROUP-STATE
R
E
Q
x
x
I
N
D
x
x
x
R
E
S
x
x
x
x
x
NTM-TRAFFIC-CONTROL
PAG-PAGE-MS
PCC-CHANNEL-ASSIGN
PCC-UL-CHN-REQ
PRH-CELL-LOAD
x
x
C
N
F
x
x
x
x
x
x
x
x
PRH-CONF-MASTER
PRH-DECONF-MASTER
PRH-PDCH-ALLOCATE
PRH-PDCH-DEALLOCATE
ED
MCD
Semantic
Reset of BSCGP interface
BSC state change notification or request
Authorised access classes are changed
for the whole BSS.
the cell is detached (i.e; no more state
change for this cell)
Start GPRS traffic within a cell
Cell state change notification or request
Stop GPRS traffic within a cell
deallocation of all cell resources
for one or several cells.
GIC group state change notification or
request
for one or several cells.
To transfer a CS or PS paging message
on PCH
To transfer an immediate assignment
message on CCCH
Notification of a CHANNEL REQUEST
received on RACH (for GPRS)
Indicates that the load of one or several
cells changes
Configure a master channel on an
existing PDCH
Deconfigure a master channel on an
existing PDCH
To request allocation by the BSC of one
or several PDCH
Indicate or request deallocation of one or
several PDCH
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Release
Pilot
Pilot
B6.2
B6.2
Pilot
Pilot
Pilot
B6.2
B6.2
Pilot
B6.2
Pilot
Pilot
Pilot
Pilot
B6.2
B6.2
Pilot
Pilot
3.3
Detailed description of service primitives provided by the layer
3.3.1 Service primitives provided to Layer Management entity

3.3.1.1 LM-BSS-CREATE-req
This primitive is used by LM to create a BSS.
Parameters
BSSid
administrative
state
network
operation mode
Presence
Range
Semantic
BSS Identifier
locked/unlocked
1, 2, 3
- mode I: CS and PS paging co-operation (Gs interface is

mandatory)
- mode II: no master PDCH
- mode III: no specific requirements
M
M
M
3.3.1.2 LM-BSS-CREATE-cnf
This primitive is used by NTM to indicate to LM that a new BSS has been successfully created or
not.
Parameters
BSSid
result
cause
Presence
Range
M
M
C
OK/NOK
0-255
Semantic
BSS Identifier
cause of the refusal
(present if result = NOK)
3.3.1.3 LM-BSS-DELETE-req
This primitive is used by LM to delete a BSS.
Parameters
BSSid
Presence
Range
Semantic
BSS Identifier
3.3.1.4 LM-BSS-DELETE-cnf
This primitive is used by NTM to indicate to LM that a BSS has been successfully deleted or not.
Parameters
BSSid
result
cause
ED
MCD
Presence
Range
M
M
C
OK/NOK
0-255
Semantic
BSS Identifier
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.5 LM-BSS-GET-req
This primitive is used by LM to get a BSS operational state.
Parameters
BSSid
Presence
Range
Semantic
BSS Identifier
3.3.1.6 LM-BSS-GET-cnf
This primitive is used by NTM to return to LM the BSS operational state.
Parameters
BSSid
result
cause
Presence
Range
M
M
C
OK/NOK
operational state
enabled/
disabled
availability status
0-255
Semantic
BSS Identifier
present if operational state = disabled
- dependency: BVC-SIG not operational
- off-line: BSS unavailable (BSCGP indication)
3.3.1.7 LM-BSS-STATE-CHANGE-ind
This primitive is used by NTM to notify to LM BSS operational state changes.
Parameters
BSSid
operational state
Presence
availability status
ED
MCD
M
M
Range
Semantic
BSS Identifier
enabled/
disabled
present if operational state = disabled

- dependency: BVC-SIG not operational
- off-line: BSS unavailable (BSCGP indication)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.8 LM-BSS-SET-req
This primitive is used by LM to modify parameters of one BSS.
Parameters
BSSid
administrative
state
network
operation mode
Presence
Range
Semantic
BSS Identifier
locked/unlocked
1, 2, 3
- mode I: CS and PS paging co-operation (Gs interface is

mandatory)
- mode II: no master PDCH
- mode III: no specific requirements
M
O
M
Network operation mode modification will have the following consequences:

Old Network Operation Mode
I/III
New Network Operation Mode

II
I
III
II
III
I
I/III
Action
If in the BSS, there are cells
supporting a master PDCH, the
master PDCH has to be
deactivated spontaneously by
RRM
no action
no action
If in the BSS, there are cells
supporting the activation of a
master PDCH, the master
PDCH shall be activated
3.3.1.9 LM-BSS-SET-cnf
This primitive is used by NTM to indicate to LM that BSS parameters have been successfully
modified or not.
Parameters
BSSid
result
cause
ED
MCD
Presence
Range
M
M
C
OK/NOK
0-255
Semantic
BSS Identifier
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.10
LM-CELL-CREATE-req
This primitive is used by LM to create a new cell and declare:

- its adjacent cells
- its parameters (configuration parameters and PSI parameters)
- composition of each PDCH group (only one in B6.2 )
A PDCH group is a set of time-slots which
- can be used for GPRS traffic,
- belong to the same TRX
- have the same frequency configuration
- are all contiguous (i.e. no hole between the time-slots of the PDCH group)
Parameters
Cellid
BSCid
MIN_MPDCH
MAX_MPDCH
Presence
Range
M
M
M
M
0/1
0/1
Nb_PDCH_Group
PDCH_Group_id1
MIN-PDCH-Group
M
M
M
1-8
Maximum number of PDCHs allocated in the cell

( 0, if MPDCH = 1)
1-8
Maximum number of PDCHs allocated in a cell when the BSC

has indicated a high load situation in the cell
Value 0 means that when the cell is in a high load situation, no
GPRS call is possible.
( 0, if MPDCH = 1)
(first PDCH
group)
MAX-PDCH-Group
(first PDCH
group)
MAX-PDCHHIGH-LOAD
(first PDCH
group)
cell parameters
adjacent
cell
parameters
administrative
state
ED
MCD
0-8
M
C
M
locked/
Semantic
Cell identifier (LAC+CI)
BSC Identifier
minimum number of PDCHs, supporting the master PDCH
maximum number of PDCHs, supporting the master PDCH
MIN_MPDCH
MAX_MPDCH
0
0
no MPDCH
0
1
dynamic MPDCH
(not in B6.2B6.2 )
1
1
static MPDCH
MAX_MPDCH = MIN_MPDCH in B6.2
PDCH group number (only one in B6.2 )
identifier of the first PDCH group
Minimum number of PDCHs statically allocated in the cell
( 0, if MPDCH = 1)
cell parameters (see 6)

(see 6)
present only if there is a master PDCH
administrative state at cell creation
unlocked
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.11
LM-CELL-CREATE-cnf
This primitive is used by NTM to indicate to LM that a new cell has been successfully created or not.
Parameters
CELLid
result
cause
3.3.1.12
Presence
Range
M
M
C
OK/NOK
0-255
Semantic
LM-CELL-DELETE-req
This primitive is used by LM to delete an existing cell.

This cell has to be previously locked.
Parameters
CELLid
3.3.1.13
Presence
Range
Semantic
LM-CELL-DELETE-cnf
This primitive is used by NTM to indicate to LM that a cell has been successfully deleted or not.
Parameters
CELLid
result
cause
ED
MCD
Presence
Range
M
M
C
OK/NOK
0-255
Semantic
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.14
LM-CELL-SET-req
This primitive is used by LM to modify the parameters or the cell administrative state of an existing
cell.
Parameters
CELLid
BSCid
administrative
state
MIN_MPDCH
MAX_MPDCH
Presence
M
M
0/1
0/1
Nb_PDCH_Group
PDCH_Group_id1
MIN-PDCH-Group
M
M
M
0-8
1-8
Maximum number of PDCHs allocated in the cell

( 0, if MPDCH = 1)
1-8
Maximum number of PDCHs allocated in a cell when the BSC

has indicated a high load situation in the cell
Value 0 means that when the cell is in a high load situation, no
GPRS call is possible.
( 0, if MPDCH = 1)
(first PDCH
group)
MAX-PDCH-Group
(first PDCH
group)
MAX-PDCHHIGH-LOAD
(first PDCH
group)
cell parameters
adjacent
cell
parameters
ED
MCD
M
M
M
M
C
Range
Locked/
unlocked
Semantic
BSC identifier
administrative state
minimum number of PDCHs, supporting the master PDCH
maximum number of PDCHs, supporting the master PDCH
MIN_MPDCH
MAX_MPDCH
0
0
no MPDCH
0
1
dynamic MPDCH
(not in B6.2 )
1
1
static MPDCH
MIN_MPDCH = MAX_MPDCH in B6.2
PDCH group number (only one in B6.2 )
identifier of the first PDCH group
Minimum number of PDCHs statically allocated in the cell
( 0, if MPDCH = 1)
Telecom parameters
if there is a master PDCH
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The modification of the following parameters requires specific conditions:

- MIN_MPDCH & MAX_MPDCH:
The new limit is taken into account.
If a static MPDCH is activated, an Allocation request is sent towards the BSC if no PDCH is allocated
yet, and a PDCH is configured as a MPDCH.
If a static MPDCH is deactivated, the PDCH carrying the MPDCH is reconfigured as a slave PDCH
and is given back to the BSC under conditions defined in 5.5.3.7.
- MAX_PDCH_Group:
If the current number of allocated PDCHs is greater than the new Max_PDCH_Group value, surplus
PDCHs are marked not to be used for new TBF establishments. They will be deallocated when free
(see 5.5.3.7)
- MAX_PDCH_High_Load:
If the cell is in a high load situation and if the current number of allocated PDCHs is greater than the
new Max_PDCH_High_Load value, surplus PDCHs are marked not to be used for new TBF
establishments. They will be deallocated when free (see 5.5.3.7)
- MAX_PDCH_PER_TBF:
If some current TBFs have more PDCHs than the new Max_PDCH_Per_TBF value, no specific
action is undertaken.
- MIN_PDCH_Group:
If the current number of allocated PDCHs is smaller than the Min_PDCH_Group value, an Allocation
request is sent towards the BSC.
If the current number of allocated PDCHs is greater than the new Min_PDCH_Group and if there are
free PDCHs. Some (or all) of these PDCHs are deallocated to be compliant with the new minimum.
- Nb_TBF_PER_PDCH/MPDCH:
If the current number of TBFs on a PDCH is greater than the new limit, no specific action is
undertaken.
- LAC/CI:
New values of LAC/CI, received from the OMC/R are only taken into account when a cell STATE
CHANGE INDICATION (with the new LAC/CI) is received from the BSC.
Then, if GPRS traffic was started in the cell: (see 5.1.5.9)
- GPRS traffic is stopped in the cell
- BVC-PTP reset procedure is triggered, in order to send the new LAC/CI to the SGSN
- then, GPRS traffic is started again in the cell
Otherwise, if GPRS traffic was not started, no specific action is undertaken.
- RA code:
On modification of this parameter, GPRS traffic is stopped in the cell, a BVC-RESET procedure is
undertaken, on the Gb interface, to send the new cell identity to the SGSN and then GPRS traffic is
re-started (see 5.1.5.9)
- BS_PAG_BLKS_RES and BS_PBCCH_BLKS:
These parameters may be changed on-line, but in this case, paging and DL assignment messages
which are queued at MAC level, to be sent on PPCH, are lost.
3.3.1.15
LM-CELL-SET-cnf
This primitive is used by NTM to indicate to LM that the cell parameters or administrative state have
been successfully modified or not
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Parameters
CELLid
result
cause
ED
MCD
Presence
Range
M
M
C
OK/NOK
267129603.doc
10/08/2000
0-255
Semantic

04 Released
3BK 11202 0265 DSZZA
3.3.1.16
LM-CELL-GET-req
This primitive is used by LM to get cell attributes

Presence
Parameters
Cellid
3.3.1.17
Range
Semantic
LM-CELL-GET-cnf
This primitive is used by NTM to give to LM the cell parameters.

Parameters
Cellid
result
cause
Presence
Range
M
M
C
OK/NOK
operational
state
availability status
3.3.1.18
0-255
enabled/
disabled
off-line/
depend
ency/
failed
Semantic
GPRS operational state
present only if operational state = disabled
- off-line:
BSCGP unavailability
- dependency: BVC-PTP unavailability
- failed:
RRM internal cause
(e.g. MPDCH not established)
LM-CELL-State-Change-ind
This primitive is used by NTM to indicate to LM cell state changes or MPDCH state changes.
Parameters
CELLid
cell operational
state
cell availability
status
Presence
MPDCH
operational state
ED
MCD
M
M
M
Range
enabled/
disabled
off-line/
depend
ency/
failed
enabled /
disabled
Semantic
GPRS cell operational state
present only if operational state = disabled
- off-line:
BSCGP unavailability
- dependency: BVC-PTP unavailability
- failed:
RRM internal cause
(e.g. MPDCH not established)
MPDCH operational state
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.19
LM-GIC-Group-CREATE-req
This primitive is used by LM to declare a GIC group with its associated Ater circuits which can be
used for GPRS traffic for a given BSS.
The BSC identifies one Ater interface circuit towards the MFS by using the following identification:
- GIC group identification (PCM identifier)
- Ater circuit (timeslot identifier) (64 kbit/s circuit)
On MFS side, a circuit is defined as an AterMux circuit (PCM, time-slot, nibble) (16Kbit/s circuit)
Sub-Multiplexer
BSC
MFS
Ater interface
Parameters
BSSid
GIC group
ATERmuxid (1)
Presence
Range
M
M
M
0-2047
ATERCid (1)
ATERmuxid (n)
ATERCid (n)
ED
MCD
AterMux interface
Semantic
BSS Identifier
GIC group (PCM identification: 11 bits)
ATERmux identification (used for local addressing)
- PCM (9 bits)
- TS (5 bits)
- nibble (2 bits)
Mapped Ater circuit identity = CIC
(used for PDCH allocation request to BSC)
- TS (5 bits)
ATERmux identification (used for local addressing)
- PCM (9 bits)
- TS (5 bits)
- nibble (2 bits)
Mapped Ater circuit identity = CIC
(used for PDCH allocation request to BSC)
- TS (5 bits)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.20
LM-GIC-Group-CREATE-cnf
This primitive is used by NTM to indicate to LM that the GIC group has been successfully created or
not.
Parameters
BSSid
result
Presence
Range
M
M
OK/NOK
cause
0-255
GIC group
3.3.1.21
Semantic
BSS Identifier
OK: the request has been totally accepted
NOK: the request has been partially or totally refused
Gic group identification (PDM: 11 bits)
(present if result = OK)
LM-GIC-Group-DELETE-req
This primitive is used by LM to delete an existing GIC group.

Parameters
BSSid
GIC group
3.3.1.22
Presence
Range
M
M
Semantic
BSS Identifier
LM-GIC-Group-DELETE-cnf
This primitive is used by NTM to indicate to LM that the GIC group has been successfully deleted or
not.
Parameters
BSSid
GIC group
result
Presence
Range
M
M
M
OK/NOK
cause
0-255
3.3.1.23
Semantic
BSS Identifier
OK: the request has been totally accepted
NOK: the request has been partially or totally refused
LM-GIC-Group-GET-req
This primitive is used by NTM to indicate to LM the GIC group attributes and states.
Parameters
BSSid
GIC group
ED
MCD
Presence
M
M
Range
Semantic
BSS Identifier
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3.3.1.24
LM-GIC-Group-GET-cnf
This primitive is used by NTM to indicate to LM the GIC group parameters and states.
Parameters
BSSid
GIC group
result
cause
Presence
operational
state
3.3.1.25
M
M
M
C
Range
Semantic
BSS Identifier
OK/NOK
0-255
enabled/
disabled

operational state
(present if result = OK)
LM-GIC-Group-State-Change-ind
This primitive is used by NTM to indicate to LM a GIC group state change.

Parameters
BSSid
GIC group
operational
state
ED
MCD
Presence
M
M
M
Range
enabled/
disabled
Semantic
BSS Identifier
operational state
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.
DEFINITION OF LAYER PROTOCOL
4.1
Peer to peer protocol description
4.1.1 Protocol definition

D provides many protocol options. This chapter is intended to define the reasons of the choices that
have been done for protocol definition.
Network requirements (NR) :
In order to optimise the radio resources usage to support the maximum possible traffic, and in order
to optimise as much as possible the QoS provided to mobile stations, the following principles were
retained :
NR1 : The network shall be able to detect if the assigned TBF is well established. Allocation
of radio blocks by (MAC) layer to the TBF for packet data transfer will start only when the
network receives the MS acknowledgement of the Packet Uplink Assignment or Packet
Downlink Assignment.
NR2 : Once established, the TBF shall be fully operational as fast as possible
NR3 : A transfer misbehaviour shall be detected as fast as possible. This is out of the scope
of RRM specification. See 4.
Besides, the network behaviour shall be made as simple and homogeneous as possible regarding
the different type of access (CCCH/PCCCH/PACCH, 1 or 2 phase access).
Induced Protocol requirements for UL path :
NR1 : MS will be requested to send a Packet Control Acknowledgement at receipt of any

Packet Uplink Assignment message. As MS can not acknowledge an Immediate
Assignment message on CCCH (1 phase access on CCCH), the network will subsequently
send to the MS a Packet Uplink Assignment on the assigned PACCH with a polling request.
NR2 : the network will provide the MS with initial timing advance.
Induced Protocol requirements for DL path :
First E limitation is that network can not assign a multislot packet connection on CCCH.
That means that 2 assignment messages are necessary : 1 on CCCH followed by 1 on
PACCH.
NR1 : MS will be requested to send a Packet Control Acknowledgement at receipt of any
Packet Downlink Assignment message. As MS can not acknowledge an Immediate
Assignment message on CCCH (DL TBF establishment on CCCH), the network will
subsequently send to the MS a Packet Downlink Assignment on the assigned PACCH with
a polling request.
NR2 : In order not to be blocked by sending window, the network shall provide initial timing
advance to MS. Indeed as an example, a 3 PDCH DL connection would stall the DL
sending window less than 480 ms, although the MS is not able to acknowledge received
blocks before up to 2 seconds. The network will therefore take profit of the Packet Control
Acknowledgment sent by MS (see previous bullet) to compute a timing advance which will
then be reported to MS through Packet Power / Timing advance update message.
All the above choices are depicted in following of the chapter.

Emphasis is put on network behaviour in that chapter.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2 Packet connection control

PCCCH
MS
BSS
Packet Channel Request
scenario 1 : request is rejected
Packet Access Reject

scenario 2 : request is accepted
Packet Uplink Assignment, polling 3a

Packet Control Acknowledgment
RLC data block
3b
3c
Packet UL ack/nack
3d
Figure 4 : 1 Phase access UL TBF establishment by MS in packet idle mode on PCCCH

(1) Packet access procedure : the Packet Channel Request message is received on PRACH and
indicates one of the following access types :
One phase access
Short access
Page Response
Cell Update
Mobility Management procedure
(2) Packet access reject procedure :
Packet Access Reject message is sent on the same PCCCH on which the Packet channel request
message was received in case the access request can not be satisfied. One reject cause will be used
by the network :
Wait : this forces the MS to stop the on-going access procedure and prevents it to perform
a new attempt for packet access in the same cell until a provided wait value (equal to
WI_PR or WI_PA) expires.
The subsequent scenario 2 is not run.
(3) Packet channel assignment procedure :
(3a) In case the packet access request can be satisfied immediately, a Packet Uplink Assignment
message is sent to MS assigning a TFI, the PDCH(s) carrying the TBF with their respective USF(s),
the TA channel, the TAI and the initial TA value. The message is sent on the same PCCCH on which
the network has received the Packet Channel request. The network forces the MS to send a Packet
Control Acknowledgment to be sure that the UL TBF has been successfully established.
The timer T_ack_wait is activated to wait for the acknowledge.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
On receipt of the assignment message, the MS switches to assigned PDCHs.

Notes
The network never forces a 2 phase access, i.e. it always allows the MS to proceed with
one phase access procedure.
In B6.2 , the network does not assign in advance radio resources to MS, i.e. the field
tbf_starting_time is not used.
(3b) The MS acknowledges the receipt of the Packet Uplink Assignment. In case that message is not
received by the network, the UL TBF establishment fails.
One phase access Contention resolution
(3c) The MS transmits uplink blocks when allowed by the network (see 5). The MS shall provide its
TLLI (and TFI) in the first 3 RLC data blocks sent to the network on the assigned PDCH(s). The
contention resolution is done at network side as soon as one of these blocks is correctly received :
the MS using the assigned TBF is non-ambiguously identified.
(3d) The contention resolution is done at MS side when the network sends on the PACCH a Packet
UL ack/Nack message with the TLLI (and TFI) field after having received correctly the first RLC data
block comprising TLLI.
Note : If no contention resolution at network side is possible (e.g. the first 3 RLC data blocks are not
correctly decoded by the network), the RLC layer shall abort the TBF.
CCCH
MS
BSS
Channel request
scenario 1 : request is rejected 2

Immediate assignment reject
scenario 2 : request is accepted 3
Immediate assignment 3a
Wait T_assign_agch_pacch
3b
Packet Uplink Assignment, polling 3c

Packet Control Acknowledgment 3d
RLC data block 3e
Packet UL ack/nack 3f
Figure 5 : 1 Phase access UL TBF establishment by MS in packet idle mode on CCCH

ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1) Packet access procedure : the Packet Channel Request message indicating a one phase access
is received on RACH. (no MS multi-slot class in this case)
Immediate assignment reject message is sent on the same CCCH timeslot on which the channel
request message was received in case the access request can not be satisfied. One reject cause will
be used :
Wait : this forces the MS to stop the on-going access procedure and prevents him to
perform a new attempt for packet access in the same cell until a provided wait value (equal
to WI_PR or WI_PA) expires.
The subsequent scenario 2 is not run in that case.
(3a)Immediate assignment is sent to MS assigning a TFI, one PDCH carrying the TBF with its
respective USF, the TA index and the initial TA value.. The message is sent on the same CCCH on
which the network has received the channel request.
Note : The network does not force 2 phase access, i.e. it always allows the MS to proceed with one
phase access procedure. Besides the network does not assign in advance radio resources to MS, i.e.
the tbf_starting_time field is not used.
The network activates the timer T_assign_agch_pacch which monitors the emission of the Packet UL
assignment on PACCH.
On receipt of the assignment message the MS switches to assigned PDCH. The MS then proceeds
with the contention resolution.
(3b) Network waits for T_assign_agch_pacch
(3c) At expiry of T_assign_agch_pacch, a Packet Uplink Assignment message is sent to MS,
assigning the same resources as those assigned in (3a)) but without TA value, to force the MS to
send a Packet Control Acknowledgment to be sure that the UL TBF has been successfully
established. The message is sent on the PACCH.
The timer T_assign_agch_pacch is restarted.
(3d) The MS acknowledges the receipt of the Packet Uplink Assignment, T_assign_agch_pacch is
stopped. In case that message is not received by the network, at expiry of T_assign_agch_pacch,
another Packet UL Assignment message is sent to the MS on PACCH (attempts are limited by an
O&M parameter: Max_GPRS_assign_agch_retrans).
One phase access Contention resolution
(3e) and (3f) Same as for 1 phase access UL TBF establishment initiated by MS in packet idle mode
on PCCCH.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.3 Two phase access UL TBF establishment initiated by MS in packet idle on PCCCH
A 2 phase access is necessary, when the MS wants
- either to use RLC unacknowledge mode
- or to precise QoS parameters (Peak_Throughput_Class, Radio_Priority)
MS
BSS
Packet Channel request

scenario 2 : one UL block is assigned
Packet Uplink Assignment
Packet Resource request
3a
3b

5

Packet Uplink assignment, polling
RLC data block
5a
5b
5c
Figure 6 : 2 Phase access UL TBF establishment by MS in packet idle mode on PCCCH

(1) Packet Access procedure : the Packet Channel Request message is received on PRACH,
indicating a 2 phase access.
(2) Packet access reject procedure : same as for 1 phase access UL TBF establishment by MS in
packet idle mode on CCCH, but on a PCCCH slot.
(3a) A Packet Uplink Assignment message is sent to MS providing the definition of 1 UL radio block
(assigned PDCH, starting_time identifying the first frame number of the single block) and the initial
TA value. The message is sent on the same PCCCH on which the network has received the Packet
Channel request. Note that no TFI, no USF and no TAI are assigned yet to the MS, i.e. the MS is not
known by the network until receipt of the Packet Resource Request message.
The time duration between the receptionof the Packet Channel request and the UL radio block
allocated to the MS is defined by the timer T_ul_assign_pcch.
(3b) At occurrence of the allocated UL radio block, the MS provides detailed informations about
requested UL resources. TLLI is also given by the MS which allows contention resolution at network
side.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(4) Packet Access Reject procedure : same as (2), but on the PACCH. The TBF is released. Note that
resources are either granted immediately or the request is rejected.
(5) Packet resource UL assignment & Contention resolution:
(5a) Packet Uplink assignment is sent to MS on the PDCH from which it received the Packet
Resource Request, assigning a TFI, the PDCH(s) carrying the TBF with their respective USF(s), the
TA channel and TAI. TLLI is also given by the network which allows contention resolution at the MS
side. No initial timing advance is provided here, but the MS uses the value previously received from
the network. The network forces the MS to send a Packet Control Acknowledgement to be sure that
the UL TBF has been successfully established.
(5c) The MS transmits uplink blocks when allowed by the network (see 5).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.4 Two phase access UL TBF establishment initiated by MS in packet idle on CCCH
A 2 phase access is necessary, when the MS wants
- either to use RLC unacknowledge mode
- or to precise QoS parameters (Peak_Throughput_Class, Radio_Priority)
- or to give its multi-slot class
MS
BSS
Channel request
Immediate assignment reject

scenario 2 : one UL block is assigned
Immediate assignment
3a
Packet resource request
3b

Packet uplink assignment, polling
5a
5b
RLC data block
5c
Figure 7 : 2 Phase access UL TBF establishment by MS in packet idle mode on CCCH

(1) Packet access procedure : the Channel Request message is received on RACH, indicating a
request for a single block.
(2) Packet access reject procedure : An Immediate Assignment Reject message is sent to the MS on
the same CCCH timeslot on which the Channel Request message was received in case the access
request can not be satisfied. One reject cause will be used :
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(3a) Immediate assignment is sent to MS providing the radio definition of 1 UL radio block ( assigned
PDCH, starting_time identifying the first frame number belonging to the single block granted for
packet access). The message is sent on the same CCCH on which the network has received the
channel request. Note that no TFI, no USF and no TAI are assigned yet to the MS, i.e. the MS is not
known by the network until receipt of Packet Resource Request. Initial timing advance is provided to
the MS.
The time duration between the reception of the Channel Request message and the uplink radio block
allocated to the MS is defined by the timer T_ul_assign_ccch.
(3b) The MS provides in the assigned UL radio block detailed informations about requested UL
resources. TLLI is also given by the MS which allows contention resolution at network side.
(4) Packet Access Reject procedure on the PACCH (PDCH assigned in 3a): One reject cause will be
used :
(5) Packet resource UL assignment & Contention resolution:
(5a) Packet Uplink assignment is sent on PACCH (PDCH assigned in 3a) to MS assigning a TFI, the
PDCH(s) carrying the TBF with their respective USF(s), the TA channel and the TAI.TLLI is also
given by the network which allows contention resolution at the MS side. Initial timing advance is not
provided to MS (no way to compute it), but the MS uses the value previously received from the
network. The network forces the MS to send a Packet Control Acknowledgement to be sure that the
UL TBF has been successfully established.
(5c) The MS transmits uplink blocks when allowed by the network (see 5).
Note : the access type single block on CCCH can only be used by the MS to send a Packet
Resource Request, since Packet Measurement Report is not supported.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.5 UL TBF establishment initiated by MS in packet transfer mode
MS
BSS
On-going DL transfer
Figure 8 :
UL TBF
RLC data block with polling bit

Packet channel access phase
Packet downlink ack/nack

request is rejected
Packet access reject

OR request is accepted
4a
4b
Start of UL transfer
RLC data block
establishment by MS in packet transfer mode

(1) DL transfer : the MS is in packet transfer mode
(2) Packet access procedure :
The MS requests establishment of an UL TBF by including a Channel Request description IE in the
Packet downlink ack/nack message sent on PACCH/U of DL TBF. The Channel request description
shall indicate the same MAC mode as the DL TBF in operation and provides the DL TFI.
The network may reject the request by sending a Packet Access Reject on the PACCH/D of the DL
TBF. One reject cause will be used by the network:
Wait : this forces the MS to return to stop the on-going access procedure and prevents him
to perform a new attempt for packet access in the same cell until a provided wait value
(equal to WI_PR or WI_PA) expires.
(4) Packet channel UL assignment :
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(4a) the network may send a Packet Uplink Assignment to the MS on the PACCH/D of the DL TBF
assigning an UL TFI, the PDCH(s) carrying the TBF with their respective USF(s), the UL TA channel
and the UL TAI. No initial timing advance value is provided to the MS, which anyway already owns a
valid value. On receipt of that message, the MS listens the PDCHs assigned for UL and DL transfers.
The network forces the MS to send a Packet Control Acknowledgement to be sure that the UL TBF
has been successfully established.
This acknowledgement is supervised by T_ack_Wait.
(5) The MS transmits uplink blocks when allowed by the network (see 5). No TLLI is provided in
Uplink RLC blocks in that case. But the network is already aware of MS identity through the DL TFI.
Notes : D protocol does not allow UL access queuing in that case. Resources are therefore granted
only if immediately available.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.6 UL TBF resources modification initiated by MS
MS
BSS
RLC data block
Packet resource request

Packet access reject
OR
4a
4b
RLC data block
Figure 9 : UL TBF resources modification by MS

(1) on-going UL transfer
Packet resource request procedure :
(2) the MS requests on PACCH new resources for the UL TBF and starts timer T3168. This may be
new throughput or new service precedence.
Two cases have to be foreseen:
- A) the requested RLC mode is different from the RLC on-going mode
- B) the requested RLC mode is the same than the RLC on-going mode
A) Packet access reject procedure :
(3) The network rejects the request in case the requested RLC mode is not the on-going one with the
cause value Read System Information to force the MS to immediately stop the uplink data transfer.
B) Packet resource UL assignment
(4a) The network assigns the same radio resources to the MS (unless some radio resources have
become unavailable). On receipt of Packet uplink assignment, MS stops timer T3168. At T3168
expiry, the MS retransmits the Packet resource request. No initial timing advance value is provided
by the network, but MS already owns a valid one. A Packet Control Acknowledgement is requested
by the network only for homogeneity of the assignment procedure in RRM.
(4b) The MS acknowledges the receipt of the Packet Uplink Assignment. That message is not
handled by the network.
(5) The UL transfers goes on assigned resources at receipt of Packet Uplink Assignment, or is
aborted in case of Packet Access reject.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.7 DL TBF establishment initiated by network for MS in packet idle mode on PCCCH
MS
BSS
Packet DL Assignment, polling
Packet Control Acknowledment
Packet power ctrl / Timing advance

RLC/MAC block
Figure 10 :
DL TBF
establishment for MS in packet idle mode on PCCCH

(1) A Packet DL Assignment message is sent on PCCCH assigning a TFI, the PDCH(s) carrying the
TBF, the TA channel and the TAI. No initial timing advance is provided. The network forces the MS to
send a Packet Control Acknowledgement message to be sure that the DL TBF has been successfully
established and to be able to compute a timing advance value.
The timer Max_PDA_Lifetime is activated to wait for the acknowledge.
On receipt of Packet Downlink Assignment, the MS starts timer T3190.
(2) MS acknowledges the receipt of the Packet DL assignment on the same PCCCH slot. In case that
message is not received by the network, the DL TBF establishment procedure is completely retried
up to Max_Retrans_DL times.
(3) The network sends to the MS on PACCH the initial timing advance (to be used by MS when
sending Packet DL ack/nack message).
(4) The MS stops T3190 on receipt of the first valid RLC/MAC block. If T3190 expires, MS aborts the
procedure and returns to packet idle mode.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.8 DL TBF establishment initiated by network for MS in packet idle mode on CCCH
MS
BSS
Immediate Assignment 1
Wait Timer T_assign_pch/agch_pacch
Packet DL Assignment, polling 2
Packet Control Acknowledment 3
Packet power ctrl / Timing advance 4
RLC/MAC block
Figure 11 : DL TBF establishment for MS in packet idle mode on CCCH

(1) First assignment message is sent on CCCH (PCH or AGCH if the MS is in non DRX mode) to MS
to assign a TFI, one PDCH (PACCH slot) and the TAI.
(2) After expiration of timer T_assign_pch_pacch (or T_assign_agch_pacch), a Packet DL
Assignment message is sent on PACCH assigning the PDCH(s) carrying the TBF, the same TA
channel and same TAI. No initial timing advance is provided. The network forces the MS to send a
Packet Control Acknowledgement message to be sure that the DL TBF has been successfully
established and to be able to compute a timing advance value. For recall, this second assignment
performed on PACCH is necessary since the network can not assign a multislot TBF on CCCH
channel and can not otherwise compute an initial timing advance.
The timer T_assign_pch/agch_pacch is restarted.
On receipt of the Immediate assignment message, the MS starts timer T3190.
(3) MS acknowledges the receipt of the Packet DL assignment on the PACCH,
T_assign_pch/agch_pacch is stopped. In case that message is not received by the network, at expiry
of T_assign_pch/agch_pacch, the Packet DL Assignment message is sent to the MS on PACCH
(attempts are limited by an O&M parameter: Max_GPRS_assign_pch_retrans or
Max_GPRS_assign_agch_retrans)
(4) The network provides on PACCH the MS with initial timing advance (to be used by MS when
sending Packet DL ack/nack message).
(5)The MS stops T3190 on receipt of the first valid RLC/MAC block. If T3190 expires, MS aborts the
procedure and returns to packet idle mode.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.9 DL TBF establishment initiated by network for MS in packet transfer mode

MS
BSS
RLC/MAC block
Packet Downlink Assignment, polling 2

Packet Control Acknowledgment 3
Packet power ctrl / Timing advance 4
RLC/MAC block
Figure 12 : DL TBF establishment for MS in packet transfer mode

(1) The MS is in packet transfer mode
(2) The message, sent on PACCH/DL of UL TBF, assigns a DL TFI, the PDCH(s) carrying the TBF,
the DL TA channel and the DL TAI. No initial timing advance value is provided here. But the MS owns
already a correct TA. The network forces the MS to send a Packet Control Acknowledgement to be
sure that the DL TBF has been successfully established.
On receipt of Packet Downlink Assignment, the MS starts timer T3190.
(3) MS acknowledges on PACCH/U of UL TBF the receipt of Packet downlink assignment. In case
that message is not received by the network, the DL TBF establishment procedure is completely
retried up to Max-Retrans_DL times.
(4) This message is not necessary (the MS has already received a TAI, when the UL TBF was
established), but it is used to have only one process for DL TBF establishment.
DL procedure.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.2.10
Fast DL TBF re-establishment
At the end of a DL TBF, the MS waits on the PACCH during T3192. This, in particular allows the BSS
to send again the last DL RLC data block in case the MS acknowledgement is not received.
The BSS may also take the opportunity to re-establish a DL TBF on the PACCH of the previous DL
TBF while the timer T3192 is running at the MS side.
This allows a fast DL TBF re-establishment without impacting the (P)CCCH resources.
MS
BSS
last RLC/MAC block (1)
Packet DL ACK/NACK (2)
T3192
T3193
Packet DL Assignment + polling (4) (PACCH)

Packet Control Ack (5)
T3190
DL LLC PDU (3)

T_Ack_Wait
Packet power ctrl/Timing advance (6)

RLC/MAC block (7)
Figure 13 : DL TBF establishment for MS in packet transfer mode

(1) The last block of a DL TBF is sent (FBI = 1)
(2) The MS acknowledges the received block and activates the T3192 timer, during which it listens to
the PACCH of the DL TBF.
At the acknowledgement reception, the BSS activates T3193 during which radio resources are
still reserved for the MS: PDCHs, TAI and the TFI.
(3) A DL LLC PDU is received, for this MS, during the T3193 activation,
If t3193 > T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin then a DL TBF re-establishment
is triggered. (see next figure)Otherwise the DL LLC PDU is queued until T3193 expiry and an
assignment is subsequently sent on (P)CCCH.
(t3193 is the time remaining before expiry of T3193, when the DL LLC PDU is received))
(T_fast_DL_margin ( 50 ms) is added to take into account the fact that the variable round trip
delay is defined at GCH level)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
single trip
delay
DL LLC PDU
t3193
MFS
t
T3193
Packet DL Ack/Nack
Packet DL assignment
MS
t
T3192
(4) The Packet DL Assignment is sent on PACCH/DL of the previous DL TBF, it assigns the radio
resources (TFI, TAI, PDCHs) which were used by the previous DL TBF. No initial timing advance
value is provided. The network forces the MS to send a Packet Control Acknowledgement to be sure
that the DL TBF has been successfully established.
The timer T_ack_wait is activated to wait for the acknowledgement.
On receipt of Packet Downlink Assignment, the MS stops T3192 and starts timer T3190.
(5) MS acknowledges the receipt of the DL assignment on PACCH.
In case that message is not received by the network, and if Max_Retrans_DL is not reached
- t3193 is re-evaluated
If t3193 > T3193 - T3192 + Round_Trip_Delay + T_Fast_DL_margin then a new attempt is
undertaken on PACCH
Otherwise ( t3193 T3193 - T3192 + Round_Trip_Delay + T_Fast_DL_margin) then an
attempt is undertaken on (P)CCCH after expiry of T3193
(6) This message is not necessary (the MS performs the continuous timing advance update process,
during T3192), but it is used to have only one process for DL TBF establishment.
DL procedure.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.3 Paging
Paging CS is received by the MFS, only when the Gs interface is supported (i.e. NMO I)
4.1.3.1 PS or CS Paging procedure for MS in packet idle mode when there is a MPDCH
MS
BSS
Packet Paging Request
Figure 14 : PS or CS Paging for MS in packet idle mode in cell with MPDCH

(1) The network sends a paging request to the MS on a PPCH subchannel according to IMSI and the
DRX parameters of the MS to be paged. If the DRX parameters are not available (only possible for a
PS Paging), the paging request is sent on the paging block defined by the IMSI (which may leads to
an extension of the paging duration).
4.1.3.2 PS or CS Paging procedure for MS in packet idle mode when there is no MPDCH
MS
BSS
Paging Request
Figure 15 : PS or CS Paging for MS in packet idle mode in cell without MPDCH

(1) The network sends a paging request to the MS on a PCH subchannel according to the IMSI of
the MS to be paged.
4.1.3.3 CS Paging procedure for MS in packet transfer mode
MS
BSS
Paging Request
Figure 16 : CS Paging for MS in packet transfer mode

(1) The network sends a paging request to the MS on the PACCH subchannel.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.1.4 Packet radio resource handling

4.1.4.1 Packet PDCH Release
MS
Figure 17 :
Packet
PDCH
release
procedure
BSS
Packet PDCH release
When one or several PDCH(s) shall be released, the network indicates that these timeslots are no
longer available for packet data service by broadcasting a Packet PDCH release on the PACCH of
the MSs which are impacted.
When the MS receives a Packet PDCH release, it stops immediately transmitting on that PDCH
which is removed from its list of assigned PDCHs.
Resources on the released PDCH(s) are frozen during timer T 3169 in UL, and T3191 in DL. The
PDCHs may be given back to the BSC afterwards.
If the list of assigned PDCHs, for a MS, becomes empty, the MS returns in Packet idle mode.
4.1.4.2 Packet System Information provisioning (B6.2 SMG29)
MS
BSS
Packet System Information
Figure 18 : Packet System Information broadcast procedure

(1): Only from B6.2 SMG29.
According to MPDCH presence:
- MPDCH presence:
PSI1, PSI2 and PSI3 are broadcast on PBCCH.
PSI1 is sent on PACCH.
- no MPDCH:
PSI13 is broadcast on PACCH
Support of GPRS is indicated on BCCH through SI3/4 and SI13.
MPDCH location is indicated in SI13.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4.2
PDU definition
4.2.1 PDU description

The following PDUs are used (Refer to D and [E]):
- Packet Access Reject (B6.2 SMG29)
- Packet Channel Request (B6.2 SMG29)
- Packet Resource Request
- Packet Uplink Assignment
- Packet Downlink Assignment
- Packet Paging Request (B6.2 SMG29)
- Packet System Information Type 1 (B6.2 SMG29)
- Packet System Information Type 3 bis (B6.2 SMG29)
- Packet Control Acknowledgement
Note : MAC provides RRM with the TFI for which the block was reserved.
- Packet PDCH Release
- Packet Power Control / Timing Advance
- Channel Request
- Immediate Assignment
- Immediate Assignment Reject
An MFS internal PDU PCC-UL-CHN2-REQ is used.
It corresponds to an UL TBF establishment request vehiculed through a Packet Downlink Ack/Nack.
Information elements
PDU type
Channel_request_description
IE
Presence
M
M
Length
Semantic
PCC-UL-CHN2-REQ
Refer to D
4.2.2 Information Element description

Refer to D..
4.3
Protocol error handling
At receipt of a non-distribution message, a GPRS MS may (option for R97 MS, mandatory for R98
MS) send a PACKET MOBILE TBF STATUS message when in packet transfer mode to notify a
protocol error, i.e syntactically incorrect message or message not compliant with its automaton state.
The peer to peer protocol used in B6.2 is rather simple, especially for GPRS MS in packet transfer
mode. As such mechanism would only be invoked in quite rare cases (e.g. not expected in case of
first assignment message), it is not really considered as an added value to help debugging of MS /
BSS interworking issues.
Consequently the PACKET MOBILE TBF STATUS PDU is ignored by the MFS.
To be completed : protocol error handling at network side.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.
LAYER DYNAMIC MODEL
5.1
Inter-entities communication
Only the main scenarios are depicted in the first section of that chapter to provide a global
understanding of layer scenarios.
In following scenarios, it shall be ensured that :
at most 500 ms are spent between the receipt by (MAC) of the Packet Channel Request
message and the sending by (MAC) of the Packet Uplink Assignment or Packet Access
Reject message
at most 200 ms are spent between the receipt by (BSCGP) of the Channel Request
message and the sending by (BSCGP) of the Immediate Assignment or Immediate
Assignment Reject message
5.1.1 Packet connection control

When FSM states are used in the MSC, they correspond to states used in SDL diagrams (see 5.3.6)
5.1.1.1 One phase access UL TBF establishment on CCCH
When CCCH is used, 2 assignment messages are sent:
- an Immediate Assignment on CCCH (PCH or AGCH when the MS is in non DRX mode)
- then, a Packet DL Assignment on PACCH
It is not possible to know precisely when the Immediate Assignment will be sent on PCH (depends on
BS_PA_MFRS which defines the number of 51-multi-frames between consecutive occurences of
paging group) or on AGCH (depends on BS_AG_BLKS_RES which defines the number of CCCH
blocks, reserved for AGCH, in a 51-multiframe)
But not to damage performances, the time between the 2 messages has not to be too long.
This means that sometimes, it may occur that the MS receives the Immediate Assignment too late.
Indeed, the Immediate Assignment has to be sent on the PCH corresponding to the MS paging
group.
To cope with this, the Packet DL Assignment is resent if the Packet Control Acknowledgement is not
received in the scheduled UL block, after T_assign_pch_pacch or T_assign_agch_pacch expiry
(attempts are limited by an O&M parameter: Max_GPRS_assign_pch_retrans or
Max_GPRS_assign_agch_retrans).
When all attempts have failed, the DL TBF establishment procedure is restarted from the beginning,
provided Max_Retrans_DL is not reached.
When the Packet Control Acknowledgement is not received, before undertaking a new attempt, it is
checked if there is not an UL TBF (in this case, the new attempt would be sent on PACCH/UL)
Nominal case :
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
BSCGP
RLC
RRM
BSSGP
idle
PCC-UL-CHN-REQ-ind (1)
(2)
PRH-PDTCH-ASSIGN-req (3)
WURadio
PRH-PDCTCH-ASSIGN-cnf
PCC-RLC-ESTABLISH-req (4)
WUETBF
PCC-RLC-ESTABLISH-cnf
RL-UL-START-req
WULSP
RL-UL-START-cnf
PCC-CHN-ASSIGN-req (5)
WUGSM
T_Assign_agch
_pacch (6)
PCC-UL-Assign-req + polling (7)

WUMS
PCC-CTRL-ACK-ind (8)
T_Assign_agch
_pacch
PCC-RLC-ACTIVATE-req (9)
WUATBF
PCC-RLC-ACTIVATE-cnf
Uready
Figure 19 : One Phase access UL TBF establishment on CCCH - nominal scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1) UL channel access request is received from RACH through (BSCGP) PCC
(2) PCC requests PRH to allocate radio resources for the TBF
(PRH may activate a PDCH allocation procedure, if necessary)
(3) A throughput is reserved for the TBF in (MAC) layer
(4) Establishment of TBF context within (RLC) layer
(5) An assignment message is sent to the MS on AGCH
(6) PCC waits for T_assign_agch_pacch
(7) An assignment message is sent to the MS on PACCH with polling requested
T_assign_agch_pacch is restarted, in order to undertake a new attempt, in case of no
acknowledgement reception (at the last attempt T_Ack_Wait is started instead of
T_assign_agch_pacch)
(8) The MS acknowledges the previous message
(9) RRM requests MAC layer to start scheduling of radio blocks
Error case :
BSCGP
RRM
PCC-CHN-ASSIGN-req (reject) (3)
(2)
Figure 20 : One Phase access UL TBF establishment on CCCH - error scenario

(1) UL channel access request is received from RACH through (BSCGP) PCC
(2) Unsuccessful allocation of radio resources for the new packet connection : resource allocation
request is rejected.
(3) An access reject message is returned to the MS on CCCH
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.2 One phase access UL TBF establishment on PCCCH or PACCH

This paragraph is relevant for :
one phase access UL TBF establishment by MS in packet idle mode on PCCCH
UL TBF establishment by MS in packet transfer mode on PACCH
Nominal case :
RLC
RRM
BSSGP
idle
PCC-UL-CHN-REQ-ind OR
PCC-UL-CHN2-REQ-ind (1)
(2)
WURadio
PRH-PDTCH-ASSIGN-cnf
WUETBF
RL-UL-START-req
WULSP
PCC-UL-ASSIGN-req polling (5)
RL-UL-START-cnf
WUMS
WUATBF
UReady
Figure 21 : One Phase access UL TBF establishment on PCCCH/PACCH - nominal scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1) UL channel access request is received either from PRACH (PCC-UL-CHN-REQ-ind) or PACCH
(PCC-UL-CHN2-REQ-ind) through (RLC) PCC
(3) A throughput is reserved in (MAC) layer for the TBF
(4) A TBF context is created in (RLC) layer
(5) An assignment message is sent to the MS on PAGCH or PACCH, with polling requested
(6) The MS acknowledges the receipt of the assignment message
(7) PCC requests (MAC) layer to start scheduling radio blocks
Error case :
RLC
RRM
PCC-UL-REJECT-req (3)
(2)
Figure 22 : One Phase access UL TBF establishment on PCCCH/PACCH - error scenario

(1) UL channel access request is received from PRACH or PACCH through (RLC) PCC
(2) Unsuccessful allocation of radio resources for the new packet connection : resource allocation
request is rejected.
(3) An access reject message is returned to the MS on AGCH or PACCH
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.3 2 phase access UL TBF establishment on CCCH

BSCGP
RLC
RRM
BSSGP
idle
(2)
PRH-BLOCK-RESERVE-req (3)
PRH-BLOCK-RESERVE-cnf
idle
PCC-UL-RES-REQ-ind (5)
(6)
WURadio
PRH-PDCTCH-ASSIGN-cnf
WUETBF
RL-UL-START-req
WULSP
RL-UL-START-cnf
WUMS
WUATBF
Uready
Figure 23 : 2 Phase access UL TBF establishment on CCCH nominal scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1) Access request is received from RACH indicating 2 phase access

(2) PCC requests PRH to allocate 1 UL radio block
(3) One UL radio block is reserved at (MAC) layer
(4) Assignment message is sent to MS on CCCH
(5) MS requests resources
(6) PCC requests PRH to allocate radio resources for the TBF.
(7) A throughput is reserved at (MAC) layer for the TBF.
(8) Establishment of TBF context within (RLC) layer
(9) Assignment message is sent to the MS on PAGCH on the same PDCH on which the network has
received the Packet resource request, with polling requested
(10) MS acknowledges receipt of assignment message
(11) PCC requests (MAC) layer to start allocation of radio blocks
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.4 2 phase access UL TBF establishment on PCCCH

RLC
RRM
BSSGP
idle
(2)
PRH-BLOCK-RESERVE-req (3)
PRH-BLOCK-RESERVE-cnf
PCC-UL-ASSIGN-req (4)
idle
PCC-UL-RESOURCE-REQ-ind (5)
(6)
WURadio
(6)
WETBF
RL-UL-START-req
WULSP
RL-UL-START-cnf

WUMS
WUATBF
UReady
Figure 24 : 2 Phase access UL TBF establishment on PCCCH nominal scenario

Same comments as for previous case.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.5 DL TBF establishment on CCCH

When CCCH is used, 2 assignment messages are sent:
- an Immediate Assignment on CCCH (AGCH)
- then, a Packet UL Assignment on PACCH
It is not possible to know precisely when the Immediate Assignment will be sent on AGCH (depends
on BS_AG_BLKS_RES which defines the number of CCCH blocks, reserved for AGCH, in a 51multiframe)
But not to damage performances, the time between the 2 messages has not to be too long.
This means that sometimes, it may occur that the MS receives the Immediate Assignment too late
and thus the MS will not be able to receive the Packet UL Assignment.
To cope with this, the Packet UL Assignment is resent if the Packet Control Acknowledgement is not
received in the scheduled UL block, after T_assign_agch_pacch expiry (attempts are limited by an
O&M parameter: Max_GPRS_assign_agch_retrans)
BSCGP
RLC
RRM
idle
LLC-PDU (1)
(2)
WDRadio
WDETBF
WDGSM
T_assign_pch/agch
_pacch (6)
PCC-DL-ASSIGN-req (7)
WDMS
T_assign_pch/agch
_pacch
PCC-TA-UPDATE-req (9)
WDATBF
(11)
DReady
Figure 25 : DL TBF establishment on CCCH nominal scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1) Receipt of a DL TBF establishment request (i.e. LLC-PDU reception, with no DL TBF for this MS)
(3) A throughput is reserved at (MAC) layer for the TBF
(4) establishment of TBF context within (RLC) layer
(5) The PACCH slot is assigned to the MS on CCCH
(6) PCC waits for T_assign_pch_pacch (or T_assign_agch_pacch).
(7) The PDCHs carrying the TBF are assigned to the MS on the PACCH slot
T_assign_pch/agch_pacch is restarted, in order to undertake a new attempt, in case of no
acknowledgement reception (at the last attempt T_Ack_Wait is started instead of
T_assign_pch/agch_pacch)
(8) MS acknowledges the previous message.
(9) The initial TA value is computed and provided to the MS.
(10) PCC requests (MAC) layer to start allocating radio blocks for the TBF
(11) PCC confirms the DL TBF establishment to TRN.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.6 DL TBF establishment on PCCCH/PACCH

RLC
RRM
idle
LLC-PDU (1)
(2)
WDRadio
WDETBF
PCC-DL-ASSIGN-req (5)
WDMS
PCC-TA-UPDATE-req (7)
WDATBF
(9)
DReady
Figure 26 : DL TBF establishment on PCCCH/PACCH nominal scenario

Same comments as in previous case, but there is no primary assignment on CCCH.
((1) to (4) see the same notes in previous figure, (5) to (9) see (7) to (11) in the previous figure)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.6. Fast DL TBF re-establishment

RLC
RRM
BSSGP
DReady
T_TBF_REL
TRN-DL-FLOW-END-ind (1)
TRN-DL-FLOW-END-res
(2)
WDREL
(3)
PCC-RLC-RElease-ind (4)
T3193
WDRRadio
PCC-RLC-Establish-req (6)
RL-DL-UNITDATA-ind (5)
WDETBF
PCC-RLC-Establish-cnf
PCC-DL-Assign-req (7)
WDMS
PCC-DL-Assign-cnf
PCC-TA-Update-req
PCC-RLC-Activate-req
WDATBF
PCC-RLC-Activate-cnf
DREADY
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- (1): When only one RLC data block remains to be sent, T_TBF_REL is activated, at RLC level.
At timer expiry, if no further DL data has been received, the release protocol is started (RRM is
requested to stop
the transfer of DL LLC PDU for that TBF).
- (2):
At RRM acknowledgement, the last RLC block is sent by RLC with FBI set.
- (3):
At MS acknowledgement reception, the context is released in RLC and RRM is notified.
- (4):
At the Release indication reception, RRM freezes radio resources (PDCHs, TAI and TFI) and
activates the timer T3193.
- (5):
If a DL LLC PDU, is received during T3193, a fast DL TBF re-establishment is triggered (if
t3193 > T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin)
- (6):
A context is created at RLC level.
- (7):
A Packet DL Assignment is sent to the MS on the PACCH of the previous TBF.

Then the usual process to establish a DL TBF is undertaken.
5.1.1.7 One phase access contention resolution

RLC
RRM
PCC-TLLI-NOTIFY-ind (1)
Figure 27 : One Phase access contention resolution scenario
(1) TLLI provided in the first correctly received UL RLC data block is notified to RRM
Note : RRM receives the TLLI before any UL LLC PDU.
5.1.1.8 Coding scheme adaptation notification
RLC
RRM
PCC-RLC-MODIFY-ind (1)
Figure 28 : Coding scheme adaptation notification

(1) The change of UL TBF coding scheme performed by RLC layer is notified to RRM, in order to
allow RRM to send the correct coding scheme when further uplink assignments are sent following a
Packet Resource Request
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.9 DL TBF Release initiated by (RRM) PRH

RLC
RRM
PCC-RLC-RELEASE-req (2)
(1)
WDRTBF
(3)
PCC-RLC-RELEASE-cnf
Figure 29 : DL TBF release scenario initiated by (RRM) PRH

(1)
(2)
(3)
ED
MCD
A TBF has been released (resources have been deallocated in MAC layer).
RLC is notified
RLC stops the data transfer (the MS will abort the DL TBF at T3190 expiry)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.10
UL TBF Release initiated by (RRM) PRH
RLC
RRM
(1)
PCC-RLC-RELEASE-req (2)
(3)
BSSGP
PCC-RLC-RELEASE-cnf
WURTBF
RL-UL-STOP-req (4)
Figure 30 : UL TBF release scenario initiated by (RRM) PRH

(1) A TBF has released (resources have been deallocated in MAC layer).
(2) RLC is notified
(3) RLC releases its context (As resources have been deallocated at MAC layer, the MS will receive
no more its USF and it will undertake a release on T3180 expiry)
(4) BSSGP is informed that the UL TBF has been released
5.1.1.11
DL TBF Release initiated by (RLC)
RLC
RRM
BSSGP
PCC-RLC-RELEASE-ind (1)
PRH-PDTCH-DEASSIGN-req (3)
PRH-PDTCH-DEASSIGN-cnf
(2)
GMM-RADIO-STATUS-req (4)
Figure 31 : DL TBF release scenario initiated by (RLC)

(1) (RLC) layer notifies a normal or abnormal TBF termination
(2) TBF radio resources are deallocated
(3) Radio resources are released at (MAC) layer
(4) In case of abnormal release, a GMM-RADIO-STATUS-req message is sent to SGSN
Note : Any DL LLC PDU that would be sent by (RRM) while (RLC) notifies to (RRM) the TBF release
is discarded by (RLC). Such case may only occur for DL TBF abnormal termination : in case of DL
TBF normal release, (RRM) is informed of the decision taken by (RLC) to terminate the DL TBF (see
5.1.3.5).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.1.12
UL TBF Release initiated by (RLC)
RLC
RRM
BSSGP
(2)
RL-UL-STOP-req (4)
Figure 32 : UL TBF release scenario initiated by (RLC)

(1) (RLC) layer notifies a normal or abnormal TBF termination
(2) the TBF radio resources are deallocated
(3) Radio resources are released at (MAC) layer
(4) BSSGP is notified that the UL TBF has been released, in order to deallocate the corresponding
throughput.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.2 Packet radio resource handling

Note: in the following sections, "PDCH group" can be replaced by "cell" as in GPRS step 1, there is
only one GPRS group per cell.
5.1.2.1 PDCH dynamic allocation
BSC
BSCGP (PRH)
RRM (PRH)
PRH-PDCH-ALLOCATE-req
ALLOCATION REQUEST(1)
ALLOCATION CONFIRM (2)
PRH-PDCH-ALLOCATE-cnf
Figure 33 : PDCH dynamic allocation scenario, successful case
(1):
(2):
of
The MFS indicates the PDCH group and the total number of PDCH requested in the PDCH
group, to serve the GPRS MS request
The BSC allocates free timeslots for GPRS usage, see ref. [18], and gives the total number
allocated PDCHs in the PDCH group.
BSC
BSCGP
RRM
ALLOCATION REQUEST (2)
T_GSL_ACK
expiry
T_GSL_ACK
expiry
(3) PRH-PDCH-ALLOCATE-cnf (NOK)

(4)
Figure 34: PDCH dynamic allocation scenario, unsuccessful case

(1):
(2):
(3):
(4):
ED
MCD
BSCGP sends the ALLOCATION REQUEST to the BSC. No response is received.

BSCGP repeats the ALLOCATION REQUEST. No response is received.
The result is set to "NOK", cause "T_GSL_ACK timer expiry".
The traffic on the cell is stopped and
- in Pilot, A RESET procedure is undertaken.
- in B6.2 , a Cell Reset procedure is undertaken
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.2.2 PDCH dynamic deallocation
BSC
BSCGP (PRH)
RRM (PRH)
PRH-PDCH-DEALLOCATE-req
DEALLOCATION REQUEST(1)
DEALLOCATION CONFIRM (2)
PRH-PDCH-DEALLOCATE-cnf
Figure 35 : PDCH dynamic deallocation scenario, successful case

(1):
(2):
The MFS indicates the PDCH(s) to be deallocated.

The BSC deallocates corresponding timeslots.
BSC
BSCGP
RRM
PRH-PDCH-DEALLOCATE-req
DEALLOCATION COMMAND(1)
DEALLOCATION COMMAND (2)
T_GSL_ACK
expiry
T_GSL_ACK
expiry
(3) PRH-PDCH-DEALLOCATE-cnf (NOK)

(4)
Figure 36: PDCH dynamic deallocation scenario, unsuccessful case

(1):
(2):
(3):
(4):
ED
MCD
BSCGP sends the DEALLOCATION COMMAND to the BSC. No response is received.

BSCGP sends the DEALLOCATION COMMAND to the BSC. No response is received.
The traffic on the cell is stopped and
- in Pilot, A RESET procedure is undertaken.
- in B6.2 , a Cell Reset procedure is undertaken
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.2.3 MPDCH dynamic allocation (B6.2 SMG29)

BSC
BSCGP
RRM
RLC
PRH-SYS-DEFINE-req (1)
Mark Master Channel
PRH-SYS-DEFINE-cnf
PRH-CONF-MASTER-req
(2)
Mark Master Channel Ack
PRH-CONF-MASTER-cnf (3)
Figure 37 : MPDCH dynamic allocation scenario

(1):
PSI broadcast is requested.
(2):
The location of the master PDCH is broadcast in SI13
(3):
a
If the result in PRH-CONF-MASTER-cnf is NOK, then RRM stops the traffic on the cell and
GPRS STOP procedure is undertaken. RRM tries afterwards to restart the GPRS traffic and
to reallocate the MPDCH indefinitly.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.2.4 MPDCH dynamic deallocation (B6.2 SMG29)

RLC
BSCGP
RRM
RLC
PRH-DECONF-MASTER-req
Unmark Master Channel
(1)
Unmark Master Channel Ack

(2)
PRH-DECONF-MASTER-cnf
PRH-SYS-DEFINE-cnf
T_MPDCH_Deact
expiry
PRH-SYS-DEFINE-cnf
Figure 38 : MPDCH dynamic deallocation scenario
(1):
The location of the master PDCH is no more broadcast on SI13.
(2):
If the result in PRH-DECONF-MASTER-cnf is NOK , then RRM stops the traffic on the cell.
RRM retries afterwards to restart the GPRS traffic if not stopped by the operator (e.g. cell
lock).
(3):
The flag BS_PCC_REL is set in PSI1, indicating that the MPDCH will be released shortly.
(When the MS will read this indication, it will attempt to receive the SI13 message on BCCH.
The SI13 message will contain no more the PBCCH description and the MS will perform a
complete acquisition of BCCH messages). The timer T_MPDCH_Deact shall at least cover
the time needed to update the BCCH information, plus 2 times the PSI1_REPEAT_PERIOD
duration to allow the MS to receive at least 2 PSI1 after the BCCH has been updated.
(4):
PSI broadcast is stopped.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.2.5 PDCH establishment

RLC
RRM
PDCH dyn.
allocation
(3)
(4)
(1)
PRH-PDCH-ESTABLISH-req (2)
PRH-PDCH-ESTABLISH-cnf
Figure 39 : PDCH establishment scenario

(1):
(2):
(3):
(4):
The PDCH has been allocated by the BSC

with the following information: USFNE, access burst type, TSC, BS_TX_PWR
this request is sent to MAC
On MAC cnf reception, PRH-PDCH-ESTABLISH-cnf is sent to RRM
Now this resource can be used to establish TBFs.
5.1.2.6 PDCH release

RLC
RRM
PRH-PDCH-RELEASE-req (1)
(3)
(4)
PRH-PDCH-RELEASE-cnf
PRH-PDCH-RELEASE-ind (2)
PDCH
deallocation
(5)
Figure 40 : PDCH release scenario

(1) PDCH release requested by (RRM) layer
(2) Or PDCH release notified by L2-GCH layer (via MAC)
(3) this request is sent to MAC
(4) On MAC cnf reception, PRH-PDCH-RELEASE-cnf is sent to RRM
(5) The PDCH is deallocated at BSC level
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3 Data transfer

5.1.3.1 DL LLC PDU transfer
Nominal case
RLC
RRM
BSSGP
RL-DL-UNITDATA-ind
DL TBF
establishment
(2)
(1)
NM-FLOW-CONTROL-MS-req
NM-FLOW-CONTROL-MS-cnf
TRN-DL-UNITDATA-req (3)
Figure 41 : DL LLC PDU transfer scenario

(1) In case there is no on-going DL TBF for the addressed MS nor on-going TBF establishment, a
TBF is established.
Note : A timeout is attached to the request, indicating the latest time the connection should be
established, i.e. at timeout expiry, the DL TBF establishment is expected to be rejected by (RRM)
PCC. The timeout is set to PDU lifetime minus estimated time to transfer the PDU (defined by
PDU size and requested throughput). In case the DL TBF establishment is rejected, the PDU is
discarded.
(2) In B6.2 , A NM-FLOW-CONTROL-MS-req is sent to SGSN, via BSSGP.
A timer T_Flow_Ctrl_MS is activated to send periodically a NM-FLOW-CONTROL-MS-req.
(3) The DL LLC PDU is sent to (RLC)TRN entity when allowed by DL flow control, from RLC
Note: In case there is an on-going DL TBF at PDU receipt and the previous TLLI is replaced by a
new one, the TLLI change is notified to (RRM) PCC.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3.2 Receipt of an invalid DL LLC PDU

RRM
BSSGP
RL-DL-UNITDATA-ind
invalid PDU 1
NM-STATUS-req
Figure 42 : Receipt of an invalid DL LLC PDU scenario
(1) At receipt of an invalid PDU, the PDU is sent back to the SGSN in a NM-STATUS-req message.
5.1.3.3 DL LLC PDU deletion
RRM
BSSGP
NM-LLC-DISCARDED-req
Figure 43 : DL LLC PDU deletion scenario

MFS notifies SGSN that DL LLC PDU has been discarded, e.g. following PDU lifetime expiry.
5.1.3.4 DL TBF flow control with RLC
RLC
RRM
TRN-DL-FLOW-CTRL-ind (1)
Figure 44 : DL TBF flow control with RLC scenario
(1)
ED
MCD
XOFF or XON notification is sent to (RRM) TRN to respectively stop and restart the transfer
of DL LLC PDU towards (RLC) TRN.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3.5 DL TBF termination notification

RLC
RRM
TRN-DL-FLOW-END-res (3)
Figure 45 : DL TBF termination scenario
(1)
(2)
(3)
When (RLC) decides to terminate a DL TBF, it requests (RRM) TRN to stop the transfer of
DL LLC PDU for that TBF.
DL LLC PDU sent by (RRM) TRN before the receipt of the previous message are sent to
the MS by (RLC) TRN.
(RRM) TRN acknowledges the RLC request and stops transmitting to RLC PDU for that
MS.
When the DL TBF is then actually released, (RLC) PCC notifies (RRM) PCC of the TBF release. See
5.1.1.11.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3.6 DL LLC transfer with RLC mode modification
5.1.3.6.1
Current mode is unacknowledged mode

RLC
RRM
(1)
RL-DL-UNITDATA-ind
(Nack RLC mode) (2)
RL-DL-UNITDATA-ind
(Ack RLC mode) (4)
(5)
RL-DL-UNITDATA-ind (8)
TRN-DL-FLOW-END-res (7)
T3193
(11)
(12)
Figure 46 RLC mode modification (current mode is unacknowledged mode)

(1)
A DL TBF is on-going, with unacknowledged RLC mode (Nack)
(2)
A LLC-PDU is received, with the same RLC mode than the on-going TBF
(3)
The LLC-PDU is sent to RLC
(4)
A LLC-PDU is received, with a different RLC mode than the on-going TBF (Acknowledged
RLC mode)
(5)
The LLC-PDU is queued
(6)
RLC has no more LLC-PDU to send (the forwarding of the last LLC PDU is on-going)
(7)
RRM acknowledges
(8)
Whatever the RLC mode of the LLC-PDU, the LLC-PDU is queued
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(9)
RLC notifies the TBF termination.
(10)
TBF throughput is released
(11)
TBF context is freezed during T3193
(12)
At T3193 expiry, a DL TBF establishment, with acknowledged RLC mode is undertaken for
the queued LLC PDU.
5.1.3.6.2
Current mode is acknowledged mode
RLC
RRM
(1)
RL-DL-UNITDATA-ind
(Ack RLC mode) (2)
RL-DL-UNITDATA-ind
(Nack RLC mode) (4)
Figure 47 RLC mode modification (current mode is acknowledged mode)

(1)
A DL TBF is on-going, with acknowledged RLC mode (Ack)
(2)
A LLC-PDU is received, with the same RLC mode than the on-going TBF
(3)
The LLC-PDU is sent to RLC
(4)
A LLC-PDU is received, with a different RLC mode than the on-going TBF (Unacknowledged
RLC mode)
(5)
The LLC-PDU is sent to RLC to be sent in acknowledged mode
5.1.3.7 UL LLC PDU transfer

RLC (TRN)
RRM (TRN)
BSSGP (TRN)
TRN-UL-UNITDATA-ind
RL-UL-UNITDATA-req
Figure 48 : UL LLC PDU transfer scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3.8 Flush procedure

RRM (TRN)
BSSGP (TRN)
NM-FLUSH-LL-ind
(1)
NM-FLUSH-LL-res
Figure 49 : Flush scenario
Flush notification is received when MS, involved in a DL transfer, is moving from a source cell to a
target one. In such case, LLC PDUs are discarded and a response is sent back to SGSN notifying
the PDU deletion.
(1):
Resources are deallocated in MAC layer and a TBF release is requested to RLC.
5.1.3.9 MS Flow Control procedure (not in Pilot)

RRM (TRN)
BSSGP (TRN)
T_Flow_Ctrl_
MS expiry
Figure 50 : MS flow control scenario

The first NM-FLOW-CONTROL-MS-req is sent when a DL TBF is established (provided the last NMFLOW-CONTROL-MS-req has been sent since more than T_FLOW_CTRL_MS duration), then it is
sent periodically according to T_Flow_Ctrl_MS.
If an acknowledgement is not received, flow control parameters computation will be processed upon
2 periods, at the next expiry)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.3.10
BVC Flow Control procedure

RRM (TRN)
BSSGP (TRN)
NM-FLOW-CONTROL-BVC-req
NM-FLOW-CONTROL-BVC-cnf
T_Flow_Ctrl_
Cell expiry
NM-FLOW-CONTROL-BVC-req
Figure 51 : BVC flow control scenario

The first NM-FLOW-CONTROL-BVC-req is sent when the cell becomes available, for GPRS traffic.
The first forwarding may trigger a retry if the acknowledgement is not received. Others dont (flow
control parameters computation will be processed upon 2 periods, at the next expiry).
In Pilot, only the first NM_FLOW-CONTROL-BVC-req is sent (T_Flow_Ctrl_Cell is not used).
5.1.4 CS or PS Paging
BSCGP (PAG)
RLC (PAG)
[PAG-PAGE-MS-req]
RRM (PAG)
BSSGP (PAG)
GMM-Paging-PS/CS-ind
[PAG-PAGE-MS-req] OR
Figure 52 : CS or PS paging scenario

The PS paging message is sent to the relevant entities according to MPDCH configuration and, in
case of CS paging, according to MS packet mode (see 5.2).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5 Network Management

5.1.5.1 BSS creation
This MSC describes a BSS creation, with the administrative state set to locked.
LM
RRM
LM-BSS-create-req (locked)
BSSGP
NM-BVC-SIG-CREATE-req
NM-BVC-SIG-T-STATUS-ind
(operational,stopped) (2)
LM-BSS-create-cnf
(1)
LM-BSS-SET-req (unlocked) (3)
(4)
LM-BSS-SET-cnf
NM-BVC-SIG-START-req
(operational,started)
NM-NSE-CAPACITY-ind
(5)
(6)
Figure 53 BSS creation scenario (administrative state = locked)

(1):
a BVC-SIG context is created at BSSGP level
(2):
BVC-SIG status is returned to RRM.

(operational if the NSE is enabled)
(3):
the BSS is unlocked thanks to an O&M command.
(4):
If the BSCGP indication is BSS state = enabled, then a NM-BVC-SIG-START-req is sent to

BSSGP.
(5):
A BVC-SIG RESET procedure is undertaken
(6):
The available bandwidth, for traffic on Gb is notified.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.2 BSS lock

This MSC describes a BSS lock
LM
RRM
LM-BSS-SET-req (locked)
LM-BSS-SET-cnf
BSSGP
NM-BVC-SIG-STOP-req
(operational,stopped)
(2)
Figure 54 BSS lock scenario
(1):
All the NS-VCs of the corresponding NSE are blocked.
(2):
GPRS traffic is stopped for all cells belonging to this BSC

(NM-BVC-PTP-STOP-req, towards the BSSGP, is not necessary)
All the BVC-PTPs become not operational, stopped at BSSGP level.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(1)
5.1.5.3 BVC-SIG failure/recovery
BSSGP
RRM
NM-BVC-SIG-T-STATUS-ind (not operational, started)
(1)
(2)
NM-BVC-SIG-T-STATUS-ind (operational, started)
(3)
(4)
NM-BVC-PTP-T-STATUS-ind (operational, stopped) (5)

(6)
(1):
Following a BVC-SIG failure, RRM is notified.

All the corresponding BVC-PTP states become not operational, stopped, at BSSGP level
(2):
RRM stops the traffic in all the corresponding cells (PRH-PDCH-DEALLOCATE-req, NTMCELL-STOP-req).
(3):
RRM
When the BVC-SIG failure disappears, a BVC-SIG RESET procedure is undertaken and
is notified at the end of this procedure.
(4):
BVC-PTP RESET procedures are undertaken, followed by Block procedures;
(5):
RRM is notified when one of this procedure succeeds.
(6):
req,
If all the conditions are OK, GPRS traffic can be started in the cell (NM-BVC-PTP-STARTthen NTM-CELL-START-req).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.4 Cell creation

This MSC describes a cell creation, with the administrative state set to locked
LM
BSCGP
RRM
LM-cell-create-req (locked)
BSSGP
(1)
NM-BVC-PTP-CREATE-req (3)
NM-Cell-State-req (2)
LM-cell-create-cnf
(4)
NM-Cell-State-cnf
NM-BVC-PTP-STATUS-ind (operational,stopped)
(6)
(5)
Figure 55 Cell creation scenario (administrative state = locked)

(1):
A cell context is created.
(2):
Cell state is requested to the BSC
(3):
The BVC is created at BSSGP level
(4):
BVC-PTP Reset procedure is undertaken, but the BVC will remain in the blocked state (a
BLOCK procedure is undertaken, at the end of the RESET procedure)
(5):
BVC status is returned to RRM (operational+stopped in this case, since the BVC is
Blocked)
(operational NSE available + BVC-PTP reset procedure OK)
(stopped BVC blocked)
(6):
NM-BVC-STATUS-ind and NM-CELL-STATE-cnf are used to determine the operational

state of the cell.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.5 Cell unlock

This MSC describes the unlock of a cell, which operational state is enabled.
5.1.5.5.1
MPDCH supported (B6.2 SMG29)
BSCGP
LM
RRM
LM-cell-set-req (unlocked)
BSSGP
RLC
NM-BVC-PTP-START-req (1)
LM-cell-set-cnf
NM-BVC-PTP-T-Status-ind (op. + started) (3)
NTM-Cell-start-req (4)
(5)
NTM-Cell-start-cnf
PRH-PDCH-Allocate-req (7)
PRH-PDCH-Allocate-cnf
NM-Flow-Control-BVC-req (6)
NM-Flow-Control-BVC-cnf
PRH-PDCH-estab-req
PRH-PDCH-estab-cnf
(8)
PRH-SYS-Define-req (9)
PRH-Conf-Master-req (10)
(11)
PRH-SYS-Define-cnf
PRH-Conf-Master-cnf
Figure 56 Cell unlock scenario (MPDCH supported)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(2)
(1):
BSSGP is requested to start the BVC-PTP

(if BVC-PTP state is operational and if BSC indication is cell state = enabled)
(2):
The Unblock procedure is performed and RRM is notified of the BVC-PTP status (3)
(4):
Start-GPRS PDU is sent to the BSC (via BSCGP)
(5):
SI13 is broadcast, by the BSC, indicating no MPDCH
(6):
BVC flow control parameters are sent to the SGSN.

In B6.2 , T_Flow_Ctrl_Cell is activated for periodic flow control purpose
(7):
According to MIN_PDCH_Group value, PDCH allocation is requested to the BSC (via

BSCGP)
(8):
At PDCH allocation response, GCH links are established
(9):
PSI is broadcast on the PBCCH
(10):
A master PDCH is requested to the BSC (via BSCGP)
(11):
The BSC modifies SI13, giving MPDCH location, thus the MS will perform a complete
acquisition of PBCCH messages.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.5.2
MPDCH not supported
BSCGP
LM
RRM
LM-cell-set-req (unlocked)
BSSGP
RLC
LM-cell-set-cnf
NM-BVC-PTP-T-Status-ind (op. + started) (3)
(5)
NTM-Cell-start-cnf
PRH-PDCH-estab-req
PRH-PDCH-estab-cnf
(8)
PRH-SYS-Define-cnf
Figure 57 Cell unlock scenario (MPDCH not supported)

(1):
BSSGP is requested to start the BVC-PTP

(if BVC-PTP state is operational and if BSC indication is cell state = enabled)
(2):
The Unblock procedure is performed and RRM is notified of the BVC-PTP status (3)
(4):
(5):
(6):
BVC flow control parameters are sent to the SGSN.

In B6.2 , T_Flow_Ctrl_Cell is activated for periodic flow control purpose
(7):

BSCGP)
(8):
(9):
PSI13 is broadcast on the PACCHs (B6.2 SMG29 only)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(2)
5.1.5.6 Cell lock

This MSC describes the lock of one cell.
5.1.5.6.1
BSCGP
LM
RRM
LM-cell-set-req (locked)
RLC
BSSGP
(1)
PRH-PDCH-release-MS-req (2)
LM-cell-set-cnf
PRH-PDCH-Release-MS-cnf
NM-BVC-PTP-STOP-req (3)
PRH-Deconf-Master-req (6)
(7)
PRH-Deconf-Master-cnf
NM-BVC-PTP-T-Status-ind (oper. + stopped) (5)
PRH-SYS-DEFINE-cnf
T_MPDCH_Deact
expiry
PRH-SYS-DEFINE-cnf
PRH-PDCH-release-req
PRH-PDCH-Deallocate-req (11)
PRH-PDCH-release-cnf
(10)
PRH-PDCH-Deallocate-cnf
NTM-Cell-stop-req (12)
(13)
NTM-Cell-stop-cnf
Figure 58 Cell lock scenario (MPDCH supported)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(4)
(1):
The cell is available for GPRS traffic, before receiving the Lock command
(2):
Packet PDCH Release messages are sent on each PACCH of the cell
(3):
BSSGP is requested to stop the BVC-PTP

(for implementation constraints, this message may be sent later, to BSSGP)
(4):
BSSGP performs a BLOCK procedure
(5):
A NM-BVC-PTP-T-Status-ind is returned to RRM
(6):
PRH-Deconf-Master-req is sent to the BSC (via BSCGP) and T_MPDCH_Deact is

activated.
(7):
The BSC stops to indicate MPDCH location in SI13.
(8):
The flag BS_PCC_REL is set into PSI1, indicating that the MPDCH will be released shortly
(when the MS will read this indication, the MS will attempt to receive the SI13 message on
BCCH which will contain no more the PBCCH description and the MS will perform a
complete acquisition of BCCH messages). The timer T_MPDCH_Deact shall at least cover
the time needed to update the BCCH information, plus 2 times the
PSI1_REPEAT_PERIOD duration to allow the MS to receive at least 2 PSI1 after the
BCCH has been updated.
(9):
PSI broadcast is stopped, at T_MPDCH_Deact expiry.

(the MSs should have been returned on BCCH)
(10):
RLC is requested to release PDCHs at GCH level
(11):
A PDCH deallocation request is sent to the BSC (via BSCGP)

(delay between PRH-PDCH-RELEASE-MS-req and PRH-PDCH-DEALLOCATE-req has to
be greater than T3169 (UL)/T3191 (DL). The PDCHs not supporting the MPDCH may be
given back to the BSC before the PDCH supporting the MPDCH.
(12):
After having received the Deallocation acknowledgement, a Stop-GPRS is sent to the BSC
(13):
The BSC stops to broadcast SI13 and indicates on SI3/4 that the cell doesnt support
GPRS.
Note:
During all this procedure, the reception of a Packet Channel request triggers the emision of
a Packet Access reject with the cause Read System Information ; the reception of a
Channel Request received on RACH triggers the emission of an Immediate Assignment
Reject.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.6.2
MPDCH not supported
BSCGP
LM
RRM
LM-cell-set-req (locked)
RLC
BSSGP
(1)
LM-cell-set-cnf
(4)
PRH-SYS-DEFINE-cnf
(7)
(10)
NTM-Cell-stop-cnf
Figure 59 Cell lock scenario (MPDCH not supported)

(1):
The cell is available for GPRS traffic, before receiving the Lock command
(2):
(3):

(4):
(5):
(6):
PSI13 is no more sent (B6.2 SMG29 only)
(7):
(8):
(9):
(10):
The BSC stops to broadcast SI13 and indicates on SI3/4 that the cell doesnt support
GPRS
Note:
During all this procedure, the reception of a Channel Request received on RACH triggers
the emission of an Immediate Assignment Reject.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.7 Gb failure/recovery
This MSC describes a Gb interface failure
LM
RRM
RLC
BSSGP
(1)
LM-BSS-State-Change
(disabled, dependency)
NM-BVC-SIG-T-Status-ind (not oper., started) (2)
(3)
LM-BSS-State-Change
(enabled)
NM-BVC-SIG-T-Status-ind ( oper., started) (5)
(4)
(6)
NM-BVC-PTP-T-Status-ind (oper., stopped) (7)
(8)
Figure 60 Gb failure/recovery scenario

(1):
The BSS is operational, before receiving the NM-BVC-SIG-T-Status
(2):
The BVC-SIG status is not operational, started, which means that if the Gb failure
disappears, a BVC-SIG RESET procedure will be undertaken at BSSGP level and if this
procedure succeeds, RRM will be notified of the BVC-SIG new state operational, started.
Therefore, if during the Gb failure, the BSS becomes locked or unavailable for the BSC,
a NM-BVC-SIG-STOP-req has to be sent to BSSGP to modify the BVC-SIG state:
not operational, started not operational, stopped
At BSSGP level, all the corresponding BVC-PTP states become not operational, stopped
(3):
In all the cells of the BSS, GPRS traffic is stopped:

- PRH-PDCH-Release-MS-req towards the MS
- master PDCH deconfiguration (if any)
- PDCHs release and deallocation
- Stop-GPRS-req towards the BSC
(4):
The Gb failure disappears, a BVC-SIG Reset procedure is undertaken
(5):
RRM is notified of the BVC-SIG state change
(6):
BVC-PTP Reset procedures are processed, for each BVC-PTP of the NSE, followed by a
BVC-PTP Block procedure
(7):
BVC-PTP state changes are notified to RRM
(8):
BVC-PTP which state has become operational may be started at BSSGP level according
to other conditions (cell administrative state, BSC cell state)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.8 Unavailability notification from BSC
5.1.5.8.1
BSCGP
LM
RRM
NTM-CELL-State-ind (disabled)
RLC
BSSGP
(1)
LM-cell-state-change-ind
PRH-Deconf-master-req (6)
PRH-Deconf-master-cnf
(4)
PRH-SYS-Define-cnf
T_MPDCH_Deact
expiry
PRH-SYS-DEFINE-cnf
(9)
NTM-Cell-stop-cnf
Figure 61 BSC unavailability notification scenario (with MPDCH)

(1):
The cell is available for GPRS traffic, before receiving the cell state change notification,
from BSC
(2):
(3):

(4):
(5):
(6):
The master PDCH is deallocated
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(7):
complete acquisition of BCCH messages. The timer T_MPDCH_Deact shall at least cover
(8):
PSI broadcast is stopped

(9):
(10):
(11):
Note:
During all this procedure, the reception of a Packet Channel request triggers the emision of
a Packet Access reject with the cause Read System Information ; the reception of a
Channel Request received on RACH triggers the emission of an Immediate Assignment
Reject.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.8.2
MPDCH not supported
BSCGP
LM
RRM
NTM-CELL-State-ind (disabled)
RLC
BSSGP
(1)
(4)
PRH-SYS-Define-cnf
(7)
NTM-Cell-stop-cnf
Figure 62 BSC unavailability notification scenario (without MPDCH)

(1):
from BSC
(2):
(3):

(4):
(5):
(6):
PSI13 broadcast is stopped (B6.2 SMG29 only)
(7):
(8):
(9):
After having received the Deallocation acknowledgement a Stop-GPRS is sent to the BSC
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note:
During all this procedure, the reception of a Channel Request received on RACH triggers
the emission of an Immediate Assignment Reject.
5.1.5.9 Cell identity modification

There are 2 different cases which have to be taken into account:
- LAC/CI modification
In this case, this information is sent by the BSC
- RA code modification
In this case, this information is sent by an O&M command
In both cases, GPRS traffic has to be stopped in the cell, a BVC RESET procedure has to be
undertaken, on the Gb interface, in order to send the new cell identity to the SGSN, and then GPRS
traffic is re-started.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.9.1
BSCGP
LM
RRM
NTM-CELL-State-ind (new LAC/CI)
RLC
BSSGP
(1)
PRH-Deconf-master-req (6)
PRH-Deconf-master-cnf
(4)
PRH-SYS-Define-cnf
T_MPDCH_Deact
expiry
PRH-SYS-DEFINE-cnf
(9)
NTM-Cell-stop-cnf
NM-BVC-PTP-Reset-req (12)
NM-BVC-PTP-Start-req (14)
Figure 63 LAC/CI modification scenario (with MPDCH)

(1):
from BSC, with the new LAC/CI
(2):
(3):

(4):
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(5):
(6):
The master PDCH is deallocated
(7):
complete acquisition of BCCH messages. The timer T_MPDCH_Deact shall at least cover
(8):
PSI broadcast is stopped

(9):
(10):
(11):
(12):
A BVC-PTP reset procedure is triggered in BSSGP to send the new LAC/CI to the SGSN,
followed by a BLOCK procedure
(13):
At the end of the BVC-PTP Reset procedure, RRM is notified
(14):
Then GPRS traffic is re-started in the cell
Note : the modification of the LAC / CI of a cell leads to cell outage.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.9.2
MPDCH not supported
BSCGP
LM
RRM
NTM-CELL-State-ind (new LAC/CI)
RLC
BSSGP
(1)
(4)
PRH-SYS-Define-cnf
(7)
NTM-Cell-stop-cnf
NM-BVC-PTP-Reset-req (10)
NM-BVC-PTP-Start-req (12)
Figure 64LAC/CI modification scenario (without MPDCH)

(1):
from BSC, with the new LAC/CI
(2):
(3):

(4):
(5):
(6):
PSI13 broadcast is stopped (B6.2 SMG29 only)
(7):
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(8):
(9):
After having received the Deallocation acknowledgement a Stop-GPRS is sent to the BSC
(10):
A BVC-PTP reset procedure is triggered in BSSGP to send the new LAC/CI to the SGSN,
followed by a BLOCK procedure
(11):
At the end of the BVC-PTP Reset procedure, RRM is notified
(12):
Then GPRS traffic is re-started in the cell
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.1.5.10
BSS reset
When the BSCGP fails out-of-service because either a GSL or a BSCGP failure, all allocated PDCHs
are released to avoid inconsistencies between the MFS and the BSC.
When the BSCGP becomes again in-service, a reset procedure is started to synchronise entity states
between the BSC and the MFS.
At the end of the reset procedure
- the MFS has to request BSC (only in Pilot. In B6.2 , the BSC state is spontaneously
notified)
and cell states to the BSC
- GicGroups are considered as disabled, by the MFS (it is BSC responsibility to notify
enabled
GIC groups to the MFS)
(1):
When a GSL link is re-established, a Reset is received from the BSC and a NTM-BSCReset-ind is sent by BSCGP
(2):
When receiving NTM-BSC-Reset-ind:

- BSS state is considered as disabled
- The state of the cells belonging to this BSS is considered as disabled
- The state of the GIC groups belonging to this BSS is considered as disabled
(3):
In Pilot, BSC state is requested to the BSC through BSCGP.

In B6.2 , the BSC notifies spontaneously its state
(4):
Available GIC_GROUPs are notified by the BSC through BSCGP

(furthermore, in B6.2 a BSS TRAFFIC CONTROL message is also sent by the BSC)
note:
(3) and (4) are not synchronised (i.e. (4) may occur before (3))
(5):
If the BSC is enabled, a BVC-SIG Start is sent to BSSGP.
(6):
The BVC-SIG status is returned to RRM (operational, started if the BVC-SIG RESET
procedure was successful)
(7):
Cell states are requested to the BSC through BSCGP.
(8):
If the cell is enabled and locally unlocked, BSSGP is requested to start the corresponding
BVC-PTP
(9):
An UNBLOCK procedure is performed.
(10):
RRM is notified of the BVC-PTP status (operational, started)
(11):
(12):

In SI3/4, it is indicated that GPRS is supported.
(13):
BVC flow control parameters are sent to the SGSN
(14):

BSCGP)
(15):
(16):
If there is a MPDCH (MIN_MPDCH=1) and the network mode of operation is either NMO I
or NMO III, PSI is broadcast on the PBCCH
If there is no MPDCH, PSI13 is broadcast on PACCHs (B6.2 SMG29 only)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
A master PDCH is requested to the BSC (via BSCGP)
(18):
The BSC modifies SI13, giving MPDCH location
(17):
BSCGP
LM
RRM
RLC
BSSGP
NTM-BSC-RESET-ind (1)
NTM-BSC-STATE-req (3)
(2)
NTM-GICGROUP-STATE-ind (4)
NTM-GICGROUP-STATE-resp
NTM-BSC-STATE-cnf
NM-BVC-SIG-START-req (5)
NM-BVC-SIG-STATUS-CHANGE-ind (6)
NTM-CELL-STATE-req (7)
NTM-CELL-STATE-cnf
NM-BVC-PTP-T-Status-Change-ind (oper. + started) (10)
(12)
NTM-Cell-start-cnf
PRH-PDCH-estab-req
PRH-PDCH-estab-cnf
(15)
[PRH-Conf-Master-req] (17)
(18)
PRH-SYS-Define-cnf
[PRH-Conf-Master-cnf]
Figure 65 BSS Reset scenario
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(9)
5.1.5.11
Cell RESET
RRM
BSSGP
NM-CELL-RESET-ind (1)
NM-CELL-RESET-cnf
NM-FLOW-CONTROL-BVC-req (2)
Figure 66 Cell Reset scenario

(1):
A BVC-PTP Reset is received, by BSSGP, from the SGSN, RRM is notified.
(2):
BVC flow control is reinitialized.
5.1.5.12
No response from the BSC
The following PDU, sent by the MFS to the BSC, must be acknowledged:
Message
Acknowledgment
ALLOCATION
REQUEST
DEALLOCATION
COMMAND
MARK MASTER
CHANNEL
RESET
ALLOCATION
CONFIRM
DEALLOCATION
COMPLETE
MARK MASTER
CHANNEL ACK
RESET
ACKNOWLEDGE
START GPRS
START GPRS
ACKNOWLEDGE
STATE REQUEST
STATE RESPONSE
STOP GPRS
STOP GPRS
ACKNOWLEDGE
DETACH
DETACH
ACKNOWLEDGE
UNMARK MASTER
CHANNEL ACK
CELL RESET ACK
UNMARK MASTER
CHANNEL
CELL RESET
ED
MCD
Action undertaken,
Pilot
RESET procedure
on no response
B6.2
Cell reset procedure
numb. of
attempts
2
RESET procedure
Cell reset procedure
Reset procedure
RESET procedure is
triggered periodically
cell GPRS stop
procedure
State request is
no action
(if a new 04-08
channel request is
received, the MFS
sends a 04.08
immediate assignment
reject and in case
there is no on-going
GPRS STOP
procedure, the MFS
will request a STOP
GPRS to the BSC.)
RESET procedure
Reset procedure
RESET procedure
RESET procedure is
cell GPRS stop
procedure
State request is
no action
(if a new 04-08
channel request is
received, the MFS
sends a 04.08
immediate assignment
reject)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2
2
2
The acknowledgement of these PDUs is controlled by the timer T_GSL_ACK. There is one timer per
PDU sent.
If T_GSL_ACK expires, the PDU is resent (the number of attempts is limited, see the previous table)
and T_GSL_ACK is restarted.
If T_GSL_ACK expires during the last attempt, then an unsuccessful indication is sent to (RRM),
which will perform an action according to the previous table..
The figure below shows an example.
BSC
BSCGP
RRM
ALLOCATION REQUEST (2)
(3)
T_GSL_ACK
expiry
T_GSL_ACK
expiry
PRH-PDCH-ALLOCATE-cnf (NOK)
(4)
Figure 67 BSC no-response scenario

(1):
BSCGP sends the ALLOCATION REQUEST to the BSC. No response is received.
(2):
BSCGP repeats the ALLOCATION REQUEST. No response is received.
(3):
(4):
The traffic of the cell is stopped, and the following actions are undertaken:
- In B6.2
- If there is a MPDCH, a PRH-Deconf-Master-req is sent (if no response a RESET
procedure is undertaken)
- Cell Reset procedure
- a STOP GPRS is sent to the BSC
- In Pilot, a RESET procedure is undertaken.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.2
PAG Entity detailed description
This function is in charge of routing the paging request on the relevant channel in the relevant cell(s).
CS paging : Emission of a CS paging to provoke RR establishment when the Gs interface

is implemented.
PS paging : Emission of a PS paging to allow SGSN to accurately know the MS cell
location.
5.2.1 CS Paging
The MFS may receive CS paging from SGSN when operating in network operation mode I. The IMSI
and DRX parameters of the MS to be paged are always provided by the SGSN.
At receipt of a PAGING CS PDU from BSSGP :
In case the TLLI is provided by SGSN (and the page area is a cell or a RA) and the paged MS is in
packet transfer mode, i.e the MS is listening a PACCH channel, a CS Paging request is sent on
PACCH in the cell where the MS is.
Otherwise for all cells to be paged (one cell, or a Location Area or a Routing Area), a CS Paging
request PDU is sent :
on PCCCH channel if a MPDCH is present in the cell
on CCCH channel otherwise
Paging on PACCH :
Coding of Packet Paging Request PDU sent on PACCH :
Message type
Page mode
Persistence_level
NLN
TMSI
Length of Mobile Identity &
Mobile identity
Channel_needed
eMLPP_priority
ED
MCD
Presence
M
M
O
O
O
O
Value
Packet Paging Request
Normal
not used
Notification list number (not used)
Temporary Mobile Subscriber Identity
Used if provided in BSSGP PDU
Used if TMSI is not provided in BSSGP PDU
M
O
Value provided in BSSGP PDU

04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Paging on CCCH :
A Paging Request is sent by RRM to the BSC in case the SGSN paging list is a Location Area, or a
BSS Area, or a Routing Area, or a cell which does not own a MPDCH.
At receipt of a paging request whose paging list is either a Location Area, a Routing Area or a BSS
Area, the BSC sends a paging request on CCCH only for cells without MPDCH. For all cells, the BSC
is in charge of computing the MS CCCH group.
For a given cell, the BTS is in charge of concatenating several paging requests in one radio interface
PDU.
Coding of CS Paging Request sent to BSCGP:
IMSI
TMSI
Cell identifier list
Channel_needed
RR_priority
Presence
M
O
O
O
O
Value
Used if Value provided in BSSGP PDU
- One Cell or
- Location Area if LA is provided in BSSGP PDU
- BSS Area if BSS is provided in BSSGP PDU
- Routing Area if RA is provided in BSSGP PDU
Note : CS Paging on a Routing Area is not forbidden by F. At receipt of a MSC paging request with
a LA, the SGSN might for instance reduce the paging area to the Routing Area where the MS is.
Besides, BSS Area, RA and LA may contain cells which are unknown from RRM (cells which do not
support GPRS).
Paging on PCCCH :
A Paging Request is sent by RRM to MAC layer when the SGSN paging list contains at least one cell
with a MPDCH. The paging request sent to the MAC layer may contain a list of master cells.
For a given cell, MAC is in charge of calculating the MS paging group and of concatenating several
paging requests in one radio interface PDU.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.2.2 PS Paging
The MFS may receive PS paging from SGSN whatever the network mode of operation. The IMSI of
the MS to be paged is always provided by the SGSN ; if known, the DRX parameters are provided
too.
At receipt of a PAGING PS PDU from BSSGP :
For all cells to be paged (one cell, or a Location Area or a Routing Area), a PS Paging request PDU
is sent :
- on PCCCH channel if a MPDCH is present in the cell
- on CCCH channel otherwise
Note : The PS Paging procedure does not take care about the MS Packet mode (MS in Packet
transfer mode or not) : TLLI is indeed not provided by SGSN in case of PS paging and (RRM) does
not store MS IMSI in PCC TBF context. That means that a PS Paging PDU may be sent over the
radio interface uselessly.
Paging on CCCH :
A Paging Request is sent by RRM to the BSC in case the SGSN paging list contains at least one cell
without a MPDCH.
A Paging Request sent to BSC may contain one slave cell (known by RRM) or a Location Area or a
BSS Area or a Routing Area.
At receipt of a paging request whose paging list is either a Location Area, a Routing Area or a BSS
Area, the BSC sends a paging request on CCCH only for cells without MPDCH. For all cells, the BSC
is in charge of computing the MS CCCH group and the paging group according to the IMSI value.
For a given cell, the BTS is in charge of concatenating several paging requests in one radio interface
PDU.
Coding of Packet Paging Request sent to BSCGP:
IMSI
PTMSI
Cell identifier list
Presence
M
O
O
Value
- One Cell or
- Location Area if LA is provided in BSSGP PDU
and at least one cell in the LA does not own a
MPDCH or
- BSS Area if BSS is provided in BSSGP PDU
and at least one cell in the BSS does not own a
MPDCH
- Routing Area if RA is provided in BSSGP PDU
and at least one cell in the RA does not own a
MPDCH
Note : PS Paging on a Location Area is not forbidden by F. It might be used by SGSN.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Paging on PCCCH :
A Paging Request sent to MAC may contain a list of master cells.
For a given cell, MAC is in charge of calculating the MS paging groups according to the IMSI and the
DRX parameters and of concatenating several paging requests in one radio interface PDU.
Note that in some defense cases (e.g. SGSN failure), it may happen that the SGSN does not know
the DRX parameters of the MS to be paged. In such case, the BSS receives a PS Paging request
from the SGSN without any DRX parameters. The paging request shall be sent on PPCCH according
to the mimimum recurrence of the paging group based on IMSI value only. RRM shall then provide
the MAC layer with a DRX parameters IE whose split-pg-cycle value is set to 1.
When the DRX parameters are provided by the SGSN, they are sent by RRM to the MAC layer.
Note : the QoS profile (only service precedence is relevant here) is not used.
PAG process is summarized in the following table.
Paging
type
Conditions
cell(s) in the paging list without MPDCH
PS
cell(s) in the paging list with MPDCH

PACCH for that MS
CS
no PACCH for that MS
cell(s) in the paging list

without MPDCH
cell(s) in the paging list
with MPDCH
RRM behaviour
a PAG-PAG-MS-req (cell list id., PS
paging) is sent to BSCGP
a PAG-PAG-MS-req (list of master
cells , PS paging) is sent to RLC
a PAG-PAG-MS-req (cell , PACCH,
CS paging) is sent to RLC
a PAG-PAG-MS-req (cell list id., CS
paging) is sent to BSCGP
a PAG-PAG-MS-req (list of master
cells , CS paging) is sent to RLC
5.2.3 Activation / Deactivation of the MPDCH

Activation of the MPDCH :
While the MPDCH is not successfully allocated with the BSC (the message PRH-Conf-Master-cnf
OK has not been received by the MFS), any PS paging message is sent on PCH ; any CS paging
message is sent either on PACCH if addressed to a MS in Packet transfer mode, or on PCH.
After the successful allocation of the MPDCH (the message PRH-Conf-Master-cnf OK has been
received), PS paging is sent on PPCH. CS paging message is sent on PACCH or PPCH. During the
30 seconds following the allocation of the MPDCH, the GPRS MS may not receive the paging
message as it may be still unaware of the MPDCH presence. The paging request may hence be
repeated by the SGSN or the MSC.
Deactivation of the MPDCH :
As soon as the MPDCH is successfully deallocated by the BSC (the message PRH-Deconf-Mastercnf OK has been received), any PS paging message is sent on PCH ; any CS paging message is
sent either on PACCH or on PCH.
Indeed, the MS which were either camping on the PPCH are assumed to switch quickly to the PCH
channels thanks to the broadcast of the BS_PCC_REL bit on the PBCCH.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3
PCC Entity detailed description
PCC entity deals with the following functions:

- TLLI handling
- packet connection establishment
- UL TBF establishment
- DL TBF establishment
- packet connection modification
- MS requested modification during on-going TBF
- Network decided coding scheme adaptation
- TLLI modification
- packet connection release
- Normal TBF termination
- Abnormal TBF termination initiated by RLC
- Abnormal TBF termination initiated by RRM
5.3.1
TLLI handling
The TLLI identifies the MS.

5.3.1.1 UL TBF
The TLLI information is known either at receipt of Packet Resource Request or on receipt of the first
UL RLC block. It is then stored in the corresponding PCC TBF context entry
A TLLI notification is received from RLC on receipt of the first UL RLC block with a valued TLLI field.
(It has to be checked that no other UL TBF is established for this TLLI. If there is another established
UL TBF, the oldest has to be released (TFI, TAI, USF(s) are frozen during T3169))
The TLLI is added to every UL-UNITDATA PDU, towards the SGSN.
5.3.1.2 DL TBF
The TLLI is received in every DL-UNITDATA PDU, received from the SGSN.
5.3.1.2.1
Nominal case
In the received DL-UNITDATA PDU, only the current TLLI parameter is present (no old TLLI).
In this case, current TLLI is used to check whether there is an established TBF:
- If there is an on-going DL TBF, the PDU is sent on this TBF
- Otherwise:
- If there is an on-going UL TBF, PACCH/DL of the UL TBF is used to send the Packet DL
Assignment message which is identified by the TFI of the UL TBF.
- Otherwise, (P)CCCH is used to send the Packet DL Assignment message which is identified
by the current TLLI.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.1.2.2
P-TMSI/TLLI reallocation procedure
A TLLI modification occurs during a P-TMSI reallocation procedure.

Let TLLI (A) be the old TLLI and TLLI (B) be the new TLLI.
Several cases can occur according to the TLLI received, by the SGSN with the GMM P-TMSI
Reallocation Command acknowledgement:
5.3.1.2.3
GMM message received with TLLI (B)
If SGSN receives the GMM message completing the P-TMSI reallocation procedure in an ULUNITDATA PDU including TLLI (B), the P-TMSI reallocation procedure is complete at the SGSN
side.
The SGSN shall then use TLLI (B) to identify the MS in any subsequent DL-UNITDATA PDU sent to
the MFS. The MFS may still have an MS context associated with TLLI (A). Such a context should not
be referenced any more.
The SGSN may include a TLLI (old) = TLLI (A) in one or a few subsequent DL-UNITDATA PDUs
sent to the MFS. If the MFS receives a DL-UNITDATA PDU including a TLLI (old) = TLLI (A), any
context associated with TLLI (A) should be removed (in B6.2, there should be no such context). If
there is no such context, a TLLI (old) = TLLI (A) may be ignored.
5.3.1.2.4
GMM message received with TLLI (A)
If SGSN receives the GMM message completing the P-TMSI reallocation procedure in an ULUNITDATA PDU indicating TLLI (A), the P-TMSI reallocation procedure is complete at the SGSN
side, but the MS is still using a TBF associated with TLLI (A).
When the GMM message completing the P-TMSI reallocation procedure is received, the SGSN may
a) start to use TLLI (B) to identify the MS in the next DL-UNITDATA PDU sent to the MFS.
b) Optionnaly, the SGSN may wait to start using TLLI (B) in DL-UNITDATA PDUs until an
LLC
frame is received in an UL-UNITDATA PDU with TLLI (B).
a) If SGSN starts to use TLLI (B) in a DL-UNITDATA PDU before an UL-UNITDATA PDU is received
with TLLI (B), it shall include the TLLI (old) = TLLI (A) in the next and optionnally in all DLUNITDATA PDUs sent to the MFS, until an UL-UNITDATA is received with TLLI (B).
If the MFS receives a TLLI (old) = TLLI (A), TLLI (A) may be used to locate an existent context for
the MS. If there is an existent UL TBF from the MS, then TLLI (B) shall be used to identify the MS in
the UL-UNITDATA PDU with any subsequent LLC frames that is delivered from MFS to SGSN.
b) In this case, there should be no context related to TLLI (A), in the MFS.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.1.2.5
MFS behaviour
When the MFS receives a DL-UNITDATA PDU which includes both current TLLI and old TLLI
parameters, the MFS has to perform the following actions, according to the presence of TBF related
to these TLLIs (see the table below):
X:
A:
B:
:
DL TBF
B
X
UL TBF
MFS behaviour
- The PDU is sent on the on-going TBF
PACCH/DL of the UL TBF is used to send the Packet
DL Assignment
- The PDU is sent on the on-going TBF
- DL TBF reference is changed from A to B
- If there is an UL TBF identified by A, its identification
is modified from A to B
- PACCH/DL of the UL TBF is used to send the Packet
DL Assignment
- TBF reference is changed from A to B
The Packet DL Assignment is identified with TLLI (B)
no TBF
TBF identified by TLLI (A)
TBF identified by TLLI (B)
whether there is a TBF or not
Notes: It may happen that 2 MS contexts respectively attached to TLLI (A) and TLLI (B)
simultaneously exist in the MFS at receipt of the BSSGP DL-UNITDATA PDU with both TLLI.
The MFS is then expected to keep only one context at receipt of the BSSGP DL-UNITDATA
PDU, as the old TLLI may be subsequently reassigned to another MS.
In B6.2, the only case where it could happen would be when the release of the DL TBF
established with A is unsuccessful (the context is frozen during 5s), and the MS establishes a
new UL TBF with TLLI B.
This case being marginal, and even in that case the old context being released after 5s,
there is
no need for the MFS to delete the second context at receipt of the BSSGP DLUNITDATA PDU.
In future, this may also occur when the cell reselection is controlled by the network. It is
possible
to have an operational DL TBF established with A, in parallel with an UL TBF
established with B.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.2 Packet connection establishment

5.3.2.1 UL packet connection establishment
5.3.2.1.1
Input parameters
The following PDUs may be received to request an UL TBF establishment :

(1) Packet Channel Request received from MS on PCCCH channel
(2) PCC-UL-CHN2-REQ received from MS on PACCH/U of DL TBF (i.e. TBF establishment
request carried through Packet DL ack/nack)
(3) Channel Request received from MS on CCCH channel
(4) Packet Resource Request received from MS on PACCH/U (second phase of a 2 phase
access)
(1) Packet Channel Request:
Message-type
Access type
Presence
M
M
Multislot class
Radio priority level
Number of blocks
Random Reference
Frame Number
Initial timing advance
O
M
M
M
ED
MCD
Value
- 1 phase access request
- short access request
- 2 phase access request
- Page response
- Cell Update
- Mobility Management procedure
- Single block without TBF establishment
Multislot class of the Mobile Equipment
(present only if access type = 1 phase access)
Requested Radio priority (1 to 4)
(only with 11 bit format)
Not used
Not used
From 0 to 31
FN on which the request is received
Computed by BTS
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(2) PCC-UL-CHN2-REQ :
Message-type
IE
Presence
M
M
Value
PCC-UL-CHN2-REQ
See below
(3) Channel Request received from MS on CCCH channel

This message is sent on the RACH.
One phase/Single block packet access requested:
Establishment cause
Random reference
Presence
M
Value
- 011110xx: One phase access requested
or 01111x0x
or 01111xx0
- 01110xxx: Single Block packet access
requested
x: random value
(4) Packet Resource Request:

Message-type
Access_type
global TFI
TLLI
MS
Radio
Access
Capabilities IE
Presence
M
O
O
O
O
IE
MA_change_mark
C_Value
Value
Not used
not used by the MS, in that context
MS identity
MS Radio access capabilities: the GPRS
multislot class is the only field used in B6.2 .
MS RA Capability is always provided in a 2phases access. The decoding of the Access
Technology types GSM-P, GSM-E, GSM-R,
GSM 1800 and DCS1900 shall be supported by
RRM.
See below
O
M
Not used
Not used
SIGN_VAR
I_LEVEL_TN0 to TN7
O
O
Not used
Not used
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Channel_request_descriptionIE:
Peak_throughput_class
Presence
M
Radio_priority
rlc_mode
llc_PDU_type
M
M
rlc_octet_count
Semantic
Requested uplink peak throughput class
Not used.
Requested Radio_priority: from priority 1
(highest priority) to priority 4 (lowest priority).
Not used
RLC acknowledged or not acknowledged mode
Type of the first LLC PDU to be sent over the
requested UL TBF
- LLC PDU is not SACK or ACK
(not used)
Not used.
Nb of bytes the MS wishes to transfer possible
values
Note: The network does not filter channel requests potentially sent successively by the same MS. In
such case, several connections are started and released upon timeout expiry. Note that configuration
of parameter S (see 6.3) shall allow to make such case seldom.
5.3.2.1.2
Behaviour
The following actions are performed.

1) TFI allocation and PCC TBF context creation
Except in case of a 2 phase access on CCCH (one block access on CCCH) or 2 phase access on
PCCCH, a TFI is allocated among the 32 available values for the uplink path (per cell).
If no TFI is available, a Reject is sent to the MS.
The following information need to be recorded per TBF
PCC TBF context attributes (classified per category of information)
User_identity
- TLLI
TBF_identity
- TFI : 0 to 31
- TBF_direction : UL
- Cell identity
Granted_QoS_description
- RLC mode
Granted_channel_description
- Timeslot allocation
- PACCH_TS
- Granted_USF_per_PDCH
- Current_coding_scheme
- Timing_advance_index
TBF_state
- State of the FSM
Multislot class
- multislot class
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note: The channel or resource request parameters (e.g. FN, Random value, channel type & timeslot
number where the request was received) are not listed in above table. The way they are stored
during allocation phase is an implementation issue.
The user identity is known at that stage only in case of PCC-UL-CHN2-REQ received from MS on
PACCH/U of DL TBF through the DL TFI, or in case of Packet Resource Request received from the
MS, which allows to retrieve the TLLI. In all other cases, a random value and a Frame Number are
available.
2) QoS definition
The throughput and service precedence are not managed.
The RLC mode of the TBF to be established is determined as indicated below.
5.3.2.2 Request type
1 phase access on RACH
1 single block access on RACH
(for 2 phase access)
1 phase access on PRACH
1 single block access on PRACH (for
2 phase access)
Short access on PRACH
Page response / Cell Update / MM
procedure (on PRACH)
UL TBF establishment request
received from MS on PACCH/U of DL
TBF or on PACCH/U (one block
allocation for 2 phase access
procedure)
ED
MCD
5.3.2.3 RLC mode

acknowledged
acknowledged
acknowledged
acknowledged
MS requested mode
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3) Radio resources request

Radio resources are requested to PRH block, which will allocate them according to the following
parameters:
- type of the request (1 UL block allocation/TBF allocation)
- direction (UL)
- concurrent TFI (present if a TBF is established in the reverse direction)
- multi-slot class of the MS (present in case of TBF allocation)
- maximum queuing time (null, no UL queuing)
- starting_time (present in case of one block allocation; defines the time from which the
block may be allowed, in number of frames)
- cell identity
The table below defines for each input message, according to the access type or establishment
cause field value, how are valued type of request and MS multi-slot class parameters.
input message
Packet channel
request (PCCCH)
access type/
establishment cause
- 1 phase access
type of the request
MS multislot class
TBF allocation
- short access
- page response
- cell update
- MM procedure
- 2 phase access
TBF allocation
value of the
message
monoslot MS
PCC-UL-CHN2-REQ
Channel request
(CCCH)
- one phase access
TBF allocation
- single block packet
1 UL block allocation
TBF allocation
Packet Resource
Request
ED
MCD
1 UL block allocation
TBF allocation
value derived from DL

TBF
monoslot MS
value of
message
04 Released
267129603.doc
10/08/2000
input
3BK 11202 0265 DSZZA
the
input
4) RLC context establishment

Except for the first phase of a 2 phase access (on CCCH or PCCCH), a TBF context is created within
RLC layer.
The initial coding scheme (retrieved from parameter TBF_INIT_CS) is provided to RLC layer. It may
be used by (RLC) layer only for unacknowledged UL TBF to reconstruct an UL PDU when some RLC
blocks are missing (to determine padding length, when a block is missing).
RRM also indicates whether dynamic coding scheme adaptation may be performed or not by RLC
layer. It is always allowed, except for FUMO BTS (information is retrieved at L2-GCH establishment)
or when the feature is not enabled by O&M (EN_CS_Adaptation parameter).
In case of 1 phase access on CCCH or PCCCH, (RLC) layer is requested to perform resolution
contention.
5) MS assignment
The relevant assignment message is sent to the MS on relevant channel.
Packet Uplink Assignment or Packet Access Reject sent to MS on :
- same PCCCH, for Packet Channel Request
- PACCH/DL of DL TBF, for PCC-UL-CHN2-REQ
- PACCH/DL of UL TBF, for Packet Resource Request
Immediate Assignment or Immediate Assignment Reject sent to MS on :
- same CCCH, for Channel Request, received on CCCH
Whether the PBCCH is configured or not, the MS is requested to use the mobile allocation included
in the SI13 message sent on BCCH.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
a) Block assignment on CCCH

An Immediate assignment message is sent on CCCH to allocate one uplink radio block to the MS in
response to a Channel request message indicating a 1 block packet access. The MS will use the
allocated uplink block to send a Packet Resource Request to the BSS.
No TFI and no USF are assigned.
Presence
format
L2 Pseudo lengh
Length
(bits)
8
RR managenent
Protocol Discriminator
Skip Indicator
Immediate
Assignment
Message Type
Page Mode
Dedicated mode or TBF
M
M
V
V
4
8
M
M
V
V
4
8
Channel Description
Packet Channel Description
C
C
V
V
Request Reference
Coding rules
Sum of all information elements
present in the message. Excluding
the Rest Octets
Radio
ressource
management
message
message is not ignored
Immediate Assignment
Normal
T/D = 1 (i.e. TBF)
DL = 0 (UL assignment)
TMA = 0 (1 message assignment)
0
Not used
24
Channel Type = 00001
Time_slot_number: PACCH slot
TSC
If FH is not supported : ARFCN
If FH is
supported : MAIO +
MA_NUMBER set to 14 (indirect
encoding refers to SI13 channel
description)
CHANGE_MARK_1
valued
with
SI13_CHANGE_MARK
received
from the BSC
24
FN + Random value received into
the Channel Request
8
-TA value is provided
8
Length valued to 0.
0
not used
Length : 11 octets
Timing Advance
M
Mobile Allocation
M
Starting time
O
Immediate Assignment Rest Octets
V
LV
TV
TFI_assignment
polling
usf
usf_granularity
P0
allocation_bitmap_length
allocation_bitmap
P0
bts_pwr_ctr_mode
channel_coding_command
tlli_blocks_channel_coding
ALPHA
O
O
O
O
O
O
O
O
O
O
O
M
V
V
V
V
V
V
V
V
V
V
V
V
GAMMA
timing_advance_index
tbf_starting_time
O
O
V
V
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Alpha parameter configured by the
O&M
GAMMA_TNx parameter for the
allocated timeslot configured by the
O&M
Not used
First_frame_number of the allocated
radio block
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note: Because of the Dedicated mode or TBF IE content which indicates a TBF assignment, the
Packet Channel Description IE shall be considered by the MS as present in the message.
The fields in grey belong to the immediate assignment rest octet.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) TBF assignment on CCCH

An Immediate assignment message is sent on CCCH to allocate one Uplink TBF to the MS in
reponse to a Channel request indicating a 1 phase access.
TFI, USF are assigned. Note that only 1 PDCH can be allocated with the Immediate assignment
PDU sent on CCCH.
Presence
Format
L2 Pseudo lengh
Length
(bit)
8
RR managenent
Skip Indicator
Message Type
Page Mode
M
M
V
V
4
8
M
M
V
V
4
4
Channel Description
C
C
24
Request Reference
Timing Advance
M
M
V
V
24
8
Mobile Allocation
M
Starting Time
O
M
LV
TV
tfi_assignment
polling
Usf
usf_granularity
P0
O
O
O
O
O
O
V
V
V
V
V
V
tlli_blocks_channel_coding
ALPHA
GAMMA
timing_advance_index
tbf_starting_time
O
O
V
V
ED
MCD
Coding rules
present in the messageExcluding
the Rest Octets
Radio ressource management
message
Normal
T/D = 1 (i.e. TBF)
DL=0 (UL assignment)
Not used
Time_slot_number: 0 to 7
TSC
If FH is supported : MAIO +
description)
CHANGE_MARK_1 valued with
SI13_CHANGE_MARK received
from the BSC
FN + Random value
-TA value is provided
8
Length valued to 0.
0
not used
Length : 11 octets
UL TFI which is assigned to the MS
the polling bit is set to 0
USF of the single allocated PDCH
1 radio block per USF
Not used
Initial CS derived from parameter
init_CS.
same value as
Channel_Coding_Command
O&M
GAMMA_TNx parameter for the
allocated timeslot configured by the
O&M
timing advance index is provided
not used
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The fields in grey belong to the immediate assignment rest octect.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
c) Block assignment on PCCCH

A PACKET UPLINK ASSIGNMENT message, using the Single Block Allocation structure is sent on
PAGCH to allocate one uplink radio block to the MS in response to a Packet Channel Request
message indicating a 2 phase access.
The MS will use the allocated uplink block to send a Packet Resource Request to the BSS.
No TFI nor TAI is assigned to the MS.
Message type
Page mode
Persistence level
referenced_address IE
Presence
M
M
O
M
tlli_block_channel_coding
M
M
packet_timing_advance IE
frequency_parameters IE
timeslot_number
ALPHA
GAMMA_TN
M
O
M
P0 & bts_pwr_ctrl_mode
tbf_starting_time
O
M
ED
MCD
Coding rules
normal
not used
Random value + FN received in the Packet
Channel Request
CS-1
CS-1
- TA value is provided
- TA index is not provided
- TA timeslot number is not provided
- TSC
- in case of non hopping channel: ARFCN
- in case of hopping channel (indirect encoding):
- MA_NUMBER = 1
- CHANGE_MARK_1 valued to
PSI2_CHANGE_MARK
- CHANGE_MARK_2: not used
PACCH slot
alpha parameter configured by O&M
GAMMA_TN parameter of the allocated TS,
configured by O&M
Not used
First frame number of the allocated radio block
(absolute FN encoding)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
d) TBF assignment on PCCCH

A PACKET UPLINK ASSIGNMENT message, using the Dynamic Allocation structure, is sent on
PAGCH to allocate one uplink TBF to the MS in response to a Packet Channel request message not
indicating a 2 phase access.
Message type
Page mode
Persistence level
Presence
M
M
O
M
M
M
Extended_Dynamic_Allocation
M
O
M
O
O
O
M
O
P0
USF granularity
uplink_tfi_assignment
rlc_data_blocks_granted
tbf_starting_time
ALPHA
usf_tn0 and gamma_tn0 to
usf_tn7 and gamma_tn7
Coding rules
normal
not used
Random value + FN received from MS on
PRACH in packet Channel Request
initial CS derived from INIT_CS
same value as Channel_Coding_Command
- TA index is always provided
- TA timeslot number is always provided (PACCH
slot)
- TSC
- MAIO
- MA_NUMBER = 1
PSI2_CHANGE_MARK
Dynamic allocation
Not used
UL TFI which is assigned to the MS
Not used
not used
The timeslot allocation with power control
parameters is used:
USFs of the allocated PDCHs and its
GAMMA_TN parameters (configured by O&M)
Note that 2 assignment messages are needed in case of 1 phase access on CCCH (see peer to peer
protocol).
e) TBF assignment on PACCH
A PACKET UPLINK ASSIGNMENT message, using the Dynamic Allocation structure, is sent on
PACCH to allocate one uplink TBF to the MS
- either in response to an uplink access requested during an on-going downlink transfer,
- or in response to a Packet Resource Request,
- or after an Immediate Assignment message sent for a one phase access on CCCH.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Message type
Page mode
Persistence level
Presence
M
M
O
M
M
M
M
Extended_Dynamic_Allocation
M
O
tbf_starting_time
ALPHA
O
O
M
O
USF granularity
ED
MCD
Coding rules
normal
not used
Global TFI in case of:
- PCC-UL-CHN2-REQ received from MS on
PACCH/U of DL TBF: DL TFI
- Packet Uplink assignment sent on PACCH
for a one phase access on CCCH: UL TFI
OR
TLLI in case of:
- Packet Resource Request received from MS
on PACCH/U (second phase of a 2 phase access
on CCCH or PCCCH)
initial CS derived from INIT_CS
same value as Channel_Coding_Command
- TA timeslot number is always provided (PACCH
slot)
- TSC
- MAIO
- MA_NUMBER =
* 14 if there is no MPDCH or if the MPDCH is
being deactivated
* 1 if there is a MPDCH in the cell
* SI13_CHANGE_MARK retrieved from the
BSC if there is no MPDCH or if the MPDCH is
being deactivated
* PSI2_CHANGE_MARK if there is a MPDCH
in the cell
Dynamic allocation
UL TFI which is assigned to the MS in case of:
PACCH/U of DL TBF
on PACCH/U (second phase of a 2 phase access
on CCCH or PCCCH)
Not used, in case of:
- Packet Uplink assignment sent on PACCH
for a one phase access on CCCH
Not used
not used
The timeslot allocation with power control
parameters is used:
USFs of the allocated PDCHs and its
GAMMA_TN parameters (configured by O&M)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6) RLC context activation

(RRM) PCC requests (MAC) layer to start allocation of radio blocks when MS acknowledges the TBF
establishment.
7) Exceptions
The packet connection request is rejected (Packet Access Reject is sent to MS) in case :
There is no more available TFI value in the cell
The request access type is Single block without TBF establishment
(only for access type on MPDCH)
The RLC context is not successfully established
There is no available radio resources : the maximum number of MS per PDCH for UL path
for all available PDCHs is reached
The received PDU is invalid
a) Assignment reject on CCCH
If the assignment is rejected, RRM sends to the MS an Immediate Assignment Reject message on
CCCH.
Presence
Format
L2 Pseudo lengh
Length
(bits)
8
RR managenent
Skip Indicator
Immediate
Assignment
Reject Message Type
Page Mode
Spare Half Octet
Request Reference 1
Wait Indication 1
M
M
V
V
4
8
M
M
M
M
V
V
V
V
4
4
24
8
Request Reference 2
Wait Indication 2
M
M
V
V
24
8
Request Reference 3
Wait Indication 3
M
M
V
V
24
8
Request Reference 4
Wait Indication 4
M
M
V
V
24
8
Spare
Coding rules
present in the message. Excluding
the Rest Octets
Radio
resource
management
message
Immediate Assignment Reject
Normal
Spare Half octet
FN + Random value
WI_PR in case of saturated PDCHs
WI_PA in case of on-going PDCH
Allocation
FN + Random value
Allocation
FN + Random value
Allocation
FN + Random value
Allocation
Spare
The fields in gray belong to the immediate assignment reject rest octect.
Note:
Request Reference 2/3/4 and Wait indication 2/3/4 fields have the same value than
respectively Request Reference 1 and Wait indication 1, because only one assignment is rejected.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) Packet Access Reject on PCCCH/PACCH (Exceptions)

Message type
Page mode
referenced_address
Presence
M
M
M
Coding rules
Normal
Random value + FN in case of:
- Packet Channel Request received from MS
on PCCCH channel
Or
Global TFI in case of:
PACCH/U of DL TBF: DL TFI
Or
Wait_indication &
Wait indication size
ED
MCD
TLLI in case of:

on PACCH/U (second phase of a 2 phase
access on PCCCH or CCCH)
- not present in case of reject case Read
system information
- WI_PA in seconds in case of a reject message
at expiry of T_ul_access_max (on-going PDCH
Allocation) ; ottherwise WI_PR in seconds
in case of saturated PDCHs (e.g. all allowed
PDCHs are full)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.2.4 DL packet connection establishment
5.3.2.4.1
Input parameters
At receipt of a DL LLC PDU from the SGSN addressed to a MS for which there is no on-going DL
TBF, the BSS establishes a DL TBF.
The following information conveyed within the DL BSSGP PDU are used:
- cuurent TLLI
TLLI identifying
the MS
- old TLLI
old TLLI identifying the MS (optional field, which may be used after a
P-TMSI reallocation procedure, see 5.3.1)
- RLC mode
acknowledged or unacknowledged mode
- LLC PDU life-time
the TBF shall be established before expiry of the LLC PDU life-time;
if not possible, no DL TBF is established and the DL LLC PDU is
discarded
- MS classmark
contains the MS multislot class
- DRX parameters
The only case where the SGSN is allowed not to send the DRX
parameters in a BSSGP DL-UNITDATA PDU is when the mobile
station is in MM non-DRX mode (e.g. on-going GPRS Attach or
Routing Area Update procedure).
The DL TBF establishment shall be sent on the first free occcurence
of the paging groups on PPCH, or on the first free occurrence of the
AGCH channel.
To achieve that, RRM shall respectively send a downlink assignment
message to the MAC layer with the DRX parameters whose split-pgcycle is set to the value 704, or send a downlink assignment on the
BSCGP interface without providing the IMSI.
- IMSI
optional parameter provided when known by the SGSN, since it is
used to derive the (P)CCCH group of the MS. If the IMSI is not
present, the MS is assumed to be in non-DRX mode and the DL TBF
establishment is sent on the first free occcurence of the paging
groups on PPCH, or on the first free occurrence of the AGCH
channel.
To achieve that, RRM shall respectively send a downlink assignment
message to the MAC layer with the DRX parameters whose split-pgcycle is set to the value 704, or send a downlink assignment on the
BSCGP interface without providing the IMSI.
- target cell
5.3.2.4.2
cell identity
Behaviour
The following actions are performed.

1) TFI allocation and PCC TBF context creation
A TFI is allocated among the 32 available values for the downlink path (per cell).
If no TFI is available, the request is queued.
In case of a fast DL TBF re-establishment, the previous TFI is used (i.e. TFI of the DL TBF, for which
T3193 is activated)
The following information need to be recorded per TBF :
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
PCC TBF context attributes (classified per category of informations)

User_identity
- TLLI
TBF_identity
Granted_QoS_description
Granted_channel_description
TBF_state
Multislot class
- TFI: 0 to 31
- TBF_direction: DL
- cell identity
- RLC mode
- Timeslot allocation
- PACCH_TS
- Current_coding_scheme
- Timing_advance_index
FSM state
Multislot class
Note: In case of a fast DL TBF re-establishment, the RLC mode may be changed with regard to the
previous TBF and the new TBF is established with the initial coding scheme defined by TBF_Init_CS.
2) QoS definition
The throughput and service precedence are not managed.
The RLC mode of the TBF to be established is those explicitly requested by the SGSN.
3) Radio resources request
Radio resources are requested to PRH block, which will allocate them according to the following
parameters:
- type of the request (TBF allocation)
- direction (DL)
- concurent TFI (if a TBF is established in the reverse direction)
- multi-slot class of the MS (value provided by the SGSN)
- maximum queuing time (DL LLC PDU lifetime)
- cell identity
In case of a fast DL TBF re-establishment, the radio resources of the previous TBF are re-used.
4) RLC context establishment :
A TBF context is created within RLC layer.
The initial coding scheme (retrieved from O&M parameter TBF_INIT_CS) is provided to RLC layer. It
is used by RLC layer to segment DL LLC PDU.
RRM also indicates whether dynamic coding scheme adaptation may be performed or not by RLC
layer. It is always allowed, except for FUMO BTS (information is retrieved at L2-GCH establishment)
or when the feature is not enabled by O&M (EN_CS_Adaptation parameter).
5) MS assignment
The relevant assignment message is sent to the MS on the relevant channel.
Packet Downlink Assignment to MS on PCCCH or PACCH/DL of UL TBF or PACCH/DL of
previous DL TBF (case of fast DL TBF re-establishment)
Immediate Assignment sent to MS on CCCH
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
a) TBF assignment on CCCH

An Immediate Assignment message is sent on PCH to allocate one downlink TBF to the MS to send
to it one or several DL LLC PDUs received from the SGSN.
A TFI and a single PDCH are allocated.
Presence
Format
L2 Pseudo lengh
Length
(bit)
8
RR managenent
Skip Indicator
Message Type
Page mode
M
M
V
V
4
8
M
M
V
V
4
8
Channel Description
C
M
V
V
Request Reference
Timing Advance
M
M
V
V
Coding rules
present in the message. Excluding the
Rest Octets
Radio resource management
message
Normal
T/D = 1 (i.e. TBF)
DL=1 (DL assignment)
0
Not used
24
Time_slot_number: 0 to 7
TSC
If FH is supported : MAIO +
description)
CHANGE_MARK_1 retrieved from
the BSC and included in SI13
24
valued to 101xxxxx
8
All bits are set to 0 (no available
timing advance value)
8
Length valued to 0.
0
not used
Length : 11 octets
Mobile Allocation
M
Starting Time
O
LV
TV
Packet downlink Assignment

TLLI
TFI assignment
RLC_mode
ALPHA
M
M
M
M
M
V
V
V
V
V
GAMMA
polling
Packet downlink Assignment

MSs TLLI
Allocated TFI.
RLC mode requested by the SGSN.
O&M
GAMMA_TNx parameter of the
allocated timeslot (PACCH),
configured by the O&M
the polling bit is set to 0
TA_VALID
Timing_Advance_Index
TBF_Starting_Time
M
O
O
O
V
V
V
V
The timing advance value is not valid

Timing Advance Index is provided
Not used
Not used
The fields in grey belong to the immediate assignment rest octect.

ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) TBF assignment on PCCCH/PACCH

A Packet Downlink Assignment message is sent on PPCH or PACCH to allocate one downlink TBF to
the MS to send to it one or several DL LLC PDUs received from the SGSN.
A TFI and one or several PDCHs are allocated.
Message type
Page mode
Persistence level
Presence
M
M
O
M
Coding rules
Packet Downlink Assignment
normal
not used
Global TFI in case of :
Assignment on PACCH/DL of UL TBF: UL TFI
Assignment on PACCH/DL of DL TBF: DL TFI
Or
MAC_mode
RLC_mode
Control Ack
Timeslot allocation
M
M
M
M
O
O
TLLI in case of :
Assignment on PCCCH
Dynamic allocation
The mode requested by SGSN
set to 0
Allocated PDCHs
- TA value is not provided
- TA timeslot number is always provided
(PACCH slot)
Not used
- TSC
- in case of hopping channel:
- MAIO
- MA_NUMBER =
* 14 if there is no MPDCH or if the MPDCH
is being deactivated
* 1 if there is a MPDCH in the cell
* SI13_CHANGE_MARK retrieved from the
BSC if there is no MPDCH or if the MPDCH is
being deactivated
* PSI2_CHANGE_MARK if there is a
MPDCH in the cell
downlink_tfi_assignment
power_control_parameters
IE
tbf_starting_time
Measurement Mapping
O
O
ED
MCD

- In case of :
- Assignment on PACCH/DL of UL TBF
- or Assignment on PCCCH
DL TFI assigned to the MS
- In case of Assignment on PACCH/DL of DL
TBF: Not used
alpha and GAMMA_TNX parameters of the
allocated PDCH(s) configured by O&M
Not used
Not used
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note that 2 assignment messages are needed in case of assignment on CCCH (see peer to peer
protocol).
In case of TBF establishment failure (no reception of the Packet Control Acknowledgment),
there are 3 cases:
- 1) The DL assignment was sent on PCCCH or CCCH:
In this case, a new attempt is undertaken, provided Max_Retrans_DL is not reached.
- 2) The DL assignment was sent on PACCH/UL
- If there is an UL TBF, a new attempt is undertaken on PACCH, provided
Max_Retrans_DL is not reached
- If there is no UL TBF, a new attempt is undertaken on (P)CCCH, provided
Max_Retrans_DL is not reached
- 3) The DL assignment was sent on PACCH/DL (fast DL TBF re-establishment)
- If t3193 > T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin, a new attempt
is undertaken on PACCH, provided Max_Retrans_DL is not reached.
- if t3193 T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin, a new attempt
is undertaken on (P)CCCH, provided Max_Retrans_DL is not reached
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6) Provisioning of initial Packet Power Control/Timing Advance

The network sends to the MS the initial Packet Power Control/Timing Advance as soon as computed
by the network, i.e. at receipt of the Packet Control Acknowledgement message (see peer to peer
protocol).
Message type
Global_power_control_parameter
s IE
Global_packet_timing_advance
IE
Presence
M
M
O
Coding rules
Packet Power control / Timing advance
DL TFI
Not used
power_control_parameters IE
- computed Timing Advance Value is always

provided
- Uplink Timing Advance Index & Uplink
Timing Advance Timeslot number are both
provided in case there is an on-going uplink
TBF with the corresponding MS
- Downlink Timing Advance Index is always
provided
- Downlink Timing Advance Timeslot number
is always provided (PACCH slot)
Not used
7) RLC context activation

(RRM) PCC requests (MAC) layer to start allocation of radio blocks when MS acknowledges the TBF
establishment.
8) Exceptions
The DL TBF establishment request is rejected in case :
There is no more available TFI value in the cell
The RLC context is not successfully established
There is no available radio resources : the maximum number of MS per PDCH on DL path
on all available PDCHs is reached.
In this case, NM-LLC-Discarded-req is sent to BSSGP.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
9) Retransmissions
Below are synthetized the different cases of retransmissions during a DL TBF establishment and the
use of T3190n.
DL assignment
type
on PCCCH
event and conditions

- no ACK
- Max_Retrans_DL 0
- no on-going UL TBF
- no ACK
- Max_Retrans_DL 0
- on-going UL TBF
on PACCH-UL
(on-going UL TBF)
on PACCH-DL
(fast DL TBF
re-establishment)
on CCCH
(Packet
Assignment
anticipation)
DL
- no ACK
- Max_Retrans_DL = 0
- no ACK
- on-going UL TBF
- Max_Retrans_DL 0
- no ACK
- no more on-going UL TBF
- Max_Retrans_DL 0
- no ACK
- no ACK
- t3193 OK
- Max_Retrans_DL 0
- no ACK
- t3193 NOK
- Max_Retrans_DL 0
- no ACK
- t3193 NOK
- on-going UL TBF
- Max_Retrans_DL 0
- no ACK
- no ACK
- Max_GPRS_assign_xxx 0
- no ACK
- Max_GPRS_assign_xxx = 0
- Max_Retrans_DL 0
- no ACK
- Max_Retrans_DL 0
- on-going UL TBF
- no ACK
ED
MCD
behaviour
- Max_Retrans_DL =
Max_Retrans_DL - 1
- retransmission on PCCCH
- Max_Retrans_DL =
Max_Retrans_DL - 1
- resources are re-calculated
- retransmission on PACCH-UL
see 5.3.3
- Max_Retrans_DL =
Max_Retrans_DL - 1
- Max_Retrans_DL =
Max_Retrans_DL - 1
- retransmission on (P)CCCH
see 5.3.3
- Max_Retrans_DL =
Max_Retrans_DL - 1
- retransmission on PACCH-DL
- Max_Retrans_DL =
Max_Retrans_DL - 1
- retransmission on (P)CCCH at
T3193 expiry
- Max_Retrans_DL =
Max_Retrans_DL - 1
see 5.3.3
- Max_GPRS_assign_xxx =
Max_GPRS_assign_xxx - 1
Packet
DL
Assignment
retransmission
on PACCH
- Max_Retrans_DL =
Max_Retrans_DL - 1
- retransmission on CCCH
Max_GPRS_assign_xxx
reinitialised
- Max_Retrans_DL =
Max_Retrans_DL - 1
see 5.3.3
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
no ACK:
t3193 OK:
t3193 NOK:
The Packet Control Ack has not been received on the scheduled UL block
t3193 > T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin
t3193 T3193 - T3192 + Round_Trip_Delay + T_fast_DL_margin
Max_GPRS_assign_xxx
stands
Max_GPRS_assign_agch_Retrans
for
Max_GPRS_assign_pch_Retrans
or
5.3.2.5 Activation / Deactivation of the MPDCH

Activation of the MPDCH :
Any incoming Channel Request received on RACH is answered by an Immediate Assignment
message on AGCH, provided that PDCHs are available to serve the request.
More precisely :
If there is not yet any allocated PDCH, while a PDCH is not successfully allocated with the BSC, the
MFS may receive Channel Request messages on the RACH channel. An Immediate Assignment
Reject message is then sent as there is not yet any PDCH available in the cell. Any DL LLC PDU is
queued.
Following a fault on a MPDCH, RRM tries to reconfigure a MPDCH. During that phase, a Channel
Request received on RACH is served if there are available radio resources.
After the PDCH is allocated and the MPDCH is activated (the message PRH-Conf-Master-cnf OK
has not been received by the MFS), the MFS may still receive during 30 seconds Channel Request
on the RACH channel. These requests are served and answered by an Immediate Assignment
message sent on the AGCH channel (provided there are radio resources available). Any Packet
Channel Request received on the PRACH channel is answered by an assignment message on the
PAGCH channel. DL LLC PDUs starts being served by establishment of a DL TBF through the
PCCCH channel. During 30 seconds the MS may still be not reachable on the PCCCH. The MFS
retries to establish a DL TBF MAX_DL_RETRANS times ; afterwards the LLC PDUs are discarded
and may be repeated later on by the SGSN.
In case of hopping PDCH group, the GPRS MA defined in the PSI2 message becomes the new
reference for any new assignment messages sent on PCCCH or PACCH, as soon as the MPDCH is
activated in the cell. Assignment sent on CCCH still uses reference to GPRS MA defined in the SI13
message. It may happen that during 30 seconds (i.e. the time for the MS to detect the presence of
the PBCCH) some TBF are aborted abruptly : e.g. if within 30 seconds the MS establishes an uplink
TBF on the RACH, and if it sends few seconds later a Packet Resource Request to the BSS, the
assignment message sent in response to the Packet Resource Request will include a reference to
the PSI2 message which may still be unknown for the MS. The TBF is aborted, the MS will read the
system information and perform a new uplink access afterwards.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Deactivation of the MPDCH :

As soon as the MPDCH deactivation phase is starting, any Packet Channel Request that still may be
received on the PRACH is rejected by the Packet Access Reject message (cause Read System
Information). Any Channel Request received on the RACH channel is served by an Immediate
Assignment message on the AGCH channel (provided there are available radio resources). Any new
DL TBF is established on the CCCH channel. The MS may still be not reachable on the CCCH few
seconds : in such case the MFS retries to establish the DL TBF MAX_DL_RETRANS times ;
afterwards the LLC PDUs are discarded and may be repeated later on by the SGSN.
However the MS which were either camping on the PPCH are assumed to switch quickly to the PCH
channels thanks to the broadcast of the BS_PCC_REL bit on the PBCCH.
In case of hopping PDCH group, the GPRS MA defined in the SI13 message becomes the new
reference for any new assignment messages sent on CCCH/PACCH, as soon as the MPDCH
deactivation phase starts. No TBF abort should occur in that case.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.3 Packet connection modification

5.3.3.1 MS requested modification of UL TBF
During an on-going uplink data transfer, the MS may request the BSS to modify the TBF throughput
or radio priority.
The MS is not allowed to modify the RLC mode of an on-going TBF. In case such request would be
received by the network, a Packet Access Reject is sent to MS and the TBF is released.
The BSS does not manage service precedence nor throughput modification : the BSS sends a
Packet Uplink Assignment to the MS without modifying the resources granted to the connection
(resources having become unavailable excepted)
Coding of Packet Uplink Assignment to be sent on PACCH/D of UL TBF :
Message type
Page mode
relative_or_absolute_FN
Presence
M
M
M
M
M
M
O
M
Extended_Dynamic_Allocati
on
tbf_starting_time
ALPHA
O
M
USF granularity
O
O
O
M
O
Coding rules
normal
Global TFI : UL TFI
On-going CS (stored in PCC TBF context)
CS-1
Absolute
Not used
- TA value not provided
- TA index : same as before (stored in PCC TBF context)
- TA timeslot number : same as before (stored in PCC
TBF context)
Not used
Dynamic Allocation
Not used
Not used
Not used
The timeslot Allocation with power control parameters is
used:
- USF(s) of the allocated PDCHs and its GAMMA_TN
parameters (configured by O&M)
same as before (stored in PCC TBF context)
Coding of Packet Access Reject on PACCH

Message type
Page mode
referenced_address
Wait_indication &
Wait indication size
ED
MCD
Presence
M
M
M
O
Coding rules
Normal
Global TFI: UL TFI
not used (i.e. equivalent to cause value Read
System Information cause)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.3.2 Network decided coding scheme adaptation

In case of coding scheme adaptation, the new coding scheme of an uplink TBF is notified by RLC
and stored in the PCC TBF context. RRM is not in charge of notifying the new coding scheme to the
MS.
This notification is needed in order to allow (RRM) PCC to build subsequent uplink assignment
messages for the MS (where the coding scheme is provided).
5.3.3.3 DL TBF modification
The BSS may receive from SGSN, PDUs addressed for a same MS with different QoS profiles. In
B6.2 the BSS reacts as indicated below :
It does not modify the throughput of an on-going DL TBF : all PDUs are sent with the throughput
requested for the first PDU sent on the TBF.
It does not handle service precedence modification of an on-going TBF.
In case of DL PDU received with a different RLC mode requirement than the RLC mode of an ongoing DL TBF, the following actions are undertaken:
- Current RLC mode is Acknowledged
If a LLC-PDU is received with Unacknowledged mode, this LLC-PDU is sent, with
Acknowledged mode
- Current RLC mode is Unacknowledged
If a LLC-PDU is received with Acknowledged mode, this LLC-PDU is queued (and all the
following LLC-PDUs, whatever the RLC mode), to wait for the end of the current TBF and
then
to establish a new TBF, with Acknowledged RLC mode
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.4 Packet connection release

The following table sums up the different cases of TBF releases.
Release cause
Resources which
can be deallocated,
at once
normal DL
termination
- throughput
reserved for the
TBF
- TBF context
- TFI
- TAI
(PCC-RLCRELEASE-ind,
from RLC)
normal UL
termination
Resources which
have to be frozen
Timer to
freeze the
resources
T3193
Additional actions
- a GMM-RADIOSTATUS notification is
sent to SGSN.
- in case LLC-PDU(s)
related to this TLLI are
queued,
a
NM-LLCDiscarded notification is
sent to SGSN
sent to SGSN.
- in case LLC-PDU(s)
related to this TLLI are
queued,
a
NM-LLCDiscarded notification is
sent to SGSN
The
RL-UL-STOP-req
message is sent to
BSSGP layer to release
reserved Gb resources
for the UL connection.
The
RL-UL-STOP-req
message is sent to
- throughput
- TBF context
- TFI
- TAI
- USF(s)
- throughput
reserved for the
TBF
- TBF context
- TFI
- TAI
T3191
- throughput
reserved for the
TBF
- TBF context
- TFI
- TAI
T3190n
UL
contention
failure
from RLC)
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USF(s)
T3166n
UL radio link lost

from RLC) or
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USF(s)
T3169
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USF(s)
T3182n
from RLC)
abnormal DL
end
from RLC)
DL radio link lost

from RLC) or any
unknown
cause
(*)
any
unknown
cause (*)
UL stalled TBF
from RLC)
ED
MCD
The reception of a DL
LLC PDU during T3193
triggers a fast TBF reestablishment if t3193 >
T3193
T3192
+
Round_Trip_Delay
+
T_Fast_DL_margin.
Otherwise, the DL LLC
PDU is queued until
T3193 expiry
The
RL-UL-STOP-req
message is sent to
The
RL-UL-STOP-req
message is sent to
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Release cause
Resources which
can be deallocated,
at once
no reception of
Packet Control
Ack, during an
UL TBF
establishment
- on PCCCH or
PACCH
- or on CCCH,
after
Max_GPRS_
assign_agch_
retrans
retransmissions
DL
TBF
establishment
failure,
after
Resources which
have to be frozen
Timer to
freeze the
resources
T3169
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USF(s)
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
T3190n
- throughput
reserved for the
TBF
-TBF context
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USF(s)
T3169 (UL)
T3191 (DL)
- TFI
- TAI
- USF(s)
T3169
Max_Retrans_DL
attempts
cell
becoming
unavailable for
GPRS traffic
RLC
mode
modification
during an UL
TBF
ED
MCD
Additional actions
The
RL-UL-STOP-req
message is sent to
sent to SGSN.
- DL LLC PDUs which are
queud are discarded and
SGSN is notified
a
Packet
PDCH
Release message is
sent on all the PACCH
of the cell
a
Packet
Access
Reject is sent
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Release cause
Resources which
can be deallocated,
at once
Resources which
have to be frozen
Timer to
freeze the
resources
- TFI
- TAI
(if an assignment
message
has
already been sent to
the MS)
T3190n
Additional actions
DL
TBF
abnormal
release,
following a
PDCH release
(PRH-PDCHRELEASE-ind,
from RLC)
1) monoslot TBF
or multislot TBF
whose PACCH is
carried by the
released PDCH
- throughput
reserved for the
TBF
-TBF context
2) multislot TBF
whose PACCH
is not carried by
the
released
PDCH
UL
abnormal
release,
following
a
The TBF context in

RLC
is
released
immediately, if already
established.
At T3190n expiry, a
TBF is re-established
if there are queued
LLC-PDUs
The
TBF
is
not
released
but
its
throughput is implicitly
reduced due to PDCH
release
PDCH release
(PRH-PDCHRELEASE-ind,
from RLC)
1) monoslot TBF
carried by the
released PDCH
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
(if an assignment
message
has
the MS)
T3169
The
RL-UL-STOP-req
message is sent to
2) multislot TBF
whose PACCH
is carried by the
released PDCH
- throughput
reserved for the
TBF
-TBF context
- TFI
- TAI
- USFs
(if an assignment
message
has
the MS)
T3169
The
RL-UL-STOP-req
message is sent to
The
TBF
is
not
released
but
its
throughput is implicitly
reduced due to PDCH
release
3) multislot TBF
whose PACCH
is not carried by
the
released
PDCH
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note: After a TBF context release, a new TBF will be established in case of receipt of either a DL
LLC PDU or an UL access request.
Note (*): any unknown cause means any cause which is not specified in the table.
5.3.5
Uplink error handling
5.3.5.1 Supported uplink messages

RRM layer shall recognize the following messages:
Message name
Signature
Channel Request
Access Burst
Packet Channel Request (in Access Burst (11 bits or 8
case of supported MPDCH)
bits)
Packet
Control 4 access bursts (11 bits or 8
Acknowledgement message
bits)
Packet Resource Request < MESSAGE_TYPE : bit (6)
message
== 000101 >
Packet Downlink Ack/Nack < MESSAGE_TYPE : bit (6)
message
with
Channel == 000010 >
Request description
5.3.5.2 Decoding of padding bits
The release 97 BSS may establish TBFs with future releases mobile stations. Then, the
recommended behaviour stated in 04.60 should apply when decoding the padding bits which allow
future extension. Note that 04.60v6.4.0 only defines the Ignore behaviour in downlink, but it shall
also apply the same in uplink, since the spare padding structure has also been included in uplink
RLC/MAC control messages.
Padding bits are necessary to fill the message up to the desired length. The padding bits may be the
null string. Otherwise, the padding bits starts with bit 0, followed by spare padding.
< padding bits > ::= { null | 0 < spare padding > ! Ignore : 1 bit** = < no string > } ;
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The padding sequence used for 'spare padding' in this EN, see GSM 04.07, is a repetition of octet
00101011, starting on an octet boundary.
Then, received padding bits may:
be null if the message contents fill the whole RLC/MAC control block,
start with 0 if the MS release is 97,
start with 1 if the MS release is more than 97.
If the received padding bits start with 0, the BSS shall accept any value of the spare padding. See
04.07: on receiver side, spare may have any value. The spare padding shall be discarded.
If the received padding bits start with 1, the BSS shall enter the ignore branch ie accept and discard
any value of the remaining string; see 04.07: on receiver side, spare may have any value.
5.3.5.3 On receipt of unexpected uplink message
When an uplink message is received which is not expected by the BSS in its current protocol state,
the BSS shall ignore the message.
5.3.5.4 On receipt of not supported messages
Messages of unknown or not implemented message type shall be ignored (generic error label
unknown message type. For instance, in release 97:
Message name
Packet Cell Change Failure
message
Packet Measurement Report
Packet PSI Status
ED
MCD
Signature
< MESSAGE_TYPE : bit (6)
== 000000 >
== 000100 >
== 000111 >
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note: since the cell configuration is broadcasted on BCCH or PBCCH, such messages should not be
received.
Furthermore a Packet Mobile TBF Status should not be received after RRM has sent a RLC/MAC
control message + polling because a Packet Control Acknowledgment (ie 4 access bursts) is then
awaited, and the BTS should not be able to decode any normal burst.
The relevant TBF shall not be released in case of receipt of such messages.
5.3.5.5 On receipt of corrupted uplink messages
When a message containing a syntactically incorrect data is received, the message shall be ignored.
Exceptions to these rules are indicated below.
Message name
Channel Request
Packet
Control
Acknowledgement
message
message
Packet Downlink Ack/Nack

with
Channel
Request
description
Behaviour
no error may be detected by RRM
Unknown type of access: send Packet Access
Reject
Unknown multislot class: the request shall be
regarded as a multislot class 1.
If at least one Access Burst is correctly
decoded, the Acknowledgement is regarded as
valid
CTRL_ACK bits shall be ignored
Unknown global TFI when a TBF has already
been established: the Packet Resource Request
shall be discarded.
regarded as a multislot class 1,
Invalid Change_Mark: the Packet Resource
Request is treated as usual
Unknown global TFI: the Packet Resource

Request shall be discarded.
regarded as a multislot class 1.
Note: in this Release of the BSS, RRM sublayer may only receive a reserved value in Multislot class
IE, since Peak Throughput Class and CTRL_ACK bits are ignored.
5.3.5.6 On no receipt of an expected uplink messages
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Message name
Packet
Control
Acknowledgement
message

message
ED
MCD
Behaviour
After a Packet Uplink Assignment, no specific
defence procedure applies
After a Packet Downlink Assignment, specific
defence procedures are described in (PCC)
functionalities.
The Packet Resource Request message is not
particularly awaited by RRM. Then no defence
procedure is entered on network side if an MS does
not send any Packet Resource Request. If another
message is received instead of a scheduled Packet
Resource Request message, it will be discarded by
RRM layer.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.6 SDL diagrams

5.3.6.1 Downlink
5.3.6.1.1
Messages
The following messages are exchanged between MsDl process and PRH:
- radioResReq: to request radio resources (MsDl--> PRH)
- radioResRsp: response to the previous message (PRH-->MsDl)
- radioResLost: all resources in the cell are lost (PRH-->MsDl)
- TFIAvailable: A TFI becomes available
5.3.6.1.2
States
- WDRadio:
Wait For DL Radio resource

Radio resources have been requested to PRH block
- WDTFI:
Wait For TFI

The request is queued and waits for an available TFI
- WDETBF:
Wait For DL TBF establishment

TBF context establishment has been requested to RLC.
- WDGSM:
Wait For CCCH retransmission delay

Immediate assignment has been sent to the MS, on CCCH.
T_assign_pch_pacch or T_assign_agch_pacch is activated
- WDMS:
Wait For Mobile acknowledgement

Packet DL assignment + polling has been sent to the MS. A timer is
activated (T3193 or Max_pda_life_time or T_Ack_Wait or T_assign_pch/agch_pacch).
- WDATBF:
Wait For DL TBF activation

MAC has been requested to start DL radio blocks allocation.
- DReady:
DL transfer Ready
DL transfer is on-going.
- WDRRadio: Wait For DL Radio Resource release

A timer to freeze resources has been activated.
- WDREL:
RLC has notified RRM, that DL TBF is being released
- WDRTBF:
Wait for DL TBF release
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
RL-DL-Unitdata-req
WDRadio
TFIAvailable
WDTFI
radio-ResRep
WDETBF
(CCCH)
WDGSM
1
Retry on
CCCH
T_assign_pch/agch
_pacch expiry
(PCCCH or PACCH)
WDMS
PCC-CTRL-Ack-ind
2
1
WDATBF
RL-DL-Unitdata-req
AND
T3193 activated
1
PCC-CTRL-Activate-cnf
DREADY
1
TRN-DL-FLOW-END-ind
2
WDREL
WDRTBF
2
PCC-RLC-Release-ind
LLC-PDU in queue
ED
MCD
WDRRadio
Freeze-timer
expiry
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
1(24)
idle
RL-DLUNITDATA
-req
MS unknown
from RRM
(no on-going
DL TBF)
TFI
available?
Y
'InitMsDl'
Queue
radioResReq
F_Abort=
False
TFI allocation
and PCC TBF
context creation
Queue
LLC PDU
is queued
WDTFI
LLC PDU
is queued
radio resources
are requested
to PRH block
a throughput is
reserved at MAC
level with
PRH-PDTCH-ASSIGN-req
This flag is set
when an event
triggering a release
occurs
WDRadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
2(24)
WDTFI
RL-DLUNITDATA
-ind
Queue
LLC-PDU
reception
NM-FLUSHLL-ind
radioRes
Lost
all resources
in the cell
are lost
LLC-PDU
is queued
NM-FLUSH
-LL-res
NM-LLCDiscarded
-req
except in the case

where the cell
unavailability is due
to Gb failure
WDTFI
TFI
available
'InitMsDl'
radioResReq
F_Abort=
False
WDRadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3(24)
WDRadio
(1/2)
Process MsDl
radioResRsp
test if resources
have been
allocated
PRH-PDTCHASSIGN-cnf
has been
received
by PRH,
from MAC
'AllocOk'
N
Y
F_Abort
N
NM-FLOWCONTROLMS
from B6.2
only
PCC-RLCESTABLISHreq
TBF context
establishment
is requested
to RLC
MCD
Release
throughput
N
Y
'lifeTime'
NOK
'Ok'
WDETBF
ED
F_Abort
radioResReq
NM-LLCif the life-time

has not expired Discarded
and if the Cause -req
in radioResRsp
authorizes it
WDRadio
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4(24)
WDRadio
(2/2)
Process MsDl
RL-DLUNITDATA
-ind
Queue
WDRadio
LLC-PDU
reception
NM-FLUSHLL-ind
LLC-PDU
is queued
NM-FLUSH
-LL-res
F_Abort=
True
radioRes
Lost
all resources
in the cell
are lost
because of cell lock
or BSC cell failure
or BVC-PTP failure
NM-LLCDiscarded
-req
except in the case

where the cell
to Gb failure
WDRadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5(24)
Process MsDl
WDETBF
(1/2)
PCC-RLCESTABLISH
-cnf
RLC response
F_Abort
True
False
Nret =
Max_Retrans_DL
PCC-RLCRELEASE
-req
Max_retrans_DL is the
number of allowed retries
for the whole DL TBF
establishment procedure
WDRTBF
F_Tbf = True
TBF established
at RLC level
several cases:
-1) fast DL TBF re-establishment
-2) no concurrent TBF, no MPDCH
-3) no concurrent TBF, MPDCH
-4) UL concurrent TBF
1) "Pacch_dl"
(fast DL TBF
re-establishment)
case?
2) 'ccch'
PCC-DLASSIGN-req
WDMS
- Packet DL
assignment
+ polling
sent on
PACCH/DL
Set
on PCH or
(T_assign
on AGCH
_pch/agch_pacch)
PCC-CHNASSIGN-req
WDGSM
PACCH slot
assignment
sent on CCCH
4) 'pacch_ul'
3) 'pccch'
Set
(max_Pda_Lifetime)
PCC-DLASSIGN-req
WDMS
PCC-DLASSIGN-req
Packet DL
assignment
+ polling
sent on PACCH/UL
Packet DL
Set(T_Ack_Wait)
assignment
+ polling
sent on PCCCH
WDMS
T3193 is
already
activated
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
6(24)
WDETBF
(2/2)
RL-DLUNITDATA
-ind
Queue
WDETBF
ED
MCD
NM-FLUSH
-LL-ind
LLC-PDU
is queud
radioResLost
all resources
in the cell are
lost, throughput
has been released
NM-FLUSH
-LL-res
F_Abort=
True
NM-LLCDiscarded
-req
except in the case

where the cell
to Gb failure
release
throughput
F_Abort=
True
WDETBF
WDETBF
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
7(24)
WDGSM
T-assign
-pch/agch_pacch
expiry
Nass =
Max_GPRS_
assign_pch/agch
RL-DLUNITDATA
-ind
maximum
number of
retries on PACCH
Set
(T_assign_
pch/agch_pacch)
PCC-DLASSIGN-req
WDMS
Queue
WDGSM
Packet DL
assignment
+ polling
sent on PACCH
ccch case
NM-FLUSH
-LL-ind
radioResLost
NM-FLUSH
-LL-res
reset
(T_assign_
pch/agch_pacch)
reset
(T_assign_
pch/agch_pacch)
NM-LLCDiscarded
-req
release
throughput
PCC-RLCRELEASE
-req
PCC-RLCRELEASE
-req
except in the
case where
the cell
unavailability
is due
to Gb failure
WDRTBF
WDRTBF
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
8(24)
WDMS
(1/5)
PCC-CTRL
ACk-ind
Reset
timer
MS acknowledgement
either T-Ack_Wait
or Max_Pda_Lifetime
or T_assign_pch/agch_pacch
or T3193
F_Abort
True
false
PCC-TAUPDATE-req
initial timing
advance value
is provided
to the MS
F_Tbf
True
PCC-RLCRELEASE
-req
PCC-RLCACTIVATE
-req
MAC is requested
to start
DL radio blocks
allocation
WDRTBF
False
Set
(freeze_timer)
timer to freeze
resources
(see 5.3.3)
WDRRADIO
WDATBF
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
ED
MCD
9(24)
WDMS
(2/5)
RL-DLUNITDAT-ind
267129603.doc
10/08/2000
NM-Flush
-LL-ind
Queue
NM-FLUSH
-LL-res
WDMS
F_Abort=
True
release
throughput
radioResLost
F_Abort
=True
NM-LLCDiscarded
-req
WDMS
WDMS
04 Released
3BK 11202 0265 DSZZA
10(24)
WDMS
(3/5)
Process MsDl
T_assign_pch/agch_pacch
(establshment on CCCH)
PCC-DLCONTROL
-cnf (fail.)
unknown PDU
received in
scheduled
UL block
activated
timer?
Max_Pda_Lifetime
(establishment on PCCCH)
other cases
WDMS
an action will
be undertaken
at timer expiry
Max_Pda_Lifetime
is stopped
Nret=0?
Y
NM-LLCDiscarded
-req
Nret =
Nret - 1
UL TBF?
Y
resources have
to be
re-calculated
Set(Max_Pda
_Life_Time)
resources
allocation
PDCHs
allocation
taking into
account the
concurrent
TBF
PCC-DLAssign-req
PCC-DLassign-req
GMM-radioStatus-req
release
throughput
SET
(T_Ack_Wait)
UL concurrent
TBF ?
WDMS
Release
throughput
Packet DL
assignment
+ polling sent
on PCCCH
PCC-RLCRelease-req
WDRTBF
packet DL
assignment
+ polling
sent on PACCH/UL
WDMS
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
11(24)
T3193
(fast DL TBF
re-establishment
on PACCH/DL)
activated
timer?
T-Ack_Wait
(establishment
on PACCH/UL)
T_Ack_Wait
is stopped
Nret=0?
Y
N
Nret=
Nret-1
UL concurrent
TBF always
established?
UL TBF?
N
Y
SET
(T_Ack_Wait)
PCCCH or
CCCH ?
'ccch'
PCC-DLassign-req
WDMS
packet DL
assignment
+ polling
sent on
PACCH/UL
Set
(T_assign_
pch/agch_pacch)
PCC-CHNASSIGN-req
WDGSM
ED
MCD
'pccch'
Set
(max_Pda_Lifetime)
PACCH slot
assignment
sent on CCCH
PCC-DLASSIGN-req
Packet DL
assignment
+ polling
sent on PCCCH
WDMS
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
12(24)
fast DL TBF
re-establishment
on PACCH/DL
Process MsDl
N
UL TBF?
N
WDMS
T3193
expiry is
awaited
to take
a decision
t3193 is the time

remaining before
expiry of T3193
t3193 OK:
t3193 > T3193 - T3192 +
Round_Trip_Delay +
T_Fast_DL_Margin
T3193
OK?
UL concurrent
TBF ?
Y
T3193
is stopped
Nret=0?
Nass=0?
Y
N
Nret=
Nret-1
Nass=
Nass-1
T3193
is stopped
release
throughput
resources have
to be
re-calculated
resources
allocation
PDCHs
allocation
taking into
account the
concurrent
TBF
PCC-DLASSIGN-req
packet DL
assignment
+ polling
sent on
PACCH/UL
T3193 is
activated
SET
(T_Ack_Wait)
PCC-DLassign-req
Packet DL
assignment
+ polling
sent on
PACCH/DL
WDMS
WDMS
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
13(24)
WDMS
(4/5)
Max_PDA_
Lifetime
expiry
T_assign_
pch/agch_
pacch expiry
Nass=0?
Y
Mret=0?
Y
B
N
Mret =
Mret - 1
UL concurrent
TBF ?
PCC-DLASSIGN-req
release
throughput
resources have
to be
re-calculated
WDMS
resource
allocation
PDCHs
allocation
taking into
account the
concurrent TBF
UL TBF?
N
Set
(T_assign
_pch/agch_pacch)
PCC-CHNASSIGN-req
number of
allowed DL TBF Nass= Nass-1
establishment
attempts
Set
(T_assign
_pch/agch_pacch)
DL TBF
establishment
procedure is
started again
SET
(T_Ack_Wait)
WDGSM
PCC-DLassign-req
T_Ack_Wait
expiry
Number of
allowed
retransmissions
of Packet DL
assignment
Packet DL
assignment
+ polling
sent on PACCH
packet DL
assignment
+ polling
sent on
PACCH/UL
WDMS
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
14(24)
WDMS
(5/5)
Process MsDl
T3193
expiry
Mret = 0?
Y
N
UL TBF?
Y
release
throughput
resources
allocation
SET
(T_Ack_Wait)
PCC-DLassign-req
UL concurrent
TBF ?
N
resources
have to be
re-calculated
PCCCH
or CCCH?
PDCHs
allocation
taking into
account the
concurrent
TBF
Set
(Max_pda_Lifetime)
Packet DL
assignment
+ polling
sent on
PACCH/UL
'pccch'
PCC-DLAssign-req
WDMS
'ccch'
Set
(T_assign_
pch/agch_pacch)
Packet DL
PCC-DLassignment
Assign-req
+ polling
sent on PCCCH
PACCH slot
assignment
sent on CCCH
WDGSM
WDMS
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
15(24)
Process MsDl
WDATBF
(1/2)
PCC-RLCActivate-cnf
RLC (MAC)
acknowledge
F_Abort
False
True
TRN-DLUNITDATA
-req
DReady
ED
MCD
LLC PDUs
are sent to
RLC
(except if the
current RLC
mode is
Unacknowledged
and if a LLC-PDU
has to be sent
in Acknowledged
mode)
PCC-RLCRELEASE
-req
WDRTBF
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
ED
MCD
16(24)
WDATBF
(2/2)
RL-DLUNITDATA
-ind
Queue
WDATBF
267129603.doc
10/08/2000
NM-FLUSH
-LL-ind
radioResLost
NM-FLUSH
-LL-res
F_Abort
=True
F_Abort=
True
release
throughput
NM-LLCDiscarded
-req
WDATBF
WDATBF
04 Released
3BK 11202 0265 DSZZA
Process MsDl
17(24)
DReady
(1/3)
NM-FLUSH
-LL-ind
radioResLost
NM-FLUSH
-LL-res
NM-LLCDiscarded
-req
release
throughput
PCC-RLCRELEASE
-req
PCC-RLCRELEASE
-req
WDRTBF
if there are
queued
LLC-PDUs
PCC-ULCHAN2-REQ
-ind
UL TBF
establishment
request
PCC-RLCrelease-ind
abnormal
TBF termination,
notified by RLC
UL-establish
-req
towards
process
MsUl
NM-LLCDiscarded
-req
if there are
queued
LLC-PDUs
DReady
GMM-Radio
-Status-req
Release
throughput
Set
(freeze_timer)
WDRTBF
WDRRADIO
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
18(24)
DReady
(2/3)
RL-DLUNITDATA
-ind
LLC PDUs
queued?
N
same
RLC mode?
Y
N
Queue
cur. mode
= Ack?
MCD
last LLC-PDU
forwarding is
on-going
(TBF is being
released)
TRN-DLFLOW-END
-res
RRM will send

no more LLC PDUs
to RLC
Test if LLC PDUs

are already
queued
test if the RLC
mode is the same
than the mode
of the established
TBF
WDREL
Y
LLC PDU
is queued
DReady
ED
TRN-DLFLOW-END
-ind
TRN-DLUNITDATA
-req
received LLC PDU

is forwarded to
RLC
DReady
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
19(24)
DReady
(3/3)
Process MsDl
PRH-PDCH
-Release-ind
PACCH
released?
N
D_ready
PDCH release
Y
throughput is
implicitely
reduced due to
PDCH release
release
throughput
monoslot TBF
or multislot TBF
whose PACCH
is carried by the
released PDCH
PCC-RLCRELEASE
-req
WDRTBF
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
20(24)
WDREL
(1/2)
NM-FLUSH
-LL-ind
radioResLost
NM-FLUSH
-LL-res
NM-LLCDiscarded
-req
release
throughput
PCC-RLCRELEASE
-req
PCC-RLCRELEASE
-req
WDRTBF
if there are
queued
LLC-PDUs
PCC-ULCHAN2-REQ
-ind
UL TBF
establishment
request
PCC-RLCrelease-ind
abnormal
TBF termination,
notified by RLC
UL-establish
-req
towards
process
MsUl
NM-LLCDiscarded
-req
if there are
queued
LLC-PDUs
WDREL
GMM-Radio
-Status-req
Release
throughput
Set
(freeze_timer)
WDRTBF
WDRRADIO
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsDl
21(24)
WDREL
(2/2)
PRH-PDCH
-Release-ind
N
D_ready
PDCH release
PACCH
released?
RL-DLUNITDATA
-req
Queue
Y
release
throughput
monoslot TBF
or multislot TBF
whose PACCH
is carried by the
released PDCH
WDREL
PCC-RLCrelease-ind
LLC-PDU
is queud
A new DL TBF
has to be
established
Radio
resources
are frozen
normal
TBF termination,
notified by RLC
PDCHs,
TFI, TAI
Set
(T3193)
WDRRADIO
PCC-RLCRELEASE
-req
WDRTBF
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
22(24)
WDRTBF
Process MsDl
RL-DLUNITDATA
-ind
radioResLost
NM-LLCDiscarded
-req
WDRTBF
ED
MCD
if there are
queued
LLC-PDUs
PCC-RLCrelease-cnf
PCC-RLCrelease-ind
NM-FLUSH
-LL-ind
Queue
Set
(freeze_timer)
NM-FLUSH
-LL-res
WDRTBF
WDRRADIO
WDRTBF
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
23(24)
WDRRADIO
(1/2)
Process MsDl
NM-FLUSH
-LL-ind
FreezeTimer
expiry
radioResLost
NM-FLUSH
-LL-res
frozen
resources are
released
Reset
(FreezeTimer)
WDRRADIO
LLC-PDU?
Yes
'InitMsDl'
radioResReq
F_Abort=
False
no
test if
LLC-PDU(s)
are queued
NM-LLCDiscarded
-req
if there are
queued
LLC-PDUs
TFI allocation
and PCC TBF
context creation
radio resources
are requested
to PRH block
a throughput is
reserved at MAC
level with
PRH-PDTCH-ASSIGN-req
This flag is set
when an event
triggering a release
occurs
WDRadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
24(24)
WDRRADIO
(2/2)
Process MsDl
RL-DLUNITDATA
-ind
T3193?
Y
t3193 < or = T3193 - T3192

+ Rounr_Trip_Delay
+ T_Fast_DL_margin
t3193?
T3193
activated?
N
t3193 is the time
remaining before
expiry of T3193
t3193 > T3193 - T3192

+ Round_Trip_Delay
+ T_Fast_DL_margin
Queue
too late to undertake

fast re-establishment
Queue
PCC-RLCESTABLISH
-req
WDRRADIO
WDETBF
ED
MCD
WDRRADIO
the previous
radio resources
are used
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.3.6.2 Uplink
5.3.6.2.1
Messages
The following messages are exchanged between MsUl process and PRH:
- radioResReq:
to request radio resources (MsUl--> PRH)
- radioResRsp:
response to the previous message (PRH-->MsUl)
- radioResLost:
all resources in the cell are lost (PRH-->MsUl)
- ul-establish-req:
request received in a Packet DL Ack
5.3.6.2.2
States
- WURadio:
Wait For UL Radio resource

Radio resources have been requested to PRH block
- WUETBF:
Wait For UL TBF establishment

TBF context establishment has been requested to RLC.
- WULSP:
Wait For LSP allocation

Request of an LSP has been sent to BSSGP
- WUGSM:
Wait For CCCH transmission delay

Immediate assignment has been sent to the MS, on CCCH.
T_assign_agch_pacch is activated
- WUMS:
Wait For Mobile acknowledgement

Packet UL assignment + polling has been sent to the MS. T_ack_Wait timer is
activated.
- WUATBF:
Wait For DL TBF activation

MAC has been requested to start UL radio blocks allocation.
-UDReady:
UL transfer Ready
UL transfer is on-going.
- WDRRadio: Wait For DL Radio Resource release

A timer to freeze resources has been activated.
- WURTBF:
ED
MCD
Wait for UL TBF release
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
PCC-UL-CHN-REQ-ind (TBF estab.)

PCC-UL-RES-REQ-ind
UL-establish-req
WURadio
radio-ResRep
WUETBF
1
WULSP
RL-UL-Start-cnf
(CCCH)
RL-UL-Start-cnf
(PCCCH/PACCH)
WUGSM
1
T_ul-assign_ccch
expiry
1
WUMS
PCC-CTRL-Ack-ind
WUATBF
PCC-RLC-RELEASE-ind
(normal release)
UReady
1
WURTBF
WURRadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
1(13)
idle
(1/2)
Process MsUl
PCC-ULRES-REQ-ind
PCC-ULCHN-REQ
-ind
Packet
Resource
request
(2 phase
access)
'OneBlock'
Packet
Channel
request
'true'
False
Set
(T_ul_access_max)
TFI
available?
Y
'InitMsUl'
radioResReq
F_Abort =
false
TFI allocation
and PCC TBF
context creation
radio resources
are requested
to PRH block
a throughput
is reserved at
MAC level
with PRH-PDTCHASSIGN-req
WURadio
'AllocOk'
No
'Yes'
'destAssign'
ED
MCD
'ccch'
'pccch'
PCC-CHNASSIGN-req
(Reject)
PCC-ULREJECT
-REQ
one UL radio block

is reserved at
MAC layer
(The time between
Packet Channel req
reception and UL
allocated radio block
has to be smaller
than T_ul_assign_pcch
'destAssign'
'ccch'
PCC-CHNASSIGN-req
'pccch'
immediate
assignment
PCC-ULASSIGN
-REQ
Packet UL
assignment
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2(13)
Process MsUl
idle
(2/2)
UL TBF establishment
request, received in
a Packet DL ACK
ULestablish-req
Set
(T_ul_access_max)
N
WUTFI
TFI
available?
Y
'InitMsUl'
radioResReq
F_Abort =
false
TFI allocation
and PCC TBF
context creation
radio resources
are requested
to PRH block
a throughput
is reserved at
MAC level
with PRH-PDTCHASSIGN-req
WURadio
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3(13)
WURadio
Process MsUl
radioResRsp
'AllocOk'
T_ul_access_max
expiry
radioResLost
no
'Yes'
PCC-RLCESTABLISH
-req
WUETBF
TBF context
establishment
is requested
to RLC
Reset
(T_ul_access_max)
'destAssign'
'pccch'
PCC-ULREJECT
-REQ
ED
MCD
'ccch'
PCC-CHNASSIGN-req
(Reject)
'pacch'
PCC-ULREJECT
-REQ
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
4(13)
WUETBF
Process MsUl
T_ul_access_maxPCC-RLCESTABLISH
expiry
-cnf
RLC response
radioResLost
Reset
(T_ul_access_max)
F_Abort= True
WUETBF
F_Abort
F_Abort= True
True
False
'destAssign'
'pccch'
'pacch'
PCC-ULREJECT
-REQ
RL-ULSTART-rq
WULSP
ED
MCD
throughput
allocation
in BSSGP
WUETBF
'ccch'
PCC-CHNASSIGN-req
(Reject)
PCC-RLCRELEASE
-req
WURTBF
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
5(13)
WULSP
T_ul_access_maxRL-ULexpiry
START-cnf
F_Abort= True
BSSGP
response
radioResLost
Reset
(T_ul_access_max)
F_Abort
true
False
Release
throughput
WULSP
'destAssign'
F_Abort= True
'pccch'
'ccch'
PCC-ULREJECT
-REQ
PCC-CHNASSIGN-req
(Reject)
WULSP
RL-ULSTOP-req
PCC-RLCReset
(T_ul_access_max) RELEASE
-req
WURTBF
'destAssign'
'ccch'
'pacch_dl'
Set
(T-assignagch-pacch)
PCC-CHNASSIGN-req
Set(T_Ack_Wait)
immediate
assignment
WUGSM
ED
MCD
PCC-ULASSIGN-req
'pccch'
Set(T_Ack_Wait)
Packet UL
assignment
+ polling
PCC-ULASSIGN-req
Packet UL
assignment
+ polling
WUMS
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6(13)
Process MsUl
WUGSM
ccch case
T_assign_
agch_pacch
expiry
radioResLost
Set
T_assign_
agch_pacch)
RL-ULSTOP-req
Nass =
maximum numberPCC-RLCMax_GPRS_assign of retries on
RELEASE
_agch_retrans
-req
PACCH
PCC-ULASSIGN-req
Packet UL
assignment
+ polling
WURTBF
WUMS
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
7(13)
WUMS
(1/2)
PCC-CTRLACK-ind
timer is
stopped
MS
acknowled
-gement
radioResLost
T_Ack_Wait
or
T_assign_agch_pacch
F_Abort= True
F_Abort
True
false
PCC-RLCACTIVATEreq
MAC is requested
to start UL radio
blocks allocation
WUATBF
ED
MCD
PCC-RLCRELEASE
-req
RL-ULSTOP-req
WUMS
WURTBF
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
8(13)
WUMS
(2/2)
T_assign_
agch_pacch
expiry
Nass=0?
T_Ack_Wait
expiry
Y
PCC-CTRL
-Ack-ind
(failed)
unknown PDU
received in
scheduled
UL block
Reset
(T_Ack_Wait)
N
SET
(T_assign_
agch_pacch)
PCC-ULAssign-req
WUMS
Release
throughput
Packet UL
assignment
+ polling
RL-ULSTOP-req
PCC-RLCRELEASE-req
WURTBF
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
ED
MCD
9(13)
WUATBF
PCC-RLCACTIVATE
-cnf
False
UReady
267129603.doc
10/08/2000
RLC
acknowledgement
F_Abort
PCC-RLCRELEASE
-req
WURTBF
radioResLost
True
F_Abort= True
RL-ULSTOP-req
WUATBF
04 Released
3BK 11202 0265 DSZZA
Process MsUl
10(13)
UReady
(1/2)
TRN-ULUNITDATA
-ind
PCC-TLLI
-NOTIFY
-ind
RL-ULUNITDATA
-req
TLLI stored
in the context
UL contention
resolution
information
(MS TLLI)
PCC-RLCMODIFYind
CS
modification
context is
updated
UReady
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
11(13)
URead(2/2)
PCC-ULRES-REQ-ind
'='
'RLCmode'
PCC-RLCRelease-ind
abnormal
PCC-RLCTBF termination Release-ind
notified by RLC
RL-ULSTOP-req
Release
throughput
Release
throughput
PCC-RLCRELEASE
-req
Set
(freezeTimer)
resources are
released
RL-ULSTOP-req
RL-ULSTOP-req
radioResLost
WURTBF
normal
TBF termination
notified by RLC
'/='
PCC-ULReject-req
on PACCH
WURRADIO
Release
throughput
PCC-RLCRELEASE
-req
WURTBF
PCC-ULASSIGN-req
on PACCH
same resources
as previously
UReady
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Process MsUl
ED
MCD
12(13)
WURTBF
PCC-RLCRelease-ind
267129603.doc
10/08/2000
PCC-RLCRelease-cnf
Set
(freezeTimer)
WURRADIO
04 Released
3BK 11202 0265 DSZZA
Process MsUl
ED
MCD
13(13)
WURRADIO
FreezeTimer
expiry
frozen
resources
are released
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.4
TRN Entity detailed description
TRN entity deals with the following functions:

- DL LLC PDU transfer
- UL LLC PDU transfer
5.4.1 DL LLC PDU transfer

5.4.1.1 DL Packet connection control
When RRM receives an LLC PDU addressed to a MS for which no DL TBF has been established, a
DL TBF establishment is undertaken. If MAX_RETRANS_DL establishment attempts fail, the LLC
PDUs are discarded and NM-LLC-DISCARDED-req is sent to BSSGP.
If RRM receives an LLC PDU destined for a MS for which a DL TBF has already been established,
two cases are possible.
The RLC mode required is the same as the already established TBF RLC mode :
The LLC PDU will be sent on that TBF.
The RLC mode required is not the same as the already established TBF RLC.
(see 5.3.3.1)
5.4.1.2 DL PDU storage
DL LLC PDU received from BSSGP are stored per MS queues within RRM :
during a TBF establishment
or on TFI unavailability
or when congestion occurs on RRM-RLC interface.
or when the RLC mode is modified (see 5.3.3.1)
The order in which an LLC PDU shall be stored in the queue shall be determined by its PDU lifetime.
5.4.1.3 DL LLC PDU lifetime expiry
If the lifetime of an LLC PDU in a MS queue expires, then the LLC PDU shall be deleted and the
notification NM-LLC-DISCARDED-req shall be sent to the SGSN.
5.4.1.4 DL LLC PDU Flush
When RRM receives a NM-FLUSH-LL-ind message, all pending LLC PDU(s) related to the MS shall
be deleted. Then message NM-FLUSH-LL-res primitive is called to acknowledge the SGSN.
RRM requests RLC to stop the DL TBF.
DL LLC PDU Rerouting is not implemented in step 1, i.e. the flush procedure is the same whether or
not a target cell is provided by the SGSN.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.4.1.5 DL congestion control
5.4.1.5.1
Gb congestion control principles
The principle of the BSSGP flow control procedures is that the BSS sends to the SGSN flow control
parameters which allow the SGSN to locally control its transmission output in the SGSN to BSS
direction.
Description of the flow control performed at SGSN side :
The SGSN shall perform flow control on each BVC and on each MS. The flow control is performed
on each LLC PDU first by the MS flow control mechanism and then by the BVC flow control
mechanism. If the LLC PDU is passed by the individual MS flow control, the SGSN then applies the
BVC flow control to the LLC PDU. If an LLC PDU is passed by both flow control mechanisms, the
entire LLC PDU is delivered to the Network Services for transmission to the BSS.
MS Flow control
MS Flow control
MS Flow control
BVC Flow control
BSS
Figure 68 : Gb congestion control at SGSN (1/2)
The BSSGP flow control model is the leaky bucket algorithm shown in below (see Figure 69). The
model of the algorithm is that an LLC PDU is passed by the algorithm as long as the bucket counter
(B) plus the length of the LLC PDU does not exceed the bucket size Bmax. When the LLC PDU is
passed, the LLC PDU length is added to B. Any PDU not transmitted is delayed until B plus the LLC
PDU length is less than Bmax.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Arrival of LLC PDU p with

length L(p) at time Tc
B* = B + L(p) - (Tc - Tp) R
B* < L(p)
?
yes
B - (Tc - Tp) R < 0
B = L(p)
no
B* > Bmax
?
no
B = B*
Tp = Tc
yes
Delay LLC PDU
Pass LLC PDU
Figure 69 : Gb congestion control at SGSN (2/2)

The variables used by the algorithm are managed by the SGSN :
Bmax : bucket size. Set by the BSS for each cell and each mobile station. Bmax shall be
large enough to accommodate at least one LLC PDU.
R : leak rate of the bucket.
B : bucket counter. (value at time Tp)
B* : predicted value of the bucket counter.
L(p) : length of LLC PDU p.
Tp : the time that the last LLC PDU p was transferred.
Tc : arrival time of LLC PDU p.
The initial conditions of these variables in the SGSN are :
Bmax = 0. For BVCs, this value is valid until Bmax is received in the Flow Control-BVC.
For MSs, this value is valid until Bmax_default_ MS is received in the Flow-Control-BVC
message.
R = 0. For a BVC, this value is valid until a Flow-Control-BVC message is received.
For an MS, this value is valid until a Flow-Control-BVC message is received.
B = 0 (the bucket is empty).
Tp = the current time for the first LLC PDU.
The SGSN shall not transmit a LLC PDU on a BVC until a Flow-Control-BVC message is received
from the BSS for that BVC.
The flow control functions as follows :
When a LLC PDU p arrives at current time Tc, the variable B* is set to the predicted bucket size if
the LLC PDU were to be transferred to the BSS.
This is given by the previous bucket size plus the new LLC PDU size, B* = B + L(p), less the amount
that the bucket will have leaked away since the last compliant LLC PDU, R * (Tc - Tp).
If this is less than the LLC PDU size then the LLC PDU is compliant and the bucket size B is reset to
L(p) and the LLC PDU is passed.
When a compliant LLC PDU is passed the last LLC PDU transfer time is set to the current time, Tp =
Tc.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
If the bucket has not completely leaked away then the bucket has to be checked to see if the limit
Bmax is going to be exceeded, B* > Bmax.
If the limit is exceeded then the LLC PDU is non compliant and is delayed for some time period, and
no updates are done on the variables.
If the bucket limit Bmax is not exceeded then the LLC PDU is compliant and the bucket counter (B)
is set equal to the value of B*.
When a conforming LLC PDU is passed then the last LLC PDU transfer time is set to the current
time, Tp = Tc.
The BSS may update the values of Bmax and R within the SGSN at any time by transmitting a new
Flow Control PDU containing the new Bmax and R values.
The variables B, B*, Tp and Tc are local to the SGSN and are not affected by the reception of a FlowControl-BVC or Flow Control-MS PDU.
The time between two consecutive updates has to be greater than C (see Figure 70)
A MS flow control process needs regular update FLOW-CONTROL-MS messages. Indeed, the
SGSN shall perform flow control on an individual MS using SGSN determined values of Bmax and R
unless it receives a FLOW-CONTROL-MS message from the BSS regarding that MS.
The SGSN shall continue to perform flow control for a particular MS using the Bmax and R values
received from the BSS for at least Th seconds after receiving a FLOW-CONTROL-MS message
from the BSS regarding that MS (see Figure 71)
When timer Th has expired or when the MS changes cells, the SGSN may reinitialise the SGSN
internal flow control variables for that MS and begin to use SGSN generated values for Bmax and R.
no new
Flow_Control_BVC
allowed
t0
t0 + C
FLOW_CONTROL_BVC
( BVC_Bucket_Size,
Bucket_Leak_Rate,
Bmax_default_MS
R_default_MS
[BVC_Measurement] )
C:
predefined value common to BSS and SGSN
Figure 70 Frequency of sending BVC_FLOW_CONTROL PDU
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
no new
Flow_Control_MS
allowed
t0 + C
t0
t0 + th
FLOW_CONTROL_MS
( MS_Bucket_Size,
Bucket_Leak_Rate)
th:
interval after FLOW_CONTROL_MS before SGSN may use SGSN generated Bmax and R
Figure 71 Frequency of sending MS_FLOW_CONTROL PDU
Flow control messages have the following parameters:

- FLOW-CONTROL-BVC
- BVC_Bucket_Size:
- BVC_Bucket_Leak_Rate:
- Bmax_Default_MS:
- R_Default_MS:
RLC
- BVC_Measurement
- FLOW-CONTROL-MS
- MS_Bucket_Size:
- MS_Bucket_Leak_Rate:
ED
MCD
Cell buffer maximum size (in MFS)

Cell measured throughput from RRM to RLC
Default value for MS buffer maximum size (in MFS)
Default value for MS measured throughput from RRM to
Average queuing delay for an LLC PDU destinated to the cell
(optional parameter, not implemented in Pilot and in B6.2 )
(not used in Pilot)
MS buffer maximum size (in MFS)
MS measured throughput from RRM to RLC
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.4.1.5.2
BSS principles
1) in Pilot
Only BVC_FLOW_CONTROL is implemented and NM-FLOW-CONTROL-BVC-req is sent only once
when the cell becomes operational.
NM-FLOW-CONTROL-BVC-cnf has to be monitored (timer T_BVC_Flow-Ack). If not received, NMFLOW-CONTROL-BVC-req has to be retransmitted (according to O&M parameter:
Nb_BVC_Flow_Retry, defining the number of allowed retries)
The parameters are valued in the following way:
MAX _ PDCH _ CELL

B _ max_ GPU Flow _ Dim _ safety _ Factor ,
MAX _ PDCH _ GPU
BVC _ Bucket _ Size max

MAX _ LLC _ PDU
BVC _ Bucket _ Leak _ Rate MAX _ PDCH _ CELL CS 2 _ RATE

min MAX _ PDCH _ CELL , 3)
B max_ default _ MS max
MAX _ PDCH _ CELL
BVC _ Bucket _ Size , MAX _ LLC _ PDU
R _ default _ MS max min MAX _ PDCH _ CELL , 3 CS 2 _ RATE , MAX _ LLC _ PDU
(Measurement_Delay is not implemented)

with:
- MAX_PDCH_CELL:
maximum number of PDCHs that can be allocated in the cell

(in pilot: MAX_PDCH_CELL = MAX_PDCH_GROUP)
- MAX_PDCH_GPU:
maximum number of PDCHs that can be managed by the GPU
- B_max_GPU:
GPU buffer maximum size
- Flow_Dim_safety_Factor:
O&M safety factor, used to tune the BVC bucket value
- MAX_LLC_PDU:
least
maximum length of a LLC PDU (SGSN has to be able to send at

one LLC PDU)
- CS2_RATE:
Coding Scheme 2 rate
(in Pilot, the maximum number of PDCHs which can be allocated to a MS is equal to 3)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2) in B6.2
a) BVC FLOW CONTROL
BVC_FLOW_CONTROL and MS_FLOW_CONTROL are implemented.
NM-FLOW-CONTROL-BVC-req is sent when the cell becomes operational for GPRS traffic and then
periodically according to T_Flow_Ctrl_Cell, as long as the cell is operational.
BVC _ Bucket _ Size
Flow _ Dim _ safety _ BVC Nb _ pdch _ cell 1 Max _ Rate _ PDCH T _ Flow _ Ctrl _ cell
Note: - BVC_Bucket_Size shall be greater than the maximum amount of data a cell may send
during a T_Flow_Ctrl_cell period. If it is not the case, the rate calculated during the period
may
not correspond to the maximum rate the cell can reach. Then it is recommended to set
Flow_Dim_safety_Factor to a value greater than 1 (e.g. 1.5)
- BVC_Bucket_Size shall never be null, even if Nb_pdch_cell = 0
- BVC_Bucket_Size shall be greater than Max_LLC_PDU_size
BVC _ Bucket _ Leak _ Rate
Data _ cell
T _ Flow _ Ctrl _ Cell
(the initial value of BVC_Bucket_Leak_Rate is 0)
B max_ default _ MS Flow _ Dim _ safety _ MS Max _ Rate _ PDCH T _ Flow _ Ctrl _ MS
(initial value is calculated as if this MS has one allocated PDCH, in the cell)
R _ default _ MS Max _ Rate _ PDCH

with:
- Nb_pdch_cell:
number of PDCHs allocated in the cell
- Max_Rate_PDCH:
maximum rate of one PDCH (calculated with CS2)
- Flow_Dim_safety_BVC:
O&M safety factor, used to tune the BVC bucket value
- MAX_LLC_PDU:
least
maximum length of a LLC PDU (SGSN has to be able to send at

one LLC PDU)
- Data_Cell:
MSs
number of bits transmitted from RRM (TRN) to RLC (TRN) by all

in the cell, since the previous FLOW_CONTROL_BVC message
related to this cell.
- T_Flow_Ctrl_cell:
sending period of NM-FLOW-CONTROL-CELL-req
- T_Flow_Ctrl_MS:
sending period of NM-FLOW-CONTROL-MS-req
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) MS FLOW CONTROL
NM-FLOW-CONTROL-MS-req is sent when the TBF is established (provided the last NM-FLOWCONTROL-MS has been sent since more than T-FLOW-CTRL-MS duration) and then periodically
according to T_Flow_Ctrl_MS, as long as the TBF is established.
n
Max _ Rate _ pdchi

T _ Flow _ Ctrl _ MS
Nb _ tbfi
i 1
MS _ Bucket _ Size Flow _ Dim _ safety _ MS
(Max_rate_pdchi/nb_tbfi represents the maximum bandwidth a MS may reach on pdchi)

(In a cell, the total sum of the buckets for the MSs can be greater than the bucket for this cell)
MS _ Bucket _ Leak _ Rate
Data _ MS
T _ Flow _ Ctrl _ MS
The initial value (value sent when the TBF is created for this MS) is:
n
Max _ rate _ pdchi

nb _ tbfi
i 1
MS _ Bucket _ Leak _ Rate
(estimation of the maximum rate a MS can reach, taking into account the number of granted PDCH
and of MSs per PDCH)
with:
- MAX_rate_pdchi:
maximum rate the MS can reach on PDCHi
- Nb_tbfi:
number of DL TBFs on PDCHi
- T_Flow_Ctrl_MS:
sending period of NM-FLOW-CONTROL-MS-req
- Data_MS:
MS,
number of bits transmitted from RRM (TRN) to RLC (TRN) by the

since the previous FLOW_CONTROL_MS message related to this
MS.
- Flow_Dim_safety_MS:
O&M safety factor, used to tune the MS bucket value
When NM-FLOW-CONTROL-BVC/MS-cnf is not received, no repetition is undertaken, at the next

T_Flow-Ctrl_BVC/MS expiry, computation will be processed upon 2 periods.
5.4.2 UL LLC PDU transfer

PDU received from RLC are sent to BSSGP with the cell location from which it was received, the
QoS profile reserved (not actual QoS profile) to transfer it on radio interface, the Routing Area Code,
the BVCI and the MS TLLI.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5
PRH Entity detailed description
PRH entity has the following functions:

- Packet System Information management
- Packet radio resource allocation
- PDCH resource control
- UL congestion control
5.5.1 Packet System Information management (B6.2 SMG29)

Packet System Information shall be broadcast to the mobiles in a cell in order to control their
behaviour whilst they are in packet idle mode or packet transfer mode and whilst attempting to
connect to the network.
RRM provides MAC with one of the following set of Packet System Information:
- either PSI13, if there is no MPDCH
- or PSI1 + PSI2 + PSI3, if there is a MPDCH
5.5.1.1 Broadcast of GPRS System Information on BCCH
5.5.1.1.1
GPRS support in the cell
MS is allowed to access the cell for GPRS data transfer if GPRS support is indicated on BCCH
(SI3/4 and SI13).
The MFS commands the scheduling of such information on BCCH through BSCGP interface (see
[3]).
(NTM-CELL-START/STOP-req)
5.5.1.1.2
PBCCH support in the cell
The presence of a PBCCH in the cell is indicated by a PBCCH description in the SI13 message
(refer to 12).
The MFS commands the scheduling of this information (PRH-CONF/DECONF-MASTER-req).
5.5.1.2 Broadcast of Packet System Information on PBCCH
(B6.2 SMG29 only)
When a cell is configured with a MPDCH, PSI 1, 2, 3 and 3bis, shall be broadcast on PBCCH. PSI 4
and 5 are not used in B6.2 SMG29 (no support of MS measurements reporting).
5.5.1.2.1
PSI organization
Below, O&M parameters are marked with
ED
MCD
*.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.1.1
Packet System Information Type 1
This message is sent to the MS in order to give information for :

Cell selection
Control of the PRACH
Description of the control channel(s)
Description of power control parameters
This message is sent on the PBCCH, and on every PDCH which carries PACCH in a cell which
supports a MPDCH.
Information
Element
Message type
Field
PAGE_MODE
PBCCH_CHANGE_
MARK
PSI_CHANGE_FIELD
PSI1_REPEAT_PERI
OD
PSI_COUNT_LR
PSI_COUNT_HR
MEASUREMENT_OR
DER
ED
MCD
Use
setting & rules
Message type
Normal paging or reorganization
PSI1 message type

Normal
Indicates
if
information
broadcast in other PSI messages
has changed
Indicates which PSI has changed
indicates the PSI1 repeat period
(see 5.5.1.2.2)
indicates the number of different

Packet
System
Information
message that are mapped onto
the PBCCH with a low repetition
rate.
Computed by RRM:
set to the number of PSI3
and PSI3 bis instances.
indicates the number of different

Packet
System
Information
message that are mapped onto
the PBCCH with a high repetition
rate. this value does not include
PSI1.
indicates whether, the MS shall
send measurements
(see 5.5.1.2.2)
* see [13]
Full set of PSI message =

PSI_COUNT_LR
+
PSI_COUNT_HR + 1
Computed by RRM:
set to the number of PSI2
instances (equal 2).
Full set of PSI message =
PSI_COUNT_LR
+
PSI_COUNT_HR + 1
Set to 0
(i.e. the MS is in control of
cell reselection and MS
shall
not
send
any
measurement
(= NC0 and EM0 in
GSM 05.08)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
GPRS
cell
options
Field
Network Mode Operation
* see 13
T3168
* see 13
T3192
timeout value of timer timer

T3168
timeout value of timer T3192
DRX_TIMER_MAX
maximum value of DRX_TIMER
ACCESS_BURST_
TYPE
CONTROL_ACK_
TYPE
8 or 11 bits access burst
PAN_DEC
PAN_INC
PAN_MAX
MCD
setting & rules
NMO
BS_CV_MAX
ED
Use
format of the Packet Control Ack

message:
- 4 bursts
- or RLC/MAC control block
round trip delay over radio
interface, in number of block
periods
value to be decremented from
MS N3102 counter when Packet
UL ACK/NACK is not received
before timer T3182
value to be incremented to MS
N3102 counter when Packet UL
ACK/NACK is received before
timer T3182
maximum value allowed for
counter N3102.
Cell reselection is done by MS
when N3102 0
* see 13
* see 13
* see 13
4 bursts
* see 13
* see 13
* see 13
* see 13
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
PRACH Control
parameters
Field
(see 5.5.1.2.2)
* see 13
PERSISTENCE_
LEVEL1
maximum number of
retransmissions allowed for
priority level 1
maximum number of
priority level 2
maximum number of
priority level 3
maximum number of
priority level 4
used for calculation of the
minimum number of slots
between 2 successive
Channel Request messages
number of slots to spread
transmission of the random
access
access persistence level for
priority level 1
PERSISTENCE_
LEVEL2

priority level 2
* see 13
PERSISTENCE_
LEVEL3

priority level 3
* see 13
PERSISTENCE_
LEVEL4

priority level 4
* see 13
BS_PCC_REL
indicates if the last PDCH

carrying PCCCH and PBCCH
will be released shortly
number of blocks allocated
to the PBCCH per 52 multiframe
to the PAGCH or PDTCH or
PACCH per 52 multi-frame
to the PRACH per 52 multiframe
on each MPDCH
MAX_RETRANS3
MAX_RETRANS4
TX_INT
BS_PBCCH_BLKS
BS_PAG_BLKS_RES
BS_PRACH_BLKS
ED
MCD
setting & rules
Access control class
ACC_CONTR_
CLASS
MAX_RETRANS1
MAX_RETRANS2
PCCH
organization
parameters
Use
* see 13
* see 13
* see 13
* see 13
* see 13
* see 13
see 5.5.1.2.2
see 5.5.1.2.2
see 5.5.1.2.2
see 5.5.1.2.2
see 5.5.1.2.2
* see 13
* see 13
* see 13
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Global
Power
Control
Parameters
Field
* see 13
power control parameter
T_AVG_W
signal strength filter period for

* see 13
power control in packet idle
mode
signal strength filter period for
* see 13
power control in packet transfer
mode
power reduction value used by
the BTS on PBCCH blocks,
set to 0 (power level of
relative to the output power
PBCCH is the same as on
used on BCCH
BCCH)
determines whether the DL
* see 13
measurements for UL power
control shall be made on BCCH
or PDCH
determines whether the MS shall * see 13
perform interference
measurements on other
channels
interfering signal strength filter
* see 13
constant for power control
indicates the PSI1 repeat period. set to 0 : the network does
not support the Packet
PSI Status message.
Pb
PC_MEAS_CHAN
INT_MEAS_
CHANNEL_LIST_
AVAIL
N_AVG_I
PSI_STATUS_I
ND
MCD
setting & rules
ALPHA
T_AVG_T
ED
Use
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.1.2
Two instances of this message are sent to the MS in order to give information of :
reference frequency lists
cell allocation
GPRS mobile allocations
PCCCH channel descriptions
Non GPRS cell options applicable to circuit switched access
cell identification
The first instance of the PSI2 defines the cell allocation. The second instance of the PSI2 contains
the description of the GPRS Mobile Allocation, the PCCCH channels, the cell identification and the
NON GPRS cell options.
First instance of PSI2
Information
Element
Message type
Field
Page Mode
PSI2 Change Mark
PSI2_INDEX
PSI2_COUNT
Cell
identification
Non GPRS cell
options
ED
MCD
Use
setting & rules
Message type
On-going page mode on PCCCH
Identifies a consistent set of
PSI2 messages
Index of the PSI2 fragmented
message
Number of PSI2 fragmented
messages
PSI2 message type

Normal
(see 5.5.1.2.2)
set to 0
set to 2
not used (included in 2nd
instance of PSI2)
not used (included in 2nd
instance of PSI2)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Reference
Frequency List
(RFL)
Field
RFL number
length of RFL
contents
RFL contents
Cell allocation
RFL_NUMBER
GPRS Mobile
Allocations
PCCCH
description
ED
MCD
Use
setting & rules
This IE is the representation of

the reference frequency lists
provided in an instance of the
PSI2 message.
An RFL number preceding each
RFL identifies the RFL.
identification of an RFL
set of radio frequency channels
defining a RFL
This IE is a representation of the
cell allocation defined for the
cell.
The set of radio frequency
channels contained in the
referenced RFLs in this IE
defines the cell allocation
identification of an RFL
the GPRS mobile allocations
provided in an instance of the
PSI2 message.
An MA_NUMBER preceding
each GPRS mobile allocation.
timeslots carrying PCCH (only
one in step1) in the cell and their
frequency configurations.
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
Not used (included in 2nd
instance of PSI2)
Not used (included in 2nd

instance of PSI2)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Second instance of PSI2 :

Information
Element
Message type
Field
Page Mode
PSI2 Change Mark
PSI2_INDEX
PSI2_COUNT
Cell
identification
Location Area
identification
RAC
Use
setting & rules
Message type
On-going page mode on PCCCH
Identifies a consistent set of
PSI2 messages
Index of the PSI2 fragmented
message
Number of PSI2 fragmented
messages
MCC + MNC + LAC
PSI2 message type

Normal
(see 5.5.1.2.2)
Routing Area Code
* (see 13)
* (see 13)
* (see 13)
Cell identity
Non GPRS cell

options
ATT
T3212
NECI
PWRC
DTX
Radio_link_timeout
BS_AG_BLKS_RES
CCCH_CONF
BS_PA_MFRMS
MAX_RETRANS
TX_INTEGER
EC
MS_TX_PWR_MAX_
CCCH
ED
MCD
allows/forbids the mobile to

apply
IMSI
attach
and
detach
procedures
Timeout value for periodic
location updating in decihours
allows/forbids new establishment
causes for phase 2 MS.
In cases where TCHs hop on
BCCH frequency, the power
level
measure
is
not
representative since no power
control is applied on BCCH. This
flag make the MS exclude the
measurement of the BCCH
carrier
indicates to the MS if it shall,
may, or shall not use DTX for
uplink transmission
number of SACCH blocks not
received after which the MS
shall consider the link as lost
number of blocks reserved for
access grant
physical channel configuration
for CCCH
number
of
51-multiframes
between transmission of paging
messages on a paging group
maximum
number
of
retransmission
of
channel
request
number of slots to spread
transmission of channel request
Emergency call allowed
Maximum Tx power level
set to 1
set to 2
* (see 13)
* (see 13)
(see 13)
* (see 13)
* (see 13)
* (see 13)
(T100)
* (see 13)
* (see 13)
* (see 13)
* (see 13)
* (see 13)
Acc_contr_class
10,
computed by RRM thanks
to BSCGP informations
* (see 13)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Reference
Frequency List
(RFL)
Cell allocation
Field
Not used (included in the

first instance of PSI2)
MA_NUMBER
GPRS Mobile
Allocation
HSN
RFL number list
option1:
MA_LENGTH
MA_BITMAP
option2:
ARFCN index list
ED
MCD
setting & rules

Not used (included in the
first instance of PSi2)
GPRS Mobile
Allocations
(provided if
hopping used
on PDCH group)
Use

the GPRS mobile allocation of
the PDCH group.
identification of a GPRS Mobile
Allocation
defines a set of radio frequency
channels and a Hopping
Sequence Number (HSN), which
may be allocated to a MS to
define its channel configuration
Hopping Sequence Number
list of RFL numbers
length of the following field
bitmap representing the radio
frequency channels belonging to
the GPRS Mobile Allocation
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
not used
list representing a set of radio

frequency channels to be
excluded in from the definition of
the GPRS Mobile Allocation.
The GPRS MA is defined as
consisting of the radio frequency
channels included in the
reference frequency lists or the
referenced cell allocation,
except those represented by
ARFCN index list
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
PCCCH
description
Field
TSC
case of nonhopping PCCCH:
ARFCN
TIMESLOT_ALLOC
ATION
case of hopping
PCCCH:
MA_NUMBER
MAIO
TIMESLOT_ALLOC
ATION
ED
MCD
Use
setting & rules

timeslots carrying PCCCH (only
one in B6.2 ) in the cell and their
frequency configurations.
training Sequence Code
(see 5.5.1.2.2)
Representation of the Absolute

Frequency Channel Number
TimeSlot assigned as PCCCH
(see 5.5.1.2.2)
identification of a GPRS Mobile

Allocation
Mobile Allocation Index Offset
TimeSlot assigned as PCCCH
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
(see 5.5.1.2.2)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.1.3
This message is sent to the MS in order to give information of :

BCCH allocation in the neighbour cells
Cell selection parameters for serving cell and non-serving cells
Up to 32 neigbour cells may be defined. The coding of the PSI3 instances shall be optimized in order
to reduce the number of PSI3 instances : by the way, it reduces the duration of the cell reselection
when there is a MPDCH in the target cell ; it also reduces the number of RLC data blocks that may
be lost by a MS when few instances of PSI3 have not been acquired in a first reading attempt.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Message type
Field
Use
setting & rules
Message type
PAGE_MODE
PSI3_CHANGE_M
ARK
PSI3_BIS_COUNT
Serving
cell
parameters
CELL_BAR_ACCESS2
EXC_ACC
GPRS_RXLEV_
ACCESS_MIN
GPRS_MS_TXPWR_
MAX_CCH
General
Cell
selection
parameters
HCS :
GPRS_PRIORITY_
CLASS
HCS :
GPRS_HCS_THR
GPRS_CELL_
RESELECT_
HYSTERESIS
C31_HYST
C32_QUAL
RANDOM_ACCESS_
RETRY
T_RESEL
RA_RESELECT_
HYSTERESIS
ED
MCD
Provides MS with the current

level of informations contained
in PSI3 and PSI3bis messages.
A new value indicates that the
MS shall reread the information
from the PSI3 and all PSI3bis
messages.
It indicates the PSI3 bis index
for the last (highest indexed)
individual PSI3 bis message.
status for cell reselection
PSI3 message type

Normal
(see 5.5.1.2.2)
according to the number

of PSI3bis messages
(see 5.5.1.2.2)
Flag to prevent MS without

exclusive access rights from
camping on the cell. Linked to
Solsa feature
minimum received level at the
MS required for access to the
system
maximum TX power level an MS
may use when accessing on a
PCCCH
HCS priority of the cell
set to 0 (no prevention)
HCS signal strength threshold
* See 13
additional hysteresis which

applies in Ready state for cells
in the same RA
determines whether the GPRS_
RESELECT_HYSTERESIS
shall be applied to the C31
criterion
indicates an exception rule for
GPRS_RESELECT_OFFSET
according to GSM TS 05.08.
indicates whether the MS is
allowed to try to access another
cell if available
If the MS has performed an
abnormal release with cell
reselection from this cell, the MS
is not allowed to reselect this cell
for T_RESEL seconds if another
cell is available.
indicates in both STANDBY and
READY state the additional
hysteresis which applies when
selecting a cell in a new RA
* See 13
* See 13
* See 13
* See 13
* See 13
* See 13
* See 13
* See 13
* See 13
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Neighbour cell
parameters
Field
START_
FREQUENCY
Cell selection
BSIC
params
(first adjacent
cell)
CELL_BAR_ACCESS2
EXC_ACC
SAME_RA_AS_
SERVING_CELL
GPRS_RXLEV_
ACCESS_MIN
GPRS_MS_TXPWR_
MAX_CCH
GPRS_TEMPORARY
_OFFSET
GPRS_PENALTY_
TIME
GPRS_RESELECT_
OFFSET
HCS params:
- GPRS_PRIORITY_
CLASS
- GPRS_HCS_THR
PSI1_REPEAT_PE
RIOD:
SI13_PBCCH_
LOCATION:
ED
MCD
Use
setting & rules
Defines the ARFCN of the

BCCH frequency of the first cell
in the list of neighbour cells.
Base Station Identity Code
* See 13

Flag to prevent MS without
camping on the cell. Linked to
Solsa feature
determines whether the neigbour
cell RA Code is the
same as serving cell RAC
system
PCCCH
negative offset to C32 used for
MS cell reselection process
set to normal
set to 0 (no prevention)
time during which

GPRS_TEMPORARY_OFFSET
is active
used by the MS to apply an
offset and an hysteresis to the
GPRS cell reselection criterion
PSI repeat period of high rate
PSI
either indicate the position of the
SI13 message or a PBCCH
position.
If not present, SI3 and SI4 in the
neighbour cell indicates if the
neighbour cell supports GPRS
* See 13
* See 13
* See 13
(**)
* See 13
(**)
* See 13
(**)
* See 13
(**)
* See 13
* See 13
(**)
* See 13
(**)
not used
not used
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Field
Use
NR_OF_REMAINI
NG_CELLS
NR_OF_REMAINING
_CELLS
Number of remaining neighbour

cells, that are defined in the
frequency group
(for each of them, the
parameters frequency_diff and
cell selection params will be
repeated)
number of bits to be used for
the frequency diff field in the
current frequency group
FREQ_DIFF_
LENGTH
next
cell
adjacent
FREQUENCY_DIFF
Cell
selection
params structure
(**):
setting & rules
specifies the difference in

ARFCN value to the previous
defined cell in the neighbour cell
params struct
(see above, the structure
description)
* according to
Start_Frequency
See 13
according to the frequency
span
between
the
2
consecutive cells
if one of these fields is omitted, its value is the same as for the preceding cell
first adjacent cell

second adjacent cell
third adjacent cell
START_FREQUENCY
Cell selection IE
NR_OF_REMAINING_CELLS
FREQ_DIF_LENGTH
FREQUENCY_DIFF
Cell selection IE
FREQUENCY_DIFF
ARFCN of the BCCH of the first cell
difference in ARFCN value to the first cell

difference in ARFCN value to the second
cell
Cell selection IE
Figure 72 Neighbour cell parameters structure
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.1.4
Packet System Information Type 3bis
Few instances of this message may be sent to the MS, in order to give information of the BCCH
allocation in the neighbour cells and cell selection parameters for non-serving cells.
Two coding of the PSI3 bis instances may be used according to the set of neigbour cell parameters.
Information
Element
Message type
Field
Use
setting & rules
Message type
PAGE_MODE
PSI3_CHANGE_M
ARK
PSI3_BIS_INDEX
PSI3_BIS_COUNT
Neighbour cell
parameters
Neighbour cell
parameters 2
Provides MS with the current

level of informations contained
in PSI3 and PSI3bis messages.
A new value indicates that the
MS shall reread the information
from the PSI3 and all PSI3bis
messages.
to distinguish individual PSI3 bis
messages
containing
information
about
different
neighbour cells.
It indicates the PSI3 bis index
for the last (highest indexed)
individual PSI3 bis message.
Neighbour
cell
parameters
structure 1
Neighbour
cell
parameters
structure 2
PSI3bis message type

Normal
(see 5.5.1.2.2)
(1)
(2)
Both neighbour cell parameters structure 1and 2 may be used. The second structure shall be used in
order to shorten the PSI3bis message when there cells share the same cell selection structure
parameters.
Neighbour cell parameters structure 1
Structure 1 has been defined in the PSI3 message. The same rules as for PSI3 shall apply.
Neighbour cell parameters structure 2
The Neighbour cell parameters structure 2 enables to shorten the neighbour cell description,
provided at least 2 cells, whose BCCH frequency can be described in the same ARFCN set, share
the same Neighbour parameter set structure.
One Neighbour cell parameters structure 2 can only contain 2 Neighbour parameter set structures.
The whole Neighbour cell parameters structure 2 is not repeated. Each Neighbour cell parameters
structure 2 may contain several START_FREQUENCYs if needed (ie the FREQUENCY_DIFF can
not be coded by 8 bits).
When several neighbour cell parameters set are present in a PSI3 bis message, an optionnal
neighbour cell parameter is omitted when its value is the same the last coded one.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Neighbour cell
parameters 2
Field
Use
setting & rules
Neighbour cell parameters 2 may be repeated if 2 Neighbour parameter set

structures are not enough
GENERATION
Reserved for future extension
Set to 00
The following structure may be repeated as many times as START_FREQUENCY parameter is needed.
Defines the ARFCN of the
BCCH frequency of the first cell
in the list of neighbour cells.
cell RA Code is the
* See 13
BCC
Base Station Colour Code
* See 13:
NR_OF_REMAINING
_CELLS
Number of remaining neighbour

cells, that are defined in the
frequency group
(for
each
of
them,
the
parameters frequency_diff and
cell selection params will be
repeated)
number of bits to be used for
the frequency diff field in the
current frequency group
START_
FREQUENCY
SAME_RA_AS_
SERVING_CELL
CELL_BAR_ACCE
SS2
FREQ_DIFF_
LENGTH
These 4 IEs may

be repeated as
many times as
neighbour cells
have the same
START
FREQUENCY
and the same
neighbour
parameters set
structure
ED
MCD
FREQUENCY_DIF
F
SAME_RA_AS_
SERVING_CELL
CELL_BAR_ACCE
SS2
specifies the difference in

ARFCN value to the previous
defined cell in the neighbour cell
params struct
cell RA Code is the
* See 13
set to normal
(see 5.5.1.2.2)
* See 13
set to normal
BCC
Base Station Colour Code
* See 13
CELL_PARAMS_P
OINTER
Reference to a Neighbour
parameter set structure
the
current
standard
allows
one
CELL
PARAMETER POINTER
for
a given
START
FREQUENCY, but several
START
FREQUENCYs
may have the same CELL
PARAMETER POINTER
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Cell
selection
params
Field
Network Colour Code
* See 13
EXC_ACC
ACC is used by the network to

prevent
mobiles
without
camping on the cell
system
PCCCH
Set to 0
(Solsa
feature
supported)
GPRS_MS_TXPWR_
MAX_CCH
HCS params:
- GPRS_PRIORITY_
CLASS
- GPRS_HCS_THR
SI13_PBCCH_
LOCATION:
SI13_LOCATION
PBCCH_LOCATION
PSI1_REPEAT_
PERIOD
GPRS_TEMPORARY
_OFFSET
GPRS_PENALTY_
TIME
GPRS_RESELECT_
OFFSET
MCD
setting & rules
NCC
GPRS_RXLEV_
ACCESS_MIN
ED
Use
* See 13
(**)
* See 13
(**)
* See 13
(**)
* See 13
(**)
either indicate the position of the

SI13 message or a PBCCH
position.
If not present, SI3 and SI4 in the
neighbour cell indicates if the
neighbour cell supports GPRS
indicates the logical channel
where the SI13 is broadcast
indicates the location of the
PBCCH on the BCCH carrier
indicates the PSI repeat period
not used
negative offset used for MS cell

reselection process
* See 13
(**)
* See 13
(**)
* See 13
(**)
time during which

is active
used by the MS to apply an
offset and an hysteresis to the
not used
not used
not used
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
not
5.5.1.2.2
Packet System Information handling
The following figure shows messages which deal with PSI parameters.
LM-Cell-Create-req
LM-Cell-Set-req
O&M
RRM
PSI handling
NTM-BSS-Traffic-Control-ind
NTM-Cell-Traffic-Control-ind
NTM-Cell-Start-cnf
NTM-Cell-State-cnf/ind
Celln
PRH-SYS-Define
MAC
Figure 73 PSI handling interface (with MPDCH)
5.5.1.2.2.1
Packet System Information Scheduling
PSI1, PSI2, PSI3 and PSI3bis are broadcast cyclically by MAC layer (see [5])
RRM gives the packet system information to MAC layer by using PRH-SYS-DEFINE primitive.
5.5.1.2.2.2
Static parameters
Most of PSI parameters are given, by O&M, at cell creation (LM-Cell-Create-req). They are marked
with * in the previous tables describing PSI
They can be modified by O&M command (LM-Cell-Set-req).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.2.3
Dynamic parameters
1) PSI1 specific parameters

- PBCCH-CHANGE-MARK
The PBCCH_CHANGE_MARK field is a 3 bit counter incremented by one, by RRM, each time
information has been changed in one or more of the broadcast PSI2-PSIn messages on PBCCH
(n2)
- PSI-CHANGE-FIELD
The PSI_CHANGE_FIELD is a 4 bit value reflecting which PSI message or group of instanciated
PSI message was most recently updated when the PBCCH_CHANGE_MARK was last incremented.
If more than one PSI message or group of instanciated PSI message were changed at the same
time, the PSI_CHANGE-FIELD indicates unspecified updates.
The values which are used are the following:
- Update of unspecified PSI message(s)
- PSI2 updated
- PSI3/PSI3bis updated
- ACC_CONTR_CLASS
ACC_CONTR_CLASS defines which access control classes are barred and if the emergency calls
are allowed (1 : not allowed/barred, 0 : allowed).
The value of this parameter takes into account the 2 following indications, sent by the BSC, which
have the same bit pattern:
- ACCESS_CONTROL_CLASS_CELL
Cell traffic parameter (received from the BSC either in NTM-CELL-TRAFFIC-CONTROL-ind
or in NTM-CELL-START-cnf).
This parameter takes into account administrative and operational indications
- ACCESS_CONTROL_CLASS_BSS
BSS traffic parameter (received from the BSC in NTM-BSS-TRAFFIC-CONTROL-ind).
This parameter takes into account administrative and operational indications.
ACC_CONTR_CLASS (PSI1) =
ACC_CONTR_CLASS_CELL OR ACC_CONTR_CLASS_BSS
(see also Figure 74)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- PERSISTENCE_LEVEL1/4
The Persistence_Level fields indicate the value of the access persistence level (Pi) for each radio
priority (1 to 4).
The Persistence_Level value broadcast in PSI1 takes into account
- Persistence_Level O&M parameter
- and Priority_Access_Threshold O&M parameter
in the way described in the table below.
Priority_Access
_Threshold
000
001
010
011
Persistence
_level1
16
Parameters broadcast on PSI1

Persistence Persistence Persistence
_level2
_level3
_level4
16
16
16
Persistence_
Level1 O&M
parameter
Persistence_
Level1 O&M
parameter
16
16
16
Persistence_
Level2 O&M
parameter
16
16
101
Persistence_
Level1 O&M
parameter
Persistence_
Level2 O&M
parameter
Persistence_
Level3 O&M
parameter
16
110
111
Persistence_
Level1 O&M
parameter
Persistence_
Level2 O&M
parameter
Persistence_
Level3 O&M
parameter
Persistence_
Level4 O&M
parameter
100
Comments
packet access
not allowed in
the cell
(whatever the
O&M
persistence
level value)
packet access
is allowed for
priority level 1
packet access
is allowed for
priority level 1
to 2
packet access
is allowed for
priority level 1
to 3
packet access
is allowed for
priority level 1
to 4
- BS-PCC-REL
This parameter is set when the master PDCH has been deallocated at BSC level.
When reading this indication, the MS has to read SI13 (i.e. to return on BCCH).
(see Figure 77 and Figure 78)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA

- PSI2_CHANGE_MARK
The purpose of the PSI2_CHANGE_MARK field is to identify a consistent set of the PSI2 messages.
It ranges from 0 to 3.
It is increased by 1, by RRM, each time a new consistent set of PSI2 message is broadcast.
- Reference frequency lists/ Cell Allocation / GPRS Mobile allocation list/ PCCCH description
The Cell Allocation shall be provided as required for the decoding of the GPRS Mobile Allocation and
for the support of GPRS MS which may access the network for circuit-switched services.
The cell allocation is provided by the BSC through the BSCGP interface : several encoding may be
used by the BSC according to the BCCH frequency band : bitmap_0, 1024_range, 512_range,
256_range, 128_range, variable bitmap formats. RRM is transparent to the chosen encoding.
The cell allocation construction shall not be included in more than one instance of the PSI2 : : both
the reference frequency list & the cell allocation structures will systematically be provided in the first
instance of the PSI2 messages whatever the size of the cell allocation.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
These fields are deduced from information received from the BSC, according to the following table:
PSI
message
BSCG
message
IE
Reference
Frequency List
field
RFL number
field
set to 1
cell allocation
Length
RFL contents
cell allocation
Content
cell radio
configuration
HSN
cell radio
configuration
cell radio
configuration
MA_Length
not used
received from BSCGP
ARFCN1/n
received from BSCGP
RFL number
GPRS
Mobile
Allocations
(present only if
hopping is used
on PDCH group)
MA_NUMBER
HSN
RFL number list
MA_LENGTH
MA_BITMAP
PCCCH
description
IE
length of RFL
contents
Cell Allocation
ARFCN
list
TSC
index
ARFCN
cell radio
configuration
cell radio
configuration
TSC
ARFCN
non-hopping PCCCH
MAIO
timeslot on which the

PCCCH
has
been
allocated
(TS which has been
sent in MARK
MASTER CHANNEL
message to the BSC)
hopping PCCCH
set to 1
hopping PCCCH
MA_NUMBER
MAIO
MCD
Length received from

BSCGP (4 to 16
octets) minus 3 octets.
list
of
frequencies
received from BSCGP.
Only 1 RFL content is
used.
set to 1. Only 1 RFL
content is referenced.
set to 1
not used
TIMESLOT_
ALLOCATION
ED
comments
cell radio
configuration
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA

- PSI3-CHANGE-MARK
The PSI3 change mark field is increased by 1, by RRM, each time information has been updated in
any of the PSI3 (or PSI3bis messages).
A new value indicates that the MS shall re-read the information from PSI3 and all PSI3bis messages
Range from 0 to 3
- CELL-BAR-ACCESS2
If CELL_BAR_ACCESS2 is set to Normal, a MS can perform an access procedure in the cell,
otherwise (CELL_BAR_ACCESS2 set to Barred), no MS can perform an access procedure. (see
1.3.4.8.2)
CELL_BAR_ACCESS2 is computed as shown on the following figure
O&M
O&M
O&M
1: automatic
barring
1: barred
CB
(cell)
O&M
Access_
control_
class (cell)
AUT_BAR
AND
OR
BSC
dynamic
actions
CBQ
(cell)
1: all classes
barred
NOT
AND
CB (BSS)
CBQ (BSS)
BSCGP interface
CB (cell)
Access_Control
Class_Cell
CBQ (cell)
Access_Control
Class_BSS
OR
MFS
AND
AND
OR
ACC_CONTR_CLASS
(PSI1)
CELL_BAR_ACCESS2
(PSI3)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Figure 74 ACC_CONTR_CLASS (PSI1) and CELL_BAR_ACCESS2 (PSI3) processing
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
CB and CBQ values on BSCGP interface are the following:
CB (O&M)
0
Initial conditions
AUT_BAR
all access_
control_class
(O&M)
barred
0
0
CBQ (O&M)
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
1
1
0
1
0
1
0
1
on BSCGP interface
CB
CBQ
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
0
1
0
1
0
1
0
0
0
1
0
1
0
1
0
0
CELL_BAR_ACCESS2 is set according to parameters received from the BSC, in the following way:
received
Parameters
CB (BSS)
from
CB (Cell)
the
BSC
CBQ (BSS)
0
0
1
0
0
1
1
0
0
1
1
0
1
1
ED
MCD
Cell_Bar_Access2
CBQ (Cell)
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
(normal)
1 (barred)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
0
1
0
1
- neighbour cell parameters

The serving cell has
- its own parameters
- and specific parameters for each adjacent cell:
- START-FREQUENCY:ARFCN of the BCCH of the first adjacent cell
- FREQUENCY_DIFF:
Difference in ARFCN value to the previous defined
neighbour
cell
- BSIC
- EXC_ACC
- SAME_RA_AS_SERVING_CELL
- GPRS_RXLEV_ACCESS_MIN
- GPRS_MS_TXPWR_MAX_CCH
- GPRS_TEMPORARY_OFFSET
- GPRS_PENALTY_TIME
- GPRS_RESELECT_OFFSET
- GPRS_PRIORITY_CLASS
- GPRS_HCS_THR
- PSI1_REPEAT_PERIOD
- SI13_PBCCH_LOCATION
The following parameters have to be computed by the MFS:
- CELL_BARR_ACCESS2
In the current release, the CELL_BAR_ACCESS2 parameter of any adjacent cell (whether
they belong or not to the same MFS) is always set to normal value.
- SI13_PBCCH_LOCATION
The MFS has to set this parameter according to the presence of a MPDCH and the actual
support of GPRS in the neighbour cell.
In the current release, the SI_13_PBCCH_LOCATION IE of any neigbour cell is omitted
(SI3 and SI4 in the neighbour cell indicates if the neighbour cell supports GPRS).
neigbour
- PSI3 / PSI3 bis instances coding
The PSI3 message is encoded according to the neigbour cell parameters structure 1.
The neigbour cell parameter structure 1 shall exclusively be used to encode all instances of the PSI3
bis message when the flag EN_PSI3_CODING2 is disabled (MFS internal parameter allowing to
revert to a simpler but not optimized format - that could be used as a fallback coding in case of ETSI
unstability regarding the other coding : neigbour cell parameters structure 2). When the flag
EN_PSI3_CODING2 is enabled (default behaviour), both neigbour cell parameters structure 1 and 2
defined in PSI3 bis message in [16] may be used to encode the 32 neigbour cells in the minimum
number of PSI3 bis instances. In particular, the second structure enables to encode more neigbour
cells when they share common parameters. However, the standard does not allow to write a
Structure 1 after a Structure 2 in the same radio block: in one radio block, the first type of Structure
shall be structure 1.
As an example, one instance of the PSI3 bis message may contain :
7 cells instead of 5 cells when coding 2 is used and the cells have the same parameters
and only one start frequency is used
2 cells instead of 1 cell when coding 2 is used and the cells share the same parameters but
2 start frequency need to be used
2 cells instead of 1 when coding 1 is used when the cell share different parameters
Practically, assuming for instance that 8 templates are used for neigbour cell parameters, the coding
2 may allow to encode 32 neigbour cells on 8 PSI3 bis instances instead of 16 ! That means that with
a BS_PBCCH_BLKS set to 2, the cell reselection duration is decreased by 1 second. With
BS_PBCCH_BLKS set to 3, the cell reselection duration is decreased by 750 ms.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
When EN_PSI3_CODING2 is enabled, the minimum following requirements are applied :

The main idea of the algorithm is to group the neighbour cells sharing the same
parameters. Two consecutive groups may share some parameters. In a such case, the
value of those parameters are not repeated.
The more likely parameters to be common in two different groups are:
< GPRS_RXLEV_ACCESS_MIN : bit (6) > and < GPRS_MS_TXPWR_MAX_CCH : bit (5)
>
Within a group, the difference of BCCH frequency between two consecutive cells must be
less than 256. This applied to both Structure 1 and Structure 2. This is not an issue for
GSM as the frequency is a number between 1 and 124. In DCS this could lead to the split
of group of cells as the frequency is a number between 512 and 885.
The idea is to add incrementally the cells and try to fill the PSI3 radio blocks one by one.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
STEP ONE
Sort the neighbour cells according to the following criteria
a) NCC
b) GPRS_RXLEV_ACCESS_MIN
c) GPRS_MS_TXPWR_MAX_CCH
d) GPRS_PRIORITY_CLASS
e) GPRS_HCS_THR
f) GPRS_TEMPORARY_OFFSET
g) GPRS_PENALTY_TIME
h) GPRS_RESELECT_OFFSET
i) GPRS_PRIORITY_CLASS
j) GPRS_HCS_THR
k) START FREQUENCY
After sorting, all cells sharing the same parameters will be contiguous.
The cell sharing some parameters will be close to each other. The sort order could be modified if we
find out that another criteria order gives a better collapsing result for the Structure 1 or 2.
STEP TWO
We take the first cell (A) and start a structure 1 or 2.
Just take care that the field NR_OF_REMAINING_CELLS must be updated once the group is
finished.
THIRD STEP
We get the next cell (B) in the sorted list.
If the START FREQUENCY (B) minus START FREQUENCY (A) is bigger than 256, we start a new
list and go back to the step two.
Otherwise we try to insert (B) after the previous cell (A).
Structure 2 should be used when the Neighbour cell parameters structure of cells are the same.
There are two cases: we coded the last cell already present in the PSI3bis with a Structure 1 or with a
Structure 2.
STRUCTURE 1
The new Neighbour cell parameters structure to insert may use the same Structure 1 or insert a
new Structure 2. Whatever his type is, this new Neighbour cell parameters structure contains only
the parameters which values are different to the one already present in the previous Neighbour
parameter set. If both Structure 1 or Structure 2 fit into the remaining space of the radio block,
then a look ahead is performed in order to compare the parameters of the new cell (the one which is
inserted) and the following ones which may be put in the same radio block. The shortest structure
type which fits in the remaining space of the radio block is then selected, and added in the radio
block.
If the new cell and the following ones have exactly the same parameters then Structure 2 should be
used; else Structure 1 shall be used.
If Structure 1 has been selected, the size of the added {FREQUENCY_DIFF, Cell selection params
structure} is more than 22 bits long (because at least one parameter is not the same); it may go up
to 54 bits. We try to add a {FREQUENCY_DIFF, Cell selection params structure} with the cell (B)
parameters but without coping the parameters having the same value in the cell (A).
If it fits in the 22 bytes of the radio block, we add the highest possible number of cells and go back to
step three.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
If Structure 2 has been selected, if the new cells have exactly the same parameters and, the size of
the added Neighbour cell parameters structure 2 is 47 bits long for one new cell, 63 bits long for 2
new cells (same START FREQUENCY), 76 bits long for 3 new cells...
Else if they have not exactly the same parameters and if Structure 2 has been selected it may go up
to 85 bits long for 2 new cells (same START FREQUENCY), 98 bits long for 3 new cells... see length
examples (69 bits long for 1 new cell should not happen since Structure 1 is then 54 bits long and
should be selected).
If it fits in the 22 bytes of the radio block, we add the highest possible number of cells and go back to
step three.
Otherwise we must start a new PSI3bis radio block. The cell (B) becomes the new first cell and we go
back to step two.
STRUCTURE 2
Since the last cell already present in the radio block is described in Structure type 2, the following
ones in the same radio block shall be only described in Structure type 2.
If the cell (B) has exactly the same parameter as the cell (A), the cell (B) can share the same
Neighbour parameter set. The size of the added structure for (B) is 13 bits. If this fits in the radio
block we add it and go back to step three.
If the added structure does not fit, we must start a new PSI3bis radio block. The cell (B) becomes the
new first cell and we go back to step two.
If the cell (B) has not exactly the same parameters as the cell (A), we must start a new Neighbour
parameter set and a new REMAINING_CELLS list. This new Neighbour parameter set contains
only the parameters which values are different from the one already present in the previous
Neighbour parameter set.
If it fits in the current radio bloc we add it and go to step three.
Otherwise we must start a new PSI3bis radio bloc. The cell (B) becomes the new first cell and we go
back to step two.
END OF THE ALGORITHM
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
We keep going until all cells parameters have been written in the PSI3bis radio block.
Examples
Example 1
Assume that we have four sorted neighbour cells A, B, C, D with exactly the same parameters and
we want to put them in a PSI3bis with a Structure 2.
A first cell (A) will create the new group.
The cell (B) will be added to the list as it has the same parameters as the previous one (A).
The cell (C) will be added to the list as it has the same parameters as the previous one (B) and by
transitivity the same parameters as the starting cell (A).
The cell (D) will be added to the list as it has the same parameters as the previous one (C) and by
transitivity the same parameters as the starting cell (A).
Example 2
Assume that we have five sorted neighbour cells A1, A2, A3, B, C1, C2.
The cells A1,A2,A3 have exactly the same parameters.
The cell B has a complete different set of parameters.
The cells C1,C2 have exactly the same parameters.
The cells A1,A2,A3 will be in the same Structure 2.
B would start a complete new Neighbour parameter set if we use a Structure 2. But if we look
ahead from the cell B, we could notice that C1 does not share any parameters with B. It may be
therefore interesting to use for B a Structure 1 instead of a Structure 2 with only one entry. If
Structure 1 is selected, a new radio block has to be started because the CSN1 coding does not allow
to write a Structure 1 after a Structure 2 in the same radio block.
C1 does not share any parameter with B but if we look ahead we can notice that it shares it
parameters with the next cell C2. So we use a Structure 2 with a new Neighbour parameter set.
5.5.1.2.3
PBCCH activation procedure
The activation of a PBCCH, in a cell can be triggered by the following events:

a) at cell activation, when the cell supports a MPDCH and with NMO II:
ED
MCD
(1):
RRM first requests to the BSC the allocation of a PDCH to support the master
channel. After the successful allocation of the first PDCH, the primitive PRH-SYSDEFINE is sent as soon as the PDCH is activated at RLC/MAC level.
(2):
At PRH-SYS-DEFINE acknowledgement, a request is sent to the BSC to allocate a

master PDCH.
(3):
The location of the master PDCH is broadcast on SI13, then the MSs performs within
30 seconds a complete acquisition of PBCCH messages.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
BSC
RRM
MAC
START GPRS
START GPRS Ack
SI13
broadcast
PDCH(s)
allocation and
activation (1)
PRH-SYS-DEFINE-req
(PSI1/2/3/3bis)
SI3/4:
GPRS
supported
PRH-SYS-DEFINE-cnf
MARK MASTER CHANNEL
(3)
MARK MASTER CHANNEL Ack
PBCCH
location
broadcast
on SI13
PSI
broadcast
PSI1 on
PACCH
Figure 75 MPDCH activation (at cell activation, BSCGP supported)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) on NMO modification ( II I or III), when the cell supports a MPDCH, or on O&M

command (modification of MIN_MPDCH: 0 1)
(1):
if no PDCH is already established, RRM first requests to the BSC the allocation of a
PDCH to support the master channel. After the successful allocation of the first
PDCH, the primitive PRH-SYS-DEFINE is sent as soon as the PDCH is activated at
RLC/MAC level, in order to broadcast PSI messages on PBCCH. In case at least one
PDCH was already allocated at the O&M configuration change, one of the allocated
PDCHs is configured as a MPDCH and the same scenario is invoked.
(2):
At PRH-SYS-DEFINE acknowledgement, a request is sent to the BSC to allocate the

master PDCH
BSC
RRM
MAC
SI13
broadcast
PSI13 on
PACCH
SI3/4:
GPRS
(1)
supported
MARK MASTER CHANNEL
PRH-SYS-DEFINE-req
(PSI1/2/3/3bis)
PRH-SYS-DEFINE-cnf (2)
MARK MASTER CHANNEL Ack
PSI
broadcast
PBCCH
location
broadcast
on SI13
PSI1 on
PACCH
Figure 76 MPDCH activation (at NMO modification)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.2.4
PBCCH deactivation procedure
The deactivation of a PBCCH, in a cell can be triggered by the following events:

a) when GPRS traffic is stopped
BSC
RRM
MAC
PBCCH
location
broadcast
on SI13
PSI
broadcast
UNMARK MASTER CHANNEL

Ack
SI13
broadcast
(no MPDCH)
PSI1 on
PACCH
BSS_PCC_REL
set in PSI1
PRH-SYS-DEFINE-req (PSI1)
PRH-SYS-DEFINE-cnf
(1)
STOP GPRS
STOP GPRS Ack
SI13
broadcast
stopped
T_MPDCH_Deact
expiry
PRH-SYS-DEFINE-req
PRH-SYS-DEFINE-cnf
PSI broadcast
is stopped
SI3/4;
GPRS not
supported
Figure 77 MPDCH deactivation (at cell deactivation)

(1):
The MS will receive a PSI1 message indicating that PBCCH is being deactivated in the cell
(BSS_PCC-REL set) and will attempt to receive the SI13 message on BCCH. The SI13
message will be received with no PBCCH description and will perform a complete
acquisition
of BCCH messages.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
b) on NMO modification ( I or III II), when the cell supports a MPDCH or on O&M command
(modification of MIN_MPDCH: 1 0):
BSC
RRM
MAC
PBCCH
location
broadcast
on SI13
PSI
broadcast

Ack
SI13
broadcast
(no MPDCH)
PSI1 on
PACCH
BSS_PCC_REL
set in PSI1
PRH-SYS-DEFINE-req (PSI1)
PRH-SYS-DEFINE-cnf
(1)
T_MPDCH_Deact
PRH-SYS-DEFINE-req
(PSI13)
(2)
PSI13 broadcast
on PACCH
Figure 78 MPDCH deactivation (at NMO modification)

(1):
ED
MCD
The MS will receive a PSI1 message indicating that PBCCH is being deactivated in the cell
and will attempt to receive the SI13 message on BCCH. The SI13 message will be received
with no PBCCH description and will perform a complete acquisition of BCCH messages.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(2):
PSI broadcast is stopped on PBCCH, PSI13 is broadcast on PACCH
5.5.1.3 Broadcast of Packet System Information on PACCH

PSI broadcast on PACCHs is controlled, at MAC layer level, by the O&M parameter T_PSI_PACCH
(scheduling period of PSI1 or PSI13 on PACCH).
This broadcast avoids to MS which are involved in a Packet transfer, to read BCCH.
5.5.1.3.1
When there is no master PDCH, this message is broadcast by the network on the PACCH. The
message provides the mobile station with GPRS cell specific access-related information. The
information in this message is the same as provided in the SI13 message on BCCH, see 12.
When this message is broadcast, MSs involved in a data transfer have not to read SI13 on BCCH.
5.5.1.3.1.1
PSI13 description
Information
Element
Message type
Page Mode
Field
Use
setting & rules
Message type
On-going page mode on
PCCCH
Status of BCCH information
BCCH_CHANGE_
MARK
SI_CHANGE_FI
ELD
Binary
representation
of
which
information
was
changed
SI13_CHANGE_
MARK
Status of SI 13
ED
MCD
PSI13 message type

Normal
The value of this field shall
be
changed
when
information
content
is
changed on BCCH (except
change in SI13), received
from BSCGP
The value of this field
indicates which SI among
type 1, 2, 3, 4 has changed
at the last
BCCH_CHANGE_MARK
indication, received from
BSCGP
The value of this field shall
be changed when the GPRS
Mobile Allocation is
changed, received from
BSCGP
(only in case of hopping
PDCH group)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
Field
GPRS
Mobile
Allocation
HSN
RFL number list
option1:
MA_LENGTH
MA_BITMAP
option2:
ARFCN index list
RAC
GPRS
options
ED
MCD
cell
Use
setting & rules
representation of the GPRS

MA. It is identified by
MA_NUMBER = 14 when
referenced from a packet
assignment message.
This IE refers to the cell
allocation defined for the cell
in SI1
Hopping Sequence Number
Set of reference frequency
list
(see 5.5.1.3.1.2)
Not used
(see 5.5.1.3.1.2)
length of the following field

bitmap representing the radio
frequency channels belonging
to the GPRS Mobile
Allocation
(see 5.5.1.3.1.2)
not used
list representing a set of radio
frequency channels to be
excluded in from the
definition of the GPRS Mobile
Allocation.
Routeing Area Code
* (see 13)
SPGC_CCCH_SUP
Support of
SPLIT_PG_CYCLE on CCCH
Set to 0 since
SPLIT_PG_CYCLE on
CCCH is not supported
PRIORITY_ACCESS_
THR
Defines GPRS access policy
NETWORK_CONTROL_
ORDER
Type of roaming policy
NMO
Network Mode of Operation
* (see 13)
* (see 13)
* (see 13)
T3168
Timer on MS side
T3192
Timer on MS side
DRX_TIMER_MAX
Control of MS DRX
ACCESS_BURST_
TYPE
CONTROL_ACK_
TYPE
8 bits or 11 bits access burst
* (see 13)
* (see 13)
* (see 13)
* (see 13)
* (see 13)
BS_CV_MAX
format of the MS PACKET

CONTROL
ACKNOWLEDGMENT
RLC parameter
PAN_DEC
RLC parameter
PAN_INC
RLC parameter
PAN_MAX
RLC parameter
* (see 13)
* (see 13)
* (see 13)
* (see 13)
Extension Bits
indicates future extension
Set to Low (no extension).
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Information
Element
GPRS
Power
Control
parameters
Field
Control of MS output power

control
* (see 13)
T_AVG_W

control
control
Type of channel for power
control
downlink
measurements
control
* (see 13)
PC_MEAS_CHAN
N_AVG_I
MCD
setting & rules
ALPHA
T_AVG_T
ED
Use
* (see 13)
* (see 13)
* (see 13)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.3.1.2
Information handling
O&M
LM-Cell-Create-req
LM-Cell-Set-req
BSC
NTM-BSS-TRAFFIC-CONTROL-ind
NTM-CELL-TRAFFIC-CONTROL-ind
NTM-CELL-START-cnf
RRM
PSI handling
PRH-SYS-DEFINE-req
MAC
Figure 79 PSI handling interface (without a MPDCH)
1) Static parameters
Most of PSI13 parameters are given, by O&M, at cell creation (LM-Cell-Create-req). They are
marked with * in the previous tables describing PSI13.
They can be modified by O&M command (LM-Cell-Set-req).
2) Dynamic parameters
- BCCH_CHANGE_MARK
BCCH_CHANGE_MARK is increased by 1 each time there is a change in the System Information
content. It is coded on 3 bits. It shall be incremented by the BSC before SYSTEM INFORMATION
reconfiguration due to BCCH info change and shall not be incremented when SI13 only is modified.
RACH parameters, which are broadcast in SI1/SI2/SI3/SI4, can be modified for the whole BSS (i.e.
the BCCH_CHANGE_MARK parameter of all the cells has to be incremented). So in order to avoid
BSCGP interface overload in this case, the following mechanism is used:
2 parameters are handled:
- BSS_CHANGE_MARK parameter which is incremented when RACH parameters are modified on a
BSS basis.
- CELL_CHANGE_MARK parameter which is incremented when SI is modified for one cell
A modification of either BSS_CHANGE_MARK or CELL_CHANGE_MARK is notified by the BSC to
the MFS.
BCCH_CHANGE_MARK is obtained both in the BSC and in the MFS with the following process:
BCCH_CHANGE_MARK = (CELL_CHANGE_MARK + BSS_CHANGE_MARK) (modulo 8)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- SI_CHANGE_FIELD
SI_CHANGE_FIELD value indicates which SI among type 1, 2, 3, 4, 7, 8 (, 9), 15 has changed at the
last BCCH_CHANGE_MARK indication,.
The following values are used:
- Update of unspecified SI message or SI messages: this is used in case of update of
several different SI types
- Update of SI1 message
- Update of SI2, SI2bis or SI2ter message
- Update of SI3, SI4 message
When these parameters are modified by the BSC, these parameters are provided to the MFS
through BSCGP interface, in NTM-TRAFFIC-CONTROL-ind or in CELL STATE CHANGE-ind.
When the BCCH change mark is changed following a BSC overload procedure, the
SI_CHANGE_FIELD is not changed : the MS will read the same SI message than the one(s)
changed at previous change of the BCCH_CHANGE_MARK ; this is valid as the RACH Control
Parameters are located in all SI sent on BCCH (i.e. SI1, SI2, SI3 and SI4).
When the cell is started, these parameters are given at the MFS by NTM-CELL-START-cnf.
- SI13_CHANGE_MARK
SI13_CHANGE_MARK is sent by the BSC when it is modified (i.e. on GPRS Mobile Allocation
modification)
- GPRS Mobile Allocation
The different parameters of this IE ( HSN, MA_LENGTH, MA_BITMAP) are deduced from
information which is transmitted by the BSC (see 5.5.1.2.2.3 )
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.3.1.3
SI13/PSI13 synchronisation
BCCH_CHANGE_MARK is sent both on BCCH (SI13) and on PACCH (PSI13).

As the BCCH_CHANGE_MARK modification has to be notified to different network elements, the
purpose of this paragraph is to study consequences of eventual desynchronisations.
MS
BTS
BSC
BCCH_CHANGE_
MARK
modification
SI13 (BCCH)
desynchronisation
MFS
TRAFFIC
CONTROL
PSI13 (PACCH)
Figure 80 SI13/PSI13 synchronisation

a) MS in packet idle mode
The MS is only listening to BCCH, so an eventual desynchronisation between SI13 and PSI13 has no
consequence.
b) MS in packet transfer mode
The MS is listening to PACCH.
(1):
PSI13 is received with a modified BCCH_CHANGE_MARK value.
(2):
The MS is waiting for PSI messages on PACCH during 10s.

But the MS will not received the required messages (according to SI_CHANGE_FIELD), on
PACCH, within the 10s
(3):
The MS attempts to receive required messages each time the message is scheduled on
BCCH.
We assume that the desynchronisation between SI13 and PSI13 will be smaller than 10s.
(i.e. when the MS will read BCCH, the information will be consistent with PSI13 information)
BCCH
PACCH
PSI13
(1)
<--------
10s
(2)
-------->
<---- (3) ----------
Figure 81 SI13/PSI13 synchronisation (MS in Packet transfer mode)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
c) MS in transition from Packet idle mode to Packet transfer mode

The MS is listening to BCCH.
case 1:
(1):
SI13 is received with a modified BCCH_CHANGE_MARK value.
(2):
Since the MS is in packet idle mode, an attempt to receive the required messages is made
each time the message is scheduled on BCCH.
(3):
The MS is now in Packet transfer mode, the SI update phase goes on.
(4):
During this update phase a non updated PSI13 may be received .

In this case, the first acquisition is aborted and a new acquisition is initialized
(5):
An updated PSI13 message is received
(6):
After a 10s period, attempts to receive the required messages are performed each time the
message is scheduled on BCCH.
BCCH
idle
mode
packet
transfer
mode
SI13
(1) (2)
(3)
PACCH
PSI13
(4)
PSI13
(5)
<------ 10s -------->
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(6)
case 2:
(1):
SI13 is received with a modified BCCH_CHANGE_MARK value.
(2):
Since the MS is in packet idle mode, an attempt to receive the required messages is made
each time the message is scheduled on BCCH.
(3):
The MS is now in Packet transfer mode, the SI update phase is finished.
(4):
A non updated PSI13 is received .
(5):
(6):
An updated PSI13 is received
(7):
BCCH
SI13
(1) (2)
PACCH
(3)
PSI13
(4)
(5)
PSI13
(6)
(7)
d) MS in transition between Packet transfer mode and Packet idle mode

The MS is listening to PACCH.
(1):
PSI13 is received with a modified BCCH_CHANGE_MARK value.

A 10s timer is activated.
(2):
Before expiry of the 10s period, the MS returns in packet idle mode
An attempt to receive the required messages is made each time the message is scheduled
BCCH.
SI information has not yet been updated.
on
(3):
An updated SI13 message is received and a new SI update is intiated.

BCCH
(2)
SI13
(3)
PACCH
PSI13
(1)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.1.3.2
ED
MCD
When there is a MPDCH, this message is periodically broadcast on the PACCH.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.2 Packet radio resources management

Uplink or downlink packet radio resources are allocated to packet connections to support an uplink or
Downlink data transfer respectively requested by MS or SGSN.
This concerns either the reservation of one radio block only (e.g. one uplink block requested by MS
to send a PACKET RESOURCE REQUEST in a 2 phase access) or the reservation of multiple
blocks for an UL or DL TBF.
This also concerns the reservation of timing advance index to allow MS to continuously update its
timing advance during the DL or UL transfer, and the reservation of USF for UL transfer.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.2.1 Packet radio resources allocation
5.5.2.1.1
Packet radio resources
TFI
Each TBF is assigned a TFI. The TFI is unique in each direction, among a PDCH group.
PDTCH / PACCH
A DL or UL packet connection needs to be granted PDTCH/PACCH radio blocks to transfer the data
and the related signalling. These radio blocks may be supported by a Master PDCH or non Master
PDCHs.
USF
An UL TBF needs to be granted one USF value per allocated PDCH.
Any PDCH (whether it is or not a MPDCH) owns 6 USF available for traffic, one value being
reserved for uplink signalling when there is no UL TBF established, and one other value (USF =
FREE, valued to 111) being reserved for PRACH blocks. Any PDCH may consequently be
immediatly configured as a MPDCH if required by O&M configuration.
Note : the value reserved for uplink signalling is defined by RRM (PRH) and provided to MAC and
physical layer at PDCH establishment.
TAI
An DL or UL TBF needs to be granted one Timing Advance Index to allow MS to continuously update
its timing advance during data transfer. Refer to 9 for description of that procedure.
A PDCH (Master or not) owns 16 TAI values.
Note : The PACCH slot of a TBF is supported by the PDCH on which the TAI is allocated. Through
TAI slot assignment the MS is able to know the PACCH slot. In case of concurrent TBF the MS may
be allocated PACCH slots for DL and UL TBF located on different PDCH (in which case the MS is
assigned 2 TAI) depending on its multislot capabilities.
5.5.2.1.2
Different needs of packet radio resources allocation
Following types of requests may be served :

Allocation of 1 UL radio block without TAI nor USF : the allocated radio block is either used by the
MS to send a Measurement Report or a Packet Cell Change Failure (not in B6.2 ) or to send a
PACKET RESOURCE REQUEST during a 2 phase access on CCCH or PCCCH.
Allocation of multiple UL radio blocks with a TAI and USF(s) : to serve an UL 1 phase access on
CCCH or PCCCH or an UL access performed during a DL transfer or to serve a PACKET
RESOURCE REQUEST received during a 2 phase access on CCCH or PCCCH.
Allocation of multiple DL radio blocks with a TAI to serve a DL transfer.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.2.1.3
Interpretation of the MS multislot capability
RRM (PRH) takes into account the mobile class to determine the multislot configuration which can
be used by the mobile. See GSM 5.02 annexe B for multislot class definition.
Multi-slot
class
T
y
p
e
R T
x x
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
1
2
2
3
2
3
3
4
3
4
4
4
3
4
5
6
17
18
19 to 29
like 10
1
1
2
1
2
2
3
1
2
2
3
4
3
4
5
6
S
u
m
2
3
3
4
4
4
4
5
5
5
5
5
T T T Supported GPRS packet connection configurations

t r r See note 1, 2 & 3
b a b
NA
NA
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
7 7
NA
1 1 0
8 8
NA
0 0 0
x x
NA
NA
NA
4
3
3
3
3
3
3
2
2
2
2
2
3
3
3
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Symmetric
configuration
1+1
1+1
1+1
1+1
1+1, (2+2)C
1+1, (2+2)C
1+1, (2+2)C
1+1
1+1, (2+2)C
1+1, (2+2)C
1+1, (2+2)C
1+1, (2+2)C
1+1, (n+n)S5 : n <= 3
1+1, (n+n)S5 : n <= 4
1+1, (n+n)S5 : n <= 5
1+1, (n+n)S5 : n <= 5
(n+n) S6 : n <= 6
1+1, (n+n)S5 : n <= 5
(n+n) S7 : n <= 7
1+1, (n+n)S5 : n <= 5
(n+n) S8 : n <= 8
1+1, (2+2)C
Asymmetric configuration
No
(2+1)C
(2+1)C
(2+1)C, (3+1)C
(2+1)C
(2+1)C, (3+1)C
(2+1)C, (3+1)C
(2+1)C/1H, (3+1)C/1H, (4+1)C
(2+1)C/1H, (3+1)C/1H, (3+2)C
(2+1)C/1H, (3+1)C/1H, (3+2)C,
(2+1)C/1H, (3+1)C/1H, (3+2)C,
(2+1)C/1H, (3+1)C/1H, (3+2)C,
(n+m)S5 : n <= 3, 0 < m < n
(n+m)S5 : n <= 4, 0 < m < n
(n+m)S5 : n <= 5, 0 < m < n
(n+m)S5 : n <= 5, 0 < m < n
(n+m)S6 : n <= 6, 0 < m < n
(n+m)S5 : n <= 5, 0 < m < n
(n+m)S7 : n <= 7, 0 < m < n
(n+m)S5 : n <= 5, 0 < m < n
(n+m)S8 : n <= 8, 0 < m < n
(2+1)C/1H, (3+1)C/1H, (3+2)C,
(4+1)C
(4+1)C
(4+1)C
(4+1)C
Note 1 : The first mention in parenthesis corresponds to the MS Receive capability,

the second to the Transmit capability.
The following letters correspond to the Timeslot arrangement, see note 2.
Note 2 : The timeslot arrangements are the following
C : configurations with Consecutive TS
1H : configurations with one hole after first Rx TS :
1 TS + 1 unavailable TS + remaining consecutive TSs
Sx : configurations with any possible arrangement of n TS within the mentioned span x
Example : (3+1)C means 3 Rx + 1 Tx with consecutive TSs, (4+4)S5 means 4 Rx + 4 Tx
with any possible time slot arrangement spread over a 5 TS window starting at DL slot 0.
Note 3:
ED
MCD
In above tables, only bold configurations are supported. Italic underlined configurations are
not supported:
- type 1 MS configurations with hole are not supported
- type 2 MS configurations are limited to 5+5 timeslots. Configurations with hole are not
supported.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Mobile Station constraints :

MS type :
Type 1 are simplex MS, i.e. without duplexer : they are not able to transmit and receive at
the same time
Type 2 are duplex MS, i.e. with duplexer : they are able to transmit and receive at the same
time
Rx :
Maximum number of receive timeslots that the MS can use per TDMA frame. The receive
TS shall be allocated within window of size Rx, but they need not be contiguous. For
SIMPLEX MS, no transmit TS shall occur between receive TS within a TDMA frame.
This does not take into account measurement window (Mx).
Tx:
Maximum number of transmit timeslots that the MS can use per TDMA frame. The transmit
TS shall be allocated within window of size Tx, but they need not be contiguous. For
SIMPLEX MS, no receive TS shall occur between transmit TS within a TDMA frame.
SUM:
Maximum number of transmit and receive timeslot (without Mx) per TDMA frame
Meaning of Ttb, Tra et Trb changes regarding MS types.

For SIMPLEX MS (type 1) :
Ttb:
Minimum time (in timeslot) necessary between Rx and Tx windows
Tra:
Minimum time between the last Tx window and the first Rx window of next
TDMA in order to be able to open a measurement window.
Trb:
same as Tra without opening a measurement window.
For DUPLEX MS (type 2),
Ttb :
frames.
Tra:
frames
Trb:
Minimum time necessary between 2 Tx windows belonging to different

Minimum time necessary between 2 Rx windows belonging to different
in order to be able to open a measurement window.
same as Tra without opening a measurement window.
For SIMPLEX MS, Rx or Tx window shall not be spread over 2 different TDMA frames to take into
account frequency hopping that may provoke frequency change and to ensure that transmit TS do
not occur between receive TS within a TDMA frame (and reverse). The following configuration is for
instance forbidden (Rx on slots 0 and 7) : Trb shall necessarily be taken into account between 2
consecutive TDMA frames.
0
DL
Mx
Rx
Ttb
UL
7
Rx
Tra
Tx
7
Tx
0
A MS of a certain class is able to support any combination of multislot which fulfils the maximum
constraints of that class.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Within a same TDMA frame, all allocated timeslots of a same multislot configuration use the
same frequency (or frequency hopping sequence) and same training sequence code.
GPRS service constraints :
Although PACCH/D of DL or UL TBF could have been dynamically allocated on the block basis on
any allocated PDCH(s) by (MAC) layer, a PACCH/D slot is defined in B6.2 by (RRM) carrying all
signalling blocks. This allows to simplify (MAC) layer which does not care about MS capabilities (Tra,
Ttb).
Because of previous simplification, there is always a bi-directional channel for any TBF to support
PACCH. Configurations without Rx timeslot or without Tx timeslot are therefore forbidden. Note that
each PACCH of concurrent DL and UL TBF may be supported by different slots, depending on MS
capabilities
An uplink transfer with dynamic allocation (with USF granularity = 1) requires symmetric
capabilities. That means that simplex MS in dynamic allocation mode may only be granted a
configuration of class 1 (1 Rx + 1 Tx) or class 5 (2 Rx + 2 TX), i.e. a maximum uplink throughput
corresponding to 2 full PDCH (up to 26 kbits/s in B6.2 ).
A downlink transfer does not require symmetric capabilities : symmetric (monoslot connection)
and asymmetric (multislot connection) configurations are supported. One slot is used on uplink path
to vehicle the PACCH/U of the DL TBF
Simultaneous uplink and downlink transfer do not require symmetric capabilities ; symmetric and
asymmetric configurations are supported.
Whilst in transfer state an MS shall continuously monitor all BCCH carriers of neighbor and
serving cell. In every TDMA frame a receive signal level measurement sample shall be taken on at
least one of the BCCH carriers, one after the other (see GSM 05.08). If a MS performing a downlink
packet transfer with dynamic allocation is not able to perform receive signal level measurements
within the TDMA frame according to its multislot class, the MS shall perform the measurements
during the block period where the downlink acknowledge is sent. During this block period, the MS
shall use the timeslots after the PDCH carrying PACCH : it is then network responsibility to provide
the necessary acknowledgement block periods to ensure that the MS will perform the required
number of measurements. As the acknowledgement policy (in RLC layer) does not take that into
account in B6.2 , RRM (PRH) will systematically schedule a Measurement window per TDMA frame,
which explains why classes upper to 19 will behave as class 10.
DL RLC data blocks carrying a polling request shall be sent over the PACCH slot (RLC
requirement).
Asymmetric configurations own more downlink timeslots than uplink ones since they are relevant
only for downlink transfer. Thats why classes 3, 7 and 12 will respectively behave like classes 2, 6
and 11 with dynamic allocation.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Allowed sequencing :
All allowed configurations are illustrated below. Note that Mx slot location may be wherever within
Tra timespan. Configurations with holes are not supported.
Note : Configurations obtained by shifting the following illustrated combinations over the TDMA
frame are allowed if they obey previous rules.
Dark underlined timeslot represents the PACCH location.
Simplex Configuration (1+1) : 1 Rx + 1 Tx
The Tx and Rx slots are necessarily separated from 2 timeslots.
0
DL
Mx
Rx
Ttb
Tra
UL
Tx
0
The PACCH is always on the same slot whether it is an :

- 1 UL slot TBF
- a 1 UL slot TBF concurrent with a 1 DL slot TBF
- 1 DL slot TBF
Simplex Configuration (2+2)C : 2 Rx + 2 Tx
The only possibility is to keep both Rx timeslots contiguous.
Indeed 1 minimum timeslot is necessary between Rx and Tx windows.
DL
Rx
Rx
Mx
Ttb
UL
Tra
Tx
Tx
In case of 2 UL slots TBF, the PACCH is located on one of the 2 slots.

In case of 1 UL slot TBF concurrent with 1 DL slot TBF, there is a PACCH on each slot.
In case of 1 UL slot TBF concurrent with 2 DL slot TBF, there is a PACCH on each slot.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA

if Tra = 2 or Tra = 3 :
if Ttb = 2 or Ttb = 1 : simplex configuration (2+1)C-b

The PACCH channel is on the second Rx timeslot.
0
DL
Rx
Rx
Mx
Ttb
Tra
Tx
UL
0
The PACCH is always on the same slot (2 DL slot TBF, 1 UL slot TBF concurrent with
2 DL slot TBF).
if Ttb = 1 : simplex configuration (2+1)C-a

The PACCH channel may also be on first Rx timeslot.
DL
Rx
Rx
Mx
Ttb
UL
Tra
Tx
0
The PACCH is always on the same slot (2 DL slot TBF, 1 UL slot TBF concurrent
with 2 DL slot TBF).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
if Tra = 2 : simplex configuration (2+1)H (not supported)
Rx
DL
Rx
Mx
Ttb
Tra
Tx
UL
0
The PACCH is always on the same slot (2 DL slot TBF, 1 UL slot TBF concurrent with 2 DL
slot TBF).
if Tra = 2 or Tra = 3 : simplex configuration (3+1)C-a
0
Rx
DL
Rx
Rx
Mx
Ttb
Tra
Tx
UL
0
slot TBF).
if Tra = 2 and (Ttb = 1 or Ttb = 2 ): simplex configuration (3+1)C-b
0
DL
Rx
Rx
Rx
Mx
Ttb
Tra
Tx
UL
0
slot TBF).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
if Tra = 2 and Ttb = 1 : simplex configuration (3+1)H (not supported)
0
DL
Rx
Rx
Rx
Mx
Ttb
Tra
Tx
UL
0
slot TBF).
Only possible if Tt = 1 et Tra = 2.
0
Rx
DL
Rx
Rx
Mx
Ttb
Tra
UL
0
Tx
Tx
In case of 1 UL slot TBF concurrent with 2 or 3 DL slot TBF, there is a PACCH on 2 slot.
In case of 2 UL slot TBF concurrent with 2 or 3 DL slot TBF, there is a PACCH on 1 or 2 slot.
Only possible if Tt = 1 et Tra = 2.
0
DL
Rx
Rx
Rx
Rx
7
Mx
Ttb
Tra
Tx
UL
0
slot TBF).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Duplex Configuration :
The Rx timeslots location depends on parameters Tra. The Tx timeslots location depends on
Ttb. Besides at least the PACCH slot is bi-directional.
0
DL
Rx
Rx
Rx
7
Mx
Tra
Ttb
UL
Tx
0
Tx
1
In case of UL TBF or DL TBF, a PACCH slot is defined taking into account Tra and Ttb. The UL
or DL other slots are located wherever taking into account either Tra (DL TBF) or Ttb (UL TBF).
In case of concurrent UL and DL TBF, 1 or 2 PACCH are defined taking into account Tra. Other
UL and DL slots are located wherever taking into account either Tra (DL TBF) or Ttb (UL TBF) and
taking into account that UL slots require corresponding DL slots.
The example above may illustrate a DL TBF on slot 0 (PACCH) and 4 and UL TBF on slot 2
(PACCH).
5.5.2.1.4
Reservation algorithm principles
The requested throughput is served on the maximum number of slots allowed by the MS multislot
class, the GPRS service constraints (the operator gives the maximum number of allowed slots for
one GPRS connection) and the network constraints (resources availability). Then the allocation
strategy consists in maximising the usage of the allocated PDCH and, if necessary, to require
additional PDCH(s) to the BSC.
This allows to:
Concentrate the load on the middle of the PDCH group.
Provide quite constant throughput to any MSs whatever the global GPRS load is.
A multislot MS gets n times the throughput of a single slot MS, where n is the number of
slots allocated to him.
Free PDCHs when the global GPRS load decreases.
The PDCH available throughput is equally shared between each MS allocated on it.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The following informations are managed per available PDCH :

PDCH identifier = GCH-identifier of the GCH supporting the PDCH
Allocation table (an example is given below):
Direction
UL
TFI
10
13
3
4
13
DL
USF
0
1
2
TAI
0
1
2
NMS
3
- Direction:
UL or DL path
- TFI:
TBF identification
- USF:
USF = 6 is reserved : it can not be allocated to UL TBF.

USF = 7 is reserved (USF = FREE) on MPDCH.
- TAI:
a TAI is used when the PDCH supports the PACCH of the TBF.
Note : a MS may be granted 2 TAI in case of concurrent TBF according to its
multislot capabilities
- NMS:
ED
MCD
current number of MS allocated on the PDCH
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3
PDCH resource control
In order to support GPRS traffic, cell TRX TS shall be configured as PDCH.

Such configuration is performed dynamically according to GPRS traffic needs : negotiation is
performed between MFS and BSC to allocate PDCHs. A maximum number of PDCH that may be
dynamically allocated is configured by the operator.
Besides the operator statically configures the network mode of operation and whether PBCCH is
supported or not in the cell. If the GPRS cell supports a PBCCH and the network mode of operation
is either NMO I or NMO III, the PBCCH is permanently allocated in the cell :
At PBCCH configuration, the MFS requests the BSC to allocate one slot in case there is not yet any
allocated PDCH, which is then afterwards marked as a Master PDCH. In case PDCHs are already
allocated, one among them is chosen as the MPDCH.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.1 Inputs of reservation algorithm
5.5.3.1.1
Parameters
Several O&M parameters enable the tuning of the dynamic allocation process:
MIN_PDCH_GROUP:
Defines the absolute minimum number of PDCHs defined in the PDCH group. As
soon as GPRS starts on a cell (message START GPRS is sent to the BSC), if
MIN_PDCH_GROUP > 0 the MFS sends an ALLOCATION REQUEST to the BSC,
requesting MIN_PDCH_GROUP PDCHs.
If the allocation fails because channels are busy in the BSC, the MFS repeats the
ALLOCATION REQUEST regularly until MIN_PDCH_GROUP PDCHs are allocated
(the timer T_Initial_PDCH is used for the repetition rate).
MIN_PDCH_GROUP=0 is possible. In this case, there is no guarantee that a GPRS
MS can establish a connection in all cases. Indeed the following situation can occur:
No GPRS calls are on-going, so all PDCHs are deallocated. The BSC is heavily
loaded, so all the TS are used for circuit switched calls. Then one GPRS MS
requests a connection: the MFS sends an ALLOCATION REQUEST to the BSC, but
no TS is available => the allocation is rejected and the GPRS call can not be served.
MAX_PDCH_HIGH_LOAD
Defines the maximum number of PDCHs that can be allocated in a PDCH group
when the BSC has indicated a high load situation.
If the number of allocated PDCH is greater than MAX_PDCH_HIGH_LOAD when the
BSC indicates a high load situation, then the MFS marks the exceeding number of
PDCHs as "unusable for new GPRS calls" to empty them and subsequently
deallocate them.
MAX_PDCH_HIGH_LOAD=0 is possible. It means that when the BSC is in a high
load situation, no GPRS call is possible in the PDCH group.
MAX_PDCH_GROUP
Defines the maximum number of PDCHs that can be allocated in a PDCH group.
Whatever the GPRS traffic is, there will never be more than MAX_PDCH_GROUP
PDCHs in a PDCH group
Notes :
In some parts of this document, the generic name MAX_PDCH_XXX is used. It represents either
MAX_PDCH_GROUP, either MAX_PDCH_HIGH_LOAD depending on the cell load situation.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Allocated PDCHs
Maximum number of
PDCHs is reached
MAX_PDCH_GROUP
High cell load: the MFS

deallocates PDCHs as soon
as exceeding PDCHs
become empty.
Maximum number of
PDCHs in high cell load
situation
MAX_PDCH_HIGH_LOAD
MIN_PDCH_GROUP
time
Normal cell load
High cell load
Normal cell load
Cell is created
A GPRS MS requests
4 timeslots
Figure 82: Example of allocated PDCHs

Master channel (B6.2 SMG29)
MIN_MPDCH
Minimum number of PDCHs supporting the master PDCH.
MAX_MPDCH
Maximum number of PDCHs supporting the master PDCH.
In a first step, the master PDCH is limited to one PDCH (no multiple PCCCH). So the range of these
two parameters is limited to [0..1].
MIN_MPDCH
0
0
1
MAX_MPDCH
0
1
1
Behaviour
No master channel in the cell
Dynamic master channel (not supported in B6.2)
Static master channel
Note: A master PDCH is not activated in case of NMO II.

As soon as GPRS starts on a cell (message START GPRS is sent to the BSC), if MIN_MPDCH = 1,
the MFS sends an ALLOCATION REQUEST to the BSC, requesting the allocation of one PDCH.
If the allocation fails because channels are busy in the BSC, the MFS repeats the ALLOCATION
REQUEST regularly until MIN_MPDCH is allocated (the timer T_Initial_PDCH is used for the
repetition rate).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
MS allocation:
MAX_PDCH_PER_TBF
Maximum number of PDCHs allocated to a single TBF. This parameter avoids the
fact that one multislot MS uses too many PDCHs each time it wants to transmit data.
N_TBF_PER_PDCH
Threshold defining the number of TBF (i.e. GPRS unidirectional connection)
supported by a slave PDCH in one direction above which the MFS serves new TBF
preferably by requesting additional resources to the BSC.
N_TBF_PER_MASTER
Threshold defining the number of TBF (i.e. GPRS unidirectional connection)
supported by a master PDCH in one direction above which the MFS serves new TBF
preferably by requesting additional resources to the BSC
MAXMS:
constant defining the maximum number of MS allowed on the PDCH for the
associated direction:
Equal to MAX_UL_TBF_SPDCH for the number of UL TBF on slave PDCH
Equal to MAX_UL_TBF_MPDCH for the number of UL TBF on master PDCH
Equal to MAX_DL_TBF_SPDCH for the number of DL TBF on slave PDCH
Equal to MAX_DL_TBF_MPDCH for the number of DL TBF on master PDCH
Note:
In some parts of this document, the generic name N_TBF_PER_XXX is used. It represents
either N_TBF_PER_PDCH, either N_TBF_PER_MASTER depending if the channel is
master or slave.
According to the number of TBFs in one direction, the PDCH state can take the following values:
MAXMS
N_TBF_PER_XXX
empty
active
bus
full
One PDCH has one state per direction (i.e. one state for UL, one state for DL):
- empty:
- active:
- busy:
- full:
ED
MCD
no established TBF
at least one established TBF and the number of established TBFs is smaller than
N_TBF_PER_XXX
the number of established TBFs is greater or equal to N_TBF_PER_XXX, but
smaller than MAXMS
the number of established TBFs is equal to MAXMS
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.1.2
PCC request
Request received from (RRM) PCC :

Parameters
Range
Request_type
Prese
nce
M
Direction
TFI
M
M
0..1
0..31
Concurrent TFI
0..31
Multislot class
0..29
Max_queuing_time
0..656
Starting_time
0..600
Cell
16
Semantic
type of the request :
- 1 block allocation
- TBF allocation
UL or DL
TBF Identification provided by (RRM) PCC corresponding to
above direction
Identification of concurrent TBF (if any) established in the other
direction
MS multislot class
0 : not known
Latest time before which the request shall be served ; at expiry
of that duration, PRH shall reject the request if not previously
served. In seconds.
0 : no queuing allowed
Present in case of 1 block allocation
Defines the time from which the block may be allowed (in
number of frames)
Cell identity
The MS is considered as a MS multislot class 1 (monoslot MS) in case the multislot class is not
provided.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.2 Initial PDCH allocation

When GPRS service starts in a cell (message START GPRS sent to the BSC), if
MIN_PDCH_GROUP > 0, then the MFS requests the allocation of MIN_PDCH_GROUP PDCHs to
the BSC.
If the required number of consecutive PDCHs is not free in the BSC, then the MFS repeats the
ALLOCATION REQUEST until the required number of PDCHs is allocated.
The repetition rate is fixed by a timer T_INITIAL_PDCH. During that phase, the cell remains
available for GPRS traffic.
The following figure shows an example with MIN_PDCH_GROUP = 2:
BSC
MFS
START GPRS
Legend
START GPRS ACK
Busy TCH
ALLOCATION REQUEST
(total = MIN_PDCH_GROUP = 2)
Free TCH
PDCH
ALLOCATION CONFIRM
(total = 1 PDCH)
Start T_INITIAL_PDCH
T_INITIAL_PDCH expiry
ALLOCATION REQUEST
(total = MIN_PDCH_CELL = 2)
Figure 83: Example of initial PDCH allocation
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.3 Reservation of 1 UL block

When a single block allocation is requested to PRH, the following algorithm is performed:
Step 1. Analysis of current situation
The MFS checks if the block can be allocated using the existing PDCHs, i.e. if there is at least one
PDCH with a state full, in the UL direction (i.e. less than MAXMS mobiles on the UL direction).
If there are several PDCHs with a state different from full, the following ordered criteria are used to
choose a PDCH:
- PDCH which does not support the Master PDCH
- If the number of allocated PDCHs is greater than MIN_PDCH_GROUP, PDCHs which are not on
the edge of the PDCH group.
- PDCH whose current usage is the lowest in the UL direction.
The USF reserved (USFNE) for uplink signalling is granted to MAC when reserving the radio block
together with the starting time from which the block may be reserved.
The selected PDCH is marked as used for one UL block reservation and timer T_One_block is
activated.
The PDCH is marked to avoid PDCH deallocation during One UL block reservation.
At timer expiry, the PDCH is unmarked.
If during the timer activation, another UL block is reserved on this PDCH, the timer is re-activated.
Step 2. Allocation of a new PDCH
If no PDCH is activated in the cell or if all activated PDCHs have their state equal to full, the MFS
checks if an additional PDCH can be allocated.
The algorithm described in section 5.5.3.4 Reservation of multiple blocks with dynamic PDCH
allocation is performed, starting at step 3 with n_MS_requested = 1.
If no additional PDCH can be requested or if the BSC cannot alocate a PDCH, the single block UL
allocation is rejected.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.4 Reservation of multiple blocks with dynamic PDCH allocation

The reservation algorithm is the following (see :
Step 1. Selection of MS supported multislot configurations
See paragraph interpretation of the MS multislot class.
At the end of this step, the maximum number of PDCHs, it is possible to allocate to the MS, is
determined (according to the MS multi-slot class and the O&M parameter MAX_PDCH_PER_TBF)
Step 2. Analysis of concurrent TBF constraints
No resource reallocation is foreseen in B6.2. Consequently TBF establishment on one direction shall
comply with constraints imposed by potential concurrent TBF on the other direction. See paragraph
interpretation of the MS multislot capability.
As a consequence:
- MS supported multislot configurations may be reduced (n_MS_requested)
- Some PDTCH/PACCH locations may be imposed.
The timeslots not usable due to concurrent TBF constraints are marqued as unusable.
Example:
1) Hypothesis:
A DL TBF establishment is requested, with an on-going UL concurrent TBF (on 2 UL slots:
TS1 and TS2).
The MS multi-slot class is 10.
2) B6.2 :
The configurations supported by a class 10 MS are the following:
2+1, 3+1, 3+2, 4+1, 1+1, 2+2 (DL + UL)
The maximum number of DL PDCHs is 4 (provided MAX_PDCH_PER_TBF 4)
3) Step2
The concurrent UL TBF has 2 UL PDCHs, so supported configurations are restricted to:
3+2 and 2+2.
- 3+2 configuration imposes DL PDTCHs on TS0, TS1 and TS2 (UL dynamic allocation
requires symetric capabilies TS1 and TS2 have to be used for DL; TS3 cannot be used,
due to Ttb constraint),
with PACCH either on TS1 or TS2 (PACCH is bi-directional)
0
Rx
DL
Rx
Rx
Ttb
UL
0
ED
MCD
Tx
Tx
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- 2+2 configuration imposes DL PDTCHs on TS1 and TS2 (UL dynamic allocation
requires symetric capabilies TS1 and TS2 have to be used for DL), with PACCH either on
TS1 or TS2
0
DL
Rx
Rx
Ttb
UL
0
Tx
Tx
At the end of step2 process, the maximum number of PDCHs is equal to 3, with TS0, TS1 and TS2
as imposed location (i.e. TS3, TS4, TS5, TS6 and TS7 are marked as unusable).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Step 3.
Selection of a timeslots allocations
At the beginning of this step

- the maximum number of PDCHs which can be allocated is known (n_MS_requested)
- some positions may be unusable due to concurrent TBF constraints
- n_allocated_pdch is the total number of allocated PDChs
The aim of this step is to compute n_consecutive_pdch which is the maximum number of
consecutive PDCHs which state is equal to active or empty and not unusable, i.e. not marqued
as described in step2.
Below are 2 examples related to the previous parameters:
MAXMS
N_TBF_PER_XXX
TC
H
- n_consecutive_pdch = 2 (TS3-TS4)
- n_allocated_pdch = 6 (TS1, TS2, TS3, TS4, TS5, TS6)
MAXMS
N_TBF_PER_XXX
TC
H
- n_consecutive_pdch = 2 (TS2-TS3)
- n_allocated_pdch = 4 (TS1, TS2, TS3, TS5)
Figure 84: Parameters calculated for dynamic allocation
When a GPRS connection request is received by PRH, PRH checks if the already allocated PDCHs
can serve the request:
n_consecutive_pdch n_MS_requested
(PRH-1)
If (PRH-1) condition is fulfilled, then step 4 of allocation algorithm is processed.

If (PRH-1) condition is not fulfilled, then the MFS checks if additional PDCHs can be allocated:
ED
MCD
Cell normal load:
n_allocated_pdch < MAX_PDCH_GROUP
Cell high load:
n_allocated_pdch < MAX_PDCH_HIGH_LOAD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(PRH-2)
If (PRH-2) is fulfilled and if new PDCHs are potentially usable (see step 2), then the MFS shall send
an ALLOCATION REQUEST to the BSC, with the following parameters:
- The PDCH group on which the allocation shall be served (in GPRS step 1, always set to 1),
- n_MS_requested
- Span (in GPRS step 1, always equal to n_MS_requested)
- MAX_PDCH_GROUP or MAX_PDCH_HIGH_LOAD, depending if the cell is in normal load or high
load,
- bm2: A bitmap giving the usable GPRS channels (see step 2 for the unusable channels).
An example of bm2 is given below:
In this example, TS0 and TS1 are not usable due to TBF concurrent constraints, TS2 is in the busy
state and TS4 is in the full state.
MAX_UL/DL_TBF_S/MPDCH
N_TBF_PER_PDCH
TC
H
bm2
unusable
The detailed description of the message is given in ref.3, the BSC behaviour when the message is
received is given in ref.[18].
In both cases, the BSC tries to allocate free timeslots (see ref. [18]) and sends an ALLOCATION
CONFIRM to the MFS indicating the new configuration of the PDCH group.
At ALLOCATION CONFIRM reception, n_consecutive_pdch and n_allocated_pdch are updated, and
the processing described in step 4 is done.
If (PRH-2) is not fulfilled, then the processing described in the step 4 is done without any allocation
request towards the BSC.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Step 4.
Selection of a timeslots allocations
The aim of this step is to select a timeslot allocation.

If a request to the BSC has been necessary, n_consecutive_pdch is recomputed at the BSC
response.
n_consecutive_pdch
n_MS_requested
The GPRS request is served on the

n_consecutive_pdch PDCHs (note 1)
(PRH-3a)
n_consecutive_pdch 0 AND
n_consecutive_pdch
n_MS_requested
The GPRS request is served on:

- n_consecutive_pdch PDCHs (note1)
- the MFS tries to extend the selected
combination of n_consecutive_pdch PDCHs
to n_MS_requested, using adjacent PDCHs
which are not in the full state (note 1)
(PRH-3b)
n_consecutive_pdch = 0
n_allocated_pdch > 0
At least one usable PDCH
not in the full state
The GPRS request is served on the usable

PDCHs not in the full state (note 1)
(PRH-3c)
n_allocated_pdch = 0 or all
usable PDCHs in the full
state
Uplink request:
The GPRS request is rejected
(PRH-3d)
Downlink request:
The
GPRS
request
is
queued
(max_queuing_time), T_INITIAL_PDCH is
started and step 5 is performed.
Note 1:
ED
MCD
If several possibilities are offered, the MFS chooses a group of consecutive PDCHs that
does not include PDCHs on the edge of the PDCH group, only if n_allocated_pdch >
Min_PDCH_Group
- If several possibilities verify that rule, then the MFS chooses the solution with the lowest
number of established GPRS Mss, in the current direction.
There is one exception to this last rule, in the following case:
- MIN_PDCH_GROUP 2
- n_allocated_pdch = 2
- n_MS-requested = 1
In this case, when the 2 PDCHs are in the active state, one PDCH is chosen in priority
(the the PDCH carrying the MPDCH if a static MPDCH is configured in the cell ; otherwise
the PDCH which is the closest of the middle of the PDCH group), in order to return more
easily to MIN_PDCH_GROUP value.
- If several possibilities verify the 2 previous rules, the concurrent combination of each
possibility, according to MS multi-slot class used in the current direction, is evaluated taking
into account on-going TBFs. The MFS chooses the combination whose concurrent
combination has the lowest number of established TBFs
- If several possibilities verify the 3 previous rules, the most central combination is chosen.
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Step 5. Queuing of downlink multiple blocks requests

At the end of step 4, if no resource is available, some downlink requests may be queued during
max_queueing_time.
When queuing is active, T_INITIAL_PDCH is running and the new downlink LLC PDU are bufferised
in the order of their time expiry, calculated using the PDU lifetime expiry. The first to be dequeued is
the one with the shortest lifetime.
If a TBF ends while queuing is active, then step 4 is reperformed as long as resources are available.
If a multislot TBF ends, then several single slot requests may be served.
If all the requests are dequeued, then T_INITIAL_PDCH is stopped.
When T_INITIAL_PDCH expires, the allocation algorithm is reperformed, starting from step3, for the
first request queued (i.e. the one with the shortest lifetime).
For each request of the queue, when max_queueing_time expires the request is removed from the
queue. If it is the last request in the queue, then T_INITIAL_PDCH is stopped.
BSC
MFS
SGSN
LLC PDU 1
All PDCHs are full.

ALLOCATION REQUEST
No new PDCH is available.
ALLOCATION CONFIRM
The request 1 is queued.
ALLOCATION REQUEST
No new PDCH is available.

ALLOCATION CONFIRM
LLC PDU 2
The request 2 is queued.
max_queueing_time of request 1 expires:
request 1 is removed from the queue.
Request 2 still in the queue.
ALLOCATION REQUEST
A new PDCH is available.

ALLOCATION CONFIRM
(new PDCH)
The request 2 is served.
Figure 85: Queuing of downlink request
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
To sum up the MFS behaviour:

TBF request
(MS mulit-slot class)
MAX_PDCH_PER_TBF
Selection of MS
supported multi-slot
configuration
STEP1
Max. number of PDCHs

Analysis of
concurrent TBF
constraints
STEP2
n_MS_requested
[imposed locations]
n_consecutive_pdch
n_MS_requested
PRH-1
STEP3
PRH-2
n_allocated_pdch < MAX_PDCH_XXX

Allocation request
to the BSC
n_consecutive_pdch
update
Selection of
time-slot allocation
STEP4
Figure 86: MFS decision process for GPRS assignment
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.5 Examples of reservation of multiple blocks

EX1: first establishment, MIN_PDCH_GROUP=0
The initial situation is:
MAXM
N_TBF_PER_XX
X
TC
H
A MS with a multislot class = 5 requires an unidirectional GPRS connection, no concurrent TBF

constraints.
The multislot class indicates that the MS is able to use 2 consecutive timeslots. The MFS requests
them to the BSC and allocates them to the MS:
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
EX2: Subsequent establishment.

MAXM
N_TBF_PER_XX
X
TC
H

constraints.
The multislot class indicates that the MS is able to use 2 consecutive timeslots.
The MFS sends an ALLOCATION REQUEST to the BSC, indicating:
- n_MS_requested = 2
- MAX_PDCH_XXX
- bm2 = xxx0xxxx
If the BSC allocates the timeslot on the high part of the TRX (TS 5), the MFS allocates timeslots 4
and 5 to the MS:
MAXM
N_TBF_PER_XX
X
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
EX3: Subsequent establishment

MAXMS
N_TBF_PER_XXX
TC
H
MAX_PDCH_GROUP = 5 and the cell in is a normal load situation.

A MS with a multislot class = 7 requires a downlink GPRS connection, with an already established
uplink connection on TS5.
The concurrent TBF constraints show that the only usable timeslots are TS4, TS5 and TS6 => TS0,
TS1, TS2, TS3 and TS7 are unusable..
TS4 is busy..
- MAX_PDCH_XXX = 5
- bm2 = 00000xx0
The BSC will try to allocate TS6.
At the response of the BSC, n_consecutive_pdch = 2 (TS5 and TS6) ( n_MS_requested).
The time-slot combination can be extended to TS4 which is not in the full state.
The downlink request will be served on TS4 + TS5 + TS6.
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
EX4: Subsequent establishment, congestion situation.

MAXMS
N_TBF_PER_ XXX
TC
H

constraints.
- MAX_PDCH_XXX
- bm2 = xxx000xx
If the BSC is not able to allocate any additional PDCH because timeslots are busy with CS calls, then
the MS request is allocated on the existing PDCHs, even if they are in the busy state (but not if
they are in the full state.
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
EX5: first establishment, MIN_PDCH_GROUP=3, MAX_PDCH_GROUP = 6

MAXMS
N_TBF_PER_XX
X
TC
H
The BSC is only able to allocate 2 PDCHs (TS1 - TS2)

MAXMS
N_TBF_PER_XX
X
TC
H
Then, these PDCHs are used for TBF establishment.
But as MIN_PDCH_GROUP value is not reached, the MFS periodically sends a request to the BSC.
When the BSC receives one of this periodic request, the situation is the following:
TS 0 and TS 3 are used for circuit-switched traffic, but TS4, TS5 and TS6 are free.
So, the BSC allocates TS4, TS5 and TS6.
MAXM
N_TBF_PER_XX
X
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
MIN_PDCH_GROUP is exceeded, so T_PDCH_inactivity timer is set for TS5 and TS6.

At T_PDCH_inactivity expiry, TS5 and TS6 are deallocated.
MAXMS
N_TBF_PER_XX
X
TC
H
EX6: The initial situation is the following:
TS1, TS4 and TS6 are allocated and are in the active state.
MAXMS
N_TBF_PER_XXX
TC
H
If a mono-slot request has to be satisfied, TS4 will be allocated (TS1 and TS6 are on the edges of
the PDCH group)
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.6 Allocation request procedure

BSC response time is limited,
- in DL, by PDU-life-time
- in UL, this time is limited by T_ul_access_max
If the BSC has not sent, the ALLOCATION CONFIRM message, at T_ul_access_max expiry,
the UL TBF establishment fails and an Immediate Assignment Reject or a Packet Access
Reject message is sent.
5.5.3.7 Dynamic deallocation
The MFS is the master for deallocation. The MFS takes into account the cell load situation.
The reason for deallocating one (or several) PDCH(s) is:
1) GPRS low load: a PDCH becomes free. (may also occur when a MPDCH is deactivated (NMO
set to NMO II) or when the value of Min_PDCH_GROUP is decreased and there is no traffic
on the exceeding PDCH(s).)
2) BSC "soft" pre-emption: the cell is in a high load situation and needs additional resources for
circuit switched call.
3) fast pre-emption in case of UL Gb congestion (see 5.5.4)
5.5.3.7.1
GPRS low load:
The following conditions must be fulfilled at the same time:

- The PDCH does not support a master channel
- The PDCH carries no more TBF (note 1). (empty state)
(PRH-4)
- The PDCH has no on-going UL block reservation

- n_allocated_pdch > MIN_PDCH_GROUP
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note 1:
That means that all the resource have been released. Especially, in case the last MS is lost,
the resource is not released until the radiolink timeout has expired.
The MFS checks (PRH-4) each time a TBF ends or the UL block reservation timer expires if at least
one PDCH respects (PRH-4), then the MFS activates T_PDCH_inactivity timer (or
T_PDCH_Inactivity_Last timer, if it is the last PDCH of the cell)
At its expiration (i.e. the PDCH has not be re-used for another TBF during the timer duration or an UL
block has not been reserved), the MFS sends a DEALLOCATION COMMAND message to the BSC.
In case a TBF is allocated or an UL block is reseved on a PDCH whose T_PDCH_Inactivity(_Last)
timer is running, the timer is stopped.
Note: As any inactive PDCH may be released by the MFS, holes are created in the PDCHs
allocated to the MFS. The BSC will try to allocate preferably these holes at next radio
resource request sent by the MFS (see RAM specification)
T_One_Block
expiry
UL block
reserved (6)
Active
no more TBF
on the PDCH
nor UL block
reserved
(1)
TBF
establishment
(5)
T_PDCH_
Inactivity_(Last)
expiry
(4)
Empty
T_One_Block
expiry
UL block
reserved
(3)
no more TBF
on the PDCH
but UL block
reserved (7)
TBF
establishment
UL block
reserved
(2)
UL block
reserved
Figure 87 Dynamic Deallocation

(1):
T_PDCH_Inactivity or T_PDCH_Inactivity_Last is activated
(2):
T_PDCH_Inactivity or T_PDCH_Inactivity_Last is deactivated, T_One_Block is activated.
(3):
T_One_Block is re-activated
(4):
Deallocation towards BSC
(5):
T_PDCH_Inactivity or T_PDCH_Inactivity_Last is deactivated
(6):
T_One_Block is activated
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
(7):
nothing is done, T_One_Block (only) is still running
5.5.3.7.2
BSC soft pre-emption
When the load situation of the cell changes from "normal load" to "high load", then the MFS limits
the number of allocated PDCHs to MAX_PDCH_HIGH_LOAD.
5.5.3.7.2.1
PDCH choice
If more than MAX_PDCH_HIGH_LOAD PDCHs are allocated in the cell, then the MFS marks
(n_allocated_pdch - MAX_PDCH_HIGH_LOAD) PDCHs as not usable for new TBFs.
The following figure defines the algorithm to choose the PDCHs to be marked:
The slot carrying the MPDCH shall not be released.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
In this algorithm,
the MPDCH shall
not be taken into
account
N PDCHs have
to be marked
No
PDCH(s) in
empty state?
Yes; Ne PDCHs in the empty state

Ne > N
N = Ne
Ne?
N PDCHs
among the Ne
have to be
deallocated
Ne < N
PDCH Choice
according to
Criteria 2
N = N -1
The Ne PDCHs
are deallocated
The Ne PDCHs
are deallocated
End
N = N- Ne
several
disjoined
PDCH sets?
N
N=0?
Choice
according to
Criteria 1
Choice
according to
Criteria 2
End
End
End
Figure 88 PDCH choice algorithm

- Criteria 1 (the aim is not to create holes)
The PDCH to be released is the PDCH located at the edge of the set of active PDCHs having the
lowest number of established TBFs. The process is run again if at least another PDCH shall be
released.
- Criteria 2 (the aim is to deallocate first PDCHs which belong to the smallest group and not to create
holes)
The PDCH(s) to be released are selected according to the following criteria ordered from the most to
the less important :
- keep the largest group of consecutive PDCHs
- limit the number of holes
- favour position closer to the largest group
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- release the PDCH with the lowest number of established TBFs

5.5.3.7.2.2
soft-pre-emption process example
A PDCH supporting a MPDCH shall never be preempted (in line with MIN_PDCH_GROUP > 0 when
a MPDCH is configured).
The following figure shows an example of choosing the "soft" pre-empted PDCHs. In this example,
the MFS could have chosen the following PDCHs : (1, 2), (1, 5), (4, 5).
The choice has been (1, 5) because TS1 and TS5 are on the edge of the PDCH group and these
PDCHs are those which have the less established TBFs (criteria 1).
(MIN_PDCH_GROUP = 2, MAX_PDCH_HIGH_LOAD = 3, n_allocated_pdch = 5
MAXMS
N_TBF_PER_XX
X
TC
H
Figure 89: Example of "soft" pre-emption decision

When the TBF(s) established on one of these marked PDCHs are released, the MFS deallocates this
PDCH by sending a DEALLOCATION COMMAND message to the BSC. (Of course,
T_PDCH_Inactivity is not used in this case)
MAXMS
N_TBF_PER_XXX
TC
H
A DEALLOCATION COMMAND message, related to TS5 is sent to the BSC
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
MAXMS
N_TBF_PER_XXX
TC
H
A DEALLOCATION COMMAND message, related to TS1 is sent to the BSC
Note:
If an unmarked PDCH becomes empty during the period where some PDCHs are marked,
one marked PDCH is unmarked.
5.5.3.7.3
fast pre-emption
This process is used in case of UL Gb congestion.

The PDCH is chosen with the same criteria as for the soft pre-emption process
5.5.3.8 Multi requests handling (B6.2 SMG29)
In order not to block other TBF requests (especially one-block UL requests), for the same cell, during
an allocation request towards the BSC, the following principles are implemented:
- Only one allocation towards the BSC at the same time
- Per direction (i.e. uplink and downlink), only one TBF request postponed for lack of
resources. During this postponement, resources are reserved for the request, in order to
make sure that the request will get always a minimum of resources at BSC response.
- During the time of the allocation request exchange with the BSC other TBF
establishment requests can be served provided no additional resources are necessary and
no more than one TBF request is postponed in the same direction.
- At BSC response, postponed requests are taken into account:
- reserved resource release
- step3 processing (n_consecutive_pdch is re-evaluated)
- step4 processing
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Example:
UL initial situation:
MAXMS
N_TBF_PER_XXX
TC
H
DL initial situation:
MAXMS
N_TBF_PER_XX
X
TC
H
1) An UL TBF establishment request needs 3 time-slots (no concurent TBF constraint)
An allocation request is sent to the BSC with the following bit-map:
0
One of the n_consecutive_pdch combination is reserved (e.g. TS2-TS3)

MAXMS
N_TBF_PER_XXX
TC
H
Then during the exchange with the BSC, other TBF establishment requests are served:
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2) An DL TBF establishment request needs 3 time-slots (no concurent TBF constraint)

n_consecutive_pdch = 2 (TS5-TS6) n_MS_requested, the request cannot be satisfied.
Supplementary resources cannot be requested to the BSC, since there is already one on-going
request.
Resources are reserved for this request (no other request already postponed in downlink): TS5-TS6
MAXMS
N_TBF_PER_XXX
TC
H
3) An DL TBF establishment request needs 1 time-slot (no concurent TBF constraint)
This request is served (TS3)
MAXMS
N_TBF_PER_XXX
TC
H
4) An UL TBF establishment request needs 1 time-slot (no concurent TBF constraint)
This request is served (TS5)
MAXMS
N_TBF_PER_XXX
TC
H
5) An DL TBF establishment request needs 1 time-slot (no concurent TBF constraint)
This request is not served and downlink is blocked (a downlink request is already postponed)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6) An UL TBF establishment request needs 3 time-slots (no concurent TBF constraint).

The request cannot be served and uplink is blocked (an uplink request is already postponed)
From this instant no more request can be served, the following requests are queued.
Request
request 1
request 2
request 5
request 6
Resource reservation
UL TS2 - TS3
DL TS5 - TS6
0
0
7) At BSC response, TS7 has been allocated and the situation is the following:
MAXMS
N_TBF_PER_XXX
TC
H
Request 1 is processed.
TS2 and TS3 reservations are deallocated:
MAXMS
N_TBF_PER_XXX
TC
H
Step3 is processed:
n_consecutive_pdch is updated: n_consecutive_pdch = 3 (TS5, TS6, TS7).
n_consecutive_pdch = n_MS_requested, these 3 time-slots are allocated to the MS (step4)
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
8) Then request 2 is processed.

TS5 and TS6 reservations are deallocated:
MAXMS
N_TBF_PER_XXX
TC
H
n_consecutive_pdch is updated: n_consecutive_pdch = 3 (TS5, TS6, TS7).
n_consecutive_pdch = n_MS_requested, these 3 time-slots are allocated to the MS.
MAXMS
N_TBF_PER_XXX
TC
H
TS7 is allocated
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA

MAXMS
N_TBF_PER_XXX
TC
H
n_consecutive_pdch (= 2) < n_MS_requested (=3)
An allocation request is performed to the BSC and TS2 and TS3 are reserved.
MAXMS
N_TBF_PER_XXX
TC
H
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.5.3.9 Allocation / Deallocation of the MPDCH

In case several PDCHs are already allocated at the time of the activation of the MPDCH, the most
central PDCH within the set of allocated PDCHs shall be configured as the MPDCH.
The parameter N_TBF_PER_MASTER, MAX_UL_TBF_MPDCH and MAX_DL_TBF_MPDCH
become the new applicable thresholds on that PDCH.
Any on-going traffic on that PDCH shall not be impacted by the configuration change.
In case the MPDCH shall be deactivated (NMO is set to NMO II, or MIN_MPDCH is set to 0), the
PDCH carrying the MPDCH can be deallocated under the conditions defined in 5.5.3.7.
In case the PDCH supporting the MPDCH is lost (e.g. occurrence of a fault on its corresponding Ater
circuit) or following the reset of a cell equipped with a MPDCH, the MFS shall autonomously reestablish the MPDCH.
5.5.4 UL congestion control

The purpose of this function is to adapt the UL data flow in case of a Gb congestion noticed on a
given NSE (i.e. a BSS). It consists in reducing the uplink data flow to avoid useless transmission of
UL LLC PDUs that would be discarded by the NS layer and that would provoke retransmissions and
waste of radio resources.
An NSE congestion is notified by BSSGP through NM-NSE-Congestion-ind, whose parameters are:
- action (start: beginning of the congestion; stop: end of the congestion)
- level 1 (only one level in B6.2 )
- NSE available bandwidth (current capacity of the NSE)
- NSE maximum bandwidth (maximum capacity of the NSE)
This information is triggered by NSC when all Operational NS-VC belonging to the same NSE are
congested (i.e. the congestion threshold of each NS-VC is over-crossed; therefore no new LSP
allocation cant be accepted) ; congestion may be either due to a configuration error or a fault while
there is high UL traffic.
In case of NSE congestion, the following UL congestion control procedure is activated if enabled by
the O&M parameter EN_UL_CONGESTION :
RRM stops the UL data traffic on one PDCH in each cell of the BSS where there is on-going data
traffic (the PDCH is chosen with the same rules as the soft pre-emption process). The PDCH
purged from GPRS traffic (the Packet PDCH Release message is sent on all PDCHs, corresponding
radio resources are frozen) may or not be deallocated according to the requirements defined in
5.5.3.7 (e.g. the PDCH is not given back to the BSC if it would violate the MIN_PDCH_GROUP > 0
request).
The MFS does not allocate any new PDCH in the BSS.
This procedure is restarted every T_UL_CONGESTION seconds if the Gb congestion is still present.
When the congestion situation disappears on all the NS-VCs, a notification is sent (action = stop).
The MFS starts reallocating PDCHs in the BSS when needed.
5.5.5 NSE capacity bandwidth adaptation (not implemented)

The purpose of this function is to adapt the UL (and DL) data flow according to the available Gb
throughput in case the NSE capacity bandwidth is reduced due to either a fault or O&M lock of one
or several NS-VCin case of a Gb failure (e.g. PCM failure). Purpose is still to avoid useless uplink
data transmissions and waste of radio resources.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
The NSE throughput on Gb interface is notified by BSSGP to RRM, through NM-NSE-CAPACITY-ind

whose parameters are:
- NSE availabilty bandwidth (takes into account throughput of the available NS-VCs)
- NSE maximum bandwidth (takes into account throughput of all the existing NS-VCs)
The first NM-NSE-CAPACITY-ind is sent at the end of the BVC-SIG RESET procedure, and then,
each time one of the 2 parameters is modified.
In case of NSE capacity bandwidth reduction, the following NSE capacity bandwidth reduction
procedure is activated if enabled by the O&M parameter EN_CAP_REDUCTION :
The maximum number of available GCHs within BSS is reduced from the percentage of loss of
bandwidth at Gb side.
Ongoing traffic is not impacted, i.e. RRM shall not reduce the number of active PDCHs even if the
number of active GCHs is higher than the number of GCHs allowed to be used due to the NSE
capacity bandwidth reduction.
5.6
NTM Entity detailed description
The main function of NTM is to manage RRM entities: BSS, GIC groups and cells.
NTM notifies entity state changes to other blocks or layers.
5.6.1 Functions description

5.6.1.1 Managed entities
RRM managed entities are shown on the following figure and described below.
BSS
1 to n
relation
GIC-group
Cell
Figure 90 Entity relationship diagram
Note: In B6.2 , as there is only one PDCH group per cell, PDCH group has not been introduced.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.6.1.1.1
BSS
Its availabilty is determined by: (see Figure 91, for numbers between brackets)
1) an operational state which depends on
- BSCGP indications (available/unavailable)
This status is sent with NTM-BSC-STATE-CHANGE-ind/cnf (1)
A BSC unavailability can have different origins:
- BSC failure
- BSC locked by an O&M command
- GSL links failure
- a Signalling BVC (BVC-SIG) status (operational/not operational)
This status is sent by the BSSGP layer (NM-BVC-SIG-T-STATUS) (3)
2) a BSC administrative state (locked/unlocked)
This state is managed by the OMC-R (LM-BSS-SET-req (2))
5.6.1.1.1.1
BSS creation
On BSS creation (LM-BSC-CREATE-req) (see 5.1.5.1), BVC-SIG is created, at BSSGP level.

5.6.1.1.1.2
BSS deletion
On BSS deletion (LM-BSC-DELETE-req), BVC-SIG is deleted, at BSSGP level

5.6.1.1.1.3
BSS state change
When the 3 following conditions are verified:

- BSCGP indication: BSS state = available
- BSS administartive state = unlocked
- BVC-SIG status = operational
the BVC-SIG is started (NM-BVC-SIG-START-req) (a BVC-SIG reset procedure is undertaken by
BSSGP) (4).
If the BSSGP procedure succeeds (BVC-SIG status = operational, started), then the BSS is available
and cells may be started for GPRS traffic.
As soon as one of the 3 previous conditions is no more verified, GPRS has to be stopped in all the
cells belonging to the BSS and the BVC-SIG is stopped (NM-BVC-SIG-STOP-req) (4).
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.6.1.1.2
Cell
Its availabilty is determined by: (see Figure 91, for numbers between the brackets)
1) a cell operational state which depends on
- BSCGP indications: NTM-CELL-STATE-CHANGE-ind/cnf (5)
- BVC-PTP status
This status is sent by the BSSGP layer (NM-BVC-PTP-T-STATUS) (6)
- BSS state (see previously) (7)
- RRM internal conditions (e.g. MPDCH release) (8)
2) a Cell administrative state
This state is managed by the OMC-R (LM-CELL-SET-req (9))
5.6.1.1.2.1
Cell creation
On cell creation (LM-CELL-CREATE-req) (see 5.1.5.4):

- BVC-PTP is created, at BSSGP level (a BVC-PTP RESET procedure is undertaken).
- cell state is requested to the BSC (NM-CELL-STATE-req)
5.6.1.1.2.2
Cell deletion
On cell deletion (LM-CELL-DELETE-req):

- BVC-PTP is deleted, at BSSGP level
- BSC is notified (NM-CELL-DETACH-req) (B6.2 only)
5.6.1.1.2.3
Cell state change
- When the 3 following conditions are verified:

- BSCGP indication: Cell state = available
- Cell administartive state = unlocked
- BVC-PTP status = operational
the BVC-PTP is started (NM-BVC-PTP-START-req) (a BVC-PTP unblock procedure is undertaken by
BSSGP) (10).
If the BSSGP procedure succeeds (BVC-PTP status = operational, started), then the cell is available
and GPRS traffic can be activated:
- NTM-CELL-START-req (11) is sent to the BSC (via BSCGP), in order to forward on BCCH, that
GPRS is supported (SI3/4) and to broadcast SI13
- Resources are requested to the BSC (through BSCGP), according to MIN_PDCH_Group or
MIN_MPDCH values.
- Corresponding GCH links are established
- a first flow control message is sent to the SGSN (NM-FLOW-CONTROL-BVC-req is sent to
BSSGP) and the timer T_Flow_Ctrl_Cell is activated to send periodically a flow control message
(B6.2 only)
(In Pilot, T_BVC_Flow_Ack is activated to control the acknowledgement reception)
- If there is a master PDCH (MIN_MPDCH = 1):
- PSI is broadcast on the PBCCH
- BSC is requested to allocate a MPDCH and to broadcast its location on SI13.
- If there is no master PDCH (MIN_MPDCH = 0), PSI13 is broadcast on PACCHs (B6.2 only)
As soon as one of the 3 previous conditions is no more verified or for an internal RRM reason (8),
GPRS has to be stopped in the cell:
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
- Packet PDCH release messages are sent on each PACCH of the cell (all the TBFs
established
in the cell have to be released)
- the BVC-PTP is stopped (NM-BVC-PTP-STOP-req) (10), a BVC-PTP block procedure is
undertaken, by BSSGP
- if there is a master PDCH:
- BSC is requested to deallocate the MPDCH (MPDCH location is no more indicated in SI13)
- PSI1 is broadcast with the BS_PCC_REL flag set (i.e. on PSI1 reading, MSs will attempt to
read SI13 and will perform a complete acquisition of BCCH messages)
- T_MPDCH_Deact is activated (to give time to the MSs to read the BS_PCC-REL indication
before stopping the broadcast of PSI)
- At T_MPDCH_Deact expiry:
- PSI broadcast is stopped
- GCH links are released
- PDCH deallocation is requested to the BSC
- A GPRS-STOP message is sent to the BSC (NTM-CELL-STOP-req) (11), SI13
broadcast is stopped and SI3/4 indicates that the cell doesnt support GPRS.
- If there is no master PDCH:
- PSI13 is no more broadcast on PACCH
- GCH links are released
- PDCH deallocation is requested to the BSC
- A GPRS-STOP message is sent to the BSC (NTM-CELL-STOP-req) (11), SI13 broadcast is
stopped and SI3/4 indicates that the cell doesnt support GPRS.
The cell also reports its MPDCH operational state (enabled / disabled). The cell operational state
does not depend on its MPDCH state. On reverse, the MPDCH operational state depends on the cell
operational state.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
O&M
BSCGP
RRM
(BSS)
LM-BSS-Set-req
(lock/unlock) (2)
BSSGP
ad.
state
NTM-BSS-St-Ch-ind/cnf
(enabled/disabled) (1)
op.
NM-BVC-SIG-T-STATUS-ind (3)
state
BSS state
O&M
BSCGP
LM-Cell-Set-req
(lock/unlock) (9)
NTM-cell-St-Ch-ind/cnf
(enabled/disabled) (5)
RRM internal
state (8)
NM-BVC-SIG-START/STOP-req (4)
(7)
ad.
state
op.
NM-BVC-PTP-START/STOP-req (10)
NM-BVC-PTP-T-STATUS-ind (6)
state
NTM-CELL-START/STOP-req (11)
BSCGP
GPRS cell availability

RRM
(cell)
Figure 91 BSS/CELL state relationship
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.6.1.1.3
GIC-Group
It is the set of all Ater circuits, usable for GPRS traffic (GIC), pertaining to the same Ater PCM.
All GICs of the same GIC-Group have the same operational state, which is provided by the BSC.
Its availability depends on BSCGP indications (NTM-GICGROUP-State-Change-ind/cnf)
5.6.1.1.3.1
GICGROUP creation
On GIC group creation (LM-GICGROUP-CREATE-req), its state is requested to the BSC (NTMGICGROUP-STATE-req)
5.6.1.1.3.2
GICGROUP state change
Gic group state changes are received from the BSC..
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
5.6.1.2 Performance Monitoring

PM telecom counters definition
(see 19)
For each cell occurrence, the following counters are associated :
name
monitored
entity
type
P1
Cell
timer
P9
Cell
counter
P10
Cell
counter
P11
Cell
counter
P12
Cell
counter
P13
Cell
timer
P14
Cell
counter
P15
Cell
counter
P16
Cell
timer
P17
Cell
counter
P19
Cell
counter
P22
ED
MCD
counter
Cell
triggering event
description
- started when a high load
indication is received from
the BSC
- stopped when a normal
load indication is received
from the BSC, or when
GPRS traffic is stopped in
the cell
number of DL TBF normal
releases
number of discarded DL LLC
PDU due to PDU lifetime
expiry
number of DL TBF releases
due to Gb failure
number of DL TBF releases
due to radio problems
- started when no more
resources are available in
the DL direction (i.e. all
PDCHs in the full state and
n_allocated_pdch =
MAX_PDCH_XXX)
- stopped when the previous
condition is false
number of DL TBF
establishment failures, at
PDU life-time expiry, due to
lack of radio resources
number of DL TBF
establishment failures, after
Max_Retrans_DL attempts,
due to MS not responding
cumulated time of DL TBFs
for one TBF:
-started, at Packet Control
Acknowledgement reception
- stopped on PCC-RLCRELEASE-ind
number of DL TBF
establishment successes
number of successful (at
least one allocated PDCH)
Allocation Confirm messages
received from the BSC
number of UL TBF normal
releases
threshold
presence
tide-mark
presence
target
no
no
B6.2
no
No
Pilot
no
no
Pilot
no
no
B6.2
no
no
Pilot
no
no
B6.2
no
No
demo
no
No
demo
no
no
B6.2
no
No
demo
no
no
B6.2
no
No
Pilot
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
monitored
entity
type
P24
Cell
counter
P25
Cell
counter
P26
Cell
timer
P27
Cell
counter
P28
Cell
counter
P29
Cell
timer
P30
Cell
counter
P36
Cell
gauge
P38
Cell
timer
P40
Cell
gauge
P43
Cell
counter
P44
Cell
counter
P49
Cell
counter
P50
Cell
counter
P52
Cell
counter
P53a
Cell
counter
name
ED
MCD
triggering event
description
number of UL TBF releases
due to Gb failure
number of UL TBF releases
due to radio problem
- started when no more
resources are available in
the UL direction (i.e. all
PDCHs in the full state and
n_allocated_pdch =
MAX_PDCH_XXX)
- stopped when the previous
condition is false
number of UL TBF
establishment failures due to
lack of radio resources
number of UL TBF
MS not responding
cumulated time of UL TBFs
for one TBF:
-started, at Packet Control
Acknowledgement reception
- stopped on PCC-RLCRELEASE-ind
number of UL TBF
establishment successes
Current number of DL TBF
threshold
presence
tide-mark
presence
target
no
no
B6.2
no
no
Pilot
no
no
B6.2
no
No
demo
no
No
demo
no
no
B6.2
no
No
demo
no
P35
(max)
no
B6.2
B6.2
Cumulative time during

which the PDCHs are
allocated for the cell
Current number of UL TBF
no
Number of DL LLC bytes,

received from the SGSN
Number of UL LLC bytes,
sent to the SGSN
Number of Immediate
assignments sent through
BSCGP
number of DL TBF
establishment procedures (a
procedure may include
Max_retrans_DL retries)
Number of Packet UL/DL
assignment sent on PCCCH
Number of PS Paging
requests sent through
BSCGP
no
P39
(max)
no
no
no
Pilot
no
no
B6.2
no
no
Pilot
no
no
B6.2
no
no
B6.2
no
B6.2
Pilot
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
name
monitored
entity
type
P53b
Cell
counter
P54
Cell
counter
P61a
Cell
counter
P61b
Cell
counter
P62
Cell
counter
P63
Cell
gauge
P65
Cell
counter
P66
Cell
counter
P67
Cell
timer
P68a
Cell
counter
P68b
Cell
counter
P69a
Cell
counter
P69b
Cell
counter
ED
MCD
triggering event
description
Number of CS Paging
BSCGP
Number of PDCH dynamic
allocation requests
Number of PS Paging
PCCCH
Number of CS Paging
PCCCH
number of UL TBF
establishment requests
average number of PDCHs
dynamically allocated
number of DL TBF
Gb failure
number of UL TBF
Gb failure
time during which the
associated BVC is not
available
Number of successful DL
TBF establishments for MS
whose mulit-slot class allows
1 or 2 TS in DL
Number of successful DL
3 or 4 TS in DL
Number of successful UL
1 or 2 TS in UL
Number of successful UL
3 or 4 TS in UL
threshold
presence
tide-mark
presence
target
no
no
B6.2
no
no
B6.2
no
no
no
no
no
no
B6.2
SMG2
9
B6.2
SMG2
9
Pilot
no
no
P64
(max)
no
B6.2
no
no
B6.2
no
no
B6.2
no
no
B6.2
no
no
B6.2
no
no
B6.2
no
no
B6.2
Pilot
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Counters creation
Above counters are created following a cell creation. O&M handles periodic reading of counter
values according to granularity period.
Counters deletion
Above counters are deleted on cell deletion requested y O&M.
Counters periodic retrieval
O&M is responsible for periodic counter retrieval. After this retrieval counters are reset to zero
(except for gauge counters).
Notes : Telecom applications only compute telecom raw counters and send notification to O&M (at
object creation, deletion, modification). O&M step2 specification shall define counters actually visible
to the operator : (post processed counters, average counters, Resource availabilty and usage
counters which may be derived from telecom notification sent by telecom applications)
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6.
SYSTEM PARAMETERS
The system dimensioning parameters related to (RRM) layer are listed in section
described in 14.
and further
The timers and other system parameters managed at (RRM) layer are listed in sections and and
further described in 13: default value, min and max value, coding, parameter type.
Parameter:
Name of the parameter.
Role:
Definition of the parameter.
Instance:
Instanciation of the parameter: per cell, per GPU or per MFS.
Target:
Target phase for the parameter: GPRS demo, GPRS pilot or GPRS step 1.
6.1
System dimensioning parameters
Parameter
MAX_PDCH_GPU
MAX_PDCH_CELL
MAX_TBF_CELL
MAX_UL_TBF_SPDCH
MAX_UL_TBF_MPDCH
MAX_DL_TBF_SPDCH
MAX_DL_TBF_MPDCH
MAX_ADJ_CELL
MAX_MPDCH
Role
Defines the maximum number of PDCH per GPU that may be activated for GPRS traffic
Defines the maximum number of PDCH per cell that may be activated for GPRS traffic
Defines the maximum number of TBF per cell
Defines the maximum number of UL TBF per Slave PDCH
Defines the maximum number of UL TBF per Master PDCH
Defines the maximum number of DL TBF per Slave PDCH
Defines the maximum number of DL TBF per Master PDCH
Defines the cell maximum number of adjacent cells per cell
Defines the maximum number of PDCHs supporting the master PDCH
Instance
GPU
GPU
GPU
GPU
GPU
GPU
GPU
GPU
Cell
MAX_PDCH_GROUP
MAX_PDCH_HIGH_LOAD
Defines the maximum number of PDCHs allocated in a PDCH group

Defines the maximum number of PDCHs allocated in a PDCH group, when the BSC has
indicated a high load situation in the cell
Defines the maximum number of PDCHs allocated to a single TBF
Defines the minimum number of PDCHs supporting the master PDCH
PDCH-Gr
PDCH-Gr
Defines the minimum number of PDCHs allocated in a PDCH group

threshold, defining the number of PDCHs supported by a slave PDCH in one direction,
above which the MFS serves new TBF preferably by requesting additional resources to the
BSC
threshold, defining the number of PDCHs supported by a master PDCH in one direction,
above which the MFS serves new TBF preferably by requesting additional resources to the
BSC
PDCH-Gr
Cell
MAX_PDCH_PER_TBF
MIN_MPDCH
MIN_PDCH_GROUP
N_TBF_PER_PDCH
N_TBF_PER_MPDCH
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Cell
Cell
Cell
Target
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
B6.2
SMG29
pilot
pilot
pilot
B6.2
SMG29
pilot
pilot
B6.2
SMG29
6.2
Timers
Parameter
Role
wait indication used in PACKET ACCESS REJECT upon loss of radio resources
WI_PR
Instance
Cell
target
Demo
WI_PA
wait indication used in PACKET ACCESS REJECT while a PDCH Allocation procedure, at
expiry of timer T_ul_access_max
Cell
B6.2
T_flow_ctrl_ms
periodicity of emission of NM- FLOW-CONTROL-MS message to SGSN
MFS
B6.2
T_flow_ctrl_cell
periodicity of emission of NM- FLOW-CONTROL-BVC message to SGSN
MFS
B6.2
T_ul_assign_pccch
Cell
Pilot
Cell
Pilot
Cell
B6.2
SMG29
MFS
Demo
Cell
Pilot
Cell
B6.2
SMG29
MFS
Demo
Cell
Demo
MFS
Demo
MFS
Demo
MFS
Demo
MFS
Demo
Cell
Demo
Cell
Demo
cell
MFS
MFS
Pilot
Pilot
Pilot
MFS
Pilot
cell
B6.2
cell
B6.2
T_one_Block
Max_Pda_Lifetime
Timer used in the procedure 2 phase UL TBF establishment on PCCCH defining the
maximum time to be taken into account between the receipt of a Packet Channel Request
and the allocated radio block intended to convey the Packet Resource Request.
Timer used in the procedure 1 phase or 2 phase UL TBF establishment on CCCH
channel, defining the maximum transmission time of an uplink assignment message on
AGCH. (also used for DL TBF establishment on AGCH)
Timer used in the procedure 1 phase UL TBF establishment on CCCH or in the DL TBF
establishment procedure when using the AGCH, to delay the Packet UL/DL assignment
message, after having sent the Immediate Assignment message on AGCH and to delay
possible retransmissions
Timer defining the maximum time to wait for a MS answer (i.e. Packet Control Ack) to a
network sollicitation.
(this timer is necessary, because in case of GCH desynchronisation, the DSP will send no
response to RRM)
Timer used in the procedure DL TBF establishment on CCCH channel, defining the
maximum transmission tine of a downlink assignment on PCH.
Timer used in the procedure DL TBF establishment on PCH channel to delay the Packet
DL Assignment message, after having sent the Immediate Assignment message on PCH
and to delay possible retransmissions
Timer used in the procedure UL TBF abnormal release defining the maximum time the MS
is waiting for a Packet Uplink Ack/nack for resolution contention.
Values of MS timers T3166 and T3168 broadcast within system information
(PSI1-PSI13)
Timer used in the procedure UL TBF abnormal release : when the UL TBF is cut due to
radio link quality or loss of the MS, the TFI, associated USF(s) and TAI can not be
reallocated during T3169.
Timer used in the procedure UL TBF abnormal release : when the UL TBF is cut due to
continuous MS stalled TBF, the TFI, associated USF(s) and TAI can not be reallocated
during T3182n.
Timer used in the procedure DL TBF abnormal release : when the DL TBF is cut due to
radio link quality or loss of the MS, the TFI and TAI can not be reallocated during T3190n.
Timer used in the procedure Abnormal DL TBF release : the timer is used on the network
side to define when the current assignment is surely invalid on the MS side so that the TFI
and TAI can be reused.
Value of MS timer T3192 broadcast within system information
(PSI1-PSI13)
Timer used in the procedure DL TBF normal release : the MS remains during the MS timer
T3192 on assigned PDCHs after the DL TBF normal release. Then it returns to common
channels.
timeout value for periodic location updating in decihours
Timer giving the repetition rate to request PDCH allocation, towards the BSC
Internal timer to let the time to RLC/MAC to deactivate the master channel before sending
the UNMARK MASTER CHANNEL to the BSC.
Timer to monitor the acknowledgement of the first Flow-Control-BVC/MS
(only in Pilot)
This timer is activated when the last TBF of the PDCH is released.
At its expiry, if no new TBF has been established on this PDCH, it is deallocated
This timer is activated when the last TBF of the last PDCH is released (MIN_PDCH_Group
= 0)
At its expiry, if no new TBF has been established on this PDCH, it is deallocated
max. time during which a one block allocation is valid
Maximum of time a Packet DL assignment may be stored in a paging queue
MFS
MFS
T_ul_access_max
T_UL_CONGESTION
timer to limit UL TBF establishment

periodicity to release one TBF per cell, in the UL congestion process
B6.2
B6.2
SMG29
B6.2
B6.2
SMG29
T_ul_assign_ccch
(HMI name: T_GPRS_assign_agch)
T_assign_agch_pacch (*)
T_Ack_Wait
(previously T_ul_wait)
T_dl_assign_ccch
(HMI name: T_GPRS_assign_pch)
T_assign_pch_pacch (*)
T3166n
T3168
T3169
T3182n
T3190n
T3191
T3192
T3193
T3212
T_INITIAL_PDCH
T_MPDCH_Deact
T_BVC_Flow_Ack
T_PDCH_Inactivity
T_PDCH_Inactivity_Last
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
MFS
BSS
(*):
T_assign_pch_pacch and T_assign_agch_pacch are not managed by the OMC-R, they are
computed , by the MFS in the following way:
- T_assign_pch_pacch = T_DL_assign_ccch / (Max_GPRS_assign_pch_retrans + 1)
- T_assign_agch_pacch = T_UL_assign_ccch / (Max_GPRS_assign_agch_retrans + 1)
Timer values are rounded off to the upper value,according to timer granularity.
Timer values have to be equal or greater than 250 ms.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
6.3
Other parameters
Parameter
Role
Instance
target
Cell
BSS
B6.2
SMG29
B6.2
SMG29
B6.2
Cell
B6.2
Cell
B6.2
SMG29
Cell
B6.2
SMG29
Cell
B6.2
SMG29
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
COMMON PARAMETERS
NETWORK_CONTROL_ORDER1
PRIORITY_ACCESS_THRESHOLD
NMO
BS_CV_MAX
PAN_DEC
PAN_INC
PAN_MAX
determines whether the MS shall send measurement reports

(PSI13)
GPRS access policy
(PSI13)
Network Mode of Operation
(PSI1 - PSI13)
RLC countdown value
(PSI1 - PSI13)
value to be decremented from MS N3102 counter when PACKET UL ACK/NACK is not
received before MS timer T3182
(PSI1 - PSI13)
value to be incremented to MS N3102 counter when PACKET UL ACK/NACK is
received by MS
(PSI1 - PSI13)
maximum value allowed for counter N3102. Cell reselection is done by MS when
N3102 <= 0
(PSI1 - PSI13)
Cell
CONTROL CHANNEL DESCRIPTIONS

BS_PBCCH_BLKS
Number of blocks allocated to the PBCCH per 52 multiframe

(PSI1)
Number of blocks allocated to the PAGCH or PDTCH or PACCH per 52 multiframe
(PSI1)
Number of blocks allocated to the PRACH per 52 multiframe on each MPDCH
(PSI1)
maximum value allowed for the MS to request for non-DRX mode after packet transfer
mode
(PSI1 - PSI13)
BS_PAG_BLKS_RES
BS_PRACH_BLKS
DRX_TIMER_MAX
Cell
Cell
Cell
PRACH CONTROL
ACCESS_BURST_TYPE
RANDOM_ACC_RETRY
MAX_RETRANS_1
MAX_RETRANS_2
MAX_RETRANS_3
MAX_RETRANS_4
ACCESS_CONTROL_CLASS
TX_INT
S
PERSISTENCE_LEVEL_1
PERSISTENCE_LEVEL_2
PERSISTENCE_LEVEL_3
PERSISTENCE_LEVEL_4
ED
MCD
Format of the access burst sent by MS

(PSI1 - PSI13)
determines whether random access retry to another cell is allowed
(PSI3)
Maximum number of allowed retransmissions of access request with priority level 1
(PSI1)
(PSI1)
(PSI1)
(PSI1)
indicates whether access classes are barred or not
(PSI1)
Number of PRACH timeslots to spread transmission of PACKET CHANNEL REQUEST
(MS steered method)
(PSI1)
Number of slots between 2 successive PACKET CHANNEL REQUEST
(MS steered method)
(PSI1)
indicates the values of the access persistence level P(I) for radio priority 1
(PSI1)
(PSI1)
(PSI1)
(PSI1)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Cell
B6.2
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
Cell
Cell
Cell
Cell
Cell
Cell
Cell
B6.2
SMG29
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
Cell
Cell
Cell
Parameter
Role
Instance
target
Cell
B6.2 SMG29
GAMMA_TN0
power control parameter

(PSI1 - PSI13)
binary representation of the ch for MS output power control on timeslot 0
Cell
Demo
GAMMA_TN1
Cell
Demo
GAMMA_TN2
Cell
Demo
GAMMA_TN3
Cell
Demo
GAMMA_TN4
Cell
Demo
GAMMA_TN5
Cell
Demo
GAMMA_TN6
Cell
Demo
GAMMA_TN7
Cell
Demo
T_AVG_W
signal strength filter period for power control in packet idle mode
(PSI1 - PSI13)
signal strength filter period for power control in packet transfer mode
(PSI1 - PSI13)
power reduction value used by the BTS on PBCCH blocks, relative to the output power
used on BCCH
(PSI1)
determines whether the downlink measurements for power control shall be made on
BCCH or PDCH
(PSI1 - PSI13)
determines whether the MS shall perform interference measurements on other channels
(PSI1)
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
N_AVG_I
interfering signal strength filter constant for power control

(PSI1 - PSI13)
Cell
B6.2 SMG29
Flow_Dim_Safety_Factor
safety factor to determine BVC and MS DL flow control parameters, on the Gb interface
(Pilot only)
safety factor to determine BVC DL flow control parameters, on the Gb interface
safety factor to determine MS DL flow control parameters, on the Gb interface
maximum number of retries for the first FLOW-CONTROL-BVC/MS
(used only in Pilot)
flag to enable or disable the UL congestion procedure
flag to enable or disable the NSE capacity bandwidth reduction procedure
MFS
Pilot
MFS
MFS
MFS
B6.2
B6.2
Pilot
BSS
BSS
B6.2 SMG29
B6.2 SMG29
Cell
Demo
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
Cell
B6.2 SMG29
POWER CONTROL
ALPHA
T_AVG_T
Pb
PC_MEAS_CHAN
INT_MEAS_CHANNEL_LIST
_AVAIL
FLOW CONTROL
Flow_Dim_Safety_BVC
Flow_Dim_Safety_MS
Nb_BVC_Flow_Retry
EN_UL_CONGESTION
EN_CAP_REDUCTION
SERVING CELL SELECTION

RA_CODE
GPRS_RXLEV_ACCESS_MIN
GPRS_MS_TXPWR_MAX_CCH
GPRS_PRIORITY_CLASS
GPRS_HCS_THR
PSI1_REPEAT_PERIOD
ED
MCD
Routing Area Code

(PSI2 - PSI13)
Minimum received level at the MS required for access to the system
(PSI3)
Maximum TX power level an MS may use when accessing on a packet control channel
(PSI3)
(PSI3)
(PSI3)
PSI repeat period
(PSI1)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Parameter
Role
Instance
target
GENERAL CELL SELECTION

GPRS_CELL_RESELECT_HYSTER
ESIS
Additional hysteris which applies in Ready state for cells in same RA

(PSI3)
Cell
B6.2
SMG29
C31_HYST
determines whether the GPRS_RESELECT_HYSTERESIS shall be applied to the C31

criterion
(PSI3)
indicates an exception rule for GPRS_RESELECT_OFFSET
(PSI3)
Indicates in both STANDBY and READY state the additional hysteresis which applies
when selecting a cell in a new Routing Area.
(PSI3)
If the MS has performed an abnormal release with cell reselection from this
cell, the MS is not allowed to reselect this cell for T_RESEL seconds if
another cell is available.
(PSI3)
Cell
B6.2
SMG29
Cell
B6.2
SMG29
B6.2
SMG29
C32_QUAL
RA_RESELECT_HYSTERESIS
T_RESEL
Cell
Cell
B6.2
SMG29B6.
2m
Cell
B6.2
SMG29
B6.2
SMG29
NEIGHBOUR CELL PARAMETERS

BSIC
SAME_RA_AS_SERVING_CELL
GPRS_RXLEV_ACCESS_MIN
GPRS_MS_TXPWR_MAX_CCH
GPRS_PENALTY_TIME
GPRS_RESELECTION_OFFSET
GPRS_PRIORITY_CLASS
GPRS_HCS_THR
PSI1-REPEAT_PERIOD
Base Station Identity Code

(PSI3)
determines whether the neigbour cell Routing Area Code is the same as serving cell
RAC
(PSI3)
BasMinimum received level at the mobile station required for access to system
(PSI3)
maximum TX power a mobile station may use when accessing the system until
otherwise commanded
(PSI3)
negative offset used for MS cell reselection process
(PSI3)
time during which GPRS_TEMPORARY_OFFSET is active
(PSI3)
used by the MS to apply an offset and an hysteresis to the
(PSI3)
(PSI3)
(PSI3)
PSI repeat period
(PSI3)
Cell
Cell
Cell
Cell
Cell
Cell
Cell
Cell
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
PACKET CONNECTION CONTROL

TBF_INIT_CS
Initial coding scheme at UL or DL TBF establishment
Cell
Demo
EN_CS_ADAPTATION
Flag indicating whether or not the dynamic coding scheme adaptation is allowed or not
in the cell
maximum number of DL TBF establishment retries
(Max_retrans_DL is decremented each time the DL TBF establishment procedure is
undertaken from the beginning)
maximum number of attempts to send a Packet DL assignment, following a nonreception of the Packet Control Acknowledgement message, during a DL TBF
establishment on PCH
maximum number of attempts to send a Packet UL or DL assignment, following a nonreception of the Packet Control Acknowledgement message, during an UL or DL TBF
establishment on AGCH
Cell
Pilot
MFS
Pilot
Cell
B6.2
SMG29
Cell
B6.2
SMG29
Instance
target
allows/forbids the MS to apply IMSI attach and detach procedures

(PSI2)
allows/forbids new establishment causes for GSM phase 2 (PSI2)
Cell
In cases where TCHs hop on BCCH frequency, the power level measure is
not representative since no power control is applied on BCCH. This flag
make the MS exclude the measurement of the BCCH carrier
(PSI2)
indicates to the MS if it shall, may, or shall not use DTX for uplink
transmission
(PSI2)
number of SACCH blocks not received after which the MS shall consider
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
Max_Retrans_DL
Max_GPRS_assign_pc
h_retrans
Max_GPRS_assign_
agch_retrans
Parameter
Role
NON GPRS CELL OPTIONS

ATT
NECI
PWRC
DTX
Radio_link_timeout
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Cell
Cell
B6.2
SMG29
Cell
B6.2
BS_AG_BLKS_RES
CCCH_CONF
BS_PA_MFRMS
MAX_RETRANS
TX_INTEGER
MS_TX_PWR_MAX_CCCH
ED
MCD
SMG29
the link as lost

(PSI2)
number of blocks reserved for access grant
(PSI2)
physical channel configuration for CCCH
Cell
Cell
number of 51-multiframes between transmission of paging messages on a

paging group
(PSI2)
maximum number of retransmission of channel request
(PSI2)
number of slots to spread transmission of channel request
(PSI2)
Cell
Maximum Tx power level to access the system on CCCH

(PSI2)
Cell
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Cell
Cell
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
B6.2
SMG29
7.
ANNEX 1
Structures length are described in Annex 1.

One radio block is supposed to limited to 22 bytes.
PSI3 header
The header length needs to be added in order to compare the structure sizes and the possibility of
putting them in one PSI3 or PSI3bis instance.
The PSI3 header length is 44 bits.
The PSI3bis header length is 12 bits.
Structure delimitation bits (PSI3bis)
In the PSI3bis, 1 start bit (value: 1) precedes any instance of any structure; 1 bit ends the set of
instances of each structure type.
Structure 1
In one type 1 structure, there may be:
SFmax (indefinite) start frequencies,
n neighbour cells, where n 17

The structure 1 length, for one START_FREQUENCY, is given by SL1:
SL1 64 54 n1 22 n 2 , n1+n2 + 1=n17

where n1 is the number of described neighbour cells for which every optionnal parameter is present
in the Cell selection params structure, n2 is the number described neighbour cells for which every
optionnal parameter is omitted in the Cell selection params structure.
The structure needs to be repeated as many times as there are START_FREQUENCies:
SL1
SFmax
64 54 n1SFi 22 n2SFi
SFi
where n1SFi is the number of described neighbour cells with START FREQUENCY i for which every
optionnal parameter is present in the Cell selection params structure, n2 is the number described
neighbour cells with START FREQUENCY i for which every optionnal parameter is omitted in the
Cell selection params structure.
Note: these calculations assume that the optionnal cell selection parameters are present, HCS
structure is included.
Structure 2
In one type 2 structure, there may be:
SFmax (indefinite) start frequencies,
maxCPP (4) Cell Parameters Pointers, ie maxCPP set of parameters, among which
nCPP_all sets contain all parameters, nCPP_man sets contain only the mandatory
parameters
one set of parameters is adressed by CPPi is related to type_i cells,
n_i cells of type_i share the same set of parameters, where n_i16
One structure 2 has the following lenght:
SL2 =
SF max
max CPP
startfrequ ency
1CPPi 4
20 3 13n _ i 2 1
42 nCPP _ all 20 nCPP _ man 1 2
(3) shall be removed if n_i is null.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
In case of SFmax Start Frequencies and only one set of parameters, for each Start Frequency n_j
neighbour cells have the same set of parameters, then one structure 2 has the following lenght:
SF max
SL2 =
23 13 n _ j 3 1 3 42
SFj
In case of 1 Start Frequency, and maxCPP set of parameters, the CSN1 coding enforces the
repetition of the (Start Frequency Same_RA_as_Serving_cell, Cell_Bar_access BCC
NR_of_Remaining_cells Freq_diff_length) IE, which are 23bits long; then the structure 2 has the
following lenght:
max CPP
SL2 =
23 13 n _ i 3 42 max CPP 3
i 1
The 42 length of the parameters set structure assumes that all the optional parameters are present
except SI13_PBCCH_LOCATION. When they are omitted (provided the value is the same as the
previous declared one), the length of the parameters set may be reduced to 20.
Note: the result of START_FREQUENCY + Frequency_Diff shall be regarded as relative to 1024
modulus (GSM frequencies range is 0-124 and DCS1800 frequencies is 512-885)
Note: we may have different NCC values (external cells may be declared as neighbour cells).
Open point 1: the coding of Cell_Bar_Access_2 (1 bit) shall be clarified on ETSI side.
Examples of lenght in PSI3 bis neighbour cells structures:
1 single cell in a structure:
SL1 64
SL2 = 1 20 2 1 42 1 2 = 69
Then, in a PSI3bis there remain 164 for structure 1 or 2. If each cell is represented in one structure,
there may be 2 structures per PSI3bis, each one defining one whole set of parameters.
2 cells have the same set of parameters :
SL1 64 22 n 2 SF max , n2 =1 if they have the same Start frequency,
2 SL1 64 2 otherwise (because each Start frequency need one type 1 structure)
If one Start frequency is used, then
SL2 = 1 23 13 2 1 42 1 2 ,
If 2 Start frequencies are used, then
SL2 = 1 20 2 1 2 42 1 2 ,
Number of Start frequencies
1
2
ED
MCD
structure 1
86
128
structure 2
85
93
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
2 cells have completly different sets of parameters :
SL1
SFmax
64 54 n1SFi
SFi
SL2 = 1 20 2 1 2 42 2 1 2
Indeed, if 1 Start frequency is used it shall be repeated with Same_RA_as_Serving_cell,
Cell_Bar_access BCC NR_of_Remaining_cells Freq_diff_length Ies, because of the CSN1 coding.
1
2
structure 1
118
128
structure 2
135
135
3 cells have the same set of parameters
SL1
SFmax
64 22 n2SFi
SFi

SL1 64 22 2
SL1 64 22 64
SL1 64 3
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj

SL2 = 23 13 2 3 1 3 42 ,
SL2 = 23 13 1 3 1 20 3 1 3 42 ,
SL2 = 20 3 1 3 3 42 ,
1
2
3
ED
MCD
structure 1
108
150
192 (NA)
structure 2
98
109
117
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Note: the figures show that some combinations can not be coded with structure 1 in one PSI3bis
message; their length is set to Not Applicable (NA).
2 cells have the same set of parameters and one cell has a different set
SL1
SFmax
SFi

SL1 64 54 1 22 1 =140
SL1 64 54 64 =182 or SL1 64 22 64 = 150
SL1 64 3 = 192
If one Start frequency is used or the 2 cells sharing the same parameters, then
SF max
SL2 =
20 3 13 n _ j 3 1 3 2 42 = 23 13 1 3 1 20 3 1 3 2 42
SFj
= 153
If Start frequencies are different for the 2 cells sharing the same parameters, then
SF max
SL2 =
20 3 13 n _ j 3 1 3 2 42 = 20 3 1 3 3 2 42 = 161
SFj

1
2
3
ED
MCD
structure 1
140
182 (NA) or 150
192 (NA)
structure 2
153
153 or 161 (NA)
161 (NA)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3 cells have different sets of parameters
SL1
SFmax
64 22 n2SFi
SFi

SL1 64 54 2 = 172, 2 PSI3bis are needed
If 2 Start frequencies are used, then 2 type 1 structures are needed,
SL1 64 54 64 182 , 2 PSI3bis are needed
If 3 Start frequencies are used, then 3 type 1 structures are needed
SL1 64 3 192 , 2 PSI3bis are needed
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj
3 Start frequencies are used (the same one needs to be repeated), then
SL2 = 20 3 1 3 3 3 42 = 201,
1
2
3
ED
MCD
structure 1
172 (NA)
182 (NA)
192 (NA)
structure 2
201 (NA)
201 (NA)
201 (NA)
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
SL1
SFmax
64 22 n2SFi
SFi

SL1 64 22 3 = 130
SL1 64 22 2 =172
SL1 64 22 64 2 = 214
SL1 64 4 = 256
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj

SL2 = 23 13 3 3 1 3 42 = 111
SL2 = 23 13 3 1 23 13 3 1 3 42 = 125
or SL2 =
23 13 2 3 1 20 3 1 3 42 = 122,

SL2 = 23 13 3 1 20 3 1 2 3 42 = 133
SL2 = 20 3 1 4 3 42 = 141
1
2
3
4
ED
MCD
structure 1
130
172 (NA)
214 (NA)
256 (NA)
structure 2
111
125 or 122
133
141
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
3 cells have the same set of parameters, one has another
SL1
SFmax
SFi

SL1 64 22 2 54 = 162 which is too long to be included in one PSI3bis message. 2, 3 or 4
Start frequencies will also induce too long structures to be included in one PSI3bis message.
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj
2 parameters sets are used so 2 at least 2 Start frequencies are used (in case of one it needs to be
repeated), then:
SL2 = 23 13 2 3 1 20 3 1 3 42 2 = 164 which is too long to be included in one
PSI3bis message. 2, 3 or 4 Start frequencies will also induce too long structures to be included in
one PSI3bis message.
1
2
3
4
ED
MCD
structure 1
162 (NA)
NA
NA
NA
structure 2
164 (NA)
164 (NA)
NA
NA
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
Such a combination is not possible in a single PSI3 or PSI3bis instance. However, optimization may
be performed by the omission of optional fields.
SL1
SFmax
64 22 n2SFi
SFi

SL1 64 22 4 = 152
If more than one Start frequency is used, then one instance of PSI3bis is too short.
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj

SL2 = 23 13 4 3 1 3 42 = 124
SL2 = 23 13 2 3 1 23 13 3 1 3 42 = 138
or SL2 =
23 13 3 3 1 20 3 1 3 42 = 135,

SL2 = 23 13 2 3 1 20 3 1 2 3 42 = 146
or SL2 =
23 13 3 1 2 20 3 1 3 42 = 149

SL2 = 20 3 1 3 3 42 23 13 3 1 = 157
1
2
3
4
5
ED
MCD
structure 1
152
NA
NA
NA
NA
structure 2
124
138 or 135
149 or 146
157
NA
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
SL1
SFmax
64 22 n2SFi
SFi

SL1 64 22 5 = 174
One instance of PSI3bis is too short.
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj

SL2 = 23 13 5 3 1 3 42 = 137
SL2 = 23 13 2 3 1 23 13 2 3 1 3 42 = 151
or SL2 =
23 13 4 3 1 20 3 1 3 42 = 148,

SL2 = 23 13 3 3 1 20 3 1 2 3 42 = 159 which is the best configuration in this
case and may be put in 1 PSI3bis instance
or SL2 = 23 13 2 3 1 23 13 3 1 20 3 1 3 42 = 162
which needs more than 1 PSI3bis instance.
or SL2 = 23 13 3 1 3 3 42 = 165
which needs more than 1 PSI3bis instance
If more Start frequencies are used, more than 1 PSI3bis instance is needed.
1
2
3
4
5
6
ED
MCD
structure 1
174 (NA)
NA
NA
NA
NA
NA
structure 2
137
151 or 148
159 or 162(NA) or 165 (NA)
NA
NA
NA
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
One instance of PSI3bis is too short for structure 1.
SF max
SL2 =
23 13 n _ j 3 1 3 42 ,
SFj

SL2 = 23 13 6 3 1 3 42 = 150
SL2 = 23 13 5 3 1 20 3 1 3 42 = 161, which is the best configuration in this case
but needs more than 1 PSI3bis instance.
SL2 = 23 13 4 3 1 20 3 1 2 3 42 = 166 which is the best configuration in this
case but needs more than 1 PSI3bis instance.
If more Start frequencies are used, more than 1 PSI3bis instance is needed.
structure 1
structure 2
1
NA
150
2
NA
161 (NA)
3
NA
NA
4
NA
NA
5
NA
NA
6
NA
NA
7
NA
NA
As a conclusion, the structure 2 enables to include 7 similar cells in one instance of PSI3bis whereas
the structure 2 only enables to include 5 similar cells.
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
8.
GLOSSARY
Bns
Bs
BSCGP
BSS
BSSGP
BVC
BVCI
CBQ
CS
CS-n
DL
DRX
EAP
FSM
GIC
GPRS
HCS
IE
LLC
LME
MA
MAC
MFS
MM
MPDCH
MS
MSG
NMO
NTM
PACCH
PAG
PAGCH
PBCCH
PCC
PCCH
PCM
PDCH
PDN
PDP
PDTCH
PDU
PM
PPCH
PRACH
PRH
PS
PTP
ED
MCD
BSCGP not supported

BSCGP supported
Base Station Controller GPRS Protocol
Base Station System
Base Station System GPRS Protocol
BSSGP Virtual Connection
BVC Identifier
Cell Barr Qualify
Circuit Switched
Coding Scheme 1 to 4
DownLink
Discontinuous reception
Entity Access Point
Finite State Machine
GPRS Identifier Circuit
General Packet Radio Service
Hierarchical Cell Structure
Information Element
Logical Link Control
Layer Management Entity
Mobile Allocation
Medium Access Control
Multi-BSS Fast packet Server
Mobility Management
Master PDCH : PDCH carrying PCCCH channels
Mobile Station
Message
Network Mode Operation
Network Management Entity
Packet associated control channel
Paging entity
Packet Access Grant Channel
Packet Broadcast Control Channel
Packet connection control entity
Packet Control Common Channel
Pulse Code Modulation
Packet Data Channel
Packet Data Network
Packet Data Protocol
Packet Data Traffic Channel
Protocol Data Unit
Performance Monitoring
Packet Paging Channel
Packet Radio Access Channel
Packet Radio Resource Handling entity
Packet Switched
Point to Point
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA
PTM
QoS
RLC
RRM
SAP
SGSN
SYC
TA
TAI
TBF
TFI
TLLI
TRN
UL
USF
USFNE
Point to Multipoint
Quality of Service
Radio Link Control
Radio Resource Management Layer
Service Access Point
Serving GPRS Support Node
Systeme Choice
Timing Advance
Timing Advance Index
Temporary Block Flow
Temporary Flow Identifier
Temporary Logical Link Identity
Transport entity
UpLink
Uplink State Flag
USF No emission used to schedule UL signalling of TBF without USF.
END OF DOCUMENT
ED
MCD
04 Released
267129603.doc
10/08/2000
3BK 11202 0265 DSZZA

ALU GPRS Radio Resource Management

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ALU GPRS Radio Resource Management

Încărcat de

Drepturi de autor:

Formate disponibile

d o c u m e n t, u s e a n d c o m m u n ic a tio n o f its c o n te n ts

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

MOBILE COMMUNICATION DIVISION

PREDISTRIBUTION: DOC. CENTRES

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

Working meeting minutes : see TD/SAS/bla/80775.98

Radio Resource algorithm, PCC & PAG & PRH FSM, Gb

Document updated for GPRS pilot & step 1.

Document updated after review, see minutes in

Document updated after review, see minutes in

Document updated after review, see minutes in TD/SYT/JPJ/90355

Document updated for B6.2 SMG29 BSS :

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

INTERNAL REFERENCED DOCUMENTS

3BK 10204 0438 DTZZA

TFD: General Packet Radio Service

FOR INTERNAL USE ONLY

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

SYSTEM FUNCTIONAL BLOCKS

3BK 11202 0265 DSZZA

1. OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER......................................

1.2 Overview description of layer services.....................................................................................

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

1.1 Layer location..............................................................................................................................

1.3 Overview description of layer protocol.....................................................................................

2. PROTOCOL LAYER STRUCTURE...........................................................................

3. SERVICE PRIMITIVES DEFINITION.........................................................................

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

4. DEFINITION OF LAYER PROTOCOL.......................................................................

5. LAYER DYNAMIC MODEL........................................................................................

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

5.1.1.11 DL TBF Release initiated by (RLC)...............................................................................

3BK 11202 0265 DSZZA

5.4 TRN Entity detailed description.................................................................................................

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

5.5 PRH Entity detailed description.................................................................................................

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

53 BSS LOCK SCENARIO.......................................................................................................

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

Ed. 01 Document creation for GPRS Demonstrator

3BK 11202 0256 DSZZA

FBS GPRS telecom presentation

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

Digital cellular telecommunications system (Phase2+)

The applicable versions of ETSI Technical Specifications are defined in [15].

GPRS Radio Resource Allocation Part III : Comparison of

3BK 11202 0265 DSZZA

n o t p e r m itte d w ith o u t w r itte n a u th o r iz a tio n f r o m A lc a te l.

3BK 11202 0265 DSZZA