Control of mobile game play on a mobile vehicle

Information

  • Patent Grant
  • 12246261
  • Patent Number
    12,246,261
  • Date Filed
    Tuesday, September 13, 2022
    2 years ago
  • Date Issued
    Tuesday, March 11, 2025
    a month ago
Abstract
In one embodiment, a system and method for controlling mobile gaming on a vessel may have a plurality of mobile gaming devices, a location server operable to track a device position of each of the plurality of mobile gaming devices and track a vessel position of the vessel, and a mobile gaming management server configured to communicate with the location server and a gaming server, the mobile gaming management server operable to individually control whether each of the plurality of mobile gaming devices is permitted to play a game of chance based on the device position and the vessel position.
Description
BACKGROUND

In a gaming environment, determining when to allow play of a game of chance is important to avoid breaking any gaming rules or laws. However, control of playing game of chance is difficult to monitor when game play is on a mobile device and in a movable environment, such as a cruise ship. There are national and international laws, as well as any other user desired criteria that need to be considered.


SUMMARY

The invention provides for the control of mobile game play on a mobile vessel. In one embodiment, a determination of whether to permit or deny play of the on-board game of chance may be based upon at least a global and local device position of the mobile gaming device. In another embodiment, determination of whether to permit or deny play of the on-board game of chance may be based upon other predefined rules such as a time rule, captain's rule, user defined rules, and other criteria. For example, determination of whether to permit or deny play of the on-board game of chance may be based upon whether the vessel is in international or national waters. In another example, determination of whether to permit or deny play of the on-board game of chance may be based upon the current time.


In one embodiment, a system for controlling mobile gaming on a vessel may have a plurality of mobile gaming devices, each of the plurality of mobile gaming device associated with a player and a location server operable to: (a) track a device position of each of the plurality of mobile gaming devices, the device position being relative to the vessel; and (b) 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 individually control whether each of the plurality of mobile gaming devices is permitted to play a game of chance based on the device position and the vessel position.


In another embodiment, a method for controlling mobile gaming on a vessel may include tracking a vessel position of the vessel, tracking a device position for each of a plurality of mobile gaming devices, receiving a request to play a game of chance from at least one of the plurality of mobile gaming devices, determining whether the game of chance is permitted to be played on the mobile gaming device, the determining based on at least the vessel position of the vessel and the device position of the mobile gaming device, and enabling the game of chance on the mobile gaming device if the determining determines that the game of chance is permitted to be played on the mobile gaming device.


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.





BRIEF DESCRIPTION OF THE DRAWINGS

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:



FIG. 1 is an example block diagram of a game control system.



FIG. 2A illustrates an example diagram of a vessel position of a cruise ship.



FIG. 2B illustrates an example layout of a cruise ship.



FIG. 2C illustrates an example gaming rules table.



FIG. 3 illustrates an example method for controlling play of a game of a chance on a vessel.



FIG. 4 illustrates another example method for controlling play of a game of a chance on a vessel.



FIG. 5 illustrates another example method for controlling play of a game of a chance on a vessel.



FIG. 6 illustrates an example block diagram of a computing device.





DETAILED DESCRIPTION

Embodiments are described herein in the context of control of mobile game play on a mobile vessel. 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 control of on-board game of chance play on a mobile device while on a vessel. A vessel may be any movable transport device such as an airplane, car, bus, and any vehicle in the water, such as cruiseliners, riverboats, and the like. In one embodiment, a determination of whether to permit or deny play of the on-board game of chance may be based upon at least a global and local device position of the mobile gaming device. In another embodiment, determination of whether to permit or deny play of the on-board game of chance 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, determination of whether to permit or deny play of the on-board game of chance may be based upon whether the vessel is in international or national waters. In another example, determination of whether to permit or deny play of the on-board game of chance may be based upon the current time.



FIG. 1 is an example block diagram of a game control system. The game control system 100 may have a mobile gaming management server 102 configured to communicate with a location server 104, a gaming server 106, and a vessel server 108. The mobile gaming management server 102 may be designed as an intermediary server to store data or information such as mobile gaming device information, gaming rules database, player gaming accounts, and any other desired data or information. The mobile gaming device information may be stored in the mobile gaming device database 110 and may include information such as the mobile gaming device identification, information of the user using the mobile gaming device 116, programs on the mobile gaming device 116, and other mobile gaming device data. The mobile gaming device 116 may be any type of portable mobile gaming device such as a mobile phone, a portable media player, a personal digital assistant, a portable gaming device, or any other similar device.


The user of the mobile gaming device 116 may also have a player gaming account 112. The player gaming account 112 may store any information such as user contact information, available funds in the player gaming account, and any other player information. In one embodiment, any wins from a game of chance played by the user of the mobile gaming device 116 may be stored in the player gaming account 112.


Gaming rules may be stored in the gaming rules database 114. The rules may be any criteria used to determine whether to permit or deny play of the game of chance on the mobile device. For example, the determination of whether to permit or deny play of the game of chance may be based on at least the device position of the mobile gaming device and the location of the vessel. If the device is, for example, located near the childcare center and the vessel is in international waters, play of the game of chance may be denied. However, if the user is sitting at a bar and the vessel is in international waters, play of the game of chance may be granted.


In another example, determination to permit or deny play of the game of chance may also be based upon a time rule that may be predetermined by the vessel. For example, the vessel may set games of chance to be played between 7 a.m. to 2 a.m. Thus, if the request to play a game of chance is made at 3 a.m., play of the game of chance may be denied. If the request to play a game of chance is made at 12 p.m., play of the game of chance may be permitted.


The mobile gaming management server 102 may be configured to communicate with a gaming server 106, which may be configured to communicate with the mobile gaming device 116. The mobile gaming device 116 may transmit a request to the gaming server 106 to play at least one game of chance on the mobile gaming device. The gaming server 106 may transmit the request to play the game of chance to the mobile gaming management server 102. The mobile gaming management server 102 may then obtain a device position and a vessel position from the location server 104.


