REMOTE APPLICATION INVOCATION SYSTEM AND METHOD

• US 20120036225A1
• Filed: 08/09/2010
• Published: 02/09/2012
• Est. Priority Date: 08/09/2010
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Mskynet, Inc. (Apollo Global Management, Inc.)
• Inventors: Chor, Jesse
• Granted Patent: US 8,438,245 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/9554 by using bar codes
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A remote application invocation system and method are provided herein.

Claims

1. A server-implemented method of remotely invoking applications on mobile devices of a plurality of mobile-device types, the method comprising:

creating a mapping, by the server, between each of a plurality of data payload types and each of the plurality of mobile-device types, each mapping comprising a non-http 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;

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

generating, by the server, a unique 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, via a machine-scannable code, 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, said first requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

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

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, said second requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

delivering, by the server, said second device-type-specific URI to said second requesting mobile device to invoke a second non-web-browser 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 non-web-browser application differs from said first non-web-browser application.

2. The method of claim 1, wherein providing said unique URL for exposure to said plurality of mobile devices comprises:

encoding, by the server, said unique URL into said machine-scannable code; and

providing said machine-scannable code for exposure to said plurality of mobile devices of the plurality of mobile-device.

3. The method of claim 2, wherein said machine-scannable code comprises an optical barcode.

4. The method of claim 1, wherein said machine-scannable code is exposed to said plurality of mobile devices via a plurality of radio-frequency identification (“

RFID”

) tags.

5. 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 non-http URI scheme corresponding to a previously-unknown non-web-browser 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 third requesting mobile device of said previously-unknown mobile device type, said requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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

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

6. 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.

7. The method of claim 1, wherein said data payload comprises at least 1 kilobyte of information, and wherein said unique URL encoded into said optical machine-readable code comprises no more than 200 bytes of information.

8. The method of claim 1, wherein said dynamically-generated image depicting said optical machine-readable code further depicts a non-machine-readable pictogram indicating said one of said plurality of data payload types.

9. A server apparatus comprising a processor and a memory, the memory including instructions that when executed by the processor, configure the server apparatus to remotely invoke applications on mobile devices of a plurality of mobile-device types according to 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 non-http 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;

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

generating a unique URL corresponding to said data payload;

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

providing said unique URL for exposure, via a machine-scannable code, 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, said first requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

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

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, said second requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

delivering said second device-type-specific URI to said second requesting mobile device to invoke a second non-web-browser 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 non-web-browser application differs from said first non-web-browser application.

10. The server apparatus of claim 9, wherein providing said unique URL for exposure to said plurality of mobile devices comprises:

encoding said unique URL into said machine-scannable code; and

providing said machine-scannable code for exposure to said plurality of mobile devices of the plurality of mobile-device.

11. The server apparatus of claim 10, wherein said machine-scannable code comprises an optical barcode.

12. The server apparatus of claim 9, wherein said machine-scannable code is exposed to said plurality of mobile devices via a plurality of radio-frequency identification (“

RFID”

) tags.

13. The server apparatus of claim 9, 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 non-http URI scheme corresponding to a previously-unknown non-web-browser 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 third requesting mobile device of said previously-unknown mobile device type, said requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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

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

14. A non-transitory computer-readable storage medium storing instructions that when executed by a processor, configure the processor to remotely invoke applications on mobile devices of a plurality of mobile-device types according to 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 non-http 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;

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

generating a unique URL corresponding to said data payload;

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

providing said unique URL for exposure, via a machine-scannable code, 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, said first requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

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

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, said second requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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;

delivering said second device-type-specific URI to said second requesting mobile device to invoke a second non-web-browser 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 non-web-browser application differs from said first non-web-browser application.

15. The computer-readable storage medium of claim 14, wherein providing said unique URL for exposure to said plurality of mobile devices comprises:

encoding said unique URL into said machine-scannable code; and

providing said machine-scannable code for exposure to said plurality of mobile devices of the plurality of mobile-device.

16. The computer-readable storage medium of claim 15, wherein said machine-scannable code comprises an optical barcode.

17. The computer-readable storage medium of claim 14, wherein said machine-scannable code is exposed to said plurality of mobile devices via a plurality of radio-frequency identification (“

RFID”

) tags.

18. The computer-readable storage medium of claim 14, 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 non-http URI scheme corresponding to a previously-unknown non-web-browser 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 third requesting mobile device of said previously-unknown mobile device type, said requesting mobile device having obtained said unique URL by scanning a manifestation of said machine-scannable code;

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

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