alu gprs radio resource management

GPRS Radio Interface RRM sublayer

SiteVELIZYMOBILE COMMUNICATION DIVISION

Originator(s)

SYTGPRS Radio Interface

RRM sub-layer

Domain:Alcatel 900/BSS

Division:PRODUCT DEFINITION

Rubric:SYS-TLA

Type:SYSTEM FUNCTIONAL BLOCKS

Distribution Codes

Internal :

External :

PREDISTRIBUTION:

MCD/TD Vlizy:L. CruchantP. DupuyR. Bialobroda (BTS)

JY AmaudrutS. BaudetM. Delprat (BTS)

S.BourdeautJ. GuinandJP Humeau (BTS)

E. DesorbayT. Donzel (CNS)B. De Jaeger

R. ForniM. Freynet (CNS)P. Godin

PJ PietriG. Linden (CNS)

M. Wu

MCD/TD Kontich:G. Van DijckJL CarpentierY. Vereecke

MCD/TD Kaisemer:R. Goedecker

MCD/TD Zuffenhausen:

PREDISTRIBUTION: DOC. CENTRES

MCD VELIZYMCD STUTTGARTMCD ANTWERP

B. Marliac

I. Lentzsch

L. Van Eyck

ABSTRACT

This document describes the RRM protocol between the MFS and the MS, for GPRS B6.2.

Approvals

Name

App.

D.Berthoumieux

AMM. Bialobroda

CNS

Name

App.

REVIEWNot applicable

HISTORY

Ed.01

In Preparation 0115/04/98Document creation

Ed.01

In Preparation 0228/05/98Working meeting minutes : see TD/SAS/bla/80775.98

Ed.01

In Preparation 03 29/07/98Radio Resource algorithm, PCC & PAG & PRH FSM, Gb congestion control are specified.

Working meeting minutes : see TD/ST/bla/80949.98

Ed.01

Proposal 01 24/08/98Remarks 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

Ed.01

Proposal 02 21/09/98Remarks 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

Ed. 01

Proposal 0309/10/98Remarks of last review meeting are taken into account.

Ed. 02

Proposal 0121/10/98Document updated for GPRS pilot & step 1.

Ed. 02

Proposal 02xx/11/98Document updated after review, see minutes in TD/SYT/JPJ/81113.98

Ed. 02

Proposal 0311/12/98Document updated after review, see minutes in TD/SYT/JPJ/81195

Ed. 02

Proposal 0415/01/99Document updated after review, see minutes in TD/SYT/JPJ/81250. Aligned on BSCGP specification, ed.2 proposal 03.

Ed. 02

Proposal 0431/05/99Document updated after review, see minutes in TD/SYT/JPJ/90159

Ed.02

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

Ed.03

Proposal 0125/06/99Document updated for B6.2 SMG29 BSS :

- Support of the Master PDCH feature

- Uplink congestion control

- Bandwidth capacity reduction

- SMG#29 impacts

Ed.03

Proposal 0209/07/99- 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

Ed.03 Released10/08/00Document updated after review, see minutes in TD/SYT/SBO/90460

Ed 04 Proposal 0101/12/99The following CRs are taken into account:

- 057386

- 057672

- 057929

- 058457

- 059220

- 059616

- 061866

- 062827

- 062852

- 064475

- 065474

- 066001

INTERNAL REFERENCED DOCUMENTS[i1]3BK 10204 0438 DTZZATFD: General Packet Radio Service

[i2]3BK 10204 0433 DTZZATFD: Multi-BSS Fast packet Server

[i3]3BK 10204 0467 DTZZAGPRS BSS technical feature list

FOR INTERNAL USE ONLYBy 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 DOCUMENTSYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS1HISTORY8

REFERENCED DOCUMENTS8

RELATED DOCUMENTS9

PREFACE10

10

1. OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER

1.1 Layer location10

1.2 Overview description of layer services11

1.2.1 Services provided by (RRM) layer11

1.2.2 Services required from (RLC) layer11

1.2.3 Services required from (BSCGP) layer11

1.2.4 Services required from (BSSGP) layer11

1.3 Overview description of layer protocol12

1.3.1 Layer procedures12

1.3.2 GPRS multiplexing principles13

1.3.2.1 Temporary Block Flow13

1.3.2.2 Temporary Flow Identity13

1.3.2.3 Medium access modes13

1.3.3 Master PDCH13

1.3.4 GPRS MS behaviour15

1.3.4.1 MS class mode of operation15

1.3.4.2 Network modes of operation15

1.3.4.3 System information reading16

1.3.4.4 Cell reselection17

1.3.4.5 MS Radio Resource state18

1.3.4.6 Channels listened by the MS20

1.3.4.7 GPRS traffic interruption, in a cell21

1.3.4.8 GPRS access in the cell and Overload control22

1.3.5 Quality of Service Management23

1.3.5.1 QoS parameters23

1.3.5.2 BSS behaviour related to QoS in B6.224

2. PROTOCOL LAYER STRUCTURE27

2.1 Overview of layer functional model27

2.2 Overview of layer interfaces28

3. SERVICE PRIMITIVES DEFINITION29

