bss telecom parameter b 10

7/28/2019 Bss Telecom Parameter b 10

1/34

ED 11 Released BSS TELECOM PARAMETERS release B10

EVOLIUM0134_11.doc22-Nov-07 3BK 11203 0134 DSZZA 1/34

Site

VELIZYEVOLIUM SAS

Originators

M. TITIN-SCHNAIDER

R. MAUGER

BSS TELECOM PARAMETERSRELEASE B10

System : ALCATEL GSM/BSS

Sub-system : SYS-TLA

Document Category : PRODUCT DEFINITION

ABSTRACT

This document lists and defines all parameters and timers that are specified by BSS telecomspecification documents.

Approvals

NameApp.

M. TITIN-SCHNAIDERSYT DPM

S. BARRESYT CCM

G. TUDOROMC-R DPM

NameApp.

QIAN EnyuanBSC DPM

R. SABELLEKBTS DPM

L. KEUERMFS DPM


2/34



REVIEW

Ed.05 Proposal 01 2006/12/18 Wireless/GSM-WiMAX/R&D/SYT/rma/0272.2006.

HISTORY

Ed. 01 Proposal 01 31/11/2005 First B10 proposal based on B9 BTP (3BK 11203 0103DSZZA, Ed.10).

The main changes with related B9 BTP/Ed.10 are linked tothe alignment with B9 BTP Ed11:

Introduction of the following Change Requests :

- 173136 (MR1): T_CONFIG_TBF,T_MAX_EXTENDED_UL

- 170161_2 (MR2) : MAX_VGCS_TS, MAX_PDCH- 169381 (MR4): PS_PREF_BCCH_TRX

- 166070_2 (MR2) : Treq_pending, Testab

-T_PSI_PACCH :30sec is coded 11110

- Missing migration rule added for :THR_CELL_LOAD_3G_REJECT,T_REPETITION_CHANNEL_RELEASE, T14

- Removal of parameters with two lines in the coding table :Treq_pending, RNC_ID(n), T_DTM_ASSIGN.

- T_UL_ASSIGN_CCCH : AG_PREMPT_TCH is replacedwith AG_PREMPT_PCH in the mandatory

- THR_MARGIN_PRIO_PS : definition clarified

The following B10 features are taken into account:

1. DTM (pseudo CR 205351 v2)

2. GboverIP

3. Mx capacity improvements

4. MCS reduction on the flight (Weighted Round Robin)

Ed. 01 Proposal 02 28/12/2005 - Takes into account all remarks received: see the report :ref MRD/TD/SYT/206003

- EDA feature is added

-Gb over IP: names modified following meeting held

with MFS and OMC.

- B9 CR 173982v2 (CIR, NIR, CBS and EBS mandatoryrule)

- B9 CR 174571v1 (EN_IM_ASS_REJ changeable at theOMC level)


3/34



Ed. 01 Proposal 03 26/01/2006 Takes into account all remarks received: see the report refMRD/TD/SYT/206032

- B9 CR 176884v2 (BTP : to increase the size ofthe MX MFS queue A and B at BSCGP level)

- B9 CR 177321 (BTP: no more than 12 TRX PS

capable per cell)

- Updates following the SFD EDA Ed1 prop4

- All B9 indications related to MRx are removed

- Memo on PCS requirements 205402v2 is takeninto account

Ed. 01 Proposal 04 28/02/2006 - Takes into account all remarks received: see the report refMRD/TD/SYT/206079

- B10 CR 179066 (EN_RESEGMENTATION_UL and EN_IR_UL

recommendation)

- alignement with SFD Mx capacity improvement Ed2 Prop2

- The 3GPP Rel6 44.060 CR 450 (Tdoc GP 032797) is taken into account

(TOM8_PRIORITY is created, for predefined TOM8 PFI introduction)

- Removal of B9 CR 177321 (this limitation to 12 TRX per cell does not

apply to B10)

- The following B9 CRs (introduced in Ed12 of the B9 BTP) are taken into

account:

-175475

: RR_ACK_TIMER, M_PEND_A

- 175601 : RR_ACK_TIMER, M_PEND_A

- 176146 : FDD_ARFCN(n), FDD_ARFCN_LIST

- 177927 : MAX_PFC_NUMBER (GP and GPU)

- Some impacts of memo PCS requirements was missed in BTP Ed1 Prop

3:

- EN_AMR_CA is removed and replaced by two new

parameters EN_AMR_CA_HR_FR and EN_AMR_CA_FR_HR

- instance changed to cell for: EN_FULL_IR_DL, EN_IR_UL,

EN_RESEGMENTATION_UL

- B9 CR 178916 (BTP : clarification on AG_PREMPT_PCHaccording to BS_AG_BLKS_RES) is taken into account

- B9 CR 177840 v1 (BTP: T_WAIT_FLUSH is too short whenMS changed cell with LA+RA update) is taken into account

Ed. 01 Proposal 05 06/03/2006 - Takes into account remarks received: see the report refMRD/TD/SYT/206082


4/34


5/34



Ed.04 Proposal 1 2006/10/23 Takes into account following approved CRs :CR20/176871CR20/185626CR20/185628 v2CR20/191039 (done in Ed.03, but was missing in history)CR20/191573 (done in Ed.03, but was missing in history)CR20/193580

