Change Note Forms

MENU
Change Note Forms

Release Delivery: EP3 MP2.0 Product Family: Base Stations Product: Flexi EDGE Base Station Release: EP3
DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 1(42)
MENU
GSM/EDGE BTS CN-id: 18704CNESPE01

Title:
Unexpected Alarm 7602 Incoming reference clock has started to deviate rapidly does not cancel
Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: In EP3 MP1.0 BTS software, alarm 7602 Incoming reference clock has started to deviate rapidly was introduced to give warning of clock synchronisation problems towards the BTS that would ultimately result in excessive dropped calls and handover failures. A problem was observed when just before EP3 MP1.0 BTS software activation, the BSC clock synchronisation was changed from internal to external and after EP3 MP1.0 activation, alarm 7602 - Incoming reference clock has started to deviate rapidly was unexpectedly raised and did not cancel. The alarm was raised because the BTS oven controlled crystal oscillator (OCXO) tuning against the new incoming reference clock moved the current DAC (Digital to Analogue Converter) word by a margin greater than 408 steps (refer to LGF case NA04492455) away from the nominal DAC word (stored on the basis of the previous BSC clock synchronisation method). In EP3 MP2.0 BTS software, the alarm will be automatically cancelled when either of the following conditions is met: when the DAC value is within 405 steps from the last nominal DAC value before the reference clock started to deviate rapidly Or after the alarm is active for 48 hours, regardless of the network clock synchronisation state
MENU
NB: It is therefore possible if the operator takes no action for the alarm to cancel whilst a fault situation remains. Also in EP3 MP2.0 the alarm text will be changed to: 7602 BCF NOTIFICATION - Difference between current and last stable DAC words Solution / Workaround: The workaround is to either re-commission the Flexi EDGE BTS, or to revert to EP3 (or earlier) BTS software before activating EP3 MP1.0 BTS software. This may be considered impractical options. System Impact: Alarm 7602 Incoming reference clock has started to deviate rapidly remains active. There is no impact to BTS performance. Description of the correction: The alarm text is changed from 7602 Incoming reference clock has started to deviate rapidly (in EP3 MP1.0) to 7602- "Difference between current and last stable DAC words" (in EP3 MP2.0) and the alarm will be cancelled after 48 hours, irrespective of the network clock synchronisation state. Corrected Fault Reports: NA04605959 : Incoming reference clock has started to deviate rapidly Modified components: Alarm Database 109 Change effects: Effects on end-user None Effects on Operator Alarm is automatically cancelled after 48 hours. Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration Any Site is commissioned with RFCAD and is in Supervisory state. EP3 MP2.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP2.0 build is the active software package.
MENU
Test execution: This was validated in a customer pilot. Expected results: In EP3 MP2.0 alarm 7602 - "Difference between current and last stable DAC words" is automatically cancelled after 48 hours Unexpected results: -
MENU

Title:
Unexpected TRX Test failure with cause Gain Calibration Error in ERxx/ECxx
Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: When a TRX test is executed, the EXxx (DTRX) module sends a test signal to the ERxx (DDU) and the DDU module loops back the signal to the connected DTRX module receiver ports. A problem has been observed where if a TRX test is executed using BTS Manager (Tests | TRX Test), the TRX test may fail with the following failure reason: Gain Calibration Error in ERxx/ECxx This problem only affects certain DDU modules when high gain Mast Head Amplifiers are used. DDU modules whose serial number starts with B6 and were manufactured in week 49 and earlier are affected. The serial number will begin with B609xx, where 09 is the year and xx is the week number. E.g. B60949, B60948, B60947 etc. The DDU module serial number and manufacture date can be checked from either the barcode label on the front panel of the DDU module or from examining the hardware properties of the DDU module in BTS Manager. Solution / Workaround: In EP3 MP2.0 an updated DDU module software image for this B6 DDU module will be included. The DDU module software is automatically installed into the DDU module upon activation of EP3 MP2.0. Although EP3 MP2.0 is required to update the DDU software image, previous BTS software releases can be reverted too after the DDU module has gone through the EP3 MP2.0 activation cycle. System Impact: TRX tests fail as described.
MENU
Description of the correction: The format of the low gain state (LGS) values (when high gain MHA is used) stored in the ERxx (DDU) module were not in accordance with the hardware requirements specification. In EP3 MP2.0 the BTS software will round the stored values. Corrected Fault Reports: NA04607382 : ERPA UNIT FAIL - TRX TEST IS NOT RUNNING - SOFTWARE DEFECT Modified components: .\tom\om\h\tom_ddum_main_stm.h@@\main\ep2_trx_intg_ir2\ep2_cd1.0_trx_intg\cr11 11\2 Change effects: Effects on end-user None Effects on Operator No unexpected TRX test failures Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 4 Omni with 2-way combining with high gain Masthead Amplifier. Site is commissioned with RFCAD and is in Supervisory state. The original fault was seen with ERxx DDU Module version B6xxxx, ensure these are utilised for this testing. EP3 MP2.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP2.0 build is the active software package. Test execution: 1. Start a MS-MS CS call and a packet data transfer in the sector. 2. Start the TRX Test for TRX1 from the BSC through MML Command 'ZUBS', with testing mode as 'GMSK' and any randomly chosen timeslot. 3. Wait until the TRX Test completes then invoke the TRX Test Report for TRX1 on the BSC using MML Command 'ZUBP'. 4. Observe the CS calls and packet data transfer started in the first step. 5. Lock one of the TRX objects from the BSC. 6. Repeat steps 2 to 4 for all TRXs in the site, including the TRX object locked in Step 5. 7. Repeat steps 2 to 4 with test MODE=8PSK for all TRXs in the site. 8. Disable the RX Diversity for the sector from BSC using the MML command ZEQM. 9. Repeat steps 6 and 7. 10. Unlock the locked TRX from the BSC.
MENU
11. Run at least one MS to MS CS call on each TRX for the timeslot which was used for the TRX test. 12. Observe the active alarms on the Flexi EDGE BTS Manager and BSC. Expected results: 1. The CS calls and packet data transfers start successfully. 2. TRX Test is started successfully. 3. Verify that the TRX test is successful and that the Report is displayed at the BSC with the following contents: BCF/BTS/TRX/RTSL Number Test Result: Passed Transmitted Power Level: >= 47 dBm BER for main branch:: 0 (RF BER) Rx Sensitivity for main branch: < -110 BER for Diversity Rx branch: 0 (RF BER) Rx Sensitivity for Diversity branch: < -110 4. Verify that there is no perceptible degradation in voice quality for CS calls and packet data transfers do not show any significant drop in the data transfer rate. 5. The TRX object is locked successfully. 6. Similar results are observed. 7. Similar results are observed. 8. RX Diversity is disabled successfully. 9. TRX test Report is displayed at the BSC with the following contents: BCF/BTS/TRX/RTSL Number Test Result: Passed Transmitted Power Level: >= 47 dBm BER for main branch:: 0 (RF BER) Rx Sensitivity for main branch: < -110 BER for Diversity Rx branch: 4294967295 (i.e. Not Measured) Rx Sensitivity for Diversity branch: 254 (i.e. Cannot be measured) 10. The TRX object is unlock successfully and returns to WO state. 11. Verify that the call establishment is successful having good voice quality with no perceptible glitches/echo/noises etc. 12. There are no active alarms at the Flexi BTS Manager, or BSC. Unexpected results: -
MENU

