Method and apparatus for caching local mashup service parameters
View Patent ↗An approach is provided for caching parameters of local mashup services. One or more devices and/or service providers determine one or more mashup services, one or more trigger conditions associated with the one or more mashup services, and/or one or more actions associated with the one or more mashup services. Further, the one or more devices cache the one or more mashup services, the one or more trigger conditions, and/or the one or more actions at one or more local caches. Furthermore, the one or more devices and/or service providers determine one or more results of one or more queries for the one or more mashup services, the one or more trigger conditions, and/or the one or more actions from the one or more local caches.
1. A method comprising:
determining with a processor one or more mashup services, one or more trigger conditions associated with the one or more mashup services, one or more actions associated with the one or more mashup services, or a combination thereof;
caching with the processor the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof at one or more local caches;
determining with the processor one or more results of one or more queries for the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof from the one or more local caches;
determining historical use information for the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof; and
caching the historical use information at the one or more local caches,
wherein the historical use information comprises information on a mashup service last used, trigger conditions that cause the mashup service, and types of component services utilized for the mashup service, and
wherein the caching of the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof is based on the historical use information.
2. The method of claim 1 , further comprising:
discovering one or more component services available to at least one device; and
generating the one or more queries based on the one or more component services.
3. The method of claim 2 , wherein the one or more local caches are associated with the at least one device, one or more other devices associated with the one or more component services, or a combination thereof.
4. The method of claim 3 , wherein the discovering, the determining of the one or more results, or a combination thereof are performed using local connectivity among the at least one device, the one or more other devices, or a combination thereof.
5. The method of claim 3 , further comprising:
distributing the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof among the one or more local caches based on capability information, resource availability information, or a combination thereof associated with the at least one device, the one or more other devices, or a combination thereof.
6. The method of claim 2 , further comprising:
determining one or more agent interfaces for the one or more mashup services from the at least one local cache; and
initiating (a) the one or more mashup services, (b) an evaluation of the one or more trigger conditions, (c) the one or more actions, or (d) a combination thereof via the one or more agent interfaces.
7. The method of claim 6 , further comprising:
coordinating the one or more mashup services among the one or more component services, the at least one device, the one or more other devices, or a combination thereof via the one or more agent interfaces.
8. The method of claim 2 , further comprising:
generating one or more updated queries based on one or more updates to the one or more component services.
9. The method of claim 8 , wherein the discovering is performed periodically, according to a schedule, on demand, or a combination thereof to determine the one or more updates.
10. An apparatus comprising:
at least one processor; and
at least one memory including computer program code for one or more programs,
the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,
determine one or more mashup services, one or more trigger conditions associated with the one or more mashup services, one or more actions associated with the one or more mashup services, or a combination thereof;
cause a caching of the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof at one or more local caches;
determine one or more results of one or more queries for the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof from the one or more local caches;
determine historical use information for the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof; and
cause a caching of the historical use information at the one or more local caches,
wherein the historical use information comprises information on a mashup service last used, trigger conditions that cause the mashup service, and types of component services utilized for the mashup service, and
wherein the caching of the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof is based on the historical use information.
11. The apparatus of claim 10 , wherein the apparatus is further caused to:
cause a discovery of one or more component services available to at least one device; and
cause a generation of the one or more queries based on the one or more component services.
12. The apparatus of claim 11 , wherein the one or more local caches are associated with the at least one device, one or more other devices associated with the one or more component services, or a combination thereof.
13. The apparatus of claim 12 , wherein the discovery, the determining of the one or more results, or a combination thereof are performed using local connectivity among the at least one device, the one or more other devices, or a combination thereof.
14. The apparatus of claim 12 , wherein the apparatus is further caused to:
cause a distribution of the one or more mashup services, the one or more trigger conditions, the one or more actions, or a combination thereof among the one or more local caches based on capability information, resource availability information, or a combination thereof associated with the at least one device, the one or more other devices, or a combination thereof.
15. The apparatus of claim 11 , wherein the apparatus is further caused to:
determine one or more agent interfaces for the one or more mashup services from the at least one local cache; and
cause an initiation of (a) the one or more mashup services, (b) an evaluation of the one or more trigger conditions, (c) the one or more actions, or (d) a combination thereof via the one or more agent interfaces.
16. The apparatus of claim 15 , wherein the apparatus is further caused to:
cause a coordination of the one or more mashup services among the one or more component services, the at least one device, the one or more other devices, or a combination thereof via the one or more agent interfaces.
17. The apparatus of claim 11 , wherein the apparatus is further caused to:
cause a generation of one or more updated queries based on one or more updates to the one or more component services.
18. The apparatus of claim 17 , wherein the discovery is performed periodically, according to a schedule, on demand, or a combination thereof to determine the one or more updates.