Change Note Dn0821807

7/28/2019 Change Note Dn0821807

http://slidepdf.com/reader/full/change-note-dn0821807 1/30

Change Note Forms

Id: CX6.0 CD2.0Product Family: Base StationsProduct: UltraSite EDGE BTS Release: CX6.0

DN0821791 1-0

© Nokia Siemens Networks Company Confidential 1 (30)

7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 1527CNESPE07

Title:BCCH TRX stays in configuring state after reset from BTS Manager when NTIM expires

Version of the SW-build:CX6 CD2.0

Valid for Product(s):UltraSite EDGE BTS

References:8803ESPE06, 8182ESPE06

Reason for the Change Note:

Summary of the original problem:When using the Antenna Hopping feature and following a mains failure and the Alarm7955 MAINS BREAKDOWN WITH BATTERY BACK-UP if the BCCH TRX is reset viaBTS Manager then when the NTIM period expires the BCCH TRX is stuck in theconfiguring state.

How end user/operator could detect the problem:By performing the steps described.

Description of the fault:In intelligent shutdown, BCCH TRX can become stuck following timer expiry.

Related feature / functionality Adjustable Intelligent Shutdown feature and Antenna Hopping

Dependency on configuration:No

Workaround:If it’s necessary to reset the TRX then lock/unlock via BSC MML should be used.

Description of the correction:O&M SW is corrected

Effects on operator:TRX gets stuck

Corrected Fault Reports:8803ESPE06: BCCH TRX gets stuck in configuring state after giving reset from BTSManager when NTIM expires

Modified components:gc_trxin.c

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Testing Instruct ions for the change

Pre-requirements:

1. The site is in supervisory state

2. UltraSite:, 4+4+4 Antenna & RF hopping sectors

Sector TRX

ETRX1

ETRX2 (Common BCCH)

ETRX3

1

ETRX4

ETRX5

ETRX6

ETRX7

2

ETRX8

ETRX9

ETRX10 (BCCH)

ETRX11

3

ETRX12

Note: Problem is not band specific

Test execution:

Test steps to reproduce the problem

Teststep

Test Step Instruct ions Output

1BTS Software: CX6 CD1.0

Simulate mains breakdown failure alarm on thesite from BSC by using the following MMLcommand:

ZEFX: <BCF_NO>:INBR=1:ROU=MAINS,POL=OPEN;

7995 mains breakdown alarm isreported on the site.

After the expiry of NTIM timer allnon-BCCH TRXs go to BL-PWRstate at the BSC (i.e. TRX1,3,4,5,6,7,8,9,11 & 12).

2 Reset command is given from BTS Manager for BTS 1.

The BCCH TRX gets stuck inconfiguring state until the expiry of BTIM.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Test steps to verify the correctionTeststep

Test Step Instruct ions Output

1 BTS Software: CX6 CD2.0

Simulate mains breakdown failure alarm on thesite from BSC by using the following MMLcommand:

ZEFX: <BCF_NO>:INBR=1:ROU=MAINS,POL=OPEN;

7995 mains breakdown alarm isreported on the site.

After the expiry of NTIM timer allnon-BCCH TRXs go to BL-PWRstate at the BSC (i.e. TRX1,3,4,5,6,7,8,9,11 & 12).

2 Reset command is given from BTS Manager for BTS 1.

The BCCH TRX comes to workingstate.

Unexpected results : After expiry of NTIM timer when all non-BCCH TRX go to BL-PWR state and for BTS thereset command is given from BTS Manager, then the BCCH TRX still gets stuck inconfiguring state till the expiry of BTIM.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 1542CNESPE07

Title:Mismatch between the Air interface and LMU TDMA Frame Number



References:1-353257333, 22378ESPE01, 26301ESPE01


Original problem: After a site reset, it is possible that a chained site comes up with FN Offset betweenthe chained BTS cabinets The BSS sync is not functioning as expected, the chainedBTS actually goes out of sync (FN offset problem) and there is a mismatch betweenthe TDMA Frame Number in the Air interface and that configured in LMU Areas.

This FN deviation is possible without either a BSC or a BTS Status change, thereforethere are no alarms generated.

Related feature / functionalitySite synchronisationDFCA

How end user/operator could detect the problem:This problem can be reproduced in two ways:1. Taking in/out the clock cable during site reset.2. Give normal site resets.

