IEEE Broadband Wireless Access Working Group < MIB II Integration and MIB II Table

Transcription

1 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 Joey Chou Intel Corporation 000 W. Chandler Blvd. Chandler, AZ Re: Abstract Purpose Notice Release Patent Policy and Procedures This contribution proposed the text for Section of IEEE P0.i WG draft. Adoption This document has been prepared to assist IEEE 0.. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) 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 0.. The contributor is familiar with the IEEE 0. Patent Policy and Procedures (Version.0) < including the statement IEEE standards may include the known use of patent(s), including patent applications, if there is technical justification in the opinion of the standards-developing committee and provided the IEEE receives assurance from the patent holder that it will license applicants under reasonable terms and conditions for the purpose of implementing the standard. Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <mailto:r.b.marks@ieee.org > as early as possible, in written or electronic form, of any patents (granted or under application) that may cover technology that is under consideration by or has been approved by IEEE 0.. The Chair will disclose this notification via the IEEE 0. web site <

2 IEEE C0.i-0/00r Table of Content.Introduction....MIB-II Integration....Configuration....Mobile MIB Definition...

3 IEEE C0.i-0/00r. Introduction This contribution proposes the text for Section of IEEE P0.i WG draft. 0. MIB-II Integration wmanifmib, as defined in IEEE P0.f standard, is located under MIB-II subtree, and can be accessed through iftype propbwapmp. propbwapmp is originally defined for proprietary broadband wireless access for point to multipoint connections, and therefore, it is not sufficient to support a complete suite of applications based on 0. standard. This contribution proposes the test for section, Configuration. Th NetMan WG should submit a request to IANA for the assignment of a new IANAiftype ieee0wman. 0. Configuration [Insert a new subclause.:]. Mobile MIB for SNMP.. MIB-II integration wmanifmib is located under MIB-II subtree. A submission will be sent to the Internet Assigned Numbers Authority (IANA) to assign ieee0wman for wmanifmib. IANAifType ::= TEXTUAL-CONVENTION SYNTAX INTEGER { ieee0wman (???) -- IEEE 0. WirelessMAN -- standard to be assigned -- by IANA } Pending on IETF approval, wmanifmib will be accessed through iso.org.dod.internet.mgmt.mib-.transmission.iftype (...0.???) 0. Mobile MIB Definition The mobile MIB is an extension to IEEE 0.f in adding MIB support for new features and functions included in IEEE 0.e standard. Therefore, mobile MIB should be a revision of IEEE 0.f MIB based on the following reasons: The revision approach will reduce significantly the amount of IEEE 0.i work, as opposed to open the complete 0.f MIBfor changes. Avoid theduplication of themajorityof managedobjects that were defined in IEEE 0.f MIB. IEEE 0.f MIB structure has been designed to support multiple PHYs (e.g. OFDM- OFDMA-0), and MACenhancements. Support the backward-compatibility requirement as defined inrfc, section.

4 IEEE C0.i-0/00r o o over the wire compability of agent and manager implementation that are based on different revisions ofthe MIB module. Compilation compatibility Support the additional enhancements to be proposed byotherwgs. 0 [Insert a new subclause..:].. 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 standards (e.g. IEEE 0.-00, IEEE 0.e). The following recommendations must be applied to each row defining BS sector: ifindex value is implementation specific iftype must be set to ieee0wman ifspeed must be null ifphysaddress must be set to the MAC Address of the BS sector All other columnar objects must be initialized as specified in RFC 0 0 Table Example of the Usage of iftable objects for BS 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, OFDM IEEE 0.e, OFDM IEEE 0.e, OFDM 0 0 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:

5 IEEE C0.i-0/00r 0 0 IEEE 0.-00, OFDM ifindex value is implementation specific iftype must be set to ieee0wman ifspeed must be null 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 SS 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 0 Figure 0 shows a procedure describing how BS can determine the FFT size of a SS or MS during the DL synchronization for. 0 0

6 IEEE C0.i-0/00r 0 fgd 0 Figure 0 SS / MS DL Synchronization. Set the Rx channel (Select a frequency for receiving DL channel). Set the FFT size. Set the CP size. If a preamble is received successfully, then go to step ; otherwise, a. If FFT size is not exhausted, then select a new FFT size, and go to step ; otherwise, 0 0 If channel to be scanned is exhausted, then declare SS / MS DL synchronization failed; otherwise, select a new channel, and go step. Set the CP size. If a FCH (Frame Control Header) is received successfully, then go to network entry; otherwise, a. If CP size is not exhausted, then select a new CP size, and go to step ; otherwise, declare SS / MS DL synchronization failed b. Set FFT size object Figure shows a procedure describing how BS can determine the MAC / PHY standard interface and capability a SS / MS can support.

7 IEEE C0.i-0/00r Receive RNG-REQ from SS / MS. If MAC version is Then Figure SS / MS Network Entry a. wmanifbsssmacversion = ieee0dotof00 b. wmanifbsssmobilityfeatures = No Supported c. Go to step. Receive REG-REQ from SS / MS. If Mobility Feature is supported, Then Otherwise a. wmanifbsssmacversion = ieee0dote b. wmanifbsssmobilityfeatures = Supported a. wmanifbsssmacversion = ieee0dote b. wmanifbsssmobilityfeatures = Not Supported. Continue network entry procedure

8 IEEE C0.i-0/00r 0 0 [Add the following ASN. code to Annex E:] WmanIfMacVersion ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Version number of IEEE 0.." SYNTAX INTEGER {ieee0dotof00(), ieee0dotcof00(), ieee0dotaof00(), ieee0dotof00(), ieee0dote()} WmanIfMacVersion ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Version number of IEEE 0.." SYNTAX BITS {mobilitysupport(0), sleepmodesupport(), idlemodesupport()}

9