System and method for providing a protocol for message data

• US 9,055,014 B2
• Filed: 01/27/2014
• Issued: 06/09/2015
• 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
• Primary Examiner(s): Ibrahim, Mohamed
• Application Number:
  US14/164,760
• Publication Number:
  US 20140143317A1
• Time in Patent Office: 498 Days
• Field of Search: None
• US Class Current: 1/1
• 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 message accessing system for accessing messages configured for receiving a plurality of messages through a network connection system from at least one sending client device and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the system comprising:

a message storage system;

a message server; and

a user interface (UI) server;

wherein the message storage system;

receives message data through the network connection system from at least one of the sending client devices, the message data comprising at least one message and associated message information for each message specifying a particular intended receiving client device; and

stores the message data;

wherein the message server;

couples to the message storage system;

retrieves only the message data from the message storage system; and

sends only the message data to the intended receiving client device though a first network connection using a non-HyperText Transfer Protocol; and

wherein the UI server;

couples to the message storage system; and

sends only UI data to the intended receiving client device through a second network connection using a HyperText Transfer Protocol, the UI data for producing webpages of a client UI of the intended receiving client device;

wherein the connecting of the message server and the UI server to the intended receiving client device occurs during an overlapping timeframe, and

wherein, during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during an overlapping timeframe.

2. The system of claim 1, wherein the message server further:

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

during the message session, sends a notification of at least one of a new message and a call to the intended receiving client device without receiving a request for data from the intended receiving client device, wherein the at least one of new message and new call is not represented in the message list.

3. The system of claim 2, wherein:

the message session ends approximately when the message server receives a session-end request from the intended receiving client device; and

during the message session, the message server automatically sends the notification of the at least one of new message and new call upon receipt of the at least one of new message and new call.

4. The system of claim 1, wherein the message server and the UI server each comprise respective computer systems.

5. The system of claim 1, wherein the connecting of the message server and the UI server to the intended receiving client device occurs during a same timeframe.

6. The system of claim 1, wherein during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during a same timeframe.

7. The system of claim 1, wherein the message server sends message data comprising a first message type to the intended receiving client device through the first network connection, and further sends message data comprising a second different message type to the intended receiving client device through a third network connection using a second different non-HyperText Transfer Protocol.

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

9. The system of claim 1, wherein the UI data comprises at least one of HTML formatted text, graphics, tables, and selectable icons for producing the webpages.

10. The system of claim 1, further comprising a program server providing a media UI file in .swf format to the intended receiving client device, wherein the UI data is rendered on the intended receiving client device using the media UI file.

11. The system of claim 1, further comprising a load balancer through which at least one of the message server and the UI server connect to the intended receiving client device.

12. The system of claim 1, further comprising respective load balancers connecting the message server and the UI server to the intended receiving client device.

13. The system of claim 1, wherein the message server connects to the intended receiving client device using a plurality of non-HyperText Transfer Protocol network connections and the UI server connects to the intended receiving client device using a plurality of HyperText Transfer Protocol network connections.

14. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processor, access messages on a message accessing system configured for receiving a plurality of messages through a network connection system from at least one sending client device and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the non-transitory computer readable medium comprising instructions for:

at a message storage system;

receiving message data through the network connection system from the at least one sending client device, the message data comprising at least one message and associated message information for each message specifying a particular intended receiving client device; and

storing the message data;

at a message server;

coupling to the message storage system;

retrieving only the message data from the message storage system; and

sending only the message data to the intended receiving client device though a first network connection using a non-HyperText Transfer Protocol; and

at a user interface (UI) server;

coupling to the message storage system; and

sending only UI data to the intended receiving client device through a second network connection using a HyperText Transfer Protocol, the UI data for producing webpages of a client UI of the intended receiving client device;

wherein the connecting of the message server and the UI server to the intended receiving client device occurs during an overlapping timeframe, and

wherein, during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during an overlapping timeframe.

15. The non-transitory computer readable medium of claim 14, further comprising instructions for, at the message server:

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

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

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

the message session ends approximately when the message server receives a session-end request from the intended receiving client device; and

during the message session, the message server automatically sends the notification of the at least one of new message and new call upon receipt of the at least one of new message and new call.

