Keeping 911 call takers safe is critical to maintaining emergency call systems during the U.S. COVID-19 outbreak, said stakeholders in interviews this week. APCO, the National Emergency Number Association and National Association of State 911 Administrators (NASNA) leaders are less worried about a potential surge in calls as there might be in a hurricane. Wider deployment of next-generation 911 would give call takers and responders more flexibility, they said.

The FCC has a plan for dealing with a pandemic if necessary, said Chairman Ajit Pai and others answering our queries during news conferences Friday. So far, the main coronavirus effect on the regulator has been cancelation of an annual wireless conference, members told us. Commissioner Geoffrey Starks worries about impacts on 911 systems and about getting more people connected to residential broadband.

House Communications Subcommittee leaders are eyeing an early March markup for the Reinforcing and Evaluating Service Integrity, Local Infrastructure and Emergency Notification for Today’s (Resilient) Networks Act (HR-5926) and at least some of the seven other public safety communications measures it will examine Thursday (see 2002200060), industry lobbyists told us. Communications and public safety stakeholders endorsed several of the measures in written testimony. HR-5926 didn’t get universal praise. The hearing begins at 10:30 a.m. in 2322 Rayburn.

The National Emergency Number Association warned floor-level data could be hard to obtain, in response to a Further NPRM on advanced vertical location, mapping and 911 services. Comments were due last week and posted through Monday in docket 07-114. “Lack of accurate, reliable floor level records represents a fundamental challenge to vertical location in the public safety setting,” the group said: “NENA has spoken with numerous participants in the real estate and indoor location industry; all agree that tax assessment records -- the most common and widely used ‘first pass’ source of building floor levels -- are roughly only 50% reliable, and nearly always require validation via another surveying method. In many jurisdictions, tax assessment records require merely square footage numbers for taxation purposes, so floor level data fields are often either left blank or inaccurately populated.” Be “mindful of the unique challenges facing rural carriers in deploying these technologies,” the Competitive Carriers Association asked. Google said the FCC should change its rules to “promote rather than discourage delivery of floor data to public safety answering points, and also encourage the use of testing protocols that account for real-world operating conditions and concerns.” T-Mobile advised flexibility. “We should not repeat the mistakes of the past, as with the initial deployments of horizontal 911 location solutions that relied on technology developed and implemented specifically for 911,” the carrier said: “Those solutions became obsolete and resulted in public safety being left behind, even as location technologies developed for the commercial market continued to develop and improve.”

National Emergency Number Association members began their annual Capitol Hill meetings Wednesday to urge Congress to pass the 911 Supporting Accurate Views of Emergency Services Act (HR-1629/S-1015) and Next Generation 9-1-1 Act (HR-2760/S-1479). HR-1629/S-1015 would change the federal government's classification of public safety call-takers and dispatchers to "protective service occupations" (see 1904050054). HR-2760/S-1479 would provide $12 billion in federal grants for NG-911 projects and directs NTIA to provide further technical assistance while also maintaining state and local control of 911 systems. Democrats included the bill’s text (see 1905220076) in their Leading Infrastructure for Tomorrow’s (Lift) America Act (HR-2741), which NENA also supports. Lead HR-1629 sponsor Rep. Norma Torres, D-Calif., urged NENA members before their meetings to counter opponents’ arguments against the measure, including that it could increase personnel costs due to a change in dispatchers’ job classification. The bill “comes with zero costs,” leaving it up to government agencies to decide whether the change in job classification should lead to higher pay for dispatchers, Torres said at the event. She noted OMB concerns torpedoed an effort to attach the text of HR-1629 to the FY 2020 National Defense Authorization Act (see 1912120061).

The National Emergency Number Association launched an NG9-1-1 Interoperability Oversight Commission. NENA said Wednesday it and other stakeholders will work together on the commission, which will address next-generation 911 issues, including “the need for Public Key Infrastructure to manage secure credentials within the 9-1-1 industry.” NENA will have “no direct control … allowing for fully independent oversight,” said Brandon Abley, NENA director-technical issues. “We’re following the exact same model used in other critical industries.”

Five states diverted nearly $198 million, or 7.6 percent of all 911 fee revenue, for unrelated purposes in 2018, the FCC reported. That dropped about $87 million from 2017. FCC members said Thursday that any reshuffling is inappropriate.

Google said the FCC should consider allowing carriers to transmit information on the floor level of a wireless call to 911 as an alternative to providing height above ellipsoid (HAE) data. Commissioners are to vote on an order Friday (see 1911130030). “An HAE estimate may not provide actionable information in the short term, particularly with regard to identifying which floor to search,” Google said in a filing posted Monday in docket 07-114: Google understands that “not every person in public safety is (or is on a clear path to be) equipped with technology capable of interpreting HAE information.” The National Emergency Number Association disagreed. “A handset’s location, including z-axis, must be delivered to the 9-1-1 system in its original format,” NENA said. “Google’s proposal -- to the extent it removes z-axis HAE from the location payload -- would reduce overall vertical location accuracy and upend the marketplace for downstream mapping and location solutions, disrupting many of the benefits of a ubiquitous standard for vertical elevation measurement.” NENA said “the vast majority of organizations representing public safety” support the z-axis mandate. A Monday news release from the FCC chairman's office laid out public safety support for the z-axis mandate.

Growing use of 5G networks for emergency services raises security issues that must be addressed, stakeholders said in recent interviews. Emergency communications systems are subject to hacking, jamming, human error and poor software development, they said. Policies that encourage reliability and security are key, said National Emergency Number Association (NENA) Technical Issues Director Brandon Abley.

The National Emergency Number Association said the FCC should require carriers to be able to locate the vertical location of wireless callers. NENA opposes CTIA’s “phased in” approach (see 1910100030), it told an aide to Commissioner Geoffrey Starks, said a filing in docket 07-114, posted Friday. “Emphasizing public safety’s sensitivity to timeline slip, we noted that the proposed benchmarks have been in place since the Commission’s 2015 Roadmap,” NENA said. But NENA agrees with CTIA that the national emergency address database faces challenges. “We remain concerned that the NEAD could generate dangerously inaccurate location results for public safety, and that its compliance regime creates the potential for vast swaths of unserved 9-1-1 callers,” the group said. Top officials at NextNav met with Public Safety Bureau staff on the proposed requirement. “A major point of discussion during the meeting was the manner in which the Commission should determine compliance with its vertical location requirements in terms of handset penetration,” the company said: “The discussion included the definition of ‘z-axis capable devices’ and whether this could be defined as handsets manufactured after a certain date that include appropriate hardware components, such as a barometric pressure sensor or other capable component necessary to calculate altitude.”