Content Delivery Architecture
Qwilt content delivery solutions extend open caching infrastructure deep within the service provider network.
Qwilt Content Delivery Architecture
Qwilt content delivery solutions leverage the following functional components:
QC – Qwilt Cloud Service Controller
A control function used by the delegating Content Publisher that enables them to identify Qwilt Edge Cloud resources available within a service provider network. QC provides a set of APIs to the Publishers while representing the entire service provider distribution network realm, tracking all of the Qwilt Node locations, status, capabilities and subscriber mapping.
QN – Qwilt Node
Universal caching software that includes open caching node functionality deployed and owned by the service provider in close proximity to the users. A typical Tier 1 service provider realm may employ multiple QNs (100s-1000s). The primary goal of QN is to deliver content to users within the service provider realm while relaying logging and billing information to the Content Publisher that delegated traffic to it.

Open APIs
The Qwilt Cloud API exposes the service provider footprint (as specified by the service provider) to a Content Publisher. The Publisher chooses whether or not to delegate content delivery to the service provider network based on the client’s location. Once delegated, the Qwilt Edge Cloud routes the client to the optimal Open Caching Node.

Qwilt content delivery solutions improve QoE by getting content closer to the user

Thousands of edge nodes placed deep in operator networks

Growing global footprint with significant delivery capacity

120+ worldwide Service Provider deployments support Qwilt content delivery solutions
Qwilt content delivery solutions are available in those ISP networks that have deployed and cloud-enabled Qwilt's Open Edge Cloud solution.
Qwilt Content Delivery – How It Works
The Content Publisher decides to delegate to the QC. The QC periodically polls the health of the QN, as well as measuring real-time performance to optimize routing decisions. Routing is performed by localizing the client based on an intimate knowledge of the service provider Open Caching Node deployments - matching the delegation method with the client type and location (e.g. in case of HTTP(S) Redirect using the request’s source IP address, and issuing an HTTP(S) 302 redirect to the nearest QN cache).
Learn More
Check out our videos, case studies and other valuable information in our resource library.
Case Studies and Resources