Remote application invocation system and method

1. A method comprising:

creating a mapping, by a server, between each of a plurality of data payload types and each of a plurality of mobile-device types, each mapping comprising a Uniform Resource Identifier (URI) scheme corresponding to an application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types;

storing in a database a data payload of one of said plurality of data payload types;

generating, by the server, a unique Uniform Resource Locator (URL) corresponding to said data payload;

associating, by the server, said data payload with said unique URL in said database;

providing, by the server, said unique URL for exposure to a plurality of mobile devices of the plurality of mobile-device types;

receiving a first request for said unique URL from a first requesting mobile device of a first one of the plurality of mobile-device types;

determining, by the server, a data payload type of said data payload corresponding to said unique URL;

obtaining, by the server, a first mapping corresponding to said data payload type and said first one of the plurality of mobile-device types;

generating, by the server according to said first mapping, a first device-type-specific URI comprising said data payload formatted for said first one of the plurality of mobile-device types; and

delivering, by the server, said first device-type-specific URI to said first requesting mobile device to invoke a first application suitable for handling said data payload on said first requesting mobile device.

2. The method of claim 1 , further comprising, after storing said data payload and providing said unique URL:

creating a new mapping between each of said plurality of data payload types and a previously-unknown mobile device type, said new mapping including a previously-unknown URI scheme corresponding to a previously-unknown application suitable for handling the mapped data payload type on said previously-unknown mobile device type;

receiving a request for said unique URL from a second requesting mobile device of said previously-unknown mobile device type;

generating, according to said new mapping, a second device-type-specific URI comprising said data payload formatted for said previously-unknown mobile device type; and

delivering said second device-type-specific URI to said second requesting mobile device to invoke said previously-unknown application for handling the mapped data payload type.

3. The method of claim 1 , wherein said data payload comprises at least one of an event information data structure, a contact information data structure, and a geo-location data structure.

4. The method of claim 1 , further comprising:

receiving a second request for said unique URL from a second requesting mobile device of a second one of the plurality of mobile-device types;

obtaining, by the server, a second mapping corresponding to said data payload type and said second one of the plurality of mobile-device types;

generating, by the server according to said second mapping, a second device-type-specific URI comprising said data payload formatted for said second one of the plurality of mobile-device types; and

delivering, by the server, said second device-type-specific URI to said second requesting mobile device to invoke a second application suitable for handling said data payload on said second requesting mobile device, wherein said second device-type-specific URI differs from said first device-type-specific URI, and said second application differs from said first application.

5. The method of claim 1 , wherein a mapping between at least one of said plurality of data payload types and at least one of the plurality of mobile-device types comprises a URI scheme corresponding to a non-web-browser application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types.

6. A server apparatus comprising:

a processor;

a non-transitory computer-readable storage medium for tangibly storing thereon program logic for execution by the processor, the program logic comprising:

creating logic executed by the processor for creating a mapping between each of a plurality of data payload types and each of plurality of mobile-device types, each mapping comprising a Uniform Resource Identifier (URI) scheme corresponding to an application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types;

storage logic executed by the processor for storing in a database a data payload of one of said plurality of data payload types;

generating logic executed by the processor for generating a unique Uniform Resource Locator (URL) corresponding to said data payload;

associating logic executed by the processor for associating said data payload with said unique URL in said database;

communication logic executed by the processor for providing said unique URL for exposure to a plurality of mobile devices of the plurality of mobile-device types;

receiving logic executed by the processor for receiving a first request for said unique URL from a first requesting mobile device of a first one of the plurality of mobile-device types;

determining logic executed by the processor for determining a data payload type of said data payload corresponding to said unique URL;

obtaining logic executed by the processor for obtaining a first mapping corresponding to said data payload type and said first one of the plurality of mobile-device types;

generating logic executed by the processor for generating, by the server according to said first mapping, a first device-type-specific URI comprising said data payload formatted for said first one of the plurality of mobile-device types; and

communication logic executed by the processor for delivering said first device-type-specific URI to said first requesting mobile device to invoke a first application suitable for handling said data payload on said first requesting mobile device.

7. The server apparatus of claim 6 , wherein the method further comprises, after storing said data payload and providing said unique URL:

