Provincial 9-1-1 Service - About TELUSabout.telus.com/publicpolicy/pdf/TID-02.pdf · This document describes the interfaces between Competitive Local Exchange Carriers ... TELUS Provincial

T E L U S ™

TID-02 November 2007

Provincial 9-1-1 Service

Network-to-Network Interfaces

Between

Competitive Local Exchange Carriers (CLECs)

And

TELUS Communications Company (TCC)

Alberta 911 Network

This document cannot be reproduced without the express permission of TELUS Communications Company Any reproduction, without authorization, is an infringement of TELUS copyright.

Copyright © TELUS Communications

2007 All Rights Reserved

TELUS Communications Company TID-02

TABLE OF CONTENTS

1.0 INTRODUCTION.................................................................................................................................1 1.1 PURPOSE ....................................................................................................................................................... 1 1.2 GENERAL ....................................................................................................................................................... 1

2.0 PROVINCIAL 9-1-1 SERVICE DESCRIPTION..................................................................................2 2.1 NETWORK OVERVIEW.................................................................................................................................... 2

3.0 VOICE NETWORK INTERFACE........................................................................................................3 3.1 PHYSICAL TRUNK INTERFACE........................................................................................................................ 3 3.2 SIGNALLING.................................................................................................................................................... 3

3.2.1 MF 9-1-1 Signalling............................................................................................................................. 4 3.2.2 ISUP (CCS7) 9-1-1 SIGNALLING PROTOCOL............................................................................. 4

3.3 9-1-1 SELECTIVE ROUTER SWITCH SIGNALLING ............................................................................ 6 4.0 DATA NETWORK INTERFACE.........................................................................................................7

4.1 GENERAL ....................................................................................................................................................... 7 4.2 DATA COMMUNICATION WITH THE 9-1-1 MANAGEMENT SYSTEM ................................................................ 7

4.2.1 ACCESS ARRANGEMENT........................................................................................................................ 7 4.2.2 COMMUNICATIONS REQUIREMENTS ...................................................................................................... 7

5.0 CUSTOMER RECORD INFORMATION FILE AND RECORD REQUIREMENTS............................8 5.1 FILE NAMING CONVENTION ........................................................................................................................... 8 5.2 RECORD TYPES ............................................................................................................................................. 8 5.3 HEADER RECORD .......................................................................................................................................... 9 5.4 CUSTOMER TRANSACTION RECORD ........................................................................................................... 10 5.5 TRAILER RECORD ........................................................................................................................................ 11

6.0 ERROR FILES ..................................................................................................................................12 6.1 GENERAL ..................................................................................................................................................... 12 6.2 FILE STRUCTURE ERRORS .......................................................................................................................... 12 6.3 ERROR FILE HEADER RECORD ................................................................................................................... 12 6.4 CUSTOMER TRANSACTION RECORD ERRORS ............................................................................................ 13

6.4.1 Customer Transaction Record Error File Structure ..................................................................... 13 6.4.2 Customer Transaction Record Error Codes ................................................................................. 13 6.5 Error File Trailer Record ...................................................................................................................... 14

6.6 SUMMARY OF ERROR FILE STRUCTURES................................................................................................... 14 6.6.1 File Structure Error Found ............................................................................................................... 14 6.6.2 File Structure OK - Some Customer Transaction Records In Error .......................................... 14 6.6.3 File Structure OK - No Customer Transaction Records In Error ............................................... 14

7.0 ADDITIONAL CUSTOMER TRANSACTION RECORD INFORMATION........................................15 7.1 TRANSACTION CODE (FIELD 1) ................................................................................................................... 15 7.2 TRANSACTION PROCESSING RULES ........................................................................................................... 15

APPENDICES..............................................................................................................................................16 APPENDIX 1 - ADDITIONAL FIELD INFORMATION ..................................................................................................... 17

Acceptable Transaction Record Entries (Field No. 12) ............................................................................... 17 Street Name LBP/LLD (Field 11) .................................................................................................................... 17 Street Name Abbreviations (Field 11)............................................................................................................ 18

November 2007 ii

TELUS Communications Company TID-02 Street Name Range / Township Roads / Highways (Field 11) .................................................................. 18

APPENDIX 2: ERROR CODES................................................................................................................................... 19 APPENDIX 3: GLOSSARY ......................................................................................................................................... 21

November 2007 iii


DOCUMENT HISTORY

------------------------------------------------------------------------------------------------------------------- 1 December 1997 Initial issue as ID-0035 2 December 1999 Issue 2, reissued as TID-02 Issue 1

• Removed references to STENTOR • Changed to Local Service Provider (LSP) to Competitive Local

Exchange Carrier (CLEC) • Removed reference to UNLOCK feature being a future capability • Changed DELETE and UNLOCK validations • Removed customer transaction record error code 203 • Removed references to Entrust/Client™ software and On-Watch ™

service • Added Entrust/Solo™ requirement

