1 / 15

OmniRAN EC SG Agenda May 2013, Waikoloa, HI

OmniRAN EC SG Agenda May 2013, Waikoloa, HI. 2013-05-13 Max Riegel (OmniRAN SG Chair). Monday, May 13 th , 10:30 – 12:30 Tuesday, May 14 th , 10:30 – 12:30 Tuesday , May 14 th , 13:30 – 15:30 Wednesday, May 15 th , 08:00 – 10:00 Wednesday, May 15 th , 13:30 – 15:30

phoebe
Télécharger la présentation

OmniRAN EC SG Agenda May 2013, Waikoloa, HI

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 AgendaMay 2013, Waikoloa, HI 2013-05-13Max Riegel (OmniRAN SG Chair)

  2. Monday, May 13th, 10:30 – 12:30 Tuesday, May 14th, 10:30 – 12:30 Tuesday, May 14th, 13:30 – 15:30 Wednesday, May 15th, 08:00 – 10:00 Wednesday, May 15th, 13:30 – 15:30 Thursday, May 16th, 10:30 – 12:30 Thursday, May 16th, 16:00 – 18:00 Meeting Room: King’s 1 Meetings

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

  8. Call Meeting to Order Attendance recording Secretary position Approval of minutes Reports Feedback from 3GPP on liaison letter OmniRANscope and extension by Mar ‘13 closing EC plenary IEEE 802 view on OmniRAN architecture Establishment of architecture document Conclusion on OmniRAN use cases Review of use cases document Gap analysis for the agreed use cases Communication with external organizations Plan and timeline for OmniRAN SG conclusion Future sessions of OmniRAN EC SG Summary report for communication inside IEEE 802 AOB Adjourn Agenda

  9. Agenda Scheduling

  10. May 2013 Session - #1 • Call Meeting to Order • Attendance recording • Please use paper sheets – and IMAT for attendance credit • Secretary position • ? • Approval of minutes • March Orlando F2F session • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0033-00-ecsg-meeting-minutes-for-march-2013-plenary-meeting.docx • April 11th conference call • May 2nd conference call • Reports • OmniRANliaison letter to 3GPP SA2 • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0024-01-0000-3gpp-liaison-on-samog-interpretations.docx • Sent out on March 28th, 2013 • So far no response received • OmniRANextension byEC closing plenary in March ‘13 • See next slide

  11. #2Refined directions provided by EC • After some hefty discussions OmniRAN was extended until end of July ‘13 plenary. • The EC provided further guidance for the tasks of OmniRAN ECSG: Motion#28The EC considers that the primary tasks of the OmniRAN ECSG, to be completed by the close of the July Plenary, are: • 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. Moved JeffreySecond ThalerResults 8 / 2 / 3Motion Passes

  12. #3Plan and Timeline (EC SG Motion) Jun’15 Jul’15 Mar’21 Apr’11 May’2 Initial meeting Use cases contributions Draft Use cases document Stretch activities out until end of Jul’13 plenary Socialize results with IEEE 802 and external SDOs Call for comments on Use cases document Use cases document finalization Classification of functional requirements Prioritization of functional requirements Gap analysis to existing solutions Decision about initial topic Initial PAR text Draft PAR completed for EC submission Finalization of PAR proposal ? Conf Call F2F meeting Jan Feb Mar Apr May Jun Jul

  13. #4Plan and Timeline (EC SG Motion) Jul’15 Mar’21 Apr’11 May’2 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. #5May 2013 Objectives • Conclude on contributions on OmniRAN use cases • Finalize use cases document including functional requirements based on agreed contributions • Establish architecture document aligned to existing IEEE 802 views to distinguish between functionality in scope of IEEE 802 and functionality out of scope. • Draft document on gaps to available IEEE 802 functionality for the agreed use cases • Plan for internal and external communication to retrieve feedback on architectural view and gaps document • Review and refine timeline and plan for creation of deliverables until Jul ‘13

  15. May 2013 Session #6 • IEEE 802 view on OmniRAN architecture • Establishment of architecture document • Conclusion on OmniRAN use cases • Review of use cases document • Gap analysis for the agreed use cases • Communication with external organizations • Plan and timeline for OmniRAN SG conclusion • Future sessions of OmniRAN EC SG • Summary report for communication inside IEEE 802 • AOB • Adjourn

More Related