hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4 Content Propagation | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.1 General | The Reference Model provides for Usage Rules to restrict the Propagation of CPCM Content inside the CPCM System to within certain realms, or to possibly leave the realms of the CPCM System altogether. One of these realms is the Authorized Domain (AD), already described in clause 8. The other realms of propagation of CP... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.2 Restrict to Authorized Domain | If Input Content carries the Usage Rule assertion that implies "Restrict to Authorized Domain", then that CPCM Content Item will be maintained within the CPCM System such that it is usable only by CPCM Devices belonging to the Authorized Domain in which it was first Acquired. In other words, it will be "bound" to that ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.3 Restrict to Local Environment | The Local Environment (LE) is the immediate vicinity around a CPCM Device. It approximates to the physical extent of a home. The basic intention with the LE is to allow the Propagation of CPCM Content over the home (local area) network, without any AD binding, but to be able to prevent its Propagation over Wide Area Ne... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.4 Restrict to Localized Authorized Domain | The Localized Authorized Domain (LAD) is the logical interclause of the Authorized Domain and the Local Environment. In other words the LAD means all CPCM Devices that are in the Local Environment and that are also members of the same Authorized Domain. In practice this would mean all devices located within a home that... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.5 Restrict to Geographically Constrained AD | This aspect of Propagation Control within the CPCM System relates to the Geographic Area (GA). The CPCM System is not required to be able to explicitly control the Propagation of CPCM Content in geographic terms, nor is any CPCM Device required to be aware of its geographical location. Rather, the geographic Propagatio... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.4.6 Propagate to Untrusted Space | Certain types of CPCM Content may be allowed to leave the realms of the CPCM System altogether, i.e. to propagate into Untrusted Space. This Usage Rule assertion could be suitable for content distributed according to the Creative Commons licence, for example, or could be valid for promotional clips of commercial conten... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.5 Output Control | As explained in clause 7.4, Device Outputs can convey different types of Content, namely CPCM Content (C.0), Consumed Content at a Consumption Output (C.2.2) and Exported Content (C.3). The abbreviated CPCM Content designations are explained fully under the treatment of each respective CPCM Functional Entity in clause ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.6 Ancillary Control | The CPCM System is required to provide a Usage Rule whereby protection via the CPCM Scrambler is not to be applied to Content within the CPCM System. This Usage Rule is referred to as "Do Not CPCM Scramble" (DNCS). Thus for CPCM Instances that are intended to be able to handle such DNCS CPCM Content, it is required to ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10 CPCM Content | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.1 General | CPCM Content is content that is protected and managed within the CPCM System. For the purposes of the CPCM Reference Model, CPCM Content is given the short-hand notation C.0. The various modes of CPCM Content described in this clause are given derivative labels of C.0 in the interest of brevity. A Content Item is a dis... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2 Content Licence | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.1 General | The Reference Model gives an overview of the contents of the Content Licence without stipulating its actual structure in detail. Figure 20 shows the logical constituent fields of the Content Licence, which may not need to be systematically populated. Figure 20: Notional Structure and Contents of the CPCM Content Licenc... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.2 CPCM Version | This field gives the version of CPCM specifications applicable for the Content Licence. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.3 Content Licence Identifier | The Content Licence Identifier (CLID) uniquely identifies the CPCM Content Licence. The format of the Content Licence Identifier shall be as specified in TS 102 825-4 [2]. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.4 Content Licence Creator | This field identifies the original creator of the (initial) Content Licence upon Acquisition into the CPCM System. The content of the Content Licence Creator shall be as specified in TS 102 825-4 [2]. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.5 C&R Regime Information | This field identifies a list of C&R regimes. A CPCM Instance shall implement at least one of them to access to the Content. ETSI ETSI TS 102 825-2 V1.2.1 (2011-03) 40 The format of the C&R Regime Information shall be as specified in TS 102 825-4 [2]. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.6 Revocation Information | This field gives revocation information for each of the C&R regimes enable to access to the Content The format of the Revocation Information shall be as specified in TS 102 825-4 [2]. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.7 Authorized Domain Identifier | If the Content Item is bound to an Authorized Domain (AD), then the AD Identifier (ADID) indicates to which AD that Content Item is bound. If this field is zero, then the Content Item is not bound to an AD. The ADID shall be generated as specified in TS 102 825-7 [5]. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.8 Content Descrambling Information | This field contains relevant information to descramble CPCM Content: descrambling mode (see TS 102 825-5 [4]) and Content Descrambling Keys, that are the key(s) generated by the Key Management element of the Security Control part of the CPCM Instance that Acquired that Content Item into, or Processed that Content Item ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.2.9 Usage State Information | The Usage State Information (USI) is the CPCM compliant coding of the Authorized Usage applicable to the Content Item associated with the particular Content Licence. The USI may also be carried embedded within the Content Item itself, but the USI stored in the Content Licence is the authoritative USI for that Content, ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.3 CPCM Content Licence Maintenance | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.3.1 General | For CPCM Content for which a Content Licence is maintained, there are two modes foreseen by which the CPCM Content Licence can be managed with respect to the Content Item: • Separate or out-of-band Content Licence. • Embedded or in-band Content Licence. These modes are orthogonal to whether the CPCM Content is scramble... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.3.2 Out-of-band (Separate) Content Licence | This mode is when the Content Licence is securely stored and maintained by a CPCM Instance separately from the CPCM Content Item to which it refers. This type of CPCM Content is given the label C.0.O. Figure 21 shows the representation of CPCM Content with out-of-band (separate) CL, with binding to the associated CPCM ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.3.3 In-band (Embedded) Content Licence | This mode is when the Content Licence is embedded within the CPCM Content to which it refers. This type of CPCM Content is given the label C.0.E. Figure 22 shows the representation of CPCM Content with in-band (embedded) CL, with binding to the associated CPCM Content Item, used in subsequent diagrams to explain CPCM C... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.4 CPCM Content Licence Protection | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.4.1 General | The CPCM System foresees several ways in which the Content Licence of any CPCM Content Item can be protected using the Security Toolbox (TS 102 825-5 [4]). Only methods described in CPCM System specification (TS 102 825-4 [2]) are permitted. The security requirements for the storage of CL keys are the same in each of t... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.4.2 CL Protection by SAC Session Key | In this mode, the CL is protected using the current SAC Session Key KS. CPCM Content protected in this mode is given the label C.0.SAC. In order to introduce the basic schematic model of CPCM Content exchange between two CPCM Devices, Figure 23 shows the basic mode of C.0.O management inside and between CPCM Devices, a... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.4.3 CL Protection by Device Secret | In this mode, the CL is protected using a permanent Device Secret Key KD known only to the CPCM Instance inside the respective CPCM Device. CPCM Content protected in this mode is given the label C.0.D. This mode is valid only for the Storage of CPCM Content managed by the CPCM Device, as such device secrets shall not b... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.4.4 CL Protection by AD Secret | In this mode, the CL is protected using a permanent Authorized Domain (AD) Secret Key KAD accessible only to the CPCM Instances inside the CPCM Devices that are members of that AD. KAD is equivalent to the AD Secret (ADS) described in clause 7.3.3.2.4. ETSI ETSI TS 102 825-2 V1.2.1 (2011-03) 43 CPCM Content protected i... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.5 CPCM Content Security | There are anticipated to be many other issues to be addressed in connection with the three CL protection modes in connection with particular CPCM Usage Rule assertions or combinations thereof. An exhaustive analysis of such is given in CPCM System specification (TS 102 825-4 [2]). |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.6 CPCM Clear Content | The default protection mode for CPCM Content is to apply all the CPCM security tools, i.e. that CPCM Devices establish mutual trust before transferring CPCM Content that is protected by the CPCM Scrambler and used in accordance with the secure USI contained in the Content Licence. CPCM is however required to provide th... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.7 CPCM Content Item Delineation | There is no secure mechanism for delineating service events that are intended to become different Content Items once Acquired by the CPCM System. This is not an issue for on-demand type content delivery systems or with Content from a storage medium, where the Content is made available as separate items at source, but w... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.8 CPCM Content Revocation | If a CPCM device has been compromised, e.g. cloned, it may be revoked on a per Content Item basis. Compliant CPCM Devices, including those that do not use on-line authentication, will be capable of being denied specific CPCM Content in accordance with a Certificate Revocation List (CRL). The CPCM Instance should includ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 10.9 CPCM Content Recovery | Facilities to enable the user to recover legitimately obtained CPCM Content in the case of damaged CPCM Devices of components thereof, or when upgrading or through the replacement of components of CPCM Devices are out of scope of the CPCM System. But the CPCM System shall not preclude the provision of such facilities b... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11 CPCM Content Management | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.1 General | This clause combines all the previously described concepts in order to provide the generic CPCM Content Management model. Each of the five abstract CPCM Functional Entities are described in terms of their mapping to actual implementations in CPCM Devices and the foreseen content management scenarios. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.2 Basic Content Management Model | The CPCM System provides a platform for interoperable post-delivery content management and protection, including a common set of Usage Rules for all content within the CPCM System. This basic content management model is shown in Figure 24. Figure 24: Basic Content Management Model Input Content, with its associated inp... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3 Acquisition | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.1 General | Input Content is received from a Trusted Source and ingested into the CPCM System at the Acquisition Point. Figure 25 shows this, extracting the relevant part of the Abstract Model, and expanding it showing the different types of Input Content. Figure 25: Input Content "Trust" between the Trusted Source and the CPCM In... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2 Protected Delivery | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.1 General | Input Content from a protected delivery system or channel is handed over securely to the CPCM Instance by the Protected Delivery Client. If the Content is already delivered with CPCM compliant scrambling applied and the keys are available to be propagated in the CPCM system, then that content will not need to pass thro... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.2 Conditional Access Integrated in the CPCM Device | In this mode of Protected Delivery, the proprietary Protected Delivery Client is fully integrated inside the CPCM Device. This is depicted in Figure 27. Here the complete process of content Acquisition from the CA system takes place within an integrated host device, e.g. a Set-Top Box (STB). The Protected Delivery Clie... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.3 Conditional Access Smart-Card | Here, two example models are depicted whereby smart-card based approaches could implement the Acquisition of Protected Delivery Content into the CPCM System. The first is where part of the CA Protected Delivery Client is hosted in the smart-card. In the first example, Content Acquisition takes place in a vertical marke... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.4 Conditional Access Module | This form of Acquisition is realized in CPCM by implementing two independent and compliant CPCM Instances, one in the Conditional Access Module (CAM) and one in the generic host receiver Device, which needs no content-provider or CA system specific functionality. Figure 30: CA Module Based Acquisition Example ETSI ETSI... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.5 Free-To-View Delivery | Free-To-View (FTV) delivery is where the broadcast delivery of the Content is protected by scrambling. This clause describes the special case of FTV where this Content is intended to become CPCM Clear Content (see clause 10.6) after Acquisition into the CPCM System, by application of the Ancillary Control Usage Rule of... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.2.6 DRM System | The DRM System form of Acquisition is exemplified below in Figure 33. Here the DRM system client transfers Content to the CPCM Instance by translating the DRM system licence and usage rights into a CPCM Content Licence containing the mapped CPCM Authorized Usage for the respective Content Item. This example assumes C.0... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.3 Trusted Clear Delivery | This is clear, meaning unprotected, Input Content from a Trusted Source. A Trusted Source for clear content could be, for example, a broadcast tuner or broadband terminator (CPE). The clear-to-air tuner module that tuned and decoded a signal that could only be generated by a "commercial" broadcaster could be trusted im... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.3.4 Trusted Content Protection System | A Trusted Content Protection System (CPS) is a third-party content protection system with which a predetermined set of CPCM interoperability rules, including a USI mapping, has been defined and approved by, for example, a C&R regime. This form of Acquisition is shown in Figure 37 for the case of C.0.O generation in CPC... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.4 Storage | Subject to USI allowing a Copy to be created, the Copy of a piece of CPCM Content that is stored in a Storage Entity is referred to as CPCM Stored Content (C.0.2). When a Content Item is copied or consumed, if allowed by the USI, then that Content flow from the Storage Entity is referred to as Retrieved Content (C.0.3)... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.5 Processing | Processing in the context of CPCM is a CPCM compliant operation upon, or Authorized Usage of Content whereby CPCM Content undergoes a permitted transformation from its original form to create new transformed CPCM Content. Figure 40 shows this, extracting the relevant part of the Abstract Model for Content classificatio... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.6 Consumption | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.6.1 General | Consumed Content is elaborated in order to differentiate between pure sound and vision and, for example, electrical and optical device outputs that are constrained to provide only the functionality of immediate Consumption by a connected device. Figure 42 shows this, building on the relevant part of the Abstract Model ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.6.2 Sound and Vision | C.2.1 Sound and Vision is Consumed Content that is directly rendered by the device hosting the Consumption Point. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.6.3 Consumption Output | A Consumption Output (C.2.2) is an Output at a digital (C.2.2.1) or analogue (C.2.2.2) device interface, containing a transformation or signal that is intended to inhibit any other function than immediate consumption of that Content, i.e. to inhibit Storage of that Content. The method of transformation or signalling de... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7 Export | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7.1 General | Exported Content is elaborated in order to differentiate between Trusted (C.3.1), Controlled (C.3.2) and Untrusted (C.3.3) Export, which are all digital. In addition there is Analogue Export (C.3.4). Figure 44 shows this, building on the relevant part of the abstract model for Content classification. Figure 44: Exporte... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7.2 Trusted Export | Trusted Export (C.3.1) is a digital Output to a Trusted CPS for which there is a defined USI mapping, with no explicit control of the Output via USI for CPCM Content transferred to that Trusted CPS. The CPSs included under Trusted Export are defined by each C&R regime. A CPS that is Trusted as an Output is not necessar... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7.3 Controlled Export | Controlled Export (C.3.2) is the digital Output of CPCM Content mapped to a Trusted CPS under the explicit control of the Output Control Usage Rule (clause 9.5) assertion carried with that CPCM Content. The Trusted CPSs included under Controlled Export will be defined by an appropriate registration authority. Controlle... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7.4 Untrusted Export | Untrusted Export (C.3.3) is any digital output or storage format that is not Trusted (or Controlled). Untrusted Exported Content is not protected. The Exported Content may however still carry CPCM USI, if the Export format is compatible with the carriage of CPCM USI. Untrusted Export is under the explicit control of th... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 11.7.5 Analogue Export | Analogue Exported Content (C.3.4) is an unprotected analogue Output, for example for the purpose of analogue recording. Depending on the type of CPCM Content concerned, Analogue Export may be subject to the Output Control Usage Rule (clause 9.5). Such Output control would be implemented as a CPCM Extension and shall on... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 12 Extensions to CPCM | The clauses described so far define the CPCM baseline System. The CPCM baseline functionality may be extended where necessary, either for future additional extended CPCM functionality (CPCM Extension), or for particular proprietary functionality (proprietary Extension). The protection and management of CPCM Content in ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 13 CPCM as an Interoperability Platform | The following elements of the CPCM System, previously described in terms of the CPCM Reference Model, provide the anchors for interoperability in the area of commercial content protection and management in the consumer environment. The first of these are the CPCM security tools: • CPCM Instance Certificate (CIC) format... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 1 Scope | The present document covers a wired Home Network Segment based on IEEE 1394 technology, as described in the Architecture Framework document [1]. The present document concentrates on how IP traffic for DVB services will be carried over IEEE 1394 technology. This covers the encapsulation of IP packets in the IEEE 1394 Se... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 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. • ... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DHCP Dynamic Host Configuration Protocol DSCP Diffserv Codepoint DVB Digital Video Broadcasting HNCD Home Network Connecting Device HNS Home Network Segment IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task ... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 4 Topology of an IEEE1394 Home Network Segment | Based on the description of a Home Network Segment (HNS) in the architectural framework specification [1], an IEEE 1394 - HNS consists of one IEEE 1394 bus. The physical topology of an IEEE 1394 bus is a tree structure. The description of the Home Reference Model in the architectural framework specification [1], furthe... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 5 Carriage of IP-based Traffic | Within the context of the architectural framework specification [1], all IP-based traffic will be carried transparently over an IEEE 1394 network. Therefore the interfaces IPI-1, IPI-2, and IPI-3 on an IEEE1394 - HNS, shall comply to the IETF specification IPv4 over IEEE 1394 [4]. For the addressing of devices on an IE... |
c6ac810bb093d6ec451419530fdd654b | 102 813 | 6 QoS | Because it is expected that the IP traffic transported on a network will consist of types with varying importance, priority levels shall be given to the different traffic types. Therefore all traffic on the interfaces IPI-1, IPI-2, and IPI-3 has to be marked to ensure consistency. The marking shall be based on the Diff... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 1 Scope | The present document is one in a series of Technical Specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products an... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 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... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO/IEC 10646 (2003): "Information technology - Universal Multiple-Octet Coded Character Set (UCS)". [2] XML Schema, W3C Recommendations (version 20010502). NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-0-200... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 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. Not applicable. |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 3 Definitions, abbreviations and mnemonics | |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 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. head end: source of emission of the transport stream where metadata is inserted metadata: d... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AU Access Unit BiM Binary format of MPEG-7 CRID Content Reference IDentifier NOTE: An identifier for content that is independent of its location. DDL Description Definition Language NOTE: The language used to define description schemes in MPEG... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 3.3 Mnemonics | For the purposes of the present document, the following mnemonics are defined to describe the different data types used: bslbf: Bit string, left bit first, where "left" is the order in which bit strings are written. Bit strings are generally written as a string of 1 s and 0 s within single quote marks, e.g. "1000 0001"... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4 System mechanisms in a unidirectional environment | |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.1 Overview | |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.1.1 Main features of a unidirectional environment | Unidirectional environments deliver content and metadata from the transmitting device (head-end) to the terminal device Personal Digital Recorder (PDR) over a one-way link. No communication is possible from the PDR to the head-end. TVA fragments Delivery Layer Terminal A/V content Figure 2: Unidirectional environment T... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.1.2 Access methods | Resources available to PDRs will vary, as will the nature of different unidirectional environments. Because of this it is anticipated that there are a number of ways in which a receiver may wish to acquire and navigate TV-Anytime metadata descriptions. The present document has been designed to support the following met... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.1.3 Definition of a TV-Anytime metadata description | A TV-Anytime metadata description is the present document, which is to be sent to the PDR. It is produced in accordance with the schema specified in the TV-Anytime metadata specification (see TS 102 822-3-1 [9], clause 6, TS 102 822-3-3 [10], TS 102 822-3-4 [11], TS 102 822-8 [19], TS 102 822-9 [20]). TV-Anytime has se... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.1.4 TV-Anytime metadata description size | In many systems a TV-Anytime description can become very large. As an example, a valid TV-Anytime document could contain all the descriptive data supplied by a single provider to feed an ECG for the next 15 days. The data-set could consist of a set of descriptions for the whole list of programmes, series and groups of ... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2 Metadata general delivery framework | The delivery of TV-Anytime metadata can be viewed as five distinct processes. Fragment Encode Encapsulate Transmit Index Transmit TVA Description Figure 3: Processes associated with delivery of metadata |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2.1 Introduction to fragmentation | Fragmentation is the generic decomposition mechanism of a TVA metadata description into self-consistent units of data, called TVA fragments. The definition of TVA fragment types allowed by TV-Anytime can be found in clause 4.3. The self-consistency capability of a TVA fragment means that: • Fragments can be obtained in... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2.2 Introduction to encoding | To enable the efficient (in terms of bandwidth, navigability and updating) delivery of data within a unidirectional environment, it is necessary to represent the TVA metadata fragments in a binary format. TV-Anytime has chosen the MPEG-7 BiM method as defined in ISO/IEC 15938-1 [4] (MPEG-7 Systems part) as the preferre... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2.3 Introduction to encapsulation | Once the fragments have been encoded they need to be encapsulated. The process of encapsulation provides further information to enable a receiving device to manage a set of transmitted TVA fragments. A receiver needs to be able to uniquely identify a fragment within the TVA metadata fragment stream and also to be able ... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2.4 Introduction to Indexing | Within a TV-Anytime metadata fragment stream there are likely to be many hundreds of fragments. Due to the volume of information necessary to provide the enhanced functionality expected of a PDR it is important that there is an efficient mechanism for locating information from within the TVA metadata fragment stream. I... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.2.5 Logical decoder architecture | The components of the logical decoder architecture are shown below. Each of these components has a specific role in the process of reconstructing a TVA description or in the navigation of the TVA fragments via the indexing system. Delivery Layer Binary Decoder Metadata Manager fragment_version fragment_id TVA fragment ... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3 Metadata description fragmentation | To enable the efficient delivery, updating and navigation of a TV-Anytime metadata description, a number of normative TVA fragment types have been defined. A fragment is the ultimate atomic part of a TV-Anytime metadata description that can be transmitted independently to a terminal. A fragment shall be self consistent... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1 TVA metadata fragments | The TV-Anytime metadata description can be split into a number of standardized types of self contained fragments. These TV-Anytime normative fragments are defined as follows. ETSI ETSI TS 102 822-3-2 V1.6.1 (2010-07) 18 |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.1 TVAMain fragment | The TVAMain fragment is special since every TVA fragment stream must contain one instance of this fragment type. The TVAMain fragment contains the TVAMain / ExtendedTVAMain root element plus a limited range of child nodes. Figure 6: UML-like representation of a TVAMain fragment As can be seen from the representation in... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.2 MetadataOriginationInformation fragment | The MetadataOriginationInformation element, as defined in TS 102 822-3-1 [9], shall form a single TVA fragment. The MetadataOriginationInformation element is a child of the MetadataOriginationInformationTable, which is a member of the TVAMain fragment. Figure 7: UML-like representation of a MetadataOriginationInformati... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.3 ProgramInformation fragment | A ProgramInformation fragment is one of the key attractor types of a TVA system (TS 102 822-3-1 [9]), it carries an element of type ProgramInformationType and all child nodes thereof. This type contains descriptive information about a piece of content, the content being identified by a CRID. The ProgramInformationEleme... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.4 GroupInformation fragment | A GroupInformation fragment contains an element of type GroupInformationType and all child nodes thereof. This contains descriptive information about a conceptual content group e.g. Series, Serial, Collection, etc. The GroupInformationElement is a child element of the GroupInformationTable, which forms part of the TVAM... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.5 OnDemandProgram and OnDemandService fragment | Within a unidirectional environment the OnDemandProgramType and the OnDemandServiceType are seen to be of limited use. However if a broadcaster wishes to transmit OnDemand program location information, a complete OnDemandProgram or an OnDemandService element instantiating respectively one of these types shall form a si... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.6 BroadcastEvent fragment | The BroadcastEventType has been designed to represent dynamic events in an environment where frequent updates are required (TS 102 822-3-1 [9]). A BroadcastEvent fragment is thus an instance of the BroadcastEventType, a child element of the ProgramLocationTable, which forms part of the TVAMain fragment. Figure 10: UML-... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.7 Schedule fragment | The Schedule type provides an alternative way to that of the BroadcastEvent type for describing events within a broadcast system. It provides a mechanism to group a number of consecutive events together, which span a given time period on a single service (TS 102 822-3-1 [9]). The use of the ScheduleType for describing ... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.8 ServiceInformation fragment | A ServiceInformation fragment contains details about a single Service within a broadcast system (TS 102 822-3-1 [9]). A ServiceInformation fragment is an instance of a ServiceInformationType and a child of the ServiceInformationTable, which is a member of the TVAMain fragment. Figure 12: UML-like representation of a Se... |
c6a5a7aac146a2b1a7d6696a7b04b65f | 102 822-3-2 | 4.3.1.9 CreditsInformation fragments | The CreditsInformationTable element instantiates the CreditsInformationTableType (TS 102 822-3-1 [9]). It gathers together details about the people and organizations involved in the production of the different content items described in the metadata description. It is used to lighten the size of the description of each... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.