WO2019023739A1

WO2019023739A1 - System and method for dynamically screening phone calls

Info

Publication number: WO2019023739A1
Application number: PCT/AU2018/050769
Authority: WO
Inventors: Ian Ivan Kuchel; Naomi Kathryn Kuchel
Original assignee: Kuchel Holdings Pty Ltd
Current assignee: Kuchel Holdings Pty Ltd
Priority date: 2017-08-02
Filing date: 2018-07-24
Publication date: 2019-02-07
Anticipated expiration: 2020-02-02

Abstract

The present invention relates to a computer-implemented system and method for screening phone calls and, in particular, to adjusting a blocked caller list of a call recipient device according to an availability status of the call recipient. The present invention further relates to dynamically screening phone calls including adjusting a blocked caller list of a call recipient device according to an availability status or availability schedule of the call recipient.

Description

SYSTEM AND METHOD FOR DYNAMICALLY SCREENING PHONE CALLS FIELD OF THE INVENTION

[0001] The present invention relates to a computer-implemented system and method for screening phone calls and, in particular, to adjusting a blocked caller list of a call recipient device according to an availability status of the call recipient. The present invention further relates to dynamically screening phone calls including adjusting a blocked caller list of a call recipient device according to an availability status or availability schedule of the call recipient.

BACKGROUND OF THE INVENTION

[0002] It is well known that mobile phones and related communication devices are capable of storing contacts in a contacts list to assist a user in recognizing a caller when receiving an incoming call, and in locating a contact's telephone number when seeking to make an outgoing call. Such devices are also capable of being programmed to screen calls, which provides the user with control over which contacts can reach the user. For example, the device can be programed to accept or decline specific contact names or phone numbers and direct declined calls from particular contacts to voicemail. Such devices may also utilize a blocked caller list in circumstances where a user prefers not to receive calls from a particular contact or telephone number. However, in these circumstances, the user is not informed of declined calls and hence will be unaware that the blocked user attempted to call.

[0003] Devices which utilise call screening applications known to the Applicant have a number of technical deficiencies since they fail to take into account the availability status of the user in a dynamic way, and the result is that the user will be disturbed irrespective of the screening. For example, tradesmen, business people, persons travelling through different time zones, and on-call or shift workers may prefer not to be disturbed when on leave, not working, or asleep, yet current screening methods fail to recognize the availability status of the user and therefore, irrespective of the availability status of the user, the call will still cause the user to be informed of the attempted contact and will therefore disturb the user. For example, once the phone has rung, the user may be inclined to accept the call regardless of their availability and get tied up in a conversation. Even if the call is not answered, the user may be inclined to check who the caller was, and/or be inclined to check multiple voice messages in their voice mail.

[0004] Accordingly, in order to prevent disturbance to a user, current systems require the user to either turn off their phone, switch the phone to silent mode, or set up call screening based on the user's contact list but these all have deficiencies as described above.

[0005] Further, current call screening techniques known to the Applicant do not allow users to inform callers of their unavailability before the call is allowed to cause the user's phone to ring (or trigger some other alert associated with receiving a call). An example of where a user may prefer to classify his or her status to a potential caller as "unavailable" and inform users regarding their unavailability is where the user is not at work and engaged in an activity with friends and/or family, for example, spending a day at the beach with the family. Another example is where a user, who uses a single phone for personal and business purposes, is in a meeting or prefers not to be disturbed by personal calls during business hours.

[0006] Current screening techniques known to the Applicant also fail to provide flexibility by allowing a user to categorize contacts and set their future availability so that, for example, certain personal contacts are blocked when the user is unavailable during business hours, and certain business contacts are blocked when the user is unavailable during non-business hours.

[0007] Further, current screening techniques known to the Applicant do not provide for the call screening to be overridden by the caller in the event of an emergency or urgent requirement to make contact with the call recipient, nor do they allow a caller to view the availability of the call recipient prior to initiating the call.

[0008] It is therefore an object of the present invention to overcome at least some of the aforementioned problems or to provide the public with a useful alternative. SUMMARY OF THE INVENTION

[0009] According to an aspect, the present invention provides a computer- implemented method of dynamically screening communication requests, the method including receiving, by a first device, input relating to a status of a first user associated with the first device, the first device configured to provide an alert to the first user upon receipt of a communication request, and the status relating to an availability of the first user to accept a communication request, when the status indicates that the first user is unavailable, ensuring that the one or more contacts associated with the first device are present in a blocked list associated with the first device, when the status indicates that the first user is available, ensuring that the one or more contacts associated with the first device are excluded from the blocked list associated with the first device, receiving, by the first device, a communication request from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device, and when the second user is present in the blocked list associated with the first device, preventing the first device from providing an alert to the first user regarding a contact attempt by the second user.

[0010] In an embodiment, the communication request is a voice call, and the blocked list is a blocked caller list. In other embodiments, the communication request is a text message, or a video call, and it is to be understood that whilst the present invention has been described herein primarily with respect to the screening of voice calls by mobile or cell phone, other forms of media communication such as texts, video calls, and the like, may also be screened using the same principles.

[0011] In an embodiment, the method further includes when the status indicates that the first user is unavailable and the second user is present in the blocked list associated with the first device, causing the first device to transmit a notification to the second device regarding the first user's unavailable status.

