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:
May. 20, 2003
Filed:
Jun. 05, 1998
Murali Aravamudan, Freehold, NJ (US);
Prakash Iyer, Freehold, NJ (US);
Lucent Technologies Inc., Murray Hill, NJ (US);
Abstract
Telephone service is supplied using a distributed architecture that employs a collection of resources each of which exposes a hierarchical namespace. The architecture includes two fundamental resource types, the device server and the call coordinator, which are interconnected by a network employing a common protocol, e.g., TCP/IP. The interaction between the various resources follows “client-server” principles to implement end-to-end communication. Device servers represent physical/logical telephone devices, which include a) end-point device servers and b) gateway device servers. End-point device servers 1) represent controls for communication, such as keypads, indicator lamps, and displays, and 2) perform media rendering, e.g., voice digitization, transport, and reconstruction. Gateway device servers have two “sides”. One side is implemented to appear to a call coordinator as if it were a device server, and the other side has an interface adapted to interwork with a preexisting island of telephone service. In the term “device server”, “server” is used in the conventional manner of the “client-server” architecture, where the server serves request from the clients and does not take action unless it is in response to a client request. A call coordinator functions in the role of the “client”. The device servers are unaware of communication state, which is maintained by the call coordinator and exposed as a hierarchical namespace. The call coordinator treats the processing of a call as a sequence of steps each of which can be implemented by a small piece of computer executable code called a “feature applet”.