TEMS Investigation & Mapinfo

Babak Kardel Mehrdad Sedaghat

April 2008
1

TEMS Investigation

Tems Investigation Course

4/14/2008

Contents
Introduction TEMS Investigations Main Windows Signalling Messages KPI Generation in TEMS Scanning Mode Map Registration in Mapinfo and TEMS Logfile import & Export in TEMS and Mapinfo (KPI and Statistic) Border in Mapinfo and TEMS & google TEMS Error
3

Introduction-Drive Test
Drive test measurements are initiated from a number of questions such as: Is the system working properly? Have the latest optimization efforts had any results (validation)? How good is the coverage in this area? Why do we get so many complaints in this area? How can we easily add capacity in this region (cell planning)?

Tems Investigation Course

4/14/2008

Introduction-Test Routes
The routes must pass through as many cells as possible in the test area The routes must cover all the major areas where e.g. outdoor, in car or indoor is predicted The routes can be planned so that handover is performed between as many cells as possible The routes must pass through important areas within the service area and the route can be planned so that important roads are included
5 Tems Investigation Course 4/14/2008

TEMS Investigations Main Windows

Map Chart

Tems Investigation Course

4/14/2008

Serving + Neighbours GSM

Radio Parameters

Current Channel

10

Hopping Channels

11

Layer 3 messages

12

Tems Investigation Course

4/14/2008

AMR Codec Usage

13

Line Chart

14

Tems Investigation Course

4/14/2008

Frequency Scanning

15

Tems Investigation Course

4/14/2008

Interference Scanning

16

Tems Investigation Course

4/14/2008

Adjacent Scanning

17

Tems Investigation Course

4/14/2008

MS Remote Control

18

Tems Investigation Course

4/14/2008

Reports
For each route measured, the followed figures may be presented (in a report regarding general performance). The following bar charts can be generated: SQI RxQual RxLev TxPow TA and many more

19

Tems Investigation Course

4/14/2008

Distribution of RXLEV

20

Tems Investigation Course

4/14/2008

RxQual sub

21

Tems Investigation Course

4/14/2008

TEMS Speech Quality Index, SQI

22

Tems Investigation Course

4/14/2008

Distribution of SQI

23

Tems Investigation Course

4/14/2008

RADIO NETWORK QUALITY

Non-Hopping System

24

Tems Investigation Course

4/14/2008

RADIO NETWORK QUALITY

Hopping System

25

Tems Investigation Course

4/14/2008

System Information Messages

OBJECTIVES: Upon completion of this part the student will be able to: Describe the content of different types of system information messages. List the channels used to transmit the different messages. Describe when system information messages are sent.

26

Tems Investigation Course

4/14/2008

Signalling Messages

27

System Information Overview

28

29

30

System Information Type 1

System Information Type 1 Time: 07:29:05.74 Latitude: not valid Longitude: not valid Frame number: 97112 Read from (ARFCN): 116 L2 Pseudo Length: 21 Cell channel description Cell Allocation Format notation: Bit map 0 ARFCN: 102 116 122 130 RACH control parameters Max retransmissions: 2 Tx-integer: 32 Cell bar access: Not barred Call reestablishment (RE): Not allowed Emergency call (EC) allowed: All MS Not barred class(es) (ACC): 0 1 2 3 4 5 6 7 8 9 11 12 13 14 15 SI 1 Rest Octets contains spare bits

31

Tems Investigation Course

4/14/2008

32

System Information Type 2

System Information Type 2 Time: 07:29:05.98 Latitude: not valid Longitude: not valid Frame number: 97163 Read from (ARFCN): 116 L2 Pseudo Length: 22 Neighbor cells description BA-IND: 1 EXT-IND: 0 BCCH Allocation Format notation: Bit map 0 ARFCN: 87 88 89 90 92 93 104 109 111 114 NCC permitted: 2 6 7 RACH control parameters Max retransmissions: 2 Tx-integer: 32 Cell bar access: Not barred Call reestablishment (RE): Not allowed Emergency call (EC) allowed: All MS Not barred class(es) (ACC): 0 1 2 3 4 5 6 7 8 9 11 12 13 14 15

33

Tems Investigation Course

4/14/2008

System Information Type 2 ter