CR20/193584CR20/194615CR20/194819 v2CR20/194824CR20/195611CR20/191739 v7CR20/194779 v2CR20/194874 v1CR20/196116 v2CR20/197726Alignment with NPO/RNP interface Ed2P1 (POLO namesand CAE files)Only following information is maintained in the display

O&M detailed: POLO name, CDE table, CAE templatefile.Ed.04 Released 2006/11/15 Takes into account following approved CRs :

CR20/192388 v3CR20/194405 v2Updated according to review reportMRD/TD/SYT/rma/0253.2006 Ed.02.

Ed.05 Proposal 01 2006/12/07 Takes into account following approved CRs :CR20/191490CR20/192386 v5CR20/192387CR20/192389 v2CR20/196984 v2

CR20/197295CR20/198580CR20/198648CR20/198663CR20/199407CR20/199975

Changes related to RNO/RNP interface :TDD_ARFCN_LIST: POLO name and specific handlingaddedQ707_T1 : comma replaced by dot in default valueQ703_N1_HSL: was listed twice in BSS template,corrected

Q703_T5: added in BSS templateQ703_T7: added in BSS templateQSEARCH_C, QSEARCH_I, QSEARCH_P: coded defaultvalue is reported in SEL file, instead of default valueTHR_ECNO_HO: coded default value is reported in HPCfile, instead of default valueCHC: 16 TREs max

Ed.05 Released 2006/12/18 Updated according to review report Wireless/GSM-WiMAX/R&D/SYT/rma/0272.2006.BTP Ed.05 is aligned with NPO & RNP interface Ed.02Proposal 05.


6/34



Ed.06 Proposal 01 2007/02/14 Takes into account following approved CRs :CR20/198004 V2 (correction of IPGSL config parameters)

CR20/201316 V2 (creation of VLAN_ID for MFS)CR20/201391 (corrections for MFS IP addresses)CR20/201416 (limit max value ofT_MAX_FOR_TBF_SCHEDULING)CR20/201418 (Missing rule for unicity FDD_ARFCN(n)/

SCRAMBLING_CODE_3G(n))CR20/201420 (change of T_i values for MX BSC)CR20/201796 (T_SEND_MULTIPLE_PAGING_CMD,modif of range and value)CR20/201801 (Addition of two new parameters:MAX_TBF_TRX_DL and MAX_TBF_TRX_UL)CR20/201802 (EN_RESEGMENTATION_UL applicable toRLC ACK mode)CR20/204555 v2 (T200 at OMC-R (RFD 204522))

Alignment with NPO & RNP interface Ed.02 Proposal06:EN_COMPRESSED_INTER_RAT_INFO in file BSS.

