Search All Patents:

---

Register or Login To Download This Patent As A PDF

---

United States Patent Application	20020057217
Kind Code	A1
Milnes, Kenneth A. ;   et al.	May 16, 2002

---

---

---

Claims

---

We claim:

1. An apparatus for tracking objects, comprising: GPS receivers mounted in moving objects; sensors mounted in said moving objects; a set of one or more base stations; transmitters/receivers at said base stations; transmitters/receivers at said moving objects in communication with said transmitters/receivers at said base station; a GPS reference station in communication with one of said base stations for providing differential GPS information; and a production center in comrunication with said base stations.

2. An apparatus according to claim 1, wherein: said moving objects are race cars.

3. A method for tracking objects, comprising the steps of: using GPS to track a set of objects; sensing data about said set of objects; communicating said data and GPS positions from said objects to base stations using wireless technology; determining a set of statistics about said set of objects; highlighting images of said set of objects in a video; and adding said statistics to said video.

4. One or more processor readable storage devices for storing processor readable code, said processor readable code for programming one or more processors to perform a method for tracking objects, the method comprising the steps of: using GPS to track a set of objects; sensing data about said set of objects; communicating said data and GPS positions from said objects to base stations using wireless technology; determining a set of statistics about said set of objects; highlighting images of said set of objects in a video; and adding said statistics to said video.

---

Description

---

[0001] This application claims the benefit of U.S. Provisional Application No. 60/213,684, "Locating an Object Using GPS With Additional Data," filed on Jun. 23, 2000; U.S. provisional application No. 60/233,360, "System for Tracking Automobiles," filed on Sep. 18, 2000; and U.S. provisional application No. 60/295,310, "Track Model Constraint Enhancement For GPS Receiver," filed on Jun. 1, 2001; all three applications are incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention is directed to a system that uses GPS receivers and other sensors to acquire various information about one or more objects at an event.

[0004] 2. Description of the Related Art

[0005] The television presentation of sporting events needs to be improved. Because of the size and speed of some objects and the distance of the television camera from the objects of interest, some objects at a sporting event are hard to see on a television screen. To compensate for objects that are hard to see on television, broadcasters will use zoom lenses. However, the limited field of view of a zoomed camera prevents the object from being viewed in relation to the playing field and prevents the viewer from seeing other objects that are part of the sporting event. Additionally, even with zoom lenses some objects and/or features remain difficult to see on television.

[0006] In auto racing, for example, it is difficult for a television viewer to identify the cars, determine how many laps a particular car has driven, the order of the cars (e.g. first place, second place, third place, etc.) and the instantaneous velocity of a car. Additionally, because the track is so large a camera can only capture images from part of the track and viewers may miss action in other parts of the track. Other sporting events and non-sporting events also present similar challenges.

[0007] Furthermore, broadcasters may be able to sustain greater viewer interest by presenting the viewers with additional desired information about the event and provide for the use of that information in an exciting way.

[0008] Thus, there is a need for enhancing the television presentation of objects at sporting events.

SUMMARY OF THE INVENTION

[0009] The present invention, roughly described, pertains to a system that uses GPS receivers and other sensors to acquire data about one or more objects at an event. The data acquired by the GPS receivers and the sensors is used to determine various statistics about the objects and/or enhance a video presentation of the objects. In one embodiment, the acquired data is used to determine a three dimensional position of an object, determine the position of an image of the object in a video and enhance the video accordingly.

[0010] One use of the present invention is with a system for tracking automobiles at a race. The system determines statistics about the automobiles and enhances a video presentation of the race. In various embodiments, the system may include RPM sensors, brake position sensors, throttle position sensors, fuel level sensors, temperature sensors, transmission position sensors, cameras, etc. In addition to an automobile race, the present invention can be used in other environments such as with other sporting events and non-sporting events.

[0011] In any system that uses sensors, the reliability of the sensors can be a concern. In one embodiment of the present invention, one subset of one or more sensors can be used to determine data normally acquired by a second subset of one or more sensors if the second subset of one or more sensors are not providing valid data.

[0012] Another embodiment of the present invention synchronizes data among different sensors.

[0013] In one implementation of the present invention, moving objects are highlighted in a video by a highlight that changes orientation according to the attitude of the object being highlighted. A further enhancement includes providing data about the object being highlighted and visually connecting that data to the highlight or the image of the object.

[0014] Various embodiment of the present invention provide different types of data to the viewer or user. For example, in the automobile race embodiment, a user can be provided with information about a car's position in the race (e.g. first place, second place, etc), time behind the leader, lap number, lap fraction, instantaneous velocity, RPM, throttle position, brake position, drafting effect, transmission gear engaged, fuel level, a prediction of when the car's fuel will be depleted, when the car has crossed certain locations on the track, when an accident is occurring and a car's position with respect to other cars which may have already raced.

[0015] The present invention can be accomplished using hardware, software, or a combination of both hardware and software. The software used for the present invention is stored on one or more processor readable storage media including hard disk drives, CD-ROMs, DVDs, optical disks, floppy disks, tape drives, flash memory, RAM, ROM or other suitable storage devices. In alternative embodiments, some or all of the software can be replaced by dedicated hardware including custom integrated circuits, gate arrays, FPGAs, PLDs, and special purpose computers. In one implementation, the present invention is performed by a combination of software, computers (one or more processors, one or more storage devices, I/O, etc), sensors and communication equipment.

[0016] These and other objects and advantages of the present invention will appear more clearly from the following description in which the preferred embodiment of the invention has been set forth in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG. 1 is a block diagram of one embodiment of a tracking system.

[0018] FIG. 2 is a block diagram of one embodiment of a DAPS unit.

[0019] FIG. 3 is a flow chart describing the process of acquiring data on a DAPS unit.

[0020] FIG. 4 is a flow chart describing a communication process for a DAPS unit.

[0021] FIG. 5 is a flow chart describing a process for creating a track model.

[0022] FIG. 6 is a block diagram of a GPS receiver.

[0023] FIG. 7 is a flow chart describing a process performed by the GPS receiver.

[0024] FIG. 8 is a flow chart describing a process for identifying an appropriate triangle from the track model.

[0025] FIG. 9 is a block diagram of a base station.

[0026] FIG. 10 is a flow chart describing the operation of the base station.

[0027] FIG. 11 is a block diagram of the components at a camera location.

[0028] FIG. 12 is a block diagram of the remote camera sensor electronics.

[0029] FIG. 13 is a block diagram of the components at the production center.

[0030] FIG. 14 is a flow chart describing the process of synchronizing GPS time and video time.

[0031] FIG. 15 is a flow chart describing the operation of the production center.

[0032] FIG. 16 is a block diagram of the components for providing physical loop data.

[0033] FIG. 17 is a flow chart describing the method of receiving and processing data.

[0034] FIG. 18 is a flow chart describing the method of processing data.

[0035] FIG. 19 is a flow chart describing the process of determining a lap number and lap fraction.

[0036] FIG. 20 depicts a portion of a race track, divided into sections.

[0037] FIG. 21 is a flow chart describing the process for determining the time behind the leader.

[0038] FIG. 22 is a flow chart describing the process for implementing virtual loops.

[0039] FIG. 23 is a flow chart describing the process for predicting when a car will run out of fuel.

[0040] FIG. 24 is a flow chart describing the process of enhancing video.

[0041] FIG. 25 is a flow chart describing the process of creating a highlight with an orientation determined based on the attitude of the car (or other object).

[0042] FIG. 26 is a flow chart describing the process of using pre-rendered images to display a phantom object.

[0043] FIG. 27 is a block diagram of the components of an alternative embodiment camera location which implements a crash camera.

[0044] FIG. 28 is a flow chart describing the operation of a crash camera.

DETAILED DESCRIPTION

[0045] The present invention pertains to a system that acquires and uses data about one or more objects. For purposes of example and illustration only, the following discussion describes a system used in conjunction with an automobile race. However, the present invention can be used with objects other than cars and can be used in conjunction with events other than auto race events.

[0046] FIG. 1 is a block diagram of one embodiment of the present invention. FIG. 1 shows Data Acquisition and Positioning System (DAPS) 12 with GPS antenna 14 and 900 MHz antenna 16. DAPS 12 is mounted to the object being tracked. In the embodiment pertaining to an automobile race, there will be a DAPS unit 12 mounted to each car being tracked. Thus, although FIG. 1 shows only one DAPS 12, the present invention contemplates using one or more DAPS 12 units. DAPS unit 12 includes a GPS receiver connected to GPS antenna 14. GPS antenna 14 is used to receive signals from one or more GPS satellites. 900 MHz antenna 16 is used to communicate with various base units (e.g. 22, 24, 26 and 28). In one embodiment, the system includes four base stations 22, 24, 26, 28. Base station 22 includes 900 MHz antenna 34, base station 24 includes 900 MHz antenna 36, base station 26 includes 900 MHz antenna 38 and base station 28 includes 900 MHz antenna 40. In one embodiment, there can be more than four base stations or less than four base stations. It is contemplated that base stations will be located at different parts of the racetrack (or other event). The base stations transmit data to and receive data from each of the DAPS units via the 900 MHz antennas.

[0047] Data from each of the base stations is communicated to production center 50 using DSL modems. FIG. 1 also shows camera locations 52 and 54. In various embodiments, there can be one camera location, two camera locations or more than two camera locations. Each camera location includes one or more cameras and electronics for instrumenting those cameras. Each of the camera locations is in communication with production center 50. In one embodiment, the system of FIG. 1 is used to track a three dimensional location of each of the cars during an automobile race, in real time. The system also tracks the movement of each of the cameras used to broadcast the race. Based on the information about the attitude of the cameras and the three dimensional locations of the cars, the system can highlight a live video of the race to produce a number of effects desired by the production team.

[0048] Base station 22 includes GPS reference station 20 with GPS antenna 32. This reference station is surveyed with accuracy to determine its location. Reference station 20 receives GPS information from GPS satellites and determines differential GPS error correction information. This error correction information is communicated from the GPS reference station (via base station 22) to production center 50 for eventual retransmission to each of the base stations. The base station will send the information to each of the DAPS units. In another embodiment, the system of FIG. 1 can use pseudolites to provide additional data to the GPS receivers in the DAPS units.

[0049] FIG. 2 is a block diagram of DAPS unit 12. FIG. 2 shows wireless modem 60, CPU 62, GPS receiver 64, analog sensors 66, and digital sensors 68. In one embodiment, modem 60 is a Utilicom 2020 radio modem, CPU 62 is a 486 processor, and GPS receiver 64 is a NovAtel OEM4 GPS receiver. DAPS unit 12 also includes a number of sensors for sensing data about the automobile. For example, the system could include a brake sensor for determining the position of the brake pedal, an RPM sensor for determining the instantaneous RPM, throttle sensor for determining the position of the throttle, gear sensors for determining the position of the transmission, temperature sensors, sensors for determining information about the driver, etc. Some of these sensors are digital sensors 68 and some of these sensors are analog sensors 66. The remaining components of DAPS 12 are interface electronics. Some of the interface electronics are contained on a FPGA, as noted by dashed line 70.

[0050] Serial to parallel module 74 converts serial data from modem 60 to an 8-bit parallel stream. The modem does not have a byte sync signal, so it receives a signal from frame sync detector 76 once a frame sync is detected. Once the frame sync signal has been detected, the serial to parallel module 74 will clock a byte out once every 8 bits have been received. Frame sync detector 76 samples a synchronous serial data stream looking for a particular pattern of bits. Once the frame sync has been detected, it signals the condition to the serial to parallel module.

