Showing posts with label QoS Architecture. Show all posts
Showing posts with label QoS Architecture. Show all posts

Wednesday, September 1, 2010

QoS Architecture for Efficient Bandwidth Management in the IEEE 802.16 Mesh Mode



Add a note hereThe IEEE 802.16 standard series represents the state-of-the-art in technology for metropolitan area broadband wireless access networks. The point-to-multipoint (PMP) mode of IEEE 802.16 has been designed to enable quality of service (QoS) in operator-controlled networks and, thus, is foreseen to complement existing third-generation cellular networks. In contrast, the optional mesh (MESH) mode of operation in IEEE 802.16 enables the setup of self-organizing wireless multi-hop mesh networks. A distinguishing characteristic of the IEEE 802.16 standard series is its support for QoS at the Medium Access Control (MAC) layer. However, the QoS specifications and mechanisms for the PMP and the MESH mode are not consistent. This article presents a novel QoS architecture as a key enhancement to the IEEE 802.16 MESH mode of operation. The architecture is based on the QoS mechanisms outlined for the PMP mode and, thus, enables a seamless coexistence of the PMP and the MESH mode. In particular, we look at the various options the standard provides and the trade offs involved when implementing QoS support in the 802.16 MESH mode, with a focus on the efficient management of the available bandwidth resources. This article is meant to provide researchers and implementers crucial anchor points for further research.

Add a note here1 Introduction and Motivation

Add a note hereThe demand for ubiquitous connectivity is the driving force for innovation in the field of wireless networks. To satisfy the differing demands of users a huge variety of wireless network platforms has developed over the years. Figure 1 shows some of the contemporary wireless access technologies.

Add a note hereFrom the figure, one can see that the IEEE 802.16 standard as published in  intends to support metropolitan area networks, rural networks, or enterprisewide networks. Initially these networks are expected to support only static nodes (subscriber stations). The standard IEEE 802.16-2004 specifies two modes of operation as shown in Figure 2. In the point-to-multipoint mode (PMP) all the Subscriber Stations (SSs) are required to be in direct range of the Base Station (BS). The SSs can directly communicate only with the BS. Direct communication between two SSs is not supported in the PMP mode. On the other hand, when operating in the MESH mode, the SSs are allowed to establish communication links with neighboring nodes and are able to communicate with each other directly. In addition, they are also able to send traffic to and receive traffic from the BS (a MESH BS is a SS, which provides backhaul services to the mesh network). The MESH mode of 802.16 allows for flexible growth in the coverage of the mesh network and also increases the robustness of the network due to the provision of multiple alternate paths for communication between nodes. An overview of the 802.16 standard is provided in. In addition, current efforts in the 802.16e task group have led to the publication of the IEEE 802.16e specification. The latter mainly offers enhancements to the IEEE 802.16-2004 to support mobility.


Add a note hereFigure 1: (a) Overview of contemporary wireless access network technologies showing the geographical scale of the wireless technologies. (b) Point-to-multipoint (PMP) mode of operation in 802.16. (c) Mesh mode (MESH) of operation in 802.16.
Figure 1: (a) Overview of contemporary wireless access network technologies showing the geographical scale of the wireless technologies. (b) Point-to-multipoint (PMP) mode of operation in 802.16. (c) Mesh mode (MESH) of operation in 802.16.

