1 / 15

IEEE 802.1 OmniRAN TG September 26 th , 2017 Conference Call

Join the IEEE 802.1 OmniRAN TG conference call on September 26th, 2017 at 09:30-11:00am ET to discuss progress reports, text proposals, and adoption of TSN. Participants have obligations under the IEEE-SA Patent Policy.

rhansen
Télécharger la présentation

IEEE 802.1 OmniRAN TG September 26 th , 2017 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. IEEE 802.1 OmniRAN TGSeptember 26th, 2017 Conference Call 2016-09-25Max Riegel, Nokia Bell Labs (TG Chair)

  2. Tuesday, September 26th , 2017 at 09:30-11:00am ET Join WebEx meeting https://nokiameetings.webex.com/nokiameetings/j.php?MTID=m54b8fa4482f931f3c880b0b97003bc73 Meeting number: 955 059 974 Meeting password: OmniRAN Join by phone +19724459814 US Dallas +442036087616 UK London Access code: 955 059 974 Global call-in numbers https://nokiameetings.webex.com/nokiameetings/globalcallin.php?serviceType=MC&ED=533522097&tollFree=0 Conference Call

  3. Minutes Reports Progress and agree on information model for Access network and User service Follow-up on actions defined during the editorial review at St. John's F2F Discuss and review text proposal for adoption of TSN in Chap 7.5 & 7.6 AOB Agenda proposal

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

  5. 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 Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 • IEEE-SA Standards Board Operations Manualhttp://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.ppt

  6. 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 Call for Potentially Essential Patents

  7. All participation in IEEE 802 Working Group meetings is on an individual basis Participants in the IEEE standards development individual process shall act based on their qualifications and experience. (https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1) IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (http://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf section 4.2.1) You have an obligation to act and vote as an individual and not under the direction of any other individual or group. Your obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders. You shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, see https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1.3 and http://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf section 3.4.1, list item x By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate. Participation in IEEE 802 Meetings

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

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

  10. Business#1 • Call Meeting to Order • Meeting called to order by chair at … AM ET • Minutes taker: • … is taking notes • Roll Call

  11. 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 … Call for Potentially Essential Patents

  12. Minutes https://mentor.ieee.org/omniran/dcn/17/omniran-17-0070-00-00TG-september-2017-f2f-meeting-minutes.docx Reports … Progress and agree on information model for Access network and User service … Follow-up on actions defined during the editorial review at St. John's F2F Max: Definition of unlicensed and authorized spectrum at the begin of chapter 7.1 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0073-00-CF00-chap-7-1-terminology-amendment.docx Max: Amend text at the beginning of NDS section to explain figure 30 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0074-00-CF00-chap-7-2-figure-amendment.docx Max: Introduce the role of NMS in the chapter 7.5 Data path Captured in TSN revision of Chap 7.5 & 7.6 Max: Provide a short introduction to the restructured chapter 8 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0075-00-CF00-chap-8-intro-amendment.docx Max: Amend chapter 4.2 with an explanation of the UML notation used in the document. Inheritance will be added to the capabilities https://mentor.ieee.org/omniran/dcn/17/omniran-17-0072-00-CF00-chap-4-2-conventions-amendment.docx Hao: Review and revise chapter 7.8.3.3 to remove overlap with section 7.2 including fig 57 … Discuss and review text proposal for adoption of TSN in Chap 7.5 & 7.6 Contribution pending. AOB Agenda

  13. Business #2 • Review of minutes • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0070-00-00TG-september-2017-f2f-meeting-minutes.docx • Reports • ... • Progress and agree on information model for Access network and User service • …

  14. Business #3 • Follow-up on actions defined during the editorial review at St. John's F2F • Max: Definition of unlicensed and authorized spectrum at the begin of chapter 7.1 • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0073-00-CF00-chap-7-1-terminology-amendment.docx • Max: Amend text at the beginning of NDS section to explain figure 30 • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0074-00-CF00-chap-7-2-figure-amendment.docx • Max: Introduce the role of NMS in the chapter 7.5 Data path • Captured in TSN revision of Chap 7.5 & 7.6 • Max: Provide a short introduction to the restructured chapter 8 • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0075-00-CF00-chap-8-intro-amendment.docx • Max: Amend chapter 4.2 with an explanation of the UML notation used in the document. Inheritance will be added to the capabilities • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0072-00-CF00-chap-4-2-conventions-amendment.docx • Hao: Review and revise chapter 7.8.3.3 to remove overlap with section 7.2 including fig 57 • …

  15. Business #3 • Discuss and review text proposal for adoption of TSN in Chap 7.5 & 7.6 • Contribution pending. • AoB • … Adjourned by chair at … AM ET

More Related