System, method and applications real-time messaging over HTTP-based protocols

• US 20020042830A1
• Filed: 04/02/2001
• Published: 04/11/2002
• Est. Priority Date: 03/31/2000
• Status: Abandoned Application

• Current Assignee: Paul A. Stirpe, Subhra Bose
• Original Assignee: Paul A. Stirpe, Subhra Bose
• Inventors: Stirpe, Paul A., Bose, Subhra
• Application Number:
  US09/824,541
• Publication Number:
  US 20020042830A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system for obtaining information is disclosed. The system comprises a server, a sender and a receiver and a communication means for the server to communicate with the sender and receiver. The receiver initiates a request message which is transmitted to the server. In the event the server is unable to immediately reply to the request with information for the receiver, the server retains the request in a pending state. The server retains the request in a pending state until a time when the server is able to respond to the request with information for the receiver and wherein at such time, the server allows for the completion of the receiver request with the information.

Claims

1. A system for obtaining information comprising a server, a sender and a receiver and a communication means for said server to communicate with said sender and receiver and wherein said receiver initiates a request message which is transmitted to said server, wherein in the event said server is unable to immediately reply to said request with information for said receiver, said server retains said request in a pending state until a time when said server is able to respond to said request with information for said receiver and wherein at such time, said server allows for the completion of said receiver request with said information,

2. The system according to claim 1 wherein the protocol used for said receiver and said server communications consists essentially of http, https, httpdav or any other variant of the http protocol.

7. The system in claim 2 wherein said receiver includes a web browser and said server includes a web server.

8. The system according to claim 2 wherein said server includes a web application server.

9. The system according to claim 2 wherein the server provides durability.

10. The system according to claim 2 wherein, in the event said server has multiple information items available for delivery to said receiver, the said server may combine said multiple information items in a single response to said receiver.

11. The system according to claim 2 wherein in the event said sender has multiple information items available to send, said sender may combine multiple information items in a single interaction with said server.

12. The system according to claim 2 further comprising, an event notification system to provide one-to-one, one-to-many and many-to-many communications wherein each communication channel is uniquely identified by a unique identifier.

13. The system according to claim 12 wherein said unique identifier is a string or number.

14. The system in claim 13 wherein the event mediator has an application programming interface.

15. The system according to claim 14 wherein the application program interface is a Java Messaging Service Interface or a subset thereof.

16. The system according to claim 2 used for a question and answer.

17. The system according to claim 2 used for real-time polling.

18. The system according to claim 2 used for page flipping.

19. The system according to claim 2 used for group membership.

20. The system according to claim 2 used for alert notification.

21. The system according to claim 2 used for follow-me browsing.

22. The system according to claim 2 used for instant messaging.

23. The system according to claim 2 used for chat.

24. The system according to claim 2 used for discussion groups.

25. The system according to claim 2 used for real-time email delivery and notification.

26. The system according to claim 2 used for text based speech.

29. The method according to claim 28 wherein said sender submits said submit-identified-event message to said server and said receiver submits a request-for-identified-event message to said server at any time with respect to each other.

30. The method according to claim 28 wherein said receiver may send a request-for-identified-event message to said server immediately after receiving said response to a previously submitted request-for-identified-event message.

31. The system in claim 27 wherein said system is used as a messaging service to a third party service provider, wherein said system is provided by a messaging service provider, where one or more third party service provider users may utilize said system provided by said messaging service provider for providing to said users real-time messaging applications, wherein said third party service provider provides consideration to said messaging service provider for said users use of said messaging service.

32. The system according to claim 2 wherein all or part of any communication is encrypted.

33. The system according to claim 2 wherein all or part of any communication is server side authenticated.

34. The system according to claim 32 wherein SSL is used as said underlying communication protocol.

35. The system according to claim 33 wherein SSL is used as said underlying communication protocol.

36. The system according to claim 32 wherein TLS is used as said underlying communication protocol.

37. The system according to claim 33 wherein TLS is used as said underlying communication protocol.

38. The system according to claim 1 wherein all or part of any communications may be secured via a Virtual Private Network.

3. The system according 2 wherein said receiver includes a browser.

4. The system according to claim 3 wherein said receiver is a computer and the computer, where said browser is executing, does not require the installation of additional software to receive a response from said server.

5. The system according to claim 4 wherein said receiver does not require the use of Java Applets, ActiveX controls or any other automatically downloaded control component to receive response from said server.

6. The system according to claim 4 wherein said computer requires the use of Javascript.

27. A system by which communicating entities using a communication protocol may send and receive messages in real-time, said system comprising a http, https, httpdav or any variant of the http communication protocol stack executing on a web server, an event mediator, and one or more communicating entities wherein said event mediator coordinates a receiver request and a response message and wherein any entity that desires to receive real-time messages is associated with an event identifier managed by said event mediator such that an entity submitting a submit-identified-event message to said web server has its request forwarded to said event mediator, said event mediator receiving said message from the web server and matching it with one or more receiver outstanding requests for the same identified event, said event mediator generating a response to said request and sending said response back to said receiver for responding to previously submitted request-for-identified-event messages sent to said web server that had said request forwarded to said event mediator.

28. A method of sending and receiving messages in real time comprising

a) a receiver submitting a request-for-identified-event message to a server;

b) said server forwarding said request-for-identified-event message to an event mediator;

c) a sender submitting a submit-identified-event message to said server;

d) said event mediator receiving said submit-identified-event message from said server and matching it with one or more receiver outstanding requests for said same identified event;

e) said event mediator sending a response back to said server for one or more previously submitted request-for-identified-event request, said server sending the corresponding response to said receiver.