Date post: | 18-Jan-2018 |
Category: |
Documents |
Upload: | stanley-kennedy |
View: | 216 times |
Download: | 0 times |
Submission
doc.: IEEE 802.11-15/1003r1
NGP TG Sep. AgendaDate: 2015-09-13
Slide 1 Jonathan Segev, Intel Corporation
Sep. 2015
Name Affiliations Address Phone email Jonathan Segev Intel Corporation +972-54-2403587 [email protected]
Authors:
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
IEEE 802.11Task Group az
Next Generation Positioning
Bangkok , ThailandSep. 13th-18th , 2015
Chair pro-tem: Jonathan Segev (Intel)Secretary pro-tem: Zhou Lan (MediaTek)
Slide 2
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Abstract
This presentation contains the IEEE 802.11 NGP (Next Generation Positioning) Study Group agenda for the Sep. meeting.
Slide 3 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
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 – [email protected]
• Cell Phones Silent or OffSlide 4
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Logistics
Attendance:https://imat.ieee.org You must register before logging attendance.You must log attendance during each 2 hour session.
Documentationhttp://mentor.ieee.orgUse “TGaz” folder for documents relating to the TGaz activity.
Slide 5
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1September 2015
Slide 6
Patent Policy
Following 5 slides
Jonathan Segev, Intel Corporation
Submission
doc.: IEEE 802.11-15/1003r1September 2015
Slide 7
Instructions for the WG ChairThe 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 6.3.5 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 802.11-15/1003r1September 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 802.11-15/1003r1September 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 Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/develop/policies/opman/sect6.html#6.3
Material about the patent policy is available at http://standards.ieee.org/about/sasb/patcom/materials.html
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at [email protected] or visit http://standards.ieee.org/about/sasb/patcom/index.html
This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt
Jonathan Segev, Intel Corporation
Submission
doc.: IEEE 802.11-15/1003r1September 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 802.11-15/1003r1September 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 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.
Jonathan Segev, Intel Corporation
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
TGaz - Schedule in a Glance
Slide 12
Sep. 2015
MON TUE WED THU FRIAM1 NGP
AM2 NGP
PM1
PM2 NGP
Eve
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Agenda Items for the Week• Patent policy• Approve previous meeting minutes (11-15/970r1). • Review CSD and PAR modifications coming from EC and NesCom approval
process.• Generate TG officers recommendation for 802.11 chair approval.• Review TG development process and documentation.• Responding to liaison letter from ATIS (Alliance for Telecommunication and
Industry Solution). • Presentations to inform the TG:
• Continued development of the use case documents.• Problems statements• Channel models
• Schedule teleconference times as needed.
Slide 13
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Submission List for the week
Slide 14
Sep. 2015
Document No. Presenter Title Topic
11-15-1003 Jonathan Segev NGP Sep. 2015 Agenda Agenda Deck
11-15-992 Jonathan Segev Liaison from ATIS on Emergency Location
Review and response to liaison letter.
11-15-388 Santosh Pandey NGP Use Case Template Use case
11-15-0030 Brian Hart NGP PAR Review PAR post IEEE-SASB approval.
Edward Au TGaz development documentation Program development process
11-15-0834 Kare Agardh Further Use Cases for Next Generation Positioning
Use cases
11-15-10
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Meeting Slot #1
Slide 15
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
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)• Review changes from PAR approval process (15min)• Closing the call for nominees for Task Group chair and nominees
presentation (10min).• Review and adopt NGP SG updated use case document (30min)• TGaz development documentation (30min)• Further Use Cases for Next Generation Positioning (30min - As time
permits)• Recess
Slide 16
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Submission order – Slot 1
Slide 17
Sep. 2015
Document No. Presenter Title Topic
11-15/1003 Jonathan Segev Next Gen. Positioning Agenda Deck
11-15-388 Brian Hart NGP Use Case Template Use case
11-15-0030 Brian Hart PAR document PAR
Edward Au TGaz development documentation Program development process
11-15-1061 Kare Agardh Further Use Cases for Next Generation Positioning
Use cases
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Approval of previous meeting minutes
July meeting minutes (11-15/970r1 ) dated July 28th .
Motion:We approve document 11-15/970r1 as our meeting minutes for the Waikoloa meeting.Move:2nd:
Y: N: A:
Slide 18
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Presentations
Slide 19
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Adopting Use Case document baseline
Use case document (https://mentor.ieee.org/802.11/dcn/15/11-15-0388-01-0ngp-ngp-use-case-template.pptx) dated August 29th .
Motion:We approve document 11-15/0388r01 as our working draft baseline for the use case document. Move:2nd:Y: N: A:
Slide 20
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Attendance remainder
Slide 21
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Recess
Slide 22
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Meeting Slot #2
Slide 23
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Meeting Slot # 2 Agenda
• Call Meeting to Order (1min)• Patent Policy and Logistics (5min)• Agenda Setting (4min)• Generating TG chair recommendation for WG chair approval (10min).• Review and respond to liaison letter form ATIS (45min).• Presentations to inform the group on use cases, process, timelines.
Slide 24
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Submission order – Slot 2
Slide 25
Sep. 2015
Document No. Presenter Title Topic
11-15/1003 Jonathan Segev Next Gen. Positioning Agenda Deck
11-15/992 Jonathan Segev Liaison from ATIS on Emergency Location
Review and respond to liaison letter.
11-15-1061 Kare Agardh Further Use Cases for Next Generation Positioning
Use cases
11-15/1003 Jonathan Segev TG process TG process
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
How long to develop an amendment?
• The number of unknowns when evaluating a project timelines are substantial:• Technical unknowns – channel development, different technical
approaches, one protocol needs to solves several usages, selection between multiple options.
• Schedule unknowns – dependency on other amendments, comment resolution and technical quality of submissions, time needed to develop agreements.
Slide 26
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
How long to develop an amendment?
• How to evaluate the schedule then?• Compare to other amendments – do we have any reason to believe we’ll
do better?• Compare to one or more projects with similar complexity and size.• Extrapolate based • Make an educated guess on size and estimate length based on historical
data progress. • Close the loop and perform sanity check by receiving inputs from ITAs
(e.g. WFA) as to the timing of market demand for products.
Slide 27
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
How long to develop an amendment?
• Risk reduction for process evaluation• Agree on a process that decreases the unknowns and helps to build
agreements amongst group members. The process should facilitate:• A focus on the what we want to solve (e.g. reduce overhead for scenario from
X to 1/10X).• Agree on the high level technological approach (e.g. agree on broadcast
method/reduced unicast/ mix for scalable location)• Focus on key elements of the solution (negotiation, scheduling, PHY element
structure, PHY level protocol details)• Go to greater details (specific messages used, message flow).
Slide 28
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Possible Development Documents
• Use case/usage model document – marketing level like document (UX, without going into too much technical specifics and challenges).
• Functional requirement document – what are the requirements to which the solution needs to comply with.
• Calibration document – channel model specific or selection of channel model subset.
• Evaluation methodology – how to select between competing proposals• Frame work document – evolving document for setting • Draft amendment text
Slide 29
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
TG documentationWe agree on development of the following documentstowards the TGaz amendment development:a. Use case documentb. Calibration documentc. Functional requirements documentd. Evaluation methodologye. Spec frame work
Move:2nd:Y-N-A:
Slide 30
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Goals for the Nov. meeting
• Continue with technical presentations.• TG approval for use case document.• Review and approve development process and timeline.
Slide 31
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Teleconference Schedule - TBD
• Oct. 28th 10:00 ET for 1hr. • Do we need anymore calls?
Strawpoll:We agree to the conference call schedule depicted above.Y:N:A:
Slide 32
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Teleconference Schedule
Oct. 28th 10:00 ET for 1hr - do we need anymore calls?
Motion:We agree to the conference call schedule depicted above.
Move:2nd:
Results: Y: N: A:
Slide 33
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Remainder to do attendance
Slide 34
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
AOB?
Slide 35
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Adjourned
Slide 36
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Backup
Slide 37
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
References
Slide 38 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Some history
IEEE 802.1
1
IEEE 802.1
1a
IEEE 802.1
1b
IEEE 802.1
1c
IEEE 802.1
1d
IEEE 802.1
1e
IEEE 802.1
1F
IEEE 802.1
1g
IEEE 802.1
1h
IEEE 802.1
1i
IEEE 802.1
1j
IEEE 802.1
1k
IEEE 802.11ma
IEEE 802.1
1n
IEEE 802.1
1p
IEEE 802.1
1r
IEEE 802.1
1s
IEEE 802.11.2
IEEE 802.1
1u
IEEE 802.1
1v
IEEE 802.1
1w
IEEE 802.1
1y
IEEE 802.1
1z
IEEE 802.11mb
IEEE 802.11aa
IEEE 802.11ac
IEEE 802.11ad
IEEE 802.11ae
IEEE 802.11af
IEEE 802.11ah
IEEE 802.1
1ai
0.00
10.00
20.00
30.00
40.00
50.00
60.00
70.00
80.00
90.00
Months between IEEE SASB Approval and publish
Months between end of last Sponsor ballot and IEEE SASB approval
Months between start of first Sponsor ballot and end of last Sponsor ballot
Months between end of last WG ballot and start of first Sponsor Ballot
Months between start of first WG ballot and end of last WG ballot
Months between PAR Ap-proval and start of first WG ballot
Slide 39 Jonathan Segev (Intel)
July 2015
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Historical performance data
Slide 40
Sep. 2015
Stage Duration
11v 11u 11ac [1] 11ad [1] Proposed for 11az
PAR approval -> Approved Standard
64 months 46 months
PAR approval -> Draft 1.0
34 months 21 months
PAR approval -> D0.1
29 months 17 months
D0.1 –> Draft 1.0
6 months 4 months
Draft 1.0 –> Draft 2.0
8 months 6 months
Draft 2.0 -> Final 22 months 19 months
Amendment size 442 pg. 679 pg.
Submission
doc.: IEEE 802.11-15/1003r1
Jonathan Segev, Intel Corporation
Study Group Timeline - modified
Slide 41
Sep. 2015
Month Milestone / Plan of Action
January (i) Formation meetingInitial discussion on PAR and CSD Presentations on use cases, usage models.
March (p) Continue discussion on PAR and CSDDiscussion supporting presentations.Study Group extension
May (i) SG Final version of PAR and CSDDiscussion on supporting presentationsWorking Group Approval on PAR and CSDPAR circulated amongst other WGs.
July (p) Presentations.Resolve EC feedback on PAR and CSD.Executive Committee Approval on PAR and CSDStudy Group extension
July NesCom Approval on PAR and CSD (July 24/Sep. 4th submittal deadline).
Nov. Sep. (actual) Task Group formation meeting
Submission
doc.: IEEE 802.11-15/1003r1
Motions and strawpolls as needed
Motion/strawpollTo 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:2nd:Y: N: A:
Slide 42 Jonathan Segev (Intel)
July 2015
Submission
doc.: IEEE 802.11-15/1003r1
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 43 Jonathan Segev (Intel)
July 2015
Submission
doc.: IEEE 802.11-15/1003r1
Motions on submission xxx
MotionTo 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: 2nd:Y: N: A:
Slide 44 Jonathan Segev (Intel)
July 2015
Submission
doc.: IEEE 802.11-15/1003r1
Strawpoll#1 submission 634
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 45 Jonathan Segev (Intel)
July 2015
Submission
doc.: IEEE 802.11-15/1003r1
802.11 Template Instructions 1/4
• To properly identify your PowerPoint presentation as an IEEE 802.11 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 46 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
802.11 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 802.11-04/9876r0" , or • "doc.: IEEE 802.11-04/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 802.11-04/9876r0”)– Footer = first author, company
• Click "Apply to all".– Step 7. Delete the four template instruction slides.
Slide 47 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
802.11 Template Instructions 3/4
• PowerPoint Submission Preparation Summary:– Things to do: 7– Fields to fill in: 12
Slide 48 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
802.11 Template Instructions 4/4Recommendations
– a) Always create a new presentation using the template, rather than using someone else's presentation.
– b) For quick and easy creation of new 802.11 submissions, place the 802.11 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\802.11– To create a new submission from within PowerPoint, menu select
File, New, then select the appropriate 802.11 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: 2010-03-01
Slide 49 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
• [begin placing presentation body text here]
Slide 50 Jonathan Segev, Intel Corporation
Sep. 2015
Submission
doc.: IEEE 802.11-15/1003r1
Slide 51 Jonathan Segev, Intel Corporation
Sep. 2015