• 沒有找到結果。

MAC subheaders and special payloads [Replace the first paragraph of with the following:][Replace the first paragraph of with the following:]

Amendment for Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in

6. MAC common part sublayer

6.3 Data/Control plane

6.3.2 MAC PDU formats .1 MAC header formats.1 MAC header formats

6.3.2.2 MAC subheaders and special payloads [Replace the first paragraph of with the following:][Replace the first paragraph of with the following:]

Six types of subheaders may be present in a MAC PDU with generic MAC header. The per-PDU subheaders (i.e., extended subheader field, Mesh, Fragmentation, Fast-feedback allocation and Grant Management) may be inserted in MAC PDUs immediately following the Generic MAC header. If both the Fragmentation sub-header and Grant Management subsub-header are indicated, the Grant Management subsub-header shall come first.

CTI 3 This field provides coherent time information.

Coherent Time Index: CTI indicates the estimated duration of the valid MIMO channel conditions

0b000: Infinite 0b001: 1 frame 0b010: 2 frames 0b011: 3 frames 0b100: 4 frames 0b101: 8 frames 0b110: 14 frames 0b111: 24 frames

This field is only present when CII is set to 0.

AI 4 This field is for Antenna Indication. It can support up to four antennas.

This feedback header can report a composite channel condition, each bit represents for each antenna; 1 is applicable, 0 is not applicable Antenna Index:

Bit 0 (MSB)- Antenna 0 Bit 1 — Antenna 1 Bit 2 — Antenna 2 Bit 3 (LSB) — Antenna 3

This field is only present when CII is set to 0.

MI 2 This field suggests the preferred STC/MIMO Matrix for the MS Matrix Indicator:

0b00: No STC 0b01: Matrix A 0b10: Matrix B 0b11: Matrix C

This field is only present when CII is set to 0.

CT 1 This field indicates the type of CQI feedback in the CQI field.

CQI Type: The type of CQI feedback in the CQI field 0: DL average CQI feedback

1: CQI feedback for the preferred bandwidth indicated in the current header

This field is only present when CII is set to 0.

CQI 5 CQI feedback

This field is only present when CII is set to 0.

CID 16 MS basic CID

This field is only present when CII is set to 1.

HCS 8 Header Check Sequence (same usage as HCS entry in Table 5).

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

If the Mesh subheader is indicated, it shall precede all other subheaders except for the extended subheader.

In the downlink, the Fast-feedback allocation subheader shall always appear as the last per-PDU subheader.

The ESF bit in the Generic MAC header indicates that the extended subheader is present. Using this field, a number of additional subheaders can be used within a PDU. The extended subheader shall always appear immediately after the Generic MAC header, and before all other subheaders. All extended subheaders are not encrypted. (See 6.3.2.2.7)

6.3.2.2.2 Grant Management subheader [Change Table 9 as indicated:]

[Insert the following new fields into Table 10:]

Table 9 Grant Management subheader format

Syntax Size

(bits) Notes

Grant Management Subheader { if (scheduling service type == UGS) {

SI 1

PM 1

FLI 1

FL 4

Reserved 149 Shall be set to zero

} else if (scheduling service type == Extended rtPS) {

Extended piggyback request 11

FLI 1

FL 4

} else{

Piggyback Request 16

} }

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

[Insert new subclause 6.3.2.2.7:]

6.3.2.2.7 Extended subheader format

The extended subheader group (see Figure 20l), when used, shall always appear immediately after the Generic MAC header and before all subheaders, and PN number (if MAC PDU is protected (i.e., when

Table 10 Grant management subheader fields

Name Size

(bits) Description

FLI 1 Frame latency indication

0 = Frame latency field disabled for this grant 1 = Frame latency field enabled for this grant

FL 4 Frame latency

The number of frames previous to the current one in which the transmitted data was available.

When the latency is greater than 15 then the FL field shall be set to 15.

Reserved 9

Extended Piggy-back Request

11 The number of bytes of uplink bandwidth requested by the MS. The bandwidth request is for the CID. The request shall not include any PHY overhead. The request shall be incremental. In case of the Extended rtPS, if the MSB is 1, the BS changes its polling size into the size specified in the LSBs of this field.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

EC=1)), as described in 6.3.2.2. The extended subheader group format is specified in Tables 13a, 13b and 13c. extended subheaders shall not be encrypted.

