doc.: IEEE <doc#>

Slides:



Advertisements
Similar presentations
Doc.: IEEE Submission May 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
Advertisements

Doc.: IEEE m SubmissionSlide 1 Nov Project: IEEE P Working Group for Wireless Personal Area Networks(WPANs) Submission.
Doc.: IEEE Submission Aug Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
Doc.: IEEE Submission Oct Slide 1 Sangjae Lee (ETRI) et al Project: IEEE P Working Group for Wireless Personal Area.
Doc.: IEEE Submission May 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
Doc.: IEEE Submission Oct Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
Doc.: IEEE Submission Oct Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
Doc.: IEEE Submission Oct Slide 1 Sangjae Lee (ETRI) et al Project: IEEE P Working Group for Wireless Personal Area.
Doc.: IEEE Submission Oct Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [Add name of submission]
doc.: IEEE <doc#>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
doc.: IEEE <doc#>
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> January 2016
doc.: IEEE <doc#>
May 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [19 May 2016]
doc.: IEEE <doc#1>
doc.: IEEE <doc#>
<month year> doc.: IEEE s March 2019
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE g-Trends-in-SUN-capacity
March 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [16 March.
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE < nnn-00-0mag>
<month year> <doc.: IEEE doc> March 2015
September 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [17.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
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: MLME-SOUNDING and MLME-CALIBRATE comment.
Presentation transcript:

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Proposed Resolution for Comment CIDs R96 and R97 from Charlie Perkins Date Submitted: August 13, 2015 Source: Jaehwan Kim (ETRI), Soo-Young Chang (SYCA), Jaebeom Kim (Ajou Univ.), and Sangsung Choi (ETRI) Company: ETRI, SYCA, Ajou Univ. Address: Voice: +82 42 850 5338, E-Mail: kimj@etri.re.kr Re: Abstract: Proposed comment resolution for comments suggested by Charlie Perkins in 15-15-0391-00 and 15-15-0399-00 on the draft of TG10 L2R routing Purpose: To suggest a comment resolution for Letter Ballot #104 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. Soo-Young Chang (SYCA) et al <author>, <company>

Aug. 2015 Introduction In this document, proposed resolutions for two comments from Charlie Perkins listed in 15-15-391-00 and 15-15-0399-00 are prepared. Comments R96 and R97 which are related to Clause 5.2.2.1 Soo-Young Chang (SYCA) et al

Comment CID R96 Commentor Related clause Comment Proposed Change Aug. 2015 Comment CID R96 Commentor Charlie Perkins Related clause 5.2.2.1 P 26 line 25 Comment How are the metric parameters known by all devices in PAN? For the Inactive Time Aware metric to work, these parameters must be known to all devices Proposed Change Explain or modify Soo-Young Chang (SYCA) et al

Explanation for Comment R96 Aug. 2015 Explanation for Comment R96 Explanation Parameter information can be known by all PAN devices. These devices can get BO and SO values which are included in beacon messages received in the association procedure. Basically the devices also know other parameter values such as transmission rate. Soo-Young Chang (SYCA) et al

Comment CID R97 Commentor Related clause Comment Proposed Change Aug. 2015 Comment CID R97 Commentor Charlie Perkins Related clause 5.2.2.1 P 26 line 33 Comment Why use maximum frame size instead of average? Average frame size would provide a measurement more meaningful for the particular network Proposed Change Explain or modify Soo-Young Chang (SYCA) et al

Explanation for Comment R97 Aug. 2015 Explanation for Comment R97 Explanation The maximum frame size is pre-defined value. To use an average frame size, an additional definition using a mathematical expression is required. Moreover, the average frame size based link metric may invoke false positive route decision error in the case that this value varies in the broad range of values. Therefore the maximum is used in this draft. Soo-Young Chang (SYCA) et al

Proposed Resolution for Comments R96 and R97 (Accept in Principle) Aug. 2015 Proposed Resolution for Comments R96 and R97 (Accept in Principle) Proposed resolution Change the first sentence in Page 26, line 17 where O, bt, SO and BO are variables described in Table 5. BO and SO values are included in beacon message of the PAN coordinator. Maximum frame size is utilized for bt in this metric. Add the sentences are already inserted to page 26, line 22 Using the maximum frame size enables a simple representation across a broad range of link conditions and traffic conditions. This has advantages over other strategies such as using the average frame size, especially in very lossy environments. Soo-Young Chang (SYCA) et al