Y

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

Technical Support Note

<TSN Id>

Satellite Abis BSS13/BSS14

BSC/BTS S13/ S14

This document contains following type of information Informative Preventive Corrective Urgent Security Information is classified as Internal Public Customer Specific

Nokia Siemens Networks

Company Confidential

1 (1)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

Table of Contents 1. 2. 3. 4. 5. 6. Validity..........................................................................................................................................3 Compatibility / Dependencies to other products ............................................................................3 Keywords .....................................................................................................................................3 Summary ......................................................................................................................................3 Detailed description ......................................................................................................................3 Solution / Instructions ...................................................................................................................4 6.1 Parameters ............................................................................................................................4 6.2 HW aspects ...........................................................................................................................6 6.3 Recommendations .................................................................................................................7 7. Note .............................................................................................................................................8 8. References ...................................................................................................................................8 Contact:
Contact your local Nokia Siemens Networks support

Summary of changes:
25-05-2010 18-06-2010 0.1 0.2 First draft Basic comments included. TSN layout introduced.

Nokia Siemens Networks

Company Confidential

2 (2)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

Purpose
This document contains generic information about products. These can be instructions that explain problem situations in the field, instructions on how to prevent or how to recover from problem situations, announcements about changes or preliminary information as requirements for new features or releases.

1. VALIDITY
Not applicable.

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

There are no interdependencies to other products.

3. KEYWORDS
Satellite Abis, PCU1/PCU2, delay in S13/S14

4. SUMMARY
The guideline has two main parts: the first reports system limitation for Satellite Abis in BSS13 and BSS S14 for any type of PCU and BTS. This should be helpful to understand typical side effects due to introduction of satellite Abis. Besides, known optimization activities helping to improve performance of network connected via satellite Abis are collected and described. Please note it should be carefully studied case-by-case whether particular trick is applicable for given network scenario.

5. DETAILED DESCRIPTION
The table below gives overview on delay options for Satellite Abis in BSS13 and BSS14: BSS release S13 Satellite Abis S14 Satellite Abis S14 Enhanced Satellite Abis max Abis e2e one-way delay 280 msec 280 msec 420 msec PCU type PCU1 or PCU2 PCU1 or PCU2 PCU2

High (compared to terrestrial link) delay values are unavoidable for satellite connections: ~240 msec is necessary to exchange the signals travelling with the speed of light assuming the satellite is on geostationary orbit (ca. 35800 km above Earths surface), some margin is necessary for transport equipment delay and signal processing (depending on transport technology, e.g. SCPC, MCPC) what leads to overall delay in the order of (up to) 280 msec, usage of external equipment in front of BTS (e.g. Abis optimization boxes, Local switching gateways) as well as introduction of a new satellite services aiming at more efficient bandwidth utilization (e.g. DAMA) contribute to further delay, therefore a new setup is needed for satellite connections supporting delays of (up to) 420 msec.

Presence of delays going well beyond the values typical for terrestrial links has effect on all traffic types transmitted over Abis interface:

Nokia Siemens Networks

Company Confidential

3 (3)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

voice: indirectly affected mainly due to actions necessary to reduce signaling load some handovers (AMR packing/unpacking, intra-BTS) may be disabled so that voice quality is reduced data: long transmission delay (and BER) reduces user throughput (up to 50% reduction were observed) signalling: re-configuration (in terms of TRXSIG capacity and timers settings) is required otherwise success rate is reduced as handling of signaling transaction requires exchange of many information within predefined timeframe (handshaking controlled by timers)

To overcome or at least to minimize impact of long delays a dedicated settings of parameters/timers are recommended in chapter 6.

6. SOLUTION / INSTRUCTIONS 6.1 Parameters

In this chapter recommendations concerning parameters change are collected. But please also refer to chapter 3 and chapter 4 for further remarks (concerning HW interdependencies and other configuration rules being relevant for satellite Abis, respectively). CS traffic T3101_ offset: T3101 timer supervises SDCCH establishment procedure. It is started, when a channel is allocated and stopped when the MS has correctly seized the channels. If the dedicated channel is not established before T3101 expires, the allocated channel is released. When satellite Abis is used T3101 timer value shall be increased according to Abis delay i.e. T3101 (for satellite Abis) = T3101 (for terrestrial Abis) + T3101_ offset. The recommended settings of T3101 offsets are different for standard setup of Satellite Abis and for Enhanced Satellite Abis (as depend on satellite delay): T3101_ offset for Satellite Abis is recommended to be of 560 msec (i.e. 2x 280 msec) T3101_offset for Enhanced Satellite Abis is recommended to be of 840 msec (i.e. 2x 420 msec)

