Method and apparatus for managing communications with selective subsets of conference participants

• US 5,805,830 A
• Filed: 08/13/1997
• Issued: 09/08/1998
• Est. Priority Date: 09/30/1994
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Reese, Ken, Rothrock, Lewis
• Primary Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/910,805
• Time in Patent Office: 391 Days
• Field of Search: 395/200.04, 395/200.02, 395/200.15, 395/200.19, 395/311, 395/312, 395/200.34, 395/200.35, 395/200.68, 395/200.79, 370/62, 370/60.1, 370/61, 370/94.3, 370/260, 370/265, 370/270, 345/330
• US Class Current: 709/205
• CPC Class Codes: G06F 2213/0038 System on Chip
• 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

Abstract

A first communication manager (CM) equipped with the ability to dynamically maintain a first multiple of communication recipient distribution lists is provided to a computer system. The first CM is also provided with operational logic capable of being instructed to send a particular piece of communication to all members of a particularized one of the distribution lists by naming only the distribution list. In one embodiment, a second CM is further provided. The second CM is equipped with the ability to dynamically maintain a second multiple of communication recipient distribution lists, the second distribution lists being a superset of the first distribution lists. The second CM is further equipped to track whether a corresponding distribution list is maintained by the first CM for each of its distribution lists, and their usage counts by executing applications. Lastly, the second CM is further equipped to dynamically adjust its manner of instructing the first CM on recipients of communications.

Claims

1. A computer system for use as a communication end-point, the computer system comprising:

a) an execution unit for executing programs; and

b) a storage unit storing a first communication manager to be executed by the execution unit during operation, the first communication manager being equipped with

b.1.1) logic for maintaining a first plurality of communication distribution lists, each of the first communication distribution lists being uniquely identifiable and having at least one list member, each list member being a remote recipient of communications or a distribution list identifier, the first communication manager having sharability constraints to ensure sharability of the first plurality of communication distribution lists among a plurality of communication applications, and

b.1.2) logic for performing physical layer services for communicating with other communication end-point computer systems including logic for sending a communication to all remote recipients who are unnested or nested members of one of the first communication distribution lists, on behalf of an application being executed by the execution unit, upon so instructed with instructions which, for recipient information, merely supply the unique identification information of a particular one of the first communication distribution lists.

2. The computer system as set forth in claim 1, wherein the logic for maintaining the first communication distribution lists includes

b.1.1.1) logic for creating one of the first communication distribution lists responsive to a create request,

b.1.1.2) logic for deleting one of the first communication distribution lists responsive to a delete request.

3. The computer system as set forth in claim 2, wherein the logic for creating one of the first communication distribution lists includes logic for detecting whether creating the one of the first communication distribution lists would violate sharability constraints on the first communication manager, and rejecting the request upon detecting such potential violation.

4. The computer system as set forth in claim 1, wherein,

the logic for maintaining the first communication distribution lists stores only identification information of the remote recipient for each remote recipient list member in each of the first communication distribution lists;

the logic for maintaining the first communication distribution lists further maintains a distribution list participant directory comprising identification and destination information of each remote recipient.

5. The computer system as set forth in claim 1, wherein, the logic for sending a communication to all remote recipients on behalf of the application includes logic for sending the communication without using duplicate data buffers when supplied with the unique identification information of a particular one of the first communication distribution lists.

6. The computer system as set forth in claim 5, wherein, the logic for sending a communication to all remote recipients on behalf of the application further includes logic for invoking the sending logic itself for sending the communication to remote recipients who are nested list members of the particular one of the first communication distribution lists.

7. The computer system as set forth in claim 1, wherein, said storage unit further stores a second communication manager being executed by the execution unit during operation, the second communication manager including

b.2.1) logic for maintaining a second plurality of communication distribution lists, the second communication distribution lists being a superset of the first communication distribution lists, each of the second communication distribution lists also being uniquely identifiable and having at least one list member, each list member also being a remote recipient of communications or a distribution list identifier, each of the second communication distribution lists further having an indicator indicating whether there is an identical one maintained among the first communication distribution lists, each of the second communication distribution lists further having a usage count of applications being executed by execution unit using the particular one of the second communication distribution lists, and

