br10 database engineering manual

GERAN-S Database Parameter Planning & Engineering Manual BR10.0 Version 29.08.08 __________________________________________________________________________________________________________

GERAN SouthNetwork Engineering BSC Database Engineering Manual BR10 and BR 10.01 August 2008

Authors: Eckardt Bertermann, (up to BR9.0)

Krystian Majchrowicz (BR10.0) Nokia Siemens Networks COO RA RD SA NE

1 / 744

Network Engineering GERAN

GERAN-S Database Parameter Planning & Engineering Manual BR10.0 and 10.01 Version 1.0 29.08.08 ______________________________________________________________________________________________________ ____

Trademarks: All designations used in this document can be trademarks, the use of which by third parties for their own purposes could violate the rights of their owners.

2 / 744



Reason for UpdateSummary: Document Issue for Release BR10.0. Details: Chapter/Section Reason for Update

Issue historyIssue Number 0.1 1.0 Date of Issue 2008 2008 Reason for Update First Document Issue for Release BR10.0 after NE internal review. Reviewed version, parameters grouping per release and feature added on

AuthorsIn addition to the author named on the cover page the following persons have collaborated on this document: Name Marcin Grygiel Piotr Grzybowski Krystian Krysmalski Sebastian Lasek Sebastian ysiak Andrzej Macioek Krystian Majchrowicz Dariusz Tomeczko Department COO RA MRD SA Network Engineering MAN COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL COO RA GERD SA Network Engineering PL

3 / 744



!IMPORTANT This document is not officially released to customers 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 may not be explicitly marked!

The documents 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 objects - 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 documents 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!

4 / 744



Contents:1 DATABASE BR10.0 ........................................................................................................................................ 11 1.1 BR10.0 OBJECT TREE OF FUNCTIONAL BSC DATABASE OBJECTS ............................................................... 11 1.2 BSC DATABASE COMMANDS AND PARAMETERS ................................................................................ 14 Setting the object entry point and time and date for the BSS: ..................................................................... 14 Setting the object entry for the BOF:........................................................................................................... 14 Setting the object entry for the RSUFW: .................................................................................................... 15 Setting the object entry for the RSUPCH: .................................................................................................. 16 Setting the object entry for the APD:........................................................................................................... 17 Creating the APM: ...................................................................................................................................... 17 Setting the BSC control values for periodic measurement data file upload:............................................... 18 Setting the timing values for BSSMAP control and BSC overload handling: ............................................. 22 Setting the global parameters of the BSC: .................................................................................................. 31 Creating new database parameters without info model change: ................................................................ 84 Setting the alarm priorities of the BSS functional objects:.......................................................................... 85 Setting the remote Inventory data of the BSC Equipment: .......................................................................... 90 Setting the alarm priorities of the BSCE objects:........................................................................................ 90 Creating the Power Supply: ........................................................................................................................ 93 Setting the alarm priorities of the EBSCE objects: ..................................................................................... 93 Defining the eBSC configuration: ............................................................................................................... 96 Setting the RELEBSCNE object entries (object introduced in BR10.0): ..................................................... 97 Creating the spare PCM interface boards: ................................................................................................. 98 Creating the PCM interface boards: ........................................................................................................... 98 Creating the common attributes for all PCUs belonging to the entire BSC:............................................... 99 Creating the PCU objects: ........................................................................................................................ 108 Creating the Network Service Entity (NSE): ............................................................................................. 109 Creating an SGSN Pool: ........................................................................................................................... 117 Creating the local NSE Virtual Link IP of an NS connection: .................................................................. 119 Creating the remote NSE Virtual Link IP:................................................................................................. 120 Creating the PCM links for the Abis interface: ......................................................................................... 121 Creating the PCMS link: ........................................................................................................................... 126 Creating the TRAU:................................................................................................................................... 129 Creating the ASUBCESTUNNEL (object shifted to BR11): ...................................................................... 134 Creating the ASUBCESPW (object shifted to BR11): ............................................................................... 136 Creating the LPDLS links: ........................................................................................................................ 138 Creating the PCMA link: ........................................................................................................................... 140 Setting the uplink and downlink volumes for specific PCMA timeslots:.................................................... 147 Creating the PCMG link: .......................................................................................................................... 148 Creating the physical link connection on the GPRS Gb interface (Frame Relay Link): .......................... 150 Creating the end-to-end communication between BSS and SGSN: Network Service Virtual Connection (NSVC): ..................................................................................................................................................... 151 Setting the object entry for the AFLEXPOOL: .......................................................................................... 152 Creating the ETH (object moved to BR11):............................................................................................... 154 Creating the ETHINTF (object moved to BR11): ...................................................................................... 155 Creating the BTS Site Manager: ............................................................................................................... 156 Creating the Common BTS data of a BTSM for Dynamic MAIO Allocation (DMA): ............................... 176 Creating the hopping laws used for Dynamic MAIO Allocation:.............................................................. 182 Creating the LPDLM links: ....................................................................................................................... 183 Creating the terrestrial Abis timeslots for flexible Abis allocation: .......................................................... 185 Creating ABISCESTUNNEL (object shifted to BR11):.............................................................................. 189 Creating ABISCESPW (object shifted to BR11):....................................................................................... 191 Creating a cell with definition of global parameters: ............................................................................... 194 Setting the cell specific parameters for DMA Admission Control ............................................................. 275 Setting the cell attributes for the Interference Measurement of idle TCHs: .............................................. 289 Setting the cell specific timer values: ........................................................................................................ 291 Setting the cell specific optional features:................................................................................................. 303 Defining the cell specific service layer lists for the feature 'Service dependent Channel Allocation' (SDCA) via 'Multi Service Layer Support' (MSLS):................................................................................................ 319

5 / 744



