1 / 17

OmniRAN EC SG June 20 th , 2013 Conference Call

OmniRAN EC SG June 20 th , 2013 Conference Call. 2013-06-18 Max Riegel (OmniRAN SG Chair). Thursday , June 20 th , 2013, 09:00-11:00 AM ET Conference Call: Call-in number: 1-(972) 445 9673 (US) Global numbers: https://www2.nokiasiemensnetworks.com/nvc Conference Code: 433 819 2102 #

nevan
Download Presentation

OmniRAN EC SG June 20 th , 2013 Conference Call

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. OmniRAN EC SG June 20th, 2013Conference Call 2013-06-18Max Riegel (OmniRAN SG Chair)

  2. Thursday, June 20th, 2013, 09:00-11:00 AM ET Conference Call: Call-in number: 1-(972) 445 9673 (US) Global numbers: https://www2.nokiasiemensnetworks.com/nvc Conference Code: 433 819 2102 # WebEXhttps://nsn.webex.com/nsn/j.php?J=707621013&PW=NMTA5MTY1Yzhj Meeting Number: 707 621 013 Meeting Password: OmniRAN Meeting

  3. Guidelines for IEEE-SA 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. --------------------------------------------------------------- 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 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. This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt

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

  5. IEEE 802 is a world-wide professional technical organization Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization. Individuals are to address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter. Meeting Etiquette

  6. LMSC Operations Manual 4.3 Study groups 4.3.1 Study group operation Progress of each Study Group shall be presented at the closing Sponsor meeting of each IEEE 802 LMSC plenary session by the appropriate WG, TAG, or ECSG Chair. Study Groups may elect officers other than the Chair, if necessary, and will follow the general operating procedures for WGs specified in the IEEE 802 LMSC WG P&P. Because of the limited time duration of a Study Group, no letter ballots are permitted. 4.3.2 Voting at study group meetings Any person attending a Study Group meeting may vote on all motions (including recommending approval of a PAR). A vote is carried by 75% of those present and voting “Approve” or “Disapprove.”

  7. Call Meeting to Order Secretary position Approval of minutes of May 2013 F2F session Reports Updates to use cases documents Review of functional requirements and gaps to existing IEEE 802 standards Plan for July 2013 F2F session Dissemination of OmniRAN SG results into IEEE 802 working groups 802.1 802.3 802.11 802.15 802.16 802.21 802.22 802.24 Other WGs and SC Liaisons with IETF and other external SDOs Agenda for July ’13 plenary session AOB Adjourn AgendaThursday, June 20th, 09:00–11:00am ET

  8. Business#1 • Call Meeting to Order • Appointment of recording secretary • Roll Call

  9. Business #2 • Approval of agenda • no additional agenda items required • agenda approved • Approval of minutes of May 2013 F2F session • draft minutes available • Juan Carlos will review and add if necessary • approval postponed to the next meeting • Reports • early planning request from 802.11 • no response from 3GPP yet • Antonio made aware of European workshop in Barcelona in October on wireless SDN • would be interesting to take part if OmniRAN continues • Updates to use cases documents • updates on SaMOG and SEP2 planned for Jul F2F • no current plan to revise SDN document

  10. Business #3 • Review of functional requirements and gaps to existing IEEE 802 standards • nothing new to report • Plan for July 2013 F2F session • main topic will become completion of tasks as required by March EC closing plenary (see next slide) • timeline remains unchanged as study group is well in plan to deliver results (see slide 12) • draft slide set summarizing conclusions on scope, results of gap analysis and providing proposals for further proceeding was prepared by the chair and uploaded just before the conference call • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0048-00-0000-omniran-ecsg-results-and-outlook.pptx • chair presented slides leading to discussion and a number of hints for enhancements • ‘OmniRAN’ is the abstraction of an access network – clarifying that OmniRAN denotes the architectural model, not the process to create one • Presentation of gap analysis results requires some refinement but should stay with 3 slides in general to keep presentation time below 30 mins • Revised slide necessary for SDN mapping to the OmniRAN reference model • Leave ‘normative’ and ‘informative’ open as it prejudges organizational arrangements

  11. OmniRAN Objectives • To perform a gap analysis that shows what pieces of work that are relevant to 802 (standards and standards under development) are not covered by existing external SDOs  (IETF, 3GPP,...) and internal, and socialize that analysis with those SDOs; • Having performed that gap analysis, define a crisp scope of the ECSG (target 15 words or less); • Define what piece(s) of work within that scope (a) fall legitimately within 802's remit and (b) are achievable within an 802 activity.

  12. OmniRANPlan and Timeline Jul’15 Mar’21 Apr’11 May’2 Jun’20 Initial meeting Use cases contributions Draft Use cases document Call for comments on Use cases document Use cases document finalization Classification of functional requirements Functional requirements within scope of IEEE 802 Gap analysis to existing solutions Socializing of gap analysis Potential standardization topics for IEEE 802 Refine scope of EC SG (crisp words) Conf Call F2F meeting Jan Feb Mar Apr May Jun Jul

  13. July 2013 OmniRAN F2F Schedule

  14. Business #4 • Plan for July 2013 F2F session, cont. • Options for continuation will be discussed in Geneva F2F • Dissemination slides should present some alternatives • ‘Crisp’ wording proposal by JC: “Generic 802 [backhaul/] access network specification,including architecture definition, communication protocols andlink-specific parameters usage” • Dissemination of OmniRAN SG results into IEEE 802 WGs • 802.1 • Chair will ask for presentation time in 802.1 • Missing p-t-p support needs more comprehensive background and slides • 802.3 • Chair will ask for presentation time in 802.3 • Some more slides on 802.3 gaps • 802.11 • joint meeting w/ ARC; short presentation in mid-week • 802.15 • Chair will ask for presentation time in 802.15 • 802.16 • Report to 802.16 closing plenary on Thu PM2

  15. Business #5 • Dissemination of OmniRAN SG results into IEEE 802 WGs • 802.21 • Chair will ask for presentation time in 802.21 • 802.22 • Chair will ask for presentation time in 802.22 • 802.24 • Chair will ask for presentation time in 802.24 • Other WGs and SC • 802.19, 802.18 • Will also be addressed to show OmniRANbeneficials to their work • Liaisons with IETF and other external SDOs • Initiate informal information exchange with Bernd Aboba to discuss further dissemination into IETF • Agenda for July ’13 plenary session • See next slide • No modifications or amendments proposed

  16. Call Meeting to Order Attendance recording Secretary position Approval of minutes Reports Review dissemination of OmniRAN SG results into IEEE 802 WGs Review of communication and dissemination with external organizations Conclusion on OmniRAN use cases Gap analysis for the agreed use cases Documentation of results Potential standardization topics for IEEE 802 Refine scope of OmniRAN EC SG (crisp words) Report slides for EC Closing Session Summary report for communication inside IEEE 802 AOB Adjourn Agenda Proposal for July 2013 F2F

  17. Business #6 • AOB • Nothing brought up • Adjourn • Adjourned at 11.08 AM ET

More Related