Sunday, September 5, 2010

QoS Support in the 802.16 PMP Mode

The 802.16 MAC is connection-oriented. QoS is provisioned in the PMP mode on a per-connection basis. All data, either from the SS to the BS or vice versa is transmitted within the context of a connection, identified by the connection identifier (CID) specified in the MAC protocol data unit (PDU). The CID is a 16-bit value that identifies a connection to equivalent peers in the MAC at both the BSs as well as the SSs. It also provides a mapping to a service flow identifier (SFID). The SFID defines the QoS parameters which are associated with a given connection (CID). The SFID is a 32-bit value and is one of the core concepts of the MAC protocol. It provides a mapping to the QoS parameters for a particular data entity.
Figure 1 shows the core objects involved in the QoS architecture as specified in the standard for the PMP mode. As is seen from Figure 1 , each MAC PDU is transmitted using a particular CID, which is in turn associated with a single service flow identified by a SFID. Thus, many PDUs may be transmitted within the context of the same service flow but a single MAC PDU is associated with exactly one service flow. Figure 1 also shows that there are different sets of QoS parameters associated with a given service flow. These are the "ProvisionedQoSParamSet," "AdmittedQoSParamSet," and "ActiveQoSParamSet." The provisioned parameter set is a set of parameters provisioned using means outside the scope of the 802.16 standard, such as with the help of a network management system. The admitted parameter set is a set of QoS parameters for which resources (bandwidth, memory, and so on) are being reserved by the BS (SS). The active parameter set is the set of QoS parameters defining the service actually being provided to the active flow. For example, the BS transmits uplink and downlink maps specifying bandwidth allocation for the service flow's active parameter set. Only an active service flow is allowed to transmit packets. To enable the dynamic setup and configuration of service flows, the standard specifies a set of MAC management messages, the so-called dynamic service messages (DSx messages). These are the dynamic service addition (DSA), dynamic service change (DSC), and the dynamic service deletion (DSD) messages. The various QoS parameters associated with a service flow are negotiated using these messages.


Add a note here
Figure 9.2: Quality-of-service (QoS) object model for IEEE 802.16-2004 point-to-multipoint mode.
Add a note hereTypical service parameters associated with a service flow are traffic priority, minimum reserved rate, tolerated jitter, maximum sustained rate, maximum traffic burst, maximum latency, and scheduling service. The BS may optionally create a service class as shown in Figure 1 . A service class is a name given to a particular set of QoS parameters, and can be considered as a macro for specifying a set of QoS parameters typically used. The value for the scheduling service parameter in the QoS parameter set specifies the data scheduling service associated with a service flow. The 802.16 standard currently defines the following data scheduling services: Unsolicited Grant Service (UGS), Real-Time Polling Service (rtPS), Non-Real-Time Polling Service (nrtPS), and Best Effort (BE). The UGS is meant to support real-time data streams consisting of fixed-size data packets issued periodically. The rtPS is meant to support data streams having variable-sized data packets issued at periodic intervals. The nrtPS is designed to support delay-tolerant streams of variable-sized data packets for which a minimum data rate is expected. The BE traffic is serviced on a space-available basis. For service flow associated with the scheduling service UGS, the BS allocates a static amount of bandwidth to the SS in every frame. The amount of bandwidth granted by the BS for this type of scheduling service depends on the maximum sustained traffic rate of the service flow. For rtPS service flows, the BS offers real-time, periodic, unicast request opportunities meeting the flow's requirements and allowing the SS to request a grant of the desired size. For nrtPS the BS, similar to the case of a rtPS service flow, offers periodic request opportunities. However, these request opportunities are not real-time, and the SS can also use contention-based request opportunities in addition to the unicast request opportunities for a nrtPS service flow as well as the unsolicited data grant types. For a BE service flow no periodic polling opportunities are granted. The SS uses contention request opportunities, unicast request opportunities, and unsolicited data grant burst types. 
Add a note hereTo summarize, the PMP mode provides the BS with efficient means to manage the bandwidth optimally and at the same time satisfy the requirements of the individual admitted service flows.

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 29, 2010

Resource Request and Scheduling Policies



Add a note hereIEEE 802.16e-2005 divides all possible data services into five classes: Unsolicited Grant Service (UGS), Real-Time Polling Service (rtPS), Extended Real-Time polling Service (ErtPS), Non-Real-Time Polling Service (nrtPS), and Best Effort (BE). Each service is associated with a set of quality of services (QoS) parameters that quantify aspects of its characteristics: (a) maximum sustained rate, (b) minimum reserved rate, (c) maximum latency tolerance, (d) jitter tolerance, and (e) traffic priority.

Add a note hereThe aforementioned parameters are the basic inputs for the service scheduler placed in the BS, whose design and implementation are left to the manufacturers, which is aimed at fulfilling service-specific QoS requirements.

Add a note hereWithin IEEE 802.16, in particular, the scheduler task is to define both uplink and downlink resource allocation maps (UL-MAP and DL-MAP) on the basis of the users' needs. With reference to BE services, an insight on the bandwidth request mechanism is provided in the following subsections and a fair and efficient scheduling strategy is proposed.

1. BE Resource Requests

