10.1 Regulatory Governance: FCC Authority & Part 9 Orders
Key Takeaways
- The Federal Communications Commission (FCC) regulates originating service providers (OSPs) under Title II and Title III of the Communications Act of 1934, while the Tenth Amendment reserves day-to-day PSAP operations, staffing, and local dispatch protocols to state and municipal governance.
- In 2019, the FCC unified previously dispersed emergency communications mandates across wireline, wireless, interconnected VoIP, text-to-911, and multi-line telephone systems (MLTS) into 47 CFR Part 9.
- FCC Docket 94-102 (opened 1994) established wireless E9-1-1: Basic 9-1-1 for all calls, including non-service-initialized (NSI) handsets; Phase I callback number and cell site/sector; and Phase II coordinates, now measured at 50 m for 67% and 150 m for 90% of calls (handset-based) or 100 m for 67% and 300 m for 90% (network-based).
- PS Docket 07-114 added indoor location rules: horizontal benchmarks of 50 meters (or dispatchable location) phased up to 80% of calls by April 2021, and a z-axis metric of ±3 meters relative to the handset for 80% of calls from z-axis-capable devices, extended nationwide by April 2025 for nationwide carriers and April 2026 for other carriers.
- Under 47 CFR Part 4, providers file NORS outage notifications within 120 minutes (240 for interconnected VoIP), initial reports within 72 hours, and final reports within 30 days; separately, 47 CFR § 4.9(h) requires notifying affected 9-1-1 special facilities within 30 minutes of discovering a 9-1-1 outage, with follow-ups within 2 hours.
10.1 Regulatory Governance: FCC Authority & Part 9 Orders
Quick Answer: The legal foundation of United States emergency communications rests on a dual regulatory framework rooted in the U.S. Constitution. Under the Interstate Commerce Clause and the Communications Act of 1934, the Federal Communications Commission (FCC) exercises regulatory jurisdiction over Originating Service Providers (OSPs)—including wireline, wireless, interconnected VoIP, and text providers—codifying comprehensive technical mandates under 47 CFR Part 9. Key FCC dockets govern wireless Phase I and Phase II location accuracy (Docket 94-102), indoor horizontal and vertical (z-axis) accuracy (Docket 07-114), and text-to-911 bounce-back and carrier delivery rules (Docket 11-153). In 2024 the FCC also adopted rules requiring originating service providers to deliver 9-1-1 traffic in NG9-1-1 formats once 9-1-1 authorities are ready. Under 47 CFR Part 4, providers report major outages through NORS and must notify affected PSAPs within 30 minutes of discovering an outage that affects 9-1-1. Crucially, the Tenth Amendment reserves the internal administration, staffing, dispatch SOPs, and facility operations of Public Safety Answering Points (PSAPs) to state and local authorities, while federal statutes grant telecommunicators and wireless/VoIP carriers statutory liability parity matching traditional wireline providers.
1. Constitutional Authority & The Federal-State Jurisdictional Balance
Emergency telecommunications in the United States operates under a dual jurisdictional framework established by the United States Constitution. Navigating the legal division between federal administrative oversight and state sovereign authority is a core competency for Emergency Number Professionals (ENPs).
┌─────────────────────────────────────────────────────────────────────────────┐
│ CONSTITUTIONAL DIVISION OF 9-1-1 REGULATORY AUTHORITY │
├──────────────────────────────────────┬──────────────────────────────────────┤
│ FEDERAL JURISDICTION (FCC) │ STATE & LOCAL JURISDICTION │
│ (Commerce Clause & Comm. Act 1934) │ (Tenth Amendment Police Powers) │
├──────────────────────────────────────┼──────────────────────────────────────┤
│ • Regulates Originating Providers │ • Operates PSAPs and ECC facilities │
│ • 47 CFR Part 9 emergency mandates │ • Establishes dispatch SOPs & QA/QI │
│ • RF spectrum licensing (Title III) │ • Sets telecommunicator hiring/STC │
│ • Location accuracy standards (Ph II)│ • Selects CAD, CPE, and LMR systems │
│ • Outage reporting (Part 4 NORS/DIRS)│ • Levies state/county 9-1-1 fees │
│ • Interconnection rights (Title II) │ • Governs emergency service response │
└──────────────────────────────────────┴──────────────────────────────────────┘
The Communications Act of 1934 & Federal Commerce Clause Powers
Article I, Section 8, Clause 3 (the Commerce Clause) of the U.S. Constitution grants Congress plenary authority to regulate interstate and foreign communications. Congress enacted the Communications Act of 1934 (47 U.S.C. § 151 et seq.), creating the Federal Communications Commission (FCC) to execute this mandate:
- Title II (Common Carriers): Governs telecommunications common carriers, mandating just, reasonable, and non-discriminatory access to communications facilities, interconnection, and service quality.
- Title III (Radio Communications): Authorizes the FCC to license and regulate the radio frequency (RF) spectrum, establishing technical rules for commercial mobile radio service (CMRS) wireless providers, broadcast systems, and public safety spectrum allocations.
Under this authority, the FCC exercises regulatory control over Originating Service Providers (OSPs)—including Incumbent Local Exchange Carriers (ILECs), Competitive Local Exchange Carriers (CLECs), CMRS cellular carriers, interconnected Voice over Internet Protocol (VoIP) providers, and mobile messaging carriers. The FCC mandates how these commercial carriers must handle, translate, format, and deliver 9-1-1 emergency transmissions across their networks to the public safety demarcation point.
State Police Powers & The Tenth Amendment Boundary
Under the Tenth Amendment to the U.S. Constitution, powers not delegated to the federal government are reserved to the states and the people. The administration of emergency medical services, structural fire response, law enforcement operations, and municipal dispatching falls squarely within state police powers.
Consequently, the FCC's statutory reach stops at the public safety demarcation point. The FCC possesses no legal authority to mandate:
- How many seconds a PSAP telecommunicator has to answer an incoming emergency line (which is governed locally by NFPA 1225 and NENA operational standards).
- Staffing minimums, shift configurations, or mandatory overtime policies for local dispatchers.
- Telecommunicator training curricula, state-mandated certification rules, or hiring qualifications.
- The specific Computer Aided Dispatch (CAD) vendor, 9-1-1 call handling software (CPE), or radio console hardware procured by a city or county.
Federal regulation dictates how carriers must deliver the call and its associated data payload (ANI, ALI, PIDF-LO) to the gateway of public safety, while state statutes and local intergovernmental agreements govern everything that occurs inside the communications center.
2. 47 CFR Part 9: Consolidation of Emergency Communications Rules
For decades, federal 9-1-1 rules were fragmented across multiple disconnected titles of the Code of Federal Regulations, including Part 12 (911 reliability), Part 20 (commercial mobile radio services), and Part 64 (common carrier and relay services). This fragmentation created regulatory ambiguity as legacy circuit-switched networks converged into unified IP architectures.
In 2019, the FCC adopted a comprehensive restructuring that consolidated all emergency communications regulations into 47 CFR Part 9 (911 Requirements for Service Providers). Part 9 unifies regulatory mandates across all communications modalities:
- Subpart B: Telecommunications Carriers: Wireline carriers must route 9-1-1 calls to the appropriate PSAP.
- Subpart C: Commercial Mobile Radio Service (CMRS): Wireless 9-1-1, Phase I and Phase II location, indoor horizontal and z-axis accuracy, location-based routing, and text-to-911 (including the bounce-back rule in § 9.10(q)).
- Subpart D: Interconnected VoIP: E9-1-1 obligations for interconnected VoIP, including registered and dispatchable location requirements.
- Subpart E: Telecommunications Relay Services: 9-1-1 obligations for relay providers serving people with disabilities.
- Subpart F: Multi-Line Telephone Systems (MLTS): Rules implementing Kari's Law (direct dialing and on-site notification) and RAY BAUM'S Act Section 506 (dispatchable location).
- Subpart G: Mobile-Satellite Service: Emergency call center requirements for satellite voice providers.
- Subpart H: Resiliency, Redundancy and Reliability of 911 Communications: Reliability certifications for covered 9-1-1 service providers.
- Subpart I: Restrictions on Use of 911 Fees: The fee diversion rules adopted in 2021 (§§ 9.21–9.26).
- Subpart J: Next Generation 911: The 2024 NG9-1-1 transition rules (§§ 9.27–9.34).
3. Major FCC Dockets & Regulatory Proceedings
The technical benchmarks that define modern emergency call delivery are established through binding administrative dockets promulgated by the FCC under 47 CFR Part 9.
FCC 9-1-1 DOCKET EVOLUTION
┌────────────────────┐ ┌────────────────────┐ ┌────────────────────┐
│ DOCKET 94-102 │ │ DOCKET 07-114 │ │ DOCKET 11-153 │
│ Wireless E9-1-1 │───►│ Indoor / Z-Axis │───►│ Text-to-911 │
│ Phase I & II │ │ Vertical Accuracy │ │ Bounce-Back & SMS │
└────────────────────┘ └────────────────────┘ └────────────────────┘
FCC Docket 94-102: Wireless E9-1-1 Deployment
Initiated in 1994, Docket 94-102 established the three-tier framework governing CMRS cellular providers:
- Basic 9-1-1: Mandates that wireless carriers transmit all 9-1-1 calls to a designated PSAP without requiring user validation, active subscription, or credit verification. This mandates processing calls from Non-Service Initialized (NSI) mobile phones (handsets without an active cellular carrier subscription). Because NSI handsets lack a valid phone number, carriers transmit a pseudo-ANI formatted as
911-XXX-XXXX. Operational Reality: If an NSI call drops, the telecommunicator cannot call the party back, making immediate verbal location verification essential. - Wireless Phase I: Within six months of receiving a valid request from a PSAP able to receive the data (the FCC later eliminated the original cost recovery precondition), carriers must deliver the caller's Mobile Directory Number (MDN / callback number) and the specific cell tower site and sector handling the call, represented by a pseudo-ANI (p-ANI) routing key.
- Wireless Phase II: Carriers must deliver the caller's geodetic horizontal latitude and longitude coordinates. Docket 94-102 established two distinct technological compliance tracks:
- Handset-Based Technologies (e.g., Assisted-GPS / A-GPS): Must achieve horizontal accuracy within 50 meters for 67% of calls, and within 150 meters for 90% of calls.
- Network-Based Technologies (e.g., Uplink Time Difference of Arrival / U-TDOA): Must achieve horizontal accuracy within 100 meters for 67% of calls, and within 300 meters for 90% of calls.
FCC Docket 07-114: Indoor Wireless Location Accuracy & Vertical (Z-Axis) Metric
While Phase II mandates functioned effectively outdoors where mobile handsets had line-of-sight to Global Positioning System (GPS) satellites, consumer behavior shifted dramatically: over 80% of emergency calls originate from wireless devices, and the overwhelming majority occur indoors. Satellite signals suffer severe attenuation and multipath distortion when penetrating commercial high-rises, subterranean transit hubs, and residential apartment buildings.
Through Docket 07-114 (incorporating the landmark Fourth and Fifth Report and Orders), the FCC established new metrics:
- The Dispatchable Location Standard: Defined in FCC rules as the validated civic street address of the calling party, plus additional interior information such as suite, apartment, room, or floor level, necessary to pinpoint the caller's physical location.
- Horizontal Indoor Benchmarks (Fourth Report and Order, 2015): Carriers must provide dispatchable location or a location within 50 meters for a rising share of wireless 9-1-1 calls, reaching 80% by April 2021.
- Vertical Z-Axis Metric (Fifth Report and Order, 2019): Carriers must deliver z-axis location within ±3 meters relative to the handset for 80% of wireless 9-1-1 calls from z-axis-capable devices, reported as height above ellipsoid (HAE). The Sixth Report and Order (2020) extended this nationwide by April 2025 for nationwide carriers and April 2026 for other carriers.
- Device-Based Hybrid (DBH) Positioning: To achieve ±3-meter precision (roughly the height of a single building floor), carriers leverage DBH positioning engines integrated into consumer smartphone operating systems. DBH blends onboard barometric pressure sensor readings (calibrated against local weather sensor networks) with Wi-Fi access point Basic Service Set Identifiers (BSSIDs), Bluetooth Low Energy (BLE) beacon telemetry, and cellular multilateration.
FCC Docket 11-153: Text-to-911 Mandates
Recognizing that voice calling is impossible for speech- or hearing-impaired citizens, or in active threat environments where speaking aloud invites immediate violence (e.g., active shooter, domestic assault, abduction), the FCC established comprehensive text-to-911 rules under Docket 11-153:
- The Automated Bounce-Back Mandate (2013): If a citizen attempts to send a text message to 9-1-1 in a geographic territory where the local PSAP has not deployed text-to-911 capabilities, the wireless carrier or over-the-top (OTT) text messaging provider must transmit an immediate, automated bounce-back text message. The notification warns the sender that text-to-911 is unavailable and instructs them to make an immediate voice call to 9-1-1.
- Six-Month Carrier Deployment Rule (2014): All nationwide CMRS providers and interconnected text providers must deliver SMS Text-to-911 service to any requesting PSAP within six months of receiving a valid operational request.
- PSAP Ingress Architectures: Text-to-911 can be integrated via three distinct technical methods:
- Web Browser Portal: Inbound messages terminate on a secure, web-hosted portal; cost-effective for legacy PSAPs but lacks CAD integration.
- Direct IP / NG911 Interface (MSRP/SIP): Inbound messages arrive over an ESInet using the Message Session Relay Protocol (MSRP), terminating directly inside the call handling console and CAD.
- Legacy TTY Emulation: Inbound SMS is converted into legacy 45.45-baud Baudot tones and routed over analog CAMA/TDM trunks to legacy call-handling consoles.
4. Telecommunications Outage Reporting: 47 CFR Part 4, NORS & DIRS
Public safety communications depend upon the physical integrity and logical availability of carrier transport networks. A severed fiber backbone, an uncoordinated cloud software update, or an unmanned central office fire can isolate an entire county from 9-1-1 service. Under 47 CFR Part 4, the FCC enforces strict, mandatory outage reporting on telecommunications carriers, cable operators, satellite providers, and interconnected VoIP carriers.
47 CFR PART 4 OUTAGE REPORTING FLOW
[Critical Network Event / Fiber Cut] ──► Impact: PSAP Trunk Failure or >900k User Minutes
│
┌─────────────────────────────────┴─────────────────────────────────┐
▼ ▼
[PSAP IMMEDIATE NOTIFICATION] [FCC NOTIFICATION (NORS)]
• Must notify affected PSAP • Electronic filing via NORS
• Within 30 minutes of discovery • Initial notification: ≤120 min
• Provides technical details, affected • Initial detailed report: ≤72 hours
trunks, and estimated restoration time • Final comprehensive report: ≤30 days
Network Outage Reporting System (NORS)
Carriers must submit confidential electronic reports through the Network Outage Reporting System (NORS) when network incidents satisfy specific federal thresholds:
- General Telecommunications Threshold: Any outage lasting at least 30 minutes that potentially affects at least 900,000 user minutes (calculated by multiplying the number of affected access lines by the outage duration in minutes).
- Special 9-1-1 Facility Threshold: A significantly more stringent threshold applies to public safety facilities. A carrier must report any outage lasting at least 30 minutes that results in the complete loss of 9-1-1 call routing, isolates a PSAP, severs dedicated emergency trunk groups, or causes the catastrophic loss of Automatic Number Identification (ANI) or Automatic Location Identification (ALI) lookup capabilities.
- Mandatory Reporting Timeline:
- Initial Notification: Must be filed electronically in NORS within 120 minutes of discovering that an outage meets reporting thresholds (240 minutes for interconnected VoIP providers).
- Initial Outage Report: A more detailed technical filing submitted within 72 hours.
- Final Outage Report: A comprehensive post-incident root-cause analysis submitted within 30 days of the incident.
- Direct PSAP Notification (47 CFR § 4.9(h)): Under rules updated in 2022 (FCC 22-88), originating service providers and covered 9-1-1 service providers must notify potentially affected 9-1-1 special facilities as soon as possible and no later than 30 minutes after discovering an outage that affects 9-1-1, follow up within 2 hours with more detail, and keep the PSAP updated until service is restored. Early notice lets the PSAP activate alternate routing, move to a backup facility, or issue public notifications.
Disaster Information Reporting System (DIRS)
During major catastrophic incidents—such as Category 4/5 hurricanes, catastrophic earthquakes, or widespread wildfires—the FCC activates the Disaster Information Reporting System (DIRS):
- DIRS is a coordinated reporting portal used in declared disaster territories.
- Originating service providers, wireless carriers, broadcast stations, and multichannel video providers submit daily operational status reports.
- DIRS tracks the operational status of local exchange central offices, cellular base station (cell site) outages by county, percentage of cell towers operating on emergency generator power, and 9-1-1 selective router availability.
- The FCC compiles DIRS filings into daily public situational awareness reports and coordinates with the Department of Homeland Security (CISA and FEMA) to prioritize emergency fuel deliveries and mobile communications assets (e.g., Cells on Wheels / COWs) to restore communications.
5. Federal Statutory Enactments & Parity of Liability
Federal legislation has repeatedly intervened to balance the responsibilities of commercial network operators with the legal protections required for public safety personnel.
1999: 911 ACT ────────────────► 2008: NET 911 ACT ───────────────► 2012: TAX RELIEF ACT
• Universal 9-1-1 number • Interconnected VoIP mandate • FirstNet created (Band 14)
• Qualified liability parity • Selective router access rights • NG9-1-1 Advancement Act
for PSAPs & wireless telcos • VoIP liability parity • Anti-diversion sanctions
Wireless Communications and Public Safety Act of 1999 (The 911 Act)
Enacted as Public Law 106-81, the 911 Act established two statutory cornerstones:
- Universal Emergency Number: Statutorily designated 9-1-1 as the universal emergency assistance number across the United States for all wireline and wireless voice communications.
- Statutory Parity of Liability: Prior to 1999, traditional wireline ILECs enjoyed broad protection against tort liability under state regulatory tariffs for dropped calls or network routing failures, absent willful misconduct. Wireless carriers, PSAP authorities, and emergency telecommunicators lacked equivalent statutory protection. The 1999 Act established statutory liability parity: it enacted federal law providing that wireless service providers, PSAPs, local public safety officials, and 9-1-1 telecommunicators shall have the exact same immunity from civil liability under federal, state, and local law as that enjoyed by traditional wireline carriers within the governing state jurisdiction.
New and Emerging Technologies 911 Improvement Act of 2008 (The NET 911 Act)
When interconnected Voice over Internet Protocol (VoIP) services proliferated, early subscribers discovered that VoIP calls either failed to reach 9-1-1 or terminated at unmonitored administrative phone numbers. The NET 911 Act (Public Law 110-283) amended the Communications Act of 1934 to resolve this crisis:
- Interconnected VoIP E9-1-1 Mandate: Obligated interconnected VoIP providers to deliver 9-1-1 calls with full E9-1-1 capabilities (ANI and registered physical location ALI) to the designated PSAP.
- Selective Router Interconnection Rights: ILECs had previously barred VoIP providers from accessing proprietary 9-1-1 selective routers. The NET 911 Act established statutory interconnection rights, granting VoIP providers access to 9-1-1 tandem selective routers, selective routing databases (SRDB), and ALI databases on reasonable, non-discriminatory rates and terms.
- VoIP Parity of Liability: Extended federal civil liability parity protections to interconnected VoIP providers, their underlying facilities carriers, and the PSAPs processing VoIP emergency calls.
Telecommunications Act of 1996
The Telecommunications Act of 1996 opened local telephone markets to competition. It required incumbent carriers to interconnect with competitive local exchange carriers (CLECs) and to offer unbundled network elements, which is why CLECs, and later VoIP providers, needed access to 9-1-1 selective routers and ALI databases on nondiscriminatory terms.
ENHANCE 911 Act of 2004
The Ensuring Needed Help Arrives Near Callers Employing 911 Act of 2004 (the ENHANCE 911 Act) created the federal E-911 Implementation Coordination Office, run jointly by NTIA and NHTSA, and authorized matching grants for PSAP E9-1-1 upgrades. Grant applicants had to certify that 9-1-1 fees were not being diverted, an early federal anti-diversion condition.
Middle Class Tax Relief and Job Creation Act of 2012
Title VI of this law created FirstNet, and its Next Generation 9-1-1 Advancement Act of 2012 provisions extended the federal 9-1-1 grant program to NG9-1-1 and directed reports on NG9-1-1 costs and legal frameworks.
FCC NG9-1-1 Transition Rules (2024)
In July 2024 the FCC adopted a Report and Order (FCC 24-78, PS Dockets 21-479 and 18-64, effective November 25, 2024) that sets a two-phase path for originating service providers, codified in 47 CFR Part 9, Subpart J:
- Phase 1: After a valid request from a 9-1-1 authority that is ready, providers must deliver 9-1-1 traffic in IP-based SIP format to the authority's designated NG9-1-1 delivery points.
- Phase 2: After a further valid request, providers must deliver calls in the NENA i3-standard format, including location information (PIDF-LO) and support for location information server functions.
- Deadlines and costs: Providers have 6 or 12 months after a valid request depending on provider type (nationwide wireless carriers and VoIP providers have the shorter period; rural local exchange carriers and non-nationwide wireless carriers have the longer), and they bear the cost of delivering traffic to the NG9-1-1 delivery points.
6. Regulatory & Technical Comparison Matrix
| Statutory / Administrative Citation | Regulatory Subject | Regulated Entities | Primary Technical Standard | Legal / Enforcement Remedy |
|---|---|---|---|---|
| 47 U.S.C. § 151 et seq. | Common Carrier & RF Oversight | All OSPs, CMRS, Wireline | Plenary interstate authority; universal emergency calling | Administrative fines, forfeitures, license revocations |
| 47 CFR Part 9 | Consolidated 911 Rules | Wireline, Wireless, VoIP, MLTS, Text | Unified regulatory code governing all emergency service providers | FCC enforcement actions; Notice of Apparent Liability (NAL) |
| FCC Docket 94-102 | Wireless E9-1-1 | Commercial Mobile Radio Service | Basic (NSI); Phase I (p-ANI/MDN); Phase II (handset 50m/network 100m) | Carrier compliance benchmarks; civil penalties |
| FCC Docket 07-114 | Indoor & Vertical Accuracy | Nationwide CMRS Providers | Indoor 50 m horizontal benchmarks; z-axis ±3 m relative to the handset for 80% of calls from z-axis-capable devices | Phased CMA deployment; carrier compliance certifications |
| FCC Docket 11-153 | Text-to-911 Mandates | CMRS & Interconnected Text | Automated bounce-back; 6-month deployment upon valid PSAP request | Federal consent decrees; carrier forfeiture orders |
| 47 CFR Part 4 | Outage Reporting (NORS/DIRS) | Wireline, CMRS, VoIP, Cable | 30-min / 900k user-min threshold; special 911 facility criteria; PSAP notice within 30 min; NORS notice within 120 min | Mandatory NORS filings; daily DIRS disaster tracking |
| P.L. 106-81 / P.L. 110-283 | Liability Parity | Wireless, VoIP, PSAPs, Dispatchers | Parity of qualified immunity matching traditional wireline carriers | Affirmative defense against civil tort claims (negligence) |
| FCC 24-78 (47 CFR Part 9, Subpart J) | NG9-1-1 Transition | Wireline, CMRS, VoIP, text, and relay providers | Phase 1 SIP delivery; Phase 2 i3 delivery with PIDF-LO; 6 or 12 months after valid request | FCC enforcement; provider bears delivery costs |
7. Operational Traps & ENP Exam Watch
- Non-Service Initialized (NSI) Handset Traps: Carriers must deliver calls from NSI phones (unsubscribed cellular handsets), but these devices lack an active phone number. They transmit a pseudo-ANI such as
911-XXX-XXXX. If disconnected, the telecommunicator cannot call the party back. Telecommunicators must immediately verify and log the caller's physical location. - The FCC Does Not Regulate PSAP Operations: An exam distractor may suggest that the FCC can penalize a municipal PSAP for poor call-answer times or inadequate telecommunicator staffing. The FCC's jurisdiction under the Communications Act covers interstate carriers and commercial service providers, not municipal public safety operations, which are governed by state law under the Tenth Amendment.
- Liability Parity Is Not Absolute Immunity: The 911 Act of 1999 and the NET 911 Act establish parity with wireline carriers under state law, which represents qualified immunity shielding against ordinary negligence. It does not protect against gross negligence, willful or wanton misconduct, or intentional civil rights violations.
- Z-Axis Metric Is Measured Against the Handset: The FCC's ±3-meter vertical metric compares the reported altitude with the handset's true altitude, and location is delivered as height above ellipsoid (HAE), not mean sea level. Raw barometric pressure readings must be calibrated with local reference data to produce a usable floor estimate.
- Direct PSAP Outage Notification Requirement: A NORS filing to the FCC is not enough. Under 47 CFR § 4.9(h), providers must notify the affected PSAP within 30 minutes of discovering an outage that affects 9-1-1 and follow up within 2 hours.
Under the FCC's wireless Phase II location accuracy rules that grew out of Docket 94-102, what are the horizontal accuracy benchmarks for handset-based positioning technologies (such as Assisted-GPS)?
Under 47 CFR Part 4, what mandatory obligation must a telecommunications service provider fulfill when an unplanned network failure causes a complete loss of 9-1-1 call routing to a primary PSAP lasting longer than 30 minutes?
How does the Tenth Amendment to the United States Constitution delineate regulatory boundaries regarding emergency communications between the Federal Communications Commission (FCC) and local 9-1-1 authorities?