------------------------------------------------------------------------------------------------------------------- 3 January 2004 Issue 3

Removed Entrust/Solo™ requirement -------------------------------------------------------------------------------------------------------------------

4 May 2006 Issue 4

• Removed references to single tandem operations and inserted requirements for dual tandem operation

• Changed references from E9-1-1 to 9-1-1 Service • Changed references from TELUS Communications INC (TCI) to

TELUS Communications Company (TCC) -------------------------------------------------------------------------------------------------------------------

5 November 2007 Issue 5

• Modified Section 3.2 to add ISUP Signalling Protocol

• Modified Section 3.3 9-1-1 Selective Router Switch Signalling

• Added Section 7.0 – Transaction Record processing information

November 2007 iv


DISCLAIMER

TELUS Communications Company reserves the right to modify the interface described in this document for any reason including, but not limited to, ensuring that it conforms with standards promulgated by various agencies from time to time, utilization of advances in the state of the technical arts, or the reflection of changes in the design of any equipment, techniques or procedures described or referred to herein. TELUS COMMUNICATIONS COMPANY SHALL NOT BE LIABLE FOR ANY DAMAGES OR INJURIES INCURRED BY ANYONE, INCLUDING BUT NOT LIMITED TO CORPORATIONS, ARISING DIRECTLY OR INDIRECTLY FROM ANY INCOMPATIBILITY BETWEEN THE NETWORK OF TELUS COMMUNICATION AND ANY OTHER NETWORK, OR FROM ANY CAUSE WHATSOEVER. Readers are specially advised that the technical requirements contained herein may change. If further information is required, please contact:

Technology Information Centre 10035 - 102 Ave NW, Floor 6 Edmonton, AB T5J 0E5 Canada Tel: (780) 493-6696 Fax: (780) 428-3686 E-mail: [email protected]: http://www.telus.com/disclosure

November 2007 v

mailto:[email protected]


1.0 Introduction

1.1 Purpose This document describes the interfaces between Competitive Local Exchange Carriers (CLECs) CLEC and the TELUS Communications Company (TCC) network for the purpose of providing Provincial Enhanced 9-1-1 Service (9-1-1). These interfaces allow 9-1-1 calls originating from CLEC customers to be passed through TCC’s network to the appropriate 9-1-1 call answer centre. These interfaces also allow the CLECs to update TCC’s 9-1-1 Management System (9-1-1 MS) with the pertinent calling number and location information of their customers. The interfaces between TCC’s network and 9-1-1 call answer centres or/and Emergency Response Agencies (ERAs) are outside of the scope of this document. Operational issues that deal with interconnection between CLECs and TCC are also outside of the scope of this document. Those issues are dealt with in TCC’s Implementation Support documentation and in special agreements with a particular CLEC.

1.2 General Provincial 9-1-1 Service provides for the transport of all customer dialled 9-1-1 calls to the appropriate municipal 9-1-1 call answer centre, hereinafter referred to as a Public Safety Answering Point (PSAP), and between the PSAP and associated police, fire and ambulance dispatch centres. The municipalities and the various agencies are responsible for answering and responding to these emergency calls. When a CLEC customer dials the digits 9 1 1, the CLEC switches and transports the call to TCC’s designated 9-1-1 tandem switch. The 9-1-1 call is then routed to the appropriate 9-1-1 PSAP, where the 9-1-1 caller’s telephone number, name and address are delivered to the 9-1-1 PSAP operator’s display device. Interconnection by CLECs to TCC’s Provincial 9-1-1 Service is available only within the boundaries of municipalities that have subscribed to the service. CLEC interconnection is accomplished by establishing the following: a) Appropriate trunk-side connections between the CLEC’s end office switch and the

designated TCC receiving 9-1-1 tandem switch; b) The use of Multi-Frequency signalling (MF) or CCS7 ISDN Services User Part (ISUP)

signalling on 9-1-1 trunks to enable the operation of certain features providing call controls; and

c) A data entry facility to enable data transfer between the CLEC’s customer record system and

TCC’s 9-1-1 MS to deliver and retrieve data records, error files, populate and update various 9-1-1 databases with CLEC customer information.

November 2007 1


2.0 Provincial 9-1-1 Service Description In a typical emergency response operation, the 9-1-1 call is delivered to a PSAP where the attendant determines the nature of the emergency and forwards the call to the appropriate fire, police or ambulance dispatch centre. 9-1-1 Service is provided in conjunction with all primary exchange services. Local governments are responsible for the PSAPs and dispatch centres.

2.1 Network Overview TCC Provincial 9-1-1 Service utilizes two networks, voice and data. The voice network is comprised of 9-1-1 tandem switches, 9-1-1 trunks and facilities’ connecting the 9-1-1 tandem switches to PSAPs and emergency response agencies. The data network is comprised of 9-1-1 ALI computers and facilities connecting PSAP display terminals to the 9-1-1 data network. The proper operation of 9-1-1 service is dependent on a number of requirements that must be met prior to service turn-up. These requirements include: • establishment of the interconnecting 9-1-1 trunks to gain access to the Provincial 9-1-1 voice

