Tgah mac ad hoc agenda and report
1 / 41

TGah MAC Ad Hoc Agenda and Report - PowerPoint PPT Presentation

  • Uploaded on

TGah MAC Ad Hoc Agenda and Report. Authors:. Date: 2013-16-09. Agenda for July 2013 –Geneva, CH . Call the meeting to order. Designation of a secretary for the minutes. Reminder on Affiliation, IEEE 802 and IEEE 802.11 IPR policies and procedures; call for awareness.

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

PowerPoint Slideshow about 'TGah MAC Ad Hoc Agenda and Report' - kyria

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
Tgah mac ad hoc agenda and report
TGah MAC Ad Hoc Agenda and Report


Date: 2013-16-09

Merlin, Liu, Shao

Tgah mac ad hoc agenda and report

Agenda for July 2013 –Geneva, CH

  • Call the meeting to order.

  • Designation of a secretary for the minutes.

  • Reminder on Affiliation, IEEE 802 and IEEE 802.11 IPR policies and procedures; call for awareness.

  • Reminder to record attendance.

  • Proposed agenda:

    • Reminder of the Ad-hoc operating rules

    • Call for submissions for comment resolution

    • Call for submissions other than for comment resolution

    • Address submissions for comment resolution

    • Address submissions not for comment resolution

  • Adjourn

Merlin, Liu, Shao

Submissions and notes

Submissions and notes

Merlin, Liu, Shao

Interpretive guide
Interpretive guide

  • Text coloring:

    • Black = pending agenda item

    • Red = item partially addressed

    • Green = item completed

    • Gray = item not addressed in the session indicated at the top of the slide

Merlin, Liu, Shao


  • 13/1027 CC9-Resolution-CID 3

    • Alfred Asterjadhi (Qualcomm Inc.)

    • No objection. Motion on Wednesday.

  • 13/1062 CIDs for Speed Frame Exchange

    • Alfred Asterjadhi (Qualcomm Inc.)

    • No objection. Motion on Wednesday.

  • 13/1064 CC9-Resolution-CIDs 808+838+839+840

    • Alfred Asterjadhi(Qualcomm Inc.)

    • No objection. Motion on Wednesday 13/1064r1

  • 13/1106 CC9-Resolution-CIDs 112+497+544+545+550+605+606+628+657+846+858

    • Alfred Asterjadhi (Qualcomm Inc.)

    • No objection. Motion on Wednesday 13/1106r1

David Halasz (Qualcomm)

Submissions cont
Submissions cont.

  • 13/1033 CIDs 835,836,687,686,779,781,131

    • George Calcev (Huawei)

    • Small edits.

    • No objection. Will have motion on 13/1033r1 on Wednesday.

David Halasz (Qualcomm)

Submissions cont1
Submissions cont.

  • YonghoSeok (LG Electronics)

    • 13/1048 clause-9-19-4a-4-comment-resolution

      • No Objection. Motion on Wednesday

    • 11-13-1084-00-00ah-CC9-clause-10-43d-comment-resolution

      • No objection. Motion on Wednesday

    • 11-13-1085-00-00ah-CC9-clause-8_4_2_170k-comment-resolution

      • No objection. Motion on Wednesday.

    • 11-13-1086-00-00ah-CC9-CID-813-816-825-826-886-comment-resolution

      • Will add more detail on rejection.

      • No objection. Motion on Wednesday to 13/1086r1

    • 11-13-1087-00-00ah-CC9-miscellaneous-comment-resolution

David Halasz (Qualcomm)

Submissions cont2
Submissions cont.

  • 13/828 MAC-CID 163

    • Bo Sun (ZTE Corp.)

    • No objection. Motion on Wednesday

  • 13/881 CC9-GEN-comment-resolutions-CID729+568

    • Bo Sun (ZTE Corp.)

    • Edits for rejection reasons will come in.

    • No objection. Motion on Wednesday on 13/881r2

  • 13/891 CC9-clause-9-32n-3-1-comment resolution

    • KaiyingLv(ZTE Corp.)

