Common use of SOURCE FUNCTION OBLIGATIONS REGARDING COPY COUNT Clause in Contracts

SOURCE FUNCTION OBLIGATIONS REGARDING COPY COUNT. When a Source Function receives CC Content, it may not transmit or Transfer such CC Content except by using one or more of the methods set forth in this Section 4: 4.1 Transfer with a valid CC Field. A Source Function may Transfer CC Content with a valid CC Field to a Sink Function as follows: 4.1.1 The Transfer may occur only over a unique connection between that Source Function and a specific Sink Function established using a method set forth in the Specification, provided that: 4.1.1.1 The Source Function may establish a series of such unique connections with multiple individual specific Sink Functions in order to Transfer copies of such CC Content to each such Sink Function. 4.1.1.2 In any Transfer of CC Content (x) where the Transfer is to a single Sink Function, the Source Function shall set the CC Field to a number that is no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function, or (y) where a series of unique connections are established to multiple Sink Functions for Transfer of such CC Content to each such Sink Function, the Source Function shall set the CC Fields for such Transfers so that the sum of all of the CC Fields is a number no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function. 4.1.1.3 If the Transfer is being made from a Bound CC Recording, when the Source Function confirms that the transmission is complete, the Source Function shall ensure that the Licensed Product decrements the Number of Permitted CC Copies associated with the Bound CC Recording by the number of CC Copies that have been Transferred and shall otherwise comply with the requirements of Section 2.9 of Part 1 of this Exhibit B. 4.2 Transfer without valid CC Field (i.e. CC Field is 0000, or CC Field is not present). A Source Function may Transfer a single copy of CC Content to a single Sink Function (regardless of whether such Licensed Product has multiple Sink Functions), either without a CC Field or with a CC Field set to invalid as follows: 4.2.1: where the copy is made from a Bound CC Recording, by following the requirements of Section 3.1 (Move), except that the requirement in Section 3.1 to delete or render unusable the bound recording shall not apply and instead (a) the terms of Section 2.9 of Part 1 of this Exhibit B shall apply and (b) for purposes of such Section 2.9, the Number of Permitted CC Copies for CC Content Transferred pursuant to this Section 4.2 shall be deemed one;

SOURCE FUNCTION OBLIGATIONS REGARDING COPY COUNT. When a Source Function receives CC Content, it may not transmit or Transfer such CC Content except by using one or more of the methods set forth in this Section 4: 4.1 Transfer with a valid CC Field. A Source Function may Transfer CC Content with a valid CC Field to a Sink Function as follows: 4.1.1 The Transfer may occur only over a unique connection between that Source Function and a specific Sink Function established using a method set forth in the DTCP2 Specification, provided that: 4.1.1.1 The Source Function may establish a series of such unique connections with multiple individual specific Sink Functions in order to Transfer copies of such CC Content to each such Sink Function. 4.1.1.2 In any Transfer of CC Content (x) where the Transfer is to a single Sink Function, the Source Function shall set the CC Field to a number that is no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function, or (y) where a series of unique connections are established to multiple Sink Functions for Transfer of such CC Content to each such Sink Function, the Source Function shall set the CC Fields for such Transfers so that the sum of all of the CC Fields is a number no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function. 4.1.1.3 If the Transfer is being made from a Bound CC Recording, when the Source Function confirms that the transmission is complete, the Source Function shall ensure that the Licensed Product decrements the Number of Permitted CC Copies associated with the Bound CC Recording by the number of CC Copies that have been Transferred and shall otherwise comply with the requirements of Section 2.9 of Part 1 of this Exhibit B. 4.2 Transfer without valid CC Field (i.e. CC Field is 0000, or CC Field is not present). A Source Function may Transfer a single copy of CC Content to a single Sink Function (regardless of whether such Licensed Product has multiple Sink Functions), either without a CC Field or with a CC Field set to invalid as follows: 4.2.1: 4.2.1 where the copy is made from a Bound CC Recording, by following the requirements of Section 3.1 (Move), except that the requirement in Section 3.1 to delete or render unusable the bound recording shall not apply and instead (a) the terms of Section 2.9 of Part 1 of this Exhibit B shall apply and (b) for purposes of such Section 2.9, the Number of Permitted CC Copies for CC Content Transferred pursuant to this Section 4.2 shall be deemed one; 4.2.2 where the copy is not made from a Bound CC Recording, by transmitting the content using the Move protocols in the DTCP2 Specification.

SOURCE FUNCTION OBLIGATIONS REGARDING COPY COUNT. When a Source Function receives CC Content, it may not transmit or Transfer such CC Content except by using one or more of the methods set forth in this Section 4: 4.1 Transfer with a valid CC Field. A Source Function may Transfer CC Content with a valid CC Field to a Sink Function as follows: 4.1.1 The Transfer may occur only over a unique connection between that Source Function and a specific Sink Function established using a method set forth in the Specification, provided that: 4.1.1.1 The Source Function may establish a series of such unique connections with multiple individual specific Sink Functions in order to Transfer copies of such CC Content to each such Sink Function. 4.1.1.2 In any Transfer of CC Content (x) where the Transfer is to a single Sink Function, the Source Function shall set the CC Field to a number that is no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function, or (y) where a series of unique connections are established to multiple Sink Functions for Transfer of such CC Content to each such Sink Function, the Source Function shall set the CC Fields for such Transfers so that the sum of all of the CC Fields is a number no greater than the Number of Permitted CC Copies associated with the CC Content as received by the Source Function. 4.1.1.3 If the Transfer is being made from a Bound CC Recording, when the Source Function confirms that the transmission is complete, the Source Function shall ensure that the Licensed Product decrements the Number of Permitted CC Copies associated with the Bound CC Recording by the number of CC Copies that have been Transferred and shall otherwise comply with the requirements of Section 2.9 of Part 1 of this Exhibit B. 4.2 Transfer without valid CC Field (i.e. CC Field is 0000, or CC Field is not present). A Source Function may Transfer a single copy of CC Content to a single Sink Function (regardless of whether such Licensed Product has multiple Sink Functions), either without a CC Field or with a CC Field set to invalid as follows: 4.2.1: where the copy is made from a Bound CC Recording, by following the requirements of Section 3.1 (Move), except that the requirement in Section 3.1 to delete or render unusable the bound recording shall not apply and instead (a) the terms of Section 2.9 of Part 1 of this Exhibit B shall apply and (b) for purposes of such Section 2.9, the Number of Permitted CC Copies for CC Content Transferred pursuant to this Section 4.2 shall be deemed one;