Then by using TEMS or a similar air interface tool monitor for the FN offset.

Description of the fault:

The FN in use at the site is not the same as that being used by the other LMUSynchronised sites in the network or in the chain.

Dependency on configuration:Chained configuration synchronised using LMU.

Workaround:Reset the site until there is no offset between the FN of the monitored sites visible withTEMS.

Description of the correction:The mismatch between the MUCA FN and the SW FN has been corrected. Also, theFN is now correctly taken account when the site is synchronising with the LMU.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Effects on end-user:

The DFCA feature will be impacted. There will be both handover and call setupfailures.

Effects on operator:There will be unexpected KPI degradation.

System effects:Sites that appear to be synchronised are not actually synchronised so new calls onthese site will drop.

Corrected Fault Reports:

22378ESPE01: BSS sync is not functioning as expected site actually out of sync (FN

offset problem)1-353257333: Mismatch between TDMA Frame Number in the Air interface thanconfigured in LMU Areas26301ESPE01: FN deviation possible without BSC or BTS Status change

Modified components:ph_intglo_testbc_ddl

CXM6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_ CD2.0_OM_INT_PRE008_BL000


The verification of the change in a laboratory requires the use of NSN internal SW toolsand traces and as such it is not possible to prove the fix without these.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 1565CNESPE07

Title: Audio break with AMR HR after handover with TRAU Bicasting feature



References:39524ESPE02


Summary of the original problem: Audio breaks are more than 100 ms for DRTRAU enabled handovers.

Description of the fault:There are noticeable audio breaks for AFS to AHS handovers of more than 100ms.

Related feature / functionality:TRAU Bicasting UL DTX, handover

Dependency on configuration:Problem is seen when both UL DTX and TRAU Bicasting are active.

Description of the correction:DRTRAU Frames being sent by BTS were not using a DRTRAU compatible codecwhen UL DTX was on. Now DRTRAU frames will be sent by BTS only when theTCMC timer has expired and UL codec is equal to the ICM of the target BTS

Effects on end user:There will no longer be long audio breaks during AFS to AHS handovers


39524ESPE02: Long audio breaks in handovers towards AMR HR with DRTRAUfeature

Modified components:

CX_GEN:CX6CD2_EDSP_B001_WS

CX_GEN:CX6CD2_EDSP_B001_BL03

DN0821791 1-1


7/28/2019 Change Note Dn0821807



Pre-requirements:

1. A multitone signal was provided as input to Mobile originating call phone (MO phone). Ideally,this same multitone should be received at Mobile terminated phone (MT phone). Voice output(received by MT phone) of MT phone (keeping this phone muted) is recorded using a soundrecorder. Mobile terminating phone was subjected to Intracell handovers i.e. AMR FR – AMRHR, AMR HR - AMR FR and again AMR FR – AMR HR. Output .wav file recorded is seen aswaveform on Wplay.

Intracell handovers can be triggered by the following MML command in a sector or in a segment.ZEHG:BTS=xx:EIC=Y,EIH=Y;

DR TRAU feature (Feature Code: 582) should be ‘ON’ in the BSC unless otherwise stated.

All test cases must be performed with RDIV enabled at the BSC unless otherwise stated.ICM of target BTS must be a part of ACS of source side.

Codec mode of ICM of target BTS must be either of 4.75, 5.15, 5.90 or 6.70.

Use BTS SW CX6 CD1.0 to reproduce the problem and CX6 CD2.0 for verification of thecorrection.

8. Use BSC SW S13

Tools Required:

Screen box, Wplay, Sound Recorder and input .wav file (providing multitone signal)

Test execution:


Input Expected Output

Configure site as defined in the test case for moreinformation on configuration refer.

Site is in supervisory state.

Configure BCCH TRX traffic timeslots as TCHHand Non BCCH TRXs traffic timeslots as TCHF

Traffic timeslots are configured accordingly.

Lock all traffic channels in the sector. Unlock the7

thtimeslot of the BCCH TRX and the 7 timeslot

of any other non-BCCH TRX.

All TCHs are locked accept two.

