Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment resolution #187] Date Submitted: [Nov-13-2008] Source: [Chang woo Pyo1, Zhou Lan1, Fumihide Kojima1, Hiroyuki Nakase1, Hirosh Harada1, Shuzo Kato1 , Huai-Rong Shao2, Edwin Kwon2, Su-Khiong Yong2, Jisung Oh2, Chiu Ngo2, Seongsoo Kim2, Vered Bar 3] Company: [NICT 1, Samsung2, Qualcomm 3] Address: [] Voice: [], FAX: [], E-Mail:[] Re: [] Abstract: [Comment resolution #187] Purpose: [To be considered in IEEE 802.15.3c standard] 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.

2. Directional communication in CAP • Comment • Suggested Resolution • Non-directional DEV-DEV communication is followed by 802.15.3b • Directional DEV-DEV communication • Specify “Directional peer IE” to allow directional DEV and DEV communication in Regular CAP

3. Directional peer IE (1/2) • Directional peer IE allows a pair of DEVs directionally communicate with each other in the Regular CAP • Directional peer IE shall be formatted as illustrated in Figure xx. • The SrcID field contains the DEVID of the source for the regular CAP • The DestID field contains the DEVID of the destination for the regular CAP • The Configuration field indicates the following • b0 - 0 indicates request of directional communication, 1 indicates release of directional communication • b1 - 0 indicates uni-directional, 1 indicates bi-directional communication • The Allocated Superframes field contains the number of superframes as the allocating time for communication directionally between Source DEV to Destination DEV Figure xx. Directional peer information element format

4. Directional peer IE (2/2) • Directional peer communication in the Regular CAP • Add the following sentences on 8.8.6.2 “Before two peer DEVs communicate in the regular CAP, the two DEVs may perform beam forming, as described in 13.4, if they do not know the antenna directions to point to each other. To support directional peer communication in the regular CAP, the source DEV may send the PNC an Announce command with directional peer IE in which “Request/Release bit” is set to “1”, as described in x.x. If the PNC can allow the directional peer communication, the PNC shall includes the directional peer IE in the beacon to announce that the two devices will use regular CAP for directional peer communication. After the source and destination DEVs receive the directional peer IE in the beacon from the PNC , the two DEVs may switch their antenna directions and communicate with each other in the regular CAP. After the two devices complete directional peer communication, the source device may send the PNC an Announce command with directional peer IE in which “Request/Release bit” is set to “0”, and the PNC shall remove directional peer IE from its beacon.”