Method for saving and accessing desktop conference characteristics with a persistent conference object

• US 5,907,324 A
• Filed: 11/05/1997
• Issued: 05/25/1999
• Est. Priority Date: 06/07/1995
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Iyengar, Sridhar, Elliott, Jim, Boss, Dale, Larson, James A.
• Primary Examiner(s): Bayerl, Raymond J.
• Application Number:
  US08/968,857
• Time in Patent Office: 566 Days
• Field of Search: 345/330, 345/329, 345/331, 345/971, 345/332, 345/333, 345/335, 345/339, 395/200.34, 395/200.35, 395/200.31, 395/200.58, 395/200.57
• US Class Current: 715/753
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• CPC Class Codes: Y10S 715/971 Cooperative decision support systems for group of users

Abstract

A method of saving, retrieving and dynamically establishing a plurality of conference parameters. A desktop conferencing system includes a plurality of nodes connected in a network. A user of the desktop conferencing system is able to manipulate a persistent conference object where a persistent conference object is an object including a plurality of items of information pertaining to a desktop conference. Each of the conference parameters are monitored, updated and saved. It is then possible to retrieve and dynamically establish conference parameters of a conference stored in a persistent conference object by: (1) prompting a user for an identifier identifying a particular persistent conference object on disk; (2) opening the specified persistent conference object by copying it from disk to memory; (3) reading the conference parameters stored in the persistent conference object in memory; and (4) implementing the conference parameters to establish the desired conference environment.

Claims

1. A method of managing a plurality of conference parameters in a persistent conference object in a conference between participants comprising:

(a) monitoring the conference parameters;

(b) updating the conference parameters stored in the persistent conference object;

(c) saving the conference parameters to the persistent conference object upon at least one first user-initiated command or at every predetermined time interval; and

(d) automatically resuming the conference upon a second user-initiated command;

wherein the conference parameters include a policy profile that governs operations of the conference without participants'"'"' manual intervention, said policy profile including a turn-taking protocol defining speaking rules to be followed by each participant.

2. The method of claim 1, wherein the persistent conference object includes application identifier information for identifying a particular application and application status information for indicating whether that application is active or inactive.

3. The method of claim 1, wherein the persistent conference object includes document identifier information for identifying a particular document and document status information for indicating whether that document is active or inactive.

4. The method of claim 1, wherein the persistent conference object includes information on at least one user policy.

5. The method of claim 1, wherein the step of saving conference parameters to a particular persistent conference object further includes the steps of:

prompting the user for an object name to be associated with the particular persistent conference object;

storing the conference parameters to the object identified by the user-selected file name.

6. The method of claim 1, wherein the step of monitoring the conference parameters further includes the steps of:

detecting when an application is opened and when an application is closed by a participant;

detecting when a document is opened and when a document is closed by a participant;

detecting when a new participant joins the conference and when a participant leaves a conference; and

detecting a change in any one of a plurality of conference policies.

7. The method of claim 1, wherein the persistent conference object includes participant identification information for identifying current and new participants and participant status information for indicating whether or not a particular participant is currently active or is no longer a participant of the conference.

8. The method of claim 1, wherein the updating of the conference parameters stored in the persistent conference object is to memory, and

wherein the saving of the conference parameters to the persistent conference object is onto a disk.

9. A method of automatically establishing a conference environment for participants comprising:

(a) opening a persistent conference object on disk;

(b) reading the persistent conference object for the conference parameters; and

(c) implementing the conference parameters to establish the desired conference environment upon a user-initiated command;

wherein the conference parameters include a policy profile that governs operations of the conference without participants'"'"' manual intervention, said policy profile including a turn-taking protocol defining speaking rules to be followed by each participant.

10. The method of claim 9, wherein the step of implementing the conference parameters includes the steps of establishing a communication link between the participants.

11. The method of claim 9, wherein the step of implementing the conference parameters further includes the step of displaying a list of application programs that were either opened at the time the persistent conference object was saved or applications that were intended by the participants to be used during the conference.

12. The method of claim 9, wherein the step of implementing the conference parameters further comprises the step of displaying a list of documents that were opened at the time the persistent conference object was saved to disk or that were intended by the participants to be used during the conference,

wherein the participants may open any of the documents on the list by selecting those documents desired.

13. The method of claim 9, wherein the step of implementing the conference parameters further includes the steps of:

opening the applications indicated in the persistent conference object; and

opening the documents indicated in the persistent conference object.

14. The method of claim 9, wherein the persistent conference object includes document identifier information and document status information.

15. The method of claim 9, wherein the persistent conference object includes application identifier information and application status information.

16. The method of claim 9, wherein the persistent conference object includes participant identifier information and participant status information.

17. The method of claim 9, wherein the persistent conference object includes policy identifier information and policy status information.

18. A computer readable medium having embodied thereon a computer program, the computer program being executable by a machine, said computer program including:

(a) a code segment for monitoring a plurality of conference parameters in a persistent conference object in a conference between participants;

(b) a code segment for updating the conference parameters stored in the persistent conference object;

(c) a code segment for saving the conference parameters to the persistent conference object upon at least one first user-initiated command or at every predetermined time inverval; and

(d) a code segment for automatically resuming the conference upon a second user-initiated command;

wherein the conference parameters include a policy profile that governs operations of the conference without participants'"'"' manual intervention, said policy profile including a turn-taking protocol defining speaking rules to be followed by each participant.

19. A computer readable medium having embodied thereon a computer program as claimed in claim 18, wherein the persistent conference object includes application identifier information for identifying a particular application and application status information for indicating whether that application is active or inactive.

20. A computer readable medium having embodied thereon a computer program as claimed in claim 18, wherein the persistent conference object includes document identifier information for identifying a particular document and document status information for indicating whether that document is active or inactive.