360 likes | 548 Views
IEEE 802.11ah Sub 1 GHz license-exempt operation Agenda for July 2013. Date: 2013-7-15. Authors:. Call for a secretary IPR and other relevant policy and procedures Approve meeting minutes May meeting minutes 13/0622r01 May-2013-f2f-meeting-minutes
E N D
IEEE 802.11ahSub 1 GHz license-exempt operation Agenda for July 2013 Date: 2013-7-15 Authors: David Halasz (Qualcomm)
Call for a secretary • IPR and other relevant policy and procedures • Approve meeting minutes • May meeting minutes • 13/0622r01 May-2013-f2f-meeting-minutes • June 19th and July 10th conference call minutes • 13/707 June 19th TGah teleconference minutes, r1 on server • 13/763 July 10th TGah teleconference minutes, r1 on server • Postponed until Tuesday to update attendance list • Operations Manual (document 11-13-0001) section 3.8 review – 4 hour rule review • Prepare for Letter Ballot • Call for submissions to address Call for comments • 13/701 review • Call for submissions IEEE 802.11ah Agenda David Halasz (Qualcomm)
13/701 comments review Summary: David Halasz (Qualcomm)
Serial ad hocs instead of concurrent ad hocs • Draft 0.x Ad Hoc Chairs • MAC ad-hoc Chair Simone Merlin • PHY ad-hoc Chair Minho Cheong • Database administrators • Minyoung Park - GEN & EDITOR • YonghoSeok - MAC • Dave Halasz - PHY IEEE 802.11ah Agenda David Halasz (Qualcomm)
Monday PM • Full TG - Agenda, initial motions for approving agenda & minutes • MAC ad hoc • Tuesday PM 2 • PHY ad hoc • Time permitting, MAC ad hoc • Wednesday AM 1 • Full TG - Motions • MAC ad hoc • Wednesday PM 1 & PM 2 • MAC ad hoc • Thursday AM 1 & AM 2 • PHY ad hoc • Time permitting, MAC ad hoc • Thursday PM 1 • Full TG - Motions IEEE 802.11ah AgendaMAC/PHY & full TG meeting slots David Halasz (Qualcomm)
Motion for specification framework doc Motion for draft text Conference call plan Timeline review IEEE 802.11ah Agenda David Halasz (Qualcomm)
MAC, YonghoSeok • 11-13-0769-00-00ah-CC9-clause-10-1-4-3-4-and-8-3-4a-2-1-comment-resolution11-13-0770-00-00ah-CC9-clause-10-43b-and-8-4-2-170d-comment-resolution11-13-0771-00-00ah-CC9-cluase-9-3-2-8-comment-resolution11-13-0772-00-00ah-CC9-cluase-9-3-6-and-9-32n-comment-resolution11-13-0773-00-00ah-CC9-cluase-9-7-6-6-and-9-19-2-4-comment-resolution11-13-0774-00-00ah-CC9-cluase-9-17b-comment-resolution11-13-0775-00-00ah-CC9-cluase-9-19-2-7-comment-resolution11-13-0776-00-00ah-CC9-cluase-9-19-4a-1-comment-resolution11-13-0777-00-00ah-CC9-cluase-9-19-4a-2-comment-resolution11-13-0778-00-00ah-CC9-cluase-9-19-4a-5-comment-resolution11-13-0779-00-00ah-CC9-EDCA-channel-access-comment-resolution11-13-0780-00-00ah-CC9-miscellaneous-comment-resolution11-13-0781-00-00ah-CC9-probe-resp-bandwidth-selection-comment-resolution11-13-0782-00-00ah-CC9-SST-sounding-comment-resolution Submissions David Halasz (Qualcomm)
MAC, Minyoung Park • Comment resolutions on subclause 9.32h • 11-13-0783-00-00ah • CIDs 58, 107, 916, 917 • Comment resolution on subclause 9.19.4a.3 • 11-13-0784-00-00ah • CIDs 123, 366, 966, 967 • Comment resolution on subclause 10.3.7 • 11-13-0785-00-00ah • CID 186, 482 Submissions cont. David Halasz (Qualcomm)
MAC, Mitsuru Iwaoka • 11/13-0793 CC9 Comment Resolutions for CID 395,396,399,400,524,525,529,547,624 • For MAC comments of CID 395,396,399,400,524,525,529,547 and 624 • The resolution of CID 547 may depend on CID 74 and 562, and need some days to upload. Submissions cont. David Halasz (Qualcomm)
MAC, Hongyuan Zhang • 11-13-0716-00-00ah-d01-MIMO-Control-Field-comment-resolutions • For MAC CIDs 106, 359, 830—i.e. for 8.4.1.47. Submissions cont. David Halasz (Qualcomm)
MAC, Younghoon Kwon • Doc. Number: 808 • Title: cc09 comment resolution for clause 8.3.4a.1.2 • Addressing CIDs: 104, 223, 899 (MAC) • Doc. Number: 809 • Title: cc09 comment resolution for clause 9.19.4a.6 • Addressing CIDs: 52, 557, 788 (MAC) • Doc. Number: 810 • Title: cc09 comment resolution for clause 9.32n.3.2 • Addressing CIDs: 513, 514, 714, 715 (MAC) • Doc. Number: 811 • Title: cc09 comment resolution for CID 520 • Addressing CID: 520 (MAC) Submissions cont. David Halasz (Qualcomm)
MAC, Wang Haiguang • CC9-Comments-Resolution-CIDs-546+906 • IEEE-802.11-13/0827r0 • CIDs 546, 906 • CC9-Comments-Resolution-CIDs-176+177+178+179+180+181+776 • IEEE-802.11-13/0830r0 • CIDs 176, 177, 178, 179, 180, 181, 776 • CC9-Comments-Resolution-CIDs-887 • IEEE-802.11-13/0831r0 • CIDs 887 Submissions cont. David Halasz (Qualcomm)
MAC, Alfred Asterjadhi 11-13-0812-00-00ah-CC9-Resolution-CIDs-8+10+17+19+321+581 11-13-0814-00-00ah-CC9-Resolution-CIDs-14+253+484+485+486 11-13-0815-00-00ah-CC9-Resolution-CIDs-15+59+168 11-13-0816-00-00ah-CC9-Resolution-CIDs-18+119+360+532+533+660+661+662+869 11-13-0817-00-00ah-CC9-Resolution-CIDs-20+111+336+625+814 11-13-0818-00-00ah-CC9-Resolution-CIDs-23+275+276+277+278 11-13-0820-00-00ah-CC9-Resolution-CIDs-32+54+187+188+240+417+543+821 11-13-0821-00-00ah-CC9-Resolution-CIDs-254+303+304+305+324+363+364+745+841+961+962+985 11-13-0822-00-00ah-CC9-Resolution-CIDs-746+747+748+924 11-13-0823-00-00ah-CC9-Resolution-CIDs-74+562+914+915 11-13-898-00-00ah-ACK_Policy_for_Short_MAC_Header, No CID submission 11-13-0824-00-00ah-CC9-Resolution-CIDs-12+560+561+563 11-13-0825-00-00ah-CC9-Resolution-CIDs-27 Submissions cont. David Halasz (Qualcomm)
MAC, Yuan Zhou • DCN 0832- CC9-Comments-Resolution-CID-927 • DCN 0833- CC9-Comments-Resolution-CIDs-85+460+928 • DCN-0834- CC9-Comments-Resolution-CIDs-473+474 Submissions cont. David Halasz (Qualcomm)
MAC, ChittabrataGhosh • 11-13-0813-00-00ah-cc09-comment-resolution-for-clause-8-4-2-170b.docs • Defer • 11-13-0819-00-00ah-cc09-comment-resolution-for-clause-9-32j.docx • 11-13-XXXX-00-00ah-cc09-comment-resolution-for-clause-CIDs169-170.docx Submissions cont. David Halasz (Qualcomm)
MAC, Ron Murias • 13/0848 "CC9 Comment resolution for MAC CIDs related to Grouping" • Addresses 98, 618, 619, 897, 929 MAC related CIDs Submissions cont. David Halasz (Qualcomm)
MAC, Jeongki Kim • 11-13-0838-00-00ah-cc9-comment-resolution-for-CID224 • 11-13-0839-00-00ah-cc9-comment-resolution-for-CID143-144-245 Submissions cont. David Halasz (Qualcomm)
MAC, Jinsoo Choi • 13/0851 CC9-subclause-8-3-4-15b-comment-resolution • CID 149, 246, 404 • 13/0857 CC9-subclause-8-4-1-6-comment-resolution • CID 80, 405, 406, 959 Submissions cont. David Halasz (Qualcomm)
MAC a. Comment resolutions on subclause 9.32g.3 (uploaded) 11-13-0887-00-00ah CIDs 36,38, 39, 40, 63, 968 b. Comment resolution on subclause 9.32g.4 (uploaded) 11-13-0888-00-00ah CIDs 257,258,988 c. Comment resolution on subclause 8.2.4.1.3 (uploaded) 11-13-0889-00-00ah CID 93 d. Comment resolution on subclause 9.32n.3 and 9.32n.3.1 (not uploaded yet) 11-13-0891-00-00ah CID 749,750, 751, 981,982,983,984, 261,262 and 263 (these three CIDs are handled by Kaiying but may be combined) Haiguang will presented since Shou Kang is not here. Submissions cont. David Halasz (Qualcomm)
Submissions cont. David Halasz (Qualcomm)
PHY, Mitsuru Iwaoka • 11/13-0668 Proposedresolutions for P802.11ah D0.1 CC9 • For PHY comments of CID 555, 570, 576 • The resolution of CID 555 and 576 may depend on CID 817 and 863, and need some days to upload. Submissions cont. David Halasz (Qualcomm)
PHY Eugene Baik • 13/767 • Draft0.1 comment res. for 24.3.17 • Doc 767 resolves CIDs: 302, 801, 802, 803, 804, 805, 806, 566 • 13/766 • Draft0.1 comment res. for 24.3.8 • Doc 766 resolves CIDs: 145, 190, 270, 271, 272, 273, 298, 299, 872, 873, 880 Submissions cont. David Halasz (Qualcomm)
PHY, Hongyuan Zhang • 11-13-0715-00-00ah-d01-PHY-comment-resolutions • For PHY, CIDs in 24.1, 24.3.3, 24.3.6~24.3.11, 24.3.18 Submissions cont. David Halasz (Qualcomm)
Ron Murias • 13/0846 "CC9 Comment resolution for CIDs 203, 211, 622, 925“ • 622 pass to editor • Other CIDs addressed by 13/715 Submissions cont. David Halasz (Qualcomm)
PHY, 13/0826r0, “CC9-PHY-comment-resolutions-24.4-CID549+871” • Bo Sun (ZTE) Submissions cont. David Halasz (Qualcomm)
PHY, Eugene Baik (Qualcomm) • https://mentor.ieee.org/802.11/dcn/13/11-13-0766-02-00ah-draft0-1-comment-res-for-24-3-8.docx • PHY, Hongyuan Zhang (Marvell) • 13/901 d01 PHY comment 141 • PHY, Bo Sun (ZTE Corp.) • https://mentor.ieee.org/802.11/dcn/13/11-13-0881-00-00ah-cc9-gen-comment-resolutions-cid729-568.docx • PHY, Shahrnaz (Intel) • 13/905 draft0-1-comment-res-for-24.3.19 and 20 • PHY, Shusaku Shimada • CID 800 clarification discussion Submissions cont. David Halasz (Qualcomm)
Submissions cont. David Halasz (Qualcomm)
Motions to address CIDs • 13/915 PHY motions 2013-07-18 • For submissions 13/901r0, 13/766r2 & 13/905r2 • Motion to address CID 800 from Shusaku? • MAC motions • Motion for update to Specification Framework Document • Motion for update to draft text Task group document motions David Halasz (Qualcomm)
Desire to have rolling time of noon, 10 AM and 7 PM • Next at 7PM • Desire weekly calls • July 31, 7 PM • Aug 7, 10 AM • Aug 14, 7 PM • Aug 21, 10 AM • Aug 28, 7 PM • Sept 4, 10 AM • Sept 11, 7 PM – Prepare for face to face meeting Agenda cont.Teleconferences David Halasz (Qualcomm)
July review • 8 meeting slots and no parallel meetings • 988 comments and X addressed in July • September suggested request (not guaranteed) • 8 Total • Monday 1 Full TG slot • Tuesday 3 double ad-hoc slots • Wednesday 1 Full TG slot & 1 double ad-hoc slot • Thursday 1 double ad-hoc slot in AM & 1 Full TG slot in PM Meeting slot requests for September David Halasz (Qualcomm)
Review 11/285 • Go to Letter Ballot at end of September meeting is next goal Timeline David Halasz (Qualcomm)
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. David Halasz (Qualcomm) (Optional to be shown)
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 David Halasz (Qualcomm)
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 David Halasz (Qualcomm)
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 David Halasz (Qualcomm)
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 David Halasz (Qualcomm)