doc.: IEEE <doc#>

Slides:



Advertisements
Similar presentations
Doc.: IEEE e Submission Kondou (Sony)Slide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission.
Advertisements

Submission Title: [Resolution on comment #20,22 and 30]
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
doc.: IEEE <doc#>
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#>
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>
September 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment resolution for i-024 and i-151.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution of CID 139] Date Submitted:
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
doc.: IEEE <doc#>
doc.: IEEE <doc#>
September 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment resolution for i-024 and i-151.
doc.: IEEE /XXXr0 Sep 19, 2007 July 2008
Submission Title: [Resolution on comment #20,22 and 30]
Submission Title: [Resolutions for CID 85, 86, and 87]
<month year> <doc.: IEEE doc> December 2015
Submission Title: [Proposed resolution to CID#133]
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> November 2000
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [Proposed resolution to CID#133]
<month year> <doc.: IEEE doc> May 2015
<month year>20 Jan 2006
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> January 2016
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
July 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Proposal for Radio Specification Comments.
doc.: IEEE <doc#1>
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE s March 2019
doc.: IEEE <doc#>
Submission Title: [Proposed resolution to cid#1064]
Submission Title: [ e Schedule Update]
<month year> <doc.: IEEE doc> July 2015
Submission Title: [LB 28 Results] Date Submitted: [14 March 2005]
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
doc.: IEEE <doc#>
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
doc.: IEEE < nnn-00-0mag>
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
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Summary.
<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,
doc.: IEEE <doc#>
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> <Jan. 2016> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Modification of capability for notifying supported kinds* of SIFS] Date Submitted: [18 January 2016] Source: [Keitarou Kondou] Company: [Sony Corporation] Address1: [1-7-1 Konan, Minato-ku, Tokyo 108-0075] E-Mail1: [keitarou.Kondou at jp.sony.com] Abstract: This document presents the method for selecting SIFS duration. Purpose: To modify the current TG3e draft document. 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 contributors acknowledge and accept that this contribution becomes the property of IEEE and may be made publicly available by P802.15. Kondou (Sony) <author>, <company>

Must Be Satisfied? (Yes or No) <Jan. 2016> MAC CID #1055 CID Submitter Name Affiliation Page Sub-clause Line # Comment Proposed Change E/T Must Be Satisfied? (Yes or No) 1055 K.Kondou Sony 39 6.4.1.1 1 Both SC and OOK PHY defines three kinds of duration for SIFS. But no procedure to choose duration among them is provided in MAC part. Define shortest SIFS field in capablity IE and add a new SIFS IE, so that DEVs can exchange capabilities in the assosiation process and notify a determined duration in the Association Response with a SIFS IE. T Yes Kondou (Sony)

SIFS duration defined in current draft <Jan. 2016> SIFS duration defined in current draft Both HRCP-SC (Table 11a-19) and HRCP-OOK(11a-31) PHY define several kinds of duration for SIFS, but no selection method is provided. Variety kinds of SIFS allows both cost effective or descent performance devices exist. Kondou (Sony)

Suggested modification <Jan. 2016> Suggested modification Add supported SIFS encoding field to current capability field to indicate shortest SIFS duration supported at each device. In case supported SIFS encoding field value is 10000, from 1.6 to 2.5 µs of SIFS duration is supported. Table X-XX – Supported SIFS encoding Field value SIFS duration 00000 0.0 µs 00001 0.1 µs 00010 0.2 µs 11000 2.4 µs 11001 2.5 µs 11010-11111 reserved Kondou (Sony)

<Jan. 2016> How it works Exchange values of SIFS in Unassociated Phase and determined value shall be used in Associated Phase. Figure 4-2a – One cycle of PPAP includes SIFS_PPC SIFS duration of 2.5 µs (default) Use SIFS duration of SIFS_ASSOC includes SIFS_DEV SIFS_PPC: shortest SIFS supported in the PPC SIFS_DEV: shortest SIFS supported in the DEV SIFS_ASSOC: shortest SIFS supported in both DEVs Kondou (Sony)

Further discussions Is one SIFS duration is enough for a session? <Jan. 2016> Further discussions Is one SIFS duration is enough for a session? Need to provide the mechanism to change the SIFS duration within Associated Phase? No objection for using fixed SIFS duration for an Associated Phase at the meeting Kondou (Sony)