MFS PMU-PTU Interface Specification B9 ed05.pdf

ED05 Released PMU - PTU INTERFACE SPECIFICATION

EVOLIUM 3bk09556jaaapbzza-ed5rl.doc

2006-2-22 3BK 09556 JAAA PBZZA 1/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Site

SHANGHAI

EVOLIUM SAS

Originators

Dong Yuhua

Zhang Rutao

MFS INTERFACE SPECIFICATION PMU - PTU INTERFACE SPECIFICATION

RELEASE B9

System : ALCATEL 900/BSS Sub-system : MFS Document Category : INTERFACE SPECIFICATION

ABSTRACT This document describes the software interface that should be implemented between the DSP and the PPC of the GPU board located inside the MFS NE. It focuses only primitives related to exchanges between RRM and DSP layers in B9 MR3. This document may change if the referenced document shall be updated.

NOTE: The fields in gray are not used

Approvals

Name App.

D. Albonico D. Lacroix Y. Wang

Name App.

L. Pigeot K. Feng

REVIEW

Ed.01 Proposal 01 02/03/04 TD/CNS/2004-4030/FDU

Ed.01 Proprosal 02 22/03/04 2004MND-RDR0322-01561-1-Dongyh

Ed.01 Proposal 03 16/04/04 2004MCG-RDR0416-01561-3-Dongyh



Ed.01 Proposal 06 16/07/04 2004MCG-RDR0716-01561-10-Dongy

Ed.02 Proposal 01 02/08/04 No comments are received after review




2006-2-22 3BK 09556 JAAA PBZZA 2/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.



Ed 03 Proposal 04 30/09/04 No review remarks

Ed 03 Proposal 05 16/11/04 2004MCG-RDR1112-01561-15-Dongy

Ed 03 Proposal 06 24/12/04 2004MCG-RDR1224-01768-4-Zhangr

Ed 03 Proposal 07 7/1/05 2005MCG-RDR0112-01768-8-Zhangr

Ed 03 Proposal 08 28/1/05 No review remarks

Ed03 Proposal 09 15/03/05 2005MCG-RDR0315-01561-28-Dongy

Ed03 Released 29/03/05 2005MCG-RDR0407-01768-12-Zhang

Ed 04 Proposal 01 14/04/05 Review by mail, no review remark

Ed 04 Proposal 02 27/05/05 2005MCG-RDR0530-01768-13-Zhang



Ed05 Proposal 03 18/11/05 Review by mail, no review remark

HISTORY HISTORY information about the editions 01 and 02 is available in the edition 03 Released

Ed 01 Released 16/07/04 According to the review report.

Released



2006-2-22 3BK 09556 JAAA PBZZA 3/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Ed 03 Proposal 01 02/08/04 Update according to DMC registered with GOMCML-MFSB9.01-08. Update according to Extended Uplink Mode. Update according to DTM. Update according to DL Retransmission in BTS. Update according to QoS. Update according to UL 8PSK & IR.

Ed 03 Proposal 02 17/08/04 Update according to the review report.

Ed 03 Proposal 03 11/09/04 Update according to the review report and DMC registered with GOMCML-MFSB9.01-09

Ed 03 Proposal 04 23/09/04 Update accordidng to the review report

Ed 03 Proposal 05 30/09/04 Update acoording to PMU proposal

Ed 03 Proposal 06 16/11/04 Update according to the review report

Aligned with GOMCML-MFSB9.01-13

Ed 03 Proposal 07 24/12/04 Update according to the review report

Aligned with GOMCML-MFSB9.01-16

Ed 03 Proposal 08 12/1/05 Update according to the review report and the CR �CS/MCS reduction in delayed final PUAN mode and in extended uplink TBF mode� (3BKA20CBR154895)

Ed 03 Proposal 09 2/2/05 Aligned with GOMCML-MFSB9.01-17

Ed 03 Released 15/03/05 Released

Ed 04 Proposal 01 7/4/05 Update according to the following CRs: 3BKA20CBR158875 3BKA20CBR158029 3BKA20CBR157815 Update the document according to review report: 2005MCG-RDR0407-01768-12-Zhang Aligned with GOMCML-MFSB9.01-18

Ed 04 proposal 02 13/05/05 Update according to the CR (3BKA20CBR161360) Change the Range of T_Delayed_DL_TBF_Pol

Ed 04 Released 30/05/05 According to the review report. Released.

Ed 05 Proposal 01 10/06/05 Update PMU-PTU interface for MX 4 capacity Keep align with DMC-MFSB9.01-07

Ed 05 Proposal 02 17/06/05 Update according to the review report One CR (3BKA13CBR164069) is considered



2006-2-22 3BK 09556 JAAA PBZZA 4/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Ed 05 Proposal 03 23/09/05 Update PMU-PTU interface according the review report: 2005MCG-RDR0923-01768-19-Zhang Keep align with DMC-MFSB9.01-09, the following CRs are contained: 3BKA13CBR169466 3BKA13CBR169470 3BKA20CBR166602 3BKA20CBR166625 3BKA20CBR167878 3BKA13CBR166751

Ed 05 Released 28/11/05 Released



2006-2-22 3BK 09556 JAAA PBZZA 5/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

TABLE OF CONTENTS

1 ACRONYMS..................................................................................................................................................9 2 INTERFACE DESCRIPTION ......................................................................................................................11

2.1 Overview .............................................................................................................................................11 2.2 Interactions with low level interface management ........................................................................13 2.3 Messages lists ...................................................................................................................................14 2.4 Scenarios of PPC-DSP exchanges ..................................................................................................15

3 DETAILED DESCRIPTION OF MESSAGES .............................................................................................16 3.1 Implementation rules.........................................................................................................................17

3.1.1 Coding rules ..............................................................................................................................17 3.1.2 Compilation rules.......................................................................................................................17 3.1.3 Checking rules...........................................................................................................................18

3.2 Class DSP.........................................................................................................................................23 3.2.1 DSP-ALARM-ind........................................................................................................................23 3.2.2 DSP-CONGESTION-ind............................................................................................................26 3.2.3 DSP-INIT-req.............................................................................................................................28 3.2.4 DSP-INIT-cnf .............................................................................................................................38 3.2.5 DSP-MODIFY-req......................................................................................................................39 3.2.6 DSP-MODIFY-cnf ......................................................................................................................41 3.2.7 DSP-PAGE-MS-req ...................................................................................................................42 3.2.8 DSP-PAGE-MS-cnf ...................................................................................................................43 3.2.9 DSP-TRANSPARENT-req (provision for DSP internal usage) .................................................44 3.2.10 DSP-TRANSPARENT-cnf (provision for DSP internal usage)..................................................44 3.2.11 DSP-TRANSPARENT-DUMP-req.............................................................................................45 3.2.12 DSP-TRANSPARENT-DUMP-cnf .............................................................................................46 3.2.13 DSP-TRANSPARENT-MODIFY-req .........................................................................................47 3.2.14 DSP-TRANSPARENT-MODIFY-cnf..........................................................................................48 3.2.15 DSP-TRANSPARENT-PERF-req..............................................................................................49 3.2.16 DSP-TRANSPARENT-PERF-cnf ..............................................................................................50 3.2.17 DSP-TRANSPARENT-PPC-req ................................................................................................51 3.2.18 DSP-TRANSPARENT-PPC-cnf ................................................................................................52 3.2.19 DSP-TRANSPARENT-TRACE-Ind ...........................................................................................53 3.2.20 DSP-GET-PM-req......................................................................................................................54 3.2.21 DSP-GET-PM-cnf ......................................................................................................................55 3.2.22 DSP-TRX-PM-GAUGE-req .......................................................................................................58 3.2.23 DSP-TRX-PM-GAUGE-cnf........................................................................................................59 3.2.24 DSP-TRX-PM-COUNTER-req...................................................................................................61 3.2.25 DSP-TRX-PM-COUNTER-cnf ...................................................................................................62 3.2.26 DSP-TRX-SAMPLE-req.............................................................................................................66 3.2.27 DSP-TRX-SAMPLE-cnf .............................................................................................................67 3.2.28 DSP-LOAD-ind ..........................................................................................................................69

3.3 Class TRX ...........................................................................................................................................70 3.3.1 TRX-CREATE-req .....................................................................................................................70 3.3.2 TRX-CREATE-cnf......................................................................................................................74 3.3.3 TRX-DELETE-req......................................................................................................................75 3.3.4 TRX-DELETE-cnf ......................................................................................................................76 3.3.5 TRX-PPCH-req..........................................................................................................................77 3.3.6 TRX-NO-PPCH-ind....................................................................................................................78 3.3.7 TRX-MODIFY-req......................................................................................................................79 3.3.8 TRX-MODIFY-cnf ......................................................................................................................80 3.3.9 TRX-SYS-DEFINE-req ..............................................................................................................81 3.3.10 TRX-SYS-DEFINE-cnf...............................................................................................................87



2006-2-22 3BK 09556 JAAA PBZZA 6/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4 Class TBF ...........................................................................................................................................88 3.4.1 TBF-ACTIVATE-req...................................................................................................................88 3.4.2 TBF-ACTIVATE-cnf ...................................................................................................................90 3.4.3 TBF-DEACTIVATE-req..............................................................................................................91 3.4.4 TBF-DEACTIVATE-cnf ..............................................................................................................92 3.4.5 TBF-DL-FLOW-CTRL-ind..........................................................................................................93 3.4.6 TBF-DL-UNITDATA-req ............................................................................................................94 3.4.7 TBF-DL-LLC-ACK-ind................................................................................................................96 3.4.8 TBF-ESTABLISH-req ................................................................................................................97 3.4.9 TBF-ESTABLISH-cnf...............................................................................................................100 3.4.10 TBF-MODIFY-req ....................................................................................................................101 3.4.11 TBF-REALLOC-req .................................................................................................................102 3.4.12 TBF-REALLOC-cnf..................................................................................................................104 3.4.13 TBF-RELEASE-req..................................................................................................................105 3.4.14 TBF-RELEASE-cnf ..................................................................................................................106 3.4.15 TBF-RELEASE-ind ..................................................................................................................107 3.4.16 TBF-START-ind.......................................................................................................................108 3.4.17 TBF-UL-CONTROL-ind ...........................................................................................................109 3.4.18 TBF-UL-UNITDATA-ind...........................................................................................................111 3.4.19 TBF-PSCD-req ........................................................................................................................112 3.4.20 TBF-PSCD-cnf.........................................................................................................................115 3.4.21 TBF-PNCD-req ........................................................................................................................116 3.4.22 TBF-PNCD-cnf ........................................................................................................................118 3.4.23 TBF-QOS-CONTROL-req .......................................................................................................119

3.5 Class PDCH related to message TRX............................................................................................121 3.5.1 PDCH-BLOCK-RESERVE-req ................................................................................................121 3.5.2 PDCH-BLOCK-RESERVE-cnf ................................................................................................122 3.5.3 PDCH-DL-CONTROL-req .......................................................................................................123 3.5.4 PDCH-DL-CONTROL-cnf........................................................................................................125 3.5.5 PDCH-UL-CONTROL-ind........................................................................................................126 3.5.6 PDCH-UL-REJECT-req...........................................................................................................128

3.6 Class GCH related to message TRX ..............................................................................................129 3.6.1 GCH-ESTABLISH-req .............................................................................................................129 3.6.2 GCH-ESTABLISH-cnf..............................................................................................................131 3.6.3 GCH-RELEASE-req ................................................................................................................133 3.6.4 GCH-RELEASE-cnf.................................................................................................................135 3.6.5 GCH-RELEASE-ind.................................................................................................................137

3.7 Class L2GCH ....................................................................................................................................139 3.7.1 L2GCH-DATA-req ...................................................................................................................139 3.7.2 L2GCH-DATA-ind....................................................................................................................140

4 PARAMETER DESCRIPTIONS................................................................................................................141 4.1 BLOCK ..............................................................................................................................................141

4.1.1 Packet Channel request BLOCK.............................................................................................141 4.1.2 Channel 2 Request BLOCK ....................................................................................................142 4.1.3 Control Acknowledgement BLOCK .........................................................................................142 4.1.4 Access Reject BLOCK.............................................................................................................143 4.1.5 Paging CS BLOCK ..................................................................................................................143 4.1.6 Paging PS BLOCK ..................................................................................................................143 4.1.7 Unknown BLOCK ....................................................................................................................144

4.2 PDU 144 4.3 BLOCK_TYPE...................................................................................................................................144 4.4 CAUSE ..............................................................................................................................................145

4.4.1 Introduction..............................................................................................................................145 4.4.2 Restriction................................................................................................................................145 4.4.3 Rule for cause value assignment ............................................................................................145 4.4.4 DSP-INIT-CNF.........................................................................................................................145 4.4.5 DSP-MODIFY-CNF .................................................................................................................145



2006-2-22 3BK 09556 JAAA PBZZA 7/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.4.6 DSP-PAGE-MS-CNF...............................................................................................................146 4.4.7 DSP-TRX-PMGAUGE-cnf .......................................................................................................146 4.4.8 DSP-TRX-PMCOUNTER-cnf ..................................................................................................146 4.4.9 DSP-TRX-SAMPLE-cnf ...........................................................................................................146 4.4.10 TRX-CREATE-CNF.................................................................................................................146 4.4.11 TRX-DELETE-CNF..................................................................................................................147 4.4.12 TRX-NO-PPCH-IND ................................................................................................................147 4.4.13 TRX-MODIFY-CNF..................................................................................................................147 4.4.14 TRX-SYS-DEFINE-CNF..........................................................................................................147 4.4.15 TBF-ESTABLISH-CNF ............................................................................................................148 4.4.16 TBF-ACTIVATE-CNF ..............................................................................................................148 4.4.17 TBF-REALLOC-CNF ...............................................................................................................148 4.4.18 TBF-DEACTIVATE-CNF .........................................................................................................149 4.4.19 TBF-RELEASE-CNF ...............................................................................................................149 4.4.20 TBF-RELEASE-IND.................................................................................................................149 4.4.21 TBF-PNCD-CNF and TBF-PSCD-CNF...................................................................................150 4.4.22 PDCH-BLOCK-RESERVE-CNF..............................................................................................150 4.4.23 PDCH-DL-CONTROL-CNF.....................................................................................................150 4.4.24 GCH-ESTABLISH-CNF...........................................................................................................151 4.4.25 GCH-RELEASE-CNF ..............................................................................................................151 4.4.26 GCH-RELEASE-IND ...............................................................................................................152

4.5 Class 153 4.6 Coding scheme ................................................................................................................................153 4.7 DEBUG INFO ....................................................................................................................................153 4.8 FN 153 4.9 GCH-index ........................................................................................................................................154 4.10 Global TFI .........................................................................................................................................154 4.11 IMSI / Mobile Identity .......................................................................................................................155 4.12 Mtype 156 4.13 Reference..........................................................................................................................................157

4.13.1 Class 1 : DSP ..........................................................................................................................157 4.13.2 Class 2 : TRX ..........................................................................................................................157 4.13.3 Class 3 : TBF...........................................................................................................................157

4.14 Packet Request Reference .............................................................................................................158 4.15 PDU_TYPE........................................................................................................................................158 4.16 POLL 158 4.17 (P)SI PDU ..........................................................................................................................................158

5 TIMING CONSTRAINT .............................................................................................................................160 5.1 Constraint defined in the RRM sublayer specification ................................................................160 Exchange sequence for concerned scenario........................................................................................160

5.1.1 Nominal case...........................................................................................................................161 5.1.2 Reject case..............................................................................................................................162

5.2 Distribution of the timing constraint .............................................................................................163 5.2.1 Definition of delays ..................................................................................................................163 5.2.2 Determination of T1, T3 and T5 delays ...................................................................................165 5.2.3 Determination of T2 and T4 delays .........................................................................................167

5.3 Constraint summary........................................................................................................................168 5.4 Conclusion .......................................................................................................................................169



2006-2-22 3BK 09556 JAAA PBZZA 8/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

INTERNAL REFERENCED DOCUMENTS

Not applicable

REFERENCED DOCUMENTS

[ 1 ] PPC / DSP Interface Specification Release B6.2

3BK 09683 FCAB PBZZA

[ 2 ] FBS GPRS � Radio Interface � RLC Sublayer 3BK 11202 0392 DSZZA

[ 3 ] GPRS � Radio Interface � MAC Sublayer 3BK 11202 0393 DSZZA

[ 4 ] Specification � DSP driver � Interface interface 3BK 09572 FCAA PBZZA

[ 5 ] PMU Logging messages description and principles 3BK 09850 JAAA DSZZA

[ 6 ] Radio Link Control/Medium Access Control (RLC/MAC) protocol (Release 4) GSM 44.060 v4.14.0

RELATED DOCUMENTS

MFS INTERFACE DATA CATALOGUE 3BK 09721 JAAA PQZZA

BSS TELECOM PARAMETER 3BK 11203 0103 DSZZA

MFS COUNTER CATALOGUE 3BK 11203 0101 DSZZA

PREFACE

This document describes the message interface that should be implemented between the DSP and the PPC of the GPU board inside the MFS NE. The document shall be applied to the B9 version nevertheless some indications related to further step(s) primitives have been kept without update but should not be used. It describes the messages exchanged over the physical interface.

The mechanisms of the interface between the PMU (PPC) and the PTU (DSP) is described in [ 1 ]

OPEN POINTS / RESTRICTIONS

Not applicable.



2006-2-22 3BK 09556 JAAA PBZZA 9/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

1 ACRONYMS

BTS Base Transceiver Station

DL Downlink

DRX Discontinuous Reception

DSP Digital Signal Processor

Edge Enhanced Data rates for the GSM Evolution

FN Frame Number

GCH GPRS Channel

GPRS General Packet Radio Service

EGPRS Enhanced GPRS

GPU GPRS P U

HPI Host Port Interface

LLC Logical Link Control

MAC Medium Access Control

MFS Multi-BSS Fast Packet Server

MS Mobile Station

NACC Network Assisted Cell Change

NE Network Element

NTM Network Management

PACCH Packet Associated Control Channel

PAG Paging

PBCCH Packet Broadcast Control Channel

PCCCH Packet Common Control Channel

PCI Peripheral Component Interface

PDCH Packet Data Channel

PDTCH Packet Data Traffic Channel

PDU Packet Data Unit

PM Performance monitoring

PMU Packet Management Unit

PPC Power PC

PRACH Packet Random Access Channel

PRH Packet Radio resource Handling

PSI Packet System Information

PTU Packet Traffic Unit

RLC Radio Link Control

RRM Radio Resource Management

RXLEV Reception Level

RXQUAL Reception Quality

TFI Temporary Flow Identifier

TLLI Temporary Logical Link Identifier

TRX Transceiver

UL Uplink

USF Uplink State Flag



2006-2-22 3BK 09556 JAAA PBZZA 10/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PSCD Packet Serving Cell Data

PNCD Packet Neighbour Cell Data

QoS Quality of Service

MX Multi-standard platform



2006-2-22 3BK 09556 JAAA PBZZA 11/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

2 INTERFACE DESCRIPTION

2.1 Overview

Semantic of some message is precised.

Clear distinction between messages which generate local (L) messages (i.e. between PPC & DSP, which are terminated in DSP) and messages which generate remote ® messages (i.e. between the MFS and the MS or BTS, which are terminated in MS or BTS) is given.

R/L Message name Type

Semantic

Req

Ind

Rsp

Cnf

Class 1 : DSP

L DSP-CONGESTION

X To indicate DSP congestion state change (related to DSP RLC resources)

L DSP-ALARM

X To report an alarm detected by DSP

L DSP-INIT X X To provide DSP and telecom layer configuration parameters and allow DSP to handle other messages.

L DSP-MODIFY X X To modify the larger configuration parameters

L DSP-PAG-MS X X To send a packet paging message on air interface

L DSP-TRANSPARENT-DUMP

X X To send a message from/to DSP via PMU and transparently to PMU application

Used for DUMP memory

L DSP-TRANSPARENT-MODIFY


Used for MODIFY memory

L DSP-TRANSPARENT-PERF


Used for performance reporting

L DSP-TRANSPARENT-PPC X X To send a message to DSP via PMU and transparently to PMU application

Used to sent message as if message was sent by PPC



2006-2-22 3BK 09556 JAAA PBZZA 12/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


Semantic

Req

Ind

Rsp

Cnf

L DSP-GET-PM X X To retrieve DSP related PM counters from DSP

L DSP-TRX-PMCOUNTER X X To retrieve TRX related PM counters from DSP every Granularity period

L DSP-TRX-PMGAUGE X X To retrieve TRX related PM Gauges from DSP every Gauge Polling Period

Class 2 : TRX

L TRX-CREATE X X To create a TRX context (configuration parameters)

L TRX-DELETE X X To delete a TRX context

R TRX-PPCH X To send the Packet DL Assignment PDU to the MS on PPCH (using DRX parameters)

L TRX-NO-PPCH X To indicate that the Packet DL Assignment PDU was not sent

L TRX-MODIFY X X To modify the TRX context

L+R TRX-SYS-DEFINE X X To provide logical channel configuration and packet system information

Class 3 : TBF

L TBF-ACTIVATE X X To start the TBF and the allocation of radio resource

L TBF-DEACTIVATE X X To stop the TBF (i.e. any data traffic with the MS)

L TBF-DL-FLOW-CTRL X To suspend/resume the DL data flow

L+R TBF-DL-UNITDATA X To send DL LLC PDU

L+R TBF-DL-LLC-ACK X To acknowledge DL LLC PDU

L TBF-ESTABLISH X X To establish/create a TBF context

L TBF-MODIFY X To modify the TBF context

L TBF-REALLOC X X To modify the TBF allocation

L TBF-RELEASE X X X To release the TBF context

L TBF-START X To indicate the reception of the first RLC data block



2006-2-22 3BK 09556 JAAA PBZZA 13/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


Semantic

Req

Ind

Rsp

Cnf

L+R TBF-UL-CONTROL X To receive MS signaling received in the Packet DL Ack/Nack

L+R TBF-UL-UNITDATA X To receive UL LLC PDU

L+R TBF-PSCD X X To send Packet Serving Cell Data to MS

L+R TBF-PNCD X X To send Packet Neighbor Cell Data to MS

L TBF- QOS-CONTROL X To change the QoS context in PTU. Class 4 : PDCH

L PDCH-BLOCK-RESERVE X X To reserve a block on a given PDCH

R PDCH -DL- CONTROL X X To send signaling to the MS

L+R PDCH-CONFIG X X To activate a PDCH

L+R PDCH-RELEASE X To release a PDCH

R PDCH -UL- CONTROL X To receive signaling issued from the MS

R PDCH-UL-REJECT X To reject the MS call/access on PCCCH Class 5 : L2GCH

GCH-16-DATA X X Used for test purpose

Class 6 : GCH

L+R GCH-ESTABLISH X X To activate some GCH�s

L+R GCH-RELEASE X X X To release some GCH�s

2.2 Interactions with low level interface management

Low level interface management is described in [ 1 ]

After successful low level initialization, the operational mode of the interface is entered. PMU and PTU are then able to exchange all messages described in this specification.



2006-2-22 3BK 09556 JAAA PBZZA 14/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

In case of fatal error triggered by DSP, a post mortem area is provided by DSP. This post mortem content includes a message DSP-ALARM-indication which format is defined in this specification and additional design dependent DSP information.

After a fatal error triggered by DSP, the exception mode of the interface is entered and no more message can be exchanged with this DSP without performing a new low level initialization. In any case after low level initialization, DSP behavior is as it is after first initialization.

2.3 Messages lists

Mapping between DSP/PPC Interface messages and primitives described in [1][2][3][4] Message Primitives described in [1][2][3][4]

Class 1 : DSP DSP-CONGESTION-ind DSP-ALARM-ind DSP-INIT-req LM-RLC-CREATE-req + LM-MAC-CREATE-req + LM-GCH-CREATE-req DSP-INIT-cnf LM-RLC-CREATE-cnf + LM-MAC-CREATE-cnf + LM-GCH-CREATE-cnf DSP-MODIFY-req LM-RLC-SET-req + LM-MAC-SET-req DSP-MODIFY-cnf LM-RLC-SET-cnf + LM-MAC-SET-cnf DSP-PAGE-MS-req PAG-PAGE-MS-req DSP-PAGE-MS-cnf DSP-TRANSPARENT-req DSP-TRANSPARENT-cnf DSP-TRANSPARENT-DUMP-req DSP-TRANSPARENT-DUMP-cnf DSP-TRANSPARENT-MODIFY-req DSP-TRANSPARENT-MODIFY-cnf DSP-TRANSPARENT-PERF-req DSP-TRANSPARENT-PERF-cnf DSP-TRANSPARENT-PPC-req DSP-TRANSPARENT-PPC-cnf DSP-GET-PM-req DSP-GET-PM-cnf DSP-TRX-PM-COUNTER-req DSP-TRX-PM-COUNTER-cnf DSP-TRX-PM-GAUGE-req DSP-TRX-PM-GAUGE-cnf DSP-LOAD-ind Class 2 : TRX TRX-CREATE-req LM-CELL-CREATE-req (RLC) + LM-CELL-CREATE-req (MAC) TRX-CREATE-cnf LM-CELL-CREATE-req (RLC) + LM-CELL-CREATE-req (MAC) TRX-DELETE-req LM-CELL-DELETE-req (RLC) + LM-CELL-DELETE-req (MAC) TRX-DELETE-cnf LM-CELL-DELETE-cnf (RLC) + LM-CELL-DELETE-cnf (MAC) TRX-NO-PPCH-ind PCC-DL-ASSIGN-cnf TRX-PPCH-req PCC-DL-ASSIGN-req TRX-MODIFY-req LM-CELL-SET-req (RLC) + LM-CELL-SET-req (MAC) TRX-MODIFY-cnf LM-CELL-SET-cnf (RLC) + LM-CELL-SET-cnf (MAC) TRX-SYS-DEFINE-req PRH-SYS-DEFINE-req TRX-SYS-DEFINE-cnf PRH-SYS-DEFINE-cnf Class 3 : TBF TBF-ACTIVATE-req PCC-RLC-ACTIVATE-req TBF-ACTIVATE-cnf PRH-RLC-ACTIVATE-cnf TBF-DEACTIVATE-req PCC-RLC-DEACTIVATE-req TBF-DEACTIVATE-cnf PRH-RLC-DEACTIVATE-cnf TBF-DL-FLOW-CTRL-ind TRN-DL-FLOW-CTRL-ind TBF-DL-UNIT-DATA-req TRN-DL-UNITDATA-req TBF-ESTABLISH-req PCC-RLC-ESTABLISH-req + PRH-PDTCH-ASSIGN-req TBF-ESTABLISH-cnf PCC-RLC-ESTABLISH-req + PRH-PDTCH-ASSIGN-req TBF-MODIFY-req PCC-RLC-MODIFY-req TBF-REALLOC-req PCC-RLC-REALLOC-req TBF-REALLOC-cnf PCC-RLC-REALLOC-cnf TBF-RELEASE-req PCC-RLC-RELEASE-req + PRH-PDTCH-DEASSIGN-req



2006-2-22 3BK 09556 JAAA PBZZA 15/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Message Primitives described in [1][2][3][4] TBF-RELEASE-cnf PCC-RLC-RELEASE-cnf + PRH-PDTCH-DEASSIGN-cnf TBF-RELEASE-ind PCC-RLC-RELEASE-ind TBF-START-ind PCC-TBF-START-ind TBF-UL-CONTROL-ind PCC-UL-CONTROL-ind TBF-UL-UNIT-DATA-ind TRN-UL-UNITDATA-ind TBF-PSCD-req PCC-PSCD-req TBF-PSCD-cnf PCC-PSCD-cnf TBF-PNCD-req PCC-PNCD-req TBF-PNCD-cnf PCC-PNCD-cnf TBF-QOS-CONTROL-req PCC-QOS-CONTROLl-req Class 4 : TRX PDCH-BLOCK-RESERVE-req PRH-BLOCK-RESERVE-req PDCH-BLOCK-RESERVE-cnf PRH-BLOCK-RESERVE-cnf PDCH-DL-CONTROL-req PCC-DL-CONTROL-req PDCH-DL-CONTROL-cnf PCC-DL- CONTROL-cnf PDCH-CONFIG-req PRH-PDCH-ESTABLISH-req PDCH-CONFIG-cnf PRH-PDCH-ESTABLISH-cnf PDCH-RELEASE-ind PRH-PDCH-RELEASE-ind PDCH-UL-CONTROL-ind PCC-UL-CONTROL-ind PDCH-UL-REJECT-req PCC-UL-REJECT-req Class 5 : L2GCH L2GCH-DATA-req L2GCH-DATA-ind Class 6 : GCH GCH-ESTABLISH-req GCH-LINK-ESTABLISH-req GCH-ESTABLISH-cnf GCH-LINK-ESTABLISH-cnf GCH-RELEASE-req GCH-LINK-RELEASE-req GCH-RELEASE-cnf GCH-LINK-RELEASE-cnf GCH-RELEASE-ind GCH-RELEASE-ind

