hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.3 CRID issuing Authority and resolution providers | The originator of a CRID is the party that actually creates the CRID and assigns it to reference an item of content: the Authority. The resolution provider is the party that provides the facility to resolve the CRID into a physical location in space and time. Three main actors can originate and resolve content referenc... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.3.1 Third party extension to static reference model | Figure 6 shows possible actors in the issuing and resolving of CRIDs. Two of those actors are already in the broadcast reference model shown in figure 1, i.e the content creator and the content service provider. Third party operation is not explicitly modelled in figure 1. However, the model can be easily extended to c... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4 CRID issuing and resolving scenarios | In the most straightforward scenario, the originator of a CRID is also the resolution authority for that CRID. However, this relationship does not always hold. There are a number of scenarios where the CRID originator does not resolve the CRID itself. Table 2 depicts all possible CRID originators to CRID resolution aut... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4.1 CRID originated by content creator, resolved by content creator | In this simple scenario, the content creator creates the content and creates a CRID to reference that piece of content. The content creator also provides the resolving information to find that particular piece of content. In the broadcast case, suppose the content creator is not the broadcaster, and the content in ques... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4.3 CRID originated by content creator, resolved by third party | In this scenario, the content creator creates the content and associated CRID. A third party resolves the CRID. Supposing the content creator is a documentary production company, and the content in question is a documentary entitled "Incredible Documentary". Several broadcasters will carry this documentary over a perio... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4.5 CRID originated by content service provider, resolved by third party | In this scenario, the content service provider creates a CRID associated to content, but a third party is delegated to resolve the CRID. The content service provider could be a broadcaster. Suppose the content in question is the movie "Best Comedy Movie Ever". The motion picture studio, the content creator of the movie... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4.6 CRID originated by third party, resolved by content service provider | In this scenario, a third party service creates e.g. a group CRID that references other CRIDs that in turn reference actual content. The third party could be an aggregator of some description. The content service provider agrees to be the resolution service provider for this third party because the third party service ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.4.7 CRID originated by third party, CRID resolved by third party | In this scenario, a third party service creates e.g. a group CRID and references other CRIDs that in turn reference actual content. The third party is an aggregator of some description. The same or another third party is also the resolution service provider. Suppose the third party provides a CRID referencing all natur... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.5 Example of coding an ISAN using a CRID | The ISO and SMPTE/ATSC have been actively working on the creation of an International Standard Audiovisual Number (ISAN). The goal of the ISAN is to uniquely identify completed audio-visual works, episodes of a work, versions of a work, and related parts of versions of a work (such as audio and subtitling tracks). In c... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.6 The relation between CRID and instance metadata | Instance description metadata is used to describe meaningful differences between specific instances of the same content i.e. instances of content that share the same CRID. For example, two instances of the same film where the instance description metadata indicates that one is in the original 16:9 aspect ratio and the ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.7 CRID lifecycle | An authority who creates CRIDs and assigns them to pieces of content has the choice of keeping this assignment permanent, or making it temporary and re-assigning CRIDs to completely different pieces of content at a later date. Assigning a CRID to a piece of content in a permanent manner has the advantage of allowing a ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.8 Harmonization of TS 102 822-4 and TS 102 822-6 | TS 102 822-4 [6] specifies the requirements for unidirectional and bi-directional resolution of content references. It also provides an HTTP binding for bi-directional resolution over IP based networks. TS 102 822-6-1 [9] and TS 102 822-6-2 [10] meets all the requirements of TS 102 822-4 [6], and also provides a rich s... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6 Metadata | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.1 Introduction | Metadata is generally defined as "data about data". Within the TV-Anytime environment, the most visible parts of metadata are the attractors/descriptors or hyperlinks used in Electronic Programme Guides (EPGs), or in Web pages. This is the information that the consumer or agent will use to decide whether or not to acqu... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.2 XML - a common representation format | For the purpose of interoperability, the TV-Anytime Forum has adopted XML as the common representation format for documentation of metadata. XML offers many advantages: it allows for extensibility, supports the separation of data from the application, and is widely used. In addition, powerful XML tools are now availabl... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3 The TV-Anytime metadata high level documents | All TV-Anytime metadata instance documents are grouped under a root element called "TVAMain". |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.1 Metadata structure | There are six basic kinds of metadata that a "TVAMain" element groups: • Content description metadata. • Instance description metadata. • Consumer metadata. • Segmentation metadata. • Metadata origination information metadata. • Interstitial and targeting metadata. The diagram in figure 7 illustrates this relationship.... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.2 Phase 1 Metadata | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.2.1 Content description metadata | Content description metadata is divided into four areas: - Descriptions of items of content e.g. television programmes. These descriptions are held in the ProgramInformationTable. They include things like the title of the programme, a synopsis, the genres it falls under and a list of keywords that can be used to match ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.2.2 Instance description metadata | Instance description metadata is divided into two areas: - Descriptions of particular instances (locations) of content. These descriptions are held in the ProgramLocationTable. This metadata contains the scheduled time, but note that using this representation is not the preferred means of determining locations. The pre... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.2.3 Consumer metadata | Consumer metadata is divided into a number of areas: - Details of a user's preferences or profile. This information is delivered by the UserPreferences description scheme, which provides rich representations of the particular types of content preferred or requested by the user. These descriptions are closely correlated... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.3 Phase 2 metadata | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.3.1 Schema overview | The Phase 2 TV-Anytime metadata schema is a backwards-compatible extension of the Phase 1 schema. It extends Phase 1 datatypes for content description and user description and makes use of datatypes imported from MPEG-21 to enable new areas of functionality. It also extends the TV-Anytime root document type, TVAMainTyp... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.3.3.2 Phase 2 as an extension to Phase 1 metadata tools | It is important to note that the Phase 2 extensions to the Phase 1 metadata tools are, like their predecessor, modular. They constitute additions to the TV-Anytime metadata toolbox. There is no need, therefore, for Phase 1 implementations to evolve in one leap to comprehensive Phase 2 compliance. A precedent for this e... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.4 Documents related through the CRID | Parts of a TV-Anytime document are related through the CRID. Metadata may be distributed across many TV-Anytime documents, but it is always possible to relate appropriate pieces through CRIDs. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.4.1 Grouping | Programmes can belong to groups, and groups can belong to other groups. Linking programme descriptions with group descriptions using CRIDs reflects this relationship in the metadata, again, which is illustrated in figure 8. Figure 8: Programme descriptions related to group descriptions through the CRID ProgramInformati... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.5 TV-Anytime document structure | The following example illustrates the structure of a valid TV-Anytime document: <TVAMain xmlns="urn:tva:metadata:2007" xmlns:mpeg7="urn:tva:mpeg7:schema:2005" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:tva:metadata:2007 schemas/tva_metadata_3-1_v141.xsd" version="03" xml:lang="en" pub... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.6 Mandatory and optional elements | The TV-Anytime XML Schema contains many elements that are optional and some that are mandatory. The diagram shows the mandatory parts of ProgramInformation: <ProgramInformationTable> <ProgramInformation programId="crid://hbc.com/foxes/episode1"> <BasicDescription> <Title type="main"> The one where Fox jumps in the Poto... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.7 Delivery of metadata over a unidirectional environment | The TV-Anytime forum has specified a generic solution for the carriage of metadata over unidirectional environments. Unidirectional environments are defined as being environments where content and metadata are delivered from the transmitting device (head-end) to the terminal device (PDR) over a one-way link and where n... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.8 Notes on Schema Extension | The TV-Anytime Schema defined in TS 102 822-3-1 [2], provides a standard way of describing common data structures required within a PDR environment. However there may be instances where third parties may wish to extend the TVA Schema to provide enhancements to existing data types, or to introduce completely new data ty... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.8.1 Polymorphism of existing type by inheritance with extension | To extend an existing TVA data type one uses the XML Schema, derive by extension mechanism. So for example if a provider wish to add a new element called MyData to a standard TVA ProgramInformationType, he would define a new type as follows: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tva="urn:tva:meta... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 6.8.2 Polymorphism of existing type by inheritance with restriction | To restrict an existing TVA data type one uses the XML Schema, derive by restriction mechanism. So for example if a provider wishes to create a new data type called MyDataType which removes all optional elements from the standard TVA ProgramInformationType, he would define a new type as follows: <xs:schema xmlns:xs="ht... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7 Phase 1 cookbook examples and scenarios | This clause describes the phases identified in a TV-Anytime System. It is followed by examples to give an overview of how a system might work. Further details and issues that arise from this example are identified in the next clause. The examples will cover usage of both content referencing and metadata (including the ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.1 TV-Anytime dynamic processes | Processes in a TV-Anytime session are depicted in figure 10. Publish Select Acquire Search View Finish Locate Figure 10: Processes in a TV-Anytime system The next clauses present an examples that show, per process, the steps that are to be taken in a TV-Anytime system. 7.2 Phase 1 example: Record every episode of this ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.7 Phase 1 example: Personal Channel Service at my PDR | A viewer wants to set his/her week's watching schedule, after electronic guide information from many service providers has been stored at PDR. However he/she does not want to navigate all the programme information at programme guide application for setting watching schedule. Also, the viewer wants PDR to generate the v... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.11 Phase 1 example: Related material recording | The RelatedMaterialType DS can be used to link, for example, a promotional trailer to the content that it promotes. For example, a PDR may be viewing a piece of content and find a Related MaterialType DS in a data stream associated with the content. The encoding of the RelatedMaterialType into this data stream and the ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.13 Phase 1 example: RMPI descriptive metadata | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.13.1 Introduction | This clause contains three examples of RMPI descriptive metadata for free-to-air (FTA), Pay-Per-View (PPV) and Video-On-Demand (VoD) content. These examples show only metadata expressing RMPI-MB (i.e. prior to domain acquisition). In order to obtain the corresponding RMPI-M (i.e. post domain acquisition), the RMPI type... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.13.2 Free-to-air content | The following example shows a possible combination of rights granted to a given piece of content broadcast free-to-air: • Content is not scrambled and will remain unscrambled after domain acquisition. • No possibility is granted to acquire new rights. • In the receiving domain, Play, Analogue Export, Digital Export (bo... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.13.3 Pay-per-view content | The following example shows a possible combination of rights granted to a given piece of content broadcast e.g. by a Pay-TV operator, where: • Content has to be re-scrambled using AES when acquired in the domain. • Possibility to acquire new rights is granted. The Pay-TV operator will grant these rights. • In the recei... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 7.13.4 Video-On-Demand Content | The following example shows a possible combination of rights granted to a given piece of content provided by a content provider using DRM technology, where: • Content is scrambled using Camellia and needs not to be re-scrambled when acquired in the domain. • Possibility to acquire new rights is granted. An URL is given... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8 RMPI cookbook examples and scenarios | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.1 Introduction | The following illustrates how the TVA-RMPI specification (TS 102 822-5-1 [7]) may be used as a standalone specification or may be integrated with other technologies to enable key business scenarios. These examples are not exhaustive and do not cover all combinations of RMPI field settings. It is anticipated that there ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.2 RMP system dependencies | "RMP systems" are defined as those systems which recognize and enforce RMPI grants. It is understood that for RMPI to be effectively used within RMP systems that compliance bodies must establish specific rules for associated functions and components. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.3 RMP concepts | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.3.1 Copy control versus playback control | RMPI regulates the use of governed content, but does not regulate its movement. In a digital era, the movement of content files is difficult to constrain. However, the use of such files can be managed using trusted systems, including cryptographic techniques and DRM technologies. By managing the use of protected conten... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.3.2 Targeting content consumption and usage with RMPI | Usage control is expressed in terms of RMP domains. An RMP domain is defined as a set of TVA-RMP compliant devices that are securely bound to each other for the purpose of exchanging protected content. It is left to the compliance bodies that adopt TVA-RMP specifications to refine this definition in terms of their spec... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.3.3 "Export Rights" as distinct from "Play Right" | The "Play Right" is limited to rendering on a TVA-RMP compliant device only. Rendering on non-RMP compliant devices (e.g. a legacy display) requires the transfer of content usage from the TVA-RMP device to the non-RMP device and this right is not included in the semantic of "Play Right". The transfer of content usage f... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.3.4 RMP / non-RMP interoperability | The purpose of granting the export right is to permit interoperability with non-RMP compliant systems. If the export right is not granted, then the release of content from an RMP compliant system is prohibited. For example, a "Play Right" granted without any export right would permit rendering of content only by an RMP... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.4 Lifecycle of RMPI | RMPI can exist in two successive phases; RMPI-MB and RMPI-M. RMPI-MB is transmitted in conjunction with the broadcast signal. At the time of reception in the end user's TVA-RMP Domain it is converted to RMPI-M. Rights that are granted to the Receiving Domain and Single Point of Control (if present) in RMPI-MB are carri... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.5 Compliance | Implementations of TV-Anytime RMP specifications are anticipated to take place under compliance regimes that will enforce the implementation of a given scenario to meet the needs of a respective product space, market segment or other defined environment. Compliance bodies may also manage certification and revocation in... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6 Scenarios | 8.6.1 Scenario 1: Free-To-Air broadcast with no redistribution/viewing control Intent Free-To-Air content is broadcast over the air with no usage constraints. ETSI ETSI TS 102 822-2 V1.4.1 (2007-11) 76 The Free-To-Air content with the grant below is allowed to migrate without further redress from the broadcaster and ca... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.6 Scenario 6: Free-To-Air live streaming | Intent Public service content is streamed in the clear over the Internet for immediate viewing only. This is currently the situation for some public service radio services. ETSI ETSI TS 102 822-2 V1.4.1 (2007-11) 83 Table 9: Grants carried in RMPI-MB for scenario 6 Function Semantic Value Grant to: "Receiving Domain" -... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.7 Scenario 7: Scrambled Free-To-Air | Intent Scrambled Free-To-Air content is broadcast carrying RMPI-MB. If the user has registered, the receiver hands over content to the user's private domain. Content is descrambled in the receiver. This model is similar to the Japanese Free-To-Air broadcast where content is scrambled for transmission. Table 10: Grants ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.9 Scenario 9: Push Content | Intent Content is pushed to the Receiving Domain without any rendering rights ("Play", "Analogue Export", "HD Digital Export", "SD Digital Export") in a speculative manner by the service provider. "Extend Rights" is granted so that the user can acquire those rendering rights on an individual basis. When the user wishes... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.10 Scenario 10: Pay-Per-View Content, "buy to keep" | Intent Content is delivered under control of a CA system as part of a pay-per-view service. The user purchases the right to keep the content without time restriction for consumption within his private domain. Control of the content is handed over from the CA system to the TVA-RMP system by the pay television receiver. ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.11 Scenario 11: Import of copy protected analogue content | Intent An analogue program is fed to a TVA-RMP compliant PDR with associated copy-control signals (e.g. CGMS-A). The associated copy control rule indicates "copy-once". The TVA-RMP compliant device generates RMPI-M from the incoming copy control information as per the compliance rules defined by the compliance body. Ta... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 8.6.12 Scenario 12: Video on Demand | Intent Content is purchased by the user from a Video On Demand service. Content is protected by a proprietary DRM system between the VOD server and the TVA-RMP compliant PDR. Control of the content is then handed over to the TVA-RMP system to address TVA-RMP enabled displays. The VOD business model dictates that no rec... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9 Issues per process | This clause gives some explicit implementation hints for less obvious issues in the different TV-Anytime processes, i.e. publish, search, select/locate, acquire, view and finish. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1 General system issues | To get an actual TV-Anytime system into the processes described in the previous clauses some generic system issues need to be solved. These issues are out of the scope of TV-Anytime, but some of them are presented here to ease the implementer's life. Most issues are related to actual PDR implementations. The issues fit... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1.1 Set-up and service discovery | In the set-up process of a PDR, e.g. when the user first installs a box in his home, a number of things need to be done to allow for it to find the TV-Anytime metadata and location resolution services. The way that this works is transport dependent and no complete descriptions for all transports are given, the analogue... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1.2 Language Identification | The xml:lang is extensively used for the identification of languages. It is important to note that the identification capabilities of the "language" datatype are now based on RFC 3066 [21], which enables the identification of a wider range of languages than the earlier RFC 1766. ISO's 3 character language codes may now... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1.3 Transport and delivery of TV-Anytime data | The transport and delivery of TVA data requires the definition and specification of a set of technical features currently not covered by the TV-Anytime specification. These features can be summarized as follows: • Identification and signalling: an identification mechanism (e.g. a metadata location descriptor correspond... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1.4 Updating resolution tables | Both the RAR tables and the Resolution tables need to be kept up to date. The RARs contain information about the various resolution services available to the PDR device. The Resolution tables contain the mappings of CRIDs to other CRIDs or to locators. In the broadcast scenario, these tables must be pushed to the box, ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.1.5 Updating metadata | There is no mechanism defined that allow for update of part or all of the metadata. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.2 "Publish" process | Re-run/repeat of content A re-run is defined as content that is broadcast at different times to suit user convenience, sometime subsequent to its original broadcast. A repeat is generally regarded as old content. The content service provider may package content being re-shown within a short period of the original broad... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.3 "Search and select" processes | Selection on basis of time/channel "What's on at 8 o'clock tonight?" The scenario depends on a few implementation issues (bullets 1 and 2) and/or how service providers will provide required metadata (bullets 3 and 4): 1) With a location resolution service that, when given a CRID, only provides locators, the box would h... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.4 "Locate" process | "Make locator names unambiguous" For example two satellites feed one box. In this scenario how does the system distinguish between say channel 5 from each satellite? Or, phrased differently, what happens when the same service is on both physical inputs? 1) Box implementation issue. If the content on both feeds has the ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 9.5 "Acquire" process | Acquisition of metadata with content and/or separate from content Some metadata may be related to the actual timeline of the content, e.g. metadata that needs to show up at a certain point in the programme. Currently there is no way of synchronizing (Meta) data with content in the TV-Anytime context. Validation of cont... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10 Phase 2 cookbook examples and scenarios | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.1 Phase 2 example: New content types | Several content types are covered as part of the examples given in the following clauses. ETSI ETSI TS 102 822-2 V1.4.1 (2007-11) 99 |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.2 Phase 2 example: Packaging | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.2.1 Program with an associated package | The instance document describes a sports program with an associated package which includes an interactive application. The package table provides information (in the example: middleware and audio) that can be used to determine which components of the package need to be captured. <?xml version="1.0" encoding="UTF-8"?> <... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.2.2 Phase 2 example: Educational package | This example describes an educational package, consisting of an animation and an application to facilitate the study of the English language. The application can be run under the Linux OS with at least 16 MB of RAM. <?xml version="1.0" encoding="UTF-8"?> <TVAMain xmlns="urn:tva:metadata:2007" xmlns:tva2="urn:tva:metada... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.2.3 Data broadcasting | The following XML snippets illustrate a data broadcasting service for drama program called "Damo". The data broadcasting service and the "Damo" AV program are broadcast at the same time. The title of the data broadcasting service is "Damo Plus," and it consists of two applications. One is the "Damo Story," and it provi... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.3 Phase 2 example: Targeting | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.3.1 User environment description | The XML snippet below describes that the consumer is using a PDA as a TV-Anytime client terminal and the video format that the PDA can decode is "AVI." In addition to the terminal related information, the snippet also provides information on the current weather conditions. Based on this environment, either the PDA can ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.3.2 Personalized service | In a personalized service a service provider makes use, with the consent of the consumer, of consumer profile data (user description, user environment and personal profile) in secure environment. HK PDR UK CP upload_Person al_Data clear_Personal _Data get_Data UK Mobile Disc overy servic e Mic hael Preference History P... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.4 Phase 2 example: Interstitials | This example shows how the framework can be used to signal that a particular Spot within a Pod should be substituted with another content item when playing back recorded content. <?xml version="1.0" encoding="UTF-8"?> <TVAMain xmlns="urn:tva:metadata:2007" xmlns:tva2="urn:tva:metadata:extended:2007" xmlns:int="urn:tva:... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.5 Phase 2 example: Sharing - metadata exchange | The scenarios below cover the specifications that explicitly add support for the exchange of metadata. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.5.1 Transfer profile to another device | This clause addresses the following scenario: "Using his rented 3G mobile phone, Michael gets access to a UK content provider's menu of contents. He knows that the provider has Manchester United matches on the menu. He wants to watch them the way he likes, so he has his user profiles transferred from his home PDR in Ho... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.5.2 Recommend content to a friend | TS 102 822-8 [13] allows the user to transfer metadata between devices, with an appropriate instruction. The specification allows the encapsulation of all forms of TV-Anytime data. One of the nice features of TS 102 822-8 [13] is the ability to recommend a piece of content to a friend. In this example the user sends th... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.5.3 Web browsing to select content and metadata acquisition | This scenario implies the following steps: • The customer uses the Web browser available in its PDR to access an EPG located on a web site. • The customer browses the EPG and selects content. A record button on the EPG page allows the customer to download the metadata associated to the selected content in order to prog... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.6.1 NDR programming for future recording | This scenario involves the following steps: • The customer uses TV Anytime technologies on his PDR to select content. • Then he discovers that the selected content instance overlaps with other content he is interested in. He decides to send a record request to the NDR Service able to record this content instance. Here ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.6.2 NDR programming for immediate recording | This scenario involves the following steps: • The customer is watching time shifted live content using his PDR. • Somebody else comes in and wants to watch the live event being broadcast soon on another channel. • The customer can then request an NDR to immediately record the content being broadcast on the current TV c... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.6.3 NDR programming for consumption by another device | The customer is in his office and discovers that tonight an interesting content will be broadcast but he knows that he will be soon on the move and so decides to record the TV Content for later viewing on its PDA. This scenario involves the following steps: • The customer uses TV Anytime technologies or EPG Web browsin... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 10.7 Phase 2 example: Coupons | The example below describes: • Content with reward coupon. • Coupon "Buy 3 movies, get one free". <?xml version="1.0" encoding="UTF-8"?> <TVAMain xmlns="urn:tva:metadata:2007" xmlns:tva2="urn:tva:metadata:extended:2007" xmlns:mpeg21="urn:tva:mpeg21:2007" xmlns:mpeg7="urn:tva:mpeg7:2005" xmlns:xsi="http://www.w3.org/200... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11 Issues per Phase 2 technology | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11.1 Sharing, content and metadata exchange | There are several issues with sharing content and metadata. There are privacy issues associated with passing personal information (TS 102 822-3-1 [2]). There are also security issues with exchanging information with others. TS 102 822-5-1 [7] describes the information on rights management for content and TS 102 822-7 [... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11.1.1 Content referencing and identification | The current specifications for content referencing describe how to reference a programme (or group of programmes) that can then be eventually resolved to instances of content. In many cases the CRID will refer to content that will be available in the future. This model particularly applies to the broadcast case where a... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11.1.2 Sharing Metadata | The specifications TS 102 822-3 (all sub-parts) [2], [3], [4] and [5] and TS 102 822-8 [13] cover the transfer of user profile information and metadata. If modifications are made to part of the metadata (e.g. creating a more comprehensive synopsis), the Phase 2 specifications include support for annotating each metadat... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11.1.3 Sharing metadata with content | The specifications do not explicitly cover the binding together of metadata and content. When content is stored or shared the device will need to store the associated metadata to allow identification later. This is needed because, for lots of broadcast content, the metadata will not be permanently available from a broa... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 11.2 Remote programming | One of the key issues with remote programming (TS 102 822-9 [14]) via e-mail is to ensure that only valid e-mails are processed. Without some form of security it would be possible for a third party to remotely control the PDR (denial of service attack). The PDR could be configured with a list of valid sources and then ... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 1 Scope | The present document lists and defines the TV-Anytime Phase 1 and Phase 2 evolutionary range of features which describe PDR (Personal Digital Recorder) usage models that the TV-Anytime standards facilitate. The features are supported and enabled by the specifications for Metadata (TS 102 822-3 sub-parts 1 [2], 2 [3], 3... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 3 Definitions and abbreviations | |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: advertiser: entity that promotes or drives sales for their products or services advertising: content that is intended to promote or drive sales for products or services application: specific set of functions running on the PDR NOTE: So... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CRID Content Reference IDentifier FTA Free To Air NDR Network Digital Recorder PDR Personal Digital Recorder PPV Pay Per View RMPI Rights Management Protection Information TLS Transport Layer Security URL Uniform Resource Locator VOD Video On ... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 4 Key Phase 1 Business Models | Table 1 KEY BUSINESS MODELS PHASE 1 BM1 001 A consumer will want to be able to capture and play back content on a PDR. BM1 002 A consumer will want to pause live incoming content on a PDR so that they can "resume" later and continue to watch the content in time shift mode. BM1 003 A consumer will want to view an on-scr... |
586bdfcefa904575f04f6e7b73641f46 | 102 822-1 | 6 Key Phase 2 Business Models | Table 3 KEY BUSINESS MODELS PHASE 2 Description BM2 001 A consumer will want to capture content onto their portable device over a wired or wireless network and transfer that content with associated metadata to their home device and other mobile devices. BM2 002 A consumer will want to make available some of their recor... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.