VELIZY M. TITIN-SCHNAIDER R.

MAUGER Originators

Site

EVOLIUM SAS BSS TELECOM PARAMETERS RELEASE B10

System Sub-system Document Category

: : :

ALCATEL GSM/BSS SYS-TLA PRODUCT DEFINITION

ABSTRACT

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

Name App. Name App.

M. TITIN-SCHNAIDER
SYT DPM

Approvals

S. BARRE
SYT CCM

G. TUDOR
OMC-R DPM

QIAN Enyuan
BSC DPM

R. SABELLEK
BTS DPM

L. KEUER
MFS DPM

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 1/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 0103 DSZZA, Ed.10). The main changes with related B9 BTP/Ed.10 are linked to the 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 replaced with AG_PREMPT_PCH in the mandatory - THR_MARGIN_PRIO_PS : definition clarified

The following B10 features are taken into account: 1. 2. 3. 4. Ed. 01 Proposal 02 28/12/2005

DTM (pseudo CR 205351 v2) GboverIP Mx capacity improvements MCS reduction on the flight (Weighted Round Robin)

- 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 mandatory rule) - B9 CR 174571v1 (EN_IM_ASS_REJ changeable at the OMC level)

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 2/34

Ed. 01 Proposal 03

26/01/2006

Takes into account all remarks received: see the report ref MRD/TD/SYT/206032 B9 CR 176884v2 (BTP : to increase the size of the 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 taken into account

Ed. 01 Proposal 04 28/02/2006

- Takes into account all remarks received: see the report ref MRD/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_PCH according to BS_AG_BLKS_RES) is taken into account B9 CR 177840 v1 (BTP: T_WAIT_FLUSH is too short when MS 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 ref MRD/TD/SYT/206082

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 3/34

Ed. 01 Proposal 06

06/03/14

Takes into account remarks received : see the report ref MRD/TD/SYT/206093 SFD Multiple CCCH is taken into account Takes into account remarks received : see the report ref MRD/TD/SYT/206098

Ed. 01 Released Ed. 02 Proposal 01 Ed.02 Proposal 02

06/03/20 06/04/14

2006/05/24

Ed. 02 Proposal 03

2006/06/09

Ed. 02 Proposal 04

2006/06/23

Ed.02 Released

2006/07/13

Ed. 03 Proposal 01 Ed.03 Released

2006/08/01 2006/09/15

Updated according to review report MRD/TD/SYT/rma/0140.2006 Takes into account following approved CRs : 20/183724 20/185627 20/185639 GCD queries have been updated to take into account migration information (B9 FR 20/182247) Updated according to review report MRD/TD/SYT/rma/0153.2006 Takes into account following approved CRs : 20/185624 20/185629 20/185640 20/185807 20/185985 Updated according to review report MRD/TD/SYT/rma/0172.2006 Takes into account following approved CRs : 20/185625 20/188329 Updated according to review report MRD/TD/SYT/rma/0180.2006 v3 Takes into account following approved CRs : CR20/188331 CR20/188301 CR20/190308 v4 CR20/189404 CR20/189840 CR20/189838 CR20/188113 v2 Takes into account CR 192040 for MR1 Takes into account following approved CRs : CR20/188135 CR20/188299 v3 (instead of CR20/192040) CR20/189889 v3 CR20/190213 v5 CR20/190664 v2 CR20/191037 CR20/191038 CR20/191109 CR20/190705 CR20/193534 CR20/193592 Updated according to review report MRD/TD/SYT/rma/0210.2006 Ed.02

IP parameters for MR2 are added, following the memo 206100 v2

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 4/34

Ed.04 Proposal 1

2006/10/23

Ed.04 Released

2006/11/15

Ed.05 Proposal 01

2006/12/07

Takes into account following approved CRs : CR20/176871 CR20/185626 CR20/185628 v2 CR20/191039 (done in Ed.03, but was missing in history) CR20/191573 (done in Ed.03, but was missing in history) CR20/193580 CR20/193584 CR20/194615 CR20/194819 v2 CR20/194824 CR20/195611 CR20/191739 v7 CR20/194779 v2 CR20/194874 v1 CR20/196116 v2 CR20/197726 Alignment with NPO/RNP interface Ed2P1 (POLO names and CAE files) Only following information is maintained in the display O&M detailed: POLO name, CDE table, CAE template file. Takes into account following approved CRs : CR20/192388 v3 CR20/194405 v2 Updated according to review report MRD/TD/SYT/rma/0253.2006 Ed.02. Takes into account following approved CRs : CR20/191490 CR20/192386 v5 CR20/192387 CR20/192389 v2 CR20/196984 v2 CR20/197295 CR20/198580 CR20/198648 CR20/198663 CR20/199407 CR20/199975 Changes related to RNO/RNP interface : TDD_ARFCN_LIST: POLO name and specific handling added Q707_T1 : comma replaced by dot in default value Q703_N1_HSL: was listed twice in BSS template, corrected Q703_T5: added in BSS template Q703_T7: added in BSS template QSEARCH_C, QSEARCH_I, QSEARCH_P: coded default value is reported in SEL file, instead of default value THR_ECNO_HO: coded default value is reported in HPC file, instead of default value CHC: 16 TREs max Updated according to review report Wireless/GSMWiMAX/R&D/SYT/rma/0272.2006. BTP Ed.05 is aligned with NPO & RNP interface Ed.02 Proposal 05.

Ed.05 Released

2006/12/18

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 5/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 of T_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 to RLC ACK mode) CR20/204555 v2 (T200 at OMC-R (RFD 204522)) Alignment with NPO & RNP interface Ed.02 Proposal 06: EN_COMPRESSED_INTER_RAT_INFO in file BSS. Takes into account following approved CRs : CR20/201535 (modifications concerning IP priorities) CR20/201537 v4 (corrections on priorities mapping and new L2 priority for GboIP) CR20/202431 (Update/addition/suppression of BTP parameters 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 for GPRS_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 radiolink timer for AMR) CR20/208330 v2 (MTP-Sequence-Number-Format applicable also to LSL) CR20/200966 (un-appropriate default limits for TBF distributions (volume and duration) Correction of SFD reference. Alignment of tags in Internal Comment according to B10 delta-DR1 decision: For MR0/MR1 parameters: no specific information For parameters new in MR2: B10 MR2 parameter indicated For parameters needed only for IP transport in the BSS: IP demo parameter. BTP Ed.06 is aligned with NPO & RNP interface Ed.02 Proposal 07.

Ed.06 Proposal 02

2007/04/06

Ed.06 Released

2007/04/13

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 6/34

Ed.07 Released

2007/06/13

M. Titin-Schnaider: Takes into account the following CRs:

Ed.08 Released

2007/06/27

Ed.09 Released

2007/08/20

Ed.10 Proposal 01

2007/09/20

In addition, the CR 194874 (not fully taken in the Ed4): is completed (mandatory rule for Max_Periodic_Realloc_Success_T3 is corrected). M. Titin-Schnaider: Complement to CR 210561: MTP_Sequence_Number_Format is added into CAE template file : BSS M. Titin-Schnaider: minor corrections needed for MR1 process: - MTP_Sequence_Number_Format: POLO Name is added - EN_HSL: external comment is added (configurable on BSC terminal) - The hpc file is indicated in CAE template for EN_IPE_PREF_CODEC_TYPE M. Titin-Schnaider: - The hpc file is removed in CAE template for EN_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

- 198649: after BTS delivery, NB_MAX_MSG_MULTIPLE_PAGING_CMD = 5 - 209771: Addition of a recommended rule for MAX_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 to CAE - 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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 7/34

Ed.10 Released

16/11/07

M. Titin-Schnaider: Last updates for MR2ed1: - 211031v4 was not taken for FORCE_TFO_VS_AMR in Ed10p1 - 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 about EN_2G_3G_HO_NO_SERVICE_HO and THR_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 if hardcoded in MAC - 223084v2: clarification about multislot class 30-33 - 223682v1: Remove POLO&CAE template for FDD_REPORTING_OFFSET and FDD_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 over IP) 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 222734 was not taken completely because the parameters FDD_REPORTING_THRESHOLD and FDD_REPORTING_OFFSET are still present in the customer doc, whereas they shouldn't: => in Ed11 Rlsd: they are indicated not in DLS (although they are in DLS) in order to be removed from the GCD table.

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 8/34

