Method and system for communication between a server and a client device

• US 9,807,162 B2
• Filed: 01/14/2014
• Issued: 10/31/2017
• Est. Priority Date: 03/03/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: LinkedIn Corporation (Microsoft Corporation)
• Inventors: Barman, Touradj, Fox, Kristofer
• Primary Examiner(s): Dollinger, Tonia L
• Assistant Examiner(s): COONEY, ADAM A
• Application Number:
  US14/154,522
• Publication Number:
  US 20140129658A1
• Time in Patent Office: 1,386 Days
• Field of Search: 709206, 709217, 709227, 717168
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425

Abstract

Systems and methods providing users with a rich web experience are disclosed. In one embodiment, a client and at least one server are in communication using a dual communication link. In another embodiment, a markup language based instant messaging application is disclosed. The instant messaging application may include group instant messaging. The instant messaging application may also provide group member persistence and message persistence at the server. In another embodiment, a card based web application is disclosed, where the card information and character may be shared with other users or within a group. The cards may also be configurable by users.

Claims

1. A network communication method for a first device, the first device associated with a user, the method comprising:

establishing a first connection between the first device and a first server, wherein the first connection is an XMPP connection or a JABBER connection that is maintained by sending packets or queries between the first device and the first server;

receiving, at the first device, a first message pushed from the first server through the first connection;

wherein the first message is generated at the first server in response to specific data being available at a second server for the user;

wherein the first message includes an instruction;

in response to receiving the first message, the first device automatically;

based upon the instruction in the first message, establishing a second connection between the first device and the second server, wherein the second connection is an HTTP connection that uses a different protocol than the first connection and is not established at the same time as the first connection, and

based upon the instruction in the first message, requesting, from the second server through the second connection, the specific data that was transmitted to the first server by a second device that is different than the first device;

causing at least a portion of the specific data to be displayed on a screen of the first device;

wherein the second connection is closed after the specific data is received from the second server.

2. The method of claim 1, wherein the first connection is the XMPP connection.

3. The method of claim 1, wherein the second server is different than the first server.

4. The method of claim 1, wherein:

the first device includes a first client and a second client that is different than the first client;

the first connection is between the first client and the first server;

the second connection is between the second client and the second server.

5. A method comprising:

establishing a first connection between a client device and a server, wherein the first connection is an HTTP connection;

establishing a second connection between the client device and the server, wherein the first connection is different than the second connection, wherein the second connection is an XMPP connection or a JABBER connection that is maintained by sending packets or queries between the client device and the server;

receiving, from the server, at the client device, a first data file through the first connection;

wherein the first connection is closed after receiving the first data file from the server;

after receiving the first data file through the first connection and while the client device stores the first data file;

receiving, from the server, at the client device, through the second connection, a message that pertains to the first data file,

in response to receiving the message that pertains to the first data file, automatically sending, from the client device to the server, a request for a second data file through a third connection that is different than the second connection and the first connection and that is not established at the same time as the second connection,

after sending the request, receiving, at the client device, the second data file through the third connection,

replacing the first data file with the second data file, and

causing the second data file to be displayed on a screen of the client device.

6. The method of claim 5, wherein:

the client device includes a first client and a second client that is different than the first client;

the first connection is between the first client and the server;

the second connection is between the second client and the server.

7. The method of claim 6, wherein:

the server includes a first server and a second server that is different than the first server;

the first connection is between the first client and the first server;

the second connection is between the second client and the second server.

8. The method of claim 5, wherein:

the message instructs the client device to refresh the first data file;

the second data file is an updated version of the first data file.

9. The method of claim 5, further comprising:

prior to receiving the first data file from the server, sending, from the client device, to the server, a particular request for the first data file.

10. The method of claim 5, wherein the second connection is the XMPP connection.

11. The method of claim 5, wherein the third connection is of the same type as the first connection.

12. A method comprising:

establishing a first connection between a client device and a server, wherein the first connection is an XMPP connection or a JABBER connection that is maintained by sending packets or queries between the client device and the server;

establishing, between the client device and the server, a second connection that is a different type of connection than the first connection, wherein the second connection is an HTTP connection;

wherein the first connection and the second connection are not established at the same time;

receiving, from the server, at the client device, through the first connection, a message that was generated at the server and is sent by the server in response to the server receiving specific data;

in response to receiving the message from the server at the client device through the first connection, requesting the specific data from the server through the second connection;

wherein the second connection is closed after the specific data is received from the server.

13. The method of claim 12, further comprising:

after requesting the specific data, receiving the specific data from the server, wherein the specific data comprises a data file;

after receiving the data file, receiving, through a third connection that is different than the second connection and the first connection, a second message that includes first data;

in response to receiving the second message;

automatically causing the first data to be added to the data file to create an updated data file,

causing the updated data file to be displayed at the client device.

14. The method of claim 12, wherein:

the client device includes a first client and a second client that is different than the first client;

the first connection is between the first client and the server;

the second connection is between the second client and the server.

15. The method of claim 14, wherein:

the server includes a first server and a second server that is different than the first server;

the first connection is between the first client and the first server;

the second connection is between the second client and the second server.

16. The method of claim 12, wherein the first connection is the XMPP connection.

21. The method of claim 13, wherein receiving the second message that includes the first data comprises receiving the message while the client device displays content of the data file.

17. A method comprising:

establishing a first connection between a first server and a wireless device that is associated with a user, wherein the first connection is an XMPP connection or a JABBER connection that is maintained by sending packets or queries between the wireless device and the first server;

determining that specific data is available at a second server for the user;

in response to determining that specific data is available at the second server for the user, generating a first message that includes an instruction;

sending, from the first server, to the wireless device, the first message through the first connection;

establishing a second connection between the second server and the wireless device, wherein the second connection is an HTTP connection that uses a different protocol than the first connection, is not established at the same time as the first connection, and is established based on the wireless device processing the instruction included in the first message;

receiving, from the wireless device, at the second server, a request for the specific data through the second connection;

wherein the second connection is closed after the specific data is transmitted to the wireless device.

18. The method of claim 17, wherein the first connection is the XMPP connection.

19. The method of claim 17, wherein the second server is different than the first server.

20. The method of claim 17, wherein:

the wireless device includes a first client and a second client that is different than the first client;

the first connection is between the first client and the first server;

the second connection is between the second client and the second server.

22. The method of claim 17, further comprising:

receiving the specific data from a second device that is different than the wireless device;

wherein the first message is generated in response to receiving the specific data from the second device.