Real-time object-oriented database for TAPI service providers

• US 6,804,339 B1
• Filed: 01/19/2000
• Issued: 10/12/2004
• Est. Priority Date: 01/19/2000
• Status: Expired due to Term

• Current Assignee: Unify Inc. (Atos SE)
• Original Assignee: Siemens Information And Communication Networks, Inc.
• Inventors: Hettish, Mark B.
• Primary Examiner(s): Deane, Jr., William J.
• Application Number:
  US09/487,553
• Time in Patent Office: 1,728 Days
• Field of Search: 379/201.01, 379/201.03, 379/211.02, 379/219, 379/229, 379/230, 379/242
• US Class Current: 379/201.01
• CPC Class Codes: H04M 1/2473 Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) details of API H04M7/0021
• CPC Class Codes: H04M 3/42 Systems providing special services or facilities to subscribers specially adapted for wireless communication networks H04W4/00
• CPC Class Codes: H04M 3/42323 PBX's with CTI arrangements
• CPC Class Codes: H04M 7/0021 Details of Application Programming Interfaces
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A TAPI database system and method according to the present invention. According to one implementation, an object-oriented TAPI database (200) is provided which supports code re-use when using in other TAPI service providers. The database (200) models all the major objects in TAPI telephony—static line, static phone, static addresses, open lines, open phones, open addresses, calls and request Ids.

Claims

1. A TAPI system, comprising:

a TAPI application program;

a TAPI service provider; and

a telephony database for managing a plurality of manager objects and

a plurality of managed objects, the managed objects including telephony objects defining a class hierarchy.

2. A TAPI system according to claim 1, said plurality of manager objects maintaining a free list and an in use list.

3. A TAPI system comprising:

a database system including a plurality of manager objects; and

a plurality of objects being managed by said manager objects;

said database useable by a TAPI service provider for managing said objects.

4. A TAPI system according to claim 3, said manager objects including at least one phone device manager object, line device manager object, open phone manager object, open line manager object, request ID manager object, open line manager object, or call manager object.

5. A TAPI system according to claim 4, said objects including at least one static phone device object, static line device object, open phone object, open line object, request ID object or call object.

6. A TAPI service provider, comprising:

a telephony database, said telephony database configured to model a plurality of manager objects and manage a plurality of telephony-related objects for use by said TAPI service provide.

7. A TAPI service provider according to claim 6, said manager objects including at least one phone device manager object, line device manager object, open phone manager object, open line manager object, request ID manager object, open line manager object, or call manager object.

8. A TAPI service provider according to claim 7, said telephony-related objects including at least one static phone device object, static line device object, open phone object, open line object, request ID object or call object.

9. A TAPI system, comprising:

a TAPI application program;

a TAPI service provider; and

a telephony database for use by said TAPI service provider, said telephony database including

one or more database applications programming interfaces;

a TAPI builder,

at least one request mapper;

at least one response mapper; and

at least one event mapper.

10. A TAPI system as recited in claim 9, wherein said at least one request mapper, at least one response mapper, and at least one event mapper are adapted to perform one or more actions on said mapper database, including creation/deletion and opening/closing of TAPI telephony objects.