| Target Namespace | http://www.wsmr.army.mil/RCC/schemas/MDL |
|---|---|
| Element and Attribute Namespaces |
|
| Schema Composition |
|
| Documentation |
TODO List
1. After constraints are standardized, add constraint for Package Time Measurement Scoping Rules, in IRIG 106 Chapter 24. 2. ExternalScript needs to be standardized. 3. For the TrafficFilterCondition element we may want to add other types of 'symbolic' conditions, like "match packet against a range of DSCPs (class)" "match packet against an IPv4 header field value" "match packet against an IPv6 header field value" "match packet against a TCP header field value" "match packet against a UDP header field value" "match packet against a ICMP header field value" 4. The HandoffRule element is a work in progress and may require some refinement. |
| Prefix | Namespace |
|---|
| Name | MDLRoot |
|---|---|
| Type | MDLRootType |
| Nillable | no |
| Abstract | no |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AggregateRateType |
|---|---|
| Abstract | no |
| Documentation |
The AggregateRate element describes common data rates for
items throughout a TmNS-based system (e.g., bit rates, sample rates,
packet rates, Package rates, TmNSDataMessage rates, etc.). The goal of
providing these elements is to support the estimation of aggregate data
rates at various points in the TmNS-based system(s) resulting from a
particular configuration. For example, the sample rates related to
individual measurements may be aggregated into bit rates and Package
rates, which may be aggregated into bit rates and TmNSDataMessages
rates. TmNSDataMessages rates may be aggregated into bit rates and
packet rates for transport-related items (e.g., paths, network
connections, and network interfaces).
The AverageRate element describes the average data rate in the units of measure specified by the UnitRef or BaseUnit element. The PeakRate element describes the peak data rate in the units of measure specified by the UnitRef or BaseUnit element. The UnitRef or BaseUnit element describes the units of measure for the AverageRate and PeakRate. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AnalogAttributesType |
|---|---|
| Abstract | no |
| Documentation |
The AnalogAttributes element describes the properties of data
when it exists in an analog form. An applicable scenario would be
describing the analog output of a sensor that is connected to the
input of an analog-to-digital converter on a DAU. The following
elements describe only the analog signal and not the methods by which
it is to be acquired or processed.
The SignalRange element, of type mdl:ConditionParameters, describes the range of values over which an analog signal exists. For example, the range of a temperature sensor could be -40C to 120C. The Resolution element, of type mdl:ConditionParameters, describes the smallest measurable increment between analog signal values. For example, the resolution of a temperature sensor could indicate that temperature changes of no larger than 0.1C may go undetected. The FilterType element is used to describe the filter used by the measurement. If a user has no desired filter, the value shall be "Negotiated", and the DAU shall populate the element with the actual filter during negotiation. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AntennasType |
|---|---|
| Abstract | no |
| Documentation | The AntennasType element is the top-level container for an unbounded list of Antenna elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AntennaType |
|---|---|
| Abstract | no |
| Documentation |
The Antenna element serves as the physical association of an
antenna, its antenna control unit, receivers, transmitters and radios.
An antenna itself is not configured via MDL.
The Name element, of type xsd:token, contains a human readable name identifier for the antenna. The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the Device. The SerialID element, of type xsd:string, contains the model number of the Device. The ACU element, of type TmNSAppRefsType, contains a TmNSAppRef which identifies the antenna control unit (if present) for this antenna. The SSTTxs element, of type TmNSAppRefsType, contains a list of TmNSAppRef elements which identify the SST transmitter elements that are physically connected to this antenna. The SSTRxs element, of type TmNSAppRefsType, contains a list of TmNSAppRef elements which identify the SST receiver elements that are physically connected to this antenna. The Radios element, of type TmNSAppRefsType, contains a list of TmNSAppRef elements which identify the TmNSRadio elements that are physically connected to this antenna. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AssetAssociationsType |
|---|---|
| Abstract | no |
| Documentation |
The AssetAssociations element is used to describe the logical
associations between ground and test article radio and SST elements
for a particular test mission.
The SSTAssociation element, of type AssetAssociationType, represents a logical association between an SST receiver and transmitter. The RadioAssociation element, of type AssetAssociationType, represents a logical association of TmNSRadio components, whether on the ground or on the test article. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | AssuredCapacityType |
|---|---|
| Abstract | no |
| Documentation | The Value element, of type ValueType, specifies the nominal portion of the overall network capacity to be allocated for all data associated with this Radio Link under steady state conditions. The units are specified using either a UnitRefType or a BaseUnitEnum. The Timeout element, of type xsd:unsignedLong, specifies the amount of time, in microseconds, that must pass with the transmission queues empty for the Radio Link before Link Management can reduce allocations below AssuredCapacity. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | BlacklistOfIPAddressesType |
|---|---|
| Abstract | no |
| Documentation |
The BlacklistOfIPAddresses element is a container for an unbounded list of
BlacklistIPAddress elements.
The BlacklistIPAddress element, of type IPAddress, defines an IP Address that is prohibited from being routed through a TSSTunnel. This element is unbounded. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | BlackoutPeriodType |
|---|---|
| Abstract | no |
| Documentation |
The BlackoutPeriod element contains parameters to describe a period
of time relative to the Epoch which the TmNSLinkManager manageable
app is not permitted to provide TxOp assignments to TmNSRadios.
The StartUSec element of type xsd:unsignedLong, specifies the start time of the Blackout period in microseconds relative to the start of an Epoch. The StopUSec element of type xsd:unsignedLong, specifies the stop time of the Blackout period in microseconds relative to the start of an Epoch. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | BlackoutScheduleType |
|---|---|
| Abstract | no |
| Documentation | The BlackoutSchedule element is a container for an unbounded list of BlackoutPeriod elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CalibrationPairsType |
|---|---|
| Abstract | no |
| Documentation | The CalibrationPairsType element is the top-level container for an unbounded list of CalibrationPair elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CalibrationPairType |
|---|---|
| Abstract | no |
| Documentation | The InputValue element, is a complex element of type mdl:ValueUnit that describes the input during calibration of the device. The OutputValue element, is a complex element of type mdl:ValueUnit that describes the output for a given input during calibration of the device. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CalibrationType |
|---|---|
| Abstract | no |
| Documentation | The Calibration element in a Device is a container for individual input and output pairs used during the calibration of the Device as well as the date of the last calibration. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CapabilitiesType |
|---|---|
| Abstract | no |
| Documentation | The CapabilitiesType element contains all the defined capabilities of a NetworkNode, its Modules, and their Submodules. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CaptureCapabilitiesType |
|---|---|
| Abstract | no |
| Documentation | The CaptureCapabilitiesType element is the top-level container for an unbounded list of CaptureCapability elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CaptureCapabilityRefsType |
|---|---|
| Abstract | no |
| Documentation | The CaptureCapabilityRefsType element is the top-level container for an unbounded list of CaptureCapabilityRefType elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CaptureCapabilityRefType |
|---|---|
| Abstract | no |
| Documentation | The CaptureCapabilityRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a CaptureCapability element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CaptureCapabilityType |
|---|---|
| Abstract | no |
| Documentation |
The CaptureCapabilityType describes the capture capabilities for a specific
type of bus data.
The ProperName element gives the proper name corresponding to this type of capture. For example, using a proper name of ARINC429 would mean that the CaptureCapability element was applicable to ARINC429 bus messages. The DataStructureRef element contains a reference to the data structure corresponding to how the capturing device perceives the captured data. The CaptureMode element states whether the capturing device is capable of filtering. The absence of filtering is defined as "AllBusCapture", and the presence of filtering is defined as "SelectiveBusCapture". The FilteringSchemes element contains a list of the possible filtering schemes usable by the capturing device for filtering the captured bus data. The PackagingSchemes element contains a list of the possible packaging schemes usable by the capturing device for packing the captured bus data. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ChildRefsType |
|---|---|
| Abstract | no |
| Documentation | The ChildRefsType element is the top-level container for an unbounded list of ChildRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ChildRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a ChildRef shall refer to the ID attribute of a Module, SubModule, DeviceModule, or DeviceSubModule element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ChildrenType |
|---|---|
| Abstract | no |
| Documentation | The Children element describes generic parent-child or master-slave relationships among the modules of a NetworkNode or between a NetworkNode and remote non-networked Device elements that require configuration or control by the NetworkNode. The Children element contains a list of one or more Child elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ChildType |
|---|---|
| Abstract | no |
| Documentation | The Child element describes a single parent-child or master-slave relationship. The parent or master is the element containing the Children element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ClassChoiceType |
|---|---|
| Abstract | no |
| Documentation | The ClassChoiceType may contain either a PRIO element, of type PRIOClassType, or an HTB element of type HTBClassType for describing the class of the queue construct. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | CodecPrioritiesType |
|---|---|
| Abstract | no |
| Documentation | The CodecPriorities element contains a list of one or more CodecPriority elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < CodecPriorityType (by extension) |
|---|---|
| Sub-types: | None |
| Name | CodecPriorityType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConditionalBlockType |
|---|---|
| Abstract | no |
| Documentation |
The ConditionalBlockType is used to define a conditional block which
determines the measurement that will be output from a data processing
function.
The If element contains the initial condition and a result to output if the condition is true. The ElseIf element contains a condition to test if none of the previous elements contained a condition that evaluated to True. A result is output if the condition is True. This element is optional as well as unbounded. The Else element contains the resulting algorithm if all previous conditions were False. This element is optional, so that a measurement may only conditionally result from the function. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConditionalType |
|---|---|
| Abstract | no |
| Documentation |
The ConditionalType is used to define a conditional assignement which
determines the measurement that will be output from a data processing
function.
The Condition element contains a condition, which shall return True/False. The Result element contains the result to be returned if the condition is True. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConditionParametersType |
|---|---|
| Abstract | no |
| Documentation | The ConditionParameters element is a container for zero or more ConditionParameter elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConditionParameterType |
|---|---|
| Abstract | no |
| Documentation |
The ConditionParameter element describes a value or bound of
values for the element containing the ConditionParameter element.
Multiple ConditionParameter elements can be used to describe ranges of
values. The ConditionParameter shall contain a ConditionValue,
and either a UnitRef or an BaseUnit, but not both.
The ConditionValue element, of type mdl:FlexibleLong or xsd:double, specifies the value to be compared against using the operation described by the ConditionOperation element. For example, if the ConditionValue element value is "0b10" and the ConditionOperation element value is greater than then the values being described by the ConditionParameter element are greater than the binary value of 0b10 (i.e., 2 in decimal). The UnitRef and BaseUnit elements describe the units of measure for the ConditionParameter. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConnectorsType |
|---|---|
| Abstract | no |
| Documentation | The ConnectorsType element is the top-level container for an unbounded list of Connector elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ConnectorType |
|---|---|
| Abstract | no |
| Documentation | The Connector element describes a physical connector on a NetworkNode or a module and contains one or more Pin elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataAttributesType |
|---|---|
| Abstract | no |
| Documentation |
The DataAttributes element describes the analog and digital
attributes of a measurement on a Test Article.
The PCMMeasurementRef is used for TMATS-described PCM stream measurements to indicate the source of the bus measurement. The UnitRef and BaseUnit elements describe the instrumentation units of measure for the Measurement. The Calibration element, of type mdl:CalibrationType, is a container for individual input and output pairs used during the calibration of the DAU as well as the date of the last calibration. The Uncertainty element describes the uncertainty of the measurement through a confidence level over a specified confidence interval. The AnalogAttributes element describes the properties of the measurement when it exists in an analog form. The DigitalAttributes element describes the properties of data when it exists in a digitally encoded form. Note that if AnalogAttributes are used to define a measurement's signal characteristics and DigitalAttributes are used to define a measurement's sample rate along with its constraints, the sample rate should be used by a component during validation and should take precedence over the AnalogAttributes for determining the configuration. This allows for purposeful over or undersampling defined by the user, while still documenting the signal's actual properties. The TimeAttributes element describes the properties of a timestamp as a measurement. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataMapsType |
|---|---|
| Abstract | no |
| Documentation | The DataMaps element describes the mapping of digital data (e.g., measurement data) to defined fields that can carry the data (e.g., package fields). The individual mappings of digital data into fields is described by the contained DataWordToFieldMap elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataProcessingType |
|---|---|
| Abstract | no |
| Documentation | The DataProcessingType contains a list of reusable data processing functions and a set of mappings from input measurements to result measurements using those functions. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamMessageRefType |
|---|---|
| Abstract | no |
| Documentation | The DataStreamMessageRef element indicates the DataStreamMessage from which the data is extracted. The DataStreamMessageRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a DataStreamMessage within the same MeasurementDomain. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamMessagesType |
|---|---|
| Abstract | no |
| Documentation | The DataStreamMessagesType element is the top-level container for an unbounded list of DataStreamMessage elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamMessageType |
|---|---|
| Abstract | no |
| Documentation |
The DataStreamMessage element defines a message type
for the described DataStream element. This message type
definition identifies the message's data structure (i.e., locations
that carry data), any filters that apply to that specific structure,
and the mapping of data content to the defined data structure.
The Size element, of type mdl:ValueUnitType, describes the size or length of the described DataStreamMessage element. The units for this element shall be in units of digital data lengths such as bits or bytes. The MessageRate element, of type mdl:AggregateRateType, describes the committed rate (AverageRate) and the peak rate at which the containing message will appear on the bus. The DataStructureRef element, of type mdl:DataStructureRefType, describes the format and location of data carrying fields within the described DataStreamMessage element. The assignment of digital data values (e.g., measurement data) to the field locations is specified using the DataMap element. The FilterMode element defines the default behavior of the CaptureFilters list. If the FilterMode is set to PassAll, then the stream will default to allowing all bus messages, and each CaptureFilter will be an exception that blocks any messages that met its conditions. If the FilterMode is set to RejectAll, then then stream will default to blocking all bus messages, and each CaptureFilter will be an exception that allows any messages that met its conditions to pass through the filter. The CaptureFilters element contains the filters that describe what bus messages should be accepted by this data stream. Note that these filters do not describe how the filtering must be done, but only what the result of the filters must be. The MeasurementSelectors element contains the selectors that describe what data from the bus messages should be extracted as measurements. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamRefsType |
|---|---|
| Abstract | no |
| Documentation | The DataStreamRefsType element is the top-level container for an unbounded list of DataStreamRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a DataStreamRef must refer to the ID attribute of a DataStream. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamsType |
|---|---|
| Abstract | no |
| Documentation | The DataStreams element is a container for one or more DataStream elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStreamType |
|---|---|
| Abstract | no |
| Documentation |
The DataStream element describes a streaming data format used
to transfer encoded data on a Test Article Network. Typically, access
to the described data stream is dependent upon a set of selected
technologies (hardware and/or software) to implement the specified
protocols, interfaces, and formats of the data stream. The DataStream
element describes an instantiation of a selected data stream
technology that appears on a Test Article Network as a means of
transporting data (e.g., measurement data). Each technology-specific
description within the DataStream element will indicate how data is
organized into defined data structures and formats. Furthermore, each
technology-specific description within the DataStream element will
specify how individual data units can be extracted and aggregated into
sampled measurements. Potentially, these sampled measurements may be
refined and processed before they are published as measurement data in
TmNSDataMessages.
The Name element, of type xsd:token, describes the textual identifier of the described DataStream element. The XML processor will remove line feeds, carriage returns, tabs, leading and trailing spaces, and multiple spaces from all elements of type xsd:token. The ReferenceDocumentation element, of type xsd:string, specifies an external document or other source material that provides more details, descriptions, or specifications regarding the formats and properties of the described DataStreamMessages element. The DataRate element, of type mdl:ConditionParameters, contains any number of ConditionParameter elements and describes the average number of transferred digital data units per unit of time for a described DataStream element. The BusSpeed element, of type xsd:double, describes the line rate of the bus media in units of Hertz. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a DataStructureFieldRef must refer to the ID attribute of a DataStructureField within the same MeasurementDomain. The Index is used to refer to a particular repetition of the field within the DataStructure. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldSetRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a DataStructureFieldSetRef must refer to the ID attribute of a DataStructureFieldSet within the same MeasurementDomain. The Index is used to refer to a particular repetition of the field set within the DataStructure. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldSetsType |
|---|---|
| Abstract | no |
| Documentation | The DataStructureFieldSetsType element contains is the top-level container for an unbounded list of DataStructureFieldSet elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldSetType |
|---|---|
| Abstract | no |
| Documentation |
The DataStructureFieldSet element describes a set of
DataStructureField elements. When mapping to a DataStructureFieldSet
element using a DataWordToFieldMap Element it is implied that the
left-most bits of the DataWord element go into the left-most bits of
the DataStructureFieldSet element.
Within a DataStructureFieldSet, all DataStructureFields shall contain the same value for FieldRepetitions. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldsType |
|---|---|
| Abstract | no |
| Documentation | The DataStructureFieldsType element contains is the top-level container for an unbounded list of DataStructureField elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureFieldType |
|---|---|
| Abstract | no |
| Documentation |
The DataStructureField element describes a location in a DataStructure
that can carry data.
The FieldRepetitions element, of type xsd:nonNegativeInteger, describes the number of repetitions for this DataStructureField. If the value of this element is equal to 1, the DataStructureField element being described occurs only once in the containing DataStructure element. If the value of this element is greater than 1, the corresponding DataStructureField element has multiple locations, each offset by the number of bits indicated by the value of the FieldOffsetIncrement element from the previous location. If the value of this element is equal to 0, the DataStructureField element repeats indefinitely. The FieldOffsetIncrement element, of type mdl:ValueUnitType, specifies the number of digital data units to increment from one location of this DataStructureField element to a subsequent location. The units for this element shall be in units of digital data lengths such as bits or bytes. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureRefType |
|---|---|
| Abstract | no |
| Documentation | The DataStructureRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a DataStructure element within the same MeasurementDomain. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructuresType |
|---|---|
| Abstract | no |
| Documentation | The DataStructures element in a MeasurementDomain element is a container for one or more DataStructure elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataStructureType |
|---|---|
| Abstract | no |
| Documentation | The DataStructure element describes a DataStructure, which is a set of data fields that make up the DataStructure and can carry data. The data fields do not need to cover all bits in a DataStructure, and may overlap. The DataStructure elements are contained in the DataStructures container element in a MeasurementDomain. They are defined at the MeasurementDomain scope and referenced within PackageDefinitions and DataStreams. A DataStructure may be used by multiple PackageDefinitions and DataStreams in a MeasurementDomain. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataWordToFieldMapType |
|---|---|
| Abstract | no |
| Documentation |
The DataWordToFieldMap element describes how digital data is
broken down or aggregated into data words and mapped into fields
(e.g., package fields). Each DataWordToFieldMap element contains
exactly one DataWord element and either a DataStructureFieldRef element
or a DataStructureFieldSetRef element.
The FillValue element, of type mdl:FlexibleLong, describes a constant value string that will be used to fill unused space in a field (defined by a DataStructureFieldRef element or a DataStructureFieldSetRef element). The unused space appears when a DataWord element is smaller in size than the field it is mapped to in the described DataWordToFieldMap element. The value string of the FillValue element shall appear only an integer number of times. Any remainder space that cannot contain the entire FillValue element's value string will be indeterminate. The TimeOrderEnum element describes the temporal ordering of instances of digital data (e.g., measurement data) within a field (defined by a DataStructureFieldRef element or a DataStructureFieldSetRef element). The TimeOffset and TimeOffsetIncrement elements, of type xsd:unsignedInt, are 32-bit values in units of nanoseconds that may be used to describe time offsets of one or more samples of a packaged Measurement, where the time offsets with respect to the Package header time are known a-priori. If the time offsets are not known a priori, the TimeOffset and TimeOffsetIncrement are not used. Given a Message header timestamp, Tm, a Package header time delta, Tp, an a-priori TimeOffset of To, and an a-priori TimeOffsetIncrement of Ti, the time at which the k-th sample of a Measurement from the given Package was collected is given by the equation T = Tm + Tp + To + k*Ti |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DataWordType |
|---|---|
| Abstract | no |
| Documentation |
The DataWord element describes how values from Syllable
elements are masked and packed into a DataWord element that is carried
in DataStructureField elements and/or DataStructureFieldSet elements.
The DataWord element describes a set of contiguous bits that contain
data. The specification of the mappings in the DataWordToFieldMap
element results in a full description of how data (e.g., measurement
data) is carried in a set of fields (e.g., a PackagePayload).
The DataWordWidth element describes the width or length of the DataWord element. The DataWordWidth element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. The Measurement element that is referenced by the MeasurementRef element provides an interface through which input data (e.g., measurement data) is transferred to be placed into a DataWord element. See SyllableType documentation for details on the encoding/decoding process. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DenominatorsType |
|---|---|
| Abstract | no |
| Documentation | The DenominatorsType element is the top-level container for an unbounded list of Denominator elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DerivedUnitType |
|---|---|
| Abstract | no |
| Documentation |
The DerivedUnit element describes a unit of measure in terms
of fractional expressions consisting of standard units of measure.
Each DerivedUnit element description can contain a name, symbol and
additional details of the meaning of the unit of measure. The terms
of the numerator and denominator of a DerivedUnit element can be
assigned units from the BaseUnitType or other previously defined
DerivedUnit elements.
The Symbol element, of type xsd:token, describes a textual symbol associated with the unit of measure defined by the containing DerivedUnit element. Common examples include "J" for Joule and "N" for Newton. The Symbol is a required element and must be unique across all DerivedUnit Symbols in the MDLRoot element. The Name is a required element and must be unique across all DerivedUnit Names in the MDLRoot element. The XML processor will remove line feeds, carriage returns, tabs, leading and trailing spaces, and multiple spaces from all elements of type xsd:token. DerivedUnit elements shall not be created to redefine or replace existing BaseUnit definitions. DerivedUnit elements should use as few BaseUnit as possible to achieve the required result. For example, if units of degrees per second squared is required, the derived unit should be based on the RadianPerSecondSquared SIUnit rather than using the Radian SIUnit and the Second SIUnit The AddedConstant element, of type xsd:double, describes a constant value to be added to the fraction described by the Numerator and Denominator elements. The Numerator and Denominator elements are of type mdl:UnitTermType. The described DerivedUnit is evaluated as the result of dividing the product of all Numerator units by the product of all Denominator units. |
| Relations |
Used in:
Referenced by:
|
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceAutoDiscoveryType |
|---|---|
| Abstract | no |
| Documentation | The DeviceAutoDiscovery element describes various ways a TmNSConsolidatedManager may perform device auto discovery. The BroadcastIPAddress may be used to describe a broadcast ping configuration. The PingSweepRanges element may be used to describe individual IP addresses, or ranges of IP addresses to which a ping query may be sent. The DeviceAutoDiscoveryPeriod element of type mdl:ValueUnitType describes a time interval (generally in seconds) at which the device auto discovery procedure is performed. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceModulesType |
|---|---|
| Abstract | no |
| Documentation | The DeviceModulesType element is the top-level container for an unbounded list of DeviceModule elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceModuleType |
|---|---|
| Abstract | no |
| Documentation |
The DeviceModule element describes the properties of module, card,
slot, or slice in a non-network-connected Device.
The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the module. The SerialID element, of type xsd:string, contains the model number of the module. The InventoryID element, of type xsd:token, describes the inventory identifier of the device. The Position element, of type xsd:nonNegativeInteger describes the slot number or the position of the module in a stack of modules. The PositionsOccupied element describes the size of the Module in terms of the number of positions or slots occupied by the module. The Sensitivity element, is a complex element of type mdl:ConditionParameters that describes the datasheet sensitivity (with units) of the module or sensor. The Calibration element in a DeviceModule is a container for individual input and output pairs used during the calibration of the Device as well as the date of the last calibration. The Children element describes generic parent-child or master-slave relationships among the modules of a NetworkNode, between a NetworkNode and remote non-networked Device, or between non-networked Device elements. The relationship is intended to describe those where the parent is responsible for configuration or control of the child. The Connector element is a complex element that describes a physical connector on the module. The Ports element is a complex element that describes the points of logical connections to the the module. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceStructureType |
|---|---|
| Abstract | no |
| Documentation |
The DeviceStructure element contains a description of the physical
modules that comprise a Device. It is analogous to an InternalStructure
element, however a Device and its modules do not contain network
interfaces.
The DeviceModule element describes the physical sub-components of a Device They may be referred to by different names, such as modules, slices, cards, etc. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DevicesType |
|---|---|
| Abstract | no |
| Documentation | The DevicesType element is the top-level container for an unbounded list of Device elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceSubModulesType |
|---|---|
| Abstract | no |
| Documentation | The DeviceSubModulesType element is the top-level container for an unbounded list of DeviceSubModule elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceSubModuleType |
|---|---|
| Abstract | no |
| Documentation |
The DeviceSubModule element describes the properties of sub-module
or card in a DAU or other module. A DeviceSubModule is a physical
sub-component attached to the DeviceModule, such as a daughter-card.
The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the module. The SerialID element, of type xsd:string, contains the model number of the module. The InventoryID element, of type xsd:token, describes the inventory identifier of the device. The Position element, of type xsd:nonNegativeInteger describes the slot number or the position of the sub-module within the module The PositionsOccupied element describes the size of the sub-module in terms of the number of positions or slots occupied by the sub-module. The Children element describes generic parent-child or master-slave relationships among the modules of a NetworkNode, between a NetworkNode and remote non-networked Device, or between non-networked Device elements. The relationship is intended to describe those where the parent is responsible for configuration or control of the child. The Connector element is a complex element that describes a physical connector on the module. The Ports element is a complex element that describes the points of logical connections to the the module. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DeviceType |
|---|---|
| Abstract | no |
| Documentation |
The Device element describes the properties of device, such as
a transducer, that is not network enabled for a TmNS-based system.
The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the Device. The SerialID element, of type xsd:string, contains the model number of the Device. The DeviceType element, can be one of the following strings: Accelerometer, FlowMeter, Microphone, Potentiometer, PressureTransducer, StrainGauge, Synchro, Thermocouple The InventoryID element, of type xsd:token, describes the inventory identifier of the device. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < DeviceTypeEnum (by restriction) < DeviceTypeEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | DeviceTypeEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The DeviceTypeEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DigitalAttributesType |
|---|---|
| Abstract | no |
| Documentation |
A DigitalAttributes element describes the properties of data
when it exists in a digitally encoded form. This element describes
digital data without regard for how it is packaged to be carried over
a digital transport or medium (e.g., Ethernet) using a specific
protocol. An applicable scenario would be describing the output
values of an analog-to-digital converter on a DAU. The following
elements describe only the digital data signal and not the methods by
which it is processed.
The DataLength element, of type mdl:ConditionParameters, describes the length or size of the digital data being described by the DigitalAttributes element in a unit related to the number of bits or bytes. The Endianness element, of type mdl:ConditionParameters, describes the ordering of bits of the of the digital data being described by the DigitalAttributes element. The DigitalEncoding element is an enumeration that describes the encoding scheme of the digital data being described by the DigitalAttributes element. The SampleRate element, of type mdl:ConditionParameters, describes the sampling rate of the digital data being described by the DigitalAttributes element, e.g. 10000 Hertz. If the user specifies both a desired range and a target value, the device should use the target value as the requested rate and validate the actual achieved rate meets the requested range. This is done by creating two ConditionParameters defining the bounds of the desired range (i.e. using > or >= and < or <=), and a third ConditionParameter defining the target value (i.e. using =). The DataRate element, of type mdl:ConditionParameters, describes the data rate of the digital data being described by the DigitalAttributes element. The data rate indicates the average number of transferred digital data units per unit of time, e.g. bits per second. The ActiveInputRange element, of type mdl:ConditionParameters, may be used to describe a range, typically in counts, in which the signal is expected to stay. For example a 12-bit analog to digital converter will produce output values in the range of 0 to 4095. In order to avoid accidental saturation, the signal conditioning may be set so that the active input range is between 100 and 4000 to allow for approximately 100 counts above and below the expected range. The DefaultValue element is used to define the value of a measurement before it has been given any other values. This should be used in two circumstances. First, when a measurement is used in a derived processing function that doesn't force the measurement to have been initialized, the measurement will have a value of its DefaultValue. Second, when a constant value is needed in a package, e.g. a subframe ID, a measurement can be given a DefaultValue and never initialized, therefore always having the same value. This second case should also make use of the ConstantValue element. The ConstantValue element is a boolean defining if the measurement is a constant value. If ConstantValue is set to true, the containing measurement shall never be initialized with any value. This should be used in conjunction with the DefaultValue element to allow for a measurement guaranteed to have a defined constant value. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < DigitalEncodingEnum (by restriction) < DigitalEncodingEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | DigitalEncodingEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The DigitalEncodingEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DSCPTableEntryRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a DSCPTableEntryRef must refer to the ID attribute of a DSCPTableEntry. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DSCPTableEntryType |
|---|---|
| Abstract | no |
| Documentation |
The DSCPTableEntry element describes a DSCP Table entry using
a value/description pair.
The Description element, of type xsd:string, is a human-interpretable description of the corresponding DSCPValue element. The DSCPValue element, of type mdl:SixBitBinary, describes a six-bit value that is placed into the IP header for delivery. The human-interpretable meaning of the six-bit value is given by the corresponding DSCPDescription element. The value of the DSCPValue element shall be unique within the MDL instance document. |
| Relations |
Used in:
Referenced by:
|
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | DSCPTableType |
|---|---|
| Abstract | no |
| Documentation | The DSCPTable element contains a description of the DiffServ Code Point (DSCP) values, which are parameters used when publishing data onto the TmNS-based system to implement the desired QoS behavior. The DSCPTable element is a collection of DSCP Table entries. TmNSDataMessages priority levels are specified through references to these DSCP bit settings (i.e., the DSCP Table entries). |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ElseType |
|---|---|
| Abstract | no |
| Documentation |
The ElseType is used to define a default assignment if none of the
conditionals before the else were true.
The Result element contains the result to be returned. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ExcitationType |
|---|---|
| Abstract | no |
| Documentation | The Values element is a complex element of type mdl:ConditionParameters that describes the excitation voltages to apply to the device or sensor such that the CalibrationPairs are valid. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ExternalScriptType |
|---|---|
| Abstract | no |
| Documentation |
The ScriptingLanguage element containts the name and version of the
scripting language used.
The GenericParameter element can be used as a container for an external script in a vendor-defined language, as well as any other information required by the system using this data, such as calling procedure. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldAssignmentsType |
|---|---|
| Abstract | no |
| Documentation | The FieldAssignmentsType element contains is the top-level container for an unbounded list of FieldAssignment elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldAssignmentType |
|---|---|
| Abstract | no |
| Documentation |
A FieldAssignment element connects a DataStructureField or FieldSet with
a Measurement. This element has two different semantic meanings, based
on whether the instance document is being used for negotiation or
configuration.
During negotiation, the FieldRef identifies that the bits contained in that field are desired, and a path should be provided to place those bits in the referenced measurement. Note that this does not necessarily mean that the referenced measurement will be packaged and directly transmitted, but only that the DAU must supply a path to obtain that measurement data from what is packaged. It is possible that the DAU cannot directly extract the bits into the target measurement, or even reference the desired field directly. In this case, the DAU may supply a new DataStructure that matches its capture abilities, update the DataStreamMessage to reference the new DataStructure, and provide derived processing functions to convert from its capture format to the target measurement. During configuration, the FieldRef still identifies the bits that are desired, but the Measurement must be directly populated by those target bits. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldDescriptionsType |
|---|---|
| Abstract | no |
| Documentation | The FieldDescriptions element is a container for one or more FieldDescription elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldDescriptionType |
|---|---|
| Abstract | no |
| Documentation | The FieldDescription element contains a FieldLocation element and a FieldEncoding element for describing a field. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldEncodingType |
|---|---|
| Abstract | no |
| Documentation | The FieldEncoding element describes the encoding of digital data contained within the described field (e.g. a DataStructureField). |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldEvaluationsType |
|---|---|
| Abstract | no |
| Documentation | The FieldEvaluationsType element is the top-level container for an unbounded list of FieldEvaluation elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldEvaluationType |
|---|---|
| Abstract | no |
| Documentation |
A FieldEvaluation element connects a DataStructureField or FieldSet to a
set of conditions which must be evaluated against that field. If every
condition is true for a given field, that field succeeds in its
evaluation.
The Bitmask element can optionally be used to preprocess the data in the field before the conditions are evaluated. This allows for a more compact representation of certain bit-comparison conditions, e.g. an octet in an IP address is within a target range. The Conditions element contains a series of ConditionParameters, each of which makes a comparison against the (optionally-bitmasked) value contained within the FieldEvaluation's target field. Every ConditionParameter must evaluate to True for the FieldEvaluation to succeed. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldLocationRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a FieldLocationRef must refer to the ID attribute of a FieldLocation in the same MeasurementDomain. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldLocationType |
|---|---|
| Abstract | no |
| Documentation |
The FieldLocation element describes the location and width of
a field (e.g., a DataStructureField). In the case that this field is
repeated (the value of the FieldRepetitions element is greater than
1), this element describes the offset for the first location of the
described field.
The FieldWidth element describes the width or size of a field. The FieldWidth element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldOffsetType |
|---|---|
| Abstract | no |
| Documentation |
The FieldOffset element describes the placement of a field
with respect to other known positions within a set of fields (e.g., a
DataStructure). The FieldOffset element indicates the location of
the first bit of a field. Along with the OffsetValue element, the
FieldOffset element shall contain only the OffsetFromLocation element
or the OffsetFromDataStructureFieldSet element.
The OffsetValue element contains the value of the offset for the field. The FieldOffset element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. If neither the OffsetFromLocation element nor the OffsetFromDataStructureFieldSet element is present, the offset indicated by the OffsetValue element is relative to the first bit of the set of fields (e.g., a Package). The OffsetFromLocation element contains an IDREF attribute, of type xsd:IDREF, that can be used to reference the ID attribute of another FieldLocation element. If this element is present, the offset indicated by the OffsetValue element is relative to the first bit of the referenced FieldLocation element. The OffsetFromDataStructureFieldSet element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a DataStructureFieldSet element. If this element is present, the offset indicated by the OffsetValue element is relative to the last bit of the referenced DataStructureFieldSet element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FieldReferencesType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FIFOQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The FIFOQDiscType describes a First In, First Out (FIFO)
classless Queuing Discipline (QDisc).
The LimitInPackets element, of type xsd:unsignedInt, is an unsigned 32-bit integer representing the maximum number of packets that the FIFO can contain before dropping. An example Linux configuration using some of the options for a FIFO QDisc is: 'tc qdisc add dev eth1 parent 1:10 handle 10:0 pfifo limit 50' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FilteringSchemesType |
|---|---|
| Abstract | no |
| Documentation | The FilteringSchemesType is the top-level container for an unbounded list of FilteringScheme elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FilteringSchemeType |
|---|---|
| Abstract | no |
| Documentation |
The FilteringSchemeType describes possibilities for how bus data fields
can be packaged by a capture device.
The Preconditions element defines a set of conditions, one of which must be true in order for this filtering scheme to apply. If the element is absent, there are no preconditions and the filtering scheme will always apply. The Exactly element defines a list of fields, all of which are required to be filtered on when using this filtering scheme. The Any element defines a list of fields, any combination of which can be filtered on when using this filtering scheme. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FiltersType |
|---|---|
| Abstract | no |
| Documentation | The CaptureFiltersType element is the top-level container for an unbounded list of Filter elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FilterType |
|---|---|
| Abstract | no |
| Documentation | The FilterType contains a series of FieldEvaluation elements, which describe the conditions necessary for a bus message to satisfy the filter. Each FieldEvaluation may draw multiple conditions about a given field, and all FieldEvaluations must be passed in order for the bus message to pass the filter. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FrequencyBandsType |
|---|---|
| Abstract | no |
| Documentation | The FrequencyBandsType element is the top-level container for an unbounded list of FrequencyBand elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FrequencyBandType |
|---|---|
| Abstract | no |
| Documentation |
The FrequencyBand element describes a frequency domain stop
band, a frequency domain pass band, or a frequency domain transition
band.
The BandType element is an enumeration that can be set to one of the following values: PassBand, StopBand, TransitionBand The EdgeFrequency element, of type mdl:ConditionParameters, describes a frequency value within the frequency domain. Assuming an analog representation of frequency content, a possible value would be 50 Hertz. The Attenuation element, of type mdl:ConditionParameters, describes an attenuation value of the corresponding frequency band. In the case of a pass band, the attenuation describes the maximum allowable attenuation, commonly 3 decibels (dB), relative to no attenuation (0 dB) within the band. In the case of a transition band, the attenuation describes maximum the allowable gain or minimum required loss relative to no attenuation (0 dB). In the case of a stop band, the attenuation describes the minimum required attenuation relative to no attenuation (0 dB). A positive value for attenuation indicates a reduction in the amplitude of a signal, whereas a negative value represents an increase or gain in the amplitude. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FrequencyContentType |
|---|---|
| Abstract | no |
| Documentation |
The FrequencyContent element describes the frequency ranges
occupied by the analog signal. This description is provided in the
frequency domain and is composed of stop bands and/or transition bands
and/or pass bands. These bands are described using a collection of
FrequencyBand elements. The frequency content description can be
provided assuming either an analog or digital representation.
The PercentSignal element may be used to describe the percent of total signal energy that falls within the FrequencyBand. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FTPServerURIsType |
|---|---|
| Abstract | no |
| Documentation | The FTPServerURIs element contains a list of one or more FTPServerURI elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FunctionMappingsType |
|---|---|
| Abstract | no |
| Documentation | The FunctionMappingsType contains a list of FunctionMapping elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FunctionMappingType |
|---|---|
| Abstract | no |
| Documentation |
The FunctionMappingType is used for mapping data processing
functions from input measurements to result measurements.
If the function's UpdateFrequency is "Triggered", the TriggerMeasurement may be used to define an external trigger for the function. The FunctionRef element points to the function being mapped. The InputMeasurement elements define which measurements will be used as inputs to the function. The ResultMeasurement elements define which measurements will be used to store the results of the function. There are at most two of these, to satisfy the Then and Else possibilities of the function. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FunctionRefType |
|---|---|
| Abstract | no |
| Documentation | The FunctionRefType is used to refer to a particular Function. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FunctionsType |
|---|---|
| Abstract | no |
| Documentation | The FunctionsType contains a list of reusable data processing functions. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FunctionType |
|---|---|
| Abstract | no |
| Documentation |
A Function element is a reusable data processing function.
The InputCount element is used to define how many input measurements the Function takes in order to complete its calculation. The UpdateFrequency element is used to define when the ResultMeasurement should be updated. The Algorithm element defines the algorithm used to calculate the value of the ResultMeasurement from the InputMeasurements. The IfThen element can be used as a replacement for the Algorithm element when a calculation must be used to determine which ResultMeasurement will be used. The ExternalScript element provides a mechanism for supplying an algorithm in a structure and language external to MDL's. The LookupTable element provides a structure for functions that implement a lookup table, defined here as a set of table entries where each table entry maps an input value or range of input values to a single output value. The Polynomial element provides a structure for functions that implement a polynomial, defined here as two sets of terms, each term containing a decimal coefficient and exponent, and each set defining the numerator or denominator of the function. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | GenericParameterType |
|---|---|
| Abstract | no |
| Documentation |
The GenericParameter element allows the description of additional
information outside the scope of the MDL schema, and may also be used to
document decisions made to arrive at a vendor-specific configuration.
The GenericParameter element contains one or more NameValue elements.
In addition, the GenericParameter element contains an xsd:any tag to allow for any well-formed XML to be placed in the element, however the intent is for the name/value pairs to be used as the primary mechanism for recording generic parameters so that the settings can be easily presented to the user in a standardized way. The main possibility that the xsd:any tags allow is the use of elements of a schema from outside MDL. This gives opportunities for uses such as including snippets from a vendor-specific schema used for finer-grained configuration of a module than MDL allows or including HTML-based help files or reports in the document returned from negotiation. The use of GenericParameter shall not be used as a work-around. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < GroupTypeEnum (by restriction) < GroupTypeEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | GroupTypeEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The GroupTypeEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HandoffRulesType |
|---|---|
| Abstract | no |
| Documentation | The HandoffRules element is a container for an unbounded list of HandoffRule elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HandoffRuleType |
|---|---|
| Abstract | no |
| Documentation |
The HandoffRule element contains a string to describe a rule for when to
execute a radio handoff while a radio network is in use.
The Name element provides a short, human-readable means of distinguishing one rule from another. The Description element provides a high-level, human-readable description of the HandoffRule. The Rule element specifies how to execute the rule engine. The string will contain the name of the executable and any options taht need to be provided to the rule. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HTBClassType |
|---|---|
| Abstract | no |
| Documentation |
Classes for HTB are used when dequeuing packets from the HTB
QDisc. Class instances can be arranged hierarchically.
The Priority element describes the order in which HTB classes are accessed when dequeuing a packet. The Rate element describes the maximum rate this class and all its children are guaranteed (in bits per second). The Ceiling element, of type ValueUnitType, describes the maximum rate (in bits per second) at which a class can send, if its parent has bandwidth to spare. The Burst element, of type xsd:unsignedInt, describes the number of bytes that can be burst at ceiling speed, in excess of the configured rate. This value should be at least as high as the highest burst of all children. The CBurst element, of type xsd:unsignedInt, describes the number of bytes that can be burst at 'infinite' speed, in other words, as fast as the interface can transmit them. An example Linux configuration using some of the options for a HTB Class is: 'tc class add dev eth1 parent 1:0 classid 1:1 htb rate 2Mbit ceil 10Mbit' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HTBQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The HTBQDiscType describes the Hierarchical Token Bucket (HTB)
classful Queuing Discipline (QDisc).
The DefaultClassHandle element indicates the destination class for packets that were not explicitly classified by filters defined for this HTB. The value of the DefaultClassHandle must match the value of an SLPHandle element within the same MisisonSLP. An example Linux configuration using some of the options for a HTB QDisc is: 'tc qdisc add dev eth1 parent root handle 1:0 htb default 1:40' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HTTPSetupType |
|---|---|
| Abstract | no |
| Documentation | The HTTPPort element, of type xsd:unsignedShort, may be used to statically assign a port number to the HTTP interface for situations where multiple NetworkNodes are running on the same network interface of a shared hardware platform. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | HTTPSSetupType |
|---|---|
| Abstract | no |
| Documentation | The HTTPSPort element, of type xsd:unsignedShort, may be used to statically assign a port number to the HTTPS interface for situations where multiple NetworkNodes are running on the same network interface of a shared hardware platform. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | InputMeasurementsType |
|---|---|
| Abstract | no |
| Documentation | The InputMeasurementsType element is the top-level container for an unbounded list of InputMeasurement elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | InputMeasurementType |
|---|---|
| Abstract | no |
| Documentation |
The InputMeasurementType is used to define input measurements
into a function.
The MeasurementRef element references the desired input measurement. The Variable element defines the variable which will be replaced with the measurement's value in the function's algorithm(s). If the function is a LookupTable or Polynomial type, the Variable element is not required. The Trigger element defines the input measurement as a trigger, to be used for functions whose UpdateFrequency has been defined as "Triggered". |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | InternalStructureType |
|---|---|
| Abstract | no |
| Documentation |
The InternalStructure element contains a description of the physical
modules that comprise a NetworkNode.
The Module element describes the physical sub-components of a NetwokNode. They may be referred to by different names, such as modules, slices, cards, etc. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LinkAgentType |
|---|---|
| Abstract | no |
| Documentation | The LinkAgent element is an element that can be contained by a TmNSRadio to describe the network interface and IP port number used to receive TCP datagrams from a TmNSLinkManager. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LogicalLocationType |
|---|---|
| Abstract | no |
| Documentation | The LogicalLocation element is used in various elements to describe the logical section or area of a network or Test Article from which the measurement is taken |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LookupTableEntryType |
|---|---|
| Abstract | no |
| Documentation | The LookupTableEntry element describes an entry in the lookup table that describes the mapping of a range of input values to a specific output value. The InputValue element describes a specific input value, that maps to the output value described by the OutputValue element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LookupTableType |
|---|---|
| Abstract | no |
| Documentation |
The LookupTable element describes a lookup table where each
table entry maps an input value or range of input values to a single
output value. The LookupTable element shall accept input data from a
single input measurement, and the LookupTable element shall produce
output data to a single output measurement.
If any LookupTableEntry has an InputValue that is equal to "PositiveInfinity", then the OutputValue from that entry will be used for any input greater than the highest defined LookupTableEntry's InputValue. If any LookupTableEntry has an InputValue that is equal to "NegativeInfinity", then the OutputValue from that entry will be used for any input less than the lowest defined LookupTableEntry's InputValue. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LTCInterfacesType |
|---|---|
| Abstract | no |
| Documentation | The LTCInterfaces element in a TmNSLTCDataSource element is a container for one or more LTCInterface elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | LTCInterfaceType |
|---|---|
| Abstract | no |
| Documentation |
An LTCInterface element associates one or more NetworkInterfaces with a
group of messages that will be output through those interfaces.
The TimeToLive element, of type xsd:unsignedByte, describes the Time-To-Live value assigned to the IP header of TmNS Data Messages produced by this MessageGroup. The NetworkInterfaceRef may be used to indicate which NetworkInterface is being used by this LTCInterface for an LTCDataSource within a NetworkNode with one or more NetworkInterfaces. The LTCInterface may contain a list of zero or more MessageDefinitionRefs that describe the messages that the LTC source is configured to generate. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MatchFieldType |
|---|---|
| Abstract | no |
| Documentation |
This condition matches if within the header of the specified
protocol (defaults to IPv4) within the byte at the location specified
by the offset (defaults to zero offset) the bits specified by the mask
(required) match the same bits of the supplied pattern value
(required)
Next Header usage: This condition matches if for the specified protocol (defaults to IPv4) within the header of the next protocol layer within the byte at the location specified by the offset (defaults to zero offset) the bits specified by the mask (required) match the same bits of the supplied pattern value (required) The FieldWidth element is an enumeration that describes 8-, 16-, or 32-bit field widths for matching. The Pattern element describes the pattern against which the fields should be matched. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MDLRootType |
|---|---|
| Abstract | no |
| Documentation |
The MDLRoot element is the root element of any MDL Instance
Document.
A note on conditional elements: The MDL schema is a system-level description. Not all components require every element to properly configure. In such cases, these elements are conditional. The documentation specifies when the conditional elements must and shall be present and processed. Components not specifically called out in documentation of conditional elements shall not fail to configure if the particular conditional element is not present. Conversely, components that are called out in documentation of conditional elements shall process any conditional elements that are proivded during configuration. In the schema notation, elements and attributes with a minOccurs attribute equal to "0" are conditional. The MDLRoot element may contain DatabaseID and Checksum elements, both of type xsd:string. The DatabaseID can be used to keep track of which database was used to generate the MDL instance document. The Checksum element contains a single checksum of all elements within the MDLRoot top-level element that follow the Checksum element. IRIG 106 Chapter 23 does not currently impose constraints on the specific checksum algorithm used. The ConfigurationVersion element, of type xsd:string, describes the unique version number of the MDL instance document. When a TmNSApp is configured with an MDL instance document or file, the ConfigurationVersion is saved and maintained on the TmNSApp and reported in accordance with IRIG 106 Chapter 25. The LastBuildDateTime element, of type xsd:dateTime, is used to optionally document the date/time the MDL instance document was produced. The DirtyBit element, of type xsd:boolean, is used in conjunction with reporting of the ConfigurationVersion element by a TmNSApp to indicate that one or more values in the reported MDL differ from the MDL file with which the TmNSApp was configured. Differences may be introduced through System Mangement interfaces, or other vendor specific interfaces. The ConfigurationVersion and DirtyBit elements combined faciliate configuration management of TmNSApps. The DirtyBit shall be set to true in a reported MDL file when configuration changes have been made that cause the MDL representation to differ from the last configuration via MDL. The TestMissions element contains the configuration associated with a particular test including the name, description, date time, a list of the participating networks, and the mission-level quality of service. The Units element is a container for all derived units used in describing measurements, data rates, time, etc. The MeasurementDomains element contains a list of MeasurementDomain elements, each of which describes a self-contained set of Measurements, Packages, Messages, and DataStreams. The NetworkDomain element contains a list of Networks and their interconnections that may be included in a TestMission description. The RANConfigurations element contains a list of RANConfiguration elements. Each RANConfiguration element describes the set of basic parameters for a Radio Access Network. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementDomainsType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementDomains element contains a list of one or more MeasurementDomain elements |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementDomainType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementDomain element contains the descriptions of Measurements, Packages, Messages, DataStreams, MeasurementGroups, MessageGroups, and associated DataProcessing to be used in a TmNS-based system. Each MeasurementDomain shall be completely self-contained, meaning, for example, that a Message shall contain only Packages from the same MeasurementDomain and a Package shall contain only Measurements from the same MeasurementDomain. Every MeasurementDomain shall contain a Name element that shall be unique within an MDL instance document. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementGroupsType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementGroups element in a MeasurementDomain element is a container for one or more MeasurementGroup elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementGroupType |
|---|---|
| Abstract | no |
| Documentation |
The MeasurementGroup element provides a method to group measurements for
purposes such as simultaneous sampling.
The GroupType element describes the type of measurement group. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementRefsType |
|---|---|
| Abstract | no |
| Documentation | The PreSelectMeasurementGroup element contains a list of MeasurementRef elements that describe which measurements are to be produced by the RCDataSource within a shorter period of time than typical requests. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementRefType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a Measurement element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementSelectorsType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementSelectors element contains a list of MeasurementSelector elements which describe what data is desired from a bus message. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementSelectorType |
|---|---|
| Abstract | no |
| Documentation | A MeasurementSelector element contains one or more FieldAssignments, which tell what bits are desired from a bus message, and a set of Selectors, which determine under what conditions those bits are desired. All Selectors must succeed in their evaluations for a given bus message for the FieldAssignments to be applied. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementsType |
|---|---|
| Abstract | no |
| Documentation |
The Measurements element in a MeasurementDomain element is a
container for one or more Measurement elements.
A Measurement element provides a description of the realization of a measurement type for a configuration of a Test Article. The Measurement element acts as a starting point to begin describing the steps and their resulting intermediate forms of a measurement that will result in the publishing of measurement data on the network. Specific elements and attributes are included to describe both the analog and digital properties of the Measurement element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementType |
|---|---|
| Abstract | no |
| Documentation |
The Measurement element provides a description of a
measurement type present in the configuration of a Test Article.
Measurements are related to physical phenomena that occur on a Test
Article. The Measurement element is a general description of the
properties of a measurement type that will potentially be realized as
measurement data that is contained in TmNSDataMessages.
The properties of a Measurement element describe both the design requirements and the resulting implementation details of a described measurement type. Specific elements and attributes are included to describe both the analog and digital properties of the Measurement elements. The Name element of the Measurement describes the mnemonic for the Measurement element. The value of the Name element must be unique among all Measurement Names within a MeasurementDomain. The MeasurementID is a unique 32-bit value. The scope of uniqueness is the MeasurementDomain. The MeasurementType element indicates the type of measurement being described and can be set to one of the following values: "Analog", "Discrete", "DigitalBus", "Computed" The MeasurementActive element indicates if a Measurement is to be acquired in the configuration specified by the MDL Instance Document. The DeliveryClass element is an enumeration of type mdl:DeliveryClassEnum that can be set to one of the following values: "Voice", "FlightSafety", or "BestEffort" The MeasurementTimeRef element may be used to identify the Measurement, which shall be of MeasurementType "Time", and represents the timestamp associated with this Measurement (see IRIG 106 Chapter 24 for Package Time Measurement Scoping Rules). The DataAttributes element describes the analog and digital attributes of a measurement on a Test Article. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | xsd:string < MeasurementTypeEnum (by restriction) < MeasurementTypeEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | MeasurementTypeEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The MeasurementTypeEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MeasurementTypesType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageDefinitionRefsType |
|---|---|
| Abstract | no |
| Documentation | The MessageDefinitionRefsType element contains is the top-level container for an unbounded list of MessageDefintionRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageDefinitionRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a MessageDefinitionRef must refer to the ID attribute of a MessageDefinitionType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageDefinitionsType |
|---|---|
| Abstract | no |
| Documentation | The MessageDefinitions element in a MeasurementDomain element is a container for one or more MessageDefinition elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageDefinitionType |
|---|---|
| Abstract | no |
| Documentation |
A MessageDefinition element describes a TmNSDataMessage type.
Please refer to the descriptions of the MaximumMessageLength element,
the MaximumMessageLatency element, and the FixedMessageLength element
for an explanation of the finalization constraints placed on the
defined TmNSDataMessage type. The following lists the elements and
attributes of the MessageDefinition elements.
The MessageDefinitionID element, of type mdl:ThirtyTwoBit, indicates the MessageDefinitionID (MDID) of this TmNSDataMessage type. The MessageDefinitionID shall be unique among all MessageDefinitionIDs within a MeasurementDomain. The MessageVersion element, of type xsd:string, describes the version of the TmNSDataMessage protocol that the MessageDefinition element follows. The OptionWordCount element, of type FourBitHex, specifies the number of 32-bit words in the ApplicationDefinedFields. The ApplicationDefinedFields element describes a set of optional message fields within a message header. The format of the ApplicationDefinedFields is similar to TCP Options. The DSCPTableEntryRef element contains an IDREF attribute of type xsd:IDREF that references the ID attribute of a DSCPTableEntry element. The DSCPValue in the DSCPTableEntry indicates the Diffserv Code Point markings that shall be applied IP header of the message. The DestinationAddress element, of type mdl:IPAddress, may be used to describe the multicast or unicast address to which the message is published. The DestinationPort element, of type xsd:unsignedShort(in the range [0,65535]) describes the destination port address of the transport. If this element is not provided, the default port as specified by IRIG 106 Chapter 26 will be used. The MaximumMessageLength element indicates the maximum length of this TmNSDataMessage type. The implied meaning is that when a TmNSDataMessage of this type reaches that length, or an additional Package would cause the length of the TmNSDataMessage to exceed this length, the TmNSDataMessage will be finalized with the current TmNSDataMessagePayload. The MaximumMessageLength element may be used in conjunction with the MaximumMessageLatency element; however, the MaximumMessageLength element shall not be present if the FixedMessageLength element is contained in the described MessageDefinition element. The MaximumMessageLength element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bytes or kilobytes. The MaximumMessageLatency element indicates the maximum amount of time that a NetworkNode shall wait before sending a TmNSDataMessage of this type. The implication is that when this timeout occurs, starting from the last sent time for a TmNSDataMessage of this type, the current TmNSDataMessage will be finalized with the current TmNSDataMessagePayload. The MaximumMessageLatency element may be used in conjunction with the MaximumMessageLength element; however, the MaximumMessageLatency element shall not be present if the FixedMessageLength element is contained in the described MessageDefinition element. The MaximumMessageLatency element is a floating-point value/units pair. The units for this element shall be in units of time such as seconds or milliseconds. If the TmNSDataMessage has a fixed length, the FixedMessageLength element indicates the length of TmNSDataMessages of this type. This length includes the TmNSDataMessageHeader. This value shall match the value that will be placed into the TmNSDataMessageHeader. If the TmNSDataMessage does not have a fixed length, then this element shall not be present in the MessageDefinition element, but a length value will appear in each TmNSDataMessageHeader. If the FixedMessageLength element is contained in the described MessageDefinition element, the MaximumMessageLatency element and the MaximumMessageLength element shall not be present. The FixedMessageLength element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bytes or kilobytes. The FixedPackageOrder element, of type xsd:boolean, indicates whether or not the Packages contained within the TmNSDataMessagePayload shall occur in a fixed order. If the value is set to "false" the ordering for a given MessageDefinition is variable and the PDID of each Package shall be unambiguously determinable. The PDID is necessary when the ordering is variable so that each Package within a TmNSDataMessagePayload can be differentiated. The FixedNumberOfPackages element, of type xsd:boolean, indicates whether or not the Packages contained within a TmNSDataMessagePayload shall occur a fixed number of times. If the value is set to "true", Packages in a TmNSDataMessagePayload shall appear exactly the same number of times their corresponding PackageInstance elements appear in the MessageDefinition element. If the value is set to "false", Packages in a TmNSDataMessagePayload can appear any number of times including zero. For example, if the FixedPackageOrder element has a value of true, the FixedNumberOfPackages element has a value of "false", and three included Package instances P1, P2, and P3 have Index values "1", "2", and "3", respectively, then the following sequences would be valid TmNSDataMessagePayloads: [P1, P2, P3], [P1, P2, P3, P1, P2, P3], [P1, P2, P3, P1], and [(P1, P2, P3)*]. The sequence [P2, P3, P1] would not be valid. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageGroupRefsType |
|---|---|
| Abstract | no |
| Documentation | The MessageGroupRefsType element is a container for one or more MessageGroupRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageGroupRefType |
|---|---|
| Abstract | no |
| Documentation | The MessageGroupRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a MessageGroup element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageGroupsType |
|---|---|
| Abstract | no |
| Documentation | The MessageGroups element in a MeasurementDomain element is a container for one or more MessageGroup elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MessageGroupType |
|---|---|
| Abstract | no |
| Documentation | The MessageGroup element provides a method to group messages. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ModulesType |
|---|---|
| Abstract | no |
| Documentation | The ModulesType element is the top-level container for an unbounded list of Module elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ModuleType |
|---|---|
| Abstract | no |
| Documentation |
The Module element describes the properties of module, card,
slot, or slice in a NetworkNode. DAUs are generally described
as a NetworkNode composed of many modules.
The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the module. The SerialID element, of type xsd:string, contains the model number of the module. The InventoryID element, of type xsd:token, describes the inventory identifier of the device. The Position element, of type xsd:nonNegativeInteger describes the slot number or the position of the module in a stack of modules. The PositionsOccupied element describes the size of the Module in terms of the number of positions or slots occupied by the module. The RunningApps element contains a list of TmNSAppRef elements That refer to the TmNSApps that are "running" on the Module. The RunningApps element is only used if the Module element is contained within a NetworkNode. The RunningApps element is not intended to be used when the Module is contained within a Device element. The Children element describes generic parent-child or master-slave relationships among the modules of a NetworkNode, between a NetworkNode and remote non-networked Device, or between non-networked Device elements. The relationship is intended to describe those where the parent is responsible for configuration or control of the child. The Connector element is a complex element that describes a physical connector on the module. The Ports element is a complex element that describes the points of logical connections to the the module. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MulticastRoutesType |
|---|---|
| Abstract | no |
| Documentation | The MulticastRoutesType element is the top-level container for an unbounded list of MulticastRoute elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MulticastRouteType |
|---|---|
| Abstract | no |
| Documentation | The MulticastRoute element describes the static routing configuration for a single multicast address. The MulticastAddress element, of type IPAddress, describes the multicast address. The StaticMulticast element may contain one or more IngressPortRef elements, of type PhysicalNetworkPortRef, and one or more EgressPortRef elements, of type PhysicalNetworkPortRef, to describe the physical network ports associated with the multicast address. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NameValuesType |
|---|---|
| Abstract | no |
| Documentation | The NameValues element is a container for one or more NameValue elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < NameValueType (by extension) |
|---|---|
| Sub-types: | None |
| Name | NameValueType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkDomainType |
|---|---|
| Abstract | no |
| Documentation | The NetworkDomain element contains a Networks element and a list of network-to-network PortMappings in the NetworkToNetworkPortMapping elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkInterfaceRefsType |
|---|---|
| Abstract | no |
| Documentation | The NetworkInterfaceRefsType element is the top-level container for an unbounded list of NetworkInterfaceRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkInterfaceRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a NetworkInterfaceRef shall refer to the ID attribute of a NetworkInterface within the same NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkInterfacesType |
|---|---|
| Abstract | no |
| Documentation | The NetworkInterfacesType element is the top-level container for an unbounded list of NetworkInterfaceType elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkInterfaceType |
|---|---|
| Abstract | no |
| Documentation |
A NetworkInterface element describes the module or component
that provides the interface between a NetworkNode and a network. A
NetworkNode can contain one or more NetworkInterfaces, and will have a
NetworkInterface element describing each.
The DHCPEnable element, of type xsd:boolean, indicates whether or not Dynamic Host Configuration Protocol (DHCP) is enabled for a NetworkInterface. The IPAddress element, of type mdl:IPAddress, describes the IP address associated with the NetworkInterface. The Netmask element, of type mdl:IPAddress, describes the netmask value associated with a NetworkInterface. The MACAddress element, of type mdl:MACAddress, describes the MAC address associated with a NetworkInterface. When a NetworkNode on which DHCP is enabled reports its current configuration, DHCPEnable shall be set to true and the IPAddress, Netmask, and Gateway need not be set. |
| Relations |
Used in:
Referenced by:
|
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkNodeRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a NetworkNodeRef must refer to the ID attribute of a NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkNodesType |
|---|---|
| Abstract | no |
| Documentation | The NetworkNodesType element contains is the top-level container for an unbounded list of NetworkNode elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkNodeType |
|---|---|
| Abstract | no |
| Documentation |
The NetworkNode element describes a NetworkNode existing
within a network. NetworkNodes are devices that contain at least one
NetworkInterface that connects the NetworkNode to a network.
NetworkNode is a generic concept to describe any device connected to
the network. Additional functionality for a NetworkNode is described
as a set of applications (TmNSApps) that it contains.
Examples include the DAU, Recorder, and TmNSGroundRadio elements
described in later sections.
The InventoryID element, of type xsd:token, describes the inventory identifier of a NetworkNode. The HostName element, of type xsd:string, identifies the host name of the NetworkNode. The Manufacturer element, of type xsd:string, describes the manufacturer, or make, of the NetworkNode. The Model element, of type xsd:string, describes the model number or name of the NetworkNode hardware (i.e., the model name that a manufacturer assigns to the product). The ModelVersion element, of type xsd:string, describes the version of the NetworkNode hardware (i.e., the revision number of a particular make and model). The SerialID element, of type xsd:string, describes the serial identifier (or serial number) assigned to the NetworkNode. The IEEE1588Version element is an enumeration that describes the version of the IEEE 1588 Precision Time Protocol (PTP) on the NetworkNode. If the value of IEEE1588Version is set to Multiple, each PhysicalNetworkPort contained in the NetworkNode shall contain the IEEE1588VersionOfPort element to describe the version for each physical network port. The Routes element is a container for one or more Route elements that together may be used to describe the routing table of the NetworkNode. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkRefsType |
|---|---|
| Abstract | no |
| Documentation | The NetworkRefs element in a TestMission element is a container for one or more NetworkRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkRefType |
|---|---|
| Abstract | no |
| Documentation | The NetworkRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a Network element |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworksType |
|---|---|
| Abstract | no |
| Documentation | The NetworksType element is the top-level container for an unbounded list of Network elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NetworkType |
|---|---|
| Abstract | no |
| Documentation |
A Network element describes the physical and logical design of
a network. This description covers the physical topology (e.g., the
NetworkNodes and how they are interconnected), the logical
configuration (e.g., the decomposition of networks into subnets and
rules for how messages will flow on the network), and the performance
capabilities (e.g., the Quality of Service (QoS) configuration, link
and NetworkNode speeds, and resources) of networks. Each Network
shall contain a Name element, of type xsd:token, that shall be unique
across all Networks in the MDL instance document. The XML processor
will remove line feeds, carriage returns, tabs, leading and trailing
spaces, and multiple spaces from all elements of type xsd:token.
The NetworkType element describes the type of the containing Network element. The NetworkType element is an enumeration that can be set to one of the following values: RangeNetwork, TmNS, TestArticle Network, VehicleNetwork, GroundStationNetwork, GroundNetwork, GenericNetwork Network elements can be contained within other Network elements. This containment allows the description of hierarchical networks. The Devices element contains descriptions of non-TmNS, non-network enabled devices such as transducers. The PortMappings element describes physical connections, or PortMappings, between NetworkNodes and Devices within a single Network. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NotificationDestinationsType |
|---|---|
| Abstract | no |
| Documentation | The NotificationsDestinations element is a container for zero or more NotificationDestination elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NotificationDestinationType |
|---|---|
| Abstract | no |
| Documentation | The NotificationDestination element describes the IP address (via the NetworkInterfaceRef) and the IP port number to which notifications are sent. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NotificationsType |
|---|---|
| Abstract | no |
| Documentation |
The Notifications element describes the settings for SNMP notifications.
The TimeLockLostEnable element describes whether notifications are sent when time lock is lost. The TimeLockLostIntervalMSec element describes the interval, in milliseconds, between repeated time lock lost notifications. The TimeLockLostMaxRepeats element describes the maximum number of repeats allowed for a time lock lost notification. The IEEE1588MaxOffsetFromMasterEnable element describes whether notifications are sent when the maximum observed time offset from the IEEE 1588 master clock exceeds the threshold described by IEEE1588MaxOffsetFromMasterThreshold. The IEEE1588MaxOffsetFromMasterIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The IEEE1588MaxOffsetFromMasterMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The IEEE1588MaxJitterEnable element describes whether notifications are sent when the maximum observed jitter from the IEEE 1588 master clock exceeds the threshold described by IEEE1588MaxJitterThreshold. The IEEE1588MaxJitterIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The IEEE1588MaxJitterMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The TempOutOfRangeEnable element describes whether notifications are sent when the maximum observed temperature exceeds the threshold described by TempOutOfRangeHighThreshold or when the minimum observed temperature goes below the TempOutOfRangeLowThreshold. The TempOutOfRangeIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The TempOutOfRangeMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The TempOutOfRangeLowThreshold and TempOutOfRangeHighThreshold are measured in degrees Celsius. The AccessAnomalyEnable element describes whether notifications are sent when an intrusion attempt is detected. The AccessAnomalyIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The AccessAnomalyMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The PowerFaultEnable element describes whether notifications are sent when a power fault occurs. The PowerFaultIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The PowerFaultMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The InvalidInputEnable element describes whether notifications are sent when invalid input is detected. The InvalidInputIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The InvalidInputMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The PointingErrorEnable element describes whether notifications are sent when an antenna failed to point to the requested pointingCommand value. PointingErrorIntervalMSec element describes the interval, in milliseconds, between repeated notifications. The PointingErrorMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The TXNumQueueOverflowsEnable element describes whether notifications are sent when the number of transmit queue overflows exceeds the specified threshold. TxNumQueueOverflowsIntervalMSec element describes the interval, in milliseconds, between repeated notifications. TxNumQueueOverflowsMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The TxNumQueueOverflowsThreshold element describes the threshold at which a notification is generated when the described number of overflows has occurred. The RXNumQueueOverflowsEnable element describes whether notifications are sent when the number of receive queue overflows exceeds the specified threshold. RxNumQueueOverflowsIntervalMSec element describes the interval, in milliseconds, between repeated notifications. RxNumQueueOverflowsMaxRepeats element describes the maximum number of repeats allowed for this type of notification. The RxNumQueueOverflowsThreshold element describes the threshold at which a notification is generated when the described number of overflows has occurred. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | NumeratorsType |
|---|---|
| Abstract | no |
| Documentation | The NumeratorsType element is the top-level container for an unbounded list of Numerator elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageDefinitionRefsType |
|---|---|
| Abstract | no |
| Documentation | The PackageDefinitionRefsType element is a container for one or more PackageDefinitionRefType elements |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageDefinitionRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a PackageDefinitionRef must refer to the ID attribute of a PackageDefinition within the same MeasurementDomain. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageDefinitionsType |
|---|---|
| Abstract | no |
| Documentation | The PackageDefinitions element in a MeasurementDomain element is a container for one or more PackageDefinition elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageDefinitionType |
|---|---|
| Abstract | no |
| Documentation |
The PackageDefinition element describes a Package type, which
is identified by the PackageDefinitionID (PDID). The value of the
PackageDefinitionID shall be unique among all PackageDefinitionIDs
within a MeasurementDomain. The StandardPackageHeader element, of
type xsd:boolean, indicates whether or not this Package type includes
the standard package header. If the StandardPackageHeader is false, the
PackageHeaderDefinition element, of type PackageHeaderDefinitionType, is
used to describe the structure and contents of the non-standard package
header.
In a PackageDefinition, there is a choice between a structure using a DataStructure and a reference to a TMATS-defined PCM data stream. In the case that a DataStructure is used, another choice is presented between a DataMap and a DataStreamMessageRef. The DataMap element provides a mapping of measurements into the package's DataStructure. The DataStreamMessageRef provides instruction to package messages that pass the filters of a target DataStreamMessage. When a DataStreamMessage is packaged, ProperNames will be used as linkage between the DataStructure referenced in the PackageDefinition and the DataStructure referenced in the DataStreamMessage, e.g. a field in the Message with a ProperName of ARINC429Data will be placed in the field in the Package with a ProperName of ARINC429Data. Note that this implies a given PackageDefinition will only package individual messages from a DataStream. If more than one message is desired to be placed in a package, it is recommended to extract the bus messages into measurements and use a DataMap to package those measurements explicitly. In the case that a PCM data stream is used, the DataStreamRef will point to the TMATS-described DataStream to be packaged, with the PCMMinorFrame elements optionally used to specify target minor frames to be packaged. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageHeaderDefinitionType |
|---|---|
| Abstract | no |
| Documentation |
The PackageHeaderDefinition element describes the set of data
fields that make up a package header and the data that gets mapped to
these data fields. The PackageHeaderDefinition element is not
required when the defined Package includes the standard package
header. When the standard package header is not used, the
PackageHeaderDefinition element can be used to describe the makeup of
the package header and the sources of the data that populates the
package fields of the package header.
The DataMap element describes the mapping of digital data to the package fields defined by the PackageHeaderStructure element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageHeaderStructureType |
|---|---|
| Abstract | no |
| Documentation |
The PackageHeaderStructure element describes the set of
package fields that make up the package header and can carry data.
The fields do not need to cover all bits in a package header, and the
fields may overlap.
The PDIDFieldDescription element describes the DataStructureField in a package header that shall contain the PDID. The PDIDFieldDescription element shall not be used when using the standard package header. The StatusFlagFields element describes the set of package fields within a package header that contain the StatusFlags field. Although the StatusFlags field is considered a single field in the standard package header, the StatusFlagFields element can describe each individual status flag in both its structure and content. The StatusFlagFields element can be used when using the standard package header to provide specific descriptions for each individual flag for this Package type. The NonTmNSPackageHeaderFieldDescription element describes a field in a package header that is not defined by the standard package header. The NonTmNSPackageHeaderFieldDescription element shall not be used when using the standard package header. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageInstancesType |
|---|---|
| Abstract | no |
| Documentation | The PackageInstancesType element is the top-level container for an unbounded list of PackageInstance elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageInstanceType |
|---|---|
| Abstract | no |
| Documentation |
The PackageInstance elements describe which Packages may be
contained in the TmNSDataMessagePayload of this TmNSDataMessage type.
Each PackageInstance element contains one required
PackageDefinitionRef element and one optional Index attribute, of type
xsd:positiveInteger. The PackageDefinitionRef element refers to a
PackageDefinition element that can be contained in the
TmNSDataMessagePayload.
The Index attribute may be included if the order of Packages in the TmNSDataMessagePayload is known. The value of the Index attribute shall be unique within the scope of a MessageDefinition element. The MDL language does not require a particular convention for the values of the Index attribute; the recommended convention is to begin with a value of "1" and increment by one. If the value of the FixedPackageOrder element for this TmNSDataMessage type is "true", then each PackageInstance element shall have an Index value specified. The implication is that the TmNSDataMessagePayload shall have Packages that occur in the sequence specified by the value of the Index attribute. If the value of the FixedNumberOfPackages element is "false", the sequence of Packages may repeat any number of times in a TmNSDataMessagePayload. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageLengthFieldDescriptionType |
|---|---|
| Abstract | no |
| Documentation | The PackageLengthFieldDescription element describes the field within a package header that contains the Package length. The FieldLocation element describes the location and width of a field within a Package. The FieldEncoding element describes the encoding and format of the digital values contained within a field. The UnitRef and BaseUnit elements describe the units of measure for describing the field. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageLengthFieldType |
|---|---|
| Abstract | no |
| Documentation |
The PackageLengthField element describes the length of a
Package and the field that contains the PackageLength field. The
PackageLengthField element shall not be used when using the standard
package header.
If the Package has a fixed length, the FixedPackageLength indicates the length of the Package. The Package length includes the size of the package header. The FixedPackageLength element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackageTimeDeltaFieldDescriptionType |
|---|---|
| Abstract | no |
| Documentation | The PackageTimeDeltaFieldDescription element describes the field in a package header that shall contain the PackageTimeDelta field. The PackageTimeDeltaFieldDescription element shall not be used when using the standard package header. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackagingSchemesType |
|---|---|
| Abstract | no |
| Documentation | The PackagingSchemesType is the top-level container for an unbounded list of PackagingScheme elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PackagingSchemeType |
|---|---|
| Abstract | no |
| Documentation |
The PackagingSchemeType describes possibilities for how bus data fields
can be packaged by a capture device.
The Preconditions element defines a set of conditions, one of which must be true in order for this packaging scheme to apply. If the element is absent, there are no preconditions and the packaging scheme will always apply. The Exactly element defines a list of fields, all of which are required to be packaged when using this packaging scheme. The Any element defines a list of fields, any combination of which can be packaged when using this packaging scheme. The Implied element defines a list of fields which cannot be packaged, but whose information is implied by the packaging. For example, a capture card may not be able to package the label, but each unique label can correspond to a particular location within the packaging. The Dropped element defines a list of fields which cannot be packaged, and for which the information cannot be recovered from the capture device. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PCMDataLinkType |
|---|---|
| Abstract | no |
| Documentation |
The PCMDataLink element describes the PCM data format for the
described PCMStream element. The PCMDataLink element specifies the
formatting of the data structure (i.e., locations that carry data) and
the mapping of data content to the defined data structure. The
properties of the described PCMDataLink element are unique to the PCM
data format according to IRIG 106 Chapters 4 and 9.
The PCMDataLink element is similar to the defined xsd:complexType element named "DataLinkType" from the TMATS schema as described in IRIG 106 Chapter 9. The PCMDataLink contains the PCMFormatAttributes element that is imported directly from the TMATS schema. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PCMMeasurementRefsType |
|---|---|
| Abstract | no |
| Documentation | The PCMMeasurementRefsType element is the top-level container for an unbounded list of PCMMeasurementRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PCMMeasurementRefType |
|---|---|
| Abstract | no |
| Documentation | The PCMMeasurementRef element contains an NameRef attribute, of type xsd:string, that shall reference the Name attribute of the TMATS schema's Measurement within the same MeasurementDomain. The XPATH expression for the location of the Name attribute is /MDLRoot/MeasurementDomains/MeasurementDomain/DataStreams/DataStream/PCMDataLink/PCMFormatAttributes/ PCMMeasurements/MeasurementList/Measurement[@ID] |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PCMMinorFramesType |
|---|---|
| Abstract | no |
| Documentation | The PCMMinorFramesType element is the top-level container for an unbounded list of PCMMinorFrame elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:positiveInteger < PCMMinorFrameType (by extension) |
|---|---|
| Sub-types: | None |
| Name | PCMMinorFrameType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhoneNumbersType |
|---|---|
| Abstract | no |
| Documentation | The PhoneNumbers element contains one or more PhoneNumber elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhoneNumberType |
|---|---|
| Abstract | no |
| Documentation | The PhoneNumberType contains a VoIPClientName element and the VoIP phone number. The PhoneNumber element is a string of between 3 and 10 digits with no hypens or dashes. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhysicalLocationType |
|---|---|
| Abstract | no |
| Documentation | The PhysicalLocation element describes the physical location from which the measurement is taken. The physical location assigned to a measurement does not necessarily match the physical location of the NetworkNode that acquires the measurement. For example, the value of the PhysicalLocation element for a measurement taken from a remote sensor on a Test Article will differ from the value of the PhysicalLocation element of a DAU that is connected to the sensor through a wire. The PhysicalLocation of a NetworkNode describes its physical location. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhysicalNetworkPortRefsType |
|---|---|
| Abstract | no |
| Documentation | The PhysicalNetworkPortRefsType element is the top-level container for an unbounded list of PhysicalNetworkPortRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhysicalNetworkPortRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a PhysicalNetworkPortRef must refer to the ID attribute of a PhysicalNetworkPort. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhysicalNetworkPortsType |
|---|---|
| Abstract | no |
| Documentation | The PhysicalNetworkPortsType element is the top-level container for an unbounded list of PhysicalNetworkPort elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PhysicalNetworkPortType |
|---|---|
| Abstract | no |
| Documentation |
A PhysicalNetworkPort element describes the physical point of
connection between the NetworkNodes that make up a network. The
Medium element describes the physical medium used by the port to
transfer data. The Medium element is an enumeration that can be set
to one of the following values: Copper, Fiber, Wireless
The PortNumber element, of type xsd:unsignedShort, describes the number assigned to a PhysicalNetworkPort. This is used to describe the numbering of the physical ports on a NetworkNode. For example, a switch may have ports "1", "2", "3", and "4". The value of the PortNumber element of PhysicalNetworkPort element shall be a non-negative integer that is unique within the scope of the NetworkNode element containing it. For instance, a switch containing a NetworkInterface element with N PhysicalNetworkPorts shall have N PhysicalNetworkPort elements, each with a unique PortNumber value. It is not required that the PortNumber elements for PhysicalNetworkPort elements on a NetworkNode have contiguous values. Likewise, the starting value (lowest number) is not standardized. A NetworkNode may use zero-based port numbering or one-based numbering. As an example, ports can be numbered 2, 4, 6, and 8. It is recommended that the PortNumber elements of a NetworkNode should be one-based and use contiguous values. For example, a NetworkNode with four ports should use the values 1, 2, 3, and 4. The PortDataRate element, of type mdl:ValueUnitType, describes the data rate of a PhysicalNetworkPort. The data rate indicates the average number of transferred digital data units per unit of time. The PortDataRate element is a floating-point value/units pair. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PingSweepRangesType |
|---|---|
| Abstract | no |
| Documentation | The PingSweepRanges element contains a list of one or more PingSweepRange elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PingSweepRangeType |
|---|---|
| Abstract | no |
| Documentation | The PingSweepRange element describes the begin and ending IP addresses to be queried during a ping sweep for device discovery. If the StartIPAddress and StopIPAddress elements are the same, only a single IP address is pinged. If the addresses are different, an inclusive search of each IP address in the range is performed. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PinRefsType |
|---|---|
| Abstract | no |
| Documentation | The PinRefsType element is the top-level container for an unbounded list of PinRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PinRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a PinRef must refer to the ID attribute of a Pin within the same NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PinsType |
|---|---|
| Abstract | no |
| Documentation | The PinsType element is the top-level container for an unbounded list of Pin elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PinType |
|---|---|
| Abstract | no |
| Documentation |
The Pin element describes a connection point on a physical
connector. The Pin element contains a Designator element that
describes the pin number or letter within a connector.
The Index attribute, of type xsd:positiveInteger, shall be unique within a connector and describes the ordering of the pin elements for display purposes. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PolynomialTermsType |
|---|---|
| Abstract | no |
| Documentation | The PolynomialTerms element describes a single variable polynomial term. The Term element describes such a term as a coefficient multiplied by a variable of interest raised to an exponent. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PolynomialType |
|---|---|
| Abstract | no |
| Documentation |
The Polynomial element describes two sets of terms, each term
containing a decimal coefficient and exponent, and each set
defining the numerator or denominator of the function.
The Polynomial element shall accept input data from a
single input measurement, and the Polynomial element shall produce
output data to a single output measurement.
The Numerator element describes the numerator of the Polynomial element as the summation of single variable polynomial terms. The Denominator element describes the denominator of the Polynomial element as the summation of single variable polynomial terms. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortMappingRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a PortMappingRef must refer to the ID attribute of a PortMapping. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortMappingsType |
|---|---|
| Abstract | no |
| Documentation | The PortMappings element may contain one or more PortMapping elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortMappingType |
|---|---|
| Abstract | no |
| Documentation |
The PortMapping element describes the connection between two
Port elements. Often, the PortMapping element will capture the flow
of data between the indicated Port elements.
The PortMapping may include either a DataStreamRef, or a MeasurementRef to describe the properties of the data that flows over the connection described by the PortMapping element. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortRefType |
|---|---|
| Abstract | no |
| Documentation | The PortRef element contains an IDREF attribute that shall refer to the ID attribute of a Port. PortRef elements within a Network shall refer to a Port contained within the same Network or a contained sub-Network. PortRef elements with the NetworkToNetworkPortMapping element may refer to Ports in other Networks. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortsType |
|---|---|
| Abstract | no |
| Documentation | The Ports element may contain one or more Port elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortType |
|---|---|
| Abstract | no |
| Documentation |
The Port element describes an logical interface through which
data passes. A Port element can contain a set of PinRef elements that
indicate the connection points (i.e., the Pin elements) that represent
the physical realization of the Port element.
The PhysicalNetworkPortRef and PinRef elements provide linkages between system topology and physical interfaces. The CaptureCapabilityRefs element provides a way for a DAU to convey its bus capture capabilities during an Inventory request by referencing defined CaptureCapability elements. The Index attribute, of type xsd:positiveInteger, shall be unique within a Ports element and describes the ordering of individual Port elements for display purposes. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | xsd:string < PortTypeEnum (by restriction) < PortTypeEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | PortTypeEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The PortTypeEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PortTypesType |
|---|---|
| Abstract | no |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PRIOClassType |
|---|---|
| Abstract | no |
| Documentation | Classes for PRIO are created automatically when the PRIO qdisc is created, but should be explicitly included in the SLP hierarchy in order to reference them (for example, when changing the underlying qdisc from PFIFO to something else, the parent class is referenced). |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | PRIOQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The PRIOQDiscType describes the Priority Queuing (PRIO)
classful Queuing Discipline (QDisc).
The NumberOfBands element, of type xsd:unsignedInt, describes the total number of bands (classes) that will be automatically created for this PRIO queuing discipline. Up to 16 bands may be described. The Priomap element describes the mapping of bands to TOS bits An example Linux configuration using some of the options for a PRIO QDisc is: 'tc qdisc add dev eth0 root handle 1: prio' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < ProperNameEnum (by restriction) < ProperNameEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | ProperNameEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The ProperNameEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the string representing the extended enumeration value. If the value is any other enumeration, the "Extension" attribute further specifies the enumeration's properties. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | QDiscChoiceType |
|---|---|
| Abstract | no |
| Documentation | An element of type QDiscChoiceType shall contain one and only one of the following elements: FIFO (of type FIFOQDiscType), RED (of type REDQDiscType), SFQ (of type SFQQDiscType), TBF (of type TBFQDiscType), PRIO (of type PRIOQDiscType), or HTB (of type HTBQDiscType). |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | QoSPoliciesType |
|---|---|
| Abstract | no |
| Documentation | The QoSPolicies element contains mission-level Quality of Service descriptions for a particular test mission. The QoSPolicies element contains a list of one or more QoSPolicy elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | QoSPolicyRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a QoSPolicyRefType must refer to the ID attribute of a QoSPolicyType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | QoSPolicyType |
|---|---|
| Abstract | no |
| Documentation |
The QoSPolicy element (or Mission Service Level Profile)
describes the high-level, mission-specific data delivery requirements
and constraints that will be provided by the Radio Access Network for
a given test mission. There may be more than one QoSPolicy element
defined per test mission, depending on the needs of the test. For
example, a test mission defining a relay platform will contain a
QoSPolicy element to define the data delivery needs for the relay
itself and a QoSPolicy element to define the data delivery needs of
the data being relayed.
The Name element is used as a short, human-readable 'tag' to identify a QoSPolicy. The Description element is used as a human-readable description of the QoSPolicy. The QoSPolicyID, which is a 32-bit field composed of 3 subfields, identifies a Mission Service Level Profile. The QoSPolicyID shall be unique within the MDLRoot documentation and must be unique across all Ranges. The most significant 8 bits (bit positions 24-31) of the QoSPolicyID contain the Range ID field(8-bits). This identifies the Test Range that this test mission is primarily associated with. Allows up to 256 unique Ranges to be identified. In cases where test missions are to be flown involving multiple ranges, well-known unique ID values should be established a priori to ensure there are no usage conflicts. Bits 4-23 of the QoSPolicyID contain a 20-bit MSLPTag field, which serves as the identification number of this MSLP. The least significant 4 bits of the QoSPolicyID constitute an InstanceID subfield which is managed and assigned by the System Manager each time a new instance of a queue structure must be created, instantiated and uniquely identified on a range. The Instance field will be zero in the initial MDL configuration file. If a queue structure must be replicated on multiple different components, the instance field of the QoSPolicyID will be used to ensure specific queues can still be identified unambiguously. The Priority element specifies a value for the overall numerical priority ranking that applies to this test, as compared to other ongoing tests competing for network resources. This is the 'collective' priority of everything defined in this QoSPolicy with respect any other QoSPolicy defined for this or any other test. The LinkManagementMinCapacity element, of type mdl:ValueUnitType, specifies the minimum amount of dedicated network capacity (measured in bits per second) to be held in reserve at all times for the Radio Link referenced by this QoSPolicy. LinkManagementMinCapacity indicates the amount of capacity that shall not be shared with other QoSPolicy definitions and is always immediately available when the referenced Radio Link is provided Transmission Opportunity Assignments by Link Management. This capacity is used to guarantee there are sufficient Transmission Opportunities for the transport of RF Network Messages. The AssuredCapacity element, of type AssuredCapacityType, specifies the network capacity (measured in bits per second) required for the Radio Link referenced by this QoSPolicy to satisfy the transmission data rates under nominal conditions. Excess capacity allocated for but unused by a Radio Link at any given time can be reallocated by Link Management to satisfy excess demand of other Radio Links. Likewise, an instantaneous need for capacity beyond this nominal allocation, e.g., due to unforeseen traffic bursts, can be satisfied using any available excess capacity from other Radio Links. The value for AssuredCapacity shall equal or exceed the value for LinkManagementMinCapacity. The AssuredCapacityType contains a Timeout element, of type xsd:unsignedLong, which specifies the amount of time, in microseconds, that must pass with the transmission queues empty for the Radio Link before Link Management can reduce allocations below AssuredCapacity making additional allocations available to other Radio Links. Link Management is responsible for detecting and removing queue levels resulting from RF Network Messages when measuring Timeouts. The Timeout element will not impact LinkManagementMinCapacity allocations as they are guaranteed to the Radio Link referenced by the QoSPolicy and are not to be shared with other Radio Links. The ServiceLevelProfiles element is a container that holds ServiceLevelProfile information that defines a hierarchy of Radio Bearers for this QoSPolicy. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | QueueConstructChoiceType |
|---|---|
| Abstract | no |
| Documentation | The QueueConstructChoiceType may contain either a QDisc element (of type QDiscChoiceType) or a Class element (of type ClassChoiceType) for describing either a queuing discipline or a class. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioAssociationsType |
|---|---|
| Abstract | no |
| Documentation | The RadioAssociationsType element contains an unbounded list of RadioAssociationType elements |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioAssociationType |
|---|---|
| Abstract | no |
| Documentation |
The RadioAssociation element is used to describe a logical
association between ground and test article radio and SST elements for
a particular test mission.
The Name element, of type xsd:token, is a human-readable name for the RadioAssociation. The Name element shall be unique within a TestMission. The Description element, of type xsd:string, is a text description of the association. The Active element, of type xsd:boolean, describes whether or not the association is active. The TmNSAppRef elements, of type TmNSAppRefType, contain references to the associated elements. A RadioAssociation contains two or more ManageAppRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioGroupRefsType |
|---|---|
| Abstract | no |
| Documentation | The RadioGroupRefsType element contains an unbounded list of RadioGroupRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioGroupRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a RadioGroupRef must refer to the ID attribute of a RadioGroupType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioGroupsType |
|---|---|
| Abstract | no |
| Documentation | The RadioGroups element is a container for an unbounded list of RadioGroup elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioGroupType |
|---|---|
| Abstract | no |
| Documentation |
The RadioGroup element contains parameters to describe a group
RF MAC address for the radios. It is a similar concept to mulicast
addresses in wired networks.
The Name element provides a short, human-readable means of distinguishing one radio group from another. The Name element must be unique among all RadioGroup Names. The Description element provides a high-level, human-readable description of the RadioGroup. The GroupRFMACAddress element of type xsd:unsignedShort, specifies the 16-bit RF MAC Address assigned to the RadioGroup being described. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioLinkRefsType |
|---|---|
| Abstract | no |
| Documentation | The RadioLinkRefs element is the top-level container for an unbounded list of RadioLinkRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioLinkRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a RadioLinkRef must refer to the ID attribute of a RadioLinkType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioLinksType |
|---|---|
| Abstract | no |
| Documentation | The RadioLinksType element contains an unbounded list of RadioLink elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RadioLinkType |
|---|---|
| Abstract | no |
| Documentation |
The RadioLink element describes a one-way connection between
two radio endpoints.
The Name element provides a human-readable name for the Radio Link The Description element provides a human-readable description of the Radio Link In some cases, not all of the endpoints of a Radio Link are known in advance. The SourceRadioRef element, of type TmNSAppRefType, indicates the source of traffic on this Radio Link The DestinationRadioRef element, of type TmNSAppRefType, indicates the desination of traffic on this Radio Link The LinkType element, of type LinkTypeEnum, describes the type of link in the system. The TxRxEnable element specifies whether transmission/reception is enabled on this Radio Link. The HeartbeatTimeout element specifies the lifetime of a heartbeat TLV message in terms of Epochs. This element can be set to an integer value in the range [0, 65535]. The LinkManagerHeartbeatTimeout element specifies the lifetime of a heartbeat TLV message in terms of Epochs. This element can be set to an integer value in the range [0, 65535]. Used to configure the Link Manager. The LinkManagerTxOpTimeout element specifies the lifetime of a TxOp TLV in terms of Epochs. This element can be set to an integer value in the range [0, 255]. Used to configure the Link Manager. The EncryptionEnabled element, of type xsd:boolean, describes whether Link Layer encryption is performed on this radio link. The EncryptionKeyID element describes an identifier for the link layer encryption key that is used on this radio link. Note that this is not the encyrption key itself but merely a key identifier. The TransmissionSchedule element describes the scheduling parameters. If the element is present, the schedule is used. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RANConfigurationRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a RANConfigurationRefType must refer to the ID attribute of a RANConfigurationType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RANConfigurationsType |
|---|---|
| Abstract | no |
| Documentation | The RANConfigurations element is the top-level container for an unbounded list of RANConfiguration elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RANConfigurationType |
|---|---|
| Abstract | no |
| Documentation |
The RANConfiguration element represents a set of system-wide
parameters that affect the behavior of a particular Radio Access
Network (RAN). This element can be referenced by any RAN component
that needs to coordinate system-wide operations with other RAN
components.
The Name element provides a short, human-readable means of distinguishing one parameter set from another. The Name element must be unique among all RANConfiguration Names. The Description element provides a high-level, human-readable description of the RAN. The LinkAgentConnectionTimeout element specifies the number of seconds of inactivity that will result in a LinkAgent connection timing out. The LinkAgentConnectionEncryptionEnabled element specifies whether TLS should be enabled for all LinkAgent connections between the TmNSLinkManager and the TmNSRadio TmNSApps. The TSSTunnelEncryptionEnabled element specifies whether TLS should be enabled for all TSSTunnel connections between the TmNSTSSClients and TmNSTSSServers associated with this RANConfiguration. The CenterFrequencyHz element specifies the center frequency (in Hertz) for all TmNS-based RF network communications on this RAN. The ModulationType element specifies the modulation waveform to be used on this RAN. For example "SOQPSK-TG". The EpochSize element describes the epoch interval in milliseconds. The valid values are 10, 20, 25, 40, 50, 100, 200, 250, 500, and 1000. The LDPCBlocksPerBurst element specifies the fixed number of LDPC code blocks to be contained in every transmission burst sequence. The MaxGuardTimeSec element specifies the guard interval (in fractions of seconds) that will ensure non-overlapping RF transmissions. The RadioControlLoopDSCPRef element specifies the Diffserv Codepoint to be applied to IP network-layer messaging associated with the RF Network Radio Control Loop. This includes all Link Manager Messages exchanged on the Link Manager to Link Agent (LM-LA) Interface between components implementing Link Manager and Radio functionality. This includes RAN Command and Control Messages exchanged on the Link Manager to Queue Manager (LM-QM) Interface between components implementing Link Manager and Queue Manager functionality. The RANCommandControlDSCPRef element specifies the Diffserv Codepoint to be applied to IP network-layer messaging associated with the Radio Access Network command and control operations. This includes all messages that use the RAN Command and Control Message format over all Radio Access Network interfaces, with the exception of the LM-QM interface. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | REDQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The REDQDiscType describes a Random Early Discard (RED)
classless Queuing Discipline (QDisc).
The Limit element, of type ValueUnitType, describes the maximum number of bytes that the queue can contain before dropping. The Min element, of type ValueUnitType, describes the average queue size (in bytes) at which marking becomes a possibility. The Max element, of type ValueUnitType, describes the average queue size (in bytes) at which the marking probability is maximal. The Avpkt element, of type ValueUnitType, describes the average packet size in bytes. The Burst element, of type xsd:unsignedInt, describes the size of traffic bursts (measured in number of packets) to be accommodated by the queue. The EnableECN element, of type xsd:boolean, describes whether Explicit Congestion Notification is enabled. The Bandwidth element, of type ValueUnitType, describes the rate (in kilobits per second) that is used for calculating the average queue size. The Probability element, of type Percentage, describes the maximum probability of marking, expressed as a percentage. An example Linux configuration using some of the options for a RED QDisc is: 'tc qdisc add dev eth1 parent 1:301 handle 40:0 red bandwidth 256 max 16000 min 5300 limit 128000 avpkt 1000 burst 9 probability 0.02' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ResultMeasurementsType |
|---|---|
| Abstract | no |
| Documentation | The ResultMeasurementsType element is the top-level container for an unbounded list of ResultMeasurement elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ResultMeasurementType |
|---|---|
| Abstract | no |
| Documentation |
The ResultMeasurementType is used to define which measurements
get their values from the result of the function.
The MeasurementRef element references the desired result measurement. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RoutesType |
|---|---|
| Abstract | no |
| Documentation | A Routes element contains a list of one or more Route elements which describe the network routes that are configured on the NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | RouteType |
|---|---|
| Abstract | no |
| Documentation |
A Route element describes a single network route configured on
a network interface of the NetworkNode.
A Destination element, of type mdl:IPAddress, describes the destination network of the route. A Netmask element, of type mdl:IPAddress, describes the netmask of the route. A Gateway element, of type mdl:IPAddress, describes the gateway address for the route. A Metric element, of type xsd:positiveInteger, describes the metric of the route. The NetworkInterfaceRef or RadioLinkRef identifies the network interface, either wired or wireless, to which the route applies. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < ScriptingLanguageEnum (by restriction) < ScriptingLanguageEnumExtType (by extension) |
|---|---|
| Sub-types: | None |
| Name | ScriptingLanguageEnumExtType |
|---|---|
| Abstract | no |
| Documentation | The ScriptingLanguageEnumExtType provides an extensible enumeration. If the value of the enumeration is "Extension", the attribute named "Extension" shall contain the chosen language's name and version. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ServiceLevelProfilesType |
|---|---|
| Abstract | no |
| Documentation | The ServiceLevelProfiles contains a list of one or more ServiceLevelProfile elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ServiceLevelProfileType |
|---|---|
| Abstract | no |
| Documentation |
The ServiceLevelProfile element represents the collection of
parameters that define the specific services to be provided by each
Radio bearer in the Radio Access Network (see Radio Bearer definition
below). A ServiceLevelProfile is primarily an RF Network Management
construct used for configuration and coordination of low-level network
services and data delivery functionality.
A Radio bearer represents the collection of services provided by the Radio Access Network to transfer data between the vehicle network and the ground network. A service is the collection of all means and facilities provided by the network to allow communication across the network. Radio bearers are used to organize the establishment and management of data transfers across the RAN segment so that appropriate QoS requirements can be supported. The Name element is used as a short, human-readable 'tag' to identify a ServiceLevelProfile. The Description element is a human-readable textual description of the bearer this ServiceLevelProfile describes, intended for display. The SLPHandle element is a 32-bit identifier used to reference the queue discipline or class associated with this SLP. The SLPHandle element value must be unique within an MSLP hierarchy. These fields represent the major/minor numbering scheme used by Linux traffic control to reference traffic engineering queues and classes. The most significant 16-bits represent the "major" number and the least significant 16-bits represent the "minor" number. By convention, the minor number is always 0 for qdiscs. For classes, the minor number must be a positive integer. A parent handle value of "0:0" imlies the root of the hierarchy. Note that an SLP instance is never explicitly defined for root. The AveragePacketDelay element, of type mdl:ValueUnitType, specifies the latency (measured in seconds) of the packet traversing the Radio Access Network. The Jitter element, of type mdl:ValueUnitType, specifies the allowed variation of packet delay (measured in seconds) measured over some period of time. The QueueConstruct element specifies the details of the queue discipline or class assoicated with this SLP. TrafficFilters are used as a flexible means of identifying and associating specific network packets with the bearer described by this ServiceLevelProfile. This will typically be some field or fields within the packet headers, including (but not limited to) IP source/destination address and port values, DiffServ codepoints. The ServiceLevelProfiles element is a container that holds additional ServiceLevelProfile information associated with this 'parent' ServiceLevelProfile and may be used to describe a hierarchy of service level profiles. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SFQQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The SFQQDiscType describes a Stochastic Fairness Queuing (SFQ)
classless Queuing Discipline (QDisc).
The Perturb element, of type ValueUnitType, describes how often (in seconds) the queue algorithm is perturbed. The Quantum element, of type ValueUnitType, describes the number of bytes a flow is allowed to dequeue during a round of the round robin process. An example Linux configuration using some of the options for a SFQ QDisc is: 'tc qdisc add dev eth1 parent 1:300 handle 30:0 sfq perturb 10' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SLPRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a SLPRef must refer to the ID attribute of a ServiceLevelProfileType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SMInterfaceType |
|---|---|
| Abstract | no |
| Documentation | The SMInterface element contains configuration information for the possible System Management interfaces of a NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SNMPSetupType |
|---|---|
| Abstract | no |
| Documentation |
The SNMPPort element, of type xsd:unsignedShort, may be used
to statically assign a port number to the SNMP agent for situations
where multiple NetworkNodes are running on the same network interface
of a shared hardware platform.
The DSCPTableEntryRef element describes DSCP settings for management data or management data requests sent by a NetworkNode or by a NetworkNodeManager. The DSCPTableEntryRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a DSCPTableEntry element. The NotificationPort element, of type xsd:unsignedShort, may be used to statically assign a port number to the SNMP agent on which it will receive notifications for situations where multiple NetworkNodes are running on the same network interface of a shared hardware platform. The Notifications element describes the settings for SNMP notifications that the containing TmNSApp is configured to send. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SNMPVersionsType |
|---|---|
| Abstract | no |
| Documentation | The SNMPVersionsType element contains one or more SNMPVersion elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTAssociationsType |
|---|---|
| Abstract | no |
| Documentation | The SSTAssociationsType element contains an unbounded list of SSTAssociationType elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTAssociationType |
|---|---|
| Abstract | no |
| Documentation |
The SSTAssociation element is used to describe a logical
association between ground and test article SST elements for a
particular test mission.
The Name element, of type xsd:token, is a human-readable name for the SSTAssociation. The Name element shall be unique within a TestMission. The Description element, of type xsd:string, is a text description of the association. The Active element, of type xsd:boolean, describes whether or not the association is active. The SSTChannelRef elements, of type SSTChannelRefType, contain references to the Channel elements within TmNSSSTRx and TmNSSSTTx elements. An SSTAssociation contains two or more SSTChannelRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTChannelRefsType |
|---|---|
| Abstract | no |
| Documentation | The SSTChannelRefsType element is the top-level container for an unbounded list of SSTChannelRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTChannelRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of an SSTChannelRefshall refer to the ID attribute of a Channel element within a TmNSSSTRx or TmNSSSTTx element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTRxChannelsType |
|---|---|
| Abstract | no |
| Documentation | The SSTRxChannelsType element is the top-level container for an unbounded list of SSTRxChannel elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTRxChannelType |
|---|---|
| Abstract | no |
| Documentation |
The SSTRxChannel element describes the channel number and the
center frequency of the RF channel.
The ChannelNumber element, of type xsd:positiveInteger, indicates the number of the channel. The CenterFrequency element, of type mdl:ValueUnitType, describes the center frequency with standard units of frequency (Hertz, or multiples of Hertz). The Bandwidth element, of type mdl:ValueUnitType, describes the bandwidth setting of the receiver. The Modulation element, of type SSTModuleationEnum, is an enumeration of possible modulation modes. The AutoGainMode element, of type xsd:boolean, describes whether the using an automatic or manual gain mode. The ManualGain element, of type ValueUnitType, describes the value and units of the manual gain, when used. The AGCTimeConstant element, of type ValueUnitType, describes the value and units of the AGC time constant. Refer to IRIG 106 Chapter 25 for the supported values. The ClockPolarityInverted element, of type xsd:boolean, describes the polarity of the bit sync TimeToLive clock output. The DataPolarityInverted element, of type xsd:boolean, describes the polarity of the bit sync TimeToLive data output. The SweepEnable element, of type xsd:boolean, describes the setting for the demodulator sweep. The SweepRangeLow element, of type xsd:ValueUnitType, describes the value and units (Hertz) for the lower limit of the sweep function. The SweepRangeHigh element, of type xsd:ValueUnitType, describes the value and units (Hertz) for the upper limit of the sweep function. The DiffDecoding element, of type xsd:boolean, indicates the differential decoding setting for the SST transmitter. The Derandomize element, of type xsd:boolean, indicates the data derandomization setting. The DataSourceSimulated element, of type xsd:boolean, describes whether the data source is simulated (true) or real (false). The InternalDataPattern element, of type xsd:unsignedInt, describes the data pattern produced by an internal source. The BitRate element, of type ValueUnitType, describes the bit rate of the receiver channel. The FECEnable element, of type xsd:boolean, indicates whether forward error correction is enabled. The FECType element, of type xsd:string, describes the type of forward error correction used. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SSTTxChannelType |
|---|---|
| Abstract | no |
| Documentation |
The CenterFrequency element, of type ValueUnitType, describes
the value and units (normally Hertz) of the center frequency of the
SST transmitter.
The Modulation element, of type SSTModuleationEnum, is an enumeration of possible modulation modes. The Deviation element, of type ValueUnitType, describes the deviation sensitivity for the PCM-FM modulation mode. The DiffEncoding element, of type xsd:boolean, indicates the differential encoding setting for the SST transmitter. The Randomize element, of type xsd:boolean, indicates the data randomization setting. The RFEnable element, of type xsd:boolean, describes if the RF output is on or off. The RFHighPowerEnable element, of type xsd:boolean, indicates whether the high power mode is enabled. The DataPolarityInverted element, of type xsd:boolean, indicates if the data polarity is normal (false) or inverted (true) The DataSourceInternal element, of type xsd:boolean, indicates wheter the data source is internal (true) or external (false). The InternalDataPattern element, of type xsd:unsignedInt, describes the data pattern produced by an internal source. The InternalClock element, of type xsd:boolean, indicates whether the internal clock is used. The ClockRate element, of type ValueUnitType, describes the clock rate, whether internal or external. The FECEnable element, of type xsd:boolean, indicates whether forward error correction is enabled. The FECType element, of type xsd:string, describes the type of forward error correction used. The SleepMode element, of type xsd:boolean, describes whether the transmitter is in a low power sleep mode. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SubModulesType |
|---|---|
| Abstract | no |
| Documentation | The SubModulesType element is the top-level container for an unbounded list of SubModule elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SubModuleType |
|---|---|
| Abstract | no |
| Documentation |
The SubModule element describes the properties of sub-module
or card in a DAU or other module. A SubModule is a physical
sub-component attached to the module, such as a daughter-card.
The Manufacturer element, of type xsd:string, contains the name of the manufacturer of the Device. The Model element, of type xsd:string, contains the model number of the module. The SerialID element, of type xsd:string, contains the model number of the module. The InventoryID element, of type xsd:token, describes the inventory identifier of the device. The Position element, of type xsd:nonNegativeInteger describes the slot number or the position of the module a stack of modules The Children element describes generic parent-child or master-slave relationships among the modules of a NetworkNode, between a NetworkNode and remote non-networked Device, or between non-networked Device elements. The relationship is intended to describe those where the parent is responsible for configuration or control of the child. The Connector element is a complex element that describes a physical connector on the module. The Ports element is a complex element that describes the points of logical connections to the the module. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SupportedMulticastAddressesType |
|---|---|
| Abstract | no |
| Documentation | The SupportedMulticastAddresses element contains a list of one or more SupportedMulticastAddress elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SupportedMulticastAddressType |
|---|---|
| Abstract | no |
| Documentation |
The SupportedMulticastAddress element describes the multicast addresses
that can be assigned to messages from TmNS network data sources. It
is expected that this list will often be established by or coordinated
with Range IT staff.
The Description element, of type xsd:string, is a human-readable identifier of the multicast address and its use. The MulticastAddress element, of type mdl:IPAddress, describes one supported multicast address. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SyllablesType |
|---|---|
| Abstract | no |
| Documentation | The SyllablesType element is the top-level container for an unbounded list of Syllable elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SyllableType |
|---|---|
| Abstract | no |
| Documentation |
The Syllable element describes a set of bits that are put into
a DataWord element. The Syllable element also describes the placement
of bits within the DataWord element. The data that is contained in a
Syllable element comes from either a MeasurementRef element or a
ConstantValue element. If the containing DataWord element contains
only a single Syllable element, and the DataWord element and the
Syllable element are of the same length, then no other elements are
needed for the description of the Syllable element. Otherwise, a
subset of the data described by the Syllable element can be selected
using the DataWordOffset, SyllableWidth, SyllableStartBit, and
SyllableMask elements. If the DataWord element contains only a single
Syllable element, and the SyllableWidth is not provided, it is assumed
that the length of the Syllable is the same as the length of the
DataWord.
The SyllableMask element, of type mdl:MaskType, describes a bit mask that is applied to the bits described by the Syllable element before the bits are placed within the containing DataWord element. This mask is applied with a bitwise AND operation. The SyllableWidth element describes the width or length of the Syllable element's bits that are to be placed within the containing DataWord element. The SyllableWidth element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. The value of the SyllableWidth element shall not exceed the size of the containing DataWord element. The SyllableStartBit element, of type xsd:positiveInteger, describes the starting bit location of the selected bits obtained from the Syllable element. These selected bits are then placed in the containing DataWord element. Beginning with the indicated start bit where the Least Significant Bit (LSB) is bit location one, the selected bits are the contiguous string of bits with a total length that matches the value of the SyllableWidth element. The DataWordOffset element, of type xsd:positiveInteger, describes the offset from the start of the containing DataWord element for the selected bits of the Syllable element. A value of "0" indicates that the selected bits of the Syllable element are inserted starting at the LSB of the DataWord element. If the DataWordOffset element is not present, then the value of the offset is assumed to be "0". When encoding a measurement into a data word, a series of syllables are created and placed in the data word. To encode a given syllable, first the SyllableMask is applied to the measurement's data. Then, the Syllable will take SyllableWidth bytes from the masked measurement with an offset of SyllableStartBit. Finally, the syllable is placed in the DataWord after the offset DataWordOffset. When decoding a data word into a measurement, the data word is broken down into its respective syllables which are reassembled into the original measurement. To decode a given syllable, first SyllableWidth bits are extracted from the data word at offset DataWordOffset. Then, the extracted bits are masked by the SyllableMask by offsetting them by SyllableStartBit within the mask. Each of the masked values created in this way are then ORed together in a reverse of the masking which extracted the syllables to recreate the original measurement. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TBFQDiscType |
|---|---|
| Abstract | no |
| Documentation |
The SFQQDiscType describes a Token Bucket Filter (TBF)
classless Queuing Discipline (QDisc).
The Limit element, of type ValueUnitType, describes the number of bytes that can be queued waiting for tokens to become available. The Burst element, of type ValueUnitType, describes the size of the token bucket, in bytes. This is the maximum amount of bytes for which tokens can be available instantaneously. The MPU element, of type ValueUnitType, describes the Minimum Packet Unit (specified in bytes), which determines the minimal token usage for a packet. The Rate element, of type ValueUnitType, describes a nominal rate limit (in kilobits per second) at which packets can be dequeued. The Peakrate element, of type ValueUnitType, describes the maximum burst rate (in kilobits per second) at which packets can be dequeued. The MTU element, of type ValueUnitType, describes the size (in bytes) of the peakrate bucket. An example Linux configuration using some of the options for a TBF QDisc is: 'tc qdisc add dev eth0 handle 2:0 parent 1:0 tbf burst 20480 limit 20480 mtu 1514 rate 32000bps' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TermType |
|---|---|
| Abstract | no |
| Documentation | The Term contains a Coefficient and an Exponent. The Exponent is applied to the input of the Polynomial, the result of which is multiplied by the Coefficient. If the Term describes a single constant term of a polynomial, the Exponent shall have the value of '0'. For the case where the term is equivalent to a constant 'A' multiplied by the input 'x', the Exponent shall have the value '1'. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TestMissionsType |
|---|---|
| Abstract | no |
| Documentation | The TestMissions element is the top-level container for an unbounded list of TestMission elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TestMissionType |
|---|---|
| Abstract | no |
| Documentation |
The TestMission element describes things that are specific to
a test. This varies dramatically from range to range. MDL allows
range policy to use TestMission to meet their needs. Precise use of
TestMission will not be standardized until commonality among ranges is
established. Every TestMission element shall contain a Name element,
of type xsd:token, that shall be unique within an MDL instance
document. The XML processor will remove line feeds, carriage returns,
tabs, leading and trailing spaces, and multiple spaces from all
elements of type xsd:token.
The TmNSCompleteness element, of type xsd:boolean, describes whether or not the containing TestMission element is a complete description of a test mission. The TmNSCompletenessDescription element, of type xsd:string, describes the degree of coverage of the containing TestMission element. The measure of coverage is with respect to the completeness of the description of a TestMission in an MDL Instance Document. The criteria against which completeness is measured are context-dependent. The NetworkReferences element contains a list of NetworkRef elements that indicate which Networks are participating in the TestMission. The QoSPolicies element is used to describe the mission-level quality of service parameters associated with the TestMission. The RadioLinks element is used to describe configuration parameters for any Radio Links associated with this test mission. The AssetAssociations element is used to describe the logical associations between ground and test article radio and SST elements for a particular test mission. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TimeAttributesType |
|---|---|
| Abstract | no |
| Documentation |
The TimestampFormat element is an enumeration of timestamp format
strings. Allowable values identify IRIG time codes, UTC, and IEEE 1588
versions.
The TimestampType element is an enumeration that identifies the type of timestamp, whether it is an absolute timestamp or a relative time offset from the Message/Package time. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TimestampDefinitionRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a TimestampDefinitionRef must refer to the ID attribute of a TimestampDefinition. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TimestampDefinitionType |
|---|---|
| Abstract | no |
| Documentation |
The TimestampDefinition element describes the properties and
format of a timestamp used within a network.
The TimestampFormat element describes the format of the timestamps defined by the TimestampDefinition element. The described timestamp format indicates how to interpret the ordering and scale factor of the values within a generated timestamp. For example, the selected format can indicate which values correspond to days, hours, minutes, or seconds. The Size element describes the size or length of the timestamp defined by a TimestampDefinition element. The Size element is an mdl:FlexibleLong value/units pair. The units for this element shall be in units of digital data lengths such as bits or bytes. The Resolution element, of type mdl:ConditionParameters, describes the smallest increment between the timestamp values defined by a TimestampDefinition element. The resolution of a timestamp is typically determined by the timescale because it defines the smallest measurable unit of time when generating a timestamp. The Resolution element contains any number of ConditionParameter elements. The Uncertainty element describes the level of uncertainty in the generated timestamp values. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSACUType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSACU element indicates that the
particular TmNSApp is an Antenna Control Unit.
The TrackingReceiver element, of type TmNSAppRefType, contains a reference to the TmNSSSTRx element that is used as the used by the antenna control unit for tracking the test article. The Azimuth and Elevation elements, of type ValueUnitType, describe the azimuth and elevation settings of the antenna being controlled by the ACU. The ServoEnergized element, of type xsd:boolean, indicates whether or not the servo is energized. The FeedEnabled element, of type xsd:boolean, indicates whether or not the feed is enabled. The AutoTrackingEnabled element, of type xsd:boolean, indicates whether or not the system is autotracking. The TrackingMode element, of type TrackingModeEnum, indicates the operating mode of the ACU tracking system. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSAppRefsType |
|---|---|
| Abstract | no |
| Documentation | The TmNSAppRefs element is a container for one or more TmNSAppRef elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSAppRefType |
|---|---|
| Abstract | no |
| Documentation | The TmNSAppRef element contains an IDREF attribute, of type xsd:IDREF, that shall reference the ID attribute of a TmNSAppType. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSAppsType |
|---|---|
| Abstract | no |
| Documentation | The TmNSApps element is a container for one or more TmNSApp elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSAppType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSApp element contains elements that describe characteristics and
configuration of an application that runs on a NetworkNode and is
manageable through the TmNS-based system.
The Name (type xsd:token) and Description (type xsd:string) elements may provide human readable information about the TmNSApp. The XML processor will remove line feeds, carriage returns, tabs, leading and trailing spaces, and multiple spaces from all elements of type xsd:token. The RoleID, of type xsd:token, shall be used to uniquely identify the TmNSApp. A RoleID shall be unique within a Network. The LoggingLevel element describes the System Management defined logging level used by the TmNSApp. The Manufacturer element, of type xsd:string, describes the manufacturer, or make, of the TmNSApp. The Product element, of type xsd:string, describes the product name or number assigned by the manufacturer. The ProductVersion element, of type xsd:string, describes the version number or name of the TmNSApp which may be a software version number or some other version information about the product. The ConfigurationVersion element, of type xsd:string, shall indicate the current configuration MDL Instance Document that the TmNSApp is configured with. The value shall be set to the string containing the value of the MDLRoot/ConfigurationVersion element, the value of the RoleID element, and the time it was configured. If the TmNSApp is not configured, then the value of this element shall be blank. The TmNSManagementResourcesVersion element, of type xsd:string, describes the version of the TmNS management resources with which this TmNSApp complies. The LastValidationDateTime element, of type xsd:dateTime, is used to optionally document the date/time validation of the MDL instance document occurred. The LastConfigurationDateTime element, of type xsd:dateTime, is used to optionally document the date/time the MDL instance document was used to configure a device. The DirtyBit element, of type xsd:boolean, is used in conjunction with reporting of the ConfigurationVersion element by a TmNSApp to indicate that one or more values in the reported MDL differ from the MDL file with which the TmNSApp was configured. Differences may be introduced through System Mangement interfaces, or other vendor specific interfaces. The ConfigurationVersion and DirtyBit elements combined faciliate configuration management of TmNSApps. The DirtyBit shall be set to true in a reported MDL file when configuration changes have been made that cause the MDL representation to differ from the last configuration via MDL. The DataBufferLength element describes the length of available (stored) data, in units of time, of the NetworkNode. This value indicates the oldest data that can be requested from the NetworkNode. A NetworkNode that does not have a backlog of data may specify the value of this element to be zero. The DataBufferLength element is a floating-point value/units pair. The TmNSApp element may contain additional elements that indicate the TmNSApp is operating as a special kind of TmNSApp. The element names all begin with 'TmNS'. The SMInterface element contains configuration information for the System Management interface of a NetworkNode. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSConsolidatedManagerType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSConsolidatedManager element is an element that can be contained
by a TmNSApp element to describe a TmNSApp that has the ability to
function as a TMAManager.
A TmNSConsolidatedManager element can contain a ManagedApps element, of type mdl:TmNSAppRefsType, that contains a list of one or more TmNSAppRef elements, each of which references the ID attribute of a TmNSApp element. The meaning is that the TmNSApp containing the TmNSConsolidatedManager element manages this set of TmNSApps. The DeviceAutoDiscovery element may be used to describe a TmNSConsolidatedManager that performs device auto discovery through a broadcast ping or through a ping sweep of IP addresses. If the element is present, the manager performs auto discovery, otherwise it does not. The FTPServerURI element may be used to statically configure the ftp address of the MDL instance document(s) that will be written or retrieved. The DeviceStatusMonitoringPeriod element of type mdl:ValueUnitType may be used to describe how long, in seconds, the manager should wait between performing status monitoring on a device. The DeviceComunicationProbationTimeoutAttempts element of type xsd:unsignedLong may be used to describe the number of SNMP queries that a manager attempts before declaring a communication probation fault. The DeviceComunicationFailureTimeoutAttempts element of type xsd:unsignedLong may be used to describe the number of device communication probation attempts that a manager executes before declaring a communication failure fault. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSDAUType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSDAU element indicates that the particular TmNSApp is a Data Acquisition Unit. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSEncryptorType |
|---|---|
| Abstract | no |
| Documentation | The presence of an TmNSEncryptor element indicates that the particular TmNSApp can function as an encryptor. The RedNetworkInterfaceRef and BlackNetworkInterfaceRef, of type mdl:NetworkInterfaceRef, indicate which NetworkInterface of the NetworkNode transports the encrypted and unencrypted data respectively. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSLinkManagerType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSLinkManager element is an element that can be
contained by a TmNSApp element to describe a TmNSApp that has
the ability to function as a Link Manager in the RF Network.
The RANConfigurationRef element refers to the RAN configuration on which the RFNM operates. The TxOpUpdateRate element specifies the number of Epochs that the TmNSLinkManager will wait before sending the next TxOp TLV. By setting this element to 0, TxOps will be generated for each Epoch by the TmNSLinkManager. A TmNSLinkManager element can contain a ManagedApps element, of type mdl:TmNSAppRefsType, that contains one or more TmNSAppRef elements, each of which references the ID attribute of a TmNSApp element that corresponds with the Radio components of the RF Network. The meaning of this is that the and Radio resources are managed by the Link Manager. The TSSRemoteIPAddress element, of type IPAddress, defines the IP Address where the TmNSTSS managable app can be located. This element is required when the TmNSLinkManager is not defined under the same NetwokNode as the TmNSTSS and therefore is not running the TmNSTSS locally. This is used with the TSSRemoteControlPort element to send control messages the to remote TmNSTSS. The TSSRemoteControlPort element, of type xsd:unsignedShort, defines the port where control messages to a remote TmNSTSS managable app can be directed. This element is required when the TmNSLinkManager is not defined under the same NetwokNode as the TmNSTSS and therefore is not running the TmNSTSS locally. This is used with the TSSRemoteIPAddress element to send control messages to the remote TmNSTSS. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSLTCDataSinkType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSLTCDataSink element indicates that the particular TmNSApp is an LTC Data Sink. The TmNSLTCDataSink contains the list of all MDIDs that the LTCSink is instructed to collect. The NetworkInterfaceRef may be used to indicate which NetworkInterface is being used by the LTCDataSink for NetworkNodes with one or more NetworkInterfaces. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSLTCDataSourceType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSLTCDataSource element indicates that the particular TmNSApp is an LTC Data Source. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSMasterClockType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSMasterClock element indicates that the
particular TmNSApp is a master clock.
The IEEE1588MasterCapabilityEnable element, of type xsd:boolean, describes whether the time master capability is enabled or disabled on the containing NetworkNode. The TimeSourceType element is an enumeration that describes whether the time source is an internal oscillator or an external time source. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSMeasurementProcessorType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSMeasurementProcessor element indicates that
the TmNSApp is capable of measurement data processing.
The TmNSMeasurementProcessor may contain a MeasurementRefs element that describes the measurements the MeasurementProcessor is instructed to process. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSMFDType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSMFD element indicates that the particular TmNSApp is a multifunction display. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSNetworkFabricDeviceType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSNetworkFabricDevice element indicates
that the particular TmNSApp is a NetworkFabricDevice, and thus
implements the TmNSNetworkFabricDevice management resources. It does
not imply any further Network Device specialization. A Network Fabric
Device provides network and/or data link layer service and
interconnectivity without modifying data above the network layer. See
Open Systems Interconnection (OSI) model. Example
TmNSNetworkFabricDevices are routers and switches.
The MulticastRoutingMode element, of type MulticastRoutingModeEnum, describes the mode of multicast routing, whether it is static, dynamic, or static and dynamic. The IGMPQuerier element, of type IGMPQuerierEnum, is an enumeration that describes the mode of the IGMP Querier, whether it is on, off, or auto. The IGMPQuerierInterval element, of type xsd:unsignedInt, is an unsigned 32-bit number that describes the number of seconds between IGMP queries. The TmNSNetworkFabricDevice element may contain zero or more StaticMulticast elements to describe static multicast addresses configured on the device. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSNullType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSNull element indicates that the particular node/SNMP agent is a NullNode. This indicates that the device is present in a TmNS-based system, but it does not implement the TmNS. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSRadioType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSRadio element indicates that the particular
TmNSApp can function as a TmNSRadio in a TmNS-based system.
The RANConfigurationRef element refers to the RAN configuration on which the radio operates. The RFMACAddress element is a 16-bit value that shall be globally unique. The FragmentationPersistencePeriodUSec, of type xsd:unsignedInt, describes the maximum time in microseconds that received frames can be buffered pending reassembly of fragmeted payload. After expiration of the time, fragments may be discarded. The TxPowerLeveldBm element, of type xsd:unsignedInt, describes the "normal" power level setting of the radio. The LowPowerModeEnable element, of type xsd:boolean, describes when the radio is put into a low power mode. If set to true, the low power mode overrides the power level set in the TxPowerLeveldBm element. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSRCDataSinkType |
|---|---|
| Abstract | no |
| Documentation |
The presence of a TmNSRCDataSink element indicates that
the TmNSApp is operating as an RC Data Sink.
The NetworkInterfaceRef may be used to indicate which NetworkInterface is being used by the RCDataSink for NetworkNodes with one or more NetworkInterfaces. The TmNSRCDataSink may contain a list of zero or more MessageDefinitionRefs, PackageDefinitionRefs, and MeasurementRefs elements that describe the messages, packages, and measurements that the RCSink is instructed to collect. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSRCDataSourceType |
|---|---|
| Abstract | no |
| Documentation |
The presence of the TmNSRCDataSource element indicates that
the TmNSApp is operating as an RC Data Source.
The NetworkInterfaceRef may be used to indicate which NetworkInterface is being used by the RCDataSource for NetworkNodes with one or more NetworkInterfaces. The ListeningPort may be used to describe the IP port on which the RC Data Source is listening, whether using the standard port or another. The TmNSRCDataSource may contain a list of zero or more MessageDefinitionRefs, PackageDefinitionRefs, and MeasurementRefs elements that describe the messages, packages, and measurements that the RCSource is instructed to generate. RC Data Source needs to be aware of all MDIDs, PDIDs, and MeasIDs in the domain so that when a request comes in it can either build the message or reject it. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSRecorderType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSRecorder element indicates that the particular TmNSApp is a Recorder. A Recorder consists of TmNSLTCDataSink and TmNSRCDataSource components. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSSSTRxType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSSSTRx element indicates that the particular TmNSApp can function as an SST receiver. The list of Channel elements indicate the RF channels available for receiving. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSSSTTxType |
|---|---|
| Abstract | no |
| Documentation | The presence of a TmNSSSTTx element indicates that the particular TmNSApp can function as an SST transmitter.The SSTTxRCCVersion element, of type xsd:string, describes the IRIG version supported by the SST transmitter. The Channel element, of type SSTTxChannelType, describes the attributes of a transmitter channel. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSTSSClientType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSTSSClient element is an element that can be contained by a
TmNSApp element to describe a TmNSApp that has the ability to
define configuration information for the Network Management with respect
to routing as coordinated by the TmNSLinkManager concepts.
The TSSTunnels element is a container for an unbounded list of TSSTunnel elements. The PacketCatalogSize element defines the maximun number of IP packets the TmNSTSSClient will maintain in its buffer to be used to detect and squelch duplicate packets. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSTSSServerType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSTSSServerType element is an element that can be contained by a
NetwokNode element to describe an interface that a TmNSTSSClient will
establish a TSSTunnel with.
The TSSTunnelConnections element is a container for an unbounded list of TSSTunnelConnection elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TmNSVoiceGatewayType |
|---|---|
| Abstract | no |
| Documentation |
The TmNSVoiceGateway element is an element that can be
contained by a TmNSApp element to describe a TmNSApp that has
the ability to function as a TmNSVoiceGateway in a TmNS-based system.
The VoiceDSCPTableEntryRef, of type mdl:DSCPTableEntryRefType, contains an IDREF attribute that refers to the ID attribute of the DSCPTableEntry that describes the DSCP markings for the voice data traffic. The ControlDSCPTableEntryRef, of type mdl:DSCPTableEntryRefType, contains an IDREF attribute that refers to the ID attribute of the DSCPTableEntry that describes the DSCP markings for the control data traffic. The CodecPriorities element contains a prioritized list of codecs to be used for voice traffic. The PhoneNumbers element contains a list of VoIP client names and their corresponding phone numbers. The SIPServerIPAddress and SIPServerPort elements, of types IPAddress and xsd:unsignedShort respectively, specify the IP Address and port that the SIP Server is listening on. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TOSBandAssignmentType |
|---|---|
| Abstract | no |
| Documentation |
The TOSBandAssignment describes the assignment of packets with
specific Type Of Service (TOS) priority bits to their assigned bands
(represented using the minor numbers of the PRIO classes).
The TOS element describes the "Type Of Service" priority field in the packet headers that will be assigned to a particular band. The Band element describes the band to which the packect will be assigned. Unlike PRIO classes, band reference numbers start from 0. For example, if a PRIO qdisc is created with 4 bands, the possible range of TOS Band Assignment values is [0,N-1], where N is the total number of bands. The maximum number of bands is 16. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TrafficFilterConditionsType |
|---|---|
| Abstract | no |
| Documentation | The Condition element, of type mdl:TrafficFilterConditionType, contains a list of one or more TrafficFilterConditionChoice elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TrafficFilterConditionType |
|---|---|
| Abstract | no |
| Documentation |
The TrafficFilterCondition element describes the attributes
which will be used to uniquely identify the data traffic associated
with a particular ServiceLevelProfile.
The MatchField element describes matching a pattern and mask against an 8, 16, or 32-bit field. The DSCPTableEntryRef refers to the DSCPTableEntry that describes the DSCP markings of the IP packets to filter. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TrafficFiltersType |
|---|---|
| Abstract | no |
| Documentation | TrafficFilters contains a list of one or more TrafficFilter elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TrafficFilterType |
|---|---|
| Abstract | no |
| Documentation |
The TrafficFilterType element is used to describe traffic
filtering conditions.
OR conditions are created by specifying two separate filters, while AND conditions are created by specifying multiple conditions within a single filter element. Any packets that match all of the filter conditions are sent to the class indicated by the handle of the SLP where this traffic filter is defined. When working in a Cisco context, the Name element may be used to supply a name for a traffic 'class map' (i.e. filter). When working in a Cisco context, the Description element may be used to supply a name for a traffic 'class map' (i.e. filter). The ParentQDiscHandle element, of type mdl:ThirtyTwoBit, contains the SLPHandle of the parent queuing discipline for this filter The Protocol element defines the protocol/OSI layer that this filter applies to. Filter Priority indicates the order of filter execution. The Condition element is a sequence of one or more traffic filter conditions. All of the conditions must be met to declare a match. An example Linux configuration using some of the options for a Traffic Filter is: 'tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32 match u8 0xe0 0xe0 at 1 classid 1:10' |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TransmissionScheduleType |
|---|---|
| Abstract | no |
| Documentation | The TransmissionSchedule element is used to describe a static schedule of transmit opportunities (TxOps) and contention periods. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSClientType |
|---|---|
| Abstract | no |
| Documentation |
The TSSClientType identifies the TmNSTSSClient that will be establishing the
TSSTunnel with the TmNSTSSServer.
The NetworkInterfaceRef, of type NetworkInterfaceRefType, identifies the IP address of the TmNSTSSClient that will be establishing the TSSTunnel with the TmNSTSSServer. The TSSTunnelInterfaceRef, of type VirtualNetworkInterfaceRefType, identifies the IP configuration of the TSSTunnelInterface of the TmNSTSSClient. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSNetworkGatewayType |
|---|---|
| Abstract | no |
| Documentation |
The TSSNetworkGateway element describes the TmNSLinkManager that acts
as the gateway to separate RANConfiguration where the TSSRouteDestination
resides.
The DestinationRadioRef element, of type TmNSAppRefType, indicates the specific TmNSRadio that is the TSSRouteDestination. This provides the destination RFMACAddress of the RadioLink managed by the other TmNSLinkManager. The DestinationRadioGroupRef element, of type RadioGroupRefType, indicates the GroupRFMACAddress subscribed to by the TmNSRadio that is the TSSRouteDestination. The TmNSLinkManagerAppRef element, of type TmNSAppRefType, indicates the specific TmNSLinkManager that is the TSSNetworkGateway to the other RANConfiguration. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSRouteDestinationsType |
|---|---|
| Abstract | no |
| Documentation | The TSSRouteDestinationsType element is a container for an unbounded list of TSSRouteDestination elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSRouteDestinationType |
|---|---|
| Abstract | no |
| Documentation |
The TSSRouteDestination element describes a single destination network
that shall be routed through the TSSTunnel. The TSSRouteDestination
element specifies either a RadioLinkRef or a TSSNetworkGateway to
indicate whether the path to the destination network is through a
RadioLink on the TmNSLinkManagers RANConfiguration or through a
TmNSLinkManager managing another RANConfiguration respectively.
The RadioLinkRef element, of type RadioLinkRefType, indicates the specific RadioLink managed by the the TmNSLinkManager that represents the path to the destination network. When this RadioLink is that active path to the destination network, the described TSSTunnel will be selected. The TSSNetworkGateway element, of type TSSNetworkGatewayType, indicates the specific TmNSLinkManager that represents the gateway to another RANConfiguration where the destination network resides. When this TSSNetworkGateway is that active path to the destination network, the described TSSTunnel will be selected. The NetworkInterfaceRefs element, of type NetworkInterfaceRefsType, specifies an unbounded list of NetworkInterfaces that represent the TSSRouteDestinations to be routed through the described TSSTunnel. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSRoutesType |
|---|---|
| Abstract | no |
| Documentation | The TSSRoutes element is a container for an unbounded list of TSSRoute elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSRouteType |
|---|---|
| Abstract | no |
| Documentation | The TSSRoute element specifies the IP subnet and netmask of the route destination network. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSServerType |
|---|---|
| Abstract | no |
| Documentation |
The TSSServer element describes the TmNSTSSServer that the TmNSTSSClient
will connect to.
The NetworkInterfaceRef element, of type NetworkInterfaceRefType, indicates the specific NetworkInterface on the TmNSTSSServer that the TmNSTSSClient will establish the TSSTunnel on. The TSSTunnelConnectionRef element, of type TSSTunnelConnectionRefType, indicates the TmNSTSSServer configuration for the incoming TSSClientConnection from the TmNSTSSClient. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSTunnelConnectionRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a TSSTunnelConnectionRef shall refer to the ID attribute of a TSSTunnelConnection. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSTunnelConnectionsType |
|---|---|
| Abstract | no |
| Documentation | The TSSTunnelConnections element is a container for an unbounded list of TSSTunnelConnection elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSTunnelConnectionType |
|---|---|
| Abstract | no |
| Documentation |
The TSSTunnelConnection element describes a single TSSTunnelConnectionInterface,
the TSSClient, the DataPort, and the TSSRoutes that are used to accept a
TSSTunnelConnection from a TSSClient. The TSSTunnel will be used to pass
all IP traffic between the TmNSTSSServer App and the TmNSTSSClient App.
The TSSTunnelConnectionInterface element, of type VirtualNetworkInterfaceType, defines a single virtual interface that is generated on the NetworkNode. This virtual interface is used by the TmNSTSSServer to accept a TSSTunnelConnection from a TmNSTSSClient. The DataPort element, of type xsd:unsignedShort, defines the listening port used by the NetwokNode for the specified TSSTunnelConnection. The TSSRoutes element is a container for an unbounded list of TSSRoute elements. The BlacklistOfIPAddresses element is a container for an unbounded list of BlacklistIPAddress elements. |
| Relations |
Used in:
Referenced by: |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSTunnelsType |
|---|---|
| Abstract | no |
| Documentation | The TSSTunnels element is a container for an unbounded list of TSSTunnel elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TSSTunnelType |
|---|---|
| Abstract | no |
| Documentation |
The TSSTunnel element describes a single TSSTunnelInterface, the
TSSServer, and the TSSRouteDestinations that are used to establish
the TSSTunnel with the TSSServer. The TSSTunnel will be used to pass
all IP traffic between the TmNSTSSServer app and the TmNSTSSClient app.
The TSSTunnelInterface element, of type VirtualNetworkInterfaceType, defines a single virtual interface that is generated on the TmNSTSSClient platform. This TSSTunnelInterface is used to establish a TSSTunnel to the TmNSTSSServer. The TSSServer element, of type TSSServerType, describes the TmNSTSSServer that the TmNSTSSClient will establish the TSSTunnel with. The TSSRouteDestinations element is a container for an unbounded list of TSSRouteDestination elements. The Enabled element, of type xsd:boolean, specifies whether the TSSTunnel should be established at configuration or not. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TxOpType |
|---|---|
| Abstract | no |
| Documentation |
The TxOp element describes one entry in a static epoch
schedule table.
The CenterFrequencyHz element specifies the center frequency (in Hertz) for this TxOp. The StartUSec element describes a "start" time (in microseconds) relative to epoch start time. If the Assignment element is set to "ContentionPeriod", then this value describes the earliest time that this transmission can occur. The entity setting this value is responsible for deconflicting a contention period by allocating adequate guard band for maximum distance to all radios. If the Assignment element is set to "TxOp", then this value describes the earliest time that a receiver can expect this transmission. In the case of a TA to GS transmission, the TA must adjust the actual transmission time to compensate for propagation delay, thus ensuring reception at the time indicated by StartUSec. This value is designed for use in a 40-bit field. Units are in microseconds. The StopUSec element describes a "stop" time (in microseconds) relative to the epoch start time by which transmissions must be stopped. The entity setting this value is responsible for de-conflicting a contention period by allocating adequate guard band for maximum distance to all radios. In the case of TA to GS transmission, the TA must adjust the actual transmission time to compensate for propagation delay, thus ensuring reception ends by the time indicated by StopUSec. The TxOpTimeout element specifies the lifetime of a TxOp TLV in terms of Epochs. This element can be set to an integer value in the range [0, 255]. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | UncertaintiesType |
|---|---|
| Abstract | no |
| Documentation | The UncertaintiesType element is the top-level container for an unbounded list of Uncertainty elements. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | UncertaintyType |
|---|---|
| Abstract | no |
| Documentation |
The Uncertainty element describes the uncertainty through a
confidence level over a specified confidence interval.
The ConfidenceInterval element, of type mdl:ConditionParametersType, contains any number of ConditionParameter elements and describes the bounds over which the confidence level apply. The ConfidenceLevel element is a percentage represented as an integer in the range from "0" to "100" inclusive. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | UnitRefType |
|---|---|
| Abstract | no |
| Documentation | The UnitRef element contains an IDREF attribute that shall refer to the ID attribute of a DerivedUnit. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | UnitsType |
|---|---|
| Abstract | no |
| Documentation | The Units element is the top-level container for an unbounded list of DerivedUnits. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | UnitTermType |
|---|---|
| Abstract | no |
| Documentation | The UnitTermType is a container for a scalar multiplier (NumericalConstant) and an BaseUnit or a UnitRef to a previously created DerivedUnit. As an example, millimeters (mm) can be represented by the numerical constant 0.001 multiplied by the SI unit meter. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ValueUnitType |
|---|---|
| Abstract | no |
| Documentation | The ValueUnitType is a generic container for either an mdl:FlexibleLong or xsd:double value with assigned units of measure. The UnitRef and BaseUnit elements describe the units of measure for the ValueUnit. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | VirtualNetworkInterfaceRefType |
|---|---|
| Abstract | no |
| Documentation | The value of the IDREF of a VirtualNetworkInterfaceRef shall refer to the ID attribute of a VirtualNetworkInterface within the same NetworkNode. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | VirtualNetworkInterfaceType |
|---|---|
| Abstract | no |
| Documentation |
A VirtualNetworkInterface describes a network interface that can be
created on a NetwokNode. This interface is not related to a physical
netowrk interface on the NetwokNode.
A IPAddress element, of type mdl:IPAddress, describes the IP address of the VirtualNetworkInterface. A Netmask element, of type mdl:IPAddress, describes the netmask of the VirtualNetworkInterface. The MACAddress element, of type mdl:MACAddress, describes the MAC address of the VirtualNetworkInterface. |
| Relations |
Used in:
Referenced by: None |
| References |
| Super-types: | xsd:string < AlgorithmType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | AlgorithmType |
|---|---|
| Content |
|
| Documentation |
The AlgorithmType contains a string of the format described in
IRIG 106 Appendix P: Derived Parameter Specification. Note that this
grammar is too complex to validate within XML, so a simple string
datatype has been used, and validation of this field is left up to the
processor of the MDL instance document.
If a constant value with units is required, and traceability of the specific units is required which prevents the use of a unitless numeric constant, a constant value measurement with the desired units can be used. |
| Super-types: | xsd:string < BandTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | BandTypeEnum |
|---|---|
| Content |
|
| Documentation | The BandType element is an enumeration that can be set to one of the following values: PassBand, StopBand, TransitionBand |
| Super-types: | xsd:string < BaseUnitEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | BaseUnitEnum |
|---|---|
| Content |
|
| Documentation | The BaseUnit element is an enumeration that can be set to the following list of standard SI units, special derived SI units, and some other fundamental, non-SI units. The value "Unitless" should be used for a fractional term that has no units. |
| Super-types: | xsd:string < BinInteger (by restriction) |
|---|---|
| Sub-types: | None |
| Name | BinInteger |
|---|---|
| Content |
|
| Documentation | The mdl:BinInteger data type is an arbitrarily long string of binary digits. It is an xsd:string containing a prefix string of "0b" followed by a string of characters of binary digits ('0' and '1'). An example value of the mdl:BinInteger data type would be "0b10101101", which is an 8-bit binary representation of the decimal number 173. |
| Super-types: | xsd:string < CaptureModeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | CaptureModeEnum |
|---|---|
| Content |
|
| Super-types: | xsd:string < ConditionOperationEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ConditionOperationEnum |
|---|---|
| Content |
|
| Documentation | The ConditionOperation is an enumeration that represents "greater than" (">"), "greater than or equal" (">="), "less than" ("<"), "less than or equal" ("<="), "equal to" ("=="), or "not equal to" ("!="). |
| Super-types: | xsd:string < DeliveryClassEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | DeliveryClassEnum |
|---|---|
| Content |
|
| Documentation | The DeliveryClass element is an enumeration of type mdl:DeliveryClassEnum that can be set to one of the following values: "Voice", "FlightSafety", or "BestEffort" |
| Super-types: | xsd:string < DeviceTypeEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | DeviceTypeEnum |
|---|---|
| Content |
|
| Documentation | The DeviceType element is an extensible enumeration of the supported non-TmNS devices, such as transducers and thermocouples. |
| Super-types: | xsd:string < DigitalEncodingEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | DigitalEncodingEnum |
|---|---|
| Content |
|
| Documentation | The DigitalEncodingEnum element is an enumeration that can be set to one of the following values: "BCD", "Two'sComplement", "One'sComplement", "UnsignedBinary", "SignedBinary", "IEEE754SinglePrecision", "IEEE754DoublePrecision" |
| Super-types: | xsd:string < EndiannessEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | EndiannessEnum |
|---|---|
| Content |
|
| Documentation | The mdl:EndiannessEnum element is an enumeration that can be set to one of the following values: LittleEndian or BigEndian |
| Super-types: | xsd:integer < EpochSizeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | EpochSizeEnum |
|---|---|
| Content |
|
| Documentation | The EpochSizeEnum is an enumeration that lists the available epoch sizes, representing epoch duration (in milliseconds). For epoch rates below 50 ms, compatibility will have to be determined as RAN components mature. |
| Super-types: | xsd:string < ExcitationSourceType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ExcitationSourceType |
|---|---|
| Content |
|
| Super-types: | xsd:string < FieldWidthEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | FieldWidthEnum |
|---|---|
| Content |
|
| Documentation | The FieldWidthEnum element indicates size, in bits, of the traffic filter field. |
| Super-types: | xsd:string < FilterClassifierEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | FilterClassifierEnum |
|---|---|
| Content |
|
| Documentation | The FilterClassifierEnum element indicates the type of classifier that applies to the filter. |
| Super-types: | xsd:string < FilterModeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | FilterModeEnum |
|---|---|
| Content |
|
| Documentation | The FilterMode element is an enumeration of the supported modes for filtering bus messages. |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | FlexibleLong |
|---|---|
| Content |
|
| Documentation | The mdl:FlexibleLong data type is an xsd:union of the xsd:long (64-bit signed integers), mdl:BinInteger, and mdl:HexInteger data types. |
| Super-types: | xsd:string < FourBitHex (by restriction) |
|---|---|
| Sub-types: | None |
| Name | FourBitHex |
|---|---|
| Content |
|
| Documentation | The mdl:FourBitHex data type is an xsd:string with a prefix "0x"followed by one character of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f'). An example value of the mdl:FourBitHex data type would be "0xa" or "0xA" which is a 4-bit hexadecimal representation of the decimal number 10. |
| Super-types: | xsd:string < GroupTypeEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | GroupTypeEnum |
|---|---|
| Content |
|
| Documentation | The GroupTypeEnum is an extensible enumeration describing the type of measurement group. |
| Super-types: | xsd:string < HexInteger (by restriction) |
|---|---|
| Sub-types: | None |
| Name | HexInteger |
|---|---|
| Content |
|
| Documentation | The mdl:HexInteger data type is an arbitrarily long string of hexadecimal digits. It is an xsd:string containing a prefix string of "0x" followed by a string of characters of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f'). An example value of the mdl:HexInteger data type would be "0xAD" or "0xad", which is an 8-bit hexadecimal representation of the decimal number 173. |
| Super-types: | xsd:string < IEEE1588VersionEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IEEE1588VersionEnum |
|---|---|
| Content |
|
| Documentation | The IEEE1588Version element, of type xsd:string, describes the version of the IEEE 1588 Precision Time Protocol (PTP) on the NetworkNode. Valid values are "2002", "2008e2e" (for end-to-end), "2008p2p" (for peer-to-peer), and "Multiple". If "Multiple" is set on the NetworkNode, each PhysicalNetworkPort in the NetworkNode shall contain the IEEE1588VersionOfPort element. If "Multiple" is not set on the NetworkNode, the PhysicalNetworkPort shall not contain the IEEE1588VersionOfPort element. |
| Super-types: | xsd:string < IEEE1588VersionOfPortEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IEEE1588VersionOfPortEnum |
|---|---|
| Content |
|
| Documentation | The IEEE1588Version element, of type xsd:string, describes the version of the IEEE 1588 Precision Time Protocol (PTP) on the NetworkNode. Valid values are "2002", "2008e2e" (for end-to-end), and "2008p2p" (for peer-to-peer). |
| Super-types: | xsd:string < IGMPQuerierEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IGMPQuerierEnum |
|---|---|
| Content |
|
| Documentation | The IGMPQuerier element is an enumeration of settings for the IGMP Querier. |
| Super-types: | xsd:string < InfinityEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | InfinityEnum |
|---|---|
| Content |
|
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | IPAddress |
|---|---|
| Content |
|
| Documentation | The mdl:IPAddress data type is an xsd:union of the mdl:IPv4Address and mdl:IPv6Address data types. |
| Super-types: | xsd:string < IPv4Address (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IPv4Address |
|---|---|
| Content |
|
| Documentation | The mdl:IPv4Address data type is an xsd:string of decimal digits separated by '.' (period) characters. It represents the 32-bit dot-decimal notation of IPv4 addresses. Valid IPv4 addresses contain a series of four one-byte long decimal numbers (0 - 255) separated by the '.' character (a total of three '.' characters appear). A valid value of the mdl:IPv4Address data type is "212.23.123.0". See RFC 790 in Section 2.2.2 for further details on IPv4 addresses. |
| Super-types: | xsd:string < IPv6Address (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IPv6Address |
|---|---|
| Content |
|
| Documentation | The mdl:IPv6Address data type is an xsd:string of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f') separated by ':' (colon) characters. It represents the 128-bit notation of IPv6 addresses. Fully expanded IPv6 addresses contain a series of eight two-byte long hexadecimal numbers separated by the ":" character (a total of seven ':' characters appear). A single two-byte long hexadecimal number contains up to four hexadecimal digits. All valid IPv6 addresses are supported in the MDL. A valid value of the mdl:IPv6Address data type is "2001:DB8:0000:0056:0000:ABCD:EF12:1234". See RFC 2460 for further details on IPv6 addresses and valid shorthand notations. |
| Super-types: | xsd:string < IRIGTimecodes (by restriction) |
|---|---|
| Sub-types: | None |
| Name | IRIGTimecodes |
|---|---|
| Content |
|
| Documentation | The IRIGTimecodes is a restricted xsd:string with valid values that conform to the listed regular expression pattern. The regular expression supports the entry of all IRIG timecode formats as defined in RCC Document 200-04. However, the entered format string is valid only if it is defined in the reference document. Not all of timecode format types (e.g., IRIG format "E") support all possible combinations of the format control codes (e.g., "IRIG E211" is an undefined format). |
| Super-types: | xsd:unsignedInt < LDPCBlocksPerBurstType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | LDPCBlocksPerBurstType |
|---|---|
| Content |
|
| Documentation | The mdl:LDPCBlocksPerBurstType data type is a unsigned integer. Valid values range from 1 to 16. |
| Super-types: | xsd:string < LinkTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | LinkTypeEnum |
|---|---|
| Content |
|
| Documentation |
The LinkTypeEnum is an enumeration that is used to
select the type of link. The LinkTypeEnum can be
set to any of the following values: "Uplink",
"Downlink", "Relay Uplink", "Relay Downlink", or "Ad Hoc".
An "Uplink" type refers to a Radio Link whose data transmission direction is from the ground to the air. A "Downlink" type refers to a Radio Link whose data transmission direction is from the air to the ground. A "Relay Uplink" type refers to a Radio Link whose data transmission direction with respect to the Ground is away from the Ground and the source Radio is at least one Radio hop from the Ground. A "Relay Downlink" type refers to a Radio Link whose data transmission direction with respect to the Ground is towards the Ground and the source Radio is at least two Radio hops from the Ground. An "Ad Hoc" type refers to a Radio Link whose data transmission direction is irrelevent. |
| Super-types: | xsd:string < LoggingLevelEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | LoggingLevelEnum |
|---|---|
| Content |
|
| Documentation |
The LoggingLevel element indicates the current logging level
mask settings. All TmNS components shall have logging capabilities.
TmNS components shall implement the following six logging levels, and
the TmNSApp shall enable the specified level and all levels above the
specified level.
1. Trace (the least serious) 2. Debug 3. Info 4. Warning 5. Error 6. Critical (the most serious) 7. None (no logging will be recorded) |
| Super-types: | xsd:string < MACAddress (by restriction) |
|---|---|
| Sub-types: | None |
| Name | MACAddress |
|---|---|
| Content |
|
| Documentation | The mdl:MACAddress data type is an xsd:string of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f') separated by either the ':' (colon) or '-' (hyphen) character. It represents the 48-bit Media Access Control (MAC) address identifier. Valid MAC addresses contain a series of six one-byte long hexadecimal numbers separated by either the ':' or the '-' character (a total of five ':' or '-' characters appear). A valid value of the mdl:MACAddress data type is "01:23:45:67:89:AB" or "01-23-45-67-89-AB". |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | MaskType |
|---|---|
| Content |
|
| Documentation | The mdl:MaskType data type is an xsd:union of the mdl:BinInteger and mdl:HexInteger data types. |
| Super-types: | xsd:string < MeasurementTypeEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | MeasurementTypeEnum |
|---|---|
| Content |
|
| Documentation |
The MeasurementType element is an enumeration that describes the
basic kind of measurement. Some example values are Analog, Discrete,
DigitalBus, Computed, Time, Video, etc.
If "Analog" or "Discrete" is selected, the AnalogAttributes element shall be used to describe the Measurement element. If "DigitalBus" or "Computed" is selected, the DigitalAttributes element shall be used to describe the Measurement element. If "Time" is selected, the TimeAttributes element shall be used to describe the Measurement element. |
| Super-types: | xsd:string < MediumEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | MediumEnum |
|---|---|
| Content |
|
| Documentation | The Medium element describes the physical medium used by the port to transfer data. The Medium element is an enumeration that can be set to one of the following values: Copper, Fiber, Wireless |
| Super-types: | xsd:string < MulticastRoutingModeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | MulticastRoutingModeEnum |
|---|---|
| Content |
|
| Documentation | The MulticastRoutingMode element is an enumeration of the supported modes for multicast routing. |
| Super-types: | xsd:string < NetworkTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | NetworkTypeEnum |
|---|---|
| Content |
|
| Documentation | The mdl:NetworkType element describes the type of the containing Network element. The mdl:NetworkType element is an enumeration that can be set to one of the following values: "RangeNetwork", "TmNS", "TestArticleNetwork", "VehicleNetwork", "GroundOperationsNetwork", "GroundNetwork", "RangeOperationsNetwork", "MissionControlRoomNetwork", "RadioAccessNetwork", "AntennaSiteNetwork", or "GenericNetwork" |
| Super-types: | xsd:token < NonZeroLengthType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | NonZeroLengthType |
|---|---|
| Content |
|
| Documentation | The NonZeroLengthType defined a string which cannot be left empty for purposes such as RoleIDs. |
| Super-types: | xsd:double < Percentage (by restriction) |
|---|---|
| Sub-types: | None |
| Name | Percentage |
|---|---|
| Content |
|
| Documentation | The Percentage element is a simple type, double-precision floating point percent value that must be greater than zero. |
| Super-types: | xsd:string < PhoneNumber (by restriction) |
|---|---|
| Sub-types: | None |
| Name | PhoneNumber |
|---|---|
| Content |
|
| Documentation | The mdl:PhoneNumber data type contains at least 3 numbers but no more than 10. |
| Super-types: | xsd:string < PolarityType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | PolarityType |
|---|---|
| Content |
|
| Super-types: | xsd:string < PortDirectionEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | PortDirectionEnum |
|---|---|
| Content |
|
| Documentation | The PortDirection element indicates the directionality of the flow of content through the interface described by a Port element. The PortDirection element is an enumeration that can be set to one of the following values: Input, Output, Bidirectional, Unspecified |
| Super-types: | xsd:string < PortTypeEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | PortTypeEnum |
|---|---|
| Content |
|
| Documentation | The PortTypeEnum element describes the type of the Port. For these port types the device only needs to know their type. Configuration details are documented elsewhere in the schema. For example, bus speed is in the DataStream description. |
| Super-types: | xsd:string < ProperNameEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | ProperNameEnum |
|---|---|
| Content |
|
| Documentation | The ProperNameEnum is an extensible enumeration of the supported "proper names" of element. A proper name is a means of identifying that the element represents a well-defined field from a standardized data stream, or a standardized data stream itself. If the element does not represent a proper name, the value shall be set to None. |
| Super-types: | xsd:string < RANModulationTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | RANModulationTypeEnum |
|---|---|
| Content |
|
| Documentation | The RANModulationTypeEnum element is an enumeration that lists the available modulation type for a RAN. |
| Super-types: | xsd:string < ScriptingLanguageEnum (by restriction) |
|---|---|
| Sub-types: |
|
| Name | ScriptingLanguageEnum |
|---|---|
| Content |
|
| Documentation | The ScriptingLanguageEnum element describes the language and version of the scripting language used. If the scripting language used is not a member of the list, the "Extension" value of this enumeration shall be chosen. |
| Super-types: | xsd:string < ShiftTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ShiftTypeEnum |
|---|---|
| Content |
|
| Documentation | The ShiftType element describes what type of bitwise shift to perform and the direction in which to shift the input data bits. The supported shift types are "Arithmetic", "Logical", and "Circular", and bits can be shifted either "left" or "right". The ShiftType element is an enumeration that can be set to one of the following values: "ArithmeticLeft", "ArithmeticRight", "LogicalLeft", "LogicalRight", "CircularLeft", "CircularRight" |
| Super-types: | xsd:string < SixBitBinary (by restriction) |
|---|---|
| Sub-types: | None |
| Name | SixBitBinary |
|---|---|
| Content |
|
| Documentation | The mdl:SixBitBinary data type is an xsd:string with a prefix "0b"followed by six characters of binary digits ('0' and '1'). An example value of the mdl:SixBitBinary data type would be "0b011011", which is a 6-bit binary representation of the decimal number 27. |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | SixtyFourBit |
|---|---|
| Content |
|
| Documentation | The mdl:SixtyFourBit data type is an xsd:union of the mdl:SixtyFourBitBinary and mdl:SixtyFourBitHex data types. |
| Super-types: | xsd:string < SixtyFourBitBinary (by restriction) |
|---|---|
| Sub-types: | None |
| Name | SixtyFourBitBinary |
|---|---|
| Content |
|
| Documentation | The mdl:SixtyFourBitBinary data type is an xsd:string with a prefix "0b"followed by 64 characters of binary digits ('0' and '1'). An example value of the mdl:SixtyFourBitBinary data type would be "0b0000000000000000000000000000000000000000000000000000000000000001", which is a 64-bit binary representation of the decimal number 1. |
| Super-types: | xsd:string < SixtyFourBitHex (by restriction) |
|---|---|
| Sub-types: | None |
| Name | SixtyFourBitHex |
|---|---|
| Content |
|
| Documentation | The mdl:SixtyFourBitHex data type is an xsd:string with a prefix "0x"followed by 16 characters of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f'). An example value of the mdl:SixtyFourBitHex data type would be "0x000A0C1DF00932E2" or "0x000a0c1df00932e2" which is a 64-bit hexadecimal representation of the decimal number 2,828,072,487,826,146. |
| Super-types: | xsd:string < SNMPVersionEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | SNMPVersionEnum |
|---|---|
| Content |
|
| Documentation | The SNMPVersionEnum element, of type xsd:string, describes the version of the SNMP protocol. |
| Super-types: | xsd:string < SSTModulationEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | SSTModulationEnum |
|---|---|
| Content |
|
| Documentation | The SSTModulationEnum element indicates the modulation employed by the SST transmitter or receiver. |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TableInputType |
|---|---|
| Content |
|
| Super-types: | xsd:string < ThermocoupleEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ThermocoupleEnum |
|---|---|
| Content |
|
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ThirtyTwoBit |
|---|---|
| Content |
|
| Documentation | The mdl:ThirtyTwoBit data type is an xsd:union of the mdl:ThirtyTwoBitBinary and mdl:ThirtyTwoBitHex data types. |
| Super-types: | xsd:string < ThirtyTwoBitBinary (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ThirtyTwoBitBinary |
|---|---|
| Content |
|
| Documentation | The mdl:ThirtyTwoBitBinary data type is an xsd:string with a prefix "0b"followed by 32 characters of binary digits ('0' and '1'). An example value of the mdl:ThirtyTwoBitBinary data type would be "0b00000000000000000000000000000010", which is a 32-bit binary representation of the decimal number 2. |
| Super-types: | xsd:string < ThirtyTwoBitHex (by restriction) |
|---|---|
| Sub-types: | None |
| Name | ThirtyTwoBitHex |
|---|---|
| Content |
|
| Documentation | The mdl:ThirtyTwoBitHex data type is an xsd:string with a prefix "0x"followed by eight characters of hexadecimal digits ('0'-'9' and 'A'-'F' or 'a'-'f'). An example value of the mdl:ThirtyTwoBitHex data type would be "0x00A9803C" or "0x00a9803c" which is a 32-bit hexadecimal representation of the decimal number 11,108,412. |
| Super-types: | xsd:string < TimeOrderEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TimeOrderEnum |
|---|---|
| Content |
|
| Documentation |
The TimeOrderEnum element describes the temporal ordering of
instances of digital data (e.g., measurement data) within a field
(defined by a DataStructureFieldRef element or a
DataStructureFieldSetRef element).
The TimeOrderEnum element is an enumeration that can be set to one of the following values: "IncreasingTemporal", "DecreasingTemporal", "Simultaneous", or "Unspecified" The value of "IncreasingTemporal" means that subsequent instances of data (e.g., measurement data) occur later in time. Conversely, "DecreasingTemporal" means that subsequent instances of data (e.g., measurement data) occur earlier in time. |
| Super-types: | xsd:string < TimescaleEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TimescaleEnum |
|---|---|
| Content |
|
| Documentation | The TimescaleEnum element describes the timescale of the timestamp defined by the TimestampDefinition element. The timescale describes the division of time into measurable units and the historical reference or epoch that specifies the starting point (i.e., time "0") from which time progresses. |
| Super-types: | xsd:string < TimeSourceTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TimeSourceTypeEnum |
|---|---|
| Content |
|
| Documentation | The TimeSourceTypeEnum is an enumerated list of valid settings for the time source for a TmNSMasterClock. |
| Super-types: | xsd:string < TimestampFormatEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TimestampFormatEnum |
|---|---|
| Content |
|
| Documentation | The TimestampFormatEnum is an enumerated list of valid values that form a subset of the allowable values of the TimestampFormatEnum. Valid values are "UTC" interpreted as Coordinated Universal Time (UTC) or Greenwich Mean Time, "IEEE 1588-2002", and "IEEE 1588-2008". |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | TimestampFormatType |
|---|---|
| Content |
|
| Documentation | The TimestampFormatEnum element describes the format of the timestamps defined by the TimestampDefinition element. The described timestamp format indicates how to interpret the ordering and scale factor of the values within a generated timestamp. For example, the selected format can indicate which values correspond to days, hours, minutes, or seconds. The TimestampFormatEnum element is an xsd:union consisting of a restricted set of xsd:string values and an enumerated set of values. |
| Super-types: | xsd:string < TimestampTypeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TimestampTypeEnum |
|---|---|
| Content |
|
| Documentation | The TimestampTypeEnum is an enumerated list of valid values for a TimestampType. A timestamp can be either an absolute timestamp or an offset time from the Message/Package time from the standard message/package headers. |
| Super-types: | xsd:string < TrackingModeEnum (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TrackingModeEnum |
|---|---|
| Content |
|
| Documentation |
The TrackingMode element indicates the operating mode of the
ACU tracking system. The individual settings are described below:
Standby: servo rate at zero, brakes applied, no power to servo amps. Manual: servo rate at zero, brakes released, power applied to servo amps. Search: Single-axis movements (Sector) or Dual-axis (Raster) based on Center position angle, range of travel, step angle, and rate. Output voltage and polarity is based on direction and range in degrees between the actual position of the pedestal and the commanded angle. As the error decreases, so does the rate voltage. Slave (Point): output voltage and polarity is based on direction and range in degrees between the actual position of the pedestal and the commanded angle. As the error decreases, so does the rate voltage. Autotrack-Auto Acquire: Stays in the previous mode the antenna control unit (ACU) was in prior to selection of Autotrack and waits until the pre-set automatic gain control (AGC) threshold is exceeded, then enters into Autotrack as long as the AGC levels are above threshold. Utilizes the Amplitude Modulator (AM) and Scan References to demodulate into Servo Rate Error. Autotrack-Forced: Enters into Autotrack regardless of AGC levels and threshold. |
| Super-types: | xsd:string < TrafficFilterProtocolEnumType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | TrafficFilterProtocolEnumType |
|---|---|
| Content |
|
| Documentation | The TrafficFilterProtocolEnumType element indicates the protocol that applies to the filter (or condition). |
| Super-types: | xsd:unsignedInt < uInt5 (by restriction) |
|---|---|
| Sub-types: | None |
| Name | uInt5 |
|---|---|
| Content |
|
| Documentation | The mdl:uInt5 data type is a 5-bit unsigned integer. Valid values are the non-negative integers in the inclusive range from 0 to 31. |
| Super-types: | xsd:unsignedByte < UnsignedInt4 (by restriction) |
|---|---|
| Sub-types: | None |
| Name | UnsignedInt4 |
|---|---|
| Content |
|
| Documentation | The mdl:UnsignedInt4 data type is a 4-bit unsigned integer. Valid values are the non-negative integers in the inclusive range from 0 to 15. |
| Super-types: | xsd:string < UpdateFrequencyType (by restriction) |
|---|---|
| Sub-types: | None |
| Name | UpdateFrequencyType |
|---|---|
| Content |
|
| Documentation | The UpdateFrequencyType is used to define when a Function should update its result. IfAny means the result shall be updated when any input to the function receives a new value. IfAll means the result shall only be updated when all the input measurements have received new values since the previous result was calculated. Triggered means the result shall be updated when any input measurement defined as a trigger is updated. |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | ValueType |
|---|---|
| Content |
|