The location server 104 may be configured to determine the location of the mobile gaming device 116 and the vessel. The location server 104 may have a global position server 118 to determine the location of the vessel relative to the globe, earth, or world. Global position server 118 may use any known position or location method to determine the location of the vessel 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 location of the mobile gaming device 116 relative to the vessel. The device position of the mobile gaming device 116 may be the position of the mobile gaming device 116 relative to the vessel. The device position server 120 may use any known position or location method to determine the location of the mobile gaming 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 vessel position of the vessel and the device position of the mobile gaming device. The vessel position and device position may be associated with a mobile gaming device.


Mobile gaming management server 102 may also be configured to communicate with a vessel server 108. Vessel server 108 may be configured to store customer information in the passenger main account database 122. The vessel server 108 may store information such as customer credit card information, address, username and password, date of birth, and any other desired information.


In use, when boarding a vessel, the passenger's information may be stored in the passenger main account 122 in the vessel 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 desired or relevant passenger information.


The passenger may be associated with a mobile gaming device 116 used to play the game of chance. In one embodiment, the mobile gaming device 116 may be provided to the passenger. In another embodiment, the passenger may utilize his own mobile gaming device 116. The passenger may request to play a game of chance on the mobile gaming device 116. 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 gaming device such as biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like).


The request to play a game of chance may be transmitted from the mobile gaming device 116 to the gaming server 106. The gaming server 106 may transmit the request to the mobile gaming management server 102. The mobile gaming management server 102 may determine whether the passenger has a player gaming account 112. If the passenger does not have a player gaming account 112, a player gaming account 112 may be created for the passenger.


The mobile gaming management server 102 may obtain location information from the location server 104. The global position server 118 may determine a global vessel position of the vessel. Referring to FIG. 2A, an example diagram of a vessel position of a cruise ship, the global position server may use any location or position determination methods to determine the position of the cruise ship 202. Although example embodiments illustrate the vessel as a cruise ship, this is not intended to be limiting as any vessel may be used such as a riverboat, and any other movable transport device. The cruise ship 202 may be positioned or located in international waters 206 or national waters 204. Thus, the vessel position may be a global position relative to the world 200. As illustrated, the cruise ship 202 is located in international waters 206.


Referring back to FIG. 1, the device position server 120 of the location server 104 may determine a device position of the mobile gaming device 116 relative to the vessel. Referring to FIG. 2B, an example layout of a cruise ship, the cruise ship 210 may have a main pool 212, pool bar 214, children's pool 216, restaurant 218, night club/bar 220, kids club or childcare center 222, reception 224, and gift store 226 on its main deck. Although example embodiments illustrate the vessel as a cruise ship, this is not intended to be limiting as the vessel may be a car, bus, airplane, train, riverboat, and any other movable transport device. Specific gaming areas may be predetermined on the cruise ship 210. For example, games of chance may be played at the main pool 212, pool bar 214, and night club/bar 220 on the main deck. Games of chance may not be permitted to be played at the children's pool 216, restaurant 218, kids club or childcare center 222, reception 224, and gift store 226. In one example, passenger A 228 may want to play a game of chance while lounging at the main pool 212. The location server may determine that the device position of the mobile gaming device is at or around the main pool area 212. In another embodiment, passenger B 230 may want to play a game of chance while at the kids club or childcare center 222. The location server 104 may determine that the device position of the mobile gaming device is at or around the childcare center 222.


Referring back to FIG. 1, once the vessel position and device position are determined, the information may be associated with the mobile gaming device and stored in the location database 113. The mobile gaming management server 102 may request and obtain location information for each mobile gaming device from the location server 104.


Once obtained, the mobile gaming management server 102 may determine whether play of the game of chance is permitted on the mobile gaming device. The determination may be based upon the gaming rules stored in the gaming rules database 114. For example, since passenger A is located at the main pool area where playing games of chance are permitted, the mobile gaming management server 102 may determine that the game of chance may be played on the mobile gaming device 116 of passenger A.


However, since passenger B is located at the childcare center where playing games of chance are not permitted, the request to play the game of chance will be denied. In this embodiment, a denial message may be transmitted to the mobile gaming 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 gaming management server 102 the game of chance may be enabled on the mobile gaming device 116. The gaming server 106 may transmit the requested game of chance to the mobile gaming device 116.


In another embodiment, the mobile gaming management server 102 may also user other criteria to determine whether to permit or deny play of a game of chance. For example, one criterion may be a time rule. A time stamp on the request to play the game of chance may be used to determine whether the game of chance may be played on the mobile gaming device. If the time stamp was at 3 a.m., the game of chance may not be permitted to be played. If the time stamp was at 10 a.m., the game of chance may be permitted to be played. 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 passenger 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. It will now be appreciated that the mobile gaming management server 102 may use any other desired criteria to determine whether or not to permit play of the game of chance on the mobile gaming device 116.



FIG. 2C illustrates an example gaming rules table. The gaming rules table may be stored, for example, in the gaming rules database 114 illustrated in FIG. 1. The gaming rules table 240 may include criteria used to determine whether to permit play of the game of chance 252 on the mobile gaming device. Each criterion may be associated with a device 242. As illustrated, the criteria may be based on device position 244, vessel position 246, and time 248.


Device 1 254 may be located at the main pool in international waters. A request 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 gaming management server 102 may determine that the game of chance may be played on the mobile gaming device.


Device 2 256 may be located at the childcare center in international waters. A request 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 gaming management server 102 may determine that the game of chance may not be played on the mobile gaming device.


Device 3 258 may be located at the night club in international waters. A request to play a game of chance may be received at 11 p.m. Based on the device position, vessel position, and time rule, the mobile gaming management server 102 may determine that the game of chance may be played on the mobile gaming device.