Note: T3101_offset is available via UTPFIL. Phone_case_table: defines maximum amount of suimultaneous SDCCH establishments in satellite Abis. In terrestrial links the equivalent parameter exists and its setting depends on TRXSIG capacity: default value for satellite Abis is the same which is currently used for 16kbit/sec terrestrial Abis, but at the same time greater TRXSIG capacity is recommended for satellite setup (i.e. at least 32kbit/sec for Satellite Abis). For enhanced satellite Abis even more conservative setting is recommended. The recommended settings of phone case table are different for standard setup of Satellite Abis and for Enhanced Satellite Abis (as depend on satellite delay): phone_case_table for Satellite Abis is recommended to be of 20, phone_case_table for Enhanced Satellite Abis is recommended to be of 10

Note: Phone_case_table is available via UTPFIL.

Nokia Siemens Networks

Company Confidential

4 (4)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

PS traffic (refer to chapter 6.2 for further details) T3141: The timer allows to supervise TBF establishment procedure on CCCH: if T3141 expires before an MS response indicating successful completion of TBF establishment is received, then the newly allocated TBF is released. For satellite link this timer should be extended from 800 msec (in case of terrestrial Abis) to 2000 msec (for Satellite Abis). Note: T3141 is available via UTPFIL T3192: This timer is used on the MS side (it is broadcasted via SysInfo) when the mobile station has received all of the RLC/MAC data blocks of a TBF. When T3192 expires, the mobile shall release the resources associated with the TBF (TFI, etc.) and begin to monitor its paging channel. The recommended setting for Satellite Abis is of 1500 msec. Note: T3192 is available via PAFILE BS_CV_MAX: This parameter is used during the countdown (CV = Countdown Value) procedure when terminating an UL TBF. The parameter determines how many radio block periods the countdown procedure lasts at the end of UL TBF: when the last data block is transmitted then MS starts transmitting the numbered sequence of radio blocks starting with BS_CV_MAX, i.e. MS will send exactly BS_CV_MAX more blocks until the UL TBF is actually completed. The setting of the parameter should reflect RTT which is large when Satellite Abis is used. The recommended setting of the parameter for Satellite Abis is of 15. Note: BS_CV_MAX is available via PAFILE PCU_PFH_FN_SYNC_TIME_MA: This parameter is used to define synchronization timeout. The longer Abis delays the more time is needed for PCU/Abis synchronization (initial time alignment and block alignment) and the value that is used for terrestrial links (3000 msec by default) is no longer sufficient. The recommended settings of PCU_PFH_FN_SYNC_TIME_MA are different for standard setup of Satellite Abis and for Enhanced Satellite Abis (as depend on satellite delay): PCU_PFH_FN_SYNC_TIME_MA for Satellite Abis is recommended to be of 5000 msec, PCU_PFH_FN_SYNC_TIME_MA for Enhanced Satellite Abis is recommended to be of 9000 msec,

Note: PCU_PFH_FN_SYNC_TIME_MA is available via UTPFIL. CMAX: This parameter is used to define maximum PS territory. It is recommended to keep PS territory equal to 1 RTSL in case of PCU1 and 2 RTSL in case of PCU2 otherwise Abis synchronization becomes an issue (block alignment and time alignment). Note: CMAX is set per BTS object. LAPD acknowledgment T200: This timer is used to define waiting time for LAPD acknowledgment frames: if the acknowledgement is not received before expiry of T200 the transmission of the frame is repeated and T200 restarted (unless the max number of repetitions is reached). For

Nokia Siemens Networks

Company Confidential

5 (5)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

satellite links this timer should be extended from 240 msec (in case of terrestrial Abis) to 1000 msec (for Satellite Abis) or 1300 msec (for Enhanced Satellite Abis). Note: This can be done by selection of a proper number of LAPD Parameter Set (parameterSetNumber is a parameter in LAPD object): 1 denotes Satellite Abis, 7 Enhanced Satellite Abis (0 terrestrial Abis). K (window size): This parameter defines the number of subsequent LAPD frames that may be sent without any acknowledgement from the opposite side. To reduce LAPD bandwidth (by reduction of the amount of acknowledgment messages) it is recommended to increase the window size from 2 (in case of terrestrial Abis) to 7 (in case of Satellite Abis) or 14 (in case of Enhanced Satellite Abis). Note: This can be done by selection of a proper number of LAPD Parameter Set (parameterSetNumber is a parameter in LAPD object): 1 denotes Satellite Abis, 7 Enhanced Satellite Abis (0 terrestrial Abis). Window size extension is only done for TRXSIG messages which are recognized by means of SAPI identifier (i.e. SAPI = 0 denotes TRXSIG message).

6.2 HW aspects
PCU HW PCU1 supports Satellite Abis delays up to 280 msec does not have predefined Satellite Abis implementation, i.e. all related parameters (T3141, T3192, BS_CV_MAX, PCU_PFH_FN_SYNC_TIME_MA must be set manually); also Abis interface type must be specified explicitly (in case of Satellite Abis: AIT = S) it is recommended to keep PS territory size of 1 RTSL (this must be ensured by CMAX planning as it depends on number of EGPRS-capable RTSL in the BTS) these principles are valid regardless on BTS type