b.2.2) logic for requesting physical layer services for communicating with other communication end-point computer systems including logic for making individualized requests to the first communication manager if the communication is intended for all remote recipients who are unnested or nested members of one of the second communication distribution lists without an identical one being maintained among the first communication distribution lists, and for making a single consolidated request supplying merely unique identification information of a corresponding one of the first communication distribution lists to the first communication manager if the communication is intended for all remote recipients who a re unnested or nested members of one of the second communication distribution lists having an identical one being maintained among the first communication distribution lists.

8. The computer system as set forth in claim 7, wherein the logic for maintaining the second communication distribution lists includes

b.2.1.1) logic for adding a remote recipient to one of the second communication distribution lists responsive to an add request, including logic for requesting the first communication manager to create a corresponding one among the first communication distribution lists if a resulting one of the second communication distribution lists from performing the add request is a new unique one of the second communication distribution lists,

b.2.1.2) logic for removing a remote recipient from one of the second communication distribution lists responsive to a remove request, including logic for requesting the first communication manager to destroy a corresponding one among the first communication distribution lists, if the usage count of the one among the second communication distribution lists against which the removal request is to be performed goes to zero upon performing the removal request and the usage count going to zero one of the second communication distribution lists is also maintained by the first communication manager.

9. The computer system as set forth in claim 8, wherein the logic for adding a remote recipient to one of the second communication distribution lists further includes logic for determining whether the resulting one of the second communication distribution lists upon performing the add request is unique, logic for setting the usage count of the resulting one of the second communication distribution lists to one if the resulting one of the second communication distribution lists is unique, and logic for incrementing the usage count of an identical one of the second communication distribution lists by one and discarding the resulting one of the second communication distribution lists if the resulting one of the second communication distribution lists is not unique.

10. The computer system as set forth in claim 9, wherein the logic for adding a remote recipient to one of the second communication distribution lists further includes logic for creating a new one of the second communication distribution lists and adding the remote recipient to the new one of the second communication distribution lists if the one of the second communication distribution lists against which the add request is to be performed has not been previously created, and logic for copying one of the second communication distribution lists and adding the remote recipient to the copied one of the second communication distribution lists if the one of the second communication distribution lists against which the add request is to be performed has been previously created.

11. The computer system as set forth in claim 8, wherein the logic for removing a remote recipient from one of the second communication distribution lists further includes logic for determining whether the resulting one of the second communication distribution lists, upon performing the removal request, is unique, logic for setting the usage count of the resulting one of the second communication distribution lists to one if the resulting one of the second communication distribution lists is unique, and logic for incrementing the usage count of an identical one of the second communication distribution lists by one and discarding the resulting one of the second communication distribution lists if the resulting one of the second communication distribution lists is not unique.

12. The computer system as set forth in claim 11, wherein the logic for removing a remote recipient from one of the second communication distribution lists further includes logic for copying one of the second communication distribution lists and removing the remote recipient from the copied one of the second communication distribution lists.

13. In a network of communication end-point computer systems comprising a plurality of applications executing on the computer systems communicating with one another, an automated method implemented in at least one of said computer systems for selectively distributing communications to the other computer systems, the method comprising the steps of:

a) maintaining a first plurality of communication distribution lists by a first communication manager on the communication end-point computer system, the first communication manager having sharability constraints to ensure the sharability of the first plurality of communication distribution lists among the plurality of applications, each of the communication distribution lists being uniquely identifiable and having at least one list member, each list member being a remote recipient of communication on the other communication end-point computer systems or a distribution list identifier, and

b) performing physical layer services by the first communication manager for communicating with remote recipients on the other communication end-point computer systems by nested members of one of the first communication distribution lists, one behalf of an application executing on the communication end-point computer system, upon so instructed with instruction which, for recipient information, merely supply the unique identification information of a particular one of the first communication distribution lists.

14. The method as set forth in claim 13, wherein step (a) comprises the steps of:

a.1) creating one of the first communication distribution lists by the first communication manager responsive to a create request,

a.2) deleting one of the first communication distribution lists by the first communication manager responsive to a delete request.