Setting the cell specific attributes for Power Control: .............................................................................. 332 Creating the GPRS point to point packet transfer service in a cell:.......................................................... 347 Creating the cell-specific Frequency Hopping systems for static MAIO Allocation (SMA):..................... 389 Creating the TRXs: .................................................................................................................................... 391 Enabling GPRS and EDGE in a cell:........................................................................................................ 396 Creating the BCCH for the cell: ................................................................................................................ 398 Creating the SDCCHs for the cell: ............................................................................................................ 399 Creating the TCHs for the cell: ................................................................................................................. 401 Creating hybrid TCHs/SDCCHs (TCH/SD) for the cell: ........................................................................... 404 Setting the cell specific parameters and threshold values for CS Handover:............................................ 410 Setting the cell specific parameters and threshold values for 14,4kbit/s data call up- and downgrading and quality inter-cell handover: ....................................................................................................................... 481 Enabling features related to ASCI, SMS-CB, Frequency Hopping, HSCSD, Call Release due to Excessive Distance and Dynamic MAIO Allocation (DMA):..................................................................................... 483 Creating the Target Cell Objects: ............................................................................................................. 489 Creating the Target Point-to-point Packet Flow Objects: ........................................................................ 492 Creating the Adjacent Cell Objects:.......................................................................................................... 494 Creating the Target Cell Objects for handover from GSM to UMTS (FDD): ........................................... 513 Creating the Target Cell Objects for handover from GSM to UMTS (TDD): ........................................... 514 Creating the Adjacent Cell Objects for external UMTS FDD or UMTS TDD cells:................................. 516 Creating the CCS7 level 3 address and basic SCCP parameters of the BSC............................................ 522 Creating the remote CCS7 transport point : ............................................................................................. 525 Creating the remote CCS7 Destination Points (DPCs of MSCs, SMLC etc.): .......................................... 525 Setting the object entry for the SMLC: ...................................................................................................... 534 Setting the timing values for the MSC: ...................................................................................................... 535 Setting the global parameters for the MSC: .............................................................................................. 540 Creating the HSLCESTUNNEL (object moved to BR11): ......................................................................... 541 Creating the HSLCESPW (object moved to BR11): .................................................................................. 543 Creating the CCS7 link set: ....................................................................................................................... 547 Creating the CCS7 link: ............................................................................................................................ 554 Creating the PCMH link: .......................................................................................................................... 555 Creating a Nailed-Up Connection through the BSC/TRAU:..................................................................... 557 Creating an X25 connection via dedicated link: ....................................................................................... 558 Creating an X25 connection via A-interface:............................................................................................ 561 Creating an IP Link connection: ............................................................................................................... 564 Creating the O&M link for the RC connection:......................................................................................... 566 Creating the link for the external connection to the SMS-CB system:....................................................... 566 Creating the SDH link for connectivity purposes:..................................................................................... 567 Defining the optical interface (INTF) configuration parameters:............................................................. 569 Creating the ATM Virtual Path (ATMVP):................................................................................................ 571 Configuration of Bidirectional Continuity Monitors for ATM Virtual Path (BCMATMVP):.................... 573 Creating the ATM Virtual Channel (ATMVC): ......................................................................................... 574 Configuration of Bidirectional Continuity Monitors for ATM Virtual Channels (BCMATMVC): ............ 576 Defining the BSC reference synchronization clock origin: ....................................................................... 577 Defining an external synchronization signal:............................................................................................ 577 Creating the Quality of Service Alarm Objects: ........................................................................................ 578 Creating the Quality of Service Alarm threshold sets: .............................................................................. 579 Creating the Quality of Service Alarm Objects for the BSC object:.......................................................... 581 Creating the Quality of Service Alarm Objects for BTS objects: .............................................................. 582 Creating the Quality of Service Alarm Objects for PTPPKF objects:....................................................... 586 Creating the Gb IP link: ............................................................................................................................ 587 Activating IMSI tracing in the BSC:.......................................................................................................... 588 Creating a Cell Traffic Recording (CTR) job:........................................................................................... 589 Activating PSIMSI tracing in the BSC: ..................................................................................................... 591 Creating a PS Cell Traffic Recording (PSCTR) job:................................................................................. 591 Enabling the data recording for the feature 'History on Dropped Calls':................................................. 595 Defining the BSC environmental alarms:.................................................................................................. 600 Configuring the feature Online RF Loopback:.......................................................................................... 601 Creating Smart Carrier Allocation: .......................................................................................................... 605

6 / 744



2 APPENDIX...................................................................................................................................................... 607 2.1 HANDOVER THRESHOLDS & ALGORITHMS ............................................................................................... 607 2.1.1 Functional Diagram Handover Thresholds for Inter-cell Handover and Intra-cell Handover (level, quality and power budget)......................................................................................................................... 607 2.1.2 Rules: Handover Thresholds for Inter-cell Handover and Intra-cell Handover (level, quality and power budget), Power Control disabled.................................................................................................... 6082.1.2.1 Inter-cell/Inter-system Handover due to level ............................................................................................ 608 2.1.2.1.1 Handover Decision / Handover Trigger Conditions........................................................................... 608 2.1.2.1.2 Target Cell List Generation ............................................................................................................... 609 2.1.2.1.3 Target Cell Ranking (HCS disabled).................................................................................................. 610 2.1.2.1.4 Target Cell Ranking with HCS........................................................................................................... 613 2.1.2.1.4.1 Ranking of 3G target cells within 3G sublist.................................................................................. 613 2.1.2.1.4.2 Ranking of 2G target cells within 2G sublist - Ranking Method 0................................................. 614 2.1.2.1.4.3 Ranking of 2G target cells within 2G sublist - Ranking Method 1................................................. 615 2.1.2.1.4. Resulting ranking of 2G and 3G target cells and sublists................................................................. 616 2.1.2.2 Intra-cell handover (quality)...................................................................................................................... 618 2.1.2.3 Inter-cell/Inter-system Handover due to quality ........................................................................................ 620 2.1.2.3.1 Handover Decision / Handover Trigger Conditions.......................................................................... 620 2.1.2.3.2 Target Cell List Generation ............................................................................................................... 621 2.1.2.3.3 Target Cell Ranking (HCS disabled)................................................................................................. 622 2.1.2.3.4 Target Cell Ranking with HCS.......................................................................................................... 622 2.1.2.4 Inter-cell/Inter-system Handover due to distance ...................................................................................... 623 2.1.2.4.1 Handover Decision / Handover Trigger Conditions.......................................................................... 623 2.1.2.4.2 Target Cell List Generation ............................................................................................................... 623 2.1.2.4.3 Target Cell Ranking (HCS disabled)................................................................................................. 625 2.1.2.4.4 Target Cell Ranking with HCS.......................................................................................................... 625 2.1.2.5 Inter-cell/Inter-system Handover due to better cell (power budget handover) .......................................... 626 2.1.2.5.1 Handover Decision / Handover Trigger Conditions.......................................................................... 626 2.1.2.5.1.1 Special Power Budget Calculation for calls in inner area of Concentric Cells............................... 627 2.1.2.5.2 Target Cell List Generation (HCS disabled) ..................................................................................... 630 2.1.2.5.3 Target Cell Ranking (HCS disabled)................................................................................................. 631 2.1.2.5.3.1 Speed sensitive handover enabled.................................................................................................. 632 2.1.2.5.4 Handover Initiation and Target Cell List Generation with HCS ....................................................... 634 2.1.2.5.5 Target Cell Ranking with HCS.......................................................................................................... 636 2.1.2.5.6 Speed sensitive handover enabled .......................................................................................................... 636 2.1.2.6 Inter-system Handover due to sufficient coverage..................................................................................... 637 2.1.2.6.1 Handover Decision / Handover Trigger Conditions & Target Cell List Generation ......................... 637 2.1.2.6.2 Target Cell Ranking (HCS disabled)................................................................................................. 638 2.1.2.6.3 Speed sensitive handover enabled..................................................................................................... 638 2.1.2.6.4 Target Cell Ranking with HCS.......................................................................................................... 639 2.1.2.6.5 Speed sensitive handover enabled (with HCS).................................................................................. 639 2.1.2.7 Forced Handover due to directed retry, preemption or O&M intervention ............................................... 640 2.1.2.7.1 Handover Decision / Handover Trigger Conditions.......................................................................... 640 2.1.2.7.2 Target Cell List Generation ............................................................................................................... 640 2.1.2.7.3 Target Cell Ranking (HCS disabled)................................................................................................. 642 2.1.2.7.4 Target Cell Ranking with HCS.......................................................................................................... 642 2.1.2.8 Fast Uplink Handover (Intra-BSC only).................................................................................................... 643 2.1.2.8.1 Handover Decision / Handover Trigger Conditions.......................................................................... 643 2.1.2.8.2 Target Cell List Generation ............................................................................................................... 643 2.1.2.8.3 Target Cell Ranking ........................................................................................................................... 644 2.1.2.9 Inter-cell Handover due to BSS Resource Management Criteria (Traffic HO) ......................................... 645 2.1.2.9.1 Handover Decision / Handover Trigger Conditions.......................................................................... 645 2.1.2.9.2 Target Cell List Generation ............................................................................................................... 650 2.1.2.9.3 Target Cell Ranking (HCS disabled).................................................................................................. 650 2.1.2.9.4 Target Cell Ranking with HCS.......................................................................................................... 652

