Method and system for software delivery service

• US 9,372,679 B2
• Filed: 08/02/2013
• Issued: 06/21/2016
• Est. Priority Date: 08/02/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Thormaehlen, Frederik
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US13/958,023
• Publication Number:
  US 20150040116A1
• Time in Patent Office: 1,054 Days
• Field of Search: 717/172, 717/177
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Provided herein are techniques for distributing software. An embodiment operates by receiving a software product request including a unique identification information, verifying the unique identification information, and distributing a software product associated with the unique identification information in response to the request.

Claims

1. A method, comprising:

receiving, by a delivery as a service (DaaS) system including at least one processor, via a communication network, a software product and unique identification information from a software vendor that is separate from the DaaS system and that maintains an offering of the software product provided to a client system, wherein the unique identification information identifies the software product;

receiving, by the DaaS system from the client system, via the communication network, a request for downloading the software product, wherein the request comprises information associated with the unique identification information received by the client system in response to a purchase of the offering from the software vendor by the client system;

using, by the DaaS system, the unique identification information received from the software vendor to verify that the information from the request of the client system allows the software product to be distributed to the client system; and

distributing, by the DaaS system, the software product to the client system in response to verifying the received request.

2. The method of claim 1, the using comprising:

processing a portion of the information using a digital signature algorithm.

3. The method of claim 1, the using comprising:

comparing a portion of the information to a list of codes associated with a plurality software products to determine that the software product is available for distribution.

4. The method of claim 1, further comprising:

receiving an identification of the client system included in the request; and

storing the identification of the client system in association with the software product in a list including a plurality of client system-software product associations, wherein the software product is identified by the unique identification information.

5. The method of claim 4, further comprising:

receiving, by the DaaS, an update to the software product from the software vendor or a software company that maintains the software package; and

distributing, in response to receipt of the update, the update to all client systems associated with the software product in the list.

6. The method of claim 4, further comprising:

receiving an update agreement between a plurality of client systems and the software product;

storing the update agreement in association with the software product in the list;

receiving an update to the software product; and

distributing, in response to receipt of the update, the update to the plurality of client systems associated with the software product based on the update agreement.

7. The method of claim 4, further comprising:

receiving an update agreement between the client system and the software product, wherein the request for downloading comprises the update agreement associated with the unique identification information;

storing the update agreement in association with the software product in the list;

receiving an update to the software product; and

distributing, in response to receipt of the update, the update to the client system associated with the software product based on the update agreement.

8. A delivery as a service (DaaS) system, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

receive, via a communication network, a software product and unique identification information from a software vendor that is separate from the DaaS system and that maintains an offering of the software product provided to a client system, wherein the unique identification information identifies the software product;

receive from the client system, via the communication network, a request for downloading the software product, wherein the request comprises the information associated with the unique identification information received by the client system in response to a purchase of the offering from the software vendor by the client system;

using the unique identification information received from the software vendor to verify that the information from the request of the client system allows the software product to be distributed to the client system; and

distribute the software product in response to verifying the received request.

9. The system of claim 8, the at least one processor further configured to:

process a portion of the information using a digital signature algorithm.

10. The system of claim 8, the at least one processor further configured to:

compare a portion of the information to a list of codes associated with a plurality software products to determine that the software product is available for distribution.

11. The system of claim 8, the at least one processor further configured to:

receive an identification of the client system included in the request; and

store the identification of the client system in association with the software product in a the memory in a list including a plurality of client system-software product associations, wherein the software product is identified by the unique identification information.

12. The system of claim 11, the at least one processor further configured to:

receive an update to the software product from the software vendor or a software company that maintains the software package; and

distribute, in response to receipt of the update, the update to all client systems associated with the software product in the list.

13. The system of claim 11, the at least one processor further configured to:

receive an update agreement between a plurality of client systems and the software product;

store the update agreement in association with the software product in the list;

receive an update to the software product; and

distribute, in response to receipt of the update, the update to the plurality of client systems associated with the software product based on the update agreement.

14. The system of claim 11, the at least one processor further configured to:

receive an update agreement between the client system and the software product, wherein the request for downloading comprises the update agreement associated with the unique identification information;

store the update agreement in association with the software product in the list;

receive an update to the software product; and

distribute, in response to receipt of the update, the update to the client system associated with the software product based on the update agreement.

15. A non-transitory tangible computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

receiving, by a delivery as a service (DaaS) system including at least one processor, via a communication network, a software product and unique identification information from a software vendor that is separate from the DaaS system and that maintains an offering of the software product provided to a client system, wherein the unique identification information identifies the software product;

receiving, by the DaaS system from the client system, via the communication network, a request for downloading the software product, wherein the request comprises information associated with the unique identification information received by the client system in response to a purchase of the offering from the software vendor by the client system;

using, by the DaaS system, the unique identification information received from the software vendor to verify that the information from the request of the client system allows the software product to be distributed to the client system; and

distributing, by the DaaS system, the software product to the client system in response to verifying the received request.

16. The computer-readable device of claim 15, the operations further comprising:

processing a portion of the information using a digital signature algorithm.

17. The computer-readable device of claim 15, the operations further comprising:

comparing a portion of the information to a list of codes associated with a plurality software products to determine that the software product is available for distribution.

18. The computer-readable device of claim 15, the operations further comprising:

receiving an identification of the client system included in the request; and

storing the identification of the client system in association with the software product in a list including a plurality of client system-software product associations, wherein the software product is identified by the unique identification information.

19. The computer-readable device of claim 18, the operations further comprising:

receiving, by the DaaS, an update to the software product from the software vendor or a software company that maintains the software package; and

distributing, in response to receipt of the update, the update to all client systems associated with the software product in the list.

20. The computer-readable device of claim 18, the operations further comprising:

receiving an update agreement between a plurality of client systems and the software product;

storing the update agreement in association with the software product in the list;

receiving an update to the software product;

distributing, in response to receipt of the update, the update to the plurality of client systems associated with the software product based on the update agreement.