15. The method as set forth in claim 14, wherein step (a.1) further comprises detecting by the first communication manager whether creating one of the first communication distribution lists would violate sharability constraints on the first communication manager, and rejecting by the first communication manager the create request upon detecting such potential violation.

16. The method as set forth in claim 13, wherein,

step (a) comprises storing only identification information of the remote recipient for each remote recipient list member in each of the first communication distribution lists by the first communication manager;

step (a) further comprises maintaining a distribution list participant directory by the first communication manager having identification and destination information of each remote recipient.

17. The method as set forth in claim 13, wherein, sending a communication to all remote recipients on behalf of the application in step (b) comprises sending the communication by the first communication manager without using duplicate data buffers when supplied with the unique identification information of a particular one of the first communication distribution lists.

18. The method as set forth in claim 13, wherein, sending a communication to all remote recipients on behalf of the application in step (b) involves recursive performance of step (b) for sending the communication to remote recipients who are nested list members of the particular one of the first communication distribution lists, one nesting level at a time.

19. The method as set forth in claim 13, wherein, the method further comprises the steps of

c) maintaining a second plurality of communication distribution lists by a second communication manager, the second communication distribution lists being a superset of the first communication distribution lists, each of the second communication distribution lists also being uniquely identifiable and having at least one list member, each list member also being a remote recipient of communications or a distribution list identifier, each of the second communication distribution lists further having an indicator indicating whether there is an identical one maintained among the first communication distribution lists, each of the second communication distribution lists further having a usage count of executing applications using the particular one of the second communication lists, and

d) requesting physical layer services for communicating with other communication end-point computer systems by the second communication manager including making individualized requests to the first communication manager if the communication is intended for all recipients of the one of the second communication distribution lists without an identical one being maintained among the first communication distribution lists, and making a single consolidated request supplying merely unique identification information of an identical one of the first communication distribution lists to the first communication manager if the communication is intended for all recipients of one of the second communication distribution lists being maintained among the first communication distribution lists.

20. The method as set forth in claim 19, wherein step (c) comprises:

c.1) adding a remote recipient to one of the second communication distribution lists by the second communication manager responsive to an add request, and requesting the first communication manager to create a corresponding one among the first communication distribution lists by the second communication manager if a resulting one of the second communication distribution lists from performing the add request is a new unique one of the second communication distribution lists,

c.2) removing a remote recipient from one of the second communication distribution lists by the second communication manager, and requesting the first communication manager to destroy a corresponding one among the first communication distribution lists by the second communication manager, if the usage count of the one among the second communication distribution lists against which the removal request is to be performed goes to zero upon performing the removal request and the usage count going to zero one of the second communication distribution lists is also maintained by the first communication manager.

21. The method as set forth in claim 20, wherein step (c.1) further includes determining whether the resulting one of the second communication distribution lists upon performing the add request is unique by the second communication manager, setting the usage count of the resulting one of the second communication distribution lists to one by the second communication manager if the resulting one of the second communication distribution lists is unique, incrementing the usage count of an identical one of the second communication distribution lists by one by the second communication manager, and discarding the resulting one of the second communication distribution lists by the second communication manager if the resulting one of the second communication distribution lists is not unique.

22. The method as set forth in claim 21, wherein step (c.1) further includes creating a new one of the second communication distribution lists and adding the remote recipient to the new one of the second communication distribution lists by the second communication manager if the one of the second communication distribution lists against which the add request is to be performed has not been previously created, and copying one of the second communication distribution lists and adding the remote recipient to the copied one of the second communication distribution lists by the second communication manager if the one of the second communication distribution lists against which the add request is to be performed has been previously created.

23. The method as set forth in claim 20, wherein step (c.2) further includes determining whether the resulting one of the second communication distribution lists upon performing the removal request is unique by the second communication manager, setting the usage count of the resulting one of the second communication distribution lists to one by the second communication manager if the resulting one of the second communication distribution lists is unique, incrementing the usage count of an identical one of the second communication distribution lists by one by the second communication manager, and discarding the resulting one of the second communication distribution lists by the second communication manager if the resulting one of the second communication distribution lists is not unique.

