ISO/IEC 16500-8-1999 信息技术 通用数字音频-可视系统 第8部分:管理体系结构和协议

标准号：ISO/IEC 16500-8-1999
中文标准名称：信息技术 通用数字音频-可视系统 第8部分:管理体系结构和协议
英文标准名称：Information technology - Generic digital audio-visual systems - Part 8: Management architecture and protocols
标准类型：L81
发布日期：1999/12/31 12:00:00
实施日期：1999/12/31 12:00:00
中国标准分类号：L81
国际标准分类号：33.160.60;35.040
适用范围：This part of ISO/IEC 16500 describes the management architecture and protocol for managing the DAVICSystem. The DAVIC system management architecture is the TMN-based (Telecommunication ManagementNetwork) architecture defined in ITU-T Recommendation M.3010. This management architecture allows forautomatic administration, configuration, monitoring, billing, and maintenance of the Service Provider System, theDelivery System, and the Consumer System over the DAVIC S5 flows. In accordance with DAVIC 1.3.1a Part 4and ISO/IEC 16500-5, the content of these flows is based on either the CMIP protocol or the SNMP protocol,depending on the complexity of the underlying subsystem or the preference of the network provider. SNMPMIBs (Management Information Base) for managing the STU and the Server have been defined in ISO/IEC16500-5. Usage related information models have also been defined in ISO/IEC 16500-9 using both CMISE andSNMP. For managing the ATM, SDH/SONET components of the Core Network of the DAVIC Delivery System,CMISE models defined in ITU-T and ATM Forum are recommended in ISO/IEC 16500-5 subclause 10.5.3.Taking into account that the current DAVIC specification for the Access Network is ATM-based 1, this Part ofISO/IEC 16500 defines CMISE information models for managing the DAVIC Access Network and servicerelateddata in the Delivery System. In the future, if DAVIC specifications allow altenative access technologies(such as IP-based), additional system management information models (such as SNMP MIB) may be needed. Themanagement of the coexistence of different access network technologies, using different protocols, could beachieved through interworking tools (i.e., interworking between CMIP and SNMP) as described in subclause 6.4.Tutorial information on a protocol-independent modeling technique is also provided in an informative annex.