Intelligent terminal SIP enabled devices

The invention facilitates SIP Enabled devices creating and exchanging augmented data communication messages. An initiating SIP Enabled device may be configured to create an augmented message that includes a call-type and/or a network identification. The augmented data may be configured for a SIP Enabled device by either an administrator or a system user. Furthermore, the system user may customize the default settings either indefinitely or temporarily. Upon receiving an augmented SIP communication request, a receiving SIP Enabled device may identify the request as augmented and subsequently extract the augmented data. The receiving SIP enabled device may be configured to execute functionality based on the extracted augmented data. For example, if the augmented data includes a “hotline” call-type, the receiving SIP enabled device may be configured to play a certain ringtone or display a “hotline” identifier on the device's display.

FIELD OF INVENTION

This invention relates generally to the field of telecommunication data management and more specifically to an apparatus, method and system for providing Session Initiation Protocol (SIP) functionality on a SIP enabled endpoint.

BACKGROUND INFORMATION

Generally, voice data transportation over computer networks has been conducted via ‘dumb’—terminals connected with ‘intelligent’ data servers. The ‘dumb’ terminals were designated, as such, because the majority of the data processing occurred at a central server location. Voice data would be encoded at the individual terminals, or in later implementations of communication networks—SIP endpoints, and transported to a communication server, where the data could be processed and transmitted to a receiving endpoint in a format conforming to the receiving endpoint's processing requirements.

However, as processors continue to increase in processing power and decrease in cost, it was determined that the data processing could be shifted from the central server to the endpoints, themselves. In order to achieve the data processing shift to the endpoints, significant modifications to the hardware/software components were necessary, in addition to modifying the communication protocols, themselves. According to the functionality shift to the endpoints, the communication server simply acts as a “middle-man” relaying the encoded data from an initiating endpoint to a receiving endpoint. This results in a paradigm shift, wherein telecommunication functionally is provided primarily by the terminal endpoints.

The shift has led to the development of communication protocols that facilitate the data encoding/decoding by the endpoint and simple transfers of the encoded data across a communication network. Session Initiation Protocol (SIP) is one of several protocols that may be used in the Internet Protocol to support Internet Telephony applications. The SIP specification is defined in the Internet Engineering Task Force (IETF) Request for Comments (RFC) 3261, dated June 2002; the disclosure of which is incorporated herein by reference in its entirety. SIP is an application-layer control protocol for creating, modifying, and terminating sessions between networked endpoints, which are referred to as SIP Enabled Devices, User Agents, or simply, SIP endpoints.

As discussed above, SIP Enabled Devices implement a network communication protocol, wherein a communication session is established for two endpoints to exchange communication data. The SIP specification defines several types of communication resources implemented for establishing and maintaining SIP based communication sessions among SIP Enabled Devices, which include SIP Registrars, SIP Redirect Servers, and SIP Proxies. These SIP communication resources are responsible for sending, receiving, routing, and relaying SIP messages among SIP Enabled Devices.

SIP Proxy Servers conventionally perform a variety of functions in SIP networks, such as coordinating data routing for SIP session requests to a particular SIP network subscriber current location; authenticating and authorizing SIP network users for particular services; implementing call-routing policies, as well as providing additional functionality to SIP network users. However, as discussed above, the paradigm is shifting to provide functionality at the SIP endpoints. The invention discussed herein is directed to achieving the paradigm shift.

SUMMARY OF THE INVENTION

An object of the invention is to modify SIP Enabled devices to create augmented SIP communication messages that include call type and/or network identification parameters. As such, an initiating SIP Enabled device is capable of creating augmented SIP communication request messages. A receiving SIP Enabled device may identify data within an incoming communication request as correlating to a certain call type and/or network identification parameter according to a standardized format.

Accordingly, a SIP Enabled device receiving such an augmented communication message can process the incoming communication request and determine what type of call it is and/or what type of network the call originated from. The receiving SIP Enabled device may also be configured to execute a range of operations/functionality based on the processed augmented communication data. As will be discussed in greater detail below, the receiving SIP Enabled device may implement a special ring tone or flash a special indicator based on the call type/network identification parameter.

It is an object of the invention to provide the additional functionality in a variety of implementations that provide users a great deal of flexibility. In one implementation, system administrators may have the ability to establish the call type/network identification parameters available for either an individual SIP endpoint of a series or SIP endpoints. Further, the administrator may provide a system user (subscriber) with a limited ability to further customize the settings for their needs. In another implementation, the administrator may allow the system user to fully customize the SIP Enabled device to meet the communication needs on an individual call basis.

