Disaster Notification Server Privacy Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing disaster notification services face challenges in selectively transmitting information to users at a disaster location without collecting their location information, leading to inconvenience and privacy concerns due to the need for consent and potential noise-like information being sent to unrelated users.

Innovation Solution

A method where a disaster notification server specifies location information sets corresponding to disaster locations and allows user terminals to determine if they are within these areas, enabling them to request and receive relevant disaster notification information without sharing their actual location, using stepwise location information or false location information to maintain privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If location information is collected periodically to transmit disaster notification information selectively, then disaster notification accuracy is improved, but user privacy is compromised and consent is required

Engineering Contradiction:
Improvedisaster notification accuracyVSAvoiduser privacy infringement
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

Instead of the server collecting user location information to determine notification targets, the invention inverts the approach: users send their location information to the server, which then determines whether to send notifications. This reverses the data collection direction, placing control in users' hands and eliminating privacy infringement while maintaining notification accuracy.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Users actively send their location information to the server themselves rather than having it collected passively. This self-service mechanism allows users to control when and how their location data is shared, eliminating the need for continuous consent while enabling accurate disaster notification delivery.

Inventive Principle:
Principle #25Self-service

2Object-affected harmful factors

If all disaster information is transmitted to all users without location collection, then user privacy is protected, but noise-like information is transferred to unrelated users increasing inconvenience

Engineering Contradiction:
Improveuser privacy protectionVSAvoidinformation noise to unrelated users
Core Design Contradiction:
Object-affected harmful factorsVSObject-generated harmful factors

Solution Approach 1:

The invention reverses the traditional notification model by having users initiate communication with their location data rather than the server pushing notifications based on collected location data. This inversion enables selective notification delivery without compromising user privacy, as users control the information they share.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent replaces the mechanical system of active location collection and tracking with an information-theoretic approach where users send location information as part of their disaster information requests. This substitution eliminates continuous location monitoring while enabling precise notification targeting through user-provided location data.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Object-affected harmful factors

If location information is not collected, then privacy concerns are reduced, but selective transmission of disaster notification information cannot be achieved

Engineering Contradiction:
Improveprivacy concernsVSAvoidselective notification capability
Core Design Contradiction:
Object-affected harmful factorsVSLoss of information

Solution Approach 1:

The invention fundamentally inverts the data flow: instead of the server collecting location information to enable selective notification, users send location information to the server when requesting disaster information. This reversal maintains selective notification capability while eliminating privacy concerns associated with active location collection.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The server acts as an intermediary that receives both disaster information requests and location information from users, processes this information together, and determines notification delivery. This intermediary role enables selective transmission without the server actively collecting or tracking user locations, thus maintaining privacy while achieving notification accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Object-affected harmful factors

If stepwise location information or false location information is used, then privacy is maintained, but accurate location-based notification delivery becomes more complex

Engineering Contradiction:
Improveprivacy maintenanceVSAvoidnotification system complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent changes the parameter of location information from requiring high precision to accepting approximate or stepwise location data. Users can send location information at different levels of detail (e.g., city, district, or approximate area), and the server processes these varied precision levels to determine notification delivery, maintaining privacy while reducing system complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3246889B1Method for disaster notification service not requiring collecting of location information, and disaster notification server and application system therefor
Publication Date: 2020.08.19 EEYA MEDIA
  • EP3246889B1 patent drawingFigure 1
  • EP3246889B1 patent drawingFigure 2
  • EP3246889B1 patent drawingFigure 3

AI summary

Disclosed are a method for a disaster notification service not requiring collecting of location information, and systems therefor. The method comprises the steps of: receiving, by a disaster notification server, from at least one registration system, disaster information including a disaster location and disaster notification information; specifying, by the disaster notification server, a set of location information, each including location information which corresponds to the disaster location of each of at least one item of disaster information; transmitting, by the disaster notification server, the specified set of location information to a plurality of user terminals; if any one of the plurality of user terminals determines that the location of the user terminal is included in matching location information included in the set of location information, receiving, from the user terminal, a content transmission request including identification information of the matching location information; and transmitting, by the disaster notification server to the user terminal, content including the matching disaster notification information corresponding to the matching location information in response to reception of the content transmission request.