Title:
Remote BTS Manager will not start Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: When the Flexi EDGE BTS Manager is installed on a NetAct server for remote operation, the application is installed under the user rights established for the user on the server. If the Flexi EDGE BTS Manager is installed using administrator (full read and write) rights on the server and a user with different (restricted write access) user rights attempts to use the BTS Manager application, then the BTS Manager will not start and a Windows error report message will be displayed. The problem is that the application needs to be able to write to its configuration files but this cannot be done if the user does not have write access to the BTS Manager installation directory. In EP3 MP2.0, these configuration files will be copied to the users BTS Manager home directory where write access will be possible. Solution / Workaround: Allow full user write access to the BTS Manager installation directory and sub directories. System Impact: Remote connection cannot be made to BTS sites. Description of the correction: Upon installation, Flexi EDGE BTS Manager will create EMConfiguration.xml, LocalConnectionConfiguration.xml and decrypted_ualc.policy files in the user's folder rather than in the installation folder.
MENU
Corrected Fault Reports: NA04577715 : Flexi Node Manager not working again Modified components: epem\application\src\com\nokia\ebts\eem\application\main\EMMain\epem\lib\em_Deve loperepem\lib\em_Customer \main\ep2_em_intg_ir1\ep2_em_intg_ir2\ep2_cd1.0_em_intg\ep3_em_intg\ep3_MP2.0 _em_di_preintg\5\main\ep2_cd1.0_em_intg\ep3_em_intg\ep3_MP2.0_em_di_preintg\1 \main\ep2_cd1.0_em_intg\ep3_em_intg\ep3_MP2.0_em_di_preintg\4 Change effects: Effects on end-user None Effects on Operator Improved BTS Manager stability Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration: Any Site is commissioned and in Supervisory state. Windows Node Manager is required. No Flexi EDGE BTS Manager is connected to the BTS. EP3 MP2.0 build is the active software package. Test execution: 1. Login to the PC as Administrator by providing correct credentials. 2. Install EP1.1 CD1.0 Flexi EDGE BTS manager on the PC. 3. Launch the Flexi EDGE BTS manager and connect remotely to the Flexi EDGE BTS site. 4. Login to PC as standard user, ensure user account does not have administrative rights. 5. Launch the Flexi EDGE BTS manager that was installed in step 2. 6. Repeat step 1. 7. Install EP3 MP2.0 Flexi EDGE BTS manager on the PC. 8. Repeat steps 3 and 4. 9. Repeat step 5. 10. Launch the Flexi EDGE BTS manager and connect locally to the Flexi EDGE BTS site. Expected results: 1. Successful login as Administrator. 2. Flexi EDGE BTS manager is successfully installed in the PC as administrative user.
MENU
3. Flexi EDGE BTS manager is launched successfully and is connected to Flexi EDGE BTS. BTS site is in supervisory state. 4. Login to PC as Standard User is done successfully. 5. A Connect error pop up is observed as "Connection refused. A connection already exists at the BTS. Press Stop button to abort connection attempt". 6. Similar results are observed. 7. Flexi EDGE BTS manager is successfully installed in the PC as administrative user. 8. Similar results are observed. 9. Flexi EDGE BTS manager is launched successfully and is connected to Flexi EDGE BTS. BTS site is in supervisory state. 10. Flexi EDGE BTS manager is launched successfully and is connected to Flexi EDGE BTS. BTS site is in supervisory state. Unexpected results: -
MENU

Title:
RFCAD fails after a BTS sector reset in a split DDU configuration Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: The ERxx (DDU) module is allowed to be split or shared across two BTS objects (e.g. 1+1 using 1 DDU module). The TRXs of one BTS sector are connected to the DDU module and the TRXs of the other BTS sector are connected to the same DDU module. If during commissioning the RF cables are set to be automatically detected (default option), then RF Cable Auto detection (RFCAD) will detect the connected internal RF cables between the EXxx (DTRX) modules and the DDU module. If the user later performs a BCF or BTS object reset using BTS Manager, the option to perform RFCAD can be selected. The problem is that if a BTS sector reset is performed with RFCAD, then the RFCAD execution will fail and the following alarm will be raised on both BTS objects: 7603 BTS FAULTY EXxx TRX detected no connection to ERxx DDU/ECxx RTC via RF cable autodetection Description of the correction: When using BTS Manager to perform a BTS sector reset, a pop up box will be displayed informing the user that the BTS sector reset cannot be done with RFCAD enabled due to the split DDU configuration. Solution / Workaround: If RFCAD is not required, the user can choose to make a BTS sector reset without RFCAD. If RFCAD is required, the user can select a BCF object reset with RFCAD. In this case, all BTS objects will be reset. System Impact: Unnecessary and blocking 7606 alarms
MENU
Corrected Fault Reports: 10201ESPE07 : RFCAD fails after sector reset in a 1+1 split configuration. Modified components: /main/ep3_MP2.0_em_di_preintg/1 Change effects: Effects on end-user None Effects on Operator Increased RFCAD coverage for BTS configurations Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 1+1 with DDU split between the sectors. Site is commissioned and in Supervisory state. EP2 CD3.0 Flexi EDGE BTS Manager is connected to the BTS. EP2 CD3.0 build is the active software package. Test execution: 1. Reset both BTS with RFCAD from Flexi DGE BTS Manager. Observe if any alarms are raised at Flexi EDGE BTS Manager and BSC. 2. Perform a BCF reset with RFCAD from the Flexi EDGE BTS Manager. Observe the alarms at the Flexi EDGE BTS Manager and BSC. 3. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 4. Observe the RF cable connections in first sector at base station view at Flexi EDGE BTS Manager. 5. From the Flexi EDGE BTS Manager click on reset button for first sector, enable the option to reset with RFCAD on the pop-up displayed. Click OK. 6. On the pop-up window click Yes to reset the BTS without RF Cable Autodetection. 7. Observe the RF cable connections in first sector at base station view at Flexi EDGE BTS Manager. 8. Change the RX cable connections at the ERxx DDU Module. (e.g. if RX cable for the TRX of the first sector is connected to ERxx DDU Module port RxA1, then connect it to either of RxA2, RxA3, or RxA4). 9. From the Flexi EDGE BTS Manager click on reset button for first sector, enable the option to reset with RFCAD on the pop-up displayed. Click OK. 10. After the sector resets, observe the RF cable connections in first sector from the base station view at the Flexi EDGE BTS Manager. 11. Perform a BCF reset with RFCAD from the Flexi EDGE BTS Manager.
MENU
12. Observe the RF cable connections in first sector at base station view at Flexi EDGE BTS Manager. Expected results: 1. Alarm 7603 "BTS FAULTY: EXxA detected no connection to ERxx DDU/ECxx RTC during RF cable autodetection" is raised at Flexi EDGE BTS Manager and BSC. 2. The 7603 alarm raised in step 1 is cancelled, no other alarms are seen. 3. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 4. The RF cabling is displayed correctly for the split DDU configuration. 5. A popup is observed indicating "BTS Object cannot be reset with RF Cable autodetection. This BTS Object is part of a split DDU configuration and a reset with RF Cable Autodetection will affect other BTS Objects. Do you want to reset without RF Cable Autodetection?". 6. The TRX in first sector reaches supervisory state after sector reset. 7. RF cable connections observed are same as observed in step 4. 8. RX cables are physically changed at Flexi EDGE BTS Site. 9. A popup is observed indicating "BTS Object cannot be reset with RF Cable autodetection. This BTS Object is part of a split DDU configuration and a reset with RF Cable Autodetection will affect other BTS Objects. Do you want to reset without RF Cable Autodetection?". 10. RF cable connections observed are same as observed in step 4. 11. The BCF is reset and reaches supervisory state. 12. RF cable connections are now observed as correct, i.e. the same as physically connected and not as observed in step 10. Unexpected results: -
MENU

