Standard

IEEE 802.16-2009

Revised

Note: Latest version: IEEE 802.16-2017

Existing or new amendments and versions must be purchased separately.

Language
Services

Abstract

Revision Standard - Superseded. This standard specifies the air interface, including the medium access control layer (MAC) and physical layer (PHY), of combined fixed and mobile point-to-multipoint broadband wireless access (BWA) systems providing multiple services. The MAC is structured to support multiple physical layer (PHY) specifications, each suited to a particular operational environment. The standard enables rapid worldwide deployment of innovative, cost effective, and interoperable multivendor broadband wireless access products, facilitates competition in broadband access by providing alternatives to wireline broadband access, encourages consistent worldwide spectrum allocations and accelerates the commercialization of broadband wireless access systems. The standard is a revision of IEEE Std 802.16-2004, and consolidates material from IEEE 802.16eTM-2005, IEEE 802.16-2004/Cor1-2005, IEEE 802.16fTM-2005 and IEEE 802.16gTM-2007, along with additional maintenance items and enhancements to the management information base specifications. This revision supersedes and makes obsolete IEEE Std 802.16-2004 and all of its subsequent amendments and corrigenda.

Products specifications

  • Standard from IEEE
  • Published:
  • Document type: IS
  • Pages
  • Publisher: IEEE
  • Distributor: IEEE
  • ICS: 35.100.10
  • ICS: 35.100.20
  • ICS: 35.110
  • National Committee: IEEE Computer Society / LAN/MAN Standards Committee

