Session # GRIDMAN Opening Report IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE gman-10/xxxx Date Submitted: Source: Tim GodfreyVoice: EPRI Chair IEEE GRIDMAN Study Group Venue: IEEE Session #68 Base Contribution: N/A Purpose: Session #68 Opening Report / Agenda for GRIDMAN SG Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who 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 IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s 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: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Further information is located at and. 1

Session #68 GRIDMAN Opening Report July 12,

GRIDMAN Web site PAR ( /0018r2) approved by NESCOM on 18 June Continuing in Study Group mode for this session – voting open to all attendees Call for Contributions for n System Requirements Document (80216GMAN-10/0022) Issued – will close this week Focus for Session #68 will be on developing a draft of the n System Requirements Document (SRD) from the outline in document C80216gman-10/0022C80216gman-10/0022 GRIDMAN Status 3

GRIDMAN AGENDA - Manchester Ballroom G 4 DateTimeDetails Tuesday 13 July :00-18:00 Approve agenda & minutes, review patent slides, attendance, roster Review of C80216gman-10/0022C80216gman-10/0022 Outline of SRD from Session #67 Revisit n integration question: m only, or all of base? Discuss and develop work plan, SRD process Establish order of contribution presentations Contribution presentations Wednesday 14 July :00-10:00 Contribution presentations 10:00-12:00 Joint Session with PPC (M2M) M2M PAR and requirements overlap, schedule alignment 13:00-18:00 Contribution presentations (if needed) Thursday 15 July :00-18:00 Initial drafting of System Requirements Document Review Work Plan, Schedule

Admistrivia Please log your attendance each day – Review of Patent slides –Now using Post-PAR slide set – 5

Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: l “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 l “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 or patent claims l “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) l The above does not apply if the patent claim 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 l Early identification of holders of potential Essential Patent Claims is strongly encouraged l No duty to perform a patent search Slide #1

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 Slide #2 If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit This slide set is available at

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

Other Guidelines for IEEE WG Meetings l All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. l Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. l Don’t discuss specific license rates, terms, or conditions. l Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. l Technical considerations remain primary focus l Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. l Don’t discuss the status or substance of ongoing or threatened litigation. l Don’t be silent if inappropriate topics are discussed … do formally object See IEEE-SA Standards Board Operations Manual, clause 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

Background material GRIDMAN home page – Draft PAR / 5C from ( /0018r2) – -10_0018r2.pdfhttp:// -10_0018r2.pdf Outline of n System Requirements Document – man-10_0022.dochttp:// man-10_0022.doc 10

Contributions for Presentation –C80216gman-10_0023.docC80216gman-10_0023.doc –Text proposal of n System Requirements Document (Section 6.2) | Kyungkyu Kim, Jungje Son, Youngbin Chang | Samsung Electronics Co., Ltd –C80216gman-10_0024.docC80216gman-10_0024.doc –Text proposal to n System Requirements Document Eldad Zeira, Ron Murias | InterDigital –C80216gman-10_0025.docC80216gman-10_0025.doc –Security considerations for mobile to mobile direct communications | Eldad Zeira, Alex Reznik| InterDigital –C80216gman-10_0026.docC80216gman-10_0026.doc –Proposed texts of n System Requirements Sungcheol Chang, Sungkyung Kim, Hyun Lee, Jaesun Cha, Chulsik Yoon| ETRI –C80216gman-10_0027.docC80216gman-10_0027.doc –Text proposal to n System Requirement Document (Section 6.1) | Anseok Lee, Wooram Shin, Hyun Jae Kim, Kwang Jae Lim | ETRI –C80216gman-10_0028.pdfC80216gman-10_0028.pdf –Proposed changes to n SRD| Youngbin Chang, Rakesh Taori and Jungje Son| Samsung 11

Revisit: Applicability of n amendment on base standard Should the n amendment be written to modify all Clauses of the base standard? –The m amendment has been written with separate PHY and MAC clauses. (section 16) –To modify all functionality of as well as TGm we will have to make changes in two places. Straw Poll from Session #67 –Option 1: Make changes for j (2009 as amended by 16j) and 16m: 5 votes –Option 2: Make changes for 16m only (benefits of 16n only apply to 16m): 7 votes Is a hybrid possible? For example some capabilities such as mobile to mobile could be 16m only, but others apply to both.

Draft TG Timetable Start of TG, Start SRD July 2010 Approved SRD Sept 2010 CFP issued Sept 2010 System Design DocJan 2011 Interim Doc July 2011 WG LB issued Sept 2011 Recirc 1 Nov 2011 Recirc 2 Jan 2012 Sponsor Mar 2012 Approved Std Nov 2012