Methods and apparatus providing a web based messaging system

• US 7,412,486 B1
• Filed: 09/12/2002
• Issued: 08/12/2008
• Est. Priority Date: 12/14/2001
• Status: Expired due to Fees

• Current Assignee: Sound View Innovations, LLC (Sound View Innovation Holdings, LLC)
• Original Assignee: eDial, Inc. (Nokia Corporation)
• Inventors: Petrack, Scott B., Poritz, Joshua
• Primary Examiner(s): Jaroenchonwanit, Bunjob
• Assistant Examiner(s): Widhalm, Angela
• Application Number:
  US10/242,507
• Time in Patent Office: 2,161 Days
• Field of Search: 709204-205, 709227-228
• US Class Current: 709/206
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Mechanisms and techniques provide a system for performing messaging between a message server and a message client. Embodiments operate to receive a first message to be sent to a messaging client and establish a first connection to the messaging client. The system then transmits a message processing script and the first message over the first connection to the messaging client. The message processing script enables the messaging client to display the first message and to receive and display at least one second message over the first connection to the messaging client. The system maintains the first connection in an open state after transmitting the first message to the messaging client. The system then receives a second message to be sent to the messaging client and transmits the second message over the first connection to the messaging client for receipt by the message processing script, while continuing to maintain the first connection in an open state. This can be repeated for subsequent messages using the same connection.

Claims

1. In a messaging server, a method for processing message data, the method comprising the steps of:

receiving a first message to be sent to a messaging client;

establishing a first connection to the messaging client;

transmitting a message processing script and the first message over the first connection to the messaging client, the message processing script enabling the messaging client to display the first message and to receive and display at least one second message over the first connection to the messaging client independent of the operating system of the messaging client and exclusive of any messaging software residing and previously stored on the messaging client;

maintaining the first connection in an open state after transmitting the first message to the messaging client;

receiving a second message to be sent to the messaging client;

transmitting the second message over the first connection to the messaging client for receipt by the message processing script, while continuing to maintain the first connection in an open state; and

repeating, for subsequent second messages, the steps of maintaining the first connection in an open state, receiving a second message, and transmitting the second message such that separate second messages are transmitted from the messaging server to the messaging client over the first connection.

2. The method of claim 1 wherein:

the step of establishing a first connection to a messaging client comprises the step of opening a transport protocol session between a message handler and the messaging client;

the steps of transmitting the first and second messages over the first connection to the messaging client each include the steps of;

encapsulating message data within a message display script;

transmitting the message display script over the transport protocol session without terminating the transport protocol session such that the messaging processing script on messaging client receives and displays the message data encapsulated within the message display script and does not close the transport protocol session.

3. The method of claim 2 wherein the transport protocol session is a markup language transport protocol session between the messaging server and the messaging client and wherein the message processing script is included in an messaging page and defines a set of functions that a browser application operating within the messaging client can maintain for invocation by a message display script to display the message data on a display associated with the message client when the first and second message are received within the messaging client.

4. The method of claim 3 wherein the step of transmitting the second message over the first connection to the messaging client comprises the step of:

configuring the message display script to invoke functionality within the message processing script to display the message data on the display associated with the messaging client by visually modifying message data previously displayed in a former message transmitted to the messaging client.

5. The method of claim 4 wherein:

and wherein the step of repeating causes the messaging server to transmit a series of second messages, each containing message data encapsulated in a message display script, to the messaging client over the first connection, such that the messaging client receives the second messages at separate times over the same first connection and such that the messaging client perceives the receipt of multiple second messages to be related to receipt of a single messaging page of data.

6. The method of claim 1 wherein:

the message processing script and the message display script are Javascript;

the first connection is a long lived hypertext transport protocol session;

wherein the first and second messages are formatted only from at least one of a hypertext markup language and a scripting language; and

wherein the steps of transmitting the first and second messages comprise the steps of transmitting the first and second message using only a hypertext transport protocol over the long lived hypertext transport protocol session.

7. The method of claim 1 wherein the first connection is a continuously open message connection and wherein the step of maintaining the first connection in an open state comprises the steps of:

