Concepts for 802.16-based Mobile Multi-hop Relay Networking

IEEE 802.16 Presentation Submission Template (Rev. 8.3)Document Number:

IEEE C802.16-05/015Date Submitted: 2005-07-19

Source:Masahito Asa Voice: +81-3-5424-3156Motorola Japan Ltd. Fax: +81-3-3440-08923-20-1 Minami-azabu, Minatoku, Tokyo 106-8573, Japan E-mail: asa@motorola.com

David T, Chen, Nat Natarajan Voice: +1-847-632-2664Motorola Inc. Fax: +1-847-435-9970 1501 W Shure Drive, Arlington Heights, IL 60004, USA E-mail: David.T.Chen@motorola.com

Venue:IEEE 802.16 Session #38, San Francisco, USA

Base Document:None

Purpose:Present concepts in support of formation of a new study group for mobile multi-hop relay networking in IEEE 802.16 systems

Notice:This document has been prepared to assist IEEE 802.16. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) 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.

IEEE 802.16 Patent Policy:The contributor is familiar with the IEEE 802.16 Patent Policy and Procedures <http://ieee802.org/16/ipr/patents/policy.html>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <mailto:chair@wirelessman.org> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.16 Working Group. The Chair will disclose this notification via the IEEE 802.16 web site <http://ieee802.org/16/ipr/patents/notices>.

Concepts for 802.16-based Mobile Multi-hop Relay Networking

Masahito AsaMotorola Japan Research Lab

Tokyo 106-8573, Japan

David T. Chen, Nat NatarajanMotorola Networks

Arlington Heights, IL 60004, USA

July 19, 2005

July 19, 2005- 3 -

Background

• At the IEEE 802.16 Session #37 meeting in Sorrento, Italy, (http://www.ieee802.org/16/meetings/mtg37/ ), KDDI Labs and Samsung had proposed a new study item entitled “Mobile Multi-hop Mesh/Relay Networking in IEEE 802.16”

• A mailing list was created. Establishment of a new study group is under way (proposed schedule indicated in next slide)

• At this early stage, high level discussion like system concept, requirements and underlying issues are appropriate for discussion

• In this presentation we propose a few concepts relevant to high-level deployment scenario and frequency assignment strategy for a 802.16-based Mobile Multi-hop Relay Networking

July 19, 2005- 4 -

Proposed Schedule

TG: the 4thmeeting #46 Plenary Nov.

TG: the 3rd meeting #45 Interim Sept.

TG: the 2nd meeting #44 Plenary July

TG: the 1st meeting #43 Interim May

802 EC endorses PARapproval#42 Plenary Mar.

SG: the 3rdmeeting–Complete a PAR #41 Interim Jan.

2006

SG: the 2ndmeeting #40 Plenary Nov.

SG: the 1stmeeting #39 Interim Sept.

Propose to form SG–Approved #38 Plenary July

Call for Interest #37 Interim May

2005

Actions 802.16session Month Year

July 19, 2005- 5 -

Proposed Concepts

• Deployment Scenario: Scalable Relay Station– 16e-based multi-hop protocol enables support for various sizes of

relay stations (RSs)– Scalable RSs could belong to typical sizes:

• Large size• Medium size• Miniature size

• Frequency Assignment Strategy– Different Carrier Frequencies– Same Carrier Frequency but Different Subchannel Assignment– Same Carrier Frequency but RS is a Dummy Relay

• Dummy Relay simply relays all information from BS to MSS and vice versa with no change

July 19, 2005- 6 -

Large Scale (infra-mesh-like deployment)

• Wireless extension of cell coverage• RS may be used with wireless backhaul from BS

To Core Network

BS

RS

RS

July 19, 2005- 7 -

Medium Scale (general relaying scheme)

• Enhance throughput and coverageby using Relay Stations (RSs)

• Minimize dead zones (cancel dead point) in communication

• Enable multi-cell operation in future

BSRS

BS

BSBS

RS

RS

RS

RS

RS

RSRSRS

RS

July 19, 2005- 8 -

Miniature Scale (portable & indoor)

• Indoor portable relay station (RS) is used to penetrate deep inside a room or underground area

• It is used to relay information from outdoor to indoor and vice versa

RS BS

July 19, 2005- 9 -

Different Carrier Frequencies

• RS deals with two frequencies, one communicates with BS in f1 and one communicates with its subordinate MSSs in f2

• MSS moving into an RS zone (within the coverage of RS antenna) will be hard handover to RS

• In this case, RS is simply a smaller-scale BS which schedules its uplink and downlink transmission with its subordinate MSS in f2 and relay the aggregated traffic with BS in f1

• BS has backhaul connection to the CO while RS doesn’t have backhaul access

• This proposal requires RS to perform full BS functionalities except the backhaul access (typically more costly)

• Advantage: no interference between MSSs under RS and MSSs under BS (due to different frequencies)

BS

MSS

MSS

MSS

MSS

MSS

MSS

RS

MSSMSS

MSS

MSS

f1

f1

f1

f1

f1

f2

f2

f2MSS

•

July 19, 2005- 10 -

Same Carrier Frequency but Different Subchannel Assignment

• MSS may communicate directly with BS or indirectly with BS via RS

• BS communicates with ‘normal’ MSS (16e-based) and the RS in one larger set of subchannels

• RS communicates with its subordinate MSSs in a smaller set of subchannels to minimize interference

• In this case, RS also has to perform full BS functionalities however only to a smaller set of subchannels

• Advantage: smaller interference between MSSs under RS and MSSsunder BS (due to different subchannels)

• Disadvantage: reduced BS capacity since BS cannot use the full set of subchannels

BS

MSS

MSS

MSS

MSS

MSS

MSS

RS

MSSMSS

MSS

MSS

f1

f1

f1

f1

f1

f1

f1

f1MSS

July 19, 2005- 11 -

Same Carrier Frequency butRS is a Dummy Relay

• BS is the only node that generates DLMAP and ULMAP for scheduling

• RS simply forwards traffic between BS and RS’s subordinate MSSs in a time-delayed way

Issues to consider:• How does the MAC request and

grant work going through RS?• Latency due to relaying

BS

MSS

MSS

MSS

MSS

MSS

MSS

RS

MSSMSS

MSS

MSS

f1

f1

f1

f1

f1

f1

f1

f1MSS

July 19, 2005- 12 -

Detailed investigation of Multi-hop Relay Networking presents a number of study items, including, but not limited to the following:

• Frequency reuse strategy• Spectrum efficiency• System capacity• Interference consideration when blanket deployment is employed • Multihop system protocol with backward compatibility (PMP)• Latency • Mobility (handover options)• Cost• Reliability• Coverage • Dynamic selection (between BS and RS)• Battery life

July 19, 2005- 13 -

Summary

• This presentation introduced two concepts relevant to 802.16 Multi-hop Relay Networking.– Scalable Relay Stations supported by single 802.16-based

multihop protocol enabling flexible deployment options– Flexible Frequency Assignment Strategies, such as,

• Multiple frequencies• Single frequency with sub-channels• Single frequency with Dummy Relays

• Detailed investigation of these and additional related architecture concepts are necessary to enable effective 802.16-based multi-hop relay networking systems