<month year> doc.: IEEE s February 2019

Slides:



Advertisements
Similar presentations
<month year> doc.: IEEE s November 2015
Advertisements

Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI “Profile” for Protocol Management] Date.
doc.: IEEE <doc#>
<month year> doc.: IEEE s May 2015
Submission Title: [Resolution on comment #20,22 and 30]
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 1014 Proposed Partial Resolution.
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 <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal of ULI primitives for handling profiles]
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for ULI primitives] Date Submitted:
January 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Sub-GHz proposal for ] Date Submitted:
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for ULI primitives] Date Submitted:
Submission Title: [Comment Resolutions for #309, #310, and #314]
<May,2009> doc.: IEEE <doc .....> <July 2009>
July 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4s Closing Report for July 2015] Date Submitted:
<month year> doc.: IEEE <xyz> January 2001
doc.: IEEE <doc#>
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI “Profile” for Protocol Management] Date.
doc.: IEEE <doc#>
Submission Title: [Resolution on comment #20,22 and 30]
January 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Sub-GHz proposal for ] Date Submitted:
<month year> doc.: IEEE s March 2016
Submission Title: [Comment Resolutions for #309, #310, and #314]
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE <xyz> November 2000
Submission Title: [IEEE WPAN Mesh Reference Model]
March 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [16 March.
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
Submission Title: [Frame and packet structure in ]
Submission Title: Rogue Resolutions from kivinen
<month year> doc.: IEEE s March 2019
<month year> doc.: IEEE s March 2019
<month year> doc.: IEEE s March 2019
doc.: IEEE <doc#>
<month year> doc.: IEEE s July 2015
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
<month year> doc.: IEEE s March 2019
May 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [19 May 2016]
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 1014 Proposed Partial Resolution.
<month year> doc.: IEEE s March 2019
Submission Title: [Channel Bands Update]
<month year> doc.: IEEE s February 2019
Submission Title: [Proposed resolution to cid#1064]
Submission Title: Rogue Resolutions from kivinen
March 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [16 March.
<month year> doc.: IEEE s November 2015
<month year> doc.: IEEE s March 2019
<month year> doc.: IEEE s January 2016
<month year> doc.: IEEE s March 2019
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
doc.: IEEE <doc#>
<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: CID 422 Proposal Date Submitted: 14 August,
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: More LB156 Comment Resolution Date Submitted:
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: More LB156 Comment Resolution Date Submitted:
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.
<month year> doc.: IEEE s September 2019
<month year> doc.: IEEE s September 2019
Presentation transcript:

<month year> doc.: IEEE 802.15-15-0850-00-004s February 2019 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Revised proposal of SRM Request/Response flows and primitives] Date Submitted: [28 February, 2019] Source: [Hidetoshi Yokota, Shoichi Kitazawa] Company [Landis&Gyr, Muroran IT] Address: [Tokyo Japan, Hokkaido Japan] Voice: [], E-Mail: [hidetoshi.yokota@landisgyr.com, kitazawa@ieee.org] Re: [Proposal of SRM Request/Response flows and primitives] Abstract: [This contribution proposes new SRM Request/Response flows and corresponding primitives based on the discussion in TG4md CRG.] Purpose: [Discussion] 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 Yokota and Shoichi Kitazawa <H.Yokota>, <Landis&Gyr>

Current flow of SRM Request/Response (1) February 2019 Current flow of SRM Request/Response (1) Figure 6-85 (Page 166, Sub clause 6.17.2.3, Line#1) Device next higher layer Device MLME Device MLME Device next higher layer MLME-SRM.request SRM Request MLME-SRM.indication MLME-GET.request MAC PIB MLME-GET.confirm MLME-SRM.response SRM Response MLME-SRM.confirm Example procedure Hidetoshi Yokota and Shoichi Kitazawa

Current flow of SRM Request/Response (2) February 2019 Current flow of SRM Request/Response (2) Figure 6-86 (Page 166, Sub clause 6.17.2.3, Line#5) Device next higher layer Device MLME Device MLME Device next higher layer MLME-SRM.request (TPC) SRM Request (TPC) (*) Device PHY MLME-SET.request TPC process MLME-SET.confirm SRM Response MLME-SRM.confirm Example procedure Hidetoshi Yokota and Shoichi Kitazawa

Modified flow of SRM Request/Response (1) February 2019 Modified flow of SRM Request/Response (1) Initiating device does not need to wait for SRM Response, which supports the case for a long-term measurement or the case where the completion of the measurement is not predictable. Device next higher layer Device MLME Device MLME Device next higher layer MLME-SRM-REQ.request SRM Request MLME-SRM-REQ.confirm MLME-SRM-REQ.indication MLME-GET.request MAC PIB MLME-GET.confirm MLME-SRM-RES.request SRM Response MLME-SRM-RES.indication MLME-SRM-RES.confirm Example procedure Hidetoshi Yokota and Shoichi Kitazawa

Modified flow of SRM Request/Response (2) February 2019 Modified flow of SRM Request/Response (2) Device next higher layer Device MLME Device MLME Device next higher layer MLME-SRM-REQ.request (TPC) SRM Request (TPC) (*) MLME-SRM-REQ.confirm Device PHY MLME-SET.request TPC process MLME-SET.confirm SRM Response MLME-SRM-RES.indication Example procedure Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-REQ.confirm and its parameters February 2019 Proposal for MLME-SRM-REQ.confirm and its parameters Add sub-clause 8.2.26.4: 8.2.26.4 MLME-SRM-REQ.confirm The MLME-SRM-REQ.confirm primitive reports the results of the MLME-SRM-REQ.request. The semantics of this primitive are as follows: MLME-SRM-REQ.confirm ( SrmHandle, DeviceAddrMode, DeviceAddress, Status ) The primitive parameters are defined in Table 8-78. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-REQ.confirm and its parameter (cont’d) February 2019 Proposal for MLME-SRM-REQ.confirm and its parameter (cont’d) Table 8-78 --- MLME-SRM-REQ.confirm parameters Name Type Valid range Description SrmHandle Integer 0x00–0xff The identifier of the corresponding MLME-SRM-REQ.request primitive. DeviceAddrMode Enumeration SHORT, EXTENDED The addressing mode of the device requesting to execute SRM operation. DeviceAddress Short address or extended address As specified by the Parameter The address of the device requesting to execute SRM operation. Status CHANNEL_ACCESS_FAILURE, NO_ACK, SUCCESS The status of the SRM Request attempt. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES.request parameters February 2019 Proposal for MLME-SRM-RES.request parameters Change Sub-clause 8.2.26.3 as follows. The parameters in the primitive are the same as those in the original MLME-SRM.response 8.2.26.3 MLME-SRM-RES.request The MLME-SRM-RES.request primitive is used to initiate a response to an MLME-SRM-REQ.indication primitive. The semantics of this primitive are as follows: MLME-SRM-RES.request ( ... ) The primitive parameters are defined in Table 8-77, which are provide by the device next higher layer. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES.request parameters (cont’d) February 2019 Proposal for MLME-SRM-RES.request parameters (cont’d) Add or change the following parameters in red on Table 8-77: Table 8-77 --- MLME-SRM-RES.request parameters Name Type Valid range Description SrmHandle Integer 0x00-0xff An identifier which can be used to refer to the particular primitive transaction; used to match an SRM Response with the corresponding SRM Request. DeviceAddrMode Enumeration SHORT, EXTENDED The addressing mode of the device requesting to execute SRM operation. DeviceAddress Short address or extended Address in 7.4.3 As specified by the Parameter The address of the device requesting to execute SRM operation. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES.request parameters (cont’d) February 2019 Proposal for MLME-SRM-RES.request parameters (cont’d) PayloadIeList Set of payload IEs as described in 7.4.3 --- The payload IEs, excluding Termination IEs, that are provided by the device next higher layer. If empty, then no payload IEs are included. The rest of the parameters are the same as in Table 8-77 Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES. indication parameters February 2019 Proposal for MLME-SRM-RES. indication parameters Add Sub-clause 8.2.26.3a as follows: 8.2.26.3a MLME-SRM-RES.indication The MLME-SRM-RES.indication primitive is used to report the reception of an MLME-SRM Response command. The semantics of this primitive are as follows: Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES. indication parameters (cont’d) February 2019 Proposal for MLME-SRM-RES. indication parameters (cont’d) MLME-SRM-RES.indication ( SrmHandle DeviceAddrMode, DeviceAddress, PayloadIeList, MeasureddDeviceAddr, MeasuredDeviceAddress, Status, SecurityLevel, KeyIdMode, KeySource, KeyIndex ) The primitive parameters are defined in Table 8-77a. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES. indication parameters (cont’d) February 2019 Proposal for MLME-SRM-RES. indication parameters (cont’d) Add the following table: Table 8-77a --- MLME-SRM-RES.indication parameters Name Type Valid range Description SrmHandle Integer 0x00-0xff An identifier which can be used to refer to the particular primitive transaction; used to match an indication primitive with the corresponding MLME-SRM-REQ.request. DeviceAddrMode Enumeration SHORT, EXTENDED The addressing mode of the device requesting to execute SRM operation. DeviceAddress Short address or extended Address As specified by the DeviceAddrMode Parameter The address of the device requesting to execute SRM operation. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES. indication parameters (cont’d) February 2019 Proposal for MLME-SRM-RES. indication parameters (cont’d) PayloadIeList Set of payload IEs as described in 7.4.3 --- The SRM-related payload IEs, excluding Termination IEs, that were included in the frame. If empty, then no payload IEs are included. MeasuredDeviceAddrMode Enumeration SHORT, EXTENDED The addressing mode of the device, for which the measurement was executed MeasuredDeviceAddress Short address or extended address As specified by the DeviceAddrMode Parameter The address of the device, for which the measurement was executed. Status SUCCESS, NON_SUPPORTED, REJECTED The status of the SRM attempt. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES. indication parameters (cont’d) February 2019 Proposal for MLME-SRM-RES. indication parameters (cont’d) SecurityLevel Integer As defined in Table 8-77 As defined in Table 8-77. KeyIdMode KeySource Set of octets KeyIndex Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES.confirm parameters February 2019 Proposal for MLME-SRM-RES.confirm parameters Add sub clause 8.2.26.3b and Table 8-77b as follows: 8.2.26.3b MLME-SRM-RES.confirm The MLME-SRM-RES.confirm primitive reports the results of the MLME-SRM-RES.request. The semantics of this primitive are as follows: MLME-SRM-RES.confirm ( SrmHandle, DeviceAddrMode, DeviceAddress, Status ) The primitive parameters are defined in Table 8-77a. Hidetoshi Yokota and Shoichi Kitazawa

Proposal for MLME-SRM-RES.confirm parameters (cont’d) February 2019 Proposal for MLME-SRM-RES.confirm parameters (cont’d) Table 8-77b --- MLME-SRM-RES.confirm parameters Name Type Valid range Description SrmHandle Integer 0x00–0xff The identifier of the corresponding MLME-SRM-RES.request primitive. DeviceAddrMode Enumeration SHORT, EXTENDED The addressing mode of the device requesting to execute SRM operation. DeviceAddress Short address or extended address As specified by the Parameter The address of the device requesting to execute SRM operation. Status CHANNEL_ACCESS_FAILURE, NO_ACK, SUCCESS The status of SRM Response attempt. Hidetoshi Yokota and Shoichi Kitazawa