Transcript
QoS and multicast aware Integration of Ad-Hoc Networks with Infrastructure networks based on 802.11 and 802.16 Andreas Kassler - Nanyang Technological University, University, Singapore Sérgio Crisó Crisóstomo - LIAAC, Portugal Pedro Neves, Susana Sargento, Rui L. Aguiar – Instituto de Telecomunicaç Telecomunicações, Universidade de Aveiro, Portugal Network Integration and QoS
Why Ad Hoc Network Integration? -Internet and Mobile Networks will merge in the future -Increased interest in hot-spot scenarios -Ad Hoc Networks can be used to extend hot-spots – an increasing market even in hard to reach locations
Network Architecture and Multicast -Propose to use 802.16 links to connect Ad Hoc Islands to the Internet -Access Router (AR) connects 802.16 BS to Access Network and Internet -AR responsible for QoS mapping and Multicast connectivity -802.16 SS provides connectivity to the 802.11 based Ad Hoc Nodes -Multicast IP Gateways (MIG) -Forward information on group membership in ad hoc fringe to AR -Periodically advertise themselves as gateway towards Ad Hoc nodes -Standard Ad Hoc Nodes reactively create Multicast Mesh -Gateway runs standard IP Multicast Protocol -Gateway instructs BS about receivers interested in joining multicast groups -BS sets up multicast delivery in 802.16 associated to the ad-hoc multicast groups.
-IntServ and DiffServ not suitable for Ad Hoc networks due to frequent topology change,… -INSIGNIA requires per-flow state in intermediate nodes. Dynamic fluctuations in Ad Hoc network would lead to frequent re-negotiation in infrastructure network -FQMM does not comprise QoS admission control procedures. FQMM parameters, which are regulated in function of the effective local link bandwidth, do not reflect the link bandwidth between a source and a destination -We adopt SWAN and abstract the ad-hoc path between an ad-hoc node and the gateway as a virtual link to the infrastructure side -Admission control is performed with collaboration of the ad-hoc source nodes, as in the normal SWAN protocol.
Session Setup AMN1
Infra-Struct. Net.
GW
AMN2
CorrNode
App_Sig_Initiation + Probing Request (DSCP, RB, BB) Update BB
App_Sig_Initiation + Probing Request (DSCP, RB, BB)
Probing Resp(DSCP, BB)
Resources/QoS Checking App_Sig & Resource Reservation
App_Sig_Reply App_Sig Ack
Data
CID=0xFEFC
CID=0xFEFC
Dynamic Session Regulation AMN1
AMN2
Multimedia Internet Keying (MIKEY)
GW
Infra-Struct. Net.
Data session Class Y overload: Start marking ECN bits and dropping packets according to defined rules
MIG
Data session ECN detected Select sessions to degrade based on user profile Regulate Message(Flow info) Application Adaptation or Renegotiation
Testbed and Measurement results Contacts Andreas Kassler,
[email protected] Pedro Neves,
[email protected] Susana Sargento,
[email protected] Rui L. Aguiar,
[email protected] Sérgio Crisóstomo,
[email protected] DAIDALOS project: www.ist-daidalos.org
Acknowledgements This work is in part supported by the EU FP 6 for Research and Development Daidalos (IST-2202-506997).
QoS Mapping for 802.16 Wireless Broadband -In 802.16, each downlink/uplink CID has a service flow associated, configured with a set of QoS parameters -A SS requests uplink bandwidth on a per connection basis -Bandwidth is granted by the BS as an aggregate of all grants for an SS -We use classifier to map between 802.16 QoS and DiffServ TOS -In the downlink direction the classifier in the BS checks the fields that identify the flow and the TOS. Then it assigns this packet to the associated service flow -In the uplink direction, SS checks these fields in packets coming from the ad-hoc network. It maps them to a specified service flow.
CorrNode
