Internet protocol telephony voice/video message deposit and retrieval

INTERNET PROTOCOL TELEPHONY VOICE/VIDEO

MESSAGE DEPOSIT AND RETRIEVAL

BACKGROUND OF THE INVENTION

1. Field pf Invention

The present invention relates to Internet Protocol telephony, and more particularly to a method for handling the signaling related to the storing and forwarding of voice and video messages in an Internet Protocol based network.

2. Description of the Related Art

Internet Protocol (IP) telephony is the real time delivery of voice, and other multimedia data, between two or more parties across a network using Internet protocols. Internet telephony began in the mid-1990's with PC-to-PC Internet telephony, which required both parties to have a personal computer with specialized hardware and software, allowing voice signals to be transmitted over the Internet. More recently, IP telephony systems have been suggested which utilize the existing public switched telephone network (PSTN) infrastructure integrated with IP networks, such as the Internet.

Internet technology is session based, rather than connection based. An Internet protocol, such as Session Initiation Protocols (SIP) is typically used to establish the session and negotiate the capabilities for the session. Once the session is established, the actual media is transported across the IP network using a different protocol, such as Real- time Transport Protocol (RTP). IP telephony use has advanced rapidly since its introduction.

IP telephony has advantages over the PSTN, providing a cost savings for both users and carriers while allowing the transport of a variety of media types, such as voice and video, as opposed to just voice as in the case of the PSTN. While IP telephony may someday replace the PSTN, it suffers some disadvantages in that it currently lacks many of the features already developed for the PSTN. One such feature is call message deposit and retrieval.

The SIP protocol is currently a leading protocol for establishing IP telephony sessions. However, currently no definitions have been established in the SIP protocol to handle the call forwarding logic and signaling requirements necessary for proper interfacing with messaging systems for message deposit and retrieval. The conditional forwarding of calls for deposit in a messaging system is generally done when a called party is either busy or fails to answer a call. A called party may also wish to have a caller unconditionally deposit a message in a messaging system. In either case, the messaging system interface must provide signaling capabilities to store the message, whether conditionally or unconditionally, and also for a called party to later retrieve the deposited message. The signalmg capabilities must also include information about the calling party depositing the message. The identity of the called party must also be verified when he or she retrieves the deposited message. Therefore, a need exists for a method of handling die signaling required for IP telephony voice and video message deposit and retrieval in an IP based network using the SIP protocol, thereby allowing integration of the IP network with an Integrated Messaging System (IMS).

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to provide a method of handling the SIP signaling requirements associated with routing calls to an IMS to allow a calling party to conditionally deposit a message in a called party's message mailbox, in an Internet Protocol based network. It is another object of the present invention to provide a method of handling the

SIP signaling requirements associated with routing calls to an IMS to allow a calling party to unconditionally deposit a message in a called party's message mailbox, in an Internet Protocol based network.

It is yet another object of the present invention to provide a method of handling the SIP signaling requirements associated with routing calls to the IMS to allow a calling party to retrieve the deposited message in the called party's messaging mailbox, in an

Internet Protocol based network.

It is still another object of the present invention to provide a method of handling the SIP signaling requirements associated with notifying the called party that a new message has been deposited in the called party's message mailbox, in an Internet Protocol based network.

To achieve the above objects, a method in accordance with the present invention is provided for signaling an IMS on an IP based network to deposit a message, the method including the steps of sending a SIP INVITE request to the IMS indicating a message deposit action; receiving a corresponding SIP message from the IMS agreeing to participate in the message deposit action; and sending an SIP acknowledge message to the EMS confirming receipt of the corresponding SIP message; and depositing the message in a destination mailbox.

Also provided is a method of signaling an IMS on an IP based network to retrieve a deposited message, the method including the steps of sending a SIP I VITE request to the IMS indicating a message retrieval action; receiving a corresponding SIP message from the IMS agreeing to participate in the message retrieval action; sending an SEP acknowledge message to the IMS corifirming receipt of the corresponding SIP message; and retrieving the deposited message from a mailbox corresponding to known account information.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features, and advantages of the present invention will become more apparent in light of the following detailed description of an exemplary embodiment thereof taken in conjunction with the attached drawings in which:

