1、 ETSI TS 102 389 V1.1.1 (2005-01)Technical Specification Broadband Radio Access Networks (BRAN);HiperMAN;Simple Network Management Protocol (SNMP)Management Information Base (MIB)ETSI ETSI TS 102 389 V1.1.1 (2005-01) 2 Reference DTS/BRAN-0040007 Keywords access, broadband, hiperMAN, management, netw
2、ork, radio ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present doc
3、ument can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of disp
4、ute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other E
5、TSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by wri
6、tten permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo a
7、re Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 389 V1.1.1 (2005-01) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5
8、 1 Scope 6 2 References 6 3 Abbreviations .6 4 BWA Network Management Reference Model .7 5 Relationship with Interface MIB7 5.1 MIB-2 Integration.8 5.2 Usage of MIB-II Tables .8 5.3 Events and Traps 8 5.4 HiperMAN MIB Structure .9 5.5 wmanIfBsObjects .10 5.5.1 wmanIfBsSystem10 5.5.1.1 wmanIfBsRegist
9、eredSsTable 10 5.5.2 wmanIfBsPacketCs.10 5.5.2.1 wmanIfBsProvisionedSfTable 10 5.5.2.2 wmanIfBsServiceClassTable 10 5.5.2.3 wmanIfBsClassifierRuleTable 11 5.5.3 wmanIfBsCps .11 5.5.3.1 wmanIfBsConfigurationTable.11 5.5.3.2 wmanIfBsChMeasurementTable.11 5.5.4 wmanIfBsPkm 11 5.5.4.1 wmanIfBsPkmBaselin
10、eTable11 5.5.4.2 wmanIfBsPkmAuthTable12 5.5.4.3 wmanIfBsPkmTekTable .12 5.5.5 wmanIfBsNotification 12 5.6 wmanIfSsObjects .12 5.6.1 wmanSsSystem.12 5.6.1.1 wmanIfSsConfigFileEncodingTable.12 5.6.2 wmanIfSsCps12 5.6.2.1 wmanIfSsConfigurationTable .12 5.6.2.2 wmanIfSsStatisticsCountersTable.12 5.6.3 w
11、manIfSsPkm.12 5.6.3.1 wmanIfSsPkmAuthTable 12 5.6.3.2 wmanIfSsPkmTekTable12 5.6.3.3 wmanIfSsPkmCertificatesTable13 5.6.4 wmanIfSsTraps.13 5.7 wmanIfCommonObjects 13 5.7.1 wmanIfCmnPacketCs .13 5.7.1.1 wmanIfCmnClassifierRuleTable.13 5.7.2 wmanIfCmnCps13 5.7.2.1 wmanIfCmnServiceFlowTable .13 5.7.2.2
12、wmanIfCmnBsSsConfigurationTable .13 5.7.2.3 wmanIfCmnSsChMeasurementTable .13 5.7.3 wmanIfCmnPrivacy13 5.7.3.1 wmanIfCmnCryptoSuiteTable 13 5.7.4 wmanIfCmnOfdmPhy.13 5.7.4.1 wmanIfOfdmUplinkChannelTable14 5.7.4.2 wmanIfOfdmDownlinkChannelTable.14 5.7.4.3 wmanIfOfdmUcdBurstProfileTable14 5.7.4.4 wman
13、IfOfdmDcdBurstProfileTable14 ETSI ETSI TS 102 389 V1.1.1 (2005-01) 4 6 ASN.1 Definition of HiperMAN MIB .14 Annex A (informative): Bibliography.94 History 95 ETSI ETSI TS 102 389 V1.1.1 (2005-01) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have
14、been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standard
15、s“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other
16、IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). Introduction HiperMAN group defi
17、nes air interface specifications for the development of standard based Base Station (BS) and Subscriber Station (SS) to provide broadband wireless services to Metropolitan Area Networks (MANs). The present document defines the HiperMAN MIB for DLC and PHY layers to achieve management interoperabilit
18、y and provide the remote management capability that are urgently needed for massive HiperMAN deployment. ETSI ETSI TS 102 389 V1.1.1 (2005-01) 6 1 Scope The scope of the present document is to define the HiperMAN DLC and PHY MIB for the SS and BS, based on HiperMAN PHY and DLC specifications. The de
19、finition of managed objects in this MIB is based on SNMPv2 Structure of Management Information (SMI) 4 and Textual Conventions 5. Therefore, HiperMAN MIB is compliant to SNMPv2, but is backward compatible to SNMPv1 through appropriate translation. Since the HiperMAN MIB has to be accessed through th
20、e MIB tree, its relationship with the Interface MIB-RFC 2863 7 are described. Additional MIBs may be necessary to manage other interfaces in the SS or BS, such as Ethernet, T1/E1 and ATM, but they are outside the scope of the present document. 2 References The following documents contain provisions
21、which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference,
22、 the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 102 177 (V1.2.1): “Broadband Radio Access Networks (BRAN); HiperMAN; Physical (PHY) layer“. 2 ETSI TS 102 178 (V1.2.1):
23、 “Broadband Radio Access Networks (BRAN); HiperMAN; Data Link Control (DLC) layer“. 3 IEEE P802.16-2004: “IEEE Standard for Local and Metropolitan area networks - Part 16: Air Interface for Fixed Broadband Wireless Access Systems“. 4 IETF RFC 1902 (1996): “Structure of Management Information for ver
24、sion 2 of the Simple Network Management Protocol (SNMPv2)“. 5 IETF RFC 1903 (1996): “Textual Convention for Version 2 of the Simple Network Management Protocol (SNMPv2)“. 6 IETF RFC 1213 (1991): “Management Information Base for Network Management of TCP/IP-based internets: MIB-II“. 7 IETF RFC 2863 (
25、2000): “The Interfaces Group MIB“. 8 PKCS #1 v2.0: “RSA Cryptography Standard“, RSA Laboratories, October 1998.“ http:/ 3 Abbreviations For the purposes of the present document, the following abbreviations apply: ATM Asynchronous Transfer Mode BS Base Station BWA Broadband Wireless Access CID Connec
26、tion ID DL Downlink ID Identifier ETSI ETSI TS 102 389 V1.1.1 (2005-01) 7 MAC Medium Access Control MIB Management Information Base NMS Network Management SystemPHY Physical layer (of network) QoS Quality of Service RSSI Received Signal Strength Indicator SDU Service Data Unit SFID Service Flow ID S
27、MI Structure of Management Information SNMP Simple Network Management Protocol SS Subscriber Station UL Uplink4 BWA Network Management Reference Model Figure 1 shows the management reference model of Broadband Wireless Access (BWA) networks. It consists of a Network Management System (NMS), performi
28、ng the network manager role, and managed nodes, which provide access to managed objects via MIB or virtual information store. SSs and BSs are managed nodes that act in the SNMP agent role. Furthermore, managed SSs, which have a secondary management CID, may be managed indirectly through the BS to wh
29、ich they are registered. In this case, the BS acts in an SNMP Proxy role on behalf of managed SSs. SS can be managed by NMS directly as well. The management information between SS and BS will be carried over Second Management CID for managed SS. If the 2ndmanagement CID does not exist, the SNMP mess
30、ages shall go through another interface in the customer premise. The SNMP agent in the SS can be managed directly, or via a SNMP proxy in the BS. MACSubscriberStation #1ManagedNodePHYMIBSNMPAgent.MACBase StationManagedNodePHYMIBSNMPProxyMACSubscriberStation #nManagedNodePHYMIBSNMPAgentNetworkManagem
31、entSystemInternetServiceFlowDatabaseFigure 1: BWA Network Management Reference Model 5 Relationship with Interface MIB This clause describes the integration with MIB-II 6 under Interface Group MIB defined in RFC 2863 7, as wmanIfMib will need to be integrated in the MIB tree. It describes where wman
32、IfMib is located in the MIB-II subtree, and how it can be accessed by NMS. ETSI ETSI TS 102 389 V1.1.1 (2005-01) 8 5.1 MIB-2 Integration The IANA has assigned the following ifType to point to multipoint broadband wireless access. IANAifType := TEXTUAL-COVENTION SYNTAX INTEGER propBWAp2Mp (184) - pro
33、p broadband wireless access - point to multipoint Therefore, upon wmanIfMib being approved by the IETF, this MIB can be accessed through iso.org.dod.internet.mgmt.mib-2.transmission.ifType (1.3.6.1.2.1.10.184) Wireless MAN interface table is located under transmission subtree, as follows. wmanIfMib
34、:= transmission 184 - WMAN interface table Before the approval of the IETF; however, wmanIfMib is temporary located under enterprise via: iso.org.dod.internet.private.enterprise.wmanIfMib (1.3.6.1.4.1.n); or iso.org.dod.internet.private.enterprise.vendorID.wmanIfMib (1.3.6.1.4.1.xxx.n). 5.2 Usage of
35、 MIB-II Tables “Interfaces“ group of MIB-II, in RFC 1573, has been designed to manage various sub-layers (e.g. MAC and PHY) beneath the internetwork-layer for numerous media-specific interfaces. ifTable in MIB-II is used to access the wmanIfMib. Table 1 describes some key attributes in the ifTable t
36、hat will be reused in the BS wmanIfMib. When the SNMP agent is implemented in a common base station controller, each BS sector will have an entry in the ifTable. When the SNMP agent is implemented in the sector controller, there is only one entry for the BS sector in the ifTable. Table 1: Usage of i
37、fTable objects for Base Station ifTable ifIndex IfType (IANA) IfSpeed ifPhysAddress ifAdminStatus ifOperStatus BS Sector 1 An ifEntry per BS sector (1) propBWAp2Mp Null MAC address of BS sector Administration Status Operational Status BS Sector 2 An ifEntry per BS sector (2) propBWAp2Mp Null MAC add
38、ress of BS sector Administration Status Operational Status BS Sector 3 An ifEntry per BS sector (3) propBWAp2Mp Null MAC address of BS sector Administration Status Operational Status Ethernet Null MAC address AdministrationStatus Operational Status Table 2 shows the usage of ifTable for SS. There is
39、 only one entry for the SS itself. Additional entries may be necessary to support other network interfaces, such as Ethernet. Table 2: Usage of ifTable objects for Subscriber Station ifTable ifIndex IfType (IANA) IfSpeed ifPhysAddress ifAdminStatus ifOperStatus SS An ifEntry for SS propBWAp2Mp Null
40、MAC address of SS Administration Status Operational Status Ethernet Null MAC address AdministrationStatus Operational Status 5.3 Events and Traps wmanIfMib defines objects for reporting events through mechanisms, such as traps and non-volatile logging. However, the definition and coding of events is
41、 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. ETSI ETSI TS 102 389 V1.1.1 (2005-01) 9 Therefore, the trap definitions should include the event reason enco
42、ded as display String, and is shown in the following example. trapName NOTIFICATION-TYPE OBJECTS ifIndex, eventReason, other useful objects MAX-Access read-only STATUS current DESCRIPTION “trap description“ := Object Id 5.4 HiperMAN MIB Structure Figure 2 shows the MIB structure of wmanIfMib for Hip
43、erMAN. The MIB structure is organized based on the reference model as defined in HiperMAN standards 1 and 2. wmanIfMib (1.3.6.1.2.1.10.184)wmanIfBsObjectswmanIfBsSystemwmanIfBsRegisteredSsTablewmanIfBsPacketCswmanIfBsProvisionedSfTablewmanIfBsServiceClassTablewmanIfBsCpswmanIfBsPkmwmanIfBsPkmBaseTab
44、lewmanIfBsPkmAuthTablewmanIfBsPkmTekTablewmanIfSsObjectswmanIfSsSystemwmanIfSsCpswmanIfSsConfigurationTablewmanIfSsPkmwmanIfSsPkmAuthTablewmanIfSsPkmTekTablewmanIfSsDeviceCertTablewmanIfCommonObjectswmanIfCmnPacketCswmanIfCmnClassifierRuleTablewmanIfCmnCpswmanIfCmnSsChMeasurementTablewmanIfCmnBsSsCo
45、nfigurationTablewmanIfCmnPrivacywmanIfCmnCryptoSuiteTablewmanIfCmnCpsServiceFlowTablewmanIfCmnOfdmPhywmanIfOfdmUplinkChannelTablewmanIfOfdmUcdBurstProfileTablewmanIfOfdmDownlinkChannelTablewmanIfOfdmDcdBurstProfileTablewmanIfBsClassifierRuleTablewmanIfSsConfigFileEncodingTablewmanIfBsNotificationwma
46、nIfBsStatCounterwmanIfBsConfigurationTablewmanIfSsNotificationFigure 2: wmanIfMib Structure ETSI ETSI TS 102 389 V1.1.1 (2005-01) 10wmanIfMib is composed of three groups: wmanIfBsObjects: This group contains managed objects to be implemented in the SNMP agent in BS. wmanIfSsObjects: This group conta
47、ins managed objects to be implemented in the SNMP agent in SS. wmanIfCommonObjects: This group contains common managed objects to be implemented in the SNMP agent in BS and SS. 5.5 wmanIfBsObjects 5.5.1 wmanIfBsSystem wmanIfBsSystem group contains system level BS managed objects. 5.5.1.1 wmanIfBsReg
48、isteredSsTable This table is indexed by BS ifIndex and wmanIfBsSsIdIndex, each entry contains the information of SS that has been registered through REG-REQ message as defined in section 6.3.2.3.7 in 3. 5.5.2 wmanIfBsPacketCs wmanIfBsPacketCs group contains BS managed objects relating to the Packet
49、CS management entity layer in figure 1 of 3. 5.5.2.1 wmanIfBsProvisionedSfTable This table is doubly indexed by SS MAC address and Service Flow ID and contains provisioned service flow profiles, Per SS. It contains the service flow attributes that have been pre-provisioned by NMS. 5.5.2.2 wmanIfBsServiceClassTable This table is provisioned and is indexed by QoS profile index. Each entry of the table contains QoS parameter set, as defined in sections 6.3.14 and
