1. omniran-15-0011-03-00TG 1 IEEE 802.1 OmniRAN TG March 2015 F2F Meeting 2015-03-09 Max Riegel, Nokia Networks (OmniRAN TG Chair)

2. omniran-15-0011-03-00TG 2 March 2015 F2F Meeting Venue –Hotel Estrel Berlin, Sonnenallee 225 12057 Berlin, Germany Sessions; meeting room –Mon,Mar 9 th, 14:00 - 18:00 Room 30310, EH Wing 3, 3rd Floor Rm 310 –Tue,Mar 10 th, 13:30 - 18:00 ECC Room 5, ECC 2nd Floor –Wed,Mar 11 th, 13:30 - 18:00 Room 30310, EH Wing 3, 3rd Floor Rm 310 –Thu,Mar 12 th, 10:30 - 12:30 Room 30310, EH Wing 3, 3rd Floor Rm 310

3. omniran-15-0011-03-00TG 3 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 “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims –“Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such 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

4. omniran-15-0011-03-00TG 4 Patent Related Links All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: –IEEE-SA Standards Boards Bylaws http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 –IEEE-SA Standards Board Operations Manual http://standards.ieee.org/develop/policies/opman/sect6.html#6.3 http://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.htmlhttp://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 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 https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt

5. omniran-15-0011-03-00TG 5 Call for Potentially Essential Patents If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: –Either speak up now or –Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or –Cause an LOA to be submitted

6. omniran-15-0011-03-00TG 6 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.

7. omniran-15-0011-03-00TG 7 Resources – URLs Link to IEEE Disclosure of Affiliation –http://standards.ieee.org/faqs/affiliationFAQ.htmlhttp://standards.ieee.org/faqs/affiliationFAQ.html Links to IEEE Antitrust Guidelines –http://standards.ieee.org/resources/antitrust- guidelines.pdfhttp://standards.ieee.org/resources/antitrust- guidelines.pdf Link to IEEE Code of Ethics –http://www.ieee.org/web/membership/ethics/code _ethics.htmlhttp://www.ieee.org/web/membership/ethics/code _ethics.html Link to IEEE Patent Policy –http://standards.ieee.org/board/pat/pat- slideset.ppthttp://standards.ieee.org/board/pat/pat- slideset.ppt

8. omniran-15-0011-03-00TG 8 Mar 2015 Agenda Graphics Mon 3/9Tue 3/10Wed 3/11Thu 3/12Fri 3/13 08:00 10:00 802 EC Opening 802.11 WNG Privacy EC SG802.11 Closing 10:30 12:30 802.1 Review Priv PAR 802.11/802.15 Mid-week Plenaries 802.1 Opening Plenary 802 EC Closing 13:30 14:00 15:30 802c LASG802.1 Closing Plenary 16:00 18:00 18:00 Tutorials 22:30 19:30 Privacy EC SG 21:30

9. omniran-15-0011-03-00TG 9 Agenda proposal for January 2015 F2F Review of minutes Reports SDN & NFV status update P802.1CF contributions –Network reference model –Backhaul representation –Fronthaul representation –SDN Abstraction –Functional design and decomposition Project planning Publicity activities Status report to IEEE 802 WGs AOB

10. omniran-15-0011-03-00TG 10 Business#1 Call Meeting to Order –Meeting called to order by chair at 15:00 Minutes taker: – Walter volunteers to take notes Attendence recording –Please sign in IMAT; reciprocal attendence credits given by 802.11 –Currently, IMAT structure is not well aligned with 802.11; Max will talk with Glenn to set up OmniRAN to fit to 802.11 schedules Roll Call NameAffiliationNameAffiliation Max RiegelNokia NetworksHesham ElBakouryHuawei Juan Carlos ZunigaInterdigitalYonggang FangZTE Walter PienciakIEEE SAXuaowu ZhaoZTE Antonio de la OlivaUC3MLu HuangChina Mobile Glenn ParsonsEricsson Charlie PerkinsFuturewei Roger MarksEthAirNet Ass.; ETRI