2.4 Scenarios of PPC-DSP exchanges

The sequence diagrams are in the BSS interlayer scenario and in the GPU/DSP interlayer scenario.



2006-2-22 3BK 09556 JAAA PBZZA 16/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3 DETAILED DESCRIPTION OF MESSAGES

Hereafter, the detailed description of messages for B9 is given.

The general (BIG ENDIAN) format of the messages exchanged between PPC and DSP layers is the following:

Byte 0 length (MSB) Length = N bytes

Byte 1 length (LSB) 1 Byte = 8 Bits

Byte 2 mclass

Byte 3 mtype Message Type

Byte 4 reference (MSB)

Byte 5 reference (LSB)

Byte 6 padding

Byte 7 padding

Byte 8 Byte 0

Byte N -1 = M + 7

Data

Byte M-1(M = N�8)

The content of the different fields is the following:

Length: This field represents the message length (padding bytes & length included). Application should not use these 2 bytes to decode the message.

Class: This field represents the class of message (see 4.5)

Reference: This field represents an index (see 4.13) and has a value between 0x0000 and 0xFFFF (NIL). The 0xFFFF indicates that the field is not significant.

Mtype : This byte contains the message type of the message.



2006-2-22 3BK 09556 JAAA PBZZA 17/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Data : the data provided in the message, depending on its type, are described in the section 3. The data field size shall be up to N bytes (with padding bytes if necessary).

Padding: the padding bytes must not be checked but it�s convenient to set them to the value (00H)

An indication �O� in the presence column indicates that the field could be not significant, but the field is nevertheless always included in the message.

PMU (Packet Management Unit) PTU (Packet Traffic Unit)

PPC DSP

Application Application

Driver Driver

Length modified modulo 4 = 0 Length modulo 4 = 0

3.1 Implementation rules

3.1.1 Coding rules

All parameters which exceed 8 bits length shall be encoded as big Indian.

All parameters are mandatory to keep a constant length of the message. If a parameter has no functional meaning i.e. optional parameter, no specific value are requested but for debug purpose it�s should set to NIL value (0xFF, or 0xFFFF, or 0xFFFFFFFF).

For each parameter with variable size, a max size shall be applied.

For the Bitmap related to a list of time slots: the most significant bit is related to time slot 0, the less significant bit is related to 7.

Bit position 8 7 6 5 4 3 2 1 Time slot number 0 1 2 3 4 5 6 7

3.1.2 Compilation rules

In order to respect the compilation rules, all the structures defined in each message should be:

1) Aligned on 16 bits boundary when no field 4 bytes long are included in the structure.

Data Length

Data Length Modified

Padding

Data Length

Data Length

Padding



2006-2-22 3BK 09556 JAAA PBZZA 18/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

2) Aligned on 32 bits boundary when at least one field 4 bytes long is included in the structure. A parameter 2 bytes long should be aligned on 16 bits boundary.

3.1.3 Checking rules

The OMC parameters displayed on the customer interface are encoded in order to fit into parameter sent on internal interface. Therefore we defined two kind of representation:

The Telecom value (TEL) which is the same as the one shown at the customer level and, The Operation And Maintenance value (AOM) which the one sent on internal inteface.

In the following table the min, max and default value are the OAM ranges. Therefore in order to retrieve the TEL value describe in the BTP, you should use the coding rule. For example with MCS_AVG_PERIOD:

OAM value: Coding rule: tel = oam x 0,02 s TEL value: Min: 1 Min: 0,02 s Max: 250 Max: 5 s Default: 5 Default: 0,1 s

It could be notice that the coding rule repect the format displayed at customer level, so:

"tel = oam x 0,02 s" is different from "tel = oam x 20 ms" because of its representation

3.1.3.1 NOT Checked value

The following parameters are coming from the OMC without any treatment done by the PMU. Therefore NO check should be done.

Logical name Message parameter min max defau

ltcoding rule

CS_AVG_PERIOD_LT DspInitReq csAvgPeriodLt 1 250 100 tel = oam x 0,02 s

CS_AVG_PERIOD_ST DspInitReq csAvgPeriodSt 1 250 16 tel = oam x 0,02 s

CS_HST_DL_LT DspInitReq csHstDlLt 0 60 5 tel = oam / 10

CS_HST_DL_ST DspInitReq csHstDlSt 0 60 15 tel = oam / 10

CS_HST_UL_LT DspInitReq csHstUlLt 0 60 5 tel = oam / 10

CS_HST_UL_ST DspInitReq csHstUlSt 0 60 15 tel = oam / 10

CS_QUAL_DL_1_2_FH_ACK DspInitReq csQualDl12FhAck 0 70 60 tel = oam / 10

CS_QUAL_DL_1_2_FH_NACK DspInitReq csQualDl12FhNack 0 70 30 tel = oam / 10

CS_QUAL_DL_1_2_NFH_ACK DspInitReq csQualDl12NfhAck 0 70 50 tel = oam / 10

CS_QUAL_DL_1_2_NFH_NACK DspInitReq csQualDl12NfhNack 0 70 30 tel = oam / 10









CS_QUAL_UL_1_2_FH_ACK DspInitReq csQualUl12FhAck 30 100 90 tel = (oam - 30) / 10



2006-2-22 3BK 09556 JAAA PBZZA 19/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

CS_QUAL_UL_1_2_FH_NACK DspInitReq csQualUl12FhNack 30 100 60 tel = (oam - 30) / 10

CS_QUAL_UL_1_2_NFH_ACK DspInitReq csQualUl12NfhAck 30 100 80 tel = (oam - 30) / 10

CS_QUAL_UL_1_2_NFH_NACK DspInitReq csQualUl12NfhNack 30 100 60 tel = (oam - 30) / 10

CS_QUAL_UL_2_3_FH_ACK DspInitReq csQualUl23FhAck 0 70 40 tel = oam / 10

CS_QUAL_UL_2_3_FH_NACK DspInitReq csQualUl23FhNack 0 70 20 tel = oam / 10

CS_QUAL_UL_2_3_NFH_ACK DspInitReq csQualUl23NfhAck 0 70 35 tel = oam / 10

CS_QUAL_UL_2_3_NFH_NACK DspInitReq csQualUl23NfhNack 0 70 20 tel = oam / 10

CS_QUAL_UL_3_4_FH_ACK DspInitReq csQualUl34FhAck 0 70 5 tel = oam / 10

CS_QUAL_UL_3_4_FH_NACK DspInitReq csQualUl34FhNack 0 70 0 tel = oam / 10

CS_QUAL_UL_3_4_NFH_ACK DspInitReq csQualUl34NfhAck 0 70 5 tel = oam / 10

CS_QUAL_UL_3_4_NFH_NACK DspInitReq csQualUl34NfhNack 0 70 0 tel = oam / 10

CS_SIR_DL_3_4_FH_ACK DspInitReq csSirDl34FhAck 0 150 140 tel = oam / 10

CS_SIR_DL_3_4_FH_NACK DspInitReq csSirDl34FhNack 0 150 150 tel = oam / 10

CS_SIR_DL_3_4_NFH_ACK DspInitReq csSirDl34NfhAck 0 150 130 tel = oam / 10

CS_SIR_DL_3_4_NFH_NACK DspInitReq csSirDl34NfhNack 0 150 150 tel = oam / 10

CS_SIR_HST_DL DspInitReq csSirHstDl 0 150 10 tel = oam / 10

DSP_LOAD_FORGETTING_FACTOR

DspInitReq dspLoadForgettingFactor 1 128 26 --

DSP_LOAD_THR_1 DspInitReq dspLoadThr1 1 95 85 tel = oam x 1 %

DSP_LOAD_THR_2 DspInitReq DspLoadThr2 1 95 95 tel = oam x 1 %

EGPRS_DL_Ack_Factor DspInitReq egprsDlAckFactor 0 100 25 step size = 1

EGPRS_DL_ACK_factor_Satellite DspInitReq egprsDlAckFactorSatellite 0 100 25 step size = 1

EGPRS_N3105_LIMIT DspInitReq egprsN3105Limit 1 32 20 --

EGPRS_N3105_LIMIT_SATELLITE DspInitReq egprsN3105LimitSatellite 1 32 24 --

EGPRS_UL_Ack_Factor DspInitReq egprsUlAckFactor 0 100 25 step size = 1

EGPRS_UL_Ack_Factor_Satellite DspInitReq egprsUlAckFactorSatellite 0 100 25 step size = 1

EN_FULL_IR_DL DspInitReq enFullIrDl 0 1 0 0: Disable the full IR, so : Incremental Redundancy with resegmentation allowed in DL, 1: Enable the full IR, so, Incremental Redundancy without resegmentation in DL

EN_DL_RETRANS_BTS DspInitReq enDlRetransBts 0 1 1 0 : disabled, 1 : enabled

EN_FAST_USF_UL_EXTENDED DspInitReq enFastUsfUlExtended 0 1 1 0: disabled, 1: enabled

EN_RESEGMENTATION_UL DspInitReq enResegmentationUl 0 1 0 0: Disabled, 1: Enabled

E_TX_EFFICIENCY_PERIOD DspInitReq eTxEfficiencyPeriod 1 500 200 step size = 1

GPRS_DL_Ack_period DspInitReq gprsDlAckPeriod 3 64 12 step size = 1

GPRS_DL_Ack_period_Satellite DspInitReq gprsDlAckPeriodSatellite 3 64 12 step size = 1

GPRS_UL_Ack_period DspInitReq gprsUlAckPeriod 3 64 16 step size =1

GPRS_UL_Ack_period_Satellite DspInitReq gprsUlAckPeriodSatellite 3 64 16 step size =1

Max_PPCH_DRX_Occurrences DspInitReq maxPpchDrxOccurrences 1 32 9 --

Max_PPCH_Non_DRX_Lifetime DspInitReq maxPpchNonDrxLifeTime 1 160 5 tel = oam x 100 ms

MCS_AVG_PERIOD DspInitReq mcsAvgPeriod 1 250 5 tel = oam x 0,02 s

MIN_RLF_TIME_DL DspInitReq minRlfTimeDl 0 250 40 tel = oam x 100 ms

N3101_LIMIT DspInitReq n3101Limit 10 64 64 --



N3105_LIMIT_SATELLITE DspInitReq n3105LimitSatellite 1 64 24 --

N_stagnating_Window_DL_LIMIT DspInitReq nStagnatingWindowDlLimit 1 256 32 --

N_stagnating_Window_UL_LIMIT DspInitReq nStagnatingWindowUlLimit 1 256 10 --

N_PDCH_Release DspInitReq nPdchRelease 0 100 10 step size: 1

N_UL_Dummy_LIMIT DspInitReq nUlDummyLimit 12 128 15 --

N_UL_Errors_LIMIT DspInitReq nUlErrorsLimit 1 16 8 --



2006-2-22 3BK 09556 JAAA PBZZA 20/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PDCH_BUFFERING_FACTOR DspInitReq pdchBufferingFactor 1 65535 25 --

PDCH_MIN_BUFFERING_FACTOR DspInitReq pdchMinBufferingFactor 1 65535 5 --

PDCH_TBF_XON_FACTOR DspInitReq pdchTbfXonFactor 1 65535 15 --

TBF_CS3_BLER_PERIOD DspInitReq tbfCs3BlerPeriod 1 512 32 step size = 1

TBF_CS4_BLER_PERIOD DspInitReq tbfCs4BlerPeriod 1 512 32 step size = 1

CS_BLER_DL_3_4 DspInitReq csBlerDl34 0 100 5 step size = 1

CS_BLER_DL_4_3 DspInitReq csBlerDl43 0 100 15 step size = 1

TBF_CS_DL DspInitReq tbfCsDl 0 15 8 step size = 1

TBF_CS_PERIOD DspInitReq tbfCsPeriod 1 256 20 --

TBF_CS_UL DspInitReq tbfCsUl 1 64 32 step size = 1

TBF_MCS_DL DspInitReq tbfMcsDl 0 15 12 step size = 1

TBF_MCS_PERIOD DspInitReq tbfMcsPeriod 1 256 20 step size = 1

TBF_MCS_UL DspInitReq tbfMcsUl 1 192 32 step size = 1

T_CONFIG_TBF DspInitReq tConfigTbf 10 20 14 tel = oam x 20 ms

T_DSP_LOAD_REPORT DspInitReq tDspLoadReport 1 100 10 tel = oam x 100 ms

T_EXTENDED_UL_TBF_POL DspInitReq tExtendedUlTbfPol 6 25 10 tel = oam x 20 ms

THRES_DSP_XOFF DspInitReq thresDspXoff 0 1000 840 tel = oam x 0,1 %

THRES_DSP_XON DspInitReq thresDspXOn 0 1000 800 tel = oam x 0,1 %

THRES_G_MAX_HIGH DspInitReq thresGMaxHigh 0 1000 959 tel = oam x 0,1 %

THRES_G_MAX_LOW DspInitReq thresGMaxLow 0 1000 850 tel = oam x 0,1 %

THRES_N_TBF_OFF DspInitReq thresNTbfOff 0 1000 790 tel = oam x 0,1 %

THRES_N_TBF_ON DspInitReq thresNTbfOn 0 1000 750 tel = oam x 0,1 %

T_MAX_FOR_TBF_SCHEDULING DspInitReq tMaxForTbfScheduling 6 250 15 tel = oam x 20 ms

Treq_pending DspInitReq treqPending 25 160 50 tel = oam x 20 ms

T_MAX_FOR_MS_SYNCHRO DspInitReq tMaxForMsSynchro 15 17 16 tel = oam x 20 ms

T_PSI_PACCH DspInitReq tPsiPacch 0 30 14 step size =1sec, 00000 == Deactivated PSI scheduling on PACCH, 00001 == 1s, � 111100 == T_PSI_PACCH = 30 sec

T_TBF_ACTIV DspInitReq tTbfActiv 1 50 5 tel = oam x 0,1 s

T_TBF_BCK_REL DspInitReq tTbfBckRel 15 100 30 tel = oam x 0,1 s

TX_EFFICIENCY_PERIOD DspInitReq txEfficiencyPeriod 1 500 200 tel = oam x 1 %

USF_NE DspInitReq usfNe 0 6 0 step size = 1.

BS_PRR_BLKS_MPDCH TrxCreateReq bsPrrBlksMpdch 1 12 2 6 possible values (1;2;3;4;6;12)

BS_PRR_BLKS TrxCreateReq bsPrrBlksSpdch 1 12 6 6 possible values (1;2;3;4;6;12)

BS_TXPWR_MAX (MFS) TrxCreateReq bsTxPwrMax 0 15 0 0 0 0 0 = 0 dB, 0 0 0 1 = -2 dB, 0 0 1 0 = -4 dB, ..., 1 1 1 1 = -30 dB

CS_MAX_IDLE_PERIOD TrxCreateReq csMaxIdlePeriod 0 250 34 tel = oam x 20 ms

DL_POLL_FACTOR TrxCreateReq dlPollFactor 1 16 1 --

GAMMA_TNx TrxCreateReq gammaTnx 0 31 15 Coded on 5 bits, step size=2dB, with 00000 == 0 dB, 00001 == 2 dB, ... 11111 == 62 dB.

NC_DL_RXQUAL_THR TrxCreateReq ncDlRxqualThr 0 70 70 step size = 0.1. At the OMC-R, the following values are displayed: �0�, �0.1�, �0.2�, �, �6.9�, �7 (Never)�.

NC_RXQUAL_AVG_PERIOD TrxCreateReq ncRxqualAvgPeriod 1 500 200 tel = oam x 20 ms

NC_RXQUAL_HYSTERESIS TrxCreateReq ncRxqualHysteresis 0 70 10 tel = oam / 10

NC_UL_RXQUAL_THR TrxCreateReq ncUlRxqualThr 0 70 70 step size = 0.1. At the OMC-R, the following values are displayed: �0�, �0.1�, �0.2�, �, �6.9�, �7 (Never)�

N_SIG_REPEAT TrxCreateReq nSigRepeat 0 7 1 step size: 1

PRACH_BUSY_THRES TrxCreateReq prachBusyThres 0 15 1 This parameter is encoded with a step size of 4 dB as follows: 0: -110 dBm, 1: -106 dBm, 2: -102 dBm, 3: -98 dBm, 4: -94 dBm, 5: -90 dBm, 6: -86 dBm, 7: -82 dBm, 8: -78 dBm, 9: -74 dBm, 10: -70 dBm, 11: -66 dBm, 12: -62 dBm, 13: -58 dBm, 14: -54 dBm, 15: -50 dBm

RACH_TA_FILTER (MFS) TrxCreateReq rachTaFilter 0 64 64 64: no filtering



2006-2-22 3BK 09556 JAAA PBZZA 21/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

round_trip_delay TrxCreateReq roundTripDelay 8 94 16 tel = oam x 10 ms

T_ACK_WAIT TrxCreateReq tAckWait 5 50 12 tel = oam x 0,1 s

Tcorr TrxCreateReq tcorr 1 20 2 tel = oam x 0,1 s

T_DL_EGPRS_MeasReport TrxCreateReq tDlEgprsMeasreport 3 150 10 tel = oam x 20 ms

T_DL_GPRS_MeasReport TrxCreateReq tDlGprsMeasreport 3 150 20 tel = oam x 20 ms

Tdsl TrxCreateReq tdsl 1 9 4 tel = oam x 100 ms

Testab TrxCreateReq testab 1 20 4 tel = oam x 0,1 s

Tfreeze TrxCreateReq tfreeze 1 12 5 tel = oam x 100 ms

T_NC_RXQUAL_VALID TrxCreateReq tNcRxqualValid 0 127 10 tel = oam x 0,1 s

T_PAG_CS (MFS) TrxCreateReq tpagCs 1 255 30 0 means infinite timer; tel =oam x 0.1s

T_PAG_PS (MFS) TrxCreateReq tpagPs 1 255 30 0 means infinite timer; tel =oam x 0.1s

Trelease TrxCreateReq trelease 2 12 5 tel = oam x 100 ms

TRTS_PS TrxCreateReq trtsPs 1 9 4 tel = oam x 100 ms

T_ul_assign_pccch TrxCreateReq tulAssignPccch 1 7 4 tel = oam x 0,1 s

Tusl TrxCreateReq tusl 1 9 4 tel = oam x 100 ms

TX_EFFICIENCY_ACK_THR TrxCreateReq txEfficiencyAckThr 0 100 10 tel = oam x 1 %

TX_EFFICIENCY_NACK_THR TrxCreateReq txEfficiencyNackThr 0 100 15 tel = oam x 1 %

UL_POLL_FACTOR TrxCreateReq ulPollFactor 1 16 1 --

WI_PR TrxCreateReq wiPr 0 255 3 --

3.1.3.2 Checked value

The following parameters are coming from the OMC but they are modified by PMU according to the required behaviour. Therefore a check should be done.

Logical name Message parameter min max default Coding_rule

ACCESS_BURST_TYPE TrxSysDefineReq accessBurstType 0 1 0 0 : 8 bits access bursts, 1 : 11 bits access bursts

BS_PAG_BLKS_RES TrxSysDefineReq bsPagBlksRes 1 10 2 coded on 4 bits (0001: 1, ..., 1010: 10) The codepoints 0000: 0, 1011: 11 and 1100: 12 are not supported by the ALCATEL BSS.

BS_PBCCH_BLKS TrxSysDefineReq bsPbcchBlks 0 3 3 coded on 2 bits : 00=Block B0 used for PBCCH, 01=Block B0, B6 used for PBCCH, 10=Block B0, B6, B3 used for PBCCH, 11=Block B0, B6, B3, B9 used for PBCCH

NB_TS_MPDCH (MFS) TrxSysDefineReq bsPccChans 0 4 0 --

BS_PRACH_BLKS TrxSysDefineReq bsPrachBlks 1 8 2 coded on 4 bits (0000: 0, .., 1000: 8)

NC_REPORTING_PERIOD_T TrxSysDefineReq ncReportingPeriodT 0 7 1 coded from 0 to 7 (0 0 0 : 0.48 sec , 0 0 1: 0.96 sec , 0 1 0 : 1.92 sec , 0 1 1: 3.84 sec, 1 0 0 : 7.68 sec , 1 0 1 : 15.36 sec , 1 1 0: 30.72 sec , 1 1 1: 61.44 sec) .

TSC TrxSysDefineReq TSC 0 7 0 coded over 3 bits



2006-2-22 3BK 09556 JAAA PBZZA 22/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Logical name Message parameter min max default Coding_rule

NETWORK_CONTROL_ORDER TbfEstablishReq networkControlOrder 0 4 0 0: NC0 mode of operation for all MS. All MS controls their cell reselections and no MS reports packet measurements to the BSS. 1: NC1 mode of operation for all MS. All MS controls their cell reselections but all the MS reports packet measurements to the BSS. (Not supported) 2: NC2 mode of operation for R99 onwards MS. The BSS controls the cell reselections of R99 onwards MS when in packet transfer mode or of R99 onwards MS when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS. 3: NC2 mode of operation for all MS. The BSS controls the cell reselections of all MS when in packet transfer mode or of all MS when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS. 4: Reserved for future use

MAX_PDCH_PER_TBF TbfEstablishReq pdchCount 1 5 5 --

T_DELAYED_DL_TBF_POL TbfEstablishReq TDelayedDlTbfPol (Note 1) 3 250 10 tel = oam x 20 ms

T_DELAYED_DL_TBF_POL_INITIAL TbfEstablishReq tDelayedDlTbfPolInitial 3 50 3 tel = oam x 20 ms

Note 1: The timer can be set to T_Delayed_DL_TBF_Pol_UL if there is concurrent UL TBF, the range of T_DELAYED_DL_TBF_POL_UL is from 50ms to 5s. And if there is no concurrent UL TBF, the timer will be set to T_DELAYED_DL_TBF_POL, the range is from 60ms to 500ms. So the range must be compatible with the two timers.

For the remaning parameters received in the message, a check should be done.

3.1.3.3 Constants values The following parameters are coming from the control station and can not be change.

Logical name parameter value coding rule

MAX_GCH_DSP MAX_GCH_DSP 120 --

MAX_MPDCH_DSP MAX_MPDCH_DSP 60 --

MAX_PDCH_DSP MAX_PDCH_DSP 120 --

MAX_RLC_blks_DSP MAX_RLC_BLKS_DSP 13000 --

MAX_TBF_DSP MAX_TBF_DSP 240 --

MAX_TRX_DSP MAX_TRX_DSP 60 --

T_MIN_POLL T_MIN_POLL 3 tel = oam x 20 ms

MAX_GCH_DSP_GP MAX_GCH_DSP_GP 480 --

MAX_MPDCH_DSP_GP MAX_MPDCH_DSP_GP 240 --

MAX_PDCH_DSP_GP MAX_PDCH_DSP_GP 480 --

MAX_RLC_blks_DSP_GP MAX_RLC_BLKS_DSP_GP 52000 --

MAX_TBF_DSP_GP MAX_TBF_DSP_GP 960 --

MAX_TRX_DSP_GP MAX_TRX_DSP_GP 240 --



2006-2-22 3BK 09556 JAAA PBZZA 23/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2 Class DSP

3.2.1 DSP-ALARM-ind

This message is used to report an alarm detected by the DSP to the PPC. Message type: DSP-ALARM-ind Direction: DSP to PPC

Header

Length Variable ≤ 296

Class DSP

Mtype DSP-ALARM-ind

Reference FFH

FFH

Padding (00H)

Padding (00H)

Byte Parameters Length

(in bytes) Semantic

DSP Alarm Indication 0 length 2 Length in bytes. Equal to N 2 alarmType 2 Type of the detected alarm 4 checksum 4 DSP Software Checksum 8 alarmNumber 2 Occurrence number of the alarm indication. It is incremented each

time an alarm indication is generated. 10 debugInfoType 2 Format of the Debug Info field.

0 DSP_general_Information 1 DSP_performance_information 2 PPC_interface_error 3 GCH_interface_error 4 Legible Trace

12

debugInfo x 4 (variable)

N �32 Consideri

ng that last byte is located

at N-1

Defined by debug Info Type

The filtering process of this message dumped in the logging file is in restriction in this proposal.



2006-2-22 3BK 09556 JAAA PBZZA 24/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.1.1 Alarm type

The filtering mask is managed by PMU through the xpuAAA.ini (refer to [ 5 ])

Alarm type

(bit representation) Filtering mask

(byte representation)

Cause

1111 xxxx yyyy zzzz NA Internal software fault, which cannot be recovered 0000 0001 yyyy zzzz 0100 0000 Internal software fault, which can be recovered,

There is no impact on Traffic (no PDU lost). 0000 0010 yyyy zzzz 0200 0000 Internal software fault, which can be recovered,

There is impact on Traffic (PDU lost). 0000 0100 yyyy zzzz 0400 0000 External protocol fault, which can be recovered,

There is no impact on Traffic (no PDU lost). 0000 1000 yyyy zzzz 0800 0000 External protocol fault, which can be recovered,

There is impact on Traffic (PDU lost). 0001 0000 yyyy zzzz 1000 0000 Using DSP_ALARM_ind as trace

(no error detected, but send an alarm ind for debug ) 0010 0000 yyyy zzzz Unmaskable Such alarm type can�t be masked.

The alarm type and filtering mask enable the filtering of DSP alarm indication. For example, to enable the detection of PDU lost caused by a external/internal protocol error, the Alarm filtering mask is set as 0200 | 0800 = 0A00.

3.2.1.2 Debug Info

3.2.1.2.1 DSP_general_information


(in bytes) Semantic

12 trxIndex 2 The TRX index from which the message come 14 radioTS 2 The time slot number from which the message come 16 pdchIndex 2 The PDCH index from which the message come 18 tbfIndex 2 The TBF index from which the message come 20 gchIndex 2 The GCH index from which the message come 22 padding1 2 24 mpdchIndex 2 The MPDCH index from which the message come 26 spare 2 28 padding 1 29 module 3 module identifier in ASCII 32 file 1 source file identifier from which the message come 33 code 1 alarm identifier 34 lineNumber 2 The line number in source file from which the message

come 36 debugInfo0 4 Other debug info 0 40 debugInfo1 4 Other debug info 1 44 debugInfo2 4 Other debug info 2



2006-2-22 3BK 09556 JAAA PBZZA 25/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.1.2.2 PPC_interface_error

The debug information content represents the message header.


(in bytes) Semantic

12 lengthMsb 1 The MSB value of length contained in the wrong message 13 lengthLsb 1 The LSB value of length contained in the wrong message 14 mclass 1 The value of class contained in the wrong message 15 mtype 1 The value of message type contained in the wrong

message 16 referenceMsb 1 The MSB value of reference contained in the wrong

message 17 referenceLsb 1 The LSB value of reference contained in the wrong

message 18 padding 2 Not used

3.2.1.2.3 GCH_interface_error

The debug information content represents the DMA register.


(in bytes) Semantic

12 dmaSecondReq0 4 DMA secondary register channel 0 used for GCH link 16 serialPortReg 4 Serial Port Register used for GCH link 20 dmaSecondReq1 4 DMA secondary register channel 1 used for GCH link

3.2.1.2.4 DSP_performance_information

The debug information content represents the Performance counter of the DSP (see DSP_GET_PM_CNF message content).

3.2.1.2.5 Legible Trace

This debug information provides legible trace for tester.


(in bytes)

Semantic

12 LegibleTrace 76 An ASCII string whose length is less than or equal to 76 bytes. Remaining bytes in the LegibleTrace will be filled with 0x00.



2006-2-22 3BK 09556 JAAA PBZZA 26/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.2 DSP-CONGESTION-ind

