After we run a simulation in omnet, omnet will automatically generate a vector file .vec and a scalar file .sca. Double-click any of the files to generate a result analysis file.anf.
Open the .anf file, select its Browse Date tag, and find the .sink item of the receiver you set. For example, if the name of the receiver you set is server, then find server.app[*].sink. Open the corresponding app, and you can see some indicators of the data packets received in the app counted by the emulator. (Digression: app[0], app[1]...respectively represent different ports of the server. If an app[*] value is set for a certain flow, then all the result information of this flow will be counted in this app[ *], so that the result information of all flows will not be piled in one port. I think the purpose of different apps is to facilitate the organization of results).
This article focuses on the meaning of meanBitLife TimePerPacket and PacketJitter. I think PacketDelayVariation and PacketDelayDifferenceToMean can be ignored. Of course, if they are used, you can check them out.
meanBitLifeTimePerPacket: end-to-end delay
PacketJitter: The difference between the delays of consecutive packets.
for example:
| stream name | end-to-end latency (meanBitLife TimePerPacket) |
Jitter (PacketJitter) |
|---|---|---|
| f1 | 320.53 us | 320.53-0=320.53 us |
| f2 | 341.97 us | 341.97-320.53=21.44 us |
| f3 | 363.41 us | 363.41-341.97=21.44 us |
If there are any errors in the above content, I hope you will criticize and correct me! ! !