IEEE Std 802.16"'-2004
`(Revision of IEEE Std 802.16-2001)
`
`802.16™
`
`IEEE Standard for
`Local and metropolitan area networks
`
`Part 16: Air Interface for Fixed
`Broadband Wireless Access Systems
`
`IEEE Computer Society
`and the
`IEEE Microwave Theory and Techniques Society
`
`Sponsored by the
`LAN/MAN Standards Committee
`
`+.IEEE
`
`3 Park Avenue, New York, NY 10016-5997, USA
`
`1 October 2004
`
`Print: SH95246
`PDF: SS95246
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 1
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16™-2004
`(Revision of
`IEEE Std 802.16-2001)
`
`IEEE Standard for
`Local and metropolitan area networks
`
`Part 16: Air Interface for Fixed
`Broadband Wireless Access Systems
`
`Sponsor
`LAN/MAN Standards Committee
`of the
`IEEE Computer Society
`
`and the
`IEEE Microwave Theory and Techniques Society
`
`Approved 24 June 2004
`
`IEEE-SA Standards Board
`
`• •
`•
`•
`•
`•
`• ~ IEEE ¥ .
`WirelessMAN®
`•
`802.16 ~ •
`•
`•
`• • • •
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 2
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`Grateful acknowledgment is made to Cable Television Laboratories for the permission to use the following
`source material:
`
`Radio Frequency Interface Specification (version I. I), part of Data-Over-Cable Service Interface
`Specifications, © Copyright J 999, Cable Television Laboratories.
`
`Baseline Privacy Plus Interface Specification,© Copyright 1999, Cable Television Laboratories.
`
`Abstract: This standard specifies the air interface of fixed broadband wireless access (BWA)
`systems supporting multimedia services. The medium access control layer (MAC) supports a
`primarily point-to-multipoint architecture, with an optional mesh topology. The MAC is structured
`to support multiple physical layer (PHY) specifications, each suited to a particular operational
`environment. For operational frequencies from 10-66 GHz, the PHY is based on single-carrier
`modulation. For frequencies below 11 GHz, where propagation without a direct line of sight
`must be accommodated, three alternatives are provided, using OFDM, OFDMA, and single(cid:173)
`carrier modulation. This standard revises and consolidates IEEE Std 802.16-2001 , IEEE Std
`802.16a ™-2003, and IEEE Std 802.16c ™-2002.
`
`Keywords: fixed broadband wireless access network, metropolitan area network, microwave,
`millimeter wave, WirelessMAN® standards
`
`The Institute of Electrical and Electronics Engineers, Inc.
`3 Park Avenue, New York, NY 10016-5997, USA
`
`Copyright© 2004 by the Institute of Electrical and Electronics Engineers, Inc.
`All rights reserved. Published 1 October 2004. Printed in the United States of America.
`
`IEEE, 802, and WirelssMAN are registered trademarks in the U.S. Patent & Trademark Office, owned by the Institute of
`Electrical and Electronics Engineers, Incorporated.
`
`WirelessMAN-OFDM, WirelessMAN-OFDMA, WirelessMAN-SC, and WirelessMAN-SCa, are trademarks owned by the
`Institute of Electrical and Electronics Engineers, Incorporated.
`
`Print:
`PDF:
`
`ISBN 0-7381-4069-4 SH95246
`ISBN 0-7381-4070-8 SS95246
`
`No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior
`written permission of the publisher.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 3
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`AIR INTERFACE FOR FIXED BROADBAND WIRELESS ACCESS SYSTEMS
`
`IEEE Std 802.16-2004
`
`6.3.10 Ranging
`
`Ranging is a collection of processes by which the SS and BS maintain the quality of the RF communication
`link between them. Distinct processes are used for managing uplink and downlink. Also some PHY modes
`support ranging mechanisms unique to their capabilities.
`
`6.3.10.1 Downlink burst profile management
`
`The downlink burst profile is determined by the BS according to the quality of the signal that is received by
`each SS. To reduce the volume of uplink traffic, the SS monitors the CINR and compares the average value
`against the allowed range of operation. This region is bounded by threshold levels. If the received CINR
`goes outside of the allowed operating region, the SS requests a change to a new burst profile using one of
`two methods. If the SS has been granted uplink bandwidth (a data grant allocation to the SS's Basic CID),
`the SS shall send a DBPC-REQ message in that allocation. The BS responds with a DBPC-RSP message. If
`a grant is not available and the SS requires a more robust burst profile on the downlink, the SS shall send a
`RNG-REQ message in an Initial Ranging interval. With either method, the message is sent using the Basic
`CID of the SS. The coordination of message transmit and receipt relative to actual change of modulation is
`different depending upon whether an SS is transitioning to a more or less robust burst profile. Figure 79
`shows the case where an SS is transitioning to a more robust type. Figure 80 shows transition to a less robust
`burst profile.
`
`The SS applies an algorithm to determine its optimal burst profile in accordance with the threshold
`parameters established in the DCD message in accordance with Figure 81.
`
`Copyright © 2004 IEEE. All rights reserved.
`
`199
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 4
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16-2004
`
`IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS-PART 16:
`
`BS
`
`-
`,
`
`Send DL data at
`DIUCk
`
`ss
`
`RN G-REQ or DBPC-REQ
`Change to DIUC k
`
`DL Data at DIUC k
`
`
`
`RN G-RSP or DBPC-R SP
`
`- - - - Yes l
`
`Continue
`monitoring DL data
`through DIUC n
`
`N 0
`
`-
`
`'
`
`Monitor DL only
`data through
`DIUCk
`
`DL Data at DIUC k
`
`-
`
`•
`'
`Figure 79- Transition to a more robust burst profile
`
`200
`
`Copyright© 2004 IEEE. All rights reserved.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 5
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`AIR INTERFACE FOR FIXED BROADBAND WIRELESS ACCESS SYSTEMS
`
`IEEE Std 802.16-2004
`
`BS
`
`ss
`
`~
`
`RN G-REQ or DBPC-REQ
`Change to DIUC m
`
`- - - -Yes i
`
`Start monitoring
`DL data through
`DIUCm
`
`RN G-RSP or DBPC-R SP
`
`~
`
`N 0
`
`Send DL data at
`DIUCm
`
`DL Data at DIUC m
`
`Figure SO-Transition to a less robust burst profile
`
`::::: ~·
`
`~ z
`
`()
`
`0
`
`Figure 81-Burst profile threshold usage
`
`Copyright © 2004 IEEE. All rights reserved.
`
`201
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 6
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16-2004
`
`IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS-PART 16:
`
`6.3.17.1 Subpacket generation
`
`H-ARQ operates at the FEC block level. The FEC encoder is responsible for generating the H-ARQ sub(cid:173)
`packets, as defined in the relevant PHY section. The subpackets are combined by the receiver FEC decoder
`as part of the decoding process.
`
`6.3.17.2 DUUL ACK/NAK signaling
`
`For DL/UL H-ARQ, fast ACK/NAK signaling is necessary. For the fast ACK/NAK signaling of DL H-ARQ
`channel, a dedicated PHY layer ACK/NAK channel is designed in UL. For the fast ACK/NAK signaling of
`UL fast feedback, H-ARQ ACK message is designed.
`
`6.3.17.3 H-ARQ parameter signaling
`
`The parameters for each subpacket should be signaled independent of the subpacket burst itself. The
`parameters for each subpacket include
`
`SPID: The BS shall set this field to the subpacket identifier for the subpacket transmission.
`ACID: The BS shall set this field to the ARQ channel identifier for the subpacket transmission.
`Al_ SN: This toggles between " O" and "I " on successfu lly transmitting each encoder packet with the
`same ARQ channel.
`
`For the signaling of those parameters, H-ARQ Allocation IE is defined and the fE is to be placed in a OL(cid:173)
`M AP or UL-MAP for a burst where H-ARQ is used.
`
`6.3.17.4 CQICH Operations
`
`This subclause describes the operation scenarios and requirements ofCQl'CH, which is designed for H-ARQ
`enabled SS. After an SS turns on its power, the only appropriate subchannels that can be allocated to the
`MSS are normal subchannels. To determine the MIC level of normal subchannels, the average CINR
`measurement is enough for the BS to determine the M/C levels of uplink and downlink. As soon as the BS
`and the SS know the capabilities of both entities modulation and coding, the BS may allocate a CQICH
`subchannel using a CQICH Control IE. Then, the MSS reports the a verage CINR of the BS preamble. From
`then on, the BS is able to determine the M/C level. A CINR measurement is quantized into 32 levels and
`encoded into 5 information bits.
`
`At any time, the BS may de-allocate the SS' CQICH by putting another CQICH Control IE with Duration
`d = 0000. Before the CQICH life timer (which is set at the receipt of the CQICH Control IE expires) sending
`another CQICH Control IE overwrites all the information related to the CQICH such as Allocation Index,
`Period, Frame offset, and Duration. Hence, unless the BS refreshes the timer, the SS should stop reporting as
`soon as the timer expires. However, in case of sending the MAP IE for re-allocation or deallocation, the BS
`should make sure if the previous CQICH is released before it is re-allocated to another SS.
`
`The SS sends the REP-RSP message in an unsolicited fashion to BS to trigger Band AMC operation. The
`triggering conditions are given by TLV encodings in UCO messages. The REP-RSP (see 11.12 for the TLY
`encodings) includes the CfNR measurements of five best bands. Only when an SS reports its BS the CfNR
`measurements of Band AMC channels, its logical definition is made differently, as follows. If the number of
`bands is 48 (2048 FFT in 20 MHz), the two contiguous bands are paired and renumbered the same as a 24
`band system. Then, if the LSB of an SS MAC address is I, it only uses the odd-numbered bands. If not, it
`only uses the even-numbered bands. Hence, for example, the LSB of an SS MAC address is I, (4m+2,
`4m+3) bands are paired and the paired band is them-th band of the SS. Similarly, for an even-numbered SS,
`(4m, 4m+ l) bands are paired and the paired band is them-th band of the SS.
`
`268
`
`Copyright© 2004 IEEE. All rights reserved.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 7
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`AIR INTERFACE FOR FIXED BROADBAND WIRELESS ACCESS SYSTEMS
`
`IEEE Std 802.16-2004
`
`The BS acknowledges the trigger by allocating Band AMC subchannels. From the next frame when the SS
`sent the REP-RSP, the SS starts reporting the differential of CINR five selected bands (increment: l and
`decrement: 0 with a step of I dB) on its CQICH. If the BS does not allocate the Band AMC subchannels
`within the specified delay (CQICH Band AMC Transition Delay) in the UCO message, the SS reports the
`updated average CINR of the preamble for normal subchannel allocations.
`
`When the BS wants to trigger the transition to Band AMC mode or update the CINR reports, it sends the
`REP-REQ message (see 11.1 1 for the TLV encodings). When the SS receives the message, it replies with
`REP-RSP. When the BS receives the REP-RSP, it should synchronize the selection of bands reported and
`their CINR. Unless the BS allocates normal subchannels, the SS reports the differential increment compared
`to the most up-to-date report from the next CQI reporting frame.
`
`Copyright© 2004 IEEE. All rights reserved.
`
`269
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 8
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16-2004
`
`IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS-PART 16:
`
`270
`
`Copyright© 2004 IEEE. All rights reserved.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 9
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16-2004
`
`IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS-PART 16:
`
`assist new nodes to enter the network. The frequency can be reduced for the case of steady state
`network operation.
`
`Table 142-SC PHY synchronization field
`
`Syntax
`
`Size
`
`Notes
`
`PHY Synchronization FieldO {
`
`Network Configuration Type (NCT)
`
`4 bits
`
`Flag to indicate network
`configuration Type
`O= PMP,
`I = OM,
`2 = PtP,
`3 - 15 Reserved
`
`Frame Duration Code
`
`Frame Number
`
`if (NCT = DM) {
`
`FCH expected
`
`}
`
`}
`
`4 bits
`
`24 bits
`
`16 bits
`
`The number of frames before the
`Frame Preamble and FCH will be
`transmitted again.
`
`8.1.4.1.2.3 UL-MAP allocation start time definition
`
`The allocation start time is the effective start time of the uplink allocation defined by the UL-MAP in units
`ofrninislots. The start time is relative to the start of the frame in which the UL-MAP message is transmitted.
`
`8.1.4.1.2.4 Required DCD parameters
`
`The following parameters shall be included in the DCD message:
`
`-
`
`BS Transmit Power
`
`NOTE- to be used by SSs to validate radio link conditions
`
`PHY type
`FDD/TDD frame duration
`
`8.1.4.1.2.5 Downlink_Burst_Profile
`
`Each Downlink_Burst_Profile in the DCD message (6.3.2.3.1) shall include the following parameters:
`
`Modulation type
`FEC Code Type
`Last codeword length
`DIUC mandatory exit threshold
`DIUC minimum entry threshold
`Preamble Presence
`
`314
`
`Copyright© 2004 IEEE. All rights reserved.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 10
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`AIR INTERFACE FOR FIXED BROADBAND WIRELESS ACCESS SYSTEMS
`
`IEEE Std 802.16-2004
`
`If the FEC Code Type is 1, 2, or 3 (RS codes), the Downlink_Burst_Profile shall also include
`
`RS information bytes (K)
`RS parity bytes (R)
`
`If the FEC Code Type is 2, the Downlink_Burst_Profile shaJI also include
`
`BCC code type
`
`If the FEC Code Type is 4, the Downlink_Burst_Profile shall also include
`
`Block Turbo Code (BTC) row code type
`BTC column code type
`BTC interleaving type
`
`The mapping between Burst Profile and DIUC is given in Table 143.
`
`Table 143-Mapping of burst profile to DIUC
`
`Burst profile
`
`DIUC
`
`Downlink Burst Profile I
`
`Downlink Burst Profile 2
`
`Downlink Burst Profile 3
`
`Downlink Burst Profile 4
`
`Downlink Burst Profile 5
`
`Downlink Burst Profile 6
`
`Downlink Burst Profile 7
`
`Downlink Burst Profile 8
`
`Downlink Burst Profile 9
`
`Downlink Burst Profile I 0
`
`Downlink Burst Profile 11
`
`Downlink Burst Profile 12
`
`Downlink Burst Profile 13
`
`reserved
`
`Gap
`
`End ofDL-MAP
`
`0
`
`I
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`II
`
`12
`
`13
`
`14
`
`15
`
`The Downlink Burst Profile I (DIUC = 0) parameters defined in 8.1.4.4.5 shall be stored in the SS and shall
`not be included in the DCD message.
`
`The Gap Downlink Burst Profile ( DfUC = 14) indicates a silent interval in downlink transmission. It is
`well-known and shall not be defined in the DCD message.
`
`Copyright © 2004 IEEE. All rights reserved.
`
`315
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 11
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`

`

