Global Positioning Group Support Server for Non-GNSS Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional navigation systems for location-based services often require client devices to have Global Navigation Satellite System (GNSS) capability to access navigation information, which excludes devices without GNSS capabilities and limits their ability to receive accurate location-based services.
Innovation Solution
A method and system that utilizes a global positioning group support server to enable client devices with or without GNSS capabilities to access navigation information by sharing GNSS addresses, allowing devices without GNSS to register and receive navigation data through neighboring GNSS-capable devices, and providing features like association tracking and phantom GNSS functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If client devices require GNSS capability to access navigation information, then navigation accuracy is improved, but device compatibility and accessibility deteriorate
Solution Approach 1:
The patent introduces a support server as an intermediary between GNSS-capable devices and non-GNSS devices. The server receives navigation information from GNSS satellites via GNSS-capable devices and redistributes it to non-GNSS devices, enabling location-based services without direct satellite access. This mediator approach resolves the contradiction by decoupling the requirement for GNSS hardware from the ability to access navigation information.
Solution Approach 2:
The patent implements a mechanism where GNSS-capable devices act as proxies, obtaining navigation information from satellites and copying it to non-GNSS devices through the support server. The support server stores and redistributes satellite ephemeris data, almanac information, and position data, allowing devices without direct satellite access to receive accurate navigation information through this copying mechanism.
2Adaptability or versatility
If all devices access navigation information through a support server, then device compatibility is improved, but system complexity increases
Solution Approach 1:
The support server is designed with multi-functional capabilities to handle various operations: receiving and processing GNSS data from satellites, storing ephemeris and almanac information, managing device registrations, distributing navigation data to different device types, and supporting both direct GNSS access and proxy-based access. This universal design consolidates complexity into a single multi-functional component rather than requiring separate systems for different device types.
Solution Approach 2:
The system implements self-service mechanisms where GNSS-capable devices automatically register with the support server and begin transmitting satellite data without manual configuration. The support server automatically manages data storage, processing, and distribution to registered devices. This automation reduces operational complexity and allows the system to scale without proportional increases in management overhead.
3Adaptability or versatility
If non-GNSS devices share GNSS addresses through neighboring devices, then accessibility is improved, but information accuracy may deteriorate
Solution Approach 1:
The support server acts as a trusted intermediary that validates and processes GNSS data before redistribution. When a non-GNSS device shares a GNSS address with a neighboring device, the server verifies the authenticity of the shared data against satellite ephemeris information it maintains, ensuring location accuracy is preserved even though the device lacks direct satellite access. The server mediates between the proxy device and the non-GNSS device to maintain data integrity.
Data Source
AI summary
A client device transmits a GNSS address to gain navigation information such as map data from a global positioning group support server. The global positioning group support server may provide navigation information of global positioning groups in the vicinity of the client device based on the received GNSS address. The GNSS address of the client device may be an inherent GNSS address or a GNSS address of a neighboring client device. Client devices are registered and divided into global positioning groups at a global positioning group support server based on corresponding GNSS addresses. A particular client device may be added or removed to or from a given global positioning group. Uni- and bi-directional association tracking within a determined time window is enabled based on corresponding GNSS addresses. Phantom GNSS moving is enabled via the association tracking.