Streaming media acceleration

The streaming media acceleration option is mainly intended to provide acceleration services for online video and audio broadcasting.The high-speed, real-time properties of webcasting are very popular with users.The real-time nature of direct broadcasting means that huge numbers of users access services concurrently. This use puts an enormous strain on source station and bandwidth resources. Such services also are subject to Chinese restrictions on cross-region or cross-carrier traffic, which impose significant requirements on high-quality, high-speed streaming media direct broadcasts.The Azure Content Delivery Network streaming media acceleration service acquires the source station video stream in real time. It then delivers the video stream to the Content Delivery Network edge node closest to the user. It uses intelligent caching and scheduling strategies to calculate and provide the optimal node for the user. This process reduces the lag and bandwidth pressures caused by link transmissions. The user is charged for data usage. The service provides users with a high-speed, smooth, high-quality direct broadcast viewing experience.

Content Delivery Network streaming media acceleration is principally based on the HTTP Live Streaming (HLS) protocol and supports Azure Media Services.

Streaming media acceleration is suitable for use with all types of streaming media direct broadcast websites, such as online television broadcasts and direct broadcasts of sporting events or major public events.

This article discusses the creation of streaming media acceleration domain names. For more information about how to create Content Delivery Network Use the Azure Content Delivery Network.

Default cache rules for streaming media acceleration

The Content Delivery Network sets default cache rules (see the following) for streaming media acceleration.You also can customize cache rules based on your needs. For more information, see the Content Delivery Network portal advanced management help file “Domain Name Management.”If the source station content is changed or updated, but the cache time-to-live (TTL) hasn’t expired, you can manually refresh the cache files and synchronize the updated source station content in real time. For more information, see the Content Delivery Network Management portal advanced management help file “Cache Refresh.”

The system’s default cache rules for streaming media acceleration:

  1. TS files are cached for two minutes.
  2. M3U8 files are cached for two seconds.

Create streaming media acceleration domain names

  1. In the navigation pane of the Azure portal, select “CDN.”
  2. In the function area, select Create New.In the Create New dialog box, select App Services > CDN > Quick Create.
  3. In the Acceleration Type drop-down list, select Streaming Media Acceleration.

    Acceleration type selection

  4. In the Origin Domain Type drop-down list, select cloud service, storage account, web app, media services, or a customized origin domain.

  5. In the Origin Domain drop-down list, select one option from the list of available media services for use in creating the Content Delivery Network endpoint.

    Origin domain selection

    If the selected origin domain type is Customized Origin Domain, enter your own origin domain address under Origin Domain.You can enter an origin domain name, such as origin.livestreaming.com. You also can enter one or multiple origin domain IP addresses. Separate multiple addresses with semicolons, for example, 126.1.1.1;172.1.1.1.

    Customized origin domain selection

  6. In Custom Domain, enter the custom domain name you want to use, for example, cdn.livestreaming.com.Custom domains support extensive domain name acceleration.

  7. In Origin Host Header, enter the return-to-source access host header accepted by your source station.After you enter the custom domain, the system automatically fills in a default value based on the origin domain type that you selected.To be more specific: If your source station is on Azure, the default value is the corresponding source station address.If your source station isn’t on Azure, the default value is the custom domain that you entered. You also can also modify this based on the actual configuration of your source station.

    If the origin domain type is media services, the corresponding return-to-source host header is:

    Media services

    If the origin domain type is a custom origin domain, the corresponding return-to-source host header is:

    Custom origin domain

  8. In ICP Number, enter the corresponding ICP record number for the custom domain that you entered (for example, Jing ICP Bei XXXXXXXX Hao-X).

    ICP record number

  9. Select Create to create the new endpoint.

After you have created the endpoint, it appears in the list of subscribed endpoints.The list view shows the custom domains that are used to access cached content, as well as the origin domains. The origin domain is the original location of the content that is cached on the CDN.Custom domains are URLs that are used to access Content Delivery Network cache content.

Custom domains and origin domains

Note: Configurations created for endpoints aren’t immediately available. They must be reviewed to check that the ICP custom domain name matches the ICP number. For more information, see the second half of “Step 2: Create a new Content Delivery Network endpoint” in Use the Azure Content Delivery Network.