Nena Issue Submission & Charter Form - Nena-Adm-003

NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003 Instructions for NENA ISSUE SUBMISSION FORM: 1. The Originator completes Section 1 and e-mails the form to the NENA Committee Resource Manager (CRM) at [email protected]. 2. Upon approval of the DSC Co-Chairs & HQ Staff1, the CRM publishes the form for 10-day review. 3. The Development Steering Council (DSC) reviews Section 1 along with comments received during the 10-day review and decides whether to accept the Issue according to the criteria described in NENA ADM-002. Acceptance of the Issue does not necessarily include acceptance of the “Requested Outcome or Proposed Solution”. If the Issue is accepted and assigned to a Committee, the CRM fills out Section 2 based on DSC instructions. 4. The Committee Co-Chair(s) and all Subcommittee/Working Group Chairs complete Section 3 (the Working Group Charter) and emails the form to the CRM. 5. The DSC approves the Working Group Charter and the CRM enters the approval date in Section 2. 6. The CRM sends a copy of the updated form to the Originator. 7. The CRM updates Section 2 when the Issue status changes.

NOTE: Some fields on this form will be used to populate the Charter if this Issue is accepted and assigned by the DSC. Section 1 - Issue Details To Be Completed by the Originator Please provide input for all fields Short title (what the Issue may easily be referred to by) Date Submitted: 05/09/2017 911 Apps and IoT Devices Interworking with NG9-1-1 and IoT