24. The method as set forth in claim 23, wherein step (c.2) further includes copying one of the second communication distribution lists and removing the remote recipient from the copied one of the second communication distribution lists by the second communication manager.

25. A communication end-point conferencing system, the conferencing system comprising:

a) a first communication manager equipped with

a.1) logic for maintaining a first plurality of conference communication distribution lists being uniquely identifiable and having at least one list member, each list member being a remote recipient of conference communications or a distribution list identifier, the logic including sharability constraints to ensure the sharability of the first plurality of conference communication distribution lists among a plurality of communication applications executable by the communication end-points, and

a.2) logic for performing physical layer services for communicating with other communication end-point conferencing systems including logic for sending a conference communication to all remote recipients who are unnested or nested members of one of the conference communication distribution lists, on behalf of a user-initiated conferencing application, upon so instructed with instructions which, for recipient information merely supply the unique identification information of a particular one of the first conference communication distribution lists.

26. The conferencing system as set forth in claim 25, wherein,

the logic for maintaining the first conferencing communication distribution lists stores only identification information of the remote recipient for each remote recipient list member in each of the first conferencing communication distribution lists;

the logic for maintaining the first conferencing communication distribution lists further maintains a distribution list participant directory comprising identification and destination information of each remote recipient.

27. The conferencing system as set forth in claim 26, wherein the logic for maintaining the first conferencing communication distribution lists includes

a.1.1) logic for creating one of the first conferencing com4munication distribution lists responsive to a create request, and

a.1.2) logic for deleting one of the first conferencing communication distribution lists responsive to a delete request.

28. The conferencing system as set forth in claim 25, wherein, the logic for sending a conferencing communication to all remote recipients on behalf of the conferencing application includes logic for sending the conferencing communication without using duplicate data buffers when supplied with the unique identification information of a particular one of the first conferencing communication distribution lists.

29. The conference system as set forth in claim 28, wherein, the logic for sending a communication to all remote recipients on behalf of the application further includes logic for invoking the sending logic itself for sending the communication to remote recipients who are nested list members of the particular one of the first communication distribution lists.

30. The conferencing system as set forth in claim 25, wherein, the conferencing system further comprises:

b) a second communication manager equipped with

b.1) logic for maintaining a second plurality of conferencing communication distribution lists, the second conferencing communication distribution lists being a superset of the first conferencing communication distribution lists, each of the second conferencing communication distribution lists also being uniquely identifiable and having at least one list member, each list member also being a remote recipient of conferencing communications or a distribution list identifier, each of the second conferencing communication distribution lists further having an indicator indicating whether there is an identical one maintained among the first conferencing communication distribution lists, each of the second conferencing communication distribution lists further having a usage count of conferencing applications using the particular one of the second conferencing communication distribution lists, and

b.2) logic for requesting physical layer services for communicating with other communication end-point conferencing systems including logic for making individualized requests to the first communication manager if the conferencing communication is intended for all remote recipients who are unnested or nested members of one of the second conferencing communication distribution lists without an identical one being maintained among the first conferencing communication distribution lists, and for making a single consolidated request supplying merely unique identification information of an identical one of the first conferencing communication distribution lists to the first communication manager if the communication is intended for all remote recipients who are unnested or nested list members of one of the second conferencing communication distribution lists also being maintained among the first conferencing communication distribution lists.

31. The conferencing system as set forth in claim 30, wherein the logic for maintaining the second conferencing communication distribution lists includes

b.1.1) logic for adding a remote recipient to one of the second conferencing communication distribution lists responsive to an add request, including logic for requesting the first communication manager to create a corresponding one among the first conferencing communication distribution lists if a resulting one of the second conferencing communication distribution lists from performing the add request is a new unique one of the second conferencing communication distribution lists,

b.1.2) logic for removing a remote recipient from one of the second conferencing communication distribution lists responsive to a remove request, including logic for requesting the first communication manager to destroy a corresponding one among the first conferencing communication distribution lists, if the usage count of the one among the second conferencing communication distribution lists against which the removal request is to be performed goes to zero upon performing the removal request and the usage count going to zero one of the second conferencing communication distribution lists is also maintained by the first communication manager.