1 / 41

TGah MAC Ad Hoc Agenda and Report

TGah MAC Ad Hoc Agenda and Report. Authors:. Date: 2012-07-17. Agenda for July 17, 2012 – PM2, San Diego, CA. Designation of a secretary for the minutes Reminder on Affiliation, IEEE Patent review and IP claims policies Reminder to record attendance

tamas
Download Presentation

TGah MAC Ad Hoc Agenda and 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. TGah MAC Ad Hoc Agenda and Report Authors: Date: 2012-07-17 Liu, Shao, Merlin

  2. Agenda for July 17, 2012 – PM2, San Diego, CA • Designation of a secretary for the minutes • Reminder on Affiliation, IEEE Patent review and IP claims policies • Reminder to record attendance • Summary of operating rules for MAC ad hoc group • Submissions • Any more submissions? • Straw polls / Pre-motions Liu, Shao, Merlin

  3. Summary of ad hoc operating rules (1) • The following summary is derived from 11-12/239r2 • Pre-Motion: A pre-motion (doesn’t require voting rights) result of >=75% is required within an Ad Hoc to approve the resolution of all or part of an issue and forward that resolved item to the Taskgroup where it becomes a motion that requires >=75% approval to modify the specification framework or the draft specification. • Note: the term Pre-Motion was introduced by11ac ad hoc operating rules to create a distinction between straw polls which intent is to result in a Motion at the Taskgroup, and strawpolls which intent is to only gauge the opinion of the members on a particular topic and are not intended to results in a motion at the Taskgroup. • Stalemate: In the case a consensus can not be reached within an Ad Hoc group (a stalemate that prohibits further progress), the subject is moved to the Taskgroup if an Ad Hoc straw poll vote to move the subject to the Taskgroup achieves >50% approval. Liu, Shao, Merlin

  4. Summary of ad hoc operating rules (2) • The following summary is derived from 11-12/239r2 • Transfer to another ad hoc: A motion passing with >50% in the Taskgroup shall be sufficient to move an issue previously assigned to an Ad Hoc group to any Ad Hoc group. A straw poll vote of >50% is required in an Ad Hoc group to refuse an issue from the Taskgroup. • Transfer to another ad hoc: An issue may be sent from one Ad Hoc to another if both the sending Ad Hoc and the receiving Ad Hoc approve straw polls for taking the respective actions with >50% approval. A notice should be sent to the reflector indicating the approval of a straw poll to move an issue. • To be accepted into the Draft specification, proposals from Ad Hoc group require a motion that passes with >=75% Taskgroup approval Liu, Shao, Merlin

  5. Submissions Liu, Shao, Merlin

  6. Interpretive guide • Text coloring: • Black = pending agenda item • Red = item partially addressed • Green = item completed • Gray = item not addressed • The following slides include all the MAC submissions as shown in TG agenda 11-12/0879r7 Liu, Shao, Merlin

  7. Submissions • 12/816r0 Channel selection for 802.11ah • Huai-RongShao, et. al. (Samsung Electronics) • 11-12/830r0 NDP Probing • YonghoSeok (LG Electronics) - MAC David Halasz, Motorola Mobility

  8. Submissions • 11-12/831r0 Uplink Channel Access General Procedure • YonghoSeok (LG Electronics) – MAC • 12/ 843 Restricted Access Window Signaling for Uplink Channel Access • (Nokia) • 11-12/840r0 AP assisted medium synchronization • Minyoung Park (Intel) – MAC • 12/409 channel-access-supporting-low-power-operation • Zander Lei (I2R) – MAC • 12/823 Target Wake Time • Matthew Fischer (Broadcom) • 12/834 Speed Frame Exchange • Eric Wong (Broadcom) • 12/867 non-TIM Allocation • Hyoungjin Kwon (ETRI) David Halasz, Motorola Mobility

  9. Submissions • 12/877 11ah-channel-access-enhancement • TimoKoskela (Renesas Mobile Corporation) • 12/860 Collision Reduction • Simone Merlin (Qualcomm) • 12/ 892 Uplink Data Delivery • Betty Zhao (Huawei) • 12/837 slot based power save improvement • Liwen Chu (STMicroelectronics) • 12/343 Enhancement of Low Power Medium Access STAs (withdraw) • Liwen Chu (STMicroelectronics) • 12/696 slot based power save without PS Poll (withdraw) • Liwen Chu (STMicroelectronics) • 12/852 sectorization for hidden node mitigation • George Calcev (Huawei) David Halasz, Motorola Mobility

  10. Submissions • 12/863 Distance Issues • Dave Halasz (Motorola Mobility) – MAC • 12/838 full beacon • Yong Liu (Marvell) – MAC David Halasz, Motorola Mobility

  11. Submissions • 12/ 842 Short Beamforming Report Poll frame • Bo Sun (ZTE Corporation) • 12/845 Max Idle Period Extension • Lin Wang (ZTE Corporation) • 12/ 859 Short BA • Alfred Asterjadhi (Qualcomm) • 12/861 EDCA Parameters for 11ah • AminJafarian (Qualcomm) • 12/857 Short MAC header design • Simone Merlin (Qualcomm) David Halasz, Motorola Mobility

  12. Submissions • 12/ 871 Spectrum access and Tx control for regulatory conformance • Shusaku Shimada(Yokogawa Co.) • 12/872 Time Freq. Measurement Mechanism & Procedure • Shusaku Shimada(Yokogawa Co.) • 12/848 NDP type PS-Poll frame • Young Hoon Kwon (Huawei) • 12/ 890 802.11ah Multi-User Aggregation PDU • Fei Tong (CSR) • 12/869 Active Scanning for 11ah • Jae Seung Lee (ETRI) David Halasz, Motorola Mobility

  13. Submissions • 12/878 on-channel-switching-in-11ah • TimoKoskela (Renesas Mobile Corporation) • 12/891 AID reassignment for TIM and non-TIM modes switching • Betty Zhao (Huawei) • 12/ ??? Channel Access • Fang Xie (CMCC) • 12/835 Responding Frame Selection • Liwen Chu (STMicroelectronics) • 12/881 PS Mode Enhancements with Timing Indication • Anna Pantelidou (Renesas Mobile Corporation) David Halasz, Motorola Mobility

  14. MAC ad hoc Straw Polls Liu, Shao, Merlin

  15. Straw Poll 1 Liu, Shao, Merlin

  16. MAC ad hoc Pre-Motions to be brought for vote in TGahtask group Liu, Shao, Merlin

  17. Pre-Motion 1 (12/0867r0) • Do you support to include, in TGah Spec Framework document, the concept of the following? • AP may indicate to TIM STAs RAW information during which no TIM STA is allowed to contend • Yes: 14 • No: 0 • Abstain: 3 • Passed Liu, Shao, Merlin

  18. Pre-Motion 2 (12/0860r0) • Do you support to add in the specification framework an operation mode for spreading the PS-Poll/trigger frame transmission, that does not require additional beacon info, by defining the following: • Paged STA starts the contention at slot boundary defined as a function of STA position in the TIM IE and additional info determined by Association or Beacon frame. • Yes: 18 • No: 0 • Abstain: 3 • Passed Liu, Shao, Merlin

  19. Pre-Motion 3 (12/0892r0) Do you support that AP may indicate a window in beacon, and during that window offloading STAs can not access medium to send uplink data? Yes: 17 No: 0 Abstain: 6 Passed Liu, Shao, Merlin

  20. Pre-Motion 4 (12/0837r0) • Do you support adding following text to the specification framework document? • A power save STA can indicate if it supports RAW operation to an AP • Yes: 2 • No: 0 • Abstain: 25 • Passed Liu, Shao, Merlin

  21. Pre-Motion 5 (12/0852r0) Do you agree to include in the SFD “The 11ah should support a mode of operation where only a selected group of stations is allowed to transmit during a specified time interval. When a STA finds that belongs to a transmission group it shall transmit only in the time interval reserved for that group and not transmit in the time interval allocated to another group.”? Yes: 33 No: 0 Abstain: 1 Passed Liu, Shao, Merlin

  22. Pre-Motion 6 (12/0852r0) Do you agree to add in SFD “The transmission group may be identified by a group ID and a group definition field that identifies a logical grouping (such as an AID range of addresses) or a physical grouping, for example using an antenna beam pattern.” ? Yes: 30 No: 0 Abstain: 0 Passed Liu, Shao, Merlin

  23. Pre-Motion 7 (12/0852r0) Do you agree to include in the SFD “The transmission group definition field, the time interval reserved for the group transmission and its repetition period or the time till the next transmission may be advertized via (short)beacons, probe response or another management frame TBD.” Yes: 29 No: 0 Abstain: 1 Passed Liu, Shao, Merlin

  24. Motions from MAC ad hoc meeting Liu, Shao, Merlin

  25. Motion 1 (12/0867r0) • Move to include, in TGah Spec Framework document, the concept of the following? • AP may indicate to TIM STAs RAW information during which no TIM STA is allowed to contend • Yes: • No: • Abstain: Liu, Shao, Merlin

  26. Motion 2 (12/0860r0) • Move to add in the specification framework document an operation mode for spreading the PS-Poll/trigger frame transmission, that does not require additional beacon info, by defining the following: • Paged STA starts the contention at slot boundary defined as a function of STA position in the TIM IE and additional info determined by Association or Beacon frame. • Yes: • No: • Abstain: Liu, Shao, Merlin

  27. Motion 3 (12/0892r0) Move to include in the SFD the operation that AP may indicate a window in beacon, and during that window offloading STAs can not access medium to send uplink data? Yes: No: Abstain: Liu, Shao, Merlin

  28. Motion 4 (12/0837r0) • Move to add the following text to the specification framework document? • A power save STA can indicate if it supports RAW operation to an AP • Yes: • No: • Abstain: Liu, Shao, Merlin

  29. Motion 5 (12/0852r0) Move to include in the SFD “The 11ah should support a mode of operation where only a selected group of stations is allowed to transmit during a specified time interval. When a STA finds that belongs to a transmission group it shall transmit only in the time interval reserved for that group and not transmit in the time interval allocated to another group.”? Yes: No: Abstain: Liu, Shao, Merlin

  30. Motion 6 (12/0852r0) Move to add in SFD “The transmission group may be identified by a group ID and a group definition field that identifies a logical grouping (such as an AID range of addresses) or a physical grouping, for example using an antenna beam pattern.” ? Yes: No: Abstain: Liu, Shao, Merlin

  31. Motion 7 (12/0852r0) Move to include in the SFD “The transmission group definition field, the time interval reserved for the group transmission and its repetition period or the time till the next transmission may be advertized via (short)beacons, probe response or another management frame TBD.” Yes: No: Abstain: Liu, Shao, Merlin

  32. References • [1] 11-11-0239-02-00ah-proposed-selection-procedure.docx • [2] 11-11-1137-09-00ah-specification-framework-for-tgah.docx • [3] 11-11-0905-05-00ah-tgah-functional-requirements-and-evaluation-methodology.docx • [4] 12/0602 TGah-Spec-Development-Process (TBD) • [5] 11-10-0001-13-0wng-900mhz-par-and-5c.docx • [6] 11-12-0651-00-00ah-TGah-Sub-Groups.pptx • [7] 11-12-0879-07-00ah-tgah-july-2012-agenda Liu, Shao, Merlin

  33. Appendix - Policies Liu, Shao, Merlin

  34. Instructions for the WG Chair 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. Liu, Shao, Merlin

  35. 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 Liu, Shao, Merlin

  36. Patent Related Links 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 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 Liu, Shao, Merlin

  37. Call for Potentially Essential Patents • 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 Slide #3 Liu, Shao, Merlin

  38. 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 Liu, Shao, Merlin

  39. Member Affiliation • It is defined in the IEEE-SA Standards Board Bylaws, 5.2.1.5 as: “An individual is deemed “affiliated” with any individual or entity that has been, or will be, financially or materially supporting that individual’s participation in a particular IEEE standards activity. This includes, but is not limited to, his or her employer and any individual or entity that has or will have, either directly or indirectly, requested, paid for, or otherwise sponsored his or her participation. • http://standards.ieee.org/faqs/affiliationFAQ.html Liu, Shao, Merlin

  40. Declaration of Affiliation • Revision: May 2007 Standards Board Bylaw 5.2.1.1 • 5.2.1.1 Openness • Openness is defined as the quality of being not restricted to a particular type or category of participants. All meetings involving standards development an all IEEE Sponsor ballots shall be open toa all interested parties. Each individual participant in IEEE Standards activities shall disclose his or her affiliations when requested. A person who knows or reasonably should know, that a participant’s disclosure is materially incomplete or incorrect should report that fact to the Secretary of the IEEE-SA Standards Board and the appropriate Sponsors. • http://standards.ieee.org/faqs/affiliationFAQ.html Liu, Shao, Merlin

  41. Affiliation Policy • Requirement to declare affiliation at all standards development meetings and recorded in the minutes • Affiliation not necessarily same as employer • Declaration requirement may be familiar to some 802 WGs, though WG declaration process may evolve • 11. What if I refuse to disclose my affiliation? • As outlined in IEEE-SA governance documents, you will lose certain rights. In a working group where voting rights are gained through attendance, no attendance credit will be granted if affiliation isn’t declared. Similarly, voting rights are to be removed if affiliation isn’t declared. • Affiliation declaration will be added to Sponsor ballot • http://standards.ieee.org/faqs/affiliationFAQ.html Liu, Shao, Merlin

More Related