creating logic executed by the processor for creating a new mapping between each of said plurality of data payload types and a previously-unknown mobile device type, said new mapping including a previously-unknown URI scheme corresponding to a previously-unknown application suitable for handling the mapped data payload type on said previously-unknown mobile device type;

receiving logic executed by the processor for receiving a request for said unique URL from a second requesting mobile device of said previously-unknown mobile device type;

generating logic executed by the processor for generating, according to said new mapping, a second device-type-specific URI comprising said data payload formatted for said previously-unknown mobile device type; and

communication logic executed by the processor for delivering said second device-type-specific URI to said second requesting mobile device to invoke said previously-unknown application for handling the mapped data payload type.

8. The server apparatus of claim 6 , further comprising:

receiving logic executed by the processor for receiving a second request for said unique URL from a second requesting mobile device of a second one of the plurality of mobile-device types;

obtaining logic executed by the processor for obtaining a second mapping corresponding to said data payload type and said second one of the plurality of mobile-device types;

generating logic executed by the processor for generating, according to said second mapping, a second device-type-specific URI comprising said data payload formatted for said second one of the plurality of mobile-device types; and

communication logic executed by the processor for delivering said second device-type-specific URI to said second requesting mobile device to invoke a second application suitable for handling said data payload on said second requesting mobile device, wherein said second device-type-specific URI differs from said first device-type-specific URI, and said second application differs from said first application.

9. The server apparatus of claim 6 , wherein a mapping between at least one of said plurality of data payload types and at least one of the plurality of mobile-device types comprises a URI scheme corresponding to a non-web-browser application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types.

10. A non-transitory computer-readable storage medium tangibly storing instructions that when executed by a processor, configure the processor to perform a method comprising:

creating a mapping between each of a plurality of data payload types and each of the plurality of mobile-device types, each mapping comprising a Uniform Resource Identifier (URI) scheme corresponding to an application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types;

storing in a database a data payload of one of said plurality of data payload types;

generating a unique Uniform Resource Locator (URL) corresponding to said data payload;

associating said data payload with said unique URL in said database;

providing said unique URL for exposure to a plurality of mobile devices of the plurality of mobile-device types;

receiving a first request for said unique URL from a first requesting mobile device of a first one of the plurality of mobile-device types;

determining a data payload type of said data payload corresponding to said unique URL;

obtaining a first mapping corresponding to said data payload type and said first one of the plurality of mobile-device types;

generating, by the server according to said first mapping, a first device-type-specific URI comprising said data payload formatted for said first one of the plurality of mobile-device types; and

delivering said first device-type-specific URI to said first requesting mobile device to invoke a first application suitable for handling said data payload on said first requesting mobile device.

11. The non-transitory computer-readable storage medium of claim 10 , wherein the method further comprises, after storing said data payload and providing said unique URL:

creating a new mapping between each of said plurality of data payload types and a previously-unknown mobile device type, said new mapping including a previously-unknown URI scheme corresponding to a previously-unknown application suitable for handling the mapped data payload type on said previously-unknown mobile device type;

receiving a request for said unique URL from a second requesting mobile device of said previously-unknown mobile device type;

generating, according to said new mapping, a second device-type-specific URI comprising said data payload formatted for said previously-unknown mobile device type; and

delivering said second device-type-specific URI to said second requesting mobile device to invoke said previously-unknown application for handling the mapped data payload type.

12. The non-transitory computer-readable storage medium of claim 10 , further comprising:

receiving a second request for said unique URL from a second requesting mobile device of a second one of the plurality of mobile-device types;

obtaining a second mapping corresponding to said data payload type and said second one of the plurality of mobile-device types;

generating, by the server according to said second mapping, a second device-type-specific URI comprising said data payload formatted for said second one of the plurality of mobile-device types; and

delivering said second device-type-specific URI to said second requesting mobile device to invoke a second application suitable for handling said data payload on said second requesting mobile device, wherein said second device-type-specific URI differs from said first device-type-specific URI, and said second application differs from said first application.

13. The non-transitory computer-readable storage medium of claim 10 , wherein a mapping between at least one of said plurality of data payload types and at least one of the plurality of mobile-device types comprises a URI scheme corresponding to a non-web-browser application suitable for handling the mapped data payload type on the mapped one of the plurality of mobile-device types.