EP1719318A1 - Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central - Google Patents

Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central

Info

Publication number
EP1719318A1
EP1719318A1 EP04709100A EP04709100A EP1719318A1 EP 1719318 A1 EP1719318 A1 EP 1719318A1 EP 04709100 A EP04709100 A EP 04709100A EP 04709100 A EP04709100 A EP 04709100A EP 1719318 A1 EP1719318 A1 EP 1719318A1
Authority
EP
European Patent Office
Prior art keywords
message
tracker
checksum
entering
hardware device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP04709100A
Other languages
German (de)
English (en)
Inventor
Clifford Yamamoto
Sebastian Nonis
Ashutosh Pande
Nikola Bulatovic
Stefan Witanis
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CSR Technology Inc
Original Assignee
Sirf Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sirf Technology Inc filed Critical Sirf Technology Inc
Publication of EP1719318A1 publication Critical patent/EP1719318A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/03—Cooperating elements; Interaction or communication between different cooperating elements or between cooperating elements and receivers
    • G01S19/09—Cooperating elements; Interaction or communication between different cooperating elements or between cooperating elements and receivers providing processing capability normally carried out by the receiver
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/13—Receivers
    • G01S19/34—Power consumption
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/01—Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/13—Receivers
    • G01S19/35—Constructional details or hardware or software details of the signal processing chain
    • G01S19/37—Hardware or software details of the signal processing chain
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/0009—Transmission of position information to remote stations
    • G01S5/0018—Transmission from mobile station to base station
    • G01S5/0036—Transmission from mobile station to base station of measured values, i.e. measurement on mobile and position calculation on base station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion

