hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.1 States | From the point of view of the present document the Notification object may be in three stable or one transient state. These states together with their transitions as sketched in figure 14. Especially transitions from the active and loaded states to (eventually) the idle state are triggered not only through explicit act... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.1.1 Absent | This is the initial state of the object, and also the final state once the object has been (completely) removed from the system. This is the only state in which an object will stay forever. No timers are associated to this state. Transition from this state to any other state implies loading the object. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.1.2 Loaded | This is the state, in which an object has been loaded (pre-fetched) into the system, but it has been neither activated nor has activation been programmed for some future time. (Due to our convention, the object will stay also in this state if an immediate activation action has been received but the activation has not y... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.1.3 Waiting | When the object has been loaded, and an action has been received for activation at some future time, the object is in the waiting state (and stays in this state until the activation is completed, i.e. the application is launched). In this waiting state the launch time is continuously compared to some external time refe... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.1.4 Active | When the object has been loaded and become active, the object is in the active state. During this state, both the active time counter and the life time counter decrement continuously. Elapsing of the active time triggers an automatic transition back to the loaded state (but the object stays present). Elapsing of the li... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.2 Timers | To manage the automatic transition between the life cycle states, it is made reference to timers as explained below. These timers are of conceptual nature and do not preclude any differing implementation. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.2.1 Active time | The remaining active time is the intended time until automatic cancellation. It is initialized as a relative time from intended object activation to cancellation. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.2.2 Life time | The remaining life time is the intended time until automatic removal of the object. It is initialized as a relative time at the time of object loading, with a resolution of milliseconds. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.3 Actions | Transitions between the object life cycle states are initiated by actions as specified in subsequent clauses. These actions may be initiated by reception of Notification messages (both explicit and implicit), or automatically triggered after a certain time. In the following the different actions are discussed together ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.3.1 Fetch | The fetch action may be used by the Notification service provider to indicate that the receiver shall download the Notification object. The terminal should then tune-in to the corresponding, already discovered, delivery channel (e.g. a FLUTE session), retrieve the object and store it for future use. As the object is fe... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.3.2 Launch | The launch action is used to indicate to receivers that the corresponding Notification object needs to be activated and processed by the target Notification application. The launch time is either indicated separately as a parameter or as part of the transport protocol (e.g. the RTP timestamp of the carrying RTP packet)... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.3.3 Cancel | The cancel action may be used to annulate an active Notification object. The Notification object may be re-activated again by re-submitting a new Notification message version with a launch action. Upon receiving a cancel action, the target Notification application stops any processing and actions triggered by the Notif... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3.3.4 Remove | The remove action may be used to instruct receivers to discard the corresponding Notification object completely (freeing up any used resources, e.g. by discarding Notification message parts). While the remove action may be triggered through a specific Notification message (or trigger), in most cases the object will be ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.4 Message filtering | This clause specifies the generic filtering of Notification messages at the terminal side. The generic filtering mechanism consists of two different parts. The first part is used for out-of-band announcement of filter definitions. This is achieved through the Notification Init Container, which is transported out of ban... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.4.1 Filter Definitions | The NotificationFilterTable element contains the exhaustive list of filter definitions associated with a Notification service. The table consists of a sequence of optional FilterEnum elements and at least one FilterDefinition element. The FilterDefinition element defines the syntax and semantics of a filter element typ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.4.2 Filter Elements | This clause specifies a binary representation for the filter elements carried in individual Notification messages. This binary representation can be embedded in the FilterElementList element of the generic header part of the Notification message using base64 encoding (see clause 6.1.1). In case of FLUTE, the binary fil... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.4.3 Filtering of aggregates | When aggregating multiple messages of the same Notification type into the same container for carriage in a single transport object over FLUTE, the Notification service shall whenever possible include filtering information at the aggregate level. The aggregate level filtering information is provided by the FilterElement... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7 Bootstrap and initialization of Notification services | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.1 Discovery of default Notification services | In this clause the bootstrap process for default Notification service is specified. As introduced in clause 5, one PDN service and several EDN services can be transported in parallel in an IP Platform. To indicate to the receiving terminal the availability of PDN and EDN services, additions to the bootstrap procedure a... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.1.1 Bootstrap descriptor | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.1.1.1 Syntax of DefaultNotificationAccessDescriptor | The "DefaultNotificationAccessDescriptor" is a binary representation of acquisition of default Notification service. The "DefaultNotificationAccessDescriptor" specifies the Acquisition information related to current IP platform or a particular ESGProviderID signalled in the "ESGProviderDiscovery" descriptor. Table 17: ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.1.1.2 Transport of DefaultNotificationAccessDescriptor | The "DefaultNotificationAccessDescriptor" is transported in ESG Bootstrap FLUTE session in a well-known IP address and port, as defined in TS 102 471 [2]. Additionally the following restrictions apply: The "DefaultNotificationAccessDescriptor" is transported in a dedicated transport object in the bootstrap FLUTE sessio... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.1.2 Bootstrap procedure | The foreseeable way to retrieve information to access the PDN service and a specific EDN service within an IP platform would be as follows: 1) Tune-in to the ESG Bootstrap session. 2) Retrieve "ESGProviderDiscovery" descriptor, "ESGAccessDescriptor" descriptor and "DefaultNotificationAccessDescriptor". 3) Look up "Defa... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.2 Discovery of user selected Notification services | User selected Notification services can be categorized as plain Notification services and service related Notification components. Both are signalled in ESG datamodel based on TS 102 471 [2]. • A standalone Notification service is signalled as a regular service in the ESG. • A service related Notification component is ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3 Notification Initialization Container | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.1 NIC Format | The Notification Initialization Container (NIC) contains the necessary information to initialize the consuming Notification application. The NIC information applies to a specific Notification application, which is identified by the Notification type. The NIC container is in XML format and conforms to the following sche... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.2 Transport of the NIC | The Notification init container may be delivered in-band, along with the corresponding Notification messages, or out-of-band e.g. in the ESG. The NIC and all its external components may be encapsulated into a Notification container or delivered as separate objects. ETSI ETSI TS 102 832 V1.2.1 (2010-01) 47 At the receiv... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.3 Signalling Compression Algorithms | The default compression algorithm used for compressing Notification messages is Gzip [5]. In case a different compression algorithm is needed by a Notification service, information about that algorithm is provided by the NotificationInitContainer. This is done using a new Init Fragment definition which conforms to the ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.4 Default Timer Information | The default active time and life time values may be indicated in the Notification Initialization Container. If not present, the default active time is assumed to be 3 600 000 milliseconds and the default life time is assumed to be 86 400 000 milliseconds. The initialization fragment of the NIC for the default timer inf... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.5 Notification type information | In order to enable the handling of unknown Notification types, terminals may find in the Notification Init Container a pointer (URL) to a source that provides further information about the Notification type. The initialization fragment of the NIC for the Notification type information shall conform to the following sche... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.3.6 Example of the NIC | In this clause an example of a NIC object is given. <?xml version="1.0" encoding="utf-8"?> <NotificationInitContainer xmlns="urn:dvb:ipdc:notification:2008" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" NotificationType="156"> <InitFragment xsi:type="CompressionInit" InitFragmentID="urn:dvb:ipdc:notification:20... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 7.4 Processing of Notification Messages | The processing of a Notification message depends on the type of its application-specific message part. The Notification type of the Notification service is mapped uniquely to the MIME type of the application-specific message part. This mapping is static for well-defined Notification applications and dynamic for other N... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 1 Scope | The present document specifies the Reference Model (Ref Mod) for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 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... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 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 ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 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... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 3 Definitions and abbreviations | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [1] apply. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [1] apply. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 4 Introduction | The CPCM Reference Model provides a technical and architectural framework for the DVB Content Protection and Copy Management (CPCM) System. The Reference Model is described on the basis of the CPCM Abbreviations, Definitions and Terms defined in TS 102 825-1 [1]. It provides a technology-agnostic basis for the CPCM Sys... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 5 CPCM System | This clause gives an overview of the various elements of the CPCM System. Figure 2 shows the basic conceptual model of the CPCM System. Figure 2: CPCM System Conceptual Diagram It is intended that the CPCM System will be implemented for different methods of Input Content delivery to the consumer including free-to-air t... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 6 CPCM Functional Entities and Content Types | The five content management operations (Acquisition, Storage, Processing, Consumption and Export) constitute the set of abstract CPCM Functional Entities. This set of Functional Entities is sufficient to describe any foreseen audio-visual content handling process in the consumer environment. Figure 5 elaborates the Fun... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7 CPCM Device | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.1 General | A CPCM Device is a device that implements any CPCM functionality in a compliant manner. The implementation of CPCM functionality is referred to as a CPCM Instance. The CPCM functionality described so far in clause 6 covers only one part of what is required to implement CPCM, namely the Content Handling part. This claus... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2 Logical Interfaces | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.1 User Interface | Naturally the CPCM Device's actual user interface and method of user interaction are outside the scope of the CPCM Reference Model. However, the following information must be able to be conveyed to the user: • Information about the CPCM Authorized Usage of CPCM Content Items that the user that the user attempts to acce... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.2 Device Interaction | The Device Interaction interface is realized through the connection between two or more devices. Typically this is a home networking protocol although it can be any bidirectional signalling mechanism. Although this logical interface is outside the scope of CPCM, it does map very specifically to CPCM functions. If any C... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.3 CPCM Interaction | This interface is not standardized within the CPCM specifications. It may be implemented in a proprietary manner inside a CPCM Device, or it might be made accessible as a published interface by the supplier of an implementation of a particular CPCM Instance. At least the following information exchanges are necessary: •... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.4 Non-Secure CPCM Communications | This logical interface is used for all communications between CPCM Instances that need to be carried out over unsecured communication links, for example ADM or CPCM related discovery operations that occur prior to the establishment of a SAC. Non-secure CPCM communications are transactions that do not require either sec... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.5 Secure Authenticated Channel | The Secure Authenticated Channel (SAC) is a virtual communications channel established between mutually authenticated CPCM entities using a shared secret non-permanent key for secure and confidential transfer of data. In the CPCM Reference Model the SAC is established between the Security Control parts of CPCM Instance... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.2.6 Proximity Control Communications | Proximity Control Communications are any communications necessary to securely establish whether or not two CPCM Instances are in the same Local Environment. These communications must of course provide a reliable, at least Boolean, indication of proximity, but they do not necessarily take place within the SAC. The metho... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3 CPCM Instance | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.1 General | The CPCM functionality inside a CPCM device is encapsulated in a logical entity called the CPCM Instance. The CPCM Instance must be a compliant and secure implementation of its respective CPCM functionalities in accordance with one or more C&R regimes. The implementation of the abstract Functional Entities within the C... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.2 CPCM Instance Logical Interfaces | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.2.1 CPCM Control | The CPCM Control interface provides the communication between the Security Control and Content Handling parts of the CPCM Instance. The relevant information flows from the Security Control part to the Content Handling part are: • Content scrambling or descrambling keys. • Protected Content Licence to be embedded in a C... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.2.2 ADM Control | The ADM Control logical interface contains the following functionality: • Send and receive ADM relevant secure messages from another CPCM Instance. • Retrieve the host Device's current AD Identifier (ADID), which is itself stored and managed within Security Control (see clause 7.3.3.2.4). • Initiate an AD (Security Con... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3 Security Control | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.1 General | Security Control provides all the security tools necessary to realize the CPCM functionality provided by the CPCM Instance. Figure 9 shows the CPCM Instance with detail about the Security Control part. Figure 9: CPCM Instance with Detail on Security Control The following clauses give a description of the functions of e... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.2 Secure Data Management | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.2.1 General | This component is responsible for securely storing and maintaining all data that is applicable to CPCM security in the host device. This component is responsible for securely storing and maintaining CPCM secret data in the host Device, such as any device secrets, private keys etc. associated with the CPCM Instance and/... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.2.2 CPCM Instance Certificate and Private Key | For the purposes of Trust Establishment with other CPCM Instances, each CPCM Instance (that needs to establish a SAC with other CPCM Instances) is equipped with a unique public key certificate, referred to as the CPCM Instance Certificate (CIC), issued by the, or a, Certificate Authority (CA). The Secure Data Managemen... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.2.3 Device Secret | The CPCM Instance might use a Device Secret (DS) in order to protect Content Licences created and/or maintained by that CPCM Instance. In that case the Secure Data Management element would maintain the DS. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.2.4 AD Secret and AD Identifier | These data fields are required to be maintained only if the host device is AD aware. If the device is not AD aware then the DS (previous clause) may surrogate for the AD Secret for the purposes of handling CPCM Content that is to be bound to the AD (see clause 9.4.2). The AD Secret (ADS) is a globally statistically uni... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.3 Trust Establishment | Trust is established between two CPCM Instances by the mutual exchange of CPCM Instance Certificates and their mutual verification. There may also be a revocation check performed on the received CIC on each side. This is described further in clause 10.8. Mutual exchange of CIC is done during SAC management (see clause ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.4 SAC Management | This component executes the task of SAC establishment with another CPCM Instance. The SAC is controlled by a volatile key that is derived through a process of a certificate-based authenticated key exchange. SAC control keys are managed by the Control Key Management component (see clause 7.3.3.6). The SAC volatile key i... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.5 Licence Processing | The core function of this component is to interpret the contents of the Content Licence in order to enforce compliant behaviour with respect to the associated CPCM Content Item within the host CPCM Device. For each CPCM Content transaction, the Content Licence can arrive by two different paths: a) The Content Licence a... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.6 Key Management | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.6.1 Content Key Management | This component has the following tasks: • Generation of new Content Key/s as required by the Content Handling part of the CPCM Instance for local content scrambling (Acquisition, Processing). • Provision of existing Content Keys, obtained from the respective Content Licences, as required by the Content Handling part of... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.6.2 Control Key Management | This component is responsible for the management of control keys such as the SAC session keys and Authorized Domain keys, i.e. their creation, expiration or other operations upon them. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.7 Cryptographic Tools | The Security Control element of a CPCM Instance must include the set of CPCM cryptographic tools necessary to implement the CPCM functionality hosted in that CPCM Instance, in accordance with CPCM System specification and C&R regimes. The CPCM Security Toolbox (TS 102 825-5 [4]) includes: • Cipher with the appropriate ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.8 Proximity Control | This component performs the Proximity Test, as and when required by the Authorized Usage of the Content Item being transferred. The Proximity Test is the means to determine whether two CPCM Devices, or a CPCM Device and a non-CPCM device storing CPCM Content, are Local with respect to each other at the time the test is... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.9 Secure Time | Secure Time control is needed for SAC management, in particular for SAC session timeout and renewal. Secure Time management is also needed in CPCM Devices that are able to handle CPCM Content with time-based Usage Rules asserted (see clause 9.3.3). The actual requirements of the Secure Time component, e.g. whether reli... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.3.10 Mapping to Other Content Protection Systems | If CPCM Content is Exported to, or Acquired from a trusted Content Protection System (CPS) (as requested by CPCM Interaction, and as possibly authorized by the Content Licence itself) a mapping has to take place, according to each C&R regime. While the security mechanisms of the other CPS are outside the scope of CPCM,... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4 Content Handling | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.1 General | Content Handling includes the logical embodiment of any of the abstract Functional Entities described in the Abstract Model that are necessary to fulfil the device's intended functionality. Figure 10 shows the CPCM Instance with detail about the Content Handling part. Figure 10: CPCM Instance with Detail on Content Han... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.2 CPCM A.P.E.C.S. | CPCM A.P.E.C.S. refers to the complete set of content management functionality that can be implemented in a CPCM Instance, in terms of the CPCM abstract Functional Entities (Acquisition, Processing, Export, Consumption and Storage). Figure 11 shows how the embodiments of the abstract Functional Entities of the Abstract... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.3 CPCM Scramble/Descramble | The Content Handling part shall include the CPCM scrambling tools if the Device functionality necessitates either scrambling and/or descrambling of CPCM Content handled by the CPCM Instance within that Device. The inclusion of the CPCM Scrambler and CPCM Descrambler in a CPCM Device implementation is dictated by the na... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.4 Embedded CL Handling | This function performs the extraction and/or insertion of the CL into CPCM Content as appropriate for the case of C.0.E CPCM Content, described in clause 10.3.3. The CL is passed to/from Security Control via the CPCM Control interface. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.5 CPCM Content Decode | This function is the logical part of the content decoder(s) inside a CPCM Device that can decode CPCM Content. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.6 CPCM Content Digital-to-Analogue Conversion | This function is the logical part of the digital-to-analogue (D/A) converter(s) inside a CPCM Device that can perform D/A conversion of CPCM Content. ETSI ETSI TS 102 825-2 V1.2.1 (2011-03) 25 |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.4.7 Exchange to/from Other Content Protection Systems | This function performs any operation on CPCM Content necessary for its handover to the other CPS (for Export or to a Consumption Output), or any operation on the content coming in from another CPS (Acquisition) to become CPCM Content. The control of the content exchange is retained by the Mapping function in the Securi... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.5 Authorized Domain Management | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.5.1 General | The Authorized Domain Management (ADM) function implements the AD Management rules for the CPCM Device. The basic ADM rules are described in clause 8. The inter-CPCM Instance protocols and exact mode of operation of ADM shall be as defined in TS 102 825-7 [5]. ADM is an optional part of the CPCM Instance, as it is not ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.5.2 AD Discovery | AD Discovery provides signalling and procedures to determine the presence of any ADs when the CPCM Device hosting the present CPCM Instance is connected to other CPCM Devices in the network, and to advertise the AD membership of the present CPCM Instance to the other ADs, or the Device's "home" AD. ETSI ETSI TS 102 825... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.5.3 AD Membership Management | AD Membership Management manages the association of the present CPCM Instance with any AD. This covers the following cases: • The process of joining any established and available AD. • The process of leaving the AD of which the CPCM Instance is a member. • The establishment of a new AD. The AD Membership of a CPCM Inst... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.3.5.4 AD Name Management | The AD Name is a human-readable text to describe any AD. It is intended as an aid to users, and not as a tool to reliably identify any AD or perform the binding of content to the AD. Thus this is a feature that does not require any secure handling, but it does necessitate communications between CPCM Instances that are ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.4 Device Interfaces | Consideration of Content flows into and out of CPCM Instances and Devices have hitherto been at an abstract level. Real CPCM Devices will exchange CPCM Content, Acquire Input Content, Export Content, and sometimes Consume Content via physical Device Interfaces. Figure 13 shows the mapping of Device Interfaces to the Lo... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.5 Storage Drives and Media | Content can also enter and leave CPCM Instances and Devices by way of storage media. Figure 14 shows, based on the examples of an internal hard-disk drive (HDD) and a removable media reader/writer drive, how physical storage provided in a CPCM Device maps to the CPCM Instance within that Device. Figure 14: CPCM Device ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 7.6 CPCM Device and Non-CPCM Content | A CPCM Device can also include non-CPCM functionality that handles non-CPCM Content. The non-CPCM functionality shall not have access to CPCM Content, and there shall be no mechanism for ingesting non-CPCM Content into the CPCM System other than the compliant Acquisition methods described in clause 11.3. Figure 15: CPC... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 8 CPCM Authorized Domain | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 8.1 General | The Authorized Domain (AD) is a distinguishable set of DVB CPCM compliant devices, which are owned, rented or otherwise controlled by members of a single household. A household is considered to be the social unit consisting of all individuals who live together, as occupants of the same domicile. This makes no assumptio... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 8.2 Authorized Domain Management | The following gives an outline of the general Authorized Domain Management aspects of the CPCM System. CPCM Authorized Domain Management (ADM) is the set of rules applying to the dynamic AD membership properties of CPCM Devices. The definitive ADM functionality, including how these requirements are addressed, is contai... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9 CPCM Usage Rules | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.1 General | A Usage Rule in CPCM is a particular operation upon, or behaviour of Content to be controlled within the scope of the CPCM System. A complete set of Usage Rules assertions for a particular CPCM Content Item is referred to as the Authorized Usage of that CPCM Content Item. A Content Item's Authorized Usage is expressed ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.2 Copy and Movement Control | CPCM Instances are required to implement the controls required to enable the following Content usage scenarios related to the Storage of Content Copies, wherever applicable to the CPCM functionality implemented: • No restriction on Copying (Copy Control Not Asserted). • Exactly one Copy is allowed to be made and mainta... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.3 Consumption Control | |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.3.1 General | There are two aspects to Consumption Control foreseen in the CPCM System: • time-based usage (Consumption) of CPCM Content; and • the ability to limit the number of concurrent Consumption and Export functions in operation for a CPCM Content Item. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.3.2 Tethered Content | CPCM offers the possibility of being able to deliver content for Storage within CPCM that is not available for Consumption or Export until such rights have been Acquired from the CPCM Instance that has the ability to interact with the delivery system. |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.3.3 Time-based Usage | For CPCM Instances that are intended to offer access to such CPCM Content, it is required to implement the ability to enforce a signalled time window for the usage (Consumption) of that Content. This implies the need to keep track of time, i.e. to implement the Secure Time component of the Security Control part of the ... |
d9d49058a13d4450c537e7988624aabe | 102 825-2 | 9.3.4 Concurrent Usage | For CPCM Instances that are intended to offer access to such CPCM Content, it is required to implement the ability to keep track of and limit the number of Consumption and Export functions in CPCM Instances that are active for a Live/Direct Content Item. If this restriction is activated for a given Content Item, the CP... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.