Set handover parameters such that handoversoccur repeatedly.(see pre-requirement #2)

Handover parameters are set accordingly.

Set up an AMR call in the BTS to an MS locked toa completely separate BTS and create continuoussound at both mobile stations. Monitor the Abis.

Make sure that the codec in use when a call isestablished and the ICM of the BTS are notsame.

An AMR call is established.Call gets continuously handed over from TCH toanother TCH.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Monitor Abis interface

Record the audio break duration.

The BTS receives a Mode Modify message fromBSC, with the FICM-bit enabled.

The BTS, sends a CMR to TC to step the codec toICM of target BTS

The TC sends a CMI indicating ICM of target BTS.

Upon receiving this message the BTS sends an ACK to the Mode Modify message.

It is to be noted that UL codec mode must notchange as quickly as DL codec mode and it mustfollow the LA principle.

A Channel Activation message is now receivedwith FICM bit enabled. A Channel Activation ACKis sent to the BSC.

As soon as the BSC receives Channel Activation ACK message, the BSC duplicates TRAU datareceived from the A-ter interface both towards thesource and target channels.

An assignment command is sent to the BTS tostart using the newly activated channel.

As soon as the call is handed over to the newly

activated channel, an Assignment Completemessage is sent to the BSC.

Mode Modify is received with FICM bit disabled.

BTS sends a Mode Modify ACK.

Handover is successfully completed and audiobreak duration is less than 100 ms towards AMRFR and is more than 100 ms towards AMR HR

Case Ref. BTS

Type

Configuration

PR39524ESPE02.01 UltraSite 2 Omni EDGE

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Test steps to verify the correction

Input Expected Output

Configure site as defined in the test case for moreinformation on configuration refer.

Site is in supervisory state.

Lock all traffic channels in the sector. Unlock the 7th

timeslot of the BCCH TRX and the 7 timeslot of anyother non-BCCH TRX.

All TCHs are locked accept two.

Configure BCCH TRX traffic timeslots as TCHH andNon BCCH TRXs traffic timeslots as TCHF

Traffic timeslots are configured accordingly.

Set handover parameters such that handoversoccur repeatedly.

Handover parameters are set accordingly.

Set up an AMR call in the BTS to an MS locked to acompletely separate BTS and create continuous

sound at both mobile stations. Monitor the Abis.

An AMR call is established. As the call gets continuously handed over from

TCH to another TCH the following messagesare seen on the GSM Protocol Analyser.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Monitor the Abis

Record the audio break duration.

The BTS receives a Mode Modify message fromBSC, with the FICM-bit enabled.

The BTS, sends a CMR to TC to step the codecto ICM of target BTS

The TC sends a CMI indicating ICM of targetBTS.

Upon receiving this message the BTS sends an ACK to the Mode Modify message.

It is to be noted that UL codec mode must notchange as quickly as DL codec mode and itmust follow the LA principle.

A Channel Activation message is now receivedwith FICM bit enabled. A Channel Activation ACK is sent to the BSC.

As soon as the BSC receives Channel Activation ACK message, the BSC duplicatesTRAU data received from the A-ter interfaceboth towards the source and target channels.

An assignment command is sent to the BTS tostart using the newly activated channel.

As soon as the call is handed over to the newlyactivated channel, an Assignment Completemessage is sent to the BSC.

Mode Modify is received with FICM bit disabled.

BTS sends a Mode Modify ACK.

Handover is successfully completed and audiobreak duration is no longer than 100 ms for AMR FR to AMR HR handovers and AMR HR to AMR FR handovers

Observe the call quality over 50 handovers As the calls get continuously handed over todifferent TCHs in the different TRX of sameBTS, no clipping sound or other disturbing noiseis heard

Case Ref. BTSType

Configuration

PR39524ESPE02.02 UltraSite 2 Omni EDGE

Unexpected results : Audio breaks in handovers towards AMR HR with DRTRAU feature are still excessive andmore than 100 ms.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 1567CNESPE07

Title:Truncated error message while opening CX6 CD1.0 ewb file with CX6 HWC





Summary of the original problem:The error message seen when opening an ewb file with an earlier version of HWC isshown truncated.

How end user/operator could detect the problem:By opening a CX6 CD1.0 file with CX6 HWC

Description of the fault:

Whenever the MMI-EW Interface version is increased, then the length of the error message also increases to account for this. This results in truncated message in older versions that are not expecting the longer message.

Related feature / functionality:XML support in HWC

Dependency on configuration:NA

WorkaroundNA

Description of the correction:Error message fixed to include all the versions.

Faulty component and version:HWC prior to CX6 CD2

Corrected Fault Reports:8348ESPE06: Truncated error message while opening CX6 CD1.0 ewb file with CX6HWC.

Modified components:XmlIFBTS Configuration

CX6_CD2.0_MMI_HWC_PR8348ESPE06_BL001

DN0821791 1-1


7/28/2019 Change Note Dn0821807



Pre-requirements:

UltraSite: Any Configuration

The test is performed with the site in supervisory state.

Test execution:


Test step Test Step Instructions Output

1Install and launch the HWConfigurator of CX6_CD1.0.

HW Configurator is launchedsuccessfully.

2

Create a configuration and save it inxml format (i.e. in .ewb format).

Configuration file is saved.

3Install and launch the HWConfigurator of CX6 version.

HW Configurator is launchedsuccessfully.

4 Open previously saved file. An error dialog is opened.

5 Click on the “Details >>” button.

Dialog expands and error reason is

displayed below the button butmessages are not complete.


Teststep

Test Step Instructions Expected Result

1Launch the HW Configurator of CX6CD2.0.

HW Configurator is launched successfully.

2 Create a configuration and save it in

Xml format (with .ewb extension).

Configuration file is saved.

3 Close the HW Configurator. HW Configurator is closed successfully.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


4 Add some extra Adaptation versionin the schema file raml21.xsd and

change the specification of xml file of the previously saved configurationfile. Adaptation version of theconfiguration file should be larger than the Adaptation version of theschema file.

Adaptation version is changed.

5 Open the previously savedconfiguration file.

An error dialog is opened.

6 Click on the “Details >>” button.Dialog expands and complete error reason isdisplayed below the button.

Unexpected results :The text box on the Error dialog still shows the truncated error reason after clicking on the“Details >>” button.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 1573CNESPE07

Title:

CX MMI conformance to SiteWizard Conformance Requirements

Version of the SW-build:

CX6.0 CD2.0


References:CR299


SiteWizard Conformance requirements for SiteWizard 6 CD2.0 lay down therequirements for all the Element Managers (EMs) installables.

One of the major changes is that the SiteWizard will now be a released quarterly) andall the EMs, which available at that time, will be included in the Site Wizard build.

