GNSS Location Message Reference Time Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current messages for location information defined in cellular standards are only compatible with GPS time, making them incompatible with other Global Navigation Satellite Systems (GNSS) like Galileo, GLONASS, and QZSS, limiting their applicability and requiring separate definitions for each system, which increases complexity.
Innovation Solution
Incorporating a reference time identifier in location information messages to specify the time base used, allowing the same message definition to be used with any GNSS system, including GPS, Galileo, GLONASS, or UTC, enabling flexibility and compatibility across different satellite systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single message definition is used for all GNSS systems, then complexity is reduced and versatility is improved, but compatibility with different time bases (GPS time, Galileo time, GLONASS time, UTC) cannot be ensured
Solution Approach 1:
The message definition is designed to be universal across all GNSS systems by incorporating a reference time identifier field that can specify different time bases (GPS time, Galileo time, GLONASS time, or UTC). This single message structure serves multiple functions by adapting to different satellite navigation systems through the time identifier parameter, eliminating the need for separate message definitions for each GNSS system.
Solution Approach 2:
The message includes a configurable reference time identifier parameter that can be set to different values depending on the GNSS system being used. This parameter change mechanism allows the same message definition to accommodate different time bases (GPS time, Galileo time, GLONASS time, or UTC) without requiring structural modifications to the message format, thus reducing complexity while maintaining versatility.
2Reliability
If separate message definitions are created for each GNSS system, then compatibility with each specific system is ensured, but the number of message definitions increases and complexity increases
Solution Approach 1:
Instead of creating separate message definitions for GPS, Galileo, GLONASS, and other GNSS systems, a single universal message definition is implemented that includes a reference time identifier field. This field specifies which time base was used, allowing the same message structure to reliably communicate location information across all GNSS systems without requiring multiple specialized message formats.
Solution Approach 2:
The time base specification is extracted as a separate identifiable parameter (reference time identifier) within the message. This extracted parameter allows the message to carry information about which GNSS time base was used without requiring separate message definitions for each system, thereby reducing the number of message types while maintaining specific compatibility.
Data Source
AI summary
For enhancing the transmission of location information, a message is received or assembled, which includes location information and a reference time identifier. The reference time identifier identifies a reference time used in determining the location information based on satellite signals. The received or assembled message is provided for transmission to a server. At a server, the location information and the reference time identifier are extracted from a received message, and the location information is processed taking account of the reference time identifier.