1、 Access to Content for (SMPTE EG 2021-3:2015) (Click here to view the publication) This Page is not part of the original publication: This page has been created by IHS as a convenience to the user in order to provide access to the content as authorized by the Copyright holder of this document. Click
2、 the link(s) below to access the content and use normal procedures for downloading or opening the files. SMPTE_Additional Data Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer when the group complains, he diverts their attention to their own fau
3、lts. Phoebe gets money she doesnt want; she complains and gets more; she gives it away and gets a can of soda in return.which contains a thumb. The beverage company gives her $7000. Monicas new boyfriend is a hit with her friends, but Monicas not too sure. Friends SMPTE EG 2021-3:2015 SMPTE 2015 All
4、 rights reserved Page 25 2.8 Query Request Context of Use: Any particular system might have the need to find out information that another system contains. Therefore, using the common xml schema amongst the participating systems, a SQL-like query is able to be used via a subset of XPATH 2.0 (http:/ww
5、w.w3.org/TR/xpath20/) to implement the and nodes syntax. Origination System: Any Destination System: Any Trigger: The originating system desires to query the target system for useful information. Additional Stakeholders and Interests: Any/all Preconditions: Information is needed that the originating
6、 system does not have and/or needs to verify from a target system Main Success Scenario: System A: 1. User of originating system A requests information from System B. System B: 2. Performs a local query using the where-clause of the originating systems query 3. Returns the desired information to the
7、 originating system using the return-structure scheme Examples: 1. All active channels for a given date range Schedule/scheduleStart=“2006-08-16T05:00:00.00“ Schedule/Channel/* Note: The “*” indicates all sub-nodes at that level and below, if the “*” is omitted only that node and its attributes woul
8、d returned. 2. Schedule identification for a given date range. Schedule/scheduleStart=“2006-08-16T05:00:00.00“ Schedule Must return: 3. Schedules for a specific Channel for a given date range. Schedule/Channel/Name=“WXYZ“ and Schedule/scheduleStart=“2006-08-16T05:00:00.00“ Schedule/* SMPTE EG 2021-3
9、:2015 SMPTE 2015 All rights reserved Page 27 This query would return schedules including all events for Channel Named “WXYZ” with a scheduleStart=2006-08-16T05:00:00.00: WXYZ 4. Only “As Run” schedules on Channel WXYZ Schedule/Channel/Name=“WXYZ“ and Schedule/scheduleStart=“2006-08-16T05:00:00.00“ S
10、chedule/AsRun/* 5. Content Transfer Query return status of all content transfers on the device specified as the message destination. * ContentTransfer Returns: SMPTE EG 2021-3:2015 SMPTE 2015 All rights reserved Page 28 2.9 Invoke Schedule Context of Use: The traffic system is responsible for mainta
11、ining the composite programming schedule. This composite schedule would include any program elements, commercials, promotions, and other interstitial material. The schedule is transferred to the automation system which is responsible for the control of systems and equipment involved in playing the s
12、chedule to air over the Channel. The Invoke Schedule example shows the activation of a schedule, which had previously been transferred to the automation system. Origination System: Traffic Destination System: Automation Trigger: A previously-transferred schedule is to be activated for broadcast. Add
13、itional Stakeholders and Interests: Traffic System Responsible for generating and disseminating the composite schedule. Traffic is also responsible for notifying the automation system of changes, and for bringing a new schedule into use to control a given Channel of playback. Automation User- Receiv
14、ing an accurate schedule in a timely manner such that it can be used to ready the schedule items for playback. Master Control Operator- Wants accurate schedules and accurate data so the right content plays at the right time. The schedule activation from traffic to be available for visual verificatio
15、n and manual updates either directly in Traffic or via Automation. Preconditions: A session has been established. Main Success Scenario: Invoke Schedule: 1. A request is sent for a particular schedule is activated. The schedule is identified by the BxFMessage.Schedules.ScheduleID attribute. 2. Autom
16、ation validates the existence and state of the schedule referenced in the request. If validation of the request is successful, Automation sends an ACK (BxFMessage.MessageType = acknowledgement), and commences with the requested operation. 3. The outcome of the operation is conveyed back to Traffic i
17、n a Reply message generated by Automation, indicating result status in BxFMessage.Status. Example: Message to automation to load the schedule into a usable playlist SMPTE EG 2021-3:2015 SMPTE 2015 All rights reserved Page 29 2.10 Heartbeat Context of Use: Any system that is interested in communicati
18、ng with another can verify that the target system is available to communicate messages. A heartbeat message can be used for this verification, thereby ensuring that messages can proceed between the systems. Origination System: Any Destination System: Any Trigger: A system is interested in knowing th
19、e communication status of another system, so a heartbeat message is sent. Additional Stakeholders and Interests: Any/all Preconditions: There is a need to determine whether a system of interest is available to communicate using BXF. Main Success Scenario: Traffic department: 1. Traffic user wants to
20、 utilize various use-cases for daily operations that include the Content Delivery system. 2. The traffic application submits a heartbeat message to ensure Content Delivery is available for messaging. Content Delivery system: 3. Content Delivery receives the heartbeat message and responds if it is av
21、ailable to communicate with the inquiring system. 4. Use Case ends. Example: Message to query the availability of a Content Delivery System: 2.11 As Run Context of Use: Automation systems are supplied with events which are eligible for going to air. These events will normally either be successfully played out or become a discrepancy. Both statuses are communicated to the traffic system and record appropriate reconciliation of the event. This use case covers the steps necessary for the communication about an event that has been aired, between automation system and the traffic system.