11. omniran-15-0011-03-00TG 11 Business#2 Approal of agenda –Review of minutes –Reports –SDN & NFV status update –P802.1CF contributions Network reference model Backhaul representation Fronthaul representation SDN Abstraction Functional design and decomposition –Project planning –Publicity activities –Status report to IEEE 802 WGs –AOB Schedule of topics and presentations –SDN & NFV status update Tue, PM2 –… Network reference model Mon, PM2 –… Backhaul representation –… Fronthaul representation –… SDN Abstraction Wed, PM2 –… Functional design and decomposition Tue PM2: Privacy Engineering

12. omniran-15-0011-03-00TG 12 Business#3 Review of minutes –https://mentor.ieee.org/omniran/dcn/15/omniran-15-0007-00-00TG-january-2015-f2f-meeting-minutes.docxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0007-00-00TG-january-2015-f2f-meeting-minutes.docx –https://mentor.ieee.org/omniran/dcn/15/omniran-15-0010-00-00TG-february-10th-confcall-meeting-minutes.docxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0010-00-00TG-february-10th-confcall-meeting-minutes.docx –No comments raised to either of the minutes. Reports – Introduction of OmniRAN to IEEE 1904.2 (http://www.ieee1904.org/index.shtml)http://www.ieee1904.org/index.shtml http://www.ieee1904.org/2/meeting_archive/2015/02/tf2_1502_elbakoury_3.pdf Hesham introduced his presentation to 1904.2 explaining that 1904.2 is seeking for network model to describe its functionality in a more generic way OmniRAN model may fit as both efforts are addressing networks with Ethernet user plane Questions regards operator approval and operator involvement were answered –Participants affiliated with operators have been participated in the establishment of P802.1CF and are participating in the discussions. –Operators may participate in the approval process of the specification by following the usual IEEE SA procedures. However, OmniRAN is aimed for a generic approach for all kind of access networks including home, enterprise and operator. Therefore its not directed only for operators. –Introduction of OmniRAN to WBA (http://www.wballiance.com/)http://www.wballiance.com/ https://mentor.ieee.org/omniran/dcn/15/omniran-15-0012-00-00TG-omniran-p802-1cf-introduction-to-wba.docx Max provided some background information about the WBA project, to which the OmniRAN description was contributed. The presented document is a revision of an initial contribution addressing comments from WBA on relation to generic SDN models, applicability and mapping of reference points to Wi-Fi hotspot networks, and usability despite keeping the IP layer out of scope. SDN & NFV status update –SDN Practice of China Mobile https://mentor.ieee.org/omniran/dcn/15/omniran-15-0016-00-wsdn-sdn-practice-of-china-mobile.pdf Presentation introduced deployment of SDN within the network of CMCC and raised the question, whether OmniRAN would fill the need for models for access, backhaul and datacenter networks. The chair responed that OmniRAN will fully address the missing model for access and potentially also for major portions of backhaul as P802.1CF embedds backhaul as a opaque container into its access network model. CMCC is welcome to contribute its requirements and specification proposals to the P802.1CF project –ONF update by Charlie Perkins https://mentor.ieee.org/omniran/dcn/15/omniran-15-0021-00-CF00-onf-wmwg-update.pptx Charlie provided an update on ONF explaining the current shift of focus and reorganization as consequence that OpenFlow has not been deployed yet in any real network. Furthermore one of the founders publically explained that OpenFlow is not well suited for carrier networks due to its origin in the data center networking.