[0051] All data messages are sent with a packet header. The packet header contains the length of the packet, a time slot number, and a CRC. Packet header detector 78 reads the data stream from the serial to parallel module 74 looking for a packet header with a valid CRC. Once a valid packet header is detected, it clocks the header and the remainder of the packet into Rx FIFO 82. Data will be clocked into the Rx FIFO until the modem DCD line becomes inactive. Packet header detector 78 contains a programmable address mask. This mask is used to filter out packets not addressed to the system. If the packet header is received with bit 7 of the control character set, the condition slot number is indicated to the master clock 80. Master clock time is synchronized by a packet header where bit 7 of the control character is set. Once this signal is received, the time slot clock counters reset to the time slot indicated in the control character. The counters are adjusted to account for the length of the packet header so the counter is aligned with the start of the next packet. Master clock 80 generates a time slot counter. The time slot counter is used by Tx control 86 to determine when to send data to the transmitter. Rx FIFO 82 is used to buffer a receive data packet. The FIFO will indicate to the CPU via an interrupt when a complete data packet is loaded into the FIFO.

[0052] Parallel to serial module 84 translates parallel data from the Tx FIFO 86 to a serial stream. The serial data is clocked out by a clock provided by modem 60. Tx control 86 controls when a packet is sent to modem 60. It contains four time slot registers. The first time slot register is loaded from the default time slot dipswitch. The remaining time slot registers as well as a default time clock register may be set by CPU 62. When master clock 80 sends a time slot signal which matches one of the time slot registers, an interrupt signal is sent to the CPU interface and sets RTS active. The CPU starts to load the Tx FIFO 88 with data. The modem will turn on and set the CTS line active after approximately 2.8 ms. Once the RTS line is active, the Tx control module will enable parallel to serial module 84. Tx FIFO 88 will send a signal when it is empty. Once this condition is detected, the Tx control module will set the RTS line inactive, thus completing the packet. The Tx FIFO module buffers data sent from the CPU interface. It will normally hold one complete packet including the packet header, data payload and trailer CRC.

[0053] Communication to and from CPU 62 is via CPU interface 72. In one embodiment, CPU interface 72 is in communication with Rx FIFO 82, Tx control 86, Tx FIFO 88, frequency translator control 96, digital I/O 94, ADC 92, UART 90, default address dip switch 102 and EEPROM 104. In one embodiment, EEPROM 104 stores code for programming CPU 62. In another embodiment, the code for programming CPU 62 is stored in a flash memory.

[0054] UART 90 is used to communicate to GPS receiver 64. An 8-channel 10-bit or greater ADC is used to sample various sensors on the system. All 8 channels can be sampled at 10 Hz per channel. This module may be part of the interface board or may be supplied by the CPU module. All analog lines should be protected against high voltage transients. The analog input interface may support rheostat sensors. Sixteen general purpose digital I/O signals (see digital I/O module 94) can be available for digital sensor 68. Frequency translator control 96 is a digital output register. In one embodiment, frequency translator 98 is used to shift the frequency of the modem. In another embodiment, frequency translator 98 is not used.

[0055] Batteries are used to power the system (see power supply and control 100). Two modes are supported, standby and operate. In the standby mode, only the CPU is powered. In operate mode, all modules are powered. The CPU is able to switch the modes.

[0056] FIG. 3 is a flowchart describing the collection of data in DAPS unit 12. In step 130, GPS data is received by CPU 62 from GPS receiver 64. In one embodiment, GPS data is received five times per second. In step 132, sensor data is acquired using analog sensors 66 and digital sensors 68. In step 134, GPS data and sensor data are stored in Tx FIFO 88. The process of FIG. 3 is continuously performed during normal operation of DAPS 12.

[0057] FIG. 4 is a flowchart describing communication to and from DAPS 12. To facilitate communication between the many DAPS units and the base stations, time is divided into a repeating set of time slots. Each modem is assigned a time slot during which it may transmit. As a car moves around the track, its DAPS unit will transmit during the appropriate time slot to all base stations that can hear the signal. In step 140, DAPS 12 waits for its time slot. While waiting, it listens for incoming messages. If a message is received (step 142), then the DAPS unit acts on that message in step 144. More detail on the messages is provided below. If an interrupt is received, the method loops to step 146. The system is set up so that an interrupt is sent to CPU 62 just prior to the time slot for the particular DAPS unit. After receiving the interrupt, the system will assemble the outgoing message in step 146. These outgoing messages include one or more GPS derived positions received since the last message was sent and the data from the various sensors received since the last message was sent. In step 148, the system will wait for the exact time for the time slot. In step 150, the assembled message will be transmitted during the allotted time slot. In one embodiment, step 150 is performed two times per second.

[0058] Data is transmitted to and from the DAPS units using a communication model having four layers: a physical layer, a link layer above the physical layer, a network layer above the link layer, and a command layer above the network layer. The structures of the messages at each layer are provided below.

1TABLE 1 Physical Layer Syntax Bits Format Description PhysicalLayerHeader() { FrameSync 32 uimsbf Frame sync pattern PhysicalPayload Variable } Total Length 32 + Variable

[0059] At the link layer, all data transmissions are formatted in a packet. The link layer packet header and trailer encapsulate the network layer packets Error checking is performed at the packet level. The packet header contains a CRC used by the interface hardware to correctly assemble the proper number of bytes for a complete packet. The interface hardware also uses the packet header to time synchronize the remote modems.

