Draft Amendment to IEEE Standard for Local and Metropolitan Area Networks - Part 16: Management Information Base Extensions

Size: px

Start display at page:

Download "Draft Amendment to IEEE Standard for Local and Metropolitan Area Networks - Part 16: Management Information Base Extensions"

Myron Rose
5 years ago
Views:

1 00-- IEEE 0.i-0/00r, November IEEE 0.i-0/00r, November 00 This a NetMan Task Group P0.i Baseline Document. Draft Amendment to IEEE Standard for Local and Metropolitan Area Networks - Part : Management Information Base Extensions Sponsor LAN MAN Standards Committee of the IEEE Computer Society and the IEEE Microwave Theory and Techniques Society Abstract: This document provides updates to IEEE Std 0. s MIB for the MAC, PHY and associated management procedures in order to accommodate recent extensions to the standard. The project will use protocol-neutral methodologies for network management to develop resource models and related solution sets for the management of devices in a multi-vendor 0. network. Keywords: fixed broadband wireless access network, mobile broadband wireless access network, metropolitan area network, microwave, millimeter wave, WirelessMAN standards, WMAN MIB Copyright 00 by the Institute of Electrical and Electronics Engineers, Inc. Three Park Avenue New York, NY 0-, USA All rights reserved. This document is an unapproved draft of a proposed IEEE Standard. As such, this document is subject to change. USE AT YOUR OWN RISK! Because this is an unapproved draft, this document must not be utilized for any conformance/ compliance purposes. Permission is hereby granted for IEEE Standards Committee participants toreproduce this document for purposes of IEEE standardization activities only. Prior to submitting this document toanother standards development organization for standardization activities, permission must first be obtained from themanager, Standards Licensing and Contracts, IEEE Standards Activities Department. Other entities seeking permission to reproduce this document, in whole or in part, must obtain permission from the Manager, Standards Licensing andcontracts, IEEE Standard Activities Department. IEEE Standards Activities Department Standards Licensing and Contracts Hoes Lane, P.O. Box Piscataway, NJ 0-, USA Copyright 00 IEEE. All rights reserved. i

2 IEEE 0.i-0/00r, November IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document. The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied AS IS. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board Hoes Lane P.O. Box Piscataway, NJ 0- USA Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, Rosewood Drive, Danvers, MA 0 USA; + 0. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. ii Copyright 00 IEEE. All rights reserved..

3 00-- IEEE 0.i-0/00r, November 00 Introduction (This introduction is not part of IEEE Draft P0.i, Draft Amendment to IEEE Standard for Local and Metropolitan Area Networks - Part : Management Information Base Extensions.) Participants This document was developed by the IEEE 0. Working Group on Broadband Wireless Access, which develops the WirelessMAN Standard for Wireless Metropolitan Area Networks. IEEE 0. Working Group Officers Roger B. Marks, Chair Jose Puthenkulam, Vice Chair Peiying Zhu, Secretary Primary development was carried out by the Working Group's Network Management Task Group Officers. Phillip Barber, Chair Changhoi Koo, Vice Chair Itzik Kitroser, Vice Chair Joey Chou, 0.f Chief Technical Editor Copyright 00 IEEE. All rights reserved. iii

4 IEEE 0.i-0/00r, November The following members of the IEEE 0. Working Group on Broadband Wireless Access participated in the Working Group Letter Ballot in which the draft of this standard was prepared and finalized for IEEE Ballot: [to be determined] The following participated as non-members in the Working Group Letter Ballot: [to be determined] The following members of the IEEE Balloting Committee voted on this standard, whether voting for approval or disapproval, or abstaining. [to be determined] The following persons, who were not members of the IEEE Balloting Committee, participated (without voting) in the IEEE Sponsor Ballot in which the draft of this standard was approved: [to be determined] When the IEEE-SA Standards Board approved this standard on [date], it had the following membership: [to be determined] Also included is the following nonvoting IEEE-SA Standards Board liaison: iv Copyright 00 IEEE. All rights reserved..

7 00-- IEEE 0.i-0/00r, November Contents. Overview.... Scope.... Purpose.... Reference Models..... Management Reference Models.... References.... Abbreviations and Acronyms.... Configuration.... ASN. Management Information Base..... SNMP..... Relationship with interface MIB MIB- integration Usage of MIB-II tables..... Events and traps..... MIB Modules WMAN-IF-MIB module WMAN-DEV-MIB module WMAN-IF-MIB module WMAN-IFM-MIB module MIB Modulesstructure for SNMP.... Structure of MIB modules..... wmanifmib..... wmandevmib..... wmanifmib wmanifbsobjects wmanifssobjects wmanifcommonobjects..... wmanifmmib wmanifmbsobjects.... ASN. Definitions of MIB Modules..... wmanifmib..... wmandevmib..... wmanifmib..... wmanifmmib... Annex E Annex F. Proposal for Adding Mobility Handover and Paging group MIBs.... Introduction.... Proposed Text Introduction.... wmanifbsobjects..... wmanifbsmobility wmanifbshandoverconfiguration wmanifbspaginggrouptable.... ASN. Definitions of 0. MIB for SNMP... Copyright 00 IEEE. All rights reserved. vii

9 00-- IEEE 0.i-0/00r, November List of Figures Figure Mobile BWA Network Management Reference Model... Figure Mobile BWA Network Management Architecture - Context A... Figure Mobile BWA Network Management Architecture - Context B... Figure SS / MS Network Entry... Figure wmanifmib structure... Figure wmanifbspacketcs structure... Figure wmanifbscps structure... Figure wmanifbspkmobjects structure... Figure wmanifbsnotification structure... Figure wmanifbsphy structure... Figure wmanifsscps structure... 0 Figure wmanifsspkmobjects structure... Figure wmanifssnotification structure... Figure wmanifssphy structure... Figure wmanifcmnpacketcs structure... Figure wmanifcmncps structure... Figure wmanifcmnpkmobjects structure... Figure wmanifmmib structure... Figure wmanifmbscm structure... Figure 0 wmanifmbspm structure... Copyright 00 IEEE. All rights reserved. ix

