2.2 Device-Based Location, Supplemental Data & RapidSOS

2.2 Device-Based Location, Supplemental Data & RapidSOS

Quick Answer: Device-Based Hybrid Location (DBHL)—operationalized through Apple's Hybridized Emergency Location (HELO, with AML where supported) and Google's Emergency Location Service (ELS)—overcomes the severe indoor latency and accuracy failures of legacy Phase II wireless triangulation by executing multi-sensor fusion directly on the smartphone. By combining GNSS, crowdsourced Wi-Fi BSSID scanning, Bluetooth Low Energy (BLE) beacons, cellular signals, and barometric altimeters, the handset derives a high-confidence horizontal coordinate fix within 3 to 8 seconds and vertical elevation within +/- 3 meters. Supplemental data clearinghouses like RapidSOS ingest this rich telemetry out-of-band and display it directly on PSAP CAD and CPE screens via secure RESTful APIs. Crucially for ENP certification, supplemental clearinghouse telemetry is non-authoritative and advisory; it does NOT route the 9-1-1 call through the selective router or NG911 ECRF.

Over 80% of 9-1-1 calls in the United States originate from wireless devices, and the overwhelming majority of those calls are placed from inside residential homes, multi-tenant apartment complexes, commercial high-rises, and industrial facilities. For public safety leadership, bridging the gap between legacy cellular network limitations and modern consumer smartphone capabilities represents one of the most vital technical transformations in modern emergency communications.

---

1. The Legacy Phase II Dilemma: Indoor Attenuation, Latency & Uncertainty

While FCC Docket 94-102 established groundbreaking standards in the late 1990s, the legacy Phase II architecture was fundamentally designed around outdoor macro-cellular environments. In modern indoor emergency scenarios, legacy Phase II exhibits three severe operational failures:

1. The RF Attenuation / "Faraday Cage" Effect

Carrier Assisted GPS (A-GPS) relies on direct line-of-sight radio reception from at least four Global Positioning System (GNSS) satellites in Earth orbit. Modern commercial and residential building construction—utilizing reinforced concrete, metal-coated structural beams, foil-backed thermal insulation, and metallized low-emissivity (low-E) window glass—attenuates satellite microwave radio signals by 20 to 30 dB. When a caller dials 9-1-1 from an interior office, elevator shaft, or basement apartment, GNSS signals fail to penetrate the structure. The carrier network is forced to fall back to network multilateration (U-TDOA) or coarse Phase I cell tower sector centroid data.

2. Carrier Positioning Latency & Time-to-First-Fix (TTFF)

In legacy Phase II, the mobile phone does not calculate its final coordinates independently. Instead, a complex signaling handshake occurs: the Mobile Switching Center (MSC) queries the Position Determining Entity (PDE) or Location Determining Entity (LDE), which commands the phone to collect raw GPS pseudo-ranges and transmit them upstream across cellular control channels. This carrier-side calculation frequently takes 15 to 45 seconds before delivering an initial Phase II fix to the PSAP. In acute medical crises, active violence, or structural fires, a 30-second delay in location retrieval can be fatal.

3. Coarse Circular and Elliptical Uncertainty

Even when carrier Phase II resolves an indoor coordinate solution, the resulting uncertainty radius ($h$-accuracy) frequently spans 150 to 500 meters. When rendered on a CAD map, a 300-meter uncertainty circle encompasses multiple city blocks, several high-density apartment buildings, and hundreds of individual living units. Telecommunicators cannot provide actionable staging instructions to responding units based on an uncertainty boundary that spans an entire neighborhood.

---

2. Device-Based Hybrid Location (DBHL): Handset Sensor Fusion

To overcome the physical barriers of satellite attenuation and carrier processing latency, Apple and Google developed Device-Based Hybrid Location (DBHL). DBHL shifts the computational burden from external carrier network servers directly to the smartphone's high-speed multicore processor, executing advanced multi-sensor data fusion algorithms locally on the device.

+-----------------------------------------------------------------------------------------+
|                    DEVICE-BASED HYBRID LOCATION (DBHL) SENSOR FUSION                    |
+-----------------------------------------------------------------------------------------+
|  [Multi-GNSS Engine]    [Wi-Fi AP Scanning]    [Bluetooth Low Energy]   [Barometric MEMS]|
|  GPS, GLONASS,          802.11 BSSID MAC       BLE Proximity Beacons    Atmospheric      |
|  Galileo, BeiDou        Crowdsourced Cache     (Retail, Transit, Malls) Pressure (HAGL)  |
+-----------------------------------------------------------------------------------------+
                                             │
                                             ▼
                       +-------------------------------------------+
                       |  ON-DEVICE SENSOR FUSION ENGINE           |
                       |  (Apple iOS AML / Android Google ELS)     |
                       |  Calculates Fix in 3 to 8 Seconds         |
                       +-------------------------------------------+
                                             │
                     ┌───────────────────────┴───────────────────────┐
                     ▼                                               ▼
       [In-Band Voice Channel]                         [Out-of-Band Data Channel]
       Cellular Carrier -> Tandem/ESInet               Direct Encrypted HTTPS / TLS
       Routes Voice Call to PSAP                       Emergency Data Clearinghouse (RapidSOS)