2.2 REPORTING, DISPLAY AND BTS INTERNAL HANDLING OF RSCP VALUES FROM 3G NEIGHBOUR CELLS .... 653 2.3 SEQUENCE OF HANDOVER TYPES WITHIN THE HANDOVER DECISION ALGORITHM IN THE BTS ............... 655 2.4.1 Functional Diagram: Power Control Thresholds - Power Increase / Power Decrease (Classic Power Control) ..................................................................................................................................................... 656 2.4.2 Rules: Power Control Thresholds: Power Increase / Power Decrease........................................... 6572.4.2.1 Power Increase .......................................................................................................................................... 657 2.4.2.2 Power Decrease ......................................................................................................................................... 657

2.4.3 Classic and Adaptive Power Control .............................................................................................. 6602.4.3.1 Introduction ................................................................................................................................................ 660

7 / 744



2.4.3.2 Classic Power Control decision process .................................................................................................... 660 2.4.3.3 Adaptive Power Control decision process ................................................................................................. 661 2.4.3.4 Differences between CLASSIC and ADAPTIVE power control decision ................................................ 662 2.4.3.5 Functional sequence of a BS and MS power control procedure ................................................................ 664 2.4.3.5.1 BS power control procedure.............................................................................................................. 664 2.4.3.5.2 MS power control procedure............................................................................................................. 665 2.4.3.6 Comparison of timing behaviour of different Power Control types - MS Power Control, BS Power Control, classic and adaptive .................................................................................................................................. 667 2.4.3.7 Further differences between CLASSIC and ADAPTIVE Power Control.................................................. 669 2.4.3.8 Interaction of Power Control Measurement Preprocessing and Power Control Decision ........................ 671

2.5 INTERWORKING OF HANDOVER AND POWER CONTROL ............................................................................ 673 2.5.1 Functional Diagram: Inter-cell Handover and Intra-cell Handover, Power Increase and Power Decrease .................................................................................................................................................... 673 2.5.2 Rules ................................................................................................................................................ 674 2.6 SERVICE DEPENDENT HANDOVER AND POWER CONTROL ........................................................................ 675 2.6.1 Introduction ..................................................................................................................................... 675 2.6.2 SGxxHOPAR and SGxxPCPAR parameter values ........................................................................... 6762.6.2.1 SGxxHOPAR parameter values (Handover) .............................................................................................. 676 2.6.2.2 SGxxPCPAR parameter values (Power Control)........................................................................................ 678

2.7 MAPPING OF RXQUAL AND C/I VALUES.................................................................................................. 681 2.8 AMR LINK ADAPTATION THRESHOLDS UPLINK ....................................................................................... 683 2.9 BSC, MSC AND BTS OVERLOAD HANDLING ........................................................................................... 691 2.9.1 BSC Overload.................................................................................................................................. 6912.9.1.1 BSC overload conditions............................................................................................................................ 691 2.9.1.1.1 SS7 Link Congestion.......................................................................................................................... 691 2.9.1.1.2 Internal Message Congestion ............................................................................................................ 691 2.9.1.1.3 PPXL Overload .................................................................................................................................. 691 2.9.1.1.4 BSC Paging Queue Overflow............................................................................................................. 693 2.9.1.2 System reactions and overload regulation measures in case of BSC overload .......................................... 703 2.9.1.2 System reactions and overload regulation measures in case of BSC overload .......................................... 703 2.9.1.2.1 Further important notes on BSC reactions ........................................................................................ 704 2.9.1.3 Mechanisms for reduction of originating traffic and reduction of terminating traffic ............................... 705 2.9.1.3.1 Overload level management .............................................................................................................. 705 2.9.1.3.2 Traffic reduction algorithms.............................................................................................................. 706 2.9.1.3.3 Special overload supervision algorithm in case of BSC paging queue overflow .............................. 707

2.9.2 MSC Overload .............................................................................................................................. 7082.9.2.1 System reactions and overload regulation measures in case of MSC overload .......................................... 708 2.9.2.1.1 Special overload level escalation algorithm in case of MSC overload............................................... 708

2.9.3 BTS Overload .................................................................................................................................. 7092.9.3.1 BTS overload conditions ............................................................................................................................ 709 2.9.3.1.1 PCH messages discarded in BTS ....................................................................................................... 709 2.3.9.1.2 AGCH messages discarded in BTS .................................................................................................... 709 2.3.9.1.3 Abis LAPD signalling overload UL ................................................................................................... 728 2.3.9.1.4 RACH overload.................................................................................................................................. 728 2.9.3.2 Traffic reduction mechanisms in case of BTS overload ............................................................................ 728 2.9.3.3 System reactions and overload regulation measures in case of BTS overload........................................... 729

2.9.4 Interaction of BTS Overload and BSC Overload ............................................................................ 732 2.9.5 Effects on Performance Measurement Counters ............................................................................. 732 4 PARAMETERS GROUPED BY RELEASE AND FEATURE ...................................................................... 733 BR10.01: ........................................................................................................................................................ 733 Downlink Dual Carrier (FRS 95462, SFD 10562): .................................................................................. 733 MultiOperator BSS 2G Network Sharing Solution (FRS96782): ........................................................... 733 Internal IP over Ethernet BSS interface (FRS 94060, SFD 10560): ......................................................... 733 BR10.0: .......................................................................................................................................................... 733 AMR Wideband TCH/WFS (FRS 89487, SFD 10557): ............................................................................. 733 Consolidation of Maintenance Bitmask (FRS 94645): .............................................................................. 733 Different Level Thresholds for RACH access and Handover access (FRS 94417): ................................. 733 Early Uplink TBF Establishment (FRS 94083, SFD 10552):.................................................................... 734 Link Adaptation Improvements (FRS94358, SF10551): ........................................................................... 734 Repeated SACCH (FRS 94171, SFD 10558):............................................................................................ 734 RRM Update for BR10.0 (FRS 95162):..................................................................................................... 734

