You are on page 1of 513

s

Siemens Base Station (SBS)
BSC Database Parameter Description

BR8.0 - DRAFT
Version 02.05.2006

made by: Eckardt Bertermann SIEMENS AG COM MN PG NT NE 1, Network Engineering GERAN Tel.: +49 89 636 47691 FAX: +49 89 636 40109 e-mail: eckardt.bertermann@siemens.com
GPRS contributions by: Wolfgang Malter SIEMENS AG COM MN PG SI RA2, Technical Product Support BSS-SBS Tel.: +49 89 722 54716 FAX: +49 89 722 28990 e-mail: wolfgang.malter.extern@mchh.siemens.de

Please consider the remarks on the next page!

2

!
IMPORTANT
• This document is not officially released and is designed as quick reference document for SBS BSC database parameters. • This document is a working document and is continuously modified and enhanced with the latest information. Changes are not explicitly marked!

• The document’s purpose is to

- describe and explain the meaning of the BSC database parameters - describe and explain the parameters’ association to related features - provide cross-references between parameters that logically belong together, but are possibly distributed over different commands - provide rules and hints that have to be considered during the decision for the parameter values to guarantee a useful application of the parameter.

• The document’s purpose is NOT

- to provide binding recommendations for parameter value settings! - to be used as a reference database with respect to the parameter settings!! The used settings were not verified for a live netwok application!

• NO GUARANTEES FOR CORRECTNESS OF THE CONTENTS! • CONTENTS ARE NOT COMMERCIALLY BINDING!
• Any comments for corrections or suggestions for improvements are welcome! • The authors’ e-mail-address is only mentioned for feedback purposes! ► If you find mistakes, please check the latest versions of the document in IMS or Siemens Extranet first, before you feed back.

• Technical queries concerning specific parameters and features shall be not be sent to the authors but to CIC, R-NCC or NCC as an official hotline query!!!
(For queries to TPS-BSS, please use the well-known procedures.)

3

Contents:
1 DATABASE BR8.0 ......................................................................................................................................................... 5 1.1 BR8.0 OBJECT TREE OF BSC DATABASE OBJECTS ........................................................................................................ 5 1.2 BSC DATABASE COMMANDS AND PARAMETERS .................................................................................................... 5 Setting the object entry point and time and date for the BSS:.................................................................................... 5 Setting the BSC control values for periodic measurement data file upload:............................................................... 5 Setting the timing values for BSSMAP control and BSC overload handling:.............................................................. 5 Setting the global parameters of the BSC:................................................................................................................. 5 Creating new database parameters without info model change:................................................................................ 5 Setting the alarm priorities of the BSS functional objects: ......................................................................................... 5 Setting the remote Inventory data of the BSC Equipment:......................................................................................... 5 Setting the alarm priorities of the BSCE objects: ....................................................................................................... 5 Creating the Power Supply: ....................................................................................................................................... 5 Creating the spare PCM interface boards:................................................................................................................. 5 Creating the PCM interface boards:........................................................................................................................... 5 Creating the common attributes for all PCUs belonging to the entire BSC: ............................................................... 5 Creating the PCU objects: ......................................................................................................................................... 5 Creating the PCM links for the Abis interface: ........................................................................................................... 5 Creating the PCMS link: ............................................................................................................................................ 5 Creating the TRAU: ................................................................................................................................................... 5 Basic TRAU-mapping 1: NOT_COMPATIBLE_WITH_CROSSCONNECT (no pools created) ........................ 5 Basic TRAU-mapping 2: COMPATIBLE_WITH_CROSSCONNECT (no pools created) ................................. 5 Creating the LPDLS links:.......................................................................................................................................... 5 Creating the PCMA link: ............................................................................................................................................ 5 Setting the uplink and downlink volumes for specific PCMA timeslots:...................................................................... 5 Creating the PCMG link: ............................................................................................................................................ 5 Creating the physical link connection on the GPRS Gb interface (Frame Relay Link): ............................................. 5 Creating the end-to-end communication between BSS and SGSN: Network Service Virtual Connection (NSVC): ... 5 Creating the BTS Site Manager: ................................................................................................................................ 5 Creating the Common BTS data of a BTSM for Dynamic MAIO Allocation (DMA): ................................................... 5 Creating the hopping laws used for Dynamic MAIO Allocation: ................................................................................. 5 Creating the LPDLM links: ......................................................................................................................................... 5 Creating the terrestrial Abis timelots for flexible Abis allocation:................................................................................ 5 Creating a cell with definition of global parameters:................................................................................................... 5 Setting the cell specific parameters for DMA Admission Control ............................................................................... 5 Setting the cell attributes for the Interference Measurement of idle TCHs: ................................................................ 5 Setting the cell specific timer values: ......................................................................................................................... 5 Setting the cell specific optional features: .................................................................................................................. 5 Defining the cell specific service layer lists for the feature ‘Service dependent Channel Allocation’ (SDCA) via ‘Multi Service Layer Support’ (MSLS): ................................................................................................................................ 5 Setting the cell specific attributes for Power Control: ................................................................................................. 5 Power Control Parameter Relations...................................................................................................................... 5 Creating the GPRS point to point packet transfer service in a cell:............................................................................ 5 Creating the LPDLR links: ......................................................................................................................................... 5 Creating the cell-specific Frequency Hopping systems for static MAIO Allocation (SMA): ........................................ 5 Creating the TRXs: .................................................................................................................................................... 5 Enabling GPRS and EDGE in a cell: ......................................................................................................................... 5 Creating the BCCH for the cell:.................................................................................................................................. 5 Creating the SDCCHs for the cell: ............................................................................................................................. 5 Creating the TCHs for the cell: .................................................................................................................................. 5 Creating hybrid TCHs/SDCCHs (TCH/SD) for the cell:.............................................................................................. 5 Setting the cell specific parameters and threshold values for voice call Handover: ................................................... 5 Handover Parameter Relations............................................................................................................................. 5 Setting the cell specific parameters and threshold values for 14,4kbit/s data call up- and downgrading and quality inter-cell handover: .................................................................................................................................................... 5 Enabling features related to ASCI, SMS-CB, Frequency Hopping, HSCSD, Call Release due to Excessive Distance and Dynamic MAIO Allocation (DMA):....................................................................................................................... 5 Creating the Target Cell Objects:............................................................................................................................... 5 Creating the Target Point-to-point Packet Flow Objects: ........................................................................................... 5 Creating the Adjacent Cell Objects: ........................................................................................................................... 5 Creating the Target Cell Objects for handover from GSM to UMTS (FDD): .............................................................. 5 Creating the Adjacent Cell Objects for external UMTS FDD or UMTS TDD cells: ..................................................... 5 Creating the CCS7 level 3 addresses of BSC, MSC and SMLC and basic SCCP parameters for the SS7 connection: ................................................................................................................................................................ 5 Setting the timer values for CCS7 MTP level 2:......................................................................................................... 5 Setting the timer values for CCS7 MTP level 3:......................................................................................................... 5 Creating the CCS7 link: ............................................................................................................................................. 5
4

Creating a Nailed-Up Connection through the BSC/TRAU: ....................................................................................... 5 Creating an X25 connection via dedicated link: ......................................................................................................... 5 Creating an X25 connection via A-interface:.............................................................................................................. 5 Creating an IP Link connection: ................................................................................................................................. 5 Creating the O&M link for the RC connection: ........................................................................................................... 5 Creating the link for the external connection to the SMS-CB system:........................................................................ 5 Defining the BSC reference synchronization clock origin:.......................................................................................... 5 Defining an external synchronization signal: .............................................................................................................. 5 Creating the Quality of Service Alarm Objects:.......................................................................................................... 5 Creating the Quality of Service Alarm threshold sets:................................................................................................ 5 Creating the Quality of Service Alarm Objects for the BSC object:............................................................................ 5 Creating the Quality of Service Alarm Objects for BTS objects: ................................................................................ 5 Creating the Quality of Service Alarm Objects for PTPPKF objects: ......................................................................... 5 Activating IMSI tracing in the BSC: ............................................................................................................................ 5 Creating a Cell Traffic Recording (CTR) job: ............................................................................................................. 5 Enabling the data recording for the feature ‘History on Dropped Calls’:..................................................................... 5 Defining the BSC environmental alarms: ................................................................................................................... 5 Configuring the feature Online RF Loopback:............................................................................................................ 5 Creating Smart Carrier Allocation: ............................................................................................................................. 5 2 APPENDIX ....................................................................................................................................................................... 5 2.1 HANDOVER THRESHOLDS & ALGORITHMS ..................................................................................................................... 5 2.1.1 Functional Diagram Handover Thresholds for Inter-cell Handover and Intra-cell Handover (level, quality and power budget)............................................................................................................................................................ 5 2.1.2 Rules: Handover Thresholds for Inter-cell Handover and Intra-cell Handover (level, quality and power budget), Power Control disabled................................................................................................................................ 5 2.1.2.1 Inter-cell/Inter-system Handover due to level ............................................................................................ 5 2.1.2.1.1 Handover Decision / Handover Trigger Conditions ........................................................................... 5 2.1.2.1.2 Target Cell List Generation .............................................................................................................. 5 2.1.2.2 Intra-cell handover (quality)...................................................................................................................... 5 2.1.2.3 Inter-cell/Inter-system Handover due to quality ........................................................................................ 5 2.1.2.3.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.3.2 Target Cell List Generation .............................................................................................................. 5 2.1.2.4 Inter-cell/Inter-system Handover due to distance ..................................................................................... 5 2.1.2.4.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.4.2 Target Cell List Generation .............................................................................................................. 5 2.1.2.5 Inter-cell/Inter-system Handover due to better cell (power budget handover) .......................................... 5 2.1.2.5.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.5.2 Target Cell List Generation .............................................................................................................. 5 2.1.2.5.1 Speed sensitive handover enabled .................................................................................................. 5 2.1.2.5 Inter-system Handover due to suifficient coverage .................................................................................. 5 2.1.2.5.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.6 Forced Handover due to directed retry, preemption or O&M intervention ................................................ 5 2.1.2.6.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2) The averaging of both RXLEV_DL values (2G neighbour cells) as well as RSCP values (3G neighbour cells) is done with an averaging window whose length is defined by parameter HOAVPWRB (SET HAND)2.1.2.7 Fast Uplink Handover (Intra-BSC only) ......................................................................................................................... 5 2.1.2.7 Fast Uplink Handover (Intra-BSC only) .................................................................................................... 5 2.1.2.7.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.7.2 Target Cell List Generation .............................................................................................................. 5 2.1.2.8 Inter-cell Handover due to BSS Resource Management Criteria (Traffic HO) ......................................... 5 2.1.2.8.1 Handover Decision / Handover Trigger Conditions .......................................................................... 5 2.1.2.8.2 Target Cell List Generation .............................................................................................................. 5 2.2 HIERARCHICAL CELL STRUCTURE ................................................................................................................................. 5 2.2.1 Cell ranking for power budget handovers (non-imperative handover).............................................................. 5 2.2.1.1 Speed sensitive handover enabled .......................................................................................................... 5 2.2.2 Cell ranking for imperative handovers (due to level, quality and distance) and forced handover (directed retry) .......................................................................................................................................................................... 5 2.2.2.1 Ranking method 0 .................................................................................................................................... 5 2.2.2.2 Ranking method 1 .................................................................................................................................... 5 2.2.3 Target Cell Ranking for Traffic Handover with HCS......................................................................................... 5 2.3 SEQUENCE OF HANDOVER TYPES WITHIN THE HANDOVER DECISION ALGORITHM IN THE BTS ............................................ 5 2.4.1 Functional Diagram: Power Control Thresholds - Power Increase / Power Decrease (Classic Power Control)5 2.4.2 Rules: Power Control Thresholds: Power Increase / Power Decrease ............................................................ 5 2.4.2.1 Power Increase ........................................................................................................................................ 5 2.4.2.2 Power Decrease....................................................................................................................................... 5 2.4.3 Classic and Adaptive Power Control................................................................................................................ 5 2.4.3.1 Introduction ............................................................................................................................................... 5 2.4.3.2 Classic Power Control decision process .................................................................................................. 5
5

2.4.3.3 Adaptive Power Control decision process ................................................................................................ 5 2.4.3.4 Differences between CLASSIC and ADAPTIVE power control decision .................................................. 5 2.4.3.5 Functional sequence of a BS and MS power control procedure............................................................... 5 2.4.3.5.1 BS power control procedure ............................................................................................................. 5 2.4.3.5.2 MS power control procedure ............................................................................................................ 5 2.4.3.6 Comparison of timing behaviour of different Power Control types - MS Power Control, BS Power Control, classic and adaptive ................................................................................................................................ 5 2.4.3.7 Further differences between CLASSIC and ADAPTIVE Power Control ................................................... 5 2.4.3.8 Interaction of Power Control Measurement Preprocessing and Power Control Decision ........................ 5 2.5 INTERWORKING OF HANDOVER AND POWER CONTROL ................................................................................................... 5 2.5.1 Functional Diagram: Inter-cell Handover and Intra-cell Handover, Power Increase and Power Decrease........ 5 2.5.2 Rules ............................................................................................................................................................... 5 2.6 SERVICE DEPENDENT HANDOVER AND POWER CONTROL ............................................................................................... 5 2.6.1 Introduction ...................................................................................................................................................... 5 2.6.2 SGxHOPAR and SGxPCPAR parameter values .............................................................................................. 5 2.6.2.1 SGxHOPAR parameter values (Handover)............................................................................................... 5 2.6.2.2 SGxPCPAR parameter values (Power Control) ........................................................................................ 5 2.6.2.3 Effects on Call processing......................................................................................................................... 5 2.7 REPORTING, DISPLAY AND BTS INTERNAL HANDLING OF RSCP VALUES FROM 3G NEIGHBOUR CELLS ................................. 5 2.8 MAPPING OF RXQUAL AND C/I VALUES ....................................................................................................................... 5 2.9 AMR LINK ADAPTATION THRESHOLDS UPLINK ............................................................................................................... 5 2.10 BSC, MSC AND BTS OVERLOAD HANDLING ............................................................................................................... 5 2.10.1 BSC Overload................................................................................................................................................ 5 2.10.1.1 BSC overload conditions......................................................................................................................... 5 2.10.1.2 System reactions and overload regulation measures in case of BSC overload ..................................... 5 2.10.1.2 System reactions and overload regulation measures in case of BSC overload ..................................... 5 2.10.1.2.1 Further important notes on BSC reactions ..................................................................................... 5 2.10.1.3 Mechanisms for reduction of originating traffic and reduction of terminating traffic ................................ 5 2.10.1.3.1 Overload level management........................................................................................................... 5 2.10.1.3.2 Traffic reduction algorithms ............................................................................................................ 5 2.10.1.3.3 Special overload supervision algorithm in case of BSC paging queue overflow............................. 5 2.10.2 MSC Overload ............................................................................................................................................... 5 2.10.2.1 System reactions and overload regulation measures in case of MSC overload...................................... 5 2.10.2.1.1 Special overload level escalation algorithm in case of MSC overload ............................................. 5 2.10.3 BTS Overload ................................................................................................................................................ 5 2.10.3.1 BTS overload conditions ......................................................................................................................... 5 2.10.3.2 Traffic reduction mechanisms in case of BTS overload ......................................................................... 5 2.10.3.3 System reactions and overload regulation measures in case of BTS overload...................................... 5 2.10.4 Interaction of BTS Overload and BSC Overload............................................................................................ 5 2.10.5 Effects on Performance Measurement Counters ........................................................................................... 5 3 ALPHABETICAL COMMAND AND PARAMETER INDEX............................................................................................. 5

6

1 Database BR8.0
1.1 BR8.0 Object Tree of BSC database objects

Note: The objects BTSMOSUSW, TRAOSUSW, SCANCO, the scanner objects (“SCANxxxx”) as well as the objects related to TD-SCDMA (objects subordinate to BTSMTD) are not considered in this document.

7

Notes:
1) The commands of this example database are basically presented in the same order as they are generated by DBAEM when generating an ASCII database from a database in binary format. 2) The parameters marked by (compared to BR7.0). grey background are new in BR8.0

3) Changes of parameter values, value ranges and default values are indicated by highlighted letters. Changes of parameter names are marked, too.
4) In BR6.0 the ‘packages’ (e.g. PKGBTSB, PKGBSCT etc.) were removed so that all parameters subordinate to one object (e.g. BTS) are included in one and the same command (CREATE/SET BTS). The disadvantage is that among the huge number of parameters within one command it is hard to find a specific parameter quickly. I decided to use the following approach in this document: - For a better logical structure, the parameters are still grouped in the ‘pseudo-packages’ (e.g. CREATE BTS [BASICS], SET BTS [CCCH] etc.) used in the LMT GUI. - Within each package, an alphabetical order was used for the sequence of parameters (as done by DBAEM) to facilitate the handling and overview.

8

1.2

BSC Database Commands and Parameters

Setting the object entry point and time and date for the BSS:
< The MEL (Managed Element) object represents the entry point of the addressing of the BSS. It simultaneously represents the object with which the network element time and date can be set. > SET MEL: NAME=MEL:0, ETIME=12-00..00..1-1-2002,
object: format: range: MEL hour –minute-secondday-month-year hour 0..23 minute 0..59 second 0..59 day 1..31 month 1..12 year 1992..2099

Object name. External time, this parameter defines the network element time in the BSS.

MELID=1;
object: range: MEL 1..83

Managed Element ID, this parameter defines the “name“ resp. ID of the BSS in the Radio Commander (RC) area. The value entered for MELID must match to the BSS_RDN in the RC database to ensure the correct operation of the higher communication layers on the O&M link between BSC and RC. This parameter replaces the BSSNAME parameter which was used in older releases up to BR5.5.

Setting the BSC control values for periodic measurement data file upload:
Attention: Since BR6.0 The DBAEM does not group the command parameters into ‘packages’ anymore. Instead, all parameters of the previous ‘BSC packages’ were moved below the object BSC and appear in the DBAEM in the SET BSC command. The logical group “[CONTROL]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . Object name. CTR file size, this attribute indicates the maximum size of the ‘Cell Traffic Recording’ logfile on the BSC disk. The feature ‘Cell Traffic Recording’ or ‘Cell Trace’ (CTR) is a feature used to record cell specific call events for monitoring purposes in a similar way like IMSI tracing (for details please see command CREATE CTRSCHED).The parameter CFS specifies the maximum file size for the CTR trace logfiles in the BSC directory. When a CTR tracing procedure is in progress, the BSC writes the binary trace data to the open binary trace file in the BSC directory TRACE_CTR. On call termination, a trace record is generated an written to the CTR trace logfile. The parameter CFS specifies the maximum size of this CTR logfile. When the trace logfile exceeds the size specified by CFS, it is closed and transferred to the BSC directory READY_CTR. Form there it is compressed to the directory DBFH_ZIP from where it is uploaded to the RC at the next possible point of time (automatic upload takes place every 5 minutes). A CTR logfile can also be automatically closed and prepared for upload if the trace is still in progress. In this case a new open binary file is generated which records the next events of the call to be traced. In the RC, the uploaded files are decompressed, merged and converted to ASCII for analysis by the DUIT application.

SET BSC [CONTROL]: NAME=BSC:0, CFS=3,
object: unit: range: default: BSC [CONTROL] 1 Mbyte 1-12 1

9

IMSIFSIZ=30,
object: unit: range: default: BSC [CONTROL] 1 Mbyte 0..30 30

HDCFS=1,
object: unit: range: default: BSC [CONTROL] 1 Mbyte 1-12 1

HDCFUPE= upPe0h,
object: BSC [CONTROL] range: upPe0h= no per. upl. upPe1h = Upl. period 1h upPe2h = Upl. period 2h upPe3h = Upl. period 3h upPe4h = Upl. period 4h upPe6h = Upl. period 6h upPe8h = Upl. period 8h upPe12h= Upl. period 12h upPe24h= Upl. period 24h default: upPe0h

IMSI file size, this parameter is associated to the feature 'IMSI Tracing' (see command CREATE TRACE) and specifies the maximum file size for the IMSI trace files in the BSC directory. When an IMSI tracing procedure is in progress, the BSC writes the binary trace data to the open binary trace file in the BSC directory TRACE_IMSI. The parameter IMSIFSIZ specifies the maximum allowed size of this binary trace file. When the tracing process is finished the binary trace files are closed and compressed to the BSC directory READY_IMSI. Form there they are compressed to the directory DBFH_ZIP from where they are uploaded to the RC at the next possible point of time. When the maximum size has been reached although the traced call is still in progress, the binary file is also closed and compressed to the directory READY_IMSI for upload and a new binary trace file is opened. In the RC, the uploaded files are decompressed, reassembled and converted to ASCII for analysis by the DUIT application. HDC file size, this attribute indicates the maximum size of the ‘History on Dropped Calls’ logfile on the BSC disk. The feature ‘History on Dropped Calls’ (HDC or HDCTR, see also command CREATe HDCTR and parameter EHDCTR in command CREATE BTS [BASICS]) is a feature used to record history data of dropped calls (for details, please refer to the command CREATE HDCTR), such as the last received MEASUREMENT REPORT messages as well as layer 3 messages relevant for channel changes. The parameter HDCFS specifies the maximum file size for the HDCTR trace logfiles in the BSC directory. When a CTR tracing procedure is in progress, the BSC writes the binary trace data to the open binary trace file in the BSC directory TRACE_HDCTR. When a call drop occurs while the HDCTR feature is enabled, a HDCTR record is generated an written to the HDCTR logfile. The parameter CFS specifies the maximum size of this HDCTR logfile. When the trace logfile exceeds the size specified by HDCFS, it is closed and transferred to the BSC directory READY_HDCTR. Form there it is compressed to the directory DBFH_ZIP from where it is uploaded to the RC at the next possible point of time (automatic upload takes place every 5 minutes). In the RC, the uploaded files are decompressed, merged and converted to ASCII for analysis by the application DUIT/RNA. HDC data file upload period, defines the time period between two uploads of logfiles for the feature ‘History on Dropped Calls’ (for details, please refer to the command CREATE HDCTR). Setting this parameter to ‘upPe0h’ disables the periodic upload.

10

The size threshold entered by MASCLOGFS determines the maximum allowed size of the file SCAN. 11 . defines the start time for measurement data file upload.LOG is automatically uploaded to the RC. period 1h UPPE_2h = Upl. upl. period 2h UPPE_3h = Upl.MASCLOGFS=3. object: BSC [CONTROL] range: UPPE_0h= no per. Form there it is compressed to the directory DBFH_ZIP from where it is uploaded to the RC.LOG and transferred to the directory READY_MEAS.upload start minute. defines the time period between two uploads of measurement data files. renamed to SCAN.59 0 0 Measurement data file upload start. MEDAFUST=0-0.TMP: when the entered size is reached for the file SCAN. This file is available in the BSC directory MEASURE_DIR.23 0. Measurement data file upload period. The file SCAN.TMP is closed. this attribute indicates the maximum size of the scanner result file on the BSC disk. Setting this parameter to UPPE_0h disables the periodic upload.TMP is the scanner logfile on the BSC disk to which all scanner results of scanners which were created ‘BYFILE’ are written. period 3h UPPE_4h = Upl. period 8h UPPE_12h= Upl. To upload the scanner results to the RC the file SCAN..TMP file. UPPE_1h = Upl. New measurement results are then written to a newly opened SCAN. period 24h default: UPPE_0h Maximum scanner logfile size.. Parameter format: upload start hour . period 6h UPPE_8h = Upl. object: range: default: BSC [CONTROL] upload start hour upload start minute upload start hour upload start minute 0. period 12h UPPE_24h= Upl.TMP the SCAN. period 4h UPPE_6h = Upl. object: unit: range: default: BSC [CONTROL] 1 Mbyte 1-6 3 MEDAFUPE=UPPE_0H.

The MSC therefore needs to be informed about Ainterface circuits that are out of service in the BSC or cannot be used due to configuration of OMAL.. the CIRCUIT GROUP BLOCKING/UNBLOCKING procedure is used (see BSCT20). unblock single affected A-timeslots by using the BSSMAP message BLOCKING/UNBLOCKING. b) Intra-cell handover: keep the old channels available for a sufficient time in order to allow the MS to return to the old channel return to it if the handover is not successful and to release the old channel if the MS is lost during the handover procedure. After a second expiration the BSS marks the associated circuits as blocked without waiting for the acknowledgement. all parameters of the previous ‘BSC packages’ were moved below the object BSC and appear in the DBAEM in the SET BSC command. This timer is started on the sending of an ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly seized the new channels.5s SEC5=5s range: 0.08) The value must be higher than the maximum transmission time of the ASSIGNMENT COMMAND and the ASSIGNMENT COMPLETE message plus the maximum duration of an attempt to establish a data link multiframe mode. Rule: BSCT10 < TTRAU (for TTRAU see command SET BTS [TIMER]) This setting is necessary to ensure that a signaling failure (T8 and T10) is detected before transcoder failure (TTRAU) 12 . the MSC marks the affected timeslots as 'unavailable'.254 default: HLFSEC-10 Reference: GSM 08. As a result.. The BSC instructs the MSC to block resp. i. BSC timer T1. LPDLS or SS7L etc. Note: Due to the SBS implementation T10 replaces the function of the GSM timer T3107. this timer determines the time to return the ASSIGNMENT COMPLETE message in case of call setup and intra-cell handover. BSC timer T10.0 The DBAEM does not group the command parameters into ‘packages’ anymore.08 (04. BSCT1=HLFSEC-12. start: a) & b): sending of an ASSIGNMENT COMMAND by the BSC stop: a) & b): receipt of an ASSIGNMENT COMPLETE or an ASSIGNMENT FAILURE from the MS expiry action: a) Assignment procedure: Sending of an ASSIGNMENT FAILURE to the MSC with cause 'radio interface message failure' followed by release of the call resources. The logical group “[TIMER]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . The timer T1 supervises the receipt of the BLOCKING/ UNBLOCKING ACKNOWLEDGE message from the MSC. T10 purpose: SET BSC [TIMER]: NAME=BSC:0. object: unit: BSC [TIMER] HLFSEC=0. After a first T1 expiration the BSS repeats the BLOCKING/UNBLOCKING message. b) Intra-cell handover: Sending of a CLEAR REQUEST to the MSC with cause 'radio interface message failure' followed by release of the call resources (CLEAR CMD received from MSC). The MSC selects the terrestrial resources (A interface traffic channels) to be used for a call.254 default: HLFSEC-12 Reference: GSM 08.Setting the timing values for BSSMAP control and BSC overload handling: Attention: Since BR6. object: unit: BSC [TIMER] HLFSEC=0. T3107 is not used by the SBS. a) Assignment procedure: release of the associated resources if the MS is lost during the assignment procedure..e.5s SEC5=5s range: 0. The value of T1 must be higher than the MSC maximum reaction time and the transmission time for the blocking/unblocking and the associated acknowledge message. If a group of A-interface timeslots is to be blocked simultaneously. this timer determines the time to receive the BSSMAP message BLOCKING ACKNOWLEDGE.08 BSCT10=HLFSEC-10. Instead. Object path name.

Notes: .5s SEC5=5s 0. which is a special enhancement of the feature ‘queuing’ required by the U. the original ‘queuing’ feature is replaced by the feature ‘Wireless Priority Service (WPS)’. The parameter BSCT11WPS defines the queing timer T11 for the ‘WPS’ queue.) and is only relevant if the feature ‘queuing’ / ‘WPS queuing’ is enabled (see parameter EQ in command SET BTS [OPTIONS] for a detailed description).0.254 HLFSEC-16 In BR8. QLPUB. WPSPREF. T11 determines the maximum time the TCH request may remain in the queue to wait for a busy TCH to become idle. . BSC timer T11 WPS. QLWPS. If no TCH can be found in the target cells. market (see parameter EQ in command SET BTS [OPTIONS]). .0..e.08 Cancelled – parameter is replaced by parameters BSCT11PUB and BSCT11WPS in BR8. the BSC sends a CLEAR REQUEST to the MSC and the context is released.BSCT11 BSCT11PUB=HLFSEC-16. Limitation of the queuing time for an TCH request due to Assignment sending of the QUEUING INDICATION (BSC->MSC) . object: unit: range: default: BSC [TIMER] HLFSEC=0. The parameter BSCT11PUB replaces the parameter BSCT11 (used up to BR7.If the BSC receives an INTERCELL HANDOVER CONDITION INDICATION from the BTS during the queuing time. the BSC directly searches for an idle TCH in the target cell! In other words.S. when the BSC receives an ASSIGNMENT REQUEST message from the MSC) is put into a queue due to TCH congestion. this timer determines the maximum allowed queuing time for TCH assignment requests in the ‘WPS queue’. Further parameters related to the WPS feature are BSCT11WPS.254 default: HLFSEC-16 Reference: GSM 08.discarding of the TCH request from the TCH queue (all cases except T11 expiry) expiry action: Sending of a CLEAR REQUEST to the MSC with cause 'no radio resource available' followed by release of the call resources. during the queuing time no SDCCH-SDCCH handover will ever be performed. this timer determines the maximum allowed queuing time for TCH assignment requests in the ‘public queue’.Queuing a TCH request means a considerable extension of the SDCCH seizure duration! . Therefore it has to be carefully considered which waiting time can be regarded as acceptable from the subscriber's point of view. BSCTQHOPUB. This feature foresees a two queue concept. When a TCH request for an assignment procedure (i. BSC timer T11 public. BSCTQHOWPS (see below) and EQ. The parameter BSCT11PUB defines the queing timer T11 for the ‘public’ queue.. In other words: it makes no sense to set T11 to a too high value. object: unit: BSC [TIMER] HLFSEC=0. If the TCH request for assignment procedure cannot be served within this time frame and T11 expires. one queue being used for ordinary subscribers (‘public’) and one for priorized subscribers (‘WPS queue’).It is important to consider that the feature 'queuing' stresses the patience of the subscribers as it extends the time a subscriber has to wait (possibly in vain) for the assignment of a TCH in a busy cell. This parameter is only relevant if the feature ‘Wireless Priority Service (WPS)’ is applied (see parameter BSCT11PUB). 13 .successful allocation of a TCH to the queued TCH request . T11 purpose: start: stop: BSCT11WPS=HLFSEC-16. This may decrease the queuing time considerably. LWWPSPRI (see command SET BTS [OPTIONS]).It is possible to accelerate the release of busy TCHs by an appropriate setting of the timer T3111 (see SET BTS [TIMER]).5s SEC5=5s range: 0. the TCH request is discarded from the queue.

the overload conditions and traffic reduction mechanisms are explained in an own chapter that comprises all possible scenarios of overload and overload handling as well as the references to the relevant parameters. object: unit: range: default: BSC [TIMER] HLFSEC=0. BSC timer T19.08 BSCT19=HLFSEC-12. this timer represents the overload observation timer and it is used in all cases of BSS overload regulation: BSC overload regulation. BSC timer T17. As MSC.5s SEC5=5s range: 0. object: unit: BSC [TIMER] HLFSEC=0.. It provides the time for the BSS to release all affected calls and to erase all affected references. If T19 expires before the receipt of the RESET CIRCUIT ACKNOWLEDGE the BSC repeats the RESET CIRCUIT PROCEDURE and restarts T19. For further details about the exact function of the timer BSCT18 within the BSS overload regulation please refer to the section “BSC. It is recommended to set both T13 in the BSC and T2 in the MSC to ca. BSCT17 is used in close relation to the timer BSCT18 (see below)..08 BSC timer T13. The timer T13 is a guard timer which is started after the receipt of the BSSMAP message RESET (see also BSCT4). BTS and MSC overload Handling” in the appendix of this document. this timer determines the time to receive RESET CIRCUIT ACKNOWLEDGE at the BSC. object: unit: BSC [TIMER] HLFSEC=0. this timer represents the overload message ignore timer which is used only in case of MSC overload.5s SEC5=5s range: 0. this timer determines the RESET guard period at the BSS.254 HLFSEC-20 BSCT18=HLFSEC-60. The RESET CIRCUIT procedure is started either by the BSC or the MSC if a single circuit has to be put into the idle state due to abnormal SCCP connection release. 10s. 14 .5s SEC5=5s range: 0. The value of T13 must be higher than the time needed by the BSS to release all affected calls and to erase all affected references.. As MSC.254 default: HLFSEC-12 Reference: GSM 08. object: unit: BSC [TIMER] HLFSEC=0. BTS and MSC overload Handling” in the appendix of this document. After expiration of T13 the BSS sends a RESET ACKNOWLEDGE message to the MSC.254 default: HLFSEC-60 Reference: GSM 08.08 BSCT17=HLFSEC-20. MSCOVLH and BTSOVLH in command SET BSC [BASICS]).BSCT13=HLFSEC-50.5s SEC5=5s 0. puts the affected traffic channel to the idle state and returns the message RESET CIRCUIT ACKNOWLEDGE to the BSC.254 default: HLFSEC-50 Reference: GSM 08. BSC and BTS overload handling are closely interwoven. If the RESET CIRCUIT procedure is initiated by the BSC it sends the BSSMAP message RESET CIRCUIT to the MSC which clears all associated call transactions. BSC and BTS overload handling are closely interwoven.. BSC timer T18. MSC overload regulation and BTS overload regulation (see parameters BSCOVLH. Rule: T16 (MSC) > BSCT13 (BSC) The value of the "Wait for Acknowledge timer" T16 in the MSC must be higher than the value of T13 plus the transmission time of the RESET and the RESET ACKNOWLEDGE message (it is recommended to set the MSC-timer T16 to 35s). the overload conditions and traffic reduction mechanisms are explained in an own chapter that comprises all possible scenarios of overload and overload handling as well as the references to the relevant parameters. For further details about the exact function of the timer BSCT18 within the BSS overload regulation please refer to the section “BSC.

T3121 is the 2G-3G handover equivalent to the timer T8 (see parameter BSCT8). As a result. The timer T20 supervises the receipt of the BLOCKING/ UNBLOCKING ACKNOWLEDGE message from the MSC.g.254 default: HLFSEC-50 Reference: GSM 08. The MS.5s SEC5=5s range: 0. The RESOURCE INDICATION message contains information about the number of available TCHs per interference band for a specific cell and is sent by from the BSC to the MSC if the BSC has previously received the BSSMAP message RESOURCE REQUEST from the MSC. due to failure of a TRAU) the BSC instructs the MSC to block the affected A-interface circuits by using the BSSMAP message CIRCUIT GROUP BLOCKING/UNBLOCKING. switches over to the target channel in the UMTS 3G neighbour cell and. This event is counted as a call drop by the PM counters NRFLTCH (subcounter 9) and NRCLRREQ (subcounter cause: radio interface message failure) and will thus appear as a call drop event in the PM statistcs.. BSC timer T3. BSC timer T3121. sends the RRC HANDOVER COMPLETE towards the target RNC which in turn sends an Iu RELOCATION COMPLETE message to the 3G MSC. It is started when the HANDOVER REQUIRED is sent and it is stopped. After a second expiration the BSS marks the associated circuits as blocked without waiting for the acknowledgement.08 BSCT3=HLFSEC-50. the BSC forwards this ISHTURAN HANDOVER COMMAND to the multiRAT MS and simultaneously starts the timer T3121. When it expires. when the CLEAR COMMAND with cause ‘handover successful’ is received. In this case the BSC has sent a BSSMAP HANDOVER REQUIRED with a UMTS 3G neighbour cell (see command CREATE ADJC3G) in the target cell list to the 3G MSC. on receipt of the HO CMD. The MSC selects the terrestrial resources (A interface traffic channels) to be used for a call. If a group of A-interface channels cannot be used any more (e. The timer T3121 is stopped. Note: T3121 has the same function for 2G-3G handover from GSM to a UTRAN-TDD neighbour cell (TD-SCDMA). this timer determines the time to receive CIRCUIT GROUP BLOCKING ACKNOWLEDGE. When the target RNC has provided the target channel data and and the 3G-MSC has sent the associated INTER SYSTEM TO UTRAN HANDOVER COMMAND to the BSC.08 BSCT3121=HLFSEC-10. The MSC therefore needs to be informed about any A-interface circuits that are out of service in the BSC or cannot be used due to other reasons. the MSC marks all affected timeslots as 'unavailable'. The RESOURCE REQUEST message indicates a specific cell identifier and can trigger the transmission a single RESOURCE INDICATION as well as the transmission of several RESOURCE INDICATIONs in a periodic manner. After a first T20 expiration the BSS repeats the BLOCKING/UNBLOCKING message.BSCT20=HLFSEC-12. when the BSC has received the CLEAR COMMAND with cause ‘handover successful’.5s SEC5=5s range: 0.. object: unit: range: default: Reference: BSC [TIMER] HLFSEC=0. For the periodic transmission of RESOURCE INDICATION the timer T3 determines the period between two consecutive transmissions of the RESOURCE INDICATION. this parameter represents a timer which is used to supervise the 2G-3G handover procedure towards an UTRAN-FDD cell. the BSC sends a CLEAR REQUEST with cause ‘radio interface message failure’ to the 3G-MSC to indicate the drop of the connection during the handover procedure.254 default: HLFSEC-12 Reference: GSM 08. object: unit: BSC [TIMER] HLFSEC=0. this timer determines the frequency of the BSSMAP message RESOURCE INDICATION sending.254 HLFSEC-10 BSC timer T20.. 15 . in case of successful link setup. The value of T20 must be higher than the MSC maximum reaction time and the transmission time for the blocking/unblocking and the associated acknowledge message.5s SEC5=5s 0. object: unit: BSC [TIMER] HLFSEC=0.

BSC timer T7. call cleared expiry action: . Rule: BSCT4 (BSC) > T2 (MSC) The value of T4 must be higher than the value of the MSC timer T2 plus the transmission time of the RESET and the RESET ACKNOWLEDGE messages (It is recommended to set the MSCtimer T2 to ca. 10s).e. Note: The RESET procedure can also be initiated by the MSC. object: unit: BSC [TIMER] HLFSEC=0. In this case equivalent timers are used: The MSC timer T16 supervises the receipt of the RESET ACKNOWLEDGE message (equivalent to the BSC timer T4) and the guard period in the BSC for the transmission of the RESET ACKNOWLEDGE is the timer T13 (see BSCT13).0! BSC timer T4.BSCT4=HLFSEC-60. the HO CMD might be received after T7 expiry.08 BSCT7=HLFSEC-8. The BSC sends the BSSMAP message RESET to the MSC in the event of a failure which leads to the loss of transaction reference information.. the BSC retransmits the RESET message and starts T4 again. After the a guard period of T2 (MSC timer) the MSC responds with a RESET ACKNOWLEDGE message.08 GSM 05..transaction has ended. All HO CMDs received after expiry of T7 are discarded by the BSC.254 default: HLFSEC-60 Reference: GSM 08. the BSS sends a HANDOVER REQUIRED message to the MSC and starts T7. Waiting time for a HANDOVER COMMAND from the MSC sending of HANDOVER REQUIRED by the BSC . The purpose of the RESET message is to initialize the BSSMAP relation between MSc and BSC and to put all affected circuits into the idle state. the BSC call processing terminates the 'waiting for HO CMD' state and the receipt of new HO COND IND message directly leads to the transmission of an updated HO RQD. This leads to the discarding of the HO CMD and thus to a forced release of the call by the MSC as the MSC supervises the by an own timer (Trr7 in Siemens MSC) which is started when the HO CMD is transmitted and which waits for the 16 . During this time the BSC ignores all new HO COND IND messages received from the BTS and no further HO RQDs are sent. This has to be considered by setting BSCT7 to a sufficiently high value in the originating BSC. If BSCT7 is too short.communication to MS is lost .new HO_RQD is sent if HO_COND_IND is received from the BTS T7 purpose: start: stop: Notes: 1) Attention: Especially in case of Inter-MSC handovers or if the features “queuing” or/and ”preemption” are used for incoming MSC controlled handovers.08 Default values changed in BR8. If the BTSE has sent a HANDOVER CONDITION INDICATION message and the handover is to be executed by the MSC (if the first target cell is an external one or if LOTERCH or LOTRACH (see SET HAND [BASICS]) are set to FALSE) or if the MSC has initiated a HANDOVER CANDIDATE ENQUIRY procedure. If no RESET ACKNOWLEDGE has been received before expiry of T4. As long as T7 runs the BSC call processing code remains in a state 'waiting for HO CMD'.254 default: HLFSEC-6 Reference: GSM 08. this timer determines the waiting time for a HANDOVER COMMAND from the MSC after transmission of a HONDOVER REQUIRED to the MSC. this BSSMAP timer determines the time to return a BSSMAP RESET ACKNOWLEDGE message. When the MSC has received the RESET message form the BSC it releases all affected connections and initializes the associated traffic channels.HO CMDs are ignored .5s SEC5=5s range: 0.receipt of a HANDOVER COMMAND from the MSC . If T7 expires (i. The timer T4 is started when the BSC transmits the RESET message to the MSC and watches over the receipt of a RESET ACKNOWLEDGE from the MSC.5s SEC5=5s range: 0. the handover completion may take a long time due to the additional handover of the preempted call in the target cell. object: unit: BSC [TIMER] HLFSEC=0. no HO CMD was received from the MSC).

As the experience has shown. object: unit: BSC [TIMER] HLFSEC=0. T8 purpose: BSCT8=HLFSEC-10.. start: transmission of a HANDOVER COMMAND from the BSC to the MS stop: a) intra-BSC handover: receipt of a HANDOVER COMPLETE or a HANDOVER FAILURE from the MS b) inter-BSC handover: receipt of a CLEAR COMMAND from the MSC or HANDOVER FAILURE from the MS expiry action: Sending of a CLEAR REQUEST to the MSC with cause 'radio interface message failure' followed by release of the call resources (CLEAR CMD received from MSC).08 The value must be bigger than the sum of the time for all messages to be sent to the MS plus the time to access a target and come back (if necessary). As the experience has shown. T8 is defined as the time that BSC layer 3 will wait for a handover to complete before releasing the source channel.5s SEC5=5s range: 0.‘handover successful’ indication from the target side or a HANDOVER FAILURE (DTAP) from the originating side. 2) This timer should be set with respect to the timer value THORQST (see command SET HAND) and the SIEMENS MSC internal timer T_HO_REJ. especially in case of InterMSC handover (with a possible GPRS preemption procedure in the target cell) the time for the receipt of the HO CMD in the originating BSC may even exceed 3 seconds. Recommended setting: THORQST (HAND) > BSCT7 (BSC) BSC timer T8. this timer determines the time to receive the HANDOVER COMPLETE message. during inter-MSC handover procedures it may take more than 2s until the HANDOVER COMMAND is received from the MSC (in case of inter-PLMN handover it may be even more). it is recommended to apply at least the setting BSCT7 ≥ HLFSEC-7 or longer.254 default: HLFSEC-10 Reference: GSM 08. Rule: BSCT8 < TTRAU (for TTRAU see command SET BTS [TIMER]) This setting is necessary to ensure that a signaling failure (T8 and T10) is detected before transcoder failure (TTRAU) 17 . Note: Due to the SBS implementation T8 replaces the function of T3103 (see SET BTS [TIMER]). keep the old channels available for a sufficient time in order to allow the MS to return to the old channel return to it if the handover is not successful and to release the old channel if the MS is lost.

this timer determines the maximum allowed queuing time for TCH requests due to incoming handover in the ‘public queue’. This parameter is only object: BSC [TIMER] unit: HLFSEC=0. This parameter is only relevant if the feature ‘queuing’ is enabled (see parameter EQ in command SET BTS [OPTIONS]). 18 ..5s relevant if the feature ‘Wireless Priority Service (WPS)’ is applied. This parameter is only object: BSC [TIMER] unit: HLFSEC=0. When a TCH request for an incoming MSC-controlled handover (i.S. BSCT11WPS (see above).5s SEC5=5s range: 0.254 default: HLFSEC-20 Reference: GSM 08.5s relevant if the feature ‘Wireless Priority Service (WPS)’ is applied SEC5=5s (see parameter BSCTQHOPUB). object: unit: BSC [TIMER] HLFSEC=0.successful allocation of a TCH to the queued TCH request . TQHO purpose: Note: It is possible to accelerate the release of busy TCHs by an appropriate setting of the timer T3111 (see SET BTS [TIMER]). QLWPS. the TCH request is rejected with a HANDOVER FAILURE. if there is another target cell available for the handover procedure. BSC timer for queuing of handover in public queue.254 defines the queing timer TQHO (see parameter BSCTQHO which is default: HLFSEC-16 used for ordinary queing) for the ‘WPS’ queue.08 BSC timer for queuing of handover. BSCTQHOWPS (see below) and EQ. BSCTQHOPUB=HLFSEC-16.BSCTQHO=HLFSEC-20. this timer determines the maximum allowed queuing time for incoming handover. The parameter BSCTQHOPUB defines the queing timer TTQHO (see parameter BSCTQHO which is used for ordinary queing) for the ‘public’ queue. market (see parameter EQ in command SET BTS default: HLFSEC-16 [OPTIONS]). If the TCH request for the incoming handover cannot be served within this time frame and TQHO expires in case of incoming MSC-controlled HO.# Limitation of the queuing time for an TCH request due to incoming MSC-controlled handover start: sending of the QUEUING INDICATION (BSC->MSC) stop: .e. This feature foresees a two queue concept. This can decrease the queuing time considerably. WPSPREF.254 the U. Further parameters related to the WPS feature are BSCT11PUB. BSC timer for queuing of handover in WPS queue.discarding of the TCH request from the TCH queue (all cases except TQHO expiry) expiry action: Sending of a HANDOVER FAILURE with cause 'no radio resource available' to the MSC followed by release of the call resources. this timer determines the maximum allowed queuing time for TCH requests due to incoming handover in the ‘public queue’. one queue being used for ordinary subscribers (‘public’) and one for priorized subscribers (‘WPS queue’).. the MSC will attempt another HO REQUEST procedure towards the next target BTS.. The parameter BSCTQHOWPS range: 0. QLPUB. when the BSC receives a HANDOVER REQUEST message from the MSC) is put into a queue due to TCH congestion. BSCTQHOWPS=HLFSEC-16. SEC5=5s which is a special enhancement of the feature ‘queuing’ required by range: 0. LWWPSPRI (see command SET BTS [OPTIONS]). TQHO determines the maximum time the TCH request may remain in the queue to wait for a busy TCH to become idle. As a result.

Acceptable GPRS degradation. this parameter defines. only the decrease of the MST below a particular threshold will lead to a system reaction (i. The upgrade is performed by adding one adjacent timeslot timeslot to the currently used ones (i.Setting the global parameters of the BSC: Attention: Since BR6. all parameters of the previous ‘BSC packages’ were moved below the object BSC and appear in the DBAEM in the SET BSC command. PER30 .e.e. in order to reach the required radio resource allocation in several steps. PER20. when the MST becomes lower than the maximum tolerable degradation of the peak throughput. with a periodicity defined by the parameter UPGRFREQ (see below). Note: As long as the ‘one radio resource a time’ algorithm is implemented it is suggested to set the ACCEPTGDEGR attribute to ‘0’ (no degradation allowed. 19 . the upgrading of radio resources is attempted. in percentage (steps of 10 %. provided that the conditions regarding horizontal allocation and the percentage of idle timeslots are verified (see parameter GASTRTH in command CREATE PTPPKF). Instead. that is: Maximum sustainable throughput (MST) = T_A_CS ∗ (1-BLER) ∗ #TS where: T_A_CS = throughput of the Actual Coding Scheme BLER = actual BLER #TS = number of allocated timeslots to the TBF SET BSC [BASICS] : NAME=BSC:0. The logical group “[BASICS]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands .0 The DBAEM does not group the command parameters into ‘packages’ anymore. As a general rule. Object path name. ACCEPTGDEGR=PER0. An extension to the number of allocated TSs is tried if: T_A_CS ∗ (1-BLER) ∗ #TS < (1. object: range: default: BSC [BASICS] PER0.e. as a ‘downgrading’ of radio resources due to MST criteria is not performed. an increase of the MST will not lead to any system reactions.ACCEPTGDEGR) ∗ PT where: T_A_CS = throughput of the Actual Coding Scheme BLER = actual BLER = peak throughput PT #TS = number of allocated timeslots to the TBF This means that. The maximum sustainable throughput (MST) is defined as the maximum throughput that would be achieved by a given TBF if it was alone on the multislot configuration.. either the BLER or the used CS/MCS coding scheme can change. Moreover. leading to a change in the ‘maximum sustainable throughput’. TCH resources on the Um) is attempted. since the variations in the maximum sustainable throughput can happen very frequently. During a TBF lifetime. PER10. PER90 PER0 A check on the current maximum sustainable throughput is performed periodically. radio resource upgrading always attempted as soon as the upgrading condition is detected). the PCU will send a PDCH_Upgrade_Request message to the TPDC). upgrading of radio resources). the acceptable degradation of packet service throughput (maximum sustainable throughput).. only a decrease of the maximum sustainable throughput is considered. before an upgrading of radio resources (i. due to variations in radio conditions. from 0% to 90%).

object: range: default: BSC [BASICS] ENABLED(1. DISABLED ENABLE(30) (minor) ENABLE(60) (major) ENABLE(90) (critical) A interface via satellite. only one of the mentioned interfaces should be configured as satellite link at the same time. object: range: default: BSC [BASICS] TRUE. see SET BSC [BASICS]) have to be carefully checked as the delay on the lower layers slows down all signaling transactions. If the A interface link is configured as satellite link. BSSAP) and b) the CCS7 layer 2 functions. major and critical QOS alarms for the traffic channels on the A-interface... However. FALSE FALSE AMONTH=ENABLED(30)ENABLE(60)-ENABLED(90). see below) and the Abis interface (see parameter LPDLMSAT in command CREATE/SET BTSM) can be configured as satellite link. the alarm messages UNAVAILABLE AINT TCH THRESHOLD MINOR. determines the state and the threshold values for the minor.AISAT=FALSE. Although multiple satellite links are not officially tested and released. Note: Also the Asub interface (parameter ASUBISAT. If the number of unavailable A-interface traffic channels exceeds the entered threshold.it is up to the operator to follow this rule. BSCT8 etc. the generally higher signal delay must be particularly considered by a) the higher layers on the CCS7 link (e. the BSC command interpreter and DBAEM do not perform any checks to avoid multiple satellite links . It might be necessary to extend selected timers to higher values to avoid undesired effects. this attribute indicates whether the A interface resp. because multiple satellite links within a BSS may cause an overall message and procedure delay that might lead to expiry of procedure supervision timers that are normally adapted to the propagation delay of terrestrial signalling links or at least to only one satellite link in the path. The entered threshold value represents the percentage of unavailable traffic channels on the Ainterface. The threshold values can only be assigned if the previous attribute is set to ENABLE. 20 . MAJOR or CRITICAL (error ID 242. SS7 link is realized via satellite link (TRUE) or not (FALSE). 243 and 244) are output. b) If the A interface is realized via satellite link the CCS7 error correction method must be set to 'preventive cyclic retransmission error correction' (see CREATE SS7L.100). BSCT7.g. A-interface TCH monitoring thresholds. Setting AISAT=TRUE has the following consequences: a) BSSAP timers (e.g. parameter ERRCORMTD).

DISABLED ENABLE(30) (minor) ENABLE(60) (major) ENABLE(90) (critical) ASUBENCAP=FALSE. when ASCIONECHMDL is set to FALSE (1. object: range: default: BSC [BASICS] TRUE. FALSE FALSE ASMONTH=ENABLED(30)ENABLE(60)-ENABLED(90).e. 21 . so that in the end only one ordinary ‘twoway’ TCH is occupied by the service subscriber (“1 channel mode”). For further details please refer to the explanation provided for the parameter WMOD in the command CREATE PCMS.ASCIONECHMDL=FALSE. for the called service subscribers basically only one downlink channel (ASCI common TCH) is provided.100). When a VGCS voice group call is set up (one dispatcher and several other called service subscribers in the group call area). a service subscriber has the possibility to request an uplink channel to transmit speech to the other group call partners by pressing the PTT (push to talk) button on the ASCI phone. the BSC assigns a completely new TCH to the subscriber in addition to the alredy existing downlink TCH .5 channel model’ is enabled. FALSE FALSE ASCI one channel model. A-interface signaling monitoring thresholds. this parameter is only relevant if the feature ASCI is enabled (see parameter ASCISER in command SET BTS [CCCH]) and determines whether the ASCI ‘one channel model’ is enabled (TRUE) or disabled (FALSE) for ASCI VGCS goup calls. object: range: default: BSC [BASICS] ENABLED(1. Asub enhanced capacity allowed. i. The entered threshold value represents the percentage of unavailable SS7 links on the A interface. the alarm messages UNAVAILABLE SS7 LINK THRESHOLD MINOR. the BSC only assigns an uplink channel to the already existing downlink channel. MAJOR or CRITICAL (error ID 236..thus the service subscriber occupies ‘one and a half’ TCHs (therefore called “1. The threshold values can only be assigned if the previous attribute is set to ENABLE. they can only listen to the dispatcher. 238 and 241) are output. Single trunk mode (ASUBENCAP=TRUE) means that all physical ports (A and B ports) of a QTLP can be used for the connection of one TRAU.5 channel mode”). major and critical QOS alarms for the SS7 signaling channels on the A-interface. the following happens: when the service subscriber requests an uplink TCH by pressing the PTT button in order to transmit speech. Setting ASCIONECHMDL to TRUE guarantees a more economic utilization of the radio TCH resources: when the service subscriber requests an uplink TCH via the PTT button in order to transmit speech. determines the state and the threshold values for the minor. However. object: range: default: BSC [BASICS] TRUE. In this situation. FALSE means that the standard ‘1. this attribute indicates whether the creation of PCMS objects in single trunk mode is allowed.5 channel mode). If the number of unavailable SS7 links exceeds the entered threshold.

22 . The effect is the same as described above .. . see SET BSC [BASICS]) have to be carefully checked as the delay on the lower layers slows down all signaling transactions. FALSE TRUE The extension of T200 ensures that the higher signal delay on the link does not lead to unnecessary retransmission of LAPD layer 2 frames. Further parameters relevant for BSC overload handling: . only one of the mentioned interfaces should be configured as satellite link at the same time. c) If the Asub interface is realized via satellite link the CCS7 error correction method must be set to 'preventive cyclic retransmission error correction' (see CREATE SS7L.g. the generally higher signal delay must be particularly taken into account by the LAPD layer 2 functions of the TRAU O&M link (LPDLS) and b) the higher layers on the CCS7 link (e. because multiple satellite links within a BSS may cause an overall message and procedure delay that might lead to expiry of procedure supervision timers that are normally adapted to the propagation delay of terrestrial signalling links or at least to only one satellite link in the path. However. the BSC command interpreter and DBAEM do not perform any checks to avoid multiple satellite links . As MSC.OVLSTTHR and OVLENTHR (SET BSC [BASICS]. see below). Setting ASUBISAT to TRUE has the following consequences: a) The LAPD timer T200 (waiting timers for LAPD acknowledgement frames) as well as the associated window sizes (the 'window size' is simply the number of I-frames that may be sent without any acknowledgement from the opposite side) are automatically extended according to the following table: BSCOVLH=TRUE. object: range: default: BSC [BASICS] TRUE. b) BSSAP timers (e. see above) and the Abis interface (see parameter LPDLMSAT in command CREATE/SET BTSM) can be configured as satellite link. determines whether BSC overload handling is enabled or not. BSC and BTS overload handling are closely interwoven. BSSAP) and c) the CCS7 layer 2 functions. For further details about the BSC overload regulation please refer to the section “BSC. If the Asub interface link is configured as satellite link. while the extension of the window size avoids further delays due to additional acknowledgement waiting times. the overload conditions and traffic reduction mechanisms are explained in an own chapter that comprises all possible scenarios of overload and overload handling as well as the references to the relevant parameters. object: range: default: BSC [BASICS] TRUE. Notes: . this attribute indicates whether the Asub resp. parameter ERRCORMTD). BTS and MSC overload Handling” in the appendix of this document.it is up to the operator to follow this rule.The satellite mode of the Asub link has to be activated in the TRAU as well.Also the A interface (parameter AISAT. It might be necessary to extend selected timers to higher values to avoid undesired effects. This is done by the parameter ASUBLPDLSAT in the command SET LPDLS TEITSL (at the TRAU LMT).BSCT18 and BSCT17 (see command SET BSC [TIMER]) . LPDLS is realized via satellite link (TRUE) or not (FALSE). Although multiple satellite links are not officially tested and released.just for the opposite direction.ASUBISAT=FALSE. BSCT7. FALSE FALSE Asub LAPD channel via satellite. BSC overload handling. BSCT8 etc.g.

as no mobile supports this feature at the moment. object: range: default: BSC [BASICS] TRUE. From the BSC side. the overload conditions and traffic reduction mechanisms are explained in an own chapter that comprises all possible scenarios of overload and overload handling as well as the references to the relevant parameters. or to PH2_CBC to indicate that the connected CBC supports the new Channel Indicator parameter value.BTSOVLH=TRUE. this means that on the A-bis interface the EXTENDED channel is not implemented. this parameter specifies the format of the circuit identification code (CIC). CICFM=GSM. NOTSTRUCT GSM CITASUP=FALSE. this parameter defines the type of Cell Broadcast Center connected to the BSC. BTS and MSC overload Handling” in the appendix of this document. object: range: default: BSC [BASICS] GSM. For further details about the BTS overload regulation please refer to the section “BSC. Parameter cancelled in BR8. BSC and BTS overload handling are closely interwoven. this flag determines whether Channel Change Notication (CCN) is enabled in the BSC (TRUE) or not (FALSE). The two possible settings for this parameter are BASIC (value = 0) or EXTENDED (value = 1). This parameter has an influence on the allowed value range for the high CIC number (see parameter HCICN (CREATE PCMA)). FALSE TRUE CBCPH = PH1_CBC. which identifies the channel on which the message has to be broadcast. but only the BASIC channel can be specified in the channel_indicator field from the CBC operator. Channel change notification active. this parameter is relevant for the feature ‚Location Based Services’ and represents the flag to enable the transmission of the Timing Advance (TA) in the COMPLETE LAYER3 INFO (which the BSC sends to the MSC during any connection setup) in addition to the Cell Identifier (CI). In this sense the RC/LMT operator can set the database flag CBCPH to PH1_CBC to indicate that the connected CBC uses the old interface (< BR6. As MSC. The setting of the CBCPH is related to the parameter “Channel Indicator”. determines whether BTS overload handling is enabled or not. object: range: default: BSC [BASICS] TRUE. CIC format. PH2_CBC PH1_CBC CCHANTFACT=FALSE. Cell ID and Timing Advance Support.0). So the customer can choose a CBC centre implementing the new interface (including the channel_indicator parameter and setting theCBC phase = 2). object: range: default: BSC [BASICS] TRUE. the old CBC interface (without Channel_Indicator parameter) is still supported. FALSE FALSE BTS overload handling. object: range: default: BSC [BASICS] PH1_CBC. FALSE FALSE CPOLICY 23 . The support of the EXTENDED channel for the Mobile Stations is optional.0 due to multi-layer service concept. Note: The support of the ‘Channel Indicator’ has been implemented only at CBC-BSC interface level. Further parameters relevant for BTS overload handling: BSCT18 and BSCT17 (see command SET BSC [TIMER]) CBC phase.

24 . As the coding schemes CS-3 and CS-4 require two concatenated PCU frames. two 16kbit/s TCHs on the Abis interface are necessary for each radio interface timeslot (PDCH).05 kbit/s 13. while ‘Data Coding’ represents the coding of the user data to be transmitted).depending on the current radio conditions . The basic principle is: the better the radio interface quality (defined by C/I . a GPRS coding scheme ‘link adaptation’ is applied. depending on the current radio conditions (defined by C/I in dB). FALSE FALSE GSM 03.Carrier/Interference).64 rcommended value: TRUE CS3 and CS4 support. GPRS Coding scheme CS-1 CS-2 CS-3 CS-4 maximum gross data rate 9.6 kbit/s 21. the GPRS coding scheme link adaptation.4 kbit/s 15. of Concatenated PCU Frames 1 (max. good radio conditions poor radio conditions Channel Coding Channel Coding Data Coding Data Coding To make sure that. the higher the available bandwidth (bitrate) for the user data coding and the smaller the bandwidth (bitrate) for channel coding and vice versa (‘Channel Coding’ is the term that represents the radio transmission error protection overhead. the higher data throughput of CS-3 and CS-4 is achieved by a smaller channel coding portion within the radio TCH. this parameter allows to enable or disable the feature GPRS Coding Scheme 3 and Coding Scheme 4 generally in the BSC. 488 payload bits) 2 (max. 488 payload bits) 2 (max.CSCH3CSCH4SUP=TRUE. the best possible GPRS coding scheme is used. In detail.4 kbit/s Similar to the AMR speech coding. object: range: default: reference: BSC [BASICS] TRUE. where . The coding schemes 3 and 4 allow a considerably higher GPRS data throughput than the previously available coding schemes 1 and 2. 488 payload bits) Consequently. which features the permanent supervision of the C/I radio conditions and the adaptation of the GPRS coding scheme to these conditions to achieve the best possible throughput. the relation of coding scheme and the required number of concatenated PCU frames is displayed in the following table: GPRS coding scheme CS-1 CS-2 CS-3 CS-4 Radio Block Size in Bits for DL/UL 181 268 312 428 No. The same parameter is also available in the PTPPKF object where it can be used to enable/disable CS3/CS4 individually per BTS (see parameter CSCH3CSCH4SUP in command CREATE PTPPKF). 216 payload bits) 2 (max. The following gross data rates according to the selected coding scheme can be achieved by the different coding schemes depending on C/I. which can also be regarded as ‘coding scheme upgrade’ and ‘coding scheme downgrade’ also might cause the seizure (for coding scheme upgrade) or/and release (for coding scheme downgrade) of an additional Abis TCH.a better speech quality is achieved by providing the smallest possible channel coding portion and the biggest possible speech coding portion.

the BSC considers all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) as ‘busy’ (like any other TCH currently seized by a CS call) in any case.DGRSTRGY Parameter moved to BTS object in BR8. this flag enables/disables the functionality that considers the setting of the parameter DGRSTRGY (see command CREATE BTS [BASICS]) for the traffic load calculation. object: range: default: BSC [BASICS] ENABLED. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE). If DLAPDOVL=TRUE. DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST. FALSE TRUE EENHDTMSUP=DISABLED.0! moved to BTS object (see CREATE BTS [BASICS]). b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i. object: range: default: BSC [BASICS] ENABLED. then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. as defined in 3GPP Release 6. Enable Enhanced DTM Support. MSC and BTS Overload handling’ in the appendix of this document.Abis TCH load calculation as follows: a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i. The parameters relevant for BTSE LAPD overload handling are FLAPDOVLTH. DISABLED DISABLED DLAPDOVL=TRUE. no matter what the setting of DGRSTRGY is. Note: This functionality is available via patch in BR8. object: range: default: BSC [BASICS] TRUE.radio TCH load calculation and .e. SLAPDOVLTH and LAPDOVLT (see CREATE BTSM).e. then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. this flag enables/disables the “Enhanced DTM Establish” mode. Downlink LAPD Overload. it sends the O&M message LAPD OVERLOAD towards the BSC.0 starting from TDPC load 32 (please see release documentation for details). DOWNGRADE_GPRS_ONLY. the BSC starts traffic reduction measures as described in the section ‘BTS overload’ in the chapter ‘BSC. the BSC considers the setting of the DGRSTRGY parameter in the . If DGRSTRGYBCNT is set to DISABLED. this parameter allows to enable or disable the procedure that detects the downlink LAPD overload. If DGRSTRGYBCNT is set to ENABLED. 25 . DISABLED DISABLED Downgrade strategy busy counting. DGRSTRGYBCNT= DISABLED. If the BTSE has detected an overload situation on the LAPD link based on the LAPD load thresholds SLAPDOVLTH (see command CREATE BTSM).

The decision. ‘Inter-BSC SDCCH handover’ consists of 1) Inter-BSC Directed Retry (see param. When the BSC receives a CIPHER MODE COMMAND from the MSC. object: default: BSC [BASICS] encalg1=NOENCR encalg2=GSMV1 encalg3. NOENCR means ‘no ciphering’. if both are allowed) for the CIPHERING MODE COMMAND towards the BTS.10=NOCONFIG 26 . Supported encryption algorithms. the BSC makes the decision for the cipher algorithm to be used by matching the list of allowed cipher algorithms as indicated in the CIPHER MODE COMMAND and the ones defined in the parameter ENCALSUP and selects the best (safest) algorithm (A5/1 is the ‘stronger’ and safer algorithm and is therefore preferred against A5/2. . FR or HR) is finally assigned to a TCH request is made by the BSC on the basis of a) the channel requirement provided by the MS in the SETUP message. FALSE FALSE EHRACTAMR Parameter was moved from BSC object to BTS object in BR8. It is up to the operator to take care that the setting of ENCALSUP matches to the cipher algorithms that are supported by the used BTS SW loads (see BTS SW Release Documentation for details).. which kind of TCH (EFR. EISDCCHHO=ENABLE. the setting of EFRSUPP has no effect on AMR. DISABLE ENABLE ENCALSUP=NOENCR& GSMV1&GSMV2. b) the MSCs capability to support the requested speech versions (which results in a corresponding contents of the ASSIGNMENT REQUEST /HANDOVER REQUEST message which the MSC sends to the BSC) and c) the current occupation of TCH resources in the affected BTS and TCH allocation strategy used by the BSC. Enable HR activation for AMR calls . this parameter determines the algorithms for the radio interface ciphering supported by the BSC.moved to BTS object in BR8. Notes: . Inter SDCCH handover enabled. GSMV1 represents the ciphering algorithm A5/1.0. Setting EISDCCHHO to ‘disable’ has the following results: a) the BSC is prevented from sending HANDOVER REQUIRED messages for ongoing SDCCH connections to the MSC and b) the BSC drops all target cells (received in the HCI) that do not belong to the own area. this parameter determines whether the assignment of enhanced full rate TCHs is generally allowed for the BSC or not.0! Enhanced full rate supported. GSMV2 represents the ciphering algorithm A5/2.EFRSUPP=FALSE. which enables/disables both standard half rate speech (HR version 1) and AMR half rate (HR version 3). object: range: default: BSC [BASICS] ENABLE. object: range: default: BSC [BASICS] TRUE. determines whether ‘Inter BSC SDCCH handover’ is enabled.As opposed to HRSPEECH. ENFORCHO) and 2) Inter-BSC SDCCH-SDCCH-Handover (see parameter IERCHOSDCCH in command SET HAND [BASICS]).

if not possible then 3) (WPS) queuing 27 . if not possible then 2) directed retry. this parameter determines whether the BSC may send a FORCED HANDOVER REQUEST message for running SDCCH connections to the BTS.2. DISABLE ENABLE Enable forced intra-cell HO. Both kinds of handover (a and b) are triggered and executed exclusively by the BSC: when the described copnditions are fulfilled. A ‘Directed Retry’ procedure is performed if a MOC or an MTC is attempted in a cell for which a) no idle TCH is available due to radio TCH congestion or b) no Abis TCH is available in the Abis TCH pool associated to the serving BTSM. parameters FHORLMO and TIMERFHO and section 2. see below) must be set in addition.6). which in turn sends HANDOVER CONDITION INDICATION messages with the cause ‘forced’.e. The HCI messages contain a list of target cells that the BTS has determined by evaluating the measurement reports sent uplink by the MS during the SDCCH phase. If there are not enough adjacent radio TCHs available when a request for multislot call (HSCSD or GPRS) is received a forced intracell handover is performed which re-orders the current timeslot seizure in such a way that a sufficient number of adjacent timeslots is available to satisfy the multislot call request to the best possible extent. the handover to the preferred layer is performed. The BTS is not involved in the handover initiation. the process of the target cell list generation and the target cell ranking is exactly the same like for a directed retry – in both cases the forced handover offset (FHORLMO) is applied. sends the ‘forced handover request’ message to the BTS. object: range: default: BSC [BASICS] TRUE. FALSE TRUE Default value changed in BR8. Forced handover enabled.ENFOIAHO=TRUE. no HANDOVER CONDITION INDICATION is sent from BTS to BSC. If a call is set up on a TRX that belongs to service layer different from the ‘preferred’ one. this parameter enables the procedures a) ‘Forced Intracell Handover due to multislot calls’ and b) ‘Forced Handover due to preferred service layer’. the BSC periodically tries to hand over the established call to a TRX of a layer with higher SLL priority. In case of ‘Forced handover due to Preemption’. However. This means that ENFOIAHO should be set to TRUE.. b) Moreover. During this procedure the BSC. Notes: . If an idle TCH is found during this check.If a CS call request is received in a congested cell. object: range: default: BSC [BASICS] ENABLE. having received the ASSREQ from the MSC. i. it must be set to TRUE if the feature ‘Multilayer Service Support’ (see command SET BTS [SEVICE]) is applied. For the BTS. the BSC sends the FORCED HO REQ to the BTS for the call which is to be preempted.1. the resulting signalling transaction rather corresponds to that of a normal handover procedure (with the appropriate cause values) than that of a directed retry.0! ENFORCHO=ENABLE. A successful ‘Directed Retry’ results in the assignment of a TCH in the best adjacent cell. the BSC tries to satisfy the TCH request in the following sequence: 1) preemption of a low priority CS call. Note: For case b) the maintenance bit 12 (MNTBMASK=BIT12. This message is used for either for ‘Directed Retry’ or for the procedure ‘Forced handover due to Preemption’ (see parameter EPRE in command SET BTS [OPTIONS]). (-> see also command CREATE ADJC. if either a) GPRS or HSCSD is used in the BSC (see command CREATE PTPPKF (for (E)GPRS) and parameter ENHSCSD (see below)). the BSC just activates the target channels and sends the associated ASSIGNMENT COMMANDs to the MSs.

If this is not the case the preempted call is immediately released ! .e. .In hierarchical cell structures the ranking of the target cells in the HCI sent as a result of the ‘forced handover request’ is performed according to the setting of the parameter HIERF (see SET HAND).The setting ENFORCHO=FALSE does not only prevent BSCinternal and outgoing Inter-BSC directed retries. the BSC allocates an SDCCH and the directed retry can be performed.Setting this parameter to ‘enable’ only activates the Directed Retry controlled by the BSC. if ENFORCHO is set to ENABLE. . it also prevents incoming Inter-BSC directed retries and incoming handovers due to preemption: When the BSC receives a HANDOVER REQUEST message with the cause values ‘directed retry’ or ‘preemption’. 28 . Note for Forced handover due to O&M: Forced handover due to O&M (initiated by the SHUTDOWN command is completely independent of any database flag. . For further details pleas refer to the parameter BTSHSCSD (see command SET BTS [BASICS]). Please refer to the parameters EPRE (for preemption) and EQ (for (WPS) queueing) in command SET BTS [OPTIONS] and to parameter DGRSTRGY (for multislot call downgrade) in command SET BTS [BASICS]. . .the MS’s multichannel requirement in a neighbour cell. the forced handoverm due to preemption is only attempted. If in this case no TCH is available for the IMMEDIATE ASSIGNMENT procedure. i.If the feature ‘Preemption’ is enabled. it rejects the attempt by sending HANDOVER FAILURE with cause ‘Protocol error between BSS and MSC’.Directed retry also works if direct TCH assignment (see parameter DIRTCHASS in command SET BTS [OPTIONS]) is enabled.If an MS tries to set up an HSCSD call in a cell where HSCSD is disabled. directed retry to target cells belonging to the same BSC. the BSC also starts a directed retry procedure to satisfy .if possible . If Inter-BSC Directed Retry shall be enabled the flag EISDCCHHO (see above) has to be set to 'enable' in addition.4) downgrade of multislot calls (GPRS/HSCSD) may be periodically attempted in parallel and queued calls can be served when down grade is successfully completed.

Handover: In symmetric mode individual signal level and quality reporting for each used channel is applied. For transparent HSCSD connections the BSC is not allowed to change the user data rate. The downlink based asymmetry allows the use of a receive rate higher than the transmission rate and is thus very typical for Internet applications. intracell handover is possible only with cause 'complete to inner' or 'inner to complete'. The BSC may alter the number of timeslots used for the connection and the channel codings when handing the connection over to the new channels. Connection modes: There are 2 types of multislot connections: symmetric and asymmetric ones. In symmetric mode all secondary TCHs are bi-directional (UL and DL) and in asymmetric mode the secondary channels are only uni-directional (DL) TCHs or can be a mix of bi-directional and uni-directional TCHs (example: One "HSCSD 3+2" call consists of: one main TCH. Each HSCSD connection consists of 1 main TCH which carries the main signalling (both FACCH and SACCH) and further 1. All kinds of inter-cell handovers are supported. it must be explicitly enabled for each BTS (see CREATE BTS [BASICS]: BTSHSCSD). one secondary bidirectional TCH and one secondary uni-directional TCH). The change of the air resource allocation is done by the BSC using ‘service level upgrading and downgrading' procedures.6) kbit/s (multislot connections). All TCHs used in an HSCSD connection are handed over simultaneously. this parameter specifies whether the feature ‘High Speed Circuit Switched Data (HSCSD)’ is enabled for the BSC or not. For non-transparent calls the BSC is also allowed to downgrade the user rate to a lower value.ENHSCSD=FALSE. Notes: 1) This parameter enables HSCSD for the BSC base only. 2) As a mandatory precondition for HSCSD the features ‘early classmark sending’ (see SET BTS [OPTIONS]:EARCLM) and ‘pooling’ (see parameter ENPOOL) must be enabled! Principle: HSCSD is a feature which allows the ‘bunching’ of up to 4 consecutive radio timeslots for data connections of up to 38.4 (= 4 x 9. It may alter the number of TCH/F as well as the channel codings used for the connection. but it may alter the number of TCHs used by the connection (in this case the data rate per TCH changes). handover and/or the maintenance of the service quality. The asymmetric mode is only possible for nontransparent data connections. The data rate depends on the bearer capability requested by the MS and the negotiation result between MS and MSC. Resource allocation: The BSC is responsible for the flexible air resource allocation. FALSE FALSE Enable HSCSD. Reasons for the change of the resource allocation may be either the lack of radio resources. however. 29 . For an asymmetric HSCSD configuration individual signal level and quality reporting is used for the main TCH. In both symmetric and asymmetric HSCSD configuration the neighbour cell measurements are reported on each uplink channel used..3 secondary TCHs. object: range: default: BSC [BASICS] TRUE. To activate it. The quality measurements reported on the main channel are based on the worst quality measured on the main and the unidirectional downlink timeslots used. All radio timeslots used for one connection are FR timeslots located on the same TRX and use the same frequency hopping mode and the same TSC.

FALSE TRUE Default value changed in BR8. As long as the mentioned condition is not fulfilled the intracell handovers due to enhanced pairing are not triggered. no. A DR TCH can assume the following usage states: .a DR TCH is in usage state “idle” if none of the subslots is seized by a call. of TCH configured in the Abis pool ∗ 100 < 100% . This threshold is based on the parameter ABISHRACTTHR (see command CREATE BTSM).the DR TCH is in usage state “busy” if both subslots are seized either by two HR calls or one FR call. b) Enhanced pairing due to BTSM Abis TCH load is triggered if the percentage of dual rate TCHs or full rate TCHs in a BTSM Abis pool with usage state “idle” has dropped below a definable threshold.EPA=FALSE. please refer to the description of parameter ABISHRATTHR). of Abis pool TCH in usage state ‚idle’ no. of radio TCH in usage state ‚idle’ no. Enhanced pairing intracell handovers are triggered if the following traffic load condition is fulfilled (for further details about the meaning of single terms of this formula. the BSC uses a cyclic process which is determined by the “Resource Allocation Timer“ (RR timer) which is fixed to 400ms: every 400 ms the BSC 30 . with another HR call. In other words: the feature transfers HR calls that currently occupy one HR subslot of a DR TCH (while the other subslot is still idle) in such a way that as many HR calls as possible share one Dual Rate TCH with another HR call. that carry only one HR call. separately for every subarea (primary/complementary). please refer to the description of parameter EPAT1). enhanced pairing intracell handovers are automatically performed by the BSC by simply activating the appropriate TCHs and by sending an ASSIGNMENT COMMAND with the new HR TCH data to the MS. For the detection of the aforementioned condition.the DR TCH is in usage state “active” if one of the two subslots (0 or 1) is occupied by a HR call. . object: range: default: BSC [BASICS] TRUE. no. The enhanced pairing intracell handover is controlled exclusively by the BSC and triggered by two different conditions: a) Enhanced pairing due to Um radio TCH load is triggered if the percentage of dual rate TCHs or full rate TCHs in the BTS in usage state “idle” has dropped below a definable threshold. “Enhanced Pairing” implies automatically triggered forced intracell handovers that fill up dual rate TCHs. This threshold is based on the parameters EPAT1 and EPAT2 (see command CREATE BTS [BASICS]). of configured radio TCH ∗ 100 < EPAT1[%] Note: Interworking of ‘Service Dependent Channel Allocation’ with traffic load calculation The percentage calculation done for the Enhanced Pairing is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types.ABISHRACTTHR[%] When the BSC detects TCHs in usage state “active” while at least one of the aforementioned condition is fulfilled. .0! Enable enhanced pairing of HR calls. Please refer to the command SET BTS [SERVICE] for further explanations. this parameter enables the feature ‘enhanced pairing of TCH/H’. Enhanced pairing intracell handovers are triggered if the following traffic load condition is fulfilled (for further details about the meaning of single terms of this formula.

0) is now replaced by a semipermanent mapping pattern.and Asubtimeslots (represented by the parameter TRANMTX which was valid up to BR4. Moreover. i. If the pooling feature is enabled the available A-interface timeslots are classified by a ‘pooling type’. AP ERROR INDICATION. Error reactions.The value FERMAINT can be used only for Processing Failure Events. Thus it is possible to assign different speech and data coding types to different TRAU shelves. When ERRACT is set to one alarm priority for a specific alarm event type all alarms of lower and equal priority are ignored for this event type. FALSE FALSE 31 . this parameter indicates whether the ‘TSLA pooling’ feature is activated on the BSC side (‘enabling flag’). if the TCH load condition is fulfilled. ‘TSLA pooling’ must be activated if HSCSD (see parameter ENHSCSD) is used on this BSC. please refer the corresponding tables included in the HW-FW Crossreference List in the SBS Release Documentation!).and Asub-! A TCH pool for multislot connections must map all Asub-timeslots used for a HSCSD-call to a single A-interface timeslot! Thus the previously rigid mapping pattern of A. which depends on the number and type of pools configured.g. this attribute is only relevant if HSCSD is enabled (ENHSCSD=TRUE). Thus FERMAINT works as a 'negative' filter. this parameter enables or disables the feature EDGE in the BSC. EDGE support. ERRACT=NOFILTERNOFILTER-NOFILTERNOFILTER-NOFILTER. HSCSD calls themselves can never be preempted. Setting the PROC field to FERMAINT enables the output of certain call processing alarm messages which are normally suppressed (e. Thus the BSC can separately manage the available resources e.Attention: the filter setting defined by ERRACT is not only relevant for spontaneous alarm output but also for the alarm output as reaction to the command GET ACTIVEALARMS BSC! .e. The different values for the pooling type are predefined by GSM and represent a certain combination of different ‘supported coding types’ for speech and data (see table at command CREATE PCMA and SET TSLA). it takes at the maximum 400ms until the unpaired HR calls are rearranged by enhanced pairing intracell handover. parameter ALLCRIT). Only the basic mapping principle can be selected initially (see command CREATE TRAU. for details. object: range: BSC [BASICS] CRITICAL MAJOR MINOR WARNING NOFILTER FERMAINT NOFILTER default: ESUP=FALSE. object: range: default: BSC [BASICS] TRUE. This means that. object: range: default: BSC [BASICS] TRUE. Enable preemption for HSCSD requests. Notes: . this parameter determines the output filters for different alarm event types. HSCSD calls may preempt other calls. the pooling types that include the support of more advanced features must be assigned to TRAU shelves equipped with the appropriate TRAC versions (Mixing of TRAC versions within one TRAU shelf is only allowed in specific configurations. DISABLED DISABLED checks if the TCH load condition for enhanced pairing is fulfilled and if there are some ongoing HR calls to be paired. Enable pooling. MESSAGE OUT OF SEQUENCE etc. The five entered subattributes represent alarm messages in the alarm event types CommunicationQualityOfService-Processing-Equipment-Environment.g. the pooling type must be adapted to the version and capabilities of the used TRAC-HW in the TRAU.EPOOL=TRUE. Attention: Pooling also affects the mapping of timeslots between the A. If it is set to TRUE. object: range: default: BSC [BASICS] ENABLED. FALSE FALSE EPREHSCSD=DISABLED. for ordinary speech calls and for high speed data connections. Setting this parameter is a precondition before EDGE services can finally be enabled on cell level (EEDGE in object PTPPKF).) in order to allow a closer look on the grade of service in the cell for maintenance purposes.

EUSCNCRESEL=FALSE. <NULL> FALSE Enable UMTS sufficient coverage network controlled cell reselection. This means that.e. only if EUSDCHO is enabled.e. An UMTS SDCCH HO can be 1) Inter-System Directed Retry (see param. this parameter is only relevant if the parameter EUHO (see command SET HAND [BASICS]) is set to TRUE and enables or disables the handovers of calls that are currently on an SDCCH towards external UMTS FDD or TDD neighbour cells in the BSC. i. a FORCED HANDOVER REQUEST message was triggered towards the BTS if the new IE ‘Service Handover Information’ in the ASSIGNMENT REQUEST message is set to "Handover to either UTRAN or cdma2000 should be performed" and the resulting INTERCELL HO CONDITION INDICATION message contains an UTRAN target cell. The status of this flag is also sent to the BTS during the database alignment procedure. Further relevant parameters are GFDDREPQTY. With some restrictions. For the speed-sensitive variant of this feature please see parameter EUMSSNCRESEL in command CREATE PTPPKF. b) the BTS inserts. USECNONCRESEL and USRSCPNCRESEL (see command CREATE ADJC3G). a forced handover was triggered and the resulting INTERCELL HANDOVER CONDITION INDICATION message contains an UMTS FDD target cell or 2) Service-Based Directed-Retry. GTDDMURREP. this parameter enables or disables the 'Network Controlled Cell Reselection from GSM/GPRS due to UMTS sufficient Coverage' for GPRS connections. object: range: default: BSC [BASICS] TRUE. if available. object: range: default: BSC [BASICS] TRUE. EUSDCHO is a kind of equivalent to the parameter EISDCCHHO (see above). GFDDMURREP. if an INTERCELL HANDOVER CONDITION INDICATION message that contains an UMTS FDD target cell (see commands CREATE TGTFDD and CREATE ADJC3G) or an UMTS TDD target cell (command CREATE TGTTDD) was received from the BTS for an activated SDCCH. For further details about the criterion ‘sufficient coverage’ please refer to the corresponding handover parameter EUSCHO (command SET HAND). ENFORCHO). the 3G target cells into the target cell list within the INTERCELL HANDOVER CONDITION INDICATION message (as also within the BTS the EUSDCCHHO flag is managed and checked) c) the BSC permits 3G neighbour cells as target cells to be sent to the MSC within the HANDOVER REQUIRED message for ongoing SDCCH connections. FALSE FALSE EUSDCHO=FALSE. This is done by the optional IE ‘Service Handover Information’ which is included in the FORCED HANDOVER REQUEST message. FALSE. i. Enable UMTS SDCCH handover. GMICROCU. 32 . Setting EUSDCCHHO to TRUE has the following results: a) the BSC is explicitly allows the BTS to include 3G target cells within the INTERCELL HANDOVER CONDITION INDICATION message. TFAILNCU (see command CREATE PTPPKF). the BSC forwards a HANDOVER REQUIRED message to the MSC.

Synchronous handover (cells finely synchronized): In case of synchronous HO the BSC activates the TCH in the target cell by a CHANNEL ACTIVATION message with the IE ‘activation type: related to synchronous handover’. it starts the timer T3124 on transmission of the first HO_ACCESS message and repeats the transmission until it receives the PHYSICAL INFO.HOSYNC=NOSYNC. Therefore it should be applied where possible as it speeds up the handover procedure and thus reduces the ‘speech gap’ that can occur during the handover procedure.10 HRSPEECH=TRUE. Note: The GSM calls the handover mode described above “ handover between finely synchronized cells ”.e. The HANDOVER COMMAND sent by the BSC then contains the “ Synchronization Indication: synchronized “.08 GSM 05. This message contains the actual timing advance value which the new BTS derives from the delay of the HO_ACCESS messages received from the MS. . 33 . The difference between the both handover procedure is the following: Asynchronous handover (cells not synchronized): In case of (normal) asynchronous HO the BSC activates the TCH in the target cell by a CHANNEL ACTIVATION message with the IE ‘activation type: related to asynchronous handover’. When the MS accesses the target cell after receipt of the HO CMD. The status of this flag determines whether the BSC allows the assignment of an HR TCH if the ASS REQ contains a corresponding ‘preferred channel type’.Handover between pseudo-synchronized cells . The MS falls back to the old TCH when T3124 expires or when the layer-2 connection setup fails. i. In addition to this mode.Handover between pre-synchronized cells Both variants are not supported by the the Siemens BSS. A fallback to the to the old TCH is only possible if the MS fails to set up the layer-2 connection. of course. No PHYS INFO is sent to the MS. FALSE FALSE Handover synchronicity. The synchronous handover is faster than the asynchronous one. When the PHYS INFO is received the MS stops T3124 and establishes the layer-2 connection on the new FACCH by sending the SABM. the appropriate TCH types (see CREATE CHAN. Synchronized handover is possible between cells belonging to the same site (intercell handover from one sector to the neighbour sector). SYNC NONSYNC GSM 04. Half rate speech. object: range: default: BSC [BASICS] TRUE. For the general TCH allocation decision process of the BSC see note in parameter EFRSUPP.g. the GSM defines two additional handover modes: .If HRSPEECH is set to FALSE. object: range: default: reference: BSC [BASICS] NONSYNC. this also automatically disables the features ‘AMR Compression Handover’ (see parameter EADVCMPDCMHO in command SET HAND).The flag HRSPEECH enables/disables both standard half rate speech (HR version 1) and AMR half rate (HR version 3). this parameter specifies whether the feature ‘Half Rate Speech’ is generally enabled for the BSC or not. if HRSPEECH=FALSE. Notes: . To assign a HR TCH. When the MS accesses the target cell after receipt of the HO CMD. parameter CHTYPE) have to be configured for the BTSs. this parameter specifies whether the handover is ‘synchronized’ or ‘non-synchronized’. In the HANDOVER COMMAND the BSC sets the ‘Synchronization Indication’ IE to the value ‘non-synchronized’. handover). neither HR version 1 nor AMR HR will be assigned to any call or any other incoming TCH request (e. it transmits 4 consecutive HO_ACCESS messages and immediately establishes the layer-2 connection on the new FACCH by sending the SABM after that.

LCSNSSC=FALSE.LCSMONTH= ENABLED(30)-ENABLE(60)ENABLED(90). Maximum LAPDm number.. ongoing calls are handed over to other TCHs within the cell to provide adjacent TCHs to an incoming HSCSD call request) . object: range: default: BSC [BASICS] 5. Maximum number of forced intracell handovers. the BSC supports the NSS centric solution and all the BSS requests are rejected.. on the contrary if it is set to FALSE the BSC support the BSS centric request and the NSS centric are rejected. object: range: default: BSC [BASICS] 1. this attribute controls the maximum number of LAPDm frames on which a layer 3 (GTTP) message can be segmented into and be sent on the main DCCH. not put into service by the network provider). MAFIRACHO=2. If the number of failed consecutive CHAN activations on one Abis timeslot (TSLB) exceeds this threshold. FALSE FALSE MADGRLV=2.g.e. i.. ENFOIAHO=TRUE) and determines the maximum number of forced intracell handovers due to HSCSD calls (i.. an alarm on all configured SUBTSLB objects (max 4) is emitted. if the value is set to 1 the threshold value is 4 and so on. The configured threshold value is multiplied by 4.. this attribute is only relevant if HSCSD and forced HSCSD forced intracell handover intracell handover is enabled (ENHSCSD=TRUE.3 2 MAXLAPDMN=5. object: range: default: BSC [BASICS] TRUE. The threshold is the percentage between ‚out of service’ SS7S on equipped SS7S. object: range: default: BSC [BASICS] 1.100). The threshold values can be assigned only when the flag attribute is set to “enabled”. this parameter indicates the A-Interface Monitor Thresholds for SS7 channels. Maximum number of target cells.16 6 Default value changed in BR8. this parameter indicates how many target cells may be included in the HANDOVER REQUIRED message sent to the MSC. that is: LCSMONTH = (SS7S out of service/SS7S equipped)*100). object: unit: range: default: BSC [BASICS] 1 1. If this parameter is set to TRUE.12 5 MAXNCELL=6. Missing timeslot threshold.e. this attribute is only relevant if HSCSD is enabled (ENHSCSD=TRUE) and determines the maximum AIUR downgrade level for non-transparent data calls. The alarm(s) indicate(s) that the timeslot is missing (e.0! MISTSTRSH=3. this attribute defines the alarming threshold for the feature ‘Detection of missing timeslots on Abis’. object: range: default: BSC [BASICS] ENABLED(1.3 2 LCS NSS Centric solution. this parameter allows to choose the location service type ( NSS centric / BSS centric ) supported by BSC. if the HO target does not belong to the own BSC area or if all handovers for a certain cell are to be performed by the MSC (see parameters LOTERCH and LOTRACH (SET HAND)). Important: This parameter must be set to FALSE if LCS BSS centric solution is used! Maximum AIUR downgrade level for NT data calls.. 40 3 34 . object: range: default: BSC [BASICS] 0. The HO RQD message is sent. DISABLED ENABLE(30) (minor) ENABLE(60) (major) ENABLE(90) (critical) LCS monitor thresholds.

CS1 and CS2 can be handled with a 35 . Null 1 parameter range extended in BR8. by the timer TEMPCH (see command CREATE CPCU). Please refer to parameter ENFOIAHO (see above) for further details.0! Maintenance bit mask. if BIT25 is set. • Setting MNTBMASK=BIT25 disables the use of the GPRS coding schemes CS3 and CS4. it is mandatory to enable EDGE. as only in this mode the BSC can use concatenated TCH frames on the Abis . Some customers prefer to disable CS3/CS4 if EDGE is enabled. Thus the disabling of CS3/CS4 shall motivate the subscribers to subscribe to the EDGE services. then the “Remote Transcoder Failure” event message (with originator 8100) is transmitted to the Radio Commander without respect to the settings of the ERRACT filter.1023) in the same cell. However. if the operator knows the exact impact of each of the bits that can be set. It has been verified that. this parameter was originally intended to be reserved for internal use only. then in addition to SFC 0 also SFC 1 (if present) of an active PDCH is controlled. This means that. although compliant to Standards. • MNTBMASK=BIT16 . The idea was to set specific bits of this parameter to enable manufacturer internal functions that require the installation of specific patches. • MNTBMASK=BIT22 is used to suppress the use of variable format in the SYSTEM INFO TYPEx messages which are sent on the Um. For this reason it is urgently recommended to use this parameter only. two concatenated Abis TCHs will also be used for CS2 (If EDGE is disabled. as both coding schemes required two concatenated Abis TCHs. However. setting MNTBMASK=BIT25 has the following side-effects: To enable CS3/CS4..this setting suppresses the sending of the BSSMAP OVERLOAD message to the MSC in case of Abis LAPD overload (the bit can be set starting from the BR8. this parameter has also been repeatedly used to enable and control project-specific SW modifications or modifications that were introduced in BR6.which is required for CS3 and CS4. as with the number of concatenated EDGE radio timeslots supported by the currently available mobile phones the performance of EDGE is not far superior than the that of CS4. the variable bitmap format included in some SYSINFO messages is not correctly managed by several mobiles in the following scenario: mix of frequencies in the two ranges (0. while SFC>=1 is controlled by the timer TEMPPDT (see command CREATE CPCU). the BSC will only use the coding schemes CS1 and CS2 for GPRS.. object: unit: range: default: BSC [BASICS] 1 BIT1. for EMPTY PDT purposes. SFC=0 is controlled by TEMPCH timer. If bit 23 is not set. however. EDGE is enabled. • MNTBMASK=BIT12 is used to enable/disable the forced intracell handover due to preferred service layer. If MNTBMASK=BIT10 is set.124) and (975. this corresponds to “Delayed TBF Release” enabled during MM procedures.0 ‘DTM load’. BIT61 <DEFAULT>. This change avoids interworking problems with Ericsson MSCs.MNTBMASK=<DEFAULT>. see release documentation for details). • If MNTBMASK=BIT17.02 as late features. • If MNTBMASK=BIT23 is set. If BIT10 is not set (default value) corresponds to “Delayed TBF Release” disabled during MM procedures.. If. The following functions can be controlled by the MNTBMASK Parameter (for guidelines for use please see below): • MNTBMASK=BIT10 is used to enable/disable delayed TBF release during Mobility Management (MM) procedures. then for EMPTY purposes.. Bit 17 set to 0: the “Remote Transcoder Failure” event message (with originator 8100) is transmitted to the Radio Commander with respect to the settings of the ERRACT filter. 1.

CS3 and CS4 will not be allocated but two concatenated Abis TCHs will be used for CS2 although this would not be necessary without EDGE. in terms of used bytes. These percentage values represent the relative percentage compared to the radio interface paging throughput which depends on the CCCH configuration (for further details please refer to the section ‘BSC Overload Handling’ in the appendix of this document). between ‘VariableBitMap’ and ‘Range128’. The paging delivery rate can be adjusted to values of 100%.0 to enable the change request CR2870 which is supposed to reduce the length of a HANDOVER COMMAND to the smallest possible size in order to use as few layer 2 messages on the Um interface as possible. The two bits are used as representation of a two-digit binary value to control the setting: BIT31 0 0 1 1 BIT30 0 1 0 1 Paging delivery rate (BSC->BTS) 130% of Um paging throughput 120% of Um paging throughput 110% of Um paging throughput 100% of Um paging throughput • The setting MNTBMASK=BIT32 and MNTBMASK=BIT33 are used in BR8. To achieve the smallest possible messag size. e. • The setting MNTBMASK=BIT26 is used to enable/disable the following behaviour: when an INTERCELL HANDOVER CONDITION INDICATION message with cause 'better cell' is received from BTS for a DTM capable MS. If the frequency list could be encoded with Range128 format (possible if less than 29 frequencies have to be coded). In other words. Two improvements are introduced: 1) If MNTBMASK=BIT32 is set the DBA subsystem will calculate the effective length of the frequency list encoded by the variable bit map.. since the two improvements are controlled by two different bits of MNTBMASK. the CR allows an optimal decoding of the frequency list.single Abis TCH). As there are mobiles on the market which might not support the variable bit length the functionality is administrable by the MNTBMASK bits 32 and 33. they could be used independently or together. by the usage of a variable bit map in case of handover to a hopping TCH using block wise frequency allocation (coding of up to 32 frequencies is feasible in one FACCH block). the smaller the probability that it is not correctly received by the MS. This is done to reduce the probability of decoding errors on the MS side for the HANDOVER COMMAND messages: the shorter the message (and the less layer 2 messages are needed for delivery to the MS).g. Messages that cannot be correctly decoded and assembled by the MS lead to call drops during handover. • The setting MNTBMASK=BIT30 and MNTBMASK=BIT31 are used in BR8. even if CS3 and CS4 are disabled by BIT25. the BSC discards the Power Budget handover request and does not triggere the associated PM counters. 2) If MNTBMASK=BIT32 is set. the DBA subsystem will chose the best encoding law.0 to control the paging delivery rate from BSC to BTS. 36 . If a minimization is not possible then the present coding is used. This means: if EDGE is enabled. the customer has to consider that in any case additional GPRS resources are required for GPRS.130%. the BSC will execute the handover when it has analyzed the target cell list and checked if one of the the target cells meets the following conditions: 1) DTM is enabled 2) EDGE is configured If no cells meet the condition above. instead of using the currently fixed value ‘16’. but CS3/CS4 is disabled by BIT25.

GSMR.GPRS: 31 frequencies .All bits can be reset to their original values using the setting MNTBMASK=Null or MNTBMASK=<DEFAULT>.Every command SET BSC:MNTBMASK=BITx. The maximum number of frequencies which currently fit into a single composed DL IMMEDIATE ASSIGNMENT is: . ??? • If MNTBMASK=BIT38 is set the BS-240XS cannot have SYSID value (see BTS object) equal to GSMDCS.‘Setting one bit’ of this parameter means: setting it to ‘1’ (i. GSM850." Important Hints for Use: . This means that. . • MNTBMASK=BIT42 is used to remove TCH/SD channels in the TCHSDPOOL (see command CREATE CHAN for TCHSD) from channels usable for DTM. EXT900. if enabled at BSC level. no mixed configurations are allowed. Several bits of the maintenance bit mask are fixed to '0' or '1' and cannot be changed.g. resets the maintenance bit mask to its default value und just changes that bit which is included in the command. • If MNTBMASK=BIT35 is set. GSM850PCS or GSM850DCS.BIT29). however. for those bits that can be set by MNTBMASK the default value is ‘0’.. only R99 onwards GPRS/EGPRS MSs will be controlled by NCCR (NC2). if it is set to 0 (default). In other words. .EDGE: 23 frequencies Value 0 (default) disables the extension of frequencies and value 1 enables it. resets BITy to '0' and sets BITx to '1'. . if some of the bits are already set. MNTBMASK=BIT8|BIT9).• The setting MNTBMASK=BIT34 is used to enable the request if the BTSM becomes an additional broadcasting element in the BSS.EDGE: 7 frequencies With bit 43 set the maximum number of frequencies that can fit into a single DL IMMEDIATE ASSIGNMENT is extended to: .e. Note: When a resource is allocated on the not preferred layer of its Service Layer List. MNTBMASK=BIT8 means: BIT8=1). a prevention mechanism for pingpong handover for power budget handover is enabled.GPRS: 15 frequencies . if BITy was set before. all GPRS/EGPRS MS’s regardless of their release. This is necessary as the DL IMMEDIATE ASSIGNMENT splitting is a feature which is not correctly supported by many MS on the market. if NCCR is enabled at BSC level. the resource reallocator will rearrange it by moving towards the preferred layer as soon as resources will be available. and another one is to be set in addition. the number of frequencies that can fit into DL IMMEDIATE ASSIGNMENT can be increased without splitting it in two parts. In this way. 37 . DCS1800. • If MNTBMASK=BIT41 is set. PCS1900. • MNTBMASK=BIT43 is used to enable a 16 bit room saving in DL IMMEDIATE ASSIGNMENT. The allowed configurations are: BB900. the parameter values must be linked with a 'pipe' (e. it is required to re-enter the command with ALL required bits set. will be submitted no NCCR. only some of them can be really modified by command. . This moving procedure is executed only if the MNTBMASK=BIT12 is set (see above). All the subordinate objects of a BS-240XS must have the same frequency range.The command allows to set 30 bits (BIT0. the command SET BSC:MNTBMASK=BITx.To set several bits at the same time.

object: range: default: BSC [BASICS] TRUE. the supported A-interface protocol variants of the connected MSC. The BSC is informed by the BSSMAP message OVERLOAD with cause „ processor overload“ . This parameter has to be set in correspondence with the GSM phase resp. PHASE2EFR indicates an MSC that supports the ‘Speech Version’ IEs. MSC version. PHASE2CCEFR indicates that the MSC supports both the IE ‘Current Channel’ and the ‘Speech Version’ IEs. MSC overload is detected by the MSC itself. too. The MSC reduces paging load by its own and therefore the BSC reduces only mobile originating traffic. this parameter specifies whether the connected MSC is able to manage the ‘pooling’ feature or not. As the MSC is the one to select the A-interface channels for a specific call the MSC has to manage the pooling types assigned to the A interface resources. object: range: default: BSC [BASICS] nc0. As MSC. the overload conditions and traffic reduction mechanisms are explained in an own chapter that comprises all possible scenarios of overload and overload handling as well as the references to the relevant parameters. the value of this attribute is put in the parameter Network Control Order inside Packet Measurement Order message. Note: If the feature 'ESVSIG' (extended speech version signaling) is enabled in the MSC the selected value must be PHASE2EFR. this parameter defines the usage of Network Control Order during NACC when the MS is in packet transfer mode. BTS and MSC overload Handling” in the appendix of this document. nc1 nc0 38 . this parameter determines the protocol type to be used on the A-interface.0! NACCNTWCOR=nc0. For further details about the BSC overload regulation please refer to the section “BSC. determines whether MSC overload handling is enabled or not. FALSE FALSE MSC overload handling. FALSE TRUE MSCPOOL=TRUE. otherwise handover procedures may fail with 'protocol error between BSC and MSC’. the receipt of this IE from the MSC is correctly handled anyway). PHASE2CC indicates that MSC the supports the Information Element ‘Current Channel’ (‘CC’ in the value of MSCV actually means that the BSC includes the IE ‘Current Channel’ in the HANDOVER REQUIRED message.MSCOVLH=TRUE. NACC Network Control Order. Further parameters relevant for BTS overload handling: BSCT18 and BSCT17 (see command SET BSC [TIMER]) MSC pooling. When NACC is enabled. BSC and BTS overload handling are closely interwoven. object: range: default: BSC [BASICS] TRUE. object: range: BSC [BASICS] PHASE1 PHASE2 PHASE2CC PHASE2EFR PHASE2CCEFR PHASE2CCEFR default: Default value changed in BR8. MSCV=PHASE2CCEFR.

the network instructs the GPRS mobile to transmit the RXLEV_DL values of both serving and adjacent cells in PACKET MEASUREMENT REPORT messages. The (Radio Link) Network Controlled Cell Reselection is a different cell reselection method: The network requests measurement reports from the GPRS MSs and controls their cell reselection based on these measurements and configurable network controlled cell selection parameters. see below). Attention: . the network may redistribute MSs among cells to satisfy the maximum number of service requests. this parameter determines whether GPRS network controlled cell reselection (NCCR) is enabled or disabled. With this feature. The Traffic Control network controlled cell reselection guarantees the optimum usage of resources. only the Radio Link Network Controlled Cell Reselection is enabled. the traffic control strategy must be enabled (TRFPS=TRUE) in addition to the network controlled cell reselection (NCRESELFLAG=ENABLE). the network may command a GPRS MS to a neighbour cell that provides better radio conditions.If the operator enables only the network controlled cell reselection feature (NCRESELFLAG=ENABLE). . For further details please refer to the parameter CRESELTRHSOUT in object PTPPKF. object: range: default: BSC [BASICS] DISABLE. Based on the reported measurement values and on the configured network controlled cell reselection parameters. This algorithm is called Radio Link Network Controlled Cell Reselection.e.NCRESELFLAG=ENABLE. if network-controlled cell reselection is enabled. In addition. a better GPRS/EGPRS traffic distribution among the available channels in all of the available cells. ENABLE DISABLE Enable network-controlled GPRS cell reselection. The ‘normal’ GPRS cell reselection algorithm is executed by the mobile station in case the parameter NTWCOR is set to NC0 (in BR70 always by default). i. 39 . Thus.if the user wants to enable the Traffic Control Network Controlled Cell Reselection. Every GPRS MS in packet idle mode and in packet transfer mode measures received signals from both the serving cell and neighbouring cells and performs cell reselection autonomously on the basis of the cell selection criteria C1 (BCCH) or C31/C32 (in case a PBCCH is available in the cell). the operator can enable Traffic Control Network Controlled Cell Reselection (parameter TRFPS.

Both measurements distinguish the immediate assignment procedures by their establishment cause values and count them in separate causespecific subcounters. the changing of the NECI parameter will change the distribution of the counts over the subcounters.0 NECI patch loaded = BR7.0 parameter NECI=FALSE 40 .e. which is broadcast in the SYSTEM INFORMATION TYPE 3 in the IE ‘Cell Selection Parameters.0. this parameter controls the value of the NECI (New Establishment Cause Indicator) bit. In releases before BR7.NECI=FALSE. The reason for the introduction of the NECI parameter is to avoid problems that were experienced with specific mobile phones by NOKIA that refused to connect to the network when the NECI bit was set to ‘1’ in the SYS INFO.BR6. the NECI bit was controlled by a TDPC patch (i. SUIMASCA counts the subsequent IMMEDIATE ASSIGNMENT messages. Moreover. they are not allowed to use them. Attention: The NECI parameter has an impact on the performance measurement counters for immediate assignment procedures ATIMASCA.08. If the NECI bit is set to ‘0’ (NECI=TRUE). which allow a more specific signaling of channel requirements (e. the cause distribution between ATIMASCA/SUIMASCA on the one hand and NSUCCHPC on the other hand will deviate to a greater extent than with NECI=FALSE.0. SUIMASCA and NSUCCHPC. Note: The parameter NECI replaces the so-called ‘NECI patch ’that was provided for each load up to BR6.0 parameter NECI=TRUE .08 New establishment cause indication. even if they support phase 2 establishment cause values.0 NECI patch not loaded = BR7. the request for HR in case of direct TCH assignment) in the random access procedure.e. the NECI bit was changed from ‘0’ to ‘1’. As some of the subcounters of ATIMASCA and SUIMASCA represent specific phase 1 and phase 2 establishment causes. no matter whether they are phase 1 mobiles or not.g. The available ‘establishment cause’ bit strings in the CHANNEL REQUEST message can be subdivided into two groups: • GSM phase 1 establishment cause values All GSM phase 1 establishment cause values consist of 3 bit are supported and are the only values which are supported by phase 1 mobiles. The limited number of bits (3) does not allow the signaling of very specific setup requirements (e.BR6. the MSs in the cell are only allowed to use only 3-bit establishment cause values.g. which consist of 4. the parameter NECI must be used as follows: . request for a HR TCH in case of direct TCH assignment) during the random access procedure via the RACH. ATIMASCA counts the CHANNEL REQUEST messages that actually reach the BSC in the CHANNEL REQUIRED message. For more details about the possible establishment cause values please refer to the section dealing with the format of the CHANNEL REQUEST message in GSM 04. especially if NECI=TRUE. To achieve the same effect as in BR6. if the patch was loaded. • GSM phase 2 establishment cause values GSM phase 2 introduced an additional set of establishment cause values. the NECI parameter was introduced.0. object: range: default: reference: BSC [BASICS] TRUE. Thus all mobiles must behave like phase 1 mobiles during the random access procedure. 5 or 6 bits.’ and which determines which ‘establishment cause’ values in the CHANNEL REQUEST message the MSs in the cell are allowed to use when requesting a dedicated control channel via the RACH for call setup or other transactions. i. FALSE FALSE GSM 04. To avoid the continuous patch maintenance for this patch.

5 channel model (see parameter ASCIONECHMDL in command SET BSC [BASICS])) can never receive a notification via the FACCH because in this case notification is only sent via the ASCI Common TCH but not via the newly activated uplink TCH. the BSSMAP message VGCS/VBS ASSIGNMENT REQUEST also contains an IE ‘call priority’. The value GSMRAILPUB means that the frequency bands GSMR and GSM900 and DCS1800 can be configured in the cells but. The standard forsees that the PAGING is only forwarded to the ASCI subscribers if its priority level is higher than the one of the VBS/VGCS call itself. However. This is done with the DTAP message NOTIFICATION FACCH which is sent via the FACCH of the ASCI Common TCH (one DL TCH used by all ASCI MSs in the cell) directly prior to the PAGING COMMAND itself (which is sent via the PCH as usual) and which indicates ‘paging information is included’. the BSC sends the NOTIFICATION FACCH message to the busy ASCI subscriber only . MTC) When a particular ASCI MS is currently involved in a CS call (MOC or MTC). no handover from/to GSMR to one of the other frequency bands is possible. HIGHEQ1. Notification on FACCH. The priority level indicated in this IE is independent of the one indicated in the (possibly subsequently sent) PAGING message. HIGHEQ2. only ‘listening’ ASCI subscribers can receive a notification on FACCH with paging information included. object: range: BSC [BASICS] NOSUPP.if the VBS/VGCS ASSIGNMENT REQUEST message from the NOTFACCH=NOSUPP. HIGHEQ3. In this case the BSC informs the busy ASCI subscriber about the new ASCI group call via the NOTIFICATION FACCH message. MTC during and ongoing ASCI group call When a particular ASCI MS is currently involved in a VBS or VGCS group call. 2. Exception: if NOTFACCH is set to ALWAYS. GSMRAILPUB GSMDCSTSM. object: BSC [BASICS] range: GSMDCS. no matter whether the priority level indicated in the PAGING message is higher or lower than the priority level indicated in the VGCS/VBS ASSIGNMENT REQUEST message. determines the type of network respectively frequency band. GSMPCSTSM default: GSMDCS Network type. GSMR. the BSC can instruct the ASCI MSs (currently involved in a group call) to monitor the PCH if a paging is to be transmitted. the ASCI subscriber may still receive a VBS/VGCS group call. HIGHEQ4 NOSUPP default: 41 . which is sent on the dedicated CS TCH and which indicates ‘goup call information is included’. The BSC sends the NOTIFICATION FACCH message to all cells with an activated ASCI common TCH only . the priority level is not checked and the NOT FACCH message is sent in any case. HIGHEQB. GSM850DCS. a subscriber who has requested and received a separate dedicated uplink TCH in 1. However. Two scenarios are possible: 1. Notes: . As the ASCI MS normally does not monitor to the paging channel (PCH) of the BCCH during an ongoing ASCI group call. ALWAYS. . GSMPCS.NETWTYPE=GSMDCS. HIGHEQ0.During setup of an ASCI VBS or VGCS call. EQA. GSM850PCS. it may still receive and accept normal terminating CS calls (MTC).if the priority level indicated in the ‘eMLPP priority’ IE is equal or higher than the priority level defined by the parameter NOTFACCH. it was decided not to use this approach in the SBS: In the Siemens BSS the called ASCI subscriber can accept the MTC in any case.e.A ‘talking’ ASCI subscriber (i.if the PAGING message from the MSC contains the optional IE ‘eMLPP priority’ and . In other words. Incoming ASCI group call during ongoing CS call (MOC. this parameter is relevant for ASCI only and and indicates for which mobile priorities the NOTIFICATION FACCH messages (BSC->MS) are sent on the FACCH belonging to the TCH seized by an ASCI subscriber.

Only exception: if NOTFACCH is set to ALWAYS. 0.10000 8500 PAGCOORCLB=DISABLED. up to BR7. This means that ‘A’ is the highest priority. B. object: range: default: BSC [BASICS] 0. object: range: default: BSC [BASICS] ENABLED. STLP boards are used as PCM interface cards. The meaning of the values is the following: ALWAYS HIGHEQ4 HIGHEQ3 HIGHEQ2 HIGHEQ1 HIGHEQ0 HIGHEQB EQA (Notification/FACCH will always be sent) (Notification/FACCH will always be sent for calls having priority equal or higher than 4) (Notification/FACCH will always be sent for calls having priority equal or higher than 3) (Notification/FACCH will always be sent for calls having priority equal or higher than 2) (Notification/FACCH will always be sent for calls having priority equal or higher than 1) (Notification/FACCH will always be sent for calls having priority equal or higher than 0) (Notification/FACCH will always be sent for calls having priority equal or higher than B) (Notification/FACCH will always be sent for calls having priority equal to A) NTWCARD=NTWSNAP. 4. OVLENTHR=8500. object: unit: range: default: BSC [BASICS] 1000=10% 1000. where the value 1000 corresponds to 10% (see also parameters OVLSTTHR and BSCOVLH). the priority level is not checked and the NOTIFICATION FACCH message is sent in any case. object: range: default: BSC [BASICS] PCM30. object: unit: range: default: BSC [BASICS] 1000=10% 7000. Note: The order of the eMLPP priority values is A. in addition to the SNAP board. ‘4’ the lowest one. 42 . 2.if the priority level indicated in the ‘call priority’ IE is equal or higher than the priority level defined by the parameter NOTFACCH. 1. object: range: default: BSC [BASICS] NTWSNAP NTWSNAP_STLP NTWSNAP OVLSTTHR=9500. The value NTWCARD=NTWSNAP_STLP is mandatory if. the alarm ‘BSC PAGING QUEUE OVERLOAD’ is raised and the BSSMAP OVERLOAD message is sent to the MSC...0. this parameter defines a percentage threshold for the indication of the alarm ‘BSC PAGING QUEUE OVERLOAD’ and the transmission of the BSSMAP message OVERLOAD on the A-interface. The threshold is applied as follows: if the percentage of discarded pagings has exceeded the threshold defined by PAGQOVLIND in the last second. where the value 1000 corresponds to 10% (see also parameters OVLENTHR and BSCOVLH). this parameter determines the TDPC load threshold for the start of overload handling. this parameter determines the TDPC load threshold for the end of overload handling. DISABLED DISABLED PAGQOVLIND=DISABLED.MSC contains the IE ‘call priority’ and . The TDPC load is specified in %.10000 9500 Network card type.0 are NTWSNAP and NTWSNAP_STLP. BSC overload start threshold. this parameter used to determine the kind of switching network whether a switching network (SN16. PCM type. 3. BSC overload end threshold.. The TDPC load is specified in %. Paging coordination class B. PCM24 PCM30 Paging queue overload indication. specifies the type of PCM system used within the network. As. starting from BR8.100 0 PCMTYPE=PCM30.0 only high capacity BSC (HC-BSC) configurations are supported. the only allowed values in BR8. this flag to enable/disable Paging coordination for Class B mobiles. SNAP used in the BSC).

the MSs are allowed to send Release-99-specific messages and information elements in their signaling messages towards the network. “172. This IE is relevant for the setup of ASCI emergency calls. this parameter indicates the Router IP address associated to all PCU port 0 (Ethernet port on the PPXU). This new procedure is allowed only with MSCs that are compliant to GSM release 99 or higher. this parameter indicates the Router IP address associated to all PCU port 1. SIMSCREL99=TRUE.0. object: range: default: BSC [BASICS] 15 character string. In case of co-located SGSN without a router between BSC and SGSN the following configuration rules apply: . Also other applications might require the R99 compatibility of the MSC. these attributes must be set to <NULL>. For further information please refer to parameter ROUIPADD0 (see above) System Information MSC release 99. An ASCI mobile is only allowed to send the IMMEDIATE SETUP 2 message if the MSC Release bit is set to ‘1’. For the SIEMENS-MSC. Router IP address 1.all SGSN and PPXU IP Adresses must belong to same IP subnets (as identified by two respective subnet masks. this parameter determines the value of the “MSC Revision“ bit (the bit after the attach-detach flag) which is included in the IE ‘Control Channel Description’ in the message SYSTEM INFORMATION TYPE 3. It is used in order to support High speed Gb Interface. <NULL> <NULL> ROUIPADD1=<NULL>. Since BR6. there is no way to check the release compliance of the MSC) to avoid protocol errors. SUBNETMASK1). which indicates that the MSC release is Release 99 or higher.31.1. Both messages are used in the scope of ASCI (Advanced Speech Call Items. mainly used for GSM-R). ROUIPADD1).ROUIPADD0=<NULL>. <NULL> <NULL> Router IP address 0. If SIMSCREL99 is set to TRUE (and thus the ‘MSC Revision’ bit is set to ‘1’ in the SYSINFO 3). parameters SUBNETMASK0. Moved to CPCU object in BR8. OTDI (Originator To Dispatcher Information) into the IMMEDIATE SETUP message. so that each PPXU's routing table contains no entry for default gateways . the bit has been administrable by the parameter SIMSCREL99. object: range: default: BSC [BASICS] TRUE.1). Note: The attributes ROUIPADD0. Note: Please see also parameter SISGSNREL99 (see below). this precondition is fulfilled starting with SR10 (CS 2. It is up to the network operator to set the value of this parameter in correspondence with the real conditions (for the BSC. SUBNETMASK1 are necessary only if SGSN is connected to BSC via router. FALSE TRUE Default value changed in BR8.the operator sets to <NULL> both Router Ip Address 0 and 1 (parameters ROUIPADD0. object: range: default: BSC [BASICS] 15 character string. SUBNETMASK0.g.21. The reason for the introduction of this parameter was the necessity to support the message IMMEDIATE SETUP 2 in addition to the normal IMMEDIATE SETUP message.88”). The new IMMEDIATE SETUP 2 message allows the mobile to include the additional Information Element. ROUIPADD1. If the router is not present.0! SISGSNREL99 43 . The convention used for this value is the dotted decimal format (e.

255. the downgrading from 14. The BTS indicates the in-call-modification to the BSC using the MODIFICATION CONDITION INDICATION message which contains the suggested new data rate. ROUIPADD1. while in countries PCM24 links (normally used in American countries) makes use of the µ-law (‘µ-law’ is indicated as ‘M_LAW’ in the parameter value) Sub net mask 0. FALSE FALSE SPENLAW=A_LAW. so that each PPXU's routing table contains no entry for default gateways . For this reason. The value must be assigned according to the local LAN configuration. SUBNETMASK0.6 kbit/s 14. The 14. Sub net mask 1.4 kbit/s coding will cause a drop.all SGSN and PPXU IP Adresses must belong to same IP subnets (as identified by two respective subnet masks. “255.SPEED145=FALSE. <NULL> <NULL> SUBNETMASK1=<NULL>. If the router is not present. <NULL> <NULL> Speed 14. In case of co-located SGSN without a router between BSC and SGSN the following configuration rules apply: . Both transparent and not-transparent connections are supported. SUBNETMASK1).255. i. This type of channel coding increases the data throughput of a single GSM time slot to 14.4 Kbit/s call handover to a cell that is not supporting 14.4 kbit/s (netto data rate. For further details please refer to parameter SUBNETMASK0 (see above).5 kbit/s (brutto data rate. It is used in order to support High speed Gb Interface.6 Kbit/s (by combining 4 GSM time slots) for a single connection. i.0”). this enables the data service with 14. parameters SUBNETMASK0.and downgrading of data calls please refer to the explanations provided for the parameters included in the command SET HAND [DATA]. including frame header) respectively 14. SUBNETMASK1 are necessary only if SGSN is connected to BSC via router. 44 .4 Kbit/s netto data rate and is based on a special transcoding algorithm which must be supported by the TRAU. these attributes must be set to<NULL>.4 kbit/s and vice versa) is implemented to adapt the data rate appropriately to the C/I environment. Speech encoding law.5 supported. object: range: default: BSC [BASICS] TRUE.4kbit/s coding available to the user in non-transparent mode or when an external end-to-end error-control is applied may drop below the effective data rate achieved with the 9. The convention used for this value is the dotted decimal format (e. The PCM30 standard (normally used in all European and non-American countries) uses the A-law transcoding standard. without frame header) speed.g.e.the operator sets to <NULL> both Router Ip Address 0 and 1 (parameters ROUIPADD0. For further details related to the up. In correspondence with GSM. As a result the effective data rate of the 14. object: range: default: BSC [BASICS] 15 character string.4kbits channels is less effective compared to the one of the 9.4 Kbit/s to 9. this parameter is the NetMask for IP address of the the PPXU-External router associated to all PCU port 0 (Ethernet port on the PPXU). The error correction mechanisms present in the Um coding of 14. In transparent mode a 14. specifies the used speech coding law used on the PCMA links. object: range: default: BSC [BASICS] A_LAW M_LAW A_LAW SUBNETMASK0=<NULL>.6kbit/s coding. a channel mode modify procedure in case of non-transparent mode (upgrading & downgrading: 9.e. ROUIPADD1). Note: The attributes ROUIPADD0. this parameter this parameter is the NetMask for IP address of the the PPXU-External router associated to all PCU port 1 (Ethernet port on the PPXU). object: range: default: BSC [BASICS] 15 character string.6kbit/s coding.6 Kbit/s is not possible for a transparent call (both in case of established call or during handover).4 Kbit/s coding can be used in combination with HSCSD allowing a data rate up to 57.

SYSPACKSYSSUP=FALSE. if the BSC cannot find any idle SDCCH to satisfy the request. see parameter EDTMSUP in command CREATE PTPPKF] and defines the maximum duration by which the BSC will delay the release of the RR connection.. defines the MS waiting time before the MS allowed to attempt another RACH access by sending a CHANNEL REQUEST. In this case the MS will stay in the cell. before MS may send a DTM-Request Indicator again after receipt of a DTM REJECT message. object: unit: range: default: BSC [BASICS] 1 minute 0. This timer value is sent to the MS in the IE ‘Wait Indication’ within the IMMEDIATE ASSIGNMENT REJECT message.. The value of this timer is sent to the MS in within the DTM REJECT message.therefore the RESTART INDICATION towards the CBC is not necessary after BTS recovery.. whether it receives an IMMEDIATE ASSIGNMENT REJECT as response to a transmitted CHANNEL REQUEST or whether it does not receive any response at all. The timer T3122 defines the time the MS must wait before it is allowed to send another CHANNEL REQUEST via the RACH in the same cell.255 5 GSM 04. this timer is relevant for the feature Dual Transfer Mode (DTM.255 5 GSM 04. On recovery of the failed BTS the BSC sends a RESTART INDICATION to the CBC which initiates a realignment with the BSC which re-establishes the transient SMS-CB data in the TDPC. all SMS-CB messages for the affected BTS are deleted from the transient TDPC memory. object: range: default: BSC [BASICS] TRUE. The RACH access is used to request a dedicated control channel (mostly an SDCCH). if the BSS response to the previous RACH access was an IMMEDIATE ASSIGNMENT REJECT.5s 3. FALSE FALSE T3122=5. Timer for CBC service interruption.. Wait indication time. While in the latter case the MS will leave the cell (by cell reselection) after a defined number of RACH access attempts without (see parameters MAXRETR and NSLOTST in command SET BTS [CCCH]) without receipt of an IMMEDIATE ASSIGNMENT COMMAND or REJECT. In the successful case. this parameter indicates if the PACKET PSI STATUS and PACKET SI STATUS messages are supported by the BSC or not. it rejects the access attempts by sending an IMMEDIATE ASSIGNMENT REJECT message via the AGCH. Value TCBCSI=0 means: The SMS-CB messages are not cleared from the TDPC memory .08 T3197=5. T3197. TCBCSI=1. The BSC transiently stores all Short Message Service Cell Broadcast (SMS-CB) messages received from the Cell Broadcast Center (CBC) in the TDPC memory. In other words: when the outage time of a BTS exceeds the time specified by TCBCSI. The mobiles are informed about the BSS support of these messages via the BCCH within the SYSTEM INFORMATION TYPE 13 and via the PBCCH within the PACKET SYSTEM INFORMATION TYPE 1. object: unit: range: default: BSC [BASICS] 0. 5 4 SYSINFO PACKET SYSNFO support.1440 1 TDTMWIND=5.08 45 . However. see parameter EDTMSUP in command CREATE PTPPKF] and defines the waiting time. Timer DTM wait indicator. the BSS responds to the CHANNEL REQUEST message by sending an IMMEDIATE ASSIGNMENT COMMAND via the AGCH. this timer is relevant for the feature Dual Transfer Mode (DTM. in case of an AGCH response with IMMEDIATE ASSIGNMENT REJECT the MS just has to obey the waiting time defined by T3122 before it may attempt the next RACH access attempt. object: unit: range: default: Reference: BSC [BASICS] 1s 0. Note: For the MS it does make a difference.. The timer TCBCSI defines the time the BSC delays the deletion of the CBC messages from the TDPC memory. object: unit: range: default: Reference: BSC [BASICS] 1s 0.

TGUARDTCHSD =SEC10. idle TCH/SDs are immediately moved back to the TCH/SD_POOL when the abovementioned SDCCH traffic load condition is detected. When it expires. the TCH/SD is moved back from the SDCCH_BACKUP_POOL to the TCH/SD_POOL. of idle TCHSDs in BACKUP_POOL” means: 1) all TCHSDs in the SDCCH_BACKUP_POOL in usage state “idle” and 2) all TCHSDs in the SDCCH_BACKUP_POOL for which TGUARDTCHSD is running This means: If there is no TCHSD in the SDCCH_BACKUP_POOL then the term 8 ∗ (no. it can be used as TCH or as an additional SDCCH/8. object: range: default: BSC [BASICS] SEC00. This means that. when the SDCCH load decreases and the congestion in the SDCCH_POOL ends. no SDCCH will be allocated in the SDCCH_BACKUP_POOL anymore. If TGUARDTCHSD=SEC00. the TCH is returned to the TCH/SD_POOL and the TCH request is satisfied with this channel. of idle TCHSDs in BACKUP_POOL)** SDCCH traffic load [%] = ∗ 100 Notes: * the calculation always considers the total amount of SDCCH subslots from both the SDCCH_POOL and the SDCCH_BACKUP_POOL ** “no. of SDCCH subslots in unlocked/enabled – 8∗(no. Whether a TCH/SD currently in the SDCCH_BACKUP_POOL can be moved back to the TCH/SD_POOL is checked during every release procedure for an SDCCH: during the SDCCH release the BSC checks the current SDCCH traffic load according to the following formula no. SEC11. . The calculated SDCCH traffic load is compared to the threshold SDCCHCONGTH (see command SET BTS). an SDCCH request will only be satisfied by a subslot from the SDCCH_BACKUP_POOL. where it can be used as normal dual rate TCH. of busy SDCCH subslots * no.Attention: The calculation of the SDCCH load that is compared to 46 . a) In case of SDCCH traffic load ≥ SDCCHCONGTH the TCH/SD remains in the SDCCH_BACKUP_POOL and TGUARDTCHSD is not started. it basically belongs to the TCH/SD_POOL. During the SDCCH allocation the SDCCHs of the SDCCH_POOL are always handled with priority. If during the run time of TGUARDTCHSD another SDCCH request establishes that the move condition (SDCCH traffic load > SDCCHCONGTH) is fulfilled again. SEC10. allowing a dynamic on-demand enhancement of the SDCCH capacity. SEC12.0 ! Guard Timer for TCH/SD. this parameter defines the time the BSC has to wait before a TCH/SD is moved from the SDCCH_BACKUP_POOL to the TCH/SD_POOL. SEC14. When the BSC receives an SDCCH request while the percentage of busy SDCCH subslots has exceeded the threshold SDCCHCONGTH (see command CREATE BTS [BASICS]). of idle TCHSDs in BACKUP_POOL) = 0.e. When a TCH is created with CHTYPE=TCHSD and CHPOOLTYP= TCHSDPOOL (see associated parameters in command CREATE CHAN). When a TCH/SD is created with TCHSDPOOL. i. TGUARDTCHSD is stopped and the TCH/SD remains in the SDCCH_BACKUP_POOL. then TGUARDTCHSD is immediately stopped. if there is no subslot available in the SDCCH_POOL. SEC13. b) In case of SDCCH traffic load < SDCCHCONGTH the timer TGUARDTCHSD is started for those TCH/SDs which are in ‘idle’ mode (no SDCCH subslot in state ‘busy’). Notes: . SEC15 SEC10 default value changed in BR8. the BSC moves the 8 SDCCH subchannels of one TCH/SD from the TCH/SD_POOL to the SDCCH_BACKUP_POOL to keep additional SDCCH resources for further incoming SDCCH requests.If TGUARDTCHSD is running for particular TCH/SD and the BSC receives a TCH request while all other TCHs are busy.

47 . Instead. Trace measurement reports enabled. this parameter determines the sending granularity for the TRACE MEASUREMENT RESULT messages. Trace measurement granularity. These TRACE MEASUREMENT RESULT messages are sent from BTS to BSC during calls for which the call trace features IMSI tracing (see command CREATE TRACE) or Cell Traffic recording (CTR.254 1 TRACEMR=TRUE. As from point of view of the BTS there is no difference between IMSI tracing and CTR the sending granularity determined by TRACEMG is valid for both features. If TRACEMR=FALSE the BSC does not send the START TRACE message to the BTS and no radio measurements can be recorded in the IMSI trace record or CTR trace record. This means that.The BTS does not know anything about the association of the TCH/SD channels to the ‘BSC channel pools’. The BTS starts to send the TRACE MEASUREMENT RESULT messages to the BSC when it receives the START TRACE message from the BSC (see also parameter TRACEMR).e. for the BTS a TCH/SD is treated as a normal dual rate TCH if it is ‘idle’ or if it has received a CHANNEL ACTIVATION for channel type ‘TCH’. This means that the BTS might send idle channel measurements (see parameter INTCLASS in command SET BTS [INTERF]) during this period. even if TGUARDTCHSD is still running for a specific TCH/SD in the BSC (i. The sending is stopped when the BSC sends STOP TRACE message or when the call is released. this parameter determines whether the TRACE MEASUREMENT RESULT messages shall be sent by the BTS or not. the TCH/SD is still in the SDCCH_BACKUP_POOL).. see command CREATE CTRSCHED) are enabled. If it has received a CHANNEL ACTIVATION for channel type ‘SDCCH’. object: range: default: BSC [BASICS] TRUE. from point of view of the BTS the TCH/SD is treated as an dual rate TCH again.TRACEMG=1. it is treated as SDCCH. even if the TCH/SD is still in the SDCCH_BACKUP_POOL. FALSE TRUE the threshold SDCCHCONGTH that is performed during the SDCCH release procedure is different from the one that is performed in case of SDCCH assignment! . object: (unit: range: default: BSC [BASICS] 480ms) 1.

USSD Transactions . then USSD transactions will be counted together with all other standardized SCI procedures by the subcounter ‘SS Management’. the distinction between both cases is only possible if the BSC analyzes the contents of the FACILITY messages which are normally transparent for the BSS. object: range: default: BSC [BASICS] TRUE.other signalling procedures (Location Update. MTC) . One central requirement for the introduction of the counter MBUSYSSP was the possibility to count USSD procedures (Unstructured Supplementary Service Data) separately.considerably increases the TDPC processor load. this parameter is relevant for a new BR8. In this case the TDPC processor load is increased by the necessary additional analysis efforts. b) If TRANSPM is set to FALSE and the measurement MBUSYSSP is activated. This ‘in depth’ analysis of normally transparent messages. In this case the TDPC processor load is not affected. FALSE FALSE Transparent messages. The purpose of this counter is to allow a more detailed observation of the SDCCH traffic with respect to the traffic type that was processed via the allocated SDCCH. Different subcounters distinguish the mean number of busy SDCCHs for .) . the parameter TRANSPM was introduced to allow the operator to avoid the described TDPC performance impact if a separate counting of standardized SCI procedures and USSD transactions is not required: a) If TRANSPM is set to TRUE and the measurement MBUSYSSP is activated. For this reason.TRANSPM=FALSE. however. IMSI Detach etc.Short Message Service (SMS-MO and SMS-MT) . The subcounter ‘SS Management’ will only count all other standardized SCI procedures. As the general signalling message sequence for USSD transaction is exactly the same like for SCI procedures for standardized SS procedures. then USSD transactions will be counted separately by the subcounter for ‘USSD signalling’. USSD procedures are non-standardized Supplementary Service procedures that may be defined operator specifically and which allow the subscribers to control particular network-specifc services by entering specific service codes as key combination on the mobile phone.g.SS Supplementary Service Management (SCI) .abnormal SDCCH activations (e. 48 .Signalling for TCH connection (MOC.0 Performance Measurement Counter called ‘Mean number of busy SDCCHs per signalling procedure (MBUSYSSP)’. no ESTABLISH INDICATION received for activated SDCCH).

If the traffic load in the cell is above the cell-specific threshold TRFHITH. no further message is sent to the BTS and the traffic handover remains enabled in the affected BTS. based on the thresholds and the current TCH load the BSC detects the condition for compression or decompression handover. see command SET BTS [BASICS]) or/and b) the Abis pool TCH load towards a particular BTSM and compares it to the threshold ABISHRACTTHR and ABISFRACTTHR. In the BTS. b) Compression-Decompression handover: On every expiry of TRFCT the BSC checks a) the traffic load in its cells and compares it to the threshold HRACTAMRT1/HRACTAMRT2. object: unit: range: default: BSC [BASICS] 1 halfsecond 10. the BSC disables the traffic handover in the affected BTS by sending an LAPD O&M message SET ATTRIBUTE with the indication ‚traffic handover disabled’ to the BTS. If the traffic handover was already enabled for a specific BTS on the previous expiry of TRFCT and the traffic load in the affected BTS is still above the threshold TRFHITH. please refer to the parameter EADVCMPDCMHO (see command SET HAND [BASICS].. the timer TRFHOT (see SET HAND [BASICS]) is used to cyclically decrease the dynamic traffic handover margin. the BSC checks the traffic load in its cells and compares it to the traffic handover high threshold (see parameter TRFHITH in command SET HAND) set for the affected BTS. 49 . If the traffic handover was enabled for a specific BTS on the previous expiry of TRFCT and the traffic load in the affected BTS has decreased below the threshold TRFHITH. For further details. the BSC checks the traffic load in its cells and compares it to BTS specific thresholds associated to the following features: a) Traffic handover (see parameter TRFHOE in command SET HAND [BASICS]): When TRFCT expires. For further details please refer to the explanations provided for the remaining traffic handover parameters (see parameter TRFHOE in command SET HAND).TRFCT=20. the BSC enables the compression or decompression handover in the affected BTS by sending an LAPD O&M message SET ATTRIBUTE with the appropriate indication to the BTS. HRACTT1/HRACTT2 (for compression handover) and FRACTTH1/FRACTTH2 and FRACTAMRTH1/FRACTAMRTH2 (for decompression handover. This indication starts the Compression/Decompression handover decision process in the BTS. If. this parameter determines the time between two consecutive traffic load checks which are performed by the BSC. TRFCT is initialized on every initialization or startup of the TDPCs and is automatically restarted on every expiry. This O&M message is the trigger for the BTS to start the traffic handover decision algorithm (for more details please refer to the appendix ‚Handover Thresholds and Algorithms’). the BSC enables the traffic handover in the affected BTS by sending an LAPD O&M message SET ATTRIBUTE with the indication ‚traffic handover enabled’ ‚to the BTSM. A reasonable setting of the BSC traffic control timer TRFCT and TRFHOT is TRFHOT (HAND) > TRFCT (BSC) This timer combination ensures that the traffic load situation is checked by the BSC before the BTS initiates the next step of traffic handover margin reduction. 200 20 (=10 seconds) Traffic (handover) control timer. if the traffic handover remains enabled for a longer time period. When TRFCT expires.

Network controlled cell reselection distributes MSs among cells according to network criteria due to traffic conditions. but the parameterization takes place on a per cell basis. Type of Alarm Module C. NTWCREPPTR. NCGPENTIME (see command CREATE ADJC). NCTRFPSCTH. Based on cell traffic thresholds. TDDGQO. This parameter is only relevant if GPRS Network Controlled Cell Reselection was enabled by setting the parameter NCRESELFLAG to ENABLE (see above). NCGTEMPOFF. the traffic is distributed among the cells belonging to the same PCU (Packet Control Unit) within the appropriate BSC. this parameter defines the type of the equipped alarm module card. this parameter determines the type of Ethernet adopted for the internal LAN. this parameter determines whether the feature ‘GPRS traffic control strategy’ is enabled for GPRS Network Controlled Cell Reselection in the BSC. The BSS updates the internal references that indicate the location of the MS. GFDDREPQTY and GUMTSSRHPRI (see command CREATE PTPPKF) and NCGRESOFF. FALSE FALSE TYPOFAMC=DK40.TRFPS=FALSE. TRFPSCTRLT. Through these network criteria. For further details please refer to the parameters CRESELTRHSOUT.0. UPGRFREQ Moved to CPCU object in BR8. object: range: BSC [BASICS] DK40. ES Traffic control packet switched. object: range: default: BSC [BASICS] ETHERNETII. object: range: default: BSC [BASICS] TRUE. the Traffic Control Network Controlled Cell Reselection is applied for GPRS and EGPRS in order to spread the load by transferring some traffic towards the neighbour cells. 50 . CRESELTRHINP. TYPOFETH=DK40. In case of traffic congestion within one cell. NTWCREPPIDL. GNMULBAC. CPEX. and a better traffic distribution among the available channels is established in all the available cells of one BSC. IEEE802 ETHERNETII Type of Ethernet. and related information is sent to the serving GPRS support nodes involved. NTWCNDRXP. the optimum use of re-sources is achieved. This feature is enabled per BSC.

> BRIDGE BSC: NAME=BSC:0. PLUTO = 55. TAPPO = BTSM:5/BTS:1. The ATTx parameter value consists of two parts a) a parameter name. ATT3 = “CIP” . ATT2.b(TRUE). which consists of a symbolic name string (max. 15 characters) and b) the associated parameter value as defined by R&D.p(BTSM:5/BTS:1). default: 51 .NULL(0).. already known and used by customers. required by change requests (CR) in the latest phases of a release. can be moved into the specific command/object of the info model in correspondence with the parameters’ association to a particular object. The association of this parameter to a particular database command and object is defined by the parameters RELCMD and RELOBJ (see below). BRIDGE BSC allows the introduction/management of new configurable database parameters. The databases are automatically converted correctly by DBAEM and CONVFILE tools. the following example may illustrate the application of the BRIDGE BSC command BRIDGE BSC:BSC:0. this parameter allows the definition of a new attribute name and its attribute value. PIPPO = <NULL>. these parameters allow the definition of additional parameters and valuese (see parameter ATT1).. ATT2 = “PLUTO” . object: format: range: BSC parameter name parameter value parameter name: “<15 characters string>” parameter value <value as defined by R&D> <NULL> default: Object path name. ATT5 = “TAPPO” . The equivalent for this command in classic syntax would be: SET BTS: NAME=BTSM:2/BTS:3.s(“OK”). CIOP = “OK”. Attribute 8. object: format: range: BSC parameter name parameter value parameter name: “<15 characters string>” parameter value <value as defined by R&D> <NULL> Attribute 2 . In the subsequent releaseses the management of these new database parameters. ATT4 = “CIOP” . Attribute 1. ATT1=<NULL>. Nearly all CRs introducing new functionalities require an enabling/disabling mechanism. without any further InfoModel change.Creating new database parameters without info model change: <The BRIDGE BSC command was introduced to avoid high development cost CR solutions that are introduced on customer pressure within a life cycle of a release. ATT1 = “PIPPO” . RELOBJ = BTSM:2/BTS:3. CIP = TRUE. RELCMD = SET.i(55).ATT8=<NULL>. In general the modelling of attributes is decided in accordance with R&D. and most of them require also some specific attributes.

determines the alarm severity of the IPLI (IP link for connetion to RC/) object 52 . GET <NULL> Related command. this parameter defines the association of the defined attributes (ATT1. ALRMSEVBTS=CRITICAL. Critical Major ALRMSEVBTSTD= CRITICAL. object: range: default: BSC [ALARMSEV] Minor. ALRMSEVBTSMTD=MAJOR.ATT5) to a particular database command. Setting the alarm priorities of the BSS functional objects: Attention: Since BR6. ALRMSEVCBCL =MAJOR. Critical Major Alarm severity IPLI. Alarm severity BTS. object: range: default: BSC [ALARMSEV] Minor. RELOBJ=<NULL>. determines the alarm severity of the CBCL object. Critical Minor Alarm severity FRL. Critical Critical ALRMSEVBTSM=MAJOR. Object path name. Critical Major Alarm severity BTSM.RELCMD=<NULL>. SET BSC [ALARMSEV]: NAME=BSC:0. all parameters of the previous ‘BSC packages’ were moved below the object BSC and appear in the DBAEM in the SET BSC command. determines the alarm severity of the BTSM object. determines the alarm severity of the BTSMTD (BTSM for TD-SCDMA) object object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the BTS object.0 The DBAEM does not group the command parameters into ‘packages’ anymore.ATT5) to a particular database object. Alarm severity BTSMTD. this parameter defines the association of the defined attributes (ATT1. ALRMSEVFRL=MINOR. Critical Major Alarm severity CBCL. The logical group “[ALARMSEV]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . Major. object: range: default: BSC <object path name> <NULL> Related object. Major. determines the alarm severity of the FRL object. ALRMSEVIPLI=MAJOR. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. Major. Major.. Instead. Major. determines the alarm severity of the BTSTD (BTS for TD-SCDMA) object.. Major. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC SET. object: range: default: BSC [ALARMSEV] Minor. Major. Critical Critical Alarm severity BTSTD.

determines the alarm severity of the OMAL object.ALRMSEVLPDLM=MAJOR. Critical Major Alarm severity PCMG. object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the PCMG object. (LPDLM for TD-SCDMA BTSM). Major. ALRMSEVPCMA=MAJOR. Major. ALRMSEVNSVC=MINOR. determines the alarm severity of the PCMA object. Critical Major Alarm severity PCMA. Major. ALRMSEVOMAL=MAJOR. Major. 53 . object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. Critical Major Alarm severity LPDLRTD. Major. ALRMSEVPCMS=MAJOR. Major. ALRMSEVPCMG=MAJOR. object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the NSVC object. Major. ALRMSEVLPDLRTD= MAJOR. ALRMSEVLPDLMTD= MAJOR. Critical Major Alarm severity LPDLS. Critical Major Alarm severity LPDLR. determines the alarm severity of the LPDLS object. Major. ALRMSEVLPDLR=MAJOR. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. ALRMSEVPCMB=MAJOR. (LPDLR for TD-SCDMA TRX). Critical Major Alarm severity OMAL. Critical Major Alarm severity PCMS. Critical Major Alarm severity LPDLMTD. determines the alarm severity of the LPDLM object. Major. ALRMSEVLPDLS=MAJOR. determines the alarm severity of the PCMS object. determines the alarm severity of the LPDLMTD object. Critical Minor Alarm severity NSVC. Major. Critical Major Alarm severity PCMB. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. Major. object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the PCMB object. determines the alarm severity of the LPDLRTD object. object: range: default: BSC [ALARMSEV] Minor. Critical Major Alarm severity LPDLM. determines the alarm severity of the LPDLR object.

ALRMSEVPTPPKF=MAJOR. 54 . Major. Critical Critical Alarm severity PCU. object: range: default: BSC [ALARMSEV] Minor. Critical Critical Alarm severity TRAU. ALRMSEVTRAU=CRITICAL. object: range: default: BSC [ALARMSEV] Minor. Major. ALRMSEVTRX=MAJOR. Critical Major Alarm severity TRX. object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the TRAU object. Major. ALRMSEVTRXTD=MAJOR. Critical Critical Alarm severity TDCU. object: range: default: BSC [ALARMSEV] Minor. object: range: default: BSC [ALARMSEV] Minor. ALRMSEVPCUTD= CRITICAL. object: range: default: BSC [ALARMSEV] Minor. determines the alarm severity of the TDCU (TD-SCDMA control unit) object. Major. Major. ALRMSEVTDCU=CRITICAL. Critical Critical Alarm severity PCUTD. determines the alarm severity of the PTPPKF object.ALRMSEVPCU=CRITICAL. object: range: default: BSC [ALARMSEV] Minor. Critical Major Alarm severity PTPPKF. determines the alarm severity of the TRXTD object (TRX in TD-SCDMA BTS). Critical Major Alarm severity TRXTD. Major. determines the alarm severity of the PCU object. Major. determines the alarm severity of the TRX object. determines the alarm severity of the PCUTD (PCU for TD-SCDMA packet switched services) object.

this attribute defines the position of the Network Element. Major. object: range: default: BSCE [ALARMSEV] Minor.0 The DBAEM does not group the command parameters into ‘packages’ anymore. object: range: default: BSC[REMINV] ENABLED. Major.Setting the remote Inventory data of the BSC Equipment: Attention: Since BR6. Critical Minor ALRMSEVDISK=MAJOR. Instead. ALRMSEVCPEX=CRITICAL. SALUNAME=”BSC1”. EAUTOREC=ENABLED. determines the alarm severity of the CPEX object (the CPEX (Control Panel and External alarms device) is the card which reports to MPCC 16 external alarms and the FAN alarm and controls the fuse and alarm panel. all parameters of the previous ‘BSCE packages’ were moved below the object BSCE and appear in the DBAEM in the SET BSCE command. object: range: default: BSC [REMINV] alphanumeric string (11 characters) in quotation marks NOT_DEFINED EQPOS=”010101”. all parameters of the previous ‘BSCE packages’ were moved below the object BSCE and appear in the DBAEM in the SET BSCE command. DISABLED DISABLED Enable auto recovery. Alarm severity CPEX. Sales Unique Name. Instead. Major. determines the alarm severity of the DK40 object. this attribute enables the automatic recovery. Alarm severity DISK. Setting the alarm priorities of the BSCE objects: Attention: Since BR6. SET BSCE [REMINV] : NAME=BSCE:0. Critical Major Alarm severity DK40. object: range: default: BSC [REMINV] alphanumeric string (6 characters) in quotation marks “010101” Equipment position. The logical group “[ALARMSEV]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . this attribute defines the BSC Network Element by its unique symbolic name. 55 .0 The DBAEM does not group the command parameters into ‘packages’ anymore. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the DISK object. SET BSCE [ALARMSEV]: NAME=BSCE:0. Object path name. The logical group “[REMINV]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . Critical Major ALRMSEVDK40=MAJOR. Object path name. object: range: default: BSCE [ALARMSEV] Minor.

determines the alarm severity of the MPCC object. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the ME2M object. Major. Major. determines the alarm severity of the EPWR object. object: range: default: BSCE [ALARMSEV] Minor. object: range: default: BSCE [ALARMSEV] Minor. ALRMSEVIXLT=MAJOR. determines the alarm severity of the PPXL object. ALRMSEVPPCC ALRMSEVPPCUFehler! Textmarke nicht definiert. Major. Critical Minor Alarm severity LICDS. Critical Major Alarm severity EPWR. Critical Major Canceled in BR8. determines the alarm severity of the LICD object. Critical Major Alarm severity IXLT. object: range: default: BSCE [ALARMSEV] Minor. object: range: default: BSCE [ALARMSEV] Minor. ALRMSEVPPXP=MINOR. Critical Major Alarm severity MPCC. object: range: default: BSCE [ALARMSEV] Minor.0 Canceled in BR8. determines the alarm severity of the IXLT object. ALRMSEVPPLD ALRMSEVPPXL=MINOR.0 Alarm severity PPXL. Major. Critical Major Alarm severity NTW. Major. determines the alarm severity of the NTW object. Major. Major. ALRMSEVMPCC=MAJOR. Major. object: range: default: BSCE [ALARMSEV] Minor.0 Canceled in BR8. Critical Minor Alarm severity LICD. Critical Min or Alarm severity PPXP. ALRMSEVNTW=MAJOR. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the PPXP object. Major. ALRMSEVLICDS=MINOR. object: range: default: BSCE [ALARMSEV] Minor.ALRMSEVEPWR=MAJOR. object: range: default: BSCE [ALARMSEV] Minor. Major. ALRMSEVMEMT=MAJOR. determines the alarm severity of the LICDS object. ALRMSEVME2M=MAJOR. determines the alarm severity of the MEMT object. 56 . ALRMSEVLICD=MINOR. Critical Major Alarm severity ME2M. Critical Major Alarm severity MEMT.

Major. Critical Major Alarm severity TDPC. object: range: default: BSCE [ALARMSEV] Minor. ALRMSEVTDPC=MAJOR. ALRMSEVPWRD=MAJOR. Major. determines the alarm severity of the TDPC object.ALRMSEVPPXT=MINOR. Major. Critical Major Alarm severity X25D. ALRMSEVX25A=MAJOR. Major. determines the alarm severity of the SYNC object. determines the alarm severity of the SYNE object. Major. ALRMSEVX25D=MAJOR. Object path name. 57 . Critical Min or Alarm severity PPXT. Creating the Power Supply: CREATE EPWR: NAME=EPWR:0. Major. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the X25A object. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the PPXT object. ALRMSEVSYNE=MAJOR. Critical Major Alarm severity PWRD. ALRMSEVPPXU=MINOR. object: range: default: BSCE [ALARMSEV] Minor. determines the alarm severity of the PWRD object. object: range: default: BSCE [ALARMSEV] Minor. Critical Min or Alarm severity PPXU. Critical Major Alarm severity X25A. ALRMSEVSYNC=MAJOR. Critical Major Alarm severity SYNC. determines the alarm severity of the X25D object. Critical Major Alarm severity SYNE. Major. object: range: default: BSCE [ALARMSEV] Minor. object: range: default: BSCE [ALARMSEV] Minor. Major. determines the alarm severity of the PPXT object. object: range: default: BSCE [ALARMSEV] Minor.

e.PPLD is no longer supported in BR8.1s 2-254 10=1s ALARMT3=5. i.Creating the spare PCM interface boards: CREATE LICDS: NAME=LICDS:0. PCM alarm counter. object: unit: range: default: LICD 0. object: unit: range: default: LICD 1 2-254 32 Object path name. object: unit: range: default: LICD 0.1] error-free seconds. after [ALARMT2∗ 0.0! 58 . the line returns to service after [ALARMT1∗ 0. Object path name.TSBS) (for TGUARD and TSBS see command CREATE OPC [BASICS]). Rules: 1) ALARMT2 < (TGUARD . determines the timeframe for the counting of PCM line errors. determines the threshold for errors that lead to a PCM alarm (see also previous parameter ALARMT3). ALARMT2=2.1] seconds of line alarm the line is disabled. It avoids A-interface reset (and thus call release) procedures even if the link interruption is very short. PCM alarm timer 3. A PCM line is set in ‘alarmed state’ if <ALACOUNT> line errors are detected within [ALARMT3∗5] minutes CREATE PPLD Canceled . object: unit: range: default: LICD 5 min 1-254 1 PCM alarm timer 2 determines the time (1 unit = 0. ALACOUNT=32.1s) after which an disturbed PCM line is put out of service. 2) ALARMT2 < TSYNC and ALARMT2 < TTRAU (for TSYNC and TTRAU see command SET BTS [TIMER]) This setting is necessary in order to avoid call release before PCM alarm detection. ALARMT1=20. Creating the PCM interface boards: CREATE LICD: NAME=LICD:0. This setting is only valid if the LICD is used for connection of a PCMS. i.1s 2-254 200=20s PCM alarm timer 1 determines the error-free time after which a previously alarmed PCM line is put back to service.e.

stops scheduling RLC/MAC blocks for this USF and starts timer T3169. N3101 represents a counter on the network side: If the network receives a valid data block from the MS after setting the Uplink State Flag (USF).Creating the common attributes for all PCUs belonging to the entire BSC: < The CPCU object was introduced with BR8. this parameter is the Low Pass Filter Coefficient used to filter Leak_Rate oscillation. object: range: default: CPCU 1. The counter is incremented for each USF for which no valid data is received. 99 50 Download BSS PFC Timer. object: unit: range: default: CPCU 100ms 2. QTLP) . Please note that many parameters were moved from the PCU object to the CPCU object in BR8.. MODBSSPFCRET=3. this parameter guards the DOWNLOAD-BSS-PFC-RETRIES number.0 to define attributes common for several PCUs belonging to the BSC. N3101 is reset. The filtering applied is the following: Rmax_eFC=alpha*Rmax(Tnow)+(1-alpha)*Rmax(Tnow-C). 5 3 MODBSSPFCT=50. object: range: default: CPCU 1.11 The supported values for pcun depend on the used HW: ....….. If N3101 reaches the threshold value. STLP) Download BSS PFC Retries.pcun = 0.0.255 20 Default value changed in BR8..5 HC BSC 72 (PPXX. FCRATE=100. this parameter represents the timer T6 and guards the MODIFY-BSS-PFC procedure.. the PCU considers the TBF lost. DNLBSSPFCRET=3. this parameter guards the MODIFY-BSSPFC-RETRIES number. Modify BSS PFC Retries. this parameter represents the timer T6 and guards the DOWNLOADBSS-PFC procedure. 5 3 DNLBSSPFCT=50.0! This parameter defines the threshold for non-valid-data error coming from the mobile station after having sent USF. Range for pcun = 0.11 HC BSC 120 (PPXX.…. object: range: default: CPCU 9. object: unit: range: default: PCU 100ms 2. 100 100 Lowpass filter coefficient leak rate.. 59 .0. object: range: default: CPCU 0.pcun = 0. Note: This parameter was moved from the PCU object to the CPCU object in BR8. > CREATE CPCU: NAME=CPCU:0. N3101=20. 99 50 Modify BSS PFC Timer. Object path name.

N3103 represents a counter on the network side: If the network receives PACKET CONTROL ACK from the MS as response to a final PACKET UPLINK ACK/NACK. Number of RA capability update retries. If a BVC-BLOCK PDU is not acknowledged within T1 seconds from the SGSN. 255 10 N3105=10.0. This parameter defines the threshold for not received RLC/MAC control message as response to a polled RLC/MAC data block. If a BVC-UNBLOCK PDU is not acknowledged within T1 seconds from the SGSN.N3103=10. N3105 is reset.0. the reset procedure is repeated at maximum NBVCRR times. If the network does not receive the PACKET CONTROL ACK in the scheduled block. Number of BVC Reset Retries. the network regards the communication with the MS lost. stops transmitting RLC data blocks and starts T3195. object: range: default: CPCU 1. N3105 represents a counter on the network side: If the network receives a valid RLC/MAC control message from the TBF. the BVC status shall be blocked and an O&M alarm is generated. Number of BVC Block Retries. The counter is incremented for each radio block allocated to that TBF with the RRBP field set. After NBVCUR unsuccessful reattempts. 30 3 NBVCUR=3.0.0. This parameter is used within the BVCI block procedure. for which no RLC/MAC control message is received. object: range: default: CPCU 1.. N3103 is incremented and the PACKET UPLINK ACK/NACK message is retransmitted. timer T3169 is started. the unblocking procedure is repeated at maximum NBVCUR times. This parameter is used within the BVCI unblock procedure.. 60 . the BVCI status remains blocked and an O&M alarm is generated.. After NBVCBR unsuccessful reattempts. 30 3 This parameter defines the threshold for not received PACKET CONTROL ACK as response to PACKET UPLINK ACK/NACK messages. object: range: default: CPCU 1.. If N3105 reaches the threshold value. 30 3 NRACPBLUPDRET=3. Note: This parameter was moved from the PCU object to the CPCU object in BR8. this parameter provides the maximum number of retransmission of RA-Capability-Update to SGSN when BSC does not accept correspondent answer (RACapability-Update-Ack) from SGSN. Note: This parameter was moved from the PCU object to the CPCU object in BR8. object: range: default: CPCU 1. object: range: default: CPCU 1. Note: This parameter was moved from the PCU object to the CPCU object in BR8. After NBVCRR unsuccessful reattempts. N3103 is reset. Note: This parameter was moved from the PCU object to the CPCU object in BR8. the blocking procedure is repeated at maximum NBVCBR times. Number of BVC Unblock Retries. If N3103 reaches the threshold value. 255 10 NBVCBR=3. If a BVC-RESET PDU is not acknowledged within T2 seconds from the SGSN.. object: range: default: CPCU 1..0. Note: This parameter was moved from the PCU object to the CPCU object in BR8. the BVCI status remains blocked and an O&M alarm is generated. This parameter is used within the BVCI reset procedure. 30 3 NBVCRR=3..

this parameter represents the timer guarding reutilisation of preallocated resources for Real Time Packet Flow Context (RTPFC). In case the DL TBF TBF is allocated on 4 timeslots. object: range: default: CPCU TRUE. object: range: default: CPCU 20. FALSE TRUE Default value changed in BR8. 29 10 System Information SGSN release 99. In case of timeout the procedure is repeated (refer to parameters NBVCBR and NBVCUR). This setting has a similar function like the parameter SIMSCREL99 (see above). the effective polling distance is defined by (NRLCMAX-12). Faster polling allows the quick retransmission of not acknowledged blocks and therefore helps to avoid a stall condition on RLC/MAC layer (with only 64 blocks window size in case of GPRS). 99 procedures such as cell selection between 2G and 3G. there is no way to check the release compliance of the SGSN) to avoid protocol errors. If SISGSNREL99 is set to TRUE (and thus the ‘SGSN Revision’ bit is set to ‘1’ in the SYSINFO 13). This behaviour applies for DL transfers with 1 or 2 timeslots allocated. In case the DL TBF is allocated on 3 timeslots. During DL TBFs: In average every NRLCMAX-th DL data block is polled (RRBP set) to request a PACKET DOWNLINK ACK/NACK from the mobile. object: unit: range: default: CPCU 1s 2. 61 . It is up to the network operator to set the value of this parameter in correspondence with the real conditions (for the BSC.0. th th This reduced polling period (every 15 /8 block) is required to optimize the throughput under field conditions. which is a mandatory precondition for specifc Rel. This applies under all circumstances for the currently supported MS multislot classes 1-10 (max. it waits maximum T1 seconds for the respective acknowledgement. Note: This parameter was moved from the PCU object to the CPCU object in BR8.NRLCMAX=20. object: unit: range: default: CPCU 100ms 0. Note: This parameter was moved from the BSC object to the CPCU object in BR8. SISGSNREL99=TRUE.64 20 PREAT=20. This timer defines the Waiting time for BVCI block/unblock procedure.. the effective polling distance is defined by (NRLCMAX-5). It indicates that the Mobile Stations are allowed to use release-99-specific messages/information elements in their signaling towards the network. During UL TBFs: After each reception of NRLCMAX UL data blocks the PCU issues a PACKET UPLINK ACK/NACK message. this parameter determines the value of the ‘SGSN Release’ bit in the SYSTEM INFORMATION TYPE 13.1 to control the “SGSN Release“ bit in the SYSINFO 13. Preallocation timer. 2 UL timeslots).0.0! T1=10.0. 100 20 This parameter specifies the rate of PACKET UPLINK ACK/NACK and PACKET DOWNLINK ACK/NACK messages being used during packet transfers in RLC/MAC acknowledged mode. the MSs are allowed to send Release-99-specific messages and information elements in their signaling messages towards the network. The parameter SISGSNREL99 replaces the setting MNTBMASK=BIT9 which was used in BR6... After the PCU has sent a BVCI block/unblock message. Note: This parameter was moved from the PCU object to the CPCU object in BR8.0/BR6.

Note: This parameter was moved from the PCU object to the CPCU object in BR8. It is stopped when the MS has correctly seized the TBF. In case of timeout the procedure is repeated (refer to parameter NBVCRR). 30 5 T3141. this timer defines the time to wait for a reuse of the TFI after reception of the final Packet Downlink Ack/Nack from the mobile station. object: unit: range: default: CPCU 1s 1. 100 50 (= 5s) This timer defines the Waiting time for BVCI reset procedure. T3191.. it waits T2 seconds for acknowledgement. Note: This parameter was moved from the PCU object to the CPCU object in BR8. Note: This parameter was moved from the PCU object to the CPCU object in BR8. object: unit: range: default: CPCU 100 ms 1-42 4 T3172.0. this timer defines the waiting time for a response from the SGSN after sending a SUSPEND PDU..255 5 T3191=5. Note: Setting T3193 to the value 4 (=400ms) still fulfils the above rule due to system-internal propagation times. Note: This parameter was moved from the PCU object to the CPCU object in BR8.0. After the PCU has sent a BVCI reset message. Important is that T3193 expires after T3192 surely elapsed (ensuring that the MS already abandoned this TFI).. is a timer running on the mobile side.. Default value changed in BR8. the newly allocated TBF is released. If T3141 elapses before a successful contention resolution procedure is completed. this timer defines the waiting time for reuse TFI after having sent the last RLC block. object: unit: range: default: CPCU 1s 2.0! T3172=5. object: unit: range: default: CPCU 1s 1. object: unit: range: default: CPCU 1s 1-30 5 T3193=4. It is included in the PACKET ACCESS REJECT message and indicates the time the mobile station shall wait before attempting another packet channel request. T3141=5. On expiry the network releases the TFI allocated to that TBF. On expiry the TFI resources are released.0. 119 10 T3=50.0. Note: This parameter was moved from the PCU object to the CPCU object in BR8. T3193. Note: This parameter was moved from the PCU object to the CPCU object in BR8. Rule: T3193 > T3192 (default = 500ms).0. this timer is started on the network side when a TBF is assigned with an IMMEDIATE ASSIGNMENT message during a packet access procedure.0..T2=10. this timer defines the waiting time to reuse the respective TFI and USF values after the thresholds N3101 and N3103 (see parameters above) were reached. T3. 30 5 T3169=5. It is started with the last DL data block sent in a TBF (Final Block Indicator=1) and stopped with the reception of the final PACKET DOWNLINK ACK/NACK (or PACKET CONTROL ACK). object: unit: range: default: CPCU 1s 0. 62 . T3169. object: unit: range: default: CPCU 0.1s 1.

However..0! T4=10. this timer defines the time to wait for a reuse of the TFI after the threshold N3105 (see above parameter) was reached. the TCH is always regarded as ‘downgradable’ resp. the allocated PDCH(s) for the “released” TBF are still regarded as allocated even if they are not used for the transfer of payload.. If GPRS/EGPRS calls are set up. the assignment of the Abis interface subslots related to these PDCHs. (which means that there is no ongoing TBF on the TCH). 254 30 Default value changed in BR8.e. The PPXU always knows the number of PDCHs (i. This change was implemented in BR7. i. Default value changed in BR8. As long as TEMPCH is running. Timer Empty Channel.0 in the scope of CR1150 (see also parameters DGRSTRGY (in command CREATE BTS [BASICS]. The purpose of this timer is to avoid continuous channel allocation requests from the PCU to the TDPC and the associated CHANNEL ACTIVATIONs and IMMEDIATE ASSIGNMENT procedures which would happen in periods of high GPRS/EGPRS traffic if the allocated resources were directly released after the stop of the TBF activities on the allocated TCHs. T5=10. in periods of TCH congestion the BSC immediately releases PDCHs (TCHs activated for GPRS) with TEMPCH running if a CS TCH request is received and no other idle TCH is available for allocation. object: range: default: CPCU 2.0! 63 . the TDPC is responsible for 1. the assignment of the proper radio resources on the air interface (PDCHs) and 2.255 5 T3195. Main reasons for N3105 expiry are radio link failure or cell reselection. if a TCH was activated as PDCH for GPRS traffic but the TEMPCH timer is running for it. radio TCHs used as PDCH) in use in a particular cell at a given time. this timer defines the waiting time for a response from the SGSN after sending RESUME PDU.e.1s 1. 29 10 T5. this timer specifies the delay time for the release of an allocated PDCH if there are no TBF activities. 100 10 (= 1s) T4.. These allocated PDTCHs can assume two main states: either a) at least one TBF is currently assigned on the PDCH or b) the last TBF on the PDCH has been stopped. no matter which value was set for the DGRSTRGY parameter (see command CREATE BTS [BASICS]).0. In other words. The timer TEMPCH is started on the stop of the last TBF and keeps the allocated TCH activated to serve possible new TBFs. this timer is started from BSC when RA-Capability-Update is stransmitted to SGSN and stops it when RA-Capability-Update-Ack is received. object: unit: range: default: CPCU 0. when the last MS associated to a PDCH is released (no TBF is ongoing on the PDCH anymore) the “virtual” assignment of the PDCH persists for the duration of the timer TEMPCH. ‘preemptable’ for CS calls. TEMPCH=30.. Note: This parameter was moved from the PCU object to the CPCU object in BR8. object: unit: range: default: CPCU 1s 0. object: unit: range: default: CPCU 1s 1.T3195=5.

0. the assignment of the proper radio resources on the air interface (PDCHs) and 2.TEMPPDT=1. 9 5 08.g. The value of TEMPPDT must be smaller than TEMPCH. object: unit: range: default: CPCU 1s 0. object: unit: range: default: GSM: CPCU 1s 2. due to a downgrade of the used coding scheme).0. when SGSN receives PFC FLOW CONTROL parameters. this parameter is the equivalent to the parameter TEMPCH (see above) for Packet Data Terminal (PDT) resources allocated on the PCU. SGSN starts TH Timer. when SGSN receives MS FLOW CONTROL parameters. TF=6. the TDPC is responsible for 1.. When TF expires SGSN may use SGSN Bmax and R generated and not more last Bmax and R sent by BSC.0! TH=6. object: range: default: CPCU 6. 30 15 TEXTULTBF=15. Note: This parameter was moved from the PCU object to the CPCU object in BR8.. only 3 of the previously 5 Abis subslots (and PDTs) are necessary to transport the user data for each PDCH. TF is restarted each time a PFC FLOW CONTROL parameters are received. As soon as the coding scheme MCS6 is applied from the PCU. 5999 ??? TH.. Note: This parameter was moved from the PCU object to the CPCU object in BR8.. The timer TEMPPDT is used to avoid continuous requests for Abis resources from the PCU to the TDPC. this attribute is used to delay the release of an UL Temporary Block Flow (TBF) in Extended UL TBF mode. Default value changed in BR8. TEMPPDT is started at that moment for the 2+2 affected PDTs (with subframe counter 3 and 4) – and if no upgrade to a higher coding scheme occurs within the runtime of TEMPPDT (or another MS using MCS9 is vertically allocated. object: unit: range: default: CPCU 1s 1. Each of the PDCHs has five 16kbit/s Abis subslots allocated – in total 10 PDTs are in use on PCU side.18 TF. This timer defines the Time for capacity reporting period used in flow control algorithm. When TH expires SGSN may use SGSN Bmax and R generated and not more last Bmax and R sent by BSC. the assignment of the Abis interface subslots related to these PDCHs. 5999 ??? TF1=5. 64 . object: range: default: CPCU 6. etc. Example situation: An MCS9 DL TBF is allocated on 2 radio timeslots (PDCH).. Let us assume a sudden downgrade of the coding scheme to MCS6 now (due to bad radio conditions). TH is restarted each time a MS FLOW CONTROL parameters are received. 49 15 Timer for empty PDT. It corresponds to the C timer reported in the GSM 8.) these 4 Abis resources are released. If GPRS/EDGE calls are set up. TEMPPDT determines the delay time for the release of an allocated PDT with subframe counter > 0 if the related PDCH does not require this PDT anymore (e. Time extended Uplink TBF. SGSN starts TF Timer.18 recommendation and specifies the minimum time period allowed between two consecutive FLOW-CONTROL PDUs.

object: format: unit: range: default: CPCU thproxt1-thproxt2-thproxt3 thproxt1: 1ms thproxt2: 1s thproxt3: 1s thproxt1: 10. This functionality is important for mobiles with multislot class 6 (3+2. Note: This parameter was moved from the PCU object to the CPCU object in BR8.g can be used either in 3+1 or in 2+2 configuration. If ‘RLC_Octet_Count’ exceeds the value of THSULBAL. the relative PFC_Buffer is de-allocated and Downlink TBF Scheduling Weight Updating Algorithm is started..0. only a single timeslot was allocated in UL.1000 500.. represents a timer to activate the ‘uplink priority’ condition. object: range: default: CPCU 0.999 thproxt2: 1. This allows a faster transfer of new DL data arriving on the Gb-interface (DL TBF already open) and a faster setup of new UL TBFs (as concurrent TBFs). Therefore they are not used by the system.. so there is a trade-off between the maximum possible UL and DL speed..550 THSULBAL=587. 30 20 Threshold Proximity Timer.550. this timer is used to delay the release of an ongoing DL TBF. Timer switch uplink balanced.0... If however the resulting UL TBF lasts longer than TSULBAL. Timer PFC buffer. 49 15 TPFCBUFF=20 object: unit: range: default: CPCU 1s 5. the system allocates two PDCHs in uplink direction instead of preferring the downlink direction (while a concurrent DL TBF is active). this timer is defined for each allocated PFC_Buffer. the system activates the ‘uplink priority’ condition and upgrades the UL TBF resources if applicable. 2000 587 TIMEDTBFREL=15 object: unit: range: default: CPCU 100ms 0.. When it expires. total 4) and 10 (4+2. therefore we strongly recommend to set the default values unless otherwise officially specified! Threshold switch uplink balanced.. It is stopped and cancelled if new LLC Frames are coming for that PFC_Buffer. object: range: default: CPCU 0. TSULBAL=20. this parameter indicates the threshold that the field ‘RLC_Octet_Count’ (part of the Channel Request Description IE) has to exceed to activate an ‘uplink priority’ condition..0. At the current stage of BR70 no official released functionalities are controlled by them.100 thproxt3: 101. Note: This parameter was moved from the PCU object to the CPCU object in BR8. Please see also parameter THSULBAL.50. Note: These timers were implemented based on older specifications which are no more valid now.THPROXT=500. If an UL TBF was originally opened with RLC_Octet_Count <= THSULBAL (assuming a small amount of data to be transferred). It is started when PFC_Buffer gets empty. Time delay for TBF release. The network decides based on THSULBAL and TSULBAL which configuration is preferred.. Caution: These three parameters were repeatedly “abused” for development and system test purposes in order to implement additional test features – partly also customer relevant features.50. Note: This parameter was moved from the PCU object to the CPCU object in BR8. Dummy LLC-PDUs are inserted to keep a DL-TBF open for the specified time interval. A class 6 mobile e. Please see also parameter TSULBAL.100 20 65 . total 5).. this parameter implements 3 thresholds for TH-proximity evaluation.

…. The minimum time between two consecutive packet resource upgrade attempts is 1 second (value SEC1).pcun = 0.5 HC BSC 72 (PPXX. QTLP) . object: format: range: default: CPCU <uplink> .11 66 .. 63 0 Best effort PFI to Different Service. object: range: PCU 0. this parameter represents the CPCU object number to which this PCU belongs. BCGRTODIFFSERV=0.pcun = 0. 63 0 BEPFITODIFFSERV=0. The creation of a PCU implies the creation of a PPXU card (same instance number as the PCU) if NTWCARD = NTWSNAP or NTWSNAP_STLP. Object path name. For details about the calculation and the upgrade of radio resources due to a drop of the MST please refer to the parameter ACCEPTGDEGR (see above). Note: The check also considers timeslot upgrades for mobiles that were initially allocated less timeslots than requested (lack of resources) or downgraded during TBF operation by higher priorized CS connections. either the BLER or the used CS/MCS coding scheme can change. STLP) Background to Different Service. this parameter represents the mapping between background class and DSCP coding.11 The supported values for pcun depend on the used HW: . object: range: default: PCU 0.. this parameter represents the mapping between predefined PFI best effort parameter and DSCP coding.<downlink> SEC1. leading to a change in the ‘maximum sustainable throughput’.UPGRFREQ=SEC1-SEC1.SEC8 (both fields) SEC1 (both fields) Upgrade frequency for packet switched traffic.. During a TBF lifetime.0.. Note: This parameter was moved from the BSC object to the CPCU object in BR8. Range for pcun = 0.11 HC BSC 120 (PPXX. The BSC periodically performs a check of the current maximum sustainable throughput (MST) and compares it to a particular threshold which is individually calculated on the basis of the parameter ACCEPTGDEGR. due to variations in radio conditions. Creating the PCU objects: < The PCU functional object represents the packet control unit designed to implement GPRS/EDGE services in the SBS. the maximum time is limited to 8 seconds.…. Common PCU number.. object: range: default: PCU 0. CREATE PCU: NAME=PCU:pcun. CPCUN=0. this parameter controls the time to pass between two consecutive radio resource upgrade attempts for packet services separately for the uplink (first field of parameter value) and the downlink (second field of parameter value) in steps of 1 second.

0 Moved to CPCU object in BR8. object: range: default: PCU FRFIX. the size of the largest packet that can be transmitted on the Ethernet. object: range: default: PCU 0. object: range: default: PCU 68 . this parameter represents the mapping between interactive class with traffic handling 3 and DSCP coding. The default value of this parameter depends on the value of GBSNS attribute: GBSNS (value) MTU (default) FRFIX NULL IPV4 1500 INTRTRFH1TODIFFSERV=0..DIFFSERVSUP=<NULL>.0 Moved to CPCU object in BR8. this parameter represents the mapping between interactive class with traffic handling 1 and DSCP coding. this parameter indicates the maximum transmission unit.0 Moved to CPCU object in BR8. object: range: default: PCU DISABLED (0) ENABLED (1) <NULL> see description Different Service Support..0 Moved to CPCU object in BR8.. Interactive traffic handling priority 3 to Different Service. Maximum transmission unit. object: range: default: PCU 0. this parameter indicates the sub network service used for CPU.0 Moved to CPCU object in BR8. the default of DIFFSERVSUP depends on the value of GBSNS attribute: GBSNS (value) DIFFSERVSUP (default) FRFIX NULL IPV4 DISABLED GBSNS=FRFIX. INTRTRFH2TODIFFSERV=0. Interactive traffic handling priority 1 to Different Service.0 67 .. PV4 FRFIX Gb subnetwork service. 63 0 INTRTRFH3TODIFFSERV=0. 1500 <NULL> see description N3101 N3103 N3105 NBVCBR NBVCRR NBVCUR Moved to CPCU object in BR8. 63 0 Interactive traffic handling priority 2 to Different Service. object: range: default: PCU 0.e. 63 0 MTU=<NULL>. this parameter represents the mapping between interactive class with traffic handling 2 and DSCP coding. FRVAR. i.

68 . object: range: default: PCU 1.0 This parameter specifies the Number of consecutive retries performed for the NS test procedure (exchange of NS-ALIVE/NSALIVE-ACK PDUs) before the NSVC is marked dead and blocked. NMO_2. The MS therefore only needs to monitor this paging channel. In Network Mode of Operation II (NMO_2) the network sends both circuit-switched as well as packet-switched pagings on the CCCH paging channel. In Network Mode of Operation I (NMO_1) the network sends circuitswitched pagings for GPRS attached mobiles either on the same channel that is used for GPRS paging (i. object: range: default: PCU NMO_1. NMO_3 NMO_2 Network mode of operation.0 Moved to CPCU object in BR8. The Gs-interface must exist to allow paging coordination between MSN and SGSN.0 Moved to CPCU object in BR8. In NMO II and NMO III the circuit switched paging is sent from the MSC via SS7 link to the BSC and GPRS paging is sent from SGSN via Gb-interface to the BSC. 30 10 Note: For proper operation the 'Network Mode of Operation' should be the same in each cell of a routing area. Therefore the MS only needs to monitor one this one and only paging channel and it receives circuit-switched pagings even if it is in packet transfer mode (PDCH allocated). circuit-switched pagings are ignored by the MS while it is in packet transfer mode. A PBCCH must not be created in the cell when NMO_2 is used! In Network Mode of Operation III (NMO_3) the network sends circuit-switched pagings on the CCCH paging channel and packetswitched pagings either on the CCCH paging channel or on the PCCCH paging channel (if a PBCCH is created in the cell).e. this parameter determines which types of channels the MS has to monitor for paging messages. if configured. Moved to CPCU object in BR8. an O&M alarm is generated and a STATUS indication is sent to the NS user entity.NMO=NMO_2. CS pagings for GPRS attached mobiles are routed via the SGSN and arrive on the Gb interface together with the packet pagings.. Therefore an MS that wants to receive pagings for both circuitswitched and packet-switched services shall monitor both paging channels if the packet paging channel is allocated in the cell. The NMO value is broadcast in the system infos on the BCCH/PBCCH. Similar to NMO_2 the mobiles are not CS reachable while they are in packet transfer mode. As a consequence. CCCH or. PCCCH) or on a GPRS traffic channel. The following table summarizes the described modes: NNSVCBLKR NNSVCRR NBVCUR NNSVCTSTR=10.

FALSE FALSE PFCSUP=DISABLED. this parameter is used to indicate whether the Enhanced Flow Control is enabled or not. The BSC distributes all cells with packet functionality (PTPPKF) depending on load considerations amongst the available PCUs (NSEIs). this parameter represents the PCU area identification and has end-to-end significance across the Gb interface. this parameter represents the mapping between predefined PFI SMS parameter and DSCP coding. the procedure is retried for NNSVCUBLR times. object: range: default: PCU string 7. Packet flow context support. object: range: default: PCU 0. object: range: default: PCU ENABLED.. Packet flow context flow control support.NNSVCUBLR=3.65534 PFCFCSUP=FALSE. The convention used for this value is the dotted decimal format (e.. Port 1. this parameter indicates the IP address for the PCU. 16 <NULL> see description SNSCHWEIRET=<NULL>. object: range: default: PCU 0.255. This value is TRUE if BSC supports the Enhanced Flow Control. object: range: PCU 0.15 chars <NULL> SMSPFITODIFFSERV=0. The convention used for this value is the dotted decimal format (e. object: range: default: PCU 0. 63 0 Signaling PFI to Different Service. Note: This attribute can be set only if the object PCU is in 'locked' state.g.15 chars <NULL> Port 0. It uniquely identifies a PCU which is connected to the SGSN (via the Gb-interface) with one or more NSVCs (group of NSVCs). 16 <NULL> see description Subnetwork Service change weight retries. this parameter allows to enable/disable the Packet Flow Context procedure support.0”). object: range: default: PCU 1.255.. object: range: default: PCU string 7... NRLCMAX NSEI=10. this parameter represents the mapping between predefined PFI signalling parameter and DSCP coding. 254 3 This parameter specifies the Maximum number of retries performed in the NSVC unblock procedure. SMS PFI to Different Service. Moved to CPCU object in BR8. DISABLED DISABLED PORT0=<NULL>.0 Network Service Element Identifier. object: range: default: PCU TRUE.g. Afterwards the system establishes a permanent virtual connection (BVCI) for each of these cells on the respective group of NSVCs. this parameter indicates the IP address for the PCU. PORT1=<NULL>. object: range: default: PCU 0. the default value of this parameter depends on the value of GBSNS attribute: GBSNS (value) SNSADDRET (default) FRFIX NULL IPV4 3 SNSADDRET=<NULL>.. “255.0”). the default of this parameter depends on the value of GBSNS attribute: GBSNS (value) SNSCHWEIRET (default) FRFIX NULL IPV4 3 69 . 63 0 SPFITODIFFSERV=0. “255..255. Subnetwork servive address retries.. If the SGSN does not answer to the unblock procedure.255.

0 Moved to CPCU object in BR8.0 Moved to CPCU object in BR8. object: PCU The default of this parameter depends on the value of GBSNS range: 0. 63 0 Stream to Different Service. this parameter represents the mapping between streaming class and DSCP coding.0 Moved to CPCU object in BR8. object: range: default: PCU 0. this parameter indicates the method of configuration of the NS-VCs for the IP sub network service. the default of this parameter depends on the value of GBSNS attribute: GBSNS (value) SNSCONFRET (default) FRFIX NULL IPV4 3 SNSDELRET=<NULL>. 16 <NULL> see description Subnetwork Service configuration retries.0 Moved to CPCU object in BR8. this parameter allows to enable/disable the real time streaming support. 16 attribute: <NULL> default: see description GBSNS (value) TYPOFNSVCCONF (default) FRFIX NULL IPV4 STATIC T1 T2 T3141 T3169 T3172 T3169 T3191 T3193 T3195 TEMPCH TEMPPDT TF1 Moved to CPCU object in BR8.0 Moved to CPCU object in BR8. 16 <NULL> see description Subnetwork Service size retries.0 Moved to CPCU object in BR8. object: range: default: PCU 0.0 Moved to CPCU object in BR8. the default of this parameter depends on the value of GBSNS attribute: GBSNS (value) SNSDELRET (default) FRFIX NULL IPV4 3 SNSSIZERET=<NULL>.. object: range: default: PCU 0.. 16 <NULL> see description Time Subnetworks procedure.15 chars udpPort: 1024 ...0 Moved to CPCU object in BR8.. DISABLED DISABLED Streaming support. 16 <NULL> see description Subnetwork Service delete retries.. object: range: default: PCU 0. STREAMTODIFFSERV=0.. object: range: default: PCU 0. this parameter indicates the startup remote IP endpoint.0 Moved to CPCU object in BR8. object: range: default: PCU ENABLED. the default of this parameter depends on the value of GBSNS attribute: GBSNS (value) TSNPRO (default) FRFIX NULL IPV4 10 TYPOFNSVCCONF=<NULL>.0 Moved to CPCU object in BR8... TSNPRO=<NULL>.0 Moved to CPCU object in BR8.SNSCONFRET=<NULL>. 65535 <NULL> Startup remote IP endpoint. object: format: range: default: PCU <ipAddress>-<udpPort> ipAddress: string 7. STREAMSUP=DISABLED. the default of this parameter depends on the value of GBSNS attribute: GBSNS (value) SNSSIZERET (default) FRFIX NULL IPV4 3 STPIPEP=<NULL>.0 70 .. Type of NSVC Configuration.

therefore we strongly recommend to set the default values unless otherwise officially specified! Moved to CPCU object in BR8..0 This timer defines the Waiting time for the NSVC block/unblock procedure.. Moved to CPCU object in BR8. it waits TNSVCR seconds for the acknowledgement. Caution: These three parameters were repeatedly “abused” for development and system test purposes in order to implement additional test features – partly also customer relevant features. object: unit: range: default: PCU 1s 1.50.. This timer defines the Periodicity timer for the NSVC test procedure.550 THSULBAL TIMEDTBFREL TNSVCBLK=3. This timer defines the Waiting time for the NSVC test procedure.. After an NS-BLOCK PDU has been sent by the PCU. 60 30 TSULBAL Creating the PCM links for the Abis interface: < PCMB is the PCM link on the Abis interface..999 thproxt2: 1. bit 2 has a fixed value of ‘1’ and bit 3 is the A-bit for urgent alarms). At the current stage of BR70 no official released functionalities are controlled by them. the procedure is repeated (parameters NNSVCBLKR and NNSVCUBLR). the periodic NS test procedure is performed on the Gb-interface from both sides (BSC and SGSN independently). BAF=2. If no acknowledge arrives in time. Bit alignment frame. it waits TNSVCBLK seconds for the acknowledgement. Therefore they are not used by the system.0 Moved to CPCU object in BR8. object: unit: range: default: PCU 1s 1.3) are reserved for other PCM link functions (bit 1 is the ‘Si’ bit and used for CRC. Although the value range of 0.1000 500.. As soon as the NS reset procedure is completed. object: range: default: PCMB 0. determines the bit values in selected bits of the NFAS. object: unit: range: default: PCU 1s 1.50.Sa8) can be set by the BAF parameter as the first 3 bits (1. > CREATE PCMB: NAME=PCMB:0.. If no acknowledge arrives in time. the reset procedure is repeated (parameter NNSVCRR).. object: unit: range: default: PCU 1s 1. 10 3 TNSVCR=3. this parameter implements 3 thresholds for TH-proximity evaluation. the test procedure is repeated (parameter NNSVCTSTR). The decimal value entered for this parameter determines .. After an NS-BLOCK or NS-UNBLOCK PDU has been sent by the PCU. 10 3 Threshold Proximity Timer... the test procedure is repeated (NNSVCTSTR). For this purpose an NSALIVE PDU is sent towards the SGSN every TNSVCTST seconds.. The entered decimal value. After an NS-ALIVE PDU has been sent by the PCU.THPROXT=500... it waits TNSVCPTST seconds for the acknowledgement.100 thproxt3: 101. If no acknowledge arrives in time. 10 3 TNSVCTST=30. 71 . the value of BAF also determines the value of bit 1 (Si bit). Note: These timers were implemented based on older specifications which are no more valid now.117.converted to binary format . range: 0. This timer defines the Waiting time for the NSVC reset procedure. converted to binary. If no acknowledge arrives in time (TNSCVPTST).. object: format: unit: range: default: PCU thproxt1-thproxt2-thproxt3 thproxt1: 1ms thproxt2: 1s thproxt3: 1s thproxt1: 10.255 0 Object path name.550. If CRC is not used.0 TNSVCPTST=3.255 allows to set all 8 bits only the last 5 bits (bits Sa4..the bits of the PCM30 ‘Service Word’ (or ‘Non-frame alignment signal’ NFAS).

E10_5 E10_3 Bit error rate. E. CRC=TRUE. if a link interruption occurs on the PCM link directly connected to the BSC normally the direction switch is executed without an additional alignment. (L1CTS=31-3).. determines whether the cyclic redundancy check systems CRC4 (for PCM30 lines) respectively CRC6 (for PCM24 links) is enabled. are transmitted by all BTSEs in the loop (as well as by the BSC) in both directions but received only from the currently 'active' direction (LI port 1 or port 2). Note: For loop configurations this parameter is mandatory from BR4.5 on) the PCMB links BSC <-> BTSM 1 and BSC <-> BTSM 3 have to be supervised by configuration of an appropriate layer 1 control timeslot. The layer-2 setup messages. however. the BTSEs start to transmit 'failure' patterns via the L1CTS. object: range: default: PCMB TRUE. 1) Loop configuration on Abis: in this case the layer 1 control timeslot is used to control the loop direction switch. Principle of loop configuration: All BTSEs in the loop and the BSC permanently transmit a signal pattern via the layer-1 timeslot which indicates 'idle' or 'failure'. in the example configuration below (BTS crossconnect function is supported from BR5. For this reason only in the 'active' direction the setup of the higher layers takes place and the traffic and signaling information is received only via the used LI port. FALSE FALSE CRC enabled.24 (for PCM24) subslot: 0.. defines the Abis timeslot to be used for layer 1 supervision of specific Abis line configurations (e.BER=E10_3.g. This pattern is transmitted only in the 'forward' direction. 72 .g.0 on as the possibility to use the SA7 bit has been removed. For those PCM links which carry a LAPD link the error detection is ensured by LAPD layer 2 functions. defines the bit-error-rate threshold that must be exceeded in order to raise a PCM alarm. Layer 1 control timeslot. 2) Abis connection using 2 PCM links (BTS+) In this case the supervision of the link availability has to be done either by layer 2 or layer 1 error detection functions. ‘31-3’ means: layer 1 supervision in timeslot 31.3 BSC QTLP port A QTLP port B LI port 1 LI BTSE port 2 0 LI port 2 LI port 1 LI BTSE port 2 1 BTSE port 1 n LI = receive direction traffic & signaling = transmit direction traffic & signaling = transmit direction layer-1 timeslot If on the L1CTS the 'idle' pattern disappears or a 'failure' pattern is received from the neighbour BTSE in the loop the BTSE immediately changes the 'receive' direction to the other LI port. subslot 3).31 (for PCM30) timeslot: 0. For all other links the error detection has to be ensured by configuration of an layer 1 control timeslot.. object: range: default: PCMB E10_3. E10_4. Moreover. object: range: PCMB timeslot: 0. If a link interruption occurs on a PCM-link between the BTSEs normally a fast alignment is sufficient to setup of the higher layers after the direction switch as the direction switch causes only very short LAPD interruptions.

determines whether or not ‘not urgent alarms’ can be signaled. object: range: default: PCMB SIMPLEXA. . PCM link: licd-no. determines the type of signal used on the PCMS. E10_4. E10_6.. 73 .g. E10_5.1 (DTLP) port-no. CODE=HDB3.0. Every logical LICD port consists of 2 physical ports A and B. AMI (Alternate Mark Inversion) and HDB3 use 1-signals of alternating polarity (e. object: range: default: PCMB HDB3. object: range: PCMB licd-no. 0..3 (QTLP) REMAL=CCITT. HDB3 has additional functions to avoid longer ‘0’ periods by automatic insertion of so-called ‘violation’ bits if a longer ‘0’ period is detected. FALSE FALSE PCML=0. E10_3 Low bit error rate. Here LREDUNEQ must be SIMPLEXA/B for STAR and MULTIDROP configuration and DUPLEX for LOOP configuration (where port B is used for the incoming end of the loop chain). E10_8. E10_7. object: range: default: PCMB E10_3. 0. object: range: default: PCMB TRUE.8 port-no. Line code. -1 and +1). ‘Not Urgent Alarm’ enabled. LREDUNEQ=SIMPLEXA. AMI HDB3 NUA=FALSE. E10_9.. 'Not urgent alarms' are signaled using the 4th bit (Sa4 bit) of the NFAS signal (“Service Word” in timeslot 0 of the PCM system). SIMPLEXB DUPLEX SIMPLEXA Link redundancy..LOWBER=0. object: range: default: PCMB CCITT BELLCORE CCITT Remote alarm. 0.licd-port-no.

WMOD=DOUBLE_TRUNK. In this case the affected PCMBs can be configured as “star” or “multidrop”.0 and is used to extend the number of PCMBs that can be connected to the available LICD ports. The value DOUBLE_TRUNK mode represents the only connection modes that were possible in releases up to BR5. in this case the remaining port remains unused.5: a) One PCM link representing one PCMB can be connected to one port of the selected STLP port only (REDUNEQ=SIMPLEXA or SIMPLEXB). In this case. this attribute indicates whether the PCMB works in single trunk mode or in double trunk mode. both ports A and B represent the same PCMB object! A DOUBLE_TRUNK mode: STLP port B PCMB 0 PCMB 0 BTSE BTSE BTSE The value SINGLE_TRUNK is represents a configuration in which one PCMB can be connected to each STLP subport (A and B). The SINGLE_TRUNK mode was introduced as part of the feature “High Capacity BSC” in BR6. A PCMB 0 not used BTSE DOUBLE_TRUNK mode: STLP port B b) One PCM link can be connected to port A and another PCM link can be connected to port B of the STLP port (REDUNEQ=DUPLEX) for an Abis loop configuration (see parameter L1CTS). A SINGLE_TRUNK mode: STLP port B PCMB 0 PCMB 1 BTSE BTSE BTSE 74 . object: range: default: PCMB SINGLE_TRUNK. DOUBLE_TRUNK DOUBLE_TRUNK Working mode.

Although the value range of 0. E10_4.converted to binary format . A redundant PCMS link is an additional physical line which is 'hot standby' to take over the traffic and signaling if the currently active one fails. determines the type of signal used on the PCMS. object: range: default: PCMS TRUE. 0.. Link redundancy. E10_7. 0. HDB3 has additional functions to avoid longer ‘0’ periods by automatic insertion of so-called ‘violation’ bits if a longer ‘0’ period is detected.. PCM link: licd-no.. object: range: default: PCMS SIMPLEXA. determines whether the cyclic redundancy check systems CRC4 (for PCM30 lines) respectively CRC6 (for PCM24 links) is enabled. CODE=HDB3. object: range: default: PCMS E10_3.1 (DTLP) port-no. The decimal value entered for this parameter determines . The range for the PCMS-no. AMI HDB3 CRC=TRUE. Bit error rate.47 Bit alignment frame. 'Not urgent alarms' are signaled using the 5th bit of the NFAS signal (Service Word in timeslot 0 of the PCM system).g. object: range: PCMS licd-no. LREDUNEQ=SIMPLEXA. object: range: default: PCMS HDB3. CRC enabled.8 port-no. object: range: default: PCMS 0. object: range: default: PCMS TRUE. E10_3 NUA=FALSE. E10_9.3 (QTLP) 75 . FALSE FALSE 'Not Urgent Alarm’ enabled. 0. In case of failure of the active link the QTLP (BSC) and BSCI (TRAU) immediately change there receive direction. BAF=0. E10_6.the bits of the PCM30 ‘Service Word’ (or ‘Non-frame alignment signal’ NFAS). .).3) are reserved for fixed PCM link functions (CRC. determines whether or not ‘not urgent alarms’ can be signaled.255 0 BER=E10_3. is 0. AMI (Alternate Mark Inversion) and HDB3 use 1-signals of alternating polarity (e. Low bit error rate. Here LREDUNEQ must be SIMPLEXA/B if a nonredundant PCM link is used and DUPLEX if port B is equipped with a redundant PCM link.Creating the PCMS link: < PCMS is the PCM link on the Asub interface. > CREATE PCMS: NAME=PCMS:0. object: range: default: PCMS E10_3. Every logical LICD port consists of 2 physical ports A and B. -1 and +1).. E10_4. D-bit etc. FALSE FALSE Line code. PCML=1-1.licd-port-no. E10_8. SIMPLEXB DUPLEX SIMPLEXA LOWBER=0.255 allows to set all 8 bits only the last 5 bits (4. E10_5... Note: If the link redundancy is set to DUPLEX both traffic and signaling info is transmitted via both links while it is received only via the active one. E10_5 E10_3 Object path name. port B can be used in addition to port one for a redundant link.8) can be set by the BAF parameter as the first 3 bits (1.. defines the bit-error-rate threshold that must be exceeded in order to raise a PCM alarm..

A DOUBLE_TRUNK mode: QTLP port B PCMS 0 redundant link T R A U The value SINGLE_TRUNK is only allowed if the parameter ASUBENCAP (see SET BSC [BASICS]) is set to TRUE. WMOD=DOUBLE_TRUNK.REMAL=CCITT. With this setting it is possible to connect one PCMS to each physical QTLP port SINGLE_TRUNK mode: A QTLP port B PCMS 0 PCMS 1 T R A U T R A U 76 . The value DOUBLE_TRUNK mode represents the only connection mode which was possible in releases up to BR5. this attribute indicates whether the PCMS works in single trunk mode or in double trunk mode. object: range: default: PCMS SINGLE_TRUNK.0: One PCMS (i. BELLCORE CCITT Remote alarm. object: range: default: PCMS CCITT. one TRAU) can be connected to one port of the selected QTLP port only (REDUNEQ=SIMPLEXA or SIMPLEXB) or one PCMS can be connected redundantly by using both ports (A and B) of the QTLP port (REDUNEQ=DUPLEX). DOUBLE_TRUNK DOUBLE_TRUNK Working mode.e.

If pools are created the whole mapping pattern changes depending on the type and number of TCH pools configured. Note: The mapping principle shown in the diagrams only illustrate the basic mapping pattern which is in effect when no pools are created. For the basic mapping principle please refer to the diagram on the next page. For the basic mapping principle please refer to the diagram on the next page. default: Object path name. ALLCRIT= NOT_COMPATIBLE_WITH_C ROSSCONNECT. b) COMPATIBLE_WITH_CROSS_CONNECT value has to be chosen when cross-connectors between BSC and TRAU are used (corresponds to the previous ‘TRAU matrix type 2’). object: range: TRAU NOT_COMPATIBLE_ WITH_CROSSCONNECT.e. This solution is of special interest if the network operator does not rent complete PCM-links for the PCMS but only single timeslots. a) The value NOT_COMPATIBLE_WITH_CROSS_CONNECT value can be chosen when no cross-connectors between BSC and TRAU are used (corresponds to the previous ‘TRAU matrix type 1’).0 and defines which mapping system is used between the timeslots of the A.and Asub-interface. Since the introduction of the feature ‘pooling’ (see SET BSC [BASICS]. COMPATIBLE_WITH_ CROSSCONNECT NOT_COMPATIBLE_ WITH_CROSSCONNECT. this attribute replaces the parameter TRANMTX which was used up to BR4. Allocation criteria. 77 . The advantage of this mapping system is that all subslots of the PCMS timeslots can be completely filled even if not all 4 PCMA-links are used between TRAU and MSC.Creating the TRAU: CREATE TRAU: NAME=TRAU:0. parameter ENPOOL) the previously rigid mapping of timeslots is replaced by a semipermanent mapping (i. a mapping modifiable by configuration commands) which depends on the types and number of TCH pools created on the A-interface.

The following example may illustrate a useful solution: Channel type CCS7 link OMAL LPDLS Used timeslot on Asub PCMS. timeslot 30 PCMS. timeslot 31 Used timeslots on A interface PCMT-0. timeslot 25 PCMT-0. timeslot 31 Used timeslots on A interface PCMT-0. Channel type CCS7 link OMAL LPDLS Used timeslot on Asub PCMS.. The timeslot number used for CCS7 link and the OMAL on the Ainterface corresponds to the one on the PCMS. 7 6 5 4 3 2 1 0 A U PCMT-3 31 30 29 28 27 . timeslots (0).. In addition. 3 2 1 0 Note: TRAU Matrix type 1: If a specific timeslot on PCMT-0 is used for CCS7 and OMAL the corresponding timeslots on all other PCMTs connected to the same TRAU remain empty. 2 1 0 subslot 0 remains empty in timeslots 1. 3 2 1 0 3 2 1 0 X PCMS-0 PCMT-2 31 . 27 26 25 24 . -2 and -3 Basic TRAU-mapping 2: COMPATIBLE_WITH_CROSSCONNECT (no pools created) PCMT-0 31 .22. timeslot 30 * PCMS. timeslot 30 none Not usable timeslots on A interface PCMT-3..25. The following example configuration has the advantage that all ‘non-usable’ A-interface-timeslots are concentrated on one PCMT link (here: PCMT-3).26. timeslot 16 PCMS. 7 6 5 4 3 2 1 0 T R ts31 ts2 ts1 ts0 3 2 1 0 . subslot 1 (CCS7 link). 3 2 1 0 3 2 1 x ts 2 ts 1 X ts 0 PCMT-2 31 .2. -2 and -3 timeslot 30 on PCMT-1.1. 7 6 5 4 3 2 1 0 PCMS-0 PCMT-1 31 . subslot 2 78 .. timeslot 25 * PCMS. 17 and 25 ! timeslots 28 .3 PCMT-3... -2 and -3 timeslot 31 on PCMT-0. 9. If timeslot N on the PCMS is created as LPDLS then the corresponding timeslot N on all other PCMTs is empty as well... timeslot 8. timeslots 20. timeslots 24. 7 6 5 4 3 2 1 0 A U PCMT-3 31 . timeslot 16 PCMT-0...Basic TRAU-mapping 1: NOT_COMPATIBLE_WITH_CROSSCONNECT (no pools created) PCMT-0 31 . 7 6 5 4 3 2 1 0 PCMT-1 31 .. OMAL and LPDLS all PCMA-timeslots that are mapped to the selected PCMS timeslot cannot be used and remain empty.. the PCMS-subslot mapped to the used PCMT timeslot will remain empty. -1.27 * not usable timeslots on PCMS: timeslot 7. timeslot 30 none Not usable timeslots on A interface timeslot 16 on PCMT-1..21.. 7 6 5 4 3 2 1 0 T R ts 31 3 2 1 0 . 31 are not usable ! Note: TRAU Matrix type 2: If specific timeslots on the PCMS are used for CCS7.23 PCMT-3.

the speech call will be carried on in the traditional way. ETFO=FALSE. this parameter indicates the target speech level for the Automatic Level Control. each TFO capable TRAU checks whether the peer TRAU is capable to support TFO and is using the same codec. Acoustic Level Control target level. DELAY_30_ms. i. EDULDL DISABLED ALCTGTLEV=m19dBM0.53 Enable Tandem Free Operation. Principle: If TFO is enabled. speech signals are transmitted in form a-law (or u-law) coded PCM signals while within the BSS speech is transmitted in form of TRAU frames based on a specific speech coding algorithms such as Full Rate. m17dBM0. Target level is applicable to both directions if both enabled. object: range: default: TRAU DISABLED. EFR) and vice versa. m20dBM0. whether it is enabled for uplink and downlink or only one direction. The Automatic Link Detection monitorizes two default windows. this parameter determines whether the feature Acoustic Echo Control feature is enabled or not. If at least one of these conditions stated above is not met. m19dBM0. m15dBM0 m19dBM0 default: BULKDCONF= DELAY_160_ms. HR or EFR). ALCST=DISABLED. m21dBM0. each TRAU can start to insert speech TFO frames into the call related PCM octet on the A interface. EDULONLY. TFO does not involve the Call Control in the MSC 79 . Preconditions: TFO operation is used in all mobile to mobile speech calls where both Mobiles/TRAUs use the same GSM transcoder (i. Background: Within the SSS.e. The main task of the TRAU (for speech calls) is the transcoding of the a-law (or u-law) signal to the GSM speech version (FR. object: range: default: Reference: TRAU TRUE. until one of two links is detected. DELAY_750_ms. The TFO signalling procedures do not depend on the any call set up procedures. Moreover. After verifying these conditions. FALSE FALSE GSM 04. terrestrial (160-260 ms) and satellite window (650-750 ms). m23dBM0. object: range: TRAU iTU. It is possible to choose between ITU-T G. m22dBM0. Acoustic Level Control activation status. Half Rate or Enhanced Full Rate. In case of a mobile-to-mobile call this transcoding process unnecessarily takes place in both involved TRAUs .HR. If TFO is enabled and all preconditions are fulfilled the uplink TRAU frames are no longer decoded to 64kbits/s (a-law) PCM speech samples but are transmitted in so-called TFO speech frames which are transported on the A interface between two TRAUs. m18dBM0. object: range: default: TRAU ENABLED. DELAY_20_ms.AECST=DISABLED. DISABLED DISABLED Acoustic Echo Control activation status. both involved TRAUs must support the TFO feature (TRAC V3 or TRAC V5 required). FR. The manual configuration is a particular case of automatic link working where the two windows are adjacent and the operator can insert the lower limit of the first window (bulk delay). object: TRAU step size: range: DELAY_0_ms. if yes.169 compliant mode (value ITU) and Siemens Enhanced solution with customizable settings. m16dBM0. this parameter is used for the default configuration of the terrestrial link. DELAY_10_ms. TFO is a feature that improves the speech quality of mobile-to-mobile speech calls by avoiding a double transcoding in both involved TRAUs. … DELAY_740_ms.at the expense of the speech quality. AUTOMATIC_LINK_DETECTION default: DELAY_160_ms Bulk delay configuration.e. this parameter determines whether the feature Acoustic Level Control feature is enabled and. EDDLONLY. this flag allows to enable or disable the TFO mode.

i. It determines the total amount of desired noise reduction (dB).60. within the used TCH. the 'TFO established mode'. No information is forwarded to the BSC in order to modify the used codec. object: range: TRAU 0. The TFO signalling exclusively takes place 'in-band'.monitoring TFO negotiation messages and the TFO speech frames . DISABLED DISABLED Noise reduction status.61. NOIREDA=DISABLED. this parameter is only relevant if the parameter NOIREDST (see below) is set to ENABLED.5 kbit/s signalling.converting the received UL TRAU frames to TFO speech frames .. this SW version must be available and loaded in the TRAU. TFO functions of the transcoder unit: .inserting TFO negotiation messages and the TFO speech frames Expected SW version. object: range: default: TRAU ENABLED. object: range: default: TRAU ENABLED. 2) In the second phase... the TFO negotiation messages are transferred in the Least Significant Bit of (a-law) PCM samples. which are similar to the frames in 08. are carried by 8 kbit/s channel mapped onto the LSB bit of each PCM sample. this parameter determines whether the feature ‘Noise reduction’ is enabled or not.19 PCMS-no. 80 .e. For HR channels the TFO speech frames. The 0. which are similar to the frames in 08. are carried by 16 kbit/s channel mapped onto the two LSB bits of each PCM sample. DISABLED DISABLED Integrated Cellular Telephone Modem status. INTCTMST=DISABLED.converting the received TFO speech frames into DL TRAU frames .5 kbits/s are regularly stolen of the 64 kbits/s circuit and by this small amount of data the degradation on the speech quality is inaudible. HR or EFR transcoder is used TFO speech frames. If it is not available the TRAU automatically requests a download of this SW version from the BSC. the 'TFO establishment mode'. The TFO message bit is transferred by replacing the LSB in every 16 consecutive PCM samples. when the FR.. PCMSN=0. object: TRAU and in the BSC. object: unit: range: default: TRAU dB -18.EXPSWV= "02-04-01-02-06-00 _98-07-30". The TFO speech frames have a fixed length of 160 bits (20msec) for 8 kbits/s traffic channels and 320 bits (20msec) for 16 kbits/s traffic channels. this parameter determines whether the feature ‘Integrated Cellular Telephone Modem’ is enabled or not. TFO Phases: The transcoder unit implements the TFO operation in two phases: 1) In the first phase. This will result in a 0. -6 (dB) -12 NOIREDST=DISABLED. Noise reduction amount.

> CREATE LPDLS: NAME=TRAU:0/LPDLS:0.3 Object path name.63 changeable) correspondence to the relative object number of the LPDLS resp. object: range: LPDLS pcms-no.SALUNAME=”BSC1TRAU0”. object: TRAU In previous releases (up to BR4. The TRAU starts this timer if 3 uplink TRAU object: TRAU frames have not been correctly received from the BTSE and it is unit: 10ms reset if a correct frame is received again (It is only used if a BTSrange: 10. TSYNC=1000. this timer is used by the TRAU to supervise time-out of TRAU frame handling. Asub channel: pcms-no. Terminal endpoint identifier of LPDLS. this attribute defines the TEI of the LPDLS resp. ASUBCH=0. . TRAU and was the only criteria used for the network element identity verification during the alignment procedure. 0.10000 TRAU traffic connection is established). Sales Unique Name.. 81 .. Voice quality enhancement status. DISABLED DISABLED Creating the LPDLS links: < The LPDLS link is the LAPD channel for O&M Information between BSC and TRAU. VQEST=DISABLED. In previous releases (up to BR4. another TRAU specific identity can optionally be used to unambiguously identify the TRAU during the alignment procedure: the Sales Unique Name (see command CREATE TRAU. 1-31 (PCM30) timeslot-no.0 on the TEI can be explicitly set for every LPDLS by the parameter TEI. object: range: default: TRAU ENABLED. 1-24 (PCM24) subslot-no.. TSYNC.19 timeslot-no. From BR5.31. As with this new approach one and the same TEI can be used more than once within a BSC. not range: 0..subslot). this attribute defines every Network Element by its unique symbolic name. The new default: NOT_DEFINED approach using the Sales Unique Name in addition to an individually configurable TEI allows a much higher flexibility in the allocation of the TRAUs to the BSCs without loss of safety.5) (11 characters) the (LPDLS-)TEI was the only criteria used for the network element in quotation marks identity verification during the alignment procedure.5) the TEI had a fixed (i. If it expires. the TRAU default: 1000 reports a transcoder failure warning to the BSC and the TRAU issues the warning DSP TSYNCEXPIRED.timeslot (.. TRAU. TEI=0. parameter SALUNAME).e.. this parameter determines whether the feature ‘Voice Quality Enhancement’ is enabled or not. It can be optionally used for the network object: TRAU element identity verification during the alignment phase in addition to range: alphanumeric string the TEI (see CREATE LPDLS). 0.

The different values for the pooling type are predefined and represent a certain combination of different ‘supported coding types’ for speech and data. The range for the PCMA-no. CRC enabled.. this parameter is only relevant if the feature ‘pooling of A-interface TCH resources’ (see parameter EPOOL in command SET BSC [BASICS]) and defines the default type of pool assigned to every TSLA of the given PCMA. Although the value range of 0.255 0 BER=E10_3. Bit alignment frame. is 0.POOL_48 NOT_DEFINED default: New pool types in BR7. FALSE FALSE Line code. Creating the PCMA link: < PCMA represents the PCM link on the A interface. determines the type of signal used on the PCMA.. determines whether the cyclic redundancy check systems CRC4 (for PCM30) respectively CRC6 (for PCM24) is enabled. object: range: default: PCMA 0. converted to binary.g.. E10_5 E10_3 Object path name. the parameter LAPDPOOL assumes the meaning of "primary PPXL" (i. The entered decimal value. the module no. of the PPXL where the LAPD must work if both PPXL are in service).LAPDPOOL=0. POOL_35 POOL_42.1 (LAPD pool is assigned by the BSC automatically) LAPD pool. For the different pooling types defined by GSM please refer to the table on the following pages.. AMI HDB3 CRC=TRUE. E10_4. HDB3 has additional functions to avoid longer ‘0’ periods by automatic insertion of so-called ‘violation’ bits if a longer ‘0’ period is detected.. -1 and +1). determines the bit values in selected bits of the NFAS. POOL_15.191. object: range: PCMA NOT_DEFINED POOL_1.0! 82 .. AMI (Alternate Mark Inversion) and HDB3 use 1-signals of alternating polarity (e. LPDLS) that could be managed by one PPLD. bit 2 has a fixed value of ‘1’ and bit 3 is the A-bit for urgent alarms).. the value of BAF also determines the value of bit 1 (Si bit). For further details please refer to the parameter LAPDPOOL in the command CREATE LPDLM. LPDLR.0 the PPLD boards are no longer supported also this meaning of the parameter does no longer exist. up to BR7. If CRC is not used.0 this parameter used to define the LAPDPOOL the LPDLM should be assigned to. DEFPOOLTYP= NOT_DEFINED.converted to binary format . object: range: default: PCMA HDB3. BAF=0. object: range: default: LPDLS 0. CODE=HDB3..the bits of the PCM30 ‘Service Word’ (or ‘Non-frame alignment signal’ NFAS). Bit error rate. For PPXL. object: range: default: PCMA E10_3.255 allows to set all 8 bits only the last 5 bits (bits Sa4. A “ LAPD Pool “ was a logical instance which represented a group of LAPD channels (LPDLM..POOL_13. defines the bit-error-rate threshold that must be exceeded in order to raise a PCM alarm.e. > CREATE PCMA: NAME=PCMA:0. Default pool type..3) are reserved for other PCM link functions (bit 1 is the ‘Si’ bit and used for CRC. Since in BR8. The decimal value entered for this parameter determines .Sa8) can be set by the BAF parameter as the first 3 bits (1. object: range: default: PCMA TRUE.

3. 3. 12.6 kbit/s) HSCSD max 2 x FR data (12.6 kbit/s) HR speech version 1 HR data (6. 6.5 kbit/s) EDGE FR data (29.5.6 kbit/s) HR data (6. 12. 3.5 kbit/s) FR data (14.6 kbit/s) FR speech version 1 FR speech version 2 FR data (12. 3. 6 kbit/s) HSCSD max 4 x FR data (12.6 kbit/s) HR data (6.6 kbit/s) HSCSD max 2 x FR data (12.0 kbit/s) FR data (14.0 kbit/s) EDGE FR data (43.0 kbit/s) EDGE FR data (43.6 kbit/s) HSCSD max 4 x FR data (12. 3.6 kbit/s) FR speech version 1 FR speech version 2 FR data (12.0 kbit/s) HSCSD max 4 x FR data (14. 3.5. 3.6 kbit/s) FR speech version 2 FR data (12. 6.6 kbit/s) HR speech version 1 HR data (6.6 kbit/s) HSCSD max 2 x FR data (12.6 kbit/s) HR speech version 1 HR data (6. 6. 6.6 kbit/s) HR data (6.0 kbit/s) FR data (14. 3. 6. 3. 3. 6 kbit/s) EDGE FR data (29. 6. 6 kbit/s) HSCSD max 6 x FR data (12. 3.6 kbit/s) 0000 0100 0000 0101 0000 0110 Circuit pool number 4 Circuit pool number 5 Circuit pool number 6 0000 0111 Circuit pool number 7 0000 1000 0000 1001 0000 1010 Circuit pool number 8 Circuit pool number 9 Circuit pool number 10 0000 1011 0000 1100 0000 1101 Circuit pool number 11 Circuit pool number 12 Circuit pool number 13 0000 1110 0000 1111 0001 0000 0001 0001 0001 0010 Circuit pool number 14 Circuit pool number 15 Circuit pool number 16 Circuit pool number 17 Circuit pool number 18 0001 0011 Circuit pool number 19 0001 0100 Circuit pool number 20 83 .6 kbit/s) HSCSD max 2 x FR data (14. 6.6 kbit/s) HR data (6. 12.6 kbit/s) HR speech version 1 HR data (6. 3.6 kbit/s) FR speech version 1 FR data (12. 6 kbit/s) FR speech version 1 FR speech version 2 FR data (12. 3. 3.Table of A-interface pool types Coding 0000 0001 0000 0010 0000 0011 Pool Circuit pool number 1 Circuit pool number 2 Circuit pool number 3 Supported channels and speech coding algorithms FR speech version 1 FR data (12. 6.6 kbit/s) HR speech version 1 HR data (6. 6 kbit/s) FR speech version 1 FR speech version 2 FR data (12. 6 kbit/s) FR data (12.6 kbit/s) HSCSD max 4 x FR data (12.5. 3. 3. 6. 6. 3.5.6 kbit/s) HR speech version 1 HR data (6. 6 kbit/s) EDGE max 2 x FR data (29. 6.6 kbit/s) HR speech version 1 HR data (6.5 kbit/s) EDGE max 2 x FR data (29. 6. 12. 6.6 kbit/s) HSCSD max 4 x FR data (14.5 kbit/s) HSCSD max 2 x FR data (14. 3. 6 kbit/s) EDGE max 2 x FR data (32. 12. 3. 3.5. 3.6 kbit/s) FR speech version 2 FR data (12. 3. 3. 3. 6 kbit/s) FR data (12.5 kbit/s) FR speech version 1 FR speech version 2 FR data (14.

6. 6. 6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6. 12. 3.6 kbit/s) HR speech version 3 HR speech version 6 FR speech version 1 FR speech version 2 FR speech version 3 FR data (14. 3.6 kbit/s) HSCSD max 2 x FR data (14.5.6 kbit/s) HR speech version 3 HR speech version 6 FR speech version 1 FR speech version 2 FR speech version 3 FR data (12. 6.5.Coding 0001 0101 Pool Circuit pool number 21 0001 0110 Circuit pool number 22 0001 0111 0001 1000 0001 1001 Circuit pool number 23 Circuit pool number 24 Circuit pool number 25 0001 1010 Circuit pool number 26 0001 1011 Circuit pool number 27 0001 1100 Circuit pool number 28 0001 1101 Circuit pool number 29 0001 1110 Circuit pool number 30 Supported channels and speech coding algorithms FR speech version 1 FR speech version 2 FR data (14. 6.5. 3. 3.6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14. 12. 6.6 kbit/s) HSCSD max 4 x FR data (14. 12. 3.5. 6.0 kbit/s) FR speech version 1 FR speech version 2 FR data (14. 6.5 kbit/s) FR speech version 3 HR speech version 3 FR speech version 3 FR data (12.5. 3.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6.6 kbit/s) HR speech version 1 HR data (6.5. 3. 12.6 kbit/s) HSCSD max 2 x FR data (12.5. 3.5. 6. 6 kbit/s) EDGE FR data (29. 3. 6 kbit/s) EDGE FR data (29.0 kbit/s) 84 .6 kbit/s) HSCSD max 2 x FR data (14.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6. 3. 12.6 kbit/s) HR speech version 1 HR data (6. 12. 3. 3. 12.0 kbit/s) EDGE FR data (43. 3. 3. 3.6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (12. 6. 6 kbit/s) EDGE max 2 x FR data (29. 12.6 kbit/s) HR speech version 3 FR speech version 1 FR speech version 2 FR speech version 3 FR data (12.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6.

12. 3. 3. 3.Coding 0001 1111 Pool Circuit pool number 31 0010 0000 Circuit pool number 32 0010 0001 Circuit pool number 33 0010 0010 Circuit pool number 34 0010 0011 Circuit pool number 35 0010 0100 0010 0101 Circuit pool number 36 Circuit pool number 37 0010 0110 Circuit pool number 38 Supported channels and speech coding algorithms FR speech version 1 FR speech version 2 FR speech version 3 FR data (12. 6 kbit/s) EDGE max 2 x FR data (29.0 kbit/s) EDGE FR data (43. 6 kbit/s) EDGE max 2 x FR data (29.6 kbit/s) HSCSD max 4 x FR data (14. 3. 12.5 kbit/s) EDGE max 2 x FR data (32.5 kbit/s) FR data (14.5. 6.5. 6 kbit/s) EDGE max 2 x FR data (29.5 kbit/s) EDGE max 2 x FR data (32. 3.5. 12.6 kbit/s) HR speech version 3 HR speech version 4 HR speech version 6 85 . 12.5 kbit/s) EDGE max 2 x FR data (32. 6. 6. 12. 3. 6 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14.0 kbit/s) FR speech version 1 FR speech version 2 FR data (14. 3.0 kbit/s) FR speech version 4 FR speech version 5 HR speech version 4 FR speech version 3 FR speech version 4 FR speech version 5 HR speech version 3 HR speech version 4 HR speech version 6 FR speech version 1 FR speech version 2 FR speech version 3 FR speech version 4 FR speech version 5 FR data (14.6 kbit/s) HSCSD max 4 x FR data (14. 3.6 kbit/s) HSCSD max 4 x FR data (14.5. 6 kbit/s) EDGE max 2 x FR data (29.6 kbit/s) HR speech version 1 HR data (6.6 kbit/s) HSCSD max 4 x FR data (12.0 kbit/s) EDGE FR data (43.5. 3.5. 3.5. 12.5.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6.6 kbit/s) HSCSD max 4 x FR data (14. 12. 6.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 6 HR data (6.5. 6. 6. 3.0 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR data (14. 12.0 kbit/s) EDGE FR data (43. 12.6 kbit/s) HR data (6.0 kbit/s) EDGE FR data (43.

5.5.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 4 HR speech version 6 HR data (6. 12.5.0 kbit/s) EDGE FR data (43.5.5 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR speech version 4 FR speech version 5 FR data (14. 12. 3. 12. 12. 6.6 kbit/s) HSCSD max 2 x FR data (14.Coding 0010 0111 Pool Circuit pool number 39 0010 1000 Circuit pool number 40 0010 1001 Circuit pool number 41 0010 1010 0010 1011 0010 1100 0010 1101 0010 1110 0010 1111 Circuit pool number 42 Circuit pool number 43 Circuit pool number 44 Circuit pool number 45 Circuit pool number 46 Circuit pool number 47 0011 0000 Circuit pool number 48 Supported channels and speech coding algorithms FR speech version 1 FR speech version 2 FR speech version 3 FR speech version 4 FR speech version 5 FR data (14. 3.6 kbit/s) HSCSD max 4 x FR data (14. 3.5. 6.0 kbit/s) FR speech version 1 + CTM FR speech version 2 + CTM FR speech version 1 + CTM FR speech version 2 + CTM FR speech version 1 + CTM FR speech version 2 + CTM HR speech version 1 + CTM FR speech version 3 + CTM HR speech version 3 + CTM HR speech version 6 + CTM FR speech version 1 + CTM FR speech version 2 + CTM FR speech version 3 + CTM HR speech version 3 + CTM HR speech version 6 + CTM FR speech version 1 + CTM FR speech version 2 + CTM FR speech version 3 + CTM HR speech version 1 + CTM HR speech version 3 + CTM HR speech version 6 + CTM 86 . 6 kbit/s) EDGE max 2 x FR data (29. 12. 3. 6 kbit/s) EDGE max 2 x FR data (29.5 kbit/s) EDGE max 2 x FR data (32.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 4 HR speech version 6 HR data (6.6 kbit/s) HSCSD max 4 x FR data (14.0 kbit/s) EDGE FR data (43. 3. 12.6 kbit/s) HR speech version 1 HR speech version 3 HR speech version 4 HR speech version 6 HR data (6. 3. 6 kbit/s) EDGE FR data (29.0 kbit/s) FR speech version 1 FR speech version 2 FR speech version 3 FR speech version 4 FR speech version 5 FR data (14.5. 6.

object: range: default: PCMA 0. NUA=FALSE. determines whether or not ‘not urgent alarms’ can be signaled. parameter structure: trau-no.. object: range: default: PCMA E10_3..9 pcm-link-no.. the first 11 bits are used to identify the PCM-link (0. object: range: default: PCMA CCITT BELLCORE CCITT Remote alarm. E10_7.3 PCM TRAU. object: range: PCMA trau-no. of the PCM link between TRAU and MSC REMAL=CCITT. E10_3 PCMT=0. The HCICN determines the value of the first 11 bits. FALSE TRUE High part of the CIC. .2730 (if CICFM=NOTSTRUCT) pcma-no. 'Not urgent alarms' are signaled using the 4th bit (Sa4 bit) of the NFAS signal (“Service Word” in timeslot 0 of the PCM system).. E10_8.no.31). The last 5 bits identify the timeslot (0. E10_5. LOWBER=0. E10_4. The range of the parameter values depends on the setting of the parameter CICFM (see SET BSC [BASICS]).HCICN=0. Low bit error rate. object: range: default: PCMA TRUE.. E10_9.0.: 0..2047). E10_6.2047 (if CICFM=GSM) 0. The CIC (circuit identification code) is a 16bitstring used to address the PCMA-timeslot used for a traffic connection. 87 ..: 0. ‘Not Urgent Alarm’ enabled.

24 12 = normal link level 0 = 12dB attenuation 24 = 12dB amplification 12 default: VOLUL=15. The setting of VOLUL to 15 is used by some network operators because this setting was found the most suitable with respect to the subjective perception of test callers.0! THROUGH=31.POOL_13. default: New pool types in BR7.. Note: This parameter is not generated by the DBAEM.POOL_48 NOT_DEFINED Object path name.24 12 = normal link level 0 = 12dB attenuation 24 = 12dB amplification 12 Volume uplink. default: 88 .. object: step size: range: TSLA 1dB 0.. object: range: TSLA 1-31 (PCM30) 1-24 (PCM24) Timeslot range. determines the value for the timeslot volume in the uplink (MS -> MSC) direction.. Pool type. object: step size: range: TSLA 1dB 0.Setting the uplink and downlink volumes for specific PCMA timeslots: SET TSLA: NAME=pcma:0/tsla:1. POOLTYP=NOT_DEFINED. offers the possibility to set the attribute values for a group of timeslots. Moreover. Volume downlink. POOL_15. determines the value for the timeslot volume in the downlink (MSC -> MS) direction.. this parameter defines the type of pool assigned to the TSLA (see also parameters DEFPOOLTYP (SET PCMA) and EPOOL (SET BSC [BASICS])).. the volume adjustment has also been used to decrease echo effects which are mainly caused by the feedback within the housing of bag of the mobile phone. It is relevant if the command is entered from a user terminal.POOL_35 POOL_42. object: range: TSLA NOT_DEFINED POOL_1. VOLDL=12. For the meaning of the different pooling types see the table in the command CREATE PCMA.

31.g. object: range: default: PCMG HDB3..converted to binary format . is 0. 89 . object: range: default: PCMG 0. -1 and +1). FALSE FALSE ‘Not Urgent Alarm’ enabled. determines whether the cyclic redundancy check systems CRC4 (for PCM30) respectively CRC6 (for PCM24) is enabled. E10_4. E10_4. E10_9. 'Not urgent alarms' are signaled using the 4th bit (Sa4 bit) of the NFAS signal (“Service Word” in timeslot 0 of the PCM system). If CRC is not used.. E10_5. FALSE FALSE CRC enabled. the value of BAF also determines the value of bit 1 (Si bit). converted to binary. > CREATE PCMG: NAME=PCMG:0.. determines the bit values in selected bits of the NFAS. BAF=0. object: range: default: PCMG E10_3. E10_3 NUA=FALSE. CRC=TRUE.Creating the PCMG link: < The PCMG functional object represents the direct physical connection between BSC and SGSN (Gb interface). Low bit error rate... HDB3 has additional functions to avoid longer ‘0’ periods by automatic insertion of so-called ‘violation’ bits if a longer ‘0’ period is detected. object: range: default: PCMG TRUE. The entered decimal value. Bit error rate. E10_6. object: range: default: PCMG E10_3. Note: the physical connection between BSC and SGSN can be realized by a direct PCM link to the SGSN (PCMG) or via a PCMA link which is looped to the SGSN via an MSC NUC. A PCMA link can also be directly connected to an SGSN without passing the MSC – in this case the bandwidth of the FRLs configured on the PCMA is not limited by the MSC´s capability of bit-synchronous switching. Although the value range of 0. The range for the PCMG-no.the bits of the PCM30 ‘Service Word’ (or ‘Non-frame alignment signal’ NFAS). determines whether or not ‘not urgent alarms’ can be signaled. AMI HDB3 LOWBER=0. E10_8. object: range: default: PCMG TRUE. AMI (Alternate Mark Inversion) and HDB3 use 1-signals of alternating polarity (e. defines the bit-error-rate threshold that must be exceeded in order to raise a PCM alarm.255 0 BER=E10_3. The decimal value entered for this parameter determines . This line carries 32 time slots of 64 kbit/s that can handle 31 Frame Relay Links at the maximum and it can be connected to one circuit of a LICD without any restrictions. E10_7. determines the type of signal used on the PCMG. bit 2 has a fixed value of ‘1’ and bit 3 is the A-bit for urgent alarms). E10_5 E10_3 Object path name. Bit alignment frame. CODE=HDB3.3) are reserved for other PCM link functions (bit 1 is the ‘Si’ bit and used for CRC.255 allows to set all 8 bits only the last 5 bits (bits Sa4. Line code.Sa8) can be set by the BAF parameter as the first 3 bits (1.

There is no standard management of the PCM redundancy in the specifications of the SGSN and of the MSC. accordingly to specific rules. Even though the PCMG cannot be redundant. because the PCM redundancy is a proprietary feature of the BSS.8 port-no. for which the redundancy does not exist. according to the value of the ASUBENCAP attribute of the BSC basic package. 0.. object: range: default: PCMG CCITT BELLCORE CCITT PCM link: licd-no. because in this way it will be possible to set the PCMS in duplex in the future.. the working mode is internally and implicitly set.1 (DTLP) 0. In the A interface (PCMA) and in the Gb interface (PCMG) the redundancy is not allowed because this feature needs that it is handled on both peers. this means that the single trunk mode is not inhibited. Remote alarm. nevertheless it can be configured in double trunk mode. TRUNKB REMAL=CCITT. 90 . For the PCMS the working mode must be explicitly set by the operator. and so it is possible to set the PCMS lines in single trunk. any PCMG shall be automatically configured in single trunk mode. and so it is used only in the interfaces Abis and Asub. and the second trunk cannot be used for another line. For the PCMG instead. object: range: PCMG licd-no. the PCMG is automatically set in double trunk mode. in a way that is transparent to the operator.. If ASUBENCAP is FALSE.trunk Remarks on the term ‚trunk’: The PCMG links cannot be redundant. because in some cases it is desired to configure a PCMS in double trunk mode although it is not redundant..licd-port-no..3 (QTLP) trunk TRUNKA. That is: if the ASUBENCAP is TRUE. When a PCMG is created. In conclusion: if ASUBENCAP is TRUE. without deleting/creating the line. it would be useless and wasteful to set a PCMG in double trunk mode: the second trunk would be wasted without reason. and the second trunk (A or B) can be used for another PCMS or PCMG line. although you cannot see this in the CREATE command. 0.PCML=0-0-TRUNKA.

N391=6. this attribute identifies the standard of the used frame relay protocol. The Frame Relay Link connection can be realized via the A interface (PCMA) or directly to SGSN via a PCMG. After N expiries of T391 a STATUS-ENQUIRY (STAE) message requesting a Full Status Report is sent to towards the SGSN. 31 values per FRL linked with '&'. The setting depends on the Frame Relay network used for the Gb connection (if any). range for FRL: 0. object: range: FRL 1-31 max. LMI ITU Object path name. In case of A interface connection the 64 kbit/s time slot are reserved on the PCMS and handled as transparent channel in the TRAU. GLK=PCMG:0. 64 timeslots per PCU if PPXX is used. this attribute defines the type of line (PCMG or PCMA) and its object instance number used for the Gb-interface connection towards the SGSN. Frame Relay Standard. This again leads to the blocking of the A-interface timeslots that are associated to the selected Asubchannels depending on the used TRAU mapping principle (see parameter ALLCRIT in command CREATE TRAU). The Siemens MSC allows to route only single timeslot FRLs through its switching network! N391.PCMG:31 GTS=1&2. A maximum of 31 timeslots can be created per FRL (limited by PCMA/PCMG bandwidth).. GPRS link.755. GPRS timeslot. this means that 4 PCMA timeslots can no longer be used for CS traffic when one timeslot is used for the FRL object on the PCMA! The more timeslots are required for the FRL object the less useful it is to create the FRL via the PCMA! If Gb-links are routed via PCMA through the MSC (nailed-up connections). object: range: FRL PCMA:0 . it has to be considered that the timeslots entered for GTS are also reserved for GPRS on the Asub. ANSI. FRSTD=ITU. N392. object: range: default: FRL 1-255 3 91 . please also ensure that the used MSC supports a bitsynchronized switching of these timeslots. In the worst case. this parameter represents the polling cycle. up to 64 timeslots can be defined per PCU. > CREATE FRL: NAME=FRL:0. max. meaning that a single PCU may be connected to the SGSN via both PCMA and PCMG links at the same time. object: range: default: FRL 1-255 6 N392=3. this parameter represents the error threshold of the polling procedure (based on N391 counter) used to put the FRL in 'disabled' state. Otherwise Frame Relay links comprising more than 1 timeslots may be corrupted due to different delays applied to the single timeslots. Mixed configurations are possible.PCMA:191 PCMG:0 . Note: If the FRL object is created via PCMA (see parameter GLK). this parameter defines the 64 kbit/s time slots reserved for this specific FRL either on the PCMA or the PCMG as specified by the parameter GLK.Creating the physical link connection on the GPRS Gb interface (Frame Relay Link): < The FRL functional object represents the 'Frame Relay Link' which is the physical link connection on the Gb interface. object: range: default: FRL ITU.

N393=4. Network Service Virtual Link Identifier.110.. object: range: default: FRL 1-255 4 N393. Congestion Timer.. This timer is needed to provide a hysteresis time in order to ensure that the traffic reduction at the mobile station can be effective. object: format: range: FRL path name of the PCU PCU:0. object: unit: range: default: FRL 1s 0. If the threshold is not reached the counters are restarted. 30 0 = no hysteresis time used 20 Creating the end-to-end communication between BSS and SGSN: Network Service Virtual Connection (NSVC): < The NSVC (Network Service Virtual Connection) functional object represent the end-to-end communication between BSS and SGSN. NSVCI=1110. the links are put in 'disabled' state. After a congestion notification. this parameter represents the common identification of the virtual connection between SGSN and BSS.65535 Object path name.PCU:11 Parameter name and format changed in BR7. Congestion off Timer. this timer represents the link integrity verification repetition period. object: range: NSVC FRLN: 0. the congestion state is notified to the upper layers.. this attribute represents the error observation window. TCONG=10. NSVLI=0. PCU Identifier. If the threshold N392 is reached within N393 * T391 time. range for NSVC: 0 – 755.. At each side of Gb interface. Network Service Virtual Connection Identifier. this attribute specifies the window for congestion abatement.0 (name changed from PCUN to PCUID)! T391=10. If the number of frames coming from SGSN containing congestion is equal or greater than the number of frames indicating no congestion. 10. 20. there is one to one correspondence between NSVC and NSVL then the NSVL can be seen as an attribute of NSVC. object: unit: range: default: FRL 1s 1-30 10 TCONOFF=20. > CREATE NSVC: NAME=nsvc:0. this attribute defines the instance number of the PCU object the FRL is connected to. no other notifications are foreseen for the time configured in this parameter. this parameter specifies the observation window for the congestion detection.755 DLCIN: 16-991 92 . this parameter defines the association of the FR-DLCI (Data Link Connection Identifier) and the FRL (Frame Relay Link). object: range: NSVC 0. Note: The value of the timer T391 set on the BSC side must be lower than the value of the timer T392 set either on the SGSN or the network side of the Frame Relay link. object: unit: range: default: FRL 1s 1-60 10 T391. It consists of two mandatory fields: FRLN and DLCIN. PCUID=PCU:0.

It performs all the Operation & Maintenance functions common to all transceivers.(*) The “no. . BTSM Abis TCH load threshold for FR activation.If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH. 93 . as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. both HR subslots busy) is counted as 2 while a SUBTSLB in usage state „active“ (only one HR subslot busy) is counted as 1.e. For Decompression handover the BSC calculates the BTSM Abis traffic load as follows BTSM Abis traffic load [%] = no..SUBTSLBs in usage state „busy“ ** .Creating the BTS Site Manager: < The BTS Site Manager represents the functionality that controls one or more BTSs within one BTSE. It defines the lower Abis pool TCH load threshold for load-dependent decompression handover. .> CREATE BTSM: NAME=BTSM:0.The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). If the Abis pool TCH load of the BTSM drops below the threshold ABISFRACTTHR. For further details..SUBTSLB in usage state „locked“ or „shutting down“ . the BTSM-no. object: unit: range: default: BTSM 1% 0. corresponds to the BTSE no. this parameter this parameter is only relevant if the parameters EADVCMPDCMHO and EADVCMPHOAMR (for AMR calls) and EADVCMPHOSC (for non-AMR calls) are set to TRUE (for the parameters please see SET HAND [BASICS]). an 8 kbit/s HR subslot of the SUBTSLB is counted as 1! .Generally a 16 kbit/s Abis TCH (SUBTSLB) is counted as 2.(**) A SUBTSLB in usage state „busy“ (i. of Abis pool TCH not available for CS TCH allocation“ includes . ABISFRACTTHR=30.100 30 Object path name. of Abis pool TCH in state unlocked/enabled ∗ 100 Attention: . the BSC enables deompression handover in the BTSs subordinate to the affected BTSM by sending a SET ATTRIBUTE message with the appropriate indications to the BTSs. please refer to the parameter EADVCMPDCMHO (see command SET HAND [BASICS]). the associated Abis subslots are regarded as ‘idle’ in any case. no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT. This message triggers the start the load-dependent AMR decompression handover decision process in the BTS. On every expiry of the timer TRFCT (see SET BSC) the BSC checks the current radio TCH load in its cells (see parameter FRACTTH1 and FRACTAMRTH1) and the current Abis TCH traffic load of its BTSMs and compares it to the threshold ABISFRACTTHR. The task of this handover type is to hand over as many calls that currently occupy a HR (or AMR-HR) TCH to an (E)FR (of AMR FR)TCH as possible to provide the best possible QoS and speech quality in time periods with an acceptably low TCH load and Abis pool TCH load. of Abis pool TCH in usage state ‘busy’* no.

ABISHRACTTHR defines a BTSM Abis traffic load threshold that is evaluated for the forced speech version selection for incoming TCH seizures. of configured Abis pool TCHs ∗ 100 Attention: . the HR activation also goes for AMR calls. this parameter is the equivalent of the parameter HRACTT1 (see command CREATE BTS [BASICS]) and defines an Abis traffic load threshold which is used for the following features: a) BTSM Abis Load Dependent Activation of Half Rate b) Enhanced Pairing of half rate TCHs due to Abis TCH load c) Compression handover due to Abis TCH load For all these features. Note: if the parameter EHRACTAMR (see command SET BTS [BASICS]) is set to TRUE.100 60 BTSM Abis TCH load threshold for HR activation.e. DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST.e. of Abis pool TCH not available for CS allocation * no. object: unit: range: default: BTSM 1% 0. DOWNGRADE_GPRS_ONLY. a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i. then all Abis subslots which are currently busy due to GPRS traffic are considered as ‘idle’.SUBTSLBs in usage state „busy“ ** . both HR subslots busy) is counted as 2 while a SUBTSLB in usage state „active“ (only one HR subslot busy) is counted as 1. . the application of this threshold is separately described for each of the involved features: a) Abis Load Dependent Activation of HR For the feature ‚Abis Load Dependent Activation of HR’ (see parameter EHRACT). as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. the associated Abis subslots are regarded as ‘idle’ in any case. If the calculated Abis TCH traffic load of the BTSM exceeds the percentage defined by ABISHRACTTHR.SUBTSLB in usage state „locked“ or „shutting down“ .The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]).* The “no. This ‘Abis pool’ is represented by all SUTSLB objects that are configured subordinate to the BTSM (for the exact definition of the term ‘Abis pool’ and the characteristics of the SUBTSLB objects please see command CREATE SUBTSLB).e. of Abis pool TCH not available for CS TCH allocation“ includes . DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE). an 8 kbit/s HR subslot of the SUBTSLB is counted as 1! .** A SUBTSLB in usage state „busy“ (i. all incoming calls are forced to FR or EFR (depending of the capability and preference indicated in the ASSIGNMENT REQUEST or HANDOVER REQUEST message).If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH. As the usage of the entered ABISHRACTTHR value depends on the feature used. then all Abis subslots which are currently busy due to GPRS traffic are considered as ‘busy’ like any other Abis resources currently seized by CS calls. no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT. all incoming calls or incoming handovers to cells of the affected BTSM (for which HR is indicated as supported speech version) are forced to a HR TCH. the BSC calculates an Abis TCH traffic load for the Abis pool assigned to the BTSM.ABISHRACTTHR=60. For this. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i. . 94 .Generally a 16 kbit/s Abis TCH (SUBTSLB) is counted as 2. For further details please refer to the parameter EHRACT. For the feature CLDAHR the BSC calculates the Abis traffic load as follows BTSM Abis traffic load [%] = no. This happens in all BTSs subordinate to the BTSM.. the BSC compares ABISHRACTTHR to the percentage of busy Abis TCHs (related to the available Abis TCHs) within the pool of available Abis TCHs for the BTSM. If the Abis TCH traffic load of the BTSM is below the percentage defined by ABISHRACTTHR.

.e.(*) The “no. both HR subslots busy) is counted as 2 while a SUBTSLB in usage state „active“ (only one HR subslot busy) is counted as 1. of Abis pool TCH in usage state ‘busy’* no. no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT.SUBTSLB in usage state „locked“ or „shutting down“ .Generally a 16 kbit/s Abis TCH (SUBTSLB) is counted as 2.ABISHRACTTHR[%] Attention: . an 8 kbit/s HR subslot of the SUBTSLB is counted as 1! .If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH.(**) For the ‘number of TCH configured in Abis pool’ each SUBTSLB is counted as ‘1’! . . if both HR subslots are idle. to transfer AMR-FR or (E)FR calls with suitably good radio link quality to an AMR-HR or HR TCH by an intracell handover in order to prevent TCH blocking by providing additional TCH resources.(*) An Abis TCH (SUBTSLB) is only considered as ‚idle’. . no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT. On every expiry of the timer TRFCT (see SET BSC) the BSC checks the current radio TCH load in its cells (see parameter HRACTAMRT1) and the current Abis TCH traffic load of its BTSMs and compares it to the threshold ABISHRACTTHR. in case of high TCH load. The enhanced pairing intracell handover is controlled exclusively by the BSC and is only triggered if either the percentage (within the pool of radio TCHs) of radio DR TCHs or/and radio FR TCHs in usage state “idle” has dropped below a definable threshold (see parameter HRACTT1) or/and the percentage (within the pool of Abis TCHs) of Abis DR TCHs or/and FR TCHs in usage state “idle” has dropped below a definable threshold. depends on the setting of the parameters EADVCMPHOAMR and EADVCMPHOSC (see command SET HAND[BASICS]). 95 .b) Enhanced Pairing of half rate TCH due to Abis TCH load The feature “Enhanced Pairing of TCH/H” (see parameter EPA in command SET BSC [BASICS]) transfers HR calls that currently occupy one HR subslot of a DR TCH (while the other subslot is still idle) in such a way that as many HR calls as possible share one Dual Rate TCH with another HR call.The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). For further details please refer to the parameter EPA (in command SET BSC).The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). this threshold is based on the parameter ABISHRACTTHR: intracell handovers due to enhanced pairing are triggered if the following BTSM Abis pool traffic load condition is fulfilled: no. the associated Abis subslots are regarded as ‘idle’ in any case.If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH. For enhanced pairing due to Abis TCH load. c) Compression handover due to Abis TCH load The task of Compression handover is. as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. .SUBTSLBs in usage state „busy“ ** .(**) A SUBTSLB in usage state „busy“ (i. of Abis pool TCH not available for CS TCH allocation“ includes . Whether AMR calls or/and non AMR calls are considered for this type of handover. of TCH configured in the Abis pool** ∗ 100 < 100% . the associated Abis subslots are regarded as ‘idle’ in any case. of Abis pool TCH in usage state ‚idle’ * no. For Compression handover the BSC calculates the BTSM Abis traffic load as follows BTSM Abis traffic load [%] = no. of Abis pool TCH in state unlocked/enabled ∗ 100 Attention: .

the BSC disables the traffic handover in the affected BTSs by sending another LAPD O&M message SET ATTRIBUTE with the ‘traffic handover disabled’ indication to the BTSM. . For this feature. see SET BSC) in all BTSMs and compares it to the threshold specified by ABISTRFHITHR. . Abis Traffic handover high threshold. no further message is sent to the BTS and the traffic handover remains enabled in the affected BTSs.. ABISTRFHITHR=90. This pool is represented by all SUTSLB objects that are configured subordinate to the BTSM (see command CREATE SUBTSLB). If the Abis traffic load in the BTSM is above the BTSM-specific threshold ABISTRFHITHRR.If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH. an 8 kbit/s HR subslot of the SUBTSLB is counted as 1! . This message starts the Compression handover decision process in the BTS. If the traffic handover was already enabled for a specific BTS on the previous expiry of TRFCT (either due to radio TCH load or due to Abis TCH load) and the radio traffic load in the affected BTS or/and the Abis traffic load of the BTSM are still above their threshold TRFHITH resp. please refer to the parameter EADVCMPDCMHO (see command SET HAND [BASICS]). the BSC calculates a current BTSM Abis TCH traffic load for the Abis TCH pool.100 90 If the Abis pool TCH load of the BTSM exceeds the threshold ABISHRACTTHR. of Abis pool TCH not available for CS TCH allocation“ includes .Generally a 16 kbit/s Abis TCH (SUBTSLB) is counted as 2. If the traffic handover was enabled for a specific BTS/BTSM on the previous expiry of TRFCT and both the radio traffic load in the affected BTS and Abis traffic load in the affected BTSM have dropped below the corresponding thresholds. The BSC cyclically checks the BTSM Abis traffic load (controlled by the timer TRFCT. For further details. as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT. this parameter is the equivalent to the paremeters TRFHITH (see SET HAND) and specifies the BTSM Abis traffic load threshold for enabling of traffic handover in the BTSM. This O&M message is the trigger for the BTS to start the traffic handover decision algorithm (for more details concerning the handover decision please refer to the appendix ‚Handover Thresholds and Algorithms’).SUBTSLBs in usage state „busy“ ** . The traffic load of a cell is calculated as follows: BTSM Abis traffic load [%] = no. object: unit: range: default: BTSM 1% 50. the associated Abis subslots are regarded as ‘idle’ in any case.as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. of Abis pool TCH in state unlocked/enabled Attention: . of Abis pool TCH in usage state ‘busy’* ∗ 100 no.e. ABISTRFHITHR. both HR subslots busy) is counted as 2 while a SUBTSLB in usage state „active“ (only one HR subslot busy) is counted as 1.SUBTSLB in usage state „locked“ or „shutting down“ . the BSC activates the traffic handover in the those BTSs (subordinate to the BTSM) for which traffic handover is enabled in the database (see parameter TRFHOE) by sending an LAPD O&M message SET ATTRIBUTE with the ‘traffic handover enabled’ indication to the BTSM. 96 .(*) The “no.(**) A SUBTSLB in usage state „busy“ (i.The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). the BSC enables Compression handover in the BTSs subordinate to the affected BTSM by sending a SET ATTRIBUTE message with the appropriate indications to the BTSs.

When the BSC has enabled the traffic handover in a specific BTS (see parameters ABISTRFHITHR and TRFHITH) the BTS makes a traffic handover decision and – if a suitable target cell is found sends an INTERCELL HANDOVER CONDITION INDICATION (HCI) with cause ‘traffic’ and a list of the determined target cells to the BSC.If the timers TEMPCH/TEMPPDT (see command CREATE PCU) are running for a particular PDCH.The GPRS downgrade strategy (see parameter DGRSTRGY in the command CREATE BTS [BASICS]) has an influence on the Abis traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). of Abis pool TCH not available for CS TCH allocation“ includes .Generally a 16 kbit/s Abis TCH (SUBTSLB) is counted as 2. If the traffic load in the first target cell / target BTSM is above the threshold. as these subslots are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. This means that it does not make any difference whether the originating cell of the traffic handover belongs to the same BTSM or not. no matter which values are set for the parameters DGRSTRGY and DGRSTRGYBCNT. of Abis TCH in usage state ‘busy’* no. the associated Abis subslots are regarded as ‘idle’ in any case. The traffic load of a cell is calculated as follows: BTSM Abis traffic load [%] = no. both HR subslots busy) is counted as 2 while a SUBTSLB in usage state „active“ (only one HR subslot busy) is counted as 1. Note: The BSC does not allow an incoming traffic handover towards a BTS from another BTS within the same BTSM.(**) A SUBTSLB in usage state „busy“ (i. . 85 70 Abis Traffic handover low threshold. 97 .e. object: unit: range: default: BTSM 1% 0. The BSC only activates a TCH in the target BTS.SUBTSLBs in usage state „busy“ ** .e.the next handover attempt HCI is then sent after expiry of TRFHOT (see SET HAND). this parameter specifies the maximum Abis traffic load a BTSM may have to accept incoming traffic handovers. if the Abis TCH load of that BTSM has exceeded the threshold ABISTRFLTHR. an 8 kbit/s HR subslot of the SUBTSLB is counted as 1! . the BSC checks the next target cell in the list and so on.SUBTSLB in usage state „locked“ or „shutting down“ .. If none of the target cells has a suitable load situation (i. if the cell traffic load > TRFLTH and/or Abis TCH load > ABISTRFLTHR ) the HCI does not lead to any successful handover completion . if the radio traffic load of this target BTS is below the threshold TRFLTH and if the Abis traffic load of the target BTSM is below the threshold ABISTRFLTHR. of Abis TCH in state unlocked/enabled ∗ 100 Attention: . if the handover conditions are still present.ABISTRFLTHR=70.(*) The “no. .

e. FALSE. which means that the non-BCCH-TRXs TRXs use the same set of hopping frequencies. as all cells within a BTSM are controlled by a common master clock. Usually. in some networks the frequency spectrum granted to the operators is so small that the number of available frequencies does not allow a suitable frequency distribution. 1/1 or 1/3) and interference management based on MAIO planning for the (synthesizer) hopping frequencies. For the non-BCCH-TRXs the operator may decide to deploy e. In fact. i. even the same frame numbers. object: range: default: BTSM TRUE. in a first step. However. The synchronicity within a site (i. in such networks. The synchronicity of the cells is based on GPS (Global Positioning System) technology. by default. the resource planning can therefore not be based on the frequencies only and a different approach must be used. This is done with the appropriate database parameters. However. In a second step. this parameter determines whether the feature ‘Inter-Site Synchronization’ (ISS) is enabled or not. as all cells of a BTSM start their operation at exactly the same point of time. within a BTSM) is guaranteed in any case.EINTSITSYN=FALSE. to achieve a controlled time de-coupling of the resources by an intelligent separation of MAIO values among the TRXs (and thus to optimally avoid co-channel interference and adjacent channel interference) the cells within a site and cells belonging to different sites must be. a 1/1 frequency reuse pattern.0. frequency planning is reduced to the BCCH-TRXs only. especially if the network must handle considerable traffic capacities. time-aligned and synchronized.e.g. GPS is used as time 98 . <NULL> FALSE Enable Inter-Site Synchronization. In such configurations the interference can be minimized by minimization of possible collisions of the hopping channels by an intelligent MAIO distribution (please see also explanations given for the feature DMA Admission Control in command SET BTS [ADM]). In these networks. all cells of the same BTSM have. the hopping patterns of the different TRXs can then be de-coupled by a suitable timing-offset value to each TRX. however.g. Purpose and principle of the ISS feature Usually the frequency planning in a GSM network is done in such a way that co-channel interference and adjacent channel interference between adjacent or colocated sites is avoided by an intelligent allocation of TRX frequencies and frequency subsets among the cells to be covered. can only be achieved with the feature ‘Inter-Site Synchronization’ (ISS) which was introduced in BR8. The feature ISS is mainly relevant for networks with a tight frequency reuse pattern (e. For other network types this feature is not really relevant. especially when the same hopping sequence (see parameter HSN in command CREATE FHSY and CREATE CFHSY) is used in all cells. cellA cellB BTSM cellC Frame n CellA CellB CellC TS0 TS0 TS0 TS1 TS1 TS1 TS2 TS2 TS2 TS3 TS3 TS3 TS4 TS4 TS4 TS5 TS5 TS5 TS6 TS6 TS6 TS7 TS7 TS7 Frame n + 1 TS0 TS0 TS0 TS1 TS1 TS1 The synchronicity of cells belonging to different sites.

B) With ISS: Also inter-site interference can be controlled by distributing MAIOs among the cells of different sites.. frame X-1 TS0 frame X TS7 frame X+1 BTSA frame X+14 TS0 frame X+15 TS7 frame X+16 BTSB frame X+4 TS0 frame X+5 TS7 frame X+6 BTSC The frame number offset can be administered by parameter FRANOFFS. As interference is always a capacity-limiting factor (considering the fact that usually every operator tries to achieve the highest possible 99 . the burst number offset is administered by parameter BURNOFFS (both parameters see command SET BTS [BASICS]). ISS thus allows the operator to allocate the available MAIOs (the number of which is determined by the number of frequencies used in the frequency hopping system (Mobile Allocation MA) to cells that are adjacent but do not belong to the same BTSM. . In case of a 1/1 reuse pattern for the hopping TCH-TRXs. a common frame numbering within a synchronized area is not desireable as this leads to simultaneous transmission of SCH and SACCH slots and thus impacts the BSIC and SACCH decoding. Example: 1/1 reuse configuration A) Without ISS: Only intra-site interference can be controlled by distributing MAIOs among the cells of the same site. As explained below in section ‘Impact of ISS on neighbour cells identification and SACCH peformance’. The purpose of ISS is to a) synchronize the cells of different sites and b) to introduce and control a fixed timing-offset (frame number offset and burst number offset) between cells of different sites.reference.

Moreover. 2). ISS can thus be used to extend the network capacity by reducing the inter-site interference. as this would mean a) simultaneous transmission of Synchronization Channel (SCH) slots in all cells (this impacts the BSIC decoding in a negative way and results in a lower performance of BSIC decoding and thus leading to a lower effectiveness of the handover algorithm). but should use pairs of TSCs that have a vanishing cross-correlation. due to the fact that SACCH messages are always transmitted regardless of the voice activity. Thus.traffic volume against a defined minimum QoS requirement). 4)). 7). Impact of ISS on Training Sequence Code (TSC) planning The training sequence code is transmitted in the center or each burst within a TDMA slot (please see also parameter TSC in command CREATE CHAN) and is used as an additional identification patterm in addition to the frequency itself. Impact of ISS on neighbour cells identification and SACCH peformance Chosing a common frame numbering for cells that belong to synchronized cluster is not desirable. the frame numbering of the synchronized cells should be 100 . to avoid degradation in channel estimation process a proper TSC planning has to be performed: cells operating on the same frequency should not use the same TSC. TDMA slot n Encrypted Bits TSC Encrypted Bits Desired burst Encrypted Bits TSC Encrypted Bits Interferer burst t Some combinations of TSCs may degrade receiver performance when the TSC values are not orthogonal (only four TSC pairs are orthogonal (0. 3) and (3. Therefore. the TSCs may arrive at the MS receiver approximately at the same time. b) simultaneous transmission of SACCH slots in the synchronized area which would increase the impact of interfering signals on the SACCH message decoding in a negative way. In synchronized networks. (0. (1. the positive effect of DTX (see parameter DTXDL in command SET BTS [OPTIONS]) on the SACCH decoding would be undone.

Emergency timer 1. these features offer the best possible interference reduction when ISS is activated. Note: BTSE emergency configuration can also be entered as a result of excessive shelter temperature in BS61 BTSEs (see explanation of parameter MOEC (CREATE TRX)). EMT1=10. 'BTSE emergency configuration' means that only the central BTSE control modules and the HW serving those TRXs which have been explicitly declared a 'Member of emergency configuration' (see parameter MOEC (CREATE TRX)) are powered. All other modules are switched off. similar effect like ‘0’) to really achieve a desynchronization of SCH and SACCH slots. the frame number offset may be different. Impact of ISS on Interference cancellation features The features UIC (Uplink Interference Cancellation) and SAIC (Single Antenna Interference Cancellation) provide the best performance when the interfering signal does not change its characteristics throughout the duration of the ‘desired’ signal’s burst in the serving cell. In this case BTSs of the same BTSM must have been configured with the same burst number offset (BURNOFFS). Thus. If it expires the BTSE enters the 'BTSE emergency configuration'. object: unit: range: default: BTSM 1min 0.ISS is only supported by BTSEs of generation BTSplus. .time de-coupled in a controlled way using the FRANOFFS parameter (see SET BTS [BASICS]): FRANOFFS should thus not be set to ‘0’ (means: no frame offset at all) or multiple values of 51 (length of a TDMA multiframe.Further the configuration of the GPS synchronization source the object SYNCBTSE (available only in the BTSE via BTSE-LMT) must be used. this parameter indicates the delay for the transition to the 'BTSE emergency configuration' in case of breakdown of the BTSE primary power supply if a battery backup is available in the BTSE. The timer EMT1 is started when the alarm 'ACDC MAINS BREAKDOWN' occurs.Multidrop.and Loop-configurations (see parameter L1TS in command CREATE BTSM) with mixture of Abis-synchronized BTSEs and GPS synchronized BTSEs is not allowed. Interaction of ISS and Dynamic MAIO Allocation (DMA) If feature DMA is enabled (see command CREATE CBTS for details about DMA). The purpose of the 'BTSE emergency configuration' is to save energy as long as the BTSE is supplied by the battery backup and thus to delay the point of time when the battery runs out of current (BTSE power off). handover bwtween BTSs of the same BTSM can be performed without transmission of the PHYSICAL INFO message (which is used for timing advance alignment). . the ISS parameters must be set in such a way that all cells (BTSs) within the site (BTSM) have the same values for frame number offset (FRANOFFS) and burst number offset (BURNOFFS). Interaction of ISS and ‘handover between finely synchronized cells’ If the feature ‘handover between finely synchronized cells’ is enabled (see parameter HOSYNC in command SET BSC [BASICS]).360 10 101 . Notes: ..

100 default: firstLevelUpperThreshold: 80 firstLevelLowerThreshold: 70 Emergency timer 2. object: BTSM format: firstLevelUpperThreshold firstLevelLowerThreshold unit: 1% range: 10. see command CREATE CTRSCHED) is enabled. object: unit: range: default: BTSM 1min 0. Note: . LAPDOVLT (CREATE BTSM) and DLAPDOVL (see command SET BSC [BASICS]). If no microwave equipment is used the 'zero carrier configuration' should be disabled (EMT2=0). 102 .. the expected SW load is immediately activated if it is available on the BTSE flash EPROMs. Note: All BTSE types also enter the 'zero carrier configuration' if the alarm 'RACK OVERTEMPERATURE' is raised.If IMSI Tracing (see command CREATE TRACE) or Cell Traffic Recording (CTR.0700_98-7-21".firstLevelLowerThreshold if the signalling traffic drops below this threshold the BTSE resumes sending MEASUREMENT RESULT (MEASUREMENT REPORT) messages on the Abis.The BTSE LAPD Overload thresholds are only used by BTSEs of the generation BTSplus. All other modules are switched off (call processing disabled). . MEASUREMENT REPORT messages are neither necessary for call processing nor for performance measurements.. For this reason they are suspended in case of LAPD overload. If it is not available an automatic download of this SW version from the BSC to the BTSE is initiated.firstLevelUpperThreshold if the signalling traffic exceeds this threshold the BTSE suspends sending MEASUREMENT RESULT (MEASUREMENT REPORT) messages on the Abis. If it expires the BTSE enters the 'zero carrier configuration'. This behaviour is not administrable. they lead to a drastic increase of the uplink load on the LPDLR links. 'BTSE zero carrier configuration' means that only the central BTSE control modules are powered. The timer EMT2 is started when the BTSE enters the 'BTSE emergency carrier configuration'. The sending of these messages is not suspended if the LAPD load exceeds FLAPDOVLTH. Expected SW version. this parameter indicates the delay for the transition to 'BTSE zero carrier configuration' in case of breakdown of the BTSE primary power supply if a battery backup is available in the BTSE.. . the BTS also sends MEASUREMENT REPORT messages. The purpose of the 'BTSE zero carrier configuration' is to keep the central control modules available if microwave-equipment is used. 0 EXPSWV="01-01-08-00. This SW load must be available and loaded in the BTSE. The difference is that in this case the MEASUREMENT REPORTs are not embedded in the MEASUREMENT RESULT but in the TRACE MEASUREMENT RESULT messages.Further parameters related to LAPD overload are SLAPDOVLTH. If these messages are sent. First LAPD overload threshold.360 0 = switch to 'zero carrier configuration' disabled. The sending of these messages can be optionally enabled using the parameter RADIOMR (see command CREATE/SET TRX) for test or monitoring purposes. object: BTSM FLAPDOVLTH=80-70. . The MEASUREMENT RESULT resp. It consists of two fields: The fields of this attribute of type sequence are: .EMT2=0. If during the alignment between BSC and BTS a different SW version than the expected one is detected. this parameter determines the SW version which should be loaded and running in the BTSE from the BSC's point of view. this parameter represents the first load level thresholds of the BTSE Radio Signalling links (LPDLRs).

10. these are better kept free for incoming CS traffic instead of first upgrading a running TBF and then pre-empting it again to serve the CS call. E. This implies that the related Abis subslots are thresholdIdleAbisSU: 0 also shared and results in saving Abis resources..100 vertical allocation strategy due to Abis scarcity is activated. new TBFs are preferably multiplexed on thresholdAbisVH: 20 already used PDCHs. The fourth field (thresholdIdleAbisRU) defines the percentage of idle Abis subslots (over the available Abis subslots) over which the Abis upgrade requests towards the TDPC are allowed again. It is composed of four fields. Note that there is no constraint between the Abis threshold to switch to vertical allocation and the Abis threshold to disable the ‘Abis upgrade requests’.: If only very few Abis resources are available (1 or 2 subslots). the first allocation of Abis resources to a TBF is performed with the same criteria used under normal conditions (looking at the candidate’s initial coding scheme).. 103 . The main purpose of this parameter is to avoid oscillating allocation/preemption cycles in case of Abis shortage.GASTRABISTH=10.g. but further upgrading of Abis resources is forbidden. Constraints on the Abis thresholds are: thresholdIdleAbisSU <= thresholdIdleAbisRU. thus increasing the signaling load of the system due to multiple reconfiguration activities.20. and vice versa.. ThresholdIdleAbisSU=0 means that the upgrade of TBF resources is stopped only after no Abis resources were left at all – the resumption of upgrades is then triggered with the below parameter. thresholdIdleAbisHV <= thresholdIdleAbisVH. thresholdIdleAbisRU: 10 The second field (thresholdIdleAbisVH) defines the percentage of idle Abis subslots (related to the available Abis subslots) over which the horizontal allocation strategy is activated again (if also the thresholds for the radio resources allow that – see GASTRTH in object PTPPKF). thresholdIdleAbisSU The first field (thresholdIdleAbisHV) defines the percentage of idle thresholdIdleAbisRU unit: 1% Abis subslots (related to the available Abis subslots) under which the range: 0. GPRS allocation strategy Abis thresholds. this parameter is the Abis equivalent to the parameter GASTRTH (see CREATE PTPPKF) used to control the switch from/to vertical/horizontal allocation object: BTSM format: thresholdAbisHV strategy and the stop/restore of PDCH upgrading due to Abis thresholdAbisVH scarcity. When this threshold is reached.0. If vertical default: thresholdAbisHV: 10 allocation is activated. the operator is free to set the one lower than the other.. The third field (thresholdIdleAbisSU) defines the percentage of idle Abis subslots (over the available Abis subslots) under which the PCU stops sending Abis upgrading requests towards the TDPC.

LAPDOVLT=10,
object: unit: range: default: BTSM 1s 1..60 10

LPDLMSAT=FALSE,
object: range: default: BTSM TRUE, FALSE FALSE

LAPD overload timer, this parameter defines the time to pass between two consecutive LAPD OVERLOAD indication messages. These messages are sent on the LAPD O&M link (LPDLM) when the LAPD load threshold defined by the parameter SLAPDOVLTH (see below) is exceeded and indicate the LAPD overload per TRX. The BTSE LAPD Overload handling and reporting based on the thresholds FLAPDOVLTH and SLAPDOVLTH are only used by BTSEs of the generation BTSplus. Please see also parameter DLAPDOVLH in command SET BSC [BASICS]). LPDLM via satellite, this attribute indicates whether the Abis resp. LPDLM is realized via satellite link (TRUE) or not (FALSE). If the Abis interface link is configured as satellite link, the generally higher signal delay must be particularly taken into account by the LAPD layer 2 functions of the BTS O&M link (LPDLM) and the BTS radio signalling links (LPDLR). Setting LPDLMSAT=TRUE has the following effects: The LAPD timers T200 and T201 (waiting timers for LAPD acknowledgement frames) as well as the associated window sizes (the 'window size' is simply the number of I-frames that may be sent without any acknowledgement from the opposite side) are automatically extended according to the following table:

4

These settings ensure that the higher signal delay on the link does not lead to unnecessary retransmission of LAPD layer 2 frames. Notes: - The satellite mode of the Abis link has to be activated in the BTSE as well. This is done by the parameter ABISLKSAT in the command SET BTSM (at the BTSE LMT). The effect is the same as described above - just for the opposite direction. - Since the implementation of CR2716 in BR7.0 the setting LPDLMSAT=TRUE has an effect on call processing: To reduce the delay between the CHANNEL REQUEST and the IMMEDIATE ASSIGNMENT COMMAND messages, the BSC sends the IMMEDIATE ASSIGNMENT message immediately after sending the CHANNEL ACTIVATION message, without waiting for the CHAN ACT ACK. Thie means that the BSC saves the time for the completion and acknowledgement of the (satellite-link-delayed) Abis channel activation procedure. As this procedure has an expected success rate of 100% (it is only unsuccessful if the BTS itself has a serious problem) it is not mandatory to wait for a positive acknowledgement before the IMMEDIATE ASSIGNMENT message can be sent. This approach drastically reduces the RACH retransmissions due to delayed IMMEDIATE ASSIGNMENT and thus avoids unnecessary load on the SDCCHs. - If an Abis is realized via satellite link (or has a considerably increased delay due to other transmission equipment) it is strongly recommended to set the parameter NSLOTST (see SET BTS [CCCH]) to ‚14’ to achieve the longest possible RACH retransmission cycle. This avoids unnecessary retransmissions that lead to unnecessary SDCCH seizures and thus to a decrease of the Immediate Assignment Success Rate (or even SDCCH congestion). - When an Abis interface is configured via satellite, it is urgently recommended to configure multiple SDCCH channels on different TRXs. This is necessary because the Abis LAPD transmit queues in the BTS are managed per TRX(TEI), i.e. each TRX (TEI) has an own transmit queue. As the biggest percentage of all signalling activities
104

OMLAPDRT=17,
object: unit: range: default: BTSM 1s 3-300 30

recommended value: 17

in a cell are processed via the SDCCHs, it is recommended, to avoid an excessive concentration of the SDCCH signalling within one TRX (and thus one LPAD transmit queue), to distribute multiple SDCCHs over different TRXs within the cell. Otherwise the probability of the BTSE alarm ‘LAPD TRANSMIT QUEUE OVERFLOW’ will considerably increase, although with a more even distribution of the signalling load over the TEIs this could be avoided. - Also the Asub interface and the A interface (parameter ASUBISAT in command SET BSC[BASICS]) can be configured as satellite link. However, only one of the mentioned interfaces should be configured as satellite link at the same time, because multiple satellite links within a BSS may cause an overall message and procedure delay that might lead to expiry of procedure supervision timers that are normally adapted to the propagation delay of terrestrial signalling links or at least to only one satellite link in the path. Although multiple satellite links are not officially tested and released, the BSC command interpreter and DBAEM do not perform any checks to avoid multiple satellite links - it is up to the operator to follow this rule. O&M LAPD release timer, this parameter represents a BTSE timer which is started after the detection of a LAPD (i.e. layer 2) interruption on the Abis link. As long as this timer runs, the BTSE maintains the call processing activity (i.e. BCCH active) in the subordinate cells. When the timer expires the BTSE call processing is blocked and functional related Managed Objects (BTS, TRX, CHAN, HAND, PWRC, ADJC, ADJC3G etc.) are deleted. In this case no BCCH information is broadcast in the subordinate cells anymore and this results in a cell reselection of the mobile stations that previously camped in this cell. After recovery of the LAPD link a ‘full alignment’ is necessary to put the BTSE in service again, as this procedure recreates and re-establishes the functional object database in the BTSE which were deleted by the expiry of OMLAPDRT before. Summary: On detection of an Abis LAPD link failure the BTSE starts the timer OMLAPDRT and the BSC starts the timer SHLAPDIT. If the OMLAPDRT expires the BTSE blocks the call processing and deletes all functional objects. On link reestablishment the BTSE forces the BSC to perform a full Abis alignment if one of the two timers has expired. If the Abis link (LAPD connection) is recovered before one of the two timers expires, the BSC performs a ‘Short Abis Alignment’ (also called ‘fast alignment’) after recovery of the Abis link. When SHLAPDIT expires, all ongoing calls in then affected cells (including ASCI group calls VBS and VGCS) are released by the BSC. Application: The timers SHLAPDIT and OMLAPDRT are relevant for a) LAPD interruption due to PPXL switch b) LAPD interruption to a certain BTSE within a multidrop chain. Here it has to be considered that the failure of the PCMB object (i.e. PCM link error between BSC and the first BTSE in the chain) always leads to a full alignment of all BTSEs in the chain after link recovery. If the PCM link error occurs between two BTSEs in the chain a full alignment is avoided if the link comes up before expiry of SHLAPDIT. Notes: - OMLAPDRT should be greater than SHLAPDIT since a ‘fast alignment’ (SHLAPDIT not yet expired when the layer 2 comes up) only makes sense if call processing has not been blocked (and the functional objects have not been deleted in the BTSE) by the expiry of OMLAPDRT before! As, on the other hand, it does not make sense to keep a BTSE with a failed LAPD connection on air even after the expiry of SHLAPDIT in the BSC (which leads to a full alignment after link recovery anyway) and as it is generally not useful to keep a BTSE with afailed LAPD connection on air for a too long time (and thus to prevent any originating call setup), the recommendation is to use the following setting

105

PCMCON0=PCMB_000PORT_0,
object: format: BTSM pcmbNumber0 portNumber0 value format: pcmbNumber0: PCMB_nnn portNumber0: PORT_m

SHLAPDIT=15, OMLAPDRT=17. Exception: In cells where ASCI features (VBS,VGCS) are enabled, it is recommended to set OMLAPDRT to a generally smaller value and, particularly, to a smaller value than SHLAPDIT to speed up the cell reselection in case of a LAPD link interruption. This is necessary in order to prevent the ASCI MSs from ‘listening’ to the Notification Channel NCH (and attempting to ‘join’ the ASCI common channel) in the cells where the ASCI common channel has already been released after expiry of SHLAPDIT. In this case, it is recommended to apply the following settings: SHLAPDIT=12, OMLAPDRT=10. - Please consider that normally, together with the LAPD link interruption, also the speech path (i.e. the used Abis TCH) is interrupted, so that all ongoing calls will be released by a CONNECTION FAILURE INDICATION with cause ‘remote transcoder failure’ after expiry of TSYNC or TSYNCDL (see command SET BTS [TIMER]). - For both timers some additional delay time for the detection of the layer 2 failure (up to 10 s) has to be taken into account. PCM connection 0, this attribute indicates the main PCM connection for the BTSM, i.e. it indicates to which BTSM port it is connected. Depending on the LPDLM configuration two cases must be distinguished: a) If only one LPDLM is configured for the BTSM, PCMCON0 indicates which PCMB carries the LPDLM. b) If more than one LPDLM is configured for the BTSM, PCMCON0 indicates which PCMB carries LPDLM:0. Notes: - Port numbers specified in all PCMCONx (x = 1..4) attributes must be compatible with the BTS hardware version, as shown in the table below:

PCMCON1=<NULL>,
object: format: BTSM pcmbNumber1 portNumber1 value format: pcmbNumber1: PCMB_nnn portNumber1: PORT_m default: <NULL>

The values PORT_2, PORT_4 or PORT_6 can be selected only if the object COSA is installed; with object COBA installed only the value PORT_0 can be selected. The hardware object PORT_<n> corresponds to the object BPORT:<n>. At the BTSE side, the BPORT object must be previously created by means of the CREATE BPORT command. - Please see also command CREATE SUBTSLB. PCM connection 1, this attribute indicates the first auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. Depending on the LPDLM configuration two cases must be distinguished: a) If only one LPDLM is configured for the BTSM, PCMCON1 indicates which PCMB does not carry the LPDLM. b) If more than one LPDLM is configured for the BTSM, PCMCON1 indicates which PCMB does not carry LPDLM:0. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

106

PCMCON2=<NULL>,
object: format: BTSM pcmbNumber2 portNumber2 value format: pcmbNumber2: PCMB_nnn portNumber2: PORT_m default: <NULL>

PCM connection 2, this attribute indicates the second auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

PCMCON3=<NULL>,
object: format: BTSM pcmbNumber3 portNumber3 value format: pcmbNumber3: PCMB_nnn portNumber3: PORT_m default: <NULL>

PCM connection 3, this attribute indicates the third auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

PCMCON4=<NULL>,
object: format: BTSM pcmbNumber4 portNumber4 value format: pcmbNumber4: PCMB_nnn portNumber4: PORT_m default: <NULL>

PCM connection 4, this attribute indicates the fourth auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

PCMCON5=<NULL>,
object: format: BTSM pcmbNumber5 portNumber5 value format: pcmbNumber5: PCMB_nnn portNumber5: PORT_m default: <NULL>

PCM connection 5, this attribute indicates the fifth auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

PCMCON6=<NULL>,
object: format: BTSM pcmbNumber6 portNumber6 value format: pcmbNumber6: PCMB_nnn portNumber6: PORT_m default: <NULL>

PCM connection 6, this attribute indicates the sixth auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

PCMCON7=<NULL>,
object: format: BTSM pcmbNumber7 portNumber7 value format: pcmbNumber7: PCMB_nnn portNumber7: PORT_m default: <NULL>

PCM connection 7, this attribute indicates the seventh auxiliary PCM connection for the given BTSM, i.e. it indicates to which BTSM port it is connected. The port numbers must be selected in correspondence with the HW of the BTSE (please refer to the ‘Notes’ in the description of PCMCON0, see above).

107

SALUNAME=”BSC1BTSE0”,
object: range: default: BTSM alphanumeric string (11 characters) in quotation marks NOT_DEFINED

SHLAPDIT=15,
object: unit: range: default: BTSM 1s 3-20 15

SLAPDOVLTH=90-80,
object: BTSM format: secondLevelUpperThreshold secondLevelLowerThreshold unit: 1% range: 10..100 default: secondLevelUpperThreshold: 90 secondLevelLowerThreshold: 80

Sales Unique Name, this attribute defines every Network Element by its unique symbolic name. It can be optionally used for the network element identity verification during the alignment phase in addition to the TEI (see parameter TEI). In previous releases (up to BR4.5) the (LPDLM-)TEI was the only criteria used for the network element identity verification during the alignment procedure. The new approach using the Sales Unique Name in addition to an individually configurable TEI allows a much higher flexibility in the allocation of the BTSEs to the BSCs (with minimization of efforts in case of BTSE swap) without loss of safety. Short LAPD interruption timer, this parameter represents a BSC timer which is started after the detection of a LAPD interruption on the Abis link. As long as this timer runs all active calls are maintained, i.e. kept alive. If the LAPD interruption exceeds the time defined by SHLAPDIT all calls in the affected BTSE are released and a ‘full alignment’ is performed after link recovery. When the LAPD link has recovered after expiry of SHLAPDIT, the BSC waits for another 30 seconds before it starts the ’full alignment’. If the LAPD link comes up again before the timer expires only a ‘fast alignment’ procedure is started. ‘Fast alignment’ is a subset of the ‘full alignment’ and comprises only the state alignment and the alarm alignment, but not the creation of functional objects. Please see also the explanation for OMLAPDRT. This timer is also used for supervision of RSL. If an RSL fails for longer than this time limit (O&M link survives) only the channels of the affected TRX are released. Second LAPD overload threshold, this parameter defines the second load level thresholds (in percentage) of the BTSE Radio Signalling links (LPDLRs). It consists of two fields: - secondLevelUpperThreshold if the signalling traffic overcomes this threshold the BTSE starts the periodic sending of LAPD OVERLOAD messages. - secondLevelLowerThreshold if the signalling traffic falls below this threshold the BTSE stops periodic sending LAPD OVERLOAD messages. These messages are sent on the LAPD O&M link (LPDLM) when the LAPD load threshold defined by SLAPDOVLTH is exceeded and indicate the LAPD overload per TRX. The time period between two consecutive LAPD OVERLOAD indication messages is determined by the parameter LAPDOVLT. Notes: - Further parameters related to LAPD overload are FLAPDOVLTH, LAPDOVLT (CREATE BTSM) and DLAPOVL (see command SET BSC [BASICS]). - The BTSE LAPD Overload thresholds are only used by BTSEs of the generation BTSplus. - If the exceeding of SLAPDOVLTH triggers the sending of LAPD OVERLOAD messages towards the BSC and the parameter DLAPDOVL (SET BSC [BASICS]) is set to TRUE, the BSC starts traffic reduction measures as described in the section ‘BTS overload’ in the chapter ‘BSC, MSC and BTS Overload handling’ in the appendix of this document.

108

TEI=0,
object: range: BTSM 0...63

Terminal endpoint identifier of LPDLM, this attribute defines the TEI of the LPDLM resp. BTSM. The TEI is the basic criteria used for the network element identity verification during the alignment procedure. In previous releases (up to BR4.5) the TEI had a fixed (i.e. not changeable) correspondence to the relative object number of the LPDLM resp. BTSM (i.e. BTSM/LPDLM-no.=TEI-no.). This approach had the disadvantage that in case of BTSE swap the TEI had to be manually changed in the BTSE to the new LPDLM-no. in the new BSC. As a temporary solution, the parameter FIXTEI was introduced which allowed to set all TEIs of the BTSMs to ‘0’. The parameter FIXTEI was removed in BR5.0 as from BR5.0 on the TEI can be explicitly set for every LPDLM by the parameter TEI. Thus in case of a swap of BTSE from one BSC to another, the TEI can be easily set in the database of the new BSC by the SET BTSM command without any necessity to modify the BTSE data on site. As with this new approach one and the same TEI can be used more than once within a BSC, another BTSE specific identity can optionally be used to unambiguously identify the BTSE during the alignment: the Sales Unique Name (see parameter SALUNAME).

109

Creating the Common BTS data of a BTSM for Dynamic MAIO Allocation (DMA):
< With this command the CBTS object is created which defines the data common for all BTSs of the BTSM which are necessary for the configuration of the synthesizer frequency hopping mode with the feature ‘Dynamic MAIO Allocation’ (DMA). The CBTS object defines the common pool of TRX/hopping frequencies shared by all BTSs that belong to the BTSM (for general information about frequency hopping please refer to the parameters HOPP and HOPMODE in command SET BTS [OPTIONS]). Purpose and principle of the DMA feature Static MAIO Allocation Up to BR7.0 in the Siemens BSS only ‘Static MAIO Allocation’ (SMA) is was supported for Frequency Hopping. SMA means that the hopping characteristics of a TCH resource that participates in a hopping pattern is fixed defined by - Mobile Allocation MA (list of frequencies included in the hopping pattern) - Hopping Sequence Number HSN (determines, together with the number of frequencies in the MA, the hopping algorithm or hopping sequence) - Mobile Allocation Index Offset MAIO (determines the position of that particular TCH within the hopping sequence). In case of SMA, the MA and HSN may be defined a) in the FHSY object (see command CREATE FHSY), in this case the MAIO can be defined (together with the relevant FHSYID) in the CHAN object that represents the TCH (see command CREATE CHAN) or in the TRX object (see command CREATE TRX). b) in the CFHSY object (see command CREATE CFHSY), in this case the MAIO can only be defined (together with the relevant FHSYID) in the TRX object (see command CREATE TRX). The definition of FHSYID and MAIO in the TRX object was introduced in BR8.0 as usually all TCHs of the same TRX are defined with the same FHSY and MAIO combination (which means that the hopping pattern is the same for all adjacent TCHs on a TRX). Dynamic MAIO Allocation DMA is is a feature designed for network configurations with Synthesizer Frequency Hopping and a 1/1 frequency reuse on the non-BCCH TRXs. Remarks on 1/1 frequency reuse: Usually the frequency planning in a GSM network is done in such a way that co-channel interference and adjacent channel interference between adjacent or colocated sites is avoided by an intelligent allocation of TRX frequencies and frequency subsets among the cells to be covered. However, in some networks the frequency spectrum granted to the operators is so small that the number of available frequencies does not allow a suitable frequency distribution, especially if the network must handle considerable traffic capacities. In these networks, the resource planning can therefore not be based on the frequencies only and a different approach must be used. Usually, in such networks, frequency planning is reduced to the BCCH-TRXs only. For the non-BCCH-TRXs the operator may decide to deploy e.g. a 1/1 frequency reuse pattern, which means that the non-BCCH-TRXs TRXs use the same set of hopping frequencies. In such configurations the interference is minimized by minimization of possible collisions of the hopping channels by an intelligent MAIO management (please see also explanations given for the feature
110

DMA Admission Control in command SET BTS [ADM]). In such networks, SMA can be applied if an intelligent MAIO planning is ensured: although the same MA frequencies are used in the hopping pattern of the cells (sectors) of the same site, interference can be avoided by splitting the set of MAIOs allocated to the site into three subsets with different MAIOs for each cell (sector). Precondition: all cells of the site must be frame-numbersynchronized, i.e. all cells have the same frame numbering (please see also parameter EINTSITSYN in command CREATE BTSM).
MA Random Hopping (1, 2, 10, 7, . . . )
BCCH MAIO = 0 MAIO = 6 MAIO = 12 TRX0 TRX1 TRX2 TRX3

Time (TDMA frame)
BCCH MAIO = 4 MAIO = 10 MAIO = 16 TRX0 TRX1 TRX2 TRX3 BCCH MAIO = 2 MAIO = 8 MAIO = 14 TRX0 TRX1 TRX2 TRX3

This configuration, however, only works fine as long as the number of hopping TRXs in the BTSM (site) does not exceed the number of frequencies available in the Mobile Allocation (the MA is the list of hopping frequencies, which is in this case the same for all cells of the site). As the number of frequencies defined in the MA simultaneously determines the number of available MAIOs, MAIO re-use is an obligatory consequence if the number of hopping TRXs in the BTSM exceeds the number of frequencies in the common MA. MAIO reuse, however, in any case means a continuous intra-site co-channel interference. As the distribution of traffic among the cells of a BTSM is usually not exactly balanced and may vary temporarily, it is reasonable not to split the available pool of MAIOs into fixed subsets (as done in case of SMA) as this lacks the required flexibility. Instead, it is reasonable to apply DMA, which regards the complete pool of MAIOs defined by the commonly used Mobile Allocation as a common resource on site level and which uses an intelligent and sophisticated algorithm which assigns, during TCH allocation, those TCHs first whose combination of timeslot and MAIO has the smallest possible impact on the overall interference. DMA increases the network capacity if the number of TRXs per site (BTSM) exceeds the number of available hopping frequencies and if the traffic is inhomogeneously distributed among the sectors of the site. The Dynamic MAIO Allocation (DMA) algorithm The DMA algorithm processes the following input data: • a list of free time slots of the serving cell • a list of MAIOs available for DMA • a table with the number of occurrences of dynamic MAIO values within the site for each timeslot • table with allocation state of dynamic MAIO values within the serving cell for each timeslot For each incoming voice call the DMA algorithm: • selects a channel on the basis of the current MAIO utilization within the site • operates on the entire timeslot x MAIO domain • uses and reuses all MAIOs in all sectors of the site

111

DMA algorithm channel selection principles: The DMA channel allocation algorithm • avoids MAIO repetition in the serving cell (thus avoiding intra-cell co-channel interference) • minimizes the number of MAIO repetitions within the site (thus minimizing the number of channels affected by intra-site cochannel interference) • controls the number of MAIO adjacencies in the serving cell (thus minimizing the number of channels affected by intra-cell adjacent channel interference) • controls the number of MAIO adjacencies within the site (thus minimizing the number of channels affected by intra-site adjacent channel interference) DMA feature preconditions & requirements • DMA applies to speech calls only (AMR, non-AMR) • DMA only applies to Synthesizer Frequency Hopping only • Within the site the same hopping system is used. This common frequency hopping system consists of - a Cell Allocation (list of used frequencies) common for all cells of the BTSM (site), which is defined by the parameter CCALLFxy (see command CREATE CBTS below) - a Mobile Allocation (list of used frequencies) and Hopping Sequence Number (HSN) common for all cells of the BTSM (see parameters CMOBALLOC and HSN in command CREATE CFHSY). • all cells of the site must be air-interface-synchronized • service layers not exclisively dedicated to speech services (e.g. service layers for data calls and (E)GPRS) can only use Static MAIO allocation (SMA). In case of DMA, the Mobile Allocation and HSN can only be defined be defined in the CFHSY object (see command CREATE CFHSY) the MAIO can only be defined (together with the relevant FHSYID) in the TRX object (see command CREATE TRX). The previously known administration of hopping parameters in the CHAN object is not possible for those TRXs where DMA is applied. Interworking of DMA, SMA and Multi Layer Service Support (MSLS) All TRXs belonging to service layers that support other services than ‘CS speech only’ cannot use DMA - on these layers SMA has to be used (for further details about MSLS please see command CREATE CBTS). Basically there are two main possibilities to configure SMA and DMA in parallel within a BTS: a) Separate frequency sets used for DMA and SMA - The DMA layers use a Cell Allocation (list of cell frequencies) as defined by the CCALL parameter (see command CREATE CBTS) the and a Mobile Allocation (i.e. list of hopping frequencies) as defined by parameter CMOBALLOC (see command CREATE CFHSY). Here the CFHSYID and MAIO data must be assigned in the TRX object. - The SMA layers use a Cell Allocation (list of cell frequencies) as defined by the CALL parameter (see command CREATE BTS) the and a Mobile Allocation (i.e. list of hopping frequencies) as defined ny parameter MOBALLOC (see command CREATE FHSY). Here the FHSYID and MAIO data can be either assigned in the TRX object or in the CHAN objects subordinate to the SMA TRX.

112

b) Common set of frequencies used for DMA and SMA In this configuration the DMA layers and SMA layers use the same Cell Allocation (list of cell frequencies) as defined by the CCALL parameter (see command CREATE CBTS) the and a Mobile Allocation (i.e. list of hopping frequencies) as defined by parameter CMOBALLOC (see command CREATE CFHSY). Here the CFHSYID and MAIO data - of the DMA layer TRXs must be configured in the TRX object - of the SMA layer TRXs can be either configured in the TRX object or in the CHAN objects subordinate to the SMA TRX. The MAIO values assigned to the DMA layer TRXs are only in effect when DMA is still disabled (ENDMA=FALSE in BTS and CBTS object). When DMA is enabled, the number of available MAIOs is automatically determined by the number of hopping frequencies in the Mobile Allocation. This pool of MAIOs is then used as a common resource on BTSM (=site) level and allocated in correspondence with the described above. Attention: When the SMA TRXs use the same CFHSY like the DMA TRXs, the BSC excludes the MAIO values of the SMA TRXs automatically from the pool of MAIOs that can be used and allocated for calls on the DMA layers. If for both the SMA and DMA TRXs the CFHSYID and MAIO data are assigned in the TRX object, there is no visible difference in the TRX creation data between the SMA from the DMA TRXs. The BSC can distinguish the SMA from the DMA TRXs by their service layer association: all TRX belonging to ‘CS speech only’ service layers are regarded as DMA TRXs, all others are considered for SMA. DMA Admission Control To avoid the allocation of channels with unacceptable interference figures, the feature ‘DMA Admission Control’ is used. For this feature, please refer to the description provided for the command SET BTS [ADM]. As mentioned above, another feature to be considered in networks with 1/1 frequency reuse (together with SMA and DMA) is ‘Inter-Site Synchronization’ (ISS). For further information about this feature, please refer to parameter EINTSITSYN in command CREATE BTSM.> CREATE CBTS: NAME=BTSM:0/CBTS:0, CCALLF01=77,
object: CBTS range: 0..1023 each field Reference: GSM 04.08 GSM 05.02 GSM 12.20

Object path name. Common cell allocation frequency 1, this parameter defines the first non-BCCH radio frequency allocated to all cells of the BTSM for Dynamic MAIO Allocation. Further frequencies used in the cell are set with the remaining parameters CCALLF02..CCALLF63. Which frequency numbers are allowed, depends on the used frequency band: SYSID=BB900: 1..124 SYSID=F2ONLY900: 0..124, 975..1023 SYSID=EXT900: 0..124, 975..1023 SYSID=DCS1800: 512..885 SYSID=GSM850: 128..251 SYSID=GSM850PCS: 128..251, 512..885 SYSID=GSM850DCS: 128..251, 512..810 SYSID=GSMR: 955..974 SYSID=PCS1900: 512..810

113

prior to command execution. DMA is enabled in the BTS object first (see parameter ENDMA in command CREATE BTS). FALSE FALSE Common cell allocation frequencies 2 to 63.) have been consistently and conclusively created in the database before.. whether all associated objects (CFHSY. In the DBAEM.In the DBAEM. In other words.. . the enabling of DMA is not possible together with the creation because for the DMA enabling both the DBAEM and the BSC command interpreter check.To be in effect. CHAN etc. For each frequency an own parameter is available . this parameter is listed within a SET CBTS command behind the CREATE CHAN commands. Notes: .to save space. they were summarized here in one table line. object: range: default: CBTS TRUE.CCALLF63 object: range: CBTS 0. TRX. 114 . this parameter determines whether the feature ‘Dynamic MAIO Allocation’ is enabled in the CBTS object.CCALLF02. DMA must be enabled both in the BTS and the CBTS object. Enable Dynamic MAIO Allocation. these parameters define all the remaining non-BCCH radio frequencies allocated to all cells of the BTSM for Dynamic MAIO Allocation (see CCALLF01).1023 each fiel ENDMA=FALSE.

Variant b) can be used for .08 Object path name.. When DMA is enabled. if DMA is to be used.1023 (each field) Reference: GSM 05.. Starting from BR8. b) the frequency hopping system is defined per BTSM (per site) in the CFHSY object which is subordinate to the CBTS object. For further details about DMA please refer to the command CREATE CBTS.0. the allocation of a FHSY and MAIO can alternatively be done in the TRX object (see command CREATE TRX). Common Mobile allocation list. the defined MAIO is no longer relevant as for the channels. Variant a) can be used for Static MAIO Allocation (SMA) only.02 GSM 04.Creating the hopping laws used for Dynamic MAIO Allocation: < With this command the hopping systems used for cells in which Dynamic MAIO Allocation is to be applied (CFHSY= Common Frequency Hopping System). determines the hopping sequence number commonly used in the site that is configured for DMA.Dynamic MAIO Allocation (see above). The below listed command CREATE FHSY is thus only relevant for variant (b).08 Common Hopping sequence number.0). which means that the BTS-specifically defined hopping system (FHSY) is allocated to the CHAN object toghether with a fixed MAIO value (see command CREATE CHAN for TCH and SDCCH) which determines the position of that particular channel in the applied hopping sequence. object: CFHSY range: 0.. > CREATE CFHSY: NAME=BTSM:0/CBTS:0/CFH SY:0. HSN=10.Static MAIO Allocation (see above). which means that the BTSMspecifically defined hopping system (CFHSY) is allocated to the TRX object toghether with a fixed MAIO value (see command CREATE TRX) which determines the position of the channels subordinate to the TRX in the applied hopping sequence when Dynamic MAIO Allocation (DMA) is not used by the service layer assigned to that TRX..0 the definition of frequency hopping systems can be done in two different ways: a) the frequency hopping system is defined per BTS (per cell) in the FHSY object (see command CREATE FHSY)which is subordinate to the affected BTS (as done in releases before BR8.. Starting from BR8. .008 GSM 04. CMOBALLOC=CCALLF01& CCALLF02&. this parameter defines is a list of those common cell allocation frequencies (defined in the CBTS object) which are used in the hopping sequence for the BTSM/CBTS.e. MAIOs are dynamically assigned by a special algorithm. 115 . i.63 Reference: 3GPP 45. which means that the BTSM-specifically defined hopping system (CFHSY) is allocated to the TRX object toghether with a fixed MAIO value (see command CREATE TRX) which determines the position of the channels subordinate to the TRX in the hopping sequence when DMA is not enabled (see parameter ENDMA in commands CREATE CBTS and CREATE BTS [BASICS]). object: CFHSY range: 0.

Configurations with multiple LPDLM per BTSM It is possible to create more than one LPDLM for a particular BTSM. while Abis RSL messages are always addressed with SAPI=0. Abis channel: pcmb-no. the number of LPDLRs handled by each LPDLM is more or less the same. The Abis timeslot which is configured as LPDLM ais always used . i.3 Object path name. Creating the LPDLM links: < The LPDLM link is the LAPD channel assigned to a BTS Site Manager for O&M Information between BSC and BTSE. EB900 Reference: 3GPP 45. i. the BTS determines which Radio Signalling Link (RSL) or LPDLR. During the switchover RSL message can be lost. LPDLM link selection management for LPDLR messages in case of failure of one LPDLM When an LPDLM fails. > CREATE LPDLM: NAME=BTSM:0/LPDLM:0.as LPDLM for O&M signaling between BSC and BTSM and .. the BTS performs a re-distribution of the LPDLRs over the LPDLM timeslots which are still available. this parameter determines the frequency band to which the CFHSY is applicable. The loadsharing among the created LPDLMs is based on a ‘preference’ which is defined per TRX/LPDLR. 0. object: range: LPDLM pcmb-no.as LPDLR for the call processing signalling communication (via Radio Signaling (RSL) messages) between BSC and a particular TRX. However.subslot). LPDLM signalling is always addressed with SAPI=62. ABISCH=0-1. These LPDLMs work in loadsharing mode. to avoid frequent LPDLR switchovers. the messages to be sent are distributed over all available LPDLMs. For further details. The associated BTS call processing subsystems (for Radio Link Control and Channel Control) are not informed about the loss of single RSL messages..e. When the failed LPDLM returns to service. is switched over which available LPDLM. object: range: CFHSY GSM850. The distinction between LPDLM messages and LPDLR radio signalling (RSL) messages is based on the LAPD layer 2 addressing scheme which uses the SAPI (Service Access Point Identifier) and TEI (Terminal Endpoint Identifier). back to the original (primary) LPDLR/LPDLM allocation. the BTS switches those LPDLRs. for each TRX the ‘preferred’ LPDLM indicates via which LPDLM (and thus via which physical Abis timelot) the associated LPDLR signalling messages shall be exchanged (see parameter LPDLMN in command CREATE TRX). The redistribution is done in such a way that the available LPDLRs are distributed over the available LPDLM links as evenly as possibly. please refer to the parameters TEI (in command CREATE BTSM) and LPDLMN (in command CREATE TRX). 1-24 (PCM24) subslot-no. BB900.008 GSM 04.SUBBAND=10.34 timeslot-no.e. for which the failed LPDLM was the “primary” one.08 Subordinate band. respectively. i. i.e.timeslot (. 0. DCS1800. 1-31 (PCM30) timeslot-no. . this happens at the earliest 30 seconds after the failed LPDLM has returned to service. PCS1900.e. 116 . Every LPDLM created for a particular BTSM also carries the LPDLR signalling information related to the TRXs subordinate to the BTSM and the associated BTSs.

LPDLS) that could be managed by one PPLD. If one of the PPXLs fails. starting from BR8. LPDLR. 117 . the parameter LAPDPOOL can only assume the value 0 or 1. NTWCARD=NTWSNAP or NTWSNAP_STLP). of the PPXL which serves the LAPD channel by default (i.1 (LAPD pool is assigned by the BSC automatically) Moreover. the parameter is only relevant for PPXL Meaning of LAPDPOOL for configuration with PPXL If PPXL boards are used (high capacity BSC HC-BSC. This means that in case of HC-BSC the parameter LAPDPOOL assumes the meaning of "primary PPXL". when both PPXL are in service). The BSC just registers the layer 2 connection setup by the BTSE and routes the messages adressed to a particluar TRX to the associated LPDLM timeslot. As. this parameter used to define the LAPDPOOL the LPDLM should be assigned to.e. both of them are in service and serve a number of LAPD channels. i. the module no. the corresponding counterpart has to be created in the BTSE using the command CREATE LAPDLE. the PPLD is no longer supported. LAPD pool.LAPDPOOL=0. for the switchover process there is no difference in the handling between LPDLRs associated to a BCCH-TRX or non-BCCH TRX.e. object: range: default: LPDLM 0. Note: For each LPDLM created in the BSC.0. In a HC-BSC two PPXL boards are available. A “ LAPD Pool “ was a logical instance which represented a group of LAPD channels (LPDLM. the remaining PPXL board immediately takes over the LAPD channels of the failed one.. After a failure of all LPDLMs the BSC decides which of the configured LPDLMs is used for the Abis Alignment Procedure.

0 provides a flexible and dynamic allocation of Abis TCHs. the dynamic Abis allocation adapts the Abis capacity to the required air interface capacity. to concatenate up to 5 16kbit/s Abis TCHs to one Um radio TCH. which is applied to both GPRS and CS calls. Considering this precondition. is no longer sufficient and efficient. New object SUBTSLB Due to the introduction of the feature ‘flexible Abis allocation’ in BR7.0 the fixed association of Um radio TCHs to a particular terrestrial Abis timeslot (and thus the ‘terrestrial channel’ parameter (TERTCH) in the CREATE CHAN command) was removed.0 on each terrestrial Abis timeslot must be created by an own CREATE SUBTSLB command. As the capacity of each Um radio TCH can vary during runtime. In correspondence with the service type. i. is restricted to interconnection or 16kbit/s Abis timeslots and full radio channels (full rate or dual rate). The following table shows the relationship between the number of 16kbit/s subslots on Abis and the coding schemes: Coding Scheme CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 Number of 16kbit/s subslots 1 2 2 2 1 2 2 2 2 3 4 5 5 As the table shows. however.e. the fixed allocation of Um radio TCHs to Abis TCHs. the BTS provides a switching matrix functionality which allows an individual throughconnection of Abis TCH resources towards Um radio TCH resources. From BR7. BR7. see parameters CSCH3CSH4SUP in command SET BSC and CREATE BTS) for GPRS require the concatenation of up to 5 Abis TCHs for only one used Um radio TCH.0. which represents a physical terrestrial 16 kbit/s channel on one of the Abis links towards a particular BTSM. Allocation principles of Um radio TCHs and Abis radio TCHs With the feature ‘flexible Abis allocation’ respectively ‘dynamic Abis allocation’ the Um radio TCHs of any BTS within the BTSM can be dynamically interconnected to any of the SUBTSLB assigned to the BTSM on a per-call base. The switching functionality. To define the terrestrial Abis timeslots.Creating the terrestrial Abis timelots for flexible Abis allocation: < Dynamic/Flexible Abis Allocation .Feature background and reason for introduction The high data rates enabled by the 8-PSK modulation for EDGE respectively EGPRS and the introduction of the additional high coding schemes (CS3 and CS4. it is not possible to interconnect any HR subslot on the Abis to any other HR 118 . To avoid a waste of Abis TCH resources. the BSC dynamically allocates the appropriate number of Abis TCHs to a particular call. which was used up to BR6. as it would require an Abis configuration according to the highest possible data rates. it is required. For this. a new database object called SUBTSLB (sub-timeslot on Abis) was introduced. depending on the coding schemes.

The amount of allocated 16 kbit/s Abis resources per radio timeslot depends on several factors. In other words. timeslot number etc.e.) which Um radio TCHs and Abis TCHs shall be interconnected by the BTS. Pooling Concept of Abis TCH resources Every 16kbit/s Abis timeslot is an object subordinate to an existing PCMB.e. a HR TCH pair on the Um is always connected to a HR TCH pair on the Abis. in case one Temporary Block Flow (TBF) applies the coding scheme MCS7. the relation of the SUBTSLB object to the BTSM is indirectly defined by the parameter ASSLAPD (see below). incoming handovers etc.HR CS speech . an additional Abis resource is dynamically allocated. Thus the Abis capacity is adapted.GPRS (CS3 and CS4) For GPRS and EGPRS several Abis TCHs resources may be used to carry their (n) concatenated PCU frames. the BTSs of the BTSM share the same Abis TCH 119 ..AMR FR CS speech . The relation of SUBTSLB and PCMB is implicitly defined in the object instance path name within the NAME attribute of the SUBTSLB object (see below). if the Link Adaptation algorithm leads to a lower coding scheme. The BSC sends the associated resource data (i. first of all the service type. e. any release and allocation of Abis capacity is not immediately executed. i. the BSC keeps track on the availability state (enabled. The number (n) of concatenated PCU frames depends on the coding scheme used for radio block transmission.e. MCS6.g.FR CS speech . Both the Um radio TCH resources and the Abis TCH resources are managed and controlled by the BSC.CS data .EFR CS speech .GPRS (CS1 and CS2 only) 1/2 x 16 kbit/s (= 8 kbit/s) . Required Abis capacity Service type 1 x 16 kbit/s . disabled) and usage state (idle.g..5) . a single Um radio TCH must be interconnected to Abis TCH resources. incoming handovers etc.) of the selected radio TCH(s) and Abis TCH(s) to the BTS in the CHANNEL ACTIVATION message which then performs the necessary throughconnection. All SUBTSLBs which are in this way created for (and thus assigned to) a particular BTSM make up the pool of Abis TCH resources that can be used to serve TCH requests (CS calls.PCMCON3 (see command CREATE BTSM). then 4 Abis resources get assigned.sublot on the radio interface. according to Link Adaptation. channel type . busy or active) of each Um radio TCH and each Abis TCH. In order to avoid continuous sequences of allocation and release. the two associated HR subslots a particular radio timeslot can only be interconnected to the two associated HR subslots of a particular Abis timeslot. e. MCS9. but follows after distinct timeout.) that are set up in the BTSs subordinate to the BTSM. In contrast. The relation of a BTSM to the PCMBs is defined by the parameters PCMCON0. If during the TBF lifetime the Link Adaptation algorithm leads to a higher coding scheme. (which message???) For example.EGPRS (MCS1 to MCS9) . In other words. depending on the service type. In case of a GPRS/EGPRS connection the BSC can adjust the Abis capacity according to Link Adaptation. superfluous Abis resources are released.AMR HR CS speech n x 16 kbit/s (n = 2. and it signals modifications with respect to the initial radio / Abis association to the BTS. The next table shows how. and determines for each TCH seizure request (call setup for CS and GPRS. i. GPRS calls.

Each Abis subpool belongs to a single PCM line (PCMB) and is associated to a specific LPDLM.e. The association of a particular SUBTSLB object to a BTSM and the LPDLM is implicitly defined within the path name included in the parameter ASSLAPD (see below). the complete Abis subpool) out of service. an ‘Abis subpool’ is defined by its simultaneous association to .. In more detail. failure safety of the Abis pool.An ‘Abis subpool’ consists of all SUBTSLB objects that are assigned to the same BTSM and the same LPDLM.e. While an ‘Abis pool’ is defined by its association to a specific BTSM only.An ‘Abis pool’ consists of all SUBTSLB objects that are assigned to the same BTSM. The following example configuration may illustrate a typical configuration:.resources pool which is also called ‘Abis pool’. This is possible because the LPDLR radio signalling for a particluar TRX/radio TCH can be performed via any of the remaing LPDLM timeslots. with different Abis subpools for different BTSMs distributed over different PCMBs). there is no whichever relation between the LPDLR call processing signalling within the LPDLM channel and the Abis TCHs in the associated Abis subpool. An ‘Abis pool’ consists of one or more ‘Abis subpools’. This relation of Abis TCH resources to a specific LPDLM channel (which always also carries the LPDLR signaling) is not call processing oriented. Typically the different Abis subpools that belong to the same BTSM are created on different PCMB lines to achieve a better availabilty resp. . The failure of PCM lines affects only Abis resources. while radio channels may continue to be assigned to new incoming calls. 120 . and the BSC immediately excludes them from the Abis pool and thus from the dynamic Abis allocation. if the LPDLM which was defined as the ‘preferred’ LPDLM for a particular TRX has changed its state to ‘disabled’ (for further details please refer to the parameter LPDLMN in command CREATE TRX). Summary: . (two BTSEs in multidrop. The association of a particular SUBTSLB object to a BTSM is implicitly defined within the path name included in the parameter ASSLAPD (see below). due to failure of the PCMB link. the pooling concept of the feature dynamic Abis allocation distinguishes so-called ‘Abis pools’ and ‘Abis subpools’. i. As soon as the ‘control LAPD’ is in service again the associated Abis subpool is put in service again and the associated abis TCH resources are available again for dynamic Abis allocation. whenever the ‘control LAPD’ is out of service (e. Instead.g.a specific PCMB and . In other words. the BSC considers the associated Abis resources (i. the purpose of the associated LPDLM (also called ‘control LAPD’) is to guarantee a suitable O&M supervision of the availability of the Abis TCH resources belonging to the Abis subpool.a specific BTSM ..a specfic LPDLM. as long as there is some available 16kbit/s Abis resource on the remaining PCMB lines.

Different Abis pools and Abis subpools must not overlap. Guaranteed minimum percentage of Abis pool TCHs per BTS To avoid a stop of call handling due to excessive traffic volume demands of other BTSs of the same BTSM and a resulting lack of Abis resources for a particular BTS. it must only be on the same PCMB) The following further notes on properties and relation of Abis pools and Abis subpools are important for consideration: .Abis subpools can be freely distributed over all PCMB lines that belong to a BTSM (see parameters PCMCON0. This parameter specifies the minimum percentage of ‘in service’ Abis subslots (i.PCMCON3). It is not necessary to guarantee that the subslots are adjacent.The Abis subslots allocated (interconnected) to a Um radio TCH may be distributed over different Abis subpools and consequently over different PCM lines.. Abis pools. the BSC considers the parameter GUARMABIS (see command command CREATE BTS [BASICS]). during TCH allocation.e. With the common pool concept any radio timeslot is dynamically associated to an appropriate number of Abis resources from the Abis pool. SUBTSLBs in state ‘unlocked/enabled’) of the Abis pool that shall in any case be kept available for allocation for this cell (BTS).BTSM:0 BTS:0 BTS:1 BTS:2 C O R E Abis pool BTSM:0 BTSM:0 subpool 1 L* Abis pool BTSM:1 BTSM:1 subpool 1 L* BTSM:0 subpool 2 L* B S C BTSM:1 Abis pool BTSM:1 BTS:0 BTS:1 BTS:2 C O R E BTSM:1 subpool 1 L* L* = associated LAPD (does not have to be directly adjacent to the pool TCHs.e. These different Abis subpools may belong to different BTSMs (i.Different Abis subpools can be defined on the same PCMB line. . In any case each subpool is associated to an own separate LPDLM channel. . 121 . . at least one subpool must be created per PCMB line. which is the most useful case!) as well as to the same BTSM.

The ASSLAPD parameter indicates the relation of a SUBTSLB object BTSM:n/LPDLM:m to a BTSM ‘Abis pool’ and an ‘Abis subpool’ in the following way: 1) All SUBTSLBs that contain the same BTSM no. As each LPDLM is an object subordinate a BTSM.e. in the ASSLAPD path name. the associated LPDLM.e.CREATE SUBTSLB: NAME=PCMB:0/TSLB:2/SUB Object path name. ASSLAPD= Associated LAPD. 122 . make up the ‘Abis pool’ of the BTSM. entered for this parameter consist of the object path name of an existing LPDLM. 2) All SUBTSLBs that contain the same BTSM no. these SUBTSLBs are the Abis TCH resources that can be dynamically used for CS and GPRS TCH requests for cells (BTSs) belonging to that BTSM. The values BTSM:0/LPDLM:0. in the ASSLAPD path name. i. i. these SUBTSLBs are that part of the BTSM Abis TCH resources which are created on the same PCMB and whose availability is supervised with the help of the same LPDLM. object: SUBTSLB format: object instance path name of the path name also identifies a BTSM (BTSM:n/LPDLM:m). For further details pleas refer to the explanations given in the command introdcution (see above). this parameter defines the so-called ‘associated LAPD channel’ of a particular SUBTSLB (Abis TCH). and the same LPDLM no. make up one ‘Abis subpool’ for the BTSM. TSLB:0.

Adaptiv Multirate (AMR) General background Adaptive Multi Rate (AMR) is a feature that introduces new speech versions in addition to the formerly used speech versions . good radio conditions poor radio conditions Channel Coding Channel Coding Speech Coding Speech Coding CREATE BTS [BASICS]: NAME=BTSM:0/BTS:0. which is a set of up to 4 AMR speech CODECs resp.Half Rate (GSM Half Rate Version 1). was changed to 0. AMRFRC1= RATE_01. For AMRFRC1 the value <NULL> is not allowed. the higher the available bandwidth (bitrate) for the speech coding and the smaller the bandwidth (bitrate) for channel coding and vice versa (‘Channel Coding’ is the term that represents the radio transmission error protection overhead.0 also GSM Speech Version 3 is introduced. RATE_07. The basic principle is: the better the radio interface quality. EFR. The logical group “[BASICS]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands .General hint concerning the SYSTEM INFORMATION messages: Some of the parameters in the following commands appear as information elements in the SYSTEM_INFORMATION_TypeX messages.. RATE_08 RATE_01 default: Active CODEC Set (ACS) Both the speech versions AMR FR and AMR HR consist of a socalled “Active CODEC Set (ACS)”.AMRFRC4 (for AMR FR) and AMRHRC1. then AMRFRC3 must be set to <NULL> and so on.Enhanced Full Rate (GSM Full Rate Version 2) and . If the ACS for AMR FR shall consist of only 3 AMR CODECs. which consists of the speech versions “AMR Full Rate” and “AMR Half Rate”. as at least one CODEC must be defined within an ACS. Due to the new object architecture (the BTS object is a subordinate object of the BTSM) the range for the BTSMno. AMR Full Rate Codec 1.23. RATE_04.AMRHRC4 (for AMR HR). speech coding schemes. all parameters of the previous ‘BTS packages’ were moved below the object BTS and appear in the DBAEM in the CREATE BTS command.0 The DBAEM does not group the command parameters into ‘packages’ anymore. this parameter defines the first AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in the BTS. > Attention: Since BR6... Please note that SYSTEM_INFORMATION_Type1 to _Type4 are sent on the BCCH if the MS is in idle mode and SYSTEM INFORMATION Type5 to _Type6 are sent on the SACCH if the MS is in busy mode. if it shall consist of only 2 CODECs. which are defined in each BTS by the parameters AMRFRC1.Full Rate (GSM Full Rate Version 1) .was changed to 0. the BTS-no. Instead. Object path name. while ‘Speech Coding’ represents the coding of the speech signal itself). HR) is that in case of AMR the used Speech Codec is not statically set for each assigned TCH but permanently adapted to the current radio conditions. RATE_03. RATE_02.. RATE_06. then AMRFRC4 must be set to <NULL>. 123 . object: range: BTS [BASICS] RATE_01. Creating a cell with definition of global parameters: < With this command all cell specific attributes not related to Common Control Channels are set.199. RATE_05. The differences between AMR and the older GSM Speech Versions (FR. Since BR6.

which are administrable by the parameters AMRFRTH12.90 kbit/s RATE_04: 6.2 kbit/s RATE_08: 12. the same principle applies in case of inter-cell handover (where the MS receives the AMR parameters in the HANDOVER COMMAND).70 kbit/s RATE_05: 7. The AMR link adaptation downlink is controlled by the MS and is based on the C/I (Carrier to Interference) thresholds. each change of the AMR CODEC means a change of the type of TRAU frame that is to be used between the BTS and the TRAU. Link adaptation Signalling The change of the CODEC is signalled in-band by 2 specific bits within the Um speech frames (allowing the adressing of 4 CODECs in the ACS).70 kbit/s RATE_05: 7.to the BTS in the CHANNEL ACTIVATION message and .40 kbit/s RATE_06: 7. Moreover. the MS (for the downlink) and the BTS (for the uplink) intiate the selection of a suitable AMR CODEC from the Active CODEC Set (ACS).2 kbit/s For AMRHRC1. the parameters defining the AMR CODECs used within the ACS and the thresholds and hysteresis values for the downlink AMR link adaptation) . Of course.AMRFRC4 the following speech coding bit rates can be set: RATE_01: 4.15 kbit/s RATE_03: 5.AMRHRC4 the following speech coding bit rates can be set: RATE_01: 4. The signalling is based on the following message types: CODEC MODE REQUEST (CMR) CMRs are exclusively sent from MS to BTS.AMRHRTH34 (for AMR HR). This dynamic change of the AMR CODEC mode depending on the radio interface quality is called “AMR Link Adaptation” or “AMR CODEC Mode Adaptaion”. The change of the TRAU frame is also signaled ‘in-band’.e. the following rule must be followed: RATEAMRFRC4 > RATEAMRFRC3 > RATEAMRFRC2 > RATEAMRFRC1 AMR link Adaptation When an AMR call has been set up.to the MS in the ASSIGNMENT COMMAND message.75 kbit/s RATE_02: 5.40 kbit/s (RATE_04 and RATE_05 only for BTSplus) In any case...95 kbit/s RATE_07: 10. as each AMR CODEC has its own TRAU frame format. within the AMR TRAU frames exchanged between the BTS and the TRAU. Depending on the results of these quality measurements.e. both the BTS and the MS continuously evaluate the radio interface quality: the MS measures the downlink quality in the same way as it does for the regular measurement reporting and the BTS derives quality values from the uplink BER measurements. the CMR is continuously sent from the MS to the BTS even if no change of the current CODEC is required.AMRFRTH34 (for AMR FR) and AMRHRTH12. i. the BTS requests the corresponding downlink CODEC via a CMC from the TRAU. The BSC sends the AMR parameters that are to be used for a particular AMR call (i.15 kbit/s RATE_03: 5. If the CMR request is correctly received by the BTS.. The prupose of a CMR is to request a CODEC that shall be used for the downlink direction.75 kbit/s RATE_02: 5.90 kbit/s RATE_04: 6. If DTX is not used.For AMRFRC1. The AMR link adaptation uplink is controlled by the BTS and is based on C/I thresholds that are hardcoded and not administrable (please refer to the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document) but which can be influenced by the tuning parameter AMRLKAT (see below). 124 ..

basically depends on the mobile’s speech version preference.CODEC MODE COMMAND (CMC) The CMC is sent from the BTS to the TRAU and the MS. AMRHRIC determine the initial AMR CODEC. but their acronym is extended by the prefix 125 . the BTS only instructs the TRAU to change the current downlink CODEC mode. which is indicated in the ASSIGNMENT REQUEST message (and which was normally originally indicated by the MS in the SETUP message (for MOC) or the CALL CONFIRMED message (for MTC)). CMCs for the uplink direction are sent from BTS to the MS in the downlink bursts in order to indicate which CODEC the MS shall use for the uplink speech frames. The MS sets the CMI in the uplink speech frames as requested by the CMC received from the BTS.AMRFRC4 and AMRHRC1. the initial CODECs AMRFRIC and AMRHRIC as well as the link adaptation thresholds for the downlink AMRFRTH12. The CMC is sent to the TRAU after an averaging process in the BTS (see parameter AMRACMRDL in command SET HAND [BASICS]): The size of the associated ‘averaging window’ for this process is defined in CODEC Mode Requests (CMRs).e. the BSC can override the MS preference due to the feature “Cell Load Dependent Activation of Half Rate” (see parameter EHRACTAMR in command SET BTS [BASICS]) or “Abis Load Dependent Activation of Half Rate” (see parameter ABISHRACTTHR). CODEC MODE INDICATION (CMI) The CMIs are sent by MS. by the CMC the BTS commands which CODEC shall be used by TRAU and MS and by the CMI the MS. if a sufficient number of corresponding CMRs received from the MS have confirmed the request to change the CODEC. The purpose of the CMI is to indicate which type of CODEC is currently used by the sending side.AMRHRC4. The BTS inserts CMIs into downlink bursts according to the CODEC signaled from the TRAU and into uplink TRAU frames according to the CODEC signaled by the MS. Interaction of AMR link adaptation and frequency hopping The parameters for the ACS AMRFRC1.. When the decision for AMR FR or AMR HR was made. the initial CODEC is then immediately adapted by the MS and BTS depending on the current radio conditions in the scope of the AMR link adaptation. or TRAU frame. i. Like for all non-AMR calls. Of course. the parameters AMRFRIC resp. CMCs for the downlink direction are sent from BTS to the TRAU within uplink TRAU frames to request the TRAU frame type in correspondence with the CODEC required by the CMR from the AMR MS. TRAU and BTS.AMRHRTH34 are valid for all calls with ‘frequency hopping inactive’. CMIs are sent within the TRAU frames as well as in the UL and DL speech frames. Its purpose is to instruct the TRAU and MS to use a specifc CODEC. TRAU and BTS indicate which CODEC they currently use to allow a correct decoding on the receive side. as the same CODEC must be used to correctly decode the received speech signal. How is the initial AMR CODEC determined during call setup? Whether an AMR FR or an AMR HR TCH is to be assigned during call setup. The TRAU sets the CMI for the downlink TRAU frames as requested by the CMC from the BTS. Separate parameters and thresholds are used for calls with ‘frequency hopping active’... the AMR CODEC that shall be used in the beginning of the call (this information is also included in the ASSIGNMENT COMMAND and CHANNEL ACTIVATION messages)..AMRFRTH34 and AMRHRTH12. These parameters have exactly the same acronyms like the parameters listed above. respectively. i.e. Summary: By the CMR the MS indicates which CODEC it desires.

that allow a switchover from an AMR HR TCH to an AMR FR TCH and vice versa based on quality and load criteria. In this context it is not only relevant. the ‘frequency hopping active’ equivalent to parameter AMRFRC1 has the acronym FHAMRFRC1. Handover and Power Control for AMR Calls The Handover and Power Control Decision for AMR calls is basically the same as for any other speech call. . The BTS uses these ‘FH’-AMR parameters for the downlink CODEC mode adaptation if frequency hopping is active for the call (for the uplink CODEC mode adaptation there is no difference between hopping active or deactivated). The FHSY parameters for AMR are only considered for a particular AMR call if hopping is currently active for a particular call. the decision whether an AMR call is set up as AMR FR or AMR HR call is either based on the speech version preference indicated in the ASSIGNMENT REQUEST or on the BSC decision (Cell load dependent activation of HR). . the involved TRAU must be equipped with TRAC V5 or TRAC V7. for example. the associated A-interface resources must be created with the appropriate channel pool type (see parameters DEFPOOLTYP in command CREATE PCMA and POOLTYP in command SET TSLA). This means that.‘FH’. please consider that for AMR calls special handover and power control thresholds may apply. This field element is included in the Information Element “Old BSS to new BSS Information” which is included in the HANDOVER REQUIRED message and which the MSC transparently passes to the target BSC in the HANDOVER REQUEST message. in case of baseband hopping with TRX failure). please refer to the parameters HOLTHQAMRDL (SET HAND [BASICS]) and LOWTQAMRDL (SET PWRC). Moreover. 126 . For further details about AMR compression and AMR decompression handover please refer to parameter EADVCMPDCMHO in command SET HAND [BASICS]. even if the database flag for frequency hopping (see parameter HOPP in command) indicates that hopping is enabled. if they have been corresponsingly set in the handover and power control service group settings (see parameters SGxxHOPAR in command SET HAND[BASICS] and SGxxPCPAR in command SET PWRC). Exception: The Handover decision algorithm as well as the Power Control Decision algorithm uses special C/I thresholds for the Handover or Power Control decision due to quality. Notes: .To support AMR.In the MSC and the BSC.During Inter-BSC handover.g. as frequency hopping can be temporarily deactivated in the BTS (e. For further details. Special intracell handovers are implemented for AMR calls. Neither TRAC V1 nor TRAC V3 support AMR. the originating BSC informs the target BSC about the currently used CODEC by the field element “MultiRate configuration Information”. AMR Compression Handover / AMR Decompression Handover As mentioned before. whether frequency hopping is configured or not.

AMRFC3). RATE_04.40 kbit/s RATE_06: 7.2 kbit/s RATE_08: 12. object: range: BTS [BASICS] RATE_01. RATE_02.15 kbit/s RATE_03: 5. this parameter defines the fourth AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in the BTS.15 kbit/s RATE_03: 5. RATE_03. RATE_08 <NULL> RATE_08 default: AMR Full Rate Codec 2. RATE_01: 4. AMR Full Rate Codec 4. For further details please refer to the descriptions provided for the parameter AMRFRC1. RATE_04.75 kbit/s RATE_02: 5. RATE_06. RATE_06.70 kbit/s RATE_05: 7.40 kbit/s RATE_06: 7. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. AMR Full Rate Codec 3. the following rule must be followed: RATEAMRFRC4 > RATEAMRFRC3 > RATEAMRFRC2 > RATEAMRFRC1 Note: An equivalent parameter is available (see below. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. In any case.90 kbit/s RATE_04: 6. RATE_07. RATE_05. 127 .2 kbit/s If AMRFRC2 is set to <NULL>.2 kbit/s RATE_08: 12. RATE_08 <NULL> RATE_06 default: AMRFRC4= RATE_08.15 kbit/s RATE_03: 5.70 kbit/s RATE_05: 7. RATE_02.2 kbit/s RATE_08: 12. RATE_07. For further details please refer to the descriptions provided for the parameter AMRFRC1. RATE_03.75 kbit/s RATE_02: 5. RATE_02.. RATE_05. In any case.2 kbit/s If AMRFRC4 is set to <NULL>.75 kbit/s RATE_02: 5.95 kbit/s RATE_07: 10.AMRFRC2= RATE_03. RATE_05.95 kbit/s RATE_07: 10. RATE_06. this parameter defines the second AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in the BTS. object: range: BTS [BASICS] RATE_01. this parameter defines the third AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in the BTS. RATE_08.2 kbit/s If AMRFRC3 is set to <NULL>. the following rule must be followed: RATEAMRFRC4 > RATEAMRFRC3 > RATEAMRFRC2 > RATEAMRFRC1 Note: An equivalent parameter is available (see below.. the ACS for AMR FR only consists of maximally two AMR CODECs (defined by AMRFRC1and AMRFC2). RATE_04. RATE_01: 4.70 kbit/s RATE_05: 7.90 kbit/s RATE_04: 6. the ACS for AMR FR only consists of maximally three AMR CODECs (defined by AMRFRC1. RATE_03. In any case. the following rule must be followed: RATEAMRFRC4 > RATEAMRFRC3 > RATEAMRFRC2 > RATEAMRFRC1 Note: An equivalent parameter is available (see below. RATE_01: 4. the ACS for AMR FR consists of only one CODEC (defined by AMRFRC1). RATE_07. object: range: BTS [BASICS] RATE_01.90 kbit/s RATE_04: 6.40 kbit/s RATE_06: 7. <NULL> RATE_03 default: AMRFRC3= RATE_06.95 kbit/s RATE_07: 10. For further details please refer to the descriptions provided for the parameter AMRFRC1.

.0 dB] AMR Full Rate Initial Codec. If the value START_MODE_FR is entered. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.5dB] threshold: 7 [3.AMRFRIC= START_MODE_FR.If the ACS consists of 1 CODEC.e. . Example: If AMRFRIC=CODEC_MODE_01.5dB hysteresis: 0.15 [0.If the ACS consists of 4 CODECs.. the one with the lower speech coding bitrate) shall be used. then the CODEC defined in AMRFRC1 will be used as initial AMR FR CODEC after FR TCH assignment. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document).5dB] hysteresis: 0. then this CODEC shall be used.Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation. the following rule must be fulfilled thresholdAMRFRTH12 + hysteresisAMRFRTH12 ≤ thresholdAMRFRTH23 + hysteresisAMRFRTH23 ≤ thresholdAMRFRTH34 + hysteresisAMRFRTH34 Notes: .7. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRFRC1 to AMRFRC2 and vice versa. .31. then the one with the most robust channel coding (i. Note: An equivalent parameter is available (see below. The values CODEC_MODE_0x represent the created AMR FR CODECs (AMRFRCx) of the ACS. then the one with the second most robust channel coding shall be used.5dB threshold: 0. object: range: BTS [BASICS] START_MODE_FR CODEC_MODE_01 CODEC_MODE_02 CODEC_MODE_03 CODEC_MODE_04 START_MODE_FR default: AMRFRTH12=7-4. The entered values are applied as follows: a) The upward transition from AMRFRC1 to AMRFRC2 is initiated when C/I > thresholdAMRFRTH12 + hysteresisAMRFRTH12 b) The downward transition from AMRFRC2 to AMRFRC1 is initiated when C/I < thresholdAMRFRTH12 Thus a) can be regarded as the ‘upper threshold’. this parameter defines which AMR FR CODEC of the created AMR FR ACS shall be used first after FR TCH assignment.. .. 128 .An equivalent parameter is available (see below. In any case.5 dB] hysteresis: 4 [2. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0. the initial CODEC is selected as defined by the GSM standard: . AMR Full Rate Thresholds 12.63 [0. The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).If the ACS consists of 2 or 3 CODECs.

The entered values are applied as follows: a) The upward transition from AMRFRC3 to AMRFRC4 is initiated when C/I > thresholdAMRFRTH34 + hysteresisAMRFRTH34 b) The downward transition from AMRFRC2 to AMRFRC1 is initiated when C/I < thresholdAMRFRTH34 Thus a) can be regarded as the ‘upper threshold’.0 dB] hysteresis: 4 [2. The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).15 [0.31.Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation. In any case.5dB] threshold: 12 [6. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document).15 [0. .5dB] hysteresis: 0.31. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRFRC3 to AMRFRC4 and vice versa.5dB hysteresis: 0.63 [0.. In any case..5 dB] hysteresis: 4 [2..5dB] hysteresis: 0.0 dB] AMRFRTH34=23-4..63 [0.0 dB] AMR Full Rate Thresholds 23. the following rule must be fulfilled thresholdAMRFRTH12 + hysteresisAMRFRTH12 ≤ thresholdAMRFRTH23 + hysteresisAMRFRTH23 ≤ thresholdAMRFRTH34 + hysteresisAMRFRTH34 Notes: . parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. The entered values are applied as follows: a) The upward transition from AMRFRC2 to AMRFRC3 is initiated when C/I > thresholdAMRFRTH23 + hysteresisAMRFRTH23 b) The downward transition from AMRFRC3 to AMRFRC2 is initiated when C/I < thresholdAMRFRTH23 Thus a) can be regarded as the ‘upper threshold’... object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0.An equivalent parameter is available (see below...7.7. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document).5dB hysteresis: 0. The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).5dB threshold: 0.AMRFRTH23=12-4. .5dB] threshold: 23 [12. this parameter defines the C/I threshold and the associated hysteresis for the AMR link adaptation transition from AMRFRC2 to AMRFRC3 and vice versa.An equivalent parameter is available (see below. 129 . object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0. AMR Full Rate Thresholds 34.5dB threshold: 0.Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation. the following rule must be fulfilled thresholdAMRFRTH12 + hysteresisAMRFRTH12 ≤ thresholdAMRFRTH23 + hysteresisAMRFRTH23 ≤ thresholdAMRFRTH34 + hysteresisAMRFRTH34 Notes: . parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.

the following rule must be followed: RATEAMRHRC4 > RATEAMRHRC3 > RATEAMRHRC2 > RATEAMRHRC1 Note: An equivalent parameter is available (see below. RATE_03. RATE_01: 4.40 kbit/s (RATE_04 and RATE_05 only for BTSplus) If the ACS for AMR HR shall consist of only 3 AMR CODECs. the ACS for AMR HR only consists of only one CODEC (defined by AMRHRC1). the following rule must be followed: RATEAMRHRC4 > RATEAMRHRC3 > RATEAMRHRC2 > RATEAMRHRC1 Note: An equivalent parameter is available (see below. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. then AMRHRC4 must be set to <NULL>. RATE_02. <NULL> RATE_02 AMRHRC3= RATE_03. RATE_04.75 kbit/s RATE_02: 5. For further general details please refer to the descriptions provided for the parameter AMRFRC1. In any case. RATE_05 RATE_01 AMRHRC2= RATE_02.75 kbit/s RATE_02: 5. In any case.AMRHRC2). For further general details please refer to the descriptions provided for the parameter AMRFRC1.AMRHRC1= RATE_01. In any case.40 kbit/s (RATE_04 and RATE_05 only for BTSplus) If AMRHRC2 is set to <NULL>. RATE_03. RATE_04 RATE_05. object: range: BTS [BASICS] RATE_01. as at least one CODEC must be defined within an ACS..15 kbit/s RATE_03: 5. this parameter defines the first AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in the BTS. 130 . AMR Half Rate Codec 3. object: range: default: BTS [BASICS] RATE_01. object: range: default: BTS [BASICS] RATE_01.90 kbit/s RATE_04: 6. RATE_02. the following rule must be followed: RATEAMRHRC4 > RATEAMRHRC3 > RATEAMRHRC2 > RATEAMRHRC1 Note: An equivalent parameter is available (see below.90 kbit/s RATE_04: 6. For AMRHRC1 the value <NULL> is not allowed. then AMRHRC3 must be set to <NULL> and so on. RATE_02. For further general details please refer to the descriptions provided for the parameter AMRFRC1. this parameter defines the third AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in the BTS.15 kbit/s RATE_03: 5. RATE_04 RATE_05. RATE_03.90 kbit/s RATE_04: 6.40 kbit/s (RATE_04 and RATE_05 only for BTSplus) If AMRHRC3 is set to <NULL>. the ACS for AMR HR only consists of maximally two AMR CODECs (defined by AMRHRC1. this parameter defines the second AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in the BTS. <NULL>default: RATE_03 AMR Half Rate Codec 1.75 kbit/s RATE_02: 5.70 kbit/s RATE_05: 7. RATE_01: 4.70 kbit/s RATE_05: 7. AMR Half Rate Codec 2. if it shall consist of only 2 CODECs.15 kbit/s RATE_03: 5. RATE_01: 4. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.70 kbit/s RATE_05: 7.

If the ACS consists of 1 CODEC. object: range: BTS [BASICS] START_MODE_HR CODEC_MODE_01 CODEC_MODE_02 CODEC_MODE_03 CODEC_MODE_04 START_MODE_HR default: AMRHRTH12=19-4.. In any case. the following rule must be followed: RATEAMRHRC4 > RATEAMRHRC3 > RATEAMRHRC2 > RATEAMRHRC1 Note: An equivalent parameter is available (see below.40 kbit/s (RATE_04 and RATE_05 only for BTSplus) If AMRHRC4 is set to <NULL>.AMRHRC3).15 [0. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.5dB] threshold: 19 [9. AMR Half Rate Initial Codec. Notes: . . object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0. For further general details please refer to the descriptions provided for the parameter AMRFRC1.If the ACS consists of 4 CODECs. <NULL>default: RATE_04 AMRHRIC= START_MODE_HR..15 kbit/s RATE_03: 5. The entered values are applied as follows: a) The upward transition from AMRHRC1 to AMRHRC2 is initiated when C/I > thresholdAMRHRTH12 + hysteresisAMRHRTH12 b) The downward transition from AMRHRC2 to AMRHRC1 is initiated when C/I < thresholdAMRHRTH12 Thus a) can be regarded as the ‘upper threshold’. the following rule must be fulfilled thresholdAMRHRTH12 + hysteresisAMRHRTH12 ≤ thresholdAMRHRTH23 + hysteresisAMRHRTH23 ≤ thresholdAMRHRTH34 + hysteresisAMRHRTH34 Notes: . the one with the lower speech coding bitrate) shall be used. then this CODEC shall be used. AMR Half Rate Thresholds 12. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of 131 .If the ACS consists of 2 or 3 CODECs. If the value START_MODE_HR is entered. the initial CODEC is selected as defined by the GSM standard: . . RATE_02..63 [0.5 dB] hysteresis: 4 [2. this parameter defines the fourth AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in the BTS.70 kbit/s RATE_05: 7. Example: If AMRHRIC=CODEC_MODE_01.31. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC1 to AMRHRC2 and vice versa..0 dB] AMR Half Rate Codec 4. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.e.5dB threshold: 0.. then the CODEC defined in AMRHRC1 will be used as initial AMR HR CODEC after AMR HR TCH assignment. object: range: BTS [BASICS] RATE_01. In any case. RATE_01: 4.7.90 kbit/s RATE_04: 6. The values CODEC_MODE_0x represent the created AMR HR CODECs (AMRHRCx) of the ACS.5dB] hysteresis: 0.An equivalent parameter is available (see below. the ACS for AMR HR only consists of maximally three AMR CODECs (defined by AMRHRC1. then the one with the second most robust channel coding shall be used. RATE_04 RATE_05.5dB hysteresis: 0.75 kbit/s RATE_02: 5.AMRHRC4= RATE_04. then the one with the most robust channel coding (i. RATE_03.An equivalent parameter is available (see below. this parameter defines which AMR HR CODEC of the created AMR HR ACS shall be used first after HR TCH assignment. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document).

the following rule must be fulfilled thresholdAMRHRTH12 + hysteresisAMRHRTH12 > thresholdAMRHRTH23 + hysteresisAMRHRTH23 ≤ thresholdAMRHRTH34 + hysteresisAMRHRTH34 Notes: .63 [0. AMR Half Rate Thresholds 34. In any case. AMR Half Rate Thresholds 23. .0 dB] hysteresis: 4 [2. .5dB hysteresis: 0. 132 . object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0.0 dB] AMRHRTH34=30-4. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC3 to AMRHRC4 and vice versa. The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).5dB] hysteresis: 0. the following rule must be fulfilled thresholdAMRHRTH12 + hysteresisAMRHRTH12 ≤ thresholdAMRHRTH23 + hysteresisAMRHRTH23 ≤ thresholdAMRHRTH34 + hysteresisAMRHRTH34Notes: .Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation.0 dB] (BTS+) <NULL> (BTS1) hysteresis: 4 [2.5dB threshold: 0. The entered values are applied as follows: a) The upward transition from AMRHRC2 to AMRHRC3 is initiated when C/I > thresholdAMRHRTH23 + hysteresisAMRHRTH23 b) The downward transition from AMRHRC3 to AMRHRC2 is initiated when C/I < thresholdAMRHRTH23 Thus a) can be regarded as the ‘upper threshold’.. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.0 dB] active frequency hopping. parameter with the same name but the prefix ‘FH’) which eclipses this one in case of active frequency hopping.5dB] threshold: 30 [15. .AMRHRTH23=24-4.7.5dB hysteresis: 0.31. object: format: unit: range: default: BTS [BASICS] threshold-hysteresis threshold: 0.. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC2 to AMRHRC3 and vice versa.31.5dB] threshold: 24 [12.63 [0.An equivalent parameter is available (see below.7..An equivalent parameter is available (see below. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document).. The entered values are applied as follows: a) The upward transition from AMRHRC3 to AMRHRC4 is initiated when C/I > thresholdAMRHRTH34 + hysteresisAMRHRTH34 b) The downward transition from AMRHRC4 to AMRHRC3 is initiated when C/I < thresholdAMRHRTH34 Thus a) can be regarded as the ‘upper threshold’. In any case..15 [0. while b) can be regarded as the ‘lower threshold’ for downlink AMR link adaptation (please see also the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document). The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).5dB] hysteresis: 0.15 [0.. The corresponding uplink thresholds are not administrable (see parameter AMRLKAT).5dB threshold: 0...Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation.Please be aware that this parameter only refers to the AMR downlink CODEC mode adaptation.

e. A value lower than the default has the opposite effect. can set the hopping period. FOURTH. SECOND. Antenna hopping mode. 200 = +10dB 100 [0dB] ANTHOPMOD = <NULL>. two or four frames. by means of the O&M parameter ANTHOPP. this parameter is only relevant if the feature ‘Antenna Hopping’ is enabled (EANTHOP=TRUE. <NULL> <NULL> <NULL> BCCHFREQ=10. It tunes the transition between CODEC modes determined by internal thresholds. However. specifies the Um channel no. (e. The default value is the optimum setting and normally requires no modification. The number of antenna changes depends on the number of used antennas and service (4-4-5 used for EDGE). see below) and defines whether Antenna Hopping is applied for the BCCH TRX or not. All possible transitions between modes are generally shifted by the same amount.08 GSM 05. The operator. BCCHFREQ 10 = C10) of that carrier which contains the FCH. BCCH frequency.. where 0 = -10dB. object: BTS [BASICS] range: 0. which means that each 3rd hopping step the period is extended from 4 to 5 frames (suitable especially for GPRS/EGPRS). SEQ_445.1dB. Antenna hopping period. Antenna Hopping is enabled either . Additionally there is the mode 4-4-5. to account for a limited range of the underlying measurements.g. A value higher than the default shifts the transition towards higher carrier-to-interferer or signal-to-noise ratios. Antenna Hopping is performed every one. this parameter is only relevant if the feature ‘Antenna Hopping’ is enabled (EANTHOP=TRUE. BCCH and CCCH. For further details please refer to the section “AMR Link Adaptation Thresholds Uplink” in the Appendix of this document. The feature "not-ramping for BCCH" is deactivated if ANTHOPMOD=ALLTRX is set. 100 = 0dB.. object: unit: range: default: BTS [BASICS] 0. he can decide how many frames are transmitted over each antenna before the next antenna is used to send the frames.1dB 0. The step size is 0.for all CUs including the BCCH-TRX CU (value ALLTRX) or .for all CUs except for the BCCH-TRX CU (value NOBCCHTRX). see below) and defines the antenna hopping period.08 AMR link adaptation tuning. the BTS algorithm calculates the Antenna Hopping sequence individually for each CU-POOL. After having grouped the CUs in pools. Adaptation of AMR Half Rate and AMR Full Rate is affected simultaneously. <NULL> <NULL> ANTHOPP = <NULL> object: range: default: BTS [BASICS] ALL. SCH. this parameter is used by the AMR Uplink Codec Mode Adaptation in the BTS (Please note that this parameter is the only one which refers to the uplink CODEC mode adaptation! All other administrable parameters refer to the downlink CODEC mode adaptation and have no relation to this parameter!). i. shifts of transitions near the upper range limit tend to saturate when shifted closer to the limit. NOBCCHTRX.AMRLKAT=100.1023 Reference: GSM 04. 133 . object: range: default: BTS [BASICS] ALLTRX.200.

.885 SYSID=GSM850DCS: 128.BCC. Further frequencies used in the cell are set with the remaining parameters CALLF02.124 SYSID=F2ONLY900: 0.g. care needs to be taken to ensure that the same NCC is not used in adjacent PLMNs which may use the same BCCH carrier frequencies in neighbouring areas.7.124. The BCC is used by the MS to correctly decode the BCCH. as an integer value.7 BCC: 0.BSIC=7-7... in the ASSIGNMENT COMMAND) in the IE ‘Cell Channel Description’.CALLF63 object: BTS [BASICS] Base Station Identity Code is sent downlink in the SCH. object: range: BTS [BASICS] NCC: 0. <NULL> Reference: <NULL> CALLF01=60. In other words: From the BCC in the SCH the MS knows the TSC of the BCCH it has to select.. For each frequency an own parameter is available .08 GSM 04.03 GSM 03. depends on the used frequency band: SYSID=BB900: 1. 512... Cell allocation frequency 1. The ‘Cell Channel Description’ is a bit map (different formats are possible). If frequency hopping is enabled the ‘Cell Channel Description’ IE is needed by the MS to decode the info in the IE ‘Mobile Allocation’ which specifies the frequencies used in the frequency hopping sequence.02 GSM 12.251..124. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 1) or/and on the main DCCH (contained e. From the point of view of network planning...810 Notes: .The SYSTEM INFORMATION TYPE 1 is only sent if frequency hopping is used. this parameter is relevant if the feature ‘inter Site Synchronization’ (ISS) is used and indicates.1023 each field Reference: GSM 04.. From the NCC the MS determines which cells are allowed for handover (see also parameter PLMNP). Within one PLMN more than one NCC may be allowed. 975. Burst number offset.DCS etc. The format is NCC . in which for every frequency of the used band (GSM. If the bit position is '1' then the frequency represented by this bit position is included in the 'cell allocation'. object: BTS [BASICS] range: 0. BCC= Base Station Colour Code.251 SYSID=GSM850PCS: 128. Which frequency numbers are allowed. Cell allocation frequencies 2 to 63. this parameter defines the first nonBCCH radio frequency allocated to the cell.. The BCC must correspond to the Training Sequence Code (TSC) assigned to the BCCH of that cell.CALLF63... 975. they were summarized here in one table line. i.. these parameters define all the remaining non-BCCH radio frequencies used in the cell (see CALLF01).885 SYSID=GSM850: 128. The BCC is selected by default as TSC for the BCCH when it is created (see also CREATE CHAN). NCC= Network Colour Code.) an own bit position is provided.02 BURNOFFS=<NULL>..08 GSM 05.251. For further details about ISS and the meaning of this parameter please refer to parameter EINTSITSYN (see command CREATE BTSM).08 GSM 05..20 CALLF02..1023 SYSID=DCS1800: 512.974 SYSID=PCS1900: 512.810 SYSID=GSMR: 955. 512.. only cells with a ‘permitted’ NCC may be included in the MEASUREMENT REPORTS. 134 .7 Reference: GSM 03.to save space. object: BTS [BASICS] range: 0. the burst number offset of the BTS..1023 SYSID=EXT900: 0.e.

.008 GSM 03. Within these messages MCC-MNC-LAC make up the IE ‘Location Area Identification’ and CI corresponds to the IE ‘Cell Identity’. that the MS is currently not or no longer booked in to a cells and starts a search for a suitable cell 'from scratch'... after switching on the MS or when the MS has lost the connection to the network (lossloss of coverage).999" MNC: "0. In this case the cell priority defined by CBQ is NOT considered by the MS! Cell selection means. but not for ‘cell reselection’.. As possible target cells.999" (PCS1900) MNC: "0. Cell Global Identity. This parameter only has to be set if CRESPARI is set to ‘1’. This happens e. 135 . The format is "MCC"-"MNC"-LAC-CI. This parameter (CELL_BAR_QUALIFY) is sent in the IE ‘SI 4 Rest Octets’ on the BCCH (SYSTEM INFORMATION TYPE 4). C2) to select a different neighbour cell because this cell offers better DL RXLEV conditions. A suitable cell with low priority is only selected if no suitable cell of normal priority can be found. only neighbour cells are considered that are included in the 'Neighbour Cell Description' which is broadcast in the SYSTEM INFORMATION TYPE 2.03 GSM 04. this digit string unambiguously identifies a cell within the worldwide GSM system.99" (all others) LAC: 0.08 Cell bar qualify. Only in this case the MS considers the cell priority defined by CBQ for the selection of the cell.22 CELLGLID="262"-"02"-10101. object: range: BTS [BASICS] 0= normal priority 1=low priority default: 0 Reference: 3GPP 45. is used to assign a priority to a cell which is to be considered by the MS during the cell selection decision.. Cell Reselection means that the MS is camping on a cell and decides (on the basis of the level criterion C1 resp.65535 CI: 0. Attention: CBQ is only considered for ‘cell selection’. SYSTEM INFORMATION TYPE 4 does not contain the CI but only the LAI. object: range: BTS [BASICS] MCC: "0.CBQ=0. MCC= Mobile Country Code (identifies the country) MNC= Mobile Network Code (identifies the network within the country) LAC = Location Area Code (identifies the location area within the network) CI = Cell Identity (identifies the cell within the location area) This parameter is sent downlink on the BCCH (SYSTEM INFORMATION TYPE 3 or 4) or on the SACCH (SYSTEM INFORMATION TYPE 6).g.65535 Reference: GSM 03.

7 2 3GPP 45.0)) where A = <receive level average> . The MS calculates the path loss criterion for the serving and the nonserving cell at least every 5 seconds (the MS derives the necessary calculation parameters from the BCCHs of the serving and the neighbour cells). Note: The C1 criterion can be replaced by the C2 criterion (see parameter CRESPARI) if the appropriate parameters are provided via the BCCH.22 GSM 12.0)= 0 if MSTXPMAXCH < P For RXLEVAMI see corresponding parameter in this command. C1 = (A . The term Max(B.P = MSTXPMAXCH .P if MSTXPMAXCH > P Max (B.Max(B.P P = Maximum RF output power of the MS (see table under parameter MSTXPMAXDCS in command SET BTS [BASICS]).CELLRESH=2. 136 . If C1 of the non-serving cell is higher than C1 of the serving cell for a period of 5 s then the MS performs a cell reselection. This mechanism is used to avoid unnecessary location update procedures.008 GSM 04. added to RXLEVAMI. Exception: If the current cell and the new cell belong to different location areas the new cell shall only be selected if the path loss criterion C1 on the new cell exceeds C1 on the old serving cell by at least CELLRESH for a period of 5 seconds. the higher the minimum RXLEV for access must be.0).0) is applied to ensure a sufficient uplink RXLEV even for MS with low transmit power level. The calculation result determines the priority of these cells within the list of the six strongest neighbour cells which is dynamically managed in the MS in idle mode. The term Max(B. indicates the value of the receiver RF power level hysteresis required for cell reselection (MS in idle mode) on the basis of the path loss criterion C1. object: unit: range: default: Reference: BTS [BASICS] 2dB 0.RXLEVAMI B = MS_TXPWR_MAX_CCH .08 GSM 03. MSTXPMAXCH see SET BTS [CCCH].RXLEV_ACCESS_MIN = RLA_P . ensures that the transmit power capability is considered in addition to the minimum receive level defined by RXLEVAMI: the lower the maximum transmit power of the MS. Max (B. The value of CELLRESH is sent on the BCCH (SYSTEM INFORMATION Type3 and Type 4) in the IE ‘Cell Selection Parameters’ and in the SET SYSTEM INFORMATION 10 in the IE ‘Differential Cell Parameters’..0)= MSTXPMAXCH . The path loss criterion is satisfied if C1 > 0 (If C1 has been < 0 for a period of 5 s the path to the cell is regarded as lost).20 Cell reselect hysteresis.

this parameter determines which kind of cell is to be defined. of course. of course.e. Instead.63) is not sufficient to display distance values greater than 35km.. only goes for GSM900/GSM850. possible only for GSM900/GSM850). Standard cells use ordinary single timeslots for TCHs and do not distinguish different coverage areas within the cell. Example configuration: ts 0 TRX:0 TRX:1 BCCH TCH ts 1 ext ext ts 2 SDCCH TCH ts 3 ext ext ts 4 TCH TCH ts 5 TCH TCH ts 6 TCH TCH ts 7 ext TCH = near area = far area Signaling of extended TA values As in an extended cell the normal coding range of the timing advance (TA. The coverage area covered by this type of TCHs is also called ‘far area’. This decision is based on the value of the distance threshold HOMSTAM (see command SET HAND [BASICS]). object: range: default: BTS [BASICS] STDCELL EXTCELL DBSTDCELL STDCELL Cell type. thus working as one radio timeslot with an extremely extended ‘guard period’ and thus allow a much higher delay of the bursts received from the MS.e. ranbge 0. MS-BTS distance) of 35km (this value. the ‘area’ is defined by the pool of ‘single’ or ‘double’ timeslots . These ‘double’ TCH are nothing but a pair of directly adjacent radio timelots that are merged together. Within an extended cell. max. max. CBCH) must be configured as ‘double’ timeslots. In an extended cell. Call setup in an extended cell When an MS sets up a call in an extended cell. As opposed to concentric cells (parameter CONCELL. see below) there is no fixed relation between an ‘area’ (far or near) and TRX.CELLTYPE=STDCELL. for DCS1800/PCS1900 the cells must be naturally smaller due to the radio propagation characteristis in the corresponding frequency band). all control channels (BCCH. When the BSC has selected a suitable TCH it forwards the TA and timing 137 . These values are used by the BSC to decide whether a ‘single’ or a ‘double’ TCH is to be assigned to the call. b) The value EXTCELL means ‘extended cell’ and represents a special cell with a maximum cell radius (i. . SDCCH. the BTS adds the current ‘timing offset’ measured from the RACH access burst delay to the CHANNEL REQUIRED message.independent of the timeslots’ association to a TRX. the BTS measures the current MS delay during the SDCCH phase (as mentioned. The coverage area served by this type of TCHs is also called ‘near area’. different TCH pools serve different coverage areas that are characterized by their distance from the antenna:ordinary ‘single’ TCHs are used to provide TCH resources for the coverage area up to the maximum possible MS-BTS distance of 35km. MS-BTS distance) of 100km (this is.special ‘extended’ or ‘double’ TCHs are used to provide channel resources for the coverage area up to the maximum possible MSBTS distance of 100km (please refer to the parameter EXTMODE in the command CREATE CHAN). a new IE called ‘timing offset’ is used in the Abis RSL signalling which allows the representation of the corresponding extended MS delay values. Moreover. CCCH. a) The value STDCELL means ‘standard cell’ and represents a normal cell with a maximum cell radius (i. the SDCCH is always a ‘double’ timeslot) and provides it as a combination of TA and ‘timing offset’ value to the BSC within the PHYSICAL CONTEXT CONFIRM message which is sent prior to the CHANNEL ACTIVATION of the TCH. A ‘single’ TCH is an ordinary TCH as used in standard cells and consists of one radio timeslot.

If the value of parameter SYSID is GSMDCS and the operator wants to preserve the resource for phase1-mobiles. which is the Service Layer Primary Area (SLPA) like a Standard cell. and packet switched data e. Note: The features 'Extended Cell' and 'Concentric Cell' (see CONCELL) exclude each other. GSM900/DCS1800 and GSM850/DCS1800. speech. For every layer. If PBCCH is configured. near-far) When a call has been established in an extended cell.e. the favoured TCHs are the ones with the lowest interference class (see parameter INTCLASS in command SET BTS [INTERF] and compatible with the mobile’s service capabilities. the parameter CONCELL must be set to FALSE in this configuration). If the operator wants to preserve resources for single band mobiles. the SLL is common to both the frequency bands.0.offset values to the BTS in the CHAN ACT for the TCH so that the BTS can can instruct the MS to correctly adjust the timing advance to the current MS-BTS distance.g. The Dual Band Standard Cell must be planned in such a way that the frequency bands have exactly the same coverage. For futher details please refer to the mentioned parameter descriptions.he must create service layers with unique band (layers with BCCH band separated by layers with non-BCCH band) and must define the layers of the non-BCCH band as last in the SLL. TCH allocation principles The radio resource allocation in a Dual band Standard Cell is performed in accordance with the feature ‘Service Dependent Channel Allocation’ but having a only one single Service Layer List (SLL). but only on the setting CELLTYPE=DBSTDCELL.0 are no longer based on the feature ‘concentric cells’ (parameter CONCELL. In other words. This implies that at any location within a Dual Band Standard Cell. i. dual band MSs are allocated on either of the frequency bands. The dual band standard cell is also called ‘Common BCCH cell’ (Attention: As opposed to BR7. In other words. depending on the current chages of the MS-BTS distance. A mobile requesting a TCH within a dual band standard cell is granted TCH resources according to the SLL and its capabilities. see above). it might be necessary to handover the call from a double to s single timeslot or vice versa. This handover is enabled by the parameter EXTCHO and the decision id based on the distance threshold HOMSTAM and the distance margin HOMRGTA (all parameters see command SET HAND [BASICS]). c) The value DBSTDCELL means ‘Dual band standard cell’ and represents a new type of cell having frequencies in two different frequency bands and a BCCH in one of these bands.g. e. GPRS/EGPRS. it must be on the BCCH frequency band. Cell characteristics The frequency bands to be supported are GSM850/PCS1900. services can be allocated in both frequency bands. The service layer selected for search of the TCH resources is determined by the service type requested by the mobile. whereas single band MSs shall be allocated only on BCCH frequencies. Intracell handover due to distance (far-near. Then he must define in 138 . Both circuit switched. the ‘Common BCCH’ cells in BR8. a service can be allocated on either of the frequency bands. he must distribute the TRXs with frequences in GSM baseband and the TRXs in GSM extended band over different service layers. with layers having TRXs of BCCH frequency band and TRXs of non-BCCH frequency band. The dualband standard cell has a cell identity as any single band GSM cell.

In this case.Definition of dedicated layers. Therefore frequencies on which to perform Dynamic MAIO Allocation (DMA) must belong to the same frequency band and two frequency bands must be defined for DMA. and after that the layers for the GSM base band. non-BCCH band frequencies only . If a GPRS mobile accesses the cell. If e.. a particular service supported both in the 900 MHz and in the 1800 MHz band. Frequency Hopping is not allowed across frequency bands. The only exception is between P900 and E900 bands specifying the first ones with the notation (301. resources are ordered on the basis of the interference band they belong to. If a layer contains TRXs from both frequency bands of the Dual band Standard cell. Hence the GPRS mobile is allocated resources within Dual Band Standard Cell depending on the operator policy and according to the settings of the feature ‘Service Dependent Channel Allocation’. Evaluation of MS capabilities A multiband network uses 2-ter and 5-ter System Info messages which enable multiband mobiles to access the network and.g. with BCCH band frequencies only or. to maintain compatibility with single band mobiles.424).g.the service layer list first the layers for GSM extended band. Interworking with feature ‘Multiple Service Layer Support If the operator wants to prioritize a particular frequency band for any given service. in the first positions. the operator wants to prioritize the 900 MHz band) ordered according to a radio quality criterion and in the remaining positions the 1800 MHz layers still ordered according to the same criterion. 139 . the mobile frequency bands of operation and relative power capabilities are sent to the network in the PACKET RESOURCE REQUEST message during the two phase access and within Additional MS Radio Access Capabilities message during one phase access. If a layer contains TRXs of both frequency bands of the Dual Band Standard cell. Interworking with frequency Hopping According to the GSM/3GPP standard. conversely. at the same time. this can be achieved by: . resources are ordered in this layer on the basis of the interference band they belong to and kept with regards both with this criteria and MS capability.Definition of mixed layers (composed of BCCH and non-BCCH frequencies) through a proper order of layers within the list associated to that service. the (for both bands) unique SLL may have. The BSS is informed about the frequency capabilities and associated power capabilities of the multiband MS on each frequency band by the Early Classmark Sending procedure (see parameter EARCLM in command SET BTS [OPTIONS]. Packet data service on the nonBCCH frequency band is allowed by associating EGPRS/GPRS service with a service layer comprising TRXs of the non-BCCH frequency band and setting GEXTS parameter (see below) to the right value. the 900 MHz layers (if e.

FALSE FALSE Concentric cell. the paremeter CELLTYP must be set to the value STDCELL (see above). The concentric cell configuration is also possible in cells with mixed frequency bands .in this case. see above). In any case all control channels of the concentric cell (BCCH. Considering the frequency propagation characteristics and the band-specific maximum cell radius. determined by the values entered for the power reduction (see parameter PWRRED (CREATE TRX)) and. TRXs with the wider range serve the so-called ‘complete area’. GSM850PCS and the parameters for maximum allowed transmission power must be set for both bands (parameters MSTXPMAXGSM and MSTXPMAXDCS. the most useful configuration is to use GSM900 resp. object: range: default: BTS [BASICS] TRUE. the parameter SYSID (see below) must be set to GSMDCS resp. Moreover. in addition to CONCELL=TRUE. Example configuration: ts 0 TRX:0 TRX:1 TRX:2 BCCH TCH TCH ts 1 SDCCH TCH TCH ts 2 TCH TCH TCH ts 3 TCH TCH TCH ts 4 TCH TCH TCH ts 5 TCH TCH TCH ts 6 TCH TCH TCH ts 7 TCH TCH TCH = complete area = inner area Within a concentric cell. Attention: Please be aware that the above configuration is to be regarded as a ‘dual band concentric cell’.CONCELL=FALSE. see below). The different TRX coverage ranges are. A ‘concentric cell’ is a cell in which different TRX may have different ranges. also the opposite configuration is also technically possible. see above) there is a fixed relation of concentric cell areas and particular TRXs. CCCH. In this case. specific intra-cell handovers from the inner to the complete area and vice versa are possible. frequencies of different frequency bands are assigned to the inner and complete area of a concentric cell. TRXs with the smaller range serve the so-called ‘inner area’. However. SDCCH. As opposed to extended cells (parameter CELLTYPE. COMPLETE area INNER area Whether a TRX serves the inner or the complete area is defined in the TRX object (see parameter TRXAREA (CREATE TRX)). for dualband concentric cells by the different TX ouput powers of the used TRX HW (CU/PA) and different propagation attenuations of the different used frequency bands. for single-band concentric cells. PCS1900 frequencies to the inner area. during the call setup procedure in a concentric cell the same values are also evaluated to determine whether the call is set up on a TCH belonging to an inner or complete area TRX. This configuration is different from the so-called ‘dual band standard cell’ configuration (CELLTYP=DBSTDCELL. which was 140 . These handovers are executed on level / distance conditions defined by appropriate thresholds in the handover package (see parameters CCDIST. HORXLVDLI. GSM850 frequencies for the complete area (and thus for the BCCH and also the SDCCHs) and to assign DCS1800 resp. CBCH) must belong to the complete area. HORXLVDLO and HOCCDIST (SET HAND [BASICS])). with all known features of a concentric cell but with different frequency bands in each area. this flag defines whether the cell is a concentric one or not.

The intracell handover cause (inner <-> complete) does not exist for SDCCH-SDCCH handover as in a concentric cell all SDCCHs are always created in the complete area..e. CONCELL cannot be set to TRUE if CELLTYPE=EXTCELL.0 and which is a standard cell with TRXs belonging to different frequency bands but with equal coverage and without any inner /complete area separation. This parameter only has to be set if CRESPARI is set to ‘1’. object: BTS [BASICS] unit: 2dB range: 0. . Cell reselection offset. This parameter. It applies an offset to the cell reselection criterion C2. 141 .63 default: 1 Reference: 3GPP 45.22 introduced in BR8.The features 'Extended Cell' and 'Concentric Cell' exclude each other.008 GSM 03. contained in the IE ‘SI 4 Rest Octets’ on the BCCH (SYSTEM INFORMATION TYPE 4).CRESOFF=1. Notes: . i. is one of the necessary input values for the calculation of C2. For further details please refer to the parameter CRESPARI.

TEMPOFF t PENTIME start of timer expiry of timer CRESOFF Equation C: If the penalty time is set to 31 (i. 1=present. If CRESPARI is set to ‘0’ the parameters CRESOFF. By this temporary offset the C2 of the non-serving cell is artificially made worse and the cell reselection is not executed. Equation B: On expiry of the timer the temporary offset is disregarded and thus . The criterion C2 is an optional feature that can be enabled on a cell basis.e. 142 . Equation A: C2 = C1 + CRESOFF . TEMPOFF. C2 C1 + CRESOFF TEMPOFF C1 C1 + CRESOFF .TEMPOFF as long as the timer (PENTIME) runs and PENTIME < 31 Equation B: C2 = C1 + CRESOFF if the timer (PENTIME) has expired and PENTIME < 31 Equation C: C2 = C1 .008 GSM 03. without any time limitation. The result of this calculation determines the priority of these cells within the list of the six strongest neighbour cells which is dynamically managed in the MS in idle mode. is useful for microcellconfigurations since it prevents fast moving MSs from performing unnecessary cell reselections. Exception: If the current cell and the new cell belong to different location areas the new cell shall only be selected if the C2 of the new cell exceeds C2 of the old serving cell by at least the cell reselect hysteresis (see parameter CELLRESH) for a period of 5 seconds.e. The MS calculates C2 (on the basis of C1) or C1 respectively (if the C2 cell reselection parameters are not broadcast in the affected cell) for the serving and all neighbour cells at least every 5 s. i. indicates the presence of C2 cell reselection parameters on the BCCH in the IE ‘SI 4 Rest Octets’ (SYSTEM INFORMATION TYPE 4) and the IE ‘SI 3 Rest Octets’ (SYSTEM INFORMATION TYPE 3). i. C2.CRESOFF if PENTIME = 31 Equation A: As long as the timer runs C2 is increased by a permanent offset (see parameter CRESOFF) and decreased by a temporary offset (see parameter TEMPOFF). Depending on the availability of C2 cell reselection parameters in the BCCH info the MS considers C1 or C2 for the cell reselection process.if the C2 of a non-serving cell still exceeds the one of the serving cell for a period of 5 s the MS performs a cell reselection. setting PENTIME to 31 results in a permanent decrease of priority. object: range: BTS [BASICS] 0=C2 parameters not present 1=C2 parameters present default: 1 Reference: 3GPP 45. Thus in this case it is possible to exclude particular cells from the cell reselection permanently.CRESPARI=1. 0=not present.22 Cell reselection parameter indicator.e. It is an enhancement of the cell selection C1 (for C1 please see parameter CELLRESH). however. General Principle of the C2 algorithm: If the MS places a non-serving cell on the list of six strongest carriers it starts a timer the value of which has been broadcast on the BCCH (see parameter PENTIME). This mechanism is used to avoid unnecessary location update procedures. 260s) the permanent offset (CRESOFF) is not added to but subtracted.

The parameter values have the following meaning: 1) HSCSD_FIRST_DOWNGRADE means that all HSCSD calls are downgraded first before a GPRS call is downgraded. the BSC first checks the other target cells for available TCH resources. this parameter defines the downgrade GPRS_FIRST_DOWNGRADE strategy for HSCSD and GPRS calls used during the resource reallocation procedure for TCH requests for single-channel circuit . if not possible then 2) directed retry. this parameter indicates which types of CU are used within the BTSE serving the cell. Coverage of serving cell. object: range: default: BTS [BASICS] URBAN. 4) DOWNGRADE_GPRS_ONLY means that only GPRS calls are downgraded while HSCSD calls remain unaffected. CU_ECU_DCSPCS. If no idle TCH can be found and if the TCH congestion is partly caused by multislot calls. This information must be considered for power aspects.CSCE=URBAN. RURAL_OPEN URBAN PENTIME. Attention: If in case c) the INTERCELL HANDOVER CONDITION INDICATION contains more than one target cell. Impacts on TCH Allocation If a CS call request is received in a congested cell. switched calls. TCH requests for single-channel CS calls can occur in form of: BTS object in BR8. HOMOGENEOUS HOMOGENEOUS CU configuration. as different CU types differ in their transmission power levels. the BSC tries to satisfy the TCH request in the following sequence: 1) preemption of a low priority CS call. DGRSTRGY= Downgrade strategy. the BSC starts the downgrade in the first target cell where this is possible. Only if in none of the target cells a TCH can be found for allocation. SUB_URBAN RURAL_QUASI_OPEN.0! b) an incoming inter-BSC handover (receipt of a HANDOVER REQUEST) c) an incoming intra-BSC handover (receipt of an INTERCELL HANDOVER CONDITION INDICATION) d) an intracell handover (receipt of an INTRACELL HANDOVER CONDITION INDICATION) In any of the mentioned cases the downgrade procedure is started to provide TCH resources to the incoming TCH request in accordance with the value set for DGRSTRGY. CBQ have to be skipped. the BSC first analyzes the TCH resources in the first target cell. 3) DOWNGRADE_HSCSD_ONLY means that only HSCSD calls are downgraded while GPRS calls remain unaffected. if not possible then 3) (WPS) queuing 4) downgrade of multislot calls (GPRS/HSCSD) may be periodically 143 . The downgrade can be considered as a kind of object: BTS [BASICS] preemption for resources currently seized by multi-channel calls.0! a) a new call setup of a (receipt of an ASSIGNMENT REQUEST) Default value changed in BR8. range: HSCSD_FIRST_DOWNGRADE With the ‚downgrade strategy’ the operator can determine how much GPRS_FIRST_DOWNGRADE the bandwidth and grade of service of HSCSD and GPRS is affected DOWNGRADE_HSCSD_ONLY DOWNGRADE_GPRS_ONLY in case of TCH congestion. The scenario that triggers a downgrade NO_DOWNGRADE procedure is always a TCH seizure request for a single-channel default: GPRS_FIRST_DOWNGRADE circuit-switched call received when all TCH resources in the cell are Parameters moved from BSC object to busy. CUCONF=HOMOGENEOUS. object: range: default: BTS [BASICS] CU_FLEXCU_BS82II. this parameter defines the propagation of a cell covered by the BTS. 5) NO_DOWNGRADE means that both GPRS and HSCSD calls remain unaffected. 2) GPRS_FIRST_DOWNGRADE means that all GPRS calls are downgraded first before an HSCSD call is downgraded.

The call that triggers the downgrade procedure is marked as “downgrade requested” in order to wait for the resources that will be available after successful completion of the downgrade procedure. running procedure. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE). the resource management process periodically starts the downgrade procedure (if correspondingly enabled via parameter DGRSTRGY) on HSCSD data calls and/or (E)GPRS data calls (if any) in order to get new resources for TCH allocation.the TCH is created with GDCH=<NULL> (see CREATE CHAN) . The call marked as “downgrade requested” must in any case wait for the resources achieved by the downgrade procedure. …).The GPRS downgrade strategy has an influence on all TCH load dependent features such as Traffic Handover (see parameter TRFHOE in command SET HAND[BASICS]). On the other hand. a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i. the BSC tries. WPS/Public call info. if a TCH was activated as PDCH for GPRS traffic but the TEMPCH timer (see parameter TEMPCH in command CREATE 144 . when possible. Service List. Notes: .e. If during the ongoing downgrade procedure other TCHs become ‘idle’ again.For GPRS the downgrade is only possible for those TCHs that can be dynamically shared between CS and GPRS traffic. . the following conditions must be fulfilled: . After the call is queued. starting from the preferred layer. Enhanced Pairing (see parameter EPA in command SET BSC [BASICS]) and AMR Compression Handover (see parameter EADVCMPDCMHO in command SET HAND [BASICS]). Interworking of the features ‘Downgrade strategy’ and (WPS) queuing When a TCH request is queued. then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST.attempted in parallel and queued calls can be served when down grade is successfully completed. For these channels.g. to serve the queued TCH requests by a multislot call downgrade procedure (e.e. in case of Abis congestion the multislot downgrade procedure will be requested on all layers of this cell associated to the multislot service layer list and in the extreme case also on other cells of the same BTSM. (E)GPRS downgrade: Every call is put in the queue with its relevant data (channel request type. DOWNGRADE_GPRS_ONLY. these resources cannot be assigned to the call marked as “downgrade requested”. then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. The downgrade procedure is requested for the multislot calls established on the shared layers with service layer association matching to the service type of the enqueued call. Cell Load Dependent Activation of Half Rate (see parameter EHRACT in command CREATE BTS [BASICS]). However.please see command SET BTS [SERVICE] for further explanations). Please refer to the parameters EPRE (for preemption) and EQ (for (WPS) queueing) in command SET BTS [OPTIONS] and to parameter ENFORCHO (for directed retry) in command SET BTS [BASICS]. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.the TRX supports GPRS (this is the case if the TRX is defined as belonging to a service layer which is included in the SLL for GPRS services .

BS240XS and e-Micro BTS. Antenna Hopping has to deal with various types of CUs (e. Antenna Hopping is enabled for either all CUs including the BCCHTRX CU or for all CUs except for the BCCH-TRX CU.Please see also parameter DGRSTRGYBCNT (command SET BSC [BASICS]). Enable antenna hopping. FALSE FALSE PCU) is running for it. It is not possible to generate Antenna Hopping sequences for each timeslot individually.EANTHOP = FALSE. in periods of TCH congestion the BSC immediately releases PDCHs (TCHs activated for GPRS) with TEMPCH running if a CS TCH request is received and no other idle TCH is available for allocation. restricting the Antenna Hopping between CUs of the same POOL only and thus also between the antennas to which the corresponding CUs of the POOL are connected.g. not on timeslot basis. DCS1800 and PCS1900). including all timeslots on them. GSMCU. the TCH is always regarded as ‘downgradable’ resp. in other words: complete CUs. In other words. this parameter enables or disables the feature “antenna hopping”. The pool grouping and the calculation of pool sequences are done in the BTS core (COBA) by a dedicated algorithm. For each pool a hopping sequence is calculated.g. which is forbidden parallel to Antenna Hopping. The hopping mechanism is the main difference between Antenna Hopping and the already supported frequency hopping schemes. Antenna Hopping is not specified for BTSs belonging to BTSone family. the corresponding CU is not assigned to any CU-POOL. Enabling/disabling Antenna Hopping for the BCCH-TRX is done using the parameter ANTHOPMOD (see below). Antenna Hopping offers a new hopping mechanism in addition to frequency hopping: the DL bursts of a channel are transmitted on GSM frame basis (or every 2nd or 4th frame) over alternating antennas within a cell. perform Antenna Hopping. baseband and synthesizer hopping: TX Antenna Hopping is performed on CU basis. such as BS60. FICOMs are tuned via motor to a specific TRX frequency so that only baseband frequency hopping is possible. whereas a combination with baseband frequency hopping is not allowed. GSM900. BS20. This change was implemented in BR7. CUs connected to a FICOM are excluded automatically from Antenna Hopping. If Antenna Hopping for the BCCH-TRX is excluded. All types of BTS combiners are supported but FICOMs. no matter which value was set for the DGRSTRGY parameter. (which means that there is no ongoing TBF on the TCH). A combination of synthesizer frequency hopping and Antenna Hopping is possible. The feature "not-ramping for BCCH" will be deactivated if Antenna Hopping with ANTHOPMOD (AntennaHoppingMode)=ALLTRX is set. Antenna Hopping allows to obtain a performance improvement (diversity gain) of several dBs in DL direction.0 in the scope of CR1150. requiring no modifications in any HW. object: range: default: BTS [BASICS] TRUE. All CUs of the same frequency band and of the same HW type are always assigned to the same CU-POOL. The feature is a complete SW feature. ‘preemptable’ for CS calls. EDGE-CU and SB-EDGE-CU for switched beams) and frequency bands (e. . because the TX Diversity/Antenna Hopping feature itself is based on some baseband hopping mechanism. Antenna Hopping is supported only by BTSplus mainline. 145 . It is not possible to perform Antenna Hopping between CUs of different types and frequency bands. Due to the limitations of the CClink PicoBTS is not able to do baseband frequency hopping and therefore also no Antenna Hopping. For this a CU-POOL concept has been developed.

the BSC inserts the BCCH frequency on the BA list sent on System Info 2. This parameter is only relevant if the HDCTR feature is generally enabled for the BSC (see command CREATE HDTCR). object: range: default: BTS [BASICS] TRUE. this parameter represents the flag to enable the setting of the TSC (Training Sequence Code) equal to the BCC (Base Station Color Code) for all channels belonging to the BCCH TRX. FALSE FALSE Further related parameters are ANTHOPMOD and ANTHOPP. Enable equal TSC to BCC. FALSE FALSE 146 . object: range: default: BTS [BASICS] TRUE. Further relevant parameters for the HDCTR file handling are HDCFS and HDCFUPE (see command SET BSC [CONTROL]. when this attribute is set to TRUE. Enable Fast Cell reselection. FALSE FALSE EHDCTR=FALSE. EFCRESEL=FALSE. The relevant BSIC inside to SYSTEM INFORMATION TYPE 2 quater will broadcast it for the specific cell. this parameter determines whether the feature ‘history on dropped calls’ (History on Dropped Call Tracing HDCTR) is enabled in the cell. Enable history on dropped call tracing. object: range: default: BTS [BASICS] TRUE.EEOTD=TRUE.

FALSE TRUE Default value changed in BR8. HRACTT2 (for inner area in concentric cells or far area in extended cell). as they are triggered by messages which indicated the speech version capabilities an preference allowed from the MS and MSC point of view.4) the BSC calculates a) the current cell traffic load (per BTS) and b) the current Abis traffic load (per BTSM) Case A: HR activation due to radio TCH load in the cell Before assigning a TCH after having received one of the abovementioned TCH seizure requests (1. object: range: default: BTS [BASICS] TRUE.0! Enable cell load dependent activation of HR.. HRACTT2 (see command CREATE BTS [BASICS]) and the Abis TCH load threshold ABISHRACTTHR (see command CREATE BTSM) the BSC decides which kind of TCH type (resp. This is achieved by setting EHRACT=TRUE and by applying a suitable traffic load threshold value (HRACTT1/HRACTT2). Detailed functional description: The BSC can receive an incoming CS TCH seizure request in the following ways: 1) Receipt of an ASSIGNMENT REQUEST (call setup) 2) Receipt of a HANDOVER REQUEST (incoming MSC-controlled handover). As long as the cell traffic load remains below the threshold defined by the parameters HRACTT1 and HRACTT2. this parameter enables the feature “Cell load dependent activation of half rate” for non-AMR calls in the cell (for AMR calls. of configured radio TCH ∗ 100 For further details about the meaning of single terms of this formula. a separate database flag EHRACTAMR (see below). the BSC forces the incoming TCH seizures to FR or EFR (depending on the preference indicated in the ASS REQ or HO REQ and the BSC/TRAU capability). Before assigning a TCH after having received one of the abovementioned TCH seizure requests (1. please refer to the description of parameter HRACTT1.The BSC calculates the cell traffic load according to the formula Cell traffic load [%] = no. the decisive factor for the BSC in the TCH assignment decision is the signalled speech version preference (unless there is TCH congestion). in situations with high traffic load it makes sense to ignore this preference and to force incoming calls to HR TCHs if HR is indicated as supported speech version in the TCH seizure request. On the basis of the radio TCH load thresholds HRACTT1 resp.4) the BSC calculates the cell traffic load and compares it to the threshold HRACTT1 resp. 3) Receipt of an INTERCELL HANDOVER CONDITION INDICATION (incoming BSC-controlled intercell handover) 4) Receipt of an INTRACELL HANDOVER CONDITION INDICATION (BSC-controlled intracell handover) Cases 1) and 2) represent ‘original’ TCH requests. This feature allows the BSC to override the speech version preferences indicated in incoming TCH seizures requests and to force these incoming TCH seizure requests to FR or HR TCHs depending on the actual radio traffic load situation in the cell (BTS) and the Abis traffic load situation in the BTSM. However. of radio TCH not available for CS TCH allocation no. speech version) is to be assigned for a particular TCH seizure request. 147 .EHRACT=TRUE.. The BSC stores the capability and preference ‘profile’ of each call in one transaction register and considers this profile for all subsequent TCH seizure requests (cases 3 and 4). If EHRACT=FALSE. Both ASS REQ and the HO REQ contain Information Elements indicating the supported speech versions and the speech version preference.

for operation of the feature ‘Cell load dependent activation of half rate’ for AMR calls only the flag EHRACTAMR is relevant. all incoming calls or incoming MSC-controlled handovers. are forced to a HR TCH.Cell Load Dependent Activation of HR does not work when Direct TCH Asssignment (see parameter DIRTCHASS in command SET BTS [OPTIONS]) is enabled. HRACTT2. are forced to a FR or EFR TCH. In case of Direct TCH Assignment the BSC has to decide about the TCH type (FR.To avoid a ping-pong handover from HR to FR and vice versa. The only information about the MS’s speech version capability which is available at this point of time is included in the ‘Establishment cause’ IE within the included CHANNEL REQUEST message. for which HR is indicated as supported speech version. This information is very restricted with respect to the grade of detail and the MS capabilities and preference. As long as the BTSM Abis traffic load remains below the threshold defined by the parameters ABISHRACTTHR.The database flags EHRACTAMR and EHRACT are independent of each other. are forced to a HR TCH. • Incoming calls or incoming handovers. . are forced to a HR TCH.. i. for which HR is indicated as supported speech version (half rate version 1). of Abis TCHs configured in Abis pool ∗ 100 For further details about the meaning of single terms of this formula. Notes: . If the BTSM Abis traffic load exceeds the percentage defined by ABISHRACTTHR.If the cell traffic load exceeds the percentage defined by HRACTT1 resp. which can occur due to subsequent execution of (AMR) decompression handover (see parameter EADVCMPDCMHO in command SET HAND [BASICS]) and intracell handover due to quality (for a call whose quality is still poor after decompression 148 . Interworking between case A and case B • Incoming calls or incoming handovers.e. please refer to the description of parameter ABISHRACTTHR (see command CREATE BTSM). The BSC calculates the Abis traffic load according to the formula BTSM Abis traffic load [%] = no. . if the BTS radio TCH load is below the threshold HRACTT1/HRACTT2 and the BTSM Abis pool TCH is below the threshold ABISHRACTTHR.4) the BSC calculates the BTSM Abis traffic load and compares it to the threshold ABISHRACTTHR. for which HR is indicated as supported speech version. At this point of time the BSC does not check the current TCH load in the cell to decide about the allocation of FR or HR but assigns a TCH type in correspondence with the ‘establishment cause’ value received in the CHANNEL REQUIRED message. all incoming calls or incoming handovers. of Abis TCH not available for CS TCH allocation no. the setting of the flag EHRACT does not have any influence. the BSC forces the incoming TCH seizures to FR or EFR (depending on the preference indicated in the ASS REQ or HO REQ and the BSC/TRAU capability). HR) when it receives the CHANNEL REQUIRED message. Case B: HR activation due to BTSM Abis TCH load Before assigning a TCH after having received one of the abovementioned TCH seizure requests (1. for which HR is indicated as supported speech version. if either the BTS radio TCH load has exceeded the threshold HRACTT1/HRACTT2 or the BTSM Abis pool TCH load has exceeded the threshold ABISHRACTTHR (or both).

EHRACTAMR=FALSE. i. object: range: default: BTS [BASICS] TRUE. For Abis load dependent activation HR the radio TCH traffic load threshold is defined by the parameter ABISHRACTTHR (see CREATE BTSM). For further details about the feature functionality and the exact calculation of the traffic load please refer to the parameters EHRACT. This means that the BSC does not check the current BTS TCH load and the BTSM Abis pool TCH load in case of an intracell handover due to quality. object: range: default: BTS [BASICS] TRUE. For cell load dependent activation HR the radio TCH traffic load threshold is defined by the parameters HRACTAMRT1 and HRACTAMRT2 (see command CREATE BTS BASICS]).0! ENPERNOTDE= FALSE. For further details about AMR please refer to the parameter AMRFRC1 (see command CREATE BTS [BASICS]).e. This feature controls the allocation of AMR HR TCHs in such a way that AMR half rate TCHs are only assigned if the percentage of busy radio TCHs in the BTS or/and the percentage of busy Abis TCHs in the BTSM Abis channel pool have exceeded a configurable threshold. the setting of the flag EHRACT does not have any influence. HRACTAMRT1 and HRACTT1 (see CREATE BTS [BASICS]) and ABISHRACTTHR (see CREATE BTSM). this parameter is the AMR equivalent to the parameter EHRACT (see command CREATE BTS [BASICS]) and allows to enable or disable the feature ‘Cell load dependent activation of half rate’ for AMR calls for all BTSs belonging to the BSC. the BSC just maintains the same channel type / speech codec as used before on the old channel. Instead. the features ‘Cell load dependent actvation of half rate’ and ‘Abis load dependent activation of half rate’ (see parameter ABISHRACTTHR in command CREATE BTSM) are not considered if the BSC receives an INTRACELL HANDOVER CONDITION INDICATION due to quality reasons (cause values ‘uplink quality’ or ‘downlink quality’). Note: The database flags EHRACTAMR and EHRACT are independent of each other. 149 . FALSE TRUE Default value changed in BR8. Enable periodic notification on dedicated channel. Enable cell load dependent activation of half rate for AMR calls. for operation of the feature ‘Cell load dependent activation of half rate’ for AMR calls only the flag EHRACTAMR is relevant. as the basic concept and the traffic load calculation algorithm are exactly the same for calls with standard speech coding (FR version 1 and 2 and HR version 1) and calls with AMR speech coding. FALSE FALSE handover).0! Parameters moved from BSC object to BTS object in BR8. this parameter enables/disables the periodical notification repetition on dedicated channels.

this TCH is regarded as ‘idle’ in any case. Note: Interworking of 'Service Dependent Channel Allocation’ with ‘Multiple Service Layer Support' (MSLS) and traffic load calculation: The percentage calculation done for the Enhanced Pairing is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types.e. 150 .A dual rate TCH (TCHF_HLF) can assume the usage state “busy“ (i.in the far area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]) The value 100 represents 1%. only on HR subslot busy) or “idle”. a TCH_HLF in state “idle” is counted as 2. both HR subslots busy). they are treated as if they were not configured! Thus the value above the fraction bar represents all TCHs in state ‘idle’ (not considering the reserved GPRS TCHs in state ‘idle’) and the value below the fraction bar is the number of the actually created TCHs minus the TCHs reserved for GPRS. no matter which values is set for the DGRSTRGY parameter. this parameter represents the threshold that indicates. no. i. when the Enhanced Pairing for TCH/H channels feature is enabled (see parameter EPA in command SET BSC).e. Enhanced pairing intracell handovers are triggered if the following radio TCH traffic load condition is fulfilled (for further details about the meaning of single terms of this formula. ”active“ (i. .TCHs ’reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation.in the complete area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) .Generally a TCH\F is counted as 2.01 % 0. . Please refer to the command SET BTS [SERVICE] for further explanations. a TCH\H is counted as 1! . In this case the relevant Abis pool TCH load threshold is defined by the parameter ABISHRACTTHR (see command CREATE BTSM). as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. A TCH_HLF in state “active” is counted as 1. Enhanced pairing can also be triggered due to BTSM Abis pool TCH load.10000 4000 Default value changed in BR8. of radio TCH in usage state ‚idle’ * no. please refer to the description of parameter EPAT1).in the whole BTS (in case of standard cell) . of configured radio TCH ∗ 100 < EPAT1[%] * Attention: . .0! Enhanced Pairing Threshold 1..The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]).EPAT1=4000. the percentage of busy radio TCHs .If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM. Note: This parameter only represents the traffic load threshold for the feature ‘Enhanced pairing due to BTS radio TCH load’. object: unit: range: default: BTS [BASICS] 0. separately for every subarea (primary/complementary).e. the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH. .

The UE is thus instructed to report. The general speech coding algorithm codes 20ms of speech to 456 bits and distributes it over 8 halfbursts. The more really relevant 3G cells are available. this parameter allows to switch between coverage mode (enabled) and standard mode (disabled).. when the Enhanced Pairing for TCH/H channels feature is enabled (see parameter EPA in command SET BSC). object: range: default: reference: BTS [BASICS] 0. It indicates the number FDD UTRAN cells the UE shall include in the MEASUREMENT REPORTs.0! ETXDIVTS=FALSE.in the inner area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) .01 % 0.018 3GPP 45. The value must therfore be set considering how many 2G neighbour cells shall be reported in any case.7 5 FDDMURREP=0. defines the number of FACCH halfburst to be received for detecting a FACCH frame.due to transmission problems on the radio interface .in the near area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]). Usually 6 neighbour cells can be reported within one MEASUREMENT REPORT message. 'Halfburst' means that the speech information of one 20ms speech block is contained in one half of the burst only (due to the interleaving one burst carries the information for two different 20ms-speech-blocks). this number of 3G neighbour cells.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode)..3 0 3GPP 44. the percentage of busy TCHs . FACCHs are normal speech bursts which are 'abused' as signaling channels.the steal-bits are falsified the FACCH halfbursts may be recognized as TCH by mistake. For further details please refer to parameter EPAT1 (see above). if available. object: unit: range: default: BTS [BASICS] 1 half burst 0. the higher the value should be set. FALSE FALSE Enhanced Pairing Threshold 2. FDD multiRAT reporting. Enable TX diversity timeshift. If . object: range: default: BTS [BASICS] TRUE. Which value should be set for this parameter strongly depends on the environment of the cell (BTS).broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . Within the 'Normal Bursts' the so-called 'steal-bits' are used to distinguish TCH from FACCH info. 151 .EPAT2=4000. The FACCHQ parameter determines how many halfbursts with the correct steal-bits must have been received to regard a received half-burst sequence as FACCH frame.008 FACCH quality.. this parameter corresponds to the 3GPP parameter FDD_MULTIRAT_REPORTING which is . FACCHQ=5. The default value of ‘0’ only makes sense in areas without any 3G neighbours (no ADJC3G object created for this BTS). this parameter represents the threshold that indicates. object: unit: range: default: BTS [BASICS] 0.10000 4000 Default value changed in BR8. The value 100 represents 1%.

FDD_Qmin_Offset (parameter FDDQMIO. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter FDDQMI (see above). see below) when broadcast in the serving cell.008 FDD Q minimum.008 FDDQMIO=DB00.FDDQMI=MDB12.g.018 3GPP 45. the MS updates the value RLA_C (receive level average of cell) for the serving cell and of the at least 6 strongest non-serving GSM cells at least every 5s. FDD Q mininum offset. MDB20 = -20dB) Algorithm for (CS) cell re-selection from GSM to UTRAN If the 3G Cell Reselection list includes UTRAN frequencies. this parameter corresponds to the 3GPP parameter FDD_Qmin which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2ter and SI2quater and is a threshold for signal Ec/No which is used for the algorithm for GSM to UTRAN cell reselection. 2. see below). DB10 = 10dB) 152 . The parameter values express a value in dB MDBxx = . Note: When a cell reselection has occurred within the previous 15 seconds. The parameter values express a value in dB DBxx = xxdB (e. An MS/UE may start reselection towards the UTRAN cell before decoding the BCCH of the UTRAN cell. The MS then reselects a suitable FDD UTRAN cell if for this FDD cell the following criteria are all met for a period of 5s: 1.018 3GPP 45. this parameter corresponds to the 3GPP parameter FDD_Qmin_Offset which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2ter and SI2quater and is related to multiRAT mobiles.xxdB (e.g. If more than one UTRAN cell fulfils the above criteria. see above). The cell’s measured Ec/No value is equal or greater than the value FDD_Qmin . The cell’s measured RSCP value is equal to or greater than the threshold FDD_RSCPmin (parameter FDDRSCPMI. whenever decoded from a UTRAN FDD cell of an equivalent PLMN. the MS selects the cell with the greatest RSCP value. see below) and 3. The cell’s measured RSCP value exceeds the value of RLA_C for the serving cell and all of the suitable non-serving GSM cells by the value FDD_Qoffset (parameter FDDQO. Cell reselection to UTRAN is prohibited within 5 seconds after the MS/UE has reselected a GSM cell from an UTRAN cell if a suitable GSM cell can be found. The UE stores the UTRAN cell RSCP suitability criterion parameters above. Note: For the meaning of the measurement values RSCP and Ec/No please refere to the description of parameter FDDREPQTY (see below). object: range: BTS [BASICS] MDB20 MDB18 MDB16 MDB14 MDB12 MDB10 MDB08 MDB06 default: MDB12 reference: 3GPP 44. it is used by the MS/UE for the cell re-selection algorithm from GSM to UTRAN. object: range: BTS [BASICS] DB00 DB04 DB06 DB08 DB10 DB12 DB14 default: DB00 reference: 3GPP 44. FDDQMIO represents an offset which is applied to the parameter FDD_Qmin (parameter FDDQMI. The parameters required to determine if the UTRAN cell is suitable are broadcast on BCCH of the UTRAN cell. FDD_Qoffset is increased by 5 dB.

then no cell with a lower value shall be reported.FDDQO=DB00. MDB20 = -20dB) DBxx = xxdB (e. The parameter values express a value in dB MDBxx = . The parameter values express a value in dB DBxx = xxdB (e.0018) defines various similar reporting offsets for different radio acces technologies. FDDREPO is relevant for ‘Enhanced Measurement Reporting’ (parameter REPTYP. even if one of these cells with a lower value would fit into the report.g.) FDDREPO=DB00. and. 1900. Therefore the standard often mentiones the reporting threshold with a wildcart: XXX_REPORTING_OFFSET. different offsets for the different frequency bands. 850. see below) and defines a fixed offset to be applied to all reported 3G neighbour cells. however. it is used by the UE for the cell re-selection algorithm from GSM to UTRAN. FDD reporting offset. This offset parameter. DB10 = 10dB) Note: The 3GPP standard (e.008 FDD Q offset.018 3GPP 45. those cells are reported that have the highest sum of the reported value and the parameter FDD_REPORTING_OFFSET.g.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . so with this setting a 3G Mobile will always change to the 3G network if any acceptable 3G cell is available. 400 etc. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter FDDQMI (see above). this parameter corresponds to the 3GPP parameter FDD_REPORTING_OFFSET which is .g.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode).g. this parameter corresponds to the 3GPP parameter FDD_Qoffset which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2ter and SI2quater and is related multiRAT mobiles. within GERAN. does not affect the actual reported value. DB20 = 20dB) The value ALWAYS indicates an infinite negative (-∞ dB) offset. 900.008 153 . It defines a level offset by which the RLA_C value of an UTRAN FDD neighbour cell must exceed the RLA_C of the serving GSM cell before the UTRAN neighbour cell is considered for cell reselection from GSM to UTRAN. object: range: BTS [BASICS] ALWAYS MDB28 MDB24 MDB20 MDB16 MDB12 MDB08 MDB04 DB00 DB04 DB08 DB12 DB16 DB20 DB24 DB28 default: DB00 reference: 3GPP 44. object: range: BTS [BASICS] DB00 DB06 DB12 DB18 DB24 DB30 DB36 DB42 default: DB00 reference: 3GPP 44.018 3GPP 45. 44.xxdB (e. The offset is applied as follows: if there is not enough space in the report for all valid cells. 1800. TDD. If a cell can not be reported due to lack of space in the report message (MEASUREMENT REPORT or ENHANCED MEASUREMENT REPORT). where XXX represents values such as (FDD.

• Ec/No = Energy chip to Noise over all. ECNO RSCP 3GPP 44. which is checked in order to determine whether a particular UMTS FDD neighbour cell is a suitable target cell for imperative handovers from GSM to UMTS. is defined by the Ec/No-oriented parameter UMECNO (see command CREATE ADJC3G).215 FDD reporting quantity. It determines in which way the MSs shall report the radio conditions of UMTS FDD neighbour cells. but the processing of the measured values is different: .433 3GPP 25.018 3GPP 45. the handover minimum condition. is defined by the RSCP-oriented parameter USRSCP (see command CREATE ADJC3G). but the processing of the measured values is different: .If FDDREPQTY is set to RSCP. • 2G-3G handovers from GSM to UMTS due to ‘sufficient coverage’ (see parameter EUSCHO in command SET HAND [BASICS]) are possible with both settings of FDDREPQTY. this value indicates the DL quality in the UMTS FDD neighbour cell and is thus comparable to the RXQUAL resp. which is checked in order to determine whether a particular UMTS FDD neighbour cell is a suitable target cell for imperative handovers from GSM to UMTS. C/I values in GSM. 154 .in the MEASUREMENT INFORMATION messages via the SACCH b) REPORTING_QUANTITY which is indicated by the MS/UE in the ENHANCED MEASUREMENT REPORT messages sent via the SACCH. the sufficient coverage condition.If FDDREPQTY is set to RSCP. object: range: default: reference: BTS [BASICS] RSCP. which is checked in order to determine whether a particular UMTS FDD neighbour cell is a suitable target cell for ‘sufficient coverage’ handovers from GSM to UMTS.If FDDREPQTY is set to ECNO. . The possible values are • RSCP = Received Signal Code Power this value indicates the DL receive level in the UMTS FDD neighbour cell and is thus comparable to the RXLEV value in GSM. this parameter corresponds to the 3GPP parameters a) FDD_REP_QUANT which is sent to the MS/UE .008 3GPP 25. is defined by the RSCP-oriented parameter RXLEVMINC (see command CREATE ADJC3G). Important: The setting of the FDDREPQTY has an influence on the 2G-3G handover processing in the BTS: • 2G-3G handovers from GSM to UMTS due to ‘better cell’ (see parameter EUBCHO in command SET HAND [BASICS]) are only possible if FDDREPQTY is set to RSCP. the handover minimum condition.FDDREPQTY=RSCP. as only in this case a comparison of the RXLEV value of the serving GSM cell to the RSCP value in the UMTS FDD neighbour cell is possible via the handover margin (see parameter HOM in command CREATE ADJC3G). • Imperative 2G-3G handovers from GSM to UMTS (see parameter EUIMPHO in command SET HAND [BASICS]) are possible with both settings of FDDREQTY. MultiRAT mobiles (RAT=Radio Access Technology) can report the radio conditions of UMTS FDD neighbour cells either by RSCP values (level oriented) or by Ec/No values (quality oriented) but not both at the same time. The setting of FDDREPQTY determines which of the two reporting methods shall be used by the multiRAT MSs.in the SYSTEM INFORMATION TYPE 2quater messages via the BCCH (in idle mode) and .

i.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and .018 155 . the threshold FDDREPTH2 is valid for the not-reported RSCP value of the affected 3G neighbour cell. This means that a) when FDDREPQTY=RSCP. object: range: default: reference: BTS [BASICS] 0. this parameter corresponds to the 3GPP parameter FDD_REPORTING_THRESHOLD_2 which which is . and.g.If FDDREPQTY is set to ECNO. 1900. 900. which is checked in order to determine whether a particular UMTS FDD neighbour cell is a suitable target cell for imperative handovers from GSM to UMTS. the distinction of the channels is done on the basis of Code division multiplex. For the exact consideration of these threshold values within the neighbour cell ranking algorithm within the ENHANCED MEASUREMENT REPORT messages. RXLEV_06. which is valid only for a particular code only. must be distinguished from the RSCP value. 63 0 3GPP 45.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode). the sufficient coverage condition. NEVER default: RXLEV_00 reference: 3GPP 45. The relation of RSSI. As described for parameter FDDREPQTY. FDDREPTH=RXLEV_00. RXLEV_12. FDDREPTH defines a threshold which UTRAN cell has to exceed in order to be reported in the ENHANCED MEASUREMENT REPORT (for further details about enhanced measurement reporting please refer to parameter REPTYP (see below)). Therefore the standard often mentiones the reporting threshold with a wildcart: XXX_REPORTING_THRESHOLD. RXLEV_30. each channel is characterized by its own code. TDD. b) when FDDREPQTY=ECNO. where XXX represents values such as (FDD. RSCP and Ec/No is defined as RSSI – RSCP = Ec/No FDD reporting threshold.018 FDDREPTH2=0. RXLEV_24. This RSSI value.g. please refer to parameter REPTYP. Additional background information: In a UMTS FDD network. the different calls are transmitted via the same radio frequency.e.0018) defines various similar reporting thresholds for different radio acces technologies.. The parameter values express an RXLEVvalue in dB RXLEV_xx = xxdB (e. RXLEV_18. 400 etc.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode). 850. is defined by the Ec/No-oriented parameter USECNO (see command CREATE ADJC3G).. RXLEV_36.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . this parameter corresponds to the 3GPP parameter FDD_REPORTING_THRESHOLD which is . object: range: BTS [BASICS] RXLEV_00. however. 1800. the UTRAN neighbour cell can either be reported by its RSCP or its Ec/No value. the threshold FDDREPTH2 is valid for the not-reported Ec/No value of the affected 3G neighbour cell.008 3GPP 44. RXLEV_06 = -115 dBm + 6dB = -109 dBm) Note: The 3GPP standard (e. different thresholds for the different frequency bands. The overall downlink signal which is broadcast in a particular UMTS neighbour cell is expressed as RSSI = Received Signal Strength Indicator. It defines the threshold which each reported UTRAN FDD adjacent cell has to exceed with its not-reported value in order to be included in the ENHANCED MEASUREMENT REPORT (for further details about enhanced measurement reporting please refer to parameter REPTYP (see below)). within GERAN.008 3GPP 44.) FDD reporting threshold 2. 44.

MDB087. this parameter defines the first AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. If frequency hopping is disabled . RATE_03. <NULL> RATE_03 default: Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. object: range: BTS [BASICS] MDB115. MDB107. object: range: BTS[BASICS] RATE_01. MDB089. in case of baseband hopping with CU failure).xxxdBm (e. MDB111. RATE_05. <NULL> RATE_01 default: Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. RATE_06. which sends the AMR parameter set to the BTS in the CHANNEL ACTIVATION and to the MS in the ASSIGNMENT COMMAND (resp.e. RATE_02. RATE_05. This parameter eclipses its equivalent parameter AMRFRC3 if frequency hopping is currently active for an AMR call. MDB113.008 3GPP 44. RATE_06. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. MDB099. FHAMRFRC1=RATE_01. the equivalent parameter of the BTS package will be considered. AMR Full Rate Codec 2 for frequency hopping. MDB101.018 FDD RSCP minimum. RATE_08.g. RATE_02. this parameter defines the third AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. RATE_05.0 FHAMRFRC2=RATE_03. MDB091. object: range: BTS[BASICS] RATE_01. RATE_04. RATE_04. MDB105. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. The parameter values express a value in dBm MDBxxx = . RATE_02. RATE_07.FDDRSCPMI=MDB101. RATE_04. object: range: BTS[BASICS] RATE_01.g. HANDOVER COMMAND in case of inter-cell handover). MDB097. Whether the AMR parameter set defined in the BTS object or the one defined in the FHSY object is used for a particular call is determined by the BSC.it is used by the UE for the cell re-selection algorithm from GSM to UTRAN. Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.0 156 . MDB095. RATE_08. This parameter eclipses its equivalent parameter AMRFRC1 if frequency hopping is currently active for an AMR call. MDB093. MDB109. RATE_06. RATE_07. MDB085 default: MDB101 reference: 3GPP 45. this parameter defines the second AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. RATE_03. RATE_03. MDB103. this parameter corresponds to the 3GPP parameter FDD_ which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2ter and SI2quater and is related multiRAT mobiles . RATE_08.no matter whether semipermanently (i.0 FHAMRFRC3=RATE_06. <NULL> RATE_06 default: AMR Full Rate Codec 3 for frequency hopping. HOPP=FALSE) or only temporarily (e. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter FDDQMI (see above). This parameter eclipses its equivalent parameter AMRFRC2 if frequency hopping is currently active for an AMR call. RATE_07. FDDRSPMI represents a minimum RSCP threshold a UTRAN must exceed to be considered for GSM to UTRAN cell reselection. MDB115 = -115dBm) AMR Full Rate Codec 1 for frequency hopping.

FHAMRFRTH23=12-4.31.. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRFRC1 to AMRFRC2 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].5dB hysteresis: 0.5dB hysteresis: 0.0 dB] Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.5dB] hysteresis: 0.5dB hysteresis: 0.7.0 dB] Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.5dB] threshold: 23 [12. RATE_02. RATE_03. RATE_04.. RATE_08. object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0.5 dB] hysteresis: 4 [1.5dB threshold: 0.0 157 .7.5dB] hysteresis: 0. This parameter eclipses its equivalent parameter AMRFRC4 in command CREATE BTS [BASICS]) if frequency hopping is currently active for an AMR call.63 [0. The values CODEC_MODE_0x represent the created AMR FR CODECs (AMRFRCx) of the ACS.5dB] threshold: 12 [3.7.. This parameter eclipses its equivalent AMRFRTH34 if frequency hopping is currently active for an AMR call.0 dB] hysteresis: 4 [1. object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0.0 FHAMRFRTH34=23-4. object: range: BTS[BASICS] RATE_01...0 AMR Full Rate Codec 4 for frequency hopping. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1.. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1.31.15 [0. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. <NULL> RATE_08 default: Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. RATE_06. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRFRC2 to AMRFRC3 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].31. AMR Full Rate Thresholds 34 for frequency hopping. RATE_07.5dB] hysteresis: 0.63 [0..15 [0.5dB threshold: 0.. object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0. this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRFRC3 to AMRFRC4 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].5dB threshold: 0. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. this parameter defines which AMR FR CODEC of the created AMR FR ACS shall be used first after FR TCH assignment in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]... this parameter defines the fourth AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Full Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]..5 dB] hysteresis: 4 [2. This parameter eclipses its equivalent parameter AMRFRTH12 if frequency hopping is currently active for an AMR call. FHAMRFRIC=START_MODE _FR. This parameter eclipses its equivalent parameter AMRFRIC if frequency hopping is currently active for an AMR call.5dB] threshold: 7 [3.0 dB] Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.0 AMR Full Rate Thresholds 12 for frequency hopping.63 [0.. object: range: BTS[BASICS] START_MODE_FR CODEC_MODE_01 CODEC_MODE_02 CODEC_MODE_03 CODEC_MODE_04 START_MODE_FR default: Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.FHAMRFRC4=RATE_08. AMR Full Rate Thresholds 23 for frequency hopping. This parameter eclipses its equivalent parameter AMRFRTH23 if frequency hopping is currently active for an AMR call.0 AMR Full Rate Initial Codec for frequency hopping. RATE_05. FHAMRFRTH12=7-4.15 [0.

For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. RATE_04. RATE_02. object: range: default: BTS[BASICS] RATE_01. RATE_02.0 FHAMRHRC4=RATE_04. RATE_04. ACS shall be used first after HR TCH assignment in case of active object: BTS[BASICS] frequency hopping (see also parameter HOPP in command SET BTS range: START_MODE_HR [OPTIONS]. <NULL> RATE_03 Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. RATE_02. This parameter eclipses its equivalent parameter AMRHRC1 if frequency hopping is currently active for an AMR call. <NULL> RATE_01 Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. <NULL> RATE_04 Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. RATE_05. RATE_03. CODEC_MODE_04 default: START_MODE_HR For further details about the parameter values and AMR parameters Parameter renamed from “<old and thresholds please refer to the parameter AMRFRC1. this parameter defines the first AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].0 FHAMRHRC3=RATE_03. AMR Half Rate Codec 4 for frequency hopping. RATE_04. RATE_05. RATE_05. The values CODEC_MODE_0x represent the created CODEC_MODE_01 AMR HR CODECs (AMRHRCx) of the ACS. This parameter eclipses its equivalent parameter AMRHRC2 if frequency hopping is currently active for an AMR call. object: range: default: BTS[BASICS] RATE_01. This parameter eclipses CODEC_MODE_02 its equivalent parameter AMRHRIC if frequency hopping is currently CODEC_MODE_03 active for an AMR call. This parameter eclipses its equivalent parameter AMRHRC4 if frequency hopping is currently active for an AMR call.0 158 . AMR Half Rate Codec 2 for frequency hopping. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1.0 FHAMRHRIC=START_MODE AMR Half Rate Initial Codec for frequency hopping. RATE_04. this parameter defines the third AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. FHAMRHRC2=RATE_02. object: range: default: BTS[BASICS] RATE_01. RATE_03. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. object: range: default: BTS[BASICS] RATE_01.0 AMR Half Rate Codec 1 for frequency hopping. this parameter defines the fourth AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].FHAMRHRC1=RATE_01. RATE_05. <NULL> RATE_02 Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. AMR Half Rate Codec 3 for frequency hopping. this parameter defines which AMR HR CODEC of the created AMR HR _HR. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. RATE_02. RATE_03. name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8. RATE_03. This parameter eclipses its equivalent parameter AMRHRC3 if frequency hopping is currently active for an AMR call. this parameter defines the second AMR (Adaptive Multi Rate) active CODEC of the Active CODEC Set (ACS) for AMR Half Rate in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS].

FHAMRHRTH12=19-4,
object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0.5dB hysteresis: 0.5dB threshold: 0..63 [0..31.5dB] hysteresis: 0..15 [0..7.5dB] threshold: 19 [9.0 dB] hysteresis: 4 [2.0 dB]

Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.0

AMR Half Rate Thresholds 12 for frequency hopping, this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC1 to AMRHRC2 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. This parameter eclipses its equivalent parameter AMRHRTH12 if frequency hopping is currently active for an AMR call. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. AMR Half Rate Thresholds 23 for frequency hopping, this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC2 to AMRHRC3 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. This parameter eclipses its equivalent parameter AMRHRTH23 in command CREATE BTS [BASICS]) if frequency hopping is currently active for an AMR call. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1. AMR Half Rate Thresholds 34 for frequency hopping, this parameter defines the C/I threshold and the associated hysteresis for the AMR downlink CODEC mode adaptation transition from AMRHRC3 to AMRHRC4 and vice versa in case of active frequency hopping (see also parameter HOPP in command SET BTS [OPTIONS]. This parameter eclipses its equivalent parameter AMRHRTH34 if frequency hopping is currently active for an AMR call. For further details about the parameter values and AMR parameters and thresholds please refer to the parameter AMRFRC1.

FHAMRHRTH23=24-4,
object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0.5dB hysteresis: 0.5dB threshold: 0..63 [0..31.5dB] hysteresis: 0..15 [0..7.5dB] threshold: 24 [12.0 dB] hysteresis: 4 [2.0 dB]

Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.0

FHAMRHRTH34=30-4,
object: format: unit: range: default: BTS[BASICS] threshold-hysteresis threshold: 0.5dB hysteresis: 0.5dB threshold: 0..63 [0..31.5dB] hysteresis: 0..15 [0..7.5dB] threshold: 30 [15.0 dB] (BTS+) <NULL> (BTS1) hysteresis: 4 [2.0 dB]

Parameter renamed from “<old name>”to “FH<old name>” and moved from FHSY object to BTS[BASICS] object in BR8.0

159

FRACTAMRTH1=3000,
object: range: default: BTS [BASICS] 0.. 10000 3000

Full Rate Activation AMR threshold, this parameter is only relevant if the parameters EADVCMPDCMHO and EADVCMPHOAMR are set to TRUE (see SET HAND [BASICS]). It is used for load-dependent AMR Decompression Handover. The task of this handover type is to hand over as many AMR calls (that currently occupy a HR TCH to a FR TCH) as possible to provide the best possible QoS and speech quality in time periods with an acceptably low TCH load and Abis pool TCH load. On every expiry of the timer TRFCT (see SET BSC) the BSC checks the traffic load in its cells and compares it to the threshold FRACTAMRTH1. For AMR compression handover the BSC calculates the traffic load as follows
Cell traffic load [%] = no. of TCH* in usage state ‘busy’** no. of TCH in state unlocked/enabled ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs indicated as ‘reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation, i.e. they are treated as if they were not configured! Thus, reserved GPRS TCHs in state ‘GPRS busy’ are not considered (value above the fraction bar) and the value below the fraction bar is the number of TCHs in ‘unlocked/enabled’ minus the TCHs reserved for GPRS in the same state. - If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

If the traffic load in the cell drops below the threshold FRACTAMRTH1, the BSC enables the load-dependent AMR decompression handover in the affected BTS by sending a SET ATTRIBUTE message with the appropriate indications to the BTS. This indication starts the load-dependent AMR decompression handover decision process in the BTS. For further details, please refer to the parameter EADVCMPDCMHO (see command SET HAND [BASICS]). Note: Interworking of ‘Service Dependent Channel Allocation’ with traffic load calculation The percentage calculation done for load dependent Compression/Decompression Handover is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types, separately for every subarea (primary/complementary). Please refer to the command SET BTS [SERVICE] for further explanations.

160

FRACTAMRTH2=3000,
object: range: default: BTS [BASICS] 0.. 10000 3000

FRACTTH1=3000,
object: range: default: BTS [BASICS] 0.. 10000 3000

Full Rate Activation Threshold 2 for AMR calls, this parameter is only relevant if the parameters EADVCMPDCMHO and EADVCMPHOAMR are set to TRUE (see SET HAND [BASICS]). FRACTAMRTH2 is the equivalent to the parameter FRACTTH2 (see below) for AMR calls and defines a traffic load threshold which is evaluated for load-dependent AMR decompression handover. It has exactly the same function like the parameter FRACTAMRTH1 (see above) but affects different cell areas: - in the inner area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) - in the near area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]). Full Rate Activation Threshold 1, this parameter this parameter is only relevant if the parameters EADVCMPDCMHO and EADVCMPHOAMR are set to TRUE (see SET HAND [BASICS]). It is used for load-dependent non-AMR Decompression Handover. The task of this handover type is to hand over as many non-AMR calls (that currently occupy a HR TCH to a (E)FR TCH) as possible to provide the best possible QoS and speech quality in time periods with an acceptably low TCH load and Abis pool TCH load. On every expiry of the timer TRFCT (see SET BSC) the BSC checks the traffic load in its cells and compares it to the threshold FRACTTH1. For AMR compression handover the BSC calculates the traffic load as follows
Cell traffic load [%] = no. of TCH* in usage state ‘busy’** no. of TCH in state unlocked/enabled ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs indicated as ‘reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation, i.e. they are treated as if they were not configured! Thus, reserved GPRS TCHs in state ‘GPRS busy’ are not considered (value above the fraction bar) and the value below the fraction bar is the number of TCHs in ‘unlocked/enabled’ minus the TCHs reserved for GPRS in the same state. - If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

If the traffic load in the cell drops below the threshold FRACTTH1, the BSC enables the load-dependent non-AMR decompression handover in the affected BTS by sending a SET ATTRIBUTE message with the appropriate indications to the BTS. This indication starts the load-dependent non-AMR decompression handover decision process in the BTS.
161

FRACTTH2=3000,
object: range: default: BTS [BASICS] 0.. 10000 3000

FRANOFFS=<NULL>,
object: range: default: BTS [BASICS] 0.. 255, <NULL> <NULL>

For further details, please refer to the parameter EADVCMPDCMHO (see command SET HAND [BASICS]). Note: Interworking of ‘Service Dependent Channel Allocation’ with traffic load calculation The percentage calculation done for load dependent Compression/Decompression Handover is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types, separately for every subarea (primary/complementary). Please refer to the command SET BTS [SERVICE] for further explanations. Full Rate Activation Threshold 2 for non-AMR calls, this parameter is only relevant if the parameters EADVCMPDCMHO and EADVCMPHOAMR are set to TRUE (see SET HAND [BASICS]). FRACTTH2 is the equivalent to the parameter FRACTAMRTH2 (see above) for non-AMR calls and defines a traffic load threshold which is evaluated for load-dependent non-AMR decompression handover. It has exactly the same function like the parameter FRACTTH1 (see above) but affects different cell areas: - in the inner area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) - in the near area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]). Frame number offset, this parameter is relevant if the feature ‘inter Site Synchronization’ (ISS) is used and indicates, as an integer value, the frame number offset of the BTS. For further details about ISS and the meaning of this parameter please refer to parameter EINTSITSYN (see command CREATE BTSM).

GEXTS=<NULL>,
object: range: default: BTS [BASICS] ALL900, ALLFREQ, <NULL> <NULL>

GPRS extension, this parameter specifies if GPRS/EGPRS is allowed also in non-BCCH bands of a dual band standard cell (parameter value CELLTYP=DBSTDCELL, see above). Guaranteed minimum Abis, this parameter specifies the minimum percentage of ‘in service ‘Abis subslots of the BTSM Abis pool (see command CREATE SUBTSLB) that shall in any case be kept available for allocation for this cell (BTS). When allocating new Abis TCH resources in any BTS X of a particular BTSM, the system guarantees that (after the Abis allocation for BTS X) for every BTS Y in the same BTSM the percentage of Abis subslots still idle and in service is equal or greater than GUARMABISy - %BusyAbisy where: (GUARMABISy ≠ 0) and (%BusyAbisy ≤ GUARMABISy ). BusyAbisy is the percentage of Abis subslots currently allocated to BTS Y, calculated with respect to the total number of Abis subslots of the Abis pool that are in state unlocked/enabled. Note: GUARMABIS is only guaranteed under normal conditions. It is not guaranteed: 1) in case a fault or an operator command causes the outage of service of part of or all the Abis subslots in the Abis pool, as long as the other cells of the site keep allocated most of the residual in service Abis resources. 2) temporarily, after a reconfiguration that reduces the Abis pool size. 3) in case the Abis pool is heavily undersized with respect to the radio configuration.

GUARMABIS=0,
object: unit: range: default: BTS [BASICS] 1% 0..20 0

162

HRACTAMRT1=6000,
object: unit: range: default: BTS [BASICS] 0,01 % 0..10000 6000

Half Rate Activation AMR threshold, this parameter is used for two different features related to AMR calls - Cell Load Dependent Activation of Half Rate for AMR Calls - load dependent AMR Compression Handover As the functionality of these features is different in both cases, they are explained in separate points. a) Cell Load Dependent Activation of Half Rate for AMR calls In this case HRACTAMRT1 is only relevant if the parameter EHRACTAMR (see above) is set to TRUE. HRACTAMRT1 is the equivalent to the parameter HRACTT1 (see below) for AMR calls and defines a traffic load threshold which is evaluated for the forced speech version selection for incoming AMR TCH seizures. For this, the BSC compares HRACTAMRT1 to the percentage of TCHs not available for CS allocation (in state busy, locked or shutting down) related to the number of TCHs configured in - in the whole BTS (in case of standard cell) - in the complete area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) - in the far area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]) If the cell traffic load exceeds the percentage defined by HRACTAMRT1, all incoming AMR calls or incoming AMR handovers, for which AMR HR is indicated as supported speech version, are forced to an AMR HR TCH. If the cell traffic load is below the percentage defined by HRACTAMRT1, all incoming calls are forced to AMR FR. As the basic principle is exactly the same like for cell load dependent activation of HR for non-AMR calls please refer to the parameters HRACTT1 (see below) and EHRACT (see above) for further details (e.g. concerning the traffic load calculation)). b) Load dependent AMR compression handover On every expiry of the timer TRFCT (see SET BSC) the BSC checks the traffic load in its cells and compares it to the threshold HRACTAMRT1. For AMR compression handover the BSC calculates the traffic load as follows
Cell traffic load [%] = no. of TCH* in usage state ‘busy’** no. of TCH in state unlocked/enabled ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs indicated as ‘reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation, i.e. they are treated as if they were not configured! Thus, reserved GPRS TCHs in state ‘GPRS busy’ are not considered (value above the fraction bar) and the value below the fraction bar is the number of TCHs in ‘unlocked/enabled’ minus the TCHs reserved for GPRS in the same state. 163

- If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

HRACTAMRT2=6000,
object: unit: range: default: BTS [BASICS] 0,01 % 0..10000 6000

If the traffic load in the cell exceeds the threshold HRACTAMRT1, the BSC enables the AMR compression handover in the affected BTS by sending a SET ATTRIBUTE message with the appropriate indications to the BTS. This indication starts the AMR compression handover decision process in the BTS. Note: Interworking of ‘Service Dependent Channel Allocation’ with traffic load calculation The percentage calculation done for load dependent Compression/Decompression Handover is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types, separately for every subarea (primary/complementary). Please refer to the command SET BTS [SERVICE] for further explanations. Half Rate Activation AMR threshold, like the parameter HRACTAMRT1, this parameter is used for the features - Cell Load Dependent Activation of Half Rate for AMR Calls - AMR Compression Handover It has exactly the same function like the parameter HRACTAMRT1 (see above) but affects different cell areas: - in the inner area of a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) - in the near area of an extended cell (see parameter CELLTYPE=EXTCELL in command CREATE BTS [BASICS]). HRACTAMRT2 is the equivalent to the parameter HRACTT2 (see below) for AMR calls and defines a traffic load threshold which is evaluated for the forced speech version selection for incoming AMR TCH seizures. For this, the BSC compares HRACTAMRT2 to the percentage of TCHs not available for CS allocation (in state busy, locked or shutting down) related to the number of TCHs configured in the cell areas mentioned above. If the cell traffic load exceeds the percentage defined by HRACTAMRT2, all incoming AMR calls or incoming AMR handovers, for which AMR HR is indicated as supported speech version, are forced to an AMR HR TCH. If the cell traffic load is below the percentage defined by HRACTAMRT2, all incoming calls are forced to AMR FR. As the basic principle is exactly the same like for cell load dependent activation of HR for non-AMR calls please refer to the parameters HRACTT1 (see below) and EHRACT (see above) for further details (e.g. concerning the traffic load calculation). For AMR compression handover, the same principles apply as described for parameter HRACTAMRT1.

164

HRACTT1=6000,
object: unit: range: default: BTS [BASICS] 0,01 % 0..10000 6000

HR activation threshold 1, this parameter defines a threshold which is used by the following features a) Cell Load Dependent Activation of Half Rate and b) load-dependent AMR compression handover a) Cell Load Dependent Activation of Half Rate This feature applies if the parameter EHRACT (see above) is set to TRUE. For this case HRACTT1 defines a traffic load threshold that is evaluated for the forced speech version selection for incoming nonAMR TCH seizures. For this, the BSC compares HRACTT1 to the percentage of busy TCHs (related to the available TCHs) within - the cell (for standard cells) - the complete area (for concentric cells) - the far area (for extended cells). For the feature CLDAHR the BSC calculates the traffic load as follows
Cell traffic load [%] = no. of TCH not available for CS TCH allocation* no. of configured TCH ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) The “no. of TCH not available for CS TCH allocation“ includes - TCHs in usage state „busy“ ** - TCHs in usage state „locked“ or „shutting down“ - (**) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs reserved for GPRS (see GMANPRES in CREATE PTPPKF) are totally excluded from the calculation, i.e. they are treated as if they were not configured. Thus neither the value above the fraction bar nor the one below the fraction bar includes the ‘reserved’ TCHs for GPRS. - If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

If the cell traffic load exceeds the percentage defined by HRACTT1, all incoming calls or incoming handovers, for which HR is indicated as supported speech version, are forced to a HR TCH. If the cell traffic load is below the percentage defined by HRACTT1, all incoming calls are forced to FR or EFR (depending on the capability and preference indicated in the ASSIGNMENT REQUEST or HANDOVER REQUEST message). For further details please refer to the parameter EHRACT. b) load dependent non-AMR compression handover The purpose of Compression handover is, in case of high TCH load, to transfer (E)FR calls with suitably good radio link quality to a HR TCH by an intracell handover in order to prevent TCH blocking by providing additional TCH resources. On every expiry of the timer TRFCT (see SET BSC) the BSC checks the traffic load in its cells and compares it to the threshold HRACTAMRT1.
165

For AMR compression handover the BSC calculates the traffic load as follows
Cell traffic load [%] = no. of TCH* in usage state ‘busy’** no. of TCH in state unlocked/enabled ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs indicated as ‘reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation, i.e. they are treated as if they were not configured! Thus, reserved GPRS TCHs in state ‘GPRS busy’ are not considered (value above the fraction bar) and the value below the fraction bar is the number of TCHs in ‘unlocked/enabled’ minus the TCHs reserved for GPRS in the same state. - If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

HRACTT2=1000,
object: unit: range: default: BTS [BASICS] 0,01 % 0..10000 6000

If the traffic load in the cell exceeds the threshold HRACTAMRT1, the BSC enables the AMR compression handover in the affected BTS by sending a SET ATTRIBUTE message with the appropriate indications to the BTS. This indication starts the AMR compression handover decision process in the BTS which has the task to hand over all AMR calls currently occupying a FR TCH to a HR TCH if the quality (C/I) conditions of this call are good. The quality criteria for the AMR compression handover are defined by the C/I thresholds HOTHAMRCDL and HOTHAMRCUL (see SET HAND [BASICS]). Note: Interworking of ‘Service Dependent Channel Allocation’ with traffic load calculation The percentage calculation done for load dependent Compression/Decompression Handover is done referring only to the TRXs included in the SLLs for the AMR speech and non-AMR speech service types, separately for every subarea (primary/complementary). Please refer to the command SET BTS [SERVICE] for further explanations. HR activation threshold 2, this parameter is only relevant for concentric cells or extended cells and defines thresholds for the features listed under HRACTT1 (see above) for non-AMR calls in - the inner area (for concentric cells) - the near area (for extended cells). The thresholds are used in exact correspondence with the explanations provided for HRACTT1.

166

LCBM0=<NULL>,
object: format: range: BTS [BASICS] <msgid> – <page> – <reprate> - <scheme> msgid: 0..65534 page: 1..92 characters string reprate: SEC_0002, SEC_0010, SEC_0030, SEC_0060, SEC_0090, SEC_0120, SEC_0150, SEC_0180, SEC_0240, SEC_0360, SEC_0480, SEC_0960, SEC_1920 scheme: GERMAN, ENGLISH, ITALIAN, FRENCH, SPANISH, DUTCH, SWEDISH, DANISH, PORTUGUESE, FINNISH, NORWEGIAN, GREEK, TURKISH, UNSPECIFIED <NULL>

Local Cell Broadcast Message 0, this specifies the handling and the contents of the Local Cell Broadcast Message.

default:

LCBM1=<NULL>,
object: BTS [BASICS] format and range: see LCBM0 default: <NULL>

Local Cell Broadcast Message 1, this parameter specifies the handling and the contents of the Local Cell Broadcast Message. For format, range and default settings of the parameter value please see parameter LCBM0. Local Cell Broadcast Message 2, this parameter specifies the handling and the contents of the Local Cell Broadcast Message. For format, range and default settings of the parameter value please see parameter LCBM0. Local Cell Broadcast Message 3, this parameter specifies the handling and the contents of the Local Cell Broadcast Message. For format, range and default settings of the parameter value please see parameter LCBM0. Measure extra BCCH frequencies, this parameter enables/disables the feature “Automatic Procedure to measure extra BCCH Frequencies per cell”.

LCBM2=<NULL>,
object: BTS [BASICS] format and range: see LCBM0 default: <NULL>

LCBM3=<NULL>,
object: BTS [BASICS] format and range: see LCBM0 default: <NULL>

MEAEXTBCCH= FALSE,
object: range: default: BTS [BASICS] TRUE, FALSE FALSE

MSTXPMAXDCS=0,
object: BTS [BASICS] unit: see tables below range: 0..15 default: 0 Reference: 3GPP 45.008 GSM 05.05 GSM 04.08 GSM 03.22 GSM 12.10

Maximum transmission power for DCS 1800, this parameter defines the maximum transmission level a MS is allowed to use on a dedicated channel (TCH and SDCCH) in the serving cell. This parameter is relevant if the cell contains frequencies of the DCS1800 band. This info determines the value of the IE 'MS Power' in the first CHANNEL ACTIVATION message sent by the BSC for a call context (e.g. CHAN ACT for an SDCCH in case of call setup, or CHAN ACT for a new TCH in case of handover). In the 'MS Power' IEs of the following CHAN ACT messages as well as in the 'Power Command' IEs contained in the ASSIGNMENT COMMAND and HANDOVER COMMAND messages the allowed power level is additionally determined by the MS power capability (whichever is lower) which is provided by the MS in the IE 'MS classmark' in the CM SERVICE REQUEST message. Value range: DCS1800: 0..15 default: 0=30dBm (step size -2dBm) Note: - Increasing the entered value decreases the allowed transmit power. For details regarding the power classes and power control levels

167

MSTXPMAXGSM=5,
object: unit: range: default: BTS [BASICS] see tables below 2..15 5

MSTXPMAXPCS=0,
object: unit: range: default: BTS [BASICS] see tables below 0..15, 30, 31 0

please refer to the GSM-tables on the following pages. - If the feature frequencies of two different frequency bands are used in the cell (dual band concentric cells, or dual band standard cells, refer to parameters CELLTYP and CONCELL, see above), both the parameters MSTXPMAXGSM and MSTXPMAXDCS must be set, as both bands are used within the cell. This information is evaluated during call setup and for the complete-to-inner intracell handover decision. Maximum transmission power for GSM 900, this parameter defines the maximum transmission level a MS is allowed to use on a dedicated channel (TCH and SDCCH) in the serving cell. This parameter is relevant if the cell contains frequencies of the GSM900 band. Value ranges: GSM900: 2..15, default: 2=39dBm (step size -2dBm) GSMR: 2..15, default: 2=39dBm (step size -2dBm) For further information please refer to the explanation provided for the parameter MSTXPMAXDCS. Note: If the feature frequencies of two different frequency bands are used in the cell (dual band concentric cells, or dual band standard cells, refer to parameters CELLTYP and CONCELL, see above), both the parameters MSTXPMAXGSM and MSTXPMAXDCS must be set, as both bands are used within the cell. This information is evaluated during call setup and for the complete-to-inner intracell handover decision. Maximum transmission power for PCS 1900, this parameter defines the maximum transmission level a MS is allowed to use on a dedicated channel (TCH and SDCCH) in the serving cell. This parameter is relevant if the cell contains frequencies of the PCS 1900 band. Value range: PCS1900: 0..15,30,31(30=33dBm, 31=32dBm) default: 0=30dBm (step size -2dBm), For further information please refer to the explanation provided for the parameter MSTXPMAXDCS. Note: - If the feature frequencies of two different frequency bands are used in the cell (dual band concentric cells, or dual band standard cells, refer to parameters CELLTYP and CONCELL, see above), both the parameters MSTXPMAXGSM and MSTXPMAXPCS must be set, as both bands are used within the cell. This information is evaluated during call setup and for the complete-to-inner intracell handover decision.

168

25 W (24 dBm) 4 W (36 dBm) PCS 1900 Nominal Maximum output power 1 W (30 dBm) 0.05.GSM 900 and GSM 850 Power control level 0.. MS Power classes Power Control Levels GSM 400.Mobile station Power Classes Power class GSM 400 & GSM 900 & GSM 850 Nominal Maximum output power 1 2 3 4 5 -----8 W (39 dBm) 5 W (37 dBm) 2 W (33 dBm) 0.8 W (29 dBm) DCS 1800 Nominal Maximum output power 1 W (30 dBm) 0.05. MS Output power tables 169 .25 W (24 dBm) 2 W (33 dBm) from GSM 05.2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19-31 Nominal Output power (dBm) 39 37 35 33 31 29 27 25 23 21 19 17 15 13 11 9 7 5 DCS 1800 Power control level 29 30 31 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15-28 Nominal Output power (dBm) 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0 PCS 1900 Power Nominal Output Control Level Power (dBm) 22-29 30 31 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16-21 Reserved 33 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0 Reserved from GSM 05.

3 . these shall be used to report the next strongest identified cells in the other bands irrespective of the band used. with known and allowed NCC part of BSIC.0 the parameter PCCCHLDI is additionally used to enable or disable a paging overload prevention functionality.The MS shall report the two strongest cells. object: unit: range: default: BTS [BASICS] 1s 0. The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell.NMULBAC=0. This parameter is relevant for dualband configurations and specifies in which way the MS shall report the neighbour cells of the frequency bands used in the serving and neighbouring cells. Period of CCCH load indication. object: range: default: reference: BTS [BASICS] 0. this parameter corresponds to the 3GPP parameter MULTIBAND_REPORTING which is .The MS shall report the strongest cell.3 0 3GPP 45. it is recommended to disable this functionality by setting PCCCHLDI=0 (as this would lead to too many discarding of pagings) and to leave the PCH overload handling to the BSC (see parameter BTSOVLH in command SET BSC [BASICS]). If there are still remaining positions. with known and allowed NCC part of BSIC. If there are still remaining positions. Note: In BR7.e. If there are still remaining positions. 170 . the BTS has sent an OVERLOAD message to the BSC. The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode). thus indicating that one PAGING COMMAND could not be placed in a paging queue and had to be discarded). these shall be used to report the next strongest identified cells in the other bands irrespective of the band used. 2 . the BTS discards all PAGING COMMANDs that contain an IMSI.e. This is done because an IMSI needs twice the space than a TMSI in the BTS paging queues and is thus an attempt to effectively prevent further overload situations by removing those messages that have the biggest impact on the load in the PCH queues. with known and allowed NCC part of BSIC. these shall be used to report the next strongest identified cells in the other bands irrespective of the band used. The CCCH LOAD INDICATION is only sent to the BSC if the CCCH load threshold TCCCHLDI (parameter description see below) is reached. irrespective of the band used. 1 . in each of the frequency bands in the BA list. If PCCCHLDI is not set to ‘0’. see below). triggers the following mechanism: as long as the PCH load is still above the threshold defined by the parameter TCCCHLDI (see below). Attention: if TMSI Reallocation is disabled in the network (i. excluding the frequency band of the serving cell.018 PCCCHLDI=255. The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . in each of the frequency bands in the BA list. this value indicates the time distance between two CCCH LOAD INDICATION messages sent to the BSC (see also parameters RACHBT and RACHLAS).The MS shall report the three strongest cells.. paging is exclusively done with the IMSI).Normal reporting of the six strongest cells.255 255 Number of multi band cells. excluding the frequency band of the serving cell.008 3GPP 44. in each of the frequency bands in the BA list. a BTS paging overload situation (i. Please see also parameter UMTSSRHPRI (same command.. Possible values: 0 . with known and allowed NCC part of BSIC. The value PCCCHLDI=0 indicates that the CCCH LOAD INDICATION is not repeated but sent only once. excluding the frequency band of the serving cell.

10=5.5 sec .0 171 . This parameter. i. This parameter only has to be set if CRESPARI is set to ‘1’. Only those neighbour cells whose NCC (please see also parameter BSIC) is indicated as ‘permitted’ in the ‘NCC permitted’ IE may be included in the MEASUREMENT REPORTs in busy mode. object: range: default: Reference: BTS [BASICS] 0.22 Penalty time..10 2=1. every ‘1’ bit indicates that the NCC corresponding to the bit position is allowed..5 sec 2. in this case the MS cannot report anything).08 GSM 02. Note: The effective penalty time value is (20s + PENTIME*20s) PLMN permitted. together with the list of the allowed neighbour cell BCCH frequencies) or on the SACCH (SYSTEM INFORMATION TYPE 6). if a specific cell has two cells using the same BCCH frequency or a directly adjacent BCCH frequency (whose “side-ramp” the MS might misinterpret as the signal of the allowed BCCH frequency due to co-channel interference) in the geographical neighbourhood..255 255 GSM 03. Note: PLMNP has no influence on cell reselection.03 GSM 04. The 8-bit string is used as a ‘bit-map’. For further details please refer to the parameter CRESPARI. contained in the IE ‘SI 4 Rest Octets’ on the BCCH (SYSTEM INFORMATION TYPE 4). “NCC Permitted” is included in the SYSINFO 2 only in order to inform the MS early enough which cells are allowed for measurement reporting when it switches to ‘busy’ mode. object: unit: range: BTS [BASICS] 0. 4 and 1 will be reported. is one of the necessary input values for the calculation of C2.. The decimal value entered for PLMNP is sent to the MS as a binary 8-bit string “ NCC permitted “ on the BCCH (SYSTEM INFORMATION TYPE 2. object: unit: range: BTS [BASICS] 20s 0.e.11 GSM 05.31 31= TEMPOFF ignored default: 0 Reference: 3GPP 45. “NCC permitted” allowed NCCs 0 7 1 6 0 5 1 4 0 3 0 2 1 1 0 0 PLMNP=255. default: PUREBBSIG44CONF parameter cancelled in BR8.0 sec 3=1.0 sec <NULL> 5= 2.08 PNOFACCH=5.008 GSM 03. this parameter specifies period (repetition rate) for the FACCH notification for a given ASCI call. Period for Notification on FACCH.PENTIME=0. this parameter corresponds to the IE ‘NCC Permitted’. the MS will only report the one with the correct NCC (unless the interference leads to an unsuccessful BSIC decoding. the MS might attempt a cell reselection to a cell with an NCC which is not included in “NCC Permitted”.5 sec Thus PLMNP=82 means that the only neighbour cells with the NCCs 6. Thus only to these cells a handover is actually possible! In other words. sets the duration for which the temporary offset is applied.. Example: PLMNP=82Dec corresponds to the to binary value 1010010.

the 3G serach mode is determined by the parameter Qsearch_C_Initial (parameter QSRHCINI.008 3GPP 44.008 3GPP 44. the neighbour cell shall be considered for cell selection/reselection. then 3G cells shall be considered for handover neighbour cell monitoring. As long as no MEASUREMENT INFORMATION message has been received after the MS/UE has entered the ‘connected mode’.The value ALWAYS means the Mobile shall always consider 3G neighbours cells for cell selection/reselection. object: range: default: reference: BTS [BASICS] QSEARCHI.QSRHC=NEVER. If the value QSEARCHI is selected.018 QSRHI=NEVER.018 Qsearch Connected. An equivalent 3G search threshold does also exist for the idle mode: Qsearch Idle (paremeter QSRHI. the initial threshold value to be used for connected mode is defined by the parameter Qsearch_C_Initial (see parameter QSRHCINI). object: range: BTS [BASICS] UMDB98 UMDB94 UMDB90 UMDB86 UMDB82 UMDB78 UMDB74 ALWAYS OMDB78 OMDB74 OMDB70 OMDB66 OMDB62 OMDB58 OMDB54 NEVER default: NEVER reference: 3GPP 45. .The value NEVER means the Mobile shall not consider 3G neighbours cells for cell selection/reselection at all. . In other words.018 QSRHCINI=QSEARCHI. this parameter corresponds to the 3GPP parameter Qsearch_l which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater and defines a threshold condition which enables the searching for 3G cells with regard to cell selection/reselection (in idle mode). if the threshold condition defined by QSRHC is fulfilled for the serving (2G) cell. see below). the actual threshold is defined by the parameter QSRHI (see below). in other words. If it does. QSRHI defines the default value of the attribute QSRHCINI (see above). 172 . that is valid after receipt of the MEASUREMENT INORMATION message on the SACCH.The values OMDBxx (=over minus xxdB) define the threshold as follows: When the level of the serving cell has exceeded the “xx dB” threshold value. Q Search Idle. which is then replaced by the threshold Qsearch_C. then 3G cells shall be considered for cell selection/reselection. if the threshold condition defined by QSRHI is fulfilled for the serving 2G cell. object: range: BTS [BASICS] UMDB98 UMDB94 UMDB90 UMDB86 UMDB82 UMDB78 UMDB74 ALWAYS OMDB78 OMDB74 OMDB70 OMDB66 OMDB62 OMDB58 OMDB54 NEVER default: NEVER reference: 3GPP 45. Q search Connected initial. It defines a threshold condition which enables the searching for 3G cells in connected mode. The parameter values have to be considered as described for the parameter QSRHC (see above).The values UMDBxx (=under minus xxdB) define the threshold as follows: When the level of the serving cell has dropped below the “xx dB” threshold value. The parameter values have to be considered as follows: . This threshold is valid as long as the MS/UE has not entered the connected mode. which is sent to the MS within the first MEASUREMENT INFORMATION message. see below). this parameter corresponds to the 3GPP parameter Qsearch_C_Initial which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater and indicates the initial value to be used in connected mode before the MS receives QSRHC (Qsearch_C. the neighbour cell shall be considered for cell selection/reselection.008 3GPP 44. ALWAYS QSEARCHI 3GPP 45. this parameter corresponds to the 3GPP parameter Qsearch_C which is sent to the MS/UE within the MEASUREMENT INFORMATION messages on the SACCH. see above) in the MEASUREMENT INFORMATION message on the SACCH. .

checks for block CRC errors and measures the delay of the RACH burst to determine the MS-BTS distance. If the received signal level is below the threshold defined by the parameter RACHBT.The value entered for parameter RACHBT is not only relevant for the CHANNEL REQUEST message on the RACH but also for the HANDOVER ACCESS message on the FACCH! The level evaluation of RACHBT against the receive level of the handover access burst on the FACCH is exactly the same as for the RACH. the received RACH message is regarded as invalid and counted by NINVRACH subcounter 2 (‘excessive distance’).e. i. e. Five of the mentioned flags from the layer 1 evaluation are regarded as ‘killer criteria’ (RSSI. measures the signalto-noise ratio (SNIR). the received RACH message is regarded as invalid and counted by NINVRACH subcounter 1 (’signal level too weak’). 2. If the ‘block CRC error’ flag has the value ‘1’. Together with the decoded signal itself. evaluates a soft decision criterion (SOVA). Notes: . the received RACH message is regarded as invalid and counted by NINVRACH subcounter 3 (’other causes’). 3. if one of these flags was set to ‘1’ by the layer 1 SW subsystem. it measures the receive level and checks if it exceeds a hardcoded minimum threshold (RSSI level. the task of the layer 1 SW subsystem is to evaluate the received signal with respect to specific criteria. On the basis of the flags received. The general purpose of this parameter is to define a minimum level criterion a received RACH signal must fulfil to be regarded as a real RACH access. If. As even without any MS RACH access there are always at least some ‘noise’ signals on the RACH. nor will it be counted by the PM counter NINVRACH (Number of invalid RACH messages per cause). the results of these checks are forwarded in form of a set of flags to the BTS call handling SW subsystem. tries to decode the training sequence.. In this case the signal will neither lead to the transmission of a CHANNEL REQUIRED. SNIR. Thus. not equal to RACHBT!). These flags indicate the results of the BTS layer 1 evaluation (the value ‘1’ indicates: criterion not fulfilled) and are the basis for the BTS call handling SW subsystem to determine whether the received signal can really be regarded as a successful RACH access or not. the setting of 173 . the BTS call handling subsystem evaluates three further criteria to check whether a RACH signal is to be regarded as ‘valid’ or ‘invalid’ (the numbering defines sequence of the checks): 1. the BTS call handling subsystem classifies the received signals either as ‘noisy’ or ‘not noisy’.127 109 RACH busy threshold. To understand the mechanism better. it is required to describe the functional sequence of RACH signal evaluation in alittle more detail: Functional sequence of RACH signal evaluation: The BTS evaluates the RACH signals in two main stages: 1) The Um layer 1 SW subsystem of the BTS continuously observes the signals received on the RACH slots. which leads to an immediate discarding of the received signal. SOVA.RACHBT=109. If none of the aforementioned conditions applies. checks the Convolution Code.g. the call handling subsystem regards the received signal as ‘noisy’. Conv Code and training sequence). If the delay of the RACH burst indicates that the MS-BTS distance is greater than the distance defined by the parameter EXCDIST (see command SET BTS [OPTIONS]). defines a threshold for the signal level on the RACH. however the mentioned five flags assume the value ‘0’ (criterion fulfilled). the RACH access is regarded as ‘valid’ and leads to the transmission of a CHANNEL REQUIRED message towards the BSC. object: unit: range: default: BTS [BASICS] -1dBm 0.

174 . The BTS reports these measurements to the BSC according to the setting of the parameter PCCCHLDI (see above). also the BTS cannot correctly decode any uplink SACCH frames anymore (because the MS has stopped transmitting them) and it is just a question of time when the radio link counter in the BTS (see RDLNKTBS) reaches ‘0’. successful decoding to an increase by 2. .reporting rate (see parameter PCCCHLDI = CCCH load indication period) RACH load averaging slots. In this case a CONNECTION FAILURE INDICATION (BTS->BSC) is sent and indicates the loss of the dedicated connection (call drop).0. In such a situation..15 0 = counter value 4 15 = counter value 64 default: 4 Reference: 3GPP 45. The ‘radio link timeout’ value is the start point for the ‘S’ counter in the MS which is in effect if the mobile is in ‘dedicated’ (or ‘busy’) mode.08 RACHBT also has an influence on the handover success rate. In other words: RACHLAS defines the averaging window for the RACH load measurements. Unsuccessful decoding of SACCH messages by the transceiver lead to a decrease of the ‘S’ counter by 1. Notes: . Radio link timeout.Please note that. defines the number of RACH bursts over which RACH measurements are performed by the BTS (see also parameter RACHBT). It is used by the MS to calculate the maximum value of the radio link counter (‘S’ counter) in the MS which is needed to detect a radio link failure in the downlink (a similar counter is realized in the BTS for the uplink. starting from BR8..measurement period (see parameter RACHLAS = RACH load averaging slots) . the value entered for this parameter determines the value of the parameter RADIO_LINK_TIMEOUT which is sent on the BCCH (SYSTEM INFORMATION TYPE 3) or on the SACCH (SYSTEM INFORMATION TYPE 6) in the IE ‘Cell Options’. If the ‘S’ counter reaches 0.RACH busy threshold (RACHBT) .If ‘Call Re-Establishment’ (see parameter CREALL) is enabled a low value of radio link time-out increases the number of call reestablishments because a decrease of RDLNKTO may lead to an earlier declaration of radio link failures. object: range: BTS [BASICS] 0.008 GSM 04. Please see also parameter TCCCHLDI. object: unit: range: default: BTS [BASICS] 1 RACH burst 102-65535 204 RDLNKTO=4. this parameter can also be separately managed for different service types using the parameters SGxxPCPAR (see command SET PWRC).RACHBT is also relevant for the BTS load recognition procedure for the RACH which is controlled by the O&M-parameters . see parameter RDLNKTBS (SET PWRC)).RACHLAS=204. Rule: The CCCH LOAD INDICATION reporting period should always be greater than the averaging time: RACHLAS ≤ PCCCHLDI. .64. of course. The maximum value S0 of the S-counter in the MS is calculated as follows: S0 = 4 + 4∗ RDLNKTO Its range is 4. the MS regards the dedicated radio connection as failed and stops any further transmission on the dedicated channel.

list of the BCCHs used by the configured neighbour cells as defined in the ADJC and ADJC3G objects).018 Report type. Contents of ENHANCED MEASUREMENT REPORT An ENHANCED MEASUREMENT REPORT message contains (among others) the following main data: • BA_USED = 2G BCCH Allocation (BCCH list of 2G neighbours) • 3G_BA_USED = 3G BCCH Allocation (BCCH list of 3G neighbours) 175 . reporting is performed on the Neighbour Cell List. which is the initial basis for the measurements. The setting of this parameter is reflected in the IE REPORT_TYPE which is sent to the MS/UE in connected mode within the MEASUREMENT INFORMATION message via the SACCH.008 3GPP 44.While in case of normal reporting only 6 neighbour cells can be reported within one MEASUREMENT REPORT message.EMR reports provide additional measurement values such as the Bit Error probability (BEP) of the serving cell channel. which is the concatenation of the GSM Neighbour Cell list and the 3G Neighbour Cell list (if any). the ‘number of correctly received downlink blocks’ which can be used to determined the downlink Frame Erasure Rate (FER) which is monitored by suitable PM counters in the BTS . this parameter indicates to the mobile to use the ENHANCED MEASUREMENT REPORT or MEASUREMENT REPORT messages for measurements reporting. Further information the MS/UE needs for enhanced measurement reporting is sent to the MS/UE within the SYSTEM INFORMATION TYPE 2quater via the BCCH.With EMR a reporting is possible for both 'valid' and 'invalid' BSICs. Reporting with Enhanced Measurement Reporting (EMR) When in dedicated mode or group transmit mode. Enhanced measurement reporting is only supported by particular mobiles and comprises new features and functionalities: . These messages contain measurement results about reception characteristics from the current cell and from neighbour cells. from information received a) on the BCCH in SYSTEM INFORMATION TYPE 2 and optionally SI2bis and/or SI2ter messages (SI2quater messages may add information for the GSM Neighbour and provide the 3G Neighbour Cell list) and b) on the SACCH in System Information 5 and optionally 5bis and/or 5ter messages (MEASUREMENT INFORMATION messages may add information for the GSM Neighbour Cell List and provide the 3G Neighbour Cell list). The Neighbour Cell list may contain up to 96 Neighbour Cells. EMR can report much more than 6 neighbour cells within one ENHANCED MEASUREMENT REPORT message. ENHANCED NORMAL 3GPP 45. For reporting with the MEASUREMENT REPORT message. . For reporting with the ENHANCED MEASUREMENT REPORT message.REPTYP=NORMAL. ENHANCED MEASUREMENT REPORT messages are sent by the MS with a defined periodicity which depends on the used channel type and the mode the MS/UE is currently in (see 3GPP 45. the MS/UE regularly sends either MEASUREMENT REPORT or ENHANCED MEASUREMENT REPORT messages to the network (the uses ENHANCED MEASUREMENT REPORT messages instead of MEASUREMENT REPORT messages if this is indicated by the parameter REPORT_TYPE and if at least one BSIC is allocated to each BA (list) frequency). object: range: default: reference: BTS [BASICS] NORMAL.008 for further details). The MS/UE derives the BA list (BA = BCCH Allocation. reporting is performed on two separate neighbour lists: the BA (list) and the 3G Neighbour Cell List (for a multi-RAT MS).

018) For each of the priority levels above. the cells are reported that have the highest sum of the reported value (RXLEV or as defined in subclause 8.If the number of valid cells is less than indicated the unused positions in the report are left for the lower priorized cells.BCCH frequency number.NBR_RCVD_BLOCKS. even if one of these cells with a lower value would fit into the report. the average over the reporting period of the mean and ‘coefficient of variation’ of the Bit Error Probability (BEP) measures.RXQUAL_FULL. then no cell with a lower value shall be reported.• REPORTING_QUANTITY = Type of reported value (parameter FDDREPQTY. If a cell can not be reported due to lack of space in the report. downlink RXLEV value of serving cell .1. however. . This offset parameter. downlink RXLEV value of neighbour cell Neighbour cell ordering Within the message part that contains the neighbour cell measurement data the neighbour cell measurements are listed in a defined priority order: 1) the number of strongest valid GSM cells with a reported value equal or greater than the reporting theshold for its band (see parameter FDDREPTH) in the frequency band of the serving cell 2) the number of strongest valid GSM cells with a reported value equal or greater than the reporting theshold for its band (see parameter FDDREPTH) in each of the frequency bands in the BA list excluding that of the serving cell 3) the number of best valid cells and with a reported value equal or greater than XXX_REPORTING_THRESHOLD (see parameter FDDREPTH). then additionally the non-reported value (from CPICH Ec/No and CPICH RSCP) must be equal or greater than FDD_REPORTING_THRESHOLD_2 (see parameter FDDREPTH2). .If there is not enough space in the report for all valid cells. 176 . validity or acces technologies (see 3GPP specification 44. although for both the same abbreviation (EMR) is used.RXLEV_NCELL.DTX used flag.BSIC . downlink RXQUAL value of serving cell . 4) Remaining cells of lower priorities. in each supported other radio access technology/mode in the 3G neighbour cell list.5) and the parameter XXX_REPORTING_OFFSET for respective radio access technology (see parameter FDDREPO). see above) • Serving cell measurement data . the following rules apply: . relative frequency number within BA list .MEAN_BEP and CV-BEP. does not affect the actual reported value. Note: ENHANCED MEASUREMENT REPORT is not to be mixed up with EXTENDED MEASUREMENT REPORT. indicates if DTX was used in uplink in the measurement period . according to the value of the parameters XXX_MULTIRAT_REPORTING (see parameter FDDMURREP). number of correctly decoded downlink blocks in the measurement period (this value is used by the BTS to calculate the downlink FER) • Neighbour cell measurement data . When the radio access technology is UTRAN FDD.RXLEV_VAL.

an equivalent parameter is broadcast on the PBCCH for GPRS mobiles to allow a separate management of cell selection and cell reselection for GPRS. Note: If a PBCCH is configured (see parameter CREATE CHAN for TCH with GDCH=PBCCH). object: unit: range: BTS [BASICS] 1 dB 0. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3 and 4) in the IE ‘Cell Selection Parameters’.008 GSM 04.63 0 = less than -110dBm 1 = -110dBm to -109dBm 2 = -109dBm to -108dBm . Thus the number of handover requests may be reduced.and non-GPRS-mobiles. 62 = -49dBm to -48dBm 63 = greater than -48dBm default: 6 Reference: 3GPP 45. 177 ..08 GSM 03. This parameter corresponds to the 3GPP parameter RXLEV_ACCESS_MIN which is used together with other parameters to define the path loss criterion C1 for cell selection and reselection (see parameter CELLRESH).. Setting RXLEVAMI to a high value means that only those MSs attempt an access to the cell which are in a location with good coverage conditions..RXLEVAMI=6.22 Minimum received level at the MS required for access to the network on the RACH. This parameter is GRXLAMI (see command CREATE PTPPKF).

of busy SDCCH subslots* no. the BSC moves the TCH/SD from the TCH/SD_POOL to the SDCCH_BACKUP_POOL and thus extends the SDCCH capacity by 8 additional SDCCH subslots. The following flow diagram shows the exact process that is triggered by an SDCCH request: 178 . of SDCCH subslots in unlocked/enabled* ∗ 100 * Note: the calculation always considers the total amount of SDCCH subslots from both the SDCCH_POOL and the SDCCH_BACKUP_POOL ! Whenever the BSC receives a seizure request for an SDCCH the BSC calculates the SDCCH traffic load and compares it to the to the threshold SDCCHCONGTH. SDCCHCONGTH determines the cell-specific trigger threshold for the percentage of busy SDCCHs which initiates the moving of a TCH/SD from the TCH/SD_POOL (see parameter setting CHPOOLTYP=TCHSDPOOL in command CREATE CHAN) to the SDCCH_BACKUP_POOL.SDCCHCONGTH=70. If the SDCCH traffic load exceeds SDCCHCONGTH. object: unit: range: default: BTS [BASICS] 1% 70. see parameter INTCLASS in command SET BTS [INTERF]) is moved first. The TCH/SD with the best quality (determined from the idle TCH measurements.. this parameter is associated to the feature “Smooth channel modification” (for further details please see command CREATE CHAN for TCH/SD) and defines the SDCCH load threshold which causes the move of a TCH/SD from the TCH/SD_POOL to the SDCCH_BACKUP_POOL and vice versa.100 70 SDCCH congestion threshold. The percentage of busy SDCCHs is calculated as follows: SDCCH traffic load [%] = no.

This is achieved by simply adding the TAADJ value to the measured timing advance value – the resulting timing advance value is then more accurate than just the measured one. suitable measurements must have been made before. If F2ONLY900 is selected only phase2 mobiles can be used. it does not move a TCH/SD to the SDCCH_BACKUP_POOL to satisfy this request! Instead. If EXT900 is selected the GSM base band is still usable for phase1 mobiles. Note: SDCCHCONGTH has no relevance for the SDCCH allocation process itself. Timing advance adjust. It is up to the operator to make sure that the parameter value is set in correspondence with the real propagation delay conditions in the BTSE. object: unit: range: default: BTS [BASICS] 100ns 0.e. The values GSMDCS and GSM850PCS must be set if the cell is to be configured with TRX frequencies of two different frequency bands (dual band concentric cells.) EXT900 (GSM mixed band) GSMR (railway GSM). To set this parameter correctly.100.0) <NULL> (BTS SW < BR7. object: range: BTS [BASICS] BB900 (GSM baseband) DCS1800 F2ONLY900 (GSM ext. phase1 mobiles are not supported. i. bd. PCS1900 GSMDCS GSM850 GSM850PCS Reference: GSM 04. however. can only be used for traffic purposes by phase2 mobiles. the extension band.The parameter SDCCHCONGTH is also evaluated during SDCCH release in order to decide whether a TCH/SD currently in the SDCCH_BACKUP_POOL can be moved back to the TCH/SD_POOL. i. the BTSE internal propagation delay must be known. see above). <NULL> 0 (BTS SW ≥ BR7.e. TAADJ=0. no matter whether additional SDCCH subslots are available in the SDCCH_BACKUP_POOL or not.e. Attention: the calculation performed during the SDCCH release procedure is different from the formula shown above! For further details please refer to the descriptions provided for the parameter TGUARDTCHSD.08 System Indicator. see command CREATE RFLOOP). The idea of this correction term is to consider the propagation delay on the BTSE internal signal path for the determination of the real timing advance value. For this reason the BSC calculates the current SDCCH traffic load and compares it to SDCCHCONGTH. refer to parameters CELLTYP and CONCELL. or dual band standard cells. this parameter allows to enter a correction term for the BTSE internal timing advance measurements (similar to the parameter RXLECADJ.. a subslot from the non-TCH/SD SDCCHs). if the BSC receives an SDCCH request. for all incoming SDCCH requests the BSC first tries to allocate an SDCCH subslot from the SDCCH_POOL (i.0) 179 . indicates the frequency band used by the traffic channels. SYSID=BB900.

(**) depends on the number of paging groups. (RACH busy threshold = parameter RACHBT. For further details please refer to 180 .‘RACH Busy Count’. the BTS sends a CCCH LOAD INDICATION. but it is not predictable which types of MS IDs will be received furtheron. If the calculated value exceeds TCCCHLDI. . paging queue place) provides the buffer space for at least 2 MS IDs .The receipt of a CCCH LOAD INDICATION does not trigger any overload mechanism in the BSC.e.TCCCHLDI=100. MS IDs) that can still be stored in a paging queue. of seized PCH blocks ∗ 2 – no.(*) MS ID = IMSI or TMSI .‘RACH Access Count’.e.depending on the MS IDs type.A ‘PCH block’ can also be called a place in the BTS paging queue.BUT: In BR7. each paging queue contains 2 blocks.0 the parameter TCCCHLDI is additionally used for a paging overload prevention funtionality which is enabled by the parameter PCCCHLDI (see above).. This IE contains the following parameters: . which includes the ‘RACH Load’ IE.100 100 Threshold for CCCH load indication. This message is used to make the current PCH load and RACH load visible on the Abis interface. of PCH blocks seized by only 1 MS-ID) This calculation is based on the fact that at least one further MS ID can be added in a paging queue place. for each paging group one queue is available. This IE contains the parameter ‘Paging Buffer Space’. of PCH blocks seized by only 1 MS ID* 2 ∗ Total number of PCH blocks available** ∗ 100 Notes: .‘RACH Slot Count’. Case b): RACH load exceeds TCCCHLDI: The BTS calculates the RACH load as follows: RACH load [%] = no. object: unit: range: default: BTS [BASICS] 1% 0. more MS IDs can be buffered. of seized PCH blocks ∗ 2 – no. The BTS calculates this value as follows: Remaining buffer space for PAGING COMMANDs (MS IDs) = 2 ∗ Total no. indicates the number of RACH bursts that were received with a level higher than (RACH busy threshold + 35dB). of busy RACH slots in the RACH load measurement period* Total no. of PCH blocks available – (no. the guaranteed number of PAGING COMMANDs (i. i. which already contains 1MS ID . Case a): PCH load exceeds TCCCHLDI: The BTS calculates the PCH load as follows: PCH load [%] = no. The BTS sends the CCCH LOAD INDICATION if either a) the PCH load (in %) exceeds the threshold TCCCHLDI or b) the RACH load (in %) exceeds the threshold TCCCHLDI. each block (resp. which includes the ‘Paging Load’ IE. of RACH slots in the RACH load measurement period* ∗ 100 Note: (*) RACH load measurement period = RACH averaging slots (parameter RACHLAS) If the calculated value exceeds TCCCHLDI. which in turn depends on the CCCH configuration and the setting of NBLKACGR and NFRAMEPG. . this value is a threshold used by the BTS to inform the BSC about the load on the CCCH by sending the Abis RSL message CCCH LOAD INDICATION. see above). corresponds to the abovementioned ‘RACH load measurement period’ (= parameter RACHLAS) . indicates the number of error-free decoded access bursts received on the RACH during the RACHLAS period. Notes: . the BTS sends a CCCH LOAD INDICATION. these events are in any case signaled in separate CCCH LOAD INDICATION messages. Even if both conditions occur simultaneously.

The parameter values express a value in dBm DBxx = xxdBm (e. this parameter corresponds to the 3GPP parameter TDD_Qoffset which is broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2ter and SI2quater and is related multiRAT mobiles.008 TDDREPTH=RXLEV_00. so with this setting a 3G Mobile will always change to the 3G network if any acceptable 3G cell is available. RXLEV_12.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . DB20 = 20dB) The value ALWAYS indicates an infinite negative (-∞ dB) offset. it is used by the UE for the cell re-selection algorithm from GSM to UTRAN. this parameter corresponds to the 3GPP parameter TDD_REPORTING_OFFSET and is broadcast on the BCCH in the SYSTEM INFORMATION 2quater.018 3GPP 45. RXLEV_36. TDDREPO=DB00. RXLEV_06 = -115 dBm + 6dB = -109 dBm) For further details please refer to the description of parameter FDDREPTH (see above). object: BTS [BASICS] unit: 10dB range: 0.018 3GPP 45. object: range: BTS [BASICS] RXLEV_00.7. 7=∞ default: 1 Reference: 3GPP 45. It defines a fixed offset to be applied to all reported TDD 3G neighbour cells.TDDMURREP=0. For further details please refer to the parameter CRESPARI..008 TEMPOFF=1. The parameter values express an RXLEVvalue in dB RXLEV_xx = xxdB (e.g. NEVER default: RXLEV_00 reference: 3GPP 44.008 the description of this parameter. The parameter values express a value in dB MDBxx = . this parameter corresponds to the 3GPP parameter TDD_MULTIRAT_REPORTING which is . The UE is thus instructed to report. Usually 6 neighbour cells can be reported within one MEASUREMENT REPORT message.g. this number of 3G neighbour cells. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter FDDQMI (see above). MDB20 = -20dB) DBxx = xxdB (e. TDD multiRAT reporting. is one of the necessary input values for the calculation of C2.xxdB (e. RXLEV_30.018 3GPP 45. DB10 = 10dBm) For further details please refer to the description of parameter FDDREPO (see above). It defines a level offset by which the RLA_C value of an UTRAN FDD neighbour cell must exceed the RLA_C of the serving GSM cell before the UTRAN neighbour cell is considered for cell reselection from GSM to UTRAN. TDD Reporting Threshold. if available. This parameter only has to be set if CRESPARI is set to ‘1’.g. Temporary offset. It defines threshold which TDD 3G cell has to exceed in order to be reported in Enhanced Measurement Report.018 3GPP 45.008 TDDQO=DB00..008 GSM 03. Which value should be set for this parameter strongly depends on the environment of the cell (BTS). RXLEV_24. This parameter. It applies a negative offset to C2 for the duration of the penalty time. contained in the IE ‘SI 4 Rest Octets’ on the BCCH (SYSTEM INFORMATION TYPE 4). object: range: BTS [BASICS] ALWAYS MDB28 MDB24 MDB20 MDB16 MDB12 MDB08 MDB04 DB00 DB04 DB08 DB12 DB16 DB20 DB24 DB28 default: DB00 reference: 3GPP 44. The default value of ‘0’ only makes sense in areas without any 3G TDD neighbours (no ADJC3G object created for this BTS).g. The more really relevant 3G TDD cells are available. TDD Q offset.22 181 . RXLEV_06.3 0 3GPP 44. It indicates the number TDD UTRAN cells the UE shall include in the MEASUREMENT REPORTs. TDD Reporting Offset. The value must therfore be set considering how many 2G neighbour cells shall be reported in any case.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode). the higher the value should be set. RXLEV_18. object: range: default: reference: BTS [BASICS] 0. this parameter corresponds to the 3GPP parameter TDD_REPORTING_THRESHOLD and is broadcast on the BCCH in the SYSTEM INFORMATION 2quater. object: range: BTS [BASICS] DB00 DB06 DB12 DB18 DB24 DB30 DB36 DB42 default: DB00 reference: 3GPP 44.

DB15. DB425. MDB025. MDB25. BCCHTRX NONE TX diversity time shift except. MDB1. A multi-RAT MS is allowed to extend this period to 13 seconds. SCH BCCHTRXTS0. MDB125. The MS attempts to demodulate the SCH on the BCCH carrier of as many surrounding cells as possible. 182 . These frames are termed "search" frames.sent to the MS/UE within the MEASUREMENT INFORMATION messages (in connected mode).g. if the neighbour cell list contains cells from other RATs and if indicated by the parameter 3G_SEARCH_PRIO.008 UMTS search priority. DB3705. MDB425. MDB2. DB225. MDB175.broadcast on the BCCH in the SYSTEM INFORMATION TYPE 2quater (in idle mode) and . object: range: default: reference: BTS [BASICS] TRUE. DB5 NONE TX diversity time shift parameter. see command SET BTS). at least once every 10 seconds. MDB325. TXDIVTSPAR=NONE. object: range: default: BTS [BASICS] NONE. and as a minimum. MDB225. DB05. and to decode the BSIC as often as possible. if the searching time can be longer than the normal value (13s instead of 10s ). i. default: UMTSSRHPRI=TRUE. in the case of TCH/F. The parameter 3G_SEARCH_PRIO is considered during BSIC decoding of surrounding neighbour cells of different radio access technologies. DB1. MDB15. this parameter parameter allows to configure time slots or logical channels which are excluded from being sent in TX Diversity Time Shift mode. indicates if a mobile may search 3G cells when BSIC decoding is required. this parameter defines the time shift of the TX signals of master and slave CU. DB3. DB35. DB275. DB0. MDB375. MDB35. object: range: BTS [BASICS] MDB5. The MS uses at least 4 spare frames per SACCH block period for the decoding the BSICs (e. DB325.TXDIVTSEXCPT=NONE. DB2. DB075. this parameter corresponds to the 3GPP parameter 3G_SEARCH_PRIO which is .018 3GPP 45. DB45. DB4. MDB4. MDB3. four idle frames per SACCH block period). MDB05. MDB075. DB025. MDB475. The parameter is not relevant if ETXDIVTS parameter is set to FALSE.e. DB125. DB475. DB25. MDB45. The MS gives priority for synchronisation attempts in signal strength order and considering the parameter MULTIBAND_REPORTING (parameter ENMU. DB175. MDB275. FALSE TRUE 3GPP 44.

e.5∗mean no. of hopping frequencies on DMA layer ∗ 100 * Mean no. However. one cell of the BTSM carries a high traffic volume. a reuse of MAIOs cannot be avoided.g. as DMA is used mainly in site configurations where the number of TRXs is higher than the number of frequencies used in the Mobile Allocation of the frequency hopping system. please refer to the explanations given for the command CREATE CBTS.e. co-channel interference and adjacent channel interference as good as possible. the more probable a MAIO reuse and thus the higher the risk of interference will be. DMA is a feature which is used in networks with a 1/1 reuse (i. The more traffic is managed in the other cells. measured by the BTS) as follows: BQP = P(FER > FERmax) In other words. 2) The Effective Fractional Load EFL represents the ‘Traffic volume (Erlang) per hopping frequency’ and is calculated by the formula EFL [%] = Mean no. during TCH allocation. of busy TCH on DMA layer * 8 ∗ Total no. the interference can be kept acceptably low if e.g. For further details about DMA. as an increase of traffic in the cells always means an increase of the overall interference level. The DMA algorithm manages the pool of available MAIOs/timeslots on a BTSM (site) level and tries to avoid. The QoS requirement is still fulfilled if the BQP does not exceed a configurable BQP threshold: BQP ≤ BQPmax The BQP threshold BQPmax is defined by the parameter ACBQPMAX (see parameter listing below).Setting the cell specific parameters for DMA Admission Control < With this command all cell specific attributes related to the feature ‘Admission Control’ which is associated to the feature ‘Dynamic MAIO Allocation’ (DMA). The benefit of DMA becomes mainly evident in case of inhomogenuous traffic distribution among the cells of the same site. defined by the ‘Bad Quality Probability’ (BQP) and 2) the load criterion ‘Effective Fractional Load’ (EFL). The explanation of these two indicators is as follows: 1) The Bad Quality Probability BQP is a value that estimates the probability for a speech call to suffer from bad quality and is calculated from the Frame Erasure Rate (FER. i. the capacity enhancement is limited by 1) a QoS requirement which is. busy FR + 0. The FER maximum threshold FERmax is defined by the parameter ACFERMAX (see parameter listing below). The capacity enhancement of DMA is achieved by an intelligent sharing the channel resources of the cells belonging to the same BTSM. the same frequencies are used for the hopping TRXs in all cells). As described in the CBTs object. busy HR 183 . but. while the other two cells serve lower traffic figures. the BQP is the probability (P) that the FER exceeds a certain maximum theshold.this is especially relevant in networks with a tight frequency reuse (e. Purpose and principle of the feature ‘DMA Admission Control’ From the operator point of view the a network is usually planned in such a way that a maximum capacity is achieved at an acceptable quality of service (QoS) . 1/1). of busy TCH on DMA layer = Mean no. for DMA.

one CFHSY can be created per frequency band).If the EFL is higher than the configurable maximum EFL threshold ‘max EFL_DMA’ (see parameter ACMAXEFLDMA).e. . admission control was only based on ‘hard blocking’ (which means that a TCH request is rejected only no TCH is available in the BTS). 184 . in releases starting from BR8. non-AMR). if the BQP exceeds a configurable threshold for a particular EFL. new call requests are rejected to keep the interference low enough to ensure an acceptable speech quality for the already established calls. also DMA Admission Ccontrol (DMA AC) is only applicable to these service layers.g. the AC decision algorithm in the BTS checks the EFL and BQP conditions in a way as indicated in the table below: Explanation: .While in releases < BR8. the new call setup on the DMA layer is admitted in any case. Remark: The evaluation of the ‘soft blocking’ criteria (and thus the rejection of TCH requests in case these criteria are fulfilled) is only performed for call setups in the serving cell. the new call setup on the DMA layer is rejected in any case. rejection of new TCH requests) can be also based on ‘soft blocking’ if the site configuration features DMA service layers.0 admission control (i.0.If the EFL is lower than or equal to the configurable maximum EFL threshold ‘min EFL_DMA’ (see parameter ACMINEFLDMA). see further details below). the BTS can (and actually does) check the DMA AC soft-blocking criterion using the AC decision algorithm. All types of incoming inter-cell handovers are served by idle TCHs (if available) even if the DMA layers of the cell are soft-blocked for call setup. Due to the fact that DMA is only applicable to ‘speech only’ service layers (AMR. The rejection of a new call request based on the BQP criterion is called ‘soft blocking’. The task of the feature DMA AC is to monitor both the current EFL and the current BQP in the cell and to consider these two factors during the TCH allocation: if particular requirements for BQP and EFL are not fulfilled (e. Detailed Functional Description of DMA Admission Control 1) DMA Admission Control Decision Algorithm The BTS continuously measures the FER of the ongoing calls and calculates the current EFL and BQP figures for each configured DMA layer / CFHSY (see command CREATE CFHSY . As during the BTS alignment all parameter values relevant for DMA AC are transmitted to the BTS. The determine the value of the ‘soft blocking flag’.

will it attempt preemption -> directed retry -> queuing&downgrade etc. The sending period for the RADIO LINK ADMISSION CONTROL message (i. starting from the lowest priority calls. If preemption is attempted. This message contains (for each configured DMA layer / CFHSYID) -> the current BQP values -> the current EFL vaue -> a flag that indicates whether the DMA layer must be soft-blocked.. If the BSC either does not find any other service layer supporting speech services or if it finds a suitable layer but no suitable TCH (or meets with soft blocking on this layer as well) it will start/check all the procedures that it also starts in case of hard blocking (i. i. the new call setup on the DMA layer is only allowed if the BQP criterion is fulfilled in correspondence with the configured ‘Admission Control Link Type’ as shown in the table below.If the EFL is lower than or equal to the configurable maximum EFL threshold ‘max EFL_DMA’ (see parameter ACMAXEFLDMA) but higher than ACMINEFLDMA. 2. 2) DMA Admission Control Signaling The BTS periodically sends the spontaneous Abis O&M message RADIO LINK ADMISSION CONTROL to the BSC. If the preferred DMA layer is soft-blocked.e. it preempts one which is compatible with the request .e. no TCH available). 3) TCH Allocation with DMA Admission Control When the BSC receives a TCH request during a call setup procedure for a particular DMA layer it checks the received soft blocking flag for the affected DMA layer.e. the TCH request is not served on the preferred DMA layer 1. ENFORCHO in command SET BSC [BASICS] and DGRSTRGY in command CREATE BTS [BASICS]). the time between two consecutive transmissions) is determined by the parameter ACPER. Explanation: The ‘Admission Control Link Type’ (see parameter ACLNKTYP) defines the type of samples to be collected and the way they are used for the estimation of BQP: • acLinkType = 0 UL and DL samples are collected and separately evaluated • acLinkType =1 only UL samples are collected and evaluated • acLinkType =2 UL and DL samples shall be collected. the BSC attempts to allocate a TCH on a different service layer where speech is allowed.also a call in the 185 . merged and commonly evaluated If the calculated BQP is higher than the already mentioned configurable BQP threshold BQPmax (parameter ACBQPMAX). (see parameters EPRE and EQ in command SET BTS [OPTIONS]. the soft-blocking flag is set for the affected DMA layer.e. the BSC looks into its internal tables where previously all vulnerable (i. preemptable) calls have been stored (ordered by priority) and.

23. ACBQPMAX=5. this parameter is only relevant if the parameter EAC is set to TRUE and it defines the maximum tolerated BQP in a DMA layer for the feature ‘DMA Admission Control’..β) * mean_BQPn-1 + β * BQPn As this formula shows. this parameter is only relevant if the parameter EAC is set to TRUE and it defines the forgetting factor for the exponential filter used for fractional load averaging. object: range: unit: default: BTS [ADM] 2 . see below) are averaged using an exponential filter with adjustable forgetting factor (β). object: range: unit: default: BTS [ADM] 1. For further details please refer to the feature description above the parameter listing. the TCH request is served when a TCH resource becomes available . If the released TCH belongs to the DMA layer and if the TCH is compatible with the request.2.. for Handover and Power Control decisions) but by adding the new sample with the weighting factor β and by simultaneously reducing the weight of the existing average value by the facfor (1-β). 0.02 . ???? > SET BTS [ADM]: NAME=BTSM:0/BTS:0. the BTS-no.this can be either due to PS call downgrade or due to release of a CS call.g.. the averaging is not done by a gliding averaging window (as done e. but in this case the MAIO of the preempted call ia maintained for the preempting one. If a TCH request is queued (no matter whether it is queued due to soft blocking of a DMA layer or due to lack of idle TCHs). allocates this TCH and reuses the previously used MAIO for the new call.g. Object path name. Admission Control exponential filter forgetting factor.04 ACFERMAX=5. To avoid the impact of stochastic fluctuation in BQP on the DMA AC decision the BQP values calculated in each AC Period (parameter ACPER. for Handover and Power Control decisions) but by adding the new sample with the weighting factor λ and by simultaneously reducing the weight of the existing average value by the facfor (1-λ). this parameter is only relevant if the parameter EAC is set to TRUE and it defines the maximum FER value which is used for the calculation of the Bad Quality Pro.was changed to 0.1 0. object: range: step size: default: BTS [ADM] 0..2.DMA layer can be preempted. <NULL> 1% 5 ACBQPFF=0. Admission Control FER max.. mean_BQPn = (1.02 0. object: range: step size: default: BTS [ADM] 0. the averaging is not done by a gliding averaging window (as done e.0. 186 . <NULL> 1% 5.0 .λ) * mean_ZZ_DMAn-1 + λ * ZZ_DMAn with (ZZ = FR or HR) ACEFLFF=0. Admission Control BQP forgetting factor. the BSC receives RADIO LINK ADMISSION CONTROL message that indicates that the DMA layer is not soft-blocked anymore. To get an estimate of the traffic on the DMA layer of the cell the average number of busy channels is calculated using exponential filter with an adjustable forgetting factor (λ) mean_ZZ_DMAn = (1. 10.. 1. 10.2 Admission Control BQP max.04. <NULL> 0. the BSC.0 As this formula shows. <NULL> 0. was changed to 0. Due to the new object architecture (the BTS object is a subordinate object of the BTSM) the range for the BTSMno. assuming that the current BQP figures do not change.1 .0. this parameter is only relevant if the parameter EAC is set to TRUE and it defines forgetting factor β for the time exponential filter used for BQP averaging for the feature ‘Admission Control’. For further details please refer to the feature description above the parameter listing.199.0.

in percent. this parameter determines whether the feature ‘Admission Control’ for Dynamic MAIO Allocation (DMA) is enabled in the cell... SET BTS:ENDMA=TRUE. … PER_45.. SET BTS:EAC=TRUE ACPER=SACCH_120. Notes: . SACCH_032. the time between two consecutive transmissions) in SACCH multiframes (1 SACCH multiframe = 480ms). if DMA and DMA AC are to be enabled. SACCH_024..) have been consistently and conclusively created in the database before. object: range: default: BTS [ADM] PER_10. PER_25.e. merged and commonly evaluated For further details please refer to the feature description above the parameter listing. object: range: BTS [ADM] SACCH_020.. PER_15. SACCH_400 SACCH_120 default: EAC=FALSE. For further details please refer to the feature description above the parameter listing.. SET CBTS:ENDMA=TRUE. object: range: default: BTS [ADM] TRUE. SACCH_036. PER_10 Admission Control minimum EFL on DMA.This parameter can only be set to TRUE in a particular BTS if DMA was enabled in the associated BTS and CBTS objects before. Enable admission control. object: range: default: BTS [ADM] PER_5. . the DBAEM command sequence is the following (for a particular BTS): CREATE CHAN. PER_15. Admission Control period. … PER_95. this parameter is only relevant if the parameter EAC is set to TRUE and it defines the sending period for the RADIO LINK ADMISSION CONTROL message (i. PER_50. For further details please refer to the feature description above the parameter listing. Thus. FALSE FALSE 187 . <NULL> ulSamplesOnly Admission Control link type. the maximum EFL on the DMA layer of the cell.. Admission Control maximum EFL on DMA.ACLNKTYP= UL_SAMPLES_ONLY. in percent. PER_100 PER_50 PER_20. this parameter is listed within a SET BTS command behind the SET CBTS command that enables DMA (which itself can only be enabled if all associated objects (CFHSY.. CHAN etc. ACMINEFLDMA=PER_10. PER_10. For further details please refer to the feature description above the parameter listing. this parameter is only relevant if the parameter EAC is set to TRUE and it specifies. this parameter is only relevant if the parameter EAC is set to TRUE and it defines the type of samples to be collected for the BQP determination and the way they are used for the estimation of BQP: • acLinkType = 0 -> ACLNKTYP = uLAndDLSamplesSeparately UL and DL samples are collected and separately evaluated • acLinkType = 1 -> ACLNKTYP = uLSamplesOnly only UL samples are collected and evaluated • acLinkType = 2 -> ACLNKTYP = uLAndDLSamplesCommonly UL and DL samples shall be collected. SACCH_028. uLSamplesOnly. SACCH_040 .. uLAndDLSamplesCommonly. TRX. the minimum EFL on the DMA layer of the cell. this parameter is only relevant if the parameter EAC is set to TRUE and it specifies. default: ACMAXEFLDMA=PER_50.. In the DBAEM. object: range: BTS [ADM] uLAndDLSamplesSeparately.

Instead. the MS receives an IMMEDIATE ASSIGNMENT COMMAND via the AGCH. In the successful case. the MS performs a RACH access by sending a CHANNEL REQUEST message to the BSS via the RACH. .delayed IMMEDIATE ASSIGNMENT sending due to Abis via satellite link (with the correspondingly high propagation delay on Abis) .in this case the BTS cannot decode the CHANNEL REQUEST(s) and discards the messages) .The level of MAXRETR has an impact on the RACH load and the speed of MS access to a cell. While in the latter case. A high value of MAXRETR will speed up the SET BTS [CCCH]: NAME=BTSM:0/BTS:0. Maximum number of retransmissions. TWO. whether it receives an IMMEDIATE ASSIGNMENT REJECT as response to a transmitted CHANNEL REQUEST or whether it does not receive any response at all. if it has previously left it due to unsuccessful RACH access attempts. as described above. The value of MAXRETR determines how often the MS may repeat its access attempt. this parameter defines the maximum number of retransmission attempts the MS can perform on the RACH if the previous attempts have been unsuccessful. The MS regards an access attempt unsuccessful when it has neither received an IMMEDIATE ASSIGNMENT COMMAND or . in case of IMMEDIATE ASSIGNMENT REJECT the MS just has to obey a waiting time before it may attempt the next RACH access attempt (see parameter T3122 in command SET BSC [BASICS]) and will in any case stay in the cell. To request a dedicated control channel (normally an SDCCH) from the network. In case of RACH and AGCH overload a decrease of MAXRETR can be used to decreases the number of access attempts of the MSs and therefore the RACH overload without barring any access classes (see parameter NALLWACC in command SET BTS [OPTIONS]). If after MAXRETR retransmissions the MS still did not receive any IMMEDIATE ASSIGNMENT COMMAND or IMMEDIATE ASSIGNMENT REJECT.RACH collisions (this happens when several MS access the same RACH at the same time .if no SDCCH is available in the cell . MAXRETR=FOUR. it starts cell reselection to a suitable neighbour cell.08 188 .08 GSM 05..radio interface problems (loss of messages) . FOUR. 2. all parameters of the previous ‘BTS packages’ were moved below the object BTS and appear in the DBAEM in the CREATE BTS command.an IMMEDIATE ASSIGNMENT REJECT via the AGCH before the time defined by the parameter NSLOTST (see below) has expired. 3 and 4) in the IE ‘RACH Control Parameters’ Notes: .overload handling (which features the discarding of CHANNEL REQUIRED messages and thus the discarding of the embedded CHANNEL REQUEST. > Attention: Since BR6. To avoid a ‘ping-pong’ cell reselection. see associated section in the appendix) The value of MAXRETR is sent on the BCCH (SYSTEM INFORMATION TYPE 1. Object path name.0 The DBAEM does not group the command parameters into ‘packages’ anymore. A RACH access without subsequent receipt of an IMMEDIATE ASSIGNMENT COMMAND or REJECT message can occur due to: .For the MS it does make a difference. The logical group “[CCCH]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands .Setting the cell specific attributes for the CCCH: < All attribute values set by this command (except for NY1) have effects on the SYSTEM INFORMATION messages on the BCCH. SEVEN default: FOUR Reference: GSM 04. the MS will leave the cell after MAXRETR access attempts without receipt of an MMEDIATE ASSIGNMENT. the MS must obey a waiting time of 5 seconds before it can return to the original cell with a further cell reselection procedure. object: range: BTS [CCCH] ONE.

31 5 GSM 04. an equivalent parameter is broadcast on the PBCCH for GPRS mobiles to allow a separate management of cell selection and cell reselection for GPRS.when de-interleaved and decoded . MSTXPMAXDCS or MSTXPMAXPCS) in command CREATE BTS [BASICS]) during a communication on a DCCH or TCH (after an IMMEDIATE ASSIGNMENT).g. The value of MSTXPMAXCH should be adapted to the size of the radio cell: the smaller the cell the lower the allowed transmit power should be in order to minimize channel interference in adjacent cells and to save MS battery. This parameter is MSTXPMAC (see command CREATE PTPPKF). The channels are shared on a block by block basis and the information within each block . These reserved CCCH blocks are never used as PCH but exclusively as AGCH. object: range: default: Reference: BTS [CCCH] 0. Up to BR7. object: range: default: Reference: BTS [CCCH] 0.. To guarantee a basic throughput of AGCH messages (no matter how high the paging load is). one multiframe. indicates the maximum transmit power level a MS is allowed to use when accessing a cell on the ‘random access channel’ (RACH) and before receiving the first ‘Power Command’ (see parameter MSTXPMAXGSM (resp.e.MSTXPMAXCH=5. a low value will delay the access and may result in cell reselection and therefore in a delay or unsuccessful cell access if no other cell is available. the mechanism checks the filling state of the AGCH queue and the ‘age’ of the enqueued messages in order to determine 189 . while MBCCHC provides only 3 CCCH blocks) is shared between PCHs and AGCHs.If a PBCCH is configured (see parameter CREATE CHAN for TCH with GDCH=PBCCH). if there were pagings in the BTS paging queues the would use the available CCCH blocks for paging first. Starting from BR8.and non-GPRS-mobiles.7 1 GSM 04. MSTXPMAXDCS or MSTXPMAXPCS) (CREATE BTS [BASICS]) to guarantee that a MS. . This means that the number of available CCCH blocks. MS maximum transmit power for CCCH.0! access and thus increase the RACH and AGCH load.0 an improved CCCH management meachnism was implemented which features a priorization of AGCH messages over PCH messages in the ‘shared’ CCCH blocks under particular load conditions. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3 and Type4) in the IE ‘Cell Selection Parameters’. channel type MAINBCCH provides 9 CCCH blocks.e. MSTXPMAXCH may be set to the same value as MSTXPMAXGSM (resp. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3) in the IE ‘Control Channel Description’. is able to communicate with the network also on the dedicated channel.allows a MS to determine whether the CCCH block is used as PCH or AGCH. This parameter is also used (together with other parameters) to define the path loss criterion C1 (see parameter CELLRESH in command CREATE BTS [BASICS]). thus guaranteeing a basic network access even in case of high paging traffic. Notes: . Number of blocks for access grant.. specifies the number of CCCH blocks to be reserved in each configured CCCH timeslot for the Access Grant Channel (AGCH) during a period of 51 TDMA frames. Paging Channel (PCH) and AGCH share the same TDMA frame mapping when combined onto a basic physical channel. which is accepted on the RACH. i. NBLKACGR can be set to a value > 0 to reserve a defined number of CCCHs exclusively for AGCH. which is determined by the created CCCH configuration (e.02 Default value changed in BR8.08 GSM 05.08 GSM 05.08 NBLKACGR=1. MSTXPMAXDCS or MSTXPMAXPCS) (CREATE BTS [BASICS])). i. In a first step.Increasing the entered value decreases the allowed transmit power on the RACH and thus the maximum allowed distance between MS and BTS for RACH access! (For details regarding the power classes and power control levels please refer to the parameter MSTXPMAXGSM (resp.0 in the BTS the transmission of PAGING REQUESTs via the PCH was strictly priorized against the transmission of IMMEDIATE ASSIGNMENTs via the AGCH. i.e.

the burst-wise receipt of more than 4 IMMEDIATE ASSIGNMENT messages within a very short time period could result in an overflow of the BTS AGCH queue and thus to AGCH overload (see also the ‘Overload’ section in the appendix of this document).According to a BR7. due to the resulting reduction of paging groups and the priority of paging in the non-reserved CCCH blocks. while AGCH messages can only be transmitted on the reserved blocks. one MAINBCCH on timeslot 0 and an additional CCCH on timeslot 2 of the BCCH TRX (with 9 CCCH blocks each). with a setting of NBLKACGR=2 in this example. if in a cell two CCCHs are created (e. but is also reduces the number of CCCH blocks available for paging by the selected value and thus also reduces the number of paging groups (see also NFRAMEPG) and paging queues in the BTS.whether a CCCH block should be ‘preempted’ for AGCH. please refer to the section ‘BTS Overload Handling’ in the appendix of this document. For further details. This means that NBLKACGR should not be set to a too high values. in both CCCHs the BTS reserves one block for AGCH.in periods of high paging load . as the AGCH queue can only be emptied every 235ms. while the 7 remaining ones remain ‘shared’ for PCH and AGCH in either CCCH. 190 .The setting of NBLKACGR refers to each CCCH timeslot created in a cell. NBLKACGR must be set to a value >0 to avoid particular alarm messages from the BTSEs. Setting NBLKACGR > 0 can increase the guaranteed AGCH throughput and thus lead to a quicker emptying of the AGCH queue.have the effect that. In correspondence with the GSM specification.NBLKACGR must be set as follows a) NBLKACGR ≤ 2 if a BCBCH is created in the cell b) NBLKACGR > 0 if a SCBCH is created in the cell (see CREATE CHAN) .0 Operator Hint. the default value NBLKACGR=1 is a recommended setting to guarantee AGCH traffic also in hours of high PCH traffic. E.g. paging is performed mainly in the non-reserved CCCH blocks. For each BCCH/CCCH timeslot the BTS provides 1 AGCH queue with 16 places each (1 place for 1 IMMEDIATE ASSIGNMENT COMMAND or IMMEDIATE ASSIGNMENT REJECT). 2 blocks will be reserved for AGCH. In any case. As these are grouped at adjacent positions within the BCCH/CCCHmultiframes (235ms). Notes: . . the blocks that are reserved for AGCH are located in adjacent CCCH blocks at a specific position within the BCCH/CCCHmultiframes (235ms).g. In other words. as this would .

defines the number of multiframes (51 TDMA frames) between two transmissions of the same paging message to mobiles of the same ‘paging group’. When DSC reaches 0 or a negative value. The paging group determines which CCCH blocks the MS shall monitor for incoming paging messages. Setting NFRAMEPG to a higher value results in an increase of the number of paging groups (that are sent on the Um with a lower frequency as the Um capacity remains the same). When the MS camps on a cell. the earlier the BTS will run into congestion of single paging queues. By just monitoring a subset of the CCCH blocks for paging (Discontinuous Reception (DRX)) the MS can save battery capacity.02 GSM 05. NFRAMEPG has an influence on the downlink signaling failure criterion which in turn is based on the ‘downlink signaling failure counter’ (DSC) in the MS. If the MS successfully decodes a message in its paging subchannel DSC is increased by 1 (however never beyond the nearest integer to 90/N) otherwise DSC is decreased by 4. see above) and refers to the so-called ‘Notification Channel’ (NCH). A NCH can be configured on those CCCH blocks within the channel NOCHFBLK=1. i. Several ASCI groups calls can be active within one cell at the same time. Notification channel first block. This parameter is relevant for ASCI (parameter ASCISER. see above) and the setting of NFRAMEPG. thus the NCH might broadcast different NOTIFICATION COMMAND messages with different group call references and ASCI Common TCH description data. and thus to an extension of the buffer space which is available in the BTS for the PAGING REQUESTs that are to be transmitted. Moreover. which results in ‘extended paging’ or/and ‘paging reorganization’.e. if the ‘Uplink Reply’ procedure is activated in the cell (see parameter ASCIULR in command SET BTS [CCCH]). The smaller the value of NFRAMEPG. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3) in the IE ‘Control Channel Description’. the more paging groups and thus paging queues are available in the BTS.NFRAMEPG=2. the higher the CCCH capacity in the cell. the used CCCH configuration in the current cell (also considering the setting NBLKACGR. A NOTIFICATION COMMAND with ASCI group call reference but without ‘Channel Description’ (indicating an ongoing ASCI group call but. the higher the value of NFRAMEPG. the longer the time distance between pagings of the same paging group. DSC is initialized to a value equal to the nearest integer to 90/N where N is the NFRAMEPG parameter for that cell. object: range: default: Reference: BTS [CCCH] 2-9 2 GSM 04.08 Number of multiframes between paging. This increases the average call setup time for MTCs (from point of view of the calling party). On the other hand. The NCH is used to transport the NOTIFICATION COMMAND message (BSC -> ASCI MS) which is used to inform the ASCI MS about the currently active ASCI group calls (by a ‘Group Call Reference’ number) and to provide the ‘Channel description’ data if an ‘ASCI Common TCH’ (TCH used simulaneously by all ASCI MSs in the cell as DL TCH for a VBS/VGCS group call) is currently activated in the cell. Thus. no allocated ASCI Common TCH) can only be sent. For each paging group an own paging queue is available in the BTS. The BSC and the MS calculate the actual paging group from the IMSI. object: range: default: BTS [CCCH] 1-7 1 191 . due to absense of ASCI subscribers currently participating in this group call. The NOTIFICATION COMMANDs are periodically repeated on the Um interface. with a higher value of NFRAMEPG the incoming paging traffic is distributed over a greater number of paging groups (paging queues) and thus the BTS can manage temporary paging ‘peaks’ in a better way than with a small value of NFRAMEPG.08 GSM 05. the periodicity of these messages is determined by the parameter TNOCH (see command SET BTS [TIMER]). a downlink signaling failure is declared and cell reselection is performed.

The position of the NCHs within the BCCH/CCCH timeslot is broadcast in the SYSTEM INFORMATION TYPE 1 within the IE ‘SI1 Rest Octets’. transmission of a CHANNEL REQUEST message). then the NCH is sent only every Nth SACCH multiframe anyway. the total number of blocks is defined by the parameter NOCHBLKN (see below). that are reserved for AGCH (parameter NBLKACGR.e.in this case the BTS cannot decode the CHANNEL REQUEST(s) and discards the messages) . Notification channel block number. . In the normal and successful case. if an ASCI MS is already involved in a CS or VBS/VGCS group call.If TNOCH=1 and NOCHBLKN=1 then the affected CCCH block is exclusively reserved for NCH. If a CCCH block used as NCH can be used for AGCH traffic as well.08 organization of a BCCH/CCCH. the IMMDIATE ASSIGNMENT COMMAND or REJECT message may not arrive on time before the MS sends the next random access attempt. see above). object: range: default: Reference: BTS [CCCH] 0. In any case the total number of NCHs (NOCHBLKN) must be smaller than the number of CCCH blocks reserved for access grant (NBLKACGR).If NOCHBLKN ≥ 1 and TNOCH=N (N≥ 1). The position of the NCHs within the BCCH/CCCH timeslot is broadcast in the SYSTEM INFORMATION TYPE 1 within the IE ‘SI1 Rest Octets’. the BTS reacts with an ERROR REPORT message. In the mobile the retransmission mechanism is continuously executed after the first RACH access and only stopped if an IMMEDIATE ASSIGNMENT COMMAND or (if no SDCCH is available) an IMMEDIATE ASSIGNMENT REJECT message is received from the BSS via the AGCH.delayed IMMEDIATE ASSIGNMENT sending due to Abis via satellite link (with the correspondingly high propagation delay on Abis) . see associated section in the appendix) 192 .RACH collisions (this happens when several MS access the same RACH at the same time .radio interface problems (loss of messages) . under specific conditions. object: range: default: BTS [CCCH] 1-4 1 NSLOTST=10.15 10 GSM 04.If NOCHBLKN ≥ 1 and TNOCH=1. If this information is not included in the SYS INFO 1 message sent from BSC to BTS while ASCI is enabled (parameter ASCISER. the MS receives the IMMEDIATE ASSIGNMENT COMMAND before a second access attempt is started. cause value ‘message sequence error’. The parameter NOCHFBLK indicates the first CCCH block to be used as NCH. For further details.e. However. A RACH access without subsequent receipt of an IMMEDIATE ASSIGNMENT COMMAND or REJECT message can occur due to: .. depends on the setting of both NOCHBLKN and TNOCH (see command SET BTS [TIMER]): . this parameter indicates the total number of CCCH blocks to be used as Notification Channel (NCH). see above). . it depends on the number of NCH blocks to be transmitted/repeated whether every now and then a CCCH block remains available for AGCH or not. i.e. determines the cycle period for retransmission of RACH accesses (i. Number of slot spread transmission. Note: The NOTIFICATION COMMAND message can also be sent the FACCH. For further details please refer to the parameter NOCHFBLK (see above). i.overload handling (which features the discarding of CHANNEL REQUIRED messages and thus the discarding of the embedded CHANNEL REQUEST.NOCHBLKN=1. please refer to the parameter NOTFACCH in command SET BSC [BASICS]. in this case the CCCH blocks for NCH can be used for AGCH in those SACCH MF where no NCH message is to be transmitted. If more than one CCCH block is to be used. it determines the time an MS must wait after a RACH access attempt before a new one can be started.

For phase 1 mobiles there is only one fixed retransmission period. 9. 25 7. see command CREATE CHAN for BCCH). 10. 32 td (RACH slots. 16 5.If an Abis is realized via satellite link it is strongly recommended to set the NSLOTST to 14 as this represents the longest possible RACH retransmission cycle that can be executed by phase 2 mobiles. i.75 sec) 217(1.If the value of NSLOTST is to be decreased in case of high traffic density on the RACH it should be done in small steps with close observation of the load situation on the RACH in order to prevent RACH overload.50 sec) 86 (0. The delay time determined by NSLOTST consists of a fixed (deterministic part “td” and a random part “tr”. a value with a small td might cause sporadic RACH overload even with few MSs roaming in the cell. 8. 11.25 sec) 55 (0. NSLOTST values with a long td may extend the duration of location update. 2.00 sec) tx_integer itself determines the size of a ‘window’ (in RACH slots) in which the access can be randomly sent after the fixed period td. 193 . 20 6.00 sec) td (RACH slots.75 sec) 115 (1. the different settings of NSLOTST only lead to different retransmission cycles for phase 2 mobiles. The MS maps the tx_integer value to the static and deterministic parts td and tr.The number of RACH retransmissions is restricted to a value determined by the parameter MAXRETR (see above). 14. Calculation: the value NSLOTST is sent as a value called “tx_integer” on the BCCH (SYSTEM INFORMATION TYPE 1. retransmission td = 163 slots first transmission with a collision NSLOTST = tx_integer = 6 tr = tx_integer = 6 tr = 6 Notes: . 3 and 4) in the IE ‘RACH Control Parameters’. 12. which is different for different BCCH configurations (combined. NSLOTST (tx_integer) tr 0 3 1 4 2 5 3 6 4 7 5 8 6 9 7 10 8 11 9 12 10 14 11 16 12 20 13 25 14 32 15 50 For phase 2 mobiles the tx_integer values have a fixed mapping to the fixed delay time td. not combined. 50 4.45 sec) 58 (0. This avoids unnecessary retransmissions that lead to additional SDCCH seizures and thus to a decrease of the Immediate Assignment Success Rate (or even to SDCCH congestion). .e. combined BCCH) 41 (0.50 sec) 163(0.25 sec) 76 (0. according to the following table: MS phase Phase 1 Phase 2 tr ----3.35 sec) 41 (0.35 sec) 52 (0. uncombined BCCH) 55 (0.35 sec) 109 (0.

After receipt of the PHYS INFO the MS normally sets up the layer-2 connection on the new channel by transmitting an SABM message. (RXLEVAMI see CREATE BTS [BASICS]. object: unit: range: BTS [CCCH] 2dB 0-3 0=feature disabled default: 0 Reference: GSM 04.08 GSM 05. If the BTS has not received the SABM from the MS after transmission of the last PHYS INFO message and expiry of timer T3105 (see T3105 in command SET BTS [TIMER]) the BTS sends a CONNECTION FAILURE indication with cause ‘Handover access failure’ to the BSC and the new allocated channels are released. The following setting is necessary to avoid the transmission of the CONN FAIL indication while the MS falls back to the old channel due to unsuccessful access to the target cell and thus an unjustified registration of a ‘call drop’: NY1*T3105 >= 2 sec. It is also used by the MS in its calculation of C1 and C2 parameters: C1 = (A . It is used only by DCS1800 Class 3 Mobile Stations to add a power offset to the value of MS_TXPWR_MAX_CCH (see MSTXPMAXCH ) used for its random access attempts.RXLEVAMI Max (B. Please refer to the description of parameter T3105 (in command SET BTS [TIMER]) for further details! Power Offset.NY1=30. . MSTXPMAXCH see SET BTS [CCCH]. this parameter is relevant only for DCS 1800 cells. The PHYS INFO message contains the actual timing advance which the BTS derives from the time delay of the handover access burst.Any CONN FAIL is a trigger event for the TCH loss counter NRFLTCH. . 194 .The MS can only receive the PHYSICAL INFO within a time frame determined by the MS timer T3124 (time to receive the PHYS INFO) which is fixed to 320ms.0! PWROFS=0.) This info is sent on the BCCH (SYSTEM INFORMATION TYPE 4) in the IE ‘SI 4 Rest Octets’. Notes: .0)) where A = <received level average> . After sending of the first HANDOVER ACCESS burst the MS waits to receive the PHYSICAL INFORMATION message from the BTS.Max(B. indicates the maximum number of repetitions of PHYSICAL INFORMATION messages from the network to the MS during an asynchronous handover.0)= 0 P = Maximum RF output power of the MS (see table below). .P Max (B.08 NY1.Since the introduction of the BR70 CR 2335 the values set for NY1 and T3105 are no longer applied for the PHYSICAL INFO procedure in case of SDCCH-SDCCH handover.08 Default value changed in BR8.The combination of the values NY1=30 and T3105=MS10-10 has turned out to improve the ‘handover speech gap’ in case of BSCcontrolled intercell handover as it avoids the ‘bombardement’ of the MS with unnecessary FACCH messages (that ‘steal’ the frames of the normal speech channel). object: range: default: Reference: BTS [CCCH] 1-254 30 GSM 04.0)= MSTXPMAXCH + PWROFS .

those TCHs with the best interference class are allocated first. the BTS measures the interference considering all frequencies used in the hopping sequence assigned to the a TCH (see parameter FHSY in command CREATE CHANNEL)! . i. defines the number of SACCH multiframes (480ms = 4 multiframes.g.threshold boundary 3 . the interleaving function distributes the SACCH info over 4 bursts) over which values are averaged (value 1.If frequency hopping is activated. also the idle TCH measurements depend on a correct configuration of the uplink path and a suitable setting of the BTSE parameter RXLEVADJ (see command CREATE RFLOOP). these values set the limits of four interference bands for the idle time slots. Instead.62 (threshold boundaries) default: 31 (averaging period) 2 (threshold boundary 1) 6 (threshold boundary 2) 12 (threshold boundary 3) 22 (threshold boundary 4) Reference: 3GPP 45.. if this parameter is set to ENABLED the BTS permanently performs interference measurements on the idle traffic channels and idle TCH/SDs in the uplink and reports he measurement results in form of ‘RF resource indication (RFRESIND)’ messages via the Abis to the BSC.Only if INTCLASS is set to TRUE the PM counters for idle TCH interference measurements (MEITCHIB and ILUPLKIC) will deliver any results. object: range: default: BTS [INTERF] TRUE. SET BTS [INTERF]: NAME=BTSM:0/BTS:0.threshold boundary 4 unit: averaging period: 1 SACCH multiframe threshold boundaries: -1dBr range: 1-31 (averaging period) 0. In the RFRESIND messages the measured TCHs are assigned to so-called ‘interference classes’. The term ‘incoming TCH request’ represents any kind of call as well as any kind of incoming handover (incl.Setting the cell attributes for the Interference Measurement of idle TCHs: < The parameters set with this command are used for averaging and reporting interference levels in idle traffic channels. INTAVEPR=312-612-22. Object path name.e.threshold boundary 2 . the subsequent TCH request is served by the next TCH on TRX:0 (e.e. Notes: . timeslot 2). the BSC also evaluates the interference band of the idle TCHs for the TCH allocation.g. selection of TCHs for incoming TCH requests is done cyclically.31) and Interference threshold boundaries X (X= 1 to 5). Note: Like any other level measurements performed by the BTS.008 INTCLASS=TRUE.0 The DBAEM does not group the command parameters into ‘packages’ anymore. > Attention: Since BR6.. Only if all TCHs with the best interference class are busy. the BSC allocates those with a worse interference class to an incoming TCH request. The logical group “[INTERF]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . An interference class is represented by an interference band (limited by an upper and lower interference level) which is defined by the parameter INTAVEPR. The threshold values entered for INTAVEPR represent uplink RXLEV values that are measured and averaged by the BTS and then mapped to the ‘interference bands’ in correspondence with the setting of INTAVEPR. the BSC starts the TCH allocation by selecting the first TCH on TRX:0 (e. intracell handover).The idle TCH measurements are performed for normal TCHs as 195 .threshold boundary 1 . timeslot 3) and so on. Averaging period for idle TCH measurements. object: fomat: BTS [INTERF] averaging period . If INTCLASS=TRUE. The status of the INTCLASS flag has an influence on the channel allocation by the BSC: Basically the channel allocation resp. i. For the BSC TCH allocation pattern there is no difference between calls and handovers. all parameters of the previous ‘BTS packages’ were moved below the object BTS and appear in the DBAEM in the CREATE BTS command. FALSE TRUE Interference classification enabled. .

RF resource indication period. from point of view of the BTS the TCH/SD is treated as a dual rate TCH again. Instead. This again means that the BTS might send idle channel measurements during this period (depending on the setting of RFRSINDP). If it has received a CHANNEL ACTIVATION for channel type ‘SDCCH’. even if TGUARDTCHSD (see command SET BSC [BASICS]) is still running for a specific TCH/SD in the BSC (i. the TCH/SD is still in the SDCCH_BACKUP_POOL). even if the TCH/SD is still in the SDCCH_BACKUP_POOL. This means that. it is treated as SDCCH. Generally the BTS does not know anything about the association of the TCH/SD channels to the ‘BSC channel pools’ (see parameter CHPOOLTYP in command CREATE CHAN for TCH/SD). object: unit: range: default: BTS [INTERF] 1 SACCH multiframe 1-254 60 well as for TCH/SD channels (see command CREATE CHAN for TCH/SD) as long as they are neither occupied as TCH nor as SDCCH. for the BTS a TCH/SD is treated as a normal dual rate TCH if it is ‘idle’ or if it has received a CHANNEL ACTIVATION for channel type ‘TCH’. defines the sending rate of the RFRESIND message towards the BSC. 196 .RFRSINDP=60.e.

the alarm with error ID 70 . Instead. * Note: CHANNEL ACTIVATIONs are only considered in case of TCH activations for CS TCH requests. > Attention: Since BR6.0! TNC no successful SDCCH ssignment TNC TNC time zone Note: The 'SLEEPING CELL' alarm will in any case be output if a BTS is 'barred' (see SET BTS [OPTIONS]: CELLBARR).e. Object path name. disables the features ‘sleeping cell detection’ and ‘sleeping TRX detection’ for the affected BTS. ESTIN for SDCCH received) SET BTS [TIMER]: NAME=BTSM:0/BTS:0. ENABLED ENABLED Default value changed in BR8.NO CALL IN TRX WITHIN A PREDEFINED TIME FRAME is output. 1)The feature ‘sleeping cell detection’ supervises the SDCCH activations within the cell: If at the end of the observation period no successful SDCCH assignment could be registered. the alarm ‘alarm with error ID 66 . The logical group “[TIMER]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . the SLEEPING TRX alarm is triggered. Channel activations due to GPRS traffic are not considered in the supervision mechanism therefore the ‘sleeping TRX’ alarm can never be reaised for TRXs which are exclusively used for GPRS traffic. all parameters of the previous ‘BTS packages’ were moved below the object BTS and appear in the DBAEM in the CREATE BTS command. Principle: Sleeping Cell Alarm active Sleeping Cell Alarm ceased = succ.NO CALL IN CELL WITHIN A PREDEFINED TIME FRAME due to missing SDCCH activity. the BSC observes the number of ESTABLISH INDICATION messages for SDCCH received from the observed BTS. this flag enables resp. in which the activity of the cell respectively the TRX is observed within time zone specific observation periods (see parameters NCDP1 and NCDP2). object: range: default: BTS [TIMER] DISABLED. 197 . For this. For both features two time zones (representing daytime and night time traffic) can be defined. ENANCD=ENABLED. Enable 'No call in TRX/cell detection'. For both alarms the ceasing of the alarm can take place at the earliest at the end of the next observation period if in this period the alarm condition has ceased (successful activities). In this case these cells carry traffic but issue the alarm with error ID 66 . If for a certain TRX the difference between the number of CHAN ACT ACK messages and the number of EST IND messages is equal or greater than eight (8). For this.Setting the cell specific timer values: < This command sets the timers on layer 2 and 3 of Um interface. In many networks this approach is commonly used for cells which are exclusively used as handover target. 2)The feature ‘sleeping TRX detection’ supervises the TCH activations on a specific TRX: If at the end of the observation period the TCH activation success rate is below a fixed threshold. SDCCH assignment (i.NO CALL IN CELL WITHIN A PREDEFINED TIME FRAME is output.0 The DBAEM does not group the command parameters into ‘packages’ anymore. the BSC observes the number of CHANNEL ACTIVATION ACKNOWLEDGE* messages for TCH and the number of ESTABLISH INDICATION messages for TCH.

Default value changed in BR8. e. Signalling messages that do not Default value changed in BR8. StartTime2 represents the beginning of the timeframe.0! NCDP2=H6-1.255 with the DTAP DISCONNECT which is transmitted between MS and default: 29 (sdcchSAPI0) 31 (facchTCHF) MSC)..facchTCHF . facchTCHH. Messages in acknowledged mode are SABM.sdcchSAPI3 facchTCHF. in the downlink the SYSTEM INFORMATION 198 .006 a transmitted message. Number of repetitions of VGCS UPLINK GRANT this parameter is only relevant if the ASCI feature is enabled and only affects VGCS object: BTS [TIMER] calls (see parameter ASCISER in SET BTS [CCCH]). It determines default: 20 the number of repetitions of the VGCS UPLINK GRANT message reference: GSM 04. this parameter allows to configure the second time-frame for the ‘sleeping TRX/cell detection’ procedure.. exchange specific LAPDm signaling messages in the so-called in sacchSDCCH. this parameter allows to configure the first time-frame for the ‘sleeping TRX/cell detection’ procedure. H0. StartTime1 represents the beginning of the time-frame TimerNoCall1 represents the observation period. sdcch SAPI3) 10ms General: During any dedicated connection the BTS and the MS (for sacchTCHSAPI0.18 during a ‘Talker Change’ procedure. object: format: unit: range: default: BTS [TIMER] StartTime1-TimerNoCall 1 StartTime1: Time in ‘1h’ TimerNoCall1: Periods of 10min StartTime1: H0. The following condition must be fulfilled: NCDP1TIMER ≤ 6x (NCDP1STARTTIME – NCDP2STARTTIME) The change of the default value was implemented to avoid unnecessary ‘sleeping cell’ alarms during nighttime. It corresponds range: 1-254 to the parameter NY2 described in the GSM Standard. T200=29-31-38-90-70-29-168. object: format: unit: range: default: BTS [TIMER] StartTime2-TimerNoCall2 StartTime2: Time in ‘1h’ TimerNoCall2: Periods of 10min StartTime2: NOTUSED. For further details please refer to parameter TGRANT (see below). Default value changed in BR8. sacchTCHSAPI3.0! have to be acknowledged are transmitted in “unacknowledged mode” via UI-frames.Sleeping TRX Alarm active Sleeping TRX Alarm ceased TNC CHAN ACT ACK (TCH) EST IND (TCH) >= 8 TNC CHAN ACT ACK (TCH) EST IND (TCH) < 8 time zone NCDP1=H1-6.TimerNoCall2 represents the observation period..H23 TimerNoCall2: 1-432 H6-1 Timer 2 for 'No call in TRX/cell detection'.g. Only 70 (sacchSDCCH) for those messages that are transmitted in acknowledged mode the 23 (sdcchSAPI3) 168 (sacchTCHSAPI3) timer T200 is used as waiting time for the layer2 acknowledgement to reference: 3GPP 44.sacchSDCCH . “acknowledged mode”. object: BTS [TIMER] unit: 5ms Parameter format: sdcchSAPI0 .facchTCHH (for sdcchSAPI0.0! NRPGRANT=20.(NCDP1STARTTIME – NCDP2STARTTIME)) The change of the default value was implemented to avoid unnecessary ‘sleeping cell’ alarms during nighttime. Note: If NCDP2 is used the following rules must be applied: 1) NCDP2STARTTIME > NCDP1STARTTIME 2) NCDP2TIMER ≤ 6x (24 . sacchTCHSAPI0 . All messages within this “acknowledged mode” are checked 38 (facchTCHH) by the LAPDm flow control mechanisms based on sequence 90 (sacchTCHSAPI0) numbers that are assigned to each transmitted LAPD message. this timer is used on different control channel types and determines the waiting time for a layer 2 frame acknowledgement. DISCONNECT and I-frames.H23 TimerNoCall1: 1-432 H1-6 Timer 1 for 'No call in TRX/cell detection'. LapDm Timer 200. This mode is started with an SABM and sacchTCHSAPI3) normally ends with the LAPDm DISCONNECT (not to be mixed up range: 0.

unnecessary retransmissions are avoided. Important: Please note that these values are the best settings from the technical point of view. which releases the associated resources. .The T200 values for sacchTCHSAPI0 and sacchSDCCH can be 199 . special rules apply for layer 2 connection setup and release: For SABM and DISC messages the value of N200 is restricted to 5 (i. and in the uplink the MEASUREMENT REPORTS. The acknowledgement frame can be another I-frame sent by the MS in the UL (if the MS has to transmit a layer-3 DTAP message anyway) as well as RECEIVE READY (RR) if there is nothing else to be transmitted on layer 3.a Um layer 2 frame retransmission should take place at the earliest after a time period the MS needs for the transmission of an acknowledgement of a received layer 2 frame .UA frames are only sent as a response to received command frames (e. Of course. Attention: Deviating from the N200 numbers listed above. SABM and DISC are transmitted at the maximum 6 times). there is no repetition based on T200 . The recommended values shown above might probably not be suitable to make a call drop rate (due to ERROR INDICATION s with cause ‘T200 expired (N200+1) times’) look ‘nice’. In fact.g. a fixed value for the BTS side specified by GSM which depends on the control channel types: N200(SDCCH)=23. For UA frames. On the basis of these considerations. the BTS development recommends the following setting of the parameter T200 T200=29-31-38-90-70-29-168 which has been implemented as default value starting from BR8. Recommended values: The different channel-type-specific values of the parameter T200 should be set in correspondence with the channel mapping and channel characteristics on the radio interface. while SAPI 0 is used for all other layer 3 radio signalling procedures. the acknowledgement mechanism based on T200 is used by the MS in the same way. The total number of repetitions is restricted to N200. the call drop rate due to T200 expiries will deliver a realistic image of the actual radio interface quality (rather than faking a good call drop rate in the performance measurement counters). Principle: When the BTS transmits a DL layer-2 frame on the air (e. Notes: . SAPI 3 is used for Short Message Service (point-to-point) transmission only.a Um layer 2 frame retransmission should take place as early as possible when the aforementioned time period has passed and no acknowledgement was received from the MS . N200(FACCH/FR)=34. . Speech frames are not transmitted via LAPD. with these settings.e.g. N200(FACCH/HR)=29 If T200 expires after the last layer 2 frame repetition the BTS sends an ERROR INDICATION with cause ‘T200 expired N200+1 times’ (followed by a RELEASE INDICATION) message to the BSC. N200(SACCH)=5. the timer values for T200 should be set in such a way that . SABM or DISC).0. an I-frame with an embedded layer 3 message) the BTS starts the timer T200 and waits for the acknowledgement frame from the MS.TYPE5 and 6 etc. To achieve an optimum radio interface performance (from the subscriber’s point of view).The LAPD mechanisms are only used for signaling messages. If the acknowledgement from the MS is not received within T200 the transmission of the layer 2 frame is repeated and T200 restarted.The SAPI (service access point identifier) is used as address for different radio signaling applications by the LAPDm protocol.

period for repetition of PHYSICAL INFORMATION message sending of PHYSICAL INFORMATION message receipt of a correctly decoded signaling or TCH frame on new channel from the MS expiry action: repetition of the PHYSICAL INFORMATION message.255 default: HLFSEC-6 Reference: GSM 04. T3105 purpose: start: stop: Notes: 200 .) the I-frame that contains channel change message (e.0! changed.08 Default value changed in BR8. This means that it can happen that. T3105: The Timer T3105 is used for the repetition of PHYSICAL INFORMATION message during the handover procedure between non synchronized cells.e. It is up to the operator to ensure that the T200 values are set long enough to avoid a call dop indication during a channel change procedure (e. HANDOVER COMMAND) is continuously repeated by the BTS due to missing layer-2 acknowledgement on the old channel. If the dedicated channel is not established before T3101 expires.. The maximum number of repetitions is determined by the parameter NY1 (see command SET BTS [CCCH]).When the BTS sends a channel assignment message to the MS that foresees a channel change (e.possibly for future purposes . thus no ESTABLISH INDICATION message is sent from BTS to BSC and T3101 expires. T3101: This timer is started. T200 is never used on these channel types). it repeats the PHYSICAL INFORMATION and restarts T3105. If this number is reached and T3105 expires again. when a channel is allocated with an IMMEDIATE ASSIGNMENT message and stopped when the MS has correctly seized the channels (ESTABLISH INDICATION is received for the assigned channel). but their value does not have any impact on the system behaviour as on the SACCH associated to a TCH and the SACCH associated to an SDCCH the ‘acknowledged mode’ is not used at present (i. the allocated channel is released. handover).. Whether the MS acknowledges this I-frame on the old channel (by RR) before it switches over to the new channel depends on the mobile type (i.e. Receipt of a correctly decoded layer 2 leads to the reset of T3105. ASSIGNMENT COMMAND or HANDOVER COMMAND). the BTS sends a CONNECTION FAILURE INDICATION message with cause ‘handover access failure' to the BSC which releases the new allocated channels and stops the context related to the handover.g.g. In this case the BSC sends an IMMEDIATE ASSIGNMENT message to the (not existing) MS which is never answered: no SABM is received from the MS. or b) by the receipt of a new SABM from the MS on return to the old channel after unsuccessful access to the target channel (this SABM initializes the T200 context and flushes the previous timer history).08 T3105=MS10-10 object: units: range: default: Reference: BTS [TIMER] MS10 = 10ms 1. If the timer expires before the BSS receives any correctly decoded layer 2 frame from the MS. The mentioned fields are available because . . TCH assignment etc. After receipt of HANDOVER ACCESS bursts with a correct handover reference the BSS sends a PHYSICAL INFORMATION message to the MS and starts timer T3105. during an ongoing channel change procedure (handover.the associated T200 values are foreseen in the GSM standard.g. This ‘T200-context’ is terminated a) after successfull access to the new channel: by the release of the old channel (RF CHANNEL RELEASE received at the BTS).5 sec SEC5 = 5s range: 0. if the maximum number of repetitions (NY1) has been reached: transmission of a CONNECTION FAILURE INDICAION with cause ‘HO access failure’ and subsequent release of new channel. some mobiles do send the RR.g. This scenario can e. the BTS starts T200 for these messages as they are embedded in an I-frame. occur if noise on the radio is decoded as RACH access ("phantom RACH") by mistake.254 MS10-10 GSM 04. others do not).T3101=HLFSEC-6. object: units: BTS [TIMER] MS100 = 100 ms HLFSEC = 0.

As described above. If the MS does not receive the UA it retransmits the SABM. Therefore the handling for TCH and SDCCH was decoupled using fixed and the technically only meaningful values for SDCCH. the MS tries to return to the old channel. Field experiences have shown that he following setting is suitable to avoid the aforementioned drawbacks: NY1*T3105 ≥ 2 sec. and as a consequence.. 800ms the MS tries to set up the layer 2 connection on the target channel. This means that for approx.Since the introduction of the BR70 CR 2335 the values set for NY1 and T3105 are no longer applied for the PHYSICAL INFO procedure in case of non-synchronized SDCCH-SDCCH handover. For an FACCH FR the time between two retransmissions (determined by the value of timer T200 for this channel type as implemented in the MS) is 32 TDMA frames and number of retransmissions (N200) is restricted to 5 (please refer to parameter T200 in command SET BTS [TIMER]).The MS can only receive the PHYS INFO within a time frame determined by the MS timer T3124 (time to receive the PHYS INFO) which is fixed to 320ms. If no PHYS INFO is received before expiry of T3124. and is stopped when the PHYSICAL INFO was received. This change was introduced in order to optimize the T3105 and NY1 setting to the characteristic periodicity of the SDCCH channel (51 frames) in case of SDCCH handover. the setup is regarded as successful and the MS transmits the HANDOVER COMPLETE. These alarms occur if the setting of T3105 and NY1 are optimized for TCH handover and are used for both TCH and SDCCH handover: while a correct setting for TCH leads to the overflow problem on the SDCCH. T3124 is started when the MS transmits the first HO ACCESS.The MS can also return to the old channel after it has successfully received the PHYS INFO. the MS returns to the old channel in the originating BTS and sends a HANDOVER FAILURE (DTAP) to the BSC. When the SABM was correctly acknowledged by a UA from the BTS. in case of SDCCH handover. the BTS applies the values T3105 = 235 msec and NY1 = 9 201 . This means that. to avoid overflows of the BTSE alarm buffer due "UI buffer overflow" alarms from subsystem U2. in case of unsuccessful access to the target channel it may (in the worst case) take more than 1 second (T3124(=320ms)+800ms) before the MS returns to the old channel. call drops would be counted even if there is no real call drop but just a reversion to old channel during handover. The signalling of the handover failure and the subsequent release of the target channel takes additional time (especially in case of MSCcontrolled handover). . When the MS has received the PHYS INFO it tries to set up the layer-2 connection in the target cell by sending the SABM via the new FACCH. . If this rule is not considered. For this reason the parameters the time determined by (NY1*T3105) must be longer than the sum of the maximum time the MS might need to return to the old channel and the time necessary for the release of the new channel (RF CHANNEL RELEASE).Any CONN FAIL is a trigger event for the TCH drop counter NRFLTCH and the SDCCH drop counter NRFLSDCC. If all these attempts fail. . regardless the values of the two BTS attributes contained in the BSC database. The combination of the values NY1=30 and T3105=MS10-10 has turned out to improve the ‘handover speech gap’ in case of BSCcontrolled intercell handover as it avoids the ‘bombardement’ of the MS with unnecessary FACCH messages (that ‘steal’ the frames of the normal speech channel). a correct setting for SDCCH leads to a insecure and potentially slow handover procedure for TCH.

5 sec SEC5 = 5s range: 0. To avoid these unnecessary CONNECTION FAILURE INDICATIONs. Subsequently the BTS acknowledges the DISCONNECT message towards the MS by an UA and informs the BSC by sending the RELEASE INDICATION message.08 Default value changed in BR8.255 default: HLFSEC-1 Reference: GSM 04. the default value HLFSEC-8. After receipt of the CHANNEL RELEASE message the MS sends a DISCONNECT message to the BTS to disconnect the FACCH. The BSC stops T3109 when it has received the RELEASE INDICATION from the BTS. object: units: BTS [TIMER] MS100 = 100 ms HLFSEC = 0. which indicates that the MS has sent the DISCONNECT message on the main signalling link. Therefore it is recommended to set T3111 to the default value (HLFSEC-1). starts T3109 and deactivates the SACCH. the BSC deactivates all channels for this MS by sending the RF CHANNEL RELEASE message to the BTS. e.255 default: HLFSEC-8 Reference: GSM 04. T3111: This timer is used to delay the radio channel deactivation in the BSC after release of the main signaling link on the Um. it is recommended to set T3109 to a small value. As a higher value of T3111 leads to a delay of the RF CHANNEL RELEASE message it simultaneously leads to an extension of the queuing time.0! T3109: This timer is used by the BSC during the dedicated channel release procedures initiated by the MSC after O&M intervention or radio link failure conditions.5 sec SEC5 = 5s range: 0. T3109 purpose: timer for forced deactivation of radio channels in case of communication loss towards the MS start: sending of the CHANNEL RELEASE message expiry action: sending of the RF CHANNEL RELEASE message T3111=HLFSEC-1. On receipt of the RELEASE INDICATION the BSC stops timer T3109 and starts timer T3111.. Thus T3111 has an impact on the feature 'Queuing' (see also parameters EQ (SET BTS [OPTIONS]) and BSCT11PUB (SET BSC [TIMER])): the longer the release procedure for an existing call takes. A released TCH is 'available' for a queued TCH request if the BSC has received the RF CHANNEL RELEASE ACKNOWLEDGE for the released TCH. The sole purpose of timer T3111 is to let some time for the acknowledgement of the disconnection (by an UA) and to protect the channel in case of loss of the acknowledge frame. security period for acknowledgement of the main signalling link disconnection start: receipt of the RELEASE INDICATION message expiry action: sending of the RF CHANNEL RELEASE message T3111 purpose: Note: The higher the value of T3111 is the longer the call release procedure takes. During the call release procedure the BSC sends the CHANNEL RELEASE message. The purpose of T3109 is to ensure the release of the radio channel in situations in which the MS cannot confirm connection release messages any more as the dedicated Um signalling connection has already been lost.08 Note: If a CONNECTION FAILURE messages is received from the BTSE during an ongoing release procedure the PM counters count a TCH loss (NRFLTCH) although there is no real TCH loss. After receipt of a CLEAR COMMAND message from the MSC or a detection of a lower layer failure the BSC sends a CHANNEL RELEASE message to the MS.g. On expiry of T3111 the BSC deactivates the radio channels by sending the RF CHANNEL RELEASE message to the BTS. the later a queued TCH request can be served. object: units: BTS [TIMER] MS100 = 100 ms HLFSEC = 0.T3109=HLFSEC-8. If T3109 expires.. 202 .

Timer for notification channel.TSYNC > ALARMT2 (see CREATE LICD) This setting is necessary in order to avoid call release before PCM alarm detection. If three consecutive DL TRAU frames have not been correctly received in the BTS the synchronization between TRAU and BTS (see explanation for TSYNCR) is considered as lost. If it expires. When a VGCS call was set up in a cell and one of the ASCI subscribers wants to talk. TSYNC. The value TNOCH=1 is recommended because test experiences have shown that other values can cause mobile problems. If this is the case the BTS starts TSYNCDL and waits for the receipt of correct downlink frames.18 TNOCH=1. object: unit: range: default: BTS [TIMER] 1 SACCH multiframe 1-254 1 Default value changed in BR8. For further details about the NCH and its function.4kbit/s data calls. The number of VGCS UPLINK GRANT message repetitions is defined by parameter NRPGRANT (see above).10000 1000 Timer grant. it starts the timer TGRANT and waits for a correctly decoded message from the MS (normally SABM with TALKER INDICATION included). When TSYNCDL expires the BTS sends a CONNECTION FAILURE INDICATION with cause ‘Remote Transcoder Failure’ to the BSC. If no correctly decoded message is received from the MS before expiry of TGRANT. Rule: TSYNCR < TSYNCDL (Recommendation TSYNCDL=1000) Note: According to GSM the timer TSYNCDL shall also be used for EFR calls.10000 1000 (recommended value >200) TSYNCDL=1000. Note: For 14. The current SBS implementation deviates from this recommendation as for EFR connections the timer TSYNC is used. the BTS repeats the VGCS UPLINK GRANT message and restarts TGRANT. object: unit: range: default: reference : BTS [TIMER] 10 ms 1-254 4 GSM 04. the MS sends an UPLINK ACCESS message via the FACCH of the ASCI Common TCH and waits for the receipt of the VGCS UPLINK GRANT message.HR and EFR) and data calls except 14.0! TSYNC=1000. The NCH is located within those CCCH blocks that were reserved for AGCH (NBLKACGR) and is used to inform the ASCI MSs in the cell about the currently ongoing ASCI VBS/VGCS group calls and the currently activated ASCI Common TCH(s). When the BTS sends the VGCS UPLINK GRANT message. he starts the ‘Talker Change’ procedure by pressing the PTT button on the mobile phone to request an uplink TCH. Rules: . It corresponds to the timer T3115 described in the GSM Standard.. object: unit: range: default: BTS [TIMER] 10ms 10.4 kbit/s data calls and AMR calls. please refer to description for parameter NOCHFBLK. this timer replaces the timer TSYNC in case of 14. the BTSE reports a CONNECTION FAILURE INDICATION with cause ‘remote transcoder failure’ to the BSC and the connection is released. As a result.TGRANT=4. TSYNC downlink. this parameter is only relevant if the ASCI feature is enabled (see parameter ASCISER in SET BTS [CCCH]) and determines minimum repetition period for messages on the Notification Channel (NCH).4kbit/s data calls and AMR calls TSYNC is replaced by the timer TSYNCDL (see below). The BTSE starts this timer if 3 downlink TRAU frames have not been correctly received from the TRAU and it is reset if a correct frame is received again (It is only used if a BTS-TRAU traffic connection is established). this timer is used by the BTSE to supervise time-out of TRAU frame handling for standard speech calls (FR. TSYNCDL is stopped when the BTS has received the first correct DL TRAU frame. this parameter is only relevant if the ASCI feature is enabled and only affects VGCS calls (see parameter ASCISER in SET BTS [CCCH]). object: unit: range: default: BTS [TIMER] 10ms 10. 203 ..

When the BTS receives the first downlink TRAU frame with the control bit ‘uplink frame error’ set it starts TSYNCUL and waits for the UFE bit to disappear in the subsequent frames. TSYNC uplink.4 kbit/s data calls and AMR calls.TSYNCR=400..10000 1000 (recommended value >150) TSYNC for resynchronization. this timer is used by the BTS to supervise time-out of TRAU datalink (traffic) at connection establishment or handover. the BTS loses the synchronization for the 14.4.TTRAU > ALARMT2 (see CREATE LICD) This setting is necessary in order to avoid call release before PCM alarm detection. If three consecutive UL TRAU frames have not been correctly received in the TRAU the synchronization between TRAU and BTS (see explanation for TSYNCR) is considered as lost.. object: unit: range: default: BTS [TIMER] 10ms 10. TTRAU. this timer is used for 14. If this is the case the TRAU sets the control bit 'uplink frame error ' (UFE) in the downlink TRAU frames towards the BTS. Rules: . object: unit: range: default: BTS [TIMER] 10ms 10. Rule: TSYNCR < TSYNCUL (Recommendation TSYNCUL=1000) Note: According to GSM the timer TSYNCUL shall also be used for EFR calls.10000 1000 TTRAU=1000. If TTRAU expires. the BTSE reports a CONNECTION FAILURE INDICATION with cause ‘remote transcoder failure’ to the BSC and the connection is released. this timer is used only in case of 14. TSYNCUL is stopped when three correct DL TRAU frames without the UFE have been received.4 kbit/s data calls. When this synchronization process is regarded as finished the BTS and TRAU switch over to the exchange of 'extended' TRAU frames. the resynchronization process is restarted again. . After receipt of the CHANNEL ACTIVATION message the BTSE starts the timer TTRAU and starts sending uplink TRAU frames towards the TRAU. When the BTSE receives the first downlink TRAU frame from the TRAU it stops TTRAU again.4 kbits/s TRAU frames it starts timer TSYNCR and restarts the synchronization process by transmitting standard TRAU frames towards the TRAU. In the normal case this synchronization process is not repeated. kbit/s data connection BTS and TRAU exchange standard TRAU frames for synchronization. When TSYNCUL expires the BTS sends a CONNECTION FAILURE INDICATION with cause ‘Remote Transcoder Failure’ to the BSC. Rule: TSYNCR < TSYNCUL and TSYNCR < TSYNCDL Note: According to GSM the timer TSYNCR shall also be used for EFR calls. The current SBS implementation deviates from this recommendation as for EFR connections the timer TSYNC is used.TTRAU > T8 and TTRAU > T10 (for T8 and T10 see command SET BSC SET BSC [TIMER]) This setting is necessary to ensure that a signaling failure (T8 and T10) is detected before transcoder failure (TSYNC and TTRAU) 204 . If the synchronization could not be reestablished before expiry of TSYNCR.. When the connection is re-synchronized BTS and TRAU start to send extended TRAU frames again and TSYNCR is stopped. The current SBS implementation deviates from this recommendation as EFR connections are handled in exactly the same way as FR connections. If.10000 400 TSYNCUL=1000. object: unit: range: default: BTS [TIMER] 10ms 10. however. At the beginning of every 14.

1450ms] The BTS stops the timer when the uplink is free again and also no talker is in the cell on a dedicated channel. 205 . i. The frequency of this UPLINK FREE message sending is defined by the parameter VGRULF in the following way: The parameter VGRULF plus an offset of 440 ms defines the repetition rate of sending this message. the BTS limits the maximum repetition rate to 1/1450ms. If an ASCI MS has started the ‘Talker Change’ procedure (i.e. object: unit: range: default: BTS [TIMER] 1 1. see parameter ASCISER in command SET BTS [CCCH]). Recommended value: VGRULF=1.e. UPLINK FREE repetition rate = MIN [(440ms+(VGRULF∗10ms)). During the ‘Uplink Reply’ procedure the BTS sends the UPLINK FREE message (with ‘Uplink access request’ included) via the FACCH of the ASCI Common TCH and repeats it periodically. the ASCI subscriber has pressed the PTT button..100 1 Default value changed in BR8. if required. this parameter is only relevant for ASCI (see parameter ASCISER in command SET BTS [CCCH]) and represents a timer which the BTS uses for the ASCI ‘Uplink Reply’ procedure (see parameter ASCIULR in command SET BTS [CCCH]). the UL is not used by any other ASCI MS in the cell and a ‘Talker Change’ procedure can be started. the ASCI MS has sent the UPLINK ACCESS message via the ASCI Common TCH) and the UL TCH was successfully allocated.TUPLREP=20. 60 20 VGRULF=1. if enabled. For further details about the functional sequence of the Uplink Reply procedure and the use of the timer defined by TUPLREP please refer to the descriptions provided for parameter ASCIULR (see command SET BTS [CCCH]). object: unit: range: default: BTS [TIMER] 1s 5. During an ongoing VGCS call the BSC sends the UPLINK FREE message to the BTS which periodically sends this message via the ASCI Common TCH in order to inform the ASCI MSs in the cell that the uplink is currently free. The time period between two consecutive transmissions of the UPLINK FREE message is determined by the parameter TUPLREP.. this parameter is only relevant if the ASCI feature is enabled (see parameter ASCISER in command SET BTS [CCCH]) and is used for the repetition of the UPLINK FREE message during the ‘Talker Change’ procedure within a VGCS call (ASCI service subscriber presses the PTT button on the ASCI phone. Voice group uplink free.0! Timer for uplink reply. the BSC sends the UPLINK BUSY message via the DL of the ASCI Common TCH.

If the number of unavailable SDCCHs exceeds the entered threshold the alarm message UNAVAILABLE RADIO SIGNALLING CHANNELS THRESHOLD MINOR.All mobiles in ‘idle’ mode perform a cell reselection .100). Cell barred. this has the following consequences: .Existing calls are continued and handovers to this cell are still possible but as soon as the busy MSs return to idle mode they perform a cell reselection. Instead. Um radio signaling channels monitoring thresholds. the alarm messages UNAVAILABLE ABIS TCH THRESHOLD MINOR.g.: all TCHs locked or all SDCCHs locked A cell is also barred for about 10s if the hopping mode changes (e. object: range: default: Reference: BTS [OPTIONS] TRUE. Please see parameter HOPP in command SET BTS [OPTIONS] for further details. object: range: default: BTS [OPTIONS] ENABLED(1. 165 and 166) are output. The entered threshold value represents the percentage of unavailable SDCCHs in the BTS. MAJOR or CRITICAL (error ID 102.08 206 . The logical group “[OPTIONS]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . the MS stays in the cell but rejects all call attempts by the subscriber.g. object: range: default: BTS [OPTIONS] ENABLED(1.Setting the cell specific optional features: < Most of the values are of Boolean type and are broadcast to the MSs on the BCCH. DISABLED ENABLE(30) (minor) ENABLE(60) (major) ENABLE(90) (critical) CELLBARR=FALSE.2.100). The entered threshold value represents the percentage of unavailable terrestrial traffic channels on the Abis. If the number of unavailable terrestrial traffic channels exceeds the entered threshold. too. major and critical QOS alarms on the PCMB link.08 GSM 05. DISABLED ENABLE(30) (minor) ENABLE(60) (major) ENABLE(90) (critical) BSMONTH= ENABLED(30)-ENABLE(60)ENABLED(90). Notes: . the value TRUE indicates that the cell is barred and camping or any other access to the cell is forbidden. MAJOR or CRITICAL (error ID 164. If the SYSINFO indicates that its access class is barred. The threshold values can only be assigned if the previous attribute is set to ENABLE. 118 and 162) is output. it immediately performs a cell reselection..RACH access to the cell is not allowed anymore .0 The DBAEM does not group the command parameters into ‘packages’ anymore.. due to automatic or manual disabling of frequency hopping). determines the state and the threshold values for the minor. These conditions could be e. > Attention: Since BR6.3 and 4) in the IE ‘RACH Control Parameters’. Abis-interface monitoring thresholds. all parameters of the previous ‘BTS packages’ were moved below the object BTS and appear in the DBAEM in the CREATE BTS command. major and critical QOS alarms for the radio signaling channels of the BTS. SET BTS [OPTIONS]: NAME=BTSM:0/BTS:0. determines the state and the threshold values for the minor. Object path name. FALSE FALSE GSM 04. The threshold values can only be assigned if the previous attribute is set to ENABLE. . This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 1. If a cell is set to ‘barred’ in the SYS_INFO.A cell can be set to 'barred' by the BSC automatically if certain conditions are fulfilled. BMONTH= ENABLED(30)-ENABLE(60)ENABLED(90).For the MS there is a big difference between a barred cell and a barred access class (see parameter NALLWACC)! When the MS receives the “cell barred” indication in the SYSINFO.

With a call re-establishment procedure the MS tries to set up a new radio connection to the BSS directly after a call drop (which might have occurred e. due to sudden loss of a radio path in e.5.) . Whether a call reestablishment can be attempted or not depends on the call control state.08 DIRTCHASS=FALSE. Setting DIRTCHASS to SDCCHMS means that direct TCH assignment is enabled but disabled for the cause 'answer to paging any channel' of the CHANNEL REQUIRED message (since SDCCHonly MS may be supported by the network). SDCCHMS NOSDCCHMS FALSE Call re-establishment allowed. It is then a task of the 'anchor' MSC (i. For call setups with direct TCH assignment. as described in GSM Rec. For this. A low value of radio link time-out (see parameter RDLNKTO in command CREATE BTS [BASICS]) increases the number of call reestablishments because a decrease of RDLNKTO leads to an earlier declaration of radio link failures. The only information about the MSs speech version capability which is available at this point of time is included in the ‘Establishment cause’ IE within the included CHANNEL REQUEST 207 .3 and 4) in the IE ‘RACH Control Parameters’. Inhibiting call reestablishment is a possibility to reduce the traffic load in the cell since call reestablishment causes considerable signaling load on the network. If in this case no TCH is available for the IMMEDIATE ASSIGNMENT procedure. the TCHs are first searched in in the SLL defined for signalling (see SLLPRM) and. object: range: default: BTS [OPTIONS] FALSE. Notes: .e.2. the MS might set up the new call in a different BTS. If ‘Direct TCH Assignment’ is enabled the TCH is first of all assigned by an IMMEDIATE ASSIGNMENT (not by ASSIGNMENT COMMAND!) and the FACCH associated to the TCH is used as main DCCH for the call setup control messages.In case of Direct TCH Assignment the BSC has to decide about the TCH type (FR.Interworking of ‘Service Dependent Channel Allocation’ and Direct TCH Assignment If Direct TCH Assignment is enabled the SLL associated to ‘signalling’ is used for allocation (see command SET BTS [SERVICE] for details). the MS sends a CM REESTABLISHMENT REQUEST (instead of a CM SERVICE REQUEST) to the network. Direct TCH assignment enabled.any channel' of the CHANNEL REQUIRED message (since SDCCHonly MS is not supported by the network). section 5. . the MSC which served the dropped call) to quickly recognize the old call context and to interconnect the new radio path to the existing connection before the call is terminated by the end users or by expiry of call supervision timers.CREALL=NOTALLOWED object: range: BTS [OPTIONS] ALLOWED. Setting DIRTCHASS to NOSDCCHMS means that direct TCH assignment is enabled also for the cause 'answer to paging .g. This SLL should be defined by the operator in such a way that the TRXs with less SDCCH and more TCHs are listed at the top. Depending on the radio conditions. ‘Direct TCH Assignment’ means: assignment of a TCH without previous assignment of an SDCCH.4. When the setup phase of the call is completed the TCH is put into service by a CHANNEL MODE MODIFY message.08. the channel is changed after receipt of this message (as it is done during normal change from SDCCH to TCH when direct assignment is not applied. 04.g. HR) when it receives the CHANNEL REQUIRED message.There is no impact on directed retry (see parameter ENFORCHO in command SET BSC [BASICS]) if direct TCH assignment is enabled. the BSC allocates an SDCCH and the directed retry can be performed. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 1. if the allocated channel does not perfectly match to service type requested in the ASSIGNMENT REQUEST message. a tunnel). NOTALLOWED default: NOTALLOWED Reference: GSM 04. indicates whether the MS may try to start a Call re-establishment procedure.

especially when it is enabled for the establishment cause ‘answer to paging’ 208 . when Direct TCH Assignment is enabled. Moreover. . e. In other words: it happens that that BSC assigns a TCH for signaling procedures. This can happen.message. for an IMSI DETACH INDICATION (which is sometimes indicated with the same establishment cause like MOC) or for SMS-MT (the BSS cannot distinguish SMS-MT from normal MTCs as the very first signaling messages are exactly the same for both procedures). For this reason Cell Load Dependent Activation of HR (see parameters EHRACT and EHRACTAMR in command CREATE BTS [BASICS] in command) does not work when Direct TCH Asssignment is enabled.g. At this point of time the BSC does not check the current TCH load in the cell to decide about the allocation of FR or HR but assigns a TCH type in correspondence with the ‘establishment cause’ value received in the CHANNEL REQUIRED message.08 for details).Direct TCH Assignment also has other disadvantages: In some cases the ‘establishment cause’ values contained in the CHANNEL REQUEST messages (especially if the parameter NECI (see command SET BSC BASICS])is set to TRUE) do not allow a clear distinction between calls (that require a TCH) and signaling procedures (for which an SDCCH is sufficient). depending on the type of MS. This information is very restricted with respect to the grade of detail and the MS capabilities and preference (see GSM04. although these procedures could be processed using an SDCCH only . several mobile types cause problems.

Both the MS and the BTS indicate in the MEASUREMENT REPORT resp.e. the MS (for DTX downlink) as well as the BTS (for DTX uplink) have to consider the utilization of DTX during the radio measurement process. So-called VAD (Voice Activity Detection) algorithms are implemented in the MS as well as in the TRAU which are able to distinguish noisy speech from real noise even in a noisy environment. Note: DTXDL is not allowed on the BCCH TRX. thus each direction of transmission is occupied about 50% of time. specifies whether “discontinuous transmission downlink (DTX downlink)“ is enabled for FR calls in the BTS. This low rate is enough to encode the background noise. RESULT messages whether in the current measurement period DTX is active (speech transmitted) or not (silence). the FULL values or RXLEV and RXQUAL may indicate bad 209 . This means that. HANDOVER REQUEST messages. From these parameters the receive sides generates a similar noise called “ comfort noise “ during periods without radio transmission. FALSE FALSE GSM 04.08 GSM 05. assuming that every 20ms a decodable TDMA frame is received. During a normal voice call. The BTS sets the DTX flag to ‘DTX employed’ if DTX was applied in at least one TDMA frame in the measurement period.31 GSM 08. The goal is to reduce the interference in a cell and to reduce the MS power consumption (DTX uplink only). This is done because ‘total silence’ is experienced as considerably irritating by the listener. the participants speak only 50% of time. This means instead of one frame of 260 bits per 20 ms only one frame per 480 ms is sent. as long as the voice inactivity between BTS and MS lasts. The VAD algorithms “isolate” the background acoustic noise in order to transmit characteristic parameters of this noise to the receive side. The following example might illustrate this time behaviour: BTS <-> MS SSSSC 480 ms C C 480 ms 480 ms C SSC C 480 ms C 480 ms S TRAU <-> BTS SSSCCCCCCCCCCCCCCCSSCCCCCCCS S = speech frame C = comfort noise frame 20 ms Impacts of DTX on Measurement Processing in the BTS and MS: When DTX is used.60 Discontinuous transmission downlink for FR calls enabled. if DTX was active in a specific measurement period (silence).08 GSM 06. DTX is a mode of operation where the transmitters are switched on only for those frames containing useful information. the MSC must declare DTX downlink ‘allowed’ in the DTX DL FLAG in the ASSIGNMENT REQUEST resp. As a precondition for operation. Between TRAU and BTS the comfort noise frames are sent every 20 ms. Both MS and BTS provide two different measurement values for RXLEV and RXQUAL: the so-called FULL and SUB values. The status of DTX downlink (applied/not applied) can be seen from the IE ‘Channel Mode’ in the CHANNEL ACTIVATION message on the Abis. General remarks about DTX: DTX was originally developed for satellite systems. These so-called SID frames (Silence Description Frames) are sent at the start of every inactivity period and repeated every 480 ms. DTX downlink must also be activated in the MSC. 1) The FULL values represent the measurements that were made on the TCH and the SACCH frames with a sample period of 20ms. DTX reduces the speech data rate from 13 kbit/s to 500 bit/s.DTXDLFR=FALSE. object: range: default: Reference: BTS [OPTIONS] TRUE. i.

Due to their higher statistic reliability it is possible to weight the FULL values in the Power Control and Handover averaging process higher than the SUB values. if the BTS applies DTX for a specific downlink measurement period.0 onwards. Attention: To allow an easier analysis of Abis measurement messages. 2) The SUB values represent the measurements that were made on the SACCH frames. the BTS does not only consider the SACCH frames but also the speech frames carrying reals speech (as the BTS can recognize these frames from their contents). As a general rule. Impacts of DTX on the Power Control and Handover Decision As the FULL values do not mirror the real radio conditions in measurement periods with active DTX (silence) the BTS has to use the SUB values for these measurement periods for the Power Control and Handover Decision Process. On the other hand.the DTX UL flag is valid for the uplink measurement results included in the same message! continuation see next page… 210 . To increase the reliability of the SUB values for AMR calls. This is done by the so-called ‘DTX-weighting factor’ included in the parameters PAVRLEV and PAVRQUAL (see SET PWRC) and HOAVLEV. The higher the number of TDMA frames with active DTX. HOAVQUAL and ALEVFULHO (see SET HAND [BASICS]). from BR8. even if the radio conditions are excellent. it uses the SUB values of the subsequent downlink MEASUREMENT REPORT. which are repeated every 480 ms and which carry the SYSTEM INFORMATION TYPE 5 and 6 (downlink) and the MEASUREMENT REPORTs (uplink).radio conditions due to missing speech frames. but have a lower statistic reliability than the FULL values that were measured during speech periods. In measurements periods without active DTX (speech frames transmitted) the BTS uses the FULL values for the PWRC and HO decision. If the MS indicates “DTX used“ in a specific MEASUREMENT REPORT. the SUB values always mirror the real radio conditions. the BTS has to consider the SUB values of the subsequent uplink MEASUREMENT RESULT (480 ms later) for the Power Control and Handover decision. this “cross-relation” has been removed by a BTS-internal “framematching” process which shifts the associated DTX flags and measurements results to one and the same MEASUREMENT RESULT message. the worse the RXLEV/RXQUAL values will look. in the MEASUREMENT RESULT and TRACE MEASUREMENT RESULT messages that are (optionally) sent from the BTS to the BSC via the Abis (see parameters RADIOMG in command CREATE TRX and TRACEMR in command SET BSC) .the DTX DL flag is valid for the downlink measurement results included in the same message . This means that .

31 measurement values used for UL PWRC and HO decision measurement values used for DL PWRC and HO decision Discontinuous transmission downlink for HR calls enabled. shall not for HR TCHs). e. For further details see parameter DTXDLFR. specifies whether ‘discontinuous transmission (DTX)’ (explanation see DTXUL) is enabled for HR calls in the BTS. FALSE FALSE GSM 04. shall not for HR TCHs). during speech pauses.08 GSM 05. (MS shall not use DTX for Full Rate TCHs.g. For more general details about DTX please refer to the descriptions provided for the parameter DTXDLFR. object: range: default: Reference: BTS [OPTIONS] TRUE. (MS shall not use DTX for FR TCHs. DTXUL=SHLFSHNH.08 GSM 06. specifies whether discontinuous transmission (DTX) shall be used by the MS. (MS shall use DTX for FR TCHs. shall for HR TCHs). moreover.08 GSM 05.The following example diagram may illustrate the principle: (TRACE) MEASUREMENT RESULT Uplink Measurements: DTX (DL) indicator: DTX employed RXLEV FULL: <rxlev-full> RXLEV SUB: <rxlev-sub> RXQUAL FULL:<rxqual-full> RXQUAL SUB: <rxqual-sub> Downlink Measurements: DTX (UL) used: not used RXLEV FULL: <rxlev-full> RXLEV SUB: <rxlev-sub> RXQUAL FULL:<rxqual-full> RXQUAL SUB: <rxqual-sub> DTXDLHR=FALSE. This feature is mainly used to save battery capacity in the MS. may use for HR TCHs). Meaning of the possible values: MAYFSHNH SHLFSHNH SHNFSHNH MAYFMAYH SHLFSHLH SHNFSHLH (MS may use DTX for FR TCHs.08 GSM 06. object: range: BTS [OPTIONS] MAYFSHNH SHLFSHNH SHNFSHNH MAYFMAYH SHLFSHLH SHNFSHLH default: SHLFSHNH Reference: GSM 04. (MS may use DTX for FR TCHs. it helps to keep the overall radio interference on a low level.31 Discontinuous transmission uplink enabled. 211 . shall for Half Rate TCHs) This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3) and on the SACCH (SYSTEM INFORMATION TYPE 6) in the IE ‘Cell Options’. (MS shall use DTX for FR TCHs. Discontinuous transmission is a mode of operation in which the transmitters turn down the sending power if the frames do not contain user information. shall not for HR TCHs).

the CLASSMARK REQUEST procedure is started to figure out whether the MS also supports the other cipher algorithms allowed in the MSC. The CLASSMARK REQUEST procedure is only started on particular conditions: in the Siemens MSC it is only triggered. LOCATZION UPDATE REQUEST) to provide the network with additional classmark information. PAGING RESONSE.0! Enable early classmark sending.EARCLM=TRUE. CM SERVICE REQUEST. As the CLASSMARK 2 information is already included in the CM SERVICE REQUEST message and the PAGING RESPONSE but not in the LOCATION UPDATE REQUEST message.08 Default value changed in BR8. object: range: default: reference: BTS [OPTIONS] TRUE. i.g. multi-band mode or HSCSD (‘multislot capability’). the MSC sends a CLASSMARK REQUEST message (BSSMAP) to the BSC during the call setup. of course. The BSC forwards the request in form of a CLASSMARK ENQUIRY message (DTAP) to the MS. A5/3) are supported. As the CLASSMARK 1 information included in the LOCATION UPDATE REQUEST message only contains the A5/1 capability. which was handed over from 2G to 3G and returns to the 2G network by a 3G-2G handover. when these entries. which means that the mobile station sends a CLASSMARK CHANGE message immediately after the first transaction request message (e. Changing this flag just changes a flag in the BCCH (SYSTEM INFORMATION TYPE 3) in the IE ‘SI 3 Rest Octets’. as the command MOD MPRDDAT can only be entered in the 'Installation Mode' of the MSC.e. only possible for those MSs that support the early classmark sending option. this parameter indicates whether the “Early Classmark Sending” is enabled or disabled. Another possibility is to change the setting by MSC patch. if in the MSC mobile project description data (MPRDDAT) the set of supported cipher algorithms is different from ‘A5/1 only’. Attention: A CLASSMARK ENQUIRY procedure can also be triggered by the BSC without receipt of a CLASSMARK REQUEST from the MSC. When this is the case. this.g. indicate that other ciphering algorithms (A5/2. however. This can happen when an MS. This is. The BSC forwards this information to the MSC within the BSSMAP message CLASSMARK UPDATE. the CLASSMARK CHANGE / CLASSMARK UPDATE procedure can also be explicitly requested by the MSC. the HANDOVER REQUEST message does 212 . Notes on CLASSMARK REQUEST procedure (started by MSC) For Location Update procedures. These UMTS radio capabilities are requested from the MS by the IE ‘Classmark Enquiry Mask’ which is included in the CLASSMARK ENQUIRY message. which answers by starting the usual CLASSMARK CHANGE procedure. This flag instructs the Mobile Stations to start the “Early classmark sending” procedure automatically for every call transaction. In the Siemens-MSC it is not possible to disable the CLASSMARK REQUEST/CLASSMARK ENQUIRY procedure by database command. The MSC starts the CLASSMARK REQUEST procedure to interrogate the CLASSMARK 2 information from the MS. Thus the flag simultaneously enables/disables the multiband handovers. The ‘Controlled Early Classmark Sending’ option must be implemented in mobiles that support e. The only way to disable this procedure is to switch off the A5/2 / A5/3 support. If in this case. Remarks on 2G-3G network architectures The CLASSMARK CHANGE / CLASSMARK UPDATE and CLASSMARK REQUEST /CLASSMARK ENQUIRY procedure is also of special interest for 2G-3G network architectures as the network needs to be informed about the 3G radio capabilities of the MS. FALSE TRUE GSM 04. cannot be done in normal operation. the MSC starts the CLASSMARK REQUEST procedure only for Location Update.

the MS will send the CLASSMARK CHANGE again. Timing and interaction of CLASSMARK REQUEST and ‘Early Classmark Sending’ procedures Experiences from real life Abis traces confirm that normally the CLASSMARK CHANGE message due to 'Early Classmark Sending' is normally sent after the MSC has sent the CIPHER MODE COMMAND (or. parameter ‘Emergency Call allowed’. The resulting CLASSMARK CHANGE message will in this case be forwarded to the MSC in the CLASSMARK UPDATE message as usual. When the MSC sends a CLASSMARK REQUEST message due to the cipher algorithm settings. if authentication is performed. this parameter determines whether emergency calls are allowed to all MSs or restricted to MSs belonging to access classes in the range 11 to 15 .3 and 4) in the IE ‘RACH Control Parameters’.EC=FALSE. the CLASSMARK REQUEST procedure must have been completed prior to the transmission of the CIPHER MODE COMMAND. the BSC may autonomously request these data by an own CLASSMARK ENQUIRY procedure. after the AUTHENTICATION REQUEST).08 GSM 02.2. FALSE FALSE GSM 04.11 not contain the suitable 3G radio capability data in the ‘Old BSS to new BSS Information’ IE. This parameter is sent on the (SYSTEM INFORMATION TYPE 1. The value 'TRUE' indicates that emergency calls are restricted. Attention: EC=FALSE means 'emergency calls allowed' EC=TRUE means 'emergency calls not allowed' 213 . On the other hand. Emergency call restricted. it also happens that an MS sends a CLASSMARK CHANGE message to the network due to ‘Early Classmark Sending’. .If the MS receives CLASSMARK ENQUIRY after having sent the CLASSMARK CHANGE message due to 'Early Classmark Sending'. The procedures 'Early Classmark Sending' and CLASSMARK ENQUIRY (Abis message that follows the A-interface message CLASSMARK REQUEST) are independet from each other. object: range: default: Reference: BTS [OPTIONS] TRUE. even if a CLASSMARK ENQUIRY hes been received and answered by another CLASSMARK CHANGE message before.

. . Notes: . The combination of these parameters determines whether an incoming TCH request may lead to a forced HO of an existing lowpriority call for TCH resource provision for high-priorized TCH requests: If the PCI is set to ‘preemption allowed’ for the incoming CS TCH request. the BSC tries to satisfy the TCH request in the following sequence: 1) preemption of a low priority CS call.The Preemption Capability Indicator (PCI) applies to the allocation of resources for an event and indicates if the event is able to trigger the preemption of radio resources. Priority Level 1 being the highest value. . The ‘Priority’ IE contains the following entries: . A priority table which correlates the subscriber and event dependent priorities and the associated parameter settings for the ‘Priority’ IE is maintained in the MSC. object: range: default: BTS [OPTIONS] ENABLED. . If Preemption is allowed and an incoming highly priorized TCH request meets a TCH congestion in a cell. the BSC will start the procedure ‘forced handover due to preemption’ for the ongoing call to provide the resource to the new incoming call. In GSM different priorities and access types are supported via the ‘Priority’ IE which is (optionally) transmitted in the ASS REQ and HO REQ message. .The forced handover due to preemption is only attempted if the flag ENFORCHO (SET BSC [BASICS]) is set to ENABLE.The Priority Level (PL) is subdivided in 14 different levels. determines whether the feature ‘Preemption’ is enabled. the handover completion may take a long time due to the additional handover of the preempted call in the target cell. . If this is not the case the preempted (low-priority) call is immediately released. if not possible then 3) (WPS) queuing 4) downgrade of multislot calls (GPRS/HSCSD) may be periodically attempted in parallel and queued calls can be served when down grade is successfully completed.If the feature ‚preemption’ is used for MSC controlled handovers. Please refer to the parameters EQ (for (WPS) queueing) in this command.The Preemption Vulnerability Indicator (PVI) applies for the entire duration of a connection and indicates whether the connection may become a target of preemption.EPRE=DISABLED.One FR call cannot preempt one HR call if one subslot is still idle. ENFORCHO (for directed retry) in command SET BSC [BASICS] and to parameter DGRSTRGY (for multislot call downgrade) in command SET BTS [BASICS].One FR call cannot preempt two HR calls. This has to be considered by setting the timer T7 (see BSCT7 see SET BSC [BASICS]) to a sufficiently high value in the originating BSC. existing calls with a lower priority are handed over to a suitable neighbour cell by a forced HO procedure with cause ‘preemption’.If a CS call request is received in a congested cell.The Queuing Allowed Indicator (QAI) is used to decide on a per call basis if queuing may be applied or not. if not possible then 2) directed retry. and if the BSC finds an existing call with lower priority level for which the PVI is set to ‘may be preempted’. . 214 . DISABLED DISABLED Enable Preemption. If the forced HO procedure is not successful for the preempted low-priority call is forced released.

In GSM different priorities and access types are supported via the ‘Priority’ IE which is (optionally) transmitted in the ASS REQ and HO REQ message.EQ=DISABLED. . incoming Inter-BSC directed retries are not queued. the TCH request can be queued. .0. and if the BSC has previously tried all other measures to free currently used TCH resources in the cell (see first ‘Note’ below). in releases up to BR7.The Preemption Capability Indicator (PCI) applies to the allocation of resources for an event and indicates if the event is able to trigger the preemption of radio resources.the priority of the received TCH request . via directed retry (see parameter ENFORCHO in SET BSC [BASICS]) are put in two different cell-specific queues based on its priority. . The sequence of queued TCH requests within this queue was determined by . Starting from BR8. If a TCH request is enqueued. incoming TCH requests for which queuing is allowed and which cannot be served by preemption (see parameter. With the WPS queueing mechanism.0.The Priority Level (PL) is subdivided in 14 different levels (1. Arrivals Arrival Arrivals No – no: WPS NS/EP WPS No no: – Public public channel? channel? channel? Yes yes Happy WPS public Served Queue Queue queue queue WPS queue public queue 215 . Every incoming TCH request contains a set of flags which determine whether a) ‘queuing’ and b) ‘preemption’ (for details see parameter EPRE below) is allowed for the TCH request. If queuing is enabled.for TCH requests of the same priority the point of tine of receipt. DISABLED DISABLED Enable (WPS) queuing.S. As a general rule. 1 the highest.. The (WPS) queuing feature is used to prevent an immediate rejection if an incoming TCH request (ASSIGNMENT REQUEST received in case of normal assignment or a HANDOVER REQUEST received in case of incoming MSC-controlled handover) cannot be served due to TCH congestion. the MSC is informed about this process by the QUEUING INDICATION message. two different queues are incoming TCH requests: one so-called ‘WPS queue’ for TCH requests from high priority subscribers and one ‘Public queue’ for TCH requests from ordinary subscribers. The ‘Priority’ IE contains the following entries: . this parameter originally enable/disable the feature ‘Queuing’ for TCH channels. 14 the lowest priority).The Queuing Allowed Indicator (QAI) is used to decide on a per call basis if queuing may be applied or not. market. object: range: default: BTS [OPTIONS] ENABLED.The Preemption Vulnerability Indicator (PVI) applies for the entire duration of a connection and indicates whether the connection may become a target of preemption. it enables the enhanced queuing feature called ‘Wireless riority Services’ (WPS) which was required especially for the U. A priority table which correlates the subscriber and event dependent priorities and the associated parameter settings for the ‘Priority’ IE is maintained in the MSC. Queuing policy Originally (i.14. The combination of these parameters determines whether an incoming TCH request may be queued: If the QAI is set to ‘queuing allowed’ for the incoming CS TCH request.0) only one queue was managed in the BSC per cell. which was introduced starting from BR8.e.

when the previously active call on one TCH resource is released) while TCH requests are queued. which defines the lowest priority level (PL) to be placed in the WPS queue. WPS or public) is full (i.the queuing time for TCH requests due to TCH assignment is deefined by parameter BSCT11PUB and . TCH requests are put into the WPS queue or the Public queue depending on their PL and are placed into the relevant queue using a first-in/first-out queuing discipline for each priority level. In other words: all incoming TCH requests with PL >= LWWPSPRI are enqueued in the ‘WPS queue’. When a previously ‘busy’ TCH becomes ‘idle’ again (i. i. If the queue is full and the new TCH request is lower than the lowest queued one. If one queue (i.the queuing time for TCH requests due to TCH assignment is deefined by parameter BSCT11WPS and . in order to 216 . the number of queued TCH requests has reached the threshold defined by the parameters QLWPS and QLPUB) and an incoming TCH request has a higher priority than at least one of the queued requests. For both queues the length and characteristics are defined by separate parameters: WPS queue: .Which priority levels are to be placed in which queue. the queues with the higher priority levels make up the WPS queue (group). then. the TCH requests in the queue are re-ordered in order to insert the new request and to remove the (youngest) lowest priority one from the respective queue (resulting in a rejection of the TCH request with an ASSIGNMENT FAILURE or HANDOVER FAILURE with cause ‘no radio resource available’).the queue length is defined by parameter QLWPUB (see below) . the ones with the lower priority levels make up the Public queue (group).e. Each queue consists of a set of queue places all having the same characteristics.e. the enqueued TCH requests are served according to the following mechanism: Starting from the beginning.e. one for each priority.the queue length is defined by parameter QLWPS (see below) . is determined by the parameter LWWPSPRI. Public queue: . the first call to be served is a TCH request in the WPS queue (if any is available). Technically each cell has 14 queues.the queuing time for TCH requests due to incoming MSC-controlled handover is deefined by parameter BSCTQHOPUB (see command SET BSC [TIMER]).e. all others are enqueued in the ‘Public queue’. These 14 queues are separated into two different queue groups as defined by LWWPSPRI according to the priority levels.the queuing time for TCH requests due to incoming MSC-controlled handover is deefined by parameter BSCTQHOWPS (see command SET BSC [TIMER]). the request is rejected in the same way as described above.

After the call is queued. The call that triggers the downgrade procedure is marked as “downgrade requested” in order to wait for the resources that will be available after successful completion of the downgrade procedure. If BSCT11WPS or BSCT11PUB expires. the queuing times are defined by separate database parameters for the two different queues (BSCT11WPS etc. the TCH request is rejected with a HANDOVER FAILURE message using the same cause ‘no radio resource available’.Interworking of the features ‘Downgrade strategy’ and (WPS) queuing When a TCH request is queued. running procedure. the resource management process periodically starts the downgrade procedure (if correspondingly enabled via parameter DGRSTRGY) on HSCSD data calls and/or (E)GPRS data calls (if any) in order to get new resources for TCH allocation. If during the ongoing downgrade procedure other TCHs become ‘idle’ again.g. a HANDOVER FAILURE message (for inc. The call marked as “downgrade requested” must in any case wait for the resources achieved by the downgrade procedure. Service List. .g. in case of Abis congestion the 217 . if not possible then 2) directed retry.). If BSCTQHOWPS or BSCTQHOPUB expires in case of incoming MSC-controlled HO. starting from the preferred layer. WPS/Public call info. The downgrade procedure is requested for the multislot calls established on the shared layers with service layer association matching to the service type of the enqueued call. the BSC tries to satisfy the TCH request in the following sequence: 1) preemption of a low priority CS call. …).) c) if the queueing time expires for the queue TCH request As mentioned above. (In these cases an ASSIGNMENT FAILURE message (for assignment requests) resp. Queued TCH requests can be discarded from a queue a) if further TCH requests with a higher priority are received or b) if (for the TCH assignment case) during the queuing time an SDCCH HO attempt fails. parameter description see below) the subsequent 3 requests will be taken from the Public queue. the BSC sends a CLEAR REQUEST message with cause ‘no radio resource available’ to the MSC and the requesting connection is released. if not possible then 3) (WPS) queuing 4) downgrade of multislot calls (GPRS/HSCSD) may be periodically attempted in parallel and queued calls can be served when down grade is successfully completed. On the other hand. If they are not present or the queue becomes empty again it will be served the WPS queue or if also this queue is empty the resource will be available for the other needs. the BSC tries. a requested sharing between WPS and Pubilc calls of 25% (reflected by the parameter setting WPSPREF=4-1. ENFORCHO (for directed retry) in command SET BSC [BASICS] and to parameter DGRSTRGY (for multislot call downgrade) in command SET BTS [BASICS]. to serve the queued TCH requests by a multislot call downgrade procedure (e. these resources cannot be assigned to the call marked as “downgrade requested”.realize e. Please refer to the parameters EPRE (for preemption) in this command. HO requests) with cause ‘no radio resource available’ is sent to the MSC. when present. Notes: . (E)GPRS downgrade: Every call is put in the queue with its relevant data (channel request type. when possible.If a CS call request is received in a congested cell.

The TX and RX paths are tied together by switching TX & RX at the same time.If the BSC receives an INTERCELL HANDOVER CONDITION INDICATION from the BTS during the queuing time. .In case of MSC-controlled HO the Siemens MSC first attempts the HO REQ procedure for all target cells (previously received in the HO RQD message) with the ‘Queuing Allowed Indicator’ set to ‘not allowed’! Only if these attempts are not successful the MSC repeats the HO REQ procedure with the ‘Queuing Allowed Indicator’ set to ‘allowed’! This means that only for this second cycle queuing can be performed by the BSC. Basband Frequency Hopping features a continuous switching of the BBSIG responsible for a particular TRX to different TPUs. Downlink data is pre-processed in the TRX related CU. i. SYNHOP BBHOP multislot downgrade procedure will be requested on all layers of this cell associated to the multislot service layer list and in the extreme case also on other cells of the same BTSM. Note: The implementation of frequency baseband hopping shows the following difference regarding the two BTSE generations. a single RX path is used with multiple TX paths. Of course.the BTSplus' implementation is different to the BTS1. object: range: default: BTS [OPTIONS] BBHOP. . the TCH allocation process attempts to serve the enqueued TCH requests with the highest priority. In other words. Synthesizer Frequency Hopping features a continuous re-tuning of the TPU/CU in correspondence with the created in correspondence with the configured hopping sequence. The number of frequencies in the frequency hopping system (mobile allocation) is restricted to the number of TRXs configured in the cell. Due to the averaging effect this means that failures in the RF-TX signal path which are 218 . so there are as many TX/RX pairings for the call as the number of transmitters in use. Thus. Here baseband hopping is exclusively used in downlink direction whereas in uplink direction always synthesizer hopping is applied. The advantage of synthesizer hopping is that it is possible to define frequency hopping systems with more frequencies than TRXs are available in the BTS. Since the mobile reports the measured RXLEV_DL values with a fixed period of 480ms (= 104TDMA bursts). Other scenarios that allpow the serving of a queued TCh request are release requests of previously ‘busy’ TCHs or the ‘return to service’ of previously ‘disabled’ TCHs.By setting the parameter QLWPS=0. Synthesizer FH requires specific HW (e. it is the hopping system (FHSY) may include also channels of the BCCH TRX. for a call.in the BTS1 baseband hopping is realized by multiplexing different TPUs to one BBSIG. If no TCH can be found in the target cells. the new resource and the queued request must be compatible in terms of supported layer.0. no mapping is possible on TDMA burst base for the DL measurements. this parameter indicates whether baseband hopping or synthesizer hopping is to be used in this cell. the TCH request is discarded from the queue. the hopping is executed by switching one and the same BBSIG among different TPUs in correspondence with the configured hopping sequence (see command CREATE FHSY).g. Hopping Mode. requested band and so on. filter combiners are not allowed) and is not allowed on the BCCH-TRX. but the burst data is then sent via the CU whose carrier frequency is equal to that of the currently calculated burst. BTS1 and BTSplus: . the BSC directly searches for an idle TCH in the target cell! In other words.e. . during the queuing time no SDCCH-SDCCH handover will ever be performed. If baseband frequency hopping is used. As soon as a TCH resource returns to service or becomes ‘idle’. the BSC queuing behaviour is exactly the same as in releases < BR8.HOPMODE=BBHOP. .

3 and GSM 02.NA9. If an ‘IMSI Detach’ message is sent to the MSC the mobile subscriber is marked as ‘detached’ in the VLR. (SYSTEM INFORMATION TYPE 3) in the IE ‘Control Channel Description’. IMSI attach/detach enabled. object: BTS [OPTIONS] range: NA0. This means that the mobile subscriber is regarded as ‘reachable’ and paging is performed in case of an MTC..located in carrier specific parts may not be reliably detected in case baseband hopping is applied (both for BTS1 and BTSplus). NALLWACC=ALLALLOWED. the access class barring remains active until the access classes are unbarred by a repeated entry of the command SET BTS using the appropriate setting of NALLWACC. BSCTQHOPUB. BSCT11WPS. In the case of difference between the stored LAI and the one received on the BCCH of the current serving cell. with this parameter the access classes 1 to 15 (the access class is stored on the SIM-card: classes 1-9 are ordinary subscribers. If an ‘IMSI Attach’ message is sent to the MSC the mobile subscriber is marked as ‘attached’ in the VLR. which is a special enhancement of the feature ‘queuing’ required by the U. parameter ‘Attach/detach allowed’. market object: BTS [OPTIONS] range: 1. classes 11-15 are priorized subscribers) can be explicitly barred for default: ALLALLOWED access to the cell (except for class 10). Not-allowed access classes. The manual barring of access classes using NALLWACC is completely independent of 219 . paging is not performed in this case. a normal location updating procedure is invoked independently of the ‘attach’ flag indication. The ‘IMSI attach’ message is a LOCATION UPDATE REQUEST’ message with the parameter ‘Location Update Type’ set to ‘IMSI Attach’. The information stating which Reference: GSM 04. the subscriber only notices an immediate call rejection when he tries to set up a call. the VLR regards the mobile subscriber as ‘not reachable’ and rejects the call completion in case of MTC. i.08 classes are barred is sent on the BCCH (SYSINFO Type 1..e.11 4) in the IE ‘RACH Control Parameters’. For the ‘IMSI Detach’ procedure the message IMSI DETACH INDICATION is used. Lowest WPS Priority. LWWPSPRI=<NULL>. The IMSI attach procedure is only used if the IMSI was deactivated while the MS was in ‘idle updated’ state before switch-off and the stored Location Area Identification is the same as the one which is actually broadcast on the BCCH of the current serving cell when it is switched on again. On the other side. Notes: . BSCTQHOWPS (see command SET BSC [BASICS]) and QLWPS.S. If this parameter is object: BTS [OPTIONS] range: TRUE. QLPUB and WPSPREF (see below). On the mobile phone.08 on respectively an ‘IMSI Detach’ message when they are switched off. class 10 is a mobile emergency call. Further parameters related to the WPS feature are BSCT11PUB. i. 2. default: <NULL> It specifies the lowest Priority level to be considered in the WPS queue. in uplink direction the BTSE knows which RX path is used per received burst.NA15. This parameter is sent on the BCCH IMSIATDT=TRUE. In fact the MS will report an RXLEV_DL value which is the average of levels received from different RF-TX equipment (and so from different paths). FALSE set to TRUE the MSs are requested by the above mentioned BCCH default: TRUE parameter to send an ‘IMSI Attach’ message when they are switched Reference: GSM 04. there is no special indication on the display if the SIM’s access class is barred while the MS is already booked in. For this reason the feature “ Online Rf Loopback “ does not work if baseband frequency hopping is configured. If the MS receives the indication that its access class is barred it remains camping in the cell but it is not allowed not perform a RACH access anymore..e. this parameter is only relevant if the feature ‘Wireless Priority Service (WPS)’ is applied. 10.The access class barring using NALLWACC is a semipermanent one. NA11. <NULL> (please see parameter EQ (above) for further details).

When the MS is powered down the current value of T3212 is kept in memory.) according to the following Rule: T3212 < IDETTIM. CU) minus the power reduction (see parameter PWRRED (CREATE TRX)). Location update. A recovery in the VLR normally leads to the loss of the subscriber data. IMSI Attach). BSCTQHOPUB.. i. this parameter specifies the length of the ‘’WPS’ queue for the Wireless Priority Services (WPS) feature. . Power output thresholds.. Periodic location update is used to ensure the continuous update of subscriber data in the VLR even if the subscriber remains in the same location area. If the setting is vice versa. it immediately performs a cell reselection. Further parameters related to the WPS feature are BSCT11PUB. MOC.MDB5DB6. BTS or MSC (please see parameters BSCOVLH. By setting the parameter to its default value QLWPS=0.e. QL QLPUB=50. this parameter is only relevant if the feature ‘Wireless Priority Service (WPS)’ is applied.PWROUT=MDB10. object: range: default: BTS [OPTIONS] 1. BTSOVLH and MSCOVLH in command SET BSC). the MS stays in the cell. 220 . periodic loc. BSCT11WPS.For the MS there is a big difference between a barred cell (see parameter CELLBARR) and a barred access class! When the MS receives the “cell barred” indication in the SYSINFO. The PA supervises its actual output power and compares it to the desired value. It specifies the length of the ‘Public’ queue for the Wireless Priority Services (WPS) feature. The procedure is controlled by the timer T3212 in the Mobile Station. If the SYSINFO indicates that its access class is barred. Reference: GSM 04. M8DB default: M10DB fixed value for BS10/BS11: -6dB reducedOutputPowerThreshold range: M10DB. This timer must be set in consideration of the „Implicit Detach“ timer in the VLR (command in SIEMENS MSC: ENTR MOBTHR:IDETTIM=. i. <NULL> 0 (=WPS queuing disabled) T3212=6. When the MS is powered up the timer starts running from the value thus contained in memory.08 Queue length. The desired value. M4DB default: MDB6 fixed value for BS10/BS11: -4dB excessiveOutputPowerThreshold range: DB3.e. the BSC queuing behaviour is exactly the same as in releases < BR8.. replaced by QLPUB and QLWPS. removed in BR8.g.. the MS may be set to ‘detached’ in the VLR even before it executes a Periodic Location Update. defines three power output thresholds: outputPowerFaultThreshold = defines the minimum output power level at the PA resp. CU output power level to initiate output of a warning. <NULL> 50 QLWPS=0.255 0 means ‘infinite timeout’. 100. CU which results in an alarm output to the BTSE core unit. object: range: default: BTS [OPTIONS] 1. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3) in the IE ‘Control Channel Description’. DB5 default: DB5 fixed value for BS10/BS11: 3dB automatic access class barring due to overload situations in the BSC. CU (depending on the type of PA resp. reducedOutputPowerThreshold = defines the PA resp. M8DB. object: BTS [OPTIONS] outputPowerFaultThreshold range: M10DB. see above). T3212. Length of public queue. default: 10 = 60 min. object: unit: range: BTS [OPTIONS] 1 decihour (6 min) 0. BSCTQHOWPS (see command SET BSC [BASICS]) and QLWPS and WPSPREF (see below)..S. Length of WPS queue. excessiveOutputPowerThreshold = defines the power level when a major alarm is generated due to too high output power.0.. market (parameter EQ. timer for periodic location update. which is a special enhancement of the feature ‘queuing’ required by the U. Please refer also to parameter QLPUB (see above).. the reference for the entered thresholds is the maximum output power of the PA resp.0. 100. This timer is reset to 0 and started when a signaling activity has taken place on the radio path (e. M6DB. On expiry the MS initiates a location updating. updating is used in the cell.

market (parameter EQ. BSCTQHOWPS (see command SET BSC [BASICS]). Further parameters related to the WPS feature are BSCT11PUB. Note: Some parameters of the command SET BTS [OPTIONS] appear at a later position when generated by the DBAEM. the second part ‘number WPS’ defines. however. QLPUB and QLWPS (see above). can only be enabled if the CHAN objects are created accordingly (parameters FHSYID for frequency hopping and CHTYPE for SMS-CB). the enqueued WPS calls are served by every 4th TCH which becomes ‘idle’.S. The command reappears after the CREATE CHAN commands with the parameters SMSCBUSE and HOPP. Frequency Hopping and SMS-CB. The first part ’counter cycle’ defines the complete cycling period in terms of: number of calls served and 2. 221 . This order is necessary to ensure that SMS Cell Broadcast and Frequency Hopping may already be enabled when the DB is loaded to the system. this parameter is only relevant if the feature ‘Wireless Priority Service (WPS)’ is applied. object: BTS [OPTIONS] format: <councerCycle><numberWPS> range: counterCycle: 2 . 10 numberWPS: 1. for each complete cycle period..WPSPREF=4-1. how many WPS requests should be consecutively served. only 1 call is served at a time. BSCTQHOPUB. Example: The default setting WPSPREF=4-1 has the following effect: When a previously busy TCH becomes ‘idle’ and TCH requests are enqueued in both the WPS queue and in the Public queue. In other words: the setting WPSPREF=4-1 will have the effect that 1 out 4 served TCH requests is a WPS call. BSCT11WPS. 3 default: 4-1 WPS preference. When the ‘serving’ of a TCH request from the WPS call is scheduled. The value of this parameter consists of two parts: 1. which is a special enhancement of the feature ‘queuing’ required by the U.. see above).

as for each service type a ‘preferred sequence’. Feature Background ‘Service Dependent Channel Allocation’ The idea of the feature ‘Service Dependent Channel Allocation’ (SDCA) via ‘Multi Service Layer Support’ (MSLS) was introduced in BR8. which is later on used as a kind of ‘TCH pool address’ when the associated TRXs are checked for available TCH resources during TCH allocation. In this context the term ‘layer’ defines a group of one or more TRXs with a common (expected) radio interface quality. Cell LY_00 TRX:1 LY_01 TRX:2 Radio quality TRX:3 LY_02 TRX:4 LY_02 TRX:5 Layers TRXs Thus the defined layers can be regarded as a virtual TCH pool which is accessed and checked by the BSC in a certain ‘preferred’ sequence when a particular service type is requested. (E)GPRS etc. In this SLL. preference. the available service layers are sorted in descending order or priority resp. which is also called ‘Service Layer List’ (SLL) is defined by an own parameter or parameter pair.0 to allow a sophisticated TCH allocation strategy which selects. If the SLL is defined as a parameter pair. for different requested service types.). whose association to a particular layer number is defined by the parameter LAYERID (see command CREATE TRX). a TCH from the most suitable TRX. CS data. At this point. the layers do not yet have any service association but just a ‘layer number’.Defining the cell specific service layer lists for the feature ‘Service dependent Channel Allocation’ (SDCA) via ‘Multi Service Layer Support’ (MSLS): < This part of the BTS object is associated to the feature ‘Service Dependent Channel Allocation’ (SDCA) via ‘Multi Service Layer Support’ (MSLS) and defines Service Layer Lists (SLL) for each service type (AMR and non-AMR speech. Service Layer List (SLL) Which layer is accessed by the BSC channel allocation process and in which sequence the BSC searches for channel resources. depends on the requested service type. a) the first parameter is always named <service name>LLPRM (PRM = primary area) and identifies 222 . depending on the (expected) radio interface quality of this TRX (depending of the frequency planning strategy applied by the operator) and the robustness of the affected service against radio quality degradations.

If yes. LY_02 by the parameter CRTSWSPELLPRM=LY_01&LY00&LY02.the SLL for the far area (double timeslots) of an extended cell b) the second parameter is always named <service name>LLCOM (COM = complementary area) and identifies .....their SLLs are defined by the parameters as listed in the table below. it is at least necessary to assign to each TRX of the cell the LAYERID=LL_00 and to define this layer as the only entry in the SLL of each configured service (i. 223 .. the channel is allocated. AMRHRLLPRM=LY_00. SLL definition The SLL for service type E(FR). 9 different service types are defined .. HR is defined as LY_01. Service Type Signalling CS speech (E)FR-HR CS speech AMR FR CS speech AMR HR CS data HSCSD GPRS EGPRS ASCI parameters for SLL of primary area SLLPRM CRTSWSPELLPRM AMRFRLLPRM AMRHRLLPRM CRTSWDLLPRM HSCSDLLPRM GLLPRM ELLPRM ASCIPRM parameters for SLL of complementary area --CRTSWSPELLCOM AMRFRLLCOM AMRHRLLCOM CRTSWDLLCOM HSCSDLLCOM GLLCOM ELLCOM --- Please note that GPRS and EGPRS are not supported in the inner area of a concentric cell and HSCSD is not supported in the far area of an extended cell..LAYERID=LL_00. Example: BSC receives TCH request for service type EFR. it looks inside the SLL defined for the requested service type and starts to search for an available resource in the service layer that has the highest priority within the SLL.. while the association of the layers to the TRXs is defined as LY_00 -> TRX:0. Channel allocation process with SDCA/MSLS When the BSC receives a channel request for a particular service type. see CREATE BTS [BASICS]).the SLL of the inner are of a concentric cell or . it first checks if for the requested service an SLL is defined. If a resource can be found in this preferred layer. CREATE TRX:NAME=TRX:1. the service is regarded as ‘not supported’ in the cell! If the service shall be supported in the cell as a default configuration without a sophisticated configuration of the feature ‘Service Dependent Channel Allocation’.LAYERID=LL_01.the SLL of the complete are of a concentric cell or .the SLL of the near area (single timeslots) of an extended cell On the whole.). Therefore GLLCOM and ELLCOM cannot be defined in a concentric cell (CONCELL=TRUE.. LY_00. GLLPRM=LY_00 etc. CREATE TRX:NAME=TRX:2. see CREATE BTS [BASICS]) and HSCSDPRM cannot be defined in an extended cell (CELLTYP=EXTCELL.. If no channel can be found on the TRX(s) belonging to the preferred layer of the SLL. LY_02 -> TRX:3. AMRFRLLPRM=LY_00. CRTSWSPELLPRM=LY_00. Attention: The value <NULL> means that for the associated service no SLL is defined.the one and only SLL for standard cells or .LAYERID=LL_01. by the commands CREATE TRX:NAME=TRX:0.e. LY_01 -> TRX:1&TRX:2. the BSC searches the next lower layer for resources and so on. If this is the case.

directed retry (see parameter ENFORCHO in command SET BSC [BASICS]) 3. i. The diagram below illustrates this configuration. LY_02. the system searches for free resources in the layer LY_01 (TRX1 and TRX2) first.e. layer TCH request (requested service type = SLL (E)FR). If no idle TCH resources can be found in layer LY_01. Moreover.CREATE TRX:NAME=TRX:3. Please note that these intracell handovers are only triggered by the BSC if the parameter ENFOIAHO is set to TRUE and MNTBMASK BIT12 is set (both parameters see command SET BSC [BASICS])! 224 . preemption (see parameter EPRE in command SET BTS [OPTIONS]) 2.LAYERID=LL_02. If also in LY_00 (TRX:0) no free resources are available.e. in parallel. SDCA/MSLS resource managent in case of TCH congestion If no idle channel resources can be found in any of the service layers defined for the requested service type. multislot call downgrade (see parameter DGRSTRGY in command SET BTS [BASICS]). if a TCH resource is found. HRdefined by SET BTS [SERVICE]: CRTSWSPELLPRM= LY 01&LY00&LY02 LY_01 TRX:2 TRX:3 3. the BSC resource management task checks the next layer of the SLL. the BSC resource management task periodically checks the preferred layer for idle resources and. LY_00. a periodic task tries to move the CS call to a better Layer with a sufficient number of free channels as soon as possible to satisfy the multislot requested originally. the BSC starts the known procedures to satisfy TCH requests in case of TCH congestion (if enabled): 1. i. SLL (EFR) 2. transfers the call by an intra-cell handover to a TRX that belongs to the layer with higher preference.. layer LY_02 TRX:4 LY_03 TRX:5 Layers TRXs Resource allocation When the TCH request for service type EFR speech is received. layer LY_00 TRX:1 Cell 1. also 4. the BSC resource management task checks the last layer of the valid SLL.. queuing (see parameter EQ in command SET BTS [OPTIONS]) and.. Intra-cell handover due to ‘preferred service layer’ When a TCH was allocated on a service layer different from the preferred one. This mechanism is only available for CS services. for HSCSD multislot calls that did not receive the requested number of TCH resources.

When the decision for FR or HR has been made. for every service (except for (E)GPRS services).the activation state of the feature ‘Cell Load Dependent Activation of Half Rate’ (CLDAHR. Within a service layer. the ‘complementary’ SLL is checked first. TCHSD in SDCCH_POOL. HRACTAMRT1.g. Channel allocation for signalling channels (SDCCH. Note: TRXs belonging to different areas (of a concentric or an extended cell) can belong to the same layer (LAYERID). the other is called ‘complementary’ SLL. A downgrade of an incoming multislot call is only performed if no resource can be found in any of the relevant SLLs. TCHSD in TCHSD_POOL have to be included in a Layer associated at least to the Signalling SLL. but for each area an own separate SLL must be defined. two separate SLLs can be defined for each area. when a cell is configured as concentric cell or extended cell. If an MS supports all speech codecs and rates (AMR.the current TCH load in the cell. every layer is checked for resources before the search in the next SLL is started. the corresponding SLL for FR is searched first. the primary SLL is searched and the channel request is served if a resource is available. SLL for CS AMR HR 3. the MS’s speech version preference (indicated in the ASSIGNMENT REQUEST or HANDOVER REQUEST message) is first of all overwritten by the BSC’s speech version preference. SLL for CS AMR FR 2. Interworking of SDCA/MSLS with traffic load calculation The percentage calculation done for the features Enhanced Pairing and Compression/Decompression Handover (see parameters EPAT1. see parameters EHRACT and EHRACTAMR in command CREATE BTS[BASICS] is enabled) and . HRACTT1. Only when no resource can be found in the complementary SLL. if the MS is suitably positioned within the TRX’s coverage area and the radio conditions are correspondingly good.Interworking of SDCA/MSLS with ‘Cell Load Dependent activation of Half Rate’ When for an incoming TCH request both (E)FR and HR (or/and AMR-FR and AMR-HR) are indicated as allowed. TCHSD) in the service layers All the TRXs with channels of type SDCCH. i. otherwise these channels will never be used as singalling channel (TCHSDs in TCHSD Pool can be used also as traffic channels). FR and HR) and FR is preferred (e.e. When a channel is requested in a cell. the resources within each service layer are sorted according to their interference class. non-AMR. separately for every subarea (primary / complementary). which depends on . 225 . The main area’s SLL is called ‘primary’ SLL. in a concentric cell one for the inner and one for the complete are and in an extended cell one for the near and one for the far area. SLL for CS (E)FR/HR Within each SLL. due to EHRACT and current TCH load) the BSC searches in more than one SLL in the following order: 1. FRACTTH1 and FRACTAMRTH1 in command CREATE BTS [BASICS]) is done referring only to the TRXs included into the SLLs for relevant to CS speech AMR service and CS speech services. SLL search in case of cells with two separate areas As described above. Interworking of service layers and Idle Channel Supervision If the feature ‘Idle Channel Supervision’ (see parameter INTCLASS in command SET BTS [INTERF]) is enabled. the resource with the best interference class is always allocated first.

concentric. The service layers of the SLL are defined in a decreasing priority order. and for each item: LL_00 .e. In other words.EMANPRESPRM is the number of reserved channels for EGPRS service in the primary area .0 GMANPRES) is the number of reserved channels for GPRS service in the primary area . AMRFRLLCOM= LL_00.12 items max list. single/dual band). or in the complementary band of a dual band standard cell. > SET BTS [SERVICE]: NAME=BTSM:0/BTS:0. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this 226 . the SLL associated to ‘signalling’ is used for allocation. before its starts to allocate a TCH/SD in TCHSD_POOL located on the high-priorized service layer.. the DMA service layer may only be included in the SLLs defined for CS speech AMR and non-AMR services. Interworking of SDCA/MSLS and Direct TCH Assignment If Direct TCH Assignment is enabled (see parameter DIRTCHASS in command SET BTS [OPTIONS]). AMR Full Rate layer list complementary.e. the channel is changed after receipt of this message (in a similar way as it is done during normal change from SDCCH to TCH when direct assignment is not applied. the BSC will first allocate a TCH from a less priorized service layer. the TCHs are first (i. The channels are reserved in the first service layer that is defined both in the SLLs for GPRS/EDGE and the SLLs for CS services in the Primary/Complementary area. This SLL should be defined by the operator in such a way that the TRXs with less SDCCH and more TCHs are listed at the top. the enabling of DMA is rejected by the DBAEM and the BSC command interpreter. Service layers for EGPRS Generally for all service types all TRXs associated to a layer of the SLL are available for resource allocation..GMANPRESCOM is the number of reserved channels for GPRS service in the complementary area (significant only if the cell is an extended cell) . after receipt of the CHANNEL REQUEST message) searched in the SLL defined for signalling (see SLLPRM) and. object: range: default: BTS [SERVICE] 1.EMANPRESCOM is the number of reserved channels for EGPRS service in the complementary area (significant only if the cell is an extended cell). if the allocated channel does not perfectly match to service type requested in the ASSIGNMENT REQUEST message.) Reservation of (E)GPRS resources in service layers For the management of reserved packet channels in service layers that are shared between CS and packet services (this happens e. LL_11 <NULL> Object path name. For call setups with direct TCH assignment. However. i. this parameter defines the service layer list (SLL) associated to speech call applying AMR FR codec in the inner/near area of dual area cell (extended. Interworking of SDCA/MSLS and Dynamic MAIO Allocation (DMA) The feature Dynamic MAIO Allocation (DMA) is only permitted on service layers that have been configured for CS speech sevices only. that have the parameter TRXMD (see command CREATE TRX) set to the value EDGE. there is one exception: for EGPRS only those TRXs within the layers of the SLL can be used for EGPRS resource allocation.GMANPRESPRM (old BR7.g. when the same service layer is simultaneously included in both the SLL of speech services and GPRS services) four parameters (see command CREATE PTPPKF) are used for the reservation: . If the DMA service layer is included in the SLL of any other service type (including signalling).If several TCH/SDs are configured in different service layers.

12 items max list. or in the complementary band of a dual band standard cell. The service layers of the SLL are defined in a decreasing priority order. AMR Half Rate layer list primary. object: range: default: BTS [SERVICE] 1. this parameter defines the service layer list (SLL) associated to speech call applying AMR HR codec in the inner/near area of dual area cell (extended. LL_11 <NULL> AMRHRLLCOM= LL_00.. If this is the case. this parameter defines the service layer list (SLL) associated to speech call applying AMR HR codec in a single band standard cell. single/dual band). Attention: The value <NULL> means that for the associated service no SLL is defined. 227 .e. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). the service is regarded as ‘not supported’ in the cell. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). i.e. and for each item: LL_00 . The service layers of the SLL are defined in a decreasing priority order. concentric single/dual band). If this is the case. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. Attention: The value <NULL> means that for the associated service no SLL is defined. concentric single/dual band).. or in the BCCH band of a dual band standard cell.e. this parameter defines the service layer list (SLL) associated to ASCI VBS/VGCS services in a single band standard cell..AMRFRLLPRM= LL_00. The service layers of the SLL are defined in a decreasing priority order. or in the complete/far area of a dual area cell (extended.. If this is the case. concentric. LL_11 <NULL> AMRHRLLPRM= LL_00.e. i. the service is regarded as ‘not supported’ in the cell. The service layers of the SLL are defined in a decreasing priority order. object: range: default: BTS [SERVICE] 1. object: range: default: BTS [SERVICE] 1. or in the BCCH band of a dual band standard cell.12 items max list. If the service shall be supported.. this parameter defines the service layer list (SLL) associated to speech call applying AMR FR codec in a single band standard cell.12 items max list. or in the complete/far area of a dual area cell (extended. i. If the service shall be supported. Attention: The value <NULL> means that for the associated service no SLL is defined. If the service shall be supported. LL_11 <NULL> ASCILLPRM= LL_00. concentric single/dual band). at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). If the service shall be supported. and for each item: LL_00 . at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). i. and for each item: LL_00 . the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service.. the service is regarded as ‘not supported’ in the cell. and for each item: LL_00 .12 items max list. Attention: The value <NULL> means that for the associated service no SLL is defined... If this is the case. AMR Full Rate layer list primary. If the service shall be supported. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). or in the complete/far area of a dual area cell (extended. AMR Half Rate layer list complementary. the service is regarded as ‘not supported’ in the cell. or in the BCCH band of a dual band standard cell. ASCI layer list primary. object: range: default: BTS [SERVICE] 1. LL_11 <NULL> service. Attention: The value <NULL> means that for the associated service no SLL is defined. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. the service is regarded as ‘not supported’ in the cell. If this is the case.

or in the complete/far area of a dual area cell (extended. Attention: The value <NULL> means that for the associated service no SLL is defined. LL_11 <NULL> CRTSWSPELLCOM= LL_00. Attention: The value <NULL> means that for the associated service no SLL is defined.. or in the complementary band of a dual band standard cell. object: range: default: BTS [SERVICE] 1. If this is the case. concentric single/dual band).e. i.12 items max list. or in the BCCH band of a dual band standard cell. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). or in the BCCH band of a dual band standard cell. The service layers of the SLL are defined in a decreasing priority order. The service layers of the SLL are defined in a decreasing priority order. the service is regarded as ‘not supported’ in the cell. Circuit switched speech layer list complementary.. 228 . and for each item: LL_00 . If the service shall be supported. If the service shall be supported. i. i. Attention: The value <NULL> means that for the associated service no SLL is defined. If this is the case. the service is regarded as ‘not supported’ in the cell. this parameter defines list of TRX layers assigned to Circuit switched single slot data call in a single band standard cell. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. If this is the case. object: range: default: BTS [SERVICE] 1. Circuit switched data layer list primary.12 items max list.CRTSWDLLCOM= LL_00. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. concentric single/dual band).. this parameter defines the service layer list (SLL) associated to circuit switched single slot data call in the inner/near area of dual area cell (extended. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). If the service shall be supported. LL_11 <NULL> CRTSWDLLPRM= LL_00. the service is regarded as ‘not supported’ in the cell.e. The service layers of the SLL are defined in a decreasing priority order. concentric single/dual band).12 items max list. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. Attention: The value <NULL> means that for the associated service no SLL is defined.. concentric single/dual band). or in the complementary band of a dual band standard cell. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). The service layers of the SLL are defined in a decreasing priority order... LL_11 <NULL> CRTSWSPELLPRM= LL_00. Circuit switched speech layer list primary.e. and for each item: LL_00 .e. this parameter defines list of TRX layers assigned to circuit switched speech call applying EFR-FR-HR codec in a single band standard cell. If this is the case. object: range: default: BTS [SERVICE] 1.. i. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). and for each item: LL_00 . this parameter defines the service layer list (SLL) associated to circuit switched speech call applying EFR-FR-HR codec in the inner/near area of dual area cell (extended. If the service shall be supported. object: range: default: BTS [SERVICE] 1. the service is regarded as ‘not supported’ in the cell. or in the complete/far area of a dual area cell (extended. and for each item: LL_00 .12 items max list. LL_11 <NULL> Circuit switched data layer list complementary..

concentric single/dual band). LL_11 <NULL> GLLPRM= LL_00. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object).. this parameter defines the service layer list (SLL) associated to GPRS service in the inner/near area of dual area cell (extended. object: range: default: BTS [SERVICE] 1. or in the complete/far area of a dual area cell (extended. If the service shall be supported. that have the parameter TRXMD (see command CREATE TRX) set to the value EDGE. If this is the case. If this is the case. object: range: default: BTS [SERVICE] 1. and for each item: LL_00 .. or in the complementary band of a dual band standard cell.. Attention: The value <NULL> means that for the associated service no SLL is defined. i. i. or in the complete/far area of a dual area cell (extended. concentric single/dual band). GPRS layer list complementary. that have the parameter TRXMD (see command CREATE TRX) set to the value EDGE.e. and for each item: LL_00 . i. However. Note: Generally for all service types all TRXs associated to a layer of the SLL are available for resource allocation. object: range: default: BTS [SERVICE] 1. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service.ELLCOM= LL_00. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. If the service shall be supported. The service layers of the SLL are defined in a decreasing priority order. Attention: The value <NULL> means that for the associated service no SLL is defined. If this is the case. EDGE layer list primary. the service is regarded as ‘not supported’ in the cell.e. object: range: default: BTS [SERVICE] 1. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service.e. and for each item: LL_00 . GPRS layer list primary. The service layers of the SLL are defined in a decreasing priority order. Attention: The value <NULL> means that for the associated service no SLL is defined. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). or in the BCCH band of a dual band standard cell. i. or in the complementary band of a dual band standard cell. concentric single/dual band). this parameter defines list of TRX layers assigned to GPRS service in a single band standard cell. concentric single/dual band).. there is one exception: for EGPRS only those TRXs within the layers of the SLL can be used for EGPRS resource allocation. the service is regarded as ‘not supported’ in the cell.. Attention: The value <NULL> means that for the associated service no SLL is defined. If the service shall be supported. there is one exception: for EGPRS only those TRXs within the layers of the SLL can be used for EGPRS resource allocation. the service is regarded as ‘not supported’ in the cell. The service layers of the SLL are defined in a decreasing priority order..e. 229 .. this parameter defines list of TRX layers assigned to EDGE service in a single band standard cell. If the service shall be supported.12 items max list. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). LL_11 <NULL> GLLCOM= LL_00. However.. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object).12 items max list. and for each item: LL_00 . this parameter defines the service layer list (SLL) associated to EDGE service in the inner/near area of dual area cell (extended. LL_11 <NULL> EDGE layer list complementary. If this is the case. the service is regarded as ‘not supported’ in the cell.12 items max list. The service layers of the SLL are defined in a decreasing priority order.12 items max list. LL_11 <NULL> ELLPRM= LL_00. or in the BCCH band of a dual band standard cell. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. Note: Generally for all service types all TRXs associated to a layer of the SLL are available for resource allocation.

object: range: default: BTS [SERVICE] 1.e. i.e. Signaling layer list primary. HSCSD layer list primary.HSCSDLLCOM= LL_00.12 items max list. The service layers of the SLL are defined in a decreasing priority order. or in the complete/far area of a dual area cell (extended. Attention: The value <NULL> means that for the associated service no SLL is defined. 230 . at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). If the service shall be supported. object: range: default: BTS [SERVICE] 1. concentric single/dual band). the service is regarded as ‘not supported’ in the cell. concentric single/dual band). this parameter defines list of TRX layers assigned to services that require only a signalling channel in a single band standard cell..e.. The service layers of the SLL are defined in a decreasing priority order. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). LL_11 <NULL> HSCSDLLPRM= LL_00. If the service shall be supported.12 items max list. and for each item: LL_00 . the service is regarded as ‘not supported’ in the cell. LL_11 <NULL> SLLPRM= LL_00. If this is the case. concentric single/dual band). the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service... or in the BCCH band of a dual band standard cell. The service layers of the SLL are defined in a decreasing priority order. this parameter defines list of TRX layers assigned to HSCSD service in a single band standard cell. or in the complete/far area of a dual area cell (extended. LL_11 <NULL> HSCSD layer list complementary. and for each item: LL_00 . If the service shall be supported. object: range: default: BTS [SERVICE] 1. and for each item: LL_00 . or in the BCCH band of a dual band standard cell. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. this parameter defines the service layer list (SLL) associated to HSCSD service in the inner/near area of dual area cell (extended. i. If this is the case. If this is the case. i. Attention: The value <NULL> means that for the associated service no SLL is defined. at least LY_00 must be set (in correspondence to the default setting of LAYERID=LY_00 in the TRX object). Attention: The value <NULL> means that for the associated service no SLL is defined. the entered sequence of layer-IDs determines the layer preference for the resource allocation for this service. or in the complementary band of a dual band standard cell.12 items max list.. the service is regarded as ‘not supported’ in the cell..

see parameter HOPMODE=BBHOP in command SET BTS BTS [OPTIONS]). b) The MS thus provides valid measurement reports even for the BCCH carrier. Setting this parameter to TRUE has the following results: a) The BS PWRC flag is permanently set to ‘0’(=disabled) in the SYSTEM INFORMATION TYPE 6 even if the database parameter indicates the opposite (EBSPWRC=CLASSIC or EBSPWRC=ADAPTIVE). FALSE TRUE Object path name. In this case all measurement reports are suppressed (or declared ‘not valid’) by the MS .Setting the cell specific attributes for Power Control: For detailed information regarding the Power Control thresholds please refer to the chapter Appendix. If frequency hopping is configured for the TCHs (see parameter FHSY and MAIO in command CREATE CHAN) but disabled.which means that neither handover nor power control is possible for these calls. due to failure of a TRX involved in a baseband FH system) – a frequency redefinition procedure is started which instructs the MSs in a cell to change the hopping system in such a way that hopping shall continue with one frequency only (which is always that frequency which is assigned to the TRX by parameter TRXFREQ in command CREATE TRX). Note: the BS Power Control Correction is managed differently for AMR-calls and non-AMR calls (due to introduction of CR 1435) in correspondence with the following table: EBSPWRC CLASSIC/ADAPTIVE CLASSIC/ADAPTIVE DISABLED DISABLED EBSPWCR TRUE FALSE TRUE FALSE PWRC -Flag in SYSINFO-6 and MEASINFO to MS for non-AMR calls 0 1 0 0 for AMR calls 1 1 0 0 231 . c) The BTS takes care that the ‘full power’ part from the BCCH carrier is correctly subtracted from the DL RXLEV values reported in the MEASUREMENT REPORTs. This flag makes the MS suppress measurement reports derived from the BCCH carrier in order to avoid the measurements to be falsified by the ‘full power’ part of the BCCH (PWRC must not be used on the BCCH carrier). which can happen either if hopping is manually disabled (SET BTS [OPTIONS]: HOPP=FALSE) or automatically disabled (e. this parameter is necessary to ensure full handover functionality if BS power control is enabled while channels are created with frequency hopping system and the hopping system involves the BCCH TRX (baseband frequency hopping only. Normally. Enable BS power control correction. EBSPWCR=TRUE. if BS PWRC is enabled the MS is informed about this by a flag in the SYSTEM INFORMATION (see parameter EBSPWRC). object: range: default: PWRC TRUE. Calls that are served by a radio TCH which belongs to the BCCH TRX will in this case hop on the BCCH frequency only. section “Power Control Thresholds & Algorithms” and “Interworking of Handover and Power Control”! SET PWRC: NAME= BTSM:0/BTS:0/PWRC:0.g.

Field experiences have shown that under specific circumstances it can happen that. This parameter is sent on the BCCH (SYSTEM INFORMATION TYPE 3) or on the SACCH (SYSTEM INFORMATION TYPE 6) in the IE ‘Cell Options’. Whether the sending power is to be increased or decreased is determined from the downlink measurement reports the MS sends to the BTS. please refer to the section ‘Power Control’ in the section “Classic and Adaptive Power Control” in the appendix of this document.e. DISABLED default: ADAPTIVE (for BTSs in SW BR7.0) CLASSIC (for BTSs in SW < BR7. but the BTS cannot correctly decode all received SACCH frames in the UL. e. This way it is ensured that during periods of (or single) missing SACCH reports the DL power control does not further decrease the power but rather increases it in normal steps if the situation persists until the RLFW is triggered or the normal function resumes. Please consider that with the current default values (RDLNKTBS=20 and PCTHRLF=18) the abovementioned conditions are met (RDLNKTBS minus 2 counts) and thus PWRC will increase the power to the maximum instead of increasing the power by a normal power control step.05 GSM 12. determines whether the BTS dynamically adjusts its sending power according to the current radio conditions (on non-BCCH carriers). object: range: PWRC CLASSIC.08 GSM 05. For further details about the power control decision process and classic and adaptive power control. Enabling BS Power Control results in a minimization of the downlink interference on the radio interface. the BS power control decision algorithm also checks the ‘missing SACCH’ counter (S-counter. due to excessive path inbalance. Note: Under specific conditions. the MS reports very good RXLEV_DL values. or PAVRQUAL in case of ‘adaptive’ power control) is started. either at least three SACCH reports in a row were missed or the current SACCH report is missing and additional SACCHs were missing before) then a normal BTS power increase will be commanded (if the interval timer is not running). If a power increase was executed the normal power control interval timer (PCONINT in case of ‘classic’. the ‘adaptive’ BS power control uses power increase and reduction step sizes that depend on the current radio conditions defined by RXLEV and REXQUAL values. As the BS power control decision is based on the measurement samples stored in the averaging window (if an UL SACCH cannot be decoded. the RXLEV_DL average value could suggest a further DL power decrease. initial value defined by RDLNKTBS): If no SACCH report was received in a particular SACCH period. no PC decision will be made for the DL. While ‘classic’ BS power control exclusively uses fixed power increase steps (see parameter PWRINCSS) and fixed power reduction steps (see parameter PWREDSS). Two variants of BS power control can be selected: CLASSIC power control and ADAPTIVE power control. ADAPTIVE. To avoid this behaviour.0) Reference: 3GPP 45. this just means that no new sample is inserted into the window). 232 .EBSPWRC=ADAPTIVE.008 GSM 04. so that a new power increase due to missing SACCH reports may only be triggered once the interval timer has expired.20 Enable BS power control. the following mechanism was implemented: If the S-counter is more than 2 below RDLNKTBS (i.g.

The following rule has to be considered: HOLTHLVUL (SET HAND) < LOWTLEVU < [LOWTLEVU (SET PWRC) + 2∗PWREDSS (SET PWRC)] < UPTLEVU (SET PWRC) 233 . DISABLED default: ADAPTIVE (for BTSs in SW BR7.08 Power control lower threshold level uplink. defines the lower threshold of the received signal level on the uplink for power increase.0) CLASSIC (for BTSs in SW < BR7.08 Enable MS power control. For further details about the power control decision process and classic and adaptive power control. MSTXPMAXDCS or MSTXPMAXPCS. object: unit: range: PWRC 1 dB 0. This feature checks the radio link counter (also called ‘S’ counter) in the BTS. object: unit: range: PWRC 1 dB 0. Two variants of MS power control can be selected: CLASSIC power control and ADAPTIVE power control. determines whether the BTS instructs the MS to dynamically adjust its sending power according to the current radio conditions. FALSE TRUE 3GPP 45.EMSPWRC= ADAPTIVE. the BTS increases the MS and BS transmit power to the maximum when the radio link counter has reached the value set by the parameter parameter PCRLFTH (see below). 62 = -48dBm 63 = greater than -48dBm default: 25 Reference: GSM 05. see CREATE BTS [BASICS]) or by the MS power class . Power control lower threshold level downlink. As a not successfully decoded UL SACCH frame is a clear indication for serious radio interface problems. MS Power Control is used to save MS battery capacity and to minimize the uplink interference on the radio interface. object: range: default: Reference: PWRC TRUE.63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm ..63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm ...05 GSM 12. If MS power control is enabled the MS adjusts the power according to appropriate commands received from the BTS. defines the lower threshold of the received signal level on the downlink for power increase.. While ‘classic’ MS power control exclusively uses fixed power increase steps (see parameter PWRINCSS) and fixed power reduction steps (see parameter PWREDSS).008 GSM 04.0) Reference: 3GPP 45. the ‘adaptive’ MS power control uses power increase and reduction step sizes that depend on the current radio conditions defined by RXLEV and REXQUAL values. The following rule has to be considered: HOLTHLVDL (SET HAND) < LOWTLEVD < [LOWTLEVD (SET PWRC) + 2∗PWREDSS (SET PWRC)] < UPTLEVD (SET PWRC) LOWTLEVU=25.. this parameter enables/disables the “BS and MS power control due to radio link failure warning”. ADAPTIVE. 62 = -48dBm 63 = greater than -48dBm default: 25 Reference: GSM 05. MS and BS power control indication due to ‘radio link failure warning' enabled.whichever is the lower.008 LOWTLEVD=25. If MS power control is disabled. whose initial value is determined by the parameter RDLNKTBS (see below) and which is decreased by ‘1’ if an UL SACCH frame could not be correctly decoded.20 EPWCRLFW=TRUE. please refer to the section ‘Power Control’ in the section “Classic and Adaptive Power Control” in the appendix of this document.08 GSM 05. The BTS generates these commands after evaluation of uplink measurement results. the BTS instructs every MS in the concerned cell to use the maximum RF output power as defined by the parameter MSTXPMAXGSM (resp. object: range: PWRC CLASSIC..

. 30 10 Power control lower threshold quality AMR downlink.63 . the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (range 0. The following rule has to be considered: HOLTHQUDL (SET HAND) > LOWTQUAD (SET PWRC) > UPTQUAD (SET PWRC) LOWTQUAMRDL=10. Attention: Unlike for the parameter LOWTQUAD..13 . 1..6% 4 = 1.62 C/I 1 2 4 5 6 7 8 9 10 11 RXQUAL 3..62 0..6% to 3.38 .. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter PAVRQUAL).12 5... object: unit: range: default: PWRC 1 dB 0 .LOWTQUAD=4.88 .12 4.88 .. 5...The integer C/I value is then compared to the threshold determined by LOWTQUAMRDL.. defines the lower threshold of the received signal quality on the downlink for power increase..13 . 7 6.The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the following table: RXQUAL 6. 6.4% 2 = 0.12 3.8% to 1.. 2.. If it drops below the threshold. 234 .2% 1 = 0.38 .37 2.From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter PAVRQUAL...13 .7 0 = less than 0. 6. the power control algorithm increases the DL transmit power if the downlink quality drops below the threshold determined by LOWTQUAMRDL..4% 6 = 6. .Like any other MS.63 . 0.62 1. 1. 2.62 6. 6..13 .....13 ..87 6.87 2.8% default: 4 Reference: GSM 05.87 4.63 .2% to 0. 5. 3....37 5.63 . The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging).08 Power control lower threshold quality downlink..Although the total value range of LOWTQUAMRDL is 0.. 4.87 2. the mapping limits the maximum useful C/I value to 20dB (see mapping table above).7). 4.30.38 .63 ..87 5.88 . 4.62 4...4% to 0.4% to 12...8% 3 = 0..12 1. .. for which the quality values are entered in RXQUAL values (range 0. 6.. . 3.. .2% to 6.. the values for LOWTQUAMRDL are entered in C/I values (carrier/interference in [dB]).88 . Notes: .8% 7 = greater than 12..37 C/I 12 13 14 15 16 17 18 19 20 For a more detailed mapping table please refer to the section “Mapping of RXQUAL and C/I values for AMR calls” in the appendix of this document.12 0 .2% 5 = 3..88 ..7) in the MEASUREMENT REPORT messages.In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls. 5. 2. The BTSE-internal processing of these values is done in the following way: . this parameter eclipses the threshold LOWTQUAD in case of an AMR (Adaptive Multi Rate) call: For AMR calls. object: unit: range: PWRC 1 dB 0. C/I threshold values above 20dB therefore can never be reached and will not show any effect.. the BTS increases the DL transmit power.

30 10 Power control lower threshold quality AMR uplink. . the power control algorithm increases the DL transmit power if the uplink quality drops below the threshold determined by LOWTQUAMRUL.7)... . the BTS measures the uplink quality in RXQUAL values (range 0.2% to 6. object: range: PWRC 0.4% 2 = 0. The following rule has to be considered: HOLTHQUUL (SET HAND) > LOWTQUAU (SET PWRC) > UPTQUAU (SET PWRC) LOWTQUAMRUL=10.2% to 0. the values for LOWTQUAMRUL are entered in C/I values (carrier/interference in [dB]).08 Power control lower threshold quality uplink. for which the quality values are entered in RXQUAL values (range 0. 235 .From the measured RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter PAVRQUAL. Notes: .Although the total value range of LOWTQUAMRDL is 0.30. defines the lower threshold of the received signal quality on the uplink for power increase.8% default: 4 Reference: GSM 05.. The BTSE-internal processing of these values is done in the following way: . it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter PAVRQUAL).7). the mapping limits the maximum useful C/I value to 20dB (see mapping table for LOWTQAMRDL). .2% 1 = 0.LOWTQUAU=4.In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls..The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the table included in the parameter description of LOWTQUAMRDL (see above). The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging).2% 5 = 3. the BTS increases the UL transmit power. Attention: Unlike for the parameter LOWTQUAU.6% 4 = 1..8% 7 = greater than 12.4% 6 = 6. C/I threshold values above 20dB therefore can never be reached and will not show any effect.6% to 3.4% to 12.As usual.8% to 1. If it drops below the threshold.4% to 0. this parameter eclipses the threshold LOWTQUAU in case of an AMR (Adaptive Multi Rate) call: For AMR calls.The integer C/I value is then compared to the threshold determined by LOWTQUAMRUL.7 0 = less than 0.8% 3 = 0. object: unit: range: default: PWRC 1 dB 0. .

e.DTX weighting factor All measurements for Power Control pass an averaging algorithm. Up to BR6. Parameter format: averaging period .e. In other words. Starting from BR7. the higher weighting was implemented by the multiple insertion of the FULL measurement sample into the gliding averaging window. The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average. defines the averaging parameters for the RXLEV measurements.0. the oldest measurement is removed from the window.PAVRLEV=4-2.0. the current weighting factor is stored in parallel under the same offset as shown in the following picture: max_av_win_size length offset sample weight 0 0 1 1 1 1 2 2 1 3 3 1 4 4 2 5 5 2 6 6 1 7 0 0 8 0 0 9 0 0 29 0 0 30 0 0 Thus the time needed to fill the averaging window will always be the same (i. if the DTX weighting factor was set to “2”. The DTX weighting factor determines how much more the FULL values shall be weighted for radio measurement results measured over a period with voice activity (DTX not active). In addition. Note: In the SDCCH phase there are no TCH speech frames. 236 . while SUB measurement samples from measurement periods with active DTX (silence) were inserted into the averaging window only once (for further details about DTX and the meaning of FULL and SUB values please refer to the explanations provided for the parameter DTXDLFR). The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. The averaging window total is then calculated by adding up all sample values currently stored in the within the averaging window while a single sample is added number of ‘weight’ times. The averaging window is called “gliding”. only dependent on the ‘laveraging period’ portion of the parameter PAVRLEV). The PAVRLEV “averaging period” defines the size of the gliding averaging window for the measured RXLEV values. This calculated value is finally used in the Power Control decision process. this approach has been changed: FULL measurement samples values for non-DTX channels no longer entered n-times into the averaging window anymore but every value will be entered once. For this reason only the SUB values (determined from the SACCH frames) are considered for the handover decision which are – as usual – inserted into the averaging window as single values only. all ‘weight’ values within the averaging window are added up). FULL measurement samples from measurement periods with inactive DTX (speech transmitted) were inserted into the averaging window twice. Then the total is divided by the ‘weight’ total (i. object: format: PWRC averaging periodDTX weighting factor unit: 1 SACCH multiframe =480ms (averaging period) range: 1-31 (averaging period) 1-3 (DTX weighting factor) default: 4 (averaging period) 2 (DTX weighting factor) Reference: 3GPP 45. as the window works as a queue: when a new measurement is received.008 Power control averaging parameters level.

defines the averaging parameters for the RXLEV measurements. the oldest measurement is removed from the window. The DTX weighting factor determines how much more the FULL values shall be weighted for radio measurement results measured over a period with voice activity (DTX not active). as the window works as a queue: when a new measurement is received.If AMR is used. Parameter format: averaging period .DTX weighting factor All measurements for Power Control pass an averaging algorithm. it is recommended to use a minimum RXQUAL averaging window size of 4 in order to achieve a suitable accuracy of the RXQUAL average value for AMR calls. This calculated value is finally used in the Power Control decision process. 237 .PAVRQUAL=4-2. The averaging window is called “gliding”.008 Power control averaging parameters quality. Notes: . The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. object: format: PWRC averaging periodDTX weighting factor unit: 1 SACCH multiframe =480ms (averaging period) range: 1-31 (averaging period) 1-3 (DTX weighting factor) default: 4 (averaging period) 2 (DTX weighting factor) Reference: 3GPP 45. The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average.In the SDCCH phase there are no TCH speech frames. For further information about the management of the DTX weigthing factor please refer to the explanations provided for the parameter PAVRLEV. . The PAVRLEV “averaging period” defines the size of the gliding averaging window for the measured RXQUAL values. For this reason only the SUB values (determined from the SACCH frames) are considered for the handover decision which are – as usual – inserted into the averaging window as single values only.

. Basically the limit for the power reduction due to BS power control is determined by the lower power control threshold (LOWTLEVD.e. defines the minimum time period (in units of 2 SACCH multiframes) between two successive modifications of the BTS or MS transmission power level. In case a power level was changed a timer with the length defined by PCONINT is started (immediately if the BTS power level was changed and in case of a MS power level change only after the MS has confirmed the new power level – see also PWRCONF).g. Dynamic power reduction is performed by BS or MS power control in order to adjust the MS and BS transmit level in correspondence with the radio conditions of an individual call. BS power control does not adjust the power to a level lower than LOWTLEVD. I. i. provides another possibility for a limitation of dynamic BS power reduction which is not related to an absolute DL RXLEV value (like LOWTLEVD) but to the relative power reduction with respect to the maximum possible DL receive level (that applied before start of power reduction) for a call. In order to allow for the most exact PWRC decisions the averaging windows should be filled completely with new measurement samples that reflect the state after the power level change. There are two types of power reduction: static power reduction and dynamic power reduction. While this timer is running (there are independent timers for BTS and MS PWRC) the PWRC algorithm continues to fill the respective level and quality averaging windows with new measurement samples.31 2 3GPP 45. This maximum allowed power reduction affects all calls in the BTS for which BS power control is applied.PCMBSTXPRL=15. In other words: At the end of every measurement period the power control (PWRC) algorithm determines whether a power increase or decrease is necessary based on the current BTS/MS averaged level and quality values (see also averaging window settings PAVRLEV/PAVRQUAL). Therefore the value of PCONINT should correspond to the size of the level or quality averaging window (whichever is longer): 238 . however. the sum of both static and dynamic power reduction can never exceed the maximum possible power reduction steps supported by the BTSE (related to the maximum nominal output power of the used CU resp. However. Band BTS type eMicro (BS-82) Pico BTS (BS-242) BTSplus (main) BTS1 (e. for as long as the timer has not expired.e. The parameter PCMBSTXPRL.. object: unit: range: default: Reference: PWRC 2 SACCH multiframes 0. the BTS or MS power control decision will be suspended after a new power level was set. BS-60) GSM900 & GSM850 42 dB 30 dB 46 dB 30 dB DCS1800 42 dB 30 dB 36 dB 30 dB PCS1900 42 dB 30 dB 36 dB 30 dB PCONINT=2.008 Power control interval. This reduction is applied in addition to the static power reduction that may have been set by the parameter PWRRED. which depends on the type and generation of BTSE in correspondence with the following table. The purpose of this parameter is basically to adapt the transmit power of the used CU or PA type to the actual size and radio propagation conditions of a particular cell. PCMBSTXPRL determines the maximum dynamic power reduction which may be applied to a call in the cell. this parameter defines the maximum allowed dynamic power reduction.15 15 Power control maximum BS TX power reduction Level. see below). object: unit: range: default: PWRC 1 power reduction step = 2dB 0. PA). Static power reduction is a continuous power reduction which is applied to a particular TRX by the parameter PWRRED (see command CREATE TRX).

defines the maximum interval that the BTS will wait for the confirmation of a newly set RF power level by the MS in units of 2 SACCH multiframes. If the radio link counter in the BTS reaches the value of PCRLFTH. DB6 DB6 3GPP 45.PCRLFTH=18. If the PWRC mode is set to 'adaptive' (see parameters EBSPWRC and EMSPWRC) this suspension timer will only be started if the power level was changed due to a decision based on signal quality. defines the step size used when increasing the MS transmit power. object: unit: range: default: Reference: PWRC 2dB DB2. PWREDSS=DB2. PAVRLEV/PAVRQUAL=4-x PCONINT=2. object: range: default: Reference: PWRC 0. this parameter is only relevant if the parameter EPWCRLFW (see above) is set to TRUE. DB4.g.. wait 4 SACCH multiframes (since the granularity of PCONINT is 2 SACCH multiframes the value should be rounded to the next higher value in case the longest averaging window length has an odd value).008 e. there is only the need to wait for the collection of all new quality samples. Power increase step size.64 18 3GPP 45. If the timer expires before the MS confirmed the requested power level the power control decision process is resumed. so that the value of PCONINT is not relevant in case of the 'adaptive' PWRC mode! Power control radio link failure threshold. 239 . object: unit: range: default: Reference: PWRC 2dB DB2.008 PWRCONF=2. the BTS immediately increases the BS and MS transmit power to the maximum. Therefore the PWRC algorithm sets the timer length automatically to the time needed to re-fill the quality averaging window. DB4 DB2 3GPP 45.008 Power reduction step size. since with the 'adaptive' mode the level samples will be automatically corrected by the value of the power level change and therefore PWRC can resume immediately after a level based decision without having to wait for the collection of new level samples. Power confirmation interval. defines the step size used when reducing the MS transmit power. Please see also parameter RDLNKTBS. It defines the threshold value for the radio link counter in the BTS for the ‘radio link failure warning’ detection. The timer administered with PWRCONF is started after a new MS power level was set. object: unit: range: default: Reference: PWRC 2 SACCH multiframes 1-31 2 3GPP 45.008 PWRINCSS=DB6. Since the suspension timer is now only started in case of quality based decisions and the level samples are automatically corrected. As long as this timer is running the BTS compares the received MS power level with the requested power level.

. see above) decision: If no SACCH report was received in a particular SACCH period. 12. Rule: RDLNKTBS > PCRLFTH .14 power control parameters. 240 .The current value of the S-Counter in the BTS is also checked in the scope of the BS power control (parameter EBSPWRC. If the parameter EPWCRLFW is set to TRUE and the BTS radio link counter counter reaches the value entered for the parameter PCRLFTH (see above) the BTS initiates the adjustment of the MS transmit power and BS transmit power to maximum transmit power.e. object: PWRC The setting <NULL> indicates that for the affected service group no range: <NULL>. Unsuccessful default: 20 decoding of uplink SACCH messages (i. Fo further details please refer to the section “Service dependent default: <NULL> Handover and Power Control” in the appendix of this document. Radio link counter BS. these parameters represent the remaining 13 parameters which allow a service groupNULL>. this parameter is the SG1PCPAR=<NULL>. indicates the maximum value of the radio link counter needed to detect a radio link failure in the uplink. Service group 1 power control parameters. 60. Notes: . range: <NULL>. initial value defined by RDLNKTBS) is more than 2 below RDLNKTBS (i. GSM 05. represent. no PC decision will be made for the DL (BS Power Control). represent. 64) for every dedicated channel (TCH or SDCCH).. If the counter reaches the value 0 (‘radio link timeout’).SG14PCPAR=< Service group 2. The object: PWRC entered value is the start point for the ‘radio link counter’ (also called range: 4-64 ‘missing SACCH’ counter or ‘Scounter’) in the BTS which is managed step size: 4 (range 4. . dependent setting of power control parameters and thresholds. the BTS sendes a CONNECTION FAILURE INDICATION with cause 'radio link failure' to the BSC which initiates the release of the whole dedicated connection. This leads to unsuccessful decoding of UL SACCH frames in the BTS (as the MS does not send any SACCH frames anymore) and thus to the continuous decrease of the BTS radio link counter. specific parameter settings are applied and the power controld n fields with ranges in decision for this service group is based the ordinary PWRC correspondence with the PWRC parameters they parameter settings. This scenario represents (together with the ERROR INDICATION with cause ‘T200 expired (N200+1) times’ (see parameter T200 in command SET BTS [TIMER])) the most common and ‘classic’ case of a call drop. 8. MEASUREMENT Reference: GSM 04.. Fo further details please refer to the section “Service dependent default: <NULL> Handover and Power Control” in the appendix of this document. The setting <NULL> indicates that for this service group no specific 12 fields with ranges in parameter settings are applied and the power controld decision for correspomdemce with the PWRC parameters they this service group is based the ordinary PWRC parameter settings. as in this case the MS stops any transmission activity on the dedicated channel. . either at least three SACCH reports in a row were missed or the current SACCH report is missing and additional SACCHs were missing before) then a normal BTS power increase will be commanded. If the ‘missing SACCH’ counter (S-counter..RDLNKTBS=20. first of the 14 parameters which allows a service group-dependent object: PWRC setting of power control parameters and thresholds.08 REPORTs) in the BTS lead to a decrease of the counter by 1. SG2PCPAR.An expiry of the radio link counter in the MS (see RDLNKTO in command CREATE BTS [BASICS]) also indirectly leads to the ‘radio link timeout’ in the BTS.08 successful decoding to an increase by 2 (a similar counter for the observation of raio link problems is also used in the MS (see parameter RDLNKTO in command CREATE BTS [BASICS])..e.

08 Default value changed in BR8.0! UPTQUAD=2.7 0 = less than 0..0! Power control upper threshold level downlink.8% default: 2 Reference: GSM 05.4% to 0. the following rule must be fulfilled: UPTLEVD > HOTDLINT For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document.2% to 6. Power control upper threshold level uplink. The following rule has to be considered: UPTQUAD (SET PWRC) < LOWTQUAD (SET PWRC) < HOLTHQUDL (SET HAND) UPTLEVU=36. defines the upper threshold of the received signal level on the uplink for power reduction...8% to 1..8% 7 = greater than 12.4% 2 = 0.. Power control upper threshold quality downlink.2% 5 = 3.08 Default value changed in BR8.. defines the upper threshold of the received signal quality on the downlink for power reduction.8% 3 = 0.4% 6 = 6. defines the upper threshold of the received signal level on the downlink for power reduction.6% to 3. the following rule must be fulfilled: UPTLEVU > HOTULINT For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document.63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . 62 = -48dBm 63 = greater than -48dBm range: 0.. 62 = -48dBm 63 = greater than -48dBm default: 36 Reference: GSM 05.UPTLEVD=36. The following rule has to be considered: UPTLEVU (SET PWRC) > [LOWTLEVU (SET PWRC) + 2∗PWREDSS (SET PWRC)] > LOWTLEVU > HOLTHLVUL (SET HAND) To guarantee a correct interworking of power control and intracell handover.6% 4 = 1.2% to 0. The following rule has to be considered: UPTLEVD (SET PWRC) > [LOWTLEVD (SET PWRC) + 2∗PWREDSS (SET PWRC)] > LOWTLEVD > HOLTHLVDL (SET HAND) To guarantee a correct interworking of power control and intracell handover.08 241 .2% 1 = 0. object: unit: range: PWRC 1 dB 0.. object: unit: range: PWRC 1 dB 0. object: range: PWRC 0.4% to 12.63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm .63 default: 36 Reference: GSM 05.

. for which the quality values are entered in RXQUAL values (range 0.Although the total value range of UPTQUAMRDL is 0.The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the following table: RXQUAL 6.. 3. 6....13 ..37 C/I 12 13 14 15 16 17 18 19 20 For a more detailed mapping table please refer to the section “Mapping of RXQUAL and C/I values for AMR calls” in the appendix of this document..13 .88 . ....63 . 6... 4.. the mapping limits the maximum useful C/I value to 20dB (see mapping table above).In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls...62 C/I 1 2 4 5 6 7 8 9 10 11 RXQUAL 3.7) in the MEASUREMENT REPORT messages. 2...87 6. 242 . Notes: .From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter PAVRQUAL. 2. If it exceeds the threshold.. 5. C/I threshold values above 20dB therefore can never be reached and will not show any effect.... 5. .12 0 . 1.13 .7).13 .88 ..38 .30. . 7 6.. the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (range 0. the power control algorithm reduces the DL transmit power if the downlink quality exceeds the threshold determined by LOWTQUAMRDL.12 3.63 .63 . the BTS reduces the DL transmit power.88 . the values for UPTQUAMRDL are entered in C/I values (carrier/interference in [dB]). 6... 6. 4.. 2. object: unit: range: default: PWRC 1 dB 0.12 1.13 .88 . The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging).. . this parameter eclipses the threshold UPTQUAD in case of an AMR (Adaptive Multi Rate) call: For AMR calls.87 2.62 1. 1..30 13 Power control upper threshold quality AMR downlink.37 5... Attention: Unlike for the parameter UPTQUAD.63 .87 4..38 .UPTQUAMRDL=13.. 5. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter PAVRQUAL)..63 ...88 ..62 4. 4. The BTSE-internal processing of these values is done in the following way: ..Like any other MS... 3..62 6.38 .87 2.87 5.12 5.The integer C/I value is then compared to the threshold determined by UPTQUAMRDL..62 0.12 4. 0.37 2..

the BTS reduces the UL transmit power. If it exceeds the threshold. this parameter eclipses the threshold UPTQUAU in case of an AMR (Adaptive Multi Rate) call: For AMR calls.. defines the upper threshold of the received signal quality on the uplink for power reduction. . . the power control algorithm reduces the UL transmit power if the uplink quality exceeds the threshold determined by UPTQUAMRUL.2% 1 = 0.8% default: 2 Reference: GSM 05. The following rule has to be considered: UPTQUAU (SET PWRC) < LOWTQUAU (SET PWRC) < HOLTHQUUL (SET HAND) UPTQUAU=2. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter PAVRQUAL)..8% 3 = 0.As usual.4% to 0.UPTQUAMRUL=13.The integer C/I value is then compared to the threshold determined by UPTQUAMRUL.7).The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the table included in the parameter description of UPTQUAMRDL (see above).8% to 1.4% to 12. the mapping limits the maximum useful C/I value to 20dB (see mapping table for UPTQUAMRDL). the BTS measures the uplink quality in RXQUAL values (range 0. C/I threshold values above 20dB therefore can never be reached and will not show any effect. Power control upper threshold quality uplink.6% 4 = 1.. Attention: Unlike for the parameter UPTQUAU.30.7 0 = less than 0.08 243 . Notes: . The BTSE-internal processing of these values is done in the following way: .6% to 3. The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging).8% 7 = greater than 12.2% 5 = 3.7).4% 2 = 0.2% to 0. object: unit: range: default: PWRC 1 dB 0.Although the total value range of LOWTQUAMRDL is 0.In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls.30 13 Power control upper threshold quality AMR uplink..From the measured RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter PAVRQUAL. the values for UPTQUAMRUL are entered in C/I values (carrier/interference in [dB]).4% 6 = 6.2% to 6. . object: range: PWRC 0. .. for which the quality values are entered in RXQUAL values (range 0.

Power Control Parameter Relations Power Control Parameters relevant for both MS and BS Power Control PWRC: PWRINCSS PWREDSS PAVRLEV PAVRQUAL PCONINT PWRCONF MS Power Control PWRC: EMSPWRC LOWTLEVU LOWTQUAU (is for AMR replaced by LOWTQAMRUL) UPTLEVU UPTQUAU (is for AMR replaced by UPTQAMRUL) BS Power Control PWRC: EBSPWRC LOWTLEVD LOWTQUAD (is for AMR replaced by LOWTQAMRDL) UPTLEVD UPTQUAD (is for AMR replaced by UPTQAMRDL) EBSPWCR PCMBSTXPRL Power Control Indiaction due to link failure warning PWRC: EPWCRLFW PCRLFTH RDLNKTBS 244 .

It is used in the mobile as filter constant for EGPRS channel quality measurements according to GSM 45. Each PDCH is transmitted with the maximum possible power.008 Bit error probability averaging period.Creating the GPRS point to point packet transfer service in a cell: < The PTPPKF functional object represents the point to point service in a cell.2.3. ABUTYP=ACBU8BIT. this parameter is broadcast inside the (packet) system information messages PSI1. BVCI=3 for the second PTPPKF.. Access burst type.18.0. 10=1. PSI13 or SI13.. ALPHA=3. this parameter represents the weight for predefined PFI best effort in DL.Pmax is the maximum MS output power Based on the above formula. Alpha value. 1=0. The BVCI is allocated by the system to each PTPPKF according to the creation position in the database: BVCI=2 for the first PTPPKF. range for PTPPKF: 0.060 Object path name.15 5 3GPP 45.02).. > CREATE PTPPKF: NAME= BTSM:0/BTS:0/PTPPKF:0. this parameter specifies the ALPHA value applied in the UL power control algorithm used with GPRS/EDGE.Γch is given by the parameter GAM (object PTPPKF) . In GSM 08.08: Pch = min (Γ0 – Γch – α * (C + 48). BEPAVGP=5. the parameter ALPHA determines the influence of the MS receive level on the MS output power calculation. object: range: default: Reference: PTPPKF 0. this parameter represents the weight for background class.1. it is specified that a cell is identified by a BVCI so there is a relation one to one from cell and BVCI.10 0=0. α >0: The MS power depends on the C-value -> open loop PC Hint: BR70 does not provide a DL Power Control on GPRS timeslots.2. this parameter corresponds to the 3GPP parameter ACCESS_BURST_TYPE and indicates the type of access burst used on uplink PDCH (PACCH or PRACH).Γ0 is a constant value . object: range: default: PTPPKF 1. object: range: default: Reference: PTPPKF ACBU8BIT. object: range: default: PTPPKF 1. Access Bursts are mainly used on the PRACH to access the system or – currently more common – as blocks of four identical access bursts coding a PACKET CONTROL ACK message.Pch is the MS ouput power .C is the normalized receive level at the MS .32 1 Best effort PFIDL weight.008 BCGRWEI=1. object: unit: range: PTPPKF 0.. Background weight. The value ACBU8BIT means that the 8 bits access burst shall be used by the mobile station and ACBU11BIT means that 11 bits access bursts shall be used by mobile station (see GSM 05. The MS uses an UL power value according to GSM 05. ACBU11BIT ACBU8BIT 3GPP 44.008 Chapter 10. With Γch being a constant value in BR70 we get the 2 extremes: α =0: C has no influence on the MS power –> Pch = const. Pmax) . 245 .0 default: 3 Reference: 3GPP 45.32 1 BEPFIDLWEI=1..1 0. etc...1.. (scheduling priority 4). The measurement results are reported to the network as EGPRS Channel Quality Report inside the EGPRS PACKET DOWNLINK ACK/NACK messages. for point to point packet transfer. ..0.

thus the unit for the entered value is 20ms. three transitions) theoretically takes a minimum of 24 seconds. UNIT200 UNIT250. BLERAVEUL=UNIT100. The BLERAVDL value is based on frame periods of 20 ms. UNIT200 UNIT250.e. UNIT300 UNIT350. reserving 12 PAGCH blocks leaving no PPCH blocks!). b) If only 1 timeslot is used for a GPRS DL TBF. Note: The system does not refuse entering senseless values which may cause blocking of the PBCCH functionality itself (e. The BLER value is used as base for the link adaptation algorithm (dynamic switch of coding schemes). TAVGBLER also defines the minimum time to pass between two consecutive upgrade/downgrade steps. this parameter is relevant for GPRS and EDGE and is used as averaging period for the Block Error Rate (BLER) calculation for an uplink TBF. the minimum time between two consecutive changes with BLERAVEDL=UNIT400 is TAVGBLER = (400 frames ∗ 20ms) / 1 = 8s This means that in this case a switchover from CS1 to CS4 (i. UNIT050 UNIT075. object: range: default: Reference: PTPPKF 0. If 4 timeslots are used in DL.. according to the formula: TAVGBLER = BLERAVEUL / #TS. the minimum time between two consecutive coding scheme changes with BLERAVEDL=UNIT400 is TAVGBLER = (400 frames ∗ 20ms) / 4 = 2s This means that a switchover from CS1 to CS4 (i. The parameter is coded according to the following table: 0000 0 blocks reserved for PAGCH. The value is expressed in unit of 20 ms. UNIT100 UNIT150. Block error rate averaging period uplink.0! As a coding scheme upgrade or downgrade is only possible when the BLER averaging window was completely filled. this parameter is relevant for GPRS and EDGE and is used as averaging period for the Block Error Rate (BLER) calculation for a downlink TBF. this parameter specifies the number of blocks reserved for PAGCH. BS PAGCH blocks reserved.e. UNIT300 UNIT350. Examples: a) Mobile SIEMENS S45 used (4 timeslots in DL. The averaging period for BLER calculation additionally depends on the number of radio timeslots allocated to a TBF and is calculated according to the following formula: TAVGBLER = BLERAVEDL ∗ 20ms / #TS where TAVGBLER = BLER averaging period #TS = number of radio timeslots used for the TBF Default value changed in BR8. UNIT400 UNIT200 default: Block error rate averaging period downlink.12 7 GSM 05. three transitions) theoretically takes a minimum of 6 seconds. PDTCH and PACCH 0001 1 blocks reserved for PAGCH. PDTCH and PACCH … … 1100 12 blocks reserved for PAGCH. UNIT050 UNIT075.g. PDTCH and PACCH for the 52 frames multiframe case (see GSM 05.0! BPAGCHR=7. 1 timeslot in UL). UNIT100 UNIT150. object: range: PTPPKF UNIT025.BLERAVEDL=UNIT200.02 246 . Please refer to the parameter BLERAVEDL for further details. The averaging period depends also on the number of radio timeslots (#TS) allocated to a radio timeslots. object: range: PTPPKF UNIT025. PDTCH and PACCH This parameter corresponds to the 3GPP parameter BS_PAG_BLKS_RES. UNIT400 UNIT100 default: Default value changed in BR8.02).

B9.15. Maximum BSC countdown value. B3. B6 0011 Block B0. B6.02). B6 used for PBCCH 1 0 Block B0. B2.BPRACHR=4. B9. B4. B10 1001 Block B0. B10. B7. B7. reserving 0 PRACH blocks allows no more packet accesses in the cell!). B3. B1.3. The mobile includes the Countdown Value CV in each uplink data block to indicate the last Block Sequence Number (BSN=0) that is sent in the UL TBF.10.. B7. B8 1011 Block B0.060 Default value changed in BR8. B1. B1 0110 Block B0. Note: Also for this parameter the system does not refuse entering senseless values which may cause blocking of the PBCCH functionality itself (e.g. B4. B3. B6. object: range: default: Reference: PTPPKF 1-15 10 3GPP 44. B6. B8. B6. B6. B10. B7. B6.7. B6. The field is coded according to the following table: 0 0 Block B0 used for PBCCH 0 1 Block B0. B3.02 BS PRACH blocks reserved. B9. B9. BS PBCCH blocks. B9. B8.8. B2 1010 Block B0.02 BSCDVMA=10. Its value is broadcast to the mobiles within PSI1 and (P)SI13.9. B10. B3 used for PBCCH 1 1 Block B0. B7. B3. this parameter is used during the countdown procedure when terminating an UL TBF. this parameter corresponds to the 3GPP parameter BS_PBCCH_BLKS and specifies the number of blocks allocated to the PBCCH in the multiframe.5. The parameter is coded according to the following table: coding blocks reserved for PRACH 0000 none (default) 0001 Block B0 0010 Block B0. object: range: default: Reference: PTPPKF 0. B10. B4. B6.4. object: range: default: Reference: PTPPKF 0.3 1 GSM 05. B6. B4 1000 Block B0. B5 1100 Block B0. B5. B3.12 4 GSM 05. B3.0! BSPBBLK=1. B3.1. B7 0111 Block B0. B6. B1. B6. B9 0101 Block B0. this parameter specifies the number of blocks reserved in a fixed way to the PRACH channel on any PDCH carrying PCCCH and PBCCH (see GSM 05.. B2. B1. B9. As soon as the MS transmits the first data block indicating a CV value different to 15 (starting with BSCDVMA). … 15. Example: Using BSCDVMA=10 will result in a CV sequence similar to: 15. B1. Thus using a smaller BSCDVMA value may allow (internally) ‘slow’ mobiles to continue the UL data transfer without opening a new TBF. B3. B2. B9. B9 used for PBCCH 247 . B4. B4. B3. B1.2.0 Any UL data arriving from higher layers after the countdown procedure has started on RLC/MAC shall be sent within a future TBF. the mobile will send exactly BSCDVMA more blocks until the UL TBF is completed. B11 This parameter corresponds to the 3GPP parameter BS_PRACH_BLKS.6. B3 0100 Block B0. B6. This parameter corresponds to the 3GPP parameter BS_CV_MAX. B7. B1. B9.

PER180 PER190 PER200 default: PER100 Reference: GSM08. PER60. PER130. PER060 PER070. Caution: It is strictly recommended to maintain the default value! GPRS C31 hysteresis. object: range: PTPPKF PER010. PER170. Caution: It is strictly recommended to maintain the default value! BVC bucket low percentage. PER110. PER150 PER160.008 248 . GPRS C32 qualifier. PER110. If the congestion state persists. BVCBLPER) are based on this value. As a consequence. this parameter corresponds to the 3GPP parameter C32_QUALIFIER. BVC Bucket Size PCU = BVCBSPPER * BVC Bucket Size It represents the buffer space ‘reserved’ in the PCU for this BVC.C corresponds to the parameter TF1 (object PCU) . PER090 PER100.. PER70. PER130. object: range: default: Reference: PTPPKF PER50.008 C32QUAL=FALSE. PER70.18 BVC bucket high percentage. object: range: PTPPKF PER100. PER080. PER050.) * Rmax . PER140. PER80. PER180 PER190 PER200 PER200 default: Reference: C31H=TRUE. PER120.Rmax is the maximum rate assigned to that BVC: Number of timeslots that can be assigned to GPRS/EDGE in this cell multiplied by the respective maximum rate per TS. As soon as the congestion state is cleared. PER040. FALSE TRUE 3GPP 45. this parameter corresponds to the 3GPP parameter C31_HYSTERESIS and indicates if the GPRS reselect hysteresis (GCELLRESH) shall be applied to the C31 criterion (in ready state if the new cell is in the same RA). FALSE FALSE 3GPP 45. thus limiting the amount of data being sent from the SGSN towards the BSC. PER60. object: range: default: Reference: PTPPKF TRUE. The BVC congestion thresholds (BVCBHIPER. positive GPRS_RESELECT_OFFSET values are only applied to the neighbour cell with the highest RLA value of those cells for which C32 is compared. PER140. PER030. the leak rate is further decreased. PER170. object: range: default: Reference: PTPPKF TRUE. the leak rate ‘R’ inside the FLOW-CONTROL-BVC PDU is set to its original value and the SGSN may increase the data rate sent towards the BSC.BVCBHIPER=PER70. the ‘Bucket Congestion’ state is ceased. PER020. Caution: It is strictly recommended to maintain the default value! BVC bucket max percentage defines the value of the BVC Bucket Size (Bmax) reported in the FLOW-CONTROL-BVC PDU towards the SGSN: BVC Bucket Size = BVCBMAPER * (C + 1 sec. If C32_QUAL is set. If ‘BVC Bucket Level’ is lower than BVCBHIPER * BVC Bucket Size PCU. PER120. Caution: It is strictly recommended to maintain the default value! BVC bucket size PCU percentage. PER90 PER60 BVCBMAPER=PER100. object: range: default: Reference: PTPPKF PER50. BVCBSPPER=PER200. PER80. the ‘Bucket Congestion’ state is activated. the Flow Control Algorithm will reduce the reported leak rate ‘R’ inside the FLOW-CONTROL-BVC PDU. PER90 PER70 BVCBLPER=PER60.This parameter specifies the ‘BVC Bucket Size PCU’ value based on the ‘BVC Bucket Size’ value Bmax reported to the SGSN. If BVC Bucket Level is greater than BVCBHIPER * BVC Bucket Size PCU. PER150 PER160.

Cell reselection threshold output. object: range: default: PTPPKF TRUE. this parameter specifies the maximum traffic load threshold allowed in a cell to be considered as potential target. Note: CRESELTHRINP is a kind of equivalent to the parameter TRFLTH (see command SET HAND [BASICS]) for CS call ‘traffic handover’. .11 Control acknowledgement type. this parameter is mandatory and represents the Common PCU the PCU refers to (see command CREATE CPCU). An example for calculating the ‘traffic percentage values’ is available in the GPRS Global Description or in the ATMN Testcase AC701683. object: PTPPKF range: 0. object: PTPPKF range: 50. the BSC starts to move TBFs to neighbour cells. Please refer to the parameter CRESELTRHSOUT for further details. object: range: PTPPKF 0. Cell reselection threshold input.The traffic control strategy is only applicable between cells belonging to the same PCU. Notes: . This flag may only be set if the same parameter available in the BSC object was set to TRUE already (see parameter CSCH3CSCH4SUP in command SET BSC [BASICS])... The GPRS traffic control strategy is based on the feature Network Controlled Cell Reselection (NCCR).1 0 3GPP 44. 85 default: 75 Reference: CSCH3CSCH4SUP=TRUE. the traffic control feature may be additionally enabled by setting TRFPS = TRUE. If the GPRS load in the source cell exceeds a certain threshold (CRESELTRHSOUT). The meaning of the parameter values is: 0 PACKET CONTROL ACKNOWLEDGEMENT format is four access bursts 1 PACKET CONTROL ACKNOWLEDGEMENT format is RLC/MAC control block Since BR55/10 onwards this parameter is hardcoded to the value ‘0’ (four access bursts format)! CPCU number...CACKTYP=0. this parameter specifies the minimum traffic load threshold above which mobiles in packet transfer mode may be moved out of the cell for load balancing purpose. This is done as long as the load in the source cell remains above NCTRFPSCTH and the available target cells are loaded with less packet load than given with the parameter CRESELTRHINP. CS3 and CS4 support. Please refer to the aforementioned parameter in the BSC object for further details. this parameter corresponds to the 3GPP parameter CONTROL_ACK_TYPE and indicates the format of the PACKET CONTROL ACKNOWLEDGEMENT message the MS shall transmit when polled.100 default: 85 Reference: CRESELTHRINP=75. object: range: default: Reference: PTPPKF 0. If NCCR is activated in the cell (NCRESELFLAG = TRUE). CRESELTRHSOUT=85. FALSE FALSE 249 . this parameter allows to enable or disable the feature GPRS Coding Scheme 3 and Coding Scheme 4 in the BTS associated to the PTPPKF object.060 CPCUN=1.CRESELTRHSOUT is a kind of equivalent to the parameter TRFHITH (see command SET HAND [BASICS]) for CS call ‘traffic handover’.

The more often the network polls the mobile for EPDAN messages. the earlier it can retransmit not acknowledged RLC/MAC blocks. object: range: default: Reference: PTPPKF 0. 8 sec. EDTMSUP=DISABLED. EGPRS polling period five time slots. <NULL> 16 EGPRS polling period seven time slots.64. this parameter specifies the polling period to be used if one timeslot is assigned. Default value changed in BR8. 16 means that every 16th DL data block is polled. 250 . <NULL> 8 EGPRS polling period one time slot. object: PTPPKF range: 8. This results in a polling period of 320ms in case a single PDCHis allocated and only 40ms in case 8 PDCHs are allocated to that TBF.7 7 3GPP 44.. this parameter corresponds to the 3GPP parameter DRX_TIMER_MAX and indicates the maximum time allowed for the mobile station to request for Non-DRX mode after packet transfer mode. The parameter is coded according to the following table and broadcast on the BCCH/PBCCH within the PSI1 and (P)SI13 messages: 000 001 010 011 100 101 110 111 No Non-DRX mode after packet transfer mode 1 sec.. EDASUP=DISABLED. Default value changed in BR8..0! EGPLGPSEVENTS=16. this parameter specifies the polling period to be used if seven timeslots are assigned. object: range: default: PTPPKF 8.64. 32 sec. The polling period is a decisive factor in case RLC/MAC acknowledged mode is used. This generally helps to increase the data transfer speed under real network conditions (BLER>0).64. object: range: default: PTPPKF 8. this parameter specifies the polling period to be used if five timeslots are assigned. Its value is given in units of RLC-blocks.060 Maximum discontinuous receipt timer. DISABLED DISABLED Extended dynamic allocation support. Each MS selects the value that it prefers and forwards this info within the ATTACH REQUEST message towards the SGSN.64. 64 sec. object: PTPPKF range: 8. object: range: default: PTPPKF ENABLED. object: range: default: PTPPKF ENABLED. 16 sec. 4 sec. this parameter defines if Dual Transfer Mode (DTM) is supported or not... object: range: default: PTPPKF 8. EGPLGPFOURTS=16. this parameter specifies the polling period to be used if four timeslots are assigned. <NULL> default: 16 Reference: EGPLGPFIVETS=16. this parameter specifies the polling period to be used if eight timeslots are assigned. e. non-DRX mode after packet transfer mode 2 sec.g. DISABLED DISABLED Enable DTM support. <NULL> default: 16 Reference: EGPRS polling period eight time slots.0! EGPLGPONETS=8. <NULL> 8 EGPRS polling period four time slots. EGPLGPEIGHTTS=16..DRXTMA=0.64. this parameter defines if Extended Dynamic Allocation is supported or not.

object: range: default: PTPPKF 8. WS992. WS256. EGPRS window size one time slot.. WS96.64. <NULL> WS512 EGPRS window size four time slots. Default value changed in BR8. WS256. WS960. WS352. WS448. WS352. object: range: PTPPKF WS64. WS416. For GPRS transfers a fixed window size of 64 blocks is applied. default: Reference: EGWSFOURTS=WS96.0! EGWSEIGHTTS=WS192. WS192. WS96. WS384. WS672. WS448. EGPLGPTHREETS=16. WS192. this parameter specifies the window size to be used if eight timeslots are assigned. default: Reference: EGWSONETS=WS64. WS416. WS640 <NULL> WS640 EGPRS window size five time slots. The biggest window size possible for each of the 8 following parameters (1-8 timeslots) is used as respective default value. object: range: PTPPKF WS64. WS160. WS544. <NULL> 8 EGPRS polling period three time slots. WS608. WS384. WS576. WS736. WS896. object: range: PTPPKF WS64. <NULL> default: 16 Reference: EGPRS polling period six time slots. 251 . WS128. WS416. Default value changed in BR8.Reference: EGPLGPSIXTS=16. WS1024 <NULL> WS1024 EGPRS window size eight time slots. WS256. WS288. this parameter specifies the polling period to be used if three timeslots are assigned. WS352. WS160. WS480. object: range: PTPPKF WS64. WS192. WS224. WS576. WS160. WS320. WS768. WS608. WS288. WS128. WS704. WS384. WS480. WS320. WS512. WS96. object: range: default: PTPPKF 8. The value is transferred to the MS within the PDAS. WS224. WS160.64. WS224. WS800. WS832. <NULL> 8 EGPRS polling period two time slots. this parameter specifies the window size to be used if four timeslots are assigned. WS480.64.. WS128. this parameter specifies the polling period to be used if three timeslots are assigned. WS640. WS544. WS864. WS96. WS448. WS288. WS128. WS320. this parameter specifies the window size to be used if one timeslot is assigned.0! EGPLGPTWOTS=8. WS512. default: Reference: EGWSFIVETS=WS128.. WS928. PUAS or PTR messages and is applied for both the UL and DL case. WS512. this parameter specifies the window size to be used if five timeslots are assigned. WS192. object: PTPPKF range: 8. this parameter specifies the polling period to be used if six timeslots are assigned.

see below). WS256. WS512. 252 . WS768. default: Reference: EGWSTHREETS=WS96. WS352. WS224. this parameter specifies the window size to be used if six timeslots are assigned. WS736. default: Reference: EGWSSIXTS=WS160. WS352. see above). The system continuously evaluates the Block Erasure Rate (BLER) values during a packet transfer and switches. WS256. object: range: PTPPKF WS64. WS288. WS480. WS224. WS288. WS320. WS192. FALSE FALSE Enable link adaptation. WS480. WS416. <NULL> WS768 EGPRS window size six time slots. WS864. WS384. WS640. WS704. WS640. WS672. object: range: default: PTPPKF TRUE. WS800. <NULL> WS256 EGPRS window size two slots. WS768. The decision is based on two internal tables. WS608. WS96. WS384. WS320.<NULL> default: WS192 Reference: EGWSSEVENTS=WS160. WS288. WS832. WS160. WS160. object: range: PTPPKF WS64. WS224. WS160. <NULL> WS384 EGPRS window size three time slots. the decision averaging speed for coding scheme changes is controlled by the parameters BLERAVEUL and BLERAVEDL (object PTPPKF. WS224. This feature adapts the used coding scheme to the current radio conditions. this parameter specifies the window size to be used if two timeslots are assigned. WS192. WS608. WS96. WS672. WS736. WS416. to a lower or higher coding scheme. this parameter specifies the window size to be used if seven timeslots are assigned. WS448. WS704. WS576. WS256. WS128. WS576. WS320. object: range: PTPPKF WS64. WS544. WS128. WS96. WS256. WS512. <NULL> WS896 EGPRS window size seven time slots. WS96. WS448. object: range: PTPPKF WS64. if required. WS544. WS384. WS160. The use of the two different tables is controlled by the parameter RAENV (object PTPPKF. default: Reference: ELKADPT=TRUE. WS128. this parameter enables/disables the GPRS/EGPRS coding scheme Link Adaptation (LA). WS896. WS192. this parameter specifies the window size to be used if three timeslots are assigned. WS352. WS192. default: Reference: EGWSTWOTS=WS64. WS128.

190 DISABLED EMCSFAMA1DL=TRUE. MCS9 Enable MCS family A padding MSC1 downlink. EMCSFAMAP1DL=FALSE. Enable MCS family A MSC1 downlink. Family B consists of: MCS2. FALSE FALSE EMCSFAMGDL=FALSE. In case of non-extended cell. Family C consists of: MCS1. In downlink direction IR is applied by the BSC and all mobiles have to support it according to specifications. MCS4 Enable MCS family A MCS1 uplink without incremental redundancy 8PSK. only the parameter EMANPRESPRM (see below) is relevant. object: range: default: PTPPKF TRUE. MCS8 Enable MCS family B MSC1 downlink. object: range: default: PTPPKF TRUE. FALSE FALSE EMCSFAMB1DL=FALSE. MCS5. MCS4 Enable MCS family GMSK downlink. object: range: default: PTPPKF TRUE. MCS6. i. this parameter enables all coding schemes with GMSK modulation to be used for downlink TBFs.e. Please see also command SET BTS [SERVICE] for further explanations about the feature ‘Service Dependent Channel Allocation. Family A consists of: MCS3. see command CREATE BTS [BASICS]). Family A Padding consists of: MCS3. MCS6. see command CREATE BTS [BASICS]). see command CREATE BTS [BASICS]) there is only one primary area. object: range: default: PTPPKF TRUE. MCS2. FALSE TRUE 253 .. this parameter enables all coding schemes belonging to Family A plus MCS1 to be used for uplink TBFs. For standard cells and dualband standard cells (CELLTYPE=STDCELL or DBSTDCELL. the primary area corresponds to the ‘far area’ (double timeslots) of the extended cell.190 DISABLED EMANPRESPRM=0. MCS9 Note: Incremental Redundancy (IR) in uplink direction is not supported in BR70. MCS3. object: range: default: PTPPKF 0. this parameter enables all coding schemes belonging to Family C to be used for downlink TBFs. MCS7 Enable MCS family C downlink. in this case EMANPRESPRM defines the overall number of TCHs reserved for EGPRS on the TRXs that are included in the SLLs of EGPRS services. FALSE FALSE EMFA1UNIR8PSK=TRUE. this parameter all coding schemes belonging to Family A Padding plus MCS1 to be used for downlink TBFs.. FALSE TRUE EGPRS maximum Number of PDCH reserved Complementary.EMANPRESCOM=0. this parameter enables all coding schemes belonging to Family B plus MCS1 to be used for downlink TBFs. Family A consists of: MCS3. Please see also command SET BTS [SERVICE] for further explanations about the feature ‘Service Dependent Channel Allocation. Coding schemes using GMSK are: MCS1. object: range: default: PTPPKF TRUE. If the cell is configured as extended cell (CELLTYPE=EXTCELL. this parameter defines the number of traffic channels reserved for EGPRS in the ‘Complementary Area’ which corresponds to the ‘near area’ (single timeslots) in an extended cell (CELLTYPE=EXTCELL. EGPRS maximum Number of PDCH reserved Primary. MCS6. object: range: default: PTPPKF 0. object: range: default: PTPPKF TRUE. FALSE FALSE EMCSFAMCDL=FALSE. this parameter enables all coding schemes belonging to Family A plus MCS1 to be used for downlink TBFs. this parameter defines the number of traffic channels reserved for EGPRS in the ‘Primary Area’.

The parameter values express a value in dB MDBxx = . Enable MCS family C uplink without incremental redundancy 8PSK. this parameter shall be used to enable the mobile speed sensitive network controlled GSM/GPRS to UMTS cell reselection algorithm. Enable MCS family GMSK uplink without incremental redundancy 8PSK.EMFAP1UNIR8PSK=FALSE. Enable MCS family B MCS1 uplink without incremental redundancy 8PSK. this parameter enables the GMSK coding schemes belonging to Family C to be used for uplink TBFs in case the MS does not support 8PSK. this parameter enables all coding schemes belonging to Family A Padding plus MCS1 to be used for uplink TBFs. object: range: default: PTPPKF TRUE. FALSE FALSE EMFGUNIRGMSK=TRUE. FDD GPRS Q offset. this parameter enables all coding schemes belonging to Family B plus MCS1 to be used for uplink TBFs. EMFCUNIRGMSK=FALSE. Enable MCS family GMSK uplink without incremental redundancy GMSK. object: range: default: PTPPKF TRUE. this parameter enables all GMSK coding schemes (MCS1-MCS4) to be used for uplink TBFs in case the MS supports 8PSK. object: range: default: PTPPKF TRUE. FALSE FALSE EMFCUNIR8PSK=FALSE. MCS6.060 254 . DB20 = 20dB) The value ALWAYS indicates an infinite negative (-∞ dB) offset.xxdB (e. this parameter corresponds to the 3GPP parameter FDD_GPRS_Qoffset which is broadcast on the PBCCH in the PACKET SYSTEM INFORMATION TYPE 3quater and is related multiRAT mobiles. this parameter enables all coding schemes belonging to Family C to be used for uplink TBFs in case the MS supports 8PSK. Further relevant parameters are EUSCNCRESEL (see command SET BSC [BASICS]) and GMICROCU. FALSE FALSE EMFGUNIR8PSK=FALSE. object: range: default: PTPPKF TRUE. It defines a level offset by which the RLA_P value of an UTRAN FDD neighbour cell must exceed the RLA_P of the serving GSM cell before the UTRAN neighbour cell is considered for cell reselection from GSM to UTRAN. Family A consists of: MCS3. MCS7 Note: Incremental Redundancy (IR) in uplink direction is not supported in BR70. In downlink direction IR is applied by the BSC and all mobiles have to support it according to specifications. Enable UMTS MSS network controlled reselection. FALSE TRUE EUMSSNCRESEL=TRUE. object: range: default: PTPPKF TRUE. TUESP and USRSCPNCRESEL (see command CREATE ADJC3G). so with this setting a 3G Mobile will always change to the 3G network if any acceptable 3G cell is available. FALSE FALSE FDDGQO=DB00. MDB20 = -20dB) DBxx = xxdB (e. Enable MCS family C uplink without incremental redundancy GMSK. For details about the GPRS cell reselection algorithm from GSM to UTRAN please refer to the description of parameter GFDDQMI (see below). object: range: PTPPKF ALWAYS MDB28 MDB24 MDB20 MDB16 MDB12 MDB08 MDB04 DB00 DB04 DB08 DB12 DB16 DB20 DB24 DB28 default: DB00 reference: 3GPP 45. object: range: default: PTPPKF TRUE. In downlink direction IR is applied by the BSC and all mobiles have to support it according to specifications.008 3GPP 44. it is used by the MS/UE for the cell re-selection algorithm from GSM to UTRAN.g. FALSE FALSE Enable MCS family A padding MCS1 uplink without incremental redundancy 8PSK. MCS5. this parameter enables all GMSK coding schemes (MCS1-MCS4) to be used for uplink TBFs in case the MS does not support 8PSK. FALSE FALSE EMFB1UNIR8PSK=FALSE. Family B consists of: MCS2. MCS8 Note: Incremental Redundancy (IR) in uplink direction is not supported in BR70.g. object: range: default: PTPPKF TRUE.

The Gamma-ch value (Γch ) is not dynamically updated within BR70.in fact. ThresholdIdleChanVH defines the point when the allocation strategy is switched back from vertical to horizontal: If more than (ThresholdIdleChanVH) percent of CS-only and CS/PS-shared timeslots are idle. . which is considered only on the TRXs shared between packet services and CS services. per_10. this parameter is common to MS and PFC. PDAS. per_20. They are not considered at all within the above load calculations.The BSC vertical allocation decision algorithm does not consider the 'layers' . this parameter defines the “gamma” value applied in the power control algorithm.100 ThresholdIdleChanVH: 0. It consists of three fields: ThresholdIdleChanHV defines the point when the allocation strategy is switched from horizontal to vertical: If less than (ThresholdIdleChanHV) percent of CS-only and CS/PS-shared timeslots are idle. Therefore vertical allocation may be activated both due to CS calls and PDCH allocations.31 0 = 0dB. it is applied only on TRXs that belong to service layers which are included in the SLLs for both GPRS and other services.. ThresholdIdleChanEU defines the threshold above which the upgrading of radio resources is enabled (see parameters UPGRFREQ.. PUAN.The GASTRTH thresholds applied only on the TRXs shared between packet services and other services. object: range: PTPPKF per_05.PDCHs are reserved in a flexible way with the parameter GMANPRESPRM and GMANPRESCOM only on thoseTRXs that belong to service layers that are included in the SLLs defined for GPRS services (see command SET BTS [SERVICE] for further explanations). PPCTA.e. . i.ThresholdIdleChanHV has to be lower than ThresholdIdleChanVH. vertical allocation is enabled. it is applied only on TRXs that belong to service layers which are 255 . it represents the shrinking value used in case of PDU life time expiration or in case of Bucket Ratio not supported in order to reduce R value sent to SGSN. per_50 per_15 Flow percentage..g. 31 = 62dB 3 = 6dB GASTRTH=10-20. . default: GAM=3. per_25. The default value of 6dB means basically that the MS always transmits with the maximum allowed output power (33/30 dBm) unless the normalized receive level at the MS side (C-value) exceeds (is better than) -48dBm.100 ThresholdIdleChanHV: 10 ThresholdIdleChanVH: 20 ThresholdIdleChanEU: 20 default: Gamma. PTR.. PUAS. It is an MS and channel specific power control parameter and is sent to the MS within an RLC control message (e. This is the case for TCHs of TRXs that belong to service layers which are included in the SLLs for both GPRS and CS services. GPRS allocation strategy thresholds. . object: unit: range: default: PTPPKF 2dB 0. therefore the UL power control for GPRS cannot be operated as closed loop power control. Remarks: . . object: format: range: PTPPKF ThresholdIdleChanHV ThresholdIdleChanVH ThresholdIdleChanEU ThresholdIdleChanHV: 0.ThresholdIdleChanVH has to be lower than or equal to ThresholdIdleChanEU. GASTRABISTH). defines the thresholds for the system to switch between horizontal and vertical GPRS channel allocation (and back).Idle ‘CS-only’ timeslots are all available TCHs of TRXs that belong to service layers which are included in the SLLs for CS services only. per_15. per_45. i.100 ThresholdIdleChanEU: 0.e.FPER=per_15. per_40. the decision about horizontal or vertical allocation is based on the load threshold GASTRTH only. per_35.‘Idle shared’ timeslots are all available timeslots in the cell that can handle both GPRS and CS services. . horizontal allocation is enabled again. .The decisive total number of idle channels changes due to GPRS and CS load. per_30. …).

060 256 .008 3GPP 44. The more really relevant 3G cells are available. GPRS FDD multiRAT reporting.060 included in the SLLs for both (E)GPRS and CS. In other words. object: range: default: reference: PTPPKF 0. GPRS cell reselect hysteresis. This approach was used as it does not make sense to restrict the bandwidth for packet calls as long as enough other resources are still available. 7=14dB 2 3GPP 45.GCELLRESH=2.in the PACKET CELL CHANGE ORDER messages via the PACCH which commands to leave the current cell and to change to a new one (which may also be an FDD cell).in the PACKET SYSTEM INFORMATION TYPE 3quater messages via the PBCCH and . the higher the value should be set. GFDDMURREP=<NULL>.in the PACKET SYSTEM INFORMATION TYPE 5 messages via the PBCCH . this parameter corresponds to the 3GPP parameter GPRS_CELL_RESELECT_HYSTERESIS and indicates the hysteresis to be subtracted from the C32 value of the neighbour cells if the MS is in ready state and the neighbour cell belongs to the same routing area. this number of 3G neighbour cells. This parameter indicates the number FDD UTRAN cells the MS/UE shall include in the MEASUREMENT REPORTs sent in ‘GPRS attached’ mode.7 0=0dB. the BSC will always allocate the PDCHs on all shared layers (starting on the preferred one) but it will not start vertical allocation before the load threshold GASTRTH has not been exceeded. GCELLRESH is additionally substracted from the C31 values of the neighbour cells. If a CS call is to be served. Usually 6 neighbour cells can be reported within one MEASUREMENT REPORT message. as described above.3. The value must therefore be set considering how many 2G neighbour cells shall be reported in any case. the shared 'packet busy' channels can still be preempted. not only the ones on the 'shared' layers.. For the load calculation the BSC considers. The value ranges from 0 dB to 14 dB (2 dB step size). object: unit: range: default: reference: PTPPKF 2dB 0. The UE is thus instructed to report. if available. <NULL> 2 3GPP 45. If C31H=TRUE. Which value should be set for this parameter strongly depends on the environment of the cell (BTS).008 3GPP 44. The default value of ‘0’ only makes sense in areas without any 3G neighbours (no ADJC3G object created for this BTS). this parameter is relevant for the feature 'Network Controlled Cell Reselection from GSM/GPRS to UMTS due to UMTS Sufficient Coverage' (see parameter EUSCNCRESEL in command SET BSC [BASICS]) and corresponds to the 3GPP parameter FDD_MULTIRAT_REPORTING which is sent to the MS/UE . When GASTRTH is exceeded the vertical allocation will start on the layer preferred for the affected GPRS service. all resources that can be used by CS calls..

g. the MS updates the value RLA_P (receive level average of cell) for the serving cell and of the at least 6 strongest non-serving GSM cells at least every 5s.060 GFDDQMIO=DB00. whenever decoded from a UTRAN FDD cell of an equivalent PLMN.xxdB (e. The MS then reselects a suitable FDD UTRAN cell if for this FDD cell the following criteria are all met for a period of 5s: 1. Cell reselection to UTRAN is prohibited within 5 seconds after the MS/UE has reselected a GSM cell from an UTRAN cell if a suitable GSM cell can be found. see above). The cell’s measured RSCP value is equal to or greater than the threshold FDD_RSCPmin (parameter GFDDRSCPMI. the MS selects the cell with the greatest RSCP value. The parameters required to determine if the UTRAN cell is suitable are broadcast on BCCH of the UTRAN cell. DB10 = 10dB) 257 . see below) when broadcast in the serving cell. The parameter values express a value in dBm DBxx = xxdB (e. this parameter corresponds to the 3GPP parameter FDD_Qmin which is broadcast on the PBCCH in the PACKT SYSTEM INFORMATION TYPE 3quater and is a threshold for signal Ec/No which is used for the algorithm for GPRS GSM to UTRAN cell reselection. The UE stores the UTRAN cell RSCP suitability criterion parameters above. it is used by the MS/UE for the cell reselection algorithm from GSM to UTRAN. FDDQMIO represents an offset which is applied to the parameter FDD_Qmin (parameter FDDQMI.FDD_Qmin_Offset (parameter GFDDQMIO. MDB20 = -20dB) Algorithm for (GPRS) cell re-selection from GSM to UTRAN If the 3G Cell Reselection list includes UTRAN frequencies. If more than one UTRAN cell fulfils the above criteria. Note: For the meaning of the measurement values RSCP and Ec/No please refere to the description of parameter GFDDREPQTY (see below). GPRS FDD Q mininum offset. see above). FDD_GPRS_Qoffset is increased by 5 dB. see below) and 3. object: range: PTPPKF MDB20 MDB19 MDB18 MDB17 MDB16 MDB15 MDB14 MDB13 <NULL> default: <NULL> reference: 3GPP 45.008 3GPP 44.060 GPRS FDD Q minimum.GFDDQMI =<NULL>. 2. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter FDDQMI (see above). this parameter corresponds to the 3GPP parameter FDD_Qmin_Offset which is broadcast on the PBCCH in the PACKET SYSTEM INFORMATION TYPE 3quater and is related to multiRAT mobiles. Note: When a cell reselection has occurred within the previous 15 seconds.008 3GPP 44.g. object: range: PTPPKF DB00 DB04 DB06 DB08 DB10 DB12 DB14 default: DB00 reference: 3GPP 45. The cell’s measured Ec/No value is equal or greater than the value FDD_Qmin . The parameter values express a value in dB MDBxx = . An MS/UE may start reselection towards the UTRAN cell before decoding the BCCH of the UTRAN cell. The cell’s measured RSCP value exceeds the value of RLA_P for the serving cell and all of the suitable non-serving GSM cells by the value FDD_GPRS_Qoffset (parameter FDDGQO.

MDB099. this value indicates the DL quality in the UMTS FDD neighbour cell and is thus comparable to the RXQUAL resp. MDB105.7 3 3GPP 45. MDB111. this parameter corresponds to the 3GPP parameter FDD_REP_QUANT which is sent to the MS/UE .If GFDDREPQTY is set to RSCP.060 GHCSPC=3.in the PACKET CELL CHANGE ORDER messages via the PACCH which commands to leave the current cell and to change to a new one (which may also be an FDD cell). object: range: default: Reference: PTPPKF 0. MDB101.008 3GPP 44.. For details about the cell reselection algorithm from GSM to UTRAN please refer to the description of parameter GFDDQMI (see above). object: range: PTPPKF MDB115.xxxdBm (e. It determines in which way the MSs shall report the radio conditions of UMTS FDD neighbour cells. The setting of the GFDDREPQTY has an influence on the decision process of the feature 'NCCR from GSM/GPRS to UMTS due to UMTS sufficient coverage': 2G-3G cell reselection due to ‘sufficient coverage’ is possible with both settings of FDDREPQTY. GPRS FDD RSCP minimum.GFDDREPQTY=<NULL>. MDB089. MultiRAT mobiles (RAT=Radio Access Technology) can report the radio conditions of UMTS FDD neighbour cells either by RSCP values (level oriented) or by Ec/No values (quality oriented) but not both at the same time. this parameter corresponds to the 3GPP parameter PRIORITY_CLASS and represents the Hierarchical Cell Structure priority for the cell reselection procedure. The parameter values express a value in dBm MDBxxx = .008 258 . MDB107. The setting of FDDREPQTY determines which of the two reporting methods shall be used by the multiRAT MSs.it is used by the UE for the GPRS cell reselection algorithm from GSM to UTRAN. FDDRSPMI represents a minimum RSCP threshold a UTRAN must exceed to be considered for GSM to UTRAN cell reselection. . the sufficient coverage condition is defined by the RSCP-oriented parameter USRSCPNCRESEL. MDB109. MDB091. MDB093.008 3GPP 44. MDB085 default: MDB101 reference: 3GPP 45. the sufficient coverage condition is defined by the Ec/No-oriented parameter USECNONCRESEL. this parameter corresponds to the 3GPP parameter FDD_RSCPmin which is broadcast on the PBCCH in the PACKET SYSTEM INFORMATION TYPE 3quater and is related multiRAT mobiles . MDB097. object: range: default: reference: PTPPKF RSCP. • Ec/No = Energy chip to Noise over all. C/I values in GSM. The possible values are • RSCP = Received Signal Code Power this value indicates the DL receive level in the UMTS FDD neighbour cell and is thus comparable to the RXLEV value in GSM.060 GPRS FDD reporting quantity. EC_NO.in the PACKET SYSTEM INFORMATION TYPE 3quater messages via the PBCCH and .If GFDDREPQTY is set to EC_NO. MDB087. MDB095. MDB115 = -115dBm) GPRS hierarchical cell structure priority class. MDB113. but the processing of the measured values is different: .g. <NULL> RSCP 3GPP 45. For both parameters (USRSCPNCRESEL and USECNONCRESEL) please refer to command CREATE ADJC3G. MDB103.in the PACKET SYSTEM INFORMATION TYPE 5 messages via the PBCCH . GFDDRSCPMI=MDB101.

3 (for each field) default: 2-2-2-2 Reference: 3GPP 44. in this case GMANPRESPRM defines the overall number of TCHs reserved for GPRS on the TRXs that are included in the SLLs of GPRS services. For standard cells and dualband standard cells (CELLTYPE=STDCELL or DBSTDCELL. object: format: PTPPKF 2 fields: < maxNoOfMS_UL >< maxNoOfMS_DL >range: 1-7 (maxNoOfMS_UL) 1-16 (maxNoOfMS_DL) default: 7 (maxNoOfMS_UL) 16 (maxNoOfMS_DL) Reference: 3GPP 44.. the second one indicates the maximum number of MS that can be multiplexed on a PDCH in downlink direction. GPRS maximum Number of PDCH reserved Primary.e. 31=-48dB default: 10 Reference: 3GPP 45. see command CREATE BTS [BASICS]). In case of non-extended cell. each field indicates the maximum number of retransmissions allowed for the affected priority level. object: format: PTPPKF 4 fields for each priority level: prio1-prio2-prio3-prio4 range: 0.190 0 GMANRETS=2-2-2-2. object: unit: range: PTPPKF 2dB 0.190 0 GMANPRESPRM=0. Priority 1 represents the highest priority.060 GPRS maximum number of allocated MSs . Please see also command SET BTS [SERVICE] for further explanations about the feature ‘Service Dependent Channel Allocation. GPRS maximum number of retransmissions. It is composed of two fields: the first indicates the maximum number of MS that can be multiplexed on a PDCH in uplink direction. GMANMSAL=7-16. see command CREATE BTS [BASICS]).. see command CREATE BTS [BASICS]) there is only one primary area. object: range: default: PTPPKF 0. this parameter corresponds to the 3GPP parameter MAX_RETRANS and indicates for each priority level 1 to 4 the maximum number of retransmission allowed on the PRACH.. this parameter corresponds to the 3GPP parameter HCS_THR and indicates the signal strength threshold used in the HCS cell reselection procedure (C31). only the parameter GMANPRESPRM (see below) is relevant. i.060 replaced by GMANPRESPRM in BR8. For each Radio Priority x parameter the following table is applied: 00 01 10 11 1 retransmission allowed 2 retransmissions allowed 4 retransmissions allowed 7 retransmissions allowed 259 . object: range: default: PTPPKF 0. The total amount of TBFs multiplexed on a PDCH is limited GMANPRES GMANPRESCOM=0. the primary area corresponds to the ‘far area’ (double timeslots) of the extended cell. If the cell is configured as extended cell (CELLTYPE=EXTCELL.008 GPRS hierarchical cell structure threshold.GHCSTH=10. Please see also command SET BTS [SERVICE] for further explanations about the feature ‘Service Dependent Channel Allocation. this parameter defines the number of traffic channels reserved for GPRS in the ‘Complementary Area’ which corresponds to the ‘near area’ (single timeslots) in an extended cell (CELLTYPE=EXTCELL. The parameter value consists of 4 fields.0 GPRS maximum Number of PDCH reserved Complementary..31 0=-110dB. this parameter defines the number of traffic channels reserved for GPRS in the ‘Primary Area’. this parameter indicates the maximum number of MSs that can be multiplexed on a PDCH in the cell.

object: range: default: Reference: PTPPKF 0. Note: In case Network Controlled Cell Reselection (NCCR) is activated in the cell (NCRESELFLAG=ENABLED). The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell. If there are still remaining positions. It is the GPRS equivalent to the parameter NMULBAC (see command CREATE BTS [BASICS]) and used by GPRS attached mobiles in case a PBCCH is created in the cell. with known and allowed NCC part of BSIC. Please see also parameter GUMTSSRHPRI (same command. excluding the frequency band of the serving cell. these shall be used to report the next strongest identified cells in the other bands irrespective of the band used. This parameter is is relevant for GPRS network-controlled cell reselection in dualband configurations. GPRS Number of multi band cells.. with known and allowed NCC part of BSIC. If there are still remaining positions.008 Maximum allowed GPRS MS transmission power on PBCCH/ PCCCH. 260 . in each of the frequency bands in the BA list. Possible values are: 0 . The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell. 3 .The MS shall report the strongest cell.GMSTXPMAC=2.. these shall be used to report the next strongest identified cells in the other bands irrespective of the band used.060 GNMULBAC=<NULL>. It specifies in which way the MS shall monitor and report the neighbour cells of the frequency bands used in the serving and neighbouring cells. this parameter corresponds to the 3GPP parameter GPRS_MS_TXPWR_MAX_CCH and defines the maximum power level that may be used by the mobile to access the cell on the PRACH. these shall be used to report the next strongest identified cells in the other bands irrespective of the band used.The MS shall report the three strongest cells.The MS shall report the two strongest cells. with known and allowed NCC part of BSIC. excluding the frequency band of the serving cell. the PCU uses GRXLAMI as well as GMSTXPMAC to calculate the C1 values also in case no PBCCH is created in the cell.3 <NULL> 3GPP 45. irrespective of the band used. excluding the frequency band of the serving cell.broadcast on the PBCCH in the PACKET SYSTEM INFORMATION TYPE 3 and . 2 . The remaining positions in the measurement report shall be used for reporting of cells in the band of the serving cell. The valid values and meanings are the same as defined for the parameter MSTXPMAXCH (see SET BTS [CCCH]). object: range: default: Reference: PTPPKF 0. If there are still remaining positions. see below).sent to the MS/UE within the PACKET CELL CHANGE ORDER message and within the PACKET MEASUREMENT ORDER message via the PACCH. this parameter corresponds to the 3GPP parameter MULTIBAND_REPORTING which is . with known and allowed NCC part of BSIC. 1 . in each of the frequency bands in the BA list.Normal reporting of the six strongest cells. in each of the frequency bands in the BA list.31 2 3GPP 44.

this parameter indicates the percentage of available “shared” traffic channels that may be used for GPRS traffic.1 SGSN). GMM/SM procedures are not affected.GPATH=PKAAP4. Note: Modification of the GPDPDTCHA setting is only possible.g. object: unit: range: default: PTPPKF 1% 0.PKAAP4 default: PKAAP4 Reference: 3GPP 44.060 GPRS priority access threshold. GPDPDTCHA determines the percentage of these TCHs that the BSC may use for GPRS traffic (the calculated value is rounded down). object: range: PTPPKF PKANA PKAAP1 . all mobiles having Prio 4 assigned do not perform a network access. If the network indicates e. if the PTPPKF object is in administrative state ‘locked’. only Prio 1 accesses are allowed. TCHSD in TCHPOOL) for which the parameter GDCH is set to <NULL> (see CREATE CHAN for TCH) and for which the superordinate TRX is in service and available for GPRS service (this is the case if the TRX is defined as belonging to a service layer which is included in the SLL for GPRS services please see command SET BTS [SERVICE] for further explanations). “Shared traffic channels” are those channels (TCHFULL. The field is coded according to the following table: PKANA PKAAP1 PKAAP2 PKAAP3 PKAAP4 000 011 100 101 110 packet access is not allowed in the cell packet access is allowed for Priority class 1 packet access is allowed for Priority class 1 to 2 packet access is allowed for Priority class 1 to 3 packet access is allowed for Priority class 1 to 4 GPDPDTCHA=100. this parameter corresponds to the 3GPP parameter PRIORITY_ACCESS_THR and indicates whether or not a mobile station of a certain priority class is authorised to do a random access in order to request for GPRS services. All TCHs created with these attributes represent 100%. TCHF_HLF.100 100 Default value changed in BR8. depends on the setting of the parameter DGRSTRGY (see SET BTS [BASICS]). 261 . GPRS Percentage of dynamic PDTCH Available. Whether these TCHs may be preempted respectively downgraded for circuit-switched calls.0! During the PDP Context activation an MS is assigned a Radio Priority (only Prio 4 is allocated using a Siemens PO3..

P if GMSTXPMAC > P Max (B. .GRXLAMI=6. which is broadcast in the PACKET SYSTEM INFORMATION TYPE 3 on the PBCCH and which is defined by the ADJC cell objects with GSUP=TRUE (see command CREATE ADJC). the PCU uses GRXLAMI as well as GMSTXPMAC to calculate the C1 values also in case no PBCCH is created in the cell.0) ensures that the transmit power capability is considered in addition to the minimum receive level defined by GRXLAMI: The lower the maximum transmit power of the MS is .P = GMSTXPMAC . this parameter corresponds to the 3GPP parameter GPRS_RXLEV_ACCESS_MIN and is used by the MS required to access the network on the PRACH. the higher must be the minimum RXLEV for access..0)) where = <receive level average> .+ GPRS_RXLEV5) The path loss criterion C1. is calculated by the following formula: C1 = (A .63 6 3GPP 44. In case a PBCCH is configured in the cell. object: range: default: Reference: PTPPKF 0.. 262 ..In case Network Controlled Cell Reselection (NCCR) is activated in the cell (NCRESELFLAG=ENABLED).Max(B. It is used together with other parameters to calculate the path loss criteria C1 and C32 for cell selection and reselection.0)= GMSTXPMAC .P P = Maximum RF output power of the MS (see table under parameter MSTXPMAXDCS in command SET BTS [BASICS]). where: – RLA_P(s) is the averaged level for the serving cell – RLA_P(n) are the averaged levels for neighboring cells The cells to be monitored for cell reselection are defined by the BA(GPRS) list. Notes: . the minimum signal level criterion for GPRS/EGPRS cell selection and cell re-selection. A GPRS MS measures the received signal level on the PBCCH carriers of the serving cell and the surrounding cells and calculates the mean received level (RLA_P) for each carrier.If no PBCCH is configured in the cell.GPRS_RXLEV_ACCESS_MIN = RLA_P – GRXLAMI B = GPRS_MS_TXPWR_MAX_CCH . This parameter is sent for the serving as well as the indicated neighbour cells on the PBCCH (PACKET SYSTEM INFORMATION TYPE 3). Max (B. Setting GRXLAMI to a high value means that only those GPRS mobiles attempt to access the cell which are in a location with good coverage conditions. the C1 criterion is calculated in the same way as it is done for standard GSM (non-GPRS MS)on the basis of the parameters RXLEVAMI and MSTXPMAXCH as described in parameter CELLRESH (see command CREATE BTS [BASICS]).0)= 0 if GMSTXPMAC < P A Subtracting Max(B. GPRS mobiles use this parameter instead of the GSM equivalent RXLEVAMI (object BTS). At least 5 received signal level measurement samples are required for a valid RLA_P: RLA_P = 1/5 ∗ (GPRS_RXLEV1 + GPRS_RXLEV2 + .060 GPRS minimum receive level.

The UE is thus instructed to report. The field is coded according to the following table: 0000 3 slots 1000 0001 4 slots 1001 0010 5 slots 1010 0011 6 slots 1011 0100 7 slots 1100 0101 8 slots 1101 0110 9 slots 1110 0111 10 slots 1111 used to spread transmission.in the PACKET SYSTEM INFORMATION TYPE 3quater messages via the PBCCH and . this parameter corresponds to the 3GPP parameter TDD_MULTIRAT_REPORTING which is sent to the MS/UE . 11 slots 12 slots 14 slots 16 slots 20 slots 25 slots 32 slots 50 slots 263 . This parameter indicates the number TDD UTRAN cells the MS/UE shall include in the MEASUREMENT REPORTs sent in ‘GPRS attached’ mode. The default value of ‘0’ only makes sense in areas without any 3G TDD neighbours (no ADJC3G object created for this BTS). All other values reserved. GPRS TDD multiRAT reporting.008 3GPP 44. Which value should be set for this parameter strongly depends on the environment of the cell (BTS).in the PACKET SYSTEM INFORMATION TYPE 5 messages via the PBCCH . The value must therfore be set considering how many 2G neighbour cells shall be reported in any case. object: range: default: Reference: PTPPKF 0. The more really relevant 3G TDD cells are available.3 <NULL> 3GPP 45... this number of 3G neighbour cells. GPRS transmission interval. object: range: default: reference: PTPPKF 0. object: range: default: Reference: PTPPKF 0.9 8 3GPP 44..060 GTXINT=3. the higher the value should be set. this parameter is used for calculation of the number of slots between two successive Channel request messages on PRACH channel.060 GPRS number of slots between two PRACH accesses. The field is coded according to the following table: 0000 0010 0100 0110 1000 S = 12 S = 20 S = 41 S = 76 S = 163 0001 0011 0101 0111 1001 S = 15 S = 30 S = 55 S = 109 S = 217 GTDDMURREP=<NULL>.15 3 3GPP 44.060 S represents the number of slots between two consecutive accesses. if available.in the PACKET CELL CHANGE ORDER messages via the PACCH which commands to leave the current cell and to change to a new one (which may also be a TDD cell). Usually 6 neighbour cells can be reported within one MEASUREMENT REPORT message. this parameter corresponds to the 3GPP parameter TX_INT and defines the number of slots to spread transmission of the random access on PRACH channel.GS=8.

the MS may use up to 25 search frames per 13 seconds without considering the need for BSIC decoding or packet transfer mode interference measurements in these frames. If a GPRS MS works in packet transfer mode it monitors continuously all BCCH carriers as indicated by the BA(GPRS) list and the PBCCH carrier of the serving cell. For this monitoring. if the neighbor cell list contains cells from other radio access technologies (RATs).060 GPRS UMTS search priority. cells or frequencies with other radio access technologies may also be included in the GPRS 3G Cell Reselection list.g. The network controls the measurements for reselection of those cells by the parameter Qsearch_P broadcast on PBCCH (parameter QSRHPRI. In addition the MS verifies the BSIC of the BCCH carriers.008 3GPP 44. a received signal level measurement sample is taken on at least one of the BCCH carriers. In every TDMA frame.in the PACKET SYSTEM INFORMATION TYPE 5 messages via the PBCCH . object: range: default: reference: PTPPKF TRUE.in the PACKET SYSTEM INFORMATION TYPE 3quater messages via the PBCCH and . Only cells with allowed BSIC are considered for re-selection purposes. the MS may use up to 25 search frames per 13 seconds without considering the need for BSIC decoding or packet transfer mode / MAC-Shared state interference measurements in these frames. and at least every 10 seconds.GUMTSSRHPRI =TRUE. e. one after the another. . and is maintained for each BCCH carrier. A multi-RAT MS is allowed to extend this period to 13 seconds. If indicated by the parameter 3G_SEARCH_PRIO (=GUMTSSRHPRI). 3G neighbour cells. The samples allocated to each carrier shall as far as possible be uniformly distributed over the evaluation period. FALSE.the BCCH carrier of the serving cell. this parameter corresponds to the 3GPP parameter 3G_SEARCH_PRIO which is sent to the MS/UE . 264 . RLA_P is an average value determined using samples collected over a period of 5s. For a multi-RAT MS.in the PACKET CELL CHANGE ORDER messages via the PACCH which commands to leave the current cell and to change to a new one (which may also be an FDD cell). <NULL> TRUE 3GPP 45. This parameter indicates if a ‘GPRS attached’ mobile can search 3G cells when BSIC decoding is required. If GUMTSSRHPRI=TRUE. The MS continuously measures the received RF signal level on: . For each of the monitored cells it calculates the average received level (RLA_P). The MS attempts to check the BSIC for each of the 6 strongest non-serving cell BCCH carriers as often as possible.the BCCH carriers of neighbour cells as indicated in the BA(GPRS) list. see below in same command). This list may be modified by PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER messages sent via the PACCH. At least 5 received signal level measurement samples are required for a valid RLA_P value. the MS may use search frames that are not required for BSIC decoding or interference measurements in packet transfer mode or MACShared state.

this parameter the weight for class. 2-phase access or EDGE PACKET CHANNEL REQUEST was used) of this mobile. It is also used as input parameter to calculate the amount of radio resources necessary to fulfil the QOS requirements (Peak Throughput Class).g. If the BSC is informed about the EDGE capability (e.060 Initial coding scheme. <NULL> MCS3 INIBLER=PER10. traffic handling priority 1 (scheduling priority 1). 265 . this parameter parameter corresponds to the 3GPP parameter INITIAL_CODING_SCHEME and indicates the coding scheme to be allocated when the packet transfer starts. traffic handling priority 2 (scheduling priority 2).. INTRTRFH3WEI=2. PER80. INTRTRFH2WEI=4. PER70.. this parameter the weight for class. This value is used in radio resource management to calculate the initial number of radio resources to be assigned to packet services in case no ‘historical’ information about BLER is available (see parameter STGTTLLIINF).32 2 Interactive Traffic Handling Priority 3 Weight. Initial MCS uplink Wout incremental redundancy GMSK. CS2. traffic handling priority 3 (scheduling priority 3)...INTRTRFH1WEI=8. this parameter specifies the MCS to be used in an EDGE UL TBF if the MS supports GMSK only and no other information about that MS in that BVC is available (see parameter STGTTLLIINF). object: range: default: PTPPKF 1. MCS7. The values CS3 and CS4 are available only in case CSCH3CSCH4SUP=TRUE in the cell. PER60. MCS2. object: range: default: PTPPKF 1.. MCS6. 2-phase access or EDGE PACKET CHANNEL REQUEST was used) of this mobile. object: range: default: Reference: PTPPKF CS1. Default value changed in BR8. this parameter defines the initial BLER estimation in a cell to be used. MCS4. this parameter specifies the MCS to be used in an EDGE UL TBF if the MS supports 8PSK and no other information about that MS in that BVC is available (see parameter STGTTLLIINF). it uses the value of IMCSULNIR8PSK in order to calculate the best possible resource allocation for the requested UL TBF. Initial BLER. IMCSULNIR8PSK =MCS3. PER90 PER10 Default value changed in BR8. CS4 CS2 3GPP 44. MCS4.32 8 Interactive Traffic Handling Priority 1 Weight. object: range: PTPPKF MCS1. object: range: default: PTPPKF 1. MCS5. CS3. MCS3. object: range: default: PTPPKF MCS1. this parameter the weight for class. MCS2.32 4 Interactive Traffic Handling Priority 2 Weight. MCS9 <NULL> MCS3 default: Initial MCS uplink Wout incremental redundancy 8PSK.. MCS8. it uses the value of IMCSULNIR8PSK in order to calculate the best possible resource allocation for the requested UL TBF. object: range: default: PTPPKF PER50.0! IMCSULNIRGMSK =MCS3. If the BSC is informed about the EDGE capability (e. MCS3.0! INICSCH=CS2.g.

PER90 PER70 MSBLPER=PER60. Caution: It is strictly recommended to maintain the default value! MS bucket low percentage. object: range: default: Reference: PTPPKF PER50. MSBLPER) are based on this value.C corresponds to the parameter TF1 (object PCU) .18 266 . PER80. object: range: default: Reference: PTPPKF PER10. PER110. Caution: It is strictly recommended to maintain the default value! MSBHIPER=PER70. MCS7. PER060 PER070. PER60 MSBMAPER=PER100. PER120. PER150 PER160.. This parameter specifies the ‘MS Bucket Size PCU’ value based on the ‘MS Bucket Size’ value Bmax reported to the SGSN.100 4 Maximum failures neighbour cell UMTS. this parameter specifies the MCS to be used in an EDGE DL TBF if the MS supports 8PSK and no other information about that MS in that BVC is available (see parameter STGTTLLIINF). the leak rate is further decreased. Caution: It is strictly recommended to maintain the default value! MS bucket size PCU percentage..) * Rmax . As consequence the Flow Control Algorithm will reduce the reported leak rate ‘R’ inside the FLOW-CONTROL-MS PDU. PER180 PER190 PER200 default: PER100 Reference: GSM08. PER30. PER20. MCS8. MCS4. PER050. thus limiting the amount of data being sent from the SGSN towards the BSC. PER140. object: range: PTPPKF MCS1. MS Bucket Size PCU = MSBSPPER * MS Bucket Size It represents the buffer space ‘reserved’ in the PCU for this MS. If the congestion state persists. PER030. MCS3.0! MAFAILNCU=4. PER140. As soon as the congestion state is cleared. PER040. If the MS Bucket Level is lower than MSBLPER * MS Bucket Size PCU. PER150 PER160.Rmax is the maximum rate assigned to that MS: Number of timeslots assigned multiplied by the respective maximum rate per TS multiplied by the usage percentage (100% if no other MS is sharing that TS). Caution: It is strictly recommended to maintain the default value! MS bucket max percentage. PER170. default: Default value changed in BR8. PER40. MCS2. object: range: default: PTPPKF 1. object: range: PTPPKF PER100. PER70. defines the value of the ‘MS Bucket Size’ (Bmax) reported in the FLOW-CONTROL-MS PDU towards the SGSN: MS Bucket Size = MSBMAPER * (C + 1 sec. If the MS Bucket Level is greater than MSBHIPER * MS Bucket Size PCU. PER70. MCS5. MCS9 <NULL> MCS6 Initial MCS downlink.18 MSBSPPER=PER200. PER130. PER170. PER110. PER080. MCS6. this parameter the maximum number of PACKET CELL CHANGE ORDER messages transmitted vie the PACCH for the same UMTS Neighbour cell for a MS/UE. PER130. The value of INIMCSDL is also used as input parameter to calculate the amount of radio resources necessary to fulfil the QOS requirements (Peak Throughput Class). the ‘Bucket Congestion’ state is activated. MS bucket high percentage. PER80. the leak rate ‘R’ inside the FLOW-CONTROL-MS PDU is set to its original value and the SGSN may increase the data rate sent towards the BSC. PER090 PER100. PER120. PER60. The MS congestion thresholds (MSBHIPER. in case the ordered cell change fails. PER60. PER180 PER190 PER200 default: PER200 Reference: GSM08. object: range: PTPPKF PER010.INIMCSDL =MCS6. PER50. the ‘Bucket Congestion’ state is ceased. PER020.

Network controlled cell reselection traffic packet switched control threshold. k = 0. Note: When this attribute is set to TRUE .100 default: 75 Reference: 267 .DB29. otherwise RGUA is used.DB30 default: DB00 Reference: NCSARA=TRUE. If NCSARA is set to FALSE. NCC1TH=DB03. object: range: default: Reference: PTPPKF 0.008 N averaging interference. If the BSC finds a suitable adjacent cell in this subgroup.. DB02 = 2dB etc. 1.MSRMAXU=FALSE. the adjacent cells of the same routing area have no priority compared to the adjacent cells of other routing areas and the BSC will select the best suitable cell for cell reselection. this parameter specifies the additional hysteresis (in steps of 1dB. this parameter corresponds to the 3GPP parameter N_AVG_I represents an interfering signal strength filter constant for power control 2(k/2).. The equivalent parameter in case NCCR is disabled is RARESH. Note: NCRARESH is used in case of NCCR only. object: range: default: PTPPKF TRUE. a network controlled cell reselection is attempted.): If the C1 value measured on the serving cell falls below NCC1TH. If network controlled cell reselection is to be performed and NCSARA is set to TRUE. object: PTPPKF range: TRUE. the BSC first of all searches an adjacent cell that belongs to the same routing area like the serving cell. Network controlled cell reselection routing area reselect hysteresis. Rmax is used for Bmax and R computation. DB01. object: PTPPKF range: DB00. NAVGI=10. object: PTPPKF range: DB00. NCRARESH=DB00.. DB02 = 2dB etc. the BSC classifies the available adjacent cells in two subgroups: a) adjacent cells that belong to the same routing area as the serving cell and b) adjacent cells that do not belong to the same routing area as the serving cell.DB63 default: DB03 Reference: Network controlled cell reselection C1 threshold. the parameter NCRARESH (see above) has to be set to DB00 (default value). FALSE FALSE Mobile station rate max used. This parameter establishes the threshold concerning the C1 value for network controlled cell reselection (NCCR) in steps of 1dB (DB01 = 1dB. Please refer to the parameter CRESELTRHSOUT for further details. this cell will be selected for cell reselection. this parameter specifies the traffic load threshold in percent below which no more mobiles are moved out of a cell due to traffic reasons. … . object: PTPPKF range: 30.DB62. It has to be set to 0 in case the parameter NCSARA =TRUE. 15. if this parameter is TRUE. FALSE default: TRUE Reference: NCTRFPSCTH=75.. DB01 = 1dB.) to be subtracted from C32 of an adjacent cell belonging to a different routing area than the serving cell. DB01. irrespective of its association to a routing area. this parameter determines whether cells of the same routing area are to be preferred during the network controlled cell reselection procedure. Network controlled cell reselection same routing area.15 10 3GPP 45. When NCSARA is set to TRUE.

object: range: PTPPKF MSEC480. Network controlled cell reselection report period idle. MSEC61440 MSEC3840 default: Reference: PCMECH=MEABCCH. default: Reference: NTWCOR=NC0. MSEC30720.MSEC15360. PACKET SYSTEM INFORMATION TYPE 1 and PACKET SYSTEM INFORMATION TYPE 5. MSEC7680. MSEC1920. MS sends measurement reports NTWCREPPIDL= MSEC61440. MSEC960. the BSC sends a PACKET MEASUREMENT ORDER at the beginning of each TBF indicating NC2 for the respective mobile.060 Network control order. no measurement reporting NC1: value 1 MS controlled cell reselection. object: range: default: Reference: PTPPKF MEABCCH. Before the TBF is terminated. MSEC1200. Only in case the feature Network Controlled Cell Reselection (NCCR) is activated (NCRESELFLAG=TRUE). this parameter corresponds to the 3GPP parameter NC_REPORTING_PERIOD_T and indicates the time period between two consecutive PACKET MEASUREMENT REPORT (PMO) messages while the MS is in packet transfer mode. MSEC960. this parameter corresponds to the 3GPP parameter NETWORK_CONTROL_ORDER and is transmitted in (PACKET) SYSTEM INFORMATION TYPE 13. the Network Control Order is reset to NC0.MSEC3840. this parameter corresponds to the 3GPP parameter PC_MEAS_CHAN and indicates where the mobile station shall measure the received power level on the downlink for the purpose of the uplink power control.NTWCNDRXP=MSEC0480. this parameter indicates the minimum time (in milliseconds. MSEC240. object: range: PTPPKF MSEC480 . MSEC480.060 Power control measurement channel. NC1 NC0 3GPP 44. Values can be: NC0: value 0 MS controlled cell reselection.MSEC15360. this parameter corresponds to the 3GPP parameter NC_REPORTING_PERIOD_I and defines the time period between two consecutive PACKET MEASUREMENT REPORT (PMO) messages while the MS is in packet idle mode. informs the mobile about the control of cell reselection.MSEC3840. . MSEC7680. object: range: PTPPKF NODRX. . MSEC960. MSEC30720. 268 . MS sends measurement reports NC2: value 12 NTW controlled cell reselection. object: range: default: Reference: PTPPKF NC0. MSEC1920. NTWCREPPTR= MSEC3840. Setting PCMECH to MEABCCH means: downlink measurements for power control shall be performed on the BCCH. MSEC720. MEAPDTCH MEABCCH 3GPP 44. MSEC1440. MSEC1920 MSEC0480 Network controlled cell reselection report period transfer. MSEC61440 MSEC61440 default: Reference: In normal operation the network always broadcasts the value NC0. Network controlled cell reselection report period transfer. MSC0480 =480ms) the mobile station shall remain in non-DRX mode after a PACKET MEASUREMENT REPORT message had been sent. Setting PCMECH to MEAPDTCH means: downlink measurements for power control shall be performed on the PDCH. Note: This parameter is not used in BR70 as the BSC does not set NC1/NC2 for mobiles in packet idle mode.

object: PTPPKF range: 0. per_30. per_150. per_140. per_70. 16 default: 5 Reference: GSM 04. per_160. object: PTPPKF range: 0. For further details please refer to PERSTLVPRI1 above. object: PTPPKF range: 0. pfc) and Rgua. per_160. per_200 per_200 PFC background bucket maximum percentage. per_20.pfc guaranteed flow rate out of the buffer in the PCU. per_190. per_20. if PFC Bucket Level is lower than PFCBackgroundBucketHighPercentage * BackgroundBucketMaxPCU PFCBBLPER=per_60. …. per_40. It specifies the access persistence on PRACH for TBFs with radio priority 3. For further details please refer to PERSTLVPRI1 above. per_200 per_100 PFC background bucket maximum percentage. per_170.14. per_110. object: PTPPKF range: 0. this parameter reduces the value of Bmax automatically computed by the BSC.. per_60. 16 default: 5 Reference: GSM 04.. PFC background bucket high percentage. per_30. default: PFCBBMAPPER=per_200. 14. per_170.60 PERSTLVPRI2=5. per_120. It specifies the access persistence on PRACH for TBFs with radio priority 1. default: 269 . PFCBBMAPER=per_100. PFC background bucket low percentage. per_90 per_70 the Bucket Congestion is started. object: range: default: PTPPKF per_10. per_120. per_140. this parameter is broadcast in the Packet System Information Type 1 on the PBCCH. For further details please refer to PERSTLVPRI1 above. object: range: default: PTPPKF per_50. 14. per_100.60 PFCBBHIPER=per_70. per_70. per_80.. BSC criteria is BmaxPFC=PFCBBMAPER *Fn*(1sec+TF1)*Rgua. 16 default: 5 Reference: GSM 04.60 PERSTLVPRI4=5. 16 default: 5 Reference: GSM 04. per_80. per_110. per_60. per_90. per_70. per_50. It specifies the access persistence on PRACH for TBFs with radio priority 2. Persistence level priority 4. this parameter is broadcast in the Packet System Information Type 1 on the PBCCH. per_130. The MS is allowed to transmit an (EGPRS) PACKET CHANNEL REQUEST message only in case the value of PERSTLVPRI1 is less or equal to R. this parameter is broadcast in the Packet System Information Type 1 on the PBCCH. per_130. For each access attempt the MS shall draw a random value R with uniform distribution in the range (0. Therefore a high value of PERSTLVPRI1 decreases the probability of a network access for a TBF with radio priority 1. this parameter is broadcast in the Packet System Information Type 1 on the PBCCH.. per_80 per_60 the Bucket Congestion is stopped. per_180.PERSTLVPRI1=5. object: range: PTPPKF per_100. object: range: PTPPKF per_10. this parameter assignes the value of Background Bucket Max PCU as percentage of Bmax. per_150. 15). per_50. Persistence level priority 3. per_190. per_40. per_180. It specifies the access persistence on PRACH for TBFs with radio priority 4. Persistence level priority 2. if PFC Bucket Level is greater than PFCBackgroundBucketHighPercentage * BackgroundBucketMaxPCU PERSTLVPRI3=5. per_60. 14.60 Persistence level priority 1.

PFC interactive bucket high percentage. per_60. Rmax is used for Bmax and R computation. per_110.PFCBRMAXU=FALSE. per_70. PFC interactive bucket low percentage. object: range: default: PTPPKF TRUE. PFCBRPER=per_100. per_130. this parameter assignes the value of Intercative Bucket Max PCU as percentage of Bmax. this parameter reduces the value of Bmax automatically computed by the BSC. per_40. per_120. per_190. per_40. per_130. per_150. object: range: default: PTPPKF per_50. per_180. per_100. FALSE FALSE PFC interactive rate max used. default: PFCIRMAXU=FALSE. per_190. object: range: PTPPKF per_10. per_60. PFCIRPER=per_100. per_190. if this parameter is TRUE. this parameter defines ??? default: 270 . per_120. per_140. per_130. per_70. pfc) and Rgua. per_30. per_110. per_90. per_70. per_60. per_50. per_160. per_100. per_160. per_180. per_150.pfc guaranteed flow rate out of the buffer in the PCU. per_120. per_140. per_190. per_140. object: range: PTPPKF per_100. PFCIBLPER=per_60. per_150. per_80. per_30. per_30. per_50. per_200 per_200 PFC interactive bucket max PCU percentage. per_60. per_170. per_80. per_160. per_40. object: range: default: PTPPKF TRUE. per_40. per_20. per_100. per_70. object: range: default: PTPPKF per_10. per_150. per_90. per_80. per_120. per_180. per_20. per_90. per_80. per_50. per_110. per_200 per_100 PFC background rate percentage default: PFCIBHIPER=per_70. per_180. otherwise RGUA is used. Rmax is used for Bmax and R computation. if PFC Bucket Level is greater than PFCInteractiveBucketHighPercentage * InteractiveBucketMaxPCU the Bucket Congestion is started. per_110. object: range: PTPPKF per_10. per_170. per_160. per_200 per_100 default: PFCIBMAPPER=per_200. per_200 per_100 PFC interactive rate percentage. per_20. otherwise RGUA is used. object: range: PTPPKF per_10. per_30. FALSE FALSE PFC background rate max used. if this parameter is TRUE. per_20. per_170. per_170. per_90 per_70 PFC interactive bucket high percentage. if PFC Bucket Level is lower than PFCInteractiveBucketLowPercentage * InteractiveBucketMaxPCU the Bucket Congestion is finished. per_130. per_140. per_60. per_80 per_60 PFCIBMAPER=per_100. BSC criteria is BmaxPFC=PFCIBMAPER *Fn*(1sec+TF1)*Rgua. per_70. per_50.

object: PTPPKF range: 0. per_70. this parameter corresponds to the 3GPP parameter PAN_DEC and defines the stepsize to decrease counter N3102 in case T3182 expires without having received a PACKET UPLINK ACK/NACK message from the network. per_140. per_60.PFCSBHIPER=per_70. this parameter assignes the value of Streaming Bucket Max PCU as percentage of Bmax. per_160. per_130. per_180. per_20. per_60. per_170. object: range: PTPPKF per_100. per_150.060 Packet number decrement.. per_80. PFCSBMAPER=per_100. FALSE FALSE PFC streaming rate max used. per_180. per_90. per_140. if PFC Bucket Level is greater than PFCStreamingBucketHighPercentage * StreamingBucketMaxPCU the Bucket Congestion is started. per_110. per_170. per_30. per_40. per_170. per_150. per_130. PFCSRPER=per_100. per_20. per_50. per_40. per_90. Rmax is used for Bmax and R computation. per_50. per_30. per_190. per_140. PKTNDEC=2.. per_180. per_70.10 default: 1 Reference: Packet measurement report counter. this parameter reduces the value of Bmax automatically computed by the BSC.pfc guaranteed flow rate out of the buffer in the PCU. 271 . per_120. default: PFCSRMAXU=FALSE. if PFC Bucket Level is lower than PFCStreamingBucketHighPercentage * StreamingBucketMaxPCU PFCSBLPER=per_60. per_160. pfc) and Rgua. object: range: default: PTPPKF per_50. per_20. object: range: PTPPKF per_10. per_80. PFC streaming bucket low percentage. per_120. if this parameter is TRUE. object: range: PTPPKF per_10.7 2 3GPP 44. per_60. per_190. object: range: default: Reference: PTPPKF 0. per_50. per_200 per_200 PFC streaming bucket max PCU percentage. per_60. per_100. otherwise RGUA is used. per_70. per_100. per_110. per_130. BSC criteria is maxPFC=PFCSBMAPER *Fn*(1sec+TF1)*Rgua. per_40. per_200 per_100 PFC streaming rate percentage default: PKTMEASREPCNT=1. default: PFCSBMAPPER=per_200. per_80 per_60 the Bucket Congestion is stopped. object: range: default: PTPPKF per_10. object: range: default: PTPPKF TRUE. this parameter indicates the number of consecutive serving cell’s BCCH carrier measurements under threshold NCC1TH required to order a cell change. per_110. per_150. per_190. per_160. per_70. Refer also to parameters PKTNINC and PKTNMA. per_120. per_200 per_100 PFC streaming bucket max percentage. per_90 per_70 PFC streaming bucket high percentage. per_30. per_80.

060 PKTNMA=4.008 GSM 04.. Maximum packet number. It is broadcast within the PACKET SYSTEM INFO TYPE 1 on the PBCCH and the stepsize is 2 dBm. object: range: default: Reference: PTPPKF TRUE. .7 4 3GPP 44. cells or frequencies with other radio access technologies may also be included in the GPRS 3G Cell Reselection list to be monitored. object: range: default: Reference: PTPPKF 0.. N3102 cannot exceed the value set by PKTNMA. This list may be modified by PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER messages sent via the PACCH. object: range: default: Reference: PTPPKF 0. the mobile station shall perform an abnormal release with cell reselection.60 Packet number increment. this parameter corresponds to the 3GPP parameter PAN_MAX and defines the maximum value for the counter N3102 used on MS side.008 3GPP 44. In case N3102 reaches the value 0 or below (see PKNDEC and PKNINC). . this parameter This parameter corresponds to the 3GPP parameter PAN_INC and defines the stepsize to increase counter N3102 in case a PACKET UPLINK ACK/NACK message was correctly received by the MS.The value NEVER means the Mobile shall not consider 3G neighbours for reporting at all. Qsearch_P defines a threshold and also indicates whether these measurements shall be performed when RLA_P (RLA_P = receive level average) of the serving cell is below or above the threshold. relative to the output power used on the BCCH. Its value is broadcast on the PBCCH within the PACKET SYSTEM INFORMATION TYPE 3 message. QSRHPRI=NEVER. this parameter corresponds to the 3GPP parameter Pb and indicates the power reduction value used by the BTS on PBCCH blocks. FALSE TRUE 3GPP 44.. For a multi-RAT MS. Refer also to parameters PKTNDEC and PKTNMA. the neighbour cell shall be considered for reporting.The value ALWAYS means the Mobile shall always consider 3G neighbours for reporting. . the neighbour cell shall be considered for reporting. object: range: PTPPKF UMDB98 UMDB94 UMDB90 UMDB86 UMDB82 UMDB78 UMDB74 ALWAYS OMDB78 OMDB74 OMDB70 OMDB66 OMDB62 OMDB58 NEVER 3GPP 45. The parameter values have to be considered as follows: .The values OMDBxx (=over minus xxdB) define the threshold as follows: When the level of the neighbour cell has exceeded the “xx dB” threshold value. If RAARET=TRUE random access retry to other cell is allowed.060 PRPBCCH=0.The values UMDBxx (=under minus xxdB) define the threshold as follows: When the level of the neighbour cell has dropped below the “xx dB” threshold value. The network controls the measurements for reselection of those cells by the parameter Qsearch_P broadcast on PBCCH.060 default: reference: RAARET=TRUE. N3102 is set to PKTNMA at each cell reselection of the MS. This parameter indicates and defines a threshold condition under which the Mobile shall monitor and report 3G neighbour cells. object: range: default: Reference: PTPPKF 0. this parameter corresponds to the 3GPP parameter Qserach_P which is sent to the MS/UE .15 0 3GPP 45. Power reduction on PBCCH. If RAARET=FALSE random access retry to another cell is not allowed.7 2 3GPP 44.in the PACKET MEASUREMENT ORDER messages and PACKET CELL CHANGE ORDER messages via the PACCH.060 272 .in the PACKET SYSTEM INFORMATION TYPE 3 messages via the PBCCH and . Q Search priority.PKTNINC=2. Random access retry. this parameter corresponds to the 3GPP parameter RANDOM_ACCESS_RETRY and determines whether random access retry is allowed or not.

7 RAENV=HIGHDIV. Coding scheme upgrades are also performed at lower BLER values compared to the LOWDIV case. MS1 with Prio 1. LOWDIV HIGHDIV RARESH=2..008 Routing area code. indoor cells. object: unit: range: PTPPKF 2dB 0.RACODE=10. The DL precedence is assigned during the PDP context activation as part of the QOS negotiations and included in each DL-UNITDATA PDU. Routing area reselect hysteresis. the default is 4. Scheduling weight of priority 1. Due to the fact that the RACODE can be smaller than LA and its numbering is not unique in the network but it’s unique in the LA. It is an indicator of user mobility. object: range: default: PTPPKF HIGHDIV. object: range: PTPPKF 0. In case of one-phase access. Two values are possible: . this attribute represents the identification of the RA to which this cell belongs. This parameter determines which decision threshold table is applied for the Link Adaptation (LA) feature if EDGE is used. MS2 with Prio 4 If the mobiles use each 4 timeslots and the same coding scheme. The value is applied in both GMM standby and ready state of the mobile. Example: 2 MS sharing 4 timeslots. this parameter specifies the radio environment in the cell. coding scheme downgrades are started already at lower BLER values compared to the LOWDIV case (means earlier). because MSs have a speed higher than 50 km/h. In case of HIGHDIV. because the cell is characterized by low user mobility (pico cells. the throughput of a DL Transfer will be split according to: MS1: 8/9 * ThroughputMAX MS2: 1/9 * ThroughputMAX 273 . object: PTPPKF range: 0. this parameter is used to choose the right RA when the mobile is listening to different LA containing routing area with the same code.LOWDIV (lowDiversity): this value means that for an MS radio conditions can change slowly. For this purpose the system internally maps two of the available QOS parameters on the internal scheduling priority: DL Precedence UL Radio Priority Internal Priority Weight (default) SCHWEIPRI1=8.. the relative importance of each MS (TBF) compared to another one can be influenced.16 default: 8 Reference: 1 2 3 1 2 3 4 1 2 3 4 8 4 2 1 The UL radio priority is present in the PACKET RESOURCE REQUEST (PRR) message in case of a two-phase access. This applies some safety margin in case of HIGHDIV environment with its fast changing radio conditions..7 0=0dB. this parameter corresponds to the 3GPP parameter RA_RESELECT_HYSTERESIS and specifies the additional hysteresis (in steps of 2dB) to be subtracted from C32 of an adjacent cell belonging to a different routing area than the serving cell. this attribute is used by the mobile to identify the specific routing area. If more than one MS is allocated on a PDCH (vertical allocation). The RA colour for the neighbour LA must be set different by network planning.HIGHDIV (highDiversity): this value means that for a MS radio conditions can change fast. this parameter indicates the scheduling weight associated to scheduling priorities 1. object: range: PTPPKF 0. 7=14dB default: 2 Reference: 3GPP 45.255 RACOL=7.. A routing area may comprise at minimum a single cell and as maximum a complete LAC area. Routing area colour. or MSs have a speed lower than 50 km/h). Radio environment. .

. object: PTPPKF unit: 1s range: 10. the system uses the previously applied BLER and coding scheme info during the resource allocation process. to obtain the real value broadcast in (P)SI 1/13. If a new TBF is setup towards this TLLI within STGTTLLIINF time.16 default: 4 Reference: Scheduling weight of priority 2. STGTTLLIINF=10.. Please refer to SCHWEIPRI1 for further details. this parameter indicates the time (in seconds) for which the BSC stores the information about the last used coding scheme and BLER of a certain TLLI (=mobile) after it terminated its last TBF (UL or DL). Please refer to SCHWEIPRI1 for further details.0! 274 . SPFIWEI=16. this parameter indicates the scheduling weight associated to scheduling priorities 4. STREAMWEI=32. object: range: default: PTPPKF 1. the respective default values are considered (INIBLER. this parameter represents the weight for streaming. this parameter represents the weight for predefined PFI signaling. this parameter represents the weight for the predefined PFI SMS.. object: PTPPKF range: 0. object: range: default: PTPPKF 1.7 2 3GPP 44.. Please refer to SCHWEIPRI1 for further details. Its value plus one must be multiplied by 500 msec.16 default: 2 Reference: Scheduling weight of priority 3.060 Storage time of TLLI info. Default value changed in BR8...SCHWEIPRI2=4. is a timer used on the mobile side.smsSDUSize range: pfiWeight: 1..32 32 Streaming weight. this parameter indicates the scheduling weight associated to scheduling priorities 3.. etc.. It defines when the MS stops waiting for a PACKET UPLINK ASSIGNMENT message after it had asked for new uplink resources (via PRR.1560 (bytes) default: pfiWeight: 1 smsSDUSize: 160 bytes PFI SMS info. INIMCSDL. If STGTTLLIINF has expired. SCHWEIPRI3=2. object: range: default: Reference: PTPPKF 0. SMSINFO=1-160.32 smsSDUSize: 160. this parameter indicates the scheduling weight associated to scheduling priorities 2. It consists of the two fields: pfiWeight and smsSDUsize.. object: PTPPKF format: pfiWeight .16 default: 1 Reference: Scheduling weight of priority 4. object: PTPPKF range: 0.32 16 Signaling PFI weight. T3168.. SCHWEIPRI4=1.). (E)PDAN or PCA).90 default: 10 Reference: T3168=2. object: PTPPKF range: 0..

008 T average time.T3192=0. when this mobile has reselected a GSM/GPRS cell. this parameter is relevant for the feature 'Network Controlled Cell Reselection from GSM/GPRS to UMTS due to UMTS Sufficient Coverage' (see parameter EUSCNCRESEL in command SET BSC [BASICS]) and defines the timer started from BSC when it has received a PACKET CELL CHANGE FAILURE message containing an UMTS cell description from a MS/UE via the PACCH. It defines a level offset by which the RLA_P value of an UTRAN TDD neighbour cell must exceed the RLA_P of the serving GSM cell before the UTRAN TDD neighbour cell is considered for cell reselection from GSM to UTRAN.7 0 3GPP 44. DB00. object: range: default: Reference: PTPPKF 0.. default: DB00 reference: 3GPP 45.25 5 3GPP 45. this UMTS neighbour cell is excluded from the UMTS Target Cell List. Timer failures neighbour cell UMTS. DB20. TDD GPRS Q offset..100 12 275 . this parameter corresponds to the 3GPP parameter T_AVG_W and indicates the signal strength filter period for power control in packet idle mode. TBNCU=5. NC GSM/GPRS to UMTS cell reselection shall be inhibited for this MS/UE. When T3192 expires. TDDGQO =DB00. MDB16. this timer is used on the MS side when the mobile station has received all of the RLC/MAC data blocks of a TBF. MDB28. MDB12.060 TFAILNCU=5.xxdB (e.) and begin to monitor its paging channel. For details about the GPRS cell reselection algorithm from GSM to UTRAN please refer to the description of parameter GFDDQMI (see below). Until expiry of this timer. object: unit: range: default: PTPPKF 1s 1. MDB04. MDB24. this parameter corresponds to the 3GPP parameter TDD_GPRS_Qoffset which is broadcast on the PBCCH in the PACKET SYSTEM INFORMATION TYPE 3quater and is related multiRAT mobiles.008 T average weight. etc. DB24. DB28.g. MDB20. The timer is broadcast withing (P)SI 1/13 and coded as follows: 0 500 ms 1 1000 ms 2 1500 ms 3 0 ms 4 80 ms 5 120 ms 6 160 ms 7 200 ms Please also refer to T3193 (object PCU). this parameter defines the timer which is started relatively to a MS/UE. The parameter values express a value in dB MDBxx = . object: range: default: Reference: PTPPKF 0. TAVGT=5. the mobile shall release the resources associated with the TBF (TFI. MDB20 = -20dB) DBxx = xxdB (e. TAVGW=15..g. Until its expiry.100 5 Timer back neighbour cell UMTS. DB04. DB12. object: range: PTPPKF ALWAYS. so with this setting a 3G Mobile will always change to the 3G network if any acceptable 3G cell is available.008 3GPP 44.. object: range: default: Reference: PTPPKF 0. this parameter corresponds to the 3GPP parameter T_AVG_T and indicates the signal strength filter period for power control in packet transfer mode.25 15 3GPP 45.... MDB08. DB20 = 20dB) The value ALWAYS indicates an infinite negative (-∞ dB) offset. DB08. object: range: default: PTPPKF 1. DB16. it is used by the MS/UE for the cell re-selection algorithm from GSM to UTRAN.060 T3192.

These mobiles receive a PACKET CELL CHANGE ORDER towards an adjacent target cell. that is. To handle this wrong mobile behaviour. then this cell can be reused by the BSC for the reselection of the 276 ..The CR covers also an anomalous behavior by a NOKIA MS: after a failed cell reselection on a target cell. .TRESEL=0. However. If the MS has performed an abnormal release with cell reselection towards a new cell (see parameter RAARET).The Maximum number of stored cells (to which a NCCR happened) is fixed to 4. but instead of sending a PACKET CELL CHANGE FAILURE. it sends a PACKET RESOURCE REQUEST to open a new TBF. The PACKET CELL CHANGE FAILURE is sent only after the PACKET UPLINK ASSIGNMENT sent by the BSC to open the new TBF. The field is coded according to the following table: 000 5 seconds 100 30 seconds 001 10 seconds 101 60 seconds 010 15 seconds 110 120 seconds 011 20 seconds 111 300 seconds This parameter was originally supposed to define the minimum time between two consecutive NCCR procedures of an MS towards the same adjacent cell (Traffic packet switched control timer). the BSC des not to order the mobile to move again into this adjacent target cell. in spite of good radio link scenario. object: PTPPKF unit: 1s range: 1. otherwise BSC may not track mobile in its cell change. .If a cell is used by the BSC for the reselection of a given MS at time T=x..which distinguish between local / foreign TLLI). Restrictions: . This action trust in the fact that mobile’s TLLI used in the old serving cell and mobile’s TLLI used in the adjacent target cell may differ only for one bit (bit 30th. NOKIA) ‘ping-pong’ behaviour was experienced.100 default: 5 Reference: Timer for cell reselection. Remarks: . This parameter corresponds to the 3GPP parameter T_RESEL which is broadcast within the PACKET SYSTEM INFORMATION TYPE 3 message on the PBCCH.008 TRFPSCTRLT =5.0) which deals with a particular mobile phone problem. Thefore the rule STGTTLLIINF >=TRFPSCTRL must be applied (settings violating this ruke are prevented by a database command check). the MS shall not reselect back to the original cell for T_RESEL seconds if another suitable cell is available. The parameter can thus be described as Time between two consecutive NCCR procedures on the same MS towards the same adjacent cell: During Network Controlled Cell Reselection with particular mobile types (Ericsson. it is not possible to have different timers for e.7 0 3GPP 45. object: range: default: Reference: PTPPKF 0. After that it goes back autonomously to the ‘old’ cell without transmitting PACKET CELL CHANGE FAILURE.g PTP1->PTP2 and PTP1->PTP3 adjacencies. the parameter was finally not implemented as intended but was ‘abused’ for a different purpose in the scope of CR1850 (implemented in BR7. After having accessed this target cell. the MS reselects the serving cell by accessing with a single block procedure. This procedure requires also that BSC stores information related to the mobile after the end of each TBF at least for the time STGTTLLIINF (storage TLLI Info).Timer TRFPSCTRL is referred to the serving PTPPKF and is applied to all the adjacent cell relations belonging to that PTPPKF. mobile performs location area update but it does not perform routing area update. the existing (but not used) parameter TRFPSCTRL is emplyed: as long as TRFPSCTRL runs.

after a failed network controlled cell reselection. only after timer TRFPSCTRL is expired. Creating the LPDLR links: CREATE LPDLR This command was deleted in BR6. but it comes back by T< 15 sec starting from PACKET CELL CHANGE ORDER message.If a MS.If a MS sends packet cell change failure message after contention resolution the BSC will not chose a second target cell until it will not receive a packet measurement report message. . 277 .0 on the LPDLR is automatically created by the command CREATE TRX. .same MS only after time T’= x + TRFPSCTRL that is.0! From BR6. then the BSC will not choose a second target cell until it will not receive a packet measurement report message. does not send any packet PACKET CELL CHANGE FAILURE on the old serving cell. the physical assignment of the created LPDLR is determined by the parameter LPDLMN (in command CREATE TRX).

This IE ‘Mobile Allocation’ is a bit map in which e. Mobile allocation list. In this case the IE also contains the HSN together with the MAIO.e.02 GSM 04. DMA is not used at all.g.0 the definition of frequency hopping systems can be done in two different ways: a) the frequency hopping system is defined per BTS (per cell) in the FHSY object which is subordinate to the affected BTS (as done in releases before BR8. In any case. which is contained in the ASSIGNMENT COMMAND and in the HANDOVER COMMAND. starting with BR8. > CREATE FHSY: NAME= BTSM:0/BTS:0/FHSY:0. If frequency hopping is enabled the parameter H is set to 1.0.. Hopping sequence number. .Static MAIO Allocation (see above).63 Reference: 3GPP 45. Starting from BR8. determines the hopping sequence’s respective algorithm. the allocation of a FHSY and MAIO can alternatively be done in the TRX object (see command CREATE TRX).Dynamic MAIO Allocation (see above). The below listed command CREATE FHSY is thus only relevant for variant (a).. object: FHSY range: 0.. this parameter defines is a list of those cell allocation frequencies used in the hopping sequence. i. Variant b) can be used for .. the DBAEM places the command CREATE FHSY before the CREATE TRX commands (in releases up to BR7. which means that the BTSM-specifically defined hopping system (CFHSY) is allocated to the TRX object toghether with a fixed MAIO value (see command CREATE TRX) which determines the position of the channels subordinate to the TRX in the hopping sequence when DMA is not enabled (see parameter ENDMA in commands CREATE CBTS and CREATE BTS [BASICS]). The value ‘0’ means cyclic hopping. b) the frequency hopping system is defined per BTSM (per site) in the CFHSY object (see command CREATE CFHSY) which is subordinate to the CBTS object. the defined MAIO is no longer relevant as for the channels.0).08 Object path name.0.08 278 . for every frequency contained in the 'cell allocation frequency list' an own bit position is provided. This parameter is sent in the main DCCH in the IE ‘Channel Description’ contained in the ASSIGNMENT COMMAND and in the HANDOVER COMMAND if it was assigned to the used channel.008 GSM 04. which means that the BTSMspecifically defined hopping system (CFHSY) is allocated to the TRX object toghether with a fixed MAIO value (see command CREATE TRX) which determines the position of the channels subordinate to the TRX in the applied hopping sequence when Dynamic MAIO Allocation (DMA) is not used by the service layer assigned to that TRX.0 it was placed before the CREATE CHAN commands). which means that the BTS-specifically defined hopping system (FHSY) is allocated to the CHAN object toghether with a fixed MAIO value (see command CREATE CHAN for TCH and SDCCH) which determines the position of that particular channel in the applied hopping sequence.. This parameter is sent in the main DCCH in the IE ‘Mobile Allocation’. The 'cell allocation frequency list' is derived from the set of frequencies defined by the reference 'Cell Channel Description' IE (see also parameter CALL in CREATE BTS MOBALLOC=CALLF01& CALLF02&.1023 (each field) Reference: GSM 05. HSN=10. object: FHSY range: 0. Variant a) can be used for Static MAIO Allocation (SMA) only.Creating the cell-specific Frequency Hopping systems for static MAIO Allocation (SMA): < Starting from BR8. When DMA is enabled. MAIOs are dynamically assigned by a special algorithm.

except that ARFCN 0. the value of TRXFREQ must be BCCHFREQ. In the cell allocation frequency list the absolute RF channel numbers are placed in increasing order of ARFCN. If the bit position representing a frequency is ‘1’ then the associated frequency is contained in the mobile allocation. if included in the set..If the FHSYID is created for a concentric cell (see CREATE BTS [BASICS]:CONCELL=TRUE) then hopping is only allowed within the complete and within the inner area.[BASICS]). If the TRX represents the BCCH carrier.From BR6.0 on the radio frequencies assigned to the FHSY are no longer represented by their absolute radio frequency number (ARFCN) but by their relative number CALLFxx which was assigned to the frequencies during creation of the BTS cell allocation (please refer to the parameters CALLF01.) 279 . . is put in the last position in the list.CALLF63 and BCCHFREQ in the command CREATE BTS [BASICS]). This means that two FHSYIDs have to be defined: one for the complete area (MOBALLOC may only consist of TRX frequencies of the complete area) and one for the inner area (MOBALLOC may only consist of TRX frequencies of the complete area. Notes: .

20 LAYERID=LY_00. object: range: TRX 0. Starting from BR8. signaling transaction or call which invloves any radio channel (CHAN object) subordinate to this TRX. is signaled via this LPDLR. especially in case of synthesizer frequency hopping. <NULL> default: <NULL> Reference: GSM 05.command CREATE FHSY .commands CREATE CBTS and CREATE CFHSY Service Layer ID. object: range: TRX CFHSY_0. no matter whether it is . For further details about frequency hopping and the creation of hopping systems for Static MAIO Allocation (SMA) and Dynamic MAIO Allocation. any cell access. this parameter defines the "primary" LPDLM object position (PCMB number and TS LAPD number) of the LPDLR links.g. the equivalent parameters in the CHAN object must be set to the <NULL> value in this case.parameters FHSYID and MAIO in command CREATE CHAN .Creating the TRXs: CREATE TRX: NAME= BTSM:0/BTS:0/TRX:0..an SDCCH transaction (e.08 GSM 12. When these parameters in the TRX object are used this means that for all CHAN objects subordinate to the TRX the same hopping law (with Mobile Allocation (MA) and Hopping Sequence Number (HSN) as defined in the assigned FHSY) is used ..7 280 . The distinction between the LPDLM messages (O&M messages between BSC and BTSM) and the LPDLR messages (TRX-specific radio signaling communication GSUP FHSYID=<NULL>. please refer to the command SET BTS [SERVICE]. In other words. see command CREATE CHAN) are also available in the TRX object. LPDLM number. which is used for the radio signaling (i. If the hopping parameters FHSYID and MAIO of the TRX object are filled.e.a transaction signaled via an SACCH or FACCH (TCH assignment.parameters HOPP and HOPMODE in command SET BTS [OPTIONS]..0 the parameters FHSYID and MAIO (that in releases up to BR7. cancelled in BR8.CFHSY_1. by the assignment of an already existing frequency hopping system (as defined by a FHSY or CFHSY object) this parameter determines the frequency hopping law that is applied to all CHAN objects that are subrodinate to the TRX.0 Frequency hopping system identifier. For further details. Object path name.FHSY_10. Background: Every TRX has an associated LPDLR channel. If the hopping system is to be defined by the CFHSY object (this is mandatory in case of Dynamic MAIO Allocation (DMA).02 GSM 04. this parameter is used for the feature ‘Service Dependent Channel Allocation’ and defines the service layer this TRX belongs to. FHSY_0. . the parameters MAIO and FHSYID must be defined in the TRX object. handover. Location Update. object: range: default: TRX LY_00.which is the usual case. random access via the RACH (CHANNEL REQUIRED sent by the BTS)..0 had been available in the CHAN object only. SMS in idle mode. please refer to the following commands and parameter descriptions .a BCCH procedure (e.) or .) Physically the LPDLR signalling messages are sent within the same Abis timeslot(s) which is (are) assigned to an existing LPDLM object(s) for the responsible BTSM.LY11 LY_00 LPDLMN=0. signalling for call processing) of this particular TRX. SMS in busy mode etc. IMSI detach etc. paging via the PCH (PAGING COMMANDs sent the BSC) or an Immediate Assignment procedure via the AGCH (IMMEDIATE ASSIGNMENT sent by the BSC)) .g.

. even if one of the PCMB connections has failed. Thus the LPDLMN definition defines the standard load sharing distribution for radio signalling communication among the available physical Abis timeslots that were configured as LPDLMs.02 GSM 04. only this LPDLM number can be selected for LPDLMN. object: range: default: Reference: TRX 0.MAIO=<NULL>. If the hopping system is to be defined by the CFHSY object (this is mandatory in case of Dynamic MAIO Allocation (DMA).63. the radio signalling messages of the affected TRX are automatically transmitted via one of the remaing LPDLMs in order to guarantee the availability of all TRXs of the BTSM. The parameter LPDLMN identifies the LPDLM link (and thus the physical Abis timeslot) via which the LPDLR signalling of the TRX shall be performed. For further details about frequency hopping and the creation of hopping systems for Static MAIO Allocation (SMA) and Dynamic MAIO Allocation. see command CREATE CHAN) are also available in the TRX object.parameters FHSYID and MAIO in command CREATE CHAN . especially in case of synthesizer frequency hopping.g.0 the parameters FHSYID and MAIO (that in releases up to BR7. If.commands CREATE CBTS and CREATE CFHSY 281 . due to failure of the superordinate PCMB link). via which the LPDLR signalling of a particular TRX shall be performed by default. If an LPDLM fails (e. which might lead to high LAPD transmission.0 had been available in the CHAN object only. If only one LPDLM is created for a particular BTSM. <NULL> <NULL> GSM 05.which is the usual case. the radio signalling messages related to a particular TRX are always signaled with SAPI=0 and the TEI no. of course. Starting from BR8.command CREATE FHSY . The restrictions to be considered in this case is the fact that the possible traffic volume will be limited due to the unavailability of a part of the Abis TCH resources and the limitation of the LAPD throughput capacity. more than one LPDLM is created for a particular BTSM.08 between BSC and BTS/TRX) is made on the basis of the LAPD addressing identities SAPI (Service Access Point Identifier) and TEI (Terminal Endpoint Identifier) in the layer-2 header of the LAPD messages: While LPDLM messages are always signaled with SAPI=62 and the TEI of the BTSM (as defined in the parameter TEI in command CREATE BTSM). however. this parameter determines the position of all channels subordinate to this TRXwithin the frequency hopping algorithm defined by the parameter FHSYID (see above). If the hopping parameters FHSYID and MAIO of the TRX object are filled the equivalent parameters in the CHAN object must be set to the <NULL> value in this case. Please see also the parameters TEI (in command CREATE BTSM). Mobile allocation index offset. which is automatically assigned to the TRX during the BTSE alignment (the TEI assignment of a TRX can be interrogated by the command GET TRX). please refer to the following commands and parameter descriptions .parameters HOPP and HOPMODE in command SET BTS [OPTIONS] . LPDLMN determines the LPDLM. the parameters MAIO and FHSYID must be defined in the TRX object. When these parameters in the TRX object are used this means that for all CHAN objects subordinate to the TRX the same hopping law (with Mobile Allocation (MA) and Hopping Sequence Number (HSN) as defined in the assigned FHSY) is used . ABISCH (in command CREATE LPDLM) and the explanations provided for the command CREATE SUBTSLB.

object: unit: range: default: Reference: TRX 2dB 0. it has to be considered that the enabling of the Radio Measurements on the Abis interface cause an additional load on the LPDLR links: the lower the value for RADIOMG.008 RADIOMG=254.MOEC=TRUE. However. Note for concentric cells: Since in concentric cells (see parameter CONCELL in command CREATE BTS [BASICS]) this parameter determines the different ranges of inner and complete area TRXs it must be set in accordance with the setting of the parameter TRXAREA (see below)! If a cell is configured for two different frequency bands (dual band concentric cells. Rules: For configuration rules concerning concentric cells and dualband concentric cells please refer to the description of parameter HORXLVDLO (see command SET HAND [BASICS]). 'Emergency configuration' is entered in case of a failure of the external BTSE power supply (alarm 'ACDC MAINS BREAKDOWN') or if the shelter temperature exceeds the allowed threshold (alarm 'SHELTER TEMPERATURE OUT OF TOLERANCE'). object: unit: range: default: TRX 1 SACCH multiframe 1-254 254 Member of emergency configuration. specifies the number of 2-dB-steps the Tx power should be reduced from the maximum transmit power. the higher the signalling load on the LPDLRs. Power reduction. Setting MOEC to TRUE for a TRX means that the HW associated to this TRX will be powered if emergency configuration is entered. FALSE TRUE PWRRED=6. this parameter is only relevant if the parameter RADIOMR is set to ON (see below) and specifies the granularity periods for retrieval of the measurement reports which are to be sent on the Abis interface in case they are enabled.6 (0dB-12dB) 6 3GPP 45. or dual band standard cells. object: range: default: TRX TRUE. Radio measurement granularity for measurements on Abis.. refer to parameters CELLTYP and CONCELL. Since the sending power determines the actual cell size the PWRRED parameter is used to adjust the sending power according to the desired transmission range. considering the differences in the output power of the TRX HW (CU/PA) for different frequency bands and the propagation attenuation of the different used frequency. see above) the use of the PWRRED might be necessary to control the coverage of the TRXs. If the Abis has to be traced for radio diagnostic of handover performance diagnostic reasons it is recommended to set the radio measurement granularity to ‚1’ because only in this case all measurement reports from the MS and the BTS will be transmitted on the Abis. this parameter determines whether a TRX belongs to the 'Emergency Configuration' or not (see also parameters EMT1 and EMT2 in the command CREATE BTSM). Its purpose is to keep only the most important BTSE units and TRXs alive and thus to save power as long as the BTSE is powered by the backup battery. 282 .

this parameter specifies whether a TRX belongs to a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) and. In some cases. object: range: default: TRX NONE. i.. CALLF01. SDCCH) must belong to the complete area (see command CREATE CHAN). whether it serves the inner or the complete area.. specifies whether radio measurement report transmission via the Abis interface is enabled. The MEASUREMENT RESULTs contain the ‘confirmed’ TA value of the previous measurement period. Only if TRXMD is set to EDGE for the BCCH TRX. if the TRX-HW which is associated to the created TRX object an EDGE CU (ECU). From BR6.RADIOMR=OFF. TRX area. assigns a radio frequency to a transceiver. see next command) to TRUE. Only in this case the feature should be activated since it results in additional load on the LPDLR links. USF granularity. this parameter indicates the capability of the TRX to support EDGE.0 on the radio frequency assigned to the TRX is no longer represented by its absolute radio frequency number (ARFCN) but by its relative number CALLFxx which was assigned to the frequency during creation of the BTS cell allocation (please refer to the parameters CALLF01. This principle also goes for the TRACE MEASUREMENT RESULTs that are sent on the Abis when CTR (see command CREATE CTRSCHED) or IMSI Tracing (see command CREATE TRACE) is enabled. If the TRX represents the BCCH carrier. Since in the SBS the preevaluation of measurement reports for handover decisions is done in the BTS. it is useful to monitor the measurement reports on the Abis interface for test purposes. CCALLF63 Reference: GSM 04. Note: The MEASUREMENT RESULT messages on the Abis also contain a timing advance (TA) value. Thie parameter can only be set to the value EDGE. CALLF63 CCALLF01. this parameter defines if USF granularity 1 is supported or not. object: range: default: TRX ENABLED. EDGE GSM TRXAREA=NONE. the SCA measurements (see command CREATE SCA) count the ‘TA order’ events. The timing advance value is determined by the BTS on the basis of the delay (within the guard period) of the bursts received from the MS and this value is used to instruct the MS to transmit its next bursts with a specific ‘timing advance’ in order to ensure that the BTS receives the burst within the guard period. OFF OFF TRXMD=GSM. USFGRAN=DISABLED. object: range: default: TRX ON.08 Radio measurement reports. however. The frequency of the measurement reports to be sent via the Abis can be controlled by the following parameter RADIOMG (see below). the value of TRXFREQ must be BCCHFREQ. normally no measurement reports are sent from BTS to BSC. object: range: default: Reference: TRX GSM.08 GSM 05. DISABLED DISABLED 283 . TRX frequency. it is possible to set the parameter EBCCHTRX (command SET PTPPKF. This instruction from BTS to MS is called ‘timing advance order’ and is acknowledged by the MS in the ‘TA confirm’.e. INNER..CALLF63 and BCCHFREQ in the command CREATE BTS [BASICS]). with the ‘TA confirm’ the MS confirms that it has transmitted its bursts in correspondence with the previous ‘TA order’. TRX Mode. In contrast.the BCCH frequency and all other frequencies with control channels (CCCH. object: range: TRX BCCHFREQ. if yes. Notes: . COMPLETE NONE TRXFREQ=CALLF01.this parameter must be set in conjunction with a sensible setting of PWRRED (see above)! .

2. For further information about MSLS please refer to command CREATE CBTS. The setting TRUE is only possible if the BCCH TRX is epuipped with EDGE CU (ECU) at least for the BCCH TRX. FALSE default: FALSE Reference: recommended value: TRUE (if BCCH TRX is equipped with ECU) Object path name. there is no problem as the CU HW has enough reserves to support the 8PSK power requirement (in this case the deviations remain within the tolerances specified by the 3GPP standard). If EGPRS with 8PSK coding schemes is allowed on the BCCH TRX. 3. In this case the operator has 3 main possibilities: 1. however. however.0. the BTS correctly equalizes the output power levels on both 8PSK and GMSK timeslots. be a problem in cells with a small number of TRXs (e. to a falsification of the BCCH transmit power. 284 .g. with PWRRED applied. i. this parameter indicates if EDGE 8PSK modulation is supported on the BCCH TRX. this will lead. Thus.e. the measured power will be lower than it really is (on the GMSK timeslots). EBCCHTRX=TRUE. This may. .g. The operator can change the PWRRED values. will reduce the coverage area and may contradict to the original coverage planning concept. as in case of automatic BCCH reconfiguration. If the operator does not want to change the cell coverage planning (which was based on PWRRED=0) he may accept the falsification of the BCCH level and adapt the relevant ADJC handover parameters accordingly (e. For this reason DBAEM places the command CREATE PTPPKF again after the creation commands for the TRXs with additional parameters. Attention: . > SET PTPPKF: NAME= BTSM:0/BTS:0/PTPPKF:0. the maximum power values that can be provided on 8PSK timeslots in the downlink will always be by 2-3dB smaller than the maximum power values on GMSK timeslots. 2 TRX only). If no PWRRED is applied. If the CU is operated with static power reduction (at least PWRRED=1(=2dB).Enabling GPRS and EDGE in a cell: < The specific parameters related to the enabling of GPRS and EDGE can only be entered if TRX objects were created before with the appropriate attributes. range for PTPPKF: 0. see corresponding parameters in command CREATE ADJC) in the surrounding cells. The operator can make use of the feature Multi Service Layer Support (MSLS) to allocate EGPRS call only on non-BCCH TRXs with suitable quality figures. In this way the falsification of the BCCH signal is avoided and no further parameter adjustment is necessary. the CU cannot generate the same maximum output power for 8PSK like for GMSK. EGPRS 8PSK on BCCH TRX. the BCCH TRX might be served by a different TRX-HW branch. reduce RXLEVMIN and HOM by 1dB.The operator must consider that. This. see TRX object).. due to the higher power density of 8PSK modulated signals. as all BCCH TRX timeslots must transmit with equal maximum power to guarantee a stable DL level reference for neighbour cell measurements. This may be a problem if EGPRS with 8PSK coding schemes is used on the BCCH TRX and PWRRED=0. better PWRRED=2.Also the other TRXs of the same BTSE should be equipped with ECU in this case. object: PTPPKF range: TRUE. depending on the number of timeslots busy with 8PSK coding schemes.

EEDGE=TRUE. FALSE default: FALSE Reference: recommended value: TRUE (if at least one TRX is equipped with ECU) Enable EDGE. if at least one of the TRXs in the cell support EDGE (see parameter TRXMD in command CREATE TRX). As this paramter can only be set to TRUE. this parameter parameter allows to enable/disable GPRS on a per cell basis. object: PTPPKF range: TRUE. 285 . EGPRS=TRUE. object: PTPPKF range: TRUE. if at least one of the TRXs in the cell supports GPRS (this is the case if the TRX is defined as belonging to a service layer which is included in the SLL for GPRS services . this parameter parameter allows to enable/disable EGPRS (EDGE GPRS) on a per cell basis.please see command SET BTS [SERVICE] for further explanations). FALSE default: FALSE Reference: recommended value: TRUE Enable GPRS. As this paramter can only be set to TRUE.

3) + SACCH/C4 (0.02 for details). CELLTYPE=EXTCELL (CREATE BTS [BASICS])) then all control channels must be set for 'extended mode'.02 GSM 04.A MBCCHC or a BCBCH can only be created if NBLKACGR ≤ 2 (see corresponding parameter in command SET BTS [CCCH]) .see GSM05.2. The info about the used control channel configuration is sent in the Parameter ‘CCCH_CONF’..If the cell type is extended cell (i. .Only one FCCH/SCH is allowed per cell . there are only 3 SDCCH available if BCBCH is selected.e.on timeslot 0 of C0! . Extended mode.3) + SACCH/C4 (0. NFRAMEPG and NBLKACGR .4 and 6 of C0.The CBCH replaces the 2nd SDCCH. Channel type.01 GSM 05. .CCCH) must belong to the complete area..). only one CBCH is allowed per cell.4. which is part of the IE ‘Control Channel description’ sent in the SYS_INFO3 on the BCCH.Creation of additional BCCH+CCCH (CHTYPE=CCCH) is possible but only on the timeslots 2. this parameter defines whether the channel is used in 'extended mode' for extended cells or not. object: range: default: CHAN TRUE.e.. If more than one BCCH is created for a cell the MSs observe the BCCH on timeslot 0 first and having detected that there are more than one (from the CCCH_CONF) . .In a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) all frequencies with common control channels (BCCH. object: range: CHAN see parameter explanations on the right Reference: GSM 05. Notes: ..Creating the BCCH for the cell: CREATE CHAN: NAME=BTSM:0/BTS:0/ TRX:0/CHAN:0. EXTMODE=FALSE.select one BCCH/CCCH timeslot for all their CCCH activities on the basis of their “CCCH_GROUP”.The radio timeslot of an 'extended' channel must have an even number (0. i.3) + CBCH Notes: .. CHTYPE=MAINBCCH. FALSE FALSE 286 .08 Object path name. possible values: a) normal broadcast control channel including frequency correction and synchronization cannel: MAINBCCH = FCCH + SCH + BCCH + CCCH* b) broadcast and common CCH only CCCH = BCCH + CCCH (CCCH = PCH + RACH + AGCH) c) Main BCCH with reduced CCCH capacity plus stand-alone dedicated CCH/4 MBCCHC = FCH + SCH + BCCH + CCCH* + SDCCH/C4 (0..3) d) MBCCHC plus SMS cell broadcast channel BCBCH = FCCH + SCH + BCCH + CCCH* + SDCCH/C4 (0. The CCCH_GROUP is calculated from the last three digits if the IMSI and the CCCH configuration (which is derived from the parameters CCCH_CONF. etc.

In a concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) all frequencies with SDCCHs must belong to the complete area. SACCH SDCCH = SDCCH/C8 (0. The TSC is part of the ‘Normal Bursts’ which are used for all channel types except RACH.20 Frequency hopping system identifier. possible values: a) pure stand-alone dedicated CCH/8 incl.63.The CBCH replaces the 2nd SDCCH.. object: range: CHAN see parameter explanations on the right Reference: GSM 05. see command CREATE BTS [BASICS]).7) b) SDCCH/8 plus SMS cell broadcast channel SCBCH = SDCCH/C8 (0. This is necessary for the correct selection and decoding of the BCCH bursts.An SDCCH/8 can also be created as follows: CHTYP=TCHSD. not used here since FHSYID=0. see CREATE BTS [BASICS] parameter BSIC) so that the MS can derive the TSC of the BCCH from the SCH. > CREATE CHAN: NAME=BTSM:0/BTS:0/ TRX:0/CHAN:1. Creating the SDCCHs for the cell: < Note: All the TRXs with channels of type SDCCH have to be included in a Layer associated at least to the Signalling SLL (see command SET BTS [SERVICE] for further explanations).08 GSM 12. especially if within a limited geographical area a frequency is used several times. SCH and FCCH. If no value is entered for the parameter TSC the BCC is automatically selected..7) + SACCH/C8 (0.FHSYID=0. . object: range: default: Reference: CHAN 0. object: range: default: CHAN 0. .7 BCC of BSIC (CREATE BTS [BASICS]) Reference: GSM 05.08 Object path name.An SCBCH can only be created if NBLKACGR > 0 (see corresponding parameter in command SET BTS [CCCH]) . otherwise these channels will never be used as singalling channel.. CHTYPE=SCBCH.. The TSC for the BCCH must correspond to the BCC (part of the BSIC sent on the SCH.In an extended cell (CELLTYPE=EXTCELL. . Channel type.01 GSM 05.02 GSM 04. MAIO=0. .02 GSM 04. <NULL> 0 GSM 05.. 287 .At least one SDCCH must be created on the BCCH TRX (due to the implementation of BCCH recovery) .7) + CBCH Notes: .7) + SACCH/C8 (0. i.2 and 3! .02 GSM 04.08 Mobile allocation index offset. there are only 7 SDCCH available. 0(=no hopping) is mandatory for the BCCH.FHSY_10.The SCBCH can only be created on the timeslots 0. <NULL> default: 0 = no hopping Reference: GSM 05.08 Training Sequence Code.The CBCH must be created on the BCCH TRX. only one CBCH is allowed per cell. (TSC=). object: range: CHAN FHYS_0. see below)..1.. all SDCCHs must be created as ‘double’ timeslots (EXTMODE=TRUE.02 GSM 04.CHPOOLTYP=TCHPOOL (see CREATE CHAN command for TCHSDs). this optional parameter specifies the Training Sequence Code of the radio channel.e.

if Dynamic MAIO Allocation (DMA. i. CCCH. hopping is not allowed for any CHAN object belonging to the BCCH TRX.in the CHAN object these parameters must be set to the <NULL> value in this case. .4.In concentric cells (CREATE BTS [BASICS]:CONCELL=TRUE) hopping is only allowed within the complete and within the inner area. etc. As the biggest percentage of all signalling activities in a cell are processed via the SDCCHs.e. Notes: . if the hopping system is defined as FHSY. Note: . .. i.. CBCH and SDCCH) must be configured as ‘double’ timeslots (EXTMODE=TRUE). object: range: CHAN FHSY_0. the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) . the BTS measures the interference considering all frequencies used in the hopping sequence assigned to the a TCH in the frequency hopping system! . Extended mode. Notes: .FHSY_10. FALSE FALSE FHSYID=FHSYID_2. this parameter defines whether the channel is used in 'extended mode' for extended cells or not. all other values ‘X’ must have been created for this cell (BTS) before by CREATE FHSY:NAME=bsc:n/bts:n/fhsyid:x. it is urgently recommended to configure multiple SDCCH channels on different TRXs. object: range: default: CHAN TRUE.02 GSM 04.e. .. 288 . i. although with a more even distribution of the signalling load over the TEIs this could be avoided. it is recommended. CELLTYPE=EXTCELL (CREATE BTS [BASICS])) then all control channels (BCCH. Otherwise the probability of the BTSE alarm ‘LAPD TRANSMIT QUEUE OVERFLOW’ will considerably increase.If synthesizer frequency hopping is used.08 GSM 12. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to. each TRX (TEI) has an own transmit queue. start position of the channel in the frequency hopping algorithm. If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA).20 MAIO=0. If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA). Mobile allocation index offset.The frequency hopping system can only be defined in the CHAN object.If Interference Classification of idle TCHs is enabled (see parameter INTCLASS in command SET BTS) while frequency hopping is active..).08 .EXTMODE=FALSE. to avoid an excessive concentration of the SDCCH signalling within one TRX (and thus one LPAD transmit queue).When an Abis interface is configured via satellite.The radio timeslot of an 'extended' channel must have an even number (0. <NULL> default: 0 = no hopping Reference: GSM 05. This has to be taken into account when the FHSYIDs are assigned to the CHAN objects.If the cell type is extended cell (i. Frequency hopping system identifier.02 GSM 04. . the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) . <NULL> 0 GSM 05. This is necessary because the Abis LAPD transmit queues in the BTS are managed per TRX(TEI).e.63. 0=no hopping. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to.The MAIO can only be defined in the CHAN object.2. to distribute multiple SDCCHs over different TRXs within the cell.in the CHAN object these parameters must be set to the <NULL> value in this case.e. if the hopping system is defined as FHSY. if Dynamic MAIO Allocation (DMA. object: range: default: Reference: CHAN 0.

A dual rate TCH can also be created as follows: CHTYP=TCHSD. The TSC is part of the ‘Normal Bursts’ which are used for all channel types except RACH. the HR portion implies HR and AMR HR. EFR and AMR FR. object: range: CHAN see parameter explanations on the right Reference: GSM 05. possible values for TCH creation: a) Full Rate channels TCHFULL = TCH/F + FACCH/F + SACCH/TF b) Dual rate (full and half) channels TCHF_HLF = TCH/H(0) + FACCH/H(0) + SACCH/H(0) + TCH/H(1) or TCH/F + FACCH/F + SACCH/TF Notes: . this parameter defines whether the channel is used in 'extended mode' for extended cells or not.If an extended cell is the target of an inter-cell HO the handover will always take place to a 'double' timeslot first as the BTS can only determine the actual MS-BTS distance when the first MS messages are received.2. .).CHPOOLTYP=TCHPOOL (see next CREATE CHAN command for TCH/SDs). Which speech version is used for TCH assignment depends on the MS capability and preference as well as on BSC database settings (see parameters EFRSUPP and HRSPEECH in command SET BSC [BASICS] and EHRACT in command CREATE BTS [BASICS]). . If the MS-BTS distance turns out to be small enough for a 'single' timeslot an intra-cell handover from far to near ('double-tosingle') is executed immediately (if enabled).If the cell type is extended cell (CREATE BTS [BASICS]:CELLTYPE=EXTCELL) then all control channels must be set for 'extended mode'. Creating the TCHs for the cell: CREATE CHAN: NAME=BTSM:0/BTS:0/ TRX:0/CHAN:3. etc. this optional parameter specifies the Training Sequence Code of the radio channel. CHTYPE=TCHF_HLF. The TSC entered here is sent to the MS in the IE ‘Channel Description’ within the ASSIGNMENT COMMAND for the SDCCH.08 Training Sequence Code..4.01 GSM 05.. FALSE FALSE 289 .02 GSM 04. object: range: default: CHAN TRUE.The FR portion of the TCH always implies speech versions FR. object: range: default: CHAN 0.7 BCC of BSIC (CREATE BTS [BASICS]) Reference: GSM 05. Channel type..(TSC=). EXTMODE=FALSE. .The radio timeslot of an 'extended' channel must have an even number (0. see CREATE BTS [BASICS] parameter BSIC). Notes: .02 GSM 04.08 Object path name. Extended mode. The TSC for any type of SDCCH must correspond to the BCC (part of the BSIC sent on the SCH. If no value is entered for the parameter TSC the system automatically selects the BCC (see parameter BSIC (CREATE BTS [BASICS])) as TSC. while TCHs may be created as 'single' and 'extended' timeslots (see also parameters CELLTYPE in command CREATE BTS [BASICS] and EXTCHO in command SET HAND [BASICS]). SCH and FCCH. This is necessary for the correct decoding of the SDCCH.

The frequency hopping system can only be defined in the CHAN object. this parameter determines the TCH configuration for GPRS usage. object: range: CHAN FHSY_0.. GPRS access is then performed via the normal (GSM-) RACHs and an initial TBF assignment (IMMEDIATE ASSIGNMENT) is sent via the (GSM-)AGCH/PCH. the GPRS system information is broadcast on the existing (GSM-)BCCH within the SYSTEM INFORMATION TYPE 13. This has to be taken into account when the FHSYIDs are assigned to the CHAN objects. . if the hopping system is defined as FHSY. object: range: default: CHAN <NULL> PBCCH. hopping is not allowed for any CHAN object belonging to the BCCH TRX. <NULL> default: 0 = no hopping Reference: GSM 05. GPRS Dedicated Channel.If synthesizer frequency hopping is used.08 GSM 12. The following values are possible: a) PBCCH: The TCH is fixed defined as Packet BCCH. 0=no hopping. all other values Y must have been created before by CREATE FHSY:NAME=bsc:n/bts:n/fhsyid:y. .If GDCH is set to PBCCH.FHSYID=FHSY_1.In concentric cells (see CREATE BTS [BASICS]:CONCELL=TRUE) hopping is only allowed within the complete and within the inner area.GDCH can be set to PCCCH only if a PBCCH was created before. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to. which is the case if the TRX is defined as belonging to a service layer which is included in the SLL for GPRS services .20 GDCH=<NULL>.If no PBCCH is defined in the cell. if Dynamic MAIO Allocation (DMA. Shared TCHs can be used for GPRS and circuit switched traffic.please see command SET BTS [SERVICE] for further explanations) belong to the pool of TCHs that can be used for both circuit-switched calls and GPRS calls (so-called “Shared traffic channels”). the BTS measures the interference considering all frequencies used in the hopping sequence assigned to the a TCH in the frequency hopping system! . i. Notes: .FHSY_10. PCCCH. <NULL> Frequency hopping system identifier.in the CHAN object these parameters must be set to the <NULL> value in this case. By creating a PBCCH the signalling of circuit switched and packet switched traffic can be separated to avoid impacts on the circuit switched capacity in case of GPRS congestion and vice versa. Notes: . . Whether the GPRS calls can be preempted by CS calls depends on the setting of the downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]). The number of these TCHs that may be aligned as PDCHs simultaneously is determined by the parameter GPDPDTCHA (see CREATE PTPPKF). b) PCCCH: The TCH is fixed defined as Packet Common Control CHannel c) <NULL> identifies a “shared” TCH. 290 . . the GPRS mobile will not listen to the GSM BCCH but instead read the packet system information on the PBCCH.02 GSM 04. the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) . If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA). TCHF_HLF and TCHSD with CHPOOLTYP=TCHPOOL) for which GDCH is set to <NULL> (and for which the superordinate TRX supports GPRS. All TCHs (TCHFULL. A packet CCCH basically extends the CCCH capacity of the already created PBCCH.e.If Interference Classification of idle TCHs is enabled (see parameter INTCLASS in command SET BTS [INTERF]) while frequency hopping is active.

The TSC entered here is sent to the MS in the IE ‘Channel Description’ within the ASSIGNMENT COMMAND for the TCH.3 Mobile allocation index offset. to which the TCH is mapped. the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) . This parameter is sent in the main DCCH in the IE ‘Channel Description’ (contained e.. .timeslot no. this parameter defines the terrestrial channel.: 0. If no value is entered for the parameter TSC the system automatically selects the BCC (see parameter BSIC (CREATE BTS [BASICS])) as TSC.2-2. SCH and FCCH. If frequency hopping is enabled the parameter H is set to 1. object: range: default: CHAN 0. The mapping is fixed.MAIO=0..08 TERTCH=0.in the CHAN object these parameters must be set to the <NULL> value in this case. if the hopping system is defined as FHSY.e. determines start position of the channel in the frequency hopping algorithm.g. 291 .08 Training Sequence Code. this optional parameter specifies the Training Sequence Code of the radio channel.63.. object: range: default: Reference: CHAN 0. if Dynamic MAIO Allocation (DMA.34 timeslot-no. .subslot-no. Terrestrial channel. If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA).: 1-31 (PCM30) 1-24 (PCM24) subslot-no.> PCMB: 0. in the ASSIGNMENT COMMAND) if it was assigned to a used channel..7 BCC of BSIC (CREATE BTS [BASICS]) Reference: GSM 05.02 GSM 04.. i. T: pcmb-no. This is necessary for the correct decoding of the TCH. <NULL> 0 GSM 05. The TSC is part of the ‘Normal Bursts’ which are used for all channel types except RACH. object: format: range: CHAN <PCMB-no.The MAIO can only be defined in the CHAN object.>-<timeslot no. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to. (TSC=). In this case the IE also contains the HSN together with the MAIO. Note: .02 GSM 04.

For this feature. SDCCH/8 (CHTYPE=SDCCH and SCBCH) and TCH/SD that the operator decides to use as configured SDCCHs (CHTYPE=TCHSD with POOLTYPE= SDCCHPOOL). train stations etc. To change the channel type (CHTYPE) for a specific CHAN object. The mode of operation (SDCCH or TCH) can be changed using the CHPOOLTYP in a SET CHAN command. b) The purpose of the feature “Smooth Channel Modification” is to allow a dynamic “on-demand” extension of the SDCCH capacity in case of SDCCH congestion. The feature avoids blocking of the SDCCH in cases of unexpected high SDCCH loads generated by SMS traffic or in specific areas (e. a reset of the BBSIG respectively CU is triggered which causes the interruption of all calls currently served by the affected TRX. This classification is also valid for the TCH_SD used as SDCCH. When the SDCCH utilization resp. • The SDCCH_BACKUP_POOL is an additional system-internal (not configurable) pool that contains the TCH/SD sub-channels that are temporarily used as SDCCH. a) The purpose of the feature “Set Command for Changes of Channel Combinations” is to allow a change of the channel type from TCH to SDCCH and vice versa without any service impact. the BSC moves 8 SDCCH subchannels from the TCH/SD_POOL to the SDCCH_BACKUP_POOL A configurable timer (see parameter TGUARD in the command SET BSC [BASICS]) avoids oscillation between both pools. If during the processing of an SDCCH request the percentage of busy SDCCHs has exceeded the threshold SDCCHCONGTH. This SET CHAN command can be executed without any impact on the calls ongoing on the superordinate TRX. Within each pool the ‘idle Interference band’ classifies the resources. With the new feature it is possible to use the new channel type TCH/SD and to determine its mode of operation (SDCCH or TCH) by the parameter CHPOOLTYP (for further details please see below). it is necessary to delete and re-create it. • The TCH_POOL contains all channels declared as TCH full or TCH dual (CHTYPE=TCHFULL or TCHF_HLF) and TCH/SD that the operator decides to use as configured TCHs (CHTYPE=TCHSD with POOLTYPE=TCHPOOL).). a pool-concept was introduced for the dedicated radio channel resources: • The SDCCH_POOL contains all channels declared as SDCCH/4 (CHTYPE=MBCCHC and BCBCH).0. • The TCH/SD_POOL contains all channels created as TCH/SD that the operator decides to share between the TCH and SDCCH resources depending on the SDCCH traffic load situation (CHTYPE=TCHSD with POOLTYPE=TCHSDPOOL). SDCCH traffic load exceeds the threshold SDCCHCONGTH (see command CREATE BTS [BASICS]) the switchover from ‘Dual Rate TCH mode’ to ‘SDCCH/8 mode’ takes place automatically. These TCH may be used for both CS and GPRS traffic.g.Creating hybrid TCHs/SDCCHs (TCH/SD) for the cell: < The creation of hybrid TCHs/SDCCHs (TCH/SD) is an integral part of the feature “Set Command for Changes of Channel Combinations” and “Smooth Channel Modification” introduced in BR6. whenever a channel on a TRX is deleted and created again. However. Channels that shall be dynamically used both as SDCCH and TCH must be created with CHTYPE=TCHSD and parameter CHPOOLTYP=TCHSDPOOL (see below). 292 . airports.

0 for the features ‘ Smooth Channel modification ’ and ‘ Set Command for Changes of Channel Combinations ‘. this parameter can only be set for those channels that have been created with CHTYPE=TCHSD and defines its application (pool type). i. object: range: CHAN see parameter explanations on the right Reference: GSM 05. each TRX (TEI) has an own transmit queue. This is necessary because the Abis LAPD transmit queues in the BTS are managed per TRX(TEI). it is handled by the call processing and channel allocation as a normal dual rate TCH. 2) If CHPOOLTYP=SDCCHPOOL the TCHSD is fixed configured as SDCCH/8 and used exclusively as SDCCH/8. CHTYPE=TCHSD. The advantage of this configuration compared to a normal SDCCH is that it is possible to change this channel to ‘Dual rate TCH mode’ without service interruption of the TRX by entering the command SET TRX:CHPOOLTYP=TCHPOOL. to avoid an excessive concentration of the SDCCH signalling within one TRX (and thus one LPAD transmit queue). > CREATE CHAN: NAME=BTSM:0/BTS:0/ TRX:0/CHAN:4. that can work a) as pure Dual Rate TCH. TCHSD in TCHSD_POOL have to be included in a Layer associated at least to the Signalling SLL (see command SET BTS [SERVICE] for further explanations).1) + FACCH/H(0. Channel type = TCHSD. b) as pure SDCCH/8 or b) can dynamically change between both modes (DR-TCH or SDCCH/8).02 GSM 04. TCHSD = SDCCH/8 + SACCH/8 + TCH/H(0. i. As the biggest percentage of all signalling activities in a cell are processed via the SDCCHs.e. otherwise these channels will never be used as singalling channel (TCHSD with TCHSD Pool can be used also as traffic channels).e. 1) If CHPOOLTYP=TCHPOOL the TCHSD is fixed configured as TCH and used exclusively as TCH. depends on the setting of the parameter CHPOOLTYP (see below). this parameter was introduced in BR6. Note: When an Abis interface is configured via satellite. i.1) + SACCH/TH(0.08 Object path name.01 GSM 05.e. it is recommended.1) or TCH/F + FACCH/F + SACCH/F The above channel capability description means that the channel type TCHSD represents a channel. Channels of this type are part of the system-internal SDCCH_POOL. it is handled by the call processing and channel allocation in the same way as if it was created with CHTYPE=SDCCH.Note: All the TRXs with channels of type TCHSD in SDCCH_POOL. object: range: CHAN TCHPOOL SDCCHPOOL TCHSDPOOL <NULL> <NULL> default: 293 . Channels of this type are part of the system-internal TCH_POOL. Please refer to CHPOOLTYP for further details about the mentioned features. although with a more even distribution of the signalling load over the TEIs this could be avoided. it is urgently recommended to configure multiple SDCCH channels (and thus also all TCHSDs with CHPOOLTYP=SDCCHPOOL or TCHSD) on different TRXs. to distribute multiple SDCCHs over different TRXs within the cell. CHPOOLTYP= TCHSDPOOL. The advantage of this configuration compared to the one with CHTYPE=TCHF_HLF is that it is possible to change this channel to ‘SDCCH mode’ without service interruption of the TRX by entering the command SET TRX:CHPOOLTYP=SDCCHPOOL. Otherwise the probability of the BTSE alarm ‘LAPD TRANSMIT QUEUE OVERFLOW’ will considerably increase. Channel pool type. Which of these operation modes is in effect.

while TCHs may be created as 'single' and 'extended' timeslots (see also parameter EXTCHO in command SET HAND [BASICS]). TCHSD mode (Dual Rate TCH) TCHSDs with CHPOOLTYP=TCHSDPOOL are initially part of the system-internal TCH/SD_POOL. but is only selected by the TCH allocation algorithm if no idle TCH from the TCH_POOL (CHTYPE=TCHFULL or TCHF_HLF) can be found. Extended mode.. SDCCH mode (SDCCH/8) If the SDCCH traffic load has exceeded the SDCCH traffic load threshold SDCCHCONGTH (see CREATE BTS [BASICS]) the BSC moves 8 SDCCH subchannels from the TCH/SD_POOL to the SDCCH_BACKUP_POOL. i.. EXTMODE=FALSE.in this case the idle TCH measurements are sent to the BSC) or if it has received a CHAN ACT for channel type ‘TCH’.Only TCH/SDs with CHPOOLTYP=TCHPOOL can be used for GPRS traffic (“shared” TCH)! . INTCLASS in command SET BTS [INTERF]) are allocated first. If it has received a CHAN ACT for channel type ‘SDCCH’. Notes: . the TCHs with the best interference class (see par. . MBCCHC or BCBCH)) can be found. In this mode a TCH/SD works as normal dual rate TCH. for the BTS a TCH/SD is treated as a normal dual rate TCH if it is ‘idle’ (i. etc. the channel mode change is simply indicated by the channel type in the CHANNEL ACTIVATION procedure.The radio timeslot of an 'extended' channel must have an even number (0.e. object: range: default: CHAN TRUE.2. this parameter defines whether the channel is used in 'extended mode' for extended cells or not. . SCBCH. Instead. its mode of operation (Dual Rate TCH or SDCCH/8) can be dynamically changed depending on the SDCCH traffic load in the cell (see parameter SDCCHCONGTH in command CREATE BTS). it is treated as SDCCH/8.e. which the BSC performs before it sends an ASSIGNMENT COMMAND (for TCH assignment) respectively an IMMEDIATE ASSIGNMENT (for SDCCH assignment).If the cell type is extended cell (CREATE BTS [BASICS]:CELLTYPE=EXTCELL) then all control channels must be set for 'extended mode'. If the MS-BTS distance turns out to be small enough for a 'single' timeslot an intra-cell handover from far to near ('double-tosingle') is executed immediately (if enabled). FALSE FALSE 294 .). In this mode the channel works as a normal SDCCH/8.4.The BTS does not know anything about the association of the TCH/SD channels to the ‘BSC channel pools’. For the change of the mode of operation (SDCCH/8 or Dual Rate TCH) no special signalling activity is required: instead.If an extended cell is the target of an inter-cell HO the handover will always take place to a 'double' timeslot first as the BTS can only determine the actual MS-BTS distance when the first MS messages are received. but its SDCCH subslots are only selected by the SDCCH allocation algorithm if no idle SDCCH from the SDCCH_POOL (CHTYPE=SDCCH. Notes: . Within the TCH_POOL and the TCH/SD_POOL.3) If CHPOOLTYP=TCHSDPOOL the TCHSD can be used for Smooth Channel Modification.

.The frequency hopping system can only be defined in the CHAN object. the same goes for the the parameter combination CHTYP=TCHSD.g.20 GDCH=<NULL>.If synthesizer frequency hopping is used.If Interference Classification of idle TCHs is enabled (see parameter INTCLASS in command SET BTS [INTERF]) while frequency hopping is active. if the hopping system is defined as FHSY. if the hopping system is defined as FHSY.CHPOOLTYP=TCHPOOL (for parameter CHPOOLTYP please see above) which indicates that the TCHSD operates as a normal TCH. i. in the ASSIGNMENT COMMAND) if it was assigned to a used channel. Notes: . object: range: default: Reference: CHAN 0. hopping is not allowed for any CHAN object belonging to the BCCH TRX. i. 295 . This has to be taken into account when the FHSYIDs are assigned to the CHAN objects. Of course. If the TCH is created with the parameter combination CHTYP=TCHSD.CHPOOLTYP=TCHPOOL it can never be used for GPRS traffic.In concentric cells (see CREATE BTS [BASICS]:CONCELL=TRUE) hopping is only allowed within the complete and within the inner area. In this case the IE also contains the HSN together with the MAIO. <NULL> 0 GSM 05. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to.02 GSM 04. the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) . . object: range: CHAN FHSY_0. the parameters MAIO and FHSYID must be defined in the TRX object (see command CREATE TRX) .The MAIO can only be defined in the CHAN object.FHSY_10. This parameter is sent in the main DCCH in the IE ‘Channel Description’ (contained e.e. determines start position of the channel in the frequency hopping algorithm. If frequency hopping is enabled the parameter H is set to 1. Note: . <NULL> default: 0 = no hopping Reference: GSM 05.CHPOOLTYP=TCHPOOL Mobile allocation index offset. the BTS measures the interference considering all frequencies used in the hopping sequence assigned to the a TCH in the frequency hopping system! . if Dynamic MAIO Allocation (DMA. Only in this case the CHAN object belongs to the system-internal TCH_POOL. .FHSYID=FHSY_1.02 GSM 04. If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA). If the hopping system is to be defined by the CFHSY object (mandatory in case of DMA).e.in the CHAN object these parameters must be set to the <NULL> value in this case. i.08 Frequency hopping system identifier. for further details see command CREATE CBTS) is not used for the service layer the superordinate TRX belongs to.08 GSM 12. if Dynamic MAIO Allocation (DMA. It is only relevant for the parameter combination CHTYP=TCHSD. GPRS Dedicated Channel. this parameter determines the TCH configuration for GPRS usage (for further details please see the same parameter in the previous CREATE CHAN command for the creation of Full Rate or Dual Rate TCHs).63. the TCHSD can be used for CS as well as for GPRS traffic..in the CHAN object these parameters must be set to the <NULL> value in this case. all other values Y must have been created before by CREATE FHSY:NAME=bsc:n/bts:n/fhsyid:y. In this configuration only the value <NULL> is allowed for GDCH – this value indicates that the TCHSD works as “shared” TCH. 0=no hopping. object: range: default: CHAN <NULL> <NULL> MAIO=0.e.

7 BCC of BSIC (CREATE BTS [BASICS]) Reference: GSM 05. This is necessary for the correct decoding of the SDCCH. The TSC for any type of SDCCH and TCH/SD must correspond to the BCC (part of the BSIC sent on the SCH. If no value is entered for the parameter TSC the system automatically selects the BCC (see parameter BSIC (CREATE BTS [BASICS])) as TSC. The TSC entered here is sent to the MS in the IE ‘Channel Description’ within the ASSIGNMENT COMMAND for the SDCCH. The TSC is part of the ‘Normal Bursts’ which are used for all channel types except RACH. see CREATE BTS [BASICS] parameter BSIC). this optional parameter specifies the Training Sequence Code of the radio channel.. object: range: default: CHAN 0.08 Training Sequence Code. 296 .02 GSM 04.(TSC=). SCH and FCCH.

the BTS directly inserts the SUB values into the averaging window (assuming that DTX was active in the measurement period) thus allowing a preliminary decision.0 The DBAEM does not group the command parameters into ‘packages’ anymore. The default value of ‘2’ is therefore reasonable.. defines the averaging window size (that is smaller than the normal window size). 30 (dB) 6 (dB) ALEVFULHO=2-1. As the fast uplink handover should react quite quickly to UL level drops. Object path name. indicates the DTX weighting factor. because it has to wait for the next MEASUREMENT REPORT from the MS which contains the ‘DTX used’ flag. Instead. the BTS cannot make a handover decision directly after the end of the UL measurement period. object: unit: range: default: HAND [BASICS] 1 SACCH multiframe (averaging period) 1-31 (averaging period) 1-3 (DTX weight. i. this attribute defines two averaging parameters for the measurement process that is used for the fast uplink handover decision. To additionally speed up the fast uplink handover decision. During periods with speech transmission (i. but tests have shown that they reflect the real radio conditions well enough to SET HAND [BASICS] : NAME= BTSM:0/BTS:0/HAND:0. Advanced compression handover offset AMR. wLevFuho. Therefore positive dB values of this attribute will give preference to AMR calls (default). In case of a normal uplink handover. The logical group “[BASICS]” is normally only used on the LMT but was used here to allow a more useful grouping of the commands . This flag determines whether the BTS must enter the FULL values (if DTX was not used in the measurement) or the SUB values (if DTX was used in the measurement period) into the averaging window for the handover decision (for further details about DTX and FULL and SUB values please refer to the parameter DTXDL in command SET BTS [OPTIONS]). the averaging window should be significantly smaller than that of other handover types (e. the SUB values have a lower statistic reliability than the FULL values. DTX not used). sum of C/I + PL + ADVCMPHOOAMR before being compared to the other calls suitable for compression.e. the BTS uses a special algorithm for the UL measurement processing. see below) may be used to give preference to the selection of either AMR or non-AMR calls for a compression handover. Normally of all calls fulfilling the advanced compression rules the one with the highest sum of C/I and power reduction level (PL) is being selected (per SACCH multiframe). the second one. a different approach is used: At the end of the UL measurement period. all parameters of the previous ‘HAND packages’ were moved below the object HAND (now subordinate to the BTS object) and appear in the DBAEM in the SET HAND command. this parameter is related to advanced compression decompression handover (parameter EADVCMPDCMHO. Handover averaging parameters for fast uplink handover decision.g.e. For an AMR call additionally the value of this attribute is being added. factor) 2 (averaging period) 1 (DTX weighting factor) 297 . aLevFuHo. For fast uplink handover. negative dB values to non-AMR calls and a 0dB value will rate both call types equally. level handover). The first field. A change of the attribute becomes effective in the next SACCH multiframe.Setting the cell specific parameters and threshold values for voice call Handover: For detailed information regarding Handover Thresholds please refer to the chapter Handover Thresholds & Algorithms and Interworking of Handover and Power Control! Attention: Since BR6. object: unit: range: default: HAND [BASICS] 1dB -30. ADVCMPHOOAMR =6.

0! justify a preliminary decision.for the downlink . the actual value range that is supported by the BTS is 1.31 5 Parameter value range adapted to real range (1. if the BTS detects (after averaging) that the MS requests a CODEC mode change in the downlink. The Periodicity of the CMR sending depends on whether DTX uplink is currently used or not.63.e. this attribute should be set to its maximum value as a the CODEC mode adaptation process (which is . Handover averaging parameters for AMR CODEC MODE REQUESTs. When a valid CMR is received. the averaging window for the neighbour cell measurements for fast uplink handover is AveragingPeriodFULHO-NC = ALEVFULHO – 1 SACCH multiframe This approach was chosen. TDMA speech frame (i. every 40 ms). the CMR CMR is repeated every 8.. then the CMR sending period lies between 40ms and 160ms. the CMR is sent every second TDMA speech frame (i. Then the average is calculated over the values present in the AMR-DL-averaging window and the average is rounded to the nearest integer value. ..e.. This means that. even if no change of the current CODEC is required. object: unit: range: default: HAND [BASICS] 1 CMR 1. this means that the suitable neighbour cell for fast uplink handover is derived from only one Measurement Report. This means that.Despite the actual selectable value range of 1. which generally defines a comparatively long averaging period. 160ms). in case of a small value of 298 . it does not make sense to set this parameter to a value greater than 31. Notes: . this parameter defines the size of the averaging window for downlink CODEC MODE REQUESTs (CMR) received from the MS during an AMR (Adaptive MultiRate) call. Also for the averaging of the neighbour cell downlink RXLEV measurements. If DTX uplink is continuously used. this CMC reaches the TRAU much later than in case of a terrestrial link. it is entered to the circular buffer (averaging window) for the AMR-CMRs whose size is defined by AMRACMRDL. The rounded average indicates the offset of the presently most appropriate CODEC within the ACS. the BTS sends a corresponding CODEC MODE COMMAND (CMC) to the TRAU to instruct the TRAU to perform the switchover to the new mode. If the ‘DTX used’ flag.31) in BR8.executed by the TRAU) is considerably slowed down by the higher transmission delay on the satellite link.31. that is received in the MEASUREMENT REPORT from the MS 480ms later. indicates that in the affected measurement period DTX was ‘not used’. the approach for fast uplink handover is different from the one of the other handover types: while for all other handover types the size of the averaging window for the neighbour cell downlink RXLEV measurements is determined by the parameter HOAVPWRB (see below). If DTX uplink is not used. This algorithm reduces the handover decision time by one measurement period (480ms) with a minimum impact on the reliability of the averaged UL RXLEV values.If the BTS is connected to an Abis via satellite link of if the Asub is created via satellite link. as a very quick handover decision due to fast uplink requires the consideration of the neighbour cells that offer a sufficient DL RXLEV at that particular point of time. In other words. The CMRs are continuously sent from the MS to the BTS.. if the default value is used (ALEVFULHO=2-1). Due to the higher delay on the satellite link. The purpose of this parameter is to avoid a too frequent changes of the downlink CODEC mode in case of instable or quickly varying radio conditions. If the usage of DTX changes in smaller steps. the BTS removes the SUB value from the averaging window and replaces it by the FULL value (the number of FULL values inserted depends on the DTX weighting factor). As mentioned in the parameter AMRFRC1 (see CREATE BTS [BASICS]).AMRACMRDL=5.

it has no relevance for the handover decisions for AMR calls. e. see below) is represented by the path name of the affected BTS object. object: range: default: HAND [BASICS] BTSM:<n>/BTS:<n>. object: range: default: HAND [BASICS] BTSM:<n>/BTS:<n>. “BTSM:0/BTS:0”. HORXLVDLO and HOCCDIST. Colocated cell 1. . this parameter is only relevant if the parameter ININHO (see below) is set to TRUE and defines the first of two possible adjacent sectorized concentric cells (see parameter CONCELL in command CREATE BTS [BASICS]) to which an intercell handover from inner-to-inner area shall be possible. This means that it is up to the operator to enter only object path names of BTS instances that are really configured correspondingly. if the concentric cell is no ‘dualband concentric cell’ (i. to avoid a ‘too nervous’ link adaptation reaction in case of quickly changing radio quality conditions. as the execution of the CODEC mode change (via CMR and CMC) is slowed down. <NULL> <NULL> AMRACMRDL and quickly changing radio conditions. FALSE FALSE CCELL1=<NULL>. this flag determines whether in the concentric cell (see parameter CONCELL in command CREATE BTS [BASICS]) the distance should also be taken into account for the intracell handover decision and for the channel assignment decision during call setup. Enable concentric cell distance handover.CCDIST=FALSE. please see below. it also makes sense to slow down the CODEC mode change decision. For more details please see parameter CCELL1. that triggered it. however. object: range: default: HAND [BASICS] TRUE.The averaging mechanism for the uplink AMR CODEC mode adaptation is independent of AMRACMRDL as the associated averaging mechanisms are hardcoded.new calls are set up in the inner area or a handover from complete to inner area is executed if the level conditions defined by the parameter HORXLVDLO are fulfilled and if the MS-BTS distance is smaller than the distance limit according to the principles explained for the parameter HOCCDIST.although the parameter AMRACMRDL is included in the SET HAND command. are no longer present. Attention: this distance criterion. . is only considered. for which the target area (inner or complete) shall be determined by the PREFERRED AREA REQUEST procedure during intercell handover.g.new calls are set up in the complete area or a handover from inner to complete area is executed if the level conditions defined by the parameters HORXLVDLO (for call setup) and HORXLVDLI (for handover) are fulfilled or if the MS-BTS distance exceeds the distance limit according to the principles explained for the parameter HOCCDIST. Thus. This means that only in this case the BSC will start the PREFERRED AREA REQUEST procedure during intre-cell handover. <NULL> <NULL> CCELL2=NOT_DEFINEDNOT_DEFINED. the CODEC mode change could be executed at a point of time when the radio conditions. For the parameters HORXLVDLI. resp. this parameter defines the second of two possible adjacent sectorized concentric cells suitable for inner-to-inner handover. The ‘Colocated Cell' (for meaning of the term ‘colocated cell’ please refer to the parameter ININHO. 299 . Colocated cell 2. no concentric cell with mixed frequency bands in the TRXs)! Note: If CCDIST is set to TRUE then . Note: The BSC only allows the ‘inner-to-inner’ handover if both the originating and target cell of a handover procedure are configured as concentric cells (CONCELL=TRUE in command CREATE BTS [BASICS]).e. .

object: range: default: Reference: HAND [BASICS] TRUE. This flag is only relevant if power budget handover is enabled (PBGTHO=TRUE. It is only relevant if intercell handover is enabled (INTERCH=TRUE. It is. FALSE FALSE 300 . used for micro-/umbrella-cell configurations. Note: This flag only determines whether inter-cell handovers may be executed with cause ‘distance’. If the handover conditions are still present when the timer expires the handover is executed. only in effect for a certain neighbour cell if the parameter MICROCELL is also set to TRUE in addition. Speed sensitive handover shall allow power budget handovers to a microcell if an MS moves slow but shall prohibit them if the MS moves fast in order to avoid unnecessary signaling load due to repeated handovers (if the MS moves fast it may have left the microcell already when the handover is actually executed). An umbrella cell covers the same area as a number of microcells and is normally used as handover target cell in case of microcell congestion or for MSs which move very fast.g. see below). determines whether handover due to long distance between MS and BTS is enabled. The parameters relevant for the administration of speed sensitive handover are: MICROCELL. HOMDOFF and HOMSOFF (see command CREATE ADJC). DPBGTHO=FALSE. however. object: range: default: HAND [BASICS] TRUE.008 Distance Handover enabled. For this reason the power budget handover to a microcell is delayed by a special timer (the microcell is ‘penalized’ as long as the timer runs). HOMDTIME.) Speed sensitive handover is e. Dynamic power budget handover. FALSE TRUE 3GPP 45. The timer is administered with the parameter HOMDTIME (CREATE ADJC).DISTHO=TRUE. this parameter determines whether ‘dynamic power budget’ handover or ‘speed sensitive handover’ is active.

In other words. this parameter is used to enable/disable the feature ‘advanced compression/decompression handover’ algorithm which was introduced in BR7.0. i.the TCH load in the cell has exceeded the thresholds HRACTT1(HRACTT2)/HRACTAMRT1(HRACTAMRT2) or/and . compression-decompression handover was available only for AMR calls.0. In BR7. 301 . The compression handover algorithm is not continuously enabled in the BTS. <NULL> <NULL> Enable advanced compression decompression handover. which could be enabled by EADVCMPDCMHO. In other words: when the BSC detects during its cyclic TCH load check (see parameter TRFCT in command SET BSC[BASICS]) that . however.0. FALSE. HR) b) Decompression Handover is also triggered due to the current TCH load in the cell c) For compression and decompression handover that is triggered due to load conditions. the advanced compression / decompression handover was additionally enhanced: a) Compression/decompression handover is supported not only for AMR but also for non-AMR calls (FR. Moreover.the Abis TCH load has exceeded the threshold ABISHRACTTHR. only apply when. These enhancements.EADVCMPDCMHO=<NULL>. with . only one handover is triggered at a time and the minimum time between two consecutive handovers of the same type is 480ms. it was triggered to guarantee an acceptable QoS for the ongoing call in case the radio conditions deteriorate. in addition to EADVCMPDCMHO. In BR8.the most suitable call being selected first and . EFR. the BSC enables compression handover for the affected type of calls (AMR/non-AMR) by sending the corresponding SATT message to the BTS. to transfer AMR-FR or (E)FR calls with suitably good radio link quality to an AMR-HR or HR TCH by an intracell handover in order to prevent TCH blocking by providing additional TCH resources. Originally. the parameters EADVCMPHOAMR (for AMR calls) and EADVCMPHOSC (for non-AMR calls) are set to TRUE. only consisted of an improved handover decision algorithm that considered level citeria in addition to quality criteria. object: range: default: HAND [BASICS] TRUE. the BTS checks the ‘best suitable call’ criteria for this type of compression handover (description see below). but is temporarily enabled / disabled by the BSC (by sending the Abis O&M message SET ATTRIBUTE (SATT) to the BTS) depending on a) the current radio TCH load of the cell (see parameters HRACTAMRT1 and HRACTT1 in command CREATE BTS [BASICS]) or b) the current Abis pool TCH load of the BTSM (see parameter ABISHRACTTHR in command CREATE BTSM). a ‘best call selection’ mechanism is implemented in the BTS which ensures that compression and decompression handover is executed in a one-by-one manner. decompression handover was only triggered due to radio reasons. in case of high TCH load. Decompression handover Decompression can be triggered in two different scenarios: a) Decompression handover due to radio conditions b) Decompression handover due to low TCH load in the cell. the ‘advanced’ option of AMR compression/decompression handover.e. If enabled by the abovementioned database flags. while compression handover was triggered due to TCH load conditions in the serving cell. Detailed Description Compression handover The purpose of Compression handover is.a maximum handover trigger rate of one per 480ms period.

Moreover. the ‘best suitable call’ selection is not performed in this case. the AMR compression and decompression handover decision is solely based based on quality (C/I) criteria defined by the parameters HOTHAMRCDL. Important: This type of decompression handover is continuously enabled and is completely independent of the current BTS radio TCH load or Abis pool TCH load.e.the TCH load in the cell has dropped below the thresholds FRACTTH1(FRACTTH2)/FRACTAMRTH1(FRACTAMRTH2) or/and . HOTHAMRDDL and HOTHAMRDUL (see below). Only for this type of decompression handover the BTS checks the ‘most suitable call’ criteria (description see below). to transfer AMR-HR or HR to an AMR-FR or (E)FR TCH by an intracell handover in order to provide the best possible speech quality and QoS. however automatically disabled if HR is generally disabled in the BSC by setting the parameter HRSPEECH to FALSE (see command SET BSC [BASICS]). 302 . This type of decompression handover algorithm is not continuously enabled in the BTS. The parameter EADVCMPDCMHO just allows to switch between different modes of AMR compression/decompression handover (standard or advanced).a) Decompression handover due to radio conditions When a HR or AMR-HR call suffers from poor radio conditions the BTS triggers a decompression handover from HR to E(FR) or from AMR-HR AMR-FR in order to improve the speech quality and to guarantee an acceptable QoS. but is temporarily enabled / disabled by the BSC (by sending the Abis O&M message SET ATTRIBUTE to the BTS) depending on a) the current radio TCH load of the cell (see parameters FRACTAMRTH1 and FRACTTH1 in command CREATE BTS [BASICS]) or b) the current Abis pool TCH load of the BTSM (see parameters ABISHRACTAMR and ABISHRACTTHR in command CREATE BTSM). Compression/decompression handover decision Standard AMR Compression Handover (EADVCMPDCMHO=FALSE) Setting the flag EADVCMPDCMHO to FALSE simply means that the compression decompression handover is only triggered for AMR calls and that the AMR compression handover decision is done in the same way as in BR6. In other words: when the BSC detects that . the decompression handover is triggered immediately.e. i. in case of sufficiently low TCH load. the BSC enables decompression handover for the affected type of calls (AMR/non-AMR) by sending the corresponding SATT message to the BTS. Please note that the basic compression/decompression handover cannot be disabled by database command (it is.the Abis TCH load has dropped below the threshold ABISHRACTTHR. HOTHAMRCUL.0. for each call for which the appropriate radio conditions apply. i. b) Decompression handover due to low TCH load in the cell The purpose of this type of decompression handover is.

HOTHCMPLVUL. this setting has several effects: a) it enhances the compression/decompression handover decision algorithm by additional consideration of radio level criteria b) it extends the compression/decompression handover with the enhanced decision algorithm also to non-AMR calls (FR. HOTHDCMLVDL and HOTHDCMLVUL (see below) are considered.0) The advanced AMR compression/dedcompression handover algorithm additionally considers the current level conditions and the current dynamic power reduction due to BS and MS power control. As mentioned above. The AMR compression handover decision is based on the rules listed below: Advanced AMR Compression handover decision criteria An compression handover from AMR FR to AMR HR is triggered if a) the BTS has received the SATT message that enables this type of handover in the BTS and b) for an AMR call the following conditions are fulfilled {[(RXLEV_UL > HOTHCMPLVUL) AND (C/I_UL >= C/Imax)] OR (C/I_UL + MS_PWRRED > HOTHAMRCUL)} AND {[(RXLEV_DL > HOTHCMPLVDL) AND (C/I_DL >= C/Imax)] OR (C/I_DL + BS_PWRRED > HOTHAMRCDL)} 303 . a) Enhanced AMR compression/decompression handover decision algorithm by level criteria (since BR7. In this context the new parameters HOTHCMPLVDL. HR) c) it enables the load-dependent decompression handover decision d) it enables the ‘best suitable call selection’ mechanism for compression and decompression handover. EFR. This is done by considering an additional level threshold and by comparing the C/I thresholds to a C/I value that was ‘corrected’ by the corrent power reduction.Standard AMR Compression handover decision criteria An AMR compression handover from AMR FR to AMR HR is triggered if for a particular AMR FR if a) the BTS has received the SATT message that enables this type of handover in the BTS and b) for an AMR call the following conditions are fulfilled: (C/I_UL > HOTHAMRCUL) AND (C/I_DL > HOTHAMRCDL) Standard AMR Decompression handover decision criteria An AMR de-compression handover from AMR HR to AMR FR is triggered only due to radio conditions (without any enabling SATT message from the BSC) if for a particular AMR HR call the following conditions are fulfilled: (C/I_UL < HOTHAMRDUL) OR (C/I_DL < HOTHAMRDDL) Advanced AMR Compression Handover The advanced compression-decompression handover algorithm is enabled for AMR calls if the database settings EADVCMPDCMHO=TRUE and EADVCMPHOAMR=TRUE are applied.

2. the following additional conditions for compression are taken into account: 1. irrespective of whether C/I was considered in the primary condition or not. e. or alternatively. C/Imax. irrespective of whether C/I was considered in the primary condition or not. A C/I limited to a maximum C/Imax may reduce the benefit of adding C/I to the current MS/BS_PWRRED (power reduction due to power control) in the transient phase of a call (the ‘transient phase’ is the start phase of a call in good coverage conditions. alternatively. the following additional conditions for decompression are therefore taken into account: 1. measurements C/I are different for both links but not marked as such in the following for the sake of simplicity): [(RXLEVxx > HOTHCMPLVxx) AND (C/I >= C/Imax)] OR (C/I + MS/BS_PWRRED > HOTHAMRCxx) Decompression handover is triggered if the sum of C/I and MS/BS_PWRRED (power reduction due to power control) is lower than the decompression handover threshold (see second part of OR 304 . for a reasonable averaging window length. C/I is equal or greater than hard coded C/Imax. the BER is very low and. or. the accuracy of the resulting C/I is limited. For high C/I values. averaged RXQUAL is equal or smaller than a certain threshold. This limitation is related to the determination of C/I via measurements of BER and mapping on corresponding C/I values. DL. RXLEV is greater than a certain threshold As an example for a combination of these additional conditions with the primary conditions the following expression shall be used to trigger compression handover (must be fulfilled for both. In case that no bit errors have been measured during the measurement period no precise prediction of the real C/I is possible at all. Similarly. To avoid unjustified decompression handover in the transient phase. To avoid delayed compression handover in the transient phase.Advanced AMR Decompression handover decision criteria A de-compression handover from AMR HR to AMR FR is triggered only due to radio conditions (without any enabling SATT message from the BSC) if for a particular AMR HR call the following conditions are fulfilled: {[(RXLEV_UL < HOTHDCMLVUL) OR (C/I_UL < C/Imax)] AND (C/I_UL + MS_PWRRED < HOTHAMRDUL)} OR {[(RXLEV_DL < HOTHCMPLVDL) OR (C/I_DL < C/Imax)] AND (C/I_DL + BS_PWRRED < HOTHAMRDDL)} where MS_PWRRED = MS power reduction due to MS power control (in dB) BS_PWRRED = BS power reduction due to BS power control (in dB) C/Imax =20dB Background information on the advanced compression handover condition formulas and C/Imax In practice the process for the continuous determination of C/I values is limited to a maximum hard-coded value C/Imax=20dB. xx = UL. averaged RXQUAL is greater than a certain threshold 2. decompression threshold may be reached within the transient phase causing an unjustified decompression handover whereas an unlimited C/I measurement would have prevented this. RXLEV is smaller than a certain threshold. when the BS/MS power is still at the maximum or close to it but is continuously changing due to dynamic power reduction) in the following way: Reaching the compression threshold may be delayed whereas an unlimited C/I measurement would trigger compression immediately. C/I is smaller than a certain threshold.g.

the decompression handover is triggered immediately after allocating the call on the HR channel (PR = 0 and HOTHAMRDxx > 20 dB). immediately after compression handover) a further condition has to be fulfilled: C/I has to be lower than C/Imax. A compression handover from (E)FR to HR is triggered if a) the BTS has received the SATT message that enables this type of handover in the BTS and b) for a call the following conditions are fulfilled: (C/I_ULavg + MS_PL – HOTHxxDUL) < HRDCMLIMTH AND (C/I_DLavg + BS_PL – HOTHxxDDL) < HRDCMLIMTH xx = AMR-HR or HR d) ‘Best suitable call’ selection mechanism This mechanism is applied for both compression and decompression 305 .g.0 is also applied to non-AMR calls.0.0. the advanced compression-decompression handover decision algorithm which was introduced in BR7. The advanced compression-decompression handover algorithm is enabled for non-AMR calls if the database settings EADVCMPDCMHO=TRUE and EADVCMPHOSC=TRUE are applied. a MS close to the BTS will perform unjustified decompression handover. the decompression handover can also be triggered due to cell load conditions. Advanced non-AMR Compression handover decision criteria An compression handover from (E)FR to HR is triggered if a) the BTS has received the SATT message that enables this type of handover in the BTS and b) for a non-AMR call the following conditions are fulfilled: {[(RXLEV_UL > HOTHCMPLVUL) AND (C/I_UL >= C/Imax)] OR (C/I_UL + MS_PWRRED > HOTH(E)FRCUL)} AND {[(RXLEV_DL > HOTHCMPLVDL) AND (C/I_DL >= C/Imax)] OR (C/I_DL + BS_PWRRED > HOTH(E)FRCDL)} Advanced non-AMR Decompression handover decision criteria A decompression handover from HR to (E)FR is triggered only due to radio conditions (without any enabling SATT message from the BSC) if for a particular HR call the following conditions are fulfilled: {[(RXLEV_UL < HOTHDCMLVUL) OR (C/I_UL < C/Imax)] AND (C/I_UL + MS_PWRRED < HOTHHRDUL)} OR {[(RXLEV_DL < HOTHCMPLVDL) OR (C/I_DL < C/Imax)] AND (C/I_DL + BS_PWRRED < HOTHHRDDL)} where MS_PWRRED = MS power reduction due to MS power control (in dB) BS_PWRRED = BS power reduction due to BS power control (in dB) C/Imax =20dB c) Load dependent decompression handover In BR8. b) Extension of the advanced decision algorithm also for non-AMR calls In BR8.relation). To avoid unjustified decompression handover during the transient phase (e. This avoids that in case of unproper setting of the decompression handover threshold. An alternative condition to C/I < C/Imax is RXLEV_xx < HOTHDCMLVxx This will avoid that e.g.

When this message is received in the core controller a timer is started for the length of a measurement period (480ms). This leads to a rate of at maximum 1 compression HO initiation per measurement period (480ms). The call with the lower QI will become (or stay) the best-suited call for decompression. If the global feature attribute EADVCMPDCMHO is set to TRUE then out of all AMR and non-AMR calls within a cell that where selected for compression or decompression HO during the length of one measurement period (480ms) one call is selected which is bestsuited for the respective HO. This happens according to the following rules: Best call selection for compression HO When a call fulfils the abovementioned advanced compression checks and if EADVCMPHOAMR is TRUE for an AMR call or EADVCMPHOAMR is TRUE for a non-AMR call then BTS-internally a ‘compression request’ message is sent from the TRX (CU) to the core controller (COBA) containing a combined quality indicator (QI) for UL and DL as follows: QI = C/I_ULavg + MS_PL + C/I_DLavg + BS_PL (for non-AMR) QI = C/I_ULavg + MS_PL + C/I_DLavg + BS_PL + ADVCMPHOOAMR (for AMR) where MS_PL = current MS Power Level BS_PL = current BS Power Level When this message is received in the core controller a timer is started for the length of a measurement period (480ms). The TRX then performs another check of the abovementioned flags. A decompression HO due to radio conditions is always triggered immediately! When a call fulfils the above advanced decompression checks due to load conditions then a ‘decompression request’ message is sent from the TRX(CU) to the core controller (COBA) containing a selected quality indicator (QI) of UL or DL for AMR and non-AMR calls as follows: IF ((C/I_ULavg + MS_PL) <= (C/I_DLavg + BS_PL)) THEN QI = C/I_ULavg + MS_PL ELSE QI = C/I_DLavg + BS_PL In other words: the worst QI of UL or DL is selected. If both 306 . The call with the higher QI will become (or stay) the best-suited call for compression.handover. If both QI's are identical then the best-suited call remains unchanged. where the initial compression request of a call can be at most 480ms delayed (if it is the first call requesting compression and thus starting the 480ms timer on the core to collect all other possible compression requests). initiates the sending of the suitable INTRACELL HANDOVER CONDITION INDICATION. Best call selection for decompression HO A ‘best call’ selection for decompression HO is only done if a call was selected for decompression due to load conditions. When the timer expires a ‘compression ok’ message is sent to the TRX (CU) of the best-suited call which will then initiate an intracell HO request to the BSC. While the timer is running the QI's of all further incoming decompression request messages from other calls within the cell will be compared against that of the currently best-suited call (which at timer start is the first call requesting a decompression HO). however. if the handover was triggered by the BSC due to load reasons. While the timer is running the QI's of all further incoming compression request messages from other calls within the cell will be compared against that of the currently best-suited call (which at timer start is the first call requesting a compression HO). it is executed only.

Necessary decompression HO's of calls due to radio conditions are triggered independently and asynchronously within the cell (decision and trigger of these HO's take place solely within the CU). see below) they are initialized to RXQUAL=0 (i. C/I=20). The point of time of the first AMR compression/decompression handover decision depends on the type (FR. the compression-decompression handover decision algorithm considers the ‘MS power level’ (MS_PL) and BS power level’ (BS_PL). This leads to a rate of at maximum 1 initiation of a decompression HO due to load conditions per measurement period (480ms). The TRX then performs another check of the abovementioned flags. the features ‘Cell load dependent actvation of half rate’ (see parameter EHRACT in command CREATE BTS [BASICS]) and ‘Abis load dependent activation of half rate’ (see parameter ABISHRACTTHR in command CREATE BTSM) are not considered if the BSC receives an INTRACELL HANDOVER CONDITION INDICATION due to quality reasons (cause values ‘uplink quality’ or ‘downlink quality’). i. see below) due to quality (for a call whose quality is still poor after decompression handover). When the timer expires a ‘decompression ok’ message is sent to the TRX (CU) of the best-suited call which will then initiate an intracell HO request to the BSC.e.QI's are identical then the best-suited call remains unchanged. HR) of activated TCH: 1) If a FR TCH is activated the BTS starts checking for decompression only when the HO quality averaging windows for UL and DL are completely filled for the first time (i. which can occur due to subsequent execution of (AMR) decompression handover and intracell handover (parameter INTRACH. To avoid unnecessary compressiondecompression handovers. both MS_PL and BS_PL are averaged in the same way as the C/I values. This means that the BSC does not check the current BTS TCH load and the BTSM Abis pool TCH load in case of an intracell handover due to quality. where the initial decompression request of a call can be at most 480ms delayed (if it is the first call requesting decompression and thus starting the 480ms timer on the core to collect all other possible decompression requests). Note: To avoid a ping-pong handover from HR to FR and vice versa.e. (HOAVQUAL * 480ms (SACCH-period time) + 480ms (results of first SACCH-period are not entered in averaging windows)). As described above. initiates the sending of the suitable INTRACELL HANDOVER CONDITION INDICATION. so that in this case the initialization value does not have any influence (otherwise it might lead to an unjustified compression HO right away).e. 307 . for the MS and BTS power values the BTS uses an averaging window with the same length like the one defined for the quality handover averaging window (HOAVQUAL). Notes on averaging With each new channel activation the channels averaging windows are initialized and in case of the HO quality averaging windows (parameter HOAVQUAL. 2) If a HR TCH is activated the radio conditions are checked right away (after omitting the first SACCH-period results) since the average quality value is averaged down from perfect quality (RXQUAL=0) to match the real situation (so the initialization value prevents an early unjustified decompression HO).

If disabled. fast uplink handover is immediately triggered if the UL receive level drops below the fast uplink handover threshold THLEVFULHO. the BTS will still trigger decompression handovers for AMR calls will still be triggered if the corresponding conditions are met. which should be set shorter than the ones of the standard level handovers to allow a shorter reaction times. If enabled calls that fulfil all (advanced algorithm) compression conditions will be considered as candidates for an intracell (E)FR HR compression HO. Moreover. To qualify an adjacent cell as a suitable target cell for fast uplink handover. Such level drops can occur e. buildings). If disabled. For this reason the ‘fast uplink handover’ was introduced: This handover type uses own averaging windows (see parameter ALEVFULHO). i. this parameter enables the feature ‘Fast Uplink Handover’ (this parameter only relevant if intercell handover is enabled (INTERCH=TRUE. object: range: default: HAND [BASICS] TRUE. i. no AMR call will be selected for compression handover.e. in urban areas with small cells and obstacles in the radio path (e. AMR Decompression handover due to quality or due to load remains unaffected by this parameter. Note: This parameter is only checked during the AMR compression handover decision in the BTS . an additional administrable level offset is considered during the handover decision (see parameter FULRXLVMOFF in the ADJC object).g. this parameter is used to enable/disable the selection of nonAMR speech calls (using standard FR/EFR codecs) as candidates for the most suitable call for a compression handover.it thus only controls AMR compression handover. Fast uplink handover is completely de-coupled from the PWRC algorithm. Enable Fast Uplink handover.EADVCMPHOAMR=FALSE. object: range: default: HAND [BASICS] TRUE. FALSE FALSE EFULHO=FALSE. object: range: default: HAND [BASICS] TRUE. Note: This parameter is only checked during the non-AMR compression handover decision in the BTS . FALSE FALSE EADVCMPHOSC=FALSE. i. the standard level handover mechanism is often too slow to ‘rescue’ the call as a the standard level handover normally uses small but not very small averaging window sizes (normal is 4 SACCH multiframes ≈ 2 sec) and is only triggered after the PWRC control algorithm (if PWRC is enabled) has adjusted the transmit power to the maximum. Decompression handover due to quality or due to load for these calls remains unaffected by this parameter. and own handover trigger thresholds (THLEVFULHO). see below).e. If the level drops too quickly. A change of the attribute becomes effective in the next SACCH multiframe.it thus only controls compression handover for non-AMR speech calls. no matter whether the MS transmit power is already at the maximum or not. Fast Uplink Handover was introduced in BR6.0 to as an additional fast handover mechanism that is able to prevent call drops that occur due to a sudden and drastic drop of the UL receive level. even if EADVCMPHOAMR=FALSE. it is possible to priorize specific adjacent cells in the ranking of the target cells by a flag in the ADJC data (see 308 .e. even if EADVCMPHOSC=FALSE. A change of the attribute becomes effective in the next SACCH multiframe. If enabled AMR calls that fulfil all (advanced algorithm) compression conditions will be considered as candidates for an intracell AFR AHR compression HO. this parameter is used to enable/disable the selection of AMR calls as candidates for the most suitable call for a compression handover. Enable Advanced compression Handover for speech calls (nonAMR).g. the BTS will still trigger decompression handovers for non-AMR calls will still be triggered if the corresponding conditions are met. no non-AMR speech call will be selected for compression handover. FALSE FALSE Enable Advanced compression Handover for AMR.

This mechanism was implemented to increase the probability that the message is successfully transmitted and received/acknowledged from the MS side. FALSE FALSE ELIMITCH=TRUE. see below) and compression/decompression (parameter EADVCMPDCMHO. Enable level handover margin. b) Limitation of Intracell Handover due to Compression / Decompression The same mechanism as described above is also used for compression/decompression Handover (parameter EADVCMPDCMHO. an inter-cell handover is desired. For the “Limitation Dompression/Decompression Handover Repetition” an own counter is implemented in the BSC. if intra-cell handovers do not lead to better radio conditions. This message leads to the start of an administrable timer (see parameter TINOIERCHO) in the BTS which suppresses the generation of further INTRACELL HANDOVER CONDITION INDICATION messages with cause ‘quality’ as long as the timer runs. For further details. If the quality handover conditions persist and another quality handover is to be triggered an inter-cell handover due to quality is attempted (if no suitable neighbour cell is available. a ping-pong between compression handover and decompression handover may occur. however. the INTERCELL HANDOVER CONDITION INDICATION contains an empty target cell list). for consecutive repeated intra-cell handovers due to quality (triggered for a particular call) the idle TCHs are assigned cyclically without ever triggering an inter-cell HO unless one of the intra-cell HOs is not successful. For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. Tests have shown that. it simultaneously increases the BS and MS power. It enables a mechanism that prevents an unlimited repetition of intra-cell handovers due to quality (parameter INTRACH. Enable limitation of intra-cell handover repetition. object: range: default: HAND [BASICS] TRUE. a) Limitation of Intracell Handover due to quality In the current implementation the following scenario might happen quite easily: if the flag ELIMITCH is set to FALSE. This feature foresees the consideration of an additional level handover margin for the determination of suitable level handover target cells. In 309 .08 cause 'handover successful'. see above). If Idle Channel Supervision is activated (see command SET BTS [INTERF]) the BSC TCH allocation algorithm considers the interference levels reported via the RF RESOURCE INDICATION messages in addition. object: range: default: HAND [BASICS] TRUE.e. In cells with good level but high interference. this parameter enables the feature ‘level handover margin’. if the quality conditions are near to the quality thresholds for compression/decompression handover. Note: If the BTS transmits a HANDOVER COMMAND for a fast uplink handover to the MS via the Um.ELEVHOM=FALSE. If the flag ELIMITCH is set to TRUE. a counter implemented in the BSC is increased on every successful quality intracell HO completion. please refer to the parameter LEVHOM (command CREATE/CREATE ADJC) and to the section “Handover Thresholds and Algorithms” in the appendix of this document. FALSE TRUE parameter FULHOC in the ADJC object). which is increased whenever the BSC executes a compression/decompression handover (i. the next CHAN ACT message the BSC sends for an intra-cell quality handover contains the GSM08. this flag determines whether the feature 'Limitation of Intracell handover repetition’ is enabled or not. especially if frequency hopping is used. see above). sends a CHANNEL ACTIVATION after receipt of an appropriate INTRACELL HANDOVER CONDITION INDICATION). If the counter reaches an administrable threshold (see parameter MAIRACHO).

the first decompression handover (HR -> FR) is not taken into account). the BTS starts the timer TINOIERCHO and sets the handover suppression flag for that type of handover for which the CHAN ACTIVATION was received. If a call is set up on a HR channel. Note: For quality intracell handover.case of decompression HO to fullrate cause the internal counter is increased for each couple of compression/decompression HOs. When a CHAN ACT message for a particular TCH is received in the BTS which contains the cause ‘handover successful’. the next CHAN ACT message the BSC sends for an intracell decompression handover (activation cause extension ‘decompression’ included in the message) contains the GSM08. the BTS manages two separate flags that indicate whether a particular type of intracell handover (quality or compression) is currently prohibited for the runtime of TINOIERCHO.g.08 cause 'handover successful'. the handover suppression mechanism is separately managed for both handover types. Handover suppression in BTS In the BTS. as for the BTS a completely new channel context is opened. the new CHAN ACT for the decompression handover may contain (if the BSC counter for this handover type has reached the MAIRACHO threshold for compression handover) the cause ‘handover successful’ again but this time. after repeated intracell handovers due to quality the intracell quality handover was suppressed. this feature only works if the quality intra-cell HO is controlled by the BSC (LOTRACH=TRUE). but during the runtime of TINOIERCHO a decompression handover was executed. This message leads to the start of the timer (see parameter TINOIERCHO) in the BTS which suppresses the generation of further INTRACELL HANDOVER CONDITION INDICATION messages with cause ‘compression’ as long as the timer runs. another intracell handover due to a cause different from the suppressed one was successfully completed. i. In other words. only one of the flags can be set at a time. If e. the BTS will only set the supression flag for compression handovers and will thus prohibit only ‘compression handovers’ as long as TINOIERCHO runs. the counter is increased by '1' after one back-and-forth compressiondecompression handover FR->HR->FR.e. 310 . If this counter reaches the threshold MAIRACHO (see below) due to repeated ping-pong between compression and decompression handover. Intracell handovers due to quality are not suppressed in this case. This is due to the fact that in the BTS no ‘call context’ is known but just the context of the activated channel. However. the ‘suppression context’ is lost. If in the meantime.

Pa) the additional requirement RXLEV_NCELL(n) > RXLEV_DL + QUALLEVHOM(n) is checked.ENAQUALEVHOM=FALSE. This means that . object: range: default: HAND [BASICS] TRUE. this parameter enables the feature ‘level handover margin for quality handover’ which implies the evaluation of the level difference between the serving cell and the neighbour cell during handover due to ‘UL quality’ or ‘DL quality’ and the comparison of this difference to a configurable handover margin (as known from power budget handover). 311 . Only those neighbour cells that fulfil both criteria are regarded as suitable target cells for the level handover and are thus inserted into the target cell list of the of the INTERCELL HANDOVER CONDITION INDICATION sent by the BTS. FALSE FALSE Enable level handover margin for quality handover.in addition to the basic minimum criteria for handovers due to level (UL or DL) RXLEV_NCELL(n) > RXLEVMIN(n) + max (0.if the feature is activated . The idea of the feature is to trigger a handover due to level only to those cells whose downlink receive level exceeds that of the serving cell by a definable margin value. For the parameter QUALLEVHOM please refer to the command CREATE ADJC.

different minimum criteria and better cell criteria apply for UMTS FDD neighbour cells than for for GSM 2G neighbour cells: . Of course. this parameter represents the database flag to generally enable or disable handover from GSM to UMTS (2G3G handover). object: range: default: HAND [BASICS] TRUE. FALSE FALSE Enable UMTS better cell handover. For an accurate comparison of the current RXLEV value of the serving 2G cell to the RSCP value of the UMTS FDD neighbour cell (see explanations provided for parameter FDDREPQTY in command CREATE BTS [BASICS]). the minimum radio requirements for UMTS FDD neighbour cells are defined by the parameter RXLEVMINC (see command CREATE ADJC3G) . FALSE FALSE EUHO=FALSE.e. DCS.e. it is up to the operator to decide which type of handover shall be used for a particular cell. i. the ‘better cell’ radio requirement for UMTS FDD neighbour cells is defined by the parameter HOM defined in object ADJC3G (see command CREATE ADJC3G).While for GSM neighbour cells the minimum receive level for handovers is defined by the parameters RXLEVMIN (see command CREATE ADJC). this parameter represents the database flag to enable or disable ‘better cell’ handover from GSM to UMTS (2G-3G handover). even if they have been created as neighbour cells in the BSC database (see commands CREATE TGTFDD and CREATE ADJC3G). when ‘power budget handover’ is generally enabled (PBGTHO=TRUE). 5bis and 5ter. the parameter UADJ (see command CREATE ADJC3G) is considered in addition. the BTS will also consider UMTS FDD neighbour cells as possible target cells in addition to the normal 2G (GSM. UMTS handover due to ‘better cell’ and UMTS handover due to ‘sufficient coverage’ (see parameter EUBCHO) cannot be enabled at the same time. the parameter FDDREPQTY (see command CREATE BTS [BASICS]) must be set to the value RSCP. EUIMPHO and EUSCHO (see below) are relevant.EUBCHO=FALSE. the BTS excludes these 3G cells from the target cell list during the power budget handover decision process. the UE can only report 3G neighbour cells if EUHO was set to TRUE in the cell and the UE was thus informed via the MEAS INFO messages about the 3G neighbours to be monitored during an ongoing call. 312 .While for GSM neighbour cells the better cell criterion for power budget handovers is defined by the parameter HOM (see command CREATE ADJC). Enable UMTS handover. object: range: default: HAND [BASICS] TRUE. This parameter is only relevant if UMTS handover is generally enabled for this BTS (see parameter EUHO) and if ‘better cell’ handover (also called Power Budget Handover) is enabled in this BTS (see parameter PBGTHO). Only if EUHO=TRUE the parameters EUBCH (see above). Note: Like for 2G-2G handover. In other words. Attention: 2G-3G handover from GSM to UMTS FDD due to ‘better cell’ is only possible if the measurement reporting of the multiRAT mobiles is based on RSCP (level-oriented). Setting this EUBCHO=TRUE simply means that. If EUBCHO is set to FALSE. Note: It is important to consider that the BTS only sends the MEASUREMENT INFORMATION messages (that are sent on the DL SACCH and which are the 3G-equivalent to SYSTEM INFORMATION TYPE 5. as they indicate the 3G neighbour cells to be monitored by the UE) to the UE only if the flag EUHO is set to TRUE. i. PCS) neighbour cells for power budget handover decisions. the averaging of the reported RSCP values of the 3G neighbour cells is done on the basis of an averaging window whose length is defined by the parameter HOAVPWRB (see below).

‘downlink quality’. such as . . This parameter is only relevant if UMTS handover is generally enabled for this BTS (see parameter EUHO). different minimum criteria apply for UMTS FDD neighbour cells than for for GSM 2G neighbour cells. EUIMPHO is only relevant if at least one of the listed handover types is enabled by the abovementioned parameters. If EUIMPHO is set to FALSE. . even if they have been created as neighbour cells in the BSC database (see commands CREATE TGTFDD and CREATE ADJC3G). DCS. object: range: default: HAND [BASICS] TRUE.While for GSM neighbour cells the minimum receive level for handovers is defined by the parameters RXLEVMIN (see command CREATE ADJC). preemption and O&M intervention (see parameters ENFORCHO (SET BSC [BASICS]) and EPRE (SET BTS [OPTIONS])). see parameter RXLEVHO) . this parameter represents the database flag to enable or disable ‘imperative’ handover from GSM to UMTS (2G-3G handover).handover due to level (handover causes ‘uplink strength’ or ‘downlink strength’. The term ‘imperative handover’ represents handover types which are triggered to ‘rescue’ ongoing calls that suffer from bad radio conditions. PCS) neighbour cells for imperative handover decisions.forced handover (handover cause ‘forced’) due to directed retry. see parameter DISTHO).handover due to distance (handover cause ‘distance’.EUIMPHO=FALSE. exclusively depends on the handover-type-specific settings of the abovementioned database flags resp. parameters. see parameter RXQUALHO) . 313 . Which type of imperative handover is considered. Setting EUIMPHO to TRUE simply means that the BTS will also consider UMTS FDD neighbour cells as possible target cells in addition to the normal 2G (GSM. an additional minimum criterion is evaluated for imperative handovers towards UMTS FDD neighbour cells: the minimum radio requirements for UMTS FDD neighbour cells for an imperative handover are defined by the parameter UMECNO (see command CREATE ADJC3G). FALSE FALSE Enable UMTS imperative handover. . the BTS excludes these 3G cells from the target cell list during the imperative handover decision process.handover due to quality (handover causes ‘uplink quality’. Of course.As opposed to GSM 2G internal handovers. the minimum radio requirements for UMTS FDD neighbour cells are defined by the parameter RXLEVMINC (if FDDREPQTY the (see command CREATE ADJC3G).

determines whether the feature Extended Cell Handover is enabled for this cell. the minimum target cell level requirement is defined by the parameter USRSCP (see command CREATE ADJC3G). In other words.EUSCHO=FALSE. if the DL radio conditions of a particular 3G UMTS neighbour cell have exceeded configurable thresholds.If FDDREPQTY is set to ECNO (quality-oriented measurement reporting based on Ec/No=Energy chip to Noise). as all SDCCHs are only in the far area. i. the minimum target cell quality requirement is defined by the parameter USECNO (see command CREATE ADJC3G). depends on the measurement reporting method defined by the parameter FDDREPQTY (see command CREATE BTS [BASICS]): . UMTS handover due to ‘better cell’ (see parameter EUBCHO) and UMTS handover due to ‘sufficient coverage’ cannot be enabled at the same time. Enable extended cell handover.If FDDREPQTY is set to RSCP (level-oriented measurement reporting based on RSCP=Received Signal Code Power from UMTS).If an extended cell (CREATE BTS [BASICS]:CELLTYPE=EXTCELL) is the target of an inter-cell HO the handover will always take place to a 'double' timeslot first as the BTS can only determine the actual MS-BTS distance when the first MS messages are received. This parameter is only relevant if UMTS handover is generally enabled for this BTS (see parameter EUHO).e. FALSE FALSE EXTCHO=FALSE. As opposed to ‘UMTS better cell’ handover (see parameter EUBCHO) and ‘UMTS imperative handover’ (see parameter EUIMPHO). this parameter represents the database flag to enable or disable ‘sufficient coverage’ handover from GSM to UMTS (2G-3G handover). it is up to the operator to decide which type of handover shall be used for a particular cell. object: range: default: HAND [BASICS] TRUE.The intracell handover causes “near to far” (single to double) respectively “far to near” (double to single) do not exist for SDCCHSDCCH handover as in an extended cell all SDCCHs are always configured as double timeslots. FALSE FALSE Enable UMTS sufficient coverage handover. This handover is performed on distance criteria determined on the basis of the threshold HOSTAM and the margin HOMRGTA (see below). 'Extended cell handover' means an intra-cell handover from near to far (singleTS-todoubleTS) or from far to near (doubleTS-to-singleTS). Which thresholds are relevant. Thus the parameter EUSCHO explicitly enables this handover type and applies it to all UMTS neighbour cells that were created in the BSC database (see commands CREATE TGTFDD and CREATE ADJC3G). . Notes: . object: range: default: HAND [BASICS] TRUE. the sufficient coverage handover represents a new handover type which does not exist for GSM internal handovers and which is only applied for 2G-3G neighbour cell relations. If the MS-BTS distance turns out to be small enough for a 'single' timeslot an intra-cell handover from far to near ('double-to-single') is executed immediately (if enabled). . ‘Sufficient coverage’ handover is triggered. 314 . an SDCCH-SDCCH handover to the near area can never take place.

The term ‘levelOffsetNcell’ represents the parameter LEVONC (CREATE ADJC). this simply means that the target cell list generation process in the BTS considers the priority levels of the serving cell (see parameter PL. This flag is only relevant if intercell handover is enabled (INTERCH=TRUE. This calculated value is finally used in the distance handover decision process. the oldest measurement is removed from the window.HIERC=FALSE. object: range: default: HAND [BASICS] RANK0. The parameter HOAVDIST defines the size of the gliding averaging window for the measured timing advance values. The averaging window is called “gliding”.Pa) are subdivided into two sublists: The upper sublist consists of all neighbour cells where RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0.Pa) + levelOffsetNcell. This flag is only relevant if intercell handover due to distance is enabled (DISTHO=TRUE. FALSE FALSE HIERF=RANK0. this parameter defines the size of the gliding averaging window for the timing advance measurements used for distance handover. cells where RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0. see above). Handover averaging window for distance handover. RANK1 RANK0 HOAVDIST=8. the lower sublist consists of all neighbour cells where RXLEV_NCELL(n) ≤ RXLEVMIN(n) + Max(0. see below). the lower sublist consists of all neighbour cells where PBGT(n) . The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. Possible values: Rank0 (Ranking Method 0): All adjc. Within each sublist the cells are sorted in increasing order of priority Neighbour cells with the same priority are sorted by PBGT(n) . The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average. 315 . For further details please refer to the section ‘Handover Thresholds & Algorithms’. object: unit: range: default: HAND [BASICS] 1 SACCH multiframe =480ms 1-31 8 Hierarchical Cell Handover. Within each sublist the cells are sorted in increasing order of priority Neighbour cells with the same priority are sorted by PBGT(n) . All measurements for handover pass an averaging algorithm. quality and distance) and forced handover (directed retry. relevant for all imperative handovers. The selectable ranking methods RANK0 and RANK1 are only relevant for imperative handovers (i. level.cells where RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0. this flag enables the feature ‘hierarchical cell structures’. this parameter is used to switch between two different ranking methods.HO_MARGIN(n) ≤ 0.Pa) are subdivided into two sublists: The upper sublist consists of all neighbour cells where PBGT(n) . except fast uplink handover).HO_MARGIN(n) > 0 .e. see parameter ENFORCHO (SET BSC [BASICS])). Rank1 (Ranking Method 1): All adjc. Hierarchical cell ranking flag. The distance between BTS and MS is determined from the ‘timing advance value’ which is continously measured by the BTS from the propagation time on the radio path.HO_MARGIN(n). object: range: default: HAND [BASICS] TRUE.HO_MARGIN(n).Pa) + levelOffsetNcell. as the window works as a queue: when a new measurement is received. only relevant in case of power budget handover and traffic handover) and the neighbour cells (see parameters PLNC and PPLNC in the ADJC object. If it is set to TRUE.

The averaging window total is then calculated by adding up all sample values currently stored in the within the averaging window while a single sample is added number of ‘weight’ times. the current weighting factor is stored in parallel under the same offset as shown in the following picture: max_av_win_size length offset sample weight 0 0 1 1 1 1 2 2 1 3 3 1 4 4 2 5 5 2 6 6 1 7 0 0 8 0 0 9 0 0 29 0 0 30 0 0 Thus the time needed to fill the averaging window will always be the same (i. FULL measurement samples from measurement periods with inactive DTX (speech transmitted) were inserted into the averaging window twice. The HOAVLEV “averaging period” defines the size of the gliding averaging window for the measured RXLEV values. Parameter format: averaging period . only dependent on the ‘laveraging period’ portion of the parameter HOAVLEV). The averaging window is called “gliding”. Notes: .as usual inserted into the averaging window as single values only. this parameter defines the size of the gliding averaging window and the DTX weighting factor for the uplink and downlink RXLEV measurements for level handovers.DTX weighting factor All measurements for handover pass an averaging algorithm. Then the total is divided by the ‘weight’ total (i.e. The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. Up to BR6. if the DTX weighting factor was set to “2”. Starting from BR7. The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average.0. see below). The DTX weighting factor determines how much more the FULL values shall be weighted for radio measurement results measured over a period with voice activity (DTX not active). factor) 8 (averaging period) 2 (DTX weighting factor) Handover averaging parameters for level handover. object: format: unit: range: default: HAND [BASICS] averaging period DTX weighting factor 1 SACCH multiframe =480ms (averaging period) 1-31 (averaging period) 1-3 (DTX weight.e. the higher weighting was implemented by the multiple insertion of the FULL measurement sample into the gliding averaging window.HOAVLEV=8-2. this approach has been changed: FULL measurement samples values for non-DTX channels no longer entered n-times into the averaging window anymore but every value will be entered once. the oldest measurement is removed from the window. as the BTS can trigger a level handover even if the averaging window is not yet completely filled with measurement 316 . while SUB measurement samples from measurement periods with active DTX (silence) were inserted into the averaging window only once (for further details about DTX and the meaning of FULL and SUB values please refer to the explanations provided for the parameter DTXDLFR). .0. It is only relevant if intercell handover due to level is enabled (RXLEVHO=TRUE.The size of the averaging window does not determine the minimum time the BTS needs to trigger a level handover at the very beginning of a call. In other words. For this reason only the SUB values (determined from the SACCH frames) are considered for the handover decision which are . all ‘weight’ values within the averaging window are added up). as the window works as a queue: when a new measurement is received. This calculated value is finally used in the handover decision process. In addition.In the SDCCH phase there are no TCH speech frames.

If the number of measurement samples for a particular neighbour cell have reached the value of HOAVPWRB. the level handover is triggered. as it is used for the averaging of the downlink RXLEV values of the neighbour cells. The parameter HOAVPWRB defines the size of the gliding averaging window for the measured RXLEV values. defines the size of the size of the averaging window for downlink RXLEV values of the serving cell (considering the current power reduction by the Power Control) for intercell handover due to Power Budget (PBGTHO=TRUE. if this minimum number of measurement samples was received and their averaged value indicates the handover condition with respect to the configured handover thresholds. the further averaging is only done over as many samples as determined by HOAVPWRB. . the oldest measurement is removed from the window. The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average. The averaging window is called “gliding”. The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. 317 .samples. however. It is important. this averaging window is used for all types of intercell handovers (except for Fast Uplink Handover). object: unit: range: default: Reference: HAND [BASICS] 1 SACCH multiframe =480ms 1-31 8 3GPP 45. Moreover. of Measurement samples 0 1 2 3 4 5 HOAVPWRB=8.008 Thus. Window size 0 1 2 3-12 13-20 21-31 Minimum no. see below). see below) and intercell handover due to traffic (TRFHOE=TRUE.The averaging window size for the neighbour cell DL RXLEV measurements is determined by the parameter HOAVPWRB (see below). This calculated value is finally used in the handover decision process for handover due to power budget and handover due to traffic. Note: The BTS uses the same averaging window size determined by HOAVPWRB also for the averaging of the neighbour cell DL RXLEV measurements for all other handover types (except Fast Uplink Handover). For each setting of the averaging window size there is a fixed defined minimum number of measurement samples that are necessary for a handover decision. to point out that for the neighbour cell DL RXLEV measurements HOAVPWRB just determined the maximum window size for averaging. Basically the BTS averages the received DL RXLEV measurement values of each reported neighbour cell over as many samples as have been received from the MS. Handover averaging window for power budget handover. All measurements for handover pass an averaging algorithm. as the window works as a queue: when a new measurement is received.

object: format: unit: range: default: HAND [BASICS] averaging period DTX weighting factor 1 SACCH multiframe =480ms (averaging period) 1-31 (averaging period) 1-3 (DTX weight.In the SDCCH phase there are no TCH speech frames. . as the window works as a queue: when a new measurement is received.DTX weighting factor The settings entered for HOAVQUAL are used for the averaging and DTX weighting for all types of handover decisions that feature an evaluation of the RXQUAL or C/I values (intercell and intracell handover due to quality.). as the BTS can trigger an imperative handover even if the averaging window is not yet completely filled with measurement samples.The averaging window size for the neighbour cell DL RXLEV measurements is determined by the parameter HOAVPWRB (see below). All measurements for handover pass an averaging algorithm. For this reason only the SUB values (determined from the SACCH frames) are considered for the handover decision which are . even if less samples have been received than places are foreseen in the averaging window. For quality handovers. This calculated value is finally used in the quality handover decision process. If the first samples have been inserted into the window. Notes: . factor) 6 (averaging period) 2 (DTX weighting factor) Handover averaging parameters for quality handover. 318 . the averaging window is initialized with values RXQUAL=0. The DTX weighting factor determines how much more the FULL values shall be weighted for radio measurement results measured over a period with voice activity (DTX not active). this parameter defines the averaging period and DTX weighting factor for the uplink and downlink RXQUAL measurements.as usual inserted into the averaging window as single values only. . The size of the averaging window determines the number of measurement samples (a new measurement sample is received every 480 ms from the MEASUREMENT REPORTs from the BTS and the MS) over which the BTS calculates the arithmetic average. if the RXQUAL average exceeds the defined threshold. the oldest measurement is removed from the window.HOAVQUAL=6-2. For further information about the management of the DTX weigthing factor please refer to the explanations provided for the parameter HOAVLEV. The algorithm can be described as a “gliding” averaging window: all measurement samples inside the window are used to calculate the arithmetic average. the BTS can trigger a quality handover. The HOAVQUAL “averaging period” defines the size of the gliding averaging window for the measured RXQUAL values. Parameter format: averaging period . The averaging window is called “gliding”. compression/decompression handovers etc.The size of the averaging window does not determine the minimum time the BTS needs to trigger a handover at the very beginning of a call.

The BTS responds with a PREFERRED AREA message stating which area is preferred. object: unit: range: HAND [BASICS] 1 dB 0.35 5 HOLTHLVDL=10. if the MS is already served by a TRX of the inner area. object: unit: range: default: HAND [BASICS] 1 km 0. . the call will be handed over to the inner area. The actual threshold value in [dBm] is calculated as follows: Handover Threshold (dBm) = -110dBm + HOLTHLVUL .. the call will be handed over to the complete area.HOCCDIST=5.. object: unit: range: HAND [BASICS] 1 dB 0. 319 . The decision is made on the basis of HORXLVDLI.e. defines the receive signal level threshold on the downlink for inter-cell level handover decision.. if the MS is already served by a TRX of the complete area. Handover lower threshold level uplink..63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . no concentric cell with mixed frequency bands in the TRXs)! It determines the distance limit used for the 'distance' intracell handover decision within the concentric cell and for the channel assignment decision during call setup. this parameter is only relevant if the parameter CCDIST is set to TRUE (see above) and if the concentric cell is no ‘dualband concentric cell’ (i. The actual threshold value in [dBm] is calculated as follows: Handover Threshold (dBm) = -110dBm + HOLTHLVDL .08 default: Reference: Handover concentric cell distance limit. see below). defines the receive signal level threshold on the uplink for inter-cell level handover decision.If MS-BTS-distance > HOCCDIST+1 then new calls will be set up in the complete area or.08 default: Reference: HOLTHLVUL=8. This parameter is only relevant if intercell handover due to level is enabled (RXLEVHO=TRUE. Please pay attention to the explanations for CCDIST (see above)! Handover lower threshold level downlink.If MS-BTS-distance < HOCCDIST then new calls will be set up in the inner area or. This parameter is only relevant if intercell handover due to level is enabled (RXLEVHO=TRUE. see below)..63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . HORXLVDLO and optionally also HOCCDIST (see above). 62 = -48dBm 63 = greater than -48dBm 10 GSM 05. The following rule has to be considered: HOLTHLVDL (SET HAND) < LOWTLEVD < [LOWTLEVD (SET PWRC) + 2∗PWREDSS (SET PWRC)] < UPTLEVD (SET PWRC) For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. The following rule has to be considered: HOLTHLVUL (SET HAND) < LOWTLEVU < [LOWTLEVU (SET PWRC) + 2∗PWREDSS (SET PWRC)] < UPTLEVU (SET PWRC) For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. 62 = -48dBm 63 = greater than -48dBm 8 GSM 05. During the call setup procedure the BSC sends the PREFERRED AREA REQUEST message to the BTS to ask whether the TCH shall be assigned in the inner or complete area of the concentric cell. ... The hysteresis '+1' is automatically applied to avoid handover oscillation if the MS moves very close to the defined distance limit.

...From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter HOAVQUAL..37 2..87 6..37 5.HOLTHQAMRDL=8.13 .87 5. 320 . .88 .38 . 5. 7 6.12 0 .. 5.. 6. 2...88 ... an intercell handover due to quality downlink is triggered if the downlink quality drops below the threshold determined by HOLTHQAMRDL..88 .. 4.The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the following table: RXQUAL 6. the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (0..88 . 4..88 ..12 5.63 .. If it drops below the threshold.... object: unit: range: default: HAND [BASICS] 1 dB 0... Attention: Unlike for the parameter HOLTHQUDL.7) in the MEASUREMENT REPORT messages... the values for HOLTHQAMRDL are entered in C/I values (carrier/interference in [dB]).62 4.20 8 Handover lower threshold quality AMR downlink. .7).63 . 2..12 4.62 6.13 .63 .Like any other MS. for which the quality values are entered in RXQUAL values (range 0. see below).37 C/I 12 13 14 15 16 17 18 19 20 For a more detailed mapping table please refer to the section “Mapping of RXQUAL and C/I values for AMR calls” in the appendix of this document.62 0.13 .63 .. 3. 2. Notes: In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls.. The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging). this parameter eclipses the threshold HOLTHQUDL in case of an AMR (Adaptive Multi Rate) call: For AMR calls.38 .62 1.. 5.. The BTSE-internal processing of these values is done in the following way: .. 4.13 . 6. 1..63 .38 .87 4... 6. 3...12 1. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter HOAVQUAL).. 6..62 C/I 1 2 4 5 6 7 8 9 10 11 RXQUAL 3.13 ..87 2.. This parameter is only relevant if intercell handover due to quality is enabled (RXQUALHO=TRUE..The integer C/I value is then compared to the threshold determined by HOLTHQUAMRDL.87 2. 0. .12 3. the BTS triggers an intercell handover due to “downlink quality”.. 1.

2% 1 = 0.The integer C/I value is then compared to the threshold determined by HOLTHQUAMRUL.4% 6 = 6.. this parameter eclipses the threshold HOLTHQUUL in case of an AMR (Adaptive Multi Rate) call: For AMR calls.4% 2 = 0.. Attention: Unlike for the parameter HOLTHQUDL.7).From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter HOAVQUAL.6% to 3.6% 4 = 1. This parameter is only relevant if intercell handover due to quality is enabled (RXQUALHO=TRUE. The BTSE-internal processing of these values is done in the following way: .7 0 = less than 0. The following rule has to be considered: HOLTHQUDL (SET HAND) > LOWTQUAD (SET PWRC) > UPTQUAD (SET PWRC) For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. HOLTHQUDL=5..2% 5 = 3. . object: range: HAND [BASICS] 0. the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (0. This parameter is only relevant if intercell handover due to quality is enabled (RXQUALHO=TRUE. the values for HOLTHQAMRDL are entered in C/I values (carrier/interference in [dB]).008 Handover lower threshold quality downlink. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter HOAVQUAL).Like any other MS.2% to 6.. an intercell handover due to quality is triggered if the quality drops below the threshold determined by HOLTHQAMRDL. object: unit: range: default: HAND [BASICS] 1 dB 0.4% to 12.7) in the MEASUREMENT REPORT messages.HOLTHQAMRUL=8..The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the mapping table included in the parameter description of HOLTHQAMRDL (see above).8% default: 5 Reference: 3GPP 45. defines the receive signal quality threshold on the downlink for inter-cell quality handover decision. . see below). .8% 7 = greater than 12. for which the quality values are entered in RXQUAL values (range 0.8% 3 = 0. see below). 321 .2% to 0. Note: In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls. If it drops below the threshold.8% to 1. The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging). the BTS triggers an intercell handover due to “uplink quality”.4% to 0.20 8 Handover lower threshold quality AMR uplink.

see above) is applied to this threshold.4% 6 = 6. a ‘single’ TCH. object: unit: range: HAND [BASICS] 1 dB 0. To avoid ping-pong handovers an additional margin (parameter HOMRGTA.2% 1 = 0. The following rule has to be considered: HOLTHQUUL (SET HAND) > LOWTQUAU (SET PWRC) > UPTQUAU (SET PWRC) For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. object: range: HAND [BASICS] 0. This parameter is only relevant if intercell handover due to quality is enabled (RXQUALHO=TRUE.2% 5 = 3.2% to 6.e. It specifies the maximum allowed MSBTS distance for the use of a 'not extended' radio channel (i.8% default: 5 Reference: 3GPP 45.. 322 . defines the receive signal quality threshold on the uplink for inter-cell quality handover decision.. the handover decision can also be based on the distance criteria defined by the parameter HOCCDIST (see parameters CCDIST and HOCCDIST). If the MS-BTS distance determined during call setup is below this threshold the call is set up on a 'single' timeslot . Rule: HOMSTAM < HOTMSRME (HAND) < EXCDIST (BTS [options]) RXLEV threshold downlink inner.8% 7 = greater than 12. this parameter defines the downlink receive level threshold in the inner area of a concentric cell (see parameter CCELL in command CREATE BTS [BASICS]). see parameter EXTMODE (CREATE CHAN))..63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm ..An extended cell handover from near to far (singleTS-to-doubleTS) is executed if MS-BTS distance = HOMSTAM .6% to 3. Optionally.8% to 1. Its transition causes an intracell handover from the inner area the complete area.4% 2 = 0.34 32 HORXLVDLI=22. object: unit: range: default: HAND [BASICS] 1km 0. The threshold HOMSTAM is also used for intracell handover decisions for extended cell handovers (see parameter EXTCHO in command SET HAND [BASICS]) between the areas (far-to-near or near-to-far handovers). It is applied to the MS-BTS distance threshold for the maximum MS distance (see parameter HOMSTAM) in the following way: ..An extended cell handover from far to near (doubleTS-to-singleTS) is executed if MS-BTS distance = HOMSTAM-HOMRGTA Threshold for the maximum MS distance.if it is above the threshold the call is set up on a 'extended' TCH (also called ‘double’ timeslot).4% to 0. HOMRGTA=4.4% to 12. see below).7 0 = less than 0. this parameter specifies the timing advance margin for the extended cell handover (see parameter EXTCHO). this parameter is only relevant for extended cells (see parameter CELLTYPE in command CREATE/SET BTS [BASICS]). 62 = -48dBm 63 = greater than -48dBm 26 default: Handover margin for timing advance.34 4 HOMSTAM=32.008 Handover lower threshold quality uplink. Rules: for configuration rules for concentric cells and dualband concentric cells please refer to the parameter description of HORXLVDLO (see below).6% 4 = 1.HOLTHQUUL=5. object: unit: range: default: HAND [BASICS] 1km 0.2% to 0. Intracell Handover: If the MS is served by the TRX of the inner area.8% 3 = 0.. the MS will be handed over to the complete area TRX if the condition RXLEV_DL < HORXLVDLI is fulfilled.

a complete-to-innet handover is triggered if the condition RXLEV_DLCOMPL > HORXLVDLO + Max[0. see command SET ADJC) for this calculation. MSTXPMAXDCS and MSTXPMAXPCS. If RXLEV_DL < HORXLVDLO the call is set up in the complete area. The BTS responds with a PREFERRED AREA message stating which area is preferred. as in such configurations the coverage difference between inner and complete area is controlled by the PWRRED parameter (see command CREATE TRX).PWRREDcomplete) + HOM [dB] where HOM = margin to avoid ping-pong HO due to fading. The decision is made on the basis of HORXLVDLO and HOCCDIST (see parameter CCDIST). Intracell Handover: If the MS is served by the TRX of the complete area.To avoid 'ping pong' handovers between inner and complete area the following rule should be followed: HORXLVDLO . handovers that might occur due to normal level variations even when the subscriber remains in a stationary position on the border between inner and complete area.HORXLVDLO=42. if the condition RXLEV_DL > HORXLVDLO + Max[0.. but it makes sense to assume the HOM default value as a suitable default setting. the MS will be handed over to the inner area TRX if the condition RXLEV_DL > HORXLVDLO is fulfilled. object: unit: range: HAND [BASICS] 1 dB 0. see CREATE BTS [BASICS]) and the MS power capability in the band used for the inner area.If a cell is configured for two different frequency bands as ‘dual band concentric cells’ (refer to parameters CELLTYP and CONCELL. It is not necessary to use the default value of HOM (power budget handover margin. the handover decision can also be based on the distance criteria defined by the parameter HOCCDIST (see parameters CCDIST and HOCCDIST).. The additional margin must be applied as a kind of ‘hysteresis’ which avoids ping-pong handovers due to fading effects. 62 = -48dBm 63 = greater than -48dBm 32 default: RXLEV threshold downlink outer.PINN)] is fulfilled. Optionally. i. suggested value = default value of parameter HOM (ADJC object) This rule is relevant for single-band concentric cells..e. This means that a call is set up in the inner area. i. (MS_TXPWR_MAXINN . If RXLEV_DL > HORXLVDLO the call is set up in the inner area. The decision for an complete-to-inner intracell handover is based on exactly the same calculation. (MS_TXPWR_MAXINN .e. . Special Case: If in the cell the feature “dualband concentric cell “ with GSM 900/1800 or 850/1900 Dual Band Operation is configured. this parameter defines the downlink receive level threshold in the complete area of a concentric cell (see parameter CCELL in command CREATE BTS [BASICS]). the call setup and intracell handover decision considers the difference in the maximum allowed transmission power (derived from the parameters MSTXPMAXGSM. Its transition causes a call setup in the inner area or an intracell handover from the complete area to the inner area.HORXLVDLI > (PWRREDinner .63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . Rules: . see above) the coverage difference is rather determined by the different transmission power values of the used CU PA modules and the different propagation attenuation in different frequency bands 323 .PINN)] is fulfilled. Call Setup: During the call setup procedure the BSC sends the PREFERRED AREA REQUEST message to the BTS to ask whether the TCH shall be assigned in the inner or complete area of the concentric cell.

The intracell handover causes “complete to inner” and “inner to complete” do not exist for SDCCH-SDCCH handover as in a Concentric Cell all SDCCHs are always configured in the complete area. i. an SDCCH-SDCCH handover to the inner area can never take place. see command SET ADJC) for this calculation. In this case the rule should be expressed as follows: HORXLVDLO ..HORXLVDLO is also evaluated during also evaluated during intercell handover between colocated concentric cells. The Path Loss Difference (PLD) is the difference in the radio propagation attenuation between the different used frequency bands (e. but it makes sense to assume the HOM default value as a suitable default setting. handovers that might occur due to normal level variations even when the subscriber remains in a stationary position on the border between inner and complete area.HORXLVDLI >= 20dB has turned out to work fine without any ping-pong effects between inner and complete area. The actual threshold value in [dBm] is calculated as follows: Handover Threshold [dBm] = -110dBm + HOTDLINT . To guarantee a correct interworking of power control and intracell handover.HORXLVDLI > BS_TXPWR_MAXCOMPL . GSM900 and DCS1800). Notes: .. It is not necessary to use the default value of HOM (power budget handover margin.08 default: Reference: The additional margin must be applied as a kind of ‘hysteresis’ which avoids ping-pong handovers due to fading effects.g. 62 = -48dBm 63 = greater than -48dBm 35 GSM 05. as all SDCCHs are only in the complete area. For dualband cells.than by different values of static power reduction of the TRXs.63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . It is only relevant if intracell handover due to quality is enabled (INTRACH=TRUE. 324 . In other words. . the rule of thumb HORXLVDLO ..e. please refer to the explanations provided for parameter ININHO (see below). This value must be known to the operator from live network measurements.BS_TXPWR_MAXINN + HOM + PLD [dB] where BS_TXPWR_MAXCOMPL = Maximum BS transmission power of complete area TRX at the antenna output BS_TXPWR_MAXINN = Maximum BS transmission power of inner area TRX at the antenna output HOM = margin to avoid ping-pong HO due to fading. For further details. the following rule must be fulfilled: UPTLEVD > HOTDLINT For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. object: unit: range: HAND [BASICS] 1 dB 0. Handover threshold level downlink intra. this parameter defines the receive signal level threshold in the downlink for the quality intracell handover decision. see below). suggested value = default value of parameter HOM (ADJC object) PLD = Path Loss Difference HOTDLINT=35.

7) in the MEASUREMENT REPORT messages. Attention: Like for other AMR quality handover parameters (such as HOLTHQAMRDL). the BTS triggers an intracell handover due to AMR compression.. .. Notes: In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls.. The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). 325 .Like any other MS. the values for HOLTHQAMRDL are entered in C/I values (carrier/interference in [dB]). the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (0. If it exceeds the threshold (and HOTHAMRCUL is exceeded. this parameter represents the downlink quality threshold used to trigger an intracell AMR Compression Handover "fullrate to halfrate”. .0! Handover threshold AMR compression downlink.HOTHAMRCDL=18.The integer C/I value is then compared to the threshold determined by HOTHAMRCDL. The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging). the AMR compression handover (AMR fullrate to AMR halfrate) is triggered only if both the thresholds for UL quality and DL quality (HOTHAMRCDL and HOTHAMRCUL. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter HOAVQUAL). see below) are exceeded. 20 18 Value range and Default value changed in BR8. Important: In contrast to the AMR decompression handover (see parameter HOTHAMRDDL). From BR7.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. object: unit: range: default: HAND [BASICS] 1 dB 0. .The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the table included in the parameter description of HOLTHQAMRDL (see above).From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter HOAVQUAL. too!). The BTSE-internal processing of these values is done in the following way: .

0! HOTHAMRDDL=13.. If it drops below the threshold HOTHAMRDDL.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. . the mapping limits the maximum useful C/I value to 20dB (see mapping table shown for HOLTHQAMRDL).. The resulting average RXQUAL value is calculated with a resolution of two places (digits) after the comma (this is achieved by multiplying the RXQUAL values with 100 before averaging). the AMR compression handover (AMR fullrate to AMR halfrate) is triggered only if both the thresholds for UL quality and DL quality (HOTHAMRCDL and HOTHAMRCUL) are exceeded. object: unit: range: default: HAND [BASICS] 1 dB 0.. the values for HOLTHQAMRDL are entered in C/I values (carrier/interference in [dB]).0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. From BR7. the BTS triggers an intracell handover due to AMR decompression. object: unit: range: default: HAND [BASICS] 1 dB 0. Important: In contrast to the AMR decompression handover (see parameter HOTHAMRDDL). C/I threshold values above 20dB therefore can never be reached and will not show any effect.The resulting ‘high-precision’ RXQUAL value is then mapped to an integer C/I value according to the table included in the parameter description of HOLTHQAMRDL (see above).The integer C/I value is then compared to the threshold determined by HOTHAMRDDL. 326 .Like any other MS. the Intracell AMR decompression handover "halfrate to fullrate" is triggered if either the UL quality drops below the threshold HOTHAMRDDL or the DL quality drops below the threshold HOTHAMRDUL. . The BTSE-internal processing of these values is done in the following way: ...20 18 Value range and Default value changed in BR8.In order to achieve a suitable accuracy of the RXQUAL average value for AMR calls. this parameter represents the uplink quality threshold used to trigger an intracell AMR Compression Handover "fullrate to halfrate”.30. this parameter represents the downlink quality threshold (as C/I value in dB) used to trigger an intracell AMR Decompression Handover "halfrate to fullrate". .20 13 Value range and Default value changed in BR8.7) in the MEASUREMENT REPORT messages. . The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). the AMR mobile reports the downlink quality values of the serving cell in form of the RXQUAL values (0..0! Handover threshold AMR compression uplink. From BR7.HOTHAMRCUL=18. Notes: . For further important details please refer to the description of HOTHAMRCUL (see above)! Handover threshold AMR decompression downlink.Although the total value range of HOTHAMRCDL is 0. Attention: Like for other AMR quality handover parameters (such as HOLTHQAMRDL). The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). Important: In contrast to the intracell AMR compression handover (see parameter HOTHAMRCDL).From the received RXQUAL values the BTS builds the arithmetic mean in accordance with the averaging parameters determined by the parameter HOAVQUAL. it is recommended to use a minimum RXQUAL averaging window size of 4 (see parameter HOAVQUAL).

this parameter is only relevant if the feature ‘advanced AMR compression / decompression handover’ (parameter EADVCMPDCMHO. 327 .63 <NULL> initial value: 40 (-70dBm) HOTHCMPLVUL=<NULL>. see above) is enabled and defines the compression threshold for the UL receive level. From BR7. Handover threshold for compression uplink.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). the Intracell AMR decompression handover "halfrate to fullrate" is triggered if either the UL quality drops below the threshold HOTHAMRDDL or the DL quality drops below the threshold HOTHAMRDUL.63 <NULL> initial value: 40 (-70dBm) Handover threshold AMR decompression uplink.. in order for a compression from FR to HR to be triggered the condition DL_RXLEV > HOTHCMPLVDL must be fulfilled (as well as the respective condition for the UL and the quality conditions). object: unit: range: default: HAND [BASICS] 1 dB 0.0! HOTHCMPLVDL=<NULL>. The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above).HOTHAMRDUL=13.e. this parameter represents the uplink quality threshold (as C/I value in dB) used to trigger an intracell AMR Decompression Handover "halfrate to fullrate". object: unit: range: default: HAND [BASICS] 1 dB 0. in order for a compression from FR to HR to be triggered the condition UL_RXLEV > HOTHCMPLVUL must be fulfilled (as well as the respective condition for the DL and the quality conditions). Important: In contrast to the intracell AMR compression handover.. Please note that From BR7.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions.e... object: unit: range: default: HAND [BASICS] 1 dB 0. Please note that From BR7. i. see above) is enabled and defines the compression threshold for the DL receive level. this parameter is only relevant if the feature ‘advanced AMR compression / decompression handover’ (parameter EADVCMPDCMHO.. For further important details please refer to the description of HOTHAMRDDL (see above)! Handover threshold for compression downlink. i.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions..20 13 Value range and Default value changed in BR8.

A change of the attribute becomes effective in the next SACCH multiframe. this parameter is used for detecting a compression Handover "Enhanced Fullrate to Halfrate" in order to use the resources more efficiently. object: unit: range: default: HAND [BASICS] 1 dB 0. HOTHEFRCUL) and UL.. see above).. 328 . Handover threshold for decompression uplink..e.and DL-level (HOTHCMPLVDL.and DL-quality (HOTHEFRCDL. object: unit: range: default: HAND [BASICS] 1 dB 0.63 <NULL> initial value: 26 (-84Bm) HOTHEFRCDL=18. HOTHCMPLVUL) signal a possible compression and if the respective call was selected as best suitable within the cell (EADVCMPHOSC and ADVCMPHOOAMR). The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above).and DL-quality (HOTHEFRCDL. For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below.20 18 HOTHEFRCUL=18. this parameter is used for detecting a compression Handover "Enhanced Fullrate to Halfrate" in order to use the resources more efficiently. Handover threshold EFR compression downlink. HOTHCMPLVUL) signal a possible compression and if the respective call was selected as best suitable within the cell (EADVCMPHOSC and ADVCMPHOOAMR). The handover EFR HR is triggered only if the advanced compression / decompression algorithm is enabled (EADVCMPDCMHO. all condition checks for UL...0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. A change of the attribute becomes effective in the next SACCH multiframe... HOTHEFRCUL) and UL. this parameter is only relevant if the feature ‘advanced AMR compression / decompression handover’ (parameter EADVCMPDCMHO.0 on the AMR compression and decompression handover decision can be based on both quality and level conditions. object: unit: range: default: HAND [BASICS] 1 dB 0. Please note that from BR7. For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below. this parameter is only relevant if the feature ‘advanced AMR compression / decompression handover’ (parameter EADVCMPDCMHO.HOTHDCMLVDL=<NULL>.63 <NULL> initial value: 26 (-84Bm) HOTHDCMLVUL=<NULL>. see above). in order for a decompression from HR to FR to be triggered the condition DL_RXLEV < HOTHDCMLVDL must be fulfilled (together with defined DL quality conditions).and DL-level (HOTHCMPLVDL. The exact conditions for the initiation of an AMR compression and decompression handover as well as references to the quality related parameters are contained in the description for the parameter EADVCMPDCMHO (see above). all condition checks for UL. i. see above) is enabled and defines the decompression threshold for the UL level. Please note that From BR7.e. in order for a decompression from HR to FR to be triggered the condition UL_RXLEV < HOTHDCMLVUL must be fulfilled (together with defined UL quality conditions).. see above) is enabled and defines the decompression threshold for the DL level.20 18 Handover threshold for decompression downlink. Handover threshold EFR compression uplink. object: unit: range: default: HAND [BASICS] 1 dB 0. i. The handover EFR HR is triggered only if the advanced compression / decompression algorithm is enabled (EADVCMPDCMHO.

20 13 Handover threshold FR compression downlink. object: unit: range: default: HAND [BASICS] 1 dB 0. Handover threshold FR decompression downlink. FRACTTHR2) and the respective call was selected as best suitable within the cell (HRDCMLIMTH). HOTHFRCUL) and UL.20 18 HOTHHRDDL =13. see above). If the MS is not capable of EFR or EFR is not possible in the target cell then a HO HR to FR shall be executed. The handover HR (E)FR is triggered if the advanced compression / decompression algorithm is enabled (EADVCMPDCMHO.HOTHFRCDL=18. all condition checks for UL.20 18 HOTHFRCUL=18. this parameter is used attribute is used for detecting a decompression Handover "Halfrate to (Enhanced) Fullrate" in order to provide better speech quality. For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below. For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below.and DL-level (HOTHDCMLVDL.. this parameter is used for detecting a compression Handover "Fullrate to Halfrate" in order to use the resources more efficiently. and either any of the condition checks for UL.and DL-quality (HOTHHRDDL. Note: A decompression HO of HR to EFR is preferred.. this parameter is used for detecting a compression Handover "Fullrate to Halfrate" in order to use the resources more efficiently. see above). HOTHDCMLVUL) signal a necessary decompression (For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below) or a low load condition exists (FRACTTHR1. A change of the attribute becomes effective in the next SACCH multiframe.and DL-quality (HOTHFRCDL. object: unit: range: default: HAND [BASICS] 1 dB 0. all condition checks for UL. HOTHCMPLVUL) signal a possible compression and if the respective call was selected as best suitable within the cell (EADVCMPHOSC and ADVCMPHOOAMR).and DLlevel (HOTHCMPLVDL. A change of the attribute becomes effective in the next SACCH multiframe. A change of the attribute becomes effective in the next SACCH multiframe.. HOTHFRCUL) and UL.. 329 . object: unit: range: default: HAND [BASICS] 1 dB 0. HOTHHRDUL) and UL. Handover threshold FR compression uplink. The handover FR HR is triggered only if the advanced compression/decompression algorithm is enabled (EADVCMPDCMHO.. see above).and DL-quality (HOTHFRCDL.and DLlevel (HOTHCMPLVDL. HOTHCMPLVUL) signal a possible compression and if the respective call was selected as best suitable within the cell (EADVCMPHOSC and ADVCMPHOOAMR).. The handover FR HR is triggered only if the advanced compression/decompression algorithm is enabled (EADVCMPDCMHO.

63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm . Note: A decompression HO of HR to EFR is preferred. If the BS-BTS distance exceeds this threshold an inter-cell handover due to distance is executed. the following rule must be fulfilled: UPTLEVU > HOTULINT For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document. Rule: HOMSTAM (HAND) < HOTMSRME < EXCDIST (BTS [OPTIONS]) Handover threshold level uplink intra. defines the threshold for the maximum permitted distance between MS and the BTS in 1km step size which is used for intercell handover due to distance. The BTS calculates the distance between MS and BTS from the delay of the RACH burst (which is used for the CHANNEL REQUEST and the HANDOVER ACCESS) and the the delay of the normal bursts. To guarantee a correct interworking of power control and intracell handover. 62 = -48dBm 63 = greater than -48dBm default: 35 Reference: GSM 05. The handover HR (E)FR is triggered if the advanced compression / decompression algorithm is enabled (EADVCMPDCMHO.. this parameter defines the receive signal level threshold in the uplink for the quality intra-cell handover decision. object: unit: range: default: HAND [BASICS] 1km 35-100 99 HOTULINT=35.and DL-quality (HOTHHRDDL. If the determined distance exceeds the entered threshold value an inter-cell handover with cause ‘distance’ is initiated. HOTHHRDUL) and UL. FRACTTHR2) and the respective call was selected as best suitable within the cell (HRDCMLIMTH).and DL-level (HOTHDCMLVDL.. see above). and either any of the condition checks for UL. In case of an extended channel (double timeslot of an extended cell. Rule: HOTMSRM (HAND) < EXCDIST (BTS [OPTIONS]) Handover threshold MS range maximum extended.35 34 3GPP 45. It is only relevant if intracell handover due to quality is enabled (INTRACH=TRUE.08 Handover threshold FR decompression uplink. see CELLTYPE=EXTCELL in CREATE BTS [BASICS]) the handover threshold MS range maximum is determined by the parameter HOTMSRME (HAND).. If the MS is not capable of EFR or EFR is not possible in the target cell then a HO HR to FR shall be executed. It is only relevant if distance handover is enabled (DISTHO=TRUE.HOTHHRDUL =13. see below) and defines the receive signal level threshold on the uplink for intra-cell handover decision. A change of the attribute becomes effective in the next SACCH multiframe. Handover threshold MS range maximum.20 13 HOTMSRM=34. It is only relevant if intercell handover due to distance is enabled (DISTHO=TRUE. HOTHDCMLVUL) signal a necessary decompression (For the mentioned parameters please refer to descriptions provided in this command (SET HAND [BASICS] above or below) or a low load condition exists (FRACTTHR1. The actual threshold value in [dBm] is calculated as follows: Handover Threshold [dBm] = -110dBm + HOTULINT .. this parameter replaces the parameter HOTMSRM (see above) in case of an extended channel (double timeslot of an extended cell. object: unit: range: HAND [BASICS] 1 dB 0. object: unit: range: default: HAND [BASICS] 1 dB 0. see CELLTYPE=EXTCELL in CREATE BTS [BASICS]). see above) and specifies the handover threshold range maximum that is used for intercell handover due to distance in extended cells..008 HOTMSRME=99. 330 .. this parameter is used attribute is used for detecting a decompression Handover "Halfrate to (Enhanced) Fullrate" in order to provide better speech quality. see above). object: unit: range: default: Reference: HAND [BASICS] 1km 0.

Only if this parameter is set to TRUE. FALSE FALSE Half Rate decompression limitation threshold. SDCCH-SDCCH handover to target cells belonging to the same BSC. i. RXLEVHO. C/I + PL – HOTHxxDyy < HRDCMLIMTH A change of the attribute becomes effective in the next SACCH multiframe. . Notes: Decompression handovers due to bad radio conditions are not affected by this attribute. this parameter determines whether inter-cell SDCCH-SDCCH handover is enabled or not.100 (dB) 6 (dB) IERCHOSDCCH=FALSE. Under low load conditions a call might be selected for a decompression handover HR/AHR (E)FR/AFR. For the relevant parameters HOTHAMRCDL.HRDCMLIMTH=6. object: range: default: HAND [BASICS] TRUE.e. If Inter-BSC Directed Retry shall be enabled the flag EISDCCHHO (see SET BSC [BASICS]) has to be set to ENABLE in addition. see above) and is used to limit the number of decompression handovers due to low load conditions to those of low quality. this parameter is only relevant if the advanced compression / decompression algorithm is enabled (EADVCMPDCMHO. Inter-cell handover for SDCCH. DISTHO. i. the settings of the flags RXQUALHO. Notes: . HOTHHRCDL and HOTHHRCUL please see descriptions above.e. These flags determine which kinds of SDCCH-SDCCH inter-cell Handover are actually allowed. PBGTHO. 331 . if the sum of its C/I and the power reduction level (PL) minus the threshold HOTHxxCyy (xx=HR or AMR.. object: unit: range: default: HAND [BASICS] 1 dB 0.Setting this parameter to ‘enable’ only activates the SDCCHSDCCH handover controlled by the BSC.. yy=DL or UL) is below this attributes value. ININHO and EFULHO are considered for SDCCH handover. HOTHAMRCDL.

the level threshold HORXLVDLO (see above) of the affected target cell. 332 . sector 1 (own cell) inner-toinner sector 2 (colocated cell 1) sector 3 (colocated cell 2) inner area complete area Default value changed in BR8. FALSE TRUE Inner-inner handover. the BSC sends a PREFERRED AREA REQUEST message to the originating BTS which contains. If the BTS suggests an inner area TCH in the PREFERRED AREA message. This parameter is only relevant in concentric cells (see parameter CONCELL in command CREATE BTS [BASICS]. the BSC directly activates the target TCH on an inner area TRX (if available) and sends the corresponding TCH info to the MS in the HANDOVER COMMAND. Which cells are to be considered as 'colocated' (i. even if the level and distance conditions allow an assignment of a TCH belonging to the inner area of the target cell. with ININHO=FALSE) any incoming handover to a concentric cell is always executed to a TCH belonging to the complete area.0! Under normal conditions (i. this flag determines whether an intercell handover from inner to inner area in sectorized concentric cells is enabled. the BSC will start the PREFERRED AREA REQUEST procedure towards the originating cell when an intercell handover is triggered. but also handovers from the complete area in the originating sector to the inner area of the target sector. The enabling of the flag ININHO simply activates the PREFERRED AREA REQUEST procedure (towards the originating cell) for all intercell handovers for the neighbour cell relations defined by CCELL1 and CCELL2. If the return message PREFERRED AREA message suggests the inner area. Principle: If the BTS triggers an inter-cell handover out of a concentric cell towards a target cell which the BSC recognizes as 'colocated' (see parameters CCELL1 and CCELL2). when ININHO is set to TRUE. the handover is performed to a corresponding inner area TRX in the target cell.e. not only inner-to-inner handovers are possible. This means that only in this case the BSC will start the PREFERRED AREA REQUEST procedure during intre-cell handover. In this case the inter-cell handover to the complete area of the target cell is directly followed by a complete-to-inner intracell handover within the target cell. for which neighbour cells the ININHO flag will be in effect) is determined by the parameters CCELL1 and CCELL2 (see above).e. If ININHO is set to TRUE these unnecessary handovers are avoided between colocated concentric cells as described below. In fact. Note: The BSC only allows the ‘to-inner’ handover if both the originating and target cell of a handover procedure are configured as concentric cells (CONCELL=TRUE in command CREATE BTS [BASICS]).ININHO=TRUE. Based on this threshold and the measured RXLEV value of the target cell the BTS answers with a PREFERRED AREA message which suggests either a 'complete' area TCH or an 'inner' area TCH. Even if the call is currently served by a complete area TRX in the serving cell. among other parameters. This means that it is up to the operator to enter only object path names of BTS instances that are really configured correspondingly. object: range: default: HAND [BASICS] TRUE.

EFULHO and TRFHOE considered for TCH handover. a double one is selected). object: range: default: HAND [BASICS] TRUE. HSCSD calls might be downgraded from 14.INTERCH=TRUE. Further parameters relevant for this type of handover are HOAVQUAL. Internal intra-cell Handover enabled. If INTRACH is set to FALSE the quality conditions which normally cause an intra-cell ‘quality’ handover in the first place directly lead to an inter-cell ‘quality’ handover (provided that RXQUALHO is set to TRUE).Only if this parameter is set to TRUE.To avoid a ping-pong handover from HR to FR and vice versa. This means that the BSC does not check the current BTS TCH load and the BTSM Abis pool TCH load in case of an intracell handover due to quality. . PBGTHO.If an extended cell (CREATE BTS [BASICS]:CELLTYPE=EXTCELL) is the target of an inter-cell HO the handover will always take place to a 'double' timeslot first as the BTS can only determine the actual MS-BTS distance when the first MS messages are received. . HOTDLINT and HOTULINT. see above) and intracell handover due to quality (for a call whose quality is still poor after decompression handover). under defined quality and level conditions (see section handover algorithms) the handover algorithm always executes intra-cell ‘quality’ handovers before Inter-cell ‘quality’ handovers are attempted. Notes: . HOs starting from a TCH) are generally allowed for this BTS. If this is the case. If the MS-BTS distance turns out to be short enough for a 'single' timeslot an intra-cell handover from far to near ('double-to-single') is executed immediately (if enabled). 333 . determines whether intra-cell handovers due to quality shall be allowed this BTS.The intracell handover selects the available TCHs cyclically or based on the idle TCH measurements (if SET BTS [INTERF]: INTCLASS=TRUE. RXLEVHO. FALSE TRUE Internal inter-cell Handover enabled. These Intra-cell handovers are independent of the status of RXQUALHO. . determines whether inter-cell handovers for TCH (i. the settings of the flags RXQUALHO. Notes: . These flags determine which kinds of TCH-TCH inter-cell Handover are actually allowed.For HSCSD calls the intracell HO due to quality is not performed. . object: range: default: HAND [BASICS] TRUE. irrespective of the status of the INTRACH flag.In an extended cell the intra-cell handover due to quality may only take place from double to double ts or from single to single ts (exception: if no single TCH is available. which can occur due to subsequent execution of (AMR) decompression handover (parameter EADVCMPDCMHO. ININHO. the features ‘Cell load dependent actvation of half rate’ (see parameter EHRACT in command CREATE BTS [BASICS]) and ‘Abis load dependent activation of half rate’ (see parameter ABISHRACTTHR in command CREATE BTSM) are not considered if the BSC receives an INTRACELL HANDOVER CONDITION INDICATION due to quality reasons (cause values ‘uplink quality’ or ‘downlink quality’).6kbit/s (see parameters in command SET HAND [DATA]). DISTHO. FALSE TRUE INTRACH=TRUE.e.4 kbit/s to 9. which only refers to inter-cell handovers.) in the scope of the intra-cell HO limitation functions set (see parameter ELIMITCH). In case of bad quality.In a concentric cell (CREATE BTS [BASICS]:CONCELL=TRUE) the intracell handover (quality) may only take place within the complete area or within the inner area! .

IRACHOSDCCH=FALSE,
object: range: default: HAND [BASICS] TRUE, FALSE FALSE

Intra-cell handover for SDCCH, this parameter determines whether intra-cell handover due to quality is enabled for SDCCH-SDCCHhandovers or not. Local inter-cell Handover enabled, determines whether inter-cell handover is controlled by the BSC (TRUE) or MSC (FALSE). If the flag is set to FALSE, and the BSC receives an INTERCELL HANDOVER CONDITION INDICATION (BWHCI) from the BTS, the BSC forwards the handover responsibility to the MSC by sending a HANDOVER REQUIRED to the MSC, even if the first target cell in the target cell list of the BWHCI is an internal one. Notes: - This flag is valid both for TCH-TCH handover and SDCCH-SDCCH handover! - The setting of this parameter has an impact on performance measurement: It must be set to TRUE to ensure the correct working of specific counters related to inter-cell handover (ATINHIRC, SINTHINT). Local intra-cell Handover enabled, determines whether intra-cell handover is controlled by the BSC (TRUE) or MSC (FALSE). If the flag is set to FALSE, and the BSC receives an INTRACELL HANDOVER CONDITION INDICATION (WIHCI) from the BTS, the BSC forwards the handover responsibility to the MSC by sending a HANDOVER REQUIRED to the MSC, indicating the serving cell as the only target cell. Notes: - This flag is valid both for TCH handover and SDCCH-SDCCH handover. - If the BTS is a concentric cell (CREATE BTS [BASICS]: CONCELL=TRUE) or an extended cell (CREATE BTS [BASICS]: CELLTYPE=EXTCELL) the setting of LOTRACH is ignored. Intracell handover (quality) is in this case always BSC-controlled! - If LOTRACH is set to FALSE the BSC automatically adds the serving cell to neighbour cell description IE (BA-list) in the SYSTEM INFORMATION TYPE 5. - For a correct working of performance measurement counters (ATINHIAC, SINTHITA) for intracell handovers LOTRACH must be set to TRUE! Maximum number of intra-cell handovers, this parameter is only considered if the flag ELIMITCH (see above) is set to TRUE. It determines the maximum number of consecutive successful intracell handovers due to quality (parameter INTRACH, see above) or intracell handovers due to compression (parameter EADVCMPDCMHO, see above) that are permitted in the same BTS for a single connection. In the BSC, two separate counters are managed: - The first counter monitors the number of consecutive intracell quality handovers. It is increased by ‘1’ whenever the BSC receives an ASSIGNMENT COMPLETE after having sent an CHANNEL ACTIVATION / ASSIGNMENT COMMAND for a quality intracell handover to the BTS). - The second counter monitors the number of consecutive compressio-decompression back-and-forth handovers. This counter is increased by ‘1’ after receipt of the last ASSIGNMENT COMPLETE of a back-and-forth compression-decompression handover (i.e. FR>HR->FR). MAIRACHO determines the common threshold value for both counters - however, both counters are managed separately and indepenently and lead to independent signalling of handover

LOTERCH=TRUE,
object: range: default: HAND [BASICS] TRUE, FALSE TRUE

LOTRACH=TRUE,
object: range: default: HAND [BASICS] TRUE, FALSE TRUE

MAIRACHO=2,
object: range: default: HAND [BASICS] 1-15 2

334

MAXFAILHO=2,
object: range: default: HAND [BASICS] 1-15 2

suppression towards the BTS. In other words: the BSC may a) send a CHAN ACT with cause ‘handover successful’ to the BTS (when the quality intracell handover counter has reached the MAIRACHO threshold) for one quality intracell handover (leading to a suppression of only quality intracell handover for the time defined by TINOIERCHO - as long as the call remains on that channel) and b) may also add the cause ‘handover successful’ also to the subsequent CHAN ACT to the BTS, if an INTRACELL HANDOVER CONDITION INDICATION with cause ‘decompression’ was received and MAIRACHO was additionally reached for the compressiondecompression handover counter in the BSC. This will then lead to a suppression of only compression intracell handovers for the time defined by TINOIERCHO - as long as the call remains on that channel. Intracell quality handovers are not suppressed by the BTs at this stage. Any kind of successful intracell handover or intercell handover with a cause different from intracell quality of compression-decompression on the same connection resets the counters. Note: Due to the feature implementation actually the maximum allowed number of consecutive successful intra-cell handovers is MAIRACHO+1. Maximum number of failed handovers, this parameter is only relevant if the parameter NOFREPHO is set to TRUE and determines the maximum number of consecutive failures of intra BSC handovers that are permitted in the same BTS for a single connection.

335

NCELL=6,
object: range: default: Reference: HAND [BASICS] 0..15 6 GSM 08.08 (for HANDOVER REQUIRED)

NOBAKHO=TRUE,
object: range: default: HAND [BASICS] TRUE, FALSE TRUE

NOFREPHO=TRUE,
object: range: default: HAND [BASICS] TRUE, FALSE TRUE

PBGTHO=TRUE,
object: range: default: Reference: HAND [BASICS] TRUE, FALSE TRUE 3GPP 45.008

Number of preferred cells, defines the number of preferred cells in the HANDOVER CONDITION INDICATION message. This message is a result of the handover measurement pre-processing function in the BTS and is sent periodically from the BTS towards the BSC (see parameter THORQST). The handover measurement pre-processing function evaluates the measurement reports received from the MS in order to determine whether a handover is necessary and - if yes which neighbour cells are suitable target cells. These cells are then inserted into the target cell list of the HCI. If the BSC does not execute the handover itself it sends the message HANDOVER REQUIRED towards the MSC. No back handover, this flag determines whether the feature 'Prevention of Back handovers' is enabled or not. It enables a mechanism that prevents a back-handovers due to power budget if the TCH in the serving cell was seized by an imperative handover procedure (handover due to level, quality or distance). If the flag NOBAKHO is set to TRUE the back-handovers are prevented by the following mechanism: if an imperative handover (to a cell for which NOBAKHO=TRUE) is performed the BSC extends the CHANNEL ACTIVATION message for the 'new' TCH in the target cell by the IE 'Cell List Preferred' which contains the CGI of the handover origin cell and by a GSM 08.08 cause IE with the cause 'distance'. This message makes the BTS suppress the handover origin cell in all following INTERCELL HANDOVER CONDITION INDICATION messages sent with the cause 'better cell' for an administrable time period (see parameter TINHBAKHO (CREATE ADJC)). Note: The flag NOBAKHO is relevant for the handover target cell, i.e. the CHAN ACT message is extended by the above mentioned IEs if the BSC detects that for the handover target cell the flag NOBAKHO is set to TRUE. The BTS then retrieves the TINHBAKHO value from the adjacent cell object that represents the handover origin cell from point of view of the handover target cell. No handover failures repetition, this flag determines whether the feature 'Prevention of handover failures repetition' is enabled or not. It enables a mechanism which prevents unlimited handover repetitions to a target cells if previously handovers to this cell have not been successful. A handover is regarded as unsuccessful if the MS returns to the old channel with a HANDOVER FAILURE message or if in case of an external handover the timer T7 expires (e.g. due to receipt of a HANDOVER REQUIRED REJECT message). If the flag NOFREPHO is set to TRUE every unsuccessful handover leads to the increase of a counter in the BSC. If this counter reaches an administrable threshold (see parameter MAXFAILHO) the BSC sends a HANDOVER FAILURE INDICATION message to the BTS which contains the CGI of the target cell to which the handover attempts failed. As a result, the BTS excludes the affected cell from the target cell list of the HANDOVER CONDITION INDICATION messages for an administrable period of time (see parameter TINHFAIHO (CREATE ADJC)). Power budget handover enabled, determines whether handover due to power budget is enabled. This flag is only relevant if intercell handover is enabled in the cell (INTERCH=TRUE, see above). Power budget handover means: handover to another cell if this cell offers a higher transmission level (irrespective of whether the power level of the actual cell is above the minimum - see RXLEVHO - or not.). Further parameters relevant for this type of handover are HOAVPWRB (HAND object, see above) and HOM (ADJC object). Note: this flag only determines whether inter-cell handovers may be executed with cause ‘better cell’.

336

PL=0,

Priority layer, if hierarchical cell handover is enabled (HIERC=TRUE) this parameter determines the priority layer of the object: HAND [BASICS] own cell. This priority is only evaluated for the Power Budget range: 0..15 handover decision and the traffic handover decision (see parameter default: 0 TRFKPRI). The priority layers of the neighbour cells are administered in the ADJC object (see ADJC object). RxLevel handover enabled, determines whether handover due to RXLEVHO=TRUE, low receive level on uplink or downlink is enabled. This flag is only relevant if intercell handover is enabled in the cell (INTERCH=TRUE, object: HAND [BASICS] range: TRUE, FALSE see above). If the receive level is below the minimum threshold default: TRUE handover is necessary. Further parameters relevant for this type of Reference: 3GPP 45.008 handover are HOAVLEV, HOLTHLVDL and HOLTHLVUL (see above). Note: this flag only determines whether inter-cell handovers may be executed with cause ‘level’. RxQual handover enabled, determines whether handover due to RXQUALHO=TRUE, bad receive quality on uplink or downlink is enabled. This flag is only relevant if intercell handover is enabled in the cell (INTERCH=TRUE, object: HAND [BASICS] range: TRUE, FALSE see above). Bad receive Quality is determined by error rate default: TRUE measurements in the MS and the BTS. Further parameters relevant Reference: 3GPP 45.008 for this type of handover are HOAVQUAL, HOLTHQUDL and HOLTHLQUUL, HOLTHQAMRDL and HOLTHQAMRUL (see above). Note: this flag only determines whether inter-cell handovers may be executed with cause ‘quality’. SG1HOPAR=<NULL>, Service group 1 handover parameters, this parameter is the first of the 14 parameters which allows a service group-dependent setting of object: HAND [BASICS] handover parameters and thresholds. range: <NULL>, The setting <NULL> indicates that for this service group no specific 8 fields with ranges in parameter settings are applied and the handover decision for this correspomdemce with the PWRC parameters they service group is based the ordinary HAND parameter settings. represent. Fo further details please refer to the section “Service dependent default: <NULL> Handover and Power Control in the appendix of this document. SG2HOPAR...SG14HOPAR=< Service group 2..14 handover parameters, these parameters represent the remaining 13 parameters which allow a service groupNULL>, dependent setting of handover parameters and thresholds. object: HAND [BASICS] The setting <NULL> indicates that for the affected service group no range: <NULL>, specific parameter settings are applied and the handover decision for n fields with ranges in this service group is based the ordinary HAND parameter settings. correspomdemce with the PWRC parameters they Fo further details please refer to the section “Service dependent represent. Handover and Power Control” in the appendix of this document. default: <NULL> THLEVFULHO=8,
object: unit: range: HAND [BASICS] 1 dB 0..63 0 = less than -110dBm 1 = -110dBm 2 = -109dBm ... 62 = -48dBm 63 = greater than -48dBm 8

Level threshold for fast uplink handover, this parameters defines the uplink receive signal strength threshold for an inter-cell fast uplink handover (see parameter EFULHO). If the UL RXLEV drops below the level defined by THLEVFULHO, the BTS triggers a fast uplink handover. For further details please refer to the section ‘Handover Thresholds and Algorithms’ in the appendix of this document.

default:

337

THORQST=8,
object: unit: range: default: Reference: HAND [BASICS] 2 SACCH multiframes 0..31 5 3GPP 45.008

Timer for handover request defines the minimum interval between HANDOVER CONDITION INDICATION messages (see parameter NCELL) related to the same connection. If the BSC cannot execute the handover itself it sends a HANDOVER REQUIRED message towards the MSC. Like the HCI the HANDOVER REQUIRED message also contains a target cell list and a handover cause (e.g. ‘uplink quality’, ‘better cell’ etc.) and is repeated under consideration of the timer T7 (see SET BSC SET BSC [TIMER], parameter BSCT7).
THORQST purpose: Minimum time between two HO_COND_IND messages related to the same connection start: sending of HO_COND_IND message by the BTS stop: - receipt of a HANDOVER COMMAND from the MSC - no further HO_COND_INDs received from the BTS - communication to MS is lost - transaction has ended, call cleared expiry action: repetition of the HO_COND_IND message is permitted

TINOIERCHO=60,
object: unit: range: default: HAND [BASICS] 1s 1-254 60

Recommendation: THORQST (HAND) > T7 (SET BSC [TIMER]) Note: If THORQST is set to 0 then the HCI is repeated after every SACCH multiframe, i.e. every 480ms. If the call remains on the same TCH this might lead to a 'toggling' of inter- and intra-cell HCIs. Timer for 'no intra-cell handover', this parameter is only considered if the flag ELIMITCH (see SET HAND [BASICS]) is set to TRUE. It specifies the timer used by the BTS to indicate how long a) quality intra-cell handover (see parameter INTRACH in command SET HAND [BASICS]) or b) AMR compression handover (see parameter EADVCMPDCMHO in command SET HAND [BASICS]) shall be prevented for a specific connection in the cell if MAIRACHO+1 successful handovers of that particular types have taken place before. The timer is started in the BTS on receipt of the adapted CHANNEL ACTIVATION message which contains an additional GSM 08.08. cause 'handover successful'. The only event that can stop this timer is the release of the call context (e.g. call release or inter-cell handover).

338

TRFHITH=90,
object: unit: range: default: HAND [BASICS] 1% 50..100 90

Traffic handover high threshold, this parameter specifies the cell traffic load that leads to the enabling of traffic handover in the BTS. The traffic load of a cell is calculated as follows:
Cell traffic load [%] = no. of TCH* in usage state ‘busy’** no. of TCH in state unlocked/enabled ∗ 100

Attention: - Generally a TCH\F is counted as 2, a TCH\H is counted as 1! - (*) A dual rate TCH (TCHF_HLF) in usage state „busy“ (i.e. both HR subslots busy) is counted as 2 while a dual rate TCH in usage state „active“ (i.e. only on HR subslot busy) is counted as 1. - (**) The GPRS downgrade strategy (see parameter DGRSTRGY in command SET BTS [BASICS]) has an influence on the radio TCH traffic load calculation if the parameter DGRSTRGYBCNT is set to ENABLED (for further details please refer to parameter DGRSTRGYBCNT in command SET BSC [BASICS]). a) If DGRSTRGY indicates ‘GPRS downgrade not allowed’ (i.e. DOWNGRADE_HSCSD_ONLY or NO_DOWNGRADE), then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘busy’ like any other TCH which is currently seized by a CS call. b) If DGRSTRGY indicates ‘GPRS downgrade allowed’ (i.e. DOWNGRADE_GPRS_ONLY, DOWNGRADE_GPRS_FIRST or DOWNGRADE_HSCSD_FIRST, then all (non-reserved) TCHs which are currently busy due to GPRS traffic (PDCH) are considered as ‘idle’. - If the timer TEMPCH (see command CREATE PCU) is running for a particular TCH/PDCH, this TCH is regarded as ‘idle’ in any case, no matter which values is set for the DGRSTRGY parameter, as these TCHs are in any case immediately preempted if a CS TCH request meets a TCH congestion situation. - TCHs indicated as ‘reserved for GPRS’ (see parameter GMANPRESPRM in the PTPPKF object) are not considered in the calculation, i.e. they are treated as if they were not configured! Thus, reserved GPRS TCHs in state ‘GPRS busy’ are not considered (value above the fraction bar) and the value below the fraction bar is the number of TCHs in ‘unlocked/enabled’ minus the TCHs reserved for GPRS in the same state. - If a GPRS call utilizes more TCHs than configured as ‘reserved’ by GMANPRESPRM, the currently used but ‘not reserved’ TCHs (‘idle/shared’ TCHs) are considered in correspondence with the setting of DGRSTRGY as indicated above.

The BSC cyclically checks the traffic load (controlled by the timer TRFCT, see SET BSC) in all cells in which traffic handover is enabled (see parameter TRFHOE) and compares it to the threshold specified by TRFHITH. If the traffic load in the cell is above the cellspecific threshold TRFHITH, the BSC enables the traffic handover in the affected BTS by sending an LAPD O&M message SET ATTRIBUTE with the appropriate contents to the BTSM. This O&M message is the trigger for the BTS to start the traffic handover decision algorithm (for more details concerning the handover decision please refer to the appendix ‚Handover Thresholds and Algorithms’). If the traffic handover was already enabled for a specific BTS on the previous expiry of TRFCT and the traffic load in the affected BTS is still above the threshold TRFHITH, no further message is sent to the BTS and the traffic handover remains enabled in the affected BTS. If the traffic handover was enabled for a specific BTS on the previous expiry of TRFCT and the traffic load in the affected BTS has decreased below the threshold TRFHITH, the BSC disables the traffic handover in the affected BTS by sending another LAPD O&M message SET ATTRIBUTE with the appropriate contents to the BTSM.

339

TRFHOE=TRUE,
object: range: default: HAND [BASICS] TRUE, FALSE FALSE

Traffic handover enabled, this parameter enables the feature ‘Handover due to BSS resource management criteria’ or shortly called ‘traffic handover’. If this flag is enabled, the BSC cyclically checks the traffic load situation of this cell. If the traffic load exceeds the threshold TRFHITH, the BSC enables the traffic handover in the BTS by sending SET ATTRIBUTE message with the ‘traffic handover enabled’ indication to the BTS via the LPDLM link. As a result, the BTS starts its handover decision process in such a way that it continuously evaluates the DL MEASUREMENT REPORTS for suitable neighbour cells for traffic handover. Similar to the power budget handover decision process the traffic handover decision process monitors the level difference between the serving cell and the neighbour cells and compares it to an administrable handover margin (traffic handover margin, see explanations for TRFHOT): when the power budget exceeds the traffic handover margin, a handover due to traffic is initiated by sending a corresponding INTERCELL HANDOVER CONDITION INDICATION with the proprietary cause ‘traffic’. Differences to the normal power budget handover decision consist in the following aspects a) While the power budget handover decision process is continuously running in the BTS if the database flag PBGTHO is set to TRUE, the traffic handover decision process only runs in those time periods where the traffic handover was explicitly enabled by the mentioned SATT message from the BSC before. b) While the power budget handover margin has a static value, the traffic handover margin is dynamically changed (reduced or increased) by a timer-controlled step-by-step reduction mechanism (see TRFHOT). When the BSC receives the INTERCELL HANDOVER CONDITION INDICATION (BWHCI) with the proprietary cause ‘traffic’, it checks the current TCH load of the target cells indicated in the BWHCI. Only if the current TCH load of the suggested target cell is lower than a configurable threshold (see TRFLTH), the handover to this target cell is actually executed. Traffic Handover can only take place within the BSC as - only for these cells the target cell traffic condition can be checked - the cause value ‘traffic’ is not defined for the A-interface signalling. This means that the Parameters relevant