3.1 Primitives provided to Layer Management Plane29

3.2 List of service primitives used by the layer30

3.2.1 Service primitives used from (RLC) layer30

3.2.2 Service Primitives used from (BSSGP) layer32

3.2.3 Service Primitives used from (BSCGP) layer33

3.3 Detailed description of service primitives provided by the layer34

3.3.1 Service primitives provided to Layer Management entity34

3.3.1.1 LM-BSS-CREATE-req34

3.3.1.2 LM-BSS-CREATE-cnf34

3.3.1.3 LM-BSS-DELETE-req34

3.3.1.4 LM-BSS-DELETE-cnf34

3.3.1.5 LM-BSS-GET-req35

3.3.1.6 LM-BSS-GET-cnf35

3.3.1.7 LM-BSS-STATE-CHANGE-ind35

3.3.1.8 LM-BSS-SET-req36

3.3.1.9 LM-BSS-SET-cnf36

3.3.1.10 LM-CELL-CREATE-req37

3.3.1.11 LM-CELL-CREATE-cnf38

3.3.1.12 LM-CELL-DELETE-req38

3.3.1.13 LM-CELL-DELETE-cnf38

3.3.1.14 LM-CELL-SET-req39

3.3.1.15 LM-CELL-SET-cnf40

3.3.1.16 LM-CELL-GET-req41

3.3.1.17 LM-CELL-GET-cnf41

3.3.1.18 LM-CELL-State-Change-ind41

3.3.1.19 LM-GIC-Group-CREATE-req42

3.3.1.20 LM-GIC-Group-CREATE-cnf43

3.3.1.21 LM-GIC-Group-DELETE-req43

3.3.1.22 LM-GIC-Group-DELETE-cnf43

3.3.1.23 LM-GIC-Group-GET-req43

3.3.1.24 LM-GIC-Group-GET-cnf44

3.3.1.25 LM-GIC-Group-State-Change-ind44

4. DEFINITION OF LAYER PROTOCOL45

4.1 Peer to peer protocol description45

4.1.1 Protocol definition45

4.1.2 Packet connection control46

4.1.2.1 One phase access UL TBF establishment initiated by MS in packet idle mode on PCCCH46

4.1.2.2 One phase access UL TBF establishment initiated by MS in packet idle mode on CCCH47

4.1.2.3 Two phase access UL TBF establishment initiated by MS in packet idle on PCCCH49

4.1.2.4 Two phase access UL TBF establishment initiated by MS in packet idle on CCCH51

4.1.2.5 UL TBF establishment initiated by MS in packet transfer mode53

4.1.2.6 UL TBF resources modification initiated by MS55

4.1.2.7 DL TBF establishment initiated by network for MS in packet idle mode on PCCCH56

4.1.2.8 DL TBF establishment initiated by network for MS in packet idle mode on CCCH57

4.1.2.9 DL TBF establishment initiated by network for MS in packet transfer mode58

4.1.3 Paging61

4.1.3.1 PS or CS Paging procedure for MS in packet idle mode when there is a MPDCH61

4.1.3.2 PS or CS Paging procedure for MS in packet idle mode when there is no MPDCH61

4.1.3.3 CS Paging procedure for MS in packet transfer mode61

4.1.4 Packet radio resource handling63

4.1.4.1 Packet PDCH Release63

4.1.4.2 Packet System Information provisioning (B6.2 SMG29)63

4.2 PDU definition64

4.2.1 PDU description64

4.2.2 Information Element description64

4.3 Protocol error handling64

5. LAYER DYNAMIC MODEL65

5.1 Inter-entities communication65

5.1.1 Packet connection control65

5.1.1.1 One phase access UL TBF establishment on CCCH65

5.1.1.2 One phase access UL TBF establishment on PCCCH or PACCH68

5.1.1.3 2 phase access UL TBF establishment on CCCH70

5.1.1.4 2 phase access UL TBF establishment on PCCCH72

5.1.1.5 DL TBF establishment on CCCH73

5.1.1.6 DL TBF establishment on PCCCH/PACCH75

5.1.1.7 One phase access contention resolution77

5.1.1.8 Coding scheme adaptation notification77

5.1.1.9 DL TBF Release initiated by (RRM) PRH78

5.1.1.10 UL TBF Release initiated by (RRM) PRH79

5.1.1.11 DL TBF Release initiated by (RLC)79

5.1.1.12 UL TBF Release initiated by (RLC)80

5.1.2 Packet radio resource handling81

5.1.2.1 PDCH dynamic allocation81

5.1.2.2 PDCH dynamic deallocation82

5.1.2.3 MPDCH dynamic allocation (B6.2 SMG29)83

5.1.2.4 MPDCH dynamic deallocation (B6.2 SMG29)84

5.1.2.5 PDCH establishment85

5.1.2.6 PDCH release85

5.1.3 Data transfer86

5.1.3.1 DL LLC PDU transfer86

5.1.3.2 Receipt of an invalid DL LLC PDU87

5.1.3.3 DL LLC PDU deletion87

5.1.3.4 DL TBF flow control with RLC87

5.1.3.5 DL TBF termination notification88

