WiMax Operator's Manual
WiMax Operator's Manual
WiMax Operator's Manual
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
94 CHAPTER 4 ■ SETTING UP PHYSICAL INFRASTRUCTURE<br />
backhaul, better to have interfaces in place rather than having to set up outboard optoelectronic<br />
converters.<br />
Another technical consideration is the number of RF ports on the base station controller.<br />
If the operator wants to operate on multiple bands, that many RF ports will be required.<br />
Routing and switching requirements should also be determined before any equipment<br />
contracts are signed. It is certainly possible to use a base station controller with an outboard<br />
router or switch, but it is generally a lot cheaper to buy an integrated network element that<br />
does it all.<br />
Lastly, investigate how the component’s element management system will fit in with the<br />
overall operations support systems (OSS) software suite utilized in the network. Few startups<br />
or competitive service providers can command deep expertise in network management software,<br />
and if off-the-shelf programs can be bolted together and made to work reasonably well,<br />
that is desired. What one wants to avoid is having to hire consultants and trying to harmonize<br />
the software for a single element with an overall system with which it is fundamentally<br />
incompatible.<br />
Integrating Wireless with Wireline Infrastructure<br />
Wireless infrastructure should always be regarded as an option, not as a cause to pursue.<br />
Sometimes it is a good option, sometimes it is not, and sometimes the best choice that a network<br />
operator can make is to put wireless links in some parts of the network but not in others.<br />
But be aware that when some portion of the network is wireless and some part wireline, integration<br />
problems may occur.<br />
One fact cannot be emphasized enough in this regard, namely, that all the commonly used<br />
networking protocols, including SONET/SDH, Ethernet, IP, MPLS, RPR, frame relay, and ATM,<br />
were devised for use over wireline networks—networks where high availability was a given.<br />
In fact, most of the more recent protocols were explicitly designed for use over optical fiber<br />
where packet loss may be presumed to be negligible. None of these protocols work well over<br />
wireless airlinks in native form, and wireless standards such as 802.11 and 802.16 all incorporate<br />
invisible layers of middleware that adapt the wireline protocol to the exigencies of the RF<br />
environment.<br />
When a network operator attempts to use a standards-based airlink to carry a protocol for<br />
which no appropriate middleware is present, performance is apt to be degraded, or the link<br />
may even fail altogether. An example would be attempting to carry SONET or ATM traffic over<br />
an 802.11 link. Both standards happen to lack mechanisms for retransmission, and both<br />
depend upon precise clocks to coordinate data flows. Furthermore, ATM has procedures for<br />
negotiating sessions that depend on the maintenance of precise timing and are intolerant of<br />
interruptions in the signal. Obviously, these protocols will not function correctly over an intermittent<br />
airlink absent appropriate middleware, and in the case of SONET, the restoration<br />
mechanism may even be invoked.<br />
Further problems may be anticipated when a multiservice switching platform sits at the<br />
core of the network in question and that platform has proprietary enhancements placed on top<br />
of the familiar transport protocols. One simply has no way of knowing how the middleware in<br />
the 802.16 airlink will cope with those ancillary protocols, but because they have been designed<br />
around a fiber connection, the likelihood is that problems will arise.<br />
The 802.16 standard generally supports IP, Ethernet, and ATM. No support is specified for<br />
frame relay, MPLS, RSVP, DiffServ, resilient packet ring (RPR), DOCSIS, MPEG video, or any IP