Text to 9-1-1 Requirements

3.3 Text to 9-1-1 Requirements

The Board is looking for Respondents to provide a hosted solution for the processing of text-to-9-1-1 messages on Respondents proposed ESInet.

The Board is seeking a text to 9-1-1 emergency telecommunications system that shall possess the highest degree of resiliency, reliability, redundancy, and service availability and conforms to current and evolving industry standard.

The system shall support the delivery of 911 text calls to all participating PSAPs located throughout Indiana.

Functionally the Board’s desire is to have emergency text messages (text-to-9-1-1) from all wireless carriers aggregated from Respondents’ proposed solution and forwarded to the appropriate PSAP.

Conceptually the solution will allow a subscriber to a wireless service in the U.S. to send an emergency text to 9-1-1 while in the confines of the State of Indiana and that emergency text will be sent to the appropriate PSAP for answering and processing.

Respondents proposed solution(s) shall aggregate incoming Short Message Service (SMS) text messages from the public through one interface to all Text Control Centers (TCCs) provided by wireless carriers/vendors and distribute the text message to the appropriate Public Safety Answering Point (PSAP) in the format required by that PSAP (web browser, TTY, Direct IP interface).

Respondents proposed solution(s) shall minimize interconnection points between Respondents proposed solution and the PSAP by providing a single content distribution node from the aggregator solution to the PSAP interface.

Such an interface node shall be compatible with all NENA i3 CPE, TTY, and Web-based text displays.

Respondents proposed solution(s) shall only require that a person requiring emergency assistance enter the short code ‘9 1 1’ in their wireless device in order to have an emergency text message sent to the PSAP.

The use of any other short code to send emergency text messages is not required nor shall there be any need for a public person to register their device in order to text 9-1-1 within the defined jurisdiction.

Respondents proposed solution(s), through a distribution method, shall allow messages to be transferred between adjoining PSAPs (primary and secondary) that use a web-based browser or NENA i3 CPE interfaces.

Respondents proposed solution(s) shall provide through the distribution method the ability to provide TTY transfer of SMS texts between TTY PSAPs on the same selective router.

Respondents proposed solution(s) should provide an Aggregator function that:

• Will aggregate text-to-9-1-1 messages from multiple TCCs into a single message stream for distribution to the PSAPs

• Supports any ATIS compliant text-enabled CPE interface

• Supports transfer of text sessions between different interfaces
Respondents proposed solution(s) should provide a Distributor function that:

• Receives text-to-9-1-1 messages from the Aggregator and uses the ESRP/ECRF to route the message to the destination PSAP for the PSAPs served by the Distribution server.

• The Distributor includes:

o TTY Interface – to handle conversion of a text message to a TTY stream for interfacing to a selective router through an Emergency Services Gateway (ESGW)

o Web Portal – contains a portal for the web-based Respondents solution for use by the call taker

o SIP/MSRP Interface – interface between the Aggregator and the NENA i3 ESInets or MSRP CPE at the PSAP.

3.3.1 Data Collection and Reporting

Quality of service information should be accessible through Respondents’ maintenance function.

Respondents shall provide diagrams for their proposed solution showing:

• System connectivity

• System NG9-1-1 functionality including connectivity to network

• Intelligent workstation equipment

3.3.2 PSAP Graphical User Interface and Text Status Windows (browser method)

The User interface proposed by Respondents solution must utilize Windows Graphical User Interface (GUI) interfaces using drop-down boxes, check boxes, text boxes, radio buttons. Etc. to facilitate user friendly data entry and editing.

The Intelligent Workstation shall present the text-call-taker, at a minimum, with the status of the following categories:

• Number of Active Text-to-9-1-1 Calls

• Number of Text-to-9-1-1 Calls on Hold

• Number of Text-to-9-1-1 Calls ‘Ringing’

• Number of Active Text-to-9-1-1 Call takers.

3.4 Text FROM 911 Requirements

The Boards expectation is that the Text FROM 911 system will be configured over a similar platform as the Text TO 911. The requirements for each system must be coordinated in a manner that minimizes the processes a PSAP must engage for Text TO and FROM 911.

Respondents shall include a call flow example of how their proposed solution would function in an sms text scenario.

Respondents must describe how their proposed solution offers the ability to block texts or divert messages that could arise as part of an sms flooding/denial of service situation.

The Text FROM 911 capability must provide:

• 
  Ability to initiate outbound texts via a user interface for all texts
  
• 
  Single platform for all outbound texts
  
• 
  Allow PSAP control
  
• 
  Audible and visual alerts for new text segments create a smooth workflow
  
• 
  Offer the ability to log, record, secure, deny or prevent control of the system by the receiver
  
• 
  Support all industry standards including ATIS JSTD-110 and NENA i3
  
• 
  Monitoring and management capability to ensure system security and resiliency
  
• 
  Reporting capability