FIG. 1 is a block diagram illustrating a system supporting the method of the present invention; and

FIG. 2 is a flow chart illustrating a method of depositing a message in accordance with an embodiment of the present invention FIG. 3 is a flow chart illustrating a method of retrieving a message in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Turning now to the drawings, in which like reference numerals identify similar or identical elements throughout the several views, FIG. 1 is a block diagram illustrating a system providing telephony services between and among subscribers using traditional telephones 13 and Internet telephones 15. Signaling and media for calls are transported over the Internet 17.

Traditional telephones 13 are connected to the Internet 17 through traditional telephone switching equipment, such as PBX's and IP telephony gateways 21. EP telephony gateways 21 each include a signaling gateway (not shown) and a media gateway (not shown). The signaling gateway provides bi-directional transportation between PSTN telephony signaling and EP telephony signaling messages, such as SIP. IP phones 15 may be connected directly to the Internet through a local area network or by a modem connection through an Internet service provider. Generally, call signaling and media are transported across the Internet 17 between an originating IP telephony gateway 21a and a destination IP telephony gateway 21b. Typically, routing information is supported by a proxy server, such as a network server (NS) 23. The NS 23 also provides call control and call forwarding control. That is, the NS 23 includes an intermediary application program that acts as both a server and a client for the purposes of making requests on behalf of other clients or, referred to generally as calling parties hereinafter. In the SIP protocol an INVITE request is sent from the originating IP telephony gateway 21a to the address of the called party at the NS 23. IP call setup signaling messages are transported back and forth between the IP telephony gateways 21 and the NS 23 until the call is setup using the SIP protocol, as is commonly known in the art.

The system also includes a location manager 31 , which provides gateway selection and mobility management services to the NS 23. The location manager 31 functions as an S P redirect server. A redirect server is a server thut accepts an SEP request, maps the address into zero or more new addresses and returns these addresses to the sender, for instance the NS 23. Unlike an SIP proxy server such as the NS 23, a redirect server does not initiate its own SIP requests or accept calls. Thus, if the NS 23 cannot send a session initiation request to the IP telephony gateway 21, the NS 23 sends a session initiation request to the called party at the location manager 31. The location manager 31 either consults its own database or accesses the legacy service control entity 29 to obtain a new address for the called party. The location manager 31 then returns the new address to the NS 23.

In cases where the called party can not be reached, i.e. the phone is busy or not answered, the call is forwarded to an Integrated Messaging System (IMS) 25. In order to properly forward, deposit and retrieve the messages in the IMS 25, the NS 23 must communicate with the EMS 25 using the SEP protocol. Currently there are no definitions established for using the SEP protocol to handle conditional call forwarding logic and the signaling requirements necessary for proper interfacing with messaging systems. The present invention establishes the SIP signaling requirements for interfacing with an IMS 25.

The NS 23 sends one or more SEP requests to the IMS 25 and receives one or more responses from the IMS 25. A request (and its retransmissions) together with the responses triggered by that request make up a SEP transaction. All responses to a request contain the same values in the Call-ID, CSeq, To, and From, as shown in the examples below. This allows responses to be matched with requests. The functions served by these parameters are commonly known in the art. A successful SEP invitation consists of two requests, ENVITE followed by an

ACK request. The ACK request following an ENVITE is not part of the transaction since it may traverse a different set of hosts. The INVITE request asks the called party to join a particular conference or establish a two-party conversation. After the called party has agreed to participate in the call by responding with, for instance, a 200 OK message, the caller confirms that it has received that response by sending an ACK request. If the caller no longer wants to participate in the call, it sends a BYE request instead of an ACK. The INVITE request typically contains a session description that provides the called party with enough information to join the session. The session description enumerates the media types and formats that the caller is willing to use and where it wishes the media data to be sent. If the called party wishes to accept the call, it responds to the invitation by returning a similar description listing the media it wishes to use. /USOO/41985

