document on gsm optimisation

Radio Network Optimisation course RANOPcalculate performance indicating figures
relate optimization to Nokia features
learn from experience with case studies
practise the learning during group works
b
- Open discussion
- Try to "steer" discussion on to subscriber and operator perspective…
- DCR, DT, NMS, Maintenance costs, Efficiency, Resources, Subscribers, Earn Money...
* © NOKIA FILENAMs.PPT/ DATE / NN
Handout
b
Quality improvement: 0,5 days
- Describe how quality cycle fits into business
- Describe how quality cycle starts out general then gets into the specific and measurable (from Management to Network Planning Engineers)
- Large Quality Cycle ~ 1 month - 1 year (not fixed, depends on business situation)
- Small Quality Cycle ~ 1 day - 1 month (Optimization process)
- Relate each box to day to day activities and Management
What is network quality ?
- Use White Board to record ideas from class…
- Try to "steer" discussion into two separate classes: subscriber and operator perspective…
- Distribute and summarize Hand-out #1
- Balance Investment versus Achieved Quality
agreements between different departments
differ from area to area (e.g. urban, suburban, motorway, etc.)
values change in time (e.g. increasing demands for CSSR and CCR)
weight of targets changes in time (e.g. network capacity becomes more important)
Must be flexible and also communicate impact of evolving network...
Quality
Capacity
Coverage
Time
Who is setting the quality targets ?
Targets
b
Call Completion Rate (CCR)
Call Quality
Operator relevant:
H/W Failure
Network Configuration
Network Traffic
Spectrum Efficiency
Quality targets could be set by :
General director
Marketing director
Handout
Priority
Targets
b
NMS
- Ask "why customer complaints?"
- Because they are part of the perception of quality of the network.
- Must also keep in perspective (I.e. CEO complaints).
- Ask "why not Planning Tool?"
- Because it is not the real system.
- Use White Board to ask class what advantages and disadvantages are for all three types of quality monitoring. (try to use green and red pens)
- After several points for each add weighting and priority
Building
Not efficient for optimizing a whole network
Difficult to distinguish between ms and bs
Good co-operation between network optimization and customer service department is needed
Might pinpoint location of problem
Helps to find not known problems
Reports indoor coverage holes
Monitoring
b
----
Restricted to specific areas
Supply only downlink information
Good to geographically locate problems
No real customer view due to too high quality equipment
Helps to adjust propagation models
Suitable for competitor analysis
- Pro-active preventative maintenance
Limited geographical location of
network quality
Permanent information flow
Field Tests
Customer Complaints
Exercise?
---
- Allows you to zoom into problem area
- NMS stores huge amount of data
- Easier to prioritize
- Main problem is only as good as maintained (I.e. requires well trained OMC personnel and good operation procedures)
- NMS not reliable at beginning of network roll-out when there is "low traffic".
- Emphasize impact of all members on Optimization
Management (progress in roll-out)
Network Planning (feedback on coverage, frequency and parameter planning)
Network Optimization (impact of optimization)
Each level in the pyramid is a "filter".
By the top level, a single Quality figure (Health index) should be given to Management
Technical Management looks at BSC level
Relate Optimization requirement to quality cycle (as a means to achieve the desired quality factor)
By the lowest level, analysis is broken down to the detailed single issues (I.e. Timeslot level)
Earliest time for Exercise (State Diagram for HO & PC)
BH
Usage pattern (I.e. lower cost after 6 pm)
Sample graphs only
Key point is must have Quality Perspective (I.e. Can't measure = Can't manage).
Must be standardized and consistent across network.
Use automated tool (I.e. NMS and Metrica) to generate "Health Index" trends.
This shows trends and identifies how the "Health Index" should be evolved as the network evolves.
Helps to identify when expansion or major changes may be required to the network.
CSSR - Call Setup Success Rate
CCR - Call Completion Rate
MOC - Mobile Originated Call
MTC - Mobile Terminated Call
Quality Indicator
Reporting
b
b
Good to get trainee's expectations to the training at this point
- Large cycle months - years (managerial trending & business / network development and planning)
- Small cycle days - weeks (technical optimization)
- Need to define scope of optimization
- On-going by dedicated NWP personnel (Continuous cell level optimization)
- Criteria (top 15 cells, KPI thresholds)
- Propose mini-network "Micro-Comm" (Draw Picture)
- Ask how many parameters in this small network?
- > 4000 parameters
Planned system configuration
configuration
Configuration
b
----
Configuration
- ADCE
- BTS
All BSS parameters in both the BSC and the NMS
One site results in many parameters
Use of default parameter sets needed !!!
NMS
Configuration
BTS
HOC
POC
BTS
HOC
POC
BTS
HOC
POC
ADCE
ADCE
ADCE
b
How many parameter entries does one site have in the
databases ?
+ ADCE, adjacent cell parameters x 6 (or more)
-> more then 1000 parameters for one simple site
Inconsistency and History tracking?
Reference: What is supposed to be in the network now
Actual: What is actually in the network now
Planned: Next planned parameter settings
History: Track changes
E.g. run checks between reference-actual-planned, inconsistencies could be automatically changed with confirmation from planner/NMS operator
E.g. automatic link can be made between databases (cron scripts at night: master database updated)
5% cell specific param.
Configuration
NMS
b
95% of a cell's parameters are normally default and 5% are cell specific (e.g. frequency, adjacencies, and specific "optimized settings")
Characteristics
logical
measurable
Engineering rules are queries that can be run on a database to check the settings of some non-default parameters.
Configuration
b
Adjacency Discrepancies (ND Report 060)
Non-symmetrical Adjacencies (ND Report 061)
Adjacent Cell with same or adjacent Frequency (ND Report 062)
Adjacencies to Non-existing Cells (ND Report 065)
Synchronized HO (ND Report 067)
BTS Parameter Survey (ND Report 068)
BTS Default Parameter Audit (ND Report 063)
ND = Network Doctor
other checks are supported by the Network Doctor (T9/T10)
Check documents for more features (e.g. cells with dominant distance range)
NMS
(OMC)
Master
Configuration
database
Cell B is deleted but incoming adjacencies were not removed
Cell C is not known in OMC Area 1 database
Cell B
Cell A
Cell C
OMC 1
OMC 2
BSC 1
BSC 2
Configuration
b
- Watch for deleting sites and re-adding with same old BSC ID
- Ensure OMC personnel grooming… Inter-OMC parameter management
Every adjacency should be towards an existing cell.
In this report all adjacencies are checked so that the adjacent cell
(c_bts:ci, lac) really is found in the NMS/2000 database in the c_bts table.
Instruction:
If found after comparing the report to the plan, remove such adjacencies .
Source Source Source ADJ.CELL ADJ.CELL
BSC (BTS id) BCF/BTS BTS int_id LAC CI
--------------- -------------------- ---------- -------- --------
CSB02A
CSB02B
SEA0142A
SEA0142B
Configuration
b
Cell B is neighbor of Cell A
Cell A is not neighbor of Cell B
Cell A
Cell B
This report shows all missing adjacencies assuming that all adjacencies
should be symmetrical (bi-directional).
Add the neighbors if missing
Note: There may be cases when only one way neighbor relation is required
from cell to cell
cell/bcf name cell/bcf name
----------------------------------- ---- ----------------------------
Cell A has carrier 10
Cell B has carrier 9, 10 or 11
Cell A
Can Swap BCCH + 2nd TRX. Also check Frequency/BSIC combination
Do not allow same frequency and BSIC on up to 3rd level adjacency
Adjacent Cell with Same or Adjacent Frequency (062)
This report displays all adjacencies where a cell and its adjacent cell
have the same frequency (f) or adjacent (f-1 or f+1) frequency.
Adjacent cells should never have the same BCCH and BSIC.
Same frequencies should not be used in adjacent cells. Also the f-1 or f+1
situation should be avoided if possible.
Source Source Target Target
-------------------- ---------------- -------------------- ----------------
(U)Forest site-1 4 (20111,2901) (U)Site F-1 55 (20381,2902)
(U)Forest site 56,4,5 (U)Site F 56,4,0
(U)1(BCCH) Town X_BSC0 (U)1(BCCH) Town X_BSC0
(U)Forest site-1 4 (20111,2901) (U)West Harbours -1 13 (20151,2901)
(U)Forest site 56,4,5 (U)West Harbours 55,4,4
Configuration
b
Synchronized handover
Non-synchronized Handover
MS sends access bursts (HO_ACCESS) (with varying TA) until it receives PHYSICAL_INFO
Synchronized Handover
MS sends a few access bursts (HO_ACCESS) and then starts transmission with previous TA
Non-synchronized handover leads to a longer communication interruption than synchronized handover (200ms vs. 100ms)
Non-Synchronized
Synchronized
Configuration
Same site above actually means "same BCF".
Generally don't use synchronized handover with repeaters, but in some cases it could work
Different Suppliers -> 100% Failures
Network Doctor Report
Synchronized Handover (067)
Synchronous HO means that the MS uses the old value of Timing Advance.
Non-synchronous HO means that the MS gets the new value of Timing Advance.
Only adjacent cells in the SAME SITE should have synchronous HO
Source Source Target Target Target
*************** *************** *************** *************** ******
BTS BTS LAC SYN
(11) 3358 (12) 30102 15000
BSC111 Phantom st BSC111 Phantom st 3358 No
(12) 30102 (11) 3358 15000
Configuration
b
Find all adjacencies with mismatched frequencies:
In BSC, Cell A has Cell B Ch.690 as neighbor (Channel was defined using MML)
In NMS, Cell A has Cell B Ch. 700 as neighbor (Adjacencies were not uploaded)
Cell A
Ch. 694
Network Doctor Report
Adjacency Discrepancies (060)
Parameters in the first line show the values in the adjacency (ADJ) of a source
cell. Parameters in the second line (TGT) show the values in the target cell.
Impact of discrepancies:
Any difference between two identical parameters of the target BTS and
the same parameter of adjacency usually results in handover failures between
the source and the target BTSs.
LAC CI FREQ PMAX NCC BCC
=== === === ==== === ===
------------------ ---------------------------- ------ ------ ---- ---- --- ---
Configuration
b
HoMargin A->B + HoMargin B->A > 6 dB
Configuration
BTS Default Parameter Audit
BTS Defaults:
Exercise?
BTS Parameter Survey (068)
This report shows the usage of the parameters in the network or part of it.
The first row shows the default parameter and the following rows show the
parameter value different from the default.
Instructions: Report 068 shows only the count of objects (BSC, BTS, TRX, ADJ)
using the default value and value different from default.
To know the objects using values different from default, use report 063.
HO Period PBDGT (HPP) COUNT
-------------------------------------------------- ----------
-------------------------------------------------- ----------
BTS Default Parameter Audit (063)
A comparison is made against the defaults stored in the NMS/2000 database.
Instruction:
Verify the reason for the object having value different from the default value.
If there is no valid reason for the object to be different from default, change it to
default value.
Name in NMS GUI: HO Period PBGT
BSC name BCF name Default Actual
BCF id : BTS id BTS name value value
--------------- --------------- -------------------- -------
6 : 11 MAKKYL1
6 : 12 MAKKYL2
Organization - Reporting - Nokia specific counters/DX-causes
Start on top with Reporting, then measurements and further down to Observation. Defining DX-causes and building up through counters to KPI's.
Quality
- basic measurements run continuously
Observations - to determine certain problems
- observed object must be known
- delivers information on BTS, TRX and TSL level
- produces huge amount of data -> temporary use only
IMSI Tracing - delivers information concerning a certain subscriber
- valuable for analyzing customer complaints
- pinpoint failures by analyzing the observation reports
Counters
KPI's
DX-cause
Quality
What is the difference between Observations and IMSI tracing?
Observation gives DX-causes for a network element, while IMSI tracing is on a subscriber.
MSC
B
S
C
B
T
S
N
M
S
DX cause is Nokia network element specific
N1: Several DX causes are mapped to one GSM cause
N1: Several DX causes are mapped to one counter
Note:
GSM cause is also called BSSMAP in Nokia docs
Counters are actually generated in the BSC, but are visually presented in the NMS on this drawing
How to detect faults?
Counters
KPI's
DX-cause
Quality
How do computer program blocks communicate with each other?
There is some kind of master program block around all other program blocks, and the individual program blocks are "controlled" by the master PRB. The master PRB checks cause in = cause out and takes appropriate action.
Note:
It is only the DX cause cause values in and out which have to be equal, not phase or the channel type, for a program block to end successfully
Events
b
section 6: Which DX causes are generated by which Program Blocks?
section 5: Which counters are updated by which DX causes
Section 5: Cause Codes - call phase handled by program block + fail causes emitted by the program block
Doc 5? Mapping
Cause Code: Code Number used internally to ID events during a call
DX Cause: Cause Codes that Describe in Detail how the transactions have succeeded.
Clear Code: A Cause Code which identifies the reason for clearing the call or a call setup.
GSM Cause Codes:
Each Program Block does different checking's (Eg. Est. Cause Valid?)
Checking's are linked to cause codes (eg. Rej_phantom_res)
Several Cause Codes are "summarized" or mapped to counters.
Mapping depends on the call phase (eg. SDCCH act Fail or TCH act Fail)
Cause Codes can be collected by observation.
AIVPRB = A interface Signaling Program Block in BSC
HASPRB = Handover Attempt Supervisor Program Block
RC0PRB = Resource Control Program Block in BSC
RCSPRB = Radio Connection Supervision Program Block
RRMPRB = Radio Resource Management Program Block
SC7PRB = Speech Circuit Control in GSM BSC A Interface
Counters
KPI's
DX-cause
Quality
PRB A
PRB B
DX Cause
are in section 6.
Each phase is handled completely by one program block in the BSC (but some blocks may handle more than one phase)
Sheet1
PHASE
PHASE_NAME
1
Paging
2
AUTHENTICATION (SDCCH)
[Supplementary References, BSC Counters: Traffic measurement]
EXPLANATION: Number of the SDCCH transactions ended due to a failure in the Abis interface during a call in progress. There is no acknowledgement of channel activation, no indication of call establishment received, i.e., ghosts.
UPDATED: When an SDCCH transaction ends due to signaling
problems in the Abis interface and the RRM releases the SDCCH.
Reasons that trigger the counter:
Phantom RACHs that have a valid establishment cause.
The BTS can hear the MS, but the MS cannot hear the BTS, and so the MS does not respond to the IMMEDIATE ASSIGNMENT message with a SABM.
MS is accessing the network at the limit of sensitivity and messages are lost.
Poor Radio conditions.
MS is accessing network through another BTS (co-channel, co-BSIC interference).
IMPACT: Call cleared
abis_fail_block_c (304)
abis_msg_corrup_to_bts_c (305)
block_slave_c (307)
ch_act_fail_c (314)
data_ind_corrup_c (319)
estab_ind_fail_c (321)
estab_conf_fail_c (322)
mode_mod_ack_fail_c (326)
no_meas_result_c (327)
no_resp_from_copro_c (328)
phy_cont_conf_fail_c (329)
rcs_alg_start_ack_fail_c (330)
rcs_alg_cl_ack_fail_c (331)
rf_ch_rel_ack_fail_c (333)
rel_ind_fail_c (335)
signaling_error_c (336)
sapi_3_fail_c (343)
sub_timer_c (367)
estab_ind_corrupted_c (370)
has_state_conflict_c (505)
Number of SDCCH transaction failures due to an Abis interface failure during call (incremented only in phases 1-8)
Counters
KPI's
DX-cause
Handout
Quality
whose contents have been corrupted.
22. estab_ind_fail (321)
23. estab_conf_fail (322)
The A-bis interface receives an establish_confirm message.
The contents of the message have been corrupted or a timer expires
while waiting for the message.
Counters
KPI's
DX-cause
[Functional Description, BSS Operability, Basic Protocols, Call Related DX cause in BSC]
Handout
Quality
Find the DX-cause cause values updating 001075
Section 6: "Call-related DX Causes in BSC"
Find the description of the DX-cause cause values
319
321
322
Find description of DX-cause phase 3 (Basic assignment)
Counters
KPI's
DX-cause
Handout
Quality
Section 6: "Call-related DX Causes in BSC", Page 25
Section 6: "Call-related DX Causes in BSC", Page 9-10
DX-cause phase 3
The DX cause phase 3 covers the mobile subscriber assignment signaling from the SDCCH to the TCH by means of the Basic Call Setup.
The ABIPRB is responsible for this phase.
Success:
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
Failure:
When a failure has occurred, the successful cause is overwritten with the failure cause and the signaling is continued as call clearing. The RRMPRB updates the failure counter.
Counters
KPI's
DX-cause
Handout
Quality
Target Cell List for Handover Observations
Radio Measurement Report
b
Here the examples with the real Observations (HO and SDCCH) should be used instead of the following slides
…
...
Tracing Reference : 256
BTS ID : 9
TRX ID : 5
CH Type : TCHF
Subchannel Number : 0
Cell ID : 12061 12062 12083 12082
Cell NCC :
Cell BCC :
Cell BCCH :
------------- ------------------ --------------
Index DTX RxL RxQ DTX RxL RxQ TA RxL RxL RxL RxL
(dBm) (BER) (dBm) (BER) (dBm) (dBm) (dBm) (dBm)
1 NO -101 4.53 NO -82 0.14 2 -105 -87 -94 -100
2 NO -95 0.14 NO -82 0.14 2 -105 -87 -94 -100
3 NO -96 0.14 NO -79 0.14 2 -105 -89 -92 -98
4 NO -96 0.14 NO -81 0.14 2 -104 -90 -91 -100
5 NO -95 0.14 NO -84 0.14 2 -104 -96 -93 -96
6 NO -96 0.14 NO -82 0.14 2 -104 -90 -99 -96
7 NO -97 0.14 NO -82 0.14 2 -104 -88 -100 -96
8 NO -97 0.14 NO -86 0.14 3 -108 -90 -101 -100
9 NO -99 0.14 NO -81 0.14 3 -108 -88 -98 -97
10 NO -97 0.14 NO -82 0.14 3 -104 -86 -91 -97
11 NO -98 0.14 NO -83 0.14 3 -105 -87 -93 -98
12 NO -98 0.14 NO -81 0.14 2 -105 -87 -102 -98
13 NO -95 0.14 NO -78 0.14 2 -107 -87 -101 -94
14 NO -95 0.14 NO -79 0.14 2 -107 -85 -93 -94
15 NO -95 0.14 NO -80 0.14 2 -108 -86 -96 -95
16 NO -94 0.14 NO -80 0.14 2 -106 -86 -96 -99
17 NO -96 0.14 NO -80 0.14 2 -105 -86 -97 -96
18 NO -95 0.14 NO -80 0.14 2 -104 -86 -102 -97
19 NO -95 0.14 NO -79 0.14 2 -107 -86 -99 -96
- TCH related measurement part
Resource Availability M. - Availability of TCHs and SDCCHs
- Time congestion of TCHs and SDCCHs
- average and peak num. of busy TCHs
and SDCCHs
Resource Access Meas. - number of messages sent in Abis interface
- number of seizures for MOCs and MTCs
- average load on control channels
Handover Measurement - number of successful/unsuccessful HO
- Handovers per cause
per Rx Quality band
Last one is at TRX level
Measurement Periods: 1 hr, 6hr? (without overloading NMS)
Section 8?
consists of:
and
Counters
KPI's
DX-cause
Quality
Table naming (P_NBSC_TRAFFIC)
Interrelation between tables (different table types linked to give meaningful output)
Counter Number is 6 digits
Following this slide the MOC and HO signaling slides should be placed? MTC, SDCCH, HO.
Section 8?
Sheet: Sheet1
measurement type
additional call attempts
TCH_CONG_TIME (10ms resolution)
time
TSL:
0
BCCH/SDCCH
Counters
KPI's
DX-cause
Quality
---
Congestion figures for NOKIA are higher since ERICSSON counts only when extra TCH requested (I.e. Blocking condition)
8
0
TCH
t
Congestion
Congestion
Blocking
648
20 sec sampling rate is also used for SDCCH traffic
---
The denominator is used since the measurement period can change
20 second Sampling period will satisfy the 1/2 "Nyquist Rate" for average call length of 40 seconds/ call
1 Erl = n * A / 3600 seconds
where:
Gives a quick overview about differences in UL and DL
Can pinpoint hardware or interference problems
Database table: P_NBSC_RX_QUAL
- Human ear can detect RX Qual 5
Link Imbalance for quality so we use LNAs, TRX, Antennas to try to compensate.
Sheet1
BER
< 0,2%
Results can be shown on TRX, BTS or BSC level
Gives a quick overview about interference
and imbalance situation
Database table: P_NBSC_RX_STATISTICS
number of samples
---
- Draw Diversity gain Graph:
- Consider PC skew and highlight where interference is identified
- Report 204...
Rx Sensitivity
Easy to find unnecessary neighbor relations
Optimize Location Areas
Database table: P_NBSC_HO_ADJ
- Cleanup Adjacencies
- 12 - 15 adjacencies ideal
HO Adjacent Cell Statistics
Cells having High Handover Failure (150)
This report shows HO failure rates for all cells sorted by failure rate.
Instructions:
- One very potential reason for a high HO failure percentage is interference.
Run Interference report (190) for cells with bad HO performance.
- Another possible reason are the discrepancies in adjacencies.
Run the adjacency check by using reports (060, 061).
Tot
BSC (BTSid) % % % % % %
ABCDEFNT MSC o: 1381 3.2 0.1 0.0 2.1 -
STTLBSC5(21) BSC i: 2013 1.2 0.0 - - 0.1
BSC o: 2051 10.5 0.0 0.0 1.4 0.2
Cell : 64 0.0 0.0 0.0 0.0 0.0
b
UL DL MS
*** *** Dist CI spee
qua qua *** *** Slow ***
BTS NAME lev lev high MSC Pre Fld Bad Mov slow
BCF NAME itf itf low Umbr PBGT DR emp drp Good MS high Nbr of
BSC (BTS id) (%) (%) (%) OMC( (%) (%) (%) (%) (%) (%) (%) HO att
---------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
ABCDEFNT3 3 18 0 0 26 0 0 0 0 0 0 3496
ABCDEFNT 20 30 0 0 0 0
STTLBSC5(21) 0 3 0
Source Target
****** ******
BTS NAME HO=> HO=> HO=> <=HO <=HO <=HO Target BTS NAME
BCF NAME **** **** **** **** **** **** ****** BCF NAME
BSC NAME (BTS) Att Blck Fail Fail Blck Att LAC BSC NAME (BTS)
BAND (%) (%) (%) (%) CI BAND
ABCDEFNT 3203 MNOPQRRE
ABCDEFNT 3321 ABCDEFNT
ABCDEFNT 3332 JKLMNOER
ABCDEFNT 3331 JKLMNOER
ABCDEFNT 3322 ABCDEFNT
ABCDEFNT 3302 WXYZAM
Shows real cell range
Database table: P_NBSC_TIMIMG_ADVANCE
Mention example about picking up traffic from far away
---
- Draw Timing advance Graph
- Show how subscriber "hot spots" can be identified (550 m / TA)…
- Measurement period of 6-24 hours
- Show Example 232 Report
range Freq of range power power power
(km) reports (%) (dBm) (dBm) (dBm)
-------- -------- ------- ------ ------ ------
16.50 0 0.00 -- -- --
22.00 0 0.00 -- -- --
34.65 0 0.00 -- -- --
b
Describe origin of this statistics (Timeslot allocation algorithm) and give some examples of timeslot allocation.
Also measures in active mode during DTX.
Data Flow to NMS
CMISE - Common Management Information Service Element (Upload Measurements)
Section 7?
CMISE
wbpmanmx
/var/tmp
wftmanmx
edmmanmx
NMS/2000
Measurements
Flag:
Open
Full
Waiting
Compressed
Transferred
FTAM
Q3
BSC
Measurement flow from BSC to NMS
1.Measurements are collected and stored in the measurement file. The status flag of the file in question in the ring buffer is Open.
2.When the file is full the flag is changed to Full.
3.If the BSS Measurement Data Transfer feature is on, the flag is changed to Waiting (to be compressed).
4.When the measurement file is compressed, the flag is changed to Compressed.
5.CMISE sends a request with the name of the measurement file to the edmmanmx process that the measurement file is ready to be transferred.
6.wtfmanmx receives the request including the measurement file name.
7.FTAM starts transferring the data from the ring buffer in the NE and stores it in /var/tmp .
8.wtfmanmx sends a message to the ring buffer via CMISE that the measurement file has been transferred. The flag is changed to Transferred.
9.wbpmanmx reads the measurement files from /var/tmp and decodes the information and stores it in the NMS/2000 database.
[NED NMS/2000: System Administrator's Guides, System
tuning, Performance measurement collection and storing]
Measurements are collected and stored in the measurement file. The status flag of the file in question in the ring buffer is Open.
When the file is full the flag is changed to Full.
If the BSS Measurement Data Transfer feature is on, the flag is changed to Waiting (to be compressed).
When the measurement file is compressed, the flag is changed to Compressed.
CMISE sends a request with the name of the measurement file to the edmmanmx process that the measurement file is ready to be transferred.
wtfmanmx receives the request including the measurement file name.
FTAM starts transferring the data from the ring buffer in the NE and stores it in /var/tmp .
wtfmanmx sends a message to the ring buffer via CMISE that the measurement file has been transferred. The flag is changed to Transferred.
wbpmanmx reads the measurement files from /var/tmp and decodes the information and stores it in the NMS/2000 database.
Quality
CH. REQUEST (RACH)
b
Run with "balloons" with all messages and student picks the next message.
Explain Ghost reservations
SETUP (SDCCH)
CONNECT ACK. (FACCH)
MEAS.REPORT
(SACCH)
MEAS.RESULT
HO.COMMAND
(FACCH)
HO.ACCESS
(FACCH)
HO.DETECT
PHYSICAL.INFO
SABM
ESTABLISH.IND
UA
HO.COMPLETE
RR
HO.COMPLETE
HO.PERF
RF.CH.RELEASE
RF.CH.REL.ACK.
---
Drop Call Rate (2%)
Average TCH Usage [%]
Handover Cause Distribution [%]
BSC (BTSid) % % % % % %
ABCDEFNT MSC o: 1381 3.2 0.1 0.0 2.1 -
STTLBSC5(21) BSC i: 2013 1.2 0.0 - - 0.1
BSC o: 2051 10.5 0.0 0.0 1.4 0.2
Cell : 64 0.0 0.0 0.0 0.0 0.0
b
Traffic Measurements
Starting point for traffic calculation in BSC is ‘A BSC’ (see signaling diagram)
Ending point for traffic calculation in BSC is ‘B BSC’
Starting point for traffic calculation in MSC is
‘A MSC’
Ending point for traffic calculation in MSC is ‘B MSC’
Counters
KPI's
DX-cause
Quality
Section 3 pages 6, 7?
Section 8?
SDCCH Blockingsystem= ----------------------------------------------- * 100 [%]
SEIZURE ATTEMPTS (001000)
Handout
Quality
SDCCH Traffic = ----------------------------------------------- [Erl]
AVE AVAILABLE SDCCH SUB CHANNEL (002004)
Avg. Avail. SDCCH = --------------------------------------------------
Counters
KPI's
DX-cause
Handout
Quality
TCH Blockingsystem= -------------------------------------------------------------------------- * 100 [%]
TCH Congestion = TOTAL CHANNEL BUSY TIME (002026) * 0.01 [s]
Counters
KPI's
DX-cause
Handout
Quality
Counters
KPI's
DX-cause
Handout
Quality
Average TCH Usage = -------------------------------------------------------------------------------[%]
---------------------------------------------------------- + --------------------------------------------------
RES AVAIL DENOMINATOR 26 (002006) RES AV DENOM 26 (002041)
AVE AVAIL TCH TIMESLOT (002059)
--------------------------------------------------------
Average TCH Availability = -------------------------------------------------------------------------------[%]
---------------------------------------------------------- + ---------------------------------------------------
RES AVAIL DENOMINATOR 26 (002006) RES AV DENOM 26 (002041)
Counters
KPI's
DX-cause
Handout
Quality
Counters
KPI's
DX-cause
Handout
Quality
Draw on White Board:
/c3030
ghost_ccch_res
5/8 OF GHOSTS (ph.1) AND OTHER FAILURES BEFORE ESTABL. INDICATION
(incl.IMSI detach):
TRUE SDCCH SEIZURES
SEIZURES FOR HO
/TRF-27
HO attempt if there are no
free SDCCH
SSR = 100 * ----------------------------------------------------------------------------------------------------%
(sdcch seizures for new calls) + (netto SDCCH HO) - (succ.DR out + blocked calls)
TNS - TCH Normal Seizure
TCR - TCH Call Request
SST - Mobile Terminated Call
SSO - Mobile Originated Call
---
Handover failure
Drop call: tch_xxx_fail_new updated on B cell
tch_xxx_fail_old updated on A cell
A
B
Quality
sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+ a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+
a.tch_tr_fail+ a.tch_tr_fail_old+a.tch_lapd_fail+ a.tch_bts_fail+
a.tch_user_act+a.tch_bcsu_reset+a.tch_netw_act+a.tch_act_fail_call)
+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch)
Counters from table(s):
a = p_nbsc_traffic
c = p_nbsc_ho
Ref.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.
TCH failures
(normal calls)+(DR calls)+(FACCH call setup calls)+(net TCH-TCH Ho to/from other cells)
Quality
*MSC HO Considered
Cell Level DOR
Handout "Call Signalling Process"
TCH failures
(normal calls)+(DR calls)+(FACCH call setup calls)+(net TCH-TCH Ho to/from other cells)
- Intra-cell Ho’s excluded (IUO) - IUO Large number of Handovers makes Denominator >>>
- Before call re-establishment - Mobile Re-Establishment Timer
Short Form of Counter Names
Quality
sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+ a.tch_abis_fail_old+a.tch_a_if_fail_call+a.tch_a_if_fail_old+
a.tch_tr_fail+ a.tch_tr_fail_old+a.tch_lapd_fail+ a.tch_bts_fail+
a.tch_user_act+a.tch_bcsu_reset+a.tch_netw_act+a.tch_act_fail_call)
100* --------------- % = 100 * --------------------------------- %
= 100 * (1- ------------------------------------------------------------------- )%
Known problems:
1) Blocking is included. Blocking makes this indicator show high values especially in the case of IUO, but it does not necessarily mean that there are some technical problems.
2) Calls that are cleared by MS user during the HO process increment the attempt-counters but can not be compensated in numerator. (XX2)
3) HO that is interrupted due to other procedure (e.g. assignment) increments attempt-counters but can not be compensated in numerator.(XX3)
Quality
=> remove CA from formula
SR blocking, Quality distribution
----
SUCC_HO = successful handovers (BSC, MSC and intra-cell)
MIO = MSC controlled incoming/outgoing handover attempts
BIO = BSC controlled incoming/outgoing handover attempts
CA = intra-cell handover attempts
band 1 (FTCH1)
band 2 (FTCH2)
band 3 (FTCH3)
band 4 (FTCH4)
band 5 (FTCH5)
SDCCH call success ratio
TCH success ratio
Call
Success
Ratio
Quality
Quality
Improvement
b
- Completion of optimization cycle (I.e. report) to summarize KPI's for technical management
- Before optimization cycle had goals but small quality cycle continues (iterative)
- "hand-off" to technical management
Test new technologies and
---
Major frequency change
Design dual band network
Below notes directly from marketing presentation:
With the above solution and service portfolio Nokia's BSS offering should be extremely competitive compared to any other vendor.
GSM 900 (Extended GSM)
EDGE (in BSS10)
Stand-alone Nokia UltraSite WCDMA BTS
Improvement
b
EDGE availability will be in several phases:
SW for BSC in S10, SW for BTS in CX3.0 and HW on stepped manner, all in 2001.
HW: as with standard units, the frequency versions will be introduced sequentially
WCDMA availability in 2002.
- either 12GSM/EDGE transceivers or
- 6 GSM/EDGE and 3 WCDMA carriers
Operates on GSM 900, 1800, 1900 MHz and WCDMA 2 GHz frequencies
For fast and cost-efficient EDGE and WCDMA rollout
GSM/EDGE
WCDMA
Improvement
b
Below notes directly from marketing presentation:
The WCDMA and GSM integration into same cabinet is possible with the Nokia UltraSite GSM Base Station.
WCDMA o/p power is 5W at the antenna connector, with 1+1+1 carrier configuration.
WCDMA units are of WCDMA Release 2.
The mix of frequencies used within one cabinet naturally have to be such that they do not overlap. This applies mostly to cases where 1800 and 1900 bands or 1900 and 2GHz are used simultaneously.
Vertical or horizontal mounting
Several integrated transmission media
Capacity:
MetroSite BTS capacity can be 1, 2, 3 or 4 TRXs in a single cabinet
Small cell size:
Nominal receiver sensitivity -108 dBm
Interference:
Receiver diversity is available when 2 or more TRXs are in same sector.
MetroSite BTS supports RF hopping in 1.0 release. Baseband hopping is supported in later release.
Site acquisition
MetroSite BTS size is 840 x 310 x 215 mm (H x W x D) and max. weight is 40 kgs
Unobtrusive shape and colour (light grey)
Available mounting options for both wall and pole installations. Can be installed vertically or, in indoor installations, horizontally.
Transmission unit is inside the BTS. MetroSite BTS supports both microwave and wireline transmission. Nokia MetroHopper Radio and Nokia FlexiHopper Microwave Radio can be used with MetroSite BTS.
57.bin
Nominal receiver sensitivity -108 dBm
Receiver diversity available when 2 or more TRXs per sector
Frequency hopping
RF Hopping
Baseband Hopping
(available later)
Baseband hopping requires SW update
Receiver diversity:
RX diversity available when 2 or more TRXs per sector
RX diversity connection between TRXs with diversity cables
Diversity principle ->
DIV OUT
DIV IN
main branch
div. branch
This slide shows the different building block for BTS sites.
Cross Polarized Panel antennas
X-pol 800/900 MHz 9/15,5/17 dBi 65°
X-pol 800/900 MHz 17 dBi 65° 6° down tilt
X-pol 1710-1880 MHz 15,5/18 dBi 65° (tilting)
XX-pol 900/1800 MHz 12,5 &13 /15 &
16,5 / 17 & 18 dBi 65° (2 and 4 ports)
Improvement
b
Co-siting
New and existing operators will start implementing 3G networks with high roll-out demands. Co-siting will be an issue
Co-siting presents a potential quality risk for all parties
Interference
Intermodulation
Sharing the load between the cells brings following benefits
Smoother demand curves for traffic
Smaller peak capacity demand per cell
Less blocking in the network
More efficient use of equipment
Cost savings
Improved quality
Therefore the existing hardware will be in more efficient use
A
B
C
D
E
F
G
H
Improvement
b
GPRS and GSM resource sharing
BSS Dimensioning, system load affects grade of service
Control Channel Dimensioning, AGCH possible bottleneck
GPRS
Radio
Network
Planning
Link adaptation ensures highest user data rate
CS1 offers higher user throughput when radio conditions are poor (<6.5dB C/I)
no noise, no hopping and TU50
User throughput heavily affected by C/I
Improvement
b
0
5
10
15
20
25
4
6
8
10
12
14
16
18
20
22
24
26
28
30
Same as the Circuit Switched idle mode cell selection
Cell is selected autonomously by the mobile
MS uses C1 and C2 parameters for cell selection/reselection
Cell reselection can be done during the data connection
Rel 1
Improvement
b
of being paged data
just been transmitting.
standby -> idle : 1hr (max: 186 min, 59 sec)
To transfer data PDP context needs to be activated.
It is possible to send SMS without PDP context, by merely being attached.
Territory border moves Dynamically based on Circuit Switched traffic load
TS
TS
TS
TS
Data Transfer - Temporary Block Flow
A Temporary Block Flow (TBF) is a one-way session for packet data transfer between MS and BSC (PCU). It uses either uplink or downlink but not both (except for associated signaling). It can use one or more timeslots. 2 TBF's (UL & DL) to allow bidirectional communication.
Uplink TBF
Downlink TBF
Uplink
Ready
State
send
RACH
Establish
Immediate
Assignment
Get
PDCH
Requested
TSL
to
Allocated
TBF
Session
Release
phase
Improvement
b
Downlink
Improvement
b
Parameters
Note: Default percentage includes dedicated channels.
PreferBCCHfreqGPRS (BTS-level) is used in association with the existing TRX Priority for CSW parameter.
Traffic (001174-001181)
GPRS Occupancy
Improvement
b
These are the counters which came with S9 within these existing measurements.
Provides cell specific information about the RLC/MAC data blocks
Frame Relay measurement
Provides bearer-specific information about the proper working in the frame relay
Improvement
b
GPRS Session Management Measurement
Data Measurement
Paging Measurement
SMS Measurement
Improvement
b
Release Rate
The Pis under individual KPI s are the factors effecting the corresponding main KPI.
0.00%
2.50%
5.00%
7.50%
10.00%
Week
Tracing Reference : 256
BTS ID : 9
TRX ID : 5
CH Type : TCHF
Subchannel Number : 0
Cell ID : 12061 12062 12083 12082
Cell NCC :
Cell BCC :
Cell BCCH :
------------- ------------------ --------------
Index DTX RxL RxQ DTX RxL RxQ TA RxL RxL RxL RxL
(dBm) (BER) (dBm) (BER) (dBm) (dBm) (dBm) (dBm)
1 NO -101 4.53 NO -82 0.14 2 -105 -87 -94 -100
2 NO -95 0.14 NO -82 0.14 2 -105 -87 -94 -100
3 NO -96 0.14 NO -79 0.14 2 -105 -89 -92 -98
4 NO -96 0.14 NO -81 0.14 2 -104 -90 -91 -100
5 NO -95 0.14 NO -84 0.14 2 -104 -96 -93 -96
6 NO -96 0.14 NO -82 0.14 2 -104 -90 -99 -96
7 NO -97 0.14 NO -82 0.14 2 -104 -88 -100 -96
8 NO -97 0.14 NO -86 0.14 3 -108 -90 -101 -100
9 NO -99 0.14 NO -81 0.14 3 -108 -88 -98 -97
10 NO -97 0.14 NO -82 0.14 3 -104 -86 -91 -97
11 NO -98 0.14 NO -83 0.14 3 -105 -87 -93 -98
12 NO -98 0.14 NO -81 0.14 2 -105 -87 -102 -98
13 NO -95 0.14 NO -78 0.14 2 -107 -87 -101 -94
14 NO -95 0.14 NO -79 0.14 2 -107 -85 -93 -94
15 NO -95 0.14 NO -80 0.14 2 -108 -86 -96 -95
16 NO -94 0.14 NO -80 0.14 2 -106 -86 -96 -99
17 NO -96 0.14 NO -80 0.14 2 -105 -86 -97 -96
18 NO -95 0.14 NO -80 0.14 2 -104 -86 -102 -97
19 NO -95 0.14 NO -79 0.14 2 -107 -86 -99 -96
measurement type
Interference (Rx Level)

document on gsm optimisation

Documents