US 7,948,968 B2Grant

Network session management

Issue Date:2011-05-24

•17 Claims

•14 Drawing Sheets

Abstract

A communication system providing telephony communication across combined circuit switched and packet switched networks, such as a telephone network and the Internet, which are connectable to terminals, such as telephones and computers, for selective communication therebetween. The communication system includes an authorization and account control object in the packet switched network, multiple gateways between the circuit switched and packet switched networks providing controlled connectivity between those networks, and an information retrieval object in the packet switched network, wherein the authorization and account control object maintains a substantially real time record of user accounts and usage, and the information and retrieval object provides substantially real time retrieval of selected information from the authorization and account control object. The retrieval object provides on demand to terminals which provide authentication for access to an identified account information regarding that account. The information regarding the account is substantially real time information including information with respect to communications in progress, which are chargeable to the account which has been authenticated. The authorization and account control object is preferably a unitary logical object having distributed instances thereof handling multitudinous accounts of widely separated terminals. The retrieval object provides isolation of the authorization and account control object permitting simultaneous multitasking by the authorization and account control object and the retrieval object respectively.

Metadata

Assignees

Verizon Communications Inc.
Verizon Services Corp.

Inventors

Eric A. Voit
Edward E. Balkovich
William D. Goodman
Jayant G. Gadre
Patrick E. White
David E. Young

Application Information

Application Number:US 10/979,317

Filing Date:2004-11-02

Priority Date:1997-09-16

Art Unit:2614

Classifications

IPC:

H04M15/00H04L12/66H04L1/00

Patent Drawings (14 sheets)

Description

Cross-Reference to Related Applications

[0001] This is a continuation of prior U.S. patent application Ser. No. 08/931,480. filed Sep. 16, 1997, titled “NETWORK SESSION MANAGEMENT,” now U.S. Pat. No. 6,839,340, which is related to U.S. patent application Ser. No. 08/931,159, filed Sep. 16, 1997, titled “NETWORK SESSION MANAGEMENT,” now U.S. Pat. No. 6,137,869, which is incorporated herein by reference in its entirety.

Field of Invention

[0002] This invention relates to methods and systems for managing signaling and communication sessions across networks, and particularly relates to a scalable methodology and system for managing telephony over hybrid networks such as combined switched telephone networks and packet switched internetworks, such as the Internet.

Background of the Invention

[0003] Attention recently has been directed to implementing a variety of communication services, including voice telephone service, over the worldwide packet data network now commonly known as the Internet. The Internet had its genesis in U.S. Government programs funded by the Advanced Research Projects Agency (ARPA) That research made possible national internetworked data communication systems. This work resulted in the development of network standards as well as a set of conventions, known as protocols, for interconnecting data networks and routing information across the networks. These protocols are commonly referred to as TCP/IP. The TCP/IP protocols were originally developed for use only through ARPANET but have subsequently become widely used in the industry. TCP/IP is flexible and robust. TCP takes care of the integrity, and IP moves the data.

[0004] Internet provides two broad types of services: connectionless packet delivery service and reliable stream transport service. The Internet basically comprises several large computer networks joined together over high-speed data links ranging from ISDN to T1, T3, FDDI, SONET, SMDS, ATM, OT1, etc. The most prominent of these national nets are MILNET (Military Network), NSFNET (National Science Foundation NETwork), and CREN (Corporation for Research and Educational Networking). In 1995, the Government Accounting Office (GAO) reported that the Internet linked 59,000 networks, 2.2 million computers and 15 million users in 92 countries. However, since then it is estimated that the number of Internet users continues to double approximately annually.

[0005] In simplified fashion the Internet may be viewed as a series of packet data switches or ‘routers’ connected together with computers connected to the routers. The Information Providers (IPs) constitute the end systems which collect and market the information through their own servers. Access providers are companies such as UUNET, PSI, MCI and SPRINT which transport the information. Such companies market the usage of their networks.

[0006] FIG. 3 shows a simplified diagram of the Internet and various types of systems which are typically connected. Generally speaking the Internet consists of Autonomous Systems (AS) type packet data networks which may be owned and operated by Internet Service Providers (ISPs) such as PSI, UUNET, MCI, SPRINT, etc. Three such AS/ISPs appear in FIG. 3 at 310, 312 and 314. The Autonomous Systems (ASs) are linked by Inter-AS Connections 311, 313 and 315. Information Providers (IPs) 316 and 318, such as America Online (AOL) and CompuServe, connect to the Internet via high speed lines 320 and 322, such as T1/T3 and the like. Information Providers generally do not have their own Internet based Autonomous Systems but have or use Dial-Up Networks such as SprintNet (X.25), DATAPAC and TYMNET.

[0007] By way of current illustration, MCI is both an ISP and an IP, SPRINT is an ISP, and the Microsoft Network (MSN) is an IP using UUNET as an ISP. Other information providers, such as universities, are indicated in exemplary fashion at 324 and are connected to the AS/ISPs via the same type connections here illustrated as T1 lines 326. Corporate Local Area Networks (LANs), such as those illustrated in 328 and 330, are connected through routers 332 and 334 and high speed data links such as T1 lines 336 and 338. Laptop computers 340 and 342 are representative of computers connected to the Internet via the public switched telephone network (PSTN), and are shown connected to the AS/ISPs via dial up links 344 and 346.

[0008] In the addressing scheme of the Internet, an address comprises four numbers separated by dots. This is called the Internet Protocol address, or IP address. An example of an IP address would be 164.109.211.237. Each machine on the Internet has a unique number assigned to it which constitutes one of these four numbers. In the IP address, the leftmost number has the greatest weight. By analogy this would correspond to the ZIP code in a mailing address. At times the first two numbers constitute this portion of the address indicating a network or a locale. That network is connected to the last router in the transport path. In differentiating between two computers in the same destination network only the last number field changes. In such an example the next number field 211 identifies the destination router.

[0009] When a packet bearing a destination address leaves the source router, the router examines the first two numbers in a matrix table to determine how many hops are the minimum to get to the destination. It then sends the packet to the next router as determined from that table, and the procedure is repeated. Each router has a database table that finds the information automatically. This continues until the packet arrives at the destination computer. The separate packets that constitute a message may not travel the same path depending on traffic load. However, they all reach the same destination and are assembled in their original order in a connectionless fashion. This is in contrast to connection oriented routing modes, such as frame relay and ATM or voice.

[0010] It would be difficult for most people to remember the four separate numbers (sometimes having ten or more digits) comprising each numeric IP address. In addition numeric IP addresses occasionally change, making it even more of a problem for people to keep track of them. The Domain Name System (DNS) was developed to provide some relief from these problems. In the DNS system words, which are more easily remembered, are used instead of numbers.

[0011] An example of a textual Domain Name is [email protected]. Each of the names separated by a dot is called a domain. The significance of each of the domains is the reverse of that of the numeric IP address. In the numeric IP address, the most significant numbers were on the left and the least significant on the right. The textual Domain Name System begins with the least significant on the left and proceeds to the most significant on the right.

[0012] The top-level domains, those of the most general significance, are as follows:

[0013] 1. COM A commercial operation

[0014] 2. EDU A university, college or other educational institution

[0015] 3. GOV A government organization

[0016] 4. MIL A military site

[0017] 5. ORG Any organization that does not fit into any of the preceding

[0018] 6. NET A network

[0019] There are now two-letter domains, each denoting a different country, which are atop the above original. domain names. An address ending in “COM.AU,” for example, would be a commercial operation in Australia. Over a hundred different countries are now connected to the Internet so the list of two-letter country codes is ever increasing. Computers associated with the Internet called domain name servers convert textual domain names into numeric IP addresses.

[0020] Recently, one or more companies have developed software for use on personal computers to permit two-way transfer of real-time voice information via an Internet data link between two personal computers. In one of the directions, the sending computer converts voice signals from analog to digital format. The software facilitates data compression down to a rate compatible with modem communication via a POTS telephone line, in some cases as low as 2.4 kbits/s. The software also facilitates encapsulation of the digitized and compressed voice data into the TCP/IP protocol, with appropriate addressing to permit communication via the Internet. At the receiving end, the computer and software reverse the process to recover the analog voice information for presentation to the other party. Such programs permit telephone-like communication between Internet users registered with Internet Phone Servers.

[0021] Such programs have relied on servers coupled to the Internet to establish voice communication links through the networks. Each person active on the network, who is willing to accept a voice call, must register with a server. A calling party can call only those persons registered on the voice communication server. Also, the address management provided by these servers, like that provided by the domain name servers, has not permitted any individualized control of routing. For example, a user could register only one current address and must reregister each time the user comes on-line with a new address. The registration server provides no automatic selection of alternate destinations.

[0022] Concurrent with recent developments in public packet data communications such as the Internet, outlined above, the telephone industry has been developing an enhanced telephone network, sometimes referred to as an Advanced Intelligent Network (AIN), for providing a wide array of new voice grade telephone service features. In an AIN type system, local and/or toll offices of the public telephone network detect one of a number of call processing events identified as AIN “triggers”. For ordinary telephone service calls, there would be no event to trigger AIN processing. The local and toll office switches would function normally and process such calls without referring to the central database for instructions. An office which detects a trigger will suspend call processing, compile a call data message and forward that message via a common channel interoffice signaling (CCIS) link to a database system, such as an Integrated Service Control Point (ISCP). Each ISCP includes a Multi-Services Application Platform (MSAP) database.

[0023] If needed, an ISCP can instruct the central office to obtain and forward additional information. Once sufficient information about the call has reached the ISCP, the ISCP accesses its stored data tables in the MSAP database. Using those tables it translates the received message data into a call control message and returns the call control message to the switching office of the network via CCIS link. The network switching offices then use the call control message to complete the particular call. An AIN type network for providing an Area Wide Centrex service, for example, was disclosed and described in detail in commonly assigned U.S. Pat. No. 5,247,571 to Kay et al., the disclosure of which is entirely incorporated herein by reference.

[0024] As shown by the art discussed above, the Internet and the AIN have remained separate, independent areas of technical development. Many telephone service subscribers are accustomed to enhanced telephone features, such as those provided by AIN processing. However, the wide range of conditional routing options offered by AIN type processing have not been available on the Internet. For example, the address processing provided by the domain name servers and the registration servers used to exchange addresses for voice communication have not permitted alternate treatments for different times, different calling parties, different destinations of roaming subscribers, etc. An enhanced domain name server which enables conditional routing and which is capable of wide database applications was disclosed and described in detail in the above-referenced parent Eric A. Voit U.S. application Ser. No. 08/812,075.

[0025] As use of the Internet expands, particularly for transport of voice telephone communications, a need exists not only for enhanced address management but also for distributed and scalable customer account authentication, authorization, usage recording, usage pricing billing account management, and inter carrier interfaces. The enhanced domain server described in the above incorporated Voit application Ser. No. 08/812,075 lends itself to serving in this capacity.

[0026] Voice over internetworks, and particularly the Internet (V/IP), involves terminal equipment affiliated with various networks. V/IP services can be divided into at least four categories based on the type of network to which the users' terminal equipment is attached, such as Internet/Intranet or narrowband Public Switched Telephone Network (PSTN) or POTS (plain old telephone service) telephone network. These four categories are:

- [0027] 1. Personal Computer (PC)—PC
- [0028] 2. PC—Telephone
- [0029] 3. Telephone—PC
- [0030] 4. Telephone Telephone

[0031] Existing V/IP implementations over the Internet are subject to best-effort quality of service (QoS). Typically, this is noticeably degraded as compared to “toll quality” service. In addition, it is subject to significant variations. There is a need for improvement over these existing implementations both in level and consistency of QoS. The QoS should be such as to be perceived by end users as consistently supporting comfortable conversation similar to that which users are accustomed. Preferably the QoS should be equivalent to “toll quality” voice service.

[0032] Residential and business customers on the PSTN are accustomed to the availability of enhanced calling features and it is desirable to provide personal dialing directories, ability to use multiple point to point connections at the same time, multi-line conferencing capabilities, and full duplex operation. Authorization and security features should be supplied, as well as user access to billing and usage accounting relating to their own accounts.

Disclosure of the Invention

[0033] It is a primary objective of the present invention to satisfy the needs which have been described.

[0034] The present invention addresses those needs by providing a robust and scalable customer account management database within the packet switched network. This database may act as manager of all transactions for a particular customer account. Each Internet telephone service subscriber will have at least one billing and authorization account maintained in a database on the Internet. During set-up of a call, the hop-off gateway will obtain identification and password information from the caller. The gateway then communicates with the database to determine if the call is authorized and to negotiate the overall billing algorithm. When the call is finished, the gateway will report usage data to the database for billing purposes.

[0035] Another objective is to provide an overall internetwork architecture that will permit the development of Internet Telephony Gateways (ITGs) capable of dealing with existing problems on a scalable basis. For example, in view of the fact that there is no “originating switch” to generate billing records for an internetwork caller, there is no present system for providing a generation site which will implement a unitary presentation of customer account usage, and also support extraction of data from the network on a real time basis. There is no present architecture or methodology to provide for customer access to his/her account or accounts records without intermixing requests for account information with requests for implementing services. Such an intermixing would subject the fulfillment of services to the traffic load of information requests and vice versa. There is no present architecture for ensuring customer authentication and billing beyond a limited number of customers.

[0036] It is another objective of the invention to implement a system to inform a customer of the pricing rules for a call prior to call connection and to report the price of the call in real time visually or orally.

[0037] It is another objective of the invention to provide customers with ready access to information in their account records without allowing the customer to access the account database which is used in implementing services, or updating or maintaining or storing such databases.

[0038] It is yet another objective of the invention to provide a system to implement the handling of multiple, concurrent calls terminating at different ITGs using the same billing account number and preventing overrun of a preset account spending limit.

[0039] It is another object of the invention to provide an architecture which will provide downloading of billing data to external service providers in isolation from the account information maintained and utilized in implementing Internet voice telephony.

[0040] It is a still further objective of the invention to ensure that such a system will operate properly in situations where the ITG is owned by a different company than the owner of the customer account.

[0041] It is another objective of the invention to provide a mechanism for reducing the potential for fraud.

[0042] According to the invention usage recording, pricing, and authorization are bundled into one logical object. This eliminates the separation between authorization and billing processes and significantly reduces the potential for fraud in a regionally deployed system. By having a single logical database which is managing customer authentication, authorization, and usage pricing for the overall network, a transaction-based approach to updating data is possible. This minimizes opportunities for fraud based on exploitation of temporary inconsistencies of partitioned or replicated data bases. There is no requirement that this logical object be implemented as a single physical system.

[0043] The single logical element or object is invoked during a call when an authorization request is received. This request may consist of an account number and password provided by a PC user to be authenticated. At this point the logical database processor checks the account password and available account balance. If the password is correct and the remaining balance in the account permits the call to be established, the object responds affirmatively to the Internet Telephony Network (ITN) Call Control Object which includes the Internet Telephony Gateway (ITG). The database retains data indicating that a call associated with that account is in progress. In such an architecture mutual authentication by the Call Control Object and ITG and the database is preferable, as is a secure (such as by encryption) call transaction between them.

[0044] In providing the authorization, the database object will evaluate the customer account status to determine if there are multiple connections currently in service, possibly across multiple ITGs. With this state information, the authorization function of the system may ensure that only one call per account is being handled by the network, and/or ensure that the maximum billing limit is not being circumvented by multiple concurrent sessions. In the absence of such a precaution, a second PC caller using the same account and password might receive authorization for a call prior to the posting of the first caller's usage record. Optionally, in order to handle low billing amount availability without denying a call completely, the database object may respond to the ITN with a maximum allowable call duration.

[0045] Another feature is that the database object may reserve a predetermined remaining balance on the account for the call so that additional calls related to that account will not result in exceeding the account's limit. The database object may return the pricing algorithm for the usage to the Call Control Object and ITG, which will pass it on to the PC user. In this way the PC user knows the initial charge and ongoing per minute rate for the usage. This is particularly important when the Call Control Object and ITG is owned by a different company than the database object. The user desires to know the rates that will be charged prior to completing the call. The PC is such as to be able to receive and utilize the algorithm, and display pricing to the PC user. The PC may also present the total charge being incurred by the user on a real time basis as the call progresses.

[0046] After the completion of the call, the database object is also responsible for accepting usage recording data which has been generated by the Call Control Object and ITG, pricing the usage, and decrementing that priced amount from a customer's available balance. The database object then logs the final call data. Preferably the Call Control Object and ITG also logs and maintains the call detail information. This feature is very useful in the situation where the Call Control Object and ITG and the database objects are owned by different companies. In this case, the database object data can be used by the owner of the database object to manage the customer account. In addition, the Call Control Object and ITG data can be used by the owner of the Call Control Object and ITG to charge the database object for the completion of the call over its facilities. In effect this Call Control Object and ITG data becomes the basis for a usage based settlement interface between carriers.

[0047] Preferably the database object is partitioned and may be distributed. A database object partition may be made by a field identifying the carrier owning the customer account, a sub-field within the customer account number (such as NPA-NXX), the customer's telephone number, the customer's e-mail domain name, the customer's originating IP address, or some other field. Each partitioned database may then be placed on its own physical system. With such a partitioned customer account data architecture, it becomes possible to divide the totality of all managed accounts into implementable sub-groups in a straight forward manner.

[0048] It is an objective of the invention to provide a code based means of querying a distributed database of codes which allows automatic accessing of the pertinent physical instance of the database for approval.

[0049] It is another objective of the invention to provide such a database and functionality on a scalable basis.

[0050] Additional objects, advantages and novel features of the invention will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the invention. The objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

Brief Description of Drawings

[0051] FIG. 1A is a high level (partition 1 level) diagram of a PC to Phone Internet Telephony architecture of one embodiment of the system of the invention.

[0052] FIG. 1B is another simplified high level diagram of the generic system.

[0053] FIG. 2 is a diagram of one embodiment of a preferred architectural implementation showing interfaces between IP network elements.

[0054] FIG. 3 shows a simplified diagram of the Internet and various types of systems typically connected thereto.

[0055] FIG. 4 is an Internet Telephony Network (ITN) block diagram showing the ITN system at a second level of partitioning (partition 2 level).

[0056] FIG. 5 illustrates the V/IP objects and interface relationships between users and the network, including external objects and interfaces.

[0057] FIG. 6 illustrates the V/IP objects and interface relationships which have been defined between internal ITN objects.

[0058] FIG. 7 is a diagram of a typical control plane message flow.

[0059] FIG. 8 is a diagram of another typical control plane message flow.

[0060] FIG. 9 provides a high level diagrammatic illustration of a typical PC which may be utilized by a user in the system of the invention.

[0061] FIG. 10 illustrates a typical client software state machine.

[0062] FIG. 11 shows the PC software interface and the relationship to the ITM interfaces.

[0063] FIG. 12 is a simplified diagram illustrating another aspect of the invention showing an architecture wherein a separate intermediary information server provides substantially real time retrieval of account information across the entire communication system.

Best Mode for Carrying Out the Invention

[0064] Referring to FIG. 1A there is illustrated a high level (partition 1) reference model of the Internet Telephony Network or ITN. The center block 100 is the Internet Telephony Network or ITN, is shown in this illustration as managing a customer call between a PC and a POTS telephone. This ITN is in the Network Provider Domain and is responsible for all functions required of a traditional POTS network, i.e., call set-up, usage accounting, surveillance, etc. The ITN spans both the circuit switched network (such as a Public Switched Telephone Network or PSTN) and the packet switched (Internet Protocol or IP—frame relay, etc.) networks. The PC Internet Telephony User (ITU or computer or PC user) is shown at 102 in the Subscriber Domain and the called POTS Internet Telephony User (ITU or telephone user) is shown at 104 in the Called Party Domain. The interface between the PC user and the ITN is designated I1, while the interface between the POTS user and the PSTN is designated I9. I9 represents a standard analog or digital telephone interface.

[0065] FIG. 1B shows a different high level depiction of the generic system wherein the packet switched and circuit switched networks are separately shown at 106 and 108. In this figure the end-to-end system connects a laptop computer 110 and a telephone 112. These constitute respectively the PC user call control object U1 and the U3 POTS U1 service user, as is presently described in further detail in relation to FIG. 2. The directory services object 114 and authentication and security accounting object 116 are coupled to the packet switched IP routed network 106. These constitute respectively the C1 ITN directory object and the C3 authorization, usage recording and pricing object, as presently described in further detail.

[0066] The Internet Telephony Gateway or ITG 118 connects the packet switched and circuit switched networks. This is sometimes referred to herein as the C2 ITN call control object. The computer may be linked to the packet switched network via any available computer to Internet link. Similarly the connection between the circuit switched network and the telephone may be any of the conventional links including POTS.

[0067] In order to manage a call across the circuit switched and packet switched and packet switched networks, it is necessary to provide an architecture, a set of interfaces, and a call flow. FIG. 2 is a diagram showing the interfaces between IP network elements in one architectural implementation. Referring to that figure there is shown at 202 the PC user System Block in the subscriber domain, which includes the U1 PC User Call Control Object. At 200 there is shown the Network System Block or network provider domain, which includes the PSTN Control Plane and C4 PSTN Call Control Object. At 204 there is shown the POTS User System Block or called party domain, which includes the U3 POTS U1 Service User. Within the Network System Block the ITN Control Plane functions are illustrated at 206. The ITN Control Plane functions are those which establish and tear-down communication paths across the User Plane. Three Control Plane Objects are illustrated, namely:

- [0068] C1: The Internet Telephony Gateway Directory Object
- [0069] C2: The Internet Telephony Call Control Object
- [0070] C3: The Internet Telephony Authorization and Usage Recording Object

[0071] These objects are shown respectively at 208, 210, and 212. Not shown in this figure is the PSTN Call Control Object C4 since neither the PSTN network elements nor the PSTN protocols are modified by the ITN system.

[0072] The C3 object represents the network element required in this architecture to perform customer authentication, call authorization, usage accounting, and usage pricing for a particular PC user's customer account. By bundling usage recording, pricing, and authorization into this one logical object, it is possible to eliminate the conventional separation between authorization and billing processes and significantly reduce the potential for fraud in a regionally deployed system. By having a single logical database which is managing customer authentication, authorization, and usage pricing for the network, a transaction-based approach to updating data is possible. This minimizes opportunities for fraud based on exploitation of the conventional temporary inconsistencies which are encountered with partitioned or replicated data bases. There is no requirement that this unitary logical object be implemented as a single physical system. Although not shown in FIG. 2, C3 can also respond to real time requests from external OSS systems for usage record details and account status information for the customer account.

[0073] The C3 object ensures coordination between User Authorization and Usage Recording for a single PC user's customer account. C3 also responds to external requests for that information.