transmitting null data over the first connection during at least one period of time when no second messages are received for transmit over the first connection such that the messaging server and messaging client do not close the first connection.

8. The method of claim 7 wherein the step of transmitting null data over the first connection is performed at a time interval between the transmission of the first and second messages that is less than a timeout period of a session protocol associated with the first connection.

9. The method of claim 1 wherein at least one of the first message and second message are received from a call control server and include telephone status information as message data to allow a user of the messaging client to monitor at least one telephone call on a communications network;

and

wherein the steps of receiving the first and second messages comprise the step of;

receiving the first and second messages from a call control server that monitors operation of the at least one phone call and wherein the message data indicates a status of the at least one phone call on a display of the messaging client.

10. The method of claim 1 wherein the messaging client perceives the repeated step of transmitting the second message over the first connection to the message client to be the receipt of inbound message page data associated with the messaging page, such that time that elapses between repeated steps of receiving a second message is perceived by the messaging client to be time required to load the single messaging page.

11. In a messaging client, a method for processing message data, the method comprising the steps of:

establishing a first connection with a messaging server;

receiving, over the first connection, an messaging page including a message processing script that defines an output area in the messaging page and that defines functionality to enable the messaging client to display message data encapsulated within a message display script received by the messaging client independent of the operating system of the messaging client and exclusive of any messaging software residing and previously stored on the messaging client;

receiving a first message over the first connection from the messaging server, the first message including message data encapsulated ha a message display script;

operating the message display script in conjunction with the message processing script to display first message data associated with the first message in the output area of the messaging page;

receiving a second message over the fast connection from the messaging server, the second message including message data encapsulated in a message display script;

operating the message display script of the second message in conjunction with the message processing script to display second message data associated with the second message in the output area of the messaging page; and

repeating the steps of receiving a second message and operating the message display script of the second message such that message data in a series of second messages is received over the same first connection that remains in an open state between the message client and messaging server and is displayed to a user of the messaging client.

12. The method of claim 11 wherein the first connection is the only connection used to receive the first and second messages during the step of repeating.

13. The method of claim 11 wherein the messaging page, the first and second messages, and the scripting language are comprised only of JavaScript and a markup language.

14. The method of claim 11 wherein the steps of receiving the first message and receiving the second message comprise the step of operating only a hypertext transport protocol as a means to receive the first and second messages from the messaging server.

15. The method of claim 11 wherein the step of establishing a first connection with the messaging server comprises the steps of;

operating a browser to receive a request to enter an messaging session;

in response to receiving the request, establishing the first connection to the messaging server from the browser; and

wherein the message processing script received in the messaging page defines functionality to define an output area within a browser and defines functionality that can be invoked by a message display script containing encapsulated message data that causes the browser to display the message data in the output area upon receipt of the message display script.

16. The method of claim 15 wherein the step of operating the message display script of the second message in conjunction with the message processing script to display second message data associated with the second message in the output area of the messaging page comprises the steps of:

retrieving the message data from the second message; and

operating the message display script that encapsulated the message data in conjunction with the message processing script included in the message page to display the message data in the output area of the browser in a manner that overwrites at least a portion of formerly displayed message data in the output area, such that repeated receipt of second messages over the first connection causes the message display script of each second message to invoke functionality of the message processing script in the messaging page to display the message data of each respective second message in the output area of the messaging page in the browser.

17. The method of claim 16 wherein the browser perceives the repeated receipt of second message to be data associated with the messaging page, such that time that elapses between repeated step of receiving a second message is perceived by the browser to be time required to load the single messaging page.

18. A method for receiving messages, the method comprising the steps of:

opening a messaging connection between a messaging client and a messaging server;

receiving message data of a first type over the open message connection;

maintaining the message connection in an open state between the messaging client and the messaging server, such that the messaging client perceives that message data received over the messaging connection is not yet completely received;

receiving message data of a second type over the open messaging connection; and

