109506957 TEMS Investigation 14 1 Technical Reference

5/23/2018 109506957 TEMS Investigation 14 1 Technical Reference

http:///reader/full/109506957-tems-investigation-14-1-technical-reference-561d5b8c

TEMS INVESTIGATION 14.1

TECHNICAL REFERENCE



This manual is provided by Ascom Network Testing AB without any kind ofwarranty. Improvements and changes in this description due to typographicalerrors or inaccuracies in current information, or improvements to programsand/or equipment may be made by Ascom Network Testing AB at any timewithout notice. These changes will, however, be incorporated into neweditions of this manual.

No part of this publication may be reproduced, transmitted, stored in aretrieval system, nor translated into any human or computer language, in anyform or by any means, electronic, mechanical, magnetic, optical, chemical,manual or otherwise, without the prior written permission of the copyrightedowner, Ascom Network Testing AB.

TEMS is a trademark of Ascom.

All other trademarks are the property of their respective holders.

Ascom 2012. All rights reserved.

Document number: NT12-7001 ver 1.0



Contents

NT12-7001 ver 1.0 i

Contents

1. Introduction 1

2. Supported Cellular System Versions 2

2.1. 3GPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2. CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3. TD-SCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.4. WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Format of CEL File (UMTS) 4

3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.2. File Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3. Column Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.4. Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.4.1. General Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.4.2. GSM-specific Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.4.3. WCDMA-specific Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.5. Comment Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.6. Neighbor Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4. Format of XML Cell File 11

4.1. Scope of XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.2. Relation to CEL Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.3. Relation to TEMS Investigation CDMA CSV Format. . . . . . . . . . . . 114.4. Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.5. General Remarks on Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12



TEMS Investigation 14.1 Technical Reference

ii

4.6. TEMS-specific Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.6.1. String_OperatingBand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.6.1.1. GSM Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.6.1.2. WCDMA Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.6.1.3. LTE Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.6.1.4. TD-SCDMA Bands . . . . . . . . . . . . . . . . . . . . . . . . . . 174.6.1.5. CDMA Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.6.1.6. WiMAX Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.6.1.7. Wi-Fi Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.7. Structure of Cell File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.7.1. Diagram Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.7.2. Overall File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.7.3. GSM Cell Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.7.4. WCDMA Cell Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.7.5. LTE Cell Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.7.6. TD-SCDMA Cell Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.7.7. CDMA Cell Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.7.8. EV-DO Cell Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.7.9. WiMAX Cell Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.7.10. Wi-Fi Access Point Data . . . . . . . . . . . . . . . . . . . . . . . . . . 314.7.11. Site Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.7.12. Container Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.7.12.1. ANTENNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.7.12.2. BSIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.7.12.3. CDMA_CHANNEL_INFO . . . . . . . . . . . . . . . . . . . . 324.7.12.4. CGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.12.5. CHANNEL_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.12.6. INFORMATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.12.7. LTE_CGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.7.12.8. NEIGHBOR_LIST . . . . . . . . . . . . . . . . . . . . . . . . . . 344.7.12.9. POSITION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.7.12.10. REPEATER_LIST . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.7.12.11. TEMS_INTERNAL . . . . . . . . . . . . . . . . . . . . . . . . 344.7.12.12. WIMAX_CHANNEL_INFO . . . . . . . . . . . . . . . . . . 34

4.7.13. Atomic Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.7.14. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.8. Example of Complete XML File: UMTS/Wi-Fi. . . . . . . . . . . . . . . . . 394.9. Example of Complete XML File: CDMA/EV-DO . . . . . . . . . . . . . . . 434.10. Note on Processing in TEMS Investigation. . . . . . . . . . . . . . . . . . 44



Contents

NT12-7001 ver 1.0 iii

5. Cell Identification 45

5.1. Cell Identification in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.1. Serving Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.1.2. Neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.2. Cell Identification in WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.3. Cell Identification in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.4. Cell Identification in CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.5. Cell Identification in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6. Format of Cell Whitelists UnderlyingUser-defined Events 48

6.1. Format Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496.3. Conversion to Event Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7. Data Session Error Messages 51

7.1. General Data Service Error Messages . . . . . . . . . . . . . . . . . . . . . . 517.2. RAS Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.3. NDIS Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.4. FTP Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.5. E-mail Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.6. Video Streaming Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 567.7. MMS Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7.7.1. MMS Send Failure Causes . . . . . . . . . . . . . . . . . . . . . . . . . 577.8. WAP Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8. Text Export Format for Logfiles 59

8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.2. File Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.3. Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

9. Notes on Third-party Logfile Export Formats 62

9.1. Export to MapInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

9.2. Export to ArcView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62




iv

9.3. Export to Marconi Planet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639.4. Export to Ethereal (Wireshark) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639.5. Export to MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10. Logfile Report 64

10.1. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.2. Logfile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.3. Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

10.3.1. Worst Cell Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.3.2. Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.3.3. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

10.3.4. Scan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.4. Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.4.1. Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.4.2. Scan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

10.5. File and Directory Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6810.5.1. Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6810.5.2. Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11. KPI Definitions 69

11.1. Overview of KPIs for Circuit-switched Services . . . . . . . . . . . . . . 6911.1.1. Diagram of Circuit-switched KPIs . . . . . . . . . . . . . . . . . . . 6911.1.2. Service Non-Accessibility (%) . . . . . . . . . . . . . . . . . . . . . . 7111.1.3. Setup Time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7111.1.4. Speech Quality on Sample Basis (dBQ) . . . . . . . . . . . . . . 7111.1.5. Speech Quality, Call Average (MOS-PESQ) . . . . . . . . . . . 7111.1.6. Call Cut-off Ratio (%). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11.2. Overview of KPIs for Packet-switched Services . . . . . . . . . . . . . . 7211.2.1. Diagrams of Packet-switched KPIs . . . . . . . . . . . . . . . . . . 7211.2.2. Service Independent KPIs . . . . . . . . . . . . . . . . . . . . . . . . . 79

11.2.2.1. Network Unavailability (%) . . . . . . . . . . . . . . . . . . . 7911.2.2.2. Attach Failure Ratio (%) . . . . . . . . . . . . . . . . . . . . . 7911.2.2.3. Attach Setup Time (s) . . . . . . . . . . . . . . . . . . . . . . . 7911.2.2.4. PDP Context Activation Failure Ratio (%). . . . . . . . 7911.2.2.5. PDP Context Activation Time (s). . . . . . . . . . . . . . . 7911.2.2.6. PDP Context Cut-off Ratio (%) . . . . . . . . . . . . . . . . 79

11.2.3. General Data Service KPIs . . . . . . . . . . . . . . . . . . . . . . . . 8011.2.3.1. Service Non-Accessibility (%) . . . . . . . . . . . . . . . . . 80