FIG. 3 illustrates an example method for controlling play of a game of a chance on a cruise ship. The method 300 may begin with receiving a request to play a game of chance from a mobile gaming device at 302. The request may be transferred to a gaming server, e.g. such as gaming server 106 illustrated in FIG. 1. The gaming server may transmit the request to an intermediary server, e.g. such as mobile gaming management server 102 illustrated in FIG. 1. The intermediary server may determine whether the passenger has a player gaming account at 304. If the passenger does not have a player gaming account, a player gaming account may be created for the passenger 306.


The intermediary server may obtain a vessel position of the vessel and device position of the mobile gaming device at 308. The vessel position and device position may be obtained from, for example, a location server e.g. such as location server 104 illustrated in FIG. 1. The vessel position of the vessel may be a position relative to the world. The device position of the mobile gaming device may be a position relative to the vessel.


Once obtained, the intermediary server may determine whether to permit or deny play of the game of chance at 310. The determination may be based upon the gaming rules stored in a gaming rules database, e.g. such as gaming rules database 114 illustrated in FIG. 1. In one embodiment, the determination whether to permit or deny play of the game of chance may be based on at least the device position and the vessel position. In another embodiment, the determination whether to transfer permit or deny play of the game of chance may be based on at least time rules, user information, or any other predetermined criteria.


If the intermediary server determines that play of the game of chance is not permitted at 310, the method 300 may end. If the intermediary server determines that play of the game of chance is permitted at 310, the game of chance may be enabled on the mobile gaming device at 312.



FIG. 4 illustrates another example method for controlling play of a game of a chance on a vessel. The method 400 may begin with the vessel position and device position being periodically updated at 402. The vessel position and device position may be periodically updated by a location server, e.g. such as location server 104 illustrated in FIG. 1. Updating the vessel position and device position ensures that play of the games of chance, are carried out only in allowable areas, environments and times. The intermediary server may determine whether the game of chance may be permitted to be played on the mobile gaming device at 404. In one embodiment, the determination of whether the game of chance may be permitted to be played on the mobile gaming device may be based upon the updated vessel position and updated device position. For example, although the original device position may have been in an area where playing games of chance is permitted, the updated device position may now indicate the mobile gaming device is located at a location where playing games of chance is not permitted. In one embodiment, the determination of whether the game of chance may be permitted to be played on the mobile gaming device may also be based upon an updated time as well. For example, although the time may have been a time when playing games of chance is permitted (e.g. 7 am-3 am), the updated time may now indicate the mobile gaming device is being played at a time when playing games of chance is not permitted (e.g. 3 am-7 am).


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 gaming 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 gaming 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. The game of chance may be terminated on the mobile gaming device within a predetermined time period at 408. The predetermined time period may allow the player to complete play of the game of chance, cash out, and perform any other functions prior to ending play of the game of chance.



FIG. 5 illustrates another example method for controlling play of a game of a chance on a vessel. The method 500 may begin with receipt of a request to play a game of chance from a mobile gaming device at 502. The request may include a time stamp. The request may be transferred to a gaming server, e.g. such as gaming server 106 illustrated in FIG. 1. The gaming server may transmit the request to an intermediary server, e.g. such as mobile gaming management server 102 illustrated in FIG. 1.


The intermediary server may obtain a vessel position of the vessel and device position of the mobile gaming device at 504. The vessel position and device position may be obtained from a location server, e.g. such as location server 104 illustrated in FIG. 1. The vessel position of the vessel may be a position relative to the world or earth. The device position of the mobile gaming device may be a position relative to the vessel.


Once obtained, the intermediary server may determine whether the game of chance may be played on the mobile gaming device based upon the vessel position at 506. If it is determined that the game of chance may not be played on the mobile gaming 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 gaming device based upon the vessel position at 506, a determination of whether the game of chance may be played on the mobile gaming device based upon the device position at 508.


If it is determined that the game of chance may not be played on the mobile gaming 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 gaming device based upon the device position at 508, a determination of whether the game of chance may be played on the mobile gaming device based upon the time stamp at 510. If it is determined that the game of chance may not be played on the mobile gaming 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 gaming device based upon the time stamp at 510, passenger information (e.g. username and password, date of birth, and any other player information) may be obtained from the passenger main account at 512. A determination of whether to permit the game of chance to be played on the mobile gaming device based on player information may be made at 514. The determination of whether the game of chance may be played on the mobile gaming device based upon the vessel position, device position, time stamp, or passenger information may be similar to the determination described above with respect to FIGS. 1, 2A, 2B, 3 and 4.


If it is determined that the game of chance may be played on the mobile gaming device based on passenger information at 514, the game of chance may be enabled on the mobile gaming device at 516.



FIG. 6 illustrates an example block diagram of a computing device. The computing device 600 can represent circuitry of a representative computing device (e.g. mobile gaming device, mobile gaming device management sever, location server, cruise ship server, gaming server) described and illustrated in FIG. 1. The computing device can be designed to primarily stationary or can be portable.


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 gaming device 116, cruise ship server 108, mobile gaming management server 102, location server 104, gaming server 106 illustrated in FIG. 1) is a mobile gaming device, the computing device 600 may store a plurality of games of chance in the file system 604. When a user desires to have the computing device play a particular game of chance, a list of available games of chance is displayed on the display 610. Then, using the user input device 608, a user can select one of the games of chance to play. The processor 602, upon receiving a selection of a particular media item, supplies the game of chance data to one or more appropriate output devices. If the particular media item is encrypted, the particular media item is first decrypted as noted above, which could involve one or more layers of encryption. As an example, for audio output, the processor 602 can supply the media data (e.g., audio file) for the particular media item to the audio CODEC 612. The audio CODEC 612 can then produce analog output signals for a speaker 614. The speaker 614 can be a speaker internal to the computing device 600 or external to the computing device 600. For example, headphones or earphones that connect to the computing device 600 would be considered an external speaker. As another example, for video output, the processor 602 can supply the media data (e.g., video file) for the particular media item to the video CODEC 615. The video CODEC 615 can then produce output signals for the display 610 and/or the speaker 614.


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.