This message is used to indicate that the congestion threshold was reached. Message type: DSP-CONGESTION-ind Direction: DSP to PPC

Header

Length

00H

9CH

Class DSP

Mtype DSP-CONGESTION-ind

Reference FFh

FFh

Padding

Padding


(in bytes) Semantic

Dsp Congestion State 0 rlcCongestionState 1 0 NO_CONGESTION

1 N_TBF_OFF 2 G_XOFF ( see below for more explanations)

1 padding 3 4 time20ms 4 DSP internal SW time reference in step of 20 ms 8 time1ms 4 Number of steps of 1ms since the last update of Time_20ms.

12 lastInitializationDate 4 Date of last initialisation of performance measurement (which includes Telecom processing context and RLC memory occupancy ).It refers to Time_20ms (i.e. DSP internal SW time reference in step of 20 ms) An initialisation leads to reset counters and to set upper and lower tide marks of gauges to the current value.

Telecom processing context 16 gTrxCreated 4 current value of number of TRXs created 20 gTrxCreatedUpper 4 upper tide mark of number of TRXs created 24 gTrxCreatedLower 4 lower tide mark of number of TRXs created 28 gTbfActivated 4 current value of number of TBF activated 32 gTbfActivatedUpper 4 upper tide mark of number of TBF activated 36 gTbfActivatedLower 4 lower tide mark of number of TBF activated 40 gMPdchActivated 4 current value of number of Master channel activated 44 gMPdchActivatedUpper 4 upper tide mark of number of Master channel activated 48 gMPdchActivatedLower 4 lower tide mark of number of Master channel activated 52 gPdchActivated 4 current value of number of PDCH activated 56 gPdchActivatedUpper 4 upper tide mark of number of PDCH activated 60 gPdchActivatedLower 4 lower tide mark of number of PDCH activated 64 gGchCreated 4 current value of number of GCHs created 68 gGchCreatedUpper 4 upper tide mark of number of GCHs created 72 gGchCreatedLower 4 lower tide mark of number of GCHs created 76 gEgprsTbfActivated 4 current value of number of EGPRS TBF activated



2006-2-22 3BK 09556 JAAA PBZZA 27/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Byte Parameters Length (in bytes)

Semantic

80 gEgprsTbfActivatedUpper 4 upper tide mark of number of EGPRS TBF activated 84 gEgprsTbfActivatedLower 4 lower tide mark of number of EGPRS TBF activated

RLC memory occupancy 88 gFreeRlcResource 4 Current value of number of free RLC resources 92 gFreeRlcResourceUpper 4 upper tide mark of number of free RLC resources 96 gFreeRlcResourceLower 4 lower tide mark of number of free RLC resources

100 numberRlcResources 4 Number of RLC resources within the DSP memory 104 cGMaxCongestion 4 Counter of number of times G_MAX congestion has been entered 108 cGXoffCongestion 4 Counter of number of times G_XOFF congestion has been entered 112 cNTbfOffCongestion 4 Counter of number of times N_TBF_OFF congestion has been entered 116 gFreePagingResource 4 Current value of number of free Paging Resources 120 gFreePagingResourceUpper 4 Upper tide mark of number of free Paging Resources 124 gFreePagingResourceLower 4 Lower tide mark of number of free Paging Resources

RLC memory occupancy bis 128 numberPagingResources 4 Number of Paging resources within the DSP memory 132 cTimerActivated 4 Number of the timer activated in the DSP 136 gTimerActivatedUp 4 Upper tide mark of the number of the Timer activated in the DSP 140 cWrongGchPduReceiveGch 4 Number of wrong GCH PDUs received on the activated GCHs i.e. CRC

error and Zseq error. 144 Spare 4 Reserved

RLC_CONGESTION_STATE

0 NO_CONGESTION

In this state, TBF establishments are accepted and PPC can send Downlink LLC PDUs.

This value is sent when percentage of RLC resources used goes below THRES_N_TBF_ON (transition from N_TBF_OFF) defined in DSP-INIT-req.

1 N_TBF_OFF

In this state, TBF establishments are not accepted but PPC can send Downlink LLC PDUs.

This value is sent when percentage of RLC resources used goes above THRES_N_TBF_OFF (transition from NO_CONGESTION) or below THRES_G_XON (transition from G_XOFF) defined in DSP-INIT-req.

2 G_XOFF

In this state, TBF establishments are not accepted. When receiving this message PPC must stop sending downlink LLC PDUs.

This value is sent when percentage of RLC resources used goes above THRES_G_XOFF (transition from N_TBF_OFF) defined in DSP-INIT-req.

Additional DSP defence mechanism

In case of the �absolute congestion� (i.e. number of RLC resources used is greater than THRES_G_MAX_HIGH defined in DSP-INIT-req), congestion recovery is performed by DSP. DSP autonomously releases some existing TBF up to have RLC resources used lower than THRES_G_MAX_LOW. Despite TBF-RELEASE-ind messages sent for each TBF released, DSP-ALARM-ind is sent to indicate that congestion recovery has occurred and is completed.



2006-2-22 3BK 09556 JAAA PBZZA 28/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.3 DSP-INIT-req

This message is used to provide DSP configuration and layer configuration parameters (i.e. L2-GCH, MAC, RLC) not specific to one given cell. Message type: DSP-INIT-req Direction: PPC to DSP

Header

Length

00H

FCh

Class DSP

Mtype DSP-INIT-req

Reference FFh

FFh

Padding

Padding

Byte Parameters Lgth Semantic

RrmPDSPCfg

0 thresDspXoff 2 Threshold used for the RLC resource congestion management. Threshold above which downlink RLC PDU are not more sent by RRM to RLC.

2 thresDspXOn 2 Threshold used for the RLC resource congestion management. Threshold above which downlink RLC PDU sending from RRM to RLC becomes possible after having previously encountered a DSP congestion.

4 thresGMaxHigh 2 Resource threshold used to handle the transistion between G_XOFF and G_MAX congestion states.

6 thresGMaxLow 2 Resource threshold used to handle the transistion between G_MAX and G_XOFF congestion states.

8 thresNTbfOff 2 Management of DSP memory in GPU. Threshold above which TBF establishment is not possible.



2006-2-22 3BK 09556 JAAA PBZZA 29/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

10 thresNTbfOn 2 Management of DSP memory in GPU. Threshold under which TBF establishment becomes possible after previously encountered TBF congestion.

12 dspLoadForgettingFactor 2 Forgetting factor of the filter used to compute the CPU load of a DSP over the last 20 ms periods.

14 dspLoadThr1 2 Threshold beyond which a given DSP is considered as loaded in terms of CPU load by RRM.

16 dspLoadThr2 2 Threshold beyond which a given DSP is considered as overloaded in terms of CPU load by RRM.

18 tDspLoadReport 2 Period with which a given DSP reports its CPU load to RRM

20 spare4736 2

22 spare4737 2

24 spare4738 2

26 spare4739 2

28 spare4740 2

30 spare4741 2

RrmPRlcCfg

32 n3101Limit 2 In an UL TBF tranfer procedure, maximum of consecutive times (before releasing abnormally the UL TBF) when the network receives an invalid UL RLC data block or nothing from the MS on its allocated PDCH.

To note that the counter N3101 can be incremented more than one time per block period.



2006-2-22 3BK 09556 JAAA PBZZA 30/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

34 n3103Limit 2 In an UL TBF releasing procedure, maximum of consecutive times (before releasing abnormally the UL TBF) when the network does not receive a Packet Control Acknowledgement from the MS in response of its Packet UL ACK/NACK which specifies the end of the TBF.

36 n3105Limit 2 For a DL GPRS TBF, if the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the maximum number of expected Packet Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.

38 pdchBufferingFactor 2 The buffering delay factor associated to one PDCH that is shared between TBF accordingly to the TBF throughput.

40 pdchMinBufferingFactor 2 The minimum buffering delay between XON and XOFF thresholds that should be used according to the TBF throughput.

42 pdchTbfXonFactor 2 Anticipation number of RLC data blocks considering a throughput of one PDCH.

44 tTbfBckRel 2 Guard timer against blocking situations where a RLC/MAC control block is expected from the MS.

Triggering condition: End of UL TBF (an expected Packet Control Ack is not received), End of DL TBF (an expected Packet Downlink Ack/Nack with FINAL indication set to 1 is not received for acknowledged mode and Packet Control Acknowledgement for unacknowledged mode), Tx window of DL TBF stalled (an expected Packet Downlink Ack/Nack is not received). Reseting condition: Receipt of a RLC/MAC control block. Action on expiry; Release of a TBF

46 egprsN3105Limit 2 For a DL EGPRS TBF, if the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the maximum number of expected Packet Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.

48 spare575 2

50 tTbfActiv 2 Waiting time during which RLC layer is waiting for the first downlink LLC PDU. This timer is started on TBF activation in RLC layer. It is stopped on receipt of the first LLC PDU from RRM layer. On its expiry, the relevant TBF is released.

52 gprsDlAckPeriod 2 If the GPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the number of transmitted radio blocks necessary to request a Packet Downlink Ack/Nack in acknowledged mode.

54 gprsUlAckPeriod 2 If the GPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the number of received radio blocks necessary to send a Packet Uplink Ack/Nack in acknowledged mode.



2006-2-22 3BK 09556 JAAA PBZZA 31/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

56 egprsUlAckFactor 2 If the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the ratio between the number of received RLC data blocks necessary to send a Packet Uplink Ack/Nack in acknowledged mode, and the RLC window size.

58 egprsDlAckFactor 2 If the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the ratio between the number of transmitted RLC data blocks necessary to request for a EGPRS Packet Downlink Ack Nack in acknowledged mode, and the RLC window size

60 nStagnatingWindowDlLimit 2 This parameter defines the maximum number of consecutive Packet Downlink ACK/NACK or EGPRS Packet Downlink ACK/NACK messages reporting the failure of progress of the RLC window during the active phase of a downlink TBF, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.

62 nStagnatingWindowUlLimit 2 NstagnatingWindow threshold limit above which a uplink TBF shall be released: the counter is incremented each time a Packet UL Ack/Nack fails in making the RLC window progress. For a multi-slot TBF or a TBF which shares its PDCH, the limit is proportional to the allocated bandwidth at the TBF establishment.

64 nUlDummyLimit 2 N_UL_Dummy threshold limit above which an uplink TBF shall be released: the counter is incremented each time the BSS receives a dummy block.

66 nUlErrorsLimit 2

Number of received erroneous UL RLC blocks above which the uplink TBF is released by the BSS.

68 spare1005 2

BssRlcCfg

70 txEfficiencyPeriod 2 Number of received RLC data blocks after which TX_EFFICIENCY is computed.

72 eTxEfficiencyPeriod 2 Number of received radio blocks for an EGPRS TBF after which E_TX_EFFICIENCY is computed.

74 enDlRetransBts 2 Enables / disables downlink retransmission in the BTS.

76 tMaxForTbfScheduling 2 Maximum time between two scheduling of a given NRT TBF (either between two DL block requests for a NRT DL TBF, or between two UL blocks received for a given NRT UL TBF).

78 tConfigTbf 2 Supervision timer for TBF context configuration in a TRX

80 enResegmentationUl 2 Enables/Disables the resegmentation for the uplink TBF in the BSS



2006-2-22 3BK 09556 JAAA PBZZA 32/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

82 minRlfTimeDl 2 Minimum time before detecting a radio link failure of a DL TBF due to very bad radio conditions. The parameters to trigger an abnormal release of a DL TBF are : N3105, NstagnatingWindowDL and TX_EFFICIENCY.

84 spare4652 2

86 spare4653 2

88 spare4654 2

BssRadioLinkAdaptationCfg

90 csHstDlLt 2 Hysteresis value for AV_RXQUAL_LT thresholds used in the downlink radio link supervision to change the TBF coding scheme.

92 csHstDlSt 2 Hysteresis value for AV_RXQUAL_ST thresholds used in the downlink radio link supervision to change the TBF coding scheme.

94 csHstUlLt 2 hysteresis value for AV_RXQUAL_LT thresholds used in the uplink radio link supervision to change the TBF coding scheme.

96 csHstUlSt 2 hysteresis value for AV_RXQUAL_ST thresholds used in the uplink radio link supervision to change the TBF coding scheme.

98 csQualDl12FhAck 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is acknowledged and the TBF is established on a hopping TRX.

100 csQualDl12FhNack 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is unacknowledged and the TBF is established on a hopping TRX.

102 csQualDl12NfhAck 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is acknowledged and the TBF is established on a non-hopping TRX.

104 csQualDl12NfhNack 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is unacknowledged and the TBF is established on a non-hopping TRX.






2006-2-22 3BK 09556 JAAA PBZZA 33/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.






122 csQualUl12FhAck 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a hopping TRX.

124 csQualUl12FhNack 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a hopping TRX.

126 csQualUl12NfhAck 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a non-hopping TRX.

128 csQualUl12NfhNack 2 RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a non-hopping TRX.

130 csQualUl23FhAck 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a hopping TRX.

132 csQualUl23FhNack 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a hopping TRX.

134 csQualUl23NfhAck 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a non-hopping TRX.

136 csQualUl23NfhNack 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a non-hopping TRX.



2006-2-22 3BK 09556 JAAA PBZZA 34/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

138 csQualUl34FhAck 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a hopping TRX.

140 csQualUl34FhNack 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a hopping TRX.

142 csQualUl34NfhAck 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the uplink direction when the RLC mode is acknowledged and the TBF is established on a non-hopping TRX.

144 csQualUl34NfhNack 2 Threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the uplink direction when the RLC mode is unacknowledged and the TBF is established on a non-hopping TRX.

146 csSirDl34FhAck 2 Signal to Interference Ratio threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the RLC mode is acknowledged and the TBF is established on a hopping TRX.

148 csSirDl34FhNack 2 Signal to Interference Ratio threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the RLC mode is unacknowledged and the TBF is established on a hopping TRX.

150 csSirDl34NfhAck 2 Signal to Interference Ratio threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the RLC mode is acknowledged and the TBF is established on a non-hopping TRX.

152 csSirDl34NfhNack 2 Signal to Interference Ratio threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the RLC mode is unacknowledged and the TBF is established on a non-hopping TRX.

154 csSirHstDl 2 Signal to Interference Ratio hysteresis used in the link adaptation algorithms to change the Coding Scheme from CS4 to CS3 in the downlink direction.

156 tbfCsDl 2 Threshold defining the number of consecutive Packet Downlink Ack/Nack not received above which the coding scheme of a downlink acknowledged or unacknowledged TBF is changed to CS1 (only in downlink).

158 tbfCsUl 2 Threshold defining the maximum number of consecutive times the network receives an invalid UL RLC data block or nothing from the MS having a monoslot GPRS TBF before changing the coding scheme to CS1. For a multislot GPRS TBF, TBF_CS_UL_limit := TBF_CS_UL x n_allocated

160 spare3319 2

162 csAvgPeriodSt 2 Forgetting time in the short term averaging of channel quality measurements in the GPRS link adaption:measurements which are older than CS_AVG_PERIOD_ST are negligible in in the average of channel quality measurements.



2006-2-22 3BK 09556 JAAA PBZZA 35/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

164 csAvgPeriodLt 2 Forgetting time in the long term averaging of channel quality measurements in the GPRS link Adaption: measurements which are older than CS_AVG_PERIOD_LT are negligible in in the average of channel quality measurements.

166 tbfCsPeriod 2 Number of RLC data blocks after which the CS adaption decision may be made, in GPRS.

BssEgprsRadioLinkAdaptationCfg

168 tbfMcsPeriod 2 Number of radio blocks after which the MCS adaption decision may be made, in EGPRS.

170 mcsAvgPeriod 2 Period Tegprs after which a weight of 0.9 is applied to the current UL or DL meanBEP samples in the averaging Modulation and Coding Scheme adaptation filter.

172 spare3209 2

174 tbfMcsUl 2 Threshold defining the maximum number of consecutive times the network receives an invalid UL RLC data block or nothing from the MS having a monoslot EGPRS TBF before changing the coding scheme to MCS1. For a multislot EGPRS TBF, TBF_MCS_UL_limit := TBF_MCS_UL x n_allocated_timeslots.

176 tbfMcsDl 2 Threshold defining the number of consecutive EGPRS PACKET DOWNLINK ACK/NACK not received above which the MCS of a DL acknowledged or unacknowledged DL TBF is changed to MCS-1.

178 tbfCs3BlerPeriod 2 Defines the window size required to estimate the CS3 BLER. The window size is expressed as a number of DL RLC data blocks.

180 tbfCs4BlerPeriod 2 Defines the window size required to estimate the CS4 BLER. The window size is expressed as a number of DL RLC data blocks.

182 csBlerDl34 2 CS3 BLER threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the SIR measurements are not reported by the MS

184 csBlerDl43 2 CS4 BLER threshold used in the link adaptation algorithms to change the Coding Scheme from CS4 to CS3 in the downlink direction when the SIR measurements are not reported by the MS.

186 enFullIrDl 2 Enables/Disables the resegmentation for the downlink TBF in the cell.

BssSatelliteProfileCfg

188 egprsDlAckFactorSatellite 2 If the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the downlink EGPRS ARQ period factor: Acknowledgement period over window size ratio.



2006-2-22 3BK 09556 JAAA PBZZA 36/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

190 egprsUlAckFactorSatellite 2 If the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the ratio between the number of received RLC data blocks necessary to send a Packet Uplink Ack/Nack in acknowledged mode, and the RLC window size.

192 gprsDlAckPeriodSatellite 2 If the GPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the number of transmitted radio blocks necessary to request a Packet Downlink Ack/Nack in acknowledged mode.

194 gprsUlAckPeriodSatellite 2 If the GPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the number of received radio blocks necessary to send a Packet Uplink Ack/Nack in acknowledged mode.

196 egprsN3105LimitSatellite 2 For a DL EGPRS TBF, if the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the maximum number of expected Packet Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.

198 n3105LimitSatellite 2 For a DL GPRS TBF, if the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the maximum number of expected Packet Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.

200 spare3494 2

202 spare3495 2

204 spare3496 2

206 spare3497 2

208 spare3498 2

210 spare3500 2

212 spare3501 2

214 spare3514 2

BssMacCfg

216 tPsiPacch 2 Scheduling period of PSI1, PSI13 or PSI14 on PACCH

218 enFastUsfUlExtended 2 Disable/enable the transmission of USF every 20ms in extended mode

220 tExtendedUlTbfPol 2 To control the USF scheduling on the uplink when a TBF is in extended TBF mode



2006-2-22 3BK 09556 JAAA PBZZA 37/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

222 spare4457 2

224 spare4458 2

RrmPMacCfg

226 usfNe 2 USF �No emission� used to schedule UL signalling of TBF without USF.

228 nPdchRelease 2 Number of repetitions of a Packet PDCH Release message.

230 maxPpchNonDrxLifeTime 2 Time limit for the sending of a paging, a Packet Downlink Assignment or a Packet Cell Change Order when the addressed MS is in non-DRX mode.

232 maxPpchDrxOccurrences 2 Maximum number of paging occurrences tested for the sending of a paging, a Packet Downlink Assignment or a Packet Cell Change Order when the addressed MS is in DRX mode.

234 treqPending 2 Maximum time during which a GCH establishment or release request from PMU can be delayed in MEGCH layer.

236 tMaxForMsSynchro 2 Timer per PDCH used to monitor the maximum time between the sending of two DL blocks which could be decoded by all the active mobiles having their PACCH supported on the PDCH.

238 spare672 2

240 spare674 2

242 spare675 2

All These parameters are OAM encoding, so the DSP has to use the coding rules to retrieve the Telecom value (no encoding or decoding is done in PPC software).



2006-2-22 3BK 09556 JAAA PBZZA 38/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.4 DSP-INIT-cnf

This message is used to confirm DSP configuration and layer configuration of parameters (i.e. L2-GCH, MAC, and RLC). Message type: DSP-INIT-cnf Direction: DSP to PPC

Header

Length

00H

5CH

Class DSP

Mtype DSP-INIT-cnf

Reference FFh

FFh

Padding

Padding


(in bytes)

Semantic Range

Short Confirmation 0 ackNack 1 Result of the Request 00H = Ack (Success) ,

01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure See 4.4 2 debugInfo 2 Index of the first field of message content in DSP-

INIT-req not compliant with checking rules This index is calculated from the first byte after the header of DSP-INIT-req

See 4.7

Intrinsic DSP parameters 4 maxRlcResources 4 Maximum number of RLC resources reserved for

partition where RLC associated to LLC PDU, Packet Uplink Assignment (PUA) and Packet Downlink Assignment (PDA) and paging are stored. To be compliant with dimensioning requirements, it should be greater or equal to Dimensioning RLC for LLC PDU + Dimensioning RLC for PUA/PDA

See § 3.1.3.3 MAX_RLC_blks_DSP

8 dimensioningRlcLlcPdu 4 Dimensioning requested for RLC resources associated to LLC PDU Based on a certain number of RLC per TBF. This value is not used by the software (see Max_RLC resources).

12 dimensioningRlcPuaPda 4 Dimensioning requested for RLC resources associated to Packet Uplink Assignment (PUA) and Packet Downlink Assignment (PDA). This value is not used by the software (see Max_RLC resources).



2006-2-22 3BK 09556 JAAA PBZZA 39/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Byte Parameters Length (in

bytes)

Semantic Range

16 gMaxLimit 4 Maximum value for THRES_G_MAX_HIGH threshold 20 nbPagingBlksDsp 4 Maximum number of resources for stocking the

paging messages

Intrinsic RLC parameters 24 maxTbfDsp

2 Maximum number of TBFs supported per GPU/DSP

sub-system See § 3.1.3.3

26 maxEgprsWindowSize

2 Maximum EGPRS window size supported in the DSP sub-system

See note

Intrinsic MAC parameters 28 maxPdchDsp

2 Maximum number of PDCHs supported per GPU/DSP

sub-system

30 maxTrxDsp

2 Maximum number of TRX supported per GPU/DSP sub-system

See § 3.1.3.3

32 maxMPdchDsp

2 Maximum number of master PDCHs supported per GPU/DSP sub-system

See § 3.1.3.3 and note

34 maxDlTbfPdch

2 Maximum number of Downlink TBFs per PDCH

36 maxUlTbfPdch

2 Maximum number of Uplink TBFs per PDCH

38 nbBlksInUlTable 1 Size of the Uplink reservation table 39 nbBlksInFutureTable 1 Size of the part of the Uplink reservation table used

for the future

40 nbBlksInPastTable 1 Size of the part of the Uplink reservation table used for the past

41 nTc 1 Number of throughput classes 42 maxGchDsp 2 Maximum number of GCH per dsp See § 3.1.3.3

44 Spare 40 Reserved

In this release, the maximum window size supported by the DSP is fixed and set to 512.

3.2.5 DSP-MODIFY-req

This message is used to modify layer configuration parameters (i.e. L2-GCH, MAC, RLC) not specific to one given cell. Message type: DSP-MODIFY-req Direction: PPC to DSP

Header

Length

As for DSP-INIT-req

Class DSP

Mtype DSP-MODIFY-req

Reference FFh

FFh

Padding

Padding



2006-2-22 3BK 09556 JAAA PBZZA 40/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

The parameters structures are the same as in Dsp-init-req but not all parameters are significant, i.e. some values are present in the message but not interpreted by PTU SW, as they are not on-line changeable.

3.2.5.1 DSP parameters RrmPDSPCfg structure is not changeable i.e. None (DLS).

3.2.5.2 RLC parameters RrmPRlcCfg structure is not changeable i.e. None (DLS). BssRlcCfg structure is changeable. BssRadioLinkAdaptationCfg structure is changeable except for the 3 last one. BssEgprsRadioLinkAdaptationCfg structure is changeable except for the 2 first one. BssSatelliteProfileCfg structure is not changeable i.e. None (DLS)

3.2.5.3 MAC parameters MacDspInfoCfg structure is changeable. BssMacCfg structure is changeable. RrmPMacCfg structure is not changeable i.e. None (DLS)



2006-2-22 3BK 09556 JAAA PBZZA 41/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.6 DSP-MODIFY-cnf

This message is used to confirm the layer configuration of parameters (i.e. L2-GCH, MAC, and RLC). Message type: DSP-MODIFY-cnf Direction: DSP to PPC

For consistency purpose, no description is provided as first definition should be based on DSP_INIT-cnf.

Header

Length

00H

0CH

Class DSP

Mtype DSP-MODIFY-cnf

Reference FFh

FFh

Padding

Padding


(in bytes)

Semantic Range

Short Confirmation 0 ackNack 1 Result of the Request 00H = Ack (Success) ,

01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure See 4.4 2 debugInfo 2 Byte index of the field in DSP-INIT-req not

compliant with checking rules See 4.7



2006-2-22 3BK 09556 JAAA PBZZA 42/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.7 DSP-PAGE-MS-req

This message is used to send a Packet Paging Request PDU to the MS in every provided cell. Message type: DSP-PAGE-MS-req Direction: PPC to DSP

Header

Length

Variable

Class DSP

Mtype DSP-PAGE-MS-req

Reference FFH

FFH

Padding

Padding


(in bytes) Semantic Range

DSP Page MS Configuration 0 splitPgCycle 1 DRX parameter used to compute the paging group 0...32

0: no DRX 1 imsi 9 International Mobile Station Identity See 4.11

10 nbMpdch 1 Number of MPDCHs on which a paging is to be sent 1... maxMPdchDsp 11 pduBlockType 1 See 4.3 12 pduBlock 24 See 4.1 36 rrmQueuingTime 2 Queuing time for paging in RRM 0 : 0 ms

1 : 100 ms 2 : 200 ms � 255 : 25,5 s NIL (FFFFH) see note

38 spare 2

TRX PDCH List 40 trxIndex[0] 2 TRX Index 0...maxNbTrx-1, NIL

(FFFFH) 42 radioTS[0] 1 Time slot number 0....7 43 padding 1

� N trxIndex [nbMpdch � 1] 2 TRX Index 0.�maxNbTrx-1, NIL

(FFFFH) n+1 radioTS [nbMpdch -1] 1 Time slot number 0�7 n+2 padding 1

n = 40 + 4 * nbMpdch. Therefore Message Length is less or equal to 48 + 4 * maxMPdchDsp

Note: When rrmQueuingTime is set to NIL, it means that the paging request has not been queued in RRM (i.e. rrmQueuingTime is equal to 0 ms).



2006-2-22 3BK 09556 JAAA PBZZA 43/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

BLOCK TYPE

Paging PS

Paging CS

The IMSI in the message is used to compute the paging group of the mobile in DRX mode i.e. to insert the packet paging request in the correct block number listen by the mobile. Therefore when RRM doesn't know the IMSI of the mobile, the only way to join the mobile is to send the packet paging request as soon as it's possible i.e. in non DRX mode. So if the splitPgCycle is set to 0, the IMSI is not relevant; or if RRM does not provide the IMSI than the splitPgCycle must be set to 0.

For the BLOCK IE, Either the IMSI, or the TMSI of the mobile could be provided. This choice is given to reduce the size of the packet paging content and to ease the concatenation of more than 2 paging request in the same radio block.

3.2.8 DSP-PAGE-MS-cnf

This message is used to indicate that the Paging message has been processed. Message type: DSP-PAGE-MS-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class DSP

Mtype DSP-PAGE-MS-cnf

Reference FFH

FFH

Padding

Padding



Long Confirmation 0 ackNack 1 Result of the Request (*) 00H = Ack (Success) ,

01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure See 4.4 2 debugInfo 6 Byte index of the field in DSP-PAGE-MS-Req not compliant

with checking rules. Byte index is calculated from the first byte after the header (ACK _NACK index)

The PMU can send a new DSP-PAGE-MS-Req only when it has received the DSP-PAGE-MS-cnf related to the preceding DSP-PAGE-MS-Req.



2006-2-22 3BK 09556 JAAA PBZZA 44/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.9 DSP-TRANSPARENT-req (provision for DSP internal usage) Message type: DSP-TRANSPARENT-req Direction: PPC to DSP

Header

Length

Variable ≤ 1644 bytes multiple of 4 bytes

Class DSP

Mtype DSP-TRANSPARENT-req

Reference Message reference

Padding

Padding

Message reference is set by the sender and will be given in DSP-TRANSPARENT-cnf Message defined as a provision for DSP internal usage.

