hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 6.2 DVB URL resolution | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 6.2.1 Service identifier descriptor | Zero or more service_identifier_descriptors may be included in the SDT description of a service. Each such descriptor defines a single textual identifier for the service. The syntax of the textual service identifier is: <service_name> "." <service_provider_domain_name> where: <service_name> is a unique name for the ser... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 7 Application transport | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 7.1 Object carousel | This clause describes the protocol used when broadcast applications are transmitted using the DSM-CC User-to-User Object Carousels. The present document is based on the following specifications: • ISO/IEC 13818-1 [3] - MPEG 2 systems. • ISO/IEC 13818-6 [4] - DSM-CC. • ETSI EN 301 192 [2] - DVB specification for data br... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 7.2 HTTP | When applications are downloaded using the HTTP protocol, the HTTP 1.1 protocol shall be supported as defined in IETF RFC 2616 [5]. ETSI ETSI TS 102 809 V1.3.1 (2017-06) 63 |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 8 Synchronization | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 8.1 Introduction | The present document supports synchronization to video or audio streams in a service using DSM-CC stream events as defined in clause B.2.4. These can be either: • "Do-it-now" events as defined in clause B.2.4.2.2. These events are posted to the application as soon as they are received by the receiver. • Events synchron... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 8.2 Referencing | Two mechanisms are defined for referencing sources of stream events from applications: • By referencing a DSM-CC stream event object in an object carousel. This requires the service to contain an object carousel as well as the elementary stream carrying the stream event messages. • By referencing an XML file containing... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9 Protection | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.1 Introduction | If an attacker can cause a receiver to receive new or modified interactive applications and services, the attacker may have an opportunity to cause receiver behaviour that may be harmful to the receiver or the viewer. The protection scheme described in the present document allows a receiver to authenticate data for int... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.2 Scope | The present document specifies how to authenticate data in a Transport Stream, and specifically data pertaining to interactive applications and services. It does not specify if and when data in a Transport Stream is to be authenticated or not. This decision is intentionally left to the users of the present document. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3 Discovery, signalling and carriage of protection data | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.1 Overview (informative) | The data structures required for the verification of protected payload data are carried in MPEG private sections. These include certificate collection messages that are used by the receiver to establish one or more trusted public keys for verifying signatures, as well as authentication messages that contain signed hash... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.2 Discovery | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.2.1 Authenticating components of a service | Clause 9.3.3 defines the protection message descriptor which identifies the components of a service that carry protection messages. If the protection messages and the payload data being authenticated are carried by different components of a service, this descriptor shall be present in the ES info loop of the PMT for th... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.2.2 Authentication of interactive components of a service | When protection messages are used to authenticate components of an interactive service, they shall be carried by one or more of the service components that carry the signalling and data for the interactive service. Additionally protection messages may be carried by an additional service component however the present do... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.3 PSI signalling | The protection message descriptor (see table 40) provides a means to locate the components of a service that carry protection messages (defined in clause 9.4 and clause 9.5) and the components of the services that can be verified by these protection messages. When used it is carried in the ES_info loop of the PMT. The ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.4 Carriage | All protection messages defined in the present document are carried in private sections as defined in ISO/IEC 13818-1 [3]. The table_id shall be coded according to clause 5.1.3 of ETSI EN 300 468 [1]. The different protection message types with table_id 0x7B are distinguished by means of the table_id_extension field. T... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.5 Time parameters | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.5.1 Repetition rate of authentication messages | No maximum interval between authentication message sub_tables is specified in the present document. NOTE: The practical minimum interval will be a consequence of factors such as the size of the quarantine FIFO, the data rate of the transmission and the authentication latency acceptable for the application. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.3.5.2 Repetition rate of certificate collection | The sub_table that conveys the certificate collection for a service shall be repeated at an interval of no longer than 30 seconds. ETSI ETSI TS 102 809 V1.3.1 (2017-06) 67 |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4 Signing and verification | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.1 Overview (informative) | The authentication scheme uses authentication message sub_tables that carry a set of cryptographic hashes of payload sections. Each section in the authentication sub_table is cryptographically signed. If the authentication sub_table sections can be verified using a trusted public key (for example, obtained by means def... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.2 Verification procedure reference model | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.2.1 General verification principles | The present clause specifies the receiver reference model in detail. Receivers shall perform verification in a manner that achieves the same acceptance and rejection of sections as defined by the reference model. Receivers may otherwise deviate from this model provided that the performance constraints specified in clau... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.2.2 Verification of authentication sub_tables | Authentication sub_table sections in the buffer are processed as follows: 1) Signature verification occurs at a specified minimum rate (see clause 9.4.6). 2) If signature verification is unsuccessful, the section is discarded. Otherwise, the section hash information from the section is used to update the cache of trust... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.2.3 Verification of payload sections | As each payload section is received the time of reception for that section shall be recorded. Three separate triggers each result in a common set of steps being followed to process items in the FIFO. The triggers are: • a payload section is received (and is inserted in to the tail of the FIFO) • the cache of trusted ha... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.3 Authentication messages | The authentication information conveyed in authentication message sections allows a receiver to verify a payload section. They shall be coded according to table 42. Table 42: Syntax of the authentication message section Syntax Number of bits Identifier authentication_message_section() { table_id 8 uimsbf section_syntax... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.4 Performance enhancements (informative) | A receiver that can satisfy the reference model in clause 9.4.2 with the constraints in clause 9.4.6 will perform acceptably. The following illustrate some techniques that may allow the receiver to meet these requirements while using fewer resources with a typical broadcast signal. Observe if an arriving authentication... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.5 Transport Stream constraints | A Transport Stream carrying data protected according to the present document shall be constructed such that it can be verified by any receiver that implements the reference model specified in clause 9.4.2 using the minimum performance and sizing requirements specified for a receiver in clause 9.4.6. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.6 Receiver requirements | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.6.1 Overview | Imposing minimum requirements on receiver capabilities allows Transport Streams to be constructed so that every receiver which implements the mandatory provisions of the present document is capable of processing the Transport Stream, and achieve the intended protection. Therefore, all receiver implementations of the pr... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.6.2 Receiver minimum requirements | Table 46: Receiver minimum requirements Parameter Constraints Requirements signature_algorithm_identifier value in authentication message section At least algorithm 0x01 Receivers shall implement at least the signature algorithm(s) identified in this constraint. section_hash_length value in authentication message secti... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.4.6.3 Additional requirements | The present document only requires receivers to satisfy the minimum requirements defined in clause 9.4.6.2. External specifications may define one or more supersets of these minimum requirements. A non-exhaustive list of requirements that might be addressed by other documents includes the following: • Additional signat... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5 Trust management | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.1 Overview | This clause addresses how trust signalling provides the receiver with verification keys to enable data carried by protectable streams to be authenticated. Protectable streams are elementary stream signalled either 1) as defined in clause 5.3.2.1 of the present document or 2) as defined in clause 5.3.2.2 of the present ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.2 Establishing trust for stand-alone services | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.2.1 Introduction | This clause addresses the mechanism by which trust is established for individual services without requiring a coordinating entity. In this case trust is established by trust signalling being observed as present, coherent and stable on a service for a "probation" period. This provides the receiver with a verification ke... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.2.2 State machine | Figure 2 shows the state diagram for how trust is established and maintained for a stand-alone service. At a high level these states enable two modes of operation: • Green box - trust has been established (a trusted verification key is stored) and application authentication is possible. The receiver shall apply the pro... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.2.3 Measuring probation and timeout periods | When the trust status of a service changes to either the probation or loss of authenticated trust signalling states or when a change in the trust signalling is detected while in one of those states, the receiver shall persistently store a copy of the candidate new trust signalling (if any) and the current time. NOTE: W... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.2.4 Behaviour while trust has yet to be established | The present document defines default behaviour for the states B and C that depends on whether a receiver modifies its channel list in reaction to NIT/SDT changes immediately the change is detected or only after the receiver is put in to standby. If the receiver does not immediately modify its channel list in reaction t... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.3 Coordinating entity assists establishing trust (optional) | A coordinating entity is an external trust anchor that is trusted by a device without any service specific trust signalling. Trust signalling that includes one or more certificate chains that depend on a coordinating entity shall also be constructed to support the stand-alone model described in clause 9.5.2 as illustra... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4 Trust messages | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.1 About certificate chains (informative) | Figure 3 shows an example of a public key certificate. The certificate payload is an electronic document that provides a public key (the "subject public key") associated with various other items of information. The certificate signature allows the integrity and authenticity of the certificate payload to be cryptographi... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.2 Succession of certificates | From time to time public keys will need to be replaced to maintain security. The cryptographic parent/child relationships within a certificate chain allow the chain to be verified but cannot prove that the certificates are current. In environments where keys are to be distributed via a unidirectional channel (such as b... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.3 Security considerations (informative) | This clause briefly summarizes some of the assumptions and intentions behind the solution described in the present document and is intended to help readers understand how the system can be used to its best effect. The present document makes the following assumptions about keys and certificates: • It is assumed that the... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.4 Certificate properties and configurations | Each certificate includes the keyUsage field as described in clause 9.5.4.10.3. The value of this field controls how the subject public key contained in a certificate can be used. Receivers shall only use public keys according to the key usage of their respective certificates. The present document defines the keyUsage ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.5 General certificate collection construction rules | Each certificate collection message shall carry a collection of certificates belonging to a single DVB service. Each collection shall contain all the certificates needed to build at least one valid certificate chain but may contain additional certificates that enable the construction of alternative chains ascending to ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.6 Certificate collection construction rules for stand-alone services | This clause illustrates a range of valid certificate collections. Figure 8 illustrates the minimum scenario where a single certificate is both the self-signed manager certificate used by the receiver as a trust anchor and also provides the public key used to verify the authentication messages. Figure 8: Minimum scenari... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.7 Certificate chain construction assisted by a coordinating entity (optional) | Figure 11 illustrates variants of the examples in clause 9.5.4.6 where a coordinating entity is additionally available to provide an alternative trust anchor. Here certificate (B) is the verification key certificate. The authority key id of certificate (B) indicates that it can be verified by pubkeyA. Two certificates ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8 Signalling in the Transport Stream | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8.1 Overview | The certificate collection message (see clause 9.5.4.8.5) shall always carry a certificate containing the current verification key (except when trust termination is being signalled as described in clause 9.5.4.8.4). This certificate can either be a self-signed manager or a verification key certificate as described in c... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8.2 Encoding the certificate collection | This clause defines the rules for encoding the certificates carried by the certificate collection message. Each certificate collection message (see clause 9.5.4.8.5) shall carry a set of certificates. The following rules shall apply: a) There shall be exactly one valid current manager certificate. The successor referen... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8.3 Updating the certificate collection | This clause defines the rules for encoding changes to the set of certificates that enable the receiver to determine if a modified certificate chain is a legitimate successor to the current certificate chain. Different mechanisms apply to the manager certificate and other certificates. These rules apply in addition to t... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8.4 Terminating the trust signalling | In addition to being able to establish trust in a service the present document also enables services to signal the termination of their trust signalling in a secure way. In order to do so, a service shall broadcast a trust termination certificate with the successorKeyId set to the key id of its own subject public key. ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.8.5 Certificate collection message | There shall be a single certificate collection message for each protected service. This shall be conveyed in a single sub_table. Each sub_table shall contain a collection of certificates encoded according to clause 9.5.4.8.2. The table shall be coded according to the table 51. NOTE: Receipt of the trust collection mess... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.9 Certificate ordering within certificate collection | One or more certificates may be placed within each certificate message section, and the complete certificate collection may be distributed over one or more sections. Regardless of how the certificates are divided between sections, if more than one certificate is present, the ordering shall comply with the requirements ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10 Certificate encoding | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10.1 Overview | In the present document certificate syntax is specified using Abstract Syntax Notation ASN.1 as specified in Recommendation ITU-T X.680 [29] and encoded using the distinguished encoding rules (DER) as specified in Recommendation ITU-T X.690 [30]. This present document uses structures devised for the representation of c... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10.2 DVBCertificate syntax | The syntax of the DVBCertificate is summarized in table 52. Each DVBCertificate shall always contain every field listed in table 52. Table 52: Elements of the DVBCertificate Field Name Field Type tbsDVBCertificate TBSDVBCertificate signatureAlgorithm AlgorithmIdentifier signature BIT STRING Semantics of fields of DVBCe... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10.3 TBSDVBCertificate syntax | The syntax of the TBSDVBCertificate is summarized in table 53. Each TBSDVBCertificate shall always contain every field in this table except for the successorKeyID field, which is conditionally present as described in clause 9.5.4.4, and the optional extensions field. Table 53: Elements of TBSDVBCertificate Field Name F... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10.4 TBSDVBCertificate extensions | The present document defines one extension for the certificates defined in clause 9.5.4.10.3. ext-URL: This extension conveys a universal resource locator (URL) and a label that identifies the purpose of the URL carried by the extension. Zero or more such extensions may be present in a certificate. The purpose of this ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.4.10.5 Computing and comparing key identifiers | In the present document key identifiers shall be computed as the SHA-256 (as specified in FIPS 180-4 [23]) of the value of the BIT STRING subjectPublicKey (excluding the tag, length, and number of unused bits). The portion of the result of the SHA-256 stored in the key identifier field depends on the context in which i... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5 Device behaviour | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.1 State stored when trust is established | For each DVB service when trust is established the receiver shall store at least the information from the certificates in the certificate chain in which trust has been established (according to the state machines in clauses 9.5.2, 9.5.5.1 and 9.5.3). NOTE: When trust is anchored in a self-signed manager certificate the... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.2 Verifying that a certificate chain is coherent | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.2.1 Common rules for certificate chain verification | The receiver shall first verify that the ordering of certificates within the certificate collection is as specified in clause 9.5.4.9. Next the receiver shall attempt to locate the certificate containing the verification key within the certificate collection. This can either be done by searching for a key that matches ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.2.2 Receivers without coordinating entity certificates | Where a receiver has no coordinating entity certificates installed that apply to the service carrying a certificate chain, a certificate chain is considered verified when it meets the common rules specified in clause 9.5.5.2.1 with the certificate a chain leading to a self-signed manager certificate. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.2.3 Receivers with coordinating entity certificates (optional) | Where a receiver has one or more coordinating entity certificates installed that apply to the service carrying a certificate chain, a certificate chain is considered verified when it meets the common rules specified in clause 9.5.5.2.1 with the certificate chain leading to at least one designated coordinating entity an... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 9.5.5.3 Verifying succession of certificate chains anchored in a manager certificate | For a receiver to verify whether or not a new different certificate chain is a valid successor to the certificate chain in which trust is currently established the receiver shall do the following: 1) Verify the new certificate chain according to the rules in clause 9.5.5.2. ETSI ETSI TS 102 809 V1.3.1 (2017-06) 97 2) I... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 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... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 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... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 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... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 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. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 3 Definitions and abbreviations | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: process of retrieving selected content application: specific set of functions running on the PDR NOTE: Some applications use metadata, either automatically or under consumer control. authority: organization that generates ... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CRID Content Reference IDentifier NOTE: An identifier for content that is independent of its location specified by TS 102 822-4 [7]. FTP File Transfer Protocol HTTP HyperText Transfer Protocol IMI Instance... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 4 Remote PDR access | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 4.1 Remote PDR programming (metadata delivery) | There is a desire to be able to remotely control a PDR, primarily to allow remote booking of recordings. Remote booking will enable a user to program their PDR from their office PC, from their mobile, whilst on holiday etc. In addition it will also provide a mechanism for a metadata provider to recommend programs to be... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 4.1.1 Remote PDR programming by e-mail | Internet Laptop computer PDA Mobile Phone PDR E-Mail SMS/E-Mail E-Mail Network Relay Service PDR Propriatory Protocol E-Mail Server Figure 1: Architecture The e-mail shall conform to RFC 822 [23]. The Subject line shall contain the CRID [7] or CRIDs to be recorded. When multiple CRIDs are provided they shall be separat... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 4.1.2 Other remote PDR programming solutions | Other mechanisms may be considered to program a PDR from a remote device and location (e.g. a Web site or an SMS service) that are not defined in the present document. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 4.2 Remote PDR management | Although certain remote PDR management functions such as "list content", "search", "delete", "show recording list", "transfer content to and from another device" are useful, the present document only defines the "recording request" function and the "related status request" function. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5 NDR operation | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.1 NDR remote programming scenarios | The use of an NDR is of interest in a number of situations where: • the end-user is outside their home with no possibility to access his home PDR; • content the end-user is interested in, is out of reach of his PDR (content broadcast on a channel not delivered to the end-user's receiver, conflict between recording requ... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2 NDR control service and transport | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.1 Introduction | The following service description is based on the "NDR Service operation and transport" structure defined in TS 102 822-6-1 [10], and on the "NDR Service discovery" mechanisms defined in TS 102 822-6-2 [11]. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.1.1 Types and Functionalities of NDR services | TV-Anytime NDR services specified are all request-response based. The network transaction is always point-to-point (client to server), and the transaction is always initiated by the client. NDR control: NDR control occurs when a client wishes to record broadcast content. For the TV-Anytime control_NDR operation that is... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.1.2 NDR service capability descriptions | In order to exploit usefully the NDR service described in the previous clause, the client needs information about the nature of the NDR service being offered. This is because different NDR services will provide different functionalities and optional features. For example, some NDR services may offer just content record... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2 NDR service types | TV-Anytime defines one type of NDR web service, which can be thought of as a remote procedure with a well-defined set of inputs and outputs and a well-defined behaviour. In WSDL [20] terminology, this remote procedure is known as an "operation" (see annex A). The NDR control operation is called the control_NDR operatio... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.1 "control_NDR" operation | The control_NDR operation allows a client to query a server in order to control the hosted NDR function. The following list gives a few examples of the types of functionality that a TV-Anytime NDR provider can offer using a control_NDR operation: • operation that takes a certain channel and a command Record to get the ... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.2 Request format | The request format allows the client to specify four types of commands. The semantics and structure of these commands are explained in more detail in clause 5.2.2.3. <complexType name="Control_NDRType"> <choice> <element name="RecordRequest" type="ndr:RecordRequestType"/> <element name="RecordStatus" type="ndr:RecordSt... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.3 RecordRequest parameters | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.3.1 Introduction | The RecordRequest command may contain a number of parameters to allow several types of record request: • a record request for the content currently broadcast on a channel (no ContentId element); • a record request for future broadcast content (all elements may be needed); • any record request may include a request for ... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.3.2 RecordStatus parameters | When a PDR or end-user wants to know if a previously accepted record request is completed or not, it issues a RecordStatus command, as follows. <!-- ########### Schema of the status of a record request ########### --> <complexType name="RecordStatusType"> <attribute name="requestId" type="string" use="required"/> </com... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.3.3 RecordCancel parameters | When a PDR or end-user wants to cancel a previously accepted record request, it issues a RecordCancel command as follows. <!-- ########### Schema of the cancel of a record request ########### --> <complexType name="RecordCancelType"> <attribute name="requestId" type="string" use="required"/> </complexType> </schema> Na... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.3.4 RecordListRequest parameters | When a PDR or end-user wants to know the list of previously accepted record requests which he generated, it issues a RecordListRequest command, as follows. <!-- ######## Schema of the list of previously accepted record requests ######## --> <complexType name="RecordListRequestType"> <sequence> <element name="Subscripti... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.4 Response format | A control_NDR response to a request contains a TVAMain XML instance document specific to each request. <complexType name="ControlNDRResultType"> <choice> <element name="RecordRequestResult" type="ndr:RecordRequestResultType"/> <element name="RecordStatusResult" type="ndr:RecordStatusResultType"/> <element name="RecordC... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.4.1 RecordRequestResult parameters | <!-- ########### Description of the response to a record request ########### --> <complexType name="RecordRequestOKType"> <sequence> <element name="RequestId" type="string"/> <element name="Time2Call" type="dateTime"/> <element name="RecordingCharge" type="tva:PriceType" minOccurs="0"/> <element name="ConservationDelay... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.4.2 RecordStatusResult parameters | <!-- ########### Description of the response to a record status request ######### --> <simpleType name="FailureType"> <restriction base="string"> <enumeration value="unknownRequest"/> <enumeration value="cancelledBroadcast"/> <enumeration value="cancelledByNDR"/> </restriction> </simpleType> <complexType name="RecordSt... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.2.4.3 RecordCancelResult parameters | <!-- ########### Description of the response to a cancel request ########### --> <simpleType name="RecordCancelResultType"> <restriction base="string"> <enumeration value="unknownRequest"/> <enumeration value="OK"/> <enumeration value="removedAfterRecording"/> </restriction> </simpleType> Name Definition RecordCancelRe... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.