Wireless Hybrid QoS Architecture with an Enhancement of Fair Intelligent Congestion Control

More subtle and explicit QoS control mechanisms are required at the radio access level, even though the simple and scalable Differentiated Services (DiffServ) QoS control model is acceptable for the core of the network. At the radio access level, available resources are severely limited and the degree of traffic aggregation is not significant, thus rendering the DiffServ principles less effective. In this paper we present a suitable hybrid QoS architecture framework to address the problem. At the wireless access end, the local QoS mechanism is designed in the context of IEEE 802.11 WLAN with 802.11e QoS extensions; so streams of those session-based applications are admitted, established according to the traffic profile they require, and guaranteed. As the core in the Admission Control of the hybrid QoS architecture, the Fair Intelligent Congestion Control (FICC) algorithm is applied to provide fairness among traffic aggregates and control congestion at the bottleneck interface between the wireless link and the network core via mechanisms of packet scheduling, buffer management, feedback and adjustments. It manages effectively the overloading scenario by preventing traffic violation from uncontrolled traffic, and providing guarantee to the priority traffic in terms of guaranteed bandwidth allocation and specified delay.


Introduction
QoS limitations/bottleneck today often occurs within the wireless segment from the end-to-end data path based on our deployment experiences of Third Generation (3G) mobile networks and Wireless Local Area Networks (WLANs).This originates from the inherent properties of mobile radio environment [1][2][3].While the total resources available over the air interface are, on average, sufficient to meet the total resource requirements of the user application sessions admitted to the system, the level of QoS (Quality of Service) desired/expected by users may not be provided.Consequently, services that are tolerant of longer delay and higher rates of data loss is sacrificed.Therefore, more subtle and explicit QoS control mechanisms are required at the radio access level, particularly, with consideration given to the entire (end-to-end) network QoS.The drawbacks of QoS architectures proposed thus far vary from insufficient level of control implemented with DiffServ model only, especially over the resource-limited air interface, to scalability and complexity problems of solutions involving end-to-end use of RSVP/IntServ model [3,4].In this paper, a hybrid QoS architecture framework is presented suitable for new generation wireless IP networks.The proposed hybrid architecture follows the principles of Differentiated Service (DiffServ) model over the core part of the network, and the principles of Integrated Services (IntServ) model locally over the wireless access segment.
As the DiffServ part for the core network has been well studied in the literature, we then only further examine the resource management/explicit Admission Control in the radio access network as the key part of the hybrid QoS architecture for the mobile/wireless environment.The analyses are given in the context of 802.11WLAN; the admission control over WLAN is largely built on the 802.11MAC (Medium Access Control) QoS extensions.To address both fair bandwidth sharing among traffic classes and congestion problems encountered in the Admission Control core, an effective rate-based congestion control scheme, the Fair Intelligent Congestion Control FICC [5][6][7], is adopted and deployed.It intelligently predicts per-queue fair share for all traffic aggregates.FICC uses feedback control to keep the Resources Manager operating at a desirable operating point at all times.Resources Manager (RM) performs admission control in new flow establishment based on the current usages of the network and nature/class of new flow.It also allows overselling bandwidth when the network is not congested to make efficient use of the network resources.In section IV, a detailed analysis on FICC is given after discussions on the Hybrid Principle and its last-hop explicit Admission Control in Sections 2 and 3.