Add a note hereA distinguishing feature of the IEEE 802.16 standard is the extensive support for QoS at the MAC layer. In addition, the IEEE 802.16 standard outlines a set of physical layer (PHY) specifications which can be used with a common MAC layer. This flexibility allows the network to operate in different frequency bands based on the users' needs and the corresponding regulations. The QoS support and flexibility at the PHY layer in the 802.16 standard make it an optimal base to support multi-service networks. Thus, 802.16 networks are expected to play a significant role in next-generation broadband wireless access (BWA) networks. Such networks cater to the demand for the so-called "Triple Play" networks, that is, a single network supporting broadband Internet access, telephony, and television services. They are thus expected to replace conventional Digital Subscriber Line (DSL)-based access networks. The needs of each of these application categories are however varying. For example, applications such as interactive video conferencing, telephony, etc. require predictable response time and a static amount of bandwidth continuously available for the life-time of the connection. On the other hand, traffic like variable rate compressed video streams (e.g., to support television services) relies on accurate timing between the traffic source and destination but does not require a static amount of bandwidth over the duration of the connection. Some other applications such as data transfer using File Transfer Protocol (FTP) have no inherent reliance on time synchronization between the traffic source and destination. However, these applications benefit when the network attempts to provide a guaranteed bandwidth or latency. Some other services may not be very important from the providers' point of view, and traffic belonging to this class may be serviced on space-available basis. This type of traffic has usually no reliance on time synchronization between the traffic source and destination. An example of application generating the latter type of traffic is web surfing. The 802.16 standard defines different data scheduling services to support these types of traffic; thus, providing tools for network operators to support multi-service networks.

Add a note hereThe optional MESH mode of operation specified by the standard allows for organic growth in coverage of the network, with low initial investment in infrastructure. In addition, a mesh inherently provides a robust network due to the possibility of multiple paths for communication between nodes. Thereby, a mesh can help to route data around obstacles or provide coverage to areas which may not be covered using the PMP setup with a similar position for the BS as in the MESH mode. A mesh also enables the support of local community networks as well as enterprisewide wireless backbone networks. This application scenario makes the MESH mode very attractive to network providers, companies, and user communities. This article focuses on efficient management of bandwidth for realization of QoS in the MESH mode. In particular we look shortly at the nuts and bolts involved and the options provided by the standard. Although the IEEE 802.16-2004 standard specifies an extensive set of messages and mechanisms to realize QoS, the algorithms to realize QoS and manage bandwidth are left open to foster innovation and provide scope for vendor optimization. This article provides the readers with an overview of the scope for innovation and some critical challenges that need to be addressed to obtain a robust and efficient implementation of the IEEE 802.16 MESH mode.
WeAdd a note hereWewwe provide an overview of the QoS specification for the MESH mode as specified by the 802.16 standard. In particular, we introduce the mechanisms available in the PMP mode and the MESH mode. In future, IEEE 802.16-based networks are expected to support seamless interworking of nodes operating in the PMP and the MESH modes. The QoS specifications for the two modes however are not consistent. We provide an overview of our proposed QoS architecture for management of the bandwidth in the MESH mode to enable support of the data scheduling services similar to those available in the PMP mode.

Add a note hereFinally, we provide an insight into the benefits and effects of deploying our proposed QoS architecture which we have been able to observe via an intensive simulation study. The simulation study was carried out using a MESH mode simulator we built into the JiST/SWANS environment. We will here also highlight some promising areas for further investigation and outline areas for research which can build up on and extend the QoS architecture described by us.

Sunday, August 15, 2010

QoS Architecture | WIMAX

In general, the process of requesting and granting QoS in a network can be logically split in two separate layers: application and network layers. The application layer provides the end-user with a simplified and standardized view of the quality level that will be granted for a given service. This layer is not aware of the technicalities of service requirements (such as bandwidth, delay, or jitter) and it does not depend on the technology-dependent issues related to the actual networks that will be traversed (such as a fiber-optic, wireless, or xDSL). On the other hand, the network layer deals with a set of technical QoS parameters, which it maps on network-specific requirements that have to be fulfilled to provide the end-user with the negotiated quality level. Usually, in wired IP networks the mapping is performed at the network layer. However, such an approach is hardly suitable for wireless networks, where there are a number of factors that influence the resource allocation: (i) the availability of bandwidth is much more limited with respect to wired networks, (ii) there is high variability of the network capacity due, for instance, to environmental conditions, (iii) the link quality experienced by different terminals is location-dependent. Therefore, it is often necessary to implement QoS provisioning at the MAC layer, as in IEEE 802.16, so as to gain a better insight of the current technology-dependent network status and to react as soon as possible to changes that might negatively affect QoS.
Add a note hereIn IEEE 802.16 the prominent QoS functions of network provisioning and admission control are logically located on the management plane. As already pointed out, the latter is outside the scope of the IEEE 802.16, which only covers the data/ control plane, as illustrated in Figure 1. Network provisioning refers to the process of approving a given type of service, by means of its network-layer set of QoS parameters that might be activated later. Network provisioning can be either static or dynamic. Specifically, it is said to be static if the full set of services that the BS supports is decided a priori. This model is intended for a service provider wishing to specify the full set of services that its subscribers can request, by means of manual or semiautomatic configuration of the BS's management information base (MIB). On the other hand, with dynamic network provisioning, each request to establish a new service is forwarded to an external policy server, which decides whether to approve or not. This model allows a higher degree of flexibility, in terms of the types of service that the provider is able to offer to its subscribers, but it requires a signaling protocol between the BS and the policy server, thus incurring additional communication overhead and increased complexity.


