System and method for distributing assets to multi-tiered network nodes

• US 8,326,883 B2
• Filed: 10/28/2010
• Issued: 12/04/2012
• Est. Priority Date: 09/01/2000
• Status: Expired due to Fees

• Current Assignee: Op40 Holdings, Inc.
• Original Assignee: Op40 Holdings, Inc.
• Inventors: Pizzorni, Paolo R., Pace, Charles P., DeForest, Darin S., Chen, Shuang
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Black, Linh
• Application Number:
  US12/925,734
• Publication Number:
  US 20110137934A1
• Time in Patent Office: 768 Days
• Field of Search: 707793-797, 709/227
• US Class Current: 707/795
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 2209/549 Remote execution
• CPC Class Codes: G06F 2216/15 Synchronised browsing
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• 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: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5651 : Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface

Abstract

Provided are methods and systems for distributing an asset to a multi-tiered network node. A pending notice is received from a distribution server. If the notice indicates that at least one asset is pending, i.e., awaiting deployment, an asset descriptor manifest is received from the distribution server. The asset descriptor manifest, which is stored in a memory on a node, identifies at least one asset to be deployed to the node and includes an offset associated with the asset identifier. A fragment, associated with the asset, is received and stored in the memory. The offset associated with the asset is marked with the end of the fragment and a second fragment, beginning at the offset, is received. Additional fragments are received, and the offset updated, until the entire asset is deployed to the node. Alternately, the entire asset or multiple assets are received in the first fragment.

Claims

1. A method for distributing an asset to a multi-tiered network node, comprising:

determining, via a client deployment process (CDP) located on a target node, at least one pending asset comprising at least one package on a component distribution server/asset distribution server system (CDS/ADS) for delivery to the target node;

wherein said CDS/ADS comprises;

a package specification process that receives at least one package which is subparts of at least one application program from at least one enterprise information system (EIS), the at least one package having at least one asset, each asset having an asset type and at least two asset layers, a first asset layer being a logic/data layer and a second asset layer being an extended environment layer, the logic/data layer having information that includes a function of the pending asset and the extended environment layer being a subset of the EIS and having portions of the EIS system necessary to support the respective logic data layer;

a process adapter process that translates at least one of the asset layers so that the asset performs the asset function on a target base environment of the target node; and

a target process that changes the at least one layers of the pending asset to provide specific information for the target node, whereby a transformed asset is an asset that is translated by the process adapter process and changed by the target process;

receiving, on the target node, a pending notice associated with the pending asset from the CDS/ADS;

receiving, on the target node, an asset descriptor manifest, called for by a client deployment agent (CDA) comprising the CDP, from the CDS/ADS, the asset descriptor manifest having at least one asset identifier and at least one offset, the asset identifier and the offset being associated with the pending asset;

storing the asset descriptor manifest in a memory;

receiving, on the target node, a first asset fragment associated with the pending asset from the CDS/ADS, the first fragment having a first offset indicating an end of the first fragment;

storing the first asset fragment in a memory;

marking the offset with the first offset; and

receiving, on the target node, a second asset fragment associated with the pending asset, the second asset fragment starting at the offset;

wherein the CDA continues to call the CDS/ADS until all fragments comprising the pending asset are received on the target node, thereby distributing the asset.

2. The method according to claim 1, wherein the pending notice does not indicate a pending asset.

3. The method according to claim 2, further comprising:

querying the CDS/ADS for a subsequent pending notice after a time delay.

4. The method according to claim 3, further comprising one or more of:

determining the time delay based on a deployment time associated with a next asset deployment sequence;

determining the time delay by polling the distribution;

or

determining the time delay based on an algorithm and at least one performance requirement of an application associated with the pending asset.

5. The method according to claim 1, further comprising:

the marked asset descriptor manifest to the CDS/ADS.

6. The method according to claim 1, further comprising:

sending a request for pending assets not yet deployed to the CDS/ADS.

7. The method according to claim 1, further comprising:

changing the asset identifier associated with the pending asset after the pending asset is received.

8. The method according to claim 1, wherein the pending asset has a schedule time, the schedule time being at or before a current time.

9. The method according to claim 1, wherein the pending asset is not included in the asset descriptor manifest if the pending asset is stored in the memory.

10. The method according to claim 1, wherein a target identifier associates the pending asset with the node.

11. The method according to claim 1, wherein the CDS/ADS insures that the pending asset is a current version residing on a source node connected to the network.

12. The method according to claim 1, wherein the asset descriptor manifest includes one or more of a deployment time schedule and the pending asset is deployed into a base environment of the node according to the deployment time schedule, a plurality of pending assets, a subset of pending assets, or a subset of dependent assets that are deployed into a base environment associated with the node after the plurality of dependent assets are received.

13. The method according to claim 1, wherein the pending asset is deployed into a base environment associated with the node if the pending asset is an independent asset.

14. The method according to claim 1, wherein the second asset fragment includes a header having the asset identifier.

15. A system for distributing an asset to a multi-tiered network node, comprising:

at least one network;

at least one CDS/ADS coupled to the network;

at least one port;

at least one processor coupled to the port and the network; and

at least one memory, coupled to the processor, storing instructions adapted to be executed by the processor to perform the method steps of claim 1.

16. A non-transitory computer memory storage device that stores a computer program with instructions for distributing an asset to a multi-tiered network node, the instructions adapted to be executed by a processor to perform the steps of the method of claim 1.