Patent Application
20080095078
The present invention exists in the construction, arrangement, and combination of the various parts of the device, and steps of the method, whereby the objects contemplated are attained as hereinafter more fully set forth, specifically pointed out in the claims, and illustrated in the accompanying drawings in which:
Referring now to the drawings wherein the showings are for purposes of illustrating the exemplary embodiments only and not for purposes of limiting the claimed subject matter,
As shown generally,
The example implementation of the CPDRA feature provided herein, which should not be considered limiting, uses an IMS compatible call based on Session Initiation Protocol (SIP) sent from the Originating End 12 to the Terminating End 14 across the IMS network 16. The SIP messaging protocol performs session control, including creating, modifying and terminating multimedia sessions supporting both packet-switched and circuited phone systems.
A Calling Party 20 uses a Calling Party terminal 22, also referred to as User Equipment (UE) or a phone, located at the Originating End 12 of the network 10, to place a call to a Called Party Destination 24, also referred to as the Called Party terminal, or UE, or phone, located at the Terminating End 14. The Calling Party 20 and Calling Party Terminal 22 are, therefore, defined as Originators, since the call originates therefrom. The Calling Party terminal 22 can be a wireless or cellular terminal, a landline terminal, an IMS terminal, a VOIP terminal, or other device or system capable of making, or originating, the call.
The Called Party terminal 24 can be a wireless or cellular terminal, a landline terminal, an IMS terminal, a VOIP terminal or other device capable of receiving the call. In the example provided, the Called Party terminal 24 is a SIP enabled device. Calls are typically routed to the Called Party terminal 24 using a Directory Number, also known as a phone number, for that destination via Call Control Messaging, examples of which can include SIP messaging. The Directory Number can also be a Universal Resource Locator (URL) for use with IP-based networks.
An Originating Call Control Entity 30 serves the Calling Party Terminal 22 by setting up the call and routing the call towards the Terminating End 14 using call control messaging as shall be described in further detail below. The Originating Call Control Entity 30 is, therefore, also referred to as an Originator, and is disposed at the Originating End 12 of the network 10.
A Terminating Call Control Entity 34 serves the Called Party 26, receiving the call control messaging from the Originating Call Control Entity 30, and setting up and routing the call to the proper Called Party destination 24. The Terminating Call Control Entity 34 is located at the Terminating End 14 of the network 10. The Originating and/or Terminating Call Control Entities 30, 34 can be 5 ESS switches, IMS-compatible systems, UMTS/CDMA/GSM Mobile Switching Centers, or other network nodes suitable for the corresponding network 10.
A Subscriber Database 36, also known as a Home Location Register (HLR) or Home Subscriber Server (HSS) is connected to the Originating Call Control Entity 30 for storing subscription information for the Calling Party. The Subscriber Database 36 can store the audio media used for the Ring Announcement as described in further detail below.
A User Interface (UI) 40 is provided for enabling the Calling Party 20 to designate Ring Announcements, creating them and storing them in a manner as described below. The UI 40 can be located in the Calling Party UE 22. Alternatively, the UI 40 can be provided by the network 10 such as on an Application Server which can be accessed by the Calling Party via his/her UE 22 or via a computer 50 connected thereto by the Internet 52. The UI 40 can even be provided by the Service Provider in the form of an operator or an automated system recognizing voice commands if so desired.
The system and method of call delivery described herein includes providing an indicator in call control signaling sent from the Originating End 12 of the network to the Terminating End 14 which indicates that the call is to be a CPDRA call. The indicator, referred to herein as a CPDRA Indicator (CPDRAI), can be a SIP command or it can be included in a SIP command such as by using Session Description Protocol (SDP) as described in further detail below. The CPDRA call provides a Ring Announcement (RA) that has been designated by the Calling Party to the Called Party terminal 24 for providing an audible alert, referred to herein as a Ring Announcement, indicating that the terminal is receiving an incoming call. The CPDRA Indicator can be considered to be an Originator-initiated indicator, because the Terminating End 14 is not required to request, or prompt, the Originator to provide the indicator.
Referring now to
The Calling Party then designates a CPD Ring Announcement at 104. The Calling Party can designate the CPDRA, also referred to as the RA, in a variety of ways. Referring now to
The User Interface 40 prompts the Calling Party 20 to provide the Ring Announcement at 1042 and the Calling Party provides the Ring Announcement at 1043. The Calling Party 20 can provide a spoken Ring Announcement via the UE 22 by speaking it into the UE microphone for recording, or via the computing device 50 and network connection 52 by speaking it into the computing device's microphone and transmitting it to the UI 40 for recording as a known audio file, also known as audio media content files. Alternatively, the Calling Party 20 can record a non-spoken Ring Announcement by playing it into the microphone of the UE 22 or computing device. As another alternative, the Calling Party 20 can provide a pre-recorded audio file to the UE 22 or the UI 40. Examples of such files can include, but are not limited to a .wav file, any suitable MPEG file, an MP3 file, or other known audio files, also known as audio media content files.
Next, it is determined if the Ring Announcement is to be saved for future calls at 1044. If the Ring Announcement is to be saved for use for future calls, the audio file is saved at 1045 and identified by an indicator, such as using a file name or a file location. The Ring Announcement audio file can be saved in the memory of the UE 22, or it can be saved on the network such as in the HSS or Subscriber Database 36.
The Calling Party 20 chooses the Ring Announcement to be used for the outgoing call at 1046. The Calling Party 20 can select the Ring Announcement on a per-call basis. For example, the Calling Party can select the Ring Announcement when making the outgoing call at 106 below. For Ring Announcements selected on a per-call basis, the Calling Party can designate a Ring Announcement recorded just prior to, or as part of, the current outgoing call, whether this RA was saved in 1045 or not. For example, the Calling Party can record a one-time RA in 1043, such as speaking “Hey Bob, it's John Doe calling”, and use this RA during the current outgoing call. Or, the Calling Party can select a pre-recorded RA audio file stored in the network 10 or in the UE 22 as described above for the current outgoing call.
The Calling Party can also select the Ring Announcement in 1046 based on the Called Party, such that a specific RA, saved in 1045 above, can be associated with a Called Party, or a group of Called Parties if so desired. The Calling Party can make this selection and association at any time, including prior to making the outgoing call. This selection can be made via the UI 40 using the UE 22 or a computer 50 connected thereto. The association between the RA and the Called Party can be saved in the UE 22 or it can be saved on the network 10 such as at the serving MSC 30. In this manner, the CPDRA is automatically selected when the Calling Party 20 calls the Called Party 26. The Calling Party 20 can select a different RA for a particular Called Party and store this association at any time. The Calling Party 20 can also use the same CPDRA for every outgoing, regardless of the Called Party, if so desired. In this example, the Originating Call Control Entity receives the same Ring Announcement from the UE 22 via a SIP message using the SDP protocol, or alternatively it retrieves the same one from the network 10 and sends it to the Terminating Call Control Entity 34 via a SIP message using the SDP protocol for every call made thereto.
Referring again to
In the example provided herein, a SIP Invite Request message is sent from the Calling Party terminal 22 to the Originating Call Control Entity 30, and then to the Terminating Call Control Entity 34 via the IMS network 16. The SIP Invite message 60 includes the CPD Ring Announcement indicator 62, indicating that the call is to be a CPDRA call. The CPDRAI 62 is a SIP compatible indicator, which can include a new SIP command. The SIP Invite Request message also includes the Ring Announcement including the audio media to be played by the Called Party terminal 24. If the Ring Announcement media content is stored in the network 10, the Originating Call Control Entity retrieves it and includes the audio media clip in the SIP call control messaging. For example, the audio content used for Ring Announcement can be included in the SIP Invite Request using SDP.
Next, it is determined whether the Called Party terminal 24 allows CPDRA calls at 108. The Terminating Call Control Entity 34 determines this using suitable logic. If the Called Party allows CPDRAs, the caller's ring announcement is played by the Called Party terminal 24 at 110, in lieu of a customized ring tone or a standard ring tone, to alert the Called Party 26 of an incoming call. For example, the Calling Party's custom Ring Announcement of “Hey Bob, it's John Doe calling” is played by the Called Party terminal 24 as an alert. Normal Call handling is then used hereinafter at 114.
If it is determined that the Called Party terminal 24 does not allow CPDRAs at 108, the RA is stripped from the SIP Invite Request message and a standard ring announcement, or one designated by the Called Party, is played at 112. Normal Call handling is then used hereinafter at 114.
The above description merely provides a disclosure of particular embodiments of the invention and is not intended for the purposes of limiting the same thereto. As such, the invention is not limited to only the above-described embodiments. Rather, it is recognized that one skilled in the art could conceive alternative embodiments that fall within the scope of the invention.
