1 / 106

Agenda for IEEE 802.11 Coexistence SC meeting in Vancouver in Mar 2019

Agenda for IEEE 802.11 Coexistence SC meeting in Vancouver in Mar 2019. 11 March 2019. Authors:. Welcome to the 11th F2F meeting of the Coex SC in Vancouver in January 2019. The IEEE 802.11 PDED ad hoc was formed in September 2016 at the Warsaw interim meeting

bradleyv
Download Presentation

Agenda for IEEE 802.11 Coexistence SC meeting in Vancouver in Mar 2019

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agenda for IEEE 802.11 Coexistence SC meeting in Vancouver in Mar 2019 • 11 March 2019 Authors: Andrew Myles, Cisco

  2. Welcome to the 11th F2F meeting of the Coex SC in Vancouver in January 2019 • The IEEE 802.11 PDED ad hoc was formed in September 2016 at the Warsaw interim meeting • The IEEE 802.11 PDED ad hoc met in San Antonio (Nov 2016), Atlanta (Jan 2017), Vancouver (Mar 2017) and Daejeon (May 2017) • In Daejeon in May 2017 it was decided to convert the IEEE 802.11 PDED ad hoc into the IEEE 802.11 Coexistence SC • The IEEE 802.11 Coexistence SC met in Berlin (July 2017), Hawaii (Sept 2017), Orlando (Nov 2017), Irvine (Jan 2018), Chicago (Mar 2018), Warsaw (May 2018), San Diego (July 2018), Hawaii (Sept 2018), Bangkok (Nov 2018), St Louis (Jan 2019) and will meet once or twice this week • Wed PM1 • Thu PM1 (if required) Andrew Myles, Cisco

  3. The first task for the Coex SC today is not to appoint a secretary • It is important to keep proper minutes of all Coexistence SC meetings • Fortunately, Guido Hiertz (Ericsson) agreed in Berlin to be appointed the IEEE 802.11 Coexistence SC’s permanent Secretary … Andrew Myles, Cisco

  4. The Coex SC will review the official IEEE-SA patent material for pre-PAR groups Andrew Myles, Cisco

  5. The Coex SC will operate using accepted principles of meeting etiquette • IEEE 802 is a world-wide professional technical organization • Meetings shall be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization • Individuals shall address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about others Andrew Myles, Cisco

  6. The Coex SC will review the modified “Participation in IEEE 802 Meetings” slide • Participation in any IEEE 802 meeting (Sponsor, Sponsor subgroup, Working Group, Working Group subgroup, etc.) is on an individual basis • Participants in the IEEE standards development individual process shall act based on their qualifications and experience (IEEE-SA By-Laws section 5.2.1) • IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (sub-clause 4.2.1 “Establishment”, of the IEEE 802 LMSC Working Group Policies and Procedures) • Participants have an obligation to act and vote as an individual and not under the direction of any other individual or group. A Participant’s obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders • Participants shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, (IEEE-SA By-Laws section 5.2.1.3 and the IEEE 802 LMSC Working Group Policies and Procedures, subclause 3.4.1 “Chair”, list item x) • By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate Dorothy Stanley, HP Enterprise

  7. The Coex SC will consider a proposed agenda for Vancouver • Proposed Agenda • Bureaucratic stuff, including approving minutes • What is happening this week? (in no particular order) • Scope of IEEE 802.11 Coexistence SC (a reminder) • Preparation for Coexistence Workshop • … • Relationships • Review of recent ETSI BRAN meeting • Review recent 3GPP RAN1 activities • Discuss response from 3GPP RAN4 to LS • … • … Additional agenda items are requested from all interested stakeholders Andrew Myles, Cisco

  8. The Coex SC will consider a proposed agenda for Vancouver • Proposed Agenda • Technical issues • Adaptivity in EN 301 893 • LBT for management/control in NR-U • Use of preambles in NR-U • Use of multiple channels • … • Other issues • … • Other business Additional agenda items are requested from all interested stakeholders Andrew Myles, Cisco

  9. Scope of IEEE 802.11 Coexistence SC Andrew Myles, Cisco

  10. The agreed Coex SC scope focuses on ensuring 802.11ax has fair access to global unlicensed spectrum Discuss the use of PD, ED or other 802.11 coexistence mechanisms with the goal of promoting “fair” use of unlicensed spectrum Promote an environment that allow IEEE 802.11ax “fair access” to global unlicensed spectrum • Will initially focus on liaising with 3GPP RAN/RAN1/RAN4 but may also lead to interactions with regulators and other stakeholders • Will probably not conclude at least until RAN4’s 802.11/LAA coexistence testing is defined and successfully executed • May require the SC to consider other simulations and results of tests of potential LAA/802.11 coexistence mechanisms • Will initially focus on encouraging a “technology neutral” solution in the next revision of EN 301 893 that allows IEEE 802.11ax fair access to unlicensed spectrum in Europe (noting the European approach is likely to have global impact) • The effort will also focus on allowing 802.11ax to use innovative mechanisms for frequency reuse without compromising the goal of fair access Andrew Myles, Cisco

  11. Coex SC will close when determined by the 802.11 WG or 802.11ax is ratified • IEEE 802.11 Coexistence SC close down criteria • The SC is closed by the IEEE 802.11 WG • … after it is determined that the SC is unlikely to make further progress towards its goals • IEEE 802.11ax completes Sponsor Ballot • … noting that the Coexistence SC ad hoc is unlikely to be relevant at that point anyway Andrew Myles, Cisco

  12. Minutes Andrew Myles, Cisco

  13. The Coex SC will consider approval of the meeting minutes from St Louis • The minutes for the Coex SC at the St Louis meeting in Jan 2019 are available on Mentor: • See 11-19-0271-00 • Motion: • The IEEE 802 Coex SC approves 11-19-0271-00as minutes of its meeting in St Louis in Jan 2019 • Moved: • Seconded: • Result: Andrew Myles, Cisco

  14. Agenda items The workshop Andrew Myles, Cisco

  15. The Coex SC will hear an update on the Coex Workshop arrangements • Topics • Invitations • Sponsorships • Call for invited papers • Call for other papers Andrew Myles, Cisco

  16. Invitations for the Coex Workshop were finally sent out on about 22 February 2019 • It was originally planned that Coex Workshop would be sent within a few weeks of the St Louis meeting • Unfortunately, weather and other factors meant that the logistics of the Workshop could not be confirmed and so the invitations were held back • By late February we still did not have confirmation of the logistics but we had sufficient confident to send the invitations anyway (on about 22 Feb 2019) • The invitation was based on the material discussed during the St Louis meeting and was sent to seven organisations Andrew Myles, Cisco

  17. The Coex Workshop invitation was sent to seven organisations • Does anyone have suggestions for invitations to additional organisations? • Recall that we decided to not send explicit invitations to regulators, although they are welcome to attend given it is an open workshop Andrew Myles, Cisco

  18. The invitation was based on the material discussed by the Coex SC in St Louis 3GPP RAN invitation Invitee Lots of CC’s Invitation + when/where Coex workshop goals Call for papers with deadline of 12 May 2019 Next page: invitation to IEEE 802 plenary Logistics with link Andrew Myles, Cisco

  19. The Coex Workshop invitation sent to the various organisations links to a web page http://grouper.ieee.org/groups/802/11/Workshops/2019-July-Coex/workshop.htm Andrew Myles, Cisco

  20. There are three Coex Workshop sponsorships of $5000, which will reduce registration fees to $50 • Two companies have agreed to sponsor the Workshop for $5000 each (with signage rights and lots of thanks) • HPE • Quantenna • The IEEE 802 Wireless Chairs have also agreed to sponsor the Workshop for up to $5000 • This means that a $50 registration fee will cover (assuming 100 attendees) two coffee breaks and a stand-up dinner • There is still an opportunity for an additional sponsorship – to replace the IEEE 802 Wireless Chairs sponsorship! Andrew Myles, Cisco

  21. The Coex Workshop schedule includes 7.5 hours of meeting and 2 hours of eating/drinking • Workshop schedule • 12:30 13:00 Welcome coffee station • 13:00-15:30 Meeting (2.5 hours) • 15:30-16:00 Coffee Break • 16:00-19:00 Meeting (3 hours) • 19:00-20.00 Dinner • 20:00-22:00 Meeting (2 hours) Andrew Myles, Cisco

  22. The web page includes a more detailed proposed agenda for the Coex Workshop • Welcome & Introduction to the Coexistence Workshop • Invited standardisation updates • IEEE 802.11ax status • 3GPP NR-U status • IEEE 802.11 EHT plans • Invited regulatory update • Brief update on the availability of the 6GHz band for unlicensed use • Deployment update • Short papers on coexistence experience between 3GPP LAA and IEEE 802.11ac in the 5GHz band • Coexistence topics • Short papers on any aspect relevant to the Coexistence Workshop’s goals • Summary of the Coexistence Workshop • Next steps Agenda Andrew Myles, Cisco

  23. Space for the Coex Workshop is limited and may require some sort of quota • Space at the Coex Workshop is limited to 100 • 3GPP are expecting to send 30-40 • Attendance from GSMA, WBA, ETSI BRAN, WFA & 5G ACIA is unknown but likely to be small – say 10 • 802.11 could easily take the whole 100 • We need to ensure that there is a balanced attendance • One way to arrange this is to have quotas • 3GPP - 25 • IEEE 802 – 25 • Invited individuals – 10 • Other orgs – 10 • First in/best dressed – 30 • Discussion on this topic will continue this week in WG leadership Andrew Myles, Cisco

  24. There are some invited individuals that need to have places at the Coex Workshop • IEEE 802.11 • Dorothy Stanley (WG Chair) • Andrew Myles (SC Chair) • Guido Hiertz (SC Secretary) • 3GPP • BalázsBertényi (RAN Chair) • Wanshi Chen (RAN1 Chair) • Havish Koorapaty • ETSI BRAN • David Boldy (ETSI BRAN rep) • Other • Andy Gowans (invited 6GHz speaker) Andrew Myles, Cisco

  25. We need to proactively arrange “invited papers” for the CoexWorkshop • The first part of the agenda consists of some invited papers • Invited standardisation updates • IEEE 802.11ax status • 3GPP NR-U status • IEEE 802.11 EHT plans • Invited regulatory update • Brief update on the availability of the 6GHz band for unlicensed use • Brief update on ETSI BRAN activities • The Coex SC Chair has reached out to the: • Chairs of RAN/RAN1 for a standards update on NR-U, particularly as it related to coexistence • Chair of ETSI BRAN for an update EN 301 893 and similar work for 6 GHz • Andy Gowans for an update on 6GHz rules globally • We need to make similar requests of: • Chair of IEEE 802.11 TGax for 802.11ax update • Chair of IEEE 802.11 TGbe (EHT SG) for 802.11be update Andrew Myles, Cisco

  26. A request was sent to the 3GPP RAN/RAN1 Chairs for an “invited paper” standards update • An e-mail request was sent to the 3GPP RAN/RAN1 Chairs for an invited paper standards update on NR-U, particularly as it relates to coexistence issues • … request that you arrange for one or more RAN/RAN1 participants to develop appropriate material for the invited paper that describes progress in  3GPP NR-U , particularly in relation to coexistence with 802.11ax and 802.11be (EHT). • There has been no response so far • It may be discussed at upcoming RAN/RAN1 meetings Andrew Myles, Cisco

  27. A request was sent to the ETSI BRAN Chair for an “invited paper” regulatoryupdate • Request to ESTI BRAN Chair for an invited paper regulatory update on EN 301 893 and similar work for 6 GHz • … request that you arrange for one or more BRAN participants to develop appropriate material for the invited paper that describes progress in the aspects of EN 301 893 related to coexistence and any plans for activities to address similar issues in the 6Ghz band. • The ETSI BRAN Chair sent the IEEE 802.11 WG Chair a response after the recent ETSI BRAN meeting • We are pleased to inform you that TC BRAN has accepted this invitation and in addition we agreed that we will prepare a short presentation for which the headlines are copied below • The presentation itself will be done by David Boldy who is vice-chair of ETSI TC BRAN • The slide deck will be send to you immediately after our next meeting in June which will end on Thursday 20 June. Andrew Myles, Cisco

  28. ETSI BRAN have prepared an outline of their contribution to the Coex Workshop • ETSI BRAN outline (1/2) • Status of 6GHz in Europe • SE45: ECC Report 302 (Timeline) • FM57: Draft CEPT Report A in response to the EC mandate (Timeline) • FM57: Draft CEPT Report B in response to the EC mandate (Timeline) • Hand off process from CEPT to ETSI • ETSI 6GHz • Development of an ETSI SRDoc (containing the spectrum request to CEPT) • Development of an ETSI Technical Report (TR) • Work item for developing an ETSI Harmonized Standard • timelines • EN 301 893 or new standard?? • Work programme (explanation of timelines/procedure/deliverables) • … Andrew Myles, Cisco

  29. ETSI BRAN have prepared an outline of their contribution to the Coex Workshop • ETSI BRAN outline (2/2) • ... • ETSI 5GHz • Status of EN 301 893 v2.2.1 • Brief History of Adaptivity • Lessons learned from the past • Most contentious requirements/compromises • What can ETSI do better for 6GHz? • Participation • Next BRAN meeting dates BRAN#103/104 • Participation / Proposals / contributions welcome Andrew Myles, Cisco

  30. The SC will discuss the scope of the 11ax/be “invited papers” • This week the Coex SC Chair will make requests for “invited papers” in relation 802.11ax and 802.11be (EHT) • The requests will be sent to the applicable TG Chairs • The scope of the request will be: • An update on the status of 802.11ax/be • A summary of coexistence mechanisms used by 802.11ax/be • … what else? • The SC will discuss the scope of the 11ax/be invited papers Andrew Myles, Cisco

  31. Andy Gowans (OFCOM) has accepted an invitation to provide a 6GHz regulatory update • Access to 6 GHz spectrum is a precondition to any coexistence discussions • Dorothy Stanley (IEEE 802.11 WG Chair) suggested that we ask Andy Gowans (OFCOM) to provide a brief summary of the situation for access to 6 GHz globally and any likely associated rules • The Coex SC Chair sent Andy an invitation by e-mail, which he accepted Andrew Myles, Cisco

  32. The Coex Workshop will also provide anyone to submit a proposal for a paper on any coex topic • The Coex Workshop will also include a section for contributed papers on any topic (related to coexistence) • Topics could include: • Deployment experience in 5 GHz • Simulation results on various coexistence schemes • Proposed requirements for any coexistence schemes • The use of ED-only vs PD/ED vs both • The use of 802.11 or common preambles • Multi-channel sharing • Blocking energy  • The use of no LBT or short LBT • CW adjustment with delayed acknowledgments • … Andrew Myles, Cisco

  33. 802.15 want to include UWB within the scope of the Coex Workshop • The main goal of the Workshop is to focus on coexistence between 802.11ax/be and NR-U in 6GHz • IEEE 802.15 WG would like to discuss coexistence with UWB in the 6GHz band … • …. and indeed inclusion in the agenda is the basis of all the Wireless Chairs agreeing to Sponsor part of the Coex Workshop • It would be nice if 802.15 WG and 802.11 WG could come to a consensus before the Coex Workshop to avoid airing any dirty washing Andrew Myles, Cisco

  34. The non-invited papers will form the basis for discussion during the Coex Workshop • A general call for papers has been issued with the invitation • A deadline for proposals has been set for 12 May, which is just before the IEEE 802 meeting in Atlanta • The idea is that the Coex SC will select a balanced set of papers at the Atlanta meeting and send out acceptances immediately afterwards • The authors will then be expected to submit final versions of their papers at the beginning of July • During the Coex Workshop, appropriate time will be allowed for each paper, followed by discussion time (it is a Workshop after all) Andrew Myles, Cisco

  35. On what would we like consensus at the end of the Coexistence Workshop? • It is probably worthwhile knowing what issues 802.11 stakeholders would like to see consensus on at the end of the Coex Workshop • This may even inspire people to focus on submissions on these topics Andrew Myles, Cisco

  36. Are any IEEE 802.11 WG participants planning to submit a proposal for a non-invited paper? Andrew Myles, Cisco

  37. Agenda items LAA status Andrew Myles, Cisco

  38. Updated statistics conform that there is significant and growing interest in LAA 1 GSMA (July 2018) 2 GSA: Evolution from LTE to 5G: Global Market Status (Nov 2018) 3 GSA: LTE in unlicensed and shared spectrum (Jan 2019) Andrew Myles, Cisco

  39. Agenda items Review of ETSI BRAN teleconference on 29 January 2019 Andrew Myles, Cisco

  40. ETSI BRAN is working diligently to complete the adaptivity clauses • ETSI BRAN is working diligently to polish the requirements in the next revision of EN 301 893 • There is very little substantive contention on most of the proposed refinements • A teleconference was held on 29 January to consider various refinements to the adaptivity clause • The following pages summarize the discussions • There do not appear to be any open issues of significant concern to IEEE 802.11 WG Andrew Myles, Cisco

  41. ETSI BRAN is working diligently to complete the adaptivity clauses • BRAN(18)099003r1- Paused COT in EN 301 893 (Cisco) • Proposal for refined text that • Requires paused COT feature to use ED-only mechanism • Imposes a requirement that a short LBT cannot interfere with 16us gap • Resolution is waiting for Ericsson evaluation • BRAN(19)000006 - Response to BRAN(18)099013r1 (Ericsson) • Proposes solution to make clear that COT length does not double count simultaneous transmissions, eg like in OFDMA • Group agreed to work on revised text • BRAN(19)000007 - Clarification regarding initiating device behavior (Ericsson) • Make references to listening in LBT more generic • Agreed but with some additional refinement required to deal with missed reference in proposal Andrew Myles, Cisco

  42. ETSI BRAN is working diligently to complete the adaptivity clauses • BRAN(19)000008 – Modifications regarding 4.2.7.3.2.6 (Ericsson) • Refinement to delete confusing and duplicated rules about COT length • Agreed • BRAN(19)000009 – Response to modifications proposed in BRAN(18)099016r2 (Ericsson) • Objection to Broadcom proposal to limit paused COT starts to 1ms boundaries • Broadcom withdrew proposal Andrew Myles, Cisco

  43. ETSI BRAN is working diligently to complete the adaptivity clauses • BRAN(18)099015a1 -TXOP Explanation to support BRAN(18)099015r2 (Broadcom) • Highlighted that EN 301 893 does not clearly allow typical Wi-Fi packet-ack-packet-ack-… behavior in a COT • Group agreed to work on appropriate text • This discussion highlights the importance of 802.11 WG monitoring the ETSI BRAN work • BRAN(19)000011– Response to BRAN(18)099014r1 (Ericsson) • Objected to a Broadcom proposal to ensure a responder used a power no greater than the initiator of COT • Broadcom withdrew the proposal • This is an issue that may still need monitoring in RAN1 Andrew Myles, Cisco

  44. ETSI BRAN is working diligently to complete the adaptivity clauses • Other issues • Cisco noted that EN 301 893 does not allow LAA to do delayed adjustment of CW, contrary to previous agreements • A group will work on refined text • This discussion highlights the importance of RAN1 monitoring the ETSI BRAN work, although this issue was actually highlighted by a Wi-Fi stakeholder Andrew Myles, Cisco

  45. The ETSI BRAN teleconference raised some practical and philosophical issues about EN 301 893 • It was noted that in EHT a distributed MIMO scheme might be introduced but that EN 301 893 was not written with this sort of feature in mind • One participant asserted that • This is a good example how TC BRAN's backwards-looking, innovation-ignoring mentality guarantees creating issues in the future • At the RAN1 meeting an argument was made that constraints on NR-U from EN 301 893 are an attack on innovation • On the other hand, it could be argued that having an independent body like ETSI BRAN putting some basic rules in place imposes a discipline on the SDOs • It certainly helped encourage RAN1 to adopt EDCA-like LBT, and other 802.11 like sharing features, rather than more LTE-U like un-sharing features • Regardless of this philosophical argument, TGbe is going to have to think about how it wants EN 301 893 to develop over time Andrew Myles, Cisco

  46. Agenda items Review of ETSI BRAN #101 meeting Andrew Myles, Cisco

  47. The Coex SC will discuss the ETSI BRAN #101 meeting • The last meeting of ETSI BRAN was in February in Sophia Antipolis • The Coex SC is focusing on final refinements for the next revision of EN 301 893 • A proposal to effectively remove the adaptivity rules in EN 301 893 did not obtain much support • It was agreed to consider adaptivity refinements for broadcasts & delayed acknowledgements • Some editorial refinements were agreed for EN 301 893 • A proposal to maintain the status quo for “paused COT” and focus on requirements was not agreed Andrew Myles, Cisco

  48. A proposal to effectively remove the adaptivity rules in EN 301 893 did not obtain much support • BRAN(19)101008 - Steps seven and eight in 4.2.7.3.2.6 (Ericsson) • Asserted that the current version of EN 301 893 does not cover broadcast, delayed block acks and HARQ in 802.11 • Proposed to adjust adaptivity clause so that adjustment of the CW is effectively not defined by EN 301 893 • Appeared to argue that it is too hard to formulate rules that do not unreasonably limit innovation • There was little support for the proposal because it essentially did not impose any sharing discipline Andrew Myles, Cisco

  49. It was agreed to consider adaptivity refinements for broadcasts & delayed acknowledgements • BRAN(19)101021 - Adaptivity refinements for broadcasts and delayed acknowledgements (Cisco) • Proposed refinements to the adaptivity clause to handle broadcasts, block acksand delayed block acks in 802.11 and delayed acks in LAA/NR-U better • A brief and very rough summary of the proposal • If txacked or will not be re-tx’dthen reset CW • If nacked (or lack of an ack) then double CW • If evidence of success unavailable then CW remains same • The proposal is: • Is aligned with 802.11 for broadcasts and block acks in 802.11 • May not be aligned with delayed block acks in 802.11 or delayed acks in LAA; the problem is these mechanisms do a CW reset before evidence of success or otherwise is available • It was agreed to use this proposal (now in Word document as BRAN(19)101034) as a starting point for further discussion Andrew Myles, Cisco

  50. Some editorial refinements were agreed for EN 301 893 • BRAN(19)101009 - The use of clause 4.2.7.3.2.5 (Ericsson) • An editorial proposal to clean up text defining the rules for declaring the state of the wireless medium to be occupied or unoccupied • Agreed • BRAN(19)101010(Qualcomm, Ericsson, Cisco & CableLabs) • A refinement to the definition of the Channel Occupancy Time (COT) • Agreed Andrew Myles, Cisco

More Related