1 / 28

VHT SG September 2008 Report

VHT SG September 2008 Report. Authors:. Date: 2008-09-05. Patent Policy. Following 5 slides. The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: Show slides #1 through #4 of this presentation Advise the WG attendees that:

shelly
Download Presentation

VHT SG September 2008 Report

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VHT SG September 2008 Report Authors: Date: 2008-09-05 Eldad Perahia, Intel Corporation

  2. Patent Policy • Following 5 slides Eldad Perahia, Intel Corporation

  3. The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: Show slides #1 through #4 of this presentation Advise the WG attendees that: The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws; Early identification of patent claims which may be essential for the use of standards under development is strongly encouraged; There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under development. Instruct the WG Secretary to record in the minutes of the relevant WG meeting: That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance. It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 12 and 12a on inclusion of potential Essential Patent Claims by incorporation or by reference. Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board. Instructions for the WG Chair (Optional to be shown) Eldad Perahia, Intel Corporation

  4. Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents orpatent claims • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) • The above does not apply if the patentclaim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2 • Early identification of holders of potential Essential Patent Claims is strongly encouraged • No duty to perform a patent search Slide #1 Eldad Perahia, Intel Corporation

  5. All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/guides/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/guides/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/board/pat/pat-material.html Patent Related Links If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide #2 Eldad Perahia, Intel Corporation

  6. If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: Either speak up now or Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or Cause an LOA to be submitted Call for Potentially Essential Patents Slide #3 Eldad Perahia, Intel Corporation

  7. Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • Technical considerations remain primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Slide #4 Eldad Perahia, Intel Corporation

  8. VHT60 Review joint conference call with 802.15.3c Review VHT60 conference call Review EC conference call Update PAR based on feedback SG/WG motion on PAR Joint meeting with 802.15.3c VHTL6 Review Nescom feedback Agenda Items for the Week • General items • Discussion of timelines • Review from July • Submissions Eldad Perahia, Intel Corporation

  9. Monday Sept 8th, 13:30 – 15:30 Patent policy, etc. Set agenda Call for submission Review from July Discussion of timelines Review VHTL6 Nescom feedback Review VHT60 joint conference call with 802.15.3c Review VHT60 conference call Review EC conference call Discuss agenda for joint meeting Presentations Monday Sept 8th, 19:30 – 21:30 Joint meeting with 802.15.3c on 60 GHz PAR Tuesday Sept 9th, 8:00 – 10:00 VHT60 PAR development Presentations Tuesday Sept 9th, 16:00 – 18:00 VHT60 PAR development PAR motion Presentations Thursday Sept 11th, 10:30 – 12:30 Reaffirm agenda Update VHT60 PAR based on WG feedback, if necessary VHTL6 discussion Presentations Thursday Sept 11th, 13:30 – 15:30 Reaffirm agenda Update VHT60 PAR based on WG feedback, if necessary PAR motion, if necessary VHTL6 discussion 15:00 Review time line Goals for November Conference calls Presentations Tentative Agenda for the Week Eldad Perahia, Intel Corporation

  10. Agenda for Monday July 14th • Patent policy, etc. • Set agenda • Call for submission • Review from July • Discussion of timelines • Review VHTL6 Nescom feedback • Review VHT60 joint conference call with 802.15.3c • Review VHT60 conference call • Review EC conference call • Discuss agenda for joint meeting • Presentations Eldad Perahia, Intel Corporation

  11. Call for Submissions • Information on following subjects will assist us in creating a PAR and 5 Criteria: • Market needs, applications, usage scenarios • Technology & feasibility • MAC efficiency evaluation and enhancements, including evaluation of 11n MAC with higher PHY rates • PHY enhancements to 11n • new MAC & PHY technology • Requirements • metrics (i.e. throughput, network capacity, spectral efficiency, range) • coexistence / interoperability • Spectrum availability & regulatory options • relationship with IMT-Advanced Eldad Perahia, Intel Corporation

  12. Submissions • Proposed Modifications to VHT60 PAR, 08/998r2, Eldad Perahia • VHTL6 task group work plan proposal, 08/1032, Marc de Courville • Alexander Maltsev • Leonardo Lanante Eldad Perahia, Intel Corporation

  13. Reviewed initial PAR feedback and prepared responses From individuals, 08/812r0, 08/855r0 From 802.15.3c, 08/724r2 Reviewed Tutorials 60 GHz Tutorial, Eldad Perahia, 08/814r1 <6 GHz Tutorial, Marc De Courville, 08/825r0 Joint meeting with 802.15 regarding 60 GHz 802.11 user experience, Gal Basson, 08/848r0 Reviewed official PAR feedback and prepared responses, 08/880r1 Based on feedback, updated PAR & 5C’s 60 GHz: 08/806r3 <6 GHz: 08/807r3 Reviewed EC report, 08/813r1 Presentations Backward Compatible or Not?, Junghoon Jee, 08/790r0 Channel Modeling for 60 GHz WLAN Systems, Alexander Maltsev, 08/0811r1 Some Ambiguities about Throughput Conditions in PAR, 08/821r3, Minho Cheong Approved PAR & feedback response motion in mid-week plenary Motion for SG extension approved by SG , WG, EC EC PAR vote VHTL6 passed VHT60 failed Goals for September Officer elections (will occur in WG) If necessary, Update PAR’s & 5C’s based on feedback from EC or NesCom Complete work on PAR & 5 C’s and re-submit motion to WG At least first session as VHT joint meeting If possible split into VHT60 and VHTL6 and begin Task Group work Topics TG process Technical contributions Review from July Eldad Perahia, Intel Corporation

  14. May 2007 (Interim) Initial meeting July 2007 (Plenary) Presentations WG approval of SG extension to Nov Sept 2007 (Interim) Presentations Nov 2007 (Plenary) Presentations SG motion for extension to March Jan 2008 (Interim) Presentations Initial version of PAR & 5 C’s Mar 2008 (Plenary) Presentations Work on PAR & 5 C’s SG/WG/EC motion for extension to July May 2008 (Interim) final version of PAR & 5 C’s WG approval June 2008 EC submission by June 17 July 2008 (Plenary) WG re-approval (if necessary) SG/WG/EC motion for extension to Sept EC approval on July 18 Aug 2008 NesCom submission by Aug 8 Sept 2008 (Interim) VHTL6 TG unofficially begins NesCom meeting on Sept 17 Nov 2008 (Plenary) TGac (VHTL6) officially starts Time Line for VHTL6 Eldad Perahia, Intel Corporation

  15. May 2007 (Interim) Initial meeting July 2007 (Plenary) Presentations WG approval of SG extension to Nov Sept 2007 (Interim) Presentations Nov 2007 (Plenary) Presentations SG motion for extension to March Jan 2008 (Interim) Presentations Initial version of PAR & 5 C’s Mar 2008 (Plenary) Presentations Work on PAR & 5 C’s SG/WG/EC motion for extension to July May 2008 (Interim) final version of PAR & 5 C’s WG approval July 2008 (Plenary) WG re-approval SG/WG/EC motion for extension to Sept Sept 2008 (Interim) Work on PAR & 5 C’s October 20, 2008 NesCom PAR submission deadline for Dec. meeting Nov 2008 (Plenary) final version of PAR & 5 C’s SG/WG/EC motion for extension to Mar EC PAR approval on Nov 14 December 9, 2008 NesCom meeting Jan 2009 (Interim) VHT60 TG unofficially begins Mar 2009 (Plenary) Task Group officially start Time Line for VHT60 Eldad Perahia, Intel Corporation

  16. Nescom feedback on VHTL6 (1/4) • WG11 received several suggestions for editorial changes to the VHTL6 PAR submitted to NesCom for approval • After reviewing the requested changes the WG chair made editorial modifications to the VHTL6 PAR shown in the next slides Eldad Perahia, Intel Corporation

  17. New: 5.2 Scope of Proposed Standard: This amendment defines standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) that enable modes of operation capable of supporting: A maximum multi-station (STA) throughput (measured at the MAC data service access point), of at least 1 Gbps and a maximum single link throughput (measured at the MAC data service access point), of at least 500 Mbps. Below 6 GHz carrier frequency operation excluding 2.4 GHz operation while ensuring backward compatibility and coexistence with legacy IEEE802.11 devices in the 5 GHz unlicensed band. Old: 5.2 Scope of Proposed Standard: Scope of Proposed Standard:The scope of this project is to define an amendment that shall define standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) so that modes of operation can be enabled that are capable of supporting: A maximum multi-station (STA) throughput (measured at the MAC data service access point), of at least 1 Gbps and a maximum single link throughput (measured at the MAC data service access point), of at least 500 Mbps. Below 6 GHz carrier frequency operation excluding 2.4 GHz operation and ensuring backward compatibility and coexistence with legacy IEEE802.11a/n devices in the 5 GHz unlicensed band. Nescom feedback on VHTL6 (2/4) Eldad Perahia, Intel Corporation

  18. New: 5.4 Purpose of Proposed Standard: The purpose of the amendment is to improve the 802.11 wireless local area network (LAN) user experience by providing significantly higher basic service set (BSS) throughput for existing WLAN application areas and to enable new market segments for operation below 6 GHz including distribution of multiple multimedia/data streams. Old: 5.4 Purpose of Proposed Standard: The purpose of the project is to improve the 802.11 wireless local area network (LAN) user experience by providing significantly higher basic service set (BSS) throughput for existing WLAN application areas and to enable new market segments for operation below 6 GHz including distribution of multiple multimedia/data streams. Nescom feedback on VHTL6 (3/4) Eldad Perahia, Intel Corporation

  19. New: 5.6 Stakeholders for the Standard: Manufacturers and users of semiconductors, personal computers, enterprise networking devices, consumer electronic devices, and mobile devices. Old: 5.6 Stakeholders for the Standard: Manufacturers and users of semiconductor, personal computer, enterpise networking device, consumer electronic device, mobile devices. Nescom feedback on VHTL6 (4/4) Eldad Perahia, Intel Corporation

  20. Review of VHT60 Aug 20 joint conference call with 802.15.3c • Two presentations • Proposed modifications to VHT60 PAR, Eldad Perahia, https://mentor.ieee.org/802.11/file/08/11-08-0988-00-0vht-proposed-modification-to-vht60-par.ppt • Replace coexistence scope statement with “Supports mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band” • Add 802.15.3c and ECMA TC48 to Section 7.1 (Are there other standards or projects with a similar scope?) • Discussion on “Current TG3c Modulation and Coding Schemes and Performance Examples”, Shu Kato, https://mentor.ieee.org/802.15/file/08/15-08-0580-00-003c-current-tg3c-modulation-and-coding-schemes-and-performance-examples.pdf Eldad Perahia, Intel Corporation

  21. Review of VHT60 Aug 21 conference call • Reviewed all proposed permutations of coexistence scope statement from Aug 20 joint conference call with 802.15.3c • Ran electronic strawpolls (results in brackets, 20 participants total) • SP1 • Preferred wording for coexistence in VHT60 PAR scope, choose one or more • Addresses coexistence with other systems in the band (5) • Ensure coexistence with IEEE 802.15.3c (1) • Supports mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band (7) • Includes mandatory mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band (11) • Provides mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band (12) • Mandates mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band (7) • SP2 • Should similar coexistence language be added to the 802.15.3c PAR scope? • Yes (17) • No (1) • Abs (2) • updated project dates in 7.1 Eldad Perahia, Intel Corporation

  22. Review of Sept 3 EC call on VHT60 Discussion items New scope wording based on VHT60 straw poll option with most vote “Provides mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band” 802.19 chair was supportive No objections were raised to the wording by EC members on the call Adding symmetrical coexistence wording to 802.15.3c PAR Objection from one member of 802.15 Timeline of 802.15.3c raised as concern If recirculation letter ballot goes well, could go to sponsor ballot in November Definition of coexistence EC suggested including in PAR (common) 802 definition for coexistence Could use 802.15.2 definition, “The ability of one system to perform a task in a given shared environment where other systems have an ability to perform their tasks and may or may not be using the same set of rules.” Reference definition in VHT60 PAR Description of “shared environment” High level definition of shared environment requested Would be used in order to determine whether coexistence was achieved Discussion on level of detail necessary in a PAR/5C’s VHT60 should add description of environment in 5C’s New work items for VHT60 Definition of coexistence Description of environment September 2008 Slide 22 Eldad Perahia, Intel Corporation Eldad Perahia, Intel Corporation

  23. Presentations for Monday Sept 8th 13:30 – 15:30 • Proposed Modifications to VHT60 PAR, 08/998r2, Eldad Perahia Eldad Perahia, Intel Corporation

  24. Minutes for Monday Sept 8th 13:30 – 15:30 Eldad Perahia, Intel Corporation

  25. Backup Eldad Perahia, Intel Corporation

  26. PAR Motion Template • Believing that the PAR and Five Criteria contained in the documents referenced below meet IEEE-SA guidelines, • Request that the updated PAR and Five Criteria contained in 08/806rY be sent to IEEE 802 Executive Committee (EC) for EC approval to submit to NesCom. • Also request that the document <docment-reference> be sent to the IEEE 802 EC as the WG 802.11 responses to comments received on the version of the PAR and 5C previously circulated. • Move: • Second: • Vote Y:, N:, Abs: Eldad Perahia, Intel Corporation

  27. Goals for November • VHT60 • If necessary, • Update VHT60 PAR’s & 5C’s based on feedback from EC and/or NesCom • Complete work on VHT60 PAR & 5 C’s and re-submit motion to WG • Begin TGac (VHTL6) Task Group work Eldad Perahia, Intel Corporation

  28. Conference call times • Continue conference call times: • Weekly on Thursday’s, 11:00 Eastern Time • two hours • Topics: • Joint call with 802.15.3c Eldad Perahia, Intel Corporation

More Related