1. doc.: Submission, Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4r Report for March 2015 Session] Date Submitted: [9 Mar 2015] Source: [Patrick Kinney] Company [Kinney Consulting LLC] Address [Chicago area, IL, USA] Voice:[+1.847.960.3715], E-Mail:[pat.kinney@ieee.org] Re: [TG4r Opening& Closing Report for March 2015 Session.] Abstract:[Report for the March Session] Purpose:[] Notice:This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. doc.: Submission, Slide 2 TG4r Meeting Goals  Wednesday 11 March, PM2:  Discussion on expanding the scope of TG4r’s PAR

3. doc.: Submission, Slide 3 The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: –Show slides #1 through #4 of this presentation –Advise the WG attendees that: The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws; Early identification of patent claims which may be essential for the use of standards under development is strongly encouraged; There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under development. –Instruct the WG Secretary to record in the minutes of the relevant WG meeting: That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. –The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance. –It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 12 and 12a on inclusion of potential Essential Patent Claims by incorporation or by reference. Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board. Instructions for the WG Chair Slide 3

4. doc.: Submission, Slide 4 Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: l “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 l “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims l “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such 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) l 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 Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2 l Early identification of holders of potential Essential Patent Claims is strongly encouraged l No duty to perform a patent search Slide #1 Slide 4

5. doc.: Submission, Slide 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 Bylaws http://standards.ieee.org/guides/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/guides/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/board/pat/pat-material.html Slide #2 If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide 5

6. doc.: Submission, Slide 6 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 Slide #3 Slide 6

7. doc.: Submission, Slide 7 Other Guidelines for IEEE WG Meetings l All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. l Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. l Don’t discuss specific license rates, terms, or conditions. l Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. l Technical considerations remain primary focus l Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. l Don’t discuss the status or substance of ongoing or threatened litigation. l 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. Slide #4 Slide 7

8. doc.: Submission Historical Perspective IEEE Std. 802.15.4 has been amended many times with minimal PHY changes necessary to address new markets or market changes Typically, each PHY amendment added only those MAC changes necessary to implement that PHY, in other words it seldom anticipated making those MAC changes applicable to other PHYs, Slide 8

9. doc.: Submission Historical Perspective (cont’d) The current IEEE Std. 802.15.4 is now confusing to the reader as to which MAC operations are compatible with which PHYs Need exists for consistent, standardized methods to apply specific MAC operations to all or almost all PHYs –This would allow the high layer to specify the MAC automatic operation, e.g. a default?, Slide 9

10. doc.: Submission, Slide 10 Current TG4r PAR Scope This amendment integrates wireless ranging techniques and technologies, including those existing within IEEE 802.15.4 and new to IEEE 802.15.4, into a consistent, standardized method addressing the needs of a wide range of applications and PHYs and enabling the interoperability of devices by different vendors using this method. Additionally, the amendment defines necessary MAC and PHY extensions which enable common radio based distance measurements.

11. doc.: Submission Other Modes/Operations with Similar Needs Dynamic Data Rate Selection Dynamic Transmit Power Selection Asymmetric Link Operation Channel Hopping Operation Dynamic Channel Selection Dynamic Preamble Selection Dynamic Modulation Selection Others?, Slide 11

12. doc.: Submission Dynamic Data Rate (DDR) Selection Many PHYs have multiple data rates Data rates are currently specified by a higher layer but often data rates could be better set by the MAC on a link-by-link basis To allow MAC to set the data rate, would need to: –Define an automatic data rate determination algorithm –Define common methods for MAC to select specific PHY data rates, FEC, PHY preambles, etc. Since the MAC already knows whether frames have been dropped DDR selection would allow the MAC to understand the timing parameters, Slide 12

13. doc.: Submission Dynamic Transmit Power Levels (DTPL) Many PHYs have defined multiple transmit power levels Transmit power levels are currently specified by a higher layer but often these levels could be better set by the MAC on a link-by-link basis To allow MAC to set the transmit power level it may need to: –Determine the CSMA impact (note: GTS or TSCH operation would have no affect) –Define a default automatic power level determination algorithm with option to download another –Define common methods for MAC to select specific PHY power levels based upon PHY preambles, PHY FEC, signal strength, failed packets, etc. –Tell the device on the other side of the link what it’s contemplating, Slide 13

14. doc.: Submission Asymmetric Link Operation Asymmetric Link Operation (ALO) is preferred for some networks with many end devices, as it allows the end devices to operate at low energy levels, etc. Example applications include shelf tags, etc. Optimized network operation for high performance device (HPD) along with low performance devices (LPDs) HPDs acting as coordinators enable lower cost LPDs to reduce energy consumption MAC ALO would free the higher layer from having to set up a network with HPDs and LPDs., Slide 14

15. doc.: Submission Channel Hopping Operation Channel Hopping is preferred for some networks operating in interference prone environments. Example applications include smart grid and industrial Channel hopping networks require a: –known hop sequence –a channel white list and a channel black list –a method to alter hop sequence on-the-fly –a method to synchronize, –a known clock (network wide? local area only?) MAC channel hopping would not require the higher layers to understand radio operation, Slide 15

16. doc.: Submission Backward Compatibility Add a new primitive parameter to the primitives e.g. Auto-DDR, Auto-DTPL, Auto- CH, Auto-ALO Older devices would continue to use the current methods, i.e. over-ride the automatic mode Setting Auto-xxx to TRUE would tell the MAC to ignore the legacy values, Slide 16

17. doc.: Submission Proposal to Go Forward 802.15 members requested to seek corporate “buy-in” into this effort Repurpose TG-4r by amending its PAR and CSD (PAR is already MAC/PHY) Set up teams to address each area: ranging, DDR, DTPL, ALO, CHO, etc. Work with existing TGs to coordinate efforts, Slide 17

18. doc.: Submission, Slide 18 Proposed TG4r PAR Modified Scope This amendment integrates wireless ranging techniques and technologies for ranging, dynamic data rates, dynamic transmit power selection, asymmetric link operation, and time scheduled channel hopping (TSCH), including those existing within IEEE 802.15.4 and new to IEEE 802.15.4, into a consistent, standardized methods addressing the needs of a wide range of applications and PHYs and enabling the interoperability of devices by different vendors using thisese methods. Additionally, the amendment defines necessary MAC and PHY extensions which enable common radio based operations such as distance measurements.

19. doc.: Submission, Slide 19 CSD  The CSD would also have to be modified as appropriate

20. doc.: Submission Conference Call Thursday, 16 April at 16:00 BST, Slide 20