2007-10-19
`
`
`
`1
`
`IEEE 802.16m-07/002r4
`
`Project
`
`IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
`
`Title
`
`IEEE 802.16m System Requirements
`
`Date
`Submitted
`
`Source(s)
`
`Re:
`
`Abstract
`
`Purpose
`
`Notice
`
`Release
`
`Patent
`Policy
`
`2007-10-19
`
`802.16m Requirements Editor:
`Mark Cudak
`Motorola
`Requirements for P802.16m-Advanced Air Interface
`
`mark.cudak@motorola.com
`
`
`This is the approved baseline TGm System Requirements. As directed by TGm, the document
`has been revised according to the comment resolution conducted by TGm in Session #51
`Updated high-level system requirements for the P802.16m draft
`
`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>.
`
`1
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 1 of 26
`
`

`

`2007-10-19
`
`
`IEEE 802.16m-07/002r4
`
`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
`
`Contents
`
`
`Overview......................................................................................................................................... 4
`1.0
`References....................................................................................................................................... 5
`2.0
`Definitions....................................................................................................................................... 6
`3.0
`Abbreviations and acronyms........................................................................................................... 7
`4.0
`General requirements...................................................................................................................... 8
`5.0
`Legacy support............................................................................................................................ 8
`5.1
`Complexity.................................................................................................................................. 8
`5.2
`Services....................................................................................................................................... 9
`5.3
`Operating frequencies ................................................................................................................. 9
`5.4
`Operating bandwidths ................................................................................................................. 9
`5.5
`Duplex schemes .......................................................................................................................... 9
`5.6
`Support of advanced antenna techniques.................................................................................. 10
`5.7
`Support for government mandates and public safety................................................................ 10
`5.8
`Functional requirements................................................................................................................ 11
`6.0
`Peak data rate ............................................................................................................................ 11
`6.1
`Latency...................................................................................................................................... 12
`6.2
`6.2.1
`Data latency ...................................................................................................................... 12
`6.2.2
`State transition latency...................................................................................................... 12
`6.2.3
`Handover interruption time............................................................................................... 13
`6.3
`QoS ........................................................................................................................................... 13
`6.4
`Radio resource management..................................................................................................... 13
`6.4.1
`Reporting........................................................................................................................... 13
`6.4.2
`Interference management.................................................................................................. 14
`6.5
`Security ..................................................................................................................................... 14
`6.6
`Handover................................................................................................................................... 14
`6.7
`Enhanced multicast broadcast service ...................................................................................... 14
`6.7.1 MBS channel reselection delay and interruption times .................................................... 15
`6.8
`Location based services (LBS) ................................................................................................. 15
`6.9
`Reduction of user overhead ...................................................................................................... 15
`6.10 System overhead ....................................................................................................................... 15
`6.11 Enhanced power saving ............................................................................................................ 15
`6.12 Multi-RAT operation................................................................................................................. 15
`7.0
`Performance requirements ............................................................................................................ 16
`7.1
`User throughput ........................................................................................................................ 16
`7.1.1
`Relative performance........................................................................................................ 16
`7.1.2
`Absolute performance....................................................................................................... 16
`7.2
`Sector throughput and VoIP capacity........................................................................................ 17
`7.2.1
`Relative sector throughput and VoIP capacity .................................................................. 17
`Absolute sector throughput and VoIP capacity ................................................................. 17
`7.2.2
`7.3 Mobility..................................................................................................................................... 18
`7.4
`Cell coverage ............................................................................................................................ 18
`7.5
`Enhanced multicast-broadcast service ...................................................................................... 19
`7.6
`Location-based services performance....................................................................................... 20
`
`2
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 2 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`Operational requirements.............................................................................................................. 20
`8.0
`Support for multi-hop relay ...................................................................................................... 20
`8.1
`Synchronization ........................................................................................................................ 20
`8.2
`Co-deployment with other networks......................................................................................... 20
`8.3
`8.3.1
`Co-deployment requirements............................................................................................ 20
`8.3.2
`Coexistence scenarios ....................................................................................................... 21
`8.4
`Support of self organizing mechanisms.................................................................................... 21
`Annex A: Usage models (informative).................................................................................................. 22
`A.1
`Service and application scenarios ............................................................................................. 22
`A.2 Deployment scenarios............................................................................................................... 23
`A.2.1
`Frequency reuse ................................................................................................................ 23
`A.2.2
`Deployment with multi-hop relay networks ..................................................................... 23
`A.2.3
`High mobility optimized scenario..................................................................................... 26
`A.2.4
`Provision for PAN/LAN/WAN collocation / coexistence................................................. 26
`A.2.5
`Very high data rates in smaller cells ................................................................................. 26
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`
`3
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 3 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`
`1.0 Overview
`
`The 802.16m amendment shall be developed in accordance with the P802.16 project authorization
`request (PAR), as approved on 6 December 2006 [1], and with the Five Criteria Statement in IEEE
`802.16-06/055r3 [2].
`According to the PAR, the standard shall be developed as an amendment to IEEE Std 802.16 [3][4]. The
`resulting standard shall fit within the following scope:
`This standard amends the IEEE 802.16 WirelessMAN-OFDMA specification to provide an
`advanced air interface for operation in licensed bands. It meets the cellular layer requirements
`of IMT-Advanced next generation mobile networks. This amendment provides continuing support
`for legacy WirelessMAN-OFDMA equipment.
`
`And the standard will address the following purpose:
`The purpose of this standard is to provide performance improvements necessary to support
`future advanced services and applications, such as those described by the ITU in Report ITU-R
`M.2072.
`
`
`The standard is intended to be a candidate for consideration in the IMT-Advanced evaluation process
`being conducted by the International Telecommunications Union– Radio Communications Sector (ITU-
`R) [5][6][7].
`This document represents the high-level system requirements for the 802.16m amendment. All content
`included in any draft of the 802.16m amendment shall meet these requirements. This document,
`however, shall be maintained and may evolve. These system requirements embodied herein are defined
`to ensure competitiveness of the evolved air interface with respect to other mobile broadband radio
`access technologies as well as to ensure support and satisfactory performance for emerging services and
`applications. These system requirements also call for significant gains and improvements relative to the
`preexisting IEEE 802.16 system that would justify the creation of the advanced air interface.
`To accelerate the completion and evaluation of the standard, to improve the clarity and reduce
`complexity of the standard specification, and to further facilitate the deployment of new systems, the
`number of optional features should be minimized.
`
`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
`
`4
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 4 of 26
`
`

