omniran ec sg agenda january 2013 vancouver bc n.
Skip this Video
Download Presentation
OmniRAN EC SG Agenda January 2013, Vancouver, BC

Loading in 2 Seconds...

play fullscreen
1 / 12

OmniRAN EC SG Agenda January 2013, Vancouver, BC - PowerPoint PPT Presentation

  • Uploaded on

OmniRAN EC SG Agenda January 2013, Vancouver, BC. 2013-01-14 Max Riegel (OmniRAN SG Chair). Tuesday, January 15 th , 13:30 – 15:30 Wednesday, January 16 th , 13:30 – 15:30 Thursday, January 17 th , 13:30 – 15:30 Meeting Room: Balmoral, Convention Level. Meetings.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'OmniRAN EC SG Agenda January 2013, Vancouver, BC' - rollo

Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
omniran ec sg agenda january 2013 vancouver bc

OmniRAN EC SG AgendaJanuary 2013, Vancouver, BC

2013-01-14Max Riegel

(OmniRAN SG Chair)

Tuesday, January 15th, 13:30 – 15:30

Wednesday, January 16th, 13:30 – 15:30

Thursday, January 17th, 13:30 – 15:30

Meeting Room:

Balmoral, Convention Level

guidelines for ieee sa meetings
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 or visit

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

resources urls
Link to IEEE Disclosure of Affiliation

Links to IEEE Antitrust Guidelines

Link to IEEE Code of Ethics

Link to IEEE Patent Policy

Resources – URLs
meeting etiquette
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
lmsc operations manual
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.”

agenda tuesday january 15 th 13 30 15 30
Call Meeting to Order

Appointment of secretary

Ground rules for EC SG

Attendance policy

Voting rules

Approval of agenda

Introduction of study group chair

Introduction of participants

Vice chair position


Vice chair (depending on SG decision)

Close of nomination

Juan Carlos Zuniga


AgendaTuesday, January 15th, 13:30 – 15:30
agenda cont
Agenda, cont.
  • Review EC decision on OmniRAN SG
    • EC Meeting minutes [p116-120]:
  • Organization
    • Website:
      • Email reflector:
      • Email archive:
    • Mentor:
      • Registration under myProject required:
  • Announcements to IETF, 3GPP, BBF, WFA, WiMAX Forum
  • OmniRAN technical scope review
agenda wednesday january 16 th 13 30 15 30
AgendaWednesday, January 16th, 13:30 – 15:30
  • Use case and deployment contributions
    • Proposal of OmniRAN architecture for Data Offload Service through Wireless P2P Networks
    • OmniRAN Smart Grid use case
  • OmniRAN use cases document
    • Including the proposals from 16HET discussions
agenda thursday january 17 th 13 30 15 30
AgendaThursday, January 17th, 13:30 – 15:30
  • Specification structuring and phasing
  • PAR and 5C templates
  • Other contributions
  • Way forward
    • Liaisons
    • Further announcements to other SDOs
    • IETF cooperation
      • IEEE802/IETF joint meeting in Orlando
  • Next meetings
  • Adjourn
motions tuesday january 15 th 13 30 15 30
Vice chair office in OmniRAN SG?

Moved: C. Perkins Second: R. Marks

Y: 26 N: 0 A: 0

Vice chair

Juan Carlos Zuniga

Y: 25 N: 0 A: 1


No nomination received

MotionsTuesday, January 15th, 13:30 – 15:30
omniran use case document
OmniRAN Use Case Document
  • Compilation of all proposed use cases
    • Contributors are asked to (re-)provide proposal for insertion in appropriate format
  • Each OmniRAN use case presented to the same structure:
    • Application domain
    • Textual description
    • Requirements derived
  • Text document or slide set?
  • Who would take the editor role?