slide1
Download
Skip this Video
Download Presentation
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Loading in 2 Seconds...

play fullscreen
1 / 10

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) - PowerPoint PPT Presentation


  • 43 Views
  • Uploaded on

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Broadcast to Broadcast CTAs (multiple CAPs) Date Submitted: 16 March, 2004 Source: Jay Bain Company: Fearn Consulting Address : 703 Owens Drive, Huntsville AL 35801

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)' - osma


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Submission Title: Broadcast to Broadcast CTAs (multiple CAPs)

Date Submitted: 16 March, 2004

Source: Jay Bain Company: Fearn Consulting

Address: 703 Owens Drive, Huntsville AL 35801

Voice: 256 539 4778 , FAX: 256 539 7335, E-Mail: [email protected]

Source: Knut Odman Company: Motorola

Address: Mail stop VA18, 8133 Leesburg Pk, Vienna VA 22180

Voice: 703 269 3058, E-Mail: [email protected]

Abstract: Discussion and recommendations on 802.15.3 MAC to improve responsiveness.

Purpose: For information

Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.

Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15

problem definition
Problem definition
  • Management response time can be excessive for many applications
    • Time to associate and be payload ready
    • Time to do dynamic CTA changes
  • Less then efficient asynchronous communication
  • peer-to-peer probe operation not supported in MCTA
solution idea
Solution idea
  • Additional opportunities for communication within a given superframe
    • Multiple CTAs similar in functionality to CAP
  • Support for peer-to-peer MCTAs
  • Implementation via PNC placing BcstID as SrcID and DestID in CTA IE blocks
  • Use stream index to further refine as described later
other considerations for following slides
Other considerationsfor following slides
  • Slotted Aloha and CSMA/CA
  • Pseudo-static and dynamic CTA
  • Carryover of CSMA/CA backoff
  • Who can talk – relationship to CAP control bits (three bits)
slotted aloha and csma ca
Slotted Aloha and CSMA/CA
  • 802.15.3 PHY calls for use of CSMA/CA and CAP
  • Optional MCTAs call for use of slotted aloha method
  • Alt-PHYs determine method to use
  • Suggest retaining both schemes in this project
pseudo static and dynamic cta
Pseudo-static and dynamic CTA
  • The new CTA CAP should be given the same robustness as currently defined by pseudo-static CTAs
  • This allows use of CTA CAPs in the event that 1 to n (up to 4) beacons are corrupted. Current rules are followed.
carryover of csma ca backoff
Carryover of CSMA/CA backoff
  • Several CAPs may be present that are each of fairly short duration
  • The current CSMA/CA backoff should carry to other CTA CAPs in a given superframe and otherwise follow the current rules for backoff (8.4.2)
  • This requires further consideration !!
who can talk relationship to cap control bits three bits
Who can talk – relationship to CAP control bits (three bits)
  • Current CAP has three control bits –
    • Association
    • Commands
    • Data
  • Consider that either CTA CAPs behave as if all three bits are set, or that the command and data bits are set since association can be done in MCTA.
conclusion
Conclusion
  • The problems stated are resolved with the approaches outlined
  • Further discussion on several points are required
  • Additional issues/comments??
ad