GSM/EDGE BSS, Rel. GSM 18,
Operating Documentation,
Issue 14
Activating and Testing
BSS11073: Recovery for BSS
and Site Synchronisation and
BSS20371: BSS
Synchronisation Recovery
Improvement
DN03284597
Issue 6-0
Approval Date 2013-06-18
Activating and Testing BSS11073: Recovery for BSS and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
Copyright © 2019 Nokia. All rights reserved.
f
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
2
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Table of Contents
This document has 22 pages
Summary of changes..................................................................... 4
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.7.1
1.7.2
1.8
1.8.1
1.8.2
1.8.3
1.9
1.10
2
2.1
2.2
2.3
2.4
2.5
2.6
DN03284597 Issue: 6-0
Activating and Testing Recovery for BSS and Site Synchronisation
and BSS Synchronisation Recovery Improvement........................ 5
Defining the LMU area configuration for BSS synchronisation...... 5
Defining the synchronisation configuration.................................... 6
Activating the synchronisation of the chain.................................... 7
Enabling Abis clock recovery functionality for BSS synchronised
BCF chain...................................................................................... 8
Adding the slave BCF to the chain that has synchronisation
enabled.......................................................................................... 8
Activating the BCF to independent synchronisation mode.............9
Testing Recovery for BSS and Site Synchronisation..................... 9
Testing recovery when BSS synchronisation is lost..................... 11
Testing recovery when BSS synchronisation is restored............. 12
Testing BSS Synchronisation Recovery Improvement.................13
Testing recovery when BSS synchronisation is lost..................... 14
Testing recovery when BSS synchronisation is restored and the
BCF chain is in 'ABIS SYNCH' mode........................................... 15
Testing recovery when BSS synchronisation is restored and the
BCF chain is unsynchronised mode.............................................16
Testing recovery when slave BCF synchronisation is lost (Nokia
UltraSite / MetroSite BTS)............................................................16
Testing recovery when slave BCF synchronisation is restored
(Nokia UltraSite / MetroSite BTS)................................................ 17
Deactivating Recovery for BSS and Site Synchronisation and BSS
Synchronisation Recovery Improvement..................................... 19
Deactivating the synchronisation of the chain..............................19
Deactivating BSS Synchronisation Recovery Improvement........ 19
Removing a slave BCF from the chain.........................................20
Removing the master clock BCF..................................................21
Removing a BCF from independent mode...................................21
Deleting the master clock BCF.....................................................22
© 2019 Nokia. Nokia confidential.
3
Summary of changes
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between 6-0 and 5-0
Updated Activating and Testing Recovery for BSS and Site Synchronisation and BSS
Synchronisation Recovery Improvement chapter to include UltraSite BTS, Flexi EDGE
BTS, and Flexi Multiradio chain combinations.
Changes made between issues 5-0 and 4-0
In the chapter Activating and Testing Recovery for BSS and Site Synchronisation and
BSS Synchronisation Recovery Improvement, syntax have been modified with new
parameters for the feature BSS101562 Flexible Frame Offset Management.
Changes made between issues 4-0 and 3-0
The description chapter Recovery for BSS and Site Synchronisation, and BSS
Synchronisation Recovery Improvement has been removed from this document. These
features are described in the document BSS Synchronisation.
4
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
1 Activating and Testing Recovery for BSS and
Site Synchronisation and BSS
Synchronisation Recovery Improvement
Purpose
These instructions are for activating Recovery for BSS and Site Synchronisation in the
Nokia MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio, and activating BSS
Synchronisation Recovery Improvement in the Nokia MetroSite, UltraSite, Flexi EDGE
and Flexi Multiradio.
g
Note: LMU equipment cannot be connected to Flexi Multiradio 10 and Flexi Compact
BTS.
For a description of Recovery for BSS and Site Synchronisation, see BSS
Synchronisation under Feature descriptions/Radio network performance in the PDF
view.
For a description of BSS Synchronisation Recovery Improvement, see section Benefits
of BSS Synchronisation Recovery Improvement in BSS Synchronisation Feature
descriptions/Radio network performance in the PDF view.
For deactivation instructions, see Deactivating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery Improvement under Test and
activate/Radio network performance in the PDF view.
1.1 Defining the LMU area configuration for BSS
synchronisation
Before you start
You need to create the LMU before creating the LMU area.
Procedure
1
Create the BCF which will be used as the master clock BCF (EFC).
Use the EFC command to create the BCF(s).
ZEFC:<bcf_id>,<site_type>:DNAME=<omu_signalling_link_name>;
2
Define LMU area parameters for synchronisation.
If the LMU area is already created in the RNW database, go to step 4.
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
5
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
3
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Create the LMU area, if it does not exist (EXA).
Use the EXA command to create the LMU area.
ZEXA
:LMUA=<LMU_area_id>:TRE=<tre_id>,BCF=<master_clock_bcf_id>:
FNO=1,LTO=1,FMU=F,LTD=6;
The following parameter values can be used for BSS synchronisation purposes:
•
•
•
•
4
Frame Number Offset (FNO): 0... 51
Time slot offset (LTO): 0 ... 7
LMU FNO 26-Multiplier Usage(FMU): 0 1
LMU TSL FN Delay(LTD): 0 ... 10
Modify the LMU area parameters for BSS Synchronisation (EXB).
See the possible parameter values for the FNO and LTO parameters in step 3.
ZEXB
:LMUA=<LMU_area_id>:BCF=<master_clock_bcf_id>:FNO=1,LTO=1:;
Note that if you leave the Frame Number Offset undefined, the default value N (no
timing signal) will be used.
1.2 Defining the synchronisation configuration
Procedure
1
Defining master clock and slave BCFs of the chain (EFM).
Use the EFM command to define the master clock BCF and slave BCF(s).
In case of BSS11073: Recovery for BSS and Site Synchronisation, the alternative
ways to define synchronisation for the chain are the following:
a) For BSS synchronisation (clock source of the master clock BCF is the LMU), the
command is:
ZEFM
:<master_clock_bcf_id>:CS=LMU,ADD=<bcf_id1>&<bcf_id2>:;
b) For Site synchronisation (clock source of the master clock BCF is BCF), the
command is:
ZEFM
:<master_clock_bcf_id>:CS=BCF,ADD=<bcf_id1>&<bcf_id2>:;
In case of BSS20371: BSS Synchronisation Recovery Improvement, the
synchronisation is defined with the following command:
a) For BSS synchronisation (clock source of the master clock BCF is the LMUABIS), the command is:
6
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
ZEFM
:<master_clock_bcf_id>:CS=LAB,ADD=<bcf_id1>&<bcf_id2>:;
Adding the new slave BCF to the chain (EFM or EFC).
2
This is an alternative way to define slave BCF(s), if the slave BCF(s) are not defined
by the previous command (see step 1).
a) BCF modification (master clock BCF: EFM).
Use the EFM command to add the slave BCF.
ZEFM:<master_clock_bcf_id>:ADD=<bcf_id>;
g
Note: If the master clock BCF's synchronisation is enabled, the administrative
state of the new slave BCF must be locked. You can lock the BCF with the EFS
command.
b) Defining the slave in BCF creation (EFC).
Use the EFC command to create a slave BCF.
ZEFC
:<bcf_id>,<site_type>:DNAME=<omu_signalling_link_name>:::
MCBCF=<master_clock_bcf_id>;
3
Defining a BCF to independent mode (EFM).
Use the EFM command to define a BCF to independent mode:
a) If the BCF is not defined to the master clock BCF, the command is:
ZEFM:<master_clock_bcf_id>:CS=PCM:;
b) If the BCF is defined to the master clock BCF, the command is:
ZEFM:<master_clock_bcf_id>:CS=NONE:;
g
Note: If the independent mode BCF's synchronisation is enabled, the
administrative state of the new slave BCF must be locked before
clock source can be changed to independent mode. You can lock the BCF
with the EFS command.
1.3 Activating the synchronisation of the chain
Procedure
1
Enable the synchronisation of the chain (master clock BCF: EFM).
Use the EFM command to enable the synchronisation of the chain.
ZEFM:<master_clock_bcf_id>:SENA=T:;
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
7
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
2
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Unlock the master clock BCF (EFS).
Use the EFS command to unlock the master clock BCF.
ZEFS:<master_clock_bcf_id>:U;
If the slave BCFs are in the UNLOCKED administrative state and you unlock the
master clock BCF, the unlocked slave BCFs will be restarted and automatically set to
synchronised mode.
1.4 Enabling Abis clock recovery functionality for BSS
synchronised BCF chain
Procedure
1
Define value LAB (LMU-ABIS) to clock source of the master clock BCF of the chain
(EFM).
BSS20371: BSS Synchronisation Recovery Improvement functionality can be taken
into use without service interruption, when BCF chain is in BSS synchronised mode
(the parameter clock source (CS) has value LMU).
ZEFM:<master_clock_bcf_id>:CS=LAB;
2
Output the synchronisation configuration of the BCF (EFL).
ZEFL:<master_clock_bcf_id>:;
Expected outcome
The parameter clock source (CS) of the master clock BCF has value LMU-ABIS.
The BCFs in the chain are in LMU SYNCH mode.
1.5 Adding the slave BCF to the chain that has
synchronisation enabled
Procedure
1
Adding the new slave BCF to the chain that has synchronisation enabled (EFC or EFM).
Adding the slave BCF to the chain can be done in two alternative ways, either by
creating a slave BCF, or modifying the master clock BCF.
8
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
a) Defining the slave in BCF creation (EFC).
Use the EFC command to create a slave BCF.
ZEFC
:<bcf_id>,<site_type>:DNAME=<omu_signalling_link_name>:::
MCBCF=<master_clock_bcf_id>;
Unlock the slave BCF (EFS).
b) BCF modification (master clock BCF: EFM).
Use the EFM command to add the locked slave BCF to the existing (master clock
has been defined) chain.
ZEFM:<master_clock_bcf_id>:ADD=<bcf_id>;
Unlock the slave BCF (EFS).
1.6 Activating the BCF to independent synchronisation
mode
Procedure
1
Enable independent synchronisation mode for the BCF (EFM).
Use the EFM command to enable the synchronisation for the BCF, the clock
source of which is in independent mode in the database.
ZEFM:<bcf_id>:SENA=T:;
2
Unlock the BCF (EFS).
ZEFS:<bcf_id>:U;
1.7 Testing Recovery for BSS and Site Synchronisation
Before you start
You need to have the following equipment available:
•
•
•
•
•
MSC
BSC
LMU or LMUB
UltraSite BTS, MetroSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS
MS
Check that the synchronisation chain or independent mode BCF is working and
Recovery for BSS and Site Synchronisation has been activated.
The allowed chain combinations are:
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
9
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
•
•
•
•
•
•
•
•
•
•
•
•
•
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
UltraSite BTS + UltraSite BTS
MetroSite BTS (chained)
UltraSite BTS + Flexi EDGE BTS
Flexi EDGE BTS + Flexi EDGE BTS
UltraSite BTS + Flexi Multiradio BTS
UltraSite BTS + Flexi Multiradio 10 BTS
UltraSite BTS + Flexi Compact BTS
Flexi EDGE BTS + Flexi Multiradio BTS
Flexi EDGE BTS + Flexi Multiradio 10 BTS
Flexi EDGE BTS + Flexi Compact BTS
Flexi Multiradio BTS + Flexi Multiradio BTS
Flexi Multiradio BTS + Flexi Multiradio 10 BTS
Flexi Multiradio BTS + Flexi Compact BTS
The first BTS cabinet in the chain can be of any type, whereas the second and the rest in
the chain must be of the same type.
The maximum allowed number of BCFs in the same chain is 9.
Procedure
1
Output the synchronisation configuration of the BCF (EFL).
Use the EFL MML command to output the synchronisation configuration of the chain
or independent mode BCF.
ZEFL:<master_clock_bcf_id>:;
a) If BSS synchronisation chain configuration is the case, check that
•
•
•
•
the BCFs of the chain are working
the clock source (CS) parameter of the master clock BCF is LMU
the synchronisation enabled parameter of the master clock BCF is true
(SENA)
the BCFs in the chain are in synchronised mode.
b) If Site synchronisation chain configuration is the case, check that
•
•
•
•
the BCFs of the chain are working
the clock source (CS) parameter of the master clock BCF is BCF
the synchronisation enabled parameter of the master clock BCF is true
(SENA)
the BCFs in the chain are in synchronised mode.
c) If independent mode BCF configuration is the case, check that
•
•
•
•
10
the BCF is working
the clock source (CS) parameter of the BCF is PCM
synchronisation of the BCF is enabled (SENA)
the BCF is in synchronised mode.
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
2
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
If BSS synchronisation chain is the case, check which alarms are currently on (EOL).
Use the EOL command to list the alarms and check that alarm 7787
SYNCHRONISATION MISSING is not active.
3
Set up a call in a TRX for each of the three configuration types.
1.7.1 Testing recovery when BSS synchronisation is lost
Procedure
1
Cause the LMU to lose the GPS signal.
Alarm 8048 LOSS OF INCOMING SIGNAL is received by the BSC. After
approximately 4 minutes from the loss of the incoming signal, the following should
happen:
•
•
•
•
2
Alarm 7602 BCF NOTIFICATION or alarm 7601 'BCF OPERATION DEGRADED'
with the alarm detail 'External Synchronisation Signals disabled' is set active, if
Nokia UltraSite, Flexi EDGE, MetroSite or Flexi Multiradio BTS is the master
clock BCF.
Alarm levelling works in UltraSite, Flexi EDGE, MetroSite or Flexi Multiradio BTS
so that if there is a higher severity alarm active for a given object when a lower
one starts, the lower one is reported at the same level as the existing higher one.
For example, if alarm 7601 was already active for some other reason, alarm
7602 quoted above would be raised to 7601.
Forced handover for TRXs in the chain having ongoing calls starts and the TRXs'
operative state is changed to BL-SYS.
After the handover, first the master clock BCF and then the slave BCFs in the
chain are restarted.
After the BCF Site restarts, BCFs and TRXs are raised to working (WO) again.
Check that the all BCFs in the chain are in unsynchronised mode (EFL).
Use the EFL MML command to check that all BCFs in the chain are in
unsynchronised mode.
3
Check that alarm 7787 SYNCHRONISATION MISSING is active for master clock BCF
(EOL).
Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is active for the master clock BCF.
4
Set up a call in the TRX for the configuration type.
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
11
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Expected outcome
1. The test is successful if one traffic channel state is occupied in the TRX.
2. The test is successful if one traffic channel state is occupied in the TRX, after
recovery action.
1.7.2 Testing recovery when BSS synchronisation is restored
Procedure
1
Cause the LMU to regain the GPS signal.
After alarm 8048 LOSS OF INCOMING SIGNAL is cancelled:
•
•
•
2
Forced handover for TRXs in the chain having ongoing calls starts and the TRX's
operative state is changed to BL-RST.
After the handover, first the master clock BCF and then the slave BCFs in the
chain are restarted.
After the BCF Site restarts, BCFs and TRXs are raised to working state (WO)
again.
Check that the all BCFs in the chain are in synchronised mode (EFL).
Use the EFL MML command to check that all BCFs in the chain are in synchronised
mode.
3
Check that alarm 7787 SYNCHRONISATION MISSING is not active for the master clock
BCF (EOL).
Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is not active for the master clock BCF.
4
Set up a call in the TRX for the configuration type.
Expected outcome
1. The test is successful if one traffic channel state is occupied in the TRX, before
recovery action.
2. The test is successful if one traffic channel state is occupied in the TRX, after
recovery action.
12
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
1.8 Testing BSS Synchronisation Recovery
Improvement
Before you start
You need to have the following equipment available:
•
•
•
•
•
MSC
BSC
LMU or LMUB
UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS
MS
Check that the synchronisation chain is working and BSS Synchronisation Recovery
Improvement has been activated.
The allowed chain combination is:
•
•
•
•
•
•
UltraSite BTS + UltraSite BTS
Flexi EDGE BTS + Flexi EDGE BTS
UltraSite BTS + Flexi EDGE BTS
UltraSite BTS + Flexi Multiradio BTS
Flexi EDGE BTS + Flexi Multiradio BTS
Flexi Multiradio BTS + Flexi Multiradio BTS
The first BTS cabinet in the chain can be of any type, whereas the second and the rest in
the chain must be of the same type.
The maximum allowed number of BCFs in the same chain is 9.
Procedure
1
Output the synchronisation configuration of the BCF (EFL).
ZEFL:<master_clock_bcf_id>:;
Expected outcome
•
•
•
•
2
The BCFs of the chain are working.
The clock source (CS) parameter of the master clock BCF is LMU-ABIS.
The synchronisation enabled parameter of the master clock BCF is true (SENA).
The BCFs in the chain are in LMU synchronised mode.
Check which alarms are currently on (EOL).
Use the EOL MML command to list the alarms and check that alarm 7787
SYNCHRONISATION MISSING is not active.
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
13
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
3
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Set up a call in a TRX of the BCF chain.
Expected outcome
The test is successful if one traffic channel state is occupied in the TRX.
1.8.1 Testing recovery when BSS synchronisation is lost
Procedure
1
Cause the LMU to lose the GPS signal.
Alarm 8048 LOSS OF INCOMING SIGNAL is received by the BSC. You can print the
alarms that are currently on with the EOL command. After approximately 4 minutes
from the loss of the incoming signal, the following should happen:
•
2
Alarm 7602 BCF NOTIFICATION or alarm 7601 'BCF OPERATION DEGRADED'
with the alarm detail 'External Synchronisation Signals disabled' is set active for
the master clock BCF.
The BSC requests locking the BSS synchronisation signal to Abis reference
clock and requests the chain BCFs to work in 'ABIS SYNCH' mode.
Alarm levelling works in UltraSite BTS, Flexi EDGE BTS and Flexi Multiradio BTS
so that if there is a higher severity alarm active for a given object when a lower
one starts, the lower one is reported at the same level as the existing higher one.
For example, if alarm 7601 was already active for some other reason, alarm
7602 quoted above would be raised to 7601.
Check that all the BCFs in the chain are in 'ABIS SYNCH' mode (EFL).
Use the EFL MML command to check that all BCFs in the chain are in 'ABIS SYNCH'
mode.
g
3
Note: If BSS Synchronisation Recovery Improvement software is activated into
use, unlocking or resetting the master clock BCF during 'ABIS SYNCH' mode
causes a reset to all other BCFs in the BCF chain to 'UNSYNCH' mode.
Set up a call in the TRX for the configuration type.
Expected outcome
The test is successful if one traffic channel state is occupied in the TRX after
recovery action.
14
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
4
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
After the BCF chain has been in 'ABIS SYNCH' mode for one hour, check that notice
7788 LONG LOSS OF LMU SYNCHRONISATION is set for master clock BCF (EOH).
1 hour (*) after raising the alarm 7602, the notice type alarm 7788 LONG LOSS OF
LMU SYNCHRONISATION is set for the master clock BCF.
Use the AHP MML command to check that the notice type alarm 7788 LONG LOSS
OF LMU SYNCHRONISATION is active for the master clock BCF.
(*) 1 hour is the default value for the user modifiable
LMUSYN_LOSS_ALARM_LIMIT parameter in PRFILE.
5
Check that chain BCFs are restarted after the BCF chain has been in 'ABIS SYNCH'
mode for 24 hours.
24 hours (**) after raising the alarm 7602:
a) The BSC performs forced handovers in all BCFs of the chain to move the traffic
to the surrounding cells.
b) The BSC restarts the master clock BCF and slave BCFs.
c) Use the EFL MML command to check that all BCFs in the chain are in
unsynchronised mode.
d) Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is active for the master clock BCF.
e) Set up a call in a TRX of the chain.
(**) 24 hour is the default value for the user modifiable
LMUSYN_LOSS_RESET_LIMIT parameter in PRFILE.
1.8.2 Testing recovery when BSS synchronisation is restored
and the BCF chain is in 'ABIS SYNCH' mode
Procedure
1
Cause the LMU to regain the GPS signal.
The BTS requests the BSC to cancel the alarm 8048 LOSS OF INCOMING
SIGNAL.
The BSC requests the chain BCFs to start using the incoming signal from LMU. The
chain BCFs stay on BSS synchronized mode without interruption.
2
Check that the all BCFs in the chain are in 'LMU SYNCH' mode (EFL).
Use the EFL MML command to check that all BCFs in the chain are in 'LMU SYNCH'
mode.
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
15
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
3
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Set up a call in the TRX for the configuration type.
The test is successful if one traffic channel state is occupied in the TRX after
recovery action.
1.8.3 Testing recovery when BSS synchronisation is restored
and the BCF chain is unsynchronised mode
Procedure
1
Cause the LMU to regain the GPS signal.
After alarm 8048 LOSS OF INCOMING SIGNAL is cancelled and master clock BCF
chain is in unsynchronized mode, there are two alternative ways to work:
a) If the PRFILE parameter SYNC_RECOV_ENABLED has value FALSE, the system
takes no action. The BCF chain stays in unsynchronised mode. Alarm 7787
SYNCHRONISATION MISSING stays active.
You need to restart the master clock BCF manually to get the BCF chain to work
in LMU synchronized mode again.
b) If the PRFILE parameter SYNC_RECOV_ENABLED has value TRUE, forced
handovers start for the TRXs in the chain having ongoing calls. The TRXs'
operative state is changed to BL-RST. After the handover, first the master clock
BCF and then the slave BCFs in the chain are restarted. After the BCF site
restarts, the BCFs and TRXs are raised to working state (WO) again.
Use the EFL MML command to check that all BCFs in the chain are in
synchronised mode.
Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is not active for the master clock BCF.
2
Set up a call in the TRX for the configuration type.
Expected outcome
The test is successful if one traffic channel state is occupied in the TRX.
1.9 Testing recovery when slave BCF synchronisation
is lost (Nokia UltraSite / MetroSite BTS)
This procedure is valid both with BSS11073: Recovery for BSS and Site Synchronisation
and BSS20371: BSS Synchronisation Recovery Improvement.
16
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
Procedure
1
Cause the slave BCF to lose the external incoming signal.
•
•
2
The BSC will receive alarm 7602 BCF NOTIFICATION or alarm 7601 BCF
OPERATION DEGRADED with the alarm detail 'Base station synchronisation
failed'.
Forced handover for TRXs in the chain having ongoing calls starts and the TRX's
operative state is changed to BL-BCF.
Check that the BCF that raised the alarm 7602 or 7601 with the alarm detail 'Base
station synchronisation failed' is in unsynchronised mode (EFL).
Use the EFL MML command.
3
Check that alarm 7787 SYNCHRONISATION MISSING is active for the slave BCF
(EOL).
Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is active for the slave BCF, if BSS synchronisation was lost.
4
Set up a call in a TRX for the configuration type.
Expected outcome
The test is successful if one traffic channel state is occupied in the TRX after
recovery action.
1.10 Testing recovery when slave BCF synchronisation
is restored (Nokia UltraSite / MetroSite BTS)
This procedure is valid both with BSS11073: Recovery for BSS and Site Synchronisation
and BSS20371: BSS Synchronisation Recovery Improvement.
Procedure
1
Cause the slave BCF to regain the external incoming signal.
•
•
•
DN03284597 Issue: 6-0
Alarm 7602 BCF NOTIFICATION or alarm 7601 'BCF OPERATION DEGRADED'
with the alarm detail 'Base station synchronisation failed' is cancelled.
The slave BCF is restarted.
After the BCF Site restart, TRXs are raised to working state (WO) again.
© 2019 Nokia. Nokia confidential.
17
Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
2
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Check that the slave BCF is in synchronised mode (EFL).
Use the EFL MML command to check that the slave BCF is in synchronised mode.
The synchronisation mode of the slave BCF is the same as the synchronisation
mode of the master clock BCF.
3
Check that alarm 7787 SYNCHRONISATION MISSING is not active for the slave BCF
(EOL).
Use the EOL MML command to check that alarm 7787 SYNCHRONISATION
MISSING is not active for the slave BCF.
4
Set up a call in a TRX for the configuration type.
Expected outcome
The test is successful if one traffic channel state is occupied in the TRX, after recovery
action.
18
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Deactivating Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
2 Deactivating Recovery for BSS and Site
Synchronisation and BSS Synchronisation
Recovery Improvement
Purpose
These instructions are for deactivating Recovery for BSS and Site Synchronisation in the
Nokia MetroSite , UltraSite, Flexi EDGE and Flexi Multiradio base stations, and
deactivating BSS Synchronisation Recovery Improvement in the Nokia MetroSite ,
UltraSite, Flexi EDGE and Flexi Multiradio base stations.
For a description of Recovery for BSS and Site Synchronisation, see BSS
Synchronisation under Feature descriptions/Radio network performance in the PDF
view.
For a description of BSS Synchronisation Recovery Improvement, see section Benefits
of BSS Synchronisation Recovery Improvement in BSS Synchronisation Feature
descriptions/Radio network performance in the PDF view.
For activation instructions, see Activating and Testing Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery Improvement under Test and
activate/Radio network performance in the PDF view.
2.1 Deactivating the synchronisation of the chain
Procedure
1
Lock master clock and slave BCFs (EFS).
Use the EFS MML command to lock the master clock BCF and slave BCFs of the
chain.
ZEFS:<bcf_id>:L;
2
Disable the synchronisation of the chain (master clock BCF: EFM).
Use the EFM MML command to disable the synchronisation of the chain
ZEFM:<master_clock_bcf_id>:SENA=F:;
2.2 Deactivating BSS Synchronisation Recovery
Improvement
To deactivate BSS20371: BSS Synchronisation Recovery Improvement, change the
synchronisation from BSS Synchronisation to Site Synchronisation. In other words,
change the clock source from LMU or LAB to BCF.
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
19
Deactivating Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Procedure
1
Lock the BCF chain (EFS).
Use the EFS MML command to lock the master clock BCF and slave BCFs of the
chain.
ZEFS:<bcf_id>:L;
2
Change the clock source of the master BCF to 'BCF' (EFM).
ZEFM:<master_clock_bcf_id>:CS=BCF:;
3
Unlock the master clock BCF (EFS).
ZEFS:<bcf_id>:U;
2.3 Removing a slave BCF from the chain
Synchronisation can be activated or deactivated when a slave BCF is removed. If
synchronisation is activated for the chain, then go to step 1, else go to step 2.
Procedure
1
Lock the slave BCF (EFS).
Use the EFS MML command to lock the slave BCF that you are going to remove.
ZEFS:<bcf_id>:L;
2
Remove the slave BCF (EFM).
Use the EFM MML command to remove the slave BCF from the chain. The removal
of the slave BCF is done by modifying the master clock BCF.
ZEFM:<master_clock_bcf_id>:REM=<bcf_id>;
20
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
Deactivating Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
2.4 Removing the master clock BCF
Procedure
1
Lock the slave and master clock BCFs (EFS).
Use the EFS MML command to lock the master clock BCF and slave BCFs of the
chain.
ZEFS:<bcf_id>:L;
2
Disable the synchronisation of the chain (EFM).
Use the EFM MML command to disable the synchronisation of the chain.
ZEFM:<master_clock_bcf_id>:SENA=F:;
3
Remove the master clock BCF (EFM).
Use the EFM MML command to remove the master clock BCF.
ZEFM:<master_clock_bcf_id>:CS=NONE;
g
Note: All information of the synchronisation chain will be lost, when you remove
the master clock BCF.
2.5 Removing a BCF from independent mode
Procedure
1
Lock the independent mode BCF (EFS).
Use the EFS MML command to lock the independent mode BCF.
ZEFS:<bcf_id>:L;
2
Remove the BCF from independent mode (EFM).
Use the EFM MML command to remove the BCF from independent mode.
ZEFM:<bcf_id>:CS=NONE;
DN03284597 Issue: 6-0
© 2019 Nokia. Nokia confidential.
21
Deactivating Recovery for BSS and Site
Synchronisation and BSS Synchronisation Recovery
Improvement
Activating and Testing BSS11073: Recovery for BSS
and Site Synchronisation and BSS20371: BSS
Synchronisation Recovery Improvement
2.6 Deleting the master clock BCF
Procedure
1
Lock the master clock BCF and all BCFs in the chain under it (EFS).
Use the EFS MML command to lock the master clock BCF and all slave BCFs in the
chain under it. Repeat the command for each BCF in the chain.
ZEFS:<bcf_id>:L;
2
Disable the synchronisation of the chain (EFM).
Use the EFM MML command to disable the synchronisation of the chain.
ZEFM:<master_clock_bcf_id>:SENA=F:;
3
Delete the master clock BCF (EFD).
Use the EFD MML command to delete the master clock BCF.
ZEFD:<master_clock_bcf_id>;
g
22
Note: All information of the synchronisation chain will be lost, when you delete
the master clock BCF.
© 2019 Nokia. Nokia confidential.
DN03284597 Issue: 6-0