Image data transfer

• US 20040249905A1
• Filed: 06/04/2004
• Published: 12/09/2004
• Est. Priority Date: 06/04/2003
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Wilcock, Lawrence, John Brittan, Paul St
• Granted Patent: US 7,404,007 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

Image data generated at a first mobile device is transferred to a storage service that is accessible via a communications infrastructure and with which a first party associated with the first mobile entity is preferably registered. This transfer is effected via one or more nearby third-party mobile devices with the first mobile device initially transferring the image data and an identifier of itself to the or each nearby third-party mobile device by using, for example, a short-range wireless link. The or each third-party device is then responsible for directly or indirectly forwarding the image data and the first-party identifier over the communications infrastructure to the storage service where it is stored. In one preferred embodiment, a reward is credited to any party whose device has been used in the successful transfer of image data to the storage service on behalf of the first party.

Claims

1. A method of transferring image data from a first mobile entity of a first party to a storage service accessible via a communications infrastructure, the method comprising the steps of:

(a) transferring from the first mobile entity, otherwise than via said communications infrastructure, both said image data and identifiers of said storage service and said first party, to at least one nearby third-party mobile entity for storage thereat;

(b) subsequent to step (a), transferring both said image data and the first-party identifier over the communications infrastructure from a said at least one third-party mobile entity to said storage service as identified by the service identifier; and

(c) storing the image data at the storage service for access by the first party.

2. A method according to claim 1, wherein in step (a) all the image data associated with one image is transferred to a single third-party mobile entity.

3. A method according to claim 1, wherein in step (a) all the image data associated with one image is transferred to each of multiple third-party mobile entities.

4. A method according to claim 1, wherein in step (a) the image data associated with one image is divided into multiple fragments and each fragment is transferred to a single respective third-party mobile entity along with fragment meta data for facilitating fragment re-assembly.

5. A method according to claim 1, wherein in step (a) the image data associated with one image is divided into multiple fragments and each fragment is transferred, along with fragment meta data for facilitating fragment re-assembly, to each of multiple third-party mobile entities.

6. A method according to claim 1, wherein following a successful transfer to the storage service of image data via a said at least one third-party mobile entity, the storage service credits a party associated with that entity with a reward.

7. A method according to claim 6, wherein the first mobile entity associates, in a subversion-resistant manner, an indication of said reward with the image data transferred to the or each third-party mobile entity, the storage service using this indication to determine the reward to be credited.

8. A method according to claim 7, wherein said reward is negotiated automatically between the first mobile entity and the or each third-party mobile entity prior to step (a) being effected.

9. A method according to claim 6, wherein with the image data transferred to the or each third-party mobile entity, the first mobile entity associates, in a subversion-resistant manner, an identifier of a party associated with the third-party entity concerned;

the storage service using this identifier for determining the party to be credited with the reward for a said successful transfer.

10. A method according to claim 1, wherein with the image data transferred to the or each third-party mobile entity, the first mobile entity associates, in a subversion-resistant manner, a third-party identifier identifying a party associated with the third-party entity concerned, the storage service only accepting image data transfer after authenticating that the entity wishing to make the transfer is associated with the party identified by the third-party identifier.

11. A method according to claim 1, wherein in step (b) the storage service only accepts transfer of the image data, or any particular fragment of it, if not already received.

12. A method according to claim 4, wherein the fragments are encrypted such that all said fragments are needed to be able to decrypt them.

13. A method according to claim 5, wherein the fragments are encrypted such that all said fragments are needed to be able to decrypt them.

14. A method according to claim 1, wherein the first mobile entity normally stores the image data or transfers it itself to the storage service but has been enabled to carry out step (a) following detection of low internal resources.

15. A method according to claim 14, wherein the first mobile entity normally stores image data in a local image-data memory but has been enabled to carry out step (a) upon the available space in its image-data memory being detected as below a predetermined level.

16. A method according to claim 14, wherein the first mobile entity has communication means capable, at least at normal battery power levels of the entity, of communicating with the storage service over the communications infrastructure, the first mobile entity having been enabled to carry out step (a) upon the power level of its battery being detected as below a predetermined value.

