ECAS. Conversion Specification. Provided to ECAS. Issue 4.1. Document No.

Transcription

1 ECAS Mobile Conversion Specification Location Provided to ECAS Issue 4.1 Document No.

2 Document Information Document Title Mobile Location Conversion Specification Filename Mobile Location Conversion Specification Issue 3.0 Purpose of Specification document Approver DCENR Document Revision Control Revision Description of change Author Approval Date Issue 1.0 Specification developed BT based on DCENR Draft Issue 1.1 Minor corrections BT following review Issue 1.2 Corrections following BT further review Issue 2.0 Issued for Circulation BT Issue 2.1 Updates to LAC default BT values Issue 3.0 Correction to coordinate BT formats Draft 4.0 Incorporate LTE CGI BT 16 April 2014 format in existing 2/3G specification Issue 4.1 Version number raised BT 14 August 2014 in line with other specifications. No other Changes

3 CONTENTS 1. INTRODUCTION SCOPE OF THE SPECIFICATION DATA REQUIREMENTS MOBILE LOCATION INFORMATION STRUCTURE INFORMATION TYPES HIGH LEVEL FILE SPECIFICATIONS UPDATE TYPES NUMBER OF RECORDS PER FILE PROCESSING AND IMPORT ERRORS REPORT FILES FREQUENCY OF UPDATES TIMELINESS OF UPDATES DATA CONSISTENCY DATA ACCURACY FILE NAMES CAPITALISATION WITHIN A FILE LOCATION INFORMATION FIELDS CELL SHAPES CELL INFO RECORDS FOR 2/3G CELLS /3G LOCATION AREA DESCRIPTION /3G CGI RECORD FORMAT CELL INFO RECORDS FOR LTE CELLS LTE CELL IDS LTE CELL ID RECORD FORMAT DATA TYPES AND FIELD VALIDATION CAPITALISATION WITHIN A FILE ALLOWABLE DATA CHARACTERS... 19

4 1. Introduction The following is an outline specification for information to be provided by Mobile Network Operators to the Emergency Call Answering Service (ECAS) to support the conversion, by ECAS, of Mobile location information to geocoordinates, in association with an Emergency Call. Where appropriate, mobile location information may be transferred from the ECAS to the Emergency Services. Part I of this specification addresses the transfer of mobile location information to the ECAS in association with an Emergency Call. Note, in this specification an Operator refers to any Authorised Operator. The majority of fixed location information is expected to be provided by eircom. 1.1 Scope of the specification This specification addresses the content and format of mobile location conversion information provided by mobile network operators. The specification is applicable to GSM, 3G and LTE networks.

5 2. Data requirements 2.1 Mobile location INFORMATION structure /3G Mobile Cells The 2/3G Mobile location information structure is as follows: MCC-MNC-LAC-CI where: MCC is the Mobile Country Code (272 for Ireland) MNC is the Mobile Network Code LAC is the Location Area Code CI is the Cell Identity LTE Mobile Cells and CGI The LTE Cell Global Identifier (CGI) is shown in the following diagram MCC As for 2/3G networks and is expected to have the value 272 for all Irish mobile network operators MNC 2 digits to be used and should be consistent with the 2/3G mobile network code used by each operator. enb ID 7 Digits Cell ID 3 Digits These elements are further described in Mobile Location Transfer Specification.

6 2.2 Information Types The 2/3G Cell ID or LTE CGI and network details of the originating emergency call will be passed to ECAS as part of the destination number as described above and in the Mobile Location Transfer Specification. The following information is required to enable ECAS to convert this Data to a geographic Location. 1. Details of any 2/3G Location area codes in use by the Mobile Network Operator and in particular where the Location area code can be used to identify an approximate geographic area an appropriate description of this area. 2. Details of the 2/3G Location area code and Cell ID combination or Cell Global Identifier including details of the location of the Cell and optionally the expected coverage area for that cell. Or 1. Details of the LTE CGI including enb ID and Cell ID including details of the location of the cell and expected coverage area of the Cell. The ECAS system will import this information from each operator as a separate file for each information type. For each imported file, the import process will create a report file which will contain the number of records imported and details of any rejected records. 2.3 High Level File Specifications The format of all files must satisfy the following requirements: 1. Text, flat file format shall be used 2. Variable length fields shall be used. Each field within the record will be delimited by a pipe ( ) character 3. Any unused field within a record shall be seen as two consecutive delimiters 4. No fields within the record shall be padded out. 5. All field values within the record must be left Justified i.e. no leading spaces or tab characters Each Record shall be separated by a carriage return, line feed. 7. The last Record within each file will hold the number of records sent excluding header and trailer records (as detailed below). 8. The first record will be written as *SOF* <ID> INPUT where <ID> is a Variable length operator id as described below

