IEEE C802.16-08/501
1
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed resolution to pending issues in C80216m-08_297
Date
Submitted
2008-05-12
Source(s)
Mihyun Lee, Jaeweon Cho, Hokyu
Choi, Jaehee Cho, Heewon Kang
Voice: +82-31-279-0390
E-mail:
mihyun.mac.lee@samsung.com
Samsung Electronics Co., Ltd.
Rakesh Taori
Samsung Advanced Inst. of
Technol]ogy
Re:
Final Draft of DL Control Rapportuer Group Contribution(C80216m-08_297): SDD Text
on Downlink Control Structure
Abstract
This contribution proposes the resolution to the pending issues for the DL control
structure as drafted in the document (C802.16m-08_297) prepared by the DL Control
Rapporteur Group.
Purpose
To be incorporated into the SDD text for DL control structure.
Notice
Release
Patent
Policy
2
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.
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.
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>.
Proposed resolution to pending issues in C80216m-08_297
3
4
Mihyun Lee, Jaeweon Cho, Hokyu Choi, Jaehee Cho, Heewon Kang
5
Samsung Electronics Co., Ltd.
6
Rakesh Taori
7
Samsung Advanced Inst. of Technology
1
IEEE C802.16-08/501
1
2
3
4
5
6
7
8
9
This contribution proposes the resolution to the pending issues in C802.16mDL_ctrl-08/297, i.e. final
draft of the DL Control Rapporteur Group Contribution. In another contribution, we have proposed an
alternative ToC (Doc Nr: C802.16mDL_ctrl-08/52.doc). In this document, unmodified ToC is used and
the focus is on the text for pending issues.
--------------------------------------------------------- Proposed text --------------------------------------------------------11.x
DL Control Structure
10
11
11.x.1. DL Control Information Classification
12
13
11.x.1.1.
14
15
16
17
18
19
11.x.1.2.
Essential system parameters and system configuration information
We propose the resolution to the pending issue in Section 11.x.1, page 4 and lines 30 ~ 32:
We propose to remove the classification of Information Type 2a, 2b and 2c at this stage because we think that
this classification, if necessary, can be done in Stage 3.
20
21
22
23
24
25
11.x.1.2.1.
26
27
28
29
30
31
11.x.1.2.2.
32
33
34
35
36
37
38
39
11.x.1.2.3.
Synchronization information
[
Network-wide common essential system parameters and system configuration
information (Type 2a)
This includes a minimal set of time critical PHY layer parameters that are common among all sectors
in the network and essential for decoding the DL. Examples of this type of information include CP
length, system bandwidth (at least DL bandwidth, UL bandwidth may be classified as Type 2C if
asymmetric bandwidth is supported), TDD ratio, superframe index, etc.
Sector-specific DL essential system parameters and system configuration
information (Type 2b)
This includes a minimal set of time critical system configuration and parameters information that are
sector-specific and are needed for the MS to decode the DL broadcasted system message that are
carried on the traffic channels. Examples of this type of information include antenna configuration, DL
resource allocation configuration, pilot configuration, 16e/16m co-existence configuration, etc.
Remaining essential system parameters and system configuration information
(Type 2c)
This includes a minimal set of time critical system configuration and parameters information that are
needed for the MS to initiate access on the UL. Examples of this type of information include UL
resource allocation configuration (if different from the DL one), system configuration for initial ranging,
UL bandwidth if asymmetric bandwidth is supported, UL power control parameters, etc.
]
2
IEEE C802.16-08/501
1
2
3
4
5
6
11.x.2. Synchronization Channel (SCH)
We propose that the pending resolution on the topic of SCH be deferred until after the discussions on DL
Preamble design.
The text for SCH is TBD.
7
8
9
10
11
11.x.3. Broadcast Control Channel
We propose the following resolution to the pending issue in section 11.x.3, page 6 and line 2:
Move the text in section 11.x.3, page 6 and line 30 to section 11.x.8 because the relationship b.t.w information
type and DL control channel is described in section 11.x.8.
12
13
11.x.3.1.
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
11.x.3.2.
Location of the BCH
We propose the following resolution to the pending issue in section 11.x.3.2, page 7 and lines 39 ~ 41:
As the title suggests, the main issue here is the location of the BCH and not the location of the superframe
header (SFH) and the SCH. The location of the SFH is already discussed in the SDD (See SDD section 11.4.1
on page 20, line 5). If changes are required to SDD section, it can be handled through comments on the SDD. It
is OK to discuss location of the BCH in this section. Our proposal is to adopt the following text for the location
of BCH:
31
32
33
34
35
36
37
38
39
40
41
42
43
11.x.3.3.
Multiplexing of the BCH with control and data
We propose the following resolution to the pending issue in section 11.x.3.3, page 8 and line 31:
This does not need to be discussed at all. This is because we first need to discuss whether other control
channels will exist or not, which is discussed in the remaining pending resolutions.
So we propose to delete the pending resolution. (Note: The text on line 34 is OK).
Primary Broadcast Channel (PBCH) and Secondary Broadcast Channel (SBCH)
The BCH is transmitted in the superframe header (SFH).
Option 1 deals with the SCH, but SCH should be described in section 11.x.2.
We propose the following resolution to the pending issue in section 11.x.3.2, page 8 and lines 6 ~ 8:
As mentioned above and as the title suggests, the main issue here is the location of the BCH and not the
location of the superframe header (SFH). The location of SFH is already discussed in the SDD (See SDD
section 11.4.1 on page 20, line 5). We propose to delete the text on section 11.x.3.2, page 8 and lines 10 ~ 24.
The BCH is TDM with the SCH.
We propose the following resolution to the pending issue in section 11.x.3.3, page 8 and line 38:
Discussing how to multiplex BCH with other control channels, without deciding what these control channels
are, is not the correct order. First decide whether there should be other control channels in the SFH. We
propose that this issue should be marked for FFS.
3
IEEE C802.16-08/501
1
2
3
4
5
6
7
8
9
10
11
12
13
14
The presence of other controls in SFH is FFS.
15
16
17
18
19
20
21
22
23
24
25
26
27
11.x.3.4.
Transmission format
We propose the following resolution to the pending issue in section 11.x.3.4, page 10 and lines 4 ~ 6:
We would like two things to be considered:
Firstly, there only seems to be consensus on BCH being in the SFH. Whether other control channels are
included or not is TBD. Therefore, we propose to limit the discussions on “BCH in SFH”.
Secondly we feel that the reason for fixing the format is robustness (especially if cell edge and cell center users
must decode the same information). However, in case of frequency reuse, it may be possible to be more flexible.
Therefore, we propose that the transmission format when frequency re-use is considered, should be left open at
this stage.
28
29
11.x.3.5.
30
31
32
33
34
11.x.4. Additional broadcast information
We propose the following resolution to the pending issue in section 11.x.4, page 10 and line 28:
At this stage, it is totally unclear what “Additional Broadcast information” actually is. To be efficient, we
should defer discussion on the section until it becomes clear whether such a section is necessary.
35
11.x.5. Unicast Service Control Channels
36
11.x.6. Multicast Service Control Channels
37
38
39
11.x.7. Multi-carrier Control Structure
We propose the following resolution to the pending issue in section 11.x.3.3, page 9 and lines 18 ~ 21
If we choose FDM for multiplexing SFH with other control channels, it is a better design choice from a
minimum bandwidth support perspective. So, we propose to adopt option 1 which supports FDM.
The BCH in the SFH is FDM with other control channels in the same subframe. (Option 1)
We propose the following resolution to the pending issue in section 11.x.3.3, page 9 and lines 32 ~ 34:
For the same reason as mentioned above, we propose to adopt option 1.
Data spans entire subframe in time, BCH in the SFH is FDM with data within the same subframe.
(option 1)
The BCH in tThe SFH is transmitted using a fixed modulation and coding rate. The modulation and
coding rate are TBD. The transmission format for frequency reuse may be considered further.
Resource allocation (physical to logical mapping, pilots, block size)
[
4
IEEE C802.16-08/501
1
2
3
4
11.x.8. Mapping of information into control channels
Broadcast information includes essential system parameter and system configuration information.
]
5