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 15, 2010, 2:22:35 PM (13 years ago)
- Author:
-
hmussman
- Comment:
-
—
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v23
|
v24
|
|
6 | 6 | [[Image(WiMAX/00:fig 1 121010_ WiMAXSystemOverview.jpg, 100%)]] |
7 | 7 | |
8 | | == 1.1 Entities == |
9 | | |
10 | | == 1.2 Interfaces == |
| 8 | == 1.1 Entities and Interfaces == |
11 | 9 | |
12 | 10 | 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. |
… |
… |
|
16 | 14 | 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. |
17 | 15 | |
18 | | == 1.3 APIs == |
| 16 | == 1.2 APIs == |
19 | 17 | |
20 | 18 | 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. |