hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7 Content Move operation | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.1 Introduction | The CPCM Content Move protocol shall be used for all cases where a CPCM Content item is Moved between CPCM Devices. The Content Move Protocol actually consists in Content Licence Moving. Encrypted Content may actually be copied without any restriction and without violating the USI as long as one single instance of the ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.2 Source CPCM Instance behaviour with Content Move | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.2.1 Content Handling Behaviour | A CPCM Instance that needs to Move a Content Licence to another CPCM Instance shall behave as depicted in figure 42: • First, the Device Application is asked to confirm that it wishes to Move the Content Licence. • Assuming the confirmation succeeds, the Source CPCM Instance sends a move_CL_begin_message to the CPCM In... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.2.2 Security control behaviour | The Security Control is involved at four steps during the CL Move Protocol which shall be executed in the following order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop. 1) After the move_CL_begin_message is sent, it will accept the challenge to r... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.3 Sink CPCM Instance behaviour with Content Move | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.3.1 Content handling behaviour | In order for a CPCM Instance to receive a CL through a Move protocol, the Sink CPCM Instance shall perform the following tasks as depicted in figure 43. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 179 Ask Appli To Confirm Confirmed Not Confirmed Move CL Ready Move CL Commit Secured Rollback No Response Rollback Move CL Con... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.3.2 Security control behaviour | The Security control is active at three stages. These steps shall be conducted in the order described below, if there is a failure at any stage it shall be reported as a protocol error and the process shall end. 1) The Content Handling requests its Security Control to prepare for the Move. To that end, the Security Con... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.4 Abnormal behaviour | In the normal course of events, assuming that no CPCM protocol message time-out occurs, when a requesting CPCM Instance sends a message to another CPCM Instance the responding CPCM Instance shall always respond with a message type corresponding to that of the request. Many possible errors are not taken into account: e.... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.7.5 Failure recovery | The Content Move protocol has been designed to be able to restart and finish successfully if it is unexpectedly interrupted (e.g. because of a power failure or a network problem that makes one of the two peers unreachable). NOTE: There is a risk that CL may be lost during and after the interruption if the Instances suf... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.8 CPCM Content Revocation | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.8.1 General | The CPCM System includes two distinct modes of CPCM Content-based revocation - per CPCM Instance, and per AD. CPCM Content revocation is performed by storing the CIC identifiers of the revoked CPCM Instances, and/or the ADS digest of the revoked ADs, for a particular CPCM Content item, within a CPCM Revocation List, th... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.8.2 CPCM Instance-based Content revocation | The CPCM Content Licence structure (see clause 5.4.4) contains the field C_and_R_regime_mask, which is an 8-bit mask that also implies for which of the eight possible C&R regimes a revocation check is to be performed for the associated CPCM Content item. CPCM Instance-based content revocation checks can be applied in t... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.8.3 AD based Content revocation | An AD may be revoked if its associated AD Secret becomes compromised and could therefore be misused to make CPCM Content bound to that AD usable outside the envisaged confines of the AD. An AD to be revoked is identified in the CPCM Revocation List by the digest (computed using Hash function described in TS 102 825-5 [... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.9 CPCM Content interoperability between C&R regimes | CPCM Instances shall not handle CPCM Content that is not covered by a CPCM Compliance and Robustness (C&R) regime that is supported by that CPCM Instance. Individual C&R regimes may allow the inclusion of coverage of CPCM Content from other C&R regimes but this is out of the scope of the CPCM specification and, if appl... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8 CPCM Content Licence management | 8.1 General This clause specifies how CPCM Content Licences (CL) are managed throughout the lifetime of the associated Content items within the CPCM System. A Content Licence is generated when a Content item is Acquired, but a new CL can also be generated upon Storage or Processing of an existing Content item. CL gener... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2 CPCM Content Licence generation | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1 CL generation upon Content Acquisition | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.1 General | A unique Content Licence shall be created upon Acquisition of each CPCM Content item from a Trusted Source in the CPCM System or upon Re-Acquisition of a Content Licence (see clause 8.5). To be able to generate a Content Licence, the CIC of the CPCM Instance hosting the Acquisition Point shall not have expired. The CPC... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.2 CPCM version | The CPCM_version field shall be set to the same value as that stored in the CPCM Instance Certificate of the Acquisition Device. The value 0x01 shall be applied for CPCM Instances that comply with the present specification. If the Content Licence is to be provided to a CPCM Instance that implements an earlier CPCM Syst... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.3 Content Licence protection | The content_licence_protection bit in the CL shall be set according to the mode of protection applied to the Content Licence by the Acquisition Point, as specified in clause 5.4.4. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.4 Descrambler information | The odd_even_indicator bit shall initially be set to indicate that the even key is applied, i.e. set to the value "0". This value is changed only if the Acquisition Point applies a change of the CPCM scrambling key. The generic process for such a change of scrambling key is specified in clause 7.6.2. How this generic p... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.5 Content Licence identifier | The Acquiring CPCM Instance shall allocate a Content Licence identifier (CLID) for each new Content item that it introduces into the CPCM System. The CLID shall be unique within the CPCM System, i.e. two Acquisition Points within the CPCM System shall not be able to generate the same CLID for different Content Items. H... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.6 Content Licence creator | The content_licence_creator field shall be set to the CIC Identifier of the CPCM Instance Acquiring the Content item. The content_licence_creator field of a CL shall not be changed by any CPCM Instance after it has been set by the CPCM Instance that Acquired the Content item. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.7 Last CL issuer | This field shall be set only when the Content Licence is protected using the AD Secret (i.e. not under the direct protection of SAC secret, see clause 8.6.1) and if needed, according to the USI settings of the Content item (see TS 102 825-10 [9]). Otherwise the use of this field is optional. If used, it is set to the C... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.8 C&R regime mask | The C&R regime mask field shall be set to the value as authorized by the delivery system of the associated Input Content item. If no value is given by the delivery system, it shall be set according to the C&R regime mask field in the CIC. If the Acquisition CPCM Instance has more than one CIC then apply the logical OR ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.9 RL index list | This field shall be populated for each of the C&R regimes asserted in the C&R regime mask in the following way: • The value delivered by the delivery system, if any; • Otherwise, the index of the most recent Revocation List known to the Acquisition Point. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.10 Authorized Domain identifier | If the Input Content is required to be bound to an AD then the Authorized Domain identifier (ADID) field in the Content Licence shall be set to the ADID of the AD to which the Acquiring CPCM Instance belongs. If the Acquiring CPCM Instance is not AD aware then the ADID field shall be set to zero. If the CPCM Instance i... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.11 Descrambling key | The CPCM Content descrambling_key shall be set to a random value, or to a value assigned by the delivering CPS. If the Content item is not to be scrambled with the CPCM Scrambler then the descrambling_key shall be set to zero. The C&R regime may set a maximum time period for the validity of a single CPCM Content descra... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.12 Usage State Information | The Usage State Information (USI) shall be set according to the requirements of the Input Content. Such settings are totally at the discretion of the content provider on a per Content item basis. Where standards exist for relevant content usage rules signalling in other systems, there can also be standardized mappings ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.13 CPCM Auxiliary Data digest | This field is present only if there is any CPCM Auxiliary Data (identified in the CPCM Content) associated with the Content item. This field is the digest of the CPCM Auxiliary Data, computed using the hash function defined in TS 102 825-5 [7]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.14 AD Secret Signature | This field is present only when Content Licence is self-protected using AD Secret. It is computed as the Message Authentication Code (see TS 102 825-5 [7]) of all other fields of the CPCM Content Licence. AD Secret signature computation is part of the Content Licence protection process (see clause 8.6). |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.1.15 CPCM Auxiliary Data | The Acquiring CPCM Content Instance may create CPCM Auxiliary Data in one of the following cases: • MGAD or VGAD is asserted in the Content Licence, and a geographical region is given. In that case, CPCM Auxiliary Data will carry the associated geographic region. NOTE: If MGAD or VGAD is asserted and there is no associ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2 CL generation in other cases | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.1 General | A Content Licence may also be generated in the following circumstances: • When the Content Licence protection mode is changed (see clause 8.6). This can occur as a result of CPCM Storage or Processing or when the Content Licence is exchanged between CPCM Instances (see clause 8.6.3); NOTE: Transitions between SAC Secre... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.2 Content Licence protection | The content_licence_protection bit may be changed if the CPCM Instance handling the Content Licence change the Content Licence Protection. The settings of the content_licence_protection bit are described in clause 5.4.4. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.3 Descrambler information | This field may be changed when a Processing Entity changes the scrambling keys or crypto-periods are suppressed from the Content item (see clause 7.6.2). The odd_even_indicator bit shall initially be set to indicate that the even key is applied, i.e. set to the value "0". This value is changed only if the Acquisition P... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.4 Content Licence identifier | This field shall be updated when creating a new Content Licence as described in clause 8.3. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.5 Last CL issuer | This field shall be updated only when the Content Licence is transmitted under the sole protection of the AD Secret (i.e. not under the direct protection of SAC secret). It shall be set to the value of the CIC Identifier of the CPCM Instance generating the Content Licence. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.6 Authorized Domain identifier | This field shall be updated under two circumstances as described in clause 8.6.3: • When the Content item becomes bound to a different AD. In this case ADID shall be set to the value of the ADID of the new AD. • When the Content item ceases to be bound to an AD. In this case the ADID shall be set to zero. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.7 Descrambling key | This field may be updated by Processing or Storage Entities. The new value of CPCM Content descrambling_key shall be set to a random value. The C&R regime will set a maximum time duration during which a single descrambling key may be used. After that time, a new descrambling key shall be set to a random value and corre... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.8 Usage State Information | This field may be updated by CPCM Instances that host an Acquisition Point or a Storage Entity. It might also be updated by a CPCM Instance hosting a Processing Entity under conditions dictated by the C&R regime. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 188 |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.9 CPCM Auxiliary Data digest | This field is present only if there is any CPCM Auxiliary Data (identified in the CPCM Content) associated with the Content item. This field is the digest of the CPCM Auxiliary Data, computed using the hash function defined in TS 102 825-5 [7]. Thus, this field must be updated when CPCM Auxiliary Data are modified. CPC... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.10 AD Secret Signature | This field is updated if the Content Licence is under the direct protection of the AD Secret and if any other field has been changed in the Content Licence. It is computed as the Message Authentication Code (see TS 102 825-5 [7]) of all other fields of the CPCM Content Licence. Computation of the AD Secret signature is... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.2.2.11 CPCM Auxiliary Data | CPCM Auxiliary Data shall be updated with the relevant CLID value when the Content Licence CLID has changed. When present, CPCM_extension_data or private_extension_data may only be changed by CPCM Instances implementing the corresponding extension and if permitted by the extension specification. When present, CLC_exten... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.3 CPCM Content Licence identification | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.3.1 General | The CPCM System manages CPCM Content Licences independently of the Content items to which they apply. This gives the benefit of CPCM more easily being able to interoperate across several home network ecosystems, but it necessitates that the CPCM System ensures that every CPCM Content Licence is uniquely identifiable. T... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.3.2 CIC Identifier (only) | In this scheme the pre-allocated part of the scheme-specific Content Licence identifier consists of the CIC Identifier of the Acquiring, Processing or Storing CPCM Instance, and is thus 8 bytes in length. The freely allocatable part is the remaining 7 bytes. This CLID allocation scheme is depicted in figure 45. ETSI ET... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.3.3 ISAN | In this scheme the pre-allocated part of the scheme-specific Content Licence identifier consists of the ISAN of the Input Content item, and is thus 12 bytes in length. The freely allocatable part is the remaining 3 bytes. This CLID allocation scheme is depicted in figure 46. Figure 46: CLID allocation scheme for ISAN |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.3.4 Truncated ISAN | In this scheme the pre-allocated part of the scheme-specific Content Licence identifier consists of the truncated ISAN of the Input Content item. Truncated ISAN consists in the first 8 bytes of the ISAN, what corresponds to the ISAN without the version number. The freely allocatable part is the remaining 7 bytes. This ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.4 CPCM Content Licence verification | When receiving a Content Licence, a CPCM Instance shall perform the following process: • Verify that its certificate and the one of the CPCM Instance from which the content has been received (when the CL is SAC protected) have not expired; • Verify that it knows the Content Licence version; • Verify the length is consi... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.5 Content Licence re-Acquisition | The CPCM System includes a mechanism whereby a CPCM Instance that has already obtained a CL for a Content item is able to request the CPCM Instance that Acquired that Content item to provide a new CL, for example to obtain extended Authorized Usage for the Content item from the appropriate AAA. A basic framework for in... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.6 Content Licence protection | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.6.1 CL protection modes | CPCM Content is always bound to some entity, either to an AD, or to the Source CPCM Device, or to the Destination CPCM Device, or to the SAC session between the Source and Destination CPCM Devices. The Content Licence can require one of the following three types of protection, which in turn protects the USI contained w... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.6.2 CL protection mode usage | Content Licence protection modes shall be applied in accordance with the following rules: • AD secret and SAC key protection shall be applied if content propagation occurs within the same AD and at least one other USI (i.e. USI that is not a Propagation control USI) requires SAC key protection; • AD secret protection s... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 8.6.3 CL protection mode changes | When Content is Copied or Moved (under the control of the USI) from one Source Instance to another Destination Instance, the protection mode of the Content Licence may vary as follows: • If Content is Moved between CPCM Instances that are members of the same AD, then the protection method may change between the differe... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 1 Scope | The present document is part 4 of multi-part deliverable "TS 102 822 series" 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 which is implementable for compliant ... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 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... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [2] IETF RFC 1591: "Domain Name System Structure and Delegation". [3] IETF RFC 2616: "Hypertext Transfer Protocol - HTTP/1.1". [4] IETF RFC 1945: "Hyperte... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 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. |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 3 Definitions, abbreviations and conventions | |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: retrieval of content authority: organization that creates CRIDs capture: storing the acquired content (e.g. to local storage) ETSI ETSI TS 102 822-4 V1.7.1 (2012-12) 9 content: anything the viewer would like to access (mov... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CGI Common Gateway Interface CRID Content Reference IDentifier DNS Domain Naming System DVB Digital Video Broadcasting EPG Electronic Programme Guide IP Internet Protocol IPR Intellectual Property Rights LR Location Resolution MX Mail eXchange... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 3.3 Conventions of specification syntax | Within the present document, syntax is defined for various textual items. Items in bold are textual characters that shall be used exactly as specified. Items in <angle brackets and italics> are replaced by a suitable value, which is specified beside the syntax definition. An item in square brackets ("[" and "]") denote... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 4 Introduction | The purpose of content referencing 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 of "The Agatha Christie Murder Mysteries" next year", he/she may want to instruct their Personal Digital Recorder (PDR... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 5 Key concepts and features | The content referencing process begins after a content item has been selected by a consumer through to, but not including, the actual acquisition of the desired content item. In figure 5.1 the scope of the content referencing process is shown. Some parts outside the scope of content referencing are included in figure 5... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 6 Location resolution | Location resolution is the process of translating a CRID into other CRIDs or locators. Location resolution involves mapping a location-independent content reference (the CRID) to its location in time (e.g. scheduled transmission time in a broadcast system) and space (e.g. TV channel, IP address). In the context other p... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 7 The authority | An authority, as defined in the present document, is the body that creates a CRID, which they guarantee to be unambiguous. An authority will also provide the ability for the CRID to be resolved into locators or other CRIDs. The CRID shall ultimately be resolved either directly by the CRID authority or by another party.... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 8 CRID | A CRID is the output of the search and selection process and is an unambiguous identifier that refers to a piece of content, however multiple CRIDs may refer to that same piece of content. It is permissible for a CRID to resolve into one or more other CRIDs. This CRID to CRID functionality can be used for two purposes:... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 9 Locators | An instance of content may be located on various media such as local storage, live broadcast stream, data broadcast stream, data file on the Internet and data stream via the Internet. A locator specifies a location, and possibly time of availability, where a content item can be acquired. There will be many formats of l... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 10 Instance metadata identifiers | TS 102 822-3-1 [10] and TS 102 822-3-2 [11] provide the ability to describe specific instances of content. Whilst TV-anytime created the CRID for location independent selection of content, it recognizes that there will be occasions where the consumer may wish to acquire a location dependent version of a piece of conten... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 11 Resolving Authority Record (RAR) | The Resolving Authority Record (RAR) is an essential element in the location resolution process for both the unidirectional and bi-directional networks. It provides the information needed for retrieving the location resolution data for a given authority. Each resolution authority will require one or more resolving auth... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 11.1 Contents of Resolving Authority Record | The present document does not define a transmission format for the RAR in uni-directional networks. The present document does however define the information that shall be carried by the encoded RAR. A transmission format is specified for the bi-directional content referencing process over TCP/IP, which is given in clau... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12 Protocols for location resolution | |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.1 Common features and interfaces | This clause defines the features common to location resolution using unidirectional or bi-directional networks. It is included here to provide a context for the details that follow in clauses 12.2 and 12.3, and provides the descriptions of the terms that will be used in these clauses. |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.1.1 Resolution handler | In the TV-anytime environment, content referencing services can be delivered through various delivery systems such as IP networks or broadcast TV. Figure 12.1 shows the concept of a modular resolution system, with multiple resolution handlers as required for specific location resolution transport mechanisms. ETSI ETSI ... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.2 Location resolution over unidirectional networks | This clause of the present document defines the common features of resolution handlers that work with unidirectional networks. Each resolution handler using a unidirectional network will have a dynamic behaviour similar to the one given in the flow chart figure 12.2. CRID Authority known Authority to URL (of resolving ... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.2.1 Guidance on use of resolution status flags | CRIDs that when resolved translate into one or more CRIDs, with the acquisition directive of "all" and have the resolution complete flag set to "no" can be used for grouping of content that changes over time, for example a TV series. Such a group CRID may continue with its resolution complete flag set to "no" for a lon... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3 Location resolution over bi-directional networks | In order for a PDR to use the location resolution services over bi-directional networks it is necessary to define a protocol to allow the PDR to initiate a connection and then transfer requested data between itself and a resolution service located at a remote server. This clause specifies how a PDR can discover the loc... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.1 Generic bi-directional resolution server discovery | This discovery stage may not be required by all network implementations. Given a CRID to resolve, the first step is to find a server that might be able to resolve this CRID. The process of server discovery is based on using the authority name from the CRID. The present document makes the assumption that the CRID the PD... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.2 Generic bi-directional request to resolution server | Once the resolution server has been discovered, the next step is to communicate with this resolution server. The inputs to the server will be a list of one or more CRIDs to resolve, and optional flags to specify how the response should be created. The TV-anytime defined optional flags are: 1) SubmittedCRID. 2) Result. ... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.3 Generic bi-directional response from resolution server | The resolution server will respond with one of three possible types of information: 1) The result from resolving the CRID. The response will contain instance(s) of XML schemas defined in TS 102 822-3-1 [10] and in annex A of the present document. The permitted response schemas are listed later in this clause. 2) A Reso... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.4 Dynamic behaviour of PDR and location resolution server | For the case where the PDR is connected to a bi-directional network there is a need to specify some aspects of the dynamic behaviour of location resolution requests in a TV-anytime compliant PDR. This is required in order to avoid large numbers of PDRs all trying to contact the same location resolution server at the sa... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.4.1 Requirements for PDR dynamic behaviour | 1) When the date and time for re-resolution arrives, the PDR shall wait a further random amount of time before contacting the location resolution server. This is required in order to reduce the chances of the location resolution server being swamped by many PDRs contacting it at the same moment in time. 2) If the locat... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.5 TCP/IP based resolution server discovery | As the <DNS name> part of the authority name is a name that is a registered Internet domain name, the mechanisms defined for DNS name lookup can be used as part of the server discovery phase. Client (PDR) LR server CRID Authority name Host name of LR server CRID Locators or CRIDs Location resolution process LR server s... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.5.1 Internet service discovery query (RFC 2782) | RFC 2782 [6] provides an expansion of the DNS (see RFC 1591 [2]) system that is used to allow Internet connected machines to find mail servers. In addition to being able to search for Mail eXchange (MX) records, it is also possible to Search for seRVice (SRV) records. ETSI ETSI TS 102 822-4 V1.7.1 (2012-12) 26 An RFC 2... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.5.2 TV-anytime location resolution service query | The name for the TV-anytime location resolution service is "lres" which is a shortened version of "location resolution". The use of a shortened name is adopted, as there is a limit of 512 characters for a DNS response in some DNS client implementations. The complete query name will look like: _lres._tcp.<CRID authority... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.6 TCP/IP based request to resolution server | The protocol for sending a request to the location resolution server is based on the HTTP protocol (see RFC 2616 [3]). The format of the query string shall follow that generated by the submission of an HTML form using a GET request: http://<Path_to_server_script>?[key=value]&[key=value] where the key/value pair is repe... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.6.1 Further requirements on a PDR HTTP client | The PDR shall at least implement the HTTP v1.0 specification (see RFC 1945 [4]) for issuing a GET request to the server. In addition to the requirements of HTTP v1.0, the PDR shall also send the HTTP v1.1 header of "host" and the HTTP v1.0 header "user-agent". The HTTP client in the PDR shall support at least the follo... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.7 TCP/IP protocol for response from resolution server | The response from the location resolution server will be based on the HTTP v1.0 specification (see RFC 1945 [4]). The response from the server can be one of three possible types: 1) The result of resolving the CRIDs sent to the server. 2) An HTTP re-direct to allow the distribution of services amongst a number of machi... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.7.1 Case 1: returning the result of resolving CRIDs | If the response from the location resolution server is the result of resolving the CRIDs requested by the PDR, one or more instances of the content referencing XML Schema as defined in the present document or in TS 102 822-3-1 [10] shall be returned. The MIME type returned by the location resolution server shall be tex... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.7.2 Case 2: returning an HTTP re-direct | Use of the HTTP redirect commands (HTTP error codes 300 to 399) may be used by the location resolution server to indicate that the PDR should disconnect and connect to a different location resolution server. The reason for providing this functionality is so that a location resolution provider can redirect their resolut... |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.7.3 Case 3: returning a resolving authority record | In the case returning a resolving authority record, the MIME type shall be text/xml and the response shall consist of an instance of a ResolvingAuthorityRecordTable conforming to the syntax specified in clause A.1.2. |
5f2db23db0ea89c5b0f3fb0738b459fc | 102 822-4 | 12.3.7.4 Encoding server response | It is permissible for the response from the server to be encoded, for example by compressing or encrypting the XML instance document. The "Content-Type" response header does not change, but rather the "Content-Encoding" gives the encoding that has been performed on the data. The exact form of encoding used is not speci... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 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... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 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... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 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... |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 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. ETSI ETSI TS 102 822-3-4 V1.6.1 (2012-12) 8 |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 3 Definitions and abbreviations | |
78dadacd0765b520534eb66312e4f792 | 102 822-3-4 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: application: specific set of functions running on the PDR NOTE: Some applications use metadata, either automatically or under consumer control. attractor: metadata element that is accessible by the consumer in order to aid in the conte... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.