6TEMS Investigation & Mapinfo(Day6)

7/30/2019 6TEMS Investigation & Mapinfo(Day6)

1/107

1

Babak Kardel

Mehrdad Sedaghat

April 2008

TEMS Investigation & Mapinfo


2/107

2

TEMS Investigation

4/14/2008

2 Tems Investigation Course


3/107

3

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 andMapinfo (KPI and Statistic)

Border in Mapinfo and TEMS & google

TEMS Error


4/107


5/107

5

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

Introduction-Test Routes

4/14/20085 Tems Investigation Course


6/107

6

TEMS Investigations Main

Windows


7/107

7

Map Chart



8/107

8

Serving + Neighbours GSM


9/107

9

Radio Parameters


10/107

10

Current Channel


11/107

11

Hopping Channels


12/107

12

Layer 3 messages



13/107

13

AMR Codec Usage


14/107

14

Line Chart



15/107

15

Frequency Scanning



16/107

16

Interference Scanning



17/107

17

Adjacent Scanning



18/107

18

MS Remote Control



19/107

19

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

TAand many more



20/107

20

Distribution of RXLEV



21/107

21

RxQual sub



22/107

22

TEMS Speech Quality Index, SQI



23/107

23

Distribution of SQI



24/107

24

RADIO NETWORK QUALITYNon-Hopping System



25/107

25

RADIO NETWORK QUALITYHopping System



26/107

26

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 messagesare sent.

System Information Messages



27/107

27

Signalling Messages


28/107

28

System Information Overview


29/107

29


30/107

30


31/107


32/107

32


33/107

33

System Information

Type 2

System Information Type 2

Time: 07:29:05.98

Latitude: not validLongitude: not valid

Frame number: 97163

Read from (ARFCN): 116

L2 Pseudo Length: 22

Neighbor cells descriptionBA-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 barredCall 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



34/107

34

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



35/107

35


36/107

36

System Information

Type 3


Time: 07:29:07.15

Latitude: 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 : 27Cell identity (CI) : 00000

Location Area Identification

MCC : 000

MNC : 00

LAC : 00

Control channel description

Attach/detach allowed (ATT) : (1) YESBS-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 transmissionRADIO-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 parametersMax 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 acceptedBCCH scheduling is not sent in SI9

GPRS indicator

RA color : 2

SI13 position : (0) SI13 message is sent on BCCH Norm



37/107

37


38/107

38

System Information

Type 4

HALF RATE SUPPORT (NECI) : (0)

New establishment causes are not supported

RXLEV-ACCESS-MIN : 0

RACH control parametersMax 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 : 2SI13 position : (0) SI13 message is sent on BCCH Norm


Time: 07:29:07.39

Latitude: not valid


Frame number: 97469

Read from ARFCN



Skip indicator : 0

Protocol discriminator : (6)

Radio resources management messagesMessage type : 28


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



39/107

39


40/107

40

System Information

Type 5System Information Type 5

Time: 15:31:52.88

Latitude: not valid


Frame number: 1521472

Neighbor cells description

BA-IND: 0

EXT-IND: 0BCCH Allocation

Format notation: Bit map 0

ARFCN:

87 88 89 90 92 93 104 109 111 114



41/107

41

System Information

Type 5 terSystem Information Type 5ter

Time: 15:31:53.35

Latitude: not valid



Neighbor cells description 2

Multiband reporting: 1

BA-IND: 0BCCH Allocation

Format notation: Variable bit map

ARFCN:

735 736 737 738 740 743 744 746 747 748749 751 753 754 757 768



42/107

42

System Information

Type 6


Time: 15:31:53.82Latitude: not valid



Skip indicator : 0

Protocol discriminator : (6) Radio resources management

messages

Message type : 30

Cell identity (CI) : 00000


MCC : 000MNC : 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

4/14/200842Tems Investigation Course


43/107

43

RLINKT (RADIO_LINK_TIMEOUT)



44/107

44

ACCMIN (RXLEV_ACCESS_MIN)



45/107

45

CCHPWR (MS_TXPWR_MAX_CCH) GSM 900



46/107

46

CCHPWR (MS_TXPWR_MAX_CCH) GSM 1800



