SYSTEM AND METHOD FOR PROVIDING A PROTOCOL FOR MESSAGE DATA

• US 20130086153A1
• Filed: 09/20/2012
• Published: 04/04/2013
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: j2 Cloud Services, LLC (Consensus Cloud Solutions, Inc.)
• Original Assignee: Advanced Messaging Technologies, Inc. (J2 Global, Inc.)
• Inventors: Vendrow, Vlad
• Granted Patent: US 8,639,754 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

Described herein are systems and methods for enabling access to messages on a message service system via user interfaces of receiving client devices. The message service system comprises a message storage system and a message access system. The message storage system receives messages from sending client devices and stores message data. The message access system comprises a message server and UI server. A receiving client device is connected with the UI server through a first HTTP connection for receiving UI data for building webpages of the user interface and is connected with the message server through a second non-HTTP connection for receiving message data for populating the webpages. The UI data does not comprise any message data. A client protocol engine on the receiving client device and a server protocol engine on the message server define and provide the non-HTTP protocol for receiving and transmitting message data.

Claims

1. A system for accessing messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the system comprising:

a message server coupled to the message storage system and configured for;

retrieving message data from the message storage system and sending the message data to a receiving client device through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message; and

a user interface (UI) server configured for;

sending UI data to the receiving client device through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data, the UI data for producing webpages of the client UI on the receiving client device, the message server and the UI server being different servers, the message server and UI server being simultaneously coupled to the receiving client device, wherein the message server sends only message data through the first network connection to the receiving client device while the UI server simultaneously sends only UI data through the second network connection to the receiving client device.

2. The system of claim 1, wherein the message server sends only message data through the first network connection to the receiving client device during a same or overlapping timeframe that the UI server sends only UI data through the second network connection to the receiving client device.

3. The system of claim 1, wherein:

the message server sends message data to the receiving client device through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type; and

the message server is further configured for sending message data to the receiving client device through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

4. The system of claim 1, wherein the message data comprises no UI data and the UI data comprises no message data.

5. The system of claim 1, wherein the message server is further configured for:

sending a message list of current messages to the receiving client device at a beginning of a message session with the receiving client device; and

during the message session, sending a notification of a new message or call to the receiving client device without receiving a request for data from the receiving client device, wherein the new message or call is not represented in the message list.

6. The system of claim 5, wherein:

the message session ends at an approximate point in time that the message server receives a session-end request from the receiving client device; and

during the message session, the message server automatically sends the notification of the new message or call upon receiving the new message or call.

7. The system of claim 1, wherein the non-HyperText Transfer Protocol comprises jWebSocket protocol.

8. The system of claim 1, wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

9. A non-transitory computer readable medium having instructions stored thereon when executed by a processor, accesses messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the non-transitory computer readable medium comprising instructions for:

at a message server, retrieving message data from the message storage system and sending the message data to a receiving client device through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message; and

at a user interface (UI) server, sending UI data to the receiving client device through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data, the UI data for producing webpages of the client UI on the receiving client device, the message server and the UI server being different servers, the message server and UI server being simultaneously coupled to the receiving client device, wherein the message server sends only message data through the first network connection to the receiving client device while the UI server simultaneously sends only UI data through the second network connection to the receiving client device.

10. The non-transitory computer readable medium of claim 9, wherein the message server sends only message data through the first network connection to the receiving client device during a same or overlapping timeframe that the UI server sends only UI data through the second network connection to the receiving client device.

11. The non-transitory computer readable medium of claim 9, wherein the message server sends message data to the receiving client device through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type, the non-transitory computer readable medium further comprising instructions for:

at the message server, sending message data to the receiving client device through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

12. The non-transitory computer readable medium of claim 9, wherein the message data comprises no UI data and the UI data comprises no message data.

13. The non-transitory computer readable medium of claim 9, further comprising instructions for:

at the message server;

sending a message list of current messages to the receiving client device at a beginning of a message session with the receiving client device; and

during the message session, sending a notification of a new message or call to the receiving client device without receiving a request for data from the receiving client device, wherein the new message or call is not represented in the message list.

14. The non-transitory computer readable medium of claim 13, wherein:

the message session ends at an approximate point in time that the message server receives a session-end request from the receiving client device; and

during the message session, the message server automatically sends the notification of the new message or call upon receiving the new message or call.

15. The non-transitory computer readable medium of claim 9, wherein the non-HyperText Transfer Protocol comprises jWebSocket protocol.

16. The non-transitory computer readable medium of claim 9, wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

17. A system for accessing messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the system comprising:

a receiving client device configured for;

receiving message data from a message server through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message;

receiving user interface (UI) data from a UI server through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data; and

using the UI data for producing webpages of the client UI on the receiving client device, the message server and the UI server being different servers, the receiving client device being simultaneously coupled to the message server and UI server, wherein the receiving client device receives only message data from the message server through the first network connection while simultaneously receiving only UI data from the UI server through the second network connection.

18. The system of claim 17, wherein the receiving client device receives message data through the first network connection during a same or overlapping timeframe as receiving UI data through the second network connection.

19. The system of claim 17, wherein the receiving client device, in parallel, receives and processes message data through the first network connection and UI data through the second network connection.

20. The system of claim 17, wherein:

the receiving client device receives message data from the message server through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type; and

the receiving client device is further configured for receiving message data from the message server through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

21. The system of claim 17, wherein the message data comprises no UI data and the UI data comprises no message data.

22. The system of claim 17, wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

23. The system of claim 17, wherein:

the receiving client device comprises a JavaScript engine and message data communicator engine; and

the JavaScript engine requests the message data from the message data communicator engine which submits the request to the message server for requesting the message data.

24. A non-transitory computer readable medium having instructions stored thereon when executed by a processor, accesses messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the non-transitory computer readable medium comprising instructions for:

at a receiving client device;

receiving message data from a message server through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message;

receiving user interface (UI) data from a UI server through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data; and

using the UI data for producing webpages of the client UI on the receiving client device, the message server and the UI server being different servers, the receiving client device being simultaneously coupled to the message server and UI server, wherein the receiving client device receives only message data from the message server through the first network connection while simultaneously receiving only UI data from the UI server through the second network connection.

25. The non-transitory computer readable medium of claim 24, wherein the receiving client device receives message data through the first network connection during a same or overlapping timeframe as receiving UI data through the second network connection.

26. The non-transitory computer readable medium of claim 24, wherein the receiving client device, in parallel, receives and processes message data through the first network connection and UI data through the second network connection.

27. The non-transitory computer readable medium of claim 24, wherein the receiving client device receives message data from the message server through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type, the non-transitory computer readable medium further comprising instructions for:

at the receiving client device, receiving message data from the message server through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

28. The non-transitory computer readable medium of claim 24, wherein the message data comprises no UI data and the UI data comprises no message data.

29. The non-transitory computer readable medium of claim 24, wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

30. The non-transitory computer readable medium of claim 24, wherein:

the receiving client device comprises a JavaScript engine and message data communicator engine; and

the JavaScript engine requests the message data from the message data communicator engine which submits the request to the message server for requesting the message data.