ANSI SCTE 154-2 pdf free download

ANSI SCTE 154-2 pdf free download.SCTE-HMS-QAM-MIB.
INFORMATIVE REFERENCE DOC-IF-M-CMTS -MIB DOCS-IF-MIB TERMS AND DEFINITIONS This document defines the following terms: Management Information Base (MIB) – the specification of information in a manner that allows standard access through a network management protocol. REQUIR EMENTS This section defines the mandatory syntax of the SCTE-HMS-QAM-MIB. It follows the IETF Simple Network Management Protocol (SNMP) for defining managed objects. This mib falls under 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.
SCTE-HMS-QAM-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT—TYPE, OBJECT— IDENTITY, MODULE- IDENTITY,
enterprises, Integer32, Unsigned32
FROM SNMPv2-SMI
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
entPhysicallndex
FROM ENTITY-MIB
if Index
FROM IF-MIB
InetAddress, InetAddressType
FROM INET-ADDRESS-MIB
QAMChannelModulationFormat, QAMChannellnterleaveMode FROM SCTE-HMS-HEADENDIDENT-TC-MIB;
heDigitaiQamMlB MODULE-IDENTITY
LAST—UPDATED “200807160305Z”
ORGAN I ZAT ION
“SCTE HMS Working Group”
CONTACT- INFO
“SCTE HMS Subcommittee, Chairman
mailto:standards@scte.org
DESCRIPT ION
“This MIB module is for representing Edge QAM equipment present
in the headend (or indoor) and is supported by a SNMP agenL.
It defines QAM channel related configuration MIB objects
associated with both QAM channel’s physical and logical
characteristics.
qamChannelTable is optional for devices that are supporting
equivalent DOCSIS MIB objects.
qamConfigTable is optional and applies to devices that choose to
provide logical level configuration.
REVISION “200807160305Z”
DESCRIPTION
“Updated Objects based on Comments at 7/11/08 meeting.
1. Made QAMChannellnterleave mode an imported enumeration and used the
values from the docsiFDownChannellnterleave enumeration.
2. Changed name of QAMModulationFormat to QAMChannelModulationFormat.
3. Added unknown and other to qamChannelAnnexMode
QamChannelCommonEntry : := SEQUENCE { qamChannelComrnonOutputBw
Integer32,
qamChannelComrnonUt iii zat ion
Integer32
}
qamChannelComrnonOutputBw OBJECT-TYPE
SYNTAX Integer32
UNITS “bps”
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“The QAM channel output bandwidth or capacity.” ::= { qamChannelCommonEntry 1
qamCharinelCommonUtilization OBJECT-TYPE
SYNTAX Integer32 (—1I0..l000)
UNITS “0.1 Percent”
MAX-ACCESS read-only
STATUS current
DESCRIPT ION
“The utilization of the QAM channel in 0.1 percentage. This rate may be calculated as transport stream packets / ( transport stream packets + null packets ) . If not applicable, a value of —1 is returned.”
::= { qamChannelCommonEntry 2
qamConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF QamConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
“This table is designed to show the IP addresses configuration
for the QAM channels, optionally UDP port range, Program Number
range associated with QAM channels. Configuring these parameters
is necessary when performing session-based provisioning.
A session-based provisioning request must conform to the configurations in this table. The QAM channels within an QAM
device may be partitioned to support multiple UDP, QAM or ProgramNo ranges. Though it’s helpful to partition the QAM
channels when the total number of QAM channel increases, this is not a must. This table may also be used to show the reserved UDP.ANSI SCTE 154-2 pdf download.