Apple Hybridized Emergency Location (HELO) & Advanced Mobile Location (AML)

Advanced Mobile Location (AML) originated in the United Kingdom and is now specified by the European Telecommunications Standards Institute (ETSI). Apple supports AML where emergency authorities accept it, and in the United States delivers device-based hybrid location for 9-1-1 calls as Hybridized Emergency Location (HELO). The iOS implementation works as follows:

1. Automatic Activation: When an iOS device detects that an emergency dial string (such as 9-1-1 or 1-1-2) has been dialed, the operating system automatically forces on high-precision location hardware—including GNSS receivers, Wi-Fi scanning, and Bluetooth radios—even if the subscriber had previously disabled location services in privacy settings to preserve battery.
2. Local Fusion: The device computes its position in 3 to 8 seconds using all available terrestrial and satellite signals.
3. Payload Transmission: The device packages coordinates, horizontal uncertainty, elevation, and direction of travel into an encrypted Data SMS or secure HTTPS POST payload transmitted directly to public safety endpoints or authorized emergency data clearinghouses.
4. Privacy Restoration: Once the call terminates, iOS automatically powers down the auxiliary location radios and restores the subscriber's prior privacy and battery configuration.

Google Emergency Location Service (ELS)

Google integrated Emergency Location Service (ELS) natively into Android via Google Play Services. ELS leverages Google's proprietary Fused Location Provider (FLP). Upon 9-1-1 call initiation, ELS combines GNSS signals, cellular timing advances, ambient Wi-Fi signal signatures, and onboard motion sensors. ELS packages latitude, longitude, vertical accuracy, and bearing into an HTTPS payload transmitted over cellular data (LTE/5G) or Wi-Fi directly to authorized public safety endpoints and clearinghouses.

---

3. Terrestrial Positioning Signals: Wi-Fi, Bluetooth & Inertial Navigation

DBHL achieves sub-room precision indoors because it does not depend exclusively on satellites orbiting 12,000 miles away. Instead, it measures terrestrial radio signals that blanket indoor environments:

Wi-Fi Positioning Systems (WPS)

In urban high-rises and residential neighborhoods, dozens of Wi-Fi access points (APs) continuously broadcast 802.11 beacon frames containing their Basic Service Set Identifier (BSSID), which is the hardware MAC address of the wireless router. Modern mobile operating systems continuously scan nearby BSSIDs and their associated Received Signal Strength Indication (RSSI) values.

• The mobile OS cross-references detected BSSIDs against vast, crowdsourced geographic databases maintained by Apple and Google.
• No Wi-Fi Connection Required: Crucially, the phone does not need to connect to the Wi-Fi network, nor does it require network passwords. The simple passive radio detection of two or three stationary BSSIDs allows the device to execute mathematical trilateration, deriving horizontal accuracy within 5 to 15 meters.

Bluetooth Low Energy (BLE) Beacons

In commercial spaces such as shopping malls, airports, transit hubs, and university complexes, fixed Bluetooth Low Energy (BLE) beacons broadcast continuous proximity advertisements. Mobile devices measure signal attenuation (path loss) to establish micro-proximity within 1 to 3 meters.

Cellular Multilateration & Inertial Navigation Systems (INS)

The smartphone fuses downlink cellular measurements (timing advance and reference signal received power [RSRP] from surrounding macro and small-cell towers) with internal Inertial Measurement Units (IMU) comprising accelerometers, gyroscopes, and magnetometers. If satellite and Wi-Fi signals temporarily drop out, the IMU executes dead reckoning, tracking the user's velocity, steps, and heading.

---

4. The Vertical Frontier: Barometric Pressure & The FCC Z-Axis Mandate

For the first five decades of 9-1-1, emergency location was strictly two-dimensional ($x, y$ coordinates). While latitude and longitude effectively identify a single-family suburban home, they fail in a 50-story high-rise. Responders arriving at the latitude and longitude coordinates are delivered to the building lobby or sidewalk footprint, leaving them blind to which floor the victim occupies.

Barometric Pressure Sensor Mechanics