PCU2 supports Satellite Abis delays up to 280 msec or up to 420 msec (depending on BTS type and SW release), uses predefined set of parameters related to Satellite Abis so they are set automatically when AIT = S; satellite setting for LAPD is also set automatically, it is recommended to keep PS territory size less than or equal to 2 RTSL (this must be ensured by CMAX planning as it depends on number of EGPRS-capable RTSL in the BTS)

BTS HW TalkFamily requires separate master files for terrestrial (BTS_S301.180) and satellite (BTS_S301.19B) Abis

UltraSite / MetroSite

Nokia Siemens Networks

Company Confidential

6 (6)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

no separate master files needed

FlexiEDGE BTS - S14 SW EP1.0: does not support Satellite Abis - S14 SW EP2.0: support for Satellite Abis - S14 SW EP3.0: support for Enhanced Satellite Abis

6.3 Recommendations
Apart from modification in parameters (described in chapter 6.1 with comment given in chapter 6.2) additional actions are recommended mainly to reduce signaling load. TRXSIG capacity is crucial requirement for Satellite Abis links: it is recommended to create links at least with capacity of 32 kbit/sec (the higher TRXSIG capacity the better signalling efficiency) to reduce probability of queuing the LAPD messages in a transmission buffers. The signalling load on satellite link can be reduced in the following ways: - reduce number of handovers disable intracell HOs (e.g. UL/DL interference, AMR packing/unpacking) if a site with satellite Abis has neighbours with terrestrial links then traffic management can be additionally introduced: apart from avoidance of intracell HO, the intercell HO towards sites with terrestrial links can be easier executed; besides harder HO hysteresis can be set to avoid ping-pong HOs Note: disabling of intracell HO will reduce voice quality but increase call drop statistics - reduce number of location updates disable periodical registration or select infrequent rate (e.g. once per day) - reduce unnecessary paging sites being connected via Satellite Abis can form their own Location Area Note: this activity becomes counterproductive if the resulting Location Area is small (and there are numerous adjacent sites connected via terrestrial links); in such case signalling load produced by Location Updates can be greater than savings from paging. The actions above aim in reduction of the number of signalling messages which are exchanged on Satellite Abis. As mentioned above these actions may affect voice quality (especially disabling of handovers) but they improve call success rate. Other activities that can help are related to configuration of signalling in radio interface. They do not have direct impact on signalling load in Abis interface but may increase call success rate in Satellite Abis environment: In case of Satellite Abis it is recommended to configure SDCCH channels on each and every TRX. This will allow to avoid an excessive concentration of the SDCCH signalling within one TRX and in one TRXSIG in consequence. The combination of TRXSIG capacity increase and balanced SDCCH load contributes to better signaling efficiency in Satellite Abis. In case of Satellite Abis it is recommended to set the longest possible RACH retransmission cycle as it avoids unnecessary retransmissions that lead to additional SDCCH seizures and thus to a decrease of the Immediate Assignment success rate or even to SDCCH congestion. This can be done by setting Number of Slots Spread Transmission to value 32. The Number of Slot Spread Transmission determines the period for retransmission of RACH accesses, i.e. it determines the time an MS must wait after a RACH access attempt before a new one can be started. In the mobile the retransmission mechanism is continuously executed after the first RACH access and only stopped if an Immediate Assignment message is received via the AGCH. In the

Nokia Siemens Networks

Company Confidential

7 (7)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

normal and successful case, the MS receives the Immediate Assignment Command before a second access attempt is started. However, under specific conditions e.g. in case of long propagation delay typical for Satellite Abis the Immediate Assignment message may not arrive on time before the MS sends the next Random Access attempt. At the same time, to maximize probability of successful assignment, it is recommended to set Number of RACH Retransmission (RET) to the maximum possible value which is 7. In case of Satellite Abis it is recommended to disable queuing by setting Max Queue Length (MQL) to 0. This will be helpful to reduce call setup time and as a result to reduce SDCCH seizure time what corresponds to SDCCH load and signalling efficiency.

7. NOTE
Not applicable

8. REFERENCES
/1/ BSS14ED CR_005 E. Rty, H. Tervonen, A. Mannila: Enhanced satellite support up to 420 ms delay (BSS21497) /2/ Activating and testing BSC4040: Satellite Abis, DN9812652, issue 6-4 BSS1e

Nokia Siemens Networks

Company Confidential

8 (8)

PD

F T ra n sf o

rm

PD

F T ra n sf o

rm

er

er

ABB

ABB

bu

bu C lic k he re to
w

y
w.
A B B Y Y.c

2.0

2.0

lic

he

re
om

to

w.

A B B Y Y.c

om

Disclaimer 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 2010. All rights reserved.

Nokia Siemens Networks

Company Confidential

9 (9)