Ed.06 Proposal 02 2007/04/06 Takes into account following approved CRs :CR20/201535 (modifications concerning IP priorities)CR20/201537 v4 (corrections on priorities mapping andnew L2 priority for GboIP)CR20/202431 (Update/addition/suppression of BTPparameters linked to IP)CR20/203809 v2 (Interoperability with GAN)CR20/205486 v2 (control on the 3G FDD frequency band(UARFCN are set by the operator)CR20/205487 v2 (GSL configuration via Ater satellite)

CR20/206119 (recommendations forGPRS_MULTISLOT_CLASS_DEF_VALUE)CR20/207392 (Clarification of the

MAX_DL/UL_TBF_SPDCH parameter definitions)CR20/207997 (new dimensioning values for GPUAB)

CR20/208306 v2 (FDD/TDD frequencies shall be unique)CR20/208328 (Impact of RFD 202100, dedicated radiolinktimer for AMR)CR20/208330 v2 (MTP-Sequence-Number-Formatapplicable also to LSL)CR20/200966 (un-appropriate default limits for TBFdistributions (volume and duration)

Correction of SFD reference.Alignment of tags in Internal Comment according to B10delta-DR1 decision:

For MR0/MR1 parameters: no specific information

For parameters new in MR2: B10 MR2 parameterindicated

For parameters needed only for IP transport in theBSS: IP demo parameter.

Ed.06 Released 2007/04/13 BTP Ed.06 is aligned with NPO & RNP interface Ed.02Proposal 07.


7/34



Ed.07 Released 2007/06/13 M. Titin-Schnaider:Takes into account the following CRs:- 198649: after BTS delivery,NB_MAX_MSG_MULTIPLE_PAGING_CMD = 5- 209771: Addition of a recommended rule forMAX_EGPRS_MCS parameter setting.- 214097: R_MIN new recommended rules- 212108: MR1 impacts of TFO for AMR-WB

- 210561: MTP_Sequence_Number_Format shall be changed toCAE- 209158: Difficulties in tuning handover to 3G (THR_ECNO_HO)- 213344: alignment with MFS for instances of GboIP parameters- 213565: correction of value for T200_TH- 215387: T_TFO- 215580: MFS GboIP corrections

In addition, the CR 194874 (not fully taken in the Ed4): iscompleted (mandatory rule for Max_Periodic_Realloc_Success_T3 iscorrected).

Ed.08 Released 2007/06/27 M. Titin-Schnaider:Complement to CR 210561:

MTP_Sequence_Number_Format is added into CAEtemplate file : BSS

Ed.09 Released 2007/08/20 M. Titin-Schnaider: minor corrections needed for MR1process:

- MTP_Sequence_Number_Format: POLO Nameis added

- EN_HSL: external comment is added(configurable on BSC terminal)

- The hpc file is indicated in CAE template forEN_IPE_PREF_CODEC_TYPE

Ed.10 Proposal 01 2007/09/20 M. Titin-Schnaider:- The hpc file is removed in CAE template forEN_IPE_PREF_CODEC_TYPE (it is a CST)- CR 177902 (uncompletely taken in the previous editions)

- CR 190213v5 (uncompletely taken in previous editions)- MAX_TRX_GPUAB = 448 (def/max/min)- MAX_CELLS_GPUAB=264 (def/max/min)

Updates for MR2:- Coding rules for IP addresses are clarified

-CR 206261 v2-CR 207616 v1-CR 211031 v4 (AMR-WB introduction)-CR 216657 v1-CR 220486 v1


8/34



Ed.10 Released 16/11/07 M. Titin-Schnaider: Last updates for MR2ed1:- 211031v4 was not taken for FORCE_TFO_VS_AMR inEd10p1- 218681 v1: P0_L3 mapping MFS: correction of the

internal comment

- 218682 v1: IPGB_SUBNET_MASK_MFS is MR2- 218685 v2: OAM_VLAN_ID is CST

- 222024 v1: Misunderstanding aboutEN_2G_3G_HO_NO_SERVICE_HO andTHR_CELL_LOAD_3G_REQ

- 222734 v1: ORANGE MR4 ACCEPTANCE:FDD_REPORTING_OFFSET not taken into account -RD00017

- 223060v1: WRR constants still in the BTP even ifhardcoded in MAC

- 223084v2: clarification about multislot class 30-33- 223682v1: Remove POLO&CAE template forFDD_REPORTING_OFFSET andFDD_REPORTING_THRESHOLD (FR A20/221081)- 223721v1: SGSN IP endpoint is unique per NSE

- 223914v3: MIN_PDCH and MAX_PDCH(_HIGH_LOAD)management inside BSC- 224224v2:mapping tables of layer 2 & 3 priority (GB overIP) as CST- 224507: impact of RFD219772 (PS detection of faulty

TRAGE)- 225556: Correction of the default value of

MIN_THROUGHPUT_GAIN.following FR 224646

Ed.11 Released 21/11/07 M. Titin-Schnaider:Correction of the following issue before DR4: CR 222734was not taken completely because the parametersFDD_REPORTING_THRESHOLD andFDD_REPORTING_OFFSET are still present in the customerdoc, whereas they shouldn't:=> in Ed11 Rlsd: they are indicated not in DLS (althoughthey are in DLS) in order to be removed from the GCDtable.


9/34



TABLE OF CONTENTS

INTERNAL REFERENCED DOCUMENTS......................................................................................... 101 INTRODUCTION.............................................................................................................................132 EXPLANATION OF THE TABLE ................................................................................................... 14

2.1 Name ........................................................................................................................... 142.2 DEFINITION ................................................................................................................ 142.3 HMI Name.................................................................................................................... 142.4 TYPE............................................................................................................................152.5 Rec ref......................................................................................................................... 152.6 Spec ref....................................................................................................................... 152.7 Application domain ................................................................................................... 162.8 MinIMUM VALUE........................................................................................................ 162.9 MaxIMUM VALUE....................................................................................................... 162.10 DefAULT VALUE........................................................................................................ 172.11 Unit .............................................................................................................................. 182.12 INSTance.....................................................................................................................192.13 CATEGORY ................................................................................................................ 202.14 OMC-R access............................................................................................................ 212.15 Authorised constellations of Categories and OMC-r accesses............................ 23

2.15.1 Sub-system: BSC.......................................................................................................... 232.15.2 Sub-System: MFS......................................................................................................... 242.15.3 Sub-System: OMC ........................................................................................................ 252.15.4 Sub-System: BTS.......................................................................................................... 252.15.5 Sub-System: TC............................................................................................................ 25

2.16 CODING RULES......................................................................................................... 262.17 Coded Min, Coded_default and Coded Max ........................................................... 262.18 Mandatory and recommended rules........................................................................ 262.19 Internal Comments.................................................................................................... 262.20 External comments.................................................................................................... 272.21 Sub-system.................................................................................................................282.22 Feature........................................................................................................................ 282.23 Nb TRX dependent..................................................................................................... 282.24 Cell Type dependent.................................................................................................. 282.25 CDE ASCII TABLE...................................................................................................... 292.26 CAE templates ........................................................................................................... 29

3 GLOSSARY.................................................................................................................................... 30


10/34



INTERNAL REFERENCED DOCUMENTS

Not applicable

REFERENCED DOCUMENTS

GSM References[1] 3GPP TS 03.41 Technical realisation of Short Message Service Cell Broadcast

(SMSCB)

[2] 3GPP TS 03.49 Example protocol stacks for interconnecting Cell Broadcast

Center (CBC) and Base Station Controller (BSC)

[3] 3GPP TS 44.006 MS-BSS interface data link layer specification

[4] 3GPP TS 44.008 Mobile radio interface - Layer 3 specification

[5] 3GPP TS 44.012 Short Message Service Cell Broadcast (SMSCB) support on the

mobile radio interface

[6] 3GPP TS 44.060 GPRS MS-BSS interface. RLC/MAC interface

[7] 3GPP TS 45.002 Multiplexing and multiple access on the radio path

[8] 3GPP TS 45.008 Radio Subsystem Link Control

[9] 3GPP TS 48.006 Signalling transport mechanism specification for the BSS-MSC

interface

[10] 3GPP TS 48.008 MSC-BSS interface - Layer 3 specification

[11] 3GPP TS 48.056 BSC-BTS interface - Layer 2 specification

[12] 3GPP TS 48.058 BSC-BTS Interface - Layer 3 specification

[13] 3GPP TS 48.060 Inband control of remote transcoders and rate adaptors for

Enhanced Full Rate (EFR) and full rate traffic channels

[14] 3GPP TS 48.061 In-band control of remote transcoders and rate adaptors for half

rate traffic channels

CCITT/ITU References

[15] CCITT Q.703 (Blue Book) SS7 - Signalling link

[16] CCITT Q.704 (Blue Book) SS7 - Signalling network functions and messages

[17] CCITT Q.707 (Blue Book) SS7 - Testing and maintenance

[18] CCITT Q.714 (Blue Book) SS7 - Signalling Connection Control Part procedures

[19] CCITT Q.921 (Blue Book) ISDN user-network interface - Link layer specification


11/34



Proprietary documents

[20] 3BK 11202 0353 DSZZA Handover preparation

[21] 3BK 11202 0340 DSZZA Paging and access grant control

[22] 3BK 11202 0341 DSZZA Radio and link establishment

[23] 3BK 11202 0343 DSZZA Normal Assignment

[24] 3BK 11202 0156 DSZZA Ciphering procedure

[25] 3BK 11202 0348 DSZZA Call release

[26] 3BK 11202 0287 DSZZA Channel modification

[27] 3BK 11202 0342 DSZZA Classmark handling

[28] 3BK 11202 0061 DSZZA Transparent message routing

[29] 3BK 11202 0062 DSZZA Short Message Service point-to-point

[30] 3BK 11202 0293 DSZZA Radio measurements

[31] 3BK 11202 0296 DSZZA DTX functional specification

[32] 3BK 11202 0294 DSZZA Radio measurements data processing

[33] 3BK 11202 0295 DSZZA Power control and radio link supervision

[34] 3BK 11202 0357 DSZZA Overload control

[35] 3BK 11202 0068 DSZZA Protocol error handling

[36] 3BK 11204 DSZZA FB Management of Trace Services

[37] 3BK 11202 0305 DSZZA BSS initialisation of the telecom part

[38] 3BK 11202 0071 DSZZA BSS Global reset

[39] 3BK 11202 0299 DSZZA Reset circuit and blocking and unequipped circuit

[40] 3BK 11202 0362 DSZZA Frequency encoding algorithm

[41] 3BK 11202 0329 DSZZA Short Message Service Cell Broadcast

[42] 3BK 11202 0306 DSZZA LAPDm functional specification

[43] 3BK 11202 0356 DSZZA System Information Management

[44] 3BK 11202 0300 DSZZA TC/BTS Interface

[45] 3BK 11202 0330 DSZZA Abis Signalling Link Multiplexing

[46] 3BK 11202 0089 DSZZA LapD Management

[47] 3BK 11202 0350 DSZZA Resource allocation and management

[48] 3BK 11202 0288 DSZZA Handover management[49] 3BK 11202 0347 DSZZA External channel changes

[50] 3BK 11202 0346 DSZZA Internal channel changes

[51] 3BK 11206 0313 DSZZA BSC Data Dictionary

[52] 3BK 11204 0035 DSZZA OMC-BSS MIB specification

[53] 3BK 11204 0034 DSZZA O&M coding rules

[54] 3BK 11202 0366 DSZZA FBS GPRS Radio interface - RRM Sublayer (PRH)

[55] 3BK 11202 0367 DSZZA FBS GPRS Radio interface - RRM Sublayer (PCC)

[56] 3BK 11202 0371 DSZZA FBS GPRS MFS-BSC interface - BSCGP Layer

[57] 3BK 11202 0261 DSZZA FBS GPRS MFS-BSC interface - GSL Stack


12/34



[58] 3BK 11202 258 DSZZA FBS GPRS Gb interface - Network Service Control Sublayer

[59] 3BK 11202 259 DSZZA FBS GPRS Gb interface - SubNetwork Service Sublayer

[60] 3BK 11202 0370 DSZZA FBS GPRS MFS-BTS interface - GCH stack

[61] 3BK 11202 0369 DSZZA FBS GPRS Radio interface - MAC Sublayer

[62] 3BK 11202 0368 DSZZA FBS GPRS Radio interface - RLC Sublayer

[63] 3BK 11202 0372 DSZZA FBS GPRS Gb interface - BSSGP Layer

[64] 3BK 11203 0055 DSZZA GPRS traffic model and performances

[65] 3BK 11202 0301 DSZZA TFO Functional Specification

[66] 3BK 11202 0373 DSZZA GPU Overload and CPU Power Budget Management

[67] 3BK 11206 0921 DSZZA NPO/RNP POLO LOGICAL PARAMETER FILE INTERFACE

RELATED DOCUMENTS

None

PREFACE

None.


13/34



1 INTRODUCTION

The aim of this document is to provide complete information for Telecom system parameters

implementation.

This document provides for each parameter: its accessibility, its instantiation, its allowed logical values

and its possible relationships with other parameters. The coding of the parameters is indicated wherever

it is relevant.

In the main part of the document, parameters have been grouped by sub-system (BSC, BTS, MFS and

transcoder), and are listed in alphabetical order.

Default values for parameters depending on the type of cell or on the number of TRX are given at the

end of the document, before the index.Coding rules reflect the coding of the parameters in the external interfaces (when applicable). Thiscoding shall be respected as far as possible in the internal interfaces.

However, if the coding of the internal interface is different from what is expressed in the coding rule(i.e. the external interface), the min., max. CODED values that are additionally indicated in the BSStelecom parameters catalogue will reflect the internal values.


14/34



2 EXPLANATION OF THE TABLE

This section gives a short explanation for each field describing the parameters.

The complete description of parameters is given in the file 0134_06.doca.pdf. The parameters are

sorted by sub-system, and then in alphabetical order.

2.1 Name

Definition:

Name of the parameter as used in the system specifications.

Constraints:

- Mandatory

- String with length < 100 characters

- Square brackets ([ and ]) are allowed only for describing the element of an array

- semi-colons (;) are not allowed.

- Hyphens (-) shall be avoided (use _ instead)

Some parameters are duplicated in BSC and MFS. In this case, the NE concerned is indicated

between brackets at the end of the name.

Note that from the OMC point of view, there is only one parameter, whose value is sent to BSC and

MFS.

2.2 DEFINITION

Definition:

Textual definition of the parameter.

Constraints:

- Mandatory

- String with no length constraint

2.3 HMI Name

Definition:

If the parameter is to be displayed at OMC-R, the name that shall appear on the OMC-R screenis given in the field HMI name.

Constraints:

- Optional


- Square brackets ([ and ]) and semi-colons (;) are not allowed.


15/34



2.4 TYPE

Definition:

Describes the type of the parameter.

Constraints:

- Mandatory

- Values are limited to the following list:

Code Meaning

(F) Flag

(T) Timer

(TH) Threshold

(N) Number

(R) Reference

(L) List of numbers

(A) Abstract parameter

An abstract parameter results from the

combination of several parameters

2.5 Rec ref

Definition:

This field indicates, if applicable, in which GSM recommendation or ITU-T recommendation the

parameter is specified.

Constraints:

- Optional


2.6 Spec ref

Definition:

This field indicates, if applicable, the doctree document in which the parameter is specified.

Constraints:

- Optional



16/34



2.7 Application domain

Definition:

This field indicates if the parameter is related to GPRS (GSM packet) or to GSM circuit.

Constraints:

- Mandatory


Table : Domains

Code Meaning

GSM Needed for GSM circuit

GPRS Needed for GSM packet (GPRS)

E-GPRS Needed for GPRS on EDGE

2G-3G Needed for 2G-3G Inter-working

LCS Needed for LCS

VGCS Needed for VGCS-eMLPP

IP Needed for IP transport in the BSS

DTM Needed for Dual Transfer Mode

2.8 MinIMUM VALUE

Definition:

Minimum value of the parameter.Constraints :

- Mandatory

- Numerical value: integer or floating point

- Same format is used for Minimum value, Maximum value and Default value fields.

2.9 MaxIMUM VALUE

Definition:

Maximum value of the parameter.Constraints:

- Mandatory

- Numerical value: integer or floating point



17/34



2.10 DefAULT VALUE

Definition:

Default value of the parameter.

If the value depends on the configuration, the default value shall be given for a normal GSM900cell, with terrestrial A-bis link. If this value is still not precise enough, the default value given in the

DLS or in the MIB shall be indicated here. The values to be applied, depending on theconfiguration shall be written in the field External comments.

When the default value is accompanied by a '*' character, this means that the parameter isalways populated with that default value and the operator is not allowed to modify the parameter,even if the parameter is declared as OMC-changeable.

Constraints:

- Mandatory

- Numerical value : integer or floating point



18/34



2.11 Unit

Definition:

Unit of the parameter.

Constraints:

- Mandatory.


Table : Units

Unit Meaning

None- No unit

byte byte

kbit kbit

kbit/s kbit/s

mn minute

s second

ms millisecond

% percent

dB dB

dBm dBm

SAmfr SACCH multiframe duration

it corresponds to about 471.1 ms on SDCCH

and to about 480.4 ms on TCH

2xSAmfr Two time SACCH multiframe duration

it corresponds to about 942.2 ms on SDCCH

and to about 960.8 ms on TCH

51mfr 51 frames multiframe duration

it corresponds to about 235.6 ms

bper bit period

it corresponds to 48/13 s,

and a distance of about 550m

CBper Cell Broadcast period duration

it corresponds to the duration of 8 x 51 framesmultiframe, namely about 1.88 s

kbyte kbyte

km km


19/34



2.12 INSTance

Definition:

Instance of the parameter.

Constraints:

- Mandatory


Table : Instances

Instance Meaning

cell there is one instance of the parameter for each cell

3G cell there is one instance of the parameter for each 3G cell

adj there is one instance of the parameter for eachdeclared adjacent cell

BTS there is one instance of the parameter for each BTS

BSS the parameter could have been defined on a per cellbasis, but, as its value shall be the same for all thecells in the BSS, there is only one instance of theparameter for the BSC

BSC there is one instance of the parameter for the BSC

MFS there is one instance of the parameter for the MFS

BC there is one instance of the parameter for each FrameRelay Bearer Channel in the MFS

BSCproc there is one instance of the parameter for eachprocessor in the BSC (i.e. each TCU, CPR and DTC)

TRAU there is one instance of the parameter for the TRAU

Trunk there is one instance of the parameter for each A trunk

TRX there is one instance of the parameter for each TRX

N7ch there is one instance of the parameter for each N7signalling link

ACH there is one instance of the parameter for each Ainterface circuit

OMC there is one instance of the parameter for the OMC-R(and possibly all the BSS managed by this OMC-R)

GPU there is one instance of the parameter for each GPU inMFS

BVC There is one instance of the parameter for each BVCin the MFS

DSP There is one instance of the parameyet for each DSPin the MFS

PDCH There is one instance of the parameter for each PDCHof the MFS

PDCH group There is one instance of the parameter for each PDCHgroup in the MFS

PVC There is one instance of the parameter for each PVCin the MFS

Abis link PCM link on Abis interface


20/34



Abis segment There is one instance of the parameter for eachsegment

Abis group There is one instance of the parameter for each Abisgroup.

IP-GSL

IP-SigLink

SGSN-IPEndPoint

Note that for all parameters per adjacency, the OMC does not verify the mandatory rules. For theseparameters, the OMC only verifies that the value corresponds to the one of the target cell.

An Abis group (or Abis BTS group, or Telecom Abis group) is defined as follows :

if IPoEthernet, it corresponds to the O&M Abis group (this corresponds to an integer numberof cells),

if IPoE1, with a 1-Abis BTS : set of BTSs connected on this E1 (! This does not correspond toan integer number of cells due to cell shared),

if IPoE1, with a 2-Abis BTS: the BTS connected on these two E1. (! This does not correspondto an integer number of cells due to cell shared). The bandwidth is the sum of the bandwidthprovided by each E1.

The telecom Abis group does not exist for BTS connected on an Abis TDM.

2.13 CATEGORY

Definition:

This field indicates if each instance of a parameter may take the same value throughout the

network, or if there is the necessity for different instances to take different values. It also shows

the nature of the changeability of the parameter by operator procedures.

Constraints:

- Mandatory


Config. Meaning

SITE (CAE) (Customer Application Engineering parameter).

Parameter which can be different from one instance

to another instance (e.g. cell to cell or from BSC to

BSC or from MFS to MFS)

Network (CDE) (Customer Design Engineering parameter).

Parameter which can be specific for a customer

and valid for the complete network.

System (CST) Constant data. Parameter that cannot or shall not

be modified by the operator (This parameter can be

hard coded or defined in a config file read at the NE

restart. It is not known by the operator)..


21/34



2.14 OMC-R access

Definition:

Indicates how the parameter is handled by the OMC-R.

Constraints:

- Mandatory


Config. Meaning

None (DLS) the parameter is present in the BSC or MFS

database, but not in the BSS-OMC interface

(MIB). As a consequence, its modification

requires a data base reload.

None (not in DLS) Hard coded parameters, can not be modified

Changeablethe parameter is present in the BSC or MFS

database and in the BSS-OMC interface (MIB). It

is modifiable from the OMC-R.OMC parameters that are marked aschangeable are local parameters at the OMC,changeable by the operator. Used to computeparameters sent to the BSC and/or MFS.

Displayed the parameter is present in the BSC or MFS

database and in the BSS-OMC interface (MIB) but

is only displayable at the OMC-R. As a

consequence, its modification requires a data

base reload.OMC parameters that are marked asdisplayed are local parameters at the OMC, onlydisplayed to the operator. Used to computeparameters sent to the BSC and/or MFS.

Virtual, Displayed the parameter is virtual, it is deduced by the

OMC-R from other parameters. It is displayed.

BSC/MFS parameters that are virtual

displayed are computed by the OMC from a local

displayed OMC parameter, and given to the

BSC/MFS.

Virtual, Changeable the parameter is virtual, it is deduced by the

OMC-R from other parameters. It is changeable.

BSC/MFS parameters that are virtualchangeable are computed by the OMC from alocal changeable OMC parameter, and given tothe BSC/MFS.

Set by create the parameter is present in the BSC or MFS

database and in the MIB. Its value is set during

the creation of the relative object and can not be

modified afterwards.

OMC local display the parameter is not in the DLS nor in the MIB. Its

default value is used locally by the OMC-R for

display purposes or to populate other parameters

Virtual (DLS) The parameter is present in a sub-system


22/34



Config. Meaning

database, is transmitted on the interface with the

OMC but not displayed by the OMC.


23/34



2.15 Authorised constellations of Categories and OMC-r accesses

Definition:

Among all possible constellations only the ones listed in the tables below are permitted. Theydepend on the sub-system (e.g. BSC, MFS). The tables below indicate also the consequences interms of migration and if the value of a parameter of such a kind can be modified / customised.

2.15.1 Sub-system: BSC

Category OMC-R access Changeable Migration comments

None (DLS) In DLS

None (not inDLS)

Parameter hardcoded

System(CST)

Displayed

NO NO

None (DLS)

Set by create

Network(CDE)

Displayed

Value can becustomised at

initialisation viathe CDE-table.

NO(Migration

only inextraordinarycases)

None(DLS) Yes (DLSmigration)

Parametersdepending onthe type ofconnected MSC

Displayed

Value notchangeable, butdefault valuemight becustomised viathe CDE-table if itis a newparameter.

Yes

Changeable Yes Yes

Virtualchangeable

Value might bechanged bychangingvalue(s) of theparameter(s) it isdepending on.

Yes

Site (CAE)

Virtual (DLS) No No


24/34



2.15.2 Sub-System: MFS

Category OMC-R access Changeable Migration comments

None (DLS) In MFS database

System(CST)

None (not in

DLS)

NO NO

Hard coded

None (DLS) Value might becustomised viaBUL files

by MFSNetwork(CDE)

Set by create Default value isset by OMC atcreation of thecorrespondinginstance.

NO

Set by create Default value isset by OMC atcreation of the

correspondinginstance.

Yes.

Displayed Depending onthe case

Dependingon the case

For example: aparameter that iscalculated by theMFS anddisplayed atOMC cannot becustomised andwill not bemigrated ofcourse.

Changeable Yes Yes. OMC

migratesradio data

(via re-

init+re-

synchro) that

are present

at OMC/

MFS itf.MFSmigratesater/ Gb/ HWdata (viadata

conversionscim) thatare presentat OMC/MFS itf.

Site (CAE)

Virtualchangeable

Value might bechanged bychangingvalue(s) of theparameter(s) it isdepending on

Yes


25/34



2.15.3 Sub-System: OMC

Category OMC-R access Changeable Migration Comments

Site (CAE) Changeable Yes Yes No migrationrules defined inthe BSS telecomparameters

2.15.4 Sub-System: BTS


System (CST) None (not inDLS)

No No Hard coded

Network (CDE) None (not inDLS)

No No Parameterconfigured viaFU.CPF file

Site (CAE) None (not inDLS)

No No Depending onthe case(FU.CPF file ordeduced fromanotherparameter)

2.15.5 Sub-System: TC


System (CST) None (not inDLS)

No No Hard coded


26/34



2.16 CODING RULES

Definition:

indicates, as far as system is concerned, how the parameter value is coded.

If this column is empty, it implicitly means that the step size between two consecutive values is 1.Coding rules reflect the coding of the parameters in the external interfaces (when applicable).

This coding shall be respected as far as possible in the internal interfaces.

Constraints:

- Optional

- String with no length constraints

2.17 Coded Min, Coded_default and Coded Max

Definition:

Coded Min indicates coded value of minimum value of parameter (see 2.8). Coded_defaultindicates coded value of default value of parameter (see 2.10). Coded Max indicates codedvalue of maximum value of parameter (see 2.9).

Remark: the coded values (Coded Min, Coded_default and Coded Max) describe how theparameter is coded inside the software. The coded value may be different than its correspondingreal value: for example, the (real) minimum value of MAX_GPRS_CS is 2 (means CS-2) and itsCoded Min is 1 (coded in two bits: 01).

Constraints:

- Mandatory

- Coded value shall conform to the coding rules (2.16).

2.18 Mandatory and recommended rules

Definition:

indicates possible relationship rules with other parameters and whether these rules are

recommended or mandatory

Remark: mandatory rules have to be checked by the relevant entities (OMC-R, DLS population

tools, etc.).

Recommended rules are purely informative and shall not be checked.

Constraints:

- Optional


2.19 Internal Comments

Definition:

This field contains any additional comments relevant for the parameter, for internal use.

Constraints:

- Optional


- Semi-colons (;) are not allowed.


27/34



2.20 External comments

Definition:

This field may contain further explanations about the parameter (use, configuration...).

If the default value of the parameter depends on the configuration, this shall be specified here(Default value given in the default value field is for implementation purposes only).

The parameter may depend on MSC type, operator...

Constraints:

- optional

- string with no length constraints

- semi-colons (;) are not allowed


28/34



2.21 Sub-system

Definition:

This field indicates which sub-system uses the parameter.

Constraints:

- Mandatory


BSC

BTS

MFS

TC

OMC

2.22 Feature

Definition:

This field indicates the feature the parameter is related to. It usually refers to the SFD that firstintroduced this parameter.

Constraints:

- Optional


2.23 Nb TRX dependent

Definition:

This field indicates if the default value depends on the number of TRX in the cell. If yes, thesedefault values shall be given in a specific table.

Constraints:

- Mandatory (default = no)

- Possible values: No, Yes

2.24 Cell Type dependent

Definition:

This field indicates if the default value depends on the cell type. If yes, these default values shallbe given in a specific table.

Constraints:

- Mandatory (default = no)

- Possible values: No, Yes


29/34



2.25 CDE ASCII TABLE

The flag CMA script within the O&M detailed information table ("O&Mdetailed") allows to indicate ifthe parameter shall be included in the CDE ASCII table.

The CDE ASCII table shall contain:

all BSC CDE parameters of a given release

all NEW BSC CAE parameters of a given release with the following two exceptions

1. Parameters such as cell or sub-system identifiers SHALL NOT be included in the list;2. Parameters enables / disables a new feature SHALL NOT be included in the list.

2.26 CAE templates

The table "CAE_Templates"' defines the contents of the following eight CAE template files: sel, pag,hpc, hoc, dir, rrm, bss and gpr. The contents of the CAE template "chc" is defined by the table called"CAE_template_CHC_info".

The information given in these tables are based on the specification: "RNO/RNP POLO LOGICAL

PARAMETER FILE INTERFACE".


30/34



3 GLOSSARY

AGCH Access Grant CHannel

ARFCN Absolute Radio Frequency Channel Number

BCCH Broadcast Control CHannel

BLKS BLocKS

BSC Base Station Controller

BSCGP BSC GPRS Protocol

BSS Base Station Subsystem (BSC+n*BTS)

BTS Base Transceiver Station

CCCH Common Control CHannel

CHAN. Channel

CND Configuration Data

CRC Cyclic Redundancy Check

CS Circuit Switched

DPC Destination Point Code

DTX Discontinuous Transmission

FACCH Fast Associated Control Channel

GPRS General Packet Radio Service

GSL GPRS Signalling Link

IE Information Element

LAPD Link Access Procedure on the D-channel

LCS LoCation ServicesLSB Less Significant Bit

MFS Multi-Function Server (GPRS)

MSB Most Significant Bit

MSC Mobile Switching Centre

MTP Message Transfer Part

NA Not Applicable

OIE Optional Information Element

OML Operations and Maintenance Link

OPC Originating Point Code

PCH Paging CHannel

PS Packet Switched

RACH Random Access CHannel

RRM Radio Resource Management (GPRS)

RSL Radio Signalling Link

RX Receiver

SACCH Slow Associated Control CHannel

SCCP Signalling Connection Control Part


31/34



SCH Synchronisation CHannel

SDCCH Stand alone Dedicated Control CHannel

SMSCB Short Message Service Cell Broadcast

SPI Signalling Point Inaccessible

SSF Sub Service Field

SPA Signalling Point Accessible

SSP/SSA SubSystem Prohibited/SubSystem Allowed

TCH Traffic Channel

TS Time slot


32/34


33/34



A.2 - RFMNGT TIMERS

T_A

It is started during the immediate assignment and SDCCH handover procedures after the

successful selection of an SDCCH channel by the SDCCH RM. It will be stopped when the

confirmation is received of the successful or unsuccessful activation of the selected SDCCH

channel. If the timer expires the selected SDCCH channel will be set to FREE in the SDCCHresource manager function and be available for selection once more when the next

CHANNEL_REQUIRED message is received over the random access channel.

Location : Broadcast TCU (RFMNGT_C_HANDLER)

T_B

It is started at the end of the immediate assignment procedure waiting for the confirm message

from the selected BSSAP. The confirm message will be sent by the selected BSSAP in parallel to

the sending of the SCCP_CONN_REQ message to the MSC. If the timer expires then the seized

radio channel will be released using the normal release procedure towards the MS and BTS and

locally within the BSC.

Location : TCU controlling the SDCCH channel seized by the MS in response to the earliertransmission of the immediate assignment message

T_C

It is started during the normal assignment procedure and the internal intra-cell handover

procedure (TCH or SDCCH) after the channel activation. It is stopped at the reception of the

EST_IND from the BTS or the reception of a clearing message (CLEAR_CMND, RELEASE_CH)

from the BSSAP. If the timer expires then the activated radio channel will be released towards

the BTS and locally within the BSC using the normal release procedure.

Location : TCU controlling the selected and activated TCH or SDCCH channel

T_IIt is started when either the ASS_CMND or the HND_CMND is sent to the MS. It is stopped

either at the reception of a clearing message from the BSSAP (CLEAR_CMND or

RELEASE_CH) or at the reception of the EST_IND from the BTS. If the timer expires then the old

radio channel will be released using the normal release procedure towards the MS and BTS and

locally within the BSC.

Location : TCU controlling the serving (old) TCH or SDCCH channel

T_C_INTER

It is used during the internal inter-cell handover and external handover procedures. It is started

after the activation of the channel waiting for EST_IND message from the BTS. This timer is

equivalent in function to timer T_C but is used as a protection timer when an inter-cell handoveris involved (internal or external) whilst timer T_C is used as a protection timer during normal

assignments and intra-cell handovers. If the timer expires then the activated radio channel will be

released towards the BTS and locally within the BSC using the normal release procedure.

Location : TCU controlling the selected and successfully activated target TCH or SDCCH

channel


34/34

A.3 - RULES INVOLVING INTERNAL TIMERS

T8 < T_I

T3103 < T_C_INTER

T3103 < T_I

T3107 < T_C

T3107 < T_I

T9103 + T9108 < T_A

T9103 + T9108 < T_CH_ACT

T9103 < T_MOD_REQ

T9105 < T_B

T9113 < T_C_INTER

T_BTS_EST_CNF < T_SMS_EST_CNF

T_C < T_I

T_CH_ACT > T11

END OF DOCUMENT

bss telecom parameter b 10

Documents