Beruflich Dokumente
Kultur Dokumente
=
before
after before
KPI
KPI KPI
rate t improvemen KPI
For the handover success rate the improvement will be calculated as:
% 100
1
_ _
=
before
before after
KPI
KPI KPI
rate t improvemen Success
Each KPI improvement ratio can be calculated separately over a period of five working days
before and after the optimization cycle (during each days network busy hour).
Any network performance KPIs that are not related to the BSS subsystem should be excluded
from the calculation.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 34 of 61
2. 5. 2 Ra d io Ne t wo r k P e r fo r ma n c e KP I Ca lc u la t io n s
The following calculations will be used for KPIs that are proposed for the radio network
performance evaluation:
( )
+ +
+ + + +
+ + +
+
=
h bsc_i_sdcc h msc_i_sdcc
_detach sdcch_imsi upd sdcch_loc_ g_call sdcch_emer
_re_est sdcch_call orig succ_seiz_ term succ_seiz_
ld_ho sdcch_rf_o o_fail sdcch_radi
_ _ _ Radio Rate Drop SDCCH
( )
+
=
h_tch msc_o_sdcc - tch bsc_o_tch_ - ch cell_tch_t -
- ign_cmplt c_seiz_ass ms_tch_suc
_ho tch_rf_old fail tch_radio_
_ _ _ Radio Rate Drop TCH
=
) _ho tch_rf_old fail tch_radio_ (
om14 res_av_den
ch ave_busy_t
_ _ _ _ Radio Drop to Erlang TCH
=
=
=
7
0
7
5
alX freq_dl_qu
alX freq_dl_qu
_ _ _
x
x
DL Quality Bad TCH
=
=
=
7
0
7
5
alX freq_ul_qu
alX freq_ul_qu
_ _ _
x
x
UL Quality Bad TCH
=
s_to_adj) ho_fail_re - _adj (ho_att_to
o_adj) (ho_succ_t
_ _ _ Rate Success HO Outgoing
Note: These calculations do not include any drops that may occur due to BSS problems, such
as transmission, BSC, TRAU, or MSC.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 35 of 61
2. 5. 3 Ad d it io n a l KP I Ca lc u la t io n s fo r Ne t wo r k P e r fo r ma n c e
Eva lu a t io n
The following calculations provide additional KPIs for network performance evaluation:
=
) _att sdcch_seiz (
) gn sdcch_assi (
_ _ Success Assignment SDCCH
+ +
+ + + +
+ + +
+ +
+ + + +
+ + + +
+ + +
=
h bsc_i_sdcc h msc_i_sdcc
_detach sdcch_imsi upd sdcch_loc_ g_call sdcch_emer
_re_est sdcch_call orig succ_seiz_ term succ_seiz_
_act sdcch_netw _act sdcch_user
_reset sdcch_bcsu fail sdcch_bts_ _fail sdcch_lapd
_fail_old sdcch_a_if _fail_call sdcch_a_if _fail_old sdcch_abis
_fail_call sdcch_abis ld_ho sdcch_rf_o o_fail sdcch_radi
_ _ Rate Drop SDCCH
+ +
+ + + + +
+ + + + +
+ + + +
=
h_tch msc_o_sdcc - tch bsc_o_tch_ - ch cell_tch_t -
- ign_cmplt c_seiz_ass ms_tch_suc
il_call tch_act_fa ct tch_netw_a
reset tch_bcsu_ ct tch_user_a il tch_bts_fa ail tch_lapd_f
il_old tch_tr_fa l tch_tr_fai fail_old tch_a_if_ ail_call tch_a_if_f
ail_old tch_abis_f ail_call tch_abis_f _ho tch_rf_old fail tch_radio_
_ _ Rate Drop TCH
+ + +
+ + + +
+ + +
+ + +
=
il_call tch_act_fa ct tch_netw_a reset tch_bcsu_ ct tch_user_a
ail tch_bts_f ail tch_lapd_f il_old tch_tr_fa l tch_tr_fai
fail_old tch_a_if_ ail_call tch_a_if_f ail_old tch_abis_f
ail_call tch_abis_f _ho tch_rf_old fail tch_radio_
om14 res_av_den
ch ave_busy_t
_ _ _ Drop to Erlang TCH
=
om15 res_av_den
dcch ave_busy_s
_Traffic SDCCH
=
om14 res_av_den
ch ave_busy_t
_Traffic TCH
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 36 of 61
+ + +
+ + + +
+ + + + + +
+ + + + + +
+ + + +
=
_CI cause_good CI cause_bad_ distance cause_low_
d_drop cause_fiel emption cause_pre_ retry cause_dir_
fic cause_traf dm cause_ch_a cause_omc t cause_pbdg cause_umbr
er_dwn cause_intf er_up cause_intf invoc cause_msc_ ance cause_dist
_lev cause_down _qual cause_down evel cause_up_l ual cause_up_q
) cause_X (
_ Cause HO
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 37 of 61
3 Da t a Co lle c t io n Ch e c klis t
SOURCE COMMENTS CHECK
Network Data
BSS Network Configuration
(XML)
BSS Network Configuration
(SQL)
Sector Coordinates File
Traffic File
Mobile Measurements Recordings
Day 1 Day 2 Day 3 Day 4 Day 5
CF Files
DAC Files
RxStatistics Files
BSS Network Configuration
(XML)
BSS Network Configuration
(SQL)
Network Performance Statistics
SDCCH Assignments
Immediate assignments attempts
Immediate assignments failures
SDCCH Traffic
SDCCH traffic per cell
SDCCH congestion
SDCCH Performance
SDCCH drop
SDCCH drop reason
TCH Assignments
TCH assignment attempts
TCH assignment failures
TCH Traffic
Traffic per cell
Traffic FR/HR
TCH Performance
Drops
Drops per reason
TCH Rx Quality
Rx Quality DL
Rx Quality UL
Handover (HO) Performance
per Cell Relation
HO attempts
HO success
HO Performance per Cell
HO types
HO reasons
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 38 of 61
4 Ap p e n d ix A: In it ia l Ac t ivia t io n
4. 1 In it ia l Ac t iva t io n o f t h e CF Fe a t u r e
The CF feature should be activated on each BSC to be measured.
First, log in to the BSC, using the following command from the OSS/NMS:
C7xtermx n bsc_name
To verify activation of the CF feature on the BSC, run the following MML command:
ZWOI:10,65;
The printout will show whether or not the CF feature is activated. 00FF means the feature is
activated; 0000 means it is disabled.
Figure 26: CF Feature Activation
Use the following command for CF activation in case it is not active:
ZWOC:10,65,FF;
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 39 of 61
4. 2 In it ia l Ac t iva t io n o f t h e DAC Fe a t u r e
The DAC feature should be activated on each BSC to be measured.
First, log in to the BSC, using the following command from the OSS/NMS:
C7xtermx n bsc_name
To verify activation of the DAC feature on the BSC, run the following MML command:
ZWOS:2,626;
The printout will show whether or not the DAC feature is activated.
When the DAC is activated, its status will be displayed as shown in the figure below.
Figure 27: DAC Feature Activation
Use the following command to activate an inactive DAC:
ZWOA:2,626,A;
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 40 of 61
4. 3 In it ia l Ac t iva t io n o f t h e RxS t a t is t ic s Fe a t u r e
The RxStatistics feature should be activated on each BSC to be measured.
First, log in to the BSC, using the following command from the OSS/NMS:
C7xtermx n bsc_name
To verify activation of the RxStatistics feature on the BSC, run the following MML command:
ZWOI:10,27;
The printout will show whether or not the RxStatistics feature is activated.
Use the following command to activate an inactive RxStatistics feature:
ZWOC:10,27,FF;
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 41 of 61
5 Ap p e n d ix B: St e p -b y-St e p 3G Upd a t e
Imp le me n t a t io n
5. 1. 1 3G Up d a t e fo r NS N Ne t wo r ks
1. The update will require Netact CM Operations Manager and CM Editor.
IMPORTANT: Modifications to different Network Elements should be implemented
depending on which OSS the 2G cells are located in.
a) If the ADJGs are from one OSS to another (Nokia or another vendor), the modifications
should be made to the Virtual Cells located in the OSS where 3G is (The VCs are under the
BSC-0/BCF-0).
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 42 of 61
The notation of the VCs is BTS-(LAC+CI) . Where LAC takes 5 spaces, for example:
BTS-91 _ _ _ 2081. The maximum allowed is 10 spaces, 5 for LAC and 5 for the CI.
b) If the ADJGs are from one OSS (3G Network) to the same OSS (2G Network also), the
modifications should be to the 3G Cells.
XML Examples for both cases:
Scenario A:
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 43 of 61
Scenario B:
The XML Script of option b is the FP generated by Forte (Set_FP.xml).
2. Prepare the XML script with CM Operations Manager.
Important: Do NOT Provision yet! (Uncheck the Provision option), and click Start.
The Prepare Plan Option checks the plan and whether all the ADJx defined for the site are
actualized in the XML plan (if our plan will modify a parameter related to the ADJxs, the CM
will automatically add the XML code in the plan to update the ADJxs)
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 44 of 61
3. When the plan preparations are finished, open the plan with CM Editor to check if the ADJGs
are correct.
In the above example, the planned and actual values are identical because the plan was
already successfully provisioned. Repeat this step after the Plan Provision finalization to
check if the ADJGs were actualized correctly
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 45 of 61
4. Open the Plan with CM Editor to check if the ADJGs are ready to actualize.
Now you have the MO ADJGs in your plan.
5. For Scenario A, start the Provision. For Scenario B, if the FP has already been executed in
MML, uncheck the Entire Plan scope and check only the RNCs of your ADJGs. For both
Scenarios, there is no need to prepare the plans again.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 46 of 61
5. 1. 2 3G Up d a t e fo r Er ic s s o n Ne t wo r ks
1. Copy Fortes .xml export on the Ericsson UMTS import directory.
2. Go to OSS WCDMA Common Explorer.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 47 of 61
3. Create a New Planned Configuration.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 48 of 61
The New Planned Configuration dialog box is displayed.
4. Import Fortes UMTS update file (.xml)
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 49 of 61
A dialog box is displayed enabling you to select the update file to import.
The progress of the import is displayed.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 50 of 61
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 51 of 61
5. Activate the planned configuration.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 52 of 61
A dialog box is displayed.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 53 of 61
Planned Configuration Activation complete.
6. UMTS Network Update successful
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 54 of 61
5. 1. 3 3G Up d a t e fo r Hu a we i Ne t wo r ks
1. Connect to the Local Management Terminal (LMT).
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 55 of 61
2. Execute FOC CMCTRL to obtain the Configuration Control Right.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 56 of 61
3. Open the Batch Commands to execute Fortes update file.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 57 of 61
4. Open the Forte update file
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 58 of 61
5. Choose where you will save the output file.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 59 of 61
6. Execute Fortes update file.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 60 of 61
7. Close the LMT and release the Configuration Control.
Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 61 of 61