hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.7.1 General | 5.3. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.1 General | DVB services may be delivered in MPEG DASH format [17] using the MPEG DASH specification [16]. An MPEG DASH Period relative Timeline is a Timeline that is relative to the start of a chosen Period in an MPEG DASH Presentation. The chosen Period is determined by the Timeline Selector used to select this Timeline and is k... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.7.2 Timeline Selector for a Period relative Timeline | The Timeline Selector for a Period relative Timeline for an MPEG DASH presentation is a URN with one of the following forms: 1) urn:dvb:css:timeline:mpd:period:rel:<ticks-per-second> 2) urn:dvb:css:timeline:mpd:period:rel:<ticks-per-second>:<period-id> For both forms urn:dvb:css:timeline:mpd:period:rel identifies that ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.7.3 Determining Time Values and Timestamps for a Period relative Timeline | For an MPEG DASH Period relative Timeline, the Time Value is the total amount of time elapsed since the start of a chosen MPEG DASH Period. The chosen Period is the one chosen as the base Period for the Timed Content currently being presented to the user. NOTE 1: The value of the Period@start attribute is not included ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.4 Timeline correlation | A correlation between two Timelines expresses a deterministic linear monotonic relationship between them, such that there is a one-to-one mapping between Time Values on each Timeline. This is the basis of how a CSA can translate between a Material Timeline and a Synchronization Timeline, or how a CSA or TV Device can r... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5 Material Information | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.1 General | Material Information is a collection of data describing the properties of one or more Materials including identifiers, private data, a Timeline for the Material and details of Trigger Events that may occur while the Material is being presented. Material Information also details the available Synchronization Timelines d... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.2 Material | A Material represents a segment of content with an editorially significant meaning, including, but not necessarily limited to: • an interval of a broadcast service during which a given DVB event is signalled in EIT present/following actual as being the present event; • an individual advert, trailer or continuity announ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.3 Material Identifiers | A Material shall have one or more Material Identifiers. A Material Identifier identifies a Material. A Material Identifier has type and value. The value shall consist of a single token string of characters with no separators (space characters or newline characters). The type is encoded as a URI and shall scope the iden... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.4 Synchronization Timeline information | An item of Synchronization Timeline information describes: • the properties of a Synchronization Timelines (see clause 5.3.2); • the circumstances in which that Synchronization Timeline may be used; • optionally the lead-in circumstances just prior to when that Synchronization Timeline may be used; • the mappings betwe... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.5 Timeline mappings | For Material Information a Timeline Mapping is a relationship between a Synchronization Timeline and a Material Timeline. It is associated with a set of one or more Correlation Timestamps (see clause 5.5.6). The representation of a Timeline Mapping in JSON is defined in clause 5.5.9.6. A Timeline Mapping also indicates... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.6 Correlation Timestamps | A Timeline Mapping is associated with one or more Correlation Timestamps. As described in clause 5.4, a Correlation Timestamp between two Timelines (combined with knowledge of the tick rates of the timelines) enables points on one Timeline to be converted to and from a point on another Timeline. The representation of a... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.7 Trigger Event info | A Material may have Trigger Event info. Trigger Event info describes Trigger Events that may occur while a Material is being presented. This information provides details needed to request that the TV Device notify the CSA if a Trigger Event occurs via the CSS-TE interface (see procedures defined in clause 4.3.6). The r... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.8 Process for determining which Materials are Active Materials | A Material is an Active Material if it relates to the editorial content currently being presented by the TV Device. Zero, one or more Materials may be active at any given moment. The CI reported by the TV and the current time position on a Synchronization Timeline are used by the CSA to determine whether a Material is ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9 JSON syntax for representing Material Information | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.1 General | 5. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.9.1 General | 5. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 9.1 General | Material Information shall be represented as JSON objects as defined in clause 5.5.9. The JSON schema defined in clause A.1.3 can be used to validate Material Information that is part of an MRS response JSON Document as defined in clause 7.3. The Material Information is delivered as part of a response from an MRS. The ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.2 JSON for Material | A Material object represents a Material as defined in clause 5.5.2. It is represented by a JSON object with properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the schema definition for "material" in the JSON schema in clause A.2.2. The template below illustrates this JS... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.3 JSON for Material Identifier | A Material Identifier object represents a Material Identifier as defined in clause 5.5.3. It is represented by a JSON object with properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the sub schema defined under the "ids" property in the schema definition for "material" i... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.4 JSON for Synchronization Timeline information | A Synchronization Timeline information object represents Synchronization Timeline information, as defined in clause 5.5.4, for a single Synchronization Timeline. It is represented by a JSON object with properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the schema defini... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.5 JSON for Timeline properties | A Timeline properties object defines the scale (rate) of a Timeline and may define its accuracy (as defined in clause 5.3.2). It is represented by a JSON object with properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the schema definition for "timelineProperties" define... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.6 JSON for Timeline Mapping | A Timeline Mapping defines a mapping interval (described in clause 5.5.5) to the Timeline of a Material from the Synchronization Timeline for the Synchronization Timeline information in which the Timeline Mapping is aggregated. ETSI ETSI TS 103 286-2 V1.3.1 (2022-01) 60 A Timeline Mapping is represented by a JSON objec... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.7 JSON for Correlation Timestamp | A Correlation Timestamp (as defined in clause 5.5.6) is represented by a JSON object with properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the schema definition for "correlation" defined in the JSON schema in clause A.1.2. The template below illustrates this JSON obje... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.5.9.8 Trigger Event Info | A Trigger Event Info object represents a set of Trigger Events, as defined in clause 5.5.7, that are applicable to a Material and the context in which to make the subscription. The object is represented by a JSON object with the properties defined in this clause. If such a JSON object is correctly formed, it can be val... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6 Content Identification and other Information (CII) | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.1 General | 5. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 6.1 General | Content Identification and other Information (CII) is reported by the TV Device to the CSA via the CSS-CII interface as part of the procedure defined in clause 4.3.2. CII provides the CSA with a Content Identifier for the Timed Content that is currently being presented by the TV Device and other information needed to e... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.2 Reporting the MRS URL | To determine the URL of the MRS for a DVB broadcast service, the TV Device shall look for a uri_linkage_descriptor with uri_linkage_type 0x02 that signals an MRS URL (as defined in clause 6.4.14 of ETSI EN 300 468 [13]). The TV Device shall look for this in the descriptor loops listed in table 5.6.2.1 that correspond t... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.3 Reporting the Content Identifier | The format of the Content Identifier shall be defined according to clause 5.2 according to the type of Timed Content being presented by the TV Device. If the TV Device does not know the Content Identifier, or if the TV Device is not presenting Timed Content (e.g. it is displaying a menu screen instead) then there is no... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.4 Status of presentation | The status of presentation of Timed Content is provided by the TV Device to inform the CSA of the status of presentation so that the CSA can adjust its behaviour and presentation if the CSA considers it appropriate to do so. The status of presentation shall be represented by a primary aspect of status followed by zero ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.6 Reporting a list of timeline options | The unordered list of Timeline Selectors and corresponding properties of Timelines shall contain zero, one or more options for Timelines that can be used as the Synchronization Timeline. Each option shall be expressed as a Timeline Selector with corresponding Timeline properties. The options represent suggestions by th... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.6.7 JSON Representation of Content Identification and other Information | Content Identification and other Information is represented by a JSON object with the properties defined in this clause. If such a JSON object is correctly formed, it can be validated by the root object of the JSON schema in clause A.1.4. The template below illustrates this JSON object: { "protocolVersion" : "1.1", (op... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7 Timestamps and Timeline Synchronization | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7.1 General | Timestamps are exchanged between the MSAS function of the TV Device and the SC function of the CSA to achieve Timeline Synchronization. This exchange takes place via the CSS-TS interface using the procedure defined in clause 4.3.5 using the protocol described in clause 9 and following the architectural concepts describ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7.2 Reference point for timestamping | This clause provides a reference model for the timestamping of Timed Content. Timestamping is the process in which a media sample (e.g. video frame or audio sample), identified by a Time Value on the Synchronization Timeline (e.g. PTS or MPEG-TEMI), is associated with a Wall Clock time. Having a well-defined reference ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7.3 Setup data | Setup data specifies the timeline that a CSA wishes to be used for Timestamps communicated via the CSS-TS interface as part of the Timeline Synchronization procedure defined in clause 4.3.5 using the protocol described in clause 9. It consists of the following information: • A Content Identifier stem. • A Timeline Sele... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7.4 Actual, Earliest and Latest Presentation Timestamp | An SC provides Actual, Earliest and Latest Presentation Timestamps to an MSAS via the CSS-TS interface as part of the Timeline Synchronization procedure described in clause 4.3.5 via the protocol described in clause 9. These Timestamps convey the earliest and latest times at which the SC is capable of presenting a give... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.7.5 Control Timestamps | An MSAS provides Control Timestamps to an SC via the CSS-TS interface as part of the Timeline Synchronization procedure described in clause 4.3.5 via the protocol described in clause 9. These Timestamps convey the times at which the SC is recommend to present a given point on the Synchronization Timeline. A Control Tim... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8 Trigger Events | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.1 General | 5. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.1 General | JSON objects (defined in clause 5.8.5) are exchanged between the CSA and the TV Device via the CSS-TS interface using the procedures described in clause 4.3.6 via a protocol defined in clause 10. These objects allow the CSA to manage subscriptions for Trigger Events and the TV Device to notify the Companion Screen Appl... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.2 Encoding Trigger Event locations | Trigger Event locations are encoded using a URI. The format depends on the broadcast encoding used for Trigger Events. The formats defined by the present document are summarized in table 5.8.2.1. Table 5.8.2.1: Trigger Event location URI format Trigger Event source Clause Event location URI DSM-CC "do it now" stream ev... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.3 Reference point for Trigger Events | Trigger Event notifications carry a presentationWallClockTime property. This represents presentation time for the event in terms of wall clock time. This allows the CSA to compute when it should act on the event. The time of presentation is in terms of the same reference point as is used for timestamping (see clause 5.... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4 Trigger Event Sources | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.1 General | This clause defines how Trigger Events are signalled in the content. References to the Trigger Events in messages between the CSA and TV Device are encoded as URIs. The URIs for the Trigger Event signalling mechanisms defined in the present document are defined in clause 5.8.4. ETSI ETSI TS 103 286-2 V1.3.1 (2022-01) 7... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.2 DSM-CC "do it now" Stream Events | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.2.1 Encoding in MPEG TS | The present document references the definitions of DSM-CC "do it now" stream events in MPEG Transport Streams in the following specifications: • ETSI ES 202 184 [21]. • ETSI TS 102 727 [22]. • ETSI TS 102 809 [23]. These have compatible definitions of how the Stream Descriptor aspect of DSM-CC "do it now" events are en... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.2.2 Encoding the URI referencing the Trigger Event | URI references to DSM-CC "do it now" stream events in messages between the CSA and TV Device are encoded as URNs as follows: • urn:dvb:css:triggerevent:dsmcc:<component_tag>:<eventId> urn:dvb:css:triggerevent:dsmcc identifies a Trigger Event according to clause 5.8.4. component_tag is the base-ten integer representatio... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.2.3 Trigger Event data | The DSM-CC Stream Event Descriptor can optionally carry event data in its privateDataByte field. If event data is present in the Stream Event Descriptor, it shall be base64 encoded and conveyed in the triggerEventData property of the Trigger Event Notification message. If there is no data in the privateDataByte field t... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.2.4 Reference point | The presentationWallClockTime property of the event notification shall be the Wall Clock time at the reference point (see clause 5.7.2) corresponding to when the surrounding content reaches the reference point. The surrounding content is defined as being the audio and/or video content which surrounds the Transport Stre... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.3 DASH Events | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.3.1 Encoding in the DASH Content | DASH defines two methods for carrying events, as described in clause 9 of ETSI TS 103 285 [16], in-band events as described in clause 5.10.3 of DASH [17] that use the 'emsg' box and MPD events as described in clause 5.10.2 of DASH [17]. Both of these mechanisms use a URI to scope and identify the event stream, and both... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.3.2 Encoding the URI referencing the event | In both cases of DASH events, a URI is used to indicate the event stream. This URI shall be comprised of the @schemeIdUri attribute value followed by a colon (":") followed by the base64 encoded @value attribute value of the EventStream or InBandEventStream element within the MPD that correspond to the desired events. ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.3.3 Event Data | When an event is received, a Trigger Event Notification message shall be generated, with properties as defined below. Where MPD events are used, then: • the @id attribute of the Event element, if present, shall be converted to a string and carried in the triggerEventId property. If this attribute is not present, then t... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.3.4 Reference Point | DASH events include explicit presentation and duration time information. The presentationWallClockTime property of the trigger event notification message shall be computed as: • For events conveyed by the 'emsg' box, the Wall Clock time corresponding to the presentation time derived, assuming a timelineSpeedMultiplier ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.4.4 Other Event Sources | It is possible that other event sources may be present, and that some of these sources may be proprietary. These sources will be identified by URIs, and these may be communicated from the MRS, or via other mechanisms that are outside the scope of the present document. The URIs that define these other event sources may ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.5 Messages | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.5.1 General | This clause defines messages for Trigger Events. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.5.2 Trigger Event Session Setup (TESS) message | After the protocol transport connection to the CSS-TE endpoint is successfully opened from the CSA to the TV Device (see clause 10.2), the first message sent from the CSA to the TV Device shall be the Trigger Event Session Setup. This message establishes the context of this connection as being the presentation of Timed... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.5.3 Trigger Event Subscription Management (TESM) messages | A single message is defined to encode the actions required by the CSA to manage Trigger Event subscriptions: • requesting a new subscription; • removing a previous subscription. The message carries: • the identifier for the Trigger Event; • the action to be performed on that event subscription. The TESM message is repr... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.8.5.4 Trigger Event Notification (TEN) message | A single message is defined to encode the notification of a Trigger Event by the TV Device to the CSA or changes in availability of the Trigger Event listener in the TV Device. The message carries: • the identifier for the Trigger Event • the Trigger Event data (if present, null otherwise) from the event signalling • t... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.9 Private data | 5.9.1 General The objects defined in clause 5 are used to convey information between parts of the ecosystem that support a companion experience. The information contained within them represents only that information needed for the generic ecosystem. In a given use of this system, e.g. to support a specific application,... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.9.2 JSON for an item of private data | A private data object represents private data as defined in clause 5.9.1. It is represented by a JSON object with the properties defined here. If such a JSON object is correctly formed, it can be validated by the schema definition for "private" defined in the JSON schema in clause A.1.2. The template below illustrates ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 6.2 Protocol | An overview of the procedures of the protocol (subscribe, notify and unsubscribe) are described in clause 4.3.2. The TV Device shall allow multiple CSAs to be connected to the CSS-CII service endpoint simultaneously. When a CSA tries to connect to the CSS-CII service endpoint, the TV Device may decline the request beca... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 6.3 Protocol transport | The TV Device shall implement a CSS-CII service endpoint that implements the server side of the WebSocket protocol version 13 as defined in IETF RFC 6455 [8]. The service endpoints provided by the TV Device in the CII message is the WebSocket URL of the WebSocket server. As defined in section 3 of the WebSocket protoco... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7 Material Resolution Service (CSS-MRS) | 7.1 General The content identifier, retrieved as described in clause 6, can be translated into Material Information, potentially including Timeline Information, by the Material Resolution Service. The following clauses define the means by which the CSA requests the MRS to perform the translation and the format of the i... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.2 Material resolution protocol | The protocol used to interact with the MRS shall be a REST API running over HTTP 1.1, as defined in IETF RFC 2616 [9] or HTTPS (specifically HTTP 1.1 running over TLS), as defined in IETF RFC 2818 [10]. The MRS URL indicates which protocol is to be used. Whilst the HTTP response codes would normally be status code 200 ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.3 Material resolution protocol query | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.3.1 Material resolution protocol general requirements | The CSA shall issue GET requests to the MRS_REST_API URL defined in clause 7.3.2. The CSA shall include an "Accept: application/json" header field in the request. ETSI ETSI TS 103 286-2 V1.3.1 (2022-01) 79 The CSA shall support both gzip and identity (for non-gzipped JSON) encoding of responses, and include in the requ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.3.2 Material resolution protocol URL | The URL that forms the MRS HTTP REST query shall be constructed by the concatenation, in order, of three parts: • The mrsUrl as identified by the TV Device as described in clause 5.6.2 and as returned by the TV Device in the mechanism described in clause 6.2. • The fixed string "/v1.1/MRS". • The one material resolutio... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.3.3 Material resolution protocol parameter | The parameter name for the Content Identifier shall be the string "contentId" and the value shall be a Content Identifier (as defined in clause 5.2). The parameter value shall be represented as an ASCII character string. The parameter value shall comply with the URI encoding rules defined in IETF RFC 3986 [1]. Specific... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.4 Material resolution protocol response | The HTTP headers of the MRS response shall include the "Expires" header. The HTTP headers of the MRS response shall also include the following CORS [14] headers, as defined in table 7.4.1. Table 7.4.1: Required CORS headers in MRS protocol CORS Header Field Recommended Value Notes Access-Control-Allow- Origin "*" Value... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.5 Material resolution protocol example (informative) | The following is an example of the interaction based on the case where the returned MRS URL is http://mrs.example.com and the content identifier is dvb://233a.1004.1044;35f7~20131004T0930Z--PT01H00M (from the example in clause C.2.1). This example represents the required subset of header fields; other header fields in ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6 MRS Update Protocols | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.1 General | The MI, or parts of it, as returned by the MRS may change whilst the content is viewed and so may require updates. Where the updateMaterial array is present and populated, it means that updates may, but need not, occur to the Materials detailed in the materials property. Where the updateTimelineSync array is present an... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.2 JSON syntax for update array element | The objects that make up the updateMaterial array and updateTimelineSync array shall follow the template: { "url" : <url>, "mimeType" : <string>, "protocolSpecificData" : <string> (optional) } Required properties: • url: this carries the URL representation of the location of update information. It shall be complete and... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.3 Update response JSON | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.3.1 Update response JSON types | The JSON object returned by the update protocols conveys changes to Materials or Synchronization Timeline Information. The JSON object shall be as defined in clause 7.4, but all properties apart from "type" are optional and it shall have additional properties as defined below in this clause. The type property shall hav... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.3.2 Semantics of Material update responses | The updates that are received through the URLs carried in the updateMaterial array property shall be a JSON object where if a property of that JSON object is present, it indicates an update to the value received in the original response, and shall be used to replace the value that property held in the original response... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.3.3 Semantics of Timeline Sync update responses | The updates that are received through the URLs carried in the updateTimelineSync array property shall be JSON Patch objects as defined in IETF RFC 6902 [20]. These patch objects convey updates to the syncTimelineInformation object returned by the MRS according to the JSON patch object syntax. The JSON patch objects sha... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.4 Long poll | A long poll is a normal request issued to the specified URL, where the response is as per clause 7.4 but where the JSON object in the response complies with the semantics defined in clauses 7.6.3.2 and 7.6.3.3 as appropriate. NOTE 1: The use of the relevant If-Modified-Since or If-Match headers as defined in clause 7.3... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.5 WebSocket protocol | The mimeType shall take the format application/json for updateMaterial or application/json-patch for updateTimelineSync and the protocol component of the URL shall be "ws" or "wss". This URL shall refer to the server- side of the WebSocket protocol version 13 as defined in IETF RFC 6455 [8]. All messages sent shall be ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.6 Server Sent Events protocol | Server-sent events (SSE) shall comply with the W3C specification [19]. The mimeType shall be "text/event-stream" and the protocol component of the URL shall be "http" or "https". The event type as signalled by the "event:" line of the event stream (as defined in SSE [19]) shall be set to "MIupdate" (i.e. the line "even... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 7.6.7 BOSH/XMPP protocol | The mimeType for XMPP IETF RFC 6120 [29] based updates shall be application/jabber+xml. The protocol part of the URL is unspecified by IETF RFC 6120 [29], but should normally be "http" or "https". The protocolSpecificData property shall be present and shall contain the base64 encoded XML stanza that shall be sent by th... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8 Wall Clock (CSS-WC) | 8.1 General To compensate for latencies in network communication between TV Device and CSA, the Timestamps exchanged in the Timeline Synchronization procedure make reference to a Wall Clock that is assumed to be synchronized between the TV Device and the CSA. Wall Clock Synchronization establishes a best effort approxi... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.2 Protocol overview | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.2.0 Protocol Introduction | The protocol between a WC Client and WC Server consists of a regular exchange of messages between them. The WC Client periodically sends a request message to which the WC Server shall respond. The protocol carries the following information: • Time values, used to estimate the offset between WC Server Wall Clock and WC ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.2.1 Time values and estimating Wall Clock offset | The WC Client records a time value T1 for the moment at which the request message is assembled and sent to the WC Server and the time value T4 for the moment at which the response message is received. The WC Server shall, similarly, record its own Wall Clock time value T2 at which the request message is received and it... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.2.2 Measurement precision | Measurement precision is the maximum error that there may be in a measurement of the Wall Clock due to the granularity by which the ticks of the Wall Clock increment, and by the time it takes to measure its value. If the smallest regular increment of the Wall Clock is N ticks at a nominal tick rate of M ticks per secon... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.2.3 Maximum frequency error | A Wall Clock may vary in frequency over time (slew from its nominal frequency) for a range of reasons. The maximum frequency error quantifies the maximum amount by which this may happen. Frequency error is quantified in units of parts per million (ppm). A frequency error of N ppm means that a period of time t seconds m... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.3 Wall Clock protocol | The syntax of the Wall Clock Synchronization messages is described in table 8.3.1. Table 8.3.1: Syntax of Wall Clock synchronization message Syntax Value No. bits Identifier wall_clock_sync_message { version 0 8 uimsbf message_type 8 uimsbf precision 8 tcimsbf reserved 0 8 bslbf max_freq_error 32 uimsbf originate_timev... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 8.4 Wall clock protocol transport | A Wall Clock Synchronization message shall be transported as the payload of a single UDP packet. A WC Server shall provide a Wall Clock Synchronization service endpoint (CSS-WC). The WC Server shall listen for Wall Clock Synchronization protocol request messages from CSAs on the IP interface and port number correspondi... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 9 Timeline Synchronization (CSS-TS) | 9.1 General Timeline Synchronization is the process by which the SC elementary function of the CSA and the MSAS elementary function of the TV Device exchange Timestamp information via the CSS-TS interface in order to coordinate the synchronized presentation of Timed Content. A Synchronization Timeline is agreed upon, a... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 9.2 Protocol | The MSAS shall allow multiple CSAs to have open sessions to the CSS-TS service endpoints simultaneously. The MSAS shall allow a CSA to have multiple open sessions to a single CSS-TS service endpoint. When a CSA begins the session the MSAS may decline to begin the session if the number of SCs communicating with the MSAS... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 9.3 Protocol transport | The MSAS elementary function of the TV Device shall implement a CSS-TS service endpoint that implements the server-side of the WebSocket protocol version 13 as defined in IETF RFC 6455 [8]. The service endpoint provided by the MSAS function in the CII message is the WebSocket URL of the WebSocket server. NOTE 1: As def... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 10 Trigger Events (CSS-TE) | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 10.1 General | The CSA obtains Trigger Event notifications from the TV Device to enable the CSA to discover if there are editorially significant occurrences in the media currently being presented by the TV Device. The Trigger Event notification and the optional data it carries allow the CSA to respond to the event. This functionality... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 10.2 Protocol | An overview of the procedures of the protocol are described in clause 4.3.6 and the message exchanged are described in clause 5.8. Subject to the number of sessions not excluding any limit that the TV Device may impose, the TV Device shall allow multiple CSAs to have simultaneously open sessions to the CSS-TE service e... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 10.3 Protocol Transport | A TV Device that supports the a CSS-TE service endpoint shall implement the server-side of the WebSocket protocol version 13 as defined in IETF RFC 6455 [8]. The service CSS-TE endpoint provided by the TV Device is describable by a WebSocket URL. NOTE 1: As defined in section 3 of the WebSocket protocol specification [... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.