network; • the collection of customer data from several service order sources (TCC and CLEC systems)

in order to create and maintain a centralized 9-1-1 database; and, • the creation of a selective routing database that is then uploaded to the 9-1-1 tandem switch

in order to route a 9-1-1 call to the correct PSAP.

Figure 1 - TELUS Provincial 9-1-1 Service Diagram

November 2007 2


3.0 Voice Network Interface This section provides details of the interface requirements to interconnect with TCC’s Provincial 9-1-1 service voice network.

3.1 Physical Trunk Interface PSAPs and TCC end offices are connected to both the primary and secondary designated 9-1-1 tandem switches. Where the CLEC has only one switch, interconnections may be required to both TCC 9-1-1 tandem switches, as indicated in the diagram below.

The primary function of the 9-1-1 trunks connecting a CLEC switch to a 9-1-1 tandem switch is to provide the signalling capabilities for the service. These signalling capabilities can be grouped into two main areas: • 9-1-1 protocols between the CLEC switch and TCC’s 9-1-1 tandem switch for call set-up, and • 9-1-1 feature set support.

The trunks that are required to interconnect a CLEC end-office to TCC’s tandem have been filed with the Commission, Tariff Notice 19 as contained in TCC’s Carrier Access Tariff Item 215.4, Local Network Interconnection And Network Component Unbundling.

All 911 trunking, MF and IT ISUP trunks with the E911 option, must carry only 9-1-1 emergency traffic

3.2 Signalling

Provincial 911 Service allows for two types of signalling methods, Multi Frequency and ISUP (CCS7).

November 2007 3


3.2.1 MF 9-1-1 Signalling Any wink-start trunk outgoing from an LSP end-office conforming to “Feature Group C “signalling and capable of spilling ANI can be used to interface with an incoming 9-1-1 trunk at a 9-1-1 tandem switch. The signalling is described in Section 6 of Bellcore Technical Reference TR-TSY-000540, Issue 2, July 1987, (Tandem Supplement to LSSGR), and in Revision 2, June 1990.

EndOffice

E9-1-1tandem

Seizure

Called digitsWink

Off-hook (ANI request)

MF - ANI

Forwarding of

called digits

Figure 2

9-1-1 Signaling Protocol The ANI information is always received as MF signals, and uses Bellcore Standard Format with a single information digit.

e.g. KP + I (single information digit) + 7D (seven-digit DN) + ST (start) where

• I = 0, indicates a valid ANI; • I = 1, indicates an “ONI” (Operator Number Identification) call; • I = 2, indicates an ANI failure.

3.2.2 ISUP (CCS7) 9-1-1 SIGNALLING PROTOCOL

The ISUP (CCS7) signalling requirements are further described in the following Telcordia documents: • GR-2956-CORE, CCS/SS7 Generic Requirements in Support of E9-1-1 Service, describes

the Signalling System No. 7 signalling between the originating switch and the E9-1-1 tandem, and between E9-1-1 tandems. Interworking with this SS7 signalling is also described in this document;

• GR-905-CORE, Common Channel Signalling (CCS) Network Interface Specification

(CCSNIS) Supporting Network Interconnection, Message Transfer Part (MTP), and Integrated Services Digital Network User Part (ISDNUP); and

• GR-1432-CORE, CCS Network Interface Specification (CCSNIS) Supporting SCCP and

TCAP.

Common Channel Signalling No. 7 (CCS7) is the layered CCS protocol used by national and international telecommunications networks to provide highly reliable information transfer with low delay and without loss or duplication of messages. GR-905-CORE and GR-1432-CORE describe the interface protocol and messages expected to

November 2007 4

TELUS Communications Company TID-02 cross the network interface. Specifically, Section 3.1 of GR-905-CORE describes the Message Transfer Part (MTP), Section 3.2 of GR-905-CORE describes the Integrated Services Digital Network (ISDN) User Part (ISDNUP) for non-call related messages, and Section 3.3 of GR-905-CORE describes the ISDNUP for call-related messages. In addition, Section 2 of GR-1432-CORE describes the Signalling Connection Control Part (SCCP), and Section 3 of GR-1432-CORE describes the Transaction Capabilities Application Part (TCAP) portion of the SS7 protocol, which play a role in non-circuit related message exchanges. The following ISUP Signalling Initial Address Message (IAM) parameters are used for wireline trunk-side 9-1-1 interconnection:

IAM Parameter Description IAM Parameter Use

Calling Party 11100000

Calling Party Number Caller’s 10-digit Number (ANI)

Called Party Number 911 or 11