System Information Type 2ter Time: 07:29:06.92 Latitude: not valid Longitude: not valid Frame number: 97367 Read from (ARFCN): 116 L2 Pseudo Length: 0 Neighbor cells description 2 Multiband reporting: 1 BA-IND: 1 BCCH Allocation Format notation: Variable bit map ARFCN: 735 736 737 738 740 743 744 746 747 748 749 751 753 754 757 768 SI 2ter Rest Octets contains spare bits

34

Tems Investigation Course

4/14/2008

35

System Information Type 3

System Information Type 3 Time: 07:29:07.15 Latitude: not valid Longitude: not valid Frame number: 97418 Read from ARFCN Channel number : (GSM 900) 116 L2 pseudo length : 18 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 27 Cell identity (CI) : 00000 Location Area Identification MCC : 000 MNC : 00 LAC : 00 Control channel description Attach/detach allowed (ATT) : (1) YES BS-AG-BLKS-RES : 1 CCCH-CONF : (0) 1 basic physical channel used for CCCH, not combined with SDCCHs BS-PA-MFRMS : 9 multiframes period T3212 timeout value : 10

Cell options (BCCH) Power control indicator (PWRC) : (0) Not set DTX indicator : (2) The MSs shall not use uplink discontinuous transmission RADIO-LINK-TIMEOUT : 24 Cell selection parameters CELL-RESELECT-HYSTERESIS : 6 dB Rxlev hysteresis for LA-reselection MS-TXPWR-MAX-CCH : 5 ADDITIONAL RESELECT PARAM IND (ACS) : (0) Spare HALF RATE SUPPORT (NECI) : (0) New estab- causes not supported RXLEV-ACCESS-MIN : 0 RACH control parameters Max retransmission : (1) Maximum 2 retransmissions Tx-integer : (14) 32 slots used Cell bar access : (0) Not barred Call reestablishment : (1) Not allowed Access control Emergency Call allowed : (0) All MSs Barred classes : Rest octets Selection Parameters cbq : 0 Cell reselection offset : (0) 0 dB Temporary offset : (0) 0 dB Penalty time : (0) 20 s System Information 2ter indicator - Available Early classmark sending control - Explicity accepted BCCH scheduling is not sent in SI9 GPRS indicator RA color : 2 SI13 position : (0) SI13 message is sent on BCCH Norm

36

Tems Investigation Course

4/14/2008

37

System Information Type 4

System Information Type 4 Time: 07:29:07.39 Latitude: not valid Longitude: not valid Frame number: 97469 Read from ARFCN Channel number : (GSM 900) 116 L2 pseudo length : 12 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 28 Location Area Identification MCC : 000 MNC : 00 LAC : 00 Cell selection parameters CELL-RESELECT-HYSTERESIS : 6 dB MS-TXPWR-MAX-CCH : 5 ADDITIONAL RESELECT PARAM IND (ACS) : (0) The SI 4 rest octets, if present, shall be used to derive the value of PI and possibly C2 parameters and/or other parameters HALF RATE SUPPORT (NECI) : (0) New establishment causes are not supported RXLEV-ACCESS-MIN : 0 RACH control parameters Max retransmission : (1) Maximum 2 retransmissions Tx-integer : (14) 32 slots used Cell bar access : (0) Not barred Call reestablishment : (1) Not allowed Access control Emergency Call allowed : (0) All MSs Barred classes : Rest octets Selection Parameters cbq : 0 Cell reselection offset : (0) 0 dB Temporary offset : (0) 0 dB Penalty time : (0) 20 s GPRS indicator RA color : 2 SI13 position : (0) SI13 message is sent on BCCH Norm

38

Tems Investigation Course

4/14/2008

39

System Information Type 5

System Information Type 5 Time: 15:31:52.88 Latitude: not valid Longitude: not valid Frame number: 1521472 Neighbor cells description BA-IND: 0 EXT-IND: 0 BCCH Allocation Format notation: Bit map 0 ARFCN: 87 88 89 90 92 93 104 109 111 114

40

Tems Investigation Course

4/14/2008

System Information Type 5 ter

