Professional Documents
Culture Documents
Operating manual
No part of this book or program may be reproduced in any form (print, photocopy, microfilm, or other media) or by
any electronic or mechanical means, including information storage and retrieval systems without our explicit written
consent. All brand names and trademarks used in this book are protected by third party rights and shall be subject in
an unrestricted fashion to the provisions and labeling law and the rights of ownership of the respectively registered
owners.
Stand: 08/2007
Software-Version: 1.7.3.8
Table of contents
1 Instruction ...................................................................... 4
2 Functional range ................................................................ 5
3 Operation ........................................................................ 6
3.1 Overview ........................................................................................... 8
3.2 Transport Packets.............................................................................. 9
3.3 PCR Statistics .................................................................................. 11
3.4 Video ............................................................................................... 12
3.5 Audio ............................................................................................... 15
3.6 TR 101 290 ...................................................................................... 16
4 Performing an IPTV analysis ......................................... 18
4.1 Analyzing the transport stream with the VQ108 Analyser IPTV
software ................................................................................................... 19
4.2.1 An example of a measurement indicating good quality .......................... 21
4.1.1 An example of a measurement indicating bad quality............................ 24
1 Instruction
The VQ108 Analyser IPTV allows for the analysis of IPTV contents found in re-
corded data streams. The software considers DVB data streams sent via UDP or RTP.
A recording may contain several data streams. There are up to seven transport pack-
ets in a UDP or RTP packet. These individual packets are allocated, clearly marked,
and analyzed. Furthermore, all audio or video streams within the packets may be ex-
tracted and played. In this way the quality of transmissions can be determined in an
objective as well as in a subjective manner.
Please note:
• the recordings, which are meant to be analyzed, should not exceed a certain
length, because otherwise the analysis and display of the data might last a con-
siderable amount of time. We recommend a recording length of up to one min-
ute. However, the recording should not be shorter than twenty seconds.
• Since the software performs quite complicated and extensive operations, a fast
processor with a large memory should be used. We recommend a processor
with at least 2 GHz and a 1 GByte memory.
• The “IPTV” option is an additional feature of the VQ108 Analyser software
and must be activated before use.
• If the transport stream is transmitted via RTP, the VQ108 Analyser main
program can provide information and quality evaluations regarding the RTP
session. Use the “RTP” dialog as described in the VQ108 Analyser main
manual.
• Minimum:
o PC with 2 GHz Taktfrequenz
o 1 GByte memory
o CD-ROM
o Windows XP
o 1 GByte of disk space
o powerful network adaptor
o min monitor resolution of 1024x768
3 Operation
The analysis can be carried out after the measurement process has been finished, or
after measurement data has been loaded or imported. Due to the extensive processor
load of the functions, the analysis cannot be conducted while recording.
After the “IPTV” button has been selected from the toolbar, every individual packet of
the recording is scanned for DVB transport streams. If the software cannot find any
transport streams, a message will appear. Otherwise, the IPTV dialog window will o-
pen automatically.
[2] [3]
[1]
The “help” button opens this manual. The “ok” button closes the IPTV dialog.
In order to start an analysis, one of the transport streams listed in [2] must be se-
lected. The Multicast-IP-Address, the port number, and the allocated sender are dis-
played. The analysis is started by selecting the „search“ button [3].
At this stage, the lower part of the main dialog also comes to life.
[1]
[2]
[3]
[7]
[4]
[5] [8]
[6]
Figure 3-3: “IPTV” analysis main dialog
[1] The “current transport stream” field shows the Multicast-IP-Address, the port
number, and the allocated sender of the analyzed transport steam. Further-
more, the duration of the session is displayed.
[2] There are five tabs, which can be used to display the different analysis win-
dows. These are thoroughly described in the following chapters.
There are six windows offering an overview of general information with regards to the
analyzed transport streams. This information is depicted in tables, diagrams, and
trees.
[7] PID statistics This table list the number of continuity errors occur-
ring in the individual PIDs. Every transport packet of
a PID is numbered with four bits, i.e. from 0 up to 15.
Any deviations from this sequence indicate an error.
Furthermore, the transport packet rate is displayed in
this table.
The tables (PAT, PMT, …) are additionally saved with
the CRC method.
The number of inaccurate tables is displayed as well.
[8] Cycles There are rules for the tables (PAT, PMT, …) defining
the frequency of repetitions. In the case of PAT and
PMT these occur every 0,5s.
This table list the average interval between two ta-
bles as well as the minimum and maximum interval
between the tables.
A green marking indicates that everything is in order,
a yellow marking indicates that the maximum value
exceeds the reference value, and a red marking indi-
cates that the average value exceeds the reference
value.
The same applies to the PCRs (Programm Clock Ref-
erence), which are also shown in this table. The in-
terval between two PCRs must not exceed 40 ms.
This overview list all transport packets of all PIDs in the transport stream. When choo-
sing this option for the first time after an analysis, the processing might take a while,
depending on the length of the transport stream, because in most cases numerous
transport packets have to be edited and displayed.
[1]
[5]
[2] [6]
[4]
[3]
[1] packet table This table list the most important header information
of the transport packets.
[2] Bytes of the trans- Displays the bytes of the above marked transport pa-
port packet (hexa- cket in hexadecimal values.
decimal)
[3] Bytes of the trans- Displays the bytes of the above marked transport pa-
port packet (char- cket as characters.
acters)
[4] Packet details Displays the decoded headers of the above marked
transport packet.
[5] Sort according to The content of the table [1] is sorted according to
PIDs PIDs.
[1]
[2]
[3]
Figure 3-5: T ransport packet diagram
The PCRs (Programm Clock Reference) play an important role in the synchroni-
zation of the transport stream. For that reason, these separate statistics can
be used to check the accuracy of the PCR arrival times.
[3]
[1]
[2]
[4]
[5]
[6]
Figure 3-6: PCR statistics dialog
First of all, the desired PCR must be selected [1], because there may be several pro-
grams in a transport stream (each of which needs a separate PCR for synchronizing).
The correlations between PCRs and programs can be seen in the DVB tree (PMTs) of
the “overview”. The “analyze” [2] button starts the analyzing process of the selected
PCRs.
The statistics field [3] provides information about the number of PCRs, the PCR rate,
and the maximum as well as the average PCR jitter.
The PCR jitter is the discrepancy between the calculated and the actual arrival time of
the PCR. The diagrams [4] display the jitter in a chronological way and also show the
distribution of jitter. The red lines represent the maximum permissible value of 500
ns.
If the “show deviations” option [5] is enagaged, all lines with a jitter exceeding 500 ns
are marked red. All lines with interarrival times exceeding 40 ms are marked yellow.
3.4 Video
The “video” tab provides an overview of the video stream belonging to a TV program.
If the video stream is encoded, some information and functions may not be available.
[1]
[3]
[2]
[9]
[7]
[5]
[6]
[4]
[8]
This diagram [3] shows the chronological sequence of the single frames in a video.
Each column represents a frame. The color of a column denotes the type of frame. I-
Frames are represented by a red column, P-frames by a blue column, and B-frames
This table [4] lists every frame of the elementary stream. The most important infor-
mation regarding frames are:
• stream ID
• length /actual length
• flags
• length of header
• frame type
• frame number
• PTS (Presentation Timestamp)
• DTS (Decoding Timestamp)
• Delta TS (discrepancy between consecutive time stamps)
• arrival time / expected arrival time
• jitter
The „TS-Quality“ button [9] open a diagram, which shows the quality of the transport-
stream in intervals of 5 seconds. The evaluating is shown procentual from 0-100%
(0%-> bad quality, 100% excellent quality). The following parameters will be con-
sider:
• Frame- Jitter
• PCR- Jitter
• Packet Loss
• Continuity Error
• Packet-Jitter
• Video-Codec
The button „Play Video“ open a separat window where the video of the Transport
Stream will be played if the video stream is not encoded. With the function „Create
AVI File“ the video stream can be saved as an uncompressed AVI24 (e.g. for objective
quality analysing according by PEVQ).
The “save video” function [6] decodes and saves the selected video data, so that the
video may be watched and evaluated in a subjective manner.
The “save complete TS” function [5] enables the user to extract a selected “pure”
transport stream from the recording. This may be necessary if the transport stream is
to be analyzed or viewed with another player or analyzing tool.
The term “frame jitter” refers to the discrepancy between the expected and the actual
arrival time of a frame. If the jitter exceeds the built-in jitter buffer of a system, the
video cannot be played without errors. The “graph” function [7] opens an additional
window, which shows the chronological sequence and the distribution of frame jitter.
TV broadcasts must transmit video as well as audio data. The audio overview shows
the audio elementary streams of the programs.
[1]
[4]
[2]
[3]
This overview is similar to the video overview. At the beginning an audio ele-
mentary stream must be selected [1], because there may be several programs
and elementary streams in a program stream. Furthermore, there is informa-
tion about the PID of the elementary stream. The “analyze” button initiates the
analyzing process of the selected audio elementary stream.
The statistics field [2] provides information about the number of blocks, blocks per
second, the number of bytes, and the maximum as well as average frame jitter.
This table [3] has the same structure as the video overview. It shows the most impor-
tant information of every audio block.
The “graph” function [4] opens an additional window, which shows the chronological
sequence and the distribution of jitter.
This overview allows for an analysis of the transport stream according to the ETSI
specification TR 101 290. A detailed description of the single analysis points cannot be
provided at this stage. For further information consult the applicable specifications.
[5]
[4]
[1]
[3]
[2]
After the dialog has been opened, the analysis script is generated automatically. After
a few seconds the results appear in the fields [1]. These are divided into three priori-
ties:
A green check mark indicates that everything is in order. A red exclamation mark indi-
cates that the according point does not meet all requirements.
If one of the items is marked, all details related to this item are shown in field [2]. In
some cases there may be several subitems, which are listed separately. These items
are also allocated a green check or a red exclamation mark. If an item is erroneous,
the location of the error is in some cases specified in the next line. In such a case, the
line with the items can be marked and by selecting the “display in table” [3] button,
an according table is generated, which highlights all errors red.
The parameters can be altered within the limiting values given on the right-hand side.
The values may be saved and loaded. Furthermore, the default values can be re-
stored.
After the values have been changed and the parameter dialog has been closed by se-
lecting the “OK” button, the “start analyzing script” button [5] must be selected to
ensure that the modified parameters are taken into consideration during the analyzing
process.
I II III
II network Features all components necessary for the reception and dis-
tribution of the data streams. These components are the
video server, the routers on the transmitting and receiving
side, and the transmission network.
III user On the user side there is the Set Top Box (STB), which de-
codes and edits the received data and finally forwards this
data to the TV set.
The measurements with the VQ108 Analyser IPTV Software are recorded at the
Ethernet interface, which is parallel to the input of the set top box. The recording
should last at least 20 second and should not exceed 1 minute. Recordings exceeding
one minute create extensive data volumes, which can cause rather time-consuming
analysis processes. Recordings shorter than 20 seconds might not produce represen-
tative data.
4.1 Analyzing the transport stream with the VQ108 Analyser IPTV soft-
ware
In order to maintain synchronism between sender and receiver, there is the Pro-
gramm Clock Reference (PCR), which sends highly accurate synchronizing time
stamps at regular intervals. The periodicity of the PCR packets can be viewed in
the overview of the IPTV analysis. A PCR packet should be received at least
every 40 ms.
Furthermore, the discrepancy between the expected and the actual arrival time
of a PCR packet should be within a certain margin. The highly accurate PCR
works with a 27 MHZ oscillator, which will only tolerate a PCR jitter of up to 500
ns. This degree of accuracy can hardly be met by a best effort network. Experi-
ence shows that videos can still be played faultlessly when higher jitter rates are
If transport packets are lost, delayed or arrive in the wrong order, this will reduce
the quality of video. In some cases, entire frames might not be shown. The over-
view of the IPTV extension lists all continuity errors. The color codes of the trans-
port packet table help to trace missing transport packets or those in wrong order
exactly.
Normally, the transport packets are sent with RTP packets (7 in a single RTP pa-
cket). In this case, the RTP session can be analyzed with the VQ108 Analyser
main program. The RTP statistics lists the RTP packets and the related packet jit-
ter as well as packet loss.
IV. compression
The relation of I, P and B frames in a transmission plays a decisive role for the
quality of a video. Only I frames transmit complete frames. P and B frames only
transmit the differences in relation to the previous and/or successive frame.
If I frames are only scarcely transmitted, the quality might suffer, especially
when it comes to changes of scene. Normally, every fortieth transferred frame
should be an I frame. Furthermore, a good encoding will ensure that the size
(number of bytes) of an I frame exceeds that of an p frame, which will in turn be
of greater size than a B frame. If that is not the case, the encoder does not work
efficiently. Another important point is the effective frame rate. This rate should
not be below 25 frames/s to ensure a video playback without jerking. The “video”
dialog of the IPTV analysis shows the chronological sequence of the frames. The
I, P and B frames are color coded. The height of the columns represents the size
of the frames.
V. Frame-Jitter
At a rate of 25 frames/s, a frame must be received every 40 ms. The frames are
buffered before they are shown. This will compensate for slight delays during re-
ception of single frames. However, if this jitter exceeds a certain margin, the
frame cannot be shown in time any more. This will result in frame losses, “freez-
ing” of the frame or “jerking”. For that reason, the “video” dialog of the IPTV
analysis shows the frame jitter for every single frame graphically and in tables.
The practical tests provided us with numerous measurement results of DVB transport
streams with various quality levels. These measurements will be analyzed as de-
scribed in the previous chapter.
Bandwidth
The overview of the IPTV analysis shows that the bandwidth of
the entire transport stream is close to 3 Mbits/s. This value is
typical of SD videos (H.264 coded). An overcompression,
which would have negative effects on the quality, cannot be
detected.
The PCR statistics reveal an average PCR jitter of 5.4 ms, which is acceptable. As a
matter of fact, most values are above the required 500 ns, but, as we have already
explained, this will not have a significant effect on the quality.
Packet loss
Frame- Jitter
The average frame jitter is 17 ms, which is
acceptable. Frame losses due to excessive
jitter are not to be expected. The diagram
shows some regular peaks resulting from
the transmission of relatively big I frames.
Quality losses are unlikely.
Conclusion
The analysis with the VQ108 Analyser IPTV software confirms the good video
quality. Possible problems could not be detected.
The analysis with the VQ108 Analyser IPTV software produced the following re-
sults:
bandwidth:
The PCR statistics show a rather high average PCR jitter, which fluctuates signifi-
cantly. Furthermore, it is obvious that packets have not been received for several sec-
onds. Literally all values are above the required 500 ns.
Packet loss:
Frame- Jitter:
The frame jitter diagram shows
fluctuations. It is clearly visible that
packets have not been received for
several seconds. The inevitable results
are frame losses. The average frame
jitter of 50 ms is definitely too large.
Conclusion:
The analysis with the VQ108 Analyser IPTV software confirms the bad video
quality. Complete RTP packets were not received and there are “interruptions” (peri-
ods in which not a single packet was received for several seconds). It is obvious that
the transmission problems are caused by the IP net.