`

`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
`
`IEEE 802.16m-07/002r4
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`2007-10-19
`
`
`2.0 References
`[1]
`IEEE 802.16m PAR, December 2006, http://standards.ieee.org/board/nes/projects/802-16m.pdf
`[2]
`IEEE 802.16 WG, “Five Criteria Statement for P802.16m PAR Proposal,” IEEE 802.16-06/55r3,
`November 2006, http://ieee802.org/16/docs/06/80216-06_055r3.pdf
`IEEE Std 802.16-2004: Part 16: IEEE Standard for Local and metropolitan area networks: Air
`Interface for Fixed Broadband Wireless Access Systems, June 2004
`IEEE Std. 802.16e-2005, IEEE Standard for Local and metropolitan area networks, Part 16: Air
`Interface for Fixed and Mobile Broadband Wireless Access Systems, Amendment 2: Physical
`and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed
`Bands, and IEEE Std. 802.16-2004/Cor1-2005, Corrigendum 1, December 2005
`Recommendation ITU-R M.1645: Framework and overall objectives of the future development
`of IMT-2000 and systems beyond IMT-2000, January 2003
`ITU-R Document 8F/TEMP/568: Guidelines for evaluation of radio interface technologies for
`IMT-Advanced, May 2007
`ITU-R Document 8F/TEMP/574: Requirements related to technical system performance for
`IMT-Advanced radio interface(s) [IMT.TECH] , May 2007
`[8] WiMAX Forum™ Mobile System Profile, Release 1.0 Approved Specification (Revision 1.4.0:
`2007-05-02), http://www.wimaxforum.org/technology/documents
`[9]
`FCC Docket no 94-102 this includes order numbers 96-264, 99-96, 99-245.
`[10] Communications Assistance for Law Enforcement Act of 1994 (CALEA), Pub. L. No. 103-414,
`108 Stat. 4279.
`[11] Communications Assistance for Law Enforcement Act and Broadband Access and Services First
`Report and Order and Further Notice of Proposed Rulemaking. ET Docket No. 04-295, RM-
`10865, 20 FCC Rcd 14989 (2005).
`IEEE 802.16 TGm, “IEEE 802.16m Evaluation Methodology Document,”
`IEEE 802.16m-07/037
`
`[7]
`
`[12]
`
`
`
`5
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 5 of 26
`
`

`

`2007-10-19
`
`
`3.0 Definitions
`
`Sector
`
`
`Cell
`
`
`Legacy MS
`
`
`Legacy BS
`
`
`IEEE 802.16m MS
`
`
`IEEE 802.16m BS
`
`
`H-FDD MS
`
`
`
`
`
`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
`
`
`WirelessMAN-OFDMA Reference System A system compliant with a subset of the WirelessMAN-
`OFDMA capabilities specified by IEEE 802.16-2004 and
`amended by IEEE 802.16e-2005 and IEEE
`802.16Cor2/D3, where the subset is defined by WiMAX
`Forum Mobile System Profile, Release 1.0 (Revision
`1.4.0: 2007-05-02) [8], excluding specific frequency
`ranges specified in the section 4.1.1.2 (Band Class Index)
`
`IEEE 802.16m-07/002r4
`
`A sector is a physical partition of a cell. Cells are
`typically partitioned into three or more sectors. One or
`more antennas per sector may be used at the BS to
`provide coverage to users within each sector.
`
`A collection of sectors (typically 3) belonging to the same
`BS
`
`A mobile station (MS) compliant with the WirelessMAN-
`OFDMA Reference System
`
`A BS compliant with the WirelessMAN-OFDMA
`Reference System
`
`An MS compliant with the IEEE 802.16 WirelessMAN-
`OFDMA specification specified by IEEE 802.16-2004
`and amended by IEEE 802.16e-2005 and IEEE 802.16m
`
`A BS compliant with the IEEE 802.16 WirelessMAN-
`OFDMA specification specified by IEEE 802.16-2004
`and amended by IEEE 802.16e-2005 and IEEE 802.16m
`
`A half-duplex FDD MS is defined as an FDD MS that is
`not required to transmit and receive simultaneously
`
`6
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 6 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`
`4.0 Abbreviations and acronyms
`
`BS
`CALEA
`CPE
`DL
`E-MBS
`FDD
`H-FDD
`IP
`ITU-R
`LAN
`LBS
`MAC
`MBS
`MBSFN
`MIH
`MIMO
`MS
`NCMS
`OFDMA
`PAN
`PAR
`PDU
`PHY
`QoS
`RAN
`RAT
`RRM
`RS
`TDD
`UL
`VoIP
`WAN
`
`
`
`
`base station
`Communications Assistance for Law Enforcement Act
`customer premises equipment
`downlink
`enhanced multicast broadcast service
`frequency division duplex
`half-duplex frequency division duplex
`Internet Protocol
`International Telecommunications Union – Radio Communications Sector
`local area network
`location based services
`medium access control layer
`multicast broadcast service
`multicast broadcast single frequency network
`media independent handover
`multiple input multiple output
`mobile station
`network control and management services
`orthogonal frequency division multiple access
`personal area network
`project authorization request
`protocol data unit
`physical layer
`quality of service
`radio access network
`radio access technology
`radio resource management
`relay station
`time division duplex
`uplink
`voice over IP
`wide area network
`
`1
`
`2
`3
`
`4
`5
`6
`
`7
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 7 of 26
`
`

`

`2007-10-19
`
`
`IEEE 802.16m-07/002r4
`
`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
`
`5.0 General requirements
`This section contains general requirements for IEEE 802.16m systems. These requirements are intended
`to address and supplement the requirements specified by the ITU-R for IMT-Advanced systems.
`IEEE802.16m shall meet the IMT-Advanced requirements.
`All enhancements included as part of IEEE 802.16m should promote the concept of continued evolution,
`allowing IEEE 802.16 to maintain competitive performance as technology advances beyond 802.16m.
`Some of the requirements in this document are separated for the mobile station (MS) and the base
`station (BS). Such requirements shall be construed as minimum performance requirements for the MSs
`and BSs.
`5.1 Legacy support
`IEEE 802.16m shall provide continuing support and interoperability for legacy WirelessMAN-OFDMA
`equipment, including MSs and BSs. Specifically, the features, functions and protocols enabled in IEEE
`802.16m shall support the features, functions and protocols employed by WirelessMAN-OFDMA
`legacy equipment. IEEE 802.16m shall provide the ability to disable legacy support.
`This continuing support shall be limited to the WirelessMAN-OFDMA Reference System which is
`defined as system compliant with a subset of the WirelessMAN OFDMA capabilities specified by IEEE
`802.16-2004 and amended by IEEE 802.16e-2005 and IEEE 802.16Cor2/D3, where the subset is
`defined by WiMAX Forum Mobile System Profile, Release 1.0 (Revision 1.4.0: 2007-05-02), excluding
`specific frequency ranges specified in the section 4.1.1.2 (Band Class Index).
`The following are backward compatibility requirements:
`• An IEEE 802.16m MS shall be able to operate with a legacy BS, at a level of performance
`equivalent to that of a legacy MS.
`• Systems based on IEEE 802.16m and the WirelessMAN-OFDMA Reference System shall be
`able to operate on the same RF carrier, with the same channel bandwidth; and should be able to
`operate on the same RF carrier with different channel bandwidths.
`• An IEEE 802.16m BS shall support a mix of IEEE 802.16m and legacy MSs when both are
`operating on the same RF carrier. The system performance with such a mix should improve with
`the fraction of IEEE 802.16m MSs attached to the BS.
`• An IEEE 802.16m BS shall support handover of a legacy MS to and from a legacy BS and to and
`from IEEE 802.16m BS, at a level of performance equivalent to handover between two legacy
`BSs.
`• An IEEE 802.16m BS shall be able to support a legacy MS while also supporting IEEE 802.16m
`MSs on the same RF carrier, at a level of performance equivalent to that a legacy BS provides to
`a legacy MS.
`5.2 Complexity
`IEEE 802.16m should minimize complexity of the architecture and protocols and avoid excessive
`system complexity. It should enable interoperability of access networks, support low cost devices and
`minimize total cost of ownership.
`
`8
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 8 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`IEEE 802.16m should only provide enhancements in areas where the WirelessMAN-OFDMA Reference
`System does not meet the requirements.
`The IEEE 802.16m system shall satisfy the performance requirements in Section 7.0. In addition, the
`complexity of MSs and BSs shall be minimized by adhering to the following:
`a) The functional and performance requirements shall be met with mandatory features only.
`b) Optional features shall be considered only if they provide significant functional and performance
`improvements over mandatory features.
`c) Support of multiple mandatory features which are functionally similar and/or have similar impact
`on performance shall be avoided.
`d) The number of states of protocols and procedures should be minimized.
`
`
`5.3 Services
`IEEE 802.16m should support legacy services more efficiently than the WirelessMAN-OFDMA
`Reference System as well as facilitate the introduction of new/emerging types of services.
`IEEE 802.16m and its services architecture shall be flexible in order to support services required for
`next generation mobile networks, such as those identified by Report ITU-R M.2072 and IMT-Advanced
`(IMT.SERV).
`IEEE 802.16m shall support different quality of service (QoS) levels for different services. IMT-
`Advanced QoS requirements shall be supported including end-to-end latency, throughput, and error
`performance.
`5.4 Operating frequencies
`IEEE 802.16m systems shall operate in RF frequencies less than 6 GHz and be deployable in licensed
`spectrum allocated to the mobile and fixed broadband services and shall be able to operate in
`frequencies identified for IMT-Advanced.
`An 802.16m compliant system shall meet the following coexistence requirements:
`a) IEEE 802.16m shall be capable of coexisting with other IMT-Advanced technologies.
`b) IEEE 802.16m shall be capable of coexisting with other IMT-2000 technologies.
`The IEEE 802.16m system should be able to use spectrum flexibly to provide TDD and FDD duplex
`modes. The IEEE 802.16m system should be able to aggregate multiple channels in more than one
`frequency band within the scope of a single MAC protocol instance.
`5.5 Operating bandwidths
`IEEE 802.16m shall support scalable bandwidths from 5 to 20 MHz. Other bandwidths shall be
`considered as necessary to meet operator and ITU-R requirements.
`5.6 Duplex schemes
`
`
`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
`
`9
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 9 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`IEEE 802.16m shall support both Time Division Duplex (TDD) and Frequency Division Duplex (FDD)
`operational modes. The FDD mode shall support both full-duplex and half-duplex MS operation.
`Specifically, a half-duplex FDD (H-FDD) MS is defined as an FDD MS that is not required to transmit
`and receive simultaneously.
`A BS supporting FDD mode shall be able to simultaneously support half duplex and full duplex
`terminals operating on the same RF carrier. The MS supporting FDD mode shall use either H-FDD or
`FDD.
`IEEE 802.16m shall support both unpaired and paired frequency allocations, with fixed duplexing
`frequency separations when operating in FDD mode.
`System performance in the desired bandwidths specified in Section 5.5 should be optimized for both
`TDD and FDD independently while retaining as much commonality as possible.
`In TDD mode, the DL/UL ratio should be adjustable. In the extreme, the IEEE 802.16m system should
`be capable of supporting downlink-only configurations on a given carrier.
`In FDD mode, the UL and DL channel bandwidths may be different and should be configurable (e.g.
`10MHz downlink, 5MHz uplink).
`5.7 Support of advanced antenna techniques
`The IEEE 802.16m standard shall define minimum antenna requirements for the BS and MS. For the BS,
`a minimum of two transmit and two receive antennas shall be supported. For the MS, a minimum of one
`transmit and two received antennas shall be supported. This minimum is consistent with a 2x2 downlink
`configuration and a 1x2 uplink configuration.
`IEEE 802.16m shall support MIMO, beamforming operation or other advanced antenna techniques.
`IEEE 802.16m shall further support single-user and multi-user MIMO techniques.
`5.8 Support for government mandates and public safety
`IEEE 802.16m shall be able to support public safety first responders, military and emergency services
`such as call-prioritization, pre-emption, push-to-talk.
`The IEEE 802.16m system shall support regional regulatory requirements, such as Emergency Services
`(E9-1-1) [9] and the Communications Assistance for Law Enforcement Act (CALEA) [10] [11].
`
`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
`
`10
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 10 of 26
`
`

