Maximum number of hops for centralized scheduling mode

Slides:



Advertisements
Similar presentations
Project Planning Committee (PPC): Next revision project
Advertisements

Session # Maintenance Task Group Opening and Agenda
[A Reliable Multicast Service in m]
MM RG Report Document Number: IEEE C802.16n-11/0083 Date Submitted:
802.16m sounding sequences comparison
Uplink Pilot Structure for IEEE802.16m
Emergency Service – NS/EP Vs E-911 for IEEE m
Session # Maintenance Task Group Opening Slides
A MAC Addressing in IEEE m
Session # Maintenance Task Group Opening and Agenda
IEEE Presentation Submission Template (Rev. 9) Document Number:
Opening report of Connection Management and QoS DG
Project Planning Committee (PPC): Report
IEEE Presentation Submission Template (Rev. 9) Document Number:
HO DG Meeting Minutes Document Number: IEEE S802.16m-09/0752
Mesh Topology for Relays
Comment on Relay Frame Structure
Project Planning Committee Opening Report
UL Control Ad-hoc group discussion summary
Session # Maintenance Task Group Closing Plenary Report
HARQ Soft Buffer Management for m
Project Planning Committee Opening Report (Session #77)
Dynamic Interference Mitigation for Femtocell Access Points in IEEE802
Title: LE TG Report for the opening plenary – Session #57
Title: LE TG Agenda for Session #54
Title: LE TG Agenda for Session #53
Title: LE TG Agenda for Session #65
Title: LE TG Agenda for Session #63.5
Title: LE TG Closing Report for Session #56
IEEE Presentation Submission Template (Rev. 9) Document Number:
Suggestion to Retaining ALL 16m Features
Uplink Subframe Aggregation
MAP NACK Channel for Persistent Allocation
Session # Maintenance Task Group Opening Report
Session # Maintenance Task Group Opening and Agenda
Session # Maintenance Task Group Opening and Agenda
Session # Maintenance Task Group Closing Plenary Report
Resource Shifting in Persistent Scheduling
Session # Maintenance Task Group Closing Report
Session # Maintenance Task Group Opening and Agenda
Session # Maintenance Task Group Opening Report
Session # Maintenance Task Group Opening and Agenda
HARQ Feedback Channel for 2bit HARQ feedback
HARQ Ad-Hoc Report IEEE Presentation Submission Template (Rev. 9)
Overview and definitions adhoc report
Broadcast Handovers Tutorial Overview
Title: LE TG Agenda for Session #66
Uplink Subframe Aggregation
Title: LE TG Agenda for Session #62
Compressed MAC PDU Overhead
ITU-R Liaison Group Report - Session #52 Closing Plenary
IETF 16ng Working Group Update
Session # Maintenance Task Group Opening and Agenda
SON in IEEE m system IEEE Presentation Submission Template (Rev. 9)
Title: Control channel allocation for femto-cells
Frame Structure & Interference adhoc report
ITU-R Liaison Group Report - Session #52 Opening Plenary
Title: LE TG Agenda for Session #52
Analysis of burst-based forwarding for non-transparent RS
A more efficient DL-MAP IE for MAPs
Project Planning Adhoc: WG Opening Plenary Report
Title: LE TG Agenda for Session #64
Network Synchronization Considerations for n
ITU-R Liaison Group Report - Session #61 Opening Plenary
Session # NRR Ad Hoc Committee Opening Report
HARQ and ARQ Interactions
Session # Maintenance Task Group Closing Plenary Report
Treasurer’s Report Document Number: IEEE /0059
Session # NRR Ad Hoc Committee Report
ARQ protocol in m IEEE Presentation Submission Template (Rev. 9)
Presentation transcript:

Maximum number of hops for centralized scheduling mode IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE 802.16j-08/050 Date Submitted: 2008-01-23 Source: Yuefeng Zhou Voice: +44 20 87523460 NEC E-mail: yuefeng.zhou@ieee.org IEEE 802.16 Session #53, Levi, Finland Base Contribution: None Purpose: For the discussion of the Maximum number of hops for centralized scheduling mode 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 >.2

Maximum number of hops for centralized scheduling mode As defined in the standard draft, P802.16j/D2, the centralized scheduling is the mode of operation applicable to multihop relay where an MR-BS determines the bandwidth allocations and generates the corresponding MAPs (or dictates the information used by RSs to generate their MAPs) for all access and relay links in the MR-cell. When increasing the number of hops, the MR-BS will have very heavy MAP overhead, since it has to generates the MAPs for each hop.

Maximum number of hops for centralized scheduling mode Figure 1 shows the estimated MAP and FCH overhead for legacy one-hop 16e system, when normal map is used. (FFT size = 1024; DL:UL = 32:15; Assume one burst for one connection; assume UL and DL subframe has same number of connections; 3 segmentation is used) Fig. 1. FCH & MAP overhead (percentage within DL subframe) vs. Number of connections (CIDs) used.

Maximum number of hops for centralized scheduling mode From the estimated results in Fig. 1, when number of connections is 10, by using repetition rate of 4 and normal MAPs, the overhead of FCH and MAPs will use about 70% of the whole DL subframe! In 16j with centralized scheduler mode, when number of hops is bigger, the MR-BS will consume much bigger FCH&MAP overhead. For example, when number of hops is 3, averagely, only two connections could be supported by each RS and MR-BS to make sure the MR-BS has enough resource to allocate all FCH and MAPs. Obviously, it is not efficient to use centralized scheduling mode when number of hops is big, e.g. > 2.