| 18 | | A very important motivation and feature of ORBIT Traffic Generator design is its integration with the [http://svn.orbit-lab.org/projects/oml OML] (''ORBIT Measurement Library'') framework. The properties of each packet generated or received such as packet size, packet deliver time are all reported to OML by OTG and OTR. Users can calculate certain measurements like throughput, delay by either applying special OML filters or querying the OML database directly. There also exists an interface to use LIBMAC to correlate each packet with corresponding physical layer parameters. |
| 19 | | The design complies with modular principle and different modules are kept loosely coupled. The interface to the [http://svn.orbit-lab.org/projects/oml OML], the interface to the user are supposed to be dynamically generated from an ORBIT application definition file. Both of them should be independent with the core module of application. |
| | 18 | A very important motivation and feature of ORBIT Traffic Generator design is its integration with the [wiki:Documentation/OML OML (''ORBIT Measurement Library'')] framework. The properties of each packet generated or received such as packet size, packet deliver time are all reported to OML by OTG and OTR. Users can calculate certain measurements like throughput, delay by either applying special OML filters or querying the OML database directly. There also exists an interface to use LIBMAC to correlate each packet with corresponding physical layer parameters. |
| | 19 | The design complies with modular principle and different modules are kept loosely coupled. The interface to the [wiki:Documentation/OML OML], the interface to the user are supposed to be dynamically generated from an ORBIT application definition file. Both of them should be independent with the core module of application. |
