70 likes | 76 Views
This document provides resolutions for three beamforming comments related to command frames, beamforming IE, and codebooks.
E N D
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [DF00 Beamforming Related Comment Resolutions: Part IV] Date Submitted: [Sept 3, 2008] Source: [Junyi Wang, Zhou Lan, Chang woo Pyo, Chin-Sean Sum, Tuncer Baykas, Azizur Rahman, Ryuhei Funada, Fumihide Kojima,Hiroshi Harada, Shuzo Kato, Ismail Lakkis+, Jisung Oh*, Huai Rong Shao*, Su-Khiong Yong*] Company [National Institute of Information and Communications Technology (NICT), Tensorcom, Samsung ] Address1[3-4 Hikari-no-oka, Yokosuka-shi, Kanagawa 239-0847, Japan; 10875 Rancho Bernardo Rd, #108, San Diego, CA 92127+; 416 Maetan-3Dong Yeongtong-Gu Suwon-shi Kyunggi-Do 443-742, Korea*] Voice1:[+81-46-847-5074] , FAX1: [+81-46-847-5440] E-Mail[junyi.wang@nict.go.jp] Re: [] Abstract: [Comment Resolutions related to Beamforming in DF00] Purpose:[ ] 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.
Summary • This document provides the resolutions for the following 3 Beamformingcomments • 2 comments for command frame and beamforming IE • 44, 492 • 1 comment for code book • 431
Comment 44: I don't see where this (Response TX sector) is further used. Delete if not used again in the draft. (pg.40 Line 37, subclause 7.5.1.1) • Resolution: • Add sentences at line 41 page 40 • The Response TXsectoristhe PNC TX sector that the PNC should use for further quasi-omni transmissions to the DEV • Modify sentences line 46-47 page 46 • “The DEV shall include the information of the best PNC quasi-omni transmit direction in its Association Request commands defined in 7.5.1.1 to inform the PNC the best PNC quasi-omni transmit direction for further quasi-omni transmissions to the DEV”
Comment 492: Value for 0010-1101 does not specify but indicated as tracking period. • Suggestion from the owner : specify the value • (subclause 7.4.28, Figure 48e, p35) • Resolution: • Some sentences will be added in L49, p34 • The Best Cluster Tracking Period and Second Best Cluster Tracking Period fields shall be set to the tracking period of the best cluster and the second best cluster, respectively. The Tracking Period fields shall be encoded as defined in Table 48e, where 0000 is reserved for that the tracking period is lower than 4us; The tracking period for 0010-1101 shall be less than 16ms and larger than 4us, . the values shall be set by implementer; 1111 is reserved for that the tracking period is larger than 16ms • The Table 48e will be revised as follows • The specified value for 0010-1101 will be set during next telecon. Table 48e – Tracking period encoding
Table 48e – Tracking period encoding • Comment 492 (cont’s) • Resolution: • Redefine Table 48e
Comment 431: The Beam forming codebooks seem to be tied to one specific antenna architecture and limited flexibility. Can't we define something more generic? (pg.162 Line 42, subclause 13.2) • Suggestion from the commenter: Redefine codebook to accommodate different antenna spacings and architectures. • Resolution: • No changes are needed. Codebooks are optimal for 1D and 2D antenna arrays with uniform spacing of half wavelength. It is suboptimal for different spacing. In all cases, the BST criterion can be used for any antenna configuration and is the most general.