th 2016 Conference Call 20160926 Max Riegel Nokia Bell Labs TG Chair Conference Call Tuesday September 27 th 2016 at 09301100am ET Join WebEx meeting httpsnokiameetingswebexcomnokiameetingsjphpMTIDmabf841eb441bcc71f495954cfd5e72d3 ID: 727402
Download Presentation The PPT/PDF document "IEEE 802.1 OmniRAN TG September 27" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
IEEE 802.1 OmniRAN TGSeptember 27th, 2016 Conference Call
2016-09-26
Max
Riegel, Nokia Bell Labs
(TG
Chair)Slide2
Conference Call
Tuesday, September 27
th
, 2016 at 09:30-11:00am ET
Join WebEx meeting
https://nokiameetings.webex.com/nokiameetings/j.php?MTID=mabf841eb441bcc71f495954cfd5e72d3
Meeting number: 950 779 738
Meeting password:
2bjbBC23
Join by phone
Global call-in numbers
https://nokiameetings.webex.com/nokiameetings/globalcallin.php?serviceType=MC&ED=487224687&tollFree=0
>
Access code: 950 779 738Slide3
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 searchSlide4
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.pptSlide5
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 submittedSlide6
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.Slide7
Resources – URLsLink 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.pptSlide8
Agenda proposalReview
of minutes
Warsaw F2F minutes
Reports
Contributions
to P802.1CF D0.3
Conclusion on additions and amendments for P802.1CF D0.3
Planning updateAoBSlide9
Business#1Call Meeting to Order
Meeting called to order by chair at 09:35 AM ET
Minutes taker:
Walter volunteered to take notes
Roll Call
Name
Affiliation
Name
Affiliation
Max Riegel
Nokia
Walter Pienciak
IEEE SAWang HaoFujitsu
Fan
Xiaojing
Fujitsu
Yonggang
Fang
ZTE TXSlide10
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
Nothing brought up.Slide11
Agenda
Review
of minutes
Warsaw F2F minutes
https://
mentor.ieee.org/omniran/dcn/16/omniran-16-0063-00-00TG-sept-2016-meeting-minutes.docx
Reports
?Contributions to P802.1CF D0.3https://mentor.ieee.org/omniran/dcn/16/omniran-16-0070-00-CF00-chapter-7-introduction.docxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0069-00-CF00-response-to-comments-on-revision-of-chapter-7-6-7.pptxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0060-01-CF00-chapter-7-6-7-revision.docx
https
://
mentor.ieee.org/omniran/dcn/16/omniran-16-0068-00-CF00-chapter-7-4-1-revision.pptx
https://
mentor.ieee.org/omniran/dcn/16/omniran-16-0067-00-CF00-deployment-scenarios-for-home-network.docxConclusion on additions and amendments for P802.1CF D0.3https://mentor.ieee.org/omniran/dcn/16/omniran-16-0059-01-00TG-p802-1cf-d0-2-collected-comments.xlshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0066-00-CF00-comments-on-p802-1cf-d02.xlsPlanning updateAoBAccess network instantiationhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0065-00-CF00-virtual-access-network-instantiation.pptxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0071-00-CF00-key-concepts-of-an-instantiation.pptx?Slide12
Business #2Review of minutes
Warsaw F2F minutes
https://mentor.ieee.org/omniran/dcn/16/omniran-16-0063-00-00TG-sept-2016-meeting-minutes.docx
Chair quickly introduced minutes of Warsaw meeting. No comments raised.
Reports
Chair mentioned that 5G SC Action B3 led to a liaison send from 802.11 to the 3GPP RAN, now followed by a further liaison from EC to the 3GPP PCG. AANI is taking care of Action B3 in 802.11.Slide13
Business #3
Contributions to P802.1CF D0.3
Review
and acceptance of updated
contributions
https://
mentor.ieee.org/omniran/dcn/16/omniran-16-0067-00-CF00-deployment-scenarios-for-home-network.docx
Wang Hao presented the contribution showing the well-fitting mapping of the architecture of a residential gateway to the P802.1CF Network Reference Model.Discussion brought up demand for a more explicit description, e.g. pointing out which of the Y.2070 functions and interfaces have direct relationship with functions and interfaces in 802.1CF NRM.The group asked the author to revise the document adding more details about the mapping of functions and interfaces.https://mentor.ieee.org/omniran/dcn/16/omniran-16-0070-00-CF00-chapter-7-introduction.docx
Max presented proposed text for the introduction of Section 7 Functional design and decomposition.
The text was accepted for inclusion into D0.3 with the condition that a small amendment is added clarifying that section 7 also provides functional specification of network setup and fault discovery and maintenance.
Max will distribute the revision by email to the participants for a check of the small amendment. If no concerns are raised the revision will be included into D0.3
https://
mentor.ieee.org/omniran/dcn/16/omniran-16-0068-00-CF00-chapter-7-4-1-revision.pptxWang Hao explained the issue of the location of the authenticator in the revised specification of 7.4.1.The group agreed that the issue is valid and the proposed remedy is appropriate. The proposed modification will be adopted to D0.3https://mentor.ieee.org/omniran/dcn/16/omniran-16-0069-00-CF00-response-to-comments-on-revision-of-chapter-7-6-7.pptxWang Hao presented the slides providing further background on the text proposal submitted by comment #56The group agreed that the proposed request acknowledge messages indeed make sense, and that https://mentor.ieee.org/omniran/dcn/16/omniran-16-0060-01-CF00-chapter-7-6-7-revision.docx should be adopted for D0.3, which explicitly mentions that the acknowledge message is send after integrity check.Slide14
Business #4Conclusion on additions and amendments for P802.1CF
D0.3
Warsaw comments database
https
://
mentor.ieee.org/omniran/dcn/16/omniran-16-0059-01-00TG-p802-1cf-d0-2-collected-comments.xls
The chair inserted in the comments table the closure of comment #56 and uploaded a revised version:
Late submission of comments on chapter 8.1https://mentor.ieee.org/omniran/dcn/16/omniran-16-0066-00-CF00-comments-on-p802-1cf-d02.xlsThe group reviewed shortly the late comments’ submission mainly addressing editorial and technical issues in chapter 8.1 on SDN.
While the editorial issues can be easily adopted by the editor for D0.3, the technical issues require more comprehensive review together with the original author of section 8.1.
The chair will inform Antonio de la Oliva about the comments and will ask for an email response to resolve the comments. If Antonio requires more input and discussions, the open comments will be put on the agenda of the next conference call on October 25
th
inviting both Yonggang and Antonio for participation.
Agreed list of amendments and additions for D0.3The following documents will be adopted to the revision D0.3:https://mentor.ieee.org/omniran/dcn/16/omniran-16-0059-02-00TG-p802-1cf-d0-2-collected-comments.xls and all the documents referenced in the resolution column of the spreadsheet.https://mentor.ieee.org/omniran/dcn/16/omniran-16-0060-01-CF00-chapter-7-6-7-revision.docxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0058-01-CF00-chapter-7-4-revision.docxhttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0068-00-CF00-chapter-7-4-1-revision.pptxEditorial comments listed in https://mentor.ieee.org/omniran/dcn/16/omniran-16-0066-00-CF00-comments-on-p802-1cf-d02.xlshttps://mentor.ieee.org/omniran/dcn/16/omniran-16-0070-01-CF00-chapter-7-introduction.docx, when no concerns raised in the email approvalSlide15
Business #5
Planning update
The chair brought up and reviewed the plan established at the Warsaw meeting.
The completion of comments’ resolution was done in conference call on Sept 27
th
.as well as the decision about the amendments adopted to D0.3. The remaining actions of the plan for creation of D0.3 are still valid:
15 days recirculation closing Nov 3rdAnnouncement of recirculation on Oct 17thExternal review of P802.1CF-D0.3The following potential actions were reviewed.Plan to present P802.1CF in intarea meeting at next IETF (Nov 14-17, Seoul, Korea)The plan was discussed and agreed at the IETF/IEEE leadership meeting in Paris on September 9th. If none of the OmniRAN core members are attending the IETF meeting in Korea, Juan Carlos Zuniga would bring up the presentation. Walter indicated that he would attend the IETF meeting in Korea and would be able to present if the session is taking place later in the week.
Preparation of the
slideset
and decision about the presenter will be done at the San Antonio meeting, which is taking place the week before of the IETF meeting.
TTC Japan; Introduction done by Fujitsu
Request for access to specificationSo far, no request for the specification has been received. Chair asked to forward the request to him for clarification with 802.1 chair Glenn Parsons.Other groups?No further groups are currently considered for distribution of the draft specification. It may change in the course of the 5G SC Action A discussions and when interest in the OmniRAN work is popping up at other locations.Slide16
Business #6AoB
Access network instantiation
https://mentor.ieee.org/omniran/dcn/16/omniran-16-0065-00-CF00-virtual-access-network-instantiation.pptx
Yonggang introduced his thoughts on the network instantiation. There was agreement that instantiation has to be followed by initialization. The proposed procedure did not find agreement.
https://mentor.ieee.org/omniran/dcn/16/omniran-16-0071-00-CF00-key-concepts-of-an-instantiation.pptx
Max presented his initial thoughts to structure the instantiation by showing relationship between orchestrator and OSS/BSS system of access network operator, which is the agreed entity issuing the requests to the orchestrator.
The four presented use cases found acceptance with Yonggang mentioning that there might be additional use cases to be taken into account.
Further discussion is required regards message flows. There was a slight preference for direct message flows between OSS/BSS and orchestrator for the creation and removal of ANC, NA and BH instances.Further discussions are required to achieve conclusion about the basic concepts of instantiation.No other issues were brought up.
The chair reminded the next conference call will take place on October 25th, 0930-1100AM ET
Meeting adjourned by chair at 11:12AM ET.