This disclosure generally relates to autonomous vehicle guidance systems, including methods for positioning an autonomous vehicle on a roadway along with destination-based navigation methods.
Autonomous vehicles typically utilize multiple data sources to determine their location, to identify other vehicles, to identify potential hazards, and to develop navigational routing strategies. These data sources can include a central map database that is preloaded with road locations and traffic rules corresponding to areas on the map. Data sources can also include a variety of sensors on the vehicle itself to provide real-time information relating to road conditions, other vehicles and transient hazards of the type not typically included on a central map database.
In many instances a mismatch can occur between the map information and the real-time information sensed by the vehicle. Various strategies have been proposed for dealing with such a mismatch. For example, U.S. Pat. No. 8,718,861 to Montemerlo et al. teaches detecting deviations between a detailed map and sensor data and alerting the driver to take manual control of the vehicle when the deviations exceed a threshold. U.S. Pub. No. 2014/0297093 to Murai et al. discloses a method of correcting an estimated position of the vehicle by detecting an error in the estimated position, in particular when a perceived mismatch exists between road location information from a map database and from vehicle sensors, and making adjustments to the estimated position.
A variety of data sources can be used for the central map database. For example, the Waze application provides navigational mapping for vehicles. Such navigational maps include transient information about travel conditions and hazards uploaded by individual users. Such maps can also extract location and speed information from computing devices located within the vehicle, such as a smart phone, and assess traffic congestion by comparing the speed of various vehicles to the posted speed limit for a designated section of roadway.
Strategies have also been proposed in which the autonomous vehicle will identify hazardous zones relative to other vehicles, such as blind spots. For example, U.S. Pat. No. 8,874,267 to Dolgov et al. discloses such a system. Strategies have also been developed for dealing with areas that are not detectable by the sensors on the vehicle. For example, the area behind a large truck will be mostly invisible to the sensors on an autonomous vehicle. U.S. Pat. No. 8,589,014 to Fairfield et al. teaches a method of calculating the size and shape of an area of sensor diminution caused by an obstruction and developing a new sensor field to adapt to the diminution.
Navigational strategies for autonomous vehicles typically include both a destination-based strategy and a position-based strategy. Destination strategies involve how to get from point ‘A’ to point ‘B’ on a map using known road location and travel rules. These involve determining a turn-by-turn path to direct the vehicle to the intended destination. Position strategies involve determining optimal locations for the vehicle (or alternatively, locations to avoid) relative to the road surface and to other vehicles. Changes to these strategies are generally made during the operation of the autonomous vehicle in response to changing circumstances, such as changes in the position of surrounding vehicles or changing traffic conditions that trigger a macro-level rerouting evaluation by the autonomous vehicle.
Position-based strategies have been developed that automatically detect key behaviors of surrounding vehicles. For example, U.S. Pat. No. 8,935,034 to Zhu et al. discloses a method for detecting when a surrounding vehicle has performed one of several pre-defined actions and altering the vehicle control strategy based on that action.
One of many challenges for controlling autonomous vehicles is managing interactions between autonomous vehicles and human-controlled vehicles in situations that are often handled by customs that are not easily translated into specific driving rules.
One aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; developing by one or more computing devices said first control strategy based at least in part on data contained on a first map; receiving by one or more computing devices sensor data from said vehicle corresponding to a first set of data contained on said first map; comparing said sensor data to said first set of data on said first map on a periodic basis; developing a first correlation rate between said sensor data and said first set of data on said first map; and adopting a second control strategy when said correlation rate drops below a predetermined value.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; receiving by one or more computing devices map data corresponding to a route of said vehicle; developing by one or more computing devices a lane selection strategy; receiving by one or more computing devices sensor data from said vehicle corresponding to objects in the vicinity of said vehicle; and changing said lane selection strategy based on changes to at least one of said sensor data and said map data.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; receiving by one or more computing devices sensor data from said vehicle corresponding to moving objects in the vicinity of said vehicle; receiving by one or more computing devices road condition data; determining by one or more computing devices undesirable locations for said vehicle relative to said moving objects; and wherein said step of determining undesirable locations for said vehicle is based at least in part on said road condition data.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; developing by one or more computing devices said first control strategy based at least in part on data contained on a first map, wherein said first map is simultaneously accessible by more than one vehicle; receiving by one or more computing devices sensor data from said vehicle corresponding to objects in the vicinity of said vehicle; and updating by said one or more computing devices said first map to include information about at least one of said objects.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle; activating a visible signal on said autonomous vehicle when said vehicle is being controlled by said one or more computing devices; and keeping said visible signal activated during the entire time that said vehicle is being controlled by said one or more computing devices.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; receiving by one or more computing devices sensor data corresponding to a first location; detecting a first moving object at said first location; changing said first control strategy based on said sensor data relating to said first moving object; and wherein said sensor data is obtained from a first sensor that is not a component of said autonomous vehicle.
Another aspect of the disclosure involves a method comprising controlling by one or more computing devices an autonomous vehicle in accordance with a first control strategy; approaching an intersection with said vehicle; receiving by one or more computing devices sensor data from said autonomous vehicle corresponding to objects in the vicinity of said vehicle; determining whether another vehicle is at said intersection based on said sensor data; determining by said one or more computing devices whether said other vehicle or said autonomous vehicle has priority to proceed through said intersection; and activating a yield signal to indicate to said other vehicle that said autonomous vehicle is yielding said intersection.
The foregoing brief description will be understood more completely from the following detailed description of the exemplary drawings, in which:
In an alternative embodiment, road features 330 and map elements 340 can relate to characteristics about the road surface such as the surface material (dirt, gravel, concrete, asphalt). In another alternative embodiment, road features 330 and map elements 340 can relate to transient conditions that apply to an area of the road such as traffic congestion or weather conditions (rain, snow, high winds).
In block 404, computer 170 selects a preferred road feature 330 (such as lane lines 332) and determines its respective location. In block 406, computer 170 determines the location of the selected instance of the road feature 330 and in block 408 compares this with the location of a corresponding map element 340. In block 410, computer 170 determines a correlation rate between the location of road feature 330 and corresponding map element 340. In block 412, computer 170 determines whether the correlation rate exceeds a predetermined value. If not, computer 170 adopts an alternative control strategy according to block 414 and reverts to block 404 to repeat the process described above. If the correlation rate is above the predetermined value, computer maintains the default control strategy according to block 416 and reverts to block 404 to repeat the process.
The correlation rate can be determined based on a wide variety of factors. For example, in reference to
In one embodiment of the disclosure, only one of the road features 330, such as lane lines 332, are used to determine the correlation between road features 330 and map elements 340. In other embodiments of the disclosure, the correlation rate is determined based on multiple instances of the road features 330 such as lane lines 332 and pavement edges 336. In yet another embodiment of the disclosure, the individual correlation between one type of road feature 330 and map element 340, such as lane lines 332, is weighted differently than the correlation between other road features 330 and map elements 340, such as pavement edges 334, when determining an overall correlation rate. This would apply in situations where the favored road feature (in this case, lane lines 332) is deemed a more reliable tool for verification of the location of vehicle 100 relative to road network 310.
In the first protocol, computer 170 relies on a secondary road feature 330 (such as pavement edges 336) for verification of the location of road network 310 relative to the vehicle 100 and for verification of the position of vehicle 100 within a lane on a roadway (such as the left lane 202 in highway 200, as shown in
The second protocol is triggered when the computer is unable to reliably use information about alternative road features 330 to verify the position of the vehicle 100. In this situation, computer 170 may use the position and trajectory of surrounding vehicles to verify the location of road network 310 and to establish the position of vehicle 100. If adjacent vehicles have a trajectory consistent with road network 310 on map 300, computer will operate on the assumption that other vehicles are within designated lanes in a roadway. If traffic density is not sufficiently dense (or is non-existent) such that computer 170 cannot reliably use it for lane verification, computer 170 will rely solely on GPS location relative to the road network 310 for navigational control purposes.
In either control strategy discussed above, computer 170 will rely on typical hazard avoidance protocols to deal with unexpected lane closures, accidents, road hazards, etc. Computer 170 will also take directional cues from surrounding vehicles in situations where the detected road surface does not correlate with road network 310 but surrounding vehicles are following the detected road surface, or in situations where the path along road network 310 is blocked by a detected hazard but surrounding traffic is following a path off of the road network and off of the detected road surface.
In accordance with another aspect of the disclosure, referring back to
Computer 170 communicates with navigational database 160 regarding the location of hazards 650, 670 detected by external sensor system 110. Navigational database 160 is simultaneously accessible by computer 170 and other computers in other vehicles and is updated with hazard-location information received by such computers to provide a real-time map of transient hazards. In a further embodiment, navigational database 160 sends a request to computer 170 to validate the location of hazards 650, 670 detected by another vehicle. Computer 170 uses external sensor system 110 to detect the presence or absence of hazards 650, 670 and sends a corresponding message to navigational database 160.
In accordance with another aspect of the disclosure,
Computer 170 adapts the lane selection strategy in real time based on information about surrounding vehicles 620. Computer 170 calculates a traffic density measurement based on the number and spacing of surrounding vehicles 620 in the vicinity of vehicle 100. Computer 170 also evaluates the number and complexity of potential lane change pathways in the vicinity of vehicle 100 to determine a freedom of movement factor for vehicle 100. Depending upon the traffic density measurement, the freedom of movement factor, or both, computer 170 evaluates whether to accelerate the lane change maneuver. For example, when traffic density is heavy and freedom of movement limited for vehicle 100, as shown in
In another aspect of the disclosure as shown in
One of the complexities of autonomous control of vehicle 100 arises in negotiating the right-of-way between vehicles. Driver-controlled vehicles often perceive ambiguity when following the rules for determining which vehicle has the right of way. For example, at a four-way stop two vehicles may each perceive that they arrived at an intersection first. Or one vehicle may believe that all vehicles arrived at the same time but another vehicle perceived that one of the vehicles was actually the first to arrive. These situations are often resolved by drivers giving a visual signal that they are yielding the right of way to another driver, such as with a hand wave. To handle this situation when vehicle 100 is under autonomous control, yield signal 790 is included on vehicle 100. Computer 170 follows a defined rule set for determining when to yield a right-of-way and activates yield signal 790 when it is waiting for the other vehicle(s) to proceed. Yield signal 790 can be a visual signal such as a light, an electronic signal (such as a radio-frequency signal) that can be detected by other vehicles, or a combination of both.
In accordance with another aspect of the disclosure,
The appended claims have been particularly shown and described with reference to the foregoing embodiments, which are merely illustrative of the best modes for carrying out the invention defined by the appended claims. It should be understood by those skilled in the art that various alternatives to the embodiments described herein may be employed in practicing the invention defined by the appended claims without departing from the spirit and scope of the invention as defined in claims. The embodiments should be understood to include all novel and non-obvious combinations of elements described herein, and claims may be presented in this or a later application to any novel and non-obvious combination of these elements. Moreover, the foregoing embodiments are illustrative, and no single feature or element is essential to all possible combinations that may be claimed in this or a later application.
With regard to the processes, methods, heuristics, etc. described herein, it should be understood that although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes described herein are provided for illustrating certain embodiments and should in no way be construed to limit the appended claims.
Accordingly, it is to be understood that the above description is intended to be illustrative and not restrictive. Many embodiments and applications other than the examples provided would be apparent to those of skill in the art upon reading the above description. The scope of the invention should be determined, not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the arts discussed herein, and that the disclosed systems and methods will be incorporated into such future embodiments. In sum, it should be understood that the invention is capable of modification and variation and is limited only by the following claims.
All terms used in the claims are intended to be given their broadest reasonable constructions and their ordinary meanings as understood by those skilled in the art unless an explicit indication to the contrary is made herein. In particular, use of the singular articles such as “a,” “the,” “said,” etc. should be read to recite one or more of the indicated elements unless a claim recites an explicit limitation to the contrary.
This application claims the benefit under 35 U.S.C. § 371 of published PCT Patent Application Number PCT/US2015/64282, filed 7 Dec. 2015 and published as WO2016/126321 on 11 Aug. 2016, which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 62/112,775, filed 6 Feb. 2015, the entire disclosure of which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5629690 | Knoll | May 1997 | A |
5995898 | Tuttle | Nov 1999 | A |
6442473 | Berstis et al. | Aug 2002 | B1 |
6526352 | Breed et al. | Feb 2003 | B1 |
6707391 | Monroe | Mar 2004 | B1 |
6747779 | Morin et al. | Jun 2004 | B1 |
6810321 | Cook | Oct 2004 | B1 |
6862537 | Skrbina et al. | Mar 2005 | B2 |
6864784 | Loeb | Mar 2005 | B1 |
6919917 | Janssen | Jul 2005 | B1 |
6959994 | Fujikawa et al. | Nov 2005 | B2 |
7075427 | Pace et al. | Jul 2006 | B1 |
7103460 | Breed | Sep 2006 | B1 |
7637631 | McDermott et al. | Dec 2009 | B2 |
8199046 | Nanami | Jun 2012 | B2 |
8478472 | Bageshwar et al. | Jul 2013 | B2 |
8480142 | Wuerfel | Jul 2013 | B2 |
8521352 | Ferguson et al. | Aug 2013 | B1 |
8589014 | Fairfield et al. | Nov 2013 | B2 |
8600606 | Nickolaou et al. | Dec 2013 | B2 |
8612135 | Montemerlo et al. | Dec 2013 | B1 |
8718861 | Montemerlo et al. | May 2014 | B1 |
8781669 | Teller et al. | Jul 2014 | B1 |
8818682 | Dolgov et al. | Aug 2014 | B1 |
8825259 | Ferguson et al. | Sep 2014 | B1 |
8825265 | Ferguson et al. | Sep 2014 | B1 |
8849494 | Herbach et al. | Sep 2014 | B1 |
8855849 | Ferguson et al. | Oct 2014 | B1 |
8874267 | Dolgov et al. | Oct 2014 | B1 |
8874305 | Dolgov et al. | Oct 2014 | B2 |
8874372 | Zhu et al. | Oct 2014 | B1 |
8880272 | Ferguson et al. | Nov 2014 | B1 |
8935034 | Zhu et al. | Jan 2015 | B1 |
9274526 | Murai et al. | Mar 2016 | B2 |
9377531 | Rostocki et al. | Jun 2016 | B2 |
9429440 | Harada | Aug 2016 | B2 |
9501058 | Mariet | Nov 2016 | B1 |
10083607 | Ginsberg et al. | Sep 2018 | B2 |
10209717 | Hazelton | Feb 2019 | B2 |
10311724 | Ginsberg et al. | Jun 2019 | B2 |
10525901 | Lewis et al. | Jan 2020 | B2 |
10678261 | Baldwin | Jun 2020 | B2 |
20050187701 | Baney | Aug 2005 | A1 |
20050280552 | Dipiazza | Dec 2005 | A1 |
20070005202 | Breed | Jan 2007 | A1 |
20070005609 | Breed | Jan 2007 | A1 |
20070046448 | Smitherman | Mar 2007 | A1 |
20070055446 | Schiffmann et al. | Mar 2007 | A1 |
20080225395 | Veerasamy | Sep 2008 | A1 |
20090140887 | Breed et al. | Jun 2009 | A1 |
20090164109 | Maruyama | Jun 2009 | A1 |
20100007523 | Hatav | Jan 2010 | A1 |
20100013615 | Herbert et al. | Jan 2010 | A1 |
20100023183 | Huang et al. | Jan 2010 | A1 |
20100026555 | Whittaker et al. | Feb 2010 | A1 |
20100063720 | Machino | Mar 2010 | A1 |
20100073194 | Ghazarian | Mar 2010 | A1 |
20100104199 | Zhang et al. | Apr 2010 | A1 |
20100106356 | Trepagnier et al. | Apr 2010 | A1 |
20100238006 | Grider et al. | Sep 2010 | A1 |
20110012755 | Mudalige | Jan 2011 | A1 |
20110125405 | Blesener et al. | May 2011 | A1 |
20110161987 | Huang | Jun 2011 | A1 |
20110163904 | Alland et al. | Jul 2011 | A1 |
20110184605 | Neff | Jul 2011 | A1 |
20110210866 | Klaus et al. | Sep 2011 | A1 |
20120022776 | Razavilar | Jan 2012 | A1 |
20120039084 | Eckhardt et al. | Feb 2012 | A1 |
20120041632 | Bordes | Feb 2012 | A1 |
20120083987 | Schwindt | Apr 2012 | A1 |
20120139754 | Ginsberg et al. | Jun 2012 | A1 |
20120166033 | Byun et al. | Jun 2012 | A1 |
20120169526 | Reihac | Jul 2012 | A1 |
20120249794 | Kiyo et al. | Oct 2012 | A1 |
20120274481 | Ginsberg et al. | Nov 2012 | A1 |
20120277967 | Isaji et al. | Nov 2012 | A1 |
20120296539 | Cooprider et al. | Nov 2012 | A1 |
20130110368 | Zagorski | May 2013 | A1 |
20130127190 | Shamoto | May 2013 | A1 |
20130131908 | Trepagnier et al. | May 2013 | A1 |
20130184926 | Spero et al. | Jul 2013 | A1 |
20130191022 | Mathes et al. | Jul 2013 | A1 |
20130218396 | Moshchuk et al. | Aug 2013 | A1 |
20130231825 | Chundrlik et al. | Sep 2013 | A1 |
20130265563 | Vogt et al. | Oct 2013 | A1 |
20130271292 | McDermott | Oct 2013 | A1 |
20130321627 | Turn et al. | Dec 2013 | A1 |
20130338858 | Cherepinsky | Dec 2013 | A1 |
20140012455 | Neff | Jan 2014 | A1 |
20140032093 | Mills | Jan 2014 | A1 |
20140081507 | Urmson | Mar 2014 | A1 |
20140081573 | Urmson et al. | Mar 2014 | A1 |
20140191882 | Varma | Jul 2014 | A1 |
20140204599 | Miura et al. | Jul 2014 | A1 |
20140210646 | Subramanua | Jul 2014 | A1 |
20140297093 | Murai et al. | Oct 2014 | A1 |
20140330479 | Dolgov et al. | Nov 2014 | A1 |
20150006005 | Yu et al. | Jan 2015 | A1 |
20150019080 | Schneider | Jan 2015 | A1 |
20150041510 | Frenzel et al. | Feb 2015 | A1 |
20150100189 | Tellis et al. | Apr 2015 | A1 |
20150124096 | Koravadi | May 2015 | A1 |
20160004915 | Chen et al. | Jan 2016 | A1 |
20160035221 | McDevitt-Pimbley et al. | Feb 2016 | A1 |
20160035223 | Gutmann et al. | Feb 2016 | A1 |
20160161267 | Harada | Jun 2016 | A1 |
20160231746 | Hazelton et al. | Aug 2016 | A1 |
20170039850 | Vanden Berg et al. | Feb 2017 | A1 |
20170371036 | Griffin | Dec 2017 | A1 |
20180004220 | Hazelton | Jan 2018 | A1 |
20180004221 | Hazelton | Jan 2018 | A1 |
20180004223 | Baldwin | Jan 2018 | A1 |
20180012492 | Baldwin et al. | Jan 2018 | A1 |
20180031696 | Lewis et al. | Feb 2018 | A1 |
20180037171 | Lewis et al. | Feb 2018 | A1 |
20180045826 | Kasaba et al. | Feb 2018 | A1 |
20180129215 | Hazelton et al. | May 2018 | A1 |
20190003895 | Krishnan et al. | Jan 2019 | A1 |
20190066498 | Baldwin et al. | Feb 2019 | A1 |
20190202355 | Tatara et al. | Jul 2019 | A1 |
20190210436 | Frederick et al. | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
3078987 | Oct 2016 | EP |
H07190732 | Jul 1995 | JP |
2004326705 | Nov 2004 | JP |
2007106199 | Apr 2007 | JP |
2008003959 | Jan 2008 | JP |
2008008870 | Jan 2008 | JP |
2010260493 | Nov 2010 | JP |
2014148293 | Aug 2014 | JP |
2014148393 | Aug 2014 | JP |
2014211862 | Nov 2014 | JP |
20010109873 | Dec 2001 | KR |
20100068944 | Jun 2010 | KR |
20110023952 | Mar 2011 | KR |
101071914 | Oct 2011 | KR |
20120072020 | Jul 2012 | KR |
20130026934 | Mar 2013 | KR |
2009070069 | Jun 2009 | WO |
2016126319 | Aug 2016 | WO |
2016126323 | Aug 2016 | WO |
20160126318 | Aug 2016 | WO |
2019059026 | Mar 2019 | WO |
Entry |
---|
“Advisory Action”, U.S. Appl. No. 15/549,061, dated Apr. 29, 2019, 6 pages. |
“Advisory Action”, U.S. Appl. No. 15/545,957, dated Jul. 16, 2019, 3 pages. |
“Final Office Action”, U.S. Appl. No. 15/549,061, dated Feb. 7, 2019, 9 pages. |
“Final Office Action”, U.S. Appl. No. 15/545,957, dated Apr. 17, 2019, 22 pages. |
“Final Office Action”, U.S. Appl. No. 15/546,196, dated Aug. 28, 2018, 16 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064235, dated Aug. 8, 2017, 12 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064243, dated Aug. 17, 2017, 12 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064282, dated Aug. 17, 2017, 16 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064225, dated Aug. 17, 2017, 6 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064283, dated Aug. 17, 2017, 6 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064289, dated Aug. 17, 2017, 6 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2016/014797, dated Aug. 17, 2017, 6 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064231, dated Aug. 17, 2017, 7 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/064240, dated Aug. 17, 2017, 7 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2016/016045, dated Aug. 17, 2017, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064289, dated Mar. 2, 2016, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064282, dated Mar. 18, 2016, 17 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064240, dated Mar. 18, 2016, 8 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064235, dated Mar. 22, 2016, 14 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064243, dated Mar. 30, 2016, 13 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064283, dated Apr. 15, 2016, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064225, dated Apr. 22, 2016, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2016/014797, dated May 11, 2016, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2016/016045, dated May 24, 2016, 9 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/064231, dated May 30, 2016, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/792,960, dated Mar. 19, 2020, 6 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/546,196, dated Apr. 5, 2018, 22 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/545,944, dated May 18, 2018, 6 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/544,283, dated Jun. 8, 2018, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/545,960, dated Jun. 15, 2018, 12 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/983,695, dated Aug. 1, 2017, 6 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/545,957, dated Aug. 16, 2019, 19 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/549,061, dated Sep. 5, 2018, 11 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/545,957, dated Oct. 15, 2018, 15 pages. |
“Notice of Allowance”, U.S. Appl. No. 15/545,957, dated Mar. 12, 2020, 10 pages. |
“Notice of Allowance”, U.S. Appl. No. 15/549,025, dated Sep. 3, 2019, 7 pages. |
“Notice of Allowance”, U.S. Appl. No. 15/545,944, dated Oct. 19, 2018, 8 pages. |
“Restriction Requirement”, U.S. Appl. No. 15/792,960, dated Jan. 9, 2020, 6 pages. |
“Restriction Requirement”, U.S. Appl. No. 14/983,695, dated Jun. 29, 2017, 8 pages. |
“Restriction Requirement”, U.S. Appl. No. 15/545,957, dated Sep. 17, 2018, 9 pages. |
“Final Office Action”, U.S. Appl. No. 15/792,960, dated Sep. 22, 2020, 7 Pages. |
“Non-Final Office Action”, U.S. Appl. No. 16/172,133, dated Oct. 16, 2020, 7 pages. |
“Notice of Allowance”, U.S. Appl. No. 16/172,133, dated Dec. 18, 2020, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20190101929 A1 | Apr 2019 | US |
Number | Date | Country | |
---|---|---|---|
62112775 | Feb 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15545957 | US | |
Child | 16208828 | US |