System Information Type 5ter Time: 15:31:53.35 Latitude: not valid Longitude: not valid Frame number: 1521574 Neighbor cells description 2 Multiband reporting: 1 BA-IND: 0 BCCH Allocation Format notation: Variable bit map ARFCN: 735 736 737 738 740 743 744 746 747 748 749 751 753 754 757 768

41

Tems Investigation Course

4/14/2008

System Information Type 6

System Information Type 6 Time: 15:31:53.82 Latitude: not valid Longitude: not valid Frame number: 1521676 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 30 Cell identity (CI) : 00000 Location Area Identification MCC : 000 MNC : 00 LAC : 00 Cell options (SACCH) Power control indicator (PWRC) : (0) Not set DTX indicator : The MS shall not use uplink DTX on a TCH/F. The MS shall not use uplink DTX on a TCH/H. RADIO-LINK-TIMEOUT : 24 NCC permitted NCC permitted values : 2 6 7 Rest octets

42

Tems Investigation Course

4/14/2008

RLINKT (RADIO_LINK_TIMEOUT)

43

Tems Investigation Course

4/14/2008

ACCMIN (RXLEV_ACCESS_MIN)

44

Tems Investigation Course

4/14/2008

CCHPWR (MS_TXPWR_MAX_CCH) GSM 900

45

Tems Investigation Course

4/14/2008

CCHPWR (MS_TXPWR_MAX_CCH) GSM 1800

46

Tems Investigation Course

4/14/2008

47

System Information Type 13 (without PBCCH)

System Information Type 13 Time: 07:29:12.33 Latitude: not valid Longitude: not valid Frame number: 98540 Read from ARFCN Channel number : (GSM 900) 116 L2 pseudo length : 0 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 0 Rest octets BCCH CHANGE MARK : 7 SI CHANGE FIELD : (0) Update of unspecified SI message PBCCH not present in cell Routing area code (RAC) : 1 SPGC CCCH SUP : (0) SPLIT PG CYCLE is not supported PRIORITY ACCESS THR : (6) Packet access is allowed for priority level 1 to 4 NETWORK CONTROL ORDER : (0) NC0: MS controlled cell re-selection 48 Tems Investigation Course
GPRS cell options NMO : (1) Network mode of operation II T3168 : (0) 500 milliseconds T3192 : (7) 200 milliseconds DRX TIMER MAX : (7) 64 s ACCESS BURST TYPE : (0) 8 bit access burst shall be used CONTROL ACK TYPE : (1) Default format is RLC/MAC control block BS CV MAX : 6 PAN DEC : 1 PAN INC : 2 PAN MAX : Maximum value allowed for counter N3102 is 20 Extension bits Length : 3 ExtensionBits : [0 ] : 0 [1 ] : 0 [2 ] : 0 [3 ] : 0 GPRS power control parameters Alpha : (1) 0.1 T AVG W : 12 T AVG T : 10 PC MEAS CHAN : (0) Downlink measurements for power control shall be made on BCCH N AVG I : 2

4/14/2008

System Information Type 13 (with PBCCH)

System Information Type 13 Time: 15:05:47.34 Latitude: not valid Longitude: not valid Frame number: 2315204 Read from ARFCN Channel number : (GSM 900) 41 L2 pseudo length : 0 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 0 Rest octets BCCH CHANGE MARK : 2 SI CHANGE FIELD : (0) Update of unspecified SI message or SI messages PBCCH present in cell PSI1 REPEAT PERIOD : PSI1 repeat period = 6 multiframe(s) Pb : -0 dB TSC : 1 TN : 7 BCCH carrier 49 Tems Investigation Course 4/14/2008

Handover Procedure

50

Layer 3 Information - Normal

51

Layer 3 Information - Handover

52

MS1 Measurement Report Time: 18:33:45.21 Frame number: 1500234

Measurement Report

53

Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 21 BA USED : 0 DTX USED : (0) DTX is not used RxLev Full Serving Cell : 39 3G BA USED : 0 MEAS VALID : (0) The measurement results are valid RxLev Sub Serving Cell : 38 RxQual Full Serving Cell : 4 RxQual Sub Serving Cell : 5 Neighbour cell measurements RxLev BSIC BCCH-INDEX : [0 ] : 41 4-6 10 [1 ] : 39 1-7 15 [2 ] : 39 4-5 03 [3 ] : 37 1-1 11 [4 ] : 36 5-3 05 [5 ] : 36 1-4 23