`IEEE Std 802.16-2004
`
`IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS-PART 16:
`
`The End of DL-MAP Burst Profile (DIUC = 15) indicates the first PS after the end of the downlink
`subframe. It is well known and shall not be included in the DCD message.
`
`Table 144 defines the fonnat of the Downlink_Burst_Profile, which is used in the DCD message (6.3.2.3.1).
`The DownJink_Burst_Profile is encoded with a Type of 1, an 8-bit length, and a 4-bit DlUC. The DlUC field
`is associated with the Downlink Burst Profile and Thresholds. The DIUC value is used in the DL-MAP
`message to specify the Burst Profile to be used for a specific downlink burst.
`
`Table 144-SC Downlink_Burst_Profile format
`
`Syntax
`
`Type=)
`
`Length
`
`reserved
`
`DIUC
`
`Size
`
`8 bits
`
`variable
`
`4 bits
`
`4 bits
`
`Notes
`
`Shall be set to zero
`
`TLV encoded information
`
`variable
`
`TLV Specific
`
`8.1.4.2 Downlink burst allocation
`
`The downlink data sections are used for transmitting data and control messages to the specific SSs. The data
`are always FEC coded and are transmitted at the current operating modulation of the individual SS. In the
`TOM portion, data shall be transmitted in order of decreasing burst profile robustness. In the case of a
`TOMA portion, the data are grouped into separately delineated bursts that need not be in robustness order
`(see 8.1.4. 1 ). The DL-MAP message contains a map stating at which PS the burst profile changes occur. In
`the case of TOMA, if the downlink data does not fill the entire downlink subframe, the transmitter is shut
`down. FEC codewords within a burst are arranged in a compact form aligned to bit-le vel boundaries. This
`implies that, while the first FEC codeword shall start on the first PS boundary, succeeding FEC codewords
`may start even within a modulation symbol or within a PS if the succeeding FEC codeword ended within a
`modulation symbol or within a PS. The exact alignment conditions depend on the burst profile parameters.
`
`In the case of shortening the last FEC block within a burst (optional, see 11.4.2), the DL-MAP provides an
`implicit indication.
`
`In general, the number of PSs i (which shall be an integer) allocated to a particular burst can be calculated
`from the DL-MAP, which indicates the starting position of each burst as well as the burst profi les. Let n
`denote the minimum number of PSs required for one FEC codeword of the given burst profile (note that n is
`not necessarily an integer). Then, i =kn + j + q, where k is the number of whole FEC codewords that fit in
`the burst, j (not necessarily an integer) is the number of PSs occupied by the largest possible shortened
`codeword, and q (0 ~ q < I) is the number of PSs occupied by pad bits inserted at the end of the burst to
`guarantee that i is an integer. In Fixed Codeword Operation (8.1.4.4.4.1 ), j is always 0. Recall that a
`codeword can end partway through a modulation symbol as well as partway through a PS . When this occurs,
`the next codeword shall start immediately, with no pad bits inserted. At the end of the burst (i.e., when there
`is no next codeword), then 4q symbols are added as padding (if required) to complete the PS allocated in the
`DL-MAP. The number of padding bits in these padding symbols is 4q times the modulation density, where
`the modulation density is 2 for QPSK, 4 for 16-QAM, and 6 for 64-QAM. Note that padding bits may be
`required with or w ithout shortening. Either k or j , but not both, may be zero. The number j implies some
`number of bits b. Assumingj is nonzero, it shall be large enough such that b is larger than the number of
`FEC bits, r, added by the FEC scheme for the burst. The number of bits (preferably an integral number of
`bytes) available for user data in the shortened FEC codeword is b-r. Any bits that may be left over from a
`
`316
`
`Copyright © 2004 IEEE. All rights reserved.
`
`HTC Corp., HTC America, Inc. - Ex. 1020, Page 12
`IPR2018-01555 and IPR2018-01581 (HTC and Apple v. INVT SPE)
`
`