Title:
Unexpected alarm 7601 Irrecoverable Loss of BSS Synch is raised when Flexi EDGE BTS is integrated in LMUB - UltraSite EDGE BTS chain Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: For BSS synchronisation the Location Measurement Unit (LMUB) can be installed to an UltraSite EDGE BTS > Flexi EDGE BTS chain where the LMUB is the master clock source for the BTS configuration. In normal operation the LMUB will be locked to a GPS signal and the master clock is provided for the UltraSite EDGE BTS. The UltraSite EDGE BTS then provides the clock reference for the Flexi EDGE BTS. If the LMUB loses the GPS signal for long enough such that it can no longer bridge the GPS outage with its internal oven controlled oscillator (OCXO) then the LMU can no longer be used as a master clock BTS in the chain. If configured to do so the UltraSite EDGE BTS internal clock then uses the incoming Abis as a master clock source whilst still providing the clock reference for the Flexi EDGE BTS. A problem has been identified where in the configuration mentioned above, when the incoming Abis is used a master clock source, due to the LMUB clock source becoming unavailable, the Flexi EDGE BTS raises the following alarm, even though both the BTS are in working order: 7601 BCF OPERATION DEGRADED - Irrecoverable Loss of BSS Synch The alarm is raised because the Flexi EDGE BTS is making repeated and unexpected timing adjustments when swapping between the Frame Clock (FCLK) provided by the LMU clock and the FCLK provided by the UltraSite EDGE BTS. Description of the correction: A delay is applied as an offset to the incoming LMU Frame Clock; the delay being derived from the BTS system clock. It was found however that the applied delay was calculated incorrectly - 48uS instead of the required 50uS. The incoming LMU Frame Clock offset is now 50uS.
MENU
Solution / Workaround: System Impact: An increase in synchronised handover failures and dropped call rates in the Flexi EDGE BTS. Corrected Fault Reports: 55815ESPE02 : 2us error on flexi bts when using LMU sync Modified components: /vob/epsys/som/build/ep_tools/bin/ep_som_cfg_file EP3_MP2.0_SOM_55815ESPE02_56043ESPE02_0001 Change effects: Effects on end-user None Effects on Operator Improved clock handling will not cause unexpected alarms Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration Any multi TRX LMUB-UltraSite EDGE BTS-Flexi EDGE BTS chain Sites are commissioned and are in Supervisory state. CX7 MP1.0 UltraSite BTS Manager is connected to the UltraSite EDGE BTS. CX7 MP1.0 build is the active software package on the UltraSite EDGE BTS. EP3 MP1.0 Flexi EDGE BTS Manager is connected to the Flexi EDGE BTS. EP3 MP1.0 build is the active software package on the Flexi EDGE BTS. Test execution: 1. Using UltraSite and Flexi EDGE BTS Managers, verify in the BCF Properties of all the BCFs in the chain, specifically the Clock Source and State of Oven Tuning. 2. Place one pair of CS calls on all sectors of the chain. 3. Disconnect the GPS antenna of the LMUB in the chain. Wait for the LMU Timeout timer to expire. On expiry of the LMU Timeout timer, check for any alarms reported for all BCFs in the chain at both EDGE BTS Managers and the BSC. 4. Observe the messages exchanges on the GSM Abis Analyzer. 5. Using UltraSite and Flexi EDGE BTS Managers, verify in the BCF Properties of all the BCFs in the chain, specifically the Clock Source and State of Oven Tuning. 6. At BSC, check the synchronisation mode using the command ZEFL:<bcf_id>; for all the BCFs in the chain.
MENU
7. At UltraSite EDGE BTS Manager and Flexi EDGE BTS Manager go to Transmission > Synchronisation and check the Active Source in the Transport Priority table. 8. From the UltraSite BTS Manager and Flexi EDGE BTS Manager monitor the DAC Word until it is stable. 9. Reconnect the GPS antenna at the LMU. 10. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 11. Repeat steps 1 to 8. 12. Reconnect the GPS antenna at the LMU. Expected results: 1. For all the BCFs, the following is seen: Clock Source: Slave, Oven Tuning: Enabled. 2. CS calls are placed successfully on all sectors. 3. The UltraSite sends alarm 8048 "Loss of Incoming Signal" and alarm 7602 "External Synchronization Signals Disabled" to the BSC and UltraSite BTS Manager. No alarms are raised on the Flexi EDGE BTS. 4. Clock control messages are exchanged for all BCFs. 5. For the UltraSite EDGE BTS the following is seen; Clock Source: Master, Oven Tuning: Enabled. For the Flexi EDGE BTS the following is seen; Clock Source: Slave, Oven Tuning: Enabled. 6. The Synchronisation mode is "Abis Sync" for all the BCFs in the chain. 7. For the UltraSite EDGE BTS the Active source is "Rx Clock IF1". For the Flexi EDGE BTS the Active source is "Sync Input". 8. The DAC word is considered stable when no more than a 2 total DAC Word change occurs within a 20 minutes period. 9. After few seconds, the UltraSite EDGE BTS sends the cancel for alarm 8048 "Loss of Incoming Signal" and alarm 7602 "External Synchronization Signals Disabled" to the BSC and UltraSite EDGE BTS Manager. The Flexi EDGE raises alarm 7601 Irrecoverable Loss of BSS Synch at the Flexi EDGE BTS Manager and BSC. 10. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 11. Similar results are observed. 12. After few seconds, the UltraSite EDGE BTS sends the cancel for alarm 8048 "Loss of Incoming Signal" and alarm 7602 "External Synchronization Signals Disabled" to the BSC and UltraSite EDGE BTS Manager. Unexpected results: -
MENU

Title:
External RX Diversity input to RTC (ECxx) module causes RSSI alarms Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: When co-siting Flexi EDGE BTS with another BTS, the RX Diversity cabling is shared or cross connected from one BTS to another. Flexi EDGE BTS may be configured to either provide or receive an external antenna for RX Diversity sharing. The RF cabling for such configurations is defined during commissioning. In EP3 MP1.0 the possibility to select an External BTS as a cable source exists in the Cabling Configuration | Non Auto-Detectable Cabling step. In earlier BTS manager versions it is not possible to define an External BTS as a source. A problem has been identified when RTC (ECxx) modules are used and an external RX diversity is connected to the RxExtIN port of the RTC. The RTC module is not able to take the external diversity antenna input into use and consequently the following alarms will be raised, when the alarm conditions are met: 7607 TRX OPERATION DEGRADED RSSI Detected Rx signal difference exceeding threshold 7604 BTS OPERATION DEGRADED RSSI Detected Rx signal difference exceeding threshold Description of the correction: A variable that assigns the state of external antenna value is now correctly set. Solution / Workaround: System Impact: High RSSI difference for all TRXs in the BTS resulting in above alarms and an increase in dropped calls will be observed.
MENU
Corrected Fault Reports: 43085ESPE01 : RSSI and high DCR problems on 12+12+12 MultiBCF RTC config Modified components: /vob/epsys/som/rtc/src/som_rtcm_utils EP3_MP2.0_SOM_43085ESPE01_0001 Change effects: Effects on end-user None Effects on Operator RX Diversity can be provided from an external BTS to the ECxx(RTC) modules Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 12+12 with RTC combining and BB Hopping. Site is commissioned and in Supervisory state. EP3 MP1.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP1.0 build is the active software package. Test execution: 1. Reset the Flexi EDGE BTS site from Flexi EDGE BTS Manager. 2. Fetch the RSSI values for the Flexi EDGE BTS site from the Flexi EDGE BTS Manager -> Supervision -> RSSI Comparison values. Check RSSI sample count reported. 3. Establish long duration static Circuit Switched voice calls in a common segment between two Flexi EDGE BTS sites. Note: Make sure that number of calls established on TRX object should be enough to generate RSSI samples, aim for more than three times user configured RSSI samples, i.e. 480,000. 4. Fetch and save the 'RSSI Comparison Values' from Flexi EDGE BTS Manager -> Supervision -> RSSI Comparison values and verify the 'RSSI Comparison Values' reported 10 minutes after the BCF reset performed in step 1. 5. Fetch and save the Site Information Report and verify 'RSSI Comparison Values' reporting after the hourly RSSI sample measurement period. 6. Check the active alarms at BSC and Flexi EDGE BTS Manager. 7. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 8. Repeats steps 2 and 3. 9. Fetch and save 'RSSI Comparison Values' from Flexi EDGE BTS Manager -> Supervision -> RSSI Comparison values after 10 minutes and verify 'RSSI Comparison Values' reported with the values received in Step 5.
MENU
10. Fetch and save Site Information Report and verify 'RSSI Comparison Values' reporting after the hourly RSSI sample measurement period. 11. Check the active alarms at BSC and Flexi EDGE BTS Manager, 12. Using a variable attenuator, introduce an attenuation of 20dB (higher than the default threshold set at BSC) on the path of antenna A of RTC1 in the common segment. 13. After one hour of providing attenuation, refresh the RSSI Comparison values at the Flexi EDGE BTS Manager. Note the value of the 'Diff.' field in the Raw, Newest and Reliable table for each TRX object of the affected BTS object and record the absolute difference in RSSI measurements. 14. Observe the alarms at Flexi EDGE BTS Manager and the BSC after hourly RSSI sample measurement period. 15. Fetch and save the Site Information Report and verify Reliable 'RSSI Measurement' reporting. 16. Re-adjust the variable attenuator to reduce the attenuation to around 5 dB (below the threshold set at BSC). 17. After 1 hour use the Flexi EDGE BTS Manager to observe the difference between the Main & Diversity signal strengths reported for all the TRXs. 18. After one hour refresh the RSSI Comparison values at the Flexi EDGE BTS Manager. Note the value of the 'Diff.' field in the Reliable table for each TRX object of first and second Flexi EDGE BTS object and record the absolute difference in RSSI measurements. 19. Observe the alarms at Flexi EDGE BTS Manager and the BSC. Expected results: 1. The Flexi EDGE BTS site resets successfully and comes up in supervisory state at the Flexi EDGE BTS Manager and BSC. 2. No RSSI sample count is reported in RSSI Comparison values for both sectors. 3. The voice calls are established successfully. Voice quality is good without disturbances, or cracking sound. 4. RSSI sample count and Rx levels reported in the 'Raw' table of Flexi EDGE BTS Manager for carriers in common segment are not consistent after 10 minutes. 5. RSSI sample count and Rx levels reported in the 'Raw' ,'Newest and 'Reliable tables in Site Information Report for carriers in common segment are not consistent after an hour. 6. No unexpected alarms are active at BSC and Flexi EDGE BTS Manager. 7. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 8. Similar results are observed. 9. Consistent RSSI sample count and balanced Rx levels are reported in the 'Raw' table of Flexi EDGE BTS Manager for carriers in first and second sector. 10. Consistent RSSI sample count and balanced Rx levels are reported in the 'Raw' ,'Newest and 'Reliable tables in Site Information Report for carriers in first and second sector. 11. No unexpected alarms are active at BSC and Flexi EDGE BTS Manager. 12. Attenuation of 20dB is introduced on the path of antenna under test. 13. RSSI Measurements table is displayed. Absolute difference in 'RSSI Comparison Values' is greater than the threshold value for each TRX object in first and second sector in 'Raw' 'Newest' and 'Reliable' tables. 14. The 7607 alarm "RSSI detected Rx signal difference exceeding threshold" is reported at Flexi EDGE BTS Manager and BSC for all TRXs objects in the common segment. It is observed that one of these alarms is reclassified to 7604 alarm "RSSI detected Rx signal difference exceeding threshold" for the common segment at flexi EDGE BTS Manager and BSC.
MENU
15. Consistent RSSI sample count and balanced difference in Rx levels are reported in the 'Reliable table' in 'RSSI Measurements ' section for all carriers in first and second sector. 16. The Attenuation is set to 5dB. 17. The difference between the Main & Diversity signal strengths reported for all the TRXs is less than the threshold set at BSC. 18. RSSI Measurements table is displayed. Absolute difference in 'RSSI Comparison Values' is less than 5dB for each TRX object in first and second sector in 'Raw' 'Newest' and 'Reliable' tables. 19. The alarms reported in Step 14 are cancelled. No active alarms are present at the Flexi EDGE BTS Manager and at the BSC. Unexpected results: -
MENU