Product Relations

  • Referred by: IEEE 8802-22-2015
  • Revised by: IEEE 802.16-2012
  • Referred by: IEEE 802.22-2011
  • Refers: IEEE 802.21-2008
  • Refers: IEEE 802.3-2008
  • Refers: IEEE 802.1Q-2005
  • Revises: IEEE 802.16-2004
  • Refers: IEEE 802.1D-2004
  • Refers: IEEE 802.16.2-2004
  • Refers: IEEE 802-2001
  • Refers: IEEE 802.2-1989
  • Refers: NIST Special Publication 800-38A-Recommendation for Block Cipher Modes of Operation—Methods and Techniques.
  • Refers: IETF RFC 3759-“RObust Header Compression (ROHC): Terminology and Channel Mapping Examples,” L-E Jonsson, April 2004. (http://www.ietf.org/rfc/rfc3759.txt)
  • Refers: IETF RFC 3584-“Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Net-work Management Framework,” August 2003.
  • Refers: IETF RFC 791-“Internet Protocol,” J. Postel, September 1981.8IETF RFC 868, “Time Protocol,” J. Postel, K. Harrenstien, May 1983
  • Refers: IETF RFC 2349-“TFTP Timeout Interval and Transfer Size Options,” G. Malkin and A. Harkin, May 1998
  • Refers: WiMAX Forum Mobile System Profile Release 1.5-FDD Specific Part
  • Refers: IETF RFC 1123-“Requirements for Internet Hosts—Application and Support,” R. Braden, October 1989.IETF RFC 1157, “A Simple Network Management Protocol (SNMP),” M. Schoffstall, M. Fedor, J. Davin, and J. Case, May 1990
  • Refers: ATM Forum Specification af-sig-0061.000-ATM User-Network Interface (UNI) Signalling Specification, Version 4.0, July 1996
  • Refers: IETF RFC 1213- “Management Information Base for Network Management of TCP/IP-based internets: MIB-II,” March 1991.IETF RFC 1902, “Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2),” January 1996
  • Refers: IETF RFC 3748-“Extensible Authentication Protocol (EAP),” B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson, H. Levkowetz, June 2004. (http://www.ietf.org/rfc/rfc3748.txt).
  • Refers: IETF RFC 3415- “View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP),” December 2002.
  • Refers: IETF RFC 3545- “Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reorder-ing,” T. Koren, S. Casner, J. Geevarghese, B. Thompson, P. Ruddy, July 2003. (http://www.ietf.org/rfc/rfc3545.txt)
  • Refers: IETF RFC3825-“DHCP for Coordinate-based Location Configuration Information,” July 2004.
  • Refers: IETF RFC 2462-“IPv6 Stateless Address Autoconfiguration,” S. Thomson, T. Narten, December 1998. (http://www.ietf.org/rfc/rfc2462.txt)
  • Refers: IETF RFC 2474-“Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers,” K. Nichols, S. Blake, F. Baker, D. Black, December 1998
  • Refers: IETF RFC 2865-“Remote Authentication Dial In User Service (RADIUS)” C. Rigney, et al, June 2000. (http://www.ietf.org/rfc/rfc2865.txt)
  • Refers: PKCS #1 v2.0-RSA Cryptography Standard, RSA Laboratories, October 1998 <http://www.rsasecu-rity.com/rsalabs/pkcs/pkcs-1>.
  • Refers: Internet Assigned Numbers Authority (IANA), “Protocol Numbers,”-<http://www.iana.org/assignments/protocol-numbers>, June 2001.
  • Refers: IETF RFC 2104-“HMAC: Keyed-Hashing for Message Authentication,” H. Krawczyk, M. Bellare, R. Canetti, February 1997
  • Refers: FIPS 186-2-Digital Signature Standard (DSS), January 2000. FIPS 197, Advanced Encryption Standard (AES)
  • Refers: IETF RFC 3315-“Dynamic Host Configuration Protocol for IPv6 (DHCPv6),” R. Droms, et al, July 2003. (http://www.ietf.org/rfc/rfc3315.txt)
  • Refers: IETF RFC 1042-“A Standard for the Transmission of IP Datagrams over IEEE 802 Networks,” J. Postel, J. Reynolds, February 1988.
  • Refers: FIPS 46-3, Data Encryption Standard (DES)-October 1999
  • Refers: WiMAX Forum Mobile System Profile Release 1.5-Common Part
  • Refers: IETF RFC 3410-“Introduction and Applicability Statements for Internet-Standard Management Frame-work,” December 2002.
  • Refers: IETF RFC 2758-"Definitions of Managed Objects for Service Level Agreements Performance Monitoring,” K. White, February 2000
  • Refers: IETF RFC 3414-User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3),” December 2002.
  • Refers: ATM Forum Specification af-uni-0010.002-ATM User-Network Interface Specification, Version 3.1, September 1994
  • Refers: IETF RFC 3412-“Message Processing and Dispatching for the Simple Network Management Protocol (SNMP),” December 2002.
  • Refers: FIPS 74-Guidelines for Implementing and Using the NBS Data Encryption Standard, April 1981
  • Refers: IETF RFC 3775-“Mobility Support in IPv6,” D. Johnson, C. Perkins, J. Arkko, June 2004. (http://www.ietf.org/rfc/rfc3775.txt)
  • Refers: IETF RFC 2789-“Mail Monitoring MIB,” N. Freed, S. Kille, March 2000. (http://www.ietf.org/rfc/rfc2789.txt)
  • Refers: WiMAX Forum® Mobile System Profile Release 1-IMT-2000 Edition.
  • Refers: IETF RFC 3280-“Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” R. Housley, W. Polk, W. Ford, D. Solo, April 2002. (http://www.ietf.org/rfc/rfc3280.txt)
  • Refers: ETSI EN 301 213-3-Fixed Radio Systems; Point-to-multipoint equipment; Point-to-multipoint digital radio systems in frequency bands in the range 24,25 GHz to 29,5 GHz using different access methods; Part 3: Time Division Multiple Access (TDMA) methods, Vers 1.3.1, Sept 2001
  • Refers: IETF RFC 3418-“Management Information Base (MIB) for the Simple Network Management Protocol (SNMP),” December 2002.
  • Refers: IETF RFC 3413-“Simple Network Management Protocol (SNMP) Applications,” December 2002.
  • Refers: IETF RFC 2131- “Dynamic Host Configuration Protocol,” R. Droms, March 1997.IETF RFC 2132, “DHCP Options and BOOTP Vendor Extensions,” S. Alexander, and R. Droms, March 1997
  • Refers: IETF RFC 2460-“Internet Protocol, Version 6 (IPv6) Specification,” S. Deering, R. Hinden, December 1998
  • Refers: IETF RFC 2373-“IP Version 6 Addressing Architecture,” R. Hinden, S. Deering, July 1998. (http://www.ietf.org/rfc/rfc2373.txt)
  • Refers: IETF RFC 3012-“Mobile IPv4 Challenge/Response Extensions,” C. Perkins, P. Calhoun, November 2000. (http://www.ietf.org/rfc/rfc3012.txt)
  • Refers: IETF RFC 3411- “An Architecture for Describing Simple Network Management Protocol (SNMP) Manage-ment Frameworks,” December 2002.
  • Refers: IETF RFC 4291-“IP Version 6 Addressing Architecture,” R. Hinden, S. Deering, February 2006.
  • Refers: ITU-T Recommendation X.690-Information Technology—ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER), and Distinguished Encoding Rules (DER), December 1997.
  • Refers: ITU-T Recommendation X.25-Interface between Data Terminal Equipment (DTE) and Data Circuit-termi-nating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit, October 1996.
  • Refers: IETF RFC 2576-“Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Net-work Management Framework,” March 2000
  • Refers: IETF RFC 2459-“Internet X.509 Public Key Infrastructure Certificate and CRL Profile,” R. Housley, W. Ford, W. Polk, D. Solo, January 1999
  • Refers: IETF RFC 2578-“Structure of Management Information Version 2 (SMIv2),” April 1999
  • Refers: NIST Special Publication 800-38B-Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication.
  • Refers: IETF RFC 1903-“Textual Convention for Version 2 of the Simple Network Management Protocol (SNMPv2),” January 1996
  • Refers: FIPS 81-DES Modes of Operation, December 1980.FIPS 180-1, Secure Hash Standard (SHS), April 1995.
  • Refers: IETF RFC 3095-“RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed,” C. Bormann, et al, July 2001. (http://www.ietf.org/rfc/rfc3095.txt)
  • Refers: IETF RFC 3394-“Advanced Encryption Standard (AES) Key Wrap Algorithm,” J. Schaad, R. Housley, Sep-tember 2002. (http://www.ietf.org/rfc/rfc3394.txt)
  • Refers: ISO/IEC 8825-Information technology—Open Systems Interconnection—Specification of the Basic Encod-ing Rules for Abstract Syntax Notation One (ASN.1), May 1999.
  • Refers: IETF RFC 2863-“The Interfaces Group MIB,” June, 2000
  • Refers: WiMAX Forum Mobile System Profile Release 1.5-TDD Specific Part.