Back to results
US 8,693,666 B2Granted
Intelligent call platform for an intelligent distributed network
AssigneeMCI Communications Corporation
InventorsRobert Barnhouse, Doug Cardy, Kelvin Porter, Ken Rambo, Carol Waller, Wendy Wong, George Yao
Life of this patent
Estimating the term…
Abstract
A network management system communicates with a plurality of intelligent distributed network nodes. The network management system dynamically distributes managed objects across the plurality of intelligent distributed network nodes. Examples of managed objects distributed by the network management system include a service control managed object, a call control managed object, a bearer control managed object, and a resource proxy managed object.
Claims20
A method comprising:
- creating, by a computing system, call control software based on a bearer capability class that includes information for managing a bearer resource,
- the information for managing the bearer resource including information associated with:
- changing a quality of service associated with a call,
- changing a bit rate associated with the call, and
- supporting one or more channels associated with the call;
- and
- deploying, by the computing system, the call control software to a call processing node over a data communications network,
- the call processing node using the call control software to manage the bearer resource to serve as part of a transmission path for the call that is received by a communication system.
5 more elements
A method comprising:
- creating, by one or more devices and based on a bearer capability class that includes information for controlling a bearer resource, a call control software object,
- the information for controlling the bearer resource including information associated with:
- changing a quality of service associated with a call,
- changing a bit rate associated with the call, and
- supporting one or more channels associated with the call;
- and
- deploying, by one or more devices and via a data communications network, the call control software object to a service logic execution environment controlling at least a portion of a communications system,
- the call control software object being instantiated in the service logic execution environment for the service logic execution environment to control the bearer resource, that is to serve as part of a transmission path for the call that is being handled by the communications system, by using the call control software object.
5 more elements
A method comprising:
- updating or adding, by a call processing node controlling at least a portion of the communications system, a first service that is associated with a first call processing action without updating a second service to account for a conflict between the first call processing action and a second call processing action that is associated with the second service;
- identifying, by the call processing node and after updating or adding the first service, the conflict between the first call processing action and the second call processing action during processing of a call;
- invoking, by the call processing node, service arbitration software after identifying the conflict;
- determining, by the call processing node and by using the service arbitration software, a particular action to be taken to resolve the conflict;
- and
- processing, by the call processing node, the call by performing the particular action.
3 more elements
A method comprising:
- storing, by a node controlling at least a portion of a communications system, service discrimination information associated with processing calls,
- the service discrimination information identifying one or more services to be invoked based on subscriber specific information;
- and
- invoking, by the node and when processing a call for a first subscriber, the one or more services based on the service discrimination information, a first activation input provided by the first subscriber, and a context or a progress of the call,
- the first activation input being different from a second activation input provided by a second subscriber to invoke the one or more services, and
- the subscriber specific information including information identifying the first subscriber, the first activation input, the second subscriber, and the second activation input.
3 more elements
Dependencies are inferred from the claim text.