TCC DMS-100 switch emergency services software supports dedicated E911 trunking that uses ISUP signalling protocol on Inter Toll (IT) trunks between an End Office (EO) and the E911 Selective Router switch. The Calling Party Category (CPC) parameter is required for ISUP IT trunks used for E911 calls. The CPC identifies an emergency service call as 11100000. ISUP IT trunks used for E911 calls can support Calling Party Hold; and Ringback when the End Office is a DMS-100 switch, activation for the Calling Party Hold and Ringback features in a DMS-100 E911 Selective Router switch requires the Operator Services Network Capability (OSNC) option assignment to the EO outgoing IT ISUP trunk. When the EO is not a DMS-100 switch, activation for the above features requires EO GR-1277 outgoing IT ISUP trunk compliance.

November 2007 5


3.3 9-1-1 SELECTIVE ROUTER SWITCH SIGNALLING The 9-1-1 Selective Router switches use specific signalling on the trunk from the end office for the following 9-1-1 PERS features: Ringback This feature enables the PSAP call-taker, via the end-office, to:

• ring the phone of the 9-1-1 caller, if it is “on-hook”; or • apply Receiver Off-Hook (ROH) treatment to the line if the phone is “off-hook”.

Called Party Forced Disconnect Allows the PSAP call-taker to force the disconnection of a 9-1-1 call, and thus release the 911 trunk (in case the originator fails to return the phone to the “on-hook” state). When the PSAP attendant goes “on-hook”, the 9-1-1 Selective Router switch sends a disconnect signal to the end-office. Calling Party Disconnect Signal This feature provides the PSAP call-taker with a distinctive tone to indicate that the 911 caller has returned the phone to the “on-hook” position. When the caller goes “on-hook”, the end-office provides an on-hook indication to the 911 Selective Router switch. The Selective Router switch then provides a distinctive tone to the PSAP call-taker.; Called Party Control Provides the PSAP attendant sole control over the disconnection of a 9-1-1 call. The end-to-end connection is maintained until a valid on-hook signal is sent by the call-taker. This prevents the 9-1-1 caller from terminating the call. The Selective Router switch requires an “on-hook” signal from the PSAP to initiate disconnection of the call. If the caller goes “on-hook”, then “off-hook”, and the PSAP attendant has remained “off-hook”, the call must remain connected. The end-office cannot release the call. The end-office must indicate to the 9-1-1 Selective Router switch that the caller has gone “on-hook”, and waits for a disconnect signal from the Selective Router switch before dropping the call. The Selective Router switch will provide the disconnect signal when the PSAP attendant goes “on-hook”, or when the Selective Router switch’s PSAP-disconnect timer expires, whichever comes first.

November 2007 6


4.0 Data Network Interface

4.1 General This interface is intended to transport the CLEC customers’ telephone number and location information for the purpose of updating TCC’s 9-1-1 Management System (9-1-1 MS).

4.2 Data Communication with the 9-1-1 Management System

4.2.1 ACCESS ARRANGEMENT To communicate with the TCC 9-1-1 Management System, the following access arrangement and software are required:

• access to the Internet, either direct or via an Internet Access Provider (ISP) • an e-mail address • an e-mail application • an Internet browser with 128 bit Hyper Text Transfer Protocol Secure (HTTPS)

encryption for manual user menu driven data exchange

and / or

• Microsoft Windows TM operating system with Microsoft Internet Explore TM 5.1 or higher with 128 bit Hyper Text Transfer Protocol Secure (HTTPS) encryption and Windows Scripting Host TM for automated machine to machine data exchange

4.2.2 COMMUNICATIONS REQUIREMENTS

Customer Record files from the CLEC to the 9-1-1 MS as well as Error Return files from the 9-1-1 MS to the CLEC are exchanged through a TELUS 911 secured web site.

The 9-1-1 MS will send an e-mail to notify the CLEC that an Error Return file is available for downloading. The SUBJECT field of the message will contain the file name as described in Section 5.1.

November 2007 7


5.0 Customer Record Information File and Record Requirements This section defines the type of data required, the file formats and the file naming conventions to be used by the CLEC when transmitting customer information to the 9-1-1 MS. Customer Record Information records must only contain standard ASCII upper case characters, digits and symbolic characters (i.e., ASCII codes between 32 and 90 inclusively). No other character will be accepted. Any record containing one or more invalid characters will result in rejection of that record. TCC can process more than one file from each interconnected CLEC on each business day (a day, other than Saturday or Sunday, on which the principal commercial bank of TELUS Communications is open for business during normal banking hours), provided they are in ascending sequence order. If more than one file is sent by a CLEC, each file is validated as to proper structure, and the first file to fail file validation and any remaining sequential files are returned as Error files to that CLEC with Error Code 107. TCC processes all CLEC customer record data files received prior to 8:00 AM Mountain Time (MT) returning error files no later than 4:30 PM MT the same day. Unless otherwise stated all fields that contain data shall be left justified and space filled. Optional fields that do not contain data shall be space filled.

5.1 File Naming Convention Customer record data files shall be named according to the following convention: The filename shall be 8 characters with a 3 character file extension in the format COMPA999.XXX where:

COMPA CLEC ID code of the CLEC as defined by TCC; 999 File Sequence Number (FSN);

FSNs range from 001 to 999. When 999 is reached, the number rolls over to 001. FSNs shall be right justified and zero filled.

XXX File extension indicating the type of file content; DAT Data files from CLEC to 9-1-1 MS ERR Error files from 9-1-1 MS to CLEC Example: AABBC051.DAT

The 51st file sent by CLEC AABBC to TCC for processing. The associated error file produced by the 9-1-1 MS is named AABBC051.ERR.

5.2 Record Types There are three record types used in the 9-1-1 MS. One is for the actual customer information transaction (customer transaction record) and the other two types are header and trailer records used for administrative purposes All Customer Record files shall contain a header record, followed by one or more (quantity X) customer transaction record(s), followed by a trailer record. An error file contains a header record only or a header record followed by one or more (quantity X) failed customer transaction record(s), followed by a trailer record.

November 2007 8


5.3 Header Record The following layout is used for the header record, first record of every Customer Record file.

Field Name Type Length Start Finish Record Type mandatory

Alphabetic “H” for Header Record.

1 1 1

CLEC ID mandatory

Alphanumeric Must match the five-character CLEC ID in the file name.

5 2 6

CLEC Contact optional

Alpha Contact name

15 7 21

CLEC TN mandatory

NPANXXXXXX Contact telephone number

10 22 31

Date and Time mandatory

YYYYMMDDHHMM File creation date/time. Time in 24 hour format

12 32 43

Filler Spaces 204 44 247

Table 1

CLEC File Header Record

November 2007 9


5.4 Customer Transaction Record The customer transaction records shall be inserted in the file by telephone numbers (TN) in numerical order. Where spaces are shown in the field data examples in this section, they shall be interpreted as ASCII Space characters. Customer transaction records shall be separated by either a Carriage Return/Line Feed combination (DOS format) or by a single Line Feed (UNIX format).

Field Field Name Type Length Start Finish1

mandatory Transaction Code Alphabetic

Acceptable characters are “A” for Add, “C” for Change, “D” for Delete and “U” for Unlock.

1 1 1

2 mandatory

NPA Numeric Area Code of telephone number

3 2 4

3 mandatory

NXX Numeric NXX code of telephone number

3 5 7

4 mandatory

Line Numeric Last four digits of telephone number

4 8 11

5 mandatory

Class of Service Alpha Acceptable characters are “R” for Residential, “B” for Business, “C” for Public Coin Telephone, “M” for Mobile telephone, e.g., cellular.

1 12 12

6 optional

Postal Code Alphanumeric 6 13 18

7 mandatory

Customer Name Alphanumeric 63 19 81

8 optional

Apartment No. Alphanumeric 5 82 86

9 optional

House Number Alphanumeric 6 87 92

10 optional

House Suffix Alphanumeric 1 93 93

11 mandatory

Street Name Alphanumeric (Additional information for entering data can be found in Appendix 1)

50 94 143

12 mandatory

Street Type Alphabetic Acceptable types are listed in Appendix 1

7 144 150

13 mandatory

Street VectorSuffix

Alphanumeric Acceptable values are N, S, W, E, SW, SE, NW, NE or space filled if none.

2 151 152

14 optional

Additional Address Information

Alphanumeric 30 153 182

15 mandatory

Municipality Alphanumeric

30 183 212

16 mandatory

Emergency Service Zone (Number)

Numeric Field must be right justified and 0 filled.

5 213 217

17 mandatory

CLEC ID Alphanumeric Must match CLEC ID in file name

5 218 222

18 mandatory

Error Code Alphanumeric Transaction Records from CLEC shall have this field space filled. The 9-1-1 MS uses this field to insert appropriate Error Codes when sending Error Files to the CLEC. Error Codes are listed in Appendix 3, B.

25 223 247

Table 2 - Customer Transaction Record

November 2007 10


5.5 Trailer Record The following record layout is used for the trailer record, last record of every file.

Field Name Type Lengt

h Start Finish

Record Type mandatory

Alphabetic (Acceptable character is “T” for Trailer Record.)

1 1 1

Record Count mandatory

Numeric (Must be right justified and 0 filled. Count shall include only transaction records, i.e., exclude header and trailer records.)

7 2 8


Table 3 - Trailer Record

November 2007 11


6.0 Error Files

6.1 General When an error is detected by the 9-1-1 MS, the erroneous elements are rejected and an error file is created which is sent back to the CLEC. The CLEC is expected to retrieve the error file, correct the error(s) and resend the corrected file to the 9-1-1 MS in a subsequent file transfer.

6.2 File Structure Errors The 9-1-1 MS determines whether the received CLEC Customer Record file can be processed by the following means: • validating the file name; • validating the header and trailer records; • verifying whether the CLEC ID codes in header and file name match; • verifying whether the file sequence number for the file is the one expected; and, • verifying whether the record count in the trailer record matches the number of records