47/107

47

System Information Type 13 (without PBCCH)


48/107

48

System Information Type 13 (without PBCCH)

System Information Type 13Time: 07:29:12.33

Latitude: not valid


Frame number: 98540

Read from ARFCN

Channel number : (GSM 900) 116L2 pseudo length : 0

Skip indicator : 0

Protocol discriminator : (6) Radio resources

management messages

Message type : 0

Rest octetsBCCH 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

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 isRLC/MAC control block

BS CV MAX : 6

PAN DEC : 1

PAN INC : 2

PAN MAX : Maximum value allowed for

counter N3102 is 20

Extension bitsLength : 3

ExtensionBits :

[0 ] : 0

[1 ] : 0

[2 ] : 0

[3 ] : 0

GPRS power control parametersAlpha : (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



49/107

49

System Information Type 13 (with PBCCH)System Information Type 13

Time: 15:05:47.34

Latitude: not valid



Read from ARFCN



Skip indicator : 0

Protocol discriminator : (6) Radio resources management messagesMessage 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



50/107

50

Handover Procedure

L 3 I f ti N l


51/107

51

Layer 3 Information - Normal


52/107

52

Layer 3 Information - Handover

MS1

M t R t


53/107

53

Measurement

Report

Measurement Report

Time: 18:33:45.21Frame number: 1500234

Skip indicator : 0

Protocol discriminator : (6) Radio resourcesmanagement messages

Message type : 21BA 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

H d C d


54/107

54

Handover Command

Handover reference

Handover reference value : 170

Power command and access type

Access type control : (0) Sending of Handover

Access is mandatoryFast 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 ignoredReport observed time difference : (0) 'Mobile

Time Difference' IE shall not be included in theHandover Complete message

Synchronization indication : (0) Non-synchronized

Mode of the first channel (channel set 1)

Mode : (65) Speech full rate or half rate version 3

MS1

Handover Command

Time: 18:33:45.75


Skip indicator : 0

Protocol discriminator : (6) Radio resources managementmessages

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) : 6Hopping RF channel : (0) NO

Absolute radio frequency channel number (ARFCN) :614


55/107

55

HO AccessMS1

Handover Access

Time: 18:33:45.77


Handover Reference : 170

Message dump (Hex): aa


56/107

56

Physical

Information

MS1

Physical Information

Time: 18:33:45.86Frame number: 152934

Skip indicator : 0

Protocol discriminator : (6)Radio resources managementmessages

Message type : 45

Timing Advance

Timing advance value : 2


57/107

57

HO CompleteMS1Handover Complete

Time: 18:33:45.86


Skip indicator : 0

Protocol discriminator : (6) Radioresources management messages

Message type : 44

Value : (0) Normal event

MS1

Time: 18:33:45.86

Handover

Case-1: HO Failure


58/107

58

Case 1: HO Failure

Case-1: Layer 3 Analysis


59/107

59

Case-1: Layer 3 Analysis

Case 1: Finding Problem


60/107

60

Case-1: Finding Problem

HO F il S l ti


61/107

61

HO Failure Solution

Removing overshoot from cell

N680AChanging BCCH frequency of

N680A or N215C.Removing not important adjacency.

Case 2: Feeder Swap


62/107

62

Case-2: Feeder Swap

Case 2: Feeder Swap


63/107

63

Case-2: Feeder Swap


64/107

64

Case-2 Site Visit : Check Cables

Feeder Swap in 900 & 1800

Bands

CSSR & CDR & SDCCH Drop &

HSR ImprovementKPI & Report-196 also can show

swap


65/107

65

Call Setup Procedure


66/107

66

Events Call Setup

Layer 3 Messages for Call Attempt Event


67/107

67

Layer 3 Messages for Call Attempt Event


68/107

68

Layer 3 Messages for Call Setup & Call Established Event


69/107

69

Call Setup Procedure in TEMS


70/107

70

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 upEvent .. 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)

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

Some Layer 3 message that cause for Call Establishment Failure


71/107

71


72/107

72

KPI Generation in TEMS


73/107

73

Drive Test procedure

1. Short Call Duration: 50 sec 10 sec wait

