hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.6.2 Local Master election request | void LM_ election_request_message ( ADM_status status, ADID ADID, LM_capability local_master_capability, CPCM_instance_certificate_id certificate_id, [DC_ADSE_values()] ADSE_values ); This message shall be broadcast by any member Instance on the local network to request the election of a new Local Master. Table 193: Lo... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.6.3 Local Master election response | void LM_ election_response_message ( ADID ADID, ADM_status status, LM_capability local_master_capability, CPCM_instance_certificate_id certificate_id, [DC_ADSE_values] ADSE_values ); This message shall be broadcast by each member Instance in response to a Local Master Election request. Table 195: Local Master election ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.6.4 Local Master election indication | void LM_ election_indication_message ( ADID ADID ); This message shall be broadcast by the winner of a Local Master election. Table 197: Local Master Election Indication message Syntax Bits Identifier LM_ election_indication_message(){ CPCM_protocol_message_type = 0x6005 16 bslbf control_field = 0x04 8 bslbf message_pa... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7 Domain Controller transfer | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.1 General | The Domain Controller transfer protocol is a transactional protocol applied in order to transfer the role of Domain Controller to another CPCM Instance, as defined in TS 102 825-7 [8]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.2 Domain Controller transfer begin | void DC_transfer_begin_message ( ADID ADID, ADM_status status, AD_capability() capability ); This message shall be sent to a Domain Controller to signal the start of a Domain Controller transfer operation. Table 199: Domain Controller Transfer begin message Syntax Bits Identifier DC_transfer_begin_message(){ CPCM_proto... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.3 Domain Controller transfer ready | void DC_transfer_ready_message ( ADID ADID, ADM_status status, ); This message shall be returned by a Domain Controller when prepared for a Domain Controller transfer operation. Table 201: Domain Controller transfer ready message Syntax Bits Identifier DC_transfer_ready_message(){ CPCM_protocol_message_type = 0x6017 16... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.4 Domain Controller transfer commit | void DC_transfer_commit_message ( ADID ADID, ADM_status status, ); This message shall be sent to a Domain Controller to proceed to a Domain Controller transfer operation. Table 203: Domain Controller transfer commit message Syntax Bits Identifier DC_transfer_commit_message(){ CPCM_protocol_message_type = 0x6018 16 bslb... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.5 Domain Controller transfer confirm | void DC_transfer_confirm_message ( AD_internal_record internal_record ); This message shall provide the confirmation that Domain Controller transfer has been completed. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 138 Table 205: Domain Controller transfer confirm message Syntax Bits Identifier DC_transfer_confirm_message(){... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.6 Domain Controller transfer finish | void DC_transfer_confirm_message ( void ); This message shall be the final message to allow cleanup of change records. Table 207: Domain Controller transfer finish message Syntax Bits Identifier DC_transfer_finish_message(){ CPCM_protocol_message_type = 0x601A 16 bslbf control_field = 0x08 8 bslbf message_payload_lengt... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.7 Become Domain Controller | void become_DC_message ( ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be sent by the Domain Controller to inform a Domain Member, a new Domain Controller (Transfer Case), or an additional Domain Controller (Split Case) of its new status. Table 208: Become Domain ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.7.8 New Domain Controller | void new_DC_message ( void ); This message shall be sent by the CPCM Instance that is about to become a Domain Controller, following a DC Split or a DC Transfer. Table 210: New Domain Controller message Syntax Bits Identifier new_DC_message(){ CPCM_protocol_message_type = 0x6081 16 bslbf control_field = 0x08 8 bslbf me... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8 Domain Controller split | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.1 General | The Domain Controller split protocol is a transactional protocol applied in order to split the available ADM resources of the current Domain Controller to be shared with another CPCM Instance able to act as Domain Controller for the AD, as defined in TS 102 825-7 [8]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.2 Domain Controller split begin | void DC_split_begin_message ( ADID ADID, ADM_status status, AD_capability() capability, ); This message shall be sent to a Domain Controller to signal the start of a Domain Controller split operation. Table 211: Domain Controller Split begin message Syntax Bits Identifier DC_split_begin_message(){ CPCM_protocol_message... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.3 Domain Controller Split ready | void DC_split_ready_message ( ADID ADID, ADM_status status, ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be returned by a Domain Controller when prepared for a Domain Controller split operation. Table 213: Domain Controller split ready message Syntax Bits Identif... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.4 Domain Controller split commit | void DC_split_commit_message ( ADID ADID, ADM_status status, ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be sent to a Domain Controller for completion of a Domain Controller Split operation. Table 215: Domain Controller split commit message Syntax Bits Identifie... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.5 Domain Controller split confirm | void DC_split_confirm_message ( AD_internal_record internal_record ); This message shall provide the confirmation that Domain Controller shall now be split. Table 217: Domain Controller split confirm message Syntax Bits Identifier DC_split_confirm_message(){ CPCM_protocol_message_type = 0x601E 16 Bslbf control_field = ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.8.6 Domain Controller split finish | void DC_split_finish_message ( void ); This message shall be the final message to allow cleanup of change records. Table 219: Domain Controller split finish message Syntax Bits Identifier DC_split_finish_message(){ CPCM_protocol_message_type = 0x601F 16 bslbf control_field = 0x08 8 bslbf message_payload_length 16 uimsb... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9 Domain Controller Merge | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.1 General | The Domain Controller merge protocol is a transactional protocol applied in order to merge the available ADM resources of another CPCM Instance with those of the initiating CPCM Instance acting as Domain Controller for the AD, as defined in TS 102 825-7 [8]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.2 Domain Controller merge begin | void DC_merge_begin_message ( ADID ADID, ADM_status status ); This message shall be sent to a Domain Controller to signal the start of a Domain Controller merge operation. Table 220: Domain Controller Merge begin message Syntax Bits Identifier DC_merge_begin_message(){ CPCM_protocol_message_type = 0x6020 16 bslbf contr... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.3 Domain Controller merge ready | void DC_merge_ready_message ( ADID ADID, ADM_status status, ); This message shall be sent by a Domain Controller when prepared for a Domain Controller merge operation. Table 222: Domain Controller Merge ready message Syntax Bits Identifier DC_merge_ready_message(){ CPCM_protocol_message_type = 0x6021 16 bslbf control_f... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.4 Domain Controller Merge commit | void DC_merge_commit_message ( ADID ADID, ADM_status status, AD_internal_record internal_record ); This message shall be sent to a Domain Controller to proceed to a Domain Controller merge operation. Table 224: Domain Controller merge commit message Syntax Bits Identifier DC_merge_commit_message(){ CPCM_protocol_messag... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.5 Domain Controller merge confirm | void DC_merge_confirm_message ( void ); This message shall provide the confirmation that Domain Controller merge has been completed. Table 226: Domain Controller merge confirm message Syntax Bits Identifier DC_merge_confirm_message(){ CPCM_protocol_message_type = 0x6023 16 bslbf control_field = 0x08 8 bslbf message_pay... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.6 Domain Controller merge finish | void DC_merge_finish_message ( void ); This message shall be the final message to allow cleanup of change records. Table 227: Domain Controller merge finish message Syntax Bits Identifier DC_merge_finish_message(){ CPCM_protocol_message_type = 0x6024 16 bslbf control_field = 0x08 8 bslbf message_payload_length 16 uimsb... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.7 Merge Domain Controller | void DC_merge_DC_message ( void ); This message shall be sent by the Domain Controller to let another Domain Controller merge with it. Table 228: Merge Domain Controller message Syntax Bits Identifier merge_DC_message(){ CPCM_protocol_message_type = 0x6082 16 bslbf control_field = 0x08 8 bslbf message_payload_length 16... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.9.8 Domain Controller Merged | void DC_merged_message ( ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be sent by a CPCM Instance merging its Domain Controller function with another one. Table 229: Domain Controller merged message Syntax Bits Identifier DC_merged_message(){ CPCM_cprotocol_messag... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10 Domain Controller rebalance | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.1 General | The Domain Controller rebalance protocol is a transactional protocol applied in order to rebalance the ADM resources of an AD, as defined in TS 102 825-7 [8]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.2 Domain Controller rebalance begin | void DC_rebalance_begin_message ( ADID ADID, ADM_status status ); This message shall be sent to a Domain Controller to signal the start of a Domain Controller Rebalance operation. Table 231: Domain Controller rebalance begin message Syntax Bits Identifier DC_rebalance_begin_message(){ CPCM_protocol_message_type = 0x602... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.3 Domain Controller rebalance ready | void DC_rebalance_ready_message ( ADID ADID, ADM_status status, ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be returned by a Domain Controller when prepared for a Domain Controller Rebalance operation. Table 233: Domain Controller Rebalance ready message Syntax ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.4 Domain Controller rebalance commit | void DC_rebalance_commit_message ( ADID ADID, ADM_status status, ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); This message shall be sent to a Domain Controller so signal completion of a Domain Controller rebalance operation. Table 235: Domain Controller rebalance commit message Syn... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.5 Domain Controller rebalance confirm | void DC_rebalance_confirm_message ( void ); This message shall provide the confirmation that Domain Controller rebalance has been completed. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 152 Table 237: Domain Controller Rebalance confirm message Syntax Bits Identifier DC_rebalance_confirm_message(){ CPCM_protocol_message_typ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.6 Domain Controller rebalance finish | void DC_rebalance_finish_message ( void ); This message shall be the final message to allow cleanup of change records. Table 238: Domain Controller rebalance finish message Syntax Bits Identifier DC_rebalance_finish_message(){ CPCM_protocol_message_type = 0x6029 16 bslbf control_field = 0x08 8 bslbf message_payload_len... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.7 Rebalance Domain Controller | void rebalance_DC_message ( ADSE_values() ADSE_values remotely_joined_cicf_list() remotely_joined_cicf_list ); ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 153 This message shall be sent by the Domain Controller to Rebalance its ADSE values with another one. Table 239: Rebalance Domain Controller message Syntax Bits Identif... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.10.8 Domain Controller rebalanced | void DC_rebalanced_message ( void ); This message shall be sent by a Domain Controller to confirm it has just Rebalanced its ADSE values. Table 241: Domain Controller rebalanced message Syntax Bits Identifier DC_rebalanced_message(){ CPCM_protocol_message_type = 0x6085 16 bslbf control_field = 0x08 8 bslbf message_payl... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.11 ADMAAA management | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.11.1 General | The ADMAAA management protocol enables the Domain Controller to verify with the AAA whether an ADM operation is allowed, as defined in TS 102 825-7 [8]. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.11.2 ADMAAA tool request | void ADMAAA_tool_request_message ( ADID ADID ADM_status status, AD_operation protocol, AD_condition condition, ADSE_values() ADSE_values ); This message is sent by the Domain Controller to test if a Join or Split is allowed by that AAA. Table 242: ADM AAA Tool request message Syntax Bits Identifier ADMAAA_tool_request_... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.6.11.3 ADMAAA tool response | void ADMAAA_tool_response_message ( ADSE_values() ADSE_values ); This message shall be in response to an ADMAAA tool request. Table 244: ADMAAA tool response message Syntax Bits Identifier ADMAAA_tool_response_message(){ CPCM_protocol_message_type = 0x60F1 16 bslbf control_field = 0x08 8 bslbf message_payload_length 16... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.7 CPCM Extension messages | void CPCM_extension_message ( identifier CPCM_extension_identifier, extension_data CPCM_extension_data ); CPCM Extensions (TS 102 825-14 [i.7]) explains how CPCM specification may be extended.In addition, a generic CPCM protocol message type for communication with CPCM extensions is defined for use by CPCM Extensions. ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 6.8 Private message | void private_data_message ( identifier private_data_identifier, data private_data ); The private date message protocol provides a generic method for the communication of private data between CPCM Instances using the CPCM protocol framework. The protocol is depicted in figure 37 and table 248, shows the syntax of this g... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7 CPCM Content Management | 7.1 General This clause lays out the generic framework of the management of CPCM Content within the CPCM System. The CPCM Reference Model (TS 102 825-2 [i.3]) sets a basic framework for CPCM Content management in terms of each of the five CPCM abstract Functional Entities - Acquisition, Storage, Processing, Consumption... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.2 CPCM Device and Content discovery | It is intended that CPCM works as transparently as possible for the user. In a typical scenario CPCM will function within a home network ecosystem that can host both CPCM Devices and Content and other non-CPCM devices and content. CPCM Devices will use the usual discovery mechanisms provided by the home network ecosyst... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.3 Inter-Device CPCM Content exchange | Once CPCM Content items have been discovered via the home network, the user can usually select a Content item from his device UI, for example to view, or Consume it. Then the Device Application, as depicted generically in figure 38, triggers its CPCM Instance to take care of CPCM-specific management of the CPCM Content... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4 CPCM functional entity behaviour | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4.1 Acquisition | When Input Content is Acquired by an Acquisition Point, the following shall be generated: • A CPCM Content Licence, as described in clause 8.2. NOTE: If the CPCM Content is to be delivered to another CPCM Instance, USI instantiation in the Content Licence may be different from the originally received USI. • CPCM Auxili... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4.2 Processing | When receiving CPCM Content, a Processing Entity shall do the following: • Verify the Content Licence, as described in clause 8.4. • Enforce the USI, as described in clause 7.5. • Check whether it will be authorized to send the Processed CPCM Content to the Destination CPCM Instance (see clause 7.5.2). • Process the CP... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4.3 Export | When receiving CPCM Content, an Export Point shall do the following: • Verify the Content Licence, as described in clause 8.4. • Enforce the USI, as described in clause 7.5. If image_constraint is asserted and the content is high resolution, the Export Point (via a Processing Entity) shall constrain the resolution to s... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4.4 Consumption | When receiving CPCM content, a Consumption Point shall do the following: • Verify the Content Licence, as described in clause 8.4. • Enforce the USI, as described in clause 7.5. • If Consumption is authorized, descramble the Content if applicable (i.e. if the Content item is not marked DNCS). • Proceed to Consume the C... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.4.5 Storage | When receiving CPCM content, a Storage Entity shall do the following: • Verify the CL, as described in clause 8.4. • Enforce the USI, as described in clause 7.5 and, if required, change the USI to indicate that a new Copy has been generated (see clause 8.2.2). • If applicable (e.g. if the CL was received through a SAC)... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5 USI enforcement | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.1 General | CPCM Content shall only be Acquired, Processed, Stored, Exported, and Consumed or handled in any other manner in accordance with the Authorized Usage, indicated by its USI, possibly in conjunction with its CPCM Auxiliary Data. Most controls are performed by Sink CPCM Instances before they handle the CPCM Content. Howev... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2 Controls prior to Content transfer | A CPCM Instance shall not send, transfer or otherwise propagate Content unless all of the following controls of this clause and its subclauses allow such action for such Content. For avoidance of doubt, unless explicitly stated differently, any disallowance of an action below per one USI field overrides all other permi... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.1 Copy and Movement control | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.1.1 Copy Control Not Asserted | If CPCM Content is marked Copy Control Not Asserted, content may be sent to a CPCM Instance or any other non-CPCM device. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.1.2 Copy Once | Copy Once Content may only be sent by an Acquisition Point or a Processing Entity. A Storage Entity may never send Copy Once Content. Copy Once Content may only be sent to a CPCM Instance and never to a non-CPCM device. If a CPCM Acquisition Point or a Processing Entity Sources more than one instance of Copy Once Conte... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.1.3 Copy No More | CPCM Content that is marked "Copy No More" may be Sourced (with relevant CL protection) to another CPCM Instance but never to a Storage Entity, and never to a non-CPCM device. CPCM Content that is marked "Copy No More" may only be Moved from one Storage Entity to another Storage Entity by using the Move Protocol (see c... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.1.4 Copy Never and Zero Retention | CPCM Content that is marked "Copy Never" may only be Sourced to another CPCM Instance (with relevant CL protection) but never to a Storage Entity, and never to a non-CPCM device. Only Acquisition Points or Processing Entities may Source "Copy Never" content. CPCM Content that is marked "Copy Never with Zero Retention n... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.2 Consumption Control | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.2.1 Viewable | If "Viewable" is asserted, no specific control is required before Sourcing the Content. Content may be sent to CPCM Instances and non-CPCM devices. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 165 If "Viewable" is not asserted, content may only be Sourced to Processing Entities, Storage Entities and non-CPCM devices. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.2.2 View Window Activated | This USI does not require any specific control before Sourcing the Content. Content may be Sourced to CPCM Instances and non-CPCM devices. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.2.3 View Period Activated | "View Period Activated" (VPA) Content may only be sent by an Acquisition Point or a Processing Entity. A Storage Entity may not Source View Period Activated Content, unless within a Content Move protocol. "View Period Activated" Content may only be sent to a CPCM Instance. Before sending content marked "View Period Act... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.2.4 Simultaneous View Count Activated | An Acquisition Point delivering Content marked SVCA may deliver Content to any number of Storage Entities or Processing Entities or non-CPCM Devices. In such case, corresponding Content Licence shall be delivered using the CPCM_put_CL_message, specified in clause 6.5.3.5. When the original Content transmission is over,... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3 Propagation Control | The CPCM_get_CL_message (if any) indicates what the destination Sink CPCM Instance intends to do with the Content (i.e. Processing, Export, Consumption or Storage). The Source assesses whether the content can be propagated. If Content is intended for Consumption, it assesses the Viewing Propagation Information. If Cont... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3.1 MLAD and VLAD | If any of the RAR rules has expired or if no RAR rule is set, Content is considered to be MAD or VAD. The MLAD/VLAD restriction no longer applies. Else, before sending MLAD or VLAD Content, the Source CPCM Instance shall perform a proximity test with the device to which it sends the content. If the test fails, Content ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3.2 MGAD and VGAD | If one of the RAR rules has expired or if no RAR rule is set, Content is considered to be MAD or VAD. The MGAD/VGAD restriction no longer applies. No specific control needs to be done before sending the Content if the Content Licence is under AD secret protection. Content can be Moved to a non-CPCM device if marked MGA... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3.3 MAD and VAD | No specific controls needs to be done if the Content Licence is under AD secret protection. Content may be sent to non- CPCM devices if marked MAD (regardless of its Viewing Propagation Information). ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 168 If the Content Licence is to be sent under SAC protection and content is not... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3.4 MCPCM and VCPCM | No specific controls needs to be done. Content can be sent to non-CPCM devices if marked MCPCM (regardless of its Viewing Propagation information). |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.3.5 MLocal and VLocal | If Content is not marked MLocal or VLocal, it may not be Moved (or Viewed) in the proximity, unless authorized by other propagation USI. The Source CPCM Instance may not send Content based on this propagation USI. Before sending Content Marked MLocal or VLocal, the sending CPCM Instance shall perform a proximity test w... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.4 Export/Output Control | Export/Output controls do not require specific verifications before sending the Content. Content may be sent to CPCM Instances and to non-CPCM devices. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.2.5 Ancillary Control | If the CPCM Content is marked DNCS, the CPCM Instance shall not scramble the CPCM Content before sending it. Content may be transmitted to CPCM Instances or non-CPCM devices. If the CPCM Content is NOT marked DNCS and Content Licence is sent under the sole protection of SAC key (i.e. not under the direct protection of ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3 Controls to be enforced when receiving Content | A CPCM Instance shall not handle received Content unless all the following controls of this clause and its subclauses allow such action for such Content. For avoidance of doubt, unless explicitly stated, any disallowance of an action below per one USI field overrides all other permissions for such action that might be ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.1 Copy and Movement Control | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.1.1 Copy Control Not Asserted | No specific control is required. A Storage Entity may generate multiple copies of such Content. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 169 |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.1.2 Copy Once | A Storage Entity receiving Copy Once Content shall replace the former Content Licence with a Content Licence with Copy No More as a Copy and Movement Control occurs before storing the CPCM Content. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.1.3 Copy No More | A Storage Entity shall not store Content marked Copy No More except as a result of performing the Move Protocol (see clause 7.7). |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.1.4 Copy Never and Zero Retention | A Storage Entity shall not Store Content marked "Copy Never - Zero Retention Asserted". A Storage Entity may store Content marked "Copy Never - Zero Retention Not Asserted". In such case, the Storing CPCM Instance shall issue a new Content Licence with the Copy Control Information set to "Copy Never - Zero Retention As... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.2 Consumption control | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.2.1 Viewable | A Consumption Point or an Export Point may only Consume or Export CPCM Content if it is marked Viewable. Else, Consumption or Export shall not be permitted. This USI shall not impact the behaviour of a Storage Entity or a Processing Entity. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.2.2 View Window Activated | A Consumption Point or an Export Point may only Consume or Export the Content if current date and time is within the view_window. If the CP or the EP is not absolute time capable, it may request time from other CPCM Instances using protocols described in TS 102 825-5 [7]. If it cannot get secure absolute time, consumpt... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.2.3 View Period Activated | No specific control is required by a Processing or a Storage Entity receiving VPA Content. A Consumption Point or an Export Point shall not handle VPA Content. NOTE: A Consumption Point or an Export Point should never receive Content Marked VPA as the Source CPCM Instance should have started the View Window and issued ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.2.4 Simultaneous View Count Activated | A Processing Entity or a Storage Entity has no specific control to perform. For a Consumption Point or an Export Point, if a CL is received via a CPCM_put_CL protocol call from the Acquisition Point that created the Content Licence and protected by a SAC, then no specific control is required. In all other cases, the Ex... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3 Propagation control | The CPCM_put_CL_message indicates which action (i.e. Movement and Copying and/or Viewing) may be performed with the Content. A Processing Entity may process the Content but should assess beforehand whether Content transmission will be permitted. The behaviour of an Export Point will be determined by the C&R regime rega... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3.1 MLAD and VLAD | If any of the RAR rules has expired or if no RAR rule is set, Content is considered to be MAD or VAD. MLAD/VLAD restriction no longer applies. If Content is received from a CPCM Instance, no specific control is required, except if the CL was pushed under SAC protection through a Processing Entity. In this case, the CPC... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3.2 MGAD and VGAD | If any of the RAR rules has expired or if no RAR rule is set, Content is considered to be MAD or VAD. MGAD/VGAD restriction no longer applies. ETSI ETSI TS 102 825-4 V1.2.1 (2011-02) 171 Else, the Sink CPCM Instance shall perform the following tests in the order shown: • Perform a proximity test with the Source CPCM In... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3.3 MAD and VAD | No specific controls are required if the Content Licence is directly protected with the AD Secret. If the Content Licence is under SAC protection, bound to a different AD and MLocal or VLocal is not asserted, the Content shall not be accepted. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3.4 MCPCM and VCPCM | No specific controls are required. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.3.5 MLocal and VLocal | A CPCM Instance receiving Content marked VLocal or MLocal shall handle it only if the Content is Sourced from another Local CPCM Instance, possibly with intermediate handling by one or more Local Processing Entities. If a Consumption Point, Export Point, or a Storage Entity receives pushed Content from a Processing Ent... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.4 Export and Consumption output control | Only Export and Consumption Points may perform these controls. A Consumption Point shall perform the following: • If Content is intended to be Consumed through a Controlled CPS, the Export/Output Controlled CPS and relevant flag in the Controlled CPS Vector must be asserted. Else, consumption shall not be permitted. • ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.3.5 Ancillary control | If the CPCM Content is marked DNCS, the CPCM Instance does not need to descramble the content before handling it. |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.4 Remote Access rules | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.4.1 General | Remote Access Rules may be verified before sending Content or after reception depending upon which CPCM Instance needs to assess whether Content can be remotely accessed. As soon as one of the Remote Access Rules has been satisfied or if none Remote Access Rules is asserted, Content shall be treated as if it were marke... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.4.2 Remote Access post record | The "Remote Access post record" restriction expires as soon as the service event from which the Content item originated ends. These controls are exclusively performed by the non-CPCM portion of a product that contains the CPCM Acquisition Point from which the Content item was Acquired. Upon service event completion as ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.4.3 Remote Access post date/time (moving window) | The "Remote Access post date/time (moving window)" restriction starts expiring when the current date and time equals the date and time specified in this field. To assess this, CPCM Instance shall have access to Secure Absolute Time. Once the "Remote Access post date/time (moving window)" restriction starts expiring, a ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.5.4.4 Remote Access post date/time (immediate) | The "Remote Access post date/time (immediate)" restriction is expired if the current date and time is later than the value specified in this field. To assess this, CPCM Instance shall have access to Secure Absolute Time. Once the current date time is over, the whole Content shall be available for Remote Access, without... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.6 CPCM Content Scrambling management | |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.6.1 General | CPCM Content shall be scrambled using the CPCM Local Scrambling Algorithm (LSA) (see TS 102 825-5 [7]) unless it is marked DNCS, in which case it shall not be scrambled using the CPCM LSA. The CPCM LSA has two possible chaining modes and two possible IV preparation modes, thus resulting in four possible combinations of... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 7.6.2 Dynamic changes of the CPCM Content scrambling key | This clause provides the generic mechanism whereby a CPCM Instance acting as a Source of a scrambled CPCM Content item is able to force a change of the content scrambling key. The application of this generic mechanism to particular CPCM Content formats is defined in TS 102 825-9 [5]. There is no mechanism of crypto-per... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.