Title:
Increased Remote Transcoder Failures when MGW is used Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: In a mobile network, speech frames carried between the BTS and the BSC are encoded / decoded in either a Transcoder or a Media Gateway (MGW). A problem has been observed in Adaptive Multi Rate Half Rate (AMR-HR) channels where the BTS occasionally loses synchronisation with the MGW. The BTS performs a resynchronisation by searching for a specific bit pattern in the DL frames. However, when the BTS has established synchronisation, it wrongly decodes the subsequent speech frames and the cyclic redundancy check (CRC) fails. After 50 incorrect frames, the BTS sends a remote transcoder failure alarm and the call will be dropped. Description of the correction: The re-synchronisation procedure is modified so that if synchronisation cannot be achieved after the BTS has received three erroneous frames then initial synchronisation shall be performed where the BTS will only search for the lower codec mode synchronisation pattern. Solution / Workaround: System Impact: Increase in dropped call rate due to transcoder failure. This can be observed as an increase in BSC Traffic Counter 1029. Corrected Fault Reports: 32436ESPE03 : BTS is reporting UFE error in UL frames while nothing wrong observed in DL frames Modified components:
MENU
esmNp\Microcode\Microblocks\common\debug esmNp\Microcode\Microblocks\downlink\dl_iwf esmNp\Microcode\Microblocks\uplink\ul_iwf esmNp\Microcode\Microblocks_apps\mp_router\dispatch_loop\app_system esmNp\Microcode\Microblocks_apps\ucode esmNp\Lab\Tools\scripts\debuliwf EP3_MP2.0_ESM_NP_32436ESPE03_0001EP3_MP2.0_ESM_NP_32436ESPE03_00 01EP3_MP2.0_ESM_NP_32436ESPE03_0001EP3_MP2.0_ESM_NP_32436ESPE03_ 0001EP3_MP2.0_ESM_NP_32436ESPE03_0001EP3_MP2.0_ESM_NP_32436ESPE0 3_0001 Change effects: Effects on end-user None Effects on Operator Increase in dropped call rate due to transcoder failure Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration Any multi-TRX Flexi EDGE BTS Site is commissioned and in Supervisory state. EP3 MP2.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP2.0 build is the active software package. Test execution: 1. Establish multiple AMR HR calls on all TRXs utilising the lowest codec of 4.75. 2. Monitor the Abis. 3. After a minimum of 10 minutes release the calls established in step 1. 4. Repeat steps 1 to 3 continuously for 5 hours. Expected results: 1. Multiple AMR HR calls are established successfully. 2. No connection fail messages are observed on the Abis. 3. Calls are released successfully. 4. Similar results are observed. Unexpected results: -
MENU