3.2.10 DSP-TRANSPARENT-cnf (provision for DSP internal usage) Message type: DSP-TRANSPARENT-cnf Direction: DSP to PPC

Header


Class DSP

Mtype DSP-TRANSPARENT-cnf


Padding (00H)

Padding (00H)

Message reference is the one received in DSP-TRANSPARENT-req Message defined as a provision for DSP internal usage.



2006-2-22 3BK 09556 JAAA PBZZA 45/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.11 DSP-TRANSPARENT-DUMP-req

This message is used to trigger the dump of Dsp memory transparently from PPC Message type: DSP-TRANSPARENT-DUMP-req Direction: PPC to DSP

Header

Length 00H

14H

Class DSP

Mtype DSP-TRANSPARENT-DUMP-req


Padding (00H)

Padding (00H)

Message reference is set by the sender and will be given in DSP-TRANSPARENT-DUMP-cnf


(in bytes)

Semantic

Memory Dump Configuration 0 startAddressIndex 4 Index defines the base address managed by

software table allowing to have a direct addressing of significant data independent from mapping (see below)

4 startAddressOffset 4 Defines the offset to be added to the address associated to �start address base index�

8 length 4 length of the data to be dumped length ≤ 1620

DUMP START ADDRESS = DSP_ADDR_BASE (start address base index) + start address offset Where DSP_ADDR_BASE is a table of significant DSP address. Index Base address 1 to n to be defined at design level 00 00 00 00h



2006-2-22 3BK 09556 JAAA PBZZA 46/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.12 DSP-TRANSPARENT-DUMP-cnf

This message is used to report the dump of Dsp memory transparently to PPC Message type: DSP-TRANSPARENT-DUMP-cnf Direction: DSP to PPC

Header

Length variable ≤ 1636

Class DSP

Mtype DSP-TRANSPARENT-DUMP-cnf


Padding (00H)

Padding (00H)

Message reference is the one received in DSP-TRANSPARENT- DUMP �req


(in bytes)

Semantic

DSP Data 0 length 2 length in bytes. 2 spare 2 4 time20ms 4 DSP internal SW time reference in step of 20

ms (synchronized on GCH time)

8 dumpedData

variable(≤ 1620)

Dumped data bytes



2006-2-22 3BK 09556 JAAA PBZZA 47/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.13 DSP-TRANSPARENT-MODIFY-req

This message is used to trigger the modification of the Dsp memory transparently from PPC Message type: DSP-TRANSPARENT-MODIFY-req Direction: PPC to DSP

Header


Class DSP

Mtype DSP-TRANSPARENT-MODIFY-req


Padding (00H)

Padding (00H)

Message reference is set by the sender and will be given in DSP-TRANSPARENT-MODIFY-cnf


Semantic

Memory Modify Configuration 0 length 4 length in bytes. Equal to N 4 startAddressIndex 4 Index defines the base address managed by software table

allowing to have a direct addressing of significant data independent from mapping (see below)

8 startAddressOffset 4 Defines the offset to be added to the address associated to �start address base index�

12 writtenDataLength 4 length of the data to be modify length ≤ 1620

16 writtenData variable DATA to write x padding if necessary variable No padding if length of data to write = 4n

Padding of 1 byte if length of data to write = 4n- 1 Padding of 2 bytes if length of data to write = 4n- 2 Padding of 3 bytes if length of data to write = 4n- 3



2006-2-22 3BK 09556 JAAA PBZZA 48/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.14 DSP-TRANSPARENT-MODIFY-cnf

This message is used to acknowledge the modification of the Dsp memory transparently to PPC Message type: DSP-TRANSPARENT-MODIFY-cnf Direction: DSP to PPC

Header

Length 00H

0CH

Class DSP

Mtype DSP-TRANSPARENT-MODIFY-cnf


Padding (00H)

Padding (00H)

Message reference is the one received in DSP-TRANSPARENT-MODIFY-req


Semantic

Transparent Confirmation 4 time20ms 4 DSP internal SW time reference in step of 20 ms

(synchronized on GCH time)



2006-2-22 3BK 09556 JAAA PBZZA 49/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.15 DSP-TRANSPARENT-PERF-req

This message is used to trigger the report of Dsp performances transparently from PPC Message type: DSP-TRANSPARENT-PERF-req Direction: PPC to DSP

Header

Length 00H

0CH

Class DSP

Mtype DSP-TRANSPARENT-PERF-req


Padding (00H)

Padding (00H)

Message reference is set by the sender and will be given in DSP-TRANSPARENT-PERF-cnf


Semantic

Performance Request 0 reinit 1 initialization

Performance counters and gauges are reported and then reinitialized. ≠ 0 No initialization Performances counters and gauges are reported

1 spare 3



2006-2-22 3BK 09556 JAAA PBZZA 50/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.16 DSP-TRANSPARENT-PERF-cnf

This message is used to report Dsp performances transparently to PPC Message type: DSP-TRANSPARENT-PERF-cnf Direction: DSP to PPC

Header

Length 01H

24H

Class DSP

Mtype DSP-TRANSPARENT-PERF-cnf


Padding (00H)

Padding (00H)

Message reference is the one received in DSP-TRANSPARENT-PERF-req


Semantic

DSP Data 0 length 2 length in bytes. 2 spare 2 4 time20ms 4 DSP internal SW time reference in step of 20 ms



bytes) Semantic

Same structure of PM counter as in DSP-GET-PM-cnf for the DSP (i.e. from �last initialization� field to �spare� field)



2006-2-22 3BK 09556 JAAA PBZZA 51/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.17 DSP-TRANSPARENT-PPC-req

This message is used to send a message to DSP as if it was sent from PPC. Only the sending is transparent to PPC (DSP processing is identical to the one performed if message was directly received from PPC) Message type: DSP-TRANSPARENT-PPC-req Direction: PPC to DSP

Header


Class DSP

Mtype DSP-TRANSPARENT-PPC-req


Padding (00H)

Padding (00H)

Message reference is set by the sender and will be given in DSP-TRANSPARENT-PPC-cnf


Semantic

PCC Data 0 ppcMessage variable One of the PPC message (except transparent message)



2006-2-22 3BK 09556 JAAA PBZZA 52/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.18 DSP-TRANSPARENT-PPC-cnf

This message is used to acknowledge the sending of PPC message transparently to PPC Message type: DSP-TRANSPARENT-PPC-cnf Direction: DSP to PPC

Header

Length 00H

0CH

Class DSP

Mtype DSP-TRANSPARENT-PPC-cnf


Padding (00H)

Padding (00H)

Message reference is the one received in DSP-TRANSPARENT-PPC-req


(in bytes)

Semantic

Transparent Confirmation 4 time20ms 4 DSP internal SW time reference in step of 20 ms




2006-2-22 3BK 09556 JAAA PBZZA 53/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.19 DSP-TRANSPARENT-TRACE-Ind

This message is used to send a trace message from the PTU to the PMU Message type: DSP-TRANSPARENT-TRACE-ind Direction: DSP to PPC

Header


Class DSP

Mtype DSP-TRANSPARENT-TRACE-Ind


Padding (00H)

Padding (00H)


Semantic

Trace Indication 0 length[0] 2 Length of data field + 12 2 spare[0] 1 3 reference[0] 1 Trace reference 4 id[0] 4 Trace identification 8 time[0] 4 Time in milliseconds

12 data[0] Variable Trace Data 0 �

n+0 length[i-1] 2 Length of data field + 12 n+2 spare[i-1] 1 n+3 reference[i-1] 1 Trace reference n+4 id[i-1] 4 Trace identification n+8 time[i-1] 4 Time in milliseconds n+12 data[i-1] Variable Trace Data i-1



2006-2-22 3BK 09556 JAAA PBZZA 54/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.20 DSP-GET-PM-req

This message is used to request the DSP global (not specific to one given) PM counters related to a given DSP. Message type: DSP-GET-PM-req Direction: PPC to DSP

Header

Length

00H

0CH

Class DSP

Mtype DSP-GET-PM-req

Reference FFh 00H

FFh

Padding

Padding



Performace Request 1 reinit 1 This flag is used to request to DSP to reset the counters 0: Reinit requested

FFH : Reinit not requested

2 spare 3



2006-2-22 3BK 09556 JAAA PBZZA 55/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.21 DSP-GET-PM-cnf

This message is used to report DSP performance information, which includes:

DSP processing load

Telecom processing context

PPC interface counters

RLC memory occupancy

internal DSP supervision

Message type: DSP-GET-PM-cnf Direction: DSP to PPC

Header

Length 01H

1CH

Class DSP

Mtype DSP-GET-PM-cnf

Reference FFH

FFH

Padding (00H)

Padding (00H)


(in bytes) Semantic

Dsp Get Pm Confirmation 0 lastInitializationDate 4 Date of last initialization of performance measurement referring to

Time_20ms (i.e. DSP internal SW time reference in step of 20 ms) DSP processing load (load)

4 gDspAverageLoad 4 Current DSP average processing load Step of 0.1%

8 gDspAverageLoadUpper 4 upper tide mark of DSP average processing load Step of 0.1%

12 gDspAverageLoadLower 4 lower tide mark of DSP average processing load Step of 0.1%

16 gTDspPeakLoad 4 Current value of DSP processing peak load Step of 4 DSP CPU cycles (e.g.20 ns with 200 MHz HW)

20 gTDspPeakLoadUpper 4 upper tide mark of DSP processing peak load Step of 4 DSP CPU cycles (e.g. 20 ns with 200 MHz HW)

24 gTDspPeakLoadLower 4 lower tide mark of DSP processing peak load



2006-2-22 3BK 09556 JAAA PBZZA 56/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


Semantic

Step of 4 DSP CPU cycles (e.g.20 ns with 200 MHz HW) Telecom processing context

28 gTrxCreated 4 current value of number of TRXs created 32 gTrxCreatedUpper 4 upper tide mark of number of TRXs created 36 gTrxCreatedLower 4 lower tide mark of number of TRXs created 40 gTbfActivated 4 current value of number of TBF activated 44 gTbfActivatedUpper 4 upper tide mark of number of TBF activated 48 gTbfActivatedLower 4 lower tide mark of number of TBF activated 52 gMPdchActivated 4 current value of number of Master channel activated 56 gMPdchActivatedUpper 4 upper tide mark of number of Master channel activated 60 gMPdchActivatedLower 4 lower tide mark of number of Master channel activated 64 gPdchActivated 4 current value of number of PDCH activated 68 gPdchActivatedUpper 4 upper tide mark of number of PDCH activated 72 gPdchActivatedLower 4 lower tide mark of number of PDCH activated 76 gGchCreated 4 current value of number of GCHs created 80 gGchCreatedUpper 4 upper tide mark of number of GCHs created 84 gGchCreatedLower 4 lower tide mark of number of GCHs created 88 gEgprsTbfActivated 4 current value of number of EGPRS TBF activated 92 gEgprsTbfActivatedUpper 4 upper tide mark of number of EGPRS TBF activated 96 gEgprsTbfActivatedLower 4 lower tide mark of number of EGPRS TBF activated

DSP processing load (L1 overload) 100 cL1Overrun 4 number of uplink GCH frames lost to recover processing overload 104 cL1Underrun 4 Number of downlink GCH frames replaced by dummy frames to recover

processing overload PPC interface

108 cHpiTransfer 4 number of PPC transfers 112 cHpiUpMsgSent 4 number of messages sent 116 cHpiDownMsgReceived 4 number of messages received 120 cHpiUpFull 4 number of uplink message received in the DSP internal queue while the

PPC interface buffer is full 124 cHpiDownEmpty 4 number of times the last downlink message of the PPC downlink buffer

is processed. 128 cHpiHintAckDownFree 4 number of times HINT is sent to PPC on the condition of enough free

memory in the PPC interface downlink buffer 132 cHpiHintAckUpSize 4 number of times HINT is sent to PPC on the condition of PPC interface

uplink buffer size 136 cHpiHintAckUpTime 4 number of time HINT is sent to PPC on the condition of time elapsed for

uplink message transfer. 140 cHpiTout0ReqUpSize 4 number of time TOUT0 is set on the condition of PPC interface uplink

buffer size

144 cHpiTout0ReqUpTime 4 number of time TOUT0 is set on the condition of time elapsed for uplink message transfer

RLC memory occupancy 148 gFreeRlcResource 4 Current value of number of free RLC resources 152 gFreeRlcResourceUpper 4 upper tide mark of number of free RLC resources 156 gFreeRlcResourceLower 4 lower tide mark of number of free RLC resources 160 numberRlcResources 4 Number of RLC resources within the DSP memory 164 cGMaxCongestion 4 Counter of number of times G_MAX congestion has been entered 168 cGXoffCongestion 4 Counter of number of times G_XOFF congestion has been entered 172 cNTbfOffCongestion 4 Counter of number of times N_TBF_OFF congestion has been entered 176 gFreePagingResource 4 Current value of number of free Paging Resources 180 gFreePagingResourceUpper 4 Upper tide mark of number of free Paging Resources 184 gFreePagingResourceLower 4 Lower tide mark of number of free Paging Resources

RLC processing load 188 gTbfXonState 4 current value of number of downlink TBF in XON TBF flow control state. 192 gTbfXonStateUpper 4 upper tide mark of number of downlink TBF in XON TBF flow control

state. 196 gTbfXonStateLower 4 lower tide mark of number of downlink TBF in XON TBF flow control

state. 200 gTbfDlRlcWaitingAck 4 current number of downlink RLC PDU already transmitted and waiting

for an acknowledgement from the MS 204 gTbfDlRlcWaitingAckUpper 4 upper tide mark of number of downlink RLC PDU already transmitted

and waiting for an acknowledgement from the MS 208 gTbfDlRlcWaitingAckLower 4 lower tide mark of number of downlink RLC PDU already transmitted



2006-2-22 3BK 09556 JAAA PBZZA 57/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


Semantic

and waiting for an acknowledgement from the MS 212 gTbfUlRlcAckMode 4 current number of uplink RLC data PDUs already received and waiting

for reassembly in acknowledged mode 216 gTbfUlRlcAckModeUpper 4 upper tide mark of number of uplink RLC data PDUs already received

and waiting for reassembly in acknowledged mode 220 gTbfUlRlcAckModeLower 4 lower tide mark of number of uplink RLC data PDUs already received

and waiting for reassembly in acknowledged mode 224 gTbfUlRlcUnackMode 4 current number of uplink RLC data PDUs already received and waiting

for reassembly in unacknowledged mode 228 gTbfUlRlcUnackModeUpper 4 upper tide mark of number of uplink RLC data PDUs already received

and waiting for reassembly in unacknowledged mode 232 gTbfUlRlcUnackModeLower 4 lower tide mark of number of uplink RLC data PDUs already received

and waiting for reassembly in unacknowledged mode 236 cTbfDlLLC 4 number of received DL LLC PDU 240 cTbfDlLLCoverhead 4 number of received DL LLC PDU while the TBF is in XOFF TBF flow

control state 244 cTbfDlLLCunderflow 4 number of times a lack of RLC data has been encountered for downlink

TBFs internal DSP supervision

248 gcStackUpper 4 number of words used in the C stack 252 cStackSize 4 number of words reserved for C stack

RLC memory occupancy bis 256 numberPagingResources 4 Number of Paging resources within the DSP memory 260 cTimerActivated 4 Number of the timer activated in the DSP 264 gTimerActivatedUp 4 Upper tide mark of the number of the Timer activated in the DSP 268 cWrongGchPduReceiveGch 4 Number of wrong GCH PDUs received on the activated GCHs i.e. CRC

error and Zseq error. 272 Spare 4 Reserved



2006-2-22 3BK 09556 JAAA PBZZA 58/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.22 DSP-TRX-PM-GAUGE-req

This message is used to request PM gauges related to a range of TRXs Message type: DSP-TRX-PM-GAUGE-req Direction: PPC to DSP

Header

Length

00H

14H

Class DSP

Mtype DSP-TRX-PM-GAUGE-req

Reference FFh 00H

FFh

Padding

Padding


(in bytes)

Semantic Range

Performance Request 0 Reinit 1 This flag is used to request to DSP to

initialise the computation of all the gauges for the following Gauge Polling period after responding

0: Reinit requested FFH : Reinit not requested

1 Spare 3 Padding Performance Configuration

4 PeriodNumber 2 Number of the granularity period 0...65535 6 FirstTrxIndex 2 First index of the range

0...maxTrxDsp-1 8 lastTrxIndex 2 Last index of the range

0...maxTrxDsp-1 10 spare 2

At most 60 TRX can be requested in this message.

It means that LastTrxIndex � FirstTrxIndex + 1 <=60.

For MX DSP, PMU can require all informations by 4 requests.



2006-2-22 3BK 09556 JAAA PBZZA 59/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.23 DSP-TRX-PM-GAUGE-cnf

As a response of DSP-TRX-PM-GAUGE-req, this message is used by PTU to convey PM gauges for the TRXs of the requested range.

Important: Only PM gauges related to the active TRX indexes (created cells within PTU) within the requested range are sent. Message type: DSP-TRX-PM-GAUGE-cnf Direction: DSP to PPC

Header

Length

Variable ≤ 1620

Class DSP

Mtype DSP-TRX-PM-GAUGE-cnf

Reference FFh 00H

FFh

Padding

Padding

The PM content of this message is in restriction for this proposal



Long Confirmation 0 ackNack 1 Result of the Request 00H = Ack (Success)

01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure See 4.4 Note[1] 2 debugInfo 6 Debug information See 4.7



Performance Confirmation 8 nbTrx 2 Number of TRX 1...maxTrxDsp

10 periodNumber 2 Number of the granularity period given in request 0...65535 TRX PM gauges for all the TRXs in the range

12 PM gauges for the first TRX in the range

2*4+4 Described below

24 PM gauges for the second TRX in the range


-- 720**

PM gauges for the last TRX in the range


(**) If we consider that the maximum length of this message is approximately the LLC PDU maximum size, PM gauges for up to the max number of TRXs could be conveyed in the same message.



2006-2-22 3BK 09556 JAAA PBZZA 60/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Note[1]: If the �FirstTrxIndex� and �LastTrxIndex� in DSP-TRX-PM-GAUGE-req primitive are not reasonable, i.e. do not keep the rule, LastTrxIndex � FirstTrxIndex + 1 <=60, in this case, the NACK DSP-TRX-PM-GAUGE-cnf with �Parameter error� will be reported to PMU, and the PM gauge value of trxid 0 will be carried.

For each TRX, PM gauge structure is as follows: Byte Parameters Length


0 trxIndex 2 0�maxNbTrx-1 2 spare 2

PM gauges

Short Name Length (in Bytes)

Presence Definition

CellRLCLayerAveragedGaugesCfg P335 4 M Average TX_EFFICIENCY computed on DL TBFs established in GPRS mode.

P336 4 M Average TX_EFFICIENCY computed on UL TBFs established in GPRS mode.



2006-2-22 3BK 09556 JAAA PBZZA 61/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.24 DSP-TRX-PM-COUNTER-req

This message is used to request PM counters for a range of cells.. Message type: DSP-TRX-PM-COUNTER-req Direction: PPC to DSP

Header

Length

00H

14H

Class DSP

Mtype DSP-TRX-PM-COUNTER-req

Reference FFh 00H

FFh

Padding

Padding


(in bytes)

Semantic Range

Performance Request 0 reinit 1 This flag is used to request to DSP to reset all the

counters for the following Granularity Period after responding

0: reset requested FFh :reset not requested

1 spare 3 Performance Configuration

4 periodNumber 2 Number of the granularity period 0 ... 65535 6 firstTrxIndex 2 First index of the range

0 ... maxTrxDsp -1 8 lastTrxIndex 2 Last index of the range

0 ... maxTrxDsp -1 10 spare 2

At most 6 TRX can be requested in this message.



2006-2-22 3BK 09556 JAAA PBZZA 62/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.25 DSP-TRX-PM-COUNTER-cnf

As a response of DSP-TRX-PM-COUNTER-req, this message is used to convey PM counters of the TRXs within requested range. Important : Only PM counters related to the active TRX indexes (created cells within PTU) of the requested range are sent. Message type: DSP-TRX-PM-COUNTER-cnf Direction: DSP to PPC

Header

Length

Variable ≤ 1412

Class DSP

Mtype DSP-TRX-PM-COUNTER-cnf

Reference FFh 00H

FFh

Padding

Padding




Long Confirmation 0 ackNack 1 Result of the Request 00H = Ack (Success) ,

01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure

See 4.4 Note [1] 2 debugInfo 6 Debug information

See 4.7



Performance Confirmation 8 nbTrx 2 Number of TRXs 1�6

10 periodNumber 2 Number of the granularity period given in request 0�65535 TRX PM counters for all the TRXs in the range

12 PM counters for the first TRX in the range


244 PM counters for the second TRX in the range


-- 1172 PM counters for the last TRX in

the range 57*4+4 Described below

PM counters for up to 6 TRXs could be conveyed in the same message.



2006-2-22 3BK 09556 JAAA PBZZA 63/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Note[1]: If the �FirstTrxIndex� and �LastTrxIndex� in DSP-TRX-PM-COUNTER-req primitive are not reasonable, i.e. do not keep the rule, LastTrxIndex � FirstTrxIndex + 1 <=6, in this case, the NACK DSP-TRX-PM-COUNTER-cnf with �Parameter error� will be reported to PMU, and the PM counters value of trxid 0 will be carried.

For each TRX the PM counters structure is as follows: Byte Parameters Length


0 trxIndex 2 0�maxTrxDsp -1 2 spare 2

PM counters

Short Name Length

(in Bytes) Presence Definition

CellGCHLayerCountersCfg P103 4 M Number of GCH frames badly received by the MFS (due to a bad CRC).

CellMACLayerCountersCfg P350a 4 M Number of DL RLC/MAC data blocks sent on PDTCH. The retransmitted radio blocks

are counted.

P350b 4 M Number of UL RLC/MAC data blocks received on PDTCH. The retransmitted radio blocks are counted.

P59 4 M Number of DL RLC blocks sent on PACCH (excluding the dummy blocks). The retransmitted blocks are counted.

P60 4 M Number of UL RLC blocks received on PACCH (excluding the dummy blocks). The retransmitted blocks are counted.

CellRLCLayerCountersCfg P20a 4 M In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC

Dummy UI Commands only) on PDTCH encoded in CS-1 retransmitted due to unacknowledgement of the MS.

P20b 4 M In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-2 retransmitted due to unacknowledgement of the MS.

P20c 4 M In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-3 retransmitted due to unacknowledgement of the MS.

P20d 4 M In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-4 retransmitted due to unacknowledgement of the MS.

P20e 4 M In acknowledged mode, number of DL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x = 1 to 9) retransmitted due to unacknowledgement of the MS.

P21a 4 M In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-1 retransmitted due to unacknowledgement of the MFS.

P21b 4 M In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-2 retransmitted due to unacknowledgement of the MFS.

P21c 4 M In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-3 retransmitted due to unacknowledgement of the MFS.

P21d 4 M In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-4 retransmitted due to unacknowledgement of the MFS.

P21e 4 M In acknowledged mode, number of UL RLC data bytes received on PDTCH encoded in MCS-x (with x = 1 to 9) retransmitted due to unacknowledgement of the MFS.



2006-2-22 3BK 09556 JAAA PBZZA 64/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

P310a 4 M Number of stall indications from the MS for an GPRS uplink TBF.

P310b 4 M Number of stall indications from MS for an EGPRS uplink TBF.

P310c 4 M Number of times the MFS RLC transmit window enters the stall state for a GPRS DL TBF.

P310d 4 M Number of times the MFS RLC transmit window enters the stall state for an EGPRS DL TBF.

P351a 4 M Number of coding scheme adaptations from a given coding scheme to a less robust coding scheme in the downlink direction for GPRS TBFs.

P351b 4 M Number of coding scheme adaptations from a given coding scheme to a more robust coding scheme in the downlink direction for GPRS TBFs.

P352a 4 M Number of coding scheme adaptations from a given coding scheme to a less robust coding scheme in the uplink direction for GPRS TBFs.

P352b 4 M Number of coding scheme adaptations from a given coding scheme to a more robust coding scheme in the uplink direction for GPRS TBFs.

P421 4 M Number of RLC data blocks containing only Dummy LLC UI Command PDUs that have been sent on the radio interface. Note: This counter applies to both GPRS and EGPRS TBFs.

P55a 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-1. The retransmitted blocks and RLC blocks containing LLC Dummy UI Commands only are not counted.

P55b 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-2. The retransmitted blocks and RLC blocks containing LLC Dummy UI Commands only are not counted.

P55c 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-3. The retransmitted blocks and RLC blocks containing LLC Dummy UI Commands only are not counted.

P55d 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-4. The retransmitted blocks and RLC blocks containing LLC Dummy UI Commands only are not counted.

P55e 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-1.

P55f 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-2.

P55g 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-3.

P55h 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-4

P55i 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-5.

P55j 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-6

P55k 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-7.

P55l 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-8.

P55m 4 M Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-9.

P57a 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-1. The retransmitted blocks are not counted.

P57b 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-2. The retransmitted blocks are not counted.

P57c 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-3. The retransmitted blocks are not counted.



2006-2-22 3BK 09556 JAAA PBZZA 65/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

P57d 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-4. The retransmitted blocks are not counted.

P57e 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-1.

P57f 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-2.

P57g 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-3.

P57h 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-4.

P57i 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-5

P57j 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-6.

P57k 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-7.

P57l 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-8.

P57m 4 M Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-9.

P72c 4 M In unacknowledged mode, number of DL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-x (with x = 1 to 4) that are lost.

P72d 4 M In unacknowledged mode, number of DL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x = 1 to 9) that are lost.

P73c 4 M In unacknowledged mode, number of UL RLC data bytes on PDTCH encoded in CS-x (with x = 1 to 4) lost.

P73d 4 M In unacknowledged mode, number of UL RLC data bytes on PDTCH encoded in MCS-x (with x = 1 to 9) lost.

P457 4 M Signalling load induced in the cell by the procedure of broadcast of (P)SI messages

P459 4 M Signalling load induced in the cell by the procedure of broadcast of neighbour (P)SI messages

P462 4 M Number of Packet Uplink Dummy Control blocks received on the radio interface. This counter applies to both GPRS and EGPRS TBFs.



2006-2-22 3BK 09556 JAAA PBZZA 66/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.26 DSP-TRX-SAMPLE-req

Request sent by PMU to PTU in order to retrieve the counters of PRACH collision. Message type: DSP-TRX-SAMPLE-req Direction: PPC to DSP

Header

Length

00h

10h

Class DSP

Mtype DSP-TRX-SAMPLE-req

Reference FFh 00H

FFh

Padding

Padding


(in bytes)

Semantic Range

Performance Request 0 reinit 1 This flag is used to request to DSP to

initialise PRACH counter for the following Polling period after responding

0: Reinit requested FFH : Reinit not requested

1 spare 3 TRX Sample Configuration

4 periodNumber 2 Number of the granularity period 0...65535 6 trxSetId 1 Indication to a set of TRX 0..3

See note 7 spare 1

DSP-TRX-SAMPLE-req can require the information of a set of TRX�s. A set means 60 TRX.

trxSetId:

0: TRX0 - TRX59 are requied.

1: TRX60 � TRX119 are required. Only used for Mx.





2006-2-22 3BK 09556 JAAA PBZZA 67/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.27 DSP-TRX-SAMPLE-cnf

As a response of DSP-TRX-SAMPLE-req, this message is used to convey PRACH collision counters of all the TRXs. Message type: DSP-TRX-SAMPLE-cnf Direction: DSP to PPC

Header

Length

03h

20h

Class DSP

Mtype DSP-TRX-SAMPLE-cnf

Reference FFh 00H

FFh

Padding

Padding


(in bytes)

Semantic Range

TRX Sample Confirmation 0 periodNumber 2 Number of the granularity period given in request 0�65535 2 trxSetId 1 Indication to a set of TRX. It corresponds to the

value in DSP-TRX-SAMPLE-req 0..3 See note[1].

3 spare 1 Long Confirmation

4 ackNack 1 Result of the Request 00H = Ack (Success) , 01H = Nack (Failure)

5 cause 1 Cause of the refusal/failure See 4.4 Note[3] 6 debugInfo 6 Byte index of the field in DSP-TRX-SAMPLE-req

