March 2016 IEEE 802.1 OmniRAN TG F2F Meeting in Macau

omniran-16-0015-01-00TG IEEE 802.1 OmniRAN TG March 2016 F2F Meeting Macau, CN 2016-03-17 Max Riegel, Nokia (TG Chair) 1

omniran-16-0015-01-00TG March 2016 F2F Meeting Venue: Sands Venetian Macao Hotel Estrada da Baia de Nossa Senhora da Esperanca, Macau Tel: +853 2882 8888 Meeting room: Mon, Tue, Wed, Thu: Milan 2102 Sessions: Mon, Tue, Wed, Thu, Mar 14th, Mar 15th, Mar 16th, Mar 17st, 16:00-18:00 16:00-18:00 16:00-18:00 10:30-12:30 2

omniran-16-0015-01-00TG Agenda proposal for March 2016 F2F Review of minutes Reports New P802.1CF contributions Fault diagnostics and maintenance Functional design and decomposition Deployment scenarios Representing access network virtualization in P802.1CF Models, approaches Network reference model amendments Review of 802.1CF editor s draft Comment resolution Wi-Fi as component of 5G within the scope of P802.1CF Project planning Status report to IEEE 802 WGs AOB 3

omniran-16-0015-01-00TG March 2016 Agenda Graphics Mon 3/14 802 WGs Opening Tue 3/15 802.11 WNG Wed 3/16 802.11 ARC Thu 3/17 Fri 3/18 802.11 Closing 08:00 10:00 IEEE 802.1 Opening Plenary 10:30 802.11/802.15 Mid-week Plenaries OmniRAN closing 12:30 13:30 IEEE 802.1 closing plenary 15:30 16:00 OmniRAN opening 18:00 19:30 5G SC 5G SC 4

omniran-16-0015-01-00TG 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. 5

omniran-16-0015-01-00TG 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

omniran-16-0015-01-00TG 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 IEEE-SA Standards Board Operations Manual 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.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

omniran-16-0015-01-00TG 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 8

omniran-16-0015-01-00TG 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

omniran-16-0015-01-00TG Resources URLs 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 10

omniran-16-0015-01-00TG Discussion items #1 Call Meeting to Order Chair called meeting to order at 16:05 Minutes taker: Walter is taking notes. Roll Call Name Affiliation Name Affiliation Max Riegel Nokia Networks Liang Jin Spirent Comm. Walter Pienciak IEEE Fulei Liu ZTE Juan Carlos Zuniga Interdigital Roger Marks EthAirnet Inc. Yonggang Fang ZTE TX Hyeong-Ho Lee ETRI Patrick Slaats IEEE SA Richard Burbidge 3GPP Glenn Parsons Ericsson Philippe Reininger 3GPP Wang Hao Fujitsu Sasha Sirotkin 3GPP 11

omniran-16-0015-01-00TG 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 Nobody spoke up. 12

omniran-16-0015-01-00TG Agenda for March 2016 F2F Review of minutes Reports New P802.1CF contributions Fault diagnostics and maintenance https://mentor.ieee.org/omniran/dcn/16/omniran-16-0012-01-CF00-ethernet-oam-survey-and-introducing- nms.pptx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and-management-in-ieee-802- 11.pptx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-00-CF00-nms-architectural-considerations.pptx Functional design and decomposition Deployment scenarios https://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptx Representing access network virtualization in P802.1CF Models, approaches https://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0017-01-CF00-nfv-for-omniran.pptx Network reference model amendments Review of 802.1CF editor s draft Next steps Wi-Fi as component of 5G within the scope of P802.1CF Presentation and discussion with 3GPP on LWA and LWIP https://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptx Project planning Status report to IEEE 802 WGs AOB 13

omniran-16-0015-01-00TG Schedules Mon Fault diagnostics and maintenance https://mentor.ieee.org/omniran/dcn/16/omniran-16-0012-01-CF00-ethernet-oam-survey-and-introducing-nms.pptx Representing access network virtualization in P802.1CF https://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptx Tue Representing access network virtualization in P802.1CF https://mentor.ieee.org/omniran/dcn/16/omniran-16-0017-01-CF00-nfv-for-omniran.pptx Deployment scenarios https://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptx Presentation and discussion with 3GPP on LWA and LWIP https://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptx Wed Review of minutes Jan https://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-01-00TG-jan-2016-f2f-meeting-minutes.docx Feb https://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docx Reports Fault diagnostics and maintenance https://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and-management-in-ieee-802-11.pptx Thu https://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-00-CF00-nms-architectural-considerations.pptx Review of 802.1CF editor s draft Discussion of way forward Project planning Status report to IEEE 802 WGs AOB 14

omniran-16-0015-01-00TG Discussions #1 Fault diagnostics and maintenance https://mentor.ieee.org/omniran/dcn/16/omniran-16-0012-01- CF00-ethernet-oam-survey-and-introducing-nms.pptx Wang Hao walking through his presentation on 802.3ah, 802.1ag, 802.11k and 802.11v architecture and capabilities. Functional similarities between wired and wireless approaches becoming visible. Considers adaptation of SS towards NM. Representing access network virtualization in P802.1CF https://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00- CF00-access-network-virtualization-nrm.pptx Max presents initial thoughts on adoption of NRM for virtualized networks NRM represents an instance of a virtual network with CIS acting as common interface towards shared resources Concept of network slicing with NRM representing one virtual network instance well received by the group. Group invites text contribution on amendment to Chapter 6 (NRM) describing the presented approach for network virtualization. 15