Title:
TRX Test fails for Auxiliary path of locked IDD TRX Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: A single TRX object at the BSC configured using Intelligent Downlink Diversity (IDD) mode uses two physical TRXs (one DTRX module); one TRX is known as Main, the other TRX is known as Auxiliary. When the IDD TRX object is locked at the BSC it is possible to execute TRX tests using the BTS Manager (Tests | TRX Tests) and the user can select either the Main IDD TRX or Auxiliary IDD TRX to test. The problem is that if the TRX test is executed on the Auxiliary IDD TRX then the test will fail with the following causes: In GMSK Mode - Low Power in Abis1-Air3 Loop In 8PSK Mode - RF Cables No Connection
When the IDD TRX is locked, the IDD status for the Auxiliary TRX is not known by the BTS software. Consequently, the results of a TRX test are invalid. The TRX test can still be performed on the locked Main IDD TRX. Description of the correction: From a BTS software point of view when an IDD configured TRX object is locked, it is in a logical reset state and its IDD feature status is unknown by the BTS software at that time. When the TRX test is commanded on the Main IDD TRX, the TRX test is successful because its IDD status although unknown, is irrelevant. However the BTS software NEEDS to know about the IDD feature status of the Auxiliary IDD TRX to be able to successfully execute the TRX test. The TRX test on the Auxiliary IDD TRX will always result in failure when the IDD TRX object is locked. In EP3 MP2.0, the user will not be allowed to execute the TRX test on a locked Auxiliary IDD TRX. Solution / Workaround: DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 23(42)
MENU
System Impact: Corrected Fault Reports: 9321ESPE06 : In locked IDD TRX object TRX test fails for Auxillary Tx path Modified components: epem\tests\src\com\nokia\ebts\eem\tests\trxtest\TRXTestUIController epem\tests\src\com\nokia\ebts\eem\tests\testscommon\TestsConstants epem\common\src\com\nokia\ebts\eem\common\constants\ResourceBundleType epem\config\MessageBundle_en_US main\ep2_em_intg_ir1\ep2_em_intg_ir2\ep3_em_intg\ep3_MP2.0_em_di_preintg\pr93 21ESPE06\3main\ep2_em_intg_ir1\ep2_em_intg_ir2\ep3_em_intg\ep3_mp1.0_em_int g\ep3_MP2.0_em_di_preintg\pr9321ESPE06\1main\ep2_em_intg_ir1\ep2_em_intg_ir2 \ep3_em_intg\ep3_mp1.0_em_intg\ep3_MP2.0_em_di_preintg\pr9321ESPE06\1main\ ep2_em_intg_ir1\ep2_em_intg_ir2\ep3_em_intg\ep3_mp1.0_em_intg\ep3_MP2.0_em_ di_preintg\pr9321ESPE06\1 Change effects: Effects on end-user None Effects on Operator Improved user feedback through BTS Manager Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 2 Omni IDD/4UD Site is commissioned and in Supervisory state. EP2 CD2.0 Flexi EDGE BTS Manager is connected to the BTS. EP2 CD2.0 build is the active software package. Test execution: 1. Lock first TRX in the sector from the BSC using the MML command ZERS. 2. Invoke a TRX Test for TRX-1 (auxiliary) from the Flexi EDGE BTS Manager by selecting Tests -> TRX test with the following parameters: Mode='GMSK', Timeslot: Any randomly chosen timeslot, IDD TRX: Auxiliary. Observe the alarms raised at the Flexi EDGE BTS Manager. 3. After the test is over, verify that the test results for locked TRX (auxiliary TX path) on the right hand pane. 4. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC.
MENU
5. Invoke TRX Test for TRX-1 (main) from the Flexi EDGE BTS Manager by selecting Tests -> TRX test with the following parameters: Mode='GMSK', Timeslot: Any randomly chosen timeslot, IDD TRX: Main. Observe the alarms raised at Flexi EDGE BTS Manager. 6. After the test is over, verify that the test results for locked TRX (auxiliary TX path) on the right hand pane. 7. Invoke TRX Test for TRX-1 (auxiliary) from the Flexi EDGE BTS Manager by selecting Tests -> TRX test with the following parameters: Mode='GMSK', Timeslot: Any randomly chosen timeslot, IDD TRX: Auxiliary. Observe the message displayed at Flexi EDGE BTS Manager. 8. Repeat steps 5 to 7 with Mode = '8PSK'. Expected results: 1. First TRX is locked and is verified using the MML command ZEEI. 2. TRX test is started on the desired TRX and timeslot. The Test result pane displays "TRX test is Ongoing". 7615 alarms are active at the Flexi EDGE BTS Manager alarm window for the duration of the test, for each of the reserved timeslots with the description 'RTS IS IN TEST USE: Radio TS is in test use'. 3. The TRX test results show "Failed" with failure reason "RF Cables No Connection". The values of different parameters are as follows:Test Result: TX Power: Main Rx BER: Main Rx Result: Diversity Rx BER: Diversity Rx1 Result: Diversity Rx2 Result: Diversity Rx3 Result: Diversity Rx3 Result: Fail NOT_TESTED 100.0000000% NOT_TESTED NOT_TESTED NOT_TESTED NOT_TESTED NOT_TESTED NOT_TESTED
4. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 5. TRX test is started on the desired TRX and timeslot. The Test result pane displays "TRX test is Ongoing". Alarm 7615 is active at Flexi EDGE BTS Manager Alarms window for the duration of the test for each of the reserved timeslots with the description 'RTS IS IN TEST USE: Radio TS is in test use'. 6. The TRX test results show "Passed". The values of the different parameters are as follows:Test Result: TX Power: Main Rx BER: Main Rx Result: Diversity Rx BER: Diversity Rx1 Result: Diversity Rx2 Result: Diversity Rx3 Result: PASS >= 47 dBm 0(RF BER) < -110 dBm 0(RF BER) < -110 dBm < -110 dBm < -110 dBm
MENU
Note: For IDD 2UD sector Diversity Rx2 Result: Diversity Rx3 Result:
NOT_TESTED NOT_TESTED
7. The following message is displayed at the Flexi EDGE BTS Manager after the TRX test for the auxiliary TRX is invoked - "TRX test is not allowed for auxiliary TX path in case of locked IDD TRX". Observe that TRX test is not started for the Auxiliary TX path. 8. Similar results are observed. Unexpected results: -
MENU

Title:
Alarm 7602 Supply voltage to ESxA near low/high threshold is too low Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: In EP2 CD3.0 the following alarms are implemented to indicate out of range input voltage to the ESMA module and ESEA module: 7602 - BCF NOTIFICATION - "Supply voltage to ESMA near low/high limit 7602 - BCF NOTIFICATION - "Supply voltage to ESEA near low/high limit" and the near low/high limits for the alarm were: Raised at <= 40.0VDC or >=58.0 VDC Cancelled at >=41.0VDC or <=57.0 VDC Refer to LGF case 28887ESPE01 corrected in EP2 CD3.0. Further studies have shown that battery voltage discharge in some installations is too rapid and power is lost at the BTS installation before the BTS software is able to send the notification alarm. Description of the correction: In EP3 MP2.0 the near low limits for the alarm have been changed to: Raised at <= 44.0VDC or >=58.0 VDC Cancelled at >=45.0VDC or <=57.0 VDC Solution / Workaround: System Impact: Increased troubleshooting effort and unnecessary hardware swap outs.
MENU
Corrected Fault Reports: 30785ESPE03 : 7602 - Supply voltage to ESxA near low/high limit alarm activated at too low voltage Modified components: /vob/epsys/som/bc/h/som_objm EP3_MP2.0_SOM_30785ESPE03_0001 Change effects: Effects on end-user None Effects on Operator Lower threshold limit implemented in EP3 MP1.0 is now higher. Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 6+4 with RTC combining and chained DC cabling. Site is commissioned and in Supervisory state. EP2 CD3.0 Flexi EDGE BTS Manager is connected to the BTS. EP2 CD3.0 build is the active software package. Test execution: 1. Generate one pair of CS voice call on all sectors. 2. Using a variable DC voltage generator, decrease the DC voltage to 41V for 5 minutes. 3. Further decrease the DC voltage to 40V for 5 minutes. 4. Further decrease the DC voltage by 1V per minute until the voltage reaches 37V. Hold 37V for 90 minutes. Observe the status of all TRX objects at the BSC. Monitor alarms at the Flexi EDGE BTS Manager and BSC. 5. Increase the DC voltage by 1V per minute until the voltage reaches 40V. Observe the status of all TRX objects on BSC. 6. Generate one pair of CS voice call on all sectors. 7. Further increase the DC voltage to 41V. 8. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 9. Generate one pair of CS voice call on all sectors. 10. Decrease the DC voltage to 45V for 5 minutes. 11. Further decrease the DC voltage to 44V for 5 minutes. 12. Further decrease the DC voltage by 1V per minute until the voltage reaches 37V. Hold 37V for 90 minutes. Observe the status of all TRX objects at the BSC. Monitor alarms at the Flexi EDGE BTS Manager and BSC. 13. Increase the DC voltage by 1V per minute until the voltage reaches 44V. Observe the status of all TRX objects on BSC.
MENU
14. Generate one pair of CS voice call on all sectors. 15. Further increase the DC voltage to 45V. Expected results: 1. CS voice calls are established successfully. 2. There is no effect on going calls and no unexpected alarms are generated. 3. There is no effect on going calls. Alarm 7602 "Supply voltage to ESMA near low/high limit' for ESMA is reported on the Flexi EDGE BTS Manager and BSC. 4. All ongoing calls are dropped. In addition to alarm observed in step 3 alarm 7606 "TRX Faulty, PDU Control has switched off EXxx TRX Module" and 7603,"BTS Faulty, PDU Control has switched off EXxx TRX Module" are raised at the Flexi EDGE BTS Manager and BSC. All the TRX objects are in BL-BTS state at the BSC. 5. The 7606 and 7603 alarms raised in step 4 are cancelled and alarm 7602 raised in step 3 is still active at the Flexi EDGE BTS Manager and BSC. Operational state of the TRX objects are reported as WO at the BSC. 6. CS voice calls are established successfully. 7. Alarm 7602 raised in step 3 is cancelled at the Flexi EDGE BTS Manager and BSC. There is no effect to the ongoing calls. 8. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 9. CS voice calls are established successfully. 10. There is no effect on going calls and no unexpected alarms are generated. 11. There is no effect on going calls. Alarm 7602 "Supply voltage to ESMA near low/high limit' for ESMA is reported on the Flexi EDGE BTS Manager and BSC. 12. All ongoing calls are dropped. In addition to alarm observed in step 11 alarm 7606 "TRX Faulty, PDU Control has switched off EXxx TRX Module" and 7603,"BTS Faulty, PDU Control has switched off EXxx TRX Module" are raised at the Flexi EDGE BTS Manager and BSC. All the TRX objects are in BL-BTS state at the BSC. 13. The 7606 and 7603 alarms raised in step 12 are cancelled and alarm 7602 raised in step 11 is still active at the Flexi EDGE BTS Manager and BSC. Operational state of the TRX objects are reported as WO at the BSC. 14. CS voice calls are established successfully. 15. Alarm 7602 raised in step 11 is cancelled at the Flexi EDGE BTS Manager and BSC. There is no effect to the ongoing calls. Unexpected results: -
MENU

