1. D0.2 Comment Resolution on CID 368
Month Year
doc.: IEEE /xxxxr0
September 2010
D0.2 Comment Resolution on CID 368
Date:
Authors:
Name
Affiliations
Address
Phone
Kapseok Chang
ETRI
138 Gajeongno, Yuseong-gu, Daejeon, , Korea
Yongsun Kim
Seung Eun Hong
Hoosung Lee
Woo Yong Lee
Hyun Kyu Chung
Kapseok Chang (ETRI)
VInko Erceg, Broadcom

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

3. Comment on CID 368 Comment detail September 2010 Comment ID Subclause
Month Year
doc.: IEEE /xxxxr0
September 2010
Comment on CID 368
Comment detail
Comment ID
Subclause
Page
Line
Comment Type
Comment
Suggested
Remedy
368
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

4. Proposed resolution (1/5)
Month Year
doc.: IEEE /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

5. 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)

6. 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)

7. Proposed resolution (4/5)
September 2010
Proposed resolution (4/5)
Proposed change: Counter
TPA procedure
Change the name of “dot11RelayTPATime” to “aRelayTPATime” throughout the spec.
Change the name of “Dtime” throughout subclause to “aDtime”.
Remove “Response Offset” subfield in Table 49 (TPA request frame body) in subclause (TPA request).
Add “aDtime” and “aRelayTPATime” to “Table 66 – MAC sublayer parameters” in subclause [2], and define these as below.
Edit “subclauses , 11.36, and [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)

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

9. Month Year
doc.: IEEE /xxxxr0
September 2010
References
[1] Kapseok Chang, “Relay operation in IEEE ad,” Doc. 10/0494r1, May 2010.
[2] IEEE P802.11ad/D0.2,
Kapseok Chang (ETRI)
VInko Erceg, Broadcom