The fields of the extended subheader group structure are described in Table 13a.

The extended subheader group starts with an 8-bit length field that is followed by one or multiple extended subheaders. The length field specifies the total length in bytes of the subheader group, including all the extended subheaders and the length byte. Each extended subheader consists of a reserved bit, a 7-bit extended subheader type field, and a variable size extended subheader body. The size of each extended sub-header is determined by the extended subsub-header type as specified in Table 13b.

Figure 20l Extended subheader group format Extended sub-header group length (8 bits)

Extended sub-header type I (7 bits) Rsv=0

(1 bit)

Extended sub-header body 1 (variable length)

Extended sub-header type II (7 bits) Rsv=0

(1 bit)

Extended sub-header body 2 (variable length)

.. .

Extended sub-header type n (7 bits) Rsv=0

(1 bit)

Extended sub-header body n (variable length)

Length of Extended sub-header group

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

The list of defined extended subheaders is given in Table 13b for the DL and in Table 13c for the UL. The support of each extended subheader shall be negotiated between the BS and the MS as part of the registra-tion dialog (REG-REQ/RSP).

Table 13a Extended subheader group format

Name Size

(bits) Description

Extended subheader group length 8 The extended subheader Group Length field indicates the total length of the subheader group, including all the extended subheaders and the length byte.

Reserved 1 Reserved =0

Extended subheader type 7 Type of subheader as defined in Tables 13b and 13c Extended subheader body variable The size of the extended subheader is determined by

extended subheader type as specified in Tables 13b and 13c.

The size of the extended subheader body is byte aligned.

Table 13b Description of extended subheaders types (DL)

ES type Name ES body Size

(bytes) Description

0 SDU_SN extended subheader 1 See 6.3.2.2.7.1

1 DL Sleep control extended subheader 3 See 6.3.2.2.7.2 2 Feedback request extended subheader 3 See 6.3.2.2.7.3

3 SN request extended subheader 1 See 6.3.2.2.7.7

4 PDU SN(short) extended subheader 1 See 6.3.2.2.7.8 5 PDU SN(long) extended subheader 2 See 6.3.2.2.7.8 6-127 reserved

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

[Insert new subclause 6.3.2.2.7.1:]

6.3.2.2.7.1 SDU SN extended subheader

The SDU SN extended subheader shall only be sent by the BS if SDU SN extended subheader capability is supported (negotiated through REG-REQ/RSP) and if SDU_SN Feedback is enabled for a DL connection (negotiated through DSA-REQ/RSP). The SDU SN extended subheader shall contain the last virtual MAC SDU sequence number of current MAC PDU. The format of the SDU SN extended subheader is as described in Table 13d.

[Insert new subclause 6.3.2.2.7.2:]

6.3.2.2.7.2 DL Sleep control extended subheader

The DL Sleep control extended subheader is sent by the BS to activate/deactivate certain Power Saving Class. The requested operation is effective from the next frame after the one where the message was trans-mitted. The format of DL Sleep control extended subheader is as described in Table 13e.

Table 13c Description of extended subheaders types (UL)

ES type Name ES body Size

(bytes) Description 0 MIMO mode feedback extended

sub-header

1 See 6.3.2.2.7.4

1 UL Tx Power Report extended sub-header

1 See 6.3.2.2.7.5

2 Mini-Feedback extended subheader 2 See 6.3.2.2.7.6 3 PDU SN(short) extended subheader 1 See6.3.2.2.7.8

4 PDU SN(long) extended subheader 2 See 6.3.2.2.7.8

5-127 reserved

Table 13d SDU SN extended subheader format

Name Size

(bits) Description

SDU sequence number 8 Last virtual MAC SDU sequence number in the current MAC PDU.

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

[Insert new subclause 6.3.2.2.7.3:]

6.3.2.2.7.3 Feedback request extended subheader

Feedback request extended subheader shall be only sent by BS to provide UL allocation he Feedback header transmission. and BS shall indicate the allocation of applied frame. The format of the Feedback request extended subheader is as described in Table 13f.

