Apple launching program to store content closer to consumers
Apple Edge Cache is a new service that enables better content delivery to end users with Apple-managed servers inside an internet provider's network.
Apple Edge Cache lets partnered ISPs deliver content directly to users.
Apple wants to utilize existing ISP networks and servers to house data closer to its customers. This means either content can be pre-cached on a server inside an ISP's network, or as content is viewed or downloaded by a customer, this data can be kept in a server local to the user for reuse throughout the provider's service area. This is a practice called edge caching.
As an example, you and your neighbor both stream the same movie in a relatively short period of time. Normally, you'll both ping the closest Apple server and have it delivered over the Akamai content distribution network, or other content delivery services that Apple has used to you.
When this occurs, the data will pass through an ISP server before reaching the user. With edge caching, the ISP can keep the data for that streamed content in the local ISP server and deliver it to you, or anyone attached to the same ISP server, again and again without pinging the originating Apple server again.
This Edge Cache allows for faster and more reliable content delivery. Less internet infrastructure to pass through before delivery reduces the potential for problems, minimizes re-routing, and cuts back on latency for the user, benefiting the user and the ISP. Other companies like Netflix and Amazon already a similar system for content delivery.
The Apple Edge Cache system is by invitation only, and applications can be sent in via the website portal for the service for consideration. Minimum requirement for applications include a minimum of 25Gbps of Apple traffic during peak usage. The network must also operate exist to primarily serve end users rather than some network operator.
Apple Edge Cache lets partnered ISPs deliver content directly to users.
Apple wants to utilize existing ISP networks and servers to house data closer to its customers. This means either content can be pre-cached on a server inside an ISP's network, or as content is viewed or downloaded by a customer, this data can be kept in a server local to the user for reuse throughout the provider's service area. This is a practice called edge caching.
As an example, you and your neighbor both stream the same movie in a relatively short period of time. Normally, you'll both ping the closest Apple server and have it delivered over the Akamai content distribution network, or other content delivery services that Apple has used to you.
When this occurs, the data will pass through an ISP server before reaching the user. With edge caching, the ISP can keep the data for that streamed content in the local ISP server and deliver it to you, or anyone attached to the same ISP server, again and again without pinging the originating Apple server again.
This Edge Cache allows for faster and more reliable content delivery. Less internet infrastructure to pass through before delivery reduces the potential for problems, minimizes re-routing, and cuts back on latency for the user, benefiting the user and the ISP. Other companies like Netflix and Amazon already a similar system for content delivery.
The Apple Edge Cache system is by invitation only, and applications can be sent in via the website portal for the service for consideration. Minimum requirement for applications include a minimum of 25Gbps of Apple traffic during peak usage. The network must also operate exist to primarily serve end users rather than some network operator.
Comments
Doesn’t Netflix pay ISP’s for this ability? Does Apple?
The only ‘loser’ here is Akamai.
Apple supplies the Edge Cache hardware, so it likely implements the same level of security as their own servers. All data would be encrypted and only accessible via authenticated means. And it would likely only cache non-personal data, such as movies and music, not personal iCloud files.
nothing worse than having to restore an iphone in an apple store. it is so slow due to the over taxed bandwidth. worse than even doing it over cellular.
at least in the australian stores.
From the description this is not personal data like email or photos, etc being cached (of course) but instead streaming content. If law enforcement would want to know what movies you watched on Apple TV or + (why and why would you care?) Apple will have those records. If you accept the app defaults it will be fairly detailed records.
https://support.apple.com/en-us/HT208511.
It would be proper to assume Apple would have to share some data about you with the ISP, presumably anonymized, in order to deliver the service but not clear whether/what they do. That little bit of "sharing" if needed wouldn't concern me anyway.
The customers own and purchased content ideally should be stored in a closer space i.e. ones home! That way the multiple devices within it can access the content locally than having to reach across the internet to gain access to it.
Ideally, one can set a rule to replicate the content either way so a seamless image of ones stuff is present locally and within an iCloud server.
Hopefully the pendulum swings back to home servers again!
We are not talking about individual data like contacts, photos, iMessages and the like. You know, the stuff law enforcement is interested in.
Apple already hands over the information on what you watched (the first set) with an applicable warrant.
That doesn’t sound normal, I’ve never seen buffering like that on Apple TV content, whether it’s TV+ or iTunes rentals.
You know the more data law enforcement is forced to wade through, especially law enforcement that is unsophisticated technically, which is probably most law enforcement in the U.S except perhaps for the CIA, the less likely they're going to find anything. I don't think law enforcement wants to know what TV shows or movies one watches. What they do want to know are the websites, chat rooms and forums you've visited, your phone calls, email and your text messages. As I understand this, this won't provide that. This is caching of often viewed content.