Supplementary Data Provisioning for IoT-Linked Emergency Incidents
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current emergency service platforms like NG911 and NG112 do not support access to data from IoT devices and sensors relevant to an incident, as these devices are not integrated into the emergency services architecture, limiting the availability of supplementary data for emergency response.
Innovation Solution
A framework is introduced to enhance emergency services architecture by enabling registration, identification, and access to IoT devices and sensors through a Data Sources Information Repository (DSIR) and Supplementary Data Providers (SDPs), allowing emergency services to retrieve supplementary data relevant to an incident.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If current NG911 or NG112 emergency platforms are used, then the emergency service architecture remains simple and isolated, but access to supplementary data from IoT devices and sensors is not supported
Solution Approach 1:
The patent introduces a Data Sources Information Repository (DSIR) as an intermediary component that mediates between emergency service platforms and IoT devices/sensors. The DSIR stores information about available data sources and enables the emergency platform to query and access relevant supplementary data without direct integration with each device, thus resolving the contradiction between information access and architectural complexity
Solution Approach 2:
The DSIR serves multiple functions: it acts as a database for data source information, a query interface for the emergency platform, and a coordination mechanism for data access. This multi-functional approach allows the system to gain access to IoT data without adding proportionally complex infrastructure
2Adaptability or versatility
If IoT devices and sensors are integrated into emergency services architecture, then supplementary data access is enabled, but the architecture becomes more complex and requires enhanced identification and access mechanisms
Solution Approach 1:
The patent segments the integration complexity by separating the emergency service platform from direct IoT device connections. The DSIR is divided into distinct functional components: a data source registry, a query processing mechanism, and an access coordination layer. This segmentation allows versatile IoT data access while managing complexity through modular architecture
Solution Approach 2:
The DSIR acts as a universal intermediary that handles all interactions between the emergency platform and diverse IoT devices. It provides standardized interfaces for device registration, data querying, and access management, enabling the system to adapt to multiple device types without increasing platform complexity
3Loss of information
If emergency services architecture is enhanced to access IoT data, then situational awareness is improved, but the system requires new components like DSIR and SDPs
Solution Approach 1:
The patent implements preliminary action by having IoT devices and data sources pre-registered in the DSIR with their capabilities, locations, and data types documented before any emergency incident occurs. This advance preparation enables rapid data access during emergencies without requiring complex real-time discovery or integration procedures
Solution Approach 2:
The DSIR serves as a pre-established intermediary that maintains a catalog of available data sources with their metadata. During emergencies, the system can quickly query this pre-organized information to obtain situational awareness data without needing to directly integrate with or discover IoT devices in real-time, thus improving information access while limiting architectural complexity
Data Source
AI summary
A method at a Supplementary Data Provider within an emergency services network, the method including receiving a message at the Supplementary Data Provider, the message including an identifier and incident data; responsive to receiving the message, creating a resource at the Supplementary Data Provider based on the incident data, the resource being associated with the identifier; receiving an access request from an Emergency Services Provider for Supplementary Data associated with the resource; and responsive to receiving the access request, providing a response with the Supplementary Data.