It is another object of the invention to provide SIP Enabled devices/servers that may be configured to operate according to the conventional SIP communication protocol or the modified SIP communication protocol. More specifically, the SIP enabled device may generate either conventional SIP data messages or augmented SIP data messages that include call type/network identification parameters depending on the particular operating environment.

DETAILED DESCRIPTION OF THE INVENTION

Overview

FIG. 1illustrates a conventional SIP Enabled device communication network. SIP Enabled devices100,106are hardware devices implementing a SIP Enabled Application module (software configured to enable the SIP communication protocol). The SIP Enabled devices100,106conduct communication sessions through any type of networked devices, such as: network servers102,104, across Local Area Networks (LANs)101,105or Wide Area Networks (WANs)103. For illustrative simplicity, network servers102and104each perform the function of a SIP Proxy Server, a SIP Redirect Server, and a SIP Registrar; the functionality of which are defined in the herein before referenced SIP protocol specification. These network servers also provide some functionality that is required for the SIP Enabled Devices to communicate; for example a Domain Name System (DNS) server, a Dynamic Host Control Protocol (DHCP) server, and a Lightweight Directory Access Protocol (LDAP) server.

The communication sessions are conducted based on the SIP Internet Telephony communication protocol. More specifically, the communications sessions are established and conducted through the transmission, processing and receipt of SIP communication data messages among SIP Enabled devices. Examples of SIP Enabled Devices include telephones, personal computers, and multimedia conferencing systems or any other type of device capable of implementing the SIP communication protocol.

In accordance with the invention, SIP Enabled devices are configured with a range of communication functionality performed upon the initiation or receipt of an augmented communication request. By way of example only, an initiating SIP enabled device may designate a communication request as a “hotline” call or any other number of call type designations. Illustrative call types include, but are not limited to: an A-B call, a hotline call, a warmline call, a hunting call, a manual hold call, callback, a call forwarded call, etc.

Furthermore, under the present invention, the initiating SIP Enabled device may also associate a designated network identification type with an augmented communication request. Example network identification parameters may include internal/private, external/public or unknown. It is to be understood that this is not an exhaustive list of call types/network identification parameters and that additional call types/network identifiers may be developed. Further, as will be described in greater detail below, the administrators/system users may automatically or manually associate the call-type/network identification designations associated with communication requests executed by an individual terminal or by any number of terminals.

Referring toFIG. 2, a SIP Enabled Device200is comprised of a User Interface Control Logic module201that interfaces with a user interface (an illustrative user interface is shown inFIG. 2and discussed below). The User Interface Control Logic module201also interfaces with a SIP Enabled Application204. The SIP Enabled Application204implements a controller coordinating the various modules interacting within a single SIP Enabled Device200for creating, sending, receiving and processing SIP data messages (as discussed in greater detail below).

The SIP Enabled Application204is also responsible for controlling additional functionality associated with the SIP Enabled device200. The SIP Enabled Application module204and the Network Communication Logic module206are stored on the SIP enabled device200in memory220and executed by processor225. The SIP Enabled Application204interfaces with Network Communications Logic module206to send and receive non-SIP messages with other networked resources (not shown). Network Communications Logic module206interfaces with Network (hardware) Interface207, which is used to physically interface to a network (an exemplary network is shown inFIG. 1) that provides connectivity with other networked devices.

FIG. 3illustrates one embodiment of the present invention where an initiating SIP Enabled device350communicates with a receiving SIP Enabled device375across a SIP proxy device355(representing one possible implementation of a communication network device). It is to be understood that the SIP Enabled devices350and375are possible implementations of the software modules/hardware components illustrated inFIG. 2and discussed above. The user interfaces illustrated inFIG. 3are example interfaces associated with SIP Enabled devices used for Internet telephony applications. The user interfaces are comprised of components including: a handset309, text display304, operational buttons305, as well as ringer306and an LED indicator308. A user physically interacts with these components to operate the SIP Enabled Device350,375in a manner that is similar to a telephone.

In accordance with the invention, the SIP Enabled devices350and375are configured to implement an augmented version of the SIP communication protocol. Initiating/Receiving SIP Enabled devices350,375provide additional functionality than that possible with a conventional telephone. More specifically, the enhanced SIP Enabled devices350and375may be configured, for example, to include call-type and/or network identification parameters as part of the SIP data communication messages.

FIG. 3also depicts a representative message exchange between a transmitting and a receiving SIP Enabled device. The figure illustrates an initiating SIP terminal implementing call type/network identification parameters within a SIP communication request (augmented SIP data message) and transmitting the augmented SIP data message to a receiving SIP terminal. The initiating SIP Enabled Application204(seeFIG. 2) in device350may be configured to augment a SIP “invite” message or “re-invite” message to include additional data corresponding to the call type/network identification parameters associated with a particular communication request.