TABLE OF CONTENTS
INTERNAL REFERENCED DOCUMENTS ......................................................................................... 10 1 INTRODUCTION............................................................................................................................. 13 2 EXPLANATION OF THE TABLE ................................................................................................... 14 2.1 Name ........................................................................................................................... 14 2.2 DEFINITION ................................................................................................................ 14 2.3 HMI Name.................................................................................................................... 14 2.4 TYPE............................................................................................................................ 15 2.5 Rec ref......................................................................................................................... 15 2.6 Spec ref....................................................................................................................... 15 2.7 Application domain ................................................................................................... 16 2.8 MinIMUM VALUE........................................................................................................ 16 2.9 MaxIMUM VALUE ....................................................................................................... 16 2.10 DefAULT VALUE ........................................................................................................ 17 2.11 Unit .............................................................................................................................. 18 2.12 INSTance..................................................................................................................... 19 2.13 CATEGORY ................................................................................................................ 20 2.14 OMC-R access............................................................................................................ 21 2.15 Authorised constellations of Categories and OMC-r accesses............................ 23 2.15.1 Sub-system: BSC .......................................................................................................... 23 2.15.2 Sub-System: MFS ......................................................................................................... 24 2.15.3 Sub-System: OMC ........................................................................................................ 25 2.15.4 Sub-System: BTS.......................................................................................................... 25 2.15.5 Sub-System: TC ............................................................................................................ 25 2.16 CODING RULES ......................................................................................................... 26 2.17 Coded Min, Coded_default and Coded Max ........................................................... 26 2.18 Mandatory and recommended rules........................................................................ 26 2.19 Internal Comments .................................................................................................... 26 2.20 External comments.................................................................................................... 27 2.21 Sub-system................................................................................................................. 28 2.22 Feature ........................................................................................................................ 28 2.23 Nb TRX dependent..................................................................................................... 28 2.24 Cell Type dependent.................................................................................................. 28 2.25 CDE ASCII TABLE...................................................................................................... 29 2.26 CAE templates ........................................................................................................... 29 3 GLOSSARY .................................................................................................................................... 30

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 9/34

