Abstract interface for media and telephony services

• US 6,445,776 B1
• Filed: 12/31/1998
• Issued: 09/03/2002
• Est. Priority Date: 12/31/1998
• Status: Expired due to Term

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Villarica, R. Alberto, Shank, Charles Kevin
• Primary Examiner(s): Hoosain, Allan
• Application Number:
  US09/223,842
• Time in Patent Office: 1,342 Days
• Field of Search: 379/67.1, 379/70, 379/76, 379/84, 379/88.01, 379/88.04, 379/88.07, 379/88.13, 379/88.14, 379/88.17, 379/88.22, 379/88.28, 379/100.15, 379/88.1, 379/112, 379/154, 379/201, 379/207, 379/210, 379/219, 379/220, 379/229, 379/242, 379/243, 379/265.09, 379/207.11, 379/88.02, 379/88.16, 379/908, 379/201.01
• US Class Current: 379/88.1
• CPC Class Codes: H04M 1/64 Automatic arrangements for answering calls; Automatic arrangements for recording messages for absent subscribers; Arrangements for recording conversations centralised dictation systems H04M11/10
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/42161 via computer interface
• CPC Class Codes: Y10S 379/908 Multimedia

Abstract

A server provides media and telephony services in a telecommunications network. The server has a distributed, object-oriented software architecture, allowing client applications to access resources located anywhere in the network. The server provides interfaces to media and telephony resources so that client applications, which may access the server through an IP data network, can access the resources. The software architecture framework is provided by Common Object Request Broker Architecture (CORBA). The interfaces provided by the server are Interface Definition Language (IDL) application program interfaces (APIs) implemented using a distributed object model such as CORBA.

Claims

1. A method for providing access from a client to multiple resources, coupled to a server, comprising:

transmitting from the client to the server an object-oriented, language-independent request to establish a session between the client and the server;

transmitting from the client to the server object-oriented, language-independent requests to establish multiple groups containing the resources, the groups corresponding to the session; and

transmitting from the client to the server, an object-oriented, language-independent request to invoke at least a function on the resources.

2. The method of claim 1 wherein transmitting a request to establish a session includes

setting a parameter corresponding to the session for determining event callback behavior.

3. The method of claim 1 wherein transmitting a request to establish a session includes

setting a parameter corresponding to the session for determining whether an event will be created.

4. The method of claim 1 wherein transmitting a request to establish a session includes

setting a parameter corresponding to the session for determining whether an event will be placed on an event queue.

5. The method of claim 1 wherein transmitting a request to establish a session includes

setting a parameter corresponding to the session indicating whether an event key should be reported to the client.

6. The method of claim 1, wherein a second resource is coupled to the server, the method further comprising

transmitting from the client to the server an object-oriented, language-independent request to establish a second group containing the second resource, the second group corresponding to the session;

and

transmitting from the client to the server an object-oriented, language-independent request to establish a connection between the first group and the second group.

7. The method of claim 1 wherein the resource is an announcement player and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a play function on the announcement player.

8. The method of claim 1 wherein the resource is a speech recognition device and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a start function on the speech recognition device.

9. The method of claim 1 wherein the resource is a speech recognition device and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a retrieve function on the speech recognition device.

10. The method of claim 1 wherein the resource is a signal generator and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a send function on the signal generator.

11. The method of claim 1 wherein the resource is a signal detector and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a retrieve function on the signal detector.

12. The method of claim 1 wherein the resource is a text-to-speech converter and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a convert function on the text-to-speech converter.

13. The method of claim 1 wherein the resource is a system call router and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke an answer function on the system call router.

14. The method of claim 1 wherein the resource is a system call router and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a function on the system call router to make a call.

15. The method of claim 1 wherein the resource is a system call router and wherein transmitting an object-oriented, language-independent request to invoke a function on the resource includes transmitting a request to invoke a function on the system call router to drop a call.

16. A client comprising:

means for transmitting to a server an object-oriented, language-independent request to establish a session between the client and the server;

means for transmitting to the server object-oriented, language-independent requests to establish multiple groups containing resources, coupled to the server, each group corresponding to the session; and

means for transmitting to the server object-oriented, language-independent requests to invoke at least a function on the resources.

17. The client of claim 16 wherein the means for transmitting a request to establish a session includes

means for setting a parameter corresponding to the session for determining event callback behavior.

18. The client of claim 16 wherein the means for transmitting a request to establish a session includes

means for setting a parameter corresponding to the session for determining whether an event will be created.

19. The client of claim 16 wherein the means for transmitting a request to establish a session includes

means for setting a parameter corresponding to the session for determining whether an event will be placed on an event queue.

20. The client of claim 16 wherein means for transmitting a request to establish a session includes

means for setting a parameter corresponding to the session indicating whether an event key should be reported to the client.

21. The client of claim 16 further comprising

means for transmitting to the server an object-oriented, language-independent request to establish a second group containing a second resource, coupled to the server, the second group corresponding to the session;

and

means for transmitting to the server an object-oriented, language-independent request to establish a connection between the first group and the second group.

22. The client of claim 16 wherein the resource is an announcement player and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a play function on the announcement player.

23. The client of claim 16 wherein the resource is a speech recognition device and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a start function on the speech recognition device.

24. The client of claim 16 wherein the resource is a speech recognition device and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a retrieve function on the speech recognition device.

25. The client of claim 16 wherein the resource is a signal generator and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a send function on the signal generator.

26. The client of claim 16 wherein the resource is a signal detector and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a retrieve function on the signal detector.

27. The client of claim 16 wherein the resource is a text-to-speech converter and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a convert function on the text-to-speech converter.

28. The client of claim 16 wherein the resource is a system call router and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke an answer function on the system call router.

29. The client of claim 16 wherein the resource is a system call router and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a function on the system call router to make a call.

30. The client of claim 16 wherein the resource is a system call router and wherein the means for transmitting an object-oriented, language-independent request to invoke a function on the resource includes means for transmitting a request to invoke a function on the system call router to drop a call.