7 9. The last record will be written as *EOF* Number of records in file The pipe ( ) character has been chosen as the delimiter due to its infrequent occurrence and lack of implied meaning within addresses in Ireland as opposed to the comma (,) character which depending on the information supplied could conceivably occur as part of a field value (e.g. name and address data) Operator id A Variable length operator id will be assigned to each Operator by ECAS. This operator id shall be included in the file name and header records for all files as described below. The operator id and other required details will be agreed between ECAS and the Operator at an operational level prior to Go-Live Header and Trailer records Header and trailer records shall be constructed and included in all files types as follows: Header Records The Header record shall be pipe delimited and contain 3 fields in the following order o The String *SOF o The operator ID o The String INPUT Trailer Records The Trailer record shall be pipe delimited and contain 2 fields in the following order o The String *EOF* o The number of Data records in the file which will be the total number of lines in the file less File Records A description of all fields contained within the various record types including details the allowable values are Numeric or Alpha/Numeric is given in the

8 section 4 for the Location Area Code records, and section 4.2 for the Cell Global Identifier Records. Note: Mobile location conversion records for both 2/3G Cells and LTE Cells should be included in a single file uploaded by operators. This file will contain a mix of 2/3G Cell records and LTE Cell records. Multiple file uploads is not supported and due to the fact that full upload types only are supported would result in all records in the ECAS ERD for a given operator being replaced by the records contained in the last upload file only Record Keys Operators should note that for the Mobile Location Conversion information, the following field combinations will be used as record keys and duplicates of these field combinations are not permitted within input files Location Area Codes Records Location area Code records will use the following field combination as a key o MCC Mobile Country Code o MNC Mobile Network Code o LAC Location area Code Cell ID Records Cell ID (or Cell Global Identifier) records will use the following field combination as a key o MCC Mobile Country Code o MNC Mobile Network Code o LAC Location area Code o CI Cell Identifier 2.4 Update Types For Mobile Location Conversion information, only a full update is provided for. Operators should provide all information as part of 2 files (Location Area Codes, and Cell Ids) in a full update as required. Operators should note that the information submitted by them with each update will be used to completely replace all data for that operator in the ECAS databases and as a result should take care to ensure that any updates provided are complete. 2.5 Number of records per file While it is not expected to apply or be a limiting factor for mobile location conversion information the number of records per file shall not exceed 64,000.

9 2.6 Processing and import errors Records in all input files will be processed and imported sequentially. In the case where a record can not be processed, for example the record is not correctly formatted, or field validation failed, this will be identified in the report file associated with that import file as described in the ECAS Data Transfer Specification document. Operators should note that a threshold for processing errors will be set on a per import file basis such that if the number of processing errors encountered while processing the file exceeds this threshold, processing and further import of the records in that file will be aborted and the entire file will be rejected. An appropriate value for this threshold will be set at the discretion of the ECAS service and notified to the operator at an operational level. 2.7 Report files The ECAS system will generate a report file for each data file received containing details of any processing errors encountered during the import of the data file. Operators shall retrieve the relevant report files from the ECAS system once processing has concluded and take immediate action to resolve any processing errors reported in order to ensure that the records are correctly formatted and will process correctly and will be re-submitted as part of the next update. The high level specification for Report files will be as described in the ECAS Data Transfer Specification document. 2.8 Frequency of updates Operators shall provide Mobile Location Conversion Information updates to ECAS as required when changes occur within their network. A full update should be provided periodically in any case at a frequency to be agreed between ECAS and the operator at an operational level. The times of day that operators should perform the transfer and also retrieve report files will also be agreed between the operator and ECAS at an operational level. 2.9 Timeliness of updates Updates to Mobile Location Conversion information should be submitted to ECAS as soon as is practical following updates to the information available on the Operator s systems. Operators shall endeavour to make updated information available to ECAS prior to or as soon as possible after a new installation is configured within its

