Metadata Standard for GNSS Software Defined Radio (SDR) Data

Size: px

Start display at page:

Download "Metadata Standard for GNSS Software Defined Radio (SDR) Data"

Alaina Waters
5 years ago
Views:

1 Metadata Standard for GNSS Software Defined Radio (SDR) Data January 26, 2014 Initial Committee Membership: Co Chair: Sanjeev Gunawardena Co Chair: TBD Member: Phil Ward Member: Michael Braasch Member: Jade Morton Member: Thomas Pany Ohio University Navward GPS Consulting Ohio University Miami University IFEN GmbH 1

2 Clarifications Requested by Council Establish the objective for an Exchange of a GNSS Software Radio Data Standards. Provide terms of reference for the committee. Specify and commercial or economic considerations. Clarify whether this will be a formal voluntary standard endorsed by ION vs. an informal voluntary standard endorsed by software radio experts. Provide a list of proposed members for the standards committee to include qualified representatives from academia, industry and government. Outline the standards setting process to include public comment and review procedure that would be taken. Outside steps taken to ensure objectivity and lack of bias. Provide a plan to document the process. Provide a summary of risk, liability and cost to ION. 2

3 Objective Proliferation of GNSS SDR tech in the past 5 10 years: GNSS SDR Data Collection Systems IFEN GmbH LabSat Spirent Loctronix National Instruments Averna TeleOrbit Nottingham Scientific Ltd. Many others GNSS SDR Processing Frameworks GNSS SDR IFEN GmbH TeleOrbit Nottingham Scientific Ltd. GNU Radio Many university developed research systems (Colorado, Calgary, Cornell, Ohio, Stanford) Many government funded systems Today: Processors are tailored for specific data format. No established standard to convey GNSS SDR metadata. Objective: Interoperability between GNSS SDR data collection systems and processors 3

4 Example GNSS SDR Metadata Number of front end streams IF (real) or baseband sampled (complex) RF center frequencies, bandwidths and digital IFs Bits per sample per stream and sample packing format Antenna/scenario information Information needed to skip through other embedded data Information needed to splice multiple files together Low rate tag information (time stamped or not) Anomalous events (before or after post processing) Front end gain settings over time (or AGC data) Temperature data User log entries 4

5 Potential Metadata Format (XML) <SDRFILE FILEVER=" " METAVER=" "> <NUMSTREAMS>4</NUMSTREAMS> <BITSPERSAMPLE>1</BITSPERSAMPLE> <BLOCKOFFSETDWORDS>0</BLOCKOFFSETDWORDS> <FOOTERMASK>00FFFFFF</FOOTERMASK> <SAMPLERATEHZ> </SAMPLERATEHZ> <! SAMPLEFORMAT: Valid Format Strings: "IF", "IQ" instructs how samples are to be interpreted > <! IF sampled data are real. IQ data are complex > <SAMPLEFORMAT>IF</SAMPLEFORMAT> <CREATIONTIME FORMAT="Coordinated Universal Time" YEAR="0000" MONTH="00" DAY="00 HOUR="00" MINUTE="00" SECOND="00" MILLISECOND="000"></CREATIONTIME> <SCENARIO>GPS/GLONASS Test, 2013 Aug 16 00:50:22:822 UTC</SCENARIO> <CAMPAIGN>GPS/GLONASS L1/L2/R1/R2 Test</CAMPAIGN> <EQUIPMENT>4ch Wideband Front End (1 bit decimated)</equipment> <ANTENNA>unknown</ANTENNA> <LOCATION>Athens OH</LOCATION> <ENGINEER>Joe Engineer</ENGINEER> <COMPANY>Joe Engineer s Company</COMPANY> <COPYRIGHT> 2013 Joe Engineer s Company</COPYRIGHT> <! The following 4 elements are used to splice files together: > <! Path elements are currently ignored in the splicer > <PREVIOUSFILEPATH>c:\sdr_data\</PREVIOUSFILEPATH> <PREVIOUSFILENAME>WideBand_1bit_L1L2R1R2_000.dat</PREVIOUSFILENAME> <NEXTFILEPATH>c:\sdr_data\</NEXTFILEPATH> <NEXTFILENAME>WideBand_1bit_L1L2R1R2_002.dat</NEXTFILENAME> <STREAM INDEX="0" NAME="Ch00" FCAR=" " FIF=" "></STREAM> <STREAM INDEX="1" NAME="Ch01" FCAR=" " FIF=" "></STREAM> <STREAM INDEX="2" NAME="Ch02" FCAR=" " FIF=" "></STREAM> <STREAM INDEX="3" NAME="Ch03" FCAR=" " FIF=" "></STREAM> <NUMEVENTS>0</NUMEVENTS> </SDRFILE> 5

