1 A Simple Comparison of Latency Between 802.16m Relay Frame Structures IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/926.

Slides:

Advertisements

Similar presentations

Clarification for Staggered Super-frame Transmissions in the SDD Document Number: IEEE C802.16m-08/854 Date Submitted: Source: Richard Li, Chun-Yen.

Advertisements

802.16m Frame Structure: Uplink Subframe Aggregation IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/099 Date Submitted:

Contribution to IEEE n System Requirements Document IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16gman-10/0018.

1 IEEE m Synchronization Channel IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/823r3 Date Submitted:

1 IEEE m Synchronization Channel IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/823r1 Date Submitted:

Relative Timing of Super-Frames in the Legacy-Support Mode IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/244.

Views on IEEE m Frame Structure Document Number: C80216m-07_354 Date Submitted: November 12, 2007 Source: Sassan Ahmadi

1 s in IEEE m Relay Frame Structure regarding Transparent ARSs in IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number:

MAC support for LBS in IEEE802.16m Document Number: C80216m-09_1986 Date Submitted: Source: Kiseon Ryu, Jinsoo Choi, Ronny Kim, and Jin Sam.

MBS Frame Structure Considerations IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/089 Date Submitted:

Macro Diversity for E-MSB IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/981r1 Date Submitted: Source:

M2M Study Report: Status Report IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16ppc-10/0008 Date Submitted:

Frame structure supporting the WirelessMAN-OFDMA frames IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C80216m-09_0475r1 Date.