If the SiteWizard build is not aligned with the Element Manager’s build, then theElement Manager should provide a stand-alone installation to the user.

Following changes will be required in MMI installation process/installable (BTSManager and HW Configurator) to comply with the SiteWizard Conformancerequirements

Check whether MSXML6 is installed on PC or not and if it is not installed, display awarning/appropriate message to the user Note: This change affects only HW Configurator installshield project.

Show a warning to the user that UALC feature is disabled when the Access Levelregistry key is either OFF or is not already present on the system. The warningmessage shall also suggest that the user to enable UALC (if required) either usingSiteWizard or manual step execution.

Currently the CX MMI applications write under the registry keyHKEY_LOCAL_MACHINE->Software -> Nokia, however, as per SiteWizard guidelinesthe registry key should be under HKEY_LOCAL_MACHINE->Software -> NokiaSiemens Networks.

Besides the changes identified above, some changes are required in MMI applicationsto support the NSN re-branded GCS and ITN Element Managers.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


The ITN EMs will be moving to .chm format of Help files as part of Vista support(Q1/2009). To support the launching of these help files from BTS Manager, a change

would be required in BTS Manager.

As part of an earlier CR, CR222 – NSN re-branding for CX MMI applications, theConnection Tool of GCS was changed from ’Nokia Connection Tool’ to ‘NokiaSiemens Networks Connection Tool’ wherever applicable in CX MMI. However, GCShas now changed to ‘GCS connection Tool’. Thus a change is required in BTSManager and HW Configurator to depict the correct name.

Corrected Fault Reports:NA


BTSBTSCommandLineParser btsconnectChildFrmHWC:CommunicationBTSInstallshield:hwconfigsetupbtsmanager

DN0821791 1-1


7/28/2019 Change Note Dn0821807



Items to be tested

Item to be tested are

• CX6 CD2.0 BTS Manager

• CX6 CD2.0 HW Configurator

Hardware Requirements

The table below specifies the HW configurations required for product integration testing of CR299