Handover Command
MS1 Handover Command Time: 18:33:45.75 Frame number: 1500350 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 43 Cell description BSIC : 4-6 BCCH ARFCN : 614 Description of the first channel, after time Channel type : (1) TCH/F + ACCHs Timeslot number (TN) : 2 Training sequence code (TSC) : 6 Hopping RF channel : (0) NO Absolute radio frequency channel number (ARFCN) : 614 Handover reference Handover reference value : 170 Power command and access type Access type control : (0) Sending of Handover Access is mandatory Fast Measurement Reporting and Power Control : (0) FPC not in use Power level : 0 Synchronization indication Normal cell indication : (0) Out of range timing advance is ignored Report observed time difference : (0) 'Mobile Time Difference' IE shall not be included in the Handover Complete message Synchronization indication : (0) Nonsynchronized Mode of the first channel (channel set 1) Mode : (65) Speech full rate or half rate version 3

54

HO Access

MS1 Handover Access Time: 18:33:45.77 Frame number: 152915 Handover Reference : 170

Message dump (Hex): aa

55

Physical Information

MS1 Physical Information Time: 18:33:45.86 Frame number: 152934 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 45 Timing Advance Timing advance value : 2

56

HO Complete

MS1 Handover Complete Time: 18:33:45.86 Frame number: 152934 Skip indicator : 0 Protocol discriminator : (6) Radio resources management messages Message type : 44 Value : (0) Normal event

MS1 Time: 18:33:45.86 Handover

57

Case-1: HO Failure

58

Case-1: Layer 3 Analysis

59

Case-1: Finding Problem

60

HO Failure Solution Removing overshoot from cell N680A Changing BCCH frequency of N680A or N215C. Removing not important adjacency.

61

Case-2: Feeder Swap

62

Case-2: Feeder Swap

63

Case-2 Site Visit : Check Cables Feeder Swap in 900 & 1800 Bands CSSR & CDR & SDCCH Drop & HSR Improvement KPI & Report-196 also can show swap
64

Call Setup Procedure

65

Events Call Setup

66

Layer 3 Messages for Call Attempt Event

67

Layer 3 Messages for Call Attempt Event

68

Layer 3 Messages for Call Setup & Call Established Event

69

Call Setup Procedure in TEMS

When Ms put a request to BTS for channel Request, BTS assign First One SDCCH in DL See in Slide One After assigned SDCCH MS go in Dedicated mode See in Slide Two After some process BTS give TCH Assignment command in DL and MS give its completion command in UL See in Slide Two Still MS is in Dedicated mode.. See in Slide Two During this time BTS is doing some process and MS is waiting for Connect command form BTS in DL When MS will got Connect command from BTS in DL, it count as a Call Set up Event .. See in Slide Three Now MS will give Connect Acknowledge to BTS in UL, and it count as a Call Established Event .. See in Slide Three But in some cases Due to Interference or LAPD or some Protocol error after receiving Assignment command form BTS, MS can receive Connect command This cause some difference in Call Attempt and Call Established Event and this is directly affect to DT Call Setup Success Rate (CSSR)
70

You can see some of example of Call Established failure in Next slide

Some Layer 3 message that cause for Call Establishment Failure

71

KPI Generation in TEMS

72

Drive Test procedure

1. Short Call Duration: 50 sec 10 sec wait CSSR-HSR-HFR-DCR (TEMS Report)
CallSet-upSuccessRate = Number of Established Calls *100 Number of Call Attempts

HandoverFailureRate =

Number of FailedHandovers *100 Number of HandoverAttempts

Number of Dropped Calls *100 Number of Established Calls

Dropped Call Rate =

2. Long Call

Rx-Quality (MapInfo Report)

DL Rx Qual (0-4) DL RxQual (5-5) DL RxQual (6-7)

73

Cammand Sequence
Example: Short Call

74

Drive Test KPI Targets

KPI based on DT
DCR% CSSR% HSR% HOF%

Nokia Target

MCI Target

2% 94% 97% 3%

1% 96% 98% 2%

RxQual%
0-5 5-6 6-7

90% 6% 4%

95% 3% 2%

75

Drive Test Statistics