counted by the 9-1-1 MS.

If any of the file structure validations fail, the 9-1-1 MS will respond as follows: • The file will not be processed. • The file sequence count will not be incremented (The CLEC is expected to resend the file

with the same file sequence number after corrections are made). • the 9-1-1 MS will create an error file having the same file name as the received file except

that the file extension is changed from .DAT to .ERR. This file will be returned to the CLEC. • The erroneous file will be deleted from the 9-1-1 MS.

6.3 Error File Header Record If the file structure is found to be in error, The error file header record will contain the following fields:


h Start Finis

h Record Type Alphabetic

“H” for Header Record 1 1 1

TCC Code Alphanumeric Always “TELUS”

5 2 6

TCC Contact Alphanumeric TCC contact name

15 7 21

TCC TN NPANXXXXXX TCC contact telephone number

10 22 31

Date and Time

YYYYMMDDHHMM File creation date/time. Time in 24 hour format

12 32 43

Error Code Numeric Left justified and space filled. Possible Error Codes are listed in Appendix 3 A

15 44 58


Table 4

Error File Header

November 2007 12


6.4 Customer Transaction Record Errors If the file structure is found to be error free, the 9-1-1 MS continues by validating the following mandatory fields in each customer transaction record:

• Transaction Code • NPA • NXX • Line • Class Of Service • Customer Name • Street Name • Street Type • Street Vector Suffix • Municipality • Emergency Service Number • CLEC ID • Error Code

6.4.1 Customer Transaction Record Error File Structure In the event that a validation failure occurs in any of the above fields, the transaction record will be rejected and put in an error file. The error file created for one or more customer transaction record errors will have a header record as described in Section 6.3. The Error field in the header record will contain Error Code value 100. Following the header record will be the failed customer transaction record(s). The customer transaction record format is described in Section 5.4. The error file’s last record will be a trailer record as described in Section 6.5.

6.4.2 Customer Transaction Record Error Codes The last field in the customer transaction record (Error Code) is used to identify where validation errors were found. Character positions 1 through 18 in the Error Code field correspond to the 18 fields in the customer transaction record. Character positions 19 through 22 are reserved for future use. Character positions 23 through 25 are used together as a three-character error code to indicate processing errors that are found after fields have been validated. The structure and error codes used in the Error Code field are given in Appendix 2.

November 2007 13


6.5 Error File Trailer Record The following record layout is used for the trailer record, i.e., last record of every error file.


h Start Finish

Record Type Alphabetic (“T” for Trailer Record) 1 1 1 Records Processed

Numeric Right justified, 0 filled. Count of transaction records processed, excluding header and trailer records.

7 2 8

Filler Space 1 9 9 Records in Error Numeric

Right justified, 0 filled. Count of transaction records that failed validation, excluding header and trailer records.

7 10 16


Table 5

Error File Trailer Record

6.6 Summary Of Error File Structures This section provides a summary of error file structure that will be returned to the CLEC by the 9-1-1 MS.

6.6.1 File Structure Error Found 1. Header record (Section 6.3) with error code (Appendix 2). 2. No customer transaction records or trailer record. Entire file must be resent by the CLEC keeping the same file sequence number.

6.6.2 File Structure OK - Some Customer Transaction Records In Error 1. Header record (Section 6.3) with error code 100. 2. Customer Transaction Records in error with Error Code field information (Appendix

2). 3. Trailer Record (Section 6.5).

6.6.3 File Structure OK - No Customer Transaction Records In Error 1. Header record (Section 6.3) with error code 100. 2. No Customer Transaction Records. 3. Trailer record (Section 6.5).

November 2007 14


7.0 Additional Customer Transaction Record Information

7.1 Transaction Code (Field 1) TCC will accept four transaction types. These are:

• ‘A’ Add – adds a customer record providing the telephone number does not already

exist.

• ‘C’ Change – changes an existing customer record (except the TN: fields NPA, NXX, and Line) providing the existing TN’s LSP ID matches the TN and LSP ID in this customer transaction record.

• ‘D’ Delete – deletes an existing record providing the existing TN’s LSP ID matches the

TN and LSP ID in this customer transaction record.

• ‘U’ Unlock – used in place of a ‘D’ transaction code when a telephone number is migrating to another CLEC. In all other respects it must contain the same information as is required for the ‘D’ transaction

Regardless of the type of transaction record (A, C, D or U), all data fields must be filled with the appropriate information.

7.2 Transaction Processing Rules This section describes how the transactions are processed by TCC. No field validation is done on Unlock or Delete transactions since data is not going to be modified or added. Valid transactions are gathered from all CLEC files submitted prior to the time of the 9-1-1 MS transaction processing job into a single list. The list is sorted by Transaction Code and order of entry in the CLEC transaction files. No file order preference is given to any one CLEC. The transactions are then processed in batches grouped by Transaction Code in the following order:

1. Unlocks 2. Deletes 3. Adds 4. Changes

