IEEE OmniRAN TG Conference Call and Patent Policy Overview

omniran 17 0037 01 00tg n.w
1 / 15
Embed
Share

Join the IEEE OmniRAN TG Conference Call on April 11th, 2017, to discuss essential patent claims and obligations under the IEEE-SA Patent Policy. Participants must be aware of their responsibilities regarding patents. Learn more about patent policies, procedures, and resources related to standards development. If you have potentially essential patents, inform the group to ensure compliance.

  • IEEE
  • OmniRAN
  • Conference Call
  • Patents
  • Policy

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. omniran-17-0037-01-00TG IEEE 802.1 OmniRAN TG April 11th, 2017 Conference Call 2016-04-11 Max Riegel, Nokia Bell Labs (TG Chair) 1

  2. omniran-17-0037-01-00TG Conference Call Tuesday, April 11th, 2017 at 09:30-11:00am ET Join WebEx meeting: https://nokiameetings.webex.com/nokiameetings/j.php?MTI D=md93c66923e06ebc2f89c76168622da8c Meeting number: 954 975 149 Meeting password: OmniRAN Join by phone Access code: 954 975 149 +1 972 445 9814 United States (Dallas) Global call-in numbers https://nokiameetings.webex.com/nokiameetings/globalcallin .php?serviceType=MC&ED=493455792&tollFree=1 2

  3. omniran-17-0037-01-00TG 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 3

  4. omniran-17-0037-01-00TG 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 Bylaws http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://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 4

  5. omniran-17-0037-01-00TG Call for Potentially Essential Patents 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 5

  6. omniran-17-0037-01-00TG Participation in IEEE 802 Meetings 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. 6

  7. omniran-17-0037-01-00TG 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. 7

  8. omniran-17-0037-01-00TG Resources URLs 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 8

  9. omniran-17-0037-01-00TG Agenda proposal Review of minutes Vancouver F2F minutes Reports Comment resolution of P802.1CF D0.4 New contributions to 802.1CF AoB 9

  10. omniran-17-0037-01-00TG Business#1 Call Meeting to Order Meeting called to order by chair at 09:30 AM ET Minutes taker: Walter is taking notes Roll Call Name Affiliation Name Affiliation Max Riegel Nokia Walter Pienciak IEEE Wang Hao Fujitsu 10

  11. omniran-17-0037-01-00TG Call for Potentially Essential Patents 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 Nothing brought up. 11

  12. omniran-17-0037-01-00TG Agenda Review of minutes Vancouver F2F minutes https://mentor.ieee.org/omniran/dcn/17/omniran-17-0036-00-00TG-mar-2017-f2f-meeting-minutes.docx https://mentor.ieee.org/omniran/dcn/17/omniran-17-0035-00-5gaa-mar-15th-f2f-meeting-minutes-for-5g-action- a.docx Reports ICAID Approval by SASB: http://standards.ieee.org/about/sasb/0317sasbmin.pdf Approval by ICcom: http://standards.ieee.org/about/sasb/iccom/032217mins.pdf ? Comment resolution of P802.1CF D0.4 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0030-02-CF00-802-1cf-d0-4-collected- comments.xls https://mentor.ieee.org/omniran/dcn/17/omniran-17-0024-00-CF00-chapt-7-2-8-mapping-to-ieee802- technologies.docx https://mentor.ieee.org/omniran/dcn/17/omniran-17-0025-00-CF00-chapt-7-5-8-mapping-to-ieee802- technologies.docx https://mentor.ieee.org/omniran/dcn/17/omniran-17-0026-00-CF00-chapt-7-6-8-mapping-to-ieee802- technologies.docx New contributions to 802.1CF No new contributions AoB Plans for the Stuttgart interim on May 15-18 ? 12

  13. omniran-17-0037-01-00TG Business #2 Review of minutes Vancouver F2F minutes https://mentor.ieee.org/omniran/dcn/17/omniran-17-0036-00-00TG-mar-2017-f2f- meeting-minutes.docx https://mentor.ieee.org/omniran/dcn/17/omniran-17-0035-00-5gaa-mar-15th-f2f- meeting-minutes-for-5g-action-a.docx Hao asked for a small correction to the March 2017 F2F meeting minutes. There is no conclusion yet about the location of the data modeling section in the document. Chair offered to introduce correction to the minutes and upload a corrected version after the call. No further comments received on the minutes Reports ICAID Approval by SASB: http://standards.ieee.org/about/sasb/0317sasbmin.pdf Approval by ICcom: http://standards.ieee.org/about/sasb/iccom/032217mins.pdf Chair reported the successful approval of the 802.1 Industry Connections activity. Glenn is still looking for someone driving the activity. Max reported that he was offered the position, but he had to decline due to shortage of resources. Nevertheless he intends to contribute to the activity, in particular to advertise and promote the 802.1CF specification to potential users in industry. Nothing else reported. 13

  14. omniran-17-0037-01-00TG Business #3 Comment resolution of P802.1CF D0.4 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0030-02-CF00-802-1cf-d0-4-collected- comments.xls Chair opened the last revision of the comments spreadsheet and reviewed the open comments. The proposal to rearrange introductory text of section 6.2 to provide better explanation of the scope directly at the beginning of chapter 6 found common support. Max will provide a text proposal for the next conference call (comment 2) The adoption of the contributions on deployment scenarios discussed at the Vancouver meeting was agreed. There was some discussion regards the dangling interfaces in the second figure in the Wi-Fi router description concluding that the current representation is appropriate (comments 11, 15, 16) Hao offered to create for the next confcall a revised version of the figure of the residential gateway following the usual orientation of terminal towards access network (terminal is shown on the left side of the figure). Max explained that he will come back with proposal regarding certificates in section 7.2. He believes that credential should be used as a generic term for a mean to realize mutual trust between peers. certificate is a particular implementation of a credential. (comment 18) https://mentor.ieee.org/omniran/dcn/17/omniran-17-0024-00-CF00-chapt-7-2-8-mapping-to- ieee802-technologies.docx Max introduced his proposal for section 7.2.8 explaining that it worked out to be more appropriate to describe realization of NDS for various technologies in separate sections, as not all technologies support for various reasons not all functions described in the chapter. The proposed text was considered appropriate and will be added to the next revision (comment 19) Hao raised the issue, whether the edition of the IEEE 802 standards should be mentioned when making references to particular clauses. The chair appreciated the comment and proposed to add within the Normative References chapter the edition year of the referenced IEEE 802 standards. Likely the clauses numbers will maintained in upcoming revisions, but sometimes revisions introduce major rearrangements of the specifications. 14

  15. omniran-17-0037-01-00TG Business #4 Comment resolution of P802.1CF D0.4 https://mentor.ieee.org/omniran/dcn/17/omniran-17-0025-00-CF00-chapt-7-5-8-mapping-to-ieee802-technologies.docx Max introduced his proposal for references to the particular sections in the IEEE 802 specifications. The table seems to be appropriate, however the relation of table entries to the described functions should become clear, i.e. the term filtering does not appear in the text, and the purpose of the function is not obvious from the text. Max will revise the document replacing the term filtering with a term appearing in the specification text. (comment 33) https://mentor.ieee.org/omniran/dcn/17/omniran-17-0026-00-CF00-chapt-7-6-8-mapping-to-ieee802-technologies.docx Max introduced his proposal especially explaining that the term QoS does not appear in the IEEE 802.3 specification at all. Hao asked for the possibility to review the referenced sections in relation to the references in the accounting sections, as references to QoS related attributes are made for accounting as well. Both sections should make use of the same references for the same capabilities. Hao will provide his results for the next conference call. (comment 36) Only open comment missing proposed remedy is comment 47 on missing text for section 8.3 on virtualized network instantiation. Max will create text proposal prior to the next conference call on May 2 Yonggang Fang (ZTETX) for the review meeting. New contributions to 802.1CF No new contribution available for the call AoB Plans for the Stuttgart interim on May 15-18 The chair informed that preliminary planning of the May F2F interim meeting reserved two half days on Monday afternoon and Tuesday afternoon for OmniRAN TG discussions. It was asked to add another half-day meeting time on Wednesday to have sufficient time for comprehensive discussions and careful review of the contributions. The chair will forward the extended demand for meeting time to the Suttgart meeting organizer. When being asked, the chair explained that currently no OmniRAN special session is planned for discussion of input to the IC activity. However such special session could be easily arranged if necessary for moving on with the IC activities. nd, and will explicitly invite Meeting adjourned by chair at 10:59 AM ET. 15

More Related Content