1 / 20

OmniRAN EC SG Agenda and Meeting Slides July 2013, Geneva, CH

OmniRAN EC SG Agenda and Meeting Slides July 2013, Geneva, CH. 2013-07-16 Max Riegel (OmniRAN SG Chair). Tuesday , July 16 th , 13:30 – 15:30 Wednesday, July 17 th , 08:00 – 10:00 Joint w/ 802.11 ARC 08:00 – 09:00 Wednesday, July 17 th , 13:30 – 15:30

akiva
Download Presentation

OmniRAN EC SG Agenda and Meeting Slides July 2013, Geneva, CH

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 Agenda and Meeting SlidesJuly 2013, Geneva, CH 2013-07-16Max Riegel (OmniRAN SG Chair)

  2. Tuesday, July 16th, 13:30 – 15:30 Wednesday, July 17th, 08:00 – 10:00 Joint w/ 802.11 ARC 08:00 – 09:00 Wednesday, July 17th, 13:30 – 15:30 Joint w/ 802.21 13:30 – 14:30 w/ 802.15 15:00 – 15:30 Thursday, July 18th, 08:00 – 10:00 Joint w/ 802.16 08:00 – 09:00 Thursday, July 18th, 13:30 – 15:30 Meeting Room: CCV – Room C Meetings

  3. July 2013 OmniRAN F2F Schedule

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

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

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

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

  8. OmniRAN ECSGResources • Website:http://www.ieee802.org/OmniRANsg/ • Document Archive on mentor: https://mentor.ieee.org/omniran/documents • Email reflector: ecsg-802-omniran@listserv.ieee.org • Email archive: http://grouper.ieee.org/groups/802/OmniRANsg/email/ • Attendance:Paper list (normative) + IMAT • IMAT mandatory for participants seeking attendence credits • Reciprocal rights for most WGs

  9. Call Meeting to Order Attendance recording Secretary position Approval of agenda 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) Reporting slides for EC Closing Session Summary report for communication inside IEEE 802 AOB Adjourn Agenda for July 2013 F2F

  10. Business #1 • Call Meeting to Order • Session called to order by the chair at Tue 13:35 • The chair presented the mandatory guiding slides of IEEE SA. • Attendance recording • Chair explained that attendance recording is done by paper sheets with the possibility to gain reciprocal attendence credits by using registration by IMAT as well. • Secretary position • Chair asked for volunteers to fill open secretary position • No volunteers showed up. The position remains open. • Juan Carlos Zuniga volunteered for taken minutes of the session. • Approval of agenda • Chair brought up the agenda propsal created in the teleconference on June 20th and published on the OmniRAN website. • The chair asked for demand for additional agenda items or changes to the agenda • No requests were brought up • The chair went over the meetings of the week and pointed out that a joint meeting with 802.11ARC is planned for the first hour of the Wed AM1 meeting (in CICG room 14) and with 802.21 in the first hour of the Wed PM1 session. • A further joint meeting with 802.16 and a presentation to 802.15 are intended but are not scheduled yet. The chair will keep the study group informed about schedules with the other working groups. • The chair asked for objections to acceptance of the proposed agenda • The agenda was approved without objections.

  11. Business #2 • Approval of minutes • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0047-00-ecsg-meeting-minutes-for-may-2013-waikoloa-session.docx • The chair brought up the minutes of the Waikoloa session and asked for corrections or amendments. No request to change the minutes was raised. • The chair asked for objections to approve the minutes of the waikoloa session. • The minutes were approved without objections. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0049-00-ecsg-meeting-minutes-of-june-20th-conference-call.docx • The chair brought up the minutes of the June 20th conference call and asked for corrections or amendments. Antonio requested to correct the spelling of his affiliation. The spelling of the affiliation was corrected and the revision of the minutes was uploaded to Mentor. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0049-01-ecsg-meeting-minutes-of-june-20th-conference-call.docx • No other requests for modifications were made. • The chair asked for objections to approve the minutes of the June 20th conference call. • The minutes were approved without objections. • Reports • The chair brought up the following two slides pointing out the objectives and the current stage of the work.

  12. OmniRAN EC SG 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.

  13. OmniRAN EC SGPlan 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

  14. Business#3 • Reports, cont. • The chair opened the slides provided to the EC opening meeting and explained that only a verbal report was given due to shortage of time. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0051-01-ecsg-jul2013-ec-opening-report.pptx • Review dissemination of OmniRAN SG results into IEEE 802 WGs • The chair mentioned that presentations of OmniRAN EC SG findings were presented to 802.1, 802.19, 802.22 and 802.24 based on the following slides. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0048-03-0000-omniran-ecsg-results-and-outlook.pptx • The following two slides mostly capture the essential outcomes of the presentations to the 802.1, 802.3, 802.19, 802.22 and 802.24 • The study group reviewed the slides and provided comments, in particular to create more concrete statements for the directions of the EC SG going forward. • Due to the limited presentation time the presentation to 802.3 was done based on the following slides with the invitation to the 802.3 attendents to come to the OmniRAN EC SG meetings to get a more comprehensive insight into the findings of the EC SG • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0052-00-ecsg-omniran-liaison-report.pptx • The chair recessed the session at Tue 15:30 reminding that the group meets Wed AM1 first with 802.11ARC before reconveneing in CCV Room C at about 09:00. • ------------------------------ • Wed, AM1 • In the joined meeting with 802.11ARC the following slides were presented: • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0048-03-0000-omniran-ecsg-results-and-outlook.pptx (without slides 33-35) • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0055-00-0000-progressing-omniran.pptx • The second presentation raised quite some discussion finally leading to the conclusion that 802.11 ARC would support the extension of OmniRAN EC SG for creation of a draft PAR and 5C.

  15. Discussions with IEEE 802 WGs • 802.1 (Mo, 13:30-14:30) • Not concerned about sticking to PHY and DLL • IEEE 802 may address higher layer functionality • Not very concerned about consistency between IETF and IEEE 802 specifications • Presented gaps are mostly addressed by existing 802.1 specifications • Functionality may not be easily visible in the specifications • Some minor details may be open • => Needs further investigations into IEEE 802.1 specifications • Further contributions to IEEE 802.1 invited on gaps to better understand the missing pieces • 802.19 (Mo, 14:30-15:30) • 802.19.1 easily fits into OmniRAN Network Reference Model • 802.19.1 defines further protocol going over R3 • CM located in Core, TV WS DB located in the Services domain • 802.19.1 defines protocol on top of TCP/IP (primitives without encoding)

  16. Discussions with IEEE 802 WGs, cont. • 802.3 (Mo, 15:30-15:40) • Only OmniRAN Liaison Report presented • Missing understanding of the ‘Stage 1 - Stage 2 - Stage 3’ approach • Doubts that specification can be created without setting up a WG • 802.24 (Mo, 16:45-17:45) • Understanding of the benefits for Smart Grid TAG • Some missing understanding of an ‘architecture’ specification • Demand for ‘example document’ • Possibilities discussed to create simple/initial document within 802.24 with specific focus on SmartGrid • 802.22 (Tu, 08:30-09:30) • Creates network side control interfaces (primitives without encoding) • Much better understanding reached what OmniRAN provides • Invitation to cooperate with 802.22 when group has been established

  17. Business #4 • The chair reconvenend the meeting in CCV room C at 09:25 and called the meeting to order. • The chair announced that the joint meeting with 802.16 has been scheduled for the first hour of the Thursday AM1 session, and a presentation to 802.15 has been reserved for Wednesday 15:00. • Following the announcement the study group continued on with the agenda. • Review of communication and dissemination with external organizations • No response received yet from 3GPP • Conclusion on OmniRAN use cases • Gap analysis for the agreed use cases • Documentation of results • Juan Carlos presented the revision of the slides on the SDN use case pointing to the edits, which went into the revision. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0044-01-0000-sdn-use-cases-summary.pptx • Discussion came up on some editorial details in the slides finally leading to another revision. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0044-02-0000-sdn-use-cases-summary.pptx • The group agreed on putting the slides in a new revision of the ec-results-and-outlook slides (ominran-13-0048-03). • The meeting was recessed by the chair at 10:05. • ------------------ • The chair called the meeting to order at Wed 13:40 explaining that the first hour of the PM1 meeting is reserved for the joint discussion with 802.21 and a presentation slot in 802.15 as reserved for 15:00 requireing the chair to recess the meeting latest 14:55. • The chair opened the joint meeting with 802.21. • The discussion with 802.21 was based and guided by the presentation • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0048-04-0000-omniran-ecsg-results-and-outlook.pptx as revised according to the discussions in the AM1 meeting. • Joe brought up in the discussion that the EC SG should address a full standard instead of a recommended practice to show the importance of the work. • There was no conclusion whether it would be more appropriate to go for full standard.

  18. Business #5 • After closing the joint meeting at Wednesday14:55 the chair recessed the meeting to head for the assigned presentation slot in 802.15 at 15:00 • ------------------- • Reconvening the meeting at Thursday, 08:30 the chair called the meeting to order and opened the joint meeting together with 802.16. • The discussion was following the presentation of the slides • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0048-04-0000-omniran-ecsg-results-and-outlook.pptx • After closing the joint meeting with 802.16 at 09:30 the chair continued with the agenda asking for the presentation of the following contribution: • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0054-00-ecsg-omniran-architecture.pptx • As the submitter was not present for presentation, the chair continued with the agenda. • Potential standardization topics for IEEE 802 • The group addressed the wording of the plan to create a PAR and 5C for a Recommended Practice • The outcome of the edits were captured of the last slide of a slidedeck, which the chair prepared as input for the creation of the report to the EC closing meeting. • The chair recessed the meeting at 10:00. • -------------

  19. Business #6 • Reconvening the meeting the chair called the meeting to order at Thursday 13:40 asking for the continuation of the discussion on the following two topics by working on the presentation • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0056-00-ecsg-omniran-ecsg-jul13-conclusions.pptx • Refine scope of OmniRAN EC SG (crisp words) • Reporting slides for EC Closing Session • By discussion and online editing a revision of the jul13-conclusion with the presentation content for the EC closing meeting was created and uploaded. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0056-01-ecsg-omniran-ecsg-jul13-conclusions.pptx • As a focused slide set without any back-up material is needed for the report a dedicated EC reporting slideset was created and uploaded. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0057-00-ecsg-omniran-ec-closing-report.pptx • A motion was brought up approving the report to the EC closing plenary together with requesting the extension of the OmniRAN EC SG was brought up. • The motion passed by 7 yes/0 no/o abstain • Summary report for communication inside IEEE 802 • Michael Montemurro presented his proposal for the summary report to working groups within IEEE 802. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0053-00-ecsg-omniran-ec-sg-liaison-report-july-2013.pptx • No proposals for corrections or amendments were raised. • The summary report was approved without objections. • AOB • No other business was brought up • Adjourn • The session of the OmniRAN EC SG was adjurned by the chair at 15:50.

  20. Motion • Approve document omniran-13-0057-00-ecsg as the report to the EC and request of extension of OmniRAN EC SG until November 2013. • Moved: Juan Carlos Zuniga, Interdigital • Yonggang Fang, ZTE • 7/0/0, motion passes

More Related