David Halasz (Qualcomm)

Submissions cont3
Submissions cont.

  • 13/1068 CC09 Comment Resolution CID 265

    • Betty Zhao (Huawei)

  • 13/1069 CID 265, 534, 535, 716 and 834

    • Betty Zhao (Huawei)

David Halasz (Qualcomm)

Submissions cont4
Submissions cont.

  • James Wang (MediaTek)

    • 11-13-1098-00-00ah CC9 Resolution of CID201 and 202

    • 11-13-1099-00-00ah CC9 Comment Resolution CID 685, 688-694

    • 11-13-1101-00-00ah-CC9-Comment Resolution-CID 214-216-221-260-679-680-824

    • 11-13-1102-00-00ah-CC9-Comment-Resolution-CID-335-760-761-762

    • 11-13-1103-00-00ah-CC9-Comment-Resolution-CID-213-220

    • 11-13-1104-00-00ah-CC9-Comment-Resolution-CID-780-782-to-787

David Halasz (Qualcomm)

Submissions cont5
Submissions cont.

  • Minho Cheong, MAC submissions to be presented on Wed.

    • 13/1120 cc9-mac-comment-resolutions-on-sectorization

    • CIDs428-429-434 withdrawn via Minho

  • Minho Cheong, PHY submissions

    • 13/1049 cc9-phy-comment-resolutions-24.2.2-24.2.3

    • 13/1050 cc9-phy-comment-resolutions-24.3.4

    • 13/1118 cc9-phy-comment-resolutions-Annex-E

David Halasz (Qualcomm)

Submissions cont6
Submissions cont.

  • 13/984 d01 PHY CID70

    • Hongyuan Zhang (Marvell)

David Halasz (Qualcomm)

Submissions cont7
Submissions cont.

  • 13/1072 Resolutions on BSS Max Idle Period

    • Lin Wang(ZTE Corporation)

David Halasz (Qualcomm)

Submissions cont8
Submissions cont.

  • 13/1026r0 CC9 Comment resolution for CIDs 657, 659

    • Ron Murias (InterDigital)

  • 13/1025r0 CC9 Comment resolution for CIDs 628, 629

    • Ron Murias (InterDigital)

  • 13/1024r0 CC9 Comment Resolution for CIDs 617, 620, 758, 759, 933

    • Ron Murias (InterDigital)

  • 13/1023r0 CC9 Comment Resolution for CID 604

    • Ron Murias (InterDigital)

David Halasz (Qualcomm)

Submissions cont9
Submissions cont.

  • 11-13-1035-00-00ah-cc9-possible-integration-regarding-cid773&774

    • Shusaku Shimada (Schubiquist Technologies Guild)

  • 11-13-1082-00-00ah-cc9-combination-analysis-with-Direct-Link-regarding-cid807

    • Shusaku Shimada (Schubiquist Technologies Guild)

David Halasz (Qualcomm)

Submissions cont10
Submissions cont.

  • 11-13-1034-00-00ah-cc9-cids-31 and 592-comment-resolutions

    • Peter Loc (Huawei)

David Halasz (Qualcomm)

Submissions cont11
Submissions cont.

  • Yuan Zhou (I2R)

    • 11-13-1093-00-00ah-CC9-Comment-Resolution-CID-86

    • 11-13-1094-00-00ah-CC9-Comment-Resolution-CID-362

    • 11-13-1095-00-00ah-CC9-Comment-Resolution-CID-717

    • 11-13-1096-00-00ah-CC9-Comment-Resolution-CID-471

David Halasz (Qualcomm)

Submissions cont12
Submissions cont.

  • 13/1124 CC9-Resolution-CIDs-856

    • Shoukang Zheng (I2R)

David Halasz (Qualcomm)