INTERNAL REFERENCED DOCUMENTS

Not applicable

REFERENCED DOCUMENTS
GSM References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] 3GPP TS 03.41 Technical realisation of Short Message Service Cell Broadcast (SMSCB)

3GPP TS 03.49 3GPP TS 44.006 3GPP TS 44.008 3GPP TS 44.012 3GPP TS 44.060 3GPP TS 45.002 3GPP TS 45.008 3GPP TS 48.006 3GPP TS 48.008 3GPP TS 48.056 3GPP TS 48.058 3GPP TS 48.060 3GPP TS 48.061

MS-BSS interface data link layer specification Mobile radio interface - Layer 3 specification

Example protocol stacks for interconnecting Cell Broadcast Center (CBC) and Base Station Controller (BSC)

Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface GPRS MS-BSS interface. RLC/MAC interface Radio Subsystem Link Control Multiplexing and multiple access on the radio path Signalling transport mechanism specification for the BSS-MSC interface

MSC-BSS interface - Layer 3 specification BSC-BTS interface - Layer 2 specification BSC-BTS Interface - Layer 3 specification

Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels

In-band control of remote transcoders and rate adaptors for half rate traffic channels

CCITT/ITU References [15] [17] [18] [19] [16] CCITT Q.703 (Blue Book) CCITT Q.707 (Blue Book) CCITT Q.714 (Blue Book) CCITT Q.921 (Blue Book) CCITT Q.704 (Blue Book) SS7 - Signalling link SS7 - Signalling network functions and messages

