26.07.2013 Views

WiMax Operator's Manual

WiMax Operator's Manual

WiMax Operator's Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

60 CHAPTER 3 ■ STRATEGIC PLANNING OF SPECTRUM AND SERVICES<br />

Packet-Based Services: A Business with Potential<br />

As with lower microwave, the network operator has a choice between IP and Ethernet. The<br />

802.16 protocol is built around IP, and IP is better suited for supporting quality of service,<br />

service differentiation, and service-level agreements. On the other hand, Ethernet is the<br />

protocol used in most internal enterprise LANs today and may be delivered over low-cost<br />

interfaces. Some wireless base station equipment has the ability to support both protocols in<br />

the last mile, and for certain operators that may make the most sense. IP and Ethernet are<br />

highly compatible, and Ethernet streams are easily transported over IP networks with little<br />

overhead or wasted capacity, but the network operator is still left with the choice of whether to<br />

opt for IP or Ethernet VPNs and of what type of packet telephony standards will be supported.<br />

Thus, choosing to support one protocol to the exclusion of the other on the access level<br />

imposes certain constraints on the network operator and the subscriber.<br />

My belief is that IP is better suited to service creation than is Ethernet but that Ethernet is<br />

better suited to service delivery—in other words, delivery of an IP stream over an Ethernet<br />

interface appears to make the most sense at this time in terms of both versatility and cost<br />

effectiveness.<br />

Whatever packet protocol is ultimately employed to manage the link between the base<br />

station and subscriber premises, the network operator should strive to differentiate the basic<br />

access service from T1 by the following means:<br />

The service velocity should be far higher than is the case for T1; that is, the operator should<br />

be able to provision the service rapidly, preferably within hours of an order being placed.<br />

T1 services typically involve a lengthy provisioning process often extending over several<br />

weeks. Providers of such services are highly vulnerable to competition on that account.<br />

Ideally, the service should lend itself to self-provisioning in the case of changes of service.<br />

If the subscriber wants to lease additional bandwidth for a short period of time to meet<br />

special needs, then the operator should permit this through a secure Web site with automatic<br />

billing processes registering the event.<br />

The service should allow for the leasing of fairly fine increments of bandwidth. In a SONET<br />

network the service is generally sold in extremely coarse increments, with DS3 (45Mbps)<br />

representing the next level of service above T1. Surveys indicate that most small- and<br />

medium-business users are interested in services with throughput rates from 2 to 10<br />

megabits per second—faster than T1 but significantly slower than DS3.<br />

Finally, the service provider should offer the same kind of options that have been traditional<br />

in ATM networks, including committed bit rates, bandwidth reservation where appropriate,<br />

and burstable rates where requirements for high bit rates are intermittent. Guarantees<br />

regarding jitter and latency are also desirable service offerings, particularly where the network<br />

must support conferencing and multimedia or a high degree of real-time interactivity. These<br />

are areas where circuit services such as T1 excel since circuits are by their very nature highly<br />

predictable, but such benefits are, in large measure, obtainable through some of the newer IP<br />

ancillary protocols such as DiffServ, RSVP, and MPLS as well as through specific QoS provisions<br />

within the 802.16 standard. Chapter 7 covers QoS in greater depth.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!