HDCP规范1.1版：高带宽数字内容保护系统

5星 · 超过95%的资源需积分: 33 90 浏览量更新于2024-07-31 收藏 466KB PDF 举报

"HDCP Specification Rev1.1" HDCP（High-bandwidth Digital Content Protection，高带宽数字内容保护）是一种数字版权管理技术，旨在防止未经许可的复制和分发高质量的数字音频和视频内容。这个规范的版本1.1是在2003年6月9日发布的，由Digital Content Protection LLC制定。HDCP系统主要用于高清视频传输，如从蓝光播放器、游戏机、有线电视盒等设备到高清电视、投影仪等显示设备的信号传输。该文档指出，提供此规格书是“按原样”提供的，没有任何明示或暗示的保证，包括但不限于适销性、非侵权、适合特定目的或任何因提议、规格或样本而产生的其他保证。英特尔公司不承担与使用本规格书中信息相关的任何责任，特别是与侵犯任何知识产权有关的责任。文档中提到的加密功能可能受到美国、日本和其他政府的出口管制。这意味着使用HDCP技术的产品和服务可能需要遵守这些国家的法规，确保内容的安全传输。 HDCP规范的开发得到了Silicon Image Inc.的贡献。这表明在数字内容保护领域，多家公司可能会参与标准的制定和实施，以促进行业的共同标准和兼容性。 Intel Corporation拥有该技术的版权，而第三方品牌和名称则归其各自所有者所有。这表明HDCP是一种受到严格知识产权保护的技术，任何未经授权的使用都可能引起法律问题。在实际应用中，HDCP通过使用加密密钥和验证协议来确保只有经过授权的接收设备才能解码和显示受保护的内容。当源设备检测到连接的显示设备支持HDCP时，它会启用加密传输，阻止非HDCP兼容设备接收到未加密的信号，从而保护内容不被非法复制。 HDCP的实施涉及多个层次的认证和密钥交换，确保了内容在传输过程中始终保持安全。随着技术的发展，HDCP也经历了多次更新，例如HDCP 2.0和HDCP 2.2，以应对更高的分辨率和新的威胁模型。 HDCP Specification Rev1.1是数字媒体行业的一个关键标准，它对于保护高清晰度视频内容的版权至关重要，同时对设备制造商和消费者都具有深远影响。其复杂的加密机制和严格的授权体系是防止非法复制和分发高清内容的关键措施。

High-bandwidth Digital Content Protection System 9 June 2003

Revision 1.1 Digital Content Protection LLC

Page 14 of 85

In order to enhance the detection of the loss of encryption synchronization, the HDCP Transmitter and

Receiver may optionally support Enhanced Link Verification, in which a computation to aid verification of

cipher synchronization is performed when a specific video pixel is processed. For every 16

frame counter

increment, the decrypted value of channel zero of the first pixel is combined with the least significant byte

Rj using the XOR operation, and the result is made available on the Pj port. If this feature is supported by

an HDCP Receiver, the Bcaps bit 1.1_FEATURES is set and the Pj’ port is always updated. The HDCP

Transmitter may optionally support reading and verifying the Pj’ value against an internally generated Pj

value. However, unless a minimum of three successive mismatches of stable values occur, this is

considered to be a pixel transmission error and not an authentication or synchronization error. In addition,

the mismatched Pj values must be sampled more than once in the same manner as the Ri value. (see

Appendix C). Note that the frame counter may advance on unencrypted frames if ADVANCE_CIPHER

mode (see below) is enabled, in which case the least significant byte Rj and the pixel data is captured every

frame. However, if ADVANCE_CIPHER is not enabled, these values are updated on every 16

encrypted frame.

ADVANCE_CIPHER mode is an optional mode in which the cipher state and frame counter is advanced

for every frame in DVI mode, or for every frame when not in AVMUTE state for HDMI mode, regardless

of whether encryption is enabled or disabled. The HDCP Receiver indicates this capability by setting the

1.1_FEATURES Bcaps bit, and the HDCP Transmitters enables it by setting the

ENABLE_1.1_FEATURES bit in the Ainfo byte. The frame counter is first updated to a value of 1 when

the first ENC_EN is sent or received after authentication, and thereafter incremented every frame, until

SET_AVMUTE is set (in HDMI mode). The cipher state is not advanced if HDMI mode AV_MUTE is

active, and resumes advancing with the first ENC_EN frame after HDMI CLEAR_AVMUTE.