Definitions

  • This invention relates to satellite positioning systems.
  • this invention relates to satellite positioning systems implemented using the processing power of a host in communication with satellite positioning tracker hardware device over a predefined interface.
  • SPS satellite positioning systems
  • GPS Global Positioning System
  • PDAs Personal Digital Assistants
  • Methods and systems consistent with the present invention provide a message interface between a computer host and a hardware tracker in a host based SPS solution.
  • the SPS is described as a GPS solution.
  • a wide variety of electronic devices may incorporate GPS functionality with less expense using less development time.
  • a host based positioning system includes host computer system that connects through a tracker hardware interface to a dedicated hardware space vehicle tracker.
  • the tracker hardware interface formats and decodes messages from the hardware tracker a more logical division of the tracking function from the location data formatting.
  • Figure 1 is a diagram of an exemplary positioning system implemented as a layered host computer based GPS solution having tracker hardware device in communication with a host.
  • Figure 2 is a block diagram of the exemplar position system of Figure 1.
  • Figure 3 illustrates the tracker hardware device of Figure 2.
  • Figure 4 is a diagram of a protocol stack that enables data transfer across the hardware tracker interface link of Figure 3.
  • Figure 5 is an illustration of the message format according to the protocol stack of Figure 4.
  • Figure 6 is a flowchart of the process for formatting a message according to the message format of Figure 5.
  • FIG. 1 a diagram of an exemplary positioning system 100 implemented as a layered host based satellite positioning system with a GPS solution having tracker hardware device 102 in communication with a host computer 104 is shown.
  • the tracker hardware device 102 is connected to a GPS antenna 106 capable of receiving multiple GPS signals 108 from a plurality of satellites.
  • the tracker hardware device 102 is also depicted as being connected to a DC power supply 110.
  • the tracker hardware device 102 communicates with the host computer 104 over a hardware tracker interface link 112.
  • Examples of the hardware tracker interface link 112 includes, but are not limited to, a serial connection (including a universal serial bus (USB), a small computer serial interface (SCSI)), a parallel connection, and a wireless connection (including RF connections and infrared connections).
  • a serial connection including a universal serial bus (USB), a small computer serial interface (SCSI)
  • SCSI small computer serial interface
  • parallel connection including a parallel connection
  • wireless connection including RF connections and infrared connections.
  • the tracker hardware device 102 may be receive power from the DC power supply 110 that is separate from the power supply of the host computer 104, or in an alternate embodiment may receive power from the host computer 104 via the hardware tracker interface link 112. Further, the GPS antenna 106 may be separate from the tracker hardware device 102 or integrated within the same housing as the tracker hardware device 102.
  • the computer host 104 includes a central processing unit (CPU) 202, a hardware tracker interface link 112, and a memory 208.
  • the CPU 202 is a controller and may be implemented as a microprocessor, embedded controller, application specific integrated circuit (ASIC), discrete logic circuits acting as a controller, analog circuits acting as a controller, and a combination of discrete logic and analog circuits.
  • the host computer 104 also includes a secondary storage device 210, and a display 212, and an input interface 214 (e.g., a mouse, keyboard, and the like).
  • An operating system 216 (e.g., Windows CE, Palm OS, UNIX, QNX, or the like) is a plurality of instructions that reside and are executed from memory 208.
  • a plurality of user applications 218 communicates with a positioning library 220 and he operating system 216.
  • One of the user applications 218 may receive position information from the positioning library, and may also communicate commands to the positioning library.
  • the user application 218 may be virtually any program that uses positioning information, including, as examples, a mapping program, course charter, location aid, and the like.
  • the host computer 104 connects through the hardware tracker interface 214 and the interface connection 112 to the tracker hardware device 102.
  • the hardware tracker interface 214 may be virtually any type of data transfer interface (as examples, a serial, parallel, PCMCIA card, USB, PC Card, or network interface).
  • the hardware tracker interface 214 is an RS232 port running at 38,400 bps, N-8-1 that communicates up to 2KB of data per second between the tracker hardware device 102 and the computer host 104.
  • the tracker hardware device (as illustrated by the reference numeral 222) is more closely incorporated into the host computer 104.
  • the tracker hardware device 222 may be directly coupled to the host computer 104 address, data, and control buses 224.
  • the host computer 104 receives and processes navigation information from the hardware tracker 102, or in an alternate embodiment 222 in order to provide the plurality of user applications 218 with position information.
  • the tracker hardware device 102 acquires and tracks GPS satellites and sends raw measurement data to the host computer 104 for position calculation.
  • the tracker hardware device 102 includes an antenna 106 for receiving GPS satellite signals 108 that are filtered by a radio frequency (RF) filter 304 for passing the signals to the RF interface circuit 302.
  • the RF interface circuit 302 processes the signals, produces 2-bit Inphase and Quadrature (I/Q) signals and recovers GPS clocks.
  • the RF interface circuit 302 provides the I/Q signals and GPS clocks to the location processing circuit 306 for digital processing.
  • a reference frequency source 308 e.g., a crystal oscillator
  • RTC real time clock
  • the tracker hardware device 102 may be implemented with components available from SiRF Technology, Inc. of San Jose California.
  • the RF interface circuit 302 may be implemented as a GRF2-/LP integrated circuit.
  • the location processing circuit may be implemented, as examples, as a GSP2t integrated circuit or GSP2e integrated circuit.
  • the tracker hardware device 102 minimizes the overhead on the host computer 104 and operating system 216 by keeping low the maximum transmission rate of raw measurements to the host computer 104 (e.g., one measurement per second).
  • FIG 4 a diagram of a protocol stack 400 that enables data transfer across the hardware tracker interface link 112 of Figure 3 is shown.
  • the transport layer 402 of the protocol stack 400 encapsulates a GPS message within two start characters and two stop characters. The values are chosen to be easily identifiable and such that they are unlikely to occur frequently in the data.
  • the transport layer prefixes the message with a two-byte (15-bit) message length and a two-byte (15-bit) check sum.
  • the values of the start and stop characters and the choice of a 15-bit values for length and check sum are designed such that both message length and check sum can not alias with either the stop or start code.
  • the transport layer 402 does not depend on the payload data, and it does not escape any payload data. Therefore the payload can contain legal start and stop code sequences.
  • the transport layer is constructed such that given a lossless environment all messages will be correctly received. Nonetheless, if data is lost synchronization should be easily regained.
  • the validation layer 404 is of part of the transport layer 402, but operates independently. The purpose of the validation layer 404 is to make transmission errors detectable by a receiving device (tracker hardware device 102 or hardware tracker interface 214).
  • the validation layer 404 has a byte count that refers to the payload byte length.
  • the check sum is a sum on the payload.
  • the check sum is a 15-bit byte check sum of the payload data 406.
  • the payload data 406 is assumed to consist of a single byte message identifier and the remaining data bytes and is encapsulated by the message validation layer 404 and transport protocol layer 402.
  • the tracker hardware device 102 is busy with other applications it may opt not to acknowledge messages from the tracker hardware device 102. In order to maintain synchronization, the messages from the host computer 104 to the tracker hardware device 102 are acknowledged by the tracker hardware device 102.
  • the tracker hardware device 102 and associated software is robust to missing messages and does not have to reset the tracker interface link 112 or the tracker hardware device
  • FIG. 5 an illustration of the message format 500 according to the protocol stack of Figure 4 is shown.
  • the message format 500 starts with a start sequence 502.
  • the start sequence is shown as OxAO, 0xA2, but in alternate embodiments different values may be chosen.
  • the message length 504 follows the start sequence 502.
  • the message length is transmitted high order byte first, followed by the low byte. This is the so-called big-endian order.
  • the High Byte must be less or equal to 0x7F.
  • the protocol has a maximum length of (2 ⁇ 15 - 1) bytes, practical considerations require the implementation to limit this value to a smaller number.
  • the receiving programs may limit the actual size to something less than this maximum.
  • the payload 506 follows the message length 504.
  • the payload 506 may contain any
  • the hardware tracker interface 112 may include an API that includes methods for reading unaligned data into larger processor types.
  • the check sum 508 follows the payload 506 and is transmitted with the high order byte first followed by the low order byte. This is the so-called big-endian order.
  • the check sum is 15-bit check sum of the bytes in the payload data.
  • the receiving device to insure receipt of uncorrupted messages uses the check sum 508 derived by the sending device.
  • the last part of the message format 500 is an end sequence 510.
  • the end sequence 510 is OxBO and 0xB3.
  • end sequence values other than OxBO and 0xB3 may be used.
  • Examples of message sent from the tracker hardware device 102 to the host computer 104 that may be defined by a message identification code (MID) and length carried in the payload 506 include, but is not limited to:
  • MEASURED DATA (MID: 0x20, Len: 85 bytes) One message for every currently tracking channel (0 to 12) tracked by the tracker hardware device 102 and is sent every one second.
  • COMPLETE (MID: 0x23, Len: 36 bytes) Contains tracker status and RTC data. Once a second after initial acquisition to prompt scheduling of one second task. Prior to initial acquisition, whenever location data is not being processed.
  • NAN DATA MID: 0x21 , Len: 49 bytes
  • SBAS DATA (MID: 0x22, Len: 20 bytes) One message per second is sent. 5.
  • ADC/ODOMETER DATA (MID: 0x2D, Len: 111 bytes @ 1Hz or 12 bytes @ 10Hz) Contains 50Hz ADC measurement averaged every lOOmilliSeconds at tracker interrupt along with odometer counter and GPIO inputs (e.g. for reverse input sensing, etc.) Message is sent at 1Hz rate with ten lOOmillisecond measurements or lOHz rate with single measurement. 6.
  • ACKNOWLEDGE (MID: OxOB, Len: 3) If feature is enabled, this is sent in response to a received command from navigation that has been successfully parsed and processed.
  • NO-ACKNOWLEDGE (MID: OxOC, Len: 2) Sent in response to a received command from navigation that is not recognized, or is a valid tracker command but has improperly formatted data fields.
  • Messages may also be sent from a host computer 104 to the tracker hardware device
  • TRACK COMMAND (MID: 0x26, Len: 60 bytes) Command to acquire or reacquire satellites with the sent parameters. Sent as needed.
  • TRACK RESET (MID: 0x27, Len: 9 bytes) Command to cause a reset of tracker software based on parameters sent. Sent as needed.
  • DOWNLOAD MESSAGE (MID: 0x28, Len: variable) Message to cause tracker to write data at a specified address for a specified byte count, or to cause the tracker software to vector to a specified address. Sent as needed.
  • RTC CONTROL (MID: 0x24, Len: variable) Command to control RTC rollover and low power operation using the RTC for timed wakeup and sleep duration.
  • PPS MESSAGE (MID: 0x2A, Len: 9 bytes) One Pulse Per Second interface from Navigation to Tracker software that is sent as needed.
  • the payload 506 for the above messages may contain binary messages, such as:
  • Tracker to Nav - MEASURED DATA Description This data block is sent from the Tracker software to the Navigation software. This message will go out for every channel tracking and is output at a 1 Hz rate. This message will be followed by the COMPLETE Message.
  • 16bit msec_number represents time in units of msec range: 0 to 19
  • 32bit CodeOffset Represents time in units of cycles units: 1/2**10 cycles range: 0 - 1540*1023*2**10 cycles
  • 16bit trk_status Status of the tracker Bit 0: Acq/Reacq successful Bit 1 : Delta carrier phase valid Bit 2: Bit sync complete Bit 3: Subframe sync completed Bit 4: Carrier pullin done Bit 5: Code locked Bit 6: Acq/Reacq failed flag l ⁇ bit CtoN_ratio[10] Carrier to noise ratio each one is collected in 100 ms l ⁇ bit correl_interval Correlation interval units: ms l ⁇ bit search_cnt # of times to search for a SV l ⁇ bit lock_status Lock or not lock flag for each 100ms l ⁇ bit power_bad_count Count of Power in 20 ms below 31 dB-Hz l ⁇ bit phase_bad_count Count of Power in 20 ms below 31 dB-Hz l ⁇ bit delta_car_interval Count of ms contained in delta_carrier phase l ⁇ bit TimelnTrack Count of ms since track started
  • the satellite message structure has a basic format of a 1500 bit long frame made up of 5 subframes, each subframe being 300 bits long. Each subframe consists of 10 words, each 30 bits long. The MSB of all words shall be transmitted first. This message goes out for every channel approximately every 6 seconds.
  • This message is sent at a rate of 1Hz (default) or 10Hz whenever it is enabled by the control words in the Track Reset message. Both ADC channels are sampled in a round-robin fashion at 50Hz whose raw measurements are then averaged every lOOmSeconds in the tracker interrupt along with the current odometer counter value and GPIO states. In 1Hz mode, there are 10 data measurements blocks in one single message. In 10Hz mode, there is a single data measurement per message.
  • This feature can be enabled by the control words in the Track Reset message. If enabled, this message is sent in response to any legal received command from navigation (except Download) that has been successfully parsed and processed.
  • Low power, non-autonomous operation requires re-issuing this command after each wakeup cycle to perpetuate forthcoming low power cycles unless retries have been disabled.
  • Selection of autonomous or non-autonomous mode at startup alters the existing autonomous mode setting previously configured with Track Reset message.
  • Sub message 1 - Sets the tracker to periodically power up and optionally power down after a specified time.
  • Sub message 2 - Sets the tracker to periodically power up in autonomous mode and optionally power down after a specified time.
  • Sub message 3 - Sets the tracker to power up at a specific time of the week in GPS time and optionally power down after a specified time. Time is accurate to about 6 seconds. Setting a field to an illegal value sets it to a don't care state. 8bit seconds match time in seconds (0-59) to wake up
  • Sub message 4 - Sets the tracker to power up in autonomous mode at a specific time of the week in GPS time and optionally power down after a specified time. Time is accurate to about 6 seconds. Setting a field to an illegal value sets it to a don't care state.
  • Sub message 5 Cancel any scheduled RTC controlled power cycling
  • Sub message 6 Instructs the tracker to set the RTC to a time of week close to GPS time. The accuracy is about 6 seconds. This sub message should be issued prior to using sub message 3 or 4 in order to correctly set the RTC for accurate wake up. It will attempt to sync for 2 minutes in the event no satellites are being tracked when the command is issued.
  • the Navigation software will fill this data block to command the tracking process to Acquire and Reacquire satellites.
  • 32bit StartCodeP hase initial code phase in chips
  • 32bit FirstDopSearchSize Size of first Doppler search 32bit half doppler range Size of largest Doppler search
  • 32bit cbin carrier doppler Doppler of initial search bin l ⁇ bit coherent time
  • Coherent integration time 1 obit noncoherent time cnt noncoherent (ms) / coherent (ms)
  • 32bit channel Channel number Set by NAN only l ⁇ bit buf_status This buffer's status(interface) J. ⁇ av to Tracker - TRACK RESET Description: This message is sent from the Navigation Software to the Tracker software to cause a reset of the tracker software. Resets can be issued for the standard soft reset requests or to change the state/modes of the tracker software.
  • the field for commanded clock divisor rate is shared with the commanded ADC rate depending on the control word setting. If both clock rate and ADC control word bits are set, then the field defaults as the commanded clock divisor rate and the ADC rate will remain unchanged.
  • This message is sent from the Navigation Software to cause the Tracker to write data at a specified address for a specified byte count, or to cause the tracker software to vector to a specified address.
  • PPS Pulse Per Second
  • Other messages such as LOCK DATA may me defined to transfer data from the host computer 104 to the tracker hardware device 102 and aid in the trackers ability to acquire satellites and lock onto the GPS signals.
  • LOCK DATA may me defined to transfer data from the host computer 104 to the tracker hardware device 102 and aid in the trackers ability to acquire satellites and lock onto the GPS signals.
  • FIG. 6 is a flowchart of the process for formatting a message according to the message format of Figure 5.
  • the process starts 602 with the tracker hardware device 102 determining that a message to the host computer 104 needs to be formatted 604 (i.e. NAV DATA).
  • a stat sequence 502 OxAO and 0xA2 is entered into a message structure 606.
  • the message structure may be implemented as an array data structure of message format 500 in software located on the tracker hardware device 102.
  • the MID 0x21 associated with the message NAV DATA message that is being formatted and the length of the 49 bytes of data being transferred is inserted in the payload portion 506 of the message structure 608.
  • the end sequence 510 of OxBO and 0xB3 is entered into the message structure to signal the end of the message.
  • the length of the complete message 504 is then determined and entered into the message structure 612.
  • the length of the message is ascertainable because the length of the checksum is known to be 15 bits.
  • the checksum 508 for the message is calculated using a predefined algorithm, such as the algorithm previously described. The calculated checksum is then entered in the message structure 614.
  • the competed message in the message structure is then sent 616 from the tracker hardware device 102 to the host computer 104.
  • the tracker hardware device 102 waits a predetermined time, such as 5 s seconds, to receive an acknowledge message (a receive acknowledge message) from the host computer 104.
  • the host computer 104 may be busy and unable to send an acknowledge message to the tracker hardware device 102.
  • Synchronization of the message link between the fracker hardware device 102 and the tracker hardware interface 214 is maintained when expected acknowledge message are not received at the tracker hardware device 102.
  • the hardware tracker interface link 112 is monitored periodically to determine if synchronization is maintained 618 and processing is complete 622.
  • process shown in Figure 6 may selectively be implemented in hardware, software, or a combination of hardware and software.
  • An embodiment of the process steps employs at least one machine-readable signal bearing medium.
  • machine-readable signal bearing mediums include computer-readable mediums such as a magnetic storage medium (i.e.
  • floppy disks or optical storage such as compact disk (CD) or digital video disk (DND)), a biological storage medium, or an atomic storage medium, a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit having appropriate logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), a random access memory device (RAM), read only memory device (ROM), electronic programmable random access memory (EPROM), or equivalent.
  • PGA programmable gate array
  • FPGA field programmable gate array
  • RAM random access memory device
  • ROM read only memory
  • EPROM electronic programmable random access memory
  • the computer-readable medium could even be paper or another suitable medium, upon which the computer instruction is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • machine-readable signal bearing medium includes computer-readable signal bearing mediums.
  • Computer-readable signal bearing mediums have a modulated carrier signal transmitted over one or more wire based, wireless or fiber optic networks or within a system.
  • one or more wire based, wireless or fiber optic network such as the telephone network, a local area network, the Internet, or a wireless network having a component of a computer-readable signal residing or passing through the network.
  • the computer readable signal is a representation of one or more machine instructions written in or implemented with any number of programming languages.
  • the multiple process steps implemented with a programming language which comprises an ordered listing of executable instructions for implementing logical functions, can be embodied in any machine-readable signal bearing medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, controller-containing system having a processor, microprocessor, digital signal processor, discrete logic circuit functioning as a controller, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)