not compliant with checking rules See 4.7

MPDCH Bitmap 12 masterBitmap[0] 1 Bitmap indicating the master time slots of the TRX

with index 0 (for debug purpose only) Bitmap[0..7] 0:not master, 1 master

13 masterBitmap[1] 1 Bitmap indicating the master time slots of the TRX with index 1 (for debug purpose only)

Bitmap[0..7] 0:not master, 1 master

� 71 masterBitmap[59] 1 Bitmap indicating the master time slots of the TRX

with index 59 (for debug purpose only) Bitmap[0..7] 0:not master, 1 master

PRACH Counters 72 nbPrachOccurence[0] 4 Number of PRACH occurence for the TRX with

index N See note[2]

76 nbPrachSuccess[0] 4 Number of PRACH success for the TRX with index N

80 nbPrachCollision [0] 4 Number of PRACH collision for the TRX with index N

84 nbPrachOccurence[1] 4 Number of PRACH occurence for the TRX with index N+1

88 nbPrachSuccess [1] 4 Number of PRACH success for the TRX with index N+1



2006-2-22 3BK 09556 JAAA PBZZA 68/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

92 nbPrachCollision [1] 4 Number of PRACH collision for the TRX with index N+1

� 780 nbPrachOccurence[59] 4 Number of PRACH occurence for the TRX with

index N+59

784 nbPrachSuccess[59] 4 Number of PRACH success for the TRX with index N+59

788 NbPrachCollision[59] 4 Number of PRACH collision for the TRX with index N+59

Note[1]:

DSP-TRX-SAMPLE-req can require the information of a set of TRX�s. A set means 60 TRX. So trxSetId:

0: TRX0 - TRX59 are reported.

1: TRX60 � TRX119 are reported. Only used for Mx.



Note[2]:

N is initial TRX index of a set corresponding to the trxSetId. For example, if trxSetId is 1, then N is 60.

Note[3]

If the parameter trxSetId is out of reasonable range, the default value 0 will be used.



2006-2-22 3BK 09556 JAAA PBZZA 69/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.2.28 DSP-LOAD-ind

This message is used to indicate the DSP load. Message type: DSP-LOAD-ind Direction: DSP to PPC

Header

Length

variable

Class DSP

Mtype DSP-LOAD-ind

Reference FFh

FFh

Padding

Padding



Dsp LOAD State 0 ind_id 2 Message number to indicate the numbered DSP-LOAD-

ind 0..255

2 spare 2 4 loadPercentage 2 Percentage of DSP load 0..100 6 nbGCH 2 Number of GCH established 8 nbPDCH 2 Number of PDCH activated

10 nbTBF 2 Number of TBF activated 12 padding 4

16 nbDspLoadInfor 4 The number of following DspLoadInfor for debug 0..100

If the value is 0, it means that there is no DspLoadInfor for debug.

20 DspLoadInfor[0] 4 Dsp LOAD State every 20 ms 24 DspLoadInfor[1] 4 28 � N DspLoadInfor[nbDspLoadInf

or-1] 4



2006-2-22 3BK 09556 JAAA PBZZA 70/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3 Class TRX

3.3.1 TRX-CREATE-req

This message is used to create a TRX context with specific parameters. Message type: TRX-CREATE-req Direction: PPC to DSP

Header

Length

00H

64h

Class TRX

Mtype TRX-CREATE-req

Reference TRX_INDEX (MSB) 00H

TRX_INDEX (LSB)

Padding

Padding

TrxInfoCfg

0 ncRxqualHysteresis

2 Hysteresis to avoid frequent NC cell reselection alarms on the PMU-PTU interface

2 trxCapability 2 Maximum data capability of the TRX

4 spare0 2

CellNC2PimPtmCfg

6 ncDlRxqualThr 2 Threshold above which a NC cell reselection Cause PT3 is triggered due to a too bad RXQUAL in downlink direction

8 ncUlRxqualThr 2 Threshold above which a NC cell reselection Cause PT4 is triggered due to a too bad RXQUAL in uplink direction

10 ncRxqualAvgPeriod 2 Period after which a weight of 0.9 s is applied to the current UL or DL RXQUAL samples in the averaging filter.

12 tNcRxqualValid 2 Timer used to control the validity of the NC RXQUAL averages at the beginning of a TBF.



2006-2-22 3BK 09556 JAAA PBZZA 71/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

CellLinkSupervisionCfg

14 spare545 2

16 spare547 2

18 txEfficiencyAckThr 2 Threshold below which the TBF is released because of a bad transmission efficiency in acknowledged mode

20 txEfficiencyNackThr 2 Threshold below which the TBF is released because of a bad transmission efficiency in unacknowledged mode

CellLinkAdaptationCfg

22 tDlEgprsMeasreport 2 Time period to request for an EGPRS Packet Downlink Ack/Nack with measurements.

24 tDlGprsMeasreport 2 Time period to request for a Packet Downlink Ack/Nack with measurements.

26 csMaxIdlePeriod 2 Maximum downlink (or respectively uplink) transfer interruption between two successive DL (or respectively UL) PDU to be able to reuse the coding scheme or modulation and coding scheme of the previous transmitted (or respectively received) radio blocks. This applies in case of data transfer resumption for a DL TBF in delayed release state, or an UL TBF in extended state. When a new LLC PDU is received and the downlink/uplink transfer is resumed, the timer defined by CS_MAX_IDLE_PERIOD shall be checked. If it has not expired, then the previous coding scheme or modulation and coding scheme of the DL/UL TBF shall be reused.

28 spare3254 2

MacTrxInfoCfg

30 rrmReferenceHigh 2

32 rrmReferenceLow 2

34 wiPr 2 Wait indication used in PACKET ACCESS REJECT.

36 tAckWait 2 Timer defining the maximum time to wait for a MS answer (i.e. Packet Control Ack) to a network solicitation sent on PACCH/DL when the MS is in PTM, or on PPCH when the MS is in PIM and non-DRX mode.

38 tulAssignPccch 2 The duration between the reception of the (EGPRS) Packet Channel Request message and one uplink radio block allocated to the MS.

40 nSigRepeat 2 Number of repetitions of Packet Measurement Order messages with a Reset command, of Packet Uplink Assignment messages, or of Packet Power Control Timing Advance messages. These repetitions are handled by the MAC layer.



2006-2-22 3BK 09556 JAAA PBZZA 72/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

CellMacCfg

42 bsPrrBlksMpdch 2 Maximum number of radio blocks which may be allocated to a Packet Resource Request in case of two phase access, to a Packet Measurement report, or to a Packet Cell Change Failure, per 52 multiframe on each uplink Master PDCH.

44 bsPrrBlksSpdch 2 Maximum number of radio blocks which may be allocated to the Packet Resource Request in case of two phase access, per 52 multiframe on each uplink slave PDCH

46 dlPollFactor 2 This parameter defines the slope in credit computation for the downlink cyclic polling algorithm.

48 ulPollFactor 2 This parameter defines the slope in credit computation for the uplink cyclic polling algorithm.

50 roundTripDelay 2 Round trip delay between the MFS and a MS.

52 tpagCs 2 This timer indicates the maximum time a CS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on A and A-bis or Gs/Gb and A-bis interface.

54 tpagPs 2 This timer indicates the maximum time a PS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on Gb and A-bis interface.

56 maxDlTbfSpdch 2 Maximum number of DownLink (E)GPRS connections per slave PDCH

58 maxUlTbfSpdch 2 Maximum number of UpLink (E)GPRS connections per slave PDCH

60 prachBusyThres 2 Received level above which a PRACH block is deemed busy.

62 rachTaFilter 2 Timing Advance threshold for CHANNEL REQUIRED and PACKET CHANNEL REQUEST filtering.

64 spare4638 2

66 spare4509 2

CellPowerControlCfg

68 bsTxPwrMax 2 This parameter defines the power reduction relative to the maximum GMSK output power of the BTS.

70 gammaTnx 2 Binary representation of the �gamma ch� for MS output power control.

72 spare470

74 spare441



2006-2-22 3BK 09556 JAAA PBZZA 73/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

CellL2GchCfg

76 tcorr 2 Timer to supervise clock drift correction loop for 16k channel.

78 tdsl 2 Supervision of loss of downlink synchronisation for 16k channels.

80 tusl 2 Supervision of loss of uplink synchronisation for 16k channels.

82 testab 2 Supervision of loss of GCH link establishment for 16k channels.

84 tfreeze 2 Freeze of PDCH resource after an abnormal release for 16k channels.

86 trelease 2 Supervision of GCH link release for 16k channel.

88 trtsPs 2 This timer is used in the BTS to supervise the state of a RTS used as a PDCH. This timer is started when the BTS does not receive in a 20 ms period a valid DL frame on the RTS and is stopped when it receives one DL valid frame.

90 spare4506 2

Notes:

ncRxqualHysteresis in TrxInfoCfg is used by RLC.

trxCapability in TrxInfoCfg is used by GCH with the following mapping:

0 (00): "CS1 only" should be considered as an error 1 (01): "CS1 and CS2" means DRFU TRE so TRAU activate format. 2 (10): "CS1 to CS4" means GCH activate format. 3 (11): "CS1 to CS4 and MCS1 to MCS9" means GCH activate format.



2006-2-22 3BK 09556 JAAA PBZZA 74/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.2 TRX-CREATE-cnf

This message is used to confirm the TRX creation. Message type: TRX-CREATE-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class TRX

Mtype TRX-CREATE-cnf


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range


01H = Nack (Failure) 1 cause 1 Cause of the refusal/failure See 4.4 2 debugInfo 6 Debug information See 4.7



2006-2-22 3BK 09556 JAAA PBZZA 75/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.3 TRX-DELETE-req

This message is used to delete a TRX context. Message type: TRX-DELETE-req Direction: PPC to DSP

Header

Length

00H

08H

Class TRX

Mtype TRX-DELETE-req


TRX_INDEX (LSB)

Padding

Padding

All TBF contexts shall be deleted before this command is applied. It doesn�t delete/stop the in-progress TBFs.



2006-2-22 3BK 09556 JAAA PBZZA 76/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.4 TRX-DELETE-cnf

This message is used to confirm the TRX deletion. Message type: TRX-DELETE-cnf Direction: DSP to PPC

Header

Length

00H

D4H

Class TRX

Mtype TRX-DELETE-cnf


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range




(in bytes)

Semantic Range

Same structure of PM counter as in 3.2.25 DSP-TRX-PM-COUNTER-cnf for the TRX, but without the TRX_INDEX and padding bytes at the

beginning




2006-2-22 3BK 09556 JAAA PBZZA 77/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.5 TRX-PPCH-req

This message is used to send the Packet DL Assignment PDU to the MS in DRX-mode or non DRX mode (PCCCH). Message type: TRX-PPCH-req Direction: PPC to DSP

Header

Length

00H

38H

Class TRX

Mtype TRX-PPCH-req


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PPCH Request 0 tsList 1 List of time slot on which the

PDU will be sent Bitmap[0..7]: 0:absent; 1:present

2 spare 3 4 reference 4 Request Reference

TRX PPCH Configuration 8 poll 1 Request a MS response See 4.16 9 splitPgCycle 1 DRX parameter used to

compute the paging group 0...98, 0: non DRX

10 ControlPduLifeTime 2 If the PDU_TYPE is a Packet DL assignment, the PDU_LIFE_TIME is the maximum time the Packet DL Assignment PDU should be kept in the PTU. This timer is also used for the Packet Cell Change Order PDU max queuing time

0 means infinite timer

1: 100 ms

2: 200 ms�

12 imsi 9 International Mobile Station Identity

See 4.11

21 padding 1 PDU Block Structure

22 padding 1 23 pduBlockType 1 Packet Data Unit Type See 4.3 24 pduBlock 24 RLC control PDU without

MAC header See [ 6 ]



2006-2-22 3BK 09556 JAAA PBZZA 78/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PDU_TYPE

Packet DL Assignment

The IMSI in the message is used to compute the paging group of the mobile in DRX mode i.e. to insert the packet DL assignment or the packet Cell Order in the correct block number listen by the mobile. Therefore when RRM doesn't know the IMSI of the mobile, the only way to join the mobile is to send the packet DL Assignment or the packet Cell Change Order as soon as it's possible i.e. in non DRX mode on all master channel (so the TS_List parameter may not be reduced to one single TS).

During Non DRX period, the mobile listen all the block on its master channel, so RRM asks MAC layer to send as soon as it's possible the packet DL Assignment or the packet Cell Change Order to speed the TBF establisment or the cell reselection i.e. SPLIT_PG_CYCLE is set to 0.

So if the SPLIT_PG_CYCLE is set to 0, the IMSI is not relevant; or if RRM does not provide the IMSI than the SPLIT_PG_CYCLE must be set to 0.

3.3.6 TRX-NO-PPCH-ind

This message is used to indicate the Packet DL Assignment PDU was not sent. Message type: TRX-NO-PPCH-ind Direction: DSP to PPC

Header

Length

00H

18H

Class TRX

Mtype TRX-NO-PPCH-ind


TRX_INDEX (LSB)

Padding

Padding Byte Parameters Length

(in bytes)

Semantic Range

PPCH Confirmation 0 tsList 1 List of time slot asked in

PPCH-request on which the PDU is not sent

Bitmap[0..7]: 0:sent or not asked; 1:not sent

1 pduType 1 Indicates Packet DL assignment or Packet Cell Change order

See 4.2

2 spare 2



2006-2-22 3BK 09556 JAAA PBZZA 79/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4 reference 4 Request Reference Nack Confirmation

8 padding 1 9 cause 1 Cause of the refusal/failure See 4.4

10 debugInfo 6 Debug information See 4.6

3.3.7 TRX-MODIFY-req

This message is used to modify the TRX context. Message type: TRX-MODIFY-req Direction: PPC to DSP

Header

Length

As for TRX-CREATE-req

Class TRX

Mtype TRX-MODIFY-req


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

As for TRX-CREATE-req

The parameters structures are the same as in Trx-create-req but not all parameters are significant, i.e. some values are present in the message but not interpreted by PTU SW, as they are not on-line changeable.

So all parameters are significant (changeable), except: trxCapability, tNcRxqualValid, tAckWait, nSigRepeat bsPrrBlksMpdch, bsPrrBlksSpdch, dlPollFactor, ulPollFactor, tdsl, tusl, tfreeze, trelease.



2006-2-22 3BK 09556 JAAA PBZZA 80/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.8 TRX-MODIFY-cnf

This message is used to confirm the TRX modification. Message type: TRX-MODIFY-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class TRX

Mtype TRX-MODIFY-cnf


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range





2006-2-22 3BK 09556 JAAA PBZZA 81/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.9 TRX-SYS-DEFINE-req

This message is used to provide/delete PSI PDUs to be broadcast in the PBCCH, to give the control channels description (PBCCH/PCCCH) and to promote a PDCH as primary master PDCH. Message type: TRX-SYS-DEFINE-req Direction: PPC to DSP

Header

Length

variable

Class TRX

Mtype TRX-SYS-DEFINE-req


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Control Channel Description 0 primaryMasterPosition 1 Eventual position of the PBCCH in the

TRX 0...7, NIL(FFH)

1 masterPdchBitmap 1 Bitmap of Master PDCH in the TRX (primary and secondary)

Bitmap[0..7] 0:absent,1:present

2 pageMode 1 Type of Page mode 0:normal paging 2:paging reorganization

3 bsPccChans 1 Number of radio timeslots reserved for the primary and secondary master PDCHs defined in the cell.

see § 3.1.3.2

4 bsPbcchBlks 1 Number of blocks allocated to the PBCCH per 52 multiframe.

see § 3.1.3.2

5 bsPagBlksRes 1 Number of blocks allocated to the PAGCH or PDTCH or PACCH per 52 multiframe.

see § 3.1.3.2

6 bsPrachBlks 1 Number of blocks statically allocated to the PRACH per 52 multiframe on each MPDCH.

see § 3.1.3.2

7 padding 1



2006-2-22 3BK 09556 JAAA PBZZA 82/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Network Control Information 8 ncReportingPeriodT 1 Reporting period of NC measurements

reported by the MS while in packet transfer mode.

see § 3.1.3.2

9 accessBurstType 1 Format of the access burst used by (E)GPRS MSs when sending a PACKET CHANNEL REQUEST, a PACKET CONTROL ACKNOWLEDGEMENT or a PTCCH/U message.

see § 3.1.3.2

10 hoppingMode 1 hopping mode of the TRE

0: non-hopping

1: hopping 11 TSC 1

Training Sequence Code for any (packet) channel except for BCCH, CCCH and CBCH.

see § 3.1.3.2

12 padding 8

Psi Scheduling Information 20 psi1RepeatPeriod 1 Repeat Period of Psi1 on PBCCH

blocks 1:1 2:2 16:16

21 psiCountHR 1 Number of High repetition rate PSI messages on PBCCH

1:1 2:2 � 8:8

22 psiCountLR 1 Number of Low repetition rate PSI messages on PBCCH

2:2 � 34:34

23 padding 1

(P)SI Pdu Information 24 pduInformation 1092

or 412

Refer to following description.

If a PBCCH is present in the Cell (even PBCCH is not in the TRX), pduInformation is as follows: PSI Pdu Information

24 psi1ChangeMark 1 PSI 1 Update Flag 0, 1, 2: see note 25 psi2ChangeMark 1 PSI 2 Update Flag 0, 1, 2: see note 26 psi3ChangeMark 1 PSI 3, 3bis & 3quater Update Flag 0, 1, 2: see note 27 SparePsiChangeMark 1 28 psi8ChangeMark 1 PSI 8 Update Flag 0, 1, 2: see note 29 psi14ChangeMark 1 PSI 14 Update Flag 0: see note 30 psi2Number 1 Number of PSI 2 instances 1...8 31 psi3bisNumber 1 Number of PSI 3 bis instances 1...16 32 psi3quaterNumber 1 Number of PSI 3 quater instances 0...16 33 Padding 3 36 psi1Pdu 24 Packet System Information data see §4.17 60 psi2Pdu[0..7] 8x24 Packet System Information data see § 4.17

252 psi3Pdu 24 Packet System Information data see § 4.17 276 psi3bisPdu[0..15] 16x24 Packet System Information data see § 4.17 660 psi3quaterPdu[0..15] 16x24 Packet System Information data see § 4.17

1044 SparePsiPdu 24 see § 4.17 1068 psi8Pdu 24 Packet System Information data see § 4.17 1092 psi14Pdu 24 Packet System Information data see § 4.17



2006-2-22 3BK 09556 JAAA PBZZA 83/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

If no PBCCH is present in the cell, pduInformation is as follows:

SI Pdu Information 24 psi13ChangeMark 1 PSI 13 Update Flag 0, 3: see note 25 Psi14changeMark 1 PSI 14 Update Flag 0: see note 26 si2terNumber 1 Number of SI2ter instances 0...8 27 Padding 1 28 psi13Pdu 24 System Information data see § 4.17 52 si1Pdu 24 System Information data see § 4.17 76 si2Pdu 24 System Information data see § 4.17

100 si2bisPdu 24 System Information data see § 4.17 124 si2terPdu[0..7] 8*24 System Information data see § 4.17 316 si2quaterPdu 24 System Information data see § 4.17 340 si3Pdu 24 System Information data see § 4.17 364 si4Pdu 24 System Information data see § 4.17 388 si13Pdu 24 System Information data see § 4.17 412 psi14Pdu 24 System Information data see § 4.17

Notes :

BsPccChans:

0: if PBCCH is not present in the cell.

1..4: if PBCCH is present in the cell.

PSIxChangeMark:

0: PSIx PDU not significant and not to be send on the air

1: PSIx PDU significant and has to be sent on PBCCH if required by 44.060 or if PBCCH is present and immediately on PACCH (if PACCH is present).

2: PSIx PDU significant and has to be sent on PBCCH if required by 44.060 or if PBCCH is present.

3: PSIx PDU significant and has to be sent on PACCH immediately if PACCH is present.

4: PSIx is significant. It is not needed to send on PACCH immediately and not needed to send on PBCCH.

Parameters used in the establishment of GCH: AccessBurstType and TSC can't be change. Therefore RRM should release all on going traffic and the TRX context in order to create a new TRX context with the changed value.

The HR PSIs are the PSI_COUNT_HR PSIs after PSI1, and the LR PSIs are the next PSI_COUNT_LR PSIs.

For the downlink PCCCH channel description, we should have the following mandatory rule: BsPbcchBlks + BsPagBlksRes < 11.

If not a confirmation with cause parameter error should be send back to RRM. •



2006-2-22 3BK 09556 JAAA PBZZA 84/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Coding rules of the message in the following cases:

Whatever the presence of a Master PDCH in the cell, a first TRX_SysDefine_Req should be sent in order to give the following parameters: pageMode, ncReportingPeriodT, accessBurstType, hoppingMode, TSC. Then the presence of the master PDCH is defined by BS_PCC_CHANS, so it also defines the type of (P)SI PDU information structure:

bsPccChans equal to 0 means pduInformation is a SI PDU Information bsPccChans different from 0 means pduInformation is a PSI PDU Information

In case there is no master PDCH in the cell, different kind of TRX-sys-define-req could be sent:

TRX-sys-define-req sent for the TRX creation: • PBCCH Position is set to NIL.

• Master PDCH Bitmap empty.

• BS_PCC_CHANS must be equal to 0.

• SIx are provided.

• PSI13 is relevant (ie: PSI13 change mark set to 1).

TRX-sys-define-req sent for (P)SI modification: • PBCCH Position is set to NIL.





TRX-sys-define-req sent for Master PDCH creation: • PBCCH Position and Master PDCH Bitmap are set if the TRX carries the Master PDCH.

• BS_PCC_CHANS must be different from 0.

• PSI1, PSI2, PSI3 are provided with their related Change mark flag set to 1.

• If CBCH is present in the cell, PSI8 is provided with its related Change mark flag set to 1.

In this last case the pageMode is set to Paging reorganization, so at the end of the reorganization a new TRX-sys-define-req is sent to switch back to normal paging with PSI change mark sent to 2.

In case there is a master PDCH in the cell, different kind of TRX-sys-define-req could be sent: • TRX-sys-define-req sent for the TRX creation at cell start for the TRX supporting the master:

• PBCCH Position is set to NIL.







2006-2-22 3BK 09556 JAAA PBZZA 85/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

TRX-sys-define-req sent after the TRX creation for the TRX supporting the master PDCH: • PBCCH Position and Master PDCH Bitmap are set.




In this last case the pageMode is set to Paging reorganization, so at the end of the reorganization a new TRX-sys-define-req is sent to switch back to normal paging with PSI change mark sent to 2.

TRX-sys-define-req sent for the TRX not supporting the master PDCH: • PBCCH Position is set to NIL.





TRX-sys-define-req sent for PSI modification: • PBCCH Position and Master PDCH Bitmap are set if the TRX carries the Master PDCH.

• BS_PCC_CHANS must be different than 0.

• PSI1, PSI2, PSI3are provided with their related Change mark flag set to 1 or 2.


TRX-sys-define-req sent for master PDCH deletion: • PBCCH Position is set to NIL.





•

• Since the master PDCH is no more PS capable, it could happen that the TRX supporting the master PDCH is not received from the BSC in the Cell State Response/indication on BSCGP interface. Therefore PMU doesn't know the TRX capability of the TRE supporting the master PDCH.

•

• Because this information is needed for PTU to select the GCH stack, PMU applies the following rule:

• When the TRX supporting the Master PDCH is described in the list. The TRX capability of the TRE supporting the master PDCH is the one of the TRE.



2006-2-22 3BK 09556 JAAA PBZZA 86/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

• When the TRX supporting the Master PDCH is not described in the list, and the first TRX is "CS1 and CS2" capable (G2 TRE), it means that all the TRE are G2 TRE (i.e. non-evolium cabinet). Therefore the TRE supporting the Master PDCH is "CS1 and CS2" capable.

• When the TRX supporting the Master PDCH is not described in the list, and the first TRX is not "CS1 and CS2" capable, all the TRE are not G2 TRE, but a mix of G3 and G4 (i.e. evolium cabinet). Therefore we make the choice to force the TRX capability of the TRE supporting the Master PDCH to "CS1 to CS4" (G3 TRE).

If the number of instances for some PSI is not up to the Max value, the PDU containing useful instance should be put at the beginning of PDU array for the PSI.

SI information�s are only valid when the SI status feature is enabled. If SI status feature is not enabled si2terNumber should be set to 0. If the SI status is enabled, PMU should provide instance�s mentioned in the message as much as possible. If PMU can�t provide some SI then the length of corresponding PDU should be set to 0. If the number of instance is less than the maximum, the PDU containing useful instance should be put at the beginning of PDU array for the PSI.



2006-2-22 3BK 09556 JAAA PBZZA 87/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.3.10 TRX-SYS-DEFINE-cnf

This message is used to confirm the providing/deletion of control channels description and PSI PDUs. Message type: TRX-SYS-DEFINE-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class TRX

Mtype TRX-SYS-DEFINE-cnf


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range





2006-2-22 3BK 09556 JAAA PBZZA 88/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4 Class TBF

3.4.1 TBF-ACTIVATE-req

This message is used to activate a TBF (enabling radio resource allocation) or modify normalEndHandling to indicate the TBF supports extended uplink mode. Message type: TBF-ACTIVATE-req Direction: PPC to DSP

Header

Length

00H

10H

Class TBF

Mtype TBF-ACTIVATE-req

Reference TBF_INDEX (MSB)

TBF_INDEX (LSB)

Padding

Padding



RLC Control parameters 2 0 initCs 1 Initial Coding Scheme (CS) See 4.6 1 maxCs 1 Maximum Coding Scheme and modulation See 4.6 2 supervisionHandling 1 Link Supervision handling

See note below 3 normalEndHandling 1 Normal End Release authorization

0: Not Allowed, 1:Allowed, 2: extended, 3: DPUAN

4 waitingTimer 2 Time to wait before activating the TBF 0�100 (step size 20ms) 6 padding 2

Note: The link and NC2 supervision shall be: 0 = Enable and Go on (Counter are incremented, timers are started and NC2 alarm allowed) 1 = Disabled (Counter are not incremented, timers and NC2 alarm are frozen) 2 = Enable and Reset (Same as 0 but counter, timers and NC2 alarm are reset before)

initCs is the copy of CHANNEL_CODING_COMMAND field in Assignment for a normal establisment or in case of reallocation.

maxCs is the maximum allowed modulation and coding scheme used during transfer computed by RRM according to MS Technology (GPRS or EDGE) and TRX Class



2006-2-22 3BK 09556 JAAA PBZZA 89/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

The initCs could be change when RRM triggers a reallocation because the O&M parameter could not be the same since the first activate sent at TBF establishment or in case of inter TRX reallocation when the BTS technology or the TRX Class force to change it. Sum-up of different cases for Initial coding scheme: Behaviour initCs maxCs Normal Establishment ONMinitCS or BTSinitCS ONMmaxCS or BTSmaxCS Reallocation (1st activate) ONMinitCS or BTSinitCS or CurrentCS see TBF-REALLOC-req Reallocation (2nd activate) CurrentCS see TBF-REALLOC-req Sum-up of different cases for TBF behaviour: Behaviour supervision normalEnd waitingTimer Normal Establishment Enable and Go on (1) (3) Reallocation (1st activate) Disabled (1) TimeToSwitch + RRBP_valueReallocation (2nd activate) Enable and Go on or

Enable and Reset (2) 0

Remark: No check is made in the DSP for combination between Supervision and NormalEnd to allow future evolution. (1) If radio capability is unknown or R99 mobile: NotAllowed for either a downlink TBF or a uplink TBF.

If radio capability is known and MS supports extended UL TBF: NotAllowed for a downlink TBF. Extended for the uplink TBF.

If the UL TBF is in delayed final PUAN phase, RRM notifies RLC sends PUAN (FAI=0 acknowledge all UL RLC data blocks except for the last one) by the primitive, normalEndHandling should be set to DPUAN.

If the UL enters into delayed final PUAN state when resource reallocation is on-going, the value of Eormal End can be set to DPUAN (if the timer T_Del_Final_PUAN does not expire in RRM) or ALLOWED (if the timer T_Del_Final_PUAN expires in RRM).