[0012] In an embodiment, the notification is in the form of a Short Message Service (SMS) message or pre-recorded voice message transmitted to the second device. [0013] In an embodiment, the method further includes when the second user is excluded from the blocked list associated with the first device, permitting the first device to provide the alert to the first user.

[0014] In an embodiment, the alert is a visible and/or audible and/or vibratory alert associated with the first device receiving an incoming phone call.

[0015] In an embodiment, the method further includes receiving, by the first device, an override request from the second user to override preventing the first device from providing the incoming call alert to the first user, and where the first user has enabled modifications to the blocked caller list in the first device, modifying the blocked caller list of the first device to ensure the second user submitting the override request is excluded from the blocked caller list, thereby permitting the first device to provide the alert to the first user.

[0016] In an embodiment, the method further includes receiving, by the first device, an override request from the second user to override preventing the first device from providing the incoming call alert to the first user, and where the first user disables modifications to the blocked caller list in the first device, causing the first device to transmit a notification to the second device regarding the first user's unavailable status.

[0017] In an embodiment, the notification is in the form of a text message or prerecorded voice message transmitted to the second device.

[0018] In an embodiment, ensuring one or more contacts associated with the first device are excluded from a blocked caller list associated with the first device includes adjusting the blocked caller list to remove the one or more contacts, if present in the blocked caller list, from the blocked caller list.

[0019] In an embodiment, ensuring one or more contacts associated with the first device are present in a blocked caller list associated with the first device includes adjusting the blocked caller list to admit the one or more contacts, if not present in the blocked caller list, to the blocked caller list. [0020] In an embodiment, receiving input relating to a status of the first user includes receiving, via a user interface of the first device, input from the first user relating to the first user availability.

[0021] In an embodiment, receiving input relating to a status or status update of the first user includes receiving, from an application operating on the first device or from a remote source, input relating to a global positioning system (GPS) location of the first user.

[0022] In an alternate embodiment, receiving input relating to a status of the first user includes receiving, from a storage means associated with the first device, input relating to the first user availability according to an availability schedule stored in the first device storage means.

[0023] In an embodiment, the availability schedule includes status updates for predefined time intervals over a pre-defined time period.

[0024] In an embodiment, when the availability schedule is stored in a storage means associated with the first device, the method further includes receiving, via a user interface of the first device, input relating to a change to a start and/or end time of a time interval.

[0025] In a further alternate embodiment, receiving input relating to a status of the first user includes receiving, from one or more remote servers, input relating to the first user availability according to an availability schedule stored on the one or more remote servers.

[0026] In this embodiment, the availability schedule includes status updates for pre-defined time intervals over a pre-defined time period.

[0027] In this embodiment where the availability schedule is stored on the one or more servers, the method further includes receiving, via a user interface of the first device, input relating to a change to a start and/or end time of a pre-defined time interval, generating, by the first device, updated schedule data based on the input relating to a change to a start and/or end time of a pre-defined time interval, and transmitting, from the first device to the one or more servers, a schedule update request containing the updated schedule data, wherein receiving, from one or more remote servers, the input relating to the first user availability according to an availability schedule stored on the one or more remote servers is a push notification from the one or more servers to the first device.

[0028] In this embodiment, the push notification is VoIP push notification that is communicated through an Application Programming Interface (API).

[0029] In this embodiment, push notifications from the one or more servers to the first and/or second device further includes instructions to an application operating on the first and/or second device to perform actions.

[0030] In an embodiment, the actions include one or more of providing a status update to the first device according to an availability schedule stored on the one or more servers; adjusting the blocked caller list of the first device; or providing a notification to the second device regarding the first user's availability status and when the status is scheduled to change according to the first user's availability schedule stored on the one or more servers.

[0031] In an embodiment, the availability schedule is linked to, and the start and end times associated with pre-defined time intervals in the schedule are updated in accordance with, one or more calendars associated with the first device.

[0032] In an embodiment, the one or more contacts are contacts present in the first device contacts list.

[0033] In an alternate embodiment, the one or more contacts are a sub-set of contacts in the first device that are selected by the first user and categorised by the first user.

[0034] In an embodiment, the status relating to an availability of the first user to receive a call includes a reason for their availability or lack of availability.

[0035] In an embodiment, the reason for the first user's unavailability includes driving, presence at work, presence in a meeting, personal commitment, or sleeping.

[0036] In an embodiment, when the status indicates that the first user is unavailable and the second user is present in the blocked list associated with the first device, and the first device is caused to transmit a notification to the second device regarding the first user's availability, the notification includes the reason for the user's lack of availability.

[0037] In an embodiment, where the first user has disabled modifications to the blocked caller list in the first device, and the first device is caused to transmit a notification to the second device regarding the first user being unavailable, the notification includes the reason for the user's lack of availability.

[0038] In an embodiment, the first and second devices are cell phones associated with the first and second user respectively.

[0039] In an embodiment, the first and second devices communicate, via a network interface, with the one or more servers through an API.

[0040] According to another aspect, the present invention provides a system for dynamically screening phone calls, the system including one or more processors associated with a first device, and a memory in communication with the one or more processors, the memory including instructions, which when executed by the one or more processors causes the one or more processors to receive input relating to a status of a first user associated with the first device, where the one or more processors are configured to provide an alert to the first user upon receipt of a phone call, and the status relating to the availability of the first user to accept a call, when the status indicates that the first user is unavailable, ensuring the one or more contacts associated with the first device are present in a blocked caller list associated with the first device, when the status indicates that the first user is available, ensuring one or more contacts associated with the first device are excluded from the blocked caller list associated with the first device, receive a voice call from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device, and when the second user is present in the blocked list associated with the first device, preventing the first device from providing the alert to the first user.

