Documente Academic
Documente Profesional
Documente Cultură
1 (25)
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2008. All rights reserved.
2 (25)
Contents
Contents
Contents 3 List of tables 4 List of figures 5 Summary of changes 7 1 2 3 3.1 3.2 3.3 4 Overview of Soft Channel Capacity 9 Requirements for Soft Channel Capacity 11 Technical description of Soft Channel Capacity 13 BSC radio network configuration with Soft Channel Capacity Radio channel allocation with Soft Channel Capacity 14 Interworking 16 User interface of Soft Channel Capacity 23 13
3 (25)
List of tables Table 1. Table 2. Table 3. Table 4. Maximum number of TCHs per BCSU 13 14
Maximum number of simultaneously active TCHs per BCSU Number of active TCHs depending on the activation type Soft Channel Capacity interworking 17 15
4 (25)
List of figures
List of figures Figure 1. Figure 2. Example of active traffic channel limits per BCSU Example of cell capacity assurance algorithm 16 14
5 (25)
6 (25)
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.
7 (25)
8 (25)
Requirements for Soft Channel Capacity Technical description of Soft Channel Capacity User interface of Soft Channel Capacity
Functional descriptions . Radio network performance . Radio Channel Allocation . Traffic Reason Handover in BSC . RF Power Control and Handover Algorithm . Operability . Radio Network Recovery and State Management
9 (25)
Feature descriptions . Radio network performance . GSM-WCDMA Interworking . Common BCCH Control in BSC . Enhanced Speech Codecs: AMR and EFR . Direct Access to Desired Layer/Band . Data . GPRS/EDGE . HSCSD and 14.4 kbit/s Data Services in BSC . Value added services . Wireless Priority Service . Trunk reservation Product descriptions . Product Description of Nokia BSC2i and BSCi High Capacity Base Station Controller . Product Description of Nokia BSC3i High Capacity Base Station Controller Operate and maintain . Nokia BSS Transmission Configuration Install and upgrade . Software . Licensing in BSC Reference . Alarms . Base Station Alarms (70007999) . Counters/performance Indicators . Circuit-switched measurements . 1 Traffic Measurement . 2 Resource Availability Measurement . 109 Soft Channel Capacity Measurement . Parameters . BSS Radio Network Parameter Dictionary . Printouts/error codes . General Error Messages of System
10 (25)
11 (25)
12 (25)
3
3.1
BSC3i 1000/2000
With these new limits it is possible to configure all radio traffic timeslots to dual rate (DR) support. Increasing the limits means that more TCHs can be created in the radio network than are allowed to be activated simultaneously. This is extra TCH capacity.
13 (25)
3.2
Maximum number of simultaneously active TCHs per BCSU Number of simultaneously active TCHs in the BCSU
512 880 1600
BSC3i 1000/2000
The number of active TCHs per BCSU is maintained in the BSC. The radio resource management part of the BSC controls the usage of TCHs. If the number of active TCHs in the BCSU reaches the limit value, it is not possible to activate a new TCH in the TRXs controlled by that BCSU until an active TCH has been released. Figure Example of active traffic channel limits per BCSU gives an example of activeTCH limits per BCSU in BSC2i.
BSC2i BCSU 1 BCSU 1: 600 TCHs created 512 TCHs active BCSU 2: 500 TCHs created 500 TCHs active BCSU 3: 600 TCHs created 450 TCHs active
BCSU 2
BCSU 3
Figure 1.
14 (25)
In the example, it is not possible to allocate a TCH in TRX 1 or in TRX 2. In BCSU 1 the maximum number of TCHs is already activated. In BCSU 2 all the TCHs are already activated. It is possible to allocate a TCH only in TRX 3. If TRX 3 happens to be in use already, it is not possible to allocate a TCH in the cell even if there were free channels in TRX 1. The principles of calculating the number of active TCHs are described in table Number of active TCHs depending on the activation type.
Table 3.
Number of active TCHs depending on the activation type Number of active TCHs
1 1 2 3 4 1 1 1
Activation type
Full rate single slot CS call Half rate single slot CS call 2-timeslot multislot CS data call 3-timeslot multislot CS data call 4-timeslot multislot CS data call GPRS/EDGE territory timeslot Dynamic SDCCH timeslot CS connection of a DTM call
Cell capacity assurance The cell capacity assurance algorithm ensures that a sufficient number of TCHs can be activated in each cell of the network at any time even if extra TCH capacity has been created in the radio network. This algorithm assures that the minimum number of the calls that can be set up in each cell of the network at any time is equal to the number of the created TCH timeslots in the cells, that is, the cell capacity assurance level is 100%. Figure Example of cell capacity assurance algorithm describes the cell capacity assurance algorithm.
15 (25)
BSC2i BTS 1: assured capacity 6 TCHs 2 active TCHs BTS 1 TRX 1 BCSU 1 BTS 3 TRX 3 BTS 3: assured capacity 6 TCHs 2 active TCHs
BTS 2 TRX 2
BCSU 2
BCSU 1: 600 TCHs created 500 TCHs active BCSU 2: 500 TCHs created 490 TCHs active
Figure 2.
The assured TCH capacity of BTS 1, 2, and 3 together is 18 TCHs. Only 6 TCHs are currently active in those BTSs. The maximum number of simultaneously active TCHs in BCSU 1 is 512. Of those, 500 are already active. Therefore, it is not possible to activate a TCH in TRX 4 of BTS 4. The free resources of BCSU 1 must be saved for BTSs 1, 2, and 3 to assure sufficient number of calls in each of the BTSs. In BTS 4, it is possible to allocate a TCH only in TRX 5 at the moment.
3.3
Interworking
The extra TCH capacity created in the radio network has effects on various operating and application software in the BSC. The effects are described in table Soft Channel Capacity interworking.
16 (25)
Table 4.
Basic/application software
Congestion time
GPRS/EDGE margins
The GPRS/EDGE territory upgrade and downgrade decisions are based on the number of idle timeslots in the BTS. If extra TCH capacity has been created in the BTS, the downgrade margin does not work optimally. The GPRS/EDGE territory downgrade caused by the increasing CS traffic is not started as early as without extra TCH capacity. The effects can be reduced by setting the BSC parameters free TSL for CS upgrade (CSU) and free TSL for CS downgrade (CSD) to maximum values.
17 (25)
Table 4.
Basic/application software
Wireless Priority Service (WPS)
The BSC checks the cell resource usage of the target cells based on the BSC parameters WPS priority capacity (WPIC) and WPS preference capacity (WPEC). If extra TCH capacity has been created in the cell, it is possible that a Directed Retry handover for a queued WPS user is started to a cell which actually is congested and the WPS call setup is interrupted. This situation can be avoided by reducing the values of the WPIC and WPEC parameters. The values of these parameters should be reduced in relation to the amount of extra TCH capacity in the network. If the number of TCHs has been doubled in the network, the values of the parameters should be halved. For more information, see Wireless Priority Service under Feature descriptions/Value added services and BSS Radio Network Parameter Dictionary under Reference/Parameters in the PDF view..
18 (25)
Table 4.
Basic/application software
BSC-initiated Traffic Reason Handover (BSC-initiated TRHO)
MSC-initiated TRHO
The BSC reports the number of idle TCHs in the cells to the MSC. If extra TCH capacity has been created in the cell, it is not necessarily possible to allocate all the reported idle channels of a cell simultaneously. As a consequence, the MSC may start handovers from one congested cell to another. For more information, see Traffic Reason Handover in BSC under Functional descriptions/ Radio network performance in the PDF view.
19 (25)
Table 4.
Basic/application software
Direct Access to Desired Layer/ Band (DADL/B)
The load distribution between different BTSs in a segment is controlled with the BTS parameter BTS load in SEG (LSEG). For each call, the BSC checks the resource usage of each BTS of the target segment based on the LSEG parameter. The BSC then decides to which BTS the call is directed. The aim is to keep the load of each BTS within the limit that the LSEG parameter defines. If extra TCH capacity has been created in the segment, the calls are not directed, for example, to a non-BCCH layer of the segment as early as without extra TCH capacity. The effects can be minimised by adjusting the value of the LSEG parameter. The value of the LSEG parameter should be reduced in relation to the amount of extra TCH capacity in the network. If the number of TCHs has been doubled in the BTS, the value of the parameter should be halved. However, if the value of the LSEG parameter has already been set to a low value (about 10% or lower), there is not necessarily any need to change the value. In this case the load distribution between layers in the segment works well also with the extra TCH capacity. For more information on the load distribution between the BTSs of the segment, see Common BCCH Control in BSC under Feature descriptions/Radio network performance in the PDF view.
20 (25)
Table 4.
Basic/application software
Dynamic SDCCH reconfiguration
ISHO from a GSM to a WCDMA RAN cell for speech calls is started on the basis of the traffic load in the serving GSM cell. The load in the serving cell is checked with the handover parameter min traffic load for speech call (LTSC). The handover is not started until the load in the serving cell exceeds the threshold. If extra TCH capacity has been created in the serving cell, the handovers to the WCDMA RAN cell are not started as early as without extra TCH capacity. The effect can be minimised by reducing the value of the LTSC parameter. The value of the LTSC parameter should be reduced in relation to the amount of extra TCH capacity in the network. If the number of TCHs has been doubled in the cell, the value of the parameter should be halved. For more information on ISHO, see GSMWCDMA Interworking under Feature descriptions/Radio network performance in the PDF view.
Trunk Reservation
Trunk Reservation does not work optimally if extra TCH capacity has been created in the BSC. The trunk reservation algorithm takes into account all the created radio interface TCHs. If extra TCH capacity has been created in the BSC, the trunk reservation algorithm cannot ensure that there is always capacity available for the priority user in a cell. For more information, see Trunk Reservation under Feature descriptions/Value added services in the PDF view.
21 (25)
Table 4.
Basic/application software
Radio network recovery
22 (25)
For more information on the command groups and MML commands, see MML commands under Reference/Commands in the PDF view. Error codes
.
With this error code, the BSC informs you that the maximum amount of soft channels in the BSC is exceeded.
.
With this error code, the BSC informs you that there are more soft channels configured in the BSC than the AMR HR licence allows.
.
With this error code, the BSC informs you that Soft Channel Capacity is not in use in the BSC.
23 (25)
For more information, see Licensing in BSC under Install and upgrade/ Software and General Error Messages of System under Reference/ Printouts/error codes in the PDF view. Alarms 7746 CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD Soft Channel Capacity introduces a field to this alarm. For a more detailed description of the alarm, see Base Station Alarms (70007999) under Reference/Alarms in the PDF view. Counters The following counters to Soft Channel Capacity Measurement are introduced:
.
109000 PEAK BUSY TCH PER BCSU 109001 AVE BUSY TCH PER BCSU 109002 AVE BUSY TCH PER BCSU DENOMINATOR 109003 TOTAL TCH BUSY TIME PER BCSU
When Soft Channel Capacity is active and extra TCHs have been created in a cell, it is possible that a radio channel allocation attempt is rejected because of the lack of BCSU capacity even if there are free radio TCHs in the cell. In this case, the existing Traffic Measurement and Resource Availability Measurement counters are updated as if the radio channel allocation attempt was rejected because of a lack of radio resources. The following counters are an exception:
.
002026 TOTAL CHANNEL BUSY TIME 002044 FULL RATE radio CONGESTION TIME 002045 HALF RATE radio CONGESTION TIME
These counters do not show congestion time unless all the radio TCHs of the cell have been occupied.
24 (25)
For more information, see the following measurements under Reference/ Counters/performance indicators/Circuit-switched measurements in the PDF view:
.
1 Traffic Measurement 2 Resource Availability Measurement 109 Soft Channel Capacity Measurement
25 (25)