MCM Base-Rover Architecture for GNSS Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Global Navigation Satellite Systems (GNSS) technologies face challenges in real-time operations due to the proprietary formats of observation data, which hinder compatibility between different vendors and do not support effective real-time processing, even with the latest RINEX-3 conversion.

Innovation Solution

A Multiple Content Message (MCM) based system is proposed, comprising a GNSS sensor, Position Velocity Time (PVT) Engine, and a Composite message generator for the base apparatus, and a GNSS sensor, PVT Engine, Composite Message decoder, RTK engine, and baseline corrector/combiner for the rover apparatus, using a packing protocol to generate and decode composite data streams in Integrated Velocity (IV) solution format, supporting real-time and post-processing navigation systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary formats are used for GNSS observation data, then vendor-specific processing capabilities are maintained, but compatibility between different vendors deteriorates

Engineering Contradiction:
Improvecompatibility between different vendorsVSAvoiddata format conversion complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces the RINEX-3 format as an intermediary standard that mediates between different vendor-specific GNSS observation data formats. The base apparatus converts proprietary formats to RINEX-3, which then serves as a universal interface for further processing, eliminating the need for direct compatibility between different proprietary formats and simplifying the overall system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the RINEX-3 format universal by designing it to accommodate multiple GNSS systems and vendor-specific observations through a single standardized structure. This universal format can be processed by any compliant receiver or analysis software, providing multi-functionality across different platforms and applications without requiring format-specific processing paths.

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

2Adaptability or versatility

If RINEX-3 conversion is used, then compatibility is improved, but real-time operation capability deteriorates

Engineering Contradiction:
ImprovecompatibilityVSAvoidreal-time processing delay
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the data processing workflow into two distinct parts: a real-time conversion component that transforms proprietary formats to RINEX-3 immediately upon reception, and a post-processing component that handles the converted data. This segmentation allows the time-sensitive conversion to be performed at the point of data acquisition without delaying subsequent analysis, as the RINEX-3 format can be processed asynchronously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary conversion of GNSS observation data to RINEX-3 format at the base apparatus before the data is transmitted to the rover or stored for later use. This preliminary action ensures that when the data is needed for real-time or post-processing operations, it is already in the standardized format, eliminating conversion delays during the actual processing phase.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If composite data streams with multiple data sets are transmitted, then information completeness is improved, but data link bandwidth requirements worsen

Engineering Contradiction:
Improveinformation completenessVSAvoiddata link bandwidth consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent applies local quality by transmitting different data at different frequencies appropriate to their specific requirements. Fast frequency positioning data is transmitted at high frequency for real-time navigation, while slow frequency observable data is transmitted at lower frequency since it changes more slowly. This differentiated transmission strategy maintains information completeness for each data type while optimizing overall bandwidth utilization.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements periodic transmission of GNSS observation data at optimized intervals rather than continuous transmission. The system transmits data at the minimum necessary frequency to maintain navigation accuracy, holding data constant between transmission periods. This periodic action reduces the total data volume transmitted over time while preserving the essential navigation information needed for accurate positioning.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9562974B2Multiple content message base-rover architecture
Publication Date: 2017.02.07 TRIMBLE INC
  • US9562974B2 patent drawing
  • US9562974B2 patent drawing
  • US9562974B2 patent drawing

AI summary

A multiple content message (MCM) base apparatus configured to generate a composite base data stream is proposed. A multiple content message (MCM) rover apparatus configured to generate a set of fast frequency baseline data is proposed.