[0041 ] According to yet another aspect, the present invention provides a computer- readable medium storing instructions executable by one or more processors associated with a first device and upon such execution cause the one or more processors to perform operations including: receive input relating to a status of a first user associated with the first device, the one or more processors configured to provide an alert to the first user upon receipt of a voice call, and the status relating to the availability of the first user to accept a voice call, when the status indicates that the first user is unavailable, ensure the one or more contacts associated with the first device are present in a blocked caller list associated with the first device, when the status indicates that the first user is available, ensure one or more contacts associated with the first device are excluded from the blocked caller list associated with the first device, , receive a voice call from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device, and when the second user is present in the blocked list associated with the first device, prevent the first device from providing the alert to the first user.

[0042] According to a still further aspect, the present invention provides a system for dynamically screening phone calls, the system including a first device associated with a first user, the first device configured to provide an alert to the first user upon receipt of a voice call, a second device associated with a second user, the second device configured to enable the second user to cause the second device to transmit a voice call to the first device, one or more remote servers with which the first and second devices communicate through an API, the first device including a user interface and a memory storing a contacts list and a blocked caller list, the memory further including instructions, which when executed by the one or more processors, causes the one or more processors to receive an input via the user interface or a notification from the one or more servers relating to a status of the first user associated with the first device, the status relating to the availability of the first user to accept a voice call, when the status indicates that the first user is available, ensure one or more contacts in the contacts list is excluded from the blocked caller list, when the status indicates that the first user is unavailable, ensure the one or more contacts in the contacts list is present in the blocked caller list, receive a voice call from the second device, the second user having contact details in the one or more contacts in the contacts list of the first device, when the second user is present in the blocked caller list, prevent the first device from providing the alert to the first user. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Features of the present disclosure are illustrated by way of example and not limited in the following figure(s), in which like numerals indicate like elements, in which: is a concept overview diagram relating to a system and method for dynamically screening phone calls according to an embodiment; is a solution overview diagram relating to the system and method of Figure 1 ; is a functional flow diagram that illustrates how users download an application relating to, and register to use, the system and method of Figures 1 and 2 according to an embodiment; is a functional flow diagram that illustrates an embodiment involving dynamically configuring the user's availability to receive phone calls; is a functional flow diagram that illustrates an embodiment relating to dynamically screening calls based on the user's availability status, such as driving, working, not-working, etc; is a functional flow diagram that illustrates an embodiment in which the availability status of the user is displayed to potential callers to advise callers why the call will not be answered or when the user might become available again; and

Figure 7 is a functional flow diagram that illustrates how a caller can override call screening according to an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENT(S) OF THE INVENTION

[0044] For simplicity and illustrative purposes, the present disclosure is described by referring mainly to an example thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure. As used herein, the terms "a" and "an" are intended to denote at least one of a particular element, the term "includes" means includes but not limited to, the term "including" means including but not limited to, and the term "based on" means based at least in part on.

[0045] Implementations, described herein, may address technical problems by enabling a user device to be improved by causing the device not to accept a phone call (and hence prevent the user from being disturbed) in circumstances where the user is unavailable according to an availability status or an availability status update associated with the user. Further, by implementing an availability schedule and taking into account an availability status of the user according to the availability schedule, the implementation(s) described herein are capable of dynamically screening calls based on the availability status of the user. Implementations described herein may also provide a caller with control over whether or not their call should proceed through to the call recipient user device irrespective of the call recipient availability.

[0046] Figure 1 is a concept overview diagram that illustrates how the present invention can be used to cause a user device to allow or prevent a phone call from reaching a user according to an availability of the user, allow users to configure their availability as a schedule, dynamically screen calls based on the availability status (such as driving, working, not-working, etc) of the user, display the availability status of the user to potential callers advising as to why the call will not or cannot be answered and when the user might become available again, and (if enabled by the user) allow a caller to override the screening when the call is of an urgent nature for example.

[0047] A first user (or call recipient) 101 is shown in Figure 1 as a person who receives a phone call via the call recipient's phone (or mobile device, or first device) 103. The phone or mobile device may be capable of making calls as well as receiving phone calls and may operate any software application required to enable the functionality.

[0048] In an embodiment, only the first user 101 has a software application operating on his or her phone that enables the functionality of the present invention, and in this regard, the method of screening a call may involve receiving, by the first device 103, input relating to a status or status update of the first user 101 , the status or status update relating to an availability of the first user to accept a phone call, and when the status or status update indicates that the first user 101 is available, ensuring one or more contacts associated with the first device 103 are not present in a blocked caller list associated with the first device. When the status or status update indicates that the first user 101 is unavailable, the method may further include ensuring the one or more contacts associated with the first device 103 are present in the blocked caller list associated with the first device. Then, when receiving a phone call from a contact who is present in the blocked caller list, the call is prevented from reaching the first device 103 and therefore does not disturb the first user 101 .

