US2020376373A1PendingUtilityA1

Multi-process communication regarding gaming information

Assignee: INTERACTIVE GAMES LLCPriority: Aug 13, 2010Filed: Jun 12, 2020Published: Dec 3, 2020
Est. expiryAug 13, 2030(~4 yrs left)· nominal 20-yr term from priority
G07F 17/3237G07F 17/3218A63F 13/35
52
PatentIndex Score
0
Cited by
0
References
0
Claims

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

exact text as granted — not AI-modified
1 . (canceled) 
     
     
         2 . A method comprising:
 storing, by at least one processor, in a memory of a gaming service, a plurality of hashes generated from operating system files of operating systems approved for use with the gaming service;
 receiving, by at least one processor, 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 the at least one processor, the received hash to the plurality of hashes stored in memory; 
 determining, by the at least one processor, 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, by the at least one processor, the mobile device to access a gaming service. 
   
     
     
         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 less than an entirety of the operating system file of the mobile device. 
     
     
         4 . The method of  claim 3 , 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. 
     
     
         5 . The method of  claim 2 , wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file. 
     
     
         6 . The method of  claim 2 , wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file. 
     
     
         7 . The method of  claim 2 , wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device. 
     
     
         8 . The method of  claim 2 , wherein the portion of the operating system file is at least one of a beginning of the operating system file and the end of the operating system file. 
     
     
         9 . The method of  claim 2 , wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file. 
     
     
         10 . 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. 
     
     
         11 . 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. 
     
     
         12 . An apparatus comprising:
 at least one processor and a 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;   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.   
     
     
         13 . The apparatus of  claim 12 , 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. 
     
     
         14 . The apparatus of  claim 12 , 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. 
     
     
         15 . The apparatus of  claim 14 , wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file. 
     
     
         16 . The apparatus of  claim 14 , wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file. 
     
     
         17 . The apparatus of  claim 14 , wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device. 
     
     
         18 . The apparatus of  claim 12 , 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. 
     
     
         19 . The apparatus of  claim 12 , wherein the beginning of the operating system file of the mobile device is the first 128 bytes of the operating system file. 
     
     
         20 . The apparatus of  claim 12 , wherein the end of the operating system file of the mobile device is the last 128 bytes of the operating system file. 
     
     
         21 . The apparatus of  claim 12 , wherein the received hash is generated from both the beginning and the end of the operating system file of the mobile device.

Join the waitlist — get patent alerts

Track US2020376373A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.