The present disclosure relates generally to electronic fund transfer. More particularly, the present disclosure relates generally to the electronic fund transfer to a mobile device based upon location or position information of the mobile device.
In a gaming environment, funds used to play a game of chance may be obtained from an operator by giving the operator a check. The amount may be credited to the player's account for use to play the games of chance. The player's domicile is sometimes checked and playing the games of chance may sometimes be denied.
The player can cash out from the device and receive either cash or a printed ticket to be presented to the operator. However, when playing games of chance on a mobile device, it is inefficient or not possible for the player to cash out by receiving cash or a printed ticket to be presented to the operator. Thus, electronic transfer of funds may be more efficient for users playing games of chance on a mobile device.
The invention provides for the electronic transfer of funds to or from a mobile device. The electronic transfer of funds may be used to purchase any desired products or services such as clothes, games of chance, e-books, food, movies, and the like. In one embodiment, the electronic transfer of funds may be used to play of a game of chance on the mobile device. A determination of whether to transfer the funds to the mobile device to play the game of chance may be based upon different criteria. For example, determination of whether to transfer the funds to the mobile device may be based on at least a global and local device position of the mobile device. In another example, the electronic transfer of funds to the mobile device may be based upon other predefined rules such as a time rule, captain's rule, user defined rules, and other criteria.
In one embodiment, a system for transferring money comprises a plurality of mobile devices, each of the plurality of mobile devices associated with a player and a location server operable to: track a device position of each of the plurality of mobile devices, the device position being relative to the vessel and track a vessel position, the vessel position being a global location relative to earth. The system may also have a mobile gaming management server configured to communicate with the location server and a gaming server, the mobile gaming management server operable to: receive a fund transfer request from the gaming server, the fund transfer request associated with at least one requesting mobile device, the fund transfer request including a fund amount used to play a game of chance; determine if the fund amount can be transferred to the associated mobile device based on the device position and the vessel position; and transfer the fund amount to the associated mobile device if it is determined that the fund amount can be transferred to the associated mobile device.
In another embodiment, a method for transferring funds on a vessel can include receiving a request to play a game of chance from at least one of the plurality of mobile devices, the request including a fund amount used to play the game of chance; determining whether the fund amount may be transferred to the mobile device based on at least a vessel position of the vessel and a device position of the mobile device; and transferring the fund amount to the mobile device if it is determined that the fund amount be transferred to the mobile device based on at least a vessel position of the vessel and a device position of the mobile device.
In another embodiment, a mobile gaming management device configured to transfer funds for passengers on a vessel may include at least one memory configured to store at least one passenger gaming account; and a processor configured to: (a) track gaming funds for use by at least one user of a mobile device; (b) receive a fund request including a fund amount; (c) obtain the fund amount, the fund amount used to play an on-board game of chance on the mobile device; (d) transfer the fund amount to the mobile device; (e) separately manage usage of the fund amount in a passenger gaming account, the passenger gaming account associated with the user playing the on-board game of chance; (f) accumulate any gaming wins from the on-board game of chance in the passenger gaming account; and (g) close the gaming account for the passenger at the conclusion of the vessel route.
The present invention provides other hardware configured to perform the methods of the invention, as well as software stored in a machine-readable medium (e.g., a tangible storage medium) to control devices to perform these methods. These and other features will be presented in more detail in the following detailed description of the invention and the associated figures.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.
In the drawings:
Embodiments are described herein in the context of an electronic fund transfer for mobile gaming. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
The invention provides for the electronic transfer of funds to or from a mobile device. The electronic transfer of funds may be used to purchase any desired products or services such as clothes, games of chance, e-books, food, movies, and the like. In one embodiment, the electronic transfer of funds may be used to play restricted entertainment activities such as playing a game of chance or sports betting on the mobile device. A determination of whether to transfer the funds to the mobile device to play the restricted entertainment activities may be based upon different criteria. For example, determination of whether to transfer the funds to the mobile device may be based on at least a global and local device position or location of the mobile device. In another example, the electronic transfer of funds to the mobile device may be based upon other predefined rules such as a time rule, captain's rule (e.g. any user desired defined rules), and other criteria. For example, if the mobile device is on a vessel (e.g., riverboats, cars, boats, cruise ships, planes, buses, or any moveable transport device), the determination of whether to transfer funds to the mobile device may be based upon at least where the device is relative to the vessel and whether the vessel is in international or national waters. In another example, if the mobile device is on an airplane, the determination of whether to transfer funds to the mobile device may be based upon at least whether the airplane is in international airspace.
In another embodiment, the electronic transfer of funds may be used to view an X-rated movie on the mobile device. A determination of whether to transfer the funds to the mobile device to play the game of chance may be based upon different criteria. For example, determination of whether to transfer the funds to the mobile device may be based on at least the device position of the mobile device. In another example, the electronic transfer of funds to the mobile device may be based upon other predefined rules such as a time rule, establishment rules, user defined rules, and other criteria. For example, if the mobile device is on a cruise ship, the determination of whether to transfer funds to the mobile device may be based upon whether the mobile device is located at an appropriate position or location to view the X-rated movie, such as in a night club and not at a child care facility or restaurant buffet line. The determination may also be based upon whether a vessel position of the vessel is in international or national waters.
The user of the mobile device 116 may also have a user account stored in the user account database 112. The user account may be any information such as user contact information, available funds in the user account, and any other user information. In one embodiment, any wins from a game of chance played by the user of the mobile device 116 may be stored in the user account.
Rules may be stored in the rules database 114. The rules may be any criteria used to determine whether to permit or deny a fund transfer request made by the mobile device. For example, if the fund transfer request is to play a game of chance on the mobile device, the determination of whether to transfer the funds to the mobile device may be based on at least the device position of the mobile device and the location of the establishment. If the mobile device is, for example, located near the childcare center and the establishment, such as a cruise ship, is in international waters, the transfer fund request may be denied. However, if the user is sitting at a bar and the establishment, such as a cruise ship, is in international waters, the transfer fund request may be granted. In another example, the fund transfer request may also be based upon a time rule that may be predetermined by the establishment. For example, the establishment may set games of chance to be played between 7 a.m. to 2 a.m. Thus, if the transfer fund request is made at 3 a.m., the transfer of fund to play the game of chance may be denied. If the transfer fund request is made at 12 p.m., the transfer of fund to play the game of chance may be permitted.
The mobile device management server 102 may be configured to communicate with an entertainment server 106, which may be configured to communicate with the mobile device 116. The mobile device 116 may purchase any type of services or products from entertainment server 106 such as clothes, play a game of chance, watch television shows or movies, listen to music, read e-books, play video games, or any other desired services or products.
The location server 104 may be configured to determine the location of the mobile device 116 and the establishment. The location server 104 may have a global position server 118 to determine the location of the establishment. In one embodiment, establishment may be a mobile establishment such as a cruise ship, airplane, bus, and the like. In another embodiment, establishment may be a non-mobile establishment such as a grocery store, casino, riverboat, and the like. Global position server 118 may use any known position or location method to determine the location of the establishment such as cellular positioning, triangulation, global positioning systems, or any other location or positioning determining method.
The location server 104 may also have a device position server 120 designed or configured to determine the position or location of the mobile device 116 relative to the establishment. In one example, if the establishment is a cruise ship, the device position of the mobile device 116 is the position of the mobile device 116 relative to the cruise ship. The device position server 120 may use any known position or location method to determine the location of the mobile device 116 such as cellular positioning, triangulation, global positioning systems, or any other location or positioning determining method.
The location server 104 may have a location database 113 to store the global position of the establishment and the device position of the mobile device. The global position and device position may be associated with a mobile device.
Mobile device management server 102 may also be configured to communicate with an establishment server 108. Establishment server 108 may be configured to store customer information in the customer main account database 122. The establishment server 108 may store information such as customer credit card information, address, username and password, date of birth, and any other desired information.
The example described below is for illustrative purposes only and is not intended to be limiting Although example embodiments illustrate the vessel as a cruise ship, this is not intended to be limiting as the vessel may be an airplane, bus, car, train, riverboat, or any other movable transport device. In another example, the service requested is to play a game of chance, however, any other type of services or products, such as to watch a movie, listen to music, and the like may be requested.
When boarding a cruise ship, the passenger's information may be stored in the customer main account 122 in the establishment server 108. The passenger's information may include financial information such as credit card information, address, birth date, family members, room number, room key number, username and password, and any other passenger information.
The passenger may be associated with a mobile device 116 to obtain services or products. In one embodiment, the mobile device 116 may be provided to the passenger. In another embodiment, the passenger may utilize his own mobile device 116. The passenger may request a transfer of funds to play a game of chance using the mobile device 116. The request may include a fund amount of $200.00 and the request to play Wheel of Fortune®. The passenger may also be authenticated and/or verified by including the passenger's username and password with the request. However, any other authentication and/or verification method may be used to authenticate and/or verify the user of the mobile device such as biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like).
The request to transfer funds may be transmitted from the mobile device 116 to the entertainment server 106. The entertainment server 106 may transmit the request to the mobile device management server 102. The mobile device management server 102 may determine whether the passenger has a user account 112. If the passenger does not have a user account 112, a user account 112 may be created for the passenger.
The mobile device management server 102 may obtain location information from the location server 104. The global position server 118 may determine a global ship position of the vessel relative to the world or earth. Referring to
Referring back to
Referring back to
However, since passenger B is located at the childcare center where playing games of chance are not permitted, the transfer of funds will be denied. In this embodiment, a denial message may be transmitted to the mobile device of passenger B. The denial message may also include at least one reason for the denial of the transfer fund request. For example, the denial message may display that games are chance are not permitted to be played in the childcare center.
Since passenger A is permitted to play the game of chance, the mobile device management server 102 may then determine whether there is enough funds in the user account 112. If there is not enough funds in the user account 112, the mobile device management server 102 may obtain passenger information, such as financial information, from the passenger main account 122 stored in the establishment server 108. For example, the mobile device management server 102 may obtain the passenger's credit card information in order to transfer the fund amount of $200.00 requested by the passenger. The $200.00 may then be transferred to the mobile device 116 via the entertainment server 106. The entertainment server 106 may also enable play of the game of chance on the mobile device 116 subsequent to the transfer of funds to the mobile device 116.
Prior to the transfer of the fund amount, the mobile device management server 102 may also user other criteria to determine whether to transfer the fund amount. For example, one criterion may be a time rule. A time stamp on the request for transfer of funds may be used to determine whether the game of chance may be played on the mobile device. If the time stamp was at 3 a.m., the game of chance may not be permitted to be played and the transfer of funds may be denied. If the time stamp was at 10 a.m., the game of chance may be permitted to be played and the transfer of funds may be approved. The time rule may also be updated based on different time zones.
In another example, one criterion may be the age of the passenger. If the user information obtained from the customer main account 122 indicates that the passenger is only 18 years old, based upon certain gaming rules, the game of chance may not be permitted to be played and the transfer of funds may be denied. It will now be appreciated that the mobile device management server 102 may use any other desired criteria to determine whether or not to transfer the fund amount to the mobile device 116.
Device 1254 may be located at the main pool in international waters. A request to transfer funds to play a game of chance may be received at 11 a.m. Based on the device position, vessel position, and time rule, the mobile device management server 102 may determine that the fund amount may be transferred to the mobile device to play the game of chance.
Device 2256 may be located at the childcare center in international waters. A request to transfer funds to play a game of chance may be received at 3 p.m. Based on the device position, vessel position, and time rule, the mobile device management server 102 may determine that the fund amount may not be transferred to the mobile device to play the game of chance.
Device 3258 may be located at the night club in international waters. A request to transfer funds to watch an X-rated movie may be received at 11 p.m. Based on the device position, vessel position, and time rule, the mobile device management server 102 may determine that the fund amount may be transferred to the mobile device to watch the X-rated movie.
The intermediary server may obtain a vessel position of the cruise ship and device position of the mobile device at 308. The vessel position and device position may be obtained from a location server, e.g. such as location server 104 illustrated in
Once obtained, the intermediary server may determine whether the fund amount may be transferred to the mobile device at 310. The determination may be based upon the rules stored in a rules database, e.g. such as rules database 114 illustrated in
If the intermediary server determines that the transfer of the fund amount is permitted at 310, a determination of whether the game of chance is permitted to be played on the mobile device is made at 312. In one embodiment, the determination whether the game of chance is permitted to be played on the mobile device may be based on at least the device position and the vessel position. In another embodiment, the determination of whether the game of chance is permitted to be played on the mobile device may be based on at least time rules, user information, establishment rules, or any other predetermined criteria. If the intermediary server determines that the game of chance is not permitted to be played on the mobile device, the method 300 may end. If the intermediary server determines that the game of chance is permitted to be played on the mobile device, the fund amount may be transferred to the mobile device and the game of chance may be enabled on the mobile device at 314.
If it is determined that the game of chance of is permitted to be played at 404, the method may continue at 402. If it is determined that the game of chance is not permitted to be played at 404, a termination notification may be transmitted to the mobile device at 406. In one embodiment, the termination notification may include at least one reason for termination of the game of chance. For example, the reason for termination may be based on the vessel position. The vessel may be entering into national waters from international waters. In another example, the reason for termination may be because the mobile device entered an unauthorized location where playing games of chance are not permitted. In still another example, the reason for termination may be because the time restriction to end play of the game of chance is imminent.
A determination may be made as to whether there are any gaming wins at 408. If the user has any wins and/or credits from playing the game of chance, the wins and/or credits may be stored in the user account in the intermediary server. Since wins and/or credits may not be transmitted back to a user's credit card or “reverse deposited”, the wins and/or credits may be stored in the user account in the intermediary server. The passenger may reconcile and close out the user account in the intermediary server when the passenger's trip ends.
If there are no gaming wins at 408 or after transfer of the gaming wins to the user account in the intermediary server at 410, the game of chance may be terminated on the mobile device at 412.
The intermediary server may obtain a vessel position of the vessel and device position of the mobile device at 504. The vessel position and device position may be obtained from, for example, a location server e.g. such as location server 104 illustrated in
Once obtained, the intermediary server may determine whether the game of chance may be played on the mobile device based upon the vessel position at 506. If it is determined that the game of chance may not be played on the mobile device based upon the vessel position at 506, the method 500 may end. If it is determined that the game of chance may be played on the mobile device based upon the vessel position at 506, a determination of whether the game of chance may be played on the mobile device based upon the device position at 508.
If it is determined that the game of chance may not be played on the mobile device based upon the device position at 508, the method 500 may end. If it is determined that the game of chance may be played on the mobile device based upon the device position at 508, a determination of whether the game of chance may be played on the mobile device based upon the time stamp at 510. If it is determined that the game of chance may not be played on the mobile device based upon the time stamp at 510, the method 500 may end. If it is determined that the game of chance may be played on the mobile device based upon the time stamp at 510, passenger information from the customer main account, including available funds to play on-board games of chance, may be obtained at 512. The determination of whether the game of chance may be played on the mobile device based upon the vessel position, device position, time stamp, or passenger information may be similar to the determination described above with respect to
The passenger information obtained from the user account may be any information necessary to transfer funds to the mobile device. For example, the passenger information may include financial information such as credit card information, passenger address and phone number, passenger date of birth, and any other information necessary in the transfer of funds to the mobile device.
A determination of whether the passenger has available funds may be made at 514. In one embodiment, the passenger information may also include any information related to playing games of chance. For example, the passenger may have a daily fund amount or limit to play games of chance, such as restricting game play to only $200.00 per day. In another example, the passenger may have a total limit of $500.00 used to play games of chance for the entire trip. If it is determined that the passenger does not have available funds at 514, the method 500 may end. If it is determined that the passenger does have available funds at 514, a determination of whether the game of chance may be played on the mobile device based on passenger information may be made at 516. For example, if the passenger information includes the date of birth indicating that the passenger is 18 years old, based upon certain gaming rules, the intermediary server may determine that the game of chance may not be permitted to be played on the mobile device.
If it is determined that the game of chance may be played on the mobile device based on passenger information at 516, the fund amount may be transferred to the mobile device and the game of chance may be enabled on the mobile device at 518.
The computing device 600 includes a processor 602 that pertains to a microprocessor or controller for controlling the overall operation of the computing device 600. The computing device 600 stores data pertaining to passengers, products and services, location, and the like in a file system 604 and a cache 606. The file system 604 is, typically, semiconductor memory (e.g., Flash memory) and/or one or more storage disks. The file system 604 typically provides high capacity storage capability for the computing device 600. However, since the access time to the file system 604 can be relatively slow, the computing device 600 can also include the cache 606. The cache 606 is, for example, Random-Access Memory (RAM). The relative access time to the cache 606 is typically shorter than for the file system 604. However, the cache 606 does not have the large storage capacity of the file system 604. The computing device 600 also includes a RAM 620 and a Read-Only Memory (ROM) 622. The ROM 622 can store programs, utilities or processes to be executed in a non-volatile manner. The RAM 620 provides volatile data storage, such as for the cache 606.
The computing device 600 may also include a user input device 608 that allows a user of the computing device 600 to interact with the computing device 600. For example, the user input device 608 can take a variety of forms, such as a button, keypad, dial, touch-sensitive surface, joystick, and the like. Still further, the computing device 600 includes a display 610 (screen display) that can be controlled by the processor 602 to display information to the user. A data bus 611 can facilitate data transfer between at least the file system 604, the cache 606, the processor 602, an audio coder/decoder (CODEC) 612 and/or a video CODEC 615.
In one embodiment, for example, if the computing device 600 (e.g. mobile device 116, establishment server 108, mobile device management server 102, location server 104, entertainment server 106 illustrated in
The computing device 600 also includes a network/bus interface 616 that couples to a data link 618. The data link 618 allows the computing device 600 to couple to another device (e.g., a host computer, a power source, or an accessory device). The data link 618 can be provided over a wired connection or a wireless connection. In the case of a wireless connection, the network/bus interface 616 can include a wireless transceiver.
The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations. Embodiments of the invention can, for example, be implemented by software, hardware, or a combination of hardware and software. Embodiments of the invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium generally include read-only memory and random-access memory. More specific examples of computer readable medium are tangible and include Flash memory, EEPROM memory, memory card, CD-ROM, DVD, hard drive, magnetic tape, and optical data storage device. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
Numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will become obvious to those skilled in the art that the invention may be practiced without these specific details. The description and representation herein are the common meanings used by those experienced or skilled in the art to most effectively convey the substance of their work to others skilled in the art. In other instances, well-known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the present invention.
In the foregoing description, reference to “one embodiment”, “an embodiment”, “one example” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Further, the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.
This application is a divisional of U.S. patent application Ser. No. 13/632,743, filed Oct. 1, 2012, and entitled “ELECTRONIC FUND TRANSFER FOR MOBILE GAMING,” which is hereby incorporated herein by reference, and which in turn claims priority benefit of U.S. Provisional Application No. 61/542,703, filed Oct. 3, 2011, and entitled “ELECTRONIC FUND TRANSFER,” which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
2033638 | Koppl | Mar 1936 | A |
2062923 | Nagy | Dec 1936 | A |
4741539 | Sutton et al. | May 1988 | A |
4948138 | Pease et al. | Aug 1990 | A |
5067712 | Georgilas | Nov 1991 | A |
5275400 | Weingardt | Jan 1994 | A |
5429361 | Raven et al. | Jul 1995 | A |
5489103 | Okamoto | Feb 1996 | A |
5630757 | Gagin | May 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5704835 | Dietz, II | Jan 1998 | A |
5727786 | Weingardt | Mar 1998 | A |
5833537 | Barrie | Nov 1998 | A |
5842921 | Mindes | Dec 1998 | A |
5919091 | Bell et al. | Jul 1999 | A |
5947820 | Morro et al. | Sep 1999 | A |
5997401 | Crawford | Dec 1999 | A |
6001016 | Walker et al. | Dec 1999 | A |
6039648 | Guinn et al. | Mar 2000 | A |
6059289 | Vancura | May 2000 | A |
6089977 | Bennett | Jul 2000 | A |
6095920 | Sudahiro | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6146271 | Kadici | Nov 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6165071 | Weiss | Dec 2000 | A |
6231445 | Acres | May 2001 | B1 |
6244958 | Acres | Jun 2001 | B1 |
6270412 | Crawford et al. | Aug 2001 | B1 |
6290600 | Glasson | Sep 2001 | B1 |
6293866 | Walker et al. | Sep 2001 | B1 |
6353390 | Beri et al. | Mar 2002 | B1 |
6364768 | Acres et al. | Apr 2002 | B1 |
6404884 | Marwell et al. | Jun 2002 | B1 |
6416406 | Duhamel | Jul 2002 | B1 |
6416409 | Jordan | Jul 2002 | B1 |
6443452 | Brune | Sep 2002 | B1 |
6491584 | Graham et al. | Dec 2002 | B2 |
6505095 | Kolls | Jan 2003 | B1 |
6508710 | Paravia et al. | Jan 2003 | B1 |
6561900 | Baerlocker et al. | May 2003 | B1 |
6592457 | Frohm et al. | Jul 2003 | B1 |
6612574 | Cole et al. | Sep 2003 | B1 |
6620046 | Rowe | Sep 2003 | B2 |
6641477 | Dietz, II | Nov 2003 | B1 |
6645078 | Mattice | Nov 2003 | B1 |
6719630 | Seelig et al. | Apr 2004 | B1 |
6749510 | Globbi | Jun 2004 | B2 |
6758757 | Luciano, Jr. et al. | Jul 2004 | B2 |
6773345 | Walker et al. | Aug 2004 | B2 |
6778820 | Tendler | Aug 2004 | B2 |
6780111 | Cannon et al. | Aug 2004 | B2 |
6799032 | McDonnell et al. | Sep 2004 | B2 |
6800027 | Giobbi et al. | Oct 2004 | B2 |
6804763 | Stockdale et al. | Oct 2004 | B1 |
6811486 | Luciano, Jr. | Nov 2004 | B1 |
6843725 | Nelson | Jan 2005 | B2 |
6846238 | Wells | Jan 2005 | B2 |
6848995 | Walker et al. | Feb 2005 | B1 |
6852029 | Baltz et al. | Feb 2005 | B2 |
6869361 | Sharpless et al. | Mar 2005 | B2 |
6875106 | Weiss et al. | Apr 2005 | B2 |
6884170 | Rowe | Apr 2005 | B2 |
6884172 | Lloyd et al. | Apr 2005 | B1 |
6902484 | Idaka | Jun 2005 | B2 |
6908390 | Nguyen et al. | Jun 2005 | B2 |
6913532 | Bearlocher et al. | Jul 2005 | B2 |
6923721 | Luciano et al. | Aug 2005 | B2 |
6935958 | Nelson | Aug 2005 | B2 |
6949022 | Showers | Sep 2005 | B1 |
6955600 | Glavich et al. | Oct 2005 | B2 |
6971956 | Rowe et al. | Dec 2005 | B2 |
6984174 | Cannon et al. | Jan 2006 | B2 |
6997803 | LeMay et al. | Feb 2006 | B2 |
7018292 | Tracy et al. | Mar 2006 | B2 |
7032115 | Kashani | Apr 2006 | B2 |
7033276 | Walker et al. | Apr 2006 | B2 |
7035626 | Luciano | Apr 2006 | B1 |
7037195 | Schneider et al. | May 2006 | B2 |
7048628 | Schneider | May 2006 | B2 |
7048630 | Berg et al. | May 2006 | B2 |
7063617 | Brosnan et al. | Jun 2006 | B2 |
7076329 | Kolls | Jul 2006 | B1 |
7089264 | Guido et al. | Aug 2006 | B1 |
7094148 | Bearlocher et al. | Aug 2006 | B2 |
7105736 | Laakso | Sep 2006 | B2 |
7111141 | Nelson | Sep 2006 | B2 |
7144321 | Mayeroff | Dec 2006 | B2 |
7152783 | Charrin | Dec 2006 | B2 |
7169041 | Tessmer et al. | Jan 2007 | B2 |
7169052 | Beaulieu et al. | Jan 2007 | B2 |
7175523 | Gilmore et al. | Feb 2007 | B2 |
7181228 | Boesch | Feb 2007 | B2 |
7182690 | Giobbi et al. | Feb 2007 | B2 |
7198571 | LeMay | Apr 2007 | B2 |
RE39644 | Alcorn et al. | May 2007 | E |
7217191 | Allen et al. | May 2007 | B2 |
7243104 | Bill | Jul 2007 | B2 |
7247098 | Bradford et al. | Jul 2007 | B1 |
7259718 | Patterson et al. | Aug 2007 | B2 |
7275989 | Moody | Oct 2007 | B2 |
7285047 | Gielb et al. | Oct 2007 | B2 |
7311608 | Danieli | Dec 2007 | B1 |
7314408 | Cannon et al. | Jan 2008 | B2 |
7316615 | Soltys et al. | Jan 2008 | B2 |
7316619 | Nelson | Jan 2008 | B2 |
7318775 | Brosnan et al. | Jan 2008 | B2 |
7326116 | O'Donovan et al. | Feb 2008 | B2 |
7330108 | Thomas | Feb 2008 | B2 |
7346358 | Wood et al. | Mar 2008 | B2 |
7355112 | Laakso | Apr 2008 | B2 |
7384338 | Rothschild et al. | Jun 2008 | B2 |
7387571 | Walker et al. | Jun 2008 | B2 |
7393278 | Gerson et al. | Jul 2008 | B2 |
7396990 | Lu et al. | Jul 2008 | B2 |
7415426 | Williams et al. | Aug 2008 | B2 |
7425177 | Rodgers et al. | Sep 2008 | B2 |
7427234 | Soltys et al. | Sep 2008 | B2 |
7427236 | Kaminkow et al. | Sep 2008 | B2 |
7427708 | Ohmura | Sep 2008 | B2 |
7431650 | Kessman | Oct 2008 | B2 |
7448949 | Kaminkow et al. | Nov 2008 | B2 |
7500913 | Baerlocher | Mar 2009 | B2 |
7510474 | Carter | Mar 2009 | B2 |
7513828 | Nguyen et al. | Apr 2009 | B2 |
7519838 | Suurballe | Apr 2009 | B1 |
7559838 | Walker et al. | Jul 2009 | B2 |
7563167 | Walker et al. | Jul 2009 | B2 |
7572183 | Olivas et al. | Aug 2009 | B2 |
7585222 | Muir | Sep 2009 | B2 |
7602298 | Thomas | Oct 2009 | B2 |
7607174 | Kashchenko et al. | Oct 2009 | B1 |
7611409 | Muir et al. | Nov 2009 | B2 |
7637810 | Amaitis et al. | Dec 2009 | B2 |
7644861 | Alderucci et al. | Jan 2010 | B2 |
7653757 | Fernald et al. | Jan 2010 | B1 |
7693306 | Huber | Apr 2010 | B2 |
7699703 | Muir et al. | Apr 2010 | B2 |
7722453 | Lark et al. | May 2010 | B2 |
7758423 | Foster et al. | Jul 2010 | B2 |
7771271 | Walker et al. | Aug 2010 | B2 |
7780529 | Rowe et al. | Aug 2010 | B2 |
7780531 | Englman et al. | Aug 2010 | B2 |
7785192 | Canterbury et al. | Aug 2010 | B2 |
7811172 | Asher et al. | Oct 2010 | B2 |
7819749 | Fish | Oct 2010 | B1 |
7822688 | Labron | Oct 2010 | B2 |
7828652 | Nguyen et al. | Nov 2010 | B2 |
7828654 | Carter | Nov 2010 | B2 |
7828661 | Fish | Nov 2010 | B1 |
7850528 | Wells | Dec 2010 | B2 |
7874919 | Paulsen et al. | Jan 2011 | B2 |
7877798 | Saunders et al. | Jan 2011 | B2 |
7883413 | Paulsen | Feb 2011 | B2 |
7892097 | Muir et al. | Feb 2011 | B2 |
7909692 | Nguyen et al. | Mar 2011 | B2 |
7909699 | Parrott et al. | Mar 2011 | B2 |
7918728 | Nguyen et al. | Apr 2011 | B2 |
7927211 | Rowe et al. | Apr 2011 | B2 |
7927212 | Hedrick et al. | Apr 2011 | B2 |
7951008 | Wolf et al. | May 2011 | B2 |
8057298 | Nguyen et al. | Nov 2011 | B2 |
8057303 | Rasmussen | Nov 2011 | B2 |
8087988 | Nguyen et al. | Jan 2012 | B2 |
8117608 | Slettehaugh | Feb 2012 | B1 |
8133113 | Nguyen | Mar 2012 | B2 |
8182326 | Speers et al. | May 2012 | B2 |
8210927 | Hedrick | Jul 2012 | B2 |
8221245 | Walker | Jul 2012 | B2 |
8226459 | Barrett | Jul 2012 | B2 |
8226474 | Nguyen et al. | Jul 2012 | B2 |
8231456 | Zielinski | Jul 2012 | B2 |
8235803 | Loose et al. | Aug 2012 | B2 |
8282475 | Nguyen et al. | Oct 2012 | B2 |
8323099 | Durham et al. | Dec 2012 | B2 |
8337290 | Nguyen et al. | Dec 2012 | B2 |
8342946 | Amaitis | Jan 2013 | B2 |
8393948 | Allen et al. | Mar 2013 | B2 |
8403758 | Homik | Mar 2013 | B2 |
8430745 | Agarwal et al. | Apr 2013 | B2 |
8461958 | Saenz | Jun 2013 | B2 |
8469813 | Joshi | Jun 2013 | B2 |
8529345 | Nguyen | Sep 2013 | B2 |
8597108 | Nguyen | Dec 2013 | B2 |
8602875 | Nguyen | Dec 2013 | B2 |
8613655 | Kisenwether | Dec 2013 | B2 |
8613659 | Nelson et al. | Dec 2013 | B2 |
8696470 | Nguyen | Apr 2014 | B2 |
8745417 | Huang et al. | Jun 2014 | B2 |
8834254 | Buchholz et al. | Sep 2014 | B2 |
8858323 | Nguyen et al. | Oct 2014 | B2 |
8864586 | Nguyen | Oct 2014 | B2 |
8942995 | Kerr | Jan 2015 | B1 |
9039507 | Allen et al. | May 2015 | B2 |
9235952 | Nguyen | Jan 2016 | B2 |
9292996 | Davis et al. | Mar 2016 | B2 |
9325203 | Nguyen | Apr 2016 | B2 |
9466171 | Hornik | Oct 2016 | B2 |
9483901 | Nguyen | Nov 2016 | B2 |
9486697 | Nguyen | Nov 2016 | B2 |
9486704 | Nguyen | Nov 2016 | B2 |
9576425 | Nguyen | Feb 2017 | B2 |
9626826 | Nguyen | Apr 2017 | B2 |
9666021 | Nguyen | May 2017 | B2 |
9672686 | Nguyen | Jun 2017 | B2 |
9741205 | Nguyen | Aug 2017 | B2 |
9811973 | Nguyen | Nov 2017 | B2 |
9814970 | Nguyen | Nov 2017 | B2 |
9842462 | Nguyen | Dec 2017 | B2 |
9875606 | Nguyen | Jan 2018 | B2 |
9875609 | Nguyen | Jan 2018 | B2 |
9981180 | Koyanagi et al. | May 2018 | B2 |
10140816 | Nguyen | Nov 2018 | B2 |
10421010 | Nguyen | Sep 2019 | B2 |
10438446 | Nguyen | Oct 2019 | B2 |
10445978 | Nguyen | Oct 2019 | B2 |
20010004607 | Olsen | Jun 2001 | A1 |
20010016516 | Takatsuka | Aug 2001 | A1 |
20010024971 | Brossard | Sep 2001 | A1 |
20010031659 | Perrie | Oct 2001 | A1 |
20010047291 | Garahi | Nov 2001 | A1 |
20020006822 | Krintzman | Jan 2002 | A1 |
20020042295 | Walker et al. | Apr 2002 | A1 |
20020043759 | Vancura | Apr 2002 | A1 |
20020045474 | Singer | Apr 2002 | A1 |
20020107065 | Rowe | Aug 2002 | A1 |
20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
20020111213 | McEntee et al. | Aug 2002 | A1 |
20020113369 | Weingardt | Aug 2002 | A1 |
20020116615 | Nguyen et al. | Aug 2002 | A1 |
20020133418 | Hammond et al. | Sep 2002 | A1 |
20020137217 | Rowe et al. | Sep 2002 | A1 |
20020142825 | Lark et al. | Oct 2002 | A1 |
20020147047 | Letovsky et al. | Oct 2002 | A1 |
20020147049 | Carter, Sr. | Oct 2002 | A1 |
20020151366 | Walker et al. | Oct 2002 | A1 |
20020152120 | Howington | Oct 2002 | A1 |
20020167536 | Valdes et al. | Nov 2002 | A1 |
20020177483 | Cannon | Nov 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20030001338 | Bennett et al. | Jan 2003 | A1 |
20030003996 | Nguyen | Jan 2003 | A1 |
20030004871 | Rowe | Jan 2003 | A1 |
20030008696 | Abecassis et al. | Jan 2003 | A1 |
20030027635 | Walker et al. | Feb 2003 | A1 |
20030064805 | Wells | Apr 2003 | A1 |
20030064807 | Walker et al. | Apr 2003 | A1 |
20030092480 | White et al. | May 2003 | A1 |
20030100361 | Sharpless et al. | May 2003 | A1 |
20030104860 | Cannon et al. | Jun 2003 | A1 |
20030104865 | Itkis et al. | Jun 2003 | A1 |
20030148809 | Nelson | Aug 2003 | A1 |
20030162588 | Brosnan et al. | Aug 2003 | A1 |
20030195024 | Slattery | Oct 2003 | A1 |
20030199295 | Vancura | Oct 2003 | A1 |
20030224852 | Walker et al. | Dec 2003 | A1 |
20030224854 | Joao | Dec 2003 | A1 |
20040002386 | Wolfe et al. | Jan 2004 | A1 |
20040005919 | Walker et al. | Jan 2004 | A1 |
20040023709 | Beaulieu et al. | Feb 2004 | A1 |
20040023716 | Gauselmann | Feb 2004 | A1 |
20040038736 | Bryant | Feb 2004 | A1 |
20040048650 | Mierau et al. | Mar 2004 | A1 |
20040068460 | Feeley | Apr 2004 | A1 |
20040082385 | Silva et al. | Apr 2004 | A1 |
20040106449 | Walker et al. | Jun 2004 | A1 |
20040127277 | Walker | Jul 2004 | A1 |
20040127290 | Walker et al. | Jul 2004 | A1 |
20040137987 | Nguyen et al. | Jul 2004 | A1 |
20040147308 | Walker et al. | Jul 2004 | A1 |
20040152508 | Lind | Aug 2004 | A1 |
20040199631 | Natsume | Oct 2004 | A1 |
20040214622 | Atkinson | Oct 2004 | A1 |
20040224753 | Odonovan et al. | Nov 2004 | A1 |
20040256803 | Ko | Dec 2004 | A1 |
20040259633 | Gentles et al. | Dec 2004 | A1 |
20050003890 | Hedrick et al. | Jan 2005 | A1 |
20050004980 | Vadjinia | Jan 2005 | A1 |
20050026696 | Hashimoto et al. | Feb 2005 | A1 |
20050054446 | Kammler | Mar 2005 | A1 |
20050101376 | Walker et al. | May 2005 | A1 |
20050101383 | Wells | May 2005 | A1 |
20050130728 | Nguyen et al. | Jun 2005 | A1 |
20050130731 | Englman | Jun 2005 | A1 |
20050137014 | Vetelaninen | Jun 2005 | A1 |
20050170883 | Muskin et al. | Aug 2005 | A1 |
20050181865 | Luciano | Aug 2005 | A1 |
20050181870 | Nguyen et al. | Aug 2005 | A1 |
20050181875 | Hoehne | Aug 2005 | A1 |
20050187020 | Amaitis | Aug 2005 | A1 |
20050202875 | Murphy et al. | Sep 2005 | A1 |
20050209002 | Blythe et al. | Sep 2005 | A1 |
20050221881 | Lannert | Oct 2005 | A1 |
20050223219 | Gatto et al. | Oct 2005 | A1 |
20050239546 | Hedrick | Oct 2005 | A1 |
20050255919 | Nelson | Nov 2005 | A1 |
20050273635 | Wilcox et al. | Dec 2005 | A1 |
20050277471 | Russell et al. | Dec 2005 | A1 |
20050282637 | Gatto et al. | Dec 2005 | A1 |
20060009283 | Englman et al. | Jan 2006 | A1 |
20060036874 | Cockerille | Feb 2006 | A1 |
20060046822 | Kaminkow et al. | Mar 2006 | A1 |
20060046830 | Webb | Mar 2006 | A1 |
20060046849 | Kovacs | Mar 2006 | A1 |
20060068893 | Jaffe et al. | Mar 2006 | A1 |
20060073869 | LeMay et al. | Apr 2006 | A1 |
20060073897 | Englman et al. | Apr 2006 | A1 |
20060079317 | Flemming et al. | Apr 2006 | A1 |
20060148551 | Walker et al. | Jul 2006 | A1 |
20060189382 | Muir et al. | Aug 2006 | A1 |
20060217170 | Roireau | Sep 2006 | A1 |
20060217193 | Walker et al. | Sep 2006 | A1 |
20060247028 | Brosnan et al. | Nov 2006 | A1 |
20060247035 | Rowe et al. | Nov 2006 | A1 |
20060252530 | Oberberger et al. | Nov 2006 | A1 |
20060253481 | Guido et al. | Nov 2006 | A1 |
20060281525 | Borissov | Dec 2006 | A1 |
20060281541 | Nguyen et al. | Dec 2006 | A1 |
20060287106 | Jensen | Dec 2006 | A1 |
20070004510 | Underdahl et al. | Jan 2007 | A1 |
20070026935 | Wolf et al. | Feb 2007 | A1 |
20070026942 | Kinsley | Feb 2007 | A1 |
20070054739 | Amaitis et al. | Mar 2007 | A1 |
20070060254 | Muir | Mar 2007 | A1 |
20070060306 | Amaitis et al. | Mar 2007 | A1 |
20070060319 | Block et al. | Mar 2007 | A1 |
20070060358 | Amaitas et al. | Mar 2007 | A1 |
20070077981 | Hungate et al. | Apr 2007 | A1 |
20070087833 | Feeney et al. | Apr 2007 | A1 |
20070087834 | Moser et al. | Apr 2007 | A1 |
20070093299 | Bergeron | Apr 2007 | A1 |
20070129123 | Eryou et al. | Jun 2007 | A1 |
20070129148 | Van Luchene | Jun 2007 | A1 |
20070149279 | Norden et al. | Jun 2007 | A1 |
20070149286 | Bemmel | Jun 2007 | A1 |
20070159301 | Hirt et al. | Jul 2007 | A1 |
20070161402 | Ng et al. | Jul 2007 | A1 |
20070184896 | Dickerson | Aug 2007 | A1 |
20070184904 | Lee | Aug 2007 | A1 |
20070191109 | Crowder et al. | Aug 2007 | A1 |
20070207852 | Nelson et al. | Sep 2007 | A1 |
20070207854 | Wolf et al. | Sep 2007 | A1 |
20070238505 | Okada | Oct 2007 | A1 |
20070241187 | Alderucci et al. | Oct 2007 | A1 |
20070248036 | Nevalainen | Oct 2007 | A1 |
20070257430 | Hardy et al. | Nov 2007 | A1 |
20070259713 | Fiden et al. | Nov 2007 | A1 |
20070259717 | Mattice et al. | Nov 2007 | A1 |
20070270213 | Nguyen et al. | Nov 2007 | A1 |
20070275777 | Walker et al. | Nov 2007 | A1 |
20070275779 | Amaitis et al. | Nov 2007 | A1 |
20070281782 | Amaitis et al. | Dec 2007 | A1 |
20070281785 | Amaitas et al. | Dec 2007 | A1 |
20070298873 | Nguyen et al. | Dec 2007 | A1 |
20080015032 | Bradford et al. | Jan 2008 | A1 |
20080020824 | Cuddy et al. | Jan 2008 | A1 |
20080020845 | Low | Jan 2008 | A1 |
20080032787 | Low et al. | Feb 2008 | A1 |
20080070652 | Nguyen et al. | Mar 2008 | A1 |
20080070681 | Marks et al. | Mar 2008 | A1 |
20080076505 | Nguyen | Mar 2008 | A1 |
20080076506 | Nguyen et al. | Mar 2008 | A1 |
20080076548 | Paulsen | Mar 2008 | A1 |
20080076572 | Nguyen et al. | Mar 2008 | A1 |
20080096650 | Baerlocher | Apr 2008 | A1 |
20080102916 | Kovacs | May 2008 | A1 |
20080102956 | Burman et al. | May 2008 | A1 |
20080102957 | Burnman et al. | May 2008 | A1 |
20080113772 | Burrill et al. | May 2008 | A1 |
20080119267 | Denlay | May 2008 | A1 |
20080126529 | Kim | May 2008 | A1 |
20080139306 | Lutnick | Jun 2008 | A1 |
20080146321 | Parente | Jun 2008 | A1 |
20080146344 | Rowe et al. | Jun 2008 | A1 |
20080150902 | Edpalm et al. | Jun 2008 | A1 |
20080153583 | Huntley et al. | Jun 2008 | A1 |
20080161110 | Campbell | Jul 2008 | A1 |
20080167106 | Lutnick et al. | Jul 2008 | A1 |
20080182667 | Davis et al. | Jul 2008 | A1 |
20080200251 | Alderucci | Aug 2008 | A1 |
20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
20080214258 | Brosnan et al. | Sep 2008 | A1 |
20080215319 | Lu | Sep 2008 | A1 |
20080234047 | Nguyen | Sep 2008 | A1 |
20080238610 | Rosenbereg | Oct 2008 | A1 |
20080248849 | Lutnick | Oct 2008 | A1 |
20080248865 | Cole | Oct 2008 | A1 |
20080252419 | Batchelor | Oct 2008 | A1 |
20080254878 | Sauders et al. | Oct 2008 | A1 |
20080254881 | Lutnick et al. | Oct 2008 | A1 |
20080254883 | Patel et al. | Oct 2008 | A1 |
20080254891 | Sauders et al. | Oct 2008 | A1 |
20080254892 | Sauders et al. | Oct 2008 | A1 |
20080254897 | Sauders et al. | Oct 2008 | A1 |
20080263173 | Weber et al. | Oct 2008 | A1 |
20080300058 | Sum et al. | Dec 2008 | A1 |
20080305864 | Kelly et al. | Dec 2008 | A1 |
20080305865 | Kelly et al. | Dec 2008 | A1 |
20080305866 | Kelly et al. | Dec 2008 | A1 |
20080311994 | Amaitas et al. | Dec 2008 | A1 |
20080318669 | Buchholz | Dec 2008 | A1 |
20080318686 | Crowder et al. | Dec 2008 | A1 |
20090005165 | Arezina et al. | Jan 2009 | A1 |
20090011822 | Englman | Jan 2009 | A1 |
20090017906 | Jackson | Jan 2009 | A1 |
20090021381 | Higuchi | Jan 2009 | A1 |
20090029766 | Lutnick et al. | Jan 2009 | A1 |
20090054149 | Brosnan et al. | Feb 2009 | A1 |
20090077396 | Tsai et al. | Mar 2009 | A1 |
20090088258 | Saunders | Apr 2009 | A1 |
20090098925 | Gagner et al. | Apr 2009 | A1 |
20090104977 | Zielinski | Apr 2009 | A1 |
20090104983 | Okada | Apr 2009 | A1 |
20090118002 | Lyons | May 2009 | A1 |
20090118013 | Finnimore et al. | May 2009 | A1 |
20090118022 | Lyons et al. | May 2009 | A1 |
20090124366 | Aoki et al. | May 2009 | A1 |
20090124390 | Seelig et al. | May 2009 | A1 |
20090131146 | Arezina et al. | May 2009 | A1 |
20090131151 | Harris et al. | May 2009 | A1 |
20090132163 | Ashley et al. | May 2009 | A1 |
20090137255 | Ashley et al. | May 2009 | A1 |
20090138133 | Buchholz et al. | May 2009 | A1 |
20090143141 | Wells | Jun 2009 | A1 |
20090149245 | Fabbri | Jun 2009 | A1 |
20090149261 | Chen et al. | Jun 2009 | A1 |
20090153342 | Thorn | Jun 2009 | A1 |
20090156303 | Kiely et al. | Jun 2009 | A1 |
20090163272 | Baker | Jun 2009 | A1 |
20090176578 | Herrmann et al. | Jul 2009 | A1 |
20090191962 | Hardy et al. | Jul 2009 | A1 |
20090197684 | Arezina et al. | Aug 2009 | A1 |
20090216547 | Canora et al. | Aug 2009 | A1 |
20090219901 | Bull et al. | Sep 2009 | A1 |
20090221342 | Katz et al. | Sep 2009 | A1 |
20090227302 | Abe | Sep 2009 | A1 |
20090239666 | Hall et al. | Sep 2009 | A1 |
20090264190 | Davis et al. | Oct 2009 | A1 |
20090270170 | Patton | Oct 2009 | A1 |
20090271287 | Halpern | Oct 2009 | A1 |
20090275410 | Kisenwether et al. | Nov 2009 | A1 |
20090275411 | Kisenwether et al. | Nov 2009 | A1 |
20090280910 | Gagner et al. | Nov 2009 | A1 |
20090282469 | Lynch | Nov 2009 | A1 |
20090298468 | Hsu | Dec 2009 | A1 |
20100002897 | Keady | Jan 2010 | A1 |
20100004058 | Acres | Jan 2010 | A1 |
20100016069 | Herrmann | Jan 2010 | A1 |
20100049738 | Mathur et al. | Feb 2010 | A1 |
20100056248 | Acres | Mar 2010 | A1 |
20100062833 | Mattice et al. | Mar 2010 | A1 |
20100062840 | Herrmann et al. | Mar 2010 | A1 |
20100079237 | Falk | Apr 2010 | A1 |
20100081501 | Carpenter et al. | Apr 2010 | A1 |
20100081509 | Burke | Apr 2010 | A1 |
20100099499 | Amaitis et al. | Apr 2010 | A1 |
20100106612 | Gupta | Apr 2010 | A1 |
20100115591 | Palermo | May 2010 | A1 |
20100120486 | DeWaal | May 2010 | A1 |
20100124967 | Lutnick et al. | May 2010 | A1 |
20100130276 | Fiden | May 2010 | A1 |
20100160035 | Herrmann | Jun 2010 | A1 |
20100160043 | Fujimoto et al. | Jun 2010 | A1 |
20100178977 | Kim et al. | Jul 2010 | A1 |
20100184509 | Sylla | Jul 2010 | A1 |
20100197383 | Rader et al. | Aug 2010 | A1 |
20100197385 | Aoki et al. | Aug 2010 | A1 |
20100203955 | Sylla | Aug 2010 | A1 |
20100203963 | Allen | Aug 2010 | A1 |
20100227662 | Speers et al. | Sep 2010 | A1 |
20100227670 | Arezine et al. | Sep 2010 | A1 |
20100227671 | Laaroussi | Sep 2010 | A1 |
20100227687 | Speers et al. | Sep 2010 | A1 |
20100234091 | Baerlocher et al. | Sep 2010 | A1 |
20100279764 | Allen et al. | Nov 2010 | A1 |
20100323780 | Acres | Dec 2010 | A1 |
20100325703 | Etchegoyen | Dec 2010 | A1 |
20110009181 | Speers et al. | Jan 2011 | A1 |
20110039615 | Acres | Feb 2011 | A1 |
20110053679 | Canterbury et al. | Mar 2011 | A1 |
20110065492 | Acres | Mar 2011 | A1 |
20110105216 | Cohen | May 2011 | A1 |
20110111827 | Nicely et al. | May 2011 | A1 |
20110111843 | Nicely et al. | May 2011 | A1 |
20110111860 | Nguyen | May 2011 | A1 |
20110118010 | Brune | May 2011 | A1 |
20110159966 | Gura et al. | Jun 2011 | A1 |
20110183732 | Block | Jul 2011 | A1 |
20110183749 | Allen | Jul 2011 | A1 |
20110207525 | Allen | Aug 2011 | A1 |
20110212711 | Scott | Sep 2011 | A1 |
20110212767 | Barclay et al. | Sep 2011 | A1 |
20110223993 | Allen et al. | Sep 2011 | A1 |
20110244952 | Schueller | Oct 2011 | A1 |
20110263318 | Agarwal et al. | Oct 2011 | A1 |
20110269548 | Barclay et al. | Nov 2011 | A1 |
20110306400 | Nguyen | Dec 2011 | A1 |
20110306426 | Novak et al. | Dec 2011 | A1 |
20120015709 | Bennett et al. | Jan 2012 | A1 |
20120028703 | Anderson et al. | Feb 2012 | A1 |
20120028718 | Barclay et al. | Feb 2012 | A1 |
20120034968 | Watkins et al. | Feb 2012 | A1 |
20120046110 | Amaitis | Feb 2012 | A1 |
20120094769 | Nguyen et al. | Apr 2012 | A1 |
20120100908 | Wells | Apr 2012 | A1 |
20120108319 | Caputo et al. | May 2012 | A1 |
20120122561 | Hedrick | May 2012 | A1 |
20120122567 | Gangadharan et al. | May 2012 | A1 |
20120122584 | Nguyen | May 2012 | A1 |
20120122590 | Nguyen | May 2012 | A1 |
20120172130 | Acres | Jul 2012 | A1 |
20120184362 | Barclay et al. | Jul 2012 | A1 |
20120184363 | Barclay et al. | Jul 2012 | A1 |
20120190426 | Acres | Jul 2012 | A1 |
20120194448 | Rothkopf | Aug 2012 | A1 |
20120208618 | Frerking | Aug 2012 | A1 |
20120231885 | Speer, II | Sep 2012 | A1 |
20120239566 | Everett | Sep 2012 | A1 |
20120322563 | Nguyen et al. | Dec 2012 | A1 |
20120330740 | Pennington et al. | Dec 2012 | A1 |
20130005433 | Holch | Jan 2013 | A1 |
20130005443 | Kosta | Jan 2013 | A1 |
20130005453 | Nguyen et al. | Jan 2013 | A1 |
20130059650 | Sylla et al. | Mar 2013 | A1 |
20130065668 | LeMay | Mar 2013 | A1 |
20130281188 | Guinn | Mar 2013 | A1 |
20130103965 | Golembeski | Apr 2013 | A1 |
20130104193 | Gatto et al. | Apr 2013 | A1 |
20130132745 | Schoening et al. | May 2013 | A1 |
20130165210 | Nelson | Jun 2013 | A1 |
20130185559 | Morel | Jul 2013 | A1 |
20130196756 | Nguyen | Aug 2013 | A1 |
20130196776 | Nguyen | Aug 2013 | A1 |
20130210513 | Nguyen | Aug 2013 | A1 |
20130210514 | Nguyen | Aug 2013 | A1 |
20130210530 | Nguyen | Aug 2013 | A1 |
20130225279 | Patceg | Aug 2013 | A1 |
20130225282 | Williams et al. | Aug 2013 | A1 |
20130252730 | Joshi | Sep 2013 | A1 |
20130316808 | Nelson | Nov 2013 | A1 |
20130337878 | Shepherd | Dec 2013 | A1 |
20140006129 | Heath | Jan 2014 | A1 |
20140057716 | Massing et al. | Feb 2014 | A1 |
20140087862 | Burke | Mar 2014 | A1 |
20140094295 | Nguyen | Apr 2014 | A1 |
20140094316 | Nguyen | Apr 2014 | A1 |
20140121005 | Nelson | May 2014 | A1 |
20140179431 | Nguyen | Jun 2014 | A1 |
20140274306 | Crawford | Sep 2014 | A1 |
20140274309 | Nguyen | Sep 2014 | A1 |
20140274319 | Nguyen | Sep 2014 | A1 |
20140274320 | Nguyen | Sep 2014 | A1 |
20140274342 | Nguyen | Sep 2014 | A1 |
20140274357 | Nguyen | Sep 2014 | A1 |
20140274360 | Nguyen | Sep 2014 | A1 |
20140274367 | Nguyen | Sep 2014 | A1 |
20140274388 | Nguyen | Sep 2014 | A1 |
20150089595 | Telles | Mar 2015 | A1 |
20150133223 | Carter | May 2015 | A1 |
20150143543 | Phegade | Aug 2015 | A1 |
20160125695 | Nguyen | May 2016 | A1 |
20170116819 | Nguyen | Apr 2017 | A1 |
20170116823 | Nguyen | Apr 2017 | A1 |
20170144071 | Nguyen | May 2017 | A1 |
20170148259 | Nguyen | May 2017 | A1 |
20170148261 | Nguyen | May 2017 | A1 |
20170148263 | Nguyen | May 2017 | A1 |
20170206734 | Nguyen | Jul 2017 | A1 |
20170228979 | Nguyen | Aug 2017 | A1 |
20170243440 | Nguyen | Aug 2017 | A1 |
20170337770 | Nguyen | Nov 2017 | A1 |
20180144581 | Nguyen | May 2018 | A1 |
20190005773 | Nguyen | Jan 2019 | A1 |
20190122490 | Nguyen | Apr 2019 | A1 |
20190122492 | Nguyen | Apr 2019 | A1 |
20190213829 | Nguyen | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
2033638 | May 1980 | GB |
2062923 | May 1981 | GB |
2096376 | Oct 1982 | GB |
2097570 | Nov 1982 | GB |
2335524 | Sep 1999 | GB |
12005000454 | May 2007 | PH |
WO 05073933 | Aug 2005 | WO |
WO 2008027621 | Mar 2008 | WO |
WO 2009026309 | Feb 2009 | WO |
WO 2009062148 | May 2009 | WO |
WO 2010017252 | Feb 2010 | WO |
Entry |
---|
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010. |
Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV. |
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009. |
Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009. |
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Ilinois at Urbana Champaign, Jun. 27, 2005. |
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
IAPS, Daily Systems LLC, 2010. |
U.S. Appl. No. 12/945,888, filed Nov. 14, 2010. |
U.S. Appl. No. 12/945,889, filed Nov. 14, 2010. |
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012. |
U.S. Appl. No. 13/800,917, filed Mar. 13, 2013. |
U.S. Appl. No. 13/296,182, filed Nov. 15, 2011. |
U.S. Appl. No. 13/801,234, filed Mar. 13, 2013. |
U.S. Appl. No. 13/801,171, filed Mar. 13, 2013. |
U.S. Appl. No. 13/843,192, filed Mar. 15, 2013. |
U.S. Appl. No. 13/843,087, filed Mar. 15, 2013. |
U.S. Appl. No. 13/632,743, filed Oct. 1, 2012. |
U.S. Appl. No. 13/632,828, filed Oct. 1, 2012. |
U.S. Appl. No. 13/833,953, filed Mar. 15, 2013. |
U.S. Appl. No. 12/619,672, filed Nov. 16, 2009. |
U.S. Appl. No. 13/801,121, filed Mar. 13, 2013. |
U.S. Appl. No. 12/581,115, filed Oct. 17, 2009. |
U.S. Appl. No. 13/801,076, filed Mar. 13, 2013. |
U.S. Appl. No. 13/617,717, filed Nov. 12, 2009. |
U.S. Appl. No. 13/633,118, filed Oct. 1, 2012. |
U.S. Appl. No. 12/797,610, filed Jun. 10, 2010. |
U.S. Appl. No. 13/801,256, filed Mar. 13, 2013. |
U.S. Appl. No. 12/757,968, filed Apr. 9, 2010. |
U.S. Appl. No. 12/797,616, filed Jun. 10, 2010. |
U.S. Appl. No. 13/557,063, filed Jul. 24, 2012. |
U.S. Appl. No. 13/833,116, filed Mar. 15, 2013. |
U.S. Appl. No. 13/801,271, filed Mar. 13, 2011. |
Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013. |
Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013. |
Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
Brochure, 5000 Ft. Inc., 1 page, Nov. 2010. |
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013. |
Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013. |
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015. |
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015. |
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015. |
Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015. |
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015. |
Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016. |
Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016. |
Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016. |
Office Action for U.S. Appl. No. 13/843,087, dated Feb. 25, 2016. |
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016. |
Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016. |
Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016. |
Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016. |
Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016. |
Office Action for U.S. Appl. No. 13/622,702, dated Mar. 22, 2016. |
Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016. |
Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016. |
Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016. |
Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016. |
Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016. |
Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016. |
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 6, 2016. |
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016. |
Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016. |
Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016. |
Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014. |
Final Office Action for U.S. Appl. No. 13/801,234, dated May 22, 2014. |
Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016. |
Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016. |
Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012. |
Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014. |
Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014. |
Notice of Allowance for U.S. Appl. No. 13/843,192, dated Aug. 10, 2016. |
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016. |
Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016. |
Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016. |
Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016. |
Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016. |
Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016. |
Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016. |
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
Office Action for U.S. Appl. No. 13/801,256, dated Aug. 18, 2017. |
Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017. |
Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017. |
Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018. |
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018. |
Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018. |
Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018. |
Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018. |
Final Office Action for U.S. Appl. No. 15/427,308, dated Mar. 19, 2018. |
Office Action for U.S. Appl. No. 15/876,095, dated Apr. 3, 2018. |
Office Action for U.S. Appl. No. 15/835,448, dated Apr. 4, 2018. |
Office Action for U.S. Appl. No. 15/427,307, dated Apr. 9, 2018. |
Office Action for U.S. Appl. No. 14/216,986, dated Apr. 6, 2018. |
Office Action for U.S. Appl. No. 15/426,898 dated Apr. 16, 2018. |
Notice of Allowance for U.S. Appl. No. 15/402,945, dated May 25, 2018. |
Office Action for U.S. Appl. No. 15/495,973, dated Jun. 4, 2018. |
Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018. |
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018. |
Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018. |
Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018. |
Office Action for U.S. Appl. No. 14/993,055, dated Jun. 22, 2018. |
Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018. |
Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018. |
Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018. |
Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018. |
Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018. |
Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018. |
Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018. |
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018. |
Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018. |
Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018. |
Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018. |
Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018. |
Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018. |
Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018. |
Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018. |
Office Action for U.S. Appl. No. 16/162.358, dated Dec. 31, 2018. |
Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019. |
Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019. |
Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019. |
Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019. |
Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019. |
Final Office Action for US Patent 2019. Application No. 15/798,363, mailed Feb. 4,. |
Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019. |
Final Office Action for U.S. Appl. No. 15/495,975, dated Apr. 18, 2019. |
Office Action for U.S. Appl. No. 15/671,133, dated May 1, 2019. |
Notice of Allowance for U.S. Appl. No. 14/216,986, dated May 17, 2019. |
Notice of Allowance for U.S. Appl. No. 14/518,909, dated May 17, 2019. |
Office Action for U.S. Appl. No. 12/797,616, dated Jun. 5, 2019. |
Office Action for U.S. Appl. No. 15/427,308, dated Jun. 14, 2019. |
Office Action for U.S. Appl. No. 15/811,654, dated Jun. 14, 2019. |
Office Action for U.S. Appl. No. 15/674,480, dated Jun. 20, 2019. |
Notice of Allowance for U.S. Appl. No. 15/835,448, dated Jul. 3, 2019. |
Final Office Action for U.S. Appl. No. 16/162,358, dated Jul. 11, 2019. |
Office Action for U.S. Appl. No. 16/190,050, dated Sep. 19, 2019. |
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 9, 2019. |
Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 18, 2019. |
Office Action for U.S. Appl. No. 15/835,448 dated Oct. 12, 2019. |
Notice of Allowance for U.S. Appl. No. 15/495,975, dated Oct. 23, 2019. |
Notice of Allowance for U.S Appl. No. 14/993,005, dated Nov. 27, 2019. |
Final Office Action for U.S. Appl. No. 15/427,308, dated Nov. 27, 2019. |
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 8, 2020. |
Number | Date | Country | |
---|---|---|---|
20170243440 A1 | Aug 2017 | US |
Number | Date | Country | |
---|---|---|---|
61542703 | Oct 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13632743 | Oct 2012 | US |
Child | 15495975 | US |