5.1.3.6 DL LLC transfer with RLC mode modification89

5.1.3.7 UL LLC PDU transfer90

5.1.3.8 Flush procedure91

5.1.3.9 MS Flow Control procedure (not in Pilot)91

5.1.3.10 BVC Flow Control procedure92

5.1.4 CS or PS Paging92

5.1.5 Network Management93

5.1.5.1 BSS creation93

5.1.5.2 BSS lock94

5.1.5.3 BVC-SIG failure/recovery95

5.1.5.4 Cell creation96

5.1.5.5 Cell unlock97

5.1.5.6 Cell lock100

5.1.5.7 Gb failure/recovery103

5.1.5.8 Unavailability notification from BSC104

5.1.5.9 LAC/CI modification107

5.1.5.10 BSS reset112

5.1.5.11 Cell RESET114

5.1.5.12 No response from the BSC114

5.2 PAG Entity detailed description116

5.2.1 CS Paging116

5.2.2 PS Paging118

5.2.3 Activation / Deactivation of the MPDCH119

5.3 PCC Entity detailed description120

5.3.1 Packet connection establishment123

5.3.1.1 UL packet connection establishment123

Request type126

RLC mode126

5.3.1.2 DL packet connection establishment137

5.3.1.3 Activation / Deactivation of the MPDCH144

5.3.2 Packet connection modification146

5.3.2.1 MS requested modification of UL TBF146

5.3.2.2 Network decided coding scheme adaptation147

5.3.2.3 TLLI notification by RLCError! Bookmark not defined.

5.3.2.4 TLLI modification by SGSNError! Bookmark not defined.

5.3.2.5 DL TBF modification147

5.3.3 Packet connection release148

5.3.4 SDL diagrams154

5.3.4.1 Downlink154

5.3.4.2 Uplink180

5.4 TRN Entity detailed description195

5.4.1 DL LLC PDU transfer195

5.4.1.1 DL Packet connection control195

5.4.1.2 DL PDU storage195

5.4.1.3 DL LLC PDU lifetime expiry195

5.4.1.4 DL LLC PDU Flush195

5.4.1.5 DL congestion control196

5.4.2 UL LLC PDU transfer202

5.5 PRH Entity detailed description203

5.5.1 Packet System Information management (B6.2 SMG29)203

5.5.1.1 Broadcast of GPRS System Information on BCCH203

5.5.1.2 Broadcast of Packet System Information on PBCCH203

5.5.1.3 Broadcast of Packet System Information on PACCH235

5.5.2 Packet radio resources management244

5.5.2.1 Packet radio resources allocation245

5.5.3 PDCH resource control255

5.5.3.1 Inputs of reservation algorithm256

5.5.3.2 Initial PDCH allocation260

5.5.3.3 Reservation of 1 UL block261

5.5.3.4 Reservation of multiple blocks with dynamic PDCH allocation262

5.5.3.5 Examples of reservation of multiple blocks269

5.5.3.6 Allocation request procedure275

5.5.3.7 Dynamic deallocation275

5.5.3.8 Multi requests handling (B6.2 SMG29)279

5.5.3.9 Allocation / Deallocation of the MPDCH284

5.5.4 UL congestion control284

5.5.5 NSE capacity bandwidth adaptation285

5.6 NTM Entity detailed description285

5.6.1 Functions description285

5.6.1.1 Managed entities285

5.6.1.2 Performance Monitoring292

6. SYSTEM PARAMETERS296

6.1 System dimensioning parameters296

6.2 Timers297

6.3 Other parameters299

7. ANNEX 1Error! Bookmark not defined.

8. GLOSSARY311

TABLE OF FIGURES

10

Figure 1 : RRM layer location

Figure 2 : Quality of service levels23

Figure 3 RRM interfaces28

Figure 4 : 1 Phase access UL TBF establishment by MS in packet idle mode on PCCCH46

Figure 5 : 1 Phase access UL TBF establishment by MS in packet idle mode on CCCH47

Figure 6 : 2 Phase access UL TBF establishment by MS in packet idle mode on PCCCH49

Figure 7 : 2 Phase access UL TBF establishment by MS in packet idle mode on CCCH51

Figure 8 : UL TBF establishment by MS in packet transfer mode53

Figure 9 : UL TBF resources modification by MS55

Figure 10 : DL TBF establishment for MS in packet idle mode on PCCCH56

Figure 11 : DL TBF establishment for MS in packet idle mode on CCCH57

Figure 12 : DL TBF establishment for MS in packet transfer mode58

Figure 13 : PS or CS Paging for MS in packet idle mode in cell with MPDCH61

Figure 14 : PS or CS Paging for MS in packet idle mode in cell without MPDCH61

Figure 15 : CS Paging for MS in packet transfer mode61

Figure 16 : Packet PDCH release procedure63

Figure 17 : Packet System Information broadcast procedure63

Figure 18 : One Phase access UL TBF establishment on CCCH - nominal scenario66

Figure 19 : One Phase access UL TBF establishment on CCCH - error scenario67

Figure 20 : One Phase access UL TBF establishment on PCCCH/PACCH - nominal scenario68

Figure 21 : One Phase access UL TBF establishment on PCCCH/PACCH - error scenario69