Abstract

L'invention concerne des procédés et des systèmes qui constituent un système de positionnement géré par l'ordinateur central. Ce système de positionnement géré par le système central comprend une interface de matériel radiogoniométrique (214) qui connecte un matériel radiogoniométrique spécialisé (102) à un ordinateur central (104). L'interface de matériel radiogoniométrique (214) reçoit des informations de positionnement de la part du matériel radiogoniométrique spécialisé (102) et communique avec l'ordinateur hôte (104) au moyen de messages prédéfinis. Ce système de positionnement géré par l'ordinateur central comprend un procédé (400) utilisant un protocole en couche de façon que les applications utilisateur (218) d'un ordinateur central puissent accéder aux données émises par un dispositif à matériel radiogoniométrique.
EP04709100A 2004-02-06 2004-02-06 Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central Withdrawn EP1719318A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2004/003664 WO2005086460A1 (fr) 2004-02-06 2004-02-06 Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central

Publications (1)

Publication Number Publication Date
EP1719318A1 true EP1719318A1 (fr) 2006-11-08

Family

ID=34920918

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04709100A Withdrawn EP1719318A1 (fr) 2004-02-06 2004-02-06 Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central

Country Status (2)

Country Link
EP (1) EP1719318A1 (fr)
WO (1) WO2005086460A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9164176B2 (en) * 2007-06-01 2015-10-20 Novatel, Inc. GNSS receiver and antenna system including a digital communication subsystem
US11614545B2 (en) 2020-03-26 2023-03-28 Novatel Inc. Systems and methods for utilizing a connector with an external antenna to utilize multifrequency GNSS functionality of a mobile device

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5497339A (en) * 1993-11-15 1996-03-05 Ete, Inc. Portable apparatus for providing multiple integrated communication media
US5831545A (en) * 1995-08-25 1998-11-03 Motorola, Inc. Method and apparatus for adjusting a communication strategy in a radio communication system using location
US5832247A (en) * 1995-12-28 1998-11-03 Trimble Navigation Limited PCI card for receiving a GPS signal
US6209090B1 (en) * 1997-05-29 2001-03-27 Sol Aisenberg Method and apparatus for providing secure time stamps for documents and computer files
US6430503B1 (en) * 1998-01-06 2002-08-06 Trimble Navigation Ltd. Distributed GPS navigation system
US6611755B1 (en) * 1999-12-19 2003-08-26 Trimble Navigation Ltd. Vehicle tracking, communication and fleet management system
WO2002031528A2 (fr) * 2000-10-12 2002-04-18 Cyterra Corporation Application de suivi d'utilisateur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005086460A1 *

