Specifications

2-8
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 2 Network Design
Service Workflow
Figure 2-3 Delivery Service Workflow Diagram
1.
The topology is propagated to all the devices registered and activated in the Internet Streaming
CDSM. The delivery service configuration is propagated to all the Service Engines subscribed to the
delivery service. The Manifest file information is sent to the Content Acquirer for the delivery
service.
2. The Content Acquirer parses the Manifest file and generates the metadata. All content listed in the
Manifest file, except for non-cache content types, is fetched.
3. The Content Acquirer propagates the metadata to all other Service Engines.
4. The Service Engines receive the metadata and associated prefetched content. The Service Engines
do not prefetch content that is “wmt-live” or “cache” types. The “wmt-live” type corresponds to the
Windows Media live streaming and the “cache” type corresponds to the hybrid ingest content.
5. The client request for a URL first performs a DNS resolution. The Service Router is configured as
the authoritative DNS server for the hosted, or service routing, domain. The URLs that are published
to the users have the service routing domain names as the prefix.
6. The Service Router resolves the service routing domain name to its own IP address.
7. The client sends the request to the Service Router and the Service Router uses its routing method to
determine the best Service Engine to stream the requested content.
8. The Service Router redirects the client to the best Service Engine.
9. The client sends the request to the Service Engine.
The following are the possible scenarios after the request reaches the Service Engine:
• Prefetched/Pinned Content
Flow 10, “Pre-ingested response.”
The content is prefetched using the URL: http://www.ivs-internal.com/video/wmv-152
The actual user request is: http://cr-video.videonet.com/video/wmv-152