[0049] Receiving input relating to a status or status update of the first user 101 may be by any means including, but not limited to, a user physically changing their availability status using the first device 103, or the first device 103 accessing information from a storage means associated with the first device or a remote source of information. For example, a status of "unavailable" may arise when the first user is driving, and this status may be automatically triggered, according to an embodiment, by tracking GPS movements of the first device and identifying that the first user is moving at a speed indicative of travel in a vehicle (for example). The GPS location of the first device 103 may also be used to indicate other useful information regarding the location and availability status of the first user. It is to be understood that additional automatic availability status updates may be triggered by tracking information associated with the first user and/or the first device.

[0050] Also shown in Figure 1 is an embodiment involving the use of a call recipient's availability schedule 105 which allows a user to configure and store their availability to receive phone calls from all or a selection of contacts. This may be as simple as setting availability for all contacts or may be specific to certain groups or individual contacts. For example contacts in a family group may have a different availability schedule to those in a work colleagues group. The schedule 105 may also provide a reason for unavailability such as 'at work', 'personal commitment' or 'in meeting'. Further, the availability schedule may be complex and include repeating periods such as daily, weekly or monthly, and have different schedules for business day, public holidays and weekends. The schedule 105 may also access one or more calendar(s) associated with the first device 103 or a remote database to automatically populate availability information.

[0051] It should be noted that at any point in time the user's status may be different for different callers or call groups. For example at night the caller may have a status of 'available to receive calls' from their family and friends but 'unavailable to receive calls' from work colleagues.

[0052] Based on the call recipient's availability, the invention embodied herein may dynamically change 107 the blocking of calls made to the call recipient's phone or mobile device 103 by adjusting the phone's "blocked list" (or blocked caller list) 109 which is a list of names or numbers that will be rejected by the phone if calls are received from the blocked names or numbers.

[0053] Figure 1 further illustrates a second user (or a potential caller) 1 1 1 who is seeking to contact the call recipient, and the potential caller's phone (or mobile device, or second device) 1 13. The potential caller's phone may be capable of receiving calls as well as making phone calls and operating any software application required to enable such functionality.

[0054] In an embodiment where the second device also has a software application operating that enables the functionality of the present invention, the mobile device 1 13 may be configured to display to a potential caller, via a user interface 1 17, the availability of their contacts, such as the first user 101 , prior to attempting to call. Additionality the interface 1 17 may display a reason for unavailability such as 'at work', 'personal commitment' or 'in meeting' and may indicate when the user may become available to receive calls. [0055] The caller may be allowed to override 1 19 the screening when the call is of an urgent nature, or for any other reason, by requesting that the call proceed irrespective of the availability status of the call recipient 101 . This may be a function that first needs to be enabled by the call recipient 101 on their device 103.

[0056] If the user 1 1 1 selects to request a call irrespective of the first user's unavailability, the recipient's blocked caller list 109 may be modified 121 to receive the call. The invention may dynamically modify the call recipients blocked list (109) to allow the call to be received, as will be described in more detail below. Once this has occurred the call can be initiated.

[0057] Figure 1 further illustrates by arrow 123 the phone call from the potential caller 1 1 1 to the call recipient 101 , a call initiation interface 125 on the second user's phone 1 13, the network 127 that carries the phone call, and the interface 129 on the first user's phone 103 indicating that the call has been received by the call recipient 101 according to an embodiment.

[0058] Figure 2 provides a solution overview diagram which outlines the components that form a solution according to an embodiment and how these components interact together to enable the embodiment. It will become evident that Figure 2 and subsequent Figures repeat certain features from Figure 1 but nonetheless have been renumbered. In this regard, the reader will appreciate that Figure 2 again illustrates a first user (or call recipient) 201 , the first user's mobile phone (or mobile device, or first device) 203, a potential caller (or second user) 205, and the second user's mobile phone (or mobile device, or second device) 207.

[0059] A software application 209 that operates at least on the first device 203 but in an embodiment is installed and operable in both the first 203 and second 207 devices, is also shown in Figure 2. It should be noted that it is not mandatory for the potential caller to use this application, however, certain functionality including the ability for the caller (second user) 205 to view the availability status of the first user 201 and to override the first user's block in the case of urgent contact, is only possible if the second device 207 is also operating the software application 209. Arrows 21 1 indicate the software application 209 being downloaded and installed in each of the first user's device 203 and the second user's device 207. The application could be downloaded from an online store or other source.

[0060] Figure 2 also illustrates one or more servers 215 that may be operated to run the 'back-end' application according to an embodiment. These servers may communicate with the mobile application 209 operating on the first and potentially also the second users' mobile device through an Application Programming Interface (API). This communication may occur via a data network such as the internet, for example, via a Wi-Fi or cellular data connection. The one or more servers 215 may store a list of registered users 217, for example, in one or more database tables within the 'back end' server application that contain information regarding each registered user. The process associated with each user registering with the application is outlined in more detail below.

[0061] The one or more servers 215 may also store any availability schedule that has been created by or on behalf of the first user 201 , and for any other registered users, and again one or more database tables within the 'back end' server application may be utilised. The availability schedules may be used to provide availability information to other users and to dynamically screen phone calls, as described herein.

[0062] The one or more servers 215 may communicate a push notification service, such as Apple VoIP Push Notifications, to initiate actions on the solution mobile application 209. This may be used to avoid the need to maintain a constant internet connection between each device and the one or more servers 215.

[0063] Figure 2 once again illustrates a blocked caller list 223 including a list of numbers that will be rejected by the phone if a call is received from any one of those numbers.