Transaction processing adheres to the following rules:

• When processing an Unlock transaction, if the TN does not exist or the TN is already

unlocked, the transaction is considered successful and no error is returned.

• When processing a Delete transaction, if the TN does not exist, the transaction is considered successful and no error is returned.

• When processing an Add transaction, if the TN already exists and is owned by the LSP

ID of the transaction, the transaction is processed as a Change and no error is returned.

• When processing a Change transaction, if the TN does not exist, or the TN is unlocked, the transaction is processed as an Add and no error is returned.

November 2007 15


Appendices The information in these appendices is subject to frequent change and is provided for illustration purposes only.

November 2007 16


Appendix 1 - Additional Field Information

Acceptable Transaction Record Entries (Field No. 12)

For Roadway Type

Street Type For Roadway Type

Street Type For Roadway Type

Street Type

ABBEY ABBEY GLADE GLADE PATHWAY PTWAY ACRES ACRS GLEN GLEN PINES PINES ALLEY ALLEY GREEN(S) GRN PLACE PL AVENUE AV GROUNDS GRNDS PLATEAU PLAT BAY BAY GROVE GROVE PLAZA PLAZA BEACH BCH HARBOUR HARBR POINT PT BEND BEND HEATH HEATH PORT PORT BOULEVARD BLVD HEIGHTS HTS PRIVATE PVT BYPASS BYPASS HIGHLANDS HGHLDS PROMENADE PR BYWAY BYWAY HIGHWAY HWY QUAY QUAY CAMPUS CAMPUS HILL HILL RANGE RNG CAPE CAPE HOLLOW HOLLOW RIDGE RDGE CENTRE CTR ISLAND ISLAND RISE RISE CHASE CHASE KEY KEY ROAD RD CIRCLE CIR KNOLL KNOLL ROUTE RTE CLOSE CL LANDING LANDING ROW ROW COMMON COMMON LANE LN RUN RUN CORNER(S) CRNR LIMITS LMTS SQUARE SQ COURT CRT LINE LINE STATION STN COVE COVE LINK LINK STREET ST CRESCENT CR LOOKOUT LKOUT TERRACE TERR CROSSING CROSS LOOP LOOP THICKET THICK DALE DALE MALL MALL TOWERS TOWERS DELL DELL MANOR MNR TRAIL TR DOWNS DWN MAZE MAZE VALE VALE DRIVE DR MEADOW(S) MDW VIA VIA END END MEWS MEWS VIEW(S) VW ESPLANADE ESPL MOOR MOOR VILLA VILA ESTATES EST MOUNT MT VILLAGE VILGE EXPRESSWAY EXPY MOUNTAIN MTN VILLAS VILA FIELD FIELD ORCHARD ORCH VISTA VISTA FOREST FOREST PARADE PARADE WALK WLK FREEWAY FWY PARK PK WAY WY FRONT FRT PARKWAY PKY WHARF WHARF GARDEN(S) GDN PASS or

PASSAGE PASS WOOD(S) WOOD

GATE GATE PATH PATH WYND WYND Note: If there is no Street Type in the address space fill the Street Type field.

Street Name LBP/LLD (Field 11) Not all municipalities in Alberta have implemented civic type addressing. As a result, areas exist where Lot/Block/Plan and/or Legal Land (quarter sections) are used to locate 9-1-1 callers. For these areas, TCC has implemented the following addressing formats:

• legal land description (LLD), e.g., SW 33 51 26 W4 • legal subdivision, e.g., 6 33 51 26 W4

November 2007 17


• lot block plan (LBP), • full LBP, e.g., 1345 112 556AB (Lot No. 1345, Block No.112, Plan No.556AB) • partial LBP, e.g., LT112333PL1231112 (Lot No. 112333, Plan No. 1231112) • partial LBP, e.g., BK4444PL123112 (Block No. 4444, Plan No. 123112)

When an LBP is used, the LLD shall be included as part of the street name. The LLD shall be added to the LBP in the format LBP / LLD. E.g., 1345 112 556AB / SW 33 51 26 W4, LT112333PL1231112 / SW 33 51 26 W4, etc.

Street Name Abbreviations (Field 11) The following abbreviations are used by TCC in the Street Name field if the ‘full name’ is included in the street name. It is recommended that CLECs use the same abbreviations.

FULL NAME ABBREVIATION FORT FT HIGHWAY HWY LAKE LK MOUNT MT MOUNTAIN MTN NUMBER NO POINT PT PRINCE PR SAINT ST SECONDARY HIGHWAY SH

Table 6 Street Name Abbreviations

Street Name Range / Township Roads / Highways (Field 11) Some rural municipalities in Alberta have chosen a Range Road / Township Road addressing system. Following are address examples showing the use of the appropriate address fields. TCC abbreviates Range Road to RNG RD, Township Road to TWP RD, Highway to HWY and Secondary Highway to SH.

• If the address is 123 20452 Township Road 515 the House Number field would be 123 and