8 / 744



Support of Real Time Road Traffic Information for TomTom (FRS97345, SF10572): ............................ 734 Group Call Broadcast Point in BSS (FRS 89901, SFD 10513): ............................................................... 734 Reactivation of VGCS/VBS channels after service unavailability (FRS 94688, SFD 10513): .................. 734 Short Data Transmission during ongoing Group Call (FRS 96747, SFD 10570, CR 4337): ................... 734 Enhancements of PCU capacity (FRS 95910, SFD 10559): ..................................................................... 734 Modified PCU load balancing (FRS 95283):............................................................................................ 734 Flexible A (FRS 94593):............................................................................................................................ 735 GERAN integrated eTRAU based on eBSC introduction (FRS 94687):.................................................... 735 Introduction of universal slot concept for eBSC-based equipment (FRS 95633):..................................... 735 BR 9.0: ........................................................................................................................................................... 735 Allocation/Retention Priority (FRS 89950, SFD 010506): ....................................................................... 735 Central Network Service Layer (FRS 89795, SFD 10507): ...................................................................... 735 NS Overload Control (FRS 92895): .......................................................................................................... 735 Flexible Gb (FRS 89900, SFD 10503): ..................................................................................................... 735 Ciphering Algorithm A5/3 FRS 89397, SFD10505): ................................................................................ 735 Ciphering for VGCS Calls (FRS92313, SFD 10523): ............................................................................... 735 Delayed PWRC for E911 Emergency Calls (FRS No. 90199, SFD 10516): ............................................. 735 Derived Handover Power (FRS 89401, SFD 10504):............................................................................... 735 Dual Transfer Mode Power Budget HO Handling (FRS 92563): ............................................................ 736 External Network Assisted Cell Change (FRS 90351, SFD10508): .......................................................... 736 Fine Tuning for Quality Thresholds (FRS 90827, SFD10524): ................................................................ 736 Gb Streaming Enhancements (FRS 89990, SFD 10512): ......................................................................... 736 Multi-standard Network Controller (FRS 94155): .................................................................................... 736 RAN Information Management (FRS 86654, SFD10518):........................................................................ 736 Real Time TBF and EDA TBF multiplexing (FRS 89997, SFD 10517): ................................................... 736 Simultaneous power activation of many TRX in test mode (FRS 92263, SFD 10527):............................. 736 Stand-alone eTRAU (FRS No. 94474):...................................................................................................... 736 Stand-alone GERAN eBSC: HC BSC step IV (FRS 89369, SFD 10522): ................................................. 737 Temporary Overpower & Repeated FACCH (FRS 92893, SFD10525):................................................... 737 Throughput improvements for LAPD on Abis (FRS 91456):.................................................................... 737 Uplink Incremental Redundancy (FRS 459, SFD 10501): ........................................................................ 737 BR8.0 ............................................................................................................................................................. 737 Common BCCH Dual Band Cells (FRS 87030, SFD 10961).................................................................... 737 Compression / decompression handover improvements (FRS 87061): ..................................................... 737 Dynamic MAIO Allocation (FRS 86113, SFD 10957): ............................................................................. 737 DMA Admission Control (FRS 87478):..................................................................................................... 737 Dual Transfer Mode (FRS 89161):............................................................................................................ 737 Extended Dynamic Allocation, Flexible USF granularity, Overheating management (FRS 88930):....... 738 Service Group dependent setting of RLT:.................................................................................................. 738 Extended UL TBF (FRS 87477, SFD 10964): ........................................................................................... 738 Flexible Carrier Unit (FRS 84798, SFD 10473):...................................................................................... 738 Inter Site Synchronization (FRS 87454, SFD 10956): .............................................................................. 738 Level Handover Margin for Quality Handover (FRS 89106): .................................................................. 738 Multi Service Layer Support (FRS 84566, SFD 10962):........................................................................... 738 Network Controlled Cell Reselection 2G-3G due to sufficient UMTS coverage (FRS 87029, SFD 10954): ................................................................................................................................................................... 738 Network Assisted Cell Change (FRS 86853, SFD 10952):........................................................................ 738 Quality of Service Streaming Services for E-/GPRS (SFD 10950: FRS 486: Quality of Service Support for PS Services, FRS 86774: Enhanced Flow Control, FRS 86941 EGPRS GPRS Scheduler Enhancements for Rel.5 QOS Support): ............................................................................................................................ 739 Wireless Priority Services (FRS 87028, SFD 10968):............................................................................... 739 BR 7.0: ........................................................................................................................................................... 739 Flexible Abis Allocation Strategy (FRS 429, SFD 10447): ....................................................................... 739 Gb / MS flow control (FRS 514, SFD 10448): .......................................................................................... 739 Link Quality Control: Link Adaption (FRS 444, SFD 10449)............................................................. 739 Improved Power Control (FRS 546, SFD 10451)................................................................................. 739 Service dependent Power Control and Handover Thresholds (FRS 534, SFD 10452) ............................. 739 Support of CS3/CS4 (FRS 419, SFD 10454) ............................................................................................. 739 Common Codec Pool for TRAU (FRS 85459, SFD 10478)....................................................................... 740

9 / 744



EDGE: Speeding up into a packet data world (FRS 481, SFD 10445)..................................................... 740 GPRS and EGPRS Quality of Service (SFD10455)................................................................................... 740 Network controlled cell reselection (FRS 418, SFD 10456) ..................................................................... 740 Use of the uplink in the group call channel (SFD 10460) ......................................................................... 740 Handover from GSM to UMTS (FRS 490, SFD 10461) ............................................................................ 740 Transmission Diversity Time Delay (FRS 84799, SFD 10468) ................................................................. 740 Performance Measurements based on EMR (FRS 84533, SFD 10469)............................................. 740 IP based O- Link (FRS 85571, SFD 10472):............................................................................................. 740 Location based services: Enhanced TA positioning (FRS 84143, SFD 10492): ....................................... 740 BR 6.0 / BR 6.1:.............................................................................................................................................. 741 Cell load dependent activation of halfrate (FRS 240, SFD 10429)........................................................... 741 Adaptive Multi-Rate codec (AMR) (FRS 201, SFD 10423)....................................................................... 741 Enhanced Pairing for HR Channels (FRS 347, SFD 10430) .................................................................... 741 Handover Decision due to BSS Resource Management Criteria (FRS 407, SFD 10436)......................... 741 Fast Uplink Handover (FRS 338, SFD 10437) ......................................................................................... 741 Introduction of Level Handover Margin Parameters (FRS 260, SFD 10438)........................................ 741 Smooth Channel Modification (FRS 352, SFD 10425) ............................................................................. 741 Service Dependent Channel Allocation Strategy Step 1(FRS457, SFD 10432) ........................................ 741 Common BCCH for GSM900/1800 , Dual Band Operation (FRS 248, SFD 10428)................................ 741 Smart Carrier Allocation (FRS 205, SFD) ................................................................................................ 742 Extended Idle Channel Measurements (FRS 206, SFD 10434)................................................................. 742 Location Services (FRS 398, SFD 10422)................................................................................................. 742 ASCI Step 2 (FRS 383, SFD 10424) .......................................................................................................... 742 Online RF Loopback (FRS 2884) .............................................................................................................. 742 CALL Number Increase (FRS 391, SFD 10435) ....................................................................................... 742 Multiple Abis LAPD Links Load Sharing and LAPD fault Recovery (FRS 308).................................... 742 BR 5.5: ........................................................................................................................................................... 742 General Packet Radio Service (GPRS)...................................................................................................... 742 Tandem free operation (TFO) of Speech Codecs ...................................................................................... 743 VAD/DTX and comfort noise for half rate speech ..................................................................................... 743 Cell traffic recording (CTR) ...................................................................................................................... 743 OLDER RELEASES: ........................................................................................................................................... 744 Handover ................................................................................................................................................... 744 Power Control ........................................................................................................................................... 744 Discontinuous transmission (DTX)............................................................................................................ 744 Preemption, directed retry and queuing.................................................................................................... 744 High Speed Circuit Switched Data (HSCSD) ............................................................................................ 744

