D0.2 Comment Resolution on CID 368 Month Year doc.: IEEE 802.11-07/xxxxr0 September 2010 D0.2 Comment Resolution on CID 368 Date: 2010-09-14 Authors: Name Affiliations Address Phone Email Kapseok Chang ETRI 138 Gajeongno, Yuseong-gu, Daejeon, 305-700, Korea +82-42-860-1639 kschang@etri.re.kr Yongsun Kim doori@etri.re.kr Seung Eun Hong iptvguru@etri.re.kr Hoosung Lee hslee@etri.re.kr Woo Yong Lee wylee@etri.re.kr Hyun Kyu Chung hkchung@etri.re.kr Kapseok Chang (ETRI) VInko Erceg, Broadcom

Outline Comment on CID 368 Proposed resolution September 2010 Month Year doc.: IEEE 802.11-07/xxxxr0 September 2010 Outline Comment on CID 368 Proposed resolution Kapseok Chang (ETRI) VInko Erceg, Broadcom

Comment on CID 368 Comment detail September 2010 Comment ID Subclause Month Year doc.: IEEE 802.11-07/xxxxr0 September 2010 Comment on CID 368 Comment detail Comment ID Subclause Page Line Comment Type Comment Suggested Remedy 368 11.37.3.1 298 30 TR Where we can find the value and definition of "dot11RelayTPATime" Add dot11 MIB definition and value Kapseok Chang (ETRI) VInko Erceg, Broadcom

Proposed resolution (1/5) Month Year doc.: IEEE 802.11-07/xxxxr0 September 2010 Proposed resolution (1/5) dot11RelayTPATime is included in link cooperating type. Link Cooperating type [1] The RSUS is actively involved in the direct link communication between S-D. At the same time, a frame transmission from the source RUS to the destination RUS is repeated by the RSUS. It can possibly increase the signal quality received at the destination RUS. For realization of the Link cooperating, it is needed as follows, Additional Relay setup procedure (i.e., Transmission time-Point Adjustment (TPA)) for Receive multi-synchronization at the destination RUS Frame exchange and link feedback rule S-D Direct link S-R Relay link R-D Relay link Source RUS Destination RSUS STA Cooperation Kapseok Chang, ETRI VInko Erceg, Broadcom

Proposed resolution (2/5) September 2010 Proposed resolution (2/5) At dot11RelayTPATime from the end of the last TPA Request frame transmitted by the destination RUS to the source RUS, the destination RUS shall send a TPA Request frame to the RSUS and set the Response Offset field to the Dtime when the RSUS shall transmit a TPA Response frame back to the destination RUS, and set the timing offset field to dTDS-dTDR. Kapseok Chang (ETRI)

Proposed resolution (3/5) September 2010 Proposed resolution (3/5) Discussion dot11RelayTPATime occupies one D-S propagation delay, one S-R propagation delay, one SBIFS, one TPA Request frame time, and two times of Dtime and TPA Response frame time. Dtime can be fixed to be SBIFS+TPA Request frame time. Use maximum propagation delay, since D does not know these exact delays. It is reasonable to define the Relay TPA time as “constant” in MAC sublayer. Kapseok Chang (ETRI)

Proposed resolution (4/5) September 2010 Proposed resolution (4/5) Proposed change: Counter 11.37.3.1 TPA procedure Change the name of “dot11RelayTPATime” to “aRelayTPATime” throughout the spec. Change the name of “Dtime” throughout subclause 11.37.3.1 to “aDtime”. Remove “Response Offset” subfield in Table 49 (TPA request frame body) in subclause 7.4.13.24 (TPA request). Add “aDtime” and “aRelayTPATime” to “Table 66 – MAC sublayer parameters” in subclause 11.36 [2], and define these as below. Edit “subclauses 7.4.13.24, 11.36, and 11.37.3.1 [2]” in order to correspond to the above bullets (see slide 8). Parameter Value aDtime aSBIFSTime+TXTIME(TPA Request frame) aRelayTPATime aSBIFSTime+2*aAirPropagationTime+2*aDtime+ TXTIME(TPA Request frame)+2*TXTIME(TPA Response frame) Kapseok Chang (ETRI)

Proposed resolution (5/5) September 2010 Proposed resolution (5/5) Edited subclauses 7.4.13.24, 11.36, and 11.37.3.1 Proposed change: Counter Kapseok Chang (ETRI)

Month Year doc.: IEEE 802.11-07/xxxxr0 September 2010 References [1] Kapseok Chang, “Relay operation in IEEE 802.11ad,” Doc. 10/0494r1, May 2010. [2] IEEE P802.11ad/D0.2, http://www.ieee802.org/11/TGad/index.html. Kapseok Chang (ETRI) VInko Erceg, Broadcom