`

`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
`
`2007-10-19
`
`6.0 Functional requirements
`This section contains system level functional requirements targeting higher peak rates, lower latency,
`lower system overhead as well as PHY/MAC features enabling improved service security, QoS and
`radio resource management (RRM).
`The functional requirements described in this document shall be met with a system comprised solely of
`IEEE 802.16m compliant MSs and BSs.
`6.1 Peak data rate
`This section defines the peak data rate achievable between a BS and an MS under ideal conditions.
`IEEE 802.16m shall support the peak, expressed as a normalized peak rate (i.e. absolute maximum
`supported data rate divided by the occupied channel bandwidth) as specified in Table 1.
`Table 1–Normalized peak data rate
`MIMO
`Configuration
`
`Requirement
`Type
`
`Link direction
`
`IEEE 802.16m-07/002r4
`
`Normalized peak
`rate
`(bps/Hz)
`8.0
`2.8
`15.0
`5.6
`
`Baseline
`
`Target
`
`Downlink
`Uplink
`Downlink
`Uplink
`
`2x2
`1x2
`4x4
`2x4
`
`
`Notes applicable to Table 1:
`a) The baseline requirement denotes the minimum peak data rate achievable between a BS and an
`MS equipped with the minimum supported antenna configuration defined in Section 5.7.
`b) The target requirement denotes the minimum peak data rate achievable between a BS and an MS
`equipped with a higher order antenna configuration, as specified in Table 1, that exceeds the
`minimum MS antenna configuration.
`c) Other MIMO antenna configurations beyond those of Table 1 can be used. For example, the
`extended uplink requirement for the 2x4 configuration would apply to an uplink 2x2
`configuration etc.
`d) The specified requirements of normalized peak rates are not distinguished by duplex mode.
`Rather, 100% of available radio resources are assumed – for the purposes of computing Table 1–
`allocable to downlink and uplink respectively regardless of duplexing mode. For example, for
`TDD, when assessing downlink performance, all available radio resources are assigned for
`downlink transmission.
`e) Table 1 accounts for layer 1 overhead due to provisioning of radio resources for essential
`functions such as pilots, cyclic-prefix, guard bands, guard intervals and synchronization channels
`(preamble).
`f) The specified minimum supported normalized peak rates are applicable to all bandwidths in
`Section 5.5.
`
`
`
`11
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 11 of 26
`
`

