Changes between Version 4 and Version 5 of Internal/WiMAX/WiMAXAPI

Timestamp:

Feb 17, 2010, 4:50:24 AM (14 years ago)

Author:

seskar

Comment:

—

Internal/WiMAX/WiMAXAPI

@@ -23 +23 @@
 A sample usage of the API for experiment setup is as shown in the Figure below.
 
+[[Image(BasicSetup.jpg,600)]]
+
 As shown in the figure, the  most basic tasks involve two operations:
  1. Requesting the slice manager to create and start the slice – [wiki:Internal/WiMAX/WiMAXAPI/SliceMgmt#createSLICE createSlice()]
@@ -34 +36 @@
 example of how system components will interact in the Figure below.
 
+[[Image(CustomFlow.jpg,600)]]
+
 The process starts when the user requests the radio manager grid service for creation of 
 a custom service class. As a part of this request we are assuming that the user intends to create the new service class using existing pre-defined service flows.  The installation supports 5 pre-defined service flows which represent a typical setting with every traffic type. The user could also define a custom service flow and include it as a part of its customized service class.  If the service class request by the user is valid, and all flows requested as a part of the service class request are valid, the system assigns the service class a  service class id (SCID). The RM service will create an internal record of the service class parameters when it assigns the service class id (SCID). The slice user can actually start using the service class only after invoking the installServiceClass(MAC, SCID) API. This results in the addition of all service flows for the client by the modified BS controller, and appropriate datapath mapping by the datapath controller. In the illustration we see the addition of two service flows when the SCID is being installed for the MAC.