10 / 744



1 Database BR10.01.1 BR10.0 Object Tree of functional BSC database objects

11 / 744



The above diagram shows the architecture of the functional objects in the BSC database, HW objects are not considered. Note: The objects BTSMOSUSW, TRAOSUSW, SCANCO, the scanner objects ('SCANxxxx') are not considered in this document.

12 / 744



Notes:1) The parameters marked by (compared to BR9.0). grey background are new in BR10.0

2) Changes of parameter values, value ranges and default values are indicated by highlighted letters. Changes of parameter names are marked, too.3) Notes on parameter grouping: - For a better logical structure, the parameters are grouped in the 'pseudopackages' (e.g. CREATE BTS [BASICS], SET BTS [CCCH] etc.) as used in the LMT GUI. - Within each package, parameters are sorted alphabetical order.

13 / 744



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 0..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 object entry for the BOF:< The BOF ((Blocking Optional Features) object is added to the configuration database with a single autocreated instance and lists the features available for the customer.> Object name.- address of the managed object Feature , this parameter defines the list of the optional feature available for the customer.

NAME= BOF:0..0, FEA =noneobject: BOF range for BSC:a32_bsc72_pcu; a32_bsc120_pcu; a38_ebsc_pcu; f34_ul_inc_red; f35_deriv_ho_pwr; f56_amr;f71_nccr_2g_2g; f72_ho_2g_3g;f74_ip_o_link;f78_edge; f84_qos_streaming;f85_nacc;f86_nccr_2g _3g; f92_eda;f93_hsgb; f94_int_echo_ctrl;f95_int_noise_red; f96_int_level_ctrl;f99_dtm; f102_flex_gb;f103_ciphering_a53; f104_arp;f105_central_ns; f106_ext_nacc; f107_ms_class_30_33; f109_gb_stream_enh; f112_delayed_pwrc; f113_bsc72_trx; f113_bsc120_trx; f113_ebsc_trx; f114_bsc72_pdt_pcu; f114_bsc120_pdt_pcu; f114_ebsc_pdt_pcu; f116_ciphering_vgcs; f117_rfacch; f118_trx_test_mode; f119_multi_mnc; f110_group_call_bp; f123_ps_ho;f124_flex_a; f125_amr_wb; f126_rep_sacch; f127_enh_pcu_capacity; f129_dl_dc; f130_pcu_mod_load_bal; f132_vcgs_vbs_react; f133_idra; b21_ps_ctr; b21_ps_imsi_tracing;

14 / 744


GERAN-S Database Parameter Planning & Engineering Manual BR10.0 and 10.01 Version 1.0 29.08.08 ______________________________________________________________________________________________________ ____ f560_rtpm; f122_virtual_etrau; f145_standby_trx; f135_shunting_yards; f144_tom_tom; f96782_tmp; range for EBSC: a32_bsc72_pcu;a32_bsc120_pcu;a38_ebs c_pcu;f34_ul_inc_red;f35_deriv_ho_pwr;f 56_amr;f71_nccr_2g_2g;f72_ho_2g_3g;f 74_ip_o_link;f78_edge;f84_qos_streamin g;f85_nacc;f86_nccr_2g_3g;f92_eda;f93_ hsgb;f94_int_echo_ctrl;f95_int_noise_red ;f96_int_level_ctrl;f99_dtm; "f99_dtm"; "f102_flex_gb"; "f103_ciphering_a53"; "f104_arp"; "f105_central_ns"; "f106_ext_nacc; f107_ms_class_30_33"; "f109_gb_stream_enh"; "f112_delayed_pwrc";"f113_bsc72_trx"; "f113_bsc120_trx"; "f113_ebsc_trx"; "f114_bsc72_pdt_pcu"; "f114_bsc120_pdt_pcu"; "f114_ebsc_pdt_pcu"; "f116_ciphering_vgcs"; "f117_rfacch";"f118_trx_test_mode"; "f119_multi_mnc"; "f110_group_call_bp"; "f123_ps_ho";"f124_flex_a"; "f125_amr_wb"; "f126_rep_sacch"; "f127_enh_pcu_capacity"; "f129_dl_dc";"f130_pcu_mod_load_bal"; "f132_vcgs_vbs_react"; "f133_idra";"b21_ps_ctr"; "b21_ps_imsi_tracing"; "f560_rtpm";" f122_virtual_etrau" ; "f145_standby_trx"; "f135_shunting_yards"; "f144_tom_tom"; "f96782_tmp" default: none

OPC=none;object: range: BOF

Originating Point Code, this parameter identifies the originating system (BSS). It consists of three fields: NetworkClusterMember, NetworkCluster, NetworkIdentifier.

for NetworkClusterMember: 0 - 255 (0-255 for CCITT 1-255 for ANSI) for NetworkCluster: 0 - 255 (0-63 for CCITT 0-255 for ANSI) for NetworkIdentifier: 1 - 254 (NO_CONFIG for CCITT 1-254 for ANSI)

default:

none

PWD =none;object: range: default: BOF 15 characters string none

Password - this attribute indicates a password associated to a feature. It is a string of 15 hexadecimal values.

QTY =none;object: range: default: BOF 0 .. 65534 none

Quantity - this attribute provides the Capacity Level of an optional feature.

Setting the object entry for the RSUFW:

15 / 744



NAME= RSUFW:0..19, ULAB =object: default: RSUFW; 130 characters string

Object name.- address of the managed object User label, this parameter assigns a user friendly name (is a userdefined string) to the BSC Executable Software Unit DB (note it is the same of the related BSC Reusable Software Unit DB). Processor firmware identifier, this parameter identifies the processor type for which the FW file is to be transferred.

PROCFWID =noneobject: range: RSUFW SMAC_FW; LIET_FW; MCP_FW; AP_FW; UPM_FW; LISO_FW; SHELFMGR_FW; LME_FW; none

default:

Range modified in BR10.0

SRCPATH=object: range: RSUFW

Source path, this attribute represents the source path of the files which are to be copied or moved.

Setting the object entry for the RSUPCH: NAME=RSUSWLH:0..59/RSU EXE:0..249/RSUPCH:0..399, PERM =none;object: range: default: RSUPCH TRUE, FALSE none

Object name.- address of the managed object Permanent, this parameter can be equal to TRUE or FALSE. If it is set equal to TRUE the patch is automatically loaded at the next "bring-up" operation; otherwise it is not loaded. Priority slot number, This attribute stores an integer value; at bring up, the loading sequence of the patches will be determined by sorting the patches in function of the slot number. The default value is valid for the unpatches; a value which will cause the patch to be loaded after the ones currently created (i.e. the current maximum slot number plus one) for the patches. Processor type, this parameter identifies the processor type for the file to be transferred in the eBSC disk.

PRIOSLOTN=;object: range: default: RSUPCH 0..65000

PROCTYPE=none;object: range: default: RSUPCH GENERICEXE; SMAC; LIET; MCP; AP; UPM; LISO; LME; none

16 / 744



SRCPATH=;object: range: default: RSUPCH

Source path, this attribute represents the source path of the files which are to be copied or moved

ULAB =object: default: RSUPCH;

User label, this parameter assigns a user friendly name (is a userdefined string) to the BSC Executable Software Unit DB (note it is the same of the related BSC Reusable Software Unit DB). User label of SW load header. This parameter defines the user label of the software load header and it consists of 30 characters string.

ULABSWLH=object: range: default: RSUPCH; 1..30 character string

Setting the object entry for the APD:The APD (AP Dependent) board has the role to provide additional Radio Resource Management (RRM) capabilities for large configurations in which not all sites can be mapped to APM due to capacity needs.

SET APD :NAME=APD:1..5 BLADEPOS1=,object: range: APD path name (e.g. 'BLADEPOS1=EBSCRACK:0/ SHELF:0/APD:1') default: none Introduced in BR10.0

Object path name. Blade position 1. The attribute indicates the shelf/slot in the rack where 1st (active) APD module is to be plugged in and the instance number of the relevant object that shall be created.

BLADEPOS2=,object:

SHELF:0/APD:2') default: none Introduced in BR10.0

Blade position 2. The attribute indicates the shelf/slot in the rack where 2nd (redundant) APD module is to be plugged in and the instance number of the relevant object that shall be created. This APDrange: path name (e.g. Application Processor does redundancy of the other one, whose 'BLADEPOS1=EBSCRACK:0/ position is set by means of BLADEPOS1.

Creating the APM:The APM (AP Master) provides the single point of access for the core network, handles centralised algorithms and also handles an own set of sites in terms of Radio Resource Management RRM. CREATE APM: NAME=APM:0..0 BLADEPOS1=,object: range: APM path name (e.g. 'BLADEPOS1=EBSCRACK:0/ SHELF:0/APD:2')

Object path name. Blade position 1. The attribute indicates the shelf/slot in the rack where 1st (active) APM module is to be plugged in and the instance number of the relevant object that shall be created.

17 / 744


GERAN-S Database Parameter Planning & Engineering Manual BR10.0 and 10.01 Version 1.0 29.08.08 ______________________________________________________________________________________________________ ____ default: none

Introduced in BR10.0

BLADEPOS2=,object: range:

Blade position 2. The attribute indicates the shelf/slot in the rack where 2nd (redundant) APM module is to be plugged in and the instance number of the relevant object that shall be created. This APM Application Processor does redundancy of the other one, whose path name (e.g. 'BLADEPOS1=EBSCRACK:0/ position is set by means of BLADEPOS1.SHELF:0/APD:2') none

default:


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 and 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. From 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 Radio Network Analyser ) RNA application. 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. From 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

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

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

18 / 744



by the Radio Network Analyser (RNA)application. HDCFS=1,object: unit: range: default: BSC [CONTROL] 1 Mbyte 1..24 1

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.

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

19 / 744



MASCLOGFS=3,object: unit: range: default: BSC [CONTROL] 1 Mbyte 1..24 3

Maximum scanner logfile size, this attribute indicates the maximum size of the scanner result file on the BSC disk. The file SCAN.TMP is the scanner logfile on the BSC disk to which all scanner results of scanners which were created 'BYFILE' are written. This file is available in the BSC directory MEASURE_DIR. To upload the scanner results to the RC the file SCAN.TMP is closed, renamed to SCAN.LOG and transferred to the directory READY_MEAS. Form there it is compressed to the directory DBFH_ZIP from where it is uploaded to the RC. The size threshold entered by MASCLOGFS determines the maximum allowed size of the file SCAN.TMP: when the entered size is reached for the file SCAN.TMP the SCAN.LOG is automatically uploaded to the RC. New measurement results are then written to a newly opened SCAN.TMP file. Measurement data file upload period, defines the time period between two uploads of measurement data files. Setting this parameter to UPPE_0h disables the periodic upload.

MEDAFUPE=UPPE_0H,object: BSC [CONTROL] range: UPPE_0h= no per. upl.. UPPE_15m = Upl. prd. 15 min. UPPE_30m = Upl. prd. 30 min. UPPE_1h = Upl. period 1h UPPE_2h = Upl. period 2h UPPE_3h = Upl. period 3h UPPE_4h = Upl. period 4h UPPE_6h = Upl. period 6h UPPE_8h = Upl. period 8h UPPE_12h= Upl. period 12h UPPE_24h= Upl. period 24h default: UPPE_0h

MEDAFUST=0-0;object: range: default: BSC [CONTROL] upload start hour upload start minute upload start hour upload start minute 0..23 0..59 0 0

Measurement data file upload start, defines the start time for measurement data file upload. Parameter format: upload start hour - upload start minute.

PSCFS=1;object: unit: range: default: BSC [CONTROL] 1 Mbyte 1..12 1


PS CTR file size, this attribute indicates the maximum size of the 'PS Cell Traffic Recording' logfile on the BSC disk. The feature PS 'Cell Traffic Recording' or 'PS Cell Trace' is a feature used to record cell specific PS call events for monitoring purposes.The parameter PS CFS specifies the maximum file size for the PS CTR trace logfiles in the BSC directory. When a PS CTR tracing procedure is in progress, the BSC writes the binary trace data to the open binary trace file. On TBF rerlease, a trace record is generated and written to the PS CTR trace logfile. The parameter PSCFS specifies the maximum size of this PS CTR logfile. When the trace logfile exceeds the size specified by PSCFS, it is closed and transferred to the BSC directory. From there it is compressed and uploaded to the RC at the next possible point of time (automatic upload takes place every 5 minutes). A PS 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 Radio Network Analyser )RNA application. PS IMSI file size, this parameter is associated to the feature 'PS IMSI Tracing' (see command CREATE TRACE) and specifies the maximum file size for the PS IMSI trace files in the BSC directory. When an PS IMSI tracing procedure is in progress, the BSC writes the binary trace data to the open binary trace file. The parameter PSIMSIFSIZ specifies the maximum allowed size of this binary trace