CSSR-HSR-HFR-DCR (TEMS Report)

2. Long Call - Rx-Quality (MapInfo Report) DL Rx Qual (0-4) DL RxQual (5-5) DL RxQual (6-7)

Number of Established CallsCallSet-upSuccessRate *100

Number of Call Attempts=

Number of FailedHandoversHandoverFailureRate *100

Number of HandoverAttempts=

Number of Dropped CallsDropped Call Rate *100

Number of Established Calls=

Cammand Sequence


74/107

74

Example: Short Call


75/107

75

Drive Test KPI Targets

2%4%6-7

3%6%5-6

95%90%0-5

RxQual%

2%3%HOF%

98%97%HSR%

96%94%CSSR%

1%2%DCR%

MCI TargetNokia TargetKPI based

on DT


76/107

76

Drive Test Statistics

CSSR = 81.35%Drop Call Rate = 3.12%

HO Success Rate = 98.2%


77/107

77

Scanning Mode

Frequency Scanning Mode


78/107

78



79/107

79



80/107

80

Investigation of Network Coverage

Interference detectionBest Frequency Selection for New

Sites

Neighbour Modification with Idle

Mode

Interference Mode


81/107

81

Interference Mode- Bar Chart


82/107

82

Interference Mode- Analyse


83/107

83

Finding Interference Source with

Strongest BCC of interfered Frequency.Searching in database of cellular

network for finding the interfered cell.


84/107

84

MapInfo


85/107

85

MapInfo-Neighbour Check

Shows 900 and 1800 neighbours easily.


86/107

86

MapInfo-Frequency Plan Check

D i T t A l R L l Di t ib ti


87/107

87

Drive Test Analyse- RxLevel Distribution

D i T t A l R Q l Di t ib ti


88/107

88

Drive Test Analyse- RxQual Distribution

D i T t A l C


89/107

89

Drive Test Analyse- Coverage

D i T t A l Bl k d C ll Di t ib ti


90/107

90

Drive Test Analyse- Blocked Call Distribution

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

TEMS- Some Notes in Logfiles- Case 1


91/107

91

TEMS - Some Notes in Logfiles- Case 2


92/107

92


93/107

93

TEMS Error

TEMS Problem


94/107

94

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.

TEMS Messages


95/107

95

When Ms put a request to BTS for channel Request, BTS assign First OneSDCCH in DL

After assigned SDCCH MS go in Dedicated mode

After some process BTS give TCH Assignment command in DL and MSgive its completion command in UL Still MS is in Dedicated mode..

During this time BTS is doing some process and MS is waiting for Connectcommand form BTS in DL

When MS will got Connect command from BTS in DL, it count as a CallSet up Event ..

Now MS will give Connect Acknowledge to BTS in UL, and it count as aCall Established Event ..

But in some cases Due to Interference or LAPD or some Protocol error afterreceiving Assignment command form BTS, MS can not receive Connectcommand

This cause some difference in Call Attempt and Call Established Event andthis is directly affect to OurCall Setup Success Rate (CSSR)

TEMS Product Error

Call Established with out Call Attempt


96/107

96

Call Established with out Call AttemptWhere is the Call

Attempt & Call Setup

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

TEMS Product Error

Error in Call End Event


97/107

97


Handover just

after Call End

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

TEMS Product Error



98/107

98


Handover

complete

successfully

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

TEMS Product Error



99/107

99


TEMS Product ErrorDropped Call in between successful

Handovers


100/107

100

Handovers

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


Handovers


101/107

101

Handovers

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 pictureFirst call in on 4th time slot, after Intracell Handover call moved on 0th time slot


Handovers


102/107

102

MS1 has

completedthe Intracell

Handover

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/107

103

Dropped call when MS is in idle mode

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

TEMS Product Error

Blocked Call Event during Call


104/107

104

g

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

Round 14th :0506_07.log

Human Error

Call Attempt missing during recording start & end


105/107

105

Log file start when Call

Attempt is already

done

Human Error

Dropped Call due to Recording Paused & Resumed


106/107

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


107/107

107

Thanks

6TEMS Investigation & Mapinfo(Day6)

Documents

Transcript of 6TEMS Investigation & Mapinfo(Day6)