US 8,725,396 B2Grant
System for providing traffic data and driving efficiency data
Issue Date:2014-05-13
•12 Claims
•10 Drawing Sheets
Abstract
Current and predicted traffic information is provided from incident data, traffic flow data, and media related to traffic received from multiple sources. The crowd sourced data may be provided passively by applications on remote mobile devices or actively by users operating the remote mobile devices. An application on a mobile device may receive the multiple data types, aggregate and validate the data, and provides traffic information for a user. The traffic information may relate to the current position and route of the user or a future route. The present technology may also provide driving efficiency information such as fuel consumption data, carbon footprint data, and a driving rating for a user associated with a vehicle.
Metadata
Assignee
- Pelmorex Canada Inc.
Inventors
- André Guéziec
- Romain Faure
- Damien Poulain
Application Information
Application Number:US 13/475,502
Filing Date:2012-05-18
Priority Date:2011-05-18
Art Unit:3668
Classifications
IPC:
G06F19/00G08G1/00G08G1/0968
Field of Search:
G08G 1/0141G08G 1/0968G08G 1/00G01C 21/3415G01C 21/3492G01C 21/3691G06F 19/00
Patent Drawings (10 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the priority benefit of U.S. Provisional Application Ser. No. 61/487,425, titled “Developing and Supporting High Usage Traffic Information Mobile Apps,” filed May 18, 2011, the disclosure of which is incorporated herein by reference.
Background of the Invention
[0002] As mobile devices become more popular among users, developers provide more applications. One type of application for mobile devices provides traffic information for roadways. Typically, the traffic information is provided on a display as a color coded roadway. For example, if traffic is flowing as normal the roadway may be highlighted in green. If traffic is disrupted, traffic may be highlighted in red.
[0003] Traffic information for existing mobile device applications is often unreliable. The traffic data may only be from a single source and may often be unavailable. As a result, the traffic information may be unreliable and frustrating for users.
[0004] There is a need in the art for an improved traffic data processing system for mobile devices.
Summary of the Claimed Invention
[0005] The present technology provides current and predicted traffic information from incident data, traffic flow data, and media related to traffic received from multiple sources. The crowd sourced data may be provided passively by applications on remote mobile devices or actively by users operating the remote mobile devices. An application on a mobile device may receive the multiple data types, aggregate and validate the data, and provides traffic information for a user. The traffic information may relate to the current position and route of the user or a future route. The present technology may also provide driving efficiency information such as fuel consumption data, carbon footprint data, and a driving rating for a user associated with a vehicle.
[0006] In an embodiment, a method for processing traffic data, beings with receiving traffic data by a mobile device. The traffic data may originate from multiple sources. Traffic information may then be provided through an interface of the mobile device. The mobile device may also provide driving efficiency information through the interface. The driving efficiency information may include fuel consumption, carbon footprint data, and a driver rating.
Brief Description of the Drawings
[0007] FIG. 1 is a block diagram of an exemplary system for analyzing traffic data.
[0008] FIG. 2 is a block diagram of an exemplary device application.
[0009] FIG. 3 is an exemplary method for processing traffic data.
[0010] FIG. 4 is an exemplary method for providing traffic information.
[0011] FIG. 5 is an exemplary method for providing fuel consumption data.
[0012] FIG. 6 is an exemplary method for providing driver rating data.
[0013] FIG. 7 is another exemplary method for providing driver rating data.
[0014] FIG. 8 is a block diagram of an exemplary mobile device.
[0015] FIG. 9 is a block diagram of an exemplary computing device.
Detailed Description
[0016] The present technology provides current and predicted traffic information from multiple types of traffic data received from multiple sources. Traffic data such as incident data, traffic flow data, and media related to traffic may be received by a mobile device. The traffic data may originate from public entities, private companies, and crowd sourcing. The crowd sourced data may be provided passively by applications on remote mobile devices or actively by users operating the remote mobile devices. An application on a mobile device receives the multiple data types, aggregates the data, validates the data, and provides traffic information for a user. The traffic information may relate to the current position and route of the user or a future route.
[0017] The present technology may also provide driving efficiency information. The driving efficiency information may include fuel consumption data, carbon footprint data, and a driving rating for a user associated with a vehicle. The fuel consumption data may be generated from vehicle speed and acceleration as determined by positioning system data provided to a mobile device application, as well as vehicle information provided by a user or other source. The carbon footprint may be derived from the fuel consumption by the vehicle. The driver rating may be determined based on fuel consumption and various EPA specifications for a vehicle or other information.
[0018] FIG. 1 is a block diagram of an exemplary system 100 for analyzing traffic data. System 100 includes mobile devices 110, 130 and 140, network 120, public entity traffic data server 150, private entity traffic data server 160, and crowd sourcing management server 170. Mobile device 100 may communicate with network 120 and be operated by a user in a moving vehicle. Mobile device 110 may include circuitry, logic, software, and other components for determining a position, speed, and acceleration of the mobile device. In some embodiments, mobile device 110 may include a global positioning system (GPS) mechanism for determining the location of the device. Based on the location data, the speed and acceleration of the device may be determined.
[0019] Mobile device 110 may also include device application 115. Device application 115 may be stored in memory and executed by one or more processors to process the GPS data, locally collected data and other data received over network 120 to provide traffic information, eco-information, and driving rating information through a display of mobile device 110.
[0020] Network 120 may communicate with mobile devices 110, 130 and 140 and data servers 150, 160 and 170. Network 120 may include a private network, public network, local area network, wide area network, the Internet, an intranet, and a combination of these networks.
[0021] Mobile devices 130 and 140 may also be associated with a respective vehicle and may include GPS or other position detection mechanisms. Each mobile device 130 and 140 may include a device application which may actively or passively provide traffic data and other data to crowd sourcing management server 170 over network 120. For example, when a device application stored on mobile device 130 is executing and the vehicle containing mobile device 130 is moving, the mobile application may passively provide data by transmitting position, speed and acceleration data detected by a GPS unit to crowd sourcing management server 170.
[0022] Mobile device 130 may also provide active data to crowd sourcing management server 170. A user may capture an image or video of a traffic incident or create an incident report by providing information of a collision, stalled car, or other event that affects traffic. The user may provide the image, video, or incident report to the device application, which in turn transmits the content to crowd sourcing management server 170.
[0023] Public entity traffic data server 150 may include one or more servers, including one or more network servers, web servers, applications servers and database servers, that provide traffic data by a public sector organization. The public sector organization may be, for example, the Department of Transportation or some other public entity. Public entity traffic data server 150 may provide traffic data such as incident data for a planned or unplanned traffic incident, traffic speed and flow data, or traffic camera image and video data. A planned traffic incident may include data for a highway closure or construction work. An unplanned traffic incident may include data for a disabled vehicle or a car crash. The traffic speed and flow data may be determined from radar outposts, toll booth data collection, or other data. The traffic camera image and video may be collected by public sector traffic cams located on roadways.
[0024] Private entity traffic data server 160 may include one or more servers, including one or more network servers, web servers, applications servers and database servers, that provide traffic data such as incident data, traffic speed and flow data and traffic camera and image data. Examples of private entity traffic data servers are those provided by companies such as Inrix, Traffic Cast, Clear Channel, and Traffic.com.
[0025] Crowd sourcing management server 170 may include one or more servers, including one or more network servers, web servers, applications servers and database servers, that receive crowd source data from mobile devices 110, 130 and 140, aggregate and organize the data, and provide traffic data to a device application on any of mobile devices 110, 130 or 140. Data is received from a plurality of remote mobile device applications regarding current traffic information. The traffic information is aggregated to create a unified set of data and broadcast to mobile devices to which the data is relevant.
[0026] In some embodiments, crowd sourcing data is transmitted directly between mobile devices. Hence, data which is passive and actively collected by mobile device 110 may be transmitted directly to mobile devices 130 and 140 via network 120, without involving crowd sourcing management server 170.
[0027] FIG. 2 is a block diagram of an exemplary device application 115. Device application 115 may include a data management module 210, personalization module 220, traffic prediction module 230, data validation module 240, trip routing module 250, data collection module 260, and eco analysis module 270. Data management module 210 may receive various types of data from different data sources. The data types may include incident data, traffic speed and flow data, and traffic camera, image and video data. The data sources may include crowd sourcing, public entity network services and private company network services. Module 210 may sort the received data and provide the data to data validation module 240.
[0028] Personalization module 220 may store and provide data regarding a particular user's preferred or favorite route, interface preferences, and other parameters that a user of device application 115 has set to customize their experience. Personalization module 220 may distill all the received data and present the user with only the relevant part according to received user criteria. The criteria may include user location (received from the mobile device), profile data, various start and end locations for routes they are likely to take, specified types of traffic information they are most interested in, and certain traffic cameras they are interested in for snapshots.
[0029] Traffic prediction module 230 may predict traffic along a user's specified route, a particular location at a particular time or period of time, or for some other roadway in the future. The prediction engine 230 learns about recurring traffic speeds at certain locations and times, and displays to the user forecasted traffic conditions on a user-centered map at various points of time as requested by the user. In this way, the system may provide to a user information such that the user can make an informed decision on whether to delay a departure, leave on time, or leave earlier if possible.
[0030] Data validation module 240 may receive data for a particular point from data management module 210. Validation module 240 may then determine if all the data points for the particular traffic points are valid. For example, if device application 115 receives multiple points of traffic data indicating different traffic speeds at a particular road for a particular time as a result of crowd sourcing data, data validation module 240 may validate the collection of data for the traffic point by removing an anomaly data point from that data set.
[0031] Data validation module 240 may implement a quality process which acts on the input data and validates it for various criteria including timeliness. The relevance of a quality process helps address data sources which are subject to being unavailable due to network connection (i.e., cellular) becoming temporarily unavailable or various types of disruptions with the data source itself. By entirely relying on just one data source and reproducing it exactly for the end user, the result for data disruption would potentially detrimental to the user/traveler. For example, the absence/intermittence of a displayced incident potentially being interpreted as the roadway being clear, just because the source became temporarily unavailable.
[0032] Trip routing module 250 allows a user to select routes between points of travel, and provides traffic predictions for the travel route. The travel prediction is provided by trip routing module 250 through an interface and is received by routing module 250 from traffic prediction module 230. The routing module may provide point to point trip times, as well as trip time predictions for various departure times, and various days of the week.
[0033] Data collection module 260 may collect data from device application 115 and mobile device 110 with respect to crowd sourcing data. The crowd sourcing data may include current location, speed and acceleration of the mobile device. The crowd sourcing data may also include data actively provided by a user, such as video, incident report, or other data.
[0034] In some embodiments, when the present application is executing and a GPS module on device 110 is operating, location data may be collected with a sampling interval and a transmission interval. The sampling interval and transmission interval may be selected so as to optimize latency and data relevance while minimizing data transmission costs for the user of the mobile device. Data is transmitted to data management module 210 by the data collection module 260 and may be provided to other mobile devices. The data may be provided to other mobile devices through a crowd sourcing management server 170 or via direct communication between mobile devices.
[0035] Eco analysis module 270 may determine a user rating, carbon footprint, fuel consumption, and other driver related data based on activity data processed by device application 115. Information provided by eco analysis module 270 is discussed in more detail below.
[0036] FIG. 3 is an exemplary method for processing traffic data. The method of FIG. 3 is performed by device application 115. Traffic information is provided at step 310. Providing traffic information may include providing an indication of the current or predicted traffic for a particular location through a display of mobile device 110. The traffic information may be generated based on multiple data types received form multiple data sources. Providing traffic information is discussed in more detail below with respect to the method of FIG. 4 .
[0037] Speed and acceleration data are received at step 320. The data collection module 250 may receive data provided by a GPS system, mobile device accelerometer components, and other sources. Vehicle information is then received at step 330. The vehicle information may be received by device application 115 from user input received by mobile device 110. The input may indicate the user's car make, model and year. Upon receiving this information, device application 115 may retrieve the vehicle mass, front area, and drag efficient from a data store maintained at mobile device 110. This information may be used to determine fuel consumption by application 115.
[0038] Fuel consumption data may be provided to a user at step 340. Device application 115 may provide fuel consumption data based on the car specification and car activity. Providing fuel consumption data is discussed in more detail below with respect to the method of FIG. 5 .
[0039] A carbon footprint data is provided for a particular user at step 350. The carbon footprint data may be based on the fuel consumed by the driver as determined by device application 115. The fuel consumed corresponds to the exhaust generated by the car, and therefore the carbon footprint data can be determined accordingly. For example, a gallon of gasoline emits 8.7 kg of CO2 into the atmosphere.
[0040] A driver rating is generated and provided for the user of the mobile device at step 360. A driver rating may be provided in a variety of ways. For example, Environment Protection Agency (EPA) statistics may be used to provide a driver rating. Alternatively, an ideal trip comparison with the user's actual trip may be determined to generate a driver rating. Providing a driver rating is discussed in more detail below with respect to FIGS. 6 and 7 .
[0041] FIG. 4 is an exemplary method for providing traffic information. The method of FIG. 4 provides more information for step 310 of the method of FIG. 3. Incident data is retrieved at step 410. The incident data may be retrieved locally from the mobile device 110 and remotely from crowd sourcing management server 170. The incident data may include planned and unplanned incidents as discussed herein.
[0042] Vehicle data and acceleration data may be retrieved at step 420. The vehicle speed and acceleration data may be retrieved from GPS components within mobile device 110. The GPS data may include a longitude, latitude and other data. Traffic media data may be retrieved at step 430. The traffic media data may include images and video associated with the user's current location or planned route. The received incident data, traffic media data, and GPS data may be validated at step 440. Data validation may include removing anomalies in sets of traffic data associated with a current point or route.
[0043] Route or current location data is received at step 450. The current location may be determined by a GPS component in mobile device 110 while a route may be received from a user through an interface at mobile device 110. Personalized traffic data is then generated for the user at step 460. The personalized traffic data may include a type of traffic information to display, settings for an interface in which to display the traffic, and other personalizations. The traffic information is then provided to the user at step 470. The information may be provided to the user through an interface of mobile device 110 by device application 115. The traffic information may be updated periodically and is based on types of data provided by multiple sources. The frequency at which the traffic information is updated may be selected by a user or set by the device application, and may be based on the balance of accuracy versus the battery performance.
[0044] FIG. 5 is an exemplary method for providing fuel consumption data. The method of FIG. 5 provides more detail for step 340 of the method of FIG. 3 . First, a current vehicle power spent is determined by a user at step 510. The current vehicle power may be estimated using the speed, the acceleration and the car's specification information, according to H. Rakha et. al's paper “Simple Comprehensive Fuel Consumption and CO2 Emission Model based on Instantaneous Vehicle Power”:
P=(Force(t)*v(t)/(3600·η),
with Force(t)=Q ·CD·Ch·Af·v(t)2/25.92+g·m·Cr·(C1·v(t)+C2)+g·m·G(t)+m·a(t)/1.04, and P in kW, with v in km/h, a(t) in m/s/s.
P=(Force(t)*v(t)/(3600·η),
with Force(t)=
[0045] In the calculation, Q is the density of air at sea level at a temperature of 15° C. (59° F.), CD is the drag coefficient (unitless), Ch is a correction factor for altitude (unitless), Af is the vehicle frontal area (m2), v(t) is the vehicle speed at time t, Cr, c1, and c2 are rolling resistance parameters that vary as a function of the road surface type, road condition, and vehicle tire type, m is the vehicle mass (kg), a(t) is the vehicle acceleration (m/s2) at time t, g=9.8066, and G(t) is the vertical acceleration.
[0046] A determination is then made as to whether the current vehicle power differs from the previous vehicle power at step 520. In some embodiments, the current vehicle power might be analyzed to determine if it differs from the previous vehicle power or is within an acceptable threshold range of the previous vehicle power trend data, such as within 5%. If the current vehicle power does not differ from the previous vehicle power by greater than a threshold amount, the vehicle power is not stored and the fuel consumption is not determined for the vehicle power. Rather, the current fuel consumption is set as the previous fuel consumption and the method of FIG. 5 continues to step 560.
[0047] If the current vehicle power does differ from the previous vehicle power, current fuel consumption is generated from the current power spent at step 530. The current fuel consumption may be generated as a function of power:
FC(t)=α0+α1·P(t)+α2·P(t)2,
FC(t)=α0+α1·P(t)+α2·P(t)2,
[0048] The coefficients of this second order polynomial may be calculated with the EPA estimations.
[0049] The current vehicle fuel consumption is then filtered at step 540. The vehicle fuel consumption may be filtered using a variety of techniques, such as a median filter, average filter, or least square filter. The filtered vehicle fuel consumption value is then stored at step 550 but the filtered vehicle fuel consumption may be stored locally at mobile device 110. The fuel consumption value is then provided through an interface to a user of mobile device 110 at step 560.
[0050] FIG. 6 is an exemplary embodiment for providing driver rating data. The method of FIG. 6 provides more detail for an embodiment of step 360 of the method of FIG. 3 . An EPA miles per gallon (MPG) is set to a city rating if the detected velocity of the mobile device (and corresponding vehicle) is the same or less than the average city speed at step 610. In some embodiments, the average city speed may be set at 21 miles per hour. Therefore, if a user is currently traveling or has shown a trend of traveling at 21 miles per hour or less, the EPA MPG is set to the vehicles city MPG rating.
[0051] The EPA MPG is set to the vehicle's highway MPG rating if the mobile device's detected velocity is the same or greater than an average highway speed at step 620. In some embodiments, the average highway speed may be 48 miles per hour.
[0052] The EPA mpg may be set to a value between the city MPG and highway MPG if the velocity is between the average city speed and average highway speed at step 630. In some embodiments, the EPA MPG may be set to a value proportionally between the city and highway MPG values based on where the velocity value is between the average city speed and the average highway speed. In some embodiments the following formula may be used to determine the EPA mpg for a speed between the city speed and highway speed.
EPA MPG=(r*EFhwy+(1−r)*EFcity),
where r=(speed−21.81)/(48.27−21.81).
EPA MPG=(r*EFhwy+(1−r)*EFcity),
where r=(speed−21.81)/(48.27−21.81).
[0053] An EPA gas spent value is determined at step 640. The EPA gas spent value is determined as the actual distance divided by the EPA mpg value determined previously. The EPA mileage traveled value is determined at step 650. The EPA mileage traveled value is determined as the EPA mpg times the fuel consumption by the user.
[0054] The potential fuel savings and potential additional miles for the user are determined at step 660. The potential fuel savings and additional miles is determined by calculating the difference between the actual fuel spent and miles traveled from the EPA fuel spent and mileage traveled. Next, the EPA and potential information is provided to a user through an interface provided by application 115 at step 670.
[0055] FIG. 7 is another exemplary method for providing a driver rating. First, fuel consumption is determined for a trip with one start and one stop. For example, for a trip from San Francisco to San Jose, the fuel consumption is determined for the trip assuming that the user leaves San Francisco and arrives at San Jose without making any stops and maintaining a constant speed.
[0056] The trip is divided into portions separated by stops at step 720. The stops may be determined based on traffic lights, off ramps, and other locations along the planned route at which a stop is likely. A beginning portion of each separate portion is replaced with an acceleration from a stop at step 730. The acceleration portion is intended to account for fuel consumption required to bring the vehicle up to speed after stopped at expected stopping points. The average speed proportion is then determined at step 740. The ideal fuel consumption is then determined for each portion based on the distance, expected average speed, and acceleration at step 750. The actual fuel consumption is compared to the ideal fuel consumption determined at step 750 at 760. A score is then based on a comparison and provided to a user at step 770.
[0057] FIG. 8 illustrates an exemplary mobile device system 800 that may be used to implement a mobile device for use with the present technology, such as for mobile devices 110, 130 and 140. The mobile device 800 of FIG. 8 includes one or more processors 810 and memory 812. Memory 812 stores, in part, programs, instructions and data for execution and processing by processor 810. The system 800 of FIG. 8 further includes storage 814, one or more antennas 816, a display system 818, inputs 820, one or more microphones 822, and one or more speakers 824.
[0058] The components shown in FIG. 8 are depicted as being connected via a single bus 826. However, the components 810-1024 may be connected through one or more data transport means. For example, processor unit 810 and main memory 812 may be connected via a local microprocessor bus, and storage 814, display system 818, input 820, and microphone 822 and speaker 824 may be connected via one or more input/output (I/O) buses.
[0059] Memory 812 may include local memory such as RAM and ROM, portable memory in the form of an insertable memory card or other attachment (e.g., via universal serial bus), a magnetic disk drive or an optical disk drive, a form of FLASH or PROM memory, or other electronic storage medium. Memory 812 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 810.
[0060] Antenna 816 may include one or more antennas for communicating wirelessly with another device. Antenna 816 may be used, for example, to communicate wirelessly via Wi-Fi, Bluetooth, with a cellular network, or with other wireless protocols and systems. The one or more antennas may be controlled by a processor 810, which may include a controller, to transmit and receive wireless signals. For example, processor 810 execute programs stored in memory 812 to control antenna 816 transmit a wireless signal to a cellular network and receive a wireless signal from a cellular network.
[0061] Display system 818 may include a liquid crystal display (LCD), a touch screen display, or other suitable display device. Display system 870 may be controlled to display textual and graphical information and output to text and graphics through a display device. When implemented with a touch screen display, the display system may receive input and transmit the input to processor 810 and memory 812.
[0062] Input devices 820 provide a portion of a user interface. Input devices 860 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, buttons or switches, a trackball, stylus, or cursor direction keys.
[0063] Microphone 822 may include one or more microphone devices which transmit captured acoustic signals to processor 810 and memory 812. The acoustic signals may be processed to transmit over a network via antenna 816.
[0064] Speaker 824 may provide an audio output for mobile device 800. For example, a signal received at antenna 816 may be processed by a program stored in memory 812 and executed by processor 810. The output of the executed program may be provided to speaker 824 which provides audio. Additionally, processor 810 may generate an audio signal, for example an audible alert, and output the audible alert through speaker 824.
[0065] The mobile device system 800 as shown in FIG. 8 may include devices and components in addition to those illustrated in FIG. 8 . For example, mobile device system 800 may include an additional network interface such as a universal serial bus (USB) port.
[0066] The components contained in the computer system 800 of FIG. 8 are those typically found in mobile device systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such mobile device components that are well known in the art. Thus, the computer system 800 of FIG. 8 can be a cellular phone, smart phone, hand held computing device, minicomputer, or any other computing device. The mobile device can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Google OS, Palm OS, and other suitable operating systems.
[0067] FIG. 9 illustrates an exemplary computing system 900 that may be used to implement a computing device for use with the present technology. System 900 of FIG. 9 may be implemented in the contexts of the likes of servers 150, 160 and 170 of FIG. 1 . The computing system 900 of FIG. 9 includes one or more processors 910 and memory 920. Main memory 920 stores, in part, instructions and data for execution by processor 910. Main memory 920 can store the executable code when in operation. The system 900 of FIG. 9 further includes a mass storage device 930, portable storage medium drive(s) 940, output devices 950, user input devices 960, a graphics display 970, and peripheral devices 980.
[0068] The components shown in FIG. 9 are depicted as being connected via a single bus 990. However, the components may be connected through one or more data transport means. For example, processor unit 910 and main memory 920 may be connected via a local microprocessor bus, and the mass storage device 930, peripheral device(s) 980, portable storage device 940, and display system 970 may be connected via one or more input/output (I/O) buses.
[0069] Mass storage device 930, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 910. Mass storage device 930 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 920.
[0070] Portable storage device 940 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or Digital video disc, to input and output data and code to and from the computer system 900 of FIG. 9 . The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 900 via the portable storage device 940.
[0071] Input devices 960 provide a portion of a user interface. Input devices 960 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 900 as shown in FIG. 9 includes output devices 950. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.
[0072] Display system 970 may include a liquid crystal display (LCD) or other suitable display device. Display system 970 receives textual and graphical information, and processes the information for output to the display device.
[0073] Peripherals 980 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 980 may include a modem or a router.
[0074] The components contained in the computer system 900 of FIG. 9 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 900 of FIG. 9 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems.
[0075] The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology 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 technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claims appended hereto.
Claims
What is claimed is:
1. A method for processing traffic data, comprising:
receiving traffic data by a mobile device, the traffic data originating from multiple sources,
wherein the traffic data is received at least in part from crowd sourced data, a portion of the crowd sourced data originating passively through a plurality of mobile devices and another portion of the crowd sourced data originating actively from a remote user through a plurality of mobile devices, and
wherein the traffic data includes incident data, traffic flow data, and media data associated with the traffic;
validating the traffic data by:
aggregating the traffic data and
removing anomalies in the traffic data;
providing traffic information to a user through an interface of the mobile device according to user criteria,
wherein the user criteria includes at least a user location and at least one type of traffic information the user is interested in receiving, and
wherein the traffic information is generated based on the validated traffic data;
providing driving efficiency information through the interface; and
updating the traffic information at a frequency based on accuracy of the traffic information and battery performance of the mobile device.
2. The method of claim 1, wherein the driving efficiency information includes fuel consumption data.
3. The method of claim 2, wherein the fuel consumption data is based at least in part on vehicle specification information.
4. The method of claim 2, wherein the fuel consumption data is filtered.
5. The method of claim 1, wherein the driving efficiency information includes carbon footprint data.
6. The method of claim 1, wherein the driving efficiency information includes driver rating data.
7. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for processing traffic data, the method comprising:
receiving traffic data by a mobile device, the traffic data originating from multiple sources,
wherein the traffic data is received at least in part from crowd sourced data, a portion of the crowd sourced data originating passively through a plurality of mobile devices and another portion of the crowd sourced data originating actively from a remote user through a plurality of mobile devices, and
wherein the traffic data includes incident data, traffic flow data, and media data associated with the traffic;
validating the traffic data by:
aggregating the traffic data and
removing anomalies in the traffic data;
providing traffic information to a user through an interface of the mobile device according to user criteria,
wherein the user criteria includes at least a user location and at least one type of traffic information the user is interested in receiving, and
wherein the traffic information is generated based on the validated traffic data;
providing driving efficiency information through the interface; and
updating the traffic information at a frequency based on accuracy of the traffic information and battery performance of the mobile device.
8. The non-transitory computer readable storage medium of claim 7, wherein the driving efficiency information includes fuel consumption data.
9. The non-transitory computer readable storage medium of claim 8, wherein the fuel consumption data is based at least in part on vehicle specification information.
10. The non-transitory computer readable storage medium of claim 8, wherein the fuel consumption data is filtered.
11. The non-transitory computer readable storage medium of claim 7, wherein the driving efficiency information includes carbon footprint data.
12. The non-transitory computer readable storage medium of claim 7, wherein the driving efficiency information includes driver rating data.
Patent Citations (304)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4734863(A) | 1988-03-01 | Honey et al. | Applicant |
| US4788645(A) | 1988-11-01 | Zavoli et al. | Applicant |
| US4792803(A) | 1988-12-01 | Madnick et al. | Applicant |
| US4796191(A) | 1989-01-01 | Honey et al. | Applicant |
| US4878170(A) | 1989-10-01 | Zeevi | Applicant |
| US4914605(A) | 1990-04-01 | Loughmiller, Jr. et al. | Applicant |
| US4926343(A) | 1990-05-01 | Tsuruta et al. | Applicant |
| US5068656(A) | 1991-11-01 | Sutherland | Applicant |
| US5095532(A) | 1992-03-01 | Mardus | Applicant |
| US5126941(A) | 1992-06-01 | Gurmu et al. | Applicant |
| US5164904(A) | 1992-11-01 | Sumner | Applicant |
| US5173691(A) | 1992-12-01 | Sumner | Applicant |
| US5182555(A) | 1993-01-01 | Sumner | Applicant |
| US5220507(A) | 1993-06-01 | Kirson | Applicant |
| US5247439(A) | 1993-09-01 | Gurmu et al. | Applicant |
| US5262775(A) | 1993-11-01 | Tamai et al. | Applicant |
| US5276785(A) | 1994-01-01 | Mackinlay et al. | Applicant |
| US5283575(A) | 1994-02-01 | Kao et al. | Applicant |
| US5291412(A) | 1994-03-01 | Tamai et al. | Applicant |
| US5291413(A) | 1994-03-01 | Tamai et al. | Applicant |
| US5291414(A) | 1994-03-01 | Tamai et al. | Applicant |
| US5297028(A) | 1994-03-01 | Ishikawa | Applicant |
| US5297049(A) | 1994-03-01 | Gurmu et al. | Applicant |
| US5303159(A) | 1994-04-01 | Tamai et al. | Applicant |
| US5311195(A) | 1994-05-01 | Mathis et al. | Applicant |
| US5311434(A) | 1994-05-01 | Tamai | Applicant |
| US5339246(A) | 1994-08-01 | Kao | Applicant |
| US5343400(A) | 1994-08-01 | Ishikawa | Applicant |
| US5345382(A) | 1994-09-01 | Kao | Applicant |
| US5359529(A) | 1994-10-01 | Snider | Applicant |
| US5374933(A) | 1994-12-01 | Kao | Applicant |
| US5377113(A) | 1994-12-01 | Shibazaki et al. | Applicant |
| US5390123(A) | 1995-02-01 | Ishikawa | Applicant |
| US5394333(A) | 1995-02-01 | Kao | Applicant |
| US5402120(A) | 1995-03-01 | Fujii et al. | Applicant |
| US5414630(A) | 1995-05-01 | Oshizawa et al. | Applicant |
| US5428545(A) | 1995-06-01 | Maegawa et al. | Applicant |
| US5430655(A) | 1995-07-01 | Adachi | Applicant |
| US5440484(A) | 1995-08-01 | Kao | Applicant |
| US5465079(A) | 1995-11-01 | Bouchard et al. | Applicant |
| US5477220(A) | 1995-12-01 | Ishikawa | Applicant |
| US5485161(A) | 1996-01-01 | Vaughn | Applicant |
| US5488559(A) | 1996-01-01 | Seymour | Applicant |
| US5499182(A) | 1996-03-01 | Ousborne | Applicant |
| US5508931(A) | 1996-04-01 | Snider | Applicant |
| US5515283(A) | 1996-05-01 | Desai | Applicant |
| US5515284(A) | 1996-05-01 | Abe | Applicant |
| US5539645(A) | 1996-07-01 | Mandhyan et al. | Applicant |
| US5546107(A) | 1996-08-01 | Deretsky et al. | Applicant |
| US5548822(A) | 1996-08-01 | Yogo | Applicant |
| US5550538(A) | 1996-08-01 | Fujii et al. | Applicant |
| US5554845(A) | 1996-09-01 | Russell | Applicant |
| US5583972(A) | 1996-12-01 | Miller | Applicant |
| US5608635(A) | 1997-03-01 | Tamai | Applicant |
| US5610821(A) | 1997-03-01 | Gazis et al. | Applicant |
| US5689252(A) | 1997-11-01 | Ayanoglu et al. | Applicant |
| US5694534(A) | 1997-12-01 | White, Jr. et al. | Applicant |
| US5699056(A) | 1997-12-01 | Yoshida | Applicant |
| US5706503(A) | 1998-01-01 | Poppen et al. | Applicant |
| US5712788(A) | 1998-01-01 | Liaw et al. | Applicant |
| US5729458(A) | 1998-03-01 | Poppen | Applicant |
| US5731978(A) | 1998-03-01 | Tamai et al. | Applicant |
| US5742922(A) | 1998-04-01 | Kim | Applicant |
| US5751245(A) | 1998-05-01 | Janky et al. | Applicant |
| US5751246(A) | 1998-05-01 | Hertel | Applicant |
| US5757359(A) | 1998-05-01 | Morimoto et al. | Applicant |
| US5774827(A) | 1998-06-01 | Smith et al. | Applicant |
| US5818356(A) | 1998-10-01 | Schuessler | Applicant |
| US5822712(A) | 1998-10-01 | Olsson | Applicant |
| US5845227(A) | 1998-12-01 | Peterson | Applicant |
| US5850190(A) | 1998-12-01 | Wicks et al. | Applicant |
| US5862244(A) | 1999-01-01 | Kleiner et al. | Applicant |
| US5862509(A) | 1999-01-01 | Desai et al. | Applicant |
| US5864305(A) | 1999-01-01 | Rosenquist | Applicant |
| US5867110(A) | 1999-02-01 | Naito et al. | Applicant |
| US5893081(A) | 1999-04-01 | Poppen | Applicant |
| US5893898(A) | 1999-04-01 | Tanimoto | Applicant |
| US5898390(A) | 1999-04-01 | Oshizawa et al. | Applicant |
| US5902350(A) | 1999-05-01 | Tamai et al. | Applicant |
| US5904728(A) | 1999-05-01 | Tamai et al. | Applicant |
| US5908464(A) | 1999-06-01 | Kishigami et al. | Applicant |
| US5910177(A) | 1999-06-01 | Zuber | Applicant |
| US5911773(A) | 1999-06-01 | Mutsuga et al. | Applicant |
| US5912635(A) | 1999-06-01 | Oshizawa et al. | Applicant |
| US5916299(A) | 1999-06-01 | Poppen | Applicant |
| US5922042(A) | 1999-07-01 | Sekine et al. | Applicant |
| US5928307(A) | 1999-07-01 | Oshizawa et al. | Applicant |
| US5931888(A) | 1999-08-01 | Hiyokawa | Applicant |
| US5933100(A) | 1999-08-01 | Golding | Applicant |
| US5938720(A) | 1999-08-01 | Tamai | Applicant |
| US5948043(A) | 1999-09-01 | Mathis et al. | Applicant |
| US5978730(A) | 1999-11-01 | Poppen et al. | Applicant |
| US5982298(A) | 1999-11-01 | Lappenbusch et al. | Applicant |
| US5987381(A) | 1999-11-01 | Oshizawa et al. | Applicant |
| US5991687(A) | 1999-11-01 | Hale et al. | Applicant |
| US5999882(A) | 1999-12-01 | Simpson et al. | Applicant |
| US6009374(A) | 1999-12-01 | Urahashi | Applicant |
| US6011494(A) | 2000-01-01 | Watanabe et al. | Applicant |
| US6016485(A) | 2000-01-01 | Amakawa et al. | Applicant |
| US6021406(A) | 2000-02-01 | Kuznetsov | Applicant |
| US6038509(A) | 2000-03-01 | Poppen et al. | Applicant |
| US6058390(A) | 2000-05-01 | Liaw et al. | Applicant |
| US6064970(A) | 2000-05-01 | McMillan et al. | Applicant |
| US6091359(A) | 2000-07-01 | Geier | Applicant |
| US6091956(A) | 2000-07-01 | Hollenberg | Applicant |
| US6097399(A) | 2000-08-01 | Bhatt et al. | Applicant |
| US6111521(A) | 2000-08-01 | Mulder et al. | Applicant |
| US6144919(A) | 2000-11-01 | Ceylan et al. | Applicant |
| US6147626(A) | 2000-11-01 | Sakakibara | Applicant |
| US6150961(A) | 2000-11-01 | Alewine et al. | Applicant |
| US6161092(A) | 2000-12-01 | Latshaw et al. | Applicant |
| US6169552(B1) | 2001-01-01 | Endo et al. | Applicant |
| US6188956(B1) | 2001-02-01 | Walters | Applicant |
| US6209026(B1) | 2001-03-01 | Ran et al. | Applicant |
| US6222485(B1) | 2001-04-01 | Walters et al. | Applicant |
| US6236933(B1) | 2001-05-01 | Lang | Applicant |
| US6253146(B1) | 2001-06-01 | Hanson et al. | Applicant |
| US6253154(B1) | 2001-06-01 | Oshizawa et al. | Applicant |
| US6256577(B1) | 2001-07-01 | Graunke | Applicant |
| US6259987(B1) | 2001-07-01 | Ceylan et al. | Applicant |
| US6282486(B1) | 2001-08-01 | Bates et al. | Applicant |
| US6282496(B1) | 2001-08-01 | Chowdhary | Applicant |
| US6292745(B1) | 2001-09-01 | Robare et al. | Applicant |
| US6295492(B1) | 2001-09-01 | Lang et al. | Applicant |
| US6297748(B1) | 2001-10-01 | Lappenbusch et al. | Applicant |
| US6298305(B1) | 2001-10-01 | Kadaba et al. | Applicant |
| US6317685(B1) | 2001-11-01 | Kozak et al. | Applicant |
| US6317686(B1) | 2001-11-01 | Ran | Applicant |
| US6335765(B1) | 2002-01-01 | Daly et al. | Applicant |
| US6353795(B1) | 2002-03-01 | Ranjan | Applicant |
| US6356836(B1) | 2002-03-01 | Adolph | Applicant |
| US6360165(B1) | 2002-03-01 | Chowdhary | Applicant |
| US6362778(B2) | 2002-03-01 | Neher | Applicant |
| US6415291(B2) | 2002-07-01 | Bouve et al. | Applicant |
| US6424910(B1) | 2002-07-01 | Ohler et al. | Applicant |
| US6456931(B1) | 2002-09-01 | Polidi et al. | Applicant |
| US6456935(B1) | 2002-09-01 | Ng | Applicant |
| US6463400(B1) | 2002-10-01 | Barkley-Yeung | Applicant |
| US6466862(B1) | 2002-10-01 | DeKock et al. | Applicant |
| US6470268(B1) | 2002-10-01 | Ashcraft et al. | Applicant |
| US6473000(B1) | 2002-10-01 | Secreet et al. | Applicant |
| US6480783(B1) | 2002-11-01 | Myr | Applicant |
| US6504541(B1) | 2003-01-01 | Liu et al. | Applicant |
| US6529143(B2) | 2003-03-01 | Mikkola et al. | Applicant |
| US6532304(B1) | 2003-03-01 | Liu et al. | Applicant |
| US6539302(B1) | 2003-03-01 | Bender et al. | Applicant |
| US6542814(B2) | 2003-04-01 | Polidi et al. | Applicant |
| US6552656(B2) | 2003-04-01 | Polidi et al. | Applicant |
| US6556905(B1) | 2003-04-01 | Mittelsteadt et al. | Applicant |
| US6559865(B1) | 2003-05-01 | Angwin | Applicant |
| US6574548(B2) | 2003-06-01 | DeKock et al. | Applicant |
| US6584400(B2) | 2003-06-01 | Beardsworth | Applicant |
| US6594576(B2) | 2003-07-01 | Fan et al. | Applicant |
| US6598016(B1) | 2003-07-01 | Zavoli et al. | Applicant |
| US6600994(B1) | 2003-07-01 | Polidi | Applicant |
| US6603405(B2) | 2003-08-01 | Smith | Applicant |
| US6622086(B2) | 2003-09-01 | Polidi | Applicant |
| US6650997(B2) | 2003-11-01 | Funk | Applicant |
| US6654681(B1) | 2003-11-01 | Kiendl et al. | Examiner |
| US6675085(B2) | 2004-01-01 | Straub | Applicant |
| US6681176(B2) | 2004-01-01 | Funk et al. | Applicant |
| US6687615(B1) | 2004-02-01 | Krull et al. | Applicant |
| US6700503(B2) | 2004-03-01 | Masar et al. | Applicant |
| US6710774(B1) | 2004-03-01 | Kawasaki et al. | Applicant |
| US6720889(B2) | 2004-04-01 | Yamaki et al. | Applicant |
| US6728605(B2) | 2004-04-01 | Lash et al. | Applicant |
| US6728628(B2) | 2004-04-01 | Peterson | Applicant |
| US6731940(B1) | 2004-05-01 | Nagendran | Applicant |
| US6735516(B1) | 2004-05-01 | Manson | Applicant |
| US6754833(B1) | 2004-06-01 | Black et al. | Applicant |
| US6785606(B2) | 2004-08-01 | DeKock et al. | Applicant |
| US6791472(B1) | 2004-09-01 | Hoffberg | Applicant |
| US6807483(B1) | 2004-10-01 | Chao et al. | Applicant |
| US6845316(B2) | 2005-01-01 | Yates | Applicant |
| US6862524(B1) | 2005-03-01 | Nagda et al. | Applicant |
| USRE38724(E) | 2005-04-01 | Peterson | Applicant |
| US6885937(B1) | 2005-04-01 | Sunranyi | Applicant |
| US6901330(B1) | 2005-05-01 | Krull et al. | Applicant |
| US6914541(B1) | 2005-07-01 | Zierden | Applicant |
| US6922629(B2) | 2005-07-01 | Yoshikawa et al. | Applicant |
| US6931309(B2) | 2005-08-01 | Phelan et al. | Applicant |
| US6952643(B2) | 2005-10-01 | Matsuoka et al. | Applicant |
| US6965665(B2) | 2005-11-01 | Fan et al. | Applicant |
| US6983204(B2) | 2006-01-01 | Knutson | Applicant |
| US6987964(B2) | 2006-01-01 | Obradovich et al. | Applicant |
| US6989765(B2) | 2006-01-01 | Gueziec | Applicant |
| US6999873(B1) | 2006-02-01 | Krull et al. | Applicant |
| US7010583(B1) | 2006-03-01 | Aizono et al. | Applicant |
| US7062378(B2) | 2006-06-01 | Krull et al. | Applicant |
| US7069143(B2) | 2006-06-01 | Peterson | Applicant |
| US7103854(B2) | 2006-09-01 | Fuchs et al. | Applicant |
| US7161497(B2) | 2007-01-01 | Gueziec | Applicant |
| US7221287(B2) | 2007-05-01 | Gueziec | Applicant |
| US7356392(B2) | 2008-04-01 | Hubbard et al. | Applicant |
| US7375649(B2) | 2008-05-01 | Gueziec | Applicant |
| US7486201(B2) | 2009-02-01 | Kelly et al. | Applicant |
| US7508321(B2) | 2009-03-01 | Gueziec et al. | Examiner |
| US7511634(B2) | 2009-03-01 | Stehle et al. | Examiner |
| US7557730(B2) | 2009-07-01 | Gueziec | Applicant |
| US7558674(B1) | 2009-07-01 | Neiley et al. | Applicant |
| US7610145(B2) | 2009-10-01 | Kantarjiev et al. | Applicant |
| US7634352(B2) | 2009-12-01 | Soulchin et al. | Applicant |
| US7702452(B2) | 2010-04-01 | Kantarjiev et al. | Applicant |
| US7792642(B1) | 2010-09-01 | Neiley et al. | Applicant |
| US7880642(B2) | 2011-02-01 | Gueziec | Applicant |
| US8103443(B2) | 2012-01-01 | Kantarjiev et al. | Applicant |
| US8280355(B1) | 2012-10-01 | Jones | Examiner |
| US8358222(B2) | 2013-01-01 | Gueziec | Applicant |
| US2001/0014848(A1) | 2001-08-01 | Walgers et al. | Applicant |
| US2001/0018628(A1) | 2001-08-01 | Jenkins et al. | Applicant |
| US2001/0026276(A1) | 2001-10-01 | Sakamoto et al. | Applicant |
| US2001/0033225(A1) | 2001-10-01 | Razavi et al. | Applicant |
| US2001/0047242(A1) | 2001-11-01 | Ohta | Applicant |
| US2002/0042819(A1) | 2002-04-01 | Reichert et al. | Applicant |
| US2002/0077748(A1) | 2002-06-01 | Nakano | Applicant |
| US2002/0152020(A1) | 2002-10-01 | Seibel | Applicant |
| US2002/0175868(A1) | 2002-11-01 | Reichert | Applicant |
| US2003/0046158(A1) | 2003-03-01 | Kratky | Applicant |
| US2003/0109985(A1) | 2003-06-01 | Kotzin | Examiner |
| US2003/0135304(A1) | 2003-07-01 | Sroub et al. | Applicant |
| US2003/0182052(A1) | 2003-09-01 | DeLorme et al. | Applicant |
| US2004/0034464(A1) | 2004-02-01 | Yoshikawa et al. | Examiner |
| US2004/0046759(A1) | 2004-03-01 | Soulchin et al. | Applicant |
| US2004/0080624(A1) | 2004-04-01 | Yuen | Applicant |
| US2004/0107288(A1) | 2004-06-01 | Menninger et al. | Applicant |
| US2004/0143385(A1) | 2004-07-01 | Smyth et al. | Applicant |
| US2004/0249568(A1) | 2004-12-01 | Endo et al. | Applicant |
| US2005/0021225(A1) | 2005-01-01 | Kantarjiev et al. | Applicant |
| US2005/0143902(A1) | 2005-06-01 | Soulchin et al. | Applicant |
| US2005/0154505(A1) | 2005-07-01 | Nakamura et al. | Applicant |
| US2006/0122846(A1) | 2006-06-01 | Burr et al. | Applicant |
| US2006/0143959(A1) | 2006-07-01 | Stehle et al. | Applicant |
| US2006/0145892(A1) | 2006-07-01 | Gueziec | Applicant |
| US2006/0158330(A1) | 2006-07-01 | Gueziec | Applicant |
| US2006/0238521(A1) | 2006-10-01 | Westerman et al. | Applicant |
| US2006/0284766(A1) | 2006-12-01 | Gruchala et al. | Applicant |
| US2007/0013551(A1) | 2007-01-01 | Gueziec | Applicant |
| US2007/0038362(A1) | 2007-02-01 | Gueziec | Examiner |
| US2007/0060384(A1) | 2007-03-01 | Dohta | Applicant |
| US2007/0066394(A1) | 2007-03-01 | Ikeda et al. | Applicant |
| US2007/0197217(A1) | 2007-08-01 | Sutardja | Applicant |
| US2007/0208495(A1) | 2007-09-01 | Chapman et al. | Examiner |
| US2007/0208496(A1) | 2007-09-01 | Downs et al. | Examiner |
| US2007/0211026(A1) | 2007-09-01 | Ohta | Applicant |
| US2007/0211027(A1) | 2007-09-01 | Ohta | Applicant |
| US2007/0222750(A1) | 2007-09-01 | Ohta | Applicant |
| US2007/0247291(A1) | 2007-10-01 | Masuda et al. | Examiner |
| US2007/0265766(A1) | 2007-11-01 | Jung et al. | Applicant |
| US2008/0071465(A1) | 2008-03-01 | Chapman et al. | Applicant |
| US2008/0084385(A1) | 2008-04-01 | Ranta et al. | Applicant |
| US2008/0133120(A1) | 2008-06-01 | Romanick | Applicant |
| US2008/0255754(A1) | 2008-10-01 | Pinto | Applicant |
| US2008/0297488(A1) | 2008-12-01 | Operowsky et al. | Applicant |
| US2009/0005965(A1) | 2009-01-01 | Forstall et al. | Applicant |
| US2009/0061971(A1) | 2009-03-01 | Weitzner et al. | Applicant |
| US2009/0066495(A1) | 2009-03-01 | Newhouse et al. | Applicant |
| US2009/0082950(A1) | 2009-03-01 | Vorona | Examiner |
| US2009/0112465(A1) | 2009-04-01 | Weiss et al. | Applicant |
| US2009/0118017(A1) | 2009-05-01 | Perlman et al. | Applicant |
| US2009/0118996(A1) | 2009-05-01 | Kantarjiev et al. | Applicant |
| US2009/0189979(A1) | 2009-07-01 | Smyth | Applicant |
| US2009/0192702(A1) | 2009-07-01 | Bourne | Examiner |
| US2010/0094531(A1) | 2010-04-01 | Macleod | Applicant |
| US2010/0100307(A1) | 2010-04-01 | Kim | Applicant |
| US2010/0145569(A1) | 2010-06-01 | Bourque et al. | Applicant |
| US2010/0145608(A1) | 2010-06-01 | Kurtti et al. | Applicant |
| US2010/0175006(A1) | 2010-07-01 | Li | Applicant |
| US2010/0198453(A1) | 2010-08-01 | Dorogusker et al. | Applicant |
| US2010/0225643(A1) | 2010-09-01 | Gueziec | Applicant |
| US2010/0305839(A1) | 2010-12-01 | Wenzel | Examiner |
| US2010/0312462(A1) | 2010-12-01 | Gueziec | Applicant |
| US2010/0333045(A1) | 2010-12-01 | Gueziec | Applicant |
| US2011/0037619(A1) | 2011-02-01 | Ginsberg et al. | Examiner |
| US2011/0106427(A1) | 2011-05-01 | Kim et al. | Applicant |
| US2011/0304447(A1) | 2011-12-01 | Marumoto | Examiner |
| US2012/0072096(A1) | 2012-03-01 | Chapman et al. | Examiner |
| US2012/0123667(A1) | 2012-05-01 | Gueziec | Examiner |
| US2012/0150422(A1) | 2012-06-01 | Kantarjiev et al. | Applicant |
| US2012/0150425(A1) | 2012-06-01 | Chapman et al. | Examiner |
| US2012/0158275(A1) | 2012-06-01 | Huang et al. | Examiner |
| US2012/0290202(A1) | 2012-11-01 | Gueziec | Applicant |
| US2012/0290204(A1) | 2012-11-01 | Gueziec | Applicant |
| US2013/0033385(A1) | 2013-02-01 | Gueziec | Applicant |
| US2013/0211701(A1) | 2013-08-01 | Baker et al. | Examiner |
| DE19856704 | 2001-06-01 | Applicant | |
| EP749103 | 1996-12-01 | Applicant | |
| EP987665 | 2000-03-01 | Applicant | |
| EP1006367 | 2000-06-01 | Applicant | |
| GB2400293 | 2004-10-01 | Applicant | |
| JP5-313578 | 1993-11-01 | Applicant | |
| JP8-77485 | 1996-03-01 | Applicant | |
| JP10-261188 | 1998-09-01 | Applicant | |
| JP10-281782 | 1998-10-01 | Applicant | |
| JP10-293533 | 1998-11-01 | Applicant | |
| JP2000-055675 | 2000-02-01 | Applicant | |
| JP2000-113387 | 2000-04-01 | Applicant | |
| JP2001-330451 | 2001-11-01 | Applicant | |
| WO98/23018 | 1998-05-01 | Applicant | |
| WO/50917 | 2000-08-01 | Applicant | |
| WO1/88480 | 2001-11-01 | Applicant | |
| WO2/77921 | 2002-10-01 | Applicant | |
| WO3/014671 | 2003-02-01 | Applicant | |
| WO2005/076031 | 2005-08-01 | Applicant | |
| WO2010/073053 | 2010-07-01 | Applicant |
Non-Patent Literature (136)
- Acura Debuts AcuraLink™ Satellite-Linked Communication System with Industry's First Standard Real Time Traffic Feature at New York International Auto Show, 2004, 4 pages.Applicant
- Adib Kanafani, “Towards a Technology Assessment of Highway Navigation and Route Guidance,” Program on Advanced Technology for the Highway, Institute of Transportation Studies, University of California, Berkeley, Dec. 1987, PATH Working Paper UCB-ITS-PWP-87-6.Applicant
- Answer, Affirmative Defenses, and Counterclaims by Defendant Westwood One, Inc., to Plaintiff Triangle Software, LLC's Complaint for Patent Infringement.Applicant
- Answer and Counterclaims of TomTom, Inc. to Plaintiff Triangle Software, LLC's Complaint for Patent Infringement.Applicant
- Amended Answer and Counterclaims of TomTom, Inc. to Plaintiff Triangle Software, LLC's Complaint for Patent Infringement.Applicant
- Attachment A of Garmin's Preliminary Invalidity Contentions and Certificate of Service filed May 16, 2011 in Triangle Software, LLC. V. Garmin International, Inc. et al., Case No. 1: 10-cv-1457-CMH-TCB in the United States District Court for the Eastern District of Virginia, Alexandria Division, 6 pages.Applicant
- Attachment B of Garmin's Preliminary Invalidity Contentions and Certificate of Service filed May 16, 2011 in Triangle Software, LLC. V. Garmin International, Inc. et al., Case No. 1: 10-cv-1457-CMH-TCB in the United States District Court for the Eastern District of Virginia, Alexandria Division, 618 pages.Applicant
- Audi-V150 Manual, Oct. 2001, 152 pages, Japan.Applicant
- Balke, K.N., “Advanced Technologies for Communicating with Motorists: A Synthesis of Human Factors and Traffic Management Issues,” Report No. FHWA/TX-92/1232-8, May 1992, Texas Department Transportation, Austin, TX, USA, 62 pages.Applicant
- Barnaby J. Feder, “Talking Deals; Big Partners in Technology,” Technology, The New York Times, Sep. 3, 1987.Applicant
- Birdview Navigation System by Nissan Motor Corp, 240 Landmarks of Japanese Automotive Technology, 1995, 2 pages, Society of Automotive Engineers of Japan, Inc., Japan.Applicant
- Blumentritt, K. et al., “Travel System Architecture Evaluation,” Publication No. FHWA-RD-96-141, Jul. 1995, 504 pages, U.S. Department of Transportation, McLean, VA, USA.Applicant
- Brooks, et al., “Turn-by-Turn Displays versus Electronic Maps: An On-the-Road Comparison of Driver Glance Behavior,” Technical Report, The University of Michigan, Transportation Research Institute (UMTRI), Jan. 1999.Applicant
- Burgett, A.L., “Safety Evaluation of TravTek,” Vehicle Navigation & Information Systems Conference Proceedings (VNIS'91), P-253, Part 1, Oct. 1991, pp. 819-825, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Campbell, J.L. “Development of Human Factors Design Guidelines for Advanced Traveler Information Systems (ATIS)”, Proceedings Vehicle Navigation and Information Systems Conference, 1995, pp, 161-164, IEEE, New York, NY, USA.Applicant
- Campbell, J.L. “Development of Human Factors Design Guidelines for Advanced Traveler Information Systems (ATIS) and Commercial Vehicle Operations (CVO)”, Publication No. FHWA-RD-98-057, Report Date Sep. 1998, 294, pages, U.S. Department of Transportation, McLean, VA 22010-2296.Applicant
- Carin Navigation System Manual and Service Manual for Model Carin 22SY520, 76 pages, Philips Car Systems, The Netherlands.Applicant
- Cathey, F.W. et al., “A Prescription for Transit Arrival/Department Prediction Using Automatic Vehicle Location Data,” Transportation Research Part C 11, 2003, pp. 241-264, Pergamon Press Ltd., Elsevier Ltd., U.K.Applicant
- Chien, S.I. et al., “Predicting Travel Times for the South Jersey Real-Time Motorist Information System,” Transportation Research Record 1855, Paper No. 03-2750, Revised Oct. 2001, pp. 32-40.Applicant
- Chira-Chavala, T. et al., “Feasibility Study of Advanced Technology HOV Systems,” vol. 3: Benefit Implications of Alternative Policies for Including HOV lanes in Route Guidance Networks, Dec. 1992, 84 ages, UCB-ITS-PRR-92-5 PATH Research Report, Inst. of Transportation Studies, Univ. of Calif., Berkeley, USA.Applicant
- Clark, E.L., Development of Human Factors Guidelines for Advanced Traveler Information Systems (ATIS) and Commercial Vehicle Operations (CVO): Comparable Systems Analysis, Dec. 1996, 199 pages.Applicant
- Dancer, F. et al., “Vehicle Navigation Systems: Is America Ready?,” Navigation and Intelligent Transportation System, Automotive Electronics Series, Society of Automotive Engineers, 1998, pp. Cover page, Table of Contents pp. 3-8.Applicant
- Davies, P. et al., “Assessment of Advanced Technologies for Relieving Urban Traffic Congestion” National Cooperative Highway Research Program Report 340, Dec. 1991, 106 pages.Applicant
- de Cambray, B. “Three-Dimensional (3D) Modeling in a Geographical Database,” Auto-Carto'11, Eleventh International Conference on Computer Assisted Cartography, Oct. 30, 1993-Nov. 1, 1993, pp. 338-347, Minneapolis, USA.Applicant
- Declaration Under 37 C.F.R. 1.131 and Source Code from U.S. Appl. No. 10/897,550.Applicant
- Dillenburg, J.F. et al., “The Intelligent Travel Assistant,” IEEE 5th International Conference on Intelligent Transportation Systems, Sep. 3-6, 2002, pp. 691-696, Singapore.Applicant
- Dingus, T.A. et al., “Human Factors Engineering the TravTek Driver Interface,” Vehicle Navigation & Information System Conference Proceedings (VNIS'91), P-253, Part 2, Oct. 1991, pp. 749-755, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Endo, et al., “Development and Evaluation of a Car Navigation System Providing a Birds Eye View Map Display,” Navigation and Intelligent Transportation Systems, Automotive Electronics Series, Society of Automotive Engineers, 1998, pp. Cover page, Table of Contents, pp. 19-22.Applicant
- Eppinger, A. et al., “Dynamic Route Guidance—Status and Trends,” Convergence 2000 International Congress on Transportation Electronics, Oct. 16-18, 1999, 7 pages, held in Detroit, MI, SAE International Paper Series, Warrendale, PA, USA.Applicant
- Expert Report of Dr. Michael Goodchild Concerning the Validity of U.S. 5,938,720 dated Jun. 16, 2011 in Triangle Software, LLC v. Garmin International Inc. et al., in the United States District Court for the Eastern District of Virginia, Alexandria Division, Case No. 1:10-cv-1457-CMH-TCB, 16 pages.Applicant
- Fawcett, J., “Adaptive Routing for Road Traffic,” IEEE Computer Graphics and Applications, May/Jun. 2000, pp. 46-53, IEEE, New York, NY, USA.Applicant
- Fleischman, R.N., “Research and Evaluation Plans for the TravTek IVHS Operational Field Test, ”Vehicle Navigation & Information Systems Conference Proceedings (VNIS'91), P-253, Part 2, Oct. 1991, pp. 827-837, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Garmin International, Inc.'s Answer and Counterclaims to Triangle Software, LLC's Complaint.Applicant
- Garmin International, Inc.'s Amended Answer and Counterclaims to Triangle Software, LLC's Complaint.Applicant
- Garmin International, Inc. and Garmin USA, Inc.'s Answer and Counterclaim to Triangle Software, LLC's Supplemental Complaints filed Jun. 17, 2011 in Triangle Software, LLC. v. Garmin International Inc. et al., in the United States District Court for the Eastern District of Virginia, Alexandria Division, Case No. 1:10-cv-1457-CMH-TCB, 36 pages.Applicant
- Garmin's Preliminary Invalidity Contentions and Certificate of Service filed May 16, 2011 in Triangle Software, LLC. V. Garmin International, Inc. et al., Case No. 1: 10-cv-1457-CMH-TCB in the United States District Court for the Eastern District of Virginia, Alexandria Division, 46 pages.Applicant
- Goldberg et al., “Computing the Shortest Path: A* Search Meets Graph Theory,” Proc. of the 16th Annual ACM-SIAM Sym. on Discrete Algorithms, Jan. 23-25, 2005. Vancouver, BC.Applicant
- Goldberg et al., “Computing the Shortest Path: A* Search Meets Graph Theory,” Microsoft Research, Technical Report MSR-TR-2004 Mar. 24, 2003.Applicant
- Golisch, F., Navigation and Telematics in Japan, International Symposium on Car Navigation Systems, May 21, 1997, 20 pages, held in Barcelona, Spain.Applicant
- GM Exhibits Prototype of TravTek Test Vehicle, Inside IVHS, Oct. 28, 1991, V. 1, No. 21, 2 pages.Applicant
- Gueziec, Andre, “3D Traffic Visualization in Real Time,” ACM Siggraph Technical Sketches, Conference Abstracts and Applications, p. 144, Los Angeles, CA, Aug. 2001.Applicant
- Gueziec, A., “Architecture of a System for Producing Animated Traffic Reports,” Mar. 30, 2011, 42 pages.Applicant
- Handley, S. et al., “Learning to Predict the Duration of an Automobile Trip,” Proceedings of the Fourth International Conference on Knowledge Discovery and Data Mining, 1998, 5 pages, AAAI Press, New York, NY, USA.Applicant
- Hankey, et al., “In-Vehicle Information Systems Behavioral Model and Design Support: Final Report,” Feb. 16, 2000, Publication No. 00-135, Research, Development, and Technology, Turner-Fairbank Highway Research Center, McLean, Virginia.Applicant
- Hirata et al., “The Development of a New Multi-AV System Incorporating an On-Board Navigation Function,” International Congress and Exposition, Mar. 1-5, 1993, pp. 1-12, held in Detroit, MI, SAE International, Warrendale, PA, USA.Applicant
- Hoffmann, G. et al., Travel Times as a Basic Part of the LISB Guidance Strategy, Third International Conference on Road Traffic Control, May 1-3, 1990, pp. 6-10, London, U.K.Applicant
- Hoffmann, T., “2005 Acura RL Prototype Preview,” Auto123.com, 4 pages.Applicant
- Hu, Z. et al., “Real-time Data Fusion on Tracking Camera Pose for Direct Visual Guidance,” IEEE Vehicles Symposium, Jun. 14-17, 2004, pp. 842-847, held in Parma, Italy.Applicant
- Hulse, M.C. et al., “Development of Human Factors Guidelines for Advanced Traveler Information Systems and Commercial Vehicle Operations: Identification of the Strengths and Weaknesses of Alternative Information Display Formats,” Publication No. FHWA-RD-96-142, Oct. 16, 1998, 187 pages, Office of Safety and Traffic Operation R&D, Federal Highway Administration, USA.Applicant
- Initial Expert Report of Roy Summer dated Jun. 16, 2011 in Triangle Software, LLC v. Garmin International Inc. et al., in the United States District Court for the Eastern District of Virginia, Alexandria Division, Case No. 1:10-cv-1457-CMH-TCB, 289 pages.Applicant
- Initial Expert Report of William R. Michalson, Ph.D. dated Jun. 17, 2011 in Triangle Software, LLC v. Garmin International Inc. et al., in the United States District Court for the Eastern District of Virginia, Alexandria Division, Case No. 1:10-cv-1457-CMH-TCB, 198 pages.Applicant
- Inman, V.W., et al., “TravTek Global Evaluation and Executive Summary,” Publication No. FHWA-RD-96-031, Mar. 1996, 104 pages, U.S. Department of Transportation, McLean, VA, USA.Applicant
- Inman, V.W., et al., “TravTek Evaluation Rental and Local User Study,” Publication No. FHWA-RD-96-028, Mar. 1996, 110 pages, U.S. Department of Transportation, McLean, VA, USA.Applicant
- Jiang, G., “Travel-Time Prediction for Urban Arterial Road: A Case on China,” Proceedings Intelligent Transportation Systems, Oct. 12-15, 2003, pp. 255-260, IEEE, New York, NY, USA.Applicant
- Karabassi, A. et al., “Vehicle Route Prediction and Time and Arrival Estimation Techniques for Improved Transportation System Management,” in Proceedings of the Intelligent Vehicles Symposium, 2003, pp. 511-516, IEEE, New York, NY, USA.Applicant
- Koller, D. et al., “Virtual GIS: A Real-Time 3D Geographic Information System,” Proceedings of the 6th IEEE Visualization Conference (Visualization 95) 1995, pp. 94-100, IEEE, New York, NY, USA.Applicant
- Kopitz et al., Table of Contents, Chapter 6, Traffic Information Services, and Chapter 7, Intelligent Transport Systems and RDS-TMC in RDS: The Radio Data System, 1992, Cover p.-XV, pp. 107-167, Back Cover page, Artech House Publishers, Boston, USA and London, Great Britain.Applicant
- Krage, M.K., “The TravTek Driver Information System,” Vehicle Navigation & Information Systems Conference Proceedings (VNIS'91), P-253, Part 1, Oct. 1991, pp. 739-748, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Ladner, R. et al., “3D Mapping of Interactive Synthetic Environment,” Computing Practices, Mar. 2000, pp. 33-39, IEEE, New York, NY, USA.Applicant
- Levinson, D., “Assessing the Benefits and Costs of Intelligent Transportation Systems: The Value of Advanced Traveler Information System,” Publication UCB-ITS-PRR-99-20, California Path Program, Jul. 1999, Institute of Transportation Studies, University of California, Berkeley, CA, USA.Applicant
- Lowenau, J., “Final Map Actualisation Requirements,” Version 1.1, ActMAP Consortium, Sep. 30, 2004, 111 pages.Applicant
- Meridian Series of GPS Receivers User Manual, Magellan, 2002, 106 pages, Thales Navigation, Inc., San Dimas, CA, USA.Applicant
- Ness, M., “A Prototype Low Cost In-Vehicle Navigation System,” IEEE-IEE Vehicle Navigation & Information Systems Conference (VNIS), 1993, pp. 56-59, New York, NY, USA.Applicant
- N'FIT XANAVI, unknown date, 94 pages, Japana.Applicant
- Nintendo Wii Operations Manual Systems Setup. 2009.Applicant
- Nissan Automobile Navigation System User Manual, [date unknown], 163 pages.Applicant
- Noonan, J., “Intelligent Transportation Systems Field Operational Test Cross-Cutting Study Advanced Traveler Information Systems,” Sep. 1998, 27 pages, U.S. Department of Transportation, McLean, VA, USA.Applicant
- Odagaki et al., Automobile Navigation System with Multi-Source Guide Information, International Congress & Exposition, Feb. 24-28, 1992, pp. 97-105. SAE International, Warrendale, PA, USA.Applicant
- Panasonic Portable Navigation System User Manual for Products KX-GT30, KX-GT30X, and KX-GT30Z, Cover page, pp. 1-5, 132-147, End pages, Matsushita Denki Sangyo K.K., Fukuoka City, Japan [Date Unknown].Applicant
- Preliminary Invalidity Contentions of Defendant TomTom, Inc., Certificate of Service and Exhibit a filed May 16, 2011 in Triangle Software, LLC. V. Garmin International, Inc. et al., Case No. 1: 10-cv-1457-CMH-TCB in the United States District Court for the Eastern District of Virginia, Alexandria Division, 354 pages.Applicant
- Raper, J.F., “Three-Dimensional GIS,” in Geographical Information Systems: Principles and Applications, 1991, vol. 1, Chapter 20, 21 pages.Applicant
- “References Manual for the Magellan RoadMate 500/700.” 2003, 65 pages, Thales Navigation, Inc., San Dimas, CA, USA.Applicant
- Riiett, L.R., “Simulating the TravTek Route Guidance Logic Using the Integration Traffic Model,” Vehicle Navigation & Information System, P-253, Part 2, Oct. 1991, pp. 775-787, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Rillings, J.H., “Advanced Driver Information Systems,” IEEE Transactions on Vehicular Technology, Feb. 1991, vol. 40, No. 1, pp. 31-40, IEEE, New York, NY, USA.Applicant
- Rillings, J.H., “TravTek,” Vehicle Navigation & Information System Conference Proceedings (VNIS'91), P-253, Part 2, Oct. 1991, pp. 729-737, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Rockwell, Mark, “Telematics Speed Zone Ahead,” Wireless Week, Jun. 15, 2004, Reed Business Information, http://www.wirelessweek.com.Applicant
- Rupert, R.L., “The TravTek Traffic Management Center and Traffic Information Network,” Vehicle Navigation & Information System Conference Proceedings (VNIS'91), P-253, Part 1, Oct. 1991, pp. 757-761, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Schofer, J.L., “Behavioral Issues in the Design and Evaluation of Advanced Traveler Information Systems,” Transportation Research Part C 1, 1993, pp. 107-117, Pergamon Press Ltd., Elsevier Science Ltd.Applicant
- Schulz, W., “Traffic Management Improvement by Integrating Modem Communication Systems,” IEEE Communications Magazine, Oct. 1996, pp. 56-60, New York, NY, USA.Applicant
- Shepard, I.D.H., “Information Integration and GIS,” in Geographical Information Systems: Principles and Applications, 1991, vol. 1, pp. Cover page, 337-360, end page.Applicant
- Sirius Satellite Radio: Traffic Development Kit Start Up Guide, Sep. 27, 2005, Version 00.00.01, NY, New York, 14 pages.Applicant
- Slothhower, D., “Sketches & Applications,” SIGGRAPH 2001, pp. 138-144, Stanford University.Applicant
- Sumner, R., “Data Fusion in Pathfinder and TravTek,” Part 1, Vehicle Navigation & Information Systems Conference Proceedings (VNIS'91), Oct. 1991, Cover & Title page, pp. 71-75.Applicant
- Supplemental Expert Report of William R. Michalson, Ph.D. Regarding Invalidity of the Patents-in-Suit dated Jul. 5, 2011 in Triangle Software, LLC v. Garmin International Inc. et al., in the United States District Court for the Eastern District of Virginia, Alexandria Division, Case No. 1:10-cv-1457-CMH-TCB, 23 pages.Applicant
- Tamuara et al., “Toward Realization of VICS—Vehicle Information and Communications System,” IEEE-IEE Vehicle Navigation & Information Systems Conference (VNIS'93), 1993, ppg. 72-77, held in Ottawa, Canada.Applicant
- Taylor, K.B., “TravTek-Information and Services Center,” Vehicle Navigation & Information System Conference Proceedings (VNIS'91), P-253, Part 2, Oct. 1991, pp. 763-774, Soc. of Automotive Engineers, Inc., Warrendale, PA, USA.Applicant
- Texas Transportation Institute, “2002 Urban Mobility Study: 220 Mobility Issues and Measures: The Effects of Incidents—Crashes and Vehicle Breakdowns” (2002).Applicant
- “The Challenge of VICS: The Dialog Between the Car and Road has Begun,” Oct. 1, 1996, pp. 19-63, The Road Traffic Information Communication System Centre (VICS Centre), Tokyo, Japan.Applicant
- Thompson, S.M., “Exploiting Telecommunications to Delivery Real Time Transport Information,” Road Transport Information and Control, Conf. Publication No. 454, Apr. 21-23, 1998, pp. 59-63, IEE, U.K.Applicant
- Tonjes, R., “3D Reconstruction of Objects from Ariel Images Using a GIS,” presented at ISPRS Workshops on “Theoretical and Practical Aspects of Surface Reconstructions and 3-D Object Extraction” Sep. 9-11, 1997, 8 pages, held in Haifa, Israel.Applicant
- “TRAVTEK Information and Services Center Policy/Procedures Manual,” Feb. 1992, 133 pages, U.S. Department of Transportation, McLean, VA, USA.Applicant
- Truett, R., “Car Navigation System May Live on After Test,” The Orlando Sentinel, Feb. 17, 1993, p. 3 pages.Applicant
- U.S. Dept. of Transportation, Closing the Data Gap: Guidelines for Quality Advanced Traveler Information System (ATIS) Data, Version 1.0, Sep. 2000, 41 pages.Applicant
- User Guide of Tom Tom ONE; 2006.Applicant
- Vollmer, R., “Navigation Systems—Intelligent Co-Drivers with Knowledge of Road and Tourist Information,” Navigation and Intelligent Transportation Systems, Automotive Electronics Series, Society of Automotive Engineers, 1998, pp. Cover page, Table of Contents, pp. 9-17.Applicant
- Volkswagen Group of America, Inc.'s Answer and Counterclaim.Applicant
- Watanabe, M. et al., “Development and Evaluation of a Car Navigation System Providing a Bird's-Eye View Map Display,” Technical Paper No. 961007, Feb. 1, 1996, pp. 11-18, SAE International.Applicant
- Wischhof, L. et al., “SOTIS—A Self-Organizing Traffic Information System,” Proceedings of the 57th IEEE Vehicular Technology Conference (VTC—03), 2003, pp. 2442-2446, New York, NY, USA.Applicant
- WSI, “TrueView Interactive Training Manual, Showfx Student Guide,” Print Date: Sep. 2004, Document Version: 4.3x. Link: http://apollo.lsc.vsc.edu/intranet/WSI—Showfx/training/970-TVSK-SG-43.pdf.Applicant
- XM Radio Introduces Satellite Update Service for Vehicle Navigation, Apr. 8, 2004, 2 pages.Applicant
- Yim et al., TravInfo. Field Operational Test Evaluation “Evaluation of TravInfo Field Operation Test” Apr. 25, 2000.Applicant
- Yim et al., “TravInfo Field Operational Test Evaluation: Information Service Providers Customer Survey” (2000).Applicant
- Yokouchi, K., “Car-Navigation Systems,” Mitsubishi Electr. Adv. Technical Reports, 2000, vol. 91, pp. 10-14, Japan.Applicant
- You, J. et al., “Development and Evaluation of a Hybrid Travel Time Forecasting Model,” Transportation Research Parc C 9, 2000, pp. 231-256, Pergamon Press Ltd., Elsevier Science Ltd., U.K.Applicant
- Zhao, Y., “Vehicle Location and Navigation Systems,” 1997, 370 pages, Arthech House, Inc., Norwood, MA, USA.Applicant
- Zhu, C. et al. “3D Terrain Visualization for Web GIS,” Center for Advance Media Technology, Nanyang Technological University, Singapore, 2003, 8 pages.Applicant
- PCT Application No. PCT/US2004/23884, Search Report and Written Opinion mailed Jun. 17, 2005.Applicant
- PCT Application No. PCT/US2011/48680, Search Report and Written Opinion mailed Feb. 7, 2012.Applicant
- PCT Application No. PCT/US2011/51647, Search Report and Written Opinion mailed Feb. 2, 2012.Applicant
- PCT Application No. PCT/US2011/60663, Search Report and Written Opinion mailed May 31, 2012.Applicant
- PCT Application No. PCT/US2012/38702, Search Report and Written Opinion mailed Aug. 24, 2012.Applicant
- EP Patent Application No. 11 825 897.9, Communication mailed May 3, 2013.Applicant
- U.S. Appl. No. 10/379,967, Final Office Action mailed May 11, 2005.Applicant
- U.S. Appl. No. 10/379,967, Office Action mailed Sep. 20, 2004.Applicant
- U.S. Appl. No. 10/897,550, Office Action mailed Jun. 12, 2009.Applicant
- U.S. Appl. No. 10/897,550, Office Action mailed Jan. 21, 2009.Applicant
- U.S. Appl. No. 10/897,550, Office Action mailed Aug. 1, 2008.Applicant
- U.S. Appl. No. 10/897,550, Office Action mailed Oct. 3, 2007.Applicant
- U.S. Appl. No. 11/509,954, Office Action mailed Nov. 23, 2007.Applicant
- U.S. Appl. No. 11/751,628, Office Action mailed Jan. 29, 2009.Applicant
- U.S. Appl. No. 12/283,748, Office Action mailed Aug. 20, 2009.Applicant
- U.S. Appl. No. 12/283,748, Office Action mailed Mar. 11, 2009.Applicant
- U.S. Appl. No. 12/398,120, Final Office Action mailed Mar. 26, 2013.Applicant
- U.S. Appl. No. 12/398,120, Office Action mailed Nov. 14, 2012.Applicant
- U.S. Appl. No. 12/398,120, Final Office Action mailed Apr. 12, 2012.Applicant
- U.S. Appl. No. 12/398,120, Office Action mailed Nov. 15, 2011.Applicant
- U.S. Appl. No. 12/763,199, Final Office Action mailed Nov. 1, 2010.Applicant
- U.S. Appl. No. 12/763,199, Office Action mailed Aug. 5, 2010.Applicant
- U.S. Appl. No. 12/860,700, Office Action mailed Feb. 26, 2013.Applicant
- U.S. Appl. No. 12/881,690, Office Action mailed Apr. 22, 2013.Applicant
- U.S. Appl. No. 12/967,045, Final Office Action mailed Jun. 27, 2012.Applicant
- U.S. Appl. No. 12/967,045, Office Action mailed Jul. 18, 2011.Applicant
- U.S. Appl. No. 13/296,108, Office Action mailed May 9, 2013.Applicant
- U.S. Appl. No. 13/316,250, Office Action mailed Jan. 18, 2013.Applicant
- U.S. Appl. No. 13/561,269, Office Action mailed Dec. 13, 2012.Applicant
- U.S. Appl. No. 13/561,327, Office Action mailed Oct. 26, 2012.Applicant