The SEP INVITE request of the current invention includes an additional header added by the NS 23. The added header will use the SEP Require header protocol extension mechanism. The Require header is used to tell the IMS 25 about the options that must be supported. The proposed format for this header includes a suitable tag, such as:

Required: org.ietf.messaging

and the following parameters: messaging-param= "action- '("deposit"|"retrieval") deposit-type= "dtype^'C'cfu' 'cfb'T'cfna")

where the action parameter identifies whether a deposit or retrieval operation is being performed and the dtype parameter determines the call forwarding condition. The dtype parameter, which is required only for deposit actions, includes values: cfu, for call forwarding unconditional; cfb, for call forwarding busy; and cf a, for call forwarding no answer.

The NS 23 adds the Require header and associated parameters to the SIP INVITE request forwarded to the IMS 25 by the NS 23. The NS 23 must first establish whether a called party, being an IMS account user, has selected to have all calls unconditionally forwarded to his message mailbox in the IMS 25. This information is acquired from the called party by the NS 23 via a call made by the called party to the NS 23 when the called party activates the unconditional call forwarding feature on the called party's telephone, or other communicating device. The NS 23 determines whether a called party is busy as a result of receiving a busy response, such as "486 Busy Here", in response to the INVITE request from the NS 23 to the called party during initial call setup. The NS 23 determines whether a called party is not answering as a result of receiving a request timeout in response to the INVITE request from the NS 23 to the called party during initial call setup.

The call flow for general IP call setup between a calling party and a called party using the SEP protocol is well known in the art and not detailed herein to avoid unnecessarily obscuring the invention. The present invention therefore focuses on the method of communications required between the NS 23 and IMS 25, and more particularly the addition of the Require header and its associated parameters.

Referring to FIG. 2, a method of depositing a message into the IMS 25 begins with a call setup and routing to the called party as described above and as represented in step 200. In step 205 the NS 23 determines if the called party has previously activated the unconditional call forwarding feature. If the unconditional call forwarding feature has been activated by the called party, the NS 23 sends an SIP INVITE request to the

IMS 25 which includes the additional Require header with the parameters action=deposit and dtype=cfu in step 206 to indicate an unconditional call forwarding message deposit. However, if the unconditional call forwarding feature has not been activated by the called party, the NS 23 determines if a busy response, such as 486 Busy Here, is received in response to the INVITE request from the NS 23 to the called party during initial call setup in step 210. If a busy response is received, the NS 23 sends an SIP INVITE request to the IMS 25 which includes the additional Require header with the parameters action=deposit and dtype=cfb in step 211 to indicate a conditional busy call forwarding message deposit. However, if the busy response is not received by the NS 23, the NS 23 determines if the called party is not answering in step 215, or more particularly, whether a request time-out has been received by the NS 23 in response to the INVITE request from the NS 23 to the called party during initial call setup. If a request time-out is received, the NS 23 sends an SIP INVITE request to the IMS 25 which includes the additional Require header with the parameters action=deposit and dtype=cfna in step 216 to indicate a conditional no answer call forwarding message deposit. However, if the request time-out is not received by the NS 23, the NS 23 determines if the NS 23 receives a connect signal in step 245 and completes the call setup to the called party in step 250. In steps 206, 211, or 216, a typical SIP INVITE request call flow sent from the

NS 23 to the IMS 25 including the additional SIP Require header is shown below:

INVITE sip:IMS- ailbox-id@ims.wco .com SIP/2.0

VIA: SIP/2.0/UDP calling-host.com VIA: SIP/2.0 UDP ns.wcom.com

Record-Route: <sip:ns.wcom.com>

From; Calling User <sip:calling-user@caUing-host.corn>

To: Called User <sip:called-user@sip.wcorn.com>

Callid: 123456@calling-host.com CSeq: 1 INVITE Contact: <sip:calling-user@calling-host.com> Required: org.ietf. messaging action=deposit dtype— cfb Content-Type: application/sdp

