hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2.5 Other categorizations | The Universal Business Registry provides other categorizations that may be useful in describing TV-Anytime metadata services (e.g. uddi-org:general_keywords). The use of such categorizations should, in general, follow the rules defined by the particular tModel, but TV-Anytime provides guidance for use of the uddi:ubr.u... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.3 Publishing a TV-Anytime metadata service | A TV-Anytime metadata service provider can publish details of their service to any node in the UDDI Business Registry. The manner in which this is done will depend upon the operator of that node (see the UDDI specification [16]). An example of the publication process can be found in annex A. A businessService is create... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.3 Web Services Inspection language (WS-Inspection) | A TV-Anytime web server may declare the presence of its metadata services using WS-Inspection [17]. This allows clients to discover service descriptions (i.e. WSDL implementation definitions) for the web services available on that website. The WS-Inspection file may also lead to the discovery of other types of web serv... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.3.1 Discovering the WS-Inspection file | To assist a client in finding a WS-Inspection file, clause 6.1, the WS-Inspection specification states that the document may have a well-known name (inspection.wsil) and be placed at a "common entry point" of the web-site. The term "common entry point" is vague, so TV-Anytime defines the following rules to make it easi... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 1 Scope | The present document is the sixth in a series of 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 and se... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 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... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] W3C Recommendations: "XML Schema" (version 20010502). NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-0-20010502, http://www.w3.org/TR/2001/REC-xmlschema-1-20010502, http://www.w3.org/TR/2001/REC-xmlschema-2-20... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 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. |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 3 Definitions and abbreviations | |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: retrieval of content application: specific set of functions running on the PDR. Some applications use metadata, either automatically or under consumer control authority: organization that creates CRIDs ETSI ETSI TS 102 822... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARIB Association of Radio Industries and Businesses NOTE: A Japanese standards organization. ATSC Advanced Television Systems Committee NOTE: American based standards organization for establishing technical standards for advanced television sy... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4 Introduction to bi-directional metadata services | The TV-Anytime Forum has defined a number of data types that can be exchanged between TV-Anytime devices. These include programme metadata, content referencing information, and user-centric metadata. The present document is concerned with data exchange between TV-Anytime clients and metadata servers over a bi-direction... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.1 Types and functionalities of metadata services | TV-Anytime metadata services can be broken into two basic types, which are shown in figures 2 and 3. The metadata services specified are all request-response based. This can be seen in the two figures - the network transaction is always point-to-point (client to server), and the transaction is always initiated by the c... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.1.1 Metadata retrieval | Metadata retrieval occurs when a client wishes to obtain certain metadata from a metadata service (figure 2) that it has previously discovered and obtained a capability description for. The following list gives some examples of metadata retrieval: • A client wishes to obtain programme reviews for a CRID. The client sen... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.1.2 Submission of anonymous user-centric metadata | Submission of user-centric metadata (figure 3) offers a number of possible benefits to both consumers and metadata service providers. These are described in clause 6.5 of the TS 102 822-3-1 [8]. Ensuring the privacy of these transactions and that the metadata service provider is trustworthy is essential to the submissi... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.1.3 Submission of personal information metadata | Submission of personal information metadata (figure 4) offers a number of possible benefits to both consumers and metadata service providers. These are described in clause 6.5 of the TS 102 822-3-1 [8]. Ensuring the privacy of these transactions and that the metadata service provider is trustworthy is essential to the ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.2 Metadata service capability descriptions | In order to exploit usefully the metadata services described in the previous clause, the client needs information about the nature of the metadata service being offered. This is because different metadata services will provide different types of metadata and can be queried in different ways. For example, some metadata ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.3 Metadata service discovery | Metadata service discovery is the process by which a client establishes a URL where a TV-Anytime metadata service can be found. There are a number of ways this process can occur, but only the third method (see clause 4.3.3) is addressed by the present document. ETSI ETSI TS 102 822-6-1 V1.8.1 (2012-12) 16 |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.3.1 Non-standardized discovery | A number of methods exist for discovering the URLs of metadata services that will not be standardized by the TV-Anytime Forum. The following list gives some examples: • The client might be pre-programmed with a set of URLs that refer to one or more metadata services. This will typically be useful in a vertical market, ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.3.2 Unidirectional delivery of discovery information | TS 102 822-2 [7] and TS 102 822-4 [12] define ways, or requirements on the underlying transport, in which the URL of a bi-directional metadata and/or content referencing service can be discovered from TV-Anytime information inserted in a unidirectional stream. The present document defines how a client can usefully expl... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 4.3.3 Client-initiated discovery using the bi-directional network | This mode of metadata service discovery involves using the bi-directional network to access a "Yellow Pages" of TV-Anytime metadata services. The mechanism is based upon W3C standards for web service discovery (UDDI [22] and WS-Inspection [24]), the use of which is standardized by the TV-Anytime Forum, according to the... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5 Metadata service types | The TV-Anytime Forum defines several types of metadata web service. Each type of web service can be thought of as a remote procedure with a well-defined set of inputs and outputs and a well-defined behaviour. In WSDL [23] terminology, this remote procedure is known as an operation (see annex A). The metadata retrieval ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1 get_Data operation | The get_Data operation allows a client to query a server in order to retrieve TV-Anytime data for a set of programmes or programme groups. The following list gives a few examples of the types of functionality that a TV-Anytime metadata provider can offer using a get_Data operation: • Operation that takes a list of CRID... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1 Request format | The request format allows the client to specify three types of parameters. The semantics and structure of these three parameters are explained in more detail in the subsequent clauses. <complexType name="ResourceIDType"> <simpleContent> <extension base="anyURI"> <attribute name="id" type="ID"/> </extension> </simpleCon... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1 Query constraint parameters | This parameter consists of a set of logical predicates, which can be nested together (according to the rules of first order predicate logic) and together define the set of results that a client is interested in. (Using SQL terminology, this parameter plays a similar role to the WHERE clause in an SQL SELECT statement.)... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1.1 Identifying contextNodes | A contextNode is an XML node of the following type: element. • Element contextNode can correspond to nodes with an XML Schema complexType model (an element containing other elements or attributes). ContextNodes are defined using an XPath expression based on a subset of XPath (for a definition of this XPath subset, see ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1.2 Identifying fields | A field is an XML node of the following type: attribute, text or element: • Attribute fields and text fields (the contents of an element's text node) have no structure, so can be represented as a string whose value can be tested against the fieldValue given in a predicate. • Element fields can correspond to nodes with ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1.3 Primary index CRID fields | Fragments containing CRIDs exist in many different locations in the TV-Anytime schema. Since CRIDs can occur in multiple places within a fragment (e.g. in a GroupInformation fragment they can be used to refer to parent groups), table 3 formally defines the CRID field that is used to identify the fragments in each case.... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1.4 Restrictions on the use of QueryConstraints | The QueryConstraints element shall not contain predicates with fields from the following tables: • ContentReferencingTable: Content referencing information does not contain metadata attractors, so none of the fields are suitable as query constraints. • CreditsInformationTable: Even if Credits information can be include... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.1.5 Evaluating a predicate | Although the fieldID values specify precisely the field being matched, a metadata service is free to interpret which metadata fields are used to match the query fieldValue. For example, if a query specifies a programme with a certain title, a server is free to match this string with any of the values given by the Title... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.2 View on returned data | |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.2.1 Requesting tables | This required RequestedTables parameter defines the types of data that a metadata service will try to provide on each result it returns. To achieve this, the client includes a list of table types that it requires. For a given result set, a server should supply, if the appropriate metadata is available, the correspondin... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.2.2 Sort criteria | <complexType name="SortCriteriaType"> <attribute name="fieldID" type="tns:fieldIDType" use="required"/> <attribute name="order" type="tns:SortingOrderType" default="ascending"/> </complexType> <simpleType name="SortingOrderType"> <restriction base="string"> <enumeration value="ascending"/> <enumeration value="descendin... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.3 Size limit parameter | An optional parameter (maxPrograms) can be inserted in the request. It is a positive integer and is used by the client to specify the number of records returned by a query. If a query results in a greater number of records, the server shall return maxPrograms records, along with their corresponding metadata. Limiting t... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.4 Interpretation of query predicates | This clause defines the data model that is used to describe how the server processes the query to build its response. This model is necessary to explain the way in which queries operate across tables. It does not imply an underlying implementation, nor does it imply that a response shall strictly satisfy the relational... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.1.5 Definition of server behaviour | This clause defines the server's behaviour to a query that is assumed by the data model. The server should return a response containing content referencing and/or metadata fragments based upon the predicates in the QueryConstraints that satisfy the query. The server shall return a response that contains only the tables... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2 Response Format | A get_Data response contains an XML instance document containing zero or one instance of the following elements: • TVAMain. • ContentReferencingTable. • InvalidFragments. <element name="get_Data_Result" type="tns:get_Data_ResultType"/> <complexType name="get_Data_ResultType"> <sequence> <element name="TableSortingInfor... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.1 Indicating the sorting of the response | The TableSortingInformation element shall be included in any response where a sort has been performed on the response. The first SortCriteria element defines the first field by which the response has been sorted. Each subsequent SortCriteria element (if any) defines the next levels of sorting that has been applied. For... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.2 Indicating the service version | The serviceVersion attribute shall be included in the response. This parameter indicates the version of the get_Data operation's capability description. When the version is updated a client can retrieve a new capability description for the metadata service (see clause 7.1 for more explanation on how this parameter is u... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.3 Truncating the result set | If the optional "truncated" attribute has the value "true", the records returned do not represent the entire query result set. This is either a result of the inclusion of the maxPrograms attribute in the request, or as a result of the server being overloaded. The actual limit used in the latter case is server specific,... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.4 Updating the result set | The fragmentVersion and fragmentId identifiers may be placed at the fragment level in the get_Data response (as defined by the TS 102 822-3-1 [8]). If included, this allows the client to request and update individual fragments. A client may cache fragment version information and be able to ignore future instances of th... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.5 Requesting a portion of tables | A thin client, which has a limited bandwidth to get metadata and/or a limited processing power issues a request for a portion of program information and location metatada tables available for two TV channels with no specified period. Only the following elements are requested in addition to the mandatory elements and at... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.1.2.6 Updating fragments requesting a portion of tables | After having received a list of fragments with a limited set of fields for each requested table, the client may wish to retrieve fragments which have been updated after a given date, i.e. September 25, 2002. If he wants to get the updated fragments as available from the server, he can issue the following request: <tns:... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.2 submit_Data operation | The "submit_Data" operation is much simpler than the "get_Data" operation. In this version of the specification, its usage is limited according to the constraints outlined in clause 3.1.2. |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.2.1 Usage and user preference data submission policy (informative) | TV-Anytime phase one technical specifications limit the data that can be submitted to a defined (in clause 3.1.2) set of anonymous profile data that has been created via manual input or intelligent agents based on usage of services and content. It is out of scope for the device to send "all" usage data to "all" potenti... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.2.2 Request format | <element name="submit_Data" type="tns:submit_DataType"/> <complexType name="submit_DataType"> <sequence> <element name="UsageHistory" type="mpeg7:UsageHistoryType"/> </sequence> </complexType> The input to the submit_Data operation simply uses the mpeg7:UsageHistoryType which is part of the UserDescription defined in T... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.2.3 Response Format | <element name="submit_Data_Result" type="tns:submit_Data_ResultType"/> <complexType name="submit_Data_ResultType"> <attribute name="serviceVersion" type="unsignedInt" use="required"/> </complexType> The submit_Data response shall contain some indication of the current version of the capability description. This allows ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.3 upload_Personal_Data Operation | The upload_Personal_Data operation is similar to submit_Data operation but it should be used in a secure and trusted environment. The upload_Personal_Data is defined to submit any personal information as defined in the ExtendedUserDescriptionType of TS 102 822 3-3 [10]. However, the service provider and the user using ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.3.1 Request format | <element name="upload_Personal_Data" type="tns:upload_Personal_DataType"/> <complexType name="upload_Personal_DataType"> <sequence> <element name="UserInformation" type="tva2:ExtendedUserDescriptionType" maxOccurs="unbounded"/> </sequence> </complexType> The input to the upload_Personal_Data operation simply uses the t... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.3.2 Response format | <element name="upload_Personal_Data_Result" type="tns:upload_Personal_Data_ResultType"/> <complexType name="upload_Personal_Data_ResultType"> <attribute name="serviceVersion" type="unsignedInt" use="required"/> <attribute name="status" use="required"> <simpleType> <restriction base="string"> <enumeration value="success... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.4 clear_Personal_Data operation | The clear_Personal_Data is an operation to remove user information submitted by upload_Personal_Data in the bi-direction networked environment. The clear_Personal_Data can be used to perform following functionalities which are: 1) Clearing submitted user information of a specified user submitted in a certain period of ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.4.1 Request format | <element name="clear_Personal_Data" type="tns:clear_Personal_DataType"/> <complexType name="clear_Personal_DataType"> <sequence> <element name="TimeFrom" type="tva:TVATimeType" minOccurs="0"/> <element name="TimeTo" type="tva:TVATimeType" minOccurs="0"/> <element name="TargetTable" type="tns:PersonalInformationTableTyp... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 5.4.2 Response format | <element name="clear_Personal_Data_Result" type="tns:clear_Personal_Data_ResultType"/> <complexType name="clear_Personal_Data_ResultType"> <attribute name="serviceVersion" type="unsignedInt" use="required"/> <attribute name="status" use="required"> <simpleType> <restriction base="string"> <enumeration value="success"/>... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6 Transport protocol | SOAP [5] and HTTP [3] are used for delivering TV-Anytime XML data over the IP networks, since this combination is very well suited to the point-to-point, request-response nature of the TV-Anytime operations. The exact usage of SOAP and HTTP is given in the next two clauses. Figure 5 provides a semantic representation o... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.1 SOAP | The following usage of SOAP is mandated: • TV-Anytime metadata services will provide an HTTP binding, and may support other transport bindings where appropriate. • SOAP supports different messaging styles, but is most commonly used for Remote Procedure Calls. TV-Anytime does not use remote procedure call messaging styl... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.2 Error Codes | The first line of error reporting is governed by the SOAP specification [5]. SOAP fault reporting and fault codes will be returned for most invalid requests or any request where the intent of the caller cannot be determined. In a manner consistent with the SOAP processing rules, HTTP status codes will be used for commu... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.2.1 General error conditions | The following error codes may be returned by invoking any of the operations defined in the present document. The field attribute is not relevant to these errors, and so shall not be present for the following error conditions: • FatalError: Signifies that a serious technical error has occurred whilst processing the requ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.2.2 get_Data operation error conditions | When any of the following errors are returned, the operation shall return a field attribute listing the field identifiers that caused the error to occur. • UnsupportedQueryField: A query contains a fieldID value that is no supported by the metadata service. When this error is returned, the operation shall return a fiel... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.3 HTTP | • The HTTP server and client shall fully support HTTP/1.0 [3]. • The client shall always send the HTTP/1.1 defined Host header (which is defined in clause 14.23 of HTTP/1.1 [4]). • The HTTP client and server negotiate a suitable compression using the Accept-Encoding header. Therefore, both the client and server shall s... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.4 Encapsulation of metadata | |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.4.1 Request and response data | In all cases, the request and response data form a single, valid XML instance document. In general, these instance documents are self-describing and need no further encapsulation. However, the metadata encapsulation for the get_Data operation is defined in more detail. ETSI ETSI TS 102 822-6-1 V1.8.1 (2012-12) 47 |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.4.2 Encapsulation of get_Data response | The content of the SOAP envelope is a TVAMain element and/or ContentReferencingTable, as specified in clause 5.1.2. These XML instance documents effectively provide an encapsulation format for the fragments they contain. The context path of each fragment is implicit from the fragment's location in the instance document... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.5 Encoding of metadata | Servers shall support UTF-8 textual encoding for all requests and responses, and may support other encodings, in which case the encoding shall be indicated in the XML header according to clause 4.3.3 of the XML specification [1]. If an encoding is so indicated it shall be consistent with the encoding indicated in the H... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 6.6 Metadata service security | The TV-Anytime phase 1 set of specifications offers clients guaranteed integrity of the metadata delivery from an authenticated server. This technology is described in TS 102 822-7 [17]. A metadata server that supports the TS 102 822-7 [17] specification for integrity checking shall be capable of communicating with cli... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7 Metadata service capability descriptions | For each TV-Anytime get_Data or submit_Data operation that is provided, there is a corresponding operation, describe_get_Data or describe_submit_Data. These two operations (an operation, X, and its corresponding describe_X operation) together form a port (see annex A). Since a port always has a single binding and endpo... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1 describe_get_Data | The get_Data capability description provides the following type of information about the operation: • Human-readable descriptive information about the operation. • The types of metadata tables available. • If metadata field selection is available, the field IDs available for each table. ETSI ETSI TS 102 822-6-1 V1.8.1 ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.1 Use of the AuthorityList element | <complexType name="AuthorityListType"> <sequence> <element name="Authority" type="string" maxOccurs="unbounded"/> </sequence> </complexType> Name Definition AuthorityListType A definition of a list of one or more Authority elements. Authority Specifies a single authority for whose CRIDs the operation is able to provide... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.2 AvailableTables information | This element describes which table types the get_Data operation is capable of returning. Depending upon the table type, each entry in the list (a table element) can contain a different child element. These child elements contain descriptive information that is relevant to that table type. <complexType name="AvailableTa... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.2.1 Operations that can deliver content referencing information | If the server is capable of delivering content referencing information then the description will include a list of Resolving Authority Records describing the resolution services offered by this server. This allows a client to establish whether a particular CRID may be resolved using the metadata service. |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.2.2 Operations that can deliver programme metadata | If the server is capable of delivering programme metadata then the description will include a list of CRID authorities for which metadata is available. If the server is capable of delivering scheduling information (ProgramLocationTable), a list of the content service URLs (e.g. broadcast channels, IP multicast services... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.3 Extended field List | If a metadata service wishes to support querying or sorting on fields that are not allocated fieldIDs by the TV-Anytime Forum, it has to define these field using its own ExtendedFieldList. This allows a get_Data operation to provide searching and sorting functionality that is specialized to the metadata available to th... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.1.4 Description of update capabilities | There are two optional features whose support shall be independently indicated using this part of the capability description. <complexType name="updateCapabilityType"> <attribute name="versionRequest" type="boolean" default="true"/> <attribute name="invalidResponse" type="boolean" default="true"/> </complexType> Name D... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.2 describe_submit_Data | The describe_submit_Data capability description provides a metadata service with the ability to describe the usage and preference information that it wishes to receive. It can optionally specify the privacy policy that will be used when user centric data is submitted to this metadata service. <complexType name="describ... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.3 describe_upload_Personal_Data | The describe_upload_Personal_Data capability description provides a metadata service with the ability to describe the user and usage related information that it wishes to receive. It can optionally specify the privacy policy that will be used when user centric data is submitted to this metadata service. <complexType na... |
65af2c65dd41cce9e7202aa633a52581 | 102 822-6-1 | 7.4 describe_clear_Personal_Data | Capability description of clear_Personal_Data is not provided in the present document. describe_clear_Personal_Data is not defined in the present document not because it is not supported, but because any metadata service with capability of receiving personal data shall also support full functionality of clear_Personal_... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 1 Scope | The present document specifies the Authorized Domain Management for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. The present document defines messages and state machines that together define the conformant behaviour of an implementation. The present document also defines a ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 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... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 825-1: "Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms". [2] ETSI TS 102 825-4: "Digital Video Broadcasting (DVB); Content... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 3 Definitions and abbreviations | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [1] apply. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [1] apply. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4 Authorized Domain Management (ADM) | ADM is the mechanism that allows CPCM Devices belonging to a household to establish and Join a DVB CPCM Authorized Domain (AD). It also provides an interoperable means of managing that AD. Basic expectations on ADM are given in TS 102 825-2 [i.3]. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.1 ADM in the CPCM System | Figure 1 shows how ADM fits into the CPCM Reference Model. Figure 1: ADM in the CPCM Reference Model ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 9 Figure 2 provides another view of ADM within a CPCM implementation. It identifies that there are three key internal sub-systems with which the ADM Sub-system must communicate. F... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.2 Local ADM Master and Domain Controller | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.2.1 ADM Local Master Concept and Requirements | A single CPCM Instance acts as a temporary Local ADM Master for the AD members in the Local network. The ADM Local Master has no specific additional data (i.e. the same AD data is replicated to all Instances in the AD). The Local Master can be replaced at any time to avoid a single-point-of-failure. Figure 12 and claus... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.2.2 The Global Domain Controller Concept | ADM defines a Domain Controller for Secure Authorized Domain Size and Extent implementation. The Domain Controller is responsible for all AD operations (including AD Joining and Leaving) that may affect ADSE records and decision making processes. The user is able to Transfer Domain Controller functionality from one CPC... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.3 Authorized Domain capabilities | CPCM Instances shall publish their Authorized Domain Management capability through the following fields in the certificate. Table 1: ADM Fields Field Meaning AD_aware An AD aware CPCM Instance is one that is able to securely create or record the AD Secret. It has direct access to Content that is bound to its AD. It is ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.4 Authorized Domain Size and Extent | Authorized Domain Size and Extent (ADSE) ensures that CPCM Instances do not violate the AD size, scope and extent requirements when they attempt to become members of the same AD. ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 12 |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.4.1 ADSE Counts and Values | The ADSE method makes use of the following counters and ceilings. Table 2: ADSE values maintained by the DC Variable Bits Type Meaning total_count 16 uimsbf The current number of CICF in the AD. total_ceiling 16 uimsbf The maximum number of CICF allowed in the Authorized Domain remote_count 16 uimsbf The current number... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.4.2 ADSE Method Description | The ADSE Method is defined by the following rules: 1) There is one logical Domain Controller per AD, initially instantiated in a single physical Domain Controller contained within a single CPCM Instance within a single CPCM Device. The logical Domain Controller function may then be Transferred from one physical device ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 4.4.3 Other ADSE Methods | Other ADSE Methods may be defined by the CPCM C&R regime. They may be built upon optional ADSE tools described in clause 7. ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 16 |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5 The ADM State Machine - Normative text | Figures 5 to 28 define conformant behaviour of ADM implementations. The standardized state machine described here provides a simple single-threaded model. Implementations are free to employ a more sophisticated multi-threaded approach provided that the system behaviour remains conformant to the states shown here. Figur... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1 Normal Behaviour | Figures 5 to 28 define normal operations. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.1 Discovery Protocol | Start Discovery Discovery Request (Broadcast) Discovery Response Start Timeout Awaiting Discovery Response Discovery Request Timeout expired End Discovery Discovery Response Figure 5: Discovery State Machine The Discovery Protocol shall be used whenever a CPCM Device makes a connection to the AD. It is used in the foll... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.2 Local Master and Domain Controller messaging | Some Authorized Domain Management operations require that an AD Member or a Domain Controller sends messages to the Local Master. However, CPCM Instances are not required to permanently know the identity of the current Local Master. Even if they recorded it, it may be the case that the Local Master has been disconnecte... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.3 Connected AD Member | Table 4 describes how a connected AD Member (that is neither a Domain Controller nor the current Local Master) shall react when receiving messages. Table 4: Actions by AD member when receiving messages Message Action and reason Discovery_request_message It shall send a Discovery_response_message. AD_update_request_mess... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.4 Connected Domain Controller | Table 5 shows how a Domain Controller that is not the Local Master shall react when receiving messages. Table 5: Actions by DC that is not the LM when receiving messages Message Action and reason Discovery_request_message It shall respond with the Discovery_response_message. AD_update_indication_message It shall update... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.5 Connected Local Master | Figure 10: Connected Local Master State Machine ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 24 Table 6 shows how a connected Local Master (that is not Domain Controller) shall react when it receives the following messages. Table 6: Actions by LM that is not DC member when receiving messages Message Action and reason Discov... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.6 Connected Local Master and Domain Controller | Connected LM-DC Discovery Request AD Update Request AD Join Begin App Request To Leave Discovery Response AD Update Response DC Joining Process AD Leave Begin DC Leaving Process Received more recent record? No Update Record Yes AD Update Ind (Broadcast) LM Election Request / LM Election Response Local Master Election P... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.