<month year> doc.: IEEE s May 2015

Slides:



Advertisements
Similar presentations
Doc.: IEEE s Submission March 2015 Hidetoshi Yokora, Landis&GyrSlide 1 Project: IEEE P Working Group for Wireless Personal Area.
Advertisements

Doc.: IEEE s Submission July 2015 Hidetoshi Yokora, Landis&GyrSlide 1 Project: IEEE P Working Group for Wireless Personal Area.
Doc.: IEEE s Submission May 2015 Hidetoshi Yokora, Landis&GyrSlide 1 Project: IEEE P Working Group for Wireless Personal Area.
<month year> doc.: IEEE s November 2015
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
<month year> doc.: IEEE <# > <April 2008>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Add name of submission] Date Submitted:
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Handling of non-ULI frame and Profile.
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<month year> doc.: IEEE < e>
July 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4s Closing Report for July 2015] Date Submitted:
March 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4s Closing Report for March 2016] Date.
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI “Profile” for Protocol Management] Date.
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE < e>
<month year> <doc.: IEEE doc> September 2015
<month year> doc.: IEEE s March 2016
<month year> <doc.: IEEE doc> December 2015
Source: [Pat Kinney] Company [Kinney Consulting LLC]
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> November 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [Frame and packet structure in ]
doc.: IEEE <doc#>
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Simplified geometry for the usage model.
<month year> <doc.: IEEE doc> May 2015
<month year> <doc.: IEEE doc> May 2015
<month year>20 Jan 2006
doc.: IEEE <doc#>
<month year> doc.: IEEE < e>
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> January 2016
<month year> doc.: IEEE s July 2015
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
May 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4s Closing Report for May 2015] Date Submitted:
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE s March 2019
doc.: IEEE <doc#>
November 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: SRU IG Closing Report for Dallas November.
<month year> <doc.: IEEE doc> July 2015
<month year> doc.: IEEE s November 2015
<month year> doc.: IEEE <030158r0> <March 2003>
<month year> doc.: IEEE s January 2016
<month year> doc.: IEEE s March 2019
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
September 2009doc.: IEEE wng0
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
<month year> <doc.: IEEE doc> September 2015
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Improve the latency between GTS request.
<month year> <doc.: IEEE doc> March 2015
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
<month year> doc.: IEEE s September 2019
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

<month year> doc.: IEEE 802.15-15-0327-00-004s May 2015 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for SRMM General Requirements in Technical Guidance Document] Date Submitted: [6 May, 2015] Source: [Hidetoshi Yokota] Company [Landis&Gyr] Address [1-2-9 Nishi Shimbashi Minato-ku, Tokyo 105-0003, Japan] Voice:[+81 3-5532-7455], FAX: [+81 3-5532-7519], E-Mail:[hidetoshi.yokota@landisgyr.com] Re: [“TG4s Technical Guidance Document”, IEEE 802.15-14-0555-04-004s] Abstract: [This contribution proposes general requirements that should be considered in the Technical Guidance Document in order to apply Spectrum Resource Management in the field of AMI (Advanced Metering Infrastructure).] Purpose: [Discussion and approval] 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. Hidetoshi Yokora, Landis&Gyr <author>, <company>

Proposal for SRMM General Requirements in Technical Guidance Document <month year> doc.: IEEE 802.15-15-0327-00-004s May 2015 Proposal for SRMM General Requirements in Technical Guidance Document Authors: Hidetoshi Yokora, Landis&Gyr <author>, <company>

General requirements Support of active and passive link measurements Link measurement request/report for instantaneous SRM (active) Cumulative SRMM information request/report for averaged SRM (passive) Equivalent functionality is supported in 802.11k RRM Support of advance SRMM information retrieval SRM information IE in the beacon frame could help a device select optimal PAN

General requirements (cont’d) Support of multihop mesh topology 802.11 WLAN 802.15 WPAN PAN request report request STA AP report Relay device (FFD) request report Requesting device (PAN Coordinator) STA Target device

General requirements (cont’d) Support of piggyback report Could reduce the number of request/report packets Could correlation of measurements on the path more easily Specific flag should be defined measurement measurement measurement M3 M2 M1 request request request N3 N2 N1 N0 Report (M3) Report (M3| M2) Report (M3|M2|M1) Target device

Proposal for General descriptions (Section 4) 4.2 General requirement of SRMM A device should be able to request another device to conduct spectrum resource measurements. A device should be able to conduct and report spectrum resource measurements at the time of receiving a request from another device, at a predefined interval or on a predefined condition. A device should be able to provide spectrum resource measurements information to another device before its joining (e.g., in the form of the beacon frame). Intermediate device(s) between the requesting and requested (target) devices should be able to relay the spectrum resource measurement request. Intermediate device(s) should be able to piggy back its own measurement information when relaying the report from the requested device to the requesting device.

Proposal for General descriptions (cont’d) 4.x Spectrum Resource Measurement Request Structure SRM request header should include the following: Requesting device ID, PAN ID Measurement type Measurement mode (e.g., autonomous, triggered) Measurement duration Relay mode (e.g., through, piggy back)