Customer premises call handling
Summary by NHIP
Customer Premises Call Routing
The system receives incoming voice calls at a customer premises and distinguishes the intended recipient based on call destination data. It forwards the call to a single shared voice mail box containing multiple prompts, playing the specific prompt associated with the identified recipient.
Claim Score by NHIP
Abstract
A computer readable storage medium holding a program element for execution by a processor for processing voice calls. The program element comprises an input interface to receive at a customer premises a signal carrying a call request indicative of an incoming voice call, wherein the call request includes a call destination identifier. Also present, a processing element at a customer premises coupled to the input interface. The processing element processes the call destination data to distinguish the call destination identifier from other call destination identifiers that the signal can carry. The processing element also processes the call request to select a handset to which the incoming call is to be linked on the basis of the call destination identifier and links the voice call to the handset. Also provided are a telephone system and method and a telephone system and method involving forwarding calls to voice mail services.

Term
Projected expiry 2 February 2032.
- Priority and filed
- Granted
- Today
- Projected expiry
16 claims: 2 independent, 14 dependent
- 1Broadest claimClaim Score 46, average(NHIP)A method for processing voice calls directed to a connection leading to a customer premises, the method comprising:a) receiving at the customer premises a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier;b) distinguishing an intended recipient of the voice call from among a plurality of recipients susceptible to receive a voice call over the connection at least in part based on information contained in the call destination data;c) causing the voice call to be forwarded to a single voice mail box that is common to the plurality of recipients, the single voice mail box having a plurality of voice prompts, each of the voice prompts being associated with a respective one of the plurality of recipients;and d) playing one voice prompt of the plurality of voice prompts associated with the single voice mail box, wherein the one voice prompt that is played is determined based on the call destination data included in the call request.
- 7A telephone system, comprising:a) a set of handsets at a customer premises;b) a base station at a customer premises having: i) an input for connection to a connection leading to a customer premises, wherein the connection is capable of carrying voice calls;and ii) an input interface to receive a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier;c) a voice mail box that is common to a plurality of recipients;and d) a processing element at a customer premises coupled to the input interface for: i) distinguishing an intended recipient of the voice call from among a plurality of recipients susceptible to receiving a voice call over the connection at least in part based on information contained in the call destination data;ii) forwarding the incoming voice call to a single voice mail box that is common to the plurality of recipients, the single voice mail box having a plurality of voice prompts, each of the voice prompts being associated with a respective one of the plurality of recipients;and iii) playing one voice prompt of the plurality of voice prompts associated with the single voice mail box, wherein the one voice prompt that is played is determined based on the call destination data included in the call request.
Independent claims2
63 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
p-0002The present invention relates to telephony solutions and, in particular, to customer premises call handling.
BACKGROUND
p-0003In the past, certain local telephone service providers have offered a differentiated ringing service for households wanting to have two numbers on the same line. With this service, two different telephone numbers were associated to a same telephone line and all the phones at the customer premises rang either one of two ways, depending on the phone number called. Thus, when a caller dialed the first number, all the phones in the household ring one way and when the caller dialed the second number, all the phones rang a second, slightly different way.
p-0004While this service allowed users in a household to identify without picking up the intended recipient of incoming phone calls, it does not allow a user to avoid getting disturbed by telephone calls not intended for them. However, it is well known that different users in a household, workplace, or other premises may have vastly varying phone usage habits/requirements. Yet it can be very frustrating to a user to be constantly disturbed by phone calls intended for another user, particularly when he/she cannot allow himself to unplug the telephone for fear of missing an important call.
p-0005Today, POTS home telephony is being replaced by VoIP alternatives. VoIP systems provide users with home telephone systems analogous to POTS telephony but using packet-based networks such as the Internet instead of analog POTS networks for communicating. Advantageously, VoIP offers a number of options not available, or costly, on POTS systems and VoIP allows for data communication to supplement voice communication. As a result, VoIP systems tend to be more flexible and can do more than POTS-type telephony systems.
p-0006There is a need in the industry for a telephony system that mitigates at least one disadvantage of the prior art.
SUMMARY OF THE INVENTION
p-0007In accordance with a first broad aspect, the present invention provides a computer readable storage medium holding a program element for execution by a processor to implement a system for processing voice calls directed to a connection leading to a customer premises. The program element comprises an input interface to receive at a customer premises a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier. The program element further comprises a processing element at a customer premises coupled to the input interface. The processing element processes the call destination data to distinguish the call destination identifier currently conveyed in the signal from other call destination identifiers that the signal can carry over the connection. The processing element also processes the call request to select a handset among a set of handsets to which the incoming call is to be linked on the basis of the distinguished call destination identifier. The processing element also links the voice call to the selected handset.
p-0008In accordance with a second broad aspect, the present invention provides a method for processing voice calls directed to a connection leading to a customer premises. The method comprises the step of receiving at a customer premises a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier. The method further comprises the step of processing the call request at customer premises to distinguish the call destination identifier currently conveyed in the signal from other call destination identifiers that the signal can carry over the connection. The call request is also processed to select a handset among a set of handsets to which the incoming call is to be linked on the basis of the distinguished call destination identifier. The method also comprises the step of linking the voice call to the selected handset.
p-0009In accordance with a third broad aspect, the present invention provides a method for processing voice calls directed to a connection leading to a customer premises. The method comprises receiving at the customer premises a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier. The method further comprises processing the call destination data to distinguish the call destination identifier currently conveyed in the signal from other call destination identifiers that the signal can carry over the connection. The method still further comprises processing the call request at the customer premises to select a voice mail service among a set of voice mail services to which the incoming call is to be forwarded on the basis of the distinguished call destination identifier. The method also comprises processing the call request at the customer premises to cause the voice call to be forwarded to the selected voice mail service.
p-0010In accordance with a fourth broad aspect, the present invention provides a telephone system. The telephone system comprises a set of handsets at a customer premises. The telephone system further comprises a base station at a customer premises. The base station has an input for connection to a connection leading to a customer premises, wherein the connection is capable of carrying voice calls. The base station also has an input interface to receive a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier. The telephone system also comprises a processing element at a customer premises coupled to the input interface. The processing element processes the call destination data to distinguish the call destination identifier currently conveyed in the signal from other call destination identifiers that the signal can carry over the connection. The processing element further processes the call request to select a handset among the set of handsets to which the incoming call is to be linked on the basis of the distinguished call destination identifier. The processing element still further links the selected handset to the incoming call.
p-0011In accordance with a fifth broad aspect, the present invention provides a telephone system. The telephone system comprises a set of handsets at a customer premises. The telephone system further comprises a base station at a customer premises. The base station has an input for connection to a connection leading to a customer premises, wherein the connection is capable of carrying voice calls. The base station further has an input interface to receive a signal over the connection carrying a call request indicative of an incoming voice call, wherein the call request includes call destination data conveying a call destination identifier. The telephone system also has a set of voice mail services. The telephone system still further has a processing element at a customer premises coupled to the input interface. The processing element processes the call destination data to distinguish the call destination identifier from other call destination identifiers that the signal can carry over the connection. The processing element further processes the call request to select a voice mail service among the set of voice mail services at which the incoming call is to be forwarded on the basis of the distinguished call destination identifier. The processing element still further forwards the incoming voice call to the selected voice mail service.
p-0012These and other aspects and features of the present invention will now become apparent to those of ordinary skill in the art upon review of the following description of specific embodiments of the invention and the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
A detailed description of examples of implementation of the present invention is provided herein below with reference to the following drawings, in which:
<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of a customer premises telephony system in accordance to a non-limiting embodiment;
<figref idrefs="DRAWINGS">FIG. 2</figref> shows a handset for use in the system of <figref idrefs="DRAWINGS">FIG. 1</figref> in accordance to a non-limiting example of implementation of the invention;
<figref idrefs="DRAWINGS">FIG. 3</figref> shows a block diagram of the base station used in the system shown in <figref idrefs="DRAWINGS">FIG. 1</figref>;
<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow chart depicting an exemplary operation of the base station of <figref idrefs="DRAWINGS">FIG. 3</figref>; and
<figref idrefs="DRAWINGS">FIG. 5</figref> is a block diagram of a customer premises telephony system in accordance to a variant;
<figref idrefs="DRAWINGS">FIG. 6</figref> is a functional block diagram of the processing element shown in <figref idrefs="DRAWINGS">FIG. 3</figref>, illustrating in greater detail components for performing call recipient identification
p-0020In the drawings, embodiments of the invention are illustrated by way of example. It is to be expressly understood that the description and drawings are only for purposes of illustration and as an aid to understanding, and are not intended to be a definition of the limits of the invention.
DETAILED DESCRIPTION
p-0021<figref idrefs="DRAWINGS">FIG. 1</figref> shows a telephony system in accordance with a non-limiting example of implementation of the invention. A customer has, at customer premises <b>145</b>, a plurality of handsets <b>110</b> connected to a base station <b>105</b>. Base station <b>105</b> has a packet-based connection <b>125</b> for connecting to a network <b>140</b> (a packet based network) and exchanging telephony data therewith. The packet based connection <b>125</b> can be wireline (ex. cable, DSL, etc.) or wireless (ex. WiMax, EDGE, EVDO, CDMA, GSM etc.). Handsets <b>110</b> have respective handset connections <b>130</b> to base station <b>105</b> for exchanging telephony data therewith. Optionally, the base station <b>105</b> is in communication with a computer <b>115</b> via a local area network (LAN) connection <b>135</b>. The connections <b>130</b> may be wireless but they could be wireline or a combination of both.
p-0022Handset <b>110</b> can be any suitable user telephony interface but in the example illustrated in <figref idrefs="DRAWINGS">FIG. 2</figref>, handset <b>110</b> is a wireless telephone having a display screen <b>210</b>, a keypad <b>215</b>, a speaker <b>205</b> and a microphone <b>220</b>. Handset <b>110</b> includes a communication module (not shown) for communicating with base station <b>105</b> over handset connection <b>130</b>. In some embodiments, handset <b>110</b> communicates with base station <b>105</b> using the Digital Enhanced Cordless Telecommunications (DECT) protocol. In these embodiments, handset <b>110</b> does not need to be connected to a physical RJ11 or other phone jack. If handset <b>110</b> has a docking station, it needs only be a charger connected to a power outlet. In a non-limiting example, the base station <b>105</b> acts as an analog telephony adapter (ATA) and serves as a gateway for packet based telephony. Base station <b>105</b> may thus translate telephony information exchanged between packet based link <b>125</b> and handsets <b>110</b> as required. As such, the handsets <b>110</b> need not include VoIP-specific support but may be any handset communicating with base station <b>105</b> in any known manner. Therefore, it is to be understood that handset <b>110</b> may also be a POTS phone. One skilled in the art will appreciate that there are many possible configurations of handset <b>110</b> that can be used without departing from the intended scope of the invention. For example, handset <b>110</b> may have a very sophisticated display screen with a touch-screen input or may have a basic dot-matrix screen or no display screen at all. Likewise, although handset <b>110</b> is described here as communicating over the DECT protocol, this is not necessarily the case and any communication means, wired or wireless, can be used as a connection to base station <b>105</b>. While handset <b>110</b> has been shown here in a specific embodiment, any handset <b>110</b> known in the art can be used and handset <b>110</b> can therefore be a fax machine.
p-0023<figref idrefs="DRAWINGS">FIG. 3</figref> shows a block diagram representation of base station <b>105</b> in accordance with a non-limiting example of implementation of the invention. Here, base station <b>105</b> has a packet based interface <b>310</b> for exchanging packeted telephony information over a packet-based network <b>140</b>, such as the Internet. Packet based connection <b>125</b> may be an IP connection or any other suitable connection. Likewise, network <b>140</b> may be any suitable network including a public packet based network (e.g. the Internet), a private packet based network or any combination of public and private networks.
p-0024Base station <b>105</b> also has a plurality of handset interfaces <b>315</b> for interfacing with respective handsets <b>110</b>. Handset interfaces <b>315</b> may be suitable for permitting wireless or wireline exchanges with handsets <b>315</b>. Alternatively, a single handset interface may be provided to handle the communications between the base station <b>105</b> and the handsets <b>110</b>. For instance, a single handset interface <b>315</b> for communicating with all handsets <b>110</b> over, e.g., a single frequency may be utilized; with specific handsets <b>110</b> being addressed by an appropriate means such as by a handset-specific ID.
p-0025Furthermore, base station <b>105</b> further has a user-interface <b>320</b> that allows a user to interface with base station <b>105</b> such as to change settings. The user interface may have a display (not shown) and an input mechanism allowing the user to input commands and/or data. The input mechanism can be a keyboard and/or a pointing device. Alternatively, speech recognition or touch sensitive surfaces can be used. The input mechanism can include a limited set of keys to fit space restrictions (for instance, if the base station <b>105</b> is physically small) while allowing the user to input all the necessary commands. Another possibility is to provide soft keys that may use part of the display to identify their purpose or function.
p-0026Processing element <b>305</b> controls interfaces <b>310</b>, <b>315</b>, <b>320</b>, <b>325</b> and handles incoming calls in the manner described below.
p-0027Base station <b>105</b> may be implemented by any suitable means. In a non-limiting example, base station <b>105</b> has a dedicated hardware comprising a processor and a memory with computer-readable storage medium holding a program element for execution by the processor to implement the functionality of the system described herein. However, base station <b>105</b> may also be implemented by software (program element) for execution by a general-purpose computer, such as a customer's personal computer. One skilled in the art will appreciate that base station <b>105</b> may also be implemented by dedicated circuitry behaving in the manner described below.
p-0028Packet based interface <b>310</b> is provided mainly to establish and maintain the packet based connection <b>125</b> with a remote node of the network <b>140</b>. The packet based interface <b>310</b> sends and receives packeted telephony data over packet-based connection <b>125</b>. Telephony data includes voice information and optionally any other data such as, video information (video conferencing) and messaging. Telephony data also includes control and signaling data for example to establish telephone calls, monitor quality of service (QoS) and ensure synchronization. Thus, in a non-limiting example of implementation, telephony data includes SIP or H.323 based exchanges.
p-0029As mentioned above, Base station <b>105</b> may act as an ATA or otherwise be a translator between packet based connection <b>125</b> and handset <b>110</b>. To this end, base station <b>105</b> may include a packetizer/depacketizer, encoders/decoders (codecs) and/or an analog-to-digital converter (or vice versa) to transform telephony information exchanged between handsets <b>110</b> and packet based connection <b>125</b> as required. One skilled in the art will readily appreciate that many translation schemes are possible (the choice of which may depend at least in part on the nature of the packet based connection <b>125</b> and of the handset connection <b>130</b>) all of which are within the intended scope of the invention. For example, incoming telephony information may be decoded and digital-to-analog converted or be decoded and re-encoded differently or may even be exchanged between handsets <b>110</b> and packet based connection <b>125</b> unaltered. In the latter case, base station <b>105</b> may still transform information received over packet based connection <b>125</b> in order to analyze it.
p-0030Optionally, base station <b>105</b> will include a LAN interface <b>325</b> for exchanging data with a computer <b>115</b> at customer premises <b>145</b>. In a non-limiting embodiment, base station <b>105</b> serves as a modem or main connection to the Internet for customer premises <b>145</b>. In this example, a customer may have one or many computers <b>115</b> linked via local area network <b>135</b> to base station <b>105</b>. Here packet based interface <b>310</b> may also serve as a generic data connection to a network through which computer data, as well as telephony data, is exchanged.
p-0031In a non-limiting embodiment, a customer (e.g. a VoIP telephony account holder, a household) may have several call destinations (and, optionally, recipients) associated with his telephony account, each having a different identifier such as telephone number, e-mail address or IP address. When a call is placed to customer premises <b>145</b>, base station <b>105</b> receives a call request. The call request may be in any suitable format such as messaging packets but in a non-limiting embodiment, the call request may be in the form of a SIP invite. The call request may contain call destination data indicative of a call destination indicated by the originator of the call. In a non-limiting embodiment, call destination data includes a label uniquely identifying a call destination such as a telephone number, an e-mail address, an IP address, or a unique customer ID. In a non-limiting example of implementation, the call request is received by packet based interface <b>310</b> and is forwarded to the processing element <b>305</b> that distinguishes the call destination data contained therein from amongst a plurality of call destination data that may be received over packet based connection <b>125</b>. For example, processing element <b>305</b> might be adapted to determine which telephone number, from a set of possible telephone numbers, has been entered by a call originator.
p-0032Optionally, processing element <b>305</b> may also be designed to determine an intended recipient, from among a set of recipients that are susceptible to receive a call over packet based connection <b>125</b>. In a non-limiting example, the intended recipient of the call may be established based on the call destination data received over packet based connection <b>125</b>, as discussed earlier. Alternatively, other information such as information on the call originator (e.g. telephone number, IP address, e-mail, etc. . . . ) may be used in addition to the call destination data. It is to be expressly understood that identifying an intended recipient is an optional step that can be dispensed with without departing from the spirit of the invention.
p-0033Processing element <b>305</b> may optionally include a call initiation module <b>600</b> which performs the function of distinguishing call destination data and, optionally, an intended recipient and causing the call to be handled accordingly. A functional block diagram of a non-limiting example of implementation of the call initiation module <b>600</b> is shown in <figref idrefs="DRAWINGS">FIG. 6</figref>. It should be understood that the call initiation module <b>600</b> is only one component of the processing element <b>305</b>. For clarity and conciseness, that is the only component that is being shown and described in connection with <figref idrefs="DRAWINGS">FIG. 6</figref>. Call initiation module <b>600</b> may be implemented by any suitable means and, in this non-limiting example, call initiation module <b>600</b> is implemented by software in the form of instructions stored on a computer-readable storage medium. Call initiation module could also be implemented using dedicated circuitry. Although call initiation module <b>600</b> has been described here as being a component of processing element <b>305</b>, it should be understood that call initiation module <b>600</b> may lie partially or entirely outside processing element <b>305</b>. For example, some or all of the functions of call initiation module <b>600</b> may be implemented in packet based interface <b>310</b> or may be implemented as a stand-alone element external to processing element <b>305</b>.
p-0034In a non-limiting example, the call processing logic <b>604</b> of the call management module <b>600</b> receives at its input <b>602</b> call request information arriving over the packet based connection <b>125</b> and extracts call data that it is programmed to look for, including call destination data. In the example illustrated, call processing logic <b>604</b> is programmed to examine call request information and identify therein the telephone number that was dialed by the calling party. In the embodiment illustrated, the call initiation module <b>600</b> carries out the optional step of identifying a recipient. To this end, the different possible intended recipient information (telephone numbers in this example) may be stored in a recipients database <b>606</b> with which call processing logic <b>604</b> communicates. In this example, call processing logic matches call recipient information extracted with entries in the recipients' database <b>606</b> and retrieves therefrom an intended recipient's identity.
p-0035In this non-limiting example, once the intended call recipient has been identified, it is passed to call handling logic <b>608</b> (via call processing logic <b>604</b>) which is responsible for determining how the call will be handled. Call handling logic <b>608</b> may be in communication with a call handling rules database <b>610</b> in which specific call handling instructions are associated with each potential recipient. Call handling logic <b>608</b> matches the intended recipient received from call processing logic <b>604</b> with its corresponding entry in call handling rules database <b>610</b> and obtains corresponding call handling instructions. In this exemplary embodiment call handling instructions are user-set rules stored as computer-readable instructions in a format suitable for causing call handling logic <b>608</b> to execute the instructions. Once call handling instructions are obtained, call handling logic <b>608</b> causes the call to be handled in accordance with the rules extracted from call handling rules database <b>610</b>. Call handling instructions stored in database <b>610</b> can be dynamically altered by a user such that each intended recipient can decide how the call will be managed. The call handling rules can be customized via any suitable interface, such as through the handsets <b>110</b>, via the interface <b>320</b> of the base station <b>105</b> or via other user interfaces as will be discussed later.
p-0036It is to be understood that the embodiment illustrated here is only exemplary, as it may not be necessary for databases <b>606</b> and <b>610</b> to be distinct. Indeed in an embodiment where the optional step of identifying an intended recipient is omitted, call initiation module may only have a single database wherein call destination data is mapped to call handling instructions. Also, while call processing logic <b>604</b> and call handling logic <b>608</b> are shown here as two separate entities, they may be combined into a single entity, e.g. in communication with a single database as described above. Of course, call initiation module and components thereof may be organized in any suitable way for achieving at base station <b>105</b> the functionality described herein.
p-0037Specific examples of call handling rules will be discussed below. In one example, the customer is a two-adult and two-child household and there are four potential recipients: a parent (office), both parents (personal), the children and a fax machine. Each of the four recipients may have their own telephone number. The customer premises <b>145</b> in this example is a household with an office, a recreational room, a living room, children's room and a parents' room. When a call request for the children is received, base station <b>105</b> analyzes the call request data, identifies the call destination data and, in this case, the intended recipient and obtains call handling instructions as described above.
p-0038A call handling rule may be setup to select to which handsets <b>110</b>, from a set of handsets <b>110</b> at customer premises, the call will be directed. In a non-limiting embodiment, once a handset <b>110</b> is selected, base station <b>105</b> directs the call to the handset and causes it to ring. For example, if the destination data comprises the children's telephone number, the base station <b>105</b> can handle the call by causing the handsets <b>110</b> in the children's room and the recreational room to ring normally and display caller information (e.g. a caller identification), by causing the handsets <b>110</b> in the living room and in the parents' room to beep once and display caller information, and by causing the handset <b>110</b> in the office not to react (such that a parent working in the office does not get disturbed by the children's phone call).
p-0039In a non-limiting embodiment, once a call has been linked to a certain handset <b>110</b>, the base station <b>105</b> may prevent other handsets <b>110</b> from ringing or may cause them to react (e.g. by ringing) in a different manner than the selected handset <b>110</b>. In this fashion, the selected handset <b>110</b> may produce a first ring sound and the other handsets <b>110</b> may also ring but they may use a differern ring sound, such as to allow a user to audibly identify the handset <b>110</b> to which the call is directed.
p-0040Rules can also be set to determine how the call will be handled when no one answers the call, once the call has been routed to a certain handset <b>110</b>. One possible example is to route the call to another handset <b>110</b>, say the parents' handset <b>110</b>. Optionally, if no one answers the handset to which the call is routed then the process may be repeated and the call may be routed to another handset <b>110</b> until all the handsets <b>110</b> have been exhausted. In this example, the call handling rules define the first handset <b>110</b> to which the call will be routed first, which is the one associated with the intended recipient and also define the order in which the remaining handsets <b>110</b> will be addressed. Of course, it is not necessary in such an embodiment for every handset <b>110</b> to be sequentially rung. For example, a plurality of handsets <b>110</b> may occupy the same place in the order (ring at the same time), and some handsets <b>110</b> may be absent from the order.
p-0041When no one answers the call, call handling rules can be set to determine how voice mail will be invoked. One simple case is to invoke a single voice mail box that is common to all recipients where a message can be left. Another option is to selectively invoke a voice mail system on the basis of the call destination data or the intended recipient. In the case where each call destination or intended recipient (except the fax machine) is associated with a distinct voice mail box within a voice mail system, each of the voice mail boxes may have their own voice prompt to invite the caller to leave a message. In this case, the call handling logic, upon identification of the call destination or intended recipient, will trigger the voice prompt associated with that call destination or recipient. When the voice prompt has been played and assuming the caller desires to leave a message, then the logic will enable the recording of a message from the calling party within the voice mail box associated with the call destination or intended recipient.
p-0042In yet another embodiment, there may be only one voice mail box but a plurality of voice prompts, each associated with a call destination or intended recipient. In this case, the voice prompt played could depend on the call destination data or the intended recipient but the voice mail message left by the call originator may be recorded within a common voice mail box. It is to be understood that the voice mail prompt may be any suitable prompt, and may or may not include a voice message. The voice mail prompt may include, for instance an audio cue without any utterance or speech. In another example, the voice mail prompt may be a message, either generic or recorded by a user, inviting a call originator to leave a voice mail message.
p-0043For clarity, each call destination or intended recipient may be associated with a voice mail service. Various voice mail services for various potential call destinations or intended recipients may be within a single voice mail system or distributed across voice mail systems. The differences between voice mail services may be the voice mail box to which the recorded message is stored, the voice mail prompt that is played to invite the caller to leave a message or both the voice mail box and the voice mail prompt. The voice mail services may be implemented within the base station <b>105</b>, in another component within the customer premises (ex. computer <b>115</b>) or a component outside the customer premises to which the base station <b>105</b> may direct the voice call.
p-0044Along with or instead of directing a handset <b>110</b> to ring to notify users of an incoming call, the processing element <b>305</b> may direct the handset <b>110</b> to which the call is being routed to display a visual incoming call alert. This visual incoming call alert may appear on the display <b>210</b> of the handset. One option is to display a text message indicating the identity of the intended recipient. The text message may be sent to handset <b>110</b> in any suitable manner and in one non-limiting embodiment, it is sent in the format used to send caller ID information. For example, base station <b>105</b> may replace caller line ID information received over connection <b>125</b> with a text message, such as the identity of the intended recipient extracted from the database <b>606</b>, to be conveyed to the handset <b>110</b>. Alternatively, base station <b>105</b> may keep all or portions of the caller line ID information and supplement it with additional information prior to forwarding it to the handset <b>110</b>. Another possibility is to show an image or pictogram or even play a video clip that designates the intended call recipient. Note that the visual incoming call alert can also be provided in conjunction with a ring tone.
p-0045The visual incoming call alert can be particularly useful when a single handset <b>110</b> is being used with the base station <b>105</b>. In such case, the visual incoming call alert may be displayed on the display <b>210</b> of the handset <b>110</b> to indicate the identity of the intended recipient. Note that, in some instances, the visual incoming call alert can be the only way for individuals in the customer premises <b>145</b> to distinguish the identity of the called party. For instance, when the ring function of the handset <b>110</b> has been muted or when a generic ring is used for all phone calls.
p-0046In a non-limiting embodiment, audio signals can be used as an indicator of a call destination or intended recipient. For example, the handset <b>110</b> selected by processing element <b>305</b> from the plurality of handsets <b>110</b> to which to link the call may be caused to ring in a different manner than other handsets. For example, it may be the only handset to ring or may ring with a different ring sound.
p-0047When call destination data or an intended recipient corresponds to a piece of equipment, such as a fax machine, the rules that are set can be such as to prevent any one of the handsets <b>110</b> to ring. Therefore, all the handsets <b>110</b> may remain silent and no one may be disturbed in the house when a fax is received. The fax machine may be connected into a phone jack and receive the ring tone and may answer normally after the predetermined number of rings. Alternatively, a fax machine may be caused to answer automatically any call destined to it by the base station <b>105</b>, and therefore no rings needing to be emitted.
p-0048More sophisticated call handling rules can be implemented by taking into account other parameters such as temporal changes (time of day and date parameters). For instance, different call handling rules can be defined for different times of day or days of the week. For example, during day time when the children are at school, the call handling rules can stipulate that all the handsets <b>110</b> will ring when a call is received, irrespective of the call destination data or identity of the call recipient. However, after school hours, different call handling rules may apply such as to direct a call only to the children's room and/or the recreational room handsets <b>110</b> if the intended recipient is a child. As well, in the above example, calls intended to the parents may cause all handsets <b>110</b> to ring during the day time (e.g. when the children are at school) and cause only the handset in the parents' room to ring at night. Also, optionally, calls intended to the children may automatically be forwarded to voicemail during the daytime and cause the phone in the children's room and recreational room to ring in the afternoon.
p-0049The behavior of base station <b>105</b> in the non-limiting embodiment described above can be broadly described as the four-step process illustrated in <figref idrefs="DRAWINGS">FIG. 4</figref>. Once a call request is received, at step <b>405</b>, the incoming data is accepted and may be analyzed to obtain information pertaining to the call including call destination data. This may require collecting and combining packets, reading packet headers, or decoding encoded data.
p-0050Step <b>410</b> is an optional step. Here, the call information is analyzed to distinguish the intended call recipient from amongst other recipients that are susceptible to receive telephone calls through the VoIP connection. In this step, information contained in the call request data on the basis of which the intended recipient will be identified is extracted.
p-0051At step <b>415</b>, the processing element <b>305</b> accesses instructions on how to handle the call. The instructions are at least in part related to the call destination data and may also be related to an intended recipient distinguished in step <b>410</b>. In a non-limiting embodiment, every potential call destination (and optionally, intended recipient) has associated with it instructions on how to handle calls for it (there may be default instructions, for call destinations or recipient with no specified instructions). It is not necessary for the instructions to be constant. For example, there can be conditional instructions (e.g. ring children's handset only between 7 am-11 pm) or time-varying instructions (e.g. change my ring tone every day). These instructions can be kept in a table or elsewhere in memory and preferably can be changed by a user via user interface <b>320</b>.
p-0052Finally, at step <b>420</b>, the processing element <b>305</b> handles the call according to the instructions obtained at step <b>415</b>. A large number of different ways of handling calls exist, any of which may be used. For example, at step <b>420</b>, the base station may: <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0052">cause a particular subset (one or more) of customer handsets <b>110</b> to ring for a predetermined amount of time (or rings);</li><li id="ul0002-0002" num="0053">case of the above, and when no one has picked up the call, cause a second subset of customer handsets <b>110</b> to ring;</li><li id="ul0002-0003" num="0054">cause one or more customer handsets to provide a visual indicator of the intended recipient when a call request is received; the visual indicator can be textual, graphical or both (e.g. display the name of the intended recipient, display a color or picture associated with recipient, etc.);</li><li id="ul0002-0004" num="0055">cause one or more customer handsets <b>110</b> to provide an audio indicator of an intended recipient (e.g. play a ring tone associated with a recipient, speak out the intended recipient's name, etc.);</li><li id="ul0002-0005" num="0056">cause the call to be forwarded to a particular voice mail box; or</li><li id="ul0002-0006" num="0057">prevent a handset <b>110</b> that was not selected from ringing.</li></ul></li></ul>
p-0053It is not necessary for base station <b>105</b> to always handle the call in accordance with the instructions obtained at step <b>415</b>. External or other factors may cause an exception to the rule. For example, if a phone call is directed to one of the telephone numbers associated with the connection <b>125</b> while connection <b>125</b> is already in an active call, an additional call request could be sent by the network <b>140</b>. In this case, the network <b>140</b> could provide call destination data for this additional call request based upon the specific telephone number that was dialed. When receiving the additional call request, the base station <b>105</b> may proceed with a similar process as discussed above with reference to <figref idrefs="DRAWINGS">FIG. 4</figref>. In particular, the base station <b>105</b> may detect the call destination data for the additional call request and, prior to or in parallel to conveying a call waiting indication to the handset(s) in the active call, determine the call handling rules to be applied for that particular call destination data (or the recipient associated with that particular call destination data). The call handling rules could include providing a visual indication of the intended recipient of the call and/or providing a distinctive audio indication on one or more handsets <b>110</b>. This visual and/or audio indication may be directed to only one or more of the handset(s) <b>110</b> that are in the active call or could be provided to one or more other handsets <b>110</b>. Alternatively, the call handling rules could comprise directing the incoming call to a voice mail system and, in particular, potentially to a specific voice mail box associated with the call destination data or intended recipient.
p-0054For example, if an incoming call is intended for the children in the above example, but the connection <b>125</b> is already in an active call, the caller may be provided a busy signal, be forwarded to a specific voice mail box based on the call destination data associated with the incoming call or be offered to the party on the active call using an audio and/or visual indication of the intended recipient.
p-0055In a non-limiting embodiment, the base station <b>105</b> may be suited for call-waiting functionality in which call requests arriving while another call is in progress are processed by emitting an alert, optionally different from a normal ring tone, to the user involved in the call that is in progress. The signal that conveys the call waiting request and that is received over the connection <b>125</b> may be processed as discussed in connection with the regular calls in order to distinguish call destination data. The call waiting request can be identified and a personalized call waiting alert generated on the basis of the performed identification. In a non-limiting example, the call waiting alert is a discrete beeping sound that is played by the speaker on the handset(s) <b>110</b> being used. However, any audible signal may be provided to the user on the handset <b>110</b> or a visual indicator may be displayed. The call waiting alert may be indicative of a call destination or recipient or of a call originator. Base station <b>105</b> may cause a call waiting alert to be dispatched to every handset <b>110</b> in use or alternatively may select a handset in any suitable way, for example using a database of call initiation module <b>600</b>.
p-0056Although numerous options are provided for providing visual and/or audio indications to the handsets <b>110</b> in the above description, it should be noted that if an analog telephone is connected to base station <b>105</b> to be used as a handset <b>110</b>, the analog telephone may not benefit from all the functionality likely found in other handsets such as wireless DECT handsets. Thus the handling options for the analog telephone may be limited to whether or not to ring and, perhaps, the ring tone that is utilized. In such a case, the limitations of the analog telephone may be taken into consideration by base station <b>105</b> when handling the call.
p-0057In the non-limiting embodiment described, base station <b>105</b> comprises a user interface <b>320</b>. In an example, user interface <b>320</b> allows a user to change the settings of base station <b>105</b> such that incoming calls are handled differently. For example, in the optional case where the base station <b>105</b> maintains a list of potential recipients, a user may be able to add or remove recipients from a list of all the possible recipients at customer premises <b>145</b>. A user may also be able to change the way the base station <b>105</b> determines whether an incoming call is intended for a recipient or set a default recipient.
p-0058The user may also be able to change the way calls are handled for each call destination or intended recipient, or change a default call handling. For example, a user may be permitted to enter via user interface <b>320</b> new routing information associated with a call destination such as a telephone number. The user may therefore be able to set which handset <b>110</b> is selected by base station <b>105</b> when a call request is received with a certain call destination data. A user may also access other information such as the contact list (add, delete, modify entries) via user interface <b>320</b>. In certain embodiments, user interface <b>320</b> may also be used for more technical activities such as adding an additional handset <b>110</b> to be connected to the base station or setting quality of service preferences.
p-0059Although the user interface <b>320</b> has been shown here uniquely as part of base station <b>105</b>, it may be partially, or entirely, contained elsewhere. For example, some or all of the user interface functions may be provided to a user at a handset <b>110</b> via handset connection <b>125</b>. Alternatively, a computer <b>115</b>, in communication with base station <b>105</b> may be used to access user interface functions. The computer acting as user interface <b>320</b> may be directly linked to base station <b>105</b> via LAN connection <b>135</b> or may be connected via the Internet (e.g. user interface <b>320</b> could be a web page).
p-0060Although the system <b>100</b> has been depicted here as a centralized system with base station <b>105</b> having most of the intelligence, one skilled in the art will appreciate that the system <b>100</b> may be distributed, with one or more of the handsets <b>110</b> performing any one or more of the steps illustrated in <figref idrefs="DRAWINGS">FIG. 4</figref>. Thus base station <b>105</b> may be entirely absent, as is the case in <figref idrefs="DRAWINGS">FIG. 5</figref> where each handset <b>110</b> is connected directly to the internet via a common packet based connection <b>125</b>. In this and the previous embodiment, it may be necessary, if there is a plurality of handsets <b>110</b>, for the handsets <b>110</b> to communicate with one another such as to ensure consistent call handling. To this end, handsets <b>110</b> may be connected to one another via handset-to-handset connections <b>505</b>. In a non-limiting embodiment, handset-to-handset connections <b>505</b> are peer-to-peer connections.
p-0061Alternatively, a base station <b>105</b> may only be responsible for depacketizing incoming data and obtaining information pertaining to an incoming call (step <b>405</b>) and forwarding it to handsets <b>110</b>, the handsets <b>110</b> being responsible for steps <b>410</b>, <b>415</b> and <b>420</b>. In this case, handsets <b>110</b> each receive the information indicative of an intended recipient contained in a call request and based on that information, decide how to handle the call. For example, a handset in the parents' room will receive information contained in a call request for a call intended for the children and will decide not to ring but only to beep and display the caller ID. In this non-limiting embodiment, upon receiving a call request the handsets <b>110</b> may communicate with one another, either through base station <b>105</b> or via a handset-to-handset connection <b>505</b> to establish at which handset(s) <b>110</b> the call is to be picked up. Thus, even though there is no centralized intelligence dictating how to handle the call, handsets <b>110</b> can ensure that every call causes at least one handset <b>110</b> to ring, and that all handsets <b>110</b> handle calls in a consistent manner.
p-0062While in <figref idrefs="DRAWINGS">FIG. 4</figref>, operations have been shown in the form of discrete steps, it is to be appreciated that steps <b>405</b>, <b>410</b>, <b>415</b> and <b>420</b> may be combined, or rearranged in any suitable order with departing from the intended scope of the invention. Optional step <b>410</b> may or may not be present.
p-0063Although the present invention has been illustrated here in the context of packet based telephony, it is to be understood that it could also be practice with circuit-switched telephony or in any other telephony system, for example by obtaining call destination data from analog ring tones impressed on a twisted pair connection with a PSTN network.
p-0064Although various embodiments have been illustrated, this was for the purpose of describing, but not limiting, the invention. Various modifications will become apparent to those skilled in the art and are within the scope of this invention, which is defined more particularly by the attached claims.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2015271216A1 | Cited by | United States of America | Pre-grant |
| US10536491B2 | Cited by | United States of America | Search report |
| US2003161454A1 | Cites | United States of America | Applicant |
| US2004022208A1 | Cites | United States of America | Search report |
| US2004196833A1 | Cites | United States of America | Search report |
| US2004213401A1 | Cites | United States of America | Applicant |
| US2005100152A1 | Cites | United States of America | Applicant |
| US2005147086A1 | Cites | United States of America | Search report |
| US2005207556A1 | Cites | United States of America | Applicant |
| US2006026277A1 | Cites | United States of America | Applicant |
| US2006062358A1 | Cites | United States of America | Search report |
| US2006067502A1 | Cites | United States of America | Search report |
| US2006274721A1 | Cites | United States of America | Search report |
| US2008125095A1 | Cites | United States of America | Search report |
| US2008192657A1 | Cites | United States of America | Search report |
| US2008299950A1 | Cites | United States of America | Search report |
| US5193110A | Cites | United States of America | Search report |
| US5636218A | Cites | United States of America | Search report |
| US5978451A | Cites | United States of America | Applicant |
| US6058178A | Cites | United States of America | Applicant |
| US6081707A | Cites | United States of America | Search report |
| US6263071B1 | Cites | United States of America | Applicant |
| US6407997B1 | Cites | United States of America | Search report |
| US6597764B1 | Cites | United States of America | Applicant |
| US6778661B1 | Cites | United States of America | Search report |
| US6826173B1 | Cites | United States of America | Search report |
| US6831899B1 | Cites | United States of America | Search report |
| US7706817B2 | Cites | United States of America | Search report |
| US7782854B2 | Cites | United States of America | Search report |
| Non-Final Office Action issued by the U.S. Patent and Trademark Office on Oct. 31, 2011 in connection with U.S. Appl. No. 12/344,007, (12 pages). | Non-patent | – | Applicant |
6 members in 2 offices; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2004708 | United States of America | A | |
| US20080020047 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| CA2633016A1 | Canada | A1 | |
| CA2958354A1 | Canada | A1 | |
| US2009190742A1 | United States of America | A1 | |
| US8634331B2This record | United States of America | B2 | |
| CA2633016C | Canada | C | |
| CA2958354C | Canada | C |
66 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Maintenance Fee Reminder MailedREM. | REM. | |
| 7.5 yr surcharge - late pmt w/in 6 mo, Large EntityM1555 | M1555 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Surcharge for Late Payment, Large EntityM1554 | M1554 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Is Now CompleteCOMP | COMP | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW | CORRDRW | |
| Corrected PaperCPAP | CPAP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
13 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee payment procedure7.5 YR SURCHARGE - LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1555); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee payment procedureSURCHARGE FOR LATE PAYMENT, LARGE ENTITY (ORIGINAL EVENT CODE: M1554)FEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.)FEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 08634331
- Publication, DOCDB
- 8634331
- Publication, EPODOC
- US8634331
- Application
- 12020047
- Application, DOCDB
- 2004708
- Application, EPODOC
- US20080020047
Titles
- English
- Customer premises call handling
Patent term adjustment
- A delay
- +1,189 daysthe office missed an examination deadline
- B delay
- +910 dayspendency past three years
- Overlap
- −518 daysdelays counted once
- Applicant delay
- −112 days
- Net adjustment
- 1,469 days
Classification
- CPC, 12
- H04M3/533
- H04M3/02
- H04M3/42042
- H04M3/42187
- H04M3/4288
- H04M3/436
- H04M3/46
- H04M3/465
- H04M2201/52
- H04M2203/2072
- H04L51/42
- H04L51/10
- IPC, 3
- H04L12 58
- H04Q11 00
- H04M3 533
- USPC, 1
- 370260000