repeating the steps of receiving massage data of a first type, maintaining the message connection in an open state, and receiving message data of a second type such that individual messages contained in the message data of the first and second types are successively received for display on the messaging client independent of the operating system thereof and exclusive of messaging software residing and previously stored on the messaging client and such that that the messaging client perceives that message data received over the messaging connection is not yet completely received.

19. A messaging system comprising:

a messaging client;

a messaging server;

a computer network coupling the messaging client and the messaging server;

the messaging client configured to;

establish a message connection with the messaging server over the computer network using only hypertext-related protocols and a simple scripting language;

receive a message connection response from the server indicating that the message connection is an open message connection;

receiving message data of a first type containing the contents of a first message over the open message connection;

receiving message data of a second type containing the contents of a second message over the open message connection;

repeating the steps of receiving message data while maintaining the open message connection and while awaiting delivery of a message termination indicator indicating that a message associated with the message connection has been completely received by the messaging client;

the messaging server configured to;

establish a message connection with the messaging client over the computer network using only hypertext-related protocols and a simple scripting language;

transmit a message connection response to the messaging client identifying the message connection has an open message connection;

transmitting message data of a first type containing the contents of a first message from the messaging server over the open message connection to the messaging client;

transmitting message data of a second type containing the contents of a second message over the open message connection to the messaging client;

repeating the steps of transmitting in order to provide a continuous stream of message data over the open message connection, the continuous stream of message data comprising a plurality of messages perceived by the messaging client as a single continuous message received over the open message connection for display on the messaging client independent of the operating system thereof and exclusive of proprietary messaging software residing and previously stored on the messaging client.

20. A messaging server computer system comprising:

at least one communications interface;

a memory;

a processor; and

an interconnection mechanism coupling the at least one communications interface, the memory and the processor;

wherein the memory is encoded with a server message handler application that when performed on the processor, produces a server message handler process that causes the messaging server computer system to processing message data by performing the operations of;

receiving, over the at least one communications interface, a first message to be sent to a messaging client;

establishing a first connection to the messaging client over the at least one communications interface;

transmitting a message processing script and the first message over the first connection to the messaging client, the message processing script enabling the messaging client to display the first message and to receive and display at least one second message over the first connection to the messaging client independent of the operating system thereof and exclusive of proprietary messaging software residing and previously stored on the messaging client;

maintaining the first connection in an open state after transmitting the first message to the messaging client;

receiving, over the at least one communications interface, a second message to be sent to the messaging client;

transmitting the second message over the first connection to the messaging client for receipt by the message processing script, while continuing to maintain the first connection in an open state; and

repeating, for subsequent second messages, the steps of maintaining the first connection in an open state, receiving a second message, and transmitting the second message such that separate second messages are transmitted from the messaging server to the messaging client over the first connection.

21. The message server of claim 20 wherein when the processor performs the step of establishing a first connection to a messaging client, the processor performs the step of opening a transport protocol session between a message handler and the messaging client;

wherein when the processor performs the step of transmitting the first and second messages over the first connection to the messaging client, the processor performs the steps of;

encapsulating message data within a message display script; and

transmitting the message display script over the transport protocol session without terminating the transport protocol session such that the messaging processing script on messaging client receives and displays the message data encapsulated within the message display script and does not close the transport protocol session.

22. The message server of claim 21 wherein the transport protocol session is a hypertext transport protocol session between the messaging server and the messaging client and wherein the message processing script is included in an messaging page and defines a set of functions that a browser application operating within the messaging client can maintain for invocation by a message display script to display the message data on a display associated with the message client when the first and second message are received within the messaging client.

23. The message server of claim 22 wherein when the processor performs the step of transmitting the second message over the first connection to the messaging client, the processor performs the step of:

configuring the message display script to invoke functionality within the message processing script to display the message data on the display associated with the messaging client by visually replacing message data previously displayed in a former message transmitted to the messaging client.

24. The message server of claim 23 wherein:

the message processing script and the message display script are JavaScript; and

