BellSouth E911 User Manual

0 (0)

Customer Guide

CG-EWCG-001

Issue 3, January 6, 2004

Wireless E911 Guide

Wireless E911 Guide	CG-EWCG-001
Copyright	Issue 3, January 6, 2004

April, 2002 - January 6, 2004

Page ii

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Table of Contents

	Contents
Subject		Page
Introduction / Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		vii
	Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	vii
	Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	vii
1.	Overview of E911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	1
1.1	Definition of E911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	1
1.1.1	Selective Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	1
1.1.2	Automatic Number Identification (ANI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	1
1.1.3	Automatic Location Identification (ALI) . . . . . . . . . . . . . . . . . . . . . . . . . . . .	1
1.1.4	Premises Based ALI Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	2
1.2	PSAP Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	2
1.3	Databases Required to Support E911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	3
1.4	Master Street Address Guide (MSAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	3
1.5	Telephone Number (TN) Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	3
1.6	E911 Tandem / Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	4
1.7	Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	5
1.8	Database Escalation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	8
1.8.1	Access To NDSC Analysts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	8
1.8.2	Level One Escalation: Intrado . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	8
1.8.3	Level Two Escalation: Intrado . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	8
1.8.4	Level Three Escalation: Bellsouth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	8
2. Coordination of Wireless Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . .		9
2.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	9
2.2	Coordination Process: Wireless Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	9
2.3	Coordination Process: BST Wireless Account Team . . . . . . . . . . . . . . . . . . . . . . .	10
2.4	Coordination Process: BST Wireless E911 Implementation Manager . . . . . . . . . . . .	10
2.5	Coordination Process: Mobile Position Center Provider . . . . . . . . . . . . . . . . . . . . .	11
2.5.1	Steps for Establishment/Change of Mobile Position Center Provider . . . . . . . . . . .	11
2.5.2	Initial Establishment of Mobile Position Center Provider . . . . . . . . . . . . . . . . . .	12
2.5.3	Change of Mobile Position Center Provider . . . . . . . . . . . . . . . . . . . . . . . . . . .	12
2.5.4	Information Required for Phase 2 MPC/GMLC Circuits to the ALI Hosts . . . . . . .	12
2.5.5	Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	13
3.	Network Specifications and Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	15
3.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	15
3.2	Specifications & Ordering Process: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	15
3.2.1	Option 1: BellSouth NORTEL Solution Carring Phase 1 Data Only (CBN & pANI)	15
3.2.2	Specification & Ordering Process: Option 2: Third Party Vendor Solution . . . . . . .	16
3.3	Wireless Carrier Owned Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	16
3.3.1	Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	16
3.3.2	Data Connections Required For Wireless Carrier Owned Hardware - Phase 1 Only .	17
3.4	Wireless Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	17

Page iii

Wireless E911 Guide	CG-EWCG-001
Table of Contents	Issue 3, January 6, 2004

3.5	Interface Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	18
4. MSAG Maintenance and ESN Assignment . . . . . . . . . . . . . . . . . . . . . . . . . .		19
4.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	19
4.2	ESN Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	19
4.3	MSAG Maintenance and Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	20
5. TN Database Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		23
5.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	23
5.2	TN Database Daily Updates: Wireless Carrier Responsibilities . . . . . . . . . . . . . . . .	24
5.3	E911 Customer Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	26
5.4	Instructions for NXX Table Update Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	27
5.5	NXX Table Update Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	29
5.6	MSAG Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	30
5.6.1	Correct Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	30
5.6.2	Incorrect Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	30
5.7	Standard Street Suffix (Thoroughfare) Designations / Directionals . . . . . . . . . . . . . .	31
5.7.1	BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) . . . . . . . . . . . . . . .	31
5.8	Standard Location Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	32
5.9	Updating the TN Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	33
5.10	Service Order Interface File Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	34
5.11	SOIR File Data Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	34
5.11.1	Table: SOIR File Data Record - BellSouth 512 Character Format for Data Exchange	34
5.12	SOIR File Header Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	40

5.12.1Table: SOIR File Header Record - BellSouth 512 Character Format for Data

	Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	40
5.13	SOIR File Trailer Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	40
5.13.1	SOIR File Trailer Record - BellSouth 512 Character Format for Data Exchange . . .	40
5.14	Mechanized File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	41
5.15	Mechanized File Confirmations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	41
6. TN Errors and Corrective Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		43
6.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	43
6.2	Electronic Error Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	43
6.2.1	The Confirmation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	43
6.2.2	The Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	46
6.2.3	Distribution of Daily Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	47
6.2.4	TN Error Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	48
6.3	Error Codes and Error Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	48
6.4	Error Code and Corrective Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	50
6.5	Compiled Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	58
7. PSAP Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		59
7.1	Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	59
7.2	PSAP Inquiry Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	60
7.3	PSAP Inquiry Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	61
7.3.1	Instructions for Completing PSAP Inquiry Log . . . . . . . . . . . . . . . . . . . . . . . .	61
7.4	Inquiry Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	62
7.5	Investigation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	62

Page iv

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Table of Contents

7.5.1	ALI Record Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		62
7.5.2	Wrong ALI Display Of: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		62
7.5.3	Address — Community — Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		62
7.5.4	ESN .	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	63
7.5.5	Misroutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		63
7.6	Blank Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		63
7.6.1	PSAP Inquiry Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		64
8. No Record Found (NRF) Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .			65
8.1	Overview	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	65
8.2	No Record Found (NRF) Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		65
8.3	No Record Found (NRF) Report Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		65
8.4	No Record Found (NRF) Report Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		66
8.5	NRF Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		66
9. NENA Company Registration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . .			69
9.1	NENA Cmpany ID Registration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		69
9.2	Purpose of the NENA Company ID Registration Service . . . . . . . . . . . . . . . . . . . .		69
9.3	Use of the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		70
9.4	Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		70
9.4.1	Input Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		70
10. Reconciliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .			73
10.1	Overview	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	73
10.2	Notification and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		73
10.3	. . . . . .	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	73
Appendix A.		BellSouth Wireless E9–1–1/SS7 Interconnection Guide . . . . . . . .	75
A.1	BellSouth Wireless E-9–1–1/SS7 Interconnection Guide . . . . . . . . . . . . . . . . . . . .		75
A.2	Executive Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		75
A.2.1	Identified Options: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		76
A.2.1.1	Call Scenario 1, ESRK Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		76
A.2.1.2	Call Scenario 2, CBN and ESRD Delivery - WITHOUT a hybrid: (WITHOUT a		77
	hybrid architecture at the Selective Router) . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1.3	Call Scenario 2, CBN and ESRD Delivery - WITH a hybrid: (WITH a hybrid		77
	architecture at the Selective Router) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1.4	Call Scenario 3, CBN, ESRD and GLP Delivery: (GLP = Geodetic Location		77
	Parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.2	Database Steering Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		78
A.3	Scope and introductory text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		78
A.3.1	Wireless E9-1-1 Service Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		78
A.4	Reason for Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		79
A.5	Organization of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		79
A.6	Wireless CCS Network Interconnection Architecture . . . . . . . . . . . . . . . . . . . . . . .		81
A.6.1	General Interconnection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		81
A.6.2	Wireless Phase 1 vs. Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		81
A.7	Interface Protocol for Wireless Call Setup when using SS7/ISUP signaling. . . . . . . .		83
A.7.1	Calling Party Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		83
A.7.2	Calling Party Number Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		84

Page v

Wireless E911 Guide	CG-EWCG-001
Table of Contents	Issue 3, January 6, 2004

A.7.3	Generic Digits Parameter & GDP Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	84
A.7.4	Charge Number Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	85
A.7.5	Calling Party Category Parameter (CPC, aka: CPCat) . . . . . . . . . . . . . . . . . . . .	85
A.7.6	Originating Line Information Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	85
A.8	Cross Reference Tables to J-STD-036-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	86
A.8.1	Wireline Compatibility Mode (NDET uses signaling option E911_STD) . . . . . . . .	86
A.8.2	ISUP Initial Address Message Parameter Contents for NCAS (NDET uses signaling
	option WRLS_STD, because MSC can support GDP) . . . . . . . . . . . . . . . . . . . .	87
A.8.3	ISUP Initial Address Message Parameter Contents for NCAS (NDET uses signaling
	option WRLS_CLD because MSC cannot support GDP) . . . . . . . . . . . . . . . . . .	88
A.8.4	ISUP Initial Address Message Parameter Contents for CAS . . . . . . . . . . . . . . . .	90
A.9	Cross Reference Tables to NENA TID 05-501 - SS7 Guidelines for MSC to Selective
	Router Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	91
A.9.1	Call Scenario 1: ESRK Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	92
A.9.2	8.2 Call Scenario 2: CBN and ESRD Delivery . . . . . . . . . . . . . . . . . . . . . . . . .	92
A.10 Attachment "A" - CPCat & OLI Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		94
A.10.1	Calling Party Category parameter (CPC): . . . . . . . . . . . . . . . . . . . . . . . . . . . .	94
A.10.2	Originating Line Parameter (OLI): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	94
A.11 Attachment "B" - Wireless Customer Questions & Answers: . . . . . . . . . . . . . . . . . .		95
A.11.1	Why is BellSouth issuing this document? . . . . . . . . . . . . . . . . . . . . . . . . . . . .	95
A.11.2	Do I have to change my existing trunks to SS7? . . . . . . . . . . . . . . . . . . . . . . . .	95
A.11.3	Will this let me deliver ESRDs/ESRKs from more than one NPA on the SS7 trunk
	group? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	95
A.11.4	Will this let me reduce the number of trunk groups I have in place? . . . . . . . . . . .	95
A.11.5	What if I don’t have SS7 signaling "A" link connectivity to support trunking to the
	appropriate NDET? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	96
A.11.6	What do I do for Continuity Testing on these SS7 trunks? . . . . . . . . . . . . . . . . .	96
A.12 11.0 Attachment "C" - Wireless Customer Checklist . . . . . . . . . . . . . . . . . . . . . . .		96

Page vi

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Introduction / Revision History

Introduction / Revision History

Purpose

This document addresses Wireless E911.

Version Information

Added SS7/ISUP signaling option for trunking between the MSC and E911 tandems. Added Appendix A.

Page vii

8 Page

Table A Revision History

Chapter	Action	Date / Issue	Description	Change
	Request			Requested By /
	#			Made By

All	N / A	January 6, 2004 /	Added SS7/ISUP signaling	Tom Breen / Bill
		3	option for trunking between	Marczak / Mike
			the MSC and E911 tandems.	Harfield
			Added Appendix A.

MSAG Maintenance	N / A	May 22, 2003 / 2b	Revised SOIR File Data	Rosemary Parker /
and ESN Assignment			Record Layout Table to	Mike Harfield
			show "Sent to PSAP" field
			footnotes in table column.

Overview of E911;	N / A	April 3, 2003 / 2a	Overview of E911: Added	Genia Harris /
Coordination			"GMLC" Term, Changed	Mike Harfield
of Wireless			contact for "Level One
Interconnection;			Escalation: Intrado".
Network			Coordination of Wireless
Specifications and			Interconnection: Added
Ordering			"Coordination Process:
			Mobile Position Center
			Provider"
			Network Specifications and
			Ordering: Added "Wireless
			Phase 2".

TN Database Updates	N / A	January 8, 2003 /	Corrected FAX numbers.	Rosemary Parker /
		2		Mike Harfield

TN Database Updates	N / A	December 2, 2002	Added step in TN Database	Rosemary Parker /
and PSAP Inquiries		/ 1c	Daily Updates: Wireless	Mike Harfield
			Carrier Responsibilities and
			changed address in Inquiry
			Flow for INTRADO.

		- continued -

Revision / Introduction	Guide E911 Wireless
History

6, January 3, Issue	EWCG-CG
2004	001-

Table A Revision History (continued)

Chapter	Action	Date / Issue	Description	Change
	Request			Requested By /
	#			Made By

All	N / A	July 15, 2002 / 1b	Revisions to sections	Rosemary Parker /
			entitled, "Overview of	Mike Harfield
			E911", "Coordination of
			Wireless Interconnection",
			and "Network Specifications
			and Ordering".

Various	N / A	June 20, 2001 / 1a	General revisions to section	Rosemary Parker /
			entitled "TN Errors and	Mike Harfield
			Corrective Action"

All	N / A	April 4, 2002 / 1	Initial Issue	Rosemary Parker /
				Mike Harfield

9 Page

6, January 3, Issue	001-EWCG-CG
2004

History Revision / Introduction

Guide E911 Wireless

Wireless E911 Guide	CG-EWCG-001
Introduction / Revision History	Issue 3, January 6, 2004

Page 10

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Overview of E911

1.Overview of E911

1.1Definition of E911

"911" has been designated in the United States as the number to be used by the public to summon emergency aid or to report a crime, fire or accident. Its main purpose is to make it easier for people in time of emotional stress to contact the proper emergency agency. An important advantage of 911 emergency service is improved (reduced) response time.

The original 911 service, known as Basic 911 (B911), routes a call to one centralized answering location. The attendant at the answering location obtains the pertinent information that identifies the call and the caller’s need. The attendant then determines the appropriate agency and dials the number to transfer

the caller to that agency.

Enhanced 911 service, or E911, is a full featured electronic system that provides three (3) major enhancements to Basic 911 service:

1.1.1Selective Routing

Electronically routes 911 emergency calls to the proper Public Safety Answering Point (PSAP) based on the Emergency Service Number (ESN) code that has been assigned to the cell site address or the longitude/latitude of the caller’s location. This may be accomplished by assigning "pseudo-ANI" telephone numbers to each face of each antenna in order to designate a fixed location for the serving area. Some wireless solutions allow the assignment of a pseudo-ANI telephone number to a specific PSAP rather than an antenna face. An ESN is assigned to the "pseudo-ANI" telephone numbers during database record processing and is assigned from the Master Street Address Guide (MSAG) based on the address. Some solutions may dynamically assign the ESN based upon the longitude/latitude of the caller’s location. Wireless Carriers must work with the local governmental agencies and agree on call routing, ESN assignments, and MSAG valid addresses. This process is described later in this document. Wireless Carriers should identify selective routing capabilities for premises based ALI systems and make arrangements to deliver wireless calls directly to the PSAP in those cases where selective routing is not utilized. See Premises Based ALI Systems below.

1.1.2Automatic Number Identification (ANI)

Provides the PSAP with the 7-digit pseudo-ANI telephone number representing the antenna face which received the wireless 9-1-1 call or the pseudo-ANI PSAP routing number, depending on the wireless solution implemented. Interfaces utilizing Feature Group D signaling between the E911 selective routing tandem and the PSAP may be capable of sending 10-digit ANI or 10-digit ANI and 10-digit call back number to the PSAP. Pseudo-ANI numbers must be assigned from the wireless carrier’s number range and must be geographically valid for the E911 selective routing tandem service area.

1.1.3Automatic Location Identification (ALI)

Provides the PSAP with cell site location information associated with the pseudo-ANI. Phase 1 compliance also requires ALI to contain the wireless subscribers call back number. This may be accomplished by the

Page 1

Wireless E911 Guide	CG-EWCG-001
Overview of E911	Issue 3, January 6, 2004

wireless carrier providing a real-time update to the ALI databases during 9-1-1 call processing. Phase 2 requires both of the data elements provided in Phase 1 plus the longitude and latitude of the caller’s

location when they dialed 9-1-1. BellSouth supports E2 connectivity between MPCs and the ALI database hosts as defined in BellSouth Technical Reference TR73610, Issue 2. BellSouth will deliver the lat / long data to the PSAP in the ALI response message as described in BellSouth Technical Reference TR73528, Issue 6. Wireless Carriers must ensure dynamically updated records will comply with TR73528 when delivered to the PSAP. These Technical References may be found on the following web site:

Note: To receive the maximum benefit of E911, the initial ALI database record must be assigned an MSAG valid address even if the tower is located in a rural area. MSAG valid addresses are obtained from the addressing authority in the E911 area where the cell site is located.

1.1.4Premises Based ALI Systems

Premises based ALI systems may have a separate database, software, and hardware located on the E911 Customer premises. Wireless Carriers must identify all premises based systems in their service areas and comply with any special data or interface requirements. Carriers should meet with PSAPs to determine if selective routing or direct trunking is used to deliver 911 calls. If calls are not selectively routed to

premises based ALI systems, the carrier may need to deliver wireless 911 calls to the PSAP administrative lines or use other arrangements as negotiated with the PSAP. This guide does not address issues related to premises based ALI systems.

1.2PSAP Display

The PSAP display for the ANI and ALI has been configured so that the PSAP attendant can immediately recognize from the English Language Translations (ELT) that the call is being made from a wireless device. The ALI response may contain the cell site sector location, subscriber call back number, and lat/long when available. An example of a typical PSAP display is shown. This screen/display will vary based on which PSAP equipment is chosen by the E911 Customer.

Page 2

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Overview of E911

1.3Databases Required to Support E911

Three (3) data files (or databases) are required to provide the data for display at the PSAP:

•Master Street Address Guide (MSAG)

•Telephone Number (TN) Database

•E911 Tandem/Network Information (TN/ESN)

1.4Master Street Address Guide (MSAG)

The MSAG contains all street information in the full featured E911 service area. The Emergency Service Numbers (ESNs) are assigned to the streets for routing 911 calls to the proper PSAP. As data records for the pseudo-ANI telephone numbers are processed from the wireless carriers, the address information on the data record is validated against the MSAG. Address information on the data records must exactly match the MSAG information or the data records will be considered an error and returned to the wireless carrier for correction. Data records are not posted to the database until they pass validation.

1.5Telephone Number (TN) Database

The TN database contains all of the wireline subscriber records and wireless pseudo-ANI records for all carriers in the E911 service area. This information includes the telephone number, name of the wireline subscriber, address, location, class and type of service. For the wireless carrier, it includes the pseudo-ANI

Page 3

Wireless E911 Guide	CG-EWCG-001
Overview of E911	Issue 3, January 6, 2004

telephone number which has been assigned by the carrier, the carrier name, and the MSAG valid address of the cell site sector location. A full description of the data fields in the TN database may be found inTN Database Updates.

The TN database is updated by the wireless carrier on an ongoing basis as new pseudo-ANI numbers are assigned or when existing information changes. This includes changes in antenna face coverage area when it impacts routing of 911 calls to the appropriate PSAP. The data record which is sent by the wireless carrier is validated against the MSAG for an exact address match and is assigned the appropriate ESN which is loaded into the E911 host database and the E911 tandem routing database. Details for providing TN data to the E911 host is explained later in this document. Some wireless solutions will dynamically update the cell site location, call back number, longitude, and latitude during 911 call processing. Wireless carriers are still required to provide "static" pseudo-ANI data records to the E911 host with MSAG valid addresses. These "static" records will be dynamically updated during 911 call processing. The cell site location information provided during the dynamic updates are not validated against the MSAG, but the original "static" record provided in the SOIR process will be validated and must contain MSAG valid information.

Wireless Carriers must provide valid data records for inclusion in the TN database prior to testing or activating service. If data records are not posted to the TN database, the PSAP will receive a "NO RECORD FOUND" display when subscribers dial 911 which may delay getting them the emergency services they need.

1.6E911 Tandem / Network Information

Interconnection arrangements to the E911 tandem are negotiated with the wireless carrier’s BST Interconnection Services Account Representative. The wireless carrier must provide a minimum of two

(2) Type 2C redundant trunks to the E911 tandem office(s) that will serve the Mobile Switching Center (MSC). Additional facilities may be required depending on the technical solution used to dynamically pass the wireless call back number and longitude/latitude to the ALI database. Data circuits must exist between MPCs and the ALI database hosts for the E2 interface required for Phase 2.

Determining the proper PSAP to route wireless 911 calls must be negotiated between the wireless carrier and the E911 Coordinators in the serving areas. This must also include the proper PSAP to receive the wireless 911 call in the event of an ANI (pANI) failure from the MSC. All 911 calls will default route to the negotiated PSAP when an ANI (pANI) failure occurs. E911 Coordinators must agree on the PSAP to receive these calls. Once agreement has been reached with the E911 Coordinators, the wireless carrier will notify the BST Interconnect Account Representative of the PSAP location for default routing. This will allow for BST to establish the necessary translations in the E911 tandem office. The BST Interconnect Account Representative may assist the wireless carrier in identifying which E911 tandem office should be used to route calls to a specific PSAP.

Page 4

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Overview of E911

1.7Glossary of Terms

	Table B Glossary of Terms

Term	Definition

ACAC	Access Carrier Advocacy Center

Address Verification	A form issued by each telco to refer and resolve address
Request (AVR)	discrepancies with the E911 Customer.

ALEC	Alternative Local Exchange Carrier

Alternate Routing	A standard feature provided to allow E911 calls to be routed to a
	designated alternate location if :
	1. all E911 trunks to the primary PSAP are busy OR
	2. the primary PSAP closes down for a period. (i.e. night service)

Automatic Location	A feature by which the address associated with the telephone
Identification (ALI)	number (ANI or pANI) is forwarded to the PSAP for display.

Automatic Number	The telephone number assigned by the wireless carrier to the cell
Identification (ANI)
	face or PSAP. Also known as Pseudo-ANI and Emergency Service
	Routing Digits (ESRD).
	Note: The pseudo-ANI number MUST be assigned from the
	wireless carrier number pool and be geographically correct for the
	serving area.

BST	BellSouth Telecommunications, Inc.

Call Back Number	Telephone number PSAP will use to dial the 911 caller in the event
	the call is disconnected. Also known as wireless Mobile Directory
	Number (MDN), Wireless Subscriber ANI (WS-ANI) and Calling
	Party Number (CPN).

Call Through Testing	The process of testing the network, equipment and database
	associated with an E911 system prior to the final cutover.

CMRS	Commercial Mobile Radio Service

CSU	Channel Service Unit

DSU	Data Service Unit

E2 Interface	The TIA / EIA / J-STD-036 E2 interface utilized to provide phase
	2 location information to the ALI database from the MPC. Refer
	to BellSouth TR73610, Issue 2.

E911 Customer	A governmental agency responsible for providing public safety and
	purchasing 911 service.

	- continued -

Page 5

Wireless E911 Guide	CG-EWCG-001
Overview of E911	Issue 3, January 6, 2004

	Table B Glossary of Terms (continued)

Term	Definition

E911 Tandem Central	The central office designated for a geographical area to receive end
Office Switch	office E911 calls and route to the appropriate PSAP.

Emergency Service	A number associated with the geographical area served by the same
Number (ESN)	fire, police and ambulance districts.

Emergency Service	See ANI or pANI
Routing Digits
(ESRD)

End Office	The central office switch receiving E911 calls from subscribers.
	For wireless, this would be the MSC.

FCC	Federal Communications Commission

FOC	Function of Change

GMLC	(see MPC)

ICO	Independent Telephone Company

Integrated Services	A message protocol to support call set up and release for interoffice
Digital Network User	voice call connections over SS7 signaling.
Part (ISUP)

Intrado	A vendor designated by BST to handle E911 data maintenance
	(formerly SCC)

LOC	Location

Master Street Address	All street data, including street names, address ranges and ESNs
Guide (MSAG)	used to validate incoming telephone number data for provisioning
	of selective routing.

Mobile Position Center	The network entity that provides phase 2 location information to
(MPC)	the ALI database over an E2 interface. For the purposes of this
	document, MPC and GMLC are considered equivalent although a
	GMLC is unique to the GSM environment.

Mobile Switching	Wireless equivalent of an End Office, which provides switching
Center (MSC)	functions from wireless calls.

National Emergency	A professional association of 9-1-1 emergency number entities
Number Association	responsible for the planning, implementation, management and
(NENA)	administration of national emergency number issues.

NPA	The area code of the telephone number.

NRF	No Record Found

NXX	The first three(3) digits of a telephone number following the NPA.

- continued -

Page 6

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Overview of E911

	Table B Glossary of Terms (continued)

Term	Definition

Pseudo-ANI (pANI)	The telephone number assigned by the wireless carrier to designate
	a specific cell antenna face or PSAP. Also see Automatic Number
	Identification (ANI).

Public Safety	The answering location for 911 calls.
Answering Point
(PSAP)

RCF	Remote Call Forwarding

SALI	Stand Alone Automatic Location Identification

SCC Communications	A vendor designated by BST to handle E911 data maintenance
	(now Intrado)

Selective Routing (SR)	A standard feature that routes an E911call from the E911 tandem to
	the designated PSAP based upon the address and assigned ESNof
	the pseudo-ANI telephone number record.

Service Order Interface	A formatted data record sent to the E911 host computer system by
Record (SOIR)	the wireless carrier. (see TSS)

Signaling System	An out-of-band signaling system used to provide basic routing
7 (SS7)/Common	information, call set up and other call termination functions.
Channel Signaling 7	Signaling is removed from the voice channel and put on a separate
(CCS7)	data network.

Subscriber	Person or end user making a 911 call.

System ID	A two(2) character code used to identify a tandem. (Assigned by
	BST)

Tandem Routing	An arrangement for connecting E911calls to the correct PSAP
	based on the ESN associated to the pseudo-ANI telephone number
	service address. (see Selective Routing)

Telco (Telephone	A term used interchangeable throughout this document to depict a
Company)	Bell Operating Co., an Independent Company, an Alternative Local
	Exchange Carrier (ALEC) or a Wireless service provider.

TN	Telephone Number

Transaction Servicing	The BellSouth E911vendor’s computer system that performs
System (TSS)	database processing.

WSANI	Wireless Subscribers ANI (see ANI or pANI)

Note: Additional wireless and technical information may be found on the NENA web site at http://nena9-1-1.org:Click here to access website.

Page 7

Wireless E911 Guide	CG-EWCG-001
Overview of E911	Issue 3, January 6, 2004

1.8Database Escalation Procedures

The following procedures have been established for Wireless Carrier escalation of database related issues to BellSouth / Intrado: (Examples of these issues are, but not limited to: MSAG problems, NPA / NXX updates, etc.)

The initial trouble / problem referral made by the Wireless Carrier should go to the Intrado NDSC Data Analyst. The escalation process will normally begin after a referral is made to the NDSC with unsatisfactory or no resolution.

1.8.1Access To NDSC Analysts

DIAL 1-888-584-3810, AT THE PROMPT, ENTER THE APPROPRIATE EXTENSION NUMBER.

1.8.2Level One Escalation: Intrado

Data Opns SUPERVISOR (Kelley Thomson) extension 6269

1.8.3Level Two Escalation: Intrado

Data Opns MANAGER (Mike Wallace) extension 6270

1-888-584-3810

1.8.4Level Three Escalation: Bellsouth

BellSouth Wireless E911 Implementation Manager: (205) 321-4785

If the problem has not been resolved by Intrado or the problem has not been resolved to the customer’s satisfaction, the BellSouth Wireless E911 Implementation Manager should be contacted:

1.The BellSouth Wireless E911 Implementation Manager should be notified of the problem.

2.The BellSouth Wireless E911 Implementation Manager will involve the BellSouth Address/911 Staff Support organization as required. All 911 / addressing issues should be referred by the Wireless E911 Implementation Manager to the Address / 911 Staff.

3.The Address / 911 Staff Support group will investigate and resolve or escalate up to the highest level necessary within BellSouth and / or Intrado. When the problem is resolved, A / 911 Staff Support will advise the Wireless E911 Implementation Manager who will notify the customer of the resolution.

Page 8

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Coordination of Wireless Interconnection

2.Coordination of Wireless Interconnection

2.1Overview

This section provides the Wireless Carrier with the steps necessary to interconnect with the BellSouth (BST) E911 network.

The FCC Wireless Phase 1 Order requires the Wireless Carrier to provide both the cell site sector location information and the wireless subscribers call - back number for wireless 911 calls. Phase 2 requires the additional data fields longitude and latitude be provided to represent the location of the caller when they dialed 911. Cell site sector location information is provided in "static" database records as described in TN Database Updates. The subscriber’s call - back number, longitude, and latitude must be provided real - time during 911call processing. Various technical solutions may be chosen by the Wireless Carrier to provide the required data to the ALI database. Wireless Carriers must work with Intrado to ensure the chosen solution is compatible with the BST ALI database interfaces. Some solutions allow the "static" database records to be assigned on a PSAP basis with the cell site sector location information, call - back number, and the longitude / latitude being provided real-time during 911 call processing.

Wireless Carriers must order Type 2C trunks for transmission of the voice and pseudo-ANI (pANI) numbers to the E911 tandem. Some solutions may require SS7 / ISUP trunking between the wireless MSC and the E911 tandem. If SS7 connectivity will be used, refer to Appendix A of this guide. In addition to these trunks, Wireless Carriers may be required to order two(2) digital data circuits with secondary channel to the BST Automatic Location Identification (ALI) computers. These circuits are necessary to provide Phase 1 real-time updates to the ALI database for storing the wireless subscribers ten digit call-back number and for some solutions, cell site sector location information. Two redundant ALI computers work as a mated pair, therefore a digital data circuit is required to each of the two ALI computers. The need for digital data circuits depends on the technical solution chosen. Steps to determine if there is a need, and how to order these circuits, are described in this section.

Wireless Carriers must also provide E2 connectivity between the MPCs and the ALI database hosts allowing Phase 2 location information to be populated in the ALI databases.

Interconnection to the BST E911 network involves the effort of various BST departments. The BST Wireless Account Team and Wireless E911 Implementation Manager will be the coordinators between the Wireless Carrier and the various BST departments to assist with steps necessary for interconnection.

2.2Coordination Process: Wireless Carrier

The Wireless Carrier will notify the BST Wireless Account team and provide general information concerning the request to interconnect to BST’s E911 network. This information should include the states, counties, and / or parishes that are involved in the wireless coverage area, the method of interconnection to the BST network, and the technical solution chosen to provide the wireless subscribers call - back number and longitude / latitude to the ALI database, and E2 interface information.

Wireless Carriers must meet with each of the E911 Customers in the wireless coverage area to discuss cell site locations, valid addresses and formats for static database records, ESN assignments, identification

Page 9

Wireless E911 Guide	CG-EWCG-001
Coordination of Wireless Interconnection	Issue 3, January 6, 2004

of the appropriate E911 tandem, 911 call routing, default routing for ANI failures, and assignment of geographically valid pANI numbers from the wireless carrier’s number range. The E911 customers must agree on which PSAP will accept 911 calls from the various cell sites including when ANI failures occur. Wireless Carriers should also determine if the E911 Customers wish to segregate wireless 911 calls from wireline 911 calls by implementing separate trunk groups to the PSAP. All premises based E911 databases should be identified as well as any special procedures necessary to update those databases.

Carriers must also work directly with Intrado to include the Carrier’s pANI numbers in the appropriate Security Tables and to identify the appropriate E2 interface to invoke for Phase 2.

A Service Inquiry must be initiated by the Wireless Carrier through the BST Account team for the Type 2C trunk connections and/or SS7 /ISUP trunks to the E911 tandems. If SS7 connectivity will be used, refer to Appendix A of this guide. The BST Wireless E911 Implementation Manager will discuss with the Wireless Carrier the process of ordering / provisioning the digital data circuits to the ALI computers, if new circuits are required.

The Wireless Carrier must contact Intrado, the BST E911 database vendor, for all database related steps necessary for the establishment and maintenance of wireless database records and interfaces to the ALI computers. Carriers must post valid records in the E911 database prior to testing or turning up service. Additional information related to database requirements is found in this guide.

Since access to E911 is a critical issue in today’s environment, it is necessary for the Wireless Carrier to provide 24 X 7 contact name and telephone number information for maintenance and trouble handling / clearing.

2.3Coordination Process: BST Wireless Account Team

The BST Wireless Account team will receive the initial request from the Wireless Carrier and initiate the BST Service Inquiry process for interconnection to the BST E911 network. The BST Account team will contact the BST Wireless E911 Implementation Manager to begin the internal BST coordination process.

Various BST departments will review the Service Inquiry and update with additional required information. The BST Account team will then complete form RF-1004WS and forward this form, along with a copy of the Service Request, to the BST Wireless Service Center where service orders will be input into the service order system.

A copy of the form RF-1004WS will also be distributed to the BST Implementation team and Intrado.

2.4Coordination Process: BST Wireless E911 Implementation Manager

The BST Wireless E911 Implementation Manager will assist the Wireless Carrier with the requirements for connecting to the BST E911 network. During this process the BST Wireless E911 Implementation Manager will determine if it is necessary for the Wireless Carrier to order digital data circuits to the BST ALI computers. The technical solution chosen by the Wireless Carrier will determine the need for these data circuits:

Page 10

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Coordination of Wireless Interconnection

•If the Wireless Carrier is connecting to a DMS100 E911 tandem utilizing an existing Nortel wireless connection to the ALI computers, no additional data circuits will be required for Phase 1.

•If the Wireless Carrier provides their own wireless solution hardware in their network, the Wireless Carrier must provide the data circuits.

•If the Wireless Carrier contracts with a third party to provide the connection to the ALI computers, the data circuits should be provided by the third party.

•If new solutions are negotiated, the BST Wireless E911 Implementation Manager will work with the Wireless Carrier and the BST team to determine the interconnection requirements and process flow.

The BST Wireless E911 Implementation Manager will coordinate with the BST Wireless Access Carrier Advocacy Center (ACAC) the provisioning, testing, and Wireless Carrier acceptance of the Type 2C trunks to the BST E911 tandems as required. The BST Wireless E911 Implementation Manager will also coordinate with the BST departments and Intrado, the provisioning, testing, and acceptance of new data circuits to the ALI computers if applicable.

The BST Wireless E911 Implementation Manager will issue a Teleprocessing Request form to Intrado and the BST IT Transport Group if new data circuits are required to the ALI computers.

As required, the BST Wireless E911 Implementation Manager will assist the Wireless Carrier through the necessary processes required to complete the interconnection to the BST E911 network.

2.5Coordination Process: Mobile Position Center Provider

The Wireless Carrier will be required to submit written notification naming the Mobile Position Center (MPC) provider they have selected. Note that MPC and GMLC are equivalent with respect to this guide although a GMLC is unique to the GSM environment. This written notification should be submitted to the BST Wireless E911 Implementation Manager. Any subsequent change in MPC provider also requires written notification naming the new provider selected.

2.5.1Steps for Establishment/Change of Mobile Position Center Provider

The Wireless Carrier is required to provide written notification of their selected or modified MPC provider to the BST E911 Implementation Manager via US Mail, electronic mail, or fax:

BST Wireless E911 Implementation Manager

Attn: John Storey

3535 Colonnade Parkway

Birmingham, AL 35243

Tel: 205-977-7653

Fax: 205-977-7692

Email: John.Storey@bellsouth.com

Page 11

Wireless E911 Guide	CG-EWCG-001
Coordination of Wireless Interconnection	Issue 3, January 6, 2004

2.5.2Initial Establishment of Mobile Position Center Provider

The first step for the Wireless Carrier in establishing their MPC provider is to contact the BST Wireless E911 Implementation Manager. At that time a discussion will take place to determine the method of connectivity. The Wireless Carrier will be provided a questionnaire used to direct the Wireless Carrier to the next steps required for Phase II connectivity. Once it has been determined what the needs of the Wireless Carrier are, they will be directed to the appropriate network entity that will provide location

information to the ALI database. When the determination has been made, the Wireless Carrier will then be asked to provide written notification to the BST Wireless E911 Implementation Manager as to who they have selected as their MPC provider.

If the Wireless Carrier will use their own equipment and provide their own E2 Interface to BST, the first step is to contact the BST ICS E911 Product Manager. The Wireless Carrier is required to sign the Wireless E911 Phase 2 MPC Operator Interface Agreement and to work with the BST Wireless E911 Implementation Manager to connect the E2 circuits to the ALI databases.

2.5.3Change of Mobile Position Center Provider

Should the Wireless Carrier change the MPC provider that was initially selected, written notification to the BST Wireless E911 Implementation Manager will be required. This notification may be sent via US Mail, electronic mail, or faxed to the address noted above.

2.5.4Information Required for Phase 2 MPC/GMLC Circuits to the ALI Hosts

The following information can be used by Wireless Carriers or their MPC/GMLC providers in placing orders for the E2 Data Links which will connect their MPCs or GMLCs to BellSouth’s ALI Host Computers located in the 4 Data Centers. The BellSouth ALI Host Computers in Miami, FL and Charlotte, NC serve FL, GA, NC and SC. The BellSouth ALI Host Computers in Birmingham, AL and Nashville, TN serve LA, MS, AL, TN and KY. MPCs/GMLCs must be connected to the appropriate ALI host pairs for the states served.

PLASE NOTE - the following also contains information related to these circuit orders which must be returned to BellSouth’s Wireless E911 Implementation Manager as soon as it is available. This will aid in completion of preliminary forms that must be provided in advance of the orders to the data center personnel. to insure there are no delays in connecting and extending the circuits. Note that there is a separate form for each of the BellSouth ALI Host Computer locations.

You should also contact Doug McCambridge at Intrado (720-494-6271) to schedule coordinated testing of these circuits. Intrado requires at a minimum 5 days notice prior to testing. Questions/comments can be directed to John Storey at 205-977-7653 or by e-mail at John.Storey@bellsouth.com.

Detailed Circuit Information (Circuit IDs for all segments of the circuits with 24 X 7 Contact names and numbers, etc.) is required so that service technicians can communicate with each other in the event of outages or maintenance issues.

Page 12

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Coordination of Wireless Interconnection

2.5.5Forms

Birmingham DATA Center: (serving LA, MS, AL, TN, KY)

Nashville DATA Center: (serving LA, MS, AL, TN, KY)

Charlotte DATA Center: (serving FL, GA, NC, SC)

Miami DATA Center: (serving FL, GA, NC, SC)

Page 13

Wireless E911 Guide	CG-EWCG-001
	Issue 3, January 6, 2004

Page 14 - Blank

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Network Specifications and Ordering

3.Network Specifications and Ordering

3.1Overview

This section provides the Wireless Carrier with the Network Specifications and Ordering Procedures to be followed when ordering facilities to interconnect to the BST E911 network.

Due to the complex nature and many processes involved with interconnecting to the BST E911 network, coordination between the Wireless Carrier and the various BST organizations involved will be accomplished through the Wireless Carrier’s Marketing Account team and the BST Wireless E911 Implementation Manager.

3.2Specifications & Ordering Process:

3.2.1Option 1: BellSouth NORTEL Solution Carring Phase 1 Data Only (CBN & pANI)

This solution can be used for delivery of CBN and pANI as the Wireless Carrier begins to make Phase 2 location data available via an E2 interface, as described in J-STD-036. The Wireless Carrier will be required to order a minimum of two(2), Type 2C, Feature Group - D (FG-D) or SS7/ISUP signaling

trunks, connecting directly to the appropriate BellSouth E911 Tandem switch. If SS7 connectivity will be used, refer to Appendix A of this guide.

Note: These trunks must use J-STD-034.7 POI-T8 (MF) Interface Signaling which can be designed with or without the optional pause for acknowledgement after the 1st stage address field. Refer to J-STD-034.7 for details. Ensure the BellSouth Wireless Account Team specifies the correct option on the order form.

The Wireless Carrier will deliver a twenty(20) Digit FG-D signal consisting of the ten(10) digit call back number (CBN) and the ten(10) digit pseudo ANI (p-ANI), to the BellSouth E911 Tandem switch. This signal is in the following format:

KP + II + 10 Digit CBN + ST + KP + 10 Digit p-ANI + ST

Note that the "II" digits are placeholders and may be filled with any two(2) digits.

These trunks are to be ordered through the Wireless Carriers BellSouth Wireless Account Team as an addendum to the Wireless Carriers existing contract with BellSouth.

The Wireless Carrier is NOT required to order / purchase data link connections to the BellSouth ALI Host computers when using this option to provide Phase 1 information. The connection to the ALI Host computers will be handled by BellSouth. Wireless Carrier’s are responsible for providing E2 connectivity between the MPCs and BellSouth ALI Host computers as defined in BellSouth Technical Reference TR73610, Issue 2.

Page 15

Wireless E911 Guide	CG-EWCG-001
Network Specifications and Ordering	Issue 3, January 6, 2004

3.2.2Specification & Ordering Process: Option 2: Third Party Vendor Solution

The Wireless Carrier will be required to order a minimum of two (2), Type 2C, CAMA or SS7/ISUP signaling trunks, connecting to the appropriate BellSouth E911 Tandem switch. If SS7 connectivity will be used, refer to Appendix A of this guide.

If using CAMA signaling, the Wireless Carrier must be able to deliver to the BellSouth E911 Tandem the two(2) stage CAMA MF signal required for interfacing directly with the appropriate BellSouth E911 Tandem switches. This signal is in the following format:

Stage 1: KP + 11 + ST

Stage 2: KP + Info Digit + 7 Digit ANI (p-ANI) + ST

These trunks are to be ordered through the BellSouth Wireless Account Team as an addendum to the Wireless Carriers existing contract with BellSouth.

The Wireless Carrier is NOT required to order / purchase data link connections to the BellSouth ALI Host computers when using this option. The connection to the ALI Host computers is handled by the provider of the solution chosen by the Wireless Carrier. Wireless Carriers must work with Intrado to ensure the chosen solution is compatible with the supported interfaces to the ALI Host computers. Wireless Carriers must establish E2 connectivity between MPCs and the BellSouth ALI Host computers for Phase 2 as defined in BellSouth Technical Reference TR73610, Issue 2.

3.3Wireless Carrier Owned Hardware

If the Wireless Carrier chooses to purchase their own protocol conversion hardware as a means of achieving Phase I Compliance, the specifications / ordering process will be as follows:

3.3.1Trunking

The Wireless Carrier’s protocol conversion hardware must be able to deliver the two(2) stage CAMA MF signal required for interfacing directly with the BellSouth E911 Tandem switch. This signal is in the following format:

Stage 1: KP + 11 + ST

Stage 2: KP + Info Digit + 7 Digit ANI (p-ANI) + ST

These trunks are to be ordered through the BellSouth Wireless Account Team as an addendum to the Wireless Carriers existing contract with BellSouth.

Page 16

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	Network Specifications and Ordering

3.3.2 Data Connections Required For Wireless Carrier Owned Hardware - Phase 1

Only

In addition to the Type 2C CAMA or SS7 trunks, the Wireless Carrier will be required to purchase two(2)data link connections from their protocol conversion hardware directly to the BellSouth ALI Host computers. Two(2) data links are required because the BellSouth ALI Host computers are mated pairs for redundancy, and are located in different locations for diversity.

These data links are 9.6 or 19.2 Kbps asynchronous or up to 56Kbps synchronous for X.25. The Secondary Channel feature is required in order to deploy end-to-end diagnostic and configuration capability from the master end (BellSouth Data Center) without disruptive consequences. The characteristics of the equipment used to modulate the data links are:

•Sub-rate digital Channel Service Unit/Data Service Unit (CSU / DSU) compatible with Memotec SC56

•10 bit data character

-1 start bit

-8 data bits (8th bit ignored)

-1 stop bit

•Full Duplex

•Continuous Carrier

For additional information and details concerning the data interface, please refer to the following document which can be found on website www. interconnection.bellsouth.com/guides/html/tech_ref.html: and may be amended from time to time:

TR 73610

BELLSOUTH E911 REAL-TIME DATA INTERFACES FOR WIRELESS AND COMMERCIAL MOBILE RADIO SERVICE (CMRS) CONNECTION

In most cases, these data links will be interlata / interstate connections. As such, they must be ordered through the Wireless Carriers Interexchange Carrier of choice. The BellSouth portion of these circuits will be provisioned and maintained through the appropriate BellSouth Interexchange Access Customer Advocacy Center (ACAC).

Wireless Carriers must work with Intrado to ensure wireless solutions are compatible with the supported interfaces to the BellSouth ALI host computers.

3.4Wireless Phase 2

BellSouth supports the implementation of Wireless E911 Phase II through the nondiscriminatory access to its ALI database for those companies wishing to provide Mobile Position Center (MPC) functionality. For the purposes of this document, GMLC and MPC are considered equivalent although a GMLC is unique to a GSM environment. This access is facilitated through the BST ALI Interface. The MPC is defined

as the network entity that provides location information to the ALI database. Each MPC provider must execute a contract with BellSouth. This contract must be signed and in place prior to testing Phase II. Wireless Carriers should ensure they have contracted with an MPC provider prior to negotiating Phase

Page 17

Wireless E911 Guide	CG-EWCG-001
Network Specifications and Ordering	Issue 3, January 6, 2004

II testing and implementation. BellSouth requires that Wireless Carriers provide notification in writing upon the selection or change in MPC providers.

BellSouth is not responsible for the location determination technology, the accuracy of the location determination technology, or the investigation or maintenance of said technologies. Only the data required and specified by the FCC in its Report and Order 94-102 will be delivered by BellSouth to the PSAP when provided by the CMRS. This required data includes the cell site or sector location, the callback number, and the longitude/latitude of the caller. The delivery, or lack of delivery, of additional data elements which may be provided by the Wireless Carrier will not be the responsibility of BellSouth and BellSouth assumes no responsibility or liability for such information.

3.5Interface Testing

Wireless Carriers shall conduct joint testing of wireless interfaces to the BellSouth ALI computers. Testing will be required for first occurrences of a particular interface or vendor, and whenever changes are made to an existing interface.

Testing shall be conducted with Intrado utilizing their test facility in Colorado, as well as field testing with the BellSouth production ALI computers within the BellSouth region. Charges may be incurred by the Wireless Carrier for this testing. Details shall be specified in interface agreements.

Page 18

CG-EWCG-001	Wireless E911 Guide
Issue 3, January 6, 2004	MSAG Maintenance and ESN Assignment

4.MSAG Maintenance and ESN Assignment

4.1Overview

This section provides general information on ESN assignments and guidelines for working with BST, BST’s data vendor, Intrado, and with the E911 Customer on MSAG maintenance. The Wireless Carrier must meet with the E911 Customers in the wireless service area and agree on 911 call routing, default routing, ESN assignments, and properly assigning MSAG valid street addresses to each ALI database record. Intrado will be the point of contact for data processing and data issue resolution. All other issues should be directed to the BST Wireless E911 Implementation Manager.

4.2ESN Assignments

ESN mapping is necessary if calls are to be routed to more than one PSAP within an E911 service area. The E911 Customer is responsible for providing boundary information to BST during the conversion to E911 and, ongoing, as emergency districts change.

When an E911system is being implemented, the E911 Customer provides BST the boundaries depicting each fire, police and EMS jurisdiction for the E911 service area. After all emergency service boundaries have been defined, a different ESN is assigned to each geographical area with the same set of responding agencies, i.e., police, fire, and EMS.

The ESN controls 911 call routing to the proper PSAP and provides emergency agency information for each wireline 911 call. The ESN numbers are assigned to the E911 serving area based on the ESN numbers available in the E911 tandem central office switch. The ESN for wireless 911 calls are used to

route the call to the proper PSAP. Due to the geographical variation in service areas of different cell sites, it is not currently feasible to display specific emergency agency information for wireless calls. Cell site service areas generally do not match existing emergency service boundaries. Creating additional ESN boundaries for wireless service areas would be difficult for the E911 Customer and quickly exhaust

the ESN numbers available.

The Wireless Carrier must meet with each E911 Customer in the service area and provide wireless service coverage areas for each cell site. The E911 Customers must agree on which PSAP should receive 911 calls based on the coverage area for each antenna face. This may require agreements between political jurisdictions if the wireless service area crosses jurisdictional boundaries. In addition to deciding PSAP routing, the E911 Customers must also decide on which PSAP should receive all 911 calls where the ANI (pANI) is not delivered to the E911 tandem with the call. This condition is known as "ANI failure" and must be default routed to a specific PSAP. The E911 Customers should agree and assign ESN numbers for both normal and default routing. Wireless Carriers must provide BST the list of PSAPs identified to receive default routed calls and the associated trunk groups.

Wireless Carriers must identify E911 Customers using premises based ALI systems. Premises based systems may have special data and interface requirements to enable the dynamic wireless data to be included in those systems.

Page 19

Wireless E911 Guide	CG-EWCG-001
MSAG Maintenance and ESN Assignment	Issue 3, January 6, 2004

For areas with existing E911 service, existing ESN numbers should be assigned for wireless call routing. Any of the currently assigned ESN numbers for a specific PSAP can be selected and placed in the corresponding MSAG entries for the cell site addresses as described in the next section. The PSAP should identify which ESNs should be used.

4.3MSAG Maintenance and Validation

The Master Street Address Guide (MSAG) is the portion of the E911 database which contains the address and ESN information. The MSAG associates the appropriate ESN to the pseudo-ANI number based on the address on the data record provided by the Wireless Carrier.

It is the responsibility of the E911 Customer to assign, maintain and resolve discrepancies in MSAG data for their service area. The E911 Customer is also responsible for providing new address information and changes to address information to the BST data vendor for updating to the MSAG database.

It is the responsibility of all telcos (wireless and wireline) participating in an E911 service area to ensure that all data records sent to the E911 host database have an MSAG valid address. Each telco will work directly with the E911 Customer to resolve any address discrepancies.

The Wireless Carrier and E911 Customers must agree on the formatting of the Wireless Carrier data records. Some wireless solutions require that each antenna face or PSAP, depending on the wireless solution implemented, be assigned an MSAG valid address. The carrier and E911 Customer must work together and agree on how the address and cell site sector location information should be formatted and to ensure the addresses exist in the MSAG database with the appropriate ESN to route 911 calls to the agreed upon PSAP. For some solutions, each antenna face should be assigned unique pseudo-ANI (pANI) numbers by the Wireless Carrier to identify the specific cell site sector location. In other solutions, each PSAP is assigned unique pANI numbers. Pseudo-ANI numbers must be geographically valid for the E911 selective routing tandem used to route the calls to PSAPs. The Wireless Carrier must create SOIR data records for the cell sites or PSAPs containing the MSAG valid street address previously agreed upon with the E911 Customer. If the street address in the SOIR data record is not formatted exactly to match the MSAG entries, the SOIR data record will be in error and returned to the Wireless Carrier for correction. Refer to tab "TN Database Updates" for detailed information on providing data for the E911 database.

For some solutions, the address used for the cell site is the address that has been assigned to the structure where the tower is located. Or, if the tower is being constructed where there is no existing structure, it is the E911 address assigned by the County to the new tower location.

If all antenna faces for a tower will route calls to the same PSAP, the one address may be shown for each pseudo-ANI number associated with that tower. If it is determined that one or more of the pseudo-ANI numbers will need to route to a different PSAP, then different addresses for each face must be obtained from the E911 Customer. Prior to sending the pseudo-ANI data record to the E911 host, the cell site address should be validated with the E911 customer’s MSAG in an effort to minimize error fallout and ensure proper ESN assignment for call routing. If the address(es) to be used are not currently in the MSAG, then the E911 Customer should send a MSAG ledger document to the BST data vendor to add the address to the MSAG database. The pseudo-ANI data records for that cell site should not be transmitted by the wireless carrier until the address has been added to the MSAG database.

Page 20

+ 77 hidden pages