13. omniran-15-0011-03-00TG 13 Business#4 P802.1CF contributions –Network reference model https://mentor.ieee.org/omniran/dcn/15/omniran-15-0008-02-CF00-nrm-refinements.pptx –No final conclusion about the content of the R8c/R1c reference point in relation to the R1d reference point What functionality belongs to the ‘data path’ reference point? –Agreement reached that R1 and R3 should become symmetric, as both may be either wired or wireless No conclusion, which label should be used for R3c; group did not like the idea to introduce 2digit reference point indices, i.e. R10c https://mentor.ieee.org/omniran/dcn/15/omniran-15-0014-00-CF00-revision-proposal-of-omniran-14-0083.docx –Edits presented to the group, but no final conclusion reached as no conclusion reached neither for treating the reference points between TEC – ANC – CNC, nor on replacement of term ‘Core Network’ –Introductory section appreciated, as well as presentation of less variations. More details required on treating control interfaces as well as definition of functional content of data path interfaces. https://mentor.ieee.org/omniran/dcn/15/omniran-15-0013-00-CF00-r9c-reference-point-discussion.pptx –Usage of ‘Core network’ for the endpoint of the data path leads to ambiguities regards location of CIS Chair proposed to look for other term replacing ‘Core Network’, e.g. by ‘Network Service’ –It remains unclear to which 802.19.1 interface the R9c reference point refers. Further clarifications necessary. Hesham discussing MSO architectural alignment –https://mentor.ieee.org/omniran/dcn/15/omniran-15-0017-00-CF00-distributed-access-architectures.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0017-00-CF00-distributed-access-architectures.pptx –P802.1CF not directly applicable due to non-IEEE 802 Ethernet transport, but different split models can easily modeled by the P802.1CF network reference model Backhaul representation –Fronthaul representation No contributions

14. omniran-15-0011-03-00TG 14 Business#5 P802.1CF contributions –SDN Abstraction https://mentor.ieee.org/omniran/dcn/15/omniran-15-0019-00-CF00-omniran-sdn-chapter- contribution-slides.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0019-00-CF00-omniran-sdn-chapter- contribution-slides.pptx https://mentor.ieee.org/omniran/dcn/15/omniran-15-0018-00-CF00-omniran-sdn-chapter- contribution.docxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0018-00-CF00-omniran-sdn-chapter- contribution.docx –Introduced by Antonio –More comprehensive review required for text proposal –Functional design and decomposition https://mentor.ieee.org/omniran/dcn/15/omniran-15-0015-00-CF00-privacy-engineered-access- network.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0015-00-CF00-privacy-engineered-access- network.pptx –Presentation was well received and led to discussion, how this proposal relates to the aims of the PRIV ECSG to establish generic privacy efforts in each and any IEEE 802 standard –JC asked for presentation in PRIV ECSG to show other participants how individual projects may address privacy issues. –There was animous agreement that P802.1CF should follow the proposed procedure, in particular as necessary work can be added towards the end of the project within an annex. https://mentor.ieee.org/omniran/dcn/14/omniran-14-0078-02-CF00-updated-text-for-an- setup.docxhttps://mentor.ieee.org/omniran/dcn/14/omniran-14-0078-02-CF00-updated-text-for-an- setup.docx –Yonggang presented the new revision of the text on access network set-up. –New revision follows the generic chapter structure but still exposes some repeated material on the network reference model. –No conclusion was reached on the scope of the section. It was raised that AN setup may comprise much more than just dynamic spectrum assignment. –Furthermore extensive discussions took place about the mapping of 802.19.1 on the NRM without final conclusion.

15. omniran-15-0011-03-00TG 15 Business#6 Project planning –Compile first draft at May Interim (May 20 th -21 st ) –2 conference calls in preparation May 8 th, 10am; April 16 th, 10am –1 conference call between May and July June 30 th, 10am Publicity activities –OmniRAN introduction to WBA https://mentor.ieee.org/omniran/dcn/15/omniran-15-0012-00-00TG-omniran-p802-1cf-introduction-to-wba.docx –Work towards informative annex on mapping of P802.1CF to real networks Wi-Fi Hotspot networks MSO architectures DSL network Virtualized networks (e.g. China Mobile model) –Get OmniRAN listed on sdn.ieee.org –Set up a wiki page listing public references to OmniRAN (articles, papers) Status report to IEEE 802 WGs –https://mentor.ieee.org/omniran/dcn/15/omniran-15-0020-00-00TG-mar-2015-report-to-802wgs.pptxhttps://mentor.ieee.org/omniran/dcn/15/omniran-15-0020-00-00TG-mar-2015-report-to-802wgs.pptx –Agreed by group AOB –none Adjourn –Adjourned at 12:10