Title of Invention

"METHOD FOR THE ANONYMOUS AUTHENTICATION OF A DATA TRANSMITTER"

Abstract

A method for verifying that data received by a receiver (2) have been sent by a transmitter (1,3) authorized by a trusted third party, the transmitter and the receiver being connected to a digital network, characterized in that an identifier (IdEvent) for data sent by the transmitter is sent with said data and in that the method comprises the steps consisting, for the receiver (2), in: (a) generating a random number (C); (b) broadcasting said random number and said identifier (IdEvent) over the network; (c) receiving from the transmitter a response (R) computed by applying a first function (G) to said random number (C) and to said identifier (IdEvent); (d) verifying the received response (R) by applying a second function (H) to the received response (R), to said random number (C) and to said identifier (IdEvent); the first function (G) having previously been delivered to the transmitter by the trusted third party and the second function (H) being a function for verifying the result of the first function, previously delivered by the trusted third party to the receiver.

Full Text

Method for the anonymous authentication of a data transmitter Field of the invention The present invention relates to the secure exchange of data over a network linking various devices and to the authentication of the source of data sent over a network. State of the art In certain cases, it is necessary for a data receiver device to be sure that the transmitter that has transmitted the data was indeed authorized to do so by a trusted third party without the receiver of the data knowing the identity of the transmitter, the data also being likely to be relayed by an intermediate device. All known schemes of authenticating a data transmitter imply that the receiver of the data knows the transmitter. Summary of the invention One aim of the invention is therefore to propose a method by which a transmitter of data can prove that it was indeed authorized to transmit the data by a trusted third party without the receiver of the data knowing the identity of the transmitter. Accordingly, the invention concerns a method for verifying that data received by a receiver have been sent by a transmitter authorized by a trusted third party, the transmitter and the receiver being connected to a digital network. According to the invention, an identifier is associated with the data sent by the transmitter and the method comprises the steps consisting, for the receiver, in: (a)generating a random number; (b)bradcasting said random number over the network; (c) receiving from the transmitter a response computed by applying a first function to said random number and to said identifier; and (d)verifying the received response by applying a second function to the received response, to said random number and to said identifier; the first function having previously been delivered to the transmitter by the trusted third party and the second function being a function for verifying the result of the first function, previously delivered by the trusted third party to the receiver. The transmitter may be either the initial transmitter of the data in the network, or an intermediate device between the initial transmitter and the receiver of the data which has for example stored the data transmitted by the initial transmitter. According to a variant of the invention, the step (b) is replaced by a step consisting in sending the random number to the transmitter. According to an embodiment of the invention, the receiver inhibits access to the data if the response received in the step (c) is not correct or if no response is received after the expiry of a predetermined time starting from the transmission of the random number. The identifier associated with the data sent by the transmitter is preferably a random number generated by the initial transmitter of the data in the network and attached to these data by the initial transmitter. Naturally, this identifier gives no information on the identity of the transmitter. The invention also relates to a method for proving that data sent to a receiver have been transmitted by a transmitter authorized by a trusted third party, the transmitter and the receiver being connected to a digital network. According to this aspect of the invention, an identifier is associated with the data sent by the transmitter and the method comprises the steps consisting, for the transmitter, in: (a) receiving a random number from the receiver; (b) computing a response by applying a first function to said random number and to said identifier; (c) sending the response to the receiver. The response is likely to be verified by the receiver by applying a second function to the received response, to said random number and to said identifier; the first function having previously been delivered to the transmitter by the trusted third party and the second function being a function for verifying the result of the first function, previously delivered by the trusted third party to the receiver. According to the principle of the invention, a trusted third party delivers to all the devices likely to be initial or intermediate transmitters in a network, the first function used to compute the response in the context of the above method. The trusted third party also delivers to all the devices likely to be receivers in the network, the second function for verifying the response computed with the aid of the first function. Brief description of the drawings The invention will be better understood on reading the description that follows, given only as an example and made with reference to the appended drawings in which: -figure 1 represents a domestic digital network in which the invention is embodied; - figures 2 and 3 illustrate two exemplary embodiments of the invention. Detailed description of the embodiments of the invention On the basis of the principle of the invention explained above, several scenarios are possible. According to a first scenario, a first transmitter, that will be called Alice, and a second transmitter, that will be called Charlie, transmit messages respectively called MA and Mc over a network to which a receiver, that will be called Bob is connected. With the message MA Alice transmits an identifier IdEventA which identifies the message MA and with the message Mc Charlie transmits an identifier IdEventc which identifies the message Mc. Alice and Charlie who are both connected to the network receive respectively the messages Mc and MA transmitted by the other transmitter of the network, but they do not retain them. Bob also receives the two messages and it is assumed that he wants to retain only the message MA. To be sure that MA comes from a source authorized by a trusted third party, Bob launches a challenge/response protocol in the following manner. Bob generates a random number C (the challenge) then broadcasts it over the network. Alice and Charlie both receive the challenge C. Prior to this, it is assumed that the trusted third party has delivered to Alice and Charlie a response computation function G and has delivered to Bob a corresponding response verification function H such that this function H returns 0 if the response is incorrect and 1 if the response is correct. When Alice and Charlie receive the challenge C transmitted by Bob, they compute respectively responses RA and Re as follows: Alice: RA = G(ldEventA, C); Charlie: Rc = G(ldEventc, C); then they send respectively the responses RA and Rc to Bob. Bob then verifies each response by computing H(C, Rx, IdEventx) where X = A and C. If all the results returned by the function H are zero, then Bob does not retain the message MA which is considered as not originating from a safe source. On the other hand, if at least one result returned by H equals 1 (in the example, it will be H(C, RA, IdEventA)), then Bob accepts the message MA because he is sure that it originates from a transmitter authorized by the trusted third party. According to a second scenario, a transmitter, Alice, broadcasts a message MA accompanied by an identifier IdEventA over a network to which a receiver Bob and an intermediate entity, that will be called Deborah, are connected. Initially, it is supposed that Bob is not interested in the message MA and that he does not retain it. Deborah however stores the message MA and its identifier IdEventA. Later, when Alice is no longer broadcasting any message, it is supposed that Deborah broadcasts the stored message MA and its identifier IdEventA over the network. Alice, being a transmitter only, does not retain MA. Bob receives MA and wants to retain it. To ensure that it originates from a source authorized by a trusted third party, Bob launches a challenge/response protocol in the following manner. Bob generates a random number C (the challenge) then broadcasts it over the network. Previously, it is supposed that the trusted third party has delivered to Alice and Deborah a response computation function G and has delivered to Bob a corresponding response verification function H such that this function H returns 0 if the response is incorrect and 1 if the response is correct. Alice and Deborah receive the challenge C. Since Alice is not transmitting a message, she does not take account of the challenge C. Deborah however computes a response RD = G(ldEventA, C) and sends this response to Bob. Bob then verifies this response by computing H(C, RD, IdEventA). If the function H returns 0, then Bob does not retain the message MA. On the other hand, if the function H returns 1, then Bob accepts the message MA which is considered as originating from an authorized source. It will be noted that in the two scenarios described above, the receiver entity Bob, even though he is capable of responding to the source of the message, does not know whether the message he receives originates from a transmitter (such as Alice) or from an intermediate device (such as Deborah) and above all he does not know the identity of the transmitter of the message MA. A description will now be given of a more concrete examplary embodiment of the invention with reference to figure 1 in which an STB (Set Top Box) decoder 1, a DTV (Digital Television) receiver 2 and an SU (Storage Unit) 3 are represented. It is supposed that the data broadcast over this network represent audiovisual programs comprising Audio and Video bit streams transported in a data transport stream as defined in the standard ISO/IEC 13818-1 "Information technology - Generic coding of moving pictures and associated audio information: Systems". The decoder 1 represents a transmitter of data over the network; it transmits data that it receives for example from a satellite antenna or from a cable connection. The digital television 2 represents a receiver of data over the network. The storage unit 3 for its part represents an intermediate device capable of retransmitting over the network data received from another transmitter device of the network. These three devices are connected to a digital bus 4, for example a bus according to the IEEE 1394 standard, and thus form a digital home network. The messages transmitted over the network are sent via the isochronous channel of the bus 4 and the messages that are addressed are sent via the asynchronous channel of the bus 4. The trusted third party which delivers a function G for computing a response to a challenge/response protocol to the transmitter or intermediate devices of the network (in our example, the decoder 1 and the storage unit 3) and which delivers a response verification function H to the receiver devices of the network (in our example the digital television 2) is for example the manufacturer of the devices. As concerns the choice of the functions G and H, three embodiments will be envisaged. According to a first preferred embodiment, the function G is a public function that uses a secret key K in order to compute a response R based on a challenge C and on an identifier IdEvent (i.e. R = G«(C, IdEvent)). To guarantee that the transmitter or intermediate devices are compliant devices, authorized by the trusted third party, the secret K is inserted into these devices, in a secure storage zone that must not be subsequently accessible (for example in a secure processor, particularly included in a smart card). The function H is in this case a function that computes a response R' based on the challenge C and on the identifier IdEvent by applying the function G with the secret key K and which then compares the result R' with the received response R. H is a boolean function which delivers a zero value "0" if R' is different from R and which delivers a "1" value if R' equals R. In this case, the secret key K must also be previously inserted by the trusted third party into the receiver devices. A function G corresponding to the above definition may in particular be an encryption function such as the AES function described in particular in TIPS 197: Specification of the Advanced Encryption Standard (AES) - 26 November 2001" available at the following Internet address: http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf. It may also be a hashing function such as the HMAC-SHA1 function described in particular in "FIPS Publication 198: The Keyed-Hash Message Authentication Code (HMAC), National Institute of Standards and Technology, 2001" available at the following Internet address: http://csrc.nist.gov/publications/fips/fips198/fips-198a.pdf. In a second embodiment, the function G is a secret function that is inserted into the transmitter or intermediate devices considered to be compliant and authorized by the trusted third party. Preferably, this function must be chosen in order to be very difficult to find by analyzing the products that contain it. In addition, this function must be resistant to adaptive chosen-plaintext attacks. As in the first embodiment, the function H is in this case a boolean function which computes a response R' based on the challenge C and on the identifier IdEvent by applying the secret function G and which then compares the result R' with the received response R, delivering a zero value "0" if R' is different from R and delivering a "1" value if R' equals R. In this embodiment, the secret function G must therefore also be previously inserted by the trusted third party into the receiver devices. In a third embodiment, the functions G and H are public functions using a pair of asymmetric keys (private key/public key). The function G is for example a function for generating a signature with the aid of a private key and the function H is a function for verifying a signature with the aid of the corresponding public key. For example the RSA (Rivest, Shamir and Adleman) signature functions will be used as follows: R = G(C, IdEvent) = RSASignKPRi(C, IdEvent) and H(C, R, IdEvent) = RSAVerifKPUB(C, R, IdEvent); where KPRI and KPUB are the private key and the public key of one and the same pair of RSA keys. In this case, the private key is inserted into the transmitter or intermediate devices of the network by the trusted third party and the public key is inserted into the receiver devices of the network. It will be assumed in what follows that the first embodiment has been chosen in which the function G is the HMAC-SHA1 function and that a secret key K is included in an inviolable storage zone of the decoder STB 1, of the digital television receiver DTV 2 and of the storage unit SU 3. First scenario: the STB transmits a program directly to the DTV As illustrated in figure 2, when the user of the decoder STB 1 selects a new program so that it is broadcast in the network, the STB randomly generates a program identifier IdEvent (step 20), which is preferably a number of 128 bits and it inserts this identifier into the messages contained in the packets transporting the data representing the program. The data transport stream is then broadcast over the network (on the isochronous channel of the bus 4) during the step 21. It is received by the digital television DTV 2 which extracts the messages containing the identifier from the received data packets in order finally to retrieve this identifier IdEvent (step 22). The DTV then generates in step 23 a challenge C which is preferably a random number of 128 bits, and it broadcasts this challenge C over the network during the step 24. When the STB receives the challenge C, it computes the response in the step 25: R = G(C, IdEvent), or more precisely: RSTB = HMAC-SHA1K(C, IdEvent) and addresses this response to the DTV via the asynchronous channel of the bus 4 (step 26). The storage unit SU 3, which also receives the challenge C does not respond since it is not in the process of transmitting data. When the DTV receives the response R=RSTB from the STB, it applies the function H (R, C, IdEvent) to verify the response R (step 27) which means computing: RDTV = HMAC-SHA1K(C, IdEvent) and comparing this result with the received response RSTB- If the two values are the same, then the DTV considers that the received program originates from a transmitter authorized by the trusted third party and can be presented to the user. Otherwise, the DTV does not display the received program to the user. If the DTV receives no response after a predetermined time has elapsed since the challenge C was sent over the network, it also blocks the display of the received program. At the end of the protocol, the challenge C and the identifier IdEvent are erased from the memories of the STB and the DTV. Second scenario: the STB transmits a program that is stored by the SU which subsequently transmits it to the DTV. This scenario is illustrated by figure 3. Initially, it is assumed that the user of the STB selects a new program. The STB then generates an identifier IdEvent (step 30) as in the first scenario above and it inserts this identifier into messages included in the data transport packets representing the program before broadcasting the data transport stream over the network (step 31). The SU then stores the data stream representing the program. The user has for example chosen not to view immediately the program that is broadcast by the decoder and prefers to store it in order to play it back later. Secondly, the user wants to play back the stored program. The SU therefore broadcasts the program over the network during a step 32. The DTV receives the data packets and extracts from them the messages containing the identifier IdEvent in step 33. The DTV then generates a challenge C as in the first scenario (step 34) and it broadcasts this challenge over the network (steps 35, 35'). The SU receives this challenge C, so it computes the response in step 36: R = G(C, IdEvent), or more precisely: Rsu = HMAC-SHA1K(C, IdEvent) and addresses this response to the DTV via the asynchronous channel of the bus 4 (step 37). The STB which is not in the process of broadcasting data does not respond to the challenge C which it also receives. When the DTV receives the response R=Rsu from the SU, it applies the function H (R, C, IdEvent) to verify the response R (step 38) which involves computing: RDTV = HMAC-SHA1K(C, IdEvent) and comparing this result with the received response Rsu- If the two values are the same, then the DTV considers that the received program originates from a transmitter authorized by the trusted third party and can be presented to the user. In the contrary case, or when no response has been received after a predetermined time after the challenge C was sent by the DTV, the latter does not display the received program to the user. It will be noted that when the STB has finished transmitting the program initially, it then erases the identifier IdEvent from its memory. At the end of the protocol, the challenge C and the identifier IdEvent are also erased from the memories of the SU and the DTV. In a variant embodiment of the invention, particularly in the two scenarii explained above, it is possible to replace the step of broadcasting over the network the challenge C computed by the DTV with a step of sending this challenge C to the transmitter of the data (the STB in the first scenario or the SU in the second scenario). In this case, only the transmitter of the data receives the challenge C. Specifically, the existing digital network management protocols allow a receiver of data to respond to the source of the data without knowing its identity. In another variant embodiment, the receiver of the data broadcasts over the network, in addition to the challenge C, the identifier IdEvent associated with the data that it has received (for example in step 24 in figure 2, or in step 35, 35' in figure 3). Each transmitting network appliance that receives the challenge C and the identifier IdEvent verifies whether it should respond to this challenge by comparing the received identifier IdEvent with that which it may just have generated in order to broadcast data. The transmitter responds only if the identifier received with the challenge corresponds to its current identifier IdEvent. This prevents all the transmitters that are broadcasting data in the network from responding when a challenge C is sent by a receiver. The invention has the following advantages in particular: Even if several transmitter or intermediate devices are connected to the network, only that which has been authorized by the trusted third party and which has sent the data is capable of responding to the challenge/response protocol initiated by the receiver of the data. The protocol does not divulge any information concerning the transmitter to the receiver. This achieves the objective of an anonymous authentication of the transmitter device. The protocol is based only on the application layer and requires no special feature on the data transport layer. We claim: 1. A method for verifying that data received by a receiver (2) have been sent by a transmitter (1, 3) authorized by a trusted third party, the transmitter and the receiver being connected to a digital network, characterized in that an identifier (IdEvent) for data sent by the transmitter is sent with said data and in that the method comprises the steps consisting, for the receiver (2), in: (a) generating a random number (C); (b) broadcasting said random number and said identifier (IdEvent) over the network; (c) receiving from the transmitter a response (R) computed by applying a first function (G) to said random number (C) and to said identifier (IdEvent); (d) verifying the received response (R) by applying a second function (H) to the received response (R), to said random number (C) and to said identifier (IdEvent); the first function (G) having previously been delivered to the transmitter by the trusted third party and the second function (H) being a function for verifying the result of the first function, previously delivered by the trusted third party to the receiver. 2. The method as claimed in claim 1, wherein step (b) is replaced by a step consisting in sending said random number (C) to the transmitter. 3. The method as claimed in any one of clams 1 to 2, wherein the receiver inhibits access to said data if the response (R) received in step (c) is not correct or if no response is received after the expiry of a predetermined time starting from the transmission of the random number (C). 4. A method for proving that data sent to a receiver (2) have been transmitted by a transmitter (1,3) authorized by a trusted third party, the transmitter and the receiver being connected to a digital network, characterized in that an identifier (IdEvent) for data sent by the transmitter is sent with said data and in that the method bomprises the steps consisting, for the transmitter (1, 3) in: (a) receiving a random number (C) and said identifier (IdEvent) from the receiver (2); (b) computing a response (R) by applying a first function (G) to said random number (C) and to said identifier (IdEvent); (c) sending said response (R) to the receiver (2); said response being likely to be verified by the receiver by applying a second function (H) to the received response (R), to said random number (C) and to said identifier (IdEvent); the first function (G) having previously been delivered to the transmitter by the trusted third party and the second function (H) being a function for verifying the result of the first function, previously delivered by the trusted third party to the receiver; wherein steps (b) and (c) are not carried out unless said identifier received in the step (a) corresponds to the identifier associated with the data that the transmitter has just sent. 5. The method as claimed in any of the preceding claims, wherein the identifier associated with the data sent by the transmitter is a random number generated by the initial transmitter of the data in the network and attached to said data by the initial transmitter. 6. The method as claimed in any of the preceding claims, wherein the first function (G) is public function using a secret key. 7. The method as claimed in claim 6, wherein the second function (H) is a Boolean function computing an expected response by applying to said random number ( C ) and to said identifier (IdEvent) the first function ( G) with the secret key and comparing the expected response with the response received in order to deliver: - a "0" value if the expected and received responses are different and - a "1" value if the expected and received responses are equal. 8. The method as claimed in any one of claims 1 to 5, wherein the first function (G) is a secret function. 9. The method as claimed in 8, wherein the second function (H) is a boolean function computing an expected response by applying the first function (G) to said random number (C ) and to said identifier. (IdEvent) and comparing the expected response with the response received in order to deliver: - a "0" value if the expected and received responses are different and - a"l" value if the expected and received responses are equal. 10. The method as claimed in any one of claims 1 to 5, wherein the first function (G) is a public function for signature generation with the aid of a private key. 11. The method as claimed in claim 10, wherein the second function (H) is a public function for signature verification with the aid of a public key corresponding to the private key used by the first function.

Documents:

2870-DELNP-2004-Abstract-(19-04-2012).pdf

2870-delnp-2004-abstract.pdf

2870-DELNP-2004-Claims-(19-04-2012).pdf

2870-delnp-2004-claims.pdf

2870-DELNP-2004-Correspondence Others-(19-04-2012).pdf

2870-delnp-2004-correspondence-others.pdf

2870-delnp-2004-description (complete).pdf

2870-DELNP-2004-Drawings-(19-04-2012).pdf

2870-DELNP-2004-Form-1-(19-04-2012).pdf

2870-delnp-2004-form-1.pdf

2870-delnp-2004-Form-13-(29-03-2007).pdf

2870-delnp-2004-form-13.pdf

2870-delnp-2004-form-18.pdf

2870-delnp-2004-form-2.pdf

2870-DELNP-2004-Form-3-(19-04-2012).pdf

2870-delnp-2004-form-3.pdf

2870-delnp-2004-form-5.pdf

2870-DELNP-2004-GPA-(19-04-2012).pdf

2870-delnp-2004-gpa.pdf

2870-DELNP-2004-Petition-137-(19-04-2012).pdf