11 00-- IEEE 0.i-0/00r, November List of Tables Table Example of the Usage of iftable objects for base station... Table Example of the Usage of iftable objects for subscriber station... Table List of ASN. MIB Modules... Copyright 00 IEEE. All rights reserved. xi

13 00-- IEEE 0.i-0/00r, November Baseline document for Draft Amendment to IEEE Standard forlocal and metropolitan area networks Part : Management Information Base Extensions NOTE-The editing instructions contained in this amendment define how to merge the material contained herein into the existing base standard IEEE Std The editing instructions are shown bold italic. Four editing instructions are used: change, delete, insert, and replace. Change is used to make small corrections in existing text or tables. The editing instruction specifies the location of the change and describes what is being changed by using strike through (to remove old material) and underscore (to add new material). Delete removes existing material. Insert adds new material without disturbing the existing material. Insertions may require renumbering. If so, renumbering instructions are given in the editing instruction. Replace is used to make large changes in existing text, subclauses, tables, or figures by removing existing material and replacing it with new material. Editorial notes will not be carried over into future editions because the changes will be incorporated into the base standard.. Overview. Scope This document provides mobility enhancements to the IEEE Std 0. Management Information Base for the medium access control layer, physical layer, and associated management procedures. It uses protocolneutral methodologies for network management to specify resource models and related solution sets for the management of devices in a multivendor 0. mobile network.. Purpose This amendment provides a definition of managed objects to enhance the standards-based management of 0. devices.. Reference Models Copyright 00 IEEE. All rights reserved.

14 IEEE 0.i-0/00r, November Management Reference Models Figure illustrates the Management Reference Model (see also GPP TS.). It shows the Operation System interfacing with other systems. A number of management interfaces are identified in Figure, namely:. Between the Network Elements (NEs) and the Element Manager (EM). Between the Element Manager (EM) and the Network Manager (NM). Between the Network Managers and the Enterprise Systems. Between Network Managers (NMs). Between Enterprise Systems & Network Managers of different Organisations. Between Network Elements (NEs). The resource model defined within this section focuses primarily on serving management interface "" and to a lesser extent on management interface "" from the above list. Figure Mobile BWA Network Management Reference Model Figure and Figure identify system contexts of the Management Interface "" in terms of its implementation, called IRPAgent, and the user of the IRPAgent, called IRPManager (for a definition of IRPManager and IRPAgent see GPP TS.). An NE can be managed either via System Context A (IRP Agent is a standalone system) or Via System Context B (element management function and IRP Agent embedded within the NE). The criterion for choosing System Context A or B to manage a particular NE is implementation dependent. An IRPAgent shall support one of the two System Contexts. Figure Mobile BWA Network Management Architecture - Context A Figure Mobile BWA Network Management Architecture - Context B Copyright 00 IEEE. All rights reserved..

15 00-- IEEE 0.i-0/00r, November References This standard shall be used in conjunction with the following publications. When the following specifications are superseded by an approved revision, the revision shall apply. [Replace the following references] IETF RFC0, "Structure of Management Information for version of the Simple Network Management Protocol (SNMPv)", January IETF RFC "Structure of Management Information Version (SMIv) " April IETF RFC0, "Textual Convention for Version of the Simple Network Management Protocol (SNMPv)", January IETF RFC "Textual Conventions for SMIv " April IETF RFC, Coexistence between Version, Version, and Version of the Internet-standard Network Management Framework, March 000 IETF RFC "TCoexistence between Version, Version, and Version of the Internet-standard Network Management Framework " August 00 [Insert the following new references] GPP TS., "Principles and High Level Requirements"; Release, archive/_series GPP TS., "Integration Reference Point (IRP) Concept and Definitions", Release, GPP TS., "Integration Reference Point (IRP) Information Service (IS) Template", Release, GPP TS., "Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) Repertoire", Release, GPP TS., "Configuration Management (CM); Generic Network Resources Integration Reference Point (IRP); Network Resource Model (NRM)"; Release, GPP S.S00-00-C, "OAM&P for cdma000 (GPP Generic NRM IRP)" Public_html/specs/index.cfm GPP TS., "Telecommunication management; Architecture", Release, Copyright 00 IEEE. All rights reserved.

16 00-- IEEE 0.i-0/00r, November specs/archive/_series. Abbreviations and Acronyms [Insert a new definition in this sunclause] RDN Relative Distinguished Name RP Integration Reference Point IS Information Service NRM Network Resource Model Copyright 00 IEEE. All rights reserved.