SS7 - Testing and maintenance

SS7 - Signalling Connection Control Part procedures

ISDN user-network interface - Link layer specification

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 10/34

Proprietary documents [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] [56] [57] ED EVOLIUM 3BK 11202 0353 DSZZA 3BK 11202 0340 DSZZA 3BK 11202 0341 DSZZA 3BK 11202 0343 DSZZA 3BK 11202 0156 DSZZA 3BK 11202 0348 DSZZA 3BK 11202 0287 DSZZA 3BK 11202 0342 DSZZA 3BK 11202 0061 DSZZA 3BK 11202 0062 DSZZA 3BK 11202 0293 DSZZA 3BK 11202 0296 DSZZA 3BK 11202 0294 DSZZA 3BK 11202 0295 DSZZA 3BK 11202 0357 DSZZA 3BK 11202 0068 DSZZA 3BK 11204 DSZZA 3BK 11202 0305 DSZZA 3BK 11202 0071 DSZZA 3BK 11202 0299 DSZZA 3BK 11202 0362 DSZZA 3BK 11202 0329 DSZZA 3BK 11202 0306 DSZZA 3BK 11202 0356 DSZZA 3BK 11202 0300 DSZZA 3BK 11202 0330 DSZZA 3BK 11202 0089 DSZZA 3BK 11202 0350 DSZZA 3BK 11202 0288 DSZZA 3BK 11202 0347 DSZZA 3BK 11202 0346 DSZZA 3BK 11206 0313 DSZZA 3BK 11204 0035 DSZZA 3BK 11204 0034 DSZZA 3BK 11202 0366 DSZZA 3BK 11202 0367 DSZZA 3BK 11202 0371 DSZZA 3BK 11202 0261 DSZZA 11 Released
0134_11.doc 22-Nov-07

Handover preparation

Radio and link establishment Normal Assignment Call release Ciphering procedure Channel modification Classmark handling

Paging and access grant control

Transparent message routing Radio measurements

Short Message Service point-to-point DTX functional specification

Radio measurements data processing Overload control

Power control and radio link supervision Protocol error handling

BSS initialisation of the telecom part BSS Global reset Reset circuit and blocking and unequipped circuit Frequency encoding algorithm Short Message Service Cell Broadcast LAPDm functional specification TC/BTS Interface System Information Management Abis Signalling Link Multiplexing LapD Management Resource allocation and management External channel changes Internal channel changes BSC Data Dictionary O&M coding rules Handover management

FB Management of Trace Services

OMC-BSS MIB specification FBS GPRS Radio interface - RRM Sublayer (PRH) FBS GPRS Radio interface - RRM Sublayer (PCC) FBS GPRS MFS-BSC interface - BSCGP Layer FBS GPRS MFS-BSC interface - GSL Stack

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 11/34

[58] [59] [60] [61] [62] [63] [64] [65] [66] [67]

3BK 11202 258 DSZZA 3BK 11202 259 DSZZA 3BK 11202 0370 DSZZA 3BK 11202 0369 DSZZA 3BK 11202 0368 DSZZA 3BK 11202 0372 DSZZA 3BK 11203 0055 DSZZA 3BK 11202 0301 DSZZA 3BK 11202 0373 DSZZA 3BK 11206 0921 DSZZA

FBS GPRS Gb interface - Network Service Control Sublayer FBS GPRS MFS-BTS interface - GCH stack FBS GPRS Radio interface - MAC Sublayer FBS GPRS Radio interface - RLC Sublayer FBS GPRS Gb interface - BSSGP Layer GPRS traffic model and performances TFO Functional Specification FBS GPRS Gb interface - SubNetwork Service Sublayer

