The present invention will be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:
With reference to
The system 10 may be used in situations where a calling party has a pre-established relation with a called party, and desires to possibly communicate with the called party regardless of whether the called party has a call waiting service or is willing or inclined to switch to an incoming call under the prompting of call waiting. For example, in the case of family use, certain children may be disinclined to switch to an incoming call when notified of such by a call waiting service, e.g., if they are talking to friends. Under the system 10, a parent or other calling party with priority privileges is given the option of interrupting the active call, for emergency purposes or otherwise.
The system 10 of the present invention is suitable for implementation on various types of communication networks 12, including stand-alone networks and interconnected networks. For example, the network(s) 12 may include wire-line networks such as DSL networks, public switched telephone networks (PSTN) 16, IP (Internet protocol)-based networks such as the Internet or other packet data networks, local area networks (LAN), and wireless networks 18 such as those using CDMA, GSM, IEEE 802.11x, and/or UMTS communications or the like. As noted above, the terminals 14a-14c are electronic devices capable of communicating with one another over the network(s) 12, and may include, for example, computer units, wire-line connected communication devices such as conventional telephones, and/or wireless units such as mobile phones, wireless PDA's, wireless devices with high-speed data transfer capabilities, such as those compliant with “3-G” or “4-G” standards, “WiFi”-equipped computer units, and the like. The terminals 14a-14c communicate with one another over the networks 12 in a standard manner, according to the communication protocols in place on the networks, and depending on the particular networks and the particular types of terminals. For example, in the case of wireless units 14a, 14b and a wireless network 18, the network may include one or more fixed base stations (“BS”) 20 having various transceivers and antennae for wireless, radio-frequency (RF) communications with the wireless units over one or more RF channels, in a manner based on the wireless communication method and protocol used. A radio network controller (“RNC”) 22 interconnects the base stations and performs the signaling functions necessary to establish calls and other data transfer to and from the wireless units. It also acts as the interface between the wireless/RF end of the network and the wire-line portion of the network and external wire-line networks. For example, a wireless network 18 typically includes landline portions (e.g., a backbone connecting the base stations and radio network controller), and is typically connected to a PSTN 16 and/or to an IP network, which allows the wireless units to communicate with terminals connected to the PSTN or IP network, such as landline phones and computer terminals.
As indicated in
Operation of the system 10 is illustrated in more detail in FIGS. 2 and 3A-3C. As indicated above, the system 10 is configured to determine if a newly initiated communication is a priority communication, when the called party is already on another call, for possibly interrupting the pre-existing, active call. As such, when a first terminal 14a initiates communication with a second terminal 14b over the network 12, as at Step 100 in
In the system 10, determinations of subscriber status and call priority may be carried out primarily with respect to user-based identifiers and records, instead of, or in addition to, terminal records and identifiers. This is described in more detail below with respect to
For determining whether the called terminal 14b is subscribed to the system 10, a notation of such may be recorded in a profile or other data record associated with the called terminal (and/or the called user, as described below). The record may be an existing record of the called terminal, such as a record in a network home location register or the like, or it may be a record stored on the application server 24. For example, the application server 24 may include a database 28 containing a record 30a-30c for each terminal subscribed to the call priority system/service 10. Each record 30a-30c includes the communication identifier 32 of its associated terminal, e.g., telephone number, e-mail or messaging address, or other identifier for initiating communication with the terminal over the network 12. For a first terminal 14a to initiate communication with a second terminal 14b, the first terminal will typically transmit the communication identifier 32 of the second terminal 14b to the network 12, as part of the network signaling protocol. If the second terminal 14b is in communication with a third terminal (Step 102), the system 10 cross-references the communication identifier 32 of the called terminal 14b to the database 28. If the communication identifier 32 is listed in one of the records (or in an index or the like), this indicates that the called terminal 14b is subscribed to the call priority service. Otherwise, the called terminal 14b may be considered to be unsubscribed to the service. Additionally, the records 30a-30c may each include an activation field or entry 34 indicating whether the service is activated or deactivated for the terminal in question. For example, even if a terminal is subscribed to the call priority service, the system 10 may be configured for an authorized user to turn the service on or off.
Alternatively, instead of utilizing subscriptions, the call priority service may be made available to all terminals generally. In this case, at Step 106 the system would determine if the call priority service has been activated for the called terminal. This could be done by cross-referencing the communication identifier 32 of the called terminal to a database 28 containing records 30a-30c for each terminal on the network 12. Each record would include an activation field 34 indicating whether the service had been “turned on” for the particular terminal.
At Step 106, if it is determined that the called terminal 14b is not subscribed or otherwise subject to the call priority system or service 10 (if applicable), or if the service has not been activated for the called terminal, at Step 108 the system/network executes its standard “busy” protocol, this is, it continues as it normally would according to the communication protocols of the network for handling an incoming call where the called party is already in communication with another network. For example, the network 12 may initiate generation of a “busy” signal at the calling terminal 14a, or it may initiate activation of a “call waiting” or “call forward when busy” service. On the other hand, if it is determined at Step 106 that the called terminal 14b is subscribed to the call priority system or service 10, and/or that the service has been activated for the called terminal, at Step 110 it is determined whether the incoming call from the first terminal 14a is a priority communication.
Generally speaking, determinations of whether or not the incoming call from the first terminal 14a is a priority communication will typically be based on whether the calling terminal 14a and/or a user of the calling terminal 14a is authorized for interrupting active communications between the called terminal 14b and other terminals. In one embodiment, priority authorizations are set up using calling terminal communication identifier. Here, the record 30a for the called terminal 14b includes a field or other entry 36 containing one or more “priority” communication identifiers 38a-38c. If the communication identifier of a calling terminal is listed in the priority field 36, communications from that terminal are deemed to be priority communications. For example, in the case of a parent and child (using wireless units 14a, 14b, respectively), the parent may add the communication identifier 38a of the parent's wireless unit 14a to the priority field 36 of the data record 30a associated with the child's wireless unit 14b. When the parent calls the child from the parent's wireless unit 14a, the communication identifier 38a of the parent's wireless unit 14a is transmitted to the network, as is the identifier 32 of the child's wireless unit 14b. For locating the record 30a associated with the child's wireless unit 14b, the identifier 32 of the child's wireless unit 14b is cross-referenced to the database 28. Then, the identifier 38a of the parent's wireless unit 14a is cross-referenced to the priority field 36. If the identifier 38a is listed in the priority field 36, the communication initiated at the parent's wireless unit 14a is considered to be a priority communication.
As should be appreciated, basing determinations of call priority on calling terminal communication identifiers has the effect of limiting the service to particular terminals. Thus, for example, if parent and child wireless units are set up in the manner described above, the parent will not be able to initiate a priority communication unless the parent uses his or her own wireless unit. To increase service portability, for basing priority determinations on user instead of terminal, other means may be utilized for designating authorized calling parties. For example, in another embodiment, after a communication is initiated at a first terminal 14a to a second terminal 14b, and after Step 106 is carried out, at Step 112 the user of the first terminal 14a enters an alphanumeric priority code 40 (e.g., set of letters and/or numbers) into the terminal 14a, which is transmitted to the system 10. (Optionally, at Step 114 the user may be prompted to enter the code.) The record 30a associated with the called terminal 14b contains a code field or other entry 42 listing one or more codes. If the code 40 entered at the calling terminal 14a is listed in the code field 42, the communication initiated at the calling terminal 14a is deemed to be a priority communication. Thus, a user with priority privileges may use any terminal for contacting the called terminal 14b. The system 42 may be configured for a user to enter the code 40 at different time points. For example, the code may be entered in the calling terminal 14a as a string at the end of the called terminal's communication identifier 32, e.g., XXX-XXX-XXXX-code.
In another embodiment, a terminal 14b is provided with a priority communication identifier 44. The priority identifier 44 is formatted the same as any other communication identifier in the network (e.g., as a telephone number), but is supplemental to the terminal's main, non-priority identifier 32. Both identifiers 32, 44 may be used for communication with the terminal 14b. However, if a communication is initiated using the priority identifier 44, communications from the calling terminal are automatically deemed to be priority communications. Thus, following the example given above, a child's wireless unit can be outfitted with the two identifiers 32, 44. The primary identifier 32 is disseminated to non-priority users for use in calling the child's wireless unit. A parent or other priority user, however, may call the child's wireless unit 14b using the priority identifier 44. If the priority identifier 44 is used, as determined at Step 110, the communication is deemed to be a priority communication.
The system 10 may be further adapted to accommodate network call forwarding services or other features of the network that interrelate various terminals and/or communication identifiers, for determining call priority status. For example, if the network includes a call forwarding service, and if the communication identifier of a calling terminal 14a is not listed as having priority status in the called terminal's profile or other record 30a, the system 10 may check the call forwarding status of each of the priority communication identifiers 38a-38c listed in the record. If the call forwarding status indicates that calls for a particular priority identifier are being forwarded to the calling terminal, then the calling terminal will be given priority status.
Instead of directly deciding whether to grant priority status to an initiated communication by way of communication identifiers, codes, or the like, the system 10 may be configured for the use of indirect designations on a user-by-user basis. For example, each terminal's profile or other record 30a-30c may include a “priority users” field or other entry 46 containing a list of priority users 48a, 48b, designated by name, nickname, primary communication identifier, or the like. Associated with each listing 48a, 48b is a user record 50 in the database 28 or elsewhere. The user record 50 is maintained and accessed by the designated user, and contains a listing of the communication identifiers 52a, 52b associated with terminals that the user may use or is currently using. For determining if an initiated communication is a priority communication, the system compares the calling terminal's communication identifier 32 to the records 50. If it is listed in one of the records, the initiated communication is given priority status. Such a configuration promotes portability, since the user record 50 may be easily accessed and modified by the user, e.g., from a terminal 14a, for conveniently adding and removing communication identifiers 52a, 52b as needed. For example, in the case of parent and child wireless units, the record 30a associated with the child's wireless unit 14b could list “Mom” as one of the priority users 48a, 48b. The record 50 associated with the “Mom” entry contains the communication identifier 52a of the wireless unit 14a that the parent normally uses. However, if the parent temporarily switches to another wireless unit, the parent accesses the record 50 and adds the communication identifier of the new wireless unit to the record 50. When the parent calls the child from the new wireless unit, its communication identifier is compared to all the records 50 linked to the record 30a of the child's wireless unit, for determining priority status. Similar arrangements are possible.
Similarly, the system 10 may be configured for use with networks 12 that primarily identify users rather than terminals, such as those using SIP or VoIP. (“VoIP” stands for voice over IP (Internet protocol), in which voice signals are sent as addressed data packets over an IP network.) In particular, in VoIP networks, users call users, rather than terminals calling terminals. Whenever a user commences use of a terminal, the network maintains a mapping or registry indicating that the user is currently reachable and is using the particular terminal. A single user can be registered at multiple terminals. For a calling party to initiate a call to the user, the calling party uses an identifier associated with the user. Based on the user identifier, the network first refers to the map/registry for looking up the terminals currently associated with the user. Then, the network routes the call appropriately.
Use of the system 10 in the context of such a network is illustrated in
Determinations of call priority may be based on both terminal and user. Here, upon initiation of a call to a busy party, the system accesses the database 28 for checking if the calling terminal OR the calling user is listed as being authorized for call interruption.
Referring back to
As shown in
The system 10 is applicable for use with “reverse 911” systems, for interrupting ongoing calls or other communications upon initiation of a reverse 911 call. A reverse 911 call is a call initiated by a municipal authority or other government authority to local users' telephones or other terminals, for informing the users about an emergency situation in the nearby area, e.g., weather alerts, evacuations, or abductions. Typically, a computerized system operated by the municipality carries out the reverse 911 calls automatically, using an electronic phone directory or the like and pre-recorded or computer-generated messages. For use with a reverse 911 system, the system 10 of the present invention could automatically include the reverse 911 system communication identifier 38c in each user profile/record 30a-30c, as a user un-modifiable “background” element. Upon initiation of a reverse 911 call, the pre-established, ongoing communication could either be automatically terminated (Step 116a) or put on call waiting hold (Step 116c). With respect to reverse 911 calls, the call priority service of the system 10 may be optionally activated for each user, or it may be mandatory for all users in the network 12, with individual users subscribing to the service for further, personalized functionality.
The system 10 may be configured for the optional use of different priority levels, which correspond to different levels of functionality in the system 10. For example, communications initiated by users or terminals with a “high” or “emergency” priority level may result in automatic termination of the pre-existing communication between the called and third terminals (Step 116a), while communications initiated by users or terminals with a lower priority level may result in optional interruption (Step 116d, etc.)
As noted above, the functionality of the system 10 will typically be offered as a network service to users, either free or as a subscription service. In either case, interested users access the application server 24 to establish and configure user accounts, including the profiles/records 30a-30c, 50. A user interface may be provided for accessing the application server 24 for this purpose. For example, the terminals 14a-14c could be provided with a hardware and/or software module acting as an interface to the application server. (In the case of a mobile phone or other wireless unit the function could be accessible using the phone's menu system, with the phone and application server exchanging data for enabling the user to establish and configure a profile/record 30a-30c.) Other options include, but are not limited to, a designated website or other Internet interface, remote access using a short message service, a telephone access system (e.g., users call a designated number and are provided with voice prompts for accessing and modifying accounts and associated records), or the like. Upon accessing the user interface, the user is provided with options for establishing a record 30a-30c, 50, including subscription options if applicable. The account/record access system will typically include user authentication means such as password protection. Additionally, certain sub-portions or sub-features of the records 30a-30c, 50 may be provided with separate passwords or other authentication means for limiting access to certain users. For example, a parent may wish to prevent a child user from modifying the listing 36 of priority users in the record 30a.
The profile/record 30a for a terminal 14b will typically include the communication identifier 32 associated with the terminal. The record 30a may also include other user data such as name, account number, and the like. After subscribing to the service (if applicable) and establishing a record 30a, the user populates the record with the communication identifiers 38a-38c of terminals to be granted priority communication status. Alternatively, the record may be populated with one or more priority codes 40, priority users 48a, 48b, or the like. In certain cases, someone other than the intended user of the terminal may configure the record, e.g., a parent.
As indicated above, when an incoming communication from a first terminal 14a to a second terminal 14b is given priority status, the active communication between the second and third terminals 14b, 14c is either terminated or put on hold. If the user of the third terminal 14c is not informed of this occurrence, e.g., if the line goes silent, the user may think that the call was dropped, or that the user of the second terminal 14b terminated the communication abruptly. Accordingly, the system 10 may be configured to initiate playback of a message at the second terminal 14b for informing the user of the second terminal that the active call has been put on hold, or was terminated due to an incoming priority call. For this purpose, the system 10 may include a media server 60 connected to the network 12. When the active communication is terminated or put on hold, the media server 60 is controlled to transmit the desired message or other content to the second terminal 14b over the network 12. For example, there may be a pre-recorded message indicating that the call has been put on temporary hold, followed by music. The message content may be customized and/or selected on a user-by-user basis. For this purpose, each profile/record 30a-30c may include an “on hold content” field 62 identifying one or more messages, greetings, or other media files for playback to an “on hold” user. Greetings may be recorded and stored on the terminal, media server, or elsewhere in the network, using standard methods. For example, the system could be configured for recording a greeting spoken into the microphone of a user terminal. Prior to connecting to the calling terminal 14a, a greeting or announcement may also be played over the called terminal 14b for informing the user of the impending interruption.
As should be appreciated, although the records 30a-30c have been shown as being stored on the application server 24, each terminal's record could instead be stored locally on the terminal, with the system 10 accessing the record on the terminal when a communication is initiated to the terminal within the context described above.
Although the notification 54 has been illustrated as being displayed on a terminal in text form (see
Since certain changes may be made in the above-described call priority management system for a communication network, without departing from the spirit and scope of the invention herein involved, it is intended that all of the subject matter of the above description or shown in the accompanying drawings shall be interpreted merely as examples illustrating the inventive concept herein and shall not be construed as limiting the invention.