`

`1
`2
`3
`4
`5
`
`6
`7
`8
`9
`
`10
`11
`12
`13
`14
`
`15
`16
`
`17
`18
`19
`20
`21
`22
`23
`
`2007-10-19
`
`6.2 Latency
`Latency should be further reduced as compared to the WirelessMAN-OFDMA Reference System for all
`aspects of the system including the air link, state transition delay, access delay, and handover.
`The following latency requirements shall be met by the system, under unloaded conditions.
`
`
`IEEE 802.16m-07/002r4
`
`6.2.1 Data latency
`The data latency is defined in terms of the one-way transit time between a packet being available at the
`IP layer (Tx reference point) in either the MS/ Radio Access Network and the availability of this packet
`at IP layer (Rx reference point) in the Radio Access Network / MS.
`
`
`
`
`Figure 1-Illustration of reference points for the maximum data latency
`
`
`
`Table 2–Maximum data latency
`Max. latency
`Link direction
`(ms)
`10
`10
`
`Downlink (BS->MS)
`Uplink (MS->BS)
`
`
`
`6.2.2 State transition latency
`Performance requirements for state transition delay define the transition from IDLE_STATE to
`ACTIVE_STATE.
`IDLE_STATE to ACTIVE_STATE transition latency is defined as the time it takes for a device to go
`from an idle state (fully authenticated/registered and monitoring the control channel) to when it begins
`exchanging data with the network on a traffic channel measured from the paging indication (i.e. not
`including the paging period).
`
`12
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 12 of 26
`
`

