System and method for retrieving remote device information

• US 20040127291A1
• Filed: 09/12/2003
• Published: 07/01/2004
• Est. Priority Date: 09/28/2001
• Status: Abandoned Application

• Current Assignee: Konami Gaming Incorporated (Konami Holdings Corp.)
• Original Assignee: Konami Gaming Incorporated (Konami Holdings Corp.)
• Inventors: George, Jeffrey, Huber, Doug, Huang, Zhiguo, Pochin, John-Paul
• Application Number:
  US10/661,450
• Publication Number:
  US 20040127291A1
• Time in Patent Office: Days
• US Class Current: 463/42
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements
• CPC Class Codes: G07F 17/3227 Configuring a gaming machine, e.g. downloading personal settings, selecting working parameters
• CPC Class Codes: G07F 17/3234 about the performance of a gaming system, e.g. revenue, diagnosis of the gaming system
• CPC Class Codes: G07F 17/3237 about the players, e.g. profiling, responsible gaming, strategy/behavior of players, location of players
• CPC Class Codes: G07F 17/3239 Tracking of individual players

Abstract

A remote system and method is associated with a gaming device which implements a player tracking system. The remote system and method uses a remote device which is coupled to a remote network interface. The remote network interface retrieves data from a host computer related to the remote device.

Claims

1. A remote system for use with a gaming system, the gaming system for implementing a player tracking system, comprising:

a remote device; and

,

a remote network interface coupled to the remote device for retrieving data from a host computer and delivering the data to the remote device, the data being associated with the remote device.

2. A remote system, as set forth in claim 1, wherein the remote device is coupled to the remote network interface by a wireless connection.

3. A remote system, as set forth in claim 2, wherein the wireless connection uses an IEEE 802.11 standard.

4. A remote system, as set forth in claim 3, wherein the wireless connection is IEEE 802.11b.

5. A remote system, as set forth in claim 3, wherein the wireless connection is IEEE 802.11g.

6. A remote system, as set forth in claim 1, the remote device having a processor and a web client for interaction with a user.

7. A remote system, as set forth in claim 1, the host computer including a database for maintaining the player tracking system, the remote network interface coupled to the database for retrieving and storing data therein.

8. A remote system, as set forth in claim 7, the database for storing data in database tables.

9. A remote system, as set forth in claim 8, further comprising a plurality of first data object coupled to the database tables for retrieving and storing data in the database tables.

10. A remote system, as set forth in claim 9, further comprising at least one second data object coupled to the first data objects for assembling multiple first data objects into a third data object.

11. A remote system, as set forth in claim 10, the third data object coupled to the remote network interface for receiving queries from the remote network interface, retrieves responsive data from the database, formatting the responsive data and returning the responsive data to the remote network interface.

12. A remote system, as set forth in claim 11, the remote network interface for receiving the responsive data and transmitting the responsive data to the remote device.

13. A remote system, as set forth in claim 12, the remote device having a processor and a web client for interaction with a user, the remote network interface for formatting the data into a hyper text mark-up language response for display by the web client.

14. A remote system, as set forth in claim 13, the web client including a plurality of servlets for providing functionality to a user.

15. A remote system, as set forth in claim 14, the web client including a login layer for identifying the user.

16. A remote system, as set forth in claim 15, the web client including a menu layer for allowing the user to navigate to and access the servlets.

17. A remote system, as set forth in claim 16, the user having an assigned type, the menu layer for allowing accessing to servlets and restricting access to servlets as a function of the assigned type.

18. A remote system, as set forth in claim 14, the data including information associated with a current client.

19. A remote system, as set forth in claim 14, the information including at least one of the TCP/IP address, a HTTP context, and ID, and a name associated with the current client.

20. A remote system, as set forth in claim 1, the data including information related to a current user of the remote device.

21. A remote system, as set forth in claim 20, the information including at least one of a user ID as a user name.

22. A method for use with a gaming system, the method including the steps of:

retrieving information associated with a remote device from a host computer; and

delivering the data to the remote device.

23. A method, as set forth in claim 22, the gaming system including a host computer and a remote network interface for coupling the remote device to the host computer, including the step of providing a wireless connection between the remote device and the remote network interface.

24. A method, as set forth in claim 23, wherein the wireless connection uses an IEEE 802.11 standard.

25. A method, as set forth in claim 24, wherein the wireless connection is IEEE 802.11b.

26. A method, as set forth in claim 24, wherein the wireless connection is IEEE 802.11g.

27. A method, as set forth in claim 22, the remote device having a processor and a web client for interaction with a user, the method including the steps of:

acquiring input via the web client from the user; and

,

formatting and presenting data to the user.

28. A method, as set forth in claim 22, data related to the player tracking system being stored in a database stored on a host computer, the method including the step of providing a remote network interface coupled to the database for retrieving and storing data therein.

29. A method, as set forth in claim 28, the method including the step of the storing data in the database in database tables.

30. A method, as set forth in claim 29, the method including the step of providing a plurality of first data object coupled to the database tables for retrieving and storing data in the database tables.

31. A method, as set forth in claim 30, the method including the step of providing at least one second data object coupled to the first data objects for assembling multiple first data objects into a third data object.

32. A method, as set forth in claim 31, the third object being coupled to the remote network interface, the method including the steps of receiving, by the third object, queries from the remote network interface, retrieving responsive data from the database, formatting the responsive data and returning the responsive data to the remote network interface.

33. A method, as set forth in claim 28, the method including the step of receiving, by the remote network interface, the responsive data and transmitting the responsive data to the remote device.

34. A method, as set forth in claim 33, the remote device having a processor and a web client for interaction with a user, the method including the steps of formatting, by the remote network interface, the responsive data into a hyper text mark-up language response for display by the web client.

35. A method, as set forth in claim 27, the web client including a plurality of servlets for providing functionality to a user.

36. A method, as set forth in claim 35, the web client including a login layer for identifying the user.

37. A method, as set forth in claim 36, the web client including a menu layer for allowing the user to navigate to and access the servlets.

38. A method, as set forth in claim 37, the user having an assigned type, the menu layer for allowing accessing to servlets and restricting access to servlets as a function of the assigned type.

39. A method, as set forth in claim 35, the data including information associated with a current client.

40. A method, as set forth in claim 35, the information including at least one of the TCP/IP address, a HTTP context, and ID, and a name associated with the current client.

41. A method, as set forth in claim 40, the data including information related to a current user of the remote device.

42. A method, as set forth in claim 41, the information including at least one of a user ID and a user name.