TEMS TOOL PRESENTATION.ppt
- 2. WHY DT Non–working sites/sectors or TRXs In–active Radio network features like frequency hopping Disabled GPRS Overshooting sites – coverage overlaps Coverage holes C/I, C/A analysis High Interference Spots Drop Calls Capacity Problems Other Interference Sources Missing Neighbors One–way neighbors Ping–Pong Handovers Not happening handovers Accessibility and Retain ability of the Network Equipment Performance Faulty Installations
- 3. AFTER DT Post processing of data Plotting RX Level and Quality Information for overall picture of the driven area Initial Discussions on drive test with Local engineers Reporting urgent problems for immediate action Analyzing Network feature performance after new implementations Transferring comments on parameter implementations after new changes
- 4. TEMS TOOL Tems 5.1 Tems 6.1
- 5. Tems 5.1 1 or 2 tems sets Tems kit with an internal antenna GPS 1 dongal key
- 6. Tems 6.1 2 tems set 1 tems kit with 2 external antennas GPS 1 dongal key 1 hub
- 7. How to connect? 1. Connect tems kit, dongal key and GPS leads to the system (computer) 2. In the Tems’ “Configuration” menu, select “Equipment Configuration” 3. Click on the “Add” icon. 4. Enter port number and device attached on that specific port.
- 10. Open map window
- 14. RADIO PARAMETER
- 16. GSM LINE CHART
- 17. MODES OF TEMS ONE TEMS IN IDEAL MODE FOR CHECKING NETWORK RX LEVEL ONE TEMS IN DEDICATED MODE CHECKING NETWORK QUALITY FREQUENCY SCANNING
- 19. DROP CALL Call can get drop because of assignment failure(layer 3 msg) having its R L time out/interference/quality/level/overshootin g issues. Call can get drop because of NO service(layer 3 msg) having its R L time out/interference/quality/level/overshootin g issues.
- 20. BLOCKED CALL Blocked call can happen with NO ASSIGNMENT FAILURE(layer-3 Msg) as the result of data link failure during signalling. No alerting or Connect(layer-3 Msg) . NO ASSIGNMENT FAILURE(layer-3 Msg) as a result of NO SDCCH allocation after 4 re-transmission of immediate assignment.
- 21. BLOCKED CALL DATA LINK FAILURE (layer-3 msg) because layer-2 protocols were not recognized in layer-3.
- 22. BLOCKED CALL
- 25. C/I APPEARENCE
- 26. LOW SIGNAL LEVEL
- 28. SUDDEN APPEARANCE & DISAPPEARENCE OF NEIGHBOURS
- 30. Stable Behavior
- 31. RX Levels too Closed to Each Other
- 32. RX Levels of Many Cells are Almost the Same
- 33. Log File Recording on Resume
- 34. Drop Call due to Bad Coverage
- 35. Bad Quality due to Signal Strength – FER is Bad
- 36. Bad Quality due to Signal Strength – FER is OK
- 37. Problem 1
- 38. Problem 2
- 39. Problem 1
- 40. Problem 6
Editor's Notes
- #38: Interference is present in the area because all the immediate neighbors are Sector-1s having same set of hopping frequencies with not much difference of signal level( at least 9dB would be required ). 52011 is overshooting in the area because 52051 should be the main server in that area.
- #39: There is no problem at the moment but bad quality will be faced when traffic load increased in the area or during BH. Because again same sectors of different Cell-Ids are immediate neighbors with same set of hopping frequencies.
- #40: Interference is present in the area because all the immediate neighbors are Sector-1s having same set of hopping frequencies with not much difference of signal level( at least 9dB would be required ). 52011 is overshooting in the area because 52051 should be the main server in that area.
- #41: Illogical serving of Cell-ID 34311 because from “Serving + Neighbor” window, we can see that either 34151 or 36183 should be the main server in the area. There is a suspected uplink interference in the area because “MS Tx Power” is at the maximum level with satisfactory RXLEV.