Title:
Unnecessary disturbance alarm is raised in Flexi EDGE BTS when Q1IC is used Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: The Q1IC box is used to enable remote connections to Q1 devices through the Flexi EDGE BTS. For example, the Flexi EDGE BTS may be connected to a legacy Talk Family site support system. The Q1IC box would enable a remote connection to be established to the site support system through the Flexi EDGE BTS. If, in this example, the site support system raises a rectifier alarm, the following can be seen at the BSC, PSM Manager and BTS Manager: ** ALARM 8128 FAULT IN EQUIPMENT When the alarm condition is cleared, the above alarm is cancelled automatically. The problem is that upon cancelling, the following disturbance alarm is seen at the BSC and BTS Manager: * DISTUR 8128 FAULT IN EQUIPMENT The PSM manager does not show this disturbance alarm. This problem is only seen when the Q1IC box is used. Description of the correction: In previous releases, the BTS software was not able to handle the start and cancel of warning/disturbance transient alarms. In EP3 MP2.0 the correction is such that if any alarm comes without a severity and the alarm condition is OFF, the BTS software will check if the same fault code is active for the target Q1 device. The BTS software can then issue an alarm cancellation or alarm start as appropriate. Solution / Workaround: A BCF reset will cancel the disturbance alarm.
MENU
System Impact: -
Corrected Fault Reports: NA04557246 : CA6512 - Fault in Equipment Modified components: /vob/epsys/som/ah/h/som_ah_q1_trs_alarms /vob/epsys/som/ah/src/som_ah_q1_trs_alarms EP3_MP2.0_SOM_NA04557246_0001EP3_MP2.0_SOM_NA04557246_0001 Change effects: Effects on end-user None Effects on Operator Improved BTS alarm handling Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration Any Site is commissioned and in Supervisory state. Q1 monitoring device and Q1IC are attached to the Q1 interface. EP2 Flexi EDGE BTS Manager is connected to the BTS. EP2 build is the active software package. Test execution: 1. Generate a Major alarm from the Q1IC device. Observe Alarm activity in the PSM manager alarm log. 2. Observe the alarms active at Flexi EDGE BTS Manager and BSC. 3. Generate a Critical alarm from the Q1IC device. Observe Alarm activity in the PSM manager alarm log. 4. Observe the alarms active at Flexi EDGE BTS Manager and BSC. 5. Cancel the Major alarm created in step 1 from the Q1IC device. Observe the alarm activity in the PSM manager alarm log, Flexi EDGE BTS Manager and the BSC. 6. Cancel the Critical alarm created in step 3 from the Q1IC device. Observe the alarm activity in the PSM manager alarm log, Flexi EDGE BTS Manager and the BSC. 7. Give BCF reset to Flexi EDGE BTS site from Flexi EDGE BTS Manager. Observe the disturbance alarms at Flexi EDGE BTS Manager and BSC after BCF reset. 8. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC.
MENU
9. Generate a Major alarm from the Q1IC device. Observe Alarm activity in the PSM manager alarm log. 10. Observe the alarms active at Flexi EDGE BTS Manager and BSC. 11. Cancel the Major alarm created in step 9 from the Q1IC device. Observe the alarm activity in the PSM manager alarm log, Flexi EDGE BTS Manager and the BSC. 12. Generate a Critical alarm from the Q1IC device. Observe Alarm activity in the PSM manager alarm log. 13. Observe the alarms active at Flexi EDGE BTS Manager and BSC. 14. Cancel the Critical alarm created in step 3 from the Q1IC device. Observe the alarm activity in the PSM manager alarm log, Flexi EDGE BTS Manager and the BSC. Expected results: 1. Q1 alarm is generated successfully. An alarm indicating the fault condition and severity Major Alarm is seen in the PSM manager alarm window. 2. Alarm 8128 Fault in equipment is seen at the Flexi EDGE BTS Manager and BSC. The alarm at the BSC is displayed as a major, or two star alarm. 3. Q1 alarm is generated successfully. An alarm indicating the fault condition and severity Major Alarm is seen in the PSM manager alarm window. 4. Alarm 8150 Fault in unit is seen at the Flexi EDGE BTS Manager and BSC. The alarm at the BSC is displayed as a critical, or three star alarm. 5. Major alarm is cancelled in PSM manager alarm window. Alarm 8128 and alarm 8150 are still active at the Flexi EDGE BTS Manager and BSC. 6. Critical alarm is cancelled in PSM manager alarm window. Alarm 8128 and alarm 8150 are still active at the Flexi EDGE BTS Manager and BSC. 7. Disturbance alarms 8128 and 8150 are cancelled as observed at Flexi EDGE BTS Manager and BSC. 8. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 9. Q1 alarm is generated successfully. An alarm indicating the fault condition and severity Major Alarm is seen in the PSM manager alarm window. 10. Alarm 8128 Fault in equipment is seen at the Flexi EDGE BTS Manager and BSC. The alarm at the BSC is displayed as a major, or two star alarm. 11. Major alarm is cancelled in PSM manager alarm window, no other alarms are active. Alarm 8128 is cancelled at the Flexi EDGE BTS Manager and BSC, no other alarms are active. 12. Q1 alarm is generated successfully. An alarm indicating the fault condition and severity Major Alarm is seen in the PSM manager alarm window. 13. Alarm 8150 Fault in unit is seen at the Flexi EDGE BTS Manager and BSC. The alarm at the BSC is displayed as a critical, or three star alarm. 14. Critical alarm is cancelled in PSM manager alarm window. Alarm 8150 is cancelled at the Flexi EDGE BTS Manager and BSC. No unexpected alarms are seen at the PSM manager, Flexi EDGE BTS Manager, or the BSC. Unexpected results: -
MENU

Title:
Audio muting during AMR HR mobile originated calls Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: Audio muting has been observed during Mobile Originating (MOC) to Mobile Terminating Calls (MTC) when using certain mobile phone models. The MOC is made and the end user begins talking; when there is a pause in the conversation and speech starts again then the end-user will hear a 5 to 10 second muting. The muting can be heard in both directions of the call. The problem has been observed only when the TCH is configured as AMR HR (Adaptive Multi Rate Half Rate) and UL DTX (Uplink Discontinuous Transmission) is active. Description of the correction: The BTS receiver DTX handler has been modified so that it is able to end DTX periods after successfully decoding speech frames, even if SID_FIRST or SID_UPDATE frames from the mobile (MS) have not been detected. This implementation will avoid the need to depend on the MS to send the ONSET frames before good SPEECH frames are sent. The DTX state in the BTS will now be changed to SPEECH state during DTX periods when either a good ONSET block or two continuous good SPEECH blocks are decoded. Solution / Workaround: Disable UL DTX System Impact: End users will experience 5 to 10 second muting periods which will be heard throughout the conversation.
MENU
Corrected Fault Reports: 32222ESPE03 : Motorola Razor Muting when UL DTX=ON Modified components: @@\main\ep2_trx_intg_ir2\ep3_trx_intg\ep3_mp2.0_dsp_di\1 Change effects: Effects on end-user The audio quality as perceived by the end user is improved Effects on Operator None Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 2+2 with each sector defined as a neighbour to each other Site is commissioned and in Supervisory state. EP1 Flexi EDGE BTS Manager is connected to the BTS. EP1 build is the active software package. Test execution: 1. Make an AHS call from a mobile in the first sector to a mobile in the second sector. Trigger handovers such that the mobiles handover between the two sectors. 2. Generate a continuous audio for 5 minutes which is transmitted from the first mobile to the second whilst monitoring the Abis. 3. Repeat steps 1 to 2 at least 4 times. 4. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 5. Make an AHS call from a mobile in the first sector to a mobile in the second sector. Trigger handovers such that the mobiles handover between the two sectors. 6. Generate a continuous audio for 5 minutes which is transmitted from the first mobile to the second whilst monitoring the Abis. 7. For the next 5 minutes send no audio between the mobiles whilst maintaining the call and handovers. Continue to monitor the Abis. 8. For the next 5 minutes generate a continuous audio from the second mobile to the first whilst monitoring the Abis. 9. Release the calls. 10. Repeat steps 5 to 9 at least 4 times. Expected results: 1. Call is established and handovers are successful.
MENU
2. Continuous audio is received at the second mobile, randomly muting may occur. On the Abis continuous speech frames are seen with no No Speech frames reported, except when random muting is observed. 3. Similar results are observed. 4. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 5. Call is established and handovers are successful. 6. Continuous audio is received at the second mobile with no muting. On the Abis continuous speech frames are seen with no No Speech frames reported. 7. No audio is received at either mobile. On the Abis No Speech frames are observed for the entire 5 minutes. 8. Continuous audio is received at the first mobile with no muting. On the Abis continuous speech frames are seen with no No Speech frames reported. 9. Calls are released successfully. 10. Similar results are observed. Unexpected results: -
MENU