Relay DG Report (for Session #63.5 TGm Closing) IEEE Presentation Submission Template (Rev. 9) Document Number: C80216m-09_2211 Date Submitted:

Common Header design in m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: Source:

Group based paging operation for p system IEEE Presentation Submission Template (Rev. 9.2) Document Number: IEEE C80216p-10_0018 Date Submitted:

Frame Structures for Legacy-Support and Legacy-Support Disabled Modes IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/243.

8Tx Pilot Pattern Performance for IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0544 Date Submitted:

Integrated Relay Architecture for IEEE m Systems Document Number: S802.16m-07_299 Date Submitted: November 12, 2007 Source: Sassan Ahmadi

Uplink OLPC Modification: Replacement of SIR_DL by SINR_DL for Easy Measurement IEEE Presentation Submission Template (Rev. 9) Document Number:

Subframe Structure with Variable-length CP IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/201, Subframe Structure.

Proposed Feature Rapporteur Group Timelines and Call for contributions IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0762r2.

1 Idle mode operation for supporting FemtoCells Document Number: IEEE C802.16m-08/1433 Date Submitted: Source: Giwon Park, Rony Yongho Kim,

Proposed changes for IEEE P802.16m/D1: Proximity based handover from macrocell to femtocell IEEE Presentation Submission Template (Rev.

FDD Frame Structure for Legacy Support ( ) IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/2095 Date Submitted:

16m Relay frame structure considering interfering issue IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/1176r1.

Text Proposals of HR-MS Forwarding in 16n Network IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16n-11/0074 Date Submitted:

1 MIMO Supports for IEEE m Broadcast Channel IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/1416r1 Date.

Uplink Pilot Structure for IEEE802.16m Document Number: IEEE C802.16m-08/293r4 Date Submitted: Source: Mohammed Nafie, Cairo University Mohamed.

Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the.

1 Uplink MIMO Proposal for IEEE m Document Number: S80216m-08/744 Date Submitted: July 16, 2008 Source: shaohua Nokia Siemens.

Comparisons on Frame Structures for Supporting WirelessMAN-OFDMA ( ) IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE.

Relay to Relay Communication - A SDD Proposal for m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/047 Date.

Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the.

Support of STR Relaying in m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/1274 Date Submitted:

Synchronization Drafting Group Schedule Document Number: IEEE C802.16m-09/0379 Date Submitted: Source: Paul Cheng

HARQ Architecture (Protocol and Timing) in IEEE m Document Number: IEEE S802.16m-08/411 Date Submitted: Source: Doo-hyun Sung, Hyungho.

Femtocell Over-The-Air Signaling Supported by Relay Link Document Number: IEEE C802.16m-09/0809 Date Submitted: 2009/04/24 Source: Hung-Yu Wei, Shih-Lung.

Backward Compatible FDD m Frame Structure for Full-Duplex and Half-Duplex MS Operations Document Number: S802.16m-08/031r2 Date Submitted: January.

Comment on Relay Frame Structure IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/1312r2 Date Submitted:

1 Proposed Text on Relay A-MAP for IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/439 Date Submitted:

Group Sleep Mode in IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/591r3 Date Submitted:

TDD frame structure for m with legacy support IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S80216m-07/215r1 Date Submitted:

DC RG Report Document Number: IEEE C802.16n-11/0088 Date Submitted: Source: Ming-Tuo Zhou, Sungcheol Chang DC RG.

1 Equation revision for Frequency Partitioning in DL/UL PHY IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0887r1.

Group Sleep Mode in IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/591r1 Date Submitted:

Definition of Device Collaboration Mode for Low Power Consumption IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16p-10_0030.

Coexistence Supports with Other TDD Systems in Frame Structure IEEE Presentation Submission Template (Rev. 9) Document Number: S802.16m-08/476 Date.

Project Planning Committee Opening Report (Session #77) IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE Gdoc.

TDD Frame Structures for Legacy Support in 16m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-07/242r1, TDD Frame.

Design Consideration for Irregular Subframe Allocation in m Network with Mixed CP Lengths Document Number: IEEE S802.16m-08/570r1 Date Submitted:

1 Power Saving Considerations for IEEE m Femtocell IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/1411 Date.

Collaborative uplink MIMO techniques for IEEE m Document Number: C80216m-08/638 Date Submitted: 7/7/2008 Source: Mohamed Abdallah Mohammed Nafie.

Relay/EMBS Ad-Hoc Group Report Document Number: IEEE C802.16m-09/2678r1 Date Submitted: Source: Kanchei(Ken) Loa Relay/LBS/EMBS.

Multi-Level Codes Sequence for Simultaneous MCS Feedback IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S80216m-08/1152 Date.

Frame Structure Considerations for n IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16n-11/0005 Date Submitted:

Project Planning Committee (PPC): Session #70 WG Opening Plenary Report IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE.

Preamble for 16m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C80216m-08/480 Date Submitted: Source:Zexian Li,

Session # Maintenance Task Group Opening Report IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE maint-11/0028.

Clarification on the Usage of Femtocell Over The Air (OTA) Signaling ( ) Document Number: IEEE C802.16m-09/2603 Date Submitted: Source:

Some Considerations about 16m Network Architecture Document Number: C80216m-08_491 Date Submitted: Source: Qu Hongyun, Fang Huiying, Liu Yang,

Clarification on Temporary Identifier of Idle AMS IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0839r2 Date Submitted:

[A Reliable Multicast Service in m]

IEEE Presentation Submission Template (Rev. 9) Document Number:

Comment on Relay Frame Structure

Proposed Text on Relay A-MAP for IEEE m

SPID transmission order in IEEE m UL HARQ

HARQ Timing Document Number: IEEE C802.16m-09/0287

Maximum number of hops for centralized scheduling mode

Network Synchronization Considerations for n

Presentation transcript:

1 A Simple Comparison of Latency Between m Relay Frame Structures IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/926 Date Submitted: Source: Aeran Youn, Jin Sam Kwak, Ji Wook Chung Voice: {aryoun; samji; samji; LG Electronics LG R&D Complex, 533 Hogye-1dong, Dongan-gu, Anyang, , Korea Ki-Dong, Li-Hsiang {kidonglee; LG Electronics Mobile Research, San Diego Venue: SDD Session 56 Cleanup; in response to the TGm Call for Contributions and Comments m-08/033 for Session 57 Purpose: This contribution proposes clarification of latency based on Relay Frame Structure in IEEE m-08/003r4. Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Further information is located at and.

2 A Simple Comparison of Latency Between m Relay Frame Structures

3 Contents  Introduction  Latency Comparison of Each Relay Frame structure  Option 1  Access-Relay/Transmit-Receive Zone  Relay-Access/Receive-Transmit Zone  Option 2  MSs use only Access Zone for reception/transmission  MSs can use Bi-Directional transmit/Receive Zone for reception/transmission  Summary  References

4  Latency Comparison with each relay frame structure  Option 1: The order of DL subframe of the BS/RS  Access Zone/Relay Zone (Transmit Zone/Receive Zone)  Relay Zone/Access Zone (Receive Zone/Transmit Zone)  Option 2: Whether the MS can use Bi-directional Zone or not  MSs use only Access Zone for reception/transmission  MSs can use Bi-Directional transmit/Receive Zone for reception/transmission  Assumption  TDD system in the legacy support mode  The duration of the DL/UL legacy zone of the BS: 3-subframe/1-subframe  The base station, relay station, or mobile station processing time is approximately 2*TTI = 1.23 ms  DL/UL traffic ratio = 5:3  Scenario  2-hop: 16m BS ↔ 16m RS3 ↔ 16m MS3  3-hop: 16m BS ↔ 16m RS3 ↔ 16m RS2 ↔ 16m MS2  4-hop: 16m BS ↔ 16m RS3 ↔ 16m RS2 ↔ 16m RS1 ↔ 16m MS1 Introduction 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

5  Access-Relay/Transmit-Receive Zone  2-hop: 2-frame(8-subframe) BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  MS(N+1 th : receive)  3-hop: 3-frame(17-subframe) BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  RS2(N+1 th [R]: receive, N+2 th [T]: transmit)  MS(N+2 th : receive)  4-hop: 4-frame(24-subframe) BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  RS2(N+1 th [R]: receive, N+2 th [T]: transmit)  RS1(N+2 th [R]: receive, N+3 th [T]: transmit)  MS(N+3 th : receive) * [A]: Access Zone, [RL]: Relay Zone, [R]: Receive Zone, [T]: Transmit Zone Option 1 case (Downlink) BS RS3 RS2 RS1 e.g., BS  MS (using RS3, RS2, RS1)Latency: 4-frame (24-subframe) N frameN+1 frame N+2 frameN+3 frame ARLA TR RT RTTR TRRT ULDL LLL L L L LL LL LL L L L L ARLA TR RT RTTR TRRT ULDL LLL L L L LL LL LL L L L L ARLA TR RT RTTR TRRT ULDL LLL L L L LL LL LL L L L L ARLA TR RT RTTR TRRT ULDL LLL L L L LL LL LL L L L L Legacy BS RS3 RS2 RS1 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

6  Relay-Access/Receive-Transmit Zone  2-hop: 2-frame(10-subframe)  BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  MS(N+1 th : receive)  3-hop: 3-frame(17-subframe)  BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  RS2(N+1 th [R]: receive, N+2 th [T]: transmit)  MS(N+2 th : receive)  4-hop: 4-frame(26-subframe)  BS(N th [RL]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  RS2(N+1 th [R]: receive, N+2 th [T]: transmit)  RS1(N+2 th [R]: receive, N+3 th [T]: transmit)  MS(N+3 th : receive) * [A]: Access Zone, [RL]: Relay Zone, [R]: Receive Zone, [T]: Transmit Zone Option 1 case (Downlink) BS RS3 RS2 RS1 N frameN+1 frame N+2 frameN+3 frame RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L Legacy BS RS3 RS2 RS1 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

7  Access-Relay/Transmit-Receive Zone  Relay-Access/Receive-Transmit Zone  2-hop: 2-frame(10-subframe)  MS(N th [R]: transmit)  RS3(N th [R]: receive, N+1 th [T]: transmit)  BS(N+1 th [RL]: receive)  3-hop: 3-frame(17-subframe)  MS(N th [R]: transmit)  RS2(N th [R]: receive, N+1 th [T]: transmit)  RS3(N+1 th [R]: receive, N+2 th [T]: transmit)  BS(N+2 th [RL]: receive)  4-hop: 4-frame(26-subframe)  MS(N th [R]: transmit)  RS1(N th [R]: receive, N+1 th [T]: transmit)  RS2(N+1 th [R]: receive, N+2 th [T]: transmit)  RS3(N+2 th [R]: receive, N+3 th [T]: transmit)  BS(N+3 th [RL]: receive) * [A]: Access Zone, [RL]: Relay Zone, [R]: Receive Zone, [T]: Transmit Zone Option 1 case (Uplink) BS RS3 RS2 RS1 N frameN+1 frame N+2 frameN+3 frame RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L RLAA RT RT TRTR RTRT ULDL LLL L L L LL LL LL L L L L Legacy BS RS3 RS2 RS1 16m BS16m RS316m RS216m RS116m MS 16m MS3 16m MS2

8  MSs use Access Zone for reception  2-hop: 2-frame(8-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N+1 th [A]: transmit)  MS(N+1 th : receive)  3-hop: 2-frame(8-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  RS2(N th [Bi-R]: receive, N+1 th [A]: transmit)  MS(N+1 th : receive)  4-hop: 3-frame(16-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  RS2(N th [Bi-R]: receive, N+1 th [Bi-T]: transmit)  RS1(N+1 th [Bi-R]: receive, N+2 th [A]: transmit)  MS(N+2 th : receive) * [A]: Access Zone, [RL]: Relay Zone, [Bi-R]: Bi-directional Receive Zone, [Bi-T]: Bi-Directional Transmit Zone Option 2 case (Downlink) BS RS3 RS2 RS1 N frameN+1 frame N+2 frameN+3 frame ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L Legacy BS RS3 RS2 RS1 16m BS16m RS316m RS216m RS116m MS 16m MS3 16m MS2

9  MSs use Bi-directional transmit Zone for reception  2-hop: 1-frame(4-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  MS(N th : receive)  3-hop: 2-frame(8-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  RS2(N th [Bi-R]: receive, N+1 th [A]: transmit)  MS(N+1 th : receive)  4-hop: 2-frame(12-subframe)  BS(N th [RL]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  RS2(N th [Bi-R]: receive, N+1 th [Bi-T]: transmit)  RS1(N+1 th [Bi-R]: receive, N+1 th [Bi-T]: transmit)  MS(N+1 th : receive) * [A]: Access Zone, [RL]: Relay Zone, [Bi-R]: Bi-directional Receive Zone, [Bi-T]: Bi-Directional Transmit Zone Option 2 case (Downlink) 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

10  MSs use Access Zone for transmission  2-hop: 2-frame(10-subframe)  MS(N th [A]: transmit)  RS3(N th [A]: receive, N+1 th [Bi-T]: transmit)  BS(N+1 th [RL]: receive)  3-hop: 2-frame(10-subframe)  MS(N th [A]: transmit)  RS2(N th [A]: receive, N+1 th [Bi-T]: transmit)  RS3(N+1 th [Bi-R]: receive, N+1 th [Bi-T]: transmit)  BS(N+1 th [RL]: receive)  4-hop: 3-frame(18-subframe)  MS(N th [A]: transmit)  RS1(N th [A]: receive, N+1 th [Bi-T]: transmit)  RS2(N+1 th [Bi-R]: receive, N+2 th [Bi-T]: transmit)  RS3(N+1 th [Bi-R]: receive, N+2 th [Bi-T]: transmit)  BS(N+2 th [RL]: receive) * [A]: Access Zone, [RL]: Relay Zone, [Bi-R]: Bi-directional Receive Zone, [Bi-T]: Bi-Directional Transmit Zone Option 2 case (Uplink) BS RS3 RS2 RS1 N frameN+1 frame N+2 frameN+3 frame ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L ARLA ABi-R ABi-T A ABi-R A ABi-T ULDL LLL L L L LL LL LL L L L L Legacy BS RS3 RS2 RS1 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

11  MSs use Access/Bi-directional receive Zone for transmission  2-hop: 2/1-frame(10/4-subframe)  MS(N th [A]: transmit)  RS3(N th [A]: receive, N+1 th [Bi-T]: transmit)  BS(N+1th[RL]: receive)  MS(N th [Bi-R]: transmit)  RS3(N th [Bi-R]: receive, N th [Bi-T]: transmit)  BS(Nth[RL]: receive)  UL-Map decoding problem  3-hop: 2-frame(10-subframe)  MS(Nth[A]: transmit)  RS2(Nth[A]: receive, N+1th[Bi-T]: transmit)  RS3(N+1th[Bi-R]: receive, N+1th[Bi-T]: transmit)  BS(N+1th[RL]: receive)  4-hop: 3/2-frame(18/12-subframe)  MS(Nth[A]: transmit)  RS1(Nth[A]: receive, N+1th[Bi-T]: transmit)  RS2(N+1th[Bi-R]: receive, N+2th[Bi-T]: transmit)  RS3(N+1th[Bi-R]: receive, N+2th[Bi-T]: transmit)  BS(N+2th[RL]: receive)  MS(Nth[Bi-R]: transmit)  RS1(Nth[Bi-R]: receive, Nth[Bi-T]: transmit)  RS2(Nth[Bi-R]: receive, N+1th[Bi-T]: transmit)  RS3(N+1th[Bi-R]: receive, N+1th[Bi-T]: transmit)  BS(N+1th[RL]: receive)  UL-Map decoding problem Option 2 case (Uplink) 16m MS316m MS2 16m BS 16m RS316m RS2 16m RS116m MS

12  DL/UL Latency based on Multi-hop Relay Frame Structures  Latency comparison between Option 1 and Option 2  Option 2 has smaller latency than Option 1.  Further latency analysis and comparison are necessary Summary # of hops Option 1Option 2 Access/RelayRelay/AccessMS use access zoneMS use Bi-D zone DL 2 2-frame(8-subframe)2-frame(10-subframe)2-frame(8-subframe)1-frame(4-subframe) 33-frame(17-subframe) 2-frame(8-subframe) 44-frame(24-subframe)4-frame(26-subframe)3-frame(16-subframe)2-frame(12-subframe) UL 2 2-frame(10-subframe) 33-frame(17-subframe) 2-frame(10-subframe) 44-frame(26-subframe) 3-frame(18-subframe)

13 References [1] IEEE C802.16m-08_848r2, “IEEE m Relay Ad HoC Group – Final Report”. [2] IEEE C802.16m-08_003r4, “The Draft IEEE m System Description Document” [3] IEEE C80216m-08_1107, “Clarifications on Open Items of Option 2 in Relay Frame Structure”