(2): Value of normalEnd in the 2nd activate case: For an UL TBF, NormalEnd keeps the same value as when the reallocation started. But if the UL TBF can be released when the resource reallocation procedure is completed, the 2nd TBF-ACTIVATE-REQ does not needed. For a DL TBF, NormalEnd is always set �NotAllowed� for a delayed DL TBF release (3): The value of the waiting timer shall be set to TimeToSwitch + RRBP for a concurrent downlink TBF establishment otherwise it shall be set to 0. (4): The value of NormalEnd can be changed as the following diagram (The following diagram is used for UL TBF only):

NotAllowed

Allowed Extended

DPUAN



2006-2-22 3BK 09556 JAAA PBZZA 90/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.2 TBF-ACTIVATE-cnf

This message is used to confirm the TBF activation. Message type: TBF-ACTIVATE-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class TBF

Mtype TBF-ACTIVATE-cnf


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range





2006-2-22 3BK 09556 JAAA PBZZA 91/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.3 TBF-DEACTIVATE-req

This message is used to deactivate a TBF (disabling radio resource allocation). Message type: TBF-DEACTIVATE-req Direction: PPC to DSP

Header

Length

00H

10H

Class TBF

Mtype TBF-DEACTIVATE-req


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Deactivate Request 0 padding 8 provisioning



2006-2-22 3BK 09556 JAAA PBZZA 92/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.4 TBF-DEACTIVATE-cnf

This message is used to confirm the TBF deactivation. Message type: TBF-DEACTIVATE-cnf Direction: DSP to PPC

Header

Length

00H

14H

Class TBF

Mtype TBF-DEACTIVATE-cnf


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Cs Info 0 currentCs 1 Current Coding Scheme See 4.6 1 padding 3


01H = Nack (Failure) 5 cause 1 Cause of the refusal/failure

See 4.4 6 debugInfo 6 Debug information

See 4.7



2006-2-22 3BK 09556 JAAA PBZZA 93/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.5 TBF-DL-FLOW-CTRL-ind

This message is used to indicate the data flow control is on/off. Message type: TBF-DL-FLOW-CTRL-ind Direction: DSP to PPC

Header

Length

00H

0CH

Class TBF

Mtype TBF-DL-FLOW-CTRL-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Flow Control Parameter 0 xonXoff 1 Flow control Indicator 00H = XON, 01h =

X0FF 1 padding 3



2006-2-22 3BK 09556 JAAA PBZZA 94/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.6 TBF-DL-UNITDATA-req

This message is used to provide LLC PDU and QoS parameters for a DL TBF. Message type: TBF-DL-UNITDATA-req Direction: PPC to DSP

Header

Length

Variable ≤ 1580 bytes

Class TBF

Mtype TBF-DL-UNITDATA-req


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

RLC QoS Parameters

0 rtflag 1 Indicate the TBF is a RT or NRT.

0: NRT. The cr value is not valid.

1:RT. The cr value is valid.

1 priority 1 0..15

2 cr 2 Credit generation rate : updated number of radio blocks to be scheduled in average per 20ms period

0..800 step size = 1. 1 means 0.01 radio block. � 800 means 8 radio block. See note.

4 nbBlockValidity 1 Indicate how many blocks should be scheduled by MAC with the priority

- 0 : the indicated priority indicated above is to be used for an unspecified number of blocks

>0 : the indicated priority indicated above is to be used only for NB_BLOCK_VALIDITY blocks scheduling (UL or DL)

5 spare 3

LLC DL PDU Block 8 length 2 LLC PDU length 5�1560

10 number 2 LLC-PDU number used for securization.

0�65535

12 pdu length LLC Packet Data Unit



2006-2-22 3BK 09556 JAAA PBZZA 95/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

length = 5 to 1560 bytes

Note:

NbBlockValidity is always set to 0.For NRT TBF, the cr should be 0.

For RT TBF, if cr is 0, it means that the TBF is scheduled like when all the cr for a RT TBF have been used thanks to the extra scheduling mechanism.



2006-2-22 3BK 09556 JAAA PBZZA 96/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.7 TBF-DL-LLC-ACK-ind

This message is used to acknowledge LLC PDU. Message type: TBF-DL-LLC-ACK-ind Direction: DSP to PPC

Header

Length

00H

10H

Class TBF

Mtype TBF-DL-LLC-ACK-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

LLC PDU Ack 0 number 2 see note 0...65535 2 currentCs 1 Current Coding Scheme See 4.6 3 padding 1

QoS Control 4 txEfficiency 2 Transmission efficiency for

EGPRS or GPRS RT and NRT TBF

0..300 The unit is 0.01 0 means that the Tx_Efficiency calculation does not start.

6 PFI 1 UL only : latest PFI received from the MS

0..127

7 spare 1

The current coding scheme is used for debug purpose. RRM doesn�t use this field.

Note: LLC PDU number of the last PDU acknowledged. (All the PDU, related to this TBF, sent by PMU before the PDU related to this LLC PDU number (and this PDU) are acknowledged) and (NIL i.e. -1) if no DL data sent or acknowledge depend on RLC mode.

PFI is not significant in this message.



2006-2-22 3BK 09556 JAAA PBZZA 97/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.8 TBF-ESTABLISH-req

This message is used to establish a TBF context. Message type: TBF-ESTABLISH-req Direction: PPC to DSP


bytes)

Semantic Range

RLC local reference 0 trxIndex 2 TRX Index 0...maxNbTrx-1

RLC initial control parameters 2 globalTFI 1 Global Temporary Block

Flow Identifier See page 154

3 tlliReq 1 TTLI Contention resolution request for an UL TBF

Note: in case of DL TBF TLLI-REQ is set to 0 (not requested)

0 = TLLI not requested 1 = TTLI requested

4 rlcMode 1 Mode of Transmission 00H = Ack mode, 01H = Nack mode

5 enCsAdaptation 1 Enables/disables the coding scheme adaptation mechanism

0 : disabled 1 : enabled

6 networkControlOrder 1 Network Control Order for cell reselection

0, 1, 2

7 tbfMode 1 Mode of the TBF 0 : GPRS 1 : EGPRS

8 ARQtype 1 UL only. 0: Type I 1: TypeII

9 spare 1 RLC radio configuration

10 pacchTS 1 Time slot of the PDCH that will support the PACCH

0...7

11 pdchCount 1 Number of PDCHs see § 3.1.3.2 12 spare 1 13 maxCs 1 Maximum Coding Scheme

and modulation see 4.6

Header

Length

00H

44H

Class TBF

Mtype TBF-ESTABLISH-req


TBF_INDEX (LSB)

Padding

Padding



2006-2-22 3BK 09556 JAAA PBZZA 98/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

14 windowSize 2 Window size, always 64 in GPRS mode

64, �, 512

16 radioTS[0] 1 Time slot of the PDCH 0...7, NIL (FFh) 17 throughputClass[0] 1 TBF throughput class on

the PDCH 1...10, NIL(FFh)

18 USF[0] 1 Uplink State Flag (In UL) 0...7, NIL (FFh) 19 padding 1 20 radioTS[1] 1 Time slot of the PDCH 0...7, NIL (FFh) 21 ThroughputClass[1] 1 TBF throughput class on


22 USF[1] 1 Uplink State Flag (In UL) 0...7, NIL (FFh) 23 Padding 1 24 radioTS[2] 1 Time slot of the PDCH 0�7, NIL (FFh) 25 throughputClass[2] 1 TBF throughput class on

the PDCH 1�10, NIL(FFh)

26 USF[2] 1 Uplink State Flag (In UL) 0�7, NIL (FFh) 27 padding 1 28 radioTS[3] 1 Time slot of the PDCH 0�7, NIL (FFh) 29 throughputClass[3] 1 TBF throughput class on


30 USF[3] 1 Uplink State Flag (In UL) 0...7, NIL (FFh) 31 padding 1 32 radioTS[4] 1 Time slot of the PDCH 0...7, NIL (FFh) 33 throughputClass[4] 1 TBF throughput class on


34 USF[4] 1 Uplink State Flag (In UL) 0...7, NIL (FFh) 35 padding 1 36 radioTS[5] 1 Time slot of the PDCH 0...7, NIL (FFh) 37 throughputClass[5] 1 TBF throughput class on


38 USF[5] 1 Uplink State Flag (In UL) 0�7, NIL (FFh) 39 padding 1 40 radioTS[6] 1 Time slot of the PDCH 0...7, NIL (FFh) 41 throughputClass[6] 1 TBF throughput class on


42 USF[6] 1 Uplink State Flag (In UL) 0...7, NIL (FFh) 43 padding 1 44 radioTS[7] 1 Time slot of the PDCH 0�7, NIL (FFh) 45 throughputClass[7] 1 TBF throughput class on


46 USF[7] 1 Uplink State Flag (In UL) 0�7, NIL (FFh) 47 padding 1

RLC Control parameters 1 48 ULAPD 1 APD value used by the MS

or default APD 0,1,3,4,5,6,

8,10 49 ncPollingPolicy 1 Polling policy in Delayed

state according to the NC timer i.e. NC_REPORTING_PERIOD_T

0 = disableNCtimerDelayed 1 = enableNCtimerDelayed

50 tDelayedDlTbfPol 1 Period of emission of Dummy UL Command in Inactive state of the TBF

see § 3.1.3.2

51 tDelayedDlTbfPolInitial 1 Period of emission of the first Dummy UL Command in Inactive state of the TBF

see § 3.1.3.2

RLC QoS Parameters 52 rtflag 1 Indicate the TBF is a RT or

NRT. 0: NRT. The cr value is not valid.

1:RT. The cr value is valid.

53 priority 1 0..15



2006-2-22 3BK 09556 JAAA PBZZA 99/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


0..800 step size = 1. 1 means 0.01 radio block. � 800 means 8 radio block. See note.

56 nbBlockValidity 1 Indicate how many blocks should be scheduled by MAC with the priority indicated above.

- 0 : the indicated priority indicated above is to be used for an unspecified number of blocks >0 : the indicated priority indicated above is to be used only for NB_BLOCK_VALIDITY blocks scheduling (UL or DL)

57 spare 3

enCsAdaptation is set according to O&M parameters enCsAdaptationAck and enCsAdaptationNack. In Package 5, the enCsAdaptation flag is always set to disabled when the tbfMode is set to EGPRS.

In B9 the feature Delayed Downlink TBF Release is always switched ON, and the release of the TBF is managed by RRM.

The networkControlOrder is set to 0 or 2 in B9, when set to 0 the NC parameters are not relevant and NC alarm should not be sent. When set to 2 RLC takes the NC2 parameters into account and could report NC alarm.

The maxCs is given in the TBF-ACTIVATE-req for TBF establishment.

NbBlockValidity is set to �0� in this message.

Note:

For NRT TBF, the cr should be 0.

For RT TBF, if cr is 0, it means that the TBF is scheduled like when all the cr for a RT TBF have been used thanks to the extra scheduling mechanism.



2006-2-22 3BK 09556 JAAA PBZZA 100/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.9 TBF-ESTABLISH-cnf

This message is used to confirm the TBF establishment. Message type: TBF-ESTABLISH-cnf Direction: DSP to PPC

Header

Length

00H

10H

Class TBF

Mtype TBF-ESTABLISH-cnf


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range





2006-2-22 3BK 09556 JAAA PBZZA 101/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.10 TBF-MODIFY-req

This message is used to modify the TBF context. It may be use to change the radio configuration in case of GCH Release, the parameters related to the feature Delayed Downlink TBF Release, the number of pdch used but not the radio parameters like TFI, USF. The message is not acknowledged. Message type: TBF-MODIFY-req Direction: PPC to DSP

Header

Length

00H

44H

Class TBF

Mtype TBF-MODIFY-req


TBF_INDEX (LSB)

Padding

Padding


(in bits) Semantic Range

Same structure as 3.4.8 TBF-ESTABLISH-req

Note: enCsAdaptation is not on line changeable. Therefore if O&M parameters enCsAdaptationAck or enCsAdaptationNack change, they will be take in account at next TBF establishment.

The rlcMode and tbfMode are not on line changeable, RRM has to release and create a new TBF context. The PACCH_TS is not on line changeable, RRM has to use the reallocation procedure to change it.

The timers: tDelayedDLtbfPol, and tDelayedDLtbfPolInitial

are under RRM control. RRM changes the polling timer value to save Dummy UI Commands in DL Delayed state (modification: tDelayedDLtbfPol and tDelayedDLtbfPolInitial <--> tDelayedDLtbfPolUL) RRM changes the NC_POLLING_POLICY value according to T_DELAYED_DL_TBF_POL in DL Delayed state B9 note: networkControlOrder is now on line changeable, for RLC to apply a NC2-dedicated Polling Policy.

The maxCs could be changed with a TBF-MODIFY-req, especially to reduce or increase the modulation and coding scheme for an EGPRS TBF.

The ULAPD could be changed with a TBF-MODIFY-req.



2006-2-22 3BK 09556 JAAA PBZZA 102/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.11 TBF-REALLOC-req

This message is used to modify the TBF context. It may be use to change the radio allocation resources for a mobile. The message is acknowledged. Message type: TBF-REALLOC-req Direction: PPC to DSP

Header

Length

00H

44H

Class TBF

Mtype TBF-REALLOC-req


TBF_INDEX (LSB)

Padding

Padding


(in bits) Ch Semantic

RLC Local reference 0 trxIndex 2 Y To change the TRX

RLC initial control parameters 2 globalTFI 1 Y To change Global Temporary Block Flow Identifier3 tlliReq 1 N Useless, RRM already know the TLLI of the MS 4 rlcMode 1 N not allow to change the RLC mode 5 enCsAdaptation 1 N not allow to change this parameter 6 networkControlOrder 1 N not allow to change the networkControlOrder 7 tbfMode 1 N not allow to change the TBF mode 8 ARQtype 1 N Not allow to change the ARQ type 9 spare 1

RLC radio configuration 10 pacchTS 1 Y To change PACCH Time slot 11 pdchCount 1 Y To change the number of PDCHs 12 spare 1 13 maxCs 1 Y Maximum Coding Scheme and modulation 14 windowSize 2 Y In GPRS, the window is always 64 blocks so it

can't be modify. In EGPRS, the window is set according to the number of allocated timeslot by RRM.

16 radioTS[0] 1 Y Time slot of the PDCH 17 throughputClass[0] 1 Y TBF throughput class on the PDCH 18 USF[0] 1 Y Uplink State Flag (In UL) 19 padding 1 Y �



2006-2-22 3BK 09556 JAAA PBZZA 103/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

44 radioTS[7] 1 Y Time slot of the PDCH 45 throughputClass[7] 1 Y TBF throughput class on the PDCH 46 USF[7] 1 Y Uplink State Flag (In UL) 47 padding 2

RLC Control parameters 1 48 ULAPD 1 Y APD value used by the MS or default APD 49 ncPollingPolicy 1 N Use TBF_MODIFY_req 50 tDelayedDLtbfPol 1 N Use TBF_MODIFY_req 51 tDelayedDLtbfPolInitial 1 N Use TBF_MODIFY_req

RLC QoS Parameters 52 rtflag 1 Y Indicate the TBF is a RT or NRT. 53 priority 1 Y To change the priority.

54 cr 2 Y To change the Credit generation rate

56 nbBlockValidity 1 Y Indicate how many blocks should be scheduled by MAC with the priority indicated above.

57 spare 3

Note: Y means the parameter could change, i.e. it has to be checked and store in the TBF context. N means the parameter could not change, i.e. it is not checked and not store in the TBF context. For the Global TFI, only the TFI part could change i.e. not the first bit which determine the direction. The maxCs could be change when RRM triggers a reallocation because the O&M parameter could not be the same since the first activate sent at TBF establishment or in case of inter TRX reallocation when the BTS technology or the TRX Class force to change it. NbBlockValidity is always set to 0.



2006-2-22 3BK 09556 JAAA PBZZA 104/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.12 TBF-REALLOC-cnf

This message is used to confirm the TBF reallocation. Message type: TBF-REALLOC-cnf Direction: DSP to PPC

Header

Length

00H

14H

Class TBF

Mtype TBF-REALLOC-cnf


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Cs Info 0 currentCs 1 Current Coding Scheme See 4.6 1 padding 3





2006-2-22 3BK 09556 JAAA PBZZA 105/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.13 TBF-RELEASE-req

This message is used to release the TBF (UL or DL). Message type: TBF-RELEASE-req Direction: PPC to DSP

Header

Length

00H

08H

Class TBF

Mtype TBF-RELEASE-req


TBF_INDEX (LSB)

Padding

Padding



2006-2-22 3BK 09556 JAAA PBZZA 106/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.14 TBF-RELEASE-cnf

This message is used to confirm the TBF end. Message type: TBF-RELEASE-cnf Direction: DSP to PPC

Header

Length

00H

2CH

Class TBF

Mtype TBF-RELEASE-cnf


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

TBF Confirmation 0 ncCause 1 Cause of the cell reselection 0: NoAlrm

1: PT3 2: PT4

1 tbfCause 1 Cause of the refusal/failure See 4.4 2 debugInfo 6 Debug information See 4.7

LLC PDU Final Ack 8 number 2 LLC PDU number of the last

PDU acknowledged. 0�65535

PDU block structure 10 padding 1 11 pduBlockType 1 Packet Data Unit Type See 4.3, 4.2 12 pduBlock 24 RLC control PDU without

MAC header See 4.2, 4.1

The reported block is always set to Unknown block in this release.



2006-2-22 3BK 09556 JAAA PBZZA 107/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.15 TBF-RELEASE-ind

This message is used to indicate a TBF end. Message type: TBF-RELEASE-ind Direction: DSP to PPC

Header

Length

00H

2CH

Class TBF

Mtype TBF-RELEASE-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

TBF Confirmation 0 ncCause 1 Cause of the cell reselection 0: NoAlrm

1: PT3 2: PT4

1 tbfCause 1 Cause of the release. See 4.4 2 debugInfo 6 Debug information

See 4.7

LLC PDU Final Ack 8 number 2 LLC PDU number of the last

PDU acknowledged. 0�65535



The reported block is always set to Unknown block for a downlink TBF, and to Packet Control Acknowledgement block for an uplink TBF.



2006-2-22 3BK 09556 JAAA PBZZA 108/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.16 TBF-START-ind

This message is used to indicate the reception of the first RLC data block. Message type: TBF-START-ind Direction: DSP to PPC

Header

Length

00H

14H

Class TBF

Mtype TBF-START-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

Ms Properties 0 TLLI 4 Temporary Logical Link

Identifier 0�4294967295

4 tlliPresence 1 Flag to validate the content of TLLI field

0: not present, 1: present

5 padding 1

6 n3101 2 Number of unexpected RLC data block received

0...n3101Limit+C C = 125


EGPRS or GPRS RT or NRT TBF



0..127

11 spare 1

N3101 is used to tune the value C in (n3101Limit+C) limit.

The TLLI is only present when RRM was required the contention resolution in TBF establishment.

PFI is set to 0xFF if PTU could not provide it.



2006-2-22 3BK 09556 JAAA PBZZA 109/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.17 TBF-UL-CONTROL-ind

This message is used to indicate the received control block. Message type: TBF-UL-CONTROL-ind Direction: DSP to PPC

Header

Length

00H

24H

Class TBF

Mtype TBF-UL-CONTROL-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

NC Info 0 currentCs 1 Current Coding Scheme See 4.6 1 ncCause 1 Cause of the cell reselection 0: NoAlrm

1: PT3 2: PT4



The current CS given back by RLC is not used by RRM.

PDU_TYPE

Packet Cell Change Failure

Packet measurement report

Packet Cell Change Notification

Packet PSI Status

Packet SI Status

Packet Resource Request



2006-2-22 3BK 09556 JAAA PBZZA 110/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

BLOCK_TYPE

Channel 2 Request

Unknown Block



2006-2-22 3BK 09556 JAAA PBZZA 111/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.18 TBF-UL-UNITDATA-ind

This message is used to indicate the received LLC PDU. Message type: TBF-UL-UNITDATA-ind Direction: DSP to PPC

Header

Length

Variable ≤ 1576 bytes

Class TBF

Mtype TBF-UL-UNITDATA-ind


TBF_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range


EGPRS or GPRS RT or NRT TBF



0..127

3 spare 1

LLC UL PDU Block 4 length 2 LLC PDU length 8�1560 6 last 1 Indicate if the LLC PDU was

build with the last RLC data block (i.e. CV = 0)

0: not last LLC PDU 1: last LLC PDU

7 spare 1 8 pdu N LLC Packet Data Unit

PFI is set to 0xFF if PTU could not provide it.

N = 8 to 1560 bytes



2006-2-22 3BK 09556 JAAA PBZZA 112/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.19 TBF-PSCD-req

This message is used to request PTU to start or stop sending of PSCD. PTU is in charge of constructing PSCD and sending to MS. If (P)SI Status feature is not activated in the cell PMU should not send the message on the PMU-PTU interface. Message type: TBF-PSCD-req Direction: PPC to DSP

Header

Length

00H

2CH

Class TBF

Mtype TBF-PSCD-req


TBF_INDEX (LSB)

Padding

Padding


bytes)

Semantic Range

PSCD information

0 PD 1 Origin 0 = BCCH

1 = PBCCH

1 containerID 1 Reference of PSCD request from PMU to PTU. 0..3

2 action 1 Indication to satr a PSCD procedure or Abort current ongoing PSCD procedure.

0 = Start a PXCD

1 = Abort a PXCD

see note

3 spare 1

PSI & SI List

4 psi14SendingMark 2 PSI14 Sending Flag see note




2006-2-22 3BK 09556 JAAA PBZZA 113/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


bytes)

Semantic Range



12 psi3bisSendingMark 2 PSI3bis Sending Flag see note

14 sparePsiSendingMark 2

16 psi3quaterSendingMark 2 PSI3quater Sending Flag see note


20 si1SendingMark 2 SI1 Sending Flag see note



26 si2SendingMark 2 Si2 Sending Flag see note

28 si2bisSendingMark 2 Si2bis Sending Flag see note

30 si2terSendingMark 2 Si2ter Sending Flag see note

32 si2quaterSendingMark 2 Si2quater Sending Flag see note

34 si4SendingMark 2 Si4 Sending Flag see note

Note:

(P)SixSendingMark: PTU check the sendingMark for a specific instance of a (P)SI according to following format. PTU does not check the rationality of the sendingMark and just considers the max number of instance bits in the sendingMark Ignoring useless bit of the SendingMark even some of them is set to 1. For example Psi2 has 8 instances at most. If Psi2SendingMark is 0x1F01, RLC just consider 01 ignoring 1F. If RLC could not get PSI2 instance 0 from MAC, RLC donsn''t send any thing for this PSI and does not send cnf to PMU. RLC continues to process next sendingMark.

(p)siNsendingMark bits format: 8 7 6 5 4 3 2 1

1 Inst 15 Inst 8 2 Inst 7 Inst 0

If PD is set to BCCH, si13SendingMark, si1SendingMark, si3SendingMark, si2SendingMark, si2bisSendingMark, si2terSendingMark, si2quaterSendingMark, si4SendingMark are significant only.

Else, psi14SendingMark, psi1SendingMark, psi2SendingMark, psi3SendingMark, psi3bisSendingMark, psi3quaterSendingMark, psi8SendingMark are significant only.



2006-2-22 3BK 09556 JAAA PBZZA 114/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

action:

0: PMU requests PTU to start a PSCD procedure. If a PSCD is running then PTU should abort ongoing procedure first and then start a PSCD procedure again for the request. In this case no TBF-PSCD-cnf is needed for aborted PSCD procedure.

1:PMU requests PTU to abort the PSCD procedure "referenced by containerID". No TBF-PSCD-cnf is needed for this case.



2006-2-22 3BK 09556 JAAA PBZZA 115/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.20 TBF-PSCD-cnf

This message is used to confirmTBF-PSCD-req. If (P)SI Status feature is not activated in the cell PMU should not send the message on the PMU-PTU interface. Message type: PCC-PSCD-cnf Direction: DSP to PPC

Header

Length

00H

14H

Class TBF

Mtype PCC-PSCD-cnf

Reference TBF_INDEX(MSB)

TBF_INDEX(LSB)

Padding

Padding


bytes)

Semantic Range

PXCD reference

0 ContainerID 1 Reference given in the request

1 spare 3

Long Confirmation


5 cause 1 Cause of the refusal/failure See 4.4

6 debugInfo 6 See 4.7

In case of abnormal release of the TBF, RLC should confirm first the on going PSCD procedure



2006-2-22 3BK 09556 JAAA PBZZA 116/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.21 TBF-PNCD-req

This message is used to request PTU to start or stop the sending of PNCD. PTU is in charge of constructing PNCD and sending to MS. If NACC feature is not activated in the cell PMU should not send the message on the PMU-PTU interface.

Message type: TBF-PNCD-req Direction: PPC to DSP

Header

Length

Variable

Class TBF

Mtype TBF-PNCD-req


TBF_INDEX (LSB)

Padding

Padding


bytes)

Semantic Range

PNCD Information

0 PD 1 Origin 0 = BCCH

1 = PBCCH

1 containerID 1 Reference of PNCD request from PMU to PTU and Indicates a complete set of PNCD for a certain cell to MS.

0..3

2 pofAB 1 Flag Indicating the present of ARFCN&BSIC 0 = following ARFCN&BSIC is invalid

1 = following ARFCN&BSIC is valid

3 BSIC 1



2006-2-22 3BK 09556 JAAA PBZZA 117/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


bytes)

Semantic Range

4 ARFCN 2 See note

6 action 1 Indication to satr a PSCD procedure or Abort current ongoing PSCD procedure.

0 = Start a PXCD

1 = Abort a PXCD

see note

7 nbOfPduBlock 1 Number of following PDU block 3�10

(P)si PDU Block List

8 psiPdu[0] 24 See 4.17

32 psiPdu[1] 24 See 4.17

56 �

N psiPdu[nbofPduBlock-1] 24 See 4.17

Notes:

ARFCN bits format: 8 7 6 5 4 3 2 1

1 Arfcn9 Arfcn8 2 arfcn7 arfcn0

(P)SI PDU Block definition: If PD = BCCH, the pdu contains SI1, SI3 and SI13. If PD = PBCCH, the pdu containes PSI1, N (N<=8) PSI2 instances and PSI14.

action:

0: PMU requests PTU to start a PNCD procedure. If a PNCD is running then PTU should abort ongoing procedure first and then start a PNCD procedure again for the request. In this case no TBF-PNCD-cnf is needed for aborted PSCD procedure.

1: PMU requests PTU to abort the PNCD procedure "referenced by containerID". No TBF-PSCD-cnf is needed for this case.



2006-2-22 3BK 09556 JAAA PBZZA 118/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.22 TBF-PNCD-cnf

This message is used to confirmTBF-PNCD-req. If NACC feature is not activated in the cell PMU should not send the message on the PMU-PTU interface. Message type: PCC-PNCD-cnf Direction: DSP to PPC

Header

Length

00H

14H

Class TBF

Mtype PCC-PNCD-cnf


TBF_INDEX(LSB)

Padding

Padding


bytes)

Semantic Range

PXCD reference

0 containerID 1 Reference given in the request

1 spare 3

Long Confirmation



6 debugInfo 6 See 4.7

In case of abnormal release of the TBF, RLC should confim first the on going PNCD procedure



2006-2-22 3BK 09556 JAAA PBZZA 119/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.4.23 TBF-QOS-CONTROL-req

This primitive is used to update QoS parameters. Message type: TBF-QOS-CONTROL-req Direction: PPC to DSP

Header

Length

00H

10H

Class TBF

Mtype TBF-QOS-CONTROL-req


TBF_INDEX(LSB)

Padding

Padding


bytes)

Semantic Range

RLC QoS Parameters

0 rtflag 1 Indicate the TBF is a RT or NRT. 0: NRT. The cr value is not valid. 1:RT. The cr value is valid.

1 priority 1 0..15


0..800 step size = 1. 0 is reserved for NRT meaning �not significant�. 1 means 0.01 radio block.� 800 means 8 radio block.

4 nbBlockValidity 1 Indicate how many blocks should be scheduled by MAC with the priority

- 0 : the indicated priority indicated above is to be used for an unspecified number of blocks >0 : the indicated priority indicated above is to be used only for NB_BLOCK_VALIDITY blocks scheduling (UL or DL)

5 spare 3



