Facility Exposure Data Generation via Network Detection Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current contact tracing systems are inaccessible to operators of mobile devices from shared device fleets, as they do not provide facility- or enterprise-wide notifications of potential exposures to infectious diseases, restricting further contact tracing.

Innovation Solution

A system that integrates anonymous, privacy-preserving contact tracing mechanisms with facility-based data tracking and analysis infrastructure, using network detection devices to generate and process proximity data, and a server to generate facility exposure data, identifying affected devices and operators within a facility based on proximity to an infected individual.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If contact tracing systems use individual mobile device tracking, then individual exposure notification is achieved, but facility-wide contact tracing capability is lost

Engineering Contradiction:
Improveindividual exposure detectionVSAvoidfacility-wide tracing capability
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent combines individual mobile device tracking with facility-based network detection devices. The server merges proximity data from multiple sources (mobile devices and fixed network devices) to create comprehensive facility exposure notifications, resolving the contradiction between individual tracking precision and facility-wide coverage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system creates a multi-functional contact tracing solution that serves both individual users through mobile device notifications and facility operators through centralized exposure notifications. The same infrastructure supports both granular individual tracking and aggregate facility-wide monitoring capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If contact tracing systems rely solely on mobile device applications, then individual privacy is preserved, but shared device fleet operators cannot access tracing capabilities

Engineering Contradiction:
Improveprivacy preservationVSAvoidaccessibility for shared device operators
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a server as an intermediary that receives anonymized proximity data from mobile devices and network detection devices. This intermediary processes the data to generate facility exposure notifications without compromising individual privacy, while simultaneously providing actionable information to shared device fleet operators who cannot directly access the mobile device tracking system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If contact tracing uses centralized data collection, then facility-wide exposure notification is achieved, but individual privacy protection is reduced

Engineering Contradiction:
Improvefacility-wide notification efficiencyVSAvoidindividual privacy
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements different data processing qualities at different levels: individual mobile device data is processed locally with strict privacy protection, while facility-wide aggregation occurs at the server level with anonymized data. This local quality differentiation maintains privacy at the individual level while enabling efficient facility-wide notifications.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11457811B2Systems and methods for determining facility exposure to a source condition
Publication Date: 2022.10.04 ZEBRA TECHNOLOGIES CORP
  • US11457811B2 patent drawing
  • US11457811B2 patent drawing
  • US11457811B2 patent drawing

AI summary

A method includes: obtaining, at a server, a diagnosis key published by a tracing service, the diagnosis key associated with a source device; identifying one or more detected proximity identifiers associated with the diagnosis key; identifying one or more affected network detection devices associated with the one or more detected proximity identifiers; retrieving, from a repository, device data for the one or more affected network devices, the device data identifying a facility of the one or more affected network devices; and generating facility exposure data for the facility, the facility exposure data defining exposure associated with the source device at the facility.