[0074] According to the invention the C3 object is implemented in a manner such that multiple sites maintain their own database servers and no single site on the Internet is in possession of all of the authentication, authorization, usage pricing, and account data. The overall data constitutes a distributed database which forms a unitary logical object which relies on the database servers at the individual sites. Operation is such that a local C3 database or server receives a request for data. If the local server database cannot locate the requested information it sends a request to a second database server asking it to locate the information and send the results back to the requester. The second database server locates the information and sends a message to the requester. If the second database server cannot locate the information in its database it (or the local server database) sends a similar request to the next database server until the desired information is located. Alternatively, the account number may be coded so as to indicate the proper database instance. Database servers with this capability are described in detail in the common assignee's copending Sistanizadeh application Ser. No. 08/634,544, filed Apr. 18, 1996. That application is incorporated by reference herein in its entirety.

[0075] The C3 object is invoked during a call when an Authorization request is relayed over the interface C3.I4. This interface is responsible for allowing an authorization of ITG usage by a service subscriber, and for maintaining the current state of a subscriber's connections within C3, as well as passing ITG generated usage records from C2 to C3 in real time. Communication through the C3.I4 interface is preferably encrypted and secure. The authorization request relayed over C3.I4 typically consists of an account number and password provided by the PC User to be authenticated by C3. At this point. C3 checks the account password and available account balance. If the password is correct and the account remaining balance permits the call to be established, then C3 responds affirmatively to C2. C3 also retains data indicating that a call associated with that account is in progress. In such an architecture, mutual authentication of C2 and C3, and a secure transaction between them is preferred.

[0076] In providing the authorization, C3 evaluates the customer account status to determine if there are multiple connections currently in service (possibly across multiple ITGs). It should be appreciated that while FIG. 2 shows only a single gateway between a PC user and the ITN (via the PSTN), a plurality of gateways exist serving the various regional areas from which subscribers may request service. With the state information obtained from the C3 status evaluation the authorization system may ensure that only one call per account is being handled by the network, and/or ensure that the maximum billing limit is not being circumvented by multiple concurrent sessions. If this precaution is not provided a second PC caller using the same account and password might receive authorization for a call prior to the posting of the first caller's usage record. Optionally, in order to handle low billing amount availability without denying a call completely, C3 can respond to C2 with a maximum allowable call duration.

[0077] Another feature is that C3 may reserve a certain remaining balance on the account for the call so that additional calls related to that account will not result in exceeding that account's limit. C3 may return the pricing algorithm for the usage to C2 which will pass it on to the PC user. In this way the PC user knows the initial charge and ongoing per minute rate for the requested usage. This is particularly important when C2 is owned by a different company than C3, and the user wants to know the overall rates that will be charged prior to completing the call. The PC is such as to be able to receive and utilize the algorithm, and display pricing to the user. The PC is also able to present the total charge being incurred by the user as time goes on during the call.

[0078] After the completion of the call, the C3 object is also responsible for accepting usage recording data from C2, pricing the usage, and decrementing that priced amount from a customer's available balance. C3 then logs the final call data. Preferably C2 also logs and maintains the call detail information. This feature is very useful in the situation where C2 and the C3 database objects are owned by different companies. In this case, the database object data can be used by its owner to manage the customer account. In addition, the C2 data can be used by the owner of the C2 object to charge the C3 database object for the completion of the call over its facilities. In effect this C2 data becomes the basis for a usage based settlement interface between carriers.

[0079] Preferably the C3 system is partitioned. Such a partition may be made by a field identifying the carrier owning the customer account, a sub-field within the customer account number (such as NPA-NXX), the customer's telephone number, the customer's e-mail domain name, the customer's originating IP address, or some other field. Each partitioned database may then be placed on its own physical system on a geographical or other basis. With such a partitioned customer account data architecture, the domain of all managed accounts may be divided into efficiently implementable sub-groups.

[0080] Referring to FIG. 4 there is provided an illustration of the ITN system at a second level of partitioning. Within this partitioning there are three planes (types of processes which span all the network elements involved with a service), and four types of network functions (domains of individual transport networks (e.g., PSTN or IP) over which communication must cross).

[0081] The three planes are:

[0082] The ITN User Plane Functions: These functions are those which are directly involved with real time communications transport and signal manipulation within a network.

[0083] The ITN Control Plane Functions: These are the functions which establish or set-up and tear-down communication paths across the User Plane.

[0084] The ITN Management Plane and Operations Support Systems Functions (OSS): These are the functions needed to provision and maintain the elements of the User Plane and Control Plane.

[0085] The four network functions are:

[0086] IP Access Network Functions (right br PC User Side): The IP access network is used locally on the PC user side simply to reach the IP network. This access may be direct via a LAN, or over a circuit switched PPP link connected to a Point of Presence (POP).

[0087] IP Network Functions: The IP network is the involved Intranet backbone and associated support systems (such as the DNS), this network provides the IP transport functions.

[0088] V/IP Gateway Functions: These are the network functions (and elements) which are involved primarily with supporting a Voice over IP service.

[0089] PSTN Access Network Functions (POTS User Side) The PSTN access network consists of the traditional PSTN connecting the Internet Telephony Gateway (ITG) to the called telephone user.

[0090] The V/IP Gateway Functions and relationships to the other elements involved with the V/IP service are now described in relation to FIGS. 4 and 5. FIG. 4 illustrates interface references defined between the different User Planes and the different -Network Functions. Although this partitioning has been done at the logical level, it is not necessary that physical systems be partitioned in this manner. As an example, an Internet Telephony Gateway may have functions spanning both the Control Plane (call setup) and User Plane (Vocoding).

[0091] The internal interface references designated within FIG. 4 are:

[0092] 1. The interface between the Control Plane and the Management Plane functions is shown at I5. Management functions such as directory table maintenance, surveillance, and periodic billing exports cross the I5 interface.

[0093] 2. The interface between the User Plane and the Control Plane Functions is shown at I4. Interfaces between various elements of the Control Plane are also designated as I4.

[0094] 3. The interface between the V/IP Gateway and POTS Access Network is shown at I7.

[0095] 4. The interface between the IP Network and the V/IP Gateway functions is shown at I6.

[0096] 5. The interface between the IP Network and the PC Access Network is shown at I3.

[0097] 6. For the sake of simplicity, one additional interface of lower utilization, I10, is not shown in FIG. 4. This interface is an external billing interface to a credit card provider and is shown and detailed in FIG. 5.

[0098] FIG. 5 illustrates the V/IP objects and interface relationships between users and the network, including external objects and interfaces. An object is a major process which has been identified within the functional specifications of the system. An interface is a communications path between two objects. External objects are objects which use interfaces that span between different network functions. By defining external objects and interfaces in this way, the V/IP system elements can be defined based on any communication which might be made across interfaces I6, I7, and I10 as shown in FIG. 5.

[0099] FIG. 5 shows a second level of partitioning illustrating the user, control and management planes within the network. Only those objects attached to a new or modified object for the V/IP service are shown. Other previously shown objects required for V/IP in the IP Management and Control Planes between I6 and I3 are not shown. The U1 PC to Phone service is a user plane service which is shown and defined in FIGS. 5 and 6.

[0100] FIG. 6 illustrates the V/IP objects and interface relationships which have been defined between internal ITN objects. Again only those objects or interfaces that are new or modified for V/IP are shown. Multiple objects may be contained within a single physical entity, and this physical entity may cross several planes.

[0101] The more significant objects and interfaces are now described in further detail.

[0102] ITN objects are considered to be partitions of the ITN processing requirements into sub-systems. A definition of ITN platform objects in this way, independent from protocol or message set constraints, provides a logical view of the system independent of those constraints.

User Plane Objects

[0103] U1 Object: Vocoder

[0104] The U1 Object converts packetized voice segments (which are encapsulated with IP) to and from circuit switched voice segments (which are encoded in Pulse Code Modulation (PCM)). The Vocoder performs various functions in order to accomplish this. It buffers a certain amount of packetized voice segments in order to maintain a continual flow on the circuit switched network. It dynamically assesses the delay characteristics of the transport network between the Vocoder and the User's software application in order to minimize those buffer requirements.

[0105] The Vocoder is able to handle all ITG ports in service, with all participants (on both sides of each call) talking at the same time. The Vocoder also identifies the level of packet loss resulting from voice transport across the IP network and maintains a record of that packet loss for summary reporting. Based on the level of packet loss, the Vocoder applies corrective algorithms to the voice wave form so that the resulting loss of signal quality is minimized for the called PSTN party.

[0106] The U1 Object is able to identify a loss of voice content packets, or a continuous stream of format errors in the encoded voice data incoming on the U1.I1 and U1.I10 interfaces (see FIG. 5),. If such a condition is found and there has been no corresponding signaling at the control plane level, U1 will notify C2 to pull down the connection and perform any necessary clean up tasks.

[0107] User Plane Interfaces

[0108] Two user plane interfaces are defined:

[0109] External Entity to V/IP User Plane

[0110] 1) U1.I1: The Internet Telephony Packetized Voice Interface is an external interface which is responsible for transporting Vocoded, packetized voice segments across the IP Access Network and IP Network.

[0111] 2) U1.I10: The Circuit Switched Voice Interface is an external interface responsible for transporting PCM voice segments across the PSTN.

[0112] Control Plane Objects

[0113] Three control plane objects are defined:

[0114] 1) C1: Internet Telephony Gateway Directory Object

[0115] 2) C2: Internet Telephony Call Control Object

[0116] 3) C3: Internet Telephony Authorization and Usage Recording Object (Internal)

[0117] The C1 Object: The Internet Telephony Gateway Directory manages which E.164 addresses (telephone numbers) are served within the terminating footprint of a particular ITG. The management of the terminating footprint may be in the form of NPA-NXX ranges which relate to an IP address for a single ITG. When queried with a “called” telephone number by the PC Call Control Object, the C1 object returns the IP address of the Internet Telephony Gateway (ITG) that serves the called telephone number.

[0118] The IP address of the V/IP Server is communicated to the PC user or Client software application prior to initiating contact with the C1 object. The object's TCP port number for the C1 directory application is defined, selected, and maintained within the client software.

[0119] The C2 Object: Internet Telephony Call Set-Up may be described as follows:

[0120] The ITN (ITG) communicates with the PC user to establish a PC-to-Telephone call. The call setup is originated by the PC user and destinated or terminated by the telephone user by supplying the address or number of the called terminal. However, it is the C2 Object or Call Control Object which coordinates the signaling among the involved network elements. Included in this signaling are:

[0121] Management of the state of the call with the client PC software (via C2.I1 shown in FIG. 5).

[0122] Validation of a PC users' Account number and password (via C3.I4 shown in FIG. 6).

[0123] Establishment and tear down of the PSTN circuit (via C4.I7 shown in FIG. 5).

[0124] Generation of usage information which is sent for processing and pricing (via C3.I4 shown in FIG. 6).

[0125] Managing the state of the connection within C3 (via C3.I4 shown in FIG. 6).

[0126] When initiating a V/IP call, the PC user may be required to provide the 10 digit E.164 (ITU-T telecommunication numbering or telephone number) address of the called telephone user, the IP address of the ITG associated with the called telephone user (obtained via the C1 Object), the PC's IP address, as well as the billing account number and associated password.

[0127] The C2 object is able to signal various states of a connection (ringing, busy, etc.) to a PC user. If the C2 object receives a maximum call duration from C3 during call set-up, this maximum call duration is sent to the PC software either as an audio message or as information to be presented on the PC screen. C2 generates the raw usage records which are sent to C3. A usage record is not tagged as billable unless the PC application has acknowledged its receipt of a connection establishment message. The C2 object may require a user ID and password to be provided by the PC Client software prior to completing a V/IP call. This information is authenticated via the C3 object.

[0128] The C3 Object: User Authorization and Usage Recording

[0129] The C3 Object ensures coordination between User Authorization and Usage Recording for a single PC user's customer account. C3 also responds to external requests for that information. C3 is a unitary logical object with distributed instances. That is, physically distributed account, authorization, validation and billing databases are so arranged as to be usable as a single logical object. The data associated with a user subscriber account is typically stored in an instance of C3 which is local to the user subscriber. The C3 Object is invoked during a call when an Authorization request is relayed over C3.I4 (this request typically consists of an account number and password provided by PC User). At this point C3 checks the account's password and available monthly minutes remaining, and responds appropriately to C2. Optionally, C3 can respond to C2 with a maximum allowable minute duration for a call. Successful account validation by the C3 Object is a prerequisite to successful call establishment by the C2 Object.

[0130] The C3 Object is also responsible for accepting usage recording data from C2, and decrementing the minutes used from the available minutes (and/or optionally pricing that usage, and decrementing that priced amount from a customer's existing balance), and then logging the information. Preferably, C3 also knows the state of a users connections across multiple ITGs. With this state information, the authorization system may ensure only one call per account is being handled by the network, and/or ensure that the maximum available minute limit is not being circumvented by multiple concurrent sessions (otherwise a second PC caller might receive authorization for a call prior to the posting of the first caller's usage record).

[0131] The theory behind bundling usage recording, pricing, and authorization into one logical object is to significantly reduce the potential for fraud when the system is widely deployed. By having a single logical database which is managing customer authentication, authorization, and usage pricing for the network, data synchronization is facilitated, and opportunities for fraud are minimized. As described, it is not necessary that C3 be implemented as a single physical system. The C2 Object will provide C3 with a customer billing account number and a password (originally supplied by the PC user). The C3 Object maintains a current account “minutes remaining” balance and usage records for each user on a monthly basis. This usage information can be extracted in real time based on a request from the M1.I5 interface as shown in FIG. 6.

[0132] If a user who is requesting authorization has a low “minutes remaining” balance, and this low balance will result in a maximum call duration which is shorter than the maximum call duration typically allowed by the network, then the Authentication server will transmit a maximum call duration back to the C2 Object.

[0133] The Control Plane Interfaces

[0134] Four control plane interfaces are defined:

[0135] External Entity to V/IP Control Plane

- [0136] 1) C1.I1: The Internet Telephony Directory Interface is an external interface which is responsible for PC to Directory services address resolution (see FIG. 5). The client PC provides the E.164 address (telephone number) of the intended party to be called, and the Directory service returns the IP address of the appropriate hop-off. Internet Telephony Gateway.
- [0137] 2) C2.I1: The Internet Telephony Call Management Interface is an external interface which is responsible for PC to Internet Telephony Gateway signaling for call establishment and tear-down.
- [0138] 3) C4.I7: PSTN Call Management Interface is an external interface which is responsible for managing signaling to the PSTN which is necessary for the PSTN to establish and tear down circuit switched connections to the called party. Signaling from the ITG to the serving PSTN central office is preferably via PRI ISDN. Alternately, T1 E&M PSTN signaling may be used.
- [0139] 4) C3.I4: The Internet Telephony Authorization and Usage Recording Interface is an internal interface shown in FIG. 6, and is responsible for two functions. First the interface must allow for an authorization of ITG usage by a service subscriber. Second, the interface must maintain the current state of a subscriber's connections within C3, as well as pass ITG generated usage records from C2 to C3 in real time.
  Management Plane Objects

[0140] Five management plane objects are defined and shown in FIG. 6:

[0141] 1) M1: ITN Information Server & Feedback Object

[0142] 2) M2: ITN Subscription Server Object

[0143] 3) M3: ITN Billing System Object

[0144] 4) M4: ITN Directory Maintenance Object (Internal)

[0145] 5) M5: ITN Surveillance Object (Internal)

[0146] The M1 Object: The ITN Information & Feedback Server allows the PC user to access information -on the V/IP service including general and user-specific information. Essentially, the M1 Object is the HTML interface to the V/IP network for subscribers of the service. Following is the information which the user might request from the ITN via HTML:

- [0147] Descriptions on how to download and install client software and operate the service
- [0148] Descriptions of service availability and pricing plans
- [0149] Graphical (map) areas showing the ITG terminating footprints
- [0150] NPA-NXX ranges supported by the ITG terminating footprints
- [0151] Call usage record details (will extract the data from the control plane in real time via M1.I5)
- [0152] Billing account status & balance (will extract the data real time via M1.I5)
- [0153] Change of the ITN password (will verify old password and update to new password via M1.I5)
- [0154] An introductory page, with links to each of the pages items listed above.

[0155] Operationally the M1 Object interface will be accessible via commercial browsers and at least a Netscape 3.0 or Internet Explorer 3.0 web browser. On any customer specific request for usage records or account balance, a PC user will have to provide within the query the same account number and password which is used for call establishment. This information will be validated by C3 when fulfilling the request.

[0156] The M2 Object: ITN Subscription Server: The ITP allows the PC user to subscribe to the V/IP service via an on-line process. Information gathered from the potential subscriber will include:

[0157] ISP (Internet Service Provider) account number

[0158] ISP email address

[0159] CPU type of PC, amount of memory

[0160] Type of sound card, microphone, and speakers

[0161] Operating System and version

[0162] Global Service Provider (GSP)

[0163] Free disk space

[0164] Upon activation the subscriber will receive notification via email. This email will include instructions, the web page URLs (Uniform Resource Locator or www (World Wide Web) address) needed to get started, and an initial password (which can be changed via M1).

[0165] The M3 Object: ITN Billing System: Monthly, the M3 Object will poll C3 to extract account balances and credit card numbers in order to request payments from credit card companies. As account balances are processed by the M3 Object, failed billing attempts will be flagged in a report (either formatted as ASCII, or in a PC database product's format).

[0166] The M4 Object: ITN Directory Maintenance: Directory data (in the form of NPA-NXX ranges pointing to ITGs) will be created, validated, and managed outside of the network (away from C1, the ITN Directory Object). The M4 object is responsible for this function. M4 will accomplish this by assisting in the creation of the Directory tables in a format which can be exported directly (via M4.I5) to C1. The M4 Object preferably also supports the creation of graphical maps showing the terminating call areas supported by the ITGs. The maps and the NPA-NXX table information may be exported so that it may be presented to the user via M1. Off the shelf software products like MapInfo may be used to support the requirements of M4.

[0167] Operationally the M4 Object is able to import NPA-NXX data, along with supporting graphical central office serving area information. The object is able to graphically define ITG terminating calling areas. The M4 Object automatically generates the NPA-NXX to ITG IP address Directory table based on the graphical information provided above. The M4 Object supports multiple versions of the C1 Object Directory database.

[0168] The M5 Object: ITN Surveillance: The V/IP service may cross many network elements within the ITN. Having a centralized surveillance capability which can span multiple platforms ensure its operation. The M5 Object attempts to identify and log critical alarms, and to present these alarms to an administrative console. Such alarms may include: Whether a network based application is under distress (via an SNMP Management Information Block (MIB)), whether the system is alive and communicating with the network (via “Ping” or similar function), whether required application processes are active and if they need to be restarted (via a “ps -eaf” or similar function), whether the processes are sane (via periodic test queries to validate correct responses).

[0169] These types of problems may be analyzed by M5, and alarms generated and logged within C5 at four levels: S Critical (service affecting), Major (user intervention recommended), Minor (of note), and Informational (components reporting normal operation). These alarms may be used to manage a local database containing managed objects representing the current operational state of ITN platforms and processes. Each managed object and/or platform will be assigned one of three operational states: Red (out of service), Orange (operating with degraded capabilities), and Green (operating normally). A graphical representation of the ITN network is presented to a console via a standard display package such as OpenView. Console operators have the option of directly connecting to any ITN object or system to perform troubleshooting or diagnostic operations. This connection presents the console operator with the same capabilities as a local system administrator.

[0170] With respect to M5 addressing requirements, new elements added to the ITN will have their IP addresses and their type of object identified in M5. The M5 Object will create its database of managed objects dynamically (once given the IP address or host name) via the M5x.I5 interfaces.

[0171] Management Plane Interfaces

[0172] Ten Management Plane Interfaces have been defined:

[0173] External Entity to V/IP Management Plane

- [0174] 1) M1.I1: Internet Telephony Data Request Interface
- [0175] 2) M2.I1: Internet Telephony Subscription Interface
- [0176] 3) M3.I10: Credit Card Provider Interface V/IP Management Plane to V/IP Control Plane
- [0177] 4) M1.I5: Internet Telephony Network Data Extraction Interface
- [0178] 5) M2.I5: Internet Telephony Subscription Management Interface
- [0179] 6) M3.I5: Internet Telephony Billing and Usage Extraction Interface
- [0180] 7) M4.I5: Internet Telephony Directory Maintenance Interface
- [0181] 8) M5a.I5: Internet Telephony Call Management Surveillance Interface
- [0182] 9) M5b.I5: Internet Telephony Authorization and Usage Recording Surveillance Interface
- [0183] 10) M5c.I5: Internet Telephony Directory Surveillance Interface

[0184] The functions of these interfaces are as follows:

[0185] The M1.I1 Interface: The Internet Telephony Data Request external interface is responsible for providing a subscriber with data requested about the ITN in real time.

[0186] The M3.I10 Interface: The Credit Card Provider external interface is responsible for allowing an ISP to place a charge against a user's credit card account number.

[0187] The M1.I5 Interface: The Internet Telephony Network Data Extraction internal interface is responsible for providing the M1 Object with real time data regarding a subscriber's remaining minutes of use, usage records of the current and previous billing cycle, and/or calls currently in progress. The M1 Object will reformat and present this data to the subscriber who requested it.

[0188] The M2.I5 Interface: The Internet Telephony Subscription Management internal interface is responsible for managing the list of account numbers allowed to use the ITN. This interface supports several functions: an initial batch load of subscribers and initial passwords, adding or removing individual account numbers, and resetting individual passwords.

[0189] The M3.I5 Interface: The Internet Telephony Billing and Usage Extraction internal interface is responsible for performing a periodic extraction of usage records from the network.

[0190] The M4.I5 Interface: The Internet Telephony Directory Maintenance internal interface is responsible for maintaining the NPA-NXX to hop-off ITG directory data.

[0191] The M5a.I5 Interface: The Internet Telephony Call Management Surveillance internal interface is responsible for carrying a variety of information which allows M5 to assess the availability, health, and status of the physical computer and software processes of the various Internet Telephony Gateways.

[0192] Based on the foregoing descriptions of the interfaces and objects a high level call flow of signaling messages is described. FIG. 7 illustrates an example diagram of such a control plane message flow. This example should be understood to show one version or embodiment of a set of messages which may be implemented for a PC to PSTN service. Converse messages would be utilized for a PSTN initiated PSTN to PC service, as well as appropriate corresponding messages for PC-PC and telephone-telephone service. Additional messages may be added if enhanced functionality is provided.

[0193] The call flow starts at the point where the user has established IP layer connectivity with the network, and has invoked the V/IP software application. This preliminary procedure typically entails the following steps by the party initiating the call (not illustrated in FIG. 7):

[0194] 1. The customer will boot the PC, and connect to the IP network following their existing procedures for network access.

[0195] 2. The customer will launch their V/IP application, either as a plug-in to an existing browser or as a stand-alone application. When launched, this application will present a template of fields which are required to initiate a call.

[0196] 3. The customer will populate a “telephone number to be called” data field. The customer will also either populate his/her account number and password, or the application will reapply this data if it has been previously saved within the application.

