The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jun. 01, 2010
Filed:
May. 21, 2002
Abdullah Murat Bog, Milpitas, CA (US);
Steven Turner, Overland Park, KS (US);
Matthew Kung-wei Jonathan Barrow, Kansas City, MO (US);
Tracey Mark Bernath, Leawood, KS (US);
Abdullah Murat Bog, Milpitas, CA (US);
Steven Turner, Overland Park, KS (US);
Matthew Kung-Wei Jonathan Barrow, Kansas City, MO (US);
Tracey Mark Bernath, Leawood, KS (US);
Sprint Communications Company L.P., Overland Park, KS (US);
Abstract
The invention is a provider agent product and method that operates as a software interface between a telephony card and a session manager in an advanced communications network. The provider agent receives event messages from the telephony card indicating on-hook events, off-hook events, and digit events. The provider agent instructs the telephony card to provide dial tone, ring current, ringback, and busy signals to the telephones. The provider agent also exchanges messages with a session manager in the network. These messages include: invite messages, reply messages, join messages, and terminate messages. In response to the above processing, the provider agent instructs the telephony card to interwork telephony signals on a telephony channel with ATM signals on an ATM virtual channel. The provider agent is comprised of a plurality of software objects that are stored on a software storage medium and that include: a controller object, port objects, and event objects. The provider agent objects are executed by a multithreaded processing system and each object has a separate processing thread. The provider agent and the telephony card communicate through an application programming interface that is specified in an Interface Definition Language (IDL) of a Common Object Request Broker Architecture (CORBA).