17. A method according to claim 14, wherein the first mobile entity normally stores image data in a local image-data memory and has communication means capable, at least at normal battery power levels of the entity, of communicating with the storage service over the communications infrastructure;

the first mobile entity responding to the available space in its image-data memory being detected as below a predetermined level by attempting to use its communication means to transfer image data to the service system unless the first entity'"'"'s battery power level is detected as below a predetermined value in which case the first entity is enabled to carry out step (a).

18. A method according to claim 1, wherein in step (a) the first mobile entity further transfers to the or each said third-party mobile entity a third-party identifier identifying a third party associated with the third-party mobile entity concerned, a reward indicator, and a digital signature over a data set comprising the image data, the first-party identifier, the third-party identifier, and the reward indicator;

the storage service, on receiving the data set and related digital signature from an entity, carrying out the following checks though not necessarily in the order given and with failure of a check potentially terminating the carrying out of the checks;

a check, based on said digital signature, that the data set has not been altered,

a check that the party identified by the first-party identifier is registered with the service,

a check that a party associated with the entity transferring the data set to the service is the party identified by the third-party identifier,

a check that the image data in the data set has not already been received,

the storage service, consequent upon all checks being passed, storing the image data for access by the first party and credits the third party with the reward indicated by the reward indicator.

19. A mobile entity associated with a first party and comprising:

camera functionality for generating image data,

a memory for storing a first-party identifier identifying the first party and a service identifier identifying a storage service with which the first party is registered, and

a transfer arrangement for transferring image data to at least one nearby third-party mobile entity for subsequent onward transfer, via a communications infrastructure, to said storage service, the transfer arrangement being arranged to communicate with the at least one nearby third-party mobile entity independently of the communications infrastructure to transfer thereto both said image data and said identifiers for storage at the third-party mobile entity.

20. A mobile entity according to claim 19, wherein the transfer arrangement is arranged to transfer all the image data associated with one image to a single third-party mobile entity.

21. A mobile entity according to claim 19, wherein the transfer arrangement is arranged to transfer all the image data associated with one image to each of multiple third-party mobile entities.

22. A mobile entity according to claim 19, wherein the transfer arrangement is arranged to divide the image data associated with one image into multiple fragments and to transfer each fragment to a single respective third-party mobile entity.

23. A mobile entity according to claim 19, wherein the transfer arrangement is arranged to divide the image data associated with one image into multiple fragments and to transfer each fragment to each of multiple third-party mobile entities.

24. A mobile entity according to claim 19, wherein the transfer arrangement is arranged to associate, in a subversion-resistant manner, a reward indication with the image data to be transferred to the or each third-party mobile entity whereby to indicate to the storage service a reward to be credited to a party associated with the third-party entity involved in the successful transfer of the image data to the storage service.

25. A mobile entity according to claim 24, wherein the transfer arrangement is arranged to negotiate said reward with the or each third-party mobile entity prior to image data transfer being effected.

26. A mobile entity according to claim 25, wherein the transfer arrangement is arranged to associate, in a subversion-resistant manner, with the image data to be transferred to the or each third-party mobile entity an identifier of a third party associated with the third-party entity concerned whereby to identify to the storage service the party to whom the reward should be credited for a successful transfer of the image data.

27. A mobile entity according to claim 22, wherein the transfer arrangement includes encryption functionality for encrypting the fragments such that all said fragments are needed to be able to decrypt them.

28. A mobile entity according to claim 23, wherein the transfer arrangement includes encryption functionality for encrypting the fragments such that all said fragments are needed to be able to decrypt them.

29. A mobile entity according to claim 19, wherein the transfer arrangement includes signing functionality for digitally signing at least the image data.

30. A mobile entity according to claim 29, wherein the transfer arrangement is arranged to transfer to the or each said third-party mobile entity, along with said image data, a third-party identifier identifying a party associated with the third-party mobile entity concerned, a reward indicator, and a digital signature generated by the signing functionality over a data set comprising the image data, the first-party identifier, the third-party identifier, and the reward indicator.