[0197] 4. The customer will then initiate the call. During the call, the call's completion status will be presented in real-time to the user by the application (via a visual display). One example of the call initiation procedure is now described.

[0198] The following steps commence with the Called Party Address Request step in FIG. 7 and proceed as follows:

[0199] 1. The user initiates a call via the PC's V/IP software. This software application invokes the Directory (C1 Object) to obtain the IP address of the destination ITG. Based on the dialed number submitted by the PC application as described in the foregoing preliminary procedure, the C1 Object returns the IP address of the associated ITG (C2 Object).

[0200] 2. The PC's V/IP software application invokes the C2 Object to set up a call by passing to C2 the number to be called, the user's account number, and a password. This is shown as SETUP in FIG. 7.

[0201] 3. C2 invokes the C3 Object in order to receive authorization to proceed with the call (PSTN Termination Request). This may entail communication among instances of the distributed database to verify the account status of the caller and optionally set a limit on the duration or cost of the call depending upon the account status and/or balance. The pricing of the call may be communicated to C2 for communication to the caller. C3 will pass the authorization information back to the C2 (PSTN Termination Authorization).

[0202] 4. If authorization was successful, C2 will establish the PSTN connection, and notify the client software that the call is proceeding (SETUP Call Proceeding). C2 may also pass on to the calling PC the pricing information obtained from C3. C2 will continue to update the client software with call establishment information as the call is proceeding and may also pass along to the caller a running account of the cost of the call.

[0203] 5. After the call has been established, the PC will respond to the network that it recognizes that a connection has been established (Connection Acknowledged), timing of the call's duration can be initiated, and any usage measurements will indicate that the call is billable.

[0204] 6. Steady state call (Voice Flow).

[0205] 7. The PC's V/IP software application invokes the C2 service to release the call. The PC application signals release to C2, and C2 releases the call in the PSTN and confirms the release back to PC application. Also, timing of the call's billable duration is completed. Alternatively, the PSTN user may initiate call tear down as well.

[0206] 8. The C2 Object passes a usage record to C3 for reporting. The C3 Object may also initiate individual call billing by reporting to M3 as shown in FIG. 6.

[0207] A modified version or embodiment of the call set up procedure is now described in connection with FIG. 8.

[0208] The following steps commence with the Called Party Address Request step in FIG. 7 and proceed as follows:

[0209] 1. The user initiates a call via the PC's V/IP software. This software application invokes the Directory (C1 Object) to obtain the IP address of the destination ITG. Based on the dialed number submitted by the PC application, the C1 Object returns the IP address of the associated ITG (C2 Object).

[0210] 2. The PC's V/IP software application invokes the C2 Object to set up a call by passing to C2 the number to be called, the user's account number, and a password (Connection Request).

[0211] 3. The C2 Object invokes the C1 Object to request the customer account server address (Customer Account Server Address Req), which is then returned (Customer Account Server Address Resp).

[0212] 4. The C2 Object invokes the C3 Object for account validation (Account Validation) using the Customer Account Server Address (address of the instance of the C3 object database) and receives call authorization (Call Authorization). This may include limitations as described in connection with the description of FIG. 7.

[0213] 5. If authorization was successful, C2 will establish the PSTN connection, and notify the client software that the call is proceeding. C2 will continue to update the client software with call establishment information as the call is proceeding.

[0214] 6. After the call has been established, the PC will respond to the network that it recognizes that a connection has been established (Connect Ack), timing of the call's duration can be initiated, and any usage measurements will indicate that the call is billable.

[0215] 7. Steady state call (U1 Service PC to telephone).

[0216] 8. The PC's V/IP software application invokes the C2 service to release the call. The PC application signals release to C2, and C2 releases the call in the PSTN and confirms the release back to PC application. Also, timing of the call's billable duration is completed. Alternatively, the PSTN user may initiate call tear down as well.

[0217] 9. The C2 Object passes a usage record to C3 for reporting and for individual call billing if that option is chosen. The C3 Object acknowledges receipt of the usage record to C2.

[0218] FIG. 9 provides a high level diagrammatic illustration of a typical PC which may be utilized by a user in the system of the invention.

[0219] FIG. 10 illustrates a typical client software state machine which is executed in the subscriber's PC. The V/IP software state machine correlates operations within the environment of the typical/high end PC of the user. FIG. 10 provides an example of how the end user interacts with the V/IP network via the client software. Interaction between the PC user and the software's state machine utilizes messages which cross between the client software's state machine and the operating system's input/output drivers for each hardware device. The more significant messages and the content which they may carry may be summarized as follows:

[0220] Keyboard/Mouse

[0221] Call Initiation: This comprises the input of information needed by the state machine (and the V/IP control plane) which is required to establish a call. The information includes the calling party's account number and password, as well as the telephone number being called.

[0222] PC User Call Termination Request: This comprises the input of a notification by the user to the software to conclude the call.

[0223] Display/Monitor

[0224] Error Notification: This comprises a dialog which shows the reason for the failure of a particular call.

[0225] Call Establishment Notification: This refers to the display information showing the step-by-step progression of a call as it is established through the network.

[0226] Call Completion Notification: This comprises a dialog which shows the statistics of a completed call.

[0227] FIG. 11 shows the PC software interfaces (stack) and the relationship to the ITN interfaces. It is necessary that the V/IP software state machine fit seamlessly within the environment of a typical high end PC owned by an ISP subscriber. FIG. 11 shows how the state machine interacts with the other software components for Internet connectivity and communication. Using the types of PC shown in FIG. 9, state machine shown in FIG. 10, and interface relationships shown in FIG. 11, the following customer software characteristics and functions are significant:

[0228] 1. It is not necessary for the client software to validate that IP Access Network or IP Network connectivity has been established prior to attempting to communicate with the network. The availability of connectivity across these layers is assumed. A lack of response by the network to the application's state machine is displayed to the user as a lack of network level connectivity.

[0229] 2. Each of the five V/IP network interfaces is able to have their transactions traverse seamlessly across the IP Access Network and IP Network. The client software should use the same IP network drivers which are used for their existing ISP Internet connectivity. Client software driver conflicts or adverse interactions should not occur with the installed base of PC software.

[0230] 3. All management plane interfaces with the user may be via the PC's existing Web Browser. The client software need not take on the task of managing network based customer data.

[0231] 4. The compressed voice interface, U1.I1, preferably communicates via UDP (User Datagram Protocol), however, RTP (Routing Table Protocol) on top of UDP is also an option. If RTP is used, the client software should validate that it is a valid option over the existing IP network.

[0232] 5. If RTP is selected, and communication over the IP Access network is performed with a PPP link, RTP header compression should be supported in order to reduce the required IP Access network bandwidth.

[0233] 6. The software must be able to transmit DTMF digits to the hop-off ITG. Preferably the digits will be transmitted “out of band” (in other words, the PC will not generate DTMF signals which are transmitted as compressed tones).

[0234] 7. The software should be able to transmit the length (duration) that a DTMF digit a pressed.

[0235] 8. The software should display to the user the current state of a call as it is made through the Internet Telephony Gateway (ITG).

[0236] 9. The voice played back to the PC user will be toll quality. The Vocoder includes capabilities such as echo cancellation, it should be able to handle varying levels of packet loss and latency, and it should be able to apply corrective algorithms to the voice stream.

[0237] 10. A user account number and password should be required within the Call Initiation message to the state machine. If the user so chooses, these items should be able to be saved within the client application.

[0238] In order to insure ease of use and maximum utility to the subscriber it is desirable to provide for the subscriber an easy access and instructional tutorial as to the use of the system. At the same time it is also desirable to provide the subscriber with his/her billing account balance, status, and call usage details on a real time basis. This information may include descriptions on how to download and install client software and operate the service, descriptions of service availability and pricing plans, graphical (map) areas showing the ITG terminating footprints, and NPA-NXX ranges supported by the ITG terminating footprints. With respect to account information the data available to the subscriber may include call usage record details, billing account status & balance, and verification of the existing password. All of the foregoing may be conveniently provided through the use of an introductory page with links to pages that provide access to each of the foregoing.

[0239] The system of the invention provides the above described features through the architecture illustrated in FIGS. 4, 5, 6, and 12. Thus FIG. 6 shows the authorization and usage object C3 connected to an Information Server Object M1 in the V/IP management plane. This information and feedback object M1 comprises a server separate from the C3 authorization and usage object but connected to the C3 control plane object via the M1.I5 interface between the ITN management plane and control plane functions. The M1 object serves as an HTML interface to the V/IP network for subscribers to the service.

[0240] Operationally the M1 Object interface is accessible via commercial browsers and at least a Netscape 3.0 or Internet Explorer 3.0 web browser. On any customer specific request for usage records or account balance, a PC user will have to provide within the query the same account number and password which is used for call establishment. This information will be validated by C3 before fulfilling the request. The M1.I1 link between the PC user browser and M1 information server is shown in FIG. 5. The subscriber, using a commercial browser such as Netscape 3.0 or Internet Explorer 3.0 and HTML by way of example, accesses the information server via M1.I1. The information server validates the password and obtains the information from the authorization, usage and account object C3 via M1.I5, and presents the information to the PC user subscriber with the correct formatting display via M1.I1.

[0241] The M1 information server provides real time interface to the authorization, usage and account object C3 while at the same time also providing isolation of the C3 object. The information server thus provides an intermediary which, among other things, prevents undesirable interaction between information retrieval and service implementation in the C3 authorization, usage and account object. Appropriate sizing of the capacity of the information server permits the provision of virtually instant access for subscribers without necessarily requiring interrelated sizing of the authentication, usage and account object.

[0242] The combination of the logically unitary distributed authorization, usage and account object with this intermediary information server, which is constantly available to subscriber, presents a unique and powerful tool for information retrieval and usage. As has been previously explained, the distinctive authorization, usage and retrieval object provides tracking of multiple ongoing calls against the same account through separate and geographically distal ITGs and network elements.

[0243] The new information server permits a subscriber to engage in real time monitoring of this activity and real time tracking of overall account status and balance. Further, there is no requirement that the subscriber perform such monitoring or information gathering from a fixed locale. The information is as readily available from a hotel room by laptop computer as from the home location of the subscriber. Still further, the information may be retrieved and monitored not only by the subscriber but also by any entity with valid credentials for accessing the service, such as a super account holder or employer. This also provides a mechanism for an employer to act on the obtained information to place a stop on further use of any supervised account.

[0244] FIG. 12 provides a simplified illustration of this aspect of the overall communication system. Referring to that figure the IP Routed Internet/Intranet is shown at 400. The Circuit Switched Network, such as a public switched telephone network, is shown at 410. The circuit switched network serves a large number of subscriber terminals, here illustrated as telephone terminals 412, 414, and 416. The telephone terminals may typically be connected to the circuit switched network via end offices or central offices 418, 420, and 422 via local links or loops. It will be appreciated that these terminals may be distributed over a wide geographical area such as the entire United States or North America, by way of example.

[0245] The circuit switched network is connected to the packet switched network via a plurality of C2 call control objects or ITGs shown here by way of illustration as 424, 426, 428, 430, and 432. These gateway control objects are connected to routers in the Internet/Intranet as shown at 434, 436, 438, 440, and 442. The ITGs are also connected to end or central offices in the circuit switched network shown here as 444, 446, 448, 450, and 452. Also connected to the Internet/Intranet are voice equipped personal computers or PCs 454, 456, and 458. These PCs are shown connected to routers 460, 462, and 464. It will be appreciated that the particular gateway or ITG chosen to effect a particular communication path is dependent upon multiple factors, such as the lowest cost connection through the telephone network, by way of example. Thus the ITG 424 may be chosen to effect a link between PC 454 and telephone terminal 412.

[0246] As has been explained, the gateway controllers are all linked to the C3 authentication, usage and account object 466 as shown here at 468. The authentication, usage and account object in turn is linked to the information server object M1, here shown at 468. This has previously been described in more detail in connection with FIGS. 4, 5, and 6 hereinabove.

[0247] It is believed that this simplified diagrammatic illustration in FIG. 12 will facilitate an appreciation of the power of the authentication, usage, and account object C3 acting in conjunction with the information server M1. The arrangement permits the information server to provide to users almost immediate access to information regarding accounts which may actually be locally stored in instances of the authentication, usage and account object dispersed over an enormous geographical area. Such flexibility permits travelers to access their accounts from hotel rooms, while their employers may also access those accounts from the home or any branch office of the business establishment.

[0248] While the foregoing has described what are considered to be preferred embodiments of the invention, it is understood that various modifications may be made therein and that the invention may be implemented in various forms and embodiments, and that it may be applied in numerous applications, only some of which have been described herein. It is intended by the following claims to claim all such modifications and variations which fall within the true scope of the invention.

Claims

The invention claimed is:

1. A method, comprising:

receiving a request from a calling party to place a call to a called party, the calling party having a calling party number in E.164 format and associated with a packet-switched network, and the called party having a called party number in E.164 format and associated with a circuit-switched network;

receiving calling party authorization information;

authorizing the call when the calling party authorization information is determined to be valid;

determining a gateway associated with the called party number, based on the called party number,

establishing a call between the calling party and called party via the gateway and at least partially via the packet-switched network;

tracking call data associated with the call, the call data including the time and length of the call;

storing the call data in substantially real-time in a database connected to the packet switched network;

receiving a request from the calling party to retrieve the call data;

retrieving the call data from the database;

providing the call data to the calling party.

2. The method of claim 1, wherein the calling party authorization information is determined to be valid when the calling party authorization information matches calling account authorization information associated with a calling account associated with the calling party.

3. The method of claim 2, wherein the calling account authorization information is stored in the database.

4. The method of claim 3, wherein the database is distributed over a plurality of remote locations.

5. The method of claim 1, wherein a calling party account is associated with the calling party, the calling party account having an available balance, and wherein the calling party authorization information is determined to be valid when a cost of the call is within the available balance.

6. The method of claim 1, further comprising:

after receiving a request from the calling party to retrieve the call data, but prior to providing the call data to the calling party, authenticating the calling party.

7. The method of claim 1, wherein the calling party authentication information includes an account number and a password.

8. A method, comprising:

receiving a request from a calling party to place a call to a called party, the calling party having a calling party number in E.164 format and associated with a packet-switched network, the called party having a called party number in E.164 format and associated with a circuit-switched network, the calling party having a calling account and credit card account;

receiving calling party authorization information;

authorizing the call when the calling party authorization information is determined to be valid;

determining a gateway associated with the called party number, based on the called party number;

establishing a call between the calling party and called party via the gateway and at least partially via the packet-switched network;

tracking call data associated with the call, the call data including the time and length of the call;

storing the call data in a database connected to the packet switched network;

calculating a fee associated with the calling party calling account based on the call data;

billing the fee to the calling party credit card account periodically.

9. The method of claim 8, wherein authorizing the call includes:

comparing the calling party authorization information to authorization information associated with the calling account.

10. The method of claim 8, wherein authorizing the call includes:

determining a cost of the call prior to establishing the call;

determining whether enough funds are available in the calling account to cover the cost of the call.

11. The method of claim 8, further comprising:

providing call cost information to the calling party prior to establishing the call.

12. The method of claim 8, further comprising:

providing the fee to the calling party during a call in substantially real time.

13. The method of claim 8, wherein the calling party authorization information is not valid when another call is in progress associated with the calling account.

14. A method, comprising:

receiving a request to establish a calling account associated with a phone service for a user, the phone service using a packet-switched network for call transmission and control;

establishing the calling account for the user, the calling account having an account number, a password and a user number in E.164 format;

receiving user credit card information associated with a user account with a credit provider, and authorization to directly submit charges for usage fees associated with usage of the phone service by the user to the credit provider;

receiving at least one request to establish a call between the user and a third party, the at least one request received over a packet-switched network, the third party associated with a circuit-switched network;

establishing the call between the user and the third party via the packet-switched network and via a gateway connected to the packet-switched network and the circuit-switched network;

generating usage fees associated with usage of the phone service by the user;

directly submitting the usage fees to the credit provider for payment.

15. The method of claim 14, further comprising:

storing the usage fees in the user account;

receiving a request from the user to view the usage fees;

providing a display including the usage fees.

16. The method of claim 14, further comprising:

receiving a request from the user to change the password;

changing the password in response to the request.

17. The method of claim 15, further comprising:

authenticating the user prior to providing the display including the usage fees.

Patent Citations (919)

