Resource management system for a broadband multipoint bridge

• US 5,742,772 A
• Filed: 05/05/1997
• Issued: 04/21/1998
• Est. Priority Date: 11/17/1995
• Status: Expired due to Term

• Current Assignee: Nokia of America Corporation (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Sreenan, Cormac J.
• Primary Examiner(s): Harrell, Robert B.
• Assistant Examiner(s): Najjar, Saleh
• Application Number:
  US08/851,056
• Time in Patent Office: 351 Days
• Field of Search: 395/200.56, 395/200.7, 395/200.59, 370/85.13, 370/17, 370/54
• US Class Current: 709/226
• CPC Class Codes: H04L 2012/5616 Terminal equipment, e.g. codecs, synch.
• CPC Class Codes: H04L 2012/563 Signalling, e.g. protocols, reference model
• CPC Class Codes: H04L 2012/5631 Resource management and allocation
• CPC Class Codes: H04L 2012/5632 Bandwidth allocation
• CPC Class Codes: H04L 2012/5638 Services, e.g. multimedia, GOS, QOS
• CPC Class Codes: H04L 2012/5642 Multicast/broadcast/point-multipoint, e.g. VOD
• CPC Class Codes: H04L 2012/5643 Concast/multipoint-to-point
• CPC Class Codes: H04L 2012/5674 Synchronisation, timing recovery or alignment
• CPC Class Codes: H04Q 11/0478 Provisions for broadband connections

Abstract

An electronic bridge resource management system, having a programmatically-implemented processing system. A bridge service interfaces with a plurality of clients and receives a quality of service (QOS) specification from each of the clients. A resource manager receives a QOS specification from the bridge service, distributes at least one QOS constraint associated with the QOS specification across flow processing modules of a channel, determines resource requirements for each of the flow processing modules, and then determines whether bridge resources can be allocated to meet the QOS specification. The clients may alter their QOS specifications and retry if the resource manager denies them admission because of a lack of available bridge resources.

Claims

1. An electronic multipoint bridge resource management system, comprising:

a programmatically-implemented processing system having;

a multipoint bridge service that interfaces with a plurality of clients and maintains record information about a group of said clients participating in a multi-user application, where said bridge service receives a quality of service (QOS) specification from each of said clients; and

a resource manager that receives said QOS specification from said bridge service, distributes at least one QOS constraint associated with said QOS specification across flow processing modules of a channel, determines resource requirements for each of said flow processing modules, and determines whether bridge resources can be allocated to meet said QOS specification;

wherein said clients may alter their QOS specifications and retry if said resource manager denies them admission because of a lack of available bridge resources;

wherein said flow processing modules perform application-level functions including audio and/or video combination, synchronization or transformation, and where said flow processing modules are interconnected by flows for data transport; and

wherein said resource requirements include memory, CPUs or DSPs.

2. The system of claim 1, wherein said client is a program running at a multimedia terminal.

3. The system of claim 1, wherein said processing system is implemented on a single host.

4. The system of claim 1, wherein said processing system is implemented on a plurality of distributed hosts.

5. The system of claim 1, wherein said processing system maintains group, client, channel, FPM/thread, and flow data structures.

6. The system of claim 5, wherein said FPM/thread data structure includes a list of resource handles, where said resource handles entitle the associated flow processing module to specific bridge resources.

7. The system of claim 1, wherein said QOS specification includes parameters indicating type of contract, traffic, and performance.

8. A method for managing computer system resources, comprising the steps of:

passing a quality of service (QOS) specification to a computer system;

said computer system associating estimated computer system resources to application-level channel processing activities based upon constraints derived from said QOS specification;

said computer systems granting or denying admission to computer systems resources depending on availability of said computer systems resources; and

altering said QOS specification and retrying if admission is denied;

wherein said channel processing activities include audio and/or video combination, synchronization or transformation and;

wherein said computer system resources include memory, CPUs or DSPs.

9. The method of claim 8, wherein said computer system is a server.

10. The method of claim 9, wherein said server is a bridge.

11. The method of claim 10, wherein the step of passing a quality of service (QOS) specification includes the substeps of:

a user specifying a high-level application QOS specification; and

translating said application QOS specification to a low-level system QOS specification.

12. The method of claim 10, wherein the step of associating estimated bridge resources to channel processing activities includes the substeps of:

performing QOS constraint distribution across a set of flow processing modules associated with said channel processing activities; and

determining resource requirements for each flow processing module.

13. The method of claim 10, further comprising the steps of:

instantiating flow processing modules and assigning said flow processing modules to threads for execution.

14. The method of claim 13, further comprising the step of:

after a client is admitted to join a channel, a resource scheduler selecting a thread for execution from amongst a queue of said threads according to a scheduling policy.

15. The method of claim 10, further comprising the steps of:

a reserver passing to said bridge a create group request specifying a future start time and future requirements of said group;

translating said request to resource estimates;

checking to determine any overlap with current resource allocations;

sending a reply to said reserver indicating whether the necessary resources will be available.

16. The method of claim 10, wherein the step of granting or denying admission further includes the step of determining whether client specified resource limits would be exceeded.

17. The method of claim 8, wherein said computer system is a terminal.

18. A Method for implementing a bridge degradation policy, comprising the steps of:

a client passing service degradation policy information to a bridge, where said degradation policy information relates to a prioritization amongst clients, channels, and groups;

said bridge storing data corresponding to said degradation policy information in a client, channel or group data structure; and

said bridge implementing said degradation policy should a bridge resource overload occur;

wherein bridge resources are allocated to execute flow processing modules which perform audio and/or video combination, synchronization or transformation as part of channel processing; and

wherein said bridge resource overload occurs when there are insufficient resources to satisfy flow processing module requirements.

19. The method of claim 18, wherein said degradation policy specifies that a video channel should be degraded in preference to an audio channel.

20. The method of claim 18, wherein said degradation policy utilizes resource price related information.