Claims
  • 1. A system for managing play of a game of chance in a vessel, the system comprising: a plurality of mobile devices operable to play the game of chance; anda server, operable to be coupled to the plurality of mobile devices, comprising at least one processor and memory storing instructions, which, when executed, cause the at least one processor to at least: receive a request including a time-stamp to play the game of chance in the vessel from a first mobile device among the plurality of mobile devices;determine a global position of the vessel with respect to earth based on the request received;determine a local position of the first mobile device within the vessel based on the request received;enable the first mobile device to play the game of chance requested in the vessel, when the global position is in an allowed geographical area and the local position of the first mobile device is within an allowed area of the vessel, based on the time-stamp received; andtransmit the game of chance requested to the first mobile device that has been enabled.
  • 2. The system of claim 1, wherein the memory further comprises a player account, and the instructions, when executed, further cause the at least one processor to authenticate the first mobile device based on the player account.
  • 3. The system of claim 2, wherein the instructions, when executed, further cause the at least one processor to deny the first mobile device from playing the game of chance requested when the first mobile device is not successfully authenticated based on the player account.
  • 4. The system of claim 1, wherein the instructions, when executed, further cause the at least one processor to enable the first mobile device to transfer fund for the game of chance requested based on the time-stamp with respect to a predefined time rule associated with the vessel.
  • 5. The system of claim 1, wherein the first mobile device includes a transceiver operable to communicate with the server wirelessly when coupled.
  • 6. The system of claim 1, wherein the instructions, when executed, further cause the at least one processor to terminate the first mobile device from playing the game of chance requested when the local position of the first mobile device is at a prohibited area within the vessel regardless of the time-stamp or the global position determined.
  • 7. The system of claim 1, wherein the instructions, when executed, further cause the at least one processor to periodically update the global position, the local position and a current time with respect of the time-stamp received.
  • 8. A method of managing play of a game of chance on a vessel in a system having a plurality of mobile devices operable to play the game of chance, and a server, operable to be coupled to the plurality of mobile devices, comprising at least one processor and memory storing instructions, which, when executed, cause the at least one processor to initiate a game, the method comprising: time-stamping a request received from a first mobile device among the plurality of mobile devices to play the game of chance in the vessel;determining a global position of the vessel with respect to earth based on the request received;determining a local position of the first mobile device in the vessel based on the request received; andtransmitting the game of chance requested to the first mobile device, when the vessel is positioned in an allowed geographical area and the first mobile device is positioned in an allowed vessel area in the vessel, based on the time-stamp received.
  • 9. The method of claim 8, wherein the memory further comprises a player account, further comprising authenticating the first mobile device based on the player account, and denying the first mobile device from playing the game of chance requested when the first mobile device is not successfully authenticated based on the player account.
  • 10. The method of claim 8, further comprising enabling the first mobile device to transfer fund for the game of chance requested based on the request with respect to a predefined time rule associated with the vessel.
  • 11. The method of claim 8, wherein the first mobile device includes a transceiver, further comprising enabling the transceiver to communicate with the server wirelessly when coupled.
  • 12. The method of claim 8, further comprising terminating the first mobile device from playing the game of chance requested when the local position of the first mobile device is at a prohibited area within the vessel regardless of the request that has been time-stamped or the global position determined.
  • 13. The method of claim 8, further comprising periodically updating the global position, the local position and a current time with respect of the request that has been time-stamped.
  • 14. A non-transitory computer-readable medium comprising instructions, for managing a game on a gaming system including a plurality of mobile devices operable to play a game of chance in a vessel, and a server operable to be coupled to the plurality of mobile devices and having at least one processor, and the instructions, which, when executed, cause one or more processors to perform the steps of: receiving a request including a time-stamp to play the game of chance in the vessel from a first mobile device among the plurality of mobile devices;determining a global position of the vessel with respect to earth based on the request received;determining a local position of the first mobile device in the vessel based on the request received;enabling the first mobile device to play the game of chance requested in the vessel, when the global position is in an allowed geographical area and the local position of the first mobile device is within an allowed area of the vessel, based on the time-stamp received; andtransmitting the game of chance requested to the first mobile device that has been enabled.
  • 15. The transitory computer-readable medium of claim 14, further comprising a player account, and wherein the instructions, when executed, further cause the at least one processor to perform the step of authenticating the first mobile device based on the player account.
  • 16. The transitory computer-readable medium of claim 15, wherein the instructions, when executed, further cause the at least one processor to the step of denying the first mobile device from playing the game of chance requested when the first mobile device is not successfully authenticated based on the player account.
  • 17. The transitory computer-readable medium of claim 14, wherein the instructions, when executed, further cause the at least one processor to the step of enabling the first mobile device to transfer fund for the game of chance requested based on the time-stamp with respect to a predefined time rule associated with the vessel.
  • 18. The transitory computer-readable medium of claim 14, wherein the first mobile device includes a transceiver operable to communicate with the server wirelessly when coupled.
  • 19. The transitory computer-readable medium of claim 14, wherein the instructions, when executed, further cause the at least one processor to perform the step of terminating the first mobile device from playing the game of chance requested when the local position of the first mobile device is at a prohibited area within the vessel regardless of the time-stamp or the global position determined.
  • 20. The transitory computer-readable medium of claim 14, wherein the instructions, when executed, further cause the at least one processor to perform the step of periodically updating the global position, the local position and a current time with respect of the time-stamp received.
RELATED APPLICATIONS

