Web services push gateway

• US 7,673,007 B2
• Filed: 08/06/2007
• Issued: 03/02/2010
• Est. Priority Date: 11/20/2001
• Status: Expired due to Fees

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Mulligan, Michael, Toijala, Jouni, Nykanen, Petri
• Primary Examiner(s): Kang; Paul H
• Application Number:
  US11/890,537
• Publication Number:
  US 20080140789A1
• Time in Patent Office: 939 Days
• Field of Search: 709/207, 709/238
• US Class Current: 709/207
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/30 Profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A system and method for interfacing Web Services push applications and mobile terminals operable with one of a plurality of different mobile push technologies. A Web Services push gateway includes a Web Services endpoint to terminate Web Services protocols utilized by the Web Services push applications in providing push messages. A plurality of mobile push bearers are each configured to communicate with a different one of the plurality of mobile push technologies. The Web Services push gateway includes a push router coupled to the Web Services endpoint to receive the push messages, and to forward the push messages to an elected one of the mobile push bearers, from where is it ultimately delivered to a recipient mobile terminal employing a mobile push technology corresponding to the elected mobile push bearer.

Claims

1. An apparatus, comprising:

a web services endpoint to terminate web services protocols utilized by web services push applications in providing push messages and to parse the push messages;

a plurality of push bearers each configured to communicate with a different one of a plurality of push technologies;

a push adaptation layer configured to collect bearer characteristics from each of the push bearers; and

a push router disposed between the web services endpoint and the push bearers to elect one of the push bearers based on the bearer characteristics collected by the push adaptation layer, convert the parsed messages to a push protocol associated with the elected push bearer, and forward the push messages to the elected push bearer for ultimate delivery to a recipient terminal employing the push technology corresponding to the elected push bearer.

2. The apparatus as claimed in claim 1, further comprising a presence agent coupled to the push router to provide the push router with recipient presence information including the recipient terminal'"'"'s online status and terminal characteristics, wherein the push router'"'"'s election of the elected one of the push bearers is based at least in part on the recipient presence information.

3. The apparatus as claimed in claim 1, further comprising a user preference agent coupled to the push router to provide the push router with particular user preferences identified by the user of the recipient terminal, wherein the push router'"'"'s election of the elected one of the push bearers is based at least in part on the user preferences.

4. The apparatus as claimed in claim 3, wherein the user preferences agent comprises a preference repository to store the user preferences for each potential push message recipient.

5. The apparatus as claimed in claim 3, further comprising a user preference interface coupled to the user preference agent to allow the user of the recipient terminal to enter and/or modify the user preferences.

6. The apparatus as claimed in claim 5, wherein the user preference interface is an HTTP server in which the user of the recipient terminal accesses via a web browser.

7. The apparatus as claimed in claim 1, further comprising a storage buffer to store one or more of the push messages if the push messages are not to be immediately sent, wherein a decision to store the one or more push messages is based on at least one of recipient presence information, user preferences, and bearer characteristics.

8. The apparatus as claimed in claim 1, wherein the web services endpoint comprises a transport layer server for terminating the web services protocols.

9. The apparatus as claimed in claim 8, wherein the transport layer server is an HTTP server.

10. The apparatus as claimed in claim 1, wherein the web services endpoint comprises an Extensible Markup Language (XML) messaging engine to parse incoming requests associated with the push messages.

11. The apparatus as claimed in claim 10, wherein the XML messaging engine comprises a Simple Object Access Protocol (SOAP) engine.

12. The apparatus as claimed in claim 1, wherein the web services endpoint includes an interface for advertising which comprises a registry interface to interface with a service registry to advertise a push service of the web services endpoint.

13. The apparatus as claimed in claim 1, wherein the push adaptation layer is coupled to the plurality of push bearers to collect bearer information from each of the push bearers, and coupled to the push router to receive and direct the push messages to the elected one of the push bearers for ultimate delivery to the recipient terminal.

14. The apparatus as claimed in claim 1, wherein at least one of the push bearers is a Short Message Service (SMS) bearer for connecting to a Short Message Service Center (SMSC).

15. The apparatus as claimed in claim 1, wherein at least one of the push bearers is a Wireless Application Protocol (WAP) Push bearer for connecting to a WAP Push Proxy Gateway (PPG) using the WAP Push Access Protocol (PAP).

16. The apparatus as claimed in claim 1, wherein at least one of the push bearers is a Wireless Application Protocol (WAP) Push bearer for connecting to the recipient'"'"'s terminal via the WAP Push Over-the-Air (POTA) protocol.

