EMERGENCYCALL DATA ANALYTICS PLATFORM
`
`BACKGROUND
`
`(6001)
`
`Public Safety Answering Points (PSAPs) receive emergencycalls from the legacy
`
`time division multiplexing (TDM)-based Selective Router (SR) network and NG9-1-1
`
`Emergency Services [IP Network (ESInet). These calls terminate to Customer Premise
`
`Equipment (CPE) that distribute the calls to dispatchers. CPE systems provide telemetry
`
`information for incoming emergencycalls, such as various types of location information,
`
`callback number, name, etc. The CPE traditionally interfaces with on-site call taking and
`
`computer-aided dispatch (CAD) applications, which operate on local servers that connect to the
`
`CPE. The 911 industry is moving towards IP-based communications, such as voice over IP
`
`(VoIP). However, with over GO000 PSAPs operating in the United States alone, the changeoverto
`
`fully IP-based PSAPs is expected to take many years. As the public safety industryat large
`
`transitions to [P-based technology that is deployed to private, public, and hybrid cloud
`
`infrastructure, interim solutions will be required to bridge the gap from legacy premise-based
`
`equipment.
`
`{0002]
`
`Because each CPEsystemis a stand-alone, custom-built system, there is alarge
`
`amount of variation in existing CPE systems across the 6000+ PSAPs. For example, many
`
`different proprietary data formats are used across different CPE systems to structure call data.
`
`Cloud-based call taking and CAD solutions are being developed, such as RapidDeploy’s CAD
`
`offering. Cloud-based call taking and CAD offers several improvements overtraditional
`
`on-premises call-taking and CAD systems, including the ability to quickly deploy newfeatures
`
`and updatesto all users, less on-site infrastructure, and increased immunity to malware attacks.
`
`

`

`However, the cloud-based solutions are IP-based, making it challenging to connect to legacy
`
`CPE systems.
`
`SUMMARY
`
`{9003}
`
`Accordingly, there is presently a need for a gatewaythat connects existing CPE
`
`systems to cloud-based CAD systems. This will allow PSAPs to implement more modern
`
`emergencydispatch applications, such as cloud-based call taking and CAD providers (referred to
`
`jointly as CAD providers). In one embodiment, an Internet of Things oT) gatewaydevice that
`
`connects to existing CPE systems and converts call data to a structured format that is transported
`
`over an IP network is disclosed herein. In another embodiment, virtual hardware interfaces and a
`
`software agent installed on the CPE are disclosed.
`
`loT Gateway Device
`
`[0004]
`
`Legacy CPE systems transmit emergency call data over wired, non-IP connections,
`
`such as serial cables. An IoT gateway device is configured to connect to a legacy CPE device,
`
`receive emergency call data in the output format of the CPE device, transform the received data
`
`into a standardized, structured format, and transmit the transformed data over an IP network, e.g.,
`
`to a cloud-basedcall taking and CAD provider. The IoT gateway device connects to a secure
`
`network, such as Microsoft Azure Government, providing a reliable connection from the CPE
`
`system to the call-taking service.
`
`10005]
`
`The loT gateway device includes one or more physical ports for connecting to CPE
`
`devices. For example, the loT gateway device includes a DB9 DTEserial interface and an RJ-45
`
`ethernet for receiving data in one or more protocols, e.g.,HTTP, SOAP/XML, TCP socket, or
`
`EIA/TIA RS-232, and data formats, e.g., ALE, Call Detail Report (CDR), or NENA13 Logging.
`
`Mm
`
`

