EN 62379-5-1:2014

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Gemeinsame Steuerschnittstelle für netzwerkbetriebene digitale Audio- und Videogeräte - Teil 5-1: Übertragung über Netzwerke - Allgemeines (IEC 62379-5-1:2014)VCommon control interface for networked digital audio and video products - Part 5-1: Transmission over networks - General (IEC 62379-5-1:2014)35.200Vmesniška in povezovalna opremaInterface and interconnection equipment33.160.01Avdio, video in avdiovizualni sistemi na splošnoAudio, video and audiovisual systems in generalICS:Ta slovenski standard je istoveten z:EN 62379-5-1:2014SIST EN 62379-5-1:2014en,fr,de01-december-2014SIST EN 62379-5-1:2014SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 62379-5-1
October 2014 ICS 35.100; 33.160
English Version
Common control interface for networked digital audio and video products - Part 5-1: Transmission over networks - General (IEC 62379-5-1:2014)
Interface de commande commune pour produits audio et vidéo numériques connectés en réseau - Partie 5-1: Transmission sur des réseaux - Généralités (CEI 62379-5-1:2014)
Gemeinsame Steuerschnittstelle für netzwerkbetriebene digitale Audio- und Videogeräte - Teil 5-1: Übertragung über Netzwerke - Allgemeines (IEC 62379-5-1:2014) This European Standard was approved by CENELEC on 2014-08-13. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung CEN-CENELEC Management Centre: Avenue Marnix 17,
B-1000 Brussels © 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62379-5-1:2014 E SIST EN 62379-5-1:2014

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent rights. Endorsement notice The text of the International Standard IEC 62379-5-1:2014 was approved by CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following note has to be added for the standard indicated : IEC 62379
NOTE Harmonized in EN 62379
series.
- 3 - EN 62379-5-1:2014 Annex ZA (normative)
Normative references to international publications with their corresponding European publications The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here: www.cenelec.eu.
Publication Year Title EN/HD Year IEC 62379-1 2007
Common control interface for networked digital audio and video products - Part 1: General EN 62379-1 2007
IEC 62379-5-2 2014
Common control interface for networked digital audio and video products - Part 5-2: Transmission over networks - Signalling EN 62379-5-2 2014
IEC 62379-5-1 Edition 1.0 2014-07 INTERNATIONAL STANDARD NORME INTERNATIONALE Common control interface for networked digital audio and video products –
Part 5-1: Transmission over networks – General
Interface de commande commune pour produits audio et vidéo numériques connectés en réseau –
Partie 5-1: Transmission sur des réseaux – Généralités
INTERNATIONAL ELECTROTECHNICAL COMMISSION COMMISSION ELECTROTECHNIQUE INTERNATIONALE X ICS 33.160; 35.100 PRICE CODE CODE PRIX ISBN 978-2-8322-1693-4
– 2 – IEC 62379-5-1:2014  IEC 2014 CONTENTS FOREWORD . 4 INTRODUCTION . 6 1 Scope . 7 2 Normative references . 7 3 Terms, definitions and abbreviations . 7 3.1 Terms and definitions. 7 3.2 Abbreviations . 7 4 Network service specifications . 8 4.1 Service for live media . 8 4.2 Service for management messages . 8 5 MIB definitions applicable to all networks . 8 5.1 General . 8 5.2 Type definitions . 8 5.3 Conceptual row type definitions . 9 5.4 MIB object definitions . 10 5.4.1 Network ports . 10 5.4.2 List of media sources . 12 5.4.3 List of live media destinations . 14 6 Calls . 19 6.1 List of destinations in end equipment . 19 6.2 Connecting a flow . 20 6.3 Terminating a flow . 20 6.4 Maintaining calls . 21 7 Status broadcasts . 21 7.1 General . 21 7.2 Coding and encapsulation of reports . 22 7.3 Standard report groups . 23 7.3.1 General . 23 7.3.2 List of sources . 23 7.3.3 List of destinations . 23 Annex A (informative)
Machine-readable block definitions. 24 Annex B (informative)
Machine-readable data formats . 36 Annex C (informative)
Support for future networks . 39 C.1 General . 39 C.2 Services provided by the network . 39 C.3 Network ports, flows, and media streams . 40 C.3.1 Calls and flows . 40 C.3.2 Connectivity model . 40 C.3.3 Privilege . 40 C.3.4 Call identity . 40 C.4 Control of routing . 41 C.5 Scheduled calls . 41 Bibliography . 42
Table 1 – Managed objects for network ports . 10 SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 3 – Table 2 – Managed objects conveying the list of sources . 12 Table 3 – Managed objects conveying the list of destinations . 15
– 4 – IEC 62379-5-1:2014  IEC 2014 INTERNATIONAL ELECTROTECHNICAL COMMISSION ____________
COMMON CONTROL INTERFACE FOR NETWORKED
DIGITAL AUDIO AND VIDEO PRODUCTS –
Part 5-1: Transmission over networks –
General
FOREWORD 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out by independent certification bodies. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights. International Standard IEC 62379-5-1 has been prepared by technical area 4: Digital system interfaces and protocol of IEC technical committee 100: Audio, video and muiltimedia systems and equipment. The text of this standard is based on the following documents: CDV Report on voting 100/2107/CDV 100/2304/RVC
Full information on the voting for the approval of this standard can be found in the report on voting indicated in the above table. SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 5 – A list of all parts in the IEC 62379 series, published under the general title Common control interface for networked digital audio and video products, can be found on the IEC website. This publication has been drafted in accordance with the ISO/IEC Directives, Part 2. The committee has decided that the contents of this publication will remain unchanged until the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data related to the specific publication. At this date, the publication will be
• reconfirmed, • withdrawn, • replaced by a revised edition, or • amended.
– 6 – IEC 62379-5-1:2014  IEC 2014 INTRODUCTION Structure of the family of standards IEC 62379 specifies the common control Interface, a protocol for managing networked audiovisual equipment. The following parts exist or are planned: 1
General 2
Audio 3
Video 4
Data 5
Transmission over networks 6
Packet transfer service 7
Measurement IEC 62379-1:2007, specifies aspects which are common to all equipment, and it includes an introduction to the common control interface. IEC 62379-2:2008, IEC 62379-3 (under consideration) and IEC 62379-4 (under consideration) specify control of internal functions specific to equipment carrying particular types of live media. IEC 62379-4 refers to time-critical data such as commands to automation equipment, but not to packet data such as the control messages themselves. IEC 62379-5 specifies control of transmission of these media over each individual network technology. It includes network specific management interfaces along with network specific control elements that integrate into the control framework. IEC 62379-5-1, (this standard) specifies management of aspects which are common to all network technologies. IEC 62379-5-2 specifies protocols which can be used between networking equipment to enable the setting up of calls which are routed across different networking technologies. IEC 62379-5-3, onwards, specify management of aspects which are particular to individual networking technologies. IEC 62379-6, specifies carriage of control and status messages and non-audiovisual data over transports that do not support audio and video, such as RS232 serial links, with (as for IEC 62379-5) a separate subpart for each technology. IEC 62379-7 specifies aspects that are specific to the measurement of the service experienced by audio and video streams and in particular to the requirements of EBU ECN-IPM Measurements Group.
IEC 62379-5-1:2014  IEC 2014 – 7 – COMMON CONTROL INTERFACE FOR NETWORKED
DIGITAL AUDIO AND VIDEO PRODUCTS –
Part 5-1: Transmission over networks –
General
1 Scope This part of IEC 62379 specifies aspects of the common control interface that are common to all network technologies, including setting up and tearing down of sessions and the service provided by the network. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 62379-1:2007, Common control interface for networked digital audio and video products – Part 1: General IEC 62379-5-2:2014, Common control interface for networked digital audio and video products – Part 5-2: Transmission over networks – Signalling 3 Terms, definitions and abbreviations 3.1 Terms and definitions For the purposes of this document, the terms and definitions given in IEC 62379-1 and IEC 62379-5-2, as well as the following apply. 3.1.1
media port source or destination of media data in an interface unit Note 1 to entry: A media port is either a physical port (e.g. an external audio or video connector on the unit) or a logical port (e.g. an internal connection to another part of the unit). 3.1.2
switch network element which routes media data and other messages between links 3.2 Abbreviations
TCP Transmission Control Protocol a UDP User Datagram Protocol b MIB Management Information Base a See RFC 793. b See RFC 768.
– 8 – IEC 62379-5-1:2014  IEC 2014 4 Network service specifications 4.1 Service for live media Live media (including status broadcasts) shall be transmitted using a service for which, if the network supports it, guaranteed levels of throughput, delay, and data loss shall be requested. 4.2 Service for management messages Management messages should be transmitted in data units on an asynchronous flow as specified in IEC 62379-5-2. If no such service is available, a connectionless datagram service such as UDP may be used. Where a connection-oriented service is used, at least one call at each privilege level shall be accepted by a destination unit at any given time. If more calls at one privilege level are accepted, this shall not prevent the acceptance of at least one call at each other privilege level. 5 MIB definitions applicable to all networks 5.1 General The structure of the MIB shall be as specified in IEC 62379-1. 5.2 Type definitions The following application-wide types shall be used:
NetPortState::= INTEGER {
disabled
(1),
closing
(2),
linkDown
(3),
linkUp
(4),
-- does not know to what linked
pointToPoint
(5),
-- link is point-to-point
peerGroup
(6),
-- e.g. Ethernet hub
sharedMedia
(7)
-- with master, e.g. 802.11
}
(disabled.sharedMedia)
PortIdentifier::= OCTET STRING (SIZE(3))
' octet 1 = port type
' octets 2 and 3 = port number (high byte in octet 2)
ConnectionEnd::= INTEGER {
source
(1),
destination (2)
} (source.destination)
CauseCode::= OBJECT IDENTIFIER NOTE Cause codes may be defined in other parts of the IEC 62379-5 series or elsewhere.
ConnectionState::= INTEGER {
readyToConnect
(1),
connectionRequested
(2),
terminating
(3),
active
(4),
failed
(5),
disconnected
(6),
pending
(7),
inactive
(8),
finished
(9), SIST EN 62379-5-1:2014
IEC 62379-5-1:2014  IEC 2014 – 9 –
callProceeding
(10),
receivedOffer
(11),
acceptedOffer
(12),
reservationRequested (13),
clearing
(14)
} (readyToConnect.clearing )
Importance::= INTEGER (1.255)
Priority::= INTEGER (1.255)
5.3 Conceptual row type definitions The following types are used to specify the syntax of managed objects in this standard that represent conceptual table rows. NetPortEntry::= SEQUENCE {
nPortBlockId
BlockId,
nPortName
Utf8String,
nPortState
NetPortState,
nPortAddressType TDomain,
nPortAddress
TAddress,
nPortPAddrType
TDomain,
nPortPartnerAddr TAddress,
nPortBarred
TruthValue }
UnitSourceEntry::= SEQUENCE {
usFlowIdentifier OCTET STRING,
usBlockId
SourceBlockId,
usBlockInput
IndexNumber,
usPackageSize
CardianlNumber,
usPrivilege
PrivilegeLevel,
usState
ConnectionState,
usCause
CauseCode,
usSource
Utf8String,
usDestination
Utf8String,
usService
Utf8String,
usImportance
Importance,
usPriority
Priority,
uStartTime
DateTime,
usEndTime
DateTime,
usConnectTime
CardinalNumber,
usFlowIdStandard TruthValue }
UnitDestEntry::= SEQUENCE {
udFlowIdentifier OCTET STRING,
udNetBlockId
SourceBlockId,
udNetBlockOutput IndexNumber,
udSourceAddrType TDomain,
udSourceAddress
TAddress,
udPackageSize
CardianlNumber,
udPrivilege
PrivilegeLevel,
udState
ConnectionState,
udCause
CauseCode,
udSource
Utf8String,
udDestination
Utf8String,
udService
Utf8String,
udImportance
Importance,
udPriority
Priority, SIST EN 62379-5-1:2014

– 10 – IEC 62379-5-1:2014  IEC 2014
udStartTime
DateTime,
udEndTime
DateTime,
udConnectTime
CardinalNumber,
udConnectCount
CardinalNumber,
udRemembered
TruthValue,
udDestBlockId
DestBlockId,
udDestBlockInput IndexNumber,
usFlowIdStandard TruthValue }
5.4 MIB object definitions 5.4.1 Network ports 5.4.1.1 General Each physical connection to a network, in a switch or end equipment, shall be represented using a network port block. A network port block shall have one input for each outgoing media flow and one output for each incoming media flow. The group of objects in Table 1 shall be implemented by all switches. The root node for these objects shall be { iso(1) standard(0) iec62379(62379) network(5) general (1) networkMIB(1) networkPorts(1) } This node shall be used as the block type identifier for network port blocks. Table 1 – Managed objects for network ports Identifier Syntax Index Readable Writable Volatile Syntax netPortTable(1) SEQUENCE OF NetPortEntry
none none yes mandatory gnetmortbntrybkc NetPortEntry
none none yes mandatory
inmortBlockfdbkc BlockId yes none none no mandatory
inmortkameblc Utf8String
listener supervisor no mandatory
inmortptatebmc NetPortState
listener supervisor yes mandatory
inmortAddressType(4) TDomain
listener none no mandatory
inmortAddressboc TAddress
listener none no mandatory
inmortmAddrTypebpc TDomain
listener none yes mandatory
inmortmartnerAddrbTc TAddress
listener none yes mandatory
gnmortBarredb8c TruthValue
listener supervisor no mandatory
5.4.1.2 netPortTable A table of network port descriptors for this unit. Each physical network port on the unit shall have a corresponding entry in this table. There may also be entries for "virtual" network ports. 5.4.1.3 netPortEntry An entry in the network port table. 5.4.1.4 nPortBlockId The block identifier for this port. Used as an index when accessing the network port table. SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 11 – 5.4.1.5 nPortName The name assigned to this port. This is an arbitrary text string assigned by the system manager. Such assignment should persist across resets of the unit. Until a name has been assigned, this object shall have a value that relates to a visible marking associated with the port's physical connector. Note that the name of a port on a network switch whose connector is labelled "2" on the unit's enclosure should default to a value such as "Port 2" or "Ethernet port 2" or "Front panel port 2". If it is connected to a network socket in, say, studio 6, a supervisor may then rename it as "Studio 6". 5.4.1.6 nPortState The current link-layer state of the port's network connection. If a management terminal sets this object to closing or linkDown, the managed unit shall reroute or, if that is not possible, gracefully close down all calls that pass through the port. In the case of closing, the port shall then enter the disabled state. For as long as the port is in linkDown state, the managed unit shall attempt to establish a network connection on the port. 5.4.1.7 nPortAddressType The type of network address used for nPortAddress. 5.4.1.8 nPortAddress An address which identifies the port. NOTE This will normally be the 48-bit MAC address of the interface. An IP address may be used if it is permanently assigned, but not if it is acquired via DHCP. 5.4.1.9 nPortPAddrType The type of network address used for nPortPartnerAddr. 5.4.1.10 nPortPartnerAddr In pointToPoint state, the address of the unit to which the port is connected. In sharedMedia state, the address of the unit which controls the local network to which the port is connected, e.g. wireless base station or clock master. In other states, the nPortPartnerAddr value is not defined by this standard. NOTE 1 This object is intended to allow a management terminal to "crawl" a network to discover its topology and what resources are present. The address allows it to make a management connection to the link partner in the case of a point-to-point link, or, in the case of a shared-media network segment, to a unit which may be able to supply a list of all the units on the segment. In contrast to nPortAddress, the nPortPartnerAddr value should identify the unit rather than its interface, so an EUI-64 is appropriate. NOTE 2 For some kinds of network segment, such as an Ethernet segment using CSMA/CD, there is no straightforward method for enumerating all the units present on the segment. 5.4.1.11 nPortBarred false (the default) if the unit is allowed to connect a route via the port; true if forbidden. SIST EN 62379-5-1:2014

