Submission doc.: IEEE /1466r0 NGP TGaz Jan. Agenda Date: Slide 1Jonathan Segev, Intel Corporation Dec Authors:

Submission doc.: IEEE /1466r0 IEEE Task Group az Next Generation Positioning Dallas, Texas Nov. 8 th -13 th, 2015 Chair: Jonathan Segev (Intel) Vice-chair: Carlos Aldana (Qualcomm) Secretary: Zhou Lan Slide 2Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Abstract This presentation contains the IEEE TGaz NGP (Next Generation Positioning) agenda for the Jan. meeting. Slide 3Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Attendance, Voting & Document Status Make sure your badges are correct Please announce your affiliation when you first address the group during a meeting slot If you plan to make a submission be sure it does not contain company logos or advertising Questions on Voting status, Ballot pool, Access to Reflector, Documentation, member’s area  see Jon Rosdahl – Cell Phones Silent or Off Slide 4Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Logistics Attendance: You must register before logging attendance. You must log attendance during each 2 hour session. Documentation Use “TGaz” folder for documents relating to the TGaz activity. Note: Per WG leadership guidance, attendance count at the midpoint of each timeslot will be conducted during each TG meeting slot. Slide 5Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 September 2015 Slide 6 Patent Policy Following 5 slides Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 September 2015 Slide 7 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 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 and in FAQs 14 and 15 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. Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 September 2015 Slide 8 Participants, Patents, and Duty to Inform Slide #1 All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]: “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 “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of 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 patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 September 2015 Slide 9 Patent Related Links Slide #2 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 Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 September 2015 Slide 10 Call for Potentially Essential Patents Slide #3 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 Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 September 2015 Slide 11 Other Guidelines for IEEE WG Meetings Slide #4 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 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Jonathan Segev, Intel Corporation

Submission doc.: IEEE /1466r0 TGaz - Schedule in a Glance Slide 12Jonathan Segev, Intel Corporation Dec MONTUEWEDTHUFRI AM1 AM2 PM1NGP PM2NGP Eve

Submission doc.: IEEE /1466r0 Agenda Items for the Week Patent policy Approve previous meeting minutes (11-15/1470).11-15/1470 Election for TG leadership – FRD editor, technical editor. Review TG development process and documentation status Presentations to inform the TG: Completion of use case document development. Initiation of Functional Requirements Document. Schedule teleconference times as needed. Slide 13Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Submission List for the week Slide 14Jonathan Segev, Intel Corporation Dec Document No.PresenterTitleTopic Jonathan SegevNGP Nov AgendaAgenda Deck Zhou LanSep. meeting minutes approvalMeeting minutes Santosh PandeyUse case documentUse case

Submission doc.: IEEE /1466r0 Meeting Slot #1 Slide 15Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Meeting Slot # 1 Agenda Call Meeting to Order (1min) Patent Policy and Logistics (5min) Last call for Submission (0min) Agenda Setting (4min) Approval of previous meeting minutes (3min - Chair) Presentation to inform TG. Slide 16Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Submission order – Slot 1 Slide 17Jonathan Segev, Intel Corporation Dec Document No.PresenterTitleTopic 11-15/1237Jonathan SegevNext Gen. PositioningAgenda Deck Zhou LanNov. meeting minutes approvalMeeting minutes

Submission doc.: IEEE /1466r0 Approval of previous meeting minutes Document 11-15/1470r1 posted to Mentor Nov. 13 th. Motion: To approve document 11-15/1470r0 as TG meeting minutes for the Dallas meeting. Moved by: Seconded by: Results (Y/N/A): Unanimous consent Slide 18Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Presentations Slide 19Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Attendance reminder Slide 20Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Recess Slide 21Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Meeting Slot #2 Slide 22Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Meeting Slot # 2 Agenda Call Meeting to Order (1min) Patent Policy and Logistics (5min) Agenda Setting (4min) Presentations to inform the TG (55min) Slide 23Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Submission order – Slot 2 Slide 24Jonathan Segev, Intel Corporation Dec Document No.PresenterTitleTopic 11-15/1003Jonathan SegevNext Gen. PositioningAgenda Deck

Submission doc.: IEEE /1466r0 Motion – approve UC document Motion We adopt document xxxx as use case document for TGaz specification development. Move: 2 nd : Y: N: 0 A: 5 Slide 25Jonathan Segev (Intel) July 2015

Submission doc.: IEEE /1466r0 Review TGaz Timeline progress Slide 26Jonathan Segev, Intel Corporation Dec az Draft 2.0 (Mar 2018).11az Final (Mar ) PAR Approved (Sep. 2015).11az Draft 1.0 (Sep. 2017) NGP SG Launch (Jan. 2015) Func. Req. Doc. (Nov 15 - May 16) 11az SFD TG formation meeting (Sep. 2015) We are here UCD Amendment text FRD Spec Frame work (May 16 – Mar. 17) Amendment text (Mar 17 – Mar. 20) UC doc. (May 15 – Nov. 17)

Submission doc.: IEEE /1466r0 Goals for the March meeting Continue on Functional Requirement Document development. Technical presentations. Slide 27Jonathan Segev, Intel Corporation Sep. 2015

Submission doc.: IEEE /1466r0 Teleconference Schedule Dec. 3 rd 10:00 ET for 1hr. Do we need anymore calls? Slide 28Jonathan Segev, Intel Corporation Sep. 2015

Submission doc.: IEEE /1466r0 Reminder to do attendance Slide 29Jonathan Segev, Intel Corporation Sep. 2015