Add a note hereIn order to support BE services (FTP, web browsing, and so on), a resource request mechanism is needed to make the scheduler aware of MSs bandwidth requirements in both directions.

Add a note hereAs for the DL direction, however, it is immediate to understand that the scheduler has a perfect knowledge of MSs needs, because they coincide with the amount of data waiting to be transmitted in the respective BS transmission queues.

Add a note hereAs far as the UL is concerned, on the contrary, a request mechanism is introduced by the standard, which allows MSs to make use of (a) contention request opportunities, (b) unicast request opportunities, and (c) unsolicited data grant burst types. In the first case a bandwidth request is transmitted during the appropriately shared UL allocation, whereas in the other two cases each MS is given a reserved UL resource to convey its request.

Add a note hereAll requests for bandwidth are made in terms of number of bytes needed to carry MAC PDUs.
Add a note hereOnce an MS is given the UL resource, further bandwidth requests may come as a piggyback request, thus avoiding to resort again to one of the three bandwidth request mechanisms introduced before (a, b, and c).
Add a note hereBandwidth requests may be incremental or aggregate; in the former case the BS adds the amount of bandwidth requested to its current perception of the bandwidth needs of the connection, whereas in the latter case it replaces its perception of the bandwidth needs of the connection with the amount of bandwidth requested. The type field in the bandwidth request header indicates whether the request is incremental or aggregate. Because piggyback bandwidth requests do not have a type field, piggyback bandwidth requests shall always be incremental.

Add a note hereThe mechanism of piggyback incremental requests can be conveniently exploited to reduce the time wastage due to the complete bandwidth request mechanism: it is reasonable to operate in such a way that the first time an MS performs a bandwidth request (adopting one of the three previously introduced procedures), it notifies the BS the dimension of the entire amount of data waiting in its transmission queue. This way the BS has an exact knowledge of each MS need and can update it (decreasing) each time PHY-level resources are assigned to that connections and the related transmissions are correctly acknowledged.

Add a note herePossible further data incoming in the MS queue while transmissions are still ongoing (i.e., before the MS queue gets empty) can be notified to the BS scheduler through the incremental piggyback bandwidth requests, which will determine a variation of the perception of MS bandwidth needs.

2. BE Scheduling

Add a note hereIn this section we still focus on BE data services and we show how to provide, at the same time, a fair and efficient resource sharing, carefully considering IEEE 802.16e-2005 specific characteristics.

Add a note hereAs far as the fairness issue is concerned, here we considered a round robin (RR) scheduling policy among all BE services. Although this choice seems the most suited to this kind of service, it has to be pointed out that its implementation, as well as the implementation of any other scheduling policy, requires some preliminary consideration on the nature of IEEE 802.16e-2005 radio resource (the OFDMA-Slot).

Add a note hereBecause the different modes that can be adopted by users convey, in a single OFDMA-Slot, different amounts of data, it follows that, to provide a really fair scheduling among BE users, a different amount of slots has to be allocated to each of them.

Add a note hereTo meet as much as possible the aforedescribed fairness requirement, hence avoiding that users with huge amount of data to be transmitted gather the most of resources, it is convenient to define an elementary resource unit, hereafter called Virtual Resource Unit (VRU), consisting in a fixed amount of data bytes, which is the basic element assigned by the scheduler in each RR cycle to BE users needing resources.

Add a note hereTo better understand the scheduler behavior, let us focus our attention, for instance, on the DL subframe: the scheduler task is, in this case, to define the DL-MAP, assigning PHY-level resources to the different BS → MS links requiring DL resources.

Add a note hereAs long as there is room (in terms of available slots) in the subframe and there are pending data that can be allocated in it, the scheduler moves from an user to the next, performing the following actions: (i) it assigns a VRU to the user, adding it to its Virtual Resource Budget (VRB); then, (ii) it virtually generates the biggest PDU that can be allocated, and (iii) correspondingly makes a slot booking; this means that although the scheduler does not effectively allocate the PDU at this time, that amount of slots is definitively reserved to that user; at the next round a bigger PDU or more PDUs may be allocated following the increased VRB, thus increasing the amount of booked slots. Please note that the scheduler would not do any slot reservation until VRB is not enough to allocate a PDU containing a single ARQ block. When the RR cycle ends (i.e., no more room or no more data to be allocated), the PDUs are effectively generated and the coding-mapping processes described in Section 8.2.3 can take place.

Add a note hereThe separation between the virtual and physical allocations guarantees a flexible management: as an example, doubling the VRB (during the second round) may allow, for instance, to generate a PDU that includes two ARQ blocks and this could be preferred than generating and transmitting two separate PDUs with a single ARQ block each.

Add a note hereAt the end of the allocation procedure users' VRBs are not reset, to allow stations with larger ARQ blocks to gain the same long-term priority as the others. Furthermore, VRB will be increased at most up to the amount of pending data.

Add a note hereThe same procedure is performed also for the definition of the UL-MAP, which is carried out on the basis of UL resource request made by users.

Add a note hereTo preserve fairness at most, in the next subframe of the same kind (UL or DL) the cyclic scheduling procedure will start from the user that follows, in the cyclic order, the last user served in the current frame.

Related Posts with Thumbnails