– 12 – IEC 62379-5-1:2014  IEC 2014 5.4.2 List of media sources 5.4.2.1 General The “list of sources” has an entry for each synchronous flow transmitted by the managed unit. The group of objects in Table 2 shall be implemented by all end equipment that can be the source for a synchronous flow, and by all switches. The root node for these objects shall be { iso(1) standard(0) iec62379(62379) network(5) general(1) networkMIB(1) callSources(2) } NOTE 1 Calls are always connected by the destination, so this table is read-only, apart from the ability to clear down a call from the source end. Management calls are not included in this list. NOTE 2 It is assumed that incoming calls specify a source in some way that may be at least partially network-dependent, and whenever a new connection is made an entry appears in this table, disappearing again when the call is released. Table 2 – Managed objects conveying the list of sources Identifier Syntax Index Readable Writable Volatile Syntax unitSourceListTable(1) SEQUENCE OF UnitSourceEntry
none none yes mandatory gunitpourcebntrybkc UnitSourceEntry
none none yes mandatory
iusclowfdentifierbkc OCTET STRING yes none none yes mandatory
iusBlockfdblc SourceBlockId yes listener none yes mandatory
iusBlockfnputbmc IndexNumber
listener none yes mandatory
iusmackageSize(4) CardinalNumber
listener none yes mandatory
iusmackageoateboc CardinalNumber
listener none yes mandatory
iusmrivilegebpc PrivilegeLevel
listener none yes mandatory
iusptatebTc ConnectionState
listener see 6.3 yes mandatory
iusCauseb8c CauseCode
listener see 6.3 yes mandatory
iuspourceb9c Utf8String
listener none yes mandatory
iusaestinationbk0c Utf8String
listener none yes mandatory
iuspervicebkkc Utf8String
listener none yes mandatory
iusfmportancebklc Importance
listener none yes mandatory
iusmrioritybkmc Priority
listener none yes mandatory
iusptartTimebk4c DateandTime
listener none yes mandatory
iusEndTime(15) DateandTime
listener none yes mandatory
iusConnectTime(16) CardinalNumber
listener none yes mandatory
gusclowfdptandardbkTc TruthValue
listener none yes mandatory
5.4.2.2 unitSourceListTable The list of flows for which this unit transmits media data. NOTE In the case of end equipment, the table lists flows for which the unit is the source. In the case of a switch, it lists information relating to onwards transmission towards the destination(s), for all synchronous flows passing through the unit. 5.4.2.3 unitSourceEntry An entry in the list of flows for which this unit transmits media data. SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 13 – 5.4.2.4 usFlowIdentifier An octet string which identifies the flow. The format specified in IEC 62379-5-2 should be used if available; see 5.4.2.20. 5.4.2.5 usBlockId The identifier of the network port block for the unit's network port through which this flow passes. 5.4.2.6 usBlockInput The input number, to the network port identified by usBlockId, through which this flow passes. NOTE The entry associated with this input in connectorTable (see Table 2 of IEC 62379-1:2007) shows the block output which is the source of the media stream. The entry associated with that output in modeTable (see Table 2 of IEC 62379-1:2007) shows the media format being transmitted. 5.4.2.7 usPackageSize The maximum number of payload octets that may be transmitted in a single data unit on the flow. NOTE This is the size negotiated for the flow, which, when multiplied by the usPackageRate value, defines the bandwidth required. It is not the maximum transmission unit size for the links over which the flow will be transmitted. For example: – for an ATM link this would be fixed at the value 48, the number of payload octets in a cell; – for an RTP stream this would be the maximum payload size for the RTP packets. 5.4.2.8 usPackageRate The number of data units per second that may be transmitted on the flow. 5.4.2.9 usPrivilege The privilege level associated with this flow, which is the highest of the privilege levels associated with its destinations if the network provides that information, supervisor otherwise. 5.4.2.10 usState The current state of this flow. The callProceeding state shall indicate that an incoming connection request has been accepted and confirmation from the caller is awaited. 5.4.2.11 usCause This object shall be initialised to a zero-length value, which shall indicate “normal call clearing”, and shall be set by the managed unit when it changes usState to failed or disconnected. See also 6.3. 5.4.2.12 usSource The source name for this flow. NOTE In the case of end equipment, the source name is specified as part of the definition of one of the blocks through which the signal passes on its way to the network port. In the case of a switch, it is inherited from the flow’s udSource object (see 5.4.3.16). SIST EN 62379-5-1:2014