For example, in one implementation, the communications processor is configured to identify whether an initiating/receiving device is connected to a network that supports the supplemental functionality. If the SIP Enabled device is configured to support the supplemental functionality, the augmented data messages are created/processed. In the event that an initiating device does not support the supplemental functionality, ordinary SIP communication data messages are sent. Further, if the receiving device does not support the supplemental functionality, the augmented data parameters would not be processed and simply ignored.

In one implementation, the SIP Enabled Application204in initiating device350may append augmented data to the “invite” or “re-invite” communication initiation messages. Alternately, the SIP Enabled device350may be configured to create augmented SIP communication initiation messages that include data bits set aside for the call type/network identification parameters.

As discussed above, the initiating SIP Enabled device350may be configured to automatically switch into an augmented functionality operational mode.FIGS. 4,5and6illustrate flow diagrams depicting three illustrative implementations of the communication session request process. The flow diagrams illustrate the procedures that are executed by the components shown inFIG. 3.

FIG. 4illustrates an implementation of the system where a system administrator accesses SIP Enabled device350, which is configured to support augmented SIP functionality. In step401, the system administrator logs into the SIP Enabled device350(either locally or remotely). According to this implementation, the administrator sets the defaults call types/network identification types for the device communication sessions.

For illustrative purposes, these steps will be discussed in the context of setting up an office telephone system. As such, the administrator has the ability to set default call-types to associate with various phone calls, such as calls originating within a specific office, from a satellite office, or from outside the company. For example, an administrator may set the default inter-office call-type as a standard A-B call type (a first user is simply calling a second user). After establishing a default call type, the administrator may then associate certain phone numbers with a different call type. For example, the administrator in step405may associate all phone numbers for subscribers within a defined workgroup as “Project A” or “warmline” calls.

Further, at this point the administrator also establishes the default network identification for the SIP Enabled device, assigning a Network_ID value that will be included as part of the SIP communication request messages. It is to be understood that an administrator may provide an identifier for a particular network of SIP communication devices. The identifier may be correlated to Network_ID values including general Network_ID values such as an interior network, exterior network and/or unknown network identifiers. Alternately or in addition to, an administrator may provide a Network_ID with a certain level of specificity, for example such to indicate a remote office network (e.g., Detroit Office) and/or a corporate network id (e.g., Siemens) and to enable a receiving unit to identify a particular initiating network. After the system administrator has finished configuring the SIP Enabled device350(see,FIG. 3), a user may initiate a communication request. In step410, the user (Subscriber A350) initiates a communication request to another user (Subscriber B375). For the purposes of this discussion, it is assumed that Subscriber B is within a work group that has been designated as a “warmline” call-type.

Accordingly, the initiating SIP Enabled device350creates an augmented communication message in step415. In one implementation, the initiating SIP Enabled device augments the SIP “invite” or the “re-invite” data message to include the call type/network identification parameters. The initiating SIP Enabled device350then transmits the augmented SIP communication message in step420to the receiving SIP Enabled device375. After receiving the message, the SIP device375identifies the message as augmented and containing call type/network identification parameters in step425. In some implementations, the receiving SIP Enabled device375may identify whether the incoming SIP message is augmented or a standard SIP message. The identification step ensures that the correct processing routine will be applied to the data message.

The next step in the communication initiation process involves the receiving SIP device375extracting the augmented data in step430and implementing defined functionality based on the extracted data in step435. For example, as shown inFIG. 3, SIP Device375displays “WarmLine” on the text display304because there was a “warmline” call type associated with the communication request. Moreover, based on locally defined parameters, SIP device375may activate the ringer306in a manner correlated with “warmline” calls. The actual functionality corresponding to correlated call types is configured on the receiving SIP device375. For example, SIP Device375may be configured to execute three short chirp rings for all “warmline” calls. During data extraction/processing SIP device375parses the network identification data and confirms the initiating SIP device350is on an internal network. Therefore, as shown inFIG. 3, the text display304shows an “Internal Network” indicator on the display.

In another implementation of the invention, the Receiving SIP device375may execute additional functionality or features based on a received (and correlated) call type. For example, subscriber A may have an established communication session with subscriber B. Another SIP device associated with subscriber C may request a communication session with subscriber B. Subscriber B's SIP enabled device may process and determine subscriber C's communication request as a “Hotline” line call type and interrupt the established communication session. Alternately, subscriber B's SIP device may be operating in “Do-Not-Disturb” mode. Subscriber A may place a “Hotline” call to subscriber B. Subscriber B's SIP device will process and determine the incoming communication request is a “Hotline” call type and may be configured to override the “Do-Not-Disturb” mode setting of subscriber B's SIP device. It is to be understood that SIP devices may be configured to execute similar functionality based on the Network_ID type or any other type of augmented SIP data parameter.