17. The apparatus as claimed in claim 1, wherein at least one of the push bearers is a Multimedia Messaging Service (MMS) bearer for communicating multimedia push messages via a WAP MMS protocol.

18. The apparatus as claimed in claim 1, wherein at least one of the push bearers is a Session Initiation Protocol (SIP) bearer to send the push messages via the SIP protocol.

19. A network system for communicating push messages, comprising:

one or more terminals capable of receiving push messages via one of a plurality of push technologies;

one or more web services applications capable of providing the push messages via web services protocols; and

a web services push gateway for interfacing the push messages provided by the web services applications to any of the plurality of push technologies, the web services push gateway configured to parse push messages received from web services applications, collect bearer characteristics from each of a plurality of push bearers respectively associated with the plurality of push technologies, elect one of the push bearers, based on the collected bearer characteristics, convert the parsed push messages to a push protocol associated with the elected push bearer, and route the push messages to the elected push bearer for ultimate transmission to the recipient terminal using the respective push technology.

20. The network system as claimed in claim 19, wherein the web services push gateway comprises:

a first interface to receive the push messages via the web services protocols from the web services applications;

a plurality of different push bearers, each capable of transmitting the push messages to a recipient terminal via a respective push technology; and

a push message router coupled to receive the push messages from the first interface, to process bearer criteria and designate one of the push bearers for transmitting the push messages in response thereto.

21. A method comprising:

receiving at least one push message from web services applications via web services protocols;

terminating the web services protocols and parsing the push message;

obtaining presence information relating to the availability and type of recipient terminal;

obtaining user preference information relating to particular user preferences identified by the user of the recipient terminal;

obtaining bearer characteristics information from each of a plurality of different push bearers each capable of communicating with the terminals using a different push technology;

selecting a push bearer to transmit the push message to the recipient terminal based on the bearer characteristics information;

converting the parsed push message to a push protocol associated with the selected push bearer; and

delivering the push message from the selected push bearer to the recipient terminal using the push technology provided by the selected push bearer.

22. The method of claim 21, wherein selecting a push bearer comprises determining a closest match of the bearer characteristics information with one or more of the presence information and the user preference information.

23. The method of claim 21, wherein selecting a push bearer comprises determining a weighted match of the bearer characteristics information with one or more of the presence information and the user preference information.

24. The method of claim 23, further comprising providing feedback regarding the quality of the selection of the push bearer.

25. The method of claim 21, wherein obtaining presence information comprises querying for information indicative of whether the recipient terminal is currently online.

26. The method of claim 21, wherein obtaining presence information comprises querying for terminal type characteristics of the recipient terminal.

27. The method of claim 21, wherein obtaining user preference information comprises querying for terminal preferences indicative of a range of terminals available as the recipient terminal.

28. The method of claim 27, wherein querying for terminal preference information further comprises querying for content types for each of the terminals available as the recipient terminal.

29. The method of claim 21, wherein obtaining user preference information comprises querying for network preferences indicative of a type of network the user is currently operating within.

30. The method of claim 21, wherein obtaining user preference information comprises querying for presence preferences indicative of user activities at any given time.

31. The method of claim 21, wherein selecting a push bearer includes processing the recipient presence information including the recipient terminal'"'"'s online status and terminal characteristics.

32. The method of claim 21, wherein selecting a push bearer includes processing the user preferences identified by the user of the recipient terminal.

33. The method of claim 21, wherein the bearer characteristics comprise one or more of bearer bandwidth, content capability, bearer availability, bearer latency, and delivery assurance.

34. The method of claim 21, further comprising parsing the push message upon receipt.

35. The method of claim 21, further comprising processing message transmission parameters to identify transmission guidelines for transmitting the push message from the selected push bearer.

36. The method of claim 35, further comprising buffering the push message prior to transmitting the push message from the selected push bearer, when processing the message transmission parameters reveals postponement of the push message transmission.

37. A computer-readable medium having computer-executable instructions for facilitating the transmission of push messages to terminals utilizing a plurality of different push technologies, the computer-executable instructions performing steps comprising:

receiving the push messages from web services applications via web services protocols;

terminating the web services protocols and parsing the push messages;

collecting bearer availability and capabilities information from each of a plurality of different push bearers each capable of communicating with the terminals using a different push technology;

selecting a push bearer to transmit the push messages to the recipient terminals based on the collected bearer availability and capabilities information;

converting the parsed push messages to a push protocol associated with the selected push bearer; and

delivering the push messages from the selected push bearer to the recipient terminals using the push technology provided by the selected push bearer.