Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11- 05-0623-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 1 Joint Wireless Groups Architecture AdHoc Notice: This document.

Similar presentations


Presentation on theme: "Doc.: IEEE 802.11- 05-0623-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 1 Joint Wireless Groups Architecture AdHoc Notice: This document."— Presentation transcript:

1 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 1 Joint Wireless Groups Architecture AdHoc Notice: This document has been prepared to assist IEEE 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// Date:

2 doc.: IEEE Submission Month Year Tom Siep, Cambridge Silicon Radio PlcSlide 2 Abstract Notes and slides from Ad Hoc meeting on Architecture for 802 wireless standards held 17May05. Background slides are from Architecture forum. Notes are on slide 9 Output of meeting on slide 10 NOTE: previous versions of slide 9 incorrectly had the number of yes votes as 13 instead of 3. Typo highlighted in RED

3 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 3 Agenda for Ad Hoc Tuesday Evening PURPOSE: Brief ad hoc attendees and prepare for Plenary meeting of Architecture Consolidate 802.wireless communitys architecture issues –Quality of Service –Security –Management –Other? Determine if we, as the wireless 802 community, want to: –Present a common set of issues –Request formation of a TAG to address architecture issues

4 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 4 Attendees (1 of 2) Last NameFirst Name AddressWG HiertzGuido

5 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 5 Attendees (2 of 2) Last NameFirst Name AddressWG KimRonny HendersonG. ZunigaJuan JeomSoon

6 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 6 Intent for Arch Committee Improve alignment between WG projects and existing 802 architecture by: –Identifying current problems, omissions, conflicts, ramifications, and their potential resolution –Identifying potential refinements or changes to the architecture –Providing a regular forum in which such discussion can take place, in a lower pressure environment than is possible during the core Plenary cycle.

7 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 7 Proposals for resolution Due diligence issues – need to fix 802 procedures –TJ to propose to SEC that the rules for forwarding to SB & RevCom be strengthened –WGs should review projects against PAR/5C requirements during the development cycle Each WG: –Prioritize issues –Characterize the problem –Propose approach to resolve, or identify as intractable –Identify other groups (802 or external) that may be affected

8 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 8 Pending PARs Security –This standard specifies unique per-device identifiers (DevID) and the management and cryptographic binding of a device to its identifiers, the relationship between an initially installed identity and subsequent locally significant identities, and interfaces and methods for use of DevIDs with existing and new provisioning and authentication protocols. –See xxxx Summary_of_PAR-5C_of_P802-1AL.ppt Management of RF –This standard specifies protocols, procedures, and managed objects to support Radio Frequency (RF) management across IEEE 802 wireless Media Access Control (MAC) layers. –See xxxx Summary_of_PAR-5C_of_P802-1AM.ppt

9 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 9 Discussions at Architecture Meeting ~60 people present (40 signed attendance sheet) Discussion turned initially to the 802.1AM PAR –There was concern that may not have the expertise to do the RF management task –Question: Is management of an RF system fundamentally different than a wired system? Yes. –Straw poll: Do you favor approval of the 802.1AM PAR? yes 3; no 20; reserve judgment 13 Discussion then turned to what wireless groups need in common –Straw poll: Is a common language needed for wireless for communicating operational characteristics and status of dissimilar wireless systems? yes 23; no 1; reserve judgement15

10 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 10 Output from Wireless Architecture Ad Hoc Discussions in Cairns Establish a joint wireless systems study group to address common 802 wireless issues consisting of representatives of the various wireless groups –Focus on cooperation between wireless groups –Might lead to formation of a TAG or WG or TGs within a WG or a standing committee –Support coexistence or handoff efforts, not duplicating –Investigate a common language for communicating operational characteristics and status of dissimilar wireless systems Action: representatives from all wireless groups to present the above request for approval

11 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 11 BACKUP SLIDES: Inputs to Arch Ad Hoc Presented at Monterey

12 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 12 Prioritized issues – Management –LLC – acts as a block to passing additional (e.g., QoS) parameters –QoS –(Signal) Power/channel management Bridging compatibility –handling of multicasts, no clause 6 section for.1D

13 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 13 LLC – acts as a block to passing additional (e.g., QoS) parameters All 3 MAC need LLC support to requests to create/modify/terminate streams based on QoS parameters Data needs to be able to be associated with a stream at the MAC SAP QoS changes need to be communicated to the higher layers Need to be able to inquire QoS characteristics of remote nodes

14 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 14 QoS Block asynchronous data –Need block size to plan and allocate resources

15 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 15 (Signal) Power/channel management Need a way to pass (up and down) information that is important to wireless, for example –Transmit power –Regulatory domain –Signal quality –Coexistence information –Other Must be extensible

16 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 16 Bridging compatibility – handling of multicasts, no clause 6 section for.1D Compatibility with.1D –15.1a – Bridging is handled in BNEP, which maps to Ethernet. –15.3 – Annex A (normative) specifies compatibility –15.4 – Annex A (normative) specifies compatibility Multicasts –15.1a – does not do multicast –15.3 – Had multicast, being revised in current work –15.4 – Had broadcast, being revised to include multicast in current work

17 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 17 Other Groups Affected LLC – acts as a block and QoS and (Signal) Power/channel management and Bridging compatibility – internal problem being worked

18 doc.: IEEE Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 18 Work to be done by Form plans to solve issues Determine feasibility of plans Study proposal to use IETF model for QoS – will it work for.15 TGs? Characterize management function needs Cant do bridging 64 to 48 bit addresses – are we OK with this?


Download ppt "Doc.: IEEE 802.11- 05-0623-00-0000 Submission May 2005 Tom Siep, Cambridge Silicon RadioSlide 1 Joint Wireless Groups Architecture AdHoc Notice: This document."

Similar presentations


Ads by Google