2006-2-22 3BK 09556 JAAA PBZZA 120/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

NbBlockValidity is always set to 0.



2006-2-22 3BK 09556 JAAA PBZZA 121/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5 Class PDCH related to message TRX

3.5.1 PDCH-BLOCK-RESERVE-req

This message is used to request the reservation of an uplink block. Message type: PDCH_BLOCK-RESERVE-req Direction: PPC to DSP

Header

Length

00H

14H

Class TRX

Mtype PDCH_BLOCK-RESERVE-req


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PDCH Reference 0 radioTS 1 Time slot number 0�7 1 spare 3 4 reference 4 Request Reference

Block Parameter 8 delay 2 Minimum delay before

reserving the uplink block Step of 100 ms 0 = 0 ms Should be sized with respect to uplink reservation table size (see Nb_Of_Blocks_In_Future provided in DSP-INIT-cnf (see page 28).

10 padding 2



2006-2-22 3BK 09556 JAAA PBZZA 122/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5.2 PDCH-BLOCK-RESERVE-cnf

This message is used to confirm the UL block reservation. Message type: PDCH_BLOCK-RESERVE-cnf Direction: DSP to PPC

Header

Length

00H

1CH

Class TRX

Mtype PDCH_BLOCK-RESERVE-cnf


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PDCH Reference 0 radioTS 1 Time slot number 0�7 1 spare 3 4 reference 4 Request Reference

Block Reference 8 absoluteFN 2 Frame Number (16 bits) See 4.8

10 padding 2 Padding byte





2006-2-22 3BK 09556 JAAA PBZZA 123/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5.3 PDCH-DL-CONTROL-req

This message is used to send a message to the MS (in non DRX-mode (except for the downlink assignment) or in transfer mode). Message type: PDCH-DL-CONTROL-req Direction: PPC to DSP

Header

Length

00H

30H

Class TRX

Mtype PDCH-DL-CONTROL-req


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PDCH Control Request Configuration 0 radioTS 1 Time slot number 0�7 1 RAS 1 Message repetition is requested or

not 0 : no repetition 1 : repetition


TBF PDCH Control 8 logicalChannel 1 Logical channel used to convey the

control PDU 0 : PACCH 1 : PAGCH

9 poll 1 Request a MS response See 4.16 10 bsTxPower 1 BTS transmit power reduction (dB) 0�31, NIL(FFh) 11 localCnfReq 1 Local confirmation request See below 12 padding 2

PDU Block Structure 14 padding 1 15 pduBlockType 1 Packet Data Unit Type See 4.3, 4.2 16 pduBlock 24 RLC control PDU without MAC

header See 4.2, 4.1

The LOCAL_CNF_REQ could take the following value: 0: No confirmation required. 1: only positive confirmation when RAS is set to 0. 2: only negative confirmation when RAS is set to 0. 3: confirmation in every case when RAS is set to 0. 4: only negative confirmation on the first sending. 5: confirmation in every case on the first sending. 6: confirmation in every case on the last sending.



2006-2-22 3BK 09556 JAAA PBZZA 124/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

If a confirmation is required on first sending, no confirmation is sent again if repetition is not possible.

PDU_TYPE

Packet UL Assignment

Packet DL Assignment

Packet Time Slot Reconfigure

Packet Access Reject

Packet PDCH Release

Packet Power/Timing Advance Update

Packet Paging Request

Packet TBF Release

Packet Cell Change Order

Packet Cell Change Continue

Packet Measurement Order

Packet System Information 13

The LOCAL_CNF_REQ IE is only used when:

Sending the PACKET PDCH RELEASE PDU (BLOCKPDU_TYPE = Packet PDCH Release). In this case, it is set to systematic local confirmation.

Packet UL Assignment, DL Assignment and Time Slot Reconfigure in case of the first assignment sent for Resources reallocation.

Sending the PACKET DOWNLINK ASSIGNMENT on the PACCH of the TBF DL or UL. In this case, it is set to local negative confirmation.

RAS Repeated messages are:

Packet UL Assignment (*)

Packet Power/Timing Advance Update (*)

Packet Measurement Order (*)

Packet PDCH Release (**)

(*): Repetition is requested only in some cases (RAS = 1). The total number of messages is then : 1 + MacTrxInfoB8Cfg.nSigRepeat (indicated in Trx-Create-Req).

(**): Repetition is always requested (RAS = 1). The total number of messages is then : 1 + RrmPMacCfg.nPdchRelease (indicated in Dsp-Init-Req).



2006-2-22 3BK 09556 JAAA PBZZA 125/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5.4 PDCH-DL-CONTROL-cnf

This message is used to a local confirmation. Message type: PDCH-DL-CONTROL-cnf Direction: DSP to PPC

Header

Length

00H

18H

Class TRX

Mtype PDCH-DL-CONTROL-cnf


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PDCH Control Confirmation Configuration 0 radioTS 1 Time slot number 0�7 1 RRBP 1 RRBP value sent within the

polling request 0�3, NIL



01H = Nack (Failure) 9 cause 1 Cause of the refusal/failure See 4.4

10 debugInfo 6 Debug information See 4.7



2006-2-22 3BK 09556 JAAA PBZZA 126/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5.5 PDCH-UL-CONTROL-ind

This message is used to indicate the received control block/pdu. Message type: PDCH-UL-CONTROL-ind Direction: DSP to PPC

Header

Length

00H

2CH

Class TRX

Mtype PDCH-UL-CONTROL-ind


TRX _INDEX (LSB)

Padding

Padding


bytes)

Semantic Range

PDCH Reference 0 radioTS 1 Time slot number 0�7 1 spare 3 4 reference 4 Request Reference, relevant

only in case of Packet Control Acknowledgement or unknown PDU

CS Info 2 8 currentCs 1 Current CS if PDU_TYPE is

Packet Resource Request See 4.6

9 padding 1 PDU Block Structure

10 padding 1 11 pduBlockType 1 Packet Data Unit Type See 4.3 or 4.2 12 pduBlock 24 RLC control PDU without

MAC header See 4.1 or 4.2

BLOCK_TYPE

Packet Control Acknowledgement

(E)GPRS Packet Channel Request

Unknown PDU (no receipt from MS)



2006-2-22 3BK 09556 JAAA PBZZA 127/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PDU_TYPE

Packet Resource Request

Packet Cell Change Failure

Packet Measurement Report

Packet Cell Change Notification



2006-2-22 3BK 09556 JAAA PBZZA 128/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.5.6 PDCH-UL-REJECT-req

This message is used to send the Packet Access reject PDU to the MS. Message type: PDCH-UL-REJECT-req Direction: PPC to DSP

Header

Length

00H

24H

Class TRX

Mtype PDCH-UL-REJECT-req


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

PDCH Reject Parameter 0 radioTS 1 Time slot number 0�7 1 padding 1

PDU Block Structure 2 padding 1 3 pduBlockType 1 Packet Data Unit Type See 4.3 4 pduBlock 24 RLC control PDU without

MAC header See 4.1

BLOCK_TYPE

Access Reject



2006-2-22 3BK 09556 JAAA PBZZA 129/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.6 Class GCH related to message TRX

3.6.1 GCH-ESTABLISH-req

This message is used to establish one or multi GCH�s for both of DRFU and G3/G4. Message type: GCH-ESTABLISH-req Direction: PPC to DSP

Header

Length

Variable

Class TRX

Mtype GCH-ESTABLISH-req


TRX_INDEX (LSB)

padding

padding


(in bytes)

Semantic Range

GCH local reference 0 trxCapability 1 Maximum data capability of the

TRX 00: CS1 only (not used) 01: CS1 and CS2 10: CS1 to CS4 11: CS1 to CS4 and MCS1 to MCS9

1 Padding 1 2 tsList 1 List of time slot on which the GCH

is assigned Bitmap[0..7]: 0: not present. It means no GCH is assigned for the TS; 1:present. It means a GCH is assigned for the TS. see note

3 TREid 1 Indicates on which TRE the GCH is established. Only used for G3/G4 TRX.

0..23

4 reference 4 RRM transmission reference GCH list

8 padding 3



2006-2-22 3BK 09556 JAAA PBZZA 130/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

11 nrGch 1 Number of GCH in the list 1�36 12 gchIndex[0] 2 First GCH context index See 4.9 14 padding[0] 2

� N gchIndex[nrGch-1] 2 Last GCH context index See 4.9

N+2 padding[nrGch-1] 2 Note: (1) tsList is only used by DRFU in this version. For G3/G4, it is always set to 0x00. (2) For DRFU, nrGch should be equal to the number of RTS�s described in the tsList. When the number of GCH is less than the maximum, the usefull gchIndex are filled at the beginning of the list. The gchIndex corresponding to the useful lowest RTS should be gchIndex[0], the gchIndex correstponding to the highest useful RTS should be gchIndex[nrGch-1] and so on. For the corresponding relationship of bit and RTS please refer to 3.1.1.

Example:

tsList = 0x11(0B00010001) 8 7 6 5 4 3 2 1 1 0 0 0 1 0 0 0 1

So: nrGch = 2 gchIndex[0] is the GCHid corresponding to RTS3 gchIndex[1] is the GCHid corresponding to RTS7. No other gchIndex is needed. For G3/G4, GCH list offers all gchIndex�s that are asked to be established.



2006-2-22 3BK 09556 JAAA PBZZA 131/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.6.2 GCH-ESTABLISH-cnf

This message is the response of the GCH establishment request. Message type: GCH-ESTABLISH-cnf Direction: DSP to PPC

Header

Length

Variable

Class TRX

Mtype GCH-ESTABLISH-cnf


TRX_INDEX (LSB)

padding

padding


(in bytes)

Semantic Range




is assigned Bitmap[0..7]: 0: not present. It means no GCH is established successfully for the TS; 1:present. It means a GCH is established successfully for the TS. see note


0..23

4 reference 4 RRM transmission reference

GCH remote parameters 8 trxCapability 1 Maximum data capability of the


9 padding 1 10 spare 1 11 roundTripTime 1 Time difference between a

downlink radio block and an uplink radio block

see § 3.1.3.1

GCH Confirmation 12 gchCnf 8 or

156 Refer to following description.



2006-2-22 3BK 09556 JAAA PBZZA 132/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

If all GCH�s in the GCH-Establish-req are established unsuccessfully, the gchCnf is as follows:

Long Confirmation

12 ackNack 1 Result of the Request 00H = Ack (Success), 01H = Nack (Failure)

13 cause 1 Cause of the refusal/failure See 4.4 14 debugInfo 6 Debug information See 4.7

The value of ackNack is Nack.

Else, if all or part of GCH�s in the GCH-Establish-req are established successfully, the gchCnf is as follows:

Extended Long GCH Confirmation


13 cause 1 Cause of the refusal/failure See 4.4 14 debugInfo 6 Debug information See 4.7 20 padding 3 23 nrGch 1 Number of GCH following 1..36 24 gchIndex[0] 2 see 4.9, see note 26 padding[0] 2

� N gchIndex[nrGch-1] 2 see 4.9, see note

N+2 padding[nrGch-1] 2

The value of ackNack is Ack.

Note:

(1) tsList is only used by DRFU in this version. For G3/G4, it is always set to 0x00. (2) Extended Long GCH Confirmation only contains the sucessful GCH list. For DRFU, nrGch should be equal to the number of RTS�s described in the tsList. When the number of GCH is less than the maximum, the usefull gchIndex are filled at the beginning of the list. The gchIndex corresponding to the useful lowest RTS should be gchIndex[0], the gchIndex correstponding to the highest useful RTS should be gchIndex[nrGch-1] and so on. For the corresponding relationship of bit and RTS please refer to 3.1.1.

Example:

tsList = 0x11(0B00010001) 8 7 6 5 4 3 2 1 1 0 0 0 1 0 0 0 1

So: nrGch = 2 gchIndex[0] is the GCHid corresponding to RTS3 gchIndex[1] is the GCHid corresponding to RTS7. No other gchIndex is needed.

The round trip time corresponds to difference between the current DBN and the received UBN.



2006-2-22 3BK 09556 JAAA PBZZA 133/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.6.3 GCH-RELEASE-req This message is used to used to release some or all GCH for both of DRFU and G3/G4.

Message type: GCH-RELEASE-req Direction: PPC to DSP

Header

Length

Variable

Class TRX

Mtype GCH-RELEASE-req


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range



1 padding 1 2 tsList 1 List of time slot on which the GCH

is askd to be relesed Bitmap[0..7] see note


0..23

4 reference 4 RRM transmission reference GCH list

8 padding 3 11 nrGch 1 Number of GCH in the list 1�36 12 gchIndex[0] 2 First GCH context index See 4.9 14 padding[0] 2

� N gchIndex[nrGch-1] 2 Last GCH context index See 4.9

N+2 padding[nrGch-1] 2 Note: (1) tsList is only used by DRFU in this edition. For G3/G4, it is always set to 0x00. (2) For DRFU, nrGch should be equal to the number of RTS�s described in the tsList. When the number of GCH is less than the maximum, the useful gchIndex are filled at the beginning of the list. The gchIndex corresponding to the useful lowest RTS should be gchIndex[0], the gchIndex correstponding to the useful highest RTS should be gchIndex[nrGch-1] and so on.



2006-2-22 3BK 09556 JAAA PBZZA 134/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Example:

tsList = 0x11(0B00010001) 8 7 6 5 4 3 2 1 1 0 0 0 1 0 0 0 1

So: nrGch = 2 gchIndex[0] is the GCHid corresponding to RTS3 gchIndex[1] is the GCHid corresponding to RTS7. No other gchIndex is needed. For G3/G4, GCH list offers all gchIndex�s that are asked to be released.



2006-2-22 3BK 09556 JAAA PBZZA 135/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.6.4 GCH-RELEASE-cnf

This message is the response to the GCH link release. Message type: GCH-RELEASE-cnf Direction: DSP to PPC

Header

Length

00H

16H

Class TRX

Mtype GCH-RELEASE-cnf


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range




is assigned Bitmap[0..7] : 0: not present. It means no GCH is released successfully for the TS; 1:present. It means a GCH is released successfully for the TS. see 3.1.1


0..23

4 reference 4 RRM transmission reference

Long Confirmation 8 ackNack 1 Result of the Request 00H = Ack

(Success), 01H = Nack (Failure)

9 cause 1 Cause of the refusal/failure See 4.4 10 debugInfo 6 Debug information See 4.7



2006-2-22 3BK 09556 JAAA PBZZA 136/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Note:

(1) tsList is only used by DRFU in this version. For G3/G4, it is always set to 0x00.



2006-2-22 3BK 09556 JAAA PBZZA 137/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.6.5 GCH-RELEASE-ind

This message is used to indicate a GCH link lost. Message type: GCH-RELEASE-ind Direction: DSP to PPC

Header

Length

Variable

Class TRX

Mtype GCH-RELEASE-ind


TRX_INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range




is assigned Bitmap[0..7] 0: not present. It means no GCH is indicated to intend to be released for the TS; 1:present. It means a GCH is indicated to intend to be released for the TS.

see note 3 TREid 1 Indicates on which TRE the GCH

is established. Only used for G3/G4 TRX.

0..23

4 reference 4 RRM transmission reference Extended Long GCH Confirmation





2006-2-22 3BK 09556 JAAA PBZZA 138/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

10 debugInfo 6 Debug information See 4.7 16 padding 3 19 nrGch 1 Number of GCH following 1..36 20 gchIndex[0] 2 see 4.9, see note 22 padding[0] 2

� N gchIndex[nrGch-1] 2 see 4.9, see note

N+2 padding[nrGch-1] 2

The GCH release indication could mean: some or all GCH link�s lost for example a transmission error, or a protocol error.

Note:

(1) ackNack is not used in the message. (2) Extended Long GCH Confirmation offers a list of GCH that is indicated to intend to be released by PTU. (3) tsList is only used by DRFU in this edition. For G3/G4, it is always set to 0x00. (4) For DRFU, nrGch should be equal to the number of RTS�s described in the tsList. When the number of GCH is less than the maximum, the useful gchIndex are filled at the beginning of the list. The gchIndex corresponding to the useful lowest RTS should be gchIndex[0], the gchIndex correstponding to the useful highest RTS should be gchIndex[nrGch-1] and so on.

Example:

tsList = 0x11(0B00010001) 8 7 6 5 4 3 2 1 1 0 0 0 1 0 0 0 1

So: nrGch = 2 gchIndex[0] is the GCHid corresponding to RTS3 gchIndex[1] is the GCHid corresponding to RTS7. No other gchIndex is needed. For G3/G4, GCH list offers all gchIndex�s that are asked to be released.



2006-2-22 3BK 09556 JAAA PBZZA 139/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.7 Class L2GCH

The following messages are only used with a specific software (different from the operational one) for tests purpose.

In data fields, the RLC/MAC header is included.

3.7.1 L2GCH-DATA-req

Message type: L2GCH-DATA-req Direction: PPC to DSP

Header

Length

00H

34h

Class TRX

Mtype L2GCH-DATA-req


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

GCH Data 0 gchIndex 2 GCH context index See 4.9 2 dataLength 2 Data length 0�38 4 data 38

42 padding 2



2006-2-22 3BK 09556 JAAA PBZZA 140/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

3.7.2 L2GCH-DATA-ind

Message type: L2GCH-DATA-ind Direction: DSP to PPC

Header

Length

00H

34h

Class TRX

Mtype L2GCH-DATA-ind


TRX _INDEX (LSB)

Padding

Padding


(in bytes)

Semantic Range

GCH Data 0 gchIndex 2 GCH context index See 4.9 2 dataLength 2 Data length 0�38 4 data 38 data

42 padding 2



2006-2-22 3BK 09556 JAAA PBZZA 141/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4 PARAMETER DESCRIPTIONS

4.1 BLOCK

The block is an Alcatel�s information used to build the message sent/received from the air interface.

All BLOCK lengths = 24 bytes (CS-1) with padding.

4.1.1 Packet Channel request BLOCK


(in bytes)

Semantic Range

0 absoluteFN 2 Frame Number where the Packet Channel Request was received

See 4.8

2 TST 1 Training Sequence type 0: normal TS 1: 8-PSK capability in uplink 2: no 8-PSK capability in uplink

3 spare 1 4 taValue 1 Timing Advance Value 0..63 5 burstType 1 00H = 8 bits,

01H = 11 bits 6 burstContent 2 Packet Channel request

content

8 padding 16 In case the TST is set to 1 or 2 the DSP should set the burstType to 01 (11 bits) and In case the TST is set to 0 the DSP should set the burstType to the value accessBurstType defined in the TRX_SYS_DEFINE_REQ message. Example for One Phase Access: 8 bits format: 8 7 6 5 4 3 2 1

1 2 1 M5 M4 M3 M2 M1 P2 P1

11 bits format: 8 7 6 5 4 3 2 1

1 0 M5 M4 2 M3 M2 M1 P2 P1 R3 R2 R1

M5�M1: MultislotClass P2�P1: Priority R3�R1: RandomBits



2006-2-22 3BK 09556 JAAA PBZZA 142/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.1.2 Channel 2 Request BLOCK

Channel 2 Request BLOCK = Channel Request Description IE in [ 6 ]. Byte Parameters Length

(in bytes)

Semantic Range

0 peakThroughputClass 1 Maximum rate at which data is expected to be transferred across the network for the individual PDP context of the LLC PDU that caused the Channel Request Description IE to be transmitted.

1..9 1: Up to 8 Kbits/s 2: Up to 16 Kbits/s � 9:Up to 2048 Kbits/s

1 priority 1 Priority of the requested TBF 00H (Priority Level 1 � Highest)..03H (Priority Level 4 � Lowest)

2 rlcMode 1 RLC mode of the requested TBF

00H (ACK) .. 1 (NACK)

3 llcFrameType 1 The type of the first LLC frame to be transmitted over the requested TBF

00H (ACK or SACK)..01H (Others)

4 rlcOctetCount 2 The bytes number of RLC data the MS wishes to transfer

00H = 150 to 199, 01H = 200 to 249, 02H = 250 to 299, FFH = 12900 to 12949 or Open Ended TBF

6 padding 18

4.1.3 Control Acknowledgement BLOCK

Control Acknowledgement BLOCK = Packet Control Acknowledgement received in burst format. Byte Parameters Length

(in bytes)

Semantic Range

0 absoluteFN 2 Frame Number where the message was received

2 spare 2 4 taValue 1 Timing Advance Value 0..63 5 burstType 1 00H = 8 bits,

01H = 11 bits 6 burstContent 2 8 padding 16

8 bits format: 8 7 6 5 4 3 2 1

1 2 M6 M5 M4 M3 M2 M1 C2 C1

11 bits format: 8 7 6 5 4 3 2 1

1 M9 M8 M7 2 M6 M5 M4 M3 M2 M1 C2 C1

M9�M1: MESSAGE_TYPE C2�C1: CTRL_ACK



2006-2-22 3BK 09556 JAAA PBZZA 143/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.1.4 Access Reject BLOCK

Access Reject BLOCK = Reject struct IE in [ 6 ](with Packet Request Reference) Byte Parameters Length

(in bytes)

Semantic Range

0 packetRejectRef 4 Packet Request Reference See 4.13 4 waitIndication 1 The time the MS shall wait

before attempting another channel Request

0..255 (seconds) NIL

5 waitIndicationSize 1 Indicates the unit of the WAIT_INDICATION field

0: units of seconds 1: units of 20 ms

6 allocationRef 1 Allocation Reference used for fixed allocation

NIL

7 padding 17

4.1.5 Paging CS BLOCK


(in bytes)

Semantic Range

0 tmsi 4 Temporary Mobile Subscriber Identity

0..4294967295

4 imsiPresence 1 If IMSI is not Present then TMSI is mandatory

00H = Not present, 01H = Present

5 imsi 9 International Mobile Subscriber Identity

See 4.11, GSM 4.08

14 chanNeeded 1 The type of the channel 00H = Any channel, 01H = SDCCH, 10H = TCH/F (Full Rate), 03H = TCH/H or TCH/F (Dual Rate)

15 eMLPPPriority 1 Priority field : not used Always 0xFF 16 padding 8

4.1.6 Paging PS BLOCK


(in bytes)

Semantic Range

0 ptmsi 4 The Packet Temporary Mobile Station Identity

0..4294967295

4 imsiPresence 1 If IMSI is not Present then PTMSI is mandatory

00H = Not present, 01H = Present

5 imsi 9 International Mobile Subscriber Identity

See 4.11, GSM 4.08

14 padding 10



2006-2-22 3BK 09556 JAAA PBZZA 144/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.1.7 Unknown BLOCK


(in bytes)

Semantic Range

0 padding 24

4.2 PDU

The PDU is the RLC_CONTROL_PDU with 2 padding bytes.

The RLC_CONTROL_PDU is the part of a RLC / MAC block carrying a control message.

See GSM 04.60. (RLC control PDU without MAC header � 22 bytes) Byte Parameters Length

(in bytes)

Semantic Range

0 content 22 22 padding 2

4.3 BLOCK_TYPE

Alcatel specific messages

Bit Bit

8 7 6 5 4 3 2 1

Others

0 1 0 0 0 0 0 0 Channel 2 Request (issued from Packet Downlink Ack/Nack)

0 1 0 0 0 0 1 0 Control Acknowledgement (Access_burst)

0 1 0 0 0 0 1 1 Paging PS (Packet Switched)

0 1 0 0 0 1 0 0 Paging CS (Circuit Switched)

0 1 0 0 0 1 0 1 Access Reject

0 1 0 0 0 1 1 0 Packet Channel Request (access burst; FN, TA value)

1 1 1 1 1 1 1 1 Unknown



2006-2-22 3BK 09556 JAAA PBZZA 145/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.4 CAUSE

4.4.1 Introduction

This section precises the different values of the cause field within the confirm and indication messages.

4.4.2 Restriction

The report supplied by DSP in case of a request message received in a not convenient state is not defined in this section. This report is performed via a DSP-ALARM-ind.

4.4.3 Rule for cause value assignment

In order to distinguish the errors detected on entities of different types, a specific range of values is assigned to the errors related to one entity type. The first digit of the value correspond to the entity class conveyed by the message, excepted for the errors common to several entities for which a dedicated first digit is assigned (�F�).

Value range

(hexadecimal)

Entity

F0 to FE Common

00 to 0F DSP

10 to 1F TRX

20 to 3F TBF

40 to 5F TRX or GCH

�FF� is used to indicate that the result is meaningless if no cause is reported

4.4.4 DSP-INIT-CNF

CAUSE Value DESCRIPTION

Parameter error F0 An error is detected on mainly a dimensioning parameter.

4.4.5 DSP-MODIFY-CNF


Dsp not activated 0x0A The DSP was not activated

Parameter error 0xF0 An error is detected on mainly a dimensioning parameter.



2006-2-22 3BK 09556 JAAA PBZZA 146/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.4.6 DSP-PAGE-MS-CNF


No Block available 0x11 No free PPCH block is available to send the Packet Paging Request

Queue Full 0x15 No paging resource, or PACCH or PAGCH queues are full (the message is discarded)

Life time expiry 0x10 The Control PDU life time has expired

TRX Not Operational 0x12 TRX(s) is (are) not created

Master Pdch isn�t established

0x13 The Master PDCH is not established in the TRX

Multiple errors 0xFA Multiple errors

4.4.7 DSP-TRX-PMGAUGE-cnf



4.4.8 DSP-TRX-PMCOUNTER-cnf



4.4.9 DSP-TRX-SAMPLE-cnf



4.4.10 TRX-CREATE-CNF



TRX already created 0x14 The TRX is already created

Dsp not activated 0x0A The DSP was not activated



2006-2-22 3BK 09556 JAAA PBZZA 147/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.4.11 TRX-DELETE-CNF


TRX Not Operational 0x12 The TRX is not created

Gch still connected 0x51 GCH are still connected

4.4.12 TRX-NO-PPCH-IND



Control PDU life time expiry 0x10 Control PDU lifetime has expired.

No available block 0x11 No uplink block is available to convey the acknowledgement from the MS.

Queue Full 0x15 No paging resource, or PACCH or PAGCH queues are full (the message is discarded)



0x13 The Master PDCH is not established

Multiple errors 0xFA Multiple errors

4.4.13 TRX-MODIFY-CNF




4.4.14 TRX-SYS-DEFINE-CNF





0x13 The Master PDCH is not established

Missing mandatory PSI 0x16 Mandatory PSI are forgotten

MAX PDCH DSP limit 0x17 MAX_PDCH_DSP limit reached on the DSP



2006-2-22 3BK 09556 JAAA PBZZA 148/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.4.15 TBF-ESTABLISH-CNF



Wrong USF 0x30 Already given USF on the PDCH

TBF already assigned 0x31 TBF already created (TBF index)

DSP congestion 0x21 Insufficient memory. The DSP memory has reached the threshold above which no TBF establishment shall be accepted.

Max number of TBF 0x32 The maximum number of TBF is overtaken for one PDCH defined within the request.


PDCH not established 0x4F One of the PDCH is not established

No Free TBF Number 0x2E No TBF number for TBF allocation


4.4.16 TBF-ACTIVATE-CNF



Traffic ongoing 0x27 TBF has not finished to transfer traffic.

4.4.17 TBF-REALLOC-CNF



Wrong USF 0x30 Already given USF on the PDCH

Max number of TBF 0x32 The maximum number of TBF is overtaken for one PDCH defined within the request.

ReleaseOnGoing 0x33 The TBF will be soon release




2006-2-22 3BK 09556 JAAA PBZZA 149/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PDCH not established 0x4F One of the PDCH is not established

No Free TBF Number 0x2E No TBF number for TBF allocation

CS Reduction Not Allowed 0x34 CS/MCS reduction not allowed


4.4.18 TBF-DEACTIVATE-CNF



Pdch not established 0x4F one of the PDCH is not established

4.4.19 TBF-RELEASE-CNF


None

4.4.20 TBF-RELEASE-IND


Normal end 0x20 The TBF transfer is correctly finished. All the data was transmitted.

DSP congestion 0x21 Insufficient memory. The DSP memory has reached the threshold above which no TBF establishment shall be accepted.

Link lost 0x22 Too many RLC PDUs are lost on the radio link.

Contention failed 0x24 For an uplink TBF, the TLLI contention resolution has failed with the MS

MS bug 0x28 A MS bug has been detected several consecutive times