Title:
Unnecessary 7607 RSSI detected Rx signal difference exceeding threshold alarms are raised Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: A partial fix to this problem is made in EP2 CD3.0 BTS software. The final correction is now provided in EP3 MP2.0. The correction will reduce the probability of a spurious alarm but this detection method still has an associated probability of some alarms being reported even after this correction. No further correction is planned for this. Description of the correction: The BTS will estimate the number of samples it would receive for high/medium traffic profiles by setting an internal threshold value (not visible to the end user) which is a multiplier of the user defined RSSI sample count. The RSSI alarm will be raised when: If in the first hour, the received sample count is greater than the internal threshold and the RSSI alarm conditions are valid then the RSSI alarm will be raised. If in the first hour the received sample count is greater than the user configured RSSI sample threshold but less than the internal RSSI alarm threshold then the BTS software will wait for the next hour to determine if the RSSI alarm is to be raised. If in the consecutive second hour the received sample count is greater than the internal RSSI alarm threshold or the user configured RSSI sample threshold and the RSSI alarm conditions are valid then the RSSI alarm will be raised. If the user configurable sample count is changed during this hour then the monitoring is reset and the process restarts from the first hour. The alarm will be cancelled automatically in the next hour if the sample count is greater than the user configured sample count and the alarm condition has been cleared. This is identical to earlier BTS software functionality.
MENU
Solution / Workaround: System impact: These alarms cause increased and unnecessary troubleshooting effort. Corrected Fault Reports: 34417ESPE01 : Unstable RSSI alarm behaviour Modified components: /vob/epsys/som/common/h/som_inos_ipc_global /vob/epsys/som/hwmgt/h/som_hwmgt_main /vob/epsys/som/hwmgt/src/som_hwmgt_main /vob/epsys/som/common/som_db/src/som_db /vob/epsys/som/common/som_db/h/som_db_private /vob/epsys/som/common/h/som_db_types /vob/epsys/som/common/h/som_global /vob/epsys/som/bc/src/som_confm_decode_conf_data /vob/epsys/som/common/som_db/src/som_db_internal_functions /vob/epsys/som/bc/src/som_objm_main /vob/epsys/som/bc/h/som_objm_exp /vob/epsys/som/build/ep_tools/src/config_file_builder /vob/epsys/som/build/ep_tools/h/config_file_builder /vob/epsys/som/build/ep_tools/bin/ep_som_cfg_file /vob/epsys/som/commis/src/som_commis_append_fsm /vob/epsys/som/commis/h/som_commis_append_fsm /vob/epsys/som/hwmgt/src/som_hwmgt_rssi vob/epsys/som/hwmgt/h/som_hwmgt_rssi Change effects: Effects on end-user None Effects on Operator Reduced amount RSSI alarms where RSSI alarms are not expected. Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration 4 Omni with 2-way combining. One TRX is reserved for PS data. Site is commissioned and in Supervisory state. EP3 MP2.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP2.0 build is the active software package.
MENU
Test execution: 1. To reset the RSSI timers reset the BCF from the Flexi EDGE BTS Manager. 2. Establish long duration static CS voice calls. The number of calls established should be enough to generate enough RSSI samples in an hour. Establish repetitive packet data transfers on multiple time slots of the TRX reserved for packet data traffic. 3. One hour after BCF reset check for alarms at Flexi EDGE BTS Manager and BSC. Fetch the RSSI Comparison values from the Flexi EDGE BTS Manager. Observe the value of the 'Diff.' field in the Newest table for each TRX object. Fetch and save SIR and compare the RSSI Measurements in Newest, Reliable and Raw columns. 4. Repeat step 3 (i.e. logs are checked after an additional hour). 5. Establish additional CS calls to generate RSSI samples more than the internal RSSI alarm threshold. 6. Using a variable attenuator, induce an attenuation of 20dB (higher than the default threshold set at BSC) on antenna path A (Main antenna) of the ERxx DDU module. 7. After 1 hour from observe any alarms at Flexi EDGE BTS Manager and BSC. Observe the supplementary fields in the alarms raised. Upload and save the Site Information Report from Flexi EDGE BTS Manager. 8. Re-adjust the variable attenuator, to reduce the attenuation to around 5 dB (below the threshold set at BSC) on the path to the antenna A (Main antenna) of ERxx DDU module in first sector. Refresh the RSSI Comparison values at the Flexi EDGE BTS Manager after one hour from step 7. Note the value of the 'Diff.' field in the Reliable table for each TRX object of BTS object and record the absolute difference in RSSI measurements. 9. Observe the alarms at Flexi EDGE BTS Manager and BSC. Observe the alarm history at the BSC and observe the supplementary fields in the alarms at the time of cancellation. 10. Set RSSI Sample Count to be 750,000 from Flexi EDGE BTS Manager. Release the ongoing CS calls, or adjust the CS calls such that only 2 timeslots in the sector should be active for CS calls. This is done so that after 1 hour sample count should not be more than 3 times the commissioned Sample count. 11. Using variable attenuator, induce an attenuation of 20dB (higher than the default threshold set at BSC) on antenna path B (diversity antenna) of the ERxx DDU Module. After one hour refresh the RSSI Comparison values at the Flexi EDGE BTS Manager. Note the value of the 'Diff.' field in the Reliable table for each TRX object of the affected BTS object and record the absolute difference in RSSI measurements. 12. After an hour check for any alarms at Flexi EDGE BTS Manager and BSC. Upload and save the Site Information Report from Flexi EDGE BTS Manager. 13. After an hour check for any alarms at Flexi EDGE BTS Manager and BSC. Observe the supplementary fields in the alarms. 14. Re-adjust the variable attenuator, to reduce the attenuation to around 5 dB (below the threshold set at BSC) on the path to the antenna B (diversity antenna) of the ERxx DDU module. Refresh the RSSI Comparison values at the Flexi EDGE BTS Manager after one hour. Note the value of the 'Diff.' field in the Reliable table for each TRX object of BTS object and record the absolute difference in RSSI measurements. 15. Observe the alarms at Flexi EDGE BTS Manager and BSC. Observe the alarm history at the BSC and observe the supplementary fields in the alarms at the time of cancellation. Expected results: 1. Flexi EDGE BTS site reached supervisory state after BCF Reset. 2. Voice calls are established successfully, voice quality is good, without any disturbances or cracking sound. Packet data transfers are ongoing on multiple time slots of the TRX reserved for packet data. 3. No RSSI alarms are present at Flexi EDGE BTS Manager & BSC. RSSI Measurements table is displayed. RSSI sample counts are more than 160,000 for the
MENU
4. 5. 6. 7.
8.
9.
10. 11.
12.
13.
14.
15.
TRX(s) on which CS calls are established. RSSI sample count is observed to be zero or low for the TRX(s) on which no CS calls are maintained. Absolute difference in RSSI measurements is less than 2dB, or defined threshold, for each TRX object. SIR is fetched and RSSI values in SIR are same as observed above. Similar results are observed. CS calls are established to generate valid RSSI sample count. Attenuation is introduced on the path of the antenna under test. Alarm 7607 "RSSI detected Rx signal difference exceeding threshold" is reported at Flexi EDGE BTS Manager and BSC for all TRXs which have reliable Main and Diversity path RSSI difference exceeding threshold. The value in the first supplementary field information for the 7607 alarm is the absolute difference in Rx levels as introduced in Step 6 for that TRX object. The second supplementary field information for the 7607 alarm indicates that the fault is on Antenna <id of antenna under test>. The contents of the Site Information report shows the same values for Raw/Newest/Reliable as seen from Flexi EDGE BTS Manager views. The Attenuation is set correctly. RSSI Measurements table is displayed. RSSI sample count of more than 480,000 are observed for the TRX(s) on which CS calls are established. RSSI sample count is observed to be zero or low for the TRX(s) on which no CS calls are maintained. Absolute difference in RSSI measurements is less than 5dB for each TRX object of affected BTS object. The alarms reported in Step 7 are cancelled. No active alarms are seen at the Flexi EDGE BTS Manager and at the BSC. The first and the second supplementary field information is the same as that observed in step 7. RSSI Sample count is set correctly. Only 2 active CS calls are made per sector. Attenuation of 20dB is introduced on the path of antenna under test. RSSI sample counts more than 750,000 but less than 2,250,000 are observed for the TRX(s) on which CS calls are established. RSSI sample count is observed to be zero or low for the TRX(s) on which no CS calls are maintained. Absolute difference in RSSI measurements is greater than the RX Difference limit set at BSC (10 dB by default) for each TRX object of affected BTS object. For the TRX in which packet data transfer is ongoing, the difference between the reliable RSSI values for the Main & Diversity paths is seen to be lesser than the threshold. No RSSI alarm is observed at Flexi EDGE BTS Manager, or BSC. The contents of the Site Information report shows the same values for Raw/Newest/Reliable as seen from Flexi EDGE BTS Manager views. Alarm 7607 "RSSI detected Rx signal difference exceeding threshold" is reported at Flexi EDGE BTS Manager and BSC for all TRXs which have reliable Main and Diversity path RSSI difference exceeding threshold for last 2 hours. Value in the first supplementary field information for the 7607 alarm is the absolute difference in Rx levels as introduced in Step 11 for that TRX object. The second supplementary field information for the 7607 alarm indicates that the fault is on Antenna <id of antenna under test>. The contents of the Site Information report shows the same values for Raw/Newest/Reliable as seen from Flexi EDGE BTS Manager views. The Attenuation is set correctly. RSSI Measurements table is displayed. RSSI sample counts more than 750,000 but less than 2,250,000 are observed for the TRX(s) on which CS calls are established. RSSI sample count is observed to be zero or low for the TRX(s) on which no CS calls are maintained. Absolute difference in RSSI measurements is less than 5dB for each TRX object of affected BTS object. The alarms reported in Step 13 are cancelled. No active alarms are seen at the Flexi EDGE BTS Manager, or the BSC. The first and the second supplementary field information is the same as that observed in step 13.
Unexpected results: -
MENU