`

`The IoT gateway device may have multiple ports to connect to and receive data from two or
`
`more CPE devices. In other embodiments, if a PSAP has two CPE devices for providing call
`
`data, a different loT gateway device may be connected to each CPE device. The IoT gateway
`
`device aiso includes one or more high-bandwidth IP interfaces, which maybe wired(e.g.,
`
`Ethernet} or wireless connections. The IoT gateway device may include one primaryIP interface
`
`and one or more backup IP interfaces (e.g., one wired connection and one wireless connection)
`
`for increased reliability and segmentation of network traffic. The gateway loT device manages
`
`traffic between the serial network and the IP network. The loT gatewaydevice also includes
`
`processing logic for parsing the received call data and converting it into a standardized format
`
`recognized by the CAD provider. The processing circuitry may be one or more general purpose
`
`processors that execute an application having instructions for transforming the call data. In other
`
`embodiments, the processing circuitry can include one or more reconfigurable processors(e.g.,
`
`FPGAs) or one or more custom processors (e.g., ASICs).
`
`[0006]
`
`The loT gateway device may be implemented as a system on a chip (SoC)built using
`
`lowcost, off-the-shelf hardware, such as a system based on a Raspberry Pi (ARM) or anIntel
`
`MinnowBoard (x86). The lof gateway device may use an operating system that is compatible
`
`with the cloud-based CAD provider; for example, the oT device uses a Microsoft loT platform,
`
`such as Windows 10 IoT Core, and the cloud-based CAD provider uses Microsoft Azure
`
`Government cloud.
`
`(0007)
`
`The CAD provider synchronizes with and monitors the status of the loT gateway
`
`devices to which itis connected. The IoT gateway device may provide the cloud-based CAD
`
`provider with an inventory of the connected on premise CPE devices andstatus updates about
`
`the connected CPEdevices, and the CAD provider may monitor the status of these CPEdevices.
`
`

