MULTI-PROCESS COMMUNICATION REGARDING GAMING INFORMATION

• US 20150238857A1
• Filed: 03/06/2015
• Published: 08/27/2015
• Est. Priority Date: 08/13/2010
• Status: Abandoned Application

• Current Assignee: Interactive Games LLC (Cantor Fitzgerald, L.P.)
• Original Assignee: CFPH LLC (Cantor Fitzgerald, L.P.)
• Inventors: Amaitis, Lee, Williams, Paul, TARA, Sunny, Morrissette, Matthew
• Application Number:
  US14/640,439
• Publication Number:
  US 20150238857A1
• Time in Patent Office: Days
• CPC Class Codes: A63F 13/35 Details of game servers
• CPC Class Codes: G07F 17/3218 wherein at least part of the system is portable
• CPC Class Codes: G07F 17/3237 about the players, e.g. profiling, responsible gaming, strategy/behavior of players, location of players

Abstract

Various embodiments that may generally relate to mobile gaming, location determination, mobile devices, authentication, and so on are described. Various methods are described. Various apparatus are described. Further embodiments are described.

Claims

1. A method comprising:

storing in memory of a gaming service a plurality of hashes generated from operating system files of operating systems approved for use with the gaming service, each hash generated from a portion of an operating system file and a length of the operating system file;

receiving, by a processor of the gaming service, from a mobile device a hash generated from a portion of an operating system file of an operating system currently in use by the mobile device and a length of the operating system file;

comparing, by a processor of the gaming service, the received hash to the plurality of hashes stored in memory;

determining, by a processor of the gaming service, that the received hash is equal to at least one of the hashes stored in memory based on the comparison; and

based on at least in part on the determination, approving the mobile device to access the gaming service.

2. The method of claim 1, wherein the portion of the operating system file of the mobile device from which the received hash is generated is less than an entirety of the operating system file of the mobile device.

3. The method of claim 2, wherein the portion of the operating system file of the mobile device from which the received hash is generated is at least one of a beginning of the operating system file of the mobile device and an end of the operating system file of the mobile device.

4. The method of claim 3, wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file.

5. The method of claim 3, wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file.

6. The method of claim 3, wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device.

7. An apparatus comprising:

at least one processor and memory including instructions that, when executed by the processor configure the at least one processor to;

store in the memory a plurality of hashes generated from operating system files of operating systems approved for use with a gaming service, each hash generated from a portion of an operating system file and a length of the operating system file;

receive from a mobile device a hash generated from a portion of an operating system file of an operating system currently in use by the mobile device and a length of the operating system file;

compare the received hash to the plurality of hashes stored in memory;

determine that the received hash is equal to at least one of the hashes stored in memory based on the comparison; and

based at least in part on the determination, approve the mobile device to access the gaming service.

8. The apparatus of claim 7, wherein the portion of the operating system file of the mobile device from which the received hash is generated is less than an entirety of the operating system file of the mobile device.

9. The method of claim 8, wherein the portion of the operating system file of the mobile device from which the received hash is generated is at least one of a beginning of the operating system file of the mobile device and an end of the operating system file of the mobile device.

10. The method of claim 9, wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file.

11. The method of claim 9, wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file.

12. The method of claim 9, wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device.

13. A non-transitory computer readable medium storing instructions that, when executed by at least one processor configure the at least one processor to:

store in the memory a plurality of hashes generated from operating system files of operating systems approved for use with a gaming service, each hash generated from a portion of an operating system file and a length of the operating system file;

receive from a mobile device a hash generated from a portion of an operating system file of an operating system currently in use by the mobile device and a length of the operating system file;

compare the received hash to the plurality of hashes stored in memory;

determine that the received hash is equal to at least one of the hashes stored in memory based on the comparison; and

based at least in part on the determination, approve the mobile device to access the gaming service.

14. The non-transitory computer readable medium of claim 13, wherein the portion of the operating system file of the mobile device from which the received hash is generated is less than an entirety of the operating system file of the mobile device.

15. The non-transitory computer readable medium of claim 14, wherein the portion of the operating system file of the mobile device from which the received hash is generated is at least one of a beginning of the operating system file of the mobile device and an end of the operating system file of the mobile device.

16. The non-transitory computer readable medium of claim 13, wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file.

17. The non-transitory computer readable medium of claim 13, wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file.

18. The non-transitory computer readable medium of claim 13, wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device.