Differentiated Services at the Core
QoS architecture at the core network should be able to deliver quantitative differentiated services with suitable network control granularity, scalable and efficient network state management.In order to gain architectural scalability, the detailed control information (e.g., perflow states) and the supporting control mechanisms (e.g., per-flow queuing) are not practical in the design of core networks.Consequently, the resulting level of service differentiation between service classes is often qualitative in nature.However, network practitioners have to use quantitative provisioning rules to automatically engineer a network that experiences persistent congestion or device failure while attempting to maintain service differentiation.Therefore, a more dynamic form of provisioning is needed to compensate for the coarse-grained state information and the lack of network controllability if QoS is to be effectively realized.However, unlike traditional telecommunication networks, where traffic characteristics are well understood and well controlled and long-term capacity planning can be effectively applied, Internet traffic is more diverse and bursty, often exhibiting long range dependence [8].As a result, there is a need to design measurement-based dynamic control algorithms that can perform well under diverse traffic conditions.Another important challenge facing bandwidth management is the complexity associated with the rate control of traffic aggregates in core networks, which may comprise of flows exiting at different network egress points.This problem occurs when ingress rate control can only be exerted on a per traffic aggregate basis, (i.e., at the root of a traffic aggregate's point-to-multipoint distribution tree).Under such conditions, any rate reduction of an aggregate would penalize traffic flowing along branches of the tree that are not congested.
Based on the rationale discussed above, we considered differentiated services model for the core network.The model aggregates individual flows into a few classes either on their entrance to the network, or when they cross-administrative domains.At these points only, flows may be rate limited, shaped or marked to conform to specific traffic profiles.These profiles are either negotiated between users and network providers (for aggregation on the entrance to the network) or between neighbouring domains (for aggregation between domains).Inside a domain, each router only needs to select a Per Hop Behavior (PHB) for each packet based on its class.State aggregation into a few classes means that this approach scales well, but the guarantees that may be provided are not as fine grained as with the integrated services, which is not economical and practical to the core network.The architecture intentionally leaves the definition of PHBs and their implementations open to allow different schemes in different domains along the entire data path.The services provided by this architecture are meant to offer various generic QoS levels as opposed to application specific guarantees; hence the decision to map traffic classes instead of flows to PHBs.Only entry points to a network must be aware of both application requirements and PHB semantics to perform flow aggregation into classes.However, when resources are limited in some of these domains, traffic policing, meaning rate limiting, shaping and marking would be performed at these points based on traffic profiles.Therefore, depending on the PHBs available, end-to-end services may not be fully offered in a pure DiffServ environment where resources are limited in some of its domains.

Explicit Control over the Last Hop
As discussed, most traffic profiles are normally static at the entry point of the domains.Both stable allocations for real-time applications like streaming video and best effort allocation for bursty data applications like web transactions are likely if a differentiated services model is used over the wireless last lop.However, due to the increasing diversity of applications, device programmability emerging, resources limitation on the wireless links and the natures of wireless channel, a stable allocation service could be easily "overrun" by non real-time sensitive data applications.Under such conditions, lower priority packets take advantage of service differentiation by transiting their packets using the higher priority service class.This practice leads to the "tragedy of the commons" phenomenon.To avoid a total withdrawal of resources from the standard traffic classes with lower QoS requirements, e.g., other than Streaming, there is a share reserved for Interactive traffic from the pool of radio resources in the cell.In times of high load traffic flows with more demanding QoS requirements are allowed to displace flows belonging to applications with lower QoS requirements, but only up to a certain limit.The limits are specified by the maximum allowed number of active sessions for the regarded traffic class.When this limit is reached, the requested QoS is not accepted, but degraded to the next-lower-prioritized class.
While the limitation on standard traffic classes is in place, the bandwidth reservation and control mechanisms are still desired for those Interactive traffic, even though they involve a difficult trade-off between guaranteeing the full length of bandwidth reservation and inhibiting excessive bandwidth hogging.Hard reservation guarantees bear the complexity of admission control when multi-tiered service quality is required.This requires applications to declare the session length in advance, which none of the widely deployed applications can easily provide.The absence of mobile device participation in the control algorithm makes it hard for bandwidth reservation.However, the natures of the applications may imply certain QoS requirements.For example, a VoIP requires a stable bandwidth reservation while a file download may prefer a possible maximum allocation in the short term.The reservation based on these implications may slightly relieve users from declaring session lifetime, and gives early warning of any pending allocation degradation while keeping potential arbitrage.
The resource reservation for a flow is initiated by the receiver of the data flow and resources are requested for simplex flow only.Two-way reservations are emulated by making two simplex flows in opposite directions.The explicit path establishment and resource reservations rely on a signalling mechanism between the receiver and the Admission Controller (AC).However, such signalling is not necessary a RSVP.Even though RSVP is not a routing protocol, it relies on existing and future routing protocols to determine where packets get forwarded.The proper signalling mechanism is only concerned with the QoS of those packets that are forwarded; and should have options for its operation layer (IP-based or MAC-based), The selection should depend on the nature of networks, which may provide simplicity and effectiveness for such signalling.The signalling transports and maintains traffic control and policy control parameters that are opaque to the signalling.Its job is to transport these parameters from node to node, the actual processing of the traffic control and policy control parameters are performed by the relevant traffic control and policy control modules present in a node.These modules should at least include Admission Control and QoS profile negotiation to radio resource status monitoring.Particularly, AC should be responsible for handling activation and deactivation of flow requests, keeping track of traffic load and radio resource utilisation status, and performing QoS renegotiation.

Overall Hybrid Architecture
While the DiffServ model is useful in providing efficient and scalable QoS control within the network segments characterised by high volume of available resources and high aggregation of traffic (i.e.core/transport network), it fails to provide subtle enough tools for controlling QoS where the resources are strongly limited and the levels of traffic aggregation are low, e.g. in the wireless access network.The last hop (wireless access) radio resource management cannot rely solely on mechanisms providing differentiated treatment of packets that belong to different application sessions.To avoid degradation of QoS as the traffic generated by the users within the same access network increases, a mechanism is needed at the access network level to control the total resource requirements of the sessions admitted to the system (explicit admission control), and to reserve the amount of resources required by each session.Such mechanism, operating on a session-by-session basis, is the characteristic of the IntServ QoS model.The above argument serves as a brief justification for our choice of hybrid model with DiffServ principles applied over the core/transport network domain, and IntServ principles applied locally to the QoS control over the wireless access segment.
The proposed QoS control architecture in Figure 1 comprises of the DiffServ part in the core/transport network segments, and explicit resource management (admission control and reservation) part in the radio access network.Our architecture does not presume any specific QoS control model in the remote network where correspondent node (the other party in the application session) is located; it assumes that it is the other network's responsibility to guarantee, at its end, a QoS level consistent with that in the remaining parts of the path.The explicit resource management is localised to a single radio access network domain, where stateful and fine-granularity control mechanisms operating at the level of individual flows and application sessions can be applied without causing scalability and complexity concerns.The resource management at the access network level is based on functional blocks typical of IntServ model, i.e. admission controller and packet (frame) classifier/ scheduler, with multiple queues and service disciplines used to enforce QoS guarantees given to the flows (sessions) upon admission.However, unlike the IETF Int-Serv architecture, it does not use explicit end-to-end path establishment and resource reservations such as those available with RSVP.In the Section 3, it is outlined reliably achieved at the medium access control level as part of MAC functions, in the context of the current 802.11 standards.Central to the admission control, the FICC, an aggregate intelligent congestion control scheme is adopted particularly at the edge devices to ensure that the domain is not congested to the point that it cannot maintain the agreed level of QoS.FICC plays a key role in Admission Control by suggesting an optimal amount of traffic that should be admitted to maintaining an agreeable QoS level.The main purpose of FICC is to achieve the fair bandwidth allocation, minimum buffer queue length variation and simple implementation.It provides the required per-flow QoS response.The flow-level admission control focuses on keeping fairness between individual flows locally to ensure that the available resources are shared fairly with the pre-assigned allocation, while also trying to ensure delay performance when possible.For those session based application streams, the Admission Control functionality is responsible for their congestion/admission control.It is located at the Radio Resource Manager (RRM) and its decisions from FICC are made on the basis of stream QoS requirements and the current RRM's knowledge of the resource usage (reservation) status in the WLAN.The admitted streams are then registered with the edge router for the purpose of mapping between the 802.11e stream QoS descriptors (TSPEC) and stream identifiers (TSID), the user priority levels on the Ethernet distribution network, and the DiffServ DSCPs visible at the edge of core/transport network.The QoS signalling between the wireless station and the Access Point is accomplished by means of MAC level TSPEC negotiation defined in 802.11e, even though the signalling is initiated from the application level as shown in Figure 2. The Service Differentiation performed at the 802.11eMAC layer level ensures that the high priority (session streams) frames have transmission opportunities (TXOP) satisfying their QoS requirements, as promised at the time of stream admission.Lower priority traffic is treated according to "best effort" principles, filling in the bandwidth available after the session-based streams admitted to the system have been satisfied.Below Figure 2 explains the details of the QoS architecture described here.

Explicit Admission Control at the Last Hop
When a wireless station (STA) initiates, or is invited to, a session-based application, a session set-up dialog is carried out (we may think of a SIP Invite dialog as an example).The QoS agent in the STA will capture the QoS requirements of media streams involved in the session, and map them to a MA layer TSPEC description C as defined in the 802.11e.In order to request admission and reserve radio resources for the stream, an 802.11eADDTS-Request (add stream request) frame is sent to the AP.It carries a TSPEC element, which describes the source address (MAC), destination address, TSID, and QoS parameters of the stream.The QoS agent at the Access Point then forwards, in an IP packet, the admission request to the Admission Controller in the Radio Resource Manager.The RRM has "global" knowledge of the WLAN resources and reservation status; it will either admit or reject the stream, taking into account the resource usage across the WLAN.If the stream is successfully admitted, the RRM registers the stream with the edge router (via IP level communication) and sends a positive reply to the AP's QoS manager.Subsequently, a QoS ADDTS-Response frame is sent back to the wireless station, carrying a TSPEC element for the admitted stream.The admitted TSPEC could be as requested, or altered as a result of resource negotiation at the RRM.
In details, in order to make such a request, the client shall transmit a TSPEC request element contained in a management frame such as a generic management action request frame.The client may subsequently decide, using any heuristic algorithm it chooses, to explicitly request an amount of time per beacon interval for a specific class.On receipt of a TSPEC request element conveyed in any management frame, RRM shall respond to requests.The RRM may use any algorithm in making such a determi-nation.Having made such a determination, the RRM shall transmit a TSPEC response element to the requesting AP/client contained in a generic management action frame.In fact, the implementation for signalling procedure in the Hybrid structure largely replies on traffic stream operation between AP and client while the RRM remains to make the AC decision.The traffic stream operation is implemented using the facilities of Traffic Stream (TS) and TSPEC description provided in IEEE 802.11e.A TSPEC describes the QoS characteristics of a traffic stream (TS).The main purpose of the TSPEC is to reserve resources within the AP/RRM and modify the AP/RRM scheduling behaviour.It also allows other parameters to be specified that are associated with the traffic stream such as ACK policy and use of FEC (Forward Error Correction).A TSPEC is transported on the air by the ADDTS (Add TS) and DELTS (Delete TS) QoS Action frames and across the MLME (MAC sublayer management entity) SAP (service access point) by the MLME-ADDTS and MLME-DELTS primitives.Following a successful negotiation, a traffic stream is created, identified within the client by its TSID and Direction, and identified within the AP by a combination of TSID, Direction and client address.In the following sections, it firstly outlines the complete TS lifecycle in a state transition diagram and further details their procedures of each lifecycle state in the time sequence diagrams.
Figure 3 summarises the TS lifecycle.Initially TS is inactive.Following a successful TS Setup initiated by the client, the TS becomes active, and either the client or AP may transmit MPDUs (MAC Protocol Data Unit) using this TSID.While the TS is active, the parameters of the TSPEC characterising the TS can be re-negotiated as initiated by the client.This negotiation can succeedresulting in a change to the TSPEC, or can fail, resulting in no change to the TSPEC.Active TS becomes inactive following a TS deletion process initiated at either client or AP.It also becomes inactive following a TS timeout detected at the AP.
Once resources are reserved for a stream, application data frames must be classified in order for the service differentiation mechanism to be applied in the AP at the MAC layer level.The task of the classifier (for downlink traffic, in the edge router) is as follows: given an IP datagram of a particular flow (identified by, for example, the source/destination IP addresses and port numbers; we will refer to this as the flow ID), allocate the stream identifier (TSID) to the corresponding MAC data frame.For user data traffic on the uplink, the classification is straightforward because the QoS agent in the wireless station has knowledge of the streams generated by this station and admitted to the system.As a result, the TSID can be inserted directly into the MAC frame when it is generated at the station.For downlink traffic, classification is more complex because the AP operates only at the MAC layer level, and has no knowledge of the traffic flows at the IP level.The process of classification and mapping of IP flows onto the TSIDs must begin at a layer 3 device, i.e. the edge router, as below.
In details, for downlink traffic, the edge router examines IP packets to detect flows and marks the distribution network (e.g.Ethernet) MAC frames with a priority level based on the TSID previously registered for the flow (recall that as part of admission control procedures, the RRM notifies the edge router of new flows).The priority information in the 802.3 MAC frame on the distribution network is carried in the additional 802.1pheader (this additional header, which can be processed by most Ethernet products available today, carries a 3-bit user priority field).Therefore, when the router sends a distribution network MAC frame towards the AP, the frame contains the mobile host MAC address and the user priority value equal to the registered TSID.The AP's QoS agent must then interpret the Ethernet user priority field as the TSID for this frame.Together with the identity of the destination station, this determines the service differentiation treatment the frame will receive at the AP.In support of classifying downlink traffic using the Ethernet user priority field, the network should be configured as below.The WLAN distribution network should be separated from other parts of the LAN by an edge router where classification of flows is performed.Fixed hosts attached to the Ethernet (such as servers within the WLAN subnet) must be equipped with a QoS agent that ensures MAC frames sent by them are marked with the appropriate user priority that will be interpreted by the APs as TSID.These seem to be practical to most of recent Ethernet subnet today.

Fair Intelligence Congestion Control
While the above mechanism is built to provide an effective way to convey traffic information included in the TSPEC, between QoS Agent in the client/applications and RRM/AP, the decisive core part of Admission Control remains in its scheduling and controlling algorithm.Such core decides how to handle stream activation, QoS profile negotiation or/and requests deactivation while keeping track of traffic load and radio resource utilisation status.It certainly provides methods and objects to store, update and evaluate radio resource utilisation data as well as traffic-flow-related QoS profile data (Traffic Flow Template).It has to perform Admission Control on the basis of this data and react to changing resource utilisation in a radio cell by engaging QoS profile renegotiation procedures above.Performances on the admission control rely on such decision and its algorithms below.Here, we examine the effectiveness and efficiency of FICC, when applying to our hybrid model.
In fact, the keys of FICC are packet scheduling, buffer management, feedback and adjustments.The purpose of such admission control functions is to prevent congestion at the edge as well as within a DiffServ domain and to allocate resources fairly among traffic classes within the domain.It uses available resource information updated to calculate an Explicit Rate (ER) for each class.Per-flow admission control guarantees the fairness among individual flows within the same class.By doing, the control algorithm firstly attempts to maintain the queue length at the bottlenecked router along the path of the session close to a target point to avoid router buffer overflow and underflow.The bottlenecked router always operates at the full capacity of the output link without interruption from traffic congestion or buffer starvation.Thus, the most efficient throughput can be achieved.In addition, variations on queue length and consequently queuing delays are reduced.On the other hand, FICC attempts to allocate the available bandwidth fairly.Specifically, FICC tries to allocate bandwidth equally among aggregates (DSCPs) with equal status and to distribute the unused bandwidth (left over by constrained aggregates) fairly among the aggregates that can use an additional share.To achieve this objective, FICC oversells bandwidth when the network operates below the target point.And each sender is continuously informed about its current fair share based on the dynamic network traffic conditions by the feedback message.
FICC firstly estimates fair share of bandwidth for competing connections and feedback relevant information concerning the network conditions to the concerned router.Creating feedback loop mechanism between sources and router, a special packet-resource discovery (RD) packet is introduced to collect the router's state information, which is generated proportionally to the traffic.The source generates forward RD-packets for each flow proportionally to the arrival packet rate, which are turned around by the destination and sent back to the source as backward RD-packets.Such resources information, e.g.available bandwidth, available buffer is then to calculated in term of capacity for adjustment if required.To achieve such calculation, it is thus essential to relate appropriately the buffer queue length to the degree of network congestion.We use Mean Allowed Class Rate (MACR) to measure the estimated fair share of the aggregate.This MACR in turn is based on the queue length at the router and determines the explicit rate (ER) of an aggregate (the maximum rate at which the network informs the source of the aggregate that it can support).The "queue control function" is expressed using Buffer Utilization Ratio (BUR) of an output queue as the target percentage of buffer capacity that should be occupied.When the target is met, the queue occupancy is Buffer_Size*BUR.This target occupancy is designed to avoid link underutilization and the remaining buffer capacity Buffer_Size*(1 − BUR) is available to absorb packets that might arrive in the queue when the network becomes highly loaded.While BUR defines the target buffer operating point, the corresponding target queue length Q 0 (=BUR*Buffer_Size) is often referred to instead of BUR.Since the queue builds up and drains out continuously, the congestion function should be continuous to regulate smoothly the queue fluctuations through the computed ER values.A sophisticated and simple queue control function, the piecewise linear congestion function f(Q) is shown in (1).It would fine-tune the performance of the congestion control algorithm, however, it should also be pointed out that BUR only indicates the desirable long-term operational level.The actual buffer utilization fluctuates around this level.The actual algorithm is described as below.The target is to estimate its available bandwidth and advise the traffic sources appropriately.Firstly, the current traffic rate of all aggregates passing through it are estimated and allocated the available bandwidth fairly among its aggregates.As below, the MACR contained in TSPEC is updated with an the exponential average factor, which is a true exponential running average of the current load from all aggregates only when the network operates below the target operating point.When the network exceeds the target operating point, FICC does not allow MACR to increase further.That means that MACR does not track any ACR value larger than the current MACR when the queue is congested.This rule prevents all those aggregates whose ACRs are already equal larger than the current MACR to increase their rates further, thereby preventing further loading of the network.Instead, all aggregates have to reduce their rates to the same explicit rate and the throttling is performed fairly.However, when the network operates below the target operating point, all aggregates are allowed to increase their rate by a factor greater than 1 (that is what we mean by overselling), which enables aggregates that are capable of using the available bandwidth to take advantage of it.The explicit rate is calculated as above.

Parameters
ER = max (MCR, min (ER, DPF*MACR) RD protocol is responsible of ensuring communications FICC in RRM and QoS Agent in clients.Its agent in AP monitors available resources of wireless links (in MAC level) and provide such feedback to FICC.Such feedback includes MACR and ER.With the supports of the signalling mechanism we discussed in Section 3, RD information captures the resources availability and is conveyed in a TSPEC frame among RRM/AP and client using the mechanism we proposed.In RRM, information is generated, calculated and updated, then is sent to AP for execution of the determination to support clients' demand.With supports of RD and signalling mechanism discussed above, FICC manage the resources among traffic flows based on the algorithms and mechanism above.By combining such policy core and signalling mechanism in Section 3, all active traffic flows can be served according to the QoS profiles negotiated.Preferably, there are only a limited number of privileged connections allowed simultaneously.Furthermore, any standard traffic should receive the resources necessary to meet its QoS requirements.Thus, it would be preferable to reject or downgrade a stream activation request rather than to endanger the quality of all sessions.On the other hand, it might be advantageous to displace background or even interactive traffic flows to allow for an additional conversational traffic flow (such as VoIP) to be admitted.

Performance Analysis
In order to provide analysis on FICC in the Hybrid network, we use Network simulator ns2 to evaluate the network.The network topology is as shown in Figure 1, where both last hops of DiffServ Domain are wireless LAN.Several agents were designed in C++ to implement the schemes.The FICC is implemented particularly in AP and RRM, and we assume that wireless link is the bottleneck of network at 1 Mpbs bandwidth avaliable.The bandwidths and propagation delays of wired links are standard.There would be four classes of traffic, AF11 (Gold), AF21 (silver), AF31 (Bronze), and Best Effort, who claim 40%, 30%, 20%, and 10% resources respectively.They are mixture of TCP and UDP traffic in which Best Effort has UDP traffic and other three classes only have TCP traffic (in Gold, Silver, and Bronze).In the simulation, UDP traffic has constant bit rate is 1 Mbps so that it most likely causes the bottleneck.The simulation results for FICC and regular DiffServ permitted performance in terms of queue length, packet loss, end-to-end delay, throughput, goodput and fairness.The throughput is defined as the number of bits of all the TCP packets transmitted at the source (including RD packets if FICC was used) divided by the duration of the transmission.The goodput is defined as the number of bits of TCP packets transmitted at the source and successfully received at the destination divided by the duration of the transmission.
We firstly look at how the FICC could prevent traffic violation from certain classes, in order to avoid traffic congestion, which is the fundamental to FICC.In Figure 4, with regular DiffServ schemes, silver class traffic does occupy most of bandwidth, exceeding the gold class indeed, as it has shorter RTT, 32 ms.Obviously, sliver class/AF21 violates the traffic condition regarding of the class it has been assigned (sliver).The damage is that gold class and others could not be allocated for bandwidth fairly, as it has been agreed.Furthermore, the gold class actually experiences lower goodput at 0.28 Mpbs in average, as shown in Figure 4 and longer delay with larger queue length.
We further examine such from the queue performance with comparison between FICC and DiffServ as in Fig- ure 5.In FICC, the queue length around the target point is controlled; there is no congestion and no packet loss due to congestion during the transmission.The queue length variation and average queue length with FICC are also smaller than those under regular DiffServ.In Figure 5, this has been proven in the gold class traffic, as its queue length has been largely improved from average 60 to 20 as shown.As above, DiffServ could not prevent any traffic violation.In fact, under regular DiffServ scheme, there is sharp fall after the queue reaches 80, due to the queue length limitation and packet timeout.However, this does not happen under our FICC scheme.
Secondly, we look at the fairness of resources allocation between two schemes, and investigate how FICC fairly allocate resources among different classes/PHB.As  discussed, FICC always accurately estimates the fair share for each session at each router and constantly conveys the information to sender by RD and ACK packets.
Based on these feedbacks, traffics are policed and sessions with FlCC should share roughly the assigned amount of bandwidth.In Figure 6 below, it shows all four classes are allocated with 10%, 20%, 30% and 40% bandwidth, as agreed in the Admission Control.Particularly, in BE class, the UDP is carried with a constant bit rate of 1 Mpbs, which would overload the system, particularly in the wireless section.However, FICC could minimise its impact and fairly distribute the resources.
Comparing to FICC, DiffServ scheme performs poorly in resources allocation among classes as shown in Figure 7.  Furthermore, we look at such in term of queue resources.
In Figure 8, the queue length comparison between AF11 and BE shows us such fair distribution, as AF11 queue constantly maintain at average of 20 even it is already allocated 40% bandwidth, while BE may suffer itself as its large request for resources while only 10% is allocated.
Finally, we also provide the end-to-end delays performance comparison for regular DiffServ and FICC schemes.As the FICC not only could prevent traffic violation, but also provide intelligent admission control, which ensure the delay performance as well.In Figure 9, the majorities of delays in FICC are within 0.5 second to 0.7 second, while the delay performance in DiffServ ranges mainly from 1.0 second to 3.7 second.Furthermore, the delay distribution analysis below shows that in FICC, 44.11% contribution comes from 0.6 second, while delays in regular DiffServ spread across 0.5 and 3.7 with a maximum of 13.41% at 2.8 second delay.This indicate the jitter, delay variation in regular DiffServ is much worst than FICC.That could be a great impact in the delay-sensitive applications, such as Voice over IP.

Conclusion
In this paper, we have presented a hybrid QoS architecture framework for next generation wireless networks.The hybrid framework applies IntServ principles of explicit admission control and resource reservation locally only in the wireless access network domain, while remaining a DiffServ-enhanced QoS control model for the core/transport part of the end-to-end path.In the context of IEEE 802.11WLAN with 802.11eQoS extensions, a flow signalling mechanism has been designed to meet the proposed explicit admission control and resource reservation locally in the wireless access network.Particularly, Admission Control is implemented with a core of FICC as its algorithm in RRM, in a way that all active traffic flows can be served according to the QoS profiles negotiated.Simulation results have shown that FICC manages effectively the overloading scenario in the edge section, which is the resources bottleneck of the wireless access domain.Particularly, there are only a limited number of privileged connections allowed simultaneously and the pre-assigned traffic would receive the resources necessary to meet its QoS requirements.It prevents traffic violation from uncontrolled traffic by rejecting or downgrading a stream activation request fro background and BE, rather than to endanger the quality of all sessions; in such, guarantee is provided to those priority traffic in terms of guaranteed bandwidth allocation and specified delay.The results demonstrate that such a proposed hybrid framework with the Fair Intelligent Congestion Control can be realized for effective end-to-end QoS delivery.

Figure 3 .
Figure 3. State transition diagram of TS lifecycle.

Figure 7 .
Figure 7. Resources allocation of bandwidth in Diffserv.

Figure 8 .Figure 9 .
Figure 8. Resources allocation of queue length in FICC.Delay Distributions in FICC and DiffSErv