IEEE 802.1 OmniRAN TGMarch 2016 F2F MeetingMacau, CN
Venue:Sands Venetian Macao HotelEstradada Baia de Nossa Senhora da Esperanca,MacauTel: +853 2882 8888Meeting room:Mon, Tue, Wed, Thu: Milan 2102Sessions:Mon, Mar 14th, 16:00-18:00Tue, Mar 15th, 16:00-18:00Wed, Mar 16th, 16:00-18:00Thu, Mar 17st, 10:30-12:30
March 2016 Agenda Graphics
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 presentationAdvise 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 standardAny 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.
All participants in this meeting have certain obligations under the IEEE-SA Patent Policy.Participants [Note:Quoted text excerpted from IEEE-SA Standards Board Bylawssubclause6.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 groupEarly identification of holders of potential Essential Patent Claims is strongly encouragedNo duty to perform a patent search
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#6IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/develop/policies/opman/sect6.html#6.3Material about the patent policy is available athttp://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 visithttp://standards.ieee.org/about/sasb/patcom/index.htmlThis slide set is available athttps://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt
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 orProvide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible orCause an LOA to be submitted
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 focusDon’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.---------------------------------------------------------------SeeIEEE-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.
Call Meeting to OrderChair called meeting to order at 16:05Minutes taker:Walter is taking notes.Roll Call
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 orProvide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible orCause an LOA to be submittedNobody spoke up.
Review of minutesReportsNew P802.1CF contributionsFault diagnostics andmaintenancehttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0012-01-CF00-ethernet-oam-survey-and-introducing-nms.pptxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and-management-in-ieee-802-11.pptxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-00-CF00-nms-architectural-considerations.pptxFunctional design and decompositionDeployment scenarioshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptxRepresenting access network virtualization in P802.1CFModels, approacheshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0017-01-CF00-nfv-for-omniran.pptxNetwork reference model amendmentsReviewof 802.1CF editor’s draftNext stepsWi-Fi as component of 5G within the scope of P802.1CFPresentation and discussion with 3GPP on LWA and LWIPhttps://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptxProject planningStatus report to IEEE 802 WGsAOB
Schedules
MonFaultdiagnostics and maintenancehttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0012-01-CF00-ethernet-oam-survey-and-introducing-nms.pptxRepresenting access network virtualization in P802.1CFhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptxTueRepresenting access network virtualization in P802.1CFhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0017-01-CF00-nfv-for-omniran.pptxDeployment scenarioshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptxPresentationand discussion with 3GPP on LWA and LWIPhttps://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptxWedReview ofminutesJanhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-01-00TG-jan-2016-f2f-meeting-minutes.docxFebhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docxReportsFaultdiagnostics and maintenancehttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and-management-in-ieee-802-11.pptxThuhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0021-00-CF00-nms-architectural-considerations.pptxReviewof 802.1CF editor’s draftDiscussion of way forwardProjectplanningStatus report to IEEE 802 WGsAOB
Representing access network virtualization in P802.1CFhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0016-00-CF00-access-network-virtualization-nrm.pptxYonggangexplained idea of Network Function Virtualization for P802.1CFDiscussion 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 modelRevision 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 scenarioshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0020-00-CF00-nrm-operational-arrangements.pptxMax went through small presentation showing the operational assumptions of P802.1CFBasic 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 OperatorYonggangclaiming 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.Presentationand discussion with 3GPP on LWA and LWIPhttps://mentor.ieee.org/802.11/dcn/16/11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip.pptxRichard 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 theeNBtaking 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.OmniRANoffered to send more information about P802.1CF to 3GPP RAN when the specification is more complete and mature.
Discussions #3
Reviewof minutesJanhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-01-00TG-jan-2016-f2f-meeting-minutes.docxRevised version created and uploaded with corrected affiliation of Yonggang Fanghttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0010-02-00TG-jan-2016-f2f-meeting-minutes.docxFebhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docxRevised version created and uploaded with corrected affiliation of Yonggang Fanghttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0014-01-00TG-feb-2016-confcall-minutes.docxReportsMax reported about the P802.1CF presentation to 5G SC based on material created inOmniRANin November 2015Concluding slide on cost and benefits caused discussions what would be needed to cover the network aspects for the various optionsIMT 2020 application would be feasible with some ‘profiling’ to P802.1CF, however IEEE 5G would require comprehensive network specification likely causing efforts >> 100 SY.Faultdiagnostics and maintenancehttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0019-01-CF00-measurement-and-management-in-ieee-802-11.pptxWangHaopresented 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.
Discussions #5
Reviewof 802.1CF editor’s draftDiscussion of wayforwardNext revision to be created after the May interim meeting with hopefully much more content merged inAmendments to NRM will be discussed in next conference call to create stable foundation for further text on function descriptionWhen Antonio would be able to attend Budapest meeting, SDN chapter would be thoroughly reviewed and revisedOpen comment resolution from Jan F2F will be concluded with Yonggang enabling to participate remotelyProjectplanningProject timeline quite stable, but dependency on amount of content, which can be adopted during/after Budapest meeting2 conference calls (April 19th, June 21st) planned until July plenaryDifficult w/ participants from California and China: 9:30AM ET, 90minsStatus report to IEEE 802WGsDrafted, presented, revised and uploaded tomentor underhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0022-00-00TG-mar-2016-status-report-to-802wgs.pptxAOBNoneMeeting adjourned by chair at 12:35
2016-03-17
ApproveOmniRANTG conference callson:April 19th,09:30AMET, 90minsJune 21st, 09:30 AM ET, 90minsAgenda and call-in details will be made available on the 802.1 mailing list and onhttps://mentor.ieee.org/omniran/bp/StartPageMoved: Max Riegel, Second:WalterPienciak
0
Embed
Upload