System and method for enabling group subscription for asynchronous push-based applications on a wireless device

• US 20060271662A1
• Filed: 04/18/2006
• Published: 11/30/2006
• Est. Priority Date: 04/18/2005
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Inventors: Shenfield, Michael, Bibr, Viera, Fritsch, Brindusa
• Application Number:
  US11/405,591
• Publication Number:
  US 20060271662A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

A system and method of enabling group subscription for asynchronous push-based applications on wireless devices are provided. The system comprises an application registry, an application repository and an application gateway server including an event sink for communicating between the system and a device. The application gateway server is configured for communication with a back-end service via an event source and including a subscription collection and a subscriber collection. The method comprises the steps of reading a Web service interface, generating a Web service interface therefrom conforming to a notification protocol, creating a notification-based application bundle for the Web service, publishing the notification-based application bundle and creating an event source.

Claims

1. A system for enabling group subscription for asynchronous push-based applications on wireless devices, the system comprising:

an application registry;

an application repository; and

an application gateway server including an event sink for communicating between the system and a device, the application gateway server configured for communication with a back-end service via an event source and including a subscription collection and a subscriber collection.

2. The system as claimed in claim 1, wherein the event source is in the back-end service.

3. The system as claimed in claim 1, wherein the event sink is a proxy in the application gateway.

4. The system as claimed in claim 1, wherein the application registry includes an entry for a component application in the application repository.

5. The system as claimed in claim 1, wherein the application repository includes a component application for accessing the back-end service via the event source.

6. The system as claimed in claim 1, wherein the system enables notification message broadcast to multiple subscribers to data content.

7. A method of enabling group subscription for asynchronous push-based applications on wireless devices, the method comprising:

reading a first Web service interface;

generating a second Web service interface therefrom conforming to a notification protocol;

creating a notification-based application bundle for the second Web service;

publishing the notification-based application bundle; and

creating an event source.

8. The method as claimed in claim 7, further comprising the steps of:

creating a subscription collection; and

creating a subscriber collection.

9. The method as claimed in claim 8, wherein the subscriber collection contains a plurality of (device, application) pairs.

10. The method as claimed in claim 8, further comprising the steps of:

receiving a first subscription request having filter content and a destination;

determining if a subscription message having the filter content and destination has been previously received; and

sending a second subscription request if the subscription message has not been previously received.

11. The method as claimed in claim 10, wherein the step of determining comprises the step of comparing the filter content and destination with subscription message data in the subscriber collection.

12. The method as claimed in claim 10, wherein the step of determining comprises the step of comparing the filter content and destination with subscription message information in the subscription collection.

13. The method as claimed in claim 8, further comprising the steps of:

receiving a notification having filter content and a destination from the event source;

comparing the filter content and destination with subscriber information in the subscriber collection; and

sending the notification to subscribers that have the filter content and destination.

14. The method as claimed in claim 8, further comprising the steps of:

receiving a notification having filter content and a destination from the event source;

comparing the filter content and destination with subscriber information in the subscription collection; and

sending the notification to subscribers that have the filter content and destination.

15. The method as claimed in claim 7, wherein the method is executed in a system having:

an application registry;

an application repository; and

an application gateway server including an event sink for communicating between the system and a device, the application gateway server configured for communication with a back-end service via an event source

16. A computer-readable medium storing instructions or statements for use in the execution in a computer of a method of enabling group subscription for asynchronous push-based applications on wireless devices, the method comprising the steps of:

reading a Web service interface;

generating a Web service interface therefrom conforming to a notification protocol;

creating a notification-based application bundle for the Web service;

publishing the notification-based application bundle; and

creating an event source.

17. A propagated signal carrier carrying signals containing computer-executable instructions that can be read and executed by a computer, the computer-executable instructions being used to execute a method of enabling group subscription for asynchronous push-based applications on wireless devices, the method comprising the steps of:

reading a Web service interface;

generating a Web service interface therefrom conforming to a notification protocol;

creating a notification-based application bundle for the Web service;

publishing the notification-based application bundle; and

creating an event source.