SMPTE 2021-0-2013 Broadcast Exchange Format - Roadmap for the 2021 Document Suite.pdf

《SMPTE 2021-0-2013 Broadcast Exchange Format - Roadmap for the 2021 Document Suite.pdf》由会员分享，可在线阅读，更多相关《SMPTE 2021-0-2013 Broadcast Exchange Format - Roadmap for the 2021 Document Suite.pdf（12页珍藏版）》请在麦多课文档分享上搜索。

1、 Copyright 2013 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved October 11, 2013 IO Document Roadmap The SMPTE 2021 suite of documents specifies the Broadcast eXchange Format (BXF). This particular document (SMPTE 2021-0-2013)

2、 serves as a roadmap to the entire suite of 2021 documents, as well as other related files. Documents in the SMPTE 2021 Suite SMPTE ST 2021-1 General Information and Informative Notes (Normative and Informative Sections) This document serves as the base standard document for the 2021 suite. It inclu

3、des a comprehensive set of definitions, discussion of system data flow, security, configuration, and a large set of informative notes. This document is critical to anyone implementing BXF, as it is referenced by all other documents in this suite. The distribution of SMPTE ST 2021-1 also includes: Sc

4、hema Definition File Collection (2021-1a-2009 Schema.zip) This is the collection of XSD files which are required to implement BXF. HTML Schema Documentation (2021-1b-2009 Schema HTML.zip) This is a visual representation of the entire BXF schema, including all XSDs. It provides a graphical, non techn

5、ical view into the structure of the schema from top to bottom, including relationships between portions of the schema, as well as complete documentation of all schema attributes and elements. SMPTE ST 2021-2 Protocol (Entirely Normative) This document specifically and exclusively deals with issues s

6、urrounding protocol as it relates to BXF. It addresses the nature of BXF TCP/IP connections, sending of messages, dealing with inactive connections, initiation of servers, timeout of services, encryption of BXF messages, message formats, as well as file-based transport. SMPTE EG 2021-3 Engineering G

7、uideline BXF Use Cases (Entirely Informative) This document provides a rich set of use cases, illustrating the use of BXF in real-world scenarios, complete with XML samples. The use cases cover such examples as: schedule, dub order, purge order, record order, transfer order, content notification, qu

8、eries, invoking schedules, heartbeat messages, as runs, playlist updates, and acquisition failures. This document is intended to assist those wishing to implement BXF in specific ways. Page 1 of 12 pages SMPTE 2021-0:2013 Revision of SMPTE 2021-0:2012 SMPTE ROADMAP Broadcast Exchange Format Roadmap

9、for the 2021 Document Suite SMPTE 2021-0:2013 Page 2 of 12 pages SMPTE EG 2021-4 Engineering Guideline BXF Schema Documentation (Entirely Informative) This document provides documentation of each of the schema definition files included with 2021 (the XSDs). It covers all of the XSD files, and explai

10、ns all of the attributes and elements contained in each. SMPTE RP 2021-5 Recommended Practice - Using Ad-ID and EIDR as alternate identifiers in SMPTE BXF and ATSC PMCP This document was created to assist BXF implementers with a recommendation for use of the two commonly used identifiers (Ad-ID and

11、EIDR) in a BXF environment. SMPTE RP 2021-9 Recommended Practice (Normative and Informative Sections) This document was created to assist BXF implementers who have read the other documents in the 2021 suite to create interoperable implementations. It covers such topics as: wellformedness and validat

12、ion, processing model, general conventions related to various messages, as well as transport protocol (both connection-based and file-based). Perhaps the most useful portion of this Recommended Practice is its enumeration of message types that are typically used by different types of applications. I

13、f you are implementing BXF for an automation system, for instance, you can go directly to that portion of the document to see what parts of BXF are specifically applicable to your system. The document then goes into each major subset of BXF (configuration, content, content transfer, format, and sche

14、dule) in detail. The document also includes annexes covering: supported extensions, message type usages, error handling, and protocol transport. Changes Contained In BXF 2.0 BXF 2.0 consists of a collection of four significant schema updates, adding new capabilities required by implementers. It is i

15、mportant to note that these changes are all backward-compatible. Existing BXF implementations will continue to operate as they always have. A new set of XSD (schema definition files) as well as XML samples is included in the 2021 package. Below is an outline of the changes included within BXF 2.0. 1

16、. Change to all XSD headers for this new release: In order to distinguish BXF 2.0 schemas from those of BXF 1.0, the headers in each of the BXF XSD files have been updated to reflect the new version, as well as a new location for the BXF 2.0 schemas. Old Version of all headers: New Version of all he

17、aders: SMPTE 2021-0:2013 Page 3 of 12 pages SMPTE 2021-0:2013 Page 4 of 12 pages 2. Addition of support for sponsored secondary events A new structure has been added within the BXF nonprimaryevent.xsd schema definition. This allows a non-primary event to be either a standard non-advertising related