10 internal systems or in the case of a change to a mobile cell site affecting range or area covered is identified Data consistency The Operator shall ensure that at all times an accurate and consistent representation of the required Mobile Location Conversion Information has been supplied to ECAS as the last full update provided Data Accuracy Operators shall be responsible for the accuracy of its Mobile Location Conversion Information. Operators shall ensure that data submitted to ECAS is accurate for the purposes of determining caller location. Operators are reminded of the importance of supplying complete and accurate information to ECAS. This is especially relevant to the expected or approximate coverage area for Cells. To assist ECAS and indeed the emergency services operators should endeavour to provide all available information including direction and coverage area where this information can be considered to be reasonably accurate. In the case where an operator has information to indicate that the details on Cell direction or coverage may not be accurate (e.g. coverage problems reported etc.) then values for these fields should not be supplied until the operator has resolved any associated issues or confirmed updated values. In situations such as this operators should submit an update to ECAS to reflect the known information on Cell coverage as soon as possible General Accuracy issues Obviously there are a number of issues which will limit the accuracy of location information generated using this system. Some of these are outlined below: 1. Cell size uncertainty. A caller may be located anywhere within a cell, and hence uncertainty as to their actual location will be proportional to the cell size. 2. Radio issues. There is a possibility that a caller using a cell is not located in the predicted coverage area of that cell but in another area. This situation is a result of the nature of mobile radio systems, with

11 overlapping cells, dynamic power outputs and dynamic radio propagation characteristics. 3. Cell map error. The representation of cells used in this specification allows only a simplistic representation of what, in reality, is a complex map. 4. Incorrect CGI conversion information. Operators should endeavour to avoid this situation where possible in submitting information to ECAS. As a result of these issues, the probability that a caller is within the area indicated by the relevant cell map is assumed to be no more than reasonably high however no measurement of actual system accuracy has been made File Names Input files File names of all input files presented to ECAS by Operators shall be in the following format ECAS_<INFO>_<TYPE>_<OPID>_<DATE>.DAT Where: <DATE> is the date that the export was performed by the Operator in the format YYYYMMDD. <OPIP> is the 5 digit operator id assigned to the Operator by ECAS. This ID will be assigned at an operational level between to the Operator by ECAS. <INFO> is a two character string indicating the type of information being submitted in this update file. The <INFO> string shall have the following values o ML for Mobile Location Conversion information detailing Location area code records o MC for mobile Location Conversion information detailing Cell Global Identifier records. <TYPE> is a one character string indicating if the update is a full or incremental update where F denotes a full update and I indicates that this file relates to an incremental update. In the case of Mobile

12 Location Conversion Information, the update type will always be F for full. The.DAT file extension indicates that this file is an input file Report files Report file names generated by the import process will be named exactly as per the input files with the exception of the file extension which will be.rep i.e. ECAS_<INFO>_<TYPE>_<OPID>_<DATE>.REP

13 2.13 Capitalisation within a file Operators shall send records with mixed case letters, as appropriate to the field value e.g. Normal personal names and place names towns counties should be lowercase starting with a capital or as appropriate to the business name e.g. AIB Bank Location information fields Geographic Location or position information should be provided for all Cell Global Identifier records. The format for this information will be Latitude and Longitude. 3. Cell shapes The specification supports one basic cell shape: an ellipse in the case where the optional coverage area and direction have been provided. The ellipse shall approximate the likely coverage area of the Cell and should be defined by the following: o A Point representing the Base station as the origin of the coverage ellipse. o The Azimuth or direction of coverage the Angle with reference to True North between 000º and 359º. o The approximate or expected Coverage area of the Cell/Ellipse in square kilometres. The shapes are indicated in the figures below. More complex shapes such as polygons are not supported and altitude is not supported. In the case of the point shape, the point refers to the Base Station or Node B.

