Method and system for deploying an asset over a multi-tiered network

• US 8,458,142 B2
• Filed: 10/22/2010
• Issued: 06/04/2013
• Est. Priority Date: 09/01/2000
• Status: Expired due to Fees

• Current Assignee: Op40 Holdings, Inc.
• Original Assignee: Op40 Holdings, Inc.
• Inventors: Pace, Charles P., DeForest, Darin S., Pizzorni, Paolo R., Chen, Shuang
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Black, Linh
• Application Number:
  US12/925,514
• Publication Number:
  US 20110099256A1
• Time in Patent Office: 956 Days
• Field of Search: 707/690, 707/695
• US Class Current: 707/690
• 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 data processing systems or methods, specially adapted for e-commerce G06Q30/00
• 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

A method for distributing changes to digital assets across a network includes determining an asset type of a first digital asset and comparing the first digital asset to a prior digital asset to determine one or more deltas, the prior digital asset being a prior version of the first digital asset and the delta being a difference between the first digital asset and the prior digital asset. The method further includes evaluating the one or more of the deltas with one or more criteria to determine if the one or more delta assets should be created, the delta asset being a second digital asset containing the respective delta, the criteria determined by the asset type. The method further includes that if the delta meets the criteria, creating the delta asset, and marking the delta asset as a first delta asset of the first digital asset.

Claims

1. A method for distributing changes to digital assets across a network, said method comprising:

determining an asset type of a first digital asset located on a source node;

comparing the first digital asset to a prior digital asset located on one or more target nodes to determine one or more deltas, the prior digital asset being a prior version of the first digital asset;

the delta being a difference between the first digital asset and the prior digital asset;

evaluating the one or more deltas with one or more criteria to determine if the one or more delta assets should be created, the delta asset containing the respective delta, the criteria determined by the asset type, wherein if the delta meets the criteria, creating the delta asset, said delta asset comprising a package which is subparts of at least one application program from at least one enterprise information system (EIS), said delta asset having the 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 delta asset and the extended environment layer being a subset of an EIS and having portions of the EIS system necessary to support the respective logic data layer;

marking the delta asset as a first delta asset of the first digital asset;

sending the first delta asset to a component distribution server/asset distribution server (CDS/ADS), said CDS/ADS comprising;

a package specification process that receives the package comprising the first delta asset;

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

a target process that changes the at least one layer of the first delta 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; and

distributing across the network, via the CDS/ADS, over a Distributed Internet Services system, the first delta asset to one or more target nodes for deployment thereon.

2. The method of claim 1, wherein the comparing is done at the Enterprise Information System (EIS) connected to the network.

3. The method of claim 2, wherein the EIS comprises one or more of the following:

an on-line customer order entry system;

an on-line retail/wholesale sales system, an on-line marketing system, an on-line inventory system, an enterprise supply chain management system, a product distribution system, a content distribution system, a television system, a phone system, an on-line financial system, a mortgage application system, an investing system, a stock trading system, a loan application system, a credit card account system, a service providing system, a medical service system, a legal service system, a real estate system, an engineering system, an education system, a distance leaning system, a technical support system, an on-line human resource system, a pay roll services system, an on-line banking system, a banking system, a financial institution, a manufacturer, an airplane manufacturer, an internal corporate system, an airline reservation system; and

a general business transacting system.

4. The method of claim 1, wherein the asset type comprises one of a static content (SC), presentational component (PC), transactional component (TC), and relational data (RD), with one or more data structures in the first digital asset, and wherein the comparing being done by a query of one or more of the data structures in the first digital asset and the prior digital asset to determine the delta, and the criteria is a threshold amount of data that has changed.

5. The method of claim 1, wherein the asset type comprises one of an entity bean (EB), and entity data (ED) and a reference data (RD), with one or more data structures in the first digital asset, and wherein the comparing being done by a query of one or more of the data structures in the first digital asset and the prior digital asset to determine the delta, and the criteria is a threshold amount of data that has changed.

6. The method of claim 1, wherein the first delta asset will be applied to the prior digital asset located on one or more target nodes connected to the network in order to create the first digital asset on the target node.

7. The method of claim 6, wherein one or more of the prior digital assets on the target is marked for removal after the respective first digital asset is created on the target node.

8. The method of claim 6, wherein one or more of the prior deltas on the target is marked for removal after the respective first digital asset is created on the target node.

9. The method of claim 1, wherein a set of two or more deltas is determined.

10. The method of claim 9, wherein the set is evaluated against a second criteria to determine whether the first delta asset is created.

11. The method of claim 10, wherein the second criteria prevents the first delta asset from being created if the aggregate of one or more of the deltas in the set are larger than the prior digital asset.

12. The method of claim 11, further comprising creating a new digital asset incorporating all of the deltas in the set.

13. The method of claim 1, further comprising coalescing two or more of the deltas into a coalesced delta that is used to create the first delta asset.

14. The method of claim 1, wherein said method is only executed on a node of the network if the first digital asset is registered with the node.

15. The method of claim 1, wherein one or more of the deltas has information used to synchronize a source node with changes at one or more target nodes, the source and target nodes connected to the network.

16. The method of claim 1, wherein one or more of the deltas is stored along with the prior digital asset in order to provide the deltas for some nodes and the deltas combined with the prior digital asset for those nodes that do not have the prior asset.

17. The method of claim 16, wherein the deltas are applied to the prior digital asset for distribution to nodes that do not contain the prior digital asset.