1 / 9

D0.2 Comment Resolution on CID 368

D0.2 Comment Resolution on CID 368. Date: 2010-09-14. Authors:. Outline. Comment on CID 368 Proposed resolution. Comment detail. Comment on CID 368. dot11RelayTPATime is included in link cooperating type. Link Cooperating type [1]

cordero-chavez
Download Presentation

D0.2 Comment Resolution on CID 368

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D0.2 Comment Resolution on CID 368 Date: 2010-09-14 Authors: Kapseok Chang (ETRI)

  2. Outline • Comment on CID 368 • Proposed resolution Kapseok Chang (ETRI)

  3. Comment detail Comment on CID 368 Kapseok Chang (ETRI)

  4. 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 Proposed resolution (1/5) STA Cooperation RSUS S-R Relay link R-D Relay link Source RUS Destination RUS S-D Direct link Kapseok Chang, ETRI

  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. Proposed resolution (2/5) Kapseok Chang (ETRI)

  6. 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. • Itis reasonable to define the Relay TPA time as “constant” in MAC sublayer. Proposed resolution (3/5) Kapseok Chang (ETRI)

  7. 11.37.3.1 TPA procedure • Change the name of “dot11RelayTPATime” to “aRelayTPATime” throughput the spec. • Change the name of “Dtime” throughput 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). Proposed resolution (4/5) Kapseok Chang (ETRI)

  8. Edited subclauses 7.4.13.24, 11.36, and 11.37.3.1 Proposed resolution (5/5) Kapseok Chang (ETRI)

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

More Related