Content-Length: ... v=0 o=UserA 28908445262890844526 IN IP4 clicnt.hcrc.coui t=0 0 t=0 0 c= _N IP4 100.101.102.103 m=audio 49170 RTP/AVP 0 a=τtpmap:0 PCMU/8000

In the above example the dtype parameter selected contains the value cfb, indicating a conditional busy call forwarding deposit operation, as in step 210. This parameter would differ for the SIP INVITE request of steps 205 and 245 and would instead be cfu and cfha, respectively. In any case, the EMS 25 responds to the SIP INVITE request by sending a 200 OK message to the NS 23 in step 225, indicating that the request was successful and the IMS

25 has agreed to participate in the call with the NS 23. A typical response is shown below:

SIP/2.0 200 OK

VIA: SIP/2.0 UDP calling-host.com

VIA: SIP/2.0 UDP ns.wcom.com

Record-Route: <sip:ns.wcom.com>

From: Calling User <sip:caUing-user@calling-host.com> To: Called User <sip:called-uscr@sip.wcom.com>

Callid: 123456@calling-host.com

CSeq: 1 INVITE

Contact: <sip:IMS-mailbox-id @ims. com.host.com>

Content-Type: application sdp Content-Length: ... v=0 o=UscιB 2890844527 2890844527 IN IP4 clicnt.therc.com r=0 0 t=0 0 c=IN IP4 110.111.112.113 m=audio 3456 RTP/AVP 0 a=rtpmap:0 PCMU/8000 The NS 23 then confirms that it has received a final response to the SIP INVITE request in step 230 by sending an ACK message to the IMS 25, typically as shown below:

ACK sip:IMS-mailbox-id@ims.wcoπLCom SIP/2.0

VIA: SIP/2.0 UDP calling-host.com VIA: SIP/2.0 UDP ns.wcom.com Route: <sip:calling-user@calling-host.com > From: Calling User <sip:calling-user@calung-host.com> To: Called User <sip:called-user@sip.wcomxorn>

Callid: 123456@calling-host.com CScq: 1 ACK Content-Length: 0

The message, being of video or voice content, is then deposited into the called party's mailbox address, the called party being an IMS account user, by the IMS 25 in step 235. Communication is then terminated via normal SIP BYE processing in step 240. A method of retrieving a deposited message in accordance with the present invention is illustrated in FIG. 3. Referring to FIG. 3, an IMS account user is notified of a message having been deposited into the user's mailbox via a call placed by the IMS 25 activating a message alert feature on the user's phone, or other communicating device, in step 300. The user's subsequent call to retrieve the deposited message is setup and routed to the IMS 25 by the NS 23 in step 300. The content of SIP INVITE request will vary according to three possible scenarios, as determined in steps 305 and 340. However, in any case the SEP INVITE request will include the additional Require header with only the action=retrieval parameter.

In step 305, if the IMS account user's account information has been authenticated by the NS 23, the call flow between the NS 23 and IMS 25 will, for example, be as follows, beginning with step 310 in which the NS 23 sends the SIP INVITE request.

INVITE sip:IMS-account-id@ims.wcom.coιn SIP/2.0

VIA: SIP/2.0/UDP calling-hosLcom

VIA: SIP/2.0/UDP ns.wcom.com Record-Route: <sip:ns.wcom,corα>

From: Calling User <sipxalujig-user@callu.ag-host.com>

To: voicemail <siρ:voicemail@sip.wcom.com>

Callid: 123456@calling-host.com

CSeq: 1 INVITE Contact: <sip:calling-user@calling-host.com> Required: org.ietr.messaging action=retrieval

Content-Type: application/sdp Content-Length: ... v=0 o=UserA 28908445262890844526 IN IP4 client.here.com t=0 0 t=00 c=IN IP4 100.101.102.103 m=audio 49170 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The EMS 25 responds to the SEP INVITE request by sending a 200 OK message to the NS 23 in step 315, indicating that the request was successful and the IMS 25 has agreed to participate in the call with the NS 23. A typical response is shown below.