the Street Name field would be 20452 TWP RD 515. (Street Type field is space filled)

• If the address is 20452 Township Road 515 the House Number field would be blank and the Street Name field would be 20452 TWP RD 515. (Street Type field is space filled)

• If the address is 123 20452 Range Road 515 the House Number field would be 123 and the

Street Name field would be 20452 RNG RD 515. (Street Type field is space filled) • If the address is 20452 Range Road 515 the House Number field would be blank and the

Street Name field would be 20452 RNG RD 515. (Street Type field is space filled) • If the address is 20452 Highway 14 the House Number field would be blank and the Street

Name field would be 20452 HWY 14. (Street Type field is space filled)

• If the address is 20452 Secondary Highway 14 the House Number field would be blank and the Street Name field would be 20452 SH 14. (Street Type field is space filled)

November 2007 18


Appendix 2: Error Codes The Error Codes in this Appendix are subject to change from time to time. Error codes are only used by the 9-1-1 MS when sending Error Files to the CLEC. Error fields are left justified and space filled. Spaces shown in field data examples below shall be interpreted as ASCII space characters.

A. Error File Header Record Error Codes Error Code Description

100 No Errors Found In File Structure. 101 Invalid File Name 102 Header Record not found or invalid Header Record format. 103 Trailer Record not found or invalid Trailer Record format. 104 CLEC ID in header record does not match CLEC ID in file name

105XXXXXX File sequence number is not the one expected by the 9-1-1 MS. Example: 105 476 458 105 indicates the error type 476 indicates the file sequence number received 458 indicates the file sequence number expected

106XXXXXXXX Actual transaction record count does not match the record count in the trailer record. Example: 106 23876 45678 106 indicates the error type 23876 indicates the transaction record count given in the trailer record 45678 indicates the number of transaction records in the file counted by the 9-1-1 MS

107 Used in cases where a CLEC has sent more than one file per day. The additional files will not be processed but returned to the CLEC with this this error code. Files should be re-submitted on the following business days at a rate of one file per day.

B. Error File Transaction Record Error Codes (Field No. 18, Character Positions 1 through 25)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

0 or 1

0 or 1

0 or 1

0 or 1

0 or 1

0

0 or 1

0

0

0

0 or 1

0 or 1

0 or 1

0

0 or 1

0 or 1

0 or 1

0 or 1

0

0

0

0

2

0

X

Validation for Transaction Record Fields 1 through 18 a) Fields for which the position is filled with “0” (i.e., Fields No. 6, 8,

9, 10, and 14) are not validated. Field content is optional. b) A “0” in another character position means the field passed validation. c) A “1” in another character position means the field failed validation.

Fields are not used at this

time.

see specific

Error Codes below

Error Code

Character Position Description23 24 25 2 0 0 Invalid Add record, TN already exits in 9-1-1 database 2 0 1 Invalid Change record, No TN found in 9-1-1 database 2 0 2 Invalid Delete record, TN not found in 9-1-1 database 2 0 3 Spare 2 0 4 CLEC ID in transaction record does not match CLEC ID in the header file. 2 0 5 CLEC ID in transaction record did not match CLEC ID in existing customer record

November 2007 19

TELUS Communications Company TID-02 Note: Transaction files sent to the 9-1-1 MS must have Field No. 18 space filled.

November 2007 20


Appendix 3: Glossary

ALI Automatic Location Identification Information regarding the location associated with the caller's telephone number. ANI Automatic Number Identification Caller’s telephone number. ASCII American Standard Code for Information Interchange. CLEC Local Service Provider Provider of local telephone service; includes ILEC’s, CLECs and Resellers CSG Carrier Services Group 9-1-1 MS 9-1-1 Management System Complete set of processes, databases and supportive hardware that form the data

sub-network of TCC’s Provincial 9-1-1 Service. ERA Emergency Response Agency (e.g., police, fire department, ambulance) ESN Emergency Service Number

Number of an Emergency Service Zone (ESZ). ESZ Emergency Service Zone (ESZ) defined by a unique set of one PSAP and one or

more Emergency Response Agencies (ERAs). FSN File Sequence Number

Number assigned to Customer Record Information and Error Return files. ILEC Incumbent Local Exchange Carrier LBP & LLD Lot/Block/Plan & Legal Land Designation Location Identification coding for rural areas used instead of Street Name CLEC Local Service Provider LNP Local Number Portability NPA Numbering Plan Area The three-digit area code according to the North American Numbering Plan (NANP). NXX Network Exchange Code The first 3 digits of a 7-digit Telephone Number. ONI Operator Number Identification. PSAP Public Safety Answering Point The answering location for 9-1-1 calls originating within a specified area. TCC TELUS Communications Inc.

November 2007 21

Documents

Provincial 9-1-1 Service - About TELUSabout.telus.com/publicpolicy/pdf/TID-02.pdf · This document describes the interfaces between Competitive Local Exchange Carriers ... TELUS Provincial