Submission doc.: IEEE /1466r0 Recess Slide 30Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Meeting Slot # 3 Agenda Call Meeting to Order (1min) Patent Policy and Logistics (5min) Agenda Setting (4min) Presentations. Slide 31Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Submission order – Slot #3 Slide 32Jonathan Segev, Intel Corporation Dec Document No.PresenterTitleTopic 11-15/1003Jonathan SegevNext Gen. PositioningAgenda Deck

Submission doc.: IEEE /1466r0 AOB? Slide 33Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Attendance remainder Slide 34Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Adjourned Slide 35Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Backup Slide 36Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Historical timelines data Slide 37Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Historical performance data Slide 38Jonathan Segev, Intel Corporation Dec StageDuration 11v11u 11ac [1]11ad [1]Proposed for 11az PAR approval -> Approved Standard 64 months46 months PAR approval -> Draft months21 months PAR approval -> D months17 months D0.1 –> Draft months4 months Draft 1.0 –> Draft months6 months Draft 2.0 -> Final 22 months19 months Amendment size 442 pg.679 pg.

Submission doc.: IEEE /1466r0 Timelines Slide 39Jonathan Segev, Intel Corporation Dec ax Draft 2.0 (Mar 2017).11az Final PAR Approved (Sep. 2015).11az Draft 1.0 (Sep. 2017) NGP SG Launch (Jan. 2015) Func. Req. Doc. (Nov 15 - May 16) 11az SFD TG formation meeting (Sep. 2015) We are here UCD Amendment text FRD Spec Frame work (May 16 – Mac. 17) Spec Frame work (Mar 17 – Jan. 19) UC doc. (May 15 – Nov. 17)

Submission doc.: IEEE /1466r0 Slide 40Jonathan Segev, Intel Corporation Dec ax Draft 2.0 (Mar 2017).11az Final PAR Approved (Sep. 2015).11az Draft 1.0 (Sep. 2017) NGP SG Launch (Jan. 2015) Functional Req. Document (Nov 15 - May 16) 11az SFD TG formation meeting (Sep. 2015) We are here UCD Amendment text FRD Spec Frame work (May 16 – Mac. 17) Spec Frame work (Mar 17 – Jan. 19)

Submission doc.: IEEE /1466r0 Motions and strawpolls as needed Motion/strawpoll To instruct the use case document editor to add use cases depicted by slides x y z of submission abc to the use case working draft document. Move: 2 nd : Y: N: A: Slide 41Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Strawpoll#1 We support the addition of use cases depicted by slides a,b,c of submission 11-15/XYZrN to the use case working draft document. Y: N: A: Slide 42Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Motions on submission xxx Motion To instruct the use case document editor to add use cases depicted by slides a,b of submission 11-15/XYZrN to the use case working draft document. Move: 2 nd : Y: N: A: Slide 43Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r0 Strawpoll#1 submission 634 Slide 44Jonathan Segev, Intel Corporation Dec We support the addition of use cases depicted by slides a,b,c of submission 11-15/XYZrN to the use case working draft document. Y: N: A:

Submission doc.: IEEE /1466r Template Instructions 1/4 To properly identify your PowerPoint presentation as an IEEE Submission there are 7 steps that you must complete, and 12 data fields that you must fill in. –Step 1. Obtain a document number (has the form yy/xxxx). –Step 2. Title slide: Fill in the presentation subject title text, the full date (in ISO 8601 format of YYYY-MM-DD), and the complete author(s) details (a total of 3 data fields). –Step 3. Abstract slide: Fill in the abstract text. –Step 4. Press “Office” button, Prepare / Properties. Fill in the 2 data fields: Author field = first author's name Title field = Title of presentation Slide 45Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r Template Instructions 2/4 –Step 5. Menu select View, Master, Slide Master, select the top master page (theme slide master). Place the document designator in the right hand side of the header. Document designator example "doc.: IEEE /9876r0", or "doc.: IEEE /9876r2" –Step 6. Menu select Insert, Header and Footer (5 data fields): Slide tab: –Date & Time, Fixed = venue date (as Sep. 2015, e.g. January 2005) –Footer = first author, company Notes tab: –Data and time, Fixed = venue date (as Sep. 2015, e.g. January 2005) –Header = document designator (e.g. “doc.: IEEE /9876r0”) –Footer = first author, company Click "Apply to all". –Step 7. Delete the four template instruction slides. Slide 46Jonathan Segev, Intel Corporation Dec. 2015

Submission doc.: IEEE /1466r Template Instructions 3/4 PowerPoint Submission Preparation Summary: –Things to do:7 –Fields to fill in:12 Slide 47Jonathan Segev, Intel Corporation Nov. 2015

Submission doc.: IEEE /1466r Template Instructions 4/4 Recommendations –a) Always create a new presentation using the template, rather than using someone else's presentation. –b) For quick and easy creation of new submissions, place the template files in the template folder area on your computer. Typical locations are: c:\Program Files\Microsoft Office\Templates\802.11, or c:\Documents and Settings\User Name\Application Data\Microsoft\Templates\ –To create a new submission from within PowerPoint, menu select File, New, then select the appropriate template file. –c) When you update or revise your presentation, remember to check all 6 fields in steps 5 and 6 for the correct values. –rev: Slide 48Jonathan Segev, Intel Corporation Nov. 2015

Submission doc.: IEEE /1466r0 [begin placing presentation body text here] Slide 49Jonathan Segev, Intel Corporation Nov. 2015

Submission doc.: IEEE /1466r0 Slide 50Jonathan Segev, Intel Corporation Nov. 2015