[0064] As discussed earlier, users can register 225 to use the solution by providing, for example, user, mobile phone and payment details. Upon successful registration a user will be added to the registered user list 217. This process is further detailed, according to an embodiment, in Figure 3. Once registered, users can regularly maintain their availability to receive phone calls by modifying 227 their availability schedule 219. This process is further detailed, according to an embodiment, in Figure 4. [0065] As a user's availability changes based on their schedule 219, the system may dynamically trigger 229 changes to the user's blocked caller list 223 by using the push notification service 221 . Effectively, the server will tell the application on the user's mobile phone to adjust the blocked caller list 223 which will cause the phone to accept or reject calls from certain contacts. This process is further detailed, according to an embodiment, in Figure 5.

[0066] Users who have the application software 209 operating on their mobile devices and who are linked as contacts on their respective devices may be able to see each other's availability at any point in time, for example, via a user interface 231 associated with their device. This may be achieved by requesting availability schedule information 219 from the one or more servers 215. This process is further detailed, according to an embodiment, in Figure 6.

[0067] An override screening process 233 may allow a caller to override the blocking of the caller, even when the call recipient's status is unavailable, for any reason including when the call is of an urgent nature, by requesting that the call progress. This may be a feature of the application 209 that needs to be enabled by the call recipient 201 or may be permanently enabled. The one or more servers may use the push notification service 221 to modify the call recipient's caller block list 223 to allow the call. Once this has occurred the call may be initiated 235 via the phone network 237, and received 239 by the call recipient 201 . This process is further detailed, according to an embodiment, in Figure 7.

[0068] The following paragraphs describe the embodiments featured in Figures 3 to 7 in more detail.

[0069] Figure 3 illustrates a functional flow diagram of an embodiment in which users download a software application, then register to use the dynamic call screening system and method embodied herein. A person 301 who prefers to use the dynamic call screening solution as either a call recipient and/or a caller may use their phone or mobile device 303, which is capable of making and receiving calls, to download, install and operate a software application 305. In particular, the user 301 may download (from an application store or similar) and install 307 the application 305 on their phone or mobile device, and then launch 309 the application 305. [0070] The user 301 may be presented with an interface 31 1 that allows the user to log in if they are already registered or to register 313 as a new user. The registration interface 315 may enable a user to enter details via one or multiple screens. The information requested of the user may include their mobile number, name, email and address information. The interface 315 may also include a profile photo and payment information to use the solution. When the user selects 317 to submit the registration, the data entered may be confirmed and validated to ensure that minimum data format and mandatory data requirements are completed.

[0071] The application software may then be caused to submit 319 the registration request containing the user's registration data to one or more servers 321 (that may run the "back-end" application) via a data network such as the internet. Typically the user's phone will have a data connection such as Wi-Fi or cellular data connection that may be utilised. Internal 'back-end' application processing 323 may then occur by the one or more servers to process the registration request containing the user's registration data. Further, the one or more servers may validate 325 the data provided in the request, and may identify issues with the data that would be returned as error to the users.

[0072] In addition, the one or more servers may verify 327 the mobile number by generating and transmitting 329 a notification using the mobile number provided, such as Short Message Service (SMS), to the mobile number. The notification may contain a confirmation code that is displayed via interface 331 to the user, which may enable the user to confirm 333 the registration using the code by entering via interface 335 the confirmation provided in the notification. The user may then select to submit 337 the confirmation code, and the application software may submit 339 the confirmation code via a data network such as the internet to the one or more servers 321 . Typically the phone has a data connection such as Wi-Fi or cellular data connection which may be utilised.

[0073] The one or more servers 321 may check that the conformation code matches the code sent in the notification. If this and all other validation and payments are successful, the user registration may be created 341 . If the code doesn't match or if other validation or payments fail, errors may be returned to the user. Finally, the server may return 343 information back to software application operating on the phone indicating the success or (failure) of the registration, and the user may be presented via interface 345 with the results of the registration process. If it is successful the user can then use the application. In the event of an error this would need to be corrected and all or some of the registration process repeated. It is to be understood that this is but one way of registering and validating a user, and the present invention is not limited to the registration/validation process described.

[0074] Figure 4 illustrates a functional flow diagram that demonstrates, according to an embodiment, how the present invention can be used to configure the user's availability and according to an embodiment, an availability schedule, to receive phone calls. Figure 4 also includes features that have been previously described, including but not limited to, a user 401 who is seeking to use the dynamic call screening system and method embodying the present invention as either a call recipient and/or a caller, the user's phone or mobile device 403 capable of making and receiving phone calls and operating the solution mobile application, and the software application 405 operating on the mobile device 403.

[0075] When a user launches 409 the application 405, an interface 41 1 may be presented which allows the user to log in if the user is not already logged into the application. This screen may allow the user to enter their Log In credentials such as username and password, and the user credentials may be verified. If successful, the user may be logged in 413 to the application. The user may then be presented with a menu interface 415 containing a range of options, including but not limited to Contacts, Availability, and Account. When one of these menu items is selected, the user may be navigated 417 to the relevant interface(s).