PSIMSIFSIZ=1;object: unit: range: default: BSC [CONTROL] 1 Mbyte 0..30 1

20 / 744


GERAN-S Database Parameter Planning & Engineering Manual BR10.0 and 10.01 Version 1.0 29.08.08 ______________________________________________________________________________________________________ ____ Introduced in BR10.0

file. When the tracing process is finished the binary trace files are closed and compressed. Then 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 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 Radio Network Analyser (RNA) application.

21 / 744



Setting the timing values for BSSMAP control and BSC overload handling: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 '[TIMER]' is normally only used on the LMT but was used here to allow a more useful grouping of the commands . Object path name. BSC timer T10, this timer determines the time to return the ASSIGNMENT COMPLETE message in case of call setup and intra-cell handover. 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.a) Assignment procedure: release of the associated resources if the MS is lost during the assignment procedure. 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. 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. 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). T10 purpose:

SET BSC [TIMER]: NAME=BSC:0, BSCT10=HLFSEC-10,object: unit: range: default: Reference: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-10 GSM 08.08 (04.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. Note: Due to the SBS implementation T10 replaces the function of the GSM timer T3107, i.e. T3107 is not used by the SBS. Rule: BSCT10 < TTRAU (for TTRAU see command SET BTS [TIMER]) This setting is necessary to ensure that a signalling failure (T8 and T10) is detected before transcoder failure (TTRAU) BSCT11PUB=HLFSEC-16,object: unit: range: default: Reference: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-16 GSM 08.08

BSC timer T11 public, this timer determines the maximum allowed queuing time for TCH assignment requests in the 'public queue'. The parameter BSCT11PUB replaces the parameter BSCT11 (used up to BR7.) and is only relevant if the feature 'queuing' / 'WPS queuing' is enabled (see parameter EQ in command SET BTS [OPTIONS] for a detailed description). When a TCH request for an assignment procedure (i.e. when the BSC receives an ASSIGNMENT REQUEST message from the MSC) is put into a queue due to TCH congestion, T11 determines the maximum time the TCH request may remain in the queue to wait for a busy TCH to become idle. If the TCH request for assignment procedure cannot be served within this time frame and T11 expires, the BSC sends a CLEAR REQUEST to the MSC and the context is released.T11 purpose: start: stop: Limitation of the queuing time for an TCH request due to Assignment sending of the QUEUING INDICATION (BSC->MSC) - successful allocation of a TCH to the queued TCH request - 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. Network Engineering GERAN

22 / 744


BSCT11WPS=HLFSEC-16,object: unit: range: default: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-16

In BR8.0, the original 'queuing' feature is replaced by the feature 'Wireless Priority Service (WPS)', which is a special enhancement of the feature 'queuing' required by the U.S. market (see parameter EQ in command SET BTS [OPTIONS]). This feature foresees a two queue concept, one queue being used for ordinary subscribers ('public') and one for priorized subscribers ('WPS queue'). The parameter BSCT11PUB defines the queuing timer T11 for the 'public' queue. Further parameters related to the WPS feature are BSCT11WPS, BSCTQHOPUB, BSCTQHOWPS (see below) and EQ, QLWPS, QLPUB, WPSPREF, LWWPSPRI (see command SET BTS [OPTIONS]). Notes: - Queuing a TCH request means a considerable extension of the SDCCH seizure duration! - 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. Therefore it has to be carefully considered which waiting time can be regarded as acceptable from the subscriber's point of view. In other words: it makes no sense to set T11 to a too high value. - It is possible to accelerate the release of busy TCHs by an appropriate setting of the timer T3111 (see SET BTS [TIMER]). This may decrease the queuing time considerably. - 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, during the queuing time no SDCCH-SDCCH handover will ever be performed. If no TCH can be found in the target cells, the TCH request is discarded from the queue. BSC timer T11 WPS, this timer determines the maximum allowed queuing time for TCH assignment requests in the 'WPS queue'. This parameter is only relevant if the feature 'Wireless Priority Service (WPS)' is applied (see parameter BSCT11PUB). The parameter BSCT11WPS defines the queing timer T11 for the 'WPS' queue.

23 / 744



BSCT14PUB=HLFSEC-16,object: unit: range: default: FRS-No.: SF-No.: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-16 94688 10513

BSC timer T14 Public, this timer determines the maximum allowed queuing time for the ASCI calls in the public queue as required by the 3GPP standard. The timer is modelled as a sequence of two fields: TUNIT and TVALUE. The first field assumes the value of 500ms (HLFSEC) or 5 seconds (SEC5), while second field is an integer with range 0..254. For further details please refer to the description of parameter EASCICRE. BSC timer T14 WPS, this timer determines the maximum allowed queuing time for the ASCI calls in the WPS queue as required by the 3GPP standard. The timer is modelled as a sequence of two fields: TUNIT and TVALUE. The first field assumes the value of 500ms (HLFSEC) or 5 seconds (SEC5), while second field is an integer with range 0..254. For further details please refer to the description of parameter EASCICRE.


BSCT14WPS=HLFSEC-16,object: unit: range: default: FRS-No.: SF-No.: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-16 94688 10513


24 / 744



BSCTAST= 5,object: unit: range: default: FRS-No.: SF-No.: Reference: BSC [TIMER] s 1..30 5 89901 10515 GSM 08.08


BSCTimerTast, this timer determines the time to report periodical information to the MSC about the cells which changed state since the last sent report message. Applicable for an ASCI call, which the ASCI Broadcast Point in BSS feature is being applied to (ASCIBROADP=TRUE). The timer is always restarted till the end of the call. The default value has been fixed 5 seconds; higher values may cause problems in case of an INTER-cell MSC-controlled HO of a VGCS subsequent talker in 1 Channel Model.

25 / 744



BSCTQHO=HLFSEC-20,object: unit: range: default: Reference: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-20 GSM 08.08

BSC timer for queuing of handover, this timer determines the maximum allowed queuing time for incoming handover. This parameter is only relevant if the feature 'queuing' is enabled (see parameter EQ in command SET BTS [OPTIONS]). When a TCH request for an incoming MSC-controlled handover (i.e. when the BSC receives a HANDOVER REQUEST message from the MSC) is put into a queue due to TCH congestion, TQHO determines the maximum time the TCH request may remain in the queue to wait for a busy TCH to become idle. 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, the TCH request is rejected with a HANDOVER FAILURE. As a result, if there is another target cell available for the handover procedure, the MSC will attempt another HO REQUEST procedure towards the next target BTS.#TQHO purpose: Limitation of the queuing time for an TCH request due to incoming MSC-controlled handover start: sending of the QUEUING INDICATION (BSC->MSC) stop: - successful allocation of a TCH to the queued TCH request - 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.

Note: It is possible to accelerate the release of busy TCHs by an appropriate setting of the timer T3111 (see SET BTS [TIMER]). This can decrease the queuing time considerably. BSCTQHOPUB=HLFSEC-16,object: unit: range: default: BSC [TIMER] HLFSEC=0,5s SEC5=5s 0..254 HLFSEC-16

BSC timer for queuing of handover in public queue, this timer determines the maximum allowed queuing time for TCH requests due to incoming handover in the 'public queue'. This parameter is only relevant if the feature 'Wireless Priority Service (WPS)' is applied, which is a special enhancement of the feature 'queuing' required by the U.S. market (see parameter EQ in command SET BTS [OPTIONS]). This feature foresees a two queue concept, one queue being used for ordinary subscribers ('public') and one for priorized subscribers ('WPS queue'). The parameter BSCTQHOPUB defines the queing timer TTQHO (see parameter BSCTQHO which is used for ordinary queing) for the 'public' queue. Further parameters related to the WPS feature are BSCT11PUB, BSCT11WPS (see above), BSCTQHOWPS (see below) and EQ, QLWPS, QLPUB, WPSPREF, LWWPSPRI (see command SET BTS [OPTIONS]).

BSCTQHOWPS=HLFSEC-16, BSC timer for queuing of handover in WPS queue, 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,5s relevant if the feature 'Wireless Priority Service (WPS)' is applied (see SEC5=5s parameter BSCTQHOPUB). The parameter BSCTQHOWPS defines range: 0..254 the queing timer TQHO (see parameter BSCTQHO which is used for default: HLFSEC-16 ordinary queing) for the 'WPS' queue.

26 / 744



ENACCTREP=30,object: unit: range: default: FRS-No.: SF-No.: BSC [TIMER] 1 min. 15..750 30[min] 86654, 90351 10518, 10508

Introduced in BR9.0

ENACCTRL=24,object: unit: range: default: FRS-No.: SF-No.: BSC [TIMER] 1h 1..60 24[h] 86654, 90351 10518, 10508

External NACC Timer for Repetitions, this parameter is related to the features 'External NACC' (see parameter ENACCE in command SET BSC [BASICS])' and 'RAN Information Management' (RIM). RIM comprises signaling procedures (RIMApp = RIM Applications) executed between two BSCs via the connected SGSN and which are employed whenever the 'controlling BSC' requests particular call processing information from the 'serving BSC'. ENACCTREP determines the time, after which the controlling BSC retries a particular RIM procedure (RIR, RI or RIAE - for further details, please refer to the descriptions of parameters ENACCTRI, ENACCTRIR and ENACCTRIAE (see below)), that were not successfully completed even after N repetitions (N depends on the type of message and is defined by the parameters ENACCTRICM (for RI), ENACCTRIAECM (for RIAE) )of the original message. T(REP) is started in the BSC when it starts the RI, RIR or RIAE procedures towards the remote peer BSC (via the SGSN) and is stopped when the corresponding procedure was successfully completed. When the corresponding procedures were not successfully completed after all attempts, i.e. no positive response or acknowledgement was received after as many message repetitions as defined by the repetition threshold parameters ENACCTRICM, ENACCTRIRCM or ENACCTRIAECM (see below) and T(REP) expires, the corresponding procedure (RI, RIR or RIAE) is attempted again until it is either successfully completed or until the abovementioned repetition thresholds are reached again. Notes: - A RIM_Failure_Indication does not stop the T(REP) timer inside the RIM Application (in BR9.0 the only RIM Application is External NACC); T(REP) will expire after the specified amount of time. - The T(REP) handling is a task of the RIM Application. External NACC Timer for Repetition Long, this parameter is related to the features 'External NACC' (see parameter ENACCE in command SET BSC [BASICS])' and 'RAN Information Management' (RIM). RIM comprises signaling procedures executed between two BSCs via the connected SGSN and which are employed whenever the 'controlling BSC' requests particular call processing information from the 'serving BSC'. ENACCTRL represents the maximum value of the BSC timer T(REPL). When controlling BSC starts an RIR Procedure towards serving BSC (please see parameter ENACCTRIR for further details), it can happen that the serving BSC does not support the ENACC functionality (yet). In this case the controlling BSC will receive a RAN INFORMATION ERROR (RIE) with cause Unknown Application Id. The timer T(REPL) is started on reception of the aforementioned message. When T(REPL) has been started, the BSC tries to repeat the RIR procedure on every T(REPL) timer expiry. Thus T(REPL) timer takes care not to transmit too many RIR messages to BSCs that do not support the RIM functionalities.

27 / 744



ENACCTRI=2,object: BSC [TIMER] unit: 1s range: 2..8 default: 2[s] FRS-No.: 86654, 90351 SF-No.: 10518, 10508 Introduced in BR9.0

External NACC timer RI, this parameter is related to the features 'External NACC' (see parameter ENACCE in command SET BSC [BASICS])' and 'RAN Information Management' (RIM). RIM comprises signaling procedures executed between two BSCs via the connected SGSN and which are employed whenever the 'controlling BSC' requests particular call processing information from the 'serving BSC'. ENACCTRI determines the value of the timer T(RI) which defines the maximum waiting time for RI acknowledgement for ENACC. RI is the abbreviation for 'RAN Information Send Procedure' which the 'serving' BSC starts to transfer the RIMApp information towards the 'controlling' BSC, that has previously requested this information via the 'RAN Information Request Procedure' (RIR). T(RI) is started in the serving BSC when it sends the RAN INFORMATION (RI) message towards the controlling BSC (via the SGSN) and is stopped when the RAN-INFORMATION ACK (RIA) message has been received from the controlling BSC. When T(RI) expires, the RI procedure is repeated again until the expected response is received or until the maximum number of repetitions (determined by parameter ENACCTRICM (see below)) is reached. Notes: - T(RI) is only started if an acknowledgement is required. External NACC timer RI Counter Max, this parameter determines a threshold that determines the maximum number of consecutive RI procedures. The RI procedure is repeated if it could not be successfully completed (i.e. no response / acknowledgement was received from the remote peer BSC) on the preceding attempt. For further details, please refer to parameter ENACCTRI (see above). External NACC timer RIAE, this parameter is related to the features 'External NACC' (see parameter ENACCE in command SET BSC [BASICS])' and 'RAN Information Management' (RIM). RIM comprises signaling procedures executed between two BSCs via the connected SGSN and which are employed whenever the 'controlling BSC' requests particular

br10 database engineering manual

Documents

5s sec5 5s range

5s sec5 5s 0

respective subnet masks

bidirectional continuity monitors

command create chan

command create adjc

overload regulation measures

command create ptppkf