The present invention relates to a method and apparatus for the secure provision of image data and to a physical add-in module for use in such apparatus.
Mobile multimedia appliances such as Internet-based cameras, multimedia mobile phones and wireless PDAs, allow users to generate multimedia information (image, video, sound, etc.) and transmit it, on-the-fly, to third parties in a highly dynamic way without requiring the access to mediation devices. This allows consumers to simplify and speed up their social interactions and professional people (such as reporters, etc.) to capture images and immediately send them back to information centres.
In traditional information technology systems (such as e-mail browsers, web browsers, etc.) protecting the privacy and confidentiality of digital data is usually effected by employing cryptographic mechanisms. Typical solutions use encryption techniques based on symmetric keys and/or RSA technology. Whilst these solutions are acceptable in traditional systems they are not straightforward to configure, use and manage in mobile appliances.
As a result, current mobile appliances mainly generate and transmit this information in clear or by means of point-to-point secured transmission channels. This information is usually stored by Telecom carriers, ISP providers or service providers either in clear or after these entities encrypt it. With the increasing diversity of inter-appliance communication options, relying on an infrastructure provider to carry out data encryption is likely to be unrealistic and to give rise to inflexible architectures.
Another approach used to secure data generated by mobile appliances is to rely on encryption functionality provided by a proxy device such as a docking station, PC, etc. Proxies usually leverage traditional encryption technologies and PKI solutions (including S/MIME, SSL and identity certificates) to provide privacy and security. Information can be encrypted by using the receiver's public certificate or shared secrets. However, such an approach not only suffers from inflexibility but uses encryption technology that is hard to configure, use and manage.
It is an object of the present invention to facilitate the protection of data, and in particular image data, provided by apparatus such as a mobile appliance.
Embodiments of the present invention to be described hereinafter make use of a cryptographic technology known as identifier-based encryption. Accordingly, a brief description will now be given of this type of encryption.
Identifier-Based Encryption (IBE) is an emerging cryptographic schema. In this schema (see
A feature of identifier-based encryption is that because the decryption key is generated from the encryption key string, its generation can be postponed until needed for decryption.
Another feature of identifier-based encryption is that the encryption key string is cryptographically unconstrained and can be any kind of string, that is, any ordered series of bits whether derived from a character string, a serialized image bit map, a digitized sound signal, or any other data source. The string may be made up of more than one component and may be formed by data already subject to upstream processing. In order to avoid cryptographic attacks based on judicious selection of a key string to reveal information about the encryption process, as part of the encryption process the encryption key string is passed through a one-way function (typically some sort of hash function) thereby making it impossible to choose a cryptographically-prejudicial encryption key string. In applications where defence against such attacks is not important, it would be possible to omit this processing of the string.
Frequently, the encryption key string serves to “identify” the intended message recipient and the trusted authority is arranged to provide the decryption key only to this identified intended recipient. This has given rise to the use of the label “identifier-based” or “identity-based” generally for cryptographic methods of the type under discussion. However, depending on the application to which such a cryptographic method is put, the string may serve a different purpose to that of identifying the intended recipient and may be used to convey other information to the trusted authority or, indeed, may be an arbitrary string having no other purpose than to form the basis of the cryptographic processes. Accordingly, the use of the term “identifier-based” or “IBE” herein in relation to cryptographic methods and systems is to be understood simply as implying that the methods and systems are based on the use of a cryptographically unconstrained string whether or not the string serves to identify the intended recipient. Generally, in the present specification, the term “encryption key string” or “EKS” is used rather than “identity string” or “identifier string”; the term “encryption key string” is also used in the shortened form “encryption key” for reasons of brevity.
A number of IBE algorithms are known and
The three prior art IBE algorithms to which
A more detailed description of the QR method is given below with reference to the entities depicted in
Each bit of the user's payload data 13 is then encrypted as follows:
The encrypted values s+ and s− for each bit m′ of the user's data are then made available to the intended recipient 11, for example via e-mail or by being placed in a electronic public area; the identity of the trust authority 12 and the encryption key string 14 will generally also be made available in the same way.
The encryption key string 14 is passed to the trust authority 12 by any suitable means; for example, the recipient 11 may pass it to the trust authority or some other route is used—indeed, the trust authority may have initially provided the encryption key string. The trust authority 12 determines the associated private key B by solving the equation:
B2≡K modN (“positive” solution)
If a value of B does not exist, then there is a value of B that is satisfied by the equation:
B2≡−K modN (“negative” solution)
As N is a product of two prime numbers p, q it would be extremely difficult for any one to calculate the decryption key B with only knowledge of the encryption key string and N. However, as the trust authority 12 has knowledge of p and q (i.e. two prime numbers) it is relatively straightforward for the trust authority 12 to calculate B.
Any change to the encryption key string 14 will result in a decryption key 16 that will not decrypt the payload data 13 correctly. Therefore, the intended recipient 11 cannot alter the encryption key string before supplying it to the trust authority 12.
The trust authority 12 sends the decryption key to the data recipient 11 along with an indication of whether this is the “positive” or “negative” solution for B.
If the “positive” solution for the decryption key has been provided, the recipient 11 can now recover each bit m′ of the payload data 13 using:
m′=jacobi(s++2B,N)
If the “negative” solution for the decryption key B has been provided, the recipient 11 recovers each bit m′ using:
m′=jacobi(s−+2B,N)
According to one aspect of the present invention, there is provided a method for the secure provision of image data representing an image, the method comprising:
Placing the thumbnail data in the encryption key string tightly binds the unencrypted (and therefore viewable) thumbnail to the full image data.
Preferably, the encryption key string further comprises at least one condition to be satisfied before the trusted party provides a decryption key for decrypting the payload data; the at least one condition thus forms a “policy” for release of the decryption key. This policy is advantageously managed by a user using a policy editor that can conveniently be provided, along with encryption functionality, in a physical add-in module.
According to another aspect of the present invention, there is provided a method for the secure provision of payload data that comprises image data representing an image, the method comprising encrypting the payload data using an Identifier-Based Encryption process employing an encryption key string comprising data that represents a low-resolution version of said image.
According to a further aspect of the present invention, there is provided apparatus for the secure provision of image data representing an image, the apparatus comprising:
According to a yet further aspect of the present invention, there is provided a physical add-in module for enabling apparatus to which the module has been added to securely provide payload data that comprises image data, the module comprising:
Embodiments of the invention will now be described, by way of non-limiting example, with reference to the accompanying diagrammatic drawings, in which:
The data-provider mobile device 20 is, for example, a mobile phone with camera functionality (not shown) for capturing an image as image data (such as image data 60); by way of a further example, the mobile device 20 can be a PDA storing image data 60 provided to it by another apparatus (also not shown).
The
As will be more fully described below, the encryption key string used to encrypt the image data 60 comprises a thumbnail (low resolution version) of the image represented by the image data, and a decryption-key release policy specifying at least one condition that the trusted service 40 must be satisfied has been met before providing the decryption key to the data-recipient device 30. Example policy conditions include that the receiving mobile device is associated with a particular person (as identified by an email address, telephone number, etc.), that a particular time has been reached, that a payment has been made, and that the trusted service has sent a notification to the data-provider device 20.
Considering the
The module 24 is, for example, an extension SIM card (where the device 20 is a mobile phone), a PCMCIA card, USB token, a smartcard, etc. The module 24 comprises the following functional blocks:
As an example usage, the user of the device 20 may wish to publish the image represented by the image data in such a manner that access to the full image is only provided to recipients who pay a specified amount. To this end, the user of device 20, arranges to send the encrypted image data to a list of potential customers including, in this case, the user of the device 30. The user of device 20 does this by selecting the image data 60 for sending to the target set of customers, and then initiating the encryption process. This cause the module 24 to be brought into action, enabling the user to use the policy editor 25 specify the required key-release policy—in this example, the payment of a specified amount into an identified account. In parallel with, or on completion of policy specification, the thumbnail generator 26 processes the image data 60 to generate corresponding thumbnail data. The thumbnail data and the policy data are then passed to the IBE encryption unit 27 where they are concatenated to form the encryption key string which the unit 27 then uses, together with the public data N of the trusted service 40 to encrypt the payload data here formed by the image data 60. The encrypted payload data 67 and the encryption key string 64 are then provided as a package 68 to the communications interface 21 for sending out over the communications infrastructure 51 according to a specified recipient list.
The package 68 is received by the mobile device 30 (see arrow 52). The device 30 is similar to the device 20 and comprises a communications interface 31, a user interface 32 (typically a keypad and display), and an IBE add-in module 34 similar to the module 24. For the purposes of accessing the received encrypted image data 67, the only element of the module 34 that is of relevance is the IBE decryption unit 38 (though, of course, the control unit 29 provides an overall control of the operation of the module 34).
Since the encryption key string 64 is included in clear in the package 68, the user of the device 30 can access the thumbnail data to view a low resolution version of the image represented by the encrypted image data 67; the user can also see the policy condition specifying the amount to be paid for access to the full image. It will be appreciated that the thumbnail image available to the user of device 30 is of little practical use for purposes other than image preview because of its low quality.
Assuming that the user of the device 30 wishes to access the full image, the user arranges for the specified amount to be paid into the identified account and requests the decryption key from the trusted service 40 (see arrow 53), this request including the encryption key string 64. Payment can be made in any manner but is conveniently done in the same message to the trusted service 40 as used to request the decryption key (it being assumed that the trusted service provides payment services).
The trusted service 40 comprises a web service front-end for interfacing with the communications infrastructure 51, an IBE trusted authority entity 42, and back-end service entities 46 (here shown as including a payment service). The IBE trusted authority entity 42 comprises an IBE policy checker for interpreting the policy data in the encryption key string and checking that the specified condition(s) have been satisfied, and a decryption key generator 44 for generating a decryption key from the encryption key string and the private data of the trusted service (for the QR IBE method, the values p and q mentioned above).
Upon the front-end 41 receiving the request from the device 30, the front-end 41 first processes any payment request by using the back-end payment service 46. Once this payment process has been completed, the front-end passes the decryption key request to the trusted authority entity 42. The IBE policy checker 43 then determines what policy conditions are present—in this case, there is only one condition, namely a payment condition, and the checker contacts the payment service 46 to verify that the required payment has been made. If this check fails, the entity 42 causes a failure message to be returned to the device 30. If the check shows that the specified policy condition(s) have been met, the key generation module is used to generate the required decryption key 69 which is then provided to the device 30 (see arrow 54).
It may be noted that although the trusted service 40 will typically receive the encryption key string from the device 30 requesting the decryption key, other mechanisms could be established for providing the encryption key string to the trusted service 40; for example, the device 20 could provide the encryption key string to the trusted service 40 directly. Furthermore, rather than generation of the decryption key being deferred until all the policy conditions have been confirmed as having been met, the trusted authority entity 42 can be arranged to start generation of the decryption key in parallel with, or even before, the policy checker carries out its checks, provided that provision of the decryption key to the device 30 is deferred until the policy checker 43 confirms that all specified conditions have been satisfied.
On receipt of the decryption key 69, the device 30 uses its decryption module 38 to decrypt the encrypted payload data 67 thereby to recover the image data 60.
In the foregoing scenario, rather than the package 68 being sent to individual recipients, it can be sent to a public website where the thumbnail image is displayed along with the associated policy conditions. Interested parties can then download the package 68 and obtain the decryption key 69 as described above.
It will be appreciated that instead of the QR IBE method, the above-described embodiment can be implemented using any other suitable IBE algorithm, such as those mentioned above that use of Weil or Tate pairings, or are RSA based.
It will be appreciated that many other variants are possible to the above described embodiments of the invention. For example, the encryption key string can be constituted by the image thumbnail without the inclusion of any policy conditions—this does not imply that any recipient of the package 68 will be able to obtain the decryption key 69 from the trusted service 40 since the latter may well have its own access restrictions (the user of the data-provider device 20 having decided to rely upon these restrictions to limit access to the image data 60).
The payload data can comprise data additional to the image data 60. This additional data could, for example, be image data of one or more further images and in this case the encryption key string can also include corresponding thumbnail data for these further images.
The functionality provided on the add-in module 24, 34 could be built into the entity 20, 30 concerned or provided (either in module form or built into) a proxy device such as a docking station or PC for the mobile device concerned. It may be noted that the add-in module with its policy editor can be implemented without the thumbnail generator (or with the possibility of by-passing it) for use in applications where the encryption key string is not required to include an image thumbnail.
As already indicated, the trusted authority functionality can be integrated with the data provider entity (or, indeed, with a proxy of the latter).
Whilst the data-provider entity and data-recipient entity in the above described embodiment take the form of mobile devices, it will be appreciated that one or both of these entities could take another form such as a traditional PC or an on-line service.
In another example scenario, rather than using a communications infrastructure to distribute images, a storage disc such as a CD-ROM or DVD can be used to distribute a large number of encrypted full images each with an associated encryption key string comprising corresponding thumbnail data and any related policy conditions. Such a disc could be distributed by anyone and the trusted service whose public data has been used in the encryption process could be a commercial trusted service set up for providing this role to anyone (the service would typically include a payment service as described above). When a possessor of the disc wishes to see a particular image in full, that party supplies the thumbnail to the trusted service and makes the required payment (or does whatever is required by the associated policy conditions); the trusted service then supplies back the decryption key (all of which can be done over a low bandwidth link).
Although in the foregoing, only a single trusted authority is involved, it is possible to require the involvement of multiple trusted authorities before an interested party is enabled to decrypt the encrypted payload data. This can be achieved in a number of ways, for example:
Number | Date | Country | Kind |
---|---|---|---|
0321807.0 | Sep 2003 | GB | national |