Figure 22 : 2 Phase access UL TBF establishment on CCCH nominal scenario70

Figure 23 : 2 Phase access UL TBF establishment on PCCCH nominal scenario72

Figure 24 : DL TBF establishment on CCCH nominal scenario73

Figure 25 : DL TBF establishment on PCCCH/PACCH nominal scenario75

Figure 26 : One Phase access contention resolution scenario77

Figure 27 : Coding scheme adaptation notification77

Figure 28 : DL TBF release scenario initiated by (RRM) PRH78

Figure 29 : UL TBF release scenario initiated by (RRM) PRH79

Figure 30 : DL TBF release scenario initiated by (RLC)79

Figure 31 : UL TBF release scenario initiated by (RLC)80

Figure 32 : PDCH dynamic allocation scenario, successful case81

Figure 33: PDCH dynamic allocation scenario, unsuccessful case81

Figure 34 : PDCH dynamic deallocation scenario, successful case82

Figure 35: PDCH dynamic deallocation scenario, unsuccessful case82

Figure 36 : MPDCH dynamic allocation scenario83

Figure 37 : MPDCH dynamic deallocation scenario84

Figure 38 : PDCH establishment scenario85

Figure 39 : PDCH release scenario85

Figure 40 : DL LLC PDU transfer scenario86

Figure 41 : Receipt of an invalid DL LLC PDU scenario87

Figure 42 : DL LLC PDU deletion scenario87

Figure 43 : DL TBF flow control with RLC scenario87

Figure 44 : DL TBF termination scenario88

Figure 45 RLC mode modification (current mode is unacknowledged mode)89

Figure 46 RLC mode modification (current mode is acknowledged mode)90

Figure 47 : UL LLC PDU transfer scenario90

Figure 48 : Flush scenario91

Figure 49 : MS flow control scenario91

Figure 50 : BVC flow control scenario92

Figure 51 : CS or PS paging scenario92

Figure 52 BSS creation scenario (administrative state = locked)93

Figure 53 BSS lock scenario94

Figure 54 Cell creation scenario (administrative state = locked)96

Figure 55 Cell unlock scenario (MPDCH supported)97

Figure 56 Cell unlock scenario (MPDCH not supported)99

Figure 57 Cell lock scenario (MPDCH supported)100

Figure 58 Cell lock scenario (MPDCH not supported)102

Figure 59 Gb failure/recovery scenario103

Figure 60 BSC unavailability notification scenario (with MPDCH)104

Figure 61 BSC unavailability notification scenario (without MPDCH)106

Figure 62 LAC/CI modification scenario (with MPDCH)108

Figure 63LAC/CI modification scenario (without MPDCH)110

Figure 64 BSS Reset scenario113

Figure 65 Cell Reset scenario114

Figure 66 BSC no-response scenario115

Figure 67 : Gb congestion control at SGSN (1/2)196

Figure 68 : Gb congestion control at SGSN (2/2)197

Figure 69 Frequency of sending BVC_FLOW_CONTROL PDU198

Figure 70 Frequency of sending MS_FLOW_CONTROL PDU199

Figure 71 Neighbour cell parameters structure216

Figure 72 PSI handling interface (with MPDCH)220

Figure 74 ACC_CONTR_CLASS (PSI1) and CELL_BAR_ACCESS2 (PSI3) processing225

Figure 75 MPDCH activation (at cell activation, BSCGP supported)231

Figure 76 MPDCH activation (at NMO modification)232

Figure 77 MPDCH deactivation (at cell deactivation)233

Figure 78 MPDCH deactivation (at NMO modification)234

Figure 79 PSI handling interface (without a MPDCH)238

Figure 80 SI13/PSI13 synchronisation240

Figure 81 SI13/PSI13 synchronisation (MS in Packet transfer mode)240

Figure 82: Example of allocated PDCHs257

Figure 83: Example of initial PDCH allocation260

Figure 84: Parameters calculated for dynamic allocation264

Figure 85: Queuing of downlink request267

Figure 86: MFS decision process for GPRS assignment268

Figure 87 Dynamic Deallocation276

Figure 88: Example of "soft" pre-emption decision278

Figure 89 Entity relationship diagram286

Figure 90 BSS/CELL state relationship290

HISTORY

Ed. 01Document creation for GPRS Demonstrator

Ed. 02Document updated for GPRS Pilot and BSS SMG28 BSS

Ed. 03 Document updated for BSS SMG29 BSS

REFERENCED DOCUMENTS

Alcatel references[1]3BK 11202 0256 DSZZAFBS GPRS telecom presentation

[2]3BK 11202 0257 DSZZAFBS GPRS Gb interface BSSGP Layer

[3]3BK 11202 0260 DSZZAFBS GPRS MFS-BSC interface BSCGP Layer

[4]3BK 11202 0264 DSZZAFBS GPRS Radio Interface RLC SUBLAYER

[5]3BK 11202 0263 DSZZAFBS GPRS Radio Interface MAC SUBLAYER

[6]3BK 11202 0262 DSZZAFBS GPRS MFS-BTS interface GCH stack

