Monday, March 19, 2012

How do I enable my VPN to work

A negative aspect of the 802.11e in the service provider's ,perspective is that it requires a hardware upgrade. That is, the ,legacy 802.11 MAC controllers cannot support the 802.11e. Our ,approach is to implement multiple queues in the device driver of ,the 802.11 MAC controller so that a frame scheduling can be ,performed in the driver level. A similar approach was made in ,[12][17]. In case of AP, this software upgrade means the firmware ,upgrade of the AP, which can be done even remotely.  ,Figure 6 shows the device driver structure for both the original ,device driver and a modified device driver supporting our ,approach. We have used the HostAP driver [2] of Intersil's Prism ,2.5 chipsets for our implementation. In the original driver, there is ,basically no queue for the frame transmission. A frame from the ,higher layer or from the wireline port is processed for the header ,and so on, and is forwarded to the MAC controller for the ,transmission. The MAC controller basically has a single first-in ,first-out (FIFO) queue. We have implemented two queues in the ,device driver level as shown in Figure 6 (b). We classify each ,frame to transmit into real-time (RT) or non-real-time (NRT). The ,current IP datagrams do not carry any information about the ,corresponding applications, and hence our implementation uses ,the port number as well as UDP packet type to classify a RT ,frame. That is, the device driver is provided the specific port ,number information of the real-time application in consideration. ,For example, KT's VoIP application utilizes a pre-assigned range ,of port numbers along with RTP over UDP protocols. For ,transmission scheduling, we have implemented a simple priority ,queuing so that the NRT queue is never served as long as the RT ,queue is not empty. We are currently investigating a more ,intelligent scheduling as will be discussed below.,

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.