ANSI SCTE 154-5-2018 pdf free download – SCTE-HMS-HEADENDIDENT TEXTUAL CONVENTIONS MIB.
sCOPE
This document is identical to SCTE 154-5 2009 except for informative components which may havebeen updated such as the title page,NOTICE text, headers and footers. No normative changes havebeen made to this document.
This document provides the branch object identifiers for each of the MIBs within the SCTE HMSDIGITAL VIDEO MIB’s (DVM) in the heDigital branch of the SCTE mibs. The SCTE HMSHEADENDIDENT-TC mib provides standard common mib text syntax for all HMS devices.
coPYRIGHT
The MIlB definition found in this document may be incorporated directly in products without furtherpermission from the copyright owner,SCTE.
NORMATIVE REFERENCE
IETF RFC 2578 SNMPv2-SMIIETF RFC 2579 SNMPv2-TCIETF RFC 2580 SNMPv2-CONFINFORMATIVE REFERENCENone
TERMS AND DEFINITIONS
TEXTUAL CONVENTIONS – Textual Conventions are a guide to standard structures used in SCTEHMS mib files. Text formats and uniform definitions are found in this file.
Management Information Base (MIB) – the specification of information in a manner that allowsstandard access through a network management protocol, specifically SNMP.
Network Timing Protocol(NTP)-NTP is a protocol designed to synchronize the clocks of computersover a network. NTP version 3 is an internet draft standard, formalized in RFC 1305,NTP version 4 isa significant revision of the NTP standard， and is the current development version, but has not beenformalized in an RFC. Simple NTP(SNTP) version 4 is described in RFC 2030.
Packet Identifier (PID) – -Packet identifier; a unique 13-bit value used to identify the type of datastored in the packet payload (see ITU-T H.222.0 / ISO/IEC13818-1).
Quadrature Amplitude Modulation (QAM) – The modulation scheme which conveys data bychanging (modulating) the amplitude of two carrier waves. These two waves are out of phase witheach other by 90 degrees and are thus called quadrature carriers.
REQUIREMENTS
This section defines the mandatory syntax of the sCTE-HMS-HEADENDIDENT-TC-MIB. It followsthe IETF Simple Network Management Protocol (SNMP) for defining managed objects. This mib fallsunder the SCTE-HMS-ROOTS mib defined by the SCTE Standards HMS Subcommittee.
To avoid issues related to device security and possible user contention, this MIB is only read-only. Device manufacturers are expected to provide device provisioning and control as a separate “out of band” service via protocols of their choice. The syntax is given below.ANSI SCTE 154-5 pdf download.