Tx efficiency too low 0x29 The transmission efficiency is too low

Blocking situation 0x2A Blocking situation is detected which may lead to an endless TBF

T-TBF-active expiry 0x2B The timer TBF activate is expired before receiving the first PDU



2006-2-22 3BK 09556 JAAA PBZZA 150/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


MS Protocol Error 0x23 A protocol Error with the MS has been detected several consecutive times

No RLC data block 0x2C USF has been scheduled but no RLC data block have been received

TBF Not operational 0x2D The activate request is missing

4.4.21 TBF-PNCD-CNF and TBF-PSCD-CNF


Normal end 0x20 The TBF transfer is correctly finished. All the data was transmitted.

Abnormal end 0x25 The TBF is abnormally released

(P)SI updated 0x26 The (P)SI blocks have been updated

4.4.22 PDCH-BLOCK-RESERVE-CNF


Trx Not Operational 0x12 The TRX doesn�t exist

Parameter error 0xF0 An Error is detected on mainly a dimensioning parameter

No Block available 0x11 No Uplink block are available for the PDCH to convey the acknowledge

PDCH not established 0x4F The PDCH is not established


4.4.23 PDCH-DL-CONTROL-CNF


Queue full 0x15 The control message queue is full and the control message is discarded.



2006-2-22 3BK 09556 JAAA PBZZA 151/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

Trx Not Operational 0x12 The TRX doesn�t exist

PDCH not established 0x4F On e of the PDCH is not established


4.4.24 GCH-ESTABLISH-CNF

CAUSE Value DESCRIPTION Layer

Unknown cause 0xFE Unknown cause from BTS GCH

TRX Not Operational 0x12 The TRX is not created MAC

Testab expiry 0x41 Not all answers are received from the BTS at Testab expiration.

GCH

Invalid parameters detected in BTS

0x42 Invalid parameters received by the BTS GCH

DL loss of synchro 0x45 Down link loss of synchronization detected in the BTS

GCH

Protocol error 0x4C A protocol error is detected by the BTS GCH

Unexpected DBN 0x4D An unexpected DBN is received by the BTS GCH


MAC or GCH

Radio TS mismatch 0x52 The time slot is prempted for GSM call GCH

Unexpected event 0xF1 An unexpected event has been received GCH/MAC

MAX PDCH DSP limit 0x17 MAX_PDCH_DSP limit reached on the DSP MAC

Treq_pending expiry 0x40 The request has not been processed GCH

4.4.25 GCH-RELEASE-CNF


Trelease expiry 0x43 Not all response from the BTS at Trelease expiration.

GCH


MAC or GCH



2006-2-22 3BK 09556 JAAA PBZZA 152/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.


Trx Not Operational 0x12 The TRX is not operational. MAC

Pdch not established 0x4F The PDCH is not established MAC

MEGCH not established 0x50 The MEGCH is not established MAC

Unexpected event 0xF1 An unexpected event has been received MAC or

GCH


4.4.26 GCH-RELEASE-IND


Unknown cause 0xFE Unknown cause from BTS GCH

Invalid parameters by BTS 0x42 Invalid parameters received by the BTS GCH

UL loss of synchro 0x44 The loss of frame synchronization is detected in UL. GCH

DL loss of synchro 0x45 Down link loss of synchronization detected in the BTS.

GCH

BTS desynchronized 0x46 MFS-BTS block desynchronized (block correction not acknowledged by BTS).

GCH

Erroneous BNE 0x47 A block with an out of range number is received. GCH

Erroneous frame type 0x48 Unknown frame type or not expected frame. GCH

Erroneous UBN 0x4B The value of UBN is out of range GCH

Protocol error 0x4C Protocol error detected by the BTS GCH

Unexpected DBN 0x4D unexpected DBN received by the BTS GCH


Exceed BTS limit 0x49 The established GCHs exceeding the BTS limit. Only for G3/G4 BTS.

GCH



2006-2-22 3BK 09556 JAAA PBZZA 153/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.5 Class

The Class element defines a table class managed inside DSP. Class (Hexa) Class name Description

0x00 DSP DSP 0x01 TRX Cell 0x02 TBF Temporary Block Flow 0x03 PDCH Packet Data CHannel are carried by the class TRX 0x04 GCH GPRS CHannel are carried by the class TRX 0x05 Not used 0x06 L2GCH L2 GPRS CHannel are used for tools environment

4.6 Coding scheme 00H: CS1 01H: CS2 02H: CS3 03H: CS4 10H: MCS1 11H: MCS2 12H: MCS3 13H: MCS4 14H: MCS5 15H: MCS6 16H: MCS7 17H: MCS8 18H: MCS9 FFH: Current one

4.7 DEBUG INFO In any case, this information is very useful and must be dump in trace file.

When the error cause is dimensioning parameter error (0xF0), the debug information represents the byte position of the parameter in the message.

4.8 FN

Byte 7 6 5 4 3 2 1 0

0 T�1 T3 (MSB)

1 T3 (LSB) T2

The T1� field is coded as the binary representation of (FN div 1326) mod 32.

The T3 field is coded as the binary representation of FN mod 51.

The T2 field is coded as the binary representation of FN mod 26.

The frame number, FN modulo 42432 can be calculated as 51x((T3-T2) mod 26)+T3+51x26xT1�.



2006-2-22 3BK 09556 JAAA PBZZA 154/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.9 GCH-index

Reference 16 kbits = GCH-INDEX (Range = 0 � maxGchDsp � 1)

For GPU2 and GPU3:

The DSP shall handle 120 channels among 32 (64 Kbps TS) x 4 (16 Kbps GCH per 64 Kbps channel) x 4 (MIC links number) channels (512 GCH).

The 8 Mbit/s link configuration at DSP side is as follow (fixed):

16 Kbits GCH

GCH Index 0 / 1 / 2 / 3 �....... 116/117/118/119

not used

64 Kbit/s channel number

0 �........ 29 30�..... 127

For MX:

The DSP shall handle 480 channels among 32 (64 Kbps TS) x 4 (16 Kbps GCH per 64 Kbps channel) x 4 (MIC links number) channels (512 GCH).

4.10 Global TFI

Warning: This coding is only valid for PMU/PTU interface and not for Air messages. Parameters Presence Length

(in bits) Semantic Range

DIRECTION M 1 Direction (UL or DL) 0 : uplink

1 : downlink TFI M 5 for

uplink and 5 for downlink

TBF identifier

Uplink

Byte 7 6 5 4 3 2 1 0

0 D=0 0 0 TFI

Downlink

Byte 7 6 5 4 3 2 1 0

0 D=1 0 0 TFI



2006-2-22 3BK 09556 JAAA PBZZA 155/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.11 IMSI / Mobile Identity • Mobile Identifier IE is formatted as follow (GSM 4.08) :

Byte Parameters Presence Length (in bits)

Semantic Range

0 Length of Mobile Identity contents M 8 1 Identity Digit 1 M 4 BCD Digit 0..9, NIL (FH) 1 Odd/Even indicator M 1 0: Even

1: Odd 1 Type of identity M 3 001: IMSI

010: IMEI 011: IMEISV 100: TMSI 000: No identity

2 Identity Digit 3 0 4 BCD Digit 0..9, NIL (FH) 2 Identity Digit 2 0 4 BCD Digit 0..9, NIL (FH) 3 Identity Digit 5 0 4 BCD Digit 0..9, NIL (FH) 3 Identity Digit 4 0 4 BCD Digit 0..9, NIL (FH) 4 Identity Digit 7 0 4 BCD Digit 0..9, NIL (FH) 4 Identity Digit 6 0 4 BCD Digit 0..9, NIL (FH) 5 Identity Digit 9 0 4 BCD Digit 0..9, NIL (FH) 5 Identity Digit 8 0 4 BCD Digit 0..9, NIL (FH) 6 Identity Digit 11 0 4 BCD Digit 0..9, NIL (FH) 6 Identity Digit 10 0 4 BCD Digit 0..9, NIL (FH) 7 Identity Digit 13 0 4 BCD Digit 0..9, NIL (FH) 7 Identity Digit 12 0 4 BCD Digit 0..9, NIL (FH) 8 Identity Digit 15 0 4 BCD Digit 0..9, NIL (FH) 8 Identity Digit 14 0 4 BCD Digit 0..9, NIL (FH)

If the number of digits is even, the bits 5 to 8 of the last byte are coded �1111�

Byte 7 6 5 4 3 2 1 0

0 Length of Mobile Identity Contents

1 Identity Digit 1 odd/

even Type of Identity

2 Identity Digit 3 Identity Digit 2

P Identity Digit p+1 Identity Digit p

8 Identity Digit 15 Identity Digit 14



2006-2-22 3BK 09556 JAAA PBZZA 156/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.12 Mtype

Mtype (Hexa) Message Name Message description

Class DSP (0x00) 0x02 DSP-CONGESTION-ind To indicate the congestion threshold was reached 0x04 DSP-INIT-req To provide the layer configuration parameters 0x05 DSP-INIT-cnf 0x08 DSP-MODIFY-req To modify the larger configuration parameters 0x09 DSP-MODIFY-cnf 0x0B DSP-PAGE-MS-req To find a packet paging message on air interface 0x0C DSP-PAGE-MS-cnf 0x0E DSP-TRANSPARENT-req 0x0F DSP-TRANSPARENT-cnf 0x11 DSP-ALARM-ind 0x12 DSP-GET-PM-req 0x13 DSP-GET-PM-cnf 0x14 DSP-TRX-PMGAUGE-req 0x15 DSP-TRX-PMGAUGE-cnf 0x16 DSP-TRX-PMCOUNTER-req 0x17 DSP-TRX-PMCOUNTER-cnf 0x18 DSP-TRX-SAMPLE-req 0x19 DSP-TRX-SAMPLE-cnf 0x1A DSP-LOAD-ind

0x20 � 0x2F Unused 0x30 DSP-TRANSPARENT-PERF-req 0x31 DSP-TRANSPARENT-DUMP-req 0x32 DSP-TRANSPARENT-MODIFY-req 0x33 DSP-TRANSPARENT-PPC-req

0x34 � 0x37 Reserved for transparent message from PMU to PTU 0x38 DSP-TRANSPARENT-PERF-cnf 0x39 DSP-TRANSPARENT-DUMP-cnf 0x3A DSP-TRANSPARENT-MODIFY-cnf 0x3B DSP-TRANSPARENT-PPC-cnf 0x3C DSP-TRANSPARENT-TRACE-ind

0x3D ... 0x3F Reserved for transparent message from PTU to PMU Class TRX (0x01)

0x40 TRX-CREATE-req To create a cell context (configuration parameters) 0x41 TRX-CREATE-cnf 0x44 TRX-DELETE-req To delete a cell context 0x45 TRX-DELETE-cnf 0x48 TRX-PPCH-req To send the Packet DL Assignment PDU to the MS on PCCCH (using DRX

parameters) 0x56 TRX-NO-PPCH-ind 0x4C TRX-MODIFY-req To modify the cell context 0x4D TRX-MODIFY-cnf 0x50 TRX-SYS-DEFINE-req To provide logical channel configuration and packet system information 0x51 TRX-SYS-DEFINE-cnf

0x52... 0x7F Unused Class TBF (0x02)

0x80 TBF-ACTIVATE-req To start the TBF and the allocation of radio resource 0x81 TBF-ACTIVATE-cnf 0x82 TBF-DEACTIVATE-req To Stop the TBF 0x83 TBF-DEACTIVATE-cnf 0x84 TBF-DL-FLOW-CTRL-ind To suspend/resume the DL data flow 0x85 TBF-PNCD-req To send PNCD to MS 0x86 TBF-PNCD-cnf 0x87 TBF-PSCD-req To send PSCD to MS 0x88 TBF-PSCD-cnf 0x89 TBF-QOS-CONTROL-req To change the QoS parameters.

0x8A�0x8B Unused 0x8C TBF-DL-UNITDATA-req To send DL LLC PDU 0x90 TBF-ESTABLISH-req To establish/create a TBF context 0x91 TBF-ESTABLISH-cnf 0x94 TBF-MODIFY-req To modify the TBF context



2006-2-22 3BK 09556 JAAA PBZZA 157/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

0x95 TBF-REALLOC-req 0x96 TBF-REALLOC-cnf 0x98 TBF-RELEASE-req To release the TBF context 0x99 TBF-RELEASE-cnf 0x9A TBF-RELEASE-ind 0x9C TBF-START-ind To indicate the reception of the first RLC data block 0xA0 TBF-UL-CONTROL-ind To receive MS signalling received in the Packet DL Ack/Nack 0xA4 TBF-UL-UNITDATA-ind To receive UL LLC PDU 0xA8 TBF-DL-LLC-ACK-ind To acknowledge DL LLC PDU

0xA9 ... 0xAF Unused Class PDCH (carried by class TRX)

0xB0 PDCH-BLOCK-RESERVE-req To reserve a block on a given PDCH 0xB1 PDCH-BLOCK-RESERVE-cnf 0xB4 PDCH-DL-CONTROL-req To send signalling to the MS 0xB5 PDCH-DL-CONTROL-CNF 0xB8 PDCH-CONFIG-req To activate a PDCH 0xB9 PDCH-CONFIG-cnf 0xBC Unused 0xBD Unused 0xBE PDCH-RELEASE-ind 0xC2 PDCH-UL-CONTROL-ind To receive signalling issued from the MS 0xC4 PDCH-UL-REJECT-req To reject the MS call/access on PCCCH

0xC5�CF Unused Class GCH (carried by class TRX)

0xD0 GCH-ESTABLISH-req 0xD1 GCH-ESTABLISH-cnf 0xD4 GCH-RELEASE-req 0xD5 GCH-RELEASE-cnf 0xD6 GCH-RELEASE-ind

0xD7�DF Unused Class L2GCH (0x06)

0xE0�FB Unused 0xFC L2GCH-DATA-req To receive an DL PDU to L2GCH 0xFE L2GCH-DATA-ind To receive an UL PDU from L2GCH 0xFF Unused

4.13 Reference The Reference defines a table index inside DSP.

4.13.1 Class 1 : DSP Reference = NIL = 0xFFFF

4.13.2 Class 2 : TRX Reference = TRX_INDEX (Range = 0.. MAX_NB_TRX - 1)

4.13.3 Class 3 : TBF Reference = TBF_INDEX (Range = 0..MAX_NB_TBF - 1)



2006-2-22 3BK 09556 JAAA PBZZA 158/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

4.14 Packet Request Reference

Parameters Presence Length

(in bits) Semantic Version Range

RAI_VALUE M 11 RANDOM_ACCESS_INFORMATION value

FN M 16 FRAME_NUMBER

Byte 7 6 5 4 3 2 1 0

0 0 0 0 0 0 RAI_VALUE (MSB)

1 RAI_VALUE (LSB)

2 FN (MSB)

3 FN (LSB)

4.15 PDU_TYPE

PDU_TYPE is coded as a byte-size representation of RLC/MAC messages type.

It is coded as follows: • Bits 8 and 7 are set to 00.

• The remainder (bits 6 to 1) is the corresponding RLC/MAC messages typeSee the [ 6 ](TSG GERAN#1) for the coding of RLC/MAC messages types.

4.16 POLL • 00H = No Uplink block needed

• 01h = One normal uplink block needed

• 02h = One access burst uplink block needed

4.17 (P)SI PDU

Byte Parameters Lengt

h (in bytes

)

Semantic Range

0 content 22 22 length 1 The length of the usefull data in byte 0..22 23 PD 1 Origin of a (P)SI



2006-2-22 3BK 09556 JAAA PBZZA 159/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

PD is usefull in case of TBF-PNCD-req because the instances maybe have different value of PD. But it is not useful in B9. It is introduced just for future safe.



2006-2-22 3BK 09556 JAAA PBZZA 160/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5 TIMING CONSTRAINT

5.1 Constraint defined in the RRM sublayer specification

The RRM sublayer specification E1P2 specifies in §.5.1 �Inter-entities communication� a delay response for the Packet channel request from a MS.

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

This delay constraint is linked to the attempts by MS to send the Packet Channel Request on PRACH. In nominal case, the MS must receive a Packet Uplink assignment or Packet Access Reject before attempting the send again the Packet Channel Request on PRACH. The delay between two attempts (value < 1s) is computed by the MS according the parameter values received in the System Information. Nevertheless, the delay between two attempts may be increased by modifying the parameter values (case of not wired Abis).

It is supposed that the delay constraint defined in the RRM specification for the GPU level takes into account the delay of the transmission on the air interface and the one inside the BSS.

Exchange sequence for concerned scenario

The above diagrams represent the different exchanges performed for the treatment of the Packet Uplink channel request from the MS in nominal case and in reject case. On these figures, INT includes several processes :

• the interface process at PPC level,

• the interface process at DSP level,

• the PCI bus.



2006-2-22 3BK 09556 JAAA PBZZA 161/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.1.1 Nominal case

This scenario corresponds to a successful resource allocation and a successful TBF establishment.

RRM INT RLC_TBF MAC_PDCH L2GCH

L2GCH-ACCESS-BURST-IND

PDCH-UL-CONTROL-IND

Packet channel request block

PDCH-UL-CONTROL-IND


TBF-ESTABLISH-REQ

TBF-ESTABLISH-REQ

TLLI-req

FOR each PDCH

PDCH-ASSIGN-REQ

PDCH-ASSIGN-CNF

EndFOR

TBF-ESTABLISH-CNF (OK)

TBF-ESTABLISH-CNF (OK)

PDCH-DL-CONTROL-REQ

PDCH-DL-CONTROL-REQ

Packet UL assignment, polling, RRM-ref

L2GCH-READY-IND

L2GCH-UNITDATA-REQ



2006-2-22 3BK 09556 JAAA PBZZA 162/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.1.2 Reject case

This scenario corresponds to an unsuccessful TBF establishment.

RRM INT RLC_TBF MAC_PDCH L2GCH

L2GCH-ACCESS-BURST-IND

PDCH-UL-CONTROL-IND


PDCH-UL-CONTROL-IND


TBF-ESTABLISH-REQ

TBF-ESTABLISH-REQ

TLLI-req

FOR each PDCH

PDCH-ASSIGN-REQ

PDCH-ASSIGN-CNF

EndFOR

TBF-ESTABLISH-CNF (NOK)

TBF-ESTABLISH-CNF (NOK)

PDCH-UL-REJECT-REQ

PDCH-UL-REJECT-REQ

Access Reject block

L2GCH-READY-IND

L2GCH-UNITDATA-REQ



2006-2-22 3BK 09556 JAAA PBZZA 163/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.2 Distribution of the timing constraint

The following diagram represents the process treatments (in DSP, between PPC/DSP and in PPC) and the delays to be precise.

T1

L2GCH

T2

RRMPPC/INT

PPC/INT

PPC/INT

PPC/INT

BUS

BUS

BUS

BUS

RLC

RLC

DSP/INT

DSP/INT

DSP/INT

MAC

MAC x n

DSP/INT

RRM

T3

T4

T5

L2GCH L1GCH DSP/INT

MAC L1GCH DSP/INT

5.2.1 Definition of delays

T1 : Delay between the receipt by DSP of the first bit of the Packet Channel Request message from the serial link and the trigger by the DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-UL-CONTROL-IND message).

T2 : Delay between the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-UL-CONTROL-IND message) and the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-REQ message).

T3 : Delay between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-REQ message) and the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-CNF message).

T4 : Delay between the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-CNF message) and the trigger by PPC to DSP of the signal indicating that messages are available in the circular buffer (storing the PDCH-DL-CONTROL-REQ or the PDCH-UL-REJECT-REQ message) .



2006-2-22 3BK 09556 JAAA PBZZA 164/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

T5 : Delay between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-DL-CONTROL-REQ or the PDCH-UL-REJECT-REQ message) and the sending by DSP of last bit of the Packet Uplink Assignment or the Packet Access Reject message onto the serial link.

T1 + T2 + T3 + T4 + T5 ≤ 500 ms

As hypothesis, T4 = T2 = T

Then, T ≤ (500ms - (T1 + T3 + T5)) /2

Each delay may be composed of the followings elementary delays : • L2GCH process delay, MAC process delay, RLC process delay:

Each process delay corresponds to the receipt of the input message, its treatment and the sending of the output message. This delay is estimated to as negligible when no additional delay is triggered.

The processing of elementary function in DSP may be considered as negligible. Nevertheless in case of full load, a processing may be delayed due to other processings (basically on 20 ms basis), due to elementary GCH frame length of 20ms.

• DSP_INT process delay in uplink or in downlink

The max DSP_INT process delay corresponds to an interface buffer fulled with LLC PDUs and the control message(to be transferred) introduced at the end of the buffer. In this worst case, the previous messages must be extracted from the buffer before transferring the considered control message.

This worst delay is estimated for uplink :

Delay for treating all messages in the queue of the interface (worst case including the delay for reassembling the LLC PDUs in the circular buffer) ≅ 30 ms

Note : The delay spent for the message transfer performed by PPC via PCI bus from the circular buffer is not considered as part of delay related to the DSP interface. When the messages are stored in the circular buffer, to DSP sends a signal to the PPC. The delay ends with the signal triggered at the output of the DSP when the messages are stored in the circular buffer.

As for the Down link, it is estimated to :

Waiting delay between the introduction of the message in the circular buffer and its taking into account (linked to the treatment of all other messages in the worst case) ≅ 10 ms

Note : The delay spent for the message transfer performed by PPC via PCI bus into the circular buffer is not considered as part of delay related to the DSP interface. When the messages are stored in the circular buffer, the PPC sends a signal to the DSP. The delay starts with the signal triggered at the input of the DSP when the messages are stored in the circular buffer.

• Bus transfer delay



2006-2-22 3BK 09556 JAAA PBZZA 165/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

This delay corresponds to the transfer of the message on the PCI bus. This delay may be considered as negligible because :

• The throughput of the PCI bus is 33 Mbytes/s.

• The size of the exchanged messages on the bus is :

PDCH-UL-CONTROL-IND 40 bytes

TBF-ESTABLISH-REQ 52 bytes

TBF-ESTABLISH-CNF 16 bytes

PDCH-DL-CONTROL-REQ 40 bytes

148 bytes

The global delay related to the different transfers on the PCI bus is equal to 148x10-6/33 ≅ 5µs.

5.2.2 Determination of T1, T3 and T5 delays

5.2.2.1 T1 delay

This delay is defined between the receipt by DSP of the first bit of the Packet Channel Request message from the serial link and the trigger by the DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-UL-CONTROL-IND message).

T1_max includes : • Delay of frame transmission = 20ms (delay for recovering the frame),

• L2GCH/L1GCH process delay ≅ 20 ms

• MAC process delay ≅ negligible

• DSP_INT process delay for uplink ≅ 30 ms

Thus T1_max ≅ 70ms.

5.2.2.2 T3 delay

This delay is defined between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-REQ message) and the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-CNF message).

T3_max includes : • DSP_INT process delay for downlink ≅ 10 ms

• 9 times the RLC process delay ≅ negligible

• 8 times the MAC process delay ≅ negligible

• DSP_INT process delay for uplink ≅ 30 ms

Thus T3_max ≅ 40ms.



2006-2-22 3BK 09556 JAAA PBZZA 166/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.2.2.3 T5 delay

This delay is defined between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-DL-CONTROL-REQ or the PDCH-UL-REJECT-REQ message) and the sending by DSP of last bit of the Packet Uplink Assignment or the Packet Access Reject message onto the serial link

The timing evaluation is based on the hypothesis that : • the concatenation of the Access Reject blocks in order to form the Packet Access Reject PDU is performed on PAGCH occurrence and that no timer delimits the block concatenation.

• there is no congestion on the PAGCH message queue.

The higher delay spent is related to the sending of the frame, because it is transmitted only on an PAGCH occurrence. This occurrence of the PAGCH in the multiframe depends on parameter values retrieved from the CELL-SYS-DEFINE-req message supplied by RRM. With BS_PAG_BLKS_RES = 1, the max delay value for PAGCH occurrence is 240 ms.

If there is some congestion, several PAGCH occurrences may be needed for the sending of the Packet Uplink Assignment and Packet Access Reject messages. Thus, with BS_PAG_BLK_RES = 1, the waiting delay may be up to 240 * n ms, where n is the number of waiting Assignment messages in the AGCH queue. Thus, this shows a STRONG variation of the value of �PAGCH occurrence delay�. If there is some PAGCH congestion, it is clear that T5 > 500 ms and furthermore T1+T2+T3+T4+T5 > 500 ms. Thus, congestion/no congestion on PAGCH is clearly the major point regarding the 500 ms delay requirement between the Packet Channel request and the Packet Uplink Assignment messages.

It is why BS_PAG_BLK_RES = 2 is recommended and is defined as default value, otherwise, with a lower value, the respect of the timing constraint may be uncertain.

Nevertheless, even if the retained default value for BS_PAG_BLK_RES is 2, the delay value for PAGCH occurrence is kept to 240 ms, because the probability to have an other Packet UL assignment message in the queue is not negligible.

T5_max includes : • DSP_INT process delay for downlink ≅ 10 ms

• MAC process delay ≅ negligible

• Delay between two L2GCH-READY-IND = 20ms,

• L2GCH process delay ≅ negligible

• L1 buffering = 20 ms (corresponding to one frame)

• PAGCH occurrence delay = 240 ms

• frame transmission delay = 20 ms

Thus T5_max ≅ 310 ms.

If the delay of PAGCH occurrence < 240 ms is not respected, the receipt by the MS of a Packet UL assignment or of a Packet Access Reject, will be done outside the timing constraint.



2006-2-22 3BK 09556 JAAA PBZZA 167/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.2.3 Determination of T2 and T4 delays

T2 = T4 ≤ (500ms - (T1 + T3 + T5)) /2 = 80 ms /2 ≅ 40 ms

T2 + T4 ≅ 80 ms.



2006-2-22 3BK 09556 JAAA PBZZA 168/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.3 Constraint summary

Delay Description Value DSP processing

PPC processing

T1 : Delay between the receipt by DSP of the first bit of the GCH frame including the Packet Channel Request message from the serial link and the trigger by the DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-UL-CONTROL-IND message).

70ms 50 ms

T2 : Delay between the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-UL-CONTROL-IND message) and the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-REQ message).

40 ms 40 ms

T3 : Delay between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-REQ message) and the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-CNF message).

40 ms 40 ms

T4 : Delay between the trigger by DSP to PPC of the signal indicating that messages are available in the circular buffer (storing the TBF-ESTABLISH-CNF message) and the trigger by PPC to DSP of the signal indicating that messages are available in the circular buffer (storing the PDCH-DL-CONTROL-REQ or the PDCH-UL-REJECT-REQ message) .

40 ms 40ms

T5 : Delay between the receipt by DSP from PPC of the signal indicating that messages are available in the circular buffer (storing the PDCH-DL-CONTROL-REQ or the PDCH-UL-REJECT-REQ message) and the sending by DSP of last bit of the GCH frame including the Packet Uplink Assignment or the Packet Access Reject message onto the serial link.

310 ms 50 ms



2006-2-22 3BK 09556 JAAA PBZZA 169/169

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Evo

lium

.

5.4 Conclusion • There is no reason to take special care to speed processes involved in this scenario within DSP or PPC SW or to handle specific PPC/DSP interface protocol (no need to fix particular priority for the flow of Packet UL assignment and Packet Access Reject).

• Congestion/no congestion on PAGCH is clearly the major point regarding the 500 ms delay requirement between the Packet Channel request and the Packet Uplink Assignment messages.

• The 40 ms objective for T2, T3 and T4 seems to be reasonable according to rough hypothesis. These delay values can not be increase greatly, because :

even in normal running, it is not possible to discard the fact that another Packet UL assignment or Packet Access Reject is waiting in the queue for transmission.

one PRACH may convey until 4 channel requests from different mobiles,

Channel requests may be simultaneously performed on several cells. • The worst case delay within the DSP could be 420 ms but only 140 ms are due to DSP processing delay, as 280 ms are due to multiframe and transmission delay.

• As indicated as the beginning, for specific configuration with big transmission delay (e.g; satellite), the appropriate sizing of parameters transmitted to MS should be done (out of the scope of the 500 ms timing constraint which is only defined at MFS level).

END OF DOCUMENT

Documents

MFS PMU-PTU Interface Specification B9 ed05.pdf