802.16m SDD Proposal Document Number: S802.16m-07_240r3 Date Submitted: November 13 2007 Source:...

15
802.16m SDD Proposal Document Number: S802.16m-07_240r3 Date Submitted: November 13 2007 Source: Hokyu Choi, Jaeweon Cho, David Mazzarese Voice: [Telephone Number (optional)] Jaehee Cho, Yungsoo Kim, DS Park E-mail: [email protected] Samsung Electronics Venue: Atlanta, GA Base Contribution: C80216m-07_240r3 Purpose: Discussion and approval by TGm for the 802.16m SDD 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>.

Transcript of 802.16m SDD Proposal Document Number: S802.16m-07_240r3 Date Submitted: November 13 2007 Source:...

802.16m SDD Proposal

Document Number: S802.16m-07_240r3

Date Submitted: November 13 2007

Source:Hokyu Choi, Jaeweon Cho, David Mazzarese Voice: [Telephone Number (optional)]Jaehee Cho, Yungsoo Kim, DS Park E-mail: [email protected] Electronics

Venue: Atlanta, GA

Base Contribution: C80216m-07_240r3

Purpose:Discussion and approval by TGm for the 802.16m SDD

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 >.

Summary

• Based on the joint SDD system architecture proposal [1], four more issues are presented in this slides:– Further thought on legacy support– Self organization network, Multi-carrier support, MIMO architecture

• Self organization function and multi-carrier support – Included in the proposed joint SDD contribution [1]– In this contribution, clarification is given for system architectural issues

regarding those features• Multi-carrier Support

– There are wide range of possible scenarios in single & multi-carrier support.– Moreover, legacy support also adds up additional scenarios to multi-carrier

support.– In this contribution, we intend to show full range of possible scenarios so that

initial discussion can focus on discriminating unrealistic and unnecessary scenarios before 802.16m have detail solution.

• Generic DL MIMO architecture – The possible range of MIMO discussion would be very wide.– A generic MIMO architecture can function as a place-holder of any kinds

of proposals while keeping overall architecture maintained.– MIMO discussion in 802.16m will change the architecture more and more

specific and detail as discussion goes.

[1] IEEE 80216m-07/297 “Proposal for IEEE 802.16m System Architecture and Protocol Structure”

Further thoughts on Legacy Support

4

Further Thoughts on Legacy Support

• Resources (time, frequency, space, code, …) can be divided for 16e and 16m– Time or Frequency are most reasonable resources to divide

: TDM vs. FDM for multiplexing legacy (16e) and 16m signals– Recommend to take a careful investigation in choosing TDM or

FDM in detail discussion phase based on proper evaluation.

• Downlink

• Uplink

or

or

<UL TDM> <UL FDM>

16mLegacy (16e)

UL subframe

OFDM symbols

Legacy (16e)

16m

UL subframe

SubC

H

OFDM symbols

SubC

H

<DL TDM> <DL FDM>

16mLegacy (16e)

DL subframe

OFDM symbols

Legacy (16e)

16m

DL subframe

SubC

H

OFDM symbols

SubC

H

5

Self Organizing Networks

6

Self Organizing Network Architecture

• Self Organization (SO) includes self-configuration and self-optimization.• Element Management System (EMS) performs SO functions over BSs.

– EMS is not in the scope of 16m• BS performs SO functions over neighboring BSs and MSs.• MS may perform measurement and report for SO operations.

Data Plane

Control Plane

Management Plane

SO Network architecture

MS MS

BS(SO)

BS(SO)

EMS(SO)

R1 R1

Scope of 16m

It also requires network side work.

7

Self Organization Mechanism

• SO procedures & signaling– Procedures may include measurement request/response for SO mechanism.– SO reference signals may be defined to enhance the SO mechanisms.

• Control signaling block may send the SO reference signal under supervision of SO block

MAC Common Part Sublayer

Higher Layer

Convergence Sublayer

PHY Layer

Control Signaling

Resource Mapping

Self Organization

Management plane Data/control plane

BS

EMS

SON Function

SON Function

Measurement

Control Management Scope of 16m project

MAC PDU formation

Encryption

Fragmentation/Packing

8

Single & Multi-Carrier Support

9

Definitions

• Multiple RF and PHY• Packet aggregation in MAC layer

5MHz

10MHz

20MHz

5MHz 5MHz 5MHz

10MHz

Multi-carrier

Sca

lable B

and

wid

th

Single-carrier

• Same OFDM symbol length• Same frequency subcarrier spacing

• Multi-carrier

• Single-carrier

• Scalable Bandwidth

10

Possible Single/Multi-Carrier Scenarios

MS5

MS4

BS

MS1

MS3

BS1 BS1’

BS

MS

BS RF+PHY

MS RF+PHYFrequency Overlay

MS5

MS4

MS1

MS3 MS3MS3

MS2 MS2

Possible scenarios

• Single carrier BS– BS, having a single wide band,

supports MSs with narrower BW– For inter-working (roaming)

among scalable bandwidths

• Multi carrier BS– Contiguous or Non-contiguous

bands– Single or Multiple bandwidths

(BS1 = BS1’ or BS1 < BS1’)– BS1/BS1’ = 16e/16m or

16m/16m

11

MIMO Architecture

12

MIMO Architecture

MIMO Encoding and Mapping

(to a basic time-frequency resource)

iFFT

iFFT

OFDMA Framing

Symbols per transmit antenna

Bit-level processing

QAM modulation

User selectionResource allocation

Codewords

Number of codewords

MCS setting

Buffer Data

Space-time encoding (STC, SM)

Closed-loop precoding (vector, matrix)

Packets selection

Resource block parsing

Bit streams

RRM, Scheduler

CQI and CSI feedbackRetransmission success/failure indication

Open-loop/closed-loop MIMO adaptation

Single-user/multiuser MIMO adaptation

Feedback requests and resource allocations to

mobile stations

Downlink control channels

Uplink feedback channels

13

MIMO Encoding and Mapping Block

• MIMO processing is uniquely described by the encoding and mapping:– Input: codewords of modulated symbols– Output: basic time-frequency resource block for each transmit

antenna

• A specific MIMO mode only needs adapting the processing blocks within the MIMO encoding and mapping block

• Selection of MIMO mode for adaptation to operating conditions may be based (among other things) on feedback of– Channel Quality Information (CQI)– Channel State Information (CSI)

• CQI and CSI may both be used in the scheduler, but also:– CQI: for modulation and coding rate adaptation in bit-level

processing– CSI: for signal processing within MIMO encoding and mapping block

14

MIMO Encoding & Mapping

Mapping of codeword symbols to MIMO

matrixPrecoder

Mapping matrix (or vector) symbols to a basic time-frequency

resource

Mapping basic time-frequency resource

to subchannels

OFDMA Framing

Other framing processes

MIMO matrix construction (layering, ST codeword)

One codeword for one MS

One codeword for one MS

Single-user / multiuserSingle / multiple

codewords OL MIMO / CL MIMO

MIMO Encoding & Mapping

• Support of single and multiple codewords • Support of diversity, multiplexing, precoding• Support of SU/MU MIMO, OL/CL MIMO• Precoder support for closed-loop MIMO:

– Beamforming with one or several beams– Beamforming to one or several users– Adaptation to short-term and/or long-term CSI

15

Q&A