Changes between Version 10 and Version 11 of Internal/WiMAX

Timestamp:

Apr 30, 2010, 8:31:21 PM (15 years ago)

Author:

shweta

Comment:

—

Internal/WiMAX

@@ -3 +3 @@
 This is a GENI project that addresses the challenges of integration and trial deployment of a commercial Mobile WiMAX radio as part of an open virtualized experimental framework. The project leverages a commercial 802.16e base station from NEC, replacing the standard WiMAX controller with an open software implementation that supports virtualization and layer 2/3 programmability. The most prominent features provided
 by the modifed BS control framework include the capability to perform all frame switching using purely layer 2 information, and control mechanisms to provide isolation across slices, which is needed to ensure experiment repeatability.
-[[Image(GENI_WiMAX_Overview.jpg, 500)High-level diagram of integration of the WiMAX Basestation with GENI]]
+
+== Integration of the WiMAX Basestation with GENI ==
+
+[[Image(GENI_WiMAX_Overview.jpg, 500)]]
+The figure above shows a schematic representation of the WiMAX base station router and its connection to the rest of the network. As shown, the WiMAX base station is typically connected to a GENI access network with layer 2 switched connectivity using Ethernet or optical fiber technology. The figure also indicates three distinct interfaces associated with the GENI WiMAX base station. The first is the GENI control interface for experimenter access to virtual networks (slices) supported by the external base station controller. This is the primary interface relevant to a GENI experimenter, and is currently based on the ORBIT Management Framework (OMF). The second interface is the so-called R6+ interface by which the base station controller communicates with the base station hardware (which includes its own internal controller running a proprietary NEC operating system and control/management software). The R6+ interface exposes the hardware features such as assignment of MAC/PHY resources (i.e. OFDMA time-frequency slots, power levels, service classification, etc.) to each flow, as well as management interfaces for initial configuration, scheduler policy selection and queue management.
 == Hardware ==