Arrangement for facilitating plug-and-play call features

• US 5,717,747 A
• Filed: 05/31/1996
• Issued: 02/10/1998
• Est. Priority Date: 05/31/1996
• Status: Expired due to Term

• Current Assignee: Avaya Incorporated
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Franklin, Andrew D., Boyle, Frank J. III, Gambill, Jane, Parker, Charles H., Sanger, Dennis R.
• Primary Examiner(s): Hong, Harry S.
• Application Number:
  US08/656,517
• Time in Patent Office: 620 Days
• Field of Search: 379/201, 379/207, 379/242, 379/268, 379/269, 379/280, 379/284
• US Class Current: 379/201.03
• CPC Class Codes: H04L 67/01 Protocols
• 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 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 3/51 Centralised call answering arrangements requiring operator intervention , e.g. call or contact centers for telemarketing
• CPC Class Codes: H04M 3/546 in private branch exchanges
• CPC Class Codes: H04Q 2213/13057 Object-oriented software
• CPC Class Codes: H04Q 3/54525 Features introduction
• CPC Class Codes: H04Q 3/54583 Software development, e.g. procedural, object oriented, software generation, software testing

Abstract

A telecommunications system infrastructure that facilitates easy insertion of feature software into existing such telecommunications systems and easy integration of the new calling features and their implementing software with existing features and their software. The infrastructure comprises the Lucent Technologies MMCX multimedia communications server (100) and middleware-compliant communications endpoints (101-102) executing the Lucent Technologies MMCX communications middleware (111-112). Feature-implementing software has a modular client/server construction, with feature managers (server modules, 300,350) executing on the MMCX server and feature administration agents (client modules, 303-353, 304-354) executing on the endpoints. The infrastructure provides a context service (120) and a context API (121) for registering an instance of a feature manager (a user policy, 301-302, 351-352) for each user upon that user becoming entitled to the feature, an administration API (360) for communications between feature managers and feature administration agents on the user'"'"'s endpoint to customize the user'"'"'s user policies for the user, and a context (a cyberspace meeting room, 200) and the context API for involving the user policies of users who are parties to a call in the call and for communicating call-related events to feature servers and other service-implementing software. Call-related events are passed to user policies involved in the call, and they are given a chance to react to the events by allowing or rejecting the events. Interactions between features are managed by having feature managers register at different priorities with the context service; higher-priority modules are serially given an opportunity to allow or reject events before lower-priority modules.

Claims

1. A call-control apparatus wherein each call feature is implemented as a server program and a cooperating client program, comprising:

means for executing the client and the server programs;

means for registering for a user an instance of a server program that implements any call feature, in a same manner as any other instances of any server programs that implement any call features, substantially at any time during operation of the call-control apparatus to provide the call feature for the user;

an administration interface for communicating information, between the server program and a cooperating said client program used by the user, in a same manner as between any other client programs and any server programs that implement any call features, to customize the instance of the server program for the user; and

means for involving the instance of the server program in a call to which the user is a party, in a same manner as any other instance of any server programs that implement any call features, to provide the feature to the call.

2. The apparatus of claim 1 wherein:

each instance of each server program has a priority associated therewith; and

the means for involving comprise

means responsive to occurrence of an event in the call, for giving instances of server programs that are involved in the call each a chance to respond to the event in an order of their associated priorities, to control interaction between the features implemented by the instances of the server programs that are involved in the call.

3. The apparatus of claim 1 wherein

the means for involving comprise:

a second interface for communicating events between a plurality of server programs that are involved in the call, in a same manner as between server programs that are involved in any other calls;

means cooperative with the second interface, responsive to receipt through the second interface of a proposal of an event from a first server program that is involved in the call, for sending a request for approval of the event through the second interface to the first server program and to a second server program that is also involved in the call;

means cooperative with the second interface and responsive to receipt through the second interface of approval of the event from both the first and the second server program, for sending the approval of the event through the second interface both to the first server program and to the second server program to cause the event to be effected, and responsive to receipt through the second interface of rejection of the event from either the first or the second server program, for forbearing from sending the approval of the event both to the first server program and to the second server program to prevent the event from being effected.

4. The apparatus of claim 3 wherein:

each server program has a priority associated therewith, and

the means for sending a request for approval are responsive to the receipt of the event, for sending the request for approval to the first and the second server programs serially in an order of the priorities of the first and the second server programs, to control interaction between the features implemented by the first and the second server programs.

5. The apparatus of claim 4 further comprising:

means for administratively changing the priorities that are associated with server programs, to change the interaction between the features implemented by the server programs.

6. The apparatus of claim 1 wherein:

the administration interface communicates information between the server program and the cooperating client program used by the user to customize a registered said instance of the server program for the user; and

the involving means involve a customized registered said instance of the server program in the call to which the user is a party.

7. The apparatus of claim 1 wherein:

each feature'"'"'s server program comprises a plurality of instances of the server program, one for each user who is entitled to the feature.

8. The apparatus of claim 1 wherein:

the executing means comprise

means for executing the server programs, and

at least one means for executing the client programs;

the server programs, the means for executing the server programs, the registering means, and the involving means are included in a call controller;

an instance of the client program of each of at least some of the features and one of said means for executing the client programs are included in each of at least one call endpoint; and

the administration interface interfaces the at least one call endpoint with the call controller to communicate information between server programs on the call controller and the instances of the client programs on the at least one endpoint.

9. A method of controlling calls in an apparatus wherein each call feature is implemented as a server program and a cooperating client program and which executes the client and the server programs, comprising the steps of:

in response to a user becoming entitled to a call feature, registering for the user an instance of the server program that implements the call feature, in a same manner as any other instance of any server programs that implement any call features, substantially at any time during operation of the apparatus, to provide the call feature for the user;

in response to the user using the client program, communicating information between the server program and the client program through an administration interface, in a same manner as information is communicated through the administration interface between any other client programs and any server programs that implement any call feature, to customize the instance of the server program for the user; and

in response to the user becoming a party to a call, involving the instance of the server program in the call, in a same manner as any other instance of any server programs that implement any call features, to provide the feature to the call.

10. The method of claim 9 wherein:

each instance of each server program has a priority associated therewith; and

the step of involving comprises the step of

in response to occurrence of an event in the call, giving instances of server programs that are involved in the call each a chance to respond to the event in an order of their associated priorities, to control interaction between the features implemented by the instances of the server programs that are involved in the call.