6 Commercial or Economic Considerations If standard is widely adopted: End users shopping for a data collection system and/or processing platform is likely to consider support for standard in purchasing decision This provides significant motivation for equipment manufacturers to support standard, especially if they are also involved with its development It is likely that a standard compliant software libraries will be implemented by open source community, further driving adoption and market pressure Key to this wide adoption is a formal voluntary standard endorsed by organization whose members represent international expertise in GNSS SDR: Institute of Navigation Formal voluntary std. endorsed by ION or informal voluntary std. endorsed by SDR experts? Formal voluntary standard endorsed by ION 6

7 (Partial) List of Proposed WG Members Academia Colorado, Cornell, Calgary, Ohio, UT Austin, AFIT, FAF Munich, UNSW, Nottingham, Tsinghua Univ, others. GNSS SDR Equipment Vendors Loctronix, LabSat, IFEN, Spirent, TeleOrbit, NSL, Averna, Ettus, others. Conventional GNSS Receiver and MGUE Vendors NovAtel, Trimble, Septentrio, NavCom, Javad, ComNav, Rockwell Collins, Raytheon, others. GNSS Chipset Vendors Broadcom, CSR, ST Micro, u blox, others. Not for profit Research Entities MITRE, Aerospace, Draper, DLR, others. Government FAA, NASA, AFRL, ESA, others. Independent Consultants 7

8 Outside steps taken to ensure objectivity and lack of bias Balanced participation from all facets of the GNSS SDR and other related communities Thorough documentation of the process Invitation to join WG in Initial Report All WG reports free and open to the public Widely publicized opportunities for public comment (presentation of reports at ION meetings and notice at ION website) 8

9 Documentation Plan from Draft Terms of Reference: 1. [Feb. 2014]: Official Terms of Reference 2. [Mar. 2014]: Proceedings of WG discussions 3. [Sep. 2014]: ION GNSS+ WG meeting minutes 4. [Sep. 2014]: Initial Report, ION GNSS+ paper 5. [Dec. 2014]: Compilation of public comments 6. [Jan. 2015]: Proceedings of WG discussions 7. [Jan. 2015]: (optional) ION ITM WG meeting minutes 8. [Jan. 2015]: Follow on Report, ION ITM paper 9. [Apr. 2015]: Compilation of public comments 10. [Jun. 2015]: Proceedings of discussions 11. [Aug. 2015]: Report on legal review 12. [Sep. 2015]: Final report, ION GNSS+ paper 9

10 Risk, Liability and Cost to ION Risk and liability is perceived to be low: Voluntary standard: compliance not sought If non compliant: end user can implement Does not require vendors to change their file formats Any existing functionality or tool flow can be preserved via format translation Multiple publicly advertised opportunities and invitations to participate in WG activities and/or provide comments Costs Legal review: approx. $10k 10

GPS Modernization and Program Update

GPS Modernization and Program Update GPS Update to ION Southern California Chapter 22 Feb 2011 Colonel Bernie Gruber Director Global Positioning Systems Directorate Contents Current Constellation Modernization