Professional Documents
Culture Documents
# Nokia Corporation
1 (30)
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Corporation 2007. All rights reserved.
2 (30)
# Nokia Corporation
Contents
Contents
Contents 3 List of tables 4 List of figures 5 Summary of changes 7 1 1.1 1.2 1.3 1.4 2 2.1 2.2 3 Satellite Abis 9 Configuration requirements 12 File descriptions in Satellite Abis 13 Effects of Satellite Abis on interfaces 14 Recommendations 14 Activating and testing Satellite Abis 17 Activating Satellite Abis 17 Testing Satellite Abis 26 Deactivating and testing Satellite Abis 29
# Nokia Corporation
3 (30)
List of tables
4 (30)
# Nokia Corporation
List of figures
# Nokia Corporation
5 (30)
6 (30)
# Nokia Corporation
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.
Steps for activating and checking Acoustic Echo Canceller have been added. The patching instructions for timer T3141 have been removed.
Added that standard SGSN is used with Satellite Abis. A sentence about EGPRS Dynamic Pool was added to Configuration requirements. Information on UltraSite and MetroSite was added to File descriptions in Satellite Abis.
# Nokia Corporation
7 (30)
Recommendations on GPRS and EGPRS parameter values have been added to Effects on interfaces in Satellite Abis. A paragraph on defining the BSC to satellite Abis use only has been deleted from Recommendations.
Activating and testing Satellite Abis
Instructions on activating Satellite Abis in UltraSite or MetroSite EDGE BTS have been added. Figure Signal Timing selection from Traffic Manager has been added. Added that GPRS and EGPRS capable mobile phones, and an operational Packet Core Network are needed while testing Satellite Abis. Step 5, make data calls, has been added to the testing instructions.
Deactivating and testing Satellite Abis
Information on deactivating GPRS and EGPRS in satellite Abis has been added to step 1.
8 (30)
# Nokia Corporation
Satellite Abis
Satellite Abis
Satellite Abis enables you to create coverage of the network in areas where the coverage could not be otherwise implemented due to the limitation of transmission media. Satellite circuits are useful when connecting extremely remote locations, but also when no other transmission means exist. The Satellite Abis is an application software intended for connecting the BSC to remote BTSs. Typically, these remote BTSs are used in special low-capacity and temporary applications. Only a minimum number of equipment is required at the remote cells. The general arrangement of the Satellite Abis connection is presented in Figure 1 Satellite link in the Abis interface.
# Nokia Corporation
9 (30)
Satellite
BTS
BTS
Abis interface
MSC-HLR interface
Figure 1.
To support satellite BSC-BTS circuits, Satellite Abis enables a connection of BTSs to a BSC over a transmission path. The main drawback of a (geostationary) satellite circuit is the relatively long one-way end-to-end delay of approximately 260 - 280 ms. As for bit error (BER) performance, the satellite circuits behave as radio links with a possibility of deep fades even down to the total loss of the signal. Long delay together with bit errors decreases signalling message throughput. BSC and BTS parameters and timers are adapted for the long delay. Tests using satellite circuits have shown the following: 1. The delay slows down all signalling traffic which needs frequent handshakes. GSM system timers are not designed for long delays, and they must be set correctly. The TRAU frame time alignment function does not tolerate long delays. The time alignment function forms a control loop between the transcoder and the BTS, and with excessive delay this control loop becomes unstable.
2.
10 (30)
# Nokia Corporation
Satellite Abis
Satellite Abis is an application software Satellite Abis can be utilised either on Abis or Ater interface Satellite Abis is introduced per BSS Satellite Abis is activated by a parameter switch in the BSC and the BTS Standard mobile phones are used Standard MSC is used Standard SGSN is used There are no alarms involved in Satellite Abis
Test and Activate . Transmission . Activating and testing Satellite Abis . Deactivating and testing Satellite Abis
References . Commands . MML Commands . DF - Memory File Handling . EG - GSM Timer and BSC Parameter Handling . EQ - Base Transceiver Station Handling in BSC . ER - Transceiver Handling . EV - BCF Hardware Database Handling . EW - BCF Software Handling . WO - Parameter Handling . Parameters . BSS Radio Network Parameter Dictionary
# Nokia Corporation
11 (30)
1.1
Configuration requirements
Satellite Abis in ETSI and ANSI networks
Networks based on European ETSI standards are mainly discussed here. Satellite Abis is also available in networks based on American ANSI standards. Where differences arise because of ANSI standards, these are separately mentioned. The satellite equipment must be compatible with Nokia GSM equipment and thus fulfil the following prerequisites in the Abis satellite link:
Networks based on ETSI standards
.
Interfaces operate at the bit rate 2 Mbit/s. Typically only some time slots of the 2 Mbit/s trunk carry traffic. The BTS - BSC connection is transparent for these time slots, and satellite transmission capacity is reserved only for these time slots. The minimum transmission capacity requirement is two 64 kbit/s time slots per one TRX. The normal requirement is two and a half time slots per one TRX. EGPRS Dynamic Abis Pool provides additional transmission capacity which is required by higher packet data bitrates. Interface must comply with ITU-T Recommendation G.703. Framing must comply with ITU-T Recommendation G.704. HDB3 line coding must be used. Line impedance must be 75 or 120 ohms. The use of CRC-4 error detection is recommended. The bit error ratio (BER) must always be better than 3x10E-5 over the BTS - BSC path and typically better than 10E-6.
Interfaces operate at the bit rate 1.5 Mbit/s. Typically only some time slots of this trunk carry traffic. The BTS - BSC connection is transparent for these time slots, and satellite transmission capacity is reserved only for these time slots. The minimum transmission capacity requirement is two 64 kbit/s time slots per one TRX. The normal requirement is two and a half time slots per one TRX. EGPRS Dynamic Abis Pool provides additional transmission capacity which is required by higher packet data bitrates. Interface and framing must comply with ANSI Recommendation T1.403. B8ZS line coding must be used. Line impedance must be 100 ohms.
12 (30)
# Nokia Corporation
Satellite Abis
The use of CRC-6 error detection is recommended. The bit error ratio (BER) must always better than 3x10E-5 over the BTS BSC path and typically better than 10E-6.
1.2
From the version B10.0 onward a special Satellite Abis software build is needed. For example, GSM/DCS BTS SW B10.0 contains two master files; the first (BTS_S301.101) is intended for regular Abis, and the second (BTS_S301.033) is intended for Satellite Abis. FUC configuration files are also different for regular Abis and Satellite Abis; for example, CFG_S301.101 is intended for regular Abis, and CFG_S301.033 is intended for Satellite Abis.
Nokia Talk-family BTS (DE34/DF34) or Nokia PrimeSite BTS (DE45/DF45)
From the version DF2.1 onward a special Satellite Abis software build is needed. For example, GSM/DCS BTS SW DF3.0 contains two master files; the first (BTS_S301.180) is intended for regular Abis, and the second (BTS_S301.19B) is intended for Satellite Abis. FUC configuration files are also different for regular Abis and Satellite Abis; for example, CFG_S301.18F is intended for regular Abis, and CFG_S301.199 is intended for Satellite Abis.
Nokia Ultrasite or Metrosite EDGE BTS
There is no separate master file in BTS SW build of Ultrasite and Metrosite Base Stations for satellite Abis.
Nokia Flexi EDGE BTS
Satellite Abis is not compatible with Nokia Flexi EDGE BTS SW EP1.0. However, it can be used with the software version EP2.0
# Nokia Corporation
13 (30)
1.3
Parameter BS_CV_MAX to value 15. Mobile entering to countdown procedure is based on BS_CV_MAX. The parameter determines how many radio block periods the countdown procedure lasts in the end of an UL TBF. The optimal value depends on BSS RLC Round Trip Time, which is large in case Satellite Abis is used. Timer T3192 value to 1 s. The MS uses this timer to determine how long to monitor PACCH after the end of a TBF. Timer T3141 to value 1500 ms. BSS uses this timer to determine how long to wait for an MS response to TBF establishment on CCCH. Parameter CMAX to value 1%. BSS uses this parameter to determine the maximum GPRS/EGPRS territory size. Using more than one GPRS/ EGPRS timeslot will increase the abnormal TBF release probability.
1.4
Recommendations
Because of the cumulative speech delay, it is recommended that only one satellite hop is used at the same time in a GSM/DCS network. However, it is possible to use MSC - MSC (or MSC - HLR) satellite circuits simultaneously, but this situation has to be taken into special consideration. Further, public switched telephone network (PSTN) may use satellite circuits as well and this should be avoided if possible.
14 (30)
# Nokia Corporation
Satellite Abis
The GSM system delay added to satellite path delay results in a delay (of echo) of approximately 180 ms + 520 ms = 700 ms. This exceeds the values given in the ETSI Recommendation ETS 300 903 and the ITU-T Recommendation G.114. If you (the telephone user) are aware of the delay, and (preferably) use echo control, the delay typically causes no harm. A remote MS to remote MS call suffers a double delay (1400 ms) due to the double satellite hop. It is highly recommended to use acoustic echo cancelling equipment in satellite BSS to avoid problems with speech intelligibility due to long delay. Both the TCSM2 and the TCSM3i can support AEC with the Satellite Abis. In TCSM3i there are no restrictions caused by the limited memory capacity. It is not recommended to allow handovers between satellite cells and terrestrial cells due to possible frequency differences between these systems. Timing depends on varying doppler shifts of the satellite system used. A typical doppler uncertainty is less than 2x10E-7. Using a BTS with an internal clock (MCLU clock unit) will avoid this timing problem, but regular clock unit maintenance may be difficult. As the BSC - BTS/TRX signalling capacity is reduced, any unnecessary signalling should be avoided. However, some signalling cannot be avoided because the network elements depend on a common MSC. You can reduce the signalling load in the following ways:
.
Periodic location updating: Disable the periodic location updating procedure or define it for a 24-hour interval. Unnecessary paging: Define for satellite cells a location area of their own. Disable intra-BTS handovers (EIC = N, EIH = N). MML commands affected: EHG, EHO, EHC.
The call processing capacity of a busy hour call attempt (BHCA) is 70% of normal GSM capacity in a satellite Abis link. This can be balanced by using more TRXs (and SDCCH capacity) than are normally needed.
# Nokia Corporation
15 (30)
16 (30)
# Nokia Corporation
Note
Satellite Abis is an application software product. It is not included in the standard BSC software.
Note
It is recommended to use the default values in GSM (BSC and MSC) system timers. Lower values than the default ones may be inadequate for handling the delay of the satellite connection.
For deactivation instructions, see Deactivating and testing Satellite Abis. For an overview, see Satellite Abis.
2.1
Steps
1. Activate Satellite Abis (WOC). Set the value of PRFILE parameter SATELL_ABIS_IN_USE to 'TRUE'.
# Nokia Corporation
17 (30)
ZWOC:10,31,FF; 2. Check Satellite Abis (WOI). ZWOI:10; 3. Activate Acoustic Echo Canceller (WOA). ZWOA:2,371,A; 4. Check Acoustic Echo Canceller (WOS). ZWOS:2,371; 5. Configure sufficient SDCCH capacity. To implement this step, choose one of the following alternatives:
Steps
i. In TRX1, two time slots are defined for signalling: a combined BCCH and SDCCH/8 (six others are defined as TCHs). Use the following commands to configure SDCCH capacity. Lock the BTS (EQS). ZEQS:BTS=<nbr>:L; Lock the TRX1 (ERS). ZERS:BTS=<nbr>,TRX=<trx1>:L; Modify the time slots (ERM). ZERM:BTS=<nbr>,TRX=<trx1>:CH0=MBCCHC; ZERM:BTS=<nbr>,TRX=<trx1>:CH1=SDCCH; ii. In other TRXs, one time slot is defined for signalling (SDCCH/8, preferably timeslot zero) and seven others are defined as TCHs. Use the following commands. Configure SDCCH capacity (ERS, ERM). ZERS:BTS=<nbr>,TRX=<trx>:L;
18 (30)
# Nokia Corporation
ZERM:BTS=<nbr>,TRX=<trx>:CH0=SDCCH; Unlock all locked TRXs (ERS). ZERS:BTS=<nbr>,TRX=<trx>:U; Unlock the BTS (EQS). ZEQS:BTS=<nbr>:U;
Other parameters which minimise the SDCCH reservations:
. . .
Number of Slots Spread Trans (SLO) = 32 Max. Number of Retransmission (RET) = 2 Max Number of Repetition (NY1) = 5
To set these parameters, use the command ZEQM:BTS=<nbr>:SLO=32,RET=2,NY1=5; Here <nbr> identifies the remote BTS. 6. Configure TCSM. You can configure the TCSM either locally or remotely. Remote access is recommended. The following instructions give the commands for remote access.
Before you start
Steps
a. Create the remote session (DDT). ZDDT:TCSM,<nbr>;
Username Password EXPERT SYSTEM
Here <nbr> is the address of the transcoder. b. Disable TRAU frame alignment in TCSM (ZRS).
ZRS:ALL:OFF
# Nokia Corporation
19 (30)
Do you want configuration changes to be permanent by saving them in flash memory? Please answer (Y/N) Y
Further information
TCSM is activated by enabling the parameter on/off per BSC. In TCSM the time alignment can be turned off from the command menu. Because of the fixed MS timers, there may be re-attempts in the signalling, causing limitations to the capacity of these cells. c. Enable acoustic echo cancelling (AEC) (RU).
ZRU:ALL: <codec_type>=ON;
Please, confirm (Y/N) Y Do you want configuration changes to be permanent by saving them in flash memory? Please answer (Y/N) Y
Note
The command depends on the type of speech coding used.
d.
Further information
Normally either 520 ms, 540 ms or 560 ms are suitable values for <delay>. You can check this with a listening test. e. Check that all selections are correct (RC). ZRC:<PCM_index>:10; <PCM_index> is the actual PCM used f. Terminate the remote session.
20 (30)
# Nokia Corporation
ZX
7.
Activating Satellite Abis in a Nokia 2nd generation BTS (DE21/DF12). Use the version 2.3 or later of the BTS OMU EPROM.
Before you start
Before activating Satellite Abis in a Nokia 2nd generation BTS (DE21/ DF12), the remote BTSs must be configured for satellite use by editing the HW database.
Steps
a. Give the timer value. In the HW database, give the System defs / LAPD T200 timer the value 1000 ms using the HW database editor.
Further information
Normally T200 = 240 ms, which is the value used when T200 has been selected as 0. b. c. Load the Satellite Abis BTS software build in the BTS. Add new HW database (EVU, EVC, EVA, EVV). If there is an active BCF HW database in the BSC, a new satellitespecific HW database must be uploaded, created, attached and activated as follows ZEVU:<BCF_index>:NAME=<file_name>,EXT=<file _extension>; ZEVC:<HW_db_name>:NAME=<file_name>,EXT=<file _extension>; ZEVA:<BCF_index>:<HW_db_name>; ZEVV:<BCF_index>:PAS; 8. Activating Satellite Abis in a Nokia Talk-family BTS (DE34/DF34) or Nokia PrimeSite BTS (DE45/DF45).
Before you start
# Nokia Corporation
21 (30)
There are no firmware requirements. Before activating Satellite Abis in DE34/DF34, remote BTSs must be configured for satellite use by editing the HW database.
Steps
a. b. In the HW database, select the BCF/Units window. Select the Abis type as Satellite.
Further information
This will further show the default satellite Abis value for LAPD T200 timer = 1000 ms. Normally, Abis type is normal and T200 = 240 ms. c. d. Load the Satellite Abis BTS software build in the BTS. Add new HW database (EVU, EVC, EVA, EVV). If there is an active BCF HW database in the BSC, a new satellitespecific HW database must be uploaded, created, attached and activated as follows ZEVU:<BCF_index>:NAME=<file_name>,EXT=<file _extension>; ZEVC:<HW_db_name>:NAME=<file_name>,EXT=<file _extension>; ZEVA:<BCF_index>:<HW_db_name>; ZEVV:<BCF_index>:PAS;
Further information
The HW database activation procedure is similar for both Nokia Talk-family (DE34/DF34) and Nokia 2nd generation (DE21/DF12) BTS types. 9. Activating Satellite Abis in UltraSite or MetroSite EDGE BTS.
Before you start
22 (30)
# Nokia Corporation
Before activating Satellite Abis in an UltraSite or MetroSite BTS, remote BTSs must be configured for satellite use by editing the Traffic Manager. Traffic Manager editor is in Ultrahub Manager for Ultrasite and in BTS Manager for Metrosite.
Steps
a. From the Ultrahub Manager, open the Traffic Manager. In the Configuration menu of the Nokia UltraSite BTS Hub Manager, select the Traffic Manager command. The Traffic Manager window is displayed. b. In Traffic Manager window, select the Signal Timing as 'Satellite'.
Figure 2.
c. 10.
BS CV MAX parameter
Set BS_CV_MAX to value 15: ZEGP:14:15; After 5 minutes, disable and then re-enable GPRS in the cells where GPRS is active for the change to take effect. Check the modified parameter: ZEGO:PAR:;
Timer T3192
# Nokia Corporation
23 (30)
Set timer T3192 to value 1s: ZEGT:T3192:1,1:; After 5 minutes, disable and then re-enable GPRS in the cells where GPRS is active for the change to take effect. Check the modified parameter: ZEGO:TIM:;
Note
The patching instructions for timer T3141 are valid only for S12 1.39-0 build.
OMU FILE N:O 00FF0000 RECORD N:O 000000F4 002E 0006 0320 0005 0005 000F 0004 0008 07D0 07D0 07D0 0BB8 0004 00C8 0000 0002 COMMAND EXECUTED
DO YOU WANT THESE SUBSTITUTIONS TO BE DISTRIBUTED ? ( Y = YES, N = NO ): Y BSC3i BSC12 2007-01-23 08:17:13
OMU
24 (30)
# Nokia Corporation
RECORD/STRING SUBSTITUTED
DISTRIBUTION IS STARTING
DISTRIBUTION DONE
OMU FILE N:O 00FF0000 RECORD N:O 000000F4 002E 0006 05DC 0005 0005 000F 0004 0008 07D0 07D0 07D0 0BB8 0004 00C8 0000 0002 COMMAND EXECUTED
CMAX parameter
Set CMAX to value 1%. To modify CMAX parameter, GPRS must be disabled in the cell first: EQV:BTS=<bts number>:GENA=N; Set CMAX to value 1% and enable GPRS: EQV:BTS=<bts number>:CMAX=1,GENA=Y;
Further information
# Nokia Corporation
25 (30)
2.2
Whole BSS dedicated for the satellite cells (correctly set up for Satellite Abis) An operational MSC An operational Packet Core Network Mobile stations (GPRS and EGPRS capable mobile phones) Transmission circuits to and from the operational satellite terminals
As regards pretesting or troubleshooting, if no real satellite circuits are available, the satellite may be simulated by suitable test equipment (adding a one-way delay of 280 ms and possibly also bit errors).
Steps
1. Create the correct BTS SW version. ZEWC:<package_name>:MF=<master_file_name>, EXT=<file_ extension>,SDIR=<subdirectory>; 2. Attach BTS SW version. ZEWA:<BCF_index>:<package_status>:<package_name>;
Expected outcome
The BTS software is downloaded to the remote BTS after the software build attachment.
Note
If BTS SW is downloaded via satellite Abis, the download time is 4 to 5 times longer than normal SW download due to the slowness of satellite Abis.
3.
26 (30)
# Nokia Corporation
ZEWV:<BCF_index>:<package_status>; 4. Make test calls. Make mobile-originated (MO) and mobile-terminated (MT) test calls to test the system
Expected outcome
Satellite delay will increase call set-up time by approximately 7 seconds. You can hear the increased speech delay. Some UL echo may occur depending on the acoustic performance of the mobile phone. If you use AEC, no echoes should be audible (if you hear echoes, however, changing the delay value may help). 5. Make data calls.
Expected outcome
Satellite delay will increase the system Round Trip Times. Throughput will be lower compared to terrestrial Abis configuration.
# Nokia Corporation
27 (30)
28 (30)
# Nokia Corporation
Further information
Typically no other parameters need to be changed. The Satellite Abis build in the BTS operates normally with the normal terrestrial Abis interface in the BSC. 3. Switch on the transcoder TRU.
ZRS:ALL=ON;
4.
Test the deactivation. A decrease in call set-up delay and speech delay indicates that Satellite Abis has been deactivated.
# Nokia Corporation
29 (30)
If special Abis test equipment is available, you can also perceive the deactivation by measurements. 5. Check that the state of LAPD timers is normal.
Further information
30 (30)
# Nokia Corporation