[Insert new subclause 6.3.2.2.7.4:]

Table 13e DL Sleep control extended subheader format

Name Size

(bits) Description

Power_Saving_Class_ID 6 Power Saving Class ID this command refers to.

Operation 1 1 = activate Power Saving Class

0 = de-activate Power Saving Class

Final_Sleep_Window_Exponent 3 For Power Saving Class Type III only: assigned factor by which the final-sleep window base is multiplied in order to calculate the duration of single sleep window requested by the message.

Final_Sleep_Window_Base 10 For Power Saving Class Type III only: the base for duration of single sleep window requested by the message.

Reserved 4

Table 13f Feedback request extended subheader format

Name Size

(bits) Description

UIUC 4

Feedback type 4 Shall be set according to Table 7i OFDMA Symbol

offset

6 The offset is relevant to the Allocation Start Time field given in the UL-MAP message.

Subchannel offset 6 The lowest index subchannel used for carrying the burst, starting from Subchannel 0.

No.slot 3 The number of slots allocated for the burst

Frame offset (F) 1 Indicate to start reporting at the frame. If F == 0, the allocation applies to the UL subframe two frames ahead of the current frame. If F==1, four frames ahead of the current frame.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

6.3.2.2.7.4 MIMO mode Feedback extended subheader

An MS uses the MIMO Feedback extended subheader to provide its feedback in terms of MIMO mode feed-back. When there is an UL MAC PDU payload to be transmitted at the same time. The format of the MIMO mode Feedback extended subheader is as described in Table 13g:

For each MS, if a MIMO mode Feedback extended subheader is present, it shall only appear in the first uni-cast PDU transmitted by that MS in that frame.

[Insert new subclause 6.3.2.2.7.5:]

6.3.2.2.7.5 UL Tx Power Report extended subheader

This subheader is sent from MS to BS to report the Tx power of the burst that carries this subheader. The for-mat of the UL Tx Power Report extended subheader is as described in Table 13h:

[Insert new subclause 6.3.2.2.7.6:]

6.3.2.2.7.6 Mini-Feedback extended subheader

The format of the mini-feedback extended subheader is shown in Table 13i:

Table 13g MIMO mode Feedback extended subheader format

Name Length

(bits) Description

Feedback type 2 0b00: feedback type 0b000 as defined in Table 302a 0b01: feedback type 0b001 as defined in Table 302a 0b10: feedback type 0b010 as defined in Table 302a 0b11: feedback type 0b011 as defined in Table 302a Feedback content 6 Feedback contents and the corresponding feedback payload

(6 bits) are the same as that defined in Table 302a and sec-tions 8.4.5.4.10.4, 8.4.5.4.10.5, 8.4.5.4.10.6, 8.4.5.4.10.7, 8.4.5.4.10.8, 8.4.5.4.10.9, 8.4.5.4.10.10 for the Enhanced Fastfeedback channel

Table 13h UL Tx Power Report extended subheader format

Name Size

(bits) Description

UL Tx Power 8 Tx power level for the burst carries this

header (11.1.1). The value shall be esti-mated and reported for the burst.

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

[Insert new subclause 6.3.2.2.7.7:]

6.3.2.2.7.7 SN request extended subheader

The SN request extended subheader is sent by the BS to request the MS to send the SN report header. The fields of the SN request extended subheader are defined in Table 13j.

[Insert new subclause 6.3.2.2.7.8:]

6.3.2.2.7.8 PDU SN extended subheader

Specify the PDU sequence number in a monotonic increasing manner. The format of the PDU SN extended subheader is as described in Table 13k and Table 13l.

Table 13i Description of Mini-Feedback extended subheaders (UL)

Name Size

(bits) Description

Feedback type 4 Type of feedback: see Table 7i

Feedback content 12

Table 13j Description of SN request extended subheader

Name Size

(bits) Description

SN report indication 2 Bit #0: set to 1 to request transmission of the first SN report header

Bit #1: set to 1 to request transmission of the sec-ond SN report header

reserved 6 Shall be set to zero

Table 13k PDU (short) SN extended subheader

Name Size

(bits) Description

PDU SN (short) 8 Specify the PDU SN number

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

6.3.2.3 MAC Management messages

相關文件