1. Agenda AANI SC September 1 2016 Teleconference
July 2009
doc.: IEEE /0840r0
Agenda AANI SC September Teleconference
Date:
Authors:

2. Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: The September 1st 2016 teleconference of the Advanced Access Networks Interface (AANI) Standing Committee

3. IEEE 802.11 AANA Standing Committee
July 2009
doc.: IEEE /0840r0
IEEE AANA Standing Committee
Agenda
September 1, 2016
Chair: Joseph Levy (InterDigital)

4. Attendance, etc. Call for a secretary: please, volunteer
July 2009
doc.: IEEE /0840r0
Attendance, etc.
Call for a secretary: please, volunteer
Reminders to attendees:
Please send me an to register your attendance
Please mute when not speaking
No recordings

5. Participants, Patents, and Duty to Inform
July 2009
doc.: IEEE /0840r0
Participants, Patents, and Duty to Inform
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

6. July 2009
doc.: IEEE /0840r0
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

7. Call for Potentially Essential Patents
July 2009
doc.: IEEE /0840r0
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

8. 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 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.

9. Agenda Call for Secretary
Jan 2009
doc.: IEEE /1455r0
Agenda
Call for Secretary
Administrative: Attendance, Participants, Patents, Duty to Inform, Call for Patents, Guideline, Agenda
Status
Discuss draft LS to 3GPP RAN and SA on the inclusion of in 3GPP's proposal to ITU for IMT-2020 (Action B3)
New Business
Future Sessions Planning 

10. August,
doc.: IEEE /1093r0
Status
The AANI SC was formed at the July 802 Plenary meeting in San Diego [1] to:
Coordinate and support an IMT-2020 proposal, external proposal (option B3) [2]
Coordinate with and support (lead) in meeting the actions towards “IEEE “5G” specification” (option A) [2]
Report status to on the activities of this committee.
AANI SC held it’s first Teleconference on Wednesday August 17, 10:00 am EDT.
The name of the SC was agreed: Advanced Access Network Interface – AANI
The meeting time for the this teleconference was agreed September 1 10:00 am EDT
A ruff draft of the LS to 3GPP RAN and SA was briefly reviewed, a call for discussion of the document was made.
Joseph Levy (InterDigital)

11. Draft LS to 3GPP RAN Completion Plan
August,
doc.: IEEE /1093r0
Draft LS to 3GPP RAN Completion Plan
Current plan for completing the LS:
Continue discussion through Sept 13 evening F2F session
Present draft at the midweek plenary Sept 14 AM2
Complete LS discussion and drafting Sept 15 AM2
WG approval at closing plenary Sept 16 AM.
Current LS Draft in 11-16/1101r1, “Draft LS from to 3GPP RAN and SA on ITM-2020”
Inputs to be considered:
s posted to reflector
Text proposals for the LS to 3GPP, if available
Continue discussion on LS to 3GPP
Joseph Levy (InterDigital)

12. E-Mail Discussion Summary
Glenn Parsons: 8/17/16 11:46 am
Recommended 2 LSs: 802→3GPP and →3GPP RAN & SA
802 has endorsed a recommendation on how to engage in 5G/IMT-2020
has technology to support IMT-2020 use cases
LWA example of 3GPP already leveraging technology
We can do better if we work together.  So let’s work together for IMT-2020
For IEEE to be admitted as a member a request would need to be made to the 3GPP Organizational Partner council (3GPP OP). (probably not necessary)
For high level decision 802 should address 3GPP OP (which is likely)
It is too early in the process to ask to include radio interface in 3GPP’s IMT-2020 submission.
We need to build the relationship towards mutual benefit first.  By focusing on “technology” that does not preclude including the radio interface and does allow leveraging interworking/aggregation

13. E-Mail Discussion Summary
Roger Marks: 8/17/16 12:48 am
Agrees with Glenn in general.
Thinks it will be difficult for RAN and SA level to decide on a response until they get guidance from the business perspective from above
Proposes 1st step is an LS 802→3GPP OP, with copy to and 802.1, that summarizes Option B3, as Glenn described, and proposes that IEEE or an “IEEE 802 Access Network” could possibly be included, but only requests 3GPP’s view.
This initial LS could be followed up with a statement to RAN and SA, referring to 802’s statement.
The current LS draft advocates an interface in IMT This is not the correct approach as it is not in the scope of B3, while is not obligated to follow 802’s recommendations, it would be beneficial to do so.

14. E-Mail Discussion Summary
Adrian Stephens: 8/18/16 5:51 am (1/2)
Agrees the need for a two-pronged approach, but not sure of the timing.
does not need permission to write to RAN directly, but RAN and its subgroups have no obligation to pay attention.
RAN may feel obligated to ignore anything that makes substantive changes to a 3GPP output document unless it comes from 3GPP members.
Proposed approach, high level:
802 would like to work with 3GPP on the following topic.   Please indicate which groups we should be corresponding with, and on what topics.
802 would like to create an MoU with 3GPP to create a collaborative relationship on a the topic of 5G. The MoU will cite what information can be received by 3GPP, and which groups can receive it.

15. E-Mail Discussion Summary
Adrian Stephens: 8/18/16 5:51 am (2/2)
Proposed approach, level:
is relevant to 3GPP
is an opportunity to meet IMT-2020 requirements using unlicensed spectrum
would like to work together with 3GPP to maximize this opportunity
If we don't talk to the higher-levels in 3GPP,  we will need to attack the process questions directly with RAN.

16. The Chair’s View
While it may be beneficial to talk to the higher layers of 3GPP – RAN is responsible for the 3GPP IMT-2020 proposal, evaluation, and specification, hence all phases of the 3GPP IMT-2020 activity.
So if any aspects is to be included in the 3GPP IMT-2020 proposal, then should talk with RAN about it.
RAN may choose to ignore or they may not: But we can only find out by asking (sending an LS).
Higher level discussion with 3GPP should be done at the 802 level. If it is agreed this is desirable, we should draft an LS and pass it on to the 802 EC.

17. New Business Any other business? August, 17 2016
doc.: IEEE /1093r0
New Business
Any other business?
Joseph Levy (InterDigital)

18. Future Sessions Planning
August,
doc.: IEEE /1093r0
Future Sessions Planning 
September F2F meeting:
Tuesday (2/13) – complete draft LS to 3GPP, so it can be presented at the Mid-Week Plenary for discussion/review
Thursday (2/15) – update LS to 3GPP if necessary, based on discussion/review at the Mid-Week Plenary. Finalize the LS for approval at the Closing Plenary.
Goal is to send an LS from to 3GPP RAN before the September 3GPP RAN Plenary meeting (September 19-22), 3GPP SA Plenary meeting (September 21-23)
Joseph Levy (InterDigital)

19. References 11-16-1057-01-0000-802-11-imt-2020-5g-sc-proposal
August,
doc.: IEEE /1093r0
References
imt g-sc-proposal
ec GSG-report-ieee-802-ec-5g-imt-2020-sc
Joseph Levy (InterDigital)