COMBINES 06/09/2015 (apps) and 11/30/2016 (IoT) Originator Name Roger Hixson (apps), Paul McLaren (IoT), Randal l Gellens (IoT) and Bob Sherry (apps) Originator Organization NENA (IoT and apps) and Intrado (apps) Originator Email [email protected], [email protected], [email protected] and [email protected] Originator Phone 202-618-4405 (apps - Hixson), 504-208-3911(IoT – McLaren), 858-658-9292 (IoT Gellens) and 630-300-2838 (apps – Sherry) Description of Problem or Opportunity (Provide detailed and clear information. If this is time sensitive or critical

1 See ADM-002 for details surrounding Issue acceptance.

NENA ADM-003, 07/28/2015 Page 1 of 6 NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003 provide an explanation. Smartphone developers are developing apps that they intend to interact with PSAPs to exchange information about an emergency incident. There are currently no standards to assist app developers in this effort. It has been identified that there may be two methods to interwork with the PSAP. One is via an Over the Top (OTT) application that would send requests directly to the PSAP, most likely over the Internet. The other method is to interwork the app through a gateway into NG9-1-1 using NENA’s i3 standard (STA 010). APCO is developing a standard to support connectivity directly to the PSAP in an OTT environment. There is no guidance on how 911 apps can interwork to NG9-1-1. The only technical interface info is embedded in the NENA i3 architecture standard. Furthermore, there are a plethora of devices connecting to the Internet (such as cameras, biometric devices, TVs, dryers, cars, door locks, door bells, fitness trackers, smart scales, etc.) and many more types being added. This Internet of Things (IoT) is providing a wealth of data for users and companies in both real time and historical. The numbers/types of devices, amount of data provided, and connectivity of these devices is increasing dramatically. Such devices can potentially place automatic/manual 9-1-1 calls, or be bridged into a 9-1-1 call placed by a different device. Some of the possible data, such as data and video from a smart door bell, or from a dryer in the event of a fire, can be critical to 9-1-1 and emergency responders. A survey of current devices, future directions, data type and format is needed. Also needed is an initial analysis as to if and when such devices should automatically initiate 9-1-1 calls, under what circumstances, and with what minimum capabilities such devices should place manual 9-1-1 calls. Includes in the analysis should be situations where the person initiating the 9-1-1 call via the device is remote, (e.g., a smart door bell attached to a building alerts an owner located in a different state or country, who initiated a 9-1-1 call, making video and event logs available to the call taker), and how and with which capabilities such devices should be capable of being bridged into 9-1-1 calls placed by other devices. Additionally, initial work in identifying how call takers and responders access data, video, and other information, on or via such devices is needed (such as Dispatch taking to responders over a video doorbell or TV). This work will help determine the impact and benefits IoT devices may have on 9-1-1. Requested Outcome/Proposed Solution (Provide detailed and clear information): Note: The final resolution and disposition of this issue may not conform precisely to the Requested Outcome or Proposed Solution. The Working Group consensus will determine the actual means used to accomplish the intent of the Requested Outcome or Proposed Solution. NENA may develop an apps-specific interface specification, based on i3 content, that would identify how 9-1-1 apps and IoT devices can be gatewayed into NG9-1-1. It would set requirements on the interface in order for sessions to be routed to the appropriate PSAP and establish a dialog between the app user and the Telecommunicator. In addition, NENA may develop white papers and/or operational documents that would define operational considerations for Apps and IoT devices interconnecting with emergency services.

Section 2 – DSC Tracking To be Completed by NENA DSC

Issue Number 20170509

NENA ADM-003, 07/28/2015 Page 2 of 6 NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003 Date Published for 10-Day IoT went out for comments 2/2/2017 Review Apps did not go out for comment as that procedure was not in place at that time. Review Comments IoT 2/28/2017 Date and Reasons for Rejection by the DSC Date Assigned by DSC 07/14/2015

Submit PINS to ANSI? ☐ Yes ☒ No Date PINS Submitted:______Referred To - Who will receive the Issue?: If applicable, which NENA Committee will own this Issue?

☐ Accessibility ☐ Agency Systems ☐ Data Management ☐ Data Structures ☒ Interconnection & Security ☐ NGTPC ☐ PSAP Operations ☐ Public Education & PSAP Training Or specify the internal NENA owner of this Issue ______******************************************************************************************** Or specify which external entity it was referred to:

☐ APCO ☐ ATIS-ESIF ☐ ATIS-PTSC ☐ ATIS-WTSC ☐ IEEE ☐ IETF ☐ NFPA OTHER ______Working Group Assigned To Emerging Topics Subcommittee (If applicable) Estimated/Requested 05/01/2018 Completion Date of draft (if applicable) DSC Instructions to the Working Group (includes supplements or modifications to the Originator’s Requested Outcome) Date the Charter is due back 03/28/2017 to DSC Date Working Group Charter 05/16/2017 Approved Actual Completion Date (to be completed later) Status Updates: link to Scopes & Goals Resolution: (a brief explanation of how the Issue was resolved for closure)

NENA ADM-003, 07/28/2015 Page 3 of 6 NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003 Section 3 – Working Group Charter To Be Completed by the Committee Co-Chairs & all Subcommittee/Working Group Co- Chairs, and approved by the DSC.

Assigned Committee & Working Group (should be based on the name Issue Number Date WG Created used in the Issue Submission form, and include the Parent Committee (from above) (if it is a new WG) name.) 20170509 Interconnection & Security Committee, Emerging Topics Subcommittee, IoT & Apps Working Group Goal/Objective/Deliverable (Describe each goal/objective/deliverable and provide detailed and clear information, based on the accepted Issue.) 1 goal/objective/deliverable: Create an INF describing the impact of IOT devices and emergency calling applications on 9-1-1 #2 goal/objective/deliverable: Create a recommendations document that provides guidance to 9-1-1 professionals, application/device manufactures, and data management/monitoring entities for NENA endorsed methodology for 9-1-1 interaction by IoT devices and emergency calling applications. #3 goal/objective/deliverable: Determine mechanism by which attachments (such as static image and video media) are either conveyed with or made available within a 9-1-1 call. Determine how data provided by applications or devices is made available to and accessed by call takers and responders. #4 goal/objective/deliverable: Determine mechanism (signaling etc.) by which applications and devices place automatic or manual 9-1-1 calls, including situations where the person initiating the call is remote, or gets bridged into a 9-1-1 call. Importance (Rank each goal/objective/deliverable as Essential, Important, or Desirable as follows;  Essential – required for something else to succeed

 Important – helpful toward the success of another work effort

 Desirable – asset for other reasons #1 goal/objective/deliverable is ranked: Important : #2 goal/objective/deliverable is ranked: Desireable #3 goal/objective/deliverable is ranked: Essential #4 goal/objective/deliverable is ranked: Essential

Schedule (Considering the Estimated Completion Date for the Issue, establish when each goal/objective/deliverable should be met or accomplished, and provide detailed and clear information, based on the accepted Issue. If applicable, list any intermediate schedule milestones, e.g., “Outline complete”, “First draft complete”.) #1 goal/objective/deliverable: Create a draft INF describing the impact of IOT devices and emergency calling applications on 9-1-1 by 12/1/17. Draft accepted as an INF by 3/31/18. #2 goal/objective/deliverable: Create a draft recommendations document that provides guidance to 9-1-1 professionals, application/device manufactures, and data management/monitoring entities for NENA endorsed methodology for 9-1-1 interaction by IoT devices and emergency calling applications by 4/30/18. Draft accepted as a final version by 7/31/18 #3 goal/objective/deliverable: Determine the appropriate i3 mechanism by which attachments (such as static image and video media) are either conveyed with or made available within a 9-1-1 call and determine how data provided by applications or devices is made available to and accessed by call takers and responders by 8/31/18. Note – similar work is already underway within i3 – synergies between the two will be leveraged. #4 goal/objective/deliverable: Determine mechanism (signaling etc.) by which applications and devices place automatic or manual 9-1-1 calls, including situations where the person initiating the call is remote, or gets bridged into a 9-1-1 call by 12/31/18. Dependencies (Identify all known dependencies for achieving success, e.g., completion of work in other committees or other organizations outside of NENA.)

Dependent on alignment with recommendations and requirements in i3v2/3

Chair(s) (Who will serve as the Chair(s) for the group performing this work? Provide name, phone and email.)

Paul McLaren and Randy Gellens

Editor(s) (Who will serve as the Editor(s) for the group performing this work? Provide name, phone and email.)

Participating Organizations (Identify all outside organizations that will be needed for success of the identified goals/objectives/deliverables, e.g., APCO, ATIS, NEIM, IHIS, etc.)

None noted at this time.

Subject Matter Expertise Needed (Identify the types of SMEs needed to achieve success.) i3, SIP, IoT developers, OTT app developers

Required Resources (Identify the types of non-human resources needed to achieve success, e.g., list server, web site, etc.) NENA Workspace, TurboBridge and Join.Me Initial Work Schedule Plan (Identify the initial call & meeting schedule, e.g., every Tuesday at 10am EASTERN.) TBD Status Reporting Schedule (The Charter serves as the guiding document to drive work activities toward established goals. Additionally, it serves as a tool to ensure timely status reports to the DSC throughout the work interval. Depending on the nature of the work, and its impact on other work, the timing of status reports may differ among WG activities. This field is to be used by the DSC to establish the timing of WG status reports to the DSC or designated Project Mgr(s).) Monthly Scopes & Goals Measurement (How will each goal/objective/deliverable be evaluated? Use quantitative and/or qualitative measures which are descriptive of the measurement criteria) #1 goal/objective/deliverable: Initial draft, final draft, final document approved by NENA #2 goal/objective/deliverable: Initial draft, final draft #3 goal/objective/deliverable: Initial evaluation, conclusion, determination on where this information should reside #4 goal/objective/deliverable: Initial evaluation, conclusion, determination on where this information should reside Other?

NENA ADM-003, 07/28/2015 Page 6 of 6