IP Library Granted Patent US 8,693,666
Granted Patent B2
US 8,693,666 · App. 13/160,169 · Granted Apr 8, 2014

Intelligent call platform for an intelligent distributed network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,693,666
App. No.
13/160,169
Granted
Apr 8, 2014
Kind
B2
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.

Claims (65)

1. 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.

2. The method of claim 1 , where the call control software implements a call state associated with the call.

3. The method of claim 1 , where the call control software implements a call model associated with a plurality of possible call states.

4. The method of claim 1 , where the call control software implements a telephony finite-state machine call model.

5. The method of claim 1 , where the bearer resource is not part of the call processing node.

6. The method of claim 1 , where deploying the call control software comprises:

determining a completion of creating the call control software, and

providing, after determining the completion of creating the call control software, the call control software to the call processing node.

7. The method of claim 1 , further comprising:

causing the call control software to be executed in a virtual machine operating in the call processing node.

8. The method of claim 1 , where the call control software comprises program instructions to be executed in a service logic execution environment associated with the call processing node.

9. The method of claim 1 , where the call control software comprises byte codes that are operational in heterogeneous data processing environments.

10. The method of claim 1 , where deploying the call control software comprises:

storing the call control software in a managed object repository; and

deploying the call control software to the call processing node from the managed object repository.

11. The method of claim 1 , where the call involves communications via a packet network.

12. The method of claim 1 , where the call processing node manages the bearer resource, using the call control software, by at least one of:

changing the bit rate associated with the call,

changing the quality of service associated with the call, or

changing a quantity of the one or more channels associated with servicing the call.

13. The method of claim 1 ,

where the computing system is associated with a particular network operator,

where a type of the call processing node is manufactured to be used by the particular network operator and one or more other network operators that use different software to process of other calls, and

where the call is placed by a subscriber associated with the particular network operator.

14. 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.

15. The method of claim 14 ,

where the call control software object is created to process particular calls being handled by a particular network operator,

where the particular calls include the call, and

where the service logic execution environment is used by the particular network operator.

16. 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.

17. The method of claim 16 , further comprising:

receiving the service arbitration software expressing service arbitration logic via a data network.

18. 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.

19. The method of claim 18 , where storing the service discrimination information comprises:

storing a first profile for the first subscriber,

the first profile including information identifying the one or more services,

the first subscriber, and the first activation input, and

storing a second profile for the second subscriber,

the second profile including information identifying the one or more services, the second subscriber, and the second activation input.

20. The method of claim 18 , further comprising:

receiving the service discrimination information via a data network.

Assignments (2)
CORRECTIVE ASSIGNMENT TO REMOVE THE PATENT NUMBER 5,835,907 PREVIOUSLY RECORDED ON REEL 032725 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 24, 2014
From: MCI COMMUNICATIONS CORPORATION
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 033408/0235 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 22, 2014
From: MCI COMMUNICATIONS CORPORATION
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 032725/0001 →