Identifier Hardware ListC1 • One UltraSite BTS

• Transmission card – FC E1/T1

C2 • One UltraSite BTS

• Transmission card – Any card except FC E1/T1

•

•

Note: Transmission menu embeds in the BTS Manager application only in the case whena FC E1T1 transmission cards is installed in the UltraSite.

Software RequirementsThe table below specifies the SW configurations required for product integration testing of CR299.

Identifier Software Required

S1 • CX6 CD2.0 BTS Manager with CR299

S2 • CX6 CD2.0 HW Configurator with CR299

S3 • E1T1 Manager with its Online Help in chm format

S4 • RRI Manager with its Online Help in chm format

S5 • GCS R6 (Required for all cases)

S6 • Windows Vista operating system

S7 • Windows XP operating system

Test Configurations

Tests SoftwareConfiguration

HardwareConfiguration

Comments

S1 NA

S2 NA

DN0821791 1-1


7/28/2019 Change Note Dn0821807


S1 NA Registry Key of BTSManager

S2 NA Registry Key of HWCS1 NA UALC + BTS Manager

S2 NA UALC + HWC

S2 NA MSXML + HWC

S1 + S3 C1 Ultra + FC E1/T1

S1 C2 Ultra + Any card

S1 Any BTS Manager + GCSConnection Tool

S2 Any HWC + GCS Connection

ToolTOTALTESTS

14

Note: Execute all above test cases on Windows Vista (S6) and Windows XP (S7)operating systems.

Test Cases

Installation/Un-installation

The purpose of this test case is to verify that installation/un-installation process of BTS

Manager and HW Configurator is compliant with Site Wizard Conformance requirements.

Execute following test case to verify the installation and un-installation of MMI applications

Test case 4.1.1.1 of the BTS Manager Regression test specification

Test case 3.2 of the HW Configurator Regression test specification

As part of this test case also test other functionalities like Registry Key, UALC, MSXML etcmentioned in sections given below.

Registry Entry

The purpose of this test case is verify that installable creates the registry key under

‘HKEY_LOCAL_MACHINE->Software -> Nokia Siemens Networks’ instead of ‘HKEY_LOCAL_MACHINE->Software -> Nokia’.

Precondition: Test case mentioned is successfully executed to install BTS Manager application.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Step Input Expected Output

1. Open Registry andverify BTS Manager key.

BTS Manager key is created under HKLM\SOFTWARE\Nokia Siemens Networks.

2. OpenHKLM\SOFTWARE\Nokia

Any existing entry of BTS Manager at this path isdeleted.

Note: Also perform this test case to check Registry entries updates with HW Configurator installer.

UALC

The purpose of this test case is to verify that installer shows a warning to the user thatUALC feature is disabled, if Access Level registry key is either NOT ON or is not alreadypresent on the system.

Precondition: UALC feature is disabled


1. Execute Setup.exe of BTS Manager.

Refer to Regressionspecs for installationrelated test cases.

There will be warning message box of missingUALC feature.

“UALC feature is currently disabled. You canenable it either through SiteWizard 6 CD2.0 &

onwards or manual step execution.Please refer to installation instructions for details.”

2. Click OK button onWarning message box

The installation of BTS Manager continues asper the BTS Manager Regression testspecification.

3. Enable UALC manuallyor through Site Wizard 6CD2.0 (or onwards) andagain start installation of BTS Manager.

There won’t be any warning message of missingUALC.

Note: Perform above test case to check behaviour of HW Configurator.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


MSXML6 DLL

The purpose of this test case is to verify that HW Configurator installable checks whether MSXML6 is installed or not and if it is not installed then it displays warning message to theuser. Also, the HW installable is not installing MSXML6 itself.

Precondition: MSXML6.dll file is not installed.


1. Execute Setup.exe of HW Configurator.

Refer to Regressionspecs for installation

related test cases.

Warning message box of missing MSXML6 dllappears

“MSXML6 dll is missing. Please install it from Accessories folder of SiteWizard 6 CD2.0 build &onwards.”

2. Click OK button onWarning message box

The installation of HW Configurator continues asper the HW Configurator Regression testspecification.

3. Uninstall MSXML6 fromPC and Install HWConfigurator.

Warning message as per step 1 appears andMSXML6 is not installed by HWC installable.

Note: This to verify that MSXML6 is not installedby HWC in previous step.

