Tg3e Comment Resolution for i-232,i-233 of Sponsor Ballot

September, 2016 IEEE P802.15-16-0710-02-003e

IEEE P802.15

Wireless Personal Area Networks

Project	IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Title	TG3e Comment Resolution for i-232,i-233 of Sponsor Ballot
Date Submitted	29, Sep. 2016
Source	[Kondou, Keitarou;Akiyama, Keiji] [Sony Semiconductor Solutions Corp.] [1-7-1 Konan, Minato-ku, Tokyo Japan]	Voice: [ [phone]] Fax: [ [phone]] E-mail: [[e-mail] , [e-mail] ]
Re:	In response to i-232, i-233 from consolidated sponsor ballot comments (15-16-0585-00-003e)
Abstract	Add description of Association procedure when DEVID or DEV address are unmatched
Purpose	To respond comment id i-232,233
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.

List of contributors

Name	Affiliation
Itaru Maekawa	Japan Radio Co., Ltd.
Kiyoshi Toshimitsu	Toshiba Corporation
Keitarou Kondou	Sony Semiconductor Solutions Corp.
Keiji Akiyama	Sony Semiconductor Solutions Corp.

Comment

Comment #	Page	Subclause	Line	Comment	Must Be Satisfied	Proposed Change
i-232		7.3a.1		It is better to specify the behaviour when the DEVID in the Association Request command is different from the value of the Next DEVID in the beacon for clarity.	No	Specify the behaviour when the DEVID in the Association Request command is different from the value of the Next DEVID in the beacon
i-233		7.3a.1		What happens if the DEV address in the Association Response command does not match with the DEV address of the receiving DEV?	No	Add description for the case mentioned in the comment.

Resolution:

Add descriptions for both behaviors to make them clear

[Resolution for i-232,233]

7.3a.1 Association
Insert the underlined sentences in the second paragraph of 7.3a.1 as indicated;
Before an HRCP DEV has completed the association process, all frames sent to the HRCP PNC by the HRCP DEV shall be exchanged in the PPAP of the superframe. An unassociated HRCP DEV initiates the association process by sending an Association Request command, as described in 6.5.1.1, to the HRCP PNC. An unassociated HRCP DEV can send an Association Request by selecting an access slot at random, after receiving every beacon and starts Association timeout timer. The duration of an Access Slot consists of the length of an Association Request Command and a SIFS. Carrier sense for sending an Association Request is not required. Association Request commands shall be sent with No-ACK policy.

When the HRCP PNC receives one of the Association Request commands, whose DEVID is the same value as the Next DEVID in the beacon, it shall stop sending the beacon, send an Association Response command instead with the same timing as the beacon or later, and start Association timeout timer. If the HRCP PNC receives the Association Request command whose DEVID does not match with the value of Next DEVID in the beacon, the HRCP PNC shall not respond to the command and shall continue sending beacons.

If an HRCP DEV received the Association Response command with the DEV address matching its own, the HRCP DEV becomes an associated HRCP DEV and sends the Stk-ACK to the Association Response command to the PNC.

If the DEV address in the Association Response command does not match with the HRCP DEV’s own DEV address, the HRCP DEV shall ignore the command.

If an associated HRCP DEV or an unassociated non-PNC HRCP DEV which has initiated an association process by sending an Association Request command receives a beacon with a different Next DEVID, it shall ignore this beacon. The HRCP PNC may maintain a list of DEV addresses that are allowed to join the pairnet. If the list is in use, when the HRCP PNC receives the Association Request command, the HRCP PNC shall consult the list to determine if the DEV address in the request is included. If the DEV address is not in the list, the HRCP PNC may send a disassociation command.

Insert the underlined parameters in MLME-ASSOCIATE.response primitive as indicated;
5.3.5.4 MLME-ASSOCIATE.response
MLME-ASSOCIATE.response (

Devid,

PncAddress,

ResultCode,

ReasonCode

)

Submission Page Kondou, Keitarou;Akiyama, Keiji, Sony Semiconductor Solutions Corp.