18 00-- IEEE 0.i-0/00r, November Configuration [Change subclause. as follows:]. ASN. Management Information Base The management information base for BS and SS is defined as two ASN. MIB modules: wmanifmib and wmandevmib. The implementation of both ASN. MIB modules is mandatory for all BSs. The implementation of bothasn. MIB modules is mandatory for SSs that are managed using SNMP protocol. The specific requirements for implementation of individual MIB modules are defined in section... The specific requirements for implementation of individual MIB objects in each MIB module are defined in conformance statements of the MIB modules. The wmanifmib MIB module (interface MIB) defines management objects relevant to 0. broadband wireless interface as defined in this standard. The wmandevmib MIB module (device MIB) defines management objects relevant to the device implementing 0. interface. The objects of this MIB module may refer explicitly to terms defined in the standard (e.g. configuration file encodings) but mainly provides the mandatory support required to implement, manage and test the equipment implementing 0. interface. This document also provides an informative Annex -- Annex D to define vendor specific managed objects, such as temperature, fan and power alarms, for IEEE based Base Station... SNMP SNMP is a protocol to access the managed objects in BS and SS. The support of SNMP is optional for SS. The support of SNMP in this standard is compliant to SNMPv, but is backward compatible to SNMPv through appropriate translation. The SNMP agent support for SNMPv is optional. In case of an agent that implements SNMPv, it is required to implement at least all the mandatory groups of the standard MIBs required for SNMPv: RFC, RFC, RFC, RFC, RFC and RFC as well as the MIB defining coexistence between SNMPv, v and v in RFC. The SNMPv framework may be considered as a mechanism to flexibly control access to this MIB module, and mitigate security vulnerbility.. SNMP agent shall support RFC... Relationship with interface MIB This subclause describes the integration of wmanifmib with MIB-II under Interface Group MIB defined in IETF RFC. Copyright 00 IEEE. All rights reserved..

19 00-- IEEE 0.i-0/00r, November This subclause describes the integration with MIB-II under Interface Group MIB defined in IETF RFC, as wmanifmib will need to be integrated in the MIB tree. It describes where wmanifmib is located in the MIB-II subtree, and how it can be accessed by NMS.... MIB- integration The Internet Assigned Number Authority (IANA) has assigned the following iftypes: to point to multipoint broadband wireless access. IANAifType ::= TEXTUAL-CONVENTION SYNTAX INTEGER { propbwapmp () -- prop broadband wireless access point to multipoint propbwapmp (), -- prop broadband wireless access point to multipoint -- use of this iftype for IEEE 0. WMAN -- interface as per Std 0.f is deprecated, -- and iftype ieee0wman should be used -- instead. ieee0wman (), -- IEEE 0. WMAN interface } Wireless MAN interface table is located under transmission subtree, as follows. wmanifmib ::= {transmission }-- WMAN interface table The amendment 0.f-00 defined interface type for point-to-multipoint broadband wireless access interfaces as "propbwapmp ()". This interface type is now deprecated. All new implementations of SNMP agents should use the newly allocated iftype number ieee0wman (). For backwards compatibility purposed SNMP managers shall accept this deprecated interface type.... Usage of MIB-II tables "Interfaces" group of MIB-II, in RFC, has been designed to manage various sub-layers (e.g. MAC and PHY) beneath the internetwork-layer for numerous media-specific interfaces. The implementation of iftable in SNMP managed BS and SS is mandatory. The implementation of the iftable for BS must create one row for each BS sector. Each BS sector may support different MAC versions of IEEE 0. standard (e.g. IEEE 0.-00, IEEE 0.e-00). The following recommendations must be applied to each row defining BS sector: ifindex value is implementation specific iftype must be set to propbwapmp (value of as defined in...) ieee0wman value of as defined in subclause...) ifspeed must be null set to 0 ifphysaddress must be set to the MAC Address of the BS sector All other columnar objects must be initialized as specified in RFC. iftable ifindex iftype (IANA) ifspeed ifphysaddress ifadminstatus ifoperstatus BS Sector ieee0wman propbwapmp BS Sector ieee0wman propbwapmp Null 0 Null 0 MAC address of BS sector MAC address of BS sector Administration Status Administration Status Operational Status Operational Status Copyright 00 IEEE. All rights reserved.

20 00-- IEEE 0.i-0/00r, November iftable ifindex iftype (IANA) ifspeed ifphysaddress ifadminstatus ifoperstatus BS Sector ieee0wman propbwapmp Table Example of the Usage of iftable objects for base station Table shows an example of the usage of iftable for BS that supports multiple sectors. Each sector may support one of the following MAC / PHY interfaces: IEEE 0.-00, OFDM IEEE 0.-00, OFDMA 0 IEEE 0.e, OFDMA IEEE 0.e, OFDMA IEEE 0.e, OFDMA The implementation of the iftable for SS must create one row for each SS WirelessMAN interface. Additional rows may be necessary to support other network interfaces, such as Ethernet. The following recommendations must be applied to each row: ifindex value is implementation specific iftype must be set to propbwapmp (value of as defined in...) ieee0wman value of as defined in subclause...) ifspeed must be null set to 0 ifphysaddress must be set to the SS MAC Address (of the WirelessMAN interface) All other columnar objects must be initialized as specified in RFC Table Example of the Usage of iftable objects for subscriber station Table shows an example of the usage of iftable for SS that may support one of the following MAC / PHY interfaces: IEEE 0.-00, OFDM IEEE 0.-00, OFDMA 0 IEEE 0.e, OFDMA IEEE 0.e, OFDMA IEEE 0.e, OFDMA Null 0 Ethernet ethernetcsmacd Interface Speed MAC address of BS sector MAC address Administration Status Administration Status Operational Status Operational Status iftable ifindex iftype (IANA) ifspeed ifphysaddress ifadminstatus ifoperstatus SS ieee0wman propbwapmp Null 0 Ethernet ethernetcsmacd Null Interface Speed MAC address of SS MAC address Administration Status Administration Status Operational Status Operational Status Figure shows a procedure describing how BS can determine the MAC / PHY standard interface and capability a SS / MS can support. Copyright 00 IEEE. All rights reserved.

21 00-- IEEE 0.i-0/00r, November Figure SS / MS Network Entry. Receive RNG-REQ from SS / MS. If MAC version is 0.-00, then a) wmanifbsssmacversion = ieee0dotof00 b) wmanifbsssmobilityfeatures = No Supported c) Go to step. Receive REG-REQ from SS / MS. If Mobility Feature is supported, then a) wmanifbsssmacversion = ieee0dote b) wmanifbsssmobilityfeatures = Supported otherwise a) wmanifbsssmacversion = ieee0dote b) wmanifbsssmobilityfeatures = Not Supported Copyright 00 IEEE. All rights reserved.

