Date post: | 05-Dec-2015 |
Category: |
Documents |
Upload: | sarah-love |
View: | 219 times |
Download: | 1 times |
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
2
Base concept
RPMO—Real-time Performance Monitoring.– an OSS feature – Fetch the data, process and export real-time information about the
network or cell behaviour.
Advantage– The R-PMO collects all the cell related measurements data at
regular intervals for defined duration and pass this information to OSS for presentation.
– The R-PMO provides the radio network optimizer with presentation of quality and traffic related monitors in real time.
– The R-PMO can be used for fast reaction to suspected problems and thus help in troubleshooting.
– The R-PMO offered several types of reports.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
3
R-PMO Architecture
R-PMO is one of function within OSS.
TCP/IP
OSSOSSR-PMOR-PMO
X.25
IOG/APG 40
BSC
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
4
Pre-Requirements
OSS RC1.1 (Radio & Core) and above versions. R-PMO Feature installed in OSS. Activation of RTED (Real Time Event Data) Feature in BSC to
enable recordings. BSC with STOC (Signaling Terminal for Open Communication)
Feature. This functionality enable communication from BSC to RPMO. This would additionally required a physical cable from BSC to OSS.
An IP address to communicate OSS and BSC. To Support RTED, One Dedicated RPG3 (AXE 810) or RPG2E
(BYB501) is required RTED in not supported in Mixed (BYB202-BYB501) combination
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
5
Get Started with R-PMO
Step 1– Go to OSS Network
Explorer on Common Desk Environment of OSS
Step 2– Click on Performance
Step 3– Go to GSM RNO tools
Step 4– Select R-PMO
This window will appear
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
6
System Defined Reports for Network Analysis
Circuit Switched Reports – TCH Traffic Report– Quality Report– TCH Drop Report– TCH/SDCCH Handover
Report– SDCCH Traffic Report– Multi Band Cell Report
Packet Switched Reports – GPRS/EGPRS Overview
Report– Data Related– GPRS/EGPRS Overview
Report– Performance Related
– GPRS/EGPRS TBF Release Report
– GPRS/EGPRS Multislot Utilization Report
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
7
Example---TCH drops Report
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
8
GUI interface in R-PMO---Main window
The Main window in R-PMO shows the activated system defined Report
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
9
GUI interface in R-PMO---Table window
In R-PMO Table window– The report is updated
every minute – N/A means data “Not
Available” – The user can select
between 1 minute up to 60 minutes(1,15,30 or 60Minutes
– Data is only shown for one hour and only saved for one hour
– The columns and data can be sorted in the way that the user wants
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
10
GUI interface in R-PMO---Graph window
The graph window views one graph for each monitor (window) and the selected cells appears in every graph with the same color.
The graph can be paused. The user can Drag and Drop
cells and monitors into the graph.
The graph has the same resolution as the table window had when the graph was opened.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
11
Set handler in R-PMO
Cell sets are created using the Set Handler available from the R-PMO main window.
Cells can then be added to and removed from cell sets by using the Set Handler.
When a cell set is deleted all reports that belong to the set will automatically be deactivated.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
12
Report Customization in R-PMO
Create User Defined Report – click on “Report” icon
from the menu bar and select subtitle “New user report definition”.
Combining the Reports in One Report
– User can select different parameters from two reports and combine into one report
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
13
Out Put for Post-Processing ---REDE (Raw Event Data Export)
This function is used for storing any events and measurements that are provided by the R-PMO , in a file. The format of the file can be tab separated or XML
The format of the file can be tab separated or XML
Post processing tool for R-PMO out put is ”Tems Visualization”
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
14
Out Put for Post-Processing ---R-PMO Event Log
This is simple XML file, generated by R-PMO after collecting the events and measurements for the a particular cell set for analysis very similar to Layer-3 Message analysis
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
15
Further Developments
RTED (Real Time Event Data) Enabling improved functionality in R-PMO:
– Add RXQUAL for CHGR level– Improved monitoring of GPRS/EDGE separately– Improved event monitoring capacity– Support for monitoring new features:
Dual Transfer Mode Mega BSC – 2000 TRXs Extended Dynamic Allocation
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
16
Limitation Observed
Below are some dimensioning or application issues related to R-PMO.
– There is no provision of scheduling of reports for user-defined time; it gives the results only as and when R-PMO starts.
– The R-PMO Configured, BSC processor load, on an average can be increased by 5-7%.
– The load on the OSS server is going to be higher side.– The number of users on the application server in the OSS
should be restricted, as the application server loading will increase by apprx.10%.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
17
Conclusion and reference
R-PMO is very useful tool to analyze nearly online performance of the network. This is also very useful to see affects of any changes made in the network in very short time.
The following document for your reference and help you analyze the network performance.
R-PMO User description R12
R-PMO monitor description
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
18
Typical case
Here is a typical case which using R-PMO to analyze the network performance.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
19
Typical case
From the R-PMO data, we can see N_14012 have 70% drops which cause by Low SS. Then we can check the monitor description and find out which Low SS drop it belongs to.
For other 30% Bad Quality drop, we also can analyze which kind of BQ it belongs to according to the drop cause value.
Top right corner for field-mark, customer or partner logotypes. See Best practice for example.
Slide title 40 pt
Slide subtitle 24 pt
Text 24 pt
Bullets level 2-520 pt
20
Monitor name Parameters Value TCH Drop (%) - TCH Drops (#) -
Drop Cause (R11)
100-Low SS BL TCH FR 101-Low SS BL TCH HR 102-Low SS BL, Overlaid Subcell TCH FR 103-Low SS BL, Overlaid Subcell TCH HR 104-Low SS DL TCH FR 105-Low SS DL TCH HR 106-Low SS DL, Overlaid Subcell TCH FR 107-Low SS DL, Overlaid Subcell TCH HR 108-Low SS UL TCH FR 109-Low SS UL TCH HR 110-Low SS UL, Overlaid Subcell TCH FR 111-Low SS UL, Overlaid Subcell TCH HR
Low SS (%)
Urgency Condition (R12)
3-Low SS Both Link 4-Low SS Down Link 5-Low SS Up Link
Drop Cause (R11)
114-Bad Q BL TCH FR 115-Bad Q BL TCH HR 116-Bad Q BL, Overlaid Subcell TCH FR 117-Bad Q BL, Overlaid Subcell TCH HR 118-Bad Q DL TCH FR 119-Bad Q DL TCH HR 120-Bad Q DL, Overlaid Subcell TCH FR 121-Bad Q DL, Overlaid Subcell TCH HR 122-Bad Q UL TCH FR 123-Bad Q UL TCH HR 124-Bad Q UL, Overlaid Subcell TCH FR 125-Bad Q UL, Overlaid Subcell TCH HR
Bad Q (%)
Urgency Condition (R12)
6-Bad RxQual Both Link 7-Bad RxQual Down Link 8-Bad RxQual Up Link
Drop Cause (R11)
87-Excessive TA TCH FR 88-Excessive TA TCH HR
Excessive TA (%)
Urgency Condition (R12)
1-Excessive TA