SIP/2.0200 OK VIA: SIP/2.0 UDP calling-host.com

VIA: SIP/2.0 UDP ns.wcom.com

Record-Route: <sip:ns.wcom.com>

From; Calling User <sip:calling-user@calling-host.com>

To: voicemail <sip:voiccmail@siρ.wcom.com> Callid: 123456@calling-host.com

CSeq: 1 INVTTE

Contact: <siρ:IMS-mailbox-id @ims.wcom.host.com>

Content-Type: application sdp

Content-Length: ... v=0 o=UscrB 2890844527 2890844527 IN IP4 clienLthere.com t=O 0 t=00 c=IN IP4 110.111.112.113 m=audio 3456 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The NS 23 then confirms that it has received a final response to the SIP INVITE request in step 320 by sendmg an ACK message to the EMS 25, typically as shown below.

ACK sip:IMS-mailbox-id@ims.wcom.com SEP/2.0 VIA: SIP/2.0 UDP calling-host.com

VIA: SIP/2.0 UDP ns.wcom.com

Route: <sip:calling-user@calling-host.com >

From: Calling User <sip:calling-user@caliing-host.com>

To: voicemail <sip:voiceroail @sip.wcom.com> Callid: 123456@calling-host.com

CSeq: 1 ACK O/41985

Content-Length: 0

In the above scenario, no prompting is required since the IMS account user's information is authenticated and, in step 325, the IMS 25 uses the account information indicated in the INVITE request Uniform Resource Locator (EJRL). Thereafter, the calling user is granted access to the mailbox in step 410 and the message is retrieved in step 415, which is followed by normal SEP BYE processing at step 420 to end the call On the other hand, if the IMS account user cannot be authenticated in step 305, and the user is accessing the IMS 25 from a device that has a default IMS account associated with it in step 340, the procedure instead continues to step 345, providing an

SIP INVITE request from the NS 23 to the EMS 25 as follows, for example:

INVITE sip:MS-accound-id:????@irns.wcom.com SIP/2.0

VIA: SIP/2.0 UDP calling-host.com VIA: SIP/2.0/UDP ns.wcom.com

Record-Route: <sip:ns.wcom.com>

From: Calling User <sip.calling-user@calliιιg-host.com>

To: voicemail <sip:voicemail@sip.wcom.com>

Callid: 123456@calling-host.com CSeq: 1 INVITE

Contact: <sip:calling-user@calling-host.com>

Required; org.ie.f.messaging action=retrieval

Content-Type: application/sdp Content-Length: ... v=0 o=UserA 2890844526 2890844526 IN IP4 client.heie.com t=0 0 t=0 0 c=IN IP4 100.101.102.103 m=audio 49170 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The IMS 25 responds to the SEP INVITE request by sending a 200 OK message to the NS 23 in step 350, indicating that the request was successful and the IMS 25 has agreed to participate in the call with the NS 23. A typical response is shown below:

SIP/2.0 200 OK

VTA: SIP/2.0 UDP calling-host.com

VIA: SIP/2.0/UDP ns.wcom.com

Record-Route: <sip:ns.wcom.com>

From: Calling User <sip:calling-user@calling-host.com> To: voicemail <sip:voicernail@sip.wcom,com>

Callid: 123456@calling-host.com CSeq: 1 INVITE

Contact: <sip:IMS-mailbox-id @ims.wcom.hosLcom> Content-Type: application/sdp Content-Length: ... v=0 o=UserB 2890844527 2890844527 IN EP4 client.thcre.com t=0 0 t=0 0 c=IN IP4 110.111.112.113 m=audio 3456 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The NS 23 then confirms that it has received a final response to the SEP INVITE request in step 355 by sending an ACK message to the EMS 25, typically as shown below:

ACK sip:IMS-mailbox-id@ims.wcom.com SEP/2.0 VIA: SIP/2.0 UDP calling-host.com

VIA: SIP/2.0 UDP ns.wcom.com

Route: <sip:calling-uscτ@calling-bost.com >