NPO/RNP POLO LOGICAL PARAMETER FILE INTERFACE

GPU Overload and CPU Power Budget Management

RELATED DOCUMENTS
None

PREFACE
None.

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 12/34

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

INTRODUCTION

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). This coding 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 BSS telecom parameters catalogue will reflect the internal values.

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 13/34

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

EXPLANATION OF THE TABLE

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
Name of the parameter as used in the system specifications. - Mandatory

Definition:

Constraints:

- String with length < 100 characters - semi-colons (;) are not allowed.

- Square brackets ([ and ]) are allowed only for describing the element of an array - 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
Textual definition of the parameter. - Mandatory

Definition:

Constraints:

- String with no length constraint

2.3

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

Definition:

Constraints:

- String with length < 100 characters

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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 14/34

2.4

TYPE
Describes the type of the parameter. - Mandatory

Definition:

Constraints:

- Values are limited to the following list: Code (F) (T) Meaning Timer Flag

(TH) (N) (R) (A) (L)

Threshold Reference Number

Abstract parameter An abstract parameter results from the combination of several parameters

List of numbers

2.5

Rec ref
This field indicates, if applicable, in which GSM recommendation or ITU-T recommendation the parameter is specified. - Optional

Definition:

Constraints:

- String with length < 255 characters

2.6

Spec ref
This field indicates, if applicable, the doctree document in which the parameter is specified. - Optional

Definition:

Constraints:

- String with length < 255 characters

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 15/34

2.7

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

Definition:

Constraints:

- Values are limited to the following list: Table : Domains Code GPRS GSM Needed for GSM circuit Meaning

E-GPRS 2G-3G VGCS DTM IP LCS

Needed for GSM packet (GPRS) Needed for 2G-3G Inter-working Needed for VGCS-eMLPP Needed for LCS Needed for GPRS on EDGE

Needed for IP transport in the BSS Needed for Dual Transfer Mode

2.8

MinIMUM VALUE
Minimum value of the parameter. - Mandatory

Definition:

Constraints :

- Numerical value: integer or floating point

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

2.9

MaxIMUM VALUE
Maximum value of the parameter. - Mandatory

Definition:

Constraints:

- Numerical value: integer or floating point

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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 16/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 GSM900 cell, 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 the configuration shall be written in the field External comments. When the default value is accompanied by a '*' character, this means that the parameter is always 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

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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 17/34

2.11 Unit
Definition: Unit of the parameter. - Mandatory.

Constraints:

- Values are limited to the following list: Table : Units Nonebyte kbit mn ms dB % s Unit Meaning No unit byte kbit

kbit/s

millisecond percent dBm dB

second

minute

kbit/s

SAmfr

dBm

it corresponds to about 471.1 ms on SDCCH Two time SACCH multiframe duration and to about 960.8 ms on TCH 51 frames multiframe duration bit period and to about 480.4 ms on TCH

SACCH multiframe duration

2xSAmfr

it corresponds to about 942.2 ms on SDCCH

51mfr bper

it corresponds to about 235.6 ms it corresponds to 48/13 s,

CBper

kbyte km

it corresponds to the duration of 8 x 51 frames multiframe, namely about 1.88 s kbyte km

Cell Broadcast period duration

and a distance of about 550m

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 18/34

2.12 INSTance
Definition: Instance of the parameter. - Mandatory

Constraints:

- Values are limited to the following list: Table : Instances Instance 3G cell adj BTS cell there is one instance of the parameter for each cell Meaning

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

there is one instance of the parameter for each declared adjacent cell the parameter could have been defined on a per cell basis, but, as its value shall be the same for all the cells in the BSS, there is only one instance of the parameter for the BSC there is one instance of the parameter for the MFS there is one instance of the parameter for the BSC