Patent	Date	Inventor	Cited By
US4054756(A)	1977-10-01	Comella et al.	Applicant
US4100377(A)	1978-07-01	Flanagan	Applicant
US4191860(A)	1980-03-01	Weber	Applicant
US4201891(A)	1980-05-01	Lawrence et al.	Applicant
US4310727(A)	1982-01-01	Lawser	Applicant
US4313035(A)	1982-01-01	Jordan et al.	Applicant
US4313036(A)	1982-01-01	Jabara et al.	Applicant
US4371752(A)	1983-02-01	Matthews et al.	Applicant
US4375097(A)	1983-02-01	Ulug	Applicant
US4555594(A)	1985-11-01	Friedes et al.	Applicant
US4565903(A)	1986-01-01	Riley	Applicant
US4577066(A)	1986-03-01	Bimonte et al.	Applicant
US4585906(A)	1986-04-01	Matthews et al.	Applicant
US4602129(A)	1986-07-01	Matthews et al.	Applicant
US4609778(A)	1986-09-01	Franklin et al.	Applicant
US4611094(A)	1986-09-01	Asmuth et al.	Applicant
US4611096(A)	1986-09-01	Asmuth et al.	Applicant
US4625081(A)	1986-11-01	Lotito et al.	Applicant
US4630262(A)	1986-12-01	Callens et al.	Applicant
US4652700(A)	1987-03-01	Matthews et al.	Applicant
US4653045(A)	1987-03-01	Stanley et al.	Applicant
US4672700(A)	1987-06-01	Poncy	Applicant
US4679190(A)	1987-07-01	Dias et al.	Applicant
US4685125(A)	1987-08-01	Zave	Applicant
US4710917(A)	1987-12-01	Tompkins et al.	Applicant
US4713806(A)	1987-12-01	Oberlander et al.	Applicant
US4718005(A)	1988-01-01	Feigenbaum et al.	Applicant
US4730071(A)	1988-03-01	Schoenthal	Applicant
US4734931(A)	1988-03-01	Bourg et al.	Applicant
US4741820(A)	1988-05-01	Coughlin	Applicant
US4747130(A)	1988-05-01	Ho	Applicant
US4748618(A)	1988-05-01	Brown et al.	Applicant
US4765924(A)	1988-08-01	Inoue	Applicant
US4766604(A)	1988-08-01	Axberg	Applicant
US4771425(A)	1988-09-01	Baran et al.	Applicant
US4782485(A)	1988-11-01	Gollub	Applicant
US4788718(A)	1988-11-01	McNabb et al.	Applicant
US4790003(A)	1988-12-01	Kepley	Applicant
US4821034(A)	1989-04-01	Anderson et al.	Applicant
US4827500(A)	1989-05-01	Binkerd et al.	Applicant
US4865763(A)	1989-09-01	Inoue	Applicant
US4866763(A)	1989-09-01	Cooper et al.	Applicant
US4872157(A)	1989-10-01	Hemmady et al.	Applicant
US4872160(A)	1989-10-01	Hemmady et al.	Applicant
US4872197(A)	1989-10-01	Pemmaraju	Applicant
US4875206(A)	1989-10-01	Nichols et al.	Applicant
US4877949(A)	1989-10-01	Danielson	Applicant
US4882476(A)	1989-11-01	White	Applicant
US4893302(A)	1990-01-01	Hemmady et al.	Applicant
US4894824(A)	1990-01-01	Hemmady et al.	Applicant
US4897874(A)	1990-01-01	Lidinsky et al.	Applicant
US4899333(A)	1990-02-01	Roediger	Applicant
US4899373(A)	1990-02-01	Lee et al.	Applicant
US4910794(A)	1990-03-01	Mahany	Applicant
US4916691(A)	1990-04-01	Goodman	Applicant
US4918722(A)	1990-04-01	Duehran et al.	Applicant
US4922486(A)	1990-05-01	Lidinsky et al.	Applicant
US4933931(A)	1990-06-01	Kokubo	Applicant
US4942574(A)	1990-07-01	Zelle	Applicant
US4958341(A)	1990-09-01	Hemmady et al.	Applicant
US4969184(A)	1990-11-01	Gordon et al.	Applicant
US4979206(A)	1990-12-01	Padden et al.	Applicant
US4996707(A)	1991-02-01	O'Malley et al.	Applicant
USD315573(S)	1991-03-01	Schultz	Applicant
US5008906(A)	1991-04-01	Reichwein	Applicant
US5008926(A)	1991-04-01	Misholi	Applicant
US5009337(A)	1991-04-01	Bimbi	Applicant
US5012511(A)	1991-04-01	Hanle et al.	Applicant
US5018191(A)	1991-05-01	Catron et al.	Applicant
US5019699(A)	1991-05-01	Koenck	Applicant
US5023868(A)	1991-06-01	Davidson	Applicant
US5025254(A)	1991-06-01	Hess	Applicant
US5029196(A)	1991-07-01	Morganstein	Applicant
US5029199(A)	1991-07-01	Jones et al.	Applicant
US5029200(A)	1991-07-01	Haas	Applicant
US5031098(A)	1991-07-01	Miller	Applicant
US5034975(A)	1991-07-01	Grimes	Applicant
US5052020(A)	1991-09-01	Koenck	Applicant
US5052943(A)	1991-10-01	Davis	Applicant
US5065393(A)	1991-11-01	Sibbitt et al.	Applicant
US5068888(A)	1991-11-01	Scherk et al.	Applicant
US5070536(A)	1991-12-01	Mahany	Applicant
US5098877(A)	1992-03-01	Coughlin	Applicant
US5107492(A)	1992-04-01	Roux et al.	Applicant
US5113499(A)	1992-05-01	Ankney et al.	Applicant
US5115431(A)	1992-05-01	Williams et al.	Applicant
US5115495(A)	1992-05-01	Tsuchiya et al.	Applicant
US5123064(A)	1992-06-01	Hacker	Applicant
US5134647(A)	1992-07-01	Pugh et al.	Applicant
US5144282(A)	1992-09-01	Sutterlin	Applicant
US5146488(A)	1992-09-01	Okada et al.	Applicant
US5146491(A)	1992-09-01	Silver et al.	Applicant
US5157390(A)	1992-10-01	Yoshie et al.	Applicant
US5157662(A)	1992-10-01	Tadamura et al.	Applicant
US5159592(A)	1992-10-01	Perkins	Applicant
US5159624(A)	1992-10-01	Makita	Applicant
US5163080(A)	1992-11-01	Amoroso	Applicant
US5164938(A)	1992-11-01	Jurkevich et al.	Applicant
US5180232(A)	1993-01-01	Chadma	Applicant
US5185860(A)	1993-02-01	Wu	Applicant
US5193110(A)	1993-03-01	Jones et al.	Applicant
US5195085(A)	1993-03-01	Bertsch et al.	Applicant
US5195086(A)	1993-03-01	Baumgartner et al.	Applicant
US5195128(A)	1993-03-01	Knitl	Applicant
US5195183(A)	1993-03-01	Miller	Applicant
US5199062(A)	1993-03-01	Von Meister	Applicant
US5200993(A)	1993-04-01	Wheeler et al.	Applicant
US5202817(A)	1993-04-01	Koenck	Applicant
US5202825(A)	1993-04-01	Miller	Applicant
US5204894(A)	1993-04-01	Darden	Applicant
US5206901(A)	1993-04-01	Harlow et al.	Applicant
US5208848(A)	1993-05-01	Pula	Applicant
US5215011(A)	1993-06-01	Monney	Applicant
US5216233(A)	1993-06-01	Main	Applicant
US5218187(A)	1993-06-01	Koenck	Applicant
US5218188(A)	1993-06-01	Hanson	Applicant
US5223699(A)	1993-06-01	Flynn et al.	Applicant
US5223820(A)	1993-06-01	Sutterlin	Applicant
US5225071(A)	1993-07-01	Coughlin	Applicant
US5226075(A)	1993-07-01	Funk et al.	Applicant
US5227614(A)	1993-07-01	Danielson	Applicant
US5231492(A)	1993-07-01	Dangi et al.	Applicant
US5235317(A)	1993-08-01	Sutterlin	Applicant
US5237604(A)	1993-08-01	Ryan	Applicant
US5241588(A)	1993-08-01	Babso et al.	Applicant
US5243645(A)	1993-09-01	Bissell et al.	Applicant
US5243654(A)	1993-09-01	Hunter	Applicant
US5247571(A)	1993-09-01	Kay et al.	Applicant
US5254971(A)	1993-10-01	Sutterlin	Applicant
US5260986(A)	1993-11-01	Pershan	Applicant
US5263080(A)	1993-11-01	Jones et al.	Applicant
US5265155(A)	1993-11-01	Castro	Applicant
US5272749(A)	1993-12-01	Masek	Applicant
US5274696(A)	1993-12-01	Perelman	Applicant
US5280159(A)	1994-01-01	Warner	Applicant
US5287199(A)	1994-02-01	Zoccolillo	Applicant
US5289378(A)	1994-02-01	Miller	Applicant
US5289468(A)	1994-02-01	Yoshida	Applicant
US5295154(A)	1994-03-01	Meier et al.	Applicant
US5303297(A)	1994-04-01	Hillis	Applicant
US5305181(A)	1994-04-01	Schultz	Applicant
US5308966(A)	1994-05-01	Danielson	Applicant
US5309437(A)	1994-05-01	Perlman et al.	Applicant
US5311583(A)	1994-05-01	Friedes et al.	Applicant
US5313053(A)	1994-05-01	Koenck	Applicant
US5317566(A)	1994-05-01	Joshi	Applicant
US5317691(A)	1994-05-01	Traeger	Applicant
US5318719(A)	1994-06-01	Hughes	Applicant
US5322991(A)	1994-06-01	Hanson	Applicant
US5325421(A)	1994-06-01	Hou et al.	Applicant
US5327421(A)	1994-07-01	Hiller et al.	Applicant
US5327486(A)	1994-07-01	Wolff et al.	Applicant
US5329520(A)	1994-07-01	Richardson	Applicant
US5329578(A)	1994-07-01	Brennan et al.	Applicant
US5331580(A)	1994-07-01	Miller	Applicant
US5333266(A)	1994-07-01	Boaz	Applicant
US5341374(A)	1994-08-01	Lewen et al.	Applicant
US5345446(A)	1994-09-01	Hiller et al.	Applicant
US5346611(A)	1994-09-01	Coughlin	Applicant
US5347633(A)	1994-09-01	Ashfield et al.	Applicant
US5349497(A)	1994-09-01	Hanson et al.	Applicant
US5349678(A)	1994-09-01	Morris	Applicant
US5351286(A)	1994-09-01	Nici	Applicant
US5353331(A)	1994-10-01	Emery et al.	Applicant
US5359185(A)	1994-10-01	Hanson	Applicant
US5361256(A)	1994-11-01	Doeringer et al.	Applicant
US5365524(A)	1994-11-01	Hiller et al.	Applicant
US5365546(A)	1994-11-01	Koenck et al.	Applicant
US5367566(A)	1994-11-01	Moe et al.	Applicant
US5371858(A)	1994-12-01	Miller	Applicant
US5375068(A)	1994-12-01	Palmer et al.	Applicant
US5375159(A)	1994-12-01	Williams	Applicant
US5377186(A)	1994-12-01	Wegner et al.	Applicant
US5381465(A)	1995-01-01	Carter et al.	Applicant
US5384831(A)	1995-01-01	Creswell et al.	Applicant
US5384840(A)	1995-01-01	Blatchford et al.	Applicant
US5386467(A)	1995-01-01	Ahmad	Applicant
US5390175(A)	1995-02-01	Hiller et al.	Applicant
US5390335(A)	1995-02-01	Stephan et al.	Applicant
US5392344(A)	1995-02-01	Ash et al.	Applicant
US5394436(A)	1995-02-01	Meier	Applicant
US5396542(A)	1995-03-01	Alger et al.	Applicant
US5400393(A)	1995-03-01	Knuth	Applicant
US5402478(A)	1995-03-01	Hluchyj et al.	Applicant
US5406557(A)	1995-04-01	Baudoin	Applicant
US5408237(A)	1995-04-01	Patterson et al.	Applicant
US5408382(A)	1995-04-01	Schultz	Applicant
US5410141(A)	1995-04-01	Koenck	Applicant
US5410754(A)	1995-04-01	Klotzbach et al.	Applicant
US5416842(A)	1995-05-01	Aziz	Applicant
US5418844(A)	1995-05-01	Morrisey et al.	Applicant
US5420211(A)	1995-05-01	Hughes	Applicant
US5420916(A)	1995-05-01	Sekiguchi	Applicant
US5422882(A)	1995-06-01	Hiller et al.	Applicant
US5422940(A)	1995-06-01	Endo et al.	Applicant
US5422941(A)	1995-06-01	Hasenauer et al.	Applicant
US5425028(A)	1995-06-01	Britton et al.	Applicant
US5425051(A)	1995-06-01	Mahany	Applicant
US5425085(A)	1995-06-01	Weinberger et al.	Applicant
US5425090(A)	1995-06-01	Orriss	Applicant
US5425091(A)	1995-06-01	Josephs	Applicant
US5425780(A)	1995-06-01	Christie	Applicant
US5426636(A)	1995-06-01	Hiller et al.	Applicant
US5428608(A)	1995-06-01	Freeman et al.	Applicant
US5428636(A)	1995-06-01	Meier	Applicant
US5430719(A)	1995-07-01	Weisser, Jr.	Applicant
US5430727(A)	1995-07-01	Callon	Applicant
US5434852(A)	1995-07-01	La Porta et al.	Applicant
US5434913(A)	1995-07-01	Tung et al.	Applicant
US5436957(A)	1995-07-01	McConnell	Applicant
US5436963(A)	1995-07-01	Fitzpatrick et al.	Applicant
US5440563(A)	1995-08-01	Isidoro et al.	Applicant
US5440620(A)	1995-08-01	Slusky	Applicant
US5440621(A)	1995-08-01	Castro	Applicant
US5442690(A)	1995-08-01	Nazif et al.	Applicant
US5444709(A)	1995-08-01	Riddle	Applicant
US5448633(A)	1995-09-01	Jamaleddin et al.	Applicant
US5450411(A)	1995-09-01	Heil	Applicant
US5452289(A)	1995-09-01	Sharma et al.	Applicant
US5452297(A)	1995-09-01	Hiller et al.	Applicant
US5452350(A)	1995-09-01	Reynolds et al.	Applicant
US5455821(A)	1995-10-01	Schaeffer et al.	Applicant
US5457629(A)	1995-10-01	Miller	Applicant
US5459775(A)	1995-10-01	Isono et al.	Applicant
US5461611(A)	1995-10-01	Drak et al.	Applicant
US5463677(A)	1995-10-01	Bash et al.	Applicant
US5465207(A)	1995-11-01	Boatwright	Applicant
US5466170(A)	1995-11-01	Pavek	Applicant
US5468947(A)	1995-11-01	Danielson	Applicant
US5468950(A)	1995-11-01	Hanson	Applicant
US5469496(A)	1995-11-01	Emery et al.	Applicant
US5469497(A)	1995-11-01	Pierce et al.	Applicant
US5469500(A)	1995-11-01	Satter et al.	Applicant
US5473608(A)	1995-12-01	Gagne et al.	Applicant
US5473677(A)	1995-12-01	D'Amato et al.	Applicant
US5475732(A)	1995-12-01	Pester, III	Applicant
US5475737(A)	1995-12-01	Garner et al.	Applicant
US5475748(A)	1995-12-01	Jones	Applicant
US5475817(A)	1995-12-01	Waldo et al.	Applicant
US5477531(A)	1995-12-01	McKee et al.	Applicant
US5479494(A)	1995-12-01	Clitherow	Applicant
US5481603(A)	1996-01-01	Gutierrez et al.	Applicant
US5483527(A)	1996-01-01	Doshi et al.	Applicant
US5483549(A)	1996-01-01	Weinberg et al.	Applicant
US5483586(A)	1996-01-01	Sussman	Applicant
US5483587(A)	1996-01-01	Hogan et al.	Applicant
US5483676(A)	1996-01-01	Mahany	Applicant
US5487111(A)	1996-01-01	Slusky	Applicant
US5488575(A)	1996-01-01	Danielson	Applicant
US5490247(A)	1996-02-01	Tung et al.	Applicant
US5493568(A)	1996-02-01	Sampat et al.	Applicant
US5493573(A)	1996-02-01	Kobayashi et al.	Applicant
US5495521(A)	1996-02-01	Rangachar	Applicant
US5500859(A)	1996-03-01	Sharma et al.	Applicant
US5500889(A)	1996-03-01	Baker et al.	Applicant
US5504746(A)	1996-04-01	Meier	Applicant
US5506887(A)	1996-04-01	Emery et al.	Applicant
US5506893(A)	1996-04-01	Buscher et al.	Applicant
US5511111(A)	1996-04-01	Serbetcioglu et al.	Applicant
US5513127(A)	1996-04-01	Gard et al.	Applicant
US5515303(A)	1996-05-01	Cargin, Jr.	Applicant
US5517434(A)	1996-05-01	Hanson	Applicant
US5517560(A)	1996-05-01	Greenspan	Applicant
US5521719(A)	1996-05-01	Yamada	Applicant
US5521924(A)	1996-05-01	Kakuma et al.	Applicant
US5524137(A)	1996-06-01	Rhee	Applicant
US5524145(A)	1996-06-01	Parker	Applicant
US5526353(A)	1996-06-01	Henley et al.	Applicant
US5526416(A)	1996-06-01	Dezonno et al.	Applicant
US5526489(A)	1996-06-01	Nilakantan et al.	Applicant
US5528539(A)	1996-06-01	Ong	Applicant
US5530744(A)	1996-06-01	Charalambous et al.	Applicant
US5530852(A)	1996-06-01	Mesk et al.	Applicant
US5537470(A)	1996-07-01	Lee	Applicant
US5539193(A)	1996-07-01	Gibbs	Applicant
US5539194(A)	1996-07-01	Miller	Applicant
US5539884(A)	1996-07-01	Robrock, II	Applicant
US5539886(A)	1996-07-01	Aldred et al.	Applicant
US5541398(A)	1996-07-01	Hanson	Applicant
US5541917(A)	1996-07-01	Farris	Applicant
US5541927(A)	1996-07-01	Kristol et al.	Applicant
US5541930(A)	1996-07-01	Klingman	Applicant
US5544010(A)	1996-08-01	Schultz	Applicant
US5551025(A)	1996-08-01	O'Reilly et al.	Applicant
US5551035(A)	1996-08-01	Arnold et al.	Applicant
US5555276(A)	1996-09-01	Koenck	Applicant
US5559068(A)	1996-09-01	Chen	Applicant
US5559721(A)	1996-09-01	Ishii	Applicant
US5559871(A)	1996-09-01	Smith	Applicant
US5561670(A)	1996-10-01	Hoffert et al.	Applicant
US5563882(A)	1996-10-01	Bruno et al.	Applicant
US5568645(A)	1996-10-01	Morris	Applicant
US5572583(A)	1996-11-01	Wheeler, Jr. et al.	Applicant
US5576529(A)	1996-11-01	Koenck	Applicant
US5579472(A)	1996-11-01	Keywort et al.	Applicant
US5583564(A)	1996-12-01	Rao	Applicant
US5583920(A)	1996-12-01	Wheeler, Jr.	Applicant
US5583926(A)	1996-12-01	Venier et al.	Applicant
US5583929(A)	1996-12-01	Ardon	Applicant
US5586175(A)	1996-12-01	Hogan	Applicant
US5586177(A)	1996-12-01	Farris et al.	Applicant
US5587577(A)	1996-12-01	Schultz	Applicant
US5590127(A)	1996-12-01	Bales et al.	Applicant
US5590133(A)	1996-12-01	Billstrom et al.	Applicant
US5590181(A)	1996-12-01	Hogan	Applicant
US5590346(A)	1996-12-01	West	Applicant
US5594717(A)	1997-01-01	Watanabe et al.	Applicant
US5594769(A)	1997-01-01	Pellegrino et al.	Applicant
US5594784(A)	1997-01-01	Velius	Applicant
US5594789(A)	1997-01-01	Seazholtz et al.	Applicant
US5598464(A)	1997-01-01	Hess et al.	Applicant
US5598487(A)	1997-01-01	Hacker	Applicant
US5602456(A)	1997-02-01	Cargin	Applicant
US5602854(A)	1997-02-01	Luse	Applicant
US5603085(A)	1997-02-01	Shedlo	Applicant
US5604682(A)	1997-02-01	McLaughlin et al.	Applicant
US5604737(A)	1997-02-01	Iwami et al.	Applicant
US5608446(A)	1997-03-01	Carr et al.	Applicant
US5608447(A)	1997-03-01	Farry et al.	Applicant
US5608786(A)	1997-03-01	Gordon	Applicant
US5610910(A)	1997-03-01	Focsaneanu et al.	Applicant
US5610972(A)	1997-03-01	Emery et al.	Applicant
US5610976(A)	1997-03-01	Uota et al.	Applicant
US5610977(A)	1997-03-01	Williams et al.	Applicant
US5615251(A)	1997-03-01	Hogan	Applicant
US5617343(A)	1997-04-01	Danielson	Applicant
US5617422(A)	1997-04-01	Litzenberger et al.	Applicant
US5617540(A)	1997-04-01	Civanlar et al.	Applicant
US5619555(A)	1997-04-01	Fenton et al.	Applicant
US5619557(A)	1997-04-01	Van Berkum	Applicant
US5619562(A)	1997-04-01	Maurer et al.	Applicant
US5621787(A)	1997-04-01	McKoy et al.	Applicant
US5623601(A)	1997-04-01	Vu	Applicant
US5625180(A)	1997-04-01	Hanson	Applicant
US5625404(A)	1997-04-01	Grady et al.	Applicant
US5625407(A)	1997-04-01	Biggs et al.	Applicant
US5625555(A)	1997-04-01	Davis	Applicant
US5625675(A)	1997-04-01	Katsumaru et al.	Applicant
US5625677(A)	1997-04-01	Feiertag et al.	Applicant
US5625681(A)	1997-04-01	Butler, II	Applicant
US5625682(A)	1997-04-01	Gray et al.	Applicant
US5627886(A)	1997-05-01	Bowman	Applicant
US5633916(A)	1997-05-01	Goldhagen et al.	Applicant
US5633919(A)	1997-05-01	Hogan	Applicant
US5636216(A)	1997-06-01	Fox et al.	Applicant
US5638430(A)	1997-06-01	Hogan	Applicant
US5640001(A)	1997-06-01	Danielson	Applicant
US5644471(A)	1997-07-01	Schultz	Applicant
US5646982(A)	1997-07-01	Hogan et al.	Applicant
US5651006(A)	1997-07-01	Fujino et al.	Applicant
US5652787(A)	1997-07-01	O'Kelly	Applicant
US5654957(A)	1997-08-01	Koyama	Applicant
US5657250(A)	1997-08-01	Park et al.	Applicant
US5657317(A)	1997-08-01	Mahany	Applicant
US5661197(A)	1997-08-01	Villiger et al.	Applicant
US5661782(A)	1997-08-01	Bartholomew et al.	Applicant
US5661790(A)	1997-08-01	Hsu	Applicant
US5661792(A)	1997-08-01	Akinpelu et al.	Applicant
US5663208(A)	1997-09-01	Martin	Applicant
US5664005(A)	1997-09-01	Emery et al.	Applicant
US5664102(A)	1997-09-01	Faynberg	Applicant
US5668857(A)	1997-09-01	McHale	Applicant
US5669062(A)	1997-09-01	Olds et al.	Applicant
US5671436(A)	1997-09-01	Morrison	Applicant
US5672860(A)	1997-09-01	Miller	Applicant
US5673031(A)	1997-09-01	Meier	Applicant
US5673263(A)	1997-09-01	Basso et al.	Applicant
US5675507(A)	1997-10-01	Bobo, II	Applicant
US5675741(A)	1997-10-01	Aggarwal et al.	Applicant
US5679943(A)	1997-10-01	Koenck	Applicant
US5680392(A)	1997-10-01	Semaan	Applicant
US5680442(A)	1997-10-01	Bartholomew et al.	Applicant
US5680446(A)	1997-10-01	Fleischer et al.	Applicant
US5680633(A)	1997-10-01	Koenck	Applicant
US5682379(A)	1997-10-01	Mahany	Applicant
US5687167(A)	1997-11-01	Bertin et al.	Applicant
US5689550(A)	1997-11-01	Garson et al.	Applicant
US5689553(A)	1997-11-01	Ahuja et al.	Applicant
US5692039(A)	1997-11-01	Brankley et al.	Applicant
US5694318(A)	1997-12-01	Miller	Applicant
US5694463(A)	1997-12-01	Christie et al.	Applicant
US5696903(A)	1997-12-01	Mahany	Applicant
US5699089(A)	1997-12-01	Murray	Applicant
US5699352(A)	1997-12-01	Kriete et al.	Applicant
US5699528(A)	1997-12-01	Hogan	Applicant
US5701295(A)	1997-12-01	Bales et al.	Applicant
US5701465(A)	1997-12-01	Baugher et al.	Applicant
US5703935(A)	1997-12-01	Raissyan et al.	Applicant
US5703942(A)	1997-12-01	Pinard et al.	Applicant
US5706286(A)	1998-01-01	Reiman et al.	Applicant
US5708680(A)	1998-01-01	Gollnick	Applicant
US5708833(A)	1998-01-01	Kinney	Applicant
US5710728(A)	1998-01-01	Danielson	Applicant
US5710884(A)	1998-01-01	Dedrick	Applicant
US5712903(A)	1998-01-01	Bartholomew et al.	Applicant
US5712906(A)	1998-01-01	Grady et al.	Applicant
US5712907(A)	1998-01-01	Wegner et al.	Applicant
US5712908(A)	1998-01-01	Brinkman et al.	Applicant
US5719854(A)	1998-02-01	Choudhury et al.	Applicant
US5722067(A)	1998-02-01	Fougnies	Applicant
US5724355(A)	1998-03-01	Bruno et al.	Applicant
US5724406(A)	1998-03-01	Juster	Applicant
US5724412(A)	1998-03-01	Srinivasan	Applicant
US5726984(A)	1998-03-01	Kubler et al.	Applicant
US5727002(A)	1998-03-01	Miller et al.	Applicant
US5727129(A)	1998-03-01	Barrett et al.	Applicant
US5729544(A)	1998-03-01	Lev et al.	Applicant
US5729599(A)	1998-03-01	Plomondon et al.	Applicant
US5732078(A)	1998-03-01	Arango	Applicant
US5732213(A)	1998-03-01	Gessel et al.	Applicant
US5737333(A)	1998-04-01	Civanlar et al.	Applicant
US5737395(A)	1998-04-01	Irribarren	Applicant
US5737404(A)	1998-04-01	Segal	Applicant
US5737414(A)	1998-04-01	Walker et al.	Applicant
US5740164(A)	1998-04-01	Liron	Applicant
US5740366(A)	1998-04-01	Mahany	Applicant
US5742596(A)	1998-04-01	Baratz et al.	Applicant
US5742668(A)	1998-04-01	Pepe et al.	Applicant
US5742670(A)	1998-04-01	Bennett	Applicant
US5742675(A)	1998-04-01	Kilander et al.	Applicant
US5742905(A)	1998-04-01	Pepe et al.	Applicant
US5744533(A)	1998-04-01	Iwamoto et al.	Applicant
US5747785(A)	1998-05-01	Miller	Applicant
US5747786(A)	1998-05-01	Cargin, Jr.	Applicant
US5748468(A)	1998-05-01	Notenboom et al.	Applicant
US5748619(A)	1998-05-01	Meier	Applicant
US5751706(A)	1998-05-01	Land et al.	Applicant
US5751707(A)	1998-05-01	Voit et al.	Applicant
US5751961(A)	1998-05-01	Smyk	Applicant
US5754639(A)	1998-05-01	Flockhart et al.	Applicant
US5754641(A)	1998-05-01	Voit et al.	Applicant
US5757784(A)	1998-05-01	Liebowitz et al.	Applicant
US5758281(A)	1998-05-01	Emery et al.	Applicant
US5761294(A)	1998-06-01	Shaffer et al.	Applicant
US5763867(A)	1998-06-01	Main	Applicant
US5764741(A)	1998-06-01	Barak	Applicant
US5768513(A)	1998-06-01	Kuthyar et al.	Applicant
US5774530(A)	1998-06-01	Montgomery et al.	Applicant
US5774533(A)	1998-06-01	Patel	Applicant
US5774535(A)	1998-06-01	Castro	Applicant
US5774660(A)	1998-06-01	Brendel et al.	Applicant
US5774695(A)	1998-06-01	Autrey et al.	Applicant
US5778313(A)	1998-07-01	Fougnies	Applicant
US5781550(A)	1998-07-01	Templin et al.	Applicant
US5781620(A)	1998-07-01	Montgomery et al.	Applicant
US5781624(A)	1998-07-01	Mitra et al.	Applicant
US5784617(A)	1998-07-01	Greenstein et al.	Applicant
US5787160(A)	1998-07-01	Chaney et al.	Applicant
US5790172(A)	1998-08-01	Imanaka	Applicant
US5790536(A)	1998-08-01	Mahany	Applicant
US5790548(A)	1998-08-01	Sistani zadeh et al.	Applicant
US5790806(A)	1998-08-01	Koperda	Examiner
US5793762(A)	1998-08-01	Penners et al.	Applicant
US5793763(A)	1998-08-01	Mayes et al.	Applicant
US5793771(A)	1998-08-01	Darland et al.	Applicant
US5796790(A)	1998-08-01	Brunner	Applicant
US5799072(A)	1998-08-01	Vulcan et al.	Applicant
US5799156(A)	1998-08-01	Hogan	Applicant
US5802502(A)	1998-09-01	Gell et al.	Applicant
US5802510(A)	1998-09-01	Jones	Applicant
US5802513(A)	1998-09-01	Bowie, III	Applicant
US5804805(A)	1998-09-01	Koenck	Applicant
US5805474(A)	1998-09-01	Danielson	Applicant
US5805587(A)	1998-09-01	Norris	Applicant
US5805682(A)	1998-09-01	Voit et al.	Applicant
US5805807(A)	1998-09-01	Hanson	Applicant
US5809128(A)	1998-09-01	McMullin	Applicant
US5812534(A)	1998-09-01	Davis et al.	Applicant
US5812639(A)	1998-09-01	Bartholomew et al.	Applicant
US5812795(A)	1998-09-01	Horovitz et al.	Applicant
US5812834(A)	1998-09-01	Suzuki	Applicant
US5812865(A)	1998-09-01	Theimer et al.	Applicant
US5818921(A)	1998-10-01	Vander Meiden et al.	Applicant
US5825780(A)	1998-10-01	Christie	Applicant
US5825862(A)	1998-10-01	Voit et al.	Applicant
US5825863(A)	1998-10-01	Walker	Applicant
US5825869(A)	1998-10-01	Brooks et al.	Applicant
US5826268(A)	1998-10-01	Schaefer et al.	Applicant
US5828737(A)	1998-10-01	Sawyer	Applicant
US5828740(A)	1998-10-01	Khuc et al.	Applicant
US5828844(A)	1998-10-01	Civanlar et al.	Applicant
US5832197(A)	1998-11-01	Houji	Applicant
US5834753(A)	1998-11-01	Danielson	Applicant
US5835723(A)	1998-11-01	Andrews et al.	Applicant
US5838665(A)	1998-11-01	Kahn et al.	Applicant
US5838682(A)	1998-11-01	Dekelbaum et al.	Applicant
US5838686(A)	1998-11-01	Ozkan	Applicant
US5838970(A)	1998-11-01	Thomas	Applicant
US5841764(A)	1998-11-01	Roderique et al.	Applicant
US5844893(A)	1998-12-01	Gollnick	Applicant
US5844896(A)	1998-12-01	Marks et al.	Applicant
US5845267(A)	1998-12-01	Ronen	Applicant
US5848143(A)	1998-12-01	Andrews et al.	Applicant
US5850358(A)	1998-12-01	Danielson	Applicant
US5850433(A)	1998-12-01	Rondeau	Applicant
US5854833(A)	1998-12-01	Hogan	Applicant
US5854975(A)	1998-12-01	Fougnies	Applicant
US5862171(A)	1999-01-01	Mahany	Applicant
US5864604(A)	1999-01-01	Moen et al.	Applicant
US5864610(A)	1999-01-01	Ronen	Applicant
US5867495(A)	1999-02-01	Elliott et al.	Applicant
US5867562(A)	1999-02-01	Scherer	Applicant
US5867566(A)	1999-02-01	Hogan	Applicant
US5870565(A)	1999-02-01	Glitho	Applicant
US5873099(A)	1999-02-01	Hogan	Applicant
US5878126(A)	1999-03-01	Velamuri et al.	Applicant
US5878130(A)	1999-03-01	Andrews et al.	Applicant
US5878212(A)	1999-03-01	Civanlar et al.	Applicant
US5881134(A)	1999-03-01	Foster et al.	Applicant
US5883891(A)	1999-03-01	Williams et al.	Applicant
US5884032(A)	1999-03-01	Bateman et al.	Applicant
US5888087(A)	1999-03-01	Hanson	Applicant
US5889774(A)	1999-03-01	Mirashrafi et al.	Applicant
US5892754(A)	1999-04-01	Kompella et al.	Applicant
US5892822(A)	1999-04-01	Gottlieb et al.	Examiner
US5892971(A)	1999-04-01	Danielson	Applicant
US5895431(A)	1999-04-01	Miller	Applicant
US5895906(A)	1999-04-01	Danielson	Applicant
US5898668(A)	1999-04-01	Shaffer	Applicant
US5898673(A)	1999-04-01	Riggan et al.	Applicant
US5901140(A)	1999-05-01	Van As et al.	Applicant
US5903558(A)	1999-05-01	Jones et al.	Applicant
US5905736(A)	1999-05-01	Ronen et al.	Applicant
US5907547(A)	1999-05-01	Foladare et al.	Applicant
US5910946(A)	1999-06-01	Csapo	Applicant
US5912887(A)	1999-06-01	Sehgal	Applicant
US5914481(A)	1999-06-01	Danielson	Applicant
US5915001(A)	1999-06-01	Uppaluru	Applicant
US5915005(A)	1999-06-01	He	Applicant
US5915008(A)	1999-06-01	Dulman	Applicant
US5915012(A)	1999-06-01	Miloslavsky	Applicant
US5917175(A)	1999-06-01	Miller	Applicant
US5917424(A)	1999-06-01	Goldman et al.	Applicant
US5918179(A)	1999-06-01	Foladare et al.	Applicant
US5923659(A)	1999-07-01	Curry et al.	Applicant
US5926482(A)	1999-07-01	Christie	Applicant
US5928292(A)	1999-07-01	Miller	Applicant
US5930343(A)	1999-07-01	Vasquez	Applicant
US5930700(A)	1999-07-01	Pepper	Applicant
US5933425(A)	1999-08-01	Iwata	Applicant
US5936958(A)	1999-08-01	Soumiya et al.	Applicant
US5937045(A)	1999-08-01	Yaoya et al.	Applicant
US5940479(A)	1999-08-01	Guy et al.	Applicant
US5940598(A)	1999-08-01	Strauss et al.	Applicant
US5940616(A)	1999-08-01	Wang	Applicant
US5940771(A)	1999-08-01	Gollnick	Applicant
US5944795(A)	1999-08-01	Civanlar	Applicant
US5946299(A)	1999-08-01	Blonder	Applicant
US5946386(A)	1999-08-01	Rogers et al.	Applicant
US5949056(A)	1999-09-01	White	Applicant
US5949776(A)	1999-09-01	Mahany	Applicant
US5949869(A)	1999-09-01	Sink	Applicant
US5953322(A)	1999-09-01	Kimball	Applicant
US5953338(A)	1999-09-01	Ma et al.	Applicant
US5953504(A)	1999-09-01	Sokal et al.	Applicant
US5953651(A)	1999-09-01	Lu et al.	Applicant
US5956391(A)	1999-09-01	Melen et al.	Applicant
US5956482(A)	1999-09-01	Agraharam et al.	Applicant
US5956697(A)	1999-09-01	Usui	Applicant
US5958016(A)	1999-09-01	Chang et al.	Applicant
US5958052(A)	1999-09-01	Bellovin et al.	Applicant
US5959998(A)	1999-09-01	Takahashi et al.	Applicant
US5966431(A)	1999-10-01	Reiman et al.	Applicant
US5966434(A)	1999-10-01	Schafer et al.	Applicant
US5969321(A)	1999-10-01	Danielson	Applicant
US5970065(A)	1999-10-01	Miloslavsky	Applicant
US5970477(A)	1999-10-01	Roden	Applicant
US5974043(A)	1999-10-01	Solomon	Applicant
US5974052(A)	1999-10-01	Johnson et al.	Applicant
US5978569(A)	1999-11-01	Traeger	Applicant
US5978840(A)	1999-11-01	Nguyen et al.	Applicant
US5979768(A)	1999-11-01	Koenck	Applicant
US5982774(A)	1999-11-01	Foladare et al.	Applicant
US5987108(A)	1999-11-01	Jagadish et al.	Applicant
US5987499(A)	1999-11-01	Morris	Applicant
US5991291(A)	1999-11-01	Asai et al.	Applicant
US5991292(A)	1999-11-01	Focsaneanu et al.	Applicant
US5991301(A)	1999-11-01	Christie	Applicant
US5991308(A)	1999-11-01	Furhmann et al.	Applicant
US5991864(A)	1999-11-01	Kinney	Applicant
US5995503(A)	1999-11-01	Crawley et al.	Applicant
US5995606(A)	1999-11-01	Civanlar et al.	Applicant
US5999524(A)	1999-12-01	Corbalis et al.	Applicant
US5999525(A)	1999-12-01	Krishnaswamy	Applicant
US6005926(A)	1999-12-01	Mashinsky	Applicant
US6006100(A)	1999-12-01	Koenck	Applicant
US6006253(A)	1999-12-01	Kumar et al.	Applicant
US6011975(A)	2000-01-01	Emery et al.	Applicant
US6012088(A)	2000-01-01	Li et al.	Applicant
US6014379(A)	2000-01-01	White et al.	Applicant
US6014687(A)	2000-01-01	Watanabe et al.	Applicant
US6016307(A)	2000-01-01	Kaplan et al.	Applicant
US6016343(A)	2000-01-01	Hogan	Applicant
US6018360(A)	2000-01-01	Stewart et al.	Applicant
US6018567(A)	2000-01-01	Dulman	Applicant
US6021126(A)	2000-02-01	White et al.	Applicant
US6021263(A)	2000-02-01	Kujoory et al.	Applicant
US6023147(A)	2000-02-01	Cargin	Applicant
US6023474(A)	2000-02-01	Christie	Applicant
US6026087(A)	2000-02-01	Mirashrafi et al.	Applicant
US6026091(A)	2000-02-01	Christie	Applicant
US6028858(A)	2000-02-01	Rivers et al.	Applicant
US6029062(A)	2000-02-01	Hanson	Examiner
US6029261(A)	2000-02-01	Christie	Applicant
US6031840(A)	2000-02-01	Christie et al.	Applicant
US6035028(A)	2000-03-01	Ward et al.	Applicant
US6036093(A)	2000-03-01	Schultz	Applicant
US6041109(A)	2000-03-01	Cardy et al.	Applicant
US6041117(A)	2000-03-01	Androski et al.	Applicant
US6044081(A)	2000-03-01	Bell et al.	Applicant
US6046992(A)	2000-04-01	Meier	Applicant
US6047051(A)	2000-04-01	Ginzboorg et al.	Applicant
US6047326(A)	2000-04-01	Kilkki	Applicant
US6049545(A)	2000-04-01	Stephenson et al.	Applicant
US6049813(A)	2000-04-01	Danielson	Applicant
US6052445(A)	2000-04-01	Bashoura et al.	Applicant
US6052450(A)	2000-04-01	Allison et al.	Applicant
US6058000(A)	2000-05-01	Koenck	Applicant
US6064653(A)	2000-05-01	Farris	Applicant
US6069890(A)	2000-05-01	White et al.	Applicant
US6075783(A)	2000-06-01	Voit	Applicant
US6078582(A)	2000-06-01	Curry et al.	Applicant
US6078943(A)	2000-06-01	Yu	Applicant
US6081525(A)	2000-06-01	Christie	Applicant
US6084867(A)	2000-07-01	Meier	Applicant
US6084953(A)	2000-07-01	Bardenheuer et al.	Examiner
US6088431(A)	2000-07-01	LaDue	Applicant
US6097804(A)	2000-08-01	Gilbert et al.	Applicant
US6098094(A)	2000-08-01	Barnhouse et al.	Applicant
US6101182(A)	2000-08-01	Sistanizadeh et al.	Applicant
US6104645(A)	2000-08-01	Ong	Applicant
US6104704(A)	2000-08-01	Buhler et al.	Applicant
US6104711(A)	2000-08-01	Voit	Applicant
US6108341(A)	2000-08-01	Christie	Applicant
US6108704(A)	2000-08-01	Hutton et al.	Applicant
US6112206(A)	2000-08-01	Morris	Applicant
US6115458(A)	2000-09-01	Taskett	Examiner
US6115737(A)	2000-09-01	Ely et al.	Applicant
US6118936(A)	2000-09-01	Lauer et al.	Applicant
US6122255(A)	2000-09-01	Bartholomew et al.	Applicant
US6125113(A)	2000-09-01	Farris et al.	Applicant
US6125126(A)	2000-09-01	Hallenstal	Applicant
US6128304(A)	2000-10-01	Gardell et al.	Applicant
US6131121(A)	2000-10-01	Mattaway	Applicant
US6134235(A)	2000-10-01	Goldman et al.	Applicant
US6134433(A)	2000-10-01	Joong et al.	Applicant
US6134530(A)	2000-10-01	Bunting et al.	Applicant
US6137792(A)	2000-10-01	Jonas et al.	Applicant
US6137869(A)	2000-10-01	Voit et al.	Examiner
US6141404(A)	2000-10-01	Westerlage et al.	Applicant
US6141412(A)	2000-10-01	Smith et al.	Applicant
US6144647(A)	2000-11-01	Lopez-Torres	Applicant
US6144661(A)	2000-11-01	Katsube et al.	Applicant
US6144667(A)	2000-11-01	Doshi et al.	Applicant
US6144976(A)	2000-11-01	Silva	Applicant
US6149062(A)	2000-11-01	Danielson	Applicant
US6154445(A)	2000-11-01	Farris et al.	Applicant
US6154777(A)	2000-11-01	Ebrahim	Applicant
US6157621(A)	2000-12-01	Brown et al.	Applicant
US6157636(A)	2000-12-01	Voit et al.	Applicant
US6157648(A)	2000-12-01	Voit et al.	Applicant
US6157823(A)	2000-12-01	Fougnies	Applicant
US6169735(B1)	2001-01-01	Alle et al.	Applicant
US6175618(B1)	2001-01-01	Shah et al.	Applicant
US6181690(B1)	2001-01-01	Civanlar	Applicant
US6181695(B1)	2001-01-01	Curry et al.	Applicant
US6181703(B1)	2001-01-01	Christie	Applicant
US6185184(B1)	2001-02-01	Mattaway	Applicant
US6185198(B1)	2001-02-01	LaDue	Applicant
US6188677(B1)	2001-02-01	Oyama et al.	Applicant
US6192050(B1)	2001-02-01	Stovall	Applicant
US6192400(B1)	2001-02-01	Hanson	Applicant
US6195425(B1)	2001-02-01	Farris et al.	Applicant
US6198738(B1)	2001-03-01	Chang et al.	Applicant
US6201812(B1)	2001-03-01	Christie	Applicant
US6205139(B1)	2001-03-01	Voit	Applicant
US6212162(B1)	2001-04-01	Horlin	Applicant
US6212193(B1)	2001-04-01	Christie	Applicant
US6215790(B1)	2001-04-01	Voit et al.	Applicant
US6222919(B1)	2001-04-01	Hollatz et al.	Applicant
US6226287(B1)	2001-05-01	Brady	Applicant
US6226678(B1)	2001-05-01	Mattaway	Applicant
US6230203(B1)	2001-05-01	Koperda et al.	Examiner
US6233318(B1)	2001-05-01	Picard et al.	Applicant
US6233604(B1)	2001-05-01	Van Horne et al.	Applicant
US6236851(B1)	2001-05-01	Fougnies	Applicant
US6240091(B1)	2001-05-01	Ginzboorg et al.	Applicant
US6243373(B1)	2001-06-01	Turock	Applicant
US6243374(B1)	2001-06-01	White	Applicant
US6252869(B1)	2001-06-01	Silverman	Applicant
US6260067(B1)	2001-07-01	Barnhouse et al.	Applicant
US6263372(B1)	2001-07-01	Hogan	Applicant
US6266685(B1)	2001-07-01	Danielson	Applicant
US6278693(B1)	2001-08-01	Aldred et al.	Applicant
US6278704(B1)	2001-08-01	Creamer et al.	Applicant
US6279038(B1)	2001-08-01	Hogan	Applicant
US6282192(B1)	2001-08-01	Murphy et al.	Applicant
US6282281(B1)	2001-08-01	Low	Applicant
US6282284(B1)	2001-08-01	Dezonno et al.	Applicant
US6282574(B1)	2001-08-01	Voit et al.	Applicant
US6285745(B1)	2001-09-01	Bartholomew et al.	Applicant
US6289010(B1)	2001-09-01	Voit et al.	Applicant
US6292478(B1)	2001-09-01	Farris	Applicant
US6292479(B1)	2001-09-01	Bartholomew et al.	Applicant
US6292481(B1)	2001-09-01	Voit et al.	Applicant
US6295292(B1)	2001-09-01	Voit et al.	Applicant
US6298057(B1)	2001-10-01	Guy	Applicant
US6298062(B1)	2001-10-01	Gardell et al.	Applicant
US6298064(B1)	2001-10-01	Christie	Applicant
US6298120(B1)	2001-10-01	Civanlar et al.	Applicant
US6301609(B1)	2001-10-01	Aravamudan et al.	Applicant
US6304567(B1)	2001-10-01	Rosenburg	Applicant
US6310873(B1)	2001-10-01	Rainis et al.	Applicant
US6310941(B1)	2001-10-01	Crutcher et al.	Applicant
US6314103(B1)	2001-11-01	Medhat et al.	Applicant
US6324264(B1)	2001-11-01	Wiener et al.	Applicant
US6327258(B1)	2001-12-01	Deschaine et al.	Applicant
US6330250(B1)	2001-12-01	Curry et al.	Applicant
US6332023(B1)	2001-12-01	Porter et al.	Applicant
US6335927(B1)	2002-01-01	Elliott et al.	Examiner
US6343115(B1)	2002-01-01	Foladare et al.	Applicant
US6347085(B2)	2002-02-01	Kelly	Applicant
US6359880(B1)	2002-03-01	Curry	Applicant
US6363065(B1)	2002-03-01	Thornton et al.	Applicant
US6373929(B1)	2002-04-01	Johnson et al.	Applicant
US6374302(B1)	2002-04-01	Galasso et al.	Applicant
US6375344(B1)	2002-04-01	Hanson	Applicant
US6381321(B1)	2002-04-01	Brown et al.	Applicant
US6385191(B1)	2002-05-01	Coffman et al.	Applicant
US6385193(B1)	2002-05-01	Civanlar et al.	Applicant
US6400702(B1)	2002-06-01	Meier	Applicant
US6407991(B1)	2002-06-01	Meier	Applicant
US6430195(B1)	2002-08-01	Christie	Applicant
US6430275(B1)	2002-08-01	Voit et al.	Applicant
US6438218(B1)	2002-08-01	Farris	Applicant
US6449259(B1)	2002-09-01	Allain et al.	Applicant
US6449356(B1)	2002-09-01	Dezonno	Applicant
US6456617(B1)	2002-09-01	Oda et al.	Applicant
US6480588(B1)	2002-11-01	Donovan	Applicant
US6493353(B2)	2002-12-01	Kelly et al.	Applicant
US6498788(B1)	2002-12-01	Emilsson et al.	Applicant
US6513066(B1)	2003-01-01	Hutton	Applicant
US6529516(B1)	2003-03-01	Parzych	Applicant
US6539015(B2)	2003-03-01	Voit et al.	Applicant
US6539077(B1)	2003-03-01	Ranalli et al.	Applicant
US6542497(B1)	2003-04-01	Curry	Applicant
US6546003(B1)	2003-04-01	Farris	Applicant
US6574216(B1)	2003-06-01	Farris et al.	Applicant
US6574681(B1)	2003-06-01	White	Applicant
US6584093(B1)	2003-06-01	Salama et al.	Applicant
US6594254(B1)	2003-07-01	Kelly	Applicant
US6600733(B2)	2003-07-01	Deng	Applicant
US6600735(B1)	2003-07-01	Iwama et al.	Applicant
US6614768(B1)	2003-09-01	Mahany	Applicant
US6614781(B1)	2003-09-01	Elliott	Applicant
US6621942(B1)	2003-09-01	Hacker	Applicant
US6625170(B1)	2003-09-01	Curry et al.	Applicant
US6633846(B1)	2003-10-01	Bennett et al.	Applicant
US6643362(B2)	2003-11-01	Hogan	Applicant
US6654357(B1)	2003-11-01	Wiedeman	Applicant
US6671285(B1)	2003-12-01	Kirkby et al.	Applicant
US6678718(B1)	2004-01-01	Khouri et al.	Applicant
US6681994(B1)	2004-01-01	Koenck	Applicant
US6687738(B1)	2004-02-01	Hutton	Applicant
US6688523(B1)	2004-02-01	Koenck	Applicant
US6690788(B1)	2004-02-01	Bauer et al.	Applicant
US6694359(B1)	2004-02-01	Morris	Applicant
US6701365(B1)	2004-03-01	Hutton	Applicant
US6704287(B1)	2004-03-01	Moharram	Applicant
US6711241(B1)	2004-03-01	White et al.	Applicant
US6714559(B1)	2004-03-01	Meier	Applicant
US6714983(B1)	2004-03-01	Koenck	Applicant
US6754181(B1)	2004-06-01	Elliott et al.	Applicant
US6760429(B1)	2004-07-01	Hung et al.	Applicant
US6775519(B1)	2004-08-01	Wiedeman et al.	Applicant
US6792256(B1)	2004-09-01	Kinney	Applicant
US6810033(B2)	2004-10-01	Derks	Applicant
US6823384(B1)	2004-11-01	Wilson et al.	Applicant
US6826165(B1)	2004-11-01	Meier	Applicant
US6829645(B1)	2004-12-01	Hutton	Applicant
US6839340(B1)	2005-01-01	Voit et al.	Applicant
US6870827(B1)	2005-03-01	Voit et al.	Applicant
US6885678(B2)	2005-04-01	Curry et al.	Applicant
US6895419(B1)	2005-05-01	Cargin	Applicant
US6910632(B2)	2005-06-01	Koerck	Applicant
US6925054(B1)	2005-08-01	Atterton et al.	Applicant
US6990090(B2)	2006-01-01	Meier	Applicant
US7012898(B1)	2006-03-01	Farris et al.	Applicant
US7013001(B1)	2006-03-01	Felger et al.	Applicant
US7079534(B1)	2006-07-01	Medhat	Applicant
US7085362(B1)	2006-08-01	Christie	Applicant
US7088705(B2)	2006-08-01	Curry	Applicant
US7092379(B1)	2006-08-01	Singh et al.	Applicant
US7120319(B2)	2006-10-01	Danielson	Applicant
US7149208(B2)	2006-12-01	Mattaway	Applicant
US7170887(B2)	2007-01-01	Rosenberg	Applicant
US7206592(B1)	2007-04-01	Gollnick	Applicant
US7236575(B2)	2007-06-01	Kim et al.	Applicant
US7274662(B1)	2007-09-01	Kalmanek, Jr. et al.	Applicant
US7286562(B1)	2007-10-01	Vargo et al.	Applicant
US7295830(B2)	2007-11-01	Lippelt	Examiner
US7359972(B2)	2008-04-01	Jorgensen	Applicant
US7492886(B1)	2009-02-01	Kalmanek, Jr. et al.	Applicant
US7502339(B1)	2009-03-01	Pirkola et al.	Applicant
US2002/0064149(A1)	2002-05-01	Elliott	Applicant
US2002/0067739(A1)	2002-06-01	Wilkes et al.	Applicant
US2002/0083166(A1)	2002-06-01	Dugan et al.	Applicant
US2002/0114324(A1)	2002-08-01	Low et al.	Applicant
US2002/0159461(A1)	2002-10-01	Hamamoto et al.	Applicant
US2003/0078006(A1)	2003-04-01	Mahany	Applicant
US2003/0112767(A1)	2003-06-01	Meier	Applicant
US2003/0169767(A1)	2003-09-01	Christie	Applicant
US2003/0189941(A1)	2003-10-01	Christie	Applicant
US2003/0193933(A1)	2003-10-01	Jonas	Applicant
US2003/0198218(A1)	2003-10-01	Farris et al.	Applicant
US2003/0198335(A1)	2003-10-01	Porter et al.	Applicant
US2004/0005046(A1)	2004-01-01	Deo et al.	Applicant
US2004/0018851(A1)	2004-01-01	Koenck	Applicant
US2004/0023651(A1)	2004-02-01	Gollnick	Applicant
US2004/0038717(A1)	2004-02-01	Mahany	Applicant
US2004/0039846(A1)	2004-02-01	Goss et al.	Applicant
US2004/0044667(A1)	2004-03-01	Mahany	Applicant
US2004/0073933(A1)	2004-04-01	Gollnick	Applicant
US2004/0090952(A1)	2004-05-01	Kubler	Applicant
US2004/0093363(A1)	2004-05-01	Cargin	Applicant
US2004/0114567(A1)	2004-06-01	Kubler	Applicant
US2004/0125753(A1)	2004-07-01	Mahany	Applicant
US2004/0131018(A1)	2004-07-01	Johnson et al.	Applicant
US2004/0145775(A1)	2004-07-01	Kubler	Applicant
US2004/0146020(A1)	2004-07-01	Kubler	Applicant
US2004/0146037(A1)	2004-07-01	Kubler	Applicant
US2004/0151150(A1)	2004-08-01	Kubler	Applicant
US2004/0151151(A1)	2004-08-01	Kubler	Applicant
US2004/0151164(A1)	2004-08-01	Kubler	Applicant
US2004/0160912(A1)	2004-08-01	Kubler	Applicant
US2004/0160913(A1)	2004-08-01	Kubler	Applicant
US2004/0162889(A1)	2004-08-01	Morris	Applicant
US2004/0165573(A1)	2004-08-01	Kubler	Applicant
US2004/0165793(A1)	2004-08-01	Hacker	Applicant
US2004/0166895(A1)	2004-08-01	Koenck	Applicant
US2004/0169583(A1)	2004-09-01	Meier	Applicant
US2004/0174841(A1)	2004-09-01	Kubler	Applicant
US2004/0174842(A1)	2004-09-01	Kubler	Applicant
US2004/0174843(A1)	2004-09-01	Kubler	Applicant
US2004/0203834(A1)	2004-10-01	Mahany	Applicant
US2004/0246940(A1)	2004-12-01	Kubler	Applicant
US2004/0264442(A1)	2004-12-01	Kubler	Applicant
US2005/0008002(A1)	2005-01-01	Kubler	Applicant
US2005/0013266(A1)	2005-01-01	Kubler	Applicant
US2005/0021713(A1)	2005-01-01	Dugan et al.	Applicant
US2005/0036467(A1)	2005-02-01	Kubler	Applicant
US2005/0078647(A1)	2005-04-01	Meier	Applicant
US2005/0083872(A1)	2005-04-01	Kubler	Applicant
US2005/0087603(A1)	2005-04-01	Mahany	Applicant
US2005/0191989(A1)	2005-09-01	Plush et al.	Applicant
US2005/0195859(A1)	2005-09-01	Mahany	Applicant
US2005/0232213(A1)	2005-10-01	Meier	Applicant
US2005/0242192(A1)	2005-11-01	Koenck	Applicant
US2005/0254475(A1)	2005-11-01	Kubler	Applicant
US2006/0007951(A1)	2006-01-01	Meier	Applicant
US2006/0062240(A1)	2006-03-01	Meier	Applicant
US2006/0131420(A1)	2006-06-01	Koenck	Applicant
US2006/0233161(A1)	2006-10-01	Koenck	Applicant
US2006/0251226(A1)	2006-11-01	Hogan	Applicant
US2006/0268806(A1)	2006-11-01	Meier	Applicant
US2006/0268807(A1)	2006-11-01	Meier	Applicant
US2006/0274732(A1)	2006-12-01	Allen, Jr. et al.	Applicant
US2006/0274735(A1)	2006-12-01	Allen, Jr. et al.	Applicant
US2006/0291752(A1)	2006-12-01	Hacker	Applicant
US2007/0001007(A1)	2007-01-01	Koenck	Applicant
US2007/0007353(A1)	2007-01-01	Danielson	Applicant
US2007/0065046(A1)	2007-03-01	Hacker	Applicant
US2007/0076687(A1)	2007-04-01	Low et al.	Applicant
US2007/0086445(A1)	2007-04-01	Mattaway	Applicant
US2007/0121529(A1)	2007-05-01	Meier	Applicant
US2007/0121591(A1)	2007-05-01	Donovan	Applicant
US2007/0201515(A1)	2007-08-01	Lewis	Applicant
US2007/0206576(A1)	2007-09-01	Radulovic	Applicant
US2007/0263644(A1)	2007-11-01	Christie et al.	Applicant
US2008/0013531(A1)	2008-01-01	Elliott	Applicant
US2008/0063161(A1)	2008-03-01	Joyce et al.	Applicant
US2009/0022147(A1)	2009-01-01	Farris	Applicant
EP235257	1987-02-01		Applicant
EP235257	1987-09-01		Applicant
EP335562	1989-04-01		Applicant
EP365885	1990-05-01		Applicant
EP381365	1990-08-01		Applicant
EP559979	1993-09-01		Applicant
EP729281	1995-02-01		Applicant
EP767568	1995-10-01		Applicant
EP802690	1996-04-01		Applicant
EP781016	1997-06-01		Applicant
EP812089	1997-12-01		Applicant
EP823809	1998-02-01		Applicant
EP722237	2007-11-01		Applicant
JP9-168051	1997-06-01		Applicant
JP9-168063	1997-06-01		Applicant
JP9-168064	1997-06-01		Applicant
JP9-168065	1997-06-01		Applicant
JP9-172459	1997-06-01		Applicant
JP9-172462	1997-06-01		Applicant
WO91/07839	1991-05-01		Applicant
WO94/11813	1994-05-01		Applicant
WO95/22221	1995-08-01		Applicant
WO95/29564	1995-11-01		Applicant
WO96/20448	1996-07-01		Applicant
WO96/20553	1996-07-01		Applicant
WO96/32800	1996-10-01		Applicant
WO96/34341	1996-10-01		Applicant
WO96/38018	1996-11-01		Applicant
WO97/14238	1997-04-01		Applicant
WO97/20424	1997-06-01		Applicant
WO97/22211	1997-06-01		Applicant
WO97/23078	1997-06-01		Applicant
WO97/28628	1997-08-01		Applicant
WO97/33412	1997-09-01		Applicant
WO98/12860	1998-03-01		Applicant
WO98/23080	1998-05-01		Applicant
WO98/34391	1998-08-01		Applicant