`

`In some embodiments, the cloud-based CAD provider can reconfigure one or more of the IoT
`
`gateway devices. For example, the cloud-based CAD provider can push a software updateto all
`
`of the connected [oT gateway devices at once.
`
`(6003)
`
`In some embodiments, the cloud-based CAD provider may perform on-demand
`
`provisioning when a new IoT gateway device is connected to the network. As discussed above,
`
`the format of emergencycall data provided by CPE systems is not standardized, and the format
`
`varies between CPE vendors and products. Advantageously, because the IoT gateway devices
`
`are network connected, each loT gateway device does not need to be individually programmed
`
`based on the format of the CPE equipment. Instead, the CAD provider may store instructions for
`
`re-formatting each call data format, and push the appropriate instructions to an IoT gateway
`
`device based onthe CPE system to which itis connected. The instructions for re-formatting a
`
`given call data format are only programmed one time (.e., for the first loT device that receives
`
`that data format), and the instructions are then automatically applied to additional IoT devices
`
`that receive data in the same format.
`
`[0009]
`
`For example, when a new IoT gateway device is installed, the PSAP or an agent
`
`affiliated with the cloud provider may transmit data to the cloud-based CAD provider indicating
`
`the call data format, or data that can be used to determine the call data format such as the vendor,
`
`product line, and/or geographic region or location of the CPE equipment. If another IoT gateway
`
`device has already been configured for this format, the cloud-based CAD provider simply
`
`transmits the configuration for the previously-installed lof gateway device to the new [oT
`
`gateway device when the new IoT gateway device connects to the network. Alternatively, when
`
`a newloT gateway device is connected to the Internet, it may transmit data about the connected
`
`CPE equipment (e.g., vendor information, product information, PSAP location, exemplarycall
`
`

`

`data, etc.) to the CAD provider that the CAD provider uses to look up a call data format. The
`
`CAD provider identifies a configuration for the loT gateway device based on the call data
`
`format, and transmits this configuration to the new IoT gatewaydevice.
`
`{O010]
`
`During operation, the loT gateway device may transmit data to one of two data
`
`targets at the cloud-based CAD provider, depending on the whether the data received from the
`
`CPE device describes in-call events or post-call events. For example, during a call, the CPE
`
`device may periodically provide updated location data, which the loT gatewaydevice transmits
`
`in real time to a “fast data” processing element at the CAD provider. After a call, the CPE may
`
`provide a data dump with information describing the call, which the loT gateway device
`
`transmits to a “slow data” processing or storage element at the CAD provider. In some
`
`embodiments, the loT gatewaydevice transmits both types of data to the CAD provider
`
`immediately upon receipt.
`
`In other embodiments, the loT gateway device prioritizes “fast data”
`
`to ensure that itis provided quickly to the CAD provider.
`
`[0011]
`
`In some embodiments, the loT gateway device has an additional output channel for
`
`providing “fast data” directly to an on premise application, to ensure that on-site call takers
`
`receive real-time call data. For example, the loT gateway device maybe configured to connect
`
`to an internal IP-based network over a wired or wireless connection, and transmit real time event
`
`data to a call taking system over the internal network. This internal network channel maybe a
`
`backup channel used if the connection to the cloud-based CAD provideris down.
`
`{O012]
`
`An example of an IoT gateway device and additional advantages provided by IoT
`
`gateway devices are described in Appendix A.
`
`

`

`E911 integration Agent
`
`[0013]
`
`An alternate system for negotiating transfer of data from legacy CPE systems to a
`
`cloud provider is an enhanced 911 (E911) integration agent. E911 is the current standard for
`
`caller location data, although the particular format of E911 data is not consistent across
`
`automatic location database (ALD database providers. The E911 integration agentis installed on
`
`existing CPE systems to provide virtual hardware interfaces for receiving call data normally
`
`output by the CPE and a software integration agent for processing the call data for receipt at a
`
`cloud-based CAD program. In other embodiments, the software integration agent is located on
`
`the cloud, rather than being installed on the CPE. The software integration agent converts call
`
`data into a consistent format. An example of an E911 integration agent andadditional
`
`advantages are described in Appendix B.
`
`6
`
`

`

`Potentially claimable subject matter includes, but is not limited to, the following:
`
`1. A gateway device comprising:
`
`a serial port for receiving data from a customer premises equipment (CPE) device
`
`located at a public safety answering point (PSAP);
`
`processing circuitry configuredto:
`
`execute an application received from a cloud-based computer-aided
`
`dispatch (CAD) provider, the application comprising instructions
`
`for parsing data in the format used by the CPE device;
`
`parse the received data according to the instructions; and
`
`convert the parsed data into a standardized format, and
`
`an Internet Protocol (IP) interface for receiving the set of instructions from the cloud-
`
`based CAD provider, and transmitting the converted data to the cloud-based
`
`CAD provider over a secure Internet connection.
`
`2. A methodfor processing emergencycall data comprising:
`
`providing, by an IoT gateway device, data to a cloud-based computer-aided dispatch
`
`(CAD) provider describing an inventory of devices connected to the loT
`
`gateway device, the inventory of devices including at least one customer
`
`premises equipment (CPE) device configured to provide emergency call data
`
`in a data format of a plurality of data formats;
`
`receiving, at the loT gateway device, instructions for processing emergency cail data
`
`according to the data format of the CPE device;
`
`receiving, at the IoT gateway device, ernergencycall data from the CPE device;
`
`

`

`transforming, by the loT gatewaydevice, data received from the CPE device to a
`
`standard data format according to the instructions for processing emergency
`
`call data; and
`
`transmitting, over an Internet connection, the transformed data from the loT gateway
`
`device to the cloud-based CAD provider.
`
`3. A method for provisioning an IoT gateway device comprising:
`
`receiving, from an loT gateway device over an Internet connection, data describing
`
`the local environment of the loT gateway device, the environment including at
`
`least one customer premises equipment (CPE) device configured to provide
`
`emergency call data and located at a public safety answering point (PSAP),
`
`determining an emergencycall data format of a plurality of data formats for the CPE
`
`device;
`
`retrieving instructions for parsing data from the emergency call data format and
`
`converting the parsed data to a standardized format;
`
`transmitting the instructions to the loT gatewaydevice overthe Internet connection;
`
`receiving, over the Internet connection, real-time emergency call data in the
`
`standardized format from the loT gateway device; and
`
`transmitting data derived from the real-time emergencycall data to computer located
`
`in the PSAP.
`
`

`

`SS
`
`X\
`
`Appendix A
`
`Zzf
`fs
`
`henatt
`
`ae
`
`“cedgreeess
`
`4
`
`Pheer
`
`%,
`g
`yess
`Perees.
`Werece
`
`oy¢
`;earth
`
`
`
` L0%,44%ef
`
`g4
`eeceeres#
`fo
`
`743of
`£04
`
`vlyseest
`warnCt4
`4,ed4
`
`£
`Perees.
`woos
`
`i,Ct4Ld
`
`gor
`
`sorte,44‘at
`
`oo,fseeeeteree
`
`yn£3yt
`
`pod
`
`SY
`ys
`wo
`8
`s—
`
`-&
`S~
`
`ite,FFolodbudh
`
`wer
`Poreess
`
`o
`ga
`Noe
`
`| Spec
`
`ficat
`
`%,
`Preece
`
`&
`pou
`
`
`
`4ecbecedbeacbrech
`_T!
`recnnica
`
`
`
`

`

`
`
`HEPOCUCTION vec cccsssccsecsecsecesssssssssssscsscsecssecscccsccecssssssssscuscsansonsenscuecsscesosssussssssansevscececssessnecascusesssesesssesscansancansesecesetassassisssscancenssesesacerceassssssissssenseenseness 2
`
`RapidDeploy Emergency Call Data Analytics Platform Overview ou...cccccssessssssssceeseeccrscesssnvsenrseecnnnsees neveeecceseersnssseseaveecennseserenseeecersasen®2
`
`Functional Process FROW occ seseescesssneessssssssssusscecsssnesssssnnnevessesesescessnnesseessnnnsessesnsuvvssssuuaseeeeeensnersseesanneeeeseeseeseesenneretessnaneensceees 3
`
`Additional furictional processesoo.eescccsssecsessseccrscccesnvssvesseeccnnnsesesnssceeececesnussevesseenenseessnnnssessresceeeavssnennsesenneseeeaesecersecovensesesneeseesesss 3
`
`RapidDeploy Emergency Data Gateway (EDG) LoT App oc ccccccsssssnneeesnsesseneseeccrseceessvesenenseeesnnsssennsrescereerseeesecernasessanteseenseecererersavess4
`
`LISTOPIOLS ec ccec ccecesseneeeesnnessesneseeeseessneseessnesssennie conn esseseessnnmecssnnsessunneeseasddssusseessuneeeeeseseeseeaninecenn oss eseesanmesennnesssunieesesddssssseessnanessennssenvneeeeees4
`
`THATS DOMES es ceccccceccccssosnenseessvesseessececcecceceszsoyvssnessvesseessececeeccecessooisysiesnresuresueecereseressecessssoyvssavesassnaseencececceessoe yoy svanseasenasececececccessoovygeesseessetets4
`
`User INtertace ce eecsssssseeccecesesessssssnnesesessssnreecceessseessssanssseessnsaseecsesssrrsrsesnecseessnsnsecsesssnsareesseeesnrsesssnnaveceesnsneseessnneseersanseseansnneeeessnnreecseeessestt 5
`
`RapidDeploy Emergency Data Gateway Device Platformccceecsssseeescesnsceesnneccenseessuuseceenvreenenseesssnsvecgastessuusseesanirenneressnsneereseess 5
`
`Hardware Compatibility... ccccccccsssessenseeesnsseecsnseseersccesnnvsrsssscenensecesnnsseeccessessasesssnsvscensnnsesssnestececsecsnasesssnsseseeatecqeeasessceesssesieennarecseensds 5
`
`DEStrIDUTION CHANT on. ee cccccesscssessneneceessssreescecesensssssnsnsessssnseessesssvererransesscnnssssseessnereceeseeesecseeesnnnsuesesnsnseessnnesessosasessennanetessnsnvecssersset 6
`
`Tested System Config uratio4ns 0...cecscssessssssesssssssscneeccrnnscessnvecgesseessssssesnsteccennsceesuvecceasieessusssecnneecennsesssuneegavivssusseessneeeeeneresnnneeeesnesss6
`
`RapidDeploy Emergency Data Reporting Platterin oc eessessssessesseneecesocessonseessnnnseeesereceensescccesssesvisessnsseenesieccennsereceesseeviesennesessaness7
`
`DashOars cesses sssssssseerecseesvecsssssssnecsssnsvrceessrsnseessnnnsesseessuescesssnsereeesosnsiesseanssneseessnssasseseessvnesesennnaseesesasneseeesseseseessoaseesceananmneesssnarrectecessett 7
`
`Emergency Call Data Reports oc esscssesssssnesnessssensecesnnsscessnveccessesssusseeeesveeccenseessanvvecaasivsesssssesenseccnnnseeesuvvecassessmssesesnvesesnetesanseevsnesss8
`
`

`

`
`
`The RapidDeploy EmergencyCall Data Analytics platform collects, processes, stores, and transforms rawdata from
`911 call handling systems and renders concise and informative views that improve resource allocation and incident
`management for public safety agencies. The platform is the first of its kind to leverage an Internet of Things (loT)
`event-driven architecture and Microsoft Azure cloud infrastructure services to provide geo-diverse, high-volume
`ingestion of 911 event data so that it is processed and available in real-time. If is also designed to work seamlessly
`with RapidDeploy’s cloud Computer-Aided Dispatch platform by aggregating 911 event data through all stages of the
`incident management process.
`
`
`RapicDeploy’s Emergency Cail Data Analytics Platform supports the following workstreams for collecting and
`processing data from 911 call handling systems:
`
`#
`
`s
`
`#
`
`»
`
`2
`
`»
`
` Fyent Creation -911 call handling systems generate event information throughout the emergencycal
`session and transmit the encoded data on industry standard and proprietary interfaces.
`Collection - Compatible loT gateway devices running RapidDeploy’s app collect event data from connected
`911 CPE and manage the transport of normalized data to RapidDeploy's geo-diverse cloud infrastructure.
`Telemetry ingestion — The lof Hub will manage the ingestion of event data collected from IoT devices and
`will provide servicefail-over capability to additional availability regions.
`Stream Processing - Transformation and routing of collected streams to provide real-time monitoring and
`alerting for fast-data processing.
`Persistent Storage — Long-term document-based storage to provide data sources for BE arid analytics with
`configurable policies for data retention and encryption.
`Presentation & Workfiow — Microsoft PowerBl provides dashboard and reporting capabilities and Azure
`services like Azure Search and Data Lake Analytics provide presentation and scheduled delivery of BI reports.
`
`Event telemetry extends the capabilities of the event data collected by RapidDeploy’s Dispatch platform. at
`
`i: VK
`
`The primary functional flow of the 911 data collection process involves the handling of emergencycall data event
`information directly from PSAP premise equipment on service provider and aggregation of event data at a centralized
`location in nearreal-time. The flow should support reliable delivery of collected data in the event of a failure to
`connect to the aggregation point and secure delivery to protect the contents of the data during transmission.
`
`

`

`The use case for the 911 data collection flowis perfectly suited for an IoT device platform with cloud-based
`infrastructure services using commodity internet connectivity for transport. RapidDeploy’s analytics platform is
`implemented as a cloud-based IoT solution that includes an loT gateway device platform to provide on-cevic
`processing of data collected at the customer edge network, and Microsoft Azure cloud services for stream processing,
`
`storage, and business intelligence.
`
`The 911 call handling system generates an emergency call telemetry event (e.g., a call data record (CDR),
`automatic location identification (ALD, and/or NENA i3 Logging) and transmits the encoded data over a
`supported connection (e.g., an IP connection or RS-232 serial connection).
`The Emergency Data Gateway (EDG) IoT device collects the incoming encoded data on the configured
`listener interface and queues the message along with a unique correlation identifier in an encrypted
`database file stored on a local file system of the EDG IoT device,
`The message is dequeued from the local database and is processed by a message parsing endine in the EDG
`loT device. The message parsing engine converts both structured and unstructured data into a lightweight
`JavaScript Object Notation GSON)-encoded data-interchange format.
`The JSON-encoded event cata is reliably transmitted to the distributed cloud loT Event Hub over a secure
`connection.
`
`The lof Event Hub routes the incoming telemetry event based on a configured policy to a fast-data target
`(e.g., a stream analytics engine) for real-time processing and alerting or a slow-data target (e.g., an SQL
`database, a Microsoft Azure Blob data store, and/or a PowerBl service) for analysis and reporting.
`Stream analytics performs transformation and real-time analytics of telemetry data received on the lof Ever
`Hub and routes directly to PowerBl or storage container.
`Event telemetry data is refreshed in PowerBl in real-time and available for reporting and analytics workfiows.
`
`ont
`
`Device boot and initial provisioning
`Device state telemetry update
`Device provisioning update
`App update
`Device firmware update
`Stream processing and routing
`Real-time alert notification
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`x ~
`
`sI
`
`s
`»
`»
`2
`s
`*
`2
`
`

`

`
`
`RapidDeploy’s Emergency Data Gateway IoT app is a Universal WindowsPlatform (UWP) package that is designed to
`run on the Windows 10 oT Core embedded operating system. The app’s primary function is to provide serialization
`and marshaling of 911 data formats captured from hardware input interfaces and to manage the reliable and secure
`transmission to RapidDeploy’s cloud infrastructure. The core EDG IoT app features include:
`
`s
`
`Centralized device provisioning — Devices that run the EDG IoT app receive provisioning data from the
`cloud services infrastructure automatically an boot and receive over-the-air updates and re-configuration
`from the cloud infrastructure as needed.
`
`s
`
`Listener interfaces — The EDG JoT app supports connectivity to 911 CPE via IP and NENA 04-001-comoliant
`serial data interfaces. Listener interfaces support data collection using HTTP, SOAP/XML, TCP socket, and
`EIA/TIA RS-232 communication protocols.
`2 Message parsing - Incoming data streams are parsed and converted to a lightweight JSON-encoded format
`using a proprietary engine that can be configured to consume virtually any structured and unstructured
`format without the need for custom programming.
`Transports — Transmission of collected event data is supported by modern protocols optimized for
`efficiency, reliability, and security. Transient fault handling is implemented using industry best practices
`including an exponential back-off retry policy by default.
`Telemetry — Device state, processing errors, and detailed metrics of app performance are transmitted to
`RapidDepioy’s cloud architecture to provide proactive monitoring and alerting in response to potential
`issues.
`
`#
`
`*
`
`»
`
`Local encrypted storage — Event data collected from listener interfaces are queued to local, encrypted
`database storage. Faults in data transmission, hardware failures, or other general failures will cause the app
`to re-enqueue the transactions from database storage preventing data loss.
`
`nee
`¥ leva
`Sees
`MISSSNTSES
`
`Listeners wait for incoming data streams received from hardware input interfaces and create discrete events for
`processing and transmission. Listeners are supported for a variety of communication protocols and data formats
`shown below:
`
`Listener Type
`
`Serial (EIA/TIA RS-232}
`
`TCP socket
`
`HTP SOAP/KAML
`
`Transports manage the delivery of JSON-encoded telemetry events to cloud services that perform the remaining
`processing, analysis, storage, rendering, and delivery tasks. The following transports are supported as targets for 911
`event telemetry data:
`
`Transport Type
`
`Blob Storade
`
`Azure lol Hub
`
`

`

`RapidDeploy WebAPI platform
`
`MOTT and AMQP are lightweight binary messaging protocols that are ideal for loT device telemetry. RapidDeploy’s
`EDG app supports configuration of these protocols according to bandwidth capabilities of backhaul connections and
`network constraints. More information about how these protocols can be used to optimize ingestion of telemetry
`data from loT devices can be found here:
`
`
`
`IoT devices running RapidDeploy’s EDG app will support a userinterface for initial device provisioning and status. The
`interface can be accessed using the connected display port (HDMD and keyboard/mouse. A Web-enabled interface
`can also be enabled for device maintenance and local dashboard status.
`
`
`
`RapidDeploy’s Emergency Data Gateway (EDG) device platform is built on Windows 10 IoT Core that leverages the
`srnallest footprint of the Windows 10 common core architecture. This optimized version of the Windows 10 platform
`provides interoperability between lost-cost IoT devices for both ARManc x86 System on a Chip Got) architectures as
`well as the following benefits:
`
`#
`
`*
`
`»
`
`Scalable platform — Windows Universal App Platform provides a converged set of APIs that allow for
`consistent development of Microsoft technologies on low-cost silicon. Device manufacturers have the choice
`to select best-of-breed boards, storage, interfaces, peripherals, and enclosures at a minimal cost.
`Device connectivity — Wired connectivity (Ethernet, USB, serial) and wireless connectivity (Wi-fi, BLE, MBB)
`with access to systern busses (GPIO, 12C, SPI) with Universal Driver (UD) API surface across Windows 10
`platforms.
`Security —- Windows 10 loT Core provides Windows-grace security for embedded device platforms and
`supports hardware-based Trusted Platform Module (TPM) technology that enables tamper-resistant crypto-
`processor functionality.
`s Manageability ~loT devices are managed like any other Windows device with the latest security and
`technology updates distributed to a smaller class of devices.
`Cloud integration ~ Windows 10 IoT devices have built-in connectivity to the cloud and robust Azure IoT
`platform services.
`:
`«
`oIM TE te.
`agschance Soranatinilive
`ASAYALTS GON Sa Ti isysy
`
`#
`
`oe
`
`RapidDeploy’s Emergency Data Gateway (EDG) UWP app will run on any hardware compatible with Windows 10 IoT
`Core (starting with build 16299/Fall Creators Update). Suggested SoC boards for Windows 10 IoT core are available
`here:
`
`
`
`USB serial device adapter interfaces compliant with EIA/TIA RS-232 standards have been tested on devices with FTDI
`(Future Technology Devices) chipsets. More information about FIDI compatibility with Windows 10 oT Core can be
`found here:
`
`
`
`

`

`ce ete:
`ex
`OSS
`WR Sevabes odds
`GAISTTISition Cannes
`eg
`
`RapidDeploy’s Emergency Data Gateway (EDG) UWP app Is distributed through trusted channels like the Microsoft
`Store for initial provisioning and app updates. A channel is also available for device hardware veridors to side-load
`specific app builds for testing and certification purposes.
`Was tae
`aes MARSees hance
`PASTAS
`hr
`SN LATE FahiOns
`
`ce
`
`Proof-of-concept Io device configurations using the Raspberry Pi 3 Model B and Minnowboard Turbot Dual-Core
`boards have been developed with the following specifications:
`
`(UHS-1 Class 10 30MB/sec}
`
`Architecture
`
`Sac
`
`Processor — frequency
`
`Processor — cares
`
`Memory
`
`Network Interface
`
`USB interfaces
`
`Video interface
`
`Storage
`
`Raspberry Pl 3 Model B
`
`ARM
`
`Braadcam BCM2837 64-bit
`
`L2Ghz
`
`4
`
`LGB SDRAM
`
`10/100 Ethernet, 24GHz SO2.1in
`wireless
`
`4 USE 20
`
`Fullsize HOM]
`
`SanDisk Ultra LGGB MicroSDHC
`
`