BSS

MFS BC BSCproc TRAU Trunk N7ch ACH OMC GPU BVC DSP PDCH PDCH group PVC Abis link ED EVOLIUM 11 Released TRX

BSC

there is one instance of the parameter for each Frame Relay Bearer Channel in the MFS there is one instance of the parameter for each processor in the BSC (i.e. each TCU, CPR and DTC) there is one instance of the parameter for each A trunk there is one instance of the parameter for each N7 signalling link there is one instance of the parameter for each A interface circuit there is one instance of the parameter for the OMC-R (and possibly all the BSS managed by this OMC-R) there is one instance of the parameter for each TRX there is one instance of the parameter for the TRAU

There is one instance of the parameter for each BVC in the MFS There is one instance of the parameyet for each DSP in the MFS There is one instance of the parameter for each PDCH of the MFS

there is one instance of the parameter for each GPU in MFS

There is one instance of the parameter for each PDCH group in the MFS PCM link on Abis interface

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

BSS TELECOM PARAMETERS release B10

0134_11.doc 22-Nov-07

3BK 11203 0134 DSZZA

19/34

Abis segment Abis group IP-SigLink IP-GSL

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

There is one instance of the parameter for each segment

SGSNIPEndPoint Note that for all parameters per adjacency, the OMC does not verify the mandatory rules. For these parameters, 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 number of cells), if IPoE1, with a 1-Abis BTS : set of BTSs connected on this E1 (! This does not correspond to an integer number of cells due to cell shared),

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

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

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

Constraints:

- Values are limited to the following list: Config. Meaning

SITE (CAE)

Network (CDE) System (CST)

(Customer Design Engineering parameter). Parameter which can be specific for a customer and valid for the complete network.

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

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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 20/34

2.14 OMC-R access

Definition: Indicates how the parameter is handled by the OMC-R. - Mandatory

Constraints:

- Values are limited to the following list: Config. None (DLS) Meaning 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) Changeable

Hard coded parameters, can not be modified

the 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 as changeable are local parameters at the OMC, changeable by the operator. Used to compute parameters sent to the BSC and/or MFS.

Displayed

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.

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 as displayed are local parameters at the OMC, only displayed to the operator. Used to compute parameters sent to the BSC and/or 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 virtual changeable are computed by the OMC from a local changeable OMC parameter, and given to the BSC/MFS. 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.

Set by create

OMC local display Virtual (DLS) ED EVOLIUM 11 Released

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 The parameter is present in a sub-system BSS TELECOM PARAMETERS release B10
0134_11.doc 22-Nov-07

3BK 11203 0134 DSZZA

21/34

Config.

database, is transmitted on the interface with the OMC but not displayed by the OMC.

Meaning

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 22/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. They depend on the sub-system (e.g. BSC, MFS). The tables below indicate also the consequences in terms of migration and if the value of a parameter of such a kind can be modified / customised.