CSSR = 81.35% Drop Call Rate = 3.12% HO Success Rate = 98.2%

76

Scanning Mode

77

Frequency Scanning Mode

78

Frequency Scanning Mode

79

Frequency Scanning Mode Investigation of Network Coverage Interference detection Best Frequency Selection for New Sites Neighbour Modification with Idle Mode

80

Interference Mode

81

Interference Mode- Bar Chart

82

Interference Mode- Analyse Finding Interference Source with Strongest BCC of interfered Frequency. Searching in database of cellular network for finding the interfered cell.

83

MapInfo

84

MapInfo-Neighbour Check

85

Shows 900 and 1800 neighbours easily.

MapInfo-Frequency Plan Check

86

Drive Test Analyse- RxLevel Distribution

87

Drive Test Analyse- RxQual Distribution

88

Drive Test Analyse- Coverage

89

Drive Test Analyse- Blocked Call Distribution

90

Site N1047 & N3047 was down on 16th & 17th during DT

TEMS- Some Notes in Logfiles- Case 1

91

TEMS - Some Notes in Logfiles- Case 2

92

TEMS Error

93

TEMS Problem
Two kind of Errors with Tems that you have to face during use it:
1. Tems Product Error itself 2. Human Error

Do not RUN log files with lower versions. (TEMS 6 . TEMS 5.1.1)
Lower versions can not show some messages and show wrong messages sometimes.

94

TEMS Messages
When Ms put a request to BTS for channel Request, BTS assign First One SDCCH in DL After assigned SDCCH MS go in Dedicated mode After some process BTS give TCH Assignment command in DL and MS give its completion command in UL Still MS is in Dedicated mode.. During this time BTS is doing some process and MS is waiting for Connect command form BTS in DL When MS will got Connect command from BTS in DL, it count as a Call Set up Event .. Now MS will give Connect Acknowledge to BTS in UL, and it count as a Call Established Event .. But in some cases Due to Interference or LAPD or some Protocol error after receiving Assignment command form BTS, MS can not receive Connect command This cause some difference in Call Attempt and Call Established Event and this is directly affect to Our Call Setup Success Rate (CSSR)

95

TEMS Product Error Call Established with out Call Attempt

Where is the Call Attempt & Call Setup

96

Before MS1 take Call Established Event it was in idle mode. But in actual there must be call Attempt event by MS1 but here Tems have some error that it couldnt record this event in this log file.

TEMS Product Error Error in Call End Event

Handover just after Call End

97

There is Error in Call End Event. After the Call End for MS2, it took Handover.Actually This Call End Event is some error one event. If you see in GSM window call is successfully handover form N216A to N2990A

TEMS Product Error Error in Call End Event

Handover complete successfully

98

MS2 is taking Handover from cell N216A to cell N2990A Event & Layer 3 Messages you can see in below picture

TEMS Product Error Error in Call End Event

99

TEMS Product Error

Dropped Call in between successful Handovers

100

Here MS1 is in dedicated mode, it is Attempting Handover successfully Then it gives Dropped Call Event, and after call is dropped it still give Handover Event.

TEMS Product Error

Dropped Call in between successful Handovers

101

Here MS1 is in dedicated mode, it is Attempting Handover successfully Then it gives Dropped Call Event, and after call is dropped it still give Handover Event. Check here time of both window in below picture First call in on 4th time slot, after Intracell Handover call moved on 0th time slot

TEMS Product Error

Dropped Call in between successful Handovers

MS1 has completed the Intracell Handover

102

MS1 stay in dedicated mode after this Dropped Call, that means Tems count a error Dropped Call Event

TEMS Product Error Dropped call when MS is in idle mode

103

See the Event Dropped Call for MS1, it happen when MS1 is in Idle mode

TEMS Product Error Blocked Call Event during Call

Round 14th :0506_07.log

104

TEMS recorded Blocked Call event After Blocked Call event it established the call with out any Call Attempt Event. This kind of event makes Call Established and Call Attempt Equal with some blocked Call Event also.

Human Error
Call Attempt missing during recording start & end

Log file start when Call Attempt is already done

105

Human Error
Dropped Call due to Recording Paused & Resumed

106

MS1 gives Dropped Call event after it comes in idle mode. Also there is no Layer 3 Message for these events

Thanks

107