wherein when the processor performs the step of repeating, the processor causes the messaging server to transmit a series of second messages, each containing message data encapsulated in a message display script, to the messaging client over the first connection, such that the messaging client receives the second messages at separate times over the same first connection and such that the messaging client perceives the receipt of multiple second messages to be related to receipt of a single messaging page of data.

25. The message server of claim 20 wherein:

the first connection is a long lived hypertext transport protocol session;

wherein the first and second messages are formatted only from at least one of a hypertext markup language and a scripting language; and

wherein when the processor performs each of the steps of transmitting the first and second messages the processor performs the step of transmitting the first and second message using only a hypertext transport protocol over the long lived hypertext transport protocol session.

26. The message server of claim 20 wherein the first connection is a continuously open message connection and wherein the step of maintaining the first connection in an open state comprises the steps of:

transmitting null data over the first connection during at least one period of time when no second messages are received for transmit over the first connection such that the messaging server and messaging client do not close the first connection.

27. The message server of claim 26 wherein the step of transmitting null data over the first connection is performed at a time interval between the transmission of the first and second messages that is less than a timeout period of a session protocol associated with the first connection.

28. The message server of claim 20 wherein at least one of the first message and second message are received from a call control server and include telephone status information as message data to allow a user of the messaging client to monitor at least one telephone call on a communications network;

and

wherein when the processor performs each of the steps of receiving the first and second messages, the processor performs the step of;

receiving the first and second messages from a call control server that monitors operation of the at least one phone call and wherein the message data indicates a status of the at least one phone call on a display of the messaging client.

29. The message server of claim 20 wherein the messaging client perceives the repeated step of transmitting the second message over the first connection to the message client to be the receipt of inbound message page data associated with the messaging page, such that time that elapses between repeated steps of receiving a second message is perceived by the messaging client to be time required to load the single messaging page.

30. A messaging client computer system comprising:

at least one communications interface;

a memory;

a processor;

a display; and

an interconnection mechanism coupling the at least one communications interface, the memory, the processor and the display;

wherein the memory is encoded with a client message handler application that when performed on the processor, produces a client message handler process that causes the messaging client computer system to process message data by performing the operations of;

establishing a first connection with a messaging server over the at least one communications interface;

receiving, over the first connection, an messaging page including a message processing script that defines an output area in the messaging page and that defines functionality to enable the messaging client to display message data encapsulated within a message display script received by the messaging client;

receiving a first message over the first connection from the messaging server, the first message including message data encapsulated in a message display script;

operating, on the processor, the message display script in conjunction with the message processing script to display first message data associated with the first message in the output area of the messaging page independent of the operating system and exclusive of proprietary messaging software residing and previously stored on the messaging client;

receiving a second message over the first connection from the messaging server, the second message including message data encapsulated in a message display script;

operating the message display script of the second message in conjunction with the message processing script to display, on the display, second message data associated with the second message in the output area of the messaging page; and

repeating the steps of receiving a second message and operating the message display script of the second message such that message data in a series of second messages is received over the same first connection that remains in an open state between the message client and messaging server and is displayed to a user of the messaging client.

31. The messaging client of claim 30 wherein the first connection is the only connection used to receive the first and second messages during the step of repeating.

32. The messaging client of claim 30 wherein the messaging page, the first and second messages, and the scripting language are comprised only of JavaScript and a markup language.

33. The messaging client of claim 30 wherein when the processor performs the steps of receiving the first message and receiving the second message the processor performs the steps of operating only a hypertext transport protocol as a means to receive the first and second messages from the messaging server.

34. The messaging client of claim 30 wherein when the processor performs the steps of establishing a first connection with the messaging server the processor performs the steps of:

operating a browser to receive a request to enter an messaging session;

in response to receiving the request, establishing the first connection to the messaging server from the browser; and

wherein the message processing script received in the messaging page defies functionality to define an output area within a browser and defines functionality that can be invoked by a message display script containing encapsulated message data that causes the browser to display the message data in the output area upon receipt of the message display script.

35. The messaging client of claim 34 wherein when the processor performs the steps of operating the message display script of the second message in conjunction with the message processing script to display second message data associated with the second message in the output area of the messaging page the processor performs the steps of:

