1. Field of the Invention
The present invention relates generally to the field of Internet multimedia and single media communication, and, more particularly, to a method and system for providing feature-based services using the Session Initiation Protocol.
2. Description of the Related Art
The last twenty years have seen the Internet grow exponentially. From a tool for the technically savvy, the Internet has turned into one of the main communication means of a large segment of the general populace. As it has grown, other tools and technology, such as music and videos, have migrated to the computer-based medium.
One example of migrating technology is the movement of telephony services to the Internet. Internet telephony refers to a wide range of services, not merely the traditional telephone call. In general, it refers to the transport of real-time media, such as voice and video, over the Internet to provide interactive communication among Internet users. Users may access the Internet through a variety of means—a personal computer (PC), a stand-alone Internet Protocol (IP)-enabled device, or even by dialing up to a gateway from the handset of a traditional Public Switched Telephone Network (PSTN).
The advantages of IP telephony are quite sweeping. It offers high-quality voice communication, improved multiplexing gains, rich computer telephony integration, advanced services, an open market for providers, and reduced cost. Most of these advantages flow from the fact that IP telephony is packet-based, rather than circuit-based, like the present phone system. In a circuit-based communication, such as a phone call on traditional equipment, an actual connection is maintained between the caller and callee through switches and wires. In a packet-based communication, the communication itself is broken down into packets which are sent over a network. This allows for a more efficient use of resources. In addition, IP telephony uses mostly text-based protocols, which allows for easy implementation and debugging in languages such as Java, Tcl, and Perl. The layered protocols in IP telephony are also designed to operate independently of one another. This means that one can use the same higher-layer protocol in a wide range of devices, from cell and desktop telephones to TVs, stereos, and computers, because the lower, physical layers will take care of the differences.
Currently, traditional PSTN telephony uses SS7 (System Signalling 7) as the signalling protocol which establishes, controls, and tears down circuit connections. IP telephony uses SIP (Session Initiation Protocol, RFC 2543) as the signalling protocol for telephony, videoconferencing, and multimedia sessions. SIP provides for establishing and releasing connections.
The SIP protocol is a text-based protocol that works above the transport layer in the TCP/IP (Transport Control Protocol/Internet Protocol) stack. SIP can use any transport protocol, including TCP (Transport Control Protocol) and UDP (User Datagram Protocol) as its transport protocol. In addition, SIP can also work with ATM AAL5 (Asynchronous Transfer Mode ATM Adaption Layer 5), IPX (Internet Packet exchange), frame relay or X.25 transport protocols.
There are two components in a SIP network: network servers and user agents. A user agent is an end system that acts on behalf of someone who wants to participate in calls. In general, the user agent contains both a protocol client (a user agent client UAC) which initiates a call and a protocol server (user agent server UAS) which responds to a call (see
The steps in initiating a session are fairly simple: as shown in
However, there are difficulties in migrating all the current services of traditional telephone networks to Internet telephony and SIP. In traditional networks, the Private Branch Exchange (PBX) is the cornerstone of business voice communication networking. For instance, all the employees at a business will have phones at their desk connected to a PBX, which routes the calls, handles voice mail, and offers other services. The replacement of traditional PBXs with IP-(Internet Protocol)-based PBXs will require that the users have the same services from their IP-enabled desktop telephone that they previously had from their traditional PBX telephone.
An example of the type of services traditional PBXs offer is the Do Not Disturb feature. Do Not Disturb (DND) is often implemented as a button that a user presses so that all calls will be automatically forwarded to the user's voice mailbox. In a traditional PBX, a DND command message is generally sent from the desktop device to the PBX, which then automatically forwards all calls to the voice mail system. But, in an SIP-based IP telephone network, the desktop telephone, or, more exactly, the user agent server UAS, would perform the forwarding. Although this works in many cases, it assumes the end client device (in this case, the SIP-based IP desktop telephone) has a DND capability, which is not assured. Therefore, there is a need for a system and method for traditional PBX services, such as the DND feature, in end client devices, such as SIP-based IP desktop telephones, without assuming the end client devices have this capability.
In addition, there are other features in traditional PBX systems that require the network server to be notified of status changes, especially when those changes affect the session/call setup handling for a user that has signed up for a network-based service. Examples include unconditional call forwarding, when the user wishes to forward all calls to another number/address; conditional call forwarding, when the user wishes to forward some calls under certain conditions; call blocking, when the user wishes to block certain addresses/numbers from being called; and call screening, when the user wishes to prevent calls from certain address/numbers from being received. Therefore, a need exists for a method and system for the user agent to notify the network server of feature status changes, such as DND, call forwarding, screening and blocking.
An object of the present invention is to provide a system and method which allows the network server in a SIP-based telephony network to perform all the functions of a traditional PBX system.
Another object of the present invention is to allow traditional PBX functions to be performed in a network, without requiring that the end client devices in that network be able to perform all of these functions.
A further object of the present invention is to provide a system and method for notifying network servers of changes to feature information for a particular user or device.
In order to fulfill these and other objects, the present invention provides an extension to the SIP protocol that would be used for notifying network servers of changes to feature information for a particular user or device. This extension, which consists of an extra field header called “Feature”, would allow an end client to inform the network server of feature changes, rather than perform these features itself.
The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawing in which:
In a traditional PBX system, when the end-user wanted to modify or begin use of a feature, such as DND, the telephone unit would send a message with special digits that indicated the feature control information. For instance, the DND button might send a “*720” message, which tells the PBX to activate the DND feature on that phone extension. Releasing the DND button might send a “@720” message, which tells the PBX to deactivate the DND feature on that phone extension.
The preferred embodiment of the present invention uses one of the message types (REGISTER) that already exists in SIP to send this type of feature control information. In order to do so, the preferred embodiment adds another field header to the REGISTER message, the “Feature” field header.
In order to more fully understand the preferred embodiment, a brief discussion of the various types of method messages in SIP is in order. INVITE and ACK are two method messages that were mentioned above; other method messages include OPTIONS, BYE, CANCEL, and REGISTER. The INVITE message indicates that the user or service is being invited to participate in a session. The ACK message confirms that the client has received a final response to an INVITE message. The OPTIONS message is a query to the server concerning the server's capabilities. The BYE message is used by the client to indicate to the server that it wishes to release or end the call. The CANCEL message is used to cancel a pending request.
The REGISTER message can be understood as a “log on” message, although it has many more uses. As an example, a desktop telephone could be designed with an “I'm here” button for indicating to the SIP server that the person is actually at that phone and ready to receive phone calls and other multimedia communications. This “I'm here” button would send a REGISTER message to the SIP server. That may or may not be followed up with a request for validation from the SIP server to ensure privacy. If it all works out, the SIP server will register that user and the user's address in the SIP server database, so that calls can be properly routed.
In general, registration either validates or invalidates a SIP user agent for user services provided by the SIP server. Additionally, the user agent provides one or more contact locations to the SIP server. An example of a REGISTER message, in which a user named “Barney” is using to log on to a SIP server, is below:
An exact description of the header fields is contained in RFC 2543, but such detail is unnecessary for complete understanding of the present invention. However, as an aside, the Authorization field header is used to validate that an authorized user is making the registration.
In a preferred embodiment of the present invention, another field header is added to the REGISTER message that would carry feature control information. This would allow the REGISTER message to perform the additional functions required to emulate a traditional PBX system. For example, if the user in a IP-based PBX system pressed the DND button, a properly formatted REGISTER message is sent from the end client device, i.e., telephone, to the SIP Proxy Server, as shown by (1) in
This Feature field entry would tell the SIP server to change the “dnd” feature status to “active”. Thus, the SIP server would know to send all incoming calls for Barney to Barney's voice mail box. This allows the user agent client UAC to be “thin”: in other words, the user agent client will not have to add all the PBX features to its own protocol. Instead, the user agent client (in our example, an IP-based desktop telephone) will simply tell the network server to provide the feature. When the SIP server has appropriately updated its tables and database, the SIP server sends (2) an OK message to the user agent client UAC to confirm that the feature status information has been updated. The OK message would have the following format (bold added to show new header):
When (3) someone attempts to call Barney, such as Frank, who happens to be using a SIP-enabled client device, the SIP server will refer to its updated tables and database and find that Barney wishes his messages to be entered into the voice mail system. The SIP server will then (4) redirect the incoming call to the voice mail messaging system.
Then the (5) voice mail system will send an OK message to Frank in order to initiate a connection.
When using features such as call forwarding, screening or blocking, the Feature field entry would contain additional information. For instance, if the activated feature was call screening, the Feature field entry could appear as:
Feature=screen; status=active; tel: +1-972-555-1212
The REGISTER message containing this Feature field entry would instruct the SIP server to activate call screening and prevent the telephone number 1-972-555-1212 from calling the user. Clearly, other features may require more or less information, depending on the function that the SIP server will be required to perform.
The solution provided by the preferred embodiment is both easier to implement than traditional message handling, such as performed in a PBX system, and easier to understand. Furthermore, it's more intuitively obvious what “dnd; status=active” means, than the traditional “720”.
While the present invention has been described in detail with reference to the preferred embodiment, it is a mere exemplary application. Thus, it is to be clearly understood that many variations can be made by anyone skilled in the art within the scope and spirit of the present invention.
This application is a continuation of U.S. application Ser. No. 09/436,793, filed on Nov. 8, 1999, now U.S. Pat. No. 6,615,236, the contents of which are hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4817085 | De Prycker | Mar 1989 | A |
5077732 | Fischer et al. | Dec 1991 | A |
5303286 | Wiedeman | Apr 1994 | A |
5353335 | D'Urso et al. | Oct 1994 | A |
5434907 | Hurst et al. | Jul 1995 | A |
5467343 | Lee et al. | Nov 1995 | A |
5664009 | Hurst et al. | Sep 1997 | A |
5680116 | Hashimoto et al. | Oct 1997 | A |
5691986 | Pearlstein | Nov 1997 | A |
5699359 | Suga | Dec 1997 | A |
5732219 | Blumer et al. | Mar 1998 | A |
5742763 | Jones | Apr 1998 | A |
5745556 | Ronen | Apr 1998 | A |
5768361 | Cowgill | Jun 1998 | A |
5794039 | Guck | Aug 1998 | A |
5802510 | Jones | Sep 1998 | A |
5826039 | Jones | Oct 1998 | A |
5832221 | Jones | Nov 1998 | A |
5859898 | Checco | Jan 1999 | A |
5864610 | Ronen | Jan 1999 | A |
5867494 | Krishnaswamy et al. | Feb 1999 | A |
5867495 | Elliott et al. | Feb 1999 | A |
5883894 | Patel et al. | Mar 1999 | A |
5889774 | Mirashrafi et al. | Mar 1999 | A |
5907547 | Foladate et al. | May 1999 | A |
5913176 | Barabash | Jun 1999 | A |
5923659 | Curry et al. | Jul 1999 | A |
5930348 | Regnier et al. | Jul 1999 | A |
5951638 | Hoss et al. | Sep 1999 | A |
5953504 | Sokal et al. | Sep 1999 | A |
5956391 | Melen et al. | Sep 1999 | A |
5958005 | Thorne et al. | Sep 1999 | A |
5999525 | Krishnaswamy et al. | Dec 1999 | A |
6067442 | Wiedeman et al. | May 2000 | A |
6069890 | White et al. | May 2000 | A |
6084952 | Beerman, Jr. et al. | Jul 2000 | A |
6094525 | Perlman et al. | Jul 2000 | A |
6094578 | Purcell et al. | Jul 2000 | A |
6134235 | Goldman et al. | Oct 2000 | A |
6137869 | Voit et al. | Oct 2000 | A |
6151390 | Volftsun et al. | Nov 2000 | A |
6151629 | Trewitt | Nov 2000 | A |
6157648 | Voit et al. | Dec 2000 | A |
6163536 | Dunn et al. | Dec 2000 | A |
6201858 | Sundhar | Mar 2001 | B1 |
6202081 | Naudus | Mar 2001 | B1 |
6215858 | Bartholomew et al. | Apr 2001 | B1 |
6226364 | O'Neil | May 2001 | B1 |
6233318 | Picard et al. | May 2001 | B1 |
6240391 | Ball et al. | May 2001 | B1 |
6240449 | Nadeau | May 2001 | B1 |
6253249 | Belzile | Jun 2001 | B1 |
6259914 | Koster | Jul 2001 | B1 |
6278707 | MacMillan | Aug 2001 | B1 |
6282270 | Porter | Aug 2001 | B1 |
6295291 | Larkins | Sep 2001 | B1 |
6301609 | Aravamudan et al. | Oct 2001 | B1 |
6331986 | Mitra et al. | Dec 2001 | B1 |
6333931 | LaPier et al. | Dec 2001 | B1 |
6335927 | Elliott et al. | Jan 2002 | B1 |
6335968 | Malik | Jan 2002 | B1 |
6339594 | Civanlar et al. | Jan 2002 | B1 |
6363053 | Schuster et al. | Mar 2002 | B1 |
6366576 | Haga | Apr 2002 | B1 |
6370120 | Hardy | Apr 2002 | B1 |
6381316 | Joyce et al. | Apr 2002 | B2 |
6393269 | Hartmaier et al. | May 2002 | B1 |
6404746 | Cave et al. | Jun 2002 | B1 |
6404870 | Kia et al. | Jun 2002 | B1 |
6411705 | Oran et al. | Jun 2002 | B2 |
6426955 | Dalton et al. | Jul 2002 | B1 |
6434143 | Donovan | Aug 2002 | B1 |
6453034 | Donovan et al. | Sep 2002 | B1 |
6463053 | Chen | Oct 2002 | B1 |
6487283 | Thomas et al. | Nov 2002 | B2 |
6507647 | Mandalia | Jan 2003 | B1 |
6515997 | Feltner et al. | Feb 2003 | B1 |
6519242 | Emery et al. | Feb 2003 | B1 |
6529499 | Doshi et al. | Mar 2003 | B1 |
6567399 | Schuster et al. | May 2003 | B1 |
6570869 | Shankar et al. | May 2003 | B1 |
6584093 | Salama et al. | Jun 2003 | B1 |
6584110 | Mizuta et al. | Jun 2003 | B1 |
6600735 | Iwama et al. | Jul 2003 | B1 |
6631186 | Adams et al. | Oct 2003 | B1 |
6633571 | Sakamoto | Oct 2003 | B1 |
6650901 | Schuster et al. | Nov 2003 | B1 |
6658022 | West et al. | Dec 2003 | B1 |
6674745 | Schuster et al. | Jan 2004 | B1 |
6681252 | Schuster et al. | Jan 2004 | B1 |
6687221 | Kurose et al. | Feb 2004 | B1 |
6744759 | Sidhu et al. | Jun 2004 | B1 |
6760324 | Scott et al. | Jul 2004 | B1 |
6779032 | Hericourt | Aug 2004 | B1 |
6937563 | Preston et al. | Aug 2005 | B2 |
6954654 | Ejzak | Oct 2005 | B2 |
7005985 | Steeves | Feb 2006 | B1 |
20020167943 | Hakim et al. | Nov 2002 | A1 |
Number | Date | Country |
---|---|---|
1207226 | Feb 1999 | CN |
0794650 | Sep 1997 | EP |
0123456 | Jan 2000 | EP |
9716007 | May 1997 | WO |
9716916 | May 1997 | WO |
9722210 | Jun 1997 | WO |
9723078 | Jun 1997 | WO |
9821874 | May 1998 | WO |
Number | Date | Country | |
---|---|---|---|
20030200260 A1 | Oct 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09436793 | Nov 1999 | US |
Child | 10440539 | US |