– 14 – IEC 62379-5-1:2014  IEC 2014 5.4.2.13 usDestination The destination name for the most important destination of the flow reached via this network port. 5.4.2.14 usService The service name for the most important destination of the flow reached via this network port. 5.4.2.15 usImportance The importance of the most important destination of the flow reached via this network port. 5.4.2.16 usPriority The priority of the part of the flow connected via this network port. 5.4.2.17 usStartTime The time at which the state is expected to change from pending to reservationRequested or active. 5.4.2.18 usEndTime The time after which the network may release the resources reserved for the flow on this port. 5.4.2.19 usConnectTime The number of seconds for which this flow has been active on this network port or the maximum CardinalNumber value, whichever is the less; zero if the state is not active. 5.4.2.20 usFlowIdStandard true if usFlowIdentifier is in the format specified in IEC 62379-5-2, false otherwise. Note that if the format specified in IEC 62379-5-2 is used, a flow has the same identifier in every piece of equipment through which it passes. Thus, records in which usFlowIdStandard or (in the list of destinations, see 5.4.3.28) udFlowIdStandard is true, even in units managed differently, refer to the same flow if, and only if, they have the same usFlowIdentifier or udFlowIdentifier value. Note that if usFlowIdStandard is false, the management terminal should regard the flow identifier simply as a value chosen by the managed unit which, when combined with usBlockId, forms an index to this table. Thus, the management terminal should not assume any relationship between flows on different ports in unitSourceListTable, or between flows in unitSourceListTable and in unitDestListTable (see 5.4.3), based on a comparison of their identifiers; relationships should be established via connectorTable (see Table 2 of IEC 62379-1:2007). 5.4.3 List of live media destinations 5.4.3.1 General The “list of destinations” has an entry for each synchronous flow received by the managed unit. The group of objects in Table 3 shall be implemented by all end equipment that can be the destination for synchronous flows, and by all switches. The root node for these objects shall be SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 15 – {iso(1) standard(0) iec62379(62379) network(5) general(1) networkMIB(1) callDestinations(3)} Table 3 – Managed objects conveying the list of destinations Identifier Syntax Index Readable Writable Volatile a Syntax unitNextFlowId(1) OCTET STRING
listener none yes see b unitNextCallId(2) OCTET STRING
listener none yes see 5.4.3.3 unitDestListTable(3) d SEQUENCE OF UnitDestEntry
none none yes mandatory gunitaestbntrybkc UnitDestEntry
none none yes mandatory
iudclowfdentifierbkc OCTET STRING yes none none maybe mandatory
iudketBlockfdblc SourceBlockId
listener see 6.1 yes mandatory
iudketBlocklutputbmc IndexNumber
listener none yes mandatory
iudpourceAddrType(4) TDomain
listener see 6.1 maybe mandatory
iudpourceAddressboc TAddress
listener see 6.1 maybe mandatory
iudmackagepizebpc CardinalNumber
listener none maybe mandatory
iudmackageoatebTc CardinalNumber
listener none maybe mandatory
iudmrivilegeb8c PrivilegeLevel
listener see 6.1 maybe mandatory
iudptateb9c ConnectionState
listener see 6.1 yes mandatory
iudCausebk0c CauseCode
listener see 6.1 yes mandatory
iudpourcebkkc Utf8String
listener none maybe mandatory
iudaestinationbklc Utf8String
listener see 6.1 maybe mandatory
iudpervicebkmc Utf8String
listener see 6.1 maybe mandatory
iudfmportancebk4c Importance
listener see 6.1 maybe mandatory
iudmrioritybkoc Priority
listener see 6.1 maybe mandatory
iudptartTimebkpc DateandTime
listener see 6.1 maybe mandatory
iudEndTime(17) DateandTime
listener see 6.1 maybe mandatory
iudConnectTimebk8c CardinalNumber
listener none maybe mandatory
iudConnectCountbk9c CardinalNumber
listener supervisor maybe optional
iudoememberedbl0c TruthValue
listener see 6.1 no see b
iudaestBlockfdblkc DestBlockId
listener see 6.1 maybe see b
iudaestBlockfnputbllc IndexNumber
listener see 6.1 maybe see b
gudclowfdptandardblmc TruthValue
listener none maybe mandatory Management calls are not included in this list. Synchronous flows are always connected by the destination, so in the case of end equipment every entry in this list is a flow which has been initiated by a management terminal through the process detailed in Clause 6. a Where the volatility is shown as "maybe", the object is volatile, if, and only if, udRemembered is false. b Objects shown as “see b” are mandatory for end equipment but should return noSuchName in units that cannot be the destination of a media flow.
5.4.3.2 unitNextFlowId A flow identifier value, not in the form specified in IEC 62379-5-2, for which a new record is created in the table, as described in 6.1. Consecutive Get requests for this object shall return different values. Values should be chosen in a way that maximises the time before re-use of any particular value. A GetNext request for this object shall not create a new record. The value returned (if any) is not defined by this standard. SIST EN 62379-5-1:2014

