Latency management in an event driven gaming network
One exemplary aspect relates to normalizing latency in a networking environment to reduce the chances of creating an unfair advantage. While an exemplary aspect will be discussed in relation to a gaming environment, it is to be appreciated that the techniques disclosed herein can be applied to other environments where latency normalization or the ability to maintain latency between various endpoints is desired. For example, other environments include eSporting, on-line betting, fantasy esports, streaming services, etc. Some more specific examples include World of Warcraft®, Overwatch®, H1Z1®, PUBG®, Fortnite®, Realm Royale®, Planet Side 2®, real-time strategy games, slot machines, electronic poker tournaments, etc.
1. A computer-implemented method of normalizing latency among endpoint computing devices, the method comprising:
providing, via at least one processor and over a network, in-game event information representing at least one in-game event to a plurality of remote endpoint devices;
measuring, via the at least one processor and over the network, based on the in-game event information a range of location-based latencies associated with the plurality of remote endpoint devices and relative to the at least one in-game event;
normalizing, via the at least one processor, time-delayed data streams associated with the in-game event and associated with the plurality of remote endpoint devices based on the range of the location-based latencies;
allowing, via the at least one processor and over the network, the plurality of remote endpoint devices to interact with the at least one in-game event in a time-synchronized manner via delivery of game event data over the network using the time-delayed data streams; and
logging, via the at least one processor, at least one interaction from the remote endpoint devices with the at least one in-game event into a ledger, wherein the ledger comprises at least one of the following types of ledgers: a blockchain, a notarized ledger, a distributed ledger, a centralized ledger, or a peer-to-peer ledger.
2. The method of claim 1 , wherein the range of the location-based latencies are measured based on clock data from local real-time clocks in the plurality of remote endpoint devices.
3. The method of claim 2 , where the clock data comprise data from at least one GPS unit.
4. The method of claim 1 , wherein the plurality of remote endpoint devices comprises at least one smart phone.
5. The method of claim 1 , wherein the at least one in-game event comprises odds related to the in-game event.
6. The method of claim 5 , wherein the odds comprise relative odds.
7. The method of claim 5 , further comprising adjusting, by the at least one processor, calculation of the odds based on a latency difference in the range of location-based latencies.
8. The method of claim 1 , further comprising grouping, via the at least one processor, the time-delayed data streams based on at least one latency range in the range of the location-based latencies.
9. The method of claim 1 , wherein normalizing the time-delayed data streams includes using a highest latency in the range of the location-based latencies as a baseline.
10. The method of claim 1 , further comprising caching, via the at least one processor, at least one stream of the time-delayed data streams for a determined delay amount.
11. The method of claim 1 , further comprising delaying, via the at least one processor, the at least one in-game event based on the range of the location-based latencies.
12. The method of claim 1 , further comprising memorializing, via the at least one processor, synchronous delivery of the game event data to the plurality of remote endpoint devices.
13. The method of claim 1 , further comprising determining, via the at least one processor, if the range of the location-based latencies comprises an unacceptable latency to at least one endpoint device of the plurality of remote endpoint devices.
14. The method of claim 13 , further comprising enabling, via the at least one processor, a different tier of service for the at least one endpoint device of the plurality of remote endpoint devices.
15. The method of claim 13 , further comprising enabling, via the at least one processor and over the network, a device in the plurality of remote endpoint devices to be a hotspot for the at least on endpoint device.
16. The method of claim 13 , further comprising providing, via the at least one processor, an alternative channel to the at least one endpoint device of the plurality of remote endpoint devices.
17. The method of claim 1 , further comprising adjusting, via the at least one processor, latency constraints of the time-delayed data streams as the at least one in-game event evolves.
18. The method of claim 17 , wherein adjusting the latency constraints includes at least one of the following adjustments: tightening a latency constraint, relaxing a latency constraint, or adjusting a latency rule.
19. An apparatus, comprising:
at least one processor; and
a memory storing instructions thereon, wherein the instructions, when executed by the at least one processor, cause the at least one processor to:
provide, over a network, in-game event information representing at least one in-game event to a plurality of remote endpoint devices;
measure, over the network, based on the in-game event information a range of location-based latencies associated with the plurality of remote endpoint devices and relative to the at least one in-game event;
normalize time-delayed data streams associated with the in-game event and associated with the plurality of remote endpoint devices based on the range of the location-based latencies;
allow, over the network, the plurality of remote endpoint devices to interact with the at least one in-game event in a time-synchronized manner via delivery of game event data over the network using the time-delayed data streams; and
log, via the at least one processor, at least one interaction from the remote endpoint devices with the at least one in-game event into a ledger, wherein the ledger comprises at least one of the following types of ledgers: a blockchain, a notarized ledger, a distributed ledger, a centralized ledger, or a peer-to-peer ledger.
20. A computer-readable information storage media having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to:
provide, over a network, in-game event information representing at least one in-game event to a plurality of remote endpoint devices;
measure, over the network, based on the in-game event information a range of location-based latencies associated with the plurality of remote endpoint devices and relative to the at least one in-game event;
normalize time-delayed data streams associated with the in-game event and associated with the plurality of remote endpoint devices based on the range of the location-based latencies;
allow, over the network, the plurality of remote endpoint devices to interact with the at least one in-game event in a time-synchronized manner via delivery of game event data over the network using the time-delayed data streams; and
log, via the at least one processor, at least one interaction from the remote endpoint devices with the at least one in-game event into a ledger, wherein the ledger comprises at least one of the following types of ledgers: a blockchain, a notarized ledger, a distributed ledger, a centralized ledger, or a peer-to-peer ledger.