[7]3BK 11202 0258 DSZZAFBS GPRS Gb interface Network Service Control Sublayer

[8]3BK 11202 0259 DSZZAFBS GPRS Gb interface Sub-Network Service Sublayer

[9]3BK 11202 0266 DSZZAFBS GPRS Radio Interface Physical link layer

[10]3DC 25176 0001 FLZZAGPRS marketing requirements

[11]3DC 25176 0001 FLZZATBF BSS GPRS feature list

[12]3BK 11202 0199 DSZZASystem information management

[13]3BK 11202 0267 DSZZABSS telecom parameters

[14]3BK 11203 0055 DSZZAGPRS traffic model and performances

[15]3BK 10204 0467 DTZZAGPRS BSS Feature List

[16]3BK 10202 0279 DSZZAApplication document 04.60

[17]3BK 10202 0222 DSZZAApplication document 04.08

[18]3BK 10202 0271 DSZZAResource Allocation and Management

(19(3BK 10204 02228 DSZZAGPRS counter catalogue

GSM references[A]GSM 02.60Digital cellular telecommunications system (Phase2+)

General Packet Radio Services (GPRS)

Service description

Stage 1

[B]GSM 03.60Digital cellular telecommunications system (Phase2+)


Service description

Stage 2

[C]GSM 03.64Digital cellular telecommunications system (Phase2+)


Overall description of the GPRS radio interface

Stage 2

[D]GSM 04.60Digital cellular telecommunications system (Phase2+)


Mobile Station (MS) Base Station System (BSS) interface

Radio Link Control / Medium Access Control (RLC/MAC) protocol

[E]GSM 04.08Digital cellular telecommunications system (Phase2+)

Mobile radio interface layer 3 specification

[F]GSM 08.18Digital cellular telecommunications system (Phase2+)


Base Station System (BSS) - Serving GPRS Support Node

(SGSN) interface; BSS GPRS Protocol (BSSGP)

[G]GSM 05.02Digital cellular telecommunications system

GSM Radio Access Phase 3

Multiplexing and multiple access on the radio path

[H]GSM 05.08Digital cellular telecommunications system

Radio subsystem link control

[I]GSM 05.10Digital cellular telecommunications system

Radio subsystem synchronisation

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

RELATED DOCUMENTS

[R1]AA-CRC/RD/Na/GSM/JBr

/1088/98 version 2.0GPRS Radio Resource Allocation Part III : Comparison of several Reservation / Polling strategies for GPRS (errorless channel)

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

1. Overview description of the protocol layer

1.1 Layer location

Figure 1 : RRM layer location

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

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)

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

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.

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.

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)

The following table gives the characteristics of the 3 modes:

ModeCircuit Paging ChannelGPRS Paging ChannelCharacteristics

PCCCHPCCCH- Gs interface

- MPDCH

ICCCHCCCH- Gs interface

- no MPDCH

Packet data channel(not applicable)- Gs interface

IICCCHCCCH- no MPDCH

- no Gs interface

IIICCCHPCCCH- MPDCH

- no Gs interface

CCCHCCCH- 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)

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.

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.

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 ModePacket Transfer Mode

RR_substatesIdle_substateUL_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

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_stateRR_substatesListened channels

Packet_Idle_modeDRX_mode(P)CCCH blocks

defined by paging

group(s)

Non_DRX_modeFull (P)CCCH (note 1)

Packet_Transfer_modeUL idleDL waitingFull (P)CCCH (note 1)

DL transferringAssigned DL PDCH(s)

UL establishingDL idleFull (P)CCCH

DL waitingFull (P) CCCH


UL waitingDL idle- 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

DL waitingFull (P)CCCH


UL transferringDL idleAssigned UL PDCH(s)

DL waitingAssigned UL PDCH(s)

DL transferringAssigned 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.

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.

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 CB = 1

CBQ = 0 Normal Barred

CBQ = 1 Normal Normal

- Normal:a MS can access to the cell

- Barred: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)

1.3.5 Quality of Service Management

1.3.5.1 QoS parameters

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.

1.3.5.2 BSS behaviour related to QoS in B6.2

- service precedenceThe 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.

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

- 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 fieldnot managed

2. Protocol layer structure

2.1 Overview of layer functional model

Figure 4 : RRM layer functional modelPRH 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

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

Figure 3 RRM interfaces

3. Service primitives definition

3.1 Primitives provided to Layer Management Plane

Primitive NameREQI

NDRESCNF

Semantic

LM-BSS-CREATEx

x

Creation of a BSS

LM-BSS-DELETEx

x

Deletion of a BSS

LM-BSS-SETx

x

to modify a BSS parameter

LM-BSS-GETx

x

to get operational state

LM-BSS-STATE-CHANGE

x

state change notification

LM-CELL-CREATEx

x

Creation of a cell

LM-CELL-SETx

x

Modification of cell parameters

LM-CELL-DELETEx

x

Deletion of a cell

LM-CELL-GETx

x

To read cell attributes or counters

LM-CELL-STATE-CHANGE

x

state change notification

LM-GIC-Group-CREATEx

x

Creation of a GIC group

LM-GIC-Group-DELETEx

x

