'keep': pass the inputs to the output on the specified flow point outside of a splice event if present. 'drop' do not pass any present (EISS and ETV-DATA) inputs to the output on the specified flow point outside of a splice event 'splice-keep': pass the inputs to the output during splice event if present 'splice-drop': do not pass any present (EISS and ETV-DATA) during a splice-event 'splice-exclusive': keep ETV-DATA and EISS from the highest priority flow point if present; if not, pass the ETV-DATA and EISS PIDs from next priority flow point if present 'persistent': at all times (non-splice and during a splice event), pass the EISS and ETV-DATA, if present, from the input to the output (note EISS is merged, but priority needs to be applied to select the ETV-DATA on the output) 'create': if not present, create ghost PIDs on the output 'private:' provides support for local/private extension. NOTES: - 'Present' implies that the pidType exists and has not been removed by any AppList filtering. - A splice event is typically initiated at the out point based on an SCTE 35 cue message received. A splice event ends when the last SCTE 30 splice complete is sent for the flow point and pass through of the primary input resumes (SCTE 30 "return to primary channel"). - Rules are only applied to pidTypes of EISS and ETV-DATA. - Splice-time rules (splice-drop and splice-keep) are only to be set on flow points that receive SCTE 35 cue messages. - More than one rule can be defined on a flow point. - If more than one flow point has a rule that results in EISS passed to the output, the EISS packets are merged into a single EISS stream. - If more than one flow point has a rule that results in ETV-DATA passed to the output, the ETV-DATA flow point with the highest priority will be passed. - A rule can be defined within one flow point for another flow point using the nameofFlowPoint attribute. - If conflicting rules are defined, the rule with the highest priority (lowest number) will take precedence. The IP destination address of the UDP IP flow of the transport stream. The UDP destination port of the UDP IP flow of the transport stream. The source IP address for a Source Specific Multicast (SSM) address. The destination multicast IP address. The UDP destination port of the multicast stream. Local IP interface; must be a configured ip-interface name. IP address for the unicast or multicast connection. For multicast connections, enter the multicast IP address. This object identifies a video output stream. In the context of MUX 3.0, it is not used for configuration, only for identification to be used as a Flow Point. Application filters and Source Management Rules can then be applied to the specified VideoOutputTs Flow Point. Use of fields for matching 1. the following are valid matching patterns for an application. Any of the values can be included but all entries in the list up to that entry are required if the value is included. If organization is not included, then no values are valid, and all applications will match the filter A filter with no attributes specfied should be created with a lower priority and can be used as a default if no other filters apply at that Flow Point. Application 1. SCTE 130 - Used in combination with an action on a SCTE 130-3 Placement element. Placement@action = "update" typeOfEntry is ignored Placement@action = "appFilter" - establish an application filter - could be a whitelist or blacklist typeOfEntry = "blacklist" - if a given app matches an entry in the app list, it is blocked; otherwise, it is allowed. typeOfEntry = "whitelist" - if a given app matches an entry in the app list, it is allowed; otherwise, it is blocked. 2. CCAP - Used wthin a FlowConfigurationType structure to statically configure a flow within a device ConfigurationItem@type = "update" typeOfEntry is ignored @filePath - URL to the CoDF file to apply Configuration@action = "appFilter" - establish an application filter - could be a whitelist or blacklist typeOfEntry = "blacklist" - if a given app matches an entry in the app list, it is blocked; otherwise, it is allowed. typeOfEntry = "whitelist" - if a given app matches an entry in the app list, it is allowed; otherwise, it is blocked. filePath is ignored Once an entry evalutes to TRUE, it will be processed and no additional entries will be evaluated. That is: - for a "whitelist" entry, if the entry matches, the application (signaling and data) will be passed out of the Flow Point - for a "blacklist" entry, if the entry matches, the application (signaling and data) will be dropped - for an "update"entry, if the entry matches, the update will be applied and the application passed out of the Flow Point (NOTE: "update" is an implicit "whitelist" entry) tracking uniquely identifies this entry It is a GUID that can be passed in SCTE 130 PSNs or in reporting entries. If more than one app list entry exist in the app list entries table and/or multiple app list entry tables are active at the same time, the priority specifies the order entries are processed. The default value is priority 1. The lower the value the higher the proirity. If multiple entries accross all entries in a single table or accross multiple tables have the same priority the order of interpretation is not deterministic. Required to setup a white or black list. typeOfEntry can be whitelist, blacklist or private:*. typeOfEntry does not apply if the action is "udpate" Specifies a 32-bit organization ID for matching. If this attribute is not specified, all other application identifier attributes are to be ignored. If this attribute is not specified, all applications will match this filter. For example, if the typOfEntry is specified as "blacklist", and no other application identifiers are specified, all applications will match this filter and be dropped. To set up a Flow Point that drops all applications by default, and only passes specified applications, create a whitelist for those specified applications, and a blacklist for all other applications with a lower priorityOfEntry. Specifies a 16-bit application ID for matching. Specifies an integer (0-255) application major version for matching. Specifies an integer (0-255) application minor version for matching. Specifies an application instance identifier for matching. Specifies the application priority (0-255) for matching. Used in combination with the other application specific attributes. 8-bit integer which specifies a test flag field for matching. The usage of this field is entirely defined by the MSO. ETV application descriptor private data field for matching. HEX string value. ConfigurationType is used to set global settings for a MUX (ex. in CCAP this may appear as an extentension under the ccap/management element) Optional list of callouts (see SCTE 130-3 for valid message values) when ADS registration messages are not used. System level default for ADSCallout in the absence of an ADSRegistration call from a Decision System. Set to TRUE if all flow points should do a callout. Set to FALSE if all flow should not do a callout. ADSCallOut can be overriden at a given flow point. If not specified at a configured Callout at the system level, this attribute MUST default to “false ” If Filtering is supported, the FilterConfiguration element MUST be supplied. FilterConfiguration defines default filtering behavior for all or specific flows within a MUX. Default filter type (MUST be provided) · whitelist – if an application matches a blacklist filter it will be dropped, otherwise it will be allowed (pass all signals and data) · blacklist - if an application matches a whitelist filter it will be passed, otherwise it will be rejected (drop all signaling and data) - private:. Default filter type on all video-input-ts Flow Points) Default filter type on all program-session Flow Points. Default filter type on all video-output-ts Flow Points This is an optional value that may be used as a control value when integrating different systems. (e.g.. A MUX may use this value as a way to "sign" export files. On import the MUX vendor may validate the signature against the last export sent.) FlowConfigurationType for use in static configuration of a flow point within a configuration. (ex. CCAP OSSI schema video element) IPDRConfig - used to override the global setting from ConfigurationType ConfigurationItem - one or more entries to define an application filter, an udpate or a private definition on the flow. Override global adsCallOutState setting. If set to TRUE, an ADS Callout should be done. ConfigurationItemType for use within FlowConfigurationType Type of configuration entry - appFilter, update, or private URI path to the CoDF file Choose a specific program number within a flow The container for configuring global IPDR sessions and collectors. ExporterConfig allows an IPDR Exporter to be turned on and off. Configures whether or not the IPDR Exporter is enabled. This configuration object is used to configure individual streaming sessions associated with service definitions. The ID for this instance. The interval in seconds at which IPDR 'keepalives' are sent from the MUX 3.0 IPDR exporter to the collector. The interval in seconds in which the MUX 3.0 IPDR exporter waits for an acknowledgment. The maximum number of unacknowledged records that can be sent by the MUX 3.0 IPDR exporter before receiving an acknowledgement. Where streaming is of the type timeInterval, this object configures the interval in seconds at which IPDR information is extracted from the MUX 3.0 management objects and transmitted to the collector. Where streaming is of the type timeEvent, this object identifies the interval at which the MUX 3.0 IPDR exporter will close the IPDR session to allow IPDR session processing to occur. Records created by Service Definitions supporting timeEvent are sent when the event is generated. The type of IPDR streaming used for the session. The value of other(1) is used when a vendor-extension has been implemented for this attribute. This object controls whether the IPDR Session is enabled or disabled. This object configures the service type definition for this IPDR session. This is a string that should specify the URI of the service definition schema. A reference to a collector id. This configuration object allows the operator to configure an IPDR collector. This key configures a unique identifier for this collector. The IP address of collector from which the MUX 3.0 will accept a connect. The collector establishes a connection to the MUX 3.0. Optional name for the IPDR collector. The port used by the collector to communicate with the MUX 3.0. This object configures the priority of this IPDR collector. The priority is used to elect the primary and active collector. The collector with the highest priority (lowest number) is elected. IPDR Reporting Control - set to TRUE to enable reporting, set to FALSE to disable reporting. This type may contain elements or attributes from any namespace and is provided for future extensibility. Revision number for this entry. Start at 1 and increment each time there is an update. Time/Date stamp for the revision. Use to control reporting on a global and flow point basis. Specify the default state of reporting. TRUE means report; FALSE means don't report. When used globally, this value will apply (becomes the default for all local ReportingAttributeGroup usage) but can be overridden on a case by case basis. The global state is FALSE by default. If FALSE, any other reporting control in this attribute group shall be ignored; otherwise, each additonal reporting control shall be applied. Specify the default state of reporting for the PMT. TRUE means report; FALSE means don't report. When used globally, this value can be overriden on a an individual flow point. FALSE by default. Specify the default state of reporting for the ETV_EISS. TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point. FALSE by default. Specify the default state of reporting for the ETV_DII. TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point.. FALSE by default. Specify the default state of reporting for the ETV_DDB. TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point.. FALSE by default. Specify the default state of reporting for the SDT. TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point. FALSE by default. Specify the default state of reporting for SCTE 35 sections. TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point. FALSE by default. Specify the default state of reporting for bandwidth.TRUE means report; FALSE means don't report. When used globally, this value can be overridden on an individual flow point. FALSE by default. The sampling interval (in seconds) for bandwidth collection. If not specified, the default is 5 (seconds) The number of sample intervals for which the MaxBandwidth and AvgBandwidth are calculated. If not specified, the default is 6 (sample intervals) The type of the configuration entry. appFilter if its a whitelist/blacklist, update, or private. The representation of a GUID, generally the id of an element. For use in uniquely identifying application instances and events. This format supports a Version 1 (MAC-based) UUID as defined in [RFC 4122] and encoded as a Base64URL string as defined in [RFC 4648]. The 16-byte binary UUID will encode to a 22-byte string by using a modified Base64 for URL variant, where no padding '=' will be used, and the '+' and '/' characters of standard Base64 are respectively replaced by '-' and '_'. AppList entry type - whitelist or blacklist Contains one or more AppListItem entries Optional nameOfFlowPoint to apply the rule to. If omitted, the rule applies to the flow point where this entry is placed. Optional elementary stream type. If omitted, the rule applies to all eiss and etvbif PIDs in the specifed flow point. If the flow point has multiple programs all PIDs of this type will be processed unless otherwise constrained to a specific program number. Optional 13-bit packet ID (PID). If omitted, the rule applies to all PIDs in the specifed flow point. Optional program number within the designed stream to apply the rule to. If omitted, the rule applies to all programs in the specifed flow point. This also applies to alll PIDs within the program unless constrained otherwise. Tracking uniquely identifies this entry. It is a GUID that can be passed in SCTE 130 PSNs or in reporting entries. (IPDR: string) The priority value defined to allow differentiation among the various stream flows based on the relative importance of the individual streams. The lower the value defined the higher the priority.