US2012131327A1PendingUtilityA1

Method of and apparatus for distributing software objects

Assignee: TOMLINSON DAVID ROBINPriority: Oct 19, 2010Filed: Nov 16, 2011Published: May 24, 2012
Est. expiryOct 19, 2030(~4.2 yrs left)· nominal 20-yr term from priority
Inventors:David Tomlinson
G06F 8/60H04L 63/0442H04L 63/061G06F 21/1062
46
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method of distributing software objects from a first entity to at least one second entity, the method comprising: using a distribution entity to accept a software object from the first entity, the software object including an identifier for a specific second entity, and wherein the at least one second entity is operable to contact the distribution entity and to enquire if a software object has been deposited for it, and if a software object has been deposited, to accept it from the distribution entity.

Claims

exact text as granted — not AI-modified
1 . A method of distributing software objects from a first entity to at least one second entity, the method comprising:
 using a distribution entity to accept a software object from the first entity, the software object including an identifier for a specific second entity, and wherein the at least one second entity is operable to contact the distribution entity and to enquire if a software object has been deposited for it, and if a software object has been deposited, to accept it from the distribution entity.   
     
     
         2 . A method as claimed in  claim 1 , in which the software object is encrypted, or has an encrypted portion. 
     
     
         3 . A method as claimed in  claim 2 , in which the software object was encrypted using the public key of a public key-private key pair associated with the specific second entity. 
     
     
         4 . A method as claimed in  claim 1 , in which the first entity is a computing device or data processor operable to connect to a communication medium, and the first entity initiates the communications with the distribution entity. 
     
     
         5 . A method as claimed in  claim 4 , in which the first entity does not have an open port for receiving communications sessions initiated by the distribution entity. 
     
     
         6 . A method as claimed in  claim 1 , in which the distribution entity performs a handshake with the first and at least one second entity, and keeps a log of transactions. 
     
     
         7 . A method as claimed in  claim 1 , in which the at least one second entity is a computing device or data processor operable to connect to a communication medium, and the at least one second entity initiates communications with the distribution entity. 
     
     
         8 . A method as claimed in  claim 7 , in which the second entity does not have an open port for receiving communication sessions initiated by the distribution entity. 
     
     
         9 . A method as claimed in  claim 7 , in which the first entity can inspect or receive data from the log of transactions. 
     
     
         10 . A method as claimed in  claim 1 , in which the software object comprises one of:
 an encryption key;   a decryption key   an instruction to use an encryption or decryption key   an instruction to replace an encryption or decryption key   an instruction to revoke a decryption key   at least one policy instruction for execution by a security system;   a licence;   an executable;   a software update;   a data file.   
     
     
         11 . A method as claimed in  claim 1 , in which each of the at least one second entity is a computing device or data processor with a machine identity. 
     
     
         12 . A method as claimed in  claim 11 , in which the or each user of a specific one of the second entities is associated with a user identity. 
     
     
         13 . A method as claimed in  claim 11 , in which the software objects are destined for a specific user and computing device combination, or for a specific computing device independent of its user. 
     
     
         14 . A method as claimed in  claim 1 , in which each message includes a checksum. 
     
     
         15 . A method as claimed in  claim 1 , in which each message includes a direction flag. 
     
     
         16 . Server software for performing the server part of the method of  claim 1 . 
     
     
         17 . Client software for performing the client part of the method defined in  claim 1 .

Join the waitlist — get patent alerts

Track US2012131327A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.