Geofence Detection via Multi-Service OS Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current geofencing systems in mobile computing are unreliable in determining when a user has crossed a geofence, leading to delayed or missed notifications, which can result in inappropriate mode settings and increased battery consumption due to inefficient wake-up mechanisms.

Innovation Solution

A method that configures multiple services of a mobile operating system to provide timely notifications of geofence crossings by using a combination of GPS, network changeover, beacon, and significant geolocation services, ensuring accurate location determination and reducing battery consumption through strategic wake-up opportunities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single geofencing service is used, then the system complexity is low, but the reliability of geofence detection is poor

Engineering Contradiction:
Improvegeofence detection reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple geofencing services (GPS service, network changeover service, beacon service, and significant geolocation service) into a unified geofencing system. Each service independently monitors for geofence crossings and provides notifications, ensuring that at least one service will reliably detect the crossing event regardless of limitations in individual services.

Inventive Principle:
Principle #5Merging (Combining)

2Speed

If the mobile operating system is frequently woken up to check geofence status, then the geofence detection speed is improved, but the battery consumption increases

Engineering Contradiction:
Improvegeofence detection speedVSAvoidbattery consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system configures multiple services in advance to automatically detect and notify when a geofence crossing occurs. Each service is pre-configured with geofence parameters and will independently monitor for crossings, eliminating the need for frequent active polling by the application. The services are set up beforehand to trigger notifications automatically when crossing events are detected.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The geofencing services are designed to autonomously monitor their respective data sources and automatically generate notifications when geofence crossings are detected. The GPS service continuously tracks location, the network service monitors network changes, the beacon service listens for beacon signals, and the significant geolocation service tracks significant location changes - all without requiring active application intervention or frequent wake-ups.

Inventive Principle:
Principle #25Self-service

3Reliability

If multiple services are configured for geofence detection, then the reliability of detection is improved, but the device complexity increases

Engineering Contradiction:
Improvegeofence detection reliabilityVSAvoidservice configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal geofencing framework that works across multiple different services and platforms. The system provides a common interface and configuration mechanism that can accommodate various service types (GPS, network, beacon, significant geolocation) through unified parameters and notification handling, reducing the complexity burden despite supporting multiple services.

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

Data Source

PatentUS10939231B2Geofencing
Publication Date: 2021.03.02 OOMA INC
  • US10939231B2 patent drawing
  • US10939231B2 patent drawing
  • US10939231B2 patent drawing

AI summary

Methods and systems for determining a geofence has been crossed are provided. Exemplary methods include: configuring a plurality of services of a mobile operating system using respective application programming interfaces; receiving a wake up from the mobile operating system; getting a notification from a service of the plurality of services; confirming the geofence has been crossed; and notifying a backend that the geofence has been crossed.