1 / 19

IEEE 802.1 OmniRAN TG November 2015 F2F Meeting Dallas, TX

IEEE 802.1 OmniRAN TG November 2015 F2F Meeting Dallas, TX. 2015-11-12 Max Riegel, Nokia Networks (TG Chair). November 2015 F2F Meeting. Venue: Hyatt Regency Dallas 300 Reunion Boulevard Dallas , Texas, USA, 75207 Meeting room: Moreno A, Atrium level Sessions:

eambrose
Download Presentation

IEEE 802.1 OmniRAN TG November 2015 F2F Meeting Dallas, TX

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 TGNovember 2015 F2F MeetingDallas, TX 2015-11-12 Max Riegel, Nokia Networks (TG Chair)

  2. November 2015 F2F Meeting • Venue: • Hyatt Regency Dallas • 300 Reunion Boulevard Dallas, Texas, USA, 75207 • Meeting room: • Moreno A, Atrium level • Sessions: • Mon, Nov 9th, 16:00-18:00 • Tue, Nov 10th, 16:00-18:00 • Wed, Nov 11th, 16:00-18:00 • Thu, Nov 12th, 10:30-12:30

  3. November 2015 Agenda Graphics

  4. Agenda proposal for November 2015 F2F • Review of minutes • Reports • Review of 802.1CF editor’s draft • Comment resolution • New P802.1CF contributions • Functional design and decomposition • Backhaul representation • SDN Abstraction • Wi-Fi as component of 5G within the scope of P802.1CF • Project planning • Publicity activities • Status report to IEEE 802 WGs • AOB

  5. Instructions for the chair • The 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.

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

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

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

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

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

  11. Discussion items #1 • Call Meeting to Order • Chair called meeting to order on Nov 9th, at 16:05 • Minutes taker: • Walter is taking notes. • Roll Call

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

  13. Agenda for November 2015 F2F • Review of minutes • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0047-00-00TG-sept-2015-f2f-meeting-minutes.docx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0050-00-00TG-sept-29th-2015-confcall-minutes.docx • Reports • 802.11 as component for 5G • Review of 802.1CF editor’s draft • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0035-02-CF00-cf-text-review.pdf • Comment resolution • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0048-01-CF00-comment-resolution-proposals-for-doc-15-0045-01.docx • New P802.1CF contributions • Network Reference Model • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0053-00-CF00-some-detailed-information-for-network-reference-model.pptx • Access network setup • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0042-01-CF00-an-setup-over-unlicensed-band.docx • Data path • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0002-02-CF00-key-concepts-of-data-path.pptx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0055-00-CF00-data-path-functional-description.docx • Fault Diagnosis and Maintenance • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0052-00-CF00-fault-diagnosis-and-maintenance.pptx • Wi-Fi as component of 5G within the scope of P802.1CF • P802.1CF within the scope of 5G • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0054-00-CF00-5g-scope-and-requirements.pptx • Project planning • Publicity activities • Status report to IEEE 802 WGs • AOB

  14. Schedule for November 2015 F2F Monday • Review of minutes • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0047-00-00TG-sept-2015-f2f-meeting-minutes.docx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0050-00-00TG-sept-29th-2015-confcall-minutes.docx • Reports • 802.11 as component for 5G • New edition cf-text-review • New P802.1CF contributions • Network Reference Model • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0053-00-CF00-some-detailed-information-for-network-reference-model.pptx Tuesday • Wi-Fi as component of 5G within the scope of P802.1CF • P802.1CF within the scope of 5G • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0054-00-CF00-5g-scope-and-requirements.pptx Wednesday • Data path • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0002-02-CF00-key-concepts-of-data-path.pptx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0055-00-CF00-data-path-functional-description.docx • Fault Diagnosis and Maintenance • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0052-00-CF00-fault-diagnosis-and-maintenance.pptx Thursday • New P802.1CF contributions • Access network setup • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0042-01-CF00-an-setup-over-unlicensed-band.docx • Review of 802.1CF editor’s draft • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0035-02-CF00-cf-text-review.pdf • Comment resolution • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0048-01-CF00-comment-resolution-proposals-for-doc-15-0045-01.docx • Project planning • Publicity activities • Status report to IEEE 802 WGs • AOB

  15. Discussion items #2 • Review of minutes • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0047-00-00TG-sept-2015-f2f-meeting-minutes.docx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0050-00-00TG-sept-29th-2015-confcall-minutes.docx • No demand for revision was raised. • Reports • 802.11 as component for 5G • Juan Carlos reported about plans and intentions of tutorial #2 the same evening. • Further discussions will come up in WNG, ARCH and 802.11 mid-week plenary. • New edition cf-text-review • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0035-02-CF00-cf-text-review.pdf • Short announcement that another edition of the initial text proposal was made available. • New P802.1CF contributions • Network Reference Model • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0053-00-CF00-some-detailed-information-for-network-reference-model.pptx • Presentation proposes to include in the P802.1CF specification comprehensive attribute sets than currently available in TR069/TR-181 device model 2 for Wi-Fi • Discussion showed that support of comprehensive attribute sets is desirable and required, however the detailed specification of the attributes is in the scope of the projects defining the IEEE 802 technologies. • P802.1CF may provide generic container concept to support comprehensive attribute sets in a common framework. >>Recess at 18:05

  16. Discussion items #3 >>Reconvene on Nov 10that 16:01 • Wi-Fi as component of 5G within the scope of P802.1CF • P802.1CF within the scope of 5G • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0054-00-CF00-5g-scope-and-requirements.pptx • Presentation and discussion showed that P802.1CF might be well suited as the basic document to address the network requirements stated in NGMN 5G whitepaper • However not addressing wide-area high mobility >>Recess at 18:00

  17. Discussion items #4 >>Reconvene on Nov 11that 16:02 • New P802.1CF contributions • Fault Diagnosis and Maintenance • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0052-00-CF00-fault-diagnosis-and-maintenance.pptx • Presentation shows needs and benefits to add a dedicated chapter on Fault diagnostics and maintenance to the Functional Design and Decomposition. • Idea and proposal was well received by group. • Data path • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0002-02-CF00-key-concepts-of-data-path.pptx • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0055-00-CF00-data-path-functional-description.docx • Document provides initial text on data path in Functional Design and Decomposition. • Extensive discussion about whether re-use of Ethernet service types of MEF in P802.1CF is appropriate. • Document requires further amendments and refinements, and re-use of MEF terminology was considered as helpful when similarities exist. >>Recess at 18:00

  18. Discussion items #5 >>Reconvene on Nov 12that 10:30 • New P802.1CF contributions • Access network setup • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0042-01-CF00-an-setup-over-unlicensed-band.docx • Updated text shortly introduced by Yonggang. • Max raised concerns about the used terminology, e.g. Service Provider Network does not exist in the P802.1CF model, and he asked for possibility for offline review of text and resolution of terminology issues with the authors before next conference call. • Review of 802.1CF editor’s draft • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0035-02-CF00-cf-text-review.pdf • Comment resolution • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0048-01-CF00-comment-resolution-proposals-for-doc-15-0045-01.docx • Highlighted issues in current text proposal were discussed and resolved, and Max provided further editorial guidance for the editing of NDS chapter to not lose valuable information. • Project planning • Review of timeline of progressing P802.1CF • Contributions to Dallas meeting indicated that sufficient content for a first editor’s draft may be available after the upcoming interim meeting in January. • Plan confirmed to release first editor’s draft D0.1 for task group ballot after next plenary meeting in March 2016 • Starting task group ballot requires approval by the 802.1 WG – earliest possible date anyhow March 2016 • Conference calls • December 10th, 10:00AM ET • Dial-in details on OmniRAN TG Wiki page on mentorhttps://mentor.ieee.org/omniran/bp/StartPage • Review contributions invited in Nov meeting to conclude on next draft text revision • Another call on Feb 23rd, 10:00AM ET to prepare for March plenary meeting • Approval of conference calls is the only topic for approval by 802.1 closing plenary • Motion was forwarded to 802.1 chair for inclusion into closing plenary slide deck.

  19. Discussion items #6 • Publicity activities • No external publicity activities planned for the upcoming period. Main focus of work is on establishment of first editor draft of P802.1CF. • Status report to IEEE 802 WGs • Chair drafted report and presented proposal for review and approval. Several comments on wording received and adopted to proposed text. • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0058-00-00TG-nov-2015-status-report-to-802-wgs.pptx • Report approved without objections. • AOB • Presentation on informative annex on Converged Cable Access Platform • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0057-00-00TG-distributed-ccap-architectures.docx • Contribution provides interesting background material and may be considered for inclusion into P802.1CF as informational annex. • Update required for formal reasons (cover page) as well as for adding text on alignment of CCAP with P802.1CF architecture and approaches. • Chair announced that he created and uploaded a Word template for creation of contributions to Functional Design and Decomposition. • https://mentor.ieee.org/omniran/dcn/15/omniran-15-0056-00-00TG-docx-template-functional-design.docx • When asking for further discussion needs, no other topics were raised. • Meeting adjourned by chair at 12:30

More Related