hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3.2 RMS Administrator | Information about a managed population of CPEs will be held by an RMS administrator based on product installation information, service changes, etc. FUS Firmware update Update files and metadata Signaling CE manufacturer IPTV services CPEs (unmanaged) ETSI ETSI TS 102 824 V2.1.1 (2016-04) 18 This RMS Administration sub... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3.3 RMS | The RMS sub-system, for which the functionality is described in clause 5.2 is responsible for managing, enforcing, and modifying the behaviour of the population of CPEs under its control. The purpose of an RMS is to: • Manage individual CPEs in terms of: - Provisioning: Configuration. - Assurance: Diagnostics. Tr... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3.4 CE manufacturer | The firmware updates will be made available by the manufacturers of the CPEs - the CE manufacturers. The CE manufacturers shall also provide the descriptive metadata associated with the firmware update files. The logical interfaces are specified in the present document, but the method of delivery used by the CE manufac... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.3.5 FUS | A FUS deals with classes / collections of CPEs without any knowledge about individual CPEs and to be compliant with the present document is a content server which is capable of: • Receiving metadata associated with new firmware update files from the CE manufacturer. • Downloading firmware updates from the CE manufactur... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.4 Control priorities of RMS vs. FUS-only | An RMS-FUS environment may include multiple RMSs controlling different populations of CPEs, as well as some unmanaged CPEs which shall be able to operate using the signalling and messaging within the capability of the FUS. If an RMS is present which manages all or part of the population of CPEs supported by the FUS, th... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.5 CPE Bootstrap process | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.5.1 FUSS Process (Managed and unmanaged CPEs) | Bootstrap is the method by which the CPE identifies the initial entry point into the FUS server using information made available through the FUS stub file (FUSS) and is described in clause 9 of ETSI TS 102 034 [1]. For any CPE the URI or address provided in the FUS stub (FUSS) will lead to the entry point from where a ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.6 Running state behaviour of CPEs | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.6.1 Unmanaged CPEs | After the boot process has completed and the CPEs are working in the normal state the methods described in the present document allow the CPEs to continue to monitor for the availability of firmware updates. The present document does not define the operational behaviour of the CPEs except in terms of the interfaces wit... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 4.6.2 Managed CPEs | Managed CPEs may use the CPE management channel based on methods defined in the appropriate RMS documents, also in addition to the options which are described above for the unmanaged CPE. It is assumed that the CPE will report update success/failure back to the RMS controlling it using one of the mechanisms specified b... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5 The RMS-FUS sub-systems | 5.0 Reference architecture The reference architecture in figure 5 extends the overall schematic of the RMS-FUS architectures (figures 2, 3 and 4) to show additional detail of the functional blocks and interfaces for the FUS and RMS sub-systems. In the RMS-only and FUS-only options the appropriate interfaces will show t... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.1 Interfaces overview | Table 1 contains an introduction to the function of each interface and the aspects which are standardized as either mandatory or optional. Table 1: Overview of interface functions Interface number Interface name Description Scope in terms of the present document 1 Firmware package This carries the files containing the ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.2 The Remote Management System (RMS) | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.2.0 General | This clause describes the functionality of the logical modules in the RMS sub-system in terms of specifying their interaction with the other modules and sub-systems within a managed environment. The total functional capability of a specific RMS for a specific RMS-FUS environment is not specified in the present document... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.2.1 Communication with RMS administration | Communication between RMS and RMS administration is done through interface 10. The requirements for this is out of scope of this DVB document in terms of both transport protocol and messaging format. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.2.2 Management of the inventory | The RMS inventory (interface 13) is internal to the RMS; therefore all aspects of this functionality and the communication over interface 13 is out of scope for the present document. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.2.3 CPE management interface | In a managed network it is recommended that the RMS shall manage the CPEs by using the methods specified in TR 069 [6] and associated documents, including extensions created within the development of the present document and profiled in annex A. The CPE management interface is shown as interface 9 in figure 5. Other ex... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3 The Firmware Update System (FUS) | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.0 General | This clause describes and specifies the functionality of the logical modules in the FUS sub-system as shown in figure 5. The diagram is conceptual and is not intended to describe any actual implementation. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.1 FUS manager and storage modules | The function of the FUS manager is to coordinate the download of the firmware update files from the CE manufacturer over interface 1 in accordance with the associated metadata delivered from the CE manufacturer to the FUS manager over interface 2, arrange the process of storage, and supply the appropriate files to the ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.2 Signalling and messaging to enable CPEs to locate updates | 5.3.2.0 Ways of signalling and messaging The FUS shall provide the signalling and messaging to enable the CPE to locate the appropriate update files and the associated delivery information. This information shall be made available in two forms: • Announcement service: one or more multicast delivery services carrying in... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.2.1 Multicast announcement service | The FUS may distribute firmware announcement information via one or more multicast channels. The HNEDs may join these channels based on information provided for example by the FUS stub file. The announcement data shall be created and maintained by the FUS based on available FUS metadata. The firmware announcement servi... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.2.2 Unicast query/response channel (QRC) | The query/response channel is shown as interface 8 in figure 5 and described in detail in clause 6.8. It is able to carry queries originated by a CPE to the FUS to identify whether a firmware update is available based on the information supplied in the query and the metadata provided by the CE manufacturer. No capabili... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.3 Firmware update delivery | 5.3.3.0 Delivery modes The FUS shall be able to deliver the payload in both multicast and unicast modes to the CPEs in the home environments. The description of the technical requirements in terms of this DVB document for these delivery mechanisms is given in clauses 6.5 and 6.6. In a managed environment the delivery s... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.3.1 Delivery failure in a managed environment | If a managed CPE is not capable of successfully completing a firmware file download an appropriate message returned on the CPE management interface may be used to inform the RMS of the problem, and it is the responsibility of the RMS to take appropriate action in these circumstances. Based on this message the RMS may i... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.3.3.2 Delivery failure in an unmanaged environment | The FUS may provide several locators with usage preferences either in the response to a query from a CPE or in the multicast announcement service. The CPE may make use of those alternatives if the first preference fails. Either multicast or unicast service options may be offered by the FUS. The operation of this mode d... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.4 Secure Message Exchange and Secure Network Time | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.4.0 Provisioning requirements | The following clauses describe the interoperation requirements for Secure Message Exchange and Secure Network Time. If authentication is required to set up a connection with the file server for either unicast or multicast, the CPE shall be provided with correct credentials. This provisioning may be done by one of sever... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.4.1 Secure Message Exchange | The Secure Message Exchange adopts the Transport Layer Security (TLS) specification [15]. The secure message exchange requirements are a function of the specific interface. The recommendation of the present document is that if the control interfaces, that is the Query Response Service (Interface 8) and the Remote Manag... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 5.4.2 Secure Network Time | The CPE and FUS should support secure network time using Network TimeProtocol v3. Note that the field that encodes the signature algorithm is carried in the NTP packet structure. The FUS and CPE shall synchronize against the network time through the NTPS:TCP:IP stack, [17]. The checksum of the protocol presumes the Mes... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6 The interfaces | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.0 Characteristics of interfaces | Thirteen interfaces are defined (shown in figure 5) as being relevant to the model, although some of these are not standardized by DVB. These are referred to by numbering (1 to 13) in figure 5. The specification of some of these interfaces is not in scope of the present document. Some interfaces, such as interface 5 fo... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.1.1 Payload coding and format | The CE manufacturer may choose to protect the firmware update file using a mechanism such as encoding or encryption in a way which is only known by the CPEs it is intended for. There shall be no requirement for the FUS to be able to access the information in the update file. 6.2 Interface 2 - Associated metadata from C... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.3 Interface 3 - CE manufacturer to RMS | This is a business to business (B2B) interface. To make it possible to manage the population of CPEs under its control the RMS shall have knowledge about the firmware update files which are available. This information delivery is not appropriate if an FUS-only mode is used, and the information provided shall be identic... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.4 Interface 4 - RMS-FUS control interface | As described in clause 6.3 the RMS will receive the same metadata from the CE manufacturer as supplied to the FUS. This will allow the RMS to control the managed CPEs for which it is responsible in terms of instructions to the FUS (Delivery Metadata) controlling the announcement service for that managed population and ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.1 Payload coding and format | Firmware update files which were originally provided by the CE manufacturer and prepared for delivery in the FUS shall be delivered to the population of CPEs through this interface. The format of the files is defined by the CE manufacturer. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.2 Security | The content (firmware update) should be protected by the CE manufacturer to avoid unauthorized use of such software. The transport stack for the interface is, in the absence of secure message exchange, the FLUTE:UDP:IP or DSM-CC:UDP:IP stack. Since the transport is multicast, the authentication of the message exchange ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.3 Delivery protocol | 6.5.3.0 Recommended protocols The recommended protocols shall be equivalent to existing content delivery protocols and those specified within developing IPTV standards. A DVB compliant FUS may implement packaging of the image and the use of an additional signature, for example as defined in TR-069 [6]. The metadata con... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.3.1 FLUTE | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.3.1.0 Introduction | This firmware download method is based on the FLUTE protocol [20] and derived from the DVB IP Datacast over DVB-H Content Delivery Specification [37], clause 5. The dynamic file delivery and Raptor FEC scheme defined in ETSI TS 102 472 [37] are not supported. FLUTE is built on top of the Asynchronous Layered Coding (AL... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.3.1.2 FLUTE session description in DVB IPI Firmware Update Service | The FLUTE specification [20] describes required and optional parameters for FLUTE session and media descriptors. They are provided by SDP over SAP. Annex D defines the SDP parameters used by RMS-FUS including FLUTE specific parameters. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.5.3.2 DSM-CC | The DSM-CC firmware download uses the DVB System Software Update service profile as defined in ETSI TS 102 006 [2]. The firmware updates are delivered via DSM-CC carousels in MPEG-2 transport streams as defined in ISO/IEC 13818-6 [3] and ETSI EN 301 192 [4]. For the FUS case the MPEG-2 transport streams are transported... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.1 Payload coding and format | The payload coding and format is up to the CPE manufacturer which provides firmware images to be used by the FUS both for multicast and unicast firmware delivery. Firmware update files which were originally provided by the CE manufacturer and prepared for delivery in the FUS shall be delivered to the population of CPEs... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.2 Security | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.2.0 Recommendations | The content (firmware update) should be protected by the CE manufacturer to avoid unauthorized use of such software. Authentication of the server and the client is recommended using the methods described in clause 5.4. The Customer Premises Equipment Wide Area network Management Protocol document (TR-069 [6]), which th... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.2.1 HyperText Transport Protocol (HTTP) | To authenticate the server, the CPE and the FUS should support the HTTP:TLS:TCP:IP stack. The CPE should support authentication of the package (or file) itself. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.2.2 File Transfer Protocol (FTP) | To authenticate the server for the message exchange, the CPE and the FUS should support the FTP:TLS:TCP:IP stack [34] and [35]. The CPE should support authentication of the package (or file) itself. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.2.3 Trivial File Transfer Protocol (TFTP) | There is no specification which covers only the TFTP:TLS:TCP:IP stack. If the CPE is to authenticate the server of the download, the CPE should adopt the same pragmatics as for the FTP:TLS:TCP:IP stack. The CPE should also authenticate the package or file as required. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.6.3 Delivery protocol | The present document will follow TR-069 [6] in terms of used protocols: HTTP, HTTPS, FTP, SFTP and TFTP. The CPE shall support both HTTP and HTTPs, which are optional for the FUS. A CPE shall support the use of SSL / TLS and shall use SSL / TLS when the file location is specified as an HTTPS URL. The CPE also support b... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7 Interface 7 - Firmware Update announcement service | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.0 Types of announcements | The announcement service is identified as interface 7 in figure 5. The announcement is used to enable the CPE to identify the appropriate firmware update files, if any, which are available for that device, the download methods and transport protocols which should be used. Each multicast announcement message delivered b... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2 Carriage of multicast announcement over SAP transport | 6.7.2.0 General The announcement message is based on coding and profiling a Session Description Protocol [26] message which is transported as Session Announcement Protocol [27] payload, therefore this clause does not describe the whole SAP and SDP protocols but only the profile which shall be used for the purpose of mu... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.1 Coding of Session Announcement Protocol | 6.7.2.1.0 Coding principles The Session Announcement Protocol (SAP) fields shall be populated as below in table 6. The function of the SAP message is to announce and describe the characteristics of the session within which the update descriptions are carried. Table 6: DVB RMS specific SAP coding Session announcement fi... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.1.1 Limitations | Due to the structure of the SAP encoding [27] there is no provision for carrying a message type identifier field in the SAP header, which would be available without parsing the SDP payload. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 38 |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.1.2 Authentication method to be used in SAP payload | The authentication data in SAP is defined in IETF RFC 2974 [27] as shown below in figure 9, its use is optional for µ RMS-FUS. Figure 9: Format of the authentication data in the SAP header If used the FUS profile for signing SAP announcements for firmware update is as follows: • The Version Number shall be set to 1 as ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.2 Payload coding of SDP header | The SDP structure describes the identifiers and characteristics of the actual update description session. A single SDP announcement session type is defined, which may be identified by a session name defined by DVB ("dvb-update"), shall be used to describe all the announcement message types. The session name may be used... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.3 Coding of media sections | Session Description Protocol (SDP) coding will be used for SAP multicast announcements as defined in the present document. The mechanisms for describing the payload are specified in IETF RFC 4566 [26] and profiled in clause 6.7.2.2. SDP uses media descriptions and attributes to describe the media sections, DVB will use... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.4 IP address range options | Since this service may have to operate in an open internet environment no specific restrictions are placed on the IP address ranges in the present document (additional to those in IETF RFC 2974 [27]) but it may be possible to consider optimizations to this problem in the longer term. The rules described in IETF RFC 297... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.2.5 Security | Encryption of the SAP messages is not supported. Authentication of the message exchange is recommended as defined in clause 6.7.2.1.2. Client authentication is not specified. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.3 Carriage over DVBSTP | 6.7.3.0 Coding principles DVBSTP may be used as one of the alternative methods of delivering the announcement messages, this clause describes the coding of the DVBSTP transport session header to carry out this task. The description of the DVBSTP coding should be assumed to be informative, with ETSI TS 102 034 [1], exce... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.3.1 Coding of DVBSTP | When the FUS announcement discovery information is carried using multicast delivery over a DVBSTP:UDP:IP transport the packet protocol defined in this clause shall be used. All values defined below shall be transmitted in normal IP network byte order (most significant byte first). ETSI ETSI TS 102 824 V2.1.1 (2016-04) ... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.3.2 Payload coding for DVBSTP | The present document extends ETSI TS 102 034 [1] in that the service over DVBSTP shall carry the RMS-FUS announcement messages, which consists of the RMS-FUS XML metadata schema which identifies the firmware updates. The RMS-FUS XML metadata carried as payload is described in annex B. The XML schema includes support fo... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.3.3 IP address options for DVBSTP | ETSI TS 102 034 [1] places no restrictions on the addressing, the present document will follow that specification in that sense. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.7.3.4 Security | Message encryption and authentication is not supported by DVBSTP. Neither client nor server authentication is specified. 6.8 Interface 8 - Query/response interface from FUS to home environment (QRC) |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.0 General | The query response channel (QRC) is a SOAP 1.1 [12] based interface where the server is the FUS and the client is the CPE. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 42 The interface is mandatory in the FUS for the FUS-only implementation but not required for the RMS-FUS mode implementation. It is optional for the CPE imple... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.2 Payload coding and format | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.2.0 Introduction | The remote procedure call (RPC) mechanism offered by SOAP 1.1 [12] is used for the bi-directional communication between the CPE and the FUS and the communication is always initiated by the CPE by using one of the methods specified in this clause. Communication between CPE and FUS is stateless. Therefore each response o... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.2.1 FirmwareUpdateCheck/FirmwareUpdateCheckResponse | The CPE invokes FirmwareUpdateCheck to ask the FUS whether new firmware is available for download, if no URL is returned it means that the CPE already has the latest available firmware version installed. By using the information in the RPC the FUS is able to narrow the choices of possible responses to the CPE. ETSI ETS... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.3 Security | The CE manufacturer and FUS shall use a standardized mechanism to authenticate each other before an operation is performed for either metadata (interface 2) or firmware update through this interface. Since the QRC interface is defined over the SOAP 1.1 [12] standard protocol, which is carried over HTTP packets, a secur... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.4 Delivery protocol | SOAP is the protocol which shall be used to deliver messages between the CPE (SOAP client) and the FUS (SOAP server) for the QRC interface. The SOAP implementations shall adhere to the interoperability requirements defined in the WS-I Basic Profile 1.0 [41] n order to guarantee the maximum interoperability, therefore S... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.8.5 Message back-off and retry strategy | In the event of contention when using unicast messages over the query/response channel (interface 8) some specified back-off and retry behaviour is necessary, as an example this may be a problem if a large population of CPEs all boot up at the same time and send "Inform" messages to the RMS. The strategy which unmanage... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.9 Interface 9 - CPE management interface | |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.9.0 Introduction | This interface shall support the functionalities described in clause 5.2.3, for the bi-directional communications between the RMS and the CPE. In annex A, the protocol TR-069 for remote management is profiled for purposes of interface 9. Other remote management methods may also be used with the present document, althou... |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.9.1 Management interface requirements | For TR-069 the message set (RPCs) for the Customer Premises Equipment (CPE) and the Remote Management Service (RMS) are described in clause 3.6 of TR-069 [6]. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.9.2 Security | The present document recommends SOAP encoded over HTTP:TLS:TCP:IP for secure message exchange. The ciphersuite recommendations are described in the security clause 4.5.1 of the present document. This is in alignment with TR-069 [6] as described in annex A. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.9.3 Delivery protocol | The present document recommends the SOAP over HTTP:TLS:TCP:IP stack for secure message exchange, compliant with the usage of SOAP [12]. The delivery of SOAP messages over HTTP using TLS is in alignment with TR-069 [6] as described in annex A. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.10 Interface 10 - RMS management and control | This is a business to business interface which is out of scope for the present document. 6.11 Interface 11 - FUS control interface and file management interface This is a connection which is internal to the FUS and is out of scope for the present document. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.12 Interface 12 - Update file streaming to delivery formatter | This is a connection which is internal to the FUS and is out of scope for the present document. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 46 |
e8615b1bed65e10867838531cab86eaa | 102 824 | 6.13 Interface 13 - RMS device registration | This is a connection which is internal to the RMS and is out of scope for the present document. |
e8615b1bed65e10867838531cab86eaa | 102 824 | 7 Data Model | The data model objects needed to define the requirements for and the management of DVB Content Download Service (CDS) have been developed and are described in annex E. These data model objects are generically applicable to any remote management data model. Although in principle a number of CPE management protocols migh... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 1 Scope | The present document shows the system behaviour of a TV-Anytime broadcast system with an interaction channel used for consumer response. The present document contains examples of how to use the TV-Anytime specifications both from static and dynamic viewpoints, i.e. it will highlight the parties involved in the processe... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 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. • ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 3 Definitions and abbreviations | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: retrieval of content advertising: content that is intended to promote or drive sales for products or services application: specific set of functions running on the PDR. Some applications use metadata, either automatically ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAF Advanced Authoring Format ACAP Advanced Common Application Platform AES Audio Engineering Society ARIB Association of Radio Industries and Businesses ATSC Advanced Television Systems Committee AV Audio-Visual AVI Audio-Visual Interface CA ... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4 TV-Anytime system architecture | A simple TV-Anytime broadcast system can be viewed as containing three major elements: a service provider delivering the TV-Anytime service, a transport provider that carries the service and a piece of equipment in the home that stores the content and plays it back at the consumer's request. The present document examin... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.1 Content referencing rationale | The purpose of content referencing (TS 102 822-4 [6]) is to allow acquisition of a specific instance of a specific item of content. For example, if a consumer sees an announcement on TV saying "there will be a new series on "Foxes in the cold" around Christmas", he may want to instruct his Personal Digital Recorder (PD... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.2 Phase 1 Metadata rationale | Users or user-agents want to choose programmes to watch or record. To make that choice they need information like what is the title of this programme, what is it about, who are the actors, is it sci-fi? On the other hand, programme makers want to attract users to their content, by providing similar information. That is... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3 Phase 2 Metadata rationale | |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.1 New content types | TV-Anytime Phase 2 supports new content types other than linear audio/video such as games, web pages, music files, graphics, data and many other applications. These new content types are treated on their own as non A/V programs and/or as components of a package (see the next clause). ETSI ETSI TS 102 822-2 V1.4.1 (2007... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.2 Packaging | TV-Anytime Phase 2 defines a technology called packaging (TS 102 822-3-3 [4]) that enables the combination of different types of content items such as games, applications and interstitial content with audio, video, still images and text, to create a new user experience. A package consists of a collection of content ite... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.3 Targeting | In brief, targeting (TS 102 822-3-3 [4]) can be defined as automatically matching and delivering relevant content to profiled consumers. There are two types of targeting, which are push targeting and pull targeting. In push targeting, broadcasters transmit content with associated metadata to be used in targeted substit... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.4 Interstitial content | TV-Anytime Phase 2 TS 102 822-3-4 [5] now targets more advanced concepts such as the ability to perform interstitial replacement at playback time based on a number of criteria. The criteria to be used for the control of what content should replace what, may be explicitly declared using the schemas defined within TS 102... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.5 Sharing | Once content or metadata is acquired it is natural to want to share it in a rightful manner. Users want to tell others about interesting content they have found, configure other devices so that they are personalized for them, and perhaps even transfer the content to other devices or other users. TV-Anytime Phase 2 spec... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.6 Remote programming | The purpose of remote programming (TS 102 822-9 [14]) is to allow the consumer to programme a recording of content from another device. For example, if the consumer is interested in two programmes which overlap in time and his PDR does not have the resources available to cope with this situation, the remote programming... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.7 Interchange data format | As illustrated in figure 4, the purpose of the Interchange Data Format specification (TS 102 822-8 [13]) is to allow the transfer of TV-Anytime metadata to a TV-Anytime compliant device from another device located in the non-TV-Anytime world. ETSI ETSI TS 102 822-2 V1.4.1 (2007-11) 18 Non TV - Anytime world TS 102 822-... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 4.3.8 Coupons | A coupon is a way to provide value in an electronic form, which can be used to complement / replace money, upon purchase of content. Coupons revitalize proven promotional techniques and deliver a competitive advantage to service providers who use them. TV-Anytime coupon metadata (TS 102 822-3-3 [4]) provides the way to... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5 TV-Anytime content referencing scenarios | The present clause introduces key concepts of content referencing, an extension of the static reference model introduced in clause 4 to model third party operation and possible scenarios of issuing and resolving references to items of content. |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.1 Content referencing key concepts | The key concept in content referencing (TS 102 822-4 [6]) is the separation of the reference to a content item - the CRID - from the information needed to actually retrieve the content item - the locator. The separation provided by the CRID enables a one-to-many mapping between content references and the locations of t... |
4389290176ce5e0b4b777e0b69a0227c | 102 822-2 | 5.2 Content referencing and unique content identification | Content referencing is the process of associating a token to a piece of content that represents its location where the content can be acquired. It is different from content identification, which creates an identifier that is the same regardless of its location. A content reference is the token that is used by the PDR t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.