Also Published As

Publication number Publication date
WO2005086460A1 (fr) 2005-09-15

Similar Documents

Publication Publication Date Title
WO2022156481A1 (fr) Procédé et appareil de prévision d'éphémérides
US7577524B2 (en) Method and system for data detection in a global positioning system satellite receiver
US7348921B2 (en) GPS receiver using stored navigation data bits for a fast determination of GPS clock time
EP1564564B1 (fr) Positionnement à GPS assisté asynchron
US6275185B1 (en) GPS receiver using coarse orbital parameters for achieving a fast time to first fix
EP1649300B1 (fr) Systeme d'etablissement de temps gps approximatif dans une station mobile a l'interieur d'un reseau asynchrone sans fil
US6430503B1 (en) Distributed GPS navigation system
US7365681B2 (en) GPS receiver having a prescribed time-of-entry into an operation mode
EP2872922B1 (fr) Échantillonnage réduit de gps basse puissance
WO2022156480A1 (fr) Procédé et dispositif de prédiction d'erreur d'horloge
WO1998034164A1 (fr) Procede et dispositif pour mesurer le temps dans un systeme de positionnement par satellites
WO2008053308A2 (fr) Identité d'éphéméride basée sur le temps dans des données d'assistance et des messages de demande de données d'assistance
US8462046B2 (en) Managing the measurement of signals
JP5101281B2 (ja) Ｇｐｓ受信器および関連する方法並びに装置
US7546395B2 (en) Navagation processing between a tracker hardware device and a computer host based on a satellite positioning solution system
CN100566207C (zh) 用于高灵敏度卫星定位系统接收器的合成导航数据
US6369753B1 (en) Host-independent monolithic integrated circuit for RF downconversion and digital signal processing of GPS signals
JP3512068B2 (ja) 測位システムにおける時間同期方法およびｇｐｓ受信装置
WO2007129263A2 (fr) Étage d'entrée radiofréquence du gps et procédé correspondant de fourniture de relevé de position, support mémoire et appareil à cet effet
EP1952172B1 (fr) Procede servant a determiner un releve de position gps et recepteur gps correspondant
JP3344470B2 (ja) データ同期方法及びデータ受信装置
US20120154217A1 (en) Method and program of acquiring navigation message, gnss receiving apparatus, and mobile terminal
WO2005086460A1 (fr) Traitement de donnees de navigation dans des procedes de positionnement par satellite geres par l'ordinateur central
US20150323677A1 (en) Position calculation method and position calculation apparatus
KR20070009997A (ko) 호스트 기반 위성 위치확인 솔루션 방법 및 시스템에서의네비게이션 프로세싱

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060816

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE IT

RIN1 Information on inventor provided before grant (corrected)

Inventor name: PANDE, ASHUTOSH

Inventor name: WITANIS, STEFAN

Inventor name: YAMAMOTO, CLIFFORD

Inventor name: NONIS, SEBASTIAN

Inventor name: BULATOVIC, NIKOLA

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE IT

17Q First examination report despatched

Effective date: 20071023

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIRF TECHNOLOGY, INC.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20110901