31. A mobile entity according to claim 19, wherein the mobile entity is arranged to normally operate in a first mode in which it is arranged to store the image data or transfer it itself to the storage service, but to change upon detection of low internal resources to a second mode in which the transfer arrangement is arranged to attempt to transfer image data to said at least one nearby third-party mobile entity.

32. A mobile entity according to claim 31, wherein the mobile entity is arranged in said first mode to store the image data in said memory but to change to said second mode upon the available space in said memory for storing image data falling below a predetermined level.

33. A mobile entity according to claim 31, further comprising a battery for powering the entity and communication means capable, at least at normal battery power levels, of communicating with the storage service over the communications infrastructure;

the mobile entity being arranged to change from its first mode to its second mode upon the state of charge of its battery falling below a predetermined value.

34. A mobile entity according to claim 31, further comprising a battery for powering the entity and communication means capable, at least at normal battery power levels, of communicating with the storage service over the communications infrastructure;

the mobile entity being arranged to change from its first mode to its second mode upon the simultaneous existence of a state of charge of its battery below a predetermined value and an availability of space in said memory for storing image data below a predetermined level.

35. A storage service system for receiving and storing image data for registered users, the system comprising:

a communications interface for receiving from a sending party, over a communications infrastructure, image data and an associated first-party identifier identifying a first party different from said sending party;

a checking arrangement arranged to check that said first party is a registered user of the service system and that the image data has not already been stored for the first party, the image data only being accepted for storage if both these checks are passed; and

an image-data store for storing accepted image data for access by the first party.

36. A storage service system according to claim 35, further comprising a fragment-assembly arrangement for assembling together image fragments that have been separately received as image data via the communications interface and stored in the store for the same first party, this re-assembly being effected on the basis of fragment meta data received with each fragment image data.

37. A storage service system according to claim 35, further comprising a reward subsystem arranged to credit said sending party with a reward following the successful transfer and storage of image data received from that party.

38. A storage service system according to claim 37, wherein the reward subsystem is arranged to determine the reward to be credited on the basis of a reward indicator received with the image data, the checking arrangement being arranged to check that the reward indicator was associated with the image data by the first party.

39. A storage service system according to claim 35, further comprising a reward subsystem arranged to credit a third party with a reward following the successful transfer and storage of image data, the reward subsystem being arranged to determine the identity of the third party to be rewarded on the basis of a third-party identifier received with the image data concerned, and the checking arrangement being arranged to check that the third-party identifier was associated with the image data by the first party.

40. A storage service system according to claim 39, wherein the reward subsystem is arranged to determine the reward to be credited on the basis of a reward indicator received with the image data, the checking arrangement being arranged to check that the reward indicator was associated with the image data by the first party.

41. A storage service system according to claim 35, wherein a third-party identifier is associated with the image data and the checking arrangement is arranged to check both that the third-party identifier was associated with the image data by the first party and that the party identified by the third-party identifier is said sending party before accepting the image data for storage.

42. A storage service system according to claim 35, wherein a digital signature is associated with the received image data and the checking arrangement is arranged to check the authenticity of the image data using said digital signature.

43. A storage service system according to claim 35, wherein the communications interface is arranged to receive from said sending party, along with said image data and the first-party identifier, a third-party identifier, a reward indicator, and a digital signature over a data set comprising the image data, the first-party identifier, third-party identifier, and the reward indicator;

the checking arrangement being arranged to carry out the following checks though not necessarily in the order given and with failure of a check potentially terminating the carrying out of the checks;

a check, based on said digital signature, that the data set has not been altered,

the said check that the party identified by the first-party identifier is registered with the service,

a check that the sending party is the party identified by the third-party identifier,

the said check that the image data in the data set has not already been received,

the image store being arranged to store the image data upon all checks being passed, the service system further comprising a reward subsystem for crediting the sending party with the reward indicated by the reward indicator upon successful storage of the image data.