close
Warning:
Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Dec 9, 2010, 7:18:21 PM (13 years ago)
- Author:
-
hmussman
- Comment:
-
—
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v5
|
v6
|
|
1 | 1 | [[TOC(Internal/WiMAX/WiMAXAPI*, depth=2)]] |
2 | 2 | |
3 | | = A1.1 API Classification and Usage = |
| 3 | = A. APIs = |
| 4 | |
| 5 | == A.1 API Classification and Usage == |
4 | 6 | |
5 | 7 | |
… |
… |
|
23 | 25 | * setters – responsible for setting the specified control information. |
24 | 26 | |
25 | | == Sample Experiment Setup Using API == |
| 27 | === A.1.1 Sample Experiment Setup Using API === |
26 | 28 | |
27 | 29 | A sample usage of the API for experiment setup is as shown in the Figure below. |
… |
… |
|
36 | 38 | The addclient() API has an optional service class parameter that the user can specify. If the user does not specify the service class id, a default service class is allocated that has a single best effort type of service flow. After this sequence is complete, the user can direct traffic to the local virtual interface in the VM with the appropriate MAC address, and traffic will be automatically sent to the correct wireless client. |
37 | 39 | |
38 | | == Sample Experiment: Custom Service Class Control == |
| 40 | === A.1.2 Sample Experiment: Custom Service Class Control === |
39 | 41 | To demonstrate how the user could possibly create custom service classes we show an |
40 | 42 | example of how system components will interact in the Figure below. |