Non-Patent Literature (358)

Cady et al., “Mastering the Internet”, Sybex Inc., Alameda, CA 1994, ISBN 94-69309.Applicant
U.S. Appl. No. 60/023,891, filed Aug. 16, 1996.Applicant
Handley et al., “SIP: Session Initiation Protocol”, Internet Engineering Task Force, Internet Draft, Jul. 31, 1997, draft-ietf-mmusic-sip-03.txt, Jul. 31, 1997.Applicant
“Free World Dialup Beta 2.0a Client,” Feb. 12, 1996.Applicant
Kahane et al., “VocalTec IP Forum Contribution”, VocalTec Inc., Seattle, WA, Jan. 15, 1997.Applicant
Kahane et al., “Call Management Agent System Specification” VoIP Forum Technical Committee, Aug. 14, 199.Applicant
IMTC Voice over IP Forum Service Interoperability Implementation Agreement, Draft 0.91, Document VoIP-008, Jan. 13, 1997.Applicant
Sebestyn, I., ITU Telecommunication Standardization Sector, Study Group 15, Q;2&3/15 Rapporteur Meeting, Document AVC-1086, v1, Dec. 5, 1996.Applicant
Oppen et al., “The Clearinghouse: A Decentralized Agent for Locating Named Objects in a Distributed Environment”, ACM Transactions on Office Information Systems, vol. 1, No. 3, Jul. 1983, pp. 230-253.Applicant
“Internet Telephony for Dummies” 2nd Edition, Chapters 14-16, 1997.Applicant
Stevens, “TCPIP Illustrated”, vol. 1, 1994, Addison-Wesley, pp. 12-122 and inside cover.Applicant
Keiser et al., “Digital Telephony and Network Integration”, 1995, Chapman Hall, Second Edition, pp. 426-428. cited by examiner.Applicant
Chopra, Manvinder, Exploring Intelligent Peripheral Configuration, Universal Personal Communications, 1994. Record., 1994 Third Annual International Conference on, Sep. 27-Oct. 1, 1994, pp. 635 -639.Applicant
Weisser et al. “The Intelligence Network and Forward-Looking Technology” IEEE COMM magazine, Dec. 1988, pp. 64-69.Applicant
Shah et al. “Application of a New Network Concept for Faster Service Deployment” International Conference on COMM. 88 Jun. 12-15, 1988, IEEE Comm. Soc. Conference. Record, vol. 3, pp. 1327-1329.Applicant
Audio Messaging Interchange Specification (AMIS)—Analog Protocol, Version 1, Issue 2, Feb. 1992.Applicant
Jabbari, B., “Common Channel Signaling System No. 7 for ISDN and Intelligent Networks”, Proceedings of the IEEE, vol. 79, No. 2, Feb. 1991, pp. 155-169.Applicant
“Supercharging the Web with Computer Telephony”, CT and the 'Net, Mar. 1996.Applicant
“Audio and Video Over the Internet”, CT and the 'Net, Computer Telephony, Mar. 1996.Applicant
Grigonis, Richard, “Computer Telephony Over The Internet”, CT and the Net, Mar. 1996.Applicant
“Geek of The Week: Carl Malamud Interviews Phil Karn & Jun Murai”, Internet Talk Radio, Mobile IP Networking, Nov. 1993.Applicant
McConnell, Brian, “How to Build an Internet PBX”, Pacific Telephony Design, printed from http://www.phonezone.com/ip-phone.htm Mar. 5, 1997.Applicant
“Welcome to the Phone Zone”, Pacific Telephony Design, http://www.phonezone.com/index2.htm, pp. 1-6.Applicant
Sears, Andrew, “Innovations in Internet Telephony: The Internet as The Competitor to The Pots Network”, Innovations in Internet Telephony: The Internet as the Successor to the Pots Network, Feb. 28, 1996, pp. 1-6.Applicant
“Computer Telephony And The Internet”, Stylus Innovation, http://www.stylus.com/hvml.htm.Applicant
Hedrick, C., “Routing Information Protocol”, Jun. 1988, http://www.internic.net/rfc/rfc1058.txt, pp. 1-30.Applicant
Mills, D.L., “An Experimental Multiple-Path Routing Algorithm”, Mar. 1986, http://www.internic.net/rfc/rfc981.txt, pp. 1-20.Applicant
Lougheed et al., “A Border Gateway Protocol (BGP)”, Jun. 1990, http://www.internic.net/rfc/rfc1163.txt, pp. 1-26.Applicant
S. Deering, “Host Extensions for IP Multicasting”, Aug. 1989, http://www.internic.net/rfc/rfc1112.txt, pp. 1-16.Applicant
Waitzman et al., “Distance Vector Multicast Routing Protocol”, Nov. 1988, http://www.internic.net/rfc/rfc1075.txt, pp. 1-22.Applicant
Hinden et al., “The DARPA Internet Gateway”, Sep. 1982, http://www.internic.net/rfc/rfc823.txt, pp. 1-41.Applicant
“VocalTec's Telephony Gateway —The Ultimate Internet Telephony Solution?,” Computer Telephony Magazine, Sep. 1996.Applicant
“A Call to Phones,” Wired Magazine, Issue 4.03, http://www.wired.com/wired/archive/4.03/updata.html (Mar. 1996).Applicant
Mascoli, Cicchetti & Listanti, “Alternative Scenarios for Data Applications Via Internet-Mobile and DECT-ATM Interworkin,” 4th IEEE International Conference on Universal Personal Communications, pp. 788-792, Nov. 6-10, 1995 published Apr. 1995.Applicant
Blackwell et al. “Secure Short-Cut Routing for Mobile IP,” USENIX Summary 1994 Technical Conferences, Jun. 6-10, 1994.Applicant
Okada et al. “Mobile Communication Using PHS [Personal Handy Phone System] Communications Server,” National Technical Report, vol. 42, No. 1, pp. 46-54 (Feb. 1996).Applicant
Sattler, Michael, “Nautilus Voice Encryption,” May 10, 1995.Applicant
Chernov , Andrey A. “SpeakFreely” software, Apr. 18, 1996.Applicant
“Netspeak Corporation Introduces Webphone, Industry's First Internet-Based Telephony Solution for Business Users,” PC Forum, Mar. 18, 1996.Applicant
Noerpel et al., “PACS: Personal Access Communications System—A Tutorial,” IEEE Personal Communications, Jun. 1996.Applicant
Varma et al., “Architecture for Interworking Data over PCS,” IEEE Communications Magazine, Sep. 1996, 124-130.Applicant
Rosenberg et al., “SIP for Presence,” 41st IETF, Apr. 3, 1998.Applicant
Handley et al., “Session Invitation Protocol”, Internet Engineering Task Force, draft-ietf-mmusic-sip-00, Feb. 22, 1996.Applicant
“Overview”, NetSpeak Corporation, Apr. 8, 1997, printed from Edgar Online.Applicant
“NetSpeak Corporation to Exhibit First Release of Voice Over IP, IP-to-PSTN Networking Products”, Business Wire, Jun. 2, 1997.Applicant
“Camelot Announces Internet Voice Communication Technology Breakthrough”, HighBeamTM Encyclopedia, From: PR Newswire, http://www.encyclopedia.com/doc/1G1-16452259.html?Q=Caml, Feb. 13, 1995, 2 pages.Applicant
1979 Annual Technical Report, “A Research Program in Computer Technology”, Oct. 1978-Sep. 1979, Prepared for the Defense Advanced Research Projects Agency, University of Southern California, ISI-SR-80-17.Applicant
Cohen et al., “A Network Voice Protocol NVP-11”, Lincoln Laboratory Massachusetts Institute of Technology, Apr. 1, 1981, ISI/RR-83-23.Applicant
1982 Annual Technical Report, “A Research Program in Computer Technology”, Jul. 1981-Jun. 1982, University of Southern California, ISI/SR-83-23.Applicant
Annual Report to the Defense Communications Agency, “Network Speech Systems Technology Program”, Massachusetts Institute of Technology Lincoln Laboratory, Oct. 1, 1980-Sep. 30, 1981, issued Feb. 4, 1982.Applicant
Heggestad et al., “Voice and Date Communication Experiments on a Wideband Satellite/Terrestrial Internetwork System”, IEEE International Conference on Communications, Integrating Communication for World Progress, Jun. 19-22, 1983.Applicant
Annual Report to the Defense Communications Agency, “Defense Switched Network Technology and Experiments Technology”, Massachusetts Institute of Technology Lincoln Laboratory, Oct. 1, 1981-Sep. 30, 1982, issued Feb. 5, 1983.Applicant
Merritt, “Providing Telephone Line Access to a Packet Voice Network”, University of Southern California, Feb. 1983, ISI/RR-83-107.Applicant
Weinstein, “The Experimental Integrated Switched Networks- A System Level Network Text Facility”, Proceedings of 1983 IEE Military Communications Conference, Washington, DC, Oct. 31, 1983-Nov. 2, 1983.Applicant
Cesner et al., “Wideband Communications”, 1984 Annual Technical Report, University of Southern California, ISI/SR-85-150, Jul. 1983-Jun. 1984.Applicant
Annual Report to the Defense Communications Agency, “Defense Switched Network Technology and Experiments Technology”, Massachusetts Institute of Technology Lincoln Laboratory, Oct. 1, 1982-Sep. 30, 1983, issued Feb. 29, 1984.Applicant
Gross, “Proceedings of the Oct. 15-17, 1988 Joint Meeting of the Internet Engineering and Internet Architecture Task Forces”, Fourth IETF, The Mitre Corporation.Applicant
Corley, “Bellsouth Trial of Wideband Packet Technology”, Bellsouth Services, 1990 IEEE, CH2829-0/90/0000-1000.Applicant
Inoue et al., “Evolution Scenario of Broadband Services Based on Granulated Broadband Network Concept”, IEEE Region 10 Conference, Tencon 92, Nov. 11-13, 1992.Applicant
Inoue et al., “Granulated Broadband Network Applicable to B-ISDN and PSTN Services”, IEEE Journal on Selected Areas in Communiations, vol. 10, No. 9, Dec. 1992.Applicant
Cerf et al., “A Protocol for Packet Network Intercommunication”, IEEE Transactions on Communications, No. 8, May 1974.Applicant
Cole, “Dialing in the WB Network”, Information Sciences Institute University of Southern California, Dialing-Cole.83, Apr. 30, 1981.Applicant
Hapgood, “Dialing Without Dollars”, Jul. 1995, vol. 17, No. 4, pp. 18, Journal Code, INO.Applicant
Yang, “INETPhone: Telephone Services and Servers on Internet”, Network Working Group, RFC 1798, Apr. 1995, http://ds.internic.net/rfc/rfc1798.txt.Applicant
Chen et al., “Integrated Voice/Data Switching”, IEEE Communication Magazine, Jun. 1988, vol. 26, No. 6.Applicant
Frezza, “The Internet Phone is Poised to Conquer”, Communications Week, Dec. 11, 1995, http://techweb.cmp.com/cw/current.Applicant
“Internet Access: Internet Phone-to-Phone Technology Now a Reality . . . ”, Edge Publishing, Aug. 12, 1996.Applicant
“Internet Phone Saves 50% on Long Distance”, 411 Newsletter, Aug. 5, 1996, vol. 17, No. 15, United Communications Group.Applicant
“Internet Phone Calls are Cheap but Limited”, New Media Markets, Feb. 23, 1995, Financial Times Business Information, Ltd., ISSN:0265-4717.Applicant
“Internet Telephony Seems to be Evolving East, But is There Anyone on the Line?”, Computergram International, Aug. 19, 1996, No. 2980, ISSN: 0268-716X.Applicant
“Internet's International Phone Calls are Cheap But Limited”, Telecom Markets, Financial Times Business Information ID, Mar. 2, 1995, ISSN: 0267-1484.Applicant
Mills, The Washington Post, “Phone Service Via the Internet May Slash Rates”, Aug. 11, 1996.Applicant
Sears, “The Effect of Internet Telephone of the Long Distance Voice Market”, Jan. 14, 1995.Applicant
National Technical Information Service, Wideband Integrated Voice/Data Technology, ADA132284, Mar. 31, 1983, Massachusetts Inst. of Tech., Lexington, Lincoln Lab.Applicant
Detreville et al., “A Distributed Experimental Communications System”, Advances in Local Area Networks, IEEE Press, 1987.Applicant
Borden et al., “Integration of Real-Time Services in an IP-ATM Network”, Internet RFC/STD/FYI/BCP ARchives, Aug. 1995.Applicant
Laubach, “Classical IP and ARP over ATM” Hewlett-Packard Laboratories, Jan. 1994, http://www.faqs.org/rfc/rfc1577.txt.Applicant
Comer, “Internetworking with TCP/IP”, vol. 1, Principles, Protocols, and Architecture, Department of Computer Sciences, 1995.Applicant
Perez et al., “ATM Signaling Support for IP Over ATM”, Network Working Group, RFC 1765, Feb. 1995, http:/www.ietf.org/rfc/rfc1765.txt.Applicant
Mills, M. (Mar. 8, 1996) “Freebie Heebie-Jeebies: New Long-Distance Calling Via the Internet Scares Small Phone Firms”, The Washington Post, sec. F, pp. 1-2.Applicant
Hughes, D.T. (Feb. 21, 1995) “What Hath (Net) God Wrought?”, The Journal [Fairfax, Virginia], sec. B, pp. 1-2.Applicant
Hughes, D.T. (May 28, 1996) “WebPhone Heading for Serious Telephony”, The Journal, [Fairfax, Virginia], sec. A, p. 8.Applicant
Mills, M. (Jan. 23, 1996) “It's the Net's Best Thing to Being There: With Right Software, Computer Becomes Toll-Free Telephone”, The Washington Post, sec. C, pp. 1,5.Applicant
Yang, C. (Feb. 12, 1997), INETPhone: Telephone Services and Serves on Internet. http://ds.internic.net/rfc/rfc/rfc1789.txt.Applicant
Margulies, Edwin (Aug. 1996) Understanding the Voice-Enabled Internet, Flatiron Publishing, Inc., pp. 4-42 and 12-1 to 12-3.Applicant
C. Low, “The Internet Telephony Red Herring,” Hewlett-Packard Laboratories, (May 15, 1996), pp. 1-15.Applicant
C. Low et al., WebIN-an architecture for fast deployment of iN-based personal services, Intelligent Network Workshop, 1996, IN '96, IEEE, (Apr. 21-24, 1996), vol. 2, 196+258.Applicant
Zellweger, Polle T., et al., “An overview of the etherphone system and its applications,” Xerox Palo Alto Research Center, pp. 160-168, Apr. 1988.Applicant
Ng, L.J., et al., “Distributed architectures and databases for intelligent personal communication networks,” Department of Electrical Engineering, U. Of British Columbia, pp. 300-304, Feb. 1992.Applicant
Malyan, Andrew D., et al., “Network architecture and signaling for wireless Personal communications,” IEEE Journal On Selected Areas in Communications, vol. 11, No. 6, pp. 830-841, Aug. 1993.Applicant
Malyan, Andrew D., et al. “A Microcellular Interconnection Architecture For Personal Communications Networks,” Department of Electrical Engineering, University of British Columbia Vancouver, B.C., V6T 1W.5, Canada, pp. 502-505, Feb. 1992.Applicant
Bakre, Ajay, et al., “M-RPC: A Remote Procedure Call Service for Mobile Clients,” Department of Computer Science Rutgers, The State University of New Jersey Piscataway, NJ, pp. 97-110, 1995.Applicant
O'Malley, Sean W., “A Dynamic Network Architecture,” Department of Computer Science, University of Arizona, ACM Transactions on computer systems, vol. 10, No. 2, pp. 110-143, May 1992.Applicant
Cheshire, Stuart, et al., “Internet Mobility 4 by 4,” SIGCOMM 96—Stanford, California, USA, pp. 1-2, Aug. 1996.Applicant
Arao, Shinya, et al., “Component-based policy deployment for service level differentiation in converging communication networks,” IEEE, pp. 1388-1392, 1999.Applicant
Goyal, Pawan, et al., “Integration of call signaling and resource management for IP telephony,” IEEE Network, pp. 24-32, May/Jun. 1999.Applicant
Delatore, J.P., et al., “The 5ESS switching system: Fatory system testing,” AT+T Technical Journal, vol. 64, No. 6, Jul.-Aug. 1985.Applicant
Oran, Dave, “Dial plan mapping for voice-over-IP,” Access Engineering, Apr. 11, 1996.Applicant
Getting started guide for Internet Phone release 4, http://www.vocaltec.com, 1993-1996 VocalTec Inc.Applicant
VocalTec desktop dialer version 3.0, User reference, http://www.vocaltec.com, 1997 VocalTec Ltd.Applicant
“Vocaltec's telephony gateway software captures 1996 product of the year honors from computer telephony magazine,” Herzliya, Israel, Dec. 18, 1996, VocalTec, Ltd.Applicant
Kahane, Opher, et al., “IMTC VoIP Forum Contribution.” Subject: Call management agent system requirements function architecture and protocol, VoIP97-010, pp. 1-44, Seattle, Jan. 1, 1997.Applicant
Kahane, Opher, “Introduction to VocalTec's CMA system,” Intelligent switching for a new era of telecom, Nov. 7, 1996.Applicant
Newton, Harry, “Newton's Telecom Dictionary,” 22nd edition, p. 728, 2006.Applicant
Braden, R., et al., “Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification,” Network Working Group, pp. 1-224, Univ. of Michigan, Sep. 1997.Applicant
Keiser, Bernhard E., et al., “Digital Telephony and Network Integration,” downloaded Jul. 1, 2008.Applicant
Boyle, Jim, et al., “The COPS (Common Open Policy Service) Protocol,” http://www.ietf.orgiintemet-drafts/draft-ietf-rap-cops-07.txt, pp. 1-35, Aug. 16, 1999.Applicant
Bellamy, John, “Digital telephony,” Dallas, TX, Oct. 1981.Applicant
Open and standardized—the world of IP Protocols, “H.323: The Leading Standard in Voice over IP,” downloaded Jul. 1, 2008.Applicant
“Inside APPN— The Essential Guide to the Next-Generation SNA,” IBM, International Technical Support Organization Raleigh Center, Raleigh, NC, Jun. 1997.Applicant
Friedes, A., et al. “Integrating the world through communications,” IEEE ICC, vol. 1 of 3, Jun. 22-25, 1986.Applicant
Huitema, Christian, “Routing in the internet,” Prentice Hall, Englewood Cliffs, NJ, 1995.Applicant
Lucky, R.W., “Applications of communications theory,” Fundamentals of digital switching, AT+T Laboratories, Second Edition, downloaded, Jul. 3, 2008.Applicant
Bellamy, John, “Digital telephony,” Second Edition, Wiley Series in Telecommunications, downloaded, Jul. 3, 2008.Applicant
Stallings, William, “ISDN and Broadband ISDN with frame relay and ATM,” Prentice Hall, Upper Saddle River, NJ, downloaded, Jul. 3, 2008.Applicant
GR-1298-CORE, AINGR: Switching Systems, Telcordia Technologies, Issue 10, Nov. 2004.Applicant
GR-2863-CORE, CCS Network Interface Specification (CCSNIS) Supporting Advanced Intelligent Network (AIN), Bellcore, Bell Communications Research, Issue 2, Dec. 1995.Applicant
GR-246-CORE, Telcordia technologies specification of signalling system No. 7, Telcordia Technologies, Issue 10, Dec. 2005.Applicant
GR-1280-CORE, Advanced intelligent network (AIN) service control point (SCP) generic requirements, Telcordia Technologies, Issue 1, Aug. 1993.Applicant
Morris, Christopher, Academic Press Dictionary of Science and Technology, Academic Press, downloaded, Jul. 3, 2008.Applicant
GR-1428-CORE, CCS Network Interface Specification (CCSNIS) Supporting Toll-Free Service, Bellcore, Issue 2, May 1995.Applicant
Mockapetris, P., “Domain names—concepts and facilities,” Network working group, Nov. 1987.Applicant
Mockapetris, P., “Domain names—implementation and specification,” Network Working Group, Nov. 1987.Applicant
Finseth, C. “An access control protocol, sometimes called TACACS,” Network Working Group, University of Minnesota, pp. 1-20, Jul. 1993.Applicant
Carrel, D., “The TACACS+ Protocol,” Network Working Group, Cisco, Oct. 1996.Applicant
ITU-T, “Line transmission of non-telephone signals,” Recommendation H.323, May 28, 1996.Applicant
Product releases webpage, VocalTec, [email protected], Aug. 26, 1996.Applicant
Tutorial on “H.323,” by The International Engineering Consortium, http://www.iec.org, pp. 1-30, downloaded, Jul. 3, 2008.Applicant
Everhart, C., et al., “New DNS RR Definitions,” Network Working Group, University of Maryland, pp. 1-11, Oct. 1990.Applicant
Handley, M., et al., “SIP: Session Initiation Protocol,” Network Working Group, The Internet Society, Mar. 1999.Applicant
Rosenberg, J., et al., “SIP: Session Initiation Protocol,” Network Working Group, The Internet Society, Jun. 2002.Applicant
Brannen, Lynn, et al., “Next generation switch,” MCI Telecommunications, May 16, 1997.Applicant
Shen, Yi-Shang, “Communications network with flexible call routing and resource allocation,” MCI Invention Disclosure Form, Jan. 8, 1998.Applicant
Kahane, Opher, et al, “Call management agent system specification,” VoIP Forum Technical Committee Contribution, Chicago, Il, Aug. 14, 1996.Applicant
Pulver, Jeff, “The internet telephone tookit,” Wiley Computer Publishing, New York, NY, 1996.Applicant
Haley, James E., “Pay-per-call blocking using LIBD,” AIN Service Description, Bell Atlantic Easy Number Call Routing Service, Oct. 1996.Applicant
American National Standard for Telecommunications—Signalling System No. 7 (SS7)—Signalling Connection Control Part (SCCP), American National Standards Institue, Inc., ANSITI.112-1992, Oct. 26, 1992.Applicant
American National Standard for Telecommunication—Signalling System No. 7 (SS7)—Message Transfer Part (MTP), American National Standards Institue, Inc., Mar. 14, 1996.Applicant
American National Standard for Telecommunications—Signalling System No. 7 (SS7)—Signalling Connection Control Part (SCCP), American National Standards Institue, Inc., ANSITI.110-1992, Jun. 2, 1992.Applicant
Gasman, Lawrence, “Broadband networking,” Van Nostrand Reinhold, Jun. 13, 1994.Applicant
Balkovich, Ed, et al., “Project clarity: First internal trial,” Readiness Review, Bell Atlantic Confidential and proprietary, Jul. 21, 1997.Applicant
Grigonis, Richard “Zippy,” “Computer telephony over the internet,” CT and the 'Net, Mar. 1996.Applicant
Park, Myung Ah, et al., “Dial-up internet access service system with automatic billing mechanism,” ICICS 1997, Electronics .and. Telecommunications Research Institute, pp. 148-151, Singapore, Sep. 9-12, 1997.Applicant
El-Gendy, Hazem, et al., “Computer-supported routing for intelligent networks and personalized wired communications,” ICCS 1994, pp. 1027-1033, Aug. 1994.Applicant
“Audio and video over the internet,” CT and the 'Net, Mar. 1996.Applicant
Malamud, Carl, et al., “Internet talk radio: Geek of the week,” Mobile IP Networking, O'Reilly .and. Associates, Inc., transcript of interview, Nov. 1993.Applicant
McConnell, Brian, “How to build an internet PBX,” Pacific Telephony Design, http://www.phonezone.com/ip-phone.htm, pp. 1-9, Oct. 28, 1996.Applicant
“Supercharging the web with computer telephony,” CT and the 'Net, Mar. 1996.Applicant
Anand, Surinder S., et al., “Accounting architecture for cellular networks,” ICPWC '96, IEEE, pp. 184-189, 1996.Applicant
Karttunen, Jari, et al., “Cost structure analysis and reference model for SCALEABLE network services,” The Institution of Electrical Engineers, pp. 1-9, 1996.Applicant
Jennings, Barbara J., “End-User Requirements for High-Integrity Directory,” Sandia National Laboratories, Albuquerque, IEEE, pp. 1793-1796, 1996.Applicant
Botvich, D., et al., “On Charging for Internet Services provided over an A.TIVI network,” IEEE, pp. 669-679, 1997.Applicant
Estrin, Deborah, et al., “Design Considerations for Usage Accounting and Feedback in Internetworks,” downloaded, Aug. 19, 2008.Applicant
Li, Chung-Sheng, et al., “Time-driven Priority Flow Control for Real-time Heterogeneous Internetworking,” IBM T. J. Watson .and.esearch Center, IEEE, pp. 189-197, 1996.Applicant
Edell, RJ., et al., “Billing users and pricing for TCP,” IEEE Journal on Selected Areas in Communications, vol. 13, Issue 7, pp. 1162-1175, Sep. 1995.Applicant
Margulies, Ed, “CT's Cynerdate With The 'Net,” Computer Telephony Periscope, pp. 28-29, Aug. 1996.Applicant
Inamori, Hisayoshi, et al., “Common Software Platform for Realizing a Strategy for Introducing the TMN,” Network Operations and Management Symposium, vol. 2, pp. 579-589, Feb. 1998.Applicant
Rajan, R., et al., “A policy framework for integrated and differentiated services inthe Internet,” Network, IEEE, vol. 13, Issue 5, pp. 36-41, Sep./Oct. 1999.Applicant
Louth, Nick, “MCI Communications Corp. vaults phone-data divide,” Reuters Limited, News article, Jan. 29, 1998.Applicant
Eriksson, Hans, “MBONE: The Multicast Backbone,” file:IIICI/Documents%20and%20Settings/ ralbertJDesktopIMBONE%2OThe%20Multicast%20Backbone.htm (1 of 13)Mar. 7, 2008 4:06:17 PM.Applicant
Macedonia, Michael R., et al., “MBone Provides Audio and Video Across the Internet,” file:///CI/Documents%20and%20Settings/ralbert/Deskt...20Audio%20and%20Video%20Across%20the% 20Internet.htm (1 of 13) Mar. 10, 2008 9: 34:00 AM.Applicant
Lapolla, Stephanie, “Net call centers, voice to merge,” News, PC Week, Mar. 31, 1997.Applicant
Bohn, Roger, et al., “Mitigating the coming Internet crunch: multiple service levels via precedence,” San Diego Supercomputer Center, Mar. 22, 1994.Applicant
Weiss, W., “QoS with differentiated services,” Bell Labs Technical Journal vol. 3, No. 4, pp. 48-62, Oct.-Dec. 1998.Applicant
Hartanto, Felix, et al., “Policy-Based Billing Architecture For Internet Differentiated Services,” Proceedings of IFIP Fifth International Conference on Broadband Communications (BC '99), Hong Kong, Nov. 10-12, 1999.Applicant
Mahadevan, I., et al., “Parallel Architectures, Algorithms, and Networks,” (I-SPAN '99) Proceedings. Fourth InternationalSymposium, pp. 420-425, Jun. 23-25, 1999.Applicant
Schulzrinne, H., et al., “A Transport Protocol for Real-Time Applications, ” Network Working Group, Audio-Video Transport Working Group, pp. 1-151, Mar. 10, 2008.Applicant
Schulzrinne, H., “RTP Profile for Audio and Video Conferences with Minimal Control,” Network Working Group, Audio-Video Transport Working Group, pp. 1-18, Jan. 1996.Applicant
Kim, Gary, “Talk is cheap voice over the internet,” America's Network, pp. 34-39, Jul. 15, 1996.Applicant
Newton, Harry, “Notes from the field: The personal side of CT,” 12 Computer Telephony, Jan. 1997.Applicant
Venditto, Gus, “Internet phones the future is calling,” Internet World Magazine, Jun. 1996.Applicant
Crowcroft, Jon, et al., “Pricing internet services,” Department of Computer Science, UCL, Gower Street, London, UK, pp. 1-16, downloaded, Aug. 19, 2008.Applicant
Newton, Harry, “Telephony Messaging On The Internet,” http://www.dialogweb.com/cgi/dwclient?req=1205770063076 (1 of 5) Mar. 17, 2008 12:08:09 PM.Applicant
Maruyama, Katsumi, et al., “A Concurrent Object-Oriented Switching Program in Chill,” 2460 IEEE Communications Magazine, Jan. 29, 1991, No. 1, pp. 60-68, New York.Applicant
Rajkumar, R., et al., “A resource allocation model for QoS management,” Proceedings. The 18th IEEE Real-Time Systems Symposium (Cat.No.97CB36172) pp. 298-307, Dec. 2-5, 1997.Applicant
Shabana, Mohamed, et al., “Intelligent switch architecture,” 8081 Proceedings of the National Communications Forum 42 Sep. 30, 1988, No. 2, Chicago, Il., pp. 1312-1319.Applicant
Elixmann, Martin, et al., “Open Switching—Extending Control Architectures to Facilitate Applications,” ISS Symposium, pp. 239-243, Apr. 23, 1995.Applicant
Chandra, P., et al., “Network support for application-oriented QoS,” (IWQoS 98) 1998 Sixth International Workshop on Quality of Service, pp. 187-195, May 18-20, 1998.Applicant
Klein, Rachelle S., et al., “Minimax Resource Allocation with Tree Structured Substitutable Resources,”Operations Research, vol. 39, No. 2, p.p. 285-295, Mar.-Apr. 1991.Applicant
Nyong, D., et al., “Resource based policies for design of interworking heterogeneous service networks,” Interoperable Communications Networks, vol. 1, Nos. 2-4, pp. 571-580, 1998.Applicant
Kabay, S., et al., “The service node—an advanced IN services element,” 8438 BT Technology Journal vol. 13 Apr. 1995, No. 2, pp. 64-72.Applicant
Mayer, Robert L., et al., “Service Net-2000: An intelligent network evolution,” 8010 At.and.T Technical Journal 70 (1991) Summer, No. 3/4, pp. 99-110, Short Hills, NJ.Applicant
Peeren, Rene, “IN in the Hybrid Broadband Network The Intelligent Web,” Presentation, Ericsson, IEEE 1996.Applicant
Jain, Surinder K., “Evolving Existing Narrowband Networks Towards Broadband Networks with IN Capabilities,” Bellcore Intelligent Networks, IEEE, Apr. 22, 1996.Applicant
Matta, Ibrahim, et al, “Type-of-Service Routing in Dynamic Datagram Networks,” Department of Computer Science, University of Maryland, pp. 992-999, IEEE 1994.Applicant
Yeager, Nancy J., et al., “Web Server Technology: The Advanced Guide for World Wide Web Information Providers,” National Center for Supercomputing Applications, pp. 250, Morgan Kaufman Publishers, Inc., 1996.Applicant
Kishimoto, Ryozo, “Agent Communication System for Multimedia Communication Services,” IEEE INFOCOM, Fifteenth Annual Joint Conference of the IEEE Computer and Communications Societies, pp. 10-17, Mar. 24-28, 1996.Applicant
Willebeek-LeMair, Marc H., “Videoconferencing over Packet-Based Networks,” IEEE Journal on Selected Areas in Communications, vol. 15. No. 6, pp. 1101-1114, Aug. 1997.Applicant
Kumar, Vinay, “Internet Multicasting: Internet's Next Big Thing,” ICAST Corporation, pp. 1-13, Sep. 23, 1997.Applicant
The Wall Street Journal article on: “MCI's New Service for Corporate Use Sets 1 Line for Net, Phone,” p. B16, Jan. 30, 1997.Applicant
Sharp, C.D., et al., “Advanced Intelligent Networks—now a reality,” Electronics .and. Communication Engineering Journal, pp. 153-162, Jun. 1994.Applicant
Pezzutti, David A., “Operations Issues for Advanced Intelligent Networks,” IEEE Communications Magazine, pp. 58-63, Feb. 1992.Applicant
Oppen, Derek C., et al., “The Clearinghouse: A Decentralized Agent for Locating Named Objects in a Distributed Environment,” ACM Transactions on Office Information Systems, vol. 1, No. 3, Jul. 1983, pp. 230-253.Applicant
Rendleman, John, et al., “ATM Goes Into Orbit . . . While IP Gets Speedy in Space,” Communications Week, Mar. 17, 1997, www.commweek.com.Applicant
Miller, Mark A., “Troubleshooting TCP/IP: Analyzing the Protocols of the Internet,” M.and.T Books, pp. 365-389, 1992.Applicant
Platt, Richard, “Why IsoEthernet Will Change the Voice and Video Worlds,” IEEE Communications Magazine, pp. 55-59, Apr. 1996.Applicant
Rosalyn, Retkwa, “Telephone Politics,” Internet World, Jun. 1996.Applicant
Schreyer, Oliver, et al., “Least Cost Call Routing—A Brilliant Application for Private IN,” IEEE International Conference on Communications, vol. 2 of 3, Jun. 23-27, 1996.Applicant
Rodriguez Serrano, Inma, “Evolution of a Hybrid Fibre Coaxial Network for Multimedia Interactive Services,” British Telecommunications Egineering, vol. 15, pp. 249-253, Oct. 1996.Applicant
Sunaga, Hiroshi, et al., “A Reliable Communication Switching Platform for Quick Service Provisioning,” IEEE International Conference on Communications, Seattle, WA, Jun. 18-22, 1995.Applicant
Marketing materials re: Workshops on “Telephony on the Internet,” to take place on Sep. 24-25, 1996, at The Drake Hotel, Chicago, Illinois.Applicant
Gralla, Preston, “How the Internet Works,” Ziff-Davis Press, pp. 118-119, 1996.Applicant
Gralla, Preston, “How the Internet Works,” Ziff-Davis Press, pp. 64-67, 1996.Applicant
Tsuchida, Hisazumi, et al., “Intelligent Dynamic Service Provisioning Architecture in the Multimedia Era,” NTT Information and Communication Systems Laboratories, IEEE, pp. 1117-1122, 1996.Applicant
Low, Colin, “Integrating Communication Services,” IEEE Communications Magazine, pp. 164-169, Jun. 1997.Applicant
Fridisch, M., et al., “Terminals for Accessing the Internet—The Internet Telephone,” Alcatel Telecommunications Review, 4th Quarter, pp. 304-309, 1996.Applicant
Hurwicz, Michael, “Switched ATM is fast, but not that smart. Routed IP is smart, but not that fast. Why not combine them?,” http://www.ipsilon.com/, Apr. 1997.Applicant
Diehl, Standford, “Data's New Voice,” BYTE, Special Report, pp. 129-135, Sep. 1996.Applicant
Kahn, Jeffery, “Videoconferencing Debuts on the Internet,” LBL, U.S. Department of Energy, Berkeley, California, University of California, Feb. 28, 1995.Applicant
Braun, Hans-Werner, et al., “A framework for flow-based accounting on the Internet,” National Science Foundation (NCR-9119473), downloaded, Aug. 21, 2008.Applicant
Kelly, Katy, “Up to their laptops in packed powder: Mountaintop office keeps skiers in touch,” USA Today, Final Edition, News, pp. 1A, Feb. 21, 1997.Applicant
Braun, Torsten, “Implementation of an Internet Video Conferencing Application over ATM,” IBM European Networking Center, Heidelberg, Germany, IEEE, pp. 287-294, 1997.Applicant
Sclavos, Jean, et al., “Information Model: From Abstraction to Application,” Telecom Paris, France, pp. 1-13, downloaded, Aug. 21, 2008.Applicant
Black, Uyless D., “OSI: A model for computer communications standards,” Prentice-Hall, Inc., pp. 157-201, 1991.Applicant
Sriram, Kotikalapudi, et al., “Voice Packetization and Compression in Broadband ATM Networks,” IEEE Journal on Selected Areas in Communications, vol. 9, No. 3, pp. 294-304, Apr. 1991.Applicant
Arango, Mauricio, et al., “Guaranteed Internet Bandwith,” IEEE, pp. 862-866, Nov. 18, 1996.Applicant
Lapolla, Stephanie, “Seagate joins the backup vendors' enterprise forays,” PC Week, The National Newspaper of Corporate Computing, vol. 13, No. 33, Aug. 19, 1996.Applicant
Harmer, Julie, et al., “Revised Requirements for Mobile-API-Interim deliverable,” OnTheMove public project, pp. 1-44, Dec. 1996.Applicant
Schulzrinne, Henning, “Personal Mobility for Multimedia Services in the Internet,” IDMS '96 (European Workshop on Interactive Distributed Multimedia Systems and Services), Berlin, Germany, pp. 1-18, Mar. 4-6, 1996.Applicant
Schulzrinne, “Simple Conference Invitation Protocol,” Internet Engineering Task Force, pp. 1-19, Feb. 22, 1996.Applicant
Ash, G.R., et al., “Design and Optimization of Networks With Dynamic Routing,” American Telephone and Telegraph Company, The Bell System Technical Journal, vol. 60, No. 8, pp. 1787-1820, Oct. 1981.Applicant
Prosecution history of U.S. Patent 6,332,023, Issued, Dec. 18, 2001.Applicant
The Phone Zone, an online reference cite and catalog of PC based telephony and networking solution for business, http://www.phonezone.com/index2.htm, Oct. 29, 1996.Applicant
“IDT's Net2Phone Launches Phone-to-Phone Technology Via The Internet,” Press release, http://web.net2phone.com/about/press/releases/p2p.asp, Sep. 8, 1997.Applicant
“Vocaltec's telephony gateway—the ultimate internet telephony solution?,” Computer Telephony, pp. 30, Sep. 1996.Applicant
Cheriton, David R., “Dissemination-Oriented Communication Systems: Final Report,” ARPA contract No. DABT63-91-K-0001, Nov. 26, 1996.Applicant
Johnson, David B., “Scalable Support for Transparent Mobile Host Internetworking,” Proceedings of the Ninth Annual IEEE Worshop on Computer Communications, pp. 1-10, Oct. 1994.Applicant
“Specifications of Signalling System No. 7,” International Telecommunication Union, ITU-T Telecommunication Standardization Sector of ITU, Recommendation, Q.700, Mar. 1993.Applicant
“Integrated Services Digital Network (ISDN) 1.312,” CCITT The International Telegraph and Telephone Consultative Committee, ITU International Telecommunication Union, Recommendation, I.312/Q.1201, Oct. 1992.Applicant
“Interface Recommendation for Intelligent Network CS-1,” International Telecommunication Union, ITU-T Telecommunication Standardization Sector of ITU, ITU-T Recommendation Q.1218, Oct. 1995.Applicant
“Series Q: Switching and Signalling,” Intelligent Network, International Telecommunication Union, ITU-T, Telecommunication Standardization Sector of ITU, Recommendation Q.1218—Addendum 1, Sep. 1997.Applicant
Imielinski, Tomasz, et al., “Mobile Wireless Computing: Solutions and Challenges in Data Management,” Department of Computer Science, Rutgers University, downloaded, Oct. 22, 2008.Applicant
Balmer, R., et al., “A Concept for RSVP Over DiffServ,” Institute of Computer Science and Applied Mathematics, University of Berne, Switzerland, http://www.iam.unibe.ch/˜rvs, pp. 412-417, IEEE, May 2000.Applicant
Ziegler, Jr., K., “A Distributed Information System Study,” IBM SYST J, vol. 18, No. 3, pp. 374-401, 1979.Applicant
Blake, S., et al., “An Architecture for Differentiated Services,” Network Working Group, pp. 1-36, Dec. 1998.Applicant
Walters, Rob, “Computer Telephony Integration,” Second Edition, Artech House, 1999.Applicant
IMTC Voice over IP Forum Service Interoperability Implementation Agreement, Draft 0.91, IMTC Voice over IP Forum Technical Committee, VoIP97-008, Jan. 13, 1997.Applicant
Braden, R., et al., “Integrated Services in the Internet Architecture: an Overview,” Network Working Group, pp. 1-28, Jul. 1994.Applicant
Braun, Torsten, “Internet Protocols for Multimedia Communications,” Part II: Resource Reservation, Transport and Application Protocols, IEEE MultiMedia, pp. 74-82, Oct.-Dec. 1997.Applicant
Black, Uyless D., “Internet Telephony Call Processing Protocols,” Prentice Hall PTR, www.phptr.com, 2001.Applicant
Briere, Daniel D., et al., “Internet Telephony for Dummies,” 2nd Edition, IDG Books Worlwide, Inc., 1997.Applicant
Vin, Harrick M., et al., “Multimedia Conferencing in the Etherphone Environment,” Xerox Palo Alto Research Center, IEEE, pp. 69-79, Oct. 1991.Applicant
Detti, Andrea, et al., “Supporting RSVP in a Differentiated Service Domain: an Architectural Framework and a Scalability Analysis,” http://www-st.inf.tu-dresden.de/elisa/, downloaded, Oct. 27, 2008.Applicant
Bernet, Yoram, “The Complementary Roles of RSVP and Differentiated Services in the Full-Service QoS Network,” QoS Mechanisms, Microsoft, downloaded, Oct. 27, 2008.Applicant
Herzog, S., et al., “COPS Usage for RSVP,” Network Working Group, pp. 1-15, Jan. 2000.Applicant
Sebestyen, Istvan, “What is the position of Q.2, Q.3/15 on Internet Telephony for the IMTC—VoIP Forum Meeting in Seattle,” ITU Telecommunication Standardization Sector, Study Group 15, pp. 1-5, Dec. 5, 1996.Applicant
Daniele, M., et al., “Textual Conventions for Internet Network Addresses,” Nework Working Group, pp. 1-16, Jun. 2000.Applicant
Handley, M., et al., “SIP: Session Initiation Protocol,” Internet Engineering Task Force, pp. 1-30, Dec. 2, 1996.Applicant
Weinstein, Clifford J., “The Experimental Integrated Switched Network—a System-Level Network Test Facility,” IEEE, pp. 449-456, Jan. 1983.Applicant
“Computer Telephony and the Internet,” pp. 1-8, downloaded, Jul. 14, 2009.Applicant
Jitian, Xiao, et al., “Sharing Model of Netware Node Resources and Real-Time Scheduling,” Mini-Micro Systems, vol. 16, No. 12, pp. 54-59, Dec. 1995.Applicant
Swinehart, D.C., et al., “Adding Voice to an Office Computer Network”, IEEE Global Telecommunications Conference, San Diego, CA, Nov. 28-Dec. 1, 1983.Applicant
Mills, Mike, “Phone service via the internet may slash rates,” The Washington Post, A Section; P. A01, Sunday, Final Edition, Aug. 11, 1996.Applicant
Chapman, Martin, et al, “Overall Concepts and Principles of TINA,” TINA-C, Version 1.0, Feb. 17, 1995.Applicant
Verjinski, Richard D., “Phase, A Portable Host Access System Environment,” IEEE, May 1989.Applicant
Verizon Services Corp., et al., v. Cox Fibernet Virginia, Inc., et al., Report of Herman J. Helgert, Ph.D., Exhibit D, downloaded, Aug. 21, 2008.Applicant
Verizon Services Corp., et al., v. Cox Fibernet Virginia, Inc., et al., Report of Herman J. Helgert, Ph.D., Exhibit E, downloaded, Aug. 21, 2008.Applicant
Verizon Services Corp., et al., v. Cox Fibernet Virginia, Inc., et al., Report of Herman J. Helgert, Ph.D., Exhibit F, downloaded, Aug. 21, 2008.Applicant
The Jeff Pulver Blog: Free World Dialup and Verizon's patent on “name translation,” http://pulverblog.pulver.com/archives/006846.html, pp. 1-19, Apr. 23, 2007.Applicant
Lipoff, Stuart, “Operations Support System Framework for Data Over Cable Services,” Data Over Cable Technical Reports, MCNS Holdings, L.P., Oct. 16, 1996.Applicant
Sinnreich, H., et al., “Interdomain IP communications with QoS, authorization and usage reporting,” http:www.cs. columbia.edu/-hgs/sip/drafts/draft-sinnreich-sip-qos-osp, Feb. 2000.Applicant
Pan, Ping, et al., “Diameter: Policy and Accounting Extension for SIP,” Internet Engineering Task Force, Internet Draft, pp. 1-17, Nov. 15, 1998.Applicant
Schulzrinne, Henning, et al., “Interaction of Call Setup and Resource Reservation Protocols in Internet Telephony,” pp. 1-13, Jun. 11, 1999, downloaded, Aug. 21, 2008.Applicant
Rosen, E., et al., “Memo re: BGP/MPLS VPNs,” Networking Group, pp. 1-25, Mar. 1999.Applicant
Waksberg, M., “Axe 10 and the Intelligent Network,” Commutation .and. Transmission, No. 4, pp. 67-76, Dec. 1993.Applicant
Niitsu, Yoshihiro, et al., “Computer-aided stepwise service creation environment for intelligent network,” NTT Communication Switching Laboratories, Tokyo, Japan, IEEE, pp. 454-458, 1992.Applicant
Morgan, Michael J., et al., “Service creation technologies for the intelligent network,” At.and.t Technical Journal, Summer 1991.Applicant
Fujioka, Masanobu, et al., “Universal service creation and provision environment for intelligent network,” XIII International Switching Symposium, Stockholm, Sweden, Proceedings vol. III, pp. 149-156, May 2 -Jun. 1, 1990.Applicant
Moy, J., “OSPF Version 2,” Network Working Group, Proteon, Inc., Jul. 1991.Applicant
Lantz, Keith A., “Towards a universal directory service,” Operating Systems Review, vol. 20, No. 2, Apr. 1986.Applicant
Fang, Wenjia, “Building An Accounting Infrastructure for the Internet,” Princeton University, IEEE, pp. 105-109, 1996.Applicant
Aidarous, Salah, et al., “The role of the element management layer in network management,” 1994 IEEE Network Operations and Management Symposium, Feb. 14-17, 1994.Applicant
Gareiss, Robin, “Voice over the internet,” Data Communications, pp. 93-100, Sep. 1996.Applicant
Bethoney, Herb, “HAHTSite Gives Pros Everything They Need,” PC Week, p. 36, Mar. 10, 1997.Applicant
Kolarov, Aleksandar, et al., “End-to-end Adaptive Rate Based Congestion Control Scheme for ABR Service in Wide Area ATM Networks,” IEEE International Conference on Communications, Seattle, Washington, pp. 138-143, Feb. 1995.Applicant
Chen, Larry T., et al., “ATM and Satellite Distribution of Multimedia Educational Courseware,” 1996 IEEE International Conference on Communications, pp. 1133-1137, Jun. 23-27, 1996.Applicant
Civanlar, M. Reha, et al., “FusionNet: Joining the Internet .and. Phone Networks for Multimedia Applications,” ACM Multimedia 96, pp. 431-432, 1996.Applicant
Cobbold, Christopher, et al., “Enhancement for Integrated Wireless Personal Communications over Metropolitan Area Networks,” 1996 IEEE International Conference on Communications, pp. 1370-1376, Jun. 23-27, 1996.Applicant
Comer, Douglas E., “Internetworking With TCP/IP,” 3rd ed., V. 1. Principles, protocols, and architecture, Prentice-Hall, Inc., 1995.Applicant
Mahadevan, I., et al., “Quality of service achitectures for wireless networks: IntServ andDiffServ models,” http://ieeexplore.ieee.org/xpllabsprintf.jsp?arnumber==778974.and.page..., Aug. 6, 2002.Applicant
Ahmadi, H., et al., “NBBS Traffic management overview,” IBM Systems Journal, vol. 34, No. 4, pp. 604-628, 1995.Applicant
Duan, Juan, et al., “Efficient Utilization of Multiple Channels between two Switches In ATM Networks,” IEEE, pp. 1906-1911, 1995.Applicant
Ejiri, Masayoshi, et al., “For Whom the Advancing service/network management,” IEEE, pp. 422-433, 1994.Applicant
Lee, Whay Chiou, et al., “Integrated Packet Networks With Quality of Service Constraints,” Globecom, IEEE, pp. 8A.3.1-8A.3.5, 1991.Applicant
Elia, Carlo, et al., “Skyplex: Distributed Up-link for Digital Television via Satellite,” IEEE Intelligent Network workshop IN, Melbourne, Australia, Apr. 21-24, 1996.Applicant
Ely, Tom, “The Service Control Point as a Cross Network Integrator,” Bellcore, IEEE, pp. 1-8, 1996.Applicant
Mamais, G., et al., “Efficient buffer management and scheduling in a combined IntServand DiffServ architecture: a performance study,” ATM, 1999. ICATM '99. 1999 2nd International Conference on, pp. 236-242, Jun. 21-23, 1999.Applicant
Baumgartner, F., et al., “Differentiated services: a new approach for quality of service in the Internet,” Proceedings of Eighth International Conference on High Performance Networking, pp. 255-273, Sep. 21-25, 1998.Applicant
Sibal, Sandeep, et al., “Controlling Alternate Routing in General-Mesh Packet Flow Networks,” SIGCOMM 1994, London, England, pp. 168-179, Aug. 1994.Applicant
Jajszczyk, A., et al., “Bringing information to People,” IEEE INFOCOM '95, Proceedings, vol. 3, Apr. 2-6, 1995.Applicant
CT and the 'Net, “Webphone,” Computer Telephony pp. 219-221, Mar. 1996.Applicant
Sisalem, Dorgham, et al., “The Network Video Terminal,” IEEE Proceedings of HPDC-5, pp. 3-10, 1996.Applicant
Baumgartner, H., et al., “Middleware for a New Generation of Mobile Networks: The ACTS OnTheMove Project,” http:// www.isoc.org/inet96/proceedings/a6/a6—3.htm, pp. 1-4, Apr. 14, 2008.Applicant
“Talk Talk,” tele.com, pp. 68-72, Jun. 1996.Applicant
Kreller, Birgit, et al., “UMTS: A Middleware Architecture and Mobile API Approach,” IEEE Personal Communications, pp. 32-38, Apr. 1998.Applicant
Low, Colin, et al., “WebIN—An Architecture for Fast Deployment of IN-based Personal Services,” IEEE, 1996.Applicant
Grami, A., et al., “The Role of Satellites in the Information Superhighway,” IEEE International Conference on Communications, pp. 1577-1581, Jun. 18-22, 1995.Applicant
Gupta, Ranabir, et al., “Technical Assessment of (T)INA—TMN—OSI Technology For Service Management Applications,” IEEE Network Operations and Management Symposium, vol. 3, pp. 877-887, Feb. 14-17, 1994.Applicant
Inamori, Hisayoshi, et al., “Applying TMN to a Distributed Communications Node System with Common Platform Software,” NTT Network Service Systems Laboratories, Tokyo, Japan, pp. 83-87, IEEE International Conference on Communications, Seattle, WA, Jun. 18.Applicant
Clark, David D., et al., “Supporting Real-Time Applications in an Integrated Services Packet Network: Architecture and Mechanism,” COMM'92, MD, USA, pp. 14-26, Aug. 1992.Applicant
Gupta, Amit, “Resource sharing for multi-party real-time communication,” Proceedings of the Fourteenth Annual Joint Conference of the IEEE Computer and Communication Societies (INFOCOM '95), pp. 1230-1237, 1995.Applicant
Kausar, Nadia, et al., “A Charging Model for Sessions on the Internet,” IEEE, pp. 32-38, Apr. 1999.Applicant
Schutzrinne, Henning, “A comprehensive multimedia control architecture for the Internet,” IEEE, pp. 65-76, Sep. 1997.Applicant
Tsaoussidis, V., et al., “A CORBA-based Application Service Middleware Architecture and Implementation,” State University, of NY at Stony Brook, pp. 1-7, downloaded, Aug. 19, 2008.Applicant
Bernet, Y., et al., “A Framework for Differentiated Services,” The Internet Society, pp. 1-35, Sep. 22, 1999.Applicant
Gleeson, B., et al., “A Framework for IP Based Virtual Private Networks,” The Internet Society, pp. 1-62, Feb. 2000.Applicant
Yavatkar, Raj, et al., “A Framework for Policy-based Admission Control,” Internet Engineering Task Force, pp. 1-19, Apr. 1999.Applicant
Ekstein, Ronnie, et al., “AAA Protocols: Comparison between RADIUS, DIAMETER and COPS,” Internet Engineering Task Force (IETF), pp. 1-17, Aug. 1999.Applicant
Hussmann, H., et al., “An edge device for supporting internet integrated services over switched ATM networks,” pp. 1-10, downloaded, Aug. 19, 2008.Applicant
Sinnreich, H., et al., “Interdomain IP communications with QoS, authorization and usage reporting,” http:www.ietf.org/internet-drafts..., Jan. 2000.Applicant
Mascolo, Cecilia, et al., “An XML based Programmable Network Platform,” Dept. of Computer Science, University College London, pp. 1-5, Jun. 10, 2005.Applicant
Kumar, Vijay P., et al., “Beyond Best Effort: Router Architectures for the Differentiated Services of Tomorrow's Internet,” IEEE Communications Magazine, pp. 152-164, May 1998.Applicant
Pan, Ping, et al., “Diameter-SIP,” Internet Draft, pp. 1-15, Nov. 15, 1998.Applicant
Neilson, Rob, et al., “A Discussion of Bandwidth Broker Requirements for Internet2 Qbone Deployment,” Internet2 Qbone BB Advisory Council, Version 0.7, pp. 1-30, Aug. 1999.Applicant
Stojsic, Goran, et al., “Formal Definition of SIP Proxy Behavior,” IEEE, pp. 289-292, Feb. 2001.Applicant
Bhuyan, L, et al., “Impact of switch Design on the Application Performance of Cache-Coherent Multiproce.ssors,” Dept. of Computer Science, TexasA.and.M University and Intel Corp., pp. 1-9, Nov. 15, 2005.Applicant
Product Overview, “IP Highway product overview,” http://iphighway.com/prod/, pp. 1-4, Sep. 22, 1999.Applicant
Rosenberg, Jonathan, et al., “Internet telephony gateway location,” IEEE, pp. 488-496, Feb. 1998.Applicant
Wright, S., et al., “IP “Telephony”vs. ATM: What is There to Discuss?,” IEEE, pp. 400-409, Feb. 1998.Applicant
Wedlund, Elin, et al., “Mobility support using SIP,” WoWMoM, Jan. 1999.Applicant
Aiken, B., et al., “Network Policy and Services: A report of a Workshop on Middleware,” Network Working Group, pp. 1-26, Feb. 2000.Applicant
Aspnes, James, et al., “On-Line Routing of Virtual Circuits willi Applications to Load Balancing and Machine Scheduling,” pp. 486-504, Journal of the ACM, vol. 44, No. 3, May 1997.Applicant
Salsano, Stefano, et al., “QoS Control by Means of COPS to Support SIP-Based Applications,” IEEE Network, Mar./Apr. 2007.Applicant
White, Paul P., “RSVP and Integrated Services in the Internet: a Tutorial,” IEEE Communications Magazine, pp. 100-106, May 1997.Applicant
Beck, Christopher J., et al., “Scheduling alternative activities,” http://www.aaai.org/home.html, 1999.Applicant
Flykt, P., et al., “SIP Services And Internetworking IPv6,” 3G Mobile Communication Technologies, Mar. 26-28, 2001, Conference Publication No. 477.Applicant
Schulzrinne, Henning, et al., “Signaling for internet telephony,” Columbia University, Dept. of Computer Science Technical Report CUCS-005-98, Feb. 2, 1998.Applicant
Barzilai, Tsipora, et al., “Design and Implementation of an RSVP-based Quality of Service Architecture for Integrated Services Internet,” IEEE, May 1997.Applicant
Hubaux, Jean-Pierre, et al., “The impact of the Internet on telecommunication architectures,” Computer Networks 31 (1999).Applicant
Roberts, Erica, “The New Class System,” http://www.data.com/roundups/class—system.html, pp. 1-14, Sep. 22, 1999.Applicant
Wroclawski, J., “The Use of RSVP with IETF Integrated Services,” ftp://ftp.isi.edu/in-notes/rfc2210.txt, Sep. 22, 1999.Applicant
Sloman, Morris, et al., “Distributed Management For The Networked Millenium,” Proceedings of the Sixth IFIP/IEEE International Symposium on Integrated Network Management—Boston, MA, U.S.A., May 24-28, 1999.Applicant
Schulzrinne, Henning, “MIME-Version: 1.0,” email communication dated Oct. 10, 1995.Applicant
Garrahan, James J., et al., “Marching toward the global intelligent network,” IEEE Communications Magazine, vol. 31, No. 3, pp. 30-36, Mar. 1993.Applicant
Gys, L, et al., “Intelligence in the Network,” Alcatel Telecommunications Review, pp. 13-22, 1st Quarter 1998.Applicant
Yang, C., “INETPhone Telephone Services and Servers on Internet, ” Network Working Group, pp. 1-6, Apr. 1995.Applicant
Perret, Stephane, et al., “MAP: Mobile Assistant Programming for Large Scale Communication Networks,” IEEE, pp. 1128-1132, Apr. 1996.Applicant
Plunkett, Bill, “ISCP Service Capacity Improvements,” Bellcore, Feb. 29, 1996.Applicant
Murray, Dave, “High speed signalling link interface for ISCP version 6.0,” Bellcore, Feb. 29, 1996.Applicant
Evans, Jeff, “Alternative Approaches for Multi-ISCP Locator,” Bell Atlantic, Mar. 13, 1996.Applicant
Performance Task Force, “Off-Line Engineering Tool,” Bellcore, Sep. 3, 1996.Applicant
Jones, Doug R., “Advanced intelligent network delivering control of network routing,” Bell Atlantic, downloaded, Aug. 20, 2008.Applicant
Gorton, Dave, “ISCP Evolution overview,” Telcordia Technologies Inc., Jun. 5, 2001.Applicant
Brown, Kathryn C., “Telecom Convergence,” PowerPoint presentation, downloaded Aug. 21, 2008.Applicant
Cohen, Danny, “Specifications for the Network Voice Protocol (NVP),” http://www.rfc-archive.org/getrfc.php?rfc=741, Nov. 22, 1977.Applicant
Low, Colin, “The Internet Telephony Red Herring,” Hewlett Packard, pp. 1-15, May 15, 1996.Applicant
de la Fuente, L.A., et al., “Application of the TINA-C Management Architecture,” Bellcore, Red Bank, NJ, downloaded, Aug. 21, 2008.Applicant
Finseth, C., “An access control protocol, sometimes called TACACS,” Network Working Group, University of Minnesota, pp. 1-21, Jul. 1993.Applicant
Buchanan, Ken, et al., “IMT-2000: Service Provider's Perspective,” IEEE Personal Communications, pp. 8-13, Aug. 1997.Applicant
Pontailler, Catherine, “TMN and New Network Architectures,” IEEE Communications Magazine, pp. 84-88, Apr. 1993.Applicant
Weinrib, A., et al., “Decentralized resource allocation for distributed systems,” IEEE INFOCOM '87. The Conference on Computer Communications. Proceedings. Sixth Annual Conference—Global Networks: Concept to Realization (Cat. No. 87CH2412-5) p. 328-36, Mar. 31-Apr. 2, 1987.Applicant
Nagarajan, Ramesh, et al., “Local Allocation of End-to-End Quality-of-Service in High-Speed Networks,” National Research Foundation under grant NCR-9116183 and the Defense Advanced Projects Research Agency under contract NAG2-578, pp. 1-28, 1993.Applicant
Chang, Rong N., et al., “A Service Acquisition Mechanism for the Client/Service Model in Cygnus,” IBM Canada Laboratory Technical Report TR 74.059, pp. 323-345, May 20-24, 1991.Applicant
Inamori, Hisayoshi, et al., “Applying TMN to a Distributed Communications Node System with Common Platform Software,” NTT Network Service Systems Laboratories, Tokyo, Japan, pp. 83-87, IEEE International Conference on Communications, Seattle, WA, Jun. 18-22, 1995.Applicant
Stoica, Ion, et al., “LIRA: An Approach for Service Differentiation in the internet,” sponsored by DARPA under contract Nos. N66001-96-C-8528 and NOO174-96-K-0002, and by a NSF Career Award under grant No. NCR-9624979. Additional support was provided by Intel Corp., MCI, and Sun Microsystems, pp. 1-14, Sep. 8, 1998.Applicant
“Introduction to VTG,” Northvale, NJ 07647, Tel. 201-768-9400, [email protected], prior to 1997.Applicant
Quicklook, “Internet By Satellite,” 1 page, http://www.netsatx.net, at least as early as 1990.Applicant
Nagarajan, Ramesh, et al., “Local Allocation of End-to-End Quality-of Service in High-Speed Networks,” National Research Foundation under grant NCR-9116183 and the Defense Advanced Projects Research Agency under contract NAG2-578, pp. 1-28, at least as early as 1993.Applicant