4. Install MSXML6.dll andagain start theinstallation of HWC.

MSXML6.0 can beinstalled from Accessories folder of Site Wizard or from anyprevious HWC installer.

No warning message of missing MSXMLappears and HWC installs successfully.

Note: There will be no warning message box when MSXML6 is already installed.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Default Installation Path

The purpose of this test case is to verify that MMI application (BTS Manager and HWConfigurator) installer is installing the application at default path (C:\Program Files\Nokia)in case GCS is missing.

The full GUI installation of MMI Applications is not possible in case GCS is missing.However, with silent installation, MMI applications can be installed without GCS.

Precondition: GCS is not installed.


1. Execute Setup.exe of BTS Manager.

Refer to Regressionspecs for installationrelated test cases toinstall application withuser interface.

There is warning on installation wizard screenthat GCS is missing and installation stops.

2. Now, install BTSManager silently andverify installation path.

Refer to Regressionspecs for silentinstallation related test

cases.

BTS Manager is installed successfully atC:\Program Files\Nokia

Note: Also perform this test case to check above behaviour for HW Configurator installer.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


ITN Element Manager Help

The purpose of this test case is to verify that BTS Manager supports Html Help (.chm)format of ITN Element Manager’s online help instead of WinHelp (.hlp) format.

Precondition: The Element Manager as per the test configuration is installed (with onlinehelp in chm format).


1. Launch BTS Manager application.

BTS Manager gets connected to BTS and“Transmission” Menu embeds and“ Transmiss ion Unit Manager” menu itemappears under Help menu.

2. Open help file of ITN

Element Manager fromTransmission UnitManager menu item.

The online help (in chm format) opens up.

3. Open different dialogassociated with menuitems under Transmission Menu.

The online help corresponding to each dialogopen up.

Card Online Help

FC E1/T1 fxce1t1man.chm

FXC E1/T1 fxce1t1man.chm

RRI Fxcrriman.chm

DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 2600CNESPE06

Title:No alarms for slip of internal frame clock following loss/restore of LMU sync



References:43345ESPE02, 21063ESPE05


Summary of the original problem:If the phase difference when tracking back to LMU following GPS restoration is beyondthe DFCA limit, no indication is sent to user. It is also possible, that when this phasedifference is much greater, that the BTS will never regain its synchronisation to theLMU.

How end user/operator could detect the problem:Site will be performing badly and this is seen in the KPI data

Description of the fault:No alarm is generated when the LMU synchronisation to the BTS has a difference of more than 20μs

Related feature / functionality:LMU synchronisation, DFCA

Dependency on configuration:LMU-US (Sync Setup) - DFCA enabled on all cabinets

Workaround:None

Description of the correction:Now when the difference is more than 20μs an alarm indication is sent to the operator warning that DFCA is degraded. This is a 7601 alarm with the text “LOSS OF BSSSYNC WHILE ON ABIS CLOCK” NB: Synchronisation will recover at 5.5μs per hour and the alarm will clear when the difference is less than 15μs

If the difference is more than 40μs a critical alarm is sent to the operator advising BCFrestart. Again this is a 7601 alarm with the text “IRRECOVERABLE LOSS OF BSSSYNCH” It is possible that the sites will not recover and therefore this alarm requires aBCF reset.

Effects on end-user:Call drops, call setup and handover failure.

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Effects on operator:

There is degraded KPI performance.

Faulty component first delivered in (e.g. release, CD):CX5.0


21063ESPE05: No alarm for clock slip of internal frame clock43345ESPE02: BCF fails to correctly track-back to LMU FCLK after being in Abisfallback


glo_ahtah_d_altah_c_altah_diagtah_handtah_inittah_recmp_cab_mainp_cab_pcm

CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_ PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000



DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 2601CNESPE06

Title: Alarm 7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED during start-up

Version of the SW-build:CX6.0 CD2.0




Summary of the original problem: There is an incorrect implementation of the 7616 OSCILLATOR ADJUSTING TEMPORARILY

INTERRUPTED alarm so that the alarm 7616 is not raised in all expected scenarios.

How end user/operator could detect the problem: As alarm is not reported some fault scenarios will not be communicated to theoperator.

