Service-to-device re-mapping for smart items

• US 20070118560A1
• Filed: 11/21/2005
• Published: 05/24/2007
• Est. Priority Date: 11/21/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Bornhoevd, Christof, Avanes, Artin, Ziekow, Hohger
• Granted Patent: US 8,005,879 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A service repository is used to store at least one service in association with service metadata describing service requirements of the service. The service repository also may store one or more platform-specific service executables. A service mapper is used to determine device metadata associated with each of a plurality of devices, where the device metadata provides device characteristics of the devices. The service mapper may thus map the service to a selected device of the plurality of devices for deployment thereon, based on a matching of corresponding elements of the service requirements and the device characteristics. The service mapper also may re-map the service between devices to maintain a quality and reliability of the service.

Claims

1. A method comprising:

determining a motivation for re-deployment of a service executing on an originating device;

mapping the service to a selected device from among a plurality of devices that includes the originating device and the selected device; and

re-deploying the service on the selected device.

2. The method of claim 1 wherein determining a motivation for re-deployment of a service comprises determining device metadata associated with the originating device and indicating that the originating device currently has insufficient device characteristics to continue adequately executing the service, based on service metadata associated with the service.

3. The method of claim 1 wherein determining a motivation for re-deployment of a service comprises:

determining that the selected device is available for re-deployment of the service; and

determining device metadata associated with the originating device and/or the selected device that indicates that the selected device is better able to execute the service.

4. The method of claim 1 wherein determining a motivation for re-deployment of a service comprises determining that a time limit for deployment of the service on the originating device has been reached.

5. The method of claim 1 wherein mapping the service to a selected device comprises:

determining service metadata associated with the service;

determining device metadata associated with each of the plurality of devices; and

mapping the service to the selected device, based on the service metadata and the device metadata.

6. The method of claim 1 wherein mapping the service to a selected device comprises:

determining service metadata associated with the service, the service metadata including a mobility description associated with the service and describing a nature and/or extent of allowed re-deployment of the service.

7. The method of claim 1 wherein mapping the service to a selected device comprises:

determining a current state of the service as the service is executing on the originating device.

8. The method of claim 1 wherein mapping the service to a selected device comprises:

determining that the selected device is associated with a device characteristic that meets or exceeds a threshold parameter required for the re-deploying to occur.

9. The method of claim 1 wherein mapping the service to a selected device comprises:

imposing a time limit to be met before the service may be re-deployed from the selected device back to the originating device, or to another device of the plurality of devices.

10. The method of claim 1 wherein re-deploying the service on the selected device comprises re-instating, on the selected device, a state of the service on the originating device prior to the re-deploying.

11. The method of claim 1 wherein re-deploying the service on the selected device comprises:

stopping execution of the service on the originating device; and

removing a service executable of the service from the originating device.

12. The method of claim 1 wherein re-deploying the service on the selected device comprises:

obtaining a service executable of the service from a service repository for deploying on the selected device.

13. A system comprising:

a system monitor that is operable to monitor an originating device of a plurality of devices, the originating device executing a service; and

a service mapper that is operable to determine a motivation for re-deployment of the service, based on an output of the system monitor, and further operable to re-deploy the service to a selected device of the plurality of devices, based on the motivation.

14. The system of claim 13 wherein the system monitor includes a system monitor component installed on the originating device and operable to report device characteristics of the originating device to the service mapper.

15. The system of claim 13 wherein the output of the system monitor includes current device metadata, including device characteristics, of the originating device.

16. The system of claim 13 wherein the motivation includes a determination that the originating device is not the best-suited of the plurality of devices to execute the service.

17. The system of claim 13 wherein the service mapper is operable to implement the re-deployment of the service based on an application of a re-mapping rule to the output of the system monitor.

18. The system of claim 13 wherein the service mapper is operable to reinstate a state of the service on the originating device at a time prior to the re-deployment, based on a data file storing state information for the service.

19. The system of claim 13 comprising:

a service repository that is operable to store at least the service in association with service metadata describing service requirements of the service,

wherein the service mapper is operable to re-deploy the service to the selected device from the service repository.

20. The system of claim 13 wherein the service mapper is operable to re-deploy the service, based on service metadata that includes service requirements of the service.