[0076] For example, interface 419 relates to Availability, and this interface may enable the user to view and maintain their availability to receive phone calls. This may be achieved by providing the user with the ability to select 'available' or 'unavailable' as a general status, or alternatively, provide the user with the ability to create an availability schedule. The user may also be requested to select reasons for their unavailability such as 'at work', 'personal commitment' or 'in meeting'. Further, a user may elect to apply call screening to all contacts, or to certain groups or individual contacts. For example, contacts categorised in a "family" group may have a different availability schedule to contacts categorised in a "work colleagues" group. The application software may also enable the user to create such groups by accessing the contacts list associated with the user's device and enabling the user to establish and name a new group and select certain contacts as group members. In the embodiment where an availability schedule is created by the user, as shown in interface 419, start and finish times may be entered by the user which define blocks of time in which the user is available or unavailable. For example, a user may create a schedule for a weekday where 9.00am may be entered to define an 'unavailable' start time and 5.00pm may be entered to define an 'unavailable' finish time, representing the hours that the user is working during the day and prefers not to be disturbed. Such a schedule may include repeating schedules such as daily, weekly or monthly, and have different schedules for business day, public holidays and weekends. The software application may also be programmed to access one or more calendars of the user to automatically populate availability information.

[0077] Once the user has made changes to their availability they may submit these changes which will ultimately update 421 their status and/or schedule. The application may create and submit a schedule update request 423 containing the user's updated schedule data to the one or more servers 425 via a data network such as the internet. As previously mentioned, typically the phone has a data connection such as Wi-Fi or cellular data connection which may be utilised. The one or more servers 425 may engage in internal 'back-end' application processing 427 in order to process the schedule update request 423containing the user's updated schedule data, and may validate the data provided in the request. Issues with the data may be returned as error to the users, but if there are no issues, the availability schedule for the user may be updated 429 to reflect the submitted changes. The availability schedule in Figure 4 is labelled using reference numeral 431 .

[0078] In an alternative embodiment, the availability schedule may be stored in a memory associated with the call recipient's device and accessed directly from the memory. In a further alternative embodiment, an availability schedule is not used and the software application operating on the call recipient's device may present an option to the call recipient to manually update his or her global status in the software application. [0079] Figure 5 illustrates a functional flow diagram that demonstrates, according to an embodiment, how the present invention may dynamically screen calls based on the user's availability status, such as driving, working, not-working, etc. Figure 5 also includes features that have been previously described, including but not limited to, a user 501 seeking to use the dynamic call screening system and method embodying the present invention as either a call recipient and/or a caller, the user's phone or mobile device 503 capable of making and receiving phone calls and operating software application 505, a blocked caller list 509 listing numbers that will be rejected by the phone 503 if a call is received from one of the listed numbers, one or more servers 51 1 that run the back-end application, processing 513 by the one or more servers to process changes to the blocked caller list associated with the user device 503, and an availability schedule 515.

[0080] In this embodiment, the one or more servers 51 1 may monitor the schedule of all users to identify points in time 517 when a user's blocked caller list needs to be modified, for example, the point in time when a user's pre-programmed schedule changes from being unavailable to available, or vice versa. When the user's blocked caller list needs to be modified, the user's device may receive a status update 519 that triggers a change to their blocked caller list. This may involve using the previously described push notification service 521 of the one or more servers 51 1 . Effectively, the one or more servers 51 1 may communicate the notification 523 to the application on the user's mobile phone, which are effectively instructions to adjust the blocked caller list in a manner that causes the phone to receive or reject calls from certain contacts. In the background the mobile application 505 may update the block list 509 accordingly, which will cause the phone to receive or reject calls from the particular contact(s).

[0081] Figure 6 illustrates a functional flow diagram that demonstrates, according to an embodiment, how the availability status of the user may be displayed to potential callers to advise callers as to why the call will not be answered or when the user might become available again. Figure 6 also includes features that have been previously described, including but not limited to, a user 601 who is seeking to use the dynamic call screening system and method embodying the present invention as either a call recipient and/or a caller, the user's phone or mobile device 603 capable of making and receiving phone calls and operating the software application 605, launching 609 of the application on the device which presents a login screen 61 1 to the user, having user credentials verified 613 and if successful logging the user in, and presenting the user with a menu interface 615 containing a range of options, including but not limited to Contacts, Availability, and Account such that when one of these menu items is selected, the user may be navigated to the relevant interface(s).

[0082] In this embodiment, in the event the user selects the Contacts option, the application may send a request 619 for the availability information of the user's contacts to the one or more servers 621 , and the internal 'back-end' application may cause the request for contact availability data to be processed 623 retrieves 625 availability data associated with each user by querying the availability schedule 627. The one or more servers 621 may return 629 the availability data to the requesting mobile application, and typically the phone will have a data connection such as Wi-Fi or cellular data connection which may be utilised. The user can then view availability of their contacts via one or more screens 631 , at least one of which may include a list showing all users and their availability, or a more detailed screen showing only a single contact's availability.

[0083] Figure 7 illustrates a functional flow diagram that demonstrates, according to an embodiment, how a caller can override call screening when the call is of an urgent nature, or for any other reason. Figure 7 includes features that have been previously described, including but not limited to, a first user (or call recipient) 701 , the call recipient's device 703 capable of at least receiving phone calls and operating a mobile application 705, a second user (or potential caller) 709, and the second user's phone or mobile device 71 1 capable of at least initiating phone calls and operating the mobile application 705.