`

`
`The business analytics too! used by RapidDeploy’s cloud Dispatch and Analytics platform is PowerBh Power Blis a
`business analytics service provided by Microsoft that provides interactive visualizations withself-service business
`intelligence capabilities, where end users can create reports and dashboards by thernseives, without having to depend
`on information technology staff or database administrators. PowerBlis integrated with Azure cloud services to
`provide real-time data processing and persistant data storage capabilities.
`Aaetc:
`Sashboards
`
`PowerBl supports real-time streaming for streaming data and updating dashboards in real-time. Event and device
`telemetry data sources can be from 911 systems, service providers, location data sources, social media sources,
`sensors, and other data sources for which time-sensitive data is collected or transmitted.
`
`Xtippy
`
`NESS
`
`es
`
`_CKMX
`
`SS
`a & x
`
`EL,HEEEEeeLEE
`
`Benteanans Quads aloes
`
`Sta? Nae:
`
`

`

`casero gall Lava Sannste
`Smarnency
`fall Sata Sanory
`Emergency Cal! Sata Resorts
`
`Standard Reports
`
`A suite of standard emergencycall data reports is available in PowerBI that provide analytics tools for PSAP resource
`utilization, call routing, dispatch performance, and wireless location accuracy. Ad hoc reporting tools are available for
`custom report generation that can be exported to a variety of target formats (Excel, PDF, etc.}. All reports support
`subscription capabilities with automated delivery via email on a daily or weekly basis.
`
`Management Reports
`
`

