1、 This is a Registered Disclosure Document prepared by the proponent identified below. It has been examined by the appropriate SMPTE Technology Committee and is believed to contain adequate information to satisfy the objectives defined in the Scope, and to be technically consistent. This document is
2、NOT a Standard, Recommended Practice or Engineering Guideline, and does NOT imply a finding or representation of the Society. Errors in this document should be reported to the proponent identified below, with a copy to engsmpte.org. All other inquiries in respect of this document, including inquirie
3、s as to intellectual property requirements that may be attached to use of the disclosed technology, should be addressed to the proponent identified below. Proponent contact information: Yoshihisa Gonno Sony Corporation, PSNC 4-14-1 Asahicho, Atsugi Kanagawa, 243-0014 Japan E-mail ygonnosm.sony.co.jp
4、 Page 1 of 44 pages RDD 4-2005 Copyright 2005 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 595 W. Hartsdale Ave., White Plains, NY 10607 (914) 761-1100 Approved June 14, 2005 SMPTE REGISTERED DISCLOSURE DOCUMENT Pro-AV MIB-1 A Professional Audio/Visual Product Simple Network Management
5、Protocol Management Information Base RDD 4-2005 Page 2 of 44 pages 1 Scope This document defines a Management Information Base (MIB) for Professional AV products as Pro-AV MIB-1 based upon Sony implementations. The MIB defines the items managed by the Simple Network Management Protocol (SNMP) and co
6、mprises variables that maintain the status of equipment. Provisions of the Pro-AV MIB-1 provides capability for any company to create a private node, contents can be individually managed by that company. 2 Normative references RFC 1155, Structure and Identification of Management Information for TCP/
7、IP-based Internets RFC 1157, A Simple Network Management Protocol RFC 1213, Management Information Base for Network Management of TCP/IP-based internets: MIB-II RFC 1903, Textual Conventions for Version 2 of the Simple Network Management Protocol RFC 1907, Management Information Base for Version 2 o
8、f the Simple Network Management Protocol RFC 2578, Structure of Management Information Version 2 RFC 2579, Textual Conventions for SMIv2 ITU-T Recommendation X.731, State Management Function ITU-T Recommendation X.733, Alarm Reporting Function 3 Definitions 3.1 Agent: A software module that performs
9、 the network management functions requested by network management stations. An agent module may be implemented in any network element that is to be managed, such as a host, bridge, or router. Agents and network management stations communicate by means of SNMP. 3.2 Management Information Base (MIB):
10、In the context of SNMP, this term is used in two contexts: (1) A structured set of data variables, called objects, in which each variable represents some resource to be managed. Each agent in a network maintains a MIB for the network element on which it executes. (2) The definition of a related coll
11、ection of objects that represent some related collection of resources to be managed. 3.3 Object: A data variable that represents some resource or other aspect of a managed device; also referred to as a managed object. 3.4 Object Identifier (OID): Uniquely identifies an object within a MIB. The form
12、of an object identifier is a sequence of numbers separated by periods. This sequence defines the location of an object in the tree-structured MIB of which it is a part. 3.5 Trap: An unsolicited message sent by an agent to a management station. The purpose is to notify the management station of some
13、unusual event. RDD 4-2005 Page 3 of 44 pages 4 Pro-AV MIB-1 Overview Pro-AV MIB-1 has a structure that can support monitoring of various products. Also, items and structures are simplified as much as possible in order to be able to easily implement for various categories of products. The Structure o
14、f Management Information (SMI) for the MIB definitions shall comply with RFC 2578 (SMIv2). The items composing the MIB should be grouped so that they can be managed in three sets of information as follows: Common information Category common information Individual product information This document de
15、fines the common information. NOTE This MIB can be applied under each individual company ID, after setting an appropriate OID number for Pro-AV MIB-1 in parallel to existing OIDs under the company OID. 5 Pro-AV MIB-1 Structure The composition of Pro-AV MIB-1 structure shall be as follows. Figure 1 P
16、ro-AV MIB-1 Overall Structure 5.1 Common Definitions (proV1MIB) Definitions commonly used in “Common MIB“, “Category MIB“ and “Product MIB“ shall be entered. Consequently, the “TEXTUAL-CONVENTION“ macro defining data expression is entered. This is not implemented as objects, but provided separately
17、as a MIB definition file. An OID shall be given to the module as a Module Identifier by the rule of SMI. Pro-AV MIB-1 (xxxx) proV1Common (2) proV1Category (3) proV1Product (4) category-1 category-2 product-1 product-2 Common MIB Product MIB proV1MIB(1) Common Definitions Category MIB iso(1)org(3)dod
18、(6)internet(1)private(4) enterprises(1) “Company ID” (xxx) RDD 4-2005 Page 4 of 44 pages 5.2 Common MIB (proV1Common) The variable items mounted in all products are defined in the Common MIB. The product ID information (including module information), information concerning the SNMP agent, error tabl
19、e, and trap definitions shall be included in the Common MIB. Figure 2 Common MIB (proV1Common) Structure 5.3 Category MIB (proV1Category) The common variable items for each category are defined in the Category MIB. When a new Category MIB is created, it shall be added positioned below this proV1Cate
20、gory. This shall be individually defined and managed by each company. 5.4 Product MIB (proV1Product) The variable items for each product are defined in the Product MIB. Product MIBs shall be prepared when defining variable items unique to a product that are not defined by the Common MIB or Category
21、MIB. When a new Product MIB is created, it is added below this proV1Product. This shall be individually defined and managed by each company. 6 Individual items in Common Definitions The Common Definitions contain definitions of information common to the “Common MIB“, “Category MIB“, and “Product MIB
22、“. Consequently, the “TEXTUAL-CONVENTION“ macro defining data expression is entered. The TEXTUAL CONVENTION is a macro used to clearly express data for which the meaning may be different even though the data type is the same. For example, when there are frequencies and cycle times as numerical infor
23、mation, both may be expressed as integers, but the values shall have different meanings for each type. The following TEXTUAL CONVENTION shall be defined for such purposes as clarifying these differences. (1) Local time This expresses the local time information as a character string with the format “
24、YYYY/MM/DD hh:mm:ss:ff GMT+HH:MM“. The ff positioned after the seconds (ss) expresses the frame number, and proV1Common(2) proV1Category(3) proV1Product(4) proV1ProductInfo proV1AgentInfo proV1ErrorStatus proV1Trap Common MIB Pro-AV MIB-1 (xxxx) proV1MIB(1) SNMP Agent Information Error Status Tables
25、 Trap Definition Product ID Information RDD 4-2005 Page 5 of 44 pages the section from GMT onward expresses the time difference from Greenwich Mean Time (GMT). The + may be replaced by . (2) Cycle time This expresses a cycle time as an integer in the range 0-2147483647. (3) Frequency This expresses
26、a frequency as an integer in the range 0-2147483647. (4) Scanning line number This expresses the scanning line number as an integer in the range 0-2147483647. (5) Frame number This expresses the frame number as an integer in the range 0-2147483647. ProV1TimeStamp := TEXTUAL-CONVENTION STATUS current
27、 DESCRIPTION “textual information for printable timestamp(local time). example: 2001/08/29 22:30:00:00 GMT+09:00“ SYNTAX DisplayString (SIZE(32) ProV1Cycle := TEXTUAL-CONVENTION STATUS current DESCRIPTION “textual information for cycle time unit: sec.“ SYNTAX Integer32 (02147483647) ProV1Frequency :
28、= TEXTUAL-CONVENTION STATUS current DESCRIPTION “textual information for frequency unit: /sec.“ SYNTAX Integer32 (02147483647) ProV1ScanningLineNumber := TEXTUAL-CONVENTION STATUS current DESCRIPTION “textual information for scanning line number unit: /sec“ SYNTAX Integer32 (02147483647) ProV1FrameN
29、umber := TEXTUAL-CONVENTION STATUS current DESCRIPTION “textual information for frame number unit: /sec“ SYNTAX Integer32 (02147483647) RDD 4-2005 Page 6 of 44 pages (6) Device status This expresses the device ON/OFF status as unknown (1), down (2) or up (3). The first character of the name of the T
30、EXTUAL CONVENTION shall always start with the capital letter P. (ProV1Abcdef). 7 Individual items in Common MIB The Common MIB shall include the following items and item tables. ProV1Status := TEXTUAL-CONVENTION STATUS current DESCRIPTION “textual information for device status.“ SYNTAX INTEGER unkno
31、wn(1), down(2), up(3) RDD 4-2005 Page 7 of 44 pages (1) proV1ProductInfo proV1AgentInfo proV1ErrorStatus proV1Trap Common MIB Product ID Information SNMP Agent Information Error Status Tables Trap Definition Product ID Information Table Product Index No. Device ID Manufacturer Model Name Destination
32、 Serial Number Product Category Product Version Model Name Suffix Product Version Suffix Module Information Table Product Index No. Module Index No. Module Type Module Name Module Version Module Name Suffix Module Version Suffix MIB Version Information Product MIB Table (MIB ObjectID) Category MIB T
33、able (MIB ObjectID) Trap Destination Address Table Index No. IP Address Entry Status Items Included in Trap Product Index No. Device ID Manufacturer Model Name Destination Serial Number Product Category Product Version Model Name Suffix Product Version Suffix Error Index No. Error Level Error Code E
34、rror Description Error Time Local Clock Time Error/Warning Information Table Product Index No. Error Index No. Error Level Error Code Error Description Error Time Equipment Status Information table Product Index No. Alarm Level Operational State Usage State Figure 3 Items included in Common MIB RDD
35、4-2005 Page 8 of 44 pages Items are read-only status unless otherwise stated. Also, items that take DisplayString (alphanumeric) as the variable type shall never include the following five characters: , does not take a value. Note *6) XXX: The Company ID. e.g. 122 for Sony Corporation. Note *7) XXXX
36、: The Company Name. e.g. sony Note *8) XXXX: The number assigned within the company. e.g. 8501 has been assigned for Sonys Pro-AV MIB-1. Note *9) (Reserved) Can be defined freely by each company. 7.1 Product ID Information The Product ID Information comprises the ID information table for specifying
37、the product and the module information table for acquiring the information for the modules included in the product. 7.1.1 Product ID Information Table Stores the Product ID Information in table format. RDD 4-2005 Page 11 of 44 pages proV1ProdIdInfoTable proV1ProdIdInfoEntry (1) Index No. proV1ProdId
38、InfoIdx Integer32 (2) Device ID proV1ProdIdInfoDevId DisplayString (3) Manufacturer proV1ProdIdInfoManufact DisplayString (4) Model Name proV1ProdIdInfoModel DisplayString (5) Destination proV1ProdIdInfoDest DisplayString (6) Serial Number proV1ProdIdInfoSN DisplayString (7) Product Category proV1Pr
39、odIdInfoCat INTEGER (8) Product Version proV1ProdIdInfoVer Integer32 (9) Model Name Suffix proV1ProdIdInfoModelSuffix DisplayString (10) Product Version Suffix proV1ProdIdInfoVerSuffix DisplayString Stand-alone Product: If the product is a stand-alone product that is connected as a stand-alone unit
40、to the network, this table has only one entry. Table 2 Example of Stand-alone Product Connected to Network as Stand-alone Unit Index No. Device ID Manufacturer Model Name Destination Serial Number Product Category Product Version 1 11 XXXX DXX-500 XX 100102 1100 110 Proxy Product/System Product: Whe
41、n the product has stand-alone products underneath it, and send/receive information to/from the network in place of the stand-alone products, the product also has entries of stand-alone products such as the following. DXX-5 DXX-500 DXX-500 DXX-550 LAN Internal bus or internal LAN Index.1 Index.2 Inde
42、x.3 Index.4 Also responsible for monitoring thestand-alone products underneathand for notification to the upperlevel. Figure 4 Proxy product/system product RDD 4-2005 Page 12 of 44 pages Table 3 Example in which the product has stand-alone products underneath it Index No. Device ID Manufacturer Mode
43、l Name Destination Serial Number Product Category Product Version 1 01 XXXX DXX-5 XX 110012 9000 200 2 11 XXXX DXX-500 XX 100102 1100 110 3 12A XXXX DXX-500 XX 100103 1100 110 4 13A XXXX DXX-550 XX 100109 1100 130 (1) Index No. This is an index number for specifying the entries in this table. (proV1
44、ProdIdInfoIdx)(variable type = Integer32) (2) Device ID A device number or name is entered that is set so that the customer can identify the product. It is assumed that the device ID is either set numerically from the control panel of the product or that a character string is set using http or telne
45、t through the network. Also, it is mounted so that the Device ID in the first line (instance) of this table takes the same value as sysName in the MIB-II System Group. (proV1ProdIdInfoDevId) (variable type = DisplayString, maximum 255 characters) (3) Manufacturer The vendor name is entered. (proV1Pr
46、odIdInfoManufact) (variable type = DisplayString, maximum 64 characters) (4) Model Name The model name is entered. Also, it is mounted so that the Model Name in the first line (instance) of this table takes the same value as sysDescr in the MIB-II System group. (proV1ProdIdInfoModel) (variable type
47、= DisplayString, maximum 255 characters) (5) Destination The destination is entered. (proV1ProdIdInfoDest) (variable type = DisplayString, maximum 64 characters) (6) Serial Number The serial number is entered. (proV1ProdIdInfoSN) (variable type = DisplayString, maximum 64 characters) (7) Product Cat
48、egory Category type groups are defined in table 4. Only the major categorization is defined. The detail categorization shall be specified and managed by each company. (proV1ProdIdInfoCat) (variable type = INTEGER) RDD 4-2005 Page 13 of 44 pages Table 4 Product Category No. Category Type Group Exampl
49、e of Product Categories 10001999 Storage Products VTR, DISK RECORDER, DATA RECORDER 20002999 Processing Products ROUTER, SWITCHER, EFFECTS, PERIPHERAL, CONTROLLER, CODEC, EDITOR 30003999 Camera Products STUDIO CAMERA, SECURITY CAMERA, CAMCORDER 40004999 Display Products MONITOR, FLAT PANEL MONITOR, PROJECTOR, LARGE DISPLAY 50005999 Audio Products AUDIO MIXER, CD, DAT, MIC 60006999 AV Other Products PRINTER 70007999 Test and Measurement WFM, SG, MPEG TEST SYSTEM 80008999 PC and Network Products PC BASED PRODUCT, PC SERV