22 00-- IEEE 0.i-0/00r, November Continue network entry procedure.. Events and traps The wmanifmib defines objects for reporting events through mechanisms, such as traps and non-volatile logging. However, the definition and coding of events is vendor-specific. In order to assist the network operators who must troubleshoot multi-vendor equipment, the circumstances and meaning of each event should be reported as human-readable text. Therefore, the trap definitions should include the event reason encoded as display String, and is shown in the following example. trapname NOTIFICATION-TYPE OBJECTS {ifindex, eventreason, other useful objects } MAX-Access read-only "trap description" ::= { Object Id }. [Insert a new subclause..].. MIB Modules Table lists all defined ASN. MIB modules, their status and module identity OID. The subsequent subclauses give more details about each defined MIB module. MIB module name Revision Status Module Identity OID WMAN-IF-MIB Deprecated iso().org().dod().internet().mgmt().mib-().transmission().wmanifmib() WMAN-DEV-MIB Active iso().std(0).iso0(0).wman().wmandevmib() WMAN-IF-MIB Active iso().std(0).iso0(0).wman().wmanifmib() WMAN-IFM-MIB Active iso().std(0).iso0(0).wman().wmanifmmib()... WMAN-IF-MIB module Table List of ASN. MIB Modules The WMAN-IF-MIB MIB module defines management objects relevant to the broadband wireless interface as defined in the standard IEEE The current status of the WMAN-IF-MIB MIB module is deprecated and the module should not be implemented by the equipment compliant with the amendment IEEE0.i. The WMAN-IF-MIB module should be implemented instead. The WMAN-IF-MIB MIB module is identified by module identity name wmanifmib and shall be accessed through the following OID: iso().org().dod().internet().mgmt().mib-().transmission().wmanifmib() Copyright 00 IEEE. All rights reserved.

23 00-- IEEE 0.i-0/00r, November WMAN-DEV-MIB module The WMAN-DEV-MIB MIB module defines management objects relevant to the device implementing the IEEE and 0.-00e standards. The objects of this MIB module may refer explicitly to terms defined in the standard (e.g. configuration file encodings) but mainly provide the mandatory support required to manage the devices implementing the IEEE 0. interface. The current status if the WMAN-DEV-MIB is active. The BS shall implement this MIB module. SS shall implement this MIB module if it is managed using SNMP protocol. The WMAN-DEV-MIB MIB module is identified by module identity name wmandevmib and shall be accessed through the following OID: iso().std(0).iso0(0).wman().wmandevmib()... WMAN-IF-MIB module The WMAN-IF-MIB MIB module defines all management objects that are common to all broadband wireless interfaces as defined in the IEEE Std 0. standard. The current status of the WMAN-IF-MIB MIB module is active. The BS shall implement this MIB module. The SS shall implement this MIB module if it is managed using SNMP protocol. The WMAN-IF-MIB MIB module is identified by module identity name wmanifmib and shall be accessed through the following OID: iso().std(0).iso0(0).wman().wmanifmib()... WMAN-IFM-MIB module The WMAN-IFM-MIB MIB module defines all management objects that are specific to mobile broadband wireless interfaces as defined in the IEEE Std 0. standard. The current status of the WMAN-IFM-MIB MIB module is active. The BS shall implement this MIB module if it supports mobility. The MS shall implement this MIB module if it is managed using SNMP protocol. The WMAN-IFM-MIB MIB module is identified by module identity name wmanifmmib and shall be accessed through the following OID: iso().std(0).iso0(0).wman().wmanifmmib() Copyright 00 IEEE. All rights reserved.