18、event (as was allowed in BXF 1.0), or an advertising-related event (indicated in the schema as a NonProgramEvent). This allows the scheduling of a non-primary program event that plays concurrently with the primary event being played. An example would be the squeezed-back end credits of a program (no

19、n-primary event) that airs concurrently with the primary event start of the following program. nonprimaryevent.xsd Version 1.0 Version 2.0 New Version supports a choice between NonProgramEvents and ProgramEvent Used to specify non-primary events that use speciific interstitial content Used to specif

20、y non-primary events that use speciific interstitial content SMPTE 2021-0:2013 Page 5 of 12 pages Used to specify non-primary events that use specific program content SMPTE 2021-0:2013 Page 6 of 12 pages 3. Support for Reuse of House Numbers It is a reality that house numbers are re-used in broadcas

21、t operations worldwide. The ATSCs A/57B standard accommodates this fact with support for a duration of effectiveness for house numbers. In BXF 2.0, support has been added to the bxfcontentid schema definition file to include four new attributes to allow for support of this. bxfcontentid.xsd Version

22、1.0 Version 2.0 New Version supports the ability to set the duration of effectiveness for a house number and to make it compatible with A/57s definitions. Generally user defined at a specific site and will only be consistent within SMPTE 2021-0:2013 Page 7 of 12 pages the defined group of users Ther

23、e is no guarantee of transportability or uniqueness. The endOfDay and uniqueFor attributes are included for consistency under the ATSC A-57B definition for HouseNumber. This 5-bit unsigned integer shall be set to the hour of the day in UTC in which the broadcast day ends and the instant after which

24、the content_id values may be re-used according to unique_for. The value of this field shall be in the range of 023. The values 2431 are reserved. Note that thevalue of this field is expected to be static per broadcaster. This 9-bit unsigned integer shall be set to the number of days, rounded up, mea

25、sured relative to the hour indicated by end_of_day (endOfDay), during which the content_id value is not reassigned to different content. The value shall be in the range 1 to 511. The value zero shall be forbidden. The value 511 shall have the special meaning of indefinitely. Note that the value of t

26、his field is expected to be essentially static per broadcaster, only changing when the method of house numbering is changed. Note also that decoders can treat stored content_id values as unique until the unique_for uniqueFor) fields expire, which can be implemented by decrementing all stored unique_

27、for (uniqueFor) fields by one every day at the end_of_day (endOfDay) until they reach zero. SMPTE 2021-0:2013 Page 8 of 12 pages SMPTE 2021-0:2013 Page 9 of 12 pages 4. Multi Language Support Many users of BXF must deal with on-air material that exists in multiple languages. BXF 1.0 only allowed for

28、 a single Event Title and Event Description on each event. This meant that a single language had to be chosen. BXF 2.0 adds support for multiple Event Titles and Event Descriptions, allowing the title and description to be included in multiple languages. eventdata.xsd Version 1.0 Version 2.0 New Ver

29、sion supports the ability to enter multiple EventTitles and EventDescriptions so that more than one language can be included in a single message. SMPTE 2021-0:2013 Page 10 of 12 pages Description of the SMPTE 2021-0:2013 Page 11 of 12 pages event Description of the event 5. Ability to communicate ev

30、ents surrounding currently airing event As BXF has introduced the ability for systems to exchange data relating to schedules and as runs in near real time, the need has arisen for a simple structure to communicate a quick update, showing events just aired, the event currently airing, and events abou

31、t to air. BXF 2.0 adds this ability to the schedule schema definition via a new node (RealTimeDetail). Using this new structure the current event, x events immediately prior to the one currently airing (a negative value in the RealTimeSequence node), as well as y events immediately following the one

32、 currently airing (a positive value in the RealTimeSequence node) can be communicated. schedule.xsd Version 1.0 Version 2.0 New Version supports the ability to handle real time actions on the automation event process. This would allow the communication of the prior event completed, the event that is

33、 currently running and the event that is next up. SMPTE 2021-0:2013 Page 12 of 12 pages Links to the events as described in ScheduledEvent if in the future or in the AsRun if current or in the past. Can be null if the event was added manually. If zero, indicates the current airing event; if negative

34、, indicates that the event was in the past and has aired; if positive, indicates an event that will air. The integer number indicates the sequence order going forward or backward in time. Either the actual start time if the event already aired or is airing or the expected start time if in the future

35、. Changes Contained In BXF 3.0 The enhancements to BXF included in the 3.0 suite of documents and schema are enumerated in EG 2021-4:2013 Schema Documentation. Each XSD that has been updated as part of the BXF 3.0 effort will have a subsection under its own XSD heading (e.g. Audio.XSD), labeled BXF 3.0 Changes. In these subsections, the changes affecting the schema in question are listed and described.