FIG. 5is a flow diagram illustrating a similar process of establishing the augmented data parameters on an initiating SIP Enabled device350as the process illustrated inFIG. 4. However, in step501of the implementation inFIG. 5, Subscriber A is provided with limited customization capabilities. The administrator configures the basic defaults associated with SIP Enabled device350, such as setting default A-B call types and the network identification parameter in step501.

The administrator also provides a limited set of user customization, for example, enabling the user to customize the call types for communication requests to subscribers within a specific workgroup. In step505, a user (Subscriber A) is able to access a customization menu on text display304through interacting with the operational buttons305. In step510, the user can designate communication requests directed to Subscriber B as a “warmline” call type. Additionally, Subscriber A may customize how SIP Enabled device350responds to incoming communication requests with various call types (i.e., what type of indicator is displayed or what type of ringtone is generated).

As discussed, Subscriber A is provided with a limited customization ability. Once these parameters have been established in step510, Subscriber A initiates a communication request directed to Subscriber B375in step513. In accordance with the customized augmented data parameters, SIP Enabled device350creates an augmented communication request message in step515and transmits the augmented request message in step520. In steps525and530respectively, the receiving SIP Enabled device375receives, identifies and processes the augmented communication request message.

FIG. 6illustrates a flow diagram associated with an implementation where the user may temporarily customize call-types. In step601, an administrator configures the basic default augmented information associated with SIP Enabled device350. As discussed regardingFIG. 5, Subscriber A is provided with the ability to further customize the initial administrator settings in step605.

However, Subscriber A may want to temporarily associate Subscriber B with a different call type. For example, Subscriber A may have to make an urgent call to Subscriber B. Advantageously, Subscriber A can make a single “hotline” communication request to Subscriber B in step608. Alternately, Subscriber A may temporarily modify the call type for a certain number of calls or a certain time period. This may be considered “one-shot” functionality, however it is to be understood that the actual number of communication requests with a modified call type association may vary between different implementations of the invention.

Accordingly, Subscriber A may press an operational button305(see,FIG. 3) to accomplish the temporary transition in call type in step610. For example, pressing one of the operational buttons305may access a call type transition menu on text display304, while pressing another button305may effectuate the new temporary association in step613.

After the temporary call-type/communication request is made, the SIP Enabled device350creates and transmits the augmented communication request in steps615and620, respectively. In steps625and630, SIP Enabled device375receives, identifies and processes the augmented communication request. The functionality associated with the temporary call-type is executed in step635and illustrated inFIG. 7. By way of example only, the “hotline” call-type correlates to functionality that includes displaying the term “HOTLINE CALL”770, flashing the LED indicator708and/or playing a distinct ringtone on ringer706on subscriber B's SIP device775.

Furthermore, SIP proxy device755may be configured to identify the communication request transmitted from Subscriber A's device750to Subscriber B's device750as an internal/private network communication request. Accordingly, as part of the communication process the “middle man,” SIP proxy device755, may set the Network_ID parameter to indicate that the communication request is transmitted on an internal network. This data may be added to the augmented message as the message is transmitted to Subscriber B's device775. As illustrated in step623, subscriber B may configure the SIP Enabled device375with a particular text indicator770or a specific ring cadence to indicate that the incoming communication request is from a SIP Enabled device750that is part of the “internal network” (as illustrated on text display704inFIG. 7).

As another example of Network_ID based functionality, SIP Enabled device775may initiate a single long ringing cadence for Internal/private network calls or a double short ringing cadence for external/public network calls based on the particular Network_ID parameter. In another implementation, SIP Enabled device775may be configured to identify the Network_ID and forward all internal network calls to a voicemail, whereas external calls are forwarded to a secretary or communication system operator.

The present invention has been illustrated and described with reference to particular embodiments and applications thereof. It will be readily apparent to those skilled in that art that the present invention will have applications beyond those described herein for purposes of description of the invention. For example, the present invention can be adapted for use in any environment where the principals taught herein are desired.

To facilitate discussion of the present invention, preferred illustrative embodiments are assumed; however, the above-described embodiments are merely illustrative of the principals of the invention and are not intended to be exclusive embodiments thereof. It should be understood by one skilled in the art that alternative embodiments drawn to variations in the enumerated embodiments and teachings disclosed herein can be derived and implemented to realize the various benefits of the present invention.

It should further be understood that the foregoing and many various modifications, omissions and additions may be devised by one skilled in the art without departing from the spirit and scope of the invention. It is therefore intended that the present invention is not limited to the disclosed embodiments but should be defined in accordance with the claims which follow.