25 00-- IEEE 0.i-0/00r, November [Change subclause as follows:]. 0. MIB Modulesstructure for SNMP [Delete the st paragraph in subclause ] [Change subclause. as follows:]. Structure of MIB modules [Move subclause heading. in 0.f to subclause..].. wmanifmib [Move nd paragraph of subclause. in 0.f to subclause.. The wmanifmib is composed of three groups: wmanifbsobjects: contains managed objects to be implemented in the SNMP agent in BS. wmanifssobjects: contains managed objects to be implemented in the SNMP agent in SS. wmanifcommonobjects: contains common managed objects to be implemented in the SNMP agent in BS and SS. [Move subclause heading. in 0.f to subclause..].. wmandevmib [Move rd paragraph of subclause. in 0.f to subclause..] The wmandevmib is composed of three groups: wmandevbsobjects: contains managed objects to be implemented in the SNMP agent in BS. wmandevssobjects: contains managed objects to be implemented in the SNMP agent in SS. wmandevcommonobjects: contains managed objects to be implemented in the SNMP agent in BS/SS. [Add a new subclause..] Copyright 00 IEEE. All rights reserved.

26 00-- IEEE 0.i-0/00r, November wmanifmib Figure shows the high level MIB structure of wmanifmib for 0.. The MIB structure is organized based on the the reference model as defined in IEEE standard.... wmanifbsobjects... wmanifbspacketcs Figure wmanifmib structure Figure shows the structure of wmanifbspacketcs subtree that contains BS managed objects related to the Packet CS management entity layer.... wmanifbsprovisionedsftable wmanifmib wmanifbsobjects wmanifbspacketcs wmanifbscps wmanifbspkmobjects wmanifbsnotification wmanifbsphy wmanifssobjects wmanifsscps wmanifsspkmobjects wmanifssnotification wmanifssphy wmanifcommonobjects wmanifcmnpacketcs wmanifcmncps wmanifcmnpkmobjects wmanifbspacketcs wmanifbsprovisionedsftable wmanifbsssprovisionedforsftable wmanifbsserviceclasstable wmanifbsclassifierruletable wmanifbssspacketcountertable Figure wmanifbspacketcs structure wmanifbsprovisionedsftable contains provisioned service flow profiles for SSs, and pointers to wmanifbsserviceclasstable and wmanifbsclassifierruletable for QoS parameters and classifier rules respectively. Copyright 00 IEEE. All rights reserved.

27 00-- IEEE 0.i-0/00r, November wmanifbsprovisionedforsftable wmanifbsprovisionedforsftable maps the MAC addresses of SSs to the service flows provisioned in wmanifbsprovisionedsftable. It enables downlink multicast services where MAC addresses of multiple SSs can be mapped to the same service flow.... wmanifbsserviceclasstable Each entry of the wmanifbsserviceclasstable contains QoS parameter set, as defined in subclause.. and. in IEEE standard.... wmanifbsclassifierruletable wmanifbsclassifierruletable contains the packet classifier rules sassociated with service flows.... wmanifbssspacketcountertable wmanifbssspacketcountertable contains counters to keep track of the number of packets and octets that have been received or transmitted on the per service flow basis.... wmanifbscps Figure shows the structure of wmanifbscps subtree that contains BS managed objects related to the MAC CPS management entity layer. wmanifbscps wmanifbsregisteredsstable wmanifbsconfigurationtable wmanifbschannelmeasurementtable wmanifbscapabilities wmanifbsssreqcapabilitiestable wmanifbsssrspcapabilitiestable wmanifbsbasiccapabilitiestable wmanifbscapabilitiesconfigtable wmanifbsssactionstable... wmanifbsregisteredsstable Figure wmanifbscps structure Each entry in the wmanifbsregisteredsstable contains the information of SS that has been registered through REG-REQ and REG-RSP messages.... wmanifbsconfigurationtable wmanifbsconfigurationtable contains objects for BS system parameters and constants as defined in subclause. of IEEE standard. wmanifbsconfigurationtable also contains objects that define the default behaviour of the BS for nd Management Channel scheduling and SFID allocation as well as configuration parameters of the CPS scheduler and AAS system. Copyright 00 IEEE. All rights reserved.

28 00-- IEEE 0.i-0/00r, November wmanifbschannelmeasurementtable wmanifbschannelmeasurementtable contains channel measurement information on the uplink signal that were received from SS, and the downlink signal were obtained from SS using REP-REQ/RSP messages..... wmanifbscapabilities... wmanifbsssreqcapabilitiestable wmanifbsssreqcapabilitiestable contains the basic capability information of SSs that have been reported by SSs to BS using RNG-REQ, SBC-REQ and REG-REQ messages.... wmanifbsssrspcapabilitiestable wmanifbsssrspcapabilitiestable contains the basic capability information of SSs that have been negotiated and agreed between BS and SS via RNG-REQ/RSP, SBC-REQ/RSP and REG-REQ/RSP messages.... wmanifbsbasiccapabilitiestable wmanifbsbasiccapabilitiestable contains the basic capabilities of the BS as implemented in BS hardware and software. These capabilities along with the configuration for them (wmanifbscapabilitiesconfigtable) are used for negotiation of basic capabilities with SS using RNG-RSP, SBC-RSP and REG-RSP messages.... wmanifbscapabilitiesconfigtable wmanifbscapabilitiesconfigtable contains the configuration for basic capabilities of BS. The table is intended to be used to restrict the Capabilities implemented by BS, for example in order to comply with local regulatory requirements. The BS should use the configuration along with the implemented Capabilities (wmanifbsbasiccapabilitiestable) for negotiation of basic capabilities with SS using RNG-RSP, SBC- RSP and REG-RSP messages.... wmanifbsssactionstable wmanifbsssactionstable contains all the actions specified for SSs in the standard. The actions are routed down to SS using nsolicited MAC messages: REG-RSP, DREG-REQ and RES-CMD. The table also contains the parameters of the actions in cases where they are specified by the standard.... wmanifbspkmobjects Figure shows the structure of wmanifbspkmobjects subtree that contains BS managed objects related to the MAC privacy management entity. wmanifbspkmobjects wmanifbspkmbasetable wmanifbspkmauthtable wmanifbspkmtektable Figure wmanifbspkmobjects structure Copyright 00 IEEE. All rights reserved.

29 00-- IEEE 0.i-0/00r, November wmanifbspkmbasetable wmanifbspkmbasetable contains base station PKM operational parameters described in subclause. of IEEE standard.... wmanifbssspkmauthtable wmanifbssspkmauthtable contains runtime subscriber station authentication and authorization parameters for each base station.... wmanifbspkmtektable wmanifbspkmtektable is double indexed by ifindex and SAId and contains runtime Security association parameters for each base station.... wmanifbsnotification Figure shows the structure of wmanifbsnotification subtree that contains BS traps to report fault events and exceptions, such as power status, RSSI threshold crossing.... wmanifbstrapcontrol... wmanifbstrapcontrolregister Figure wmanifbsnotification structure wmanifbstrapcontrolregister is used to enable or disable Base traps independently.... wmanifbsstatustrapcontrolregister wmanifbsstatustrapcontrolregister is used to enable or disable Base Station status notification traps.... wmanifbsthresholdconfigtable wmanifbsthresholdconfigtable contains threshold objects that can be set to detect the threshold crossing events.... wmanifbstrapdefinitions wmanifbstrapdefinitions object group defines all the traps reported by BS.... wmanifbsphy wmanifbsnotification wmanifbstrapcontrol wmanifbstrapcontrolregister wmanifbsstatustrapcontrolregister wmanifbsthresholdconfigtable wmanifbstrapdefinitions Figure shows the structure of wmanifbsphy subtree that contains BS managed objects related to the Physical layer. Copyright 00 IEEE. All rights reserved.

30 00-- IEEE 0.i-0/00r, November wmanifbsphy wmanifbsofdmphy wmanifbsofdmuplinkchanneltable wmanifbsofdmdownlinkchanneltable wmanifbsofdmucdburstprofiletable wmanifbsofdmdcdburstprofiletable wmanifbsofdmconfigurationtable wmanifbsssofdmreqcapabilitiestable wmanifbsssofdmreqcapabilitiestable wmanifbsofdmcapabilitiestable wmanifbsofdmcapabilitiesconfigtable wmanifbsofdmaphy wmanifbsofdmauplinkchanneltable wmanifbsofdmadownlinkchanneltable wmanifbsofdmaucdburstprofiletable wmanifbsofdmadcdburstprofiletable wmanifbsofdmaconfigurationtable wmanifbsssofdmareqcapabilitiestable wmanifbsssofdmarspcapabilitiestable wmanifbsofdmacapabilitiestable wmanifbsofdmacapabilitiesconfigtable wmanifbsofdmaexuplinkchanneltable wmanifbsofdmaexdownlinkchanneltable... wmanifbsofdmphy Figure wmanifbsphy structure wmanifbsofdmphy is a group containing objects specific to OFDM PHY.... wmanifbsofdmuplinkchanneltable wmanifbsofdmuplinkchanneltable contains OFDM UCD (Uplink Channel Descriptor) channel attributes, defining the transmission characteristics of uplink channels.... wmanifbsofdmdownlinkchanneltable wmanifbsofdmdownlinkchanneltable contains OFDM DCD (Downlink Channel Descriptor) channel attributes, defining the transmission characteristics of downlink channels.... wmanifbsofdmucdburstprofiletable wmanifbsofdmucdburstprofiletable contains OFDM UCD burst profiles for each uplink channel.... wmanifbsofdmdcdburstprofiletable wmanifbsofdmdcdburstprofiletable provides one row for each OFDM DCD burst profile.... wmanifbsofdmconfigurationtable wmanifbsofdmconfigurationtable contains BS configuration objects, specific to OFDM PHY. Copyright 00 IEEE. All rights reserved.

31 00-- IEEE 0.i-0/00r, November wmanifbsssofdmreqcapabilitiestable wmanifbsssofdmreqcapabilitiestable contains the basic capability information, specific to OFDM Phy, of SSs that have been reported by SSs to BS using RNG-REQ, SBC-REQ and REG-REQ messages. Entries in this table should be created when an SS registers with a BS.... wmanifbsssofdmrspcapabilitiestable wmanifbsssofdmrspcapabilitiestable contains the basic capability information, specific to OFDM Phy, of SSs that have been negotiated and agreed between BS and SS via RNG-REQ/RSP, SBC-REQ/RSP and REG-REQ/RSP messages. This table augments the wmanifbsregisteredsstable.... wmanifbsofdmcapabilitiestable wmanifbsofdmcapabilitiestable contains the basic capabilities, specific to OFDM Phy, of the BS as implemented in BS hardware and software.... wmanifbsofdmcapabilitiesconfigtable wmanifbsofdmcapabilitiesconfigtable contains the configuration for basic capabilities of BS, specific to OFDM Phy. The table is intended to be used to restrict the Capabilities implemented by BS.... wmanifbsofdmaphy wmanifbsofdmaphy is a group containing objects specific to OFDMA PHY.... wmanifbsofdmauplinkchanneltable wmanifbsofdmauplinkchanneltable contains OFDMA UCD channel attributes, defining the transmission characteristics of uplink channels.... wmanifbsofdmadownlinkchanneltable wmanifbsofdmadownlinkchanneltable contains OFDMA DCD channel attributes, defining the transmission characteristics of downlink channels.... wmanifbsofdmaucdburstprofiletable wmanifbsofdmaucdburstprofiletable contains OFDMA UCD burst profiles for each uplink channel.... wmanifbsofdmadcdburstprofiletable wmanifbsofdmadcdburstprofiletable provides one row for each OFDMA DCD burst profile.... wmanifbsofdmaconfigurationtable wmanifbsofdmaconfigurationtable contains BS configuration objects, specific to OFDMA PHY.... wmanifbsssofdmareqcapabilitiestable wmanifbsssofdmareqcapabilitiestable contains the basic capability information, specific to OFDMA Phy, of SSs or MSs that have been reported by SSs to BS using RNG-REQ, SBC-REQ and REG-REQ messages. Entries in this table should be created when an SS registers with a BS. Copyright 00 IEEE. All rights reserved.

32 00-- IEEE 0.i-0/00r, November wmanifbsssofdmarspcapabilitiestable wmanifbsssofdmarspcapabilitiestable contains the basic capability information, specific to OFDMA Phy, of SSs or MSs that have been negotiated and agreed between BS and SS via RNG-REQ/RSP, SBC- REQ/RSP and REG-REQ/RSP messages. This table augments the wmanifbsregisteredsstable.... wmanifbsofdmacapabilitiestable wmanifbsofdmacapabilitiestable contains the basic capabilities, specific to OFDMA Phy, of the BS as implemented in BS hardware and software.... wmanifbsofdmacapabilitiesconfigtable wmanifbsofdmacapabilitiesconfigtable contains the configuration for basic capabilities of BS, specific to OFDMA Phy. The table is intended to be used to restrict the Capabilities implemented by BS.... wmanifbsofdmaexuplinkchanneltable wmanifbsofdmaexuplinkchanneltable arguments wmanifbsofdmauplinkchanneltable to contain new UCD channel encidings that have been added to IEEE 0.e wmanifbsofdmaexdownlinkchanneltable wmanifbsofdmaexdownlinkchanneltable arguments wmanifbsofdmadownlinkchanneltable to contain new DCD channel encidings that have been added to IEEE 0.e wmanifssobjects... wmanifsscps Figure shows the structure of wmanifsscps subtree that contains SS managed objects related to the MAC CPS management entity layer.... wmanifssconfigurationtable Figure wmanifsscps structure wmanifssconfigurationtable contains objects for SS system parameters and constants as defined in subclause. of IEEE standard.... wmanifsschannelmeasurementtable wmanifsschannelmeasurementtable contains downlink channel measurement information for each SS.... wmanifsspkmobjects wmanifsscps wmanifssconfigurationtable wmanifsschannelmeasurementtable Figure shows the structure of wmanifsspkmobjects subtree that contains subscriber station manageable objects related to the privacy management entity. Copyright 00 IEEE. All rights reserved. 0

33 00-- IEEE 0.i-0/00r, November wmanifsspkmauthtable Figure wmanifsspkmobjects structure wmanifsspkmauthtable contains subscriber station authentication and authorization parameters including those described in subclause. of IEEE wmanifsspkmtektable wmanifsspkmtektable contains subscriber station runtime parameters for each active security association.... wmanifssdevicecerttable wmanifssdevicecerttable describes the PKM device certificates for each SS wireless interface.... wmanifssnotification Figure shows the structure of wmanifssnotification subtree that contains SS traps to report fault events and exceptions, such as RSSI threshold crossing.... wmanifsstrapcontrol... wmanifsstrapcontrolregister Figure wmanifssnotification structure wmanifsstrapcontrolregister is used to enable or disable Subscriber Station traps.... wmanifssthresholdconfigtable wmanifssthresholdconfigtable contains threshold objects that can be set to detect the threshold crossing events.... wmanifsstrapdefinitions wmanifbspkmobjects wmanifsspkmauthtable wmanifsspkmtektable wmanifssdevicecerttable wmanifssnotification wmanifsstrapcontrol wmanifsstrapcontrolregister wmanifssthresholdconfigtable wmanifsstrapdefinitions wmanifsstrapdefinitions group defines all the traps reported by SS. Copyright 00 IEEE. All rights reserved.

34 00-- IEEE 0.i-0/00r, November wmanifssphy Figure shows the structure of wmanifssphy subtree that contains SS managed objects related to the Physical layer.... wmanifssofdmphy Figure wmanifssphy structure wmanifssofdmphy is a group containing objects specific to OFDM PHY.... wmanifssofdmuplinkchanneltable wmanifssofdmuplinkchanneltable contains OFDM UCD channel attributes, defining the transmission characteristics of uplink channels.... wmanifssofdmdownlinkchanneltable wmanifssofdmuplinkchanneltable contains OFDM DCD channel attributes, defining the transmission characteristics of downlink channels.... wmanifssofdmucdburstprofiletable wmanifssofdmucdburstprofiletable contains OFDM UCD burst profiles for each uplink channel.... wmanifssofdmdcdburstprofiletable wmanifssofdmdcdburstprofiletable provides one row for each OFDM DCD burst profile.... wmanifssofdmaphy wmanifssphy wmanifssofdmphy wmanifssofdmuplinkchanneltable wmanifssofdmdownlinkchanneltable wmanifssofdmucdburstprofiletable wmanifssofdmdcdburstprofiletable wmanifssofdmaphy wmanifssofdmauplinkchanneltable wmanifssofdmadownlinkchanneltable wmanifssofdmaucdburstprofiletable wmanifssofdmadcdburstprofiletable wmanifssofdmaphy is a group containing objects specific to OFDMA PHY.... wmanifssofdmauplinkchanneltable wmanifssofdmauplinkchanneltable contains OFDMA UCD channel attributes, defining the transmission characteristics of uplink channels. Copyright 00 IEEE. All rights reserved.

35 00-- IEEE 0.i-0/00r, November wmanifssofdmadownlinkchanneltable wmanifssofdmadownlinkchanneltable contains OFDMA DCD channel attributes, defining the transmission characteristics of downlink channels.... wmanifssofdmaucdburstprofiletable wmanifssofdmaucdburstprofiletable contains OFDMA UCD burst profiles for each uplink channel.... wmanifssofdmadcdburstprofiletable wmanifssofdmadcdburstprofiletable provides one row for each OFDMA DCD burst profile.... wmanifcommonobjects... wmanifcmnpacketcs Figure shows the structure of wmanifcmnpacketcs subtree that contains common managed objects related to the Packet CS management entity layer.... wmanifcmnclassifierruletable Figure wmanifcmnpacketcs structure wmanifcmnclassifierruletable contains runtime classifier rules screening criteria for each service flow.... wmanifcmnphsruletable wmanifcmnphsruletable contains PHS rule dictionary entries. Each entry contains the data of the header to be suppressed along with its identification - PHSI.... wmanifcmncps Figure shows the structure of wmanifcmncps subtree that contains common managed objects related to the MAC CPS management entity.... wmanifcmncpsserviceflowtable wmanifcmnpacketcs wmanifcmnclassifierruletable wmanifcmnphsruletable wmanifcmncps wmanifcmncpsserviceflowtable wmanifcmnbsssconfigurationtable Figure wmanifcmncps structure wmanifcmncpsserviceflowtable contains Service Flow managed objects that are common in BS and SS. Copyright 00 IEEE. All rights reserved.

36 00-- IEEE 0.i-0/00r, November wmanifcmnbsssconfigurationtable wmanifcmnbsssconfigurationtable provides one row for each BS sector that contains the system parameters common in both SS and BS. All SSs shall have the same parameters as the BS to which the SSs are associated.... wmanifcmnpkmobjects Figure shows the structure of wmanifcmnpkmobjects subtree that contains common PKM objects.... wmanifcmncryptosuitetable Figure wmanifcmnpkmobjects structure wmanifcmncryptosuitetable contains supported crypto suites for the particular SS and other crypto parameters such as key lifetimes. [Add a new subclause..].. wmanifmmib wmanifcmnpkmobjects wmanifcmncryptosuitetable Figure shows the high level MIB structure of wmanifmmib for IEEE 0.e-00. The MIB structure is organized based on the the FCAPS reference model. wmanifmmib wmanifmbsobjects wmanifmbscm wmanifmbspm wmanifmbsfm wmanifmbssm wmanifmbsam wmanifmssobjects wmanifmsscm wmanifmsspm wmanifmssfm wmanifmsssm wmanifmssam wmanifmcommonobjects wmanifmcmncm wmanifmcmnpm wmanifmcmnfm wmanifmcmnsm wmanifmcmnam Copyright 00 IEEE. All rights reserved.

37 00-- IEEE 0.i-0/00r, November wmanifmbsobjects... wmanifmbscm Figure wmanifmmib structure Figure shows the structure of wmanifmbscm subtree that contains BS managed objects related to Configuration Management. wmanifmbscm wmanifmbscapabilities wmanifmbsssreqcapabilitiestable wmanifmbsssrspcapabilitiestable wmanifmbsbasiccapabilitiestable wmanifmbscapabilitiesconfigtable wmanifmbspowersavingmode wmanifmbssspowersavingstatustable wmanifmbssspowersavingclassestable... wmanifmbscapabilities... wmanifmbsssreqcapabilitiestable Figure wmanifmbscm structure wmanifmbsssreqcapabilitiestable contains the basic capability information of SSs that have been reported by SSs to BS using RNG-REQ, SBC-REQ and REG-REQ messages... wmanifmbsssrspcapabilitiestable wmanifmbsssrspcapabilitiestable contains the basic capability information of SSs that have been negotiated and agreed between BS and SS via RNG-REQ/RSP, SBC-REQ/RSP and REG-REQ/RSP messages... wmanifmbsbasiccapabilitiestable wmanifmbsbasiccapabilitiestable contains the basic capabilities of the BS as implemented in BS hardware and software. These capabilities along with the configuration for them (wmanifmbscapabilitiesconfigtable) are used for negotiation of basic capabilities with SS using RNG- RSP, SBC-RSP and REG-RSP messages.... wmanifmbscapabilitiesconfigtable wmanifmbscapabilitiesconfigtable contains the configuration for basic capabilities of BS. The table is intended to be used to restrict the Capabilities implemented by BS, for example in order to comply with local regulatory requirements. The BS should use the configuration along with the implemented Capabilities (wmanifmbsbasiccapabilitiestable) for negotiation of basic capabilities with SS using RNG-RSP, SBC- RSP and REG-RSP messages. Copyright 00 IEEE. All rights reserved.

38 00-- IEEE 0.i-0/00r, November wmanifmbspowersavingmode... wmanifmbssspowersavingstatustable wmanifmbssspowersavingstatustable contains the power saving status for each CID in an SS.... wmanifmbssspowersavingclassestable wmanifmbssspowersavingclassestable contains the power saving classes definitions, and activation / deactivation information that are provided by MOB_SLP-REQ and MOB_SLP-RSP messages..... wmanifmbspm Figure 0 shows the structure of wmanifmbspm subtree that contains BS managed objects related to Performance Management. Figure 0 wmanifmbspm structure... wmanifmbssssleepmodestatisticstable wmanifmbssssleepmodestatisticstable contains the sleep mode statistic for SS.. ASN. Definitions of MIB Modules.. wmanifmib.. wmandevmib wmanifmbspm wmanifmbssssleepmodestatisticstable Copyright 00 IEEE. All rights reserved.

39 00-- IEEE 0.i-0/00r, November wmanifmib WMAN-IF-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned, Integer, Counter, Counter, transmission FROM SNMPv-SMI SnmpAdminString FROM SNMP-FRAMEWORK-MIB TEXTUAL-CONVENTION, MacAddress, RowStatus, TruthValue, TimeStamp, DateAndTime FROM SNMPv-TC InetAddressType, InetAddress FROM INET-ADDRESS-MIB OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv-CONF ifindex FROM IF-MIB; wmanifmmib MODULE-IDENTITY LAST-UPDATED "000000Z" -- November, 00 ORGANIZATION "IEEE 0." CONTACT-INFO "WG stds-0-@ieee.org WG Chair: Roger B. Marks Postal: NextWave Broadband, Inc. r.b.marks@ieee.org TGf Chair: Phillip Barber Postal: Huawei Technologies Co., Ltd pbarber@futurewei.com Editor: Joey Chou Postal: Intel Corporation 00 W. Chandler Blvd, Chandler, AZ, USA joey.chou@intel.com" "This material is from IEEE Std 0.i Copyright (c) 00 IEEE. This MIB Module defines managed objects for Subscriber Station and Base Station based on IEEE Std and its amendment IEEE Std 0.e-00. The MIB contains managed objects that are specific to mobile Broadband Wireless Networks." REVISION "000000Z" Copyright 00 IEEE. All rights reserved.

IEEE Broadband Wireless Access Working Group <http://ieee802.org/16> MIB II Integration and MIB II Table

IEEE Broadband Wireless Access Working Group <http://ieee802.org/16> MIB II Integration and MIB II Table 00-0-0 IEEE C0.i-0/00r Project Title Date Submitted Source(s) IEEE 0. Broadband Wireless Access Working Group MIB II Integration and MIB II Table 00-0-0 Joey Chou Intel Corporation