Description of the fault:The alarm is not raised in all the expected cases. On further analysis the parametersto raise alarm and validation of DAC word is wrong. So that instead of alarm 7616,alarm 7601 is raised.

Related feature / functionality:DFCA

Dependency on configuration:LMUB - Ultra. However LMUA (LMU Fly can also be used)

Workaround:None

Description of the correction:DAC word Mean checks were insufficient to detect the DAC word fluctuations seen inthe reported problem, this is now corrected.

Effects on end-user:Possibility of handover and call setup failures until site is correctly synchronised.

Effects on operator:Degradation of KPI


43295ESPE02: Incorrect implementation of 7616 OSCILLATOR ADJUSTINGTEMPORARILY INTERRUPTED alarm

DN0821791 1-1


7/28/2019 Change Note Dn0821807



p_cab_pcmp_cab_mainp_cab_rssi

CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000CX6_CD2.0_OM_INT_PRE008_BL000



DN0821791 1-1


7/28/2019 Change Note Dn0821807


GSM/EDGE BTS

CN-id: 16037CNESPE01

Title:BTS information is missing in NetAct Hardware Browser



References:1-356828482


Summary of the original problem:When the hardware information is viewed in the NetAct Hardware Browser then noBTS identity is shown for unit type for example TSxx.

How end user/operator could detect the problem:When viewing individual BCF records in Hardware Browser the BTS identity is notshown for unit type TSxx.

Description of the fault:BTS identity is not added to the BTS HW REPORT Abis message for TSXs

Related feature / functionality:BTS HW REPORT

Dependency on configuration:None

Workaround:Obtain BTS identity from MML commands at BSC.

Description of the correction:

The missing identity information is added to the BTS HW REPORT Abis message.

Effects on end-user:None

Effects on operator:BTS identity is not available in the NetAct Hardware Browser

System effects:None

Other effects:None

Faulty component and version:BTS HW REPORT

DN0821791 1-1


7/28/2019 Change Note Dn0821807


Corrected Fault Reports:1-356828482: BTS information is missing in Hardware Browser

Modified components:bc/gc_hwinq

cx6cd2_om_ul_b004#1

Effects on Operator BTS identity is now available in the NetAct Hardware Browser

DN0821791 1-1


7/28/2019 Change Note Dn0821807



Pre-requirements:1. In order to access Nokia NetAct OSS, you must have Citrix ICA Client installed on thePC. Citrix Independent Computing Architecture (ICA) protocol is one of the remoteterminal services supported by Windows, in addition to the native Microsoft RemoteDesktop Protocol (RDP).

Test execution:


Input to Reproduce the Problem Expected Output

BTS SW CX6 is used.

O&M on NetHawk is monitored. BTS HW Report: - Hardware unit identity for TSX hasIndex Number, BCF Number, BTS 255 and TRX 255information displayed. The BTS and TRX are incorrect.

Login to Nokia NetAct OSS. Login is successful

From the NetAct Start page select'Desktop' and launch the 'Top LevelUser Interface application.

Application starts

From the NetAct Start page select'Administration' and launch the 'NetActHardware Browser'.

Hardware Browser will displayPLMN-PLMN/BSC-xxxxx/BCF-xx/TSxx-xNo BTS information displayed, this is unexpectedbehaviour.

Case Ref. BCF Configuration

356828482.01 Any 12 TRX UltraSite

DN0821791 1-1


7/28/2019 Change Note Dn0821807



Input to Verify the Correction Expected Output

BTS SW CX6 CD2.0.

O&M on NetHawk is monitored. BTS HW Report: - Hardware unit identity for TSX has Index Number, BCF Number, BTSNumber and TRX Number informationdisplayed. The BTS and TRX numbering iscorrect for each unit.

Login to Nokia NetAct OSS. Login is successful

From the NetAct Start page select 'Desktop' andlaunch the 'Top Level User Interface application.

Application starts

From the NetAct Start page select 'Administration'and launch the 'NetAct Hardware Browser’.

Hardware Browser will display

PLMN-PLMN/BSC-xxxxx/BCF-xx/BTS-xx/TSxx-x

BTS information displayed, this is expectedbehaviour.

Case Ref. BCF Configuration

356828482.02 Any 12 TRX UltraSite

Unexpected results :The BTS information is still not present in the Hardware Browser.

Change Note Dn0821807

Documents

Transcript of Change Note Dn0821807