2.15.1 Sub-system: BSC Category System(CST) OMC-R access None (DLS) None DLS) (not in Changeable NO Migration NO comments In DLS Parameter hard coded

Network(CDE)

Displayed

None (DLS) Displayed

Set by create

Value can be customised at initialisation via the CDE-table. Value not changeable, but default value might be customised via the CDE-table if it is a new parameter. Value might be changed by changing value(s) of the parameter(s) it is depending on.

Site (CAE)

None(DLS)

Yes (DLS migration) Yes

NO (Migration only in extraordinary cases)

Displayed

Parameters depending on the type of connected MSC

Changeable Virtual changeable

Yes

Yes

Yes

Virtual (DLS)

No

No

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 23/34

2.15.2 Sub-System: MFS Category System(CST) OMC-R access None (DLS) None (not DLS) None (DLS) Set by create in Value might be customised via BUL files Default value is set by OMC at creation of the corresponding instance. Default value is set by OMC at creation of the corresponding instance. Depending on the case by MFS NO Changeable NO Migration NO comments In MFS data base Hard coded

Network(CDE)

Site (CAE)

Set by create

Yes.

Displayed

Depending on the case

Changeable

Yes

Yes. OMC migrates radio data (via reinit+resynchro) that are present at OMC/ MFS itf. MFS migrates ater/ Gb/ HW data (via data conversion scim) that are present at OMC/ MFS itf. Yes

For example: a parameter that is calculated by the MFS and displayed at OMC cannot be customised and will not be migrated of course.

Virtual changeable

Value might be changed by changing value(s) of the parameter(s) it is depending on

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 24/34

2.15.3 Sub-System: OMC Category Site (CAE) OMC-R access Changeable Changeable Yes Migration Yes Comments No migration rules defined in the BSS telecom parameters

2.15.4 Sub-System: BTS Category System (CST) Network (CDE) Site (CAE) OMC-R access None DLS) (not (not (not in in in Changeable No No No Migration No No No Comments Hard coded Parameter configured FU.CPF file via

None DLS)

None DLS)

Depending on the case (FU.CPF file or deduced from another parameter)

2.15.5 Sub-System: TC

Category System (CST)

OMC-R access None DLS) (not in

Changeable No

Migration No

Comments Hard coded

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 25/34

2.16 CODING RULES

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

Constraints:

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. - 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_default indicates coded value of default value of parameter (see 2.10). Coded Max indicates coded value of maximum value of parameter (see 2.9).

Constraints:

Remark: the coded values (Coded Min, Coded_default and Coded Max) describe how the parameter is coded inside the software. The coded value may be different than its corresponding real value: for example, the (real) minimum value of MAX_GPRS_CS is 2 (means CS-2) and its Coded Min is 1 (coded in two bits: 01). - 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.). Constraints: Recommended rules are purely informative and shall not be checked.

- Optional

- String with length < 255 characters

2.19 Internal Comments

Definition: This field contains any additional comments relevant for the parameter, for internal use. - Optional

Constraints:

- String with no length constraints ED EVOLIUM 11 Released

- Semi-colons (;) are not allowed. BSS TELECOM PARAMETERS release B10
0134_11.doc 22-Nov-07

3BK 11203 0134 DSZZA

26/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... - optional

Constraints:

- string with no length constraints

- semi-colons (;) are not allowed

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 27/34

2.21 Sub-system
Definition: This field indicates which sub-system uses the parameter. - Mandatory BSC BTS TC

Constraints:

- Values are limited to the following list:

MFS OMC

2.22 Feature
Definition: This field indicates the feature the parameter is related to. It usually refers to the SFD that first introduced this parameter. - Optional

Constraints:

- String with no length constraints

2.23 Nb TRX dependent

Definition: This field indicates if the default value depends on the number of TRX in the cell. If yes, these default values shall be given in a specific table. - Mandatory (default = no)

Constraints:

- 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 shall be given in a specific table. - Mandatory (default = no)

Constraints:

- Possible values: No, Yes

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 28/34

2.25 CDE ASCII TABLE

The flag CMA script within the O&M detailed information table ("O&Mdetailed") allows to indicate if the 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".

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 29/34

AGCH BCCH BLKS BSC BSS BTS

GLOSSARY

ARFCN

Access Grant CHannel

BLocKS

Broadcast Control CHannel

Absolute Radio Frequency Channel Number

BSCGP

Base Station Controller Base Station Subsystem (BSC+n*BTS) Common Control CHannel BSC GPRS Protocol

CCCH CND CRC CS DPC DTX

Base Transceiver Station Channel

CHAN.

Configuration Data Circuit Switched

Cyclic Redundancy Check Destination Point Code

FACCH GPRS GSL IE

Discontinuous Transmission

GPRS Signalling Link Information Element LoCation Services

General Packet Radio Service

Fast Associated Control Channel

LAPD LCS LSB