2.3 HDCP Transmitter State Diagram

The HDCP Transmitter Link State Diagram and HDCP Transmitter Authentication Protocol

State Diagram (Figures 2-5 and 2-6) illustrate the operation states of the authentication

protocol for an HDCP Transmitter that is not an HDCP Repeater. For HDCP Repeaters, the

downstream (HDCP Transmitter) side is covered in Section 2.5.

A variety of events are involved in the transmitter’s decision to begin authentication or to

transmit video. Some examples of such events may include hot plug detection of an attached

HDCP Receiver, completion of certain phases of the operating system, a software request, and

mode settings. HDCP receivers are not required to authenticate until presented with a video

signal. When an HDCP Receiver acknowledges an I

C register read, it must be ready to

authenticate, and, in the event of authentication failure, must be prepared to process

subsequent authentication attempts. The HDCP transmitter should not attempt to authenticate

until it has successfully obtained an acknowledged read of an HDCP I

C register. Should the

C register read or the authentication fail, the HDCP Transmitter must retry periodically, with

a period of no more than 2 seconds (preferably much more often). It may cease to attempt

authentication only if the HDCP Receiver is clearly disconnected, as with a hot-plug detach.

High-bandwidth Digital Content Protection System 9 June 2003

Revision 1.1 Digital Content Protection LLC

Page 16 of 85

Transition Any State:H0. Reset conditions at the HDCP Transmitter or loss of Hot Plug

Detect (HPD) cause the HDCP Transmitter to enter the No Receiver Attached state. Some

TMDS transmitters have the ability to directly sense the presence of a TMDS receiver

(Receiver Sense). If this signal is present and indicates the absence of an HDCP Receiver, it

should cause a transition to State H0.

Transition H0:H1. The detection of Hot Plug Detect indicates that a sink device is attached

and that the EDID ROM is available for reading.

State H1: Read EDID. Whenever HPD is active, the HDCP Transmitter must assume that

the receiver is available and displaying an image to the user. Consequently, the transmitter

should transmit an image to the screen as soon as feasible. Upon detection of HPD, the HDCP

Transmitter reads the EDID to determine the capabilities of the sink device, including whether

it is HDMI capable (refer to the HDMI Specification 1.0 for details). If both transmitter and

receiver are HDMI-capable, then the TMDS transmitter enters HDMI mode, otherwise, it

enters DVI mode.

Transition H1:H2. Immediately after transitioning to DVI mode, the transmitter should begin

sending an unencrypted video signal. This signal may be required before the registers of the

HDCP Receiver are visible to the HDCP Transmitter.

Transition H1:H3. Immediately after transitioning to HDMI mode, the transmitter should

begin sending a video signal. This signal may be required before the registers of the HDCP

Receiver are visible to the HDCP Transmitter.

Transition H2:A0, H3:A0. If content protection is desired by the Upstream Content Control

Function, then the HDCP Transmitter waits for the availability of an Active HDCP Receiver.

State A0: Wait For Active Receiver. In this state the HDCP Transmitter enables video to a

non-HDCP receiver with HDCP Encryption disabled. If no low value content is available or

appropriate, a “blue screen” or informative on-screen display should be transmitted. The

transmitter must repeatedly attempt to read an HDCP register, at least once every 2 seconds

and preferably much more often. Note that in most cases, if the user is watching video from a

different input, the Hot Plug Detect signal will still be asserted but the HDCP Receiver’s

registers will not be readable. Upon switching to the HDCP input, the user will wish to see

valid video within a fraction of a second or they may conclude that the HDCP input is not

connected and immediately switch to another input. For this reason, a valid video screen

should at all times be transmitted whenever HPD is asserted and authentication should be

started immediately after detecting a valid Bksv (Transition A0: A1).

Transition A0:A1. The successful read of an I2C HDCP register initiates the authentication

protocol.

State A1: Exchange KSVs. In this state, the HDCP Transmitter generates a 64-bit pseudo-

random value (An) and writes that value to the HDCP Receiver. The transmitter reads the

Bcaps register and determines the transport operating mode (DVI or HDMI). If necessary, it

sets Ainfo in the HDCP Receiver to determine the options that will be in effect prior to writing

its KSV (Aksv) to the HDCP Receiver. The HDCP Transmitter also reads the HDCP

Receiver’s KSV (Bksv) and the REPEATER status bit necessary for cipher initialization.