[0084] In the embodiment of Figure 7, process 713 involves the potential caller 709 launching the application 705, logging in and viewing the availability of a contact that they prefer to connect with via a phone call. The potential caller sees that the contact 701 has their status set to unavailable 715. However, since the contact (call recipient) 701 has enabled, through his device, to allow for call screening to be overridden (e.g. in respect of calls of an urgent nature), the potential caller 709 has the option to request 717 that the call progress irrespective of the unavailable status of the contact 701 . The software application 705 may create and submit a request 719 to one or more servers 721 for the one or more servers to unblock the potential caller 709 on the call recipient's device 705. The one or more servers 721 may include internal 'back-end' application processing to process 723 the request to override the screening.

[0085] The one or more servers 721 may trigger the modification 725 of the call recipient's blocked caller list associated with the first device 703, and this may involve using a push notification service 727 as previously described. Effectively, the one or more servers may communicate a notification 729 to the application operating on the user's mobile phone 703 in the form of instructions to adjust or modify 731 the blocked caller list 733. This will ensure that the contact's phone number is not present in the blocked caller list, and will allow the phone 703 to receive the call from contact 709. In other words, once the potential caller 709 has been successfully unblocked, the call will be initiated 737 via the phone network 739 and the call will be received 741 by the call recipient 701 .

[0086] The skilled person will appreciate the advantages afforded by the present invention including improving a mobile (cell) phone or similar communication device to dynamically screen communication requests sent to the device according to a real-time status of the user's availability.

[0087] Throughout this specification and claims which follow, unless the context requires otherwise, the word "comprise", and variations such as "comprises" and "comprising", will be understood to imply the inclusion of a stated integer or step, or group of integers or steps, but not the exclusion of any other integer or step, or group of integers or steps.

[0088] The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any suggestion that the prior art forms part of the common general knowledge in Australia.

Claims

The claims defining the invention are as follows:

1 . A computer-implemented method of dynamically screening communication requests, the method including: receiving, by a first device, input relating to a status of a first user associated with the first device, the first device configured to provide an alert to the first user upon receipt of a communication request, and the status relating to an availability of the first user to accept a communication request; when the status indicates that the first user is unavailable, ensuring that one or more contacts associated with the first device are present in a blocked list associated with the first device; when the status indicates that the first user is available, ensuring that the one or more contacts associated with the first device are excluded from the blocked list associated with the first device; receiving, by the first device, a communication request from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device; and when the second user is present in the blocked list associated with the first device, preventing the first device from providing an alert to the first user regarding a contact attempt by the second user.

2. A computer-implemented method according to claim 1 , wherein the communication request is a voice call, and the blocked list is a blocked caller list.

3. A computer-implemented method according to claim 1 , wherein the communication request is a text message or a video call.

4. A computer-implemented method according to any one of the preceding claims, further including: when the status indicates that the first user is unavailable and the second user is present in the blocked list associated with the first device, causing the first device to transmit a notification to the second device regarding the first user's status.

5. A computer-implemented method according to claim 4, wherein the notification is in the form of a text message or pre-recorded voice message transmitted to the second device.

6. A computer-implemented method according to any one of the preceding claims, further including: when the second user is excluded from the blocked list associated with the first device, permitting the first device to provide the alert to the first user.

7. A computer-implemented method according to any one of the preceding claims, wherein the alert is a visible and/or audible and/or vibratory alert associated with the first device receiving an incoming communication request.

8. A computer-implemented method according to any one of the preceding claims, further including: receiving, by the first device, an override request from the second user to override preventing the first device from providing the incoming call alert to the first user, and where the first user has enabled modifications to the blocked caller list in the first device, modifying the blocked caller list of the first device to ensure the second user submitting the override request is excluded from the blocked caller list, thereby permitting the first device to provide the alert to the first user.

9. A computer-implemented method according to any one of claims 1 to 7, further including: receiving, by the first device, an override request from the second user to override preventing the first device from providing the incoming call alert to the first user, and where the first user disables modifications to the blocked caller list in the first device, causing the first device to transmit a notification to the second device regarding the first user's status.

10. A computer-implemented method according to claim 9, wherein the notification is in the form of a text message or pre-recorded voice message transmitted to the second device.

1 1 . A computer-implemented method according to any one of the preceding claims wherein ensuring one or more contacts associated with the first device are excluded from a blocked caller list associated with the first device includes adjusting the blocked caller list to remove the one or more contacts, if present in the blocked caller list, from the blocked caller list.

12. A computer-implemented method according to any one of the preceding claims, wherein ensuring one or more contacts associated with the first device are present in a blocked caller list associated with the first device includes adjusting the blocked caller list to admit the one or more contacts, if excluded from the blocked caller list, to the blocked caller list.

13. A computer-implemented method according to any one of the preceding claims, wherein receiving input relating to a status of the first user includes receiving, via a user interface of the first device, input from the first user relating to the first user availability.

14. A computer-implemented method according to any one of the preceding claims, wherein receiving input relating to a status of the first user includes receiving, from an application operating on the first device or from a remote source, input relating to a global positioning system (GPS) location of the first user.

15. A computer-implemented method according to any one of the preceding claims, wherein receiving input relating to a status of the first user includes receiving, from a storage means associated with the first device, input relating to the first user availability according to an availability schedule stored in the first device storage means.

16. A computer-implemented method according to claim 15, wherein the availability schedule includes status updates for pre-defined time intervals over a pre-defined time period.

17. A computer-implemented method according to claim 16, further including: receiving, via a user interface of the first device, input relating to a change to a start and/or end time of a time interval.

18. A computer-implemented method according to any one of claims 1 to 14, wherein receiving input relating to a status of the first user includes receiving, from one or more remote servers, input relating to the first user availability according to an availability schedule stored on the one or more remote servers.