The present application is a continuation of and claims priority to U.S. patent application Ser. No. 16/735,691, filed Jan. 6, 2020, and entitled “Control of Mobile Game Play on a Mobile Vehicle,” which is a continuation of U.S. patent application Ser. No. 15/426,898, filed Feb. 7, 2017, issued on Jan. 21, 2020, as U.S. Pat. No. 10,537,808, and entitled “Control of Mobile Game Play on a Mobile Vehicle,” which is a continuation of U.S. patent application Ser. No. 13/632,828, filed Oct. 1, 2012, issued on Apr. 25, 2017, as U.S. Pat. No. 9,630,096, and entitled “Control of Mobile Game Play on a Mobile Vehicle,” which claims priority benefit of U.S. Provisional Application No. 61/542,705, filed Oct. 3, 2011, and entitled “Control Of Mobile Game Play on a Cruise Ship,” all of which are hereby incorporated by reference in their entireties.

US Referenced Citations (579)
Number Name Date Kind
2033638 Koppl Mar 1936 A
2062923 Nagy Dec 1936 A
4741539 Sutton May 1988 A
4948138 Pease Aug 1990 A
5067712 Georgilas Nov 1991 A
5275400 Weingardt Jan 1994 A
5429361 Raven Jul 1995 A
5489103 Okamoto Feb 1996 A
5630757 Gagin May 1997 A
5655961 Acres 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 Jul 1999 A
5947820 Morro Sep 1999 A
5997401 Crawford Dec 1999 A
6001016 Walker Dec 1999 A
6039648 Guinn Mar 2000 A
6059289 Vancura May 2000 A
6089977 Bennett Jul 2000 A
6095920 Sadahiro Aug 2000 A
6110041 Walker Aug 2000 A
6142872 Walker Nov 2000 A
6146271 Kadlic 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 Aug 2001 B1
6290600 Glasson Sep 2001 B1
6293866 Walker Sep 2001 B1
6353390 Beri Mar 2002 B1
6364768 Acres Apr 2002 B1
6404884 Marwell Jun 2002 B1
6416406 Duhamel Jul 2002 B1
6416409 Jordan Jul 2002 B1
6443452 Brune Sep 2002 B1
6491584 Graham Dec 2002 B2
6505095 Kolls Jan 2003 B1
6508710 Paravia Jan 2003 B1
6561900 Baerlocher May 2003 B1
6592457 Frohm Jul 2003 B1
6612574 Cole Sep 2003 B1
6620046 Rowe Sep 2003 B2
6641477 Dietz, II Nov 2003 B1
6645078 Mattice Nov 2003 B1
6719630 Seelig Apr 2004 B1
6749510 Giobbi Jun 2004 B2
6758757 Luciano, Jr. Jul 2004 B2
6773345 Walker Aug 2004 B2
6778820 Tendler Aug 2004 B2
6780111 Cannon Aug 2004 B2
6799032 McDonnell Sep 2004 B2
6800027 Giobbi Oct 2004 B2
6804763 Stockdale Oct 2004 B1
6811486 Luciano, Jr. Nov 2004 B1
6843725 Nelson Jan 2005 B2
6846238 Wells Jan 2005 B2
6848995 Walker Feb 2005 B1
6852029 Baltz Feb 2005 B2
6869361 Sharpless Mar 2005 B2
6875106 Weiss Apr 2005 B2
6884170 Rowe Apr 2005 B2
6884172 Lloyd Apr 2005 B1
6902484 Idaka Jun 2005 B2
6908390 Nguyen Jun 2005 B2
6913532 Baerlocher Jul 2005 B2
6923721 Luciano Aug 2005 B2
6935958 Nelson Aug 2005 B2
6949022 Showers Sep 2005 B1
6955600 Glavich Oct 2005 B2
6971956 Rowe Dec 2005 B2
6984174 Cannon Jan 2006 B2
6997803 Lemay Feb 2006 B2
7018292 Tracy Mar 2006 B2
7032115 Kashani Apr 2006 B2
7033276 Walker Apr 2006 B2
7035626 Luciano, Jr. Apr 2006 B1
7037195 Schneider May 2006 B2
7048628 Schneider May 2006 B2
7048630 Berg May 2006 B2
7063617 Brosnan Jun 2006 B2
7076329 Kolls Jul 2006 B1
7089264 Guido Aug 2006 B1
7094148 Baerlocher 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 Jan 2007 B2
7169052 Beaulieu Jan 2007 B2
7175523 Gilmore Feb 2007 B2
7181228 Boesch Feb 2007 B2
7182690 Giobbi Feb 2007 B2
7198571 Lemay Apr 2007 B2
RE39644 Alcorn May 2007 E
7217191 Cordell May 2007 B2
7243104 Bill Jul 2007 B2
7247098 Bradford Jul 2007 B1
7259718 Patterson Aug 2007 B2
7275989 Moody Oct 2007 B2
7285047 Gelb Oct 2007 B2
7311608 Danieli Dec 2007 B1
7314408 Cannon Jan 2008 B2
7316615 Soltys Jan 2008 B2
7316619 Nelson Jan 2008 B2
7318775 Brosnan Jan 2008 B2
7326116 O'Donovan Feb 2008 B2
7330108 Thomas Feb 2008 B2
7346358 Wood Mar 2008 B2
7355112 Laakso Apr 2008 B2
7384338 Rothschild Jun 2008 B2
7387571 Walker Jun 2008 B2
7393278 Gerson Jul 2008 B2
7396990 Lu Jul 2008 B2
7415426 Williams Aug 2008 B2
7425177 Rodgers Sep 2008 B2
7427234 Soltys Sep 2008 B2
7427236 Kaminkow Sep 2008 B2
7427708 Ohmura Sep 2008 B2
7431650 Kessman Oct 2008 B2
7448949 Kaminkow Nov 2008 B2
7500913 Baerlocher Mar 2009 B2
7510474 Carter, Sr. Mar 2009 B2
7513828 Nguyen Apr 2009 B2
7519838 Suurballe Apr 2009 B1
7559838 Walker Jul 2009 B2
7563167 Walker Jul 2009 B2
7572183 Olivas Aug 2009 B2
7585222 Muir Sep 2009 B2
7602298 Thomas Oct 2009 B2
7607174 Kashchenko Oct 2009 B1
7611409 Muir Nov 2009 B2
7637810 Amaitis Dec 2009 B2
7644861 Alderucci Jan 2010 B2
7653757 Fernald Jan 2010 B1
7693306 Huber Apr 2010 B2
7699703 Muir Apr 2010 B2
7722453 Lark May 2010 B2
7758423 Foster Jul 2010 B2
7771271 Walker Aug 2010 B2
7780529 Rowe Aug 2010 B2
7780531 Englman Aug 2010 B2
7785192 Canterbury Aug 2010 B2
7811172 Asher Oct 2010 B2
7819749 Fish Oct 2010 B1
7822688 Labrou Oct 2010 B2
7828652 Nguyen Nov 2010 B2
7828654 Carter, Sr. Nov 2010 B2
7828661 Fish Nov 2010 B1
7850528 Wells Dec 2010 B2
7874919 Paulsen Jan 2011 B2
7877798 Saunders Jan 2011 B2
7883413 Paulsen Feb 2011 B2
7892097 Muir Feb 2011 B2
7909692 Nguyen Mar 2011 B2
7909699 Parrott Mar 2011 B2
7918728 Nguyen Apr 2011 B2
7927211 Rowe Apr 2011 B2
7927212 Hedrick Apr 2011 B2
7951008 Wolf May 2011 B2
8057298 Nguyen Nov 2011 B2
8057303 Rasmussen Nov 2011 B2
8087988 Nguyen Jan 2012 B2
8117608 Slettehaugh Feb 2012 B1
8133113 Nguyen Mar 2012 B2
8182326 Speer, II May 2012 B2
8210927 Hedrick Jul 2012 B2
8221245 Walker Jul 2012 B2
8226459 Barrett Jul 2012 B2
8226474 Nguyen Jul 2012 B2
8231456 Zielinski Jul 2012 B2
8235803 Loose Aug 2012 B2
8282475 Nguyen Oct 2012 B2
8323099 Durham Dec 2012 B2
8337290 Nguyen Dec 2012 B2
8342946 Amaitis Jan 2013 B2
8393948 Allen Mar 2013 B2
8403758 Hornik Mar 2013 B2
8430745 Agarwal 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 Dec 2013 B2
8696470 Nguyen Apr 2014 B2
8745417 Huang Jun 2014 B2
8834254 Buchholz Sep 2014 B2
8858323 Nguyen Oct 2014 B2
8864586 Nguyen Oct 2014 B2
8942995 Kerr Jan 2015 B1
9039507 Allen May 2015 B2
9235952 Nguyen Jan 2016 B2
9292996 Davis 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 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 Apr 2002 A1
20020043759 Vancura Apr 2002 A1
20020045474 Singer Apr 2002 A1
20020107065 Rowe Aug 2002 A1
20020111210 Luciano Aug 2002 A1
20020111213 McEntee Aug 2002 A1
20020113369 Weingardt Aug 2002 A1
20020116615 Nguyen Aug 2002 A1
20020133418 Hammond Sep 2002 A1
20020137217 Rowe Sep 2002 A1
20020142825 Lark Oct 2002 A1
20020147047 Letovsky Oct 2002 A1
20020147049 Carter Oct 2002 A1
20020151366 Walker Oct 2002 A1
20020152120 Howington Oct 2002 A1
20020167536 Valdes Nov 2002 A1
20020177483 Cannon Nov 2002 A1
20020183105 Cannon Dec 2002 A1
20030001338 Bennett Jan 2003 A1
20030003996 Nguyen Jan 2003 A1
20030004871 Rowe Jan 2003 A1
20030008696 Abecassis Jan 2003 A1
20030027635 Walker Feb 2003 A1
20030064805 Wells Apr 2003 A1
20030064807 Walker Apr 2003 A1
20030092480 White May 2003 A1
20030100361 Sharpless May 2003 A1
20030104860 Cannon Jun 2003 A1
20030104865 Itkis Jun 2003 A1
20030148809 Nelson Aug 2003 A1
20030162588 Brosnan Aug 2003 A1
20030195024 Slattery Oct 2003 A1
20030199295 Vancura Oct 2003 A1
20030224852 Walker Dec 2003 A1
20030224854 Joao Dec 2003 A1
20040002386 Wolfe Jan 2004 A1
20040005919 Walker Jan 2004 A1
20040023709 Beaulieu Feb 2004 A1
20040023716 Gauselmann Feb 2004 A1
20040038736 Bryant Feb 2004 A1
20040048650 Mierau Mar 2004 A1
20040068460 Feeley Apr 2004 A1
20040082385 Silva Apr 2004 A1
20040106449 Walker Jun 2004 A1
20040127277 Walker Jul 2004 A1
20040127290 Walker Jul 2004 A1
20040137987 Nguyen Jul 2004 A1
20040147308 Walker Jul 2004 A1
20040152508 Lind Aug 2004 A1
20040199631 Natsume Oct 2004 A1
20040214622 Atkinson Oct 2004 A1
20040224753 O'Donovan Nov 2004 A1
20040256803 Ko Dec 2004 A1
20040259633 Gentles Dec 2004 A1
20050003890 Hedrick Jan 2005 A1
20050004980 Vadjinia Jan 2005 A1
20050026696 Hashimoto Feb 2005 A1
20050054446 Kammler Mar 2005 A1
20050101376 Walker May 2005 A1
20050101383 Wells May 2005 A1
20050130728 Nguyen Jun 2005 A1
20050130731 Englman Jun 2005 A1
20050137014 Vetelainen Jun 2005 A1
20050170883 Muskin Aug 2005 A1
20050181865 Luciano, Jr. Aug 2005 A1
20050181870 Nguyen Aug 2005 A1
20050181875 Hoehne Aug 2005 A1
20050187020 Amaitis Aug 2005 A1
20050202875 Murphy Sep 2005 A1
20050209002 Blythe Sep 2005 A1
20050221881 Lannert Oct 2005 A1
20050223219 Gatto Oct 2005 A1
20050239546 Hedrick Oct 2005 A1
20050255919 Nelson Nov 2005 A1
20050273635 Wilcox Dec 2005 A1
20050277471 Russell Dec 2005 A1
20050282637 Gatto Dec 2005 A1
20060009283 Englman Jan 2006 A1
20060036874 Cockerille Feb 2006 A1
20060046822 Kaminkow Mar 2006 A1
20060046830 Webb Mar 2006 A1
20060046849 Kovacs Mar 2006 A1
20060068893 Jaffe Mar 2006 A1
20060073869 Lemay Apr 2006 A1
20060073897 Englman Apr 2006 A1
20060079317 Flemming Apr 2006 A1
20060126529 Hardy Jun 2006 A1
20060148551 Walker Jul 2006 A1
20060189382 Muir Aug 2006 A1
20060217170 Roireau Sep 2006 A1
20060217193 Walker Sep 2006 A1
20060247028 Brosnan Nov 2006 A1
20060247035 Rowe Nov 2006 A1
20060252530 Oberberger Nov 2006 A1
20060253481 Guido Nov 2006 A1
20060281525 Borissov Dec 2006 A1
20060281541 Nguyen Dec 2006 A1
20060287106 Jensen Dec 2006 A1
20070004510 Underdahl Jan 2007 A1
20070026935 Wolf Feb 2007 A1
20070026942 Kinsley Feb 2007 A1
20070054739 Amaitis Mar 2007 A1
20070060254 Muir Mar 2007 A1
20070060306 Amaitis Mar 2007 A1
20070060319 Block Mar 2007 A1
20070060358 Amaitis Mar 2007 A1
20070077981 Hungate Apr 2007 A1
20070087833 Feeney Apr 2007 A1
20070087834 Moser Apr 2007 A1
20070093299 Bergeron Apr 2007 A1
20070129123 Eryou Jun 2007 A1
20070129148 Van Luchene Jun 2007 A1
20070149279 Norden Jun 2007 A1
20070149286 Bemmel Jun 2007 A1
20070159301 Hirt Jul 2007 A1
20070161402 Ng Jul 2007 A1
20070184896 Dickerson Aug 2007 A1
20070184904 Lee Aug 2007 A1
20070191109 Crowder Aug 2007 A1
20070207852 Nelson Sep 2007 A1
20070207854 Wolf Sep 2007 A1
20070238505 Okada Oct 2007 A1
20070241187 Alderucci Oct 2007 A1
20070248036 Nevalainen Oct 2007 A1
20070257430 Hardy Nov 2007 A1
20070259713 Fiden Nov 2007 A1
20070259717 Mattice Nov 2007 A1
20070270213 Nguyen Nov 2007 A1
20070275777 Walker Nov 2007 A1
20070275779 Amaitis Nov 2007 A1
20070281782 Amaitis Dec 2007 A1
20070281785 Amaitis Dec 2007 A1
20070298873 Nguyen Dec 2007 A1
20080013906 Matsuo Jan 2008 A1
20080015032 Bradford Jan 2008 A1
20080020824 Cuddy Jan 2008 A1
20080020845 Low Jan 2008 A1
20080032787 Low Feb 2008 A1
20080070652 Nguyen Mar 2008 A1
20080070681 Marks Mar 2008 A1
20080076505 Nguyen Mar 2008 A1
20080076506 Nguyen Mar 2008 A1
20080076548 Paulsen Mar 2008 A1
20080076572 Nguyen Mar 2008 A1
20080096650 Baerlocher Apr 2008 A1
20080102916 Kovacs May 2008 A1
20080102956 Burman May 2008 A1
20080102957 Burman May 2008 A1
20080113772 Burrill 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 Jun 2008 A1
20080150902 Edpalm Jun 2008 A1
20080153583 Huntley Jun 2008 A1
20080161110 Campbell Jul 2008 A1
20080167106 Lutnick Jul 2008 A1
20080182667 Davis Jul 2008 A1
20080207307 Cunningham, II Aug 2008 A1
20080214258 Brosnan Sep 2008 A1
20080215319 Lu Sep 2008 A1
20080234047 Nguyen Sep 2008 A1
20080238610 Rosenberg Oct 2008 A1
20080248849 Lutnick Oct 2008 A1
20080248865 Tedesco Oct 2008 A1
20080252419 Batchelor Oct 2008 A1
20080254878 Saunders Oct 2008 A1
20080254881 Lutnick Oct 2008 A1
20080254883 Patel Oct 2008 A1
20080254891 Saunders Oct 2008 A1
20080254892 Saunders Oct 2008 A1
20080254897 Saunders Oct 2008 A1
20080263173 Weber Oct 2008 A1
20080300058 Sum Dec 2008 A1
20080305864 Kelly Dec 2008 A1
20080305865 Kelly Dec 2008 A1
20080305866 Kelly Dec 2008 A1
20080311994 Amaitis Dec 2008 A1
20080318669 Buchholz Dec 2008 A1
20080318686 Crowder Dec 2008 A1
20090005165 Arezina Jan 2009 A1
20090011822 Englman Jan 2009 A1
20090017906 Jackson Jan 2009 A1
20090021381 Kondo Jan 2009 A1
20090029766 Lutnick Jan 2009 A1
20090054149 Brosnan Feb 2009 A1
20090077396 Tsai Mar 2009 A1
20090088258 Saunders Apr 2009 A1
20090098925 Gagner Apr 2009 A1
20090104977 Zielinski Apr 2009 A1
20090104983 Okada Apr 2009 A1
20090118002 Lyons May 2009 A1
20090118013 Finnimore May 2009 A1
20090118022 Lyons May 2009 A1
20090124366 Aoki May 2009 A1
20090124390 Seelig May 2009 A1
20090131146 Arezina May 2009 A1
20090131151 Harris May 2009 A1
20090132163 Ashley, Jr. May 2009 A1
20090137255 Ashley, Jr. May 2009 A1
20090138133 Buchholz May 2009 A1
20090143141 Wells Jun 2009 A1
20090149245 Fabbri Jun 2009 A1
20090149261 Chen Jun 2009 A1
20090153342 Thorn Jun 2009 A1
20090156303 Kiely Jun 2009 A1
20090163272 Baker Jun 2009 A1
20090176578 Herrmann Jul 2009 A1
20090191962 Hardy Jul 2009 A1
20090197684 Arezina Aug 2009 A1
20090216547 Canora Aug 2009 A1
20090219901 Bull Sep 2009 A1
20090221342 Katz Sep 2009 A1
20090227302 Abe Sep 2009 A1
20090239666 Hall Sep 2009 A1
20090264190 Davis Oct 2009 A1
20090270170 Patton Oct 2009 A1
20090271287 Halpern Oct 2009 A1
20090275410 Kisenwether Nov 2009 A1
20090275411 Kisenwether Nov 2009 A1
20090280910 Gagner 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 Feb 2010 A1
20100056248 Acres Mar 2010 A1
20100062833 Mattice Mar 2010 A1
20100062840 Herrmann Mar 2010 A1
20100079237 Falk Apr 2010 A1
20100081501 Carpenter Apr 2010 A1
20100081509 Burke Apr 2010 A1
20100099499 Amaitis Apr 2010 A1
20100106612 Gupta Apr 2010 A1
20100115591 Kane-Esrig May 2010 A1
20100120486 Dewaal May 2010 A1
20100124967 Lutnick May 2010 A1
20100130276 Fiden May 2010 A1
20100160035 Herrmann Jun 2010 A1
20100160043 Fujimoto Jun 2010 A1
20100178977 Kim Jul 2010 A1
20100184509 Sylla Jul 2010 A1
20100197383 Rader Aug 2010 A1
20100197385 Aoki Aug 2010 A1
20100203955 Sylla Aug 2010 A1
20100203963 Allen Aug 2010 A1
20100227662 Speer, II Sep 2010 A1
20100227670 Arezina Sep 2010 A1
20100227671 Laaroussi Sep 2010 A1
20100227687 Speer, II Sep 2010 A1
20100234091 Baerlocher Sep 2010 A1
20100279764 Allen Nov 2010 A1
20100323780 Acres Dec 2010 A1
20100325703 Etchegoyen Dec 2010 A1
20110009181 Speer, II Jan 2011 A1
20110039615 Acres Feb 2011 A1
20110053679 Canterbury Mar 2011 A1
20110065492 Acres Mar 2011 A1
20110105216 Cohen May 2011 A1
20110111827 Nicely May 2011 A1
20110111843 Nicely May 2011 A1
20110111860 Nguyen May 2011 A1
20110118010 Brune May 2011 A1
20110159966 Gura 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 Sep 2011 A1
20110223993 Allen Sep 2011 A1
20110244952 Schueller Oct 2011 A1
20110263318 Agarwal Oct 2011 A1
20110269548 Barclay Nov 2011 A1
20110306400 Nguyen Dec 2011 A1
20110306426 Novak Dec 2011 A1
20120015709 Bennett Jan 2012 A1
20120028703 Anderson Feb 2012 A1
20120028718 Barclay Feb 2012 A1
20120034968 Watkins Feb 2012 A1
20120046110 Amaitis Feb 2012 A1
20120094769 Nguyen Apr 2012 A1
20120100908 Wells Apr 2012 A1
20120108319 Caputo May 2012 A1
20120122561 Hedrick May 2012 A1
20120122567 Gangadharan May 2012 A1
20120122584 Nguyen May 2012 A1
20120122590 Nguyen May 2012 A1
20120172130 Acres Jul 2012 A1
20120184362 Barclay Jul 2012 A1
20120184363 Barclay 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 Dec 2012 A1
20120330740 Pennington Dec 2012 A1
20130005433 Holch Jan 2013 A1
20130005443 Kosta Jan 2013 A1
20130005453 Nguyen Jan 2013 A1
20130059650 Sylla Mar 2013 A1
20130065668 Lemay Mar 2013 A1
20130103965 Golembeski, Jr. Apr 2013 A1
20130104193 Gatto Apr 2013 A1
20130132745 Schoening 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 Aug 2013 A1
20130252730 Joshi Sep 2013 A1
20130281188 Guinn Oct 2013 A1
20130316808 Nelson Nov 2013 A1
20130337878 Shepherd Dec 2013 A1
20140006129 Heath Jan 2014 A1
20140057716 Massing 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, III 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, Sr. May 2015 A1
20150143543 Phegade May 2015 A1
20160125695 Nguyen May 2016 A1
20170016819 Barwicz Jan 2017 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
Foreign Referenced Citations (11)
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 JP
2005073933 Aug 2005 WO
2008027621 Mar 2008 WO
2009026309 Feb 2009 WO
2009062148 May 2009 WO
2010017252 Feb 2010 WO
Non-Patent Literature Citations (236)
Entry
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.
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.
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012.
Advisory Action for U.S. Appl. No. 13/632,828, mailed Feb. 25, 2016.
Notice of Allowance for U.S. Appl. No. 13/843,192, mailed Aug. 10, 2016.
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jun. 1, 2022 for U.S. Appl. No. 16/735,691 (pp. 1-5).
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jul. 7, 2022 for U.S. Appl. No. 16/735,691 (pp. 1-2).
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 Illinois 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/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,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, 2013.
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.
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 Office Action 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.
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, mailed 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.
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.
Non-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 Office Action for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014.
Final Office Action 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/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.
Related Publications (1)
Number Date Country
20230001306 A1 Jan 2023 US
Provisional Applications (1)
Number Date Country
61542705 Oct 2011 US
Continuations (3)
Number Date Country
Parent 16735691 Jan 2020 US
Child 17944136 US
Parent 15426898 Feb 2017 US
Child 16735691 US
Parent 13632828 Oct 2012 US
Child 15426898 US