Relay DG Report (for TGm Closing Report)

IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: C80216m-09_2134Date Submitted: 2009-09-01Source:

Rakesh Taori Voice: [Telephone Number (optional)]Samsung Electronics E-mail: rakesh.taori@samsung.com*http://standards.ieee.org/faqs/affiliationFAQ.html

Venue:Re: Session #63 Jeju Meeting

Base Contribution: C80216m-09_2134 Purpose: To report the Relay DG activities in Session #63 to TGm.

Notice:This document does not represent the agreed views of the IEEE 802.16 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 802.16.

Patent Policy:The contributor is familiar with the IEEE-SA Patent Policy and Procedures:

<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>.Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >.

Agenda

• Establish DG goals, strategy, and process

• Review classification of contributions– Do we want to consider all given our goals and our

strategy?

• Develop ToC

• Time for contribution presentation (voluntary basis)

• Establish timeline for work between meetings

Relay DG Goal

• To draft relay text that can be adopted in D2 during Session #63.5 (Hawaii)– Must have very high level of support (75% required

for adoption)– Must be fully specified and self-consistent; cannot

contain major placeholders or vague text for which protocols/procedures will need to be specified later.

Relay DG Strategy

• Use the DG to specify a simple baseline relay system– Stick to a modest scope and to basic, non-controversial

relay concepts

– Generate DG document which can meet the 75% acceptance requirement

– Provide a baseline for additional relay proposals/concepts.

• Extensions and more advanced relay concepts can be considered as LB comments against the D2 or later drafts.

Relay DG Process

• Classify Contributions into categories - done• Prioritization (Scope Reduction) - done

– See the slide titled “Scope reduction”

• Adopt a ToC (For DG text development) - done

• Publish initial draft (DG chairs put together a draft)• Review the draft using email and 4 conference calls.• Finalize the draft during Session #63.5 (Hawaii) and

propose to the WG for adoption.

Scope reduction: Topics that we agreed not to focus on in this DG

(during the development of the draft for Session #63.5 (Hawaii))

• Mobile RS

• Centralized scheduling

• Interference mitigation

• Multi-hop

• Transparent RS

• Cooperative Relay

• RS groups

Table of Contents(for the development of the DG draft)

• 15.5 Support for Relay– 15.5.1 Relay Modes and General

Description– 15.5.2 Support for 802.16e (official term)

MS– 15.5.3 MAC

• 15.5.3.1 Addressing• 15.5.3.2 MPDU Formats• 15.5.3.3 Construction and Transmission of

MPDUs• 15.5.3.4 MAC Control Messages• 15.5.3.5 Security• 15.5.3.6 Handover• 15.5.3.7 Connection Management• 15.5.3.8 Scheduling and QoS• 15.5.3.9 Bandwidth Request• 15.5.3.10 ARQ• 15.5.3.11 HARQ• 15.5.3.12 Network Entry

– 15.5.3.12.1 AMS Network Entry– 15.5.3.12.2 ARS Network Entry

• 15.5.3.13 Ranging• 15.5.3.14 Sleep Mode• 15.5.3.15 Idle Mode

– 15.5.4 Physical Layer• 15.5.3.1 Frame Structure • 15.5.3.2.DL Physical structure• 15.5.3.3 Downlink Control Channels

– 15.5.3.3.1 Relay amble– 15.5.3.3.2 Superframe Header– 15.5.3.3.3 Advanced Map

• 15.5.3.4 Uplink Control Channels

Until Session #63.5

• Work will be carried out in the DG on the basis of the comments and contributions that were by the CfC deadline for features (30th Aug AOE).

• DG chairs to prepare the initial draft and circulate it for discussion (by the 4th Sept)

• Comments and discussions based on the draft in accordance with the plan proposed in the slide titled “DG activities between meetings”

DG Activities Between Session #63 and #63.5

• Initial draft – To be sent by the chairs by September 4, 2009– Chairs will prepare the draft on the basis of the

• received contributions• agreed reduced scope.• agreed ToC (See Doc “”)

• Conference calls:– All calls at 7 pm PST (= 10 PM EST, 11 AM KST/JST (+1), 10 AM China(+1), 6 AM Russia, 7:30 AM India(+1))

– First conference call – September 8, 2009– Second CC – September 10, 2009– Third CC – September 15, 2009– Fourth CC – September 17, 2009– Try to limit the call to two hours (no longer than 3 hours).

• Revised drafts and requests for comments/inputs to be issued in between calls.

What you need to do to join the DG activity

• Send your e-mail address to the DG chairs:– Jerry.Sydir@intel.com

– Rakesh.Taori@samsung.com