omniran-16-0015-01-00TG Discussions#2 Representing access network virtualization in P802.1CF https://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptx Yonggang explained idea of Network Function Virtualization for P802.1CF Discussion on clarification of ambiguities in presentation on terminology, definition of network functions in the context of P802.1CF and location of NFV in the network reference model Revision of presentation with more comprehensive explanation requested to allow evaluation and verification of proposals. There seems to be close relations to SDN concepts hinting to integration of NFV with SDN chapter. Deployment scenarios https://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptx Max went through small presentation showing the operational assumptions of P802.1CF Basic operational model assumes that operation of Access Network is distinct from Subscription Service and Access Router. Max highlighting that distinct operators have distinct network management systems, i.e. network management of Access Network resides within the Access Network Operator Yonggang claiming that a single operator may operate access network, subscription service and access router. Max agrees that this would be possible but strongly recommends to reflect only the distinct model in the P802.1CF specification, potentially with some informative annex to show the variety of models, which can be supported by the P802.1CF. Presentation and discussion with 3GPP on LWA and LWIP https://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptx Richard and Philippe interactively going through the slides explaining the basic assumptions and solutions of aggregation of LTE radio frames over WLAN in downlink direction. Aggregation is controlled by the eNB taking into account a number of radio parameters of WLAN AP. Network interface of WLAN access to be assumed either at a WLAN controller or at an AP. 3GPP does not make assumptions about implementation of WLAN access, but it seems that WT more likely relates to a WLC. Some ambiguities detected in control flow between 3GPP and WLAN. WLAN does not know about reservation of resources for a STA before association. Impression that P802.1CF specification may help designing of interworking solutions between 3GPP and IEEE 802. OmniRAN offered to send more information about P802.1CF to 3GPP RAN when the specification is more complete and mature. 16

omniran-16-0015-01-00TG Discussions #3 Review of minutes Jan https://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-01-00TG-jan-2016-f2f-meeting- minutes.docx Revised version created and uploaded with corrected affiliation of Yonggang Fang https://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-02-00TG-jan-2016-f2f-meeting-minutes.docx Feb https://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docx Revised version created and uploaded with corrected affiliation of Yonggang Fang https://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docx Reports Max reported about the P802.1CF presentation to 5G SC based on material created in OmniRAN in November 2015 Concluding slide on cost and benefits caused discussions what would be needed to cover the network aspects for the various options IMT 2020 application would be feasible with some profiling to P802.1CF, however IEEE 5G would require comprehensive network specification likely causing efforts >> 100 SY. Fault diagnostics and maintenance https://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and- management-in-ieee-802-11.pptx Wang Hao presented various options and thoughts for mapping network management and monitoring to the NRM. In particular there was no common view on the options for the interface between the Element Managers and the Network Management. Much less concerns were expressed in the discussions on the concept of a set of functions. No conclusion could be reached on the location of the NM in the NRM. The presented location in the SS was seen as inappropriate. 17

omniran-16-0015-01-00TG Discussions #4 https://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-00-CF00-nms- architectural-considerations.pptx Max presented slides and explained that P802.1CF has to focus on the network management only of the access network. An additional slide was added after slide 8 to clarify NMS arrangements of access network and IP service operation , showing that in the generic case NMS of access network is independent of NMS of IP service operation It was agreed that an operator may combine NMS of access network and IP service operation, when owning both access and IP service parts. But for the generic case the NMS are separated. Discussion of option 1 versus option 2 for the location of the NM led to unanimous support for adopting option 1 to the NRM Introducing a dedicated functional unit containing the network management functions allows for more easy representation of the IEEE 802 managed objects work Agreement was reached on a revision of the NRM exposing NM as an additional function next to CIS connected to the ANC, which contains the EM. Reference points will be slightly renumbered to maintain meaningful assignments Max will create a text proposal of the amended NRM for approval in the upcoming OmniRAN TG conference call The updated slides were uploaded to mentor under https://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-01-CF00-nms-architectural- considerations.pptx 18

omniran-16-0015-01-00TG Discussions #5 Review of 802.1CF editor s draft Discussion of way forward Next revision to be created after the May interim meeting with hopefully much more content merged in Amendments to NRM will be discussed in next conference call to create stable foundation for further text on function description When Antonio would be able to attend Budapest meeting, SDN chapter would be thoroughly reviewed and revised Open comment resolution from Jan F2F will be concluded with Yonggang enabling to participate remotely Project planning Project timeline quite stable, but dependency on amount of content, which can be adopted during/after Budapest meeting 2 conference calls (April 19th , June 21st) planned until July plenary Difficult w/ participants from California and China: 9:30AM ET, 90mins Status report to IEEE 802 WGs Drafted, presented, revised and uploaded to mentor under https://mentor.ieee.org/omniran/dcn/16/omniran-16-0022-00-00TG-mar-2016-status- report-to-802wgs.pptx AOB None Meeting adjourned by chair at 12:35 19

omniran-16-0015-01-00TG IEEE 802.1 OmniRAN TG Motion for 802.1 Closing Plenary 2016-03-17 20

omniran-16-0015-01-00TG Motion Approve OmniRAN TG conference calls on: April 19th, 09:30 AM ET, 90mins June 21st, 09:30 AM ET, 90mins Agenda and call-in details will be made available on the 802.1 mailing list and on https://mentor.ieee.org/omniran/bp/StartPage Moved: Max Riegel, Second: Walter Pienciak 21

omniran-16-0015-01-00TG Motion 802.1 instructs the Editor for P802.1CF (Walter Pienciak) to prepare drafts for Task Group balloting. Proposed: Max Riegel Second: Walter Pienciak For____Against____Abstain____ 22