Co-located peers for peer-to-peer matching

Abstract

The techniques and systems described herein achieve improved peer-to-peer matching by coordinating peer-to-peer matching requests across multiple peer-to-peer matching nodes configured within a peer-to-peer matching unit such that resource consumption can be spread out and resource limits are not exceeded Matching service. Also, the Peer Matching Service can determine whether the Peer Matching Unit is overloaded (e.g., has experienced an increased number of requests in a given time interval, which causes performance degradation), and the Peer Matching Service can implement a An action to expand said number of requests within a peer matching unit (eg, redistribute some peer matching requests to another peer matching unit). In various examples, the peer matching service may determine whether a peer device is a co-located peer device based on the location information, and may generate a list of co-located peer devices that is prioritized.

Description

[0001] priority application [0002] This application claims the benefit and priority of U.S. Non-Provisional Application No. 15 / 052757, filed February 24, 2016, and U.S. Provisional Application No. 62 / 121413, filed February 26, 2015, the entire contents of which are incorporated herein by reference . Background technique [0003] Digital content, such as operating system updates or video games, is often available for download from digital content providers over network connections, thereby eliminating the need for users to install digital content on computing devices. Digital content can include large amounts of data, and thus, downloading digital content can potentially take a significant amount of time and / or can consume significant resources (eg, networking resources, processing resources, memory resources, etc.). Exacerbations associated with downloading digital content from digital content providers are exacerbated when many computing devices attempt to download the sam...

AI Technical Summary

Problems solved by technology

When this limited number is reached, the specific instance of the central service becomes overloaded and the peer matching performance achieved by the specific instance of the central service is severely degraded (e.g. requests can be rejected)

Moreover, a particular instance of the central service may even fail or go offline due to overload or some other reason, and as a result, computing devices that have contacted the particular instance of the central service may be lost (e.g., may not recognize their peer-matched availability)

Images