1 / 41

IEEE 802.18 RR-TAG Waikoloa Wireless Interim Agenda

This is the agenda for the IEEE 802.18.RR-TAG Waikoloa Wireless Interim meeting, including administrative items, discussion items, and general items for the wireless industry.

lopezd
Download Presentation

IEEE 802.18 RR-TAG Waikoloa Wireless Interim Agenda

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. IEEE 802.18 RR-TAGWaikoloa Wireless Interim Agenda • Dates: 11 September 18 • 13 September 18 Authors: Jay Holcomb (Itron)

  2. Call to Order / Administrative Items • Officers for the RR-TAG / IEEE 802.18: • Chair is Jay Holcomb (Itron) • Vice-chair is open • Secretary is Allan Zhu (Huawei) • Number of voters: 40 (9 on EC); Nearly Voter: 1; Aspirant members: 9 • A quorum is met since this meeting was announced more then 45 days ago. • Attendance server is open • IEEE 802 Required notices: • Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html • > Be sure to announce you name, affiliation, employer and clients the first time you speak. • Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf • Ethics - https://www.ieee.org/about/corporate/governance/p7-8.html • IEEE 802 WG Policies and Procedures - http://www.ieee802.org/devdocs.shtml • The 4 administration slides, reminder from your WG opening plenary  new 02jan18 • (note: call for essential patents is n/a, as the RR-TAG does not do standards) Jay Holcomb (Itron)

  3. Jay Holcomb (Itron) 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 of different technical approaches that include relative costs of patent licensing terms may be discussed in standards development meetings. • Technical considerations remain the 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. --------------------------------------------------------------- For more details, see IEEE-SA Standards Board Operations Manual, clause 5.3.10 and Antitrust and Competition Policy: What You Need to Know at http://standards.ieee.org/develop/policies/antitrust.pdf

  4. Participation in IEEE 802 Meetings • 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. (https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf 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”. (subclause 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, see https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf 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. (and to please leave the meeting.) Jay Holcomb (Itron)

  5. Agenda • Discussion items, few more details: • Congratulations • EU Items • General items, ETSI, CEPT, etc. • Google waiver request, NCTA feedback request • No one stepping up to ex Parte • General discussion items: • Additional FS Protection ex parte • 6 (5-7) GHz and single voice from IEEE 802. • IEEE EU Spectrum Management Statement • Since July plenary. (Uganda and Ofcom) • NPRM, Expanding Flexible Use of 3.7 to 4.2GHz Band • Call to Order • Attendance server is open • Administrative items • Need a recording secretary • Approve agenda & last minutes • Any interest in being the 802.18 Vice-Chair? • Discussion items • Congratulations • EU Items • Google waiver request • General Discussion Items • Actions required • Several • AOB and Adjourn Jay Holcomb (Itron) Agenda

  6. Administrative – Motions and more • Need a recording secretary for this Wireless Interim in Waikoloa, anyone please? • Ben Rolf (BlindCreek Assoc. and UWB Alliance) volunteered. • Motion: To approve the agenda as presented on previous slide • Moved by: John Notor (Notor Research) • Seconded by: Billy Verso (Decawave) • Discussion? • Vote: Unanimous consent • Motion: To approve the minutes from the IEEE 802.18 Plenary on 10-12 July 2018 in San Diego, CA, USA in document: https://mentor.ieee.org/802.18/dcn/18/18-18-0110-00-0000-meeting-minutes-july-2018-f2f-san-diego.docx Posted: 08-Sep-2018 11:30:35 ET • Moved by: John Notor (Notor Research) • Seconded by: Tim Godfrey (EPRI) • Discussion? • Vote: Unanimous consent • Does anyone have an interest in being the 802.18 Vice-Chair? No one spoke up. • See next slides Jay Holcomb (Itron)

  7. Responsibilities of Working Group Officers • 3.0 Officers • There shall be a Chair and a Secretary, and there should be a Vice Chair. The office of Treasurer is suggested if significant funds are involved in the operation of the Working Group and/or its subgroups or if the group has multiple financial reports to supply to the IEEE Standards Association. A person may simultaneously hold the positions of Secretary and Treasurer. • The Chair and Vice Chair(s) shall each be IEEE members of any grade, except Student grade, or IEEE Society affiliates, and also be members of IEEE-SA. • 3.4 Responsibilities of Working Group Officers • When carrying out the duties of an officer described in IEEE’s policies and procedures, officers of the Working Group: • a) shall not act: • 1) in bad faith; • 2) to the detriment of IEEE-SA; • 3) to further the interest of any party outside IEEE over the interest of IEEE; or • 4) in a manner that is inconsistent with the purposes or objectives of IEEE, and; • b) shall use best efforts to ensure that participants of the working group conduct themselves in accordance with applicable policies and procedures including, but not limited to, SASB Bylaws 5.2.1. • The officers of the Working Group shall manage the day-to-day operations of the Working Group. The officers are responsible for implementing the decisions of the Working Group and managing the activities that result from those decisions. Jay Holcomb (Itron)

  8. Responsibilities of WG Vice Chair • 3.4.2 Vice Chair(s) • The responsibilities of the Vice Chair(s) shall include: • a) Carrying out the Chair's duties if the Chair is temporarily unable to do so or chooses to recuse himself or herself (i.e., to give a technical opinion) or chooses to delegate specific duties. • b) Being knowledgeable in IEEE standards processes and parliamentary procedures and assisting the Chair in ensuring that the processes and procedures are followed. • c) Being familiar with training materials available through IEEE Standards Development Online. • ---------- Some specifics for the RR-TAG --------------- • Needs to be a member of the IEEE SA. • Declaration of term commitment and affiliation letters to the EC. • Expected to be in attendance at all face to face meetings and most all the teleconferences. • Should consider to attend sunday wireless chair meeting and rules, EC open and EC close meetings during a plenary. • Stand in for the Chair or Secretary if one of them is not able to attend a meeting or call or activity. • e.g. at the Plenary EC opening and closing meetings if the Chair can not make it. • Learn how and be able to update the website and attendance / approved voters process.. • Support the Chair and secretary in general • Including feedback to the chair and secretary on improved processes, e.g. meetings, calls, docs, procedures, etc. • Currently amount of time is not anticipated too much on the day to day basis • Though busier if some research is needed for a topic, help on comments, etc. • Maybe once a month or so. It will vary. • There may be helping/supporting the Chair with prep for the face to faces and occasionally for teleconferences. • Would look at a periodic touch point with the chair depending on activity. Jay Holcomb (Itron)

  9. Congratulations • Want to Congratulate Rich Kennedy for being awarded: • IEEE-SA Standards Medallion • “For being a driving force to achieve the worldwide harmonization of spectrum for IEEE 802TM Wireless Networks (e.g. Wi-Fi).” Jay Holcomb (Itron)

  10. EU items to share • General EU news? • TG28, TG11, TG-UWB are joining up to work this problem. Putting a document together. E.g. do all receive parameters have to be met in all standards? More to it. • Chair of the ETSI group on receivers is getting all the inputs from all the different groups affected; which is most all groups. • There is technical and political issues. • E.g. it is more than the receiver parameters, there is the manufacturers declarations questions also. • Spectrum utilization is the key, not efficiency, so clarity from the RE-D expectations. • There is an ERM workshop coming up on 12 October that will be working on this issue. • Earlier: • Many are questioning the consultant’s input and EC services desk officer concern on leaving to much up to the manufacturer, and why the technical focus, though it should be processes. • Letters are being generated to send to the EC with the concerns. • This is hitting all the different technical and standards groups, e.g. could hit 3GPP even. • There is some discussion if already OJEU standards, may be pulled back. Huge concern Jay Holcomb (Itron)

  11. EU items to share • ETSI – BRAN – meeting #99 – 18-21 Sept. • There is a push to approve the 60 GHz SR doc, next week. It is needed for other activities to move forward. • Earlier: Contributions coming in. • Upper 6GHz band TFES TR 103 612 early draft is out and BRAN TR 103 631 is posted. • ETSI - ERM - TG-11 – meeting #54 – 15-19 Oct. • Nothing new. • Earlier: EN 300 328 (v2.2.1 (2018-04)) will not be published in the OJEU. And, to avoid existence of 2 different versions, the older v2.1.1. maybe withdrawn. Then a NB would be needed. Jay Holcomb (Itron)

  12. EU items -2 • CEPT – ECC SE45 - Next f2f  2-3 October in Maisons-Alfort, Paris (France) • Minutes finally came out last night from the previous meetings. • Incldued the discussions of SE45 and FM57 on UWB. FM57 document 8 has the details. • 6 technical contributions coming in. • The report for all this will not make this year, will slide into first of the 2019. • Earlier: Input papers being worked on for the next meeting, revised simulation results, duty cycle, channelization, etc. • CEPT – ECC FM57 -Next f2f  4 October in Maisons-Alfort, Paris (France) • Call tonight and more calls before October meeting. • Earlier: Minutes are not out yet and a call on 12 Sept. being setup. • FM57(18)007 Draft interim report in response to mandate is available for comment. Jay Holcomb (Itron)

  13. Google Wavier -1 • Latest Google submission did attempt to answer some of our questions. • https://mentor.ieee.org/802.18/dcn/18/18-18-0080-00-0000-google-s-waiver-request-supplement-to-coexist-with-802-11-with-motion-sensing-57-64ghz.pdf • Note: The waiver is to allow the marketing and certification of equipment / production. • Reminder on our 4 Points • Our comments; https://mentor.ieee.org/802.18/dcn/18/18-18-0032-05-0000-google-s-waiver-request-ieee-802-comments-motion-sensing-57-64-ghz.pdf • Sharing is not clear with 100% duty cycle, it is a 10x e.i.r.p. level, 802.11 has LBT, etc. • Google says 10% now, where the new analysis was done with negligible degradation, along with 100% duty cycle showing 8% degradation. Also, the Soli is out side the WiFi channel 75% of the time. • 2. Didn’t test with 802.11ad with single carrier modulation which is the majority of users. (OFDM is more tolerant which is what they did test with.) • In the new analysis, they did with single carrier. • 3. Didn’t test in the same device, like a phone. • In the new analysis they did what they say is atypical close proximity to WiFi client and again with 10% duty cycle there was no negative affects. With 100% duty cycle no harm on Wi-Fi through put 80% to 95% of the time. • 4. Didn’t test with 802.15.3e (which is different from 3c which Google mentions). • IEEE 802.15.3e made some footnotes that it has a closer intended range than the 11ad so concerns are less likely to materialize. Jay Holcomb (Itron)

  14. Google Wavier -2 • In our view, does it resolve some of the concerns that IEEE 802 raised? • Not completely. • The proceeding: • ECFS: https://www.fcc.gov/ecfs/search/filings?proceedings_name=18-70&sort=date_disseminated,DESC • We reviewed Google’s response to us & Facebook’s excellent rebuttal: • https://mentor.ieee.org/802.18/dcn/18/18-18-0080-00-0000-google-s-waiver-request-supplement-to-coexist-with-802-11-with-motion-sensing-57-64ghz.pdf • https://mentor.ieee.org/802.18/dcn/18/18-18-0089-00-0000-google-s-waiver-request-facebook-letter-after-reply-comments-motion-sensing-57-64-ghz.pdf • Again, no one has stepped forward to work on ex parte. • Though we still do not agree with Google’s answers to our comments. • An option is word on street is Google is working on a response to FaceBook. • Learned last night, a joint letter with Google and FaceBook was posted in the FCC filing. • Looks like some compromise / clarity on the request; • Lower EIRP of +13dBm from original request and duty cycle limits of 10% over 33mS. • No concerns or questions by the RR-TAG were brought up after this review. • If no further requests from the group to do an ex parte, after f2f this week, we will move to monitor. Jay Holcomb (Itron)

  15. General Discussion Items -0 • Additional Fixed Service (FS) Protection ex parte • An ex parte filing given to the FCC on July 31st on sharing • https://mentor.ieee.org/802.18/dcn/18/18-18-0097-00-0000-ex-parte-next-data-base-6-ghz-additional-fs-protection-discussion.pdf • The proposal is to add a third database to the current TVWS & CBRS databases. • Automatic Frequency Coordination. • Anyone familiar with the Frankenstein mess of automotive emissions controls knows that a piecemeal approach has a troubled future. Now is the time for us to plan for spectrum management for the next 20 years. • We don’t need to stop current database developments, but must keep an eye to a future where all spectrum is controlled this way • So far: 11y, TVWS, CBRS, this one at 6 GHz, and maybe a 5th at 3.7-4.2GHz? • What are thoughts from all on adding another coordination data base? • A paper is being worked to cover this more completely. • The FCC is looking at 3rd parties to manage the different data bases, so they would not being having to deal with them directly. • Maybe a question on how the ‘services’ are without bound and changes over time. • It does seem early to minimize data bases, need to let the technologies stabilize. Jay Holcomb (Itron)

  16. General Discussion Items -1 • 6 GHz and single voice from IEEE 802. • Should see the NPRM ‘draft’ text 3 weeks before the FCC Open meeting this is on the agenda. (Open meeting dates: 26 Sept, 23 Oct, 15 Nov) • The time frame for comments and reply comments should be in this. • Next step continues on where the 11ax CoEx document goes. • There is a draft of the CoEx document comment resolutions and status: • https://mentor.ieee.org/802-ec/dcn/18/ec-18-0169-00-WCSG-2018-waikoloa-802-11ax-coexistence-comment-status.docx • Plan is to have CoEx document in place by the November Plenary. • If the NPRM comes out before IEEE 802 has a single voice, the .18 chair will call teleconference (s?) to work on the plan for NPRM response. • Here is the link to the document discussed at the July Plenary with several of the EC Chairs, that talks to some options. • https://mentor.ieee.org/802-ec/dcn/18/ec-18-0133-00-00EC-how-can-ieee-802-get-to-a-single-voice-for-6ghz-band.pptx Jay Holcomb (Itron)

  17. General Discussion Items -2 • IEEE EU spectrum management statement • Summary was the IEEE EU should consider using the IEEE SA Intelligent Spectrum Allocation and Management statement: • https://mentor.ieee.org/802.18/dcn/18/18-18-0010-10-0000-sa-use-of-spectrum-draft-position-06dec17.docx • Email sent to GPPC and cc:’d the IEEE EU spectrum group contact. • No reply at this point. Jay Holcomb (Itron)

  18. General Discussion Items -3 • Since July Plenary: • Uganda Consultation Approved and sent to UCC. • The (Uganda) Commission has developed TV White Spaces (TVWS) guidelines to guide its management of the TVWS radio spectrum use in Uganda. • As a stakeholder in the use of the radio spectrum in Uganda, the Commission invites your comments on the proposed guidelines with reference to the topics highlighted in the guideline document. • EC approved: https://mentor.ieee.org/802.18/dcn/18/18-18-0086-04-0000-uganda-tvws-comments-to-guidelines-for-consultation.docx • Ofcom Consultation, RR-TAG approved, EC Ballot done this week • This consultation calls on stakeholders to help us play an important part in shaping the regulations that govern how the world’s radio spectrum is used. It sets out the key issues to be discussed at next year’s World Radiocommunications Conference (WRC-19) – and spells out our early thinking on the outcomes we’d like to achieve. It also explains the engagement process which Ofcom manages in order to allow stakeholders to feed into the development of UK positions for the WRC • RR-TAG approved: . https://mentor.ieee.org/802.18/dcn/18/18-18-0088-03-0000-ofcom-consultation-comments-on-prep-for-wrc19.docx; Jay Holcomb (Itron)

  19. General Discussion Items -4 • FCC – Flexible Use of the 3.7 to 4.2 GHz Band, Order & NPRM • ECFS: https://www.fcc.gov/ecfs/search/filings?proceedings_name=18-122&sort=date_disseminated,DESC • Mentor: https://mentor.ieee.org/802.18/dcn/18/18-18-0076-01-0000-nprm-3-7-4-2ghz-gn-18-122.pdf • The Commission then seeks comment on various proposals for transitioning all or part of the band for flexible use, terrestrial mobile spectrum, with clearing for flexible use beginning at 3.7 GHz and moving higher up in the band as more spectrum is cleared. The Commission also seeks comment on potential changes to the Commission's rules to promote more efficient and intensive fixed use of the band on a shared basis starting in the top segment of the band and moving down the band. To add a mobile, except aeronautical mobile, allocation and to develop rules that would enable the band to be transitioned for more intensive fixed and flexible uses, the Commission encourages commenters to discuss and quantify the costs and benefits associated with any proposed approach along with other helpful technical or procedural details. • Questions were brought up in 802.24 meeting at the plenary and 802.22 at the leadership meeting that Saturday, to watch this one. • NPRM came out in Federal Register on 29 Aug: <click here> • Comments are due on or before October 29, 2018; • Reply comments are due on or before November 27, 2018. • .18 chair sent to .11, .15, .22 and .24 chairs. • If no contributions will plan to move to monitor. Jay Holcomb (Itron)

  20. Jay Holcomb (Itron) Recess • AOB before Recess to Thursday AM1. • We are recessed until Thursday AM1.

  21. Jay Holcomb (Itron) Thursday Agenda • Reminder of IEEE policies we are under. • Attendance server is open. • Remember to state your name, affiliation, employer and/or clients first time you speak. • Need a recording secretary • Items from Tuesday or new. • None • Actions Required • AOB • Adjourn

  22. Actions Required • Outline on spectrum management / multiple data bases, for .18 discussion. • Monitor: • 6 GHz and single voice from IEEE 802. <doc> • Sharing and license-exempt; • Additional Fixed Service (FS) Protection ex parte<doc> • Next Generation Spectrum Management (NGSM) <doc> • 802.11 WNG proposal on Future of Unlicensed Spectrum <doc> • A perspective on regardless of everything we do, the available spectrum has a hard limit <doc> • Including push to bi-directional sharing <doc> • Other: • EU Spectrum Management Statement • FCC NPRM on 3.7-4.2 GHz, any inputs <doc> • Google waiver Jay Holcomb (Itron)

  23. Any Other Business • Note, the November Plenary meeting in Bangkok announcement is out. • Note, do not plan to schedule the Thursday AM2 slot, we have never used it. • If we need a session, will do an Ad Hoc. • Straw Poll • How many people would like to come back to this venue? • Yes -- # • No – # • Like the Social – # • Disliked the Social – # • Did not go to Social – # Jay Holcomb (Itron)

  24. Adjourn • Next teleconference: 27 Sept 2018 – 15:00 – <15:55 ET • Note: No teleconference on 20 September. • Call in info: https://mentor.ieee.org/802.18/dcn/16/18-16-0038-10-0000-teleconference-call-in-info.pptx(or latest) • Note: If the call-in link doesn’t work send the Chair an email right away. • All changes/cancellations will be sent out to the 802.18 list server. • The next face to face meeting of the 802.18 RR-TAG will be at the IEEE 802 Plenary 11-16 Nov 2018 at the, Marriott Marquis Bangkok, Thailand. • Time slots, Tuesday AM2 and Thursday AM1 • Adjourn: • We are the end of our agenda, any objection to Adjourn. • None heard, we are Adjourned at ___:___local time, 13 Sept 2018 • Thank You Jay Holcomb (Itron)

  25. Jay Holcomb (Itron) Thank You • Reference, links to EU sites: • Bran: https://portal.etsi.org/tb.aspx?tbid=287&SubTB=287 • ERM TG-11: https://portal.etsi.org/tb.aspx?tbid=442&SubTB=442 • CEPT SE45: https://cept.org/ecc/groups/ecc/wg-se/se-45/client/introduction/ • CEPT FM57: https://cept.org/ecc/groups/ecc/wg-fm/fm-57/client/introduction/ • OJEU: https://eur-lex.europa.eu/oj/direct-access.html • HS: https://ec.europa.eu/growth/single-market/european-standards/harmonised-standards/ Back up and/or previous slides follow

  26. General Discussion Items -4 • Sharing and license-exempt • A study on feasibility and next steps toward a Next Generation Spectrum Management (NGSM). • https://mentor.ieee.org/802.11/dcn/18/11-18-1386-00-0wng-ngsm-next-generation-spectrum-management.pptx • 802.11 San Diego WGN proposal on Future of Unlicensed Spectrum • https://mentor.ieee.org/802-ec/dcn/18/ec-18-0155-00-00EC-push-to-bi-directional-spectrum-sharing.pptx • A perspective on regardless of everything we do to develop new, better, faster wireless technologies, the available spectrum has a hard limit • https://mentor.ieee.org/802.18/dcn/18/18-18-0060-02-0000-a-future-for-unlicensed-spectrum.pptx • Bi-directional sharing • https://mentor.ieee.org/802-ec/dcn/18/ec-18-0155-00-00EC-push-to-bi-directional-spectrum-sharing.pptx • This came up in the IEEE 802 LeaderCon session in July and the 802.18 chair along with others have an action item to look at this more. Jay Holcomb (Itron)

  27. Motion - FCC Google Wavier ex parte • Motion:Move to approve the ex parte in 18-18/00___r___, response to Google reply comments on request for wavier (FCC ET Docket 18-70) of section 15.255(c)(3) of the FCC rules for their interactive motion sensing in the 57-64 GHz band, to increase the allowed power. For review and approval by the EC for sending to the FCC by _______. The Chair of 802.18 is authorized to make editorial changes as necessary. • Move by: . • Second by: . • Discussion: None • Vote: ___ Yes ___ No ___ Abstain • Motion:Passed Jay Holcomb (Itron)

  28. Ofcom - WRC-19 AIs Consultation • Ofcom Consultation: UK preparations for the World Radiocommunication Conference 2019 (WRC-19) • https://www.ofcom.org.uk/consultations-and-statements/category-1/uk-preparations-wrc-19 • https://mentor.ieee.org/802.18/dcn/18/18-18-0069-01-0000-ofcom-consultation-on-preparations-for-wrc-19.pdf(with some 802.18 comments started.) • https://mentor.ieee.org/802.18/dcn/18/18-18-0088-03-0000-ofcom-consultation-comments-on-prep-for-wrc19.docx • We should focus on AIs from our view point document; 1.12, 1.13, 1.15, 1.16, 9.1.5 and 10. • 1.1 This consultation calls on stakeholders to help us play an important part in shaping the regulations that govern how the world’s radio spectrum is used. It sets out the key issues to be discussed at next year’s World Radiocommunications Conference (WRC-19) – and spells out our early thinking on the outcomes we’d like to achieve. It also explains the engagement process which Ofcom manages in order to allow stakeholders to feed into the development of UK positions for the WRC. • From last week, if we want to send additional AI 10 input, what do we need to do? • The proposal was for Ofcom to not propose any 6 GHz band AIs in WRC-23. • What is happening is there are notable other paths and groups that will cover what was proposed, so not that urgent if IEEE 802 adds or not. We will go to monitor. Jay Holcomb (Itron)

  29. Ofcom - WRC-19 AIs Consultation -2 • From last week, What do we do about question 32 and AI 10? • Proposed Response to begin: "IEEE 802 urges the UK to oppose any attempts to have a new WRC-2023 Agenda Item associated with the 5925-7125 MHz range. Consideration of the 5925-7125 MHz range under a WRC-2023 Agenda Item would be highly disruptive to future planned RLAN deployments / services and would further delay provisions of high-speed internet. In adopting the ECC Work Item (5925-6425 MHz) there was an expectation that spectrum above 6425 MHz may be considered for future RLAN deployments." == followed by proposed TVWS text in 18-88r3 == • With this not in the approved IEEE 802 viewpoints <doc>, • Can add to the view points once we know what to put. • And without an IEEE 802 as a whole single voice on 6GHz yet, • This is a different activity, should we start there? • For question brought up on clarification of ‘oppose’, will work after answering above. Jay Holcomb (Itron)

  30. IEEE 802 – Can we get to a Single Voice on 6GHz?-1 • Word is the FCC NPRM (Notice of Proposed Rulemaking) on 6GHz band should be out before the end of the year, and could be as soon as September. • Comment period could be shorter, tbd. • With that we need to understand in what direction IEEE 802 as a whole should (or should not) respond to the NPRM with. • Reminder: • IEEE P802.11ax – wants this band for spectrum expansion that WiFi needs. • Keep in mind, others, e.g. 3GPP also want the band. • IEEE 802.15.4, UWB, is already in use in the band, and is the band most used around the world for 802.15.4-UWB. • The concern is WiFi interferes with UWB with its very low power. • Recently 802.19 voted on the .11ax CoEx document and it failed. • This is being worked on through the normal IEEE 802 process, to be updated and part upcoming letter ballot, etc. • There are a number of other incumbents in USA and the EU concerned with coexistence. Jay Holcomb (Itron)

  31. IEEE 802 – Can we get to a Single Voice on 6GHz?-2 • Sunday, chairs of 802.11, 802.15, 802.18, 802.19 and others met to discuss this. • Here is a link to what was reviewed, • https://mentor.ieee.org/802-ec/dcn/18/ec-18-0133-00-00EC-how-can-ieee-802-get-to-a-single-voice-for-6ghz-band.pptx (includes comment that in the EU (and most other countries) UWB is a lower priority than WS/RLAN usage) • Next steps • 802.19/802.11ax, will work through the 802.11ax coexistence document through the process so it is updated, passes 802.19 and can be in an upcoming 802.11ax letter ballot. (802.18 will stay involved) • Once the 802.11ax coexistence document is finished up, this will start next phase of defining the voice from IEEE 802 as a whole, that can be used on the NPRM. • Until the NPRM actually comes out, we will not be sure what is in them exactly to know just how to do final comments, assuming we have a direction on voice from 802. • Timing? Until the NPRM is published in the Federal Register, no way to speculate very close the date comments will be due. • Speculating the shortest time frame is the NPRM is published early September with a 30 day comments period. Making them due mid-October between the September Interim and November plenary. • New feedback, Learned this week October FCC open meeting is the latest word of when we may see the NPRM, not September as earlier indications. Jay Holcomb (Itron)

  32. WiFi / UWB Coexistence -1 • IEEE 802.19 and other WG chairs are working on IEEE 802 single voice. • From a high level, could we list out some of the following. • Do not want to get into detail, just high level points to consider to help. • What criteria should be considered? • Power out needed, different for each technology. • Bandwidth considerations. • Channel sense, e.g. LBT. • Incumbent protection. • Interference types, blocks .vs. range decrease. • Operational ranges themselves. • Different modulation types . • Tuning range of UWB (global considerations). • Thursday: • Is there a way to ID that UWB is there and transmitting? Jay Holcomb (Itron)

  33. WiFi / UWB Coexistence -2 • What Use Cases should be considered? • Higher speed (wider BWs) for WiFi users, e.g. streaming video, etc. • Global availability (S. Korea just this week consultation 6 – 10.2 GHz for UWB) • UWB applications - Many (See 15-17/0660), e.g. location is a significant use case. • Where devices are used, height, indoor/outdoor, etc. • Review 15.2 co-existence of WiFi / BT / … • Co-located in a device, and non-co-located. • Thursday: • Nothing new. Jay Holcomb (Itron)

  34. IEEE EU position statement on spectrum management • From earlier teleconferences: • IEEE European Public Policy Position Statement on Spectrum Management • https://mentor.ieee.org/802.18/dcn/18/18-18-0028-01-0000-draft-ieee-european-public-policy-position-statement-on-spectrum-management.pdf (old rev) • We are being asked to review this statement, similar to the one in November, though some focus for the EU. Guidance is to review and comment in detail. • Document 18-18/0028rxx, latest revision is our current review markup. • Please send comments to .18 chair, to integrate, to be reviewed by the TAG. • Becoming clearer the starting premise of the current paper is from several years ago and input is coming in the premise has changed in recent years. • Considering the question on older premise, it has on the statement: • This statement was developed by the IEEE European Public Policy Committee Working Group on ICT and represents the considered judgment of a broad group of European IEEE members with expertise in the subject field. Jay Holcomb (Itron)

  35. IEEE EU Position Statement -2 • Went through 18-18/0028r01 review copy, the remaining sections we have not reviewed and found a couple of specific areas that need clarity. • And brought audience up to speed on point premise of paper is from a few years back and had agreement with those that spoke up. • Some general questions: • Should the IEEE SA (the position statement we reviewed in November and January) and the IEEE EU collaborate on these 2 separate position statements in some fashion? • Then move above them. (.18 should still review) • What was original driver to do the statement? • Who is the general audience it is written for? • As it is, there is a concern if it is sent out and organizations our members are working with, CEPT, BRAN, etc. it will cause confusion, and more. • Request that anyone with specific input to continue to please pass on to the .18 chair, sooner. • .18 chair will cleanup the review revision of the paper (should end up r02) and ask the IEEE 802 chair for further guidance on next steps. Jay Holcomb (Itron)

  36. IEEE EU spectrum management statement • What was sent to the IEEE 802 chair for a short write up on our overall view and what is needed: • In our opinion spectrum policy cannot be based on measuring 3-D occupancy and then enforce corrections. Spectrum policy needs to allow for dynamic sharing and allocation with the technologies available today and coming in the future. In addition, society’s goals are not that all spectrum is occupied in high-value locations, rather that services are available in high-value locations, meeting what users are expecting. • And there is agreement to propose using the SA statement for this need also, as it will work globally. • Discussed even if SA wants to keep separate from the other Operating Units, we still feel this statement could work for the EU (and globally). • Email sent to GPPC and cc: the EU spectrum group contact. • And, nothing at this point. Jay Holcomb (Itron)

  37. A Future For Unlicensed Spectrum – from last week • A perspective on regardless of everything we do to develop new, better, faster wireless technologies, the available spectrum has a hard limit • See: https://mentor.ieee.org/802.18/dcn/18/18-18-0060-02-0000-a-future-for-unlicensed-spectrum.pptx • Will review and discuss • The idea is to cover the entire spectrum in the database, all of it. • Then knowing what frequency range the device is in and geographic location, can manage the users. • Similar idea years back were not fully accepted, though with recent actions, e.g. 6GHz, a data base maybe viewed differently now. • Should look at the CBRS database and what can we learn from it. • This is a long term effort, and need to start to put all the pieces together, before going to regulators. • 3550 filings of interest: • Google October 2017 overall summary • https://ecfsapi.fcc.gov/file/10160477327041/2017-10-16%20Ex%20Parte%20(GN%2012-354%20RM-11788%20RM-11789).pdf • Slide 16 SAS providers & carriers have developed a mutuall satisfactory legal agreement covering confidential data • Appendix A:Wireless Innovation Forum and SAS and CBSD Standards Development • https://ecfsapi.fcc.gov/file/60001854348.pdf Jay Holcomb (Itron)

  38. A Future For Unlicensed Spectrum • A perspective on regardless of everything we do to develop new, better, faster wireless technologies, the available spectrum has a hard limit • See: https://mentor.ieee.org/802.18/dcn/18/18-18-0060-02-0000-a-future-for-unlicensed-spectrum.pptx (more regulatory based) • The most recent document is: 11-18/1055rxx (more standards based) • We reviewed and discussed the latest .11 version for Plenary WNG in San Diego. • The idea is to cover the entire spectrum in the database, all of it. • Then knowing what frequency range the device is in and geographic location, can manage the users. • Similar idea years back were not fully accepted, though with recent actions, e.g. 6GHz, a data base maybe viewed differently now. • A perspective on regardless of everything we do to develop new, better, faster wireless technologies, the available spectrum has a hard limit Jay Holcomb (Itron)

  39. IEEE – not connected and underserved (from last week) • IEEE Connectivity Coalition • Internet Inclusion means that all stakeholders are engaged in the planning and implementation of technology systems; that all potential people impacted can access and have certain rights to understand the implications of the technology and know how to use it safely and ethically; and that with these technologies come more services, tools, increased information and opportunities to expand access for communities around the world. As digital technology is increasingly used for educational, employment, health, commercial and informational purposes, Internet Inclusion is critical for full engagement, participation and opportunity in the social, economic and civic life of society. • This ties into the effort brought up at the Chicago meeting on how to connect the 3.8B people, not connected today. • Stayed tuned as we learn more. • Rich will be talking to Senior Director, Technology Policy and International Affairs on this and what we can do. Jay Holcomb (Itron)

  40. Potential reference document when doing comments • Note: in the 802.19 co-existence <1 GHz meeting it was brought up for IEEE 802 as a whole to put together a document on basic spectrum parameters that would be good for all IEEE 802 standards to co-exist (less interference….) • Actually, need to have this for all IEEE 802 to just work in the spectrum, e.g. BWs needed. Not just coexistence. • Point being that 802.18 can refer to / use when responding to regulators on different consultations, to encourage regulators in general to configure their spectrum to allow all the IEEE 802 standards in a more consistent/friendly way. • For the many in attendance, it was felt many regulators would appreciate at least knowing this. • Additional point to add to the doc, duty cycle is not for the protocol/standard/amendment being discussed, it is a regulation to allow others (and their packet lengths) to have access to the spectrum. Jay Holcomb (Itron)

  41. Fellowship Request • Fellowship request on reaching out to all regulators. • Enhancing Collaboration between IEEE 802 and World Regulators on unlicensed spectrum regulations • https://mentor.ieee.org/802.11/dcn/18/11-18-0580-01-coex-enhancing-collaboration-between-ieee-802-and-world-regulators-on-unlicensed-spectrum-regulations.pptx • Thursday: • A start is to keep in touch with the fellowship attendees. • They are welcome to our meetings and calls. • Could something be added to the IEEE newsletter/communication for the regulators, to answer the news letter input? • Can IEEE be more pro-active with some of the other (e.g. regional) regulators? • The challenge is to ID which we can, and being a volunteer / individual organization, the time and money from the volunteers? • Many regulators don’t have IEEE has a point of contact like they do with WFA or other implementing orgs do. Jay Holcomb (Itron)

More Related