Link Access Procedure on the D-channel

MFS

Less Significant Bit

MSB MTP NA OIE

Multi-Function Server (GPRS) Mobile Switching Centre Most Significant Bit

MSC

OML PCH PS

Optional Information Element Originating Point Code Packet Switched Paging CHannel

Not Applicable

Message Transfer Part

OPC

Operations and Maintenance Link

RACH RRM RSL RX

Radio Signalling Link Receiver

Radio Resource Management (GPRS)

Random Access CHannel

SACCH SCCP ED EVOLIUM 11

Signalling Connection Control Part Released

0134_11.doc 22-Nov-07

Slow Associated Control CHannel

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 30/34

SCH

SDCCH SMSCB SPI SSF

Synchronisation CHannel

Stand alone Dedicated Control CHannel Short Message Service Cell Broadcast

Signalling Point Inaccessible Sub Service Field Signalling Point Accessible

SPA

SSP/SSA TCH TS

Time slot

Traffic Channel

SubSystem Prohibited/SubSystem Allowed

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 31/34

A - ANNEX : INTERNAL TIMERS A.1 - BSSAP TIMERS

T_SZE_CH It is started when sending SEIZE_CHANNEL to the DH_DTC waiting for the reply SEIZE_CHANNEL_ACK. If the timer expires then an ASS_FAIL or HND_FAIL will be returned to the MSC depending upon the reason for the seizure of the CIC. Location : DTC controlling the SCCP connection T_CH_ACT

It is started at the transmission of SEL_CH to the TCH RM requesting the selection of a TCH channel. It is stopped at the reception of TCH_ACT_ACK from the RFMNGT. If the timer expires then the assignment or handover will fail with an appropriate message being returned to the MSC depending upon the reason for attempted radio channel seizure. If the failed radio channel seizure was associated with an internal handover then the attempt will fail and the next cell in the preferred cell list will be attempted (if allowed). Location : DTC controlling the SCCP connection

It is started at the transmission of SELECT_SDCCH to the SDCCH RM requesting the selection of an SDCCH channel. It is stopped at the reception of DCH_ACT_ACK from the RFMNGT.

T_SMS_EST_CNF

It is started when sending the first short message to the RFMNGT. It is stopped at the reception of the message SMS_EST_CNF. If the timer expires then the set-up of the SAPI 3 connection will fail and an appropriate failure message will be sent to the MSC. Location : DTC controlling the SCCP connection

T_DEL_RLS

It is started when the MSC starts the release procedure (CLEAR_REQ not sent to the MSC), provided that the speech/data path across the BSC is established. It is used to prevent the RFMNGT controlling the connected radio channel receiving the RLS_REQ from the DH_TCU before the CLEAR_CMND message is received from the BSSAP. Location : DTC controlling the SCCP connection

T_MOD_REQ

It is started at the beginning of the in call modification procedure when the BSSAP triggers the RFMNGT to send the MODE_MODIFY message to the BTS. It is stopped at the reply from the RFMNGT. If the timer expires the in call modification procedure will fail and an ASS_FAIL message will be returned to the MSC. Location : DTC controlling the SCCP connection

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 32/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 SDCCH resource 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 earlier transmission 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_I

It 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 handover is 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

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 33/34

A.3 - RULES INVOLVING INTERNAL TIMERS

T8 < T_I T3103 < T_C_INTER T3103 < T_I T3107 < T_I T3107 < T_C T9103 + T9108 < T_A

T9103 + T9108 < T_CH_ACT T9103 < T_MOD_REQ T9105 < T_B T9113 < T_C_INTER T_C < T_I

T_BTS_EST_CNF < T_SMS_EST_CNF T_CH_ACT > T11

END OF DOCUMENT

ED EVOLIUM

11

Released
0134_11.doc 22-Nov-07

BSS TELECOM PARAMETERS release B10 3BK 11203 0134 DSZZA 34/34