2TABLE 2 Link Layer Syntax Bits Format Description LinkLayerPacket() { LinkHeader() { PacketLength 8 uimsbf Length of data payload SystemActive 1 uimsbf Set to command all remotes that are enabled to enter wake state SlotNumber 7 uimsbf Slot number for source modem Clock Sync Bit 1 uimsbf Set if this is a clock synchronization packet SourceAddress 7 uimsbf Address of source modem HeaderCRC 16 uimsbf Lower 16 bits of 32 bit CRC. CRC is computed from PacketLength to ClockSyncBit. Polynomial = X.sup.32 + X.sup.26 + X.sup.23 + X.sup.22 + X.sup.16 + X.sup.12 + X.sup.11 + X.sup.10 + X.sup.8 + X.sup.7 + X.sup.5 + X.sup.4 + X.sup.2 + X.sup.1 + X.sup.0 The CRC calculation is seeded with 0.times.ffffffff. The result of the CRC computation is stored as the 1's compliment of the result. } LinkPayload Variable uimsbf TrailerCRC 32 uimsbf 32 bit CRC of header and payload. CRC starts from first byte of LinkPayload and ends at end of LinkPayload. Polynomial = X.sup.32 + X.sup.26 + X.sup.23 + X.sup.22 + X.sup.16 + X.sup.12 + X.sup.11 + X.sup.10 + X.sup.8 + X.sup.7 + X.sup.5 + X.sup.4 + X.sup.2 + X.sup.1 + X.sup.0 The CRC calculation is seeded with 0.times.ffffffff. The result of the CRC computation is stored as the 1's compliment of the result. } Total Length 288 + Variable

[0060] The system also makes use a second version of a link layer packet for communications between a base station and production center 50. Data 5 originating from DAPS units passing through base stations will be stripped of their link layer (above) and will be shipped to the Communications Controller computer 520 (see FIG. 13) with this reduced link layer packet inside a TCP/IP packet.

3TABLE 3 Link Layer II Syntax Bits Format Description LinkLayer2Packet() { Link2Header() { SourceAddress 7 uimsbf Address of DAPS modem Pad 1 uimbsf prevents misalignment } LinkPayload Variable uimsbf } Total Length 8 + Variable

[0061] The Network layer is used to assemble and delineate individual commands. One packet may contain a partial, 0, 1 or more commands. The Network Layer Header contains a length and sequence number. With knowledge of the fragment length and packet length, the network parser can loop through multiple packets and may re-assemble a packet which spans packets.

4TABLE 4 Network Layer Syntax Bits Format Description Network_Layer() { NetworkHeader() { FragmentLength 8 uimsbf Length of current fragment, including header. NetworkLength 10 uimsbf Length of packet, excluding header. This length represents the total length of the entire assembled network packet payload. PortNumber 2 uimsbf Stays the same for all data coming from a particular socket on the originating device. SequenceNumber 10 uimsbf Sequence number for all messages coming from a particular port. This increases with every message or fragment. This rolls over back to 0 only after 2 10 messages/fragments have been sent. NetworkStart 1 uimsbf This bit is set if this is the first fragment of a command or a complete command. NetworkStop 1 uimsbf This bit is set if this is the last fragment of a command or a complete command. } NetworkPayload Variable uimsbf Command payload. } Total Length 24 + Variable

[0062] The Command layer is used to identify command types. With knowledge of the length of each command type, multiple commands may be placed in a packet

5TABLE 5 Command Layer Syntax Bits Format Description Command_Layer() { CommandHeader() { CommandNumber 8 uimsbf Denotes the command type } CommandPayload Variable uimsbf } Total Length 1 + Variable

[0063] Each modem is assigned an address. The one byte address space is broken into three ranges which describe the type of station.

6TABLE 6 Address Map Address Description 0 Address of the master base station. 1-7 Address range for slave base stations. 8-254 Address range for remote stations.

[0064] Message Commands

[0065] The Command Number in the Command Packet Header describes the type of command being sent. Commands may have 0, 1 or more bytes of payload. The size of the payload is command dependent. Various commands are described below.

[0066] The Position Report, command 1, is the primary message sent from the DAPS unit to the base stations. It contains position and sensor data.

7TABLE 7 Position Report Syntax bits Format Description Position_Report() { LatitudeRef 32 simsbf Absolute Latitude LongitudeRef 32 simsbf Absolute Longitude AltitudeRef 32 simsbf Absolute Altitude Time (bits 0-31) 32 uimsbf Absolute time associated with first latitude/longitude and sensor report. LSB of time represents 0.01 seconds. Time is offset from January 1, 1999. Time (bits 32-35) 4 uimsbf StandardDev 4 uimsbf the range of actual standard deviation NumberLatLonDeltas 4 uimsbf Number of Lat/lon deltas sent in this message NumberSensorReports 4 uimsbf Number of sample reports sent in this message for (i = 0; i < NumberLatLonDeltas; i++) { LatitudeDelta 16 simsbf Change in Latitude from previous sample LongitudeDelta 16 simsbf Change in Longitude from previous sample AltitudeDelta 16 simsbf Change in Altitude from previous sample Time Delta 8 uimsbf Change in time from previous sample } for (i = 0; i < NumberLatLonDeltas + 1; i++) { StandardDev 4 uimsbf range of actual standard deviation } If (NumberLatLonDeltas = odd) { NULL 4 uimsbf } for (i = 0; i < NumberSensorReports; i++) { RPM 16 simsbf engine RPM Throttle 8 uimsbf throttle position Brake 8 uimsbf brake position Other Sensor 8 uimsbf data from other sensor Time Delta 8 uimsbf change in time from last sample } }

[0067] The Status Report message, command 2, is sent by the DAPS units to the base stations to report on various status parameters.

8TABLE 8 Status Command Syntax Bits Format Description Status_Report() { Time (bits 0-31) 32 uimsbf Absolute time associated with first latitude/longitude and sensor report. LSB of time represents 0.01 seconds. Time is offset from January 1, 1999 Time (bits 32-35) 4 uimsbf NULL 4 uimsbf Temperature 8 simsbf in centigrade Battery Voltage 16 uimsbf one LSB = .001 V }

[0068] The base stations will broadcast the Enable Position Report message, command 8, to enable a set of DAPS units to send position reports (command type 1).

9TABLE 9 Enable Position Report Syntax Bits Format Description EnablePositionReport() { AddressBitmap 256 uimsbf Address bitmask is 256 bits (32 bytes) long. The bit position designates a particular address LSB represents address 0, MSB represents address 255. }

[0069] The base stations will broadcast the Wake Mode message, command 9, to set all modems to wake mode. The SystemActive bit must be set in the Link Layer Packet Header and the modem must have the address bitmask bit set to enter wake mode.

10TABLE 10 Wake Mode Message Syntax Bits Format Description EnableTransmissions() { AddressBitmap 256 uimsbf Address bitmask is 256 bits (32 bytes) long. The bit position designates a particular address LSB represents address 0, MSB represents address 255. }

[0070] The base stations will send an Assign Time slot message, command 10, to a DAPS unit to request that the DAPS unit start transmissions on the specified time slot.

11TABLE 11 Assign Time slot Message Syntax Bits Format Description AssignTime slot() { SlotNumber 8 uimsbf Slot number for transmissions Address 8 uimsbf Address of DAPS }

[0071] Any modem may send an Echo Data Request message, command 11, to any other modem. The receiving modem will extract the source address from the packet header and send an Echo Data Response command back to the source modem with the EchoData.

12TABLE 12 Echo Data Request Syntax Bits Format Description EchoDataRequest() { Address 8 uimsbf Address of modem being requested to echo data EchoData Variable uimsbf Data. May be any characters }

[0072] The Echo Data Response, command 12, is the response to theEcho Data Request command. Any modem will respond to an Echo Data Request command by sending the Echo Data Response message.

13TABLE 13 Echo Data Response Syntax Bits Format Description EchoDataResponse() { Address 8 uimsbf Address of modem which sent the Echo Data Request command EchoData Variable uimsbf Data received in the Echo Data Request message }

[0073] The base station will send the Power Mode message, command 13, to a DAPS unit to request that the DAPS unit change the wake period and sleep period

14TABLE 14 Power Mode Message Syntax Bits Format Description PowerMode() { AddressBitmask 256 uimsbf 256 bits (32 bytes) long. The bit position designates a particular address LSB represents address 0, MSB represents address 255. WakePeriod 32 uimsbf The time between now and when the device should wake up. SleepPeriod 32 uimsbf An interval that indicates to wake up every SleepPeriod interval and check for power mode messages. After a short time, it will go back to sleep if not instructed otherwise. }

[0074] The time slot broadcast message, command 15, will request the DAPS units to set the period of their time slots.

15TABLE 15 Slot Time Message Syntax Bits Format Description SlotTime() { Time 8 uimsbf Period in 100's of microseconds for each time slot }

[0075] The "number of slots" command, command 16, will be sent by the base stations to request the DAPS units to set the total number of time slots.

16TABLE 16 Number Slots Syntax Bits Format Description NumberSlots() { NumberSlots 8 uimsbf Number of slots }

[0076] In one embodiment, the base stations will send RTCA command 17 to the DAPS units to convey differential GPS information. In another embodiment, different commands can be used to convey different types of differential GPS information.

17TABLE 17 RTCA Syntax Bits Format Description RTCA1Wrapper() { DataLength 8 uimsbf length of the Data field. Data Variable uchar[len] Array of unsigned characters that should be passed directly from the receiving modem to the GPS receiver }

[0077] The Debug command 20 is sent to convey special debugging information to the addressed device that is parsed and handled by an object separate from the standard command hierarchy.

18TABLE 18 DEBUG Syntax Bits Format Description DEBUG() { DataLength 8 uimsbf length of the Data field. Data Variable uchar[len] Array of unsigned characters that should be passed directly to the DEBUG handling object. }

[0078] In one embodiment, the system will operate with 51 time slots. Two slots are reserved for transmit and receive transition, 6 time slots are reserved for base stations and 43 time slots are reserved for remote stations.

19 Time Slot Timing Parameters Cycle Period 0.500 sec Number time slots 51 Time slot length 0.0098 sec Preamble time 0.0031 sec Data time 0.0067 sec Bit Rate 148,640 bits/sec Total Data Bits 996 bits Total Data Bytes 124 bytes/sec

[0079] The position of each DAPS unit is determined by using the Global Positioning System (GPS). GPS is a satellite based navigation system operated and maintained by the U.S. Department of Defense. GPS consists of a constellation of GPS satellites providing worldwide, 24 hour, three dimensional navigational services. By computing the distance to GPS satellites orbiting the earth, a GPS receiver can calculate an accurate position of itself. This process is called satellite ranging. The position being tracked is the position of the antenna of the GPS receiver.

[0080] Each GPS satellite carries an atomic clock to provide timing information for the signals transmitted by the satellites. Internal clock correction is provided for each satellite clock. Each GPS satellites transmits two spread spectrum, L-band carrier signals-an L.sub.1 signal with carrier frequency f.sub.1=1575.42 MHz and an L.sub.2 signal with carrier frequency f.sub.2=1227.6 MHz. These two frequencies are integral multiples f.sub.1=1540f.sub.0 and f.sub.2=1200f.sub.0 of a base frequency f.sub.0=1.023 MHz. The L.sub.1 signal from each satellite uses binary phase shift keying (BPSK), modulated by two pseudorandom noise (PRN) codes in phase quadrature, designated as a C/A code and P code. The L2 signal from each satellite is BPSK modulated by only the P code.

[0081] A GPS receiver measures distance using the travel time of radio signals. To measure travel time of a GPS signal from the satellite to a receiver, the receiver will generate the same pseudo-random code as the satellite and compare the generated code with the received code to determine the shift between the two codes. The travel time is multiplied by the speed of light to determine the distance between the satellite and the receiver. Along with distance, a GPS receiver needs to know exactly where the satellites are in space. A calculation of a three dimensional location generally requires valid data from four satellites. GPS receivers can also provide precise time information.

[0082] The above described method of computing position requires very accurate synchronization of the satellite and receiver clocks used for the time measurements. GPS satellites use very accurate and stable atomic clocks, but it is economically infeasible to provide a comparable clock in a receiver. The problem of clock synchronization is circumvented in GPS by treating the receiver clock error as an additional unknown in the navigation equations and using measurements from an additional satellite to provide enough equations for a solution for time as well as for position. Thus, the receiver can use a less expensive clock for measuring time. Such an approach leads to the pseudorange measurement:

p=c(t.sub.rcve-t.sub.xmit)

[0083] where t.sub.rcve is the time at which a specific, identifiable portion of the signal is received, t.sub.xmit is the time at which that same portion of the signal is transmitted, and c is the speed of light. Note that t.sub.rcve is measured according to the receiver clock, which may have a large time error. The variable t.sub.xmit is in terms of GPS satellite time.

[0084] If pseudorange measurements can be made from at least four satellites, enough information exists to solve for the unknown position (X, Y, Z) of the receiver antenna and for the receiver clock error C.sub.b. The equations are set up by equating the measured pseudorange to each satellite with the corresponding unknown user-to-satellite distance plus the receiver clock error:

p.sub.1={square root over ((x.sub.1-X).sup.2+(y.sub.1+Y).sup.2+(z.sub.1+Z)- .sup.2)}+c.sub.b

p.sub.2={square root over ((x.sub.2-X).sup.2+(y.sub.2+Y).sup.2+(z.sub.2+Z)- .sup.2)}+c.sub.b

p.sub.3={square root over ((x.sub.3-X).sup.2+(y.sub.3+Y).sup.2+(z.sub.3+Z)- .sup.2)}+c.sub.b

p.sub.4={square root over ((x.sub.4-X).sup.2+(y.sub.4+Y).sup.2+(z.sub.4+Z)- .sup.2)}+c.sub.b

[0085] where p.sub.1 denotes the measured pseudorange of the ith satellite whose position in ECEF coordinates at t.sub.xmit is (x.sub.1, y.sub.1, z.sub.1,). There are four equations depicted above. The unknowns in this nonlinear system of equations are the receiver position (X,Y,Z) in ECEF coordinates and the receiver clock error C.sub.b. If more than four satellites are used, there will be an equation for each satellite.

[0086] There are a number of errors that are associated with GPS ranging, including errors due to the Earth's ionosphere and atmosphere, noise, multipath satellite clock, and ephemeris errors. Additionally, basic geometry itself can based on the configuration of the satellites in the sky can magnify the errors. The dilution of precision, a measure of error, is a description of the uncertainty of particular GPS data.

[0087] One enhancement to standard GPS technology includes the techniques of differential GPS, which involves a reference GPS receiver that is stationary and has its position accurately surveyed. To understand differential GPS, it is important to know that satellite signals have errors which have a high spatial and temporal correlation. So, if two receivers are fairly close to each other, the signals that reach both of them will have traveled through virtually the same slice of atmosphere, and will have virtually the same errors. With differential GPS, the stationary reference receiver is used to measure errors. The reference receiver then provides error correction information to the other receivers (e.g. roving receivers). This way, systemic errors can be reduced. The reference receiver receives the same GPS signals as the roving receivers. Instead of using timing signals to calculate its position, the reference receiver uses its known position to calculate timing. It figures out what the travel time of the GPS signals should be, and compares it to what they actually are. The difference is used to identify the error information (also called differential corrections or differential GPS data). The reference receiver then transmits the differential corrections to the roving receivers in order to correct the measurement of the roving receivers. Since the reference receiver has no way of knowing which of the many available satellites a roving receiver might be using to calculate is position, the reference receiver quickly runs through all the visible satellites and computes each of their errors. The roving receivers apply the differential corrections to the particular satellite data they are using based on information from the reference receiver. The differential correction from the reference receiver improves the pseudorange position accuracy because its application can eliminate to varying degrees many of the spatially and temporally correllated errors in the pseudorange measured at the rover receiver. A differential GPS reference receiver can also transmit its carrier measurements and pseudoranges to the roving receiver. The set of measurements and pseduoranges transmitted from the reference receiver can be used to improve the position accuracy through the use of differential carrier positioning methods.

[0088] One embodiment of the present invention uses a track model to constrain a GPS derived position. In one implementation, a track model is a set of two or more planar surfaces which approximate the (contiguous or non-contiguous) surface (or surfaces) on which the navigation takes place (or near where navigation takes place). A track model can model may different types of surfaces, and is not confined to only model a race track. In one embodiment, each planar surface is defined by three vertex points and, thus, is a triangle. Other shapes can also be used. In one implementation, the constraint provided by the track model is that while the antenna is "within" the triangle, the position of the antenna is constant in the direction normal to the planar section. Based on a fixed antenna height, a planar constraint can be defined with respect to the local planar section.

[0089] The track model positions are defined in WGS84 geographic coordinates but the internal reference frame for the GPS filter is in ECEF coordinates. This would not be a problem (the geographic co-ordinates can be simply transformed to ECEF vectors), except that the triangle search engine (described below) requires a primarily two dimensional frame. This could be satisfied if the internal position was transformed to geographic co-ordinates, but this transformation is time consuming, and it is possible that it may have to be carried out more than once per solution. So, the system generates a local (or intermediate) frame representing the model and a simple transformation that converts vectors in the ECEF frame to vectors in the local frame. The corner positions of all the triangles (in the ECEF frame) are differenced with a local "base position." These are rotated to the local frame by the rotation matrix required to rotate a vector in the ECEF frame at the base position to a vector at the base position but in the geographic frame. Local coordinates are generated in this manner for all the points in the track model. The generation is as follows:

[0090] Coordinates of model point in the local frame:

P.sub.1=R.sub.e.sup.1*(P.sub.ECEF-P.sub.BaseECEF)

[0091] where P.sub.BaseECEF is the base position vector in the ECEF frame, P.sub.ECEF is the track model position in the ECEF frame, and R.sub.e.sup.1 is the rotation matrix used to transform a vector in the ECEF frame to the geographic frame at the base position.

[0092] If a triangle search is required (see below), the current GPS position is transformed to the local frame via the same method and the search progresses as usual in that frame. Internally in the GPS receiver, the coordinates for all the points in the track model are maintained both in the ECEF frame and in the local frame. The constraint position is generated from the ECEF coordinates, and the search algorithm is applied using the coordinates in the local frame. The search algorithm described later finds an appropriate triangle. The previously generated constraint position is taken from it and used as a seed position in the least squares pseduorange filter and as a position update in the Kalman filter used to generate refined carrier based positons. In the pseudo range case, the 6 weight matrix elements for that triangle constraint are expanded to generate a weight matrix P.sub.X for the least squares filter. Alternatively, in the combined pseudo range/carrier observation case, the 6 elements representing the upper triangular portion of the covariance matrix for that triangle constraint are expanded to generate a covariance matrix .sub.Cx for the Kalman filter.

[0093] FIG. 5 is a flow chart describing the process for creating a track model. In step 160, various locations on the ground at or near the race track (or other surface) that are easy to recognize are accurately surveyed. In step 162, aerial photographs are taken of the race track (or other surface). The photographs are taken from an aircraft approximately 300 meters above the track surface and are overlapping so that they capture each location on the race track and each of the surveyed location from at least two angles. The location of the aircraft is recorded for each photograph (step 164). In step 166, photogrammetry is used to determine thousands of three dimensional coordinates along the track surface and location near the edge of the track. In step 168, the edges of the track surface are extracted. In some cases, the edges of the track surface include an inner oval (or other shape) and an outer oval (or other shape). In step 170, the track surface is divided into a set of two or more sub-surfaces. In one embodiment, the sub-surfaces are polygons (or other shapes). In one implementation, step 170 includes dividing the track into triangles using Delauney triangulation. In step 172, the triangles are transformed from the geographic frame to the local frame as discussed above. In step 174, the triangles are transformed to the ECEF frame. In step 176, the system computes the covariance matrix C.sub.X and the weight matrix P.sub.X (described below) with respect to the ECEF frame for each triangle. In step 178, the entire track model space is divided into a grid. In one embodiment, the grid includes 256 equally sized rectangles in the local frame.

[0094] In one implementation, the process of FIG. 5 is performed prior to a race (or other event). After the process of FIG. 5 is completed, the track model is available to the GPS receiver for use in determining the position of the GPS antenna.

[0095] FIG. 6 is a block diagram of the major components of one embodiment of a GPS receiver that can be used with the current invention. Other receiver configurations and designs can also be used with the current invention. FIG. 6 shows antenna 14 connected to low-noise amplifier ("LNA") 200. LNA 200 is connected to RF to IF translation unit 202, which translates the incoming RF signal to an IF signal usable by the digital section of the receiver. RF to IF translation unit 202 supplies power to LNA 200 and receives a clock signal from on-board 20MHz voltage controlled, temperature compensated crystal oscillator (VCTCXO) 210. The digital section of the receiver receives a down-converted, amplified GPS signal which it digitizes and processes to obtain a GPS solution (position, velocity and time). The GPS signal is sent from RF to IF translation unit 202 to signal processor 204. In one embodiment, the analog to digital converter is part of signal processor 204 and receives the signal from RF to IF translation unit 202. In another embodiment, the analog to digital converter is a separate component between RF to IF translation unit 202 and signal processor 204. Signal processor 204 receives a clock signal from VCTCXO 170, provides a clock signal to CPU 206 and sends information back to RF to IF translation unit 202 (see signal AGC). Signal processor 204 receives control signals from CPU 206 and provides data to CPU 206. Information is transmitted between CPU 206 and system I/0 208 for communication with components outside of the receiver. Differential GPS data is provided to the GPS receiver via system I/0 208. Not explicitly depicted in FIG. 2 are various supporting circuitry, memory (which may be part of the CPU), control and configuration logic, and serial peripheral devices, each of which can be separate components or part of one of the depicted components (including the processor). One example of a GPS receiver is the OEM4 from Novatel, Inc.

[0096] FIG. 7 is a flow chart describing one embodiment of the operation of a GPS receiver according to the present invention. In step 240, one or more signals from a set of satellites are received. In step 242, psuedoranges are determined. FIG. 7 shows that after step 242, two independent processes are performed. The first process includes steps 244-248. The second process includes steps 250-260.

[0097] In step 244, differential corrections are received from the differential reference receiver. In step 246, the system accesses the track model and determines the appropriate planar surface to use for constraining the GPS determined position. In one embodiment, the track model is comprised of a set of triangles and step 246 includes determining which triangle represents the portion of the track that the receiver is currently on (or within). In one implementation, there are four relevant frames: (1) ECEF, (2) local frame, (3) geographic frame (e.g. WGS84), and (4) the planar surface (or triangle) frame. One embodiment of the track model is originally created and broken into triangles in the geographic frame. All of the vertices of the triangles are converted to the local frame and the ECEF frame prior to the race (or other event). The position supplied to the search mechanism of step 246 is converted from ECEF to the local plane in real-time and the search mechanism operates in the local frame. The result of the search mechanism is an identification of a triangle in the local plane, which is used to access the three vertices of the triangle already converted to the ECEF frame. In step 248, the GPS receiver performs a least squares process using the triangle identified in step 246.

[0098] In step 250, the system receives pseudoranges and carrier measurements from the reference receiver. In step 252, the system determines carrier measurements. In step 254, the system performs the double difference/carrier filter. In step 256, the system determines the appropriate triangle. In step 258a floating ambiguity estimator is used, which provides a position covariance. In step 260, ambiguities are fixed using an integer ambiguity estimator. More detail about steps 252-260 are provided below.

[0099] In step 262, the system chooses the best position to report, based on the least squares process, the floating ambiguity estimator and the integer ambiguity estimator. In step 264, the position determined by the GPS receiver is reported. In one embodiment, reporting includes transmitting an electronic message to a client device so that the position, velocity and time can be stored, used, displayed, etc. In a different alternative, the receiver will initially report the position based on step 248, and after a predesignated amount of time or calculations the receiver will report the position based on steps 258 and 260.

[0100] FIG. 8 is a flow chart that describes the process of determining which triangle of the track model the receiver is currently navigating on. In step 300, the process receives a position of the receiver. In one embodiment, the position received in step 300 is the position generated by the GPS receiver at the last epoch. In another embodiment, the position received in step 300 is a current position determined by the GPS receiver without using the track model constraint.

[0101] In one implementation, the process of FIG. 8 is performed twice: once for the least squares process and once for the Kalman filter. When performing the process of FIG. 8 for the least squares process, step 300 includes receiving the position generated by the GPS receiver at the last epoch for the least squares process. When performing the process of FIG. 8 for the Kalman filter, step 300 includes receiving the current position determined by the GPS receiver without using the track model constraint for the Kalman filter.

[0102] In step 302, the receiver determines the rectangle in the track model space (see step 176) that contains the position received in the previous step. If no such rectangle is found (step 304), than the process reports in step 306 that the position is not within a triangle and the track model cannot be used to constrain the GPS position. If a rectangle is found (step 304), then the GPS receiver accesses one of the triangles within the rectangle in step 308 and determines whether the position (from step 300) is in (or on) the triangle in step 310. A triangle is in a rectangle (for purposes of step of 308) if any part of the triangle is within the rectangle. Thus, a triangle can be in many rectangles and a rectangle may contain many triangles. Step 310 can be performed by comparing the coordinates of the vertices of the triangle to the position from step 300. If the position is within the triangle (step 310), then the process of FIG. 8 identifies the triangle in step 312. If the position was not in the triangle (step 310), then the process determines whether there are more triangles in the rectangle that need to be considered (step 314). If there are more triangles to consider, then the method loops back to step 308. If there are no more triangles to consider, then the process reports in step 316 that the position is not within a triangle and the track model cannot be used to constrain the GPS position.

[0103] Step 248 includes using a least squares process with the identified triangle. The least squares process is described below. The modification required to constrain to a planar surface follows.

[0104] The least squares filter generates corrections to the system's ECEF position and clock according to the equation:

.delta.X=(A.sup.TPA).sup.-1A.sup.TP.omega.

[0105] where .delta.X=correction vector to position vector and clock [X,Y,Z,Clk].sup.T A=design matrix (n.times.4) based on satellite to receiver geometry

[0106] In detail A=[A.sub.1, A.sub.2, A.sub.3...A.sub.n].sup.T

[0107] And A.sub.i=[.differential.R.sup.i/.differential.X, .differential.R.sup.i/.differential.Y, .differential.R.sup.i/.differentia- l.Z,1]

[0108] With R.sup.1=((X.sup.i-X).sup.2+(Y.sup.i-Y).sup.2+(Z.sup.i-Z).sup.2- ).sup.1/2

[0109] X,Y,Z=ECEF user position

[0110] X.sup.i, Y.sup.i, Z.sup.i=ECEF satellite position P=Pseudo range observation weight matrix (nxn) which is diagonal, with the diagonal entries being the reciprocal of the variance entries of the pseudo ranges; and .omega.=The vector of misclosures between the theoretical observations based on the current satellite set and the last set of positions estimated, and the actual observations (pseudo ranges). The values of X, Y, Z at the first iteration are the constrain position, X.sub.cp. At later iterations, the position remains somewhat close to X.sub.cp, with the vertical component of the position being especially close to the vertical component of X.sub.cp

[0111] So:

.omega.=R.sub.obs-R.sup.1-Clk

=R.sub.obs-((X.sup.1-X).sup.2+(Y.sup.i-Y).sup.2+(Z.sup.i-Z).sup.2).sup.1/2- -Clk

[0112] R.sub.obs is based on the measured pseudoranges. At every observation time, the process is repeated until the length of the vector of corrections (.delta.X) to the position/clock parameter vector is small enough. In some cases, this may be accomplished after two iterations. At each epoch, the previous position and clock estimate is used to start the process, but any covariance information associated with that estimate is ignored. This means that at every epoch, at least 4 satellites are needed to estimate the 4 elements on the position/clock vector. If information related to the position/clock parameters were available, then this could be included in a modified least squares process according to the following:

.delta.X=(A.sup.TPA+P.sub.x).sup.-1A.sup.TP.omega.

[0113] where P.sub.X=Parameter weight matrix (4.times.4) based on knowledge of the parameters includes in the estimation process.

[0114] If certain elements of the parameter vector are well known, then this knowledge can be incorporated in the system by making the appropriate diagonal elements of the parameter weight P.sub.x large. If, for example, the clock estimate has a standard deviation of 1/2 m, then the P.sub.x entry P.sub.4,.sub.4 would be 4, and one less satellite would be required in the estimation process to generate a 4 parameter solution.

[0115] There are more complications if the knowledge of height is to be represented by this system. Height is in the geographic reference frame; therefore, the covariance information for height must be transformed from the geographic frame to the ECEF frame before it can be used by the system in the estimation process. The P.sub.X matrix is:

P.sub.x=C.sub.x.sup.-1=(J.sup.TC.sub.gJ).sup.-1

[0116] where:

[0117] C.sub.g=the covariance matrix of the position/clock in the geographic frame;

[0118] J=the matrix of derivatives of the transformation of position/clock from the geographic to the ECEF frame; and

[0119] C.sub.x=the covariance matrix of position/clock in the ECEF frame.

[0120] In the case of the track model application, J is not the rotation matrix used to transform a vector from the geographic to the ECEF frame, but instead a rotation matrix used to transform a vector from the planar section frame to the ECEF frame. The J matrix is used to set up the weight and covariance matrices of the constraint positions, and these matrices are pre-computed prior to the race. The J matrices are not required except for this, so in one embodiment they aren't retained for or recomputed during the race. The J matrix can be generated by representing three basis vectors, describing the planar section frame and a normal to it, in the ECEF frame. The positions of the vertices of each triangle are transformed from the geographic to the ECEF frame. The differences of these vectors are parallel to the planar section, and the cross product of two of these difference vectors provides a normal vector to the planar section. The cross product of the normal vector with either of the vector differences generates a vector parallel to the planar section and orthogonal to the other two vectors used in the cross product. Finally, normalizing these three vectors provides a set of orthonormal basis vectors representing the planar section frame in ECEF co-ordinates. So this set of vectors can be concatenated to generate J, the 3 by 3 rotation matrix used to rotate a vector from the planar section frame to the ECEF frame. Symbolically:

J=[B.sub.1.vertline.B.sub.2.vertline.B.sub.3]

[0121] where B.sub.1,B.sub.2, B.sub.3 are the basis vectors whose construction is defined in the previous paragraph.

[0122] The constraint position is given by the average of the three comer positions in the ECEF frame plus the constraint position relative to the planar section, transformed to the ECEF frame. Symbolically, this is:

Constraint position: X.sub.cp=((X.sub.1+X.sub.2 +X.sub.3)/3.0)+J *[0,0,h.sub.a].sup.T

[0123] where X.sub.1, X.sub.2, X.sub.3 are the ECEF positions of the planar section comers, and ha is the antenna height with respect to a level planar section.

[0124] Looking back at FIG. 7, the process of steps 250-260 will be explained in more detail. The system uses a Kalman filter with the track model. This process is also known as the RT20 process. The RT20 process generates estimates of the relative position between a reference GPS receiver and a roving GPS receiver as well as estimates of floating ambiguities related to the double difference carrier observations for those two receivers. In one embodiment, the RT20 process provides a best available solution when real-time kinematic (RTK) data is not available as well as providing an initial search space for the RTK carrier based process.

[0125] Carrier positioning is a process in which a relative position between two ground sites (a base station and a roving receiver) is computed based upon observed fractional phase differences and known whole cycle differences between the two receivers. The fractional and whole cycle differences together produce a synthetic observation which is equal (when converted to meters) to the geometrical difference in distance between the two receivers and the satellite they are both observing. Knowledge of the whole cycle portion of the synthetic observation cannot normally be determined directly from the observations, but must be determined indirectly from many observations over time during what is known as a whole cycle resolution process. The whole cycle difference is also known as a carrier ambiguity, and the resolution process is known as an ambiguity resolution process.

[0126] In one process, in order to resolve fixed integer ambiguities, an initial guess of the position difference is made and a series of sets of ambiguity candidates is selected such that each set will generate a position difference that is close to the one chosen in the initial guess. Each set is used to compute a position difference and an associated set of residuals. For each set, these residuals are accumulated and the accumulation compared to a theoretical accumulation and also to other accumulations in the series of candidate sets. If the correct set of ambiguities is in the series, then eventually its residual accumulation will be close to the theoretical accumulation and also smaller than any of the residual accumulations for the other sets. At this time the correct ambiguity set is known and can be used to generate relative positions with carrier type accuracy.

[0127] To summarize, there are two things that are done to resolve ambiguities:

[0128] (1): Guess at an initial position, and an associated search space whose size is based on the precision of the initial position estimate; and

[0129] (2): Use the guess and its precision to define a series of candidate sets of ambiguities and then accumulate computed residuals over time and eliminate sets whose residual accumulation exceeds some kind of threshold.

[0130] Typically a Kalman filter with both position and ambiguity states is used to define an initial guess for the search space. It is run in real-time as carrier and pseudo range observations are provided to it and some kind of executive routine monitors its position covariance to see when the search space can be defined and search can commence. By including position constraints with the GPS observation set, the precision of the initial position estimate used to define the search space can be reduced sooner and more, and this should significantly speed up the resolution process.

[0131] The Kalman filter used to estimate position and floating ambiguity states can be described as follows:

State: X=[x,y,z,N1,N2,...Nk]

[0132] State Initial Covariance: P=[big diagonal elements, 0 off diagonal elements]

[0133] The design matrix H defines the linear relationship between the double difference observation (satellites r,j and the two receivers) and the state elements. For satellite j and reference satellite r the phase relationship is:

H=[.DELTA.x.sup.r.sub.m/R.sup.r.sub.m-.DELTA.x.sup.j.sub.m/E.sup.j.sub.m, .DELTA.y.sup.r.sub.m/R.sup.r.sub.m-.DELTA.y.sup.j.sub.m, .DELTA.z.sup.T.sub.m/R.sup.r.sub.m/.DELTA.z.sup.j.sub.m/R.sup.j.sub.m, 0,0,...1,0,...0];

[0134] The pseudorange relationship is:

H=[.DELTA.x.sup.r.sub.m/R.sup.r.sub.m-.DELTA.x.sup.j.sub.m/E.sup.j.sub.m, .DELTA.y.sup.r.sub.m/R.sup.r.sub.m-.DELTA.y.sup.j.sub.m, .DELTA.z.sup.T.sub.m/R.sup.r.sub.m/.DELTA.z.sup.j.sub.m/R.sup.j.sub.m, 0,0,...0,...0]

[0135] The Kalman filter mechanization is as follows:

Gain: Kk=P.sub.k(-)H.sub.k.sup.T[H.sub.kP.sub.k(-)H.sub.k.sup.T+R.sub.k[.s- up.-1

Covariance Update: P.sub.k (+)=[I-KH.sub.k]P.sub.k(-)

State Update: X.sub.k(+)=X.sub.k(-)+K.sub.k[Z.sub.k-H.sub.kX.sub.k]

[0136] where R=Observation covariance matrix (scalar for phase and pseudo range observations) and is the same as the C.sub.x matrix (below) for the position update; and z=Observation (pseudo range or carrier measurement)

[0137] In the pseudo range and phase measurement implementation, the observations are decorrelated and the updates are done serially, one for each observation. With the position constraint information from the track model, the observation/state relationship is:

H=.vertline.1,0,0,0,...,0.vertline..vertline.1,0,0,0,...,0.vertline..vertl- ine.1,0,0,0,...,0.vertline.

[0138] H=[I,0] with I=3x3 and 0=3x(n-3), (n=number of states) and C.sub.x is the covariance matrix of the constraint position:

C.sub.x=J.sup.TC.sub.tJ

[0139] where C.sub.t=The covariance matrix of the position in the "triangle" (or planar section) frame; and J=The rotation matrix used to rotate a vector from the triangle frame to the ECEF frame.

[0140] In one embodiment, the covariance matrix of the position in the triangle frame can be defined as: 1 C t = 10000 , 0 , 0 0 , 10000 , 0 0 , 0 , 0.0001

[0141] that is, the parallel elements are more or less unknown, and the normal element is known to 10 cm at 1 sigma.

[0142] The results of the RT20 process is a vector which can be applied to the base station ECEF position (also transmitted to the local receiver with the differential observations) to give an ECEF position of the local receiver. The RT20 vector becomes more accurate as time goes on, so the local position accuracy also becomes more accurate.

[0143] The RT20 filter computes a vector between the base station and the local or rover receiver. In the absence of any track model the derived position will be Base Position plus RT20 vector. If the base station coordinates are in error relative to the relevant frame, then there will be a reported mismatch between the items in the true ECEF frame and the ECEF positions reported by the receiver. In order to account and remove this mismatch, the base station's transmitted position can be shifted by the amount of the mismatch and then the true and reported positions should be the same.

[0144] The mismatch is determined by a reconciliation process that is done prior to each race (or other event). In one embodiment, the data is reconciled by shifting the base station coordinates in the track model by an offset. The offset is determined by comparing the position of a stationary object in the track model with an accurately surveyed position for that object. In another embodiment, the reconciliation process is determined by comparing the track model normal constraint with the precise GPS position in the direction normal to the track model section applicable to the GPS position. This comparison is given by .omega.:

.omega.=R.sub.e.sup.p.sub.(Row 3)(Pos.sub.RT-Pos.sub.TM)

[0145] where R.sub.e.sup.P=the rotation matrix used to transform a vector from the ECEF to "triangle" frame;

[0146] POS.sub.RT=the unconstrained GPS ECEF position and POS.sub.TM=the track model constraint position in the ECEF frame;

[0147] Note that co is just the third element of the vector, because this is the part in the direction normal to that pertinent triangle.

[0148] The following estimation process can be used to determine the offsets required to reconcile the base station and track model reference frames. The offset between the base station frame and the track model frame is reflected in triangle frame coordinates as x.sup.t.sub.3=x.sup.eo n.sub.3. The observation equation that models this vector component is:

.omega.=x.sup.eo n.sub.3=R.sub.e.sup.p.sub.(Row 3)(Pos.sub.RT-Pos.sub.TM)

[0149] or

.omega.=x.sup.eo n.sub.3=U.sub.3.sup.TR.sub.p.sup.e(Pos.sub.RT-Pos.sub.TM)

[0150] where:

[0151] x.sup.e=Base station shift in the ECEF frame,

[0152] x.sup.t.sub.3=z component of base station shift in triangle frame

[0153] n.sub.3=normal vector to the triangle in the ECEF frame, R.sub.p.sup.e=the rotation matrix used to transform a vector in "triangle frame" coordinates to the ECEF frame; U.sub.3=unit vector normal to the triangle in the "triangle frame" U.sub.3=[0,0,1].sup.T; and o =dot product operator.

[0154] Note that n.sub.3 is simply the transpose of the last column of R.sub.p.sup.e. A least squares estimate can easily be generated from this .omega. via

X=(.SIGMA.(A.sup.TA)).sup.-1.SIGMA.(A.sup.T.omega.)

[0155] where:

A.sub.1=n.sub.3i=R.sub.p.sup.e.sub.1U.sub.3

[0156] The summation goes from i=1 to the number of RTK observations on the model. In order for this to work, a model with reasonable variation of normal vectors has to be used if all three components are to be observable.

[0157] The track model constraints improve the positioning accuracy significantly, up to a factor of 10 in many cases and sometimes more. In most cases, the improvement is in height, but in conditions of poor geometry the horizontal accuracy is also much better (sometimes more than 100 times better) in the constrained case. The horizontal accuracy also improves depending on the slope of the constraining section with respect to the local level because if there is a significant slope, then a component of the planar section's normal vector will be parallel to the local level plane.

[0158] In some embodiments, the track model is extended (extrapolated) outside the ribbon of the track so that bad geometry cases also have the use of a planar constraint.

[0159] In some embodiments, the track model constraints only work in the cases where there are at least four satellites. In other embodiments, the track model can be used when providing a degraded solution by accepting fewer observations as the required minimum number in either the least squares process or the RT20/Kalman filter.

[0160] FIG. 9 is a block diagram of a base station. FIG. 9 shows 900 MHz transmitter and receiver 340 connected to antenna 342 and computer 344. Computer 344 is connected to DSL modem 346, which is in communication with a DSL modem at production center 50. In general, each base station receives communications from all the cars with DAPS units that are in range of the base station and forwards the received information to production center 50. In addition, information from production center 50 is received by all of the base stations and retransmitted to all of the DAPS units within range of the particular base stations.

[0161] FIG. 10 is a flowchart describing the operation of a base station. In step 360, the system waits for its allotted time slot. While waiting, the system is listening for incoming messages from DAPS units. If an incoming message is received (step 362), that message is communicated to communication control computer 520 (see FIG. 13) at the production center 50 in step 364 and the method loops back to step 360. If an interrupt is received (step 362), then the system determines whether there is any data to send to the DAPS units (step 366). If there is no data to send, the method loops back to step 360. If there is data to send, the message is assembled in step 368. The system waits for its time slot in step 370 and transmits the message during its time slot in step 372. After step 372, the method loops back to step 360. The messages sent in step 372 are messages that originated from the production center 50.

[0162] FIG. 11 depicts an example of a camera location, including camera 392 with camera sensors 390. The camera sensors could include any or all of the following: optical shaft encoders, fiber optic gyros, inclinometers, and reading voltages from the lens (e.g. 2X Extender, focus, zoom). More information about camera sensors and cameras can be found in U.S. patent application Ser. No. 09/472,635, "Measuring Camera Attitude," filed on Dec. 27, 1999, incorporated herein by reference. Other camera sensors can also be used. Data from camera sensors 390 are sent to production center 50. In one embodiment, the camera sensor data for a given camera is transmitted to production center 50 via the camera's audio channel. The production center includes hardware to demodulate the audio channel. In some instances, the production center is in a truck at the event. The video from camera 392 is sent to camera control unit 394, which controls various video and optical parameters for camera 392. The output of camera control unit 394 is sent to VITC inserter 396 which adds a time code and unique camera identifier into the vertical blanking interval of the video from camera 392. The output of VITC inserter 396 is transmitted to production center 50. The present invention can be operated using one or more instrumented cameras. In one embodiment, the present invention is operated with six instrumented cameras. Each of the six cameras has its own CCU and its own VITC inserter. Each camera=s VITC inserter is synchronized with master VITC 506 (see FIG. 13). In alternative embodiments, the present invention can be used with fixed, non-instrumented cameras. In another alternative, the present invention can be used with non- instrumented cameras that are not fixed, in combination with image recognition.

[0163] FIG. 12 shows a block diagram of the electronics for using the camera attitude sensors. FIG. 22 shows pan encoder 400, tilt encoder 402, gyro 404, gyro 406, inclinometer 408 and inclinometer 410. The output of pan encoder 400 and tilt encoder 402 are sent to FPGA 412. Pan encoder 400 and tilt encoder 402, in one embodiment, are optical encoders that output a signal which is measured as a number of counts (or pulses) that indicate the rotation of a shaft. The output signal is a quadrature signal indicating rate and direction. FPGA 412 decodes the signal from the optical encoders to output a count. FPGA 412 also controls analog to digital converter 414 and provides interface logic for processor 416. In regard to the analog to digital converter 414, FPGA 412 provides interface logic and a buffer, including a register to store a value for each sensor connected to analog to digital converter 414.

[0164] Gyro 404 is connected to interface board 420, which is connected to analog to digital converter 414. Interface board 420 comprises electronics for receiving a signal from gyro 404 and presenting the information to analog to digital converter 414. The electronics of board 420 includes a differential amplifier and other electronics which can reject common mode noise and amplify the signal from the gyro. The output of gyro 406 is connected to interface board 422. Interface board 422 operates in the same manner as interface board 420 and is also connected to analog to digital converter 414.

[0165] Signal 424 represents the electrical output of the zoom lens potentiometer of the camera and is connected to analog to digital converter 414. Signal 426 represents the electrical output of the 2X extender of the camera and is connected to analog to digital converter 414. Signal 428 represents the connection to the lens of the camera, provides the value of the focus of the camera and is connected to analog to digital converter 414.

[0166] The output of inclinometer 408 is connected to interface electronics 430. The output of inclinometer 410 is connected to interface electronics 432. The outputs of interface board 430 and interface board 432 are both connected to analog to digital converter 414. Analog to digital converter 414 converts the input analog signals to digital signals, and sends the output digital signals to FPGA 412. FPGA 412 includes a register for each of the sensors.

[0167] Processor 416 is in communication with data memory 436 for storing data and program memory 438 for storing program code. In one alternative, memory 438 is a flash memory and memory 436 is a static RAM. In one embodiment, processor 416 is an 8032 processor from Intel. Processor 416 also receives an output signal from sync decoder 440. Sync decoder 440 receives a video signal 450 from the camera and generates a sync signal so that the data from the sensors can be synchronized to the video. In one embodiment, the video is transmitted at 30 frames per second. Other video rates can also be used. Processor 416 assembles data from each of the sensors into a packet and sends the data to modulator 444. Processor 416 assembles the data using the sync signal so that data is collected and sent in synchronization with the video from the camera. For example, data can be sent for every field, every video frame, every other video frame, every third video frame, etc.

[0168] Modulator 444 receives the packet of data from processor 416 and encodes data for transmission on an audio frequency signal. The output of modulator 444 is sent to audio driver 446 and coax driver 448. Most broadcast cameras have a microphone input channel. The output of audio driver 446 is sent to the microphone input channel for the camera. The camera then combines the audio input channel with the video and sends a combined signal to the production equipment. If the audio signal is needed on a coax cable, then that signal is received from coax driver 248. In one embodiment, there can also be an RS232 or RS422 output directly from processor 216. More information about the system of FIG. 12 can be found in U.S. patent application Ser. No. 09/472,635, "Measuring Camera Attitude," filed on Dec. 27, 1999, incorporated herein by reference.

[0169] FIG. 13 is a block diagram of production center 50. Audio demodulator 50 receives the audio signals from each of the camera locations and demodulates the signals to remove the camera sensor data. The data is sent to gather computer 502, which is a Pentium based personal computer. Gather computer 502 acts as a central data concentrator, logger, synchronizer and forwarder. The computer receives camera data from the instrumented cameras and time code data from VITC 506. Gather computer 502 synchronizes and consolidates the time code and camera sensor data streams and forwards the data to race computer 504 via a serial line. Gather computer 502 is used to stamp VITC on the camera sensor data stream.

[0170] Race computer 504 receives program video with time code (via VITC 506), camera data from gatherer 502, vehicle data from communication control computer 520 and the camera identification information from the program video. Race computer 504 determines what camera is being used to provide the broadcast video (based on the camera identification inserted by VITC 396), what camera sensor data to use, what vehicles are selected to be highlighted and what data needs to be depicted in the video. It uses this information to send render computer 508 a description of the graphics to draw. Note that race computer 504, render computer 508, Tsync computer 534, communication control 520 and Booth UI computer 532 all communicate via an Ethernet.

[0171] Render computer 508 uses the information from race computer 504 to create an appropriate key and fill signals which are sent to keyer 510. Keyer 510 uses the key signal from render computer 508 to blend the graphics defined by the fill signal with the program video. The program video is provided to keyer 570 from video delay 512, which receives the program video from VITC 506. In one embodiment, all the cameras from an event send their video to a video production truck. The video production truck will include a switcher for choosing a video signal for broadcast. That chosen signal will be sent to VITC 506.

[0172] In one embodiment, gather computer 502, Tsync computer 534, communication control computer 520 and booth UI computer 532 are personal computers. Race computer 504 and render computer 508 are 02 computers from Silicon Graphics.

[0173] Communication control computer 520 is connected to DSL modems 522, 524, 526 and 528. Each of these DSL modems are in communication with a DSL modem at a base station. In one embodiment, there is one DSL modem connected to communication control computer 520 for each base station. Communication control computer 520 controls the flow of information between the DAPS units, the base stations and the production center 50. Communication control computer 520 communicates with the base stations via the DSL modems (in one embodiment over the same Ethernet as described above). Communication control computer 520 also receives differential GPS data from the GPS reference station 20 and sends that data to the base stations for transmissions to the DAPS units.

[0174] Booth UI computer 532 has a touch screen which displays all the available enhancements that the system can perform. An operator can touch the screen to choose a particular enhancement. This selection of enhancements is sent to communication control computer 520 and race computer 504.

[0175] Race computer 504 presents feedback to the booth UI, computer 532 which is transformed into a visual representation of confidence-of-measure and availability This is on a per-DAPS basis, and works for other DAPS equipped targets such as roving announcers. Race computer 504 also disables effects/enhancements if certain conditions (such as being in RT20 or better or having 2.5 meter standard. deviation or smaller) are not met. Race computer 504 smoothes small gaps in data via interpolation. The race computer also stores data (camera and DAPS) for use in replay (when used in concert with a tape striped with VITC 506). Render computer 508 interpolates the 2d coordinates of the objects in video between frames (i.e. field interpolation) since race computer 504 only computes positions per-frame.

[0176] Tsync computer 534 is used to synchronize video time to GPS time. Tsync 534 is connected to a Trimble Pallisades GPS receiver 536, VITC reader 535 and VITC 506. FIG. 14 is a flowchart describing the operation of Tsync 534. GPS receiver 536 outputs the GPS time to Tsync 534 via an RS 422 line once per second. This message contains time, date and status. The receiver also outputs a 1 Hz pulse. At (within 1 us of) the top of every second, the pulse signals the time. Some milliseconds later, the message is output. Tsync computer 534 receives these events and records the PC system time when the events happen in step 540. Tsync computer 534 has a vertical sync detector installed on one of the ISA slots. This board generates an interrupt signal once at the beginning of every odd field (step 542). When this interrupt occurs, the Tsync computer 534 PC records the PC time. Tsync 534 is also reading VITC data from the VITC reader 535 (step 544). When the last character of a VITC packet is received, the VITC time (video time) is recorded. Tsync computer 534 interpolates between GPS time values, to determine a GPS time at the start of a frame. This determined GPS time is matched to the VITC value for that frame in step 546. In step 548, a message is sent from Tsync 534 to communication control 520 indicating a GPS time at the beginning of a frame and the VITC time at the beginning of the same frame. This relationship is used by the system to match GPS data with the appropriate video frame (see step 564 of FIG. 15, below).

[0177] FIG. 15 is a flow chart describing the overall process performed at production center 50. In step 550, real loop data is received by communication control computer 520. FIG. 16 describes a system for providing real loop data.

[0178] FIG. 16 shows receivers 602. Only three receivers are depicted in the figure, however, it is contemplated that more or less than three receivers can be used. FIG. 16 also shows loops 604 connected to the receivers. Each loop is connected to one receiver. In one alternative, one receiver may service multiple loops. FIG. 16 shows the loop with a rectangular-like shape. However, the current invention contemplates other shapes being used. The receivers are connected to data gatherer 606 via a network (e.g. Ethernet). Data gatherer 606 is connected to computer 608. FIG. 16 also shows transmitter 610 which transmits an RF signal to loop 604. Instead of an RF signal, an inductive coupling can also be used.

[0179] In the embodiment for use with an auto race, each car would have a transmitter 610 (or transponder) mounted on the car that uniquely identifies the car by transmitting a unique code or frequency. Loops 604 are located below the surface of the race track, road or other surface. As the transmitter passes over a loop, the loop receives a signal from the transmitter. Based on the received signal, receiver 602 identifies the transmitter and the time when the signal was received and stopped being received. Receiver 602 sends this information to data gatherer 606. Data gatherer 606 compiles all the information from all the different receivers 602 and sends the compiled information to computer 608 for final analysis and storage. Data can then be sent from computer 608 to communication control computer 520. In one embodiment, the functions of data gatherer 606 and computer 608 can be performed by a single device. In another embodiment, data gatherer 606 may perform some of the calculations (e.g. speed and position) and then send a smaller data stream to computer 608.

[0180] In one embodiment, loop 604 is an insulated electrical wire. Loops other than wires can be used. In one embodiment, loop 604 acts as an antenna receiving RF signals. In another embodiment, loop 604 is used as a component of an inductive coupling system. Loops are typically placed below the surface of the road or track. Most loops will detect the presence of a transmitter crossing over the middle of the loop with sub-millisecond accuracy and a resolution of better than one ten-thousandths of a second. In one embodiment, the loop and transmitter should be mounted such that they are within twenty four inches of each other when the transmitter is passing over the loop. One implementation includes only using one loop 604, and locating that loop at the Finish Line of the race track.

[0181] Receiver 602 processes the raw signals picked up by loop 604. In one embodiment, it is the job of receiver 602 to convert the raw signals into digital information that can be transmitted to data gatherer 606. Each receiver stores a transmitter identification number, the crossing time and other data for each detection of a signal. Under normal operation, the data from the receiver is uploaded and processed as information is received from the loop

[0182] Looking back at FIG. 15, step 550 includes receiving loop data from computer 608. After receiving the real loop data in step 550, the system receives and processes data from the DAPS in step 552. That is, communication control 520 receives data from the base stations that was originally transmitted from the DAPS units. In step 554, camera sensor data is received via audio demodulator 500 and gatherer computer 502. In step 556, program video is received. In step 558, race computer 504 and/or communication control 520 will access the selections of what data to display, which were inputted via booth UI computer 532. In step 560, the selection of objects to highlight will be accessed by communication control computer 520. In step 562, race computer will determine which camera sensor data to use. That is, each of the video signals had a unique identifier added to the vertical blanking interval (VBI). Race computer 504 will read the VBI of the program video and determine which camera was selected for broadcast. Then, the camera sensor data received via gatherer 502 for the chosen camera will be accessed in step 562. In step 564, the appropriate GPS position data will be accessed by race computer 504. In one embodiment, communications control computer 520 sends all of the data to race computer 504 and race computer 504 picks out the data that it needs. In step 566, the video is enhanced. In step 568, the enhanced video is transmitted for broadcast or storage on a tape or other medium. The steps of FIG. 15 do not necessarily need to be performed in the order depicted in the drawing.

[0183] FIG. 17 is a flowchart describing the method of receiving and processing data from the DAPS units (step 552 of FIG. 15). In step 570, a message is received from a DAPS unit, via a base station, at communication control computer 520. In step 572, communication control computer 520 accesses the data in the message and stores the data in logs.. In step 574, any data that has already been received by communication control 520 will be discarded. In step 576, data that has not been discarded is stored in a log. In step 578, the data is processed to determine certain statistics. In step 580, the determined statistics are stored. In step 582, the data and/or statistics are transmitted to the appropriate clients (e.g. race computer 504).

[0184] FIG. 18 is a flowchart describing the method of processing data to determine statistics (see step 578 of FIG. 17). In step 632, RPM data is filtered. In one embodiment, any values above 10,000 are discarded and the remaining values are subjected to a simple IIR filter (filteredrpm=1/2 filteredrpm +1/2 rpm). In step 634, the velocity of each automobile is determined based on two position measurements and times (V=distance divided by time). In step 636, acceleration is determined for each of the DAPS units. In step 638, a lap count and lap fraction is determined for each DAPS unit. Each lap around the track is counted and each fraction of a lap is counted (e.g. the lap fraction). In step 640, the race position is determined. That is, whether the driver is in first place, second place, third place, etc. In step 642, it is determined how far (in terms of time) each car is behind the leader car (the first place car). In step 644, virtual loop information is determined. In step 646, the system predicts when one or more of the cars will run out of fuel. In step 648, missing sensor data can be estimated using the GPS information. The method of FIG. 18 is primarily performed by communication control computer 520. The steps of FIG. 18 can be performed in a different order than as depicted in the drawing.

[0185] FIG. 19 is a flowchart describing the method of determining the lap count and lap fraction (step 638 of FIG. 18). To aid in determining lap fractions, a racetrack (or other track or surface) is broken up into a number of sections, with each section having borders. For example, FIG. 20 shows a portion of racetrack 650 broken up into a number of sections 652, 654 and 656. In FIG. 20, the sections are rectangular, however other shapes can be used. For example, at curved portions of a track, a section can be trapezoidal in shape. Section 652 has beginning border 658 and end border 660. Section 654 has beginning border 660 and end border 662. Section 656 has beginning border 662 and end border 664.

[0186] FIG. 19 describes a process for determining lap numbers and lap fractions. The process of FIG. 19 is performed for each DAPS unit. In step 670, it is determined whether there is GPS determined position data currently available for the DAPS unit under consideration. If so, the method loops to 672 and accesses the GPS determined position of the car under consideration. In step 674, the system determines which section of the track the car is on based on the position from step 672. In step 676, the system determines what lap the car is on based on what section the car is in and the previous lap stored for the car. Prior to the race, the beginning border of each section is pre-assigned with a lap fraction. In one embodiment, the track is broken into one hundred equally spaced sections so that the first section is at lap fraction 0, the second section is at lap fraction .01, the third section is lap fraction .02, etc. The system will store the previous lap fraction and lap number. By knowing the new lap fraction, the system can determine whether the car has crossed the finish line, thus, starting a new lap. In step 678, the system accesses the pre-stored lap fractions for the start border of the section the car is currently in and the next section. While the car may be exactly at one of the borders, it is likely to be between the borders. Therefore, in step 680, the system interpolates the lap fraction based on the two borders.

[0187] If it is determined in step 670 that there is not a current GPS determined position available for the car under consideration, the method loops to step 686. The latest real loop data for the car under consideration is accessed in step 686. The system also accesses the latest real loop data for the car directly ahead of the current car under consideration. In step 690, the system determines the difference in time between the loop data for the two cars. In step 692, the system accesses the previously recorded or computed speed of the car directly ahead of the car under consideration at the time of crossing the loop. This speed and time may need to be interpolated. In step 694, the distance between the two cars at the time of crossing the loop is determined based on speeds and time. This distance is assumed to be the distance between the two cars during the entire lap as long as no GPS data is available. Thus, in step 696, the system determines the current position of the car under consideration by subtracting the distance computed in 694 from the current position of the car directly ahead of it. After step 696, the method loops to step 694.

[0188] Once knowing the lap fractions for all the cars, the system can determine the race position (step 640 of FIG. 18) by ranking all the DAPS units based on lap and lap fraction.

[0189] FIG. 21 is a flowchart for describing the process for determining the time behind the leader (step 642 of FIG. 18). In step 700, the system stores the lap fractions and associated times at each lap fraction for the leader car at one hundred positions along of the track. More or less than one hundred positions can also be used. Steps 702-712 are then performed for each car for which the time behind the leader is to be computed. In step 702, the system accesses the lap and lap fraction for the car under consideration. In step 704, the system determines whether there is position data for the leader car at the exact same lap and lap fraction. If so, the times of the two cars are compared in step 706 to determine the time behind the leader. If not, then the lap fraction of the leader car just before the lap fraction of the car under consideration is accessed in step 708 and the lap fraction just after the lap fraction for the car under consideration is accessed in step 710. In step 712, the system interpolates the times for the two lap fractions of step 708 and 710 to determine the time the leader was at the same position as the current car under consideration. The time of the leader car and the time of the current car under consideration are compared to determine the difference, which is the time behind the leader.

[0190] FIG. 22 is a flowchart describing the method of determining virtual loop information (see step 644 of FIG. 18). Actual physical loops have been described above. In one embodiment, the system uses virtual loops. Rather (or in addition to) installing a real loop wire in the track, the system virtually creates loops and measures information about cars passing over these virtual loops using the GPS position data. FIG. 20 was used to explain how the track was divided up into sections. In one embodiment, the beginning of each section can be used as a virtual loop. In step 720 of FIG. 22, the system accesses the current position of each DAPS unit. In step 722, the system accesses the previous position of each car. In step 724 the system determines whether any of the cars have crossed the beginning of the section being used as a virtual loop. In one embodiment, there can be one virtual loop. In another embodiment, more than one virtual loop can be used in which case, step 724 will determine whether any of the virtual loops have been crossed. In addition to sections on the track, the pit area can also be divided into sections and a virtual loop can be created at the beginning or end of the pit area. Thus, the system can determine whether any cars entered the pit area or left the pit area, and how long the cars were in the pit area based on entrance and exit times.

[0191] For all cars that have crossed the virtual loop between the previous and current position, the system interpolates to determine the exact time the loop was crossed (step 726). In step 728, the system determines the speed at the time of crossing the loop by considering at the current position and the previous position. In step 730, any split times are determined. That is, in one embodiment, the system may determine split times between virtual loops. In step 732, the speed at the time of crossing the virtual loop, the crossing time and the split times are all stored. In step 734, any of the information stored in step 732 can be reported to race computer 504, or any other client.

[0192] FIG. 23 is a flowchart describing the process for predicting when a particular car will run out of fuel. The process of FIG. 23 can be performed for each car. In step 820, the system accesses the current throttle position for the car. In step 822, the system accesses the current speed for the car. The speed can be determined by looking at the current and previous positions (and associated times). In step 824, the system determines the proximity of the car under consideration to nearby cars. In step 826, the system determines which of the nearby cars cause a drafting effect for the car under consideration. In step 828, the system determines a current rate of fuel consumption as a function of speed, throttle position and distance to nearby cars that are causing drafting. In step 830, the system updates the fuel volume for the car based on the new consumption rate determined in step 828 and the time from the last update. In one embodiment, booth UI computer 532 is used by an operator to indicate when a car fills its gas tank. The volume of the tank is known in advance. The level of the fuel is then updated each iteration of step 830, with the process of FIG. 23 performed each time a GPS position is received. In step 832, the system makes a prediction of when the fuel tank will be empty based on the current consumption rate and the current volume. That is, current consumption rate multiplied by time will equal the current volume at a certain time, this time is calculated and reported.

[0193] Step 648 of FIG. 18 includes estimating missing sensor data using GPS information. That is, there may be situations when the sensors on the DAPS units are not able to sense or report data. In those instances, the system uses GPS derived information to estimate the missing sensor data. For example, the following equations explain how to estimate throttle position and brake position. 2 v x n = ( ( n - n - 1 ) cos ( L n ) 60 6072 ( t n - t n - 1 ) ) v y n = ( ( L n - L n - 1 ) 60 6072 ( t n - t n - 1 ) ) v n = v x n 2 + v y n 2 RPM n = ( v n 60 R g 2 t ) ( 1 + a L n s ) a L n = ( ( v n - v n - 1 ) 32 ( t n - t n - 1 ) ) g H E = k ( RPM - RPM MAX ) 2 + H E MAX F d = ( 1 2 C d A v 2 32 ) F R = r r V F a = a L M F w = F a + F R + F d H w = ( F w r t 2 RPM 60 R g 550 ) T = ( 100 H w H E ) B = 100 ( F w M )

[0194] where:

[0195] M=car weight (e.g. 3600 lb)

[0196] L.sub.n=latitude at time n

[0197] .lambda..sub.n=longitude at time n

[0198] V.sub.n=velocity at time n

[0199] v.sub.x.sub..sub.n=x component of velocity

[0200] v.sub.y.sub..sub.n=y component of velocity

[0201] R.sub.g=gear ratio

[0202] RPM=revolutions per minute

[0203] r.sub.t=tire radius

[0204] a.sub.l.sub..sub.n=longitudinal acceleration at time n

[0205] .alpha..sub.s=slip factor of tire

[0206] H.sub..SIGMA.=horsepower of engine at full throttle as a function of RPM

[0207] RPM.sub.max=RPM where horsepower is maximum

[0208] H.sub.E.sub..sub.MAX=peak engine horsepower

[0209] K=engine horsepower constant

[0210] F.sub.d=aerodynamic drag

[0211] A=frontal area

[0212] C.sub.d=drag coefficient

[0213] p=air density =.0801

[0214] F=rolling resistance drag

[0215] r.sub.r=rolling resistance constraint

[0216] F.sub.a=force from acceleration

[0217] F.sub.w=force applied to wheels

[0218] H.sub.w=horsepower applied to wheel

[0219] T=throttle position

[0220] B=brake position

[0221] Step 566 of FIG. 15 includes enhancing the video. FIG. 24 is a flowchart describing more details of the process of enhancing the video. Before the process of FIG. 24 is performed, race computer knows which cars will be highlighted and what data (including statistics determined above) needs to be added to the video. In step 860, the positions in the video of the image of each of the cars to be highlighted is determined. The system already knows the three dimensional location of the cars in real space based on the GPS technology described above. These three dimensional locations are transformed to two- dimensional positions in the video in step 860. Enhancing video and transforming three-dimensional locations to two dimensional positions is known in the art and described in U.S. Pat. Nos. 5,912,700; 6,252,632; 5,917,553; 6,229,550; and U.S. patent application Ser. Nos. 09/472,635, "Measuring Camera Attitude" filed on Dec. 27, 1999 and 09/425,992, "Telestrator System" filed on Oct. 21,1999, all of the above listed patents and applications are incorporated herein by reference. In step 862, the system creates highlights at or near the positions determined in step 860. The following are examples of highlights that can be created: a cloud, circle, oval or other shape can be placed over a car; an ellipsoid can be placed over the car; an arrow or line pointing to the car can be added; an identification (such as a image of a driver, car number, sponsor, team name, etc.) can be added to the video at or near the car; or any other type of highlight can be used. In one embodiment, a frame or field of the video is created with the highlight at the appropriate position. In step 864, data can be added to the created field or frame of video. In one embodiment the data is added as text. In another embodiment, the data is added as graphics. The data could include driver name, car number, throttle position, RPM, brake position, speed, time behind the leader, current position in the race (e.g. first place, second place, etc.), split time, an indication of whether the car is in the pit area, time in pit area, speed, etc. In one embodiment, the data from step 864 is connected to the highlight from 862 by a line (step 866). In other embodiments the data is not connected to the highlight. In step 868, the data and/or highlights are blended with the video of the race using keyer 510 or another video modification unit.

[0222] One embodiment described above includes using an ellipsoid as a highlight of a car or other object. In one embodiment, the orientation of the ellipsoid (or other shape) changes as the attitude of the image of the car changes in the video. FIG. 25 is a flowchart describing the process of providing an ellipsoid (or other shape) whose orientation changes as the attitude of the car (or other object) changes. In step 880, the system determines the attitude of the car. This is determined by comparing two successive positions of the car and assuming the attitude to be the direction from the first position to the second position. In step 882, an ellipsoid is created. The major axis and the minor axis of the ellipsoid are the length and width of the car. In step 884, the system finds all points on the ellipsoid that have a tangent plane that includes the nodal point of the camera providing the video of the race. The tangent plane of a point is a plane that touches that particular point under consideration and no other point on the ellipsoid. It turns out that all the points identified in step 884 will be in a plane. In step 886, the system determines that plane. In step 888, the plane determined in step 886 is intersected with the ellipsoid. The intersection of the plane and the ellipsoid is drawn in step 890. That intersection drawn in step 890 is the highlight added to the video at the position of the image of the car in the process of FIG. 24. As the attitude of the image of the car wheel changes, the shape and orientation of the ellipsoid will change. In one embodiment, the image drawn in step 890 is a solid. In another embodiment, the image is an outline with the center of the shape being clear. The equations below include math used to implement the process of FIG. 25.

[0223] A standard ellipse centered at the origin can be described by the equation, 3 x 2 a 2 + y 2 b 2 + z 2 c 2 = 1 ( Equation 1 )

[0224] or with the matrix equation, 4 [ x y z 1 ] [ 1 a 2 0 0 0 0 1 b 2 0 0 0 0 1 c 2 0 0 0 0 - 1 ] [ x y z 1 ] = 0 ( Equation 2 )

[0225] Let S be the 4 by 4 matrix, 5 S = [ 1 a 2 0 0 0 0 1 b 2 0 0 0 0 1 c 2 0 0 0 0 - 1 ] ( Equation 3 )

[0226] Then points on the standard ellipsoid can be given by the equation, 6 [ x y z 1 ] S [ x y z 1 ] = 1. ( Equation 4 )

[0227] The general ellipsoid of a given orientation and location can be represented by rotating and translating the standard ellipsoid. Let points on the general ellipsoid be given by (x1,y1,z1). Then the (x1,y1,z1) points can be described by the equation,

[x1 y1 z1 1]=[x y z 1]R.multidot.T, (Equation 5)

[0228] where R is a four by four rotation matrix, and T is a four by four translation matrix. Let

Mew=R.multidot.T, (Equation 6)

[0229] and

Mwe=Mew.sup.-1. (Equation 7)

[0230] Then we have the equation,

]x y z 1]=[x1 y1 z1 1]Mwe. (Equation 8)

[0231] Then points on the general ellipsoid can be described by the equation, 7 [ x1 y1 z1 1 ] Mwe S Mwe T [ x1 y1 z1 1 ] = 0 , ( Equation 9 )

[0232] where Mwe.sup.T is the transpose of the matrix, Mwe.

[0233] Let 8 Mwe S Mwe T = [ c11 c12 c13 c14 c21 c22 c23 c24 c31 c32 c33 c34 c41 c42 c43 c44 ] , ( Equation 10 )

[0234] and let A=c11, B=c22, C=c33, D=c12+c21, E=c23+c32, F=c13+c31, G=c14+c41, H=c24+c42, I=c34+c43, J=c44. Let the nodal point of the camera model be (nx,ny,nz). Let A3=Fnz+2Anx+Dny+G, B3=Enz+Dnx+2Bny+H, C3=2Cnz+Fnx+Eny+I, and D3=lnz+Gnx+Hny+2J.

[0235] Then it can be shown that the intersection of the general ellipsoid and plane is described by the equation,

A3x1+B3y1+C3z1+D3=0. (Equation 11)

[0236] The set of points on the ellipsoid whose tangent plane contains the nodal point all lie in a single plane. That plane is given in Equation 11.

[0237] In one embodiment of the system described above, the system can show phantom cars in a video that depicts actual cars racing. For example, during time trials, while a particular car is driving around the track, a phantom car showing the position of the leading car can be added to the video. Alternatively, while a driver of interest is being shown on television during a race, the position of another car during another running of the race (or other situation) can be depicted in the image. In one embodiment, the image of the phantom car is an image of a car added to each field of the video. In another embodiment, the phantom image will change orientation as appropriate for the particular segment of track. In one embodiment, the system determines the orientation of the track in the current video field or frame and creates a new car image with an orientation matching that of the track. In another embodiment, the system pre-renders images of a car for different orientations of the track or car.

[0238] FIG. 26 is a flowchart describing a process for providing virtual cars using pre-rendered images. In step 900, pre-rendered images of a car in different orientations are created and stored. Step 900 is most likely done prior to the start of a race; however, it can be done later. Steps 902-916 are likely to be done during or after the race (or other event). At step 902, the system determines the elapsed time for the position information for the actual car being shown in the video. It is assumed that the actual car is in the video and the system is attempting to add a virtual car to the video. The virtual car represents another car that will be referred to as the reference car. The latest position information known for the actual car has a time associated with it. By subtracting the time associated with the car position from the time of the start of the race, an elapsed time can be determined for the actual car. In step 904, the system finds a three dimensional location of the reference car associated with the time determined in step 902. For example, if the elapsed time during a time trial was thirty seconds, the system will look for the three dimensional location of the reference car thirty seconds into the time trial for the reference car. In step 906, that three-dimensional location of the reference car is transformed into a two dimensional position in the video as described above. In step 908, the system determines the three dimensional location data of the reference car just prior to the location data determined in step 904. By knowing two different locations of the car, the orientation of the reference car can be determined. The system then looks for the pre-rendered image having an orientation closest to the orientation of the reference car. Alternatively, the system can look for the closest pair of pre-rendered images and interpolate between the two of them in step 914. In step 916, the new interpolated images (or one of the pre-rendered images without interpolating) is blended with the video. In an alternative embodiment, by identifying the three dimensional location of the virtual car in step 904, the system can determine which section of the track the car was in. Each section of the track can be associated with one of the pre-rendered images and that image can be used to blend with the video in step 916.

[0239] One embodiment of the present invention also includes a crash camera, which is a camera that automatically detects that a crash has occurred and automatically points toward the crash. The crash camera enables the television viewer to instantly view a crash scene at a race. FIG. 27 shows one embodiment of the components of the camera location for the crash camera. Camera 940 is a standard broadcast television camera known in the art. Connected to camera 940 are camera sensors and servo motors 942. The camera sensors are similar to the camera sensors described above. Servo motors are motors that move the camera about the pan and tilt axes. The servo motors are controlled by, and in communication with, processor 948. Processor 948 is in communication with communication control computer 520 and the television production equipment that chooses a video source for broadcast. When a crash is detected, processor 548 sends a signal to the production equipment to select the video from camera 940 for broadcast. Processor 948 will receive data about various DAPS units from communication control computer 520. Similar to the camera locations described above, camera 940 is in communication with camera control unit 944, which is connected to VITC 946.

[0240] FIG. 28 is a flowchart describing the process performed by processor 948. In one embodiment, processor 948 is a personal computer. In step 960, processor 948 receives the current positions of all the cars (or other objects) from communication control computer 520. In step 962, processor 948 determines whether any of the car positions, as compared to previous positions, indicate a change in speed or direction that meets a predefined threshold. Any car that has a sufficient change of direction in a small amount of time or sufficient decrease in speed in a small amount of time is considered to be crashing. If a crash is detected, then the processor 948 sends signals to servo motors 942 to point camera 940 toward the position of the crashing car and a signal is sent from processor 948 to the production equipment to select the video of camera 940 for broadcast. If a crash wasn't detected (see step 964), the method loops back to step 960 and waits for the next set of positions to arrive.

[0241] In some embodiments, prior to operating the system for enhancing video described above, the system should be registered. Registration, a technology known by those skilled in the art, is the process of defining how to interpret data from a sensor and/or to ascertain data variables for operation of the system. The camera sensors described above output data, for example, related to position and orientation. Since position and orientation are relative, the system needs a reference from which to determine position or orientation. Thus, in order to be able to use camera sensor data, the system needs to know how to interpret the data to make use of the information. Generally, registration includes pointing the instrumented cameras at known locations and solving for unknown variables used in transformation matrices and other mathematics. More detail of how to register the system can be found in U. S. Pat. Nos. 5,862,517 and 6,229,550, both of which are incorporated herein by reference.

[0242] The foregoing detailed description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto.

* * * * *