hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.5.5 ProgramInformation.BasicDescription Element [More Episodes] | Table 45: ProgramInformation.BasicDescription Element [More Episodes] Element Name/ Required Description Example Title Mandatory {1..2} per language A label identifying the name of the Box Set. A Title element with @type attribute set to main is mandatory. A second Title element with @type attribute set to secondary is... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.5.6 GroupInformation.BasicDescription Element [Box Set List] | Table 46: GroupInformation.BasicDescription Element [Box Set Lists] Element Name/ Required Description Example Title Mandatory {1} per language A label identifying the name of the Box Set. The @type attribute shall carry a value of main. The character length of the Title shall not exceed 80 characters. <Title type="mai... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.5.7 GroupInformation.BasicDescription Element [More Episodes] | Table 47: GroupInformation.BasicDescription Element [More Episodes] Element Name/ Required Description Example RelatedMaterial for pagination Optional {0, 2, 4} A link to a relative page of results. There may be up to 4, depending on the current page. See clause 6.9 for further details. See clause 6.10.13 for further d... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.5.8 GroupInformation.BasicDescription Element [Box Set Categories] | Table 48: GroupInformation.BasicDescription Element [Box Set Categories - parent category] Element Name/ Required Description Example Title Mandatory {1} per language A label identifying the name of the Box Set. The @type attribute shall carry a value of main. The character length of the Title shall not exceed 80 chara... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.6 Schedule Element | The Schedule element provides an envelope for a number of individual ScheduleEvent elements associated with a single service. The attributes of the Schedule element provide information on which service the schedule is associated with and the period covered. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 112 Table 50: Schedule E... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.7 ScheduleEvent Element | Multiple ScheduleEvent elements are wrapped within a Schedule element, with a Schedule element per service in Schedule endpoint responses. Each ScheduleEvent element identifies an individual programme within the schedule period and there may be gaps in the schedule. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 113 Table 51: S... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.8 OnDemandProgram Element | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.8.1 Introduction | The OnDemandProgram element is used in a number of locations and the included metadata is different depending on context. The variations are therefore displayed in individual subsections below; the applicable endpoint is indicated in square [ ] brackets. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 114 |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.8.2 OnDemandProgram Element [Schedules, Detailed Programme Information] | Table 52: OnDemandProgram Element [Schedules, Detailed Programme Information] Element Name/ Required Description Example @serviceIDRef Mandatory {1} It shall match UniqueIdentifier or ContentGuideServiceRef in the Service element (see clause 5.5.2). <OnDemandProgram serviceIDRef="http:/ /www.channel7.com/se rvices/dtt/... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.8.3 OnDemandProgram Element [More Episodes] | Table 53: OnDemandProgram Element [More Episodes] Element Name/ Required Description Example @serviceIDRef Mandatory {1} It shall match UniqueIdentifier in the Service element (see clause 5.5.2). The ServiceInstance element of Service element may be used to provide DVB-I Content guide for a linear broadcast channel. <O... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.8.4 OnDemandProgram Element [Box Set Contents] | Table 54: OnDemandProgram Element [Box Set Contents] Element Name/ Required Description Example @serviceIDRef Mandatory {1} It shall match UniqueIdentifier in the Service element (see clause 5.5.2). The ServiceInstance element of Service element may be used to provide DVB-I Content guide for a linear broadcast channel.... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.9 AVAttributes Element | Table 55: AVAttributes Element Element Name/ Required Description Example AudioAttributes Optional {0..2} per language Describes the audio characteristics. See clause 6.10.10. A separate AudioAttributes element may be provided for each AudioLanguage@purpose (Main and Audio Described). Multiple languages may be provided... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.17.1 Introduction | The GroupInformation element is used in a number of locations and the included metadata is different depending on context. The variations are therefore displayed in individual subsections below; the applicable endpoint is indicated in square [ ] brackets. 6.10.17.2 GroupInformation Element [Box Set Categories, Box Set ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.17.3 GroupInformation Element [Now/Next Filtered Schedules] | Table 64: GroupInformation Element [Now/Next Filtered Schedules] Element Name/ Required Description Example @groupId Mandatory {1} The CRID of the group, identifying whether the group represents the current, future or previous events. This shall be one of: • crid://dvb.org/metadata/schedules/now- next/now • crid://dvb.... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.10.17.4 GroupInformation Element [More Episodes] | Table 65: GroupInformation Element [More Episodes] Element Name/ Required Description Example @groupId Mandatory {1} The CRID of the results group, identifying that the group represents the response to a More Episodes request. <GroupInformation groupId="crid://mdata.co. uk/more-episodes/results" ordered="true" numOfIte... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11 Classification Terms | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.1 Introduction | This clause details the Classification Scheme (CS) terms used for the DVB-I content guide. The CS terms are profiled from MPEG-7 [20], TV-Anytime [7] and the Freeview Play specification [i.11]. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.2 Audio Mix Types | The values identified in Table 66 are profiled from MPEG-7, ISO/IEC 15938-5 [20]. Table 66: Audio Mix Types XPath(s) .../InstanceDescription/AVAttributes/AudioAttributes/MixType[@href] Fully Qualified Classification Scheme Term Term Name urn:mpeg:mpeg7:cs:AudioPresentationCS:2001:2 Mono urn:mpeg:mpeg7:cs:AudioPresentat... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.3 Audio Purpose | The values identified in Table 67 are profiled from TV-Anytime, ETSI TS 102 822-3-1 [7]. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 126 Table 67: Audio Purpose XPath(s) .../InstanceDescription/AVAttributes/AudioAttributes/AudioLanguage[@purpose] Fully Qualified Classification Scheme Term Term Name urn:tva:metadata:cs:AudioP... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.4 Caption Coding Format | The values identified in Table 68 are profiled from TV-Anytime, ETSI TS 102 822-3-1 [7]. Table 68: Caption Coding Format XPath(s) .../InstanceDescription/AVAttributes/CaptioningAttributes/Coding[@href] Fully Qualified Classification Scheme Term Term Name urn:tva:metadata:cs:CaptionCodingFormatCS:2015:2.1 DVB Subtitles ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.5 Content Genre | All values from the TV-Anytime ContentCS (urn:tva:metadata:cs:ContentCS:2011) or FormatCS (urn:tva:metadata:cs:FormatCS:2011) defined in ETSI TS 102 822-3-1 [7] or the DVB ContentSubject defined in clause D.5 are applicable. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.6 Credit Role | The values identified in Table 69 are profiled from MPEG-7, ISO/IEC 15938-5 [20], and TV-Anytime, ETSI TS 102 822-3-1 [7]. Table 69: Credit Role XPath(s) .../BasicDescription/CreditsList/CreditsItem[@role] Fully Qualified Classification Scheme Term Term Name urn:mpeg:mpeg7:cs:RoleCS:2001:ACTOR Actor urn:mpeg:mpeg7:cs:R... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.7 Media Availability | The values identified in Table 70 are profiled from Freeview Play [i.11]. Table 70: Media Availability XPath(s) .../OnDemandProgram/InstanceDescription/Genre[@href] Fully Qualified Classification Scheme Term Term Name urn:fvc:metadata:cs:MediaAvailabilityCS:2014-07:media_available Media Available urn:fvc:metadata:cs:Me... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.8 Forward EPG Availability | The values identified in Table 71 are profiled from Freeview Play [i.11]. Table 71: Forward EPG Availability XPath(s) .../OnDemandProgram/InstanceDescription/Genre[@href] Fully Qualified Classification Scheme Term Term Name urn:fvc:metadata:cs:FEPGAvailabilityCS:2014-10:fepg_available Forwards EPG OnDemand Available ur... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.11.9 Relationship | The values identified in Table 72 are profiled from TV-Anytime, ETSI TS 102 822-3-1 [7]. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 133 Table 72: Relationship XPath(s) .../BasicDescription/RelatedMaterial/HowRelated[@href] .../Service/RelatedMaterial[@href] Fully Qualified Classification Scheme Term Term Name urn:tva:metada... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 6.12 Metadata Precedence | The DVB-I client will receive multiple sources of metadata, each with a particular scope and granularity. Among the sources of DVB-I metadata, programme content guide metadata (see clause 6) should take precedence over Service List metadata (see clause 5.5) when there is overlap, due to its higher granularity and typic... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7 Security | 7.1 Introduction This clause covers security including risks and mitigations and the use of TLS as a security mechanisms. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2 Risks and mitigations (informative) | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1 Ensuring users get the expected (correct) service | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1.1 One service list provider impersonating another | If the DVB-I client permits the user to choose a service list based on information from the service list provider (e.g. ServiceList.Name and/or ServiceList.ProviderName) then a service list provider may mis-represent their service list such that users choose that service list and not the intended one. Extreme examples ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1.2 One service impersonating another - social engineering | Users will choose services based on information from a service list (e.g. Service.ServiceName and/or Service.ProviderName). A service provider may mis-represent their services in a service list so that users choose that service and not the intended one. Extreme examples of this may be addressed as trademark infringemen... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1.3 One service impersonating another - hybrid | A service provider may mis-represent a DASH service such that a false positive match is created with an existing broadcast service and indicates the DASH service instance has higher priority (i.e. lower value). This would result in users not getting the expected service. Mitigation: Organizations compiling service list... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1.4 Compromising service list registry servers or service list servers | An attacker who was able to compromise the server hosting a service list registry or one or more service lists would be able to replace the service lists or contents of them. Mitigation: Service list registry operators need to follow best practice security for the web. The same applies for organizations hosting service... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.1.5 Man in the middle attack on service list provider - broadcast | Where DVB-I service lists are announced in the broadcast channel (see clause 5.1.3.3 of the present document), there is a risk of a man in the middle attack on the broadcast replacing the signalled URI. Mitigation: None. NOTE 1: The techniques defined in clause 9 of ETSI TS 102 809 [5] can be used to protect elementary... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.2 Ensuring content is only available to users allowed to consume it | There are many different reasons why some users may not be allowed to consume particular content. Some examples include the following: • The content needs to be paid for and an individual user has not done so. • A particular device may not meet security requirements for the consumption of particular content. • The serv... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.3 Leakage of content | Some content providers will impose requirements on service providers to ensure that some content is protected from leaking beyond the users who are permitted to consume it and the device(s) on which those users are permitted to consume that content. For example, ensuring that a user does not use tools like wireshark to... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.2.4 Protecting user identification information | There will be some services where users need to identify themselves and/or pay for. This is outside the scope of the present document. Some examples of how this could be done include the following: • A linked application may offer the user a UI for payment in the same way as is done in the web today. • The user may mak... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 7.3 Use of HTTP over TLS | All HTTP transactions and connections between the DVB-I client and DVB-I metadata endpoints, specifically Service List Registries, Service List Servers, Content Guide Servers, described in the present document shall be performed using HTTP over TLS as defined in IETF RFC 2818 [24], using root certificates, cipher suite... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8 Interoperability Points | 8.1 Introduction Consumers, accustomed to the user experience offered today when watching TV services delivered over broadcast networks, will legitimately expect an equivalent or better user experience when accessing services on a DVB-I receiver. This clause describes the minimum set of functionalities required for del... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.2 Interoperability Point - IP0 | The minimum feature receiver allows service providers and receivers to deliver and access free-to-view DVB-I services that consist of video, audio, and subtitles without personalization. For this interoperability point no distinction is made between mobile/nomadic and hybrid device. The required features of the DVB-I c... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.3 Interoperability Point - IP1 | For mobile/nomadic IP-only receivers, i.e. DVB-I receivers only equipped with a network interface for lean-forward consumption of broadband services (e.g. smartphone, tablet, personal computer, etc.), the expected user experience includes: • Find the URLs of relevant DVB-I service lists by querying a Service list Regis... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.4 Service Features | 8.4.1 Introduction In each table in this clause, the value "Y" in columns labelled "minimum", "hybrid", "IP-only lean-back" or "IP-only mobile" indicates that support of that requirement is mandatory to realize the expected functionality of the profile, i.e. receivers are required to understand and act on that item whe... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.4.2 Service Delivery | Receivers shall support all mandatory features of the urn:dvb:dash:profile:dvb-dash:2014 and urn:dvb:dash:profile:dvb-dash:2017 profiles of DVB-DASH as defined in ETSI TS 103 285 [1]. Additionally, receivers shall support optional features from that specification as defined in table 78. Table 78: Additional minimum req... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.4.3 Service Discovery | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.4.3.1 Service list discovery during installation phase | Table 79 indicates the minimum requirements for DVB-I service list discovery, during the receiver installation (or reinstallation) phase. Table 79: Supported mechanisms for DVB-I service list discovery Mechanism IP0 IP1 Minimum Hybrid receiver IP-only lean-back IP-only mobile URL of DVB-I service list(s) retrieved by m... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.4.3.2 Support of service discovery metadata | The following tables indicate for each DVB-I service discovery function defined in clause 5, its status in terms of required support by service providers and receivers. Table 80: Support of Service List Entry Point fields Element/attribute IP0 IP1 Minimum Hybrid receiver IP-only lean-back IP-only mobile ServiceListEntr... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 1 Scope | The present document extends ETSI TS 102 796 [1] to enable the replacement of advertisements in the broadcast with ones targeted at the consumer including defining how adverts are to be preloaded, defining an API for switching from broadcast to an advert and vice-versa and defining how reporting of advert playback can ... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 2 References | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 3 Definition of terms, symbols and abbreviations | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 796 [1] and the following apply: browser task: task as defined in HTML5 [3] DAS application: HbbTV® application performing broadcast advert substitution as defined in the present document landing period: reserved time within the broadcast filled w... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 3.2 Symbols | Void. |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 796 [1] and the following apply: DAS Dynamic Ad Substitution GDPR General Data Protection Regulation MSE Media Source Extensions |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4 Overview | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.1 Architectures for generating DAS signalling | An HbbTV® application performs Dynamic Ad Substitution ("DAS") in response to in-band or out-of-band signalling describing advert placement opportunities. Figure 1 illustrates the information flows required from broadcaster to HbbTV® application if the application is to correctly identify an advert placement opportunit... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2 Timing concepts and definitions | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.1 Timelines and units | A PTS timestamp carried in a broadcast transport stream refers to the presentation time of a particular access unit of media (typically a frame of the video). In the present document, the presentation time refers to the time at which that access unit starts to be presented. ISO/IEC 13818-1 [7] clause U.3.6 specifies th... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.2 Advance timing of API calls by the application | If the terminal requires that an API call is made by the application at least N seconds in advance of a timestamp T then it needs to take place at or before timestamp S where: = − In the present document, a single spin of the JavaScript event loop is considered to take place at timestamp S if any changes it makes ... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.3 Broadcast to broadband switch: accuracy | When an application requests a switch from broadcast media to broadband media, the switch is scheduled at a media time T1 ("the scheduled switch time") which is the value provided by the application, rounded up to align to a broadcast video frame boundary. A terminal that is capable of switching from broadcast to broad... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.4 Broadcast to broadband switch: duration | The switch period for the switch from broadcast to broadband is the time period between the beginning of the switch (as defined in clause 4.2.3) and the beginning of presentation of the broadband video or audio, as observed by the end-user. NOTE: The observed beginning of the switch is when either broadcast video or br... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.5 Broadband to broadcast switch: accuracy | Broadband media can comprise any combination of video, audio or subtitle (caption) components. When an application requests a switch from broadband media back to broadcast media, the switch is scheduled at a media time T2 (the "scheduled switch time") as follows: • If the application does not explicitly provide a switc... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.6 Broadband to broadcast switch: duration | The switch period for the switch from broadband to broadcast is the time period between when the switch begins (as defined in clause 4.2.5) and the beginning of presentation of the broadcast video or audio, as observed by the end-user. ETSI ETSI TS 103 736-1 V1.1.1 (2020-06) 18 A random access point for broadcast video... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 4.2.7 Drift | When PCR and PTS and the playback rate of broadcast audio and video are running within a tolerance of ±30 ppm (as specified by ISO/IEC 13818-1 [7]) then a terminal with a maximum drift rate δ ppm plays broadband audio and video such that, on average, every second of broadband content playback varies in duration compare... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 5 User experience (informative) | 5.1 Introduction This clause describes the behaviour of the terminal as seen by the end-user. It should be considered as usability guidelines for implementing Dynamic Ad Substitution. The described behaviour results from a combination of: • the timing and content of the broadcast content; • the functionality coded into... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 5.3 Visibility and z-axis ordering of DOM elements | This clause describes the user experience in the simplest scenario where a single substitution takes place. The substitution content consists of a sequence of one or more adverts assembled as a single stream. Other scenarios are supported, including ones where multiple separate substitutions occur consecutively with no... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 6 Service and application model | 6.1 Introduction For regular HbbTV® applications, the service and application model shall be identical to that specified in ETSI TS 102 796 [1] except as specified here. For operator applications, the service and application model shall be identical to that specified in ETSI TS 103 606 [i.3]. 6.2 Access to broadcast re... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7 Formats and protocols | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7.1 General | Except as stated below, the present document does not introduce any additional requirements beyond those in ETSI TS 102 796 [1]. |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7.2 Broadcast specific formats and protocols | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7.2.1 Signalling of applications | In the transport protocol descriptor (see clause 7.2.3.1 of ETSI TS 102 796 [1] and clause 5.3.6.2 of ETSI TS 102 809 [8]), the contents of the URL_base field (i.e. the initial page of the application) shall be traceable back to the broadcaster of the service. ETSI ETSI TS 103 736-1 V1.1.1 (2020-06) 22 |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7.3 Broadband-specific format and protocols | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 7.3.1 Subtitles | MSE [4] only requires support for SourceBuffers for video and audio. There is no requirement for SourceBuffers for subtitle data to be supported. Display of subtitles with video and audio presented using MSE needs to be done either by JavaScript code in the application (e.g. using WebVTTCue (see clause A.3.4) as used b... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8 Browser application environment | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1 Fast Media Switch API | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.1 Introduction (informative) | The Fast Media Switch API enables an application to define ahead of time when a switch is to be made from media presented by one object or element to media presented by another object or element. The application can define the time at which the switch is to be made with reference to a timeline associated with either th... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.2 Object | The terminal shall support a non-visual embedded object of type "application/hbbtvMediaSwitcher" and class MediaSwitcher with the JavaScript API defined below. ETSI ETSI TS 103 736-1 V1.1.1 (2020-06) 23 |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.3 Method signatures | Promise switchMediaPresentation( Element originalMediaObject, String timelineSelector, Boolean timelineSource, Number switchTime, Element newMediaObject, String minimumSwitchPerformanceRequired) Description Requests a switch from the media being presented by originalMediaObject to the media to be presented by newMediaO... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.4 Algorithms | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.4.1 When switchMediaPresentation is called | When this method is called, the terminal shall run the following steps: 1) Let promise be a new promise. 2) If any of the following preconditions are not met at the time of the call to the method then return a promise rejected with a NotSupportedError: - originalMediaObject is either a video/broadcast object or an HTML... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.4.2 Between a call to switchMediaPresentation and the start of a switch | If timelineSelector specifies a TEMI timeline that is not already being monitored then, if the current timeline time is not known to the terminal within 2,5 seconds of starting to monitor the timeline in the switchMediaPresentation() call, then the requested switch shall be aborted and promise shall be rejected with a ... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.4.3 Executing the switch | The executing the switch algorithm shall be followed on the first occasion that one of these conditions occurs for each call to the switchMediaPresentation method that has not failed with the promise being rejected or resolved: • If timelineSelector is null, when the terminal detects the end of the media item in origin... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 8.1.4.4 Allocate suitable video and audio decoders for newMediaObject | The terminal shall use the following algorithm for attempting to allocate suitable video and audio decoders for newMediaObject: 1) If newMediaObject already has a suitable video and a suitable audio decoder allocated then stop. 2) If the terminal has suitable video and audio decoders that are available to HbbTV® but ar... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9 System integration | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1 MSE | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1.1 Resource management | Except as follows, the requirements of clause 9.6 of ETSI TS 102 796 [1] shall apply to HTML5 media elements whose source is MSE as well as those whose source is defined in that document. Multiple HTML5 media elements The following requirement in clause 9.6.2 of ETSI TS 102 796 [1] does not apply to HTML5 media element... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1.2 System, video and audio formats | Terminals shall support playing via MSE all video and audio codecs listed in <video_profile> elements in their XML capabilities (see clause 10.2.4 of ETSI TS 102 796 [1]) except that, as there is no requirement to support more than one audio SourceBuffer, there is no requirement to support the MRMP mode of NGA audio wi... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1.3 Media Synchronization | Clause 9.7.1.2 of ETSI TS 102 796 [1] shall apply to HTML5 media elements whose source is MSE as well as those whose source is a URL. Specifically: • If the media element is potentially playing and the readyState transitions from HAVE_FUTURE_DATA or more to HAVE_CURRENT_DATA or less (i.e. the application does not appen... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1.4 Visibility and audibility | When content that has been delivered through MSE is played from the beginning to the end, the first and last frame of video shall be visible and the audio corresponding to the period from the start of the first video frame to the end of the last video frame shall be audible. |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.1.5 Out of band subtitles | Clause A.2.12.2 ("Out-of-band text tracks") of ETSI TS 102 796 [1] shall be supported for HTML5 video elements whose source is MSE. |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.2 Reliability and resilience | Terminals shall remain fully functional in the following circumstances. Fully functional in this case means at least that video, audio and subtitles are presented, the HbbTV® application runs as specified including advert substitution and stream event reception: • An application substitutes broadcast video and audio 20... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3 Limitations and restrictions | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3.1 User-initiated background activities | Simultaneously with presenting broadcast television, terminals may enable the user to initiate background activities that, in turn, may reduce switching accuracy and/or increase switching duration while they are happening. Some possible examples of this include the following: • Local PVR recording or time-shift • Relay... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3.2 Application-initiated activities | Activities initiated by an HbbTV® application may reduce switching accuracy and/or increase switching duration while they are happening. Some possible examples of this include the following: • Multi-stream synchronization (as defined in clause 13.3.2 of ETSI TS 102 796 [1]) • File download (as defined in annex H of ETS... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3.3 System-initiated background activities | Simultaneously with presenting broadcast television, terminals may perform background activities that are not initiated by the user that may reduce switching accuracy and/or increase duration while they are happening. Some possible examples of this include the following: • Downloading a software update prior to install... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3.4 Non-predictable background activities | Television receivers are complex systems with many activities and processes happening in parallel. Some will not be interruptible. The design of the Fast Media Switch API is intended to minimize the impact of this but eliminating it is impossible. There will always be some risk of non-predictable activities delaying on... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 9.3.5 Testing considerations | Testing of any performance requirements for switching accuracy and duration shall be done in the absence of both user- initiated background activities (as defined in clause 9.3.1 of the present document) and application-initiated activities (as defined in clause 9.3.2 of the present document) and, as far as can be know... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10 Capabilities | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.1 MSE | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.1.1 Basic requirements | Terminals shall support pause and resume of content delivered through MSE. Terminals shall support random access into content delivered through MSE. NOTE: The present document inherits the requirement from clause 1.2 of MSE [4] that "Implementations MUST support at least 1 MediaSource object with the following configur... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.