Modern smartphones contain micro-electro-mechanical systems (MEMS) barometric pressure sensors capable of detecting atmospheric pressure shifts as small as 1 to 2 Pascals, corresponding to vertical elevation changes of less than 1 meter (approximately 3 feet). However, atmospheric pressure fluctuates constantly due to dynamic weather fronts, ambient temperature shifts, and high-rise building HVAC cycling. Therefore, raw barometric readings from an isolated smartphone cannot determine elevation reliably.

To derive accurate vertical height, the device's barometric reading must be compared against a real-time terrestrial reference barometer network. By subtracting localized weather-induced pressure fluctuations measured by fixed ground calibration stations, the positioning engine calculates the handset's true Height Above Ellipsoid (HAE), which is mathematically converted into Height Above Mean Sea Level (HAMSL) and Height Above Ground Level (HAGL), ultimately resolving to a specific building story.

The FCC Z-Axis Mandate (PS Docket 07-114)

Recognizing vertical positioning as a life-safety imperative, the FCC built its indoor location accuracy rules in PS Docket 07-114: the Fourth Report and Order (2015) set the phased framework, the Fifth Report and Order (2019) adopted the vertical metric, and the Sixth Report and Order (2020) extended it nationwide:

• Vertical Metric: CMRS providers must deliver z-axis location within ±3 meters relative to the handset for 80% of wireless 9-1-1 calls placed from z-axis-capable devices, reported as height above ellipsoid (HAE) and accompanied by floor level where available. Delivering dispatchable location is an accepted alternative.
• Operational Floor Equivalent: The FCC specifically codified the +/- 3-meter tolerance because 3 meters corresponds to the standard floor-to-floor architectural height of commercial and multi-family residential buildings, enabling telecommunicators to identify the caller's exact floor.
• Phased Geographic Deployment: Nationwide carriers had to meet the z-axis metric in the top 25 Cellular Market Areas (CMAs) by April 3, 2021 and the top 50 CMAs by April 3, 2023. The Sixth Report and Order extended the requirement nationwide by April 2025 for nationwide carriers and April 2026 for non-nationwide carriers.
• Location-Based Routing (2024): In a separate January 2024 order (FCC 24-4), the FCC required wireless providers to route 9-1-1 voice calls using device-based location when that location is timely and accurate to within 165 meters at 90% confidence: nationwide carriers by November 13, 2024, and non-nationwide carriers (and all providers for RTT) by May 13, 2026. This carrier-delivered routing location is different from the advisory clearinghouse data discussed below.

---

5. Supplemental Data Clearinghouses: The RapidSOS Architecture

While smartphones generate precise DBHL coordinates and z-axis telemetry, legacy telecommunications networks and E9-1-1 selective routers were engineered in the 20th century to carry only 8 to 20 digits of ANI and retrieve 512-character tabular text ALI records. Legacy networks cannot transmit rich, streaming IP data payloads.

To deliver this data to PSAPs without waiting decades for universal NG911 network replacement, public safety pioneered Supplemental Emergency Data Clearinghouses—most prominently the RapidSOS Clearinghouse.

The Dual-Path Architecture: In-Band Voice vs. Out-of-Band Data

The clearinghouse operates on a dual-path architecture that completely decouples voice delivery from rich emergency data:

1. In-Band Voice Path (Regulated Telecommunications Carrier): The 9-1-1 voice call travels across the wireless carrier's cellular network, traverses the legacy E9-1-1 Selective Router (or NG911 ESInet), and terminates at the PSAP's call handling Customer Premises Equipment (CPE) alongside traditional ANI and carrier Phase I/Phase II ALI.
2. Out-of-Band Data Path (Secure IP Clearinghouse): Concurrently, the handset's OS (Apple HELO/AML or Google ELS) establishes an encrypted HTTPS connection over commercial cellular data (LTE/5G) or Wi-Fi to the RapidSOS Clearinghouse, transmitting high-precision DBHL coordinates, vertical altitude, horizontal uncertainty, and device telemetry.
3. PSAP CAD/CPE Ingestion: The PSAP's CAD or CPE mapping software detects the incoming 10-digit ANI/callback number over the voice trunk. The CAD/CPE immediately fires an automated, secure RESTful API query to the clearinghouse using the 10-digit number as the lookup key. Within 1 to 3 seconds, the clearinghouse returns the device telemetry, plotting a high-confidence pin on the telecommunicator's map alongside the CAD incident entry window.