17. The non-transitory computer readable medium of claim 14, wherein the message server and the UI server each comprise respective computer systems.

18. The non-transitory computer readable medium of claim 14, wherein the connecting of the message server and the UI server to the intended receiving client device occurs during a same timeframe.

19. The non-transitory computer readable medium of claim 14, wherein during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during a same timeframe.

20. The non-transitory computer readable medium of claim 14, further comprising instructions for, at the message server:

sending message data comprising a first message type to the intended receiving client device through the first network connection; and

sending message data comprising a second different message type to the intended receiving client device through a third network connection using a second different non-HyperText Transfer Protocol.

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

22. The non-transitory computer readable medium of claim 14, wherein the UI data comprises at least one of HTML formatted text, graphics, tables, and selectable icons for producing the webpages.

23. The non-transitory computer readable medium of claim 14, further comprising instructions for, at a program server, providing a media UI file in .swf format to the intended receiving client device, wherein the UI data is rendered on the intended receiving client device using the media UI file.

24. The non-transitory computer readable medium of claim 14, further comprising instructions for, at a load balancer, connecting at least one of the message server and the UI server to the intended receiving client device.

25. The non-transitory computer readable medium of claim 14, further comprising instructions for, at respective load balancers, connecting the message server and the UI server to the intended receiving client device.

26. The non-transitory computer readable medium of claim 14, wherein the message server connects to the intended receiving client device using a plurality of non-HyperText Transfer Protocol network connections and the UI server connects to the intended receiving client device using a plurality of HyperText Transfer Protocol network connections.

27. A method for accessing messages on a message accessing system configured for receiving a plurality of messages through a network connection system from at least one sending client device and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the method comprising:

at a message storage system;

receiving message data through the network connection system from the at least one sending client device, the message data comprising at least one message and associated message information for each message specifying a particular intended receiving client device; and

storing the message data;

at a message server;

coupling to the message storage system;

retrieving only the message data from the message storage system; and

sending only the message data to the intended receiving client device though a first network connection using a non-HyperText Transfer Protocol; and

at a user interface (UI) server;

coupling to the message storage system; and

sending only UI data to the intended receiving client device through a second network connection using a HyperText Transfer Protocol, the UI data for producing webpages of a client UI of the intended receiving client device;

wherein the connecting of the message server and the UI server to the intended receiving client device occurs during an overlapping timeframe, and

wherein, during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during an overlapping timeframe.

28. The method of claim 27, further comprising, at the message server:

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

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

29. The method of claim 28, wherein:

the message session ends approximately when the message server receives a session-end request from the intended receiving client device; and

during the message session, the message server automatically sends the notification of the at least one of new message and new call upon receipt of the at least one of new message and new call.

30. The method of claim 27, wherein the message server and the UI server each comprise respective computer systems.

31. The method of claim 27, wherein the connecting of the message server and the UI server to the intended receiving client device occurs during a same timeframe.

32. The method of claim 27, wherein during the connecting of the message server and the UI server to the intended receiving client device, the sending of the message data and the sending of the UI data occur during a same timeframe.

33. The method of claim 27, further comprising, at the message server:

sending message data comprising a first message type to the intended receiving client device through the first network connection; and

sending message data comprising a second different message type to the intended receiving client device through a third network connection using a second different non-HyperText Transfer Protocol.

34. The method of claim 27, wherein the non-HyperText Transfer Protocol comprises jWebSocket protocol.

35. The method of claim 27, wherein the UI data comprises at least one of HTML formatted text, graphics, tables, and selectable icons for producing the webpages.

36. The method of claim 27, further comprising, at a program server, providing a media UI file in .swf format to the intended receiving client device, wherein the UI data is rendered on the intended receiving client device using the media UI file.

37. The method of claim 27, further comprising, at a load balancer, connecting at least one of the message server and the UI server to the intended receiving client device.

38. The method of claim 27, further comprising, at respective load balancers, connecting the message server and the UI server to the intended receiving client device.

39. The method of claim 27, wherein the message server connects to the intended receiving client device using a plurality of non-HyperText Transfer Protocol network connections and the UI server connects to the intended receiving client device using a plurality of HyperText Transfer Protocol network connections.