Patent Application
20080084980
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,
A Calling Party 20 uses a Calling Party terminal 22, located at the Originating End 12 of the network 10, to place a call to a Called Party Destination 24, 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, an IP terminal or other device or system capable of making, or originating, the call.
The Called Party Destination 24 can be a wireless or cellular terminal, a landline terminal, an IMS terminal, an IP terminal or other device capable of receiving a call. The Called Party Destination 24 can also be the Called Party's Voice Mail system, or an alternate network-based message recording system different from the Called Party's ordinary Voice Mail system, capable of receiving a call. Calls are typically routed to the Called Party Destination 24 using a Directory Number, also known as a phone number, for that destination. 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 14.
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 Terminating Call Control Entity 34 can also route the call to a Called Party's Call Forwarding Destination 40 using a Forward-to Directory Number, as shall be described in further detail below. The Called Party's Call Forwarding Destination 40 can be a Voice Mail system, or other network-based voice recording system, capable of receiving the Calling Party's call routed thereto using a Forward-to Directory Number.
The Originating and/or Terminating Call Control Entities 30, 34 can be 5ESS switches, IMS-compatible systems, UMTS/CDMA/GSM Mobile Switching Centers, or other network nodes suitable for the corresponding network 10.
A Service Control Point (SCP) 50 is connected to the Terminating Call Control Entity 34 for providing services to the Called Party such as call screening, as shall be described in further detail below. The SCP 50 can be an Application Server or other processing node suitable for the corresponding network 10.
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 call forwarded without ringing the Called Party's Destination 24 as defined by the dialed Called Party Directory Number. This can occur regardless of the status of the dialed Called Party's Destination 24, such as it being busy, or not answered. This can also occur without a conventional Call Forwarding Attendant relationship between the Terminating Call Control Entity 34 and the Called Party 26. The indicator can be considered to be an Originator-initiated indicator, because the Terminating End 14 does not request, or prompt, the Originator to provide the indicator.
The system and method of call delivery described herein is independent of access, network, and signaling technology, and thus could be used with landline, cellular, an Internet Protocol Multimedia Subsystem (IMS), among others, or suitable combinations thereof.
A method for providing Originator Initiated Direct-to-Call Forwarding Destination (OIDTCFD) call delivery shall now be described. In the example provided herein, which should not be considered limiting, a Calling Party 20 calls a Called Party 26, but wants to leave a Voice Mail message for the Called Party rather than speaking to her. Utilizing the invention as described herein, the Calling Party 20 uses the Calling Party Terminal 22 to make an OIDTCFD call which does not ring the Called Party Destination 24 having the Directory Number the Calling Party has just dialed. Instead, the call is forwarded directly to the Called Party's Call Forwarding Destination using a Forward-to Directory Number as described in further detail below. The Calling Party 20 does not need to know the Forward-to Directory Number to reach this Called Forwarding Destination. Further details, features and advantages of the invention shall be described below.
Referring now to
The Originating Call Control Entity 30 determines that the call is to be an OIDTCFD call at 106 using logic which recognizes the dialed feature code digits as signifying the associated call is to be an OIDTCFD call.
The Originating Call Control Entity 30 begins to set-up the call for routing the call to the Terminating Call Control Entity 34 serving the Called Party 26 utilizing the Called Party Directory Number that the Calling Party has dialed. During call set-up, the Originating Call Control Entity 30 generates an OIDTCFD indicator at 108. The OIDTCFD indicator can be a special bit, a flag, a command, or other portion of a call control message capable of notifying the Terminating End 14 that the associated call is an OIDTCFD call and is to be handled as described herein.
The Originating Call Control Entity 30 can optionally save information in a billing record at 110 indicating that the Calling Party 20 has made/requested an OIDTCFD call to bill the Calling Party 20 for this service, if so desired. Step 110 can occur later in this call delivery process, such as for example while the call is being delivered to the Call Forwarding Destination or afterwards.
The Originating Call Control Entity 30 can optionally inform the Calling Party that OIDTCFD charges apply to the call at 112.
At step 114, the Originating Call Control Entity 30 sends the OIDTCFD indicator across the telecommunications network to the Terminating Call Control Entity 34 at the Terminating End 14. The OIDTCFD indicator notifies the Terminating Call Control Entity 34 that the call is an OIDTCFD call which is to be sent directly to the Called Party's Call Forwarding Destination 40 without ringing the Called Party Destination 24 as defined by the Directory Number dialed by the Calling Party in step 102.
The Originating Call Control Entity 30 sends the OIDTCFD indicator 60 to the Terminating Call Control Entity 34 in a call control message 62 shown in
Some examples, which should not be considered limiting, include the OIDTCFD indicator being sent in a SIP INVITE call control message, or an ISUP Initial Address Message (IAM) message, among others.
The OIDTCFD indicator is Originator-Initiated because no node at the Terminating End 14, such as for example an Attendant or the Terminating Call Control Entity 34, prompts or requests the Originator to provide the OIDTCFD indicator. Rather, the Originator, such as the Originating Call Control Entity 34 or the Calling Party Terminal 22, generates the OIDTCFD indicator and sends it to the Terminating End 14 to notify the Terminating End that the call is to be Forwarded directly to the Called Party's call forwarding destination.
The Terminating Call Control Entity 34 receives the OIDTCFD indicator in the call control messaging and examines the Called Party's subscriber information at 116. The Terminating Call Control Entity 34 can use this information to determine whether to proceed with the call at 118.
For example, a Service Provider can provide this system and method of call delivery only to subscribing parties, if so desired. Alternatively, it can be provided to all parties. If a subscription is required, the Terminating Call Control Entity 34 can determine whether or not the Called Party 26 subscribes to this service using Called Party subscriber information stored in a subscribe database and associated with the Called Party in a known manner. The subscriber database can be stored at the Terminating Call Control Entity 34, on the Called Party's Home Location Register (HLR), or in other suitable locations/nodes in the network 10. If the Called Party 26 does not subscribe, the Terminating Call Control Entity 34 can end the call at 120.
Other conditions, besides the existence of subscription privileges, can be used by the Terminating Call Control Entity 34 in determining whether to proceed with the call at 118. For example, the Called Party can pre-provision a directive to inhibit any OIDTCFD calls made to them. In this example, the Terminating Call Control Entity 34 can obtain this directive from the subscriber information obtained in 116 and will determine at 118 to end the call at 120.
After being notified by the OIDTCFD indicator that the incoming call is to be directly forwarded to the Called Party's Call Forwarding Destination, the Terminating Call Control Entity 34 at 122 determines the appropriate Forward-to Directory Number needed to route the call thereto. The Terminating Call Control Entity 34 can determine the Forward-to Directory Number in a variety of different ways.
The Called Party 26 may provide a specific Forward-to Directory Number for OIDTCFD calls made to the Called Party. The Called Party 26 can pre-provision the network with this Directory Number and it can be stored in the network, such as for example in subscriber database. This Directory Number may by the same as the Forward-to Directory Number of other types, or “flavors”, of Call Forwarding which cause the call to be forwarded to the Called Party's Voicemail System.
If a Forward-to Directory Number specific to the OIDTCFD service has not been provisioned by, or for, the specific Called Party 26, the Terminating Call Control Entity 34 may be provisioned with global settings to use the Forward-to Directory Number of a particular type of Call Forwarding Destination. For example, the Forward-to Directory Number typically used for Call Forwarding when the Called Party Destination 24 does not answer can also be used for OIDTCFD calls. Alternatively, the global setting may dictate that the Terminating Call Control Entity 34 use the same Forward-to Directory number for all OIDTCFD calls made to all subscribers to send all such calls to the same Voice Mail system destination number.
The Terminating Call Control Entity 34 then routes the call at 124 to the Called Party's Call Forwarding Destination 40 using the Forward-to Directory Number determined in step 122. For example, the Forward-to Directory Number for the Called Party's Voice Mail system is used to forward the call thereto. The Terminating Call Control Entity 34 did not ring the Called Party Destination 24 defined by the Directory Number dialed by the Calling Party in step 102 above, and thus did not determine the availability of the Called Party destination.
However, the Terminating Call Control Entity 34 can provide an optional indication to the Called Party Destination 24 at 126 that the Called Party has/is receiving an OIDTCFD call. This can occur either before, during or after the Calling Party is leaving/has left the recorded voice message at the Call Forwarding Destination as described below. Examples of providing such an indication can include the Terminating Call Control Entity 34 providing a ping ring to the Called Party Destination 24. The ping ring provides an audible indication to the Called Party phone 24 that someone is trying to reach the Called Party such as by an OIDTCFD call. A bearer path capable of providing voice communications is not established, or attempted to be established, to the Called Party phone 24 during a ping ring, as would happen when the ringing the Called Party Destination. Other examples can include, but are not limited to, the Terminating Call Control Entity 34 sending such an indication via call control messaging, or via other forms of messaging to light an indicator light on the Called Party Destination phone 24 or enabling the phone to give such an indication via a symbol displayed on the screen, or sending a text message to the phone 24.
At step 128, the Terminating Call Control Entity 34 can also send the OIDTCFD indicator to the Called Party's Voice Mail system 40 in the forwarded call leg in a manner in which it can be associated with the call, such as for example via call control messaging as indicated at 66 in
The Voice Mail system 40 records the spoken message from the Calling Party 20 at 132 to generate a Voice Mail message for the Called Party 26.
Additionally, if so desired, the Voice Mail system 40 can prompt the Calling Party 20 for a delivery time for this Voice Mail message at 134. The Calling Party 20 can indicate the time she would like to have the Voice Mail message delivered to the Called Party 26, such as, for example, the time at which the Called Party is alerted to having received the Voice Mail message. The Voice Mail System delivers the Voice Mail message to the Called Party at 136.
The Voice Mail system 40 can notify the Called Party 26 at 138 that the Calling Party 20 has left a Direct-to-Call Forwarding Destination Voice Mail message without ringing the Called Party's phone using the OIDTCFD indicator saved in step 130.
Referring now to
Referring now to
Referring now to
The system and method of call delivery described herein enables the Calling Party, rather than the Attendant/Call-Taker on the Terminating End 14, to direct the call to the Called Party's Voice Mail system as defined by the suitable Forward-to Directory Number. It does not require the Calling and Called Parties to be served by the same switch, and it does not require any type of relationship (e.g. coverage service) between the Calling Party 20 and the Called Party 26. Also, the Called Party Directory Number dialed by the Calling Party is not rung, though a “ping ring” may optionally be used.
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.