`

`Appendix B
`
`g3
`Geeceeteh
`LO,
`
`
`
`LILYITE.%
`
`toesses
`
`ef%LAF
`
`Onesteree
`tte,wr
`
`£E%4yd
`LES,
`
`cOLETOSIEE,g%g4“carl
`
`eee
`
`pool
`
`7K
`1%Zeel
`
`fo“eg
`
`encessgstl!
`
`5
`gf
`tity,
`
`Gereverch
`
`
`
`ettlites,
`
`ieaeeg,
`
`werystigs
`
`,%
`‘ennrfl
`
`oo
`ee
`:s
`
`¢$A
`
`oS
`
`‘etnwe
`
`wereeep4ecceel
`
`%%hea
`
`Ny
`‘ecnttt
`4%,
`%3B
`
`4
`Soeeee
`
`ratte,LT4Uf
`
`%
`or,
`‘eeatt
`S
`wn
`
`eyeeeel
`$4
`
`4
`yore
`Prreets
`
`es,
`‘eet
`
`geen
`
`Melee
`44
`frrtts.
`Meares,
`
`3arrests,weUPPEELET
`
`74%3%Cae
`“dtl
`
`f%440%
`You,
`‘ethDeap
`
`Z%
`LTPt:
`terres
`
`eyeeeel
`$4
`
`wertttths
`+”Y!
`Technic
`
`<
`
`il Speci
`
`fication Documeri
`
`t
`
`
`