Deletion of a GIC group

LM-GIC-Group-GETx

x

To read GIC group attributes

LM-GIC-Group-STATE-CHANGE

x

Notification of GIC Group state change

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(:

Primitive nameType

Semantic

reqindrescnf

PRH-SYS-DEFINE x

xto provide MAC with MPDCH logical configuration and sysinfo. MAC is in charge of broadcasting provided sysinfo msg.

PRH-BLOCK-RESERVEx

xto request allocation of a block on a given PDCH for 2 phase access

PRH-PDCH-ESTABLISHx

xto declare a new PDCH in MAC layer, and to activate it for GPRS in BTS

PRH-PDCH-RELEASExx

xto release a PDCH in MAC layer ; indication that a PDCH has been released (e.g. L2GCH desynchronisation)

PRH-PDTCH-ASSIGNx

xto reserve resources for a new TBF

PRH-PDTCH-DEASSIGNx

xto free resources reserved for an existing TBF

PAG-PAGE-MSx

to send a CS or PS paging request on PPCH

PCC-DL-CONTROLx

xTo send RRM signalling PDU to a MS .

PCC-UL-CONTROL

x

To receive RRM signalling PDU from a MS

PCC-DL-ASSIGNx

xTo perform a DL assignment on PCCCH. To receive notification when the Packet Downlink Assignment is not sent by MAC.

PCC-UL-REJECTx

to reject access request on PCCCH

PCC-RLC-ESTABLISHx

xto establish a TBF context in (RLC)

PCC-RLC-ACTIVATEx

xto start allocation of radio blocks

PCC-RLC-RELEASExx

xto free a TBF context

PCC-RLC-MODIFY

x

Used by RLC to notify a coding scheme adaptation

PCC-TLLI-NOTIFY

x

UL contention resolution information

TRN-DL-FLOW-CTRL

x

DL flow control with RLC for 1 TBF

TRN-DL-UNITDATAx

to send DL PDU to (RLC)

TRN-UL-UNITDATA

x

received UL PDU

TRN-DL-FLOW-END

xx

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.

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 MSRLC primitive used when PDU is sent on Master PDCHRLC primitive used when PDU is sent on other PDCHPDU name in subsequent scenarios and finite state machines

PACKET DOWNLINK ASSIGNMENTPCC-DL-ASSIGN-reqPCC-DL-CONTROL-reqPCC-DL-ASSIGN-req

PACKET UPLINK ASSIGNMENTPCC-DL-CONTROL-reqPCC-UL-ASSIGN-req

PACKET ACCESS REJECTPCC-UL-REJECT-reqPCC-DL-CONTROL-req

PCC-UL-REJECT-req

PACKET PAGING REQUESTPAG-PAG-MS-reqPCC-DL-CONTROL-reqPAG-PAGE-MS-req

PACKET PDCH RELEASEPCC-DL-CONTROL-req

PRH-PDCH-RELEASE-MS-req

PACKET POWER / TIMING ADVANCE UPDATE PCC-DL-CONTROL-reqPCC-TA-UPDATE-req

PACKET SYSTEM INFORMATIONPRH-SYS-DEFINENot applicablePRH-SYS-DEFINE-req

PACKET CHANNEL REQUESTPCC-UL-CONTROL-indNot applicablePCC-UL-CHN-REQ-ind

UL access request during DL transferNot applicablePCC-UL-CONTROL-indPCC-UL-CHN2-REQ-ind

PACKET RESOURCE REQUESTPCC-UL-CONTROL-ind

PCC-UL-RES-REQ-ind

PACKET CONTROL ACKNOWLEDGEMENTPCC-UL-CONTROL-indPCC-CTRL-ACK-ind

3.2.2 Service Primitives used from (BSSGP) layer

Primitive nameType

Semantic

reqindrescnf

RL-DL-UNITDATA

x

send a DL-UNITDATA to BSS

RL-UL-UNITDATAx

send a UL-UNITDATA to SGSN

RL-UL-STARTx

xthroughput reservation request

RL-UL-STOPx

(RRM) informs (BSSGP) of end of transfer

GMM-PAGING-PS

x

page an MS within group of cells

GMM-PAGING-CS

x

page an MS within group of cells

GMM-RADIO-STATUSx

report that an exception condition occurred in the operation of the radio interface for an MS.

NM-FLUSH-LL

xx

request to re-route or delete queued LLC-SDU(s)

NM-LLC-DISCARDEDx

indicates that a number of buffered LLC-SDUs in a cell for an MS have been deleted inside the BSS

NM-FLOW-CONTROL-BVCx

xBVC flow control is notified to SGSN

NM-FLOW-CONTROL-MSx

xMS flow control is notified to SGSN

NM-STATUSx

indicates a PDU exception condition occurred.

NM-BVC-PTP-CREATE x

BVC-PTP creation requested to BSSGP layer

NM-BVC-PTP-DELETE x

BVC-PTP deletion requested to BSSGP layer

NM-BVC-SIG-CREATE x

BVC-SIG creation requested to BSSGP layer

NM-BVC-SIG-DELETE x

BVC-SIG deletion requested to BSSGP layer

NM-BVC-PTP-T-STATUS

x

BVC-PTP transmission status change notified by (BSSGP) layer

NM-BVC-SIG-T-STATUS

x

BVC-SIG transmission status change notified by (BSSGP) layer

NM-NSE-CONGESTION

x

NSE congestion notified by (BSSGP) layer

NM-NSE-CAPACITY

x

NSE available bandwidth notification

NM-BVC-PTP-STARTx

RRM asks to BSSGP to unblock a PTP-BVC

NM-BVC-PTP-STOPx

RRM asks to BSSGP to block a PTP-BVC

NM-BVC-SIG-STARTx

RRM asks to BSSGP to start a SIG-BVC

NM-BVC-SIG-STOPx

RRM asks to BSSGP to stop a SIG-BVC

NM-CELL-RESETxxx

BVC-PTP RESET has been received from SGSN

3.2.3 Service Primitives used from (BSCGP) layer

Primitive NameR

E

QI

N

DR

E

SC

N

FSemanticRelease

NTM-BSC-RESETxx

xReset of BSCGP interface Pilot

NTM-BSC-STATExxxxBSC state change notification or request Pilot

NTM-BSC-TRAFFIC-CONTROL

xx

Authorised access classes are changed for the whole BSS. B6.2

NTM-CELL-DETACHxxxxthe cell is detached (i.e; no more state change for this cell) B6.2

NTM-CELL-STARTx

xStart GPRS traffic within a cell Pilot

NTM-CELL-STATExxxxCell state change notification or request Pilot

NTM-CELL-STOPx

xStop GPRS traffic within a cell Pilot

NTM-CELL-RESETx

xdeallocation of all cell resources B6.2

NTM-CELL-TRAFFIC-CONTROL

xx

Authorised access classes are changed for one or several cells. B6.2

NTM-GICGROUP-STATExxxxGIC group state change notification or request Pilot

NTM-TRAFFIC-CONTROL

xx

Authorised access classes are changed for one or several cells. B6.2

PAG-PAGE-MSx

To transfer a CS or PS paging message on PCH Pilot

PCC-CHANNEL-ASSIGNx

To transfer an immediate assignment message on CCCH Pilot

PCC-UL-CHN-REQ

x

Notification of a CHANNEL REQUEST received on RACH (for GPRS) Pilot

PRH-CELL-LOAD

xx

Indicates that the load of one or several cells changes Pilot

PRH-CONF-MASTERx

xConfigure a master channel on an existing PDCH B6.2

PRH-DECONF-MASTERx

xDeconfigure a master channel on an existing PDCH B6.2

PRH-PDCH-ALLOCATEx

xTo request allocation by the BSC of one or several PDCH Pilot

PRH-PDCH-DEALLOCATExxxxIndicate or request deallocation of one or several PDCH 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.

ParametersPresenceRangeSemantic

BSSidM BSS Identifier

administrative stateM

locked/unlocked

network operation modeM1, 2, 3- mode I: CS and PS paging co-operation (Gs interface is mandatory)

- mode II: no master PDCH

- mode III: no specific requirements

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.



resultMOK/NOK

(cause(C 0-255

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.



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.



resultMOK/NOK

(cause(C 0-255



3.3.1.5 LM-BSS-GET-req

This primitive is used by LM to get a BSS operational state.



3.3.1.6 LM-BSS-GET-cnf

This primitive is used by NTM to return to LM the BSS operational state.



resultMOK/NOK

(cause(C 0-255



operational stateMenabled/disabled

availability statusC

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.



operational stateMenabled/disabled

availability statusC

present if operational state = disabled

- dependency: BVC-SIG not operational

- off-line: BSS unavailable (BSCGP indication)

3.3.1.8 LM-BSS-SET-req

This primitive is used by LM to modify parameters of one BSS.



administrative stateO

locked/unlocked

network operation modeM1, 2, 3- mode I: CS and PS paging co-operation (Gs interface is mandatory)

- mode II: no master PDCH

- mode III: no specific requirements

Network operation mode modification will have the following consequences:

Old Network Operation ModeNew Network Operation ModeAction

I/III IIIf in the BSS, there are cells supporting a master PDCH, the master PDCH has to be deactivated spontaneously by RRM

I IIIno action

III Ino action

II I/IIIIf 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.



resultMOK/NOK

(cause(C 0-255



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)


CellidM Cell identifier (LAC+CI)

BSCidM

BSC Identifier

MIN_MPDCHM0/1minimum number of PDCHs, supporting the master PDCH

MAX_MPDCHM0/1maximum 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

Nb_PDCH_GroupM1PDCH group number (only one in B6.2 )

PDCH_Group_id1M

identifier of the first PDCH group

MIN-PDCH-Group(first PDCH

group)M0-8Minimum number of PDCHs statically allocated in the cell

( (0, if MPDCH = 1)

MAX-PDCH-Group(first PDCH

group)M1-8Maximum number of PDCHs allocated in the cell

( (0, if MPDCH = 1)

MAX-PDCH-HIGH-LOAD

(first PDCH

group)M1-8Maximum 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)

cell parametersM

cell parameters (see 6)

adjacent cell parametersC (see 6)

present only if there is a master PDCH

administrative stateMlocked/

unlockedadministrative state at cell creation

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.


CELLidM Cell identifier (LAC+CI)

resultMOK/NOK

(cause(C 0-255



3.3.1.12 LM-CELL-DELETE-req

This primitive is used by LM to delete an existing cell.

This cell has to be previously locked.



3.3.1.13 LM-CELL-DELETE-cnf

This primitive is used by NTM to indicate to LM that a cell has been successfully deleted or not.



resultMOK/NOK

(cause(C 0-255



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.



BSCidM

BSC identifier

administrative state MLocked/

unlockedadministrative state

MIN_MPDCHM0/1minimum number of PDCHs, supporting the master PDCH

MAX_MPDCH

M0/1maximum 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

Nb_PDCH_GroupM

PDCH group number (only one in B6.2 )

PDCH_Group_id1M

identifier of the first PDCH group

MIN-PDCH-Group

(first PDCH

group)M0-8Minimum number of PDCHs statically allocated in the cell

( (0, if MPDCH = 1)

MAX-PDCH-Group(first PDCH

group)M1-8Maximum number of PDCHs allocated in the cell

( (0, if MPDCH = 1)

MAX-PDCH-HIGH-LOAD

(first PDCH

group)M1-8Maximum 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)

cell parametersM

Telecom parameters

adjacent cell parametersC if there is a master PDCH

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:The new limit is taken into account.

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:The new limit is taken into account.

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:The new limit is taken into account.

If some current TBFs have more PDCHs than the new Max_PDCH_Per_TBF value, no specific action is undertaken.

- MIN_PDCH_Group:The new limit is taken into account.

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:The new limit is taken into account.

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



resultMOK/NOK

(cause(C 0-255



3.3.1.16 LM-CELL-GET-req

This primitive is used by LM to get cell attributes



3.3.1.17 LM-CELL-GET-cnf

This primitive is used by NTM to give to LM the cell parameters.



resultMOK/NOK

(cause(C 0-255



operational

stateMenabled/

disabledGPRS operational state

availability statusCoff-line/

dependency/

failedpresent only if operational state = disabled

- off-line: BSCGP unavailability

- dependency: BVC-PTP unavailability

- failed: RRM internal cause

(e.g. MPDCH not established)

3.3.1.18 LM-CELL-State-Change-ind

This primitive is used by NTM to indicate to LM cell state changes or MPDCH state changes.



cell operational

stateMenabled/

disabledGPRS cell operational state

cell availability statusMoff-line/

dependency/

failedpresent only if operational state = disabled

- off-line: BSCGP unavailability

- dependency: BVC-PTP unavailability

- failed: RRM internal cause

(e.g. MPDCH not established)

MPDCH operational stateMenabled / disabledMPDCH operational state

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)


BSSidM

BSS Identifier

GIC groupM0-2047GIC group (PCM identification: 11 bits)

ATERmuxid (1)M

ATERmux identification (used for local addressing)

- PCM (9 bits)

- TS (5 bits)

- nibble (2 bits)

ATERCid (1)M Mapped Ater circuit identity = CIC

(used for PDCH allocation request to BSC)

- TS (5 bits)

ATERmuxid (n)C

ATERmux identification (used for local addressing)

- PCM (9 bits)

- TS (5 bits)

- nibble (2 bits)

ATERCid (n)C Mapped Ater circuit identity = CIC

(used for PDCH allocation request to BSC)

- TS (5 bits)

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.



resultMOK/NOKOK: the request has been totally accepted

NOK: the request has been partially or totally refused

(cause(C 0-255



GIC groupC

Gic group identification (PDM: 11 bits)

(present if result = OK)

3.3.1.21 LM-GIC-Group-DELETE-req

This primitive is used by LM to delete an existing GIC group.



GIC groupM

GIC group (PCM identification: 11 bits)

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



GIC groupM


resultMOK/NOKOK: the request has been totally accepted

NOK: the request has been partially or totally refused

(cause(C 0-255



3.3.1.23 LM-GIC-Group-GET-req

This primitive is used by NTM to indicate to LM the GIC group attributes and states.



GIC groupM


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.



GIC groupM


resultMOK/NOK

(cause(C 0-255



operational

stateCenabled/

disabledoperational state

(present if result = OK)

3.3.1.25 LM-GIC-Group-State-Change-ind

This primitive is used by NTM to indicate to LM a GIC group state change.



GIC groupM


operational

stateMenabled/

disabledoperational state

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.

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

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.

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.

4.1.2.2 One phase access UL TBF establishment initiated by MS in packet idle mode on CCCH

Figure 5 : 1 Phase access UL TBF establishment by MS in packet idle mode on CCCH

(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)

(2) Packet access reject procedure :

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.

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)

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.

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

The timer T_ack_wait is activated to wait for the acknowledge.

(5b) 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.

(5c) The MS transmits uplink blocks when allowed by the network (see (5().

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

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 :



(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) Pa

alu gprs radio resource management

Documents

review meeting

proposal 02xx1198document

working meeting minutes

document creation

bss division

working group meeting

smg29 bss

mcdtd vlizy