retrieving the message data from the second message; and

operating the message display script that encapsulated the message data in conjunction with the message processing script included in the message page to display the message data in the output area of the browser in a manner that ovemmites at least a portion of formerly displayed message data in the output area, such that repeated receipt of second messages over the first connection causes the message display script of each second message to invoke functionality of the message processing script in the messaging page to display the message data of each respective second message in the output area of the messaging page in the browser.

36. The messaging client of claim 35 wherein the browser perceives the repeated receipt of second message to be data associated with the messaging page, such that time that elapses between repeated step of receiving a second message is perceived by the browser to be time required to load the single messaging page.

37. A messaging system comprising:

a messaging client;

a messaging server;

a computer network coupling the messaging client and the messaging server;

the messaging client configured to provide;

means for establishing a message connection with the messaging server over the computer network using only hypertext-related protocols and a simple scripting language;

means for receiving a message connection response from the server indicating that the message connection is an open message connection;

means for receiving message data of a first type containing the contents of a first message over the open message connection;

means for receiving message data of a second type containing the contents of a second message over the open message connection;

means for repeating the steps of receiving message data while maintaining the open message connection and while awaiting delivery of a message termination indicator indicating that a message associated with the message connection has been completely received by the messaging client;

the messaging server configured to provide;

means for establishing a message connection with the messaging client over the computer network using only hypertext-related protocols and a simple scripting language;

means for transmitting a message connection response to the messaging server identifying the message connection has an open message connection;

means for transmitting message data of a first type containing the contents of a first message from the messaging server over the open message connection to the messaging client;

means for transmitting message data of a second type containing the contents of a second message over the open message connection to the messaging client

means for repeating the steps of transmitting in order to provide a continuous stream of message data over the open message connection, the continuous stream of message data comprising a plurality of messages perceived by the messaging client as a single continuous message received over the open message connection for display on the messaging client independent of the operating system thereof and exclusive of proprietary messaging software residing and previously stored on the messaging client.

38. A computer program product having a computer-readable medium including computer program logic encoded thereon that performed on a processor in a computerized device having a coupling of a memory, a processor, and at least one communications interface provides a method for processing message data by performing the operations of:

receiving a first message to be sent to a messaging client;

establishing a first connection to the messaging client;

transmitting a message processing script and the first message over the first connection to the messaging client, the message processing script enabling the messaging client to display the first message and to receive and display at least one second message over the first connection to the messaging client independent of the operating system thereof and exclusive of proprietary messaging software residing and previously stored on the messaging client;

maintaining the first connection in an open state after transmitting the first message to the messaging client;

receiving a second message to be sent to the messaging client;

transmitting the second message over the first connection to the messaging client for receipt by the message processing script, while continuing to maintain the first connection in an open state; and

repeating, for subsequent second messages, the steps of maintaining the first connection in an open state, receiving a second message, and transmitting the second message messages such that separate second message are transmitted from the messaging server to the messaging client over the first connection.

39. A computer program product having a computer-readable medium including computer program logic encoded thereon that performed on a processor in a computerized device having a coupling of a memory, a processor, and at least one communications interface provides a method for processing message data by performing the operations of:

establishing a first connection with a messaging server;

receiving, over the first connection, an messaging page including a message processing script that defines an output area in the messaging page and that defines functionality to enable the messaging client to display message data encapsulated within a message display script received by the messaging client independent of the operating system thereof and exclusive of proprietary messaging software residing and previously stored on the messaging client;

receiving a first message over the first connection from the messaging server, the first message including message data encapsulated in a message display script;

operating the message display script in conjunction with the message processing script to display first message data associated with the first message in the output area of the messaging page;

receiving a second message over the first connection from the messaging server, the second message including message data encapsulated in a message display script;

operating the message display script of the second message in conjunction with the message processing script to display second message data associated with the second message in the output area of the messaging page; and

repeating the steps of receiving a second message and operating the message display script of the second message such that message data in a series of second messages is received over the same first connection that remains in an open state between the message client and messaging server and is displayed to a user of the messaging client.