19. A computer-implemented method according to claim 18, wherein the availability schedule includes status updates at pre-defined time intervals over a pre-defined time period

20. A computer-implemented method according to claim 19, further including: receiving, via a user interface of the first device, input relating to a change to a start and/or end time of a pre-defined time interval, generating, by the first device, updated schedule data based on the input relating to a change to a start and/or end time of a pre-defined time interval, and transmitting, from the first device to the one or more servers, a schedule update request containing the updated schedule data, wherein receiving, from one or more remote servers, the input relating to the first user availability according to an availability schedule stored on the one or more remote servers is a push notification from the one or more servers to the first device.

21 . A computer-implemented method according to claim 20, wherein the push notification is a VoIP push notification communicated through an Application Programming Interface (API).

22. A computer-implemented method according to either claim 20 or claim 21 , wherein push notifications from the one or more servers to the first and/or second device further includes instructions to an application operating on the first and/or second device to perform one or more actions.

23. A computer-implemented method according to claim 22, wherein the one or more actions include one or more of: providing a status update to the first device according to an availability schedule stored on the one or more servers; adjusting the blocked caller list of the first device; or providing a notification to the second device regarding the first user's availability status and when the status is scheduled to change according to the first user's availability schedule stored on the one or more servers.

24. A computer-implemented method according to any one of claims 15 to 23, the availability schedule is linked to, and the start and end times associated with pre-defined time intervals in the schedule are updated in accordance with, one or more calendars associated with the first device.

25. A computer-implemented method according to any one of the preceding claims, wherein the one or more contacts are contacts present in the first device contacts list.

26. A computer-implemented method according to any one of claims 1 to 24, wherein the one or more contacts are a sub-set of contacts in the first device that are selected by the first user and categorised by the first user.

27. A computer-implemented method according to any one of the preceding claims, wherein the status relating to an availability of the first user to receive a call includes a reason for their availability or lack of availability.

28. A computer-implemented method according to claim 27, wherein the reason for the first user's unavailability includes driving, presence at work, presence in a meeting, personal commitment, or sleeping.

29. A computer-implemented method according to either claim 27 or claim 28, further including: when the status indicates that the first user is unavailable and the second user is present in the blocked list associated with the first device, and the first device is caused to transmit a notification to the second device regarding the first user's lack of availability, the notification includes the reason for the user's lack of availability.

30. A computer-implemented method according to any one of claims 27 to 29, further including: where the first user has disabled modifications to the blocked caller list in the first device, and the first device is caused to transmit a notification to the second device regarding the first user's lack of availability, the notification includes the reason for the user's lack of availability.

31 . A computer-implemented method according to any one of the preceding claims, wherein the first and second devices are cell phones associated with the first and second user respectively.

32. A computer-implemented method according to any one of the preceding claims, wherein the first and second devices communicate, via a network interface, with the one or more servers through an API.

33. A system for dynamically screening phone calls, the system including: one or more processors associated with a first device; and a memory in communication with the one or more processors, the memory including instructions, which when executed by the one or more processors causes the one or more processors to: receive input relating to a status of a first user associated with the first device, where the one or more processors are configured to provide an alert to the first user upon receipt of a phone call, and the status relating to the availability of the first user to accept a voice call; when the status update indicates that the first user is unavailable, ensuring the one or more contacts associated with the first device are present in the blocked caller list associated with the first device; when the status indicates that the first user is available, ensuring one or more contacts associated with the first device are excluded from the blocked caller list associated with the first device; receive a voice call from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device; and when the second user is present in the blocked list associated with the first device, preventing the first device from providing the alert to the first user.

34. A computer-readable medium storing instructions executable by one or more processors associated with a first device and upon such execution cause the one or more processors to perform operations including: receive input relating to a status of a first user associated with the first device, the one or more processors configured to provide an alert to the first user upon receipt of a voice call, and the status relating to the availability of the first user to accept a voice call; when the status indicates that the first user is unavailable, ensure the one or more contacts associated with the first device are present in a blocked caller list associated with the first device; when the status indicates that the first user is available, ensure one or more contacts associated with the first device are excluded from the blocked caller list associated with the first device; receive a voice call from a second device associated with a second user, the second user having contact details in the one or more contacts associated with the first device; and when the second user is present in the blocked list associated with the first device, prevent the first device from providing the alert to the first user.

35. A system for dynamically screening phone calls, the system including: a first device associated with a first user, the first device configured to provide an alert to the first user upon receipt of a voice call; a second device associated with a second user, the second device configured to enable the second user to cause the second device to transmit a voice call to the first device; one or more remote servers with which the first and second devices communicate through an API; the first device including a user interface and a memory storing a contacts list and a blocked caller list, the memory further including instructions, which when executed by the one or more processors, causes the one or more processors to: receive an input via the user interface or a notification from the one or more servers relating to a status of the first user associated with the first device, the status relating to the availability of the first user to accept a voice call; when the status indicates that the first user is available, ensure one or more contacts in the contacts list excluded from the blocked caller list; when the status indicates that the first user is unavailable, ensure the one or more contacts in the contacts list is present in the blocked caller list; receive a voice call from the second device, the second user having contact details in the one or more contacts in the contacts list of the first device; when the second user is present in the blocked caller list, prevent the first device from providing the alert to the first user.