Title:
BTS Manager freezes during log file retrieval Version of the SW-build: EP3 MP2.0 Valid for Product(s): Flexi EDGE BTS References: Reason for the Change Note: Description of the fault: A problem has been observed where the EP3 BTS Manager application may freeze when the user attempts to retrieve the Commissioning Report (Commissioning | Report | Fetch from BTS), the Site Commissioning File (Commissioning | Fetch SCF from BTS), or the Site Information Report (Supervision | Site Information). Description of the correction: In the Windows operating system, when dynamically linked libraries (dlls) are searched for, the system directories always have a higher precedence than local folders. Only the directory from which the application is run from has a higher precedence. If corrupt dlls (like nspr4.dll and plc4.dll ) already exist (for example in the windows\system32 directory) then BTS Manager will take these dlls to use and the BTS manager will stop responding as described. Now, the dependent dlls will be installed to the same directory as the BTS manager executable when the BTS Manager application is installed, either as a stand alone product or as part of SiteWizard. Solution / Workaround: Delete the dynamic link library (DLL) files nspr4.dll and plc4.dll from the windows system directory C:\WINNT\SYSTEM32 or C:\WINDOWS\SYSTEM32. The version number of the DLL files has so far been observed as v4.1.2. (Select the file and Mouse Right Click | Properties | Version Tab). System impact: No impact. Corrected Fault Reports: 23140ESPE05 : Flexi EDGE BTS Manager gets jammed
MENU
Modified components: epem\build @@\main\ep2_em_intg_ir1\ep2_em_intg_ir2\ep2_cd1.0_em_intg\ep3_em_intg\ep3_M P2.0_em_di_preintg\1 Change effects: Effects on end-user None Effects on Operator Improved BTS Manager stability Other effects None New functionality No Testing Instructions for the change Pre-requirements: Site Configuration Any Site is commissioned and in Supervisory state. Existing installation of Netscape is required on the PC to recreate the fault conditions. EP3 MP1.0 Flexi EDGE BTS Manager is connected to the BTS. EP3 MP1.0 build is the active software package. Test execution: 1. From the Flexi EDGE BTS Manager fetch the commissioning report, go to Commissioning Menu -> Report -> Fetch from BTS. 2. Close the Flexi EDGE BTS Manager by killing the process via the OS Task Manager. 3. Reconnect the Flexi EDGE BTS Manager to the Flexi EDGE BTS site. 4. From the Flexi EDGE BTS Manager un-commission the BTS Site and disconnect the Flexi EDGE BTS Manager from the BTS by closing the Flexi EDGE BTS Manager. 5. Launch Flexi EDGE BTS Manager. 6. Go to "Commissioning Wizard" and click on "Create SCF" and check the box of "Complete SCF". Click on "Next" button. 7. Provide the correct details as prompted by the Commissioning Wizard. Click on "Next" button. 8. Repeat steps 2 to 5. 9. Go to "Commissioning Wizard" and click on "Create SCF" and check the box of "Complete SCF". Click on "SCF Preview" button. 10. Repeat step 2. 11. Attach EP3 MP2.0 Flexi EDGE BTS Manager to the BTS and download the EP3 MP2.0 build. Attach and activate the build to the BCF from BSC. 12. Repeat step 6. 13. Repeat step 7. 14. Click "Save & Exit" to complete the wizard. 15. Repeat step 9. 16. Repeat step 14.
MENU
Expected results: 1. It is observed that Flexi EDGE BTS Manager hangs whilst fetching Commissioning Report. 2. Flexi EDGE BTS Manager process is killed successfully. 3. Flexi EDGE BTS Manager is connected to Flexi EDGE BTS site. 4. The site is un-commissioned successfully. Flexi EDGE BTS Manager is disconnected from the site and closed in the OS. 5. Flexi EDGE BTS Manager is launched successfully. 6. Commissioning Wizard starts and the "Site Specific Information" window appeared on the screen. 7. The data is entered correctly without incident, it is observed that after clicking on the "Next" button it becomes disabled and BTS Manager hangs. 8. Similar results are observed. 9. After clicking on the " SCF Preview " button it becomes disabled and BTS Manager hangs. 10. Similar results are observed. 11. Software is downloaded successfully from Flexi EDGE BTS Manager. Build is successfully attached and activated. BTS site gets reset and comes to supervisory state with no unexpected alarms. 12. "Site Specific Information" window appears on the screen. 13. "Next" button is enabled and BTS Manager does not hang once it is clicked. 14. SCF is saved successfully on the local PC and BTS Manager does not hang after clicking "Save & Exit". 15. "SCF Preview" button is enabled and BTS Manager does not hang once it is clicked. 16. Similar results are observed. Unexpected results: -

Change Note Forms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Change Note Forms

Uploaded by

Copyright:

Available Formats

MENU

Change Note Forms

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 1(42)

GSM/EDGE BTS CN-id: 18704CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 3(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 4(42)

GSM/EDGE BTS CN-id: 18637CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 7(42)

GSM/EDGE BTS CN-id: 18597CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 8(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 9(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 10(42)

GSM/EDGE BTS CN-id: 18513CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 12(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 13(42)

GSM/EDGE BTS CN-id: 18509CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 15(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 16(42)

GSM/EDGE BTS CN-id: 18510CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 17(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 18(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 19(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 20(42)

GSM/EDGE BTS CN-id: 18511CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 21(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 22(42)

GSM/EDGE BTS CN-id: 18512CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 25(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 26(42)

GSM/EDGE BTS CN-id: 18514CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 27(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 29(42)

GSM/EDGE BTS CN-id: 18515CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 30(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 31(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 32(42)

GSM/EDGE BTS CN-id: 18516CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 33(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 34(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 35(42)

GSM/EDGE BTS CN-id: 18517CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 37(42)

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 39(42)

GSM/EDGE BTS CN-id: 18518CNESPE01

DN088147 Issue 4-2 en 22/12/09 Nokia Siemens Networks 42(42)

You might also like