hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 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... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 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... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 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... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 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. |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 3 Definitions and abbreviations | |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: process of retrieving selected content client: typically a personal digital recorder or any device connected to the Internet content: audio, video or other types of material the viewer would like to access NOTE: Movies, ga... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CRID Content Reference IDentifier NOTE: An identifier for content that is independent of its location specified by TS 102 822-4 [6]. DVB Digital Video Broadcasting project NOTE: European project providing technical specifications for publicati... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4 Core data | |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.1 Description | The following elements have been identified to be part of the core data: • One or more selected contents, each of them containing: - a CRID with optionally an IMI; - a TVAMain table as specified in TS 102 822-3-1 [3], containing information on a specific content item and/or instance (optional); - a content referencing ... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.2 Namespace | The namespace for the TV-Anytime CoreData interchange format has been defined as: urn:tva:CoreData:2012 ETSI ETSI TS 102 822-8 V1.6.1 (2012-12) 10 |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.3 CoreData element | <complexType name="SelectedContentType"> <sequence> <element ref="tva:TVAMain" minOccurs="0"/> <element ref="CR:ContentReferencingTable" minOccurs="0"/> <element name="WSIFServerAddress" type="anyURI" minOccurs="0"/> <element name="Action" type="CD:CoreDataActionType" minOccurs="0"/> </sequence> <attribute name="id" ty... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.4 Action element | <complexType name="CoreDataActionType"> <sequence> <element name="Type" type="tva:ControlledTermType"/> </sequence> <attribute name="instruction" use="optional" default="create"> <simpleType> <restriction base="string"> <enumeration value="create"/> <enumeration value="cancel"/> </restriction> </simpleType> </attribute... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.5 Examples | |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.5.1 CoreData example for a single selected content | Here is an example of a "CoreData" structure containing detailed information about a selected content to be recorded. Content location is included in the ProgramLocationTable. <?xml version="1.0" encoding="UTF-8"?> <CoreData xmlns="urn:tva:CoreData:2012" xmlns:tva="urn:tva:metadata:2012" xmlns:CR="urn:tva:ContentRefere... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 4.5.2 CoreData example for a set of selected contents | Although this example is not realistic, it is used to illustrate the different actions which can be requested on a selected content. It includes: • A selected content with the action "recordAllowDuplicates". • A selected content with the action "remind". • A selected content with the action "recommend". • A selected co... |
8df4bb22c95686d4c2327db534f591e9 | 102 822-8 | 5 TVA metadata retrieval from web sites | There are many providers of EPG related services on the web who offer information about content in formats that would not be understood by TV Anytime enabled devices. Without using the present document, when a consumer sees a piece (or pieces) of content described on the website EPG, and chooses to record that content,... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 1 Scope | The present document gives the specification for the link between a Digital Radio Mondiale (DRM) Multiplexer and a DRM Modulator. |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 2 References | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 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... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 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... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 3 Definitions, symbols, abbreviations and conventions | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Alternative Frequency Switching (AFS): feature of the DRM multiplex which allows receivers to automatically re-tune to a frequency offering more reliable reception without a break in the decoded audio byte: collection of 8-bits ETSI ET... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: Nx The value "N" is expressed in radix "x". The radix of "x" is decimal, thus 2A16 is the hexadecimal representation of the decimal number 42. |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AD Anno Domini AF Application Framing AFS Alternative Frequency Switching ASCII American Standard Code for Information Interchange BOOTP BOOT Protocol CRC Cyclic Redundancy Check DCP Distribution and Communication Protocol DHCP Dynamic Host Co... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 3.4 Conventions | The order of bits and bytes within each description uses the following notation unless otherwise stated: • in figures, the bit or byte shown in the left hand position is considered to be first; • in tables, the bit or byte shown in the left hand position is considered to be first; • in byte fields, the Most Significant... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 4 General description | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 4.1 System overview | The Multiplex Distribution Interface carries the description of a complete DRM Multiplex from the equipment generating the data (the DRM Multiplex Generator) to the DRM Modulator in such a way that reliable networks of transmitters (MFN, SMFN and SFN) can be constructed. Typically the DRM Multiplex Generator will be si... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 4.2 System architecture | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 4.2.0 General | The protocol stack provided by the Distribution and Communication Protocols (ETSI TS 102 821 [2]) is described in figure 1. As can be seen, the Multiplex Distribution Interface as described in the present document builds upon the DCP stack, defining the TAG Items to be used and the format of the data carried. The resul... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 4.2.1 TAG items and packets (informative) | For ease of reference, the basic structure of a TAG Packet and the TAG Items it contains is described in figure 2. The normative definition is contained in ETSI TS 102 821 [2]. Name Length Value TAG Item TAG Item TAG Item padding TAG padding TAG Item TAG Item TAG Item TAG Packet <8 bytes <8 bits 4 bytes Length bits 4 b... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5 TAG items | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.0 Introduction | Each MDI Packet consists of a number of TAG Items where each TAG Item carries a single piece of information. When combined, the TAG Items present in one MDI Packet completely describe one DRM logical frame. Upon reception of an MDI Packet, one DRM transmission frame may be produced. A DRM transmission super-frame may b... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1 Mandatory TAG items | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.0 General | DRM equipment receiving/decoding MDI shall correctly decode and interpret the following TAG Items. DRM equipment generating MDI shall generate all the following TAG Items, unless an exception is explicitly stated for individual TAG Items. Table 1: Mandatory TAG items TAG Name (ASCII) TAG Length (bits) TAG Value *ptr 64... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.1 Protocol type and revision (*ptr) | This TAG Item shall be included in every MDI Packet. TAG Value TAG Length TAG Name Protocol Minor Major D M D I * p r t 0016 0016 0016 0016 0016 0016 0016 4016 ASCII “*ptr” 64 bits 4 bytes 4 bytes 8 bytes Figure 3: Protocol type and revision Protocol type: The ASCII string "DMDI" (DRM Multiplex Distribution Interface).... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.2 DRM logical frame count (dlfc) | This TAG Item shall be included in every MDI Packet. TAG Value TAG Length TAG Name Logical framecount d l f c 0000000016 … FFFFFFFF16 ASCII “dlfc” 32 bits 0016 0016 0016 2016 4 bytes 4 bytes 4 bytes Figure 4: DRM logical frame count Logical frame count: The value shall be incremented by one by the device generating the... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.3 Fast access channel (fac_) | This TAG Item shall be included in every MDI Packet. Figure 5: Fast access channel Channel parameters: as described in ETSI ES 201 980 [1], clause 6.3.3. Service parameters: as described in ETSI ES 201 980 [1], clause 6.3.4. The data carried in the Service Parameters shall be repeated according to the FAC repetition ru... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.4 Service description channel (sdc_) | This TAG Item shall only be included in the MDI Packet containing the data for the first logical frame in each transmission super-frame. This TAG Item shall not be included in any other MDI Packets. TAG Name TAG Value TAG Length (8n + 24) bits ASCII “sdc_” s d c _ Service Description Channel Block AFS Index SDC data CR... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.5 Service description channel information (sdci) | This TAG Item shall be included in every MDI Packet. TAG Name TAG Value TAG Length ... Protection (24n+32) bits ASCII “sdci” s d c i P L A P L B n+1 stream description(s) Rfu Stream Description 0 Stream Description n 4 bytes 4 bytes 3 bytes 3 bytes 4 bits 2 bits 2 bits ... Figure 7: Service description channel informat... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.6 Robustness mode (robm) | This TAG Item shall be included in every MDI Packet. TAG Name TAG Value TAG Length 8 bits ASCII “robm” r o b m Robustness mode 0016 0016 0016 0816 4 bytes 4 bytes 1 byte Figure 8: Robustness mode Robustness mode: the robustness mode to be used encoded as shown in table 2. All other values are reserved for future use. T... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.1.7 Stream <n> (str0, str1, str2 and str3) | The str0, str1, str2 and str3 TAG Items shall contain the data for the corresponding DRM stream. If the TAG Length is zero, the TAG Item may be omitted from the MDI Packet. TAG Name TAG Length TAG Value 8n bits Data ASCII str0, str1, str2 or str3 s t r 0 4 bytes 4 bytes n bytes Figure 9: Stream data Data: the content o... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.2 Optional TAG items | |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.2.0 General | Every DRM MDI implementation may choose to support the following optional TAG Items. Where one or more of the optional TAG Items are supported, they shall behave as described below. When not supported by an implementation, the presence of these TAG Items shall be ignored. Table 3: Optional TAG Items TAG Name (ASCII) TA... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.2.1 Information (info) | This TAG Item may be included in any MDI Packet. TAG Name TAG Value TAG Length 8n bits ASCII “info” i n f o UTF-8 text 4 bytes 4 bytes n bytes Figure 10: Info TAG item UTF-8 Text: an arbitrary number of bytes encoding a text string using UTF-8 (ISO/IEC 10646 [3]). No fixed purpose is defined for this string, however it... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.2.2 Timestamp (tist) | This TAG Item shall be included in every MDI Packet intended to be broadcast using an SFN or SMFN. It may be included in any other MDI Packet if desired. TAG Name TAG Value TAG Length UTCO 64 bits ASCII “tist” t i s t DRM Timestamp 0016 0016 0016 4016 Milliseconds Seconds 4 bytes 4 bytes 8 bytes 14 bits 40 bits 10 bits... |
7fac14e27bf0fc41d4041df494f0a560 | 102 820 | 5.3 Revision history | Table 4 contains the history of the TAG Item changes of the MDI Protocol for each new revision. Table 4: Revision history Major revision Minor revision Date Changes from previous to new revision 000016 000016 2003-02-04 Initial revision 000116 000016 2010-03-01 Values and definitions for robustness mode E added; versio... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 1 Scope | The present Phase 2 document extends the scope for data exchange between users and content/service providers. The exchange of such user profiles offers a number of possible benefits to both consumers and service providers. For example, a personalized web-service in which a service provider provides the response of user... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-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... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-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... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-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. Not applicable. |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 3 Definitions and abbreviations | |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access control: act of mediating requested access to a resource based on privilege attributes of the requestor and control attributes of the requested resource account: formal business agreement for providing regular transactions and s... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: EPG Electronic Programme Guide HTTP Hyper Text Transport Protocol ID-WSF IDentity - Web Service Framework IP Internet Protocol OASIS Organization for the Advancement of Structured Information Standards PDA Personal Digital Assistance PDR Perso... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 4 TV-Anytime User Profile Service Type | |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 4.1 Service Type Definition | The TV-Anytime user profile service is a web service that acts upon some resource to either retrieve and update information (such as preferences, demography, and location) about a user, or perform some action for the benefit of some user. The types used in the TV-Anytime user profile service are defined in the "urn:tva... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 4.2 Discovery | A service provider can use the discovery service to ascertain the location of a specific identity service for a user. The discovery service enables various entities to dynamically and securely discover a user's identity services, and it responds, on a permission-basis, with a service description of the desired identity... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 4.3 Data Model | The data model of the TV-Anytime user profile is defined in the TV-Anytime metadata specification TS 102 822-3-3 [5]. The XML schema defined thereby specifies the data the service can host. The data model defines the data and the data structure. Typically this structure is hierarchical and has the root node TVAMain. Th... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5 TV-Anytime User Profile Message Interface | This clause defines two protocols, one for querying data and another for modifying data. These protocols both rely on a request/response message-exchange pattern. The messages specified in the present document for those protocols are carried in the SOAP body [18]. More information on the general aspects of SOAP can be ... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1 Common Parts | |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.1 Resources | Both protocols, for querying and modifying data, have a defined hierarchy for accessing data. In the first level the desired resources are selected. For example, a resource might be the personal profile of a certain person. Multiple resources can be accessed in a single request, but querying and modifying cannot be mix... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.2 <Select> element | The second level of resource selection is inside the <Query> and <Modify> elements. The request message shall describe in more detail what it wants to access inside the specified resource. This is specified in <Select> elements. As an example, when the resource is a personal profile, the <Select> can point to UserPrefe... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.3 Discovery Option Keywords | The following discovery option keywords are used to indicate services options of the TV-Anytime user profile services. Table 2: Description of Discovery Option Keywords Discovery Option Keywords Definition Urn:liberty:dst:allPaths Optional. This indicates that the service provider supports all (required) paths without ... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.4 <Status> | A response message contains one or more <Status> elements to indicate whether or not the processing of the request succeeded. A <Status> element has a code attribute, which contains the return status as a string. Table 3 defines the status codes to be used as values for the code attribute. ETSI ETSI TS 102 822-6-3 V1.6... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.5 Linking with ids | Different types of id attributes are used to link queries and responses together. Response messages are correlated with requests using messageId and inResponseToMessageId attributes that are present in the SOAP Header [18]. Services shall include messageId and inResponseToMessageId attributes in all request and respons... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.1.6 The timeStamp Attribute | A response message can also have a time stamp. This time stamp is provided so that the requesting party can later check whether there have been any changes since a response was received, or make modifications, which will only succeed if there have been no other modifications made after the time stamp was received. |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.2 Querying Data | Two different kinds of queries are supported, one for retrieving current data, and another for requesting only changed data. These two different kinds of queries can be present together in the same message. The response can contain the data with or without the common technical attributes, depending on the request. Some... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.2.1 <Query> | The schema for the Query operation is as follows. ETSI ETSI TS 102 822-6-3 V1.6.1 (2012-12) 17 <complexType name="QueryType"> <sequence> <group name="ResourceIDGroup" type="tvap:ResourceIDGroup" minOccurs="0"/> <element name="QueryItem" minOccurs="0" maxOccurs="unbounded"> <complexType> <sequence> <element name="Select... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.2.2 <QueryResponse> | The schema for QueryResponse is as follows. ETSI ETSI TS 102 822-6-3 V1.6.1 (2012-12) 18 <complexType name="QueryResponseType"> <sequence> <element name="Status" type="tvap:StatusType" minOccurs="1"/> <element name="Data" minOccurs="0" maxOccurs="unbounded"> <complexType> <sequence> <element name="TVAMain" type="tva:TV... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.2.3 Processing Rules for Query | A request message can contain multiple <Query> elements. |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.3 Modifying Data | The data stored by a data service can be given initial values, existing values can be replaced with new values and the data can also be removed. Usually the principal can make these modifications directly at the data service using the provided user interface, but these modifications may also be made by other service pr... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.3.1 <Modify> | The schema for Modify is as follows. <complexType name="ModifyType"> <sequence> <group name="ResourceIDGroup" type="tvap:ResourceIDGroup" minOccurs="0"/> <element name="Modification" maxOccurs="unbounded"> <complexType> <sequence> <element name="Select" type="tvap:SelectType" minOccurs="0"/> <element name="NewData" min... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.3.2 Modify Response | The <ModifyResponse> element contains the <Status> element, which describes whether or not the requested modification succeeded. There is also a possible time stamp attribute, which provides a time value that can be used later to check whether there have been any changes since this modification, and an itemIDRef attrib... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 5.3.3 Processing Rules for Modify | A request message can contain multiple <Modify> elements. |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6 Notes on Privacy and Security | |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1 Privacy Considerations | |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1.1 Introduction | Information concerning demography, personal preferences, and viewing history, by its very nature, is fairly sensitive. Even a very simple indication of personal taste allows a watcher to have an idea of the user's personal traits. When detailed status and location information are added to the personal profile, control ... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1.2 Authorization of Watchers | At a minimum a user shall be able to specify who is able to request his personal profile for him/her. The consequence of this to the implementer is that incoming profile requests shall be checked to ensure that their requesting Principal has been authorized by the target Principal to receive his/her personal profile in... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1.3 Consent | The <Consent> header block allows profile exchange service clients to indicate to the profile exchange service provider that they have obtained consent to receive the presence data for a Principal. |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1.4 Usage Directives | The <UsageDirective> header block allows a principal to specify limits on how his/her presence data may be used. The semantics for this block have not yet been fully specified, but one possible usage would involve a URL being specified in the UsageDirective block in the presence response, and this URL would reference a... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.1.5 Options | As has been discussed, it is important that the user profile service provider be capable of specifying what information contained in user metadata can be exchanged and, in particular, whether the user ID is to be shared. This is handled by defining options in the offered resources that are publicized during the exchang... |
bc73ab1c39a922bf95b76bc6f2a4588d | 102 822-6-3 | 6.2 Security Mechanisms | The security mechanisms described in TS 102 822-7 [12] and Web Services Security: SOAP Message Security [19] should be supported. ETSI ETSI TS 102 822-6-3 V1.6.1 (2012-12) 22 Annex A (normative): Schema and classification scheme A.1 Schema <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="urn:tva:profile:... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 1 Scope | The present document contains normative mappings between Digital Video Broadcasting (DVB) Free-To-Air Control Signalling and Content Protection and Copy Management (CPCM) Usage State Information (USI) and from CPCM to external content protection systems. |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 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... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems". [2] CEA-608-E (April 2008): "Line 21 Data Service". [3] CEA-805-D (November 2008): "Data Services on the Compo... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 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] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 3 Definitions and abbreviations | |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [7] apply. |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [7] and the following apply: CGMS-A Copy Generation Management System on Analogue video interface NOTE: Please see EN 300 294 [4], IEC 61880 [5] and IEC 62375 [6]. RCD Redistribution Control Descriptor RCI Redistribution Control Informati... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 4 Introduction | The CPCM System provides an interoperability platform and common trusted destination for commercial content in the consumer environment, so it is natural that CPCM should be open to being mapped to, and from, any other suitable content delivery system, content protection system or secure content storage format. Such ma... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5 Acquisition mappings | |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.1 General | As described in TS 102 825-3 [8], when Content first enters the DVB CPCM system, at a particular Acquisition Point, the Authorized Usage of that Content shall be determined and then preserved by securely binding it as USI and Auxiliary Data to the Content. Content that may be Acquired into DVB CPCM should include input... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.2 DVB Defined Signalling | The present document includes two sets of input usage rights signalling, defined in EN 300 468 [1], and defines their mappings to CPCM be it for user interface or Usage Rule mapping purposes. • CPCM Delivery Signalling. - This signalling is informative and is not used to determine the CPCM USI during Acquisition unless... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.3 CPCM Delivery Signalling | The CPCM Delivery Signalling in EN 300 468 [1] provides a set of input usage rights signals that is, with the exception of the temporal Remote Access Rules, a one-to-one match for internal CPCM USI fields. For the avoidance of doubt, the internal CPCM USI may not match this CPCM Delivery Signalling since the CPCM USI i... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.4.1 General | The following normative section describes how compliant DVB CPCM implementations shall Acquire incoming Free-To-Air (FTA) broadcast signals that include DVB-defined FTA usage signalling defined in EN 300 468 [1] including the mapping of such signalling to CPCM Usage State Information as defined in TS 102 825-3 [8]. Fre... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.4.2 DVB FTA receivers/Acquisition Points | DVB CPCM implementations receiving DVB FTA broadcasts shall inspect them for the DVB-defined FTA usage signalling defined in EN 300 468 [1] and, if present, shall Acquire such Content into CPCM using the mapping defined herein. In the absence of any signalling, DVB FTA broadcast content shall not be Acquired into CPCM,... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.4.3 DVB FTA broadcast signalling | The DVB-SI (EN 300 468 [1]) defines a generic signalling mechanism for Free-to-Air broadcasts, which provides generic content protection information. This clause describes the normative interpretation of these generic signals to the specific DVB-CPCM environment, and table 1 precisely defines the specific mapping into ... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 5.4.4 Mapping to CPCM USI | CPCM Acquisition Points shall use the following mapping for FTA broadcast signalling to CPCM USI. Column '3' shows default values that may be superseded by a C&R regime. Table 1: DVB FTA USI mapping USI field "control_remote_access_over_internet" Comment '0' '1' '2' '3' Copy and Movement Control Copy Control Informatio... |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 6 Consumption and Export mappings | |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 6.1 General | In general, CPCM USI and Auxiliary Data should be retained, to the extent possible, on all Outputs from the CPCM System, including analogue outputs and digital Consumption and Export Outputs to Trusted CPSs. |
fa230c9d1b025eb0a14955b54e49e0ce | 102 825-10 | 6.2 Digital outputs | The mapping of CPCM USI and Auxiliary Data shall be conducted in accordance with rules set forth in the C&R regime. Note that the original signalling used to generate the USI that is retained within the Auxiliary Data may be used in addition to the CPCM USI to ensure the best possible mapping. All Revocation Lists for ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.