Verizon had initiated location-based routing for 56 public safety answering points nationwide as of July 7, with another 244 in progress, said a filing posted Thursday in docket 18-64. Verizon said it met with FCC Public Safety Bureau staff at the bureau’s request. “To determine whether device-based hybrid location information provided by the device during a call is adequate for routing, Verizon uses an accuracy threshold of 200 meters maximum horizontal uncertainty with confidence of 90 percent,” the filing said: “Verizon uniformly applies this threshold for all PSAPs, which was derived based on testing and analysis across many different jurisdictions and morphologies.”
Industry groups supported a March petition by the Competitive Carriers Association seeking tweaks to the FCC’s 911 outage reporting rules, approved 4-0 by commissioners last year (see 2211170051). APCO and the Boulder Regional Emergency Telephone Service Authority (BRETSA) opposed the petition in the initial comment round (see 2306270045). But most groups waited for the reply round to weigh in.
CTIA and member companies raised concerns about an FCC proposal that carriers more precisely route wireless 911 calls and texts to public safety answering points through location-based routing (LBR) (see 2212210047), in a meeting with staff from FCC Public Safety and Wireless bureaus. “As wireless providers take different approaches to implementing LBR, CTIA noted that a wireless providers’ obligation to use LBR should be premised upon a valid PSAP request that includes the provision of the shapefiles, which are necessary for wireless providers to tailor their networks to unique geographies and PSAP boundaries,” said a filing posted Monday in docket 18-64: “For these reasons, CTIA also noted that non-nationwide wireless providers should have more time to deploy LBR within their networks than proposed in the NPRM.” CTIA also offered counsel on rules for providing location information with next-generation text solutions. The group “encouraged the Commission to focus on the use of LBR for real-time text and ensure that wireless providers have the flexibility to implement LBR for text-to-911 in ways that are consistent with their unique network and handset configurations.” AT&T, Dish Network, Southern Linc, T-Mobile and Verizon participated in the meeting.
Public safety answering points continued to have a 30% increase in call volume in June, apparently tied to interface updates to some Android phones (see 2306210030), the National Emergency Number Association said. “NENA staff has been working with Google and Original Equipment Manufacturers (OEMs) regarding a recent and large uptick in accidental calls caused by changes to default behavior in some devices for the Emergency SOS feature in Android,” the group said last week. Android operating system software from both Google and the OEMs have updates to address the issue, NENA said: “For multiple major OEMs, the updates have already been pushed to the public and installed on many devices. It will take some time for updates to reach a critical mass of handsets, and for users to install them, for the issue to be completely addressed. This may take weeks to months. NENA advises all Android users to update their OS to the latest version.”
ATIS supported a March petition by the Competitive Carriers Association seeking tweaks to the FCC’s 911 outage reporting rules, approved 4-0 by commissioners last year (see 2211170051). Comments were due Monday in docket 15-80 (see 2306140057). ATIS’ Network Reliability Steering Committee “believes that it is infeasible to comply with the recently-adopted reporting rules” requiring carriers to provide 911 special facilities with all available material information they have about an outage within 30 minutes of discovery, said a filing posted Tuesday. “Until there is notification from a third-party (such as from a vendor or another service provider etc.), originating service providers would not know of an outage or its impact,” ATIS said: “Even after an originating service provider receives notification of an outage, 30 minutes is a challenging deadline. … In this very short window of time, providers likely will not know the root cause, the outage’s extent, or be able to estimate when service would be restored, and in some cases may not be able to identify the affected” public safety answering points. The Boulder Regional Emergency Telephone Service Authority opposed the petition. “If providers are unwilling or unable to monitor their systems and traffic, and timely report outages, then they should authorize or assign third-party network providers on which their services are dependent to provide outage notifications, and supply those third-party network providers the information they need to fully report the impact of the outage,” the Colorado agency said. APCO also opposed the reconsideration petition (see 2306260062).
The rollout of next-generation 911 to public safety answering points remains at the top of the agenda for the National Emergency Number Association and its members, CEO Brian Fontes said in an interview. NENA's annual meeting is this week in Grapevine, Texas. Fontes warned against a "patchwork" of service across the U.S.
The FCC's proposal to limit mobile supplemental coverage from space (SCS) operations to co-channel licenses held by one party in geographically independent areas (GIA) is getting pushback from some satellite and terrestrial interests, per NPRM reply comments in docket 23-65 Tuesday. There was wireless and satellite disagreement on whether a waiver system suffices or if the agency needs SCS rules. The SCS NPRM was adopted 4-0 in March (see 2303160009) and the wireless industry argued in initial comments SCS rules are premature (see 2305150007).
Washington state regulators slapped Lumen with nearly $1.32 million in penalties for a December 2018 outage that resulted in at least 13,000 dropped or incomplete 911 calls. The Washington Utilities and Transportation Commission issued a final order Friday in docket UT-181051. "CenturyLink committed at least 13,000 violations of” a state rule “by failing to render prompt, expeditious, and efficient service; to keep its facilities, instrumentalities, and equipment in good condition and repair; and to ensure that its appliances, instrumentalities, and services are modern, adequate, sufficient, and efficient,” said the Washington UTC, assessing $100 per violation. Also, the UTC assessed $1,000 for each of 15 violations of a separate state regulation requiring telecom companies to promptly notify the commission and affected public safety answering points. “The service disruption lasting 49 hours and 32 minutes in December 2018 was a serious health and safety threat to Washington state residents,” the UTC said. “CenturyLink failed both in its obligations under statutory provisions and Commission rules to adequately manage and provide 911 service.” The penalty was lower than the $7.2 million penalty sought by Attorney General Bob Ferguson (D) in 2021 (see 2112160048). Lumen cooperated with the state commission’s investigation, a Lumen spokesperson said Monday: “We know that when someone calls 911, seconds count, and we take that responsibility seriously.”
The FCC’s final 42 GHz NPRM, released Friday, got few changes from the draft proposed by Chairwoman Jessica Rosenworcel, as expected (see 2306020048). Commissioners approved the 42 GHz item 4-0 Thursday (see 2306080042). The final version of the next-generation 911 NPRM adds numerous questions to the draft and got the most tweaks among the items approved Thursday. No major changes were made to the final NPRM on robocalls and robotexts, which were also approved unanimously (see 2306080043).
The FCC approved 4-0 NPRMs on expediting the transition to next-generation 911 and giving consumers more choice on the robocalls and robotexts they’ll receive (see 2305180069). Both were approved with limited comments from commissioners.