Figure 1: Quality-of-service model of the IEEE 802.16.
Add a note here
Add a note hereUnlike the network provisioning function, which only deals with services that might be activated later, and that are therefore said deferred, the admission control function is responsible for resource allocation. Thus, it will only accept a new service if (i) it is possible to provide the full set of QoS guarantees that it has requested, and (ii) the QoS level of all the services that have been already admitted would remain above the negotiated threshold. Quite clearly, admission control acts on a time scale smaller than that of network provisioning. This is motivated by the latter being much more complex than the former, as pointed out by a recent study  on an integrated end-to-end QoS reservation protocol in a heterogeneous environment, with IEEE 802.16 and IEEE 802.11e  devices. Tested results showed that the network provisioning latency of IEEE 802.16 equipments currently available in the market is in the order of several seconds, whereas the activation latency is in the order of milliseconds.
Add a note hereIn IEEE 802.16, the set of network layer parameters that entirely defines the QoS of a unidirectional flow of packets resides into a service flow (SF) specification. Each SF can be in one of the following three states: provisioned, admitted, active. Provisioned SFs are not bound to any specific connection, because they are only intended to serve as an indication of what types of service are available at the BS. Then, when an application on the end-user side starts, the state of the provisioned SF will become admitted, thus booking resources that will be shortly needed to fulfill the application requirements. When the SF state becomes admitted, then it is also assigned a connection identifier (CID) that will be used to classify the SDUs among those belonging to different SFs. However, in this phase, resources are still not completely activated; for instance, the connection is not granted bandwidth yet. This last step is performed during the activation of the SF, which happens just before SDUs from the application starts flowing through the network.
Add a note hereThus a two-phase model is employed, where resources are booked before the application is started. This is the model employed in traditional telephony applications. At any time it is possible to "put on hold" the application by moving back the state of the SF from active to admitted. When the application stops the SF is set to either provisioned or deleted; in any case, the one-to-one mapping between the service flow identifier (SFID) and the CID is lost, and the CID can be reassigned for other purposes. The SF transition diagram is illustrated in Figure 2.


Figure 2: Service flow transition diagram.
Add a note here
Add a note hereFigure 3 shows the blueprint of the functional entities for QoS support, which logically reside within the MAC CPS of the BS and SSs. Each DL connection has a packet queue (or queue, for short) at the BS (represented with solid lines). In accordance with the set of QoS parameters and the status of the queues, the BS DL scheduler selects from the DL queues, on a frame basis, the next SDUs to be transmitted to SSs. On the other hand, UL connection queues reside at SSs.


Figure 3: Medium Access Control architecture of the Base and Subscriber Stations. 
Add a note here
Add a note hereBandwidth requests are used on the BS for estimating the residual backlog of UL connections. In fact, based on the amount of bandwidth requested (and granted) so far, the BS UL scheduler estimates the residual backlog at each UL connection (represented in Figure 3as a virtual queue, with dashed lines), and allocates future UL grants according to the respective set of QoS parameters and the (virtual) status of the queues. However, as already introduced, although bandwidth requests are per connection, the BS nevertheless grants UL capacity to each SS as a whole. Thus, when an SS receives an UL grant, it cannot deduce from the grant which of its connections it was intended for by the BS. Consequently, an SS scheduler must also be implemented within each SS MAC to redistribute the granted capacity to the SS's connections.

Related Posts with Thumbnails