Table D.1 provides an example MPD for an On-Demand service.
Table D.2 provides an example MPD for a live service.
Table D.3 provides an example MPD with reference to external Period element as provided in
Table D.4. An equivalent MPD to the one in
Table D.3 after dereferencing with the Period element in
Table D.4 is shown in
Table D.2.
In the following MPD example, the content is 30 minutes in duration. There are 3 Periods, each of 10 minutes duration. Each Period has 3 Representations and each Representation is contained within one 3gp file. Each Representation has audio encoded with Low Complexity-AAC. One Representation of each Period (p1rep1.3gp, p2rep1.3gp, and p3rep1.3gp) has video resolution 320x240 encoded with H.264 baseline profile level 1.1. Another Representation of each Period (p1rep2.3gp, p2rep2.3gp, and p3rep2.3gp) has resolution 320x240 encoded with H.264 baseline profile level 1.3. Finally, a third representation in each period (p1rep3.3gp, p2rep3.3gp, and p3rep3.3gp) has resolution 480×240 encoded with H.264 baseline profile level 2.1. One Representation of each Period has bandwidth of 239 kbps, a second representation has bandwidth of 478 kbps, and a third representation has bandwidth of 892 kbps.
Since each representation is contained in one file, the Initialization Segments and the Media Segments for a representation are accessed with byte ranges. Each SegmentURL element in the MPD contains a mediaRange attribute and the corresponding byte range for the Initialization Segment or Media Segment. For the example each Segment of all representations is 10 seconds in duration.
Line numbers of the MPD in the example are shown for clarity, although these would not be present in the MPD.
EXAMPLE 1 (add)
The change of adding the SegmentURL element for the next Segment to the Representation of the third Period of the MPD in the example with 239K bandwidth can be described as follows.
The SegmentURL element is added on a new line after line number 492.
EXAMPLE 2 (replace)
Replacing the line containing the DeltaSupport element to correspond to the MPD after the next update can be described as follows.
EXAMPLE 3 (delete)
If lines 8 through 10 of the original MPD are deleted and not present in the updated MPD, the delta to express this is:
Below is what the MPD looks like after approximately 29 minutes and 40 seconds. In this case, the MPD is updated approximately every 10 seconds.
Since the value of @sourceURL in the above MPD is
"delta1.mpdd", delta1.mpdd is an empty file at the time of publication of the above MPD.
The following file is delta1.mpdd after the next MPD update. Notice that clients have access to the new value of @sourceURL referenced by the latest MPD via the delta.
At the next MPD update,
"delta1.mpdd" would contain the cumulative update for 2 MPD updates.