From: Calling User <sip:caUing-user@calling-host.com>

To: voicemail <sip:voicemail @sip. com.com> Callid: 123456@calling-host.com

CSeq: 1 ACK

Content-Length: 0

The SEP ENVITE request above contains the accoimt information, with no password authentication. At this point, the IMS 25 prompts the calling EMS account user for a password to verify the account contained in the INVITE request EJRL in step 360.

If the account is verified, the procedure continues to steps 410-420 as described above.

If, however, the password entered is incorrect, or the user indicates he or she is calling from a device with a default account assigned to it corresponding to another user's account, then the IMS 25 prompts the user for a user name and password in step 395 and continues to step 400 as described below.

However, if in step 340, the IMS account user is accessing the IMS 25 from a gateway or other device that does not have a default IMS account assigned to it, the NS

23 sends an account unknown SEP INVITE request to the IMS 25 in step 380 as shown below:

INVITE sip:UNKNOWN@ims.wcom.com SIP/2.0 VIA: SIP/2.0 UDP calling-host.com VIA: SIP/2.0/UDP ns.wcom.com Record-Route: <sip:ns.wcom.com> From: Calling User <sip:calling-user@calling-host.com> To: voicemail <sip:voicemail@sip.wcom.com> Callid: 123456@calling-host.com

CSeq: 1 INVITE

Contact: <sip:calling-user@calling-host.com> Required: org.ietf.messaging action=retrieval Content-Type: application/sdp

Content- Length: ... v=0 o=UserA 2890844526 2890844526 IN EP4 client.here.com t-0 0 t=0 0 <img file="WO0139441A1_D0001.tif" /> m=audio 49170 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The IMS 25 responds to the SIP INVITE request by sending a 200 OK message to the NS 23 in step 385, indicating that the request was successful and the IMS 25 has agreed to participate in the call with the NS 23. A typical response is shown below:

SIP/2.0 200 OK

VIA: SIP/2.0/UDP calling-hostcom

VIA: SIP/2.0/UDP ns.wcom.com

Record-Route: &lt;sip:ns.wcom.com&gt; From: Calling User &lt;sip:calling-user@calling-hosLcom&gt;

To: voicemail &lt;sip:voicemail@sip.wcom.com&gt;

Callid: 123456@calIing-host.com

CSeq: 1 INVITE

Contact: &lt;sip:IMS-mailbox-id @ims.wcom.host.com&gt; Content-Type: application/sdp

Content-Length: ... v=0 o=UserB 2890844527 2890844527 IN IP4 client.there.com t=0 0 t=0 0 c=IN IP4 110.111.112.113 m=audio 3456 RTP/AVP 0 a=rtpmap:0 PCMU/8000

The NS 23 then confirms that it has received a final response to the SIP INVITE request in step 390 by sending an ACK message to the IMS 25, typically as shown below:

ACK sip:IMS-mailbox-id@ims. com.com SIP/2.0 VIA: SIP/2.0/UDP calling-host.com VIA: SIP/2.0/UDP ns.wcom.com Route: &lt;sip:calling-user@calling-host.com &gt; From: Calling User &lt;sip:calling-uscr@calling-host.com&gt; To: voicemail &lt;sip:voiccmail @sip.wcoaι.com&gt;

Callid: 123456@calling-host.com CSeq: 1 ACK Content-Length: 0 In this case, the SEP INVITE request contains no account or authentication information, but only the identifier UNKNOWN in the INVITE request URL. Accordingly, in step 395, a calling party is prompted for a user name and password. If the account is verified in step 400, the procedure continues to steps 410-420 as described above. However, if the user name and password is entered incorrectly, the user is allowed a predetermined number of re-entry attempts in step 405 before the operation is aborted, ending the call in step 406.

While the present invention has been described in detail with reference to the preferred embodiments, they represent mere exemplary applications. Thus, it is to be clearly understood that many variations can be made by anyone of ordinary skill in the art while staying within the scope and spirit of the present invention as defined by the appended claims.