`

`2007-10-19
`
`
`IEEE 802.16m-07/002r4
`
`Table 3–Maximum state transition latency
`Max. latency
`Metric
`(ms)
`100 ms
`
`IDLE_STATE to
`ACTIVE_STATE
`
`
`
`
`6.2.3 Handover interruption time
`This section addresses handover interruption time requirements applicable to handovers between
`802.16m BSs for intra- and inter-frequency handover.
`The maximum handover interruption times specified in Table 4 apply to handover of IEEE 802.16m MS
`between IEEE 802.16m BSs operating in the absence of legacy MSs under normal operating conditions.
`The handover interruption time represents the time duration that an MS cannot receive service from any
`BS during a handover.
`
`Table 4–Maximum handover interruption
`Max. interruption time
`Handover type
`(ms)
`30
`100
`
`Intra-frequency
`Inter-frequency
`
`
`6.3 QoS
`IEEE 802.16m shall support QoS classes, enabling an optimal matching of service, application and
`protocol requirements (including higher layer signaling) to radio access network (RAN) resources and
`radio characteristics. This includes enabling new applications such as interactive gaming [5].
`IEEE 802.16m shall provide support for preserving QoS during handover with other RATs when it is
`feasible.
`
`6.4 Radio resource management
`IEEE 802.16m shall enable the advanced RRM for efficient utilization of radio resources. This may be
`achieved by appropriate measurement/reporting, interference management and flexible resource
`allocation mechanisms.
`
`6.4.1 Reporting
`IEEE 802.16m shall enable advanced RRM by enabling the collection of reliable statistics over different
`timescales, including system (e.g. dropped call statistics, BS loading condition, channel occupancy),
`user (e.g. terminal capabilities, mobility statistics, and battery life), flow, packet, etc.
`
`
`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
`
`13
`
`Intel Corporation Ex. 1007
`Intel Corp v. UNM Rainforest Innovations - IPR2020-01576
`Page 13 of 26
`
`

`

`IEEE 802.16m-07/002r4
`
`2007-10-19
`
`6.4.2 Interference management
`IEEE 802.16m shall support interference mitigation schemes.
`IEEE 802.16m shall support flexible frequency re-use schemes.
`
`6.5 Security
`IEEE 802.16m shall include a security function which provides the necessary means to achieve:
`• protection of the integrity of the system (e.g. system access, stability and availability)
`• protection and confidentiality of user-generated traffic and