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.

Changes between Version 7 and Version 8 of Old/WiMAX/00


Ignore:
Timestamp:
Nov 30, 2010, 2:53:45 PM (10 years ago)
Author:
hmussman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/WiMAX/00

    v7 v8  
    1 = System Architecture =
     1= System Configuration =
    22
    33== Entities ==
     
    99The 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.
    1010
    11 == Grid Services ==
     11== APIs ==
    1212
    1313[[Image(SysArch.jpg, 500)]]
    1414
    15 The virtualized WiMAX Basestation Transceiver (BTS) system consists of different sets of APIs shared by components of the system. A brief overview of the interaction between different system components is as shown in the Figure 1. The [wiki:Internal/WiMAX/AggMgr/ogs_wimaxvm slice manager (SM)] service allows the user to perform basic setup functions such as slice creation, instantiation, and destruction. The Radio management (RM) grid service allows the user to invoke all the WiMAX radio functionalities when operating as part of a slice. The SM and RM services in turn talk to other system components such as the datapath controller and NEC BS controller to execute API invoked by the Slice owners.  The Datapath controller module is responsible for laying out the L2 datapath from the slice virtual machines to the physical WiMAX BTS. The [wiki:Internal/WiMAX/NecBSContr NEC BTS controller] allows for the getting and setting of various WiMAX radio features.
     15The virtualized WiMAX Basestation Transceiver (BTS) system consists of different sets of APIs shared by components of the system. A brief overview of the interaction between different system components is as shown in the Figure 1.
    1616
     17The [wiki:Internal/WiMAX/AggMgr/ogs_wimaxvm slice manager (SM)] service allows the user to perform basic setup functions such as slice creation, instantiation, and destruction.
     18
     19The Radio management (RM) grid service allows the user to invoke all the WiMAX radio functionalities when operating as part of a slice. The SM and RM services in turn talk to other system components such as the datapath controller and NEC BS controller to execute API invoked by the Slice owners. 
     20
     21The Datapath controller module is responsible for laying out the L2 datapath from the slice virtual machines to the physical WiMAX BTS.
     22
     23The [wiki:Internal/WiMAX/NecBSContr NEC BTS controller] allows for the getting and setting of various WiMAX radio features.
     24