IEEE C802.16m-09/0660
1
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Text for the Draft P802.16m Amendment on the PHY Structure for BWREQ
channel
Date
Submitted
2009-03-06
Source(s)
Yuan Zhu, Xiangying Yang, Roshni
Srinivasan, Jong-kae Fwu, Hujun Yin
E-mail: (yuan.y.zhu, Xiangying.Yang,
Roshni.m.Srinivasan, Jong-kae.fwu,
Hujun.Yin)@intel.com
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
Re:
802.16m amendment working document
Abstract
Proposed text for the PHY structure for UL control in the draft P802.16m amendment
Purpose
Discussion and adoption by TGm
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>.
Notice
Release
Patent
Policy
2
3
4
5
6
7
8
Proposed Text for the Draft P802.16m Amendment on the PHY
Structure for BWREQ Control
Yuan Zhu, Xiangying Yang, Roshni Srinivasan, Jong-Kae (JK) Fwu, Hujun Yin
Intel
Introduction
9
10
11
This contribution provides additional amendment text for the BWREQ channel Structure in the Advanced Air
Interface to be included in Section 15 of the IEEE 802.16m Amendment Working Document [1]. The text was
developed based on UL Control Drafting group output [2].
12
References
1
IEEE C802.16m-09/0660
1
[1]
IEEE 802.16m Amendment Working Document, IEEE 802.16m-08/050
2
3
[2]
“Proposed Text for the Draft P802.16m Amendment on the PHY Structure for UL Control”, IEEE
C802.16m-09/386.
4
5
6
7
8
9
10
Proposed Amendment Text
The following text is proposed for inclusion in Section 15 of the IEEE 802.16m Amendment Working
Document [1].
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
[
------------------- Recommended AWD Text Proposal #10 --------------------]
15.3.9.2.1.
Bandwidth request Channel
[Proposed text starts]
Contention based random access is used to transmit bandwidth request information on this control channel.The
bandwidth request (BW REQ) channel contains resources for the AMS to send a BW REQ access sequence and
an optional quick access message. Prioritized bandwidth requests are supported on this channel. The mechanism
for such prioritization is TBD.
The random access based bandwidth request procedure for MZone or LZone with AMC is described in Figure
UL- 1. In these cases, aA 5-step regular procedure (step 1 to 5) or an optional 3-step quick access procedure
(step 1, 4 and 5) may be supported concurrently. Step 2 and 3 are used only in 5-step regular procedure. In step
1, AMS sends a bandwidth request indicator and a message for quick access. The 5-step regular procedure is
used independently or as a fallback mode for the 3-step bandwidth request quick access procedure. The AMS
may piggyback additional BW REQ information along with user data during uplink transmission (step 5).
Following Step 1 and Step 3, ABS may acknowledge the reception of bandwidth request. If AMS does not
receive any acknowledgement or UL grant, it waits until the expiration of a pre-defined period and restarts the
bandwidth request. The pre-defined period may be differentiated by factors such as QoS parameters (e.g.
scheduling type, priority, etc). In case BW is granted immediately, there is no need for ABS to send explicit
ACK.
2
IEEE C802.16m-09/0660
Bandwidth Request indicator and
quick access message
Acknowledgement for BR indicators
2
1
UL grant for BW REQ message
MS
BS
BW REQ message
3
Acknowledgement for BW REQ
4
UL grant
UL scheduled transmission with optional
piggybacked bandwidth request
5
1
2
Figure UL- 1, Bandwidth Request Procedure in MZone or LZone with AMC.
3
4
5
The bandwidth request procedure for LZone with PUSC is described in Figure UL-n. In LZone with PUSC, only
a 5-step regular procedure is supported. In step 1, AMS sends a bandwidth request indicator only. The rest of
bandwidth request procedure in LZone with PUSC shall be the same as the 5-step procedure in Figure UL-8.
Bandwidth Request indicator
1
Acknowledgement for BR indicators
2
UL grant for BW REQ message
3
MS
BS
BW REQ message
Acknowledgement for BW REQ
4
UL grant
UL scheduled transmission with optional
piggybacked bandwidth request
5
6
7
Figure UL-n Bandwidth Request Procedure in LZone with PUSC
8
9
10
11
As shown in Figure UL- 2, in the LZone with PUSC, one BW REQ tile consists of 4 contiguous subcarriers by 6
OFDM symbols. The total 72 subcarriers of one LZone BRCH are indexed firstly in frequency, secondly in
OFDM symbol and lastly in tile as in Figure UL- 2. Each BW REQ tile carries a BW REQ access sequence.
3
IEEE C802.16m-09/0660
1
2
3
4
5
6
In the MZone, the total 108 subcarriers of one MZone BW REQ channel are indexed one tile at a time, firstly in
frequency, then in OFDMA symbol as in Figure UL- 3.
Time
0
1
22
23
Frequency
24
25
46
47
48
49
70
71
7
8
Figure UL- 2, 4x6 BW REQ tile structure.
9
10
11
Time
0
1
34
35
Frequency
36
37
70
71
72
73
106
107
12
13
Figure UL- 3, 6x6 BW REQ Tile Structure in the Advance Air Interface.
14
15
16
A BW REQ tile in the Advanced Air Interface specifications is defined as 6 contiguous subcarriers by 6 OFDM
symbols. As illustrated in Figure UL-1, a BW REQ access sequence (BW REQ preamble) shall be transmitted
in step-1 of the bandwidth request procedure. As shown in Figure 1, the BW REQ preamble shall be transmitted
4
IEEE C802.16m-09/0660
1
2
3
4
5
on a resource that spans 4 subcarriers by 6 OFDM symbols. Additionally, a quick access BW REQ message
shall be carried in the data portion of the tile that spans 2 contiguous subcarriers by 6 OFDM symbols. Each BW
REQ channel shall comprise of 3 distributed BW REQ tiles for frequency diversity. The procedure for allocation
of resources for transmission of UL control information and the formation of DRUs for such transmission is
TBD.
Time
Frequency
Prn,0
Prn,1
Mn,0
Mn,1
Prn,2
Prn,3
Prn,4
Prn,5
Mn,6
Mn,7
Prn,6
Prn,7
Prn,8
Prn,9
Mn,12
Mn,13
Prn,10
Prn,11
Prn,12
Prn,13
Mn,18
Mn,19
Prn,14
Prn,15
Prn,16
Prn,17
Mn,24
Mn,25
Prn,18
Prn,19
Prn,20
Prn,21
Mn,30
Mn,31
Prn,22
Prn,23
Prn,24
Prn,25
Mn,2
Mn,3
Prn,26
Prn,27
Prn,28
Prn,29
Mn,8
Mn,9
Prn,30
Prn,31
Prn,32
Prn,33
Mn,14
Mn,15
Prn,34
Prn,35
Prn,36
Prn,37
Mn,20
Mn,21
Prn,38
Prn,39
Prn,40
Prn,41
Mn,26
Mn,27
Prn,42
Prn,43
Prn,44
Prn,45
Mn,32
Mn,33
Prn,46
Prn,47
Prn,48
Prn,49
Mn,4
Mn,5
Prn,50
Prn,51
Prn,52
Prn,53
Mn,10
Mn,11
Prn,54
Prn,55
Prn,56
Prn,57
Mn,16
Mn,17
Prn,58
Prn,59
Prn,60
Prn,61
Mn,22
Mn,23
Prn,62
Prn,63
Prn,64
Prn,65
Mn,28
Mn,29
Prn,66
Prn,67
Prn,68
Prn,69
Mn,34
Mn,35
Prn,70
Prn,71
6
7
8
9
Figure 1: 6x6 BW REQ Tile Structure in the Advance Air Interface
Let b0b1b2 ...b15 denote a total of 16 bits of information which can be carried in the quick access message. The
10
last 4 bits b12b13b14b15 shall be carried in the BW REQ preamble using the preamble index. The combined
11
12
resource in the data portions of the three tiles that form the BRCH shall be used to transmit the first 12 bits of
information, b0b1b2 ...b11 . Figure 2 illustrates the construction of the BW REQ preamble and quick access
13
message for a 6x6 tile structure.
5
IEEE C802.16m-09/0660
4 bits
Bandwidth
Request
Message
12 bit Bandwidth
Request Message
72 BW REQ CH
Preamble
symbols
Sequence
Selection
Scrambling
108 BW
REW CH
symbols
36 BW REQ CH
Data symbols
Channel
encoding
(Block
Codes)
Randomizer
Mtuliplexing&
Normalization
Modulation
(BPSK)
×
Scrambling
αd
1
2
Figure 2: Bandwidth Request Channel structure with 6x6 tiles
3
4
5
6
7
The logical preamble sequence index, BWREQ_PREAMBLE_INDEX, which is configured by the upper layer
and 4 bits of the bandwidth request message shall be used to select three sequences of length 24 from Table 1 in
order to construct 72 preamble symbols. As shown in Figure 2 , the 72 preamble symbols shall be scrambled
before multiplexing with data symbols in the BRCH.
8
Table 1: BRCH Preamble sequences
pu (k ), 0  k  24
u
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
9
10
11
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
-1
1
1
1
-1
1
-1
-1
1
-1
-1
1
-1
1
1
1
-1
1
-1
-1
1
-1
-1
1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
1
1
1
1
1
1
1
1
1
1
1
1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
1
1
-1
1
1
1
-1
-1
-1
1
-1
1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
-1
-1
1
1
-1
1
1
1
-1
-1
-1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
1
1
-1
1
1
1
-1
-1
-1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
1
-1
-1
1
-1
1
1
-1
1
1
1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
-1
-1
-1
1
-1
1
1
-1
1
1
1
-1
1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
-1
-1
-1
-1
1
-1
1
1
-1
1
1
1
The preamble sequences transmitted in the three BW REQ tiles of a BRCH are defined as
6
1
-1
1
1
1
-1
1
-1
-1
1
-1
-1
-1
1
-1
-1
-1
1
-1
1
1
-1
1
1
1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
-1
1
1
-1
-1
-1
1
-1
1
1
-1
1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
1
1
1
-1
-1
-1
1
-1
1
1
-1
1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
-1
-1
1
1
1
-1
-1
-1
1
-1
1
1
1
-1
1
-1
-1
-1
1
1
1
-1
1
-1
-1
1
-1
1
1
1
-1
-1
-1
1
-1
1
IEEE C802.16m-09/0660
1
Prn,24mk  pum (k), 0  k  24, 0  m  3, 0  um  24
2
3
4
where n is BRCH channel index, k is symbol index in the preamble portion of a BW REQ tile, m is BW
REQ tile index, um is sequence index in BW REQ tile m .
5
6
7
The mapping between the combination of the logical preamble sequence index, BWREQ_PREAMBLE_INDEX
and the 4 bits of the bandwidth request message b12b13b14b15 to the physical preamble index, um ,0  m  3 is as
8
9
below equation.
um,=mod( BWREQ_PREAMBLE_INDEX+ bin2dec( b12b13b14b15 ), 24)
10
11
The first 12 bits of information b0b1b2 ...b11 in the quick access message transmitted in the BRCH shall be
12
encoded into 36 bits c0 , c1 , c2 ,
13
14
source not found.. The 36 coded bits shall then be BPSK modulated as described in Section TBD and
scrambled to generate 36 data symbols, v0 , v1 ,...v35 . The combined data portions of the three distributed BW
15
16
REQ tiles that form the BRCH shall be used to transmit these data symbols. The data symbols shall be scaled by
 d before multiplexing with preamble symbols and the scaling factor  d is configured by the MAC layer. The
17
mapping of the 36 data symbols to the data portions of three distributed 6×6 BW REQ tiles in a BRCH is given
18
in Table 2. The final 108 modulated BRCH symbols shall be scaled by a factor of
19
the total transmitted energy.
20
c35 using the linear block code (36, 12) described in section Error! Reference
Table 2: Mapping of data symbols to subcarriers in the data portion of the BW REQ Tile
 n ,12 m  k , 0  k  12
BW REQ tile index
m
21
22
23
24
25
26
3  2   d2  to normalize
0
 d v0 ,  d v1 ,  d v6 ,  d v7 ,  d v12 ,  d v13 ,  d v18 ,  d v19 ,  d v24 ,  d v25 ,  d v30 ,  d v31
1
 d v2 ,  d v3 ,  d v8 ,  d v9 ,  d v14 ,  d v15 ,  d v20 ,  d v21 ,  d v26 ,  d v27 ,  d v32 ,  d v33
2
 d v4 ,  d v5 ,  d v10 ,  d v11 ,  d v16 ,  d v17 ,  d v22 ,  d v23 ,  d v28 ,  d v29 ,  d v34 ,  d v35
In order to support operation in the legacy mode, a BW REQ tile shall be defined as 4 contiguous subcarriers by
6 OFDM symbols. As shown in Figure 3, only the BW REQ access sequence or BW REQ preamble shall be
transmitted in all 24 subcarriers that form the BW REQ tile. In this case, the BWREQ_PREAMBLE_INDEX
shall be randomly selected from all available logical preamble sequences, as shown in Figure 3.
7
IEEE C802.16m-09/0660
Time
Frequency
Prn,0
Prn,1
Prn,2
Prn,3
Prn,4
Prn,5
Prn,6
Prn,7
Prn,8
Prn,9
Prn,10
Prn,11
Prn,12
Prn,13
Prn,14
Prn,15
Prn,16
Prn,17
Prn,18
Prn,19
Prn,20
Prn,21
Prn,22
Prn,23
Prn,24
Prn,25
Prn,26
Prn,27
Prn,28
Prn,29
Prn,30
Prn,31
Prn,32
Prn,33
Prn,34
Prn,35
Prn,36
Prn,37
Prn,38
Prn,39
Prn,40
Prn,41
Prn,42
Prn,43
Prn,44
Prn,45
Prn,46
Prn,47
Prn,48
Prn,49
Prn,50
Prn,51
Prn,52
Prn,53
Prn,54
Prn,55
Prn,56
Prn,57
Prn,58
Prn,59
Prn,60
Prn,61
Prn,62
Prn,63
Prn,64
Prn,65
Prn,66
Prn,67
Prn,68
Prn,69
Prn,70
Prn,71
1
2
Figure 3: 4x6 BW REQ tile structure
3
Random
Sequence
Selection
4
5
Scrambling
Figure 4: 4x6 Bandwidth Request Channel structure with 4x6 tiles
6
7
8
[Proposed text Ends]
9
[
10
11
12
13
14
15
16
72 BRCH
Preamble
symbols
------------------- Recommended AWD Text Proposal #13 --------------------]
15.3.9.3.1.
Bandwidth request Channel
[Proposed text starts]
When the 3-step quick access bandwidth request is used, a quick access message is sent in step-1 along with a
BW REQ preamble sequence. The quick access message and the corresponding preamble index contain 16-bit
information, including bandwidth request ID that uniquely identifies the MS, the request size, QoS ID. The
message format is as follows
Length (bit) Description
note
BWREQ ID
10
Uniquely identifies the MS Negotiated during MS network entry
BWREQ size
2
00: 1PRU (with lowest
Buffer size report with ariable granularity
MCS defined in cell)
01: 2PRU
8
IEEE C802.16m-09/0660
1
2
3
4
5
6
7
QoS ID
[Flow ID]
1
[2]
[4]
Reserved
[3]
10: 3PRU
11: max buffer request
negotiated during MS
network entry for this QoS
class
0: 50ms
1: 100ms
A QoS ID corresponding to a specific latency
requirement. This implies that best-effort
traffic will only perform 5-step regular
BWREQ.
[4bit Flow-ID consistent with connection
addressing]
When 3-step quick access is used, MS shall set BWREQ_PREAMBLE_INDEX according to equation XX-4
before accessing the BW REQ channel.
BWREQ_PREAMBLE_INDEX= mod(mod(m, 24)  mod( m / 24  t, 24), 24)
equation XX-4
where m is BWREQ ID and t is BW REQ opportunity index monotonically increasing with time.
[Proposed text ends]
9