configuration scenario for multi-hop relay network · ad-hoc network • rapidly deployed without...

25
Configuration Scenario for Multi-Hop Relay Network IEEE 802.16 Presentation Submission Template (Rev. 8.3) Document Number: IEEE C802.16mmr-06/013 Date Submitted: 2006-01-09 Source: Changhoi Koo, Purva R Rajkotia Voice: +1-972-761-7934 Samsung Telecommunications America Fax: +1-972-761-7909 75081 1130 E.Arapaho Rd. Richardson TX E-mail: [email protected] Venue: IEEE 802.16 Session #41, New Delhi, India Base Document: None Purpose: Information 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:[email protected]> 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>.

Upload: others

Post on 07-Aug-2020

7 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Configuration Scenario for Multi-Hop Relay Network

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

IEEE C802.16mmr-06/013Date Submitted:

2006-01-09Source:

Changhoi Koo, Purva R Rajkotia Voice: +1-972-761-7934Samsung Telecommunications America Fax: +1-972-761-790975081 1130 E.Arapaho Rd. Richardson TX E-mail: [email protected]

Venue:IEEE 802.16 Session #41, New Delhi, India

Base Document:None

Purpose:Information

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:[email protected]> 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>.

Page 2: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Configuration Scenario for Multi-Hop Relay Network

Changhoi Koo and Changhoi Koo and PurvaPurva R R RajkotiaRajkotia

Samsung Telecommunications AmericaSamsung Telecommunications America

January, 2006

Page 3: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Contents

• Multi-Hop Relay Architecture

• Comparison of Multi-Hop Relay Systems with Conventional Systems

• Multi-Hop Relay Channel Configuration

• Multi-Hop Relay Configuration Set-up Scenario

• Multi-Hop Bandwidth Allocation Mechanism

• Multi-Hop Power Control and Load Control Mechanism

1

Page 4: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-hop Relay Architecture

Page 5: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Conventional RAN

• Limitation: Fixed BS location and cell coverage (less flexible)

• In the next generation RAN,

– Various traffic demand, ever-changing user distribution

– Large number of small cells

• Not easy to construct such RAN in the conventional (centralized) manner

Page 6: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Ad-hoc Network

• Rapidly deployed without relying on pre-existing fixed network infrastructure

• Application– Military Communication, Wireless LAN, Wireless PAN, Wireless

Sensor Network• Features

–– SelfSelf--organizingorganizing, Dynamic topology, Dynamic topology

Gateway OrdinaryCluster HeadBase Station Mobile Station

AdAd--hoc Networkhoc NetworkCellular NetworkCellular Network

Page 7: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-hop Cellular Networks

• Hybrid network of Cellular and Ad-hoc

– Fixed BS (stability) + Multi-hop Relay (flexibility)

• Hybrid transmission mode

– Provides flexibility in design and operation of the cellular network

Single-hop mode Multi-hop mode

Page 8: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

One Example of MMR Configuration2 BS and 1 RS configuration

Advantages:•Cost Effective Cell Planning

•Reduction of Signaling Overhead

•Timely delivery of Signals

Page 9: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Channel Configuration

Page 10: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Channel Configuration

• Configuration 1 of the multi-hop relay network

Page 11: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Channel Configuration• Channel configuration for configuration 1

Path Direction ChannelAllocation

BWAllocation

AvailableChannel Scheduling fashion

Dedicated Sub-carriers Fixed BW

Dynamic Sub-carriers

Dynamic BWw/wo limitation

DL_2 RS to MS Dynamic Control/Traffic channel

RS allocates BWto MS through

the BW allocated from the BS

DedicatedSub-carrier Fixed BW

Dynamic Dynamic BW

Control/Trafficchannel

With/withoutContentionUL_1 RS to BS

Control/Traffic channel

BS allocatesparticular BW

to RS (No MS aware BW

allocation)

DL_1 BS to RS

Page 12: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Channel Configuration

• Configuration 2 of the multi-hop relay network

Page 13: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Channel Configuration• Channel configuration for configuration 2

Path Direction Channel allocation

BWallocation

Availablechannel Scheduling fashion

Dedicated Sub-carrier Fixed BW

Dynamic Sub-carrier

Dynamic BWw/wo limitation

DL_2 RS to MS Dynamic Traffic channel

RS allocates BW for Traffic only to MS

through the BW allocated from the BS

DL_3 BS to MS Dynamic Control channel(Net. Entry)

BS allocates BW for Signaling only to MS

DedicatedSub-carrier Fixed BW

Dynamic Dynamic BW

UL_2 MS to RS Dynamic Traffic channel With/without contention

UL_3 MS to BS Dynamic Control channel(Net. Entry) With/without contention

Control/Traffic channel

With/withoutContentionUL_1 RS to BS

Control/Traffic channel

BS allocates particular BW to RSDL_1 BS to RS

Page 14: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Configuration Set-up Scenario

Page 15: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

MMR Configuration Set-up Scenario• Multi-hop cellular networks provides an alternative path to the

single hop direct link. It also obtains a path gain in the condition of free space propagation and as a result of which there is an added capacity and coverage to the network.

• The RS can also have multiple connections to the BS and at the same time, communicate with the MS in the cell boundary of 2 BS.

• Hence, a framework of communication link is needed between the multiple base stations, mobile station and relay station, for effective operation of the multi-hop relay network.

• The present contribution describes the framework for the communication between the different entities in the multi-hop relay network.

Page 16: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

MMR Configuration Set-up Scenario• Call Flow for MS initiated Case in BS

Page 17: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

• Call Flow for MS initiated case in RS

MMR Configuration Set-up Scenario

Page 18: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Bandwidth Allocation Mechanism

Page 19: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Bandwidth Allocation Mechanism

• Bandwidth Allocation in the MMR architecture is tricky and critical.

• Bandwidth should be allocated in the cell configuration in which the RS is connected to the multiple base stations.

• MS connected to the RS having different paths may have different capacity because of the link going thru’ the different multipath effect.

• If the RS allocates the higher bandwidth to the MS, but not supported by the BS, then the effective bandwidth is reduced, as the link between the RS and the BS would serve as a bottleneck.

• The contribution suggests the effective mechanism to quickly vary the total available bandwidth and resulting in effective bandwidth allocation.

Page 20: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Bandwidth Allocation Mechanism

• Bandwidth Allocation Mechanism

Page 21: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Power Control and Load Control Mechanism

Page 22: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Power Control Mechanism

• The base station coverage is limited by a combination of the range from the Base station, terrain blockage and building penetration loss.

• The communication between the Base station and the mobile station can be extended by the RS, which may be fixed or mobile.

• However the coverage extension or user data rates of the cell using the above means is limited by the available power at the RS.

• In this proposal, the effective technique for providing the coverage extension is provided with minimal usage of power.

Page 23: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Power Control Mechanism

• Available Power lower at the RS

Page 24: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Load Control Mechanism

• The base station coverage is limited by a combination of the range from the Base station, terrain blockage and building penetration loss.

• The communication between the Base station and the mobile station can be extended by the RS, which may be fixed or mobile.

• However the coverage extension or user data rates of the cell using the above means is limited by the loading of the RS.

• In this proposal, the effective technique for providing the coverage extension is provided taking into consideration the load at the RS.

Page 25: Configuration Scenario for Multi-Hop Relay Network · Ad-hoc Network • Rapidly deployed without relying on pre-existing fixed network infrastructure ... • Bandwidth Allocation

Multi-Hop Relay Load Control Mechanism

• Available Load reaches the threshold at RS