hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARIB Association of Radio Industries and Businesses NOTE: Japanese Standardization Body. ATSC Advanced Television Systems Committee NOTE: This committee is for the digital broadcast of multimedia and applications in North America and other reg... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 4 Use of CRID | As is the case with the TV-Anytime Phase 1 specifications, the CRID (TS 102 822-4 [6]) forms a key role within the present document. It is used to identify an individual interstitial item i.e. a content item. Still as is the case in Phase 1, a CRID shall be assigned to each unique piece of content. The present document... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 5 Identification of pods | Many of the business models supported by the data model defined below require that a "pod" has a unique identifier. The present document assumes that this identifier takes the form of an URI, but the detailed format of this URI is not defined in the present document. ETSI ETSI TS 102 822-3-4 V1.6.1 (2012-12) 10 No mech... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 6 Targeting controlled terms and rules | The present document provides a framework for the broadcaster to control the playback/replacement of interstitial content. Within current day interstitial scheduling systems extensive use of "rules" are used to automatically select where a "spot" should be placed within a "pod" relative to other content and spots. The ... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7 Metadata definitions | For the purpose of interoperability, TV-Anytime has adopted XML as the common representation format for metadata. XML offers many advantages: it allows for extensibility, supports the separation of data from the application, and is widely used. XML schema is mainly used to represent the data model. TV-Anytime descripti... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.1 Use of MPEG-7 | A metadata schema is the formal definition of the structure and type of metadata. TV-Anytime uses the MPEG-7 Description Definition Language (DDL) [17] to describe metadata structure as well as the XML encoding of metadata. DDL is based on XML schema as recommended by W3C in [15]. TV-Anytime uses several MPEG-7 datatyp... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.2 TV-Anytime metadata namespace | TV-Anytime interstitial metadata description schemes are associated with the TV-Anytime interstitial metadata XML namespace, defined as: xmlns:int="urn:tva:metadata:interstitial:2012" TV-Anytime interstitial metadata includes metadata description schemes defined by TV-Anytime as included in the XML file. xmlns:tva="urn... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.3 TargetingControlledTerms | The following defines the syntax and semantics for the TargetingControlledTerms. These TargetingControlledTerms are used within the MPEG-7 ClassificationSchemeType to provide a set of terms for use within the rule complex type. ETSI ETSI TS 102 822-3-4 V1.6.1 (2012-12) 12 <complexType name="TermConstraintsType"> <attri... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.4 Expressing rules | The ability to express rules by which interstitial content items are selected is a key part of the present document. A rule is composed of a set of Unary and Binary Predicates which can be combined together within a Predicate Bag using the AND and OR clauses. This is very much like the WHERE declaration within an SQL S... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.4.1 PredicateTypes | <complexType name="RuleMethodType"> <sequence> <choice> <element name="MethodParameter" type="anySimpleType" minOccurs="0" maxOccurs="1" /> <element name="RuleMethod" type="int:RuleMethodType" minOccurs="0" maxOccurs="1" /> </choice> </sequence> <attribute name="methodName" type="mpeg7:termReferenceType" use="required"... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.4.2 PredicateBagType | <complexType name="RuleRefType"> <attribute name="ref" type="tva:TVAIDRefType" use="required"/> </complexType> <simpleType name="PredicateBagTypeType"> <restriction base="string"> <enumeration value="AND"/> <enumeration value="OR"/> </restriction> </simpleType> <complexType name="PredicateBagType"> <sequence maxOccurs=... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.4.3 RuleType | <complexType name="OtherRuleLanguageType"> <attribute name="ruleLanguage" type="mpeg7:termReferenceType" use="required" /> <attribute name="href" type="anyURI" use="required"/> </complexType> <complexType name="RuleType"> <sequence> <choice minOccurs="0" maxOccurs="unbounded"> <element name="PredicateBag" type="int:Pre... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.5 Interstitial framework | The interstitial framework enables an operator to describe the conditions under which interstitial replacement should take place and what replacements should take place. |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.5.1 Core schema types | |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.5.1.1 ConditionType | The ConditionType is used extensively within the present document to define conditions that shall be met, before a statement is "true". For example it is used to define what rules shall be met before a particular substitution can take place. A Condition element represents a condition. As such, it denotes the parent ele... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.5.1.2 ContentRefType | <complexType name="ContentRefType"> <sequence> <element name="Condition" type="int:ConditionType" minOccurs="0" maxOccurs="unbounded"/> <element name="ContentRef" type="tva:CRIDRefType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </complexType> Name Definition ContentRefType A complex type that represents a Cont... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.6 Interstitial break and cascading | |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.6.1 Interstitial break type | <complexType name="InterstitialBreakType"> <sequence> <element name="InterstitialBreakSelectionRule" type="int:RuleType" minOccurs="0" maxOccurs="1"/> <element name="PodSubstitution" type="int:PodSubstitutionType" minOccurs="0" maxOccurs="unbounded"/> <element name="SpotSubstitution" type="int:SpotSubstitutionType" min... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.6.2 Substitution cascading | With the framework defined within the present document it is possible to cascade substitutions. For example the conditions declared may cause a "pod" substitution to occur. It is then possible via one or more SpotSubstitution(s) to change the "spots" that will form the final "pod" substitution. ETSI ETSI TS 102 822-3-4... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.7 PodSubstitution type | <complexType name="ReplacementPodType"> <sequence> <element name="Condition" type="int:ConditionType" minOccurs="0" maxOccurs="unbounded" /> <element name="Spot" type="tva:CRIDRefType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="podId" type="tva:TVAIDType"/> </complexType> <complexType name="PodS... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 7.8 SpotSubstitutionType | <complexType name="SpotSubstitutionType"> <sequence> <element name="SpotSelectionRule" type="int:RuleType" minOccurs="1"/> <element name="ReplacementSpot" type="int:ContentRefType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> Name Definition SpotSubstitutionType A complex type that describes the con... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 8 Recording cache | To enable interstitial replacement to take place the receiver shall have the appropriate content items available to enable the substitution to take place. These content items may for example be automatically pushed to the device during a quiet period in the broadcast schedule, or they may be available for OnDemand down... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 9 Root Types | The following data type forms the root of an interstitial instance document, and is used to encapsulate the set of rules used within the present document, the "recording cache" and the "interstitial substitution" controls. < complexType name="InterstitialTableType"> < sequence> < element name="InterstitialBreak" type="... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 1 Scope | The present document is part of TV-Anytime Phase 2 that proposes an evolutionary range of features which describe PDR (Personal Digital Recorder) usage models that the TV-Anytime standards facilitate. The TV-Anytime specifications enable search, select, acquire and rightful use of content on local and/or remote persona... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 822-1: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 1: Benchmark Features". [2] ETSI TS 102 822-2: "Broadcast and On-line Service... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IEEE 802.3: "Ethernet". [i.2] ITU-T Recommendation V.42: "Error-correcting procedures for DCEs using asynchronous-to- synchronous conversion". [i.3] I... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 3 Definitions and abbreviations | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: application: specific set of functions running on the PDR NOTE: Some applications use metadata, either automatically or under consumer control. attractor: metadata element that is accessible by the consumer in order to aid in the conte... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AV Audio-Visual CRID Content Reference IDentifier NOTE: As defined in TS 102 822-4 [6], it is an identifier for content that is independent of its location. CS Classification Scheme DDL Description Definition Language NOTE: The language used t... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 4 TV-Anytime metadata data model | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 4.1 TV-Anytime metadata process model | Create Metadata aggregation Metadata editing Content creation Publish Content publishing Metadata publishing Search and selection metadata Location resolution metadata Navigation metadata Select and Present Search & Selection Location Resolution Storage Metadata Content User Interaction Figure 1: Metadata and content f... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 4.2 TV-Anytime metadata structure model | Two modelling approaches are used in the following clauses. A simple data modelling methodology is shown in figure 2 that allows to describe metadata structures at a high level in a manner independent of any particular representation. This syntax allows relationships between TV-Anytime entities to be clearly stated (e.... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 4.3 CRID and metadata | The cornerstone of TV-Anytime metadata is the CRID [6]. As a content reference identifier, a CRID refers to a piece of content, though in some cases it may refer to one or more other CRIDs. The CRID also acts as the link that connects different content-related metadata descriptions. Content-related metadata is classifi... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 5 Metadata definitions | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 5.1 Introduction | For the purpose of interoperability, TV-Anytime has adopted XML [15] as the common representation format for metadata. XML offers many advantages: it allows for extensibility, supports the separation of data from the application, and is widely used. XML schema is mainly used to represent the data model. TV-Anytime desc... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 5.2 Use of MPEG-21 | In the areas of content packages and targeting the specification makes use of existing data types defined by MPEG-21. In particular types are borrowed from the Digital Item Declaration (DID) specification [18], and Digital Item Adaptation (DIA) specification [19]. |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 5.3 TV-Anytime metadata namespace | TV-Anytime metadata description schemes are associated with the TV-Anytime metadata XML namespace. The TV-Anytime Phase 2 metadata namespace is defined as: xmlns:tva2="urn:tva:metadata:extended:2012" TV-Anytime Phase 1 metadata namespace is defined as: xmlns:tva="urn:tva:metadata:2012" <import namespace="urn:tva:metada... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6 Phase 2 basic types | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1 New content yypes | Clause 6.1 contains types that may be used to describe components that are not traditional broadcast content. These content types may be standalone content items or included as part of a Package, where a Package is a collection of content grouped with a certain application scenario in the background. The new content ty... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.1 Content attributes base type | This is the abstract base type for all specific context-independent attribute types. <complexType name="ContentAttributesType" abstract="true"/> Name Definition ContentAttributesType An abstract type to indicate content attribute according to content type. |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.1.1 Audio attributes | The audio attributes may be used to describe the characteristics of an audio component or audio content item. <complexType name="AudioAttributesType"> <complexContent> <extension base="tva2:ContentAttributesType"> <sequence> <element name="Coding" type="tva:ControlledTermType" minOccurs="0"/> <element name="NumOfChanne... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.1.2 Video attributes | The video attributes may be used to describe the characteristics of a video component or video content item. <complexType name="VideoAttributesType"> <complexContent> <extension base="tva2:ContentAttributesType"> <sequence> <element name="Coding" type="tva:ControlledTermType" minOccurs="0"/> <element name="Scan" type="... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.1.3 Still image content attributes | The still image content attributes may be used to describe the characteristics of a "still image" content item. <simpleType name="OrientationType"> <restriction base="nonNegativeInteger"> <minInclusive value="0"/> <maxInclusive value="360"/> </restriction> </simpleType> <complexType name="StillImageContentAttributesTyp... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2 Context attributes base type | This context attributes type serves as the base attribute for context specific attributes. Context specific attributes differ from the previously described content specific attributes in a way that they are dependent on the environment and the circumstances content is consumed. The context may be different for example,... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2.1 Data broadcasting context | Data broadcasting context describes context attributes specific to a data broadcasting service and its applications. A data broadcasting service provides procedural and declarative contents over broadcasting TV channel. Users can play and interact with the data broadcasting content at the set-top box connected to the b... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2.2 Interstitial context | The interstitial context may be used to describe the context of an interstitial content item. <complexType name="InterstitialContextAttributesType"> <complexContent> <extension base="tva2:ContextAttributesType"> <sequence> <element name="MemberOfCampaign" type="tva:TVAIDRefsType" minOccurs="0" maxOccurs="unbounded"/> <... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2.3 Educational context | Content that is used in an educational context has special description requirements that are met by the EducationalContextAttributesType. <complexType name="EducationalContextAttributesType"> <complexContent> <extension base="tva2:ContextAttributesType"> <sequence> <element name="IntendedUser" type="tva:ControlledTermT... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2.4 Application context | This following defines syntax and semantics to describe the feature of the application program which is a set of functions to be run on the PDR. <complexType name="ApplicationContextAttributesType"> <complexContent> <extension base="tva2:ContextAttributesType"> <sequence> <element name="Freeware" type="boolean" default... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.2.5 Game context attributes | The following defines syntax and semantics to describe the features of game content. <complexType name="GameContextAttributesType"> <complexContent> <extension base="tva2:ContextAttributesType"> <sequence> <element name="Perspectives" type="tva:ControlledTermType" minOccurs="0" maxOccurs="unbounded"/> <element name="Ma... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.1.3 Content properties datatype | The ContentPropertiesType serves as the base element for content properties. Content properties can consist of file specific properties (described below), content attributes and context attributes. ETSI ETSI TS 102 822-3-3 V1.6.1 (2012-12) 23 <complexType name="ChecksumType"> <simpleContent> <extension base="hexBinary"... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2 Targeting information | The present clause defines descriptions applicable to a typical consumer's environment including terminal characteristics, network characteristics and natural environment. Various targeting scenarios can be enabled by matching the provided usage environment and the targeting conditions of the content. TV-Anytime's usag... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.1 Biographic information | The following describes descriptive properties of consumer's biographic information. <complexType name="AgeRangeType"> <attribute name="min" type="byte" use="optional"/> <attribute name="max" type="byte" use="optional"/> </complexType> <complexType name="LanguageType"> <simpleContent> <extension base="language"> <attri... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.2 Accessibility information | If the consumer has special access condition needed to consume content, the following AccessibilityInformation table is to be used to describe such conditions. <complexType name="AccessibilityInformationType"> <sequence> <element name="AuditoryImpairment" type="mpeg21:AuditoryImpairmentType" minOccurs="0" maxOccurs="un... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.3 User information | The user information table holds multiples of user information and each user information describes information of a single consumer. <complexType name="UserInformationType"> <sequence> <element name="BiographicInformation" type="tva2:BiographicInformationType" minOccurs="0" maxOccurs="unbounded"/> <element name="Access... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.4 Terminal information | The following describes descriptive properties of terminal information. <simpleType name="VersionType"> <restriction base="string"> <whiteSpace value="collapse"/> <pattern value="[0-9]+(.[0-9]+)*"/> </restriction> </simpleType> <complexType name="VersionedControlledTermType"> <complexContent> <extension base="tva:Contr... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.5 Network information | The following describes descriptive properties of network information. <complexType name="NetworkInformationType"> <sequence> <element name="NetworkCharacteristic" type="mpeg21:NetworkCharacteristicBaseType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="networkInformationId" type="tva:TVAIDType" us... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.6 Natural environment information | The following describes descriptive properties of natural information. <complexType name="TemperatureType"> <sequence> <element name="MinTemperature" type="float" minOccurs="0"/> <element name="MaxTemperature" type="float" minOccurs="0"/> </sequence> <attribute name="unit" use="required"> <simpleType> <restriction base... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.7 Usage environment description table | The following describes descriptive properties of usage environment. <complexType name="UsageEnvironmentDescriptionType"> <sequence> <element name="TerminalInformationTable" type="tva2:TerminalInformationTableType" minOccurs="0"/> <element name="NetworkInformationTable" type="tva2:NetworkInformationTableType" minOccurs... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.2.8 TargetingInformationType | The following describes information on targeted user(s) based on user preferences, usage history, device(s), and network capabilities. <complexType name="TargetPlaceType"> <complexContent> <extension base="mpeg7:PlaceType"> <attribute name="exclusive" type="boolean" use="optional" default="false"/> </extension> </compl... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.3 Coupon description | A coupon description allows you to describe pricing and discount information for a content item. <complexType name="NonTVACouponRefType"> <simpleContent> <extension base="anyURI"> <attribute name="couponAuthority" type="string" use="required"/> </extension> </simpleContent> </complexType> <complexType name="RequiredCou... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 6.4 Extended purchase item description | The following allows instantiation of rights information and coupon information with a purchase item. <complexType name="NonTVARightsInformationRefType"> <simpleContent> <extension base="anyURI"> <attribute name="rightsExpressionFormat" type="mpeg7:termReferenceType" use="required"/> </extension> </simpleContent> </com... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7 Extensions to programme description datatypes | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7.1 Extended basic content description datatype | In the present document, the Phase 1 BasicContentDescriptionType has been extended to enable the description of new content types, content packages, content targeting and the association of printable material with content. ETSI ETSI TS 102 822-3-3 V1.6.1 (2012-12) 45 <complexType name="ExtendedContentDescriptionType"> ... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7.2 Extended instance description | The Phase 1 InstanceDescriptionType is here extended to enable the association of new content properties with individual content instances. <complexType name="ExtendedInstanceDescriptionType"> <complexContent> <extension base="tva:InstanceDescriptionType"> <sequence> <element name="ContentProperties" type="tva2:Content... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7.3 Extended segment description | The ExtendedSegmentDescriptionType enables content providers and others to provide content consumers with coupons as a reward for consuming a content segment. <complexType name="ExtendedSegmentDescriptionType"> <complexContent> <extension base="tva:BasicSegmentDescriptionType"> <sequence> <element name="RewardCoupon" t... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7.4 Extended related material type | The ExtendedRelatedMaterialType enables content providers to declare the properties of related content that is referenced by the metadata description but not directly described by it. <complexType name="ExtendedRelatedMaterialType" mixed="false"> <complexContent mixed="false"> <extension base="tva:RelatedMaterialType">... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 7.5 Extended service information type | The Phase 1 ServiceInformationType is here extended to enable the association of targeting metadata with individual services. <complexType name="ExtendedServiceInformationType"> <complexContent> <extension base="tva:ServiceInformationType"> <sequence> <element name="TargetingInformation" type="tva2:TargetingInformation... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8 Content package description | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.1 Introduction | A package is defined as a collection of items, where an item is a consumable entity, and the terminal/user is able to select between the various items of a package, therefore personalizing the end experience. An item is made up of one or more components, which again can be selected depending on such criteria as: • the ... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.2 Declarations | The following defines the syntax and semantics for the declarations. Declarations are used to define items, descriptors, components, and anchors, which are elements of a package so that, within the same document, those elements can be referenced more than once by using ReferenceType to compose the package. <complexType... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.3 Descriptor | The following defines the syntax and semantics for the descriptor. A descriptor is used to associate descriptive data with a parent element which can a package, an item, a component, an anchor, a choice or a selection. <complexType name="ObjectDescriptionType"> <sequence> <element name="Description" type="mpeg7:Textual... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.4 Item | An item represents a multimedia experience as an unit of consumption. For example, it may be a video/audio clip, for which there is a choice between different encoding formats. In addition, an item itself can contain further items which allow the further refinement of the multimedia experience. For example, in the case... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.5 Component | Figure 4 shows an example of the temporal relations between items and components. With the relation description defined in RelationType, the relative temporal relation between items and/or components in a package can be described. Temporal relation Temporal relation Temporal relation Temporal relation Temporal relation... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 8.6 Package | A package is defined as a collection of content components that in some combination (either all or a subset) together provide a consumer experience and are intended to be used together. A package can be instantiated with or without main AV content depending on scenarios, in which main AV content and package can be tigh... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 9 Extended user description datatypes | The present clause defines consumer metadata extended to describe consumer and consumer's environments supporting targeting and compatibility with Phase 1 user description metadata. NOTE: Clause 5.5 of TS 102 822-3-2 [4] provides more detailed information on TV-Anytime consumer metadata including User Preferences and U... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 10 Information tables | |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 10.1 Package table | A package is defined as a collection of content components that in some combination (either all or a subset) together provide a consumer with an enriched experience. A package can be instantiated with or without main AV content depending on scenarios, in which main AV content and a package can be tightly associated or ... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 10.2 Interstitial campaign table | The interstitial campaign table is used to hold information about campaigns for which interstitial content descriptions are provided. <complexType name="CampaignDescriptionType"> <sequence> <element name="Agency" type="string" minOccurs="0" /> </sequence> <attribute name="campaignId" type="tva:TVAIDType" use="required"... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 10.4 Coupon table | This table contains the coupon descriptions which are stand-alone, this means not included in the "PurchaseList" of a "BasicContentDescription". <complexType name="CouponTableType"> <sequence> <element name="CouponDescription" type="tva2:CouponDescriptionType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribut... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 10.5 Targeting information table | This table contains the targeting information. <complexType name="TargetingInformationTableType"> <sequence> <element name="TargetingInformation" type="tva2:TargetingInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> Name Definition TargetingInformationTableType A complex type that serves... |
26cca746fec82ba38062f18f32557711 | 102 822-3-3 | 11 Extended TV-Anytime information document | The following extends the TVAMain type developed in TS 102 822-3-1 [3] to enable the instantiation of the extended schema type. <complexType name="ExtendedTVAMainType"> <complexContent> <extension base="tva:TVAMainType"> <sequence> <element name="PackageTable" type="tva2:PackageTableType" minOccurs="0"/> <element name=... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 1 Scope | The present document contains the specification for the remote management and firmware update system for DVB IPTV services and forms an addendum to the DVB IPTV Handbook ETSI TS 102 034 [1]. All aspects of the RMS and FUS functionality which are standardized by DVB are described within this single common document, but ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 2 References | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 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... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 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... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 3 Definitions, abbreviations and notations | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: NOTE: The following definitions for entities, services and functionalities described in the present document are given on an informative basis, with the IPTV Handbook ETSI TS 102 034 [1] containing the normative versions of these defin... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 034 [1] and the following apply: ABNF Augmented Backus-Naur Form ACS Auto-Configuration Server AES Advanced Encryption Standard ALC Asynchronous Layered Coding ASM Any Source Multicast B2B Business To Business BBF Broadband Forum CDS Conte... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 3.3 Notations | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 3.3.1 Augmented Backus-Naur Form (ABNF) | The present document uses the Augmented Backus-Naur Form (ABNF) conform to IETF RFC 2234 [28], for syntax specification. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 14 |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4 Reference Model | 4.0 Overview Figure 1: Overview of RMS-FUS environment architecture The functional model as shown in figure 1 enables a range of methods for CPEs to be remotely managed and provided with firmware updates. These methods are: • RMS-only for managed devices where there is no support for firmware updates; • RMS-FUS for man... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.1 Modes of operation | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.1.0 Characteristics of RMS and FUS entities | The significant difference between the RMS-FUS methods is summarized by describing the abilities of the RMS and FUS entities: • An RMS is a management entity that interacts with individual CPEs: - If the use case requires a network entity to have knowledge of and in defined cases to be able to exert control over indivi... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.1.1 RMS-only mode | This mode will be used to allow a service provider or other agency to manage a population of CPEs on an individual basis because it is assumed the managing authority (the RMS administrator) has knowledge of that population of CPEs. Figure 2 shows an overview of the logical RMS-only architecture. The ability to maintain... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.1.2 RMS-FUS mode | The FUS may be added to manage the ongoing firmware status of a population of CPEs managed by that RMS. This is then the RMS-FUS mode, although the scope of the services offered by any RMS is not specified in the present document. Figure 3 shows an overview of the logical RMS-FUS architecture, the "CPEs (unmanaged)" bl... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.1.3 FUS-only mode | The FUS-only mode will be used to allow unmanaged CPEs to get firmware updates over the network. Figure 4 shows an overview of the logical FUS-only architecture. In this mode the CPEs will either receive notifications of new firmware versions available from the FUS by monitoring the multicast announcement service or di... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.2 Type of firmware update files | Depending on the structure of the firmware stack in the CPE and the policy of the CE manufacturer and RMS (for a managed CPE), a single firmware update image file may be one of several options: • Full firmware stack. • Application. • Middleware. • Middleware module. • Management system. • Boot block. • Configuration. N... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3 The role of the entities in the RMS-FUS architecture | 4.3.0 Overview All the entities identified within the FUS and RMS sub-systems are logical rather than physical in nature. No specific physical device is implied. The architecture supports firmware maintenance for any type of CPE in a managed or unmanaged environment provided they support the present document. The funct... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3.1 CPEs | The CPE is the device in the home environment which is managed by the RMS and for which firmware updates are provided by the FUS. CPEs which are intended to be provided with firmware updates over the network in a DVB specified manner (either managed or unmanaged) should support the appropriate delivery protocols and si... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.