Configure MPer for DASH

You need to have MPer set up in your AMD property and also set up your player to include a query string value in requests.

Add MPer for DASH to your property

You need to work with your account representative ("rep") to add MPer to your AMD property. Your account rep will add an "Advanced Override." This adds customized metadata and inserts it in the XML that makes up your AMD property's configuration file. Consider these points when setting up MPer:

  • You need to determine the maximum bit rate (bandwidth) value for your content. When a request meets the match criteria for MPer, the "Representation" elements are rewritten in the manifest. One is set to support your maximum bit rate (via its "bandwidth" parameter) and others are included for lower bit rate "buckets." (More on buckets in the next section.) Representation elements that included bit rates above the maximum are dropped from the manifest. MPer supports a maximum bit rate of 10,000 Kbps.
  • The rule is set with a match criteria for requests that include DASH manifest files. Work with your account rep to ensure that the proper file names and extensions for your DASH manifests are included in your Advanced Override.

Apply a bit rate upper limit in your player

This is accomplished by appending the "b-upper-limit=<#>" query string to requests for your content. You need to update your player to ensure that this query string is included in all requests, if you want to use MPer to apply bit rate targeting.
  • Values set in the "b-upper-limit" are in Kbps. DASH manifests use bps to specify the "bandwidth" attribute used for bit rate. Akamai metadata recognizes this in the query string and makes the conversion.
  • There are threshold bit rate "buckets." Akamai has set up a range of threshold points—buckets—for ranges of "b-upper-limit" values. Your manifest is updated by MPer to include your maximum bit rate and all buckets below it. Values set in the query string that fall into a certain range are round down to the applicable bucket for bit rate targeting.
    If a request includes a "b-upper-limit" in this range... ...the manifest applies this bucket bit rate (in Kbps)
    1000 - 1999 1000
    2000 - 2999 2000
    3000 - 3999 3000
    4000 - 4999 4000
    5000 - 5999 5000
    6000 - 7999 6000
    8000 - 9999 8000
    10000 + 10000
  • You can set the value for "b-upper-limit" in a request to any value below your established maximum bit rate value. For example, if you've defined a maximum bit rate of 4,000 Kbps, you could still set the query string to "b-upper-limit=2000" for a single request. Content delivered for that request would be served at a maximum of 2,000 Kbps.
  • A "b-upper-limit" won't exceed your maximum bit rate. The maximum bit rate you communicated to your account rep when initially adding MPer is the absolute maximum. If the value in "b-upper-limit=<#>" exceeds that, MPer still serves the content, but at your maximum bit rate.