– 16 – IEC 62379-5-1:2014  IEC 2014 Whereas the port number is an index into the list of sources, the source flow numbers only need to be unique for each port, in the list of destinations the flow number is the only index, and therefore it needs to be unique across all ports of the managed unit. Managed units that support flow identifiers in the format specified in IEC 62379-5-2 should internally allocate a call identifier as if unitNextCallId had been requested. The value returned may be the call identifier, or a flow identifier based on it, or some other value which refers to it. In any case, the record that is created shall have udFlowIdStandard set to false, and the value returned shall be different from any flow identifier in the format specified in IEC 62379-5-2 that could be created using a call identifier returned by reading unitNextCallId. To meet this requirement, it is sufficient for the octet string to be a different length from the format specified in IEC 62379-5-2, or to begin with the internally allocated call identifier. 5.4.3.3 unitNextCallId A new call identifier value in the form specified in IEC 62379-5-2, from which flow identifiers may be derived, as described in 6.1. Consecutive Get requests for this object shall return different values. Values should be chosen in a way that maximises the time before re-use of any particular value. The value (if any) returned for a GetNext request for this object is not defined by this standard. This object is mandatory for end equipment that supports flow identifiers in the format specified in IEC 62379-5-2, but shall return noSuchName in units that do not support that format and in units that return noSuchName for unitNextFlowId. 5.4.3.4 unitDestList The list of synchronous flows which this unit receives. NOTE In the case of end equipment, the table lists flows for which the unit is the destination. In the case of a switch, it lists information relating to reception from the source, for all media flows passing through the unit. 5.4.3.5 unitDestEntry An entry in the list of synchronous flows which this unit receives. 5.4.3.6 udFlowIdentifier An octet string which identifies the flow uniquely within the unit. See also 5.4.3.28. Note that this is the only index field, so it shall be unique within the unit, not merely for each port. 5.4.3.7 udNetBlockId In inactive and readyToConnect states, the identifier of the network port block for the unit's network port through which this flow should be connected, or nullBlock if the network port is to be chosen by the managed unit. The managed unit may ignore this value even if it is not nullBlock. In other states, the identifier of the network port block for the unit's network port through which this flow passes, or zero if the flow is not associated with a specific network port. 5.4.3.8 udNetBlockOutput The output number, of the network port identified by udNetBlockId, through which this flow passes, or zero if udNetBlockId is zero or the output has not yet been chosen. SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 17 – NOTE The entry associated with this output in modeTable (see Table 2 of IEC 62379-1:2007) shows the media format being received, and connectorTable (see Table 2 of IEC 62379-1:2007) shows to which block inputs (if any) the received media stream is being routed internally. In the case of a switch, these blocks will be the network ports on which the flow is being output. 5.4.3.9 udSourceAddrType The type of network address used for ucSourceAddress. 5.4.3.10 udSourceAddress The network address of the source. 5.4.3.11 udPackageSize The maximum number of payload octets that may be transmitted in a single data unit on the flow. NOTE See examples in 5.4.2.7. 5.4.3.12 udPackageRate The number of data units per second that may be transmitted for the flow. 5.4.3.13 udPrivilege The privilege level associated with this flow. 5.4.3.14 udState The current state of this flow. 5.4.3.15 udCause This object shall be initialised to a zero-length value, which shall indicate “normal call clearing”, and shall be set by the managed unit when it changes udState to failed or disconnected. See also 6.3. 5.4.3.16 udSource The source name for this flow. NOTE This object is not writable by the management terminal. The source name is inherited from the source of the flow. 5.4.3.17 udDestination The destination name for this flow. 5.4.3.18 udService The service name for this flow. 5.4.3.19 udImportance The importance for this flow. 5.4.3.20 udPriority The reconnection priority for this flow. SIST EN 62379-5-1:2014

