hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.7 Local Master Election | The function and operation of the Local Master are described in clause 4.2.1. If a CPCM Instance is Local Master capable, it shall enter into election mode in two main circumstances: • the CPCM Instance is the Local Master Election initiator (e.g. because it has detected that no Local Master was present). In which case... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.8 AD Member Reconnection | Figure 13: AD Member or Domain Controller Connection/AD Update When an AD Member makes a network reconnection, it is called a reconnecting CPCM Instance and it shall perform the following: • First it shall perform the Discovery Protocol. • If the reconnecting CPCM Instance does not discover a Local Master from the same... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.9 Blank Instance Connection | Connected Blank Device Start Discovery Responses No Ask App. Create new AD App Response No Create New AD Yes Connected DC-LM 1 Domain Proposed AD proposed in invitation available Several Domains proposed Self-Managing Ask App. To select a domain App. AD selection Ask App. To Confirm AD Join Yes App. Confirms AD Join AD... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.10 AD Joining | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.10.1 Blank Instance Joining an AD | In order to become a Connected AD Member, the Blank Joining Instance shall perform the following steps as depicted figure 15: • It shall send an AD_join_begin_message to the Local Master that it has already found using the Discover process (see clause 5.1.1). • If no AD_join_ready_message response is received, the Blan... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.10.2 Local Master in AD Joining | Figure 16: Local Master in AD Joining Process ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 36 When receiving an AD Join Request, a Local Master that is not a Domain Controller first checks the AD capability of the requesting CPCM Instance: • If the requesting CPCM Instance is not ADM capable, the AD Join is refused, the Loc... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.10.3 Domain Controller in AD Joining | In order for the Domain Controller to be able to let a new Instance Join the AD, it shall perform the following tasks as depicted in figure 17. If the Domain Controller is also a Local Master, it may receive an AD Join request designating another Domain Controller. In that case, the Joining Domain Controller shall act ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.11 Instance Leaving the AD | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.11.1 AD Member Leaving | AD member leaving AD Leave Begin No Response AD Leave Ready AD Leave Commit AD Leave Confirm Connected AD member Connected Blank Device Transaction Rollback Ask App. To confirm AD Leaving Confirmed? No Secured Transaction Rollback Yes Disable AD Secret AD Leaving Completed AD Leave Finish Local Master messaging Start A... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.11.2 Local Master in AD Leaving | In order for the Local Master to enable another CPCM Instance to Leave the AD, it shall perform the following tasks as depicted in figure 19. When receiving an AD Leave request, a Local Master that is not a Domain Controller first checks whether the requesting Instance is from the same AD. If not, AD Leaving is refused... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.11.3 Domain Controller in AD Leaving | In order for the Domain Controller to be able to let an Instance Leave the AD, it shall perform the following tasks as depicted in figure 20. If the Domain Controller is also a Local Master, it may receive an AD_leave_begin_message designating another Domain Controller. In that case, it shall act as a Local Master for ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.12 Domain Controller Transfer | The function and operation of the Domain Controller are described in clause 4.2.2. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.12.1 AD Member becoming a Domain Controller | DC Transfer Begin No Response DC Transfer Ready DC Transfer Commit DC Transfer Confirm Local Master Election Launch Transaction Rollback Ask App. To confirm Transfer Confirmed? No Secured Transaction Rollback Yes Prepare to be DC Enable DC DC Transfer Finish Start DC Transfer AD Update Ind (Broadcast) Ask App. To confi... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.12.2 The Domain Controller Transfer process | In order for the Domain Controller to be able to Transfer its Domain Controller function, it shall perform the following tasks as depicted in figure 22. When receiving a Domain Controller Transfer request, a Domain Controller (whether Local Master or not) does the following. • If the requesting Instance is not Domain C... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.13 Domain Controller Splitting | The function and operation of the Domain Controller are described in clause 4.2.2. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.13.1 AD Member becoming an additional Domain Controller | DM becoming additional DC DC Split Begin No Response DC Split Ready DC Split Commit DC Split Confirm Connected AD member Transaction Rollback Which Balance? Confirmed? No Secured Transaction Rollback Yes Prepare to be additional DC Enable DC (to SEC) DC Split Finish Start DC Splitting AD Update Ind (Broadcast) Am I LM?... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.13.2 A Domain Controller is Split | In order for the Domain Controller to be able to Split its Domain Controller function, it shall perform the following tasks as depicted in figure 24. When receiving a Domain Controller Split request, a Domain Controller (whether Local Master or not) does the following: • If the requesting Instance is not Domain Control... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.14 Domain Controller Merging | The function and operation of the Domain Controller are described in clause 4.2.2. |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.14.1 The Merging Domain Controller | DC Merge DC Merge Begin No Response DC Merge Ready DC Merge Commit DC Merge Confirm Transaction Rollback Ask Appli to Confirm Confirmed? No Secured Transaction Rollback Yes Prepare to DC merge DC Merge Completed (to SEC) DC Merge Finish Am I LM? Connected DC Connected LM-DC No Yes Am I LM? Connected AD Member Election ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.14.2 The Merged Domain Controller | In order for the Domain Controller to be able accept the Merging of another Domain Controller function, it shall perform the following tasks as depicted in figure 26. When receiving a Domain Controller Merge request, a responding Domain Controller (whether Local Master or not) does the following: • It checks that the r... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.15 Domain Controller Rebalancing | The function and operation of the Domain Controller are described in clause 4.2.2. ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 56 |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.15.1 The Rebalancing Domain Controller | DC Rebalance DC Rebalance Begin No Response DC Rebalance Ready DC Rebalance Commit DC Rebalance Confirm Transaction Rollback Ask Appli to Confirm Confirmed? No Secured Transaction Rollback Yes Prepare to Rebalance DC Enable new ADSE counts DC Rebalance Finish LM messaging Am I LM? Connected DC Connected LM-DC No Yes As... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.1.15.2 The Rebalanced Domain Controller | In order for the Domain Controller to be able to be Rebalanced with another Domain Controller function, it shall perform the following tasks as depicted in figure 28. When receiving a Domain Controller Rebalance request, a responding Instance Domain Controller (whether Local Master or not) does the following: • The res... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.2 Abnormal Behaviour | In the normal course of events when a requesting Instance sends a message to another Instance, assuming that there is no time-out, the responding Instance shall always respond with the corresponding message type to the request, for example, an AD_discovery_response_message will be sent in response to an AD_discovery_re... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.3 Protocol Failure Recovery | The AD Joining, AD Leaving, Domain Controller Transfer, DC Split, DC Merge and DC Rebalance protocols have all been designed to be able to restart and finish successfully if they were unexpectedly interrupted (e.g. because of a power failure or a network problem that makes one of the two peers unreachable). The protoco... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.3.1 Client behaviour with a stored CIC Identifier | When a client with a stored CPCM Instance Certificate Identifier has sent a _commit message but not yet received a _confirm message, the following shall occur: • At the next Discovery (e.g. when a CPCM Instance reconnects), it checks whether the CPCM Instance with its stored CPCM identifier is connected. If the protoco... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.3.2 Server behaviour with a stored CPCM CIC Identifier | When a server with a stored CPCM Instance Certificate Identifier has received a _commit message but not yet a _finish message, the following shall occur: • It accepts any restart of the protocol by the relevant CPCM Instance. If it had already changed the ADSE values in the course of the protocol, it does not change th... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.4 Domain Internal Record | Each Domain Controller or Local Master is required to store information describing the current Authorized Domain (to which it belongs). This is optional for other AD Members. This information is called the Domain Internal Record. This information might be used in case a failure in one of the Domain Controllers that wou... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.4.1 Domain Internal Record information | Table 9 show the information gathered in Domain Internal Record. Table 9: Domain Internal Record Syntax Number of bits Meaning ADID 72 A globally unique identifier for the AD assigned by the CPCM Instance that initially created the AD, and is never changed thereafter (see TS 102 825-4 [2]). domain_controller_id 64 The ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 5.4.2 Domain Internal Record management | The Domain Internal Record is managed by a Domain Controller in the following way: • domain_controller_local_id is set to 0 for the Domain Controller that created the Authorized Domain. • domain_controller_local_id is unchanged upon Domain Controller Transfer. • At each Domain Controller Split, an unused domain_control... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.1 AD Creation | AD creation is initiated by a Device Application request when an AD aware Blank Instance connects for the first time where no AD currently exists. The ADM component requests its Security Control to create the new Authorized Domain by a create_new_AD_message. Upon receiving such a request, Security Control first checks ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.2 Domain Controller Leaving | Upon request of its ADM component to Leave the AD, the Security Control of a Domain Controller does the following: • It erases its AD Secret and ADID. • It sets all the ADSE values to 0. • It becomes a Blank Instance. It confirms the completion of the AD Leave to the ADM component. If it was not a Domain Controller, a ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.3 AD Joining | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.3.1 Blank Instance Joining an AD | The Security Control is involved at five steps during the AD Join. The next five steps below shall be executed in the described order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop. 1) First, when connecting, the Blank Instance checks with its Sec... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.3.2 Local Master in AD Joining Process | The Local Master (that is not Domain Controller) intervenes at two stages during the AD Join process. These two steps shall be conducted in order, if there is a failure at any stage it shall be reported as a protocol error and the process shall end: 1) Upon receipt of an AD_join_begin_message, it establishes a SAC with... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.3.3 Domain Controller in AD Joining protocol | For a non ADSE countable Instance, the Domain Controller Security Control behaves exactly as a Local Master for the same case. For an ADSE countable Instance, the Domain Controller Security Control is active in three stages. These steps shall be conducted in order, if there is a failure at any stage it shall be reporte... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.3.4 Other AD Members | At any moment, the Security Components of other AD Members that are ADSE countable shall be ready to perform a Quorum Test with the Domain Controller. To that end, it shall respond to any ADM_quorum_test_query_message carrying the relevant ADID with message ADM_quorum_test_response_message. It shall also be ready to pe... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.4 AD Leave | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.4.1 AD Member Leaving | The Security Control is involved at four steps during the AD Leave executed in the following order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop: 1) After the AD_leave_begin_message is sent, it will accept the challenge to run the SAC establishme... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.4.2 Local Master in AD Leaving Process | The Local Master (that is not a Domain Controller) intervenes at three stages during the AD Leaving process. These three steps shall be conducted in order, if there is a failure at any stage it shall be reported as a protocol error and the process shall end: 1) Upon receipt of an AD_leave_begin_message, it verifies tha... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.4.3 Domain Controller in AD Leaving protocol | For a non ADSE countable Instance, the Domain Controller Security Control behaves exactly as a Local Master for the same case. For an ADSE countable Instance, the Domain Controller Security Control is active in four stages. These steps shall be conducted in order, if there is a failure at any stage it shall be reported... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.5 Domain Controller Transfer | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.5.1 AD Member becoming a Domain Controller | The Security Control is involved at four steps during the Domain Controller Transfer which shall be executed in the following order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop: 1) After the DC_transfer_begin_message is sent, it will accept the ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.5.2 Domain Controller Transfer Process | The Domain Controller Security Control is active in three stages. These steps shall be conducted in the order described below, if there is a failure at any stage it shall be reported as a protocol error and the process shall end. 1) The ADM component requests its Security Control to prepare for the DC Transfer. To that... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.6 Domain Controller Split | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.6.1 AD Member becoming an additional Domain Controller | The Security Control is involved at four steps during the Domain Controller Split; these steps shall be executed in the described order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop. 1) After the DC_split_begin_message is sent, it will accept the... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.6.2 Domain Controller in Splitting process | The Domain Controller Security Control is active in three stages. These steps shall be conducted in order, if there is a failure at any stage it shall be reported as a protocol error and the process shall end. 1) The ADM component requests its Security Control to prepare to the Split. To that end, the Security Control ... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.7 Domain Controller Merge | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.7.1 Merging Domain Controller | The Security Control is involved at four steps during the Domain Controller Merge which shall be executed in the described order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop. 1) After the DC_merge_begin_message is sent, it will accept the challe... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.7.2 Merged Domain Controller process | The Domain Controller Security Control is active in four stages which shall be conducted in order, if there is a failure at any stage it shall be reported as a protocol error and the process shall end. 1) The ADM component requests its Security Control to prepare to DC Merge. To that end, the Security Control checks wh... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.8 Domain Controller Rebalance | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.8.1 The Rebalancing Domain Controller | The Security Control is involved at four steps during the Domain Controller Rebalance which shall be executed in the described order. Any inversion or omission shall result in a negative result and any failure of one step will cause the process to stop. 1) After the DC_rebalance_begin_message is sent, it will accept th... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 6.8.2 Rebalanced Domain Controller | The Domain Controller Security Control is active in four stages which shall be conducted in order, if there is a failure at any stage it shall be reported as a protocol error and the process shall end. 1) The ADM component requests its Security Control to prepare to be Rebalanced. To that end, the Security Control chec... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7 Generic ADSE tools (optional) | |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.1 Single Household Metric (SHM) | The SHM tool provides a means to associate an AD with a unique household. Examples of an SHM include requirements of the use of a password/PIN, security dongle, or other anonymous household identification metric prior to performed AD-related functions, such as an AD Join, or prior to allowing AD-related usage. NOTE: In... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.2 Total AD Count (TAC) | The Total AD Count tool shall use the following data field: total_ceiling, which will be protected against unauthorized modification. If the number of Instances in the AD would exceed total_ceiling though the addition of another Instance, then this test shall return a result that the "ADSE would be exceeded". If an Ins... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.3 Total and Remote AD Count (TARC) | The TARC tool shall use the following data fields: total_ceiling and remote_ceiling, which will be protected against unauthorized modification. AD Joining can be limited to only Instances that are Local to one AD member Instance. The details of the definition of Local (to any AD Instance or a number of AD Instances) wi... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.4 Total and Remote AD Count + (TARC+) | The TARC+ tool shall use the following data fields: total_ceiling, remote_ceiling, connected_device_floor, which will be protected against unauthorized modification. This tool is the same as the TARC tool with an additional rule regarding the minimum number of AD Members that must be connected to allow an AD Join. Quor... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.5 Quorum Test | The Quorum Test tool shall use the following data fields: total_ceiling, local_ceiling and remote_ceiling, which will be protected against unauthorized modification. The Quorum Test expands on the TARC Tool. In TARC: Number of local CICF Joins that can be allowed = total_ceiling - remote_ceiling Or total_ceiling= Deriv... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.6 Domain Membership History (DMH) | The DMH tool shall use the history_ceiling data field, which will be protected against unauthorized modification. This tool limits the number of times that a CPCM Instance may Join new ADs. The history_ceiling field can be modified by an ADM Authorized Authenticated Agent (ADMAAA), e.g. increased to allow more Joins. E... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 7.7 Wayfaring Device Limits (WDL) | The WDL tool shall use the following data fields: disconnnected_time_limit and remote_time_limit, which will be protected against unauthorized modification. These two fields provide the ability to expire the membership of a CPCM Instance in an AD and can be used for both fraud detection/action and lost device count rec... |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 8 ADM message structure and elements | Please see the System Specification (TS 102 825-4 [2]) for the definition of ALL CPCM messages. Please see TS 102 825-4 [2] for the actual messages that are exchanged over the ADM1 Interface (see figure 3) between Authorized Domain Management Instances. ETSI ETSI TS 102 825-7 V1.2.1 (2011-02) 78 |
fa7561cd985e031c9c1e179fd41729e4 | 102 825-7 | 8.1 Local Master Delegation | When receiving a message from an AD Member that needs to be delegated, the Local Master places the requesting CPCM Instance Certificate Identifier in the delegating_instance_id field. The Domain Controller shall answer with the same delegating_instance_id field. Then, the Local Master returns the message to the request... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 1 Scope | The present document specifies the Security Specification for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. |
747818b49536d6fef162edf23646da2c | 102 825-5 | 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... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 005: Guidelines for the use of compression formats over IPDigital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in DVB services delivered directly over IP protocols"Digital Video... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 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. |
747818b49536d6fef162edf23646da2c | 102 825-5 | 3 Definitions, abbreviations and notation | |
747818b49536d6fef162edf23646da2c | 102 825-5 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [4] apply. |
747818b49536d6fef162edf23646da2c | 102 825-5 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [4] apply. |
747818b49536d6fef162edf23646da2c | 102 825-5 | 3.3 Notation | The present document uses the following notation throughout: Table 1: Notation Scope Notation Meaning Hashes H(M) The Hash of message M. H(X,Y) The Hash of the concatenation of messages X and Y, X being first. MAC MAC{K}(M) The MAC of message M using key K. Encryption E{K}(M) Encryption of message M using key K. Decryp... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4 Cryptographic Algorithms | |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.1 Hash function | CPCM compliant implementations shall use the SHA-1 hash algorithm described in [3]. ETSI ETSI TS 102 825-5 V1.2.1 (2011-02) 7 |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.2 Message Authentication Code | CPCM compliant implementations shall use the HMAC Message Authentication Code generation and verification algorithm described in [6]. NOTE: Message Authentication Code are sometimes also named signature when the key is AD Secret or SAC Session key. |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.3 Symmetric cipher | CPCM compliant implementations shall use the symmetric cipher algorithm Advanced Encryption Standard (AES) with 128-bit key length as described in [7]. For SAC protection, cipher is used in Cipher Block Chaining (CBC) mode as described in [8] with a fixed Initialization Vector (IV) value for both Licence Protection and... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.4 Revocation Lists Digital Signature | Revocation Lists are signed using RSASSA-PKCS1-V1_5-SIGN described in PKCS #1 v2.1 [10]. CPCM compliant implementations do not need to implement RSASSA-PKCS1-V1_5-SIGN. Revocation Lists signatures are verified using RSASSA-PKCS1-V1_5-VERIFY described in PKCS #1 v2.1,[10]. The public exponent used in the signature proce... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5 Local Scrambler Algorithm (LSA) | The LSA described in this clause shall be used to protect Content within compliant CPCM systems. The LSA uses the AES cipher described in [7] as its basic building block, with 128-bit keys, called Control Words (CWs). The basic unit of scrambling (or descrambling) is called a packet. Each packet is scrambled independen... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.1 Control signals and parameters | Figure 2 shows the scrambling/descrambling process on a very high level. The length of the MSC Part is denoted as MSCL. Table 2: lists the LSA parameters and control signals. Scram bling Process Descram bling Process Payload MSC Part MSCL Packet Length Scrambled Payload MSC Part (clear) MSCL Figure 2: High-level view o... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.1.1 IV for encryption payload preparation and Short Solitary Block Handling | Figure 4 shows the preparation process for the initial value used in the scrambling of the first payload block, i.e. the Effective IV (IVE), on the left side, and the Short Solitary Block Handing (SSBH) process, on the right side. These processes are independent of the Chaining Mode, CBC or RCBC, although the value of ... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.2 CBC Chaining Mode | Figure 5 shows the CBC encryption (top part) and decryption (bottom part) of n plaintext blocks P1…Pn and ciphertext blocks C1…Cn. The left side shows the case that the non-MSC Data in a packet constitutes an exact number of basic blocks (i.e. is a multiple of 16 bytes). The right side shows the Ciphertext Stealing (CS... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.3 RCBC Chaining Mode | Figure 6 shows the RCBC encryption (top part) and decryption (bottom part) of n plaintext blocks P1…Pn and ciphertext blocks C1…Cn, organised as n/2 super blocks. The part on the right shows the Ciphertext Stealing (CS), which is only used if the size of the last block, Pn and Cn, is less than a basic block. The encryp... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.4 Summary of CBC and RCBC scrambling/descrambling process | If at least 16 bytes need to be scrambled/descrambled this is done using either CBC or RCBC, possibly with Ciphertext Stealing. The process can be summarized as follows. Table 4:Scrambling modes Mode Action Do if nr bytes left bytes left afterwards Next action CBC CBC (nr = n) or (nr ≥ 2n) 0 or ≥ 2n CBC or CS CS n < nr... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.5 LSA - Normative Specification | This clause provides the formal description of the LSA. Inputs, outputs, arrays and addition are as defined in clauses 3.1, 3.2, 3.3 and 4.1 in [6]. If Chaining Mode is CBC, the IVseed is: IVseed=f(MSCL, Packet Length) where f is defined in table 3. Else, IVseed=IVseedConstant; where IVseedConstant is given in clause 6... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.5.6 MPEG-2 Transport Stream adaptation | This clause describes the adaptation of the LSA to scramble/descramble MPEG-2 Transport Streams as described in [1]. The unit of scrambling is a 188-byte MPEG-2 Transport Stream (TS) packet. The MSC Part of a packet consists of the header and the (optional) Adaptation Field (AF) bytes. In MDD mode: The transport error ... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.6 Certificate verification | Certificate signature verification shall be performed using RSA with recovery and fixed exponent e. The Certificate signature shall be verified using the following steps: 1) Identify the public RSA signature key used to sign the certificate and the corresponding certificate, henceforth designated as the parent certific... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.7 Certificate keys and digest generation | This clause is provided as reference for Certificate Providers. CPCM Instances need not implement the described algorithm. CPCM Certificate keys depends on the type of the certificate. A CPCM Signing Certificate contains a compressed RSA modulus, whereas a leaf Certificate contains a public Diffie-Hellman key. CPCM Cer... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.8 Revocation List verification | When a new Content Revocation List is received, a CPCM Instance shall first verify that list and if this succeeds proceed to check the revocation status. If the verification fails, the new Revocation List shall be ignored and discarded. The CPCM Instance shall verify all new Revocation Lists as follows: 1) If the recei... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 4.9 Secure time management | A CPCM Instance may be able to securely determine both Secure Absolute Time and Secure Relative Time as described in the following: 1) Secure Absolute Time. This measures CPCM date and time as defined in the System Specification (TS 102 825-4 [5]). The way to implement such a Secure Absolute Time source is out of the s... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 5 Cryptographic Protocols | |
747818b49536d6fef162edf23646da2c | 102 825-5 | 5.1 Authenticated Key Exchange (AKE) | DVB CPCM compliant implementations shall use the following protocol to establish trust and create a SAC. The protocol is based on Diffie-Hellman. Each CPCM entity shall have a private key (Kpriv) and a Certificate that embeds an identity (e.g. the Certificate serial number) and the public key (Kpub=gKpriv mod p where g... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 5.2 Trust Management | Each CPCM Instance has CPCM credentials in the form of a Certificate chain that provides the Instances public key and other attributes. Trust establishment between different CPCM Instances shall be based on Certificate chain exchange and verification. The Certificate chain has a tree hierarchy with a single source of t... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 6 Formats and definitions | |
747818b49536d6fef162edf23646da2c | 102 825-5 | 6.1 Certificate format | Table 7 shows the CPCM Instance Certificate after verification as defined in clause 4.6. Table 8 shows the structure of the certificate body, which corresponds to the Certificate field blocks, M2,…,M8, that are recovered as part of the Certificate verification process. This structure is described in detail in TS 102 82... |
747818b49536d6fef162edf23646da2c | 102 825-5 | 6.2 Revocation List hierarchy | The revocation list format can be found in TS 102 825-4 [5]. CPCM Compliant devices shall support a simple two level root and branch Revocation List hierarchy as in figure 9. Figure 9: Revocation List Hierarchy ETSI ETSI TS 102 825-5 V1.2.1 (2011-02) 23 |
747818b49536d6fef162edf23646da2c | 102 825-5 | 6.3 Cryptography Toolbox parameters | CPCM compliant implementations shall use the following parameters. Table 10: Cryptography Toolbox parameters Context Parameter Value Certification Public Exponent e=216+1=65537 RSA modulus size 2048 bits IVcertificate C0 AC 29 B7 C9 7C 50 DD 3F 84 D5 B5 B5 47 09 17 C 24 3F 6A 88 85 A3 08 D3 13 19 8A 2E 03 70 73 44 SAC ... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 1 Scope | The present document is the specification of the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) System. It contains the generic specification applicable to all deployments of CPCM. Technology-specific adaptations for content formats, storage formats, home network ecosystems and applicati... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems". [2] IEEE List of Registered OUI. NOTE: Available at http://standards.ieee.org/regauth/oui/index.shtml. [3] ISO... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [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... |
bd3d0428f407f7867a0c202a7c97ce88 | 102 825-4 | 3 Definitions and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.