14 North Angle α Cell Area Base Station/Node B Figure 1: Cell modelled with an ellipse

15 4. Cell Info Records for 2/3G Cells Mobile location Conversion information records should be included in the upload files submitted by each operator for all 2/3G Cells on that operators network using the record format described here 4.1 2/3G Location Area Description A location area description shall be provided. The description offers limited location information in the event of an unidentified Cell Identity being received. LAC Description records should be provided in files formatted and named as described in Section 2 and the records should be formatted as described below LAC description Record ID Field Mandatory Type Value Definition 1. MCC Yes N 272 Fixed 2. MNC Yes N 01 - Vodafone, 02 - O Meteor 05 - H3GI Or other values assigned by Comreg. 2 Digit Zero filled Numeric Value 3. LAC Yes N 1 to Set by mobile operator. 5 Digit Zero Filled numeric Value 4. LAC description Yes AN Description of the Location Area. The Location Area description should not imply greater precision than is available. An example of a suitable description would be South Leinster area Note: As the record format for this text file is delimited, all fields are required. The heading mandatory in the table above is used to indicate there a value must be provided or a null or empty value (represented as 2 consecutive delimiters) may be provided. The fields types for the above fields are AN denoting an alphanumeric variable length string, and N for a purely numeric value. Table 1: Location Area description record

16 4.2 2/3G CGI Record Format Cell ID or Cell Global Identifier records should be provided for all Cell sites in the Operator s network. CGI Description records should be provided in files formatted and named as described in Section 2 and the records should be formatted as described below /3G CGI Records ID Field Mandatory Type Value Definition 1. MCC Yes N 272 Fixed 2. MNC Yes N 01 - Vodafone, 02 - O Meteor 05 - H3GI 3. LAC Yes N 1 to Set by mobile operator 4. CI Yes N 1 to Set by mobile operator Or other values assigned by Comreg. 2 Digit Zero filled Numeric value 5 Digit Zero filled numeric value. 5 Digit Zero filled numeric value. 5. Latitude of Base Station/Node B Yes AN See note 2 Latitude in decimal degrees prefixed with N or S. See note 2 below. Reference system WGS 84 shall be used. 6. Longitude of Base Station/Node B Yes AN See note 2 Longitude in decimal degrees prefixed with E or W. See note 2 below Reference system WGS 84 shall be used. 7. Angle α No N 0 to +359 See Section Cell area No N [Km 2 ] 9. Address No AN Address of the Cell (where applicable). Free format. Note 1: Note 2: As the record format for this text file is delimited, all fields are required. The heading mandatory in the table above is used to indicate there a value must be provided or a null or empty value (represented as 2 consecutive delimiters) may be provided. Position values for the Cell site i.e. Fields 5 and 6, the Latitude and longitude should be provided as a string in exactly the following format. Latitude (5) Longitude (6) NDD dddd WDD dddd Where N and W denote North or West. All locations in Ireland will be West however the W indicator should be used as opposed to a E or negative East value. DD denotes a 2 digit zero filled numeric value for Degrees from 0 to 90 (in reality between 51 and 54 for latitude and between 5 and 11 for Longitude) MM denotes a 2 digit zero filled numeric value for minutes. dddd denotes an (upto) 4 digit value for decimals of a degree Table 2: CGI record