Submissions cont13
Submissions cont.

  • 13/1067 CC9 resolution of CID 219 317

    • Liwen Chu (STMicroelectronics)

  • Withdraw the following comments: 312, 318, 319, 320, 322, 325

    • Liwen Chu (STMicroelectronics)

David Halasz (Qualcomm)

Submissions cont14
Submissions cont.

  • 13/1088 coexistence assurance

    • YonghoSeok (LG Electronics)

David Halasz (Qualcomm)

Submissions cont15
Submissions cont.

  • 13/1134 Resolutions to CIDs 41, 150, 350, and 898

    • ChittabrataGhosh (Nokia)

David Halasz (Qualcomm)

Submissions cont16
Submissions cont.

  • 13/1138, Comment resolution for annexDCID730 (PHY)

    • Jianhan Liu (Mediatek)

  • 13/1136, Comment resolution for clause-8-4-2-170a CID418 and CID903 (PHY)

    • Jianhan Liu (Mediatek Inc.)

David Halasz (Qualcomm)

Submissions cont17
Submissions cont.

  • Amin Jafarian (Qualcomm)

    • 13/1141 CC9-Resolution-CIDs-831+542

    • 13/1140 CC9-Resolution-CIDs-499+

    • 13/1139 CC9-Resolution-CIDs-323+266+416+431+430+91+794+16+517+697+698+795+699

    • 13/0981 CC9-Resolution-CIDs-68+445+676+446+447+35+232+674+449+450+451

    • 13/0975 CC9-Resolution-CIDs-393+632+631

David Halasz (Qualcomm)

Submissions cont18
Submissions cont.

  • Matthew Fischer MAC submissions

    • 11-13-1145-00-00ah-CC9-resolutions-for-8_4_2_170j-4_11c_d

    • 11-13-1142-00-00ah-CC9-resolutions-for-9_32k

    • 11-13-1143-00-00ah-CC9-resolutions-for-9_32f

David Halasz (Qualcomm)

Submissions cont19
Submissions cont.

  • 13/1127 CCA channelization and levels

    • Eugene Baik (Qualcomm)

David Halasz (Qualcomm)

Mac ad hoc straw polls

MAC ad hoc Straw Polls

Merlin, Liu, Shao

Straw poll 1
Straw Poll 1

Template - Text




(Session: AM/PM N)

Merlin, Liu, Shao

Mac ad hoc pre motions to be brought for vote in tgah task group

MAC ad hoc Pre-Motions to be brought for vote in TGahtask group

Merlin, Liu, Shao

Pre motion 1
Pre-Motion 1

  • Do you agree with

  • (Session:)

Merlin, Liu, Shao


  • [1] 11-11-0239-02-00ah-proposed-selection-procedure.docx

  • [2] 11-11-1137-06-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] 12/591r8 TGah Agenda, May 2012

    • [8] 12/672r0 PHY ad hoc Agenda

Merlin, Liu, Shao




Merlin, Liu, Shao

Instructions for the wg chair
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.

Merlin, Liu, Shao

Participants patents and duty to inform
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

    Merlin, Liu, Shao

    Patent related links
    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

    IEEE-SA Standards Board Operations Manual

    Material about the patent policy is available at

    If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit

    This slide set is available at

    Slide #2

    Merlin, Liu, Shao

    Call for potentially essential patents
    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

    Merlin, Liu, Shao

    Other guidelines for ieee wg meetings
    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

    Merlin, Liu, Shao

    Member affiliation
    Member Affiliation

    • It is defined in the IEEE-SA Standards Board Bylaws, 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.


    Merlin, Liu, Shao

    Declaration of affiliation
    Declaration of Affiliation

    • Revision: May 2007 Standards Board Bylaw

      • 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.


    Merlin, Liu, Shao

    Affiliation policy
    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


    Merlin, Liu, Shao

    Review of ad hoc operating rules
    Review of ad hoc operating rules

    • 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.

    Merlin, Liu, Shao

    Review of ad hoc operating rules1
    Review of ad hoc operating rules

    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

    Merlin, Liu, Shao