|
Carrier/Deployment |
FCC |
Voicestream |
Nextel |
Cingular (1) |
AWS (2) |
Verizon |
Sprint |
|
Technology Type |
|
GSM |
IDEN |
GSM |
GSM |
CDMA |
CDMA |
|
Solution Type |
E-OTD Handset |
AGPS Handset |
E-OTD Handset |
E-OTD Handset |
AGPS/AFLT Handset |
AGPS/AFLT Handset |
|
|
Handset Activations (3) |
|
|
|
|
|
|
|
|
Start date |
10/01/01 |
Before 10/1/1 |
10/01/02 |
10/01/01 |
|
12/31/01 |
10/01/01 |
|
10% |
|
|
12/31/02 |
|
|
|
|
|
25% |
12/31/01 |
Before 10/1/1 |
|
12/31/01 |
|
07/31/02 |
07/31/02 |
|
40% |
|
|
|
03/31/02 |
|
|
|
|
50% |
06/30/02 |
10/01/01 |
12/01/03 |
|
|
03/31/03 |
|
|
65% |
|
|
|
06/30/02 |
|
|
|
|
100% |
12/31/02 |
03/31/02 |
12/01/04 |
09/30/02 |
Sold Day 1 |
12/31/03 |
12/31/02 |
|
95% Penetration |
12/31/05 |
12/31/05 |
12/31/05 |
12/31/05 |
12/31/05 |
12/31/05 |
|
|
Handset 67% Accuracy 95% |
50m 150m |
100m 300m |
50m 150m |
100m 300m |
100m 300m |
50m 150m |
50m 150m |
|
Accuracy Compliance Date |
10/01/01 |
10/01/03 |
10/01/02 |
10/01/03 |
10/01/03 |
12/31/02 |
10/01/01 |
|
Initial Requests Deployed |
Implement |
All 10/01/01 |
|
12/31/02 |
All as GSM activated |
12/31/02 (4) |
06/30/02 |
|
Lucent areas |
10/01/01 |
|
|
|
04/01/02 |
05/30/02 |
|
|
Nortel areas |
10/01/01 |
|
|
12/01/02 |
08/30/02 |
08/01/02 |
|
|
Motorola areas |
10/01/01 |
|
|
|
|
03/01/03 |
|
|
Ericson |
10/01/01 |
|
|
12/01/02 |
|
|
|
|
Network Implement Dates |
|
|
|
|
|
|
|
|
PSAP 50% (5) |
10/01/01 |
|
|
|
|
12/31/01/ |
|
|
PSAP 100% |
10/01/02 |
04/01/02 (6) |
|||||
|
Accuracy 67% 95% |
100m 300m |
|
|||||
|
Accuracy Compliance Date |
10/01/01 |
10/01/03 |
10/01/03 |
||||
|
Backup Network Implementation Dates
|
|
12/31/01 |
|
03/31/02 to 06/30/02 |
100% as Headsets Enabled |
None Given |
|
|
Backup method |
None |
NSS |
None |
NSS |
EFLT |
None |
|
|
Backup accuracy |
1000m |
1000m |
250-350m |
1–Cingulars network based compliance plan for their TDMA customer base was not approved. Sent to the FCCs Enforcement Bureau for enforcement and a possible consent decree.
2–AWS network based compliance plan for their TDMA customer base was not approved. Sent to the FCCs Enforcement Bureau for enforcement and a possible consent decree.
3–A carrier will generally show compliance with an approved deployment plan by demonstrating that it has complied with the required fractional percentage figures during the period beginning at the date on which that percentage takes effect and ending at the date of the next benchmark. Thus, for the 10 percent benchmark, a Carrier would demonstrate that at least 10 percent of the new handsets it activated during the period between the effective date of that benchmark, and the effective date of the next benchmark were Phase II capable.
4–Except in markets served by Motorola switches. In those markets, Verizon must complete all valid PSAP requests received on or before 09/30/02 by 03/31/02.
5–As of October 1, 2001, within 6 months of a PSAP request, carriers employing network-based location technologies must provide Phase II information for at least 50% of the PSAPs coverage area or population. Within 18 months of a PSAP request, carriers must provide PHASE II information for 100 percent of the PSAPs coverage area or population. Note: for handset-based solutions, the coverage is based on percentages of handsets sold (with 25%, 50% and 100% levels, plus 95% of total customer base).
6–Verizon Wireless must employ a network based solution for 100% of St. Clair County, Illinois (St. Louis) and Lake County, Indiana (Gary-East Chicago market) by 12/31/01; and, for 100% of Cook County, Illinois (Chicago), St. Louis County, Missouri (St. Louis) and Harris County, Texas (Houston) by 04/01/02. In areas where Verizon receives a valid PSAP request where the majority of the PSAPs coverage area is covered by Verizons analog-only network, Verizon must take affirmative steps to comply with FCC rules.
7–In all markets served by Lucent and Nortel switches (on or before 04/01/02).
PSAP Readiness and Valid Phase II Requests
In response to a petition for clarification filed by the City of Richardson, Texas, the FCC amended its rules to clarify what constitutes a valid PSAP request for Phase II service (and thus triggers a Carriers obligation to provide such service). Specifically, the FCC held that a Carrier must implement wireless E911 service within the six-month period following the date of the request. If (only if) the Carrier challenges the validity of the request, the request will be deemed valid if the PSAP demonstrates that:
- A mechanism is in place by which the PSAP will recover its costs of the facilities and equipment necessary to receive and utilize the E9-1-1 data elements;
Citation to or a copy of the relevant funding legislation is sufficient to demonstrate compliance. Presumably this could range from a local municipal ordinance, to state statute. Also, presumably, this could include an adopted local budget that addresses said implementation.
 |
The PSAP has ordered the equipment necessary to receive and utilize the E911 data and the equipment will be installed and capable of receiving and utilizing that data no later than six months following its request; and |
Essentially, this includes CPE necessary to locate the callers location for the purposes of dispatching assistance, and that such equipment is scheduled to be installed and operable by the end of the six-month period. The Order indicates that “substantiation” could take the form of a listing of the necessary facilities and equipment and copies of the relevant vendor purchase orders. In that latter instance, such orders should reflect six-month vendor commitment. The Order does not specify the type of equipment or technology involved, nor, for that matter, a particular type of mapping capacity. These are local decisions.
| |
The PSAP has made a timely request to the appropriate local exchange carrier (LEC) for the necessary trunking and other facilities, including any necessary Automatic Identification Location (ALI) database upgrades, to enable the E911 data to be transmitted to the PSAP. |
The Order notes that such facilities and equipment could include upgrades to the 9-1-1 selective router, trunking and ALI database. Evidence could consist of the letter of request, as well as any other pertinent correspondence between the PSAP and the LEC (9-1-1 Service Provider).
Finally, as an alternative to the above, the Order holds that a PSAP requesting Phase II service may demonstrate that a funding mechanism is in place, that it is Phase I-capable using a Non-call Associated Signaling (NCAS) technology, and that it has made a timely request to the appropriate LEC (9-1-1 service provider) for the upgrade to the ALI database necessary to enable the PSAP to receive the Phase II data.