+-------------------------------------------------------------------------+
|                   RAPIDSOS DUAL-PATH ARCHITECTURAL FLOW                 |
+-------------------------------------------------------------------------+
|                                                                         |
|   [ Mobile Handset ]                                                    |
|         │                                                               |
|         ├───────── [1] In-Band Voice Call (Cellular Voice Trunk) ───┐   |
|         │          Carries Voice Audio + Carrier ANI                │   |
|         │                                                           ▼   |
|         │                                              [Selective Router]|
|         │                                                           │   |
|         │                                                           ▼   |
|         │                                                   [PSAP Console]|
|         │                                                   Answers Call |
|         │                                                   Receives ANI │
|         │                                                           │   |
|         └───────── [2] Out-of-Band Data (HTTPS / TLS 1.3) ──┐       │   |
|                    Carries DBHL, Z-Axis, Telematics         │       │   |
|                                                             ▼       │   |
|                                                   [RapidSOS Core]   │   |
|                                                   Clearinghouse     │   |
|                                                             │       │   |
|                                                             ▼       │   |
|                                                   [API Query Link] ◄┘   |
|                                                   CAD queries API       |
|                                                   using 10-digit ANI    |
|                                                   Displays 5m Pin + CAD |
+-------------------------------------------------------------------------+

Supplemental Data Telemetry Capabilities

Beyond raw horizontal and vertical coordinates, clearinghouse architectures ingest and present multi-source emergency payloads:

• Dynamic Real-Time Breadcrumbing: For moving callers (such as vehicular pursuits, abductions, or lost hikers), the clearinghouse streams continuous location coordinates every few seconds, generating a dynamic breadcrumb trail on the CAD map without requiring manual ALI re-bids.
• Advanced Automatic Crash Notification (AACN): Connected vehicles (e.g., OnStar, Ford, SiriusXM Connected Vehicle) stream crash telemetry directly to the clearinghouse, providing telecommunicators with delta-V (force of impact), principal direction of force (PDOF), rollover status, seatbelt latch status, and airbag deployment.
• User-Managed Emergency Health Profiles: Secure integration with personal health records (e.g., Apple Medical ID, Emergency Health Profile) presenting critical medical conditions, severe allergies, blood types, mobility impairments, emergency contacts, and primary language preferences.
• Commercial Building & Sensor IoT Data: Commercial fire alarm activations, hazardous chemical sensor readings, and digital architectural building floor plans pushed directly to the call-taker's console.

---

6. Authoritative Routing vs. Supplemental Advisory Data: ENP Imperative

For the ENP examination and PSAP standard operating procedures (SOPs), public safety leadership must maintain a strict, legally grounded boundary between authoritative location and supplemental data.

Authoritative Location

Authoritative location is the location delivered by the originating telecommunications carrier through regulated 9-1-1 network paths (the legacy Selective Router and tabular ALI database, or an NG911 Emergency Call Routing Function [ECRF] using a Presence Information Data Format - Location Object [PIDF-LO]).

• Legal Liability: Authoritative location carries statutory regulatory liability governed by FCC Part 9 rules and state public utility commissions.
• Call Routing Exclusivity: Authoritative location is the ONLY data permitted to make call routing decisions to steer the 9-1-1 call to the primary PSAP. A call cannot be routed across network tandems based on supplemental clearinghouse telemetry.

Supplemental Advisory Data

Supplemental data delivered via commercial clearinghouses (e.g., RapidSOS) is legally defined as non-authoritative, advisory information.

• Regulatory Standing: Clearinghouses are commercial emergency data brokers operating over best-effort public and private IP clouds; they are not regulated telecommunications common carriers.
• Call Routing Prohibition: Supplemental data does NOT route the 9-1-1 call. Call handling systems cannot alter the ingress routing of a 9-1-1 call based solely on clearinghouse coordinates.

Operational Discrepancy Protocols

When a telecommunicator observes a significant geographic discrepancy between the carrier's authoritative ALI (e.g., a tower sector 2 miles away with an uncertainty of 800 meters) and a supplemental clearinghouse pin (e.g., displaying a specific residential rooftop with an uncertainty of 6 meters):

1. Verbal Confirmation: The telecommunicator must verbally interrogate the caller: "I show your phone in the vicinity of 742 Evergreen Terrace, is that where the emergency is?"
2. Tactical Dispatch for Unresponsive Callers: If the caller is unresponsive, choking, incapacitated, or disconnected, agency SOPs generally authorize dispatching responders to the high-confidence clearinghouse coordinates while documenting the discrepancy in the CAD narrative.
3. Mandatory ALI Re-Bid: The telecommunicator must still execute standard ALI re-bids to update the official carrier record for evidentiary and legal archiving.
4. Call Transfer Constraints: If transferring the call to an outside agency over legacy trunks, only the authoritative carrier ALI will transfer automatically. Telecommunicators must verbally relay the supplemental clearinghouse coordinates to the receiving agency unless both centers share an integrated CAD-to-CAD clearinghouse federation.