System and method for enterprise software distribution

• US 20050144298A1
• Filed: 03/05/2002
• Published: 06/30/2005
• Est. Priority Date: 03/05/2002
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Samuel, Subodh A., Abraham, Raji
• Granted Patent: US 8,166,185 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• 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/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method for distributing software is provided. The method includes distributing a message from an application server to one or more application layer routers, such as servers that are being used to route enterprise software distribution messages, using a modified publish and subscribe architecture that includes the route to all recipients in the message address and that uses existing network communications. The message can thus be distributed to one or more subscribers on a first channel. The message is then distributed to one or more subscribers using the modified publish and subscribe architecture on one or more second channels selected from a second channel layer if necessary. This process is repeated until the message reaches all subscribers listed as recipients in the message.

Claims

1. A method for distributing software comprising:

distributing a message from an application server to one or more application layer routers using a publish and subscribe architecture to one or more first channels selected from a first channel layer; and

distributing the message to an endpoint using the publish and subscribe architecture to one or more second channels selected from a second channel layer.

2. The method of claim 1 wherein distributing the message to the endpoint further comprises:

distributing the message to one or more secondary application layer routers using the publish and subscribe architecture to one or more second channels selected from a second channel layer; and

distributing the message to the endpoint using the publish and subscribe architecture to one or more third channels selected from a third channel layer.

3. The method of claim 1 wherein the first channel and the second channel are selected by the application server.

4. The method of claim 1 wherein the first channel and the second channel are selected by the application server based on the available data communications bandwidth in one of the first channels or one of the second channels.

5. The method of claim 1 wherein the first channel and the second channel are selected by the application server based on the available data processing capacity of the selected application layer router.

6. The method of claim 1 wherein distributing the message to the endpoint further comprises:

storing the message at the selected application layer router; and

distributing the message to the endpoint using the publish and subscribe architecture to one or more second channels selected from the second channel layer after the occurrence of a predetermined event.

7. The method of claim 6 wherein the predetermined event is one or more of the group comprising an expiration of a timer, receipt of an event occurrence message, receipt of a bandwidth availability message, and receipt of a processor capacity availability message.

8. The method of claim 1 further comprising determining a sequence for the message prior to distributing the message from the application server to one or more application layer routers.

9. The method of claim 8 wherein determining the sequence comprises determining the sequence base on one or more of the group comprising data communications bandwidth availability between the application server and the endpoint, processing capacity of one or more of the application layer routers, processing capacity of a gateway receiving messages from the endpoint and the application server, and data communications bandwidth availability between the endpoint and the gateway.

10. The method of claim 1 further comprising:

generating a response to the message at the endpoint; and

transmitting the response to a destination system using an application layer gateway.

11. A system for distributing software comprising:

an application server transmitting a message that includes a first channel selected from a first channel layer and a second channel selected from a second channel layer;

a first application layer router coupled to the first channel layer receiving the message and transmitting the message over the first channel;

a second application layer router coupled to the second channel layer receiving the message and transmitting the message over the second channel; and

an endpoint receiving the message from the second channel layer.

12. The system of claim 11 wherein the application server further comprises a bandwidth allocation system transmitting the message.

13. The system of claim 11 wherein the application server further comprises an event based sequencing system transmitting the message.

14. The system of claim 11 wherein the first application layer router further comprises a router controller storing the message prior to transmitting the message over the first channel.

15. The system of claim 14 wherein the router controller further comprises a message timing system storing the message for a predetermined period of time.

16. The system of claim 14 wherein the router controller further comprises an event based message system storing the message until the occurrence of a predetermined event.

17. The system of claim 11 further comprising a gateway receiving response data from the endpoint generated in response to the message.