`

`£911 Computer-Aided Dispatch (CAD) integration
`
`ro
`mt
`rye
`:
`sryviantec
`gah
`
`PEPOCUCHION oe ecssssseseeccscensescessnnnnsseessscssssnmmsssennnnssseesessnsnssesesennnssecesnnaessecennerssnmssisesssnnecesesenneneessecnnesesesnenneseceesnmecessscessanieeessennastieseeennaenteet 2
`
`RapidDeplay E971 Agent Intec ration Architecture ooccccccccsssessecsescerecceeccceerseceecerecesseceececeersecceccercecrersecsennseceececcerrseceeccceereceecereeertecescersecreeen &
`
`Virtual Serial Port Driver oo ccccssssssssssssesseeseeesssessceeeessonvsscescnsnsvsseeenessnssecesennsnssssessnevvenscveceessnvsseesensnsseeeennsnnseceesensesesenennssveeseceereeceeveeseenecaneteess 3
`
`Windows Driver Profile oo esccssseesccssceensesssssssssnasesssnnnscessesnsnsecescensnseceecenneseseenersssssssecannnsieceesennnscesennnnsiessecavieeseecennsieeisiiesenneseets 3
`
`LIX Driver Profile cc ceeeseccesensecceecccccsseccersesrsneseesesoeesecceceeveerseceecerceesseceeccceerseccsncersaarseesescersceececceersectecereersseceecceeereecescessersecerseenereceececeeersess 3
`
`Standard Interface SpecifiCATON oeccccccceseececsssseeeseeeeeesenecececcnsnsvsseeecnssnsseceesensnssesesennseseceneereesenssveteenssesssesennnsnssseseennsnereeessnveeeeeeennsreneceeeeeser® 3
`
`COMMUNICATION PLOTOCOL cesses eeeccescenneeeecencersssnsssessssseecescnnsnsecesscnnnsseceecennssseceessneiecessisesssnsieceesnnnestiseesennnssieceesennesscenennesiecseecenersossseeseeeened® 3
`
`Deployment SLrateQy acccccceeesccccceereeceecececerseceeceecenseseccescerseccececcerseccececceerseceecercersseceseceeaereseereerseceeccceerseceecercerrseceeeeceerteceescasseereceersenenseccececeeersest 4
`
`Datta MO ete esccccsesseecccccssnsseceeccnsssvseceenensnssesessnescensvssseescensseseennsnnvssesennssnsvesessensnensseesnnvseensvscesseenssseseessneveeesenesnnsseceesensnerssesenesenseseeeneescenevesesesenesesss 4
`
`Service Lifecycle Managemerita... sss eseccscsesesssessssnseseescennnsecesecnnnseceesensssieceeennnnseseeceessssmsssisennnesieeeeeennnssieseeeennnsreseeeennnessseeennesieiiseeeneds 5
`
`LOGI BL MOMitOriing once secccseeeccernececcececeececreceesereseceersereccerececeereceesececceceereccececcececcerecseererceseernersceereececcereececersececeereccececeesserserceeeseeenensnssceeecsereceeres 5
`
`Test PLA oc ecccessssssssesssesssssssesssessnesssssssscsssesssassssssssussnsssssssssessnessussessesssessusssssesussuesssuesessusssessnssessecsuessnsssasesssessnecsussessessuesenvenesssnsusssesssssesscsanesenssesseessesenesenss 5
`
`X RapidDeploy
`SUGSION ERITH CAL PIRPATCH
`
`1
`
`

`

`£911 Computer-Aided Dispatch (CAD) integration
`
`The transition to NG9-1-1 will invalve the move to the industry standard EmergencyIncident Data Document (EIDD}
`format for aggreqating and disseminating detailed incident data between public safety entities. In the interim,
`RapidDepioy will continue to support integration with 311 call handling systems using standard legacy interfaces
`currently used by existing CPE solution providers. Since these interfaces rely on physical hardware components to
`support interconnectivity between 911 call taking and CAD systems, a new model will be required for integrating
`premise equipment with RapidDeploy’s CAD APIs hosted in the cloud. RapidDeploy’s integration strategy for £911 is
`to provide a combination of virtual hardware interfaces and a software agent installed on CPE to reliably broker the
`transmission of incident data.
`
`
`The architecture of RapidDeploy’s £971 Agent program shown in Figure 1 iHustrates the configuration that will apply
`to most 9114 call handli