– 18 – IEC 62379-5-1:2014  IEC 2014 5.4.3.21 udStartTime This object shall be initialised to a zero-length octet string. The managed unit may set it to the time at which the flow should be connected, see 6.2. 5.4.3.22 udEndTime The time after which the network may release the resources reserved for this flow. A zero-length octet string indicates that the flow is to remain connected indefinitely. 5.4.3.23 udConnectTime The number of seconds for which this flow has been active or the maximum CardinalNumber value, whichever is less, zero if the state is not active. 5.4.3.24 udConnectCount The number of times this flow has been connected (includes both rerouting and automatic reconnection). Connection of a flow is only counted when it has been active for at least 1 min. The count may be reset by writing the value zero. Writing any other value shall be rejected with the badValue error code. 5.4.3.25 udRemembered If true, indicates this is a “remembered” flow which should be reconnected after a disconnection by the network (for instance as a result of a link failure) or a reset of the managed unit. 5.4.3.26 udDestBlockId When udState is readyToConnect or active, indicates the identifier of the block to which this flow should be internally connected, or nullBlock if no internal connection is to be made. The value in other states is not defined by this standard. Note that there are two ways to connect a block's input to an external source. The input can be identified by udDestBlockId and udDestBlockInput, in which case the managed unit makes the internal connection, or these objects can be left as zero and the internal connection are made explicitly after the managed unit has set udNetBlockOutput to a non-zero value. The former is a simpler process for the management terminal. The latter allows the management terminal to check the format being received before making the internal connection and, if the destination block already has a connection, to wait until data units are being received on the new connection before making the switch. 5.4.3.27 udDestBlockInput The input number, of the block identified by udDestBlockId, to which this flow should be internally connected. The value of this object shall be ignored by the managed unit when connecting a flow if udDestBlockId is nullBlock, also if the block identified by udDestBlockId only has one input. 5.4.3.28 udFlowIdStandard true if udFlowIdentifier is in the format specified in IEC 62379-5-2, false otherwise. Note that SIST EN 62379-5-1:2014

IEC 62379-5-1:2014  IEC 2014 – 19 – – if the format specified in IEC 62379-5-2 is used, a flow has the same identifier in every piece of equipm
...