11.2.3.2. Setup Time (s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80



Contents

NT12-7001 ver 1.0 v

11.2.3.3. IP Service Access Failure Ratio (%) . . . . . . . . . . . . 8011.2.3.4. IP Service Setup Time (s) . . . . . . . . . . . . . . . . . . . . 8011.2.3.5. Mean Data Rate (kbit/s) . . . . . . . . . . . . . . . . . . . . . 8011.2.3.6. Data Transfer Cut-off Ratio (%). . . . . . . . . . . . . . . . 8111.2.3.7. Data Transfer Time (s) . . . . . . . . . . . . . . . . . . . . . . 81

11.2.4. Ping KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8111.2.4.1. Ping Roundtrip Time (ms) . . . . . . . . . . . . . . . . . . . . 81

11.2.5. WAP KPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8111.2.5.1. WAP Activation Failure Ratio (%) . . . . . . . . . . . . . . 8111.2.5.2. WAP Activation Time (ms) . . . . . . . . . . . . . . . . . . . 8111.2.5.3. WAP Page Request Failure Ratio (%) . . . . . . . . . . 8111.2.5.4. WAP Page Request Time (s) . . . . . . . . . . . . . . . . . 8111.2.5.5. WAP Portal Access Time (s) . . . . . . . . . . . . . . . . . . 82

11.2.5.6. WAP Portal Non-accessibility (%) . . . . . . . . . . . . . . 8211.2.5.7. WAP Site Access Time (s) . . . . . . . . . . . . . . . . . . . 8211.2.5.8. WAP Site Non-accessibility (%) . . . . . . . . . . . . . . . 82

11.2.6. MMS KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8211.2.6.1. MMS Send Failure Ratio (MO) (%) . . . . . . . . . . . . . 8211.2.6.2. MMS Send Time (MO) (s) . . . . . . . . . . . . . . . . . . . . 8311.2.6.3. MMS Notification Failure Ratio (%) . . . . . . . . . . . . . 8311.2.6.4. MMS Notification Time (s) . . . . . . . . . . . . . . . . . . . . 8311.2.6.5. MMS Retrieval Failure Ratio (MT) (%) . . . . . . . . . . 8311.2.6.6. MMS Retrieval Time (MT) (s) . . . . . . . . . . . . . . . . . 8311.2.6.7. MMS End-to-End Failure Ratio (%). . . . . . . . . . . . . 8311.2.6.8. MMS End-to-End Delivery Time (MO/MT) (s) . . . . . 83

11.2.7. Streaming KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.2.7.1. Service Non-Accessibility (%) . . . . . . . . . . . . . . . . . 8411.2.7.2. Service Access Time (s) . . . . . . . . . . . . . . . . . . . . . 8411.2.7.3. Reproduction Start Failure Ratio (%) . . . . . . . . . . . 8411.2.7.4. Reproduction Start Delay (s) . . . . . . . . . . . . . . . . . . 8411.2.7.5. Reproduction Cut-off Ratio (%) . . . . . . . . . . . . . . . . 8411.2.7.6. Streaming Session Cut-off Ratio (%) . . . . . . . . . . . 85

11.2.7.7. Streaming Quality (MOS-VSQI) . . . . . . . . . . . . . . . 8511.2.8. VoIP KPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

11.2.8.1. MTSI Registration Failure Ratio (%) . . . . . . . . . . . . 8511.2.8.2. MTSI Registration Time (s) . . . . . . . . . . . . . . . . . . . 8511.2.8.3. MTSI Session Setup Failure Ratio (%) . . . . . . . . . . 8511.2.8.4. MTSI Session Setup Time (s) . . . . . . . . . . . . . . . . . 8511.2.8.5. MTSI Session Completion Failure Ratio (%). . . . . . 85

11.3. Interdependence of KPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86




vi

Index 87



Chapter 1. Introduction

NT12-7001 ver 1.0 1

1. Introduction

This book covers various technical aspects of TEMS Investigation 14.1:

File formats

File export formats

Report formats

Descriptions of various algorithms used in the application.




2

2. Supported Cellular System

Versions

For details on frequency bands and references to specifications, consultsection 4.6.1.

2.1. 3GPP

TEMS Investigation 14.1 is 3GPP Release 8 compliant. Within 3GPP, thefollowing bands are supported:

GSM/GPRS/EGPRS

GSM 850 MHz

GSM E-900 MHz

GSM 1800 MHz

GSM 1900 MHz

WCDMA/HSPA

Bands IVI

Band VIII

Band IX

Band XI

LTE (with Rohde & Schwarz TSMW, any LTE band can be scanned)

(FDD) Bands IXIV (114), XVIIXXI (1721)

(TDD) Bands XXXIIIXL (3340).

2.2. CDMA

CDMA standards are supported by TEMS Investigation 14.1 as follows:

cdmaOne (IS-95)



Chapter 2. Supported Cellular System Versions

NT12-7001 ver 1.0 3

cdma2000 (IS-2000)/EV-DO (IS-856) Rel. 0/Rev. A/Rev. B

on the following bands:

450 MHz

800 MHz

1900 MHz

2100/1700 MHz AWS

2.3. TD-SCDMA

The TD-SCDMA 20102025 MHz band is supported.

2.4. WiMAX

WiMAX (802.16e) scanning can be done on the 2.3, 2.5 and 3.5 GHz bands.

The following RF Profiles are supported:

Prof1.B 2.3-5

Prof1.B 2.3-10

Prof2.A 2.305 Prof2.B 2.305

Prof2.C 2.305

Prof3.A 2.496-5

Prof3.A 2.496-10

Prof4.A 3.3

Prof4.B 3.3

Prof4.C 3.3

Prof5.A 3.4

Prof5.B 3.4

Prof5.C 3.4




4

3. Format of CEL File (UMTS)

In the current version of the CEL file, columns from the older GSM- andWCDMA-specific versions of the CEL format may be freely combined, withpartly different columns being filled in for GSM and WCDMA cells.

3.1. GeneralThe file is in ASCII format with tab-delimited data. There is no restriction onthe number of cells in the file, but very large cell files will slow the applicationdown noticeably. The default file extension is .cel.

3.2. File Header

The cell file header, which takes up the first line of the file, consists of arevision number and an identification string:

TEMS_-_Cell_names

where is a revision number.

3.3. Column Headers

The second line in the cell file is the column header line. It consists of tab-separated strings, each of which identifies a category of data. The set ofcolumn headers used appears from the table in section 3.4below; columnscan be arranged in any order as long as their headers are valid.

3.4. Data

The remainder of the cell file contains data. Each data line represents one cellname entry and is stored in ASCII as:

data1data2data3...dataN



Chapter 3. Format of CEL File (UMTS)

NT12-7001 ver 1.0 5

The table below describes the format of the data in each column:

3.4.1. General Data

Column Header Data Content and Format

Cell Cell name. Text string.

NETWORK_CELLID

Free text field describing the cell. Text string.

Lat,Lon Latitude and longitude. Text string. The input format

must be one of the following, whereH is one of {N, n, S, s, W, w, E, e, +, -}, +representingN orE,

d= degree digit, m= minute digit, s= second digit,

*= degree sign, one of {*, , o, O, ^, }:

H dddmm.mmmm (decimal minutes). Here,minutes must be written with two and degrees withat least two digits. Thus, when entering N 4 2.86,

the degrees and minutes must be written0402. H ddd* mm.mmmm (decimal minutes). This

format, unlike the previous one, does not requirepadding zeroes in theddd* mm segment.

H ddd* mm ss (degrees, minutes and seconds;the sign for seconds must be a double quote,

ASCII 0x22 it cannot be replaced by two singlequotes).

H ddd* mm ss.ssss (degrees, minutes and

decimal seconds).

H ddd.dddd* (decimal degrees).

In all formats, the number of decimals is unlimited.

The presentation format isH dddmm.mmmm, i.e.decimal minutes rounded off to four decimal places.This gives a resolution of about 20 cm, so that theerror is negligible compared to other sources of error.




6

3.4.2. GSM-specific Data

MCC Mobile Country Code. Integer, base 10

representation.

MNC Mobile Network Code. Integer, base 10representation.

LAC Location Area Code. Integer, base 10 or (withprefix 0x) hexadecimal representation.

RA Routing Area Code. Integer, base 10 representation.

CI The Cell Identity reported in System Information. ForWCDMA, this is the same as UC-Id = RNC-Id + C-Id in 3GPP 25.401, section 6.1.5. Integer, base 10 or(with prefix 0x) hexadecimal representation.

CI_N_n Cell Identity of neighborn of this cell.Same format asforCI.

ANT_DIRECTION

Antenna direction in degrees clockwise from north.Decimal number. (Alternative name:

ANT_ORIENTATION)

ANT_BEAM_WIDTH

Antenna beam width in degrees. Integer.

ANT_TYPE Antenna type. Text string.

ANT_HEIGHT Antenna height in meters. Decimal number.

ANT_TILT Antenna tilt in degrees. Decimal number.

CELL_TYPE Cell type (e.g. Macro, Micro, Pico). Text string.


ARFCN ARFCN. Mandatory for GSM cells. Integer.

BSIC BSIC. Integer in the range 00 ... 77 (octal).





NT12-7001 ver 1.0 7

3.4.3. WCDMA-specific Data

TCH_ARFCN_n ARFCN of TCH no. n used by this cell. Integer.

LAC_N_n LAC for neighborn of this cell. Same format as forLAC.


UARFCN UARFCN. Mandatory for WCDMA cells. Integer.

SC Scrambling code. Integer.

RNC-ID Radio Network Controller ID. Equal to the 12-bitRNC-Id in 3GPP 25.401, section 6.1.5. Integer,base 10 or (with prefix 0x) hexadecimalrepresentation.

RNC-ID_N_n Radio Network Controller ID of neighborn of this cell.Same format as forRNC-ID.

C-ID Cell Identity. Equal to the 16-bit C-Id in 3GPP25.401, section 6.1.5. Integer, base 10 or (withprefix 0x) hexadecimal representation.

The 28-bit Cell Identity (UC-Id in 3GPP) is aconcatenation of RNC-ID (see above) and C-ID.

C-ID_N_n Cell Identity of neighborn of this cell. Same format asforC-ID.

URA UTRAN Registration Area. Integer.

TIME_OFFSET Time offset of P-SCH synchronization signal in chips.Integer.

CPICH_POWER Power (in dBm) on P-CPICH control channel. Decimalnumber.

MAX_TX_POWER

Maximum transmit power (in dBm) for the cell.Decimal number.





8

3.5. Comment Lines

A comment line starts with an exclamation mark !.

Comment lines are ignored when the cell file is imported.

3.6. Neighbor Identification

In GSM, the following parameters are used to identify neighbors:CI,CI_N_n,LAC,LAC_N_n.

In WCDMA, the following parameters are used to identify neighbors: either{CI, CI_N_n} or{C-ID, C-ID_N_n, RNC-ID, RNC-ID_N_n}.

3.7. ExampleBelow is a sample cell file. The data columns are split into sections here forobvious reasons of presentation; the actual file has one single row of datacolumns below the header.

Cells no. 13 are WCDMA cells, while cells no. 46 are GSM cells.

NODE_B Node B identity assigned by the operator. Text string.

NODE_B_STATUS

Node B status (e.g. Operational, Phase 3). Textstring.





NT12-7001 ver 1.0 9

55 TEMS_-_Cell_names

Cell ARFCN BSIC UARFCN SC Lat Lon1 10714 32 N 47.719283 W 27.2938492 10714 16 N 47.719283 W 27.2938493 10714 0 N 47.719283 W 27.2938494 617 21 N 46.571874 W 26.9797715 592 20 N 46.571874 W 27.2938496 599 23 N 46.571874 W 27.293849

MCC MNC LAC CI LAC_N_1 CI_N_1147 2 201147 2 201147 2 201147 93 76 32500 76 32501147 93 76 32501 76 32500147 93 76 32502 76 32500

RNC-ID C-ID RNC-ID_N_1 C-ID_N_1687 3756 687 3757687 3757 687 3756687 3758 687 3756

ANT_DIRECTION ANT_BEAM_WIDTH ANT_TYPE ANT_HEIGHT156.2 90 Kath1 15.1228.4 90 Kath1 13.7310.9 90 Kath1 14.273.1 45 Kath2 8.8147.8 45 Kath2 9.1266.8 90 Kath2 9.5




10

ANT_TILT CELL_TYPE NODE_B NODE_B_STATUS0.0 Macro RBS Teleby Operational

11.2 Macro RBS Teleby Operational7.8 Macro RBS Teleby Not Operational4.4 Macro14.2 Macro9.9 Macro

RA URA TIME_OFFSET CPICH_POWER MAX_TX_POWER1 4 9442 33 45.51 4 22156 33 45.51 4 34870 33 45.5111



Chapter 4. Format of XML Cell File

NT12-7001 ver 1.0 11

4. Format of XML Cell File

The XML cell file format is used for representing (primarily) cell and siteinformation and for interchanging such information between products in theTEMS portfolio.

4.1. Scope of XML FormatThe XML format incorporates cell and site data for GSM, WCDMA, LTE,TD-SCDMA, CDMA (1x as well as EV-DO), and WiMAX. It also includesWi-Fi access point data, which is of interest for GAN-capable user terminals.

4.2. Relation to CEL Format

No formal mapping exists from the older *.cel format (chapter3) to the XMLformat, but the correspondences are obvious throughout. All columnheadings in the *.cel file have their counterparts in XML file elements; inaddition, the XML file contains further data. Just note that in the *.cel file,neighbors are indicated by their CIs, whereas in the XML file, cell names areused to identify neighbors.

4.3. Relation to TEMS Investigation CDMA CSVFormat

The CSV cell file format used in TEMS Investigation CDMA can be convertedto the XML format using TEMS Discovery. Please consult the documentationfor that product.

Please note that the CSV format lacks certain items of information that arepresent in the XML format. For example, the band class is lacking in CSV butis mandatory in XML (see sections 4.7.12.3, 4.7.13). This information mustbe entered manually in the XML files.




12

4.4. Schemas

The XML-format cell file is based on two XML schemas:

The schemaTEMSDataTypes.xsd defines TEMS-specific XML datatypes, derived from the fundamental data types set down in the XMLspecification. See section 4.6.

The schemaTEMSCell.xsd defines XML attributes and elements thatembody cell and site data, relying on the data types inTEMSDataTypes.xsd. See section 4.7.

The schemas are found in the directoryXMLSchema beneath the TEMSInvestigation installation directory. The syntax laid down in the schemasshould always be followed when composing XML cell files.

4.5. General Remarks on Format

The file format should generally follow the recommendation for XML 1.0. Seethe World Wide Web Consortium recommendation at www.w3.org/TR/REC-xml.

Files should be encoded in Unicode UTF-8 (RFC2279). They therefore needto begin with:

When composing XML files it is a good idea to use an XML-capable editor orother tool with XML support. To ensure that language-specific characters arehandled correctly, any tool used needs to support the UTF-8 encoding. UTF-8allows a set of more than 28= 256 characters to be mapped into 8-bitsymbols, by using two-byte sequences for certain characters. For example,Swedish needs to be encoded as_ in the XML file. Tools with UTF-8support normally handle this automatically.

The file should have extension .xml.

Free text comments must be formatted like this:

4.6. TEMS-specific Data Types

To facilitate handling of data, a number of TEMS-specific data types are

defined. They are collected in the schemaTEMSDataTypes.xsd. The
http://www.w3.org/TR/REC-xmlhttp://www.w3.org/TR/REC-xmlhttp://www.w3.org/TR/REC-xmlhttp://www.w3.org/TR/REC-xml




NT12-7001 ver 1.0 13

definition of custom data types enables range checks and validation of celldata. The data types are used in defining the elements and attributes of theXML cell file, as described in section 4.7.

All TEMS-specific data types are derived from basic (generic) XML schemadata types with additional constraints on value ranges or enumeration. Itshould be noted that these data types do not compare directly to theircounterparts in programming languages. For example, it does not followautomatically that the Long data types found below should always berepresented by a long data type in a programming language.

Full information on the basic set of XML schema data types, includingdefinitions of int, long, float, double, and string, is found at www.w3.org/TR/xmlschema-2/.

Value ranges below are given in the form of inclusive minimum and maximumvalues, that is, the endpoints of the ranges are valid values.

The TEMS-specific data types are as follows:

Data Type Range/Description

Double90_90 90.0 ... 90.0

Double180_180 180.0 ... 180.0

Double5000 0.0 ... 5000.0

Float90 0.0 ... 90.0

Float90_90 90.0 ... 90.0

Float100 1.0 ... 100.0

Float180_180 180.0 ... 180.0

Float360 0.0 ... 360.0

Float_LteBandwidth {1.4, 3, 5, 10, 15, 20}

Int2To3 2, 3

Long2 0, ..., 2

Long7, Long9, etc. (analogous to Long2)

LongPositive 0, ..., 9,223,372,036,854,775,807

String128 String with max 128 characters
http://www.w3.org/TR/xmlschema-2/http://www.w3.org/TR/xmlschema-2/http://www.w3.org/TR/xmlschema-2/http://www.w3.org/TR/xmlschema-2/




14

4.6.1. String_OperatingBand

A string of type String_OperatingBand can have the following values:

4.6.1.1. GSM Bands

For full details see 3GPP 45.005.

String128_Collapse String with max 128 characters, collapsed white

spaces1

String_GeodeticDatum String indicating geodetic datum; one of WGS84,Bessel 1841, Krasovsky, Clarke 1880

String_OperatingBand String; for values see section 4.6.1

String_SystemType String equal to one of the following: GSM,WCDMA, CDMA, EV-DO, WIMAX, WIFI

1. Any leading and trailing spaces are removed when the file is read. Also,

any sequences of spaces inside the string are replaced by single spaces.More about white space handling is found at www.w3.org/TR/xmlschema-2/#rf-whiteSpace.

Band Description

GSM Unspecified GSM band. Can be used when thefrequency band is not known or not defined.

GSM 450, GSM 480,GSM 850, GSM 900,

E-GSM 900,R-GSM 900,GSM 1800,GSM 1900

E-GSM = Extended GSM

R-GSM = Railway GSM

The rest is self-explanatory.

Data Type Range/Description
http://www.w3.org/TR/xmlschema-2/#rf-whiteSpacehttp://www.w3.org/TR/xmlschema-2/#rf-whiteSpacehttp://www.w3.org/TR/xmlschema-2/#rf-whiteSpacehttp://www.w3.org/TR/xmlschema-2/#rf-whiteSpace




NT12-7001 ver 1.0 15

4.6.1.2. WCDMA Bands

For full details see 3GPP 25.101, chapter 5.

4.6.1.3. LTE Bands

For full details see 3GPP 36.101, tables 5.5-1 E-UTRA Operating Bandsand 5.6.1-1 E-UTRA Channel Bandwidth.

Band Description

W-CDMA Unspecified WCDMA band. Can be used when thefrequency band is not known or not defined.

W-CDMA 850 Band V, AM/China

W-CDMA 850 JP Band VI, JP

W-CDMA 900 Band VIII, EU (GSM)

W-CDMA 1800 Band III, EU/JP/APAC

W-CDMA 1800 JP Band IX, JP

W-CDMA 1900 Band II, AM

W-CDMA 2100 Band I, EU/JP/APAC

W-CDMA 2100 AM Band IV, AM

W-CDMA 2500 Band VII, Global

Band Description

EUTRA Generic Unspecified E-UTRA band. Can be used when the

frequency band is not known or not defined.

FDD bands

EUTRA 1 Band I, UMTS IMT 2100 MHz

EUTRA 2 Band II, PCS 1900 MHz

EUTRA 3 Band III, DCS 1800 MHz

EUTRA 4 Band IV, AWS 1700/2100 MHz




16

EUTRA 5 Band V, Cellular 850 MHz, UMTS 850 MHz

EUTRA 6 Band VI, UMTS 800 MHz

EUTRA 7 Band VII, IMT-E 2600 MHz

EUTRA 8 Band VIII, GSM, UMTS 900 MHz, E-GSM 900 MHz

EUTRA 9 Band IX, UMTS 1700 MHz

EUTRA 10 Band X, UMTS IMT-2000, 1700/2100 MHz

EUTRA 11 Band XI, PDC 1500 MHz

EUTRA 12 Band XII, Lower SMH Blocks A/B/C, 700 MHz

EUTRA 13 Band XIII, Upper SMH Block C, 700 MHz

EUTRA 14 Band XIV, Upper SMH Block D, 700 MHz

EUTRA 17 Band XVII, 700 MHz

EUTRA 18 Band XVIII, 800 MHz

EUTRA 19 Band XIX, 800 MHz

EUTRA 20 Band XX, EU Digital Dividend 800 MHz

EUTRA 21 Band XXI, 1400 MHz

EUTRA 22 Band XXII, 3400/3500 MHz

EUTRA 23 Band XXIII, 2000/2100 MHz

EUTRA 24 Band XXIV, 1600/1500 MHz

EUTRA 25 Band XXV, 1800/1900 MHz

TDD bands

EUTRA 33 Band XXXIII, 1900 to 1920 MHz

EUTRA 34 Band XXXIV, 2010 to 2025 MHz

EUTRA 35 Band XXXV, 1850 to 1910 MHz

EUTRA 36 Band XXXVI, 1930 to 1990 MHz

Band Description




NT12-7001 ver 1.0 17

4.6.1.4. TD-SCDMA Bands

TD-SCDMA bands are not represented in the cell file. (The UARFCNuniquely identifies the band.)

4.6.1.5. CDMA Bands

The CDMA band definitions are from 3GPP2 C.S0057-B, version 1.0.

EUTRA 37 Band XXXVII, 1910 to 1930 MHz

EUTRA 38 Band XXXVIII, 2570 to 2620 MHz

EUTRA 39 Band XXXIX, 1880 to 1920 MHz

EUTRA 40 Band XL, IMT-2000, 2300 to 2400 MHz

EUTRA 41 Band XLI, 2496 to 2690 MHz

EUTRA 42 Band XLII, 3400 to 3600 MHz

EUTRA 43 Band XLIII, 3600 to 3800 MHz

Band Description

CDMA Unspecified CDMA band. Can be used when thefrequency band is not known or not defined.

CDMA 800 Band 0, 800 MHz cellular

CDMA 1900 Band 1, 1.8 to 2.0 GHz PCS

CDMA TACS Band 2, 872 to 960 MHz TACS

CDMA JTACS Band 3, 832 to 925 MHz JTACS

CDMA PCS KR Band 4, 1.75 to 1.87 GHz Korean PCS

CDMA 450 Band 5, 450 MHz NMT

CDMA 2GHz Band 6, 2 GHz IMT-2000

CDMA 700 Band 7, 700 MHz


Band Description




18

4.6.1.6. WiMAX Bands

The WiMAX bands are as defined in the document WiMAX Forum MobileSystem Profile Release 1.0 Approved Specification, Revision 1.7.0.


CDMA 800 2nd Band 10, Secondary 800 MHz

CDMA 400 PAMR EU Band 11, 400 MHz European PAMR

CDMA 800 PAMR Band 12, 800 MHz PAMR

CDMA 2.5GHz IMT2000 Band 13, 2.5 GHz IMT-2000 Extension band

CDMA 1900 PCS US Band 14, US PCS 1.9 GHz

CDMA AWS Band 15, AWS (US)

CDMA 2.5GHz US Band 16, US 2.5 GHz

CDMA 2.5GHz US FW LO Band 17, US 2.5 GHz Forward Link Only

Band

WIMAX (Unspecified WiMAX band. Can be used whenthe frequency band is not known or not defined.)

WIMAX 2300-1.A (8.75 MHz)

WIMAX 2300-1.B (5 MHz)

WIMAX 2300-1.B (10 MHz)

WIMAX 2300-2.A1 (3.5 MHz)

WIMAX 2300-2.A2 (3.5 MHz)

WIMAX 2300-2.B1 (5 MHz)

WIMAX 2300-2.B2 (5 MHz)

WIMAX 2300-2.C1 (10 MHz)

WIMAX 2300-2.C2 (10 MHz)

Band Description




NT12-7001 ver 1.0 19

WIMAX 2500 (5 MHz)

WIMAX 2500 (10 MHz)

WIMAX 2500-3.A (5 MHz)

WIMAX 2500-3.A (10 MHz)

WIMAX 2500-BRS.AB (10 MHz)

WIMAX 2500-BRS.BC (10 MHz)

WIMAX 2500-BRS.CD (10 MHz)

WIMAX 2500-BRS.EF (10 MHz)

WIMAX 2500-BRS.FH (10 MHz)

WIMAX 2500-BRS.HG (10 MHz)

WIMAX 2600 (5 MHz)

WIMAX 2600 (10 MHz)



WIMAX 3300-4.C (10 MHz)



WIMAX 3500-5.AL (5 MHz)

WIMAX 3500-5.AH (5 MHz)


WIMAX 3500-5.BL (7 MHz)

WIMAX 3500-5.BH (7 MHz

WIMAX 3500-5.C (10 MHz)

WIMAX 3500-5.CL (10 MHz)

Band




20

4.6.1.7. Wi-Fi Bands

Wi-Fi uses unlicensed (ISM) frequency bands as specified in IEEE 802.11.These bands are not represented in the XML cell file.

WIMAX 3500-5.CH (10 MHz)

Band




NT12-7001 ver 1.0 21

4.7. Structure of Cell File

4.7.1. Diagram Conventions

In this section, the structure of the XML cell file is illustrated using treediagrams. A few conventions in these diagrams need to be explained:

Solid line box:The element is mandatory.

Lines in upper left corner:The element is atomic,i.e. it is fully defined in itself and does not containother elements. Non-atomic elements are drawnwithout these lines.

Arrow:The element type is global. Global elementtypes are ones that are reused multiple times in thefile structure, for instance because they are neededfor all technologies (e.g. CELLNAME, ANTENNA).The element type is defined only once in theschema file, and all occurrences of the elementtype refer to that definition. An element without thearrow is local and has a definition of its own.

Dashed line box:The element is optional.

Plus sign:The entity in the diagram contains otherelements within it. The subordinate structure iscollapsed in this case.

Minus sign:The subordinate structure is expanded.

Stacked boxes:Several instances of the elementmay occur. The permitted number of instances isindicated by a range; in this case, there must be atleast one CELL_LIST, but there is no fixed upperlimit on the number of such elements.

The element on the left must precede the element onthe right.

The element on the left must precede the elements onthe right; the latter, however, may come in arbitraryorder.




22

4.7.2. Overall File Structure

Nearly every piece of data in an XML cell file will be described as an elementor attribute. The main root element is TEMS_CELL_EXPORT; it has amandatory attribute VERSION which indicates the version of the cell fileformat.

The GENERATED_DATE element, also mandatory, indicates when the cellfile was generated.

A number of further, standard attributes need to be included in the cell file to

enable schema validation (checking of element names, value ranges, etc.):

xmlns:dataType="http://www.ascom.com/networktesting/dataTypes"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="TEMSCell.xsd" VERSION="1.2"

Please note that no path should be given toTEMSCell.xsd.




NT12-7001 ver 1.0 23

4.7.3. GSM Cell Data

GSM cell data is organized as follows:

The GSM element contains at least one and optionally several CELL_LISTelements. Cell lists are intended to be used to distinguish operators. Each celllist element contains at least one GSM cell. There is no limit to the number ofeither cells or cell lists.

Like the main root element, the GSM element has a mandatory VERSIONattribute stating the version of the GSM cell data structure.

CELL_LIST elements have one mandatory attribute, NET_OPERATOR.

For each GSM cell the following elements are specified:




24

Each cell element is a container that holds multiple subordinate elements. Ascan be seen in the diagram, only a few of these are mandatory. One isCELLNAME, whose value must be unique in the entire file. CELLNAME hasSYSTEM_TYPE as attribute; if this attribute is not set, it is implicitly assumed

that this cell belongs to the system (the communications technology) inwhose structure it is found, e.g. GSM.




NT12-7001 ver 1.0 25

4.7.4. WCDMA Cell Data

WCDMA cell data is organized like GSM cell data; compare section 4.7.3.

For each WCDMA cell the following elements are specified:




26

4.7.5. LTE Cell Data

LTE cell data is organized like GSM cell data; compare section 4.7.3.

For each LTE cell the following elements are specified:




NT12-7001 ver 1.0 27

4.7.6. TD-SCDMA Cell Data

TD-SCDMA cell data is organized like GSM cell data; compare section 4.7.3.

For each TD-SCDMA cell the following elements are specified:




28

4.7.7. CDMA Cell Data

CDMA cell data is organized like GSM cell data; compare section 4.7.3.

For each CDMA cell the following elements are specified:




NT12-7001 ver 1.0 29

4.7.8. EV-DO Cell Data

EV-DO cell data is organized like GSM cell data; compare section 4.7.3.

For each EV-DO cell the following elements are specified:




30

4.7.9. WiMAX Cell Data

WiMAX cell data is organized like GSM cell data; compare section 4.7.3.

For each WiMAX cell the following elements are specified:




NT12-7001 ver 1.0 31

4.7.10. Wi-Fi Access Point Data

Wi-Fi access point data is organized like GSM cell data; see section 4.7.3.1

For each Wi-Fi access point the following elements are specified:

1. For simplicity, the term CELL has been retained in the Wi-Fi datastructure, although Wi-Fi access points are not in fact cells in a cellular

network in the way that (e.g.) GSM cells are.




32

4.7.11. Site Data

The SITES data structure allows grouping of cells. However, this structure isnot used by the present version of TEMS Investigation, and therefore no

detailed description of it is provided here.

4.7.12. Container Elements

This section lists all remaining elements that contain other elements ascomponents. The atomic elements follow in section 4.7.13.

Mandatory components and global ones are indicated as such below. Forcomponents whose number may vary, the range of that number is given;

means that there is no fixed upper limit.

4.7.12.1. ANTENNA

4.7.12.2. BSIC

4.7.12.3. CDMA_CHANNEL_INFO

DIRECTION (mandatory)

BEAM_WIDTH

GAIN

HEIGHT

POLARIZATION

ELECTRICAL_TILT

MECHANICAL_TILT

TYPE

INFORMATION (global)

NCC (mandatory)

BCC (mandatory)

BAND (mandatory, global)

CHANNEL (mandatory, global)




NT12-7001 ver 1.0 33

4.7.12.4. CGI

4.7.12.5. CHANNEL_INFO

4.7.12.6. INFORMATION1

4.7.12.7. LTE_CGI

MCC

MNC_LENGTH

MNC

LAC

CI

BCCH (mandatory; this element contains:) ARFCN (mandatory, global)

BAND (global)

TCH [0 ... ] (this element contains:)

ARFCN (global)

BAND (global)

INFO [0 ...]

1. This element also has the attribute INFO_CATEGORY (section 4.7.14).

MCC

MNC_LENGTH

MNC

TAC

CI




34

4.7.12.8. NEIGHBOR_LIST

4.7.12.9. POSITION

4.7.12.10. REPEATER_LIST

4.7.12.11. TEMS_INTERNAL

This is data used internally by TEMS products.

4.7.12.12. WIMAX_CHANNEL_INFO

4.7.13. Atomic Elements

Under this heading, finally, are listed all elements which do not containsmaller elements as components. Global elements and local technology-specific elements are collected in a single list.

CELLNAME [1 ...] (mandatory, global)

GEODETIC_DATUM (mandatory)

LATITUDE (mandatory)

LONGITUDE (mandatory)

ALTITUDE

REPEATER [0 ...](this element contains:)

POSITION (mandatory, global)

ANTENNA (global)

BAND (mandatory, global)

CHANNEL (mandatory, global)

Element Description Data Type

ALTITUDE Ground height in meters above mean

sea level.

double




NT12-7001 ver 1.0 35

ARFCN Absolute Radio Frequency Channel

Number.

Long1023

BAND Operating band used for the cell. String_ OperatingBand

BASE_STATION_ID WiMAX Base Station Id. Mostsignificant 24 bits are Operator Id.Least significant 24 bits are Sector Id.

LongPositive

BCC Base Station Colour Code. Long7

BEAM_WIDTH Width of antenna beam in degrees. Float360CELL_NUMBER Unique numeric ID for the cell (must

be unique in the entire file).LongPositive

CELL_TYPE Type of the cell, e.g. Macro, Micro,Pico.

String128

CELLNAME Text label for cell; must be unique inthe entire cell file.

This element has the attribute

SYSTEM_TYPE (section 4.7.14).

string

CHANNEL The CDMA RF channel number. Long1023

CI Cell Identity. Equal to the 16-bit C-Id in 3GPP 25.401, section 6.1.5.

The 28-bit Cell Identity (UC-Id in3GPP) is a concatenation of RNC_IDand CI.

Long65535

CPI Cell Parameter ID. Long127

CPICH_POWER Primary CPICH power in dBm. double

DIRECTION Direction of the antenna beam indegrees clockwise from north.

Float360

EARFCN_DL Downlink EARFCN. Long65535

EIRP Effective Isotropic Radiated Power:the apparent power (in W) transmittedtowards the receiver.

double





36

ELECTRICAL_TILT Electrical tilt in degrees. Float90

ENODE_B Name of eNode B. String128_ Collapse

ENODE_B_STATUS Status of eNode B (e.g.Operational).

String128_Collapse

FREQUENCY Center frequency in Hz. LongPositive

GAIN Antenna gain in dB. float

GENERATED_DATE Date and time of XML file generation:YYYY-MM-DD.

Note:Other date formats (e.g. MM/DD/YYYY) are not allowed.

string

GEODETIC_DATUM Reference ellipsoid used by the GPSto calculate coordinates. The defaultGPS ellipsoid is WGS84. (Note thatthis element does notindicate theprojection.)

String_GeodeticDatum

HEIGHT Height above ground of antenna inmeters.

double

INFO Arbitrary additional information. String128

LAC Location Area Code. Long65535

LATITUDE Latitude in decimal degrees. Double90_90

LOCALCELLID Identifier used to uniquely identify theset of resources within a Node B

required to support a cell (as identifiedby a C-Id). 3GPP 25.401,section 6.1.6

Long268435455

LONGITUDE Longitude in decimal degrees. Double180_180

LTE_BANDWIDTH Bandwidth in LTE cell. Float_ LteBandwidth

MAC_ADDRESS MAC address of connected WLANaccess point (BSSID in IEEE 802.11

standard).

String128_Collapse





NT12-7001 ver 1.0 37

MAX_TX_POWER Maximum transmission power (in

dBm) for all downlink channels addedtogether.

Double5000

MECHANICAL_TILT Mechanical tilt in degrees. Float90

MCC Mobile Country Code. Long999

MNC Mobile Network Code. Long999

MNC_LENGTH Number of digits in MNC. Int2To3

NCC Network Colour Code. Long7

NODE_B Name of Node B. String128_ Collapse

NODE_B_STATUS Status of Node B (e.g. Operational). String128_ Collapse

PCI Physical Cell Identity. Long2

PCIG Physical Cell Identity Group. Long167

PHYSICAL_LAYER_CELL_ID

Physical Layer Cell Id, equal to3 PCIG + PCI. Optionally usedinstead of {PCI, PCIG}.

Long511

POLARIZATION Polarization of antenna (vertical,horizontal, or circular).

String128

PREAMBLE_INDEX WiMAX preamble index. Long113

RAC Routing Area Code. Long255

RNC_ID Radio Network Controller ID. Equal tothe 12-bit RNC-Id in 3GPP 25.401,section 6.1.5.

The 28-bit Cell Identity (UC-Id in3GPP) is a concatenation of RNC_IDand CI.

Long4096

RS_POWER Transmitted Reference Signal RSSI. double

SC Primary downlink scrambling code tobe used in the cell.

Long511





38

4.7.14. Attributes

SSID Service Set Identifier of connected

WLAN access point.

String128

TA E-UTRAN Tracking Area. Same asTAC; please use TAC instead.

Long65535

TAC E-UTRAN Tracking Area Code. Long65535

TIME_OFFSET Time offsets used in various contexts,for example in WCDMA to define thestarting point of scrambling codes onthe CPICH, SCH, etc. Express as a

multiple of 256 chips.

Long9

TYPE Type of antenna used. String128

UARFCN_DL Downlink UARFCN. Long16383

URA UTRAN Registration Area. Long65535


INFO_CATEGORY Associated with the INFORMATIONelement (section 4.7.12.6). Allowscategorization of the data put into thiselement.

String128_Collapse

NET_OPERATOR Associated with the CELL_LISTelement (sections 4.7.34.7.8).Consists of a string indicating the

name of the network operator.

String128_Collapse

SYSTEM_TYPE Associated with the CELLNAMEelement (see section 4.7.13). Consistsof a string indicating the type ofnetwork.

String_SystemType





NT12-7001 ver 1.0 39

4.8. Example of Complete XML File: UMTS/Wi-Fi

This example shows what an XML cell file with UMTS and Wi-Fi data maylook like. Certain parts which merely repeat previously shown structures areleft out; such omissions are indicated by ....

A complete file can be found in the directoryXMLSchema beneath the TEMSInvestigation installation directory.

2006-11-28

GSM Cell 10

MacroWGS8490.0180.03.14159265358979

360.0360.03.14159

3.14159265358979

VERSION Associated with

the file as a whole (main rootelement, TEMS_CELL_EXPORT:section 4.7.2)

with the elements denoting acommunications technology(sections 4.7.34.7.8). Separateversion numbering is applied toeach of these entities.

Float100





40

Vertical90.090.0Antenna Type 1

Antenna Info 1Antenna Info 2

255

999399965535

65535

77

1023GSM 900

1023GSM 900

1023GSM 900

3.14159265358979

GSM Cell 2GSM Cell 3

GSM Cell 2...

GSM Cell 3...




NT12-7001 ver 1.0 41

...

...

...

...

WCDMA Cell 10String268435455

...

...

255...

5111638340966553593.141592653589795000

Base Station 1Operational

WCDMA Cell 2WCDMA Cell 3

WCDMA Cell 2...




42

WCDMA Cell 3...

...

...

...

...

Wi-Fi AP 10String268435455

...

00-00-00-00-00-00MyESS

Wi-Fi AP 2Wi-Fi AP 3

Wi-Fi AP 2...

Wi-Fi AP 3...

...

...

...




NT12-7001 ver 1.0 43

...

4.9. Example of Complete XML File: CDMA/EV-DO

Below is an example showing an XML cell file with CDMA and EV-DO data.Again, some parts which repeat previously shown structures are left out;omissions are indicated by .... See also section 4.8.

2006-11-28

CDMA Cell 1

0Macro

...

...147

CDMA 450

233.141592653589792.71828182845904

CDMA Cell 2CDMA Cell 3

CDMA Cell 2




44

...

CDMA Cell 3

...

...

...

...

...

EV-DO Cell 1

...

...

...

...

4.10. Note on Processing in TEMS Investigation

Any syntax errors found when loading the XML cell file into TEMSInvestigation are reported in a single message box. If there are many errors,the entire box might not fit on the screen, so that only part of it will be visible.



Chapter 5. Cell Identification

NT12-7001 ver 1.0 45

5. Cell Identification

This chapter describes the algorithms used to identify in the cell file thosecells that a device interacts with or scans.

5.1. Cell Identification in GSM

For the cell file formats, see chapter3(CEL format) and chapter4(XMLformat).

The CGI step in the algorithms below can be performed only with devicescapable of obtaining CGI data. With other devices, this step is skipped.Compare the descriptions of the information elements Cell Name Algorithmand Neighbor Cell Name Algorithm: see Information Elements and Events,section 3.1.

5.1.1. Serving Cell

The following procedure is used to find a matching cell:

1. If CGI (MCC, MNC, LAC, CI) is available, look up the cell in the cell file.

2. Otherwise, try to match the ARFCN and BSIC in the cell file, alsoconsidering the geographical position of the sample. A position isconsidered valid if the distance to the cell is less than 35 km. If multiplematches are found within a 35 km radius, the closest cell is picked. Ifthe position is invalid, no result is returned unless a unique match is

found in the cell file.

5.1.2. Neighbors


1. If CGI (MCC, MNC, LAC, CI) is available, look up the cell in the cell file.

2. Otherwise, if the current serving cell is known, search that cellsneighbor list as defined in the cell file for a neighbor with matching

ARFCN and BSIC.
http://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdf




46

3. If the current serving cell is not known, search the entire cell file for cellswith matching ARFCN and BSIC, also considering the geographicalposition of the sample. A position is considered valid if the distance tothe cell is less than 35 km. If multiple matches are found within a 35 kmradius, the closest cell is picked. If the position is invalid, no result isreturned unless a unique match is found in the cell file.

5.2. Cell Identification in WCDMA

For the cell file formats, see chapter3(CEL format) and chapter4(XMLformat). Note the following:

CEL format: CI must be the full 28-bit Cell Id (see section 3.4).

XML format: Both CI and RNC_ID must be set (see section 4.7.13).


1. If a valid 28-bit Cell Id is available for the SAN (Serving/Active set/Neighbors) constellation, look up the cell in the cell file. This is possiblein idle mode only, because only then can the Cell Id be obtained.

2. Otherwise, try to match the UARFCN and SC in the cell file, alsoconsidering the geographical position of the sample. A position isconsidered valid if the distance to the cell is less than 200 km. If multiple

matches are found within a 200 km radius, the closest cell is picked. Ifthe position is invalid, no result is returned unless a unique match isfound in the cell file.

Step 1 is possible only with a UE. With a scanner, only step 2 is performed.

5.3. Cell Identification in LTE

For the cell file format, see chapter4(XML format).


1. If a valid 28-bit Cell Id is available for the SAN (Serving/Active set/Neighbors) constellation, look up the cell in the cell file. This is possiblein idle mode only, because only then can the Cell Id be obtained.

2. Otherwise, try to match the EARFCN and Physical Layer Cell ID(= PCI + 3 * PCIG) in the cell file, also considering the geographicalposition of the sample. A position is considered valid if the distance tothe cell is less than 50 km. If multiple matches are found within a 50 km



Chapter 5. Cell Identification

NT12-7001 ver 1.0 47

radius, the closest cell is picked. If the position is invalid, no result isreturned unless a unique match is found in the cell file.

Step 1 is possible only with a UE. With a scanner, only step 2 is performed.

5.4. Cell Identification in CDMA



Try to match the samples system type (CDMA/EV-DO), frequency band,RF channel and PN offset in the cell file, also considering thegeographical position of the sample. A position is considered valid if the

distance to the cell is less than 100 km. If multiple matches are foundwithin a 100 km radius, the closest cell is picked. If the position is invalid,no result is returned unless a unique match is found in the cell file.

5.5. Cell Identification in WiMAX



Try to match the samples system frequency band, RF channel andPreamble Index in the cell file, also considering the geographical positionof the sample. A position is considered valid if the distance to the cell isless than 50 km. If multiple matches are found within a 50 km radius, nocell is picked. If the position is invalid, no result is returned unless aunique match is found in the cell file.




48

6. Format of Cell Whitelists

Underlying User-definedEvents

This chapter describes the format of cell whitelists, which are composed in

the Cell Whitelist Generator of the Event Definition window and converted byTEMS Investigation into a user-defined event. See the Users Manual,section 22.4.

6.1. Format Description

Overall Structure

The basic structure of the whitelist is as follows:

$#,[],[],...[],

An arbitrary number of cells (LAC/CI lines) can be listed. The RAT, MCC, andMNC apply to all of these cells.

The above structure can be iterated in the following ways:

Under one RAT, multiple #, sections can be entered,each with a separate list of cells.

Multiple $ sections can be entered, each containing the abovestructure in its entirety.

Radio Access Technology

is one of {GSM, WCDMA}.
http://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdf



Chapter 6. Format of Cell Whitelists Underlying User-defined Events

NT12-7001 ver 1.0 49

Information Elements Used for GSM

= MCC, Mobile Country Code.

= MNC, Mobile Network Code.

= LAC, serving cell Location Area Code in decimal format. This isoptional and will be left out of the event expression if not specified.

= Cell Id, Cell Identity of serving cell in decimal format.

Information Elements Used for WCDMA

= MCC, Mobile Country Code.

= MNC, Mobile Network Code.

= Serving Cell LAC, serving cell Location Area Code in decimalformat. This is optional and will be left out of the event expression if notspecified.

= Serving Cell Id (CI Part), serving cell C-ID (16 bits) in decimalformat.

Spaces and empty lines are ignored throughout.

6.2. Example

Below is an example of a valid whitelist. Spaces and newlines have beeninserted for readability.

Note that in the WCDMA section, the LAC has been omitted throughout.

$GSM

#240, 054301, 31501

4301, 315024301, 315747849, 293617849, 29362

#240, 072605, 189752605, 18978
http://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/IEs%20and%20Events/Investigation%20IEs%20and%20Events.pdf




50

$WCDMA

#240, 01, 49017, 49018, 49019

6.3. Conversion to Event Expression

For a given RAT, each #,section is transformed into a logicalexpression of this form:

MCC = ANDMNC =

AND(

(LAC = ) AND (CI = )OR(LAC = ) AND (CI = )OR...

OR(LAC = ) AND (CI = )

)

If some LACiis omitted, the ith member of the OR expression simplifies toCI = .

If there are multiple #,sections, they are joined by OR at thetop level.



Chapter 7. Data Session Error Messages

NT12-7001 ver 1.0 51

7. Data Session Error Messages

Below are listed error messages that may occur when doing data servicetesting, whether manually (see the Users Manual, section 9.3) or inautomated fashion using Service Control scripts (see the Users Manual,chapter20).

7.1. General Data Service Error Messages

Message Explanation

Bad hostname An attempt was made to use an APN withoutweb services.

Connection failed A failure occurred in connecting to the server.

Connection terminated The connection was terminated (most likelyby the server) before completion.

Connection timeout A timeout occurred while the client wasattempting to establish a connection to theserver. Possible causes:

Use of incorrect port number.

(FTP)URL or IP address put into FTPAccount field instead of Remote Address

field.

Failed to start IP sniffer Start-up of the IP sniffing function in TEMSInvestigation failed.

Session aborted by user The user aborted the session for somereason.

Socket already open or inuse

An attempt was made to use a socket that isalready opened or already in use.
http://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdf




52

Socket creation failed An attempt to create a socket was

unsuccessful.

Socket error Socket binding to local port failed, orreceiving of data from the socket failed.Possible causes:

The socket already exists whenattempting a dial-up. Try disconnectingthe data session (icon in system tray).

The phone has been deactivated in TEMS

Investigation. Try reactivating the phone.

(FTP)Use of leading slash for root-located file.

The address is not valid Possible causes:

Use of non-existent URL or IP address asremote address.

The DNS lookup of the host name failed.

(FTP)Path appended to the URL or IPaddress under Remote Address (notallowed: see the Users Manual,sections 20.16.3.9, 20.16.3.10).

Timeout A connection to the server was successfullyestablished, but a timeout occurred at a latertime. (Compare Connection timeoutabove.)

Unknown error A failure occurred in decoding a message

from the server. Possible causes:

Use of forward slashes in the Target File(local) path.

Phone disconnected from TEMSInvestigation. Reconnect the phone.

Message Explanation
http://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdfhttp://c/Users/sepeer/Documents/backup/in_progress/Investigation%2014.1/FrameMaker/User's%20Manual/Investigation%20User's%20Manual.pdf




NT12-7001 ver 1.0 53

7.2. RAS Error Messages

7.3. NDIS Error Messages

Message Explanation

Internal error An invalid APN was used.

No answer The remote computer did not respond.

The PPP link controlprotocol terminated

Possible causes:

PDP Context Activation failure. See theActivate PDP Context Reject message inthe Layer 3 Messages window for thecause value.

The phone lacks an APN for the network.Try setting the APN by sending thefollowing command to the phone:

AT+CGDCONT=1, "IP","my_server.com"(replace the final string by the correctURL).

The request has timedout

A subsequent error occurred after an initialPDP Context Activation error. Action: Stop,

reload, and restart the script.

Unknown error Possible cause: Use of *99***n#as accessphone number (where nindicates the nth

APN entry in the phone). Some phones donot accept this syntax.

Message Explanation

NDIS device notconnected. IP addressnot assigned to networkadapter

No connect operation has been performed inthe phone-specific software application. Seethe Users Manual, section 20.16.3.1.




54

7.4. FTP Error Messages

Message Explanation

Account not accepted The FTP account was invalid.

Cannot transfer withoutvalid account

The user lacked a valid account for logging into the FTP server.

Data port could not beopened

The server failed to connect on the FTP dataport. (FTP utilizes two ports, a data port and acommand port.)

File access denied The user did not have permission to accessthe file on the server.

File not found The file to upload or download was not found.Possible causes (download):

The file was not in the remote directory.

The file was in the remote directory, butthe user lacked read permission for thatdirectory.

Local directory error (FTP DL)The target file directory did notexist, and an attempt to create it failed.

(FTP UL)The source file directory did notexist.

Not able to open file forwriting

The specified file is read-only.

Password not accepted The password was invalid.

Port command failed Something went wrong when non-passivemode was used. This could happen if theclient is behind a firewall.

The RETR commandfailed

A failure occurred when trying to retrieve afile from the server.

Unsufficient storagespace

There was not enough disk space available todownload the file.




NT12-7001 ver 1.0 55

7.5. E-mail Error Messages

User not accepted The user name was invalid.

Message Explanation

Failed to add attachmentto the message

Adding an attachment failed.

HELLO command wasrejected or notresponded to by theserver

The client attempted to initiate a connectionwith the e-mail server, but the server did notrespond.

Invalid values ofparameters

Typically reported when the e-mail messagebody or receiver/sender is missing.

Password commandtimed out or rejected

Sending the password to the server failed.

The DATA commandfailed

Sending the e-mail message body to therecipient failed.

The message body is toobig

(The maximum message body size is 32 kB.)

The RETR commandfailed

An attempt to retrieve a file from the serverfailed.

The user command has

timed out or rejected

Sending the user name failed.

There was a problemwith the server withrespect to the RCPTcommand

The e-mail server could not resolve theidentity of the message recipient.

There was no responsefrom the server

The client attempted to retrieve the responsecode from the server, but the server did notrespond to the clients request.

Message Explanation




56

7.6. Video Streaming Error Messages

7.7. MMS Error Messages

Message Explanation

Connection failed A failure occurred in the RTSP protocol whenthe streaming client was trying to initiate aconnection with the streaming server.

Data timeout The streaming client did not receive any datawithin the specified timeout period.

File not found The requested file was not found on thestreaming server.

Host could not beresolved

The streaming server with the specifiedremote address could not be found.

Invalid parameter Some parameters in the script setup areincorrect.

Live measurement moderequired

(Live measurement mode is required whenspecifying an SDP file as source file.)

Stream setup failed The streaming client did not succeed insetting up the video/audio streams.

Streaming client initial-ization failed

A failure occurred related to adding orconnecting video/audio filters.

Streaming client internalerror

This message is usually reported due to afailure in the RTSP communication with thestreaming server.

Unsupported payload An attempt was made to use an unsupported

video or audio codec.

Message Explanation

Message not found onMMSC

The message could not be located on theMMSC.




NT12-7001 ver 1.0 57

7.7.1. MMS Send Failure Causes

An unspecified error occurred during the processing or reception of thecorresponding request.

The client did not have permission or funds to perform the requestedoperation.

An inconsistency with the message format was detected when thecorresponding request was parsed.

There was no MMS address (From:, To:, Cc:, Bcc:) in a proper format, ornone of the addresses belonged to the MMSC.

The MMSC was not able to accept the corresponding request due to

capacity overload. The MMSC does not support the corresponding request abstract

message.

The corresponding M-Send.req as received was valid and understood bythe MMS Proxy-Relay, but some temporary condition or event caused anerror to occur.

The MMS Proxy-Relay was not able to handle the correspondingM-Send.req due to an unspecified error on the transport layer or due tocapacity overload.

MMS receive failure A failure occurred when retrieving the MMS

from the MMSC.

MMS send failure This error message has many possiblecauses. They are listed in section 7.7.1.

MMSC redirect notsupported

The MMSC reply is a redirection request.

MMSC request error A failure occurred following a request to theMMSC.

MMSC unexpected reply A reply was received in a format other thanan MMS message.

Received MMS is corrupt The received MMS is corrupt.

Message Explanation




58

An unspecified permanent error occurred during the processing orreception of the corresponding M-Send.req.

The corresponding M-Send.req was rejected due to failure of

authentication or authorization of the originating MMS client. An inconsistency in the formats of optional or mandatory header fields or

an error in header field values was detected when the correspondingM-Send.req was parsed.

The MMS Proxy-Relay was not able to resolve the insert-address-tokeninto a valid sending address.

The MM content in the M-Send.req was not accepted due to size, mediatype, copyrights, or for some other reason.

The corresponding request contained a reply MM that was too large, notwithin the reply charging deadline, and/or contained non-text mediaelements although only text was allowed.

The M-Send.req contained an XMms-Reply-Charging header field withthe value Accepted or Accepted text only.

The MMS Proxy-Relay does not support reply charging. Thecorresponding M-Send.req contained reply charging parameters and wasthus rejected.

The MMS Proxy-Relay does not support address hiding. Thecorresponding M-Send.req had XMms-Sender-Visibility set to Hide andwas thus rejected.

7.8. WAP Error Messages

Message Explanation

Failed to create WAPstack

Something went wrong when creating theWAP stack.

Failed to disconnect An error occurred when disconnecting fromthe server.

The GET commandfailed

The requested data source could not beretrieved.



Chapter 8. Text Export Format for Logfiles

NT12-7001 ver 1.0 59

8. Text Export Format for

Logfiles

8.1. General

The text export format for logfiles uses an ASCII representation with tab

delimited data. The default file extension is .fmt.

8.2. File Header

The first line in the file contains column headers. Headers marked * are orcan be excluded from the reduced version of the text export file (see theUsers Manual, section 11.6.2.2):

Time

MS

Frame Number*

Direction

Message Type

Message ID*

Hexadecimal String*

Event

Event Info*

One header for each information element component exported,composed of: the device designation (orAll, if the data is exported for alldevices), the name of the information element, and the argument, if thereis one. Examples:

(GSM)All-RxLev Full,MS1-Neighbor BSIC [1]

(WCDMA)All-RRC State,MS1-AS CPICH Ec/No [1]

(CDMA)All-CDMA Rx State,MS1-Neighbor Set PN [2]




60

Note that positioning data, too, is exported as ordinary information elementcolumns.

8.3. Data

The remainder of the export file contains logfile data. Each line of datarepresents one message. The table below describes the format of the data ineach column:

Column Header Description/Format

Time Current time:hh:mm:ss:tt, wherett = decimal seconds.

MS Device designation:MSn orDCn(n is an integer).

Frame Number Frame number of the TDMA frame. Integer in therange 0 ... 2715648. (Valid only for GSM messages;Not Valid for WCDMA and CDMA messages.)

Direction Direction of the message: UL, DL, orInternal.

Message Type Type of message, e.g.

(GSM)Paging Request Type 1, Synch ChannelInformation

(WCDMA)System Information Bl

109506957 TEMS Investigation 14 1 Technical Reference

Documents

Transcript of 109506957 TEMS Investigation 14 1 Technical Reference