Generation of An using the HDCP Cipher is described in section 4.5.

Transition A1:A0. Failure to read Bksv containing 20 zeros and 20 ones is considered a

protocol failure and causes this state transition to State A0.

High-bandwidth Digital Content Protection System 9 June 2003

Revision 1.1 Digital Content Protection LLC

Page 17 of 85

Transition A1:A2. The random value An and HDCP Transmitter KSV have been written, and

a valid HDCP Receiver Bksv and REPEATER bit have been read. HDCP Transmitter has

confirmed that Bksv contains 20 ones and 20 zeros.

State A2: Computations. In this state, the HDCP Transmitter computes the values Km, Ks,

and R

, using the HDCP Transmitter’s Device Private Keys, Bksv read during State A1,

and the random number An written to the HDCP Receiver during state A1.

Transition A2:A3. When the computed results from State A2 are available, the HDCP

Transmitter proceeds to State A3.

State A3: Validate Receiver. The HDCP Transmitter reads R

' from the HDCP Receiver and

compares it with the corresponding R

produced by the HDCP Transmitter during the

computations of State A2. If R

is equal to R

', then HDCP Encryption is immediately

enabled. The verification timer is set up to generate timer events at the nominal rate of once

every two seconds, plus or minus one-half second. The HDCP Transmitter must allow the

HDCP Receiver up to 100 ms to make R

' available from the time that Aksv is written. The

HDCP Transmitter also checks the current revocation list for the HDCP Receiver’s KSV

Bksv. If Bksv is in the revocation list, then the HDCP Receiver is considered to have failed the

authentication. Note: checking the revocation list for Bksv may begin as soon as the Bksv has

been read in State A1, asynchronously to the other portions of the protocol, but it must

complete prior to the transition into the authenticated state (State A4).

The integrity of the current revocation list must be verified by checking the signature of the

SRM using the Digital Content Protection LLC public key, as specified in Section 5.

Transition A3:A0. The link integrity message R

received from the HDCP Receiver does not

match the value calculated by the HDCP Transmitter, or Bksv is in the current revocation list.

Transition A3:A6. The link integrity message R

received from the HDCP Receiver matches

the expected value calculated by the HDCP Transmitter and Bksv is not in the current

revocation list.

State A4: Authenticated. The HDCP Transmitter has completed the authentication protocol.

At this time, and at no time prior, the HDCP System makes available to the Upstream Content

Control Function upon request, information that indicates that the HDCP System is fully

engaged and able to deliver HDCP Content, which means (a) HDCP Encryption is operational

on each downstream HDCP-protected Interface Port attached to an HDCP Receiver, (b)

processing of valid received SRMs, if any, has occurred, as defined in this Specification, and

KSVs in the current revocation list.

Transition A4:A5. A verification timer event causes this transition to State A5.

State A5: Link Integrity Check. In this state, the HDCP Transmitter reads R

' from the

HDCP Receiver and compares that value against its value R

. If the values are not equal, then

the HDCP Receiver is incorrectly decrypting the transmitted stream. The R

' value may be re-

read to allow for synchronization and I

C bus errors. The HDCP Transmitter may also check

for a loss of synchronization with the HDCP Receiver (see Appendix C). If both the HDCP

Transmitter and HDCP Receiver are capable of the Enhanced Link Verification option, the Pj

values may be used to check for loss of synchronization more frequently than the Ri check.

Transition A5:A4. R

' from the HDCP Receiver correctly matches the expected value, Ri.

剩余84页未读，继续阅读

leo125

粉丝: 0
资源: 1

HDCP规范1.1版：高带宽数字内容保护系统

hdcp2.2_hdcp_hdcpkey_hdcp2.2key_hdcp2.2流程_miracastHDCP_

MTK Keys(hdcp） Partitioner_tools

HDCP.rar_HDCP DRM_HDMI_hdcp_hdcp d_hdmi标准

hisilicon_2_hdcp_HiSilicon_hdcpkey_

HDCP Specification Rev1_4_Secure_hdcp_HDCPSpecRev1_4_

hdcp.rar_hdcp

HDCP_Specification-Rev1.3-for-HDMI.rar_HDCP specification_HDMI_H

HDCP 2_2_IIA_Errata_v3.pdf

hdcp_key.rar_hdcp_hdcp key

HDCP Specification Rev1_4_Secure

最新资源