There has been an increased use of handheld or dashboard-mounted travel guidance systems, for example, Global Positioning System (GPS)-embedded personal digital assistants (PDAs) and smart phones. In addition, there has been an increase in applications such as route planners, hot route finders, traffic flow analyzers, and geographical social network applications that use GPS data to achieve a better quality of service.
Typically, a GPS trajectory consists of a sequence of positions with latitude, longitude, instant speed, direction and timestamp information. However, this data can often be incorrect as a result of measurement errors caused by the limitations of typical GPS devices, as well as sampling errors caused by the sampling rate. Therefore, an observed GPS position often needs to be aligned with a road network on a digital map. This process is referred to as map-matching. The difficulty of map-matching can greatly differ depending on GPS accuracy and the sampling frequency, for example, map-matching is easier with data that is gathered frequently, and with a high degree of accuracy, than with data that is inaccurate or that is gathered less frequently.
Existing map-matching approaches generally employ an algorithm that maps sampled positions from a GPS trajectory onto vector road segments on a map. Such an approach typically considers sampled positions on a GPS trajectory while overlooking the speed and temporal data that may also be found in the GPS trajectory. These map-matching algorithms are typically most accurate when using data gathered at a high sampling rate. As sampling frequency decreases, measurement errors typically increase. However, while a high sampling rate results in increased accuracy, it also carries a greater computational cost.
Map-matching for low-sampling-rate GPS data is challenging because, as the sampling rate decreases, the interval between two neighboring positions in a trajectory increases, and less information is available to deduce the precise location of an object. A more effective approach for map-matching for low-sampling rate GPS trajectories utilizes temporal and speed data from the GPS trajectory to augment the spatial data.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
In view of the above, this disclosure describes an exemplary method, user-interface, and computer-readable media for implementing map-matching for low-sampling rate GPS trajectories.
In an exemplary implementation, a mapping module receives a GPS trajectory that represents a path traveled by a user. For example, as the user is driving through town, a GPS device automatically records data at regular, predetermined time intervals. The GPS trajectory includes spatial data (e.g., one or more sampling points, latitude, longitude, and direction) and temporal data (e.g., speed and timestamp). A set of one or more candidate projection points surrounding each of the one or more sampling points of the trajectory is retrieved from a road network database, and one or more candidate road segments upon which the candidate projection points lie are determined. Spatial and temporal analyses are performed on the retrieved set of one or more candidate projection points. A candidate graph is constructed based upon the results of the spatial analysis and the temporal analysis, and the candidate graph is evaluated to determine the set of candidate projection points that best matches the one or more sampling points received from the user.
Map-matching that is performed based on the GPS trajectory may also be used to calculate a recommended route based on user-submitted data that identifies additional locations to which the user would like to travel. For example, a user interface may be provided through which a user submits one or more locations to which the user would like to travel. Those points are appended to the existing GPS trajectory, and the mapping module calculates a route to the user-submitted locations based, at least in part, on the previously collected GPS trajectory. The calculated route is then presented to the user.
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
Map-matching for low-sampling rate global positioning system (GPS) trajectories is described. More specifically, an exemplary map-matching algorithm utilizes both a spatial analysis and a temporal analysis to analyze a submitted set of sampling points to determine a best match trajectory, or route, which is presented to the user.
The network(s) 104 represent any type of communications network(s), including, but not limited to, wire-based networks (e.g., cable), wireless networks (e.g., cellular, satellite), cellular telecommunications network(s), and IP-based telecommunications network(s) (e.g., Voice over Internet Protocol networks). The network(s) 104 may also include traditional landline or a public switched telephone network (PSTN), or combinations of the foregoing (e.g., Unlicensed Mobile Access or UMA networks, circuit-switched telephone networks or IP-based packet-switch networks).
The computing device 102 accesses a global positioning system (GPS) that conveniently logs navigation and positioning information as the device moves with the user 106. In an exemplary implementation, a GPS 108 in the computing device 102 starts recording location data upon detecting a satellite signal. For example, a GPS receiver collects the location data, p1, p2, and p3 along a GPS trajectory 110 based on pre-determined rate. In the exemplary implementation, the GPS 108 in the computing device 102 uses a low sampling rate to minimize computations and network bandwidth usage. For example, the GPS 108 may record data every 2 minutes, every 5 minutes, or the like. The GPS 108 continues to collect the location data as long as there is a satellite signal detected on the network 104.
The user 106 enters a starting location and a desired destination through a user interface of the computing device 102. The user-submitted starting location and desired destination, along with the data collected by the GPS 108, is sent over network 104 to servers 112. Exemplary servers 112 include a map-matching module 114 that analyzes the data collected by the GPS to determine a preferred route, for example, the shortest and most direct route from the starting location to the user-submitted desired destination. The map-matching module 114 determines the preferred route by preparing candidate projection points, performing spatial and temporal analysis, and matching the results. The determined route is then stored and/or presented visually to the user. Alternatively, the data collected by the GPS may be used to determine a route consisting entirely of highways, a route consisting entirely of service roads, or the like. The map-matching module 114 provides the result back to the user via the computing device 102 through a network service provider, a context-aware computing service, email, text message, a pop up, and the like.
When executed on the processor 202, the operating system 208 and UI module 210 collectively facilitate presentation of a user interface on a display of the computing device 102. GPS 108 may be implemented as a component of a web browser or a search engine, or may be implemented as an application in the computing device 102. As described above, the GPS 108 collects location data (e.g., GPS trajectories) over time as the computing device physically moves from one location to another. Content storage 212 provides local storage of sampling points and/or data received from map-matching module 114. For example, the sampling points and/or data received from the map-matching module may be stored in GPS log 214.
The communication interfaces 204 may include, without limitation, a wide area network (WAN) interface, a local area network interface (e.g., WiFi), a personal area network (e.g., Bluetooth) interface, and/or any other suitable communication interfaces to allow the computing device 102 to communicate over the network(s) 104.
The computing device 102, as described above, may be implemented in various types of system or networks. For example, the computing device may be a part of, without limitation, a client-server system, a peer-to-peer computer network, a distributed network, an enterprise architecture, a local area network, a wide area network, a virtual private network, a storage area network, and the like.
An operating system 310, and a map-matching module 114 are maintained in the memory 304 and executed on the processor 302. In an exemplary implementation, the map-matching module 114 includes a road network database 312 that includes, without limitation information pertaining to at least geographical locations within roadway system(s). For example, road network database 312 may contain a mapping system of the roadways of the greater Seattle area including, service roads, highways, and any other roads available to the user 106. Map-matching module 114 may also include databases of other types of information, including for example, rivers, railways, airports, restaurants, hotels, etc.
Communication interfaces 314, allow the processor 302 to communicate with the computing device 102, other network servers, network storage, and/or other devices over the network(s) 104, and content storage 316. Content storage 316 may store the GPS data collected by the GPS 108 and sent to the server 112. For example, the GPS data may be stored in GPS log 318. Although not shown in
Any memory described herein may include volatile memory (such as RAM), nonvolatile memory, removable memory, and/or non-removable memory, implemented in any method or technology for storage of information, such as, computer-readable instructions, data structures, applications, program modules, emails, and/or other content. Also, any of the processors described herein may include onboard memory in addition to or instead of the memory shown in the figures. The memory may include storage media such as, but not limited to, random access memory (RAM), read only memory (ROM), flash memory, optical storage, magnetic disk storage or other storage devices, or any other medium which can be used to store the desired information and which can be accessed by the respective systems and devices.
The process 400 includes, without limitation, preparation of candidate projection points 402, spatial and temporal analyses 404, and result matching, storage, and visualization 406.
To prepare the candidate projection points, the map-matching module obtains data from GPS logs 408(1), 408(2), . . . , 408(N) and the road network database 312. A candidate computation 410 is then performed, the results of which are used to determine candidate sets 412. GPS logs 408 may correspond, for example, to GPS log 214 or GPS log 318 shown in
Spatial and temporal analyses 404 are then performed. For example, a spatial analysis 414 and a temporal analysis 416 are performed on the candidate sets 412, resulting in a candidate graph 418.
The process concludes with result matching, storage, and visualization 406. For example, a best path search 420 is performed on the candidate graph 418 to determine a matching result 422. The matching result, or the preferred route, is presented to the user via a user interface 424.
Specific portions of process 400 are described below in greater detail with reference to
Exemplary candidate computation 410 is determined by plotting one or more sampling points, pi, along a determined candidate road segment. For each sampling point pi, a circle 502 encompasses a set of candidate road segments supplied by road network database 312 within a given radius. In the example illustrated in
Similarly, the map-matching module 114 also identifies candidate projection points ci1 and ci2 along candidate road segments ri1 and ri2 respectively, within the circle 502(2) encompassing sampling point pi; and identifies candidate projection points ci+11 and ci+11 corresponding to sampling point pi+1, where sampling point pi+1 is encompassed by circle 502(3).
The result of the candidate computation 410 is, for each sampling point, a set of candidate projection points. Referring to the example shown in
In an exemplary implementation, one or more indexing techniques may be used to expedite the generation of a set of candidate projection points. For example, indexing techniques that may be used include, without limitation, a space-partition based indexing method, such as the grid-based spatial index and the quad tree indexing structure, or a data driven indexing structure such as an R-tree indexing structure.
After determining the set of candidate projection points, as described above, the map-matching algorithm performs a spatial analysis 414 and a temporal analysis 416 to identify a particular candidate projection point within each set of candidate projection points that best matches the corresponding sampling point.
Exemplary spatial analysis 414 utilizes geometric and topological information from the road network database 312 to evaluate each of the determined candidate projection points. In one implementation, spatial analysis 414 includes two components, an observation probability component and a transmission probability component.
The observation probability component represents the likelihood that a trajectory, or route, supplied from the map-matching module 114 to the user 106 is the best route based upon the distance between two candidate points, such as candidate points ci1 and ci2. However, because no additional information is taken into account the result typically includes an error.
The error in the observation probability is calculated as a normal distribution N (μ, σ2) using the distance between sampling point pi and candidate point cij. The normal distribution demonstrates how likely the trajectory supplied from the map-matching module 114 would have been if the user 106 had actually been on a road with a location cij and without considering any previous points. Accordingly, the observation probability is calculated according to:
where x is the distance between the sampling point pi and its corresponding candidate point cij, represented as xij: =dist(cij, pi). In one implementation, a zero-mean normal distribution with a standard deviation of about 66 feet (or about 20 meters) may be used. Alternatively, any normal distribution with a suitable standard deviation may be used.
It is assumed that a typical user 106 would desire the shortest and most direct route to a destination. Therefore, in one implementation, Equation (1) corresponds to a shortest path computation. A variety of shortest path algorithms may be used to compute the shortest path.
{ } // S will ultimately contains vertices of final shortest-path
V[G]
EXTRACT_MIN(Q) // Pull out new vertex
S ∪ {u}
where G represents a candidate graph, s represents a source vertex or source sampling point, Q is a set of candidate projection points, and a vertex represents sampling points other than the source sampling point. A tree T is built that spans all reachable vertices from a point S. Vertices are added to the tree T in order of the distance between the source sampling point and the remaining sampling points. For example, a first distance S, then a vertex closest to S, and so on.
As described above, an exemplary spatial analysis 414 has an observation probability component and a transmission probability component. The example Dijkstra's algorithm described above results in an observation probability.
The transmission probability for candidate points ci−1t to cis for two neighboring sampling points pi−1 and pi respectively, is the likelihood that the “true” path from pi−1 and pi follows the shortest path from ci−1t to cis. Such a true path is represented by:
where di−1→I=dist(pi, pi−1) is the Euclidean distance between pi and pi−1, and w(i−1,t)→(I,s) is the length of the shortest path from ci−1t to cis.
The product of the observation probability and the transmission probability reflect the likelihood that the user 106 will move from ci−1t to cis. Combining the observation probability and the transmission probability, an exemplary spatial analysis function is:
Fs(ci−1t→cis)=N(cis)*V(ci−1t→cis), 2≤i≤n Equation (3)
where ci−1t and cis may be any two candidate points for two neighboring sampling points pi−1 and pi. The spatial analysis 414 for a candidate pi will differ depending upon the previous candidate point.
As previously discussed, map-matching based on spatial analysis alone, typically leads to poor accuracy when determining a best trajectory or route. For example, as illustrated in
Analyzing speed information in addition to the location information can increase the accuracy of the map-matching. In the example shown in
Therefore, an exemplary temporal analysis 416 is based upon an average speed between two candidate points ci−11 and cis corresponding to two neighboring sampling points, pi−1 and pi, respectively. The average speed
where iu=e′u*l is the length of road segment e′u, and Δti−1→i=pi*t−pi−1*t is the time interval between the two sampling points pi and pi−1. In an exemplary implementation, each road segment e′u is also associated with a typical speed value e′u*υ, and a cosine distance may be used to measure the similarity between the actual average speed from ci−11 to cis and the speed constraints (e.g., known speed limits) of the path. Alternatively, any suitable measurement may be used to determine the similarity. Considering a vector k with elements of the same value
Combining Equation (3) and Equation (5), as set forth above, the spatial-temporal (ST) function ci−11→cis is:
F(ci−1t→cis)=Fs(ci−1t→cis)*Ft(ci−1t→cis), 2≤i≤n Equation (6)
Referring back to the process illustrated in
T: p1→p2→pn, where V′T is a set of candidate points corresponding to each of a set of received sampling points, and E′T is a set of edges representing the shortest paths between any two neighboring candidate points.
The candidate path search 420 may include c1s1→c2s2→ . . . cnsn, for example, 802→804→806.
To determine which candidate path sequence is a best match trajectory or route 422 corresponding to the sample points input by the user 106 or collected by the GPS 108, a score for each of the candidate path sequences is calculated. For example, scores for candidate path sequences 808(1) and 808(2) may be calculated and compared to determine which of the two candidate path sequences has the highest score, and is therefore the best match for the sampling points along the trajectory. In an exemplary implementation, the score for such a candidate sequence path is given by:
F(Pc)=Σi=2nF(ci−1s
The best-match path P for a trajectory T may be selected using:
P=arg maxP
Algorithm 1, set forth below, outlines an exemplary algorithm for a spatial and temporal analysis 404 using the map-matching module 114. Algorithm 1 includes the terms and equations described above in
Algorithm 2, set forth below, outlines an exemplary algorithm for result matching, storage and visualization 406 based upon the results of Algorithm 1. Algorithm 2 determines the trajectory or route most likely to correspond to the received sampling points.
The exemplary ST-matching strategy represented by Algorithm 1 and Algorithm 2 is based upon a global algorithm, meaning the best path sequence is computed based upon an overall score for the entire trajectory of the candidate path sequence. However, if a trajectory has too many sampling points (i.e., n is very large) map-matching module 114 may use a local algorithm, based on a subset of the sampling points, to determine a matching result 422.
At block 1010 a candidate graph may be constructed. For example, a candidate graph 1106, may be created corresponding to those measurements set forth in Tables 1 and 2, 1102 and 1104 of
c11→c22→c32.
Although map-matching for low-sampling rate GPS trajectories has been described in language specific to structural features and/or methods, it is to be understood that the subject of the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations.
This application is a continuation of U.S. application Ser. No. 12/712,857, filed Feb. 25, 2010, now U.S. Pat. No. 10,288,433, issued May 14, 2019, and titled “MAP-MATCHING FOR LOW-SAMPLING-RATE GPS TRAJECTORIES,” the disclosure of which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5428546 | Shah | Jun 1995 | A |
5802492 | DeLorme | Sep 1998 | A |
5845227 | Peterson | Dec 1998 | A |
5904727 | Prabhakaran | May 1999 | A |
6023241 | Clapper | Feb 2000 | A |
6091359 | Geier | Jul 2000 | A |
6091956 | Hollenberg | Jul 2000 | A |
6122628 | Castelli | Sep 2000 | A |
6128279 | O'Neil | Oct 2000 | A |
6219662 | Fuh | Apr 2001 | B1 |
6243647 | Berstis | Jun 2001 | B1 |
6317684 | Roeseler | Nov 2001 | B1 |
6317686 | Ran | Nov 2001 | B1 |
6351775 | Yu | Feb 2002 | B1 |
6356838 | Paul | Mar 2002 | B1 |
6385539 | Wilson | May 2002 | B1 |
6411897 | Gaspard, II | Jun 2002 | B1 |
6424370 | Courtney | Jul 2002 | B1 |
6427122 | Lin | Jul 2002 | B1 |
6430547 | Busche | Aug 2002 | B1 |
6446121 | Shah | Sep 2002 | B1 |
6493650 | Rodgers | Dec 2002 | B1 |
6496814 | Busche | Dec 2002 | B1 |
6513026 | Horvitz | Jan 2003 | B1 |
6516272 | Lin | Feb 2003 | B2 |
6553310 | Lopke | Apr 2003 | B1 |
6584401 | Kirshenbaum | Jun 2003 | B2 |
6606643 | Emens | Aug 2003 | B1 |
6611881 | Gottfurcht | Aug 2003 | B1 |
6618507 | Divakaran | Sep 2003 | B1 |
6625319 | Krishnamachari | Sep 2003 | B1 |
6724733 | Schuba | Apr 2004 | B1 |
6732120 | Du | May 2004 | B1 |
6785704 | McCanne | Aug 2004 | B1 |
6816779 | Chen | Nov 2004 | B2 |
RE38724 | Peterson | Apr 2005 | E |
6919842 | Cho | Jul 2005 | B2 |
6925447 | McMenimen | Aug 2005 | B2 |
6965827 | Wolfson | Nov 2005 | B1 |
6970884 | Aggarwal | Nov 2005 | B2 |
6981055 | Ahuja | Dec 2005 | B1 |
7003555 | Jungck | Feb 2006 | B1 |
7013290 | Ananian | Mar 2006 | B2 |
7013517 | Kropf | Mar 2006 | B2 |
7031517 | Le | Apr 2006 | B1 |
7062562 | Baker | Jun 2006 | B1 |
7111061 | Leighton | Sep 2006 | B2 |
7136932 | Schneider | Nov 2006 | B1 |
7152118 | Anderson, IV | Dec 2006 | B2 |
7171415 | Kan | Jan 2007 | B2 |
7194552 | Schneider | Mar 2007 | B1 |
7197500 | Israni | Mar 2007 | B1 |
7203693 | Carlbom | Apr 2007 | B2 |
7219067 | McMullen | May 2007 | B1 |
7228359 | Monteiro | Jun 2007 | B1 |
7233861 | Van Buer | Jun 2007 | B2 |
7239962 | Plutowski | Jul 2007 | B2 |
7281199 | Nicol | Oct 2007 | B1 |
7284051 | Okano | Oct 2007 | B1 |
7349768 | Bruce | Mar 2008 | B2 |
7366726 | Bellamy | Apr 2008 | B2 |
7389283 | Adler | Jun 2008 | B2 |
7395250 | Aggarwal | Jul 2008 | B1 |
7428551 | Luo | Sep 2008 | B2 |
7437239 | Serre | Oct 2008 | B2 |
7437372 | Chen | Oct 2008 | B2 |
7447588 | Xu | Nov 2008 | B1 |
7479897 | Gertsch | Jan 2009 | B2 |
7493294 | Flinn | Feb 2009 | B2 |
7519690 | Barrow | Apr 2009 | B1 |
7548936 | Liu | Jun 2009 | B2 |
7561959 | Hopkins | Jul 2009 | B2 |
7574508 | Kommula | Aug 2009 | B1 |
7584159 | Chakrabarti | Sep 2009 | B1 |
7584301 | Joshi | Sep 2009 | B1 |
7603233 | Tashiro | Oct 2009 | B2 |
7610151 | Letchner | Oct 2009 | B2 |
7660441 | Chen | Feb 2010 | B2 |
7685422 | Isozaki | Mar 2010 | B2 |
7739040 | Horvitz | Jun 2010 | B2 |
7801842 | Dalton | Sep 2010 | B2 |
7840407 | Strope | Nov 2010 | B2 |
7904530 | Partridge | Mar 2011 | B2 |
7920965 | Nesbitt | Apr 2011 | B1 |
7930427 | Josefsberg | Apr 2011 | B2 |
7948400 | Horvitz | May 2011 | B2 |
7982635 | Seong | Jul 2011 | B2 |
7984006 | Price | Jul 2011 | B2 |
8060462 | Flinn | Nov 2011 | B2 |
8117138 | Apte | Feb 2012 | B2 |
8190649 | Bailly | May 2012 | B2 |
8219112 | Youssef | Jul 2012 | B1 |
8275649 | Zheng | Sep 2012 | B2 |
8458298 | Josefsberg | Jun 2013 | B2 |
8562439 | Shuman | Oct 2013 | B2 |
8577380 | Frias Martinez | Nov 2013 | B2 |
9009177 | Zheng | Apr 2015 | B2 |
10288433 | Zheng | May 2019 | B2 |
10621228 | Desmond | Apr 2020 | B2 |
10982961 | Sumizawa | Apr 2021 | B2 |
20010029425 | Myr | Oct 2001 | A1 |
20020032689 | Abbott, III | Mar 2002 | A1 |
20020038360 | Andrews | Mar 2002 | A1 |
20020044690 | Burgess | Apr 2002 | A1 |
20020052873 | Delgado | May 2002 | A1 |
20020062193 | Lin | May 2002 | A1 |
20020077749 | Doi | Jun 2002 | A1 |
20020128768 | Nakano | Sep 2002 | A1 |
20030053424 | Krishnamurthy | Mar 2003 | A1 |
20030063133 | Foote | Apr 2003 | A1 |
20030069893 | Kanai | Apr 2003 | A1 |
20030069968 | O'Neil | Apr 2003 | A1 |
20030139898 | Miller | Jul 2003 | A1 |
20030140040 | Schiller | Jul 2003 | A1 |
20030195810 | Raghupathy | Oct 2003 | A1 |
20030212689 | Chen | Nov 2003 | A1 |
20030217070 | Gotoh | Nov 2003 | A1 |
20030229697 | Borella | Dec 2003 | A1 |
20040039798 | Hotz | Feb 2004 | A1 |
20040064338 | Shiota | Apr 2004 | A1 |
20040073640 | Martin | Apr 2004 | A1 |
20040117358 | von Kaenel | Jun 2004 | A1 |
20040196161 | Bell | Oct 2004 | A1 |
20040198386 | Dupray | Oct 2004 | A1 |
20040217884 | Samadani | Nov 2004 | A1 |
20040220965 | Harville | Nov 2004 | A1 |
20040264465 | Dunk | Dec 2004 | A1 |
20050004830 | Rozell | Jan 2005 | A1 |
20050004903 | Tsuda | Jan 2005 | A1 |
20050031296 | Grosvenor | Feb 2005 | A1 |
20050075116 | Laird | Apr 2005 | A1 |
20050075119 | Sheha | Apr 2005 | A1 |
20050075782 | Torgunrud | Apr 2005 | A1 |
20050075784 | Gray | Apr 2005 | A1 |
20050080554 | Ono | Apr 2005 | A1 |
20050108261 | Glassy | May 2005 | A1 |
20050131889 | Bennett | Jun 2005 | A1 |
20050198286 | Xu | Sep 2005 | A1 |
20050203927 | Sull | Sep 2005 | A1 |
20050225678 | Zisserman | Oct 2005 | A1 |
20050231394 | Machii | Oct 2005 | A1 |
20050265317 | Reeves | Dec 2005 | A1 |
20050278371 | Funk | Dec 2005 | A1 |
20060020597 | Keating | Jan 2006 | A1 |
20060036630 | Gray | Feb 2006 | A1 |
20060042483 | Work | Mar 2006 | A1 |
20060085177 | Toyama | Apr 2006 | A1 |
20060085419 | Rosen | Apr 2006 | A1 |
20060090122 | Pyhalammi | Apr 2006 | A1 |
20060095540 | Anderson | May 2006 | A1 |
20060101377 | Toyama | May 2006 | A1 |
20060129675 | Zimmer | Jun 2006 | A1 |
20060143442 | Smith | Jun 2006 | A1 |
20060149464 | Chien | Jul 2006 | A1 |
20060155464 | Smartt | Jul 2006 | A1 |
20060156209 | Matsuura | Jul 2006 | A1 |
20060161560 | Khandelwal | Jul 2006 | A1 |
20060164238 | Karaoguz | Jul 2006 | A1 |
20060173838 | Garg | Aug 2006 | A1 |
20060178807 | Kato | Aug 2006 | A1 |
20060190602 | Canali | Aug 2006 | A1 |
20060200539 | Kappler | Sep 2006 | A1 |
20060212217 | Sheha | Sep 2006 | A1 |
20060224303 | Hayashi | Oct 2006 | A1 |
20060224773 | Degenaro | Oct 2006 | A1 |
20060247844 | Wang | Nov 2006 | A1 |
20060251292 | Gokturk | Nov 2006 | A1 |
20060265125 | Glaza | Nov 2006 | A1 |
20060266830 | Horozov | Nov 2006 | A1 |
20070005419 | Horvitz | Jan 2007 | A1 |
20070006098 | Krumm | Jan 2007 | A1 |
20070016663 | Weis | Jan 2007 | A1 |
20070038362 | Gueziec | Feb 2007 | A1 |
20070041393 | Westhead | Feb 2007 | A1 |
20070064633 | Fricke | Mar 2007 | A1 |
20070064715 | Lloyd | Mar 2007 | A1 |
20070088974 | Chandwani | Apr 2007 | A1 |
20070100776 | Shah | May 2007 | A1 |
20070118668 | McCarthy | May 2007 | A1 |
20070127833 | Singh | Jun 2007 | A1 |
20070168208 | Aikas | Jul 2007 | A1 |
20070203638 | Tooyama | Aug 2007 | A1 |
20070226004 | Harrison | Sep 2007 | A1 |
20080004789 | Horvitz | Jan 2008 | A1 |
20080004793 | Horvitz | Jan 2008 | A1 |
20080016051 | Schiller | Jan 2008 | A1 |
20080016233 | Schneider | Jan 2008 | A1 |
20080052303 | Adler | Feb 2008 | A1 |
20080059576 | Liu | Mar 2008 | A1 |
20080071465 | Chapman | Mar 2008 | A1 |
20080076451 | Sheha | Mar 2008 | A1 |
20080086574 | Raciborski | Apr 2008 | A1 |
20080098313 | Pollack | Apr 2008 | A1 |
20080201074 | Bleckman | Aug 2008 | A1 |
20080201102 | Boettcher | Aug 2008 | A1 |
20080214157 | Ramer | Sep 2008 | A1 |
20080215237 | Perry | Sep 2008 | A1 |
20080228396 | Machii | Sep 2008 | A1 |
20080228783 | Moffat | Sep 2008 | A1 |
20080235383 | Schneider | Sep 2008 | A1 |
20080268876 | Gelfand | Oct 2008 | A1 |
20080270019 | Anderson | Oct 2008 | A1 |
20080312822 | Lucas | Dec 2008 | A1 |
20080319648 | Poltorak | Dec 2008 | A1 |
20080319660 | Horvitz | Dec 2008 | A1 |
20080319974 | Ma | Dec 2008 | A1 |
20090005987 | Vengroff | Jan 2009 | A1 |
20090019181 | Fang | Jan 2009 | A1 |
20090063646 | Mitnick | Mar 2009 | A1 |
20090070035 | Van Buer | Mar 2009 | A1 |
20090083128 | Siegel | Mar 2009 | A1 |
20090083237 | Gelfand | Mar 2009 | A1 |
20090100018 | Roberts | Apr 2009 | A1 |
20090138188 | Kores | May 2009 | A1 |
20090164516 | Svendsen | Jun 2009 | A1 |
20090213844 | Hughston | Aug 2009 | A1 |
20090216435 | Zheng | Aug 2009 | A1 |
20090216704 | Zheng | Aug 2009 | A1 |
20090222581 | Josefsberg | Sep 2009 | A1 |
20090228198 | Goldberg | Sep 2009 | A1 |
20090239552 | Churchill | Sep 2009 | A1 |
20090282122 | Patel | Nov 2009 | A1 |
20090326802 | Johnson | Dec 2009 | A1 |
20100004997 | Mehta | Jan 2010 | A1 |
20100027527 | Higgins | Feb 2010 | A1 |
20100070171 | Barbeau | Mar 2010 | A1 |
20100076968 | Boyns | Mar 2010 | A1 |
20100082611 | Athsani | Apr 2010 | A1 |
20100111372 | Zheng | May 2010 | A1 |
20100153292 | Zheng | Jun 2010 | A1 |
20100279616 | Jin | Nov 2010 | A1 |
20100312461 | Haynie | Dec 2010 | A1 |
20110022299 | Feng | Jan 2011 | A1 |
20110029224 | Chapman | Feb 2011 | A1 |
20110130947 | Basir | Jun 2011 | A1 |
20110176000 | Budge | Jul 2011 | A1 |
20110184949 | Luo | Jul 2011 | A1 |
20110191011 | McBride | Aug 2011 | A1 |
20110191284 | Dalton | Aug 2011 | A1 |
20110208419 | Boss | Aug 2011 | A1 |
20110280453 | Chen | Nov 2011 | A1 |
20120030064 | Flinn | Feb 2012 | A1 |
20120256770 | Mitchell | Oct 2012 | A1 |
20130166188 | Zheng | Jun 2013 | A1 |
20140088791 | Alpert | Mar 2014 | A1 |
20170131110 | Zheng | May 2017 | A1 |
Number | Date | Country | |
---|---|---|---|
20190265047 A1 | Aug 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12712857 | Feb 2010 | US |
Child | 16406529 | US |