17 5. Cell Info Records for LTE Cells Mobile location conversion information records for all LTE Cells on an operators network that are capable of carrying voice traffic including emergency calls should be included in the upload file using the format and rules specified in this section. 5.1 LTE Cell IDs. LTE Cell IDs differ from 2/3G Cell IDs in that they incorporate a 7 digit enb ID and 3 Digit Cell ID as opposed to the 2/3G 5 Digit LAC and 5 Digit Cell ID. In order to utilise the existing 2/3G file format and import specification operators should include LTE Cell IDs for all LTE Cells by splitting the 7+3 digit format of enb and CellID into a 5+5 Digit format as shown in the following diagram. 5.2 LTE Cell ID Record Format Cell ID or Cell Global Identifier records should be provided for all LTE Cell sites in the Operator s network. CGI Description records should be provided in files formatted and named as described in Section 2 and the records should be formatted as described below LTE CGI Records

18 ID Field Mandatory Type Value Definition 1. MCC Yes N 272 Fixed 2. MNC Yes N 01 - Vodafone, 02 - O Meteor 05 - H3GI 3. LAC Yes N 1 to Set by mobile operator 4. CI Yes N 1 to Set by mobile operator Or other values assigned by Comreg. 2 Digit Zero filled Numeric value Leftmost 5 Digits of the LTE enb ID 5 Digit field comprised of the rightmost 2 Digits of the LTE enb ID prepended to the 3 Digit LTE Cell ID 5. Latitude of Base Station/Node B Yes AN See note 2 Latitude in decimal degrees prefixed with N or S. See note 2 below. Reference system WGS 84 shall be used. 6. Longitude of Base Station/Node B Yes AN See note 2 Longitude in decimal degrees prefixed with E or W. See note 2 below Reference system WGS 84 shall be used. 7. Angle α No N 0 to +359 See Section Cell area No N [Km 2 ] 9. Address No AN Address of the Cell (where applicable). Free format. Note 1: Note 2: As the record format for this text file is delimited, all fields are required. The heading mandatory in the table above is used to indicate there a value must be provided or a null or empty value (represented as 2 consecutive delimiters) may be provided. Position values for the Cell site i.e. Fields 5 and 6, the Latitude and longitude should be provided as a string in exactly the following format. Latitude (5) Longitude (6) NDD dddd WDD dddd Where N and W denote North or West. All locations in Ireland will be West however the W indicator should be used as opposed to a E or negative East value. DD denotes a 2 digit zero filled numeric value for Degrees from 0 to 90 (in reality between 51 and 54 for latitude and between 5 and 11 for Longitude) MM denotes a 2 digit zero filled numeric value for minutes. dddd denotes an (upto) 4 digit value for decimals of a degree Table 3: CGI record

19 6. Data types and field validation It should be noted that it is the responsibility of the operator to ensure that information submitted can be successfully imported into the ECAS databases Alphabets Text and character fields shall support the Irish and English alphabets only. 6.2 Capitalisation within a file All name and address fields should be supplied in mixed case as used to represent address fields. 6.3 Allowable data Characters The following Characters are the only valid Data Characters within a Record Character Printer Graphi c Field Types Position in Field Space Space AN Anywhere except first or last Character in a populated field Full stop. AN Anywhere except first Character in a populated field Ampersand & AN Anywhere except first Character in a populated field. Ampersand can be used instead of the word and e.g. John & Mary etc. Back slash \ AN Irish language fada. Inserted after the vowel to which the fada is to be applied. Forward / AN Anywhere slash Left ( AN Anywhere. Parenthesis Right Parenthesis ) AN Anywhere Minus - AN Anywhere except first Character in a

20 populated field Apostrophe AN Anywhere except first Character in a populated field Comma, AN Anywhere except first Character in a populated field A to Z A to Z AN Anywhere in Alpha or Alpha/Numeric fields a to z a to z AN Anywhere in Alpha or Alpha/Numeric fields 0 to 9 0 to 9 AN, N Anywhere in Numeric or Alpha/Numeric fields Colon : AN Anywhere except first Character in a populated field At AN Anywhere except first Character in a populated field Plus + AN Anywhere except first Character in a populated field Quotation Mark AN Anywhere Question Mark Percentage Sign? AN Anywhere except first Character in a populated field % AN Anywhere except first Character in a populated field TABLE II: Allowable Data Characters. Operators shall note that as the pipe ( ) character is to be used as the field delimiter within records; this character is not permitted as part of a field value and should be omitted if present.