1 / 20

IEEE 802.1 OmniRAN TG July 2016 F2F Meeting San Diego, CA

IEEE 802.1 OmniRAN TG July 2016 F2F Meeting San Diego, CA. 2016-07-27 Max Riegel, Nokia (TG Chair). July 2016 F2F Meeting. Venue: Manchester Grand Hyatt 1 Market Place San Diego, CA USA Information Tel: +1 619-232-1234 Meeting room: Mon, Tue, Wed, Thu: Hillcrest C Sessions:

eiler
Télécharger la présentation

IEEE 802.1 OmniRAN TG July 2016 F2F Meeting San Diego, CA

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.1 OmniRAN TGJuly 2016 F2F MeetingSan Diego, CA 2016-07-27 Max Riegel, Nokia (TG Chair)

  2. July 2016 F2F Meeting • Venue: • Manchester Grand Hyatt • 1 Market Place San Diego, CA USA Information Tel: +1 619-232-1234 • Meeting room: • Mon, Tue, Wed, Thu: Hillcrest C • Sessions: • Mon, Mar 25th, 16:00-18:00 • Tue, July 26th, 13:30-15:30 special session on 5G • Tue, Mar 26th, 16:00-18:00 • Wed, Mar 27th, 16:00-18:00 • Thu, Mar 28th, 10:30-12:30

  3. Agenda proposal for July 2016 F2F • Review of minutes • Reports • Review of 802.1CF-D0.1 editor’s draft • Contributions addressing issues of 802.1CF–D0.1 • Revised and new P802.1CF contributions • Contributions proposing new content • Plan for 802.1CF-D0.2 draft • Bug fixes • New content • Timeline and plan for initial TG ballot • Project planning • Timeline • External reviewers of 802.1CF-D0.2 • Contributions to 5G SC • Status report to IEEE 802 WGs • AOB

  4. July 2016 Agenda Graphics

  5. 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. 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 Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 • IEEE-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 patcom@ieee.org 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

  7. 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 Call for Potentially Essential Patents

  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 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.

  9. Link to IEEE Disclosure of Affiliation http://standards.ieee.org/faqs/affiliationFAQ.html Links to IEEE Antitrust Guidelines http://standards.ieee.org/resources/antitrust-guidelines.pdf Link to IEEE Code of Ethics http://www.ieee.org/web/membership/ethics/code_ethics.html Link to IEEE Patent Policy http://standards.ieee.org/board/pat/pat-slideset.ppt Resources – URLs

  10. Business #1 • Call Meeting to Order • Chair called meeting to order at 16:04 • Minutes taker: • Wang Hao is taking notes. • Roll Call

  11. 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 Nothing brought up. Call for Potentially Essential Patents

  12. Agenda for March 2016 F2F • Review of minutes • Reports • Review of 802.1CF-D0.1 editor’s draft • Contributions addressing issues of 802.1CF–D0.1 • Revised and new P802.1CF contributions • Contributions proposing new content • Plan for 802.1CF-D0.2 draft • Bug fixes • New content • Timeline and plan for initial TG ballot • Project planning • Timeline • External reviewers of 802.1CF-D0.2 • Contributions to 5G SC • Status report to IEEE 802 WGs • AOB

  13. Schedules • Mon • Revised and new P802.1CF contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-01-CF00-an-setup-over-unlicensed-band.docx • Tue • Review of minutes • Reports • Revised and new P802.1CF contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0042-00-CF00-text-proposal-for-monitoring-and-accounting.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0043-00-CF00-key-concepts-of-authorization-qos-and-policy-control.pptx • Wed • Review of 802.1CF-D0.1 editor’s draft • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0044-00-CF00-omniran-d0-1-comments.xlsx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0046-00-CF00-p802-1cf-d0-1-comments.xls • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0048-00-CF00-p802-1cf-d0-1-comments.xlsx • Revised and new P802.1CF contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0047-00-CF00-functional-design-association-and-disassociation.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-00-CF00-network-function-virtualization.docx • Thu • Revised and new P802.1CF contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0013-01-CF00-chapt-7-4-authentication-functional-description.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0052-00-CF00-functional-description-authorization-qos-policy-control.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0042-01-CF00-text-proposal-for-monitoring-and-accounting.docx • Plan for 802.1CF-D0.2 draft • Bug fixes • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0052-00-CF00-functional-description-authorization-qos-policy-control.docx • New content • Timeline and plan for initial TG ballot • Project planning • Timeline • External reviewers of 802.1CF-D0.2 • Contributions to 5G SC • Status report to IEEE 802 WGs • AOB

  14. Business #2 • Revised and new P802.1CF contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-01-CF00-an-setup-over-unlicensed-band.docx • Text proposal for section 7.1.4 Network initialization, which was uploaded shortly after the last conference call, was reviewed and terminology was jointly cleaned up to align with the definitions introduced in the latest revision of the NRM. • According to the agreement in the Budapest meeting, text for section 7.1.5 Network instantiation was removed and the text ready for inclusion into 7.1.4 of the next draft D0.2 was uploaded to mentor under https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-02-CF00-an-setup-over-unlicensed-band.docx • Discussion about the future location of the text proposed for 7.1.5 led to the conclusion to extend the scope of chapter 8 to ‘Network virtualization functions’ with subsections 8.1 ‘SDN functional decomposition’, 8.2 ‘Network Function Virtualization’, and 8.3 ‘Network instantiation’

  15. Business #3 • Review of minutes • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0040-00-00TG-jun-2016-confcall-minutes.docx • No comments raised on the minutes • Reports • Status and plans 5G SC • https://mentor.ieee.org/802-ec/dcn/16/ec-16-0112-00-5GSG-5g-sc-opening-status-for-ec.pdf • https://mentor.ieee.org/802-ec/dcn/16/ec-16-0094-06-5GSG-proposed-draft-report-ieee-802-ec-5g-imt-2020-sc.pptx • Chair provided short overview about 5G SC activities during the week as well as a verbal update on the outcome of the OmniRAN special session on WP5A. • IEEE SDN Whitepaper • http://sdn.ieee.org/images/files/pdf/towards-5g-software-defined-ecosystems.pdf • Chair shortly introduced the white paper and asked for review by the group. • No other reports

  16. Business #4 • Revised and new P802.1CF contributions, cont. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0042-00-CF00-text-proposal-for-monitoring-and-accounting.docx • Proposed text was reviewed and several small issues were detected which are up for correction by Wang Hao. • Overall the text looked fine and seems to be ready for inclusion when the issues are corrected. A revised version was invited and shortly reviewed in the session on Thursday. All issues were resolved. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0042-01-CF00-text-proposal-for-monitoring-and-accounting.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0043-00-CF00-key-concepts-of-authorization-qos-and-policy-control.pptx • Max presented his initial thoughts, which only addressed the very basic features of QoS and policy control. • Most of the content was agreed by the group, however some of the more advanced features for dynamic service flow management caused discussions and did not yet lead to fully aligned views. • Max will create a text contribution until latest the Thursday session, which will be reviewed for inclusion into D0.2. Recommendation was given to focus mainly on the introductory aspects.

  17. Business #5 • Review of 802.1CF-D0.1 editor’s draft • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0044-00-CF00-omniran-d0-1-comments.xlsx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0046-00-CF00-p802-1cf-d0-1-comments.xls • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0048-01-CF00-p802-1cf-d0-1-comments.xlsx • The comments were combined into a common working document. All comments were reviewed and resolved. The conclusion of the review of the D0.1 draft is captured in • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0050-01-CF00-d0-1-collected-comments-resolved.xlsx • There were two contributions attached to the comments of Wang Hao, which were both accepted. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0049-00-CF00-comments-resolution-for-fdm-chapter.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0051-00-CF00-comments-resolution-for-fdm-configuration.docx • Revised and new P802.1CF contributions, cont. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0047-00-CF00-functional-design-association-and-disassociation.docx • Max introduced his proposed text on association, which is mainly aligned to the 802.11 behavior. In a subsequent effort the difference of the IEEE 802 technologies to the described behavior has to be documented in the ‘Mapping to IEEE 802 section’.

  18. Business #6 • Revised and new P802.1CF contributions, cont. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-00-CF00-network-function-virtualization.docx • The proposed text was presented and a number of issues were detected during the review. • In particular the figures in the contribution hardly fit to the P802.1CF design and structure. • During an ad-hoc session an updated version of the contribution was jointly edited and the figures cleaned up. The output of the effort was regarded as appropriate for inclusion into the draft 0.2 • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-02-CF00-network-function-virtualization.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0052-00-CF00-functional-description-authorization-qos-policy-control.docx • Max presented his proposed text based on the content and outcome of the presentation on Tuesday. The text focuses on the generic concepts and does not contain detailed procedures which raised contentious discussions on Tuesday. No issues were detected in the text and the document was accepted for inclusion into draft 0.2 • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0013-01-CF00-chapt-7-4-authentication-functional-description.docx • Max went through the document and introduced the high level approach to address the topic. Discussions came up on some of the stated requirements and Max invited to submit comments, if requirement statements have to be modified. Adoption of the text to the draft 0.2 was agreed.

  19. Business #7 • Plan for 802.1CF-D0.2 draft • Bug fixes • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0050-01-CF00-d0-1-collected-comments-resolved.xlsx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0051-00-CF00-comments-resolution-for-fdm-configuration.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0049-00-CF00-comments-resolution-for-fdm-chapter.docx • New content • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-02-CF00-network-function-virtualization.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-02-CF00-an-setup-over-unlicensed-band.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0042-01-CF00-text-proposal-for-monitoring-and-accounting.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0052-00-CF00-functional-description-authorization-qos-policy-control.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0013-01-CF00-chapt-7-4-authentication-functional-description.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0047-00-CF00-functional-design-association-and-disassociation.docx • Timeline and plan for initial TG ballot • TG ballot start on Aug 9th, end on Sept 8th

  20. Business #8 • Project planning • Timeline • Plan to have P802.1CF roughly complete in Jul 2016 was met. The begin of the WG ballot and SB was postponed by one meeting to allow for a recirculation in the TG balloting. • External reviewers of 802.1CF-D0.2 • Announcement to IEEE-IETF coordination will be done to allow IETF to participate in ballot • September interim meeting location • Warsaw, PL; motion drafted and submitted to WG • Plans for York • Single day session on Sept 12th to meet with commenters from 802.1 • Contributions to 5G SC • Special meeting took place on Tuesday • Report amended to the meeting slides and presented in 5G SC meeting on Tuesday evening • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0045-01-00TG-july-26-special-session-on-5g-sc-action-a.pptx • Special session planned for Warsaw to progress Industry Connection activities for Action A • Status report to IEEE 802 WGs • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0053-00-00TG-jul-2016-report-to-802-wgs.pptx • AOB • Nothing brought up • Adjourned by chair at 12:40pm

More Related