System for conducting multi-media communication sessions

• US 8,499,084 B2
• Filed: 08/06/2008
• Issued: 07/30/2013
• Est. Priority Date: 02/06/2006
• Status: Expired due to Fees

• Current Assignee: Xumii, Inc. (Myriad Group AG)
• Original Assignee: Xumii, Inc. (Myriad Group AG)
• Inventors: Wooldridge, Christopher, Howells, Michael David
• Primary Examiner(s): SALL, EL HADJI MALICK
• Application Number:
  US12/187,378
• Publication Number:
  US 20090094369A1
• Time in Patent Office: 1,819 Days
• Field of Search: 709/203, 709/228, 455/566
• US Class Current: 709/228
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system for conducting multi-media communication sessions between two or more terminals includes a smart client application to dynamically load application code and data from servers on demand using an application management protocol. In the present embodiment the smart client is maintained on each terminal and initially executes a core application. This core application provides a user interface for selectively establishing and maintaining a communication session with a remote terminal. The core application also provides a user interface for including shared applications in the session to which the remote terminal has access. The core application provides a further user interface for combining two sessions into one that includes all participants and shared applications from both original sessions. Each shared application provides a user interface to each participant of the session according to their access rights: the participant who added an application to a session will typically have full access, while other participants typically have more restricted access. The core application uses a session management protocol to maintain consistent session state between all terminals involved in a session.

Claims

1. A system including:

a client application maintainable on a first communication terminal for dynamically loading on demand, data and executable code from a separate server in a network, the data and executable code representing an application held temporarily on the first communication terminal and executed by the client application;

a core application maintained on core application servers in the network for execution by communication terminals and downloadable by the client application from a core application server for execution by the first communication terminal on demand, and when executed, the core application provides a user interface for selectively establishing and maintaining general purpose person to person communication sessions between the first communication terminal and a second communication terminal which has previously downloaded the core application, the core application allowing a general purpose person to person communication session between the first communication terminal and the second communication terminal;

a multiplicity of shared applications maintained on shared application servers in the network for execution by communication terminals and downloadable by the client application from a shared application server for execution by the client application on demand, and when executed the shared applications provide a user interface for presenting and controlling a variety of multi-media content from the second communication terminal; and

an application management protocol by which the client application communicates with the core application servers and shared application servers on the network to populate and maintain its data and executable code for the core applications and shared applications respectively.

2. A system according to claim 1 wherein the first communication terminal is a handheld device.

3. A system according to claim 2 wherein the first handheld device is a cellular telephone.

4. A system according to claim 1 wherein a user of the first and second communication terminal is allocated one or more unique user identifiers.

5. A system according to claim 4 wherein the core application associates with each user identifier a set of subscriptions to shared applications.

6. A system according to claim 5 wherein the core application allows the terminal user to access any shared application to which they have subscribed.

7. A system according to claim 4 wherein the shared applications associate with each user identifier a collection of data exclusively allocated to that user.

8. A system according to claim 4 wherein the unique identifier is a SIP address.

9. A system according to claim 4 wherein the unique identifier is an Instant Messaging service username.

10. A system according to claim 1 wherein the application management protocol is carried within the Transmission Control Protocol (TCP).

11. A system according to claim 1 wherein the application management protocol is carried within the Hyper-Text Transfer Protocol (HTTP).

12. A system according to claim 1 further comprising a mechanism for establishing and maintaining person-to-person communication sessions with shared applications, including:

a user interface to the core application allowing a first user to initiate a session with a second user;

a user interface to the core application allowing a first user to select a shared application to include in the session such that it is accessible to the second user;

a user interface to the shared application allowing the first user full access to their data, and a user interface to the shared application allowing the second user more restricted access to the first user'"'"'s data;

a user interface to the core application allowing a user to merge two sessions to create a combined session with multiple participants and shared applications; and

a session management protocol by which the core application maintains consistent session state between the participating terminals.

13. A system according to claim 12 wherein the session management protocol is the Session Initiation Protocol (SIP).

14. A system according to claim 12 wherein the session management protocol is based on an Instant Messaging protocol such as XMPP or IMPS and extensions thereof.

15. A system according to claim 7 wherein each shared application included in a session provides a temporary secure key by which session participants may gain access to the shared application.

16. A system according to claim 7 wherein the core application